Try the current version of eDAB
One day, eDAB hopes to be a fully fledged replacement for traditional assignment notebooks. It aims to provide a synchronized, cross-platform interface to input and manage homework. Also, people in the same class will be able to share assignments, upcoming tests, and notes, in order to effectively crowdsource information.
Currently, eDAB requires users to authorize via an fcpsschools.net account - which means that only Fairfax County Public Schools will be able to use it. This is mainly because I'm an FCPS student, and federated login is a quick and easy method to ensure that everyone can log in and validate their identity. Obviously, it would be nice if the system was expanded in the future to allow for other school systems, or simply signing in with social media accounts, but that would involve more complexity.
Right now, eDAB is being developed as a web app, hopefully responsive to also work on mobile devices. Further expansion is certainly expected after eDAB actually starts doing something, including a native Android app. But hopefully, the web app will be good enough so that won't be completely necessary.
An early mock-up of eDAB from January 2013
eDAB, on the client side, is a single-page application, thanks to the help of Angular.js. This means it never reloads; it retrieves all data via Ajax (which is really a terribly overused buzzword). It also uses Bootstrap because I'm not that pro at designing. The server-side components were built using Google App Engine. It manages database interactions with Objectify, and the data is marshalled into JSON with the help of Jackson. Finally, it's transferred to the client via a REST-like API powered by Jersey.
If you are interested in contributing, please contact me! Even if you don't know how to use App Engine or Angular.js or any of this, if you're willing to learn or help with anything, including graphics or logo design, promotion, documentation, background photography, please let me know! :)
Before building, you'll need a Config.java file, which contains several configuration details outlined in Config.java.template.
You'll also need a Google APIs Console project.
If you want to contribute, please contact me and I'll give you the proper details for the ones I'm using right now.
Otherwise, if you want to clone eDAB or something, you can create your own configuration file from the template. If you're planning on deploying to App Engine, creating a new App Engine application will also create a Google APIs Console project that you can get a client ID/secret from. And don't forget to change the application id... :c
I've been developing eDAB from Eclipse. So the easiest way to get started is simply to use Eclipse and the App Engine SDK for Eclipse. Check out eDAB from git, and File -> Import the project. From there you can run the development server and work on the project.
If you want to use another IDE or something, make sure you have the App Engine SDK, and include all of the files in /war/WEB-INF/lib in the project's classpath.
I probably can't really help you...
eDAB is a product of Desklamp Studios, which was formed when Richard, Jenny, and I (Kevin) were bored and we wanted to do something in early 2013. We spent a good amount of time planning and making the mock-up shown above together. Since then, I've gotten some baseline code done, which is basically all the project is right now. Contact Desklamp Studios on Google+ if you have any questions!
Later, we may also be looking for aspiring photographers to provide background images for eDAB. :)