Re: com.google.code.flexiframe

[Harbs]

Here’s it in use in an actual app:



I also have this code on intiComplete:

browser.addEventListener("locationChanged",locationChanged);
(browser.element as HTMLIFrameElement).sandbox = 
"allow-top-navigation allow-forms allow-scripts allow-same-origin";

If you need more extensive communication, take a look at postMessage: 
https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage 

HTH,
Harbs

> On Dec 17, 2019, at 6:51 AM, Greg Dove  wrote:
> 
> Sorry, I don't know of any. That class looked like it was intended for what 
> you needed, but I have not used it myself. When I needed the type of thing 
> that you described in the past, I wrote a custom component to do that, but it 
> looked like WebBrowser had part of the setup I had used when I did that.
> I just pushed a quick fix for startup url value assignment.
> I was able to get it displaying something that way with this:
> 
> https://royale.apache.org/ " 
> width="400" height="400"/>
> 
> 
>  it seems that both Alex and Harbs have worked on that. Maybe they can 
> provide more info. 
> 
> 
> On Tue, Dec 17, 2019 at 4:47 PM Takeshita Shoichiro  > wrote:
> Greg, is there any sample code snippet to use WebBrowser.as?
> 
> 2019年12月17日(火) 12:10 Greg Dove  >:
> I was just looking at the original lib. It has a bunch of extra api methods 
> etc. It might need some effort to add in the various ExternalInterface calls 
> that the original lib had if you need those. But basically, the Flex lib was 
> reaching out to html to do this. In Royale you are already 'closer' to the 
> iframe, so it should be relatively easy.
> 
> 
> On Tue, Dec 17, 2019 at 4:06 PM Takeshita Shoichiro  > wrote:
> Greg, thanks for a good news.  Will try.
> 
> 2019年12月17日(火) 12:04 Greg Dove  >:
> That should be quite easy. 
> 
> Either it should be easy to do it directly, or it looks like you could use:  
> org.apache.royale.html.WebBrowser
> from Basic lib.
> I did not use this yet, but it seems like it should be what you need.
> 
> 
> On Tue, Dec 17, 2019 at 4:00 PM Takeshita Shoichiro  > wrote:
> Hi,
> 
> Our application uses this library extensively to display page-size image as 
> embedded.
> 
> How it would be easy or difficult to make it work in Royale?
> -- 
> Shoichiro Takeshita
> 武下　祥一郎
> -- 
> Shoichiro Takeshita
> 武下　祥一郎
> -- 
> Shoichiro Takeshita
> 武下　祥一郎

Re: com.google.code.flexiframe

[Takeshita Shoichiro]

Greg, is there any sample code snippet to use WebBrowser.as?

2019年12月17日(火) 12:10 Greg Dove :

> I was just looking at the original lib. It has a bunch of extra api
> methods etc. It might need some effort to add in the various
> ExternalInterface calls that the original lib had if you need those. But
> basically, the Flex lib was reaching out to html to do this. In Royale you
> are already 'closer' to the iframe, so it should be relatively easy.
>
>
> On Tue, Dec 17, 2019 at 4:06 PM Takeshita Shoichiro 
> wrote:
>
>> Greg, thanks for a good news.  Will try.
>>
>> 2019年12月17日(火) 12:04 Greg Dove :
>>
>>> That should be quite easy.
>>>
>>> Either it should be easy to do it directly, or it looks like you could
>>> use:  org.apache.royale.html.WebBrowser
>>> from Basic lib.
>>> I did not use this yet, but it seems like it should be what you need.
>>>
>>>
>>> On Tue, Dec 17, 2019 at 4:00 PM Takeshita Shoichiro 
>>> wrote:
>>>
 Hi,

 Our application uses this library extensively to display page-size
 image as embedded.

 How it would be easy or difficult to make it work in Royale?
 --
 Shoichiro Takeshita
 武下 祥一郎

>>> --
>> Shoichiro Takeshita
>> 武下 祥一郎
>>
> --
Shoichiro Takeshita
武下 祥一郎

Re: com.google.code.flexiframe

[Greg Dove]

I was just looking at the original lib. It has a bunch of extra api methods
etc. It might need some effort to add in the various ExternalInterface
calls that the original lib had if you need those. But basically, the Flex
lib was reaching out to html to do this. In Royale you are already 'closer'
to the iframe, so it should be relatively easy.


On Tue, Dec 17, 2019 at 4:06 PM Takeshita Shoichiro 
wrote:

> Greg, thanks for a good news.  Will try.
>
> 2019年12月17日(火) 12:04 Greg Dove :
>
>> That should be quite easy.
>>
>> Either it should be easy to do it directly, or it looks like you could
>> use:  org.apache.royale.html.WebBrowser
>> from Basic lib.
>> I did not use this yet, but it seems like it should be what you need.
>>
>>
>> On Tue, Dec 17, 2019 at 4:00 PM Takeshita Shoichiro 
>> wrote:
>>
>>> Hi,
>>>
>>> Our application uses this library extensively to display page-size image
>>> as embedded.
>>>
>>> How it would be easy or difficult to make it work in Royale?
>>> --
>>> Shoichiro Takeshita
>>> 武下 祥一郎
>>>
>> --
> Shoichiro Takeshita
> 武下 祥一郎
>

Re: com.google.code.flexiframe

[Takeshita Shoichiro]

Greg, thanks for a good news.  Will try.

2019年12月17日(火) 12:04 Greg Dove :

> That should be quite easy.
>
> Either it should be easy to do it directly, or it looks like you could
> use:  org.apache.royale.html.WebBrowser
> from Basic lib.
> I did not use this yet, but it seems like it should be what you need.
>
>
> On Tue, Dec 17, 2019 at 4:00 PM Takeshita Shoichiro 
> wrote:
>
>> Hi,
>>
>> Our application uses this library extensively to display page-size image
>> as embedded.
>>
>> How it would be easy or difficult to make it work in Royale?
>> --
>> Shoichiro Takeshita
>> 武下 祥一郎
>>
> --
Shoichiro Takeshita
武下 祥一郎

Re: com.google.code.flexiframe

[Greg Dove]

That should be quite easy.

Either it should be easy to do it directly, or it looks like you could
use:  org.apache.royale.html.WebBrowser
from Basic lib.
I did not use this yet, but it seems like it should be what you need.


On Tue, Dec 17, 2019 at 4:00 PM Takeshita Shoichiro 
wrote:

> Hi,
>
> Our application uses this library extensively to display page-size image
> as embedded.
>
> How it would be easy or difficult to make it work in Royale?
> --
> Shoichiro Takeshita
> 武下 祥一郎
>

com.google.code.flexiframe

[Takeshita Shoichiro]

Hi,

Our application uses this library extensively to display page-size image as
embedded.

How it would be easy or difficult to make it work in Royale?
-- 
Shoichiro Takeshita
武下 祥一郎

Re: Creation popup by as

[De Carli Gustavo]

Carlos, I think the error is classified with this post.

http://apache-royale-development.20373.n8.nabble.com/TypeError-this-generateMXMLAttributes-is-not-a-function-td8881.html

thk.

El lun., 16 dic. 2019 a las 19:11, De Carli Gustavo (<
gustavodeca...@gmail.com>) escribió:

>
> Carlos No. both examples didn't work for me .
> About your comment, MyPopup already has inside a label component.
>
>
>
>
>
> El lun., 16 dic. 2019 a las 15:59, Carlos Rovira ()
> escribió:
>
>> Hi Gustavo,
>>
>> I didn't understand if you finally get it working or not, can you specify?
>> thanks
>> Carlos
>>
>> El lun., 16 dic. 2019 a las 18:52, De Carli Gustavo (<
>> gustavodeca...@gmail.com>) escribió:
>>
>>>
>>> Carlos: thank, Yes, those examples were where we started from. Now
>>> MyPopup already has a label (StyledUIBase) inside.
>>>
>>> MyPopup.mxml
>>>
>>> 
>>> http://ns.adobe.com/mxml/2009;
>>> xmlns:j="library://ns.apache.org/royale/jewel">
>>>
>>> 
>>>
>>> 
>>>
>>>
>>> It was also tested in this way, by code and not in mxml.
>>>
>>> public function popupByAS(event:Event):void
>>> {
>>> trace('In method byAs');
>>> var onePopup:MyPopup = new MyPopup();
>>> var oneLabel2:Label = new Label();
>>> oneLabel2.text = "Hi !!";
>>> onePopup.content = oneLabel2;
>>> this.addElement(onePopup);
>>>
>>> onePopup.open = true;
>>> }
>>>
>>>
>>> Thanks for your time
>>> Gustavo.
>>>
>>>
>>>
>>> El lun., 16 dic. 2019 a las 13:43, Carlos Rovira (<
>>> carlosrov...@apache.org>) escribió:
>>>
 Hi Gustavo,

 thanks for your kindly words :)

 About your problem, I don't see in the code exposed that you are adding
 MyPopup to the onePopup instance

 Popup has Defaultproperty "content". you must create and assign to it

 In Tour De Jewel: https://royale.apache.org/tourdejewel/
 You can see this:
 https://github.com/apache/royale-asjs/blob/develop/examples/royale/TourDeJewel/src/main/royale/PopUpPlayGround.mxml

 >>> closePopUp="popupFormContent.formValidator.removeAllErrorTips()">
 
 


 since content is Default property we can nest FormExample directly in
 the instance

 in AS you need to add to content

 Best

 Carlos



 El lun., 16 dic. 2019 a las 17:27, De Carli Gustavo (<
 gustavodeca...@gmail.com>) escribió:

> Carlos, Thanks for your prompt response. It fix !!! Now we are dealing
> with an external Popup, all this is for the migration of TitleWindow of
> flex to royale. We believe it is the best way. Take this opportunity to
> congratulate the framework, hopefully you have the first release version.
> Gustavo.
>
> public function popupByAS(event:Event):void
> {
> trace('In method byAs');
> var onePopup:MyPopup = new MyPopup();
> this.addElement(onePopup);
>
> onePopup.open = true;
> }
>
>
> Where MyPopup.mxml
> 
> http://ns.adobe.com/mxml/2009;
> xmlns:j="library://ns.apache.org/royale/jewel">
>
> 
>
> 
>
> MyPopup.js:42 Uncaught TypeError: this.generateMXMLAttributes is not a
> function
> at new main.components.Form.MyPopup (MyPopup.js:42)
> at Main.popupByAS (Main.mxml:22)
> at Main.$EH1 (Main.mxml:51)
> at Function.goog.events.fireListener [as googFireListener]
> (events.js:753)
> at
> Object.org.apache.royale.core.HTMLElementWrapper.fireListenerOverride [as
> fireListener] (HTMLElementWrapper.js:53)
> at HTMLButtonElement.goog.events.handleBrowserEvent_
> (events.js:879)
> at HTMLButtonElement.f (events.js:296)
>
> El lun., 16 dic. 2019 a las 13:11, Carlos Rovira (<
> carlosrov...@apache.org>) escribió:
>
>> Hi Carli,
>>
>> the main problem is that you need to add to the parent the popup
>> created with
>>
>> addElement(onePopup);
>>
>> Notice that each time you'll be creating one popup and adding to the
>> container, so maybe you need to create some logic to ensure creation and
>> addition to parent is done just one time.
>>
>> An additional issue (that does not gives error) is that click event
>> handlers has binding expressions. That's not needed
>>
>> instead of
>>
>> click="{this.popByMethod.open = true}"
>>
>> you write only:
>>
>> click="popByMethod.open = true"
>>
>>
>> HTH
>>
>> Carlos
>>
>>
>> El lun., 16 dic. 2019 a las 17:03, Carlos Rovira (<
>> carlosrov...@apache.org>) escribió:
>>
>>> Hi Carli,
>>> I'm going to try your code and see what I can report about it
>>>
>>> El lun., 16 dic. 2019 a las 16:56, De Carli Gustavo (<
>>> gustavodeca...@gmail.com>) escribió:
>>>
 Hello, someone could be oriented because I do not have the same
 behavior in the creation of a popup by msxml than by as. thank you 
 very much
 Method, 

Re: blog/BE0011_Loading_external_data_through_HTTPService

[Takeshita Shoichiro]

Carlos,

It did not solve the problem.

Instead I run mvn install under examples folder against the latest build;
could build without errors. Anyway, thanks a lot.

2019年12月16日(月) 21:40 Carlos Rovira :

> Hi Takeshita,
>
> the fail indicates that you didn't build the themes.
> You can go to framework/themes and build "mvn install"
> Themes are build when you build entire repo normally
>
>
>
> El lun., 16 dic. 2019 a las 13:17, Takeshita Shoichiro ()
> escribió:
>
>> Carlos,
>>
>> Thanks.  I'be just downloaded the night build and run mvn clean install
>> under \blog directory.
>>
>> It only built BE0001.
>>
>> The following are console errors (Windows 10).  Can I run mvn in blog
>> directory?  Or some other problems?
>>
>> O]
>> 
>> [INFO] Reactor Summary for Apache Royale: Examples: Blog 0.9.7-SNAPSHOT:
>> [INFO]
>> [INFO] Apache Royale: Examples: Blog .. SUCCESS
>> [01:01 min]
>> [INFO] Apache Royale: Examples: Blog: 0001: Hello World ... SUCCESS [
>> 14.558 s]
>> [INFO] Apache Royale: Examples: Blog: 0002: Using Jewel Alert Control
>> FAILURE [ 21.684 s]
>> [INFO] Apache Royale: Examples: Blog: 0003: Using Jewel HSlider Control
>> SKIPPED
>> [INFO] Apache Royale: Examples: Blog: 0004: Adding an item to a Jewel
>> List SKIPPED
>> [INFO] Apache Royale: Examples: Blog: 0005: Creating a group of Jewel
>> RadioButtons SKIPPED
>> [INFO] Apache Royale: Examples: Blog: 0006: Binding the text property of
>> a Jewel Textinput to update a text label SKIPPED
>> [INFO] Apache Royale: Examples: Blog: 0007: Selecting options from a
>> group of jewel checkbox controls SKIPPED
>> [INFO] Apache Royale: Examples: Blog: 0008: Using View States to show or
>> hide content SKIPPED
>> [INFO] Apache Royale: Examples: Blog: 0009: Using an Item Renderer with a
>> List SKIPPED
>> [INFO] Apache Royale: Examples: Blog: 0010: Customization through the
>> Royale API SKIPPED
>> [INFO] Apache Royale: Examples: Blog: 0011: Loading external data through
>> HTTPService SKIPPED
>> [INFO] Apache Royale: Examples: Blog: 0012: Using external javascript
>> libraries in Apache Royale SKIPPED
>> [INFO] Apache Royale: Examples: Blog: 0013: Dividing an Apache Royale
>> application with modules SKIPPED
>> [INFO] BE0013_Dividing_an_Apache_Royale_application_with_modules:
>> MainJewelApp SKIPPED
>> [INFO] BE0013_Dividing_an_Apache_Royale_application_with_modules:
>> JewelModule SKIPPED
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time:  02:00 min
>> [INFO] Finished at: 2019-12-16T21:11:32+09:00
>> [INFO]
>> 
>> [ERROR] Failed to execute goal on project
>> BE0002_Using_Jewel_Alert_Control: Could not resolve dependencies for
>> project
>> org.apache.royale.examples:BE0002_Using_Jewel_Alert_Control:swf:0.9.7-SNAPSHOT:
>> Could not find artifact
>> org.apache.royale.framework:Jewel-Light-NoFlat-Emphasized-Red-Theme:swc:0.9.7-SNAPSHOT
>> in apache.snapshots (https://repository.apache.org/snapshots) -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn  -rf :BE0002_Using_Jewel_Alert_Control
>>
>> On Mon, Dec 16, 2019 at 4:48 AM Carlos Rovira 
>> wrote:
>>
>>> Hi,
>>>
>>> just fixed all examples maven compilation
>>>
>>>
>>> El dom., 15 dic. 2019 a las 20:28, Carlos Rovira (<
>>> carlosrov...@apache.org>) escribió:
>>>
 Hi,

 I went through all the blog examples and fixed all. As well put
 asconfig.json working. ANT and Moonshine should be fixed by others with the
 time to contribute that.

 I'm know checking the rest of examples to fix mostly child tags prefixes



 El dom., 15 dic. 2019 a las 18:49, Carlos Rovira (<
 carlosrov...@apache.org>) escribió:

> Hi Takeshita,
>
> just fixed both examples.
> Some of the problems was due to child nodes in mxml not having the
> right prefix. Josh fixed that in compiler recently and we can still have
> examples broken for that. Can you please submit PR if you find others
> broken?.
> In BE0011, the main GitHubService object was not in x:Declaration tag.
> I was not aware, that is currently needed. Other seems to fix that in the
> past weeks.
> Notice that BE0012 apart from the fixes if run in localhost, since is
> loading a text 

Re: A part of Jewel

[Takeshita Shoichiro]

Carlos, thanks.

I’ve confirmed that links are working.

2019年12月17日(火) 4:33 Carlos Rovira :

> Hi Takeshita,
>
> I updated the website with all fixes and changes. You know can navigate it
> with no broken links and code in examples should match now the code in
> project examples.
>
> Please report if you find something more.
>
> Thanks
>
> Carlos
>
>
>
> El lun., 16 dic. 2019 a las 13:54, Andrew Wetmore ()
> escribió:
>
>> Thanks for catching up on that
>>
>> On Mon, Dec 16, 2019 at 8:50 AM Carlos Rovira 
>> wrote:
>>
>>> Hi Andrew,
>>>
>>> I reverted that commit since the I changed weeks ago all links to match
>>> the same pattern, i.e:  /jewel/themes or /jewe/button and be only permalinks
>>> I fixed all blog examples tutorials today in pre site (still not
>>> published to production) since links to royale docs wasn't working due to
>>> that issue and due to the migration to use only permalinks.
>>> Sorry, I didn't mention this one here, so you can't know about it.
>>>
>>> Thanks
>>>
>>> Carlos
>>>
>>>
>>>
>>> El lun., 16 dic. 2019 a las 13:39, Andrew Wetmore ()
>>> escribió:
>>>
   About the Jewel themes page, I see it at
 https://apache.github.io/royale-docs/component-sets/jewel/jewel-themes.html


 There was an error in the permalink for the page, and I have fixed it.
 The fix should be available soon.

 Andrew

 On Mon, Dec 16, 2019 at 8:23 AM Takeshita Shoichiro 
 wrote:

> Carlos, thanks for your explanation.  I will study SASS.
>
> As to VS Code compilation, I cannot get the same output as the one
> using mvn.  I do not know how to specify three themes in asconfig.json,
> which would be the root cause.
> In the meantime, I need to use mvn.
>
> By the way, I'd like to know the current status of the following page.
>
> https://apache.github.io/royale-docs/component-sets/jewel#jewel-themes
>
>
> Thanks.
>
> On Mon, Dec 16, 2019 at 5:47 PM Carlos Rovira 
> wrote:
>
>> Hi Takeshita,
>>
>> to clean the input is something you can do in a number of ways:
>>
>>- You can just clear textinputs after navigate to the next
>>screen, so when you come back for whatever reason is clean
>>- You can send an Event when perform the LOGOUT to make the
>>textinputs be cleared
>>
>> This depends more on the structure of your app. Take into account
>> that the example is just a very simple view state example on how that 
>> works.
>>
>> About skinning with CSS. I mean that really there's no a SKIN concept
>> like in Flex 4, since in HTML we can just rely on CSS. So you can create
>> custom CSS in you APP to add up to some concrete style in Jewel, or just
>> override it completely. You have available all HTML infrastructure using
>> "lclassName" or "style" (to go directly to low level html styling). That
>> kind of things can be ok for few changes you want. If you need to create
>> your own Theme (override all component styles or most of them), you can
>> create your own JewelTheme. Copying the project and changing to your 
>> needs.
>> I use in JewelTheme SASS since it give us structure and organization in
>> files. SASS is for CSS like AS3/MXML for Javascript. A way to code it in 
>> a
>> better and easy way and left the SASS compiler to minimize the output. 
>> You
>> have SASS compilation only in Maven build for free. More info in Royale
>> Docs in [1] & [2]
>>
>> [1] Jewel Themes
>> 
>> [2] Jewel Theme Creation
>> 
>>
>>
>>
>> El lun., 16 dic. 2019 a las 2:35, Takeshita Shoichiro (<
>> jl03...@gmail.com>) escribió:
>>
>>> Carlos, thanks.
>>>
>>> I cloud center the login panel.
>>>
>>> This is just my preference. When showing the login panel, I would
>>> not see the preset data. And after pressing LOGOUT button, I’d like to
>>> clear the input. How can we clear the input?
>>>
>>> As to skin class replacement by CSS is also fine.  Can I see such an
>>> example?
>>>
>>>
>>>
>>> 2019年12月16日(月) 2:23 Carlos Rovira :
>>>
 Hi Takeshita,

 El dom., 15 dic. 2019 a las 3:17, Takeshita Shoichiro (<
 jl03...@gmail.com>) escribió:

> Carlos, the current asconfig.json is fine.  One note is that we
> need to use  "targets": ["JSRoyale"], for JS only build.
> It seems I made some mistakes when creating a project BE0008
> project in VS Code. This morning I tried again and things worked well.
>

 Thanks I committed the fix :)


> By the way, would you please advise me on how to display this
> Login panel at the center of the 

Re: Creation popup by as

[De Carli Gustavo]

Carlos No. both examples didn't work for me .
About your comment, MyPopup already has inside a label component.





El lun., 16 dic. 2019 a las 15:59, Carlos Rovira ()
escribió:

> Hi Gustavo,
>
> I didn't understand if you finally get it working or not, can you specify?
> thanks
> Carlos
>
> El lun., 16 dic. 2019 a las 18:52, De Carli Gustavo (<
> gustavodeca...@gmail.com>) escribió:
>
>>
>> Carlos: thank, Yes, those examples were where we started from. Now
>> MyPopup already has a label (StyledUIBase) inside.
>>
>> MyPopup.mxml
>>
>> 
>> http://ns.adobe.com/mxml/2009;
>> xmlns:j="library://ns.apache.org/royale/jewel">
>>
>> 
>>
>> 
>>
>>
>> It was also tested in this way, by code and not in mxml.
>>
>> public function popupByAS(event:Event):void
>> {
>> trace('In method byAs');
>> var onePopup:MyPopup = new MyPopup();
>> var oneLabel2:Label = new Label();
>> oneLabel2.text = "Hi !!";
>> onePopup.content = oneLabel2;
>> this.addElement(onePopup);
>>
>> onePopup.open = true;
>> }
>>
>>
>> Thanks for your time
>> Gustavo.
>>
>>
>>
>> El lun., 16 dic. 2019 a las 13:43, Carlos Rovira (<
>> carlosrov...@apache.org>) escribió:
>>
>>> Hi Gustavo,
>>>
>>> thanks for your kindly words :)
>>>
>>> About your problem, I don't see in the code exposed that you are adding
>>> MyPopup to the onePopup instance
>>>
>>> Popup has Defaultproperty "content". you must create and assign to it
>>>
>>> In Tour De Jewel: https://royale.apache.org/tourdejewel/
>>> You can see this:
>>> https://github.com/apache/royale-asjs/blob/develop/examples/royale/TourDeJewel/src/main/royale/PopUpPlayGround.mxml
>>>
>>> >> closePopUp="popupFormContent.formValidator.removeAllErrorTips()">
>>> 
>>> 
>>>
>>>
>>> since content is Default property we can nest FormExample directly in
>>> the instance
>>>
>>> in AS you need to add to content
>>>
>>> Best
>>>
>>> Carlos
>>>
>>>
>>>
>>> El lun., 16 dic. 2019 a las 17:27, De Carli Gustavo (<
>>> gustavodeca...@gmail.com>) escribió:
>>>
 Carlos, Thanks for your prompt response. It fix !!! Now we are dealing
 with an external Popup, all this is for the migration of TitleWindow of
 flex to royale. We believe it is the best way. Take this opportunity to
 congratulate the framework, hopefully you have the first release version.
 Gustavo.

 public function popupByAS(event:Event):void
 {
 trace('In method byAs');
 var onePopup:MyPopup = new MyPopup();
 this.addElement(onePopup);

 onePopup.open = true;
 }


 Where MyPopup.mxml
 
 http://ns.adobe.com/mxml/2009;
 xmlns:j="library://ns.apache.org/royale/jewel">

 

 

 MyPopup.js:42 Uncaught TypeError: this.generateMXMLAttributes is not a
 function
 at new main.components.Form.MyPopup (MyPopup.js:42)
 at Main.popupByAS (Main.mxml:22)
 at Main.$EH1 (Main.mxml:51)
 at Function.goog.events.fireListener [as googFireListener]
 (events.js:753)
 at
 Object.org.apache.royale.core.HTMLElementWrapper.fireListenerOverride [as
 fireListener] (HTMLElementWrapper.js:53)
 at HTMLButtonElement.goog.events.handleBrowserEvent_ (events.js:879)
 at HTMLButtonElement.f (events.js:296)

 El lun., 16 dic. 2019 a las 13:11, Carlos Rovira (<
 carlosrov...@apache.org>) escribió:

> Hi Carli,
>
> the main problem is that you need to add to the parent the popup
> created with
>
> addElement(onePopup);
>
> Notice that each time you'll be creating one popup and adding to the
> container, so maybe you need to create some logic to ensure creation and
> addition to parent is done just one time.
>
> An additional issue (that does not gives error) is that click event
> handlers has binding expressions. That's not needed
>
> instead of
>
> click="{this.popByMethod.open = true}"
>
> you write only:
>
> click="popByMethod.open = true"
>
>
> HTH
>
> Carlos
>
>
> El lun., 16 dic. 2019 a las 17:03, Carlos Rovira (<
> carlosrov...@apache.org>) escribió:
>
>> Hi Carli,
>> I'm going to try your code and see what I can report about it
>>
>> El lun., 16 dic. 2019 a las 16:56, De Carli Gustavo (<
>> gustavodeca...@gmail.com>) escribió:
>>
>>> Hello, someone could be oriented because I do not have the same
>>> behavior in the creation of a popup by msxml than by as. thank you very 
>>> much
>>> Method, popupByAs, is the problem, does nothing.
>>>
>>> thank
>>>
>>>
>>> 
>>> http://ns.adobe.com/mxml/2009;
>>> xmlns:html="library://ns.apache.org/royale/html"
>>> xmlns:j="library://ns.apache.org/royale/jewel"
>>> xmlns:Button="main.components.Button.*"
>>> xmlns:Form="main.components.Form.*"
>>> xmlns:js="library://ns.apache.org/royale/basic"
>>> xmlns:c="components.*">
>>>
>>> 
>>> 
>>> 
>>>

Re: A part of Jewel

[Carlos Rovira]

Hi Takeshita,

I updated the website with all fixes and changes. You know can navigate it
with no broken links and code in examples should match now the code in
project examples.

Please report if you find something more.

Thanks

Carlos



El lun., 16 dic. 2019 a las 13:54, Andrew Wetmore ()
escribió:

> Thanks for catching up on that
>
> On Mon, Dec 16, 2019 at 8:50 AM Carlos Rovira 
> wrote:
>
>> Hi Andrew,
>>
>> I reverted that commit since the I changed weeks ago all links to match
>> the same pattern, i.e:  /jewel/themes or /jewe/button and be only permalinks
>> I fixed all blog examples tutorials today in pre site (still not
>> published to production) since links to royale docs wasn't working due to
>> that issue and due to the migration to use only permalinks.
>> Sorry, I didn't mention this one here, so you can't know about it.
>>
>> Thanks
>>
>> Carlos
>>
>>
>>
>> El lun., 16 dic. 2019 a las 13:39, Andrew Wetmore ()
>> escribió:
>>
>>>   About the Jewel themes page, I see it at
>>> https://apache.github.io/royale-docs/component-sets/jewel/jewel-themes.html
>>>
>>>
>>> There was an error in the permalink for the page, and I have fixed it.
>>> The fix should be available soon.
>>>
>>> Andrew
>>>
>>> On Mon, Dec 16, 2019 at 8:23 AM Takeshita Shoichiro 
>>> wrote:
>>>
 Carlos, thanks for your explanation.  I will study SASS.

 As to VS Code compilation, I cannot get the same output as the one
 using mvn.  I do not know how to specify three themes in asconfig.json,
 which would be the root cause.
 In the meantime, I need to use mvn.

 By the way, I'd like to know the current status of the following page.

 https://apache.github.io/royale-docs/component-sets/jewel#jewel-themes

 Thanks.

 On Mon, Dec 16, 2019 at 5:47 PM Carlos Rovira 
 wrote:

> Hi Takeshita,
>
> to clean the input is something you can do in a number of ways:
>
>- You can just clear textinputs after navigate to the next screen,
>so when you come back for whatever reason is clean
>- You can send an Event when perform the LOGOUT to make the
>textinputs be cleared
>
> This depends more on the structure of your app. Take into account that
> the example is just a very simple view state example on how that works.
>
> About skinning with CSS. I mean that really there's no a SKIN concept
> like in Flex 4, since in HTML we can just rely on CSS. So you can create
> custom CSS in you APP to add up to some concrete style in Jewel, or just
> override it completely. You have available all HTML infrastructure using
> "lclassName" or "style" (to go directly to low level html styling). That
> kind of things can be ok for few changes you want. If you need to create
> your own Theme (override all component styles or most of them), you can
> create your own JewelTheme. Copying the project and changing to your 
> needs.
> I use in JewelTheme SASS since it give us structure and organization in
> files. SASS is for CSS like AS3/MXML for Javascript. A way to code it in a
> better and easy way and left the SASS compiler to minimize the output. You
> have SASS compilation only in Maven build for free. More info in Royale
> Docs in [1] & [2]
>
> [1] Jewel Themes
> 
> [2] Jewel Theme Creation
> 
>
>
>
> El lun., 16 dic. 2019 a las 2:35, Takeshita Shoichiro (<
> jl03...@gmail.com>) escribió:
>
>> Carlos, thanks.
>>
>> I cloud center the login panel.
>>
>> This is just my preference. When showing the login panel, I would not
>> see the preset data. And after pressing LOGOUT button, I’d like to clear
>> the input. How can we clear the input?
>>
>> As to skin class replacement by CSS is also fine.  Can I see such an
>> example?
>>
>>
>>
>> 2019年12月16日(月) 2:23 Carlos Rovira :
>>
>>> Hi Takeshita,
>>>
>>> El dom., 15 dic. 2019 a las 3:17, Takeshita Shoichiro (<
>>> jl03...@gmail.com>) escribió:
>>>
 Carlos, the current asconfig.json is fine.  One note is that we
 need to use  "targets": ["JSRoyale"], for JS only build.
 It seems I made some mistakes when creating a project BE0008
 project in VS Code. This morning I tried again and things worked well.

>>>
>>> Thanks I committed the fix :)
>>>
>>>
 By the way, would you please advise me on how to display this Login
 panel at the center of the screen in Jewel?

>>>
>>> In the example just add a   to he View
>>> beads. That's all.
>>>
>>>
 And does Jewel support skin class?

>>>
>>> Not for now. Skin support will depend on plans on Spark emulation.
>>> 

Re: Creation popup by as

[Carlos Rovira]

Hi Gustavo,

I didn't understand if you finally get it working or not, can you specify?
thanks
Carlos

El lun., 16 dic. 2019 a las 18:52, De Carli Gustavo (<
gustavodeca...@gmail.com>) escribió:

>
> Carlos: thank, Yes, those examples were where we started from. Now MyPopup
> already has a label (StyledUIBase) inside.
>
> MyPopup.mxml
>
> 
> http://ns.adobe.com/mxml/2009;
> xmlns:j="library://ns.apache.org/royale/jewel">
>
> 
>
> 
>
>
> It was also tested in this way, by code and not in mxml.
>
> public function popupByAS(event:Event):void
> {
> trace('In method byAs');
> var onePopup:MyPopup = new MyPopup();
> var oneLabel2:Label = new Label();
> oneLabel2.text = "Hi !!";
> onePopup.content = oneLabel2;
> this.addElement(onePopup);
>
> onePopup.open = true;
> }
>
>
> Thanks for your time
> Gustavo.
>
>
>
> El lun., 16 dic. 2019 a las 13:43, Carlos Rovira ()
> escribió:
>
>> Hi Gustavo,
>>
>> thanks for your kindly words :)
>>
>> About your problem, I don't see in the code exposed that you are adding
>> MyPopup to the onePopup instance
>>
>> Popup has Defaultproperty "content". you must create and assign to it
>>
>> In Tour De Jewel: https://royale.apache.org/tourdejewel/
>> You can see this:
>> https://github.com/apache/royale-asjs/blob/develop/examples/royale/TourDeJewel/src/main/royale/PopUpPlayGround.mxml
>>
>> > closePopUp="popupFormContent.formValidator.removeAllErrorTips()">
>> > width="490" height="392"/>
>> 
>>
>>
>> since content is Default property we can nest FormExample directly in the
>> instance
>>
>> in AS you need to add to content
>>
>> Best
>>
>> Carlos
>>
>>
>>
>> El lun., 16 dic. 2019 a las 17:27, De Carli Gustavo (<
>> gustavodeca...@gmail.com>) escribió:
>>
>>> Carlos, Thanks for your prompt response. It fix !!! Now we are dealing
>>> with an external Popup, all this is for the migration of TitleWindow of
>>> flex to royale. We believe it is the best way. Take this opportunity to
>>> congratulate the framework, hopefully you have the first release version.
>>> Gustavo.
>>>
>>> public function popupByAS(event:Event):void
>>> {
>>> trace('In method byAs');
>>> var onePopup:MyPopup = new MyPopup();
>>> this.addElement(onePopup);
>>>
>>> onePopup.open = true;
>>> }
>>>
>>>
>>> Where MyPopup.mxml
>>> 
>>> http://ns.adobe.com/mxml/2009;
>>> xmlns:j="library://ns.apache.org/royale/jewel">
>>>
>>> 
>>>
>>> 
>>>
>>> MyPopup.js:42 Uncaught TypeError: this.generateMXMLAttributes is not a
>>> function
>>> at new main.components.Form.MyPopup (MyPopup.js:42)
>>> at Main.popupByAS (Main.mxml:22)
>>> at Main.$EH1 (Main.mxml:51)
>>> at Function.goog.events.fireListener [as googFireListener]
>>> (events.js:753)
>>> at
>>> Object.org.apache.royale.core.HTMLElementWrapper.fireListenerOverride [as
>>> fireListener] (HTMLElementWrapper.js:53)
>>> at HTMLButtonElement.goog.events.handleBrowserEvent_ (events.js:879)
>>> at HTMLButtonElement.f (events.js:296)
>>>
>>> El lun., 16 dic. 2019 a las 13:11, Carlos Rovira (<
>>> carlosrov...@apache.org>) escribió:
>>>
 Hi Carli,

 the main problem is that you need to add to the parent the popup
 created with

 addElement(onePopup);

 Notice that each time you'll be creating one popup and adding to the
 container, so maybe you need to create some logic to ensure creation and
 addition to parent is done just one time.

 An additional issue (that does not gives error) is that click event
 handlers has binding expressions. That's not needed

 instead of

 click="{this.popByMethod.open = true}"

 you write only:

 click="popByMethod.open = true"


 HTH

 Carlos


 El lun., 16 dic. 2019 a las 17:03, Carlos Rovira (<
 carlosrov...@apache.org>) escribió:

> Hi Carli,
> I'm going to try your code and see what I can report about it
>
> El lun., 16 dic. 2019 a las 16:56, De Carli Gustavo (<
> gustavodeca...@gmail.com>) escribió:
>
>> Hello, someone could be oriented because I do not have the same
>> behavior in the creation of a popup by msxml than by as. thank you very 
>> much
>> Method, popupByAs, is the problem, does nothing.
>>
>> thank
>>
>>
>> 
>> http://ns.adobe.com/mxml/2009;
>> xmlns:html="library://ns.apache.org/royale/html"
>> xmlns:j="library://ns.apache.org/royale/jewel"
>> xmlns:Button="main.components.Button.*"
>> xmlns:Form="main.components.Form.*"
>> xmlns:js="library://ns.apache.org/royale/basic"
>> xmlns:c="components.*">
>>
>> 
>> 
>> 
>>
>> 
>> 
>> > text="By Method MXML"
>> x="10"
>> y="200"
>> emphasis="primary"
>> click="{this.popByMethod.open = true}"/>
>>
>>
>> 
>> 
>> 
>>
>>
>> > text="By Metodo AS"
>> x="10"
>> y="200"
>> emphasis="primary"
>> click="{this.popupByAS(event)}"/>
>> 
>> 
>> 
>>

Re: Creation popup by as

[De Carli Gustavo]

Carlos: thank, Yes, those examples were where we started from. Now MyPopup
already has a label (StyledUIBase) inside.

MyPopup.mxml


http://ns.adobe.com/mxml/2009;
xmlns:j="library://ns.apache.org/royale/jewel">






It was also tested in this way, by code and not in mxml.

public function popupByAS(event:Event):void
{
trace('In method byAs');
var onePopup:MyPopup = new MyPopup();
var oneLabel2:Label = new Label();
oneLabel2.text = "Hi !!";
onePopup.content = oneLabel2;
this.addElement(onePopup);

onePopup.open = true;
}


Thanks for your time
Gustavo.



El lun., 16 dic. 2019 a las 13:43, Carlos Rovira ()
escribió:

> Hi Gustavo,
>
> thanks for your kindly words :)
>
> About your problem, I don't see in the code exposed that you are adding
> MyPopup to the onePopup instance
>
> Popup has Defaultproperty "content". you must create and assign to it
>
> In Tour De Jewel: https://royale.apache.org/tourdejewel/
> You can see this:
> https://github.com/apache/royale-asjs/blob/develop/examples/royale/TourDeJewel/src/main/royale/PopUpPlayGround.mxml
>
>  closePopUp="popupFormContent.formValidator.removeAllErrorTips()">
>  width="490" height="392"/>
> 
>
>
> since content is Default property we can nest FormExample directly in the
> instance
>
> in AS you need to add to content
>
> Best
>
> Carlos
>
>
>
> El lun., 16 dic. 2019 a las 17:27, De Carli Gustavo (<
> gustavodeca...@gmail.com>) escribió:
>
>> Carlos, Thanks for your prompt response. It fix !!! Now we are dealing
>> with an external Popup, all this is for the migration of TitleWindow of
>> flex to royale. We believe it is the best way. Take this opportunity to
>> congratulate the framework, hopefully you have the first release version.
>> Gustavo.
>>
>> public function popupByAS(event:Event):void
>> {
>> trace('In method byAs');
>> var onePopup:MyPopup = new MyPopup();
>> this.addElement(onePopup);
>>
>> onePopup.open = true;
>> }
>>
>>
>> Where MyPopup.mxml
>> 
>> http://ns.adobe.com/mxml/2009;
>> xmlns:j="library://ns.apache.org/royale/jewel">
>>
>> 
>>
>> 
>>
>> MyPopup.js:42 Uncaught TypeError: this.generateMXMLAttributes is not a
>> function
>> at new main.components.Form.MyPopup (MyPopup.js:42)
>> at Main.popupByAS (Main.mxml:22)
>> at Main.$EH1 (Main.mxml:51)
>> at Function.goog.events.fireListener [as googFireListener]
>> (events.js:753)
>> at
>> Object.org.apache.royale.core.HTMLElementWrapper.fireListenerOverride [as
>> fireListener] (HTMLElementWrapper.js:53)
>> at HTMLButtonElement.goog.events.handleBrowserEvent_ (events.js:879)
>> at HTMLButtonElement.f (events.js:296)
>>
>> El lun., 16 dic. 2019 a las 13:11, Carlos Rovira (<
>> carlosrov...@apache.org>) escribió:
>>
>>> Hi Carli,
>>>
>>> the main problem is that you need to add to the parent the popup created
>>> with
>>>
>>> addElement(onePopup);
>>>
>>> Notice that each time you'll be creating one popup and adding to the
>>> container, so maybe you need to create some logic to ensure creation and
>>> addition to parent is done just one time.
>>>
>>> An additional issue (that does not gives error) is that click event
>>> handlers has binding expressions. That's not needed
>>>
>>> instead of
>>>
>>> click="{this.popByMethod.open = true}"
>>>
>>> you write only:
>>>
>>> click="popByMethod.open = true"
>>>
>>>
>>> HTH
>>>
>>> Carlos
>>>
>>>
>>> El lun., 16 dic. 2019 a las 17:03, Carlos Rovira (<
>>> carlosrov...@apache.org>) escribió:
>>>
 Hi Carli,
 I'm going to try your code and see what I can report about it

 El lun., 16 dic. 2019 a las 16:56, De Carli Gustavo (<
 gustavodeca...@gmail.com>) escribió:

> Hello, someone could be oriented because I do not have the same
> behavior in the creation of a popup by msxml than by as. thank you very 
> much
> Method, popupByAs, is the problem, does nothing.
>
> thank
>
>
> 
> http://ns.adobe.com/mxml/2009;
> xmlns:html="library://ns.apache.org/royale/html"
> xmlns:j="library://ns.apache.org/royale/jewel"
> xmlns:Button="main.components.Button.*"
> xmlns:Form="main.components.Form.*"
> xmlns:js="library://ns.apache.org/royale/basic"
> xmlns:c="components.*">
>
> 
> 
> 
>
> 
> 
>  text="By Method MXML"
> x="10"
> y="200"
> emphasis="primary"
> click="{this.popByMethod.open = true}"/>
>
>
> 
> 
> 
>
>
>  text="By Metodo AS"
> x="10"
> y="200"
> emphasis="primary"
> click="{this.popupByAS(event)}"/>
> 
> 
> 
>
>
>

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


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

Re: Creation popup by as

[Carlos Rovira]

Hi Gustavo,

thanks for your kindly words :)

About your problem, I don't see in the code exposed that you are adding
MyPopup to the onePopup instance

Popup has Defaultproperty "content". you must create and assign to it

In Tour De Jewel: https://royale.apache.org/tourdejewel/
You can see this:
https://github.com/apache/royale-asjs/blob/develop/examples/royale/TourDeJewel/src/main/royale/PopUpPlayGround.mxml






since content is Default property we can nest FormExample directly in the
instance

in AS you need to add to content

Best

Carlos



El lun., 16 dic. 2019 a las 17:27, De Carli Gustavo (<
gustavodeca...@gmail.com>) escribió:

> Carlos, Thanks for your prompt response. It fix !!! Now we are dealing
> with an external Popup, all this is for the migration of TitleWindow of
> flex to royale. We believe it is the best way. Take this opportunity to
> congratulate the framework, hopefully you have the first release version.
> Gustavo.
>
> public function popupByAS(event:Event):void
> {
> trace('In method byAs');
> var onePopup:MyPopup = new MyPopup();
> this.addElement(onePopup);
>
> onePopup.open = true;
> }
>
>
> Where MyPopup.mxml
> 
> http://ns.adobe.com/mxml/2009;
> xmlns:j="library://ns.apache.org/royale/jewel">
>
> 
>
> 
>
> MyPopup.js:42 Uncaught TypeError: this.generateMXMLAttributes is not a
> function
> at new main.components.Form.MyPopup (MyPopup.js:42)
> at Main.popupByAS (Main.mxml:22)
> at Main.$EH1 (Main.mxml:51)
> at Function.goog.events.fireListener [as googFireListener]
> (events.js:753)
> at
> Object.org.apache.royale.core.HTMLElementWrapper.fireListenerOverride [as
> fireListener] (HTMLElementWrapper.js:53)
> at HTMLButtonElement.goog.events.handleBrowserEvent_ (events.js:879)
> at HTMLButtonElement.f (events.js:296)
>
> El lun., 16 dic. 2019 a las 13:11, Carlos Rovira ()
> escribió:
>
>> Hi Carli,
>>
>> the main problem is that you need to add to the parent the popup created
>> with
>>
>> addElement(onePopup);
>>
>> Notice that each time you'll be creating one popup and adding to the
>> container, so maybe you need to create some logic to ensure creation and
>> addition to parent is done just one time.
>>
>> An additional issue (that does not gives error) is that click event
>> handlers has binding expressions. That's not needed
>>
>> instead of
>>
>> click="{this.popByMethod.open = true}"
>>
>> you write only:
>>
>> click="popByMethod.open = true"
>>
>>
>> HTH
>>
>> Carlos
>>
>>
>> El lun., 16 dic. 2019 a las 17:03, Carlos Rovira (<
>> carlosrov...@apache.org>) escribió:
>>
>>> Hi Carli,
>>> I'm going to try your code and see what I can report about it
>>>
>>> El lun., 16 dic. 2019 a las 16:56, De Carli Gustavo (<
>>> gustavodeca...@gmail.com>) escribió:
>>>
 Hello, someone could be oriented because I do not have the same
 behavior in the creation of a popup by msxml than by as. thank you very 
 much
 Method, popupByAs, is the problem, does nothing.

 thank


 
 http://ns.adobe.com/mxml/2009;
 xmlns:html="library://ns.apache.org/royale/html"
 xmlns:j="library://ns.apache.org/royale/jewel"
 xmlns:Button="main.components.Button.*"
 xmlns:Form="main.components.Form.*"
 xmlns:js="library://ns.apache.org/royale/basic"
 xmlns:c="components.*">

 
 
 

 
 
 >>> text="By Method MXML"
 x="10"
 y="200"
 emphasis="primary"
 click="{this.popByMethod.open = true}"/>


 
 
 


 >>> text="By Metodo AS"
 x="10"
 y="200"
 emphasis="primary"
 click="{this.popupByAS(event)}"/>
 
 
 



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

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

Re: Creation popup by as

[De Carli Gustavo]

Carlos, Thanks for your prompt response. It fix !!! Now we are dealing with
an external Popup, all this is for the migration of TitleWindow of flex to
royale. We believe it is the best way. Take this opportunity to
congratulate the framework, hopefully you have the first release version.
Gustavo.

public function popupByAS(event:Event):void
{
trace('In method byAs');
var onePopup:MyPopup = new MyPopup();
this.addElement(onePopup);

onePopup.open = true;
}


Where MyPopup.mxml

http://ns.adobe.com/mxml/2009;
xmlns:j="library://ns.apache.org/royale/jewel">





MyPopup.js:42 Uncaught TypeError: this.generateMXMLAttributes is not a
function
at new main.components.Form.MyPopup (MyPopup.js:42)
at Main.popupByAS (Main.mxml:22)
at Main.$EH1 (Main.mxml:51)
at Function.goog.events.fireListener [as googFireListener]
(events.js:753)
at
Object.org.apache.royale.core.HTMLElementWrapper.fireListenerOverride [as
fireListener] (HTMLElementWrapper.js:53)
at HTMLButtonElement.goog.events.handleBrowserEvent_ (events.js:879)
at HTMLButtonElement.f (events.js:296)

El lun., 16 dic. 2019 a las 13:11, Carlos Rovira ()
escribió:

> Hi Carli,
>
> the main problem is that you need to add to the parent the popup created
> with
>
> addElement(onePopup);
>
> Notice that each time you'll be creating one popup and adding to the
> container, so maybe you need to create some logic to ensure creation and
> addition to parent is done just one time.
>
> An additional issue (that does not gives error) is that click event
> handlers has binding expressions. That's not needed
>
> instead of
>
> click="{this.popByMethod.open = true}"
>
> you write only:
>
> click="popByMethod.open = true"
>
>
> HTH
>
> Carlos
>
>
> El lun., 16 dic. 2019 a las 17:03, Carlos Rovira ()
> escribió:
>
>> Hi Carli,
>> I'm going to try your code and see what I can report about it
>>
>> El lun., 16 dic. 2019 a las 16:56, De Carli Gustavo (<
>> gustavodeca...@gmail.com>) escribió:
>>
>>> Hello, someone could be oriented because I do not have the same behavior
>>> in the creation of a popup by msxml than by as. thank you very much
>>> Method, popupByAs, is the problem, does nothing.
>>>
>>> thank
>>>
>>>
>>> 
>>> http://ns.adobe.com/mxml/2009;
>>> xmlns:html="library://ns.apache.org/royale/html"
>>> xmlns:j="library://ns.apache.org/royale/jewel"
>>> xmlns:Button="main.components.Button.*"
>>> xmlns:Form="main.components.Form.*"
>>> xmlns:js="library://ns.apache.org/royale/basic"
>>> xmlns:c="components.*">
>>>
>>> 
>>> 
>>> 
>>>
>>> 
>>> 
>>> >> text="By Method MXML"
>>> x="10"
>>> y="200"
>>> emphasis="primary"
>>> click="{this.popByMethod.open = true}"/>
>>>
>>>
>>> 
>>> 
>>> 
>>>
>>>
>>> >> text="By Metodo AS"
>>> x="10"
>>> y="200"
>>> emphasis="primary"
>>> click="{this.popupByAS(event)}"/>
>>> 
>>> 
>>> 
>>>
>>>
>>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

Re: Creation popup by as

[Carlos Rovira]

Hi Carli,

the main problem is that you need to add to the parent the popup created
with

addElement(onePopup);

Notice that each time you'll be creating one popup and adding to the
container, so maybe you need to create some logic to ensure creation and
addition to parent is done just one time.

An additional issue (that does not gives error) is that click event
handlers has binding expressions. That's not needed

instead of

click="{this.popByMethod.open = true}"

you write only:

click="popByMethod.open = true"


HTH

Carlos


El lun., 16 dic. 2019 a las 17:03, Carlos Rovira ()
escribió:

> Hi Carli,
> I'm going to try your code and see what I can report about it
>
> El lun., 16 dic. 2019 a las 16:56, De Carli Gustavo (<
> gustavodeca...@gmail.com>) escribió:
>
>> Hello, someone could be oriented because I do not have the same behavior
>> in the creation of a popup by msxml than by as. thank you very much
>> Method, popupByAs, is the problem, does nothing.
>>
>> thank
>>
>>
>> 
>> http://ns.adobe.com/mxml/2009;
>> xmlns:html="library://ns.apache.org/royale/html"
>> xmlns:j="library://ns.apache.org/royale/jewel"
>> xmlns:Button="main.components.Button.*"
>> xmlns:Form="main.components.Form.*"
>> xmlns:js="library://ns.apache.org/royale/basic"
>> xmlns:c="components.*">
>>
>> 
>> 
>> 
>>
>> 
>> 
>> > text="By Method MXML"
>> x="10"
>> y="200"
>> emphasis="primary"
>> click="{this.popByMethod.open = true}"/>
>>
>>
>> 
>> 
>> 
>>
>>
>> > text="By Metodo AS"
>> x="10"
>> y="200"
>> emphasis="primary"
>> click="{this.popupByAS(event)}"/>
>> 
>> 
>> 
>>
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

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

Re: Creation popup by as

[Carlos Rovira]

Hi Carli,
I'm going to try your code and see what I can report about it

El lun., 16 dic. 2019 a las 16:56, De Carli Gustavo (<
gustavodeca...@gmail.com>) escribió:

> Hello, someone could be oriented because I do not have the same behavior
> in the creation of a popup by msxml than by as. thank you very much
> Method, popupByAs, is the problem, does nothing.
>
> thank
>
>
> 
> http://ns.adobe.com/mxml/2009;
> xmlns:html="library://ns.apache.org/royale/html"
> xmlns:j="library://ns.apache.org/royale/jewel"
> xmlns:Button="main.components.Button.*"
> xmlns:Form="main.components.Form.*"
> xmlns:js="library://ns.apache.org/royale/basic"
> xmlns:c="components.*">
>
> 
> 
> 
>
> 
> 
>  text="By Method MXML"
> x="10"
> y="200"
> emphasis="primary"
> click="{this.popByMethod.open = true}"/>
>
>
> 
> 
> 
>
>
>  text="By Metodo AS"
> x="10"
> y="200"
> emphasis="primary"
> click="{this.popupByAS(event)}"/>
> 
> 
> 
>
>
>

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

Creation popup by as

[De Carli Gustavo]

Hello, someone could be oriented because I do not have the same behavior in
the creation of a popup by msxml than by as. thank you very much
Method, popupByAs, is the problem, does nothing.

thank



http://ns.adobe.com/mxml/2009;
xmlns:html="library://ns.apache.org/royale/html"
xmlns:j="library://ns.apache.org/royale/jewel"
xmlns:Button="main.components.Button.*"
xmlns:Form="main.components.Form.*"
xmlns:js="library://ns.apache.org/royale/basic"
xmlns:c="components.*">

Re: A part of Jewel

[Andrew Wetmore]

Thanks for catching up on that

On Mon, Dec 16, 2019 at 8:50 AM Carlos Rovira 
wrote:

> Hi Andrew,
>
> I reverted that commit since the I changed weeks ago all links to match
> the same pattern, i.e:  /jewel/themes or /jewe/button and be only permalinks
> I fixed all blog examples tutorials today in pre site (still not published
> to production) since links to royale docs wasn't working due to that issue
> and due to the migration to use only permalinks.
> Sorry, I didn't mention this one here, so you can't know about it.
>
> Thanks
>
> Carlos
>
>
>
> El lun., 16 dic. 2019 a las 13:39, Andrew Wetmore ()
> escribió:
>
>>   About the Jewel themes page, I see it at
>> https://apache.github.io/royale-docs/component-sets/jewel/jewel-themes.html
>>
>>
>> There was an error in the permalink for the page, and I have fixed it.
>> The fix should be available soon.
>>
>> Andrew
>>
>> On Mon, Dec 16, 2019 at 8:23 AM Takeshita Shoichiro 
>> wrote:
>>
>>> Carlos, thanks for your explanation.  I will study SASS.
>>>
>>> As to VS Code compilation, I cannot get the same output as the one using
>>> mvn.  I do not know how to specify three themes in asconfig.json, which
>>> would be the root cause.
>>> In the meantime, I need to use mvn.
>>>
>>> By the way, I'd like to know the current status of the following page.
>>>
>>> https://apache.github.io/royale-docs/component-sets/jewel#jewel-themes
>>>
>>> Thanks.
>>>
>>> On Mon, Dec 16, 2019 at 5:47 PM Carlos Rovira 
>>> wrote:
>>>
 Hi Takeshita,

 to clean the input is something you can do in a number of ways:

- You can just clear textinputs after navigate to the next screen,
so when you come back for whatever reason is clean
- You can send an Event when perform the LOGOUT to make the
textinputs be cleared

 This depends more on the structure of your app. Take into account that
 the example is just a very simple view state example on how that works.

 About skinning with CSS. I mean that really there's no a SKIN concept
 like in Flex 4, since in HTML we can just rely on CSS. So you can create
 custom CSS in you APP to add up to some concrete style in Jewel, or just
 override it completely. You have available all HTML infrastructure using
 "lclassName" or "style" (to go directly to low level html styling). That
 kind of things can be ok for few changes you want. If you need to create
 your own Theme (override all component styles or most of them), you can
 create your own JewelTheme. Copying the project and changing to your needs.
 I use in JewelTheme SASS since it give us structure and organization in
 files. SASS is for CSS like AS3/MXML for Javascript. A way to code it in a
 better and easy way and left the SASS compiler to minimize the output. You
 have SASS compilation only in Maven build for free. More info in Royale
 Docs in [1] & [2]

 [1] Jewel Themes
 
 [2] Jewel Theme Creation
 



 El lun., 16 dic. 2019 a las 2:35, Takeshita Shoichiro (<
 jl03...@gmail.com>) escribió:

> Carlos, thanks.
>
> I cloud center the login panel.
>
> This is just my preference. When showing the login panel, I would not
> see the preset data. And after pressing LOGOUT button, I’d like to clear
> the input. How can we clear the input?
>
> As to skin class replacement by CSS is also fine.  Can I see such an
> example?
>
>
>
> 2019年12月16日(月) 2:23 Carlos Rovira :
>
>> Hi Takeshita,
>>
>> El dom., 15 dic. 2019 a las 3:17, Takeshita Shoichiro (<
>> jl03...@gmail.com>) escribió:
>>
>>> Carlos, the current asconfig.json is fine.  One note is that we need
>>> to use  "targets": ["JSRoyale"], for JS only build.
>>> It seems I made some mistakes when creating a project BE0008 project
>>> in VS Code. This morning I tried again and things worked well.
>>>
>>
>> Thanks I committed the fix :)
>>
>>
>>> By the way, would you please advise me on how to display this Login
>>> panel at the center of the screen in Jewel?
>>>
>>
>> In the example just add a   to he View
>> beads. That's all.
>>
>>
>>> And does Jewel support skin class?
>>>
>>
>> Not for now. Skin support will depend on plans on Spark emulation.
>> Maybe @Alex, could give more light on the plans in SparkRoyale.
>> In the other hand, I must admit I was a big user of skins in Flex 4,
>> but in Royale since CSS seems to me more powerful that what we had in 
>> Flex
>> times, it don't miss that feature.
>>
>>
>>>
>>> Please also check the following links in your HTML document do not
>>> work.
>>>
>>> Where to go from here
>>>
>>>- View 

Re: A part of Jewel

[Carlos Rovira]

Hi Andrew,

I reverted that commit since the I changed weeks ago all links to match the
same pattern, i.e:  /jewel/themes or /jewe/button and be only permalinks
I fixed all blog examples tutorials today in pre site (still not published
to production) since links to royale docs wasn't working due to that issue
and due to the migration to use only permalinks.
Sorry, I didn't mention this one here, so you can't know about it.

Thanks

Carlos



El lun., 16 dic. 2019 a las 13:39, Andrew Wetmore ()
escribió:

>   About the Jewel themes page, I see it at
> https://apache.github.io/royale-docs/component-sets/jewel/jewel-themes.html
>
>
> There was an error in the permalink for the page, and I have fixed it. The
> fix should be available soon.
>
> Andrew
>
> On Mon, Dec 16, 2019 at 8:23 AM Takeshita Shoichiro 
> wrote:
>
>> Carlos, thanks for your explanation.  I will study SASS.
>>
>> As to VS Code compilation, I cannot get the same output as the one using
>> mvn.  I do not know how to specify three themes in asconfig.json, which
>> would be the root cause.
>> In the meantime, I need to use mvn.
>>
>> By the way, I'd like to know the current status of the following page.
>>
>> https://apache.github.io/royale-docs/component-sets/jewel#jewel-themes
>>
>> Thanks.
>>
>> On Mon, Dec 16, 2019 at 5:47 PM Carlos Rovira 
>> wrote:
>>
>>> Hi Takeshita,
>>>
>>> to clean the input is something you can do in a number of ways:
>>>
>>>- You can just clear textinputs after navigate to the next screen,
>>>so when you come back for whatever reason is clean
>>>- You can send an Event when perform the LOGOUT to make the
>>>textinputs be cleared
>>>
>>> This depends more on the structure of your app. Take into account that
>>> the example is just a very simple view state example on how that works.
>>>
>>> About skinning with CSS. I mean that really there's no a SKIN concept
>>> like in Flex 4, since in HTML we can just rely on CSS. So you can create
>>> custom CSS in you APP to add up to some concrete style in Jewel, or just
>>> override it completely. You have available all HTML infrastructure using
>>> "lclassName" or "style" (to go directly to low level html styling). That
>>> kind of things can be ok for few changes you want. If you need to create
>>> your own Theme (override all component styles or most of them), you can
>>> create your own JewelTheme. Copying the project and changing to your needs.
>>> I use in JewelTheme SASS since it give us structure and organization in
>>> files. SASS is for CSS like AS3/MXML for Javascript. A way to code it in a
>>> better and easy way and left the SASS compiler to minimize the output. You
>>> have SASS compilation only in Maven build for free. More info in Royale
>>> Docs in [1] & [2]
>>>
>>> [1] Jewel Themes
>>> 
>>> [2] Jewel Theme Creation
>>> 
>>>
>>>
>>>
>>> El lun., 16 dic. 2019 a las 2:35, Takeshita Shoichiro (<
>>> jl03...@gmail.com>) escribió:
>>>
 Carlos, thanks.

 I cloud center the login panel.

 This is just my preference. When showing the login panel, I would not
 see the preset data. And after pressing LOGOUT button, I’d like to clear
 the input. How can we clear the input?

 As to skin class replacement by CSS is also fine.  Can I see such an
 example?



 2019年12月16日(月) 2:23 Carlos Rovira :

> Hi Takeshita,
>
> El dom., 15 dic. 2019 a las 3:17, Takeshita Shoichiro (<
> jl03...@gmail.com>) escribió:
>
>> Carlos, the current asconfig.json is fine.  One note is that we need
>> to use  "targets": ["JSRoyale"], for JS only build.
>> It seems I made some mistakes when creating a project BE0008 project
>> in VS Code. This morning I tried again and things worked well.
>>
>
> Thanks I committed the fix :)
>
>
>> By the way, would you please advise me on how to display this Login
>> panel at the center of the screen in Jewel?
>>
>
> In the example just add a   to he View
> beads. That's all.
>
>
>> And does Jewel support skin class?
>>
>
> Not for now. Skin support will depend on plans on Spark emulation.
> Maybe @Alex, could give more light on the plans in SparkRoyale.
> In the other hand, I must admit I was a big user of skins in Flex 4,
> but in Royale since CSS seems to me more powerful that what we had in Flex
> times, it don't miss that feature.
>
>
>>
>> Please also check the following links in your HTML document do not
>> work.
>>
>> Where to go from here
>>
>>- View States Royale Docs page
>>
>> 
>>- Jewel TextInput Royale Docs page
>>
>> 

Re: A part of Jewel

[Carlos Rovira]

Hi Takeshita,

I had the same problem. I added this issue in VSCode GitHub [1] so Josh
could give us some guidance.

[1] https://github.com/BowlerHatLLC/vscode-as3mxml/issues/433




El lun., 16 dic. 2019 a las 13:23, Takeshita Shoichiro ()
escribió:

> Carlos, thanks for your explanation.  I will study SASS.
>
> As to VS Code compilation, I cannot get the same output as the one using
> mvn.  I do not know how to specify three themes in asconfig.json, which
> would be the root cause.
> In the meantime, I need to use mvn.
>
> By the way, I'd like to know the current status of the following page.
>
> https://apache.github.io/royale-docs/component-sets/jewel#jewel-themes
>
> Thanks.
>
> On Mon, Dec 16, 2019 at 5:47 PM Carlos Rovira 
> wrote:
>
>> Hi Takeshita,
>>
>> to clean the input is something you can do in a number of ways:
>>
>>- You can just clear textinputs after navigate to the next screen, so
>>when you come back for whatever reason is clean
>>- You can send an Event when perform the LOGOUT to make the
>>textinputs be cleared
>>
>> This depends more on the structure of your app. Take into account that
>> the example is just a very simple view state example on how that works.
>>
>> About skinning with CSS. I mean that really there's no a SKIN concept
>> like in Flex 4, since in HTML we can just rely on CSS. So you can create
>> custom CSS in you APP to add up to some concrete style in Jewel, or just
>> override it completely. You have available all HTML infrastructure using
>> "lclassName" or "style" (to go directly to low level html styling). That
>> kind of things can be ok for few changes you want. If you need to create
>> your own Theme (override all component styles or most of them), you can
>> create your own JewelTheme. Copying the project and changing to your needs.
>> I use in JewelTheme SASS since it give us structure and organization in
>> files. SASS is for CSS like AS3/MXML for Javascript. A way to code it in a
>> better and easy way and left the SASS compiler to minimize the output. You
>> have SASS compilation only in Maven build for free. More info in Royale
>> Docs in [1] & [2]
>>
>> [1] Jewel Themes
>> 
>> [2] Jewel Theme Creation
>> 
>>
>>
>>
>> El lun., 16 dic. 2019 a las 2:35, Takeshita Shoichiro ()
>> escribió:
>>
>>> Carlos, thanks.
>>>
>>> I cloud center the login panel.
>>>
>>> This is just my preference. When showing the login panel, I would not
>>> see the preset data. And after pressing LOGOUT button, I’d like to clear
>>> the input. How can we clear the input?
>>>
>>> As to skin class replacement by CSS is also fine.  Can I see such an
>>> example?
>>>
>>>
>>>
>>> 2019年12月16日(月) 2:23 Carlos Rovira :
>>>
 Hi Takeshita,

 El dom., 15 dic. 2019 a las 3:17, Takeshita Shoichiro (<
 jl03...@gmail.com>) escribió:

> Carlos, the current asconfig.json is fine.  One note is that we need
> to use  "targets": ["JSRoyale"], for JS only build.
> It seems I made some mistakes when creating a project BE0008 project
> in VS Code. This morning I tried again and things worked well.
>

 Thanks I committed the fix :)


> By the way, would you please advise me on how to display this Login
> panel at the center of the screen in Jewel?
>

 In the example just add a   to he View
 beads. That's all.


> And does Jewel support skin class?
>

 Not for now. Skin support will depend on plans on Spark emulation.
 Maybe @Alex, could give more light on the plans in SparkRoyale.
 In the other hand, I must admit I was a big user of skins in Flex 4,
 but in Royale since CSS seems to me more powerful that what we had in Flex
 times, it don't miss that feature.


>
> Please also check the following links in your HTML document do not
> work.
>
> Where to go from here
>
>- View States Royale Docs page
>
> 
>- Jewel TextInput Royale Docs page
>
> 
>- Jewel Button Royale Docs page
>
> 
>- Jewel Card Royale Docs page
>
> 
>
>
>
 Thanks for letting me know, I fixed in pre site. I'll try to publish
 changes soon

 Thanks!

 Carlos



>
> On Sat, Dec 14, 2019 at 12:17 AM Carlos Rovira <
> carlosrov...@apache.org> wrote:
>
>> Hi Takehita,
>>
>> thanks for looking into it. As expected, maven is set up but the rest
>> of build system are not. if you want to 

Re: blog/BE0011_Loading_external_data_through_HTTPService

[Carlos Rovira]

Hi Takeshita,

the fail indicates that you didn't build the themes.
You can go to framework/themes and build "mvn install"
Themes are build when you build entire repo normally



El lun., 16 dic. 2019 a las 13:17, Takeshita Shoichiro ()
escribió:

> Carlos,
>
> Thanks.  I'be just downloaded the night build and run mvn clean install
> under \blog directory.
>
> It only built BE0001.
>
> The following are console errors (Windows 10).  Can I run mvn in blog
> directory?  Or some other problems?
>
> O] 
> [INFO] Reactor Summary for Apache Royale: Examples: Blog 0.9.7-SNAPSHOT:
> [INFO]
> [INFO] Apache Royale: Examples: Blog .. SUCCESS [01:01
> min]
> [INFO] Apache Royale: Examples: Blog: 0001: Hello World ... SUCCESS [
> 14.558 s]
> [INFO] Apache Royale: Examples: Blog: 0002: Using Jewel Alert Control
> FAILURE [ 21.684 s]
> [INFO] Apache Royale: Examples: Blog: 0003: Using Jewel HSlider Control
> SKIPPED
> [INFO] Apache Royale: Examples: Blog: 0004: Adding an item to a Jewel List
> SKIPPED
> [INFO] Apache Royale: Examples: Blog: 0005: Creating a group of Jewel
> RadioButtons SKIPPED
> [INFO] Apache Royale: Examples: Blog: 0006: Binding the text property of a
> Jewel Textinput to update a text label SKIPPED
> [INFO] Apache Royale: Examples: Blog: 0007: Selecting options from a group
> of jewel checkbox controls SKIPPED
> [INFO] Apache Royale: Examples: Blog: 0008: Using View States to show or
> hide content SKIPPED
> [INFO] Apache Royale: Examples: Blog: 0009: Using an Item Renderer with a
> List SKIPPED
> [INFO] Apache Royale: Examples: Blog: 0010: Customization through the
> Royale API SKIPPED
> [INFO] Apache Royale: Examples: Blog: 0011: Loading external data through
> HTTPService SKIPPED
> [INFO] Apache Royale: Examples: Blog: 0012: Using external javascript
> libraries in Apache Royale SKIPPED
> [INFO] Apache Royale: Examples: Blog: 0013: Dividing an Apache Royale
> application with modules SKIPPED
> [INFO] BE0013_Dividing_an_Apache_Royale_application_with_modules:
> MainJewelApp SKIPPED
> [INFO] BE0013_Dividing_an_Apache_Royale_application_with_modules:
> JewelModule SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time:  02:00 min
> [INFO] Finished at: 2019-12-16T21:11:32+09:00
> [INFO]
> 
> [ERROR] Failed to execute goal on project
> BE0002_Using_Jewel_Alert_Control: Could not resolve dependencies for
> project
> org.apache.royale.examples:BE0002_Using_Jewel_Alert_Control:swf:0.9.7-SNAPSHOT:
> Could not find artifact
> org.apache.royale.framework:Jewel-Light-NoFlat-Emphasized-Red-Theme:swc:0.9.7-SNAPSHOT
> in apache.snapshots (https://repository.apache.org/snapshots) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :BE0002_Using_Jewel_Alert_Control
>
> On Mon, Dec 16, 2019 at 4:48 AM Carlos Rovira 
> wrote:
>
>> Hi,
>>
>> just fixed all examples maven compilation
>>
>>
>> El dom., 15 dic. 2019 a las 20:28, Carlos Rovira (<
>> carlosrov...@apache.org>) escribió:
>>
>>> Hi,
>>>
>>> I went through all the blog examples and fixed all. As well put
>>> asconfig.json working. ANT and Moonshine should be fixed by others with the
>>> time to contribute that.
>>>
>>> I'm know checking the rest of examples to fix mostly child tags prefixes
>>>
>>>
>>>
>>> El dom., 15 dic. 2019 a las 18:49, Carlos Rovira (<
>>> carlosrov...@apache.org>) escribió:
>>>
 Hi Takeshita,

 just fixed both examples.
 Some of the problems was due to child nodes in mxml not having the
 right prefix. Josh fixed that in compiler recently and we can still have
 examples broken for that. Can you please submit PR if you find others
 broken?.
 In BE0011, the main GitHubService object was not in x:Declaration tag.
 I was not aware, that is currently needed. Other seems to fix that in the
 past weeks.
 Notice that BE0012 apart from the fixes if run in localhost, since is
 loading a text file from other domain you need to remove CORS restrictions
 in your browser. I'll be adding a note in the tutorial, since others could
 not take that into account and think the example is broken.

 Thanks for catching and reporting all this! Very useful!! As we fix
 things here and there we need to catch this 

Re: A part of Jewel

[Andrew Wetmore]

  About the Jewel themes page, I see it at
https://apache.github.io/royale-docs/component-sets/jewel/jewel-themes.html

There was an error in the permalink for the page, and I have fixed it. The
fix should be available soon.

Andrew

On Mon, Dec 16, 2019 at 8:23 AM Takeshita Shoichiro 
wrote:

> Carlos, thanks for your explanation.  I will study SASS.
>
> As to VS Code compilation, I cannot get the same output as the one using
> mvn.  I do not know how to specify three themes in asconfig.json, which
> would be the root cause.
> In the meantime, I need to use mvn.
>
> By the way, I'd like to know the current status of the following page.
>
> https://apache.github.io/royale-docs/component-sets/jewel#jewel-themes
>
> Thanks.
>
> On Mon, Dec 16, 2019 at 5:47 PM Carlos Rovira 
> wrote:
>
>> Hi Takeshita,
>>
>> to clean the input is something you can do in a number of ways:
>>
>>- You can just clear textinputs after navigate to the next screen, so
>>when you come back for whatever reason is clean
>>- You can send an Event when perform the LOGOUT to make the
>>textinputs be cleared
>>
>> This depends more on the structure of your app. Take into account that
>> the example is just a very simple view state example on how that works.
>>
>> About skinning with CSS. I mean that really there's no a SKIN concept
>> like in Flex 4, since in HTML we can just rely on CSS. So you can create
>> custom CSS in you APP to add up to some concrete style in Jewel, or just
>> override it completely. You have available all HTML infrastructure using
>> "lclassName" or "style" (to go directly to low level html styling). That
>> kind of things can be ok for few changes you want. If you need to create
>> your own Theme (override all component styles or most of them), you can
>> create your own JewelTheme. Copying the project and changing to your needs.
>> I use in JewelTheme SASS since it give us structure and organization in
>> files. SASS is for CSS like AS3/MXML for Javascript. A way to code it in a
>> better and easy way and left the SASS compiler to minimize the output. You
>> have SASS compilation only in Maven build for free. More info in Royale
>> Docs in [1] & [2]
>>
>> [1] Jewel Themes
>> 
>> [2] Jewel Theme Creation
>> 
>>
>>
>>
>> El lun., 16 dic. 2019 a las 2:35, Takeshita Shoichiro ()
>> escribió:
>>
>>> Carlos, thanks.
>>>
>>> I cloud center the login panel.
>>>
>>> This is just my preference. When showing the login panel, I would not
>>> see the preset data. And after pressing LOGOUT button, I’d like to clear
>>> the input. How can we clear the input?
>>>
>>> As to skin class replacement by CSS is also fine.  Can I see such an
>>> example?
>>>
>>>
>>>
>>> 2019年12月16日(月) 2:23 Carlos Rovira :
>>>
 Hi Takeshita,

 El dom., 15 dic. 2019 a las 3:17, Takeshita Shoichiro (<
 jl03...@gmail.com>) escribió:

> Carlos, the current asconfig.json is fine.  One note is that we need
> to use  "targets": ["JSRoyale"], for JS only build.
> It seems I made some mistakes when creating a project BE0008 project
> in VS Code. This morning I tried again and things worked well.
>

 Thanks I committed the fix :)


> By the way, would you please advise me on how to display this Login
> panel at the center of the screen in Jewel?
>

 In the example just add a   to he View
 beads. That's all.


> And does Jewel support skin class?
>

 Not for now. Skin support will depend on plans on Spark emulation.
 Maybe @Alex, could give more light on the plans in SparkRoyale.
 In the other hand, I must admit I was a big user of skins in Flex 4,
 but in Royale since CSS seems to me more powerful that what we had in Flex
 times, it don't miss that feature.


>
> Please also check the following links in your HTML document do not
> work.
>
> Where to go from here
>
>- View States Royale Docs page
>
> 
>- Jewel TextInput Royale Docs page
>
> 
>- Jewel Button Royale Docs page
>
> 
>- Jewel Card Royale Docs page
>
> 
>
>
>
 Thanks for letting me know, I fixed in pre site. I'll try to publish
 changes soon

 Thanks!

 Carlos



>
> On Sat, Dec 14, 2019 at 12:17 AM Carlos Rovira <
> carlosrov...@apache.org> wrote:
>
>> Hi Takehita,
>>
>> thanks for looking into it. As expected, maven is set up but the rest

Re: A part of Jewel

[Takeshita Shoichiro]

Carlos, thanks for your explanation.  I will study SASS.

As to VS Code compilation, I cannot get the same output as the one using
mvn.  I do not know how to specify three themes in asconfig.json, which
would be the root cause.
In the meantime, I need to use mvn.

By the way, I'd like to know the current status of the following page.

https://apache.github.io/royale-docs/component-sets/jewel#jewel-themes

Thanks.

On Mon, Dec 16, 2019 at 5:47 PM Carlos Rovira 
wrote:

> Hi Takeshita,
>
> to clean the input is something you can do in a number of ways:
>
>- You can just clear textinputs after navigate to the next screen, so
>when you come back for whatever reason is clean
>- You can send an Event when perform the LOGOUT to make the textinputs
>be cleared
>
> This depends more on the structure of your app. Take into account that the
> example is just a very simple view state example on how that works.
>
> About skinning with CSS. I mean that really there's no a SKIN concept like
> in Flex 4, since in HTML we can just rely on CSS. So you can create custom
> CSS in you APP to add up to some concrete style in Jewel, or just override
> it completely. You have available all HTML infrastructure using
> "lclassName" or "style" (to go directly to low level html styling). That
> kind of things can be ok for few changes you want. If you need to create
> your own Theme (override all component styles or most of them), you can
> create your own JewelTheme. Copying the project and changing to your needs.
> I use in JewelTheme SASS since it give us structure and organization in
> files. SASS is for CSS like AS3/MXML for Javascript. A way to code it in a
> better and easy way and left the SASS compiler to minimize the output. You
> have SASS compilation only in Maven build for free. More info in Royale
> Docs in [1] & [2]
>
> [1] Jewel Themes
> 
> [2] Jewel Theme Creation
> 
>
>
>
> El lun., 16 dic. 2019 a las 2:35, Takeshita Shoichiro ()
> escribió:
>
>> Carlos, thanks.
>>
>> I cloud center the login panel.
>>
>> This is just my preference. When showing the login panel, I would not see
>> the preset data. And after pressing LOGOUT button, I’d like to clear the
>> input. How can we clear the input?
>>
>> As to skin class replacement by CSS is also fine.  Can I see such an
>> example?
>>
>>
>>
>> 2019年12月16日(月) 2:23 Carlos Rovira :
>>
>>> Hi Takeshita,
>>>
>>> El dom., 15 dic. 2019 a las 3:17, Takeshita Shoichiro (<
>>> jl03...@gmail.com>) escribió:
>>>
 Carlos, the current asconfig.json is fine.  One note is that we need to
 use  "targets": ["JSRoyale"], for JS only build.
 It seems I made some mistakes when creating a project BE0008 project in
 VS Code. This morning I tried again and things worked well.

>>>
>>> Thanks I committed the fix :)
>>>
>>>
 By the way, would you please advise me on how to display this Login
 panel at the center of the screen in Jewel?

>>>
>>> In the example just add a   to he View
>>> beads. That's all.
>>>
>>>
 And does Jewel support skin class?

>>>
>>> Not for now. Skin support will depend on plans on Spark emulation.
>>> Maybe @Alex, could give more light on the plans in SparkRoyale.
>>> In the other hand, I must admit I was a big user of skins in Flex 4, but
>>> in Royale since CSS seems to me more powerful that what we had in Flex
>>> times, it don't miss that feature.
>>>
>>>

 Please also check the following links in your HTML document do not work.

 Where to go from here

- View States Royale Docs page

 
- Jewel TextInput Royale Docs page

 
- Jewel Button Royale Docs page

 
- Jewel Card Royale Docs page

 



>>> Thanks for letting me know, I fixed in pre site. I'll try to publish
>>> changes soon
>>>
>>> Thanks!
>>>
>>> Carlos
>>>
>>>
>>>

 On Sat, Dec 14, 2019 at 12:17 AM Carlos Rovira 
 wrote:

> Hi Takehita,
>
> thanks for looking into it. As expected, maven is set up but the rest
> of build system are not. if you want to fix it and submit PR would be 
> great
> :)
>
> Best
>
> Carlos
>
> El vie., 13 dic. 2019 a las 14:18, Takeshita Shoichiro (<
> jl03...@gmail.com>) escribió:
>
>> Carlos, I could see the output with maven clean install on Mac.
>>
>> But, VS Code compilation against it (project is copied to the
>> different directory) does not create the output to be shown on the 
>> 

Re: blog/BE0011_Loading_external_data_through_HTTPService

[Takeshita Shoichiro]

Carlos,

Thanks.  I'be just downloaded the night build and run mvn clean install
under \blog directory.

It only built BE0001.

The following are console errors (Windows 10).  Can I run mvn in blog
directory?  Or some other problems?

O] 
[INFO] Reactor Summary for Apache Royale: Examples: Blog 0.9.7-SNAPSHOT:
[INFO]
[INFO] Apache Royale: Examples: Blog .. SUCCESS [01:01
min]
[INFO] Apache Royale: Examples: Blog: 0001: Hello World ... SUCCESS [
14.558 s]
[INFO] Apache Royale: Examples: Blog: 0002: Using Jewel Alert Control
FAILURE [ 21.684 s]
[INFO] Apache Royale: Examples: Blog: 0003: Using Jewel HSlider Control
SKIPPED
[INFO] Apache Royale: Examples: Blog: 0004: Adding an item to a Jewel List
SKIPPED
[INFO] Apache Royale: Examples: Blog: 0005: Creating a group of Jewel
RadioButtons SKIPPED
[INFO] Apache Royale: Examples: Blog: 0006: Binding the text property of a
Jewel Textinput to update a text label SKIPPED
[INFO] Apache Royale: Examples: Blog: 0007: Selecting options from a group
of jewel checkbox controls SKIPPED
[INFO] Apache Royale: Examples: Blog: 0008: Using View States to show or
hide content SKIPPED
[INFO] Apache Royale: Examples: Blog: 0009: Using an Item Renderer with a
List SKIPPED
[INFO] Apache Royale: Examples: Blog: 0010: Customization through the
Royale API SKIPPED
[INFO] Apache Royale: Examples: Blog: 0011: Loading external data through
HTTPService SKIPPED
[INFO] Apache Royale: Examples: Blog: 0012: Using external javascript
libraries in Apache Royale SKIPPED
[INFO] Apache Royale: Examples: Blog: 0013: Dividing an Apache Royale
application with modules SKIPPED
[INFO] BE0013_Dividing_an_Apache_Royale_application_with_modules:
MainJewelApp SKIPPED
[INFO] BE0013_Dividing_an_Apache_Royale_application_with_modules:
JewelModule SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time:  02:00 min
[INFO] Finished at: 2019-12-16T21:11:32+09:00
[INFO]

[ERROR] Failed to execute goal on project BE0002_Using_Jewel_Alert_Control:
Could not resolve dependencies for project
org.apache.royale.examples:BE0002_Using_Jewel_Alert_Control:swf:0.9.7-SNAPSHOT:
Could not find artifact
org.apache.royale.framework:Jewel-Light-NoFlat-Emphasized-Red-Theme:swc:0.9.7-SNAPSHOT
in apache.snapshots (https://repository.apache.org/snapshots) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :BE0002_Using_Jewel_Alert_Control

On Mon, Dec 16, 2019 at 4:48 AM Carlos Rovira 
wrote:

> Hi,
>
> just fixed all examples maven compilation
>
>
> El dom., 15 dic. 2019 a las 20:28, Carlos Rovira ()
> escribió:
>
>> Hi,
>>
>> I went through all the blog examples and fixed all. As well put
>> asconfig.json working. ANT and Moonshine should be fixed by others with the
>> time to contribute that.
>>
>> I'm know checking the rest of examples to fix mostly child tags prefixes
>>
>>
>>
>> El dom., 15 dic. 2019 a las 18:49, Carlos Rovira (<
>> carlosrov...@apache.org>) escribió:
>>
>>> Hi Takeshita,
>>>
>>> just fixed both examples.
>>> Some of the problems was due to child nodes in mxml not having the right
>>> prefix. Josh fixed that in compiler recently and we can still have examples
>>> broken for that. Can you please submit PR if you find others broken?.
>>> In BE0011, the main GitHubService object was not in x:Declaration tag. I
>>> was not aware, that is currently needed. Other seems to fix that in the
>>> past weeks.
>>> Notice that BE0012 apart from the fixes if run in localhost, since is
>>> loading a text file from other domain you need to remove CORS restrictions
>>> in your browser. I'll be adding a note in the tutorial, since others could
>>> not take that into account and think the example is broken.
>>>
>>> Thanks for catching and reporting all this! Very useful!! As we fix
>>> things here and there we need to catch this problems. Hopefully Royale is
>>> enough robust these days and each day we have less and lees issues :)
>>>
>>> Thanks!
>>>
>>>
>>>
>>> El dom., 15 dic. 2019 a las 10:36, Takeshita Shoichiro (<
>>> jl03...@gmail.com>) escribió:
>>>
 Carlos,

 js-debug/index.html does not show output on the browser.
 js-release/index.html does show the output on the other hand.

 I run mvn clean install against 0.96 on Mac.
 Would you please check.

Re: A part of Jewel

[Carlos Rovira]

Hi Takeshita,

to clean the input is something you can do in a number of ways:

   - You can just clear textinputs after navigate to the next screen, so
   when you come back for whatever reason is clean
   - You can send an Event when perform the LOGOUT to make the textinputs
   be cleared

This depends more on the structure of your app. Take into account that the
example is just a very simple view state example on how that works.

About skinning with CSS. I mean that really there's no a SKIN concept like
in Flex 4, since in HTML we can just rely on CSS. So you can create custom
CSS in you APP to add up to some concrete style in Jewel, or just override
it completely. You have available all HTML infrastructure using
"lclassName" or "style" (to go directly to low level html styling). That
kind of things can be ok for few changes you want. If you need to create
your own Theme (override all component styles or most of them), you can
create your own JewelTheme. Copying the project and changing to your needs.
I use in JewelTheme SASS since it give us structure and organization in
files. SASS is for CSS like AS3/MXML for Javascript. A way to code it in a
better and easy way and left the SASS compiler to minimize the output. You
have SASS compilation only in Maven build for free. More info in Royale
Docs in [1] & [2]

[1] Jewel Themes

[2] Jewel Theme Creation




El lun., 16 dic. 2019 a las 2:35, Takeshita Shoichiro ()
escribió:

> Carlos, thanks.
>
> I cloud center the login panel.
>
> This is just my preference. When showing the login panel, I would not see
> the preset data. And after pressing LOGOUT button, I’d like to clear the
> input. How can we clear the input?
>
> As to skin class replacement by CSS is also fine.  Can I see such an
> example?
>
>
>
> 2019年12月16日(月) 2:23 Carlos Rovira :
>
>> Hi Takeshita,
>>
>> El dom., 15 dic. 2019 a las 3:17, Takeshita Shoichiro ()
>> escribió:
>>
>>> Carlos, the current asconfig.json is fine.  One note is that we need to
>>> use  "targets": ["JSRoyale"], for JS only build.
>>> It seems I made some mistakes when creating a project BE0008 project in
>>> VS Code. This morning I tried again and things worked well.
>>>
>>
>> Thanks I committed the fix :)
>>
>>
>>> By the way, would you please advise me on how to display this Login
>>> panel at the center of the screen in Jewel?
>>>
>>
>> In the example just add a   to he View
>> beads. That's all.
>>
>>
>>> And does Jewel support skin class?
>>>
>>
>> Not for now. Skin support will depend on plans on Spark emulation.
>> Maybe @Alex, could give more light on the plans in SparkRoyale.
>> In the other hand, I must admit I was a big user of skins in Flex 4, but
>> in Royale since CSS seems to me more powerful that what we had in Flex
>> times, it don't miss that feature.
>>
>>
>>>
>>> Please also check the following links in your HTML document do not work.
>>>
>>> Where to go from here
>>>
>>>- View States Royale Docs page
>>>
>>> 
>>>- Jewel TextInput Royale Docs page
>>>
>>> 
>>>- Jewel Button Royale Docs page
>>>
>>> 
>>>- Jewel Card Royale Docs page
>>>
>>> 
>>>
>>>
>>>
>> Thanks for letting me know, I fixed in pre site. I'll try to publish
>> changes soon
>>
>> Thanks!
>>
>> Carlos
>>
>>
>>
>>>
>>> On Sat, Dec 14, 2019 at 12:17 AM Carlos Rovira 
>>> wrote:
>>>
 Hi Takehita,

 thanks for looking into it. As expected, maven is set up but the rest
 of build system are not. if you want to fix it and submit PR would be great
 :)

 Best

 Carlos

 El vie., 13 dic. 2019 a las 14:18, Takeshita Shoichiro (<
 jl03...@gmail.com>) escribió:

> Carlos, I could see the output with maven clean install on Mac.
>
> But, VS Code compilation against it (project is copied to the
> different directory) does not create the output to be shown on the browser
> (Windows 10 Chrome).
>
> I will examine the problem tomorrow.
>
> On Fri, Dec 13, 2019 at 8:27 PM Carlos Rovira 
> wrote:
>
>> Hi,
>>
>> Blog examples was created with maven build system. Unless others
>> setup ANT, or IDE configs, I can't guarantee it would work.
>> I think others like you can try and fix if needed that config files
>> and submit as a PR to improve it.
>>
>> Thanks!
>>
>> Carlos
>>
>>
>>
>> El vie., 13 dic. 2019 a las 8:47, Takeshita Shoichiro (<
>> jl03...@gmail.com>) escribió:
>>
>>> Carlos, thanks a lot.
>>>
>>> There might be