Monday, December 01, 2003

technically WriteFree Journal is an InkPicture, 2 toolbars, menus and image files for the template. All development was done on XP or W2K, sometimes with a tablet. The image files are Windows Journal templates exported to tiff and then converted to jpg (am not sure why i went to the trouble).
Most of the development was done using the designers in VS.NET.
R1 will be refactored and then will be refactored some more, it will be componetized so that we can reuse alot of the common stuff.
There will be an R2 and apart from thinking it may be more like OneNote than Windows Journal i don't know what its going to be like.
One of my fears about ink and winforms is that sometimes when you do particular things (zoom in and out for example) it stops behaving like ink and paper, it starts behaving like a windows computer (hanging and might bluescreen) .... that has to change. Paper never hangs and does not need saving (thats why auto save might make sense - in its own thread)

Other than that , i just need to get a break from work to test the thing and see what else i need to do to make it a useful program :)

one thing about WriteFree Journal R1 is that like Windows Journal it seems to suffer performance issues of one type or another, like saving seems to take quite a bit of time. I never multi threaded it and i should. There is also the issue of auto-save, i will bring that up on the messageboard to see what everyone thinks.
Sucks that i can't say much about it since i haven't actually used it. I did some smoke testing but thats about all the testing that i did.
A neat feature of WriteFree Journal R1 is the ability to read and take notes at the same time. A menuitem provides 11 different transparency levels including totally invisible (quite useless) and 2 toolbar buttons provide 9 transparency levels each. I haven't had time to actually beta test R1, so am curious as to how folks will use this feature.
The editor is not as lightwieight as i woul d like it to be and there should be more work done in that area after i get beta testing feedback.
We went with a single document model since not only was that easier to do but most of us never do lots of multiple document notes.
R1 is finally ready

lots of refactoring needs to be done.