Priorities and Dev Branch

[Jörn Zaefferer]

Hi,

we've tweaked our process to develop new plugins a few times already,
and this probably won't be the last time. After various discussion
during the DevDays and the conference, Richard, Scott and me decided
during the team meeeting today to restructure the dev branch, and
therefore our priorities, as the following:

- Move all folders currently under branches/dev into branches/labs
- Create a new branch from trunk under braches/dev
- Start from scratch, in that single branch, with autocomplete,
button, modal, menu and tooltip
- Once these five are all merged into trunk, start on a new dev branch
with five new widgets

I'll be doing the necessary changes, starting tomorrow. If you have
any questions, let me know in this thread.

Jörn

[Jörn Zaefferer]

One more change: During the DevDays it was suggested to prepend
"jquery" to our source files. Considering that the Download Builder
needs a rewrite anyway, we'll rename files in trunk asap (before
creating the new dev branch).

So we'll get
- jquery.ui.pluginName.js
- jquery.effects.pluginName.js

Jörn

[Ca-Phun Ung]

On Thu, Sep 17, 2009 at 3:18 AM, Jörn Zaefferer <joern.z...@googlemail.com> wrote:

- Start from scratch, in that single branch, with autocomplete,
button, modal, menu and tooltip

- I propose adding spinner to this list. It's pretty close to being ready.

- How does this change affect the 1.8 release. Will 1.8 wait for these to be ready or are we not going to add more to 1.8?
 

--
Ca-Phun Ung
+ http://yelotofu.com
+ hongkong, zce, jquery, jqueryui, php, css, html

[Scott González]

On Wed, Sep 16, 2009 at 3:41 PM, Ca-Phun Ung <cap...@yelotofu.com> wrote:

- I propose adding spinner to this list. It's pretty close to being ready.

We chose this list based on the feedback we've been hearing from the community over the past several months. We're going to be very strict about sticking to these priorities. We've had too many distractions from various people working on various new plugins, especially plugins that are not listed as a priority. As a team, we absolutely must focus on our actual priorities or we will never get where we need to be.

- How does this change affect the 1.8 release. Will 1.8 wait for these to be ready or are we not going to add more to 1.8?

1.8 will likely come out in early January with lots of pre-releases prior to the final release. Whatever is stable enough for trunk by the time of our first beta release (date TBD) is what will land in 1.8. We will only land new plugins that are in our priority list, and only accept the most basic and common functionality for those plugins.

After all of our priority plugins land in trunk, we will discuss the next set of plugins to work on.

[Richard D. Worth]

On Wed, Sep 16, 2009 at 3:40 PM, Jörn Zaefferer <joern.z...@googlemail.com> wrote:

One more change: During the DevDays it was suggested to prepend
"jquery" to our source files. Considering that the Download Builder
needs a rewrite anyway, we'll rename files in trunk asap (before
creating the new dev branch).

So we'll get
- jquery.ui.pluginName.js
- jquery.effects.pluginName.js

perhaps lcase?

jquery.ui.pluginname.js

jquery.effects.pluginname.js

After all, jquery.js is lcase even though the variable is jQuery.

- Richard

[Scott González]

On Wed, Sep 16, 2009 at 4:03 PM, Richard D. Worth <rdw...@gmail.com> wrote:

perhaps lcase?

jquery.ui.pluginname.js

jquery.effects.pluginname.js

After all, jquery.js is lcase even though the variable is jQuery.

Yeah, the files will be all lowercase, this was just to show the prepending. 

[Ralph Whitbeck]

I think this approach of moving everything to labs makes sense.

2009/9/16 Scott González <scott.g...@gmail.com>

[Jörn Zaefferer]

I've started outlining the functional specs for Modal and Tooltip:

http://wiki.jqueryui.com/Modal
http://wiki.jqueryui.com/Tooltip

It looks like both Buttons (as Button?) and Menu need a reset, there
is no way to start with 9 and 12 options...

Suggestions?

Jörn

[Ralph Whitbeck]

Jörn,

When do you sleep?  You are like machine today!

Ralph

[Ca-Phun Ung]

Menu options:

• width - not sure why there are two width options listed?
• maxHeight - could this be handled by css?
  
• hoverClass, hoverClassSecondary & nextMenuClass - Could probably drop these as currently marked "tbd"
• flyoutDelay - this could be merged into the type option so if an integer is passed we know it's a time delay and the default is flyout anyway.

That brings us down to 5 options.

[Ca-Phun Ung]

On Thu, Sep 17, 2009 at 12:56 PM, Ca-Phun Ung <cap...@yelotofu.com> wrote:

 

That brings us down to 5 options.

Correction: That brings us down to 6 options.

[Paul Bakaus]

On Wed, Sep 16, 2009 at 9:18 PM, Jörn Zaefferer <joern.z...@googlemail.com> wrote:

Hi,

we've tweaked our process to develop new plugins a few times already,
and this probably won't be the last time. After various discussion
during the DevDays and the conference, Richard, Scott and me decided
during the team meeeting today to restructure the dev branch, and
therefore our priorities, as the following:

- Move all folders currently under branches/dev into branches/labs

I think this might not be the best idea. The labs are a place to explore new ideas that

are off table, and everything in the dev branch, though low priorized, is actual dev work.

We might need another place for low priorized stuff to sit, but I'm not sure labs is that

place - it's not our trash dump. Thoughts?

 

- Create a new branch from trunk under braches/dev

I really like that. All those branches off trunk made me really unproductive at times, it's

a mess to sync all of them. Thanks!

 

- Start from scratch, in that single branch, with autocomplete,
button, modal, menu and tooltip

 

- Once these five are all merged into trunk, start on a new dev branch
with five new widgets

I'm a bit concerned about selectables. There's a ton of people waiting for this to get out, and

it's 95% done (I guess). I absolutely don't want to get the focus off the other plugins, but at

any chance, would like to suggest that we leave the possibility open to introduce this rewrite

to 1.8 as well.

 

I'll be doing the necessary changes, starting tomorrow. If you have
any questions, let me know in this thread.

Thanks,

Paul

 

Jörn

--
Paul Bakaus
UI Architect @ smart.fm
--
http://paulbakaus.com
http://www.linkedin.com/in/paulbakaus

[Richard D. Worth]

On Thu, Sep 17, 2009 at 2:23 AM, Paul Bakaus <paul....@googlemail.com> wrote:

On Wed, Sep 16, 2009 at 9:18 PM, Jörn Zaefferer <joern.z...@googlemail.com> wrote:

Hi,

we've tweaked our process to develop new plugins a few times already,
and this probably won't be the last time. After various discussion
during the DevDays and the conference, Richard, Scott and me decided
during the team meeeting today to restructure the dev branch, and
therefore our priorities, as the following:

- Move all folders currently under branches/dev into branches/labs

I think this might not be the best idea. The labs are a place to explore new ideas that

are off table, and everything in the dev branch, though low priorized, is actual dev work.

We might need another place for low priorized stuff to sit, but I'm not sure labs is that

place - it's not our trash dump. Thoughts?

Labs should be a welcome home to plugins at various levels of maturity that can be collaborated on by individuals and the community while waiting for the full attention of the UI Dev team. Just as labs has no requirement like "that plugin isn't mature enough" labs should have no requirement like "that plugin is too mature". If something is ready it will wait there for review. If it's not ready, labs is a fine place for it to be made ready.

 

 

- Create a new branch from trunk under braches/dev

I really like that. All those branches off trunk made me really unproductive at times, it's

a mess to sync all of them. Thanks!

 

- Start from scratch, in that single branch, with autocomplete,
button, modal, menu and tooltip

 

- Once these five are all merged into trunk, start on a new dev branch
with five new widgets

I'm a bit concerned about selectables. There's a ton of people waiting for this to get out, and

it's 95% done (I guess).

The specs changes that were agreed upon since it was recently reviewed for inclusion in trunk leave about 50% in my estimation. If I'm wrong, I'll be pleasantly surprised when someone completes it in a matter of hours instead of days or weeks.

 

I absolutely don't want to get the focus off the other plugins, but at

any chance, would like to suggest that we leave the possibility open to introduce this rewrite

to 1.8 as well.

That possibility is open. It wasn't decided that selectables can't be in 1.8. It was decided that the UI Dev team will focus development effort on these other plugins first. It's quite reasonable for you, and anyone else, to

- work on selectables in parallel in the labs

or

- work on these five plugins with us so that we can get to selectables sooner

- Richard

[Richard D. Worth]

On Wed, Sep 16, 2009 at 3:40 PM, Jörn Zaefferer <joern.z...@googlemail.com> wrote:

One more change: During the DevDays it was suggested to prepend
"jquery" to our source files. Considering that the Download Builder
needs a rewrite anyway, we'll rename files in trunk asap (before
creating the new dev branch).

So we'll get
- jquery.ui.pluginName.js
- jquery.effects.pluginName.js

Done in r3243. TestSwarm is showing no regressions in those file renames, but there were a lot of files changed. Would appreciate a quick review, if someone gets a chance. Especially with the many datepicker i18n files. Thanks.

- Richard

[Jörn Zaefferer]

I've finished the move, updated links on affected wiki pages, and
created a fresh branch. New jquery.ui.[plugin].js files for
autocomplete, button, menu, modal and tooltip are commited, too.

I'll start a new thread for some Menu planning, which also affects Autocomplete.

Jörn

[Todd Parker]

Awesome work Jörn, you are a machine! 

Todd Parker

to...@filamentgroup.com

On Sep 17, 2009, at 8:33 AM, Jörn Zaefferer <joern.z...@googlemail.com> wrote:

Jörn