Interesting. Two replies with different view points. I have another
factor that occurred to me. I think we should try to get a release out
ASAP so that folks can have a chance to look at it and get interested and
consider a last minute signup for 360|Flex (assuming there are still
spots).
That
>
> 1) Do some package reorganization: Currently most components are in
> org.apache.flex.html.staticControls. However these controls aren't quite
> so static, so I'm thinking of removing the staticControls folder and
> flattening the hierarchy by one level.
>
All for it. Be sure to "freeze the
On 21/03/14 19:19, Alex Harui wrote:
folks to try. Yes, the changes above might have backward compatibility
impact on folks using these first releases, but IMO, if we set expectation
correctly, folks will be flexible.
Release early, release often would be my suggestion.
Package or XMLNS change
Hi Folks,
Getting some sort of checkintest infrastructure was the last "must-have"
on my list before starting the process of cutting our first FlexJS
release. Below is a list of things I thought about doing, but since this
is 'alpha' I think we don't have to wait. That said, we do want to make a
