Thanks a lot everyone for listening!
I'm just a poor CSS developer, I'm afraid I can't really contribute yet.
All I can do is beg for full CSS support:
(some of this logic may be a bit off, but I hope y'all understand
nonetheless)
1. Positioning items in a row:
<s:layout>
<s:HorizontalLayout />
</s:layout>
Oughta be: #column-chart { display: inline; }
2. Hiding shadows:
<mx:seriesFilters>
<fx:Array />
</mx:seriesFilters>
Oughta be: #column-chart { box-shadow: none; }
Or: .drop-shadow { display: none; }
3. Hiding grid lines:
<mx:backgroundElements>
<fx:Array />
</mx:backgroundElements>
Oughta be: .grid-lines { display: none; }
4. Hiding axis lines and tick placements:
<mx:horizontalAxisRenderers>
<mx:AxisRenderer id="horizontalAxis" axis="{chart.horizontalAxis}"
showLine="false" tickPlacement="none" />
</mx:horizontalAxisRenderers>
<mx:verticalAxisRenderers>
<mx:AxisRenderer id="verticalAxis" axis="{chart.verticalAxis}"
showLine="false" tickPlacement="none" />
</mx:verticalAxisRenderers>
Oughta be:
#horizontal-axis-renderer.gridlines,
#horizontal-axis-renderer.tick-placements,
#vertical-axis-renderer.gridlines,
#vertical-axis-renderer.tick-placements { display: none; }
8. No made up declaration names (make those selectors instead):
.myAxisStyles { showLine: false; tickPlacement: none; }
Oughta be: .axis-lines, .tick-placements { display: none; }
5. Use real size units:
mx|DataTip { paddingLeft: 3; paddingTop: 3; }
Oughta be: .datatip { padding-left: 3px; padding-top: 3px; }
7. Support CSS shorthand:
.datatip { padding: 3px 0 0 3px; }
Thanks again!
--Dwayne
On Tue, Jan 17, 2012 at 10:35 AM, David Arno <da...@davidarno.org> wrote:
> > From: Dwayne Henderson [mailto:its.code.in.h...@gmail.com]
> > Sent: 17 January 2012 00:17
> >
> > Does anybody know if this will change?
> > Are there any new Flex charting libraries in the making?
>
> +1 to what Roland said. If you feel up to it, get writing them yourself and
> submit them. It's the best way of ensuring that a new Flex charting library
> gets written. Even if you don't think your skills are up to it, you can
> still help by documenting what you think is wrong with the current ones and
> how they could be improved. This may well spur someone else to get
> involved.
> Adobe Flex work isn't just confined to committers (I'm not one after all):
> everyone in the Flex community is encouraged to take part. :)
>
> David.
>
>
