Hi,

> I think we have confusion over what FlexJS is trying to deliver. If we are
> trying to make a new Flex that works on both HTML/JS and SWF platforms,
> that, to me, implies SWF is the preferred platform and we need to make
> HTML/JS platform conform to it. Thus the coordinate system needs to
> reflect that. 
> 
> If we are trying to make it possible to use ActionScript and MXML to build
> apps that run on HTML/JS platform primarily with SWF being a good way to
> debug and to also run efficiently, then we need to make clean JS code and
> write code to support/mimic that on SWF.

I not sure home many people are going to use the SWF output, but perhaps I’m 
missing a use case. I expect currently if people are targeting swf, AIR or 
mobile they would still use the FlexSDK. Anyone have a different opionion here?

The workflow I found to work well as an application developer is basically to 
ignore the AS side. Reasons being:
- The framework code is different on the AS side to the JS and has different 
features / bugs
- Layout is different between plaftforms and it's a lot of work to get an 
application looking the same in both
- AS side is missing support for a number of common style attributes
- Issues setting up debugging support in the IDE
- Chrome has a decent JS debugger now. You can set breakpoints, look at 
variables etc etc
- Project I’m working on is targeting JS as final output

You still get the benefits of coding in AS and the IDE and compiler pick up a 
lot of issues for you quickly because of that.

> I am not a JavaScript developer so I don't know what JS
> folks come to expect and how they work with this coordinate system. Maybe
> most of the UI is static and the apps just use form fields for input and
> effects are set up in CSS and then triggered so programmatic manipulation
> of object position is rare; I don't know.

Programmatic manipulation currently is required (IMO) if you want your 
application to resize nicely / be responsive.

If % x, % y, min width / height and max width / height  were implemented and/or 
% height and % width worked differently then it may not be so important.

Thanks,
Justin

Reply via email to