On 10/17/14, 4:42 PM, "OmPrakash Muppirala" wrote:
>>
>> (assuming you size it and don’t scale it).
>>
>
>I think this is the key. Scaling is so much more easier to do than resize
>each and every element.
Maybe I don’t understand what that means. One of the main benefits of
vector graphics is
>
> (assuming you size it and don’t scale it).
>
I think this is the key. Scaling is so much more easier to do than resize
each and every element.
Both on the Flash and the SVG side, the power and flexibility comes from
the fact that they are inherently scalable. Your resizing approach would
en
On 10/17/14, 1:31 PM, "OmPrakash Muppirala" wrote:
>
>Specifying percentages or LTRB does not the solve the problem of
>maintaining the stroke thickness while scaling. When buttons scale, we
>want the stroke widths to remain same. That is where 9-slice helps. If
>not, you will have to specif
On Fri, Oct 17, 2014 at 1:31 PM, OmPrakash Muppirala
wrote:
> On Thu, Oct 16, 2014 at 10:37 PM, Alex Harui wrote:
>
>>
>>
>> On 10/16/14, 1:04 PM, "OmPrakash Muppirala" wrote:
>>
>> >On Thu, Oct 16, 2014 at 12:49 PM, Alex Harui wrote:
>> >
>> >>
>> >>
>> >> On 10/16/14, 12:30 PM, "OmPrakash Mu
On Thu, Oct 16, 2014 at 10:37 PM, Alex Harui wrote:
>
>
> On 10/16/14, 1:04 PM, "OmPrakash Muppirala" wrote:
>
> >On Thu, Oct 16, 2014 at 12:49 PM, Alex Harui wrote:
> >
> >>
> >>
> >> On 10/16/14, 12:30 PM, "OmPrakash Muppirala"
> >>wrote:
> >>
> >> >
> >> >Agreed, there does not have to be j
I do. Resizable buttons are critical for localization. The button labels can be
drastically different sizes, and the buttons need to resize to fit the
different labels.
On Oct 17, 2014, at 8:37 AM, Alex Harui wrote:
> One other question: having resizable button skins is great for prototyping
>
On 10/16/14, 1:04 PM, "OmPrakash Muppirala" wrote:
>On Thu, Oct 16, 2014 at 12:49 PM, Alex Harui wrote:
>
>>
>>
>> On 10/16/14, 12:30 PM, "OmPrakash Muppirala"
>>wrote:
>>
>> >
>> >Agreed, there does not have to be just one approach. Most common use
>>of
>> >9-slice skinning would be in butt
On Thu, Oct 16, 2014 at 12:49 PM, Alex Harui wrote:
>
>
> On 10/16/14, 12:30 PM, "OmPrakash Muppirala" wrote:
>
> >
> >Agreed, there does not have to be just one approach. Most common use of
> >9-slice skinning would be in buttons, scroll bars, title bars, icons, etc.
> >It should be possible t
On 10/16/14, 12:30 PM, "OmPrakash Muppirala" wrote:
>
>Agreed, there does not have to be just one approach. Most common use of
>9-slice skinning would be in buttons, scroll bars, title bars, icons, etc.
>It should be possible to add this support in a separate namespace.
Just curious: If you h
On Thu, Oct 16, 2014 at 12:03 PM, Alex Harui wrote:
> Thanks for that info on Jquery and Dojo. Do they have skinning models?
> How does it work?
>
>
Styling is strictly through CSS. There are no other skinning model, per
se.
> More inline..
>
>
> On 10/16/14, 11:29 AM, "OmPrakash Muppirala"
Thanks for that info on Jquery and Dojo. Do they have skinning models?
How does it work?
More inline..
On 10/16/14, 11:29 AM, "OmPrakash Muppirala" wrote:
>I understand that you want to use the default HTML elements as building
>blocks. I think there are major problems with this approach.
>
I understand that you want to use the default HTML elements as building
blocks. I think there are major problems with this approach.
First of all, there are only a small set of default input types UI elements:
button, checkbox, radio and text.
HTML5 adds a few more UI elements:
color, date, date
Ah yes, skinning in FlexJS.
The general guidance for doing anything in FlexJS is to first consider
what is possible/practical/popular on the HTML/JS/CSS side, find the
patterns, propose encapsulations, then figure out how to implement that in
AS.
I’ve never promised FlexJS would offer Spark-like
I have checked in the required changes to support FXG/MXMLG style drawing
in FlexJS. I have also updated the chart classes to accommodate for these
changes so that they continue to work properly.
Next up, figure out how to skin a component in FlexJS!
Thoughts, suggestions?
Thanks,
Om
On Wed, O
On 10/15/14, 2:53 PM, "OmPrakash Muppirala" wrote:
>
>On the JS side, I now have GraphicShape extend UIBase as well. I added
>the
>same exact code path as in the AS version.
>
>We now have FXG like drawing on both Flash and HTML5/SVG with close to
>100%
>fidelity :-)
Sweet!
-Alex
On Wed, Oct 15, 2014 at 7:53 AM, Alex Harui wrote:
> Did you try it? It should have at least compiled. What error did you get?
>
> In FlexJS, MXML is not converted to code, but the net result should be
> equivalent to:
>
> var comp:Object = new Rect();
> this[“myRect”] = comp;
> comp.width = 30
On Oct 15, 2014 8:34 AM, "Peter Ent" wrote:
>
> I just checked in a change to the GraphicShape.js to include setters for x
> and y; ActionScript already had them as a result of inheritance. I needed
> to have them to change the origin of the so I could draw chart axes
> graphics in the right loca
I just checked in a change to the GraphicShape.js to include setters for x
and y; ActionScript already had them as a result of inheritance. I needed
to have them to change the origin of the so I could draw chart axes
graphics in the right location.
I think that change would have been necessary gi
Did you try it? It should have at least compiled. What error did you get?
In FlexJS, MXML is not converted to code, but the net result should be
equivalent to:
var comp:Object = new Rect();
this[“myRect”] = comp;
comp.width = 300;
comp.height = 300;
comp.x = 10;
comp.y = 10;
var comp2:Object =
How does it currently work with FXG and Flash?
On Oct 15, 2014, at 11:05 AM, OmPrakash Muppirala wrote:
> I am quite satisfied with the way the drawing APIs are shaping up. Before
> I continue adding more APIs, I would like to make them work from MXML so
> that I can start importing some real g
20 matches
Mail list logo