Thanks alot for your quick answer!

You are correct in your interpretation of the problem. Qooxdoo client in a
browser loading application code from different servers. Basically the need
come from having a third-party plugin system for additional views which the
main application might not know at build-time. I could have a central server
but I would rather not do that. I might resort to the JSON/XML approach
which was one of the options we were looking at but when the editors need
particular views it might not be as appropriate. Is there a standard way for
providing third party plugins? Otherwise I guess I'll have to do the
handwork piece in making this possible..

Bests,
Mathieu

On Thu, Mar 3, 2011 at 12:02 PM, thron7-2 [via qooxdoo] <
[email protected]> wrote:

> Mathieu,
>
> thanks.
>
> I'm not sure if I fully get what you're trying to achieve. My impression
> is that you have a qooxdoo client running in a browser, and want to load
> application code from various servers, right?!
>
> If, OTOH, you have a central server, this one could proxy all
> distributed code parts, so the client thinks it is actually getting the
> code from a single host. Could that be?!
>
> On a general level, you have to understand that a qooxdoo application is
> built monolitically: All classes that are eventually used by the
> application have to be known at build-time! You could use parts to
> partition such an application into chunks of code, and distribute these
> chunks to several servers (You would then need to apply some magic to
> the qooxdoo loader to support the loading from the various hosts,
> though). Still, all those distributed parts would be known at build-time.
>
> There is no such concept as "dynamically linking" of components at
> run-time (although there is a project that has achieved that with
> qooxdoo components, but had to build all the infrastructure necessary
> for that on its own). So if this is actually what you are after, i.e.
> loading code at run-time that is _not_ known at build-time, you have to
> do quite a bit of hand-work. There is currently no support for that
> built-in to qooxdoo. People in similar situations have resorted to a
> declarative approach, where all the code is known at build-time, but is
> written in a way that you later at run-time pass in just descriptions of
> GUI elements (e.g in the form of Json or XML), and the existing code
> creates the correpsonding widgets on the fly, and displays them. I don't
> know if that makes sense in your situation.
>
> T.
>
>
> On 03/03/2011 03:30 PM, Mathieu Lemay wrote:
>
> > Dear Qooxdoo devels and community,
> >
> > First I want to say that I love the library , it is well written ,
> > structured and pleasant to work with. So far I've been having no issues
> in
> > doing everything I wanted to do with it . However I have a border case
> which
> > I can't seem to figure out on my own so I'm resorting to some advice.
> >
> > I have centralized management application that talk with many distributed
>
> > servers in different domains using SAML Federated Security. So far , I
> can
> > invoke the data services using cross-domain scripting however I'm trying
> to
> > figure out a way to load UI specific details from the server-side as
> well.
> > What I mean by that is currently each resource types available on the
> > distributed servers must be known in the centralized qooxdoo frontend and
> I
> > would rather "load" the appropriate UI components (Wizards, Forms, etc.)
>  at
> > runtime from these distributed servers so that I could have  a generic
> > central service.
> >
> > I've been looking at the PartLoader or ScriptLoader however I am
> uncertain
> > on how to tackle this problem. Should I use JSONP to load
> Resource-specific
> > (Wizards, Forms,etc) javascript definitions and then use a convention
> naming
> > to load the proper panels? Would PartLoader or ScriptLoader work or
> should I
> > use Requests manually.What would be the recommended approach by on your
> > experience to do such a thing? I don't see many example of that on the
> web
> > as usually cross-domain scripting is to load data-only and not complete
> ui
> > resources.
> >
> > Thank you for your time,
> > Bests,
> > Mathieu
> >
> >
> > --
> > View this message in context:
> http://qooxdoo.678.n2.nabble.com/Cross-Domain-Parts-in-Qooxdoo-application-tp6084959p6084959.html<http://qooxdoo.678.n2.nabble.com/Cross-Domain-Parts-in-Qooxdoo-application-tp6084959p6084959.html?by-user=t>
> > Sent from the qooxdoo mailing list archive at Nabble.com.
> >
> >
> ------------------------------------------------------------------------------
>
> > Free Software Download: Index, Search&  Analyze Logs and other IT data in
>
> > Real-Time with Splunk. Collect, index and harness all the fast moving IT
> data
> > generated by your applications, servers and devices whether physical,
> virtual
> > or in the cloud. Deliver compliance at lower cost and gain new business
> > insights. http://p.sf.net/sfu/splunk-dev2dev
> > _______________________________________________
> > qooxdoo-devel mailing list
> > [hidden 
> > email]<http://user/SendEmail.jtp?type=node&node=6085549&i=0&by-user=t>
> > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> >
> >
>
> ------------------------------------------------------------------------------
>
> Free Software Download: Index, Search & Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT
> data
> generated by your applications, servers and devices whether physical,
> virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]<http://user/SendEmail.jtp?type=node&node=6085549&i=1&by-user=t>
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://qooxdoo.678.n2.nabble.com/Cross-Domain-Parts-in-Qooxdoo-application-tp6084959p6085549.html
>  To unsubscribe from Cross-Domain Parts in Qooxdoo application, click 
> here<http://qooxdoo.678.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=6084959&code=bWxlbWF5QGlub2N5YmUuY2F8NjA4NDk1OXwxMzAzODg2MjY=>.
>
>


--
View this message in context: 
http://qooxdoo.678.n2.nabble.com/Cross-Domain-Parts-in-Qooxdoo-application-tp6084959p6085735.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to