Re: [royale-asjs] branch develop updated: Jewel Group: Fix dynamic adding Horizontal/Vertical layout

Ok Piotr, thanks El lun., 28 ene. 2019 a las 21:17, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Hi Carlos, > > Ok I will revert changes soon. > > Thanks, > Piotr > > niedz., 27 sty 2019 o 18:04 Carlos Rovira > napisał(a): > > > Hi Piotr, > > > > thinking on it better, I prefer your

Re: FormItemView changes

Piotr, I think your problem is with having no gap between items right? you can get it adding "gap:3" (search for that in other parts of Jewel) for example: .verticalContentFormItem { IFormItemContentArea: ClassReference("org.apache.royale.jewel.VGroup"); gap: 3; } remember to add this in sass a

Re: [royale-compiler] branch develop updated: compiler-jx: Assigning a value to an int or uint coerces it so that variables don't store decimal values (closes #74)

Hi Josh, I'm not sure if it's related but I just build two applications using latest sources and both of them are not working. I'm getting following error in console [1] It happened in function: org.apache.royale.utils.Language.string = function(value) { return org.apache.royale.utils.Language.

Re: FormItemView changes

Carlos, I wrote about that problem, cause I simply was searching an answer - and this one provided by you probably resolve issue, but I'm not sure if it should be part of framework. Let's think about it. User has default: IFormItemContentArea: ClassReference("org.apache.royale.jewel.Group"); - I

Build failed in Jenkins: royale-asjs #1868

See -- [...truncated 2.39 MB...] [mxmlc] org.apache.royale.core.SimpleStatesImpl depends on org.apache.royale.core.IBead [mxmlc] Dependencies calculated f

Re: [royale-compiler] branch develop updated: compiler-jx: Assigning a value to an int or uint coerces it so that variables don't store decimal values (closes #74)

Language.string needed a cast. I just committed a fix for that. I think it was a side effect of Josh fixing string casting… ;-) Harbs > On Jan 29, 2019, at 12:46 PM, Piotr Zarzycki > wrote: > > Hi Josh, > > I'm not sure if it's related but I just build two applications using latest > sources

Re: FormItem and center align

Hi Piotr, don't understand the problem just with that info. The problem is about the "!important" part? what was your solution to solve it? we need to see all the scenario in order to get the best response and make the setup of Jewel as much flexible as possible thanks El mar., 29 ene. 2019 a

Re: FormItem and center align

Carlos, Problem itself was resolved in my code (to me it's workaround), but I'm saying that you are assuming that all items in FormItem are centered which in my opinion shouldn't happen. It has been done by that code [1] - In users application he need to override this one in order to have it for e

Re: [royale-compiler] branch develop updated: compiler-jx: Assigning a value to an int or uint coerces it so that variables don't store decimal values (closes #74)

Hi Harbs, I rebuild all with the latest change but seems the problem is still there. Now I get this: RangeError: Maximum call stack size exceeded Language.js:115 at String.toString () at Function.org.apache.royale.utils.Language.string (/Users/carlosrovira/Dev/Codeoscopic/Source/sgc/webapp/src/ma

Re: FormItemView changes

Group doesn't support gap since items are positioned absolutely. gap starts to have sense in Horizontal and Vertical layouts El mar., 29 ene. 2019 a las 11:50, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Carlos, > > I wrote about that problem, cause I simply was searching an answer

Re: Problems dealing with bead substitution in Royale

Hi Alex, El lun., 28 ene. 2019 a las 17:22, Alex Harui () escribió: > It is fine to have a utility function such as this, but IMO, it doesn't > actually solve the problem. If the original bead does not know how to > remove itself, then a version of that bead needs to be created that does > know

Re: Problems dealing with bead substitution in Royale

That sounds good Harbs, you could that of if you want to save some effort, first make a new email thread with some example of code on how this would look in the end, so we all can understand it and provide some feedback so your effort could be more easy in the end. El lun., 28 ene. 2019 a las 17:2

Re: Problems dealing with bead substitution in Royale

Agree too. We can have more beads to give options as already happens in other parts of Royale. So don't see a problem your stacked version could come in. Also, as I have time, I could review and see if I could provide some support so we can get all of it more integrated... Most of the things in Jew

Re: [royale-compiler] branch develop updated: compiler-jx: Assigning a value to an int or uint coerces it so that variables don't store decimal values (closes #74)

You’re right. I just committed a work-around. > On Jan 29, 2019, at 2:00 PM, Carlos Rovira wrote: > > Hi Harbs, > > I rebuild all with the latest change but seems the problem is still there. > Now I get this: > > RangeError: Maximum call stack size exceeded > Language.js:115 > at String.toStr

Re: [royale-compiler] branch develop updated: compiler-jx: Assigning a value to an int or uint coerces it so that variables don't store decimal values (closes #74)

Thanks Harbs, that worked! :) El mar., 29 ene. 2019 a las 13:30, Harbs () escribió: > You’re right. > > I just committed a work-around. > > > On Jan 29, 2019, at 2:00 PM, Carlos Rovira > wrote: > > > > Hi Harbs, > > > > I rebuild all with the latest change but seems the problem is still > there.

Jenkins build is back to normal : royale-asjs_jsonly #2367

See

Jenkins build is back to normal : royale-asjs #1869

See

Re: FormItemView changes

Carlos, This one won't work. .verticalContentFormItem { IFormItemContentArea: ClassReference("org.apache.royale.jewel.VGroup"); gap: 3; } Cause how that gap would be propagated to IFormItemContentArea ? I think the solution is here if someone wanted to have gap between elements he need to provid

Re: FormItemView changes

To better reflect what I was actually have in mind from user point of view I have committed changes to TourDeJewel. You can take a look. Form looks the same as it was now. wt., 29 sty 2019 o 15:52 Piotr Zarzycki napisał(a): > Carlos, > > This one won't work. > > .verticalContentFormItem > { > IF

Re: FormItem and center align

Hi Piotr, In > users application he need to override this one in order to have it for > example aligned to left. > > I think you're assuming that centering is "horizontal", but "itemsCentered" refers to vertical centering (that's how flex-box is designed) So removing that makes all items (label, r

Re: FormItemView changes

Hi Piotr, I think you missed my latest response or I didn't could translate the main idea: Group doesn't have gap. So "he need to provide appropriate Group with gap - Am I right ?" is not right to figure that. El mar., 29 ene. 2019 a las 15:52, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escr

Re: FormItemView changes

I know that Group doesn't have gap. I'm saying that IF I would like to have children layed out differently - I will have to provide my own Group - VGroup for example. IF I would like to have those children laying out vertically with gap - my Group should come with that gap. wt., 29 sty 2019 o 16:

Re: FormItemView changes

By "my Group" - I'm not saying about Group component specifically - I'm talking about component which allows you to specify that gap for example VGroup. wt., 29 sty 2019 o 16:31 Piotr Zarzycki napisał(a): > I know that Group doesn't have gap. I'm saying that IF I would like to > have children la

Re: FormItemView changes

Going to try it El mar., 29 ene. 2019 a las 16:03, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > To better reflect what I was actually have in mind from user point of view > I have committed changes to TourDeJewel. You can take a look. Form looks > the same as it was now. > > wt., 29

Re: FormItemView changes

Hi Piotr, ok I saw the problem. You are having issues trying to configure the content from the parent component (the form item itself). But looking at the code I think there's some confusion For example, the code in the FormItemView with the coment // add the layout bead to the content area. *I

Re: FormItemView changes

Carlos, Comment was your probably - i forgot to remove it. Comments inline. wt., 29 sty 2019 o 17:04 Carlos Rovira napisał(a): > Hi Piotr, > > ok I saw the problem. You are having issues trying to configure the content > from the parent component (the form item itself). > > But looking at the

Re: FormItemView changes

I'm sorry you were saying " write that code avoiding since the default (to Group) will be useless most of the times." - so Group in your opinion will be used not so often - just opposite than I wrote. wt., 29 sty 2019 o 17:19 Piotr Zarzycki napisał(a): > Carlos, > > Comment was your probably - i

URLRequest

Hi: I am using URLRequest to send information to a web. But I do not know how to fill the property: data. This is my code: var urlRequest: URLRequest = new URLRequest("www.[my-domain].com"); var urlLoader: URLLoader = new URLLoader(); var urlVariables: URLVariables = new URLVariables("parameter

Re: FormItemView changes

El mar., 29 ene. 2019 a las 17:19, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > > I didn't say anywhere that I'm going to commit any of that group to > Framework. User should be responsible for creating such Group. - PAYG - I'm > showing how to do that in example. > > ok, cool. But I

Re: [royale-asjs] branch develop updated: Language: workaround that is closer to the original (references apache/royale-compiler#74)

I’m pretty sure I tried that and it did not work. Isn’t that the same as my first commit? > On Jan 29, 2019, at 7:14 PM, joshtynj...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > joshtynjala pushed a commit to branch develop > in repository https:

Re: [royale-asjs] branch develop updated: Language: workaround that is closer to the original (references apache/royale-compiler#74)

Ah. No. Different parens… > On Jan 29, 2019, at 7:23 PM, Harbs wrote: > > I’m pretty sure I tried that and it did not work. > > Isn’t that the same as my first commit? > >> On Jan 29, 2019, at 7:14 PM, joshtynj...@apache.org wrote: >> >> This is an automated email from the ASF dual-hosted git

Re: FormItemView changes

But you didn't merge my branch and in FormItemView where changes. How can I in develop change content layout without changing L and Required label ? wt., 29 sty 2019 o 18:23 Carlos Rovira napisał(a): > El mar., 29 ene. 2019 a las 17:19, Piotr Zarzycki (< > piotrzarzyck...@gmail.com>) escribió: >

Re: FormItemView changes

If you don't have solution and it looks like you won't have in FormItemView my changes - that's ok. I will create separate View with different name which will give user capability which I'm talking about. - Content only manipulation. Let me know if you are going to merge it. wt., 29 sty 2019 o 18

Re: FormItemView changes

Piotr, if you build current develop Jewel and TourDeJewel, you'll see that you can change content layout just setting the layout at formitem level: This is vertical content: This is horizontal content: That's what you want right? (not L and * involved here, since that will

Build failed in Jenkins: royale-asjs_MXTests #418

See Changes: [joshtynjala] Language: workaround that is closer to the original (references [carlosrovira] TourDeJewel: removing artificial VGroup and HGroup in FormExample since [

Jenkins build is back to normal : royale-asjs_MXTests #419

See

Re: FormItemView changes

Carlos, No it's not doing what I need. Let's stay with your design if you really need it. I did my changes in order to give myself possibilities to create StackedFormView and discover all of that problems on the road. Current design simply doesn't allow implement StackedFormView. Maybe when you st

Re: [royale-asjs] branch develop updated: Jewel Group: Fix dynamic adding Horizontal/Vertical layout

I will revert that tomorrow, cause I need to apply above changes or whatever other solution to my application first and seems that above code do not break anything. Thanks, Piotr wt., 29 sty 2019 o 11:41 Carlos Rovira napisał(a): > Ok Piotr, > thanks > > El lun., 28 ene. 2019 a las 21:17, Piotr