Re: Dynamic loading of a component into a container?
Re: Dynamic loading of a component into a container?
- Subject: Re: Dynamic loading of a component into a container?
- From: David Holt <email@hidden>
- Date: Thu, 28 Jul 2011 10:16:28 -0700
Quicktime for Lion has screen capture/movies built in now...
d
On 2011-07-28, at 9:28 AM, John & Kim Larson wrote:
> Done. Then not done. ScreenFlow didn't work with Lion. As soon as update is done I'll post it.
>
> Sent from my iPhone
>
> On Jul 28, 2011, at 9:46 AM, Pascal Robert <email@hidden> wrote:
>
>> A small podcast to demo how it works would be really cool!
>>
>>> I know this has been a while, but I finished what I call a Remote Component. You put it anywhere in your page. It has static methods that allow you to set the component name and bindings you want to use in the component and puts them in your session dictionary. Wrap the remote component in an Ajax update container, and update it after you've set the component and bindings using the static methods.
>>>
>>> The component generates a WOComponenReference using your component name and bindings (WOAssociations - I've built a couple custom ones since bindings are usually useless here). It then generates a component instance and pushes it to the remote component's subcomponent dictionary with the right elementID. From there it calls invokeAction, takeValuesFromRequest and appendToResponse on the custom component reference.
>>>
>>> The result is that you can put, via Java, any component with any bindings in the remote component's spot on the page. I have a popup modal dialog that I really only want one of, but I want to put lots of different components in it. With WOSwitchComponent I had to have a wrapper around whatever component I wanted to include to take a generic dictionary and extract bindings specific to the component I wanted to show. Now I don't have to do that. You could use it for banners, etc. It seems to work good. ?
>>>
>>> Any interest in seeing this from anyone?
>>>
>>> John
>>>
>>> Sent from my iPhone
>>>
>>> On Jun 10, 2011, at 3:38 AM, Paul Dunkler <email@hidden> wrote:
>>>
>>>> Yes, this is exactly what i am trying to do!
>>>> I will try your approach - But first, i will have a look at the WOSwitchComponent (thanks Chuck!)
>>>>
>>>> Will tell you when i was successfull with that....
>>>>
>>>>
>>>> Am 10.06.2011 um 00:57 schrieb John & Kim Larson:
>>>>
>>>>> If I get what you're asking, you want a div in your app template, say, that you can replace ad hoc from some other component.
>>>>>
>>>>> If so, I've done something similar by pushing the name of the component and a dictionary with bindings to the session dictionary, then in your template pull that name and binding dictionary out of the session, and use that to work a switchcomponent like chuck said that's in the auc. You just have to make sure your contained component knows what to do with your binding dictionary.
>>>>>
>>>>> Sorry if that's unclear. Typing on a rough bus ride one handed.
>>>>>
>>>>> John A. Larson
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>> On Jun 9, 2011, at 3:26 PM, Paul Dunkler <email@hidden> wrote:
>>>>>
>>>>>> At the moment i use the AjaxUpdateLink only to trigger a refresh on the AjaxUpdateContainer. In that AjaxUpdateContainer i defined some WOConditionals... But i want an AjaxUpdateLink to load the content of a component into an empty AjaxUpdateContainer...
>>>>>>
>>>>>> Am 09.06.2011 um 22:22 schrieb John Huss:
>>>>>>
>>>>>>> Isn't this what AjaxUpdateContainer does? What is wrong with using it?
>>>>>>>
>>>>>>> On Thu, Jun 9, 2011 at 3:12 PM, Paul Dunkler <email@hidden> wrote:
>>>>>>> Hey Guys,
>>>>>>>
>>>>>>> is there any possibility in wonder to load a component into a pre-defined zone in the template?
>>>>>>> I´m dealing with AjaxUpdateContainers and so on since 4 months - it´s nice - i like it, but i see no possibility to load something into an AjaxUpdateContainer... If there is any possibility or some of you may have a suggestion how to do this "the good way" in wonder - It would be very nice to hear from you.
>>>>>>>
>>>>>>> For exmaple:
>>>>>>>
>>>>>>> Main-Template:
>>>>>>> <html>
>>>>>>> <head>
>>>>>>> <title>
>>>>>>> </head>
>>>>>>> <body>
>>>>>>> ....
>>>>>>> <wo:AjaxUpdateZone id="testZone" />
>>>>>>> </body>
>>>>>>> </html>
>>>>>>>
>>>>>>>
>>>>>>> Navigation-Template
>>>>>>> <html>
>>>>>>> <head>
>>>>>>> <title>
>>>>>>> </head>
>>>>>>> <body>
>>>>>>> ....
>>>>>>> <ul>
>>>>>>> <li><wo:LoadComponentIntoZoneLink x="AddProductComponent" zone="testZone">Add Products</wo:LoadComponentIntoZoneLink ></li>
>>>>>>> </ul>
>>>>>>> </body>
>>>>>>> </html>
>>>>>>>
>>>>>>>
>>>>>>> (the names of the components are chosen random by me ^^ just for showing you what behavior i want)
>>>>>>>
>>>>>>>
>>>>>>> Thanks in advance!
>>>>>>>
>>>>>>> Best Regards,
>>>>>>> Paul Dunkler _______________________________________________
>>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>>> Webobjects-dev mailing list (email@hidden)
>>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>>
>>>>>>> This email sent to email@hidden
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>> Webobjects-dev mailing list (email@hidden)
>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>
>>>>>> This email sent to email@hidden
>>>>
>>>> Mit freundlichen Grüßen
>>>>
>>>> Paul Dunkler
>>>>
>>>>
>>>> <xyrality_logo_medium.png>
>>>>
>>>>
>>>> -----------------------------------------------------
>>>> XYRALITY GmbH • Lerchenstraße 28a • 22767 Hamburg
>>>> Paul Dunkler • Softwareentwickler
>>>> Mail: email@hidden
>>>> Tel: +49 (0) 40 23 51 78 97
>>>> Mobil: +49 (0) 151 11624143
>>>> Fax: +49 (0) 40 23 51 78 98
>>>> Web: http://www.xyrality.com/
>>>> Registergericht: Hamburg HRB 115332
>>>> Geschäftsführer: Sven Ossenbrüggen & Alexander Spohr
>>>> -----------------------------------------------------
>>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden
>>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden