You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Alex Harui <ah...@adobe.com> on 2016/01/14 20:33:53 UTC
[FLEXJS] POC MXML "Live" Editing
Hi,
I spend the last few days creating a proof-of-concept that FlexJS and the
Falcon compiler can support limited "live" editing of MXML. I've never
used Design View in FB, but when tweaking the UI for Flex apps, I often
find myself in a cycle of: edit some values in the mxml, save it, reload
the app, make more edits, etc. Each time, the app has to be reloaded to
see the changes. "Live" editing allows you to see certain changes without
reloading the app. The POC handles a few scenarios that involve MXML
states.
It is kind of hard to demo, but I think these are the steps:
0. Download Apache FlexJS 0.5.0 (or the 0.6.0 nightly) and install it as
an SDK in FB.
1. Download this FB project:
http://home.apache.org/~aharui/MXMLLiveEditing/DataBindingTest.fxp
2. Download this FB project:
http://home.apache.org/~aharui/MXMLLiveEditing/MXMLLiveEditAgent.fxp
3. Import both projects into FB.
4. Run MXMLLiveEditAgent.
5. In the MXMLLiveEditAgent UI, select the MyInitialView.mxml file from
the DataBindingTest project.
6. Hit the Watch button.
7. Run DataBindingTest.
8. Make and save a change to MyInitialView.mxml
When the file is saved, a few seconds later, the changes should be
reflected in DataBindingTest. This POC has a white list of properties, so
you can edit width, height, x, y, label, text and style properties. And
you can edit state-bound properties like height.showAll in the TextArea
tag.
Remember that styles in FlexJS are like HTML styles, so you can add, for
example, style="marginLeft:90" to one of the tags.
This is just for tweaking the visuals of your app. You can't edit binding
expressions or event handlers or add or remove new components. If you do
the POC will fail. A more robust version would probably detect such
changes and tell you to refresh the app. Also, if you save illegal XML,
the POC will fail. A more robust version would also watch the output SWF
to see if it changes in order to know the MXML edit didn't have syntax
errors.
The way this works is that there is a plugin added to MyInitialView that
communicates with the MXMLLiveEditAgent. The MXMLLiveEditAgent is
monitoring the last-modified date on the file. When it changes, it loads
the MXML and compares it to the last copy and transmits changes to the
plugin that applies them to the app. Certain scenarios like state-bound
properties and state-bound components can be handled in because the Falcon
compiler converts a lot of the MXML into data structures that the plugin
can find and modify. It isn't clear that you could do this in the regular
Flex SDK without finishing up Falcon compiler support in the regular Flex
SDK.
Also, none of this really requires FB. You can unzip the FXP files, build
everything yourself and edit the MXML with a text editor and it still all
works.
Future work (hopefully by other volunteers) would be to handle changes to
CSS syntax, watch multiple files at once, and swap out the LocalConnection
to use sockets so you could "live" edit an mobile app on a device, or have
an IDE communicate directly with the running app.
Anyway, let me know what you think. I'm off to work on other things.
Thanks,
-Alex
Re: [FLEXJS] POC MXML "Live" Editing
Posted by Alex Harui <ah...@adobe.com>.
On 5/12/16, 11:18 PM, "jude" <fl...@gmail.com> wrote:
>Is the MXMLLiveEditAgent.mxml the only place those methods are from? I
>thought I read somewhere that you copied those methods from somewhere
>else.
>I'm trying to find the class that those methods were originally in to
>learn
>how to parse an XML tree and then track it's changes as if a user was
>updating it constantly in an editor. I looked at the MXMLDataInterpreter
>but that looks like it's for importing.
>
>OK, I think here is where I got the idea. The comments are from
>MXMLLiveEditAgent.mxml:
>
>// we go deep first because that's how the Falcon compiler
>// generates IDs for tags that don't have id attributes set.
>
>I'm guessing that the methods are from or inspired from a class in Falcon?
>That class or code is what I'm trying to find and learn from.
>
Well, that's how we match up the IDs. We need to know how the compiler
generates the array of data that represents the MXML file. But MXML is
supposed to be valid XML, so there is no need for a custom parser, at
least for the POC. Maybe you will need more smarts later. You can look
at the Falcon MXML parser if you want, but I'm pretty sure I didn't borrow
code from there.
-Alex
Re: [FLEXJS] POC MXML "Live" Editing
Posted by Alex Harui <ah...@adobe.com>.
On 5/13/16, 7:16 AM, "jude" <fl...@gmail.com> wrote:
>Thanks. I'll look into it. I think what that's doing is working with an
>existing instance and checking for changes to it. I think I have to parse
>a
>string into a new XML instance each time and then do a compare.
Yes, that's correct. And I believe that tree comparison is an entire
field of algorithm research [1]
However, there is another approach to consider which is essentially
writing an MXML compiler in ActionScript. Maybe you don't care about the
changes, you just want to rewrite the data array that the compiler
generated and have that data re-interpreted. This option is possible
because the framework uses a data array and not actual code. So it might
be possible to read the MXML, parse it into a tree, and just walk the tree
instead of comparing it to the old tree. You would have to have some way
to track and re-use event handlers in the old array though. I think you
will also need some way to "give up" and say that the changes were too
complex and you must reload the app. The compiler could also be taught to
output extra information to help you track code.
And also consider the opposite problem: modify live and write out the
results. The POC works by having an Agent communicate with a plug-in in a
running SWF. The Agent and/or plug-in could also popup UI to highlight
components in the running app and let you tweak those values in a GUI.
Then those changes could be written to the MXML.
Lots of possibilities here. I'm glad to see that you are interested. I
hope to see something like this in an IDE someday.
-Alex
[1]
http://stackoverflow.com/questions/5894879/detect-differences-between-tree-
structures
Re: [FLEXJS] POC MXML "Live" Editing
Posted by jude <fl...@gmail.com>.
Thanks. I'll look into it. I think what that's doing is working with an
existing instance and checking for changes to it. I think I have to parse a
string into a new XML instance each time and then do a compare.
On Fri, May 13, 2016 at 2:52 AM, Harbs <ha...@gmail.com> wrote:
> Is this useful?
>
> http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/utils/XMLNotifier.html#watchXML%28%29
>
> On May 13, 2016, at 9:18 AM, jude <fl...@gmail.com> wrote:
>
> > Is the MXMLLiveEditAgent.mxml the only place those methods are from? I
> > thought I read somewhere that you copied those methods from somewhere
> else.
> > I'm trying to find the class that those methods were originally in to
> learn
> > how to parse an XML tree and then track it's changes as if a user was
> > updating it constantly in an editor. I looked at the MXMLDataInterpreter
> > but that looks like it's for importing.
> >
> > OK, I think here is where I got the idea. The comments are from
> > MXMLLiveEditAgent.mxml:
> >
> > // we go deep first because that's how the Falcon compiler
> > // generates IDs for tags that don't have id attributes set.
> >
> > I'm guessing that the methods are from or inspired from a class in
> Falcon?
> > That class or code is what I'm trying to find and learn from.
> >
> >
> > On Thu, May 12, 2016 at 11:08 PM, Alex Harui <ah...@adobe.com> wrote:
> >
> >>
> >>
> >> On 5/12/16, 5:31 PM, "jude" <fl...@gmail.com> wrote:
> >>
> >>> I read somewhere, and it might have been the code comments, that you
> used
> >>> some code from mxmlc or maybe it was an class used in Eclipse MXML
> class
> >>> to
> >>> parse the MXML and compute the changes for your live MXML PoC. I'm
> trying
> >>> to find the class that had the following functions:
> >>>
> >>> parseFile();
> >>> computeChanges();
> >>> applyChanges();
> >>
> >> In my POC, the MXMLLiveEditAgent has those methods.
> >>
> >> The MXML parsing is done by the XML class.
> >>
> >> I think you may be thinking of the MXMLDataInterpreter, and how the
> Falcon
> >> compiler outputs MXML as an array to be interpreted by the
> >> MXMLDataInterpreter (as well as the MXMLLiveEditPlugin) instead of a
> pile
> >> of one-off methods that are not manipulatable at runtime.
> >>
> >> -Alex
> >>
> >>
>
>
Re: [FLEXJS] POC MXML "Live" Editing
Posted by Harbs <ha...@gmail.com>.
Is this useful?
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/utils/XMLNotifier.html#watchXML%28%29
On May 13, 2016, at 9:18 AM, jude <fl...@gmail.com> wrote:
> Is the MXMLLiveEditAgent.mxml the only place those methods are from? I
> thought I read somewhere that you copied those methods from somewhere else.
> I'm trying to find the class that those methods were originally in to learn
> how to parse an XML tree and then track it's changes as if a user was
> updating it constantly in an editor. I looked at the MXMLDataInterpreter
> but that looks like it's for importing.
>
> OK, I think here is where I got the idea. The comments are from
> MXMLLiveEditAgent.mxml:
>
> // we go deep first because that's how the Falcon compiler
> // generates IDs for tags that don't have id attributes set.
>
> I'm guessing that the methods are from or inspired from a class in Falcon?
> That class or code is what I'm trying to find and learn from.
>
>
> On Thu, May 12, 2016 at 11:08 PM, Alex Harui <ah...@adobe.com> wrote:
>
>>
>>
>> On 5/12/16, 5:31 PM, "jude" <fl...@gmail.com> wrote:
>>
>>> I read somewhere, and it might have been the code comments, that you used
>>> some code from mxmlc or maybe it was an class used in Eclipse MXML class
>>> to
>>> parse the MXML and compute the changes for your live MXML PoC. I'm trying
>>> to find the class that had the following functions:
>>>
>>> parseFile();
>>> computeChanges();
>>> applyChanges();
>>
>> In my POC, the MXMLLiveEditAgent has those methods.
>>
>> The MXML parsing is done by the XML class.
>>
>> I think you may be thinking of the MXMLDataInterpreter, and how the Falcon
>> compiler outputs MXML as an array to be interpreted by the
>> MXMLDataInterpreter (as well as the MXMLLiveEditPlugin) instead of a pile
>> of one-off methods that are not manipulatable at runtime.
>>
>> -Alex
>>
>>
Re: [FLEXJS] POC MXML "Live" Editing
Posted by jude <fl...@gmail.com>.
Is the MXMLLiveEditAgent.mxml the only place those methods are from? I
thought I read somewhere that you copied those methods from somewhere else.
I'm trying to find the class that those methods were originally in to learn
how to parse an XML tree and then track it's changes as if a user was
updating it constantly in an editor. I looked at the MXMLDataInterpreter
but that looks like it's for importing.
OK, I think here is where I got the idea. The comments are from
MXMLLiveEditAgent.mxml:
// we go deep first because that's how the Falcon compiler
// generates IDs for tags that don't have id attributes set.
I'm guessing that the methods are from or inspired from a class in Falcon?
That class or code is what I'm trying to find and learn from.
On Thu, May 12, 2016 at 11:08 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
> On 5/12/16, 5:31 PM, "jude" <fl...@gmail.com> wrote:
>
> >I read somewhere, and it might have been the code comments, that you used
> >some code from mxmlc or maybe it was an class used in Eclipse MXML class
> >to
> >parse the MXML and compute the changes for your live MXML PoC. I'm trying
> >to find the class that had the following functions:
> >
> > parseFile();
> > computeChanges();
> > applyChanges();
>
> In my POC, the MXMLLiveEditAgent has those methods.
>
> The MXML parsing is done by the XML class.
>
> I think you may be thinking of the MXMLDataInterpreter, and how the Falcon
> compiler outputs MXML as an array to be interpreted by the
> MXMLDataInterpreter (as well as the MXMLLiveEditPlugin) instead of a pile
> of one-off methods that are not manipulatable at runtime.
>
> -Alex
>
>
Re: [FLEXJS] POC MXML "Live" Editing
Posted by Alex Harui <ah...@adobe.com>.
On 5/12/16, 5:31 PM, "jude" <fl...@gmail.com> wrote:
>I read somewhere, and it might have been the code comments, that you used
>some code from mxmlc or maybe it was an class used in Eclipse MXML class
>to
>parse the MXML and compute the changes for your live MXML PoC. I'm trying
>to find the class that had the following functions:
>
> parseFile();
> computeChanges();
> applyChanges();
In my POC, the MXMLLiveEditAgent has those methods.
The MXML parsing is done by the XML class.
I think you may be thinking of the MXMLDataInterpreter, and how the Falcon
compiler outputs MXML as an array to be interpreted by the
MXMLDataInterpreter (as well as the MXMLLiveEditPlugin) instead of a pile
of one-off methods that are not manipulatable at runtime.
-Alex
Re: [FLEXJS] POC MXML "Live" Editing
Posted by jude <fl...@gmail.com>.
I read somewhere, and it might have been the code comments, that you used
some code from mxmlc or maybe it was an class used in Eclipse MXML class to
parse the MXML and compute the changes for your live MXML PoC. I'm trying
to find the class that had the following functions:
parseFile();
computeChanges();
applyChanges();
The PoC you made works supports computing the changes for adding, modifying
and removing attributes. That make sense. Now I'm trying to figure out how
to tell if an XML element has been added or removed. I have some theories
but would like to confirm them before starting anything.
On Wed, May 11, 2016 at 9:46 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
> On 5/11/16, 5:13 PM, "jude" <fl...@gmail.com> wrote:
>
> >What is the class that you used that parses the XML? is that in the flex
> >sdk directory as plain text?
>
> Pretty sure we just use XML(String) to parse the XML. Or am I not
> understanding the question?
>
> -Alex
>
>
Re: [FLEXJS] POC MXML "Live" Editing
Posted by Alex Harui <ah...@adobe.com>.
On 5/11/16, 5:13 PM, "jude" <fl...@gmail.com> wrote:
>What is the class that you used that parses the XML? is that in the flex
>sdk directory as plain text?
Pretty sure we just use XML(String) to parse the XML. Or am I not
understanding the question?
-Alex
Re: [FLEXJS] POC MXML "Live" Editing
Posted by jude <fl...@gmail.com>.
What is the class that you used that parses the XML? is that in the flex
sdk directory as plain text?
On Jan 14, 2016 1:34 PM, "Alex Harui" <ah...@adobe.com> wrote:
> Hi,
>
> I spend the last few days creating a proof-of-concept that FlexJS and the
> Falcon compiler can support limited "live" editing of MXML. I've never
> used Design View in FB, but when tweaking the UI for Flex apps, I often
> find myself in a cycle of: edit some values in the mxml, save it, reload
> the app, make more edits, etc. Each time, the app has to be reloaded to
> see the changes. "Live" editing allows you to see certain changes without
> reloading the app. The POC handles a few scenarios that involve MXML
> states.
>
> It is kind of hard to demo, but I think these are the steps:
>
> 0. Download Apache FlexJS 0.5.0 (or the 0.6.0 nightly) and install it as
> an SDK in FB.
> 1. Download this FB project:
> http://home.apache.org/~aharui/MXMLLiveEditing/DataBindingTest.fxp
> 2. Download this FB project:
> http://home.apache.org/~aharui/MXMLLiveEditing/MXMLLiveEditAgent.fxp
>
> 3. Import both projects into FB.
> 4. Run MXMLLiveEditAgent.
> 5. In the MXMLLiveEditAgent UI, select the MyInitialView.mxml file from
> the DataBindingTest project.
> 6. Hit the Watch button.
> 7. Run DataBindingTest.
> 8. Make and save a change to MyInitialView.mxml
>
> When the file is saved, a few seconds later, the changes should be
> reflected in DataBindingTest. This POC has a white list of properties, so
> you can edit width, height, x, y, label, text and style properties. And
> you can edit state-bound properties like height.showAll in the TextArea
> tag.
>
> Remember that styles in FlexJS are like HTML styles, so you can add, for
> example, style="marginLeft:90" to one of the tags.
>
> This is just for tweaking the visuals of your app. You can't edit binding
> expressions or event handlers or add or remove new components. If you do
> the POC will fail. A more robust version would probably detect such
> changes and tell you to refresh the app. Also, if you save illegal XML,
> the POC will fail. A more robust version would also watch the output SWF
> to see if it changes in order to know the MXML edit didn't have syntax
> errors.
>
> The way this works is that there is a plugin added to MyInitialView that
> communicates with the MXMLLiveEditAgent. The MXMLLiveEditAgent is
> monitoring the last-modified date on the file. When it changes, it loads
> the MXML and compares it to the last copy and transmits changes to the
> plugin that applies them to the app. Certain scenarios like state-bound
> properties and state-bound components can be handled in because the Falcon
> compiler converts a lot of the MXML into data structures that the plugin
> can find and modify. It isn't clear that you could do this in the regular
> Flex SDK without finishing up Falcon compiler support in the regular Flex
> SDK.
>
> Also, none of this really requires FB. You can unzip the FXP files, build
> everything yourself and edit the MXML with a text editor and it still all
> works.
>
> Future work (hopefully by other volunteers) would be to handle changes to
> CSS syntax, watch multiple files at once, and swap out the LocalConnection
> to use sockets so you could "live" edit an mobile app on a device, or have
> an IDE communicate directly with the running app.
>
> Anyway, let me know what you think. I'm off to work on other things.
>
> Thanks,
> -Alex
>
>
Re: [FLEXJS] POC MXML "Live" Editing
Posted by Alex Harui <ah...@adobe.com>.
On 1/15/16, 6:23 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
<omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
>One really cool feature would be to have a website where we can invite
>users to 'try out' FlexJS. Essentially like JSFiddle, where you can type
>mxml/as3 code and see the results in the adjacent panel. Is that
>possible?
Possible? Probably.
Putting up two text areas, uploading the contents, compiling it and having
the page load it doesn't sound too hard. But I think once you get into
code-coloring, code-assistance, error reporting, etc it starts to become
real work. It would be a good dog-food test to try to create it with
FlexJS. Any volunteers?
-Alex
Re: [FLEXJS] POC MXML "Live" Editing
Posted by OmPrakash Muppirala <bi...@gmail.com>.
One really cool feature would be to have a website where we can invite
users to 'try out' FlexJS. Essentially like JSFiddle, where you can type
mxml/as3 code and see the results in the adjacent panel. Is that possible?
Thanks,
Om
On Fri, Jan 15, 2016 at 5:56 PM, OmPrakash Muppirala <bi...@gmail.com>
wrote:
> Hmm, I followed all the steps. But when I changed the width of the label
> in MyInitialView.mxml and try to save the file, I am getting this error:
>
> Could not write file:
> C:\p\flexroot\workspace\DataBindingTest\src\MyInitialView.mxml.
> C:\p\flexroot\workspace\DataBindingTest\src\MyInitialView.mxml (The
> process cannot access the file because it is being used by another process)
>
> Looks like the watch is causing this issue. When I close that AIR app, I
> am able to save the file fine.
>
> This is on Windows, btw.
>
> Thanks,
> Om
>
>
>
>
> On Fri, Jan 15, 2016 at 12:27 PM, OK <OK...@edscha.com> wrote:
>
>> Alex Harui wrote
>> > Anyway, let me know what you think. I'm off to work on other things.
>>
>> Hey Alex,
>> I've just followed your instructions and tested your POC by using FlexJS
>> 0.6.0.... and it just works!
>> Awesome, very impressive!
>> IMO a live editing feature would be a big plus. In competition to other
>> transpiling JS frameworks this could be a key feature.
>>
>> Thanks,
>> Olaf
>>
>>
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-flex-development.2333347.n4.nabble.com/FLEXJS-POC-MXML-Live-Editing-tp51278p51291.html
>> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>>
>
>
Re: [FLEXJS] POC MXML "Live" Editing
Posted by jude <fl...@gmail.com>.
Once I have some more of it decoupled I'll work on folding that code back
in. I'll provide another update when that happens.
It looks like the screenshots didn't go through. http://imgur.com/a/aKp2U
The first is codepen with html, css and js window and rendering on the
bottom. The second image is Radiate with rendering on the top and page
html, layout html and css on the bottom. The rendering area is not showing
the rendering of the html as it normally does since I'm doing a refactor.
The third image is the Live MXML Editor showing a rendering area on top and
a problems view and mxml editor on bottom.
The live editor code is here,
https://github.com/monkeypunch3/Radii8/blob/master/Radii8Desktop/src/LiveMXMLEditor.mxml.
The setup instructions are here if anyone wants to try and get it working,
https://cwiki.apache.org/confluence/display/FLEX/Setting+up+the+Radii8+Development+Environment.
Note: It looks like developers on Windows are getting a less than stellar
experience than if you run it on a Mac. In the browser it's always just
worked but I found out that Native menus are only a Mac thing so a bunch of
errors were popping up when launching it on the desktop. Hopefully, the
next update will alleviate those issues.
If you wanted you could adapt the MiniInspector
<https://github.com/monkeypunch3/flexcapacitor/blob/master/MainLibrary/src/com/flexcapacitor/utils/MiniInspector.as>
class to work with FlexJS. You add it to your project in declarations and
then at runtime when you hold down cmd and click it finds the object under
the mouse pointer. It finds the top most item in the display list and
isolates it. Then you click on the label and it gives you a property and
value text inputs. You can then change the values at runtime. Any changed
values are traced to the console so you can update your MXML as you change
values in the runtime swf. http://imgur.com/a/3ipJE
On Thu, Apr 28, 2016 at 1:44 PM, Alex Harui <ah...@adobe.com> wrote:
> Sounds very promising.
>
> It might be time to check the MXMLLIveEditing code into a repo, maybe the
> radii8 repo. That will make it easier for folks to share and help
> delineate what code has been donated to the ASF and what is intended for
> your IDE product and hasn't been donated to the ASF. You have the latest
> copy and committer rights so please do that if you agree.
>
> Thanks,
> -Alex
>
>
> From: jude <fl...@gmail.com>>
> Reply-To: "dev@flex.apache.org<ma...@flex.apache.org>" <
> dev@flex.apache.org<ma...@flex.apache.org>>
> Date: Thursday, April 28, 2016 at 7:19 AM
> To: "dev@flex.apache.org<ma...@flex.apache.org>" <dev@flex.apache.org
> <ma...@flex.apache.org>>
> Subject: Re: [FLEXJS] POC MXML "Live" Editing
>
> I've been digging into the MXML live agent and have some feedback and
> updates to some of the comments. I've been studying the examples that check
> for changes in the MXML / XML and have some progress there but it seems
> it's been built mainly for Flex JS. I'm converting some of those changes
> over to also work with Flex. I've attached a screenshot:
>
> [cid:ii_injc0ghn0_1545978fb7d04745]
>
> What I have working (some of this is old news):
> * updating the view with MXML live
> * checking if the xml is valid (i'm using an internal browser control in
> AIR to load the xml parser and get a row and line number of any errors)
> * converting a XML node into a class instance (i have dictionary of
> supported classes)
> * checking the attributes to see if they are a valid style, event or
> property
> * providing errors if they are not valid and annotations
>
> Based on your example what I have partially working is (see the
> screenshot):
> * getting the attribute that was changed (working)
> * getting the value that it was changed to (working)
> * getting the list of attributes that were removed (working)
>
> Still to do:
> * getting the instance that is related to the xml node
> * verifying that the attribute is a member of the class created from the
> xml node
> * updating just the instance instead of rerendering the document on each
> change
>
> Once I get the last few items working it's possible to make code
> completion work in the text editor. I'd also be able to provide inline
> documentation for each component and class member so new developers can
> learn as they go.
>
> Once that's working we can do the following:
>
> * make an online MXML renderer in the browser like http://codepen.io for
> testing, education and sharing
> * connect that to a list of community examples online
> * make a default html page and swf that is strictly to render MXML (no
> editor)
> * create a sort of live design rendering for IDE's based on the MXML
>
> As for a sort of http://www.jsfiddle.net / http://codepen.io<
> http://codepen.io/bengroulx/pen/QNZbZx> editor I have something like that
> working for rendering HTML / CSS editor now in Radiate and rendering MXML
> in the LiveMXMLEditor. In the screenshot you can see the MXML rendering.
> You can switch to the HTML markup below. The template, HTML markup and CSS
> is all generated from the HTMLDocumentExporter but it can be modifed in
> real time. It's then reassembled into an HTML page and passed to the
> internal browser. In the screen shot there is a live editing checkbox below
> (see screenshot) and changes are rendered live in an HTML tab (not shown
> since I'm refactoring it - centering is troublesome).
>
> [cid:ii_ink1s9k11_1545c0d84274a54d]
>
>
> Still to do is decouple the DocumentImporter classes from the Radiate.as
> class. Right now it's pulling in a lot of extra classes. The desktop
> application is around 6MB. I'm hoping to get it down to 2MB or less.
>
> After that we can make a simple application.swf with default linked in
> classes or references that will interpret the plain text MXML at runtime
> from a URL or directly from an HTML page:
>
> <html>
> <object id="mxmlRenderer" source="renderer.swf" width=100% height=100%/>
> <!-- mxml here -->
> <s:Application id="application" style="display:none">
> <s:Label text="hello world"/>
> </s:Application>
> </html>
>
> or something like:
>
> - http://www.domain.com/render_page.html?page=myApp.mxml<
> http://www.domain.com/page.html?page=myApp.mxml>
>
> where myApp.mxml is a plain text file.
>
> After that is setup anyone can make a FlexJSDocumentImporter using
> MXMLDocumentImporter as a reference and it should all just work since it
> uses reflection. You could have a sortof codepen.io<http://codepen.io>
> for FlexJS. You'd have a basic rendered view, problems view, editor with
> code completion and linked documentation.
>
> If anyone wants to help they're welcome to join in. If you don't have time
> but want to help I'm considering setting up a Patreon which would help move
> things along.
>
> This is different than the POC because that watches a file. For it to run
> in the browser we'd have to make some adjustments which is what the
> DocumentTranscoder classes are about.
>
> I'm providing this update because people on this list have asked for
> updates.
>
> Disclaimer:
> Radii8 = donated project to Apache Flex. hosted at apache
> Radiate (name subject to change) = project based on Radii8 with product
> releases, blog updates, etc. hosted at github and radii8.com<
> http://radii8.com> (domain name subject to change).
>
> FYI My goal has been to promote and build the Flash, Flex Platforms and
> web development tool chain with projects like I've described above.
>
> On Sat, Jan 16, 2016 at 9:43 AM, Alex Harui <aharui@adobe.com<mailto:
> aharui@adobe.com>> wrote:
> I made the change I suggested below and updated the fxp file at [1]. See
> if it makes things better for you. I think there is always the
> probability that at the moment the editor tries to save the file that the
> watcher will have the file locked to check its modification date, but that
> shouldn't lock the file forever. Hitting save again should save the file.
>
> It would be much more robust if an IDE/editor integrated the agent code so
> it didn't require polling. It might also be possible to write an ANE that
> watches for changes in a way that doesn't lock the file.
>
> -Alex
>
> [1] http://home.apache.org/~aharui/MXMLLiveEditing/MXMLLiveEditAgent.fxp
>
> On 1/15/16, 11:46 PM, "Alex Harui" <aharui@adobe.com<mailto:
> aharui@adobe.com>> wrote:
>
> >Worked for me on Windows 7. Maybe try slowing down the watch interval?
> >
> >If you want to dig into it more, the mxmlFile object is kept around
> >between timer events. Maybe it needs to be created in each interval so it
> >doesn't leave a lock on the file.
> >
> >Thanks,
> >-Alex
> >
> >On 1/15/16, 5:56 PM, "omuppi1@gmail.com<ma...@gmail.com> on
> behalf of OmPrakash Muppirala"
> ><om...@gmail.com> on behalf of
> bigosmallm@gmail.com<ma...@gmail.com>> wrote:
> >
> >>Hmm, I followed all the steps. But when I changed the width of the label
> >>in MyInitialView.mxml and try to save the file, I am getting this error:
> >>
> >>Could not write file:
> >>C:\p\flexroot\workspace\DataBindingTest\src\MyInitialView.mxml.
> >>C:\p\flexroot\workspace\DataBindingTest\src\MyInitialView.mxml (The
> >>process
> >>cannot access the file because it is being used by another process)
> >>
> >>Looks like the watch is causing this issue. When I close that AIR app, I
> >>am able to save the file fine.
> >>
> >>This is on Windows, btw.
> >>
> >>Thanks,
> >>Om
> >>
> >>
> >>
> >>
> >>On Fri, Jan 15, 2016 at 12:27 PM, OK <OKrueger@edscha.com<mailto:
> OKrueger@edscha.com>> wrote:
> >>
> >>> Alex Harui wrote
> >>> > Anyway, let me know what you think. I'm off to work on other things.
> >>>
> >>> Hey Alex,
> >>> I've just followed your instructions and tested your POC by using
> >>>FlexJS
> >>> 0.6.0.... and it just works!
> >>> Awesome, very impressive!
> >>> IMO a live editing feature would be a big plus. In competition to other
> >>> transpiling JS frameworks this could be a key feature.
> >>>
> >>> Thanks,
> >>> Olaf
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> View this message in context:
> >>>
> >>>
> http://apache-flex-development.2333347.n4.nabble.com/FLEXJS-POC-MXML-Liv
> >>>e
> >>>-Editing-tp51278p51291.html
> >>> Sent from the Apache Flex Development mailing list archive at
> >>>Nabble.com.
> >>>
> >
>
>
>
Re: [FLEXJS] POC MXML "Live" Editing
Posted by Alex Harui <ah...@adobe.com>.
Sounds very promising.
It might be time to check the MXMLLIveEditing code into a repo, maybe the radii8 repo. That will make it easier for folks to share and help delineate what code has been donated to the ASF and what is intended for your IDE product and hasn't been donated to the ASF. You have the latest copy and committer rights so please do that if you agree.
Thanks,
-Alex
From: jude <fl...@gmail.com>>
Reply-To: "dev@flex.apache.org<ma...@flex.apache.org>" <de...@flex.apache.org>>
Date: Thursday, April 28, 2016 at 7:19 AM
To: "dev@flex.apache.org<ma...@flex.apache.org>" <de...@flex.apache.org>>
Subject: Re: [FLEXJS] POC MXML "Live" Editing
I've been digging into the MXML live agent and have some feedback and updates to some of the comments. I've been studying the examples that check for changes in the MXML / XML and have some progress there but it seems it's been built mainly for Flex JS. I'm converting some of those changes over to also work with Flex. I've attached a screenshot:
[cid:ii_injc0ghn0_1545978fb7d04745]
What I have working (some of this is old news):
* updating the view with MXML live
* checking if the xml is valid (i'm using an internal browser control in AIR to load the xml parser and get a row and line number of any errors)
* converting a XML node into a class instance (i have dictionary of supported classes)
* checking the attributes to see if they are a valid style, event or property
* providing errors if they are not valid and annotations
Based on your example what I have partially working is (see the screenshot):
* getting the attribute that was changed (working)
* getting the value that it was changed to (working)
* getting the list of attributes that were removed (working)
Still to do:
* getting the instance that is related to the xml node
* verifying that the attribute is a member of the class created from the xml node
* updating just the instance instead of rerendering the document on each change
Once I get the last few items working it's possible to make code completion work in the text editor. I'd also be able to provide inline documentation for each component and class member so new developers can learn as they go.
Once that's working we can do the following:
* make an online MXML renderer in the browser like http://codepen.io for testing, education and sharing
* connect that to a list of community examples online
* make a default html page and swf that is strictly to render MXML (no editor)
* create a sort of live design rendering for IDE's based on the MXML
As for a sort of http://www.jsfiddle.net / http://codepen.io<http://codepen.io/bengroulx/pen/QNZbZx> editor I have something like that working for rendering HTML / CSS editor now in Radiate and rendering MXML in the LiveMXMLEditor. In the screenshot you can see the MXML rendering. You can switch to the HTML markup below. The template, HTML markup and CSS is all generated from the HTMLDocumentExporter but it can be modifed in real time. It's then reassembled into an HTML page and passed to the internal browser. In the screen shot there is a live editing checkbox below (see screenshot) and changes are rendered live in an HTML tab (not shown since I'm refactoring it - centering is troublesome).
[cid:ii_ink1s9k11_1545c0d84274a54d]
Still to do is decouple the DocumentImporter classes from the Radiate.as class. Right now it's pulling in a lot of extra classes. The desktop application is around 6MB. I'm hoping to get it down to 2MB or less.
After that we can make a simple application.swf with default linked in classes or references that will interpret the plain text MXML at runtime from a URL or directly from an HTML page:
<html>
<object id="mxmlRenderer" source="renderer.swf" width=100% height=100%/>
<!-- mxml here -->
<s:Application id="application" style="display:none">
<s:Label text="hello world"/>
</s:Application>
</html>
or something like:
- http://www.domain.com/render_page.html?page=myApp.mxml<http://www.domain.com/page.html?page=myApp.mxml>
where myApp.mxml is a plain text file.
After that is setup anyone can make a FlexJSDocumentImporter using MXMLDocumentImporter as a reference and it should all just work since it uses reflection. You could have a sortof codepen.io<http://codepen.io> for FlexJS. You'd have a basic rendered view, problems view, editor with code completion and linked documentation.
If anyone wants to help they're welcome to join in. If you don't have time but want to help I'm considering setting up a Patreon which would help move things along.
This is different than the POC because that watches a file. For it to run in the browser we'd have to make some adjustments which is what the DocumentTranscoder classes are about.
I'm providing this update because people on this list have asked for updates.
Disclaimer:
Radii8 = donated project to Apache Flex. hosted at apache
Radiate (name subject to change) = project based on Radii8 with product releases, blog updates, etc. hosted at github and radii8.com<http://radii8.com> (domain name subject to change).
FYI My goal has been to promote and build the Flash, Flex Platforms and web development tool chain with projects like I've described above.
On Sat, Jan 16, 2016 at 9:43 AM, Alex Harui <ah...@adobe.com>> wrote:
I made the change I suggested below and updated the fxp file at [1]. See
if it makes things better for you. I think there is always the
probability that at the moment the editor tries to save the file that the
watcher will have the file locked to check its modification date, but that
shouldn't lock the file forever. Hitting save again should save the file.
It would be much more robust if an IDE/editor integrated the agent code so
it didn't require polling. It might also be possible to write an ANE that
watches for changes in a way that doesn't lock the file.
-Alex
[1] http://home.apache.org/~aharui/MXMLLiveEditing/MXMLLiveEditAgent.fxp
On 1/15/16, 11:46 PM, "Alex Harui" <ah...@adobe.com>> wrote:
>Worked for me on Windows 7. Maybe try slowing down the watch interval?
>
>If you want to dig into it more, the mxmlFile object is kept around
>between timer events. Maybe it needs to be created in each interval so it
>doesn't leave a lock on the file.
>
>Thanks,
>-Alex
>
>On 1/15/16, 5:56 PM, "omuppi1@gmail.com<ma...@gmail.com> on behalf of OmPrakash Muppirala"
><om...@gmail.com> on behalf of bigosmallm@gmail.com<ma...@gmail.com>> wrote:
>
>>Hmm, I followed all the steps. But when I changed the width of the label
>>in MyInitialView.mxml and try to save the file, I am getting this error:
>>
>>Could not write file:
>>C:\p\flexroot\workspace\DataBindingTest\src\MyInitialView.mxml.
>>C:\p\flexroot\workspace\DataBindingTest\src\MyInitialView.mxml (The
>>process
>>cannot access the file because it is being used by another process)
>>
>>Looks like the watch is causing this issue. When I close that AIR app, I
>>am able to save the file fine.
>>
>>This is on Windows, btw.
>>
>>Thanks,
>>Om
>>
>>
>>
>>
>>On Fri, Jan 15, 2016 at 12:27 PM, OK <OK...@edscha.com>> wrote:
>>
>>> Alex Harui wrote
>>> > Anyway, let me know what you think. I'm off to work on other things.
>>>
>>> Hey Alex,
>>> I've just followed your instructions and tested your POC by using
>>>FlexJS
>>> 0.6.0.... and it just works!
>>> Awesome, very impressive!
>>> IMO a live editing feature would be a big plus. In competition to other
>>> transpiling JS frameworks this could be a key feature.
>>>
>>> Thanks,
>>> Olaf
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>>
>>>http://apache-flex-development.2333347.n4.nabble.com/FLEXJS-POC-MXML-Liv
>>>e
>>>-Editing-tp51278p51291.html
>>> Sent from the Apache Flex Development mailing list archive at
>>>Nabble.com.
>>>
>
Re: [FLEXJS] POC MXML "Live" Editing
Posted by jude <fl...@gmail.com>.
I've been digging into the MXML live agent and have some feedback and
updates to some of the comments. I've been studying the examples that check
for changes in the MXML / XML and have some progress there but it seems
it's been built mainly for Flex JS. I'm converting some of those changes
over to also work with Flex. I've attached a screenshot:
What I have working (some of this is old news):
* updating the view with MXML live
* checking if the xml is valid (i'm using an internal browser control in
AIR to load the xml parser and get a row and line number of any errors)
* converting a XML node into a class instance (i have dictionary of
supported classes)
* checking the attributes to see if they are a valid style, event or
property
* providing errors if they are not valid and annotations
Based on your example what I have partially working is (see the
screenshot):
* getting the attribute that was changed (working)
* getting the value that it was changed to (working)
* getting the list of attributes that were removed (working)
Still to do:
* getting the instance that is related to the xml node
* verifying that the attribute is a member of the class created from the
xml node
* updating just the instance instead of rerendering the document on each
change
Once I get the last few items working it's possible to make code completion
work in the text editor. I'd also be able to provide inline documentation
for each component and class member so new developers can learn as they go.
Once that's working we can do the following:
* make an online MXML renderer in the browser like http://codepen.io for
testing, education and sharing
* connect that to a list of community examples online
* make a default html page and swf that is strictly to render MXML (no
editor)
* create a sort of live design rendering for IDE's based on the MXML
As for a sort of http://www.jsfiddle.net / http://codepen.io
<http://codepen.io/bengroulx/pen/QNZbZx> editor I have something like that
working for rendering HTML / CSS editor now in Radiate and rendering MXML
in the LiveMXMLEditor. In the screenshot you can see the MXML rendering.
You can switch to the HTML markup below. The template, HTML markup and CSS
is all generated from the HTMLDocumentExporter but it can be modifed in
real time. It's then reassembled into an HTML page and passed to the
internal browser. In the screen shot there is a live editing checkbox below
(see screenshot) and changes are rendered live in an HTML tab (not shown
since I'm refactoring it - centering is troublesome).
Still to do is decouple the DocumentImporter classes from the Radiate.as
class. Right now it's pulling in a lot of extra classes. The desktop
application is around 6MB. I'm hoping to get it down to 2MB or less.
After that we can make a simple application.swf with default linked in
classes or references that will interpret the plain text MXML at runtime
from a URL or directly from an HTML page:
<html>
<object id="mxmlRenderer" source="renderer.swf" width=100% height=100%/>
<!-- mxml here -->
<s:Application id="application" style="display:none">
<s:Label text="hello world"/>
</s:Application>
</html>
or something like:
- http://www.domain.com/render_page.html?page=myApp.mxml
<http://www.domain.com/page.html?page=myApp.mxml>
where myApp.mxml is a plain text file.
After that is setup anyone can make a FlexJSDocumentImporter using
MXMLDocumentImporter as a reference and it should all just work since it
uses reflection. You could have a sortof codepen.io for FlexJS. You'd have
a basic rendered view, problems view, editor with code completion and
linked documentation.
If anyone wants to help they're welcome to join in. If you don't have time
but want to help I'm considering setting up a Patreon which would help move
things along.
This is different than the POC because that watches a file. For it to run
in the browser we'd have to make some adjustments which is what the
DocumentTranscoder classes are about.
I'm providing this update because people on this list have asked for
updates.
Disclaimer:
Radii8 = donated project to Apache Flex. hosted at apache
Radiate (name subject to change) = project based on Radii8 with product
releases, blog updates, etc. hosted at github and radii8.com (domain name
subject to change).
FYI My goal has been to promote and build the Flash, Flex Platforms and web
development tool chain with projects like I've described above.
On Sat, Jan 16, 2016 at 9:43 AM, Alex Harui <ah...@adobe.com> wrote:
> I made the change I suggested below and updated the fxp file at [1]. See
> if it makes things better for you. I think there is always the
> probability that at the moment the editor tries to save the file that the
> watcher will have the file locked to check its modification date, but that
> shouldn't lock the file forever. Hitting save again should save the file.
>
> It would be much more robust if an IDE/editor integrated the agent code so
> it didn't require polling. It might also be possible to write an ANE that
> watches for changes in a way that doesn't lock the file.
>
> -Alex
>
> [1] http://home.apache.org/~aharui/MXMLLiveEditing/MXMLLiveEditAgent.fxp
>
> On 1/15/16, 11:46 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
> >Worked for me on Windows 7. Maybe try slowing down the watch interval?
> >
> >If you want to dig into it more, the mxmlFile object is kept around
> >between timer events. Maybe it needs to be created in each interval so it
> >doesn't leave a lock on the file.
> >
> >Thanks,
> >-Alex
> >
> >On 1/15/16, 5:56 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
> ><omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
> >
> >>Hmm, I followed all the steps. But when I changed the width of the label
> >>in MyInitialView.mxml and try to save the file, I am getting this error:
> >>
> >>Could not write file:
> >>C:\p\flexroot\workspace\DataBindingTest\src\MyInitialView.mxml.
> >>C:\p\flexroot\workspace\DataBindingTest\src\MyInitialView.mxml (The
> >>process
> >>cannot access the file because it is being used by another process)
> >>
> >>Looks like the watch is causing this issue. When I close that AIR app, I
> >>am able to save the file fine.
> >>
> >>This is on Windows, btw.
> >>
> >>Thanks,
> >>Om
> >>
> >>
> >>
> >>
> >>On Fri, Jan 15, 2016 at 12:27 PM, OK <OK...@edscha.com> wrote:
> >>
> >>> Alex Harui wrote
> >>> > Anyway, let me know what you think. I'm off to work on other things.
> >>>
> >>> Hey Alex,
> >>> I've just followed your instructions and tested your POC by using
> >>>FlexJS
> >>> 0.6.0.... and it just works!
> >>> Awesome, very impressive!
> >>> IMO a live editing feature would be a big plus. In competition to other
> >>> transpiling JS frameworks this could be a key feature.
> >>>
> >>> Thanks,
> >>> Olaf
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> View this message in context:
> >>>
> >>>
> http://apache-flex-development.2333347.n4.nabble.com/FLEXJS-POC-MXML-Liv
> >>>e
> >>>-Editing-tp51278p51291.html
> >>> Sent from the Apache Flex Development mailing list archive at
> >>>Nabble.com.
> >>>
> >
>
>
Re: [FLEXJS] POC MXML "Live" Editing
Posted by Alex Harui <ah...@adobe.com>.
I made the change I suggested below and updated the fxp file at [1]. See
if it makes things better for you. I think there is always the
probability that at the moment the editor tries to save the file that the
watcher will have the file locked to check its modification date, but that
shouldn't lock the file forever. Hitting save again should save the file.
It would be much more robust if an IDE/editor integrated the agent code so
it didn't require polling. It might also be possible to write an ANE that
watches for changes in a way that doesn't lock the file.
-Alex
[1] http://home.apache.org/~aharui/MXMLLiveEditing/MXMLLiveEditAgent.fxp
On 1/15/16, 11:46 PM, "Alex Harui" <ah...@adobe.com> wrote:
>Worked for me on Windows 7. Maybe try slowing down the watch interval?
>
>If you want to dig into it more, the mxmlFile object is kept around
>between timer events. Maybe it needs to be created in each interval so it
>doesn't leave a lock on the file.
>
>Thanks,
>-Alex
>
>On 1/15/16, 5:56 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
><omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
>
>>Hmm, I followed all the steps. But when I changed the width of the label
>>in MyInitialView.mxml and try to save the file, I am getting this error:
>>
>>Could not write file:
>>C:\p\flexroot\workspace\DataBindingTest\src\MyInitialView.mxml.
>>C:\p\flexroot\workspace\DataBindingTest\src\MyInitialView.mxml (The
>>process
>>cannot access the file because it is being used by another process)
>>
>>Looks like the watch is causing this issue. When I close that AIR app, I
>>am able to save the file fine.
>>
>>This is on Windows, btw.
>>
>>Thanks,
>>Om
>>
>>
>>
>>
>>On Fri, Jan 15, 2016 at 12:27 PM, OK <OK...@edscha.com> wrote:
>>
>>> Alex Harui wrote
>>> > Anyway, let me know what you think. I'm off to work on other things.
>>>
>>> Hey Alex,
>>> I've just followed your instructions and tested your POC by using
>>>FlexJS
>>> 0.6.0.... and it just works!
>>> Awesome, very impressive!
>>> IMO a live editing feature would be a big plus. In competition to other
>>> transpiling JS frameworks this could be a key feature.
>>>
>>> Thanks,
>>> Olaf
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>>
>>>http://apache-flex-development.2333347.n4.nabble.com/FLEXJS-POC-MXML-Liv
>>>e
>>>-Editing-tp51278p51291.html
>>> Sent from the Apache Flex Development mailing list archive at
>>>Nabble.com.
>>>
>
Re: [FLEXJS] POC MXML "Live" Editing
Posted by Alex Harui <ah...@adobe.com>.
Worked for me on Windows 7. Maybe try slowing down the watch interval?
If you want to dig into it more, the mxmlFile object is kept around
between timer events. Maybe it needs to be created in each interval so it
doesn't leave a lock on the file.
Thanks,
-Alex
On 1/15/16, 5:56 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
<omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
>Hmm, I followed all the steps. But when I changed the width of the label
>in MyInitialView.mxml and try to save the file, I am getting this error:
>
>Could not write file:
>C:\p\flexroot\workspace\DataBindingTest\src\MyInitialView.mxml.
>C:\p\flexroot\workspace\DataBindingTest\src\MyInitialView.mxml (The
>process
>cannot access the file because it is being used by another process)
>
>Looks like the watch is causing this issue. When I close that AIR app, I
>am able to save the file fine.
>
>This is on Windows, btw.
>
>Thanks,
>Om
>
>
>
>
>On Fri, Jan 15, 2016 at 12:27 PM, OK <OK...@edscha.com> wrote:
>
>> Alex Harui wrote
>> > Anyway, let me know what you think. I'm off to work on other things.
>>
>> Hey Alex,
>> I've just followed your instructions and tested your POC by using FlexJS
>> 0.6.0.... and it just works!
>> Awesome, very impressive!
>> IMO a live editing feature would be a big plus. In competition to other
>> transpiling JS frameworks this could be a key feature.
>>
>> Thanks,
>> Olaf
>>
>>
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>>
>>http://apache-flex-development.2333347.n4.nabble.com/FLEXJS-POC-MXML-Live
>>-Editing-tp51278p51291.html
>> Sent from the Apache Flex Development mailing list archive at
>>Nabble.com.
>>
Re: [FLEXJS] POC MXML "Live" Editing
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Hmm, I followed all the steps. But when I changed the width of the label
in MyInitialView.mxml and try to save the file, I am getting this error:
Could not write file:
C:\p\flexroot\workspace\DataBindingTest\src\MyInitialView.mxml.
C:\p\flexroot\workspace\DataBindingTest\src\MyInitialView.mxml (The process
cannot access the file because it is being used by another process)
Looks like the watch is causing this issue. When I close that AIR app, I
am able to save the file fine.
This is on Windows, btw.
Thanks,
Om
On Fri, Jan 15, 2016 at 12:27 PM, OK <OK...@edscha.com> wrote:
> Alex Harui wrote
> > Anyway, let me know what you think. I'm off to work on other things.
>
> Hey Alex,
> I've just followed your instructions and tested your POC by using FlexJS
> 0.6.0.... and it just works!
> Awesome, very impressive!
> IMO a live editing feature would be a big plus. In competition to other
> transpiling JS frameworks this could be a key feature.
>
> Thanks,
> Olaf
>
>
>
>
>
>
>
> --
> View this message in context:
> http://apache-flex-development.2333347.n4.nabble.com/FLEXJS-POC-MXML-Live-Editing-tp51278p51291.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
Re: [FLEXJS] POC MXML "Live" Editing
Posted by OK <OK...@edscha.com>.
Alex Harui wrote
> Anyway, let me know what you think. I'm off to work on other things.
Hey Alex,
I've just followed your instructions and tested your POC by using FlexJS
0.6.0.... and it just works!
Awesome, very impressive!
IMO a live editing feature would be a big plus. In competition to other
transpiling JS frameworks this could be a key feature.
Thanks,
Olaf
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/FLEXJS-POC-MXML-Live-Editing-tp51278p51291.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.