Thursday, May 3, 2007
Derailed by baby
Just in case anyone has actually looked at this and wondered where the content was hiding; I wanted to inform you that due to the arrival of new daughter I haven't posted in the last few weeks. Sorry. Will try to make time to continue to post but can't promise anything. Sleep has now become a premium.
Wednesday, April 11, 2007
Initial Outline for the Hack's next posts
There are lots of resources out there for getting started (I should link to those here). I don't want to try to be another one of those (not that there is anything wrong with that). So, I'm gonna try to keep my topics germane to the theme "Hack".
NOTE: Some of these issues might have been addressed in a later dojo build (I really hope so in some cases). As mentioned before this is as pertaining to dojo 0.3.1 build. Now you might ask why bother writing this about already antiquated code? And that's a good question.
1. Adding simple APIs to widgets to greatly improve usability. Don't be afraid to Hack.
2. Fixing the widget engine's bug with loading CSS repeatedly.
3. Fixing dynamically created widgets so they don't all fire "checkSize" when the browser resizes.
4. Building extension widgets that supplement existing widgets without modifying the original widget (something I wish I had known/realized before).
5. Hacking the dojo build (ie making a custom build)
6. Making compiled / compressed "master" javascript files to be served beside dojo to reduce dojo.js's footprintacross several pages but still keep a small overall pageload.
7. Fixing the IE6 operation aborted error caused by using certain widgets
That should be enough for now. I'll get to those posts...now...(or at least soon)
Again, as always, thanks for reading.
NOTE: Some of these issues might have been addressed in a later dojo build (I really hope so in some cases). As mentioned before this is as pertaining to dojo 0.3.1 build. Now you might ask why bother writing this about already antiquated code? And that's a good question.
1. Adding simple APIs to widgets to greatly improve usability. Don't be afraid to Hack.
2. Fixing the widget engine's bug with loading CSS repeatedly.
3. Fixing dynamically created widgets so they don't all fire "checkSize" when the browser resizes.
4. Building extension widgets that supplement existing widgets without modifying the original widget (something I wish I had known/realized before).
5. Hacking the dojo build (ie making a custom build)
6. Making compiled / compressed "master" javascript files to be served beside dojo to reduce dojo.js's footprintacross several pages but still keep a small overall pageload.
7. Fixing the IE6 operation aborted error caused by using certain widgets
That should be enough for now. I'll get to those posts...now...(or at least soon)
Again, as always, thanks for reading.
Welcome to the Hack
Welcome to the Hack the Dojo blog. My name is Brec Carson and I've been working with Dojo as a Javascript framework for about a year now. I'm starting this blog now as an attempt to pass on and archive what I've learned.
Dojo has been, during this year, a moving target as far as frameworks go. So, most of my experience has been with the 0.3.1 build. We settled on that build mostly because of a large investment in time I made to create a Table Tree widget. When 0.4.0 came out and the widget didn't work we decided that there wasn't a pressing need to migrate. Our next migration will happen (I anticipate) with either the 0.9.x or 1.0 builds as the expectation is that the base will solidify at that point.
Thanks for reading. Next post I'll try to get into my point in making this blog. Namely demonstrating my use of dojo as I understand it. Hopefully it's useful to someone (anyone) else.
Dojo has been, during this year, a moving target as far as frameworks go. So, most of my experience has been with the 0.3.1 build. We settled on that build mostly because of a large investment in time I made to create a Table Tree widget. When 0.4.0 came out and the widget didn't work we decided that there wasn't a pressing need to migrate. Our next migration will happen (I anticipate) with either the 0.9.x or 1.0 builds as the expectation is that the base will solidify at that point.
Thanks for reading. Next post I'll try to get into my point in making this blog. Namely demonstrating my use of dojo as I understand it. Hopefully it's useful to someone (anyone) else.
Subscribe to:
Posts (Atom)
