Re: [Wonder-disc] A WOSwitchComponent taking an instance rather than a component name = bad idea?

[Amiel M. <bos...@gm...>]

Hey Chuck,

Short story: Because the internet is about to hit 2 billion users and I want
them to use my apps as soon as possible.

Long story: I have 2 apps that needs to use some common components (managing
user accounts, EditUser, Payments ... etc). I have put the common components
in a framework.

Now each app have different user interfaces. (e.g. header, menus, footer,
styles ...etc). Since my common components must not be tightly coupled to
any app, there is a need to create some kind of wrapper component to contain
each common component in each app.

So I was thinking of instead of creating a bunch of wrappers for each common
component, I would just create one wrapper that contains a WOSwitchComponent
and stick any common component I want in there, problem is and if I
understood correctly how WOSwitchComponent works, is that it dynamically
instantiates the component but I need to set some attributes to my common
component before pushing it.

I hope I'm making sense, I'm finding it hard to explain.

Thanks,
Amiel

On Wed, Oct 20, 2010 at 7:22 AM, Chuck Hill <ch...@gl...>wrote:

> OK, I will bite.  Why the hell are you doing that?  :-)
>
>
> On Oct 18, 2010, at 9:21 PM, Amiel Montecillo wrote:
>
> > Hello Guys,
> >
> > I know I am going to get a "why the hell are you doing that or worse
> WTF?" kind of reaction to this but I just need to ask.
> >
> > So is there? or is it a bad idea?
> >
> > Thanks,
> > Amiel
>
>
>
> --
> Chuck Hill             Senior Consultant / VP Development
>
> Practical WebObjects - for developers who want to increase their overall
> knowledge of WebObjects or who are trying to solve specific problems.
> http://www.global-village.net/products/practical_webobjects
>
>
>
>
>
>
>
>


-- 
socket error: unable to connect to 127.0.0.1