Re: Cairngorm framework

2019-10-17 Thread Takeshita Shoichiro 
Carlos, I do not know at moment how difficult it is.  So, firstly, I will
investigate the use of Crux with help of Greg.

2019年10月17日(木) 17:07 Carlos Rovira :

> Takehista,
>
> if you go for the emulation of Cairngorm, please, consider to donate it to
> the Royale. I'm sure others would want to use to migrate to.
> Thanks
>
> El jue., 17 oct. 2019 a las 8:36, Takeshita Shoichiro ()
> escribió:
>
>> Alex and Greg, thanks.
>>
>> 2019年10月17日(木) 14:33 Greg Dove :
>>
>>>
>>> Fwiw I did also look at Cairngorm before I ended up using Crux. iirc I
>>> think there might be some ADDED and REMOVED events for the views support
>>> that probably need to be addressed if you are using the views support.
>>> Crux has a stage events emulator that does that for
>>> addedToStage/removedFromStage, but ADDED and REMOVED are more about
>>> child/parent changes than about 'stage' I think.
>>>
>>> I used Crux mainly because I knew I could get it to work without any
>>> problems, and because I had other more critical issues to address (getting
>>> the Adobe rss syndication lib working, and in particular, the way it was
>>> being used in the app )
>>>
>>>
>>> On Thu, Oct 17, 2019 at 6:09 PM Alex Harui  wrote:
>>>
 Yes, if you want to emulate Cairngorm, get the source and build it with
 Flex so you know you have all of the pieces.



 Then, back up the source in case you need to go back and start
 replacing the import flash.*.* with Royale imports.  For example:



   Import flash.events.EventDispatcher;



 Would be replaced by



   Import org.apache.royale.events.EventDispatcher;





 If you have a question about what class to use as a replacement, ask on
 d...@royale.apache.org.  Then try to compile with Royale and see what
 kinds of errors you get.  If you don’t need the functionality in the code
 that has a compile error, one option is to comment it out.  For example, I
 just emulated WebService and commented out all of the flash.xml.XMLDocument
 support because I don’t think many people used it.



 Good luck,

 -Alex



 *From: *Takeshita Shoichiro 
 *Reply-To: *"users@royale.apache.org" 
 *Date: *Wednesday, October 16, 2019 at 8:37 PM
 *To: *"users@royale.apache.org" 
 *Subject: *Re: Cairngorm framework



 Alex, I have a question re Cairngorm emulation?



 I think  I need to put the Cairngorm source in the Royale project src
 folder.  Then, what should I do?



 Thanks for your advice.



 2019年10月14日(月) 16:47 Takeshita Shoichiro :

 Carlos, thanks.



 I am very glad to hear that.



 Then, no hesitation to use Crux.



 2019年10月14日(月) 16:43 Carlos Rovira :

 Hi Takeshita,



 I'll try to answer your questions



 El lun., 14 oct. 2019 a las 8:08, Takeshita Shoichiro (<
 jl03...@gmail.com>) escribió:



 1. Does Apache Royale contain almost the ready-to-use emulation code
 for Swiz?  Or do we need more work for Apache Royale SDK?



 Yes. Swiz is ported to Royale (not emulated) and called Crux. So Crux
 is ready to use for you right now. No more work are needed for Royale in
 that line unless you report some bug around it.



 2. Is the use of Jewel required?  Or is it possible also with existing
 MXML code?





 Jewel is not required. In Royale you are not tied to only one UI Set
 like in Flex. You have several ones to choose. You can use emulation
 components for MX/Spark, Basic, Jewel, MDL



 If you use MXRoyale, you'll get a near 0% code changes, but your
 application will look black/white unless you try to improve the look and
 feel.

 In exchange, Jewel will requiere you to recode you visual code, what
 means in most cases very easy changes, but is not as direct as MXRoyale, in
 exchange you get a more good looking interface since Jewel is crafted with
 look and feel and themes in mind.










 --

 Carlos Rovira

 http://about.me/carlosrovira
 



 --

 Shoichiro Takeshita
 武下 祥一郎

 --

 Shoichiro Takeshita
 武下 祥一郎

>>> --
>> Shoichiro Takeshita
>> 武下 祥一郎
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
> --
Shoichiro Takeshita
武下 祥一郎

Re: Cairngorm framework

2019-10-17 Thread Carlos Rovira 
Takehista,

if you go for the emulation of Cairngorm, please, consider to donate it to
the Royale. I'm sure others would want to use to migrate to.
Thanks

El jue., 17 oct. 2019 a las 8:36, Takeshita Shoichiro ()
escribió:

> Alex and Greg, thanks.
>
> 2019年10月17日(木) 14:33 Greg Dove :
>
>>
>> Fwiw I did also look at Cairngorm before I ended up using Crux. iirc I
>> think there might be some ADDED and REMOVED events for the views support
>> that probably need to be addressed if you are using the views support.
>> Crux has a stage events emulator that does that for
>> addedToStage/removedFromStage, but ADDED and REMOVED are more about
>> child/parent changes than about 'stage' I think.
>>
>> I used Crux mainly because I knew I could get it to work without any
>> problems, and because I had other more critical issues to address (getting
>> the Adobe rss syndication lib working, and in particular, the way it was
>> being used in the app )
>>
>>
>> On Thu, Oct 17, 2019 at 6:09 PM Alex Harui  wrote:
>>
>>> Yes, if you want to emulate Cairngorm, get the source and build it with
>>> Flex so you know you have all of the pieces.
>>>
>>>
>>>
>>> Then, back up the source in case you need to go back and start replacing
>>> the import flash.*.* with Royale imports.  For example:
>>>
>>>
>>>
>>>   Import flash.events.EventDispatcher;
>>>
>>>
>>>
>>> Would be replaced by
>>>
>>>
>>>
>>>   Import org.apache.royale.events.EventDispatcher;
>>>
>>>
>>>
>>>
>>>
>>> If you have a question about what class to use as a replacement, ask on
>>> d...@royale.apache.org.  Then try to compile with Royale and see what
>>> kinds of errors you get.  If you don’t need the functionality in the code
>>> that has a compile error, one option is to comment it out.  For example, I
>>> just emulated WebService and commented out all of the flash.xml.XMLDocument
>>> support because I don’t think many people used it.
>>>
>>>
>>>
>>> Good luck,
>>>
>>> -Alex
>>>
>>>
>>>
>>> *From: *Takeshita Shoichiro 
>>> *Reply-To: *"users@royale.apache.org" 
>>> *Date: *Wednesday, October 16, 2019 at 8:37 PM
>>> *To: *"users@royale.apache.org" 
>>> *Subject: *Re: Cairngorm framework
>>>
>>>
>>>
>>> Alex, I have a question re Cairngorm emulation?
>>>
>>>
>>>
>>> I think  I need to put the Cairngorm source in the Royale project src
>>> folder.  Then, what should I do?
>>>
>>>
>>>
>>> Thanks for your advice.
>>>
>>>
>>>
>>> 2019年10月14日(月) 16:47 Takeshita Shoichiro :
>>>
>>> Carlos, thanks.
>>>
>>>
>>>
>>> I am very glad to hear that.
>>>
>>>
>>>
>>> Then, no hesitation to use Crux.
>>>
>>>
>>>
>>> 2019年10月14日(月) 16:43 Carlos Rovira :
>>>
>>> Hi Takeshita,
>>>
>>>
>>>
>>> I'll try to answer your questions
>>>
>>>
>>>
>>> El lun., 14 oct. 2019 a las 8:08, Takeshita Shoichiro (<
>>> jl03...@gmail.com>) escribió:
>>>
>>>
>>>
>>> 1. Does Apache Royale contain almost the ready-to-use emulation code for
>>> Swiz?  Or do we need more work for Apache Royale SDK?
>>>
>>>
>>>
>>> Yes. Swiz is ported to Royale (not emulated) and called Crux. So Crux is
>>> ready to use for you right now. No more work are needed for Royale in that
>>> line unless you report some bug around it.
>>>
>>>
>>>
>>> 2. Is the use of Jewel required?  Or is it possible also with existing
>>> MXML code?
>>>
>>>
>>>
>>>
>>>
>>> Jewel is not required. In Royale you are not tied to only one UI Set
>>> like in Flex. You have several ones to choose. You can use emulation
>>> components for MX/Spark, Basic, Jewel, MDL
>>>
>>>
>>>
>>> If you use MXRoyale, you'll get a near 0% code changes, but your
>>> application will look black/white unless you try to improve the look and
>>> feel.
>>>
>>> In exchange, Jewel will requiere you to recode you visual code, what
>>> means in most cases very easy changes, but is not as direct as MXRoyale, in
>>> exchange you get a more good looking interface since Jewel is crafted with
>>> look and feel and themes in mind.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Carlos Rovira
>>>
>>> http://about.me/carlosrovira
>>> 
>>>
>>>
>>>
>>> --
>>>
>>> Shoichiro Takeshita
>>> 武下 祥一郎
>>>
>>> --
>>>
>>> Shoichiro Takeshita
>>> 武下 祥一郎
>>>
>> --
> Shoichiro Takeshita
> 武下 祥一郎
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: excludeFrom vs visible & includeInLayout

2019-10-17 Thread Serkan Taş 
Hi Alex, as soon as i am available, i am going to work on the subect.




Thanks


Serkan




Android için Outlook'u edinin







On Wed, Oct 16, 2019 at 9:33 AM +0300, "Alex Harui"  wrote:




















Hi Serkan,


 


I looked at this sample.  The problem appears to be that the header appears at 
the bottom.  In debugging the code, I noticed that the 
StatesWithTransitionsImpl is not in sync with the SimpleStatesImpl.  Yishay 
added support for position==”first”
 to SimpleStatesImpl but apparently forgot to add it to 
StatesWithTransitionsImpl.


 


I’m at the end of my workday, so maybe you or some other volunteer can make 
that change and see if it solves your problem.


 


HTH,


-Alex


 



From:
Serkan Taş 

Reply-To: "users@royale.apache.org" 

Date: Monday, October 14, 2019 at 12:36 AM

To: "users@royale.apache.org" 

Subject: Re: excludeFrom vs visible & includeInLayout




 




Hi Alex,



Sometime it is really difficult to create test cases but for the actual case, I 
created a sample application.




Basically, there is a button to toggle the header and footer components 
show/hide with setting the state. You can see the strange behavior.



Also there are commented parts that do the same thing with visible & 
includeInLayout rather than state change, which is working as expected.



Here is the js-debug output : 
https://drive.google.com/open?id=1oF7OIXuGTfLvqM8mtWGSaKiT8C6lQhb5



Thanks

Serkan







13.10.2019 09:43 tarihinde Alex Harui yazdı:




We want to understand why excludeFrom is not working.  If you can create a 
simple test case, that would be great, otherwise let’s try to debug a public 
version.  Instead of paying for hosting, if you can create
 a version that doesn’t require server-side processing, then you can just 
upload the HTML/JS/CSS files to DropBox or some other account.


 


HTH,


-Alex


 



From:
Serkan Taş 


Reply-To: "users@royale.apache.org"


Date: Saturday, October 12, 2019 at 6:43 AM

To: "users@royale.apache.org"


Subject: excludeFrom vs visible & includeInLayout




 



Hi Herbs,



As you mentioned before, after updating the latest sources from github my 
actual problem is clearly related with the state concept, especially 
excludeFrom.



According to your advises I tried using  visible & includeInLayout, 



eg. :







It did not work because when using  excludeFrom the component is not created 
until the state is changed. But with the second option the component is 
created, and due to architecture of my application flow,


throws exceptions related with created components that shouldn't be.



I have 2 options :



1. Reconstruct my whole application as the excludeFrom will never work

2. Try to find out why excludeFrom is not working



Which why should I go through ?



Thanks.

Re: Cairngorm framework

2019-10-17 Thread Takeshita Shoichiro 
Alex and Greg, thanks.

2019年10月17日(木) 14:33 Greg Dove :

>
> Fwiw I did also look at Cairngorm before I ended up using Crux. iirc I
> think there might be some ADDED and REMOVED events for the views support
> that probably need to be addressed if you are using the views support.
> Crux has a stage events emulator that does that for
> addedToStage/removedFromStage, but ADDED and REMOVED are more about
> child/parent changes than about 'stage' I think.
>
> I used Crux mainly because I knew I could get it to work without any
> problems, and because I had other more critical issues to address (getting
> the Adobe rss syndication lib working, and in particular, the way it was
> being used in the app )
>
>
> On Thu, Oct 17, 2019 at 6:09 PM Alex Harui  wrote:
>
>> Yes, if you want to emulate Cairngorm, get the source and build it with
>> Flex so you know you have all of the pieces.
>>
>>
>>
>> Then, back up the source in case you need to go back and start replacing
>> the import flash.*.* with Royale imports.  For example:
>>
>>
>>
>>   Import flash.events.EventDispatcher;
>>
>>
>>
>> Would be replaced by
>>
>>
>>
>>   Import org.apache.royale.events.EventDispatcher;
>>
>>
>>
>>
>>
>> If you have a question about what class to use as a replacement, ask on
>> d...@royale.apache.org.  Then try to compile with Royale and see what
>> kinds of errors you get.  If you don’t need the functionality in the code
>> that has a compile error, one option is to comment it out.  For example, I
>> just emulated WebService and commented out all of the flash.xml.XMLDocument
>> support because I don’t think many people used it.
>>
>>
>>
>> Good luck,
>>
>> -Alex
>>
>>
>>
>> *From: *Takeshita Shoichiro 
>> *Reply-To: *"users@royale.apache.org" 
>> *Date: *Wednesday, October 16, 2019 at 8:37 PM
>> *To: *"users@royale.apache.org" 
>> *Subject: *Re: Cairngorm framework
>>
>>
>>
>> Alex, I have a question re Cairngorm emulation?
>>
>>
>>
>> I think  I need to put the Cairngorm source in the Royale project src
>> folder.  Then, what should I do?
>>
>>
>>
>> Thanks for your advice.
>>
>>
>>
>> 2019年10月14日(月) 16:47 Takeshita Shoichiro :
>>
>> Carlos, thanks.
>>
>>
>>
>> I am very glad to hear that.
>>
>>
>>
>> Then, no hesitation to use Crux.
>>
>>
>>
>> 2019年10月14日(月) 16:43 Carlos Rovira :
>>
>> Hi Takeshita,
>>
>>
>>
>> I'll try to answer your questions
>>
>>
>>
>> El lun., 14 oct. 2019 a las 8:08, Takeshita Shoichiro ()
>> escribió:
>>
>>
>>
>> 1. Does Apache Royale contain almost the ready-to-use emulation code for
>> Swiz?  Or do we need more work for Apache Royale SDK?
>>
>>
>>
>> Yes. Swiz is ported to Royale (not emulated) and called Crux. So Crux is
>> ready to use for you right now. No more work are needed for Royale in that
>> line unless you report some bug around it.
>>
>>
>>
>> 2. Is the use of Jewel required?  Or is it possible also with existing
>> MXML code?
>>
>>
>>
>>
>>
>> Jewel is not required. In Royale you are not tied to only one UI Set like
>> in Flex. You have several ones to choose. You can use emulation components
>> for MX/Spark, Basic, Jewel, MDL
>>
>>
>>
>> If you use MXRoyale, you'll get a near 0% code changes, but your
>> application will look black/white unless you try to improve the look and
>> feel.
>>
>> In exchange, Jewel will requiere you to recode you visual code, what
>> means in most cases very easy changes, but is not as direct as MXRoyale, in
>> exchange you get a more good looking interface since Jewel is crafted with
>> look and feel and themes in mind.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> Carlos Rovira
>>
>> http://about.me/carlosrovira
>> 
>>
>>
>>
>> --
>>
>> Shoichiro Takeshita
>> 武下 祥一郎
>>
>> --
>>
>> Shoichiro Takeshita
>> 武下 祥一郎
>>
> --
Shoichiro Takeshita
武下 祥一郎