--- Quote from: feline on September 23, 2011, 12:48:32 PM ---Well Norv ... Great plan ... but how long is the time to see a final 2.1 or a 3.0?For the 2.0 the team needs more then 4 years ... and I think the "one man show" need longer to 3.0 ...

As long as the development team is not changed significantly, and increased with experienced programmers, rather drift a meteor the earth, as it will give an SMF 3.0 ...

--- End quote ---

Development of 3.0 is not a one man team, don't worry about that. The people you see in the development team on SMF are not the only people working on 3.0 :)

GravuTrad:

--- Quote from: Fustrate on September 23, 2011, 05:08:43 PM ------ Quote from: feline on September 23, 2011, 12:48:32 PM ---Well Norv ... Great plan ... but how long is the time to see a final 2.1 or a 3.0?For the 2.0 the team needs more then 4 years ... and I think the "one man show" need longer to 3.0 ...

As long as the development team is not changed significantly, and increased with experienced programmers, rather drift a meteor the earth, as it will give an SMF 3.0 ...

--- End quote ---

Development of 3.0 is not a one man team, don't worry about that. The people you see in the development team on SMF are not the only people working on 3.0 :)

--- End quote ---

Exactly.

Burridge:

--- Quote from: AngelinaBelle on September 20, 2011, 08:35:57 PM ---It will be exciting to see new versions coming out routinely, with small bundles of features and other refinements.Maybe future versions will also DROP things we don't need any more!

--- End quote ---Hell yeah. That would be awesome.

Hopefully with everything now in place (or so it seems) we'll see more frequent updates, and not have to wait like 5(?) years for a new release x)

emilykrys:
Can't wait to see how this goes :)

Antechinus:
Just noting that as of last night Australian time, our trunk is now running jQuery as the official default javascript library.

This gives us a lot of scope for improvements in functionality and accessibility with a minimum of extra code. :)

The list of what will be included is not set in stone at the moment, but we will be tending towards things we regard as truly useful rather than just frills for the sake of frills.

At the moment only the drop menu system has been done, but more things will follow. To quote from the team's dev board:

--- Quote from: Antechinus on October 20, 2011, 05:47:52 AM ---Update (for anyone who give a rat's): These menus now work with the latest jQuery.

After doing a bit of fiddling around I have also managed to get full keyboard navigation (via tab key) of the drop menus without requiring javascript, just in case anyone is using Tab without js. The only drawback is that the sub menu links display in isolation (without the ul backing being visible). However, the links are in their correct locations, and as long as they have a background colour set on focus they are readable and fine for use. Note that also calling the ul itself visibly is beyond the scope of pure CSS, so this is as good as it gets without js.

With js enabled there is still full Tab key access available of course, but with the added bonus of the ul backing being visible on link focus like it is on hover. Of course the js also brings configurable mouseout delay for those whose tracking skills aren't quite what they should be, and HoverIntent to stop the menus flashing and/or sticking open when the cursor passes over a tab without stopping. Plus of course you can get animation (which does nothing for a11y but looks cool).

I've also changed the display: none; in the default drops to left: -999em; to make them screenreader compatible without js enabled, and changed the visibility: hidden; in the js to make the menus screenreader compatible with js enabled.

Net result is that for 2.1, and for any 2.0 theming any of us do in the meantime, we can now have a drop menu system that will meet the legal requirements of any organisation anywhere.