No argument.

I'd like to think I was clearly expressing personal preference, not dictating other people's actions.

On 1/4/2012 5:44 PM, Jonathan Campos wrote:
Just to be fair. If they want to make another set of Components that is completely their choice. Sorry Jeff for responding with this to your post, just see lots of people talking about what should and should not be done. We all have to remember that some people's passions may be in a different direction then what we believe and that is perfectly okay.

I can't say that everyone's passion will be accepted into the trunk, but you are more than happy to work on it.

On Wed, Jan 4, 2012 at 4:37 PM, Jeffry Houser <jef...@dot-com-it.com <mailto:jef...@dot-com-it.com>> wrote:


     Has open Laszlo stayed up to date?  I hadn't heard of it in many
    years.

     I--personally--would  rather see efforts put towards optimizing
    existing Flex Components or the component framework; not on
    creating a 3rd component framework within Flex.


    On 1/4/2012 5:10 PM, Raju Bitter wrote:

        It would make sense to build a light-weight component set for
        Flex,
        which could be used for rendering Flex apps in HTML5 later on. The
        approach could be based on the UI/component implementation
        OpenLaszlo
        has (which provides cross-compilation features for
        ActionScript and
        JavaScript, check this demo):
        http://vimeo.com/32853986
        HTML5 version
        http://www.openlaszlo.org/lps_demos/demos/lzpix/app.lzx?lzr=dhtml
        SWF version
        http://www.openlaszlo.org/lps_demos/demos/lzpix/app.lzx?lzr=swf10

        2012/1/4 Fréderic Cox<frede...@exuvis.com
        <mailto:frede...@exuvis.com>>:

            And it's not only on mobile, on desktop (mostly Mac's)
            this is a problem
            also. I'm talking about big enterprise applications and
            websites here
            (like a CMS with graphical skin applied, nothing really in
            standard Flex
            skin)

            On 04/01/12 22:49, "Arthur
            Lockman"<arthurlock...@ajobi.net
            <mailto:arthurlock...@ajobi.net>>  wrote:

                +1 on this. Performance definitely needs to be
                addressed on Flex. I've
                noticed that on newer devices, it works fine. But on
                the slightly older
                ones, performance is a huge issue. Hopefully we can
                get in there and
                clean it up so it performs better.


                --
                Arthur Lockman | Senior Developer @ Vivace
                vi.vace.me <http://vi.vace.me>
                Twitter: @arthurlockman
                a.rthr.me <http://a.rthr.me>


                On Wednesday, January 4, 2012 at 4:28 PM, Fréderic Cox
                wrote:

                    I've worked on Flex applications for the past 4-5
                    years and see a lot
                    of developers picking it up since it is easy to
                    create rich
                    applications. However performance is often an issue.

                    I mostly see it when using a lot of styles (or one
                    large CSS file) and
                    skinned components (It is even worse with Flex 4
                    then it was with Flex
                    3). When a Flex application gets really large the
                    UI is blocked because
                    there is too much actionscript code needed to get
                    things running. (with
                    this I mean the processing time is acceptable but
                    UI is blocked so the
                    perception is that things are slow)

                    Therefore I'd like to vote on improving the
                    performance of the Flex
                    framework where possible so new and existing
                    applications can benefit.
                    Flex 4 with spark is great but comes with some
                    performance drawbacks, I
                    hope we can improve on this significantly.

                    I'm speaking on behalf of the experience and
                    perception in the company
                    I work for, I'm curious to see if this is also a
                    problem for the rest of
                    you.

                    I'm not the expert here but I'd like to get
                    involved and learn so I can
                    eventually help to fix issues but I believe
                    UIComponent had some
                    overhead and this together with the StyleManager
                    can cause performance
                    drawbacks in large applications





-- Jeffry Houser
    Technical Entrepreneur
    203-379-0773 <tel:203-379-0773>
    --
    http://www.flextras.com?c=104
    UI Flex Components: Tested! Supported! Ready!
    --
    http://www.theflexshow.com
    http://www.jeffryhouser.com
    http://www.asktheflexpert.com
    --
    Part of the DotComIt Brain Trust




--
Jonathan Campos
Dallas Flex User Group Manager
http://www.d-flex.org/
blog: http://www.unitedmindset.com/jonbcampos
twitter: http://www.twitter.com/jonbcampos


--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust

Reply via email to