Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

Is this feature planned for the next release ? ___ List: Catalyst@lists.rawmode.org Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.rawmode.org/ Dev site:

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

On Mon, May 14, 2007 at 06:05:20PM +0400, Oleg Pronin wrote: Is this feature planned for the next release ? I'm not sure the 'feature' is really well-defined enough yet to call it such. It's going to take somebody with a requirement for something along these lines to spike the work and see what

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

Please tell me how could i implement that without making the interface a complete app ? 2007/5/8, Matt S Trout [EMAIL PROTECTED]: On Mon, May 07, 2007 at 06:58:16PM +0400, Oleg Pronin wrote: I can test the part related to the subject of this thread with great pleasure. I'm currently making

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

On Mon, May 14, 2007 at 06:46:59PM +0400, Oleg Pronin wrote: 2007/5/8, Matt S Trout [EMAIL PROTECTED]: On Mon, May 07, 2007 at 06:58:16PM +0400, Oleg Pronin wrote: I can test the part related to the subject of this thread with great pleasure. I'm currently making full-featured dynamic

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

This interface is accessible under /folder/. It has its own templates, static content, DBIC sources and controllers. What excatly do i need to specify? So please share your ideas :) 2007/5/8, Matt S Trout [EMAIL PROTECTED]: On Mon, May 07, 2007 at 06:58:16PM +0400, Oleg Pronin wrote: I can

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

On Tue, May 08, 2007 at 12:20:33PM +0400, Oleg Pronin wrote: This interface is accessible under /folder/. It has its own templates, static content, DBIC sources and controllers. What excatly do i need to specify? Whether it shares views/models/etc. with the main app, like I asked in my first

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

I think it would be better if it does not. Because AppA don't know and don't want to know the templates and models of AppB. They communicate through controllers only. 2007/5/8, Matt S Trout [EMAIL PROTECTED]: On Tue, May 08, 2007 at 12:20:33PM +0400, Oleg Pronin wrote: This interface is

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

On Tue, May 08, 2007 at 06:13:29PM +0400, Oleg Pronin wrote: I think it would be better if it does not. Because AppA don't know and don't want to know the templates and models of AppB. They communicate through controllers only. How about, after setup_components, injcting AppB's -controllers

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

A good point to start with. As a more complex solution later maybe one should try to store a hash of applications ($c) with all surrounding stuff. And make independent component which will decide which application (i.e. $c) the request is to be dispatched to. Ahh, unfortunately im not familiar

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

On Wed, May 02, 2007 at 08:02:04PM +0400, Oleg Pronin wrote: You didn't understand what i meant. MyApp::A is not a class. It's a whole application with all surrounding stuff. so and MyApp::B. Ok lets build the question in another manner: Catalyst scans for all modules under

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

I can test the part related to the subject of this thread with great pleasure. I'm currently making full-featured dynamic admin interface for catalyst (not so simple as plugin CRUD :) ) And it will have been loaded as plugin into a project (while this interface is catalyst project itself).

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

Yes, your right. I just wanted to start with something simple :) In two worlds, i want the same effect (visual) like this (in apache config): Location / PerlHandler Application_A /Location Location /folder PerlHandler Application_B /Location But in this way the program code A

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

On Mon, May 07, 2007 at 06:58:16PM +0400, Oleg Pronin wrote: I can test the part related to the subject of this thread with great pleasure. I'm currently making full-featured dynamic admin interface for catalyst (not so simple as plugin CRUD :) ) And it will have been loaded as plugin into

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

On Wednesday 02 May 2007 05:30, Oleg Pronin wrote: Greetings! I want to make MyApp::B a part of MyApp::A under namespace for example /folder/ Pretty sure that you can't do this now, although it is a feature planned for the next release. The app/context split branch in svn might have the

[Catalyst] How to make MyApp::B a part of MyApp::A ?

Greetings! I want to make MyApp::B a part of MyApp::A under namespace for example /folder/ Both B and A are normal catalyst applications. (both do '__PACKAGE__-setup()' and etc. and therefore cannot work together). How to do this with minimal changes to application A (for example, using B as

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

Oleg Pronin scribbled on 5/2/07 5:30 AM: Greetings! I want to make MyApp::B a part of MyApp::A under namespace for example /folder/ Both B and A are normal catalyst applications. (both do '__PACKAGE__-setup()' and etc. and therefore cannot work together). How to do this with minimal changes

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

Peter Karman wrote: Oleg Pronin scribbled on 5/2/07 5:30 AM: Greetings! I want to make MyApp::B a part of MyApp::A under namespace for example /folder/ Both B and A are normal catalyst applications. (both do '__PACKAGE__-setup()' and etc. and therefore cannot work together). How to

Re: [Catalyst] How to make MyApp::B a part of MyApp::A ?

Oleg Pronin wrote: You didn't understand what i meant. MyApp::A is not a class. It's a whole application with all surrounding stuff. so and MyApp::B. Ok lets build the question in another manner: Catalyst scans for all modules under MyApp::Controller to build the list of url actions.