flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maurice Amsellem <maurice.amsel...@systar.com>
Subject RE: Feedback on SDK 4.10 Callout component
Date Thu, 01 Aug 2013 09:47:21 GMT
Hi, I have made some small "improvements" to experimental spark Callout component:

- Increased the size of the arrow to 24 instead of 18, as it was really too tiny.  This should
be styleable however.
- Display the arrow as dark outline on white background instead of plain black, so that the
callout looks more like a callout (see attached image).

If you are interested, I can contribute the change.  Should I open a JIRA for that and submit
a patch ? 


-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com] 
Envoyé : jeudi 1 août 2013 02:21
À : users@flex.apache.org
Objet : RE: Feedback on SDK 4.10 Callout component

Thank you Justin for the quick answer, and  the consideration.

I have raised a JIRA per your request: https://issues.apache.org/jira/browse/FLEX-33642



-----Message d'origine-----
De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : jeudi 1 août 2013 02:06
À : users@flex.apache.org Objet : Re: Feedback on SDK 4.10 Callout component


Thanks for the feedback.

> -          Leaves a lot of trace statements in debug mode.  Maybe this is on purpose
as it's an experimental component, but it's rather annoying.
Annoying no more - I've just commented them out.

> -          Is not part of spark manifest (s), or any one manifest, so it creates "components"
namespace pointing to "spark.components.*".  I was used to short namespaces for core flex
components. Once again, maybe this was done on purpose.
It should really be part of the experimental name space/manifest, we'll see if we can clean
that up for the next release.

> -          The callout frame and arrow are displayed in black by default, and changing
the application's chrome-color does not affect it.   Other spark components have dark gray
outlines by default.  So maybe it was on purpose, or maybe it's because of the mobile origin
of the Callout component.
Mind raising a JIRA issue for this.


  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message