You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Carlos Rovira <ca...@codeoscopic.com> on 2012/08/14 21:49:42 UTC
New components code
Hi Carol,
I check your whiteboard to see the new components added but I miss a spark
DateField. We can expect to see it in your whiteboard at some time?
On the other hand, I'm interested in do some work on dinamic view states. I
remember that Alex said that some work was done in Adobe regarding this
feature, so I would want to ask if there's something done, if it is is
checked? what level of completion has?
Thanks in advance for any insight on those things
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 35 57 77
<http://www.codeoscopic.com>
CODEOSCOPIC S.A. <http://www.codeoscopic.com>
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid
Re: New components code
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Again that's a shame since I was aware that Flash Player should be the
backbone for DateField. I think DateField is the most needed spark
component since mx:DateField has many problems. I don't have the knowledge
to evaluate but without the flash player support you comment, we have few
possibilities to have ending the component we really need. What do you
think about it?
2012/8/14 Carol Frampton <cf...@adobe.com>
>
>
> On 8/14/12 4 :11PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
> >Thanks Carol,
> >
> >I check the link you provide, but nothing seems to throw for states.
> >
> >Regarding DateField, it's a pitty since I never read what you say and was
> >convinced that spark DateField was one of the components that was coming
> >from Adobe.
>
> The major work for the spark DateChooser was internationalization
> (strings, date formats, horizontal and vertical layout, left-to-right and
> right-to-left layout, ability to put any image in any date cell for
> example moons, Chinese characters, etc).
>
> The DateField was suppose to parse all kinds of date strings and the parse
> support was suppose to come from the player. I looked recently and that
> support did not end up being done.
>
> Carol
>
>
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 35 57 77
<http://www.codeoscopic.com>
CODEOSCOPIC S.A. <http://www.codeoscopic.com>
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid
Re: New components code
Posted by Carol Frampton <cf...@adobe.com>.
On 8/14/12 4 :11PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>Thanks Carol,
>
>I check the link you provide, but nothing seems to throw for states.
>
>Regarding DateField, it's a pitty since I never read what you say and was
>convinced that spark DateField was one of the components that was coming
>from Adobe.
The major work for the spark DateChooser was internationalization
(strings, date formats, horizontal and vertical layout, left-to-right and
right-to-left layout, ability to put any image in any date cell for
example moons, Chinese characters, etc).
The DateField was suppose to parse all kinds of date strings and the parse
support was suppose to come from the player. I looked recently and that
support did not end up being done.
Carol
Re: New components code
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Thanks Carol,
I check the link you provide, but nothing seems to throw for states.
Regarding DateField, it's a pitty since I never read what you say and was
convinced that spark DateField was one of the components that was coming
from Adobe.
2012/8/14 Carol Frampton <cf...@adobe.com>
>
>
> On 8/14/12 3 :49PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
> >Hi Carol,
> >
> >I check your whiteboard to see the new components added but I miss a spark
> >DateField. We can expect to see it in your whiteboard at some time?
>
> I've said numerous times there is no spark DateField. It was assigned to
> me but it was not started.
>
> >
> >On the other hand, I'm interested in do some work on dinamic view states.
> >I
> >remember that Alex said that some work was done in Adobe regarding this
> >feature, so I would want to ask if there's something done, if it is is
> >checked? what level of completion has?
>
> I've moved the code I found over from Adobe but haven't touched it since.
> Since I didn't do that work I don't know where it might be or what state
> it is in.
>
> I dumped the svn history for the changes into
> https://svn.apache.org/repos/asf/incubator/flex/whiteboard/cframpton/adobe.
> next/CHANGES.adobe.next so you could scan that. This includes all the
> changes except for the spark DateChooser component.
>
> Once I have time to look at the code and write some sample programs I will
> figure out what might be done enough to move out of my whiteboard to
> wherever we finally decide it should land.
>
> Carol
>
>
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 35 57 77
<http://www.codeoscopic.com>
CODEOSCOPIC S.A. <http://www.codeoscopic.com>
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid
Re: New components code
Posted by Alex Harui <ah...@adobe.com>.
On 8/14/12 12:59 PM, "Carol Frampton" <cf...@adobe.com> wrote:
>
>
> On 8/14/12 3 :49PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
>> Hi Carol,
>>
>> I check your whiteboard to see the new components added but I miss a spark
>> DateField. We can expect to see it in your whiteboard at some time?
>
> I've said numerous times there is no spark DateField. It was assigned to
> me but it was not started.
>
>>
>> On the other hand, I'm interested in do some work on dinamic view states.
>> I
>> remember that Alex said that some work was done in Adobe regarding this
>> feature, so I would want to ask if there's something done, if it is is
>> checked? what level of completion has?
The states work was being prototyped as part of the Falcon/MXML work. It
was separate from the Flex.Next components.
I will have to find it and see if I can just check it in w/o having to go
through the usual process.
That said, the reason this kind of thing was being prototyped was because
Falcon was supposed to be SDK version independent. IOW, it was going to be
integrated into and shipped with Flash Builder. SDKs could be shipped
independently. The plan was to take all of the current generated code and
generate data structures instead and have SDK code interpret the data
structures (which turned out to be faster in almost every case). By turning
the states generated code into data structures it would be possible to
create a library to generate and manipulate those data structures at
runtime.
Now with Falcon at Apache, we have no guarantee that Flash Builder will be
able to successfully incorporate an Apache-built Falcon compiler into Flash
Builder. IMO, there isn't a very good abstraction layer between the
compiler and the rest of FB.
So, we may end up with Falcon being packaged and run more like MXMLC. The
MXMLC scripts might just get changed to call into Falcon for example. And
that eliminates one major reason for taking the time to finish this kind of
code. A safer route which is much farther along already is to try to make
sure Falcon generates the same AS code as MXMLC. Then you know you're less
likely to hit new issues at runtime.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: New components code
Posted by Carol Frampton <cf...@adobe.com>.
On 8/14/12 3 :49PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>Hi Carol,
>
>I check your whiteboard to see the new components added but I miss a spark
>DateField. We can expect to see it in your whiteboard at some time?
I've said numerous times there is no spark DateField. It was assigned to
me but it was not started.
>
>On the other hand, I'm interested in do some work on dinamic view states.
>I
>remember that Alex said that some work was done in Adobe regarding this
>feature, so I would want to ask if there's something done, if it is is
>checked? what level of completion has?
I've moved the code I found over from Adobe but haven't touched it since.
Since I didn't do that work I don't know where it might be or what state
it is in.
I dumped the svn history for the changes into
https://svn.apache.org/repos/asf/incubator/flex/whiteboard/cframpton/adobe.
next/CHANGES.adobe.next so you could scan that. This includes all the
changes except for the spark DateChooser component.
Once I have time to look at the code and write some sample programs I will
figure out what might be done enough to move out of my whiteboard to
wherever we finally decide it should land.
Carol