Re: [DISCUSSION] Design Mode for developers
Hi Igor, why would not you host your project somewhere on the web for other to play with it, say at mxml.flex.org domain ? Just my 5c. - Andriy On 16 June 2013 07:13, Cortlandt Winters wrote: > Igor, your Kung-Fu is always strong. > > > On Sat, Jun 15, 2013 at 6:56 PM, Igor Costa wrote: > > > Hi there fellows! > > > > Just trying to fill the gap left over Flash Builder in Design mode and I > > just wrote a simple > > GUI builder, that may or may not help developers out there. > > > > > > Please checkout over my Github repository: > > https://github.com/igorcosta/ApacheFlexUIBuilder > > > > > > Feel free to pull requests, fork and help. > > > > Best Regards > > > > Igor Costa > > www.igorcosta.com > > www.igorcosta.org > > >
Re: [FlexJS][FalconJX] MXML States
On 6/16/13 11:37 AM, "OmPrakash Muppirala" wrote: >On Jun 15, 2013 11:34 PM, "Alex Harui" wrote: >> >> >> >> On 6/15/13 7:36 PM, "OmPrakash Muppirala" wrote: >> > >> >I want to try and port some skins from the current Flex SDK. Does >>FlexJS >> >support FXG/MXMLG or is it just bitmap based CSS? >> FXG/MXMLG is not supported. I thought you were going to take on SVG >> skinning? >> > > >Yes, but that was under the assumption that we skin using FXG/MXMLG for >Flex and SVG for HTML. > >Were you thinking of using SVG for both? I was assuming you were going to figure that all out. I don't recall anyone saying that the FXG portion of Falcon was broken, so it is worth trying. I haven't tried it myself. It should generate an embedded asset. MXMLG support would require duplicating those classes and deciding on how/if to consolidate display objects for performance. Sounds like a significant chunk of work. Right now, the bitmap skinning relies on external image files and CSS. I guess an FXG/SVG skinning bead would use embedded FXG in the SWF and SVG in some form in JS. But anyway, it is pretty much up to you. I'm going to have my hands full with data binding. -Alex
Re: AW: [DISCUSS] Alerts and dialogs in Flex 4.x / Spark (was: Alerts and dialogs in FlexJS)
Very Cool Toaster component Maxime :)
2013/6/16 Maxime Cowez
> For those interested:
> I've had some fun creating another implementation of SkinnablePopUp: it's a
> Toaster that allows you to display toast-style messages.
> In its simplest form you use it like this:
>
>
>
>
>
>
>
> The positioning properties ('bottom' and 'right' in this example) are
> relative to the application.
>
> See it in action at http://riastar.github.io/SkinnablePopUpFx/ (it can
> be customized through custom item renderers and some addtional
> properties)
>
> Max
>
>
>
> On Sun, Jun 16, 2013 at 10:09 PM, Maxime Cowez >wrote:
>
> > @Carlos
> > > Maybe we could update it to get the benefits in your implementation to
> > get best of both worlds.
> >
> > I'll see what I can do from my end to integrate both approaches. I'll
> also
> > try to address some of the feedback I gathered here.
> >
> > @Christopher
> > > Regarding the callback-functionality, I would prefer the event based
> > approach over the old one where you provide the callbac functionality.
> >
> > There's nothing preventing us from providing both approaches. I never
> > liked that static function myself - which is why I created this Spark
> > implementation in the first place -, but who are we to tell people how to
> > instantiate alerts ;)
> >
> > > As far as I understood it, I can still programatically create Alerts
> > and addEventListeners for the CloseEvents. I would really like to be able
> > to continue to be able to create Alerts programatically.
> >
> > Yes you can:
> >
> > var alert:Alert = new Alert("my title", "my message");
> > alert.addEventListener(PopUpEvent.CLOSE, handleAlertClose);
> > alert.show();
> >
> > > Regarding the discussion of what Buttons the Allert should have, what
> > about implementing an abstract BaseAlert (or something similar that
> > contains a command-bar which can be filled with Buttons and a concrete
> > subclass Alert that mimics the functionality of the original Alert?
> >
> > I already did it that way, kind of. Only the base class is a bit more
> > generic than what you describe: it is a SkinnablePopUp which you can
> extend
> > to add whatever you want. But perhaps I should consider adding another
> base
> > class as you suggest in between.
> >
> > Max
> >
> >
> > On Tue, Jun 11, 2013 at 9:40 PM, Peter Ent wrote:
> >
> >> For FlexJS, the Alert will have an AlertModel where the title, message,
> >> and button labels will be stored. The model is assigned via style sheet
> >> (or programmatically) and the model can be changed dynamically. If you
> >> wanted something different or more generic, it will be possible to
> extend
> >> the AlertModel and add whatever else you'd like and then extend or
> replace
> >> the AlertBead to handle the extra layout or items.
> >>
> >> Peter Ent
> >> Flex SDK Team
> >> Adobe Systems
> >>
> >> On 6/11/13 4:15 AM, "christofer.d...@c-ware.de"
> >> wrote:
> >>
> >> >Regarding the callback-functionality, I would prefer the event based
> >> >approach over the old one where you provide the callbac functionality.
> >> >
> >> >As far as I understood it, I can still programatically create Alerts
> and
> >> >addEventListeners for the CloseEvents. I would really like to be able
> to
> >> >continue to be able to create Alerts programatically.
> >> >
> >> >Regarding the discussion of what Buttons the Allert should have, what
> >> >about implementing an abstract BaseAlert (or something similar that
> >> >contains a command-bar which can be filled with Buttons and a concrete
> >> >subclass Alert that mimics the functionality of the original Alert?
> >> >
> >> >Chris
> >> >
> >> >
> >> >Von: Maxime Cowez [maxime.co...@gmail.com]
> >> >Gesendet: Montag, 10. Juni 2013 22:08
> >> >An: dev@flex.apache.org
> >> >Betreff: [DISCUSS] Alerts and dialogs in Flex 4.x / Spark (was: Alerts
> >> >and dialogs in FlexJS)
> >> >
> >> >As we were discussing some options in the thread "Alerts and dialogs in
> >> >FlexJS", we started to elaborate on dialog implementation in general.
> >> This
> >> >was carrying us away from the initial question so I started this new
> >> >thread.
> >> >
> >> >One of the initial topics was the possibility to declare Alerts/Dialogs
> >> as
> >> >mxml tags instead of using the old static function, something like
> this:
> >> >
> >> >
> >> > >> >close="handleAlertClose(event)"/>
> >> >
> >> >
> >> >
> >> >
> >> >I mentioned that I had already created such an implementation, which
> can
> >> >be
> >> >found at https://github.com/RIAstar/SkinnablePopUpFx
> >> >There's also a live demo at http://riastar.github.io/SkinnablePopUpFx/
> >> >
> >> >Some people seemed to like the idea and asked some questions, which
> I'll
> >> >try to answer next.
> >> >
> >> >Max
> >>
> >>
> >
>
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es
Re: AW: [DISCUSS] Alerts and dialogs in Flex 4.x / Spark (was: Alerts and dialogs in FlexJS)
For those interested:
I've had some fun creating another implementation of SkinnablePopUp: it's a
Toaster that allows you to display toast-style messages.
In its simplest form you use it like this:
The positioning properties ('bottom' and 'right' in this example) are
relative to the application.
See it in action at http://riastar.github.io/SkinnablePopUpFx/ (it can
be customized through custom item renderers and some addtional
properties)
Max
On Sun, Jun 16, 2013 at 10:09 PM, Maxime Cowez wrote:
> @Carlos
> > Maybe we could update it to get the benefits in your implementation to
> get best of both worlds.
>
> I'll see what I can do from my end to integrate both approaches. I'll also
> try to address some of the feedback I gathered here.
>
> @Christopher
> > Regarding the callback-functionality, I would prefer the event based
> approach over the old one where you provide the callbac functionality.
>
> There's nothing preventing us from providing both approaches. I never
> liked that static function myself - which is why I created this Spark
> implementation in the first place -, but who are we to tell people how to
> instantiate alerts ;)
>
> > As far as I understood it, I can still programatically create Alerts
> and addEventListeners for the CloseEvents. I would really like to be able
> to continue to be able to create Alerts programatically.
>
> Yes you can:
>
> var alert:Alert = new Alert("my title", "my message");
> alert.addEventListener(PopUpEvent.CLOSE, handleAlertClose);
> alert.show();
>
> > Regarding the discussion of what Buttons the Allert should have, what
> about implementing an abstract BaseAlert (or something similar that
> contains a command-bar which can be filled with Buttons and a concrete
> subclass Alert that mimics the functionality of the original Alert?
>
> I already did it that way, kind of. Only the base class is a bit more
> generic than what you describe: it is a SkinnablePopUp which you can extend
> to add whatever you want. But perhaps I should consider adding another base
> class as you suggest in between.
>
> Max
>
>
> On Tue, Jun 11, 2013 at 9:40 PM, Peter Ent wrote:
>
>> For FlexJS, the Alert will have an AlertModel where the title, message,
>> and button labels will be stored. The model is assigned via style sheet
>> (or programmatically) and the model can be changed dynamically. If you
>> wanted something different or more generic, it will be possible to extend
>> the AlertModel and add whatever else you'd like and then extend or replace
>> the AlertBead to handle the extra layout or items.
>>
>> Peter Ent
>> Flex SDK Team
>> Adobe Systems
>>
>> On 6/11/13 4:15 AM, "christofer.d...@c-ware.de"
>> wrote:
>>
>> >Regarding the callback-functionality, I would prefer the event based
>> >approach over the old one where you provide the callbac functionality.
>> >
>> >As far as I understood it, I can still programatically create Alerts and
>> >addEventListeners for the CloseEvents. I would really like to be able to
>> >continue to be able to create Alerts programatically.
>> >
>> >Regarding the discussion of what Buttons the Allert should have, what
>> >about implementing an abstract BaseAlert (or something similar that
>> >contains a command-bar which can be filled with Buttons and a concrete
>> >subclass Alert that mimics the functionality of the original Alert?
>> >
>> >Chris
>> >
>> >
>> >Von: Maxime Cowez [maxime.co...@gmail.com]
>> >Gesendet: Montag, 10. Juni 2013 22:08
>> >An: dev@flex.apache.org
>> >Betreff: [DISCUSS] Alerts and dialogs in Flex 4.x / Spark (was: Alerts
>> >and dialogs in FlexJS)
>> >
>> >As we were discussing some options in the thread "Alerts and dialogs in
>> >FlexJS", we started to elaborate on dialog implementation in general.
>> This
>> >was carrying us away from the initial question so I started this new
>> >thread.
>> >
>> >One of the initial topics was the possibility to declare Alerts/Dialogs
>> as
>> >mxml tags instead of using the old static function, something like this:
>> >
>> >
>> >> >close="handleAlertClose(event)"/>
>> >
>> >
>> >
>> >
>> >I mentioned that I had already created such an implementation, which can
>> >be
>> >found at https://github.com/RIAstar/SkinnablePopUpFx
>> >There's also a live demo at http://riastar.github.io/SkinnablePopUpFx/
>> >
>> >Some people seemed to like the idea and asked some questions, which I'll
>> >try to answer next.
>> >
>> >Max
>>
>>
>
[jira] [Commented] (FLEX-33086) Make SDK build with Maven/Flexmojos and deploy release and snapshot artifacts to the Apache Maven repository
[ https://issues.apache.org/jira/browse/FLEX-33086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684771#comment-13684771 ] Alexander Rotnov commented on FLEX-33086: - Thanks for answer, Frédéric. There is no flexmojos 6.0.1 tag in github, only 6.1.0-snapshot in branch. Well, there is another problem to me: flexmojos compiled with jdk 1.6, while most of maven plugins required jdk 1.5+. All java projects I am worked on based on 1.5, and there is no possibility to migrate on 1.6 now. So I run maven using jdk 1.5, and have no troubles. But I can't run FM this way. So, I must run maven under jdk 1.6, and configure maven-compiler-plugin to use jdk 1.5 for each java project, because maven is one :) I think I can't using FM now for these reasons, and it made me sad :( > Make SDK build with Maven/Flexmojos and deploy release and snapshot artifacts > to the Apache Maven repository > > > Key: FLEX-33086 > URL: https://issues.apache.org/jira/browse/FLEX-33086 > Project: Apache Flex > Issue Type: Story >Reporter: Alex Harui > Time Spent: 2h > Remaining Estimate: 0h > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: AW: [DISCUSS] Alerts and dialogs in Flex 4.x / Spark (was: Alerts and dialogs in FlexJS)
@Carlos
> Maybe we could update it to get the benefits in your implementation to
get best of both worlds.
I'll see what I can do from my end to integrate both approaches. I'll also
try to address some of the feedback I gathered here.
@Christopher
> Regarding the callback-functionality, I would prefer the event based
approach over the old one where you provide the callbac functionality.
There's nothing preventing us from providing both approaches. I never liked
that static function myself - which is why I created this Spark
implementation in the first place -, but who are we to tell people how to
instantiate alerts ;)
> As far as I understood it, I can still programatically create Alerts and
addEventListeners for the CloseEvents. I would really like to be able to
continue to be able to create Alerts programatically.
Yes you can:
var alert:Alert = new Alert("my title", "my message");
alert.addEventListener(PopUpEvent.CLOSE, handleAlertClose);
alert.show();
> Regarding the discussion of what Buttons the Allert should have, what
about implementing an abstract BaseAlert (or something similar that
contains a command-bar which can be filled with Buttons and a concrete
subclass Alert that mimics the functionality of the original Alert?
I already did it that way, kind of. Only the base class is a bit more
generic than what you describe: it is a SkinnablePopUp which you can extend
to add whatever you want. But perhaps I should consider adding another base
class as you suggest in between.
Max
On Tue, Jun 11, 2013 at 9:40 PM, Peter Ent wrote:
> For FlexJS, the Alert will have an AlertModel where the title, message,
> and button labels will be stored. The model is assigned via style sheet
> (or programmatically) and the model can be changed dynamically. If you
> wanted something different or more generic, it will be possible to extend
> the AlertModel and add whatever else you'd like and then extend or replace
> the AlertBead to handle the extra layout or items.
>
> Peter Ent
> Flex SDK Team
> Adobe Systems
>
> On 6/11/13 4:15 AM, "christofer.d...@c-ware.de"
> wrote:
>
> >Regarding the callback-functionality, I would prefer the event based
> >approach over the old one where you provide the callbac functionality.
> >
> >As far as I understood it, I can still programatically create Alerts and
> >addEventListeners for the CloseEvents. I would really like to be able to
> >continue to be able to create Alerts programatically.
> >
> >Regarding the discussion of what Buttons the Allert should have, what
> >about implementing an abstract BaseAlert (or something similar that
> >contains a command-bar which can be filled with Buttons and a concrete
> >subclass Alert that mimics the functionality of the original Alert?
> >
> >Chris
> >
> >
> >Von: Maxime Cowez [maxime.co...@gmail.com]
> >Gesendet: Montag, 10. Juni 2013 22:08
> >An: dev@flex.apache.org
> >Betreff: [DISCUSS] Alerts and dialogs in Flex 4.x / Spark (was: Alerts
> >and dialogs in FlexJS)
> >
> >As we were discussing some options in the thread "Alerts and dialogs in
> >FlexJS", we started to elaborate on dialog implementation in general. This
> >was carrying us away from the initial question so I started this new
> >thread.
> >
> >One of the initial topics was the possibility to declare Alerts/Dialogs as
> >mxml tags instead of using the old static function, something like this:
> >
> >
> > >close="handleAlertClose(event)"/>
> >
> >
> >
> >
> >I mentioned that I had already created such an implementation, which can
> >be
> >found at https://github.com/RIAstar/SkinnablePopUpFx
> >There's also a live demo at http://riastar.github.io/SkinnablePopUpFx/
> >
> >Some people seemed to like the idea and asked some questions, which I'll
> >try to answer next.
> >
> >Max
>
>
Re: [FlexJS][FalconJX] MXML States
On Jun 15, 2013 11:34 PM, "Alex Harui" wrote: > > > > On 6/15/13 7:36 PM, "OmPrakash Muppirala" wrote: > > > >I want to try and port some skins from the current Flex SDK. Does FlexJS > >support FXG/MXMLG or is it just bitmap based CSS? > FXG/MXMLG is not supported. I thought you were going to take on SVG > skinning? > > Yes, but that was under the assumption that we skin using FXG/MXMLG for Flex and SVG for HTML. Were you thinking of using SVG for both? > >What kind of beautification are you taking about? > I'm don't think it looks as good as Spark or MX right now. Colors, > styles, spacing might make it look more like it is worth trying to use > this stuff. > Perhaps the designers in this list could help us design the next gen default look and feel for Flex? Any takers? Thanks, Om
