Education/Projects/JetpackForLearning/DesignCamp/Projects/Rubrick: Difference between revisions
No edit summary |
No edit summary |
||
| Line 39: | Line 39: | ||
Day 2, 4:46 | Day 2, 4:46 | ||
* Details of the new rubric editor seem to be worked out. Very happy that it'll let me get rid of almost 1000 lines of crappy crufty code and replace it with much more useful and reusable code. But that work has come at the expense of having a complete, working demo for tomorrow. Tactical fail, hopefully long-term strategic win? | * Details of the new rubric editor seem to be worked out. Very happy that it'll let me get rid of almost 1000 lines of crappy crufty code and replace it with much more useful and reusable code. But that work has come at the expense of having a complete, working demo for tomorrow. Tactical fail, hopefully long-term strategic win? | ||
Day 2, 5:00 | |||
Where I got | |||
* biggest issues solved. Most of what I need to do now is more cosmetic, in teh sense that getting Frankenstein's monster ready for the prom is just a matter of doing some cosmetic work | |||
Hopefully for tonight: | |||
* populate with some fresh, real data | |||
* double-check reports | |||
* maybe style-up some things better | |||
Revision as of 23:05, 11 March 2010
Day 1 Status and Plan
- Status -- Needs some luck to make pieces come together
- Several bugs still outstanding
- Distinct aspects of app are mostly working, but need to be integrated
- UI needs lots of help
- Plan for Camp
- Debug, integrate parts, improve UI
- Hopefully add some of the management features (like User lookup)
- Future of Rubrick
- Recruit faculty to work with Rubrick to evaluate it
End of Day 1 Update
Not quite feeling the luck yet, but getting closer.
Each step in the past few weeks has shown me new and better ways to do things that I had already done. The result is lots of code that did similar things, but the more recent code did it better.
And so for the last week or so I gambled on trying to redo lots of old working code to make the approaches and classes used more consistent. Sounded good at the time, but it's taken longer than I'd hoped.
But, with the intense work today, as well as the inspiration from seeing others' projects, I finally got a big stinker of a problem sorted out. I'm hoping that will mean some smoother sailing toward a safe arrival.
So
- One huge issue fixed
- Ready to reintegrate the parts and sort out regression issues
- Ready to chop away a lot of old code based on the revisions
- Brain ready to explode.
Day 2
- Pulling details together
- Making hard choices about what to attempt to have ready to go and what jettison
Day 2, 3:25
- Details of much improved rubric editing coming together, tho it's taken far too long :(
- After that's settled, begin liberal application of band-aids!
Day 2, 4:46
- Details of the new rubric editor seem to be worked out. Very happy that it'll let me get rid of almost 1000 lines of crappy crufty code and replace it with much more useful and reusable code. But that work has come at the expense of having a complete, working demo for tomorrow. Tactical fail, hopefully long-term strategic win?
Day 2, 5:00
Where I got
- biggest issues solved. Most of what I need to do now is more cosmetic, in teh sense that getting Frankenstein's monster ready for the prom is just a matter of doing some cosmetic work
Hopefully for tonight:
- populate with some fresh, real data
- double-check reports
- maybe style-up some things better