incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Avinash Narayanan <avinasha...@gmail.com>
Subject Re: OSGi bundle Plugin registry system
Date Wed, 18 Jan 2012 11:52:16 GMT
Hello Michael,

Like Cosma mentioned, I found the same issues when it came to using
modules. especially when used with some sort of IoC framework (I found it
with parseley 2.3) so any move in making modularization more flexible would
be awesome!

Thanks
Avinash Y


On Wed, Jan 18, 2012 at 5:19 PM, Cosma Colanicchia <cosmacol@gmail.com>wrote:

> Hello Michael,
>
> thanks, this is very interesting - I am probably the user you were
> referring to :)
>
> I don't have the time to look into it now, but I'd like to know if the
> base (plugin) framework can be used without the UI part, and how did
> you manage runtime loading and unloading of plugins, and I will look
> at your code as soon as I can.
>
> One of my original issues with modular client applications was related
> to remote aliases: currently, the built-in flash
> serialization-deserialization system for objects exchanged with a
> remote service (e.g. a Java/Spring service exposed by BlazeDS) are
> based on a registry that is held by the SecurityDomain. This create a
> lot of problems on modules unloading, conflicting versions of the same
> class, and so on..
>
>
> Cosma
>
> 2012/1/18 Michael Schmalle <mike@teotigraphix.com>:
> > Hi,
> >
> > I noticed in a thread a member talking about modules and loading at
> runtime,
> > using the term bundles. Anyone familiar with that term might think OSGi.
> >
> > He listed the link below and said wouldn't it be great if Adobe open
> sourced
> > this and donated it to Apache Flex.
> >
> >
> http://blogs.adobe.com/gravity/2011/09/09/hellogravity-sample-application/
> >
> > Well, I have been working with a plugin registry system on my own for
> about
> > 3 years now, that uses IoC, and extension registry like Eclipse with
> > extension points and extensions. The asdoc editor was created with this
> very
> > same framework.
> >
> > Currently I'm using SpringAS for the IoC but if there was interest, we
> could
> > abstract out the IoC and leave it application dependent on the system the
> > app is using at the time.
> >
> > I would really love to know if there was an interest in this type of
> project
> > because I have so much time into one already. I have experimented as well
> > with loading modules as bundles and it worked great using the Plugin
> > paradigm. New extensions were loaded at runtime which would say allow new
> > views and editors, commands etc.
> >
> > Truly if there was an area I would love to expose with Apache Flex is
> > showing it's potential in creating this dynamic runtime component system.
> >
> > The base framework is located;
> >
> > https://github.com/teotigraphix/sx-plugins
> >
> > The ui framework;
> >
> > https://github.com/teotigraphix/sx-ui
> >
> > -> Menus, Toolbars, Dialogs, Windows
> >
> > Note; I have been updating these in the last month to abstract AIR deps
> out
> > of the ui framework. The base framework still uses Spring 1.1. But as I
> > said, if there was interest, we would abstract this to an IoC interface.
> >
> > Let me know, if now, I will still keep developing this for my won
> projects.
> >
> > Also, I now have it that you can run an app in the browser and desktop
> using
> > the same code, creates different type shells based on the environment.
> >
> > Thanks,
> > Mike
> >
> >
> >
> >
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message