You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Martin Heidegger <mh...@leichtgewicht.at> on 2012/03/10 10:04:31 UTC
[Wiki] Code conventions
Hello Adobe team,
I was planning to copy the code conventions of the Adobe wiki to the
Apache wiki so we can start extending/finishing it. I was wondering
about the legal implications.
any thoughts?
yours
Martin.
Re: Haxe and Flex
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Mon, Mar 12, 2012 at 1:03 PM, James Cowan <ja...@googlemail.com> wrote:
> ...Perhaps if anyone else is interested, they could drop me an email and we
> could have a (skype) chat?...
Feel free to discuss this here, any technical discussions related to
Flex are welcome here, and exposing them might help in getting more
people interested.
-Bertrand
Re: Haxe and Flex
Posted by Niel Drummond <ni...@grumpytoad.org>.
The topic was discussed a little, but it seemed to me that the general
feeling was "as3 is not haxe", and "let's wait and see what adobe
hands us on a plate".
I am definitely interested in such a project, but it's still an idea
that needs some traction in the community, or it will have some
difficulty finishing.
- Niel
On 13/03/2012, James Cowan <ja...@googlemail.com> wrote:
>
> MXML/AS3/Flex are conceptually identical to XAML/C#/WPF. They borrow a
> lot of ideas from previous XML UI technologies.
> MXML/haXe/Flex does sound quite viable.
>
> The issue is that both Silverlight and Flash are dieing and haXe
> represents a future for Flex because it is clever cross compiler
> technology that targets lots of platforms - native o/s including mobile
> via nme/cpp, vm via neko, browser via js and swf and in time java/c#.
>
> The problem with haXe is that a language/compiler is only a part of a
> development environment - libraries/frameworks for persistence and GUI
> are as important. If I could develop in haXe and use a haXe enabled Flex
> as my GUI framework and a haXe enabled ORM (on the lines of
> JPA/Hibernate) as my persistence framework and then could target
> desktop/javascript/swf/mobile from the same code base, that would be
> awesome.
>
> It may be a pipe dream if every library has to be rewritten at the
> source level and I can understand anyone baulking at that. I will ask
> Nicolas
> if there might be a way of interfacing Flex or say Hibernate (when the
> java target is ready) without rewrite at source level. I imagine he will
> point at the migration tools and say that once the migration from AS3 to
> haXe is done, one would dump the AS3 code.
>
> I live in the town where "Flash on the Beach" had its last year - there
> was a big local Flash community but now it has moved on to Javascript
> (with canvas)
> and to mobile and they are much more interested in
> HaXe/Corona/Titanium/Marmalade than Flex/Air mobile.
>
> Java/Swing failed on the desktop and the browser (applets) mainly
> because of runtime issues (and competition from Microsoft/Apple) and I
> would be sorry to see Flex die because the runtime (Flash) died under it.
>
> I would certainly see a future for Flex on Flash/Air technology if Adobe
> donated the defunct Air for Linux to Apache and Apple issued a statement
> embracing it
> on OSX but I do not see this happening soon.
>
> James
>
>
> On 12/03/2012 20:10, Martin Heidegger wrote:
>> To be honest: if I would have to write a framework for haXe I would
>> focus it on other things than I do in AS3.
>> AS3 is not a perfect language (by a long shot) but in Flex MXML is a
>> key concept and it does take some time to implement a hxml of
>> the same logic, same goes for quite a few other aspects (that now
>> "just work"). I am not opposed to that but like I said before:
>> I wouldn't call that Flex because it most likely will not resemble
>> Flex a lot.
>>
>> yours
>> Martin.
>>
>>
>> On 13/03/2012 04:56, James Cowan wrote:
>>> haXe's ability to compiled to many targets (native cpp, java/c#,
>>> javascript, as3/swf and neko vm) does make it very attractive
>>> and it is open source.
>>>
>>> I noticed that ASwing (the port of Java Swing to AS3) is making the
>>> plunge and moving to haXe to take advantage of the cpp
>>> target: http://www.aswing.org/?cat=26.
>>>
>>> I did not get a sense from looking at the thread that there was much
>>> enthusiasm for moving from AS3 to haXe and not porting
>>> to haXe would mean 2 code bases which does not sound ideal.
>>>
>>> James
>>
>>
>
>
--
Sent from my mobile device
Re: Haxe and Flex
Posted by Left Right <ol...@gmail.com>.
Niel,
I've tried to bootstrap the framework once, but I've reduced it to the
minimum required to support MXML (so no visual components, collections
etc), only bindings + some other stuff I wasn't able to remove. It would be
all in all about 30 classes. So, if you are interested, I could give it a
try, but there's one important thing about it: current Flex compiler
expects the AS3 classes to be in place, either as sources, or in the
framework.swc (probably, it would be able to take them from another swc -
that's something I didn't try), but if they aren't found, it'll replace
them with the ones it "knows" to exist. So it would be quite difficult to
compile in parallel and see if the results match.
Another thing: what I could understand from Michael and Alex is that the
way the code used to be generated is going to change - and we don't know in
what way. Those classes depend on the generated code to work properly (they
are usually instantiated from the generated code).
Also, so far I could understand, no one is planning serious changes until
Adobe releases the last stable version - until then it's kind of pointless
to try to make changes, because we have a good chance to get out of sync.
Yet on the other hand, the new compiler is going to compile MXML directly
(why is that is another question... but I'm not asking it). And this later
fact is putting anyone who would think about circumventing AS3 generated
behind MXML into a very problematic position, as they would also need to
generate the same code from MXML... I actually have difficult times
understanding the ways the new compiler is going to be used - will it
replace authoring_asc.jar for Flash CS? If so, I'm kind of lost, because
there's a lot of technology built already on top of it, especially
technology that involves code generation, use of AS3 compiled libraries and
so on. So, how would Adobe continue to plan their own development in sync
with Apache? I'm not saying it's impossible, but sounds strange...
Best.
Oleg
Re: Haxe and Flex
Posted by Sanford Redlich <si...@gmail.com>.
I'll put something together. I'm on a rush job right now but hopefully I
can do it next week. - S.
On 3/26/2012 1:45 AM, Carlos Rovira wrote:
> Hi Sandford,
>
> there's some link to see demos or code of waht you are commenting?
>
> Thanks
>
> C.
>
> 2012/3/26 Sanford Redlich<si...@gmail.com>
>
>> Hi Oleg,
>>
>> I've developed a set of CSS-styleable base components based on
>> SpriteVisualElement that might help this effort. It's based on a demo
>> system by Nahuel Faronda.
>>
>> It was intended to speed up Flex mobile apps, which it does, actually.
>>
>> Would that help?
>>
>> Cheers,
>>
>>
>> Sanford
>>
>>
>> On 3/21/2012 1:30 AM, Left Right wrote:
>>
>>> Hi, sorry for the late response. I found the class I was thinking about,
>>> it's spark.core.**SpriteVisualElement. It's not as small as I hoped, but
>>> it's
>>> way much smaller then UIComponent, and it's possible to use it as a base
>>> class for Flex components, so, it may be a good target for a PoC. It has
>>> an
>>> added value of a class that potentially can host FXG graphics, not sure
>>> what it gives us though... The class is about 3K loc big + has some
>>> dependencies, however, the dependencies should be easy to bootstrap, for
>>> example the dependency to IUIComponent is through some
>>> IUIComponent-specific add-child routine, which can be removed entirely
>>> with
>>> no harm to the component (as it's not going to be used in connection to
>>> UIComponent for the test purposes anyway).
>>>
>>> Best.
>>>
>>> Oleg
>>>
>>>
>
Re: Haxe and Flex
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Sandford,
there's some link to see demos or code of waht you are commenting?
Thanks
C.
2012/3/26 Sanford Redlich <si...@gmail.com>
> Hi Oleg,
>
> I've developed a set of CSS-styleable base components based on
> SpriteVisualElement that might help this effort. It's based on a demo
> system by Nahuel Faronda.
>
> It was intended to speed up Flex mobile apps, which it does, actually.
>
> Would that help?
>
> Cheers,
>
>
> Sanford
>
>
> On 3/21/2012 1:30 AM, Left Right wrote:
>
>> Hi, sorry for the late response. I found the class I was thinking about,
>> it's spark.core.**SpriteVisualElement. It's not as small as I hoped, but
>> it's
>> way much smaller then UIComponent, and it's possible to use it as a base
>> class for Flex components, so, it may be a good target for a PoC. It has
>> an
>> added value of a class that potentially can host FXG graphics, not sure
>> what it gives us though... The class is about 3K loc big + has some
>> dependencies, however, the dependencies should be easy to bootstrap, for
>> example the dependency to IUIComponent is through some
>> IUIComponent-specific add-child routine, which can be removed entirely
>> with
>> no harm to the component (as it's not going to be used in connection to
>> UIComponent for the test purposes anyway).
>>
>> Best.
>>
>> Oleg
>>
>>
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 35 57 77
<http://www.codeoscopic.com>
CODEOSCOPIC S.A. <http://www.codeoscopic.com>
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid
Re: Haxe and Flex
Posted by Sanford Redlich <si...@gmail.com>.
Hi Oleg,
I've developed a set of CSS-styleable base components based on
SpriteVisualElement that might help this effort. It's based on a demo
system by Nahuel Faronda.
It was intended to speed up Flex mobile apps, which it does, actually.
Would that help?
Cheers,
Sanford
On 3/21/2012 1:30 AM, Left Right wrote:
> Hi, sorry for the late response. I found the class I was thinking about,
> it's spark.core.SpriteVisualElement. It's not as small as I hoped, but it's
> way much smaller then UIComponent, and it's possible to use it as a base
> class for Flex components, so, it may be a good target for a PoC. It has an
> added value of a class that potentially can host FXG graphics, not sure
> what it gives us though... The class is about 3K loc big + has some
> dependencies, however, the dependencies should be easy to bootstrap, for
> example the dependency to IUIComponent is through some
> IUIComponent-specific add-child routine, which can be removed entirely with
> no harm to the component (as it's not going to be used in connection to
> UIComponent for the test purposes anyway).
>
> Best.
>
> Oleg
>
Re: Haxe and Flex
Posted by Left Right <ol...@gmail.com>.
Hi, sorry for the late response. I found the class I was thinking about,
it's spark.core.SpriteVisualElement. It's not as small as I hoped, but it's
way much smaller then UIComponent, and it's possible to use it as a base
class for Flex components, so, it may be a good target for a PoC. It has an
added value of a class that potentially can host FXG graphics, not sure
what it gives us though... The class is about 3K loc big + has some
dependencies, however, the dependencies should be easy to bootstrap, for
example the dependency to IUIComponent is through some
IUIComponent-specific add-child routine, which can be removed entirely with
no harm to the component (as it's not going to be used in connection to
UIComponent for the test purposes anyway).
Best.
Oleg
Re: Haxe and Flex
Posted by Left Right <ol...@gmail.com>.
I tried once to use some spark components with very reduced functionality
for the purpose of using GFX - that's why I mentioned it. I *hope* that
there may be a way do build a PoC using some Spark interfaces masking
alternative smaller implementations.
However, I fell victim to Ubuntu update %) and after a week of crazy
efforts of restoring my system to operational state, I moved to Debian -
but I've got bare bones only for now, so I'll probably try to restore what
I could have saved from my last file system and programs... I hope I'll
find the time to look into Spark sources to try to find that interface I
had in mind, but I can't promise.
Cheers!
Oleg
Re: Haxe and Flex
Posted by ganaraj p r <ga...@gmail.com>.
Would seriously love to get started with porting Flex onto Haxe. That is
something I prize most of all the changes.
Flex was known for being the best single RIA tool in the market for a long
time. Now over the past months it is losing its glitter. Perhaps porting it
to Haxe and making it truly cross compile into different languages ( and
efficiently ! ) should give it a traction that it deserves. This will also
ensure that finally Haxe will get its critical mass of subscribers.
If there is someone here who has delved into Flex code and figured out
independent modules or systems that can be ported, It would be really
great. Lets get started guys!!!!
On Wed, Mar 14, 2012 at 5:06 AM, James Ong <ya...@gmail.com> wrote:
> It will be ideal if there a way to interface any DLL from as3 code when
> cross compile to c or cpp, this will attract developers who are using QT
> On Mar 14, 2012 6:42 AM, "Arnoud Bos" <ar...@artim-interactive.nl> wrote:
>
> >
> > On Mar 13, 2012, at 10:07 PM, Niel Drummond wrote:
> >
> > >
> > > Regarding Arnoud Bos' suggestion of using as3hx, this might be a
> > solution,
> > > if (and only if) it's desired to keep as3 as-is, but I doubt it will
> be a
> > > satisfactory solution, because I suspect eventually flex will want to
> > > migrate some of it's components to pure HTML equivalents, which is
> > > difficult to do purely on an NME basis.
> >
> > Hi Neil, yeah i just came up with a possible approach. For sure it's not
> > the best.
> > I think you have much deeper understanding on how to do this stuff
> better.
> > I'm just learning haxe and enjoying it very much.
> >
> > It would be nice to know how you would approach it as you have much
> deeper
> > understanding of haxe and mapping on a Js/HTML target.
> >
> > Oleg's suggestion to use his minimum set as a starting point could be a
> > nice.
> >
> > Arnoud
> >
> > > [1]
> > http://lists.motion-twin.com/pipermail/haxe/2008-November/020644.html
> > >
> > > - Niel
> >
> >
> >
> >
>
--
Regards,
Ganaraj P R
Re: Haxe and Flex
Posted by James Ong <ya...@gmail.com>.
It will be ideal if there a way to interface any DLL from as3 code when
cross compile to c or cpp, this will attract developers who are using QT
On Mar 14, 2012 6:42 AM, "Arnoud Bos" <ar...@artim-interactive.nl> wrote:
>
> On Mar 13, 2012, at 10:07 PM, Niel Drummond wrote:
>
> >
> > Regarding Arnoud Bos' suggestion of using as3hx, this might be a
> solution,
> > if (and only if) it's desired to keep as3 as-is, but I doubt it will be a
> > satisfactory solution, because I suspect eventually flex will want to
> > migrate some of it's components to pure HTML equivalents, which is
> > difficult to do purely on an NME basis.
>
> Hi Neil, yeah i just came up with a possible approach. For sure it's not
> the best.
> I think you have much deeper understanding on how to do this stuff better.
> I'm just learning haxe and enjoying it very much.
>
> It would be nice to know how you would approach it as you have much deeper
> understanding of haxe and mapping on a Js/HTML target.
>
> Oleg's suggestion to use his minimum set as a starting point could be a
> nice.
>
> Arnoud
>
> > [1]
> http://lists.motion-twin.com/pipermail/haxe/2008-November/020644.html
> >
> > - Niel
>
>
>
>
Re: Haxe and Flex
Posted by Arnoud Bos <ar...@artim-interactive.nl>.
On Mar 13, 2012, at 10:07 PM, Niel Drummond wrote:
>
> Regarding Arnoud Bos' suggestion of using as3hx, this might be a solution,
> if (and only if) it's desired to keep as3 as-is, but I doubt it will be a
> satisfactory solution, because I suspect eventually flex will want to
> migrate some of it's components to pure HTML equivalents, which is
> difficult to do purely on an NME basis.
Hi Neil, yeah i just came up with a possible approach. For sure it's not the best.
I think you have much deeper understanding on how to do this stuff better.
I'm just learning haxe and enjoying it very much.
It would be nice to know how you would approach it as you have much deeper
understanding of haxe and mapping on a Js/HTML target.
Oleg's suggestion to use his minimum set as a starting point could be a nice.
Arnoud
> [1] http://lists.motion-twin.com/pipermail/haxe/2008-November/020644.html
>
> - Niel
Re: Haxe and Flex
Posted by Niel Drummond <ni...@grumpytoad.org>.
I think if some work were to go into this, it would be a great primer for
the issues around targeting javascript/HTML regardless of which compiler is
used. Many issues that were raised in the "porting to haxe" threads
revolved around generic issues that would need to be dealt with regardless
of whether falconJS or a separate custom compiler is used instead. I think
this puts haxe into a bad light, and offsets the problems the flex
community will have further down the road, when it's finally decided to put
some work into cross-compiling.
Nicolas didn't mention how haxe can be used from AS3/flex with minimal
work, because that's only possible over the flash runtime, which is only a
great reason if you wish to interface with flex from the haxe source code
(so the other way around).
>From my point of view, being a little bit naive about flex, and having
plenty of experience cross-compiling flash->js code with haxe (my first
demo was end 2008 [1]), looking at the flex code is quite intimidating at
first, and it would take me a considerable amount of time to find a
starting point. It would make it hugely more approachable if a tiny cross
section of core classes + one independent component were identified from
another expert as a potential candidate for a POC, ignoring any parsers,
ignoring tooling and most importantly not dependent on other parts of the
infrastructure.
Regarding Arnoud Bos' suggestion of using as3hx, this might be a solution,
if (and only if) it's desired to keep as3 as-is, but I doubt it will be a
satisfactory solution, because I suspect eventually flex will want to
migrate some of it's components to pure HTML equivalents, which is
difficult to do purely on an NME basis.
[1] http://lists.motion-twin.com/pipermail/haxe/2008-November/020644.html
- Niel
On Tue, Mar 13, 2012 at 4:23 PM, Michael A. Labriola <
labriola@digitalprimates.net> wrote:
> >Hasn't the MXMLC Flex compiler been open source since version 3?
>
> No, not really. If you look at the licenses (which are contradictory in
> some cases) the modules directory containing the compiler source *may* have
> been Adobe license and not Mozilla so we may not have the right to
> redistribute. This is one of the long-ish battles Spoon was fighting as we
> wanted to modify this source.
>
> Mike
>
>
RE: Haxe and Flex
Posted by "Michael A. Labriola" <la...@digitalprimates.net>.
>Hasn't the MXMLC Flex compiler been open source since version 3?
No, not really. If you look at the licenses (which are contradictory in some cases) the modules directory containing the compiler source *may* have been Adobe license and not Mozilla so we may not have the right to redistribute. This is one of the long-ish battles Spoon was fighting as we wanted to modify this source.
Mike
Re: Haxe and Flex
Posted by Jeffry Houser <je...@dot-com-it.com>.
On 3/13/2012 10:22 AM, James Cowan wrote:
>
> that is a good summary and yes it sounds like a massive amount of work.
>
> I have never seen an open source MXML compiler but I have seen XAML
> open source compilers.
Hasn't the MXMLC Flex compiler been open source since version 3?
--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust
Re: Haxe and Flex
Posted by James Cowan <ja...@googlemail.com>.
that is a good summary and yes it sounds like a massive amount of work.
I have never seen an open source MXML compiler but I have seen XAML open
source compilers.
extras/mxml.xsd seems to have disappeared but this project
(http://code.google.com/p/xsd4mxml/) seems to be useful.
James
On 13/03/2012 14:01, Arnoud Bos wrote:
> On Mar 13, 2012, at 1:17 PM, James Cowan wrote:
>
>> MXML/AS3/Flex are conceptually identical to XAML/C#/WPF. They borrow a lot of ideas from previous XML UI technologies.
>> MXML/haXe/Flex does sound quite viable.
> Sure, it could be done. But i guess someone should be willing to port the actionscript code.
> A mapping on haxe-nme should be possible as it implements the flash displaylist.
>
> some challenges here:
> ==================
> - the code base is huge
> - bindings. Could be solved with macro's i hope
> - embed and other metadata. Could be solved with macro's i guess
> - actionscript has 4 access modifiers, haxe only public and private
> - namespaces are not present in Haxe, not sure how to solve that
> - E4X, but i'm not sure how much this is used in the SDK.
> - uint data type although i 99.9% of the cases it can be mapped on a
> Haxe Int (i just ported a SHA256 from actionscript to haxe that used uints and it works)
> - AND Probably MANY issues that i forgot to mentio here...
>
> But, if you want to do that it's probably best to extend the as3hx project (see haxe trunk) which
> does basic translation from as3 to haxe and try to solve those issues described above in an automated way.
> IF you could solve all those isuess in an automated way then you could every time the flex
> trunk changes generate an automated haxe port :-)
>
> so if you got that all working, which would take a while then you could at least test performance etc.
>
> If that's ok then the fun part. Write a MXML (or Haxe Markup Language :-) compiler front end for haxe...
>
> It would be a massive amount of work and i didn't mention the hard things like modules, resource bundles, runtime libs, swc's etc.
>
> But indeed it would be very nice!
>
> cheers,
>
> arnoud
>
>
>> The issue is that both Silverlight and Flash are dieing and haXe represents a future for Flex because it is clever cross compiler
>> technology that targets lots of platforms - native o/s including mobile via nme/cpp, vm via neko, browser via js and swf and in time java/c#.
>>
>> The problem with haXe is that a language/compiler is only a part of a development environment - libraries/frameworks for persistence and GUI
>> are as important. If I could develop in haXe and use a haXe enabled Flex as my GUI framework and a haXe enabled ORM (on the lines of
>> JPA/Hibernate) as my persistence framework and then could target desktop/javascript/swf/mobile from the same code base, that would be awesome
> I like haxe's own SPOD implementation
>
>> It may be a pipe dream if every library has to be rewritten at the source level and I can understand anyone baulking at that. I will ask Nicolas
>> if there might be a way of interfacing Flex or say Hibernate (when the java target is ready) without rewrite at source level. I imagine he will
>> point at the migration tools and say that once the migration from AS3 to haXe is done, one would dump the AS3 code.
>>
>> I live in the town where "Flash on the Beach" had its last year - there was a big local Flash community but now it has moved on to Javascript (with canvas)
>> and to mobile and they are much more interested in HaXe/Corona/Titanium/Marmalade than Flex/Air mobile.
>>
>> Java/Swing failed on the desktop and the browser (applets) mainly because of runtime issues (and competition from Microsoft/Apple) and I would be sorry to see Flex die because the runtime (Flash) died under it.
>>
>> I would certainly see a future for Flex on Flash/Air technology if Adobe donated the defunct Air for Linux to Apache and Apple issued a statement embracing it
>> on OSX but I do not see this happening soon.
> Air and flash runs on osx / IOS, so why bother?
>
>> James
>
>
>
>
>
Re: Haxe and Flex
Posted by Arnoud Bos <ar...@artim-interactive.nl>.
On Mar 13, 2012, at 1:17 PM, James Cowan wrote:
>
> MXML/AS3/Flex are conceptually identical to XAML/C#/WPF. They borrow a lot of ideas from previous XML UI technologies.
> MXML/haXe/Flex does sound quite viable.
Sure, it could be done. But i guess someone should be willing to port the actionscript code.
A mapping on haxe-nme should be possible as it implements the flash displaylist.
some challenges here:
==================
- the code base is huge
- bindings. Could be solved with macro's i hope
- embed and other metadata. Could be solved with macro's i guess
- actionscript has 4 access modifiers, haxe only public and private
- namespaces are not present in Haxe, not sure how to solve that
- E4X, but i'm not sure how much this is used in the SDK.
- uint data type although i 99.9% of the cases it can be mapped on a
Haxe Int (i just ported a SHA256 from actionscript to haxe that used uints and it works)
- AND Probably MANY issues that i forgot to mentio here...
But, if you want to do that it's probably best to extend the as3hx project (see haxe trunk) which
does basic translation from as3 to haxe and try to solve those issues described above in an automated way.
IF you could solve all those isuess in an automated way then you could every time the flex
trunk changes generate an automated haxe port :-)
so if you got that all working, which would take a while then you could at least test performance etc.
If that's ok then the fun part. Write a MXML (or Haxe Markup Language :-) compiler front end for haxe...
It would be a massive amount of work and i didn't mention the hard things like modules, resource bundles, runtime libs, swc's etc.
But indeed it would be very nice!
cheers,
arnoud
>
> The issue is that both Silverlight and Flash are dieing and haXe represents a future for Flex because it is clever cross compiler
> technology that targets lots of platforms - native o/s including mobile via nme/cpp, vm via neko, browser via js and swf and in time java/c#.
>
> The problem with haXe is that a language/compiler is only a part of a development environment - libraries/frameworks for persistence and GUI
> are as important. If I could develop in haXe and use a haXe enabled Flex as my GUI framework and a haXe enabled ORM (on the lines of
> JPA/Hibernate) as my persistence framework and then could target desktop/javascript/swf/mobile from the same code base, that would be awesome
I like haxe's own SPOD implementation
> It may be a pipe dream if every library has to be rewritten at the source level and I can understand anyone baulking at that. I will ask Nicolas
> if there might be a way of interfacing Flex or say Hibernate (when the java target is ready) without rewrite at source level. I imagine he will
> point at the migration tools and say that once the migration from AS3 to haXe is done, one would dump the AS3 code.
>
> I live in the town where "Flash on the Beach" had its last year - there was a big local Flash community but now it has moved on to Javascript (with canvas)
> and to mobile and they are much more interested in HaXe/Corona/Titanium/Marmalade than Flex/Air mobile.
>
> Java/Swing failed on the desktop and the browser (applets) mainly because of runtime issues (and competition from Microsoft/Apple) and I would be sorry to see Flex die because the runtime (Flash) died under it.
>
> I would certainly see a future for Flex on Flash/Air technology if Adobe donated the defunct Air for Linux to Apache and Apple issued a statement embracing it
> on OSX but I do not see this happening soon.
Air and flash runs on osx / IOS, so why bother?
>
> James
Re: Haxe and Flex
Posted by James Cowan <ja...@googlemail.com>.
MXML/AS3/Flex are conceptually identical to XAML/C#/WPF. They borrow a
lot of ideas from previous XML UI technologies.
MXML/haXe/Flex does sound quite viable.
The issue is that both Silverlight and Flash are dieing and haXe
represents a future for Flex because it is clever cross compiler
technology that targets lots of platforms - native o/s including mobile
via nme/cpp, vm via neko, browser via js and swf and in time java/c#.
The problem with haXe is that a language/compiler is only a part of a
development environment - libraries/frameworks for persistence and GUI
are as important. If I could develop in haXe and use a haXe enabled Flex
as my GUI framework and a haXe enabled ORM (on the lines of
JPA/Hibernate) as my persistence framework and then could target
desktop/javascript/swf/mobile from the same code base, that would be
awesome.
It may be a pipe dream if every library has to be rewritten at the
source level and I can understand anyone baulking at that. I will ask
Nicolas
if there might be a way of interfacing Flex or say Hibernate (when the
java target is ready) without rewrite at source level. I imagine he will
point at the migration tools and say that once the migration from AS3 to
haXe is done, one would dump the AS3 code.
I live in the town where "Flash on the Beach" had its last year - there
was a big local Flash community but now it has moved on to Javascript
(with canvas)
and to mobile and they are much more interested in
HaXe/Corona/Titanium/Marmalade than Flex/Air mobile.
Java/Swing failed on the desktop and the browser (applets) mainly
because of runtime issues (and competition from Microsoft/Apple) and I
would be sorry to see Flex die because the runtime (Flash) died under it.
I would certainly see a future for Flex on Flash/Air technology if Adobe
donated the defunct Air for Linux to Apache and Apple issued a statement
embracing it
on OSX but I do not see this happening soon.
James
On 12/03/2012 20:10, Martin Heidegger wrote:
> To be honest: if I would have to write a framework for haXe I would
> focus it on other things than I do in AS3.
> AS3 is not a perfect language (by a long shot) but in Flex MXML is a
> key concept and it does take some time to implement a hxml of
> the same logic, same goes for quite a few other aspects (that now
> "just work"). I am not opposed to that but like I said before:
> I wouldn't call that Flex because it most likely will not resemble
> Flex a lot.
>
> yours
> Martin.
>
>
> On 13/03/2012 04:56, James Cowan wrote:
>> haXe's ability to compiled to many targets (native cpp, java/c#,
>> javascript, as3/swf and neko vm) does make it very attractive
>> and it is open source.
>>
>> I noticed that ASwing (the port of Java Swing to AS3) is making the
>> plunge and moving to haXe to take advantage of the cpp
>> target: http://www.aswing.org/?cat=26.
>>
>> I did not get a sense from looking at the thread that there was much
>> enthusiasm for moving from AS3 to haXe and not porting
>> to haXe would mean 2 code bases which does not sound ideal.
>>
>> James
>
>
Re: Haxe and Flex
Posted by Martin Heidegger <mh...@leichtgewicht.at>.
To be honest: if I would have to write a framework for haXe I would
focus it on other things than I do in AS3.
AS3 is not a perfect language (by a long shot) but in Flex MXML is a key
concept and it does take some time to implement a hxml of
the same logic, same goes for quite a few other aspects (that now "just
work"). I am not opposed to that but like I said before:
I wouldn't call that Flex because it most likely will not resemble Flex
a lot.
yours
Martin.
On 13/03/2012 04:56, James Cowan wrote:
> haXe's ability to compiled to many targets (native cpp, java/c#,
> javascript, as3/swf and neko vm) does make it very attractive
> and it is open source.
>
> I noticed that ASwing (the port of Java Swing to AS3) is making the
> plunge and moving to haXe to take advantage of the cpp
> target: http://www.aswing.org/?cat=26.
>
> I did not get a sense from looking at the thread that there was much
> enthusiasm for moving from AS3 to haXe and not porting
> to haXe would mean 2 code bases which does not sound ideal.
>
> James
Re: Haxe and Flex
Posted by James Cowan <ja...@googlemail.com>.
haXe's ability to compiled to many targets (native cpp, java/c#,
javascript, as3/swf and neko vm) does make it very attractive
and it is open source.
I noticed that ASwing (the port of Java Swing to AS3) is making the
plunge and moving to haXe to take advantage of the cpp
target: http://www.aswing.org/?cat=26.
I did not get a sense from looking at the thread that there was much
enthusiasm for moving from AS3 to haXe and not porting
to haXe would mean 2 code bases which does not sound ideal.
James
On 12/03/2012 12:54, Martin Heidegger wrote:
> On 12/03/2012 21:03, James Cowan wrote:
>>
>> This has probably been discussed before but I was wondering what the
>> conclusion/response
>> to the suggestion of linking Haxe with Flex was:
>> http://ncannasse.fr/blog/open_letter_to_flex_community
>>
>> Is it actually possible to link Haxe and Flex? This tutorial
>> (http://haxe.org/doc/flash/flex) is very out of
>> date.
>>
>> Perhaps if anyone else is interested, they could drop me an email and
>> we could have a (skype) chat?
>>
>> James
>>
>
> I remember writing a summary at one point [1]. However: There are
> people here interested in making haXe and Flex work.
> I personally want to invest my time in other things. You can organize
> your attempt to work with haXe here too!
>
> yours
> Martin
>
> [1] http://markmail.org/thread/flt3vpqqs5ffmf55
>
Re: Haxe and Flex
Posted by Martin Heidegger <mh...@leichtgewicht.at>.
On 12/03/2012 21:03, James Cowan wrote:
>
> This has probably been discussed before but I was wondering what the
> conclusion/response
> to the suggestion of linking Haxe with Flex was:
> http://ncannasse.fr/blog/open_letter_to_flex_community
>
> Is it actually possible to link Haxe and Flex? This tutorial
> (http://haxe.org/doc/flash/flex) is very out of
> date.
>
> Perhaps if anyone else is interested, they could drop me an email and
> we could have a (skype) chat?
>
> James
>
I remember writing a summary at one point [1]. However: There are people
here interested in making haXe and Flex work.
I personally want to invest my time in other things. You can organize
your attempt to work with haXe here too!
yours
Martin
[1] http://markmail.org/thread/flt3vpqqs5ffmf55
Haxe and Flex
Posted by James Cowan <ja...@googlemail.com>.
This has probably been discussed before but I was wondering what the
conclusion/response
to the suggestion of linking Haxe with Flex was:
http://ncannasse.fr/blog/open_letter_to_flex_community
Is it actually possible to link Haxe and Flex? This tutorial
(http://haxe.org/doc/flash/flex) is very out of
date.
Perhaps if anyone else is interested, they could drop me an email and we
could have a (skype) chat?
James
Re: [Wiki] Code conventions
Posted by Paul Evans <pa...@creative-cognition.co.uk>.
On 10 Mar 2012, at 15:31, Martin Heidegger wrote:
> There is a reason why I wrote the "Getting Started" area in the wiki. It should answer exactly what you asked for.
> *Please read the wiki*
https://cwiki.apache.org/confluence/display/FLEX/Getting+Started
Re: [Wiki] Code conventions
Posted by Martin Heidegger <mh...@leichtgewicht.at>.
Hello Sumit,
There is a reason why I wrote the "Getting Started" area in the wiki. It
should answer exactly what you asked for.
*Please read the wiki*
Short summary:
If you want to commit, commit. There is no need to wait. You can submit
patches via jira[1] create discussable forks
via github[2] and discuss new things via this mailing-list. You might be
asked as to become a commiter once you've
published something. But you do *not* need to wait for that to start.
yours
Martin.
[1] https://issues.apache.org/jira/browse/FLEX
[2] https://github.com/apache/flex
Re: [Wiki] Code conventions
Posted by sumit arora <er...@gmail.com>.
Martin,
I am saying I want to be the part of flex-dev team for making changes in
flex sdk for releasing next version.
I have been working in flex for almost 5 years now and know about sdk in
depth.
so whom should I contact for this.
Regards,
Sumit Arora
On Sat, Mar 10, 2012 at 8:52 PM, Martin Heidegger <mh...@leichtgewicht.at>wrote:
> On 10/03/2012 23:51, sumit arora wrote:
>
>> Sure,
>>
>> Hi Martin,
>>
>> I am new to project and want to help for same.
>> can you tell me how contribute for same.
>>
>
> Hello Sumit,
>
> Did you read [1]? Basically for the code conventions to get juicy we
> should have them
> at a place where we can edit/comment on them. I wanted to copy [2] From
> adobe
> but I have doubts if that is legally okay. Thats why I asked the *Adobe*
> guys if it they
> know if that would be a problem.
>
> yours
> Martin.
>
> [1] https://cwiki.apache.org/**confluence/display/FLEX/**Getting+Started<https://cwiki.apache.org/confluence/display/FLEX/Getting+Started>
> [2] http://opensource.adobe.com/**wiki/display/flexsdk/Coding+**
> Conventions<http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions>
>
--
Sumit Arora
(Nothing is impossible it is only impossible untill you or someone else
finds the appropriate solution to it.
The only way to discover the limits of possible is to go beyond them into
the impossible.)
Re: [Wiki] Code conventions
Posted by Martin Heidegger <mh...@leichtgewicht.at>.
On 10/03/2012 23:51, sumit arora wrote:
> Sure,
>
> Hi Martin,
>
> I am new to project and want to help for same.
> can you tell me how contribute for same.
Hello Sumit,
Did you read [1]? Basically for the code conventions to get juicy we
should have them
at a place where we can edit/comment on them. I wanted to copy [2] From
adobe
but I have doubts if that is legally okay. Thats why I asked the *Adobe*
guys if it they
know if that would be a problem.
yours
Martin.
[1] https://cwiki.apache.org/confluence/display/FLEX/Getting+Started
[2] http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions
Re: [Wiki] Code conventions
Posted by sumit arora <er...@gmail.com>.
Sure,
Hi Martin,
I am new to project and want to help for same.
can you tell me how contribute for same.
On Sat, Mar 10, 2012 at 2:34 PM, Martin Heidegger <mh...@leichtgewicht.at>wrote:
> Hello Adobe team,
>
> I was planning to copy the code conventions of the Adobe wiki to the
> Apache wiki so we can start extending/finishing it. I was wondering about
> the legal implications.
>
> any thoughts?
>
> yours
> Martin.
>
--
Sumit Arora
(Nothing is impossible it is only impossible untill you or someone else
finds the appropriate solution to it.
The only way to discover the limits of possible is to go beyond them into
the impossible.)
Re: [Wiki] Code conventions
Posted by David Francis Buhler <da...@gmail.com>.
I was going to suggest trying to find an existing style-guide from an
open-source project. Perhaps the Apache Flex project can use the Android
Style Guide if the project itself uses an Apache License. Then, in my
research, I found many projects simply refer to a simpler style-guide for
naming conventions, and format tends to be dictated by an agreed-upon
formatting style. We should be able to pull from a simple style-guide for
naming conventions, and the format we can alter as we go along, starting
with Martin's properties file.
[1] http://source.android.com/source/code-style.html
[2] http://source.android.com/source/licenses.html
On Sat, Mar 10, 2012 at 12:43 PM, Alex Harui <ah...@adobe.com> wrote:
> I'm pretty sure it is not legal to copy a webpage without permission, and
> getting permission will currently require our legal folks to get involved.
> Recently I asked for permission to publish an internal spec and that got
> blocked by requiring legal review.
>
> Bertrand said he'd help me get a blanket agreement so everything I say and
> do and want to donate doesn't have to go through legal. I was going to
> work
> on that after we get the compiler code in.
>
> For now, I think your choices are to provide a link to the Adobe page, or
> just write your own, or assume we'll get permission. But of course, I'm
> not
> a lawyer...
>
> -ALex
>
>
> On 3/10/12 1:04 AM, "Martin Heidegger" <mh...@leichtgewicht.at> wrote:
>
> > Hello Adobe team,
> >
> > I was planning to copy the code conventions of the Adobe wiki to the
> > Apache wiki so we can start extending/finishing it. I was wondering
> > about the legal implications.
> >
> > any thoughts?
> >
> > yours
> > Martin.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: [Wiki] Code conventions
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
It might help to take a look at the Flex Formatter property file I placed up on the whiteboard.[1]
This should be fairly similar to Adobe format stye and is mostly human readable.
Thanks,
Justin
1. http://svn.apache.org/viewvc/incubator/flex/whiteboard/jmclean/formatting/format.properties?view=markup
Re: [Wiki] Code conventions
Posted by Jeffry Houser <je...@dot-com-it.com>.
It depends..
Under US Copyright work; any modifications are derivative works. In
writing, I haven't the foggiest idea how much needs to be changed to
make it 'separate'.
In music, the "common knowledge" is that you need four bars to make
something unique. That means, you can copy less than four bars from
someone else and be okay.
Four bars is a very very small piece of any musical work.
[Note, I am not a lawyer, and this is in no way legal advice, and
common knowledge is not always legally accurate; and we are potentially
dealing with a lot more than "US copyright law" in this case].
On 3/12/2012 4:38 AM, John Fletcher wrote:
> Once you modify a piece of writing enough, it's legally a separate work
> isn't it?
>
> John
>
--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust
Re: [Wiki] Code conventions
Posted by John Fletcher <fl...@gmail.com>.
Once you modify a piece of writing enough, it's legally a separate work
isn't it?
John
Re: [Wiki] Code conventions
Posted by Alex Harui <ah...@adobe.com>.
On 3/10/12 11:00 AM, "Martin Heidegger" <mh...@leichtgewicht.at> wrote:
> Thanks Alex,
>
> lets see what to do about this. I guess I don't want to bother the Adobe
> lawyers ... as they
> have (a lot) more important things to do. Which leaves it open to write
> a new one *yey*. I am not
> sure when I will start with that. Any work I will do will be based on
> current code and not on the
> document (not not start to create any conflicts ...).
>
I think you could say: We use the coding conventions at <link> with the
following changes, modifications, and enhancements...
Then it hopefully wouldn't take you as much time.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [Wiki] Code conventions
Posted by Martin Heidegger <mh...@leichtgewicht.at>.
Thanks Alex,
lets see what to do about this. I guess I don't want to bother the Adobe
lawyers ... as they
have (a lot) more important things to do. Which leaves it open to write
a new one *yey*. I am not
sure when I will start with that. Any work I will do will be based on
current code and not on the
document (not not start to create any conflicts ...).
yours
Martin.
On 11/03/2012 02:43, Alex Harui wrote:
> I'm pretty sure it is not legal to copy a webpage without permission, and
> getting permission will currently require our legal folks to get involved.
> Recently I asked for permission to publish an internal spec and that got
> blocked by requiring legal review.
>
> Bertrand said he'd help me get a blanket agreement so everything I say and
> do and want to donate doesn't have to go through legal. I was going to work
> on that after we get the compiler code in.
>
> For now, I think your choices are to provide a link to the Adobe page, or
> just write your own, or assume we'll get permission. But of course, I'm not
> a lawyer...
>
> -ALex
Re: [Wiki] Code conventions
Posted by Alex Harui <ah...@adobe.com>.
I'm pretty sure it is not legal to copy a webpage without permission, and
getting permission will currently require our legal folks to get involved.
Recently I asked for permission to publish an internal spec and that got
blocked by requiring legal review.
Bertrand said he'd help me get a blanket agreement so everything I say and
do and want to donate doesn't have to go through legal. I was going to work
on that after we get the compiler code in.
For now, I think your choices are to provide a link to the Adobe page, or
just write your own, or assume we'll get permission. But of course, I'm not
a lawyer...
-ALex
On 3/10/12 1:04 AM, "Martin Heidegger" <mh...@leichtgewicht.at> wrote:
> Hello Adobe team,
>
> I was planning to copy the code conventions of the Adobe wiki to the
> Apache wiki so we can start extending/finishing it. I was wondering
> about the legal implications.
>
> any thoughts?
>
> yours
> Martin.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui