Planning Glow 2 - we want your feedback!
Now we've got 1.7 out the door, our minds are turning towards planning for version 2, our next major release which will be out in the new year. We're planning a significant overhaul, and as the major version increment indicates this will include a fundamental rewrite of large portions of the library.
Now is also a great time for users and contributors to get involved. Please tell us what you've liked and disliked about version 1, and what features you'd most like to see in version 2.
We have produced a set of four themes that we'd like to explore in Glow 2. These might get you thinking about what your perfect desert island library would contain, or maybe you think we've missed something vital?
- Accessibility - provide a step-change in accessible and usable widgets
- Performance - reduce load and execution times to the bare minimum
- Design - build widgets that look fantastic alone or in combination
- Community - open up the project and help the community thrive
We really want to hear what you think. If you'd like to talk to us about your ideas then join us on our mailing list, chat with us on IRC or you can send a message on twitter or by adding the hastag #bbcglow2 - we'll do our best to respond to everyone who sends us a suggestion.
Comment number 1.
At 26th Oct 2009, Simon Cross wrote:Yay! Glow 2.0. Would really like a plugin directory so people can build plugins and upload links and docs to them.
Then potentially some of the plugins could get rolled into the core library...
Complain about this comment (Comment number 1)
Comment number 2.
At 30th Oct 2009, Mo McRoberts wrote:One I came across this morning with 1.7: I’d love to see improved support for fluid/elastic layouts. For example, if you create a carousel within a fluid layout and resize the browser window, the carousel remains fixed to its original size.
(I’m possibly doing something wrong, mind)
Complain about this comment (Comment number 2)
Comment number 3.
At 2nd Nov 2009, Mo McRoberts wrote:If anybody's curious, incidentally, the carousel _does_ work with a fluid layout, if you use !important rules to override the inline width set by the JS to be 100% on .glow170-carousel and .carousel-window, then use absolute positioning on previous/next buttons (in my case, they overlay the content, though you’d need to come up with something—margin on the .carousel-window?—to do otherwise).
I’ve not tested this cross-browser yet, so IE 6 probably fails miserably with it ;)
Complain about this comment (Comment number 3)
Comment number 4.
At 2nd Nov 2009, Frances Berriman wrote:@Simon - we're certainly toying with the idea of allowing and actively supporting plug-ins. We'll certainly be discussing this on the users' mailing list. Obviously, we have the quality-control and support overhead worries that come with such a thing. We have a generally positive feeling about the idea though.
@nevali - All of our widgets will probably be getting somewhat of a UI and aesthetic freshen, so we'll be sure to check that they can scale suitably and continue to make it relatively easy for people to re-skin and make elastic/fluid, as you describe.
Complain about this comment (Comment number 4)