On 08/02/2012 16:44, Dany Dhondt wrote:
Correct me on this if I'm wrong but isn't it so that swf printing engine always
creates bitmaps? Is there any postscript handling?
-Dany
At least the api says that vectors are available too:
http://help.adobe.com/en_US/FlashPlatform/reference/actionscri
Correct me on this if I'm wrong but isn't it so that swf printing engine always
creates bitmaps? Is there any postscript handling?
-Dany
Op 8-feb.-2012, om 08:34 heeft Martin Heidegger het volgende geschreven:
> On 07/02/2012 11:32, Dany Dhondt wrote:
>> ... as long as the output is uncompromis
On Tue, Feb 7, 2012 at 11:09 PM, Martin Heidegger wrote:
> I think I am talking about this:
> http://gingerbinger.com/2010/07/actionscript-3-0-events-the-myth-of-useweakreference/
Nice read, thanks.
> Would you be interested in a working group: "Remove the weak"?
Sure, potentially. I certainly
On 07/02/2012 11:32, Dany Dhondt wrote:
... as long as the output is uncompromised and perfect.
As I have had (serious) problems with printing in flash my first step to
action would be a test as to how far the current printing solution works.
The user test suite should consist of a swf that
I think I am talking about this:
http://gingerbinger.com/2010/07/actionscript-3-0-events-the-myth-of-useweakreference/
Of course the mentioned example of me is irrelevant but that doesn't
make the current use of
weak references in the system less problematic.
Would you be interested in a worki
On 2/7/12 10:49 PM, "Martin Heidegger" wrote:
>
> Uhm, how can folks help you?
>
Someday, after we get all the code in and test suites running, I hope to
spend 2 days/week on my whiteboard re-write, 3 on shorter term improvements
that folks want including reviewing commits and patches. We'
On 08/02/2012 15:31, Alex Harui wrote:
You can have a back-door to replace singletons if you want to. That's even
easier to add to Singleton. For now though, keep in mind that because of
the stew of dependencies between classes in the framework, you really need
to restart the app or implement a
Trust me on this Doug, JIRA is far from being polished on many
administrative services, especially with their "data migration" which I
experienced the pain of it last week. *shiver*
M
On Tue, Feb 7, 2012 at 1:22 PM, Doug Arthur wrote:
> On Tue, Feb 7, 2012 at 10:23 AM, Omar Gonzalez
> wrote:
You can have a back-door to replace singletons if you want to. That's even
easier to add to Singleton. For now though, keep in mind that because of
the stew of dependencies between classes in the framework, you really need
to restart the app or implement a reset protocol, otherwise something migh
On 08/02/2012 15:02, Alex Harui wrote:
One way is to define another set of mixins that get initialized before
the SystemManager starts registering singletons.
In my whiteboard re-write, the Singletons will probably be defined in
some manifest, will only register just before first use, and there
On 2/7/12 10:22 AM, "Doug Arthur" wrote:
>
> Why would Jira be so difficult to import data from a minor version
> change??? Can we contact someone at Jira to assist with this?
I'm not sure it is intentionally difficult, it is probably that the project
import feature is not used often enough t
On 2/7/12 8:42 PM, "Martin Heidegger" wrote:
> This second part is the reason I wrote this. I am all ears as to how
> this can be fixed more easily!
One way is to define another set of mixins that get initialized before the
SystemManager starts registering singletons.
In my whiteboard re-writ
On 2/7/12 8:51 AM, "Michael A. Labriola"
wrote:
>>> So yeah, I'm all for some byte-code optimizations and some fudging of the
>>> language rules (so you really can inline a constant), but I am still hoping
>>> a class definition will be same everywhere so newbies have fewer >>things to
>>> lea
Internet Explorer 10 does enable Plugins but Metro(browser within the
new ui) does not - as for now. This is in sync with the decision of
Adobe to drop the mobile browser support: In other words: in modern
browser systems they want Flash Player to be gone. I am interested in
Air for Windows 8 t
On 08/02/2012 12:09, Alex Harui wrote:
I don't understand what this does other than what mx.core.Singleton already
does.
Actually there are two points: If you saw the small sample code: The use
of mx.core.Singleton is not just a simple redirect,
if (!_embeddedFontRegistry && !noEmbeddedFont
>
> There's a reason why IoC containers like SwiftSuspenders have a
> mapSingleton() method,...
>
And when I said that I actually meant the injector in Robotlegs:
https://github.com/robotlegs/robotlegs-framework/blob/8340bfda8d4e60a39617303a5fd09c4183c61de6/src/org/robotlegs/core/IInjector.as
-om
>
> And then there is the whole debate about Singletons in general...
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
I don't think the issue a lot of devs have with Singletons is actually with
the concept of Singletons itself but the implementation in wh
On 2/7/12 11:33 AM, "Martin Heidegger" wrote:
> This means to me: Any use of
> weak Dictionaries and weak event listeners would need to vanish from the
> Flex SDK to actually make it portable.
>
> I just wanted to point that out. It might be interesting to a few.
>
> And related to that two
On 2/7/12 12:11 PM, "Martin Heidegger" wrote:
> Hello List,
>
> when thinking about unit testing of Flex components I got a strong
> argument against it due to the heavy use of Singletons throughout the
> project. I think I might have a good refactoring path to ease the
> transition from the
On Tue, Feb 7, 2012 at 4:08 PM, FRANKLIN GARZON wrote:
>
> Good day, any people know what was at the end? Adobe Flash will stay into
> windows 8 metro too? (Internet Explorer 10).
>
>
> Franklin Garzón
>
> Regional Development Manager
>
> MCITP Microsoft SQLServer
>
>
> *Si el hombre dejara de a
Good day, any people know what was at the end? Adobe Flash will stay into
windows 8 metro too? (Internet Explorer 10).
Franklin Garzón
Regional Development Manager
MCITP Microsoft SQLServer
*Si el hombre dejara de aprender entonces dejaría de existir*
094496862
+1 for Piergiorgio
:)
Il giorno 07 febbraio 2012 08:54, Piergiorgio Niero <
piergiorgio.ni...@gmail.com> ha scritto:
> my humble opinion is:
> all threads are discussion, if we're going to have many threads on a
> specific topic just move those threads in another mailing list.
> special thin
>The dependency injection requires to rewrite a lot without having unit test on
>the way. I think at the end of mentioned process we could simply switch to a
>DI model.
To me it looks like the opposite. I think the amount of rewrite here would be
more than injecting dependencies. Just my though
> Ah, I guess I should go to bed, gn8
You were right up to Flash Player 8 ;)
http://www.adobe.com/devnet/flashplayer/articles/garbage_collection.html
(that's when FP switched from ref counting to mark-and-sweep, which
avoids problems with circular references)
Still, weak references are certainl
On 08/02/2012 05:36, Maciek Sakrejda wrote:
How so?...
My very tired brain pictures a implementation like:
class EventDispatcher {
private var _listeners: Object = {};
public function addEventListener(event: String, listener: Function) {
if((_listeners[event] ||= []).indexOf(listener)
> Yeah, its funny how such a language construct actually is implemented in
> Firefox without the world knowing. Chrome/Opera and IE have nothing alike.
> However: It will not become standard before the release of IE10 and
> therefore will take - estimate at least more 5 years
> until it can be safe
On 08/02/2012 05:20, Michael A. Labriola wrote:
Or, if you were going to go through all of that refactoring, you could
use a dependency injection rather than service locator pattern
The dependency injection requires to rewrite a lot without having unit
test on the way. I think at the end of men
Personally, that's a long time I think that destructors would be beneficial :p
Frédéric THOMAS
> Date: Wed, 8 Feb 2012 05:29:31 +0900
> From: m...@leichtgewicht.at
> To: flex-dev@incubator.apache.org
> Subject: Re: JavaScript VS. Weak references
>
> On 08/02/2012 05:21, Frédéric THOMAS wrote:
>
On 08/02/2012 05:21, Frédéric THOMAS wrote:
In the section "Circular references collection" it's explained that the
reference is cleaned up when the outer element dies but may be is not what you looked for
?
Frédéric THOMAS
Ah! Now I understand the meaning. Its quite late here, should be in
b
On 08/02/2012 05:14, Maciek Sakrejda wrote:
Weak references are on the horizon for JS:
http://wiki.ecmascript.org/doku.php?id=harmony:weak_maps#weakmap
Yeah, its funny how such a language construct actually is implemented in
Firefox without the world knowing. Chrome/Opera and IE have nothing ali
In the section "Circular references collection" it's explained that the
reference is cleaned up when the outer element dies but may be is not what you
looked for ?
Frédéric THOMAS
> Date: Wed, 8 Feb 2012 05:09:45 +0900
> From: m...@leichtgewicht.at
> To: flex-dev@incubator.apache.org
> Subject
>>when thinking about unit testing of Flex components I got a strong argument
>>against it due to the heavy use of Singletons throughout the project. I think
>>I might have a good refactoring path to ease the transition >>from the
>>current code to a code that might be easier manageable.
Or, if
Weak references are on the horizon for JS:
http://wiki.ecmascript.org/doku.php?id=harmony:weak_maps#weakmap
> And related to that two questions:
> 1) Does anyone know how browsers avoid memory leaks with addEventListener ?
Not all listeners have to be weak references. If what you're listening
to
Hello List,
when thinking about unit testing of Flex components I got a strong
argument against it due to the heavy use of Singletons throughout the
project. I think I might have a good refactoring path to ease the
transition from the current code to a code that might be easier manageable.
T
The content of the link says nothing about "addEventlistener".
yours
Martin.
On 08/02/2012 05:03, Frédéric THOMAS wrote:
I guess you will have element of response here
http://javascript.info/tutorial/memory-leaks
Frédéric THOMAS
Hello List,
when I recently thought about a way to get AS3 code to JavaScript I got
into a major concept problem related to Weak references. As maybe most
of you know weak references are not supported by JavaScript. However:
The current code using addEventListener() relies heavily on weak
ref
Update: Was told by the infrastructure team that this has to wait until
this weekend so that it doesn't interrupt any other projects using the
repository.
Carol
On 2/6/12 2 :48PM, "Carol Frampton" wrote:
>The svn dumpfile for the Adobe Flex frameworks directory was just
>uploaded to Apache and
On Tue, Feb 7, 2012 at 10:23 AM, Omar Gonzalez
wrote:
> On Tuesday, February 7, 2012, Justin Mclean
> wrote:
>> Hi,
>>
>>> The import file contains SDK, FLEXDMV and FLEXENT bugs. Did I miss a
> project?
>> I honestly don't know. I was under the understanding (obviously mistaken)
> that only the
I have put the proposal in a Random Thoughts subpage [1].
Enjoy!
yours
Martin.
[1] https://cwiki.apache.org/confluence/display/FLEX/Random+Thoughts
> I'm not sure if the Wiki is the place for proposals.
I think it makes sense. Nice way to get thoughts from emails aggregated, and
even if an idea is not implemented, there is a place to come and find it and
revive it someday.
Ariel Jakobovits
Email: arielj...@yahoo.com
Phone: 650-690-2213
Fa
On Tuesday, February 7, 2012, Bertrand Delacretaz
wrote:
> On Tue, Feb 7, 2012 at 6:57 PM, Martin Heidegger
wrote:
>> On 08/02/2012 02:51, Omar Gonzalez wrote:
>>> I'm not sure if the Wiki is the place for proposals. If we put every
thing
>>> that everyone thinks about in the wiki as a Proposal w
On 08/02/2012 02:59, Michel Boudreau wrote:
Can I ask what
particular issue you're having?
Hello Michel,
it would be nice if you read the proposal. I expressed the "why" and a
bunch of code that does not involve properties passed in by the
compiler. I personally need it for a more comfortabl
On Tue, Feb 7, 2012 at 6:57 PM, Martin Heidegger wrote:
> On 08/02/2012 02:51, Omar Gonzalez wrote:
>> I'm not sure if the Wiki is the place for proposals. If we put every thing
>> that everyone thinks about in the wiki as a Proposal we are going to have a
>> lot of wiki stuff I go through. Who ke
I would agree, they are not the easiest to integrate. Can I ask what
particular issue you're having? I personally like to not use compile time
variables and use an external XML to load variables through Parsley, which
then injects it automatically into wherever I need it. Maybe that would be
mor
On 08/02/2012 02:51, Omar Gonzalez wrote:
I'm not sure if the Wiki is the place for proposals. If we put every
thing that everyone thinks about in the wiki as a Proposal we are
going to have a lot of wiki stuff I go through. Who keeps it updated?
How de we know it's still in progress or that so
On Tuesday, February 7, 2012, Martin Heidegger wrote:
> Hello everybody,
>
> in the sense of making progress I tried to write down the feature I want
to implement in the compiler once the compiler source & tests are available.
> I am not sure if I abused the wiki for that.
>
>
https://cwiki.apache
Hello Michel,
The defined properties are just a small fraction of data that is
available at compile time and they are not particularly easy to integrate.
yours
Martin.
Don't compiler variables do this already with compiler.define?
-compiler.define
> alias -define
> define a global AS3 conditional compilation definition, e.g.
> -define=CONFIG::debugging,true or -define+=CONFIG::debugging,true (to
> append to existing definitions in flex-config.xml) (advanced,
>
Hello everybody,
in the sense of making progress I tried to write down the feature I want
to implement in the compiler once the compiler source & tests are available.
I am not sure if I abused the wiki for that.
https://cwiki.apache.org/confluence/display/FLEX/Compile-time-data+injection
your
Hi Michael,
I think you're completely right, and I feel the same problems as you
comment. This new way under Apache should bring us all this new things many
advanced devs are waiting while keeping what made flex great. Evolution of
composition vs inheritance, bytecode manipulation, AOP, metadata,
On Tuesday, February 7, 2012, Justin Mclean
wrote:
> Hi,
>
>> The import file contains SDK, FLEXDMV and FLEXENT bugs. Did I miss a
project?
> I honestly don't know. I was under the understanding (obviously mistaken)
that only the SDK bugs were in the first import and the rest were due to be
impor
>>So yeah, I'm all for some byte-code optimizations and some fudging of the
>>language rules (so you really can inline a constant), but I am still hoping a
>>class definition will be same everywhere so newbies have fewer >>things to
>>learn to be successful with Flex.
Understood but I think tha
If Adobe would have chosen another comunication strategy probably
Flex/Flash wouldn't be in this situation.
They announced at the same time the stop of the development of the
FlashPlayer for mobile and then the release ofFlex to Apache...
We all know that are 2 complete different issues but the wor
On 2/7/12 6:45 AM, "Michael A. Labriola"
wrote:
>
> I understand your position, however, I really think that some of the byte code
> approaches could get us very maintainable code and speed of execution. That's
> why I am so interested in this approach. Honestly, with a really good
> optimizi
> In
> my company we keep using Flex 3, we didn't even switch to 4, cause it
> isn't really worth the effort (IMHO).
Oops. It was worth it.
Ariel Jakobovits
ajako...@adobe.com
650-350-0282
On Feb 7, 2012, at 5:23 AM, Piotr Kawiak wrote:
> I totally agree with Alex. I am working in a large comp
>>Under the looser Wikipedia definition, the current mustella test suite (note
>>that I have not called it a unit testing framework on this mailing list) has
>>tests for the major classes in the framework. When you finally see >>the
>>code, there is a class called UnitTester that contains a set
Hi,
> Nothing specific at this time. Mainly, I will be willing to break
> compatibility to achieve a significant goal, whether it is performance, DI,
> unit-testing, cross-compilation to HTML/CSS/JS, accessibility, size, etc.
I have no issue with that as long as the upgrade/conversion path is rel
Hi,
> The import file contains SDK, FLEXDMV and FLEXENT bugs. Did I miss a project?
I honestly don't know. I was under the understanding (obviously mistaken) that
only the SDK bugs were in the first import and the rest were due to be imported
end of the month.
> I'm trying to see if I can find
If that's (or will be) a vote, +1 for Alex's proposal!
About newbies and getting up to speed, I don't think that will be even
comparable to learning (Java) Spring or Hibernate, and with a good
instructor/training, it's not that difficult either. I'm all for more
configuration on the minus side if
On 2/7/12 2:04 AM, "Justin Mclean" wrote:
> Hi,
>
> Good news.
>
>
> Given that the initial list of bugs to be imported is now about 3 weeks away
> and that's not the full list (it's only the SDK bugs - please correct me if I
> wrong here) it's going to be something like 4 or 5 weeks until
I totally agree with Alex. I am working in a large company on
enterprise scale project with Flex GUI and I'd love 'new' Flex to be
backwards compatible, but this sure looks like an enormous effort. In
my company we keep using Flex 3, we didn't even switch to 4, cause it
isn't really worth the effor
On 2/6/12 8:51 PM, "Justin Mclean" wrote:
> Anything in particular you thinking of breaking or is this just a general
> statement and more long term than short term thinking?
Nothing specific at this time. Mainly, I will be willing to break
compatibility to achieve a significant goal, whether
On Tue, Feb 7, 2012 at 11:53 AM, Marcus Fritze
wrote:
> Please don't kill me for this question, but why doesn't Apache update the
> JIRA from 4.4.1 to 4.4.4? So we could import this file (thie Flex JIRA import
> file) easily (without hacking XML's) and I think it's better (to update from
> 4.4.
Please don't kill me for this question, but why doesn't Apache update the JIRA
from 4.4.1 to 4.4.4? So we could import this file (thie Flex JIRA import file)
easily (without hacking XML's) and I think it's better (to update from 4.4.4 to
5.0 instead of 4.4.1 to 5.0) for the following JIRA 5.0 up
On Tue, Feb 7, 2012 at 11:04 AM, Justin Mclean wrote:
> ...So the question is now do we hold off submitting patches to know bugs (ie
> those documented in Adobe's JIRA) until all of them have been imported or do
> we go ahead and enter patches to bugs that might be duplicates and do a bit
> of
On Mon, Feb 6, 2012 at 7:53 PM, jude wrote:
> ...We need a wiki that allows people to contribute to it, we need a blog
> updated so people can stay up to date without being on the mailing list, we
> need a FAQ to answer questions we've had before, we need to allow
> non-commiters to have white boa
Hi,
Good news.
> Ideally issues that don't overlap what's going to be imported, or we'll have
> to merge after the import.
Ideally sure but then ideally the bug base would of been imported by now. I'm
sure I'm not the only person who want to contribute to improve the current Flex
SDK by submit
On Mon, Feb 6, 2012 at 10:41 PM, Justin Mclean wrote:
> ...So is the consensus still that we hold off using JIRA until the end of
> this month (at a minimum)? I'd suggest we just start using JIRA now and sort
> out duplicates bugs etc after the import...
As mentioned at INFRA-4380, Tony says he
I'm aware of the existing options, but what I was suggesting is to use
these options that are low-level to make printing easier in Flex. For
example handling all the scaling and splitting into multiple pages based on
user's settings. But more interesting would be to add a way of defining
media-type
69 matches
Mail list logo
