Loading ...
Sorry, an error occurred while loading the content.

YUI Library: Monthly Roadmap Update

Expand Messages
  • Eric Miraglia
    Monthly YUI Roadmap Update — October 2006: The YUI Library currently stands at version 0.11.4. When I last published a roadmap update two months ago, we were
    Message 1 of 19 , Oct 10, 2006
    View Source
    • 0 Attachment
      Monthly YUI Roadmap Update — October 2006:

      The YUI Library currently stands at version 0.11.4.

      When I last published a roadmap update two months ago, we were projecting an October release for 0.12; that release has been pushed back to the first half of November.  The best of our current thinking with respect to 0.12 is detailed below; in summary, it's expected to feature the debut of the YUI Tab Control, enhancements to the Yahoo Object (methods supporting object extension and augmentation), major improvements to the Calendar Control API, and assorted bug fixes.  A YUI Button Control is well along in its development cycle; we expect it to be a part of 0.13, projected for December.  

      Beyond 0.13, taking us into 2007, we are focusing on three major areas:

      1.  Additional core components.  I mentioned in August that we're working on a YUI Table Control/DataGrid; that is one of several core components we'd like to add to YUI.  The Table Control should be available by early next year and additional components will follow.

      2.  Improved interface consistency.  Currently we support several different patterns for configuring and interacting with our controls.  In the next phase of development, we are looking to improve the quality and consistency of YUI interfaces across the board.

      3.  Improved documentation.  

      + + + + + + + + 

      Next two release windows for YUI Library Beta:
      1.  Early November (v. 0.12) — Tab Control, Yahoo Object enhancements (extension and augmentation of objects), Event Utility enhancements, significant Calendar Control API improvements, bug fixes.
      2.  December (v. 0.13) — Button Control, bug fixes.

      Projects in Development:
      1.  Tab Control
      The Tab Control will provide support for a variety of tabbed-module implementations.
      Projected Release: 0.12
      Confidence: High

      2.  Button Control 
      The Button Control will enable the deployment buttons with (1) diverse visual treatments (e.g., with or without images); (2) configurable actions (clicking can be tied to form submission or other custom functions); (3) integrated menus and submenus; .  
      Projected Release: 0.13
      Confidence: High

      3.  History Utility
      Managing the browser's history stack is critical to the creation of applications that are intuitive, usable, and sharable.  Currently, management of the History stack in applications based on YUI requires you to roll your own solution.  The History Utility will help facilitate this process by providing a simple interface for adding application states to the History stack during asynchronous interaction flows.
      Projected Release: After 0.13
      Confidence: We continue to investigate actively the best approach to this problem across the A-Grade.  We are pushing this back beyond 0.13 at this point based on what we've learned so far, but we remain interested in creating a reliable cross-browser solution for this problem.

      4.  Table/DataGrid Control
      Dynamic tabular data controls are a common interactive treatment for data-intensive interfaces, going beyond simple table functionality to add features like dynamic sorting, editing-in-place, resizable columns, and more.
      Projected Release: after 0.13
      Confidence: Medium

      + + + + + + + +

      Note:  This roadmap projects our plans over the next quarter or so; in so doing, it makes assumptions about conditions that are naturally dynamic.  Some of the projects detailed here may be delivered earlier or later than we are currently expecting; some may not be delivered at all.  Other projects not listed here may be escalated during this period.  Use this document only as a rough guide; never rely on unreleased code listed here for any crucial needs.

      Regards,
      Eric

      ______________________________________________
      Eric Miraglia
      Yahoo! Presentation Platform Engineering

    • Nige White
      Eric, I assume you have been keeping up with Jack s developments in these areas. Jack s Grid component is extremely well designed, flexible and easy to use.
      Message 2 of 19 , Oct 11, 2006
      View Source
      • 0 Attachment
        Eric, I assume you have been keeping up with Jack's developments in
        these areas. Jack's Grid component is extremely well designed, flexible
        and easy to use.

        Will the YUI Grid be comparable or based on Jack's implementation? There
        are already people using it, and it would be a shame to see a
        "competition". While I would like to be fully YUI-standard compliant (to
        place a lot of maintenance onus on the larger resources of Yahoo - I'm
        the only UI dev guy here), I don't want to move away from the concepts.

        What I particularly like is the MVC separation. This is something that
        really facilitates flexible supply of data and metadata to the grid.

        I think the YUI TreeView control is due a radical overhaul to move to an
        MVC architecture too.

        I also like Jack's "Element" abstraction of DOM elements into a powerful
        object. His additions to the Function prototype are useful too.

        Nige

        Eric Miraglia wrote:

        > *Monthly YUI Roadmap Update — October 2006:*
        >
        > The YUI Library currently stands at version 0.11.4.
        >
        > When I last published a roadmap update two months ago, we were
        > projecting an October release for 0.12; that release has been pushed
        > back to the first half of November. The best of our current thinking
        > with respect to 0.12 is detailed below; in summary, it's expected to
        > feature the debut of the YUI Tab Control, enhancements to the Yahoo
        > Object (methods supporting object extension and augmentation), major
        > improvements to the Calendar Control API, and assorted bug fixes. A
        > YUI Button Control is well along in its development cycle; we expect
        > it to be a part of 0.13, projected for December.
        >
        > Beyond 0.13, taking us into 2007, we are focusing on three major areas:
        >
        > 1. *Additional core components.* I mentioned in August that we're
        > working on a YUI Table Control/DataGrid; that is one of several core
        > components we'd like to add to YUI. The Table Control should be
        > available by early next year and additional components will follow.
        >
        > 2. *Improved interface consistency.* Currently we support several
        > different patterns for configuring and interacting with our controls.
        > In the next phase of development, we are looking to improve the
        > quality and consistency of YUI interfaces across the board.
        >
        > 3. *Improved documentation.*
        >
        > + + + + + + + +
        >
        > /Next two release windows for YUI Library Beta:/
        > 1. * Early November* (v. 0.12) — Tab Control, Yahoo Object
        > enhancements (extension and augmentation of objects), Event Utility
        > enhancements, significant Calendar Control API improvements, bug fixes.
        > 2. *December* (v. 0.13) — Button Control, bug fixes.
        >
        > /Projects in Development:/
        > 1. Tab Control
        > The Tab Control will provide support for a variety of tabbed-module
        > implementations.
        > *Projected Release: *0.12
        > *Confidence: *High
        >
        > 2. Button Control
        > The Button Control will enable the deployment buttons with (1) diverse
        > visual treatments (e.g., with or without images); (2) configurable
        > actions (clicking can be tied to form submission or other custom
        > functions); (3) integrated menus and submenus; .
        > *Projected Release:* 0.13
        > *Confidence:* High
        >
        > 3. History Utility
        > Managing the browser's history stack is critical to the creation of
        > applications that are intuitive, usable, and sharable. Currently,
        > management of the History stack in applications based on YUI requires
        > you to roll your own solution. The History Utility will help
        > facilitate this process by providing a simple interface for adding
        > application states to the History stack during asynchronous
        > interaction flows.
        > *Projected Release:* After 0.13
        > *Confidence:* We continue to investigate actively the best approach to
        > this problem across the A-Grade. We are pushing this back beyond 0.13
        > at this point based on what we've learned so far, but we remain
        > interested in creating a reliable cross-browser solution for this problem.
        >
        > 4. Table/DataGrid Control
        > Dynamic tabular data controls are a common interactive treatment for
        > data-intensive interfaces, going beyond simple table functionality to
        > add features like dynamic sorting, editing-in-place, resizable
        > columns, and more.
        > *Projected Release:* after 0.13
        > *Confidence: *Medium
        >
        > + + + + + + + +
        >
        > *Note:* This roadmap projects our plans over the next quarter or so;
        > in so doing, it makes assumptions about conditions that are naturally
        > dynamic. Some of the projects detailed here may be delivered earlier
        > or later than we are currently expecting; some may not be delivered at
        > all. Other projects not listed here may be escalated during this
        > period. Use this document only as a rough guide; never rely on
        > unreleased code listed here for any crucial needs.
        >
        > Regards,
        > Eric
        >
        > *______________________________________________*
        > *Eric Miraglia*
        > Yahoo! Presentation Platform Engineering
        >
        >
        > _____________________________________________________________________
        > This message has been checked for all known viruses. Virus scanning
        > powered by Messagelabs http://www.messagelabs.com For more information
        > e-mail : hostmaster@...



        _____________________________________________________________________
        This message has been checked for all known viruses. Virus scanning
        powered by Messagelabs http://www.messagelabs.com For more information
        e-mail : hostmaster@...
      • Nige White
        ... Ah, erm, I ve just visited yuiblog.com! _____________________________________________________________________ This message has been checked for all known
        Message 3 of 19 , Oct 11, 2006
        View Source
        • 0 Attachment
          Nige White wrote:

          >Eric, I assume you have been keeping up with Jack's developments...
          >
          >
          Ah, erm, I've just visited yuiblog.com!

          _____________________________________________________________________
          This message has been checked for all known viruses. Virus scanning
          powered by Messagelabs http://www.messagelabs.com For more information
          e-mail : hostmaster@...
        • Ivan Lazarte
          Maybe Jack should just be added to the dev team :) I d rather have the source of YAHOO related code consolidated so I don t get competing functionality
          Message 4 of 19 , Oct 11, 2006
          View Source
          • 0 Attachment
            Maybe Jack should just be added to the dev team :) I'd rather have
            the source of YAHOO related code consolidated so I don't get
            competing functionality implemented in both libraries... It would be
            the inevitable return of the fork problem.

            --- In ydn-javascript@yahoogroups.com, Nige White <nigelw@...> wrote:
            >
            > Eric, I assume you have been keeping up with Jack's developments
            in
            > these areas. Jack's Grid component is extremely well designed,
            flexible
            > and easy to use.
            >
            > Will the YUI Grid be comparable or based on Jack's implementation?
            There
            > are already people using it, and it would be a shame to see a
            > "competition". While I would like to be fully YUI-standard
            compliant (to
            > place a lot of maintenance onus on the larger resources of Yahoo -
            I'm
            > the only UI dev guy here), I don't want to move away from the
            concepts.
            >
            > What I particularly like is the MVC separation. This is something
            that
            > really facilitates flexible supply of data and metadata to the
            grid.
            >
            > I think the YUI TreeView control is due a radical overhaul to move
            to an
            > MVC architecture too.
            >
            > I also like Jack's "Element" abstraction of DOM elements into a
            powerful
            > object. His additions to the Function prototype are useful too.
            >
            > Nige
            >
            > Eric Miraglia wrote:
            >
            > > *Monthly YUI Roadmap Update — October 2006:*
            > >
            > > The YUI Library currently stands at version 0.11.4.
            > >
            > > When I last published a roadmap update two months ago, we were
            > > projecting an October release for 0.12; that release has been
            pushed
            > > back to the first half of November. The best of our current
            thinking
            > > with respect to 0.12 is detailed below; in summary, it's
            expected to
            > > feature the debut of the YUI Tab Control, enhancements to the
            Yahoo
            > > Object (methods supporting object extension and augmentation),
            major
            > > improvements to the Calendar Control API, and assorted bug
            fixes. A
            > > YUI Button Control is well along in its development cycle; we
            expect
            > > it to be a part of 0.13, projected for December.
            > >
            > > Beyond 0.13, taking us into 2007, we are focusing on three major
            areas:
            > >
            > > 1. *Additional core components.* I mentioned in August that
            we're
            > > working on a YUI Table Control/DataGrid; that is one of several
            core
            > > components we'd like to add to YUI. The Table Control should be
            > > available by early next year and additional components will
            follow.
            > >
            > > 2. *Improved interface consistency.* Currently we support
            several
            > > different patterns for configuring and interacting with our
            controls.
            > > In the next phase of development, we are looking to improve the
            > > quality and consistency of YUI interfaces across the board.
            > >
            > > 3. *Improved documentation.*
            > >
            > > + + + + + + + +
            > >
            > > /Next two release windows for YUI Library Beta:/
            > > 1. * Early November* (v. 0.12) — Tab Control, Yahoo Object
            > > enhancements (extension and augmentation of objects), Event
            Utility
            > > enhancements, significant Calendar Control API improvements, bug
            fixes.
            > > 2. *December* (v. 0.13) — Button Control, bug fixes.
            > >
            > > /Projects in Development:/
            > > 1. Tab Control
            > > The Tab Control will provide support for a variety of tabbed-
            module
            > > implementations.
            > > *Projected Release: *0.12
            > > *Confidence: *High
            > >
            > > 2. Button Control
            > > The Button Control will enable the deployment buttons with (1)
            diverse
            > > visual treatments (e.g., with or without images); (2)
            configurable
            > > actions (clicking can be tied to form submission or other custom
            > > functions); (3) integrated menus and submenus; .
            > > *Projected Release:* 0.13
            > > *Confidence:* High
            > >
            > > 3. History Utility
            > > Managing the browser's history stack is critical to the creation
            of
            > > applications that are intuitive, usable, and sharable.
            Currently,
            > > management of the History stack in applications based on YUI
            requires
            > > you to roll your own solution. The History Utility will help
            > > facilitate this process by providing a simple interface for
            adding
            > > application states to the History stack during asynchronous
            > > interaction flows.
            > > *Projected Release:* After 0.13
            > > *Confidence:* We continue to investigate actively the best
            approach to
            > > this problem across the A-Grade. We are pushing this back
            beyond 0.13
            > > at this point based on what we've learned so far, but we remain
            > > interested in creating a reliable cross-browser solution for
            this problem.
            > >
            > > 4. Table/DataGrid Control
            > > Dynamic tabular data controls are a common interactive treatment
            for
            > > data-intensive interfaces, going beyond simple table
            functionality to
            > > add features like dynamic sorting, editing-in-place, resizable
            > > columns, and more.
            > > *Projected Release:* after 0.13
            > > *Confidence: *Medium
            > >
            > > + + + + + + + +
            > >
            > > *Note:* This roadmap projects our plans over the next quarter
            or so;
            > > in so doing, it makes assumptions about conditions that are
            naturally
            > > dynamic. Some of the projects detailed here may be delivered
            earlier
            > > or later than we are currently expecting; some may not be
            delivered at
            > > all. Other projects not listed here may be escalated during
            this
            > > period. Use this document only as a rough guide; never rely on
            > > unreleased code listed here for any crucial needs.
            > >
            > > Regards,
            > > Eric
            > >
            > > *______________________________________________*
            > > *Eric Miraglia*
            > > Yahoo! Presentation Platform Engineering
            > >
            > >
            > >
            _____________________________________________________________________
            > > This message has been checked for all known viruses. Virus
            scanning
            > > powered by Messagelabs http://www.messagelabs.com For more
            information
            > > e-mail : hostmaster@...
            >
            >
            >
            >
            _____________________________________________________________________
            > This message has been checked for all known viruses. Virus scanning
            > powered by Messagelabs http://www.messagelabs.com For more
            information
            > e-mail : hostmaster@...
            >
          • Donald J. Sipe III
            I think the separation of Jack s code and Yahoo s code is important. To me, I feel more comfortable incorporating Yahoo s tried and tested code into
            Message 5 of 19 , Oct 11, 2006
            View Source
            • 0 Attachment
              I think the separation of Jack's code and Yahoo's code is important.  To me, I feel more comfortable incorporating Yahoo's tried and tested code into mission-critical projects.  Jack has done some amazing and wonderful stuff that is also well-tested and documented, but putting the Yahoo seal on it gives it all a greater sense of legitimacy.  This is especially helpful when you start incorporating YUI into the play-it-safe corporate environment, which still regards AJAX with standoffish skepticism.

              I think Jack is making great strides in pushing the envelope and advancing YUI to its full potential, but adoption and stability are critical.  People who might see building UIs in JavaScript as a liability want assurances it will work and that they can trust it. Telling them it's the same library that Yahoo uses on its own sites goes a long way toward soothing their nerves.

            • Matt Warden
              ... These are very good points. I am currently trying to get buy-in to use YUI, and it is clear to me that it would be nearly impossible to do if not for the
              Message 6 of 19 , Oct 11, 2006
              View Source
              • 0 Attachment
                On 10/11/06, Donald J. Sipe III <donald.sipe@...> wrote:
                >
                > I think the separation of Jack's code and Yahoo's code is important. To me, I feel more comfortable incorporating Yahoo's tried and tested code into mission-critical projects. Jack has done some amazing and wonderful stuff that is also well-tested and documented, but putting the Yahoo seal on it gives it all a greater sense of legitimacy. This is especially helpful when you start incorporating YUI into the play-it-safe corporate environment, which still regards AJAX with standoffish skepticism.
                >
                > I think Jack is making great strides in pushing the envelope and advancing YUI to its full potential, but adoption and stability are critical. People who might see building UIs in JavaScript as a liability want assurances it will work and that they can trust it. Telling them it's the same library that Yahoo uses on its own sites goes a long way toward soothing their nerves.
                >
                >


                These are very good points. I am currently trying to get buy-in to use
                YUI, and it is clear to me that it would be nearly impossible to do if
                not for the Yahoo's backing of the project. Given Yahoo's reluctance
                to accept direct code contributions, I think they are probably aware
                and working to develop a contribution model that respects this.


                --
                Matt Warden
                Cleveland, OH, USA
                http://mattwarden.com


                This email proudly and graciously contributes to entropy.
              • Jack Slocum
                ... I think that depends on how you look at it. Imagine if the code was part of the regular distribution and had the same resources and cycles for testing as
                Message 7 of 19 , Oct 11, 2006
                View Source
                • 0 Attachment
                  > I think the separation of Jack's code and Yahoo's code is important.

                  I think that depends on how you look at it. Imagine if the code was part of the regular distribution and had the same resources and cycles for testing as the rest of the YUI code. That certainly couldn't be a negative thing. I not rallying for them to be joined, I'm just being hypothetical.

                  > To me, I feel more comfortable incorporating Yahoo's tried and tested code into
                  > mission-critical projects.

                  I would too. This is completely understandable.

                  > Jack has done some amazing and wonderful stuff
                  > that is also well-tested and documented...


                  Thank you.

                  > but putting the Yahoo seal on it
                  > gives it all a greater sense of legitimacy.  This is especially helpful when
                  > you start incorporating YUI into the play-it-safe corporate environment,
                  > which still regards AJAX with standoffish skepticism.
                  > I think Jack is making great strides in pushing the envelope and advancing
                  > YUI to its full potential, but adoption and stability are critical. People
                  > who might see building UIs in JavaScript as a liability want assurances it
                  > will work and that they can trust it. Telling them it's the same library
                  > that Yahoo uses on its own sites goes a long way toward soothing their
                  > nerves.
                  >

                  I understand this as well. A lot of my development experience is in the manufacturing industry. They are as resistent to change as anyone. The Yahoo name has certainly helped me in that aspect as well.

                  The reason my project started was because developing a large application with YUI only (no prototype or other libraries) requires a bit of "reinventing the wheel"  and "long hand" coding. The YUI utilities give you the perfect tools to do your JavaScript development independent of the browser, but for most application development it's nice to start with something more than that. This additional "plumbing" code has to be written by someone (unless you plan of repeating code over and over). IMO, it's better to use an extension that is tested by thousands of  developers than a homegrown solution especially if that code is also free.

                  The Element, UpdateManager, and new DomHelper classes extend on that YUI foundation and provide a developer a time-saving API and some features that currently no other library provides (like automatic box model corrections, insertion optimization, auto-animations, etc). All the code is built on the solid foundation of YUI. I have learned to rely on these tools in my development and I can't tell you how many hours they save me. I make the code available on my site not to compete with Yahoo, but simply to follow Yahoo's example and share my work with others.

                  Each project has it's own needs. For many projects the yui-ext code is overkill.  But that doesn't mean you should rule it out simply because it was written by me and isn't official YUI code.

                Your message has been successfully submitted and would be delivered to recipients shortly.