June 29, 2008
I’ve had a go at making the ajax GANTT chart respect dependencies, which turned out to be quite tricky as this is happening on a webpage, and I can’t really spend much processor-time laying it all out.
It seems to work just fine on my test-cases, but I’m sure I haven’t thought of everything. 🙂
June 24, 2008
I’ve added a small auto-saving text box to the right menu, which pops up whenever you’re working on something. Whatever you enter in there will be logged to your current work log, so it’s even easier to remember what you’ve done.
June 23, 2008
When I added translations to ClockingIT I went with a really simple system where all the strings to be translated are defined along with their translations in a file, with one file per language. This worked great for initially translating the whole thing to a new language, but it’s broken down as I’ve added more and more languages, changed strings, and added new strings.
To get some new text translated these days, I’ve had to add the strings to 13 different files, and contact 13 different people to do update the translations, some of which don’t have Git and need to have the complete file emailed back and forth.
No more! New strings are now automatically added to a table in the database, and I’ve added a simple form to update the translation of your language. I’ve also added a couple of rake tasks to dump/restore this information to/from the normal language files so you have a backup in case someone makes a mistake.
June 18, 2008
I’ve been running ClockingIT for quite a while now, and at some point something was introduced which made the memory usage grow and grow over time. I installed God to monitor and restart my Mongrels whenever they grew too big, but I can’t say I’ve been very comfortable with that solution.
Then, when I bought a new server to run on, I figured I’d get a bit more RAM and go 64bit to be able to use it. And found out that Ruby uses ~ 2x the memory, due to addresses in every object taking double the space.
I took some time to look for a better solution, and found something which works really great for me.
Setup Time VIRT RES ----------------------------------------------- MRI/Mongrel 0m37.607s 181660 120720 MRI/Mongrel/Erubis 0m37.536s 181660 120920 MRI/Mongrel/Slim 0m36.399s 181672 119300 MRI/Mongrel/Erubis/Slim 0m36.020s 182696 120064 GC/Mongrel 0m37.416s 177560 119268 GC/Mongrel/Erubis 0m37.260s 172440 114484 GC/Mongrel/Slim 0m35.024s 164260 105656 GC/Mongrel/Erubis/Slim 0m35.049s 163236 104656 MRI/Thin 0m36.828s 172624 111512 MRI/Thin/Erubis 0m36.878s 175696 114724 MRI/Thin/Slim 0m35.457s 175708 113532 MRI/Thin/Erubis/Slim 0m35.087s 176732 114700 GC/Thin 0m36.208s 166476 108888 GC/Thin/Erubis 0m36.121s 166476 108724 GC/Thin/Slim 0m33.854s 155224 97060 GC/Thin/Erubis/Slim 0m33.832s 155224 97080
Keep in mind that this is on a 64bit platform, so a 32bit version would use ~ half the memory.
I’m getting a lot fewer restarts of my webservers with this setup, which can only be a good thing. It’s also been rock solid after ironing out a couple of problems with Slim Attributes.
June 17, 2008
I’ve had a bit of fun lately, adding a way to easily see your schedule and make changes. It’s not a strict gantt chart like MS Project uses, but rather an automatic one which shows remaining work as time passes and work is logged.
Whenever an estimate or due date is changed, the chart is automatically updated and re-scheduled to try and accomodate your wanted schedule.
If multiple people are assigned to the same task, it’ll be scheduled for when everyone has time free. This will probably be possible to specify with an option later on.
I’m also not sure if filtering the list makes a lot of sense, as you’d end up with either a bogus schedule (consider only the shown tasks) or strange gaps in the schedule (occupied by hidden tasks).
Hope you find it as usefull as I do. 🙂
June 2, 2008
As I’m at home with my young daughter these days on paternity leave, I needed something to do while she had her naps in the mornings. I really liked the idea of a Facebook-ish messaging system, which someone suggested on the forums, and started last Tuesday.
On Saturday, it was ready for launch, and is now live. 🙂
Total implementation time, 9.5 hours including styling and fiddling with IE6.