zzbbyy at gmail
May 11, 2008, 3:48 AM
Post #4 of 4
(214 views)
Permalink
|
|
Re: Re: Suggestions for default options for CatalystX::Installer
[In reply to]
|
|
Hi,
On Sun, May 11, 2008 at 8:40 AM, Paul Cain <fat.perl.hacker[at]gmail.com> wrote:
> Sorry for replying to my own email, but it appears that
> Catalyst::Example::InstantCRUD could take care of a lot of the
> database configuration work here.
Don't take InstantCRUD too seriously - it is a bit dated it it's
choices. I am now working on porting it to use Rose::HTML::Form
instead of HTML::Widget (which is now unmaintained) - but there is
still a long way ahead of me.
I am also looking forward to base the next Instant on
CatalystX::Installer - so you know - don't make it too circular :)
>
> Also, I wonder if I should post this on the Catalyst mailing list too
> in order to get more feedback on what kind of things people want.
>
> On Sat, May 10, 2008 at 9:43 PM, Paul Cain <fat.perl.hacker[at]gmail.com> wrote:
>> I was thinking about what the default options should be for
>> CatalystX::Installer and am wondering what people want. Basically, I
>> was thinking that they should be configuration information for the
>> most common tools used with Catalyst. CatalystX::Installer runs
>> during or right after the installation of a Catalyst application and
>> takes care of the initial configuration.Therefore, things that are
>> commonly done during that time are a good candidate for adding to list
>> of default options.
>>
>> Here is what I have so far:
>>
>> 1. Login information
>>
>> This is where the user logs into the setup application with a username
>> and password.
>>
>> 2. Required Plugins
>>
>> Here is where the user enters all of the plugins, such as HTML::Widget
>> Authorization::ACL, and StackTrance, that need to be loaded.
>> CatalystX::Installer will then add them to lib/MyApp.pm.
>>
>> 3. Database Locations and Types
>>
>> This is where the user enters the location of and type of all of the
>> database that they are going to use. CatalystX::Installer will then
>> generate all of the necessary config files.
>>
>> 4. Engine
>>
>> The user can select whether to use mod_perl, fastcgi, or something
>> else. CatalystX::Installer will then do the necessary configuration.
>>
>>
>> That is all I have so far. I was also think about having 4 screens, 1
>> for login, 1 for models, 1 for views, and 1 for controllers; however,
>> this might be hard to implement due to how blurry the borders between
>> those last 3 can be.
>>
>> Anyways, I welcome any suggestions for default(or even non-default)
>> options for the setup application(which will consist of HTML forms).
>> I also welcome comments or questions on my current ideas or
>> CatalystX::Installer in general.
>>
>
> _______________________________________________
> Catalyst-dev mailing list
> Catalyst-dev[at]lists.scsys.co.uk
> http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst-dev
>
--
Zbigniew Lukasiak
http://brudnopis.blogspot.com/
_______________________________________________
Catalyst-dev mailing list
Catalyst-dev[at]lists.scsys.co.uk
http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst-dev
|
