Re: [flexcoders] Re: Posting patched versions of framework code to this list?

Sun, 17 Sep 2006 01:50:45 -0700

While open source it could be a solution, I think is not strictly necesary. The main point here is that Adobe should provide as soon as posible a way to expose flex framework revisions.
 
If they fail in provide quick solutions to the actual framework problems they could make people entering flex and flash world (i.e, coming from java) stop working with this technology due to some strange or weird bugs found.
 
May of that bugs are very anoying and were found one or two months ago. I think it's time for Adobe to start giving some feedback to the community about some updates. I think this is more important that start aasking about new additions to the framework in the future. Most of use are satisfied with the actual framework but would like to see it working 100% without any problem that make us rethink the way we plan a view or a functionality just because there's a bug that doesn't allow us to create that part in the way we were thinking. Add new features is great and is great that Adobe start thinking in future enhancements, but please! is more important provide a way for people to get updates, and even provide possible solutions to framework bugs and problems.
 
Some months ago we talked about SVN, or other ways to accomplish this. I think now is not a problem the "how"...now is important the "when". Maybe as Adobe did providing feedback support about linux flash player (knowing the importance of such release for the future of flash platform in the enterprise), this should be the same, and provide info( i.e, in the flex team blog) about plans regarding this issue.
 


 
On 9/17/06, Renaun Erickson <[EMAIL PROTECTED]> wrote:

Anatole I see your point about Adobe and open source. I would prefer
it closed with the ability to modified more than making it fully open
source. There are good and bad reasons for both ways.

In the components I have created quite often I learn and take bits of
pieces from the source of the Flex framework and have had great
success (even with private variable quirks).

I think what we have now is a big step to what we had before and will
get more and more open as time goes on.

Renaun

--- In flexcoders@yahoogroups.com, "Anatole Tartakovsky"


<[EMAIL PROTECTED]> wrote:
>
> Renaun,
>
> I don't think Louis changes can be placed in extension layer as they
would
> involve access to private methods and variables. I think his
question is if
> Adobe foresee making Flex framework open source project administered by
> Adobe and is looking for repository/approval process.
> I also believe ( from reading the license in the past - can be wrong
- did
> not talk to lawyers) that working in mx. packages is not allowed -
so in
> the past any changes of that sort required us to recreate
significant part
> of Flex stack.
>
> Addressing this issue via open source project would greatly simplify
life of
> the people doing routine changes to framework and needing those
changes to
> be present.
>
> The only other alternative I can see is to replicating Flex objects
in open
> source project and making sure they are synchronized with the
releases of
> Flex. However, it might lead to significant market fragmentation as
well as
> break of existing libraries that are working within mx packages like
> Mercury.
>
> I would really like to hear Adobe position on Louis offer.
>
> Thank you,
> Anatole Tartakovsky
> http://www.faratasystems.com
>
>
>
>
> On 9/16/06, Renaun Erickson <[EMAIL PROTECTED]> wrote:
> >
> > You can always extend the class, make your own component and
post it
> > on Flex Exchange on Adobe.com < http://adobe.com/>.
> >
> > Renaun
> >
> >
> > --- In flexcoders@yahoogroups.com <flexcoders%40yahoogroups.com>,

"Louis
> > Ryan" <louiscryan@> wrote:
> > >
> > > I have modified the DataGrid class to allow columns to be locked on
> > > the right. I posted this as an enhancement request to Adobe but its
> > > not so easy to include alot of text in their suggestion area so I
> > > didnt include the sample code I had for this.
> > >
> > > Is it OK to post modified versions of the Flex framework code
here? If
> > > not is there a better way to send suggested code/patches to
Adobe for
> > > review?
> > >
> > > Thanks
> > >
> > > Louis Ryan
> > >
> >
> >
> >
>




--
::| Carlos Rovira
::| http://www.carlosrovira.com
::| http://www.madeinflex.com __._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Software development tool Software development Software development services
Home design software Software development company

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe

__,_._,___

Reply via email to