Hi T-San,

Just to make sure:  What version of Cairngorm did you use in your app?

Thanks,
-Alex

From: Takeshita Shoichiro <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Wednesday, October 30, 2019 at 5:02 AM
To: "[email protected]" <[email protected]>
Subject: Re: Cairngorm to Crux

Greg, thanks a lot for your great work.  It seems it's very possible to migrate 
from Cairngorm to Crux.  I will check the changes you made in details tomorrow 
at the office.

I have your favors for the following matters.

- Mock service helper in the Crux library
I'm interested in this.  Would you provide the information?

- I used maven locally to build that, as a local variation inside the royale 
crux examples.
Could you provide your maven build procedure for this application?  I do not 
know how to build an application with product-like architecture (the one I sent 
to you).  I'd like to build my application and see the result quickly.  Using 
Visual Studio Code with ActionScript & MXML and Chrome Debugger extension is 
desirable.  However, if it takes time, Maven is fine but I want to build one 
application.

Appreciate your help.

S. Takeshita

On Wed, Oct 30, 2019 at 3:52 PM Greg Dove 
<[email protected]<mailto:[email protected]>> wrote:

@aharui
Actually it looks like I already based the 'QuickStart' examples in 
crux-examples on that, so maybe I did already 'test' the serviceHelper/Mock 
services stuff. I had forgotten these details. I need to attribute those 2 
specific examples with that Swiz source. I will add that tomorrow.

For the Cairrngorm stuff I believe Cairngorm 3 became more generic and provided 
various enhancements to the other newer architectural frameworks (Swiz, 
Robotlegs, Parsley etc) instead of being an evolution of the original 
Cairngorm, but I might be wrong about that. The app I ported was using 
Cairngorm 2 which was the 'original' I think (I don't know about any Cairngorm 
1, but presumably there was a Cairngorm 1 before 2) . I'll take a look at those 
version 3 examples as well, but in terms of 'porting' I think the main use will 
probably be Cairngorm 2 -> Crux. It still might be viable to port the Cairngorm 
2 code itself to Royale, I think I only saw something that would need to be 
resolved with the view processing part,  but I don't know about the Adobe 
licence for that (it is permissive, but I don't know offhand whether it is 
compatible for Apache).



On Wed, Oct 30, 2019 at 7:11 PM Alex Harui 
<[email protected]<mailto:[email protected]>> wrote:


From: Greg Dove <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Date: Tuesday, October 29, 2019 at 10:22 PM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Re: Cairngorm to Crux

Snip…
I will try to make another example (maybe the github viewer again) in royale 
examples using MXRoyale instead of Jewel/Basic in the coming days.
regards,
Greg

It would be interesting to find out how many changes to this example are needed 
to get it to run in Royale
https://swizframework.jira.com/wiki/spaces/SWIZ/pages/1999155/Quick+Start<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fswizframework.jira.com%2Fwiki%2Fspaces%2FSWIZ%2Fpages%2F1999155%2FQuick%2BStart&data=02%7C01%7Caharui%40adobe.com%7C16584df9b54f4aec3c6b08d75d310608%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637080337450723727&sdata=F7LuD8HU62Oj5F7FcWO4TrLsBMUnWEhS7mL2VOrhpH4%3D&reserved=0>

Same for some of the Cairngorm examples:
https://sourceforge.net/adobe/cairngorm/code/HEAD/tree/cairngorm3/trunk/samples/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fadobe%2Fcairngorm%2Fcode%2FHEAD%2Ftree%2Fcairngorm3%2Ftrunk%2Fsamples%2F&data=02%7C01%7Caharui%40adobe.com%7C16584df9b54f4aec3c6b08d75d310608%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637080337450723727&sdata=%2Fi0YFVVCiT1Cq1ioD0Q4KH4Jf08p3f2iaDS9BBQMqCg%3D&reserved=0>

Just an idea…
-Alex


--
Shoichiro Takeshita
武下 祥一郎

Reply via email to