This content has been marked as final.
Show 23 replies
-
1. Re: Kittens saved, Fx prefix will go away
Nate Beck Feb 13, 2009 11:01 AM (in response to matt_chotin)I think it's a great thing that the community and Adobe can work together to make this the best possible platform to develop on.
now let's all go back to being friends :) -
2. Re: Kittens saved, Fx prefix will go away
Simeon Bateman Feb 13, 2009 11:08 AM (in response to matt_chotin)Remember that we "the community" asked for this, and its perfectly acceptable to expect us to help in developing the solutions for the SDK.
But thank you so much to Adobe for listening and for showing your commitment to the concerns of your customers. -
3. Re: Kittens saved, Fx prefix will go away
(Tony_HIllerson) Feb 13, 2009 11:17 AM (in response to matt_chotin)Well played, Flex Team, well played. The community thanks you! -
4. Re: Kittens saved, Fx prefix will go away
matt_chotin Feb 13, 2009 11:34 AM (in response to matt_chotin)I definitely intend to ask for community help on testing the usability of the solutions we come up with. I don’t know that we’d ask that anyone go ahead and implement the changes we have in mind, though if someone feels really comfortable with Batik and wants to get started on handling the CSS solution (as well as making it work in the framework) let us know that it excites you :-)
We’re also really looking to understand how folks will handle the intermix of Spark and Halo components. Not so much that you’d expect the different buttons to appear in the same MXML page, but you’ll have Spark buttons and Halo DateChoosers (which in turn contain Halo buttons) etc, and we want to know what problems folks run into.
Matt
On 2/13/09 11:08 AM, "Simeon Bateman" < member@adobeforums.com> wrote:
A new message was posted by Simeon Bateman in
Developers --
Kittens saved, Fx prefix will go away
Remember that we "the community" asked for this, and its perfectly acceptable to expect us to help in developing the solutions for the SDK.
But thank you so much to Adobe for listening and for showing your commitment to the concerns of your customers.
View/reply at Kittens saved, Fx prefix will go away < http://www.adobeforums.com/webx?13@@.59b7e849/1>
Replies by email are OK.
Use the unsubscribe < http://www.adobeforums.com/webx?280@@.59b7e849!folder=.3c060fa3> form to cancel your email subscription.
-
5. Re: Kittens saved, Fx prefix will go away
Jcheng2334 Feb 13, 2009 12:03 PM (in response to matt_chotin)I didn't know that kittens were at stake!? Anyhow, great work on everyone's part in resolving this sticking point without getting too many feathers ruffled (hopefully).
Matt, I'd expect that you'd probably see a good bit of intermix between the components as the Gumbo components come online--a lot of the stuff I see us working with tend to interleave both rich skinning (for which Gumbo and Catalyst are going to rock) as well as some of the more advanced components that aren't in the immediate Gumbo scope which for the moment look like they'll be extended/skinned Halo ones.
Now that the kittens are saved and Fx is gone, let's all get back to the work of getting the new SDK and new ***-kicking Flex applications out the door, tested and into the hands of happy users. :)
Thanks Flex Team! -
6. Re: Kittens saved, Fx prefix will go away
bclinkinbeard Feb 13, 2009 12:09 PM (in response to matt_chotin)Well played indeed, Flex Team. Thanks for listening to us, we complain because we care. :) -
7. Re: Kittens saved, Fx prefix will go away
(Nick_Kwiatkowski) Feb 13, 2009 12:13 PM (in response to matt_chotin)Matt and the Flex Team : Thanks for listening. I think this exercise has shown everybody involved two important things:
(a) The community really does care about the framework and its direction. Its the love of the product that made us dig in our heels and tell you what we really though about it.
(b) Adobe, and the Flex team cares about the community. Had this project been apart of any other company, I'm sure the response would have been "you'll take what we give you, and you'll like it".
You are all truely steller programmers and we all thank you for that! -
8. Re: Kittens saved, Fx prefix will go away
ChivertonT Feb 13, 2009 12:27 PM (in response to matt_chotin)Thank you so much ! -
9. Re: Kittens saved, Fx prefix will go away
(Arul_Prasad) Feb 13, 2009 12:39 PM (in response to matt_chotin)woohoo!
Awesome you guys! Love you all! -
10. Re: Kittens saved, Fx prefix will go away
(Arul_Prasad) Feb 13, 2009 12:41 PM (in response to matt_chotin)>>I didn't know that kittens were at stake!?
Think Matt was responding to this http://blog.benstucki.net/?p=53 -
11. Re: Kittens saved, Fx prefix will go away
(Josh_Tynjala) Feb 13, 2009 12:43 PM (in response to matt_chotin)Awesome. Thanks to both the Flex team and the passionate community for making this happen! -
12. Re: Kittens saved, Fx prefix will go away
(Daniel_Rinehart) Feb 13, 2009 1:01 PM (in response to matt_chotin)> Kittens saved, Fx prefix will go away<br /><br />My hats off to Adobe for opening the discussion up to the community.<br />While the posts that shaped this discussion were well thought out, I'm<br />happy to see that Fx will be dropped in favor of namespaces. I fell,<br />as others have more eloquently stated, it better positions the<br />platform for the long term.<br /><br />-- Daniel R. <danielr@neophi.com> [http://danielr.neophi.com/] -
13. Re: Kittens saved, Fx prefix will go away
(boobiestar1234) Feb 13, 2009 1:25 PM (in response to matt_chotin)You guys rock! Love you guys! -
14. Re: Kittens saved, Fx prefix will go away
(Peter_deHaan) Feb 13, 2009 1:56 PM (in response to matt_chotin)Yay, that's Fx-ing awesome news! Thanks Matt/Vera/Adobe!!!1!one!!!
I think we should all go and fix [at least] one bug from the "SDK Community Bug Fix Candidates" list at http://bugs.adobe.com/jira/secure/IssueNavigator.jspa?mode=hide&requestId=11403
_peter -
15. Re: Kittens saved, Fx prefix will go away
hgarland Feb 13, 2009 2:00 PM (in response to matt_chotin)What's next? 4 namespaces in Flex 5? :-) -
16. Re: Kittens saved, Fx prefix will go away
(Haykel_Ben_Jemia) Feb 14, 2009 1:38 AM (in response to matt_chotin)Thanks Adobe for listening to us! Now I love Flex even more and knowing that my opinion counts makes me even more convinced that choosing Flex is future proof.
Regarding the intermix of Halo and Spark, my biggest concern was regarding applications that use Arabic text, but now I think it's just a matter of setting the style 'textFieldClass' to 'mx.core.UITLFTextField' to make Halo components use the new TLF. Great!
Another thing is mirroring. Will the Halo components also support it?
The last remaining point is regarding skins. Until all Halo components are ported to Spark, we will have to create skins for component types, but I think this is manageable.
Haykel Ben Jemia
Allmas
Web & RIA Development
http://www.allmas-tn.com
On Fri, Feb 13, 2009 at 8:34 PM, Matt Chotin < member@adobeforums.com> wrote:
A new message was posted by Matt Chotin in
I definitely intend to ask for community help on testing the usability of the solutions we come up with. I don't know that we'd ask that anyone go ahead and implement the changes we have in mind, though if someone feels really comfortable with Batik and wants to get started on handling the CSS solution (as well as making it work in the framework) let us know that it excites you :-)
Developers --
Kittens saved, Fx prefix will go away
We're also really looking to understand how folks will handle the intermix of Spark and Halo components. Not so much that you'd expect the different buttons to appear in the same MXML page, but you'll have Spark buttons and Halo DateChoosers (which in turn contain Halo buttons) etc, and we want to know what problems folks run into.
Matt
On 2/13/09 11:08 AM, "Simeon Bateman" < member@adobeforums.com> wrote:
A new message was posted by Simeon Bateman in
Developers --
Kittens saved, Fx prefix will go away
View/reply at Kittens saved, Fx prefix will go away < http://www.adobeforums.com/webx?13@@.59b7e849/1>
Remember that we "the community" asked for this, and its perfectly acceptable to expect us to help in developing the solutions for the SDK.
But thank you so much to Adobe for listening and for showing your commitment to the concerns of your customers.
Replies by email are OK.
Use the unsubscribe < http://www.adobeforums.com/webx?280@@.59b7e849!folder=.3c060fa3> form to cancel your email subscription.
View/reply at Kittens saved, Fx prefix will go away
Replies by email are OK.
Use the unsubscribe form to cancel your email subscription.
-
17. Re: Kittens saved, Fx prefix will go away
(Haykel_Ben_Jemia) Feb 14, 2009 1:40 AM (in response to matt_chotin)Small correction:
The last remaining point is regarding skins. Until all Halo components
are ported to Spark, we will have to create skins for BOTH component types,
but I think this is manageable.
Haykel Ben Jemia
Allmas
Web & RIA Development
http://www.allmas-tn.com
On Sat, Feb 14, 2009 at 10:38 AM, Haykel BEN JEMIA < haykelbj@gmail.com> wrote:
Thanks Adobe for listening to us! Now I love Flex even more and knowing that my opinion counts makes me even more convinced that choosing Flex is future proof.
Regarding the intermix of Halo and Spark, my biggest concern was regarding applications that use Arabic text, but now I think it's just a matter of setting the style 'textFieldClass' to 'mx.core.UITLFTextField' to make Halo components use the new TLF. Great!
Another thing is mirroring. Will the Halo components also support it?
The last remaining point is regarding skins. Until all Halo components are ported to Spark, we will have to create skins for component types, but I think this is manageable.
Haykel Ben Jemia
Allmas
Web & RIA Development
http://www.allmas-tn.com
On Fri, Feb 13, 2009 at 8:34 PM, Matt Chotin < member@adobeforums.com> wrote:
A new message was posted by Matt Chotin in
I definitely intend to ask for community help on testing the usability of the solutions we come up with. I don't know that we'd ask that anyone go ahead and implement the changes we have in mind, though if someone feels really comfortable with Batik and wants to get started on handling the CSS solution (as well as making it work in the framework) let us know that it excites you :-)
Developers --
Kittens saved, Fx prefix will go away
We're also really looking to understand how folks will handle the intermix of Spark and Halo components. Not so much that you'd expect the different buttons to appear in the same MXML page, but you'll have Spark buttons and Halo DateChoosers (which in turn contain Halo buttons) etc, and we want to know what problems folks run into.
Matt
On 2/13/09 11:08 AM, "Simeon Bateman" < member@adobeforums.com> wrote:
A new message was posted by Simeon Bateman in
Developers --
Kittens saved, Fx prefix will go away
View/reply at Kittens saved, Fx prefix will go away < http://www.adobeforums.com/webx?13@@.59b7e849/1>
Remember that we "the community" asked for this, and its perfectly acceptable to expect us to help in developing the solutions for the SDK.
But thank you so much to Adobe for listening and for showing your commitment to the concerns of your customers.
Replies by email are OK.
Use the unsubscribe < http://www.adobeforums.com/webx?280@@.59b7e849!folder=.3c060fa3> form to cancel your email subscription.
View/reply at Kittens saved, Fx prefix will go away
Replies by email are OK.
Use the unsubscribe form to cancel your email subscription.
-
18. Re: Kittens saved, Fx prefix will go away
(Mrinal_Wadhwa) Feb 14, 2009 3:06 AM (in response to matt_chotin)Thank you, Flex Team ... this reflects greatly on Adobe's commitment to listening to the community, we appreciate it a lot.
Also, a big thanks to all the community members who made efforts to making this happen.
Cheers,
Mrinal -
19. Re: Kittens saved, Fx prefix will go away
(Joseph_Balderson) Feb 15, 2009 1:42 AM (in response to matt_chotin)I guess if I read this first I needn't have made this post:
Joseph Balderson, "Fx prefix revisited" #67, 15 Feb 2009 1:17 am
Awesome news Matt! Thanks for listening Adobe!! -
20. Re: Kittens saved, Fx prefix will go away
matt_chotin Feb 15, 2009 11:47 AM (in response to matt_chotin)We plan on making mirroring work for Halo too. And the textFieldClass will be TLFTextField by default hopefully.
On 2/14/09 1:38 AM, "Haykel Ben Jemia" < member@adobeforums.com> wrote:
A new message was posted by Haykel Ben Jemia in
Developers --
Kittens saved, Fx prefix will go away
Thanks Adobe for listening to us! Now I love Flex even more and knowing that my opinion counts makes me even more convinced that choosing Flex is future proof.
Regarding the intermix of Halo and Spark, my biggest concern was regarding applications that use Arabic text, but now I think it's just a matter of setting the style 'textFieldClass' to 'mx.core.UITLFTextField' to make Halo components use the new TLF. Great!
Another thing is mirroring. Will the Halo components also support it?
The last remaining point is regarding skins. Until all Halo components are ported to Spark, we will have to create skins for component types, but I think this is manageable.
Haykel Ben Jemia
Allmas
Web & RIA Development
http://www.allmas-tn.com
On Fri, Feb 13, 2009 at 8:34 PM, Matt Chotin < member@adobeforums.com> wrote:
A new message was posted by Matt Chotin in
Developers --
Kittens saved, Fx prefix will go away
I definitely intend to ask for community help on testing the usability of the solutions we come up with. I don't know that we'd ask that anyone go ahead and implement the changes we have in mind, though if someone feels really comfortable with Batik and wants to get started on handling the CSS solution (as well as making it work in the framework) let us know that it excites you :-)
We're also really looking to understand how folks will handle the intermix of Spark and Halo components. Not so much that you'd expect the different buttons to appear in the same MXML page, but you'll have Spark buttons and Halo DateChoosers (which in turn contain Halo buttons) etc, and we want to know what problems folks run into.
Matt
On 2/13/09 11:08 AM, "Simeon Bateman" < member@adobeforums.com < http://member@adobeforums.com> > wrote:
A new message was posted by Simeon Bateman in
Developers --
Kittens saved, Fx prefix will go away
Remember that we "the community" asked for this, and its perfectly acceptable to expect us to help in developing the solutions for the SDK.
But thank you so much to Adobe for listening and for showing your commitment to the concerns of your customers.
View/reply at Kittens saved, Fx prefix will go away < http://www.adobeforums.com/webx?13@@.59b7e849/1>
Replies by email are OK.
Use the unsubscribe < http://www.adobeforums.com/webx?280@@.59b7e849!folder=.3c060fa3 < http://www.adobeforums.com/webx?280@@.59b7e849%21folder=.3c060fa3> > form to cancel your email subscription.
View/reply at Kittens saved, Fx prefix will go away < http://www.adobeforums.com/webx?13@@.59b7e849/3>
Replies by email are OK.
Use the unsubscribe < http://www.adobeforums.com/webx?280@@.59b7e849%21folder=.3c060fa3> form to cancel your email subscription.
View/reply at Kittens saved, Fx prefix will go away < http://www.adobeforums.com/webx?13@@.59b7e849/15>
Replies by email are OK.
Use the unsubscribe < http://www.adobeforums.com/webx?280@@.59b7e849!folder=.3c060fa3> form to cancel your email subscription.
-
21. Re: Kittens saved, Fx prefix will go away
Constantin Ehrenstein Feb 18, 2009 11:53 AM (in response to matt_chotin)Yay, that's good news!
I'll chime in with the others, stating my gratitude and satisfaction with the outcome of the matter as well as with the way the Flex SDK opened up to the community.
You showed that you care, and obviously for all of us the most sophisticated, forward-compatible language is the top priority.
Best regards
Constantin -
22. Re: Kittens saved, Fx prefix will go away
Sekhar Ravinutala Feb 19, 2009 9:25 AM (in response to matt_chotin)Excellent news, thanks guys for listening! -
23. Re: Kittens saved, Fx prefix will go away
(RJ_Owen) Feb 20, 2009 1:31 PM (in response to matt_chotin)I've been on Mars the last week. Thanks for this, Flexers!


