Hi Nick,
I was looking at the code from the link below and was noticing a couple of
things that might need to be considered when building for mobile devices.
Primarily the need for skins to be Multi-DPI capable. It doesn't seem like you
have taken this into account. Also I would suggest using t
Mazel tov, Martin!
On Mar 25, 2012 12:22 AM, "Yennick Trevels"
wrote:
> Gratz Martin!
>
> http://images3.wikia.nocookie.net/__cb20100501113730/warhammer40kfanon/images/e/ee/Official_Seal_of_Awesomeness.gif
>
Gratz Martin!
http://images3.wikia.nocookie.net/__cb20100501113730/warhammer40kfanon/images/e/ee/Official_Seal_of_Awesomeness.gif
On 3/24/12 3:41 AM, "imagene...@gmail.com" wrote:
> I am porting Flex to Starling with a fork of Starling that will have the
> additional functionality to support such a port. Besides that, I will
> attempt to get Flex working with Jangaroo. I have not looked into Jangaroo.
> To facilitate bot
After having a deeper look at as3commons-async I think it is pretty
unmature, however: I actually quite like the new threading API that uses
promises.
Imagine:
var serial: Async = new Async();
serial.
.next( thread.doSomething() ) // passes the Promise from
"thread.doSomething
Hooray for Martin! :) Seriously, he deserves it!
On 24 March 2012 23:08, Nicholas Kwiatkowski wrote:
> Hey Everybody!
>
> I wanted to formally introduce Martin Heidegger as our newest project
> committer. Martin has a few patches in JIRA, and has been very active on
> this mailing list.
>
> -Ni
Hey Everybody!
I wanted to formally introduce Martin Heidegger as our newest project
committer. Martin has a few patches in JIRA, and has been very active on
this mailing list.
-Nick Kwiatkowski
Apache Flex PPMC Member
An Apache Flex Twitter account that is sufficiently updated is a must
nowdays. I would'nt say "regularly updated" because it means "twit
anything, even if it doesn't have much value".
Even more than one could help staying more focused...
apacheFlex (news, events, general stuff)
apacheFlex_mailing
what about more than commit activity? what about ideas being passed around or
even worked on? new wiki pages?
Ariel Jakobovits
Email: arielj...@yahoo.com
Phone: 650-690-2213
Fax: 650-641-0031
Cell: 650-823-8699
From: Jun Heider
To: flex-dev@incubator.apache.o
On Mar 23, 2012, at 8:08 PM, Rick Winscot wrote:
> ...or tweet a digest of daily activity? Keep it interesting and highly
> focused and people will look forward to the info... The second people feel
> there is a bot behind the account - they'll un-follow.
>
> Rick Winscot
> On Mar 23, 2012 9:17 P
On 24 March 2012 19:42, Robert Smith wrote:
> Hi Cosma,
>
> It sounds like you really can't do much about the timing of your bootstrap
> if one call is dependent upon the result of your prior call. Even if you
> had threads available, you'd be waiting the same amount of time. So, I'm
> thinking
I agree with Sebastian. As long as both component sets remain available,
the argument is pretty moot. My personal opinion is that I'll take the
spark components and the power they provide over mx components any day.
In advertising, it's very helpful to have the extra capability to do
most anyth
Hi Cosma,
It sounds like you really can't do much about the timing of your
bootstrap if one call is dependent upon the result of your prior call.
Even if you had threads available, you'd be waiting the same amount of
time. So, I'm thinking the best you're going to get at this point is
some n
True. But the point I was trying to make was not about the power (which,
it is extremely powerful), but that it is powerful, even at
the introductory level. Making an Alert Box look like the iOS Alert Box in
Halo is damn near impossible without resorting to raster images -- which
don't scale, and
On Saturday, March 24, 2012, sébastien Paturel
wrote:
> Hey Adobe guys,
> Would'nt it be a good idea to make flash player rely fully on stage3D?
> it could make it more easy to target any new device as GPU apis are more
standard than others, and you only have to care about graphic cards and not
th
Thats just the thing
The example youve shown isn't really a very
different look than the standard one. Just
different images in basically the same component.
With spark skin you can make a component radically
different in ways that would be impossible in
halo.
Try for example in halo, taking t
I'd love to.
Take a look at some of the components that are being submitted via our own
SVN (in the whiteboard area). For example, the MobileAlert component I've
been writing uses Spark skinning, and in all honesty, it is pretty nice.
http://svn.apache.org/viewvc/incubator/flex/whiteboard/quetwo
+1 !! Hey, thats bizarre! I havent even know about Satrling and Jangaroo!
But yes, thats EXACTLY the point to Flex get over everything on the web!
Develop in Flex, run in HTML Canvas! Insane!
2012/3/24 sébastien Paturel
> Great initiative !
> I also believe that flex has a great future if we man
@William. A good example is an app I am working on now. It's not released
to the public yet, but when it does I will be sure to post a link here.
About samples online, not sure, but did you check
http://www.scalenine.com/gallery/ . It usually has good skin collections.
About mixing it, like I sai
Hey Adobe guys,
Would'nt it be a good idea to make flash player rely fully on stage3D?
it could make it more easy to target any new device as GPU apis are more
standard than others, and you only have to care about graphic cards and
not the mutliplicity of OS or navigators?
just a thought, mayb
i already started a discussion several weeks ago about it.
MX versus Spark war has no sens since flex could not stay without
separating ui logic and skin code. spark components had to be done.
Without Spark architecture, im not sure we would be able to target
mobile today.
The main issue here
Great initiative !
I also believe that flex has a great future if we manage to get it cross
compiled to HTML5 and maybe other platforms (video game platforms for
example).
The future is mutli screen (smart tv coming) and media merging in one
device (phone, computer, watch, videogame etc in one
+1
Le 24/03/2012 12:45, Jesus Barquin a écrit :
+1
2012/3/24 Paw Suddergaard
That is an awesome initiative!
Do you have a blog/twitter/xx where its possible to follow your work?
/paw
On Sat, Mar 24, 2012 at 11:41 AM, imagene...@gmail.com<
imagene...@gmail.com
wrote:
I am porting Flex to St
+1
2012/3/24 Paw Suddergaard
> That is an awesome initiative!
>
> Do you have a blog/twitter/xx where its possible to follow your work?
>
> /paw
>
> On Sat, Mar 24, 2012 at 11:41 AM, imagene...@gmail.com <
> imagene...@gmail.com
> > wrote:
>
> > I am porting Flex to Starling with a fork of Starl
That is an awesome initiative!
Do you have a blog/twitter/xx where its possible to follow your work?
/paw
On Sat, Mar 24, 2012 at 11:41 AM, imagene...@gmail.com wrote:
> I am porting Flex to Starling with a fork of Starling that will have the
> additional functionality to support such a port.
Oleg,
I'm not saying that the problems you are point are not there, but if we are
commeting between halo vs spark. I think the later is the way to go. MX was
a component set brought from the Flash MX and MX 2004 days. It has many
problems, more than spark.
If this discussion is about to choose a
Carlos,
I've just explained why using Spark skins sometimes is absolutely
impossible - they are literary order of magnitude bigger and slower then
their Halo counterparts. This may be a weak argument in the light of how
the entire framework is slow and bloated, but there are always certain
requirem
>
> You can't design and preview skins in Illustrator, Fireworks and Photoshop
> and export as FXG?
>
Only to the extent allowed by those programs, which, in many cases is
almost nothing (you need to be able to name your components in a particular
way in order for them to be displayed in the way i
I agree with the people that thinks that "spark was the best thing happen
in Flex4". Until Flex 4 skinning was limited and a pain. Right now skinning
is s much easy. Why people thinks the opposite let me think that they
does not understand how to use skinning in the right way.
For example I se
You can't design and preview skins in Illustrator, Fireworks and Photoshop and
export as FXG?
Tink
Left Right wrote:
>I think that the most important motivation behind new skinning system was
>that assets imported from Flash CS aren't editable / aren't fully editable
>in other editors comm
I think that the most important motivation behind new skinning system was
that assets imported from Flash CS aren't editable / aren't fully editable
in other editors commonly used for Flex framework. Since new skins are all
in plain text, they eliminate this restriction. However, several important
Spark has a lot of potential and for me personally, I never went back to
Flex 3.x mx skinning.
But your complaints are valid of course, simple skinning tasks can be very
cumbersome and 'visualizing' MXML code as you type it can be quite hard,
I briefly tried Catalyst but didn't end up using it,
32 matches
Mail list logo
