Hi,
With a tag on the framework directory we can easily checkout the trunk before
any changes that are made to it. We don't actually even need a tag a svn
checkout -revision 1290843 will get the framework as it was initially donated
by Adobe. If we did create a tag it would only be use to creat
On Wed, Feb 22, 2012 at 10:46 PM, Alex Harui wrote:
>
>
>
> On 2/22/12 7:58 PM, "Justin Mclean" wrote:
>
> > Hi,
> >
> >> Well, My assumption is because the size of the SVN dumps
> > I wouldn't expect the framework code that's already in SVN to be
> reimported in
> > the same way again. Other Ad
Hi,
> However, I think you can branch what's there, make your changes in trunk and
> we can cut the parity release from the branch. I'm not an SVN expert, but I
> think we can control what revisions get integrated into the parity branch.
I think you mean tag which is a named snapshot of an SVN r
+1 of course
Il giorno 22 febbraio 2012 11:03, Dimitri k. ha scritto:
> After the discussion on the ML about the Design View, I thought it would
> be a good idea to ask Deepa at the Flex Paris meeting if Adobe could
> consider to open-source it after the removal from next version of Flash
> B
On 2/22/12 7:58 PM, "Justin Mclean" wrote:
> Hi,
>
>> Well, My assumption is because the size of the SVN dumps
> I wouldn't expect the framework code that's already in SVN to be reimported in
> the same way again. Other Adobe donations would be a large import but there no
> issues there.
>
>
This is brilliant!!
I am not good in designing but if any running around work needs to be done,
let me know.
Thanks
Avinash Y
On Thu, Feb 23, 2012 at 11:21 AM, Martin Heidegger wrote:
> I mean designs (photoshop/illustrator/gimp/**scribbles/css/etc.) and
> concepts (swfs/code/text/anything real
I mean designs (photoshop/illustrator/gimp/scribbles/css/etc.) and
concepts (swfs/code/text/anything really) for user interfaces that
utilize the
power of flash and flex. Flex default styles look pretty rusty compared
to Android and co. and new designs start with ideas, right?
yours
Martin.
O
I'm in, but what do you mean?
Ariel Jakobovits
Email: arielj...@yahoo.com
Phone: 650-690-2213
Fax: 650-641-0031
Cell: 650-823-8699
From: Martin Heidegger
To: flex-dev@incubator.apache.org
Sent: Wednesday, February 22, 2012 7:55 PM
Subject: [IDEAS] Flex: New u
I like what Cortlandt is saying here. While I don't disregard a new compiler or
outputting HTML as worthy goals, they seem like long term goals to me.
And while Adobe is focusing Flash Player on gaming, I don't see how that will
negatively affect Flex since we already have the features we need t
Hi,
> Well, My assumption is because the size of the SVN dumps
I wouldn't expect the framework code that's already in SVN to be reimported in
the same way again. Other Adobe donations would be a large import but there no
issues there.
Hopefully Carol (or someone else) can confirm that changes t
Hello List,
I think we need new ideas for user interface designs created with Flex.
New compared to the efforts in the Android/iOS community but also just
spectacular ones.
What do you think?
yours
Martin.
Hello List,
Thinking about it a little I think its good to clear up the mind about
haXe. So I want to summarize the things about it
haXe...
* ... contains a very fast and good avm2 bytecode compiler (that does
things Falcon will do in future - today).
* ... has established and tested a
Hi Jeffrey,
If anything is more frustrating than the Me 2's to expanding and improving
existing features it's the constant whining and noise about what adobe
could have done or isn't willing to do, or speculation about totally
throwing away the baby with the bathwate0,r or core framework features
On Wednesday, February 22, 2012, Justin Mclean wrote:
> Hi,
>
> > I actually don't know the impact I just wanted to relay Carol's message,
> Understand. I'm fairly sure the locale changes would have no impact. The
> changes to the framework_build.xml may have an impact but as I said if
> they do
Hi,
> I actually don't know the impact I just wanted to relay Carol's message,
Understand. I'm fairly sure the locale changes would have no impact. The
changes to the framework_build.xml may have an impact but as I said if they do
they can be reverted and I'll then reapply the patch to the new
On Wednesday, February 22, 2012, Justin Mclean wrote:
> Hi,
>
> > Carol did request that we didn't check any patches into trunk until she
> > gets the rest of the framework in, I'm not sure how the locales affect or
> > don't affect that request.
>
> I had assumed it was only changes to the build.
Hi,
> Why wouldn't you revise the build scripts to compile various resource bundle
> SWCs for these locales?
I have provided a patch to revise the build files but Adobe is still working on
changes that may impact that patch.
The build files can be edited by hand to compile for a different loca
Hi,
> Carol did request that we didn't check any patches into trunk until she
> gets the rest of the framework in, I'm not sure how the locales affect or
> don't affect that request.
I had assumed it was only changes to the build.xml files, but perhaps I
misread?
I fairly confident that checki
Why wouldn't you revise the build scripts to compile various resource bundle
SWCs for these locales?
- Gordon Smith, Adobe
-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com]
Sent: Wednesday, February 22, 2012 5:22 PM
To: flex-dev@incubator.apache.org
Subject: [LAZ
On Wed, Feb 22, 2012 at 5:22 PM, Justin Mclean wrote:
> Hi,
>
> We have en_AU and en_GB locale pataches waiting to applied here:
> https://issues.apache.org/jira/browse/FLEX-16
>
> Only the resource files would be checked in and there would be no changes
> to build scripts or any framework code.
>
Hi,
We have en_AU and en_GB locale pataches waiting to applied here:
https://issues.apache.org/jira/browse/FLEX-16
Only the resource files would be checked in and there would be no changes to
build scripts or any framework code.
Further improvements such as looking into using CLDR can be looked
On Wed, Feb 22, 2012 at 10:44 AM, Neil Robbins
wrote:
> name: Neil Robbins
> email: nrobb...@lexialearning.com
>
> Thanks,
>
> - Neil
You have been added. Use your powers wisely. :)
- Doug
On Wed, Feb 22, 2012 at 3:15 PM, Alex Harui wrote:
>
>
>
> On 2/22/12 11:34 AM, "Martin Heidegger" wrote:
>
>> As a developer I know that when being stuck, sometimes a clear mind
>> helps. I basically just
>> wanted to offer my help and was suggesting that I wasn't the only one.
> And I really ap
On 2/22/12 11:34 AM, "Martin Heidegger" wrote:
> As a developer I know that when being stuck, sometimes a clear mind
> helps. I basically just
> wanted to offer my help and was suggesting that I wasn't the only one.
And I really appreciate your energy and contributions. And you are not the
on
Linux users are usually happier with less bells and whistles then their
peers on other platforms. Probably because the platform itself provides
much more tools, so there's no real need to add even more on top of it.
You say it's difficult to get program with complex GUI to run both under
KDE and G
[
https://issues.apache.org/jira/browse/FLEX-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214016#comment-13214016
]
Justin Mclean commented on FLEX-14:
---
Would you be OK with the changes to build_framework.xm
>> *) e4x: Its such a pleasure to use in AS3.
>We have haxe.xml.Fast API which is maybe not as much powerful as E4X but still
>very convenient for quick XML parsing. It should be possible to write a quite
>complete E4X equivalent with haXe macros.
>Keep in mind also that XML is being replaced i
On Wed, Feb 22, 2012 at 2:11 PM, Nicolas Cannasse
wrote:
> Yes, let's do it slowly : the first year only line numbers multiples of 4
> will have mandatory semicolons, then the next year only odds lines and then
> finally in three years every line.
>
> This way users can adapt their habits little b
Nice.
How about a compiler option that's on by default, but can be turned off
for those compiling legacy content. So get folks into the habit of using
semicolons for new content, and still be able to update legacy content
as they see fit.
Brent
On 2/22/12 1:11 PM, Nicolas Cannasse wrote:
Le 22/02/2012 19:31, Martin Heidegger a écrit :
Thanks for explaining that, Gordon. I guess everybody wonders why the
compiler doesn't make use of those opcodes in the the other syntax.
yours
Martin.
For the record, haXe compiler does.
It's 4 times faster and uses less bytes.
There are actual
Carol, think of any number between 1 and 100, and I will find that number
of public or protected properties or methods that have not been documented,
and, instead were using @private ASDoc comment.
Ideally, that might have been as you describe it, but in practice it was
very far from that. (I only
Le 22/02/2012 19:20, Greg Reddin a écrit :
On Wed, Feb 22, 2012 at 6:53 AM, David Arno wrote:
If Dimitri's great efforts to try and get us early access to the Falcon
compiler fail and we instead carry on with trying to develop our Goshawk
compiler, I'd like to make a change to the AS3 language
On Feb 17, 2012, at 3:51 AM, Jun Heider wrote:
>
> I agree with Bertrand. I propose we remove the [DECISION] marker in favor of
> having a [LAZY] marker to handle lazy consensus:
> http://www.apache.org/foundation/voting.html#LazyConsensus
>
> Main reason, is ability to skim the ML when you're
Ah gotcha, now I see it. Thanks for that clarification :)
M
On Wed, Feb 22, 2012 at 2:44 PM, Nicholas Kwiatkowski wrote:
> I'm not from Adobe, but I can say that according to that doc, on the Linux
> platform, Flash Player will only be available using the new PEIPR API,
> which at this time is
I'm not from Adobe, but I can say that according to that doc, on the Linux
platform, Flash Player will only be available using the new PEIPR API,
which at this time is only exposed by Chrome.
This will not affect Mac or Windows based Flash Player deployments.
-Nick
On Wed, Feb 22, 2012 at 2:39 P
On Wed, Feb 22, 2012 at 1:39 PM, Michel Boudreau
wrote:
> I'm not sure if I'm reading this correctly. Can someone from Adobe please
> comment on it?
>
Stop FUD fast.
Only on Linux.
--
Jonathan Campos
http://blogs.adobe.com/flashplayer/2012/02/adobe-and-google-partnering-for-flash-player-on-linux.html
I'm not sure if I'm reading this correctly. Can someone from Adobe please
comment on it?
Thanks,
--
Michel Boudreau
"If at first you don't succeed, use a bigger hammer." - Unofficial motto o
On 23/02/2012 04:19, Alex Harui wrote:
Falcon is simply being developed as closed source in the interest of time.
In fact, Gordon Smith is on the Falcon team and is monitoring the Apache
Flex mailing list, but they are working on AS3. The MXML compiler code they
wrote earlier is still in there, b
On Feb 22, 2012, at 7:49 AM, Carol Frampton (Commented) (JIRA) wrote:
>
>[
> https://issues.apache.org/jira/browse/FLEX-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213668#comment-13213668
> ]
>
> Carol Frampton commented on FLEX-14:
> -
On 2/22/12 11:09 AM, "Martin Heidegger" wrote:
> I mean:
> Somehow it seems like there is no question to them on the path where the
> Apache community could help. Aside from that: If you want to develop a
> compiler for Gaming you should drop all "enterprise" features like mxml
> or binding f
>
> > I seem to remember reading somewhere that Falcon uses a grammar based
> approach as well to parsing AS3. I'm wondering how they're pulling it off
> then...
>
> Falcon currently uses an ANTLR 2 grammar to parse ActionScript. We've been
> improving the grammar that was previously used for code
On 2/22/12 1:53 AM, "David Arno" wrote:
> However, they could still provide
> access to it as you describe before then.
I think there is a difference between opening up the source under an Adobe
license and an Apache license. The Flex code we just got into Apache this
week was available on th
On 23/02/2012 03:54, Alex Harui wrote:
Adobe employees involved in Apache Flex are discussing things on the Apache
Flex mailing list.
I guess that is common knowledge. I am saying that Adobe employees that
are involved in the AS3/MXML compiler writing should be too. I mean:
Somehow it seems l
On Feb 22, 2012, at 10:45 AM, Left Right wrote:
> I honestly believe that a concept of 3 different nulls (null, undefined and
> false) in ECMAScript is... well, just yet another thing ECMAScript did
> wrong. By reducing it to 2 nulls HaXe did it some justice, but I'd still be
> happier with only
I'll try to make it happen in Falcon.
- Gordon Smith, Falcon team, Adobe
-Original Message-
From: Martin Heidegger [mailto:m...@leichtgewicht.at]
Sent: Wednesday, February 22, 2012 10:31 AM
To: flex-dev@incubator.apache.org
Subject: Re: Flex adopting haXe ?
Thanks for explaining that,
On 2/22/12 3:04 AM, "n.x.j...@accenture.com" wrote:
> In the technical roadmap we saw that Flash player will focus on Gaming and
> premium Video support.
>
> What about Enterprise development support? Do we continue Enterprise dev. in
> Flex
>
Adobe will not be focusing on Enterprise develop
On 2/22/12 4:16 AM, "Martin Heidegger" wrote:
> On 22/02/2012 18:29, Dimitri k. wrote:
>> At the Paris Flex meeting, I spoke with Thibault Imbert, who is Senior
>> Runtimes product manager , about the fact that the Apache Flex project would
>> really benefit from having some kind of early acce
On 23/02/2012 03:29, Alex Harui wrote:
On 2/22/12 7:18 AM, "Martin Heidegger" wrote:
Also another thing is that
if(a == null) is slower than if(a) at least compiled with mxmlc.
Did you try if(a === null)
IIRC, there are lots of things going on when you use "==".
I created the test [1] a
Thanks for explaining that, Gordon. I guess everybody wonders why the
compiler doesn't make use of those opcodes in the the other syntax.
yours
Martin.
On 23/02/2012 03:25, Gordon Smith wrote:
Flash Player has special newarray and newobject bytecodes that are used for
array literals like [ 1
Flex is still an enterprise level tools. What they mean by the whitepaper
is that Flex will not be part of the technical decisions for the Flash
Player in the future. It doesn't mean that Flex won't work (that's our
job), it just means that Flash Player won't add features just because Flex
could
On 2/22/12 7:18 AM, "Martin Heidegger" wrote:
>
> Also another thing is that
>
> if(a == null) is slower than if(a) at least compiled with mxmlc.
Did you try if(a === null)
IIRC, there are lots of things going on when you use "==".
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http:
Flash Player has special newarray and newobject bytecodes that are used for
array literals like [ 1, 2, 3 ] and object literals like { a: 1, b: 2, c: 3 }
and are faster than a generic constructor call. That's why the coding
guidelines for Flex recommend using the literal syntax rather than new A
On Wed, Feb 22, 2012 at 6:53 AM, David Arno wrote:
>
> If Dimitri's great efforts to try and get us early access to the Falcon
> compiler fail and we instead carry on with trying to develop our Goshawk
> compiler, I'd like to make a change to the AS3 language spec by making
> semicolons at the end
> At Adobe, every single Flex public property, method and class had to be
> approved by the architectual review board which oversees the Flash API.
This is also true of 'protected' ones.
- Gordon Smith, Adobe (member of the Platform Architectural Review Board)
-Original Message-
From:
I echo your sentiments, Left Right!
Being able to develop Flex applications on Linux is extremely important to
me, and I'm happy to assist to that end in any way that I can.
On 23/02/2012 03:11, Charles Monteiro wrote:
I could care less, but I'm just wondering what this buys us ? i.e. and if
it doesn't buy us much why would you add discrepancies vis a vis AS3 ?
It has been described at the start: the optional semicolons are not
describable using BNF.
BNF is a lan
> I seem to remember reading somewhere that Falcon uses a grammar based
> approach as well to parsing AS3. I'm wondering how they're pulling it off
> then...
Falcon currently uses an ANTLR 2 grammar to parse ActionScript. We've been
improving the grammar that was previously used for code intel
I could care less, but I'm just wondering what this buys us ? i.e. and if
it doesn't buy us much why would you add discrepancies vis a vis AS3 ?
On Wed, Feb 22, 2012 at 12:09 PM, Omar Gonzalez
wrote:
> >
> >
> > If we went through with writing our own compiler I would cheer making
> semicolons ma
On 23/02/2012 02:01, Nicolas Cannasse wrote:
Le 22/02/2012 17:56, Martin Heidegger a écrit :
in haXe case, "this" is always the object in which the local function
function has been declared, not the one on which the event listener is
added.
Did you see my example code? I am not sure how to na
name: Neil Robbins
email: nrobb...@lexialearning.com
Thanks,
- Neil
On 2/22/12 5:21 AM, "Martin Heidegger" wrote:
>State your username here(in the mailinglist) with request for wiki
>access and it (most likely) will be granted.
>
>yours
>Martin.
>
Companies that base development decisions on *_current_* market share is what
is short-sighted and only reinforces the status quo. That's no better than the
dark ages of webdevs coding for IE4 at 800x600 resolution.
tlj
-Original Message-
From: Nicholas Kwiatkowski [mailto:nicho...@
>
>
> If we went through with writing our own compiler I would cheer making
semicolons mandatory.
--
Omar Gonzalez
s9tpep...@apache.org
Apache Flex PPMC Member
>
>
> Kill it!
:)
--
Omar Gonzalez
s9tpep...@apache.org
Apache Flex PPMC Member
>
>
>
>> In my experience, the mx_internal namespace was used often for the
>> purposes such as to cover the weak points in design. I think that the
>> problem of not documenting things could've been solved by @private
At Adobe, every single Flex public property, method and class had to be
approve
As an avid Ubuntu user (obviously, desktop Linux), few clarifications on
how Adobe runtimes worked, until recently, at least:
- player plugin - There was a flash-player-nonfree in the Debian (and
Ubuntu) PPAs, that one would normally install if using Firefox, Opera,
Seamonkey or any similar browse
Le 22/02/2012 17:56, Martin Heidegger a écrit :
in haXe case, "this" is always the object in which the local function
function has been declared, not the one on which the event listener is
added.
Did you see my example code? I am not sure how to name that particular
difference.
In ActionScrip
- Original Message -
From: "Jeffry Houser"
This is a high traffic mailing list; so I get frustrated with the
occasional barrage of "me too/+1" non-vote-thread posts which add nothing
to any discussion.
I question how many of the people who want this are willing to put time
and effo
On 23/02/2012 00:48, Nicolas Cannasse wrote:
Well, speaking of the niceties of haXe, we have
--dead-code-elimination now that will only include in the output the
methods/fields actually used by the application.
That is treating the symptom not the problem. The dead-code-elimination
(like unus
On 2/22/2012 11:41 AM, Dimitri k. wrote:
From: "Jeffry Houser"
I don't think any number of +1s will convince Adobe either way.
Honestly, I personally could care less about design view. It made
sense when Adobe wanted to make Flex the "new Visual Basic" and
accessible to anyone. I'm not
Thanks for the tip.. I hadn't heard of IntelliJ.
-Original Message-
From: Conrad Winchester [mailto:con...@chiwestern.com]
Sent: Monday, February 13, 2012 1:49 AM
To: flex-dev@incubator.apache.org
Subject: Re: Apache Flex suggestion - dumping SWF support in favor of HTML5 -
don't listen
From: "Jeffry Houser"
I don't think any number of +1s will convince Adobe either way.
Honestly, I personally could care less about design view. It made sense
when Adobe wanted to make Flex the "new Visual Basic" and accessible to
anyone. I'm not sure if I would put effort to try to fulfi
+1
2012/2/22 Nicolas Cannasse
> Le 22/02/2012 13:53, David Arno a écrit :
>
>> As I suspect there are many here not following the [gosh] threads, I'm
>> repeating a question from yesterday to a wider audience. Apologies in
>> advance if you do read those threads and just didn't care enough to
>>
My personal workflow wouldn't change if we had it, but I agree that it
is a useful piece of FB (especially for newer devs) and if we could
have it, then that would be terrific!
+1
JP
On Wed, Feb 22, 2012 at 9:37 AM, Jeffry Houser wrote:
>
> I don't think any number of +1s will convince Adobe e
Le 22/02/2012 15:33, ganaraj p r a écrit :
Thanks Nicolas,
I was the one who mentioned you in a post and wanted your inputs on "How we
could go about porting Flex to Haxe?".. I assumed that since you built Haxe
( duh! ) and that since Haxe is inspired by AS3, you would be able to
provide some de
Le 22/02/2012 13:53, David Arno a écrit :
As I suspect there are many here not following the [gosh] threads, I'm
repeating a question from yesterday to a wider audience. Apologies in
advance if you do read those threads and just didn't care enough to comment
yesterday ;)
If Dimitri's great effor
Le 22/02/2012 13:09, Carlos Rovira a écrit :
[...]
Now haXe has evolved great and Apache Flex could go the haXe way to be a
real open source framework that does not depend only in Adobe's runtime.
The problems behind : This way is hard, but feasible, and take into account
that principal actors u
Le 22/02/2012 15:30, Martin Heidegger a écrit :
The point of the functions-files is that you don't create huge code
dependencies: Say you create a dependency to StringTools.endsWith() then
the compiler better compiles all functions of StringTools into the swf
so it can be loaded properly. In AS3:
I honestly believe that a concept of 3 different nulls (null, undefined and
false) in ECMAScript is... well, just yet another thing ECMAScript did
wrong. By reducing it to 2 nulls HaXe did it some justice, but I'd still be
happier with only one :P
And, you are really arguing on unimportant issues
On Wed, Feb 22, 2012 at 8:03 AM, Saurabh Seth wrote:
> Username : Saurabh
> Email : saurabh.s...@bdisys.com
I've added you to the wiki.
I don't think any number of +1s will convince Adobe either way.
Honestly, I personally could care less about design view. It made
sense when Adobe wanted to make Flex the "new Visual Basic" and
accessible to anyone. I'm not sure if I would put effort to try to
fulfill that role, though.
I did performance tests ... but these things change very often.
My understanding is that there is no casting going on. It is just a test
if the "memory" at x is filled or not.
However at a==null it tries to verify if statement a is same as
statement b putting each in a memory.
yours
Martin.
O
>
> > From: Martin Heidegger [mailto:m...@leichtgewicht.at]
> > Sent: 22 February 2012 15:18
> > Also another thing is that
> >
> > if(a == null) is slower than if(a) at least compiled with mxmlc.
> Is it really? I didn't know that.
>
> Writing code that enables a cast + comparison to happen q
+1
its essential for RAD , Design View is key to prototyping , getting things
up and running, source view is for tweaking and polishing, both are
essential in any modern RAD environment
+ 1000 really
On Wed, Feb 22, 2012 at 10:19 AM, Iuri Pereira wrote:
> +1
>
> Iuri
>
>
> 2012/2/22 Arturo Alv
> From: Martin Heidegger [mailto:m...@leichtgewicht.at]
> Sent: 22 February 2012 15:18
> Also another thing is that
>
> if(a == null) is slower than if(a) at least compiled with mxmlc.
Is it really? I didn't know that.
Writing code that enables a cast + comparison to happen quicker than a
di
+1
Iuri
2012/2/22 Arturo Alvarado
>
> > Another +1, it's good for quick wireframes and getting started
> > > Right, Design View is very important to learn the Flex components
> behaviours.
> > > +1
> > > Bruce Lane
>
> +1 Also
>
> Arturo Alvarado
>
>
On 23/02/2012 00:13, David Arno wrote:
read into coding with haXe...
The problem with your examples Martin is that you have the resultant code
equivalent slightly wrong unfortunately and this slight difference can be
the cause of problems. The correct version is:
var a: String= ...;
ret
> From: Martin Heidegger [mailto:m...@leichtgewicht.at]
> Sent: 22 February 2012 14:55
> I just remembered another thing that makes me a little mad every time I
read into coding with haXe...
The problem with your examples Martin is that you have the resultant code
equivalent slightly wrong unfort
I think whiteboard/frameworks should be deleted. I had thought of that on
Saturday when the trunk code went in but somehow I forgot about it on my
few days away :) I will delete it today to avoid confusion.
Carol
On 2/21/12 9 :14AM, "almansour belleh blanco"
wrote:
>By the way, I made the di
Username : Saurabh
Email : saurabh.s...@bdisys.com
Thanks & Regards,
Saurabh Seth
Team Lead
BDI Systems | www.bdisys.com
'A Business Data Intelligence Company'
M: +91-99496-53530
-Original Message-
From: Martin Heidegger [mailto:m...@leichtgewicht.at]
Sent: Wednesday, February 22, 2012 3
> Another +1, it's good for quick wireframes and getting started
> > Right, Design View is very important to learn the Flex components
> > behaviours.
> > +1
> > Bruce Lane
+1 Also
Arturo Alvarado
I just remembered another thing that makes me a little mad every time I
read into coding with haXe:
var a: String= ...;
return a || "b";
// equals
return a != null ? a : "b";
is so incredibly comfortable in ActionScript3. And it can be 100%
syntatically right. And the ||= is even more
[
https://issues.apache.org/jira/browse/FLEX-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213668#comment-13213668
]
Carol Frampton commented on FLEX-14:
Please don't commit these changes until we finish ge
+1
On 2/22/12 9:38 AM, Eugene Diana wrote:
+1 on keeping DV alive
-Original Message-
From: Jason Batten [mailto:i...@jasonbatten.com]
Sent: Wednesday, February 22, 2012 5:18 AM
To: flex-dev@incubator.apache.org
Subject: Re: Adobe might think of open-sourcing the Design View if there
is
+1 on keeping DV alive
-Original Message-
From: Jason Batten [mailto:i...@jasonbatten.com]
Sent: Wednesday, February 22, 2012 5:18 AM
To: flex-dev@incubator.apache.org
Subject: Re: Adobe might think of open-sourcing the Design View if there
is sufficient interest
Another +1, it's good for
Thanks Nicolas,
I was the one who mentioned you in a post and wanted your inputs on "How we
could go about porting Flex to Haxe?".. I assumed that since you built Haxe
( duh! ) and that since Haxe is inspired by AS3, you would be able to
provide some deep insights into the migration of Flex to Hax
+1
I handle it as mandatory and always add missing semicolons when I work on
code written by others.
Haykel
Sorry the formatting of my post seems to have
gone. Hope it's still kind of readable
-Original Message-
From: Glenn Williams [mailto:i...@tinylion.co.uk]
Sent: 22 February 2012 14:14
To: flex-dev@incubator.apache.org
Subject: RE: Adobe might think of open-sourcing
the Design View if there
+1 for design view.
On Feb 22, 2012, at 9:08 AM, Pepe wrote:
> +1 for Design View
>
> 2012/2/22 Dimitri k. :
>> After the discussion on the ML about the Design View, I thought it would be
>> a good idea to ask Deepa at the Flex Paris meeting if Adobe could consider
>> to open-source it after th
I think the point the 'experienced user' dont use
DV is only true because DV was and is basically
broken.
I would have used it if:
When I clicked into DV it actually did display
what that part of my project looked like
When I clicked into DV I didnt just get a 'broken
image' and a list of reaso
+1 for Design View
2012/2/22 Dimitri k. :
> After the discussion on the ML about the Design View, I thought it would be
> a good idea to ask Deepa at the Flex Paris meeting if Adobe could consider
> to open-source it after the removal from next version of Flash Builder.
> Frédéric Thomas, also on
1 - 100 of 182 matches
Mail list logo
