Fx prefix up for discussion

[Simeon Bateman]

Ok guys,

Its like our dreams have been answered. http://www.adobeforums.com/webx/.59b7cdf0

Matt has opened the floor for discussion of the Fx prefix issue. The
make some noise campaign is working!

sim

[Tom Gonzalez]

After reading the thread, it is comforting to know at least the Adobe folks have put a bit of thought into this issue.

One suggestion would be to post a formal response on the thread for a solution that we all agree to, and have it signed by all of us - that should carry some weight.

Question:   Do we internally have agreement on the solution we would like to see, or are we only agreed that we don't like the current solution Adobe is proposing?

- Tom

Tom Gonzalez

Managing Director

BRIGHTPOINT CONSULTING, INC.

data visualization - software research and development

direct line: 760.634.7657

fax: 760.454.2258

www.brightpointinc.com 

[Brian Holmes]

Is it correct to assume that newer gumbo components are not going to
support the same functionality and styles as halo components? Or is it
just that their underlying implementation is what's different between
the two?

if it's the former i'd like to see a new <fx> prefix to differentiate
between the two.

If it's the latter shouldn't the halo components just be moved and one
namespace be arrived at? fx or mx, whichever? As new gumbo components
come online they could just take the place of the halo component.
Developers maintaining flex 3 and accessing flex 4 would have to do
the work of modifying their program to either use older or newer
components, but maintaining code is alot different that writing new
code and they'd be doing this anyways.

> Question: Do we internally have agreement on the solution we would like to see, or are we only agreed that we don't like the current solution Adobe is proposing?

I don't like the Fx prefix. I go back and forth on what I'd like to
see. But this does look like a great opportunity for us to organize
and present ideas to Adobe.

[Ben Clinkinbeard]

Since Adobe is obviously listening, should we all just pile on support in the thread? http://www.adobeforums.com/webx?128@@.59b7cdf0

I added comments (echoing Sim's great points) because I couldn't resist. I am wondering if we really need a clear consensus among this group now that there is an actual discussion with Adobe. I think if every member of this group comments on that thread in support of roughly the same solution it will be a powerful message.

Ben

[Tom Gonzalez]

I think if we want to support Adobe in making things more open so we can have more direct input then we it owe it to ourselves to be as constructive as possible in providing feedback.

I see a big difference between us deciding as a group on an agreed upon solution that we propose versus having dozens of us offer up lots of different solutions that Adobe then has to wade through which still forces them to do the tough work of evaluating all the trade-offs.   The second scenario seems like it would almost discourage Adobe from opening up stuff like this in the future because it just causes them more work and headaches.   I think the power we have is working with them as an intelligent collective.

That said, I cant argue with the pure visceral pleasure of just having us all post on that thread ;)

- Tom

[Ben Stucki]

I think this list and Adobe's forums are both valid places to talk this through. Hopefully this list gives us a place to gut check thoughts on new plans and proposals from Adobe with our peers. It'll help us validate what we're thinking with each-other, cut down on the noise of the Adobe forum, and get us all headed in the same direction on our efforts. At the same time Adobe is asking for an open dialog with us individually and we should probably feel free to post our responses directly.

The reopening of the discussion also gives us a great opportunity to push this further though. Let's allow the forum to serve it's purpose, but if we can decide as a group the outcome we would like to see from Adobe and back it (post about it) in mass... I have to think it would be very effective. I'll start another post for that purpose, whatever the action is it will probably be good to come to a consensus on the proposed solution.

- Stucki

[Tom Gonzalez]

good points and suggestion

[Tom Chiverton]

2009/2/7 Ben Clinkinbeard <ben.clin...@gmail.com>:

> I added comments (echoing Sim's great points) because I couldn't resist. I

I don't think I can resist waiting much longer, but ...

> am wondering if we really need a clear consensus among this group now that
> there is an actual discussion with Adobe.

We need to 'out' this group now. That means agreeing the 'who we are'
statement in a separate thread. Ben has the final call there.

Then we need to write a few paragraphs that can go on that thread
'from the SDK Community'.
I think everyone here is against FxClass

--
Tom