Hi Brandon,<br><br>InstantCRUD is definitively evolving into the direction that you described below. As we add new features to it (like sessions, authentication, authorisation) it is less and less InstantCRUD and I am thinking about renaming it to InstantApp. It has a replacement for
catalyst.pl. Currently you need to specify all the inputs to it on the commandline - perhaps we can turn it into a wizard but with wizards you still need to at least save the chosen options somewhere so that the user does not need to go again and again through the whole process when fixing some mistakes he did and that makes it a bit complicated.
<br><br>--<br>Zbyszek<br><br><div><span class="gmail_quote">On 7/5/06, <b class="gmail_sendername">Brandon Black</b> <<a href="mailto:blblack@gmail.com">blblack@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 7/3/06, Matt S Trout <<a href="mailto:dbix-class@trout.me.uk">dbix-class@trout.me.uk</a>> wrote:<br>> I think I might have finally figured out the answer:<br>><br>> Catalyst has a One True Way.<br>><br>
> "Do whatever makes most sense within the design of *your* application"<br>><br><br>Agreed here. But to expand in a certain direction: I've always<br>pictured in my head that eventually Catalyst will gain a couple of new
<br>layers on top of the existing open-ended, flexible framework for<br>guiding new users into building apps with minimal effort along the<br>lines of the One True Way (and still making it easy for them, as they<br>become more advanced, to deviate from the One True Way as much as
<br>neccesary).<br><br>One of those layers could be the idea of an app-construction "wizard"<br>of sorts, like catalyst.pl on steroids.<br><br>"Do you need to support sessioning? [Yes]", "Do you need to support
<br>user authentication? [No]", etc .... Importantly, this wizard forces<br>the user down the best practices path. That means it does *not* ask<br>questions like "which view|orm|widget|ajax module?", only questions
<br>that are relevant to the (relatively unknowledgeable about the<br>Catalyst universe) user.<br><br>This wizard then does catalyst.pl + setting all the right plugins, and<br>sets up their basic config file with the right DSNs (and perhaps
<br>commented out examples for changing the config of some of the plugins<br>loaded), and even sets up a few new controllers aside from the<br>standard welcome page, which demonstrate the set of plugins in use and<br>how to use them properly.
<br><br>Its a somewhat tough project (not in coding terms, but more in design<br>terms), but I feel it could be a big win for the Cat community too.<br><br>You could of course take this idea to a whole new level by making a
<br>minimal Cat app implementation of the above wizard, and when the<br>wizard is done it cpan-downloads all the neccesary but missing plugins<br>into the app directory and overwrites itself with the new sample app.<br>Then the user can just "./cat-
wizard.pl MyApp" (which creates the<br>wizard app at MyApp and fires up the built-in server on port 3000),<br>and walk through a web-wizard to tweak up his new application.<br><br>-- Brandon<br><br>_______________________________________________
<br>Catalyst-dev mailing list<br><a href="mailto:Catalyst-dev@lists.rawmode.org">Catalyst-dev@lists.rawmode.org</a><br><a href="http://lists.rawmode.org/mailman/listinfo/catalyst-dev">http://lists.rawmode.org/mailman/listinfo/catalyst-dev
</a><br></blockquote></div><br><br clear="all"><br>-- <br>Zbigniew Lukasiak<br><a href="http://brudnopis.blogspot.com/">http://brudnopis.blogspot.com/</a>