Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <20120118065333.19422qnvek2l1cjh@www.teotigraphix.com>
Date: Wed, 18 Jan 2012 06:53:33 -0500
From: Michael Schmalle <mike@teotigraphix.com>
To: flex-dev@incubator.apache.org
Subject: Re: OSGi bundle Plugin registry system
References: <20120118063537.159124i231jed0nd@www.teotigraphix.com>
 <CAAgciqr7L77hpCOpozh9Zz-ktoZgWPCcGZQk+oScABYxZnvGZQ@mail.gmail.com>
In-Reply-To: 
 <CAAgciqr7L77hpCOpozh9Zz-ktoZgWPCcGZQk+oScABYxZnvGZQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=ISO-8859-1;
 DelSp="Yes";
 format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.3.9)

Outside obviously. :)

I think I can see the future and Apache Flex needs multiple sub trunks  
IE sub projects.

If you think about the amount of wasted momentum Flex has had over the  
last 4 years with code here, there and everywhere. Apache Flex needs  
to say our core value is consolidating code that can be used by many  
and we support that. GIT is fine for independent projects but I think  
if there is enough interest in the community for something that will  
enhance the flex SDK we need to figure out a way to consolidate these  
projects under our project.

Doing this will only exponentially increase the traction of all our  
efforts. If this doesn't happen, Apache Flex than does what Adobe did,  
community last SDK first.

Were not talking about an application framework here, its a runtime  
component framework that application frameworks can expose and use.

Mike

PS I'm happy just using this stuff in my projects as well, I'm just  
interested in the communities definitions right now.

By no means is the way I did it the "right way" but, I do know the  
power of this pattern and it hasn't been exposed in Flex which is a  
shame.


Quoting Roland Zwaga <roland@stackandheap.com>:

> Hey there,
>
> I think such as system could be really interesting, because the development
> patterns it exposes are pretty widely used. At the same time,
> I'm not sure if it should be part of the SDK, or perhaps rather more as an
> extension of the SDK.
> It'll be a good discussion to determine what exactly people see as the
> scope for the SDK, what type of functionality belongs in it, and what not.
> An OSGi type of system as you describe is a really good example of such
> functionality. In or out?
>
> thoughts?
>
> Roland
>
> On 18 January 2012 12:35, Michael Schmalle <mike@teotigraphix.com> wrote:
>
>> 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/<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<https://github.com/teotigraphix/sx-plugins>
>>
>> The ui framework;
>>
>> https://github.com/**teotigraphix/sx-ui<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
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> regards,
> Roland
>
> --
> Roland Zwaga
> Senior Consultant | Stack & Heap BVBA
>
> +32 (0)486 16 12 62 | roland@stackandheap.com | http://www.stackandheap.com
>