[Extendflash] JSFL: Macromedia Request your Feedback

[Patrick Mineault]

1) Complete access to all commands and tools. For example, I can't have 
the document scroll where I want to (hand tool). I can't access find and 
replace and some of the other dialogs. I can't trigger a panel or 
windowSWF to open/close. I can't make the library panel scroll either. I 
can't access anything if anything other than an fla is open. I can't 
emulate the lasso tool, etc.
2) Event-oriented structure. Tools have activate, deactivate, mouseDown, 
etc.. functions and that works swell. Why not have the same thing for 
stage related commands: frameSelect, timelineChanged, etc.
3) Fix the current bugs. JSFL is way, way cool but it's ridiculously 
buggy in some places. Some bugs off the top of my head:

   - setSelectionRect does not select the exact locations, it's always a 
twip off in either direction, and it seems fairly random
   - XMLUI related stuff as noted on Guy's blog
   - selection a library item doesn't make the library scroll to that place
   - closing a windowSWF panel only hides a swf, it doesn't remove it so 
setInterval keeps being called
   - Using persitent drawing on the drawingLayer while using Edit in 
place with a non (0,0) clip fails

4) There's no way to retrieve the selected fills as an array of objects, 
it all comes back as one 'blob'. Having a Fills object would be cool.
5) All my tools, Keith's, Julian's, Guy's and Tony's should be installed 
by default ;)

Patrick

clark slater wrote:

> 1.) Access to duration (frames or time) for Video and Audio items.
> 2.) Ability to add right click menu commands
> 3.) Fix the bug that opens random windowSWF's when Netconnection 
> Debugger is present.
>
>  
> On 10/31/05, *Tomas van der Haase* <tvander at macromedia.com 
> <mailto:tvander at macromedia.com>> wrote:
>
>     Hello:
>
>     I've noted some interest in submitting "JSFL Wish-List" feedback to
>     Macromedia, along with some confusion about where to post such
>     remarks.
>     Well, as one of the Flash QA Engineers working with JSFL, I'd say the
>     best place to send them is to this list, and the best time is now.
>     Although personally I have not more than a teenie-weenie influence re:
>     what gets added or improved upon, [no sarcasm, it's really about
>     thisbig ] I can bend the ear of those with more influence, but users
>     have by far the loudest voice. [ ie: FLfile  came from ur requests. ]
>     With this in mind, Macromedia periodically asks for the "top 3
>     things u
>     would like to do with JSFL which currently are not possible." [because
>     of bugs or functionality which just isn't currently implemented].
>
>
>
>     So here it is: the First Official Request for "Flash 9" (btw, name
>     TBD)
>     re JSFL:
>
>
>
>     Please list the top 3 things u would like to do with JSFL which
>     currently are not possible, or are possible, just not gracefully.
>
>
>     1.
>
>     2.
>
>     3.
>
>
>
>
>     **Please note: The document assembled from ur suggestions &
>     exposed to
>     the powers-that-be will include every single suggestion, so make urs
>     count.
>
>     ***Please also note that this is a timely request for u to provide ur
>     feedback - soon Development resources will be spoken for & changes
>     will
>     get harder & harder to push through.
>
>
>
>     Thanks,
>
>     Tomas van der Haäse
>     Sr. QA Engineer,
>     Macromedia, Inc.
>
>
>     _______________________________________________
>     Extendflash mailing list
>     Extendflash at flashguru.co.uk <mailto:Extendflash at flashguru.co.uk>
>     http://lists.flashguru.co.uk/mailman/listinfo/extendflash
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Extendflash mailing list
>Extendflash at flashguru.co.uk
>http://lists.flashguru.co.uk/mailman/listinfo/extendflash
>  
>