I know I didn't express my thoughts enough clear.
> Request.classes( classes.. );
Request.methods( class, methods...)
Wow Mike this is Awesome! :)
Thanks Mike and Alex!
Piotr
-
Apache Flex Committer
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-develop
>In flex unit 4 most of those information about test we have got into
>TestRunnerBase. When I add FU 4 to project I've simple removed all of those
>methods and UI for display information and I replaced it one line of code
>.
In FlexUnit4, the information doesn't do into TestRunnerBase really.
Thanks for working on it. If it is easier to hook most tests to cilistener that
is probably a good achievement. A custom runner for performance and memory
could probably wait.
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
piotrz wrote:
After a lot of modifications I've managed to
At some point a TextBlock is generated to create TextLines and then they
are added to the display list. You can try hanging on to them, but it
might mess up the recycler.
-Alex
On 4/6/14 10:50 AM, "Harbs" wrote:
>
>On Apr 6, 2014, at 8:28 PM, Alex Harui wrote:
>
>>> Does anyone have any concer
On Apr 6, 2014, at 8:28 PM, Alex Harui wrote:
>> Does anyone have any concerns with this approach?
> Performance and memory, of course. Don't know if pooling would help or
> avoiding spending too much time on cells that are off-screen.
I'd expect performance to be better for most cases. Cells w
On 4/6/14 2:42 AM, "Harbs" wrote:
>While working on TLF tables, I came to the conclusion that the simplest
>way to handle the composition is to create a separate TExtFlow for each
>cell in a table. The reason for this being that the composition of each
>cell is in fact completely separate from
I don't know of any. It would be great if you could document it.
On 4/6/14 5:27 AM, "Harbs" wrote:
>I'm referring more to the composition lifecycle. (i.e. Text is marked
>damaged by x, Class y is called to start compostion by y. Composition is
>started by z, the process continues with lmnop, et
I'm referring more to the composition lifecycle. (i.e. Text is marked damaged
by x, Class y is called to start compostion by y. Composition is started by z,
the process continues with lmnop, etc. How does ContainerController,
BaseCompose FlowComposer, etc. all interact with each other.)
It's re
This one maybe ?
http://help.adobe.com/en_US/as3/dev/WSb2ba3b1aad8a27b0-1b8898a412218ad3df9-8000.html
-Message d'origine-
De : Harbs [mailto:harbs.li...@gmail.com]
Envoyé : dimanche 6 avril 2014 12:55
À : dev
Objet : Docs on TLF composition?
While working on TLF, I constantly forget the
While working on TLF, I constantly forget the finer points of the composition
flow. It's highly inefficient to constantly step through the code to figure out
exactly what happens when and by what.
I'm thinking of putting together a doc which specifies the flow and how all the
classes work toget
I think the default of the css box model is broken by design.
I'd think the solution is simply to stick to using border-box.
http://css-tricks.com/box-sizing/
On Apr 4, 2014, at 9:54 PM, Peter Ent wrote:
> Hi,
>
> I've been working on a mobile app example for FlexJS as a way to try out the
> F
After a lot of modifications I've managed to run first test's class with Flex
Unit 4.2 RC3 -> AccessibilityMethodsTest.
But I need some confirmation about my direction. In TLF "automation_apps"
project we have "TestDescriptorRunner" which implements this interface ->
http://bit.ly/1jQwerN -> Thank
While working on TLF tables, I came to the conclusion that the simplest way to
handle the composition is to create a separate TExtFlow for each cell in a
table. The reason for this being that the composition of each cell is in fact
completely separate from the composition of the main text, and b
Hi Folks,
I just spent the past week or so trying to get Falcon integrated into FB.
It won't replace ASC2.0 as the code-model compiler. I'm just trying to
get FB to call Falcon when you build your project. It turns out that FB
doesn't call mxmlc directly and has a poorly documented interface des
14 matches
Mail list logo
