Must not lose focus and start new programming project...
Tuesday, August 31, 2004
Why hasn't anyone written a zeroconf app that gives anyone a file explorer ( finder ) of discoverable drives? This could be it's own app ( easier ) or as a kernel level driver, where new drives would be automatically added and removed as they appeared?
Must not lose focus and start new programming project...
Must not lose focus and start new programming project...
Saturday, August 28, 2004
I am extremly impressed with my new PowerBook as a development environment. I started using Interface Builder to prototype a GUI which would eventually be built in Swing and Java. I started poking around for Cocoa documentation... and I found file:///Developer/Documentation/ the Mac OS X Developer Documentation. Wow. I haven't read much, and the docs are pretty high level, but I think it is the kind of docs that I need, just to kick me off into the right direction. I started with the Human Interface guide lines last night. Basic Good Stuff.
It would be fantastic if someone would consolidate the Linux Newbie Documentation into a similar, pleasing package that ships with the OS. man pages are great, once you grok a lot of unix, but getting from newbie to competent is really hard without working around unix gurus. Overview documentation is a great substitute.
It would be fantastic if someone would consolidate the Linux Newbie Documentation into a similar, pleasing package that ships with the OS. man pages are great, once you grok a lot of unix, but getting from newbie to competent is really hard without working around unix gurus. Overview documentation is a great substitute.
Wednesday, August 25, 2004
qpict
iview
Searching for a Mac OS X photo organizer that works with photos in any location and moves them on the hard disk to actual location that you dropped it. No invisible database that obscure your ability to organize your photo folders.
iview looks very promising. It is 49.99 for their home version, I will have to try out the 20 day demo. I can't tell much from qpict's website. I may or maynot check that one out also.
iview
Searching for a Mac OS X photo organizer that works with photos in any location and moves them on the hard disk to actual location that you dropped it. No invisible database that obscure your ability to organize your photo folders.
iview looks very promising. It is 49.99 for their home version, I will have to try out the 20 day demo. I can't tell much from qpict's website. I may or maynot check that one out also.
Monday, August 23, 2004
I think my biggest pet peeve of August 23 2003 - August 23 2004 is the common Java practise of meta-programming with XML. I am all for letting users configure frameworks with their own classnames and if this is machine generated by a visual config editor, than it can be in XML, but don't make users write XML by hand. Worse is scripting in XML using declarative elements and testing attributes, like with ant. This is awful.
XML is great for applications to talk to each other, and we can humans can eavesdrop, but write a parser for a mini-configuration language, or reuse an existing standard, for files edited by hand!
Struts and Ant are the poster children for this problem. They should support a config in xml and a more programmer/sys admin friendly format, that compiles down to build.xml files. If your lazy, that's ok have it do python/other scripting language variables in a file <==> build.xml
XML is great for applications to talk to each other, and we can humans can eavesdrop, but write a parser for a mini-configuration language, or reuse an existing standard, for files edited by hand!
Struts and Ant are the poster children for this problem. They should support a config in xml and a more programmer/sys admin friendly format, that compiles down to build.xml files. If your lazy, that's ok have it do python/other scripting language variables in a file <==> build.xml
Broadcasting from Top-Pot Wireless, I love the Pink Boa. It is the best donut, bar none.
Friday, August 20, 2004
I have been chipping away at my simple templating engine.
I have been having a hard time wrapping my brain around
looping conditions. Basically it took me a while to figure
out a data structure that would allow me to access the
template data as I parsed and executed tempalte code.
I finally have a working prototype. The template programmer
would store their data in multi-dimensional arrays and
put them into the TemplateData instance.
The TemplateEngine will now have a Hashtable for looping
contexts. A Stack is placed into this Hashtable and a
reference to the multi-dimensional array is pushed onto
the stack. As we enter loops, a new value is pushed onto
the stack, which is the Array.get( stack.peek(), index )
of our loopContext. As we delve into deeply nested loops,
we get closer and closer to the String stored in the array.
Once we enter the loop context where the value will be used,
a String is what will be pushed into the stack, instead of
another reference to a multi-dimensional array.
Uses of variables are a simple peek() call.
As we exit loop contexts, we pop the stack.
My prototype is a hardcoded 3x loop, now to generalize the code
to handel n deep loops.
I have been having a hard time wrapping my brain around
looping conditions. Basically it took me a while to figure
out a data structure that would allow me to access the
template data as I parsed and executed tempalte code.
I finally have a working prototype. The template programmer
would store their data in multi-dimensional arrays and
put them into the TemplateData instance.
The TemplateEngine will now have a Hashtable for looping
contexts. A Stack is placed into this Hashtable and a
reference to the multi-dimensional array is pushed onto
the stack. As we enter loops, a new value is pushed onto
the stack, which is the Array.get( stack.peek(), index )
of our loopContext. As we delve into deeply nested loops,
we get closer and closer to the String stored in the array.
Once we enter the loop context where the value will be used,
a String is what will be pushed into the stack, instead of
another reference to a multi-dimensional array.
Uses of variables are a simple peek() call.
As we exit loop contexts, we pop the stack.
My prototype is a hardcoded 3x loop, now to generalize the code
to handel n deep loops.
Thursday, August 19, 2004
I have switched to a 12" PowerBook. Perhaps dual booting will be a think of the past. I am very impressed that OS X started up with perl, python, and ruby pre-installed! I also had the XCode installation package waiting for me under Applications/installers. I fired up Mail which will be handeling all the traffic that filled up gmail :)
Monday, August 16, 2004
I filled up my gmail account! All my email has been bouncing for a week. I have 282402 messages in my spam folder, and would have to delete them 100 at a time by hand. I think this is the end of me and gmail :) Seriously, it is a bad idea to make me "Delete Forever" Trash and Spam. I have already physically searched, checked, and clicked these guys away, why not auto-delete them every 3 days or as space gets tight?
Friday, August 13, 2004
SmaCC compiler compiler for Squeak.
Tuesday, August 03, 2004
Reading the purple book gave me an idea for a javadoc enhancement.
I think it would be helpful if you could categorize your methods
into categories. This has no effect on the java language, but could
be used by javadoc, IDE's, and other tools.
/**
* Get Foo
* @category getters
* @return Foo
*/
Javadoc's framed layout is already similar to a Class Browser, it would be great if the Javadoc Class page allowed you to view only methods of a certain category, or all categories, etc.
Similarly eclipse and other IDE have the ability to collapse blocks of code, with this functionality you show only a certain category, or sort your class outline by category.
Currently I find myself adding comments like
//- Begin getters
...
//- Begin setters
But these comments are fragile and invisible once they are scrolled away.
I think it would be helpful if you could categorize your methods
into categories. This has no effect on the java language, but could
be used by javadoc, IDE's, and other tools.
/**
* Get Foo
* @category getters
* @return Foo
*/
Javadoc's framed layout is already similar to a Class Browser, it would be great if the Javadoc Class page allowed you to view only methods of a certain category, or all categories, etc.
Similarly eclipse and other IDE have the ability to collapse blocks of code, with this functionality you show only a certain category, or sort your class outline by category.
Currently I find myself adding comments like
//- Begin getters
...
//- Begin setters
But these comments are fragile and invisible once they are scrolled away.
