I'm can't found any information about license. What license used for xJSFL? It's proprietary or free software?

I'm try use xJSFL on my Mac, but after install when I'm restart Flash xJSFL doesn't start initialization. Maybe problem with Creative Cloud version of Flash?

This is screenshot what I captured after install. And this is install log.

Very strange what installed commands is doesn't appears in command menu after restart.

keep it up. well done

=================================================================

           ██  █████ ██████ ██
           ██ ██     ██     ██
  ██ ██    ██  ████  █████  ██
   ███     ██     ██ ██     ██
  ██ ██ ████  █████  ██     █████

=================================================================

  The Rapid-Development Framework for Extending Adobe Flash

> xjsfl: INSTALLING xJSFL...
> xjsfl: loading proxy classes...
> xjsfl: loading xjsfl...
The following JavaScript error(s) occurred:


> xjsfl: LOADING CORE CLASSES...
The following JavaScript error(s) occurred:

Thats it, nothing else. I look for the panel in CS6 after restarting, but. as expected, is not working...

Can you help?

I have version CS6 (12.0.2)

Many thanks!

I was trying to install xJSFL framework from commit (872de94c70) on Flash CS5.5 on Windows 7 x64 but it failed with empty error in output panel.

I have tried running Flash as Administrator but it gave no results either. 

Is there anything I can do with that (taking earlear version or something)?

I found bug with user libraries initialization. After Flash IDE start in output panel shows what all my libraries is loaded. But is not true. For solving this problem I must manualy execute reloading in commands panel.

I check on Win7 and Win8 with Flash CS6, in both cases this bug apears.

Video with bug reproduction. Test snippet code:

(function() {
  function testIt() {
    trace(xjsfl);
    trace(XULER);
  }

  xjsfl.init(this);

  testIt();
})(); 

TypeError: redeclaration of const IFL_FILE_EXT 

This same script also will throw errors running through the snippets panel (with flash gobbling the error message) but when I run it through commands>run it usually will run without errors.  Right now it's just a hunch that CONST is causing trouble - since I don't use it and it runs fine.  Searches elsewhere on the web say that CONST implementation in Javascript is spotty so if there's reasons not to do it I'd just as well pull it out.

edit: added error text

I have question about XUL interface layouts. At this moment default layout have 2 columns. One for labels and second for elements like textarea and dropdown. How I can customize layout using basic API methods (addButton, addDropdown and etc).

And small second question. How I can select some element in Listbox?

I tried to use #reveal() method in ItemsCollection but it didn't work (function #exapandFolder() executes and returns "true" but folder is still collapsed). I have found in forums that library.expandFolder doesn't work at all on CS versions >3. Does it work for you?

Thanks!
Rytis 

I'm trying to parse some .xml to extract datas, so  I tried you're xml-testing.jsfl and xml.jsfl, in Codes Examples.
And read you're support about xml.
If I try this (xmlTest.jsfl) :

xjsfl.init(this);
clear()
		var xml =
			<xml>
				<a id='a' vowel="true"/>
				<b id='b'/>
				<c id='c' class="test" />
				<d id='d' class="test">
					<e id='e' vowel="true">
						<f id='f' class="test" />
					</e>
				</d>
			</xml>

fl.trace(xml.toXMLString());
var nodes = xml.find('a');
trace("nodes :  " + nodes); 

trace >>

nodes : undefined

 If I try 

 xml.remove('.test', true);
 trace(xml.toXMLString());

trace >>

XML > processing path ".test": Object (depth:4, objects:0, values:7, time:0.0 seconds)
---------------------------------------------------------------------------------------
object => Object
match: ".test"
operator: "."
node: "test"
index: ""
filter: ""
attribute: ""
matchIndex: 0
<xml>
  <a id="a" vowel="true"/>
  <b id="b"/>
  <c id="c" class="test"/>
  <d id="d" class="test">
    <e id="e" vowel="true">
      <f id="f" class="test"/>
    </e>
  </d>
</xml>

I suppose I use a wrong method to access to nodes (?)
Thank's for this great framework. 
:-)
Nardo 

Thanks!

I couldn't get the selector $$ to work with library fonts, I had to instead iterate through the entire library and look for all instances that are fonts.

I feel like I am doing this the hard way, or I am missing something?

Tries:

$$("fonts");

but instead, need to use:

var libraryItems = dom.library.items;
var i = libraryItems.length;
while (i--) {
	var item = libraryItems[i];
	if (item.itemType == "font") {
		processFont(item);
	}
}

I am looking for a user-friendly way to append as3 code into a timeline. I have it working ( see below ), but it's not elegant.

In english:

• select first layer on stage root timeline.
• test if the name is "ACTIONS", if not make it.
• clear all as code in the clip
• write new code into the clip

timeline.setSelectedLayers(0);
if( timeline.getLayerProperty("name") != "ACTIONS" ){
	timeline.addNewLayer('ACTIONS');
	timeline.setSelectedLayers(0);
}
var trgt = timeline.layers[0].frames[0];
trgt.actionScript = "";
trgt.actionScript +='\n // ADD as3 Code line by line';

I'm just starting out converting our exporter to a xJSFL module and I'm not sure whether the custom module needs to be in the xJSFL/modules folder? If they do, it seems a little messy, although I suppose I could make it a git submodule (even though they suck :)).

Also, assuming it's OK to do so, you should update your docs to remove the absolute paths from your Sample Module code here: http://www.xjsfl.com/support/guides/extensibility/modules#swf-panel.

-Aranda

I got this output just after I run the "install.jsfl". It seems no xjsfl script has been loaded and when I try to execute code such as "xjsfl.init()" I got an error: xjsfl.init is not a function.

I'm using Flash CS5 with Simplified Chinese environment. How can I fix this?

At the moment, you can't pass native DataTypes from AS3 to JSFL:

throw new Error('Objects of type ' + type + ' cannot be passed to JSFL');

Is there a reason for not using the JSON encoder/decoder to pass values around, so you could encode any object (to native object).
And you could also pass the type as an extra field (like amfphp does) so you can reconstruct the same object on the other side.

I'm developing a panel, and while there is a nice snippet for uploading the swf to the WindowSWF folder, it seems I have to restart Flash every time I have changed my JSFL module code. The 'Reload xJSFL' doesn't work either.

I've tested it with altering traces, and the changes only show up after I've restarted Flash.

Is this normal behavior? Can there be done anything to make this process easier?

I ran into a specific problem while trying to update xJSFL to version 1.0, I thought you might want to know about it. Context: Flash CS5.5 *and* CS6, OSX 10.7.4 - with existing installation of the previous xJSFL release in /Developer/xJSFL

First thing that happened is the installer complained about needing a document open before proceeding - not sure where that call was from exactly (see log at the bottom). My (frustrating) experience with jsfl would point to something along the lines of a document check (dom != null) in a context where it's not necessary. Searching for "REMOVING OLD COMMANDS..." brought me to install.jsfl, which I modified to trace values. I found it seems to go belly-up here (line 148)

var uris = Utils.getURIs(fl.configURI + 'Commands/xJSFL/');

What I think happened is the "xJSFL" folder was successfully deleted the first time around, before I was asked to open a document. Then when trying to find the same folder to clean up an existing installation which was already cleaned up (at least in part), an error is returned. I added an empty xJSFL folder in Configuration/Commands, and the next time I ran the installer, it successfully completed (without having a document open -- although the installer creates an empty one and leaves it there)

A note: my first update on a separate computer (same OS and Flash version) was successful on the first try. I can't remember if I had a document open or not, but I'm assuming I did. 

Here's how I was able to reproduce the bug at least three times:

- run /Developer/xJSFL/core/jsfl/install/uninstall.jsfl

- restart Flash CS5.5/CS6

- run /Developer/xJSFL/install.jsfl (without a FLA open)

Additional info: I noticed that uninstall.jsfl sometimes leaves the Commands/xJSFL folder and its contents in the file system.

 Congrats on the tremendous amount of work you put into this project. I'm very impressed, especially by the efforts that went into the Komodo integration/plugins.

Max

CS5.5:

> xjsfl: INSTALLING xJSFL...

> xjsfl: loading proxy classes...

> xjsfl: loading xjsfl...

> xjsfl: LOADING CORE CLASSES...

> xjsfl: loading library: Globals

> xjsfl: loading library: Utils

> xjsfl: loading library: URI

> xjsfl: loading library: URIList

> xjsfl: LOADING SUPPORTING CLASSES...

> xjsfl: added 25 search paths for "{core}jsfl/libraries/Macintosh HD/Developer/xJSFL/core/"

> xjsfl: loading library: JSFLInterface

> xjsfl: loading library: XUL

> xjsfl: loading library: File

> xjsfl: loading library: Class

> xjsfl: loading library: FileSystemObject

> xjsfl: loading library: Folder

> xjsfl: loading library: XML

> xjsfl: loading library: String

> xjsfl: loading library: SimpleTemplate

> xjsfl: loading library: XULControl

> xjsfl: loading library: XULEvent

> xjsfl: loading library: Output

> xjsfl: loading library: Table

> xjsfl: loading library: PropertyResolver

> xjsfl: REMOVING OLD COMMANDS...

The following JavaScript error(s) occurred:

Open a Flash document (FLA) before running this script.

CS6:

> xjsfl: INSTALLING xJSFL...

> xjsfl: loading proxy classes...

> xjsfl: loading xjsfl...

The following JavaScript error(s) occurred:

> xjsfl: LOADING CORE CLASSES...

The following JavaScript error(s) occurred:

xjsfl.init(this)

var files = [];
var assetPath = "file:////Users/.../"
var pathToFLA = "file:////Users/.../";
//TODO - investigate xjsfl opening XFL files? Seems to not work correctly.
var folder = new Folder(assetPath).each(
										function(element,index)
										{
											trace(index,element);
											files.push(element)
										})
var doc = fl.openDocument("file:///" + files[0].path)

var mc = $("*").select();

if(files[0].open)
{
	optimiseRaster();
	nestedCollection();
}

function checkNames(item)
{
	//sets compression type of each bitmap in the library
	item.compressionType = 'photo';
}

function optimiseRaster()
{
	//creates an item collection array of the bmp's in the library
	var collection = $$(":bitmap");
	collection.exec(checkNames);
	//save the file
	saveFile();
}

function nestedCollection()
{
	trace(mc.timeline)
}

function saveFile()
{
	//TODO - get the file name and use it to name the save file
	
	var docName = document.name;
	var append = "youth_1.fla"
	var docURI = pathToFLA + append;
	fl.saveDocument(docName,docURI);
	
	publishFile();
}

function publishFile()
{
	var profileXML = document.exportPublishProfileString('Default');
	profileXML = profileXML.replace("1", "0");
	profileXML = profileXML.replace("1", "0");
	profileXML = profileXML.replace("1", "0");
	
	var findString = "";
	var startIndex = profileXML.indexOf(findString) + findString.length;
	
	findString = "";
	var endIndex = profileXML.indexOf(findString);
	
	var curName = profileXML.substring(startIndex, endIndex);
	
	var publishPath = "../swf/" + document.name.replace(".fla","");
	trace("This file is publishing to " + publishPath  + ".swf")
	profileXML = profileXML.replace(curName,publishPath);
	document.importPublishProfileString(profileXML);
	document.publish();
}

//TODO - add layer script
function addLayer()
{
	//trace("done")
}

Firstly, how could I optimise this code a bit, any suggestions would be much appreciated.

Secondly, How do I access nested elements? I have been struggling with this. I don't fully understand Iterators and have been getting errors when working through the tutorials. I have to access the elements inside the main movieclip because they are placed in the correct position. If I convert them to movieclips in the library, I would have to place them stage and check x and y positions and these differ from file to file.

As soon as I try to use the second context param, it fails, whether a string, or a library item (see code below) it fails.

Each time, all I get is a silent JS error.

function checkContents(item, index, items) {
    var collection = $('*', item);
    collection.list();
}
var objects = $$('/characters/*:movieclip');
objects.list();
objects.each(checkContents);
trace("done");

in the above example objects list() is successful, and other trace statements indicate it's dying on the $ selector (ie collection.list() never produces output. Any suggestions?

I've been trying to install with CS5 and I get an error (helpfully no output). I did some tracing and tracked the error down to for each loops, which don't seem to work. The first error I get is in xsfl.load around line 679 (I can't be sure because I've been adding traces everywhere) which is "for each(var uri in uris)". If I replace this with a normal for loop, it works.

I wrote a simple test case:

var arr = [1,2,3,4];

for each (var n in arr)

{

fl.trace(n);

}

which outputs:

1

2

3

4

function (keya, keyb) {

 var comparisonFunction = (function (a, b) {var ta = a[keya];var tb = b[keya];if (ta < tb) {return -1;}if (ta > tb) {return 1;}var tc = a[keyb];var td = b[keyb];if (tc < td) {return -1;}if (tc > td) {return 1;}return 0;});

 this.sort(comparisonFunction);

}

pretty sure this last entry is not right! Not sure what can be done about this other than to replace all the for eachs, will try a test on CS5.5 and see if it's any different.

1. The JSFL language definitions are not yet complete
2. Komodo does take a little bit of setting up

It would be REALLY helpful if you're having issues with Komodo, or you just think that something should be better, if you could post here. This will allow me to compile a master list of issues I need to look at for the final release. It doesn't matter if it's small, just let me know.

Thanks!

Dave

Looking at the docs it doesn't look like it, but for build automation purposes it would be really great ;)

I have been experimenting with iterators and , if I understand the docs, I should be able to run this script

xjsfl.init(this);
clear();

try {


    var doc = fl.openDocument("file:////mypath/myfile.fla");

    Iterators.items(true, null, processLayer, processFrame, processElement);
    doc.close(false);
}
catch (err) {
    xjsfl.debug.error(err);
}
function processLayer(layer, index, layers, context) {
    trace('> ' + layer.name);

}

function processFrame(frame, index, frames, context) {
    trace('    > ' + frame.startFrame);

}

function processElement(element, index, elements, context) {
    trace('        > ' + element.name);
}

in order to iterate through all the library elements of my source file.

First off, I had to fix what I believe is a bug in core/jsfl/libraries/flash/Context.jsfl:

diff --git a/core/jsfl/libraries/flash/Context.jsfl b/core/jsfl/libraries/flash/Context.jsfl
index e24989b..8da2662 100644
--- a/core/jsfl/libraries/flash/Context.jsfl
+++ b/core/jsfl/libraries/flash/Context.jsfl
@@ -61,15 +61,17 @@
                                if(timeline)this.setTimeline(timeline);
                                if(this.timeline)
                                {
-                                       if(layer)this.setLayer(layer);
-                                       if(this.layer.layerType !== 'folder')
-                                       {
-                                               this.setFrame(frame);
-                                               if(this.frame)
+                                       if(layer){
+                                               this.setLayer(layer);
+                                               if(this.layer.layerType !== 'folder')
                                                {
-                                                       if(element)this.setElement(element);
+                                                       this.setFrame(frame);
+                                                       if(this.frame)
+                                                       {
+                                                               if(element)this.setElement(element);
+                                                       }
                                                }
-                                       }
+                                       }       
                                }
                        }
                        return this;

because I was getting errors when this.layer was undefined and layer.layerType was tested.

With this small fix I am able to (sort of) run the Iterators.items code but I always get stuck with what I believe you guys call a silent error on the console:

The following JavaScript error(s) occurred:

that is, no exception raised, the code stops executing somewhere inside the iterator (doc.close(false) doesn't get called, nor the catch block), no debug info.

This can happen, depending on the file, right away or halfway through the library scan.

I can successully use the layers method on the same files with no issues.

At the moment I have reverted to using the old (and not so cool) library scan nested for loop found in various sample jsfl files, but it would be great if I could understand whether I'm doing something I'm not supposed to do, or whether there's a problem and I can help fix it.

Unfortunately, with no debug info and no exception raised I cannot really tell what's happening ...

I installed xJSFL. All worked fine (in Flash),  but i want to remove it and reinstall it in from a different location (folder). Removing it with the xJSFL command gave me an error (without any text). So i removed it manualy and tried to reinstall it. Somehow the snippets window has the wrong (old) links in it. So i removed and reinstalled it again. Didn't work. 

How do i remove all ? Or how do i reinstall ? I use windows 7 & Flash CS4.  

Thanks for any tips

xjsfl.utils appears to have been refactored at some point, and not all functions moved over?

The core/utils.jsfl implementation has some string functions that the one in libraries/utils.Utils.jsfl does not.

This breaks snippets like 'Propogate element names across frames" as they are looking for these functions in the latter implementation of the class. ( toCamelCase() and toUndederscore() ). Copy / pasting the relevant functions over  gets the snippet working again, but you'd be a better judge of what exactly is going on here (and what else might need to be refactored?).

cheers,

Hugh