Moosifying Jifty.

I've allocated this weekend's time away from the Pugs repository, to concentrate on merging my day $job and Perl 6 -- namely, by converting Jifty from Class::Accessor into Moose, so I can use Class::MOP to implement the long-overdue support for API reflection on Action parameters, as well as use Moose's TypeConstraint for introspection on validators.

Not only this make Jifty coding much more declarative, it also makes it far easier to create custom views -- for example, a RESTish API with an endpoint for each Action, or translating validators as Web Forms 2.0 attributes.

As Web Applications 1.0 gradually matures, we can translate even more of this Object Model to run on the client side via JavaScript, and invent creative embeddings for browser with less native support for client-side continuations.  (See slipwave.info for some nice hackery toward that direction.)

Those techniques will form half of my upcoming OSCON talk; the other half involves put-closures-into-embedded-SQLite, a trick I've used in $job to create stored procedures that are aware of the current Jifty session/continuation context.

This way it's easier to pretend SQLite speaks perl, so the surface experience can begin to resemble DLINQ -- though the inner working is very much different.  More on that later... :-)

Comments

[Humberto Massa]

Have I ever mentioned that you *rock*? Do you think by monday I can get my dirty fingers in Moosefyed Jifty? :-)

[Audrey T]

Humberto: Sure! I've finished converting all use of Class::Accessor to Moose in Jifty, so feel free to check out the branch and see if it still works for you. (Also, try out the trunk version for Jifty-DBI for a nifty compile-time schema definition syntax that's much shorter to write.)