Z
Zed A. Shaw
Hi Everyone,
I'm finally done tinkering and messing with my latest rendition of
CookbooXUL. Feel free to read all about it at:
http://www.zedshaw.com/projects/cookbooxul/
It comes with available code, which will work once you install Rails and
Ruby/Odeum from my site as well. You'll also have to download recipes
and such to get it all up on your own. It's released LGPL for now.
The neat things about this are:
1. Uses a very thin Rails backend with a thick XUL/XPFE frontend.
2. Client is controlled by a little Finite State Machine framework I
wrote that simplifies the application logic.
3. It's completely asynchronous, which is easy to do with the FSM.
4. The FSM framework includes lots of goodies for working with the DOM,
pasting in XSLT, and doing asynch XmlHttpRequests.
5. The backend actually passes back events to the client using a special
HTTP header (X-AppState).
6. It includes the same 10,000 recipes.
7. It demonstrates modifying the XUL interface using an XSLT based on a
response.
8. Demonstrates doing a timer 'tick' to work the UI while waiting for
something.
9. There's a demo available at http://zedsucks.dhs.org:8000/recipes/
(also mentioned in the article). This is up as long as I can keep it
without pissing off my ISP.
I fixed a ton of bugs, but I'm sure there's more. Feel free to send
them my way as well as comments. Hopefully the article is detailed
enough to get you started, but not so detailed that you don't have fun
figuring it out.
Zed
I'm finally done tinkering and messing with my latest rendition of
CookbooXUL. Feel free to read all about it at:
http://www.zedshaw.com/projects/cookbooxul/
It comes with available code, which will work once you install Rails and
Ruby/Odeum from my site as well. You'll also have to download recipes
and such to get it all up on your own. It's released LGPL for now.
The neat things about this are:
1. Uses a very thin Rails backend with a thick XUL/XPFE frontend.
2. Client is controlled by a little Finite State Machine framework I
wrote that simplifies the application logic.
3. It's completely asynchronous, which is easy to do with the FSM.
4. The FSM framework includes lots of goodies for working with the DOM,
pasting in XSLT, and doing asynch XmlHttpRequests.
5. The backend actually passes back events to the client using a special
HTTP header (X-AppState).
6. It includes the same 10,000 recipes.
7. It demonstrates modifying the XUL interface using an XSLT based on a
response.
8. Demonstrates doing a timer 'tick' to work the UI while waiting for
something.
9. There's a demo available at http://zedsucks.dhs.org:8000/recipes/
(also mentioned in the article). This is up as long as I can keep it
without pissing off my ISP.
I fixed a ton of bugs, but I'm sure there's more. Feel free to send
them my way as well as comments. Hopefully the article is detailed
enough to get you started, but not so detailed that you don't have fun
figuring it out.
Zed