title says it all, really.
I'm building tools for my art team to help convert a ton of Flash assets. I'vee been at JSFL long enough to see the attraction of xJSFL. But I need tools I can package as .mxp files and pass to my team wiht a minimum of fuss. If I build windowSWF tools in xJSFL, will others need xJSFL nstalled?
Hey Mambo,
Yeah, they will if you are going to use any code from xJFSL.
The xJSFL install is easy though - download the zip, unzip to a location of your choice, and double-click install.jsfl.
In your panel code, to check if xJSFL is installed, you only need to test for window.xjsfl. It might be prudent of me to stick some boilerplate code on the site that directs users to the latest download.
Regarding distributing the panels and code, currently, xJSFL modules just need to be copied to the modules/ subfolder to run. No MXP file needed, although there is an XML manifest, and there would of course be a short learning curve - but that's what the forum is here for!
Also, check the Sample module that ships with the framework to see how modules package panels, config, JSFL and AS3 code into an easy-to-manage folder structure.
I don't know that much about MXPs, but I'm sure they could be used to deliver payloads of xJSFL modules, even if I have to do something like copy them to a temp Flash folder, then on next restart, move them to the xJSFL folder.
Feel free to suggest ideas if you have any good ones!
Cheers,
Dave
I would prefer keep the end user experience for my tools as idot proof as possible...as in "just click this icon and let Adobe Extension Managerdo it"
MXP files are the compiled files, generated by Adobe's Extansion Mananger from an MXI file(really just XML) telling Extansion Mananger "gather these source files together. On install, place them in these locations." that plus a few details about version/ platform etc...
a line form the mxi file for 'installing' a JSFL script looks like this:
<file name="SetMCtoTopLeftWithElementAdjust.jsfl" destination="$flash/WindowSWF" />
I can't imagine it would be hard to make
<file name="xJSFL_source_file_of_some _sort.xjfl" destination="$flash/wherever/" />
Maybe If I get a moment I'll see if I can create an mxp installer for xJSFL
Hi,
I'm also looking for packaging a jsfl panel, without the need of installing xJSFL on each computer of my team.
Did you figured out the issue ?
Thank you ;)
Hey exoa,
This functionality will be part of the Pro Tools pack that will be released in the next month or so.
The framework is going to be released on an Open Source license, so will be free to use, but the packager will be a paid add-on. It's going to come with a whole bunch of goodness, including an interactive debugger panel for Komodo, and a bunch of other nice things.
Can you hang on that long!?
PS. The Beta 2 which is going to be released next week makes a LOT of changes under the hood, so might be worth hanging on till then anyway :)
nice !
I can't wait to see the new great stuff you will provide !
The first panel I have to build is for next week, so i will use the xjsf installer anyway plus the snippet panel for now.
Looking forward to the next builds !
Thank you.