Re: FormItemView changes

2019-01-30 Thread Piotr Zarzycki
Good Luck! śr., 30 sty 2019 o 11:10 Carlos Rovira napisał(a): > Ok Piotr, > > thanks will do. Hope to get soon to the finish of our project to have more > time for this issues :) > > El mié., 30 ene. 2019 a las 11:08, Piotr Zarzycki (< > piotrzarzyck...@gmail.com>) escribió: > > > Carlos, > > >

Re: FormItemView changes

2019-01-30 Thread Carlos Rovira
Ok Piotr, thanks will do. Hope to get soon to the finish of our project to have more time for this issues :) El mié., 30 ene. 2019 a las 11:08, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Carlos, > > I'm not in a hurry here. You don't have to respond immediately ;) I'm good > cause

Re: FormItemView changes

2019-01-30 Thread Piotr Zarzycki
Carlos, I'm not in a hurry here. You don't have to respond immediately ;) I'm good cause my FormItemView and StackedFormItemView are working fine, so look into that if you want in the future. Thanks for your thoughts, Piotr śr., 30 sty 2019 o 11:03 Carlos Rovira napisał(a): > Hi Piotr, > > I'm

Re: FormItemView changes

2019-01-30 Thread Carlos Rovira
Hi Piotr, I'm facing a complicated situation now, since we need to finish our App in following days, and we're running out of time, and today we have a problem with latest change in compiler about Number to int conversion for AMF dates. So sorry, but can invest time on this for now. Just to be ab

Re: FormItemView changes

2019-01-29 Thread Piotr Zarzycki
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: FormItemView changes

2019-01-29 Thread Carlos Rovira
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

Re: FormItemView changes

2019-01-29 Thread Piotr Zarzycki
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

2019-01-29 Thread Piotr Zarzycki
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

2019-01-29 Thread Carlos Rovira
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: FormItemView changes

2019-01-29 Thread Piotr Zarzycki
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

Re: FormItemView changes

2019-01-29 Thread Piotr Zarzycki
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

2019-01-29 Thread Carlos Rovira
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

2019-01-29 Thread Carlos Rovira
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

2019-01-29 Thread Piotr Zarzycki
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

2019-01-29 Thread Piotr Zarzycki
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

2019-01-29 Thread Carlos Rovira
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

2019-01-29 Thread Piotr Zarzycki
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: FormItemView changes

2019-01-29 Thread Piotr Zarzycki
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

2019-01-29 Thread Carlos Rovira
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: FormItemView changes

2019-01-29 Thread Piotr Zarzycki
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

Re: FormItemView changes

2019-01-29 Thread Carlos Rovira
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