Hi,
I just noticed that I was unable to use the mavenizer (aka flex-sdk-converter)
for Air 24 and 25. A short investigation resulted in the result that this is
probably only a problem on macs as Adobe changed the packaging of the AIR SDK
starting with version 24 and right now we don’t have any
On 5/5/17, 12:10 AM, "Christofer Dutz" wrote:
>Hi,
>
>I just noticed that I was unable to use the mavenizer (aka
>flex-sdk-converter) for Air 24 and 25. A short investigation resulted in
>the result that this is probably only a problem on macs as Adobe changed
>the packaging of the AIR SDK star
Maybe MDL should have its own set of layouts and layout-compliant
interfaces. Opinions?
‹peter
On 5/5/17, 2:15 AM, "piotrz" wrote:
>Hi Peter,
>
>I have found one scenario where there is a null pointer exception, but I'm
>not sure whether even we should cover such case. Let me know what do you
>t
Hi Alex,
Well I guess I could probably do that, but I am no fan of this. The Mavenizer
is platform independent and is generally able to provide the Mac SDK on a
Windows machine. Also, there are major drawbacks when starting OS processes
from within a Java VM. That’s why my implementation should
On 5/5/17, 8:02 AM, "Christofer Dutz" wrote:
>Hi Alex,
>
>Well I guess I could probably do that, but I am no fan of this. The
>Mavenizer is platform independent and is generally able to provide the
>Mac SDK on a Windows machine. Also, there are major drawbacks when
>starting OS processes from w
Well maybe that's not bad idea - to make similar set of layouts, but, what
would be the difference ?
In general MDL should be like our Basic set of components, should be able to
use such beads.
Maybe I should implement to the containers View parts and move there
appropriate logic. - In that case
If it opens a popup, it will mess up the mavenizer … at least in
non-interactive mode which CI servers require.
One more reason to implement it the way I am doing it … I know whenever I took
the easy path in the past it kept on coming back at me with support questions,
so I’ll prefer to do thin
On 5/5/17, 8:25 AM, "Christofer Dutz" wrote:
>If it opens a popup, it will mess up the mavenizer … at least in
>non-interactive mode which CI servers require.
>
>One more reason to implement it the way I am doing it … I know whenever I
>took the easy path in the past it kept on coming back at m
Well, the LayoutBase assume's the host/strand implements ILayoutParent and
provides the ILayoutHost. The ILayoutHost then provides the ILayoutView.
These can all be the same thing.
The layouts in Basic assume the items being laid out are ILayoutChild
compliant. So if MDL components followed that p
I will try to look into that deeply and probably will go through this path in
MDL.
Thanks Peter!
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Layouts-tp61120p61505.html
Sent from the Apache Flex Dev
10 matches
Mail list logo
