You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@royale.apache.org by Piotr Zarzycki <pi...@gmail.com> on 2019/01/23 14:46:07 UTC

Vertical FormItem

Hi Carlos,

I'm was trying to change FormItem to be Vertical oriented. In general I
would like to have following view. Label of FormItem is on the top and in
the bottom is content.

[image: image.png]

Code for that will looks like that [1]. Results is following:

[image: image.png]

It happened cause Label and required star label are different components -
everything is being laying out vertically. What is your suggestion to fix
that ?

Mine is wrapping "First name" and "*" into one Group with HorizontalLayout.

More thoughts are welcome. I hope you see screenshots. :)

[1] https://paste.apache.org/5odt

Thanks,
-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

Let's leave it for now implementation part and get back for a moment where
require indicator should be placed. I see one scenario where it will looks
pretty weird when you have:

L
C *

Scenario is where I have form which has in one line two Form items. Example
[1] It will looks like that in your idea:

L     L
C *  C *

Do you think that in this case require indicator is better here:

L*  L*
C   C

Thoughts ?

[1] https://imgur.com/H5EmZrs

Thanks, Piotr


czw., 24 sty 2019 o 17:57 Carlos Rovira <ca...@apache.org>
napisał(a):

> El jue., 24 ene. 2019 a las 17:38, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > In case of your implementation proposition - I'm not going to touch at
> all
> > any layout part stuff, cause there is an issue there - I have described
> it
> > in the earlier emails.
> >
>
> Right, but we must solve it to get something more final, maybe it can be
> delayed for now
> But you'll need in that case change layout to vertical and change view to
> the new one ("Stacked")
>
>
> >
> > It seems to me that you are agree with me on having separate View which
> > handles case above.
>
>
> yes
>
>
> > In terms of handling that case - in whatever direction
> > we will go
> >
> > L          L*
> > C* OR C
> >
>
> better first, for what I said in previous response
>
>
> >
> > Do you think that we should have additional container for L or C which
> > where ?
> >
> > <Group> - Horizotnal layout
> >    L * OR C *
> > </Group>
> >
>
> No. This:
> IFormItemContentArea: ClassReference("org.apache.royale.jewel.Group")
>
> is ok since we change layout of elements through IFormItemLayout
>
> so this:
>
> IFormItemLayout: ClassReference(
> "org.apache.royale.jewel.beads.layouts.VerticalLayout")
>
> should remain as is to layout contents vertically (by default)
>
>
> > If you have other idea let me know.
> >
> > Thanks,
> > Piotr
> >
> >
> > On Thu, Jan 24, 2019, 5:30 PM Piotr Zarzycki <pi...@gmail.com>
> > wrote:
> >
> > > Carlos,
> > >
> > > Why you are proposing have that?
> > >
> > > L
> > > C *
> > >
> > > I'm in favor of staying
> > >
> > > L *
> > > C
> > >
> > > Thanks,
> > > Piotr
> > >
> > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <ca...@apache.org>
> > > wrote:
> > >
> > >> I forgot to mention about IBeadLayout more, since it could be
> > >> misinterpreted:
> > >>
> > >> IBeadLayout for the global component is important, but what I'm
> > >> considering
> > >> is that although we can put HorizontalLayout (for the current
> FormtItem)
> > >> and VerticalLayout (for the stacked), I'm seeing that many components
> > >> would
> > >> need its own layout class. In this case we could create a
> > FormItemLayout,
> > >> and this will handle the layout vía CSS as it happens mostly in many
> > other
> > >> Jewel component.
> > >>
> > >> (Just say that some of them are using an standard layout class, like
> > >> HorizontalLayout, or even a NullLayout class), since I didn't have the
> > >> time
> > >> to create its own one, and that's temporal. But my plan is to create a
> > >> concrete layout for some of this components. FormItem could be one of
> > >> those
> > >> cases, for what we're seeing
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
> > >> carlosrovira@apache.org>)
> > >> escribió:
> > >>
> > >> > Hi Piotr,
> > >> >
> > >> > looking at the screen shot, seems the required indicator is
> positioned
> > >> to
> > >> > the right side of the element, what seems coherent, although could
> be
> > a
> > >> bit
> > >> > problematic depending on the width of the component. we assume a
> fixed
> > >> > width (to the widest element) and align all required (or not a put
> the
> > >> > required indicator just before the element, anyway this seems
> > something
> > >> to
> > >> > be solved as we have some real implementation.
> > >> >
> > >> > In order to implement it:
> > >> >
> > >> > We have 3 parts:
> > >> > - L (this is the label)
> > >> > - * (this is the required indicator)
> > >> > - C (this is the element(s) that the user adds)
> > >> >
> > >> > * Actual FormItem is :
> > >> >
> > >> > L * C
> > >> >
> > >> > * We want for the new
> > >> >
> > >> > L
> > >> > C *
> > >> >
> > >> > So it seems to me that
> > >> >
> > >> > a) IBeadLayout: ClassReference(
> > >> > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> > >> > Does not has much sense to me
> > >> >
> > >> > b) IFormItemLayout: ClassReference(
> > >> > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> > >> >
> > >> > This is the one important to me (to configure), so user can change
> > >> layout
> > >> > of the content part
> > >> >
> > >> > c) IBeadView: ClassReference(
> > >> > "org.apache.royale.jewel.beads.views.FormItemView")
> > >> > IFormItemContentArea:
> ClassReference("org.apache.royale.jewel.Group")
> > >> >
> > >> > These are the parts important to me.
> > >> >
> > >> > I think we really want to change only the IBeadView, so we can have
> a
> > >> > FormItemView and a StackedFormItemView, and could change it vía
> > >> className
> > >> > (for example)
> > >> >
> > >> > Let me know your thought about it
> > >> >
> > >> > thanks
> > >> >
> > >> > Carlos
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> > >> > piotrzarzycki21@gmail.com>) escribió:
> > >> >
> > >> >> Carlos,
> > >> >>
> > >> >> I have analyzed FormItem in Flex and here is how it is done there.
> > >> >> StackedFormItemSkin is using FormItemLayout which is constrained
> > into 3
> > >> >> columns (sequenceCol, contentCol and helpCol) and 2 rows. [1][2]
> > >> >>
> > >> >> When you look into the screenshot [2] you may think that reuired
> > >> indicator
> > >> >> is part of the content, but it's not. It's not even part of the
> > layout
> > >> >> cause it has includeInLayout="false". [3]
> > >> >> In Royale we don't have concept that something doesn't belong to
> > layout
> > >> >> and
> > >> >> is not calculated and indicator default is being placed in
> different
> > >> area.
> > >> >> Do you have some idea apart what I have proposed how to resolve
> that
> > ?
> > >> >>
> > >> >> [1] https://paste.apache.org/9Imj
> > >> >> [2] https://imgur.com/GGOtzEU
> > >> >> [3] https://paste.apache.org/kqlP
> > >> >>
> > >> >> Thanks,
> > >> >> Piotr
> > >> >>
> > >> >>
> > >> >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <piotrzarzycki21@gmail.com
> >
> > >> >> napisał(a):
> > >> >>
> > >> >> > That's more clear to me. I will check and get back to you.
> > >> >> >
> > >> >> > Thank you!
> > >> >> >
> > >> >> >
> > >> >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <ca...@apache.org>
> > >> >> > napisał(a):
> > >> >> >
> > >> >> >> No,
> > >> >> >>
> > >> >> >> I was asking you about how flex solves visualy the problem in
> > their
> > >> >> >> stacked
> > >> >> >> version. The required icon is setup next to the label? is in
> other
> > >> >> place?
> > >> >> >> if we had an image of how it is designed (and like it), we can
> > copy
> > >> >> it. I
> > >> >> >> still not proposing a technical solution. Just that I don't have
> > >> clear
> > >> >> how
> > >> >> >> we should layout it
> > >> >> >>
> > >> >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
> > >> >> >> piotrzarzycki21@gmail.com>) escribió:
> > >> >> >>
> > >> >> >> > Carlos,
> > >> >> >> >
> > >> >> >> > Your suggestion is to have new form item (StackedFormItem)
> with
> > >> new
> > >> >> >> > StackedFormItemView - cause problem is inside FormitemView,
> not
> > >> >> inside
> > >> >> >> > layout itself. Current layout is doing what it should do -
> apart
> > >> of
> > >> >> the
> > >> >> >> > problem - it's making children to be Horizontal/Vertical.
> > >> >> >> >
> > >> >> >> > If I'm correct what you are saying - that's ok, but if you
> have
> > >> had
> > >> >> >> > different idea by saying above let me know.
> > >> >> >> >
> > >> >> >> > Thanks, Piotr
> > >> >> >> >
> > >> >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
> carlosrovira@apache.org
> > >
> > >> >> >> > napisał(a):
> > >> >> >> >
> > >> >> >> > > Ok, I understand now.
> > >> >> >> > >
> > >> >> >> > > In Flex I think we had that layout and was
> > >> >> called....StackedFormItem
> > >> >> >> or
> > >> >> >> > > something like that?
> > >> >> >> > > Could you check how Flex solve this? If we continue liking
> the
> > >> way
> > >> >> >> > stacked
> > >> >> >> > > form layout in flex looks, we can do the same for our Royale
> > >> >> version
> > >> >> >> > >
> > >> >> >> > >
> > >> >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
> > >> >> >> > > piotrzarzycki21@gmail.com>) escribió:
> > >> >> >> > >
> > >> >> >> > > > I'm not sure how Serkan is doing that on users forum, but
> I
> > >> see
> > >> >> all
> > >> >> >> > hist
> > >> >> >> > > > pasted images. Anyway here you go:
> > >> >> >> > > >
> > >> >> >> > > > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
> > >> >> >> > > > What I got from Jewel FormItem:
> https://snag.gy/Slfbt9.jpg
> > >> >> >> > > >
> > >> >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
> > >> carlosrovira@apache.org>
> > >> >> >> > > > napisał(a):
> > >> >> >> > > >
> > >> >> >> > > > > Piotr,
> > >> >> >> > > > >
> > >> >> >> > > > > remember that images pasted in list are not shared, you
> > must
> > >> >> share
> > >> >> >> > with
> > >> >> >> > > > > some image service
> > >> >> >> > > > >
> > >> >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
> > >> >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> > >> >> >> > > > >
> > >> >> >> > > > > > There is one more problem with Layout. Currently
> default
> > >> in
> > >> >> >> > framework
> > >> >> >> > > > we
> > >> >> >> > > > > > have [1]. It means that:
> > >> >> >> > > > > >
> > >> >> >> > > > > > My content of FormItem will be vertical and
> IBeadLayout
> > is
> > >> >> >> > basically
> > >> >> >> > > > > > ignored at some point. If I specify beads -
> > >> HorizontalLayout
> > >> >> as
> > >> >> >> it
> > >> >> >> > is
> > >> >> >> > > > in
> > >> >> >> > > > > > above example it will be taken as a primary and I have
> > my
> > >> >> >> content
> > >> >> >> > > > laying
> > >> >> >> > > > > > out horizontally. The question is - what is for
> > >> >> >> IFormItemLayout in
> > >> >> >> > > > > > default.css? Is it a bug?
> > >> >> >> > > > > >
> > >> >> >> > > > > > [1] https://paste.apache.org/rV0K
> > >> >> >> > > > > >
> > >> >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> > >> >> >> piotrzarzycki21@gmail.com
> > >> >> >> > >
> > >> >> >> > > > > > napisał(a):
> > >> >> >> > > > > >
> > >> >> >> > > > > >> Hi Carlos,
> > >> >> >> > > > > >>
> > >> >> >> > > > > >> I'm was trying to change FormItem to be Vertical
> > >> oriented.
> > >> >> In
> > >> >> >> > > general
> > >> >> >> > > > I
> > >> >> >> > > > > >> would like to have following view. Label of FormItem
> is
> > >> on
> > >> >> the
> > >> >> >> top
> > >> >> >> > > and
> > >> >> >> > > > > in
> > >> >> >> > > > > >> the bottom is content.
> > >> >> >> > > > > >>
> > >> >> >> > > > > >> [image: image.png]
> > >> >> >> > > > > >>
> > >> >> >> > > > > >> Code for that will looks like that [1]. Results is
> > >> >> following:
> > >> >> >> > > > > >>
> > >> >> >> > > > > >> [image: image.png]
> > >> >> >> > > > > >>
> > >> >> >> > > > > >> It happened cause Label and required star label are
> > >> >> different
> > >> >> >> > > > components
> > >> >> >> > > > > >> - everything is being laying out vertically. What is
> > your
> > >> >> >> > suggestion
> > >> >> >> > > > to
> > >> >> >> > > > > fix
> > >> >> >> > > > > >> that ?
> > >> >> >> > > > > >>
> > >> >> >> > > > > >> Mine is wrapping "First name" and "*" into one Group
> > with
> > >> >> >> > > > > >> HorizontalLayout.
> > >> >> >> > > > > >>
> > >> >> >> > > > > >> More thoughts are welcome. I hope you see
> screenshots.
> > :)
> > >> >> >> > > > > >>
> > >> >> >> > > > > >> [1] https://paste.apache.org/5odt
> > >> >> >> > > > > >>
> > >> >> >> > > > > >> Thanks,
> > >> >> >> > > > > >> --
> > >> >> >> > > > > >>
> > >> >> >> > > > > >> Piotr Zarzycki
> > >> >> >> > > > > >>
> > >> >> >> > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > >> >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > >> >> >> > > > > >>
> > >> >> >> > > > > >
> > >> >> >> > > > > >
> > >> >> >> > > > > > --
> > >> >> >> > > > > >
> > >> >> >> > > > > > Piotr Zarzycki
> > >> >> >> > > > > >
> > >> >> >> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > >> >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > >> >> >> > > > > >
> > >> >> >> > > > >
> > >> >> >> > > > >
> > >> >> >> > > > > --
> > >> >> >> > > > > Carlos Rovira
> > >> >> >> > > > > http://about.me/carlosrovira
> > >> >> >> > > > >
> > >> >> >> > > >
> > >> >> >> > > >
> > >> >> >> > > > --
> > >> >> >> > > >
> > >> >> >> > > > Piotr Zarzycki
> > >> >> >> > > >
> > >> >> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > >> >> >> > > > <https://www.patreon.com/piotrzarzycki>*
> > >> >> >> > > >
> > >> >> >> > >
> > >> >> >> > >
> > >> >> >> > > --
> > >> >> >> > > Carlos Rovira
> > >> >> >> > > http://about.me/carlosrovira
> > >> >> >> > >
> > >> >> >> >
> > >> >> >> >
> > >> >> >> > --
> > >> >> >> >
> > >> >> >> > Piotr Zarzycki
> > >> >> >> >
> > >> >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > >> >> >> > <https://www.patreon.com/piotrzarzycki>*
> > >> >> >> >
> > >> >> >>
> > >> >> >>
> > >> >> >> --
> > >> >> >> Carlos Rovira
> > >> >> >> http://about.me/carlosrovira
> > >> >> >>
> > >> >> >
> > >> >> >
> > >> >> > --
> > >> >> >
> > >> >> > Piotr Zarzycki
> > >> >> >
> > >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > >> >> > <https://www.patreon.com/piotrzarzycki>*
> > >> >> >
> > >> >>
> > >> >>
> > >> >> --
> > >> >>
> > >> >> Piotr Zarzycki
> > >> >>
> > >> >> Patreon: *https://www.patreon.com/piotrzarzycki
> > >> >> <https://www.patreon.com/piotrzarzycki>*
> > >> >>
> > >> >
> > >> >
> > >> > --
> > >> > Carlos Rovira
> > >> > http://about.me/carlosrovira
> > >> >
> > >> >
> > >>
> > >> --
> > >> Carlos Rovira
> > >> http://about.me/carlosrovira
> > >>
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Carlos Rovira <ca...@apache.org>.

El jue., 24 ene. 2019 a las 17:38, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> In case of your implementation proposition - I'm not going to touch at all
> any layout part stuff, cause there is an issue there - I have described it
> in the earlier emails.
>

Right, but we must solve it to get something more final, maybe it can be
delayed for now
But you'll need in that case change layout to vertical and change view to
the new one ("Stacked")


>
> It seems to me that you are agree with me on having separate View which
> handles case above.


yes


> In terms of handling that case - in whatever direction
> we will go
>
> L          L*
> C* OR C
>

better first, for what I said in previous response


>
> Do you think that we should have additional container for L or C which
> where ?
>
> <Group> - Horizotnal layout
>    L * OR C *
> </Group>
>

No. This:
IFormItemContentArea: ClassReference("org.apache.royale.jewel.Group")

is ok since we change layout of elements through IFormItemLayout

so this:

IFormItemLayout: ClassReference(
"org.apache.royale.jewel.beads.layouts.VerticalLayout")

should remain as is to layout contents vertically (by default)


> If you have other idea let me know.
>
> Thanks,
> Piotr
>
>
> On Thu, Jan 24, 2019, 5:30 PM Piotr Zarzycki <pi...@gmail.com>
> wrote:
>
> > Carlos,
> >
> > Why you are proposing have that?
> >
> > L
> > C *
> >
> > I'm in favor of staying
> >
> > L *
> > C
> >
> > Thanks,
> > Piotr
> >
> > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <ca...@apache.org>
> > wrote:
> >
> >> I forgot to mention about IBeadLayout more, since it could be
> >> misinterpreted:
> >>
> >> IBeadLayout for the global component is important, but what I'm
> >> considering
> >> is that although we can put HorizontalLayout (for the current FormtItem)
> >> and VerticalLayout (for the stacked), I'm seeing that many components
> >> would
> >> need its own layout class. In this case we could create a
> FormItemLayout,
> >> and this will handle the layout vía CSS as it happens mostly in many
> other
> >> Jewel component.
> >>
> >> (Just say that some of them are using an standard layout class, like
> >> HorizontalLayout, or even a NullLayout class), since I didn't have the
> >> time
> >> to create its own one, and that's temporal. But my plan is to create a
> >> concrete layout for some of this components. FormItem could be one of
> >> those
> >> cases, for what we're seeing
> >>
> >>
> >>
> >>
> >>
> >> El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
> >> carlosrovira@apache.org>)
> >> escribió:
> >>
> >> > Hi Piotr,
> >> >
> >> > looking at the screen shot, seems the required indicator is positioned
> >> to
> >> > the right side of the element, what seems coherent, although could be
> a
> >> bit
> >> > problematic depending on the width of the component. we assume a fixed
> >> > width (to the widest element) and align all required (or not a put the
> >> > required indicator just before the element, anyway this seems
> something
> >> to
> >> > be solved as we have some real implementation.
> >> >
> >> > In order to implement it:
> >> >
> >> > We have 3 parts:
> >> > - L (this is the label)
> >> > - * (this is the required indicator)
> >> > - C (this is the element(s) that the user adds)
> >> >
> >> > * Actual FormItem is :
> >> >
> >> > L * C
> >> >
> >> > * We want for the new
> >> >
> >> > L
> >> > C *
> >> >
> >> > So it seems to me that
> >> >
> >> > a) IBeadLayout: ClassReference(
> >> > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> >> > Does not has much sense to me
> >> >
> >> > b) IFormItemLayout: ClassReference(
> >> > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> >> >
> >> > This is the one important to me (to configure), so user can change
> >> layout
> >> > of the content part
> >> >
> >> > c) IBeadView: ClassReference(
> >> > "org.apache.royale.jewel.beads.views.FormItemView")
> >> > IFormItemContentArea: ClassReference("org.apache.royale.jewel.Group")
> >> >
> >> > These are the parts important to me.
> >> >
> >> > I think we really want to change only the IBeadView, so we can have a
> >> > FormItemView and a StackedFormItemView, and could change it vía
> >> className
> >> > (for example)
> >> >
> >> > Let me know your thought about it
> >> >
> >> > thanks
> >> >
> >> > Carlos
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> >> > piotrzarzycki21@gmail.com>) escribió:
> >> >
> >> >> Carlos,
> >> >>
> >> >> I have analyzed FormItem in Flex and here is how it is done there.
> >> >> StackedFormItemSkin is using FormItemLayout which is constrained
> into 3
> >> >> columns (sequenceCol, contentCol and helpCol) and 2 rows. [1][2]
> >> >>
> >> >> When you look into the screenshot [2] you may think that reuired
> >> indicator
> >> >> is part of the content, but it's not. It's not even part of the
> layout
> >> >> cause it has includeInLayout="false". [3]
> >> >> In Royale we don't have concept that something doesn't belong to
> layout
> >> >> and
> >> >> is not calculated and indicator default is being placed in different
> >> area.
> >> >> Do you have some idea apart what I have proposed how to resolve that
> ?
> >> >>
> >> >> [1] https://paste.apache.org/9Imj
> >> >> [2] https://imgur.com/GGOtzEU
> >> >> [3] https://paste.apache.org/kqlP
> >> >>
> >> >> Thanks,
> >> >> Piotr
> >> >>
> >> >>
> >> >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <pi...@gmail.com>
> >> >> napisał(a):
> >> >>
> >> >> > That's more clear to me. I will check and get back to you.
> >> >> >
> >> >> > Thank you!
> >> >> >
> >> >> >
> >> >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <ca...@apache.org>
> >> >> > napisał(a):
> >> >> >
> >> >> >> No,
> >> >> >>
> >> >> >> I was asking you about how flex solves visualy the problem in
> their
> >> >> >> stacked
> >> >> >> version. The required icon is setup next to the label? is in other
> >> >> place?
> >> >> >> if we had an image of how it is designed (and like it), we can
> copy
> >> >> it. I
> >> >> >> still not proposing a technical solution. Just that I don't have
> >> clear
> >> >> how
> >> >> >> we should layout it
> >> >> >>
> >> >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
> >> >> >> piotrzarzycki21@gmail.com>) escribió:
> >> >> >>
> >> >> >> > Carlos,
> >> >> >> >
> >> >> >> > Your suggestion is to have new form item (StackedFormItem) with
> >> new
> >> >> >> > StackedFormItemView - cause problem is inside FormitemView, not
> >> >> inside
> >> >> >> > layout itself. Current layout is doing what it should do - apart
> >> of
> >> >> the
> >> >> >> > problem - it's making children to be Horizontal/Vertical.
> >> >> >> >
> >> >> >> > If I'm correct what you are saying - that's ok, but if you have
> >> had
> >> >> >> > different idea by saying above let me know.
> >> >> >> >
> >> >> >> > Thanks, Piotr
> >> >> >> >
> >> >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <carlosrovira@apache.org
> >
> >> >> >> > napisał(a):
> >> >> >> >
> >> >> >> > > Ok, I understand now.
> >> >> >> > >
> >> >> >> > > In Flex I think we had that layout and was
> >> >> called....StackedFormItem
> >> >> >> or
> >> >> >> > > something like that?
> >> >> >> > > Could you check how Flex solve this? If we continue liking the
> >> way
> >> >> >> > stacked
> >> >> >> > > form layout in flex looks, we can do the same for our Royale
> >> >> version
> >> >> >> > >
> >> >> >> > >
> >> >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
> >> >> >> > > piotrzarzycki21@gmail.com>) escribió:
> >> >> >> > >
> >> >> >> > > > I'm not sure how Serkan is doing that on users forum, but I
> >> see
> >> >> all
> >> >> >> > hist
> >> >> >> > > > pasted images. Anyway here you go:
> >> >> >> > > >
> >> >> >> > > > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
> >> >> >> > > > What I got from Jewel FormItem: https://snag.gy/Slfbt9.jpg
> >> >> >> > > >
> >> >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
> >> carlosrovira@apache.org>
> >> >> >> > > > napisał(a):
> >> >> >> > > >
> >> >> >> > > > > Piotr,
> >> >> >> > > > >
> >> >> >> > > > > remember that images pasted in list are not shared, you
> must
> >> >> share
> >> >> >> > with
> >> >> >> > > > > some image service
> >> >> >> > > > >
> >> >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
> >> >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> >> >> >> > > > >
> >> >> >> > > > > > There is one more problem with Layout. Currently default
> >> in
> >> >> >> > framework
> >> >> >> > > > we
> >> >> >> > > > > > have [1]. It means that:
> >> >> >> > > > > >
> >> >> >> > > > > > My content of FormItem will be vertical and IBeadLayout
> is
> >> >> >> > basically
> >> >> >> > > > > > ignored at some point. If I specify beads -
> >> HorizontalLayout
> >> >> as
> >> >> >> it
> >> >> >> > is
> >> >> >> > > > in
> >> >> >> > > > > > above example it will be taken as a primary and I have
> my
> >> >> >> content
> >> >> >> > > > laying
> >> >> >> > > > > > out horizontally. The question is - what is for
> >> >> >> IFormItemLayout in
> >> >> >> > > > > > default.css? Is it a bug?
> >> >> >> > > > > >
> >> >> >> > > > > > [1] https://paste.apache.org/rV0K
> >> >> >> > > > > >
> >> >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> >> >> >> piotrzarzycki21@gmail.com
> >> >> >> > >
> >> >> >> > > > > > napisał(a):
> >> >> >> > > > > >
> >> >> >> > > > > >> Hi Carlos,
> >> >> >> > > > > >>
> >> >> >> > > > > >> I'm was trying to change FormItem to be Vertical
> >> oriented.
> >> >> In
> >> >> >> > > general
> >> >> >> > > > I
> >> >> >> > > > > >> would like to have following view. Label of FormItem is
> >> on
> >> >> the
> >> >> >> top
> >> >> >> > > and
> >> >> >> > > > > in
> >> >> >> > > > > >> the bottom is content.
> >> >> >> > > > > >>
> >> >> >> > > > > >> [image: image.png]
> >> >> >> > > > > >>
> >> >> >> > > > > >> Code for that will looks like that [1]. Results is
> >> >> following:
> >> >> >> > > > > >>
> >> >> >> > > > > >> [image: image.png]
> >> >> >> > > > > >>
> >> >> >> > > > > >> It happened cause Label and required star label are
> >> >> different
> >> >> >> > > > components
> >> >> >> > > > > >> - everything is being laying out vertically. What is
> your
> >> >> >> > suggestion
> >> >> >> > > > to
> >> >> >> > > > > fix
> >> >> >> > > > > >> that ?
> >> >> >> > > > > >>
> >> >> >> > > > > >> Mine is wrapping "First name" and "*" into one Group
> with
> >> >> >> > > > > >> HorizontalLayout.
> >> >> >> > > > > >>
> >> >> >> > > > > >> More thoughts are welcome. I hope you see screenshots.
> :)
> >> >> >> > > > > >>
> >> >> >> > > > > >> [1] https://paste.apache.org/5odt
> >> >> >> > > > > >>
> >> >> >> > > > > >> Thanks,
> >> >> >> > > > > >> --
> >> >> >> > > > > >>
> >> >> >> > > > > >> Piotr Zarzycki
> >> >> >> > > > > >>
> >> >> >> > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> >> >> >> > > > > >>
> >> >> >> > > > > >
> >> >> >> > > > > >
> >> >> >> > > > > > --
> >> >> >> > > > > >
> >> >> >> > > > > > Piotr Zarzycki
> >> >> >> > > > > >
> >> >> >> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> >> >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
> >> >> >> > > > > >
> >> >> >> > > > >
> >> >> >> > > > >
> >> >> >> > > > > --
> >> >> >> > > > > Carlos Rovira
> >> >> >> > > > > http://about.me/carlosrovira
> >> >> >> > > > >
> >> >> >> > > >
> >> >> >> > > >
> >> >> >> > > > --
> >> >> >> > > >
> >> >> >> > > > Piotr Zarzycki
> >> >> >> > > >
> >> >> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> >> >> >> > > > <https://www.patreon.com/piotrzarzycki>*
> >> >> >> > > >
> >> >> >> > >
> >> >> >> > >
> >> >> >> > > --
> >> >> >> > > Carlos Rovira
> >> >> >> > > http://about.me/carlosrovira
> >> >> >> > >
> >> >> >> >
> >> >> >> >
> >> >> >> > --
> >> >> >> >
> >> >> >> > Piotr Zarzycki
> >> >> >> >
> >> >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> >> >> >> > <https://www.patreon.com/piotrzarzycki>*
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Carlos Rovira
> >> >> >> http://about.me/carlosrovira
> >> >> >>
> >> >> >
> >> >> >
> >> >> > --
> >> >> >
> >> >> > Piotr Zarzycki
> >> >> >
> >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> >> >> > <https://www.patreon.com/piotrzarzycki>*
> >> >> >
> >> >>
> >> >>
> >> >> --
> >> >>
> >> >> Piotr Zarzycki
> >> >>
> >> >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> >> <https://www.patreon.com/piotrzarzycki>*
> >> >>
> >> >
> >> >
> >> > --
> >> > Carlos Rovira
> >> > http://about.me/carlosrovira
> >> >
> >> >
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >
>


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

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

In case of your implementation proposition - I'm not going to touch at all
any layout part stuff, cause there is an issue there - I have described it
in the earlier emails.

It seems to me that you are agree with me on having separate View which
handles case above. In terms of handling that case - in whatever direction
we will go

L          L*
C* OR C

Do you think that we should have additional container for L or C which
where ?

<Group> - Horizotnal layout
   L * OR C *
</Group>

If you have other idea let me know.

Thanks,
Piotr


On Thu, Jan 24, 2019, 5:30 PM Piotr Zarzycki <pi...@gmail.com>
wrote:

> Carlos,
>
> Why you are proposing have that?
>
> L
> C *
>
> I'm in favor of staying
>
> L *
> C
>
> Thanks,
> Piotr
>
> On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <ca...@apache.org>
> wrote:
>
>> I forgot to mention about IBeadLayout more, since it could be
>> misinterpreted:
>>
>> IBeadLayout for the global component is important, but what I'm
>> considering
>> is that although we can put HorizontalLayout (for the current FormtItem)
>> and VerticalLayout (for the stacked), I'm seeing that many components
>> would
>> need its own layout class. In this case we could create a FormItemLayout,
>> and this will handle the layout vía CSS as it happens mostly in many other
>> Jewel component.
>>
>> (Just say that some of them are using an standard layout class, like
>> HorizontalLayout, or even a NullLayout class), since I didn't have the
>> time
>> to create its own one, and that's temporal. But my plan is to create a
>> concrete layout for some of this components. FormItem could be one of
>> those
>> cases, for what we're seeing
>>
>>
>>
>>
>>
>> El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
>> carlosrovira@apache.org>)
>> escribió:
>>
>> > Hi Piotr,
>> >
>> > looking at the screen shot, seems the required indicator is positioned
>> to
>> > the right side of the element, what seems coherent, although could be a
>> bit
>> > problematic depending on the width of the component. we assume a fixed
>> > width (to the widest element) and align all required (or not a put the
>> > required indicator just before the element, anyway this seems something
>> to
>> > be solved as we have some real implementation.
>> >
>> > In order to implement it:
>> >
>> > We have 3 parts:
>> > - L (this is the label)
>> > - * (this is the required indicator)
>> > - C (this is the element(s) that the user adds)
>> >
>> > * Actual FormItem is :
>> >
>> > L * C
>> >
>> > * We want for the new
>> >
>> > L
>> > C *
>> >
>> > So it seems to me that
>> >
>> > a) IBeadLayout: ClassReference(
>> > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
>> > Does not has much sense to me
>> >
>> > b) IFormItemLayout: ClassReference(
>> > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
>> >
>> > This is the one important to me (to configure), so user can change
>> layout
>> > of the content part
>> >
>> > c) IBeadView: ClassReference(
>> > "org.apache.royale.jewel.beads.views.FormItemView")
>> > IFormItemContentArea: ClassReference("org.apache.royale.jewel.Group")
>> >
>> > These are the parts important to me.
>> >
>> > I think we really want to change only the IBeadView, so we can have a
>> > FormItemView and a StackedFormItemView, and could change it vía
>> className
>> > (for example)
>> >
>> > Let me know your thought about it
>> >
>> > thanks
>> >
>> > Carlos
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
>> > piotrzarzycki21@gmail.com>) escribió:
>> >
>> >> Carlos,
>> >>
>> >> I have analyzed FormItem in Flex and here is how it is done there.
>> >> StackedFormItemSkin is using FormItemLayout which is constrained into 3
>> >> columns (sequenceCol, contentCol and helpCol) and 2 rows. [1][2]
>> >>
>> >> When you look into the screenshot [2] you may think that reuired
>> indicator
>> >> is part of the content, but it's not. It's not even part of the layout
>> >> cause it has includeInLayout="false". [3]
>> >> In Royale we don't have concept that something doesn't belong to layout
>> >> and
>> >> is not calculated and indicator default is being placed in different
>> area.
>> >> Do you have some idea apart what I have proposed how to resolve that ?
>> >>
>> >> [1] https://paste.apache.org/9Imj
>> >> [2] https://imgur.com/GGOtzEU
>> >> [3] https://paste.apache.org/kqlP
>> >>
>> >> Thanks,
>> >> Piotr
>> >>
>> >>
>> >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <pi...@gmail.com>
>> >> napisał(a):
>> >>
>> >> > That's more clear to me. I will check and get back to you.
>> >> >
>> >> > Thank you!
>> >> >
>> >> >
>> >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <ca...@apache.org>
>> >> > napisał(a):
>> >> >
>> >> >> No,
>> >> >>
>> >> >> I was asking you about how flex solves visualy the problem in their
>> >> >> stacked
>> >> >> version. The required icon is setup next to the label? is in other
>> >> place?
>> >> >> if we had an image of how it is designed (and like it), we can copy
>> >> it. I
>> >> >> still not proposing a technical solution. Just that I don't have
>> clear
>> >> how
>> >> >> we should layout it
>> >> >>
>> >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
>> >> >> piotrzarzycki21@gmail.com>) escribió:
>> >> >>
>> >> >> > Carlos,
>> >> >> >
>> >> >> > Your suggestion is to have new form item (StackedFormItem) with
>> new
>> >> >> > StackedFormItemView - cause problem is inside FormitemView, not
>> >> inside
>> >> >> > layout itself. Current layout is doing what it should do - apart
>> of
>> >> the
>> >> >> > problem - it's making children to be Horizontal/Vertical.
>> >> >> >
>> >> >> > If I'm correct what you are saying - that's ok, but if you have
>> had
>> >> >> > different idea by saying above let me know.
>> >> >> >
>> >> >> > Thanks, Piotr
>> >> >> >
>> >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <ca...@apache.org>
>> >> >> > napisał(a):
>> >> >> >
>> >> >> > > Ok, I understand now.
>> >> >> > >
>> >> >> > > In Flex I think we had that layout and was
>> >> called....StackedFormItem
>> >> >> or
>> >> >> > > something like that?
>> >> >> > > Could you check how Flex solve this? If we continue liking the
>> way
>> >> >> > stacked
>> >> >> > > form layout in flex looks, we can do the same for our Royale
>> >> version
>> >> >> > >
>> >> >> > >
>> >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
>> >> >> > > piotrzarzycki21@gmail.com>) escribió:
>> >> >> > >
>> >> >> > > > I'm not sure how Serkan is doing that on users forum, but I
>> see
>> >> all
>> >> >> > hist
>> >> >> > > > pasted images. Anyway here you go:
>> >> >> > > >
>> >> >> > > > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
>> >> >> > > > What I got from Jewel FormItem: https://snag.gy/Slfbt9.jpg
>> >> >> > > >
>> >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
>> carlosrovira@apache.org>
>> >> >> > > > napisał(a):
>> >> >> > > >
>> >> >> > > > > Piotr,
>> >> >> > > > >
>> >> >> > > > > remember that images pasted in list are not shared, you must
>> >> share
>> >> >> > with
>> >> >> > > > > some image service
>> >> >> > > > >
>> >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
>> >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
>> >> >> > > > >
>> >> >> > > > > > There is one more problem with Layout. Currently default
>> in
>> >> >> > framework
>> >> >> > > > we
>> >> >> > > > > > have [1]. It means that:
>> >> >> > > > > >
>> >> >> > > > > > My content of FormItem will be vertical and IBeadLayout is
>> >> >> > basically
>> >> >> > > > > > ignored at some point. If I specify beads -
>> HorizontalLayout
>> >> as
>> >> >> it
>> >> >> > is
>> >> >> > > > in
>> >> >> > > > > > above example it will be taken as a primary and I have my
>> >> >> content
>> >> >> > > > laying
>> >> >> > > > > > out horizontally. The question is - what is for
>> >> >> IFormItemLayout in
>> >> >> > > > > > default.css? Is it a bug?
>> >> >> > > > > >
>> >> >> > > > > > [1] https://paste.apache.org/rV0K
>> >> >> > > > > >
>> >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
>> >> >> piotrzarzycki21@gmail.com
>> >> >> > >
>> >> >> > > > > > napisał(a):
>> >> >> > > > > >
>> >> >> > > > > >> Hi Carlos,
>> >> >> > > > > >>
>> >> >> > > > > >> I'm was trying to change FormItem to be Vertical
>> oriented.
>> >> In
>> >> >> > > general
>> >> >> > > > I
>> >> >> > > > > >> would like to have following view. Label of FormItem is
>> on
>> >> the
>> >> >> top
>> >> >> > > and
>> >> >> > > > > in
>> >> >> > > > > >> the bottom is content.
>> >> >> > > > > >>
>> >> >> > > > > >> [image: image.png]
>> >> >> > > > > >>
>> >> >> > > > > >> Code for that will looks like that [1]. Results is
>> >> following:
>> >> >> > > > > >>
>> >> >> > > > > >> [image: image.png]
>> >> >> > > > > >>
>> >> >> > > > > >> It happened cause Label and required star label are
>> >> different
>> >> >> > > > components
>> >> >> > > > > >> - everything is being laying out vertically. What is your
>> >> >> > suggestion
>> >> >> > > > to
>> >> >> > > > > fix
>> >> >> > > > > >> that ?
>> >> >> > > > > >>
>> >> >> > > > > >> Mine is wrapping "First name" and "*" into one Group with
>> >> >> > > > > >> HorizontalLayout.
>> >> >> > > > > >>
>> >> >> > > > > >> More thoughts are welcome. I hope you see screenshots. :)
>> >> >> > > > > >>
>> >> >> > > > > >> [1] https://paste.apache.org/5odt
>> >> >> > > > > >>
>> >> >> > > > > >> Thanks,
>> >> >> > > > > >> --
>> >> >> > > > > >>
>> >> >> > > > > >> Piotr Zarzycki
>> >> >> > > > > >>
>> >> >> > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
>> >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
>> >> >> > > > > >>
>> >> >> > > > > >
>> >> >> > > > > >
>> >> >> > > > > > --
>> >> >> > > > > >
>> >> >> > > > > > Piotr Zarzycki
>> >> >> > > > > >
>> >> >> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
>> >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
>> >> >> > > > > >
>> >> >> > > > >
>> >> >> > > > >
>> >> >> > > > > --
>> >> >> > > > > Carlos Rovira
>> >> >> > > > > http://about.me/carlosrovira
>> >> >> > > > >
>> >> >> > > >
>> >> >> > > >
>> >> >> > > > --
>> >> >> > > >
>> >> >> > > > Piotr Zarzycki
>> >> >> > > >
>> >> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
>> >> >> > > > <https://www.patreon.com/piotrzarzycki>*
>> >> >> > > >
>> >> >> > >
>> >> >> > >
>> >> >> > > --
>> >> >> > > Carlos Rovira
>> >> >> > > http://about.me/carlosrovira
>> >> >> > >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> >
>> >> >> > Piotr Zarzycki
>> >> >> >
>> >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
>> >> >> > <https://www.patreon.com/piotrzarzycki>*
>> >> >> >
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Carlos Rovira
>> >> >> http://about.me/carlosrovira
>> >> >>
>> >> >
>> >> >
>> >> > --
>> >> >
>> >> > Piotr Zarzycki
>> >> >
>> >> > Patreon: *https://www.patreon.com/piotrzarzycki
>> >> > <https://www.patreon.com/piotrzarzycki>*
>> >> >
>> >>
>> >>
>> >> --
>> >>
>> >> Piotr Zarzycki
>> >>
>> >> Patreon: *https://www.patreon.com/piotrzarzycki
>> >> <https://www.patreon.com/piotrzarzycki>*
>> >>
>> >
>> >
>> > --
>> > Carlos Rovira
>> > http://about.me/carlosrovira
>> >
>> >
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>

Re: Vertical FormItem

Posted by Carlos Rovira <ca...@apache.org>.

You're right, the "transfer" thing come from Basic Panel, and I think that
code is not working even in Basic, but I didn't clean it.
So yours seems more clean.
If it works (example continue working as before) commit that and we see if
we found some eventual regression

thanks


El sáb., 26 ene. 2019 a las 14:00, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> In my opinion this part should looks like that:
> https://paste.apache.org/gbn2 - Simple initialization. If someone would
> like to use anything more than default (currently it's
> IFormItemContentArea:
> ClassReference("org.apache.royale.jewel.Group"); ) - He can use it - for
> example HGroup.
>
> What do you think ?
>
> sob., 26 sty 2019 o 12:58 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > Remember I'm talking above only about contentArea of FormItem.
> >
> > sob., 26 sty 2019 o 12:57 Piotr Zarzycki <pi...@gmail.com>
> > napisał(a):
> >
> >> Carlos,
> >>
> >> I think I got it. It looks like we don't need IFormItemLayout as you
> >> said, cause I should be able to manipulate content of my FormItem by
> doing
> >> that:
> >>
> >> IBeadLayout:
> >>
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> >> IFormItemContentArea: ClassReference("org.apache.royale.jewel.HGroup");
> >>
> >> However above code won't work cause you have this [1] -
> transferLayoutBead
> >> is being added to contentArea you have now in output code for content
> area
> >> something weird. [2]
> >>
> >> To me IBeadLayout - shouldn't be transfered to content - Are you agree ?
> >>
> >> [1] https://paste.apache.org/m9ST
> >> [2] https://paste.apache.org/9Orx
> >>
> >> Thanks,
> >> Piotr
> >>
> >>
> >> sob., 26 sty 2019 o 12:18 Carlos Rovira <ca...@apache.org>
> >> napisał(a):
> >>
> >>> Piotr, I think I don't think we need and IFormItemLayout.
> >>> IBeadLayout seems sufficient for me, since that layout will be based
> just
> >>> on css selectors that are in the end what solves the layout
> >>>
> >>> El sáb., 26 ene. 2019 a las 12:00, Piotr Zarzycki (<
> >>> piotrzarzycki21@gmail.com>) escribió:
> >>>
> >>> > Too bad that you didn't understand me. Just question to above
> >>> requirements
> >>> > - What in your opinion should do layout added trough ->
> >>> *IFormItemLayout
> >>> > ?*
> >>> >
> >>> > sob., 26 sty 2019 o 11:54 Carlos Rovira <ca...@apache.org>
> >>> > napisał(a):
> >>> >
> >>> > > Hi Piotr,
> >>> > >
> >>> > > Don't think if I understand right your exposition. I'll try to
> write
> >>> in
> >>> > > words what I expect from a FormItemLayout and let me know if we're
> >>> > thinking
> >>> > > on the same.
> >>> > >
> >>> > > We want to have a specialized layout for FormItem that support
> >>> horizontal
> >>> > > and stacked form item layouts. At this point we can choose to have
> 2
> >>> > > layouts or only 1.
> >>> > > Since we always have 2, maybe that's the best way to go :
> >>> > > HorizontalFormItemLayout and VerticalFormItemLayout.
> >>> > >
> >>> > > HorizontalFormItemLayout: should put label, required indicator and
> >>> > content
> >>> > > in the same "row", o mostly as HorizontalLayout does, and will be
> >>> equal
> >>> > to
> >>> > > what we have now.
> >>> > >
> >>> > > VerticalFormItemLayout should put Label followed by
> >>> requiredIndicator in
> >>> > a
> >>> > > row and just below, the content part. *Or* Label in a row and below
> >>> > Content
> >>> > > followed by requited Indicator
> >>> > > (I think this should be configurable in some way, or implement a
> >>> case and
> >>> > > made and additional layout for the other, so we can have both).
> >>> > >
> >>> > > Some technical needs:
> >>> > >
> >>> > > * All we'll be solved using CSS and css class selectors as with the
> >>> rest
> >>> > of
> >>> > > Jewel Layouts and phyloshopy
> >>> > > * We'll continue using flexbox since is the standard in Jewel
> >>> > > * We can use the flexbox order to have a property that puts content
> >>> > before
> >>> > > required indicator or viceversa using a property in the layout.
> >>> > > * I think FormItemView would need to adapt to this, and maybe will
> >>> need
> >>> > two
> >>> > > Views to support each layout (don't have clear now)
> >>> > >
> >>> > >
> >>> > >
> >>> > >
> >>> > > El vie., 25 ene. 2019 a las 16:23, Piotr Zarzycki (<
> >>> > > piotrzarzycki21@gmail.com>) escribió:
> >>> > >
> >>> > > > I won't follow Flex, so if you would like to do this I'm fine.
> I'm
> >>> > going
> >>> > > to
> >>> > > > implement my own View in my application. I won't commit it to
> >>> Royale.
> >>> > > > However I would like to fix issue with layout. Currently
> >>> IBeadLayout -
> >>> > Is
> >>> > > > making whole FormItem vertical or horizontal. *IFormItemLayout -
> >>> Should
> >>> > > > treat content appropriately, but it doesn't do anything. I would
> >>> like
> >>> > to
> >>> > > > change it in the following way:*
> >>> > > >
> >>> > > > *IBeadLayout do:*
> >>> > > >
> >>> > > > *1) When user: IBeadLayout:
> >>> > > >
> >>> >
> >>>
> ClassReference("org.apache.royale.jewel.beads.layouts.VerticalLayout");*
> >>> > > > L
> >>> > > > C
> >>> > > > *2) When user: **IBeadLayout:
> >>> > > >
> >>> > >
> >>> >
> >>>
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");*
> >>> > > > *L C*
> >>> > > >
> >>> > > > *IFormItemLayout will do:*
> >>> > > > 1) IFormItemLayout:
> >>> > > >
> >>> >
> >>>
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> >>> > > > and #1 - *IBeadLayout*
> >>> > > > L
> >>> > > > C - Set children Horizotnally
> >>> > > > 2) IFormItemLayout:
> >>> > > >
> >>> >
> >>>
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> >>> > > > and #2 - *IBeadLayout*
> >>> > > > *L*
> >>> > > > *C - Set children Vertically*
> >>> > > >
> >>> > > > *Thoughts ?*
> >>> > > >
> >>> > > > Piotr
> >>> > > >
> >>> > > >
> >>> > > >
> >>> > > > pt., 25 sty 2019 o 16:13 Carlos Rovira <ca...@apache.org>
> >>> > > > napisał(a):
> >>> > > >
> >>> > > > > Ops!,
> >>> > > > >
> >>> > > > > ok, since I was using the other layout I was in the believe
> that
> >>> was
> >>> > > the
> >>> > > > > standard. So if we want to follow flex, we can change the
> >>> current as
> >>> > > > well.
> >>> > > > >
> >>> > > > > El jue., 24 ene. 2019 a las 18:34, Piotr Zarzycki (<
> >>> > > > > piotrzarzycki21@gmail.com>) escribió:
> >>> > > > >
> >>> > > > > > Nope - I just checked [1] - Code [2] - You are showing me
> some
> >>> > custom
> >>> > > > > > implementation.
> >>> > > > > >
> >>> > > > > > [1] https://imgur.com/INKlfcC
> >>> > > > > > [2] https://paste.apache.org/jyrl
> >>> > > > > >
> >>> > > > > > czw., 24 sty 2019 o 18:20 Carlos Rovira <
> >>> carlosrovira@apache.org>
> >>> > > > > > napisał(a):
> >>> > > > > >
> >>> > > > > > > Piotr,
> >>> > > > > > >
> >>> > > > > > > in Flex we have the same align (as we have now in Royale),
> >>> check
> >>> > > this
> >>> > > > > > > image: url
> >>> > > > > > > <
> >>> > > > > > >
> >>> > > > > >
> >>> > > > >
> >>> > > >
> >>> > >
> >>> >
> >>>
> https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249
> >>> > > > > > > >
> >>> > > > > > >
> >>> > > > > > > El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
> >>> > > > > > > piotrzarzycki21@gmail.com>) escribió:
> >>> > > > > > >
> >>> > > > > > > > If we are going in that direction it requires as well
> work
> >>> were
> >>> > > > > > indicator
> >>> > > > > > > > in case of L* C (current implementation) will be changed
> >>> to L
> >>> > C*
> >>> > > -
> >>> > > > > Yes
> >>> > > > > > ?
> >>> > > > > > > -
> >>> > > > > > > > Being consistent it should be like that.
> >>> > > > > > > >
> >>> > > > > > > > I'm not sure what the trends are in that case.
> >>> > > > > > > >
> >>> > > > > > > > czw., 24 sty 2019 o 17:51 Carlos Rovira <
> >>> > carlosrovira@apache.org
> >>> > > >
> >>> > > > > > > > napisał(a):
> >>> > > > > > > >
> >>> > > > > > > > > Hi Piotr,
> >>> > > > > > > > >
> >>> > > > > > > > > since is what you show in the flex version.
> >>> > > > > > > > > I think Adobe put side to content instead of side to
> >>> label
> >>> > > since
> >>> > > > > the
> >>> > > > > > > user
> >>> > > > > > > > > fill the content elements and if not filled and
> required
> >>> ,
> >>> > the
> >>> > > > > > tooltip
> >>> > > > > > > > > should popup there.
> >>> > > > > > > > > IOW, for usability, seems more appropriated the way
> flex
> >>> > > > layedout,
> >>> > > > > or
> >>> > > > > > > > seems
> >>> > > > > > > > > more natural.
> >>> > > > > > > > >
> >>> > > > > > > > > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
> >>> > > > > > > > > piotrzarzycki21@gmail.com>) escribió:
> >>> > > > > > > > >
> >>> > > > > > > > > > Carlos,
> >>> > > > > > > > > >
> >>> > > > > > > > > > Why you are proposing have that?
> >>> > > > > > > > > >
> >>> > > > > > > > > > L
> >>> > > > > > > > > > C *
> >>> > > > > > > > > >
> >>> > > > > > > > > > I'm in favor of staying
> >>> > > > > > > > > >
> >>> > > > > > > > > > L *
> >>> > > > > > > > > > C
> >>> > > > > > > > > >
> >>> > > > > > > > > > Thanks,
> >>> > > > > > > > > > Piotr
> >>> > > > > > > > > >
> >>> > > > > > > > > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <
> >>> > > > > > carlosrovira@apache.org
> >>> > > > > > > >
> >>> > > > > > > > > > wrote:
> >>> > > > > > > > > >
> >>> > > > > > > > > > > I forgot to mention about IBeadLayout more, since
> it
> >>> > could
> >>> > > be
> >>> > > > > > > > > > > misinterpreted:
> >>> > > > > > > > > > >
> >>> > > > > > > > > > > IBeadLayout for the global component is important,
> >>> but
> >>> > what
> >>> > > > I'm
> >>> > > > > > > > > > considering
> >>> > > > > > > > > > > is that although we can put HorizontalLayout (for
> the
> >>> > > current
> >>> > > > > > > > > FormtItem)
> >>> > > > > > > > > > > and VerticalLayout (for the stacked), I'm seeing
> that
> >>> > many
> >>> > > > > > > components
> >>> > > > > > > > > > would
> >>> > > > > > > > > > > need its own layout class. In this case we could
> >>> create a
> >>> > > > > > > > > FormItemLayout,
> >>> > > > > > > > > > > and this will handle the layout vía CSS as it
> happens
> >>> > > mostly
> >>> > > > in
> >>> > > > > > > many
> >>> > > > > > > > > > other
> >>> > > > > > > > > > > Jewel component.
> >>> > > > > > > > > > >
> >>> > > > > > > > > > > (Just say that some of them are using an standard
> >>> layout
> >>> > > > class,
> >>> > > > > > > like
> >>> > > > > > > > > > > HorizontalLayout, or even a NullLayout class),
> since
> >>> I
> >>> > > didn't
> >>> > > > > > have
> >>> > > > > > > > the
> >>> > > > > > > > > > time
> >>> > > > > > > > > > > to create its own one, and that's temporal. But my
> >>> plan
> >>> > is
> >>> > > to
> >>> > > > > > > create
> >>> > > > > > > > a
> >>> > > > > > > > > > > concrete layout for some of this components.
> FormItem
> >>> > could
> >>> > > > be
> >>> > > > > > one
> >>> > > > > > > of
> >>> > > > > > > > > > those
> >>> > > > > > > > > > > cases, for what we're seeing
> >>> > > > > > > > > > >
> >>> > > > > > > > > > >
> >>> > > > > > > > > > >
> >>> > > > > > > > > > >
> >>> > > > > > > > > > >
> >>> > > > > > > > > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
> >>> > > > > > > > > > carlosrovira@apache.org
> >>> > > > > > > > > > > >)
> >>> > > > > > > > > > > escribió:
> >>> > > > > > > > > > >
> >>> > > > > > > > > > > > Hi Piotr,
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > looking at the screen shot, seems the required
> >>> > indicator
> >>> > > is
> >>> > > > > > > > > positioned
> >>> > > > > > > > > > to
> >>> > > > > > > > > > > > the right side of the element, what seems
> coherent,
> >>> > > > although
> >>> > > > > > > could
> >>> > > > > > > > > be a
> >>> > > > > > > > > > > bit
> >>> > > > > > > > > > > > problematic depending on the width of the
> >>> component. we
> >>> > > > > assume
> >>> > > > > > a
> >>> > > > > > > > > fixed
> >>> > > > > > > > > > > > width (to the widest element) and align all
> >>> required
> >>> > (or
> >>> > > > not
> >>> > > > > a
> >>> > > > > > > put
> >>> > > > > > > > > the
> >>> > > > > > > > > > > > required indicator just before the element,
> anyway
> >>> this
> >>> > > > seems
> >>> > > > > > > > > something
> >>> > > > > > > > > > > to
> >>> > > > > > > > > > > > be solved as we have some real implementation.
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > In order to implement it:
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > We have 3 parts:
> >>> > > > > > > > > > > > - L (this is the label)
> >>> > > > > > > > > > > > - * (this is the required indicator)
> >>> > > > > > > > > > > > - C (this is the element(s) that the user adds)
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > * Actual FormItem is :
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > L * C
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > * We want for the new
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > L
> >>> > > > > > > > > > > > C *
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > So it seems to me that
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > a) IBeadLayout: ClassReference(
> >>> > > > > > > > > > > >
> >>> > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> >>> > > > > > > > > > > > Does not has much sense to me
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > b) IFormItemLayout: ClassReference(
> >>> > > > > > > > > > > >
> >>> "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > This is the one important to me (to configure),
> so
> >>> user
> >>> > > can
> >>> > > > > > > change
> >>> > > > > > > > > > layout
> >>> > > > > > > > > > > > of the content part
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > c) IBeadView: ClassReference(
> >>> > > > > > > > > > > >
> "org.apache.royale.jewel.beads.views.FormItemView")
> >>> > > > > > > > > > > > IFormItemContentArea:
> >>> > > > > > > > ClassReference("org.apache.royale.jewel.Group")
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > These are the parts important to me.
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > I think we really want to change only the
> >>> IBeadView, so
> >>> > > we
> >>> > > > > can
> >>> > > > > > > > have a
> >>> > > > > > > > > > > > FormItemView and a StackedFormItemView, and could
> >>> > change
> >>> > > it
> >>> > > > > vía
> >>> > > > > > > > > > className
> >>> > > > > > > > > > > > (for example)
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > Let me know your thought about it
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > thanks
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > Carlos
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki
> >>> (<
> >>> > > > > > > > > > > > piotrzarzycki21@gmail.com>) escribió:
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > >> Carlos,
> >>> > > > > > > > > > > >>
> >>> > > > > > > > > > > >> I have analyzed FormItem in Flex and here is how
> >>> it is
> >>> > > > done
> >>> > > > > > > there.
> >>> > > > > > > > > > > >> StackedFormItemSkin is using FormItemLayout
> which
> >>> is
> >>> > > > > > constrained
> >>> > > > > > > > > into
> >>> > > > > > > > > > 3
> >>> > > > > > > > > > > >> columns (sequenceCol, contentCol and helpCol)
> and
> >>> 2
> >>> > > rows.
> >>> > > > > > [1][2]
> >>> > > > > > > > > > > >>
> >>> > > > > > > > > > > >> When you look into the screenshot [2] you may
> >>> think
> >>> > that
> >>> > > > > > reuired
> >>> > > > > > > > > > > indicator
> >>> > > > > > > > > > > >> is part of the content, but it's not. It's not
> >>> even
> >>> > part
> >>> > > > of
> >>> > > > > > the
> >>> > > > > > > > > layout
> >>> > > > > > > > > > > >> cause it has includeInLayout="false". [3]
> >>> > > > > > > > > > > >> In Royale we don't have concept that something
> >>> doesn't
> >>> > > > > belong
> >>> > > > > > to
> >>> > > > > > > > > > layout
> >>> > > > > > > > > > > >> and
> >>> > > > > > > > > > > >> is not calculated and indicator default is being
> >>> > placed
> >>> > > in
> >>> > > > > > > > different
> >>> > > > > > > > > > > area.
> >>> > > > > > > > > > > >> Do you have some idea apart what I have proposed
> >>> how
> >>> > to
> >>> > > > > > resolve
> >>> > > > > > > > > that ?
> >>> > > > > > > > > > > >>
> >>> > > > > > > > > > > >> [1] https://paste.apache.org/9Imj
> >>> > > > > > > > > > > >> [2] https://imgur.com/GGOtzEU
> >>> > > > > > > > > > > >> [3] https://paste.apache.org/kqlP
> >>> > > > > > > > > > > >>
> >>> > > > > > > > > > > >> Thanks,
> >>> > > > > > > > > > > >> Piotr
> >>> > > > > > > > > > > >>
> >>> > > > > > > > > > > >>
> >>> > > > > > > > > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
> >>> > > > > > > > piotrzarzycki21@gmail.com>
> >>> > > > > > > > > > > >> napisał(a):
> >>> > > > > > > > > > > >>
> >>> > > > > > > > > > > >> > That's more clear to me. I will check and get
> >>> back
> >>> > to
> >>> > > > you.
> >>> > > > > > > > > > > >> >
> >>> > > > > > > > > > > >> > Thank you!
> >>> > > > > > > > > > > >> >
> >>> > > > > > > > > > > >> >
> >>> > > > > > > > > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <
> >>> > > > > > > carlosrovira@apache.org
> >>> > > > > > > > >
> >>> > > > > > > > > > > >> > napisał(a):
> >>> > > > > > > > > > > >> >
> >>> > > > > > > > > > > >> >> No,
> >>> > > > > > > > > > > >> >>
> >>> > > > > > > > > > > >> >> I was asking you about how flex solves
> visualy
> >>> the
> >>> > > > > problem
> >>> > > > > > in
> >>> > > > > > > > > their
> >>> > > > > > > > > > > >> >> stacked
> >>> > > > > > > > > > > >> >> version. The required icon is setup next to
> the
> >>> > > label?
> >>> > > > is
> >>> > > > > > in
> >>> > > > > > > > > other
> >>> > > > > > > > > > > >> place?
> >>> > > > > > > > > > > >> >> if we had an image of how it is designed (and
> >>> like
> >>> > > it),
> >>> > > > > we
> >>> > > > > > > can
> >>> > > > > > > > > copy
> >>> > > > > > > > > > > >> it. I
> >>> > > > > > > > > > > >> >> still not proposing a technical solution.
> Just
> >>> > that I
> >>> > > > > don't
> >>> > > > > > > > have
> >>> > > > > > > > > > > clear
> >>> > > > > > > > > > > >> how
> >>> > > > > > > > > > > >> >> we should layout it
> >>> > > > > > > > > > > >> >>
> >>> > > > > > > > > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr
> >>> Zarzycki
> >>> > (<
> >>> > > > > > > > > > > >> >> piotrzarzycki21@gmail.com>) escribió:
> >>> > > > > > > > > > > >> >>
> >>> > > > > > > > > > > >> >> > Carlos,
> >>> > > > > > > > > > > >> >> >
> >>> > > > > > > > > > > >> >> > Your suggestion is to have new form item
> >>> > > > > > (StackedFormItem)
> >>> > > > > > > > with
> >>> > > > > > > > > > new
> >>> > > > > > > > > > > >> >> > StackedFormItemView - cause problem is
> inside
> >>> > > > > > FormitemView,
> >>> > > > > > > > not
> >>> > > > > > > > > > > >> inside
> >>> > > > > > > > > > > >> >> > layout itself. Current layout is doing what
> >>> it
> >>> > > should
> >>> > > > > do
> >>> > > > > > -
> >>> > > > > > > > > apart
> >>> > > > > > > > > > of
> >>> > > > > > > > > > > >> the
> >>> > > > > > > > > > > >> >> > problem - it's making children to be
> >>> > > > > Horizontal/Vertical.
> >>> > > > > > > > > > > >> >> >
> >>> > > > > > > > > > > >> >> > If I'm correct what you are saying - that's
> >>> ok,
> >>> > but
> >>> > > > if
> >>> > > > > > you
> >>> > > > > > > > have
> >>> > > > > > > > > > had
> >>> > > > > > > > > > > >> >> > different idea by saying above let me know.
> >>> > > > > > > > > > > >> >> >
> >>> > > > > > > > > > > >> >> > Thanks, Piotr
> >>> > > > > > > > > > > >> >> >
> >>> > > > > > > > > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
> >>> > > > > > > > > carlosrovira@apache.org>
> >>> > > > > > > > > > > >> >> > napisał(a):
> >>> > > > > > > > > > > >> >> >
> >>> > > > > > > > > > > >> >> > > Ok, I understand now.
> >>> > > > > > > > > > > >> >> > >
> >>> > > > > > > > > > > >> >> > > In Flex I think we had that layout and
> was
> >>> > > > > > > > > > > >> called....StackedFormItem
> >>> > > > > > > > > > > >> >> or
> >>> > > > > > > > > > > >> >> > > something like that?
> >>> > > > > > > > > > > >> >> > > Could you check how Flex solve this? If
> we
> >>> > > continue
> >>> > > > > > > liking
> >>> > > > > > > > > the
> >>> > > > > > > > > > > way
> >>> > > > > > > > > > > >> >> > stacked
> >>> > > > > > > > > > > >> >> > > form layout in flex looks, we can do the
> >>> same
> >>> > for
> >>> > > > our
> >>> > > > > > > > Royale
> >>> > > > > > > > > > > >> version
> >>> > > > > > > > > > > >> >> > >
> >>> > > > > > > > > > > >> >> > >
> >>> > > > > > > > > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr
> >>> > Zarzycki
> >>> > > > (<
> >>> > > > > > > > > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
> >>> > > > > > > > > > > >> >> > >
> >>> > > > > > > > > > > >> >> > > > I'm not sure how Serkan is doing that
> on
> >>> > users
> >>> > > > > forum,
> >>> > > > > > > > but I
> >>> > > > > > > > > > see
> >>> > > > > > > > > > > >> all
> >>> > > > > > > > > > > >> >> > hist
> >>> > > > > > > > > > > >> >> > > > pasted images. Anyway here you go:
> >>> > > > > > > > > > > >> >> > > >
> >>> > > > > > > > > > > >> >> > > > What I wanted to achieve:
> >>> > > > > https://snag.gy/DmH7yk.jpg
> >>> > > > > > > > > > > >> >> > > > What I got from Jewel FormItem:
> >>> > > > > > > > https://snag.gy/Slfbt9.jpg
> >>> > > > > > > > > > > >> >> > > >
> >>> > > > > > > > > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira
> <
> >>> > > > > > > > > > > carlosrovira@apache.org>
> >>> > > > > > > > > > > >> >> > > > napisał(a):
> >>> > > > > > > > > > > >> >> > > >
> >>> > > > > > > > > > > >> >> > > > > Piotr,
> >>> > > > > > > > > > > >> >> > > > >
> >>> > > > > > > > > > > >> >> > > > > remember that images pasted in list
> >>> are not
> >>> > > > > shared,
> >>> > > > > > > you
> >>> > > > > > > > > > must
> >>> > > > > > > > > > > >> share
> >>> > > > > > > > > > > >> >> > with
> >>> > > > > > > > > > > >> >> > > > > some image service
> >>> > > > > > > > > > > >> >> > > > >
> >>> > > > > > > > > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14,
> >>> Piotr
> >>> > > > Zarzycki
> >>> > > > > > (<
> >>> > > > > > > > > > > >> >> > > > > piotrzarzycki21@gmail.com>)
> escribió:
> >>> > > > > > > > > > > >> >> > > > >
> >>> > > > > > > > > > > >> >> > > > > > There is one more problem with
> >>> Layout.
> >>> > > > > Currently
> >>> > > > > > > > > default
> >>> > > > > > > > > > in
> >>> > > > > > > > > > > >> >> > framework
> >>> > > > > > > > > > > >> >> > > > we
> >>> > > > > > > > > > > >> >> > > > > > have [1]. It means that:
> >>> > > > > > > > > > > >> >> > > > > >
> >>> > > > > > > > > > > >> >> > > > > > My content of FormItem will be
> >>> vertical
> >>> > and
> >>> > > > > > > > IBeadLayout
> >>> > > > > > > > > > is
> >>> > > > > > > > > > > >> >> > basically
> >>> > > > > > > > > > > >> >> > > > > > ignored at some point. If I specify
> >>> > beads -
> >>> > > > > > > > > > > HorizontalLayout
> >>> > > > > > > > > > > >> as
> >>> > > > > > > > > > > >> >> it
> >>> > > > > > > > > > > >> >> > is
> >>> > > > > > > > > > > >> >> > > > in
> >>> > > > > > > > > > > >> >> > > > > > above example it will be taken as a
> >>> > primary
> >>> > > > > and I
> >>> > > > > > > > have
> >>> > > > > > > > > my
> >>> > > > > > > > > > > >> >> content
> >>> > > > > > > > > > > >> >> > > > laying
> >>> > > > > > > > > > > >> >> > > > > > out horizontally. The question is -
> >>> what
> >>> > is
> >>> > > > for
> >>> > > > > > > > > > > >> >> IFormItemLayout in
> >>> > > > > > > > > > > >> >> > > > > > default.css? Is it a bug?
> >>> > > > > > > > > > > >> >> > > > > >
> >>> > > > > > > > > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
> >>> > > > > > > > > > > >> >> > > > > >
> >>> > > > > > > > > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr
> >>> Zarzycki <
> >>> > > > > > > > > > > >> >> piotrzarzycki21@gmail.com
> >>> > > > > > > > > > > >> >> > >
> >>> > > > > > > > > > > >> >> > > > > > napisał(a):
> >>> > > > > > > > > > > >> >> > > > > >
> >>> > > > > > > > > > > >> >> > > > > >> Hi Carlos,
> >>> > > > > > > > > > > >> >> > > > > >>
> >>> > > > > > > > > > > >> >> > > > > >> I'm was trying to change FormItem
> >>> to be
> >>> > > > > Vertical
> >>> > > > > > > > > > oriented.
> >>> > > > > > > > > > > >> In
> >>> > > > > > > > > > > >> >> > > general
> >>> > > > > > > > > > > >> >> > > > I
> >>> > > > > > > > > > > >> >> > > > > >> would like to have following view.
> >>> Label
> >>> > > of
> >>> > > > > > > FormItem
> >>> > > > > > > > > is
> >>> > > > > > > > > > on
> >>> > > > > > > > > > > >> the
> >>> > > > > > > > > > > >> >> top
> >>> > > > > > > > > > > >> >> > > and
> >>> > > > > > > > > > > >> >> > > > > in
> >>> > > > > > > > > > > >> >> > > > > >> the bottom is content.
> >>> > > > > > > > > > > >> >> > > > > >>
> >>> > > > > > > > > > > >> >> > > > > >> [image: image.png]
> >>> > > > > > > > > > > >> >> > > > > >>
> >>> > > > > > > > > > > >> >> > > > > >> Code for that will looks like that
> >>> [1].
> >>> > > > > Results
> >>> > > > > > is
> >>> > > > > > > > > > > >> following:
> >>> > > > > > > > > > > >> >> > > > > >>
> >>> > > > > > > > > > > >> >> > > > > >> [image: image.png]
> >>> > > > > > > > > > > >> >> > > > > >>
> >>> > > > > > > > > > > >> >> > > > > >> It happened cause Label and
> required
> >>> > star
> >>> > > > > label
> >>> > > > > > > are
> >>> > > > > > > > > > > >> different
> >>> > > > > > > > > > > >> >> > > > components
> >>> > > > > > > > > > > >> >> > > > > >> - everything is being laying out
> >>> > > vertically.
> >>> > > > > > What
> >>> > > > > > > is
> >>> > > > > > > > > > your
> >>> > > > > > > > > > > >> >> > suggestion
> >>> > > > > > > > > > > >> >> > > > to
> >>> > > > > > > > > > > >> >> > > > > fix
> >>> > > > > > > > > > > >> >> > > > > >> that ?
> >>> > > > > > > > > > > >> >> > > > > >>
> >>> > > > > > > > > > > >> >> > > > > >> Mine is wrapping "First name" and
> >>> "*"
> >>> > into
> >>> > > > one
> >>> > > > > > > Group
> >>> > > > > > > > > > with
> >>> > > > > > > > > > > >> >> > > > > >> HorizontalLayout.
> >>> > > > > > > > > > > >> >> > > > > >>
> >>> > > > > > > > > > > >> >> > > > > >> More thoughts are welcome. I hope
> >>> you
> >>> > see
> >>> > > > > > > > screenshots.
> >>> > > > > > > > > > :)
> >>> > > > > > > > > > > >> >> > > > > >>
> >>> > > > > > > > > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
> >>> > > > > > > > > > > >> >> > > > > >>
> >>> > > > > > > > > > > >> >> > > > > >> Thanks,
> >>> > > > > > > > > > > >> >> > > > > >> --
> >>> > > > > > > > > > > >> >> > > > > >>
> >>> > > > > > > > > > > >> >> > > > > >> Piotr Zarzycki
> >>> > > > > > > > > > > >> >> > > > > >>
> >>> > > > > > > > > > > >> >> > > > > >> Patreon: *
> >>> > > > > https://www.patreon.com/piotrzarzycki
> >>> > > > > > > > > > > >> >> > > > > >> <
> >>> https://www.patreon.com/piotrzarzycki
> >>> > >*
> >>> > > > > > > > > > > >> >> > > > > >>
> >>> > > > > > > > > > > >> >> > > > > >
> >>> > > > > > > > > > > >> >> > > > > >
> >>> > > > > > > > > > > >> >> > > > > > --
> >>> > > > > > > > > > > >> >> > > > > >
> >>> > > > > > > > > > > >> >> > > > > > Piotr Zarzycki
> >>> > > > > > > > > > > >> >> > > > > >
> >>> > > > > > > > > > > >> >> > > > > > Patreon: *
> >>> > > > > https://www.patreon.com/piotrzarzycki
> >>> > > > > > > > > > > >> >> > > > > > <
> >>> https://www.patreon.com/piotrzarzycki>*
> >>> > > > > > > > > > > >> >> > > > > >
> >>> > > > > > > > > > > >> >> > > > >
> >>> > > > > > > > > > > >> >> > > > >
> >>> > > > > > > > > > > >> >> > > > > --
> >>> > > > > > > > > > > >> >> > > > > Carlos Rovira
> >>> > > > > > > > > > > >> >> > > > > http://about.me/carlosrovira
> >>> > > > > > > > > > > >> >> > > > >
> >>> > > > > > > > > > > >> >> > > >
> >>> > > > > > > > > > > >> >> > > >
> >>> > > > > > > > > > > >> >> > > > --
> >>> > > > > > > > > > > >> >> > > >
> >>> > > > > > > > > > > >> >> > > > Piotr Zarzycki
> >>> > > > > > > > > > > >> >> > > >
> >>> > > > > > > > > > > >> >> > > > Patreon: *
> >>> > > https://www.patreon.com/piotrzarzycki
> >>> > > > > > > > > > > >> >> > > > <https://www.patreon.com/piotrzarzycki
> >*
> >>> > > > > > > > > > > >> >> > > >
> >>> > > > > > > > > > > >> >> > >
> >>> > > > > > > > > > > >> >> > >
> >>> > > > > > > > > > > >> >> > > --
> >>> > > > > > > > > > > >> >> > > Carlos Rovira
> >>> > > > > > > > > > > >> >> > > http://about.me/carlosrovira
> >>> > > > > > > > > > > >> >> > >
> >>> > > > > > > > > > > >> >> >
> >>> > > > > > > > > > > >> >> >
> >>> > > > > > > > > > > >> >> > --
> >>> > > > > > > > > > > >> >> >
> >>> > > > > > > > > > > >> >> > Piotr Zarzycki
> >>> > > > > > > > > > > >> >> >
> >>> > > > > > > > > > > >> >> > Patreon: *
> >>> https://www.patreon.com/piotrzarzycki
> >>> > > > > > > > > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
> >>> > > > > > > > > > > >> >> >
> >>> > > > > > > > > > > >> >>
> >>> > > > > > > > > > > >> >>
> >>> > > > > > > > > > > >> >> --
> >>> > > > > > > > > > > >> >> Carlos Rovira
> >>> > > > > > > > > > > >> >> http://about.me/carlosrovira
> >>> > > > > > > > > > > >> >>
> >>> > > > > > > > > > > >> >
> >>> > > > > > > > > > > >> >
> >>> > > > > > > > > > > >> > --
> >>> > > > > > > > > > > >> >
> >>> > > > > > > > > > > >> > Piotr Zarzycki
> >>> > > > > > > > > > > >> >
> >>> > > > > > > > > > > >> > Patreon: *
> https://www.patreon.com/piotrzarzycki
> >>> > > > > > > > > > > >> > <https://www.patreon.com/piotrzarzycki>*
> >>> > > > > > > > > > > >> >
> >>> > > > > > > > > > > >>
> >>> > > > > > > > > > > >>
> >>> > > > > > > > > > > >> --
> >>> > > > > > > > > > > >>
> >>> > > > > > > > > > > >> Piotr Zarzycki
> >>> > > > > > > > > > > >>
> >>> > > > > > > > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> >>> > > > > > > > > > > >> <https://www.patreon.com/piotrzarzycki>*
> >>> > > > > > > > > > > >>
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > > --
> >>> > > > > > > > > > > > Carlos Rovira
> >>> > > > > > > > > > > > http://about.me/carlosrovira
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > > >
> >>> > > > > > > > > > >
> >>> > > > > > > > > > > --
> >>> > > > > > > > > > > Carlos Rovira
> >>> > > > > > > > > > > http://about.me/carlosrovira
> >>> > > > > > > > > > >
> >>> > > > > > > > > >
> >>> > > > > > > > >
> >>> > > > > > > > >
> >>> > > > > > > > > --
> >>> > > > > > > > > Carlos Rovira
> >>> > > > > > > > > http://about.me/carlosrovira
> >>> > > > > > > > >
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > > > > > --
> >>> > > > > > > >
> >>> > > > > > > > Piotr Zarzycki
> >>> > > > > > > >
> >>> > > > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> >>> > > > > > > > <https://www.patreon.com/piotrzarzycki>*
> >>> > > > > > > >
> >>> > > > > > >
> >>> > > > > > >
> >>> > > > > > > --
> >>> > > > > > > Carlos Rovira
> >>> > > > > > > http://about.me/carlosrovira
> >>> > > > > > >
> >>> > > > > >
> >>> > > > > >
> >>> > > > > > --
> >>> > > > > >
> >>> > > > > > Piotr Zarzycki
> >>> > > > > >
> >>> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> >>> > > > > > <https://www.patreon.com/piotrzarzycki>*
> >>> > > > > >
> >>> > > > >
> >>> > > > >
> >>> > > > > --
> >>> > > > > Carlos Rovira
> >>> > > > > http://about.me/carlosrovira
> >>> > > > >
> >>> > > >
> >>> > > >
> >>> > > > --
> >>> > > >
> >>> > > > Piotr Zarzycki
> >>> > > >
> >>> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> >>> > > > <https://www.patreon.com/piotrzarzycki>*
> >>> > > >
> >>> > >
> >>> > >
> >>> > > --
> >>> > > Carlos Rovira
> >>> > > http://about.me/carlosrovira
> >>> > >
> >>> >
> >>> >
> >>> > --
> >>> >
> >>> > Piotr Zarzycki
> >>> >
> >>> > Patreon: *https://www.patreon.com/piotrzarzycki
> >>> > <https://www.patreon.com/piotrzarzycki>*
> >>> >
> >>>
> >>>
> >>> --
> >>> Carlos Rovira
> >>> http://about.me/carlosrovira
> >>>
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> <https://www.patreon.com/piotrzarzycki>*
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

In my opinion this part should looks like that:
https://paste.apache.org/gbn2 - Simple initialization. If someone would
like to use anything more than default (currently it's IFormItemContentArea:
ClassReference("org.apache.royale.jewel.Group"); ) - He can use it - for
example HGroup.

What do you think ?

sob., 26 sty 2019 o 12:58 Piotr Zarzycki <pi...@gmail.com>
napisał(a):

> Remember I'm talking above only about contentArea of FormItem.
>
> sob., 26 sty 2019 o 12:57 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
>> Carlos,
>>
>> I think I got it. It looks like we don't need IFormItemLayout as you
>> said, cause I should be able to manipulate content of my FormItem by doing
>> that:
>>
>> IBeadLayout:
>> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
>> IFormItemContentArea: ClassReference("org.apache.royale.jewel.HGroup");
>>
>> However above code won't work cause you have this [1] - transferLayoutBead
>> is being added to contentArea you have now in output code for content area
>> something weird. [2]
>>
>> To me IBeadLayout - shouldn't be transfered to content - Are you agree ?
>>
>> [1] https://paste.apache.org/m9ST
>> [2] https://paste.apache.org/9Orx
>>
>> Thanks,
>> Piotr
>>
>>
>> sob., 26 sty 2019 o 12:18 Carlos Rovira <ca...@apache.org>
>> napisał(a):
>>
>>> Piotr, I think I don't think we need and IFormItemLayout.
>>> IBeadLayout seems sufficient for me, since that layout will be based just
>>> on css selectors that are in the end what solves the layout
>>>
>>> El sáb., 26 ene. 2019 a las 12:00, Piotr Zarzycki (<
>>> piotrzarzycki21@gmail.com>) escribió:
>>>
>>> > Too bad that you didn't understand me. Just question to above
>>> requirements
>>> > - What in your opinion should do layout added trough ->
>>> *IFormItemLayout
>>> > ?*
>>> >
>>> > sob., 26 sty 2019 o 11:54 Carlos Rovira <ca...@apache.org>
>>> > napisał(a):
>>> >
>>> > > Hi Piotr,
>>> > >
>>> > > Don't think if I understand right your exposition. I'll try to write
>>> in
>>> > > words what I expect from a FormItemLayout and let me know if we're
>>> > thinking
>>> > > on the same.
>>> > >
>>> > > We want to have a specialized layout for FormItem that support
>>> horizontal
>>> > > and stacked form item layouts. At this point we can choose to have 2
>>> > > layouts or only 1.
>>> > > Since we always have 2, maybe that's the best way to go :
>>> > > HorizontalFormItemLayout and VerticalFormItemLayout.
>>> > >
>>> > > HorizontalFormItemLayout: should put label, required indicator and
>>> > content
>>> > > in the same "row", o mostly as HorizontalLayout does, and will be
>>> equal
>>> > to
>>> > > what we have now.
>>> > >
>>> > > VerticalFormItemLayout should put Label followed by
>>> requiredIndicator in
>>> > a
>>> > > row and just below, the content part. *Or* Label in a row and below
>>> > Content
>>> > > followed by requited Indicator
>>> > > (I think this should be configurable in some way, or implement a
>>> case and
>>> > > made and additional layout for the other, so we can have both).
>>> > >
>>> > > Some technical needs:
>>> > >
>>> > > * All we'll be solved using CSS and css class selectors as with the
>>> rest
>>> > of
>>> > > Jewel Layouts and phyloshopy
>>> > > * We'll continue using flexbox since is the standard in Jewel
>>> > > * We can use the flexbox order to have a property that puts content
>>> > before
>>> > > required indicator or viceversa using a property in the layout.
>>> > > * I think FormItemView would need to adapt to this, and maybe will
>>> need
>>> > two
>>> > > Views to support each layout (don't have clear now)
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > El vie., 25 ene. 2019 a las 16:23, Piotr Zarzycki (<
>>> > > piotrzarzycki21@gmail.com>) escribió:
>>> > >
>>> > > > I won't follow Flex, so if you would like to do this I'm fine. I'm
>>> > going
>>> > > to
>>> > > > implement my own View in my application. I won't commit it to
>>> Royale.
>>> > > > However I would like to fix issue with layout. Currently
>>> IBeadLayout -
>>> > Is
>>> > > > making whole FormItem vertical or horizontal. *IFormItemLayout -
>>> Should
>>> > > > treat content appropriately, but it doesn't do anything. I would
>>> like
>>> > to
>>> > > > change it in the following way:*
>>> > > >
>>> > > > *IBeadLayout do:*
>>> > > >
>>> > > > *1) When user: IBeadLayout:
>>> > > >
>>> >
>>> ClassReference("org.apache.royale.jewel.beads.layouts.VerticalLayout");*
>>> > > > L
>>> > > > C
>>> > > > *2) When user: **IBeadLayout:
>>> > > >
>>> > >
>>> >
>>> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");*
>>> > > > *L C*
>>> > > >
>>> > > > *IFormItemLayout will do:*
>>> > > > 1) IFormItemLayout:
>>> > > >
>>> >
>>> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
>>> > > > and #1 - *IBeadLayout*
>>> > > > L
>>> > > > C - Set children Horizotnally
>>> > > > 2) IFormItemLayout:
>>> > > >
>>> >
>>> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
>>> > > > and #2 - *IBeadLayout*
>>> > > > *L*
>>> > > > *C - Set children Vertically*
>>> > > >
>>> > > > *Thoughts ?*
>>> > > >
>>> > > > Piotr
>>> > > >
>>> > > >
>>> > > >
>>> > > > pt., 25 sty 2019 o 16:13 Carlos Rovira <ca...@apache.org>
>>> > > > napisał(a):
>>> > > >
>>> > > > > Ops!,
>>> > > > >
>>> > > > > ok, since I was using the other layout I was in the believe that
>>> was
>>> > > the
>>> > > > > standard. So if we want to follow flex, we can change the
>>> current as
>>> > > > well.
>>> > > > >
>>> > > > > El jue., 24 ene. 2019 a las 18:34, Piotr Zarzycki (<
>>> > > > > piotrzarzycki21@gmail.com>) escribió:
>>> > > > >
>>> > > > > > Nope - I just checked [1] - Code [2] - You are showing me some
>>> > custom
>>> > > > > > implementation.
>>> > > > > >
>>> > > > > > [1] https://imgur.com/INKlfcC
>>> > > > > > [2] https://paste.apache.org/jyrl
>>> > > > > >
>>> > > > > > czw., 24 sty 2019 o 18:20 Carlos Rovira <
>>> carlosrovira@apache.org>
>>> > > > > > napisał(a):
>>> > > > > >
>>> > > > > > > Piotr,
>>> > > > > > >
>>> > > > > > > in Flex we have the same align (as we have now in Royale),
>>> check
>>> > > this
>>> > > > > > > image: url
>>> > > > > > > <
>>> > > > > > >
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249
>>> > > > > > > >
>>> > > > > > >
>>> > > > > > > El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
>>> > > > > > > piotrzarzycki21@gmail.com>) escribió:
>>> > > > > > >
>>> > > > > > > > If we are going in that direction it requires as well work
>>> were
>>> > > > > > indicator
>>> > > > > > > > in case of L* C (current implementation) will be changed
>>> to L
>>> > C*
>>> > > -
>>> > > > > Yes
>>> > > > > > ?
>>> > > > > > > -
>>> > > > > > > > Being consistent it should be like that.
>>> > > > > > > >
>>> > > > > > > > I'm not sure what the trends are in that case.
>>> > > > > > > >
>>> > > > > > > > czw., 24 sty 2019 o 17:51 Carlos Rovira <
>>> > carlosrovira@apache.org
>>> > > >
>>> > > > > > > > napisał(a):
>>> > > > > > > >
>>> > > > > > > > > Hi Piotr,
>>> > > > > > > > >
>>> > > > > > > > > since is what you show in the flex version.
>>> > > > > > > > > I think Adobe put side to content instead of side to
>>> label
>>> > > since
>>> > > > > the
>>> > > > > > > user
>>> > > > > > > > > fill the content elements and if not filled and required
>>> ,
>>> > the
>>> > > > > > tooltip
>>> > > > > > > > > should popup there.
>>> > > > > > > > > IOW, for usability, seems more appropriated the way flex
>>> > > > layedout,
>>> > > > > or
>>> > > > > > > > seems
>>> > > > > > > > > more natural.
>>> > > > > > > > >
>>> > > > > > > > > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
>>> > > > > > > > > piotrzarzycki21@gmail.com>) escribió:
>>> > > > > > > > >
>>> > > > > > > > > > Carlos,
>>> > > > > > > > > >
>>> > > > > > > > > > Why you are proposing have that?
>>> > > > > > > > > >
>>> > > > > > > > > > L
>>> > > > > > > > > > C *
>>> > > > > > > > > >
>>> > > > > > > > > > I'm in favor of staying
>>> > > > > > > > > >
>>> > > > > > > > > > L *
>>> > > > > > > > > > C
>>> > > > > > > > > >
>>> > > > > > > > > > Thanks,
>>> > > > > > > > > > Piotr
>>> > > > > > > > > >
>>> > > > > > > > > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <
>>> > > > > > carlosrovira@apache.org
>>> > > > > > > >
>>> > > > > > > > > > wrote:
>>> > > > > > > > > >
>>> > > > > > > > > > > I forgot to mention about IBeadLayout more, since it
>>> > could
>>> > > be
>>> > > > > > > > > > > misinterpreted:
>>> > > > > > > > > > >
>>> > > > > > > > > > > IBeadLayout for the global component is important,
>>> but
>>> > what
>>> > > > I'm
>>> > > > > > > > > > considering
>>> > > > > > > > > > > is that although we can put HorizontalLayout (for the
>>> > > current
>>> > > > > > > > > FormtItem)
>>> > > > > > > > > > > and VerticalLayout (for the stacked), I'm seeing that
>>> > many
>>> > > > > > > components
>>> > > > > > > > > > would
>>> > > > > > > > > > > need its own layout class. In this case we could
>>> create a
>>> > > > > > > > > FormItemLayout,
>>> > > > > > > > > > > and this will handle the layout vía CSS as it happens
>>> > > mostly
>>> > > > in
>>> > > > > > > many
>>> > > > > > > > > > other
>>> > > > > > > > > > > Jewel component.
>>> > > > > > > > > > >
>>> > > > > > > > > > > (Just say that some of them are using an standard
>>> layout
>>> > > > class,
>>> > > > > > > like
>>> > > > > > > > > > > HorizontalLayout, or even a NullLayout class), since
>>> I
>>> > > didn't
>>> > > > > > have
>>> > > > > > > > the
>>> > > > > > > > > > time
>>> > > > > > > > > > > to create its own one, and that's temporal. But my
>>> plan
>>> > is
>>> > > to
>>> > > > > > > create
>>> > > > > > > > a
>>> > > > > > > > > > > concrete layout for some of this components. FormItem
>>> > could
>>> > > > be
>>> > > > > > one
>>> > > > > > > of
>>> > > > > > > > > > those
>>> > > > > > > > > > > cases, for what we're seeing
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
>>> > > > > > > > > > carlosrovira@apache.org
>>> > > > > > > > > > > >)
>>> > > > > > > > > > > escribió:
>>> > > > > > > > > > >
>>> > > > > > > > > > > > Hi Piotr,
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > looking at the screen shot, seems the required
>>> > indicator
>>> > > is
>>> > > > > > > > > positioned
>>> > > > > > > > > > to
>>> > > > > > > > > > > > the right side of the element, what seems coherent,
>>> > > > although
>>> > > > > > > could
>>> > > > > > > > > be a
>>> > > > > > > > > > > bit
>>> > > > > > > > > > > > problematic depending on the width of the
>>> component. we
>>> > > > > assume
>>> > > > > > a
>>> > > > > > > > > fixed
>>> > > > > > > > > > > > width (to the widest element) and align all
>>> required
>>> > (or
>>> > > > not
>>> > > > > a
>>> > > > > > > put
>>> > > > > > > > > the
>>> > > > > > > > > > > > required indicator just before the element, anyway
>>> this
>>> > > > seems
>>> > > > > > > > > something
>>> > > > > > > > > > > to
>>> > > > > > > > > > > > be solved as we have some real implementation.
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > In order to implement it:
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > We have 3 parts:
>>> > > > > > > > > > > > - L (this is the label)
>>> > > > > > > > > > > > - * (this is the required indicator)
>>> > > > > > > > > > > > - C (this is the element(s) that the user adds)
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > * Actual FormItem is :
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > L * C
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > * We want for the new
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > L
>>> > > > > > > > > > > > C *
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > So it seems to me that
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > a) IBeadLayout: ClassReference(
>>> > > > > > > > > > > >
>>> > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
>>> > > > > > > > > > > > Does not has much sense to me
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > b) IFormItemLayout: ClassReference(
>>> > > > > > > > > > > >
>>> "org.apache.royale.jewel.beads.layouts.VerticalLayout")
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > This is the one important to me (to configure), so
>>> user
>>> > > can
>>> > > > > > > change
>>> > > > > > > > > > layout
>>> > > > > > > > > > > > of the content part
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > c) IBeadView: ClassReference(
>>> > > > > > > > > > > > "org.apache.royale.jewel.beads.views.FormItemView")
>>> > > > > > > > > > > > IFormItemContentArea:
>>> > > > > > > > ClassReference("org.apache.royale.jewel.Group")
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > These are the parts important to me.
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > I think we really want to change only the
>>> IBeadView, so
>>> > > we
>>> > > > > can
>>> > > > > > > > have a
>>> > > > > > > > > > > > FormItemView and a StackedFormItemView, and could
>>> > change
>>> > > it
>>> > > > > vía
>>> > > > > > > > > > className
>>> > > > > > > > > > > > (for example)
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > Let me know your thought about it
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > thanks
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > Carlos
>>> > > > > > > > > > > >
>>> > > > > > > > > > > >
>>> > > > > > > > > > > >
>>> > > > > > > > > > > >
>>> > > > > > > > > > > >
>>> > > > > > > > > > > >
>>> > > > > > > > > > > >
>>> > > > > > > > > > > >
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki
>>> (<
>>> > > > > > > > > > > > piotrzarzycki21@gmail.com>) escribió:
>>> > > > > > > > > > > >
>>> > > > > > > > > > > >> Carlos,
>>> > > > > > > > > > > >>
>>> > > > > > > > > > > >> I have analyzed FormItem in Flex and here is how
>>> it is
>>> > > > done
>>> > > > > > > there.
>>> > > > > > > > > > > >> StackedFormItemSkin is using FormItemLayout which
>>> is
>>> > > > > > constrained
>>> > > > > > > > > into
>>> > > > > > > > > > 3
>>> > > > > > > > > > > >> columns (sequenceCol, contentCol and helpCol) and
>>> 2
>>> > > rows.
>>> > > > > > [1][2]
>>> > > > > > > > > > > >>
>>> > > > > > > > > > > >> When you look into the screenshot [2] you may
>>> think
>>> > that
>>> > > > > > reuired
>>> > > > > > > > > > > indicator
>>> > > > > > > > > > > >> is part of the content, but it's not. It's not
>>> even
>>> > part
>>> > > > of
>>> > > > > > the
>>> > > > > > > > > layout
>>> > > > > > > > > > > >> cause it has includeInLayout="false". [3]
>>> > > > > > > > > > > >> In Royale we don't have concept that something
>>> doesn't
>>> > > > > belong
>>> > > > > > to
>>> > > > > > > > > > layout
>>> > > > > > > > > > > >> and
>>> > > > > > > > > > > >> is not calculated and indicator default is being
>>> > placed
>>> > > in
>>> > > > > > > > different
>>> > > > > > > > > > > area.
>>> > > > > > > > > > > >> Do you have some idea apart what I have proposed
>>> how
>>> > to
>>> > > > > > resolve
>>> > > > > > > > > that ?
>>> > > > > > > > > > > >>
>>> > > > > > > > > > > >> [1] https://paste.apache.org/9Imj
>>> > > > > > > > > > > >> [2] https://imgur.com/GGOtzEU
>>> > > > > > > > > > > >> [3] https://paste.apache.org/kqlP
>>> > > > > > > > > > > >>
>>> > > > > > > > > > > >> Thanks,
>>> > > > > > > > > > > >> Piotr
>>> > > > > > > > > > > >>
>>> > > > > > > > > > > >>
>>> > > > > > > > > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
>>> > > > > > > > piotrzarzycki21@gmail.com>
>>> > > > > > > > > > > >> napisał(a):
>>> > > > > > > > > > > >>
>>> > > > > > > > > > > >> > That's more clear to me. I will check and get
>>> back
>>> > to
>>> > > > you.
>>> > > > > > > > > > > >> >
>>> > > > > > > > > > > >> > Thank you!
>>> > > > > > > > > > > >> >
>>> > > > > > > > > > > >> >
>>> > > > > > > > > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <
>>> > > > > > > carlosrovira@apache.org
>>> > > > > > > > >
>>> > > > > > > > > > > >> > napisał(a):
>>> > > > > > > > > > > >> >
>>> > > > > > > > > > > >> >> No,
>>> > > > > > > > > > > >> >>
>>> > > > > > > > > > > >> >> I was asking you about how flex solves visualy
>>> the
>>> > > > > problem
>>> > > > > > in
>>> > > > > > > > > their
>>> > > > > > > > > > > >> >> stacked
>>> > > > > > > > > > > >> >> version. The required icon is setup next to the
>>> > > label?
>>> > > > is
>>> > > > > > in
>>> > > > > > > > > other
>>> > > > > > > > > > > >> place?
>>> > > > > > > > > > > >> >> if we had an image of how it is designed (and
>>> like
>>> > > it),
>>> > > > > we
>>> > > > > > > can
>>> > > > > > > > > copy
>>> > > > > > > > > > > >> it. I
>>> > > > > > > > > > > >> >> still not proposing a technical solution. Just
>>> > that I
>>> > > > > don't
>>> > > > > > > > have
>>> > > > > > > > > > > clear
>>> > > > > > > > > > > >> how
>>> > > > > > > > > > > >> >> we should layout it
>>> > > > > > > > > > > >> >>
>>> > > > > > > > > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr
>>> Zarzycki
>>> > (<
>>> > > > > > > > > > > >> >> piotrzarzycki21@gmail.com>) escribió:
>>> > > > > > > > > > > >> >>
>>> > > > > > > > > > > >> >> > Carlos,
>>> > > > > > > > > > > >> >> >
>>> > > > > > > > > > > >> >> > Your suggestion is to have new form item
>>> > > > > > (StackedFormItem)
>>> > > > > > > > with
>>> > > > > > > > > > new
>>> > > > > > > > > > > >> >> > StackedFormItemView - cause problem is inside
>>> > > > > > FormitemView,
>>> > > > > > > > not
>>> > > > > > > > > > > >> inside
>>> > > > > > > > > > > >> >> > layout itself. Current layout is doing what
>>> it
>>> > > should
>>> > > > > do
>>> > > > > > -
>>> > > > > > > > > apart
>>> > > > > > > > > > of
>>> > > > > > > > > > > >> the
>>> > > > > > > > > > > >> >> > problem - it's making children to be
>>> > > > > Horizontal/Vertical.
>>> > > > > > > > > > > >> >> >
>>> > > > > > > > > > > >> >> > If I'm correct what you are saying - that's
>>> ok,
>>> > but
>>> > > > if
>>> > > > > > you
>>> > > > > > > > have
>>> > > > > > > > > > had
>>> > > > > > > > > > > >> >> > different idea by saying above let me know.
>>> > > > > > > > > > > >> >> >
>>> > > > > > > > > > > >> >> > Thanks, Piotr
>>> > > > > > > > > > > >> >> >
>>> > > > > > > > > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
>>> > > > > > > > > carlosrovira@apache.org>
>>> > > > > > > > > > > >> >> > napisał(a):
>>> > > > > > > > > > > >> >> >
>>> > > > > > > > > > > >> >> > > Ok, I understand now.
>>> > > > > > > > > > > >> >> > >
>>> > > > > > > > > > > >> >> > > In Flex I think we had that layout and was
>>> > > > > > > > > > > >> called....StackedFormItem
>>> > > > > > > > > > > >> >> or
>>> > > > > > > > > > > >> >> > > something like that?
>>> > > > > > > > > > > >> >> > > Could you check how Flex solve this? If we
>>> > > continue
>>> > > > > > > liking
>>> > > > > > > > > the
>>> > > > > > > > > > > way
>>> > > > > > > > > > > >> >> > stacked
>>> > > > > > > > > > > >> >> > > form layout in flex looks, we can do the
>>> same
>>> > for
>>> > > > our
>>> > > > > > > > Royale
>>> > > > > > > > > > > >> version
>>> > > > > > > > > > > >> >> > >
>>> > > > > > > > > > > >> >> > >
>>> > > > > > > > > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr
>>> > Zarzycki
>>> > > > (<
>>> > > > > > > > > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
>>> > > > > > > > > > > >> >> > >
>>> > > > > > > > > > > >> >> > > > I'm not sure how Serkan is doing that on
>>> > users
>>> > > > > forum,
>>> > > > > > > > but I
>>> > > > > > > > > > see
>>> > > > > > > > > > > >> all
>>> > > > > > > > > > > >> >> > hist
>>> > > > > > > > > > > >> >> > > > pasted images. Anyway here you go:
>>> > > > > > > > > > > >> >> > > >
>>> > > > > > > > > > > >> >> > > > What I wanted to achieve:
>>> > > > > https://snag.gy/DmH7yk.jpg
>>> > > > > > > > > > > >> >> > > > What I got from Jewel FormItem:
>>> > > > > > > > https://snag.gy/Slfbt9.jpg
>>> > > > > > > > > > > >> >> > > >
>>> > > > > > > > > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
>>> > > > > > > > > > > carlosrovira@apache.org>
>>> > > > > > > > > > > >> >> > > > napisał(a):
>>> > > > > > > > > > > >> >> > > >
>>> > > > > > > > > > > >> >> > > > > Piotr,
>>> > > > > > > > > > > >> >> > > > >
>>> > > > > > > > > > > >> >> > > > > remember that images pasted in list
>>> are not
>>> > > > > shared,
>>> > > > > > > you
>>> > > > > > > > > > must
>>> > > > > > > > > > > >> share
>>> > > > > > > > > > > >> >> > with
>>> > > > > > > > > > > >> >> > > > > some image service
>>> > > > > > > > > > > >> >> > > > >
>>> > > > > > > > > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14,
>>> Piotr
>>> > > > Zarzycki
>>> > > > > > (<
>>> > > > > > > > > > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
>>> > > > > > > > > > > >> >> > > > >
>>> > > > > > > > > > > >> >> > > > > > There is one more problem with
>>> Layout.
>>> > > > > Currently
>>> > > > > > > > > default
>>> > > > > > > > > > in
>>> > > > > > > > > > > >> >> > framework
>>> > > > > > > > > > > >> >> > > > we
>>> > > > > > > > > > > >> >> > > > > > have [1]. It means that:
>>> > > > > > > > > > > >> >> > > > > >
>>> > > > > > > > > > > >> >> > > > > > My content of FormItem will be
>>> vertical
>>> > and
>>> > > > > > > > IBeadLayout
>>> > > > > > > > > > is
>>> > > > > > > > > > > >> >> > basically
>>> > > > > > > > > > > >> >> > > > > > ignored at some point. If I specify
>>> > beads -
>>> > > > > > > > > > > HorizontalLayout
>>> > > > > > > > > > > >> as
>>> > > > > > > > > > > >> >> it
>>> > > > > > > > > > > >> >> > is
>>> > > > > > > > > > > >> >> > > > in
>>> > > > > > > > > > > >> >> > > > > > above example it will be taken as a
>>> > primary
>>> > > > > and I
>>> > > > > > > > have
>>> > > > > > > > > my
>>> > > > > > > > > > > >> >> content
>>> > > > > > > > > > > >> >> > > > laying
>>> > > > > > > > > > > >> >> > > > > > out horizontally. The question is -
>>> what
>>> > is
>>> > > > for
>>> > > > > > > > > > > >> >> IFormItemLayout in
>>> > > > > > > > > > > >> >> > > > > > default.css? Is it a bug?
>>> > > > > > > > > > > >> >> > > > > >
>>> > > > > > > > > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
>>> > > > > > > > > > > >> >> > > > > >
>>> > > > > > > > > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr
>>> Zarzycki <
>>> > > > > > > > > > > >> >> piotrzarzycki21@gmail.com
>>> > > > > > > > > > > >> >> > >
>>> > > > > > > > > > > >> >> > > > > > napisał(a):
>>> > > > > > > > > > > >> >> > > > > >
>>> > > > > > > > > > > >> >> > > > > >> Hi Carlos,
>>> > > > > > > > > > > >> >> > > > > >>
>>> > > > > > > > > > > >> >> > > > > >> I'm was trying to change FormItem
>>> to be
>>> > > > > Vertical
>>> > > > > > > > > > oriented.
>>> > > > > > > > > > > >> In
>>> > > > > > > > > > > >> >> > > general
>>> > > > > > > > > > > >> >> > > > I
>>> > > > > > > > > > > >> >> > > > > >> would like to have following view.
>>> Label
>>> > > of
>>> > > > > > > FormItem
>>> > > > > > > > > is
>>> > > > > > > > > > on
>>> > > > > > > > > > > >> the
>>> > > > > > > > > > > >> >> top
>>> > > > > > > > > > > >> >> > > and
>>> > > > > > > > > > > >> >> > > > > in
>>> > > > > > > > > > > >> >> > > > > >> the bottom is content.
>>> > > > > > > > > > > >> >> > > > > >>
>>> > > > > > > > > > > >> >> > > > > >> [image: image.png]
>>> > > > > > > > > > > >> >> > > > > >>
>>> > > > > > > > > > > >> >> > > > > >> Code for that will looks like that
>>> [1].
>>> > > > > Results
>>> > > > > > is
>>> > > > > > > > > > > >> following:
>>> > > > > > > > > > > >> >> > > > > >>
>>> > > > > > > > > > > >> >> > > > > >> [image: image.png]
>>> > > > > > > > > > > >> >> > > > > >>
>>> > > > > > > > > > > >> >> > > > > >> It happened cause Label and required
>>> > star
>>> > > > > label
>>> > > > > > > are
>>> > > > > > > > > > > >> different
>>> > > > > > > > > > > >> >> > > > components
>>> > > > > > > > > > > >> >> > > > > >> - everything is being laying out
>>> > > vertically.
>>> > > > > > What
>>> > > > > > > is
>>> > > > > > > > > > your
>>> > > > > > > > > > > >> >> > suggestion
>>> > > > > > > > > > > >> >> > > > to
>>> > > > > > > > > > > >> >> > > > > fix
>>> > > > > > > > > > > >> >> > > > > >> that ?
>>> > > > > > > > > > > >> >> > > > > >>
>>> > > > > > > > > > > >> >> > > > > >> Mine is wrapping "First name" and
>>> "*"
>>> > into
>>> > > > one
>>> > > > > > > Group
>>> > > > > > > > > > with
>>> > > > > > > > > > > >> >> > > > > >> HorizontalLayout.
>>> > > > > > > > > > > >> >> > > > > >>
>>> > > > > > > > > > > >> >> > > > > >> More thoughts are welcome. I hope
>>> you
>>> > see
>>> > > > > > > > screenshots.
>>> > > > > > > > > > :)
>>> > > > > > > > > > > >> >> > > > > >>
>>> > > > > > > > > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
>>> > > > > > > > > > > >> >> > > > > >>
>>> > > > > > > > > > > >> >> > > > > >> Thanks,
>>> > > > > > > > > > > >> >> > > > > >> --
>>> > > > > > > > > > > >> >> > > > > >>
>>> > > > > > > > > > > >> >> > > > > >> Piotr Zarzycki
>>> > > > > > > > > > > >> >> > > > > >>
>>> > > > > > > > > > > >> >> > > > > >> Patreon: *
>>> > > > > https://www.patreon.com/piotrzarzycki
>>> > > > > > > > > > > >> >> > > > > >> <
>>> https://www.patreon.com/piotrzarzycki
>>> > >*
>>> > > > > > > > > > > >> >> > > > > >>
>>> > > > > > > > > > > >> >> > > > > >
>>> > > > > > > > > > > >> >> > > > > >
>>> > > > > > > > > > > >> >> > > > > > --
>>> > > > > > > > > > > >> >> > > > > >
>>> > > > > > > > > > > >> >> > > > > > Piotr Zarzycki
>>> > > > > > > > > > > >> >> > > > > >
>>> > > > > > > > > > > >> >> > > > > > Patreon: *
>>> > > > > https://www.patreon.com/piotrzarzycki
>>> > > > > > > > > > > >> >> > > > > > <
>>> https://www.patreon.com/piotrzarzycki>*
>>> > > > > > > > > > > >> >> > > > > >
>>> > > > > > > > > > > >> >> > > > >
>>> > > > > > > > > > > >> >> > > > >
>>> > > > > > > > > > > >> >> > > > > --
>>> > > > > > > > > > > >> >> > > > > Carlos Rovira
>>> > > > > > > > > > > >> >> > > > > http://about.me/carlosrovira
>>> > > > > > > > > > > >> >> > > > >
>>> > > > > > > > > > > >> >> > > >
>>> > > > > > > > > > > >> >> > > >
>>> > > > > > > > > > > >> >> > > > --
>>> > > > > > > > > > > >> >> > > >
>>> > > > > > > > > > > >> >> > > > Piotr Zarzycki
>>> > > > > > > > > > > >> >> > > >
>>> > > > > > > > > > > >> >> > > > Patreon: *
>>> > > https://www.patreon.com/piotrzarzycki
>>> > > > > > > > > > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
>>> > > > > > > > > > > >> >> > > >
>>> > > > > > > > > > > >> >> > >
>>> > > > > > > > > > > >> >> > >
>>> > > > > > > > > > > >> >> > > --
>>> > > > > > > > > > > >> >> > > Carlos Rovira
>>> > > > > > > > > > > >> >> > > http://about.me/carlosrovira
>>> > > > > > > > > > > >> >> > >
>>> > > > > > > > > > > >> >> >
>>> > > > > > > > > > > >> >> >
>>> > > > > > > > > > > >> >> > --
>>> > > > > > > > > > > >> >> >
>>> > > > > > > > > > > >> >> > Piotr Zarzycki
>>> > > > > > > > > > > >> >> >
>>> > > > > > > > > > > >> >> > Patreon: *
>>> https://www.patreon.com/piotrzarzycki
>>> > > > > > > > > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
>>> > > > > > > > > > > >> >> >
>>> > > > > > > > > > > >> >>
>>> > > > > > > > > > > >> >>
>>> > > > > > > > > > > >> >> --
>>> > > > > > > > > > > >> >> Carlos Rovira
>>> > > > > > > > > > > >> >> http://about.me/carlosrovira
>>> > > > > > > > > > > >> >>
>>> > > > > > > > > > > >> >
>>> > > > > > > > > > > >> >
>>> > > > > > > > > > > >> > --
>>> > > > > > > > > > > >> >
>>> > > > > > > > > > > >> > Piotr Zarzycki
>>> > > > > > > > > > > >> >
>>> > > > > > > > > > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > > > > > > > > > > >> > <https://www.patreon.com/piotrzarzycki>*
>>> > > > > > > > > > > >> >
>>> > > > > > > > > > > >>
>>> > > > > > > > > > > >>
>>> > > > > > > > > > > >> --
>>> > > > > > > > > > > >>
>>> > > > > > > > > > > >> Piotr Zarzycki
>>> > > > > > > > > > > >>
>>> > > > > > > > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
>>> > > > > > > > > > > >> <https://www.patreon.com/piotrzarzycki>*
>>> > > > > > > > > > > >>
>>> > > > > > > > > > > >
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > --
>>> > > > > > > > > > > > Carlos Rovira
>>> > > > > > > > > > > > http://about.me/carlosrovira
>>> > > > > > > > > > > >
>>> > > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > > --
>>> > > > > > > > > > > Carlos Rovira
>>> > > > > > > > > > > http://about.me/carlosrovira
>>> > > > > > > > > > >
>>> > > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > > --
>>> > > > > > > > > Carlos Rovira
>>> > > > > > > > > http://about.me/carlosrovira
>>> > > > > > > > >
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > > > --
>>> > > > > > > >
>>> > > > > > > > Piotr Zarzycki
>>> > > > > > > >
>>> > > > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > > > > > > > <https://www.patreon.com/piotrzarzycki>*
>>> > > > > > > >
>>> > > > > > >
>>> > > > > > >
>>> > > > > > > --
>>> > > > > > > Carlos Rovira
>>> > > > > > > http://about.me/carlosrovira
>>> > > > > > >
>>> > > > > >
>>> > > > > >
>>> > > > > > --
>>> > > > > >
>>> > > > > > Piotr Zarzycki
>>> > > > > >
>>> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > > > > > <https://www.patreon.com/piotrzarzycki>*
>>> > > > > >
>>> > > > >
>>> > > > >
>>> > > > > --
>>> > > > > Carlos Rovira
>>> > > > > http://about.me/carlosrovira
>>> > > > >
>>> > > >
>>> > > >
>>> > > > --
>>> > > >
>>> > > > Piotr Zarzycki
>>> > > >
>>> > > > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > > > <https://www.patreon.com/piotrzarzycki>*
>>> > > >
>>> > >
>>> > >
>>> > > --
>>> > > Carlos Rovira
>>> > > http://about.me/carlosrovira
>>> > >
>>> >
>>> >
>>> > --
>>> >
>>> > Piotr Zarzycki
>>> >
>>> > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > <https://www.patreon.com/piotrzarzycki>*
>>> >
>>>
>>>
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

Remember I'm talking above only about contentArea of FormItem.

sob., 26 sty 2019 o 12:57 Piotr Zarzycki <pi...@gmail.com>
napisał(a):

> Carlos,
>
> I think I got it. It looks like we don't need IFormItemLayout as you said,
> cause I should be able to manipulate content of my FormItem by doing that:
>
> IBeadLayout:
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> IFormItemContentArea: ClassReference("org.apache.royale.jewel.HGroup");
>
> However above code won't work cause you have this [1] - transferLayoutBead
> is being added to contentArea you have now in output code for content area
> something weird. [2]
>
> To me IBeadLayout - shouldn't be transfered to content - Are you agree ?
>
> [1] https://paste.apache.org/m9ST
> [2] https://paste.apache.org/9Orx
>
> Thanks,
> Piotr
>
>
> sob., 26 sty 2019 o 12:18 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
>> Piotr, I think I don't think we need and IFormItemLayout.
>> IBeadLayout seems sufficient for me, since that layout will be based just
>> on css selectors that are in the end what solves the layout
>>
>> El sáb., 26 ene. 2019 a las 12:00, Piotr Zarzycki (<
>> piotrzarzycki21@gmail.com>) escribió:
>>
>> > Too bad that you didn't understand me. Just question to above
>> requirements
>> > - What in your opinion should do layout added trough ->
>> *IFormItemLayout
>> > ?*
>> >
>> > sob., 26 sty 2019 o 11:54 Carlos Rovira <ca...@apache.org>
>> > napisał(a):
>> >
>> > > Hi Piotr,
>> > >
>> > > Don't think if I understand right your exposition. I'll try to write
>> in
>> > > words what I expect from a FormItemLayout and let me know if we're
>> > thinking
>> > > on the same.
>> > >
>> > > We want to have a specialized layout for FormItem that support
>> horizontal
>> > > and stacked form item layouts. At this point we can choose to have 2
>> > > layouts or only 1.
>> > > Since we always have 2, maybe that's the best way to go :
>> > > HorizontalFormItemLayout and VerticalFormItemLayout.
>> > >
>> > > HorizontalFormItemLayout: should put label, required indicator and
>> > content
>> > > in the same "row", o mostly as HorizontalLayout does, and will be
>> equal
>> > to
>> > > what we have now.
>> > >
>> > > VerticalFormItemLayout should put Label followed by requiredIndicator
>> in
>> > a
>> > > row and just below, the content part. *Or* Label in a row and below
>> > Content
>> > > followed by requited Indicator
>> > > (I think this should be configurable in some way, or implement a case
>> and
>> > > made and additional layout for the other, so we can have both).
>> > >
>> > > Some technical needs:
>> > >
>> > > * All we'll be solved using CSS and css class selectors as with the
>> rest
>> > of
>> > > Jewel Layouts and phyloshopy
>> > > * We'll continue using flexbox since is the standard in Jewel
>> > > * We can use the flexbox order to have a property that puts content
>> > before
>> > > required indicator or viceversa using a property in the layout.
>> > > * I think FormItemView would need to adapt to this, and maybe will
>> need
>> > two
>> > > Views to support each layout (don't have clear now)
>> > >
>> > >
>> > >
>> > >
>> > > El vie., 25 ene. 2019 a las 16:23, Piotr Zarzycki (<
>> > > piotrzarzycki21@gmail.com>) escribió:
>> > >
>> > > > I won't follow Flex, so if you would like to do this I'm fine. I'm
>> > going
>> > > to
>> > > > implement my own View in my application. I won't commit it to
>> Royale.
>> > > > However I would like to fix issue with layout. Currently
>> IBeadLayout -
>> > Is
>> > > > making whole FormItem vertical or horizontal. *IFormItemLayout -
>> Should
>> > > > treat content appropriately, but it doesn't do anything. I would
>> like
>> > to
>> > > > change it in the following way:*
>> > > >
>> > > > *IBeadLayout do:*
>> > > >
>> > > > *1) When user: IBeadLayout:
>> > > >
>> > ClassReference("org.apache.royale.jewel.beads.layouts.VerticalLayout");*
>> > > > L
>> > > > C
>> > > > *2) When user: **IBeadLayout:
>> > > >
>> > >
>> >
>> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");*
>> > > > *L C*
>> > > >
>> > > > *IFormItemLayout will do:*
>> > > > 1) IFormItemLayout:
>> > > >
>> >
>> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
>> > > > and #1 - *IBeadLayout*
>> > > > L
>> > > > C - Set children Horizotnally
>> > > > 2) IFormItemLayout:
>> > > >
>> >
>> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
>> > > > and #2 - *IBeadLayout*
>> > > > *L*
>> > > > *C - Set children Vertically*
>> > > >
>> > > > *Thoughts ?*
>> > > >
>> > > > Piotr
>> > > >
>> > > >
>> > > >
>> > > > pt., 25 sty 2019 o 16:13 Carlos Rovira <ca...@apache.org>
>> > > > napisał(a):
>> > > >
>> > > > > Ops!,
>> > > > >
>> > > > > ok, since I was using the other layout I was in the believe that
>> was
>> > > the
>> > > > > standard. So if we want to follow flex, we can change the current
>> as
>> > > > well.
>> > > > >
>> > > > > El jue., 24 ene. 2019 a las 18:34, Piotr Zarzycki (<
>> > > > > piotrzarzycki21@gmail.com>) escribió:
>> > > > >
>> > > > > > Nope - I just checked [1] - Code [2] - You are showing me some
>> > custom
>> > > > > > implementation.
>> > > > > >
>> > > > > > [1] https://imgur.com/INKlfcC
>> > > > > > [2] https://paste.apache.org/jyrl
>> > > > > >
>> > > > > > czw., 24 sty 2019 o 18:20 Carlos Rovira <
>> carlosrovira@apache.org>
>> > > > > > napisał(a):
>> > > > > >
>> > > > > > > Piotr,
>> > > > > > >
>> > > > > > > in Flex we have the same align (as we have now in Royale),
>> check
>> > > this
>> > > > > > > image: url
>> > > > > > > <
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249
>> > > > > > > >
>> > > > > > >
>> > > > > > > El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
>> > > > > > > piotrzarzycki21@gmail.com>) escribió:
>> > > > > > >
>> > > > > > > > If we are going in that direction it requires as well work
>> were
>> > > > > > indicator
>> > > > > > > > in case of L* C (current implementation) will be changed to
>> L
>> > C*
>> > > -
>> > > > > Yes
>> > > > > > ?
>> > > > > > > -
>> > > > > > > > Being consistent it should be like that.
>> > > > > > > >
>> > > > > > > > I'm not sure what the trends are in that case.
>> > > > > > > >
>> > > > > > > > czw., 24 sty 2019 o 17:51 Carlos Rovira <
>> > carlosrovira@apache.org
>> > > >
>> > > > > > > > napisał(a):
>> > > > > > > >
>> > > > > > > > > Hi Piotr,
>> > > > > > > > >
>> > > > > > > > > since is what you show in the flex version.
>> > > > > > > > > I think Adobe put side to content instead of side to label
>> > > since
>> > > > > the
>> > > > > > > user
>> > > > > > > > > fill the content elements and if not filled and required ,
>> > the
>> > > > > > tooltip
>> > > > > > > > > should popup there.
>> > > > > > > > > IOW, for usability, seems more appropriated the way flex
>> > > > layedout,
>> > > > > or
>> > > > > > > > seems
>> > > > > > > > > more natural.
>> > > > > > > > >
>> > > > > > > > > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
>> > > > > > > > > piotrzarzycki21@gmail.com>) escribió:
>> > > > > > > > >
>> > > > > > > > > > Carlos,
>> > > > > > > > > >
>> > > > > > > > > > Why you are proposing have that?
>> > > > > > > > > >
>> > > > > > > > > > L
>> > > > > > > > > > C *
>> > > > > > > > > >
>> > > > > > > > > > I'm in favor of staying
>> > > > > > > > > >
>> > > > > > > > > > L *
>> > > > > > > > > > C
>> > > > > > > > > >
>> > > > > > > > > > Thanks,
>> > > > > > > > > > Piotr
>> > > > > > > > > >
>> > > > > > > > > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <
>> > > > > > carlosrovira@apache.org
>> > > > > > > >
>> > > > > > > > > > wrote:
>> > > > > > > > > >
>> > > > > > > > > > > I forgot to mention about IBeadLayout more, since it
>> > could
>> > > be
>> > > > > > > > > > > misinterpreted:
>> > > > > > > > > > >
>> > > > > > > > > > > IBeadLayout for the global component is important, but
>> > what
>> > > > I'm
>> > > > > > > > > > considering
>> > > > > > > > > > > is that although we can put HorizontalLayout (for the
>> > > current
>> > > > > > > > > FormtItem)
>> > > > > > > > > > > and VerticalLayout (for the stacked), I'm seeing that
>> > many
>> > > > > > > components
>> > > > > > > > > > would
>> > > > > > > > > > > need its own layout class. In this case we could
>> create a
>> > > > > > > > > FormItemLayout,
>> > > > > > > > > > > and this will handle the layout vía CSS as it happens
>> > > mostly
>> > > > in
>> > > > > > > many
>> > > > > > > > > > other
>> > > > > > > > > > > Jewel component.
>> > > > > > > > > > >
>> > > > > > > > > > > (Just say that some of them are using an standard
>> layout
>> > > > class,
>> > > > > > > like
>> > > > > > > > > > > HorizontalLayout, or even a NullLayout class), since I
>> > > didn't
>> > > > > > have
>> > > > > > > > the
>> > > > > > > > > > time
>> > > > > > > > > > > to create its own one, and that's temporal. But my
>> plan
>> > is
>> > > to
>> > > > > > > create
>> > > > > > > > a
>> > > > > > > > > > > concrete layout for some of this components. FormItem
>> > could
>> > > > be
>> > > > > > one
>> > > > > > > of
>> > > > > > > > > > those
>> > > > > > > > > > > cases, for what we're seeing
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
>> > > > > > > > > > carlosrovira@apache.org
>> > > > > > > > > > > >)
>> > > > > > > > > > > escribió:
>> > > > > > > > > > >
>> > > > > > > > > > > > Hi Piotr,
>> > > > > > > > > > > >
>> > > > > > > > > > > > looking at the screen shot, seems the required
>> > indicator
>> > > is
>> > > > > > > > > positioned
>> > > > > > > > > > to
>> > > > > > > > > > > > the right side of the element, what seems coherent,
>> > > > although
>> > > > > > > could
>> > > > > > > > > be a
>> > > > > > > > > > > bit
>> > > > > > > > > > > > problematic depending on the width of the
>> component. we
>> > > > > assume
>> > > > > > a
>> > > > > > > > > fixed
>> > > > > > > > > > > > width (to the widest element) and align all required
>> > (or
>> > > > not
>> > > > > a
>> > > > > > > put
>> > > > > > > > > the
>> > > > > > > > > > > > required indicator just before the element, anyway
>> this
>> > > > seems
>> > > > > > > > > something
>> > > > > > > > > > > to
>> > > > > > > > > > > > be solved as we have some real implementation.
>> > > > > > > > > > > >
>> > > > > > > > > > > > In order to implement it:
>> > > > > > > > > > > >
>> > > > > > > > > > > > We have 3 parts:
>> > > > > > > > > > > > - L (this is the label)
>> > > > > > > > > > > > - * (this is the required indicator)
>> > > > > > > > > > > > - C (this is the element(s) that the user adds)
>> > > > > > > > > > > >
>> > > > > > > > > > > > * Actual FormItem is :
>> > > > > > > > > > > >
>> > > > > > > > > > > > L * C
>> > > > > > > > > > > >
>> > > > > > > > > > > > * We want for the new
>> > > > > > > > > > > >
>> > > > > > > > > > > > L
>> > > > > > > > > > > > C *
>> > > > > > > > > > > >
>> > > > > > > > > > > > So it seems to me that
>> > > > > > > > > > > >
>> > > > > > > > > > > > a) IBeadLayout: ClassReference(
>> > > > > > > > > > > >
>> > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
>> > > > > > > > > > > > Does not has much sense to me
>> > > > > > > > > > > >
>> > > > > > > > > > > > b) IFormItemLayout: ClassReference(
>> > > > > > > > > > > >
>> "org.apache.royale.jewel.beads.layouts.VerticalLayout")
>> > > > > > > > > > > >
>> > > > > > > > > > > > This is the one important to me (to configure), so
>> user
>> > > can
>> > > > > > > change
>> > > > > > > > > > layout
>> > > > > > > > > > > > of the content part
>> > > > > > > > > > > >
>> > > > > > > > > > > > c) IBeadView: ClassReference(
>> > > > > > > > > > > > "org.apache.royale.jewel.beads.views.FormItemView")
>> > > > > > > > > > > > IFormItemContentArea:
>> > > > > > > > ClassReference("org.apache.royale.jewel.Group")
>> > > > > > > > > > > >
>> > > > > > > > > > > > These are the parts important to me.
>> > > > > > > > > > > >
>> > > > > > > > > > > > I think we really want to change only the
>> IBeadView, so
>> > > we
>> > > > > can
>> > > > > > > > have a
>> > > > > > > > > > > > FormItemView and a StackedFormItemView, and could
>> > change
>> > > it
>> > > > > vía
>> > > > > > > > > > className
>> > > > > > > > > > > > (for example)
>> > > > > > > > > > > >
>> > > > > > > > > > > > Let me know your thought about it
>> > > > > > > > > > > >
>> > > > > > > > > > > > thanks
>> > > > > > > > > > > >
>> > > > > > > > > > > > Carlos
>> > > > > > > > > > > >
>> > > > > > > > > > > >
>> > > > > > > > > > > >
>> > > > > > > > > > > >
>> > > > > > > > > > > >
>> > > > > > > > > > > >
>> > > > > > > > > > > >
>> > > > > > > > > > > >
>> > > > > > > > > > > >
>> > > > > > > > > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
>> > > > > > > > > > > > piotrzarzycki21@gmail.com>) escribió:
>> > > > > > > > > > > >
>> > > > > > > > > > > >> Carlos,
>> > > > > > > > > > > >>
>> > > > > > > > > > > >> I have analyzed FormItem in Flex and here is how
>> it is
>> > > > done
>> > > > > > > there.
>> > > > > > > > > > > >> StackedFormItemSkin is using FormItemLayout which
>> is
>> > > > > > constrained
>> > > > > > > > > into
>> > > > > > > > > > 3
>> > > > > > > > > > > >> columns (sequenceCol, contentCol and helpCol) and 2
>> > > rows.
>> > > > > > [1][2]
>> > > > > > > > > > > >>
>> > > > > > > > > > > >> When you look into the screenshot [2] you may think
>> > that
>> > > > > > reuired
>> > > > > > > > > > > indicator
>> > > > > > > > > > > >> is part of the content, but it's not. It's not even
>> > part
>> > > > of
>> > > > > > the
>> > > > > > > > > layout
>> > > > > > > > > > > >> cause it has includeInLayout="false". [3]
>> > > > > > > > > > > >> In Royale we don't have concept that something
>> doesn't
>> > > > > belong
>> > > > > > to
>> > > > > > > > > > layout
>> > > > > > > > > > > >> and
>> > > > > > > > > > > >> is not calculated and indicator default is being
>> > placed
>> > > in
>> > > > > > > > different
>> > > > > > > > > > > area.
>> > > > > > > > > > > >> Do you have some idea apart what I have proposed
>> how
>> > to
>> > > > > > resolve
>> > > > > > > > > that ?
>> > > > > > > > > > > >>
>> > > > > > > > > > > >> [1] https://paste.apache.org/9Imj
>> > > > > > > > > > > >> [2] https://imgur.com/GGOtzEU
>> > > > > > > > > > > >> [3] https://paste.apache.org/kqlP
>> > > > > > > > > > > >>
>> > > > > > > > > > > >> Thanks,
>> > > > > > > > > > > >> Piotr
>> > > > > > > > > > > >>
>> > > > > > > > > > > >>
>> > > > > > > > > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
>> > > > > > > > piotrzarzycki21@gmail.com>
>> > > > > > > > > > > >> napisał(a):
>> > > > > > > > > > > >>
>> > > > > > > > > > > >> > That's more clear to me. I will check and get
>> back
>> > to
>> > > > you.
>> > > > > > > > > > > >> >
>> > > > > > > > > > > >> > Thank you!
>> > > > > > > > > > > >> >
>> > > > > > > > > > > >> >
>> > > > > > > > > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <
>> > > > > > > carlosrovira@apache.org
>> > > > > > > > >
>> > > > > > > > > > > >> > napisał(a):
>> > > > > > > > > > > >> >
>> > > > > > > > > > > >> >> No,
>> > > > > > > > > > > >> >>
>> > > > > > > > > > > >> >> I was asking you about how flex solves visualy
>> the
>> > > > > problem
>> > > > > > in
>> > > > > > > > > their
>> > > > > > > > > > > >> >> stacked
>> > > > > > > > > > > >> >> version. The required icon is setup next to the
>> > > label?
>> > > > is
>> > > > > > in
>> > > > > > > > > other
>> > > > > > > > > > > >> place?
>> > > > > > > > > > > >> >> if we had an image of how it is designed (and
>> like
>> > > it),
>> > > > > we
>> > > > > > > can
>> > > > > > > > > copy
>> > > > > > > > > > > >> it. I
>> > > > > > > > > > > >> >> still not proposing a technical solution. Just
>> > that I
>> > > > > don't
>> > > > > > > > have
>> > > > > > > > > > > clear
>> > > > > > > > > > > >> how
>> > > > > > > > > > > >> >> we should layout it
>> > > > > > > > > > > >> >>
>> > > > > > > > > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr
>> Zarzycki
>> > (<
>> > > > > > > > > > > >> >> piotrzarzycki21@gmail.com>) escribió:
>> > > > > > > > > > > >> >>
>> > > > > > > > > > > >> >> > Carlos,
>> > > > > > > > > > > >> >> >
>> > > > > > > > > > > >> >> > Your suggestion is to have new form item
>> > > > > > (StackedFormItem)
>> > > > > > > > with
>> > > > > > > > > > new
>> > > > > > > > > > > >> >> > StackedFormItemView - cause problem is inside
>> > > > > > FormitemView,
>> > > > > > > > not
>> > > > > > > > > > > >> inside
>> > > > > > > > > > > >> >> > layout itself. Current layout is doing what it
>> > > should
>> > > > > do
>> > > > > > -
>> > > > > > > > > apart
>> > > > > > > > > > of
>> > > > > > > > > > > >> the
>> > > > > > > > > > > >> >> > problem - it's making children to be
>> > > > > Horizontal/Vertical.
>> > > > > > > > > > > >> >> >
>> > > > > > > > > > > >> >> > If I'm correct what you are saying - that's
>> ok,
>> > but
>> > > > if
>> > > > > > you
>> > > > > > > > have
>> > > > > > > > > > had
>> > > > > > > > > > > >> >> > different idea by saying above let me know.
>> > > > > > > > > > > >> >> >
>> > > > > > > > > > > >> >> > Thanks, Piotr
>> > > > > > > > > > > >> >> >
>> > > > > > > > > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
>> > > > > > > > > carlosrovira@apache.org>
>> > > > > > > > > > > >> >> > napisał(a):
>> > > > > > > > > > > >> >> >
>> > > > > > > > > > > >> >> > > Ok, I understand now.
>> > > > > > > > > > > >> >> > >
>> > > > > > > > > > > >> >> > > In Flex I think we had that layout and was
>> > > > > > > > > > > >> called....StackedFormItem
>> > > > > > > > > > > >> >> or
>> > > > > > > > > > > >> >> > > something like that?
>> > > > > > > > > > > >> >> > > Could you check how Flex solve this? If we
>> > > continue
>> > > > > > > liking
>> > > > > > > > > the
>> > > > > > > > > > > way
>> > > > > > > > > > > >> >> > stacked
>> > > > > > > > > > > >> >> > > form layout in flex looks, we can do the
>> same
>> > for
>> > > > our
>> > > > > > > > Royale
>> > > > > > > > > > > >> version
>> > > > > > > > > > > >> >> > >
>> > > > > > > > > > > >> >> > >
>> > > > > > > > > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr
>> > Zarzycki
>> > > > (<
>> > > > > > > > > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
>> > > > > > > > > > > >> >> > >
>> > > > > > > > > > > >> >> > > > I'm not sure how Serkan is doing that on
>> > users
>> > > > > forum,
>> > > > > > > > but I
>> > > > > > > > > > see
>> > > > > > > > > > > >> all
>> > > > > > > > > > > >> >> > hist
>> > > > > > > > > > > >> >> > > > pasted images. Anyway here you go:
>> > > > > > > > > > > >> >> > > >
>> > > > > > > > > > > >> >> > > > What I wanted to achieve:
>> > > > > https://snag.gy/DmH7yk.jpg
>> > > > > > > > > > > >> >> > > > What I got from Jewel FormItem:
>> > > > > > > > https://snag.gy/Slfbt9.jpg
>> > > > > > > > > > > >> >> > > >
>> > > > > > > > > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
>> > > > > > > > > > > carlosrovira@apache.org>
>> > > > > > > > > > > >> >> > > > napisał(a):
>> > > > > > > > > > > >> >> > > >
>> > > > > > > > > > > >> >> > > > > Piotr,
>> > > > > > > > > > > >> >> > > > >
>> > > > > > > > > > > >> >> > > > > remember that images pasted in list are
>> not
>> > > > > shared,
>> > > > > > > you
>> > > > > > > > > > must
>> > > > > > > > > > > >> share
>> > > > > > > > > > > >> >> > with
>> > > > > > > > > > > >> >> > > > > some image service
>> > > > > > > > > > > >> >> > > > >
>> > > > > > > > > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr
>> > > > Zarzycki
>> > > > > > (<
>> > > > > > > > > > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
>> > > > > > > > > > > >> >> > > > >
>> > > > > > > > > > > >> >> > > > > > There is one more problem with Layout.
>> > > > > Currently
>> > > > > > > > > default
>> > > > > > > > > > in
>> > > > > > > > > > > >> >> > framework
>> > > > > > > > > > > >> >> > > > we
>> > > > > > > > > > > >> >> > > > > > have [1]. It means that:
>> > > > > > > > > > > >> >> > > > > >
>> > > > > > > > > > > >> >> > > > > > My content of FormItem will be
>> vertical
>> > and
>> > > > > > > > IBeadLayout
>> > > > > > > > > > is
>> > > > > > > > > > > >> >> > basically
>> > > > > > > > > > > >> >> > > > > > ignored at some point. If I specify
>> > beads -
>> > > > > > > > > > > HorizontalLayout
>> > > > > > > > > > > >> as
>> > > > > > > > > > > >> >> it
>> > > > > > > > > > > >> >> > is
>> > > > > > > > > > > >> >> > > > in
>> > > > > > > > > > > >> >> > > > > > above example it will be taken as a
>> > primary
>> > > > > and I
>> > > > > > > > have
>> > > > > > > > > my
>> > > > > > > > > > > >> >> content
>> > > > > > > > > > > >> >> > > > laying
>> > > > > > > > > > > >> >> > > > > > out horizontally. The question is -
>> what
>> > is
>> > > > for
>> > > > > > > > > > > >> >> IFormItemLayout in
>> > > > > > > > > > > >> >> > > > > > default.css? Is it a bug?
>> > > > > > > > > > > >> >> > > > > >
>> > > > > > > > > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
>> > > > > > > > > > > >> >> > > > > >
>> > > > > > > > > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr
>> Zarzycki <
>> > > > > > > > > > > >> >> piotrzarzycki21@gmail.com
>> > > > > > > > > > > >> >> > >
>> > > > > > > > > > > >> >> > > > > > napisał(a):
>> > > > > > > > > > > >> >> > > > > >
>> > > > > > > > > > > >> >> > > > > >> Hi Carlos,
>> > > > > > > > > > > >> >> > > > > >>
>> > > > > > > > > > > >> >> > > > > >> I'm was trying to change FormItem to
>> be
>> > > > > Vertical
>> > > > > > > > > > oriented.
>> > > > > > > > > > > >> In
>> > > > > > > > > > > >> >> > > general
>> > > > > > > > > > > >> >> > > > I
>> > > > > > > > > > > >> >> > > > > >> would like to have following view.
>> Label
>> > > of
>> > > > > > > FormItem
>> > > > > > > > > is
>> > > > > > > > > > on
>> > > > > > > > > > > >> the
>> > > > > > > > > > > >> >> top
>> > > > > > > > > > > >> >> > > and
>> > > > > > > > > > > >> >> > > > > in
>> > > > > > > > > > > >> >> > > > > >> the bottom is content.
>> > > > > > > > > > > >> >> > > > > >>
>> > > > > > > > > > > >> >> > > > > >> [image: image.png]
>> > > > > > > > > > > >> >> > > > > >>
>> > > > > > > > > > > >> >> > > > > >> Code for that will looks like that
>> [1].
>> > > > > Results
>> > > > > > is
>> > > > > > > > > > > >> following:
>> > > > > > > > > > > >> >> > > > > >>
>> > > > > > > > > > > >> >> > > > > >> [image: image.png]
>> > > > > > > > > > > >> >> > > > > >>
>> > > > > > > > > > > >> >> > > > > >> It happened cause Label and required
>> > star
>> > > > > label
>> > > > > > > are
>> > > > > > > > > > > >> different
>> > > > > > > > > > > >> >> > > > components
>> > > > > > > > > > > >> >> > > > > >> - everything is being laying out
>> > > vertically.
>> > > > > > What
>> > > > > > > is
>> > > > > > > > > > your
>> > > > > > > > > > > >> >> > suggestion
>> > > > > > > > > > > >> >> > > > to
>> > > > > > > > > > > >> >> > > > > fix
>> > > > > > > > > > > >> >> > > > > >> that ?
>> > > > > > > > > > > >> >> > > > > >>
>> > > > > > > > > > > >> >> > > > > >> Mine is wrapping "First name" and "*"
>> > into
>> > > > one
>> > > > > > > Group
>> > > > > > > > > > with
>> > > > > > > > > > > >> >> > > > > >> HorizontalLayout.
>> > > > > > > > > > > >> >> > > > > >>
>> > > > > > > > > > > >> >> > > > > >> More thoughts are welcome. I hope you
>> > see
>> > > > > > > > screenshots.
>> > > > > > > > > > :)
>> > > > > > > > > > > >> >> > > > > >>
>> > > > > > > > > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
>> > > > > > > > > > > >> >> > > > > >>
>> > > > > > > > > > > >> >> > > > > >> Thanks,
>> > > > > > > > > > > >> >> > > > > >> --
>> > > > > > > > > > > >> >> > > > > >>
>> > > > > > > > > > > >> >> > > > > >> Piotr Zarzycki
>> > > > > > > > > > > >> >> > > > > >>
>> > > > > > > > > > > >> >> > > > > >> Patreon: *
>> > > > > https://www.patreon.com/piotrzarzycki
>> > > > > > > > > > > >> >> > > > > >> <
>> https://www.patreon.com/piotrzarzycki
>> > >*
>> > > > > > > > > > > >> >> > > > > >>
>> > > > > > > > > > > >> >> > > > > >
>> > > > > > > > > > > >> >> > > > > >
>> > > > > > > > > > > >> >> > > > > > --
>> > > > > > > > > > > >> >> > > > > >
>> > > > > > > > > > > >> >> > > > > > Piotr Zarzycki
>> > > > > > > > > > > >> >> > > > > >
>> > > > > > > > > > > >> >> > > > > > Patreon: *
>> > > > > https://www.patreon.com/piotrzarzycki
>> > > > > > > > > > > >> >> > > > > > <
>> https://www.patreon.com/piotrzarzycki>*
>> > > > > > > > > > > >> >> > > > > >
>> > > > > > > > > > > >> >> > > > >
>> > > > > > > > > > > >> >> > > > >
>> > > > > > > > > > > >> >> > > > > --
>> > > > > > > > > > > >> >> > > > > Carlos Rovira
>> > > > > > > > > > > >> >> > > > > http://about.me/carlosrovira
>> > > > > > > > > > > >> >> > > > >
>> > > > > > > > > > > >> >> > > >
>> > > > > > > > > > > >> >> > > >
>> > > > > > > > > > > >> >> > > > --
>> > > > > > > > > > > >> >> > > >
>> > > > > > > > > > > >> >> > > > Piotr Zarzycki
>> > > > > > > > > > > >> >> > > >
>> > > > > > > > > > > >> >> > > > Patreon: *
>> > > https://www.patreon.com/piotrzarzycki
>> > > > > > > > > > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
>> > > > > > > > > > > >> >> > > >
>> > > > > > > > > > > >> >> > >
>> > > > > > > > > > > >> >> > >
>> > > > > > > > > > > >> >> > > --
>> > > > > > > > > > > >> >> > > Carlos Rovira
>> > > > > > > > > > > >> >> > > http://about.me/carlosrovira
>> > > > > > > > > > > >> >> > >
>> > > > > > > > > > > >> >> >
>> > > > > > > > > > > >> >> >
>> > > > > > > > > > > >> >> > --
>> > > > > > > > > > > >> >> >
>> > > > > > > > > > > >> >> > Piotr Zarzycki
>> > > > > > > > > > > >> >> >
>> > > > > > > > > > > >> >> > Patreon: *
>> https://www.patreon.com/piotrzarzycki
>> > > > > > > > > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
>> > > > > > > > > > > >> >> >
>> > > > > > > > > > > >> >>
>> > > > > > > > > > > >> >>
>> > > > > > > > > > > >> >> --
>> > > > > > > > > > > >> >> Carlos Rovira
>> > > > > > > > > > > >> >> http://about.me/carlosrovira
>> > > > > > > > > > > >> >>
>> > > > > > > > > > > >> >
>> > > > > > > > > > > >> >
>> > > > > > > > > > > >> > --
>> > > > > > > > > > > >> >
>> > > > > > > > > > > >> > Piotr Zarzycki
>> > > > > > > > > > > >> >
>> > > > > > > > > > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
>> > > > > > > > > > > >> > <https://www.patreon.com/piotrzarzycki>*
>> > > > > > > > > > > >> >
>> > > > > > > > > > > >>
>> > > > > > > > > > > >>
>> > > > > > > > > > > >> --
>> > > > > > > > > > > >>
>> > > > > > > > > > > >> Piotr Zarzycki
>> > > > > > > > > > > >>
>> > > > > > > > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
>> > > > > > > > > > > >> <https://www.patreon.com/piotrzarzycki>*
>> > > > > > > > > > > >>
>> > > > > > > > > > > >
>> > > > > > > > > > > >
>> > > > > > > > > > > > --
>> > > > > > > > > > > > Carlos Rovira
>> > > > > > > > > > > > http://about.me/carlosrovira
>> > > > > > > > > > > >
>> > > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > --
>> > > > > > > > > > > Carlos Rovira
>> > > > > > > > > > > http://about.me/carlosrovira
>> > > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > --
>> > > > > > > > > Carlos Rovira
>> > > > > > > > > http://about.me/carlosrovira
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > --
>> > > > > > > >
>> > > > > > > > Piotr Zarzycki
>> > > > > > > >
>> > > > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
>> > > > > > > > <https://www.patreon.com/piotrzarzycki>*
>> > > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > --
>> > > > > > > Carlos Rovira
>> > > > > > > http://about.me/carlosrovira
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > > > --
>> > > > > >
>> > > > > > Piotr Zarzycki
>> > > > > >
>> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
>> > > > > > <https://www.patreon.com/piotrzarzycki>*
>> > > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Carlos Rovira
>> > > > > http://about.me/carlosrovira
>> > > > >
>> > > >
>> > > >
>> > > > --
>> > > >
>> > > > Piotr Zarzycki
>> > > >
>> > > > Patreon: *https://www.patreon.com/piotrzarzycki
>> > > > <https://www.patreon.com/piotrzarzycki>*
>> > > >
>> > >
>> > >
>> > > --
>> > > Carlos Rovira
>> > > http://about.me/carlosrovira
>> > >
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: *https://www.patreon.com/piotrzarzycki
>> > <https://www.patreon.com/piotrzarzycki>*
>> >
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

Carlos,

I think I got it. It looks like we don't need IFormItemLayout as you said,
cause I should be able to manipulate content of my FormItem by doing that:

IBeadLayout:
ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
IFormItemContentArea: ClassReference("org.apache.royale.jewel.HGroup");

However above code won't work cause you have this [1] - transferLayoutBead
is being added to contentArea you have now in output code for content area
something weird. [2]

To me IBeadLayout - shouldn't be transfered to content - Are you agree ?

[1] https://paste.apache.org/m9ST
[2] https://paste.apache.org/9Orx

Thanks,
Piotr


sob., 26 sty 2019 o 12:18 Carlos Rovira <ca...@apache.org>
napisał(a):

> Piotr, I think I don't think we need and IFormItemLayout.
> IBeadLayout seems sufficient for me, since that layout will be based just
> on css selectors that are in the end what solves the layout
>
> El sáb., 26 ene. 2019 a las 12:00, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > Too bad that you didn't understand me. Just question to above
> requirements
> > - What in your opinion should do layout added trough ->  *IFormItemLayout
> > ?*
> >
> > sob., 26 sty 2019 o 11:54 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > Don't think if I understand right your exposition. I'll try to write in
> > > words what I expect from a FormItemLayout and let me know if we're
> > thinking
> > > on the same.
> > >
> > > We want to have a specialized layout for FormItem that support
> horizontal
> > > and stacked form item layouts. At this point we can choose to have 2
> > > layouts or only 1.
> > > Since we always have 2, maybe that's the best way to go :
> > > HorizontalFormItemLayout and VerticalFormItemLayout.
> > >
> > > HorizontalFormItemLayout: should put label, required indicator and
> > content
> > > in the same "row", o mostly as HorizontalLayout does, and will be equal
> > to
> > > what we have now.
> > >
> > > VerticalFormItemLayout should put Label followed by requiredIndicator
> in
> > a
> > > row and just below, the content part. *Or* Label in a row and below
> > Content
> > > followed by requited Indicator
> > > (I think this should be configurable in some way, or implement a case
> and
> > > made and additional layout for the other, so we can have both).
> > >
> > > Some technical needs:
> > >
> > > * All we'll be solved using CSS and css class selectors as with the
> rest
> > of
> > > Jewel Layouts and phyloshopy
> > > * We'll continue using flexbox since is the standard in Jewel
> > > * We can use the flexbox order to have a property that puts content
> > before
> > > required indicator or viceversa using a property in the layout.
> > > * I think FormItemView would need to adapt to this, and maybe will need
> > two
> > > Views to support each layout (don't have clear now)
> > >
> > >
> > >
> > >
> > > El vie., 25 ene. 2019 a las 16:23, Piotr Zarzycki (<
> > > piotrzarzycki21@gmail.com>) escribió:
> > >
> > > > I won't follow Flex, so if you would like to do this I'm fine. I'm
> > going
> > > to
> > > > implement my own View in my application. I won't commit it to Royale.
> > > > However I would like to fix issue with layout. Currently IBeadLayout
> -
> > Is
> > > > making whole FormItem vertical or horizontal. *IFormItemLayout -
> Should
> > > > treat content appropriately, but it doesn't do anything. I would like
> > to
> > > > change it in the following way:*
> > > >
> > > > *IBeadLayout do:*
> > > >
> > > > *1) When user: IBeadLayout:
> > > >
> > ClassReference("org.apache.royale.jewel.beads.layouts.VerticalLayout");*
> > > > L
> > > > C
> > > > *2) When user: **IBeadLayout:
> > > >
> > >
> >
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");*
> > > > *L C*
> > > >
> > > > *IFormItemLayout will do:*
> > > > 1) IFormItemLayout:
> > > >
> > ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> > > > and #1 - *IBeadLayout*
> > > > L
> > > > C - Set children Horizotnally
> > > > 2) IFormItemLayout:
> > > >
> > ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> > > > and #2 - *IBeadLayout*
> > > > *L*
> > > > *C - Set children Vertically*
> > > >
> > > > *Thoughts ?*
> > > >
> > > > Piotr
> > > >
> > > >
> > > >
> > > > pt., 25 sty 2019 o 16:13 Carlos Rovira <ca...@apache.org>
> > > > napisał(a):
> > > >
> > > > > Ops!,
> > > > >
> > > > > ok, since I was using the other layout I was in the believe that
> was
> > > the
> > > > > standard. So if we want to follow flex, we can change the current
> as
> > > > well.
> > > > >
> > > > > El jue., 24 ene. 2019 a las 18:34, Piotr Zarzycki (<
> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > >
> > > > > > Nope - I just checked [1] - Code [2] - You are showing me some
> > custom
> > > > > > implementation.
> > > > > >
> > > > > > [1] https://imgur.com/INKlfcC
> > > > > > [2] https://paste.apache.org/jyrl
> > > > > >
> > > > > > czw., 24 sty 2019 o 18:20 Carlos Rovira <carlosrovira@apache.org
> >
> > > > > > napisał(a):
> > > > > >
> > > > > > > Piotr,
> > > > > > >
> > > > > > > in Flex we have the same align (as we have now in Royale),
> check
> > > this
> > > > > > > image: url
> > > > > > > <
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249
> > > > > > > >
> > > > > > >
> > > > > > > El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
> > > > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > >
> > > > > > > > If we are going in that direction it requires as well work
> were
> > > > > > indicator
> > > > > > > > in case of L* C (current implementation) will be changed to L
> > C*
> > > -
> > > > > Yes
> > > > > > ?
> > > > > > > -
> > > > > > > > Being consistent it should be like that.
> > > > > > > >
> > > > > > > > I'm not sure what the trends are in that case.
> > > > > > > >
> > > > > > > > czw., 24 sty 2019 o 17:51 Carlos Rovira <
> > carlosrovira@apache.org
> > > >
> > > > > > > > napisał(a):
> > > > > > > >
> > > > > > > > > Hi Piotr,
> > > > > > > > >
> > > > > > > > > since is what you show in the flex version.
> > > > > > > > > I think Adobe put side to content instead of side to label
> > > since
> > > > > the
> > > > > > > user
> > > > > > > > > fill the content elements and if not filled and required ,
> > the
> > > > > > tooltip
> > > > > > > > > should popup there.
> > > > > > > > > IOW, for usability, seems more appropriated the way flex
> > > > layedout,
> > > > > or
> > > > > > > > seems
> > > > > > > > > more natural.
> > > > > > > > >
> > > > > > > > > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
> > > > > > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > >
> > > > > > > > > > Carlos,
> > > > > > > > > >
> > > > > > > > > > Why you are proposing have that?
> > > > > > > > > >
> > > > > > > > > > L
> > > > > > > > > > C *
> > > > > > > > > >
> > > > > > > > > > I'm in favor of staying
> > > > > > > > > >
> > > > > > > > > > L *
> > > > > > > > > > C
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > > Piotr
> > > > > > > > > >
> > > > > > > > > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <
> > > > > > carlosrovira@apache.org
> > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > I forgot to mention about IBeadLayout more, since it
> > could
> > > be
> > > > > > > > > > > misinterpreted:
> > > > > > > > > > >
> > > > > > > > > > > IBeadLayout for the global component is important, but
> > what
> > > > I'm
> > > > > > > > > > considering
> > > > > > > > > > > is that although we can put HorizontalLayout (for the
> > > current
> > > > > > > > > FormtItem)
> > > > > > > > > > > and VerticalLayout (for the stacked), I'm seeing that
> > many
> > > > > > > components
> > > > > > > > > > would
> > > > > > > > > > > need its own layout class. In this case we could
> create a
> > > > > > > > > FormItemLayout,
> > > > > > > > > > > and this will handle the layout vía CSS as it happens
> > > mostly
> > > > in
> > > > > > > many
> > > > > > > > > > other
> > > > > > > > > > > Jewel component.
> > > > > > > > > > >
> > > > > > > > > > > (Just say that some of them are using an standard
> layout
> > > > class,
> > > > > > > like
> > > > > > > > > > > HorizontalLayout, or even a NullLayout class), since I
> > > didn't
> > > > > > have
> > > > > > > > the
> > > > > > > > > > time
> > > > > > > > > > > to create its own one, and that's temporal. But my plan
> > is
> > > to
> > > > > > > create
> > > > > > > > a
> > > > > > > > > > > concrete layout for some of this components. FormItem
> > could
> > > > be
> > > > > > one
> > > > > > > of
> > > > > > > > > > those
> > > > > > > > > > > cases, for what we're seeing
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
> > > > > > > > > > carlosrovira@apache.org
> > > > > > > > > > > >)
> > > > > > > > > > > escribió:
> > > > > > > > > > >
> > > > > > > > > > > > Hi Piotr,
> > > > > > > > > > > >
> > > > > > > > > > > > looking at the screen shot, seems the required
> > indicator
> > > is
> > > > > > > > > positioned
> > > > > > > > > > to
> > > > > > > > > > > > the right side of the element, what seems coherent,
> > > > although
> > > > > > > could
> > > > > > > > > be a
> > > > > > > > > > > bit
> > > > > > > > > > > > problematic depending on the width of the component.
> we
> > > > > assume
> > > > > > a
> > > > > > > > > fixed
> > > > > > > > > > > > width (to the widest element) and align all required
> > (or
> > > > not
> > > > > a
> > > > > > > put
> > > > > > > > > the
> > > > > > > > > > > > required indicator just before the element, anyway
> this
> > > > seems
> > > > > > > > > something
> > > > > > > > > > > to
> > > > > > > > > > > > be solved as we have some real implementation.
> > > > > > > > > > > >
> > > > > > > > > > > > In order to implement it:
> > > > > > > > > > > >
> > > > > > > > > > > > We have 3 parts:
> > > > > > > > > > > > - L (this is the label)
> > > > > > > > > > > > - * (this is the required indicator)
> > > > > > > > > > > > - C (this is the element(s) that the user adds)
> > > > > > > > > > > >
> > > > > > > > > > > > * Actual FormItem is :
> > > > > > > > > > > >
> > > > > > > > > > > > L * C
> > > > > > > > > > > >
> > > > > > > > > > > > * We want for the new
> > > > > > > > > > > >
> > > > > > > > > > > > L
> > > > > > > > > > > > C *
> > > > > > > > > > > >
> > > > > > > > > > > > So it seems to me that
> > > > > > > > > > > >
> > > > > > > > > > > > a) IBeadLayout: ClassReference(
> > > > > > > > > > > >
> > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> > > > > > > > > > > > Does not has much sense to me
> > > > > > > > > > > >
> > > > > > > > > > > > b) IFormItemLayout: ClassReference(
> > > > > > > > > > > >
> "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> > > > > > > > > > > >
> > > > > > > > > > > > This is the one important to me (to configure), so
> user
> > > can
> > > > > > > change
> > > > > > > > > > layout
> > > > > > > > > > > > of the content part
> > > > > > > > > > > >
> > > > > > > > > > > > c) IBeadView: ClassReference(
> > > > > > > > > > > > "org.apache.royale.jewel.beads.views.FormItemView")
> > > > > > > > > > > > IFormItemContentArea:
> > > > > > > > ClassReference("org.apache.royale.jewel.Group")
> > > > > > > > > > > >
> > > > > > > > > > > > These are the parts important to me.
> > > > > > > > > > > >
> > > > > > > > > > > > I think we really want to change only the IBeadView,
> so
> > > we
> > > > > can
> > > > > > > > have a
> > > > > > > > > > > > FormItemView and a StackedFormItemView, and could
> > change
> > > it
> > > > > vía
> > > > > > > > > > className
> > > > > > > > > > > > (for example)
> > > > > > > > > > > >
> > > > > > > > > > > > Let me know your thought about it
> > > > > > > > > > > >
> > > > > > > > > > > > thanks
> > > > > > > > > > > >
> > > > > > > > > > > > Carlos
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> > > > > > > > > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > > > > >
> > > > > > > > > > > >> Carlos,
> > > > > > > > > > > >>
> > > > > > > > > > > >> I have analyzed FormItem in Flex and here is how it
> is
> > > > done
> > > > > > > there.
> > > > > > > > > > > >> StackedFormItemSkin is using FormItemLayout which is
> > > > > > constrained
> > > > > > > > > into
> > > > > > > > > > 3
> > > > > > > > > > > >> columns (sequenceCol, contentCol and helpCol) and 2
> > > rows.
> > > > > > [1][2]
> > > > > > > > > > > >>
> > > > > > > > > > > >> When you look into the screenshot [2] you may think
> > that
> > > > > > reuired
> > > > > > > > > > > indicator
> > > > > > > > > > > >> is part of the content, but it's not. It's not even
> > part
> > > > of
> > > > > > the
> > > > > > > > > layout
> > > > > > > > > > > >> cause it has includeInLayout="false". [3]
> > > > > > > > > > > >> In Royale we don't have concept that something
> doesn't
> > > > > belong
> > > > > > to
> > > > > > > > > > layout
> > > > > > > > > > > >> and
> > > > > > > > > > > >> is not calculated and indicator default is being
> > placed
> > > in
> > > > > > > > different
> > > > > > > > > > > area.
> > > > > > > > > > > >> Do you have some idea apart what I have proposed how
> > to
> > > > > > resolve
> > > > > > > > > that ?
> > > > > > > > > > > >>
> > > > > > > > > > > >> [1] https://paste.apache.org/9Imj
> > > > > > > > > > > >> [2] https://imgur.com/GGOtzEU
> > > > > > > > > > > >> [3] https://paste.apache.org/kqlP
> > > > > > > > > > > >>
> > > > > > > > > > > >> Thanks,
> > > > > > > > > > > >> Piotr
> > > > > > > > > > > >>
> > > > > > > > > > > >>
> > > > > > > > > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
> > > > > > > > piotrzarzycki21@gmail.com>
> > > > > > > > > > > >> napisał(a):
> > > > > > > > > > > >>
> > > > > > > > > > > >> > That's more clear to me. I will check and get back
> > to
> > > > you.
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > Thank you!
> > > > > > > > > > > >> >
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <
> > > > > > > carlosrovira@apache.org
> > > > > > > > >
> > > > > > > > > > > >> > napisał(a):
> > > > > > > > > > > >> >
> > > > > > > > > > > >> >> No,
> > > > > > > > > > > >> >>
> > > > > > > > > > > >> >> I was asking you about how flex solves visualy
> the
> > > > > problem
> > > > > > in
> > > > > > > > > their
> > > > > > > > > > > >> >> stacked
> > > > > > > > > > > >> >> version. The required icon is setup next to the
> > > label?
> > > > is
> > > > > > in
> > > > > > > > > other
> > > > > > > > > > > >> place?
> > > > > > > > > > > >> >> if we had an image of how it is designed (and
> like
> > > it),
> > > > > we
> > > > > > > can
> > > > > > > > > copy
> > > > > > > > > > > >> it. I
> > > > > > > > > > > >> >> still not proposing a technical solution. Just
> > that I
> > > > > don't
> > > > > > > > have
> > > > > > > > > > > clear
> > > > > > > > > > > >> how
> > > > > > > > > > > >> >> we should layout it
> > > > > > > > > > > >> >>
> > > > > > > > > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki
> > (<
> > > > > > > > > > > >> >> piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > > > > >> >>
> > > > > > > > > > > >> >> > Carlos,
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> > Your suggestion is to have new form item
> > > > > > (StackedFormItem)
> > > > > > > > with
> > > > > > > > > > new
> > > > > > > > > > > >> >> > StackedFormItemView - cause problem is inside
> > > > > > FormitemView,
> > > > > > > > not
> > > > > > > > > > > >> inside
> > > > > > > > > > > >> >> > layout itself. Current layout is doing what it
> > > should
> > > > > do
> > > > > > -
> > > > > > > > > apart
> > > > > > > > > > of
> > > > > > > > > > > >> the
> > > > > > > > > > > >> >> > problem - it's making children to be
> > > > > Horizontal/Vertical.
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> > If I'm correct what you are saying - that's ok,
> > but
> > > > if
> > > > > > you
> > > > > > > > have
> > > > > > > > > > had
> > > > > > > > > > > >> >> > different idea by saying above let me know.
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> > Thanks, Piotr
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
> > > > > > > > > carlosrovira@apache.org>
> > > > > > > > > > > >> >> > napisał(a):
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> > > Ok, I understand now.
> > > > > > > > > > > >> >> > >
> > > > > > > > > > > >> >> > > In Flex I think we had that layout and was
> > > > > > > > > > > >> called....StackedFormItem
> > > > > > > > > > > >> >> or
> > > > > > > > > > > >> >> > > something like that?
> > > > > > > > > > > >> >> > > Could you check how Flex solve this? If we
> > > continue
> > > > > > > liking
> > > > > > > > > the
> > > > > > > > > > > way
> > > > > > > > > > > >> >> > stacked
> > > > > > > > > > > >> >> > > form layout in flex looks, we can do the same
> > for
> > > > our
> > > > > > > > Royale
> > > > > > > > > > > >> version
> > > > > > > > > > > >> >> > >
> > > > > > > > > > > >> >> > >
> > > > > > > > > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr
> > Zarzycki
> > > > (<
> > > > > > > > > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > > > > >> >> > >
> > > > > > > > > > > >> >> > > > I'm not sure how Serkan is doing that on
> > users
> > > > > forum,
> > > > > > > > but I
> > > > > > > > > > see
> > > > > > > > > > > >> all
> > > > > > > > > > > >> >> > hist
> > > > > > > > > > > >> >> > > > pasted images. Anyway here you go:
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > > > What I wanted to achieve:
> > > > > https://snag.gy/DmH7yk.jpg
> > > > > > > > > > > >> >> > > > What I got from Jewel FormItem:
> > > > > > > > https://snag.gy/Slfbt9.jpg
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
> > > > > > > > > > > carlosrovira@apache.org>
> > > > > > > > > > > >> >> > > > napisał(a):
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > > > > Piotr,
> > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > >> >> > > > > remember that images pasted in list are
> not
> > > > > shared,
> > > > > > > you
> > > > > > > > > > must
> > > > > > > > > > > >> share
> > > > > > > > > > > >> >> > with
> > > > > > > > > > > >> >> > > > > some image service
> > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr
> > > > Zarzycki
> > > > > > (<
> > > > > > > > > > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > >> >> > > > > > There is one more problem with Layout.
> > > > > Currently
> > > > > > > > > default
> > > > > > > > > > in
> > > > > > > > > > > >> >> > framework
> > > > > > > > > > > >> >> > > > we
> > > > > > > > > > > >> >> > > > > > have [1]. It means that:
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > > > My content of FormItem will be vertical
> > and
> > > > > > > > IBeadLayout
> > > > > > > > > > is
> > > > > > > > > > > >> >> > basically
> > > > > > > > > > > >> >> > > > > > ignored at some point. If I specify
> > beads -
> > > > > > > > > > > HorizontalLayout
> > > > > > > > > > > >> as
> > > > > > > > > > > >> >> it
> > > > > > > > > > > >> >> > is
> > > > > > > > > > > >> >> > > > in
> > > > > > > > > > > >> >> > > > > > above example it will be taken as a
> > primary
> > > > > and I
> > > > > > > > have
> > > > > > > > > my
> > > > > > > > > > > >> >> content
> > > > > > > > > > > >> >> > > > laying
> > > > > > > > > > > >> >> > > > > > out horizontally. The question is -
> what
> > is
> > > > for
> > > > > > > > > > > >> >> IFormItemLayout in
> > > > > > > > > > > >> >> > > > > > default.css? Is it a bug?
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr
> Zarzycki <
> > > > > > > > > > > >> >> piotrzarzycki21@gmail.com
> > > > > > > > > > > >> >> > >
> > > > > > > > > > > >> >> > > > > > napisał(a):
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > > >> Hi Carlos,
> > > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > > >> >> > > > > >> I'm was trying to change FormItem to
> be
> > > > > Vertical
> > > > > > > > > > oriented.
> > > > > > > > > > > >> In
> > > > > > > > > > > >> >> > > general
> > > > > > > > > > > >> >> > > > I
> > > > > > > > > > > >> >> > > > > >> would like to have following view.
> Label
> > > of
> > > > > > > FormItem
> > > > > > > > > is
> > > > > > > > > > on
> > > > > > > > > > > >> the
> > > > > > > > > > > >> >> top
> > > > > > > > > > > >> >> > > and
> > > > > > > > > > > >> >> > > > > in
> > > > > > > > > > > >> >> > > > > >> the bottom is content.
> > > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > > >> >> > > > > >> [image: image.png]
> > > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > > >> >> > > > > >> Code for that will looks like that
> [1].
> > > > > Results
> > > > > > is
> > > > > > > > > > > >> following:
> > > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > > >> >> > > > > >> [image: image.png]
> > > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > > >> >> > > > > >> It happened cause Label and required
> > star
> > > > > label
> > > > > > > are
> > > > > > > > > > > >> different
> > > > > > > > > > > >> >> > > > components
> > > > > > > > > > > >> >> > > > > >> - everything is being laying out
> > > vertically.
> > > > > > What
> > > > > > > is
> > > > > > > > > > your
> > > > > > > > > > > >> >> > suggestion
> > > > > > > > > > > >> >> > > > to
> > > > > > > > > > > >> >> > > > > fix
> > > > > > > > > > > >> >> > > > > >> that ?
> > > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > > >> >> > > > > >> Mine is wrapping "First name" and "*"
> > into
> > > > one
> > > > > > > Group
> > > > > > > > > > with
> > > > > > > > > > > >> >> > > > > >> HorizontalLayout.
> > > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > > >> >> > > > > >> More thoughts are welcome. I hope you
> > see
> > > > > > > > screenshots.
> > > > > > > > > > :)
> > > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
> > > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > > >> >> > > > > >> Thanks,
> > > > > > > > > > > >> >> > > > > >> --
> > > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > > >> >> > > > > >> Piotr Zarzycki
> > > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > > >> >> > > > > >> Patreon: *
> > > > > https://www.patreon.com/piotrzarzycki
> > > > > > > > > > > >> >> > > > > >> <
> https://www.patreon.com/piotrzarzycki
> > >*
> > > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > > > --
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > > > Piotr Zarzycki
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > > > Patreon: *
> > > > > https://www.patreon.com/piotrzarzycki
> > > > > > > > > > > >> >> > > > > > <https://www.patreon.com/piotrzarzycki
> >*
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > >> >> > > > > --
> > > > > > > > > > > >> >> > > > > Carlos Rovira
> > > > > > > > > > > >> >> > > > > http://about.me/carlosrovira
> > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > > > --
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > > > Piotr Zarzycki
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > > > Patreon: *
> > > https://www.patreon.com/piotrzarzycki
> > > > > > > > > > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > >
> > > > > > > > > > > >> >> > >
> > > > > > > > > > > >> >> > > --
> > > > > > > > > > > >> >> > > Carlos Rovira
> > > > > > > > > > > >> >> > > http://about.me/carlosrovira
> > > > > > > > > > > >> >> > >
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> > --
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> > Piotr Zarzycki
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> > Patreon: *
> https://www.patreon.com/piotrzarzycki
> > > > > > > > > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >>
> > > > > > > > > > > >> >>
> > > > > > > > > > > >> >> --
> > > > > > > > > > > >> >> Carlos Rovira
> > > > > > > > > > > >> >> http://about.me/carlosrovira
> > > > > > > > > > > >> >>
> > > > > > > > > > > >> >
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > --
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > Piotr Zarzycki
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > > > > > >> > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > > > >> >
> > > > > > > > > > > >>
> > > > > > > > > > > >>
> > > > > > > > > > > >> --
> > > > > > > > > > > >>
> > > > > > > > > > > >> Piotr Zarzycki
> > > > > > > > > > > >>
> > > > > > > > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > > > >>
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > Carlos Rovira
> > > > > > > > > > > > http://about.me/carlosrovira
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Carlos Rovira
> > > > > > > > > > > http://about.me/carlosrovira
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Carlos Rovira
> > > > > > > > > http://about.me/carlosrovira
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > > > Piotr Zarzycki
> > > > > > > >
> > > > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Carlos Rovira
> > > > > > > http://about.me/carlosrovira
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Piotr Zarzycki
> > > > > >
> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > <https://www.patreon.com/piotrzarzycki>*
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Carlos Rovira <ca...@apache.org>.

Piotr, I think I don't think we need and IFormItemLayout.
IBeadLayout seems sufficient for me, since that layout will be based just
on css selectors that are in the end what solves the layout

El sáb., 26 ene. 2019 a las 12:00, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> Too bad that you didn't understand me. Just question to above requirements
> - What in your opinion should do layout added trough ->  *IFormItemLayout
> ?*
>
> sob., 26 sty 2019 o 11:54 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Hi Piotr,
> >
> > Don't think if I understand right your exposition. I'll try to write in
> > words what I expect from a FormItemLayout and let me know if we're
> thinking
> > on the same.
> >
> > We want to have a specialized layout for FormItem that support horizontal
> > and stacked form item layouts. At this point we can choose to have 2
> > layouts or only 1.
> > Since we always have 2, maybe that's the best way to go :
> > HorizontalFormItemLayout and VerticalFormItemLayout.
> >
> > HorizontalFormItemLayout: should put label, required indicator and
> content
> > in the same "row", o mostly as HorizontalLayout does, and will be equal
> to
> > what we have now.
> >
> > VerticalFormItemLayout should put Label followed by requiredIndicator in
> a
> > row and just below, the content part. *Or* Label in a row and below
> Content
> > followed by requited Indicator
> > (I think this should be configurable in some way, or implement a case and
> > made and additional layout for the other, so we can have both).
> >
> > Some technical needs:
> >
> > * All we'll be solved using CSS and css class selectors as with the rest
> of
> > Jewel Layouts and phyloshopy
> > * We'll continue using flexbox since is the standard in Jewel
> > * We can use the flexbox order to have a property that puts content
> before
> > required indicator or viceversa using a property in the layout.
> > * I think FormItemView would need to adapt to this, and maybe will need
> two
> > Views to support each layout (don't have clear now)
> >
> >
> >
> >
> > El vie., 25 ene. 2019 a las 16:23, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> > > I won't follow Flex, so if you would like to do this I'm fine. I'm
> going
> > to
> > > implement my own View in my application. I won't commit it to Royale.
> > > However I would like to fix issue with layout. Currently IBeadLayout -
> Is
> > > making whole FormItem vertical or horizontal. *IFormItemLayout - Should
> > > treat content appropriately, but it doesn't do anything. I would like
> to
> > > change it in the following way:*
> > >
> > > *IBeadLayout do:*
> > >
> > > *1) When user: IBeadLayout:
> > >
> ClassReference("org.apache.royale.jewel.beads.layouts.VerticalLayout");*
> > > L
> > > C
> > > *2) When user: **IBeadLayout:
> > >
> >
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");*
> > > *L C*
> > >
> > > *IFormItemLayout will do:*
> > > 1) IFormItemLayout:
> > >
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> > > and #1 - *IBeadLayout*
> > > L
> > > C - Set children Horizotnally
> > > 2) IFormItemLayout:
> > >
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> > > and #2 - *IBeadLayout*
> > > *L*
> > > *C - Set children Vertically*
> > >
> > > *Thoughts ?*
> > >
> > > Piotr
> > >
> > >
> > >
> > > pt., 25 sty 2019 o 16:13 Carlos Rovira <ca...@apache.org>
> > > napisał(a):
> > >
> > > > Ops!,
> > > >
> > > > ok, since I was using the other layout I was in the believe that was
> > the
> > > > standard. So if we want to follow flex, we can change the current as
> > > well.
> > > >
> > > > El jue., 24 ene. 2019 a las 18:34, Piotr Zarzycki (<
> > > > piotrzarzycki21@gmail.com>) escribió:
> > > >
> > > > > Nope - I just checked [1] - Code [2] - You are showing me some
> custom
> > > > > implementation.
> > > > >
> > > > > [1] https://imgur.com/INKlfcC
> > > > > [2] https://paste.apache.org/jyrl
> > > > >
> > > > > czw., 24 sty 2019 o 18:20 Carlos Rovira <ca...@apache.org>
> > > > > napisał(a):
> > > > >
> > > > > > Piotr,
> > > > > >
> > > > > > in Flex we have the same align (as we have now in Royale), check
> > this
> > > > > > image: url
> > > > > > <
> > > > > >
> > > > >
> > > >
> > >
> >
> https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249
> > > > > > >
> > > > > >
> > > > > > El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
> > > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > >
> > > > > > > If we are going in that direction it requires as well work were
> > > > > indicator
> > > > > > > in case of L* C (current implementation) will be changed to L
> C*
> > -
> > > > Yes
> > > > > ?
> > > > > > -
> > > > > > > Being consistent it should be like that.
> > > > > > >
> > > > > > > I'm not sure what the trends are in that case.
> > > > > > >
> > > > > > > czw., 24 sty 2019 o 17:51 Carlos Rovira <
> carlosrovira@apache.org
> > >
> > > > > > > napisał(a):
> > > > > > >
> > > > > > > > Hi Piotr,
> > > > > > > >
> > > > > > > > since is what you show in the flex version.
> > > > > > > > I think Adobe put side to content instead of side to label
> > since
> > > > the
> > > > > > user
> > > > > > > > fill the content elements and if not filled and required ,
> the
> > > > > tooltip
> > > > > > > > should popup there.
> > > > > > > > IOW, for usability, seems more appropriated the way flex
> > > layedout,
> > > > or
> > > > > > > seems
> > > > > > > > more natural.
> > > > > > > >
> > > > > > > > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
> > > > > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > >
> > > > > > > > > Carlos,
> > > > > > > > >
> > > > > > > > > Why you are proposing have that?
> > > > > > > > >
> > > > > > > > > L
> > > > > > > > > C *
> > > > > > > > >
> > > > > > > > > I'm in favor of staying
> > > > > > > > >
> > > > > > > > > L *
> > > > > > > > > C
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Piotr
> > > > > > > > >
> > > > > > > > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <
> > > > > carlosrovira@apache.org
> > > > > > >
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > I forgot to mention about IBeadLayout more, since it
> could
> > be
> > > > > > > > > > misinterpreted:
> > > > > > > > > >
> > > > > > > > > > IBeadLayout for the global component is important, but
> what
> > > I'm
> > > > > > > > > considering
> > > > > > > > > > is that although we can put HorizontalLayout (for the
> > current
> > > > > > > > FormtItem)
> > > > > > > > > > and VerticalLayout (for the stacked), I'm seeing that
> many
> > > > > > components
> > > > > > > > > would
> > > > > > > > > > need its own layout class. In this case we could create a
> > > > > > > > FormItemLayout,
> > > > > > > > > > and this will handle the layout vía CSS as it happens
> > mostly
> > > in
> > > > > > many
> > > > > > > > > other
> > > > > > > > > > Jewel component.
> > > > > > > > > >
> > > > > > > > > > (Just say that some of them are using an standard layout
> > > class,
> > > > > > like
> > > > > > > > > > HorizontalLayout, or even a NullLayout class), since I
> > didn't
> > > > > have
> > > > > > > the
> > > > > > > > > time
> > > > > > > > > > to create its own one, and that's temporal. But my plan
> is
> > to
> > > > > > create
> > > > > > > a
> > > > > > > > > > concrete layout for some of this components. FormItem
> could
> > > be
> > > > > one
> > > > > > of
> > > > > > > > > those
> > > > > > > > > > cases, for what we're seeing
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
> > > > > > > > > carlosrovira@apache.org
> > > > > > > > > > >)
> > > > > > > > > > escribió:
> > > > > > > > > >
> > > > > > > > > > > Hi Piotr,
> > > > > > > > > > >
> > > > > > > > > > > looking at the screen shot, seems the required
> indicator
> > is
> > > > > > > > positioned
> > > > > > > > > to
> > > > > > > > > > > the right side of the element, what seems coherent,
> > > although
> > > > > > could
> > > > > > > > be a
> > > > > > > > > > bit
> > > > > > > > > > > problematic depending on the width of the component. we
> > > > assume
> > > > > a
> > > > > > > > fixed
> > > > > > > > > > > width (to the widest element) and align all required
> (or
> > > not
> > > > a
> > > > > > put
> > > > > > > > the
> > > > > > > > > > > required indicator just before the element, anyway this
> > > seems
> > > > > > > > something
> > > > > > > > > > to
> > > > > > > > > > > be solved as we have some real implementation.
> > > > > > > > > > >
> > > > > > > > > > > In order to implement it:
> > > > > > > > > > >
> > > > > > > > > > > We have 3 parts:
> > > > > > > > > > > - L (this is the label)
> > > > > > > > > > > - * (this is the required indicator)
> > > > > > > > > > > - C (this is the element(s) that the user adds)
> > > > > > > > > > >
> > > > > > > > > > > * Actual FormItem is :
> > > > > > > > > > >
> > > > > > > > > > > L * C
> > > > > > > > > > >
> > > > > > > > > > > * We want for the new
> > > > > > > > > > >
> > > > > > > > > > > L
> > > > > > > > > > > C *
> > > > > > > > > > >
> > > > > > > > > > > So it seems to me that
> > > > > > > > > > >
> > > > > > > > > > > a) IBeadLayout: ClassReference(
> > > > > > > > > > >
> "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> > > > > > > > > > > Does not has much sense to me
> > > > > > > > > > >
> > > > > > > > > > > b) IFormItemLayout: ClassReference(
> > > > > > > > > > > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> > > > > > > > > > >
> > > > > > > > > > > This is the one important to me (to configure), so user
> > can
> > > > > > change
> > > > > > > > > layout
> > > > > > > > > > > of the content part
> > > > > > > > > > >
> > > > > > > > > > > c) IBeadView: ClassReference(
> > > > > > > > > > > "org.apache.royale.jewel.beads.views.FormItemView")
> > > > > > > > > > > IFormItemContentArea:
> > > > > > > ClassReference("org.apache.royale.jewel.Group")
> > > > > > > > > > >
> > > > > > > > > > > These are the parts important to me.
> > > > > > > > > > >
> > > > > > > > > > > I think we really want to change only the IBeadView, so
> > we
> > > > can
> > > > > > > have a
> > > > > > > > > > > FormItemView and a StackedFormItemView, and could
> change
> > it
> > > > vía
> > > > > > > > > className
> > > > > > > > > > > (for example)
> > > > > > > > > > >
> > > > > > > > > > > Let me know your thought about it
> > > > > > > > > > >
> > > > > > > > > > > thanks
> > > > > > > > > > >
> > > > > > > > > > > Carlos
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> > > > > > > > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > > > >
> > > > > > > > > > >> Carlos,
> > > > > > > > > > >>
> > > > > > > > > > >> I have analyzed FormItem in Flex and here is how it is
> > > done
> > > > > > there.
> > > > > > > > > > >> StackedFormItemSkin is using FormItemLayout which is
> > > > > constrained
> > > > > > > > into
> > > > > > > > > 3
> > > > > > > > > > >> columns (sequenceCol, contentCol and helpCol) and 2
> > rows.
> > > > > [1][2]
> > > > > > > > > > >>
> > > > > > > > > > >> When you look into the screenshot [2] you may think
> that
> > > > > reuired
> > > > > > > > > > indicator
> > > > > > > > > > >> is part of the content, but it's not. It's not even
> part
> > > of
> > > > > the
> > > > > > > > layout
> > > > > > > > > > >> cause it has includeInLayout="false". [3]
> > > > > > > > > > >> In Royale we don't have concept that something doesn't
> > > > belong
> > > > > to
> > > > > > > > > layout
> > > > > > > > > > >> and
> > > > > > > > > > >> is not calculated and indicator default is being
> placed
> > in
> > > > > > > different
> > > > > > > > > > area.
> > > > > > > > > > >> Do you have some idea apart what I have proposed how
> to
> > > > > resolve
> > > > > > > > that ?
> > > > > > > > > > >>
> > > > > > > > > > >> [1] https://paste.apache.org/9Imj
> > > > > > > > > > >> [2] https://imgur.com/GGOtzEU
> > > > > > > > > > >> [3] https://paste.apache.org/kqlP
> > > > > > > > > > >>
> > > > > > > > > > >> Thanks,
> > > > > > > > > > >> Piotr
> > > > > > > > > > >>
> > > > > > > > > > >>
> > > > > > > > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
> > > > > > > piotrzarzycki21@gmail.com>
> > > > > > > > > > >> napisał(a):
> > > > > > > > > > >>
> > > > > > > > > > >> > That's more clear to me. I will check and get back
> to
> > > you.
> > > > > > > > > > >> >
> > > > > > > > > > >> > Thank you!
> > > > > > > > > > >> >
> > > > > > > > > > >> >
> > > > > > > > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <
> > > > > > carlosrovira@apache.org
> > > > > > > >
> > > > > > > > > > >> > napisał(a):
> > > > > > > > > > >> >
> > > > > > > > > > >> >> No,
> > > > > > > > > > >> >>
> > > > > > > > > > >> >> I was asking you about how flex solves visualy the
> > > > problem
> > > > > in
> > > > > > > > their
> > > > > > > > > > >> >> stacked
> > > > > > > > > > >> >> version. The required icon is setup next to the
> > label?
> > > is
> > > > > in
> > > > > > > > other
> > > > > > > > > > >> place?
> > > > > > > > > > >> >> if we had an image of how it is designed (and like
> > it),
> > > > we
> > > > > > can
> > > > > > > > copy
> > > > > > > > > > >> it. I
> > > > > > > > > > >> >> still not proposing a technical solution. Just
> that I
> > > > don't
> > > > > > > have
> > > > > > > > > > clear
> > > > > > > > > > >> how
> > > > > > > > > > >> >> we should layout it
> > > > > > > > > > >> >>
> > > > > > > > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki
> (<
> > > > > > > > > > >> >> piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > > > >> >>
> > > > > > > > > > >> >> > Carlos,
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> > Your suggestion is to have new form item
> > > > > (StackedFormItem)
> > > > > > > with
> > > > > > > > > new
> > > > > > > > > > >> >> > StackedFormItemView - cause problem is inside
> > > > > FormitemView,
> > > > > > > not
> > > > > > > > > > >> inside
> > > > > > > > > > >> >> > layout itself. Current layout is doing what it
> > should
> > > > do
> > > > > -
> > > > > > > > apart
> > > > > > > > > of
> > > > > > > > > > >> the
> > > > > > > > > > >> >> > problem - it's making children to be
> > > > Horizontal/Vertical.
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> > If I'm correct what you are saying - that's ok,
> but
> > > if
> > > > > you
> > > > > > > have
> > > > > > > > > had
> > > > > > > > > > >> >> > different idea by saying above let me know.
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> > Thanks, Piotr
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
> > > > > > > > carlosrovira@apache.org>
> > > > > > > > > > >> >> > napisał(a):
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> > > Ok, I understand now.
> > > > > > > > > > >> >> > >
> > > > > > > > > > >> >> > > In Flex I think we had that layout and was
> > > > > > > > > > >> called....StackedFormItem
> > > > > > > > > > >> >> or
> > > > > > > > > > >> >> > > something like that?
> > > > > > > > > > >> >> > > Could you check how Flex solve this? If we
> > continue
> > > > > > liking
> > > > > > > > the
> > > > > > > > > > way
> > > > > > > > > > >> >> > stacked
> > > > > > > > > > >> >> > > form layout in flex looks, we can do the same
> for
> > > our
> > > > > > > Royale
> > > > > > > > > > >> version
> > > > > > > > > > >> >> > >
> > > > > > > > > > >> >> > >
> > > > > > > > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr
> Zarzycki
> > > (<
> > > > > > > > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > > > >> >> > >
> > > > > > > > > > >> >> > > > I'm not sure how Serkan is doing that on
> users
> > > > forum,
> > > > > > > but I
> > > > > > > > > see
> > > > > > > > > > >> all
> > > > > > > > > > >> >> > hist
> > > > > > > > > > >> >> > > > pasted images. Anyway here you go:
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > > > What I wanted to achieve:
> > > > https://snag.gy/DmH7yk.jpg
> > > > > > > > > > >> >> > > > What I got from Jewel FormItem:
> > > > > > > https://snag.gy/Slfbt9.jpg
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
> > > > > > > > > > carlosrovira@apache.org>
> > > > > > > > > > >> >> > > > napisał(a):
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > > > > Piotr,
> > > > > > > > > > >> >> > > > >
> > > > > > > > > > >> >> > > > > remember that images pasted in list are not
> > > > shared,
> > > > > > you
> > > > > > > > > must
> > > > > > > > > > >> share
> > > > > > > > > > >> >> > with
> > > > > > > > > > >> >> > > > > some image service
> > > > > > > > > > >> >> > > > >
> > > > > > > > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr
> > > Zarzycki
> > > > > (<
> > > > > > > > > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > > > >> >> > > > >
> > > > > > > > > > >> >> > > > > > There is one more problem with Layout.
> > > > Currently
> > > > > > > > default
> > > > > > > > > in
> > > > > > > > > > >> >> > framework
> > > > > > > > > > >> >> > > > we
> > > > > > > > > > >> >> > > > > > have [1]. It means that:
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > > > My content of FormItem will be vertical
> and
> > > > > > > IBeadLayout
> > > > > > > > > is
> > > > > > > > > > >> >> > basically
> > > > > > > > > > >> >> > > > > > ignored at some point. If I specify
> beads -
> > > > > > > > > > HorizontalLayout
> > > > > > > > > > >> as
> > > > > > > > > > >> >> it
> > > > > > > > > > >> >> > is
> > > > > > > > > > >> >> > > > in
> > > > > > > > > > >> >> > > > > > above example it will be taken as a
> primary
> > > > and I
> > > > > > > have
> > > > > > > > my
> > > > > > > > > > >> >> content
> > > > > > > > > > >> >> > > > laying
> > > > > > > > > > >> >> > > > > > out horizontally. The question is - what
> is
> > > for
> > > > > > > > > > >> >> IFormItemLayout in
> > > > > > > > > > >> >> > > > > > default.css? Is it a bug?
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> > > > > > > > > > >> >> piotrzarzycki21@gmail.com
> > > > > > > > > > >> >> > >
> > > > > > > > > > >> >> > > > > > napisał(a):
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > > >> Hi Carlos,
> > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > >> >> > > > > >> I'm was trying to change FormItem to be
> > > > Vertical
> > > > > > > > > oriented.
> > > > > > > > > > >> In
> > > > > > > > > > >> >> > > general
> > > > > > > > > > >> >> > > > I
> > > > > > > > > > >> >> > > > > >> would like to have following view. Label
> > of
> > > > > > FormItem
> > > > > > > > is
> > > > > > > > > on
> > > > > > > > > > >> the
> > > > > > > > > > >> >> top
> > > > > > > > > > >> >> > > and
> > > > > > > > > > >> >> > > > > in
> > > > > > > > > > >> >> > > > > >> the bottom is content.
> > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > >> >> > > > > >> [image: image.png]
> > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > >> >> > > > > >> Code for that will looks like that [1].
> > > > Results
> > > > > is
> > > > > > > > > > >> following:
> > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > >> >> > > > > >> [image: image.png]
> > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > >> >> > > > > >> It happened cause Label and required
> star
> > > > label
> > > > > > are
> > > > > > > > > > >> different
> > > > > > > > > > >> >> > > > components
> > > > > > > > > > >> >> > > > > >> - everything is being laying out
> > vertically.
> > > > > What
> > > > > > is
> > > > > > > > > your
> > > > > > > > > > >> >> > suggestion
> > > > > > > > > > >> >> > > > to
> > > > > > > > > > >> >> > > > > fix
> > > > > > > > > > >> >> > > > > >> that ?
> > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > >> >> > > > > >> Mine is wrapping "First name" and "*"
> into
> > > one
> > > > > > Group
> > > > > > > > > with
> > > > > > > > > > >> >> > > > > >> HorizontalLayout.
> > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > >> >> > > > > >> More thoughts are welcome. I hope you
> see
> > > > > > > screenshots.
> > > > > > > > > :)
> > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
> > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > >> >> > > > > >> Thanks,
> > > > > > > > > > >> >> > > > > >> --
> > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > >> >> > > > > >> Piotr Zarzycki
> > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > >> >> > > > > >> Patreon: *
> > > > https://www.patreon.com/piotrzarzycki
> > > > > > > > > > >> >> > > > > >> <https://www.patreon.com/piotrzarzycki
> >*
> > > > > > > > > > >> >> > > > > >>
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > > > --
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > > > Piotr Zarzycki
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > > > Patreon: *
> > > > https://www.patreon.com/piotrzarzycki
> > > > > > > > > > >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > >
> > > > > > > > > > >> >> > > > >
> > > > > > > > > > >> >> > > > > --
> > > > > > > > > > >> >> > > > > Carlos Rovira
> > > > > > > > > > >> >> > > > > http://about.me/carlosrovira
> > > > > > > > > > >> >> > > > >
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > > > --
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > > > Piotr Zarzycki
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > > > Patreon: *
> > https://www.patreon.com/piotrzarzycki
> > > > > > > > > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > >
> > > > > > > > > > >> >> > >
> > > > > > > > > > >> >> > > --
> > > > > > > > > > >> >> > > Carlos Rovira
> > > > > > > > > > >> >> > > http://about.me/carlosrovira
> > > > > > > > > > >> >> > >
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> > --
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> > Piotr Zarzycki
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >>
> > > > > > > > > > >> >>
> > > > > > > > > > >> >> --
> > > > > > > > > > >> >> Carlos Rovira
> > > > > > > > > > >> >> http://about.me/carlosrovira
> > > > > > > > > > >> >>
> > > > > > > > > > >> >
> > > > > > > > > > >> >
> > > > > > > > > > >> > --
> > > > > > > > > > >> >
> > > > > > > > > > >> > Piotr Zarzycki
> > > > > > > > > > >> >
> > > > > > > > > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > > > > >> > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > > >> >
> > > > > > > > > > >>
> > > > > > > > > > >>
> > > > > > > > > > >> --
> > > > > > > > > > >>
> > > > > > > > > > >> Piotr Zarzycki
> > > > > > > > > > >>
> > > > > > > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > > >>
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Carlos Rovira
> > > > > > > > > > > http://about.me/carlosrovira
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Carlos Rovira
> > > > > > > > > > http://about.me/carlosrovira
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Carlos Rovira
> > > > > > > > http://about.me/carlosrovira
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > Piotr Zarzycki
> > > > > > >
> > > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Carlos Rovira
> > > > > > http://about.me/carlosrovira
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Piotr Zarzycki
> > > > >
> > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > >
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

Too bad that you didn't understand me. Just question to above requirements
- What in your opinion should do layout added trough ->  *IFormItemLayout ?*

sob., 26 sty 2019 o 11:54 Carlos Rovira <ca...@apache.org>
napisał(a):

> Hi Piotr,
>
> Don't think if I understand right your exposition. I'll try to write in
> words what I expect from a FormItemLayout and let me know if we're thinking
> on the same.
>
> We want to have a specialized layout for FormItem that support horizontal
> and stacked form item layouts. At this point we can choose to have 2
> layouts or only 1.
> Since we always have 2, maybe that's the best way to go :
> HorizontalFormItemLayout and VerticalFormItemLayout.
>
> HorizontalFormItemLayout: should put label, required indicator and content
> in the same "row", o mostly as HorizontalLayout does, and will be equal to
> what we have now.
>
> VerticalFormItemLayout should put Label followed by requiredIndicator in a
> row and just below, the content part. *Or* Label in a row and below Content
> followed by requited Indicator
> (I think this should be configurable in some way, or implement a case and
> made and additional layout for the other, so we can have both).
>
> Some technical needs:
>
> * All we'll be solved using CSS and css class selectors as with the rest of
> Jewel Layouts and phyloshopy
> * We'll continue using flexbox since is the standard in Jewel
> * We can use the flexbox order to have a property that puts content before
> required indicator or viceversa using a property in the layout.
> * I think FormItemView would need to adapt to this, and maybe will need two
> Views to support each layout (don't have clear now)
>
>
>
>
> El vie., 25 ene. 2019 a las 16:23, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > I won't follow Flex, so if you would like to do this I'm fine. I'm going
> to
> > implement my own View in my application. I won't commit it to Royale.
> > However I would like to fix issue with layout. Currently IBeadLayout - Is
> > making whole FormItem vertical or horizontal. *IFormItemLayout - Should
> > treat content appropriately, but it doesn't do anything. I would like to
> > change it in the following way:*
> >
> > *IBeadLayout do:*
> >
> > *1) When user: IBeadLayout:
> > ClassReference("org.apache.royale.jewel.beads.layouts.VerticalLayout");*
> > L
> > C
> > *2) When user: **IBeadLayout:
> >
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");*
> > *L C*
> >
> > *IFormItemLayout will do:*
> > 1) IFormItemLayout:
> > ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> > and #1 - *IBeadLayout*
> > L
> > C - Set children Horizotnally
> > 2) IFormItemLayout:
> > ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> > and #2 - *IBeadLayout*
> > *L*
> > *C - Set children Vertically*
> >
> > *Thoughts ?*
> >
> > Piotr
> >
> >
> >
> > pt., 25 sty 2019 o 16:13 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> > > Ops!,
> > >
> > > ok, since I was using the other layout I was in the believe that was
> the
> > > standard. So if we want to follow flex, we can change the current as
> > well.
> > >
> > > El jue., 24 ene. 2019 a las 18:34, Piotr Zarzycki (<
> > > piotrzarzycki21@gmail.com>) escribió:
> > >
> > > > Nope - I just checked [1] - Code [2] - You are showing me some custom
> > > > implementation.
> > > >
> > > > [1] https://imgur.com/INKlfcC
> > > > [2] https://paste.apache.org/jyrl
> > > >
> > > > czw., 24 sty 2019 o 18:20 Carlos Rovira <ca...@apache.org>
> > > > napisał(a):
> > > >
> > > > > Piotr,
> > > > >
> > > > > in Flex we have the same align (as we have now in Royale), check
> this
> > > > > image: url
> > > > > <
> > > > >
> > > >
> > >
> >
> https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249
> > > > > >
> > > > >
> > > > > El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > >
> > > > > > If we are going in that direction it requires as well work were
> > > > indicator
> > > > > > in case of L* C (current implementation) will be changed to L C*
> -
> > > Yes
> > > > ?
> > > > > -
> > > > > > Being consistent it should be like that.
> > > > > >
> > > > > > I'm not sure what the trends are in that case.
> > > > > >
> > > > > > czw., 24 sty 2019 o 17:51 Carlos Rovira <carlosrovira@apache.org
> >
> > > > > > napisał(a):
> > > > > >
> > > > > > > Hi Piotr,
> > > > > > >
> > > > > > > since is what you show in the flex version.
> > > > > > > I think Adobe put side to content instead of side to label
> since
> > > the
> > > > > user
> > > > > > > fill the content elements and if not filled and required , the
> > > > tooltip
> > > > > > > should popup there.
> > > > > > > IOW, for usability, seems more appropriated the way flex
> > layedout,
> > > or
> > > > > > seems
> > > > > > > more natural.
> > > > > > >
> > > > > > > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
> > > > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > >
> > > > > > > > Carlos,
> > > > > > > >
> > > > > > > > Why you are proposing have that?
> > > > > > > >
> > > > > > > > L
> > > > > > > > C *
> > > > > > > >
> > > > > > > > I'm in favor of staying
> > > > > > > >
> > > > > > > > L *
> > > > > > > > C
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Piotr
> > > > > > > >
> > > > > > > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <
> > > > carlosrovira@apache.org
> > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > I forgot to mention about IBeadLayout more, since it could
> be
> > > > > > > > > misinterpreted:
> > > > > > > > >
> > > > > > > > > IBeadLayout for the global component is important, but what
> > I'm
> > > > > > > > considering
> > > > > > > > > is that although we can put HorizontalLayout (for the
> current
> > > > > > > FormtItem)
> > > > > > > > > and VerticalLayout (for the stacked), I'm seeing that many
> > > > > components
> > > > > > > > would
> > > > > > > > > need its own layout class. In this case we could create a
> > > > > > > FormItemLayout,
> > > > > > > > > and this will handle the layout vía CSS as it happens
> mostly
> > in
> > > > > many
> > > > > > > > other
> > > > > > > > > Jewel component.
> > > > > > > > >
> > > > > > > > > (Just say that some of them are using an standard layout
> > class,
> > > > > like
> > > > > > > > > HorizontalLayout, or even a NullLayout class), since I
> didn't
> > > > have
> > > > > > the
> > > > > > > > time
> > > > > > > > > to create its own one, and that's temporal. But my plan is
> to
> > > > > create
> > > > > > a
> > > > > > > > > concrete layout for some of this components. FormItem could
> > be
> > > > one
> > > > > of
> > > > > > > > those
> > > > > > > > > cases, for what we're seeing
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
> > > > > > > > carlosrovira@apache.org
> > > > > > > > > >)
> > > > > > > > > escribió:
> > > > > > > > >
> > > > > > > > > > Hi Piotr,
> > > > > > > > > >
> > > > > > > > > > looking at the screen shot, seems the required indicator
> is
> > > > > > > positioned
> > > > > > > > to
> > > > > > > > > > the right side of the element, what seems coherent,
> > although
> > > > > could
> > > > > > > be a
> > > > > > > > > bit
> > > > > > > > > > problematic depending on the width of the component. we
> > > assume
> > > > a
> > > > > > > fixed
> > > > > > > > > > width (to the widest element) and align all required (or
> > not
> > > a
> > > > > put
> > > > > > > the
> > > > > > > > > > required indicator just before the element, anyway this
> > seems
> > > > > > > something
> > > > > > > > > to
> > > > > > > > > > be solved as we have some real implementation.
> > > > > > > > > >
> > > > > > > > > > In order to implement it:
> > > > > > > > > >
> > > > > > > > > > We have 3 parts:
> > > > > > > > > > - L (this is the label)
> > > > > > > > > > - * (this is the required indicator)
> > > > > > > > > > - C (this is the element(s) that the user adds)
> > > > > > > > > >
> > > > > > > > > > * Actual FormItem is :
> > > > > > > > > >
> > > > > > > > > > L * C
> > > > > > > > > >
> > > > > > > > > > * We want for the new
> > > > > > > > > >
> > > > > > > > > > L
> > > > > > > > > > C *
> > > > > > > > > >
> > > > > > > > > > So it seems to me that
> > > > > > > > > >
> > > > > > > > > > a) IBeadLayout: ClassReference(
> > > > > > > > > > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> > > > > > > > > > Does not has much sense to me
> > > > > > > > > >
> > > > > > > > > > b) IFormItemLayout: ClassReference(
> > > > > > > > > > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> > > > > > > > > >
> > > > > > > > > > This is the one important to me (to configure), so user
> can
> > > > > change
> > > > > > > > layout
> > > > > > > > > > of the content part
> > > > > > > > > >
> > > > > > > > > > c) IBeadView: ClassReference(
> > > > > > > > > > "org.apache.royale.jewel.beads.views.FormItemView")
> > > > > > > > > > IFormItemContentArea:
> > > > > > ClassReference("org.apache.royale.jewel.Group")
> > > > > > > > > >
> > > > > > > > > > These are the parts important to me.
> > > > > > > > > >
> > > > > > > > > > I think we really want to change only the IBeadView, so
> we
> > > can
> > > > > > have a
> > > > > > > > > > FormItemView and a StackedFormItemView, and could change
> it
> > > vía
> > > > > > > > className
> > > > > > > > > > (for example)
> > > > > > > > > >
> > > > > > > > > > Let me know your thought about it
> > > > > > > > > >
> > > > > > > > > > thanks
> > > > > > > > > >
> > > > > > > > > > Carlos
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> > > > > > > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > > >
> > > > > > > > > >> Carlos,
> > > > > > > > > >>
> > > > > > > > > >> I have analyzed FormItem in Flex and here is how it is
> > done
> > > > > there.
> > > > > > > > > >> StackedFormItemSkin is using FormItemLayout which is
> > > > constrained
> > > > > > > into
> > > > > > > > 3
> > > > > > > > > >> columns (sequenceCol, contentCol and helpCol) and 2
> rows.
> > > > [1][2]
> > > > > > > > > >>
> > > > > > > > > >> When you look into the screenshot [2] you may think that
> > > > reuired
> > > > > > > > > indicator
> > > > > > > > > >> is part of the content, but it's not. It's not even part
> > of
> > > > the
> > > > > > > layout
> > > > > > > > > >> cause it has includeInLayout="false". [3]
> > > > > > > > > >> In Royale we don't have concept that something doesn't
> > > belong
> > > > to
> > > > > > > > layout
> > > > > > > > > >> and
> > > > > > > > > >> is not calculated and indicator default is being placed
> in
> > > > > > different
> > > > > > > > > area.
> > > > > > > > > >> Do you have some idea apart what I have proposed how to
> > > > resolve
> > > > > > > that ?
> > > > > > > > > >>
> > > > > > > > > >> [1] https://paste.apache.org/9Imj
> > > > > > > > > >> [2] https://imgur.com/GGOtzEU
> > > > > > > > > >> [3] https://paste.apache.org/kqlP
> > > > > > > > > >>
> > > > > > > > > >> Thanks,
> > > > > > > > > >> Piotr
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
> > > > > > piotrzarzycki21@gmail.com>
> > > > > > > > > >> napisał(a):
> > > > > > > > > >>
> > > > > > > > > >> > That's more clear to me. I will check and get back to
> > you.
> > > > > > > > > >> >
> > > > > > > > > >> > Thank you!
> > > > > > > > > >> >
> > > > > > > > > >> >
> > > > > > > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <
> > > > > carlosrovira@apache.org
> > > > > > >
> > > > > > > > > >> > napisał(a):
> > > > > > > > > >> >
> > > > > > > > > >> >> No,
> > > > > > > > > >> >>
> > > > > > > > > >> >> I was asking you about how flex solves visualy the
> > > problem
> > > > in
> > > > > > > their
> > > > > > > > > >> >> stacked
> > > > > > > > > >> >> version. The required icon is setup next to the
> label?
> > is
> > > > in
> > > > > > > other
> > > > > > > > > >> place?
> > > > > > > > > >> >> if we had an image of how it is designed (and like
> it),
> > > we
> > > > > can
> > > > > > > copy
> > > > > > > > > >> it. I
> > > > > > > > > >> >> still not proposing a technical solution. Just that I
> > > don't
> > > > > > have
> > > > > > > > > clear
> > > > > > > > > >> how
> > > > > > > > > >> >> we should layout it
> > > > > > > > > >> >>
> > > > > > > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
> > > > > > > > > >> >> piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > > >> >>
> > > > > > > > > >> >> > Carlos,
> > > > > > > > > >> >> >
> > > > > > > > > >> >> > Your suggestion is to have new form item
> > > > (StackedFormItem)
> > > > > > with
> > > > > > > > new
> > > > > > > > > >> >> > StackedFormItemView - cause problem is inside
> > > > FormitemView,
> > > > > > not
> > > > > > > > > >> inside
> > > > > > > > > >> >> > layout itself. Current layout is doing what it
> should
> > > do
> > > > -
> > > > > > > apart
> > > > > > > > of
> > > > > > > > > >> the
> > > > > > > > > >> >> > problem - it's making children to be
> > > Horizontal/Vertical.
> > > > > > > > > >> >> >
> > > > > > > > > >> >> > If I'm correct what you are saying - that's ok, but
> > if
> > > > you
> > > > > > have
> > > > > > > > had
> > > > > > > > > >> >> > different idea by saying above let me know.
> > > > > > > > > >> >> >
> > > > > > > > > >> >> > Thanks, Piotr
> > > > > > > > > >> >> >
> > > > > > > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
> > > > > > > carlosrovira@apache.org>
> > > > > > > > > >> >> > napisał(a):
> > > > > > > > > >> >> >
> > > > > > > > > >> >> > > Ok, I understand now.
> > > > > > > > > >> >> > >
> > > > > > > > > >> >> > > In Flex I think we had that layout and was
> > > > > > > > > >> called....StackedFormItem
> > > > > > > > > >> >> or
> > > > > > > > > >> >> > > something like that?
> > > > > > > > > >> >> > > Could you check how Flex solve this? If we
> continue
> > > > > liking
> > > > > > > the
> > > > > > > > > way
> > > > > > > > > >> >> > stacked
> > > > > > > > > >> >> > > form layout in flex looks, we can do the same for
> > our
> > > > > > Royale
> > > > > > > > > >> version
> > > > > > > > > >> >> > >
> > > > > > > > > >> >> > >
> > > > > > > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki
> > (<
> > > > > > > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > > >> >> > >
> > > > > > > > > >> >> > > > I'm not sure how Serkan is doing that on users
> > > forum,
> > > > > > but I
> > > > > > > > see
> > > > > > > > > >> all
> > > > > > > > > >> >> > hist
> > > > > > > > > >> >> > > > pasted images. Anyway here you go:
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > > > What I wanted to achieve:
> > > https://snag.gy/DmH7yk.jpg
> > > > > > > > > >> >> > > > What I got from Jewel FormItem:
> > > > > > https://snag.gy/Slfbt9.jpg
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
> > > > > > > > > carlosrovira@apache.org>
> > > > > > > > > >> >> > > > napisał(a):
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > > > > Piotr,
> > > > > > > > > >> >> > > > >
> > > > > > > > > >> >> > > > > remember that images pasted in list are not
> > > shared,
> > > > > you
> > > > > > > > must
> > > > > > > > > >> share
> > > > > > > > > >> >> > with
> > > > > > > > > >> >> > > > > some image service
> > > > > > > > > >> >> > > > >
> > > > > > > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr
> > Zarzycki
> > > > (<
> > > > > > > > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > > >> >> > > > >
> > > > > > > > > >> >> > > > > > There is one more problem with Layout.
> > > Currently
> > > > > > > default
> > > > > > > > in
> > > > > > > > > >> >> > framework
> > > > > > > > > >> >> > > > we
> > > > > > > > > >> >> > > > > > have [1]. It means that:
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > > > My content of FormItem will be vertical and
> > > > > > IBeadLayout
> > > > > > > > is
> > > > > > > > > >> >> > basically
> > > > > > > > > >> >> > > > > > ignored at some point. If I specify beads -
> > > > > > > > > HorizontalLayout
> > > > > > > > > >> as
> > > > > > > > > >> >> it
> > > > > > > > > >> >> > is
> > > > > > > > > >> >> > > > in
> > > > > > > > > >> >> > > > > > above example it will be taken as a primary
> > > and I
> > > > > > have
> > > > > > > my
> > > > > > > > > >> >> content
> > > > > > > > > >> >> > > > laying
> > > > > > > > > >> >> > > > > > out horizontally. The question is - what is
> > for
> > > > > > > > > >> >> IFormItemLayout in
> > > > > > > > > >> >> > > > > > default.css? Is it a bug?
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> > > > > > > > > >> >> piotrzarzycki21@gmail.com
> > > > > > > > > >> >> > >
> > > > > > > > > >> >> > > > > > napisał(a):
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > > >> Hi Carlos,
> > > > > > > > > >> >> > > > > >>
> > > > > > > > > >> >> > > > > >> I'm was trying to change FormItem to be
> > > Vertical
> > > > > > > > oriented.
> > > > > > > > > >> In
> > > > > > > > > >> >> > > general
> > > > > > > > > >> >> > > > I
> > > > > > > > > >> >> > > > > >> would like to have following view. Label
> of
> > > > > FormItem
> > > > > > > is
> > > > > > > > on
> > > > > > > > > >> the
> > > > > > > > > >> >> top
> > > > > > > > > >> >> > > and
> > > > > > > > > >> >> > > > > in
> > > > > > > > > >> >> > > > > >> the bottom is content.
> > > > > > > > > >> >> > > > > >>
> > > > > > > > > >> >> > > > > >> [image: image.png]
> > > > > > > > > >> >> > > > > >>
> > > > > > > > > >> >> > > > > >> Code for that will looks like that [1].
> > > Results
> > > > is
> > > > > > > > > >> following:
> > > > > > > > > >> >> > > > > >>
> > > > > > > > > >> >> > > > > >> [image: image.png]
> > > > > > > > > >> >> > > > > >>
> > > > > > > > > >> >> > > > > >> It happened cause Label and required star
> > > label
> > > > > are
> > > > > > > > > >> different
> > > > > > > > > >> >> > > > components
> > > > > > > > > >> >> > > > > >> - everything is being laying out
> vertically.
> > > > What
> > > > > is
> > > > > > > > your
> > > > > > > > > >> >> > suggestion
> > > > > > > > > >> >> > > > to
> > > > > > > > > >> >> > > > > fix
> > > > > > > > > >> >> > > > > >> that ?
> > > > > > > > > >> >> > > > > >>
> > > > > > > > > >> >> > > > > >> Mine is wrapping "First name" and "*" into
> > one
> > > > > Group
> > > > > > > > with
> > > > > > > > > >> >> > > > > >> HorizontalLayout.
> > > > > > > > > >> >> > > > > >>
> > > > > > > > > >> >> > > > > >> More thoughts are welcome. I hope you see
> > > > > > screenshots.
> > > > > > > > :)
> > > > > > > > > >> >> > > > > >>
> > > > > > > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
> > > > > > > > > >> >> > > > > >>
> > > > > > > > > >> >> > > > > >> Thanks,
> > > > > > > > > >> >> > > > > >> --
> > > > > > > > > >> >> > > > > >>
> > > > > > > > > >> >> > > > > >> Piotr Zarzycki
> > > > > > > > > >> >> > > > > >>
> > > > > > > > > >> >> > > > > >> Patreon: *
> > > https://www.patreon.com/piotrzarzycki
> > > > > > > > > >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > >> >> > > > > >>
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > > > --
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > > > Piotr Zarzycki
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > > > Patreon: *
> > > https://www.patreon.com/piotrzarzycki
> > > > > > > > > >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > >
> > > > > > > > > >> >> > > > >
> > > > > > > > > >> >> > > > > --
> > > > > > > > > >> >> > > > > Carlos Rovira
> > > > > > > > > >> >> > > > > http://about.me/carlosrovira
> > > > > > > > > >> >> > > > >
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > > > --
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > > > Piotr Zarzycki
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > > > Patreon: *
> https://www.patreon.com/piotrzarzycki
> > > > > > > > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > >
> > > > > > > > > >> >> > >
> > > > > > > > > >> >> > > --
> > > > > > > > > >> >> > > Carlos Rovira
> > > > > > > > > >> >> > > http://about.me/carlosrovira
> > > > > > > > > >> >> > >
> > > > > > > > > >> >> >
> > > > > > > > > >> >> >
> > > > > > > > > >> >> > --
> > > > > > > > > >> >> >
> > > > > > > > > >> >> > Piotr Zarzycki
> > > > > > > > > >> >> >
> > > > > > > > > >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > >> >> >
> > > > > > > > > >> >>
> > > > > > > > > >> >>
> > > > > > > > > >> >> --
> > > > > > > > > >> >> Carlos Rovira
> > > > > > > > > >> >> http://about.me/carlosrovira
> > > > > > > > > >> >>
> > > > > > > > > >> >
> > > > > > > > > >> >
> > > > > > > > > >> > --
> > > > > > > > > >> >
> > > > > > > > > >> > Piotr Zarzycki
> > > > > > > > > >> >
> > > > > > > > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > > > >> > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > >> >
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > > >> --
> > > > > > > > > >>
> > > > > > > > > >> Piotr Zarzycki
> > > > > > > > > >>
> > > > > > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > > >>
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Carlos Rovira
> > > > > > > > > > http://about.me/carlosrovira
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Carlos Rovira
> > > > > > > > > http://about.me/carlosrovira
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Carlos Rovira
> > > > > > > http://about.me/carlosrovira
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Piotr Zarzycki
> > > > > >
> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > <https://www.patreon.com/piotrzarzycki>*
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Carlos Rovira <ca...@apache.org>.

Hi Piotr,

Don't think if I understand right your exposition. I'll try to write in
words what I expect from a FormItemLayout and let me know if we're thinking
on the same.

We want to have a specialized layout for FormItem that support horizontal
and stacked form item layouts. At this point we can choose to have 2
layouts or only 1.
Since we always have 2, maybe that's the best way to go :
HorizontalFormItemLayout and VerticalFormItemLayout.

HorizontalFormItemLayout: should put label, required indicator and content
in the same "row", o mostly as HorizontalLayout does, and will be equal to
what we have now.

VerticalFormItemLayout should put Label followed by requiredIndicator in a
row and just below, the content part. *Or* Label in a row and below Content
followed by requited Indicator
(I think this should be configurable in some way, or implement a case and
made and additional layout for the other, so we can have both).

Some technical needs:

* All we'll be solved using CSS and css class selectors as with the rest of
Jewel Layouts and phyloshopy
* We'll continue using flexbox since is the standard in Jewel
* We can use the flexbox order to have a property that puts content before
required indicator or viceversa using a property in the layout.
* I think FormItemView would need to adapt to this, and maybe will need two
Views to support each layout (don't have clear now)




El vie., 25 ene. 2019 a las 16:23, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> I won't follow Flex, so if you would like to do this I'm fine. I'm going to
> implement my own View in my application. I won't commit it to Royale.
> However I would like to fix issue with layout. Currently IBeadLayout - Is
> making whole FormItem vertical or horizontal. *IFormItemLayout - Should
> treat content appropriately, but it doesn't do anything. I would like to
> change it in the following way:*
>
> *IBeadLayout do:*
>
> *1) When user: IBeadLayout:
> ClassReference("org.apache.royale.jewel.beads.layouts.VerticalLayout");*
> L
> C
> *2) When user: **IBeadLayout:
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");*
> *L C*
>
> *IFormItemLayout will do:*
> 1) IFormItemLayout:
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> and #1 - *IBeadLayout*
> L
> C - Set children Horizotnally
> 2) IFormItemLayout:
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> and #2 - *IBeadLayout*
> *L*
> *C - Set children Vertically*
>
> *Thoughts ?*
>
> Piotr
>
>
>
> pt., 25 sty 2019 o 16:13 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Ops!,
> >
> > ok, since I was using the other layout I was in the believe that was the
> > standard. So if we want to follow flex, we can change the current as
> well.
> >
> > El jue., 24 ene. 2019 a las 18:34, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> > > Nope - I just checked [1] - Code [2] - You are showing me some custom
> > > implementation.
> > >
> > > [1] https://imgur.com/INKlfcC
> > > [2] https://paste.apache.org/jyrl
> > >
> > > czw., 24 sty 2019 o 18:20 Carlos Rovira <ca...@apache.org>
> > > napisał(a):
> > >
> > > > Piotr,
> > > >
> > > > in Flex we have the same align (as we have now in Royale), check this
> > > > image: url
> > > > <
> > > >
> > >
> >
> https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249
> > > > >
> > > >
> > > > El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
> > > > piotrzarzycki21@gmail.com>) escribió:
> > > >
> > > > > If we are going in that direction it requires as well work were
> > > indicator
> > > > > in case of L* C (current implementation) will be changed to L C* -
> > Yes
> > > ?
> > > > -
> > > > > Being consistent it should be like that.
> > > > >
> > > > > I'm not sure what the trends are in that case.
> > > > >
> > > > > czw., 24 sty 2019 o 17:51 Carlos Rovira <ca...@apache.org>
> > > > > napisał(a):
> > > > >
> > > > > > Hi Piotr,
> > > > > >
> > > > > > since is what you show in the flex version.
> > > > > > I think Adobe put side to content instead of side to label since
> > the
> > > > user
> > > > > > fill the content elements and if not filled and required , the
> > > tooltip
> > > > > > should popup there.
> > > > > > IOW, for usability, seems more appropriated the way flex
> layedout,
> > or
> > > > > seems
> > > > > > more natural.
> > > > > >
> > > > > > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
> > > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > >
> > > > > > > Carlos,
> > > > > > >
> > > > > > > Why you are proposing have that?
> > > > > > >
> > > > > > > L
> > > > > > > C *
> > > > > > >
> > > > > > > I'm in favor of staying
> > > > > > >
> > > > > > > L *
> > > > > > > C
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Piotr
> > > > > > >
> > > > > > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <
> > > carlosrovira@apache.org
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > I forgot to mention about IBeadLayout more, since it could be
> > > > > > > > misinterpreted:
> > > > > > > >
> > > > > > > > IBeadLayout for the global component is important, but what
> I'm
> > > > > > > considering
> > > > > > > > is that although we can put HorizontalLayout (for the current
> > > > > > FormtItem)
> > > > > > > > and VerticalLayout (for the stacked), I'm seeing that many
> > > > components
> > > > > > > would
> > > > > > > > need its own layout class. In this case we could create a
> > > > > > FormItemLayout,
> > > > > > > > and this will handle the layout vía CSS as it happens mostly
> in
> > > > many
> > > > > > > other
> > > > > > > > Jewel component.
> > > > > > > >
> > > > > > > > (Just say that some of them are using an standard layout
> class,
> > > > like
> > > > > > > > HorizontalLayout, or even a NullLayout class), since I didn't
> > > have
> > > > > the
> > > > > > > time
> > > > > > > > to create its own one, and that's temporal. But my plan is to
> > > > create
> > > > > a
> > > > > > > > concrete layout for some of this components. FormItem could
> be
> > > one
> > > > of
> > > > > > > those
> > > > > > > > cases, for what we're seeing
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
> > > > > > > carlosrovira@apache.org
> > > > > > > > >)
> > > > > > > > escribió:
> > > > > > > >
> > > > > > > > > Hi Piotr,
> > > > > > > > >
> > > > > > > > > looking at the screen shot, seems the required indicator is
> > > > > > positioned
> > > > > > > to
> > > > > > > > > the right side of the element, what seems coherent,
> although
> > > > could
> > > > > > be a
> > > > > > > > bit
> > > > > > > > > problematic depending on the width of the component. we
> > assume
> > > a
> > > > > > fixed
> > > > > > > > > width (to the widest element) and align all required (or
> not
> > a
> > > > put
> > > > > > the
> > > > > > > > > required indicator just before the element, anyway this
> seems
> > > > > > something
> > > > > > > > to
> > > > > > > > > be solved as we have some real implementation.
> > > > > > > > >
> > > > > > > > > In order to implement it:
> > > > > > > > >
> > > > > > > > > We have 3 parts:
> > > > > > > > > - L (this is the label)
> > > > > > > > > - * (this is the required indicator)
> > > > > > > > > - C (this is the element(s) that the user adds)
> > > > > > > > >
> > > > > > > > > * Actual FormItem is :
> > > > > > > > >
> > > > > > > > > L * C
> > > > > > > > >
> > > > > > > > > * We want for the new
> > > > > > > > >
> > > > > > > > > L
> > > > > > > > > C *
> > > > > > > > >
> > > > > > > > > So it seems to me that
> > > > > > > > >
> > > > > > > > > a) IBeadLayout: ClassReference(
> > > > > > > > > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> > > > > > > > > Does not has much sense to me
> > > > > > > > >
> > > > > > > > > b) IFormItemLayout: ClassReference(
> > > > > > > > > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> > > > > > > > >
> > > > > > > > > This is the one important to me (to configure), so user can
> > > > change
> > > > > > > layout
> > > > > > > > > of the content part
> > > > > > > > >
> > > > > > > > > c) IBeadView: ClassReference(
> > > > > > > > > "org.apache.royale.jewel.beads.views.FormItemView")
> > > > > > > > > IFormItemContentArea:
> > > > > ClassReference("org.apache.royale.jewel.Group")
> > > > > > > > >
> > > > > > > > > These are the parts important to me.
> > > > > > > > >
> > > > > > > > > I think we really want to change only the IBeadView, so we
> > can
> > > > > have a
> > > > > > > > > FormItemView and a StackedFormItemView, and could change it
> > vía
> > > > > > > className
> > > > > > > > > (for example)
> > > > > > > > >
> > > > > > > > > Let me know your thought about it
> > > > > > > > >
> > > > > > > > > thanks
> > > > > > > > >
> > > > > > > > > Carlos
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> > > > > > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > >
> > > > > > > > >> Carlos,
> > > > > > > > >>
> > > > > > > > >> I have analyzed FormItem in Flex and here is how it is
> done
> > > > there.
> > > > > > > > >> StackedFormItemSkin is using FormItemLayout which is
> > > constrained
> > > > > > into
> > > > > > > 3
> > > > > > > > >> columns (sequenceCol, contentCol and helpCol) and 2 rows.
> > > [1][2]
> > > > > > > > >>
> > > > > > > > >> When you look into the screenshot [2] you may think that
> > > reuired
> > > > > > > > indicator
> > > > > > > > >> is part of the content, but it's not. It's not even part
> of
> > > the
> > > > > > layout
> > > > > > > > >> cause it has includeInLayout="false". [3]
> > > > > > > > >> In Royale we don't have concept that something doesn't
> > belong
> > > to
> > > > > > > layout
> > > > > > > > >> and
> > > > > > > > >> is not calculated and indicator default is being placed in
> > > > > different
> > > > > > > > area.
> > > > > > > > >> Do you have some idea apart what I have proposed how to
> > > resolve
> > > > > > that ?
> > > > > > > > >>
> > > > > > > > >> [1] https://paste.apache.org/9Imj
> > > > > > > > >> [2] https://imgur.com/GGOtzEU
> > > > > > > > >> [3] https://paste.apache.org/kqlP
> > > > > > > > >>
> > > > > > > > >> Thanks,
> > > > > > > > >> Piotr
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
> > > > > piotrzarzycki21@gmail.com>
> > > > > > > > >> napisał(a):
> > > > > > > > >>
> > > > > > > > >> > That's more clear to me. I will check and get back to
> you.
> > > > > > > > >> >
> > > > > > > > >> > Thank you!
> > > > > > > > >> >
> > > > > > > > >> >
> > > > > > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <
> > > > carlosrovira@apache.org
> > > > > >
> > > > > > > > >> > napisał(a):
> > > > > > > > >> >
> > > > > > > > >> >> No,
> > > > > > > > >> >>
> > > > > > > > >> >> I was asking you about how flex solves visualy the
> > problem
> > > in
> > > > > > their
> > > > > > > > >> >> stacked
> > > > > > > > >> >> version. The required icon is setup next to the label?
> is
> > > in
> > > > > > other
> > > > > > > > >> place?
> > > > > > > > >> >> if we had an image of how it is designed (and like it),
> > we
> > > > can
> > > > > > copy
> > > > > > > > >> it. I
> > > > > > > > >> >> still not proposing a technical solution. Just that I
> > don't
> > > > > have
> > > > > > > > clear
> > > > > > > > >> how
> > > > > > > > >> >> we should layout it
> > > > > > > > >> >>
> > > > > > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
> > > > > > > > >> >> piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > >> >>
> > > > > > > > >> >> > Carlos,
> > > > > > > > >> >> >
> > > > > > > > >> >> > Your suggestion is to have new form item
> > > (StackedFormItem)
> > > > > with
> > > > > > > new
> > > > > > > > >> >> > StackedFormItemView - cause problem is inside
> > > FormitemView,
> > > > > not
> > > > > > > > >> inside
> > > > > > > > >> >> > layout itself. Current layout is doing what it should
> > do
> > > -
> > > > > > apart
> > > > > > > of
> > > > > > > > >> the
> > > > > > > > >> >> > problem - it's making children to be
> > Horizontal/Vertical.
> > > > > > > > >> >> >
> > > > > > > > >> >> > If I'm correct what you are saying - that's ok, but
> if
> > > you
> > > > > have
> > > > > > > had
> > > > > > > > >> >> > different idea by saying above let me know.
> > > > > > > > >> >> >
> > > > > > > > >> >> > Thanks, Piotr
> > > > > > > > >> >> >
> > > > > > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
> > > > > > carlosrovira@apache.org>
> > > > > > > > >> >> > napisał(a):
> > > > > > > > >> >> >
> > > > > > > > >> >> > > Ok, I understand now.
> > > > > > > > >> >> > >
> > > > > > > > >> >> > > In Flex I think we had that layout and was
> > > > > > > > >> called....StackedFormItem
> > > > > > > > >> >> or
> > > > > > > > >> >> > > something like that?
> > > > > > > > >> >> > > Could you check how Flex solve this? If we continue
> > > > liking
> > > > > > the
> > > > > > > > way
> > > > > > > > >> >> > stacked
> > > > > > > > >> >> > > form layout in flex looks, we can do the same for
> our
> > > > > Royale
> > > > > > > > >> version
> > > > > > > > >> >> > >
> > > > > > > > >> >> > >
> > > > > > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki
> (<
> > > > > > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > >> >> > >
> > > > > > > > >> >> > > > I'm not sure how Serkan is doing that on users
> > forum,
> > > > > but I
> > > > > > > see
> > > > > > > > >> all
> > > > > > > > >> >> > hist
> > > > > > > > >> >> > > > pasted images. Anyway here you go:
> > > > > > > > >> >> > > >
> > > > > > > > >> >> > > > What I wanted to achieve:
> > https://snag.gy/DmH7yk.jpg
> > > > > > > > >> >> > > > What I got from Jewel FormItem:
> > > > > https://snag.gy/Slfbt9.jpg
> > > > > > > > >> >> > > >
> > > > > > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
> > > > > > > > carlosrovira@apache.org>
> > > > > > > > >> >> > > > napisał(a):
> > > > > > > > >> >> > > >
> > > > > > > > >> >> > > > > Piotr,
> > > > > > > > >> >> > > > >
> > > > > > > > >> >> > > > > remember that images pasted in list are not
> > shared,
> > > > you
> > > > > > > must
> > > > > > > > >> share
> > > > > > > > >> >> > with
> > > > > > > > >> >> > > > > some image service
> > > > > > > > >> >> > > > >
> > > > > > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr
> Zarzycki
> > > (<
> > > > > > > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > > >> >> > > > >
> > > > > > > > >> >> > > > > > There is one more problem with Layout.
> > Currently
> > > > > > default
> > > > > > > in
> > > > > > > > >> >> > framework
> > > > > > > > >> >> > > > we
> > > > > > > > >> >> > > > > > have [1]. It means that:
> > > > > > > > >> >> > > > > >
> > > > > > > > >> >> > > > > > My content of FormItem will be vertical and
> > > > > IBeadLayout
> > > > > > > is
> > > > > > > > >> >> > basically
> > > > > > > > >> >> > > > > > ignored at some point. If I specify beads -
> > > > > > > > HorizontalLayout
> > > > > > > > >> as
> > > > > > > > >> >> it
> > > > > > > > >> >> > is
> > > > > > > > >> >> > > > in
> > > > > > > > >> >> > > > > > above example it will be taken as a primary
> > and I
> > > > > have
> > > > > > my
> > > > > > > > >> >> content
> > > > > > > > >> >> > > > laying
> > > > > > > > >> >> > > > > > out horizontally. The question is - what is
> for
> > > > > > > > >> >> IFormItemLayout in
> > > > > > > > >> >> > > > > > default.css? Is it a bug?
> > > > > > > > >> >> > > > > >
> > > > > > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
> > > > > > > > >> >> > > > > >
> > > > > > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> > > > > > > > >> >> piotrzarzycki21@gmail.com
> > > > > > > > >> >> > >
> > > > > > > > >> >> > > > > > napisał(a):
> > > > > > > > >> >> > > > > >
> > > > > > > > >> >> > > > > >> Hi Carlos,
> > > > > > > > >> >> > > > > >>
> > > > > > > > >> >> > > > > >> I'm was trying to change FormItem to be
> > Vertical
> > > > > > > oriented.
> > > > > > > > >> In
> > > > > > > > >> >> > > general
> > > > > > > > >> >> > > > I
> > > > > > > > >> >> > > > > >> would like to have following view. Label of
> > > > FormItem
> > > > > > is
> > > > > > > on
> > > > > > > > >> the
> > > > > > > > >> >> top
> > > > > > > > >> >> > > and
> > > > > > > > >> >> > > > > in
> > > > > > > > >> >> > > > > >> the bottom is content.
> > > > > > > > >> >> > > > > >>
> > > > > > > > >> >> > > > > >> [image: image.png]
> > > > > > > > >> >> > > > > >>
> > > > > > > > >> >> > > > > >> Code for that will looks like that [1].
> > Results
> > > is
> > > > > > > > >> following:
> > > > > > > > >> >> > > > > >>
> > > > > > > > >> >> > > > > >> [image: image.png]
> > > > > > > > >> >> > > > > >>
> > > > > > > > >> >> > > > > >> It happened cause Label and required star
> > label
> > > > are
> > > > > > > > >> different
> > > > > > > > >> >> > > > components
> > > > > > > > >> >> > > > > >> - everything is being laying out vertically.
> > > What
> > > > is
> > > > > > > your
> > > > > > > > >> >> > suggestion
> > > > > > > > >> >> > > > to
> > > > > > > > >> >> > > > > fix
> > > > > > > > >> >> > > > > >> that ?
> > > > > > > > >> >> > > > > >>
> > > > > > > > >> >> > > > > >> Mine is wrapping "First name" and "*" into
> one
> > > > Group
> > > > > > > with
> > > > > > > > >> >> > > > > >> HorizontalLayout.
> > > > > > > > >> >> > > > > >>
> > > > > > > > >> >> > > > > >> More thoughts are welcome. I hope you see
> > > > > screenshots.
> > > > > > > :)
> > > > > > > > >> >> > > > > >>
> > > > > > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
> > > > > > > > >> >> > > > > >>
> > > > > > > > >> >> > > > > >> Thanks,
> > > > > > > > >> >> > > > > >> --
> > > > > > > > >> >> > > > > >>
> > > > > > > > >> >> > > > > >> Piotr Zarzycki
> > > > > > > > >> >> > > > > >>
> > > > > > > > >> >> > > > > >> Patreon: *
> > https://www.patreon.com/piotrzarzycki
> > > > > > > > >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > >> >> > > > > >>
> > > > > > > > >> >> > > > > >
> > > > > > > > >> >> > > > > >
> > > > > > > > >> >> > > > > > --
> > > > > > > > >> >> > > > > >
> > > > > > > > >> >> > > > > > Piotr Zarzycki
> > > > > > > > >> >> > > > > >
> > > > > > > > >> >> > > > > > Patreon: *
> > https://www.patreon.com/piotrzarzycki
> > > > > > > > >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > >> >> > > > > >
> > > > > > > > >> >> > > > >
> > > > > > > > >> >> > > > >
> > > > > > > > >> >> > > > > --
> > > > > > > > >> >> > > > > Carlos Rovira
> > > > > > > > >> >> > > > > http://about.me/carlosrovira
> > > > > > > > >> >> > > > >
> > > > > > > > >> >> > > >
> > > > > > > > >> >> > > >
> > > > > > > > >> >> > > > --
> > > > > > > > >> >> > > >
> > > > > > > > >> >> > > > Piotr Zarzycki
> > > > > > > > >> >> > > >
> > > > > > > > >> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > >> >> > > >
> > > > > > > > >> >> > >
> > > > > > > > >> >> > >
> > > > > > > > >> >> > > --
> > > > > > > > >> >> > > Carlos Rovira
> > > > > > > > >> >> > > http://about.me/carlosrovira
> > > > > > > > >> >> > >
> > > > > > > > >> >> >
> > > > > > > > >> >> >
> > > > > > > > >> >> > --
> > > > > > > > >> >> >
> > > > > > > > >> >> > Piotr Zarzycki
> > > > > > > > >> >> >
> > > > > > > > >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > >> >> >
> > > > > > > > >> >>
> > > > > > > > >> >>
> > > > > > > > >> >> --
> > > > > > > > >> >> Carlos Rovira
> > > > > > > > >> >> http://about.me/carlosrovira
> > > > > > > > >> >>
> > > > > > > > >> >
> > > > > > > > >> >
> > > > > > > > >> > --
> > > > > > > > >> >
> > > > > > > > >> > Piotr Zarzycki
> > > > > > > > >> >
> > > > > > > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > > >> > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > >> >
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >> --
> > > > > > > > >>
> > > > > > > > >> Piotr Zarzycki
> > > > > > > > >>
> > > > > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > > > > > >>
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Carlos Rovira
> > > > > > > > > http://about.me/carlosrovira
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Carlos Rovira
> > > > > > > > http://about.me/carlosrovira
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Carlos Rovira
> > > > > > http://about.me/carlosrovira
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Piotr Zarzycki
> > > > >
> > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > >
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

Re: Jewel Group layout change dynamically (was: Re: Vertical FormItem)

Posted by Carlos Rovira <ca...@apache.org>.

I must to leave now, at this time can't give you an answer. If you see a
clear place where this could be fixed we can try it.

thanks

El sáb., 26 ene. 2019 a las 12:11, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> Fix probably should be placed in SimpleVerticalLayout in beadsAddedHandler
>
> sob., 26 sty 2019 o 12:09 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > Carlos,
> >
> > This is html output when you add Vertical layout dynamically ->
> > https://imgur.com/7MhKEyS - basic is not needed yes ?
> >
> > Thanks,
> > Piotr
> >
> > sob., 26 sty 2019 o 12:06 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> >> Changing subject since this seems not related to FormItem right?
> >>
> >> to see what's happening and understand the problem and find a solution
> we
> >> should look at:
> >>
> >> * generated HTML: since all in Jewel is CSS based, what is the html
> >> output?
> >>
> >> The way I think Royale works (for Basic, Jewel,..), is that adding a
> bead
> >> in MXML will be added to the beads array. I think the other bead is not
> >> removed and still is there, but the new one takes precedence and when
> >> component ask for the layout bead it gets the latest.
> >>
> >> Maybe this is a problem related to the way Royale manage beads, or is a
> >> problem to Jewel not updating correctly css selectors.
> >>
> >>
> >> El sáb., 26 ene. 2019 a las 11:46, Piotr Zarzycki (<
> >> piotrzarzycki21@gmail.com>) escribió:
> >>
> >> > Carlos,
> >> >
> >> > I discovered also one more bug or at least I'm thinking about that as
> a
> >> > bug. Having following code [1] does work, but if I add bead
> dynamically
> >> -
> >> > it doesn't work. [2] - I believe fix can be placed in method
> >> > beadsAddedHandler
> >> > - Do you think this is a bug and fix can be here ?
> >> >
> >> > [1] https://paste.apache.org/IvoK
> >> > [2] https://paste.apache.org/kyfP
> >> >
> >> > Thanks,
> >> > Piotr
> >> >
> >>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

Re: Jewel Group layout change dynamically (was: Re: Vertical FormItem)

Posted by Piotr Zarzycki <pi...@gmail.com>.

Fix probably should be placed in SimpleVerticalLayout in beadsAddedHandler

sob., 26 sty 2019 o 12:09 Piotr Zarzycki <pi...@gmail.com>
napisał(a):

> Carlos,
>
> This is html output when you add Vertical layout dynamically ->
> https://imgur.com/7MhKEyS - basic is not needed yes ?
>
> Thanks,
> Piotr
>
> sob., 26 sty 2019 o 12:06 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
>> Changing subject since this seems not related to FormItem right?
>>
>> to see what's happening and understand the problem and find a solution we
>> should look at:
>>
>> * generated HTML: since all in Jewel is CSS based, what is the html
>> output?
>>
>> The way I think Royale works (for Basic, Jewel,..), is that adding a bead
>> in MXML will be added to the beads array. I think the other bead is not
>> removed and still is there, but the new one takes precedence and when
>> component ask for the layout bead it gets the latest.
>>
>> Maybe this is a problem related to the way Royale manage beads, or is a
>> problem to Jewel not updating correctly css selectors.
>>
>>
>> El sáb., 26 ene. 2019 a las 11:46, Piotr Zarzycki (<
>> piotrzarzycki21@gmail.com>) escribió:
>>
>> > Carlos,
>> >
>> > I discovered also one more bug or at least I'm thinking about that as a
>> > bug. Having following code [1] does work, but if I add bead dynamically
>> -
>> > it doesn't work. [2] - I believe fix can be placed in method
>> > beadsAddedHandler
>> > - Do you think this is a bug and fix can be here ?
>> >
>> > [1] https://paste.apache.org/IvoK
>> > [2] https://paste.apache.org/kyfP
>> >
>> > Thanks,
>> > Piotr
>> >
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Jewel Group layout change dynamically (was: Re: Vertical FormItem)

Posted by Carlos Rovira <ca...@apache.org>.

Right!, so "basic" is from "BasicLayout", and there's a bug somewhere that
is not removing that selector.
I think the problem is that in the mxml declaration, Royale never tries to
assign a BasicLayout and goes directly with the new one.
Instead, in the other way it adds BasicLayout, and then the other. But we
need to do maintenance and remove class names as the bead is replaced

El sáb., 26 ene. 2019 a las 12:09, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> Carlos,
>
> This is html output when you add Vertical layout dynamically ->
> https://imgur.com/7MhKEyS - basic is not needed yes ?
>
> Thanks,
> Piotr
>
> sob., 26 sty 2019 o 12:06 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Changing subject since this seems not related to FormItem right?
> >
> > to see what's happening and understand the problem and find a solution we
> > should look at:
> >
> > * generated HTML: since all in Jewel is CSS based, what is the html
> output?
> >
> > The way I think Royale works (for Basic, Jewel,..), is that adding a bead
> > in MXML will be added to the beads array. I think the other bead is not
> > removed and still is there, but the new one takes precedence and when
> > component ask for the layout bead it gets the latest.
> >
> > Maybe this is a problem related to the way Royale manage beads, or is a
> > problem to Jewel not updating correctly css selectors.
> >
> >
> > El sáb., 26 ene. 2019 a las 11:46, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> > > Carlos,
> > >
> > > I discovered also one more bug or at least I'm thinking about that as a
> > > bug. Having following code [1] does work, but if I add bead
> dynamically -
> > > it doesn't work. [2] - I believe fix can be placed in method
> > > beadsAddedHandler
> > > - Do you think this is a bug and fix can be here ?
> > >
> > > [1] https://paste.apache.org/IvoK
> > > [2] https://paste.apache.org/kyfP
> > >
> > > Thanks,
> > > Piotr
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

Re: Jewel Group layout change dynamically (was: Re: Vertical FormItem)

Posted by Piotr Zarzycki <pi...@gmail.com>.

Carlos,

This is html output when you add Vertical layout dynamically ->
https://imgur.com/7MhKEyS - basic is not needed yes ?

Thanks,
Piotr

sob., 26 sty 2019 o 12:06 Carlos Rovira <ca...@apache.org>
napisał(a):

> Changing subject since this seems not related to FormItem right?
>
> to see what's happening and understand the problem and find a solution we
> should look at:
>
> * generated HTML: since all in Jewel is CSS based, what is the html output?
>
> The way I think Royale works (for Basic, Jewel,..), is that adding a bead
> in MXML will be added to the beads array. I think the other bead is not
> removed and still is there, but the new one takes precedence and when
> component ask for the layout bead it gets the latest.
>
> Maybe this is a problem related to the way Royale manage beads, or is a
> problem to Jewel not updating correctly css selectors.
>
>
> El sáb., 26 ene. 2019 a las 11:46, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > Carlos,
> >
> > I discovered also one more bug or at least I'm thinking about that as a
> > bug. Having following code [1] does work, but if I add bead dynamically -
> > it doesn't work. [2] - I believe fix can be placed in method
> > beadsAddedHandler
> > - Do you think this is a bug and fix can be here ?
> >
> > [1] https://paste.apache.org/IvoK
> > [2] https://paste.apache.org/kyfP
> >
> > Thanks,
> > Piotr
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Jewel Group layout change dynamically (was: Re: Vertical FormItem)

Posted by Carlos Rovira <ca...@apache.org>.

Changing subject since this seems not related to FormItem right?

to see what's happening and understand the problem and find a solution we
should look at:

* generated HTML: since all in Jewel is CSS based, what is the html output?

The way I think Royale works (for Basic, Jewel,..), is that adding a bead
in MXML will be added to the beads array. I think the other bead is not
removed and still is there, but the new one takes precedence and when
component ask for the layout bead it gets the latest.

Maybe this is a problem related to the way Royale manage beads, or is a
problem to Jewel not updating correctly css selectors.


El sáb., 26 ene. 2019 a las 11:46, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> Carlos,
>
> I discovered also one more bug or at least I'm thinking about that as a
> bug. Having following code [1] does work, but if I add bead dynamically -
> it doesn't work. [2] - I believe fix can be placed in method
> beadsAddedHandler
> - Do you think this is a bug and fix can be here ?
>
> [1] https://paste.apache.org/IvoK
> [2] https://paste.apache.org/kyfP
>
> Thanks,
> Piotr
>


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

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

Carlos,

I discovered also one more bug or at least I'm thinking about that as a
bug. Having following code [1] does work, but if I add bead dynamically -
it doesn't work. [2] - I believe fix can be placed in method beadsAddedHandler
- Do you think this is a bug and fix can be here ?

[1] https://paste.apache.org/IvoK
[2] https://paste.apache.org/kyfP

Thanks,
Piotr

pt., 25 sty 2019 o 17:16 Piotr Zarzycki <pi...@gmail.com>
napisał(a):

> Carlos,
>
> I see following comment in FormItemView:
>
> "// Look for a layout and/or viewport bead on the formItem's beads list.
> If one
>
> // is found, pull it off so it will not be added permanently
> // to the strand."
>
> Why beads from strand is being removed ? It's because it was reused in other places ?
>
> Thanks,
>
> Piotr
>
>
> pt., 25 sty 2019 o 16:24 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
>> And I forgot to add that IBeadLayout is working fine.
>>
>> pt., 25 sty 2019 o 16:23 Piotr Zarzycki <pi...@gmail.com>
>> napisał(a):
>>
>>> I won't follow Flex, so if you would like to do this I'm fine. I'm going
>>> to implement my own View in my application. I won't commit it to Royale.
>>> However I would like to fix issue with layout. Currently IBeadLayout - Is
>>> making whole FormItem vertical or horizontal. *IFormItemLayout - Should
>>> treat content appropriately, but it doesn't do anything. I would like to
>>> change it in the following way:*
>>>
>>> *IBeadLayout do:*
>>>
>>> *1) When user: IBeadLayout:
>>> ClassReference("org.apache.royale.jewel.beads.layouts.VerticalLayout");*
>>> L
>>> C
>>> *2) When user: **IBeadLayout:
>>> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");*
>>> *L C*
>>>
>>> *IFormItemLayout will do:*
>>> 1) IFormItemLayout:
>>> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
>>> and #1 - *IBeadLayout*
>>> L
>>> C - Set children Horizotnally
>>> 2) IFormItemLayout:
>>> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
>>> and #2 - *IBeadLayout*
>>> *L*
>>> *C - Set children Vertically*
>>>
>>> *Thoughts ?*
>>>
>>> Piotr
>>>
>>>
>>>
>>> pt., 25 sty 2019 o 16:13 Carlos Rovira <ca...@apache.org>
>>> napisał(a):
>>>
>>>> Ops!,
>>>>
>>>> ok, since I was using the other layout I was in the believe that was the
>>>> standard. So if we want to follow flex, we can change the current as
>>>> well.
>>>>
>>>> El jue., 24 ene. 2019 a las 18:34, Piotr Zarzycki (<
>>>> piotrzarzycki21@gmail.com>) escribió:
>>>>
>>>> > Nope - I just checked [1] - Code [2] - You are showing me some custom
>>>> > implementation.
>>>> >
>>>> > [1] https://imgur.com/INKlfcC
>>>> > [2] https://paste.apache.org/jyrl
>>>> >
>>>> > czw., 24 sty 2019 o 18:20 Carlos Rovira <ca...@apache.org>
>>>> > napisał(a):
>>>> >
>>>> > > Piotr,
>>>> > >
>>>> > > in Flex we have the same align (as we have now in Royale), check
>>>> this
>>>> > > image: url
>>>> > > <
>>>> > >
>>>> >
>>>> https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249
>>>> > > >
>>>> > >
>>>> > > El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
>>>> > > piotrzarzycki21@gmail.com>) escribió:
>>>> > >
>>>> > > > If we are going in that direction it requires as well work were
>>>> > indicator
>>>> > > > in case of L* C (current implementation) will be changed to L C*
>>>> - Yes
>>>> > ?
>>>> > > -
>>>> > > > Being consistent it should be like that.
>>>> > > >
>>>> > > > I'm not sure what the trends are in that case.
>>>> > > >
>>>> > > > czw., 24 sty 2019 o 17:51 Carlos Rovira <ca...@apache.org>
>>>> > > > napisał(a):
>>>> > > >
>>>> > > > > Hi Piotr,
>>>> > > > >
>>>> > > > > since is what you show in the flex version.
>>>> > > > > I think Adobe put side to content instead of side to label
>>>> since the
>>>> > > user
>>>> > > > > fill the content elements and if not filled and required , the
>>>> > tooltip
>>>> > > > > should popup there.
>>>> > > > > IOW, for usability, seems more appropriated the way flex
>>>> layedout, or
>>>> > > > seems
>>>> > > > > more natural.
>>>> > > > >
>>>> > > > > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
>>>> > > > > piotrzarzycki21@gmail.com>) escribió:
>>>> > > > >
>>>> > > > > > Carlos,
>>>> > > > > >
>>>> > > > > > Why you are proposing have that?
>>>> > > > > >
>>>> > > > > > L
>>>> > > > > > C *
>>>> > > > > >
>>>> > > > > > I'm in favor of staying
>>>> > > > > >
>>>> > > > > > L *
>>>> > > > > > C
>>>> > > > > >
>>>> > > > > > Thanks,
>>>> > > > > > Piotr
>>>> > > > > >
>>>> > > > > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <
>>>> > carlosrovira@apache.org
>>>> > > >
>>>> > > > > > wrote:
>>>> > > > > >
>>>> > > > > > > I forgot to mention about IBeadLayout more, since it could
>>>> be
>>>> > > > > > > misinterpreted:
>>>> > > > > > >
>>>> > > > > > > IBeadLayout for the global component is important, but what
>>>> I'm
>>>> > > > > > considering
>>>> > > > > > > is that although we can put HorizontalLayout (for the
>>>> current
>>>> > > > > FormtItem)
>>>> > > > > > > and VerticalLayout (for the stacked), I'm seeing that many
>>>> > > components
>>>> > > > > > would
>>>> > > > > > > need its own layout class. In this case we could create a
>>>> > > > > FormItemLayout,
>>>> > > > > > > and this will handle the layout vía CSS as it happens
>>>> mostly in
>>>> > > many
>>>> > > > > > other
>>>> > > > > > > Jewel component.
>>>> > > > > > >
>>>> > > > > > > (Just say that some of them are using an standard layout
>>>> class,
>>>> > > like
>>>> > > > > > > HorizontalLayout, or even a NullLayout class), since I
>>>> didn't
>>>> > have
>>>> > > > the
>>>> > > > > > time
>>>> > > > > > > to create its own one, and that's temporal. But my plan is
>>>> to
>>>> > > create
>>>> > > > a
>>>> > > > > > > concrete layout for some of this components. FormItem could
>>>> be
>>>> > one
>>>> > > of
>>>> > > > > > those
>>>> > > > > > > cases, for what we're seeing
>>>> > > > > > >
>>>> > > > > > >
>>>> > > > > > >
>>>> > > > > > >
>>>> > > > > > >
>>>> > > > > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
>>>> > > > > > carlosrovira@apache.org
>>>> > > > > > > >)
>>>> > > > > > > escribió:
>>>> > > > > > >
>>>> > > > > > > > Hi Piotr,
>>>> > > > > > > >
>>>> > > > > > > > looking at the screen shot, seems the required indicator
>>>> is
>>>> > > > > positioned
>>>> > > > > > to
>>>> > > > > > > > the right side of the element, what seems coherent,
>>>> although
>>>> > > could
>>>> > > > > be a
>>>> > > > > > > bit
>>>> > > > > > > > problematic depending on the width of the component. we
>>>> assume
>>>> > a
>>>> > > > > fixed
>>>> > > > > > > > width (to the widest element) and align all required (or
>>>> not a
>>>> > > put
>>>> > > > > the
>>>> > > > > > > > required indicator just before the element, anyway this
>>>> seems
>>>> > > > > something
>>>> > > > > > > to
>>>> > > > > > > > be solved as we have some real implementation.
>>>> > > > > > > >
>>>> > > > > > > > In order to implement it:
>>>> > > > > > > >
>>>> > > > > > > > We have 3 parts:
>>>> > > > > > > > - L (this is the label)
>>>> > > > > > > > - * (this is the required indicator)
>>>> > > > > > > > - C (this is the element(s) that the user adds)
>>>> > > > > > > >
>>>> > > > > > > > * Actual FormItem is :
>>>> > > > > > > >
>>>> > > > > > > > L * C
>>>> > > > > > > >
>>>> > > > > > > > * We want for the new
>>>> > > > > > > >
>>>> > > > > > > > L
>>>> > > > > > > > C *
>>>> > > > > > > >
>>>> > > > > > > > So it seems to me that
>>>> > > > > > > >
>>>> > > > > > > > a) IBeadLayout: ClassReference(
>>>> > > > > > > > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
>>>> > > > > > > > Does not has much sense to me
>>>> > > > > > > >
>>>> > > > > > > > b) IFormItemLayout: ClassReference(
>>>> > > > > > > > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
>>>> > > > > > > >
>>>> > > > > > > > This is the one important to me (to configure), so user
>>>> can
>>>> > > change
>>>> > > > > > layout
>>>> > > > > > > > of the content part
>>>> > > > > > > >
>>>> > > > > > > > c) IBeadView: ClassReference(
>>>> > > > > > > > "org.apache.royale.jewel.beads.views.FormItemView")
>>>> > > > > > > > IFormItemContentArea:
>>>> > > > ClassReference("org.apache.royale.jewel.Group")
>>>> > > > > > > >
>>>> > > > > > > > These are the parts important to me.
>>>> > > > > > > >
>>>> > > > > > > > I think we really want to change only the IBeadView, so
>>>> we can
>>>> > > > have a
>>>> > > > > > > > FormItemView and a StackedFormItemView, and could change
>>>> it vía
>>>> > > > > > className
>>>> > > > > > > > (for example)
>>>> > > > > > > >
>>>> > > > > > > > Let me know your thought about it
>>>> > > > > > > >
>>>> > > > > > > > thanks
>>>> > > > > > > >
>>>> > > > > > > > Carlos
>>>> > > > > > > >
>>>> > > > > > > >
>>>> > > > > > > >
>>>> > > > > > > >
>>>> > > > > > > >
>>>> > > > > > > >
>>>> > > > > > > >
>>>> > > > > > > >
>>>> > > > > > > >
>>>> > > > > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
>>>> > > > > > > > piotrzarzycki21@gmail.com>) escribió:
>>>> > > > > > > >
>>>> > > > > > > >> Carlos,
>>>> > > > > > > >>
>>>> > > > > > > >> I have analyzed FormItem in Flex and here is how it is
>>>> done
>>>> > > there.
>>>> > > > > > > >> StackedFormItemSkin is using FormItemLayout which is
>>>> > constrained
>>>> > > > > into
>>>> > > > > > 3
>>>> > > > > > > >> columns (sequenceCol, contentCol and helpCol) and 2 rows.
>>>> > [1][2]
>>>> > > > > > > >>
>>>> > > > > > > >> When you look into the screenshot [2] you may think that
>>>> > reuired
>>>> > > > > > > indicator
>>>> > > > > > > >> is part of the content, but it's not. It's not even part
>>>> of
>>>> > the
>>>> > > > > layout
>>>> > > > > > > >> cause it has includeInLayout="false". [3]
>>>> > > > > > > >> In Royale we don't have concept that something doesn't
>>>> belong
>>>> > to
>>>> > > > > > layout
>>>> > > > > > > >> and
>>>> > > > > > > >> is not calculated and indicator default is being placed
>>>> in
>>>> > > > different
>>>> > > > > > > area.
>>>> > > > > > > >> Do you have some idea apart what I have proposed how to
>>>> > resolve
>>>> > > > > that ?
>>>> > > > > > > >>
>>>> > > > > > > >> [1] https://paste.apache.org/9Imj
>>>> > > > > > > >> [2] https://imgur.com/GGOtzEU
>>>> > > > > > > >> [3] https://paste.apache.org/kqlP
>>>> > > > > > > >>
>>>> > > > > > > >> Thanks,
>>>> > > > > > > >> Piotr
>>>> > > > > > > >>
>>>> > > > > > > >>
>>>> > > > > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
>>>> > > > piotrzarzycki21@gmail.com>
>>>> > > > > > > >> napisał(a):
>>>> > > > > > > >>
>>>> > > > > > > >> > That's more clear to me. I will check and get back to
>>>> you.
>>>> > > > > > > >> >
>>>> > > > > > > >> > Thank you!
>>>> > > > > > > >> >
>>>> > > > > > > >> >
>>>> > > > > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <
>>>> > > carlosrovira@apache.org
>>>> > > > >
>>>> > > > > > > >> > napisał(a):
>>>> > > > > > > >> >
>>>> > > > > > > >> >> No,
>>>> > > > > > > >> >>
>>>> > > > > > > >> >> I was asking you about how flex solves visualy the
>>>> problem
>>>> > in
>>>> > > > > their
>>>> > > > > > > >> >> stacked
>>>> > > > > > > >> >> version. The required icon is setup next to the
>>>> label? is
>>>> > in
>>>> > > > > other
>>>> > > > > > > >> place?
>>>> > > > > > > >> >> if we had an image of how it is designed (and like
>>>> it), we
>>>> > > can
>>>> > > > > copy
>>>> > > > > > > >> it. I
>>>> > > > > > > >> >> still not proposing a technical solution. Just that I
>>>> don't
>>>> > > > have
>>>> > > > > > > clear
>>>> > > > > > > >> how
>>>> > > > > > > >> >> we should layout it
>>>> > > > > > > >> >>
>>>> > > > > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
>>>> > > > > > > >> >> piotrzarzycki21@gmail.com>) escribió:
>>>> > > > > > > >> >>
>>>> > > > > > > >> >> > Carlos,
>>>> > > > > > > >> >> >
>>>> > > > > > > >> >> > Your suggestion is to have new form item
>>>> > (StackedFormItem)
>>>> > > > with
>>>> > > > > > new
>>>> > > > > > > >> >> > StackedFormItemView - cause problem is inside
>>>> > FormitemView,
>>>> > > > not
>>>> > > > > > > >> inside
>>>> > > > > > > >> >> > layout itself. Current layout is doing what it
>>>> should do
>>>> > -
>>>> > > > > apart
>>>> > > > > > of
>>>> > > > > > > >> the
>>>> > > > > > > >> >> > problem - it's making children to be
>>>> Horizontal/Vertical.
>>>> > > > > > > >> >> >
>>>> > > > > > > >> >> > If I'm correct what you are saying - that's ok, but
>>>> if
>>>> > you
>>>> > > > have
>>>> > > > > > had
>>>> > > > > > > >> >> > different idea by saying above let me know.
>>>> > > > > > > >> >> >
>>>> > > > > > > >> >> > Thanks, Piotr
>>>> > > > > > > >> >> >
>>>> > > > > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
>>>> > > > > carlosrovira@apache.org>
>>>> > > > > > > >> >> > napisał(a):
>>>> > > > > > > >> >> >
>>>> > > > > > > >> >> > > Ok, I understand now.
>>>> > > > > > > >> >> > >
>>>> > > > > > > >> >> > > In Flex I think we had that layout and was
>>>> > > > > > > >> called....StackedFormItem
>>>> > > > > > > >> >> or
>>>> > > > > > > >> >> > > something like that?
>>>> > > > > > > >> >> > > Could you check how Flex solve this? If we
>>>> continue
>>>> > > liking
>>>> > > > > the
>>>> > > > > > > way
>>>> > > > > > > >> >> > stacked
>>>> > > > > > > >> >> > > form layout in flex looks, we can do the same for
>>>> our
>>>> > > > Royale
>>>> > > > > > > >> version
>>>> > > > > > > >> >> > >
>>>> > > > > > > >> >> > >
>>>> > > > > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki
>>>> (<
>>>> > > > > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
>>>> > > > > > > >> >> > >
>>>> > > > > > > >> >> > > > I'm not sure how Serkan is doing that on users
>>>> forum,
>>>> > > > but I
>>>> > > > > > see
>>>> > > > > > > >> all
>>>> > > > > > > >> >> > hist
>>>> > > > > > > >> >> > > > pasted images. Anyway here you go:
>>>> > > > > > > >> >> > > >
>>>> > > > > > > >> >> > > > What I wanted to achieve:
>>>> https://snag.gy/DmH7yk.jpg
>>>> > > > > > > >> >> > > > What I got from Jewel FormItem:
>>>> > > > https://snag.gy/Slfbt9.jpg
>>>> > > > > > > >> >> > > >
>>>> > > > > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
>>>> > > > > > > carlosrovira@apache.org>
>>>> > > > > > > >> >> > > > napisał(a):
>>>> > > > > > > >> >> > > >
>>>> > > > > > > >> >> > > > > Piotr,
>>>> > > > > > > >> >> > > > >
>>>> > > > > > > >> >> > > > > remember that images pasted in list are not
>>>> shared,
>>>> > > you
>>>> > > > > > must
>>>> > > > > > > >> share
>>>> > > > > > > >> >> > with
>>>> > > > > > > >> >> > > > > some image service
>>>> > > > > > > >> >> > > > >
>>>> > > > > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr
>>>> Zarzycki
>>>> > (<
>>>> > > > > > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
>>>> > > > > > > >> >> > > > >
>>>> > > > > > > >> >> > > > > > There is one more problem with Layout.
>>>> Currently
>>>> > > > > default
>>>> > > > > > in
>>>> > > > > > > >> >> > framework
>>>> > > > > > > >> >> > > > we
>>>> > > > > > > >> >> > > > > > have [1]. It means that:
>>>> > > > > > > >> >> > > > > >
>>>> > > > > > > >> >> > > > > > My content of FormItem will be vertical and
>>>> > > > IBeadLayout
>>>> > > > > > is
>>>> > > > > > > >> >> > basically
>>>> > > > > > > >> >> > > > > > ignored at some point. If I specify beads -
>>>> > > > > > > HorizontalLayout
>>>> > > > > > > >> as
>>>> > > > > > > >> >> it
>>>> > > > > > > >> >> > is
>>>> > > > > > > >> >> > > > in
>>>> > > > > > > >> >> > > > > > above example it will be taken as a primary
>>>> and I
>>>> > > > have
>>>> > > > > my
>>>> > > > > > > >> >> content
>>>> > > > > > > >> >> > > > laying
>>>> > > > > > > >> >> > > > > > out horizontally. The question is - what is
>>>> for
>>>> > > > > > > >> >> IFormItemLayout in
>>>> > > > > > > >> >> > > > > > default.css? Is it a bug?
>>>> > > > > > > >> >> > > > > >
>>>> > > > > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
>>>> > > > > > > >> >> > > > > >
>>>> > > > > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
>>>> > > > > > > >> >> piotrzarzycki21@gmail.com
>>>> > > > > > > >> >> > >
>>>> > > > > > > >> >> > > > > > napisał(a):
>>>> > > > > > > >> >> > > > > >
>>>> > > > > > > >> >> > > > > >> Hi Carlos,
>>>> > > > > > > >> >> > > > > >>
>>>> > > > > > > >> >> > > > > >> I'm was trying to change FormItem to be
>>>> Vertical
>>>> > > > > > oriented.
>>>> > > > > > > >> In
>>>> > > > > > > >> >> > > general
>>>> > > > > > > >> >> > > > I
>>>> > > > > > > >> >> > > > > >> would like to have following view. Label of
>>>> > > FormItem
>>>> > > > > is
>>>> > > > > > on
>>>> > > > > > > >> the
>>>> > > > > > > >> >> top
>>>> > > > > > > >> >> > > and
>>>> > > > > > > >> >> > > > > in
>>>> > > > > > > >> >> > > > > >> the bottom is content.
>>>> > > > > > > >> >> > > > > >>
>>>> > > > > > > >> >> > > > > >> [image: image.png]
>>>> > > > > > > >> >> > > > > >>
>>>> > > > > > > >> >> > > > > >> Code for that will looks like that [1].
>>>> Results
>>>> > is
>>>> > > > > > > >> following:
>>>> > > > > > > >> >> > > > > >>
>>>> > > > > > > >> >> > > > > >> [image: image.png]
>>>> > > > > > > >> >> > > > > >>
>>>> > > > > > > >> >> > > > > >> It happened cause Label and required star
>>>> label
>>>> > > are
>>>> > > > > > > >> different
>>>> > > > > > > >> >> > > > components
>>>> > > > > > > >> >> > > > > >> - everything is being laying out
>>>> vertically.
>>>> > What
>>>> > > is
>>>> > > > > > your
>>>> > > > > > > >> >> > suggestion
>>>> > > > > > > >> >> > > > to
>>>> > > > > > > >> >> > > > > fix
>>>> > > > > > > >> >> > > > > >> that ?
>>>> > > > > > > >> >> > > > > >>
>>>> > > > > > > >> >> > > > > >> Mine is wrapping "First name" and "*" into
>>>> one
>>>> > > Group
>>>> > > > > > with
>>>> > > > > > > >> >> > > > > >> HorizontalLayout.
>>>> > > > > > > >> >> > > > > >>
>>>> > > > > > > >> >> > > > > >> More thoughts are welcome. I hope you see
>>>> > > > screenshots.
>>>> > > > > > :)
>>>> > > > > > > >> >> > > > > >>
>>>> > > > > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
>>>> > > > > > > >> >> > > > > >>
>>>> > > > > > > >> >> > > > > >> Thanks,
>>>> > > > > > > >> >> > > > > >> --
>>>> > > > > > > >> >> > > > > >>
>>>> > > > > > > >> >> > > > > >> Piotr Zarzycki
>>>> > > > > > > >> >> > > > > >>
>>>> > > > > > > >> >> > > > > >> Patreon: *
>>>> https://www.patreon.com/piotrzarzycki
>>>> > > > > > > >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
>>>> > > > > > > >> >> > > > > >>
>>>> > > > > > > >> >> > > > > >
>>>> > > > > > > >> >> > > > > >
>>>> > > > > > > >> >> > > > > > --
>>>> > > > > > > >> >> > > > > >
>>>> > > > > > > >> >> > > > > > Piotr Zarzycki
>>>> > > > > > > >> >> > > > > >
>>>> > > > > > > >> >> > > > > > Patreon: *
>>>> https://www.patreon.com/piotrzarzycki
>>>> > > > > > > >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
>>>> > > > > > > >> >> > > > > >
>>>> > > > > > > >> >> > > > >
>>>> > > > > > > >> >> > > > >
>>>> > > > > > > >> >> > > > > --
>>>> > > > > > > >> >> > > > > Carlos Rovira
>>>> > > > > > > >> >> > > > > http://about.me/carlosrovira
>>>> > > > > > > >> >> > > > >
>>>> > > > > > > >> >> > > >
>>>> > > > > > > >> >> > > >
>>>> > > > > > > >> >> > > > --
>>>> > > > > > > >> >> > > >
>>>> > > > > > > >> >> > > > Piotr Zarzycki
>>>> > > > > > > >> >> > > >
>>>> > > > > > > >> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
>>>> > > > > > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
>>>> > > > > > > >> >> > > >
>>>> > > > > > > >> >> > >
>>>> > > > > > > >> >> > >
>>>> > > > > > > >> >> > > --
>>>> > > > > > > >> >> > > Carlos Rovira
>>>> > > > > > > >> >> > > http://about.me/carlosrovira
>>>> > > > > > > >> >> > >
>>>> > > > > > > >> >> >
>>>> > > > > > > >> >> >
>>>> > > > > > > >> >> > --
>>>> > > > > > > >> >> >
>>>> > > > > > > >> >> > Piotr Zarzycki
>>>> > > > > > > >> >> >
>>>> > > > > > > >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
>>>> > > > > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
>>>> > > > > > > >> >> >
>>>> > > > > > > >> >>
>>>> > > > > > > >> >>
>>>> > > > > > > >> >> --
>>>> > > > > > > >> >> Carlos Rovira
>>>> > > > > > > >> >> http://about.me/carlosrovira
>>>> > > > > > > >> >>
>>>> > > > > > > >> >
>>>> > > > > > > >> >
>>>> > > > > > > >> > --
>>>> > > > > > > >> >
>>>> > > > > > > >> > Piotr Zarzycki
>>>> > > > > > > >> >
>>>> > > > > > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
>>>> > > > > > > >> > <https://www.patreon.com/piotrzarzycki>*
>>>> > > > > > > >> >
>>>> > > > > > > >>
>>>> > > > > > > >>
>>>> > > > > > > >> --
>>>> > > > > > > >>
>>>> > > > > > > >> Piotr Zarzycki
>>>> > > > > > > >>
>>>> > > > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
>>>> > > > > > > >> <https://www.patreon.com/piotrzarzycki>*
>>>> > > > > > > >>
>>>> > > > > > > >
>>>> > > > > > > >
>>>> > > > > > > > --
>>>> > > > > > > > Carlos Rovira
>>>> > > > > > > > http://about.me/carlosrovira
>>>> > > > > > > >
>>>> > > > > > > >
>>>> > > > > > >
>>>> > > > > > > --
>>>> > > > > > > Carlos Rovira
>>>> > > > > > > http://about.me/carlosrovira
>>>> > > > > > >
>>>> > > > > >
>>>> > > > >
>>>> > > > >
>>>> > > > > --
>>>> > > > > Carlos Rovira
>>>> > > > > http://about.me/carlosrovira
>>>> > > > >
>>>> > > >
>>>> > > >
>>>> > > > --
>>>> > > >
>>>> > > > Piotr Zarzycki
>>>> > > >
>>>> > > > Patreon: *https://www.patreon.com/piotrzarzycki
>>>> > > > <https://www.patreon.com/piotrzarzycki>*
>>>> > > >
>>>> > >
>>>> > >
>>>> > > --
>>>> > > Carlos Rovira
>>>> > > http://about.me/carlosrovira
>>>> > >
>>>> >
>>>> >
>>>> > --
>>>> >
>>>> > Piotr Zarzycki
>>>> >
>>>> > Patreon: *https://www.patreon.com/piotrzarzycki
>>>> > <https://www.patreon.com/piotrzarzycki>*
>>>> >
>>>>
>>>>
>>>> --
>>>> Carlos Rovira
>>>> http://about.me/carlosrovira
>>>>
>>>
>>>
>>> --
>>>
>>> Piotr Zarzycki
>>>
>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>> <https://www.patreon.com/piotrzarzycki>*
>>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Carlos Rovira <ca...@apache.org>.

ForItem is based on Basic Panel work since we have "chrome" elements and
"content" elements.
don't remember exactly but I found that in Panel changes to bead layout was
not working as expected, so all this can be part of that problem

El vie., 25 ene. 2019 a las 17:17, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> Carlos,
>
> I see following comment in FormItemView:
>
> "// Look for a layout and/or viewport bead on the formItem's beads list. If
> one
>
> // is found, pull it off so it will not be added permanently
> // to the strand."
>
> Why beads from strand is being removed ? It's because it was reused in
> other places ?
>
> Thanks,
>
> Piotr
>
>
> pt., 25 sty 2019 o 16:24 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > And I forgot to add that IBeadLayout is working fine.
> >
> > pt., 25 sty 2019 o 16:23 Piotr Zarzycki <pi...@gmail.com>
> > napisał(a):
> >
> >> I won't follow Flex, so if you would like to do this I'm fine. I'm going
> >> to implement my own View in my application. I won't commit it to Royale.
> >> However I would like to fix issue with layout. Currently IBeadLayout -
> Is
> >> making whole FormItem vertical or horizontal. *IFormItemLayout - Should
> >> treat content appropriately, but it doesn't do anything. I would like to
> >> change it in the following way:*
> >>
> >> *IBeadLayout do:*
> >>
> >> *1) When user: IBeadLayout:
> >> ClassReference("org.apache.royale.jewel.beads.layouts.VerticalLayout");*
> >> L
> >> C
> >> *2) When user: **IBeadLayout:
> >>
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");*
> >> *L C*
> >>
> >> *IFormItemLayout will do:*
> >> 1) IFormItemLayout:
> >>
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> >> and #1 - *IBeadLayout*
> >> L
> >> C - Set children Horizotnally
> >> 2) IFormItemLayout:
> >>
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> >> and #2 - *IBeadLayout*
> >> *L*
> >> *C - Set children Vertically*
> >>
> >> *Thoughts ?*
> >>
> >> Piotr
> >>
> >>
> >>
> >> pt., 25 sty 2019 o 16:13 Carlos Rovira <ca...@apache.org>
> >> napisał(a):
> >>
> >>> Ops!,
> >>>
> >>> ok, since I was using the other layout I was in the believe that was
> the
> >>> standard. So if we want to follow flex, we can change the current as
> >>> well.
> >>>
> >>> El jue., 24 ene. 2019 a las 18:34, Piotr Zarzycki (<
> >>> piotrzarzycki21@gmail.com>) escribió:
> >>>
> >>> > Nope - I just checked [1] - Code [2] - You are showing me some custom
> >>> > implementation.
> >>> >
> >>> > [1] https://imgur.com/INKlfcC
> >>> > [2] https://paste.apache.org/jyrl
> >>> >
> >>> > czw., 24 sty 2019 o 18:20 Carlos Rovira <ca...@apache.org>
> >>> > napisał(a):
> >>> >
> >>> > > Piotr,
> >>> > >
> >>> > > in Flex we have the same align (as we have now in Royale), check
> this
> >>> > > image: url
> >>> > > <
> >>> > >
> >>> >
> >>>
> https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249
> >>> > > >
> >>> > >
> >>> > > El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
> >>> > > piotrzarzycki21@gmail.com>) escribió:
> >>> > >
> >>> > > > If we are going in that direction it requires as well work were
> >>> > indicator
> >>> > > > in case of L* C (current implementation) will be changed to L C*
> -
> >>> Yes
> >>> > ?
> >>> > > -
> >>> > > > Being consistent it should be like that.
> >>> > > >
> >>> > > > I'm not sure what the trends are in that case.
> >>> > > >
> >>> > > > czw., 24 sty 2019 o 17:51 Carlos Rovira <carlosrovira@apache.org
> >
> >>> > > > napisał(a):
> >>> > > >
> >>> > > > > Hi Piotr,
> >>> > > > >
> >>> > > > > since is what you show in the flex version.
> >>> > > > > I think Adobe put side to content instead of side to label
> since
> >>> the
> >>> > > user
> >>> > > > > fill the content elements and if not filled and required , the
> >>> > tooltip
> >>> > > > > should popup there.
> >>> > > > > IOW, for usability, seems more appropriated the way flex
> >>> layedout, or
> >>> > > > seems
> >>> > > > > more natural.
> >>> > > > >
> >>> > > > > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
> >>> > > > > piotrzarzycki21@gmail.com>) escribió:
> >>> > > > >
> >>> > > > > > Carlos,
> >>> > > > > >
> >>> > > > > > Why you are proposing have that?
> >>> > > > > >
> >>> > > > > > L
> >>> > > > > > C *
> >>> > > > > >
> >>> > > > > > I'm in favor of staying
> >>> > > > > >
> >>> > > > > > L *
> >>> > > > > > C
> >>> > > > > >
> >>> > > > > > Thanks,
> >>> > > > > > Piotr
> >>> > > > > >
> >>> > > > > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <
> >>> > carlosrovira@apache.org
> >>> > > >
> >>> > > > > > wrote:
> >>> > > > > >
> >>> > > > > > > I forgot to mention about IBeadLayout more, since it could
> be
> >>> > > > > > > misinterpreted:
> >>> > > > > > >
> >>> > > > > > > IBeadLayout for the global component is important, but what
> >>> I'm
> >>> > > > > > considering
> >>> > > > > > > is that although we can put HorizontalLayout (for the
> current
> >>> > > > > FormtItem)
> >>> > > > > > > and VerticalLayout (for the stacked), I'm seeing that many
> >>> > > components
> >>> > > > > > would
> >>> > > > > > > need its own layout class. In this case we could create a
> >>> > > > > FormItemLayout,
> >>> > > > > > > and this will handle the layout vía CSS as it happens
> mostly
> >>> in
> >>> > > many
> >>> > > > > > other
> >>> > > > > > > Jewel component.
> >>> > > > > > >
> >>> > > > > > > (Just say that some of them are using an standard layout
> >>> class,
> >>> > > like
> >>> > > > > > > HorizontalLayout, or even a NullLayout class), since I
> didn't
> >>> > have
> >>> > > > the
> >>> > > > > > time
> >>> > > > > > > to create its own one, and that's temporal. But my plan is
> to
> >>> > > create
> >>> > > > a
> >>> > > > > > > concrete layout for some of this components. FormItem could
> >>> be
> >>> > one
> >>> > > of
> >>> > > > > > those
> >>> > > > > > > cases, for what we're seeing
> >>> > > > > > >
> >>> > > > > > >
> >>> > > > > > >
> >>> > > > > > >
> >>> > > > > > >
> >>> > > > > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
> >>> > > > > > carlosrovira@apache.org
> >>> > > > > > > >)
> >>> > > > > > > escribió:
> >>> > > > > > >
> >>> > > > > > > > Hi Piotr,
> >>> > > > > > > >
> >>> > > > > > > > looking at the screen shot, seems the required indicator
> is
> >>> > > > > positioned
> >>> > > > > > to
> >>> > > > > > > > the right side of the element, what seems coherent,
> >>> although
> >>> > > could
> >>> > > > > be a
> >>> > > > > > > bit
> >>> > > > > > > > problematic depending on the width of the component. we
> >>> assume
> >>> > a
> >>> > > > > fixed
> >>> > > > > > > > width (to the widest element) and align all required (or
> >>> not a
> >>> > > put
> >>> > > > > the
> >>> > > > > > > > required indicator just before the element, anyway this
> >>> seems
> >>> > > > > something
> >>> > > > > > > to
> >>> > > > > > > > be solved as we have some real implementation.
> >>> > > > > > > >
> >>> > > > > > > > In order to implement it:
> >>> > > > > > > >
> >>> > > > > > > > We have 3 parts:
> >>> > > > > > > > - L (this is the label)
> >>> > > > > > > > - * (this is the required indicator)
> >>> > > > > > > > - C (this is the element(s) that the user adds)
> >>> > > > > > > >
> >>> > > > > > > > * Actual FormItem is :
> >>> > > > > > > >
> >>> > > > > > > > L * C
> >>> > > > > > > >
> >>> > > > > > > > * We want for the new
> >>> > > > > > > >
> >>> > > > > > > > L
> >>> > > > > > > > C *
> >>> > > > > > > >
> >>> > > > > > > > So it seems to me that
> >>> > > > > > > >
> >>> > > > > > > > a) IBeadLayout: ClassReference(
> >>> > > > > > > > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> >>> > > > > > > > Does not has much sense to me
> >>> > > > > > > >
> >>> > > > > > > > b) IFormItemLayout: ClassReference(
> >>> > > > > > > > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> >>> > > > > > > >
> >>> > > > > > > > This is the one important to me (to configure), so user
> can
> >>> > > change
> >>> > > > > > layout
> >>> > > > > > > > of the content part
> >>> > > > > > > >
> >>> > > > > > > > c) IBeadView: ClassReference(
> >>> > > > > > > > "org.apache.royale.jewel.beads.views.FormItemView")
> >>> > > > > > > > IFormItemContentArea:
> >>> > > > ClassReference("org.apache.royale.jewel.Group")
> >>> > > > > > > >
> >>> > > > > > > > These are the parts important to me.
> >>> > > > > > > >
> >>> > > > > > > > I think we really want to change only the IBeadView, so
> we
> >>> can
> >>> > > > have a
> >>> > > > > > > > FormItemView and a StackedFormItemView, and could change
> >>> it vía
> >>> > > > > > className
> >>> > > > > > > > (for example)
> >>> > > > > > > >
> >>> > > > > > > > Let me know your thought about it
> >>> > > > > > > >
> >>> > > > > > > > thanks
> >>> > > > > > > >
> >>> > > > > > > > Carlos
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> >>> > > > > > > > piotrzarzycki21@gmail.com>) escribió:
> >>> > > > > > > >
> >>> > > > > > > >> Carlos,
> >>> > > > > > > >>
> >>> > > > > > > >> I have analyzed FormItem in Flex and here is how it is
> >>> done
> >>> > > there.
> >>> > > > > > > >> StackedFormItemSkin is using FormItemLayout which is
> >>> > constrained
> >>> > > > > into
> >>> > > > > > 3
> >>> > > > > > > >> columns (sequenceCol, contentCol and helpCol) and 2
> rows.
> >>> > [1][2]
> >>> > > > > > > >>
> >>> > > > > > > >> When you look into the screenshot [2] you may think that
> >>> > reuired
> >>> > > > > > > indicator
> >>> > > > > > > >> is part of the content, but it's not. It's not even part
> >>> of
> >>> > the
> >>> > > > > layout
> >>> > > > > > > >> cause it has includeInLayout="false". [3]
> >>> > > > > > > >> In Royale we don't have concept that something doesn't
> >>> belong
> >>> > to
> >>> > > > > > layout
> >>> > > > > > > >> and
> >>> > > > > > > >> is not calculated and indicator default is being placed
> in
> >>> > > > different
> >>> > > > > > > area.
> >>> > > > > > > >> Do you have some idea apart what I have proposed how to
> >>> > resolve
> >>> > > > > that ?
> >>> > > > > > > >>
> >>> > > > > > > >> [1] https://paste.apache.org/9Imj
> >>> > > > > > > >> [2] https://imgur.com/GGOtzEU
> >>> > > > > > > >> [3] https://paste.apache.org/kqlP
> >>> > > > > > > >>
> >>> > > > > > > >> Thanks,
> >>> > > > > > > >> Piotr
> >>> > > > > > > >>
> >>> > > > > > > >>
> >>> > > > > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
> >>> > > > piotrzarzycki21@gmail.com>
> >>> > > > > > > >> napisał(a):
> >>> > > > > > > >>
> >>> > > > > > > >> > That's more clear to me. I will check and get back to
> >>> you.
> >>> > > > > > > >> >
> >>> > > > > > > >> > Thank you!
> >>> > > > > > > >> >
> >>> > > > > > > >> >
> >>> > > > > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <
> >>> > > carlosrovira@apache.org
> >>> > > > >
> >>> > > > > > > >> > napisał(a):
> >>> > > > > > > >> >
> >>> > > > > > > >> >> No,
> >>> > > > > > > >> >>
> >>> > > > > > > >> >> I was asking you about how flex solves visualy the
> >>> problem
> >>> > in
> >>> > > > > their
> >>> > > > > > > >> >> stacked
> >>> > > > > > > >> >> version. The required icon is setup next to the
> label?
> >>> is
> >>> > in
> >>> > > > > other
> >>> > > > > > > >> place?
> >>> > > > > > > >> >> if we had an image of how it is designed (and like
> >>> it), we
> >>> > > can
> >>> > > > > copy
> >>> > > > > > > >> it. I
> >>> > > > > > > >> >> still not proposing a technical solution. Just that I
> >>> don't
> >>> > > > have
> >>> > > > > > > clear
> >>> > > > > > > >> how
> >>> > > > > > > >> >> we should layout it
> >>> > > > > > > >> >>
> >>> > > > > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
> >>> > > > > > > >> >> piotrzarzycki21@gmail.com>) escribió:
> >>> > > > > > > >> >>
> >>> > > > > > > >> >> > Carlos,
> >>> > > > > > > >> >> >
> >>> > > > > > > >> >> > Your suggestion is to have new form item
> >>> > (StackedFormItem)
> >>> > > > with
> >>> > > > > > new
> >>> > > > > > > >> >> > StackedFormItemView - cause problem is inside
> >>> > FormitemView,
> >>> > > > not
> >>> > > > > > > >> inside
> >>> > > > > > > >> >> > layout itself. Current layout is doing what it
> >>> should do
> >>> > -
> >>> > > > > apart
> >>> > > > > > of
> >>> > > > > > > >> the
> >>> > > > > > > >> >> > problem - it's making children to be
> >>> Horizontal/Vertical.
> >>> > > > > > > >> >> >
> >>> > > > > > > >> >> > If I'm correct what you are saying - that's ok, but
> >>> if
> >>> > you
> >>> > > > have
> >>> > > > > > had
> >>> > > > > > > >> >> > different idea by saying above let me know.
> >>> > > > > > > >> >> >
> >>> > > > > > > >> >> > Thanks, Piotr
> >>> > > > > > > >> >> >
> >>> > > > > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
> >>> > > > > carlosrovira@apache.org>
> >>> > > > > > > >> >> > napisał(a):
> >>> > > > > > > >> >> >
> >>> > > > > > > >> >> > > Ok, I understand now.
> >>> > > > > > > >> >> > >
> >>> > > > > > > >> >> > > In Flex I think we had that layout and was
> >>> > > > > > > >> called....StackedFormItem
> >>> > > > > > > >> >> or
> >>> > > > > > > >> >> > > something like that?
> >>> > > > > > > >> >> > > Could you check how Flex solve this? If we
> continue
> >>> > > liking
> >>> > > > > the
> >>> > > > > > > way
> >>> > > > > > > >> >> > stacked
> >>> > > > > > > >> >> > > form layout in flex looks, we can do the same for
> >>> our
> >>> > > > Royale
> >>> > > > > > > >> version
> >>> > > > > > > >> >> > >
> >>> > > > > > > >> >> > >
> >>> > > > > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki
> >>> (<
> >>> > > > > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
> >>> > > > > > > >> >> > >
> >>> > > > > > > >> >> > > > I'm not sure how Serkan is doing that on users
> >>> forum,
> >>> > > > but I
> >>> > > > > > see
> >>> > > > > > > >> all
> >>> > > > > > > >> >> > hist
> >>> > > > > > > >> >> > > > pasted images. Anyway here you go:
> >>> > > > > > > >> >> > > >
> >>> > > > > > > >> >> > > > What I wanted to achieve:
> >>> https://snag.gy/DmH7yk.jpg
> >>> > > > > > > >> >> > > > What I got from Jewel FormItem:
> >>> > > > https://snag.gy/Slfbt9.jpg
> >>> > > > > > > >> >> > > >
> >>> > > > > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
> >>> > > > > > > carlosrovira@apache.org>
> >>> > > > > > > >> >> > > > napisał(a):
> >>> > > > > > > >> >> > > >
> >>> > > > > > > >> >> > > > > Piotr,
> >>> > > > > > > >> >> > > > >
> >>> > > > > > > >> >> > > > > remember that images pasted in list are not
> >>> shared,
> >>> > > you
> >>> > > > > > must
> >>> > > > > > > >> share
> >>> > > > > > > >> >> > with
> >>> > > > > > > >> >> > > > > some image service
> >>> > > > > > > >> >> > > > >
> >>> > > > > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr
> >>> Zarzycki
> >>> > (<
> >>> > > > > > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> >>> > > > > > > >> >> > > > >
> >>> > > > > > > >> >> > > > > > There is one more problem with Layout.
> >>> Currently
> >>> > > > > default
> >>> > > > > > in
> >>> > > > > > > >> >> > framework
> >>> > > > > > > >> >> > > > we
> >>> > > > > > > >> >> > > > > > have [1]. It means that:
> >>> > > > > > > >> >> > > > > >
> >>> > > > > > > >> >> > > > > > My content of FormItem will be vertical and
> >>> > > > IBeadLayout
> >>> > > > > > is
> >>> > > > > > > >> >> > basically
> >>> > > > > > > >> >> > > > > > ignored at some point. If I specify beads -
> >>> > > > > > > HorizontalLayout
> >>> > > > > > > >> as
> >>> > > > > > > >> >> it
> >>> > > > > > > >> >> > is
> >>> > > > > > > >> >> > > > in
> >>> > > > > > > >> >> > > > > > above example it will be taken as a primary
> >>> and I
> >>> > > > have
> >>> > > > > my
> >>> > > > > > > >> >> content
> >>> > > > > > > >> >> > > > laying
> >>> > > > > > > >> >> > > > > > out horizontally. The question is - what is
> >>> for
> >>> > > > > > > >> >> IFormItemLayout in
> >>> > > > > > > >> >> > > > > > default.css? Is it a bug?
> >>> > > > > > > >> >> > > > > >
> >>> > > > > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
> >>> > > > > > > >> >> > > > > >
> >>> > > > > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> >>> > > > > > > >> >> piotrzarzycki21@gmail.com
> >>> > > > > > > >> >> > >
> >>> > > > > > > >> >> > > > > > napisał(a):
> >>> > > > > > > >> >> > > > > >
> >>> > > > > > > >> >> > > > > >> Hi Carlos,
> >>> > > > > > > >> >> > > > > >>
> >>> > > > > > > >> >> > > > > >> I'm was trying to change FormItem to be
> >>> Vertical
> >>> > > > > > oriented.
> >>> > > > > > > >> In
> >>> > > > > > > >> >> > > general
> >>> > > > > > > >> >> > > > I
> >>> > > > > > > >> >> > > > > >> would like to have following view. Label
> of
> >>> > > FormItem
> >>> > > > > is
> >>> > > > > > on
> >>> > > > > > > >> the
> >>> > > > > > > >> >> top
> >>> > > > > > > >> >> > > and
> >>> > > > > > > >> >> > > > > in
> >>> > > > > > > >> >> > > > > >> the bottom is content.
> >>> > > > > > > >> >> > > > > >>
> >>> > > > > > > >> >> > > > > >> [image: image.png]
> >>> > > > > > > >> >> > > > > >>
> >>> > > > > > > >> >> > > > > >> Code for that will looks like that [1].
> >>> Results
> >>> > is
> >>> > > > > > > >> following:
> >>> > > > > > > >> >> > > > > >>
> >>> > > > > > > >> >> > > > > >> [image: image.png]
> >>> > > > > > > >> >> > > > > >>
> >>> > > > > > > >> >> > > > > >> It happened cause Label and required star
> >>> label
> >>> > > are
> >>> > > > > > > >> different
> >>> > > > > > > >> >> > > > components
> >>> > > > > > > >> >> > > > > >> - everything is being laying out
> vertically.
> >>> > What
> >>> > > is
> >>> > > > > > your
> >>> > > > > > > >> >> > suggestion
> >>> > > > > > > >> >> > > > to
> >>> > > > > > > >> >> > > > > fix
> >>> > > > > > > >> >> > > > > >> that ?
> >>> > > > > > > >> >> > > > > >>
> >>> > > > > > > >> >> > > > > >> Mine is wrapping "First name" and "*" into
> >>> one
> >>> > > Group
> >>> > > > > > with
> >>> > > > > > > >> >> > > > > >> HorizontalLayout.
> >>> > > > > > > >> >> > > > > >>
> >>> > > > > > > >> >> > > > > >> More thoughts are welcome. I hope you see
> >>> > > > screenshots.
> >>> > > > > > :)
> >>> > > > > > > >> >> > > > > >>
> >>> > > > > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
> >>> > > > > > > >> >> > > > > >>
> >>> > > > > > > >> >> > > > > >> Thanks,
> >>> > > > > > > >> >> > > > > >> --
> >>> > > > > > > >> >> > > > > >>
> >>> > > > > > > >> >> > > > > >> Piotr Zarzycki
> >>> > > > > > > >> >> > > > > >>
> >>> > > > > > > >> >> > > > > >> Patreon: *
> >>> https://www.patreon.com/piotrzarzycki
> >>> > > > > > > >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> >>> > > > > > > >> >> > > > > >>
> >>> > > > > > > >> >> > > > > >
> >>> > > > > > > >> >> > > > > >
> >>> > > > > > > >> >> > > > > > --
> >>> > > > > > > >> >> > > > > >
> >>> > > > > > > >> >> > > > > > Piotr Zarzycki
> >>> > > > > > > >> >> > > > > >
> >>> > > > > > > >> >> > > > > > Patreon: *
> >>> https://www.patreon.com/piotrzarzycki
> >>> > > > > > > >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
> >>> > > > > > > >> >> > > > > >
> >>> > > > > > > >> >> > > > >
> >>> > > > > > > >> >> > > > >
> >>> > > > > > > >> >> > > > > --
> >>> > > > > > > >> >> > > > > Carlos Rovira
> >>> > > > > > > >> >> > > > > http://about.me/carlosrovira
> >>> > > > > > > >> >> > > > >
> >>> > > > > > > >> >> > > >
> >>> > > > > > > >> >> > > >
> >>> > > > > > > >> >> > > > --
> >>> > > > > > > >> >> > > >
> >>> > > > > > > >> >> > > > Piotr Zarzycki
> >>> > > > > > > >> >> > > >
> >>> > > > > > > >> >> > > > Patreon: *
> https://www.patreon.com/piotrzarzycki
> >>> > > > > > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
> >>> > > > > > > >> >> > > >
> >>> > > > > > > >> >> > >
> >>> > > > > > > >> >> > >
> >>> > > > > > > >> >> > > --
> >>> > > > > > > >> >> > > Carlos Rovira
> >>> > > > > > > >> >> > > http://about.me/carlosrovira
> >>> > > > > > > >> >> > >
> >>> > > > > > > >> >> >
> >>> > > > > > > >> >> >
> >>> > > > > > > >> >> > --
> >>> > > > > > > >> >> >
> >>> > > > > > > >> >> > Piotr Zarzycki
> >>> > > > > > > >> >> >
> >>> > > > > > > >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> >>> > > > > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
> >>> > > > > > > >> >> >
> >>> > > > > > > >> >>
> >>> > > > > > > >> >>
> >>> > > > > > > >> >> --
> >>> > > > > > > >> >> Carlos Rovira
> >>> > > > > > > >> >> http://about.me/carlosrovira
> >>> > > > > > > >> >>
> >>> > > > > > > >> >
> >>> > > > > > > >> >
> >>> > > > > > > >> > --
> >>> > > > > > > >> >
> >>> > > > > > > >> > Piotr Zarzycki
> >>> > > > > > > >> >
> >>> > > > > > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
> >>> > > > > > > >> > <https://www.patreon.com/piotrzarzycki>*
> >>> > > > > > > >> >
> >>> > > > > > > >>
> >>> > > > > > > >>
> >>> > > > > > > >> --
> >>> > > > > > > >>
> >>> > > > > > > >> Piotr Zarzycki
> >>> > > > > > > >>
> >>> > > > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> >>> > > > > > > >> <https://www.patreon.com/piotrzarzycki>*
> >>> > > > > > > >>
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > > > > > --
> >>> > > > > > > > Carlos Rovira
> >>> > > > > > > > http://about.me/carlosrovira
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > > > >
> >>> > > > > > > --
> >>> > > > > > > Carlos Rovira
> >>> > > > > > > http://about.me/carlosrovira
> >>> > > > > > >
> >>> > > > > >
> >>> > > > >
> >>> > > > >
> >>> > > > > --
> >>> > > > > Carlos Rovira
> >>> > > > > http://about.me/carlosrovira
> >>> > > > >
> >>> > > >
> >>> > > >
> >>> > > > --
> >>> > > >
> >>> > > > Piotr Zarzycki
> >>> > > >
> >>> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> >>> > > > <https://www.patreon.com/piotrzarzycki>*
> >>> > > >
> >>> > >
> >>> > >
> >>> > > --
> >>> > > Carlos Rovira
> >>> > > http://about.me/carlosrovira
> >>> > >
> >>> >
> >>> >
> >>> > --
> >>> >
> >>> > Piotr Zarzycki
> >>> >
> >>> > Patreon: *https://www.patreon.com/piotrzarzycki
> >>> > <https://www.patreon.com/piotrzarzycki>*
> >>> >
> >>>
> >>>
> >>> --
> >>> Carlos Rovira
> >>> http://about.me/carlosrovira
> >>>
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> <https://www.patreon.com/piotrzarzycki>*
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

Carlos,

I see following comment in FormItemView:

"// Look for a layout and/or viewport bead on the formItem's beads list. If
one

// is found, pull it off so it will not be added permanently
// to the strand."

Why beads from strand is being removed ? It's because it was reused in
other places ?

Thanks,

Piotr


pt., 25 sty 2019 o 16:24 Piotr Zarzycki <pi...@gmail.com>
napisał(a):

> And I forgot to add that IBeadLayout is working fine.
>
> pt., 25 sty 2019 o 16:23 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
>> I won't follow Flex, so if you would like to do this I'm fine. I'm going
>> to implement my own View in my application. I won't commit it to Royale.
>> However I would like to fix issue with layout. Currently IBeadLayout - Is
>> making whole FormItem vertical or horizontal. *IFormItemLayout - Should
>> treat content appropriately, but it doesn't do anything. I would like to
>> change it in the following way:*
>>
>> *IBeadLayout do:*
>>
>> *1) When user: IBeadLayout:
>> ClassReference("org.apache.royale.jewel.beads.layouts.VerticalLayout");*
>> L
>> C
>> *2) When user: **IBeadLayout:
>> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");*
>> *L C*
>>
>> *IFormItemLayout will do:*
>> 1) IFormItemLayout:
>> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
>> and #1 - *IBeadLayout*
>> L
>> C - Set children Horizotnally
>> 2) IFormItemLayout:
>> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
>> and #2 - *IBeadLayout*
>> *L*
>> *C - Set children Vertically*
>>
>> *Thoughts ?*
>>
>> Piotr
>>
>>
>>
>> pt., 25 sty 2019 o 16:13 Carlos Rovira <ca...@apache.org>
>> napisał(a):
>>
>>> Ops!,
>>>
>>> ok, since I was using the other layout I was in the believe that was the
>>> standard. So if we want to follow flex, we can change the current as
>>> well.
>>>
>>> El jue., 24 ene. 2019 a las 18:34, Piotr Zarzycki (<
>>> piotrzarzycki21@gmail.com>) escribió:
>>>
>>> > Nope - I just checked [1] - Code [2] - You are showing me some custom
>>> > implementation.
>>> >
>>> > [1] https://imgur.com/INKlfcC
>>> > [2] https://paste.apache.org/jyrl
>>> >
>>> > czw., 24 sty 2019 o 18:20 Carlos Rovira <ca...@apache.org>
>>> > napisał(a):
>>> >
>>> > > Piotr,
>>> > >
>>> > > in Flex we have the same align (as we have now in Royale), check this
>>> > > image: url
>>> > > <
>>> > >
>>> >
>>> https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249
>>> > > >
>>> > >
>>> > > El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
>>> > > piotrzarzycki21@gmail.com>) escribió:
>>> > >
>>> > > > If we are going in that direction it requires as well work were
>>> > indicator
>>> > > > in case of L* C (current implementation) will be changed to L C* -
>>> Yes
>>> > ?
>>> > > -
>>> > > > Being consistent it should be like that.
>>> > > >
>>> > > > I'm not sure what the trends are in that case.
>>> > > >
>>> > > > czw., 24 sty 2019 o 17:51 Carlos Rovira <ca...@apache.org>
>>> > > > napisał(a):
>>> > > >
>>> > > > > Hi Piotr,
>>> > > > >
>>> > > > > since is what you show in the flex version.
>>> > > > > I think Adobe put side to content instead of side to label since
>>> the
>>> > > user
>>> > > > > fill the content elements and if not filled and required , the
>>> > tooltip
>>> > > > > should popup there.
>>> > > > > IOW, for usability, seems more appropriated the way flex
>>> layedout, or
>>> > > > seems
>>> > > > > more natural.
>>> > > > >
>>> > > > > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
>>> > > > > piotrzarzycki21@gmail.com>) escribió:
>>> > > > >
>>> > > > > > Carlos,
>>> > > > > >
>>> > > > > > Why you are proposing have that?
>>> > > > > >
>>> > > > > > L
>>> > > > > > C *
>>> > > > > >
>>> > > > > > I'm in favor of staying
>>> > > > > >
>>> > > > > > L *
>>> > > > > > C
>>> > > > > >
>>> > > > > > Thanks,
>>> > > > > > Piotr
>>> > > > > >
>>> > > > > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <
>>> > carlosrovira@apache.org
>>> > > >
>>> > > > > > wrote:
>>> > > > > >
>>> > > > > > > I forgot to mention about IBeadLayout more, since it could be
>>> > > > > > > misinterpreted:
>>> > > > > > >
>>> > > > > > > IBeadLayout for the global component is important, but what
>>> I'm
>>> > > > > > considering
>>> > > > > > > is that although we can put HorizontalLayout (for the current
>>> > > > > FormtItem)
>>> > > > > > > and VerticalLayout (for the stacked), I'm seeing that many
>>> > > components
>>> > > > > > would
>>> > > > > > > need its own layout class. In this case we could create a
>>> > > > > FormItemLayout,
>>> > > > > > > and this will handle the layout vía CSS as it happens mostly
>>> in
>>> > > many
>>> > > > > > other
>>> > > > > > > Jewel component.
>>> > > > > > >
>>> > > > > > > (Just say that some of them are using an standard layout
>>> class,
>>> > > like
>>> > > > > > > HorizontalLayout, or even a NullLayout class), since I didn't
>>> > have
>>> > > > the
>>> > > > > > time
>>> > > > > > > to create its own one, and that's temporal. But my plan is to
>>> > > create
>>> > > > a
>>> > > > > > > concrete layout for some of this components. FormItem could
>>> be
>>> > one
>>> > > of
>>> > > > > > those
>>> > > > > > > cases, for what we're seeing
>>> > > > > > >
>>> > > > > > >
>>> > > > > > >
>>> > > > > > >
>>> > > > > > >
>>> > > > > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
>>> > > > > > carlosrovira@apache.org
>>> > > > > > > >)
>>> > > > > > > escribió:
>>> > > > > > >
>>> > > > > > > > Hi Piotr,
>>> > > > > > > >
>>> > > > > > > > looking at the screen shot, seems the required indicator is
>>> > > > > positioned
>>> > > > > > to
>>> > > > > > > > the right side of the element, what seems coherent,
>>> although
>>> > > could
>>> > > > > be a
>>> > > > > > > bit
>>> > > > > > > > problematic depending on the width of the component. we
>>> assume
>>> > a
>>> > > > > fixed
>>> > > > > > > > width (to the widest element) and align all required (or
>>> not a
>>> > > put
>>> > > > > the
>>> > > > > > > > required indicator just before the element, anyway this
>>> seems
>>> > > > > something
>>> > > > > > > to
>>> > > > > > > > be solved as we have some real implementation.
>>> > > > > > > >
>>> > > > > > > > In order to implement it:
>>> > > > > > > >
>>> > > > > > > > We have 3 parts:
>>> > > > > > > > - L (this is the label)
>>> > > > > > > > - * (this is the required indicator)
>>> > > > > > > > - C (this is the element(s) that the user adds)
>>> > > > > > > >
>>> > > > > > > > * Actual FormItem is :
>>> > > > > > > >
>>> > > > > > > > L * C
>>> > > > > > > >
>>> > > > > > > > * We want for the new
>>> > > > > > > >
>>> > > > > > > > L
>>> > > > > > > > C *
>>> > > > > > > >
>>> > > > > > > > So it seems to me that
>>> > > > > > > >
>>> > > > > > > > a) IBeadLayout: ClassReference(
>>> > > > > > > > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
>>> > > > > > > > Does not has much sense to me
>>> > > > > > > >
>>> > > > > > > > b) IFormItemLayout: ClassReference(
>>> > > > > > > > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
>>> > > > > > > >
>>> > > > > > > > This is the one important to me (to configure), so user can
>>> > > change
>>> > > > > > layout
>>> > > > > > > > of the content part
>>> > > > > > > >
>>> > > > > > > > c) IBeadView: ClassReference(
>>> > > > > > > > "org.apache.royale.jewel.beads.views.FormItemView")
>>> > > > > > > > IFormItemContentArea:
>>> > > > ClassReference("org.apache.royale.jewel.Group")
>>> > > > > > > >
>>> > > > > > > > These are the parts important to me.
>>> > > > > > > >
>>> > > > > > > > I think we really want to change only the IBeadView, so we
>>> can
>>> > > > have a
>>> > > > > > > > FormItemView and a StackedFormItemView, and could change
>>> it vía
>>> > > > > > className
>>> > > > > > > > (for example)
>>> > > > > > > >
>>> > > > > > > > Let me know your thought about it
>>> > > > > > > >
>>> > > > > > > > thanks
>>> > > > > > > >
>>> > > > > > > > Carlos
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
>>> > > > > > > > piotrzarzycki21@gmail.com>) escribió:
>>> > > > > > > >
>>> > > > > > > >> Carlos,
>>> > > > > > > >>
>>> > > > > > > >> I have analyzed FormItem in Flex and here is how it is
>>> done
>>> > > there.
>>> > > > > > > >> StackedFormItemSkin is using FormItemLayout which is
>>> > constrained
>>> > > > > into
>>> > > > > > 3
>>> > > > > > > >> columns (sequenceCol, contentCol and helpCol) and 2 rows.
>>> > [1][2]
>>> > > > > > > >>
>>> > > > > > > >> When you look into the screenshot [2] you may think that
>>> > reuired
>>> > > > > > > indicator
>>> > > > > > > >> is part of the content, but it's not. It's not even part
>>> of
>>> > the
>>> > > > > layout
>>> > > > > > > >> cause it has includeInLayout="false". [3]
>>> > > > > > > >> In Royale we don't have concept that something doesn't
>>> belong
>>> > to
>>> > > > > > layout
>>> > > > > > > >> and
>>> > > > > > > >> is not calculated and indicator default is being placed in
>>> > > > different
>>> > > > > > > area.
>>> > > > > > > >> Do you have some idea apart what I have proposed how to
>>> > resolve
>>> > > > > that ?
>>> > > > > > > >>
>>> > > > > > > >> [1] https://paste.apache.org/9Imj
>>> > > > > > > >> [2] https://imgur.com/GGOtzEU
>>> > > > > > > >> [3] https://paste.apache.org/kqlP
>>> > > > > > > >>
>>> > > > > > > >> Thanks,
>>> > > > > > > >> Piotr
>>> > > > > > > >>
>>> > > > > > > >>
>>> > > > > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
>>> > > > piotrzarzycki21@gmail.com>
>>> > > > > > > >> napisał(a):
>>> > > > > > > >>
>>> > > > > > > >> > That's more clear to me. I will check and get back to
>>> you.
>>> > > > > > > >> >
>>> > > > > > > >> > Thank you!
>>> > > > > > > >> >
>>> > > > > > > >> >
>>> > > > > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <
>>> > > carlosrovira@apache.org
>>> > > > >
>>> > > > > > > >> > napisał(a):
>>> > > > > > > >> >
>>> > > > > > > >> >> No,
>>> > > > > > > >> >>
>>> > > > > > > >> >> I was asking you about how flex solves visualy the
>>> problem
>>> > in
>>> > > > > their
>>> > > > > > > >> >> stacked
>>> > > > > > > >> >> version. The required icon is setup next to the label?
>>> is
>>> > in
>>> > > > > other
>>> > > > > > > >> place?
>>> > > > > > > >> >> if we had an image of how it is designed (and like
>>> it), we
>>> > > can
>>> > > > > copy
>>> > > > > > > >> it. I
>>> > > > > > > >> >> still not proposing a technical solution. Just that I
>>> don't
>>> > > > have
>>> > > > > > > clear
>>> > > > > > > >> how
>>> > > > > > > >> >> we should layout it
>>> > > > > > > >> >>
>>> > > > > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
>>> > > > > > > >> >> piotrzarzycki21@gmail.com>) escribió:
>>> > > > > > > >> >>
>>> > > > > > > >> >> > Carlos,
>>> > > > > > > >> >> >
>>> > > > > > > >> >> > Your suggestion is to have new form item
>>> > (StackedFormItem)
>>> > > > with
>>> > > > > > new
>>> > > > > > > >> >> > StackedFormItemView - cause problem is inside
>>> > FormitemView,
>>> > > > not
>>> > > > > > > >> inside
>>> > > > > > > >> >> > layout itself. Current layout is doing what it
>>> should do
>>> > -
>>> > > > > apart
>>> > > > > > of
>>> > > > > > > >> the
>>> > > > > > > >> >> > problem - it's making children to be
>>> Horizontal/Vertical.
>>> > > > > > > >> >> >
>>> > > > > > > >> >> > If I'm correct what you are saying - that's ok, but
>>> if
>>> > you
>>> > > > have
>>> > > > > > had
>>> > > > > > > >> >> > different idea by saying above let me know.
>>> > > > > > > >> >> >
>>> > > > > > > >> >> > Thanks, Piotr
>>> > > > > > > >> >> >
>>> > > > > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
>>> > > > > carlosrovira@apache.org>
>>> > > > > > > >> >> > napisał(a):
>>> > > > > > > >> >> >
>>> > > > > > > >> >> > > Ok, I understand now.
>>> > > > > > > >> >> > >
>>> > > > > > > >> >> > > In Flex I think we had that layout and was
>>> > > > > > > >> called....StackedFormItem
>>> > > > > > > >> >> or
>>> > > > > > > >> >> > > something like that?
>>> > > > > > > >> >> > > Could you check how Flex solve this? If we continue
>>> > > liking
>>> > > > > the
>>> > > > > > > way
>>> > > > > > > >> >> > stacked
>>> > > > > > > >> >> > > form layout in flex looks, we can do the same for
>>> our
>>> > > > Royale
>>> > > > > > > >> version
>>> > > > > > > >> >> > >
>>> > > > > > > >> >> > >
>>> > > > > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki
>>> (<
>>> > > > > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
>>> > > > > > > >> >> > >
>>> > > > > > > >> >> > > > I'm not sure how Serkan is doing that on users
>>> forum,
>>> > > > but I
>>> > > > > > see
>>> > > > > > > >> all
>>> > > > > > > >> >> > hist
>>> > > > > > > >> >> > > > pasted images. Anyway here you go:
>>> > > > > > > >> >> > > >
>>> > > > > > > >> >> > > > What I wanted to achieve:
>>> https://snag.gy/DmH7yk.jpg
>>> > > > > > > >> >> > > > What I got from Jewel FormItem:
>>> > > > https://snag.gy/Slfbt9.jpg
>>> > > > > > > >> >> > > >
>>> > > > > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
>>> > > > > > > carlosrovira@apache.org>
>>> > > > > > > >> >> > > > napisał(a):
>>> > > > > > > >> >> > > >
>>> > > > > > > >> >> > > > > Piotr,
>>> > > > > > > >> >> > > > >
>>> > > > > > > >> >> > > > > remember that images pasted in list are not
>>> shared,
>>> > > you
>>> > > > > > must
>>> > > > > > > >> share
>>> > > > > > > >> >> > with
>>> > > > > > > >> >> > > > > some image service
>>> > > > > > > >> >> > > > >
>>> > > > > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr
>>> Zarzycki
>>> > (<
>>> > > > > > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
>>> > > > > > > >> >> > > > >
>>> > > > > > > >> >> > > > > > There is one more problem with Layout.
>>> Currently
>>> > > > > default
>>> > > > > > in
>>> > > > > > > >> >> > framework
>>> > > > > > > >> >> > > > we
>>> > > > > > > >> >> > > > > > have [1]. It means that:
>>> > > > > > > >> >> > > > > >
>>> > > > > > > >> >> > > > > > My content of FormItem will be vertical and
>>> > > > IBeadLayout
>>> > > > > > is
>>> > > > > > > >> >> > basically
>>> > > > > > > >> >> > > > > > ignored at some point. If I specify beads -
>>> > > > > > > HorizontalLayout
>>> > > > > > > >> as
>>> > > > > > > >> >> it
>>> > > > > > > >> >> > is
>>> > > > > > > >> >> > > > in
>>> > > > > > > >> >> > > > > > above example it will be taken as a primary
>>> and I
>>> > > > have
>>> > > > > my
>>> > > > > > > >> >> content
>>> > > > > > > >> >> > > > laying
>>> > > > > > > >> >> > > > > > out horizontally. The question is - what is
>>> for
>>> > > > > > > >> >> IFormItemLayout in
>>> > > > > > > >> >> > > > > > default.css? Is it a bug?
>>> > > > > > > >> >> > > > > >
>>> > > > > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
>>> > > > > > > >> >> > > > > >
>>> > > > > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
>>> > > > > > > >> >> piotrzarzycki21@gmail.com
>>> > > > > > > >> >> > >
>>> > > > > > > >> >> > > > > > napisał(a):
>>> > > > > > > >> >> > > > > >
>>> > > > > > > >> >> > > > > >> Hi Carlos,
>>> > > > > > > >> >> > > > > >>
>>> > > > > > > >> >> > > > > >> I'm was trying to change FormItem to be
>>> Vertical
>>> > > > > > oriented.
>>> > > > > > > >> In
>>> > > > > > > >> >> > > general
>>> > > > > > > >> >> > > > I
>>> > > > > > > >> >> > > > > >> would like to have following view. Label of
>>> > > FormItem
>>> > > > > is
>>> > > > > > on
>>> > > > > > > >> the
>>> > > > > > > >> >> top
>>> > > > > > > >> >> > > and
>>> > > > > > > >> >> > > > > in
>>> > > > > > > >> >> > > > > >> the bottom is content.
>>> > > > > > > >> >> > > > > >>
>>> > > > > > > >> >> > > > > >> [image: image.png]
>>> > > > > > > >> >> > > > > >>
>>> > > > > > > >> >> > > > > >> Code for that will looks like that [1].
>>> Results
>>> > is
>>> > > > > > > >> following:
>>> > > > > > > >> >> > > > > >>
>>> > > > > > > >> >> > > > > >> [image: image.png]
>>> > > > > > > >> >> > > > > >>
>>> > > > > > > >> >> > > > > >> It happened cause Label and required star
>>> label
>>> > > are
>>> > > > > > > >> different
>>> > > > > > > >> >> > > > components
>>> > > > > > > >> >> > > > > >> - everything is being laying out vertically.
>>> > What
>>> > > is
>>> > > > > > your
>>> > > > > > > >> >> > suggestion
>>> > > > > > > >> >> > > > to
>>> > > > > > > >> >> > > > > fix
>>> > > > > > > >> >> > > > > >> that ?
>>> > > > > > > >> >> > > > > >>
>>> > > > > > > >> >> > > > > >> Mine is wrapping "First name" and "*" into
>>> one
>>> > > Group
>>> > > > > > with
>>> > > > > > > >> >> > > > > >> HorizontalLayout.
>>> > > > > > > >> >> > > > > >>
>>> > > > > > > >> >> > > > > >> More thoughts are welcome. I hope you see
>>> > > > screenshots.
>>> > > > > > :)
>>> > > > > > > >> >> > > > > >>
>>> > > > > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
>>> > > > > > > >> >> > > > > >>
>>> > > > > > > >> >> > > > > >> Thanks,
>>> > > > > > > >> >> > > > > >> --
>>> > > > > > > >> >> > > > > >>
>>> > > > > > > >> >> > > > > >> Piotr Zarzycki
>>> > > > > > > >> >> > > > > >>
>>> > > > > > > >> >> > > > > >> Patreon: *
>>> https://www.patreon.com/piotrzarzycki
>>> > > > > > > >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
>>> > > > > > > >> >> > > > > >>
>>> > > > > > > >> >> > > > > >
>>> > > > > > > >> >> > > > > >
>>> > > > > > > >> >> > > > > > --
>>> > > > > > > >> >> > > > > >
>>> > > > > > > >> >> > > > > > Piotr Zarzycki
>>> > > > > > > >> >> > > > > >
>>> > > > > > > >> >> > > > > > Patreon: *
>>> https://www.patreon.com/piotrzarzycki
>>> > > > > > > >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
>>> > > > > > > >> >> > > > > >
>>> > > > > > > >> >> > > > >
>>> > > > > > > >> >> > > > >
>>> > > > > > > >> >> > > > > --
>>> > > > > > > >> >> > > > > Carlos Rovira
>>> > > > > > > >> >> > > > > http://about.me/carlosrovira
>>> > > > > > > >> >> > > > >
>>> > > > > > > >> >> > > >
>>> > > > > > > >> >> > > >
>>> > > > > > > >> >> > > > --
>>> > > > > > > >> >> > > >
>>> > > > > > > >> >> > > > Piotr Zarzycki
>>> > > > > > > >> >> > > >
>>> > > > > > > >> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > > > > > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
>>> > > > > > > >> >> > > >
>>> > > > > > > >> >> > >
>>> > > > > > > >> >> > >
>>> > > > > > > >> >> > > --
>>> > > > > > > >> >> > > Carlos Rovira
>>> > > > > > > >> >> > > http://about.me/carlosrovira
>>> > > > > > > >> >> > >
>>> > > > > > > >> >> >
>>> > > > > > > >> >> >
>>> > > > > > > >> >> > --
>>> > > > > > > >> >> >
>>> > > > > > > >> >> > Piotr Zarzycki
>>> > > > > > > >> >> >
>>> > > > > > > >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > > > > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
>>> > > > > > > >> >> >
>>> > > > > > > >> >>
>>> > > > > > > >> >>
>>> > > > > > > >> >> --
>>> > > > > > > >> >> Carlos Rovira
>>> > > > > > > >> >> http://about.me/carlosrovira
>>> > > > > > > >> >>
>>> > > > > > > >> >
>>> > > > > > > >> >
>>> > > > > > > >> > --
>>> > > > > > > >> >
>>> > > > > > > >> > Piotr Zarzycki
>>> > > > > > > >> >
>>> > > > > > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > > > > > > >> > <https://www.patreon.com/piotrzarzycki>*
>>> > > > > > > >> >
>>> > > > > > > >>
>>> > > > > > > >>
>>> > > > > > > >> --
>>> > > > > > > >>
>>> > > > > > > >> Piotr Zarzycki
>>> > > > > > > >>
>>> > > > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
>>> > > > > > > >> <https://www.patreon.com/piotrzarzycki>*
>>> > > > > > > >>
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > > > --
>>> > > > > > > > Carlos Rovira
>>> > > > > > > > http://about.me/carlosrovira
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > >
>>> > > > > > > --
>>> > > > > > > Carlos Rovira
>>> > > > > > > http://about.me/carlosrovira
>>> > > > > > >
>>> > > > > >
>>> > > > >
>>> > > > >
>>> > > > > --
>>> > > > > Carlos Rovira
>>> > > > > http://about.me/carlosrovira
>>> > > > >
>>> > > >
>>> > > >
>>> > > > --
>>> > > >
>>> > > > Piotr Zarzycki
>>> > > >
>>> > > > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > > > <https://www.patreon.com/piotrzarzycki>*
>>> > > >
>>> > >
>>> > >
>>> > > --
>>> > > Carlos Rovira
>>> > > http://about.me/carlosrovira
>>> > >
>>> >
>>> >
>>> > --
>>> >
>>> > Piotr Zarzycki
>>> >
>>> > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > <https://www.patreon.com/piotrzarzycki>*
>>> >
>>>
>>>
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

And I forgot to add that IBeadLayout is working fine.

pt., 25 sty 2019 o 16:23 Piotr Zarzycki <pi...@gmail.com>
napisał(a):

> I won't follow Flex, so if you would like to do this I'm fine. I'm going
> to implement my own View in my application. I won't commit it to Royale.
> However I would like to fix issue with layout. Currently IBeadLayout - Is
> making whole FormItem vertical or horizontal. *IFormItemLayout - Should
> treat content appropriately, but it doesn't do anything. I would like to
> change it in the following way:*
>
> *IBeadLayout do:*
>
> *1) When user: IBeadLayout:
> ClassReference("org.apache.royale.jewel.beads.layouts.VerticalLayout");*
> L
> C
> *2) When user: **IBeadLayout:
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");*
> *L C*
>
> *IFormItemLayout will do:*
> 1) IFormItemLayout:
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> and #1 - *IBeadLayout*
> L
> C - Set children Horizotnally
> 2) IFormItemLayout:
> ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
> and #2 - *IBeadLayout*
> *L*
> *C - Set children Vertically*
>
> *Thoughts ?*
>
> Piotr
>
>
>
> pt., 25 sty 2019 o 16:13 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
>> Ops!,
>>
>> ok, since I was using the other layout I was in the believe that was the
>> standard. So if we want to follow flex, we can change the current as well.
>>
>> El jue., 24 ene. 2019 a las 18:34, Piotr Zarzycki (<
>> piotrzarzycki21@gmail.com>) escribió:
>>
>> > Nope - I just checked [1] - Code [2] - You are showing me some custom
>> > implementation.
>> >
>> > [1] https://imgur.com/INKlfcC
>> > [2] https://paste.apache.org/jyrl
>> >
>> > czw., 24 sty 2019 o 18:20 Carlos Rovira <ca...@apache.org>
>> > napisał(a):
>> >
>> > > Piotr,
>> > >
>> > > in Flex we have the same align (as we have now in Royale), check this
>> > > image: url
>> > > <
>> > >
>> >
>> https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249
>> > > >
>> > >
>> > > El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
>> > > piotrzarzycki21@gmail.com>) escribió:
>> > >
>> > > > If we are going in that direction it requires as well work were
>> > indicator
>> > > > in case of L* C (current implementation) will be changed to L C* -
>> Yes
>> > ?
>> > > -
>> > > > Being consistent it should be like that.
>> > > >
>> > > > I'm not sure what the trends are in that case.
>> > > >
>> > > > czw., 24 sty 2019 o 17:51 Carlos Rovira <ca...@apache.org>
>> > > > napisał(a):
>> > > >
>> > > > > Hi Piotr,
>> > > > >
>> > > > > since is what you show in the flex version.
>> > > > > I think Adobe put side to content instead of side to label since
>> the
>> > > user
>> > > > > fill the content elements and if not filled and required , the
>> > tooltip
>> > > > > should popup there.
>> > > > > IOW, for usability, seems more appropriated the way flex
>> layedout, or
>> > > > seems
>> > > > > more natural.
>> > > > >
>> > > > > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
>> > > > > piotrzarzycki21@gmail.com>) escribió:
>> > > > >
>> > > > > > Carlos,
>> > > > > >
>> > > > > > Why you are proposing have that?
>> > > > > >
>> > > > > > L
>> > > > > > C *
>> > > > > >
>> > > > > > I'm in favor of staying
>> > > > > >
>> > > > > > L *
>> > > > > > C
>> > > > > >
>> > > > > > Thanks,
>> > > > > > Piotr
>> > > > > >
>> > > > > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <
>> > carlosrovira@apache.org
>> > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > > > I forgot to mention about IBeadLayout more, since it could be
>> > > > > > > misinterpreted:
>> > > > > > >
>> > > > > > > IBeadLayout for the global component is important, but what
>> I'm
>> > > > > > considering
>> > > > > > > is that although we can put HorizontalLayout (for the current
>> > > > > FormtItem)
>> > > > > > > and VerticalLayout (for the stacked), I'm seeing that many
>> > > components
>> > > > > > would
>> > > > > > > need its own layout class. In this case we could create a
>> > > > > FormItemLayout,
>> > > > > > > and this will handle the layout vía CSS as it happens mostly
>> in
>> > > many
>> > > > > > other
>> > > > > > > Jewel component.
>> > > > > > >
>> > > > > > > (Just say that some of them are using an standard layout
>> class,
>> > > like
>> > > > > > > HorizontalLayout, or even a NullLayout class), since I didn't
>> > have
>> > > > the
>> > > > > > time
>> > > > > > > to create its own one, and that's temporal. But my plan is to
>> > > create
>> > > > a
>> > > > > > > concrete layout for some of this components. FormItem could be
>> > one
>> > > of
>> > > > > > those
>> > > > > > > cases, for what we're seeing
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
>> > > > > > carlosrovira@apache.org
>> > > > > > > >)
>> > > > > > > escribió:
>> > > > > > >
>> > > > > > > > Hi Piotr,
>> > > > > > > >
>> > > > > > > > looking at the screen shot, seems the required indicator is
>> > > > > positioned
>> > > > > > to
>> > > > > > > > the right side of the element, what seems coherent, although
>> > > could
>> > > > > be a
>> > > > > > > bit
>> > > > > > > > problematic depending on the width of the component. we
>> assume
>> > a
>> > > > > fixed
>> > > > > > > > width (to the widest element) and align all required (or
>> not a
>> > > put
>> > > > > the
>> > > > > > > > required indicator just before the element, anyway this
>> seems
>> > > > > something
>> > > > > > > to
>> > > > > > > > be solved as we have some real implementation.
>> > > > > > > >
>> > > > > > > > In order to implement it:
>> > > > > > > >
>> > > > > > > > We have 3 parts:
>> > > > > > > > - L (this is the label)
>> > > > > > > > - * (this is the required indicator)
>> > > > > > > > - C (this is the element(s) that the user adds)
>> > > > > > > >
>> > > > > > > > * Actual FormItem is :
>> > > > > > > >
>> > > > > > > > L * C
>> > > > > > > >
>> > > > > > > > * We want for the new
>> > > > > > > >
>> > > > > > > > L
>> > > > > > > > C *
>> > > > > > > >
>> > > > > > > > So it seems to me that
>> > > > > > > >
>> > > > > > > > a) IBeadLayout: ClassReference(
>> > > > > > > > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
>> > > > > > > > Does not has much sense to me
>> > > > > > > >
>> > > > > > > > b) IFormItemLayout: ClassReference(
>> > > > > > > > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
>> > > > > > > >
>> > > > > > > > This is the one important to me (to configure), so user can
>> > > change
>> > > > > > layout
>> > > > > > > > of the content part
>> > > > > > > >
>> > > > > > > > c) IBeadView: ClassReference(
>> > > > > > > > "org.apache.royale.jewel.beads.views.FormItemView")
>> > > > > > > > IFormItemContentArea:
>> > > > ClassReference("org.apache.royale.jewel.Group")
>> > > > > > > >
>> > > > > > > > These are the parts important to me.
>> > > > > > > >
>> > > > > > > > I think we really want to change only the IBeadView, so we
>> can
>> > > > have a
>> > > > > > > > FormItemView and a StackedFormItemView, and could change it
>> vía
>> > > > > > className
>> > > > > > > > (for example)
>> > > > > > > >
>> > > > > > > > Let me know your thought about it
>> > > > > > > >
>> > > > > > > > thanks
>> > > > > > > >
>> > > > > > > > Carlos
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
>> > > > > > > > piotrzarzycki21@gmail.com>) escribió:
>> > > > > > > >
>> > > > > > > >> Carlos,
>> > > > > > > >>
>> > > > > > > >> I have analyzed FormItem in Flex and here is how it is done
>> > > there.
>> > > > > > > >> StackedFormItemSkin is using FormItemLayout which is
>> > constrained
>> > > > > into
>> > > > > > 3
>> > > > > > > >> columns (sequenceCol, contentCol and helpCol) and 2 rows.
>> > [1][2]
>> > > > > > > >>
>> > > > > > > >> When you look into the screenshot [2] you may think that
>> > reuired
>> > > > > > > indicator
>> > > > > > > >> is part of the content, but it's not. It's not even part of
>> > the
>> > > > > layout
>> > > > > > > >> cause it has includeInLayout="false". [3]
>> > > > > > > >> In Royale we don't have concept that something doesn't
>> belong
>> > to
>> > > > > > layout
>> > > > > > > >> and
>> > > > > > > >> is not calculated and indicator default is being placed in
>> > > > different
>> > > > > > > area.
>> > > > > > > >> Do you have some idea apart what I have proposed how to
>> > resolve
>> > > > > that ?
>> > > > > > > >>
>> > > > > > > >> [1] https://paste.apache.org/9Imj
>> > > > > > > >> [2] https://imgur.com/GGOtzEU
>> > > > > > > >> [3] https://paste.apache.org/kqlP
>> > > > > > > >>
>> > > > > > > >> Thanks,
>> > > > > > > >> Piotr
>> > > > > > > >>
>> > > > > > > >>
>> > > > > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
>> > > > piotrzarzycki21@gmail.com>
>> > > > > > > >> napisał(a):
>> > > > > > > >>
>> > > > > > > >> > That's more clear to me. I will check and get back to
>> you.
>> > > > > > > >> >
>> > > > > > > >> > Thank you!
>> > > > > > > >> >
>> > > > > > > >> >
>> > > > > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <
>> > > carlosrovira@apache.org
>> > > > >
>> > > > > > > >> > napisał(a):
>> > > > > > > >> >
>> > > > > > > >> >> No,
>> > > > > > > >> >>
>> > > > > > > >> >> I was asking you about how flex solves visualy the
>> problem
>> > in
>> > > > > their
>> > > > > > > >> >> stacked
>> > > > > > > >> >> version. The required icon is setup next to the label?
>> is
>> > in
>> > > > > other
>> > > > > > > >> place?
>> > > > > > > >> >> if we had an image of how it is designed (and like it),
>> we
>> > > can
>> > > > > copy
>> > > > > > > >> it. I
>> > > > > > > >> >> still not proposing a technical solution. Just that I
>> don't
>> > > > have
>> > > > > > > clear
>> > > > > > > >> how
>> > > > > > > >> >> we should layout it
>> > > > > > > >> >>
>> > > > > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
>> > > > > > > >> >> piotrzarzycki21@gmail.com>) escribió:
>> > > > > > > >> >>
>> > > > > > > >> >> > Carlos,
>> > > > > > > >> >> >
>> > > > > > > >> >> > Your suggestion is to have new form item
>> > (StackedFormItem)
>> > > > with
>> > > > > > new
>> > > > > > > >> >> > StackedFormItemView - cause problem is inside
>> > FormitemView,
>> > > > not
>> > > > > > > >> inside
>> > > > > > > >> >> > layout itself. Current layout is doing what it should
>> do
>> > -
>> > > > > apart
>> > > > > > of
>> > > > > > > >> the
>> > > > > > > >> >> > problem - it's making children to be
>> Horizontal/Vertical.
>> > > > > > > >> >> >
>> > > > > > > >> >> > If I'm correct what you are saying - that's ok, but if
>> > you
>> > > > have
>> > > > > > had
>> > > > > > > >> >> > different idea by saying above let me know.
>> > > > > > > >> >> >
>> > > > > > > >> >> > Thanks, Piotr
>> > > > > > > >> >> >
>> > > > > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
>> > > > > carlosrovira@apache.org>
>> > > > > > > >> >> > napisał(a):
>> > > > > > > >> >> >
>> > > > > > > >> >> > > Ok, I understand now.
>> > > > > > > >> >> > >
>> > > > > > > >> >> > > In Flex I think we had that layout and was
>> > > > > > > >> called....StackedFormItem
>> > > > > > > >> >> or
>> > > > > > > >> >> > > something like that?
>> > > > > > > >> >> > > Could you check how Flex solve this? If we continue
>> > > liking
>> > > > > the
>> > > > > > > way
>> > > > > > > >> >> > stacked
>> > > > > > > >> >> > > form layout in flex looks, we can do the same for
>> our
>> > > > Royale
>> > > > > > > >> version
>> > > > > > > >> >> > >
>> > > > > > > >> >> > >
>> > > > > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
>> > > > > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
>> > > > > > > >> >> > >
>> > > > > > > >> >> > > > I'm not sure how Serkan is doing that on users
>> forum,
>> > > > but I
>> > > > > > see
>> > > > > > > >> all
>> > > > > > > >> >> > hist
>> > > > > > > >> >> > > > pasted images. Anyway here you go:
>> > > > > > > >> >> > > >
>> > > > > > > >> >> > > > What I wanted to achieve:
>> https://snag.gy/DmH7yk.jpg
>> > > > > > > >> >> > > > What I got from Jewel FormItem:
>> > > > https://snag.gy/Slfbt9.jpg
>> > > > > > > >> >> > > >
>> > > > > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
>> > > > > > > carlosrovira@apache.org>
>> > > > > > > >> >> > > > napisał(a):
>> > > > > > > >> >> > > >
>> > > > > > > >> >> > > > > Piotr,
>> > > > > > > >> >> > > > >
>> > > > > > > >> >> > > > > remember that images pasted in list are not
>> shared,
>> > > you
>> > > > > > must
>> > > > > > > >> share
>> > > > > > > >> >> > with
>> > > > > > > >> >> > > > > some image service
>> > > > > > > >> >> > > > >
>> > > > > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr
>> Zarzycki
>> > (<
>> > > > > > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
>> > > > > > > >> >> > > > >
>> > > > > > > >> >> > > > > > There is one more problem with Layout.
>> Currently
>> > > > > default
>> > > > > > in
>> > > > > > > >> >> > framework
>> > > > > > > >> >> > > > we
>> > > > > > > >> >> > > > > > have [1]. It means that:
>> > > > > > > >> >> > > > > >
>> > > > > > > >> >> > > > > > My content of FormItem will be vertical and
>> > > > IBeadLayout
>> > > > > > is
>> > > > > > > >> >> > basically
>> > > > > > > >> >> > > > > > ignored at some point. If I specify beads -
>> > > > > > > HorizontalLayout
>> > > > > > > >> as
>> > > > > > > >> >> it
>> > > > > > > >> >> > is
>> > > > > > > >> >> > > > in
>> > > > > > > >> >> > > > > > above example it will be taken as a primary
>> and I
>> > > > have
>> > > > > my
>> > > > > > > >> >> content
>> > > > > > > >> >> > > > laying
>> > > > > > > >> >> > > > > > out horizontally. The question is - what is
>> for
>> > > > > > > >> >> IFormItemLayout in
>> > > > > > > >> >> > > > > > default.css? Is it a bug?
>> > > > > > > >> >> > > > > >
>> > > > > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
>> > > > > > > >> >> > > > > >
>> > > > > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
>> > > > > > > >> >> piotrzarzycki21@gmail.com
>> > > > > > > >> >> > >
>> > > > > > > >> >> > > > > > napisał(a):
>> > > > > > > >> >> > > > > >
>> > > > > > > >> >> > > > > >> Hi Carlos,
>> > > > > > > >> >> > > > > >>
>> > > > > > > >> >> > > > > >> I'm was trying to change FormItem to be
>> Vertical
>> > > > > > oriented.
>> > > > > > > >> In
>> > > > > > > >> >> > > general
>> > > > > > > >> >> > > > I
>> > > > > > > >> >> > > > > >> would like to have following view. Label of
>> > > FormItem
>> > > > > is
>> > > > > > on
>> > > > > > > >> the
>> > > > > > > >> >> top
>> > > > > > > >> >> > > and
>> > > > > > > >> >> > > > > in
>> > > > > > > >> >> > > > > >> the bottom is content.
>> > > > > > > >> >> > > > > >>
>> > > > > > > >> >> > > > > >> [image: image.png]
>> > > > > > > >> >> > > > > >>
>> > > > > > > >> >> > > > > >> Code for that will looks like that [1].
>> Results
>> > is
>> > > > > > > >> following:
>> > > > > > > >> >> > > > > >>
>> > > > > > > >> >> > > > > >> [image: image.png]
>> > > > > > > >> >> > > > > >>
>> > > > > > > >> >> > > > > >> It happened cause Label and required star
>> label
>> > > are
>> > > > > > > >> different
>> > > > > > > >> >> > > > components
>> > > > > > > >> >> > > > > >> - everything is being laying out vertically.
>> > What
>> > > is
>> > > > > > your
>> > > > > > > >> >> > suggestion
>> > > > > > > >> >> > > > to
>> > > > > > > >> >> > > > > fix
>> > > > > > > >> >> > > > > >> that ?
>> > > > > > > >> >> > > > > >>
>> > > > > > > >> >> > > > > >> Mine is wrapping "First name" and "*" into
>> one
>> > > Group
>> > > > > > with
>> > > > > > > >> >> > > > > >> HorizontalLayout.
>> > > > > > > >> >> > > > > >>
>> > > > > > > >> >> > > > > >> More thoughts are welcome. I hope you see
>> > > > screenshots.
>> > > > > > :)
>> > > > > > > >> >> > > > > >>
>> > > > > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
>> > > > > > > >> >> > > > > >>
>> > > > > > > >> >> > > > > >> Thanks,
>> > > > > > > >> >> > > > > >> --
>> > > > > > > >> >> > > > > >>
>> > > > > > > >> >> > > > > >> Piotr Zarzycki
>> > > > > > > >> >> > > > > >>
>> > > > > > > >> >> > > > > >> Patreon: *
>> https://www.patreon.com/piotrzarzycki
>> > > > > > > >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
>> > > > > > > >> >> > > > > >>
>> > > > > > > >> >> > > > > >
>> > > > > > > >> >> > > > > >
>> > > > > > > >> >> > > > > > --
>> > > > > > > >> >> > > > > >
>> > > > > > > >> >> > > > > > Piotr Zarzycki
>> > > > > > > >> >> > > > > >
>> > > > > > > >> >> > > > > > Patreon: *
>> https://www.patreon.com/piotrzarzycki
>> > > > > > > >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
>> > > > > > > >> >> > > > > >
>> > > > > > > >> >> > > > >
>> > > > > > > >> >> > > > >
>> > > > > > > >> >> > > > > --
>> > > > > > > >> >> > > > > Carlos Rovira
>> > > > > > > >> >> > > > > http://about.me/carlosrovira
>> > > > > > > >> >> > > > >
>> > > > > > > >> >> > > >
>> > > > > > > >> >> > > >
>> > > > > > > >> >> > > > --
>> > > > > > > >> >> > > >
>> > > > > > > >> >> > > > Piotr Zarzycki
>> > > > > > > >> >> > > >
>> > > > > > > >> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
>> > > > > > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
>> > > > > > > >> >> > > >
>> > > > > > > >> >> > >
>> > > > > > > >> >> > >
>> > > > > > > >> >> > > --
>> > > > > > > >> >> > > Carlos Rovira
>> > > > > > > >> >> > > http://about.me/carlosrovira
>> > > > > > > >> >> > >
>> > > > > > > >> >> >
>> > > > > > > >> >> >
>> > > > > > > >> >> > --
>> > > > > > > >> >> >
>> > > > > > > >> >> > Piotr Zarzycki
>> > > > > > > >> >> >
>> > > > > > > >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
>> > > > > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
>> > > > > > > >> >> >
>> > > > > > > >> >>
>> > > > > > > >> >>
>> > > > > > > >> >> --
>> > > > > > > >> >> Carlos Rovira
>> > > > > > > >> >> http://about.me/carlosrovira
>> > > > > > > >> >>
>> > > > > > > >> >
>> > > > > > > >> >
>> > > > > > > >> > --
>> > > > > > > >> >
>> > > > > > > >> > Piotr Zarzycki
>> > > > > > > >> >
>> > > > > > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
>> > > > > > > >> > <https://www.patreon.com/piotrzarzycki>*
>> > > > > > > >> >
>> > > > > > > >>
>> > > > > > > >>
>> > > > > > > >> --
>> > > > > > > >>
>> > > > > > > >> Piotr Zarzycki
>> > > > > > > >>
>> > > > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
>> > > > > > > >> <https://www.patreon.com/piotrzarzycki>*
>> > > > > > > >>
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > --
>> > > > > > > > Carlos Rovira
>> > > > > > > > http://about.me/carlosrovira
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > > > --
>> > > > > > > Carlos Rovira
>> > > > > > > http://about.me/carlosrovira
>> > > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Carlos Rovira
>> > > > > http://about.me/carlosrovira
>> > > > >
>> > > >
>> > > >
>> > > > --
>> > > >
>> > > > Piotr Zarzycki
>> > > >
>> > > > Patreon: *https://www.patreon.com/piotrzarzycki
>> > > > <https://www.patreon.com/piotrzarzycki>*
>> > > >
>> > >
>> > >
>> > > --
>> > > Carlos Rovira
>> > > http://about.me/carlosrovira
>> > >
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: *https://www.patreon.com/piotrzarzycki
>> > <https://www.patreon.com/piotrzarzycki>*
>> >
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

I won't follow Flex, so if you would like to do this I'm fine. I'm going to
implement my own View in my application. I won't commit it to Royale.
However I would like to fix issue with layout. Currently IBeadLayout - Is
making whole FormItem vertical or horizontal. *IFormItemLayout - Should
treat content appropriately, but it doesn't do anything. I would like to
change it in the following way:*

*IBeadLayout do:*

*1) When user: IBeadLayout:
ClassReference("org.apache.royale.jewel.beads.layouts.VerticalLayout");*
L
C
*2) When user: **IBeadLayout:
ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");*
*L C*

*IFormItemLayout will do:*
1) IFormItemLayout:
ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
and #1 - *IBeadLayout*
L
C - Set children Horizotnally
2) IFormItemLayout:
ClassReference("org.apache.royale.jewel.beads.layouts.HorizontalLayout");
and #2 - *IBeadLayout*
*L*
*C - Set children Vertically*

*Thoughts ?*

Piotr



pt., 25 sty 2019 o 16:13 Carlos Rovira <ca...@apache.org> napisał(a):

> Ops!,
>
> ok, since I was using the other layout I was in the believe that was the
> standard. So if we want to follow flex, we can change the current as well.
>
> El jue., 24 ene. 2019 a las 18:34, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > Nope - I just checked [1] - Code [2] - You are showing me some custom
> > implementation.
> >
> > [1] https://imgur.com/INKlfcC
> > [2] https://paste.apache.org/jyrl
> >
> > czw., 24 sty 2019 o 18:20 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> > > Piotr,
> > >
> > > in Flex we have the same align (as we have now in Royale), check this
> > > image: url
> > > <
> > >
> >
> https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249
> > > >
> > >
> > > El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
> > > piotrzarzycki21@gmail.com>) escribió:
> > >
> > > > If we are going in that direction it requires as well work were
> > indicator
> > > > in case of L* C (current implementation) will be changed to L C* -
> Yes
> > ?
> > > -
> > > > Being consistent it should be like that.
> > > >
> > > > I'm not sure what the trends are in that case.
> > > >
> > > > czw., 24 sty 2019 o 17:51 Carlos Rovira <ca...@apache.org>
> > > > napisał(a):
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > since is what you show in the flex version.
> > > > > I think Adobe put side to content instead of side to label since
> the
> > > user
> > > > > fill the content elements and if not filled and required , the
> > tooltip
> > > > > should popup there.
> > > > > IOW, for usability, seems more appropriated the way flex layedout,
> or
> > > > seems
> > > > > more natural.
> > > > >
> > > > > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > >
> > > > > > Carlos,
> > > > > >
> > > > > > Why you are proposing have that?
> > > > > >
> > > > > > L
> > > > > > C *
> > > > > >
> > > > > > I'm in favor of staying
> > > > > >
> > > > > > L *
> > > > > > C
> > > > > >
> > > > > > Thanks,
> > > > > > Piotr
> > > > > >
> > > > > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <
> > carlosrovira@apache.org
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > I forgot to mention about IBeadLayout more, since it could be
> > > > > > > misinterpreted:
> > > > > > >
> > > > > > > IBeadLayout for the global component is important, but what I'm
> > > > > > considering
> > > > > > > is that although we can put HorizontalLayout (for the current
> > > > > FormtItem)
> > > > > > > and VerticalLayout (for the stacked), I'm seeing that many
> > > components
> > > > > > would
> > > > > > > need its own layout class. In this case we could create a
> > > > > FormItemLayout,
> > > > > > > and this will handle the layout vía CSS as it happens mostly in
> > > many
> > > > > > other
> > > > > > > Jewel component.
> > > > > > >
> > > > > > > (Just say that some of them are using an standard layout class,
> > > like
> > > > > > > HorizontalLayout, or even a NullLayout class), since I didn't
> > have
> > > > the
> > > > > > time
> > > > > > > to create its own one, and that's temporal. But my plan is to
> > > create
> > > > a
> > > > > > > concrete layout for some of this components. FormItem could be
> > one
> > > of
> > > > > > those
> > > > > > > cases, for what we're seeing
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
> > > > > > carlosrovira@apache.org
> > > > > > > >)
> > > > > > > escribió:
> > > > > > >
> > > > > > > > Hi Piotr,
> > > > > > > >
> > > > > > > > looking at the screen shot, seems the required indicator is
> > > > > positioned
> > > > > > to
> > > > > > > > the right side of the element, what seems coherent, although
> > > could
> > > > > be a
> > > > > > > bit
> > > > > > > > problematic depending on the width of the component. we
> assume
> > a
> > > > > fixed
> > > > > > > > width (to the widest element) and align all required (or not
> a
> > > put
> > > > > the
> > > > > > > > required indicator just before the element, anyway this seems
> > > > > something
> > > > > > > to
> > > > > > > > be solved as we have some real implementation.
> > > > > > > >
> > > > > > > > In order to implement it:
> > > > > > > >
> > > > > > > > We have 3 parts:
> > > > > > > > - L (this is the label)
> > > > > > > > - * (this is the required indicator)
> > > > > > > > - C (this is the element(s) that the user adds)
> > > > > > > >
> > > > > > > > * Actual FormItem is :
> > > > > > > >
> > > > > > > > L * C
> > > > > > > >
> > > > > > > > * We want for the new
> > > > > > > >
> > > > > > > > L
> > > > > > > > C *
> > > > > > > >
> > > > > > > > So it seems to me that
> > > > > > > >
> > > > > > > > a) IBeadLayout: ClassReference(
> > > > > > > > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> > > > > > > > Does not has much sense to me
> > > > > > > >
> > > > > > > > b) IFormItemLayout: ClassReference(
> > > > > > > > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> > > > > > > >
> > > > > > > > This is the one important to me (to configure), so user can
> > > change
> > > > > > layout
> > > > > > > > of the content part
> > > > > > > >
> > > > > > > > c) IBeadView: ClassReference(
> > > > > > > > "org.apache.royale.jewel.beads.views.FormItemView")
> > > > > > > > IFormItemContentArea:
> > > > ClassReference("org.apache.royale.jewel.Group")
> > > > > > > >
> > > > > > > > These are the parts important to me.
> > > > > > > >
> > > > > > > > I think we really want to change only the IBeadView, so we
> can
> > > > have a
> > > > > > > > FormItemView and a StackedFormItemView, and could change it
> vía
> > > > > > className
> > > > > > > > (for example)
> > > > > > > >
> > > > > > > > Let me know your thought about it
> > > > > > > >
> > > > > > > > thanks
> > > > > > > >
> > > > > > > > Carlos
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> > > > > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > >
> > > > > > > >> Carlos,
> > > > > > > >>
> > > > > > > >> I have analyzed FormItem in Flex and here is how it is done
> > > there.
> > > > > > > >> StackedFormItemSkin is using FormItemLayout which is
> > constrained
> > > > > into
> > > > > > 3
> > > > > > > >> columns (sequenceCol, contentCol and helpCol) and 2 rows.
> > [1][2]
> > > > > > > >>
> > > > > > > >> When you look into the screenshot [2] you may think that
> > reuired
> > > > > > > indicator
> > > > > > > >> is part of the content, but it's not. It's not even part of
> > the
> > > > > layout
> > > > > > > >> cause it has includeInLayout="false". [3]
> > > > > > > >> In Royale we don't have concept that something doesn't
> belong
> > to
> > > > > > layout
> > > > > > > >> and
> > > > > > > >> is not calculated and indicator default is being placed in
> > > > different
> > > > > > > area.
> > > > > > > >> Do you have some idea apart what I have proposed how to
> > resolve
> > > > > that ?
> > > > > > > >>
> > > > > > > >> [1] https://paste.apache.org/9Imj
> > > > > > > >> [2] https://imgur.com/GGOtzEU
> > > > > > > >> [3] https://paste.apache.org/kqlP
> > > > > > > >>
> > > > > > > >> Thanks,
> > > > > > > >> Piotr
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
> > > > piotrzarzycki21@gmail.com>
> > > > > > > >> napisał(a):
> > > > > > > >>
> > > > > > > >> > That's more clear to me. I will check and get back to you.
> > > > > > > >> >
> > > > > > > >> > Thank you!
> > > > > > > >> >
> > > > > > > >> >
> > > > > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <
> > > carlosrovira@apache.org
> > > > >
> > > > > > > >> > napisał(a):
> > > > > > > >> >
> > > > > > > >> >> No,
> > > > > > > >> >>
> > > > > > > >> >> I was asking you about how flex solves visualy the
> problem
> > in
> > > > > their
> > > > > > > >> >> stacked
> > > > > > > >> >> version. The required icon is setup next to the label? is
> > in
> > > > > other
> > > > > > > >> place?
> > > > > > > >> >> if we had an image of how it is designed (and like it),
> we
> > > can
> > > > > copy
> > > > > > > >> it. I
> > > > > > > >> >> still not proposing a technical solution. Just that I
> don't
> > > > have
> > > > > > > clear
> > > > > > > >> how
> > > > > > > >> >> we should layout it
> > > > > > > >> >>
> > > > > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
> > > > > > > >> >> piotrzarzycki21@gmail.com>) escribió:
> > > > > > > >> >>
> > > > > > > >> >> > Carlos,
> > > > > > > >> >> >
> > > > > > > >> >> > Your suggestion is to have new form item
> > (StackedFormItem)
> > > > with
> > > > > > new
> > > > > > > >> >> > StackedFormItemView - cause problem is inside
> > FormitemView,
> > > > not
> > > > > > > >> inside
> > > > > > > >> >> > layout itself. Current layout is doing what it should
> do
> > -
> > > > > apart
> > > > > > of
> > > > > > > >> the
> > > > > > > >> >> > problem - it's making children to be
> Horizontal/Vertical.
> > > > > > > >> >> >
> > > > > > > >> >> > If I'm correct what you are saying - that's ok, but if
> > you
> > > > have
> > > > > > had
> > > > > > > >> >> > different idea by saying above let me know.
> > > > > > > >> >> >
> > > > > > > >> >> > Thanks, Piotr
> > > > > > > >> >> >
> > > > > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
> > > > > carlosrovira@apache.org>
> > > > > > > >> >> > napisał(a):
> > > > > > > >> >> >
> > > > > > > >> >> > > Ok, I understand now.
> > > > > > > >> >> > >
> > > > > > > >> >> > > In Flex I think we had that layout and was
> > > > > > > >> called....StackedFormItem
> > > > > > > >> >> or
> > > > > > > >> >> > > something like that?
> > > > > > > >> >> > > Could you check how Flex solve this? If we continue
> > > liking
> > > > > the
> > > > > > > way
> > > > > > > >> >> > stacked
> > > > > > > >> >> > > form layout in flex looks, we can do the same for our
> > > > Royale
> > > > > > > >> version
> > > > > > > >> >> > >
> > > > > > > >> >> > >
> > > > > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
> > > > > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > >> >> > >
> > > > > > > >> >> > > > I'm not sure how Serkan is doing that on users
> forum,
> > > > but I
> > > > > > see
> > > > > > > >> all
> > > > > > > >> >> > hist
> > > > > > > >> >> > > > pasted images. Anyway here you go:
> > > > > > > >> >> > > >
> > > > > > > >> >> > > > What I wanted to achieve:
> https://snag.gy/DmH7yk.jpg
> > > > > > > >> >> > > > What I got from Jewel FormItem:
> > > > https://snag.gy/Slfbt9.jpg
> > > > > > > >> >> > > >
> > > > > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
> > > > > > > carlosrovira@apache.org>
> > > > > > > >> >> > > > napisał(a):
> > > > > > > >> >> > > >
> > > > > > > >> >> > > > > Piotr,
> > > > > > > >> >> > > > >
> > > > > > > >> >> > > > > remember that images pasted in list are not
> shared,
> > > you
> > > > > > must
> > > > > > > >> share
> > > > > > > >> >> > with
> > > > > > > >> >> > > > > some image service
> > > > > > > >> >> > > > >
> > > > > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki
> > (<
> > > > > > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > > >> >> > > > >
> > > > > > > >> >> > > > > > There is one more problem with Layout.
> Currently
> > > > > default
> > > > > > in
> > > > > > > >> >> > framework
> > > > > > > >> >> > > > we
> > > > > > > >> >> > > > > > have [1]. It means that:
> > > > > > > >> >> > > > > >
> > > > > > > >> >> > > > > > My content of FormItem will be vertical and
> > > > IBeadLayout
> > > > > > is
> > > > > > > >> >> > basically
> > > > > > > >> >> > > > > > ignored at some point. If I specify beads -
> > > > > > > HorizontalLayout
> > > > > > > >> as
> > > > > > > >> >> it
> > > > > > > >> >> > is
> > > > > > > >> >> > > > in
> > > > > > > >> >> > > > > > above example it will be taken as a primary
> and I
> > > > have
> > > > > my
> > > > > > > >> >> content
> > > > > > > >> >> > > > laying
> > > > > > > >> >> > > > > > out horizontally. The question is - what is for
> > > > > > > >> >> IFormItemLayout in
> > > > > > > >> >> > > > > > default.css? Is it a bug?
> > > > > > > >> >> > > > > >
> > > > > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
> > > > > > > >> >> > > > > >
> > > > > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> > > > > > > >> >> piotrzarzycki21@gmail.com
> > > > > > > >> >> > >
> > > > > > > >> >> > > > > > napisał(a):
> > > > > > > >> >> > > > > >
> > > > > > > >> >> > > > > >> Hi Carlos,
> > > > > > > >> >> > > > > >>
> > > > > > > >> >> > > > > >> I'm was trying to change FormItem to be
> Vertical
> > > > > > oriented.
> > > > > > > >> In
> > > > > > > >> >> > > general
> > > > > > > >> >> > > > I
> > > > > > > >> >> > > > > >> would like to have following view. Label of
> > > FormItem
> > > > > is
> > > > > > on
> > > > > > > >> the
> > > > > > > >> >> top
> > > > > > > >> >> > > and
> > > > > > > >> >> > > > > in
> > > > > > > >> >> > > > > >> the bottom is content.
> > > > > > > >> >> > > > > >>
> > > > > > > >> >> > > > > >> [image: image.png]
> > > > > > > >> >> > > > > >>
> > > > > > > >> >> > > > > >> Code for that will looks like that [1].
> Results
> > is
> > > > > > > >> following:
> > > > > > > >> >> > > > > >>
> > > > > > > >> >> > > > > >> [image: image.png]
> > > > > > > >> >> > > > > >>
> > > > > > > >> >> > > > > >> It happened cause Label and required star
> label
> > > are
> > > > > > > >> different
> > > > > > > >> >> > > > components
> > > > > > > >> >> > > > > >> - everything is being laying out vertically.
> > What
> > > is
> > > > > > your
> > > > > > > >> >> > suggestion
> > > > > > > >> >> > > > to
> > > > > > > >> >> > > > > fix
> > > > > > > >> >> > > > > >> that ?
> > > > > > > >> >> > > > > >>
> > > > > > > >> >> > > > > >> Mine is wrapping "First name" and "*" into one
> > > Group
> > > > > > with
> > > > > > > >> >> > > > > >> HorizontalLayout.
> > > > > > > >> >> > > > > >>
> > > > > > > >> >> > > > > >> More thoughts are welcome. I hope you see
> > > > screenshots.
> > > > > > :)
> > > > > > > >> >> > > > > >>
> > > > > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
> > > > > > > >> >> > > > > >>
> > > > > > > >> >> > > > > >> Thanks,
> > > > > > > >> >> > > > > >> --
> > > > > > > >> >> > > > > >>
> > > > > > > >> >> > > > > >> Piotr Zarzycki
> > > > > > > >> >> > > > > >>
> > > > > > > >> >> > > > > >> Patreon: *
> https://www.patreon.com/piotrzarzycki
> > > > > > > >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > > > > >> >> > > > > >>
> > > > > > > >> >> > > > > >
> > > > > > > >> >> > > > > >
> > > > > > > >> >> > > > > > --
> > > > > > > >> >> > > > > >
> > > > > > > >> >> > > > > > Piotr Zarzycki
> > > > > > > >> >> > > > > >
> > > > > > > >> >> > > > > > Patreon: *
> https://www.patreon.com/piotrzarzycki
> > > > > > > >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > >> >> > > > > >
> > > > > > > >> >> > > > >
> > > > > > > >> >> > > > >
> > > > > > > >> >> > > > > --
> > > > > > > >> >> > > > > Carlos Rovira
> > > > > > > >> >> > > > > http://about.me/carlosrovira
> > > > > > > >> >> > > > >
> > > > > > > >> >> > > >
> > > > > > > >> >> > > >
> > > > > > > >> >> > > > --
> > > > > > > >> >> > > >
> > > > > > > >> >> > > > Piotr Zarzycki
> > > > > > > >> >> > > >
> > > > > > > >> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > >> >> > > >
> > > > > > > >> >> > >
> > > > > > > >> >> > >
> > > > > > > >> >> > > --
> > > > > > > >> >> > > Carlos Rovira
> > > > > > > >> >> > > http://about.me/carlosrovira
> > > > > > > >> >> > >
> > > > > > > >> >> >
> > > > > > > >> >> >
> > > > > > > >> >> > --
> > > > > > > >> >> >
> > > > > > > >> >> > Piotr Zarzycki
> > > > > > > >> >> >
> > > > > > > >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > >> >> >
> > > > > > > >> >>
> > > > > > > >> >>
> > > > > > > >> >> --
> > > > > > > >> >> Carlos Rovira
> > > > > > > >> >> http://about.me/carlosrovira
> > > > > > > >> >>
> > > > > > > >> >
> > > > > > > >> >
> > > > > > > >> > --
> > > > > > > >> >
> > > > > > > >> > Piotr Zarzycki
> > > > > > > >> >
> > > > > > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > >> > <https://www.patreon.com/piotrzarzycki>*
> > > > > > > >> >
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> --
> > > > > > > >>
> > > > > > > >> Piotr Zarzycki
> > > > > > > >>
> > > > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Carlos Rovira
> > > > > > > > http://about.me/carlosrovira
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Carlos Rovira
> > > > > > > http://about.me/carlosrovira
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > <https://www.patreon.com/piotrzarzycki>*
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Carlos Rovira <ca...@apache.org>.

Ops!,

ok, since I was using the other layout I was in the believe that was the
standard. So if we want to follow flex, we can change the current as well.

El jue., 24 ene. 2019 a las 18:34, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> Nope - I just checked [1] - Code [2] - You are showing me some custom
> implementation.
>
> [1] https://imgur.com/INKlfcC
> [2] https://paste.apache.org/jyrl
>
> czw., 24 sty 2019 o 18:20 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Piotr,
> >
> > in Flex we have the same align (as we have now in Royale), check this
> > image: url
> > <
> >
> https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249
> > >
> >
> > El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> > > If we are going in that direction it requires as well work were
> indicator
> > > in case of L* C (current implementation) will be changed to L C* - Yes
> ?
> > -
> > > Being consistent it should be like that.
> > >
> > > I'm not sure what the trends are in that case.
> > >
> > > czw., 24 sty 2019 o 17:51 Carlos Rovira <ca...@apache.org>
> > > napisał(a):
> > >
> > > > Hi Piotr,
> > > >
> > > > since is what you show in the flex version.
> > > > I think Adobe put side to content instead of side to label since the
> > user
> > > > fill the content elements and if not filled and required , the
> tooltip
> > > > should popup there.
> > > > IOW, for usability, seems more appropriated the way flex layedout, or
> > > seems
> > > > more natural.
> > > >
> > > > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
> > > > piotrzarzycki21@gmail.com>) escribió:
> > > >
> > > > > Carlos,
> > > > >
> > > > > Why you are proposing have that?
> > > > >
> > > > > L
> > > > > C *
> > > > >
> > > > > I'm in favor of staying
> > > > >
> > > > > L *
> > > > > C
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <
> carlosrovira@apache.org
> > >
> > > > > wrote:
> > > > >
> > > > > > I forgot to mention about IBeadLayout more, since it could be
> > > > > > misinterpreted:
> > > > > >
> > > > > > IBeadLayout for the global component is important, but what I'm
> > > > > considering
> > > > > > is that although we can put HorizontalLayout (for the current
> > > > FormtItem)
> > > > > > and VerticalLayout (for the stacked), I'm seeing that many
> > components
> > > > > would
> > > > > > need its own layout class. In this case we could create a
> > > > FormItemLayout,
> > > > > > and this will handle the layout vía CSS as it happens mostly in
> > many
> > > > > other
> > > > > > Jewel component.
> > > > > >
> > > > > > (Just say that some of them are using an standard layout class,
> > like
> > > > > > HorizontalLayout, or even a NullLayout class), since I didn't
> have
> > > the
> > > > > time
> > > > > > to create its own one, and that's temporal. But my plan is to
> > create
> > > a
> > > > > > concrete layout for some of this components. FormItem could be
> one
> > of
> > > > > those
> > > > > > cases, for what we're seeing
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
> > > > > carlosrovira@apache.org
> > > > > > >)
> > > > > > escribió:
> > > > > >
> > > > > > > Hi Piotr,
> > > > > > >
> > > > > > > looking at the screen shot, seems the required indicator is
> > > > positioned
> > > > > to
> > > > > > > the right side of the element, what seems coherent, although
> > could
> > > > be a
> > > > > > bit
> > > > > > > problematic depending on the width of the component. we assume
> a
> > > > fixed
> > > > > > > width (to the widest element) and align all required (or not a
> > put
> > > > the
> > > > > > > required indicator just before the element, anyway this seems
> > > > something
> > > > > > to
> > > > > > > be solved as we have some real implementation.
> > > > > > >
> > > > > > > In order to implement it:
> > > > > > >
> > > > > > > We have 3 parts:
> > > > > > > - L (this is the label)
> > > > > > > - * (this is the required indicator)
> > > > > > > - C (this is the element(s) that the user adds)
> > > > > > >
> > > > > > > * Actual FormItem is :
> > > > > > >
> > > > > > > L * C
> > > > > > >
> > > > > > > * We want for the new
> > > > > > >
> > > > > > > L
> > > > > > > C *
> > > > > > >
> > > > > > > So it seems to me that
> > > > > > >
> > > > > > > a) IBeadLayout: ClassReference(
> > > > > > > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> > > > > > > Does not has much sense to me
> > > > > > >
> > > > > > > b) IFormItemLayout: ClassReference(
> > > > > > > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> > > > > > >
> > > > > > > This is the one important to me (to configure), so user can
> > change
> > > > > layout
> > > > > > > of the content part
> > > > > > >
> > > > > > > c) IBeadView: ClassReference(
> > > > > > > "org.apache.royale.jewel.beads.views.FormItemView")
> > > > > > > IFormItemContentArea:
> > > ClassReference("org.apache.royale.jewel.Group")
> > > > > > >
> > > > > > > These are the parts important to me.
> > > > > > >
> > > > > > > I think we really want to change only the IBeadView, so we can
> > > have a
> > > > > > > FormItemView and a StackedFormItemView, and could change it vía
> > > > > className
> > > > > > > (for example)
> > > > > > >
> > > > > > > Let me know your thought about it
> > > > > > >
> > > > > > > thanks
> > > > > > >
> > > > > > > Carlos
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> > > > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > >
> > > > > > >> Carlos,
> > > > > > >>
> > > > > > >> I have analyzed FormItem in Flex and here is how it is done
> > there.
> > > > > > >> StackedFormItemSkin is using FormItemLayout which is
> constrained
> > > > into
> > > > > 3
> > > > > > >> columns (sequenceCol, contentCol and helpCol) and 2 rows.
> [1][2]
> > > > > > >>
> > > > > > >> When you look into the screenshot [2] you may think that
> reuired
> > > > > > indicator
> > > > > > >> is part of the content, but it's not. It's not even part of
> the
> > > > layout
> > > > > > >> cause it has includeInLayout="false". [3]
> > > > > > >> In Royale we don't have concept that something doesn't belong
> to
> > > > > layout
> > > > > > >> and
> > > > > > >> is not calculated and indicator default is being placed in
> > > different
> > > > > > area.
> > > > > > >> Do you have some idea apart what I have proposed how to
> resolve
> > > > that ?
> > > > > > >>
> > > > > > >> [1] https://paste.apache.org/9Imj
> > > > > > >> [2] https://imgur.com/GGOtzEU
> > > > > > >> [3] https://paste.apache.org/kqlP
> > > > > > >>
> > > > > > >> Thanks,
> > > > > > >> Piotr
> > > > > > >>
> > > > > > >>
> > > > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
> > > piotrzarzycki21@gmail.com>
> > > > > > >> napisał(a):
> > > > > > >>
> > > > > > >> > That's more clear to me. I will check and get back to you.
> > > > > > >> >
> > > > > > >> > Thank you!
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <
> > carlosrovira@apache.org
> > > >
> > > > > > >> > napisał(a):
> > > > > > >> >
> > > > > > >> >> No,
> > > > > > >> >>
> > > > > > >> >> I was asking you about how flex solves visualy the problem
> in
> > > > their
> > > > > > >> >> stacked
> > > > > > >> >> version. The required icon is setup next to the label? is
> in
> > > > other
> > > > > > >> place?
> > > > > > >> >> if we had an image of how it is designed (and like it), we
> > can
> > > > copy
> > > > > > >> it. I
> > > > > > >> >> still not proposing a technical solution. Just that I don't
> > > have
> > > > > > clear
> > > > > > >> how
> > > > > > >> >> we should layout it
> > > > > > >> >>
> > > > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
> > > > > > >> >> piotrzarzycki21@gmail.com>) escribió:
> > > > > > >> >>
> > > > > > >> >> > Carlos,
> > > > > > >> >> >
> > > > > > >> >> > Your suggestion is to have new form item
> (StackedFormItem)
> > > with
> > > > > new
> > > > > > >> >> > StackedFormItemView - cause problem is inside
> FormitemView,
> > > not
> > > > > > >> inside
> > > > > > >> >> > layout itself. Current layout is doing what it should do
> -
> > > > apart
> > > > > of
> > > > > > >> the
> > > > > > >> >> > problem - it's making children to be Horizontal/Vertical.
> > > > > > >> >> >
> > > > > > >> >> > If I'm correct what you are saying - that's ok, but if
> you
> > > have
> > > > > had
> > > > > > >> >> > different idea by saying above let me know.
> > > > > > >> >> >
> > > > > > >> >> > Thanks, Piotr
> > > > > > >> >> >
> > > > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
> > > > carlosrovira@apache.org>
> > > > > > >> >> > napisał(a):
> > > > > > >> >> >
> > > > > > >> >> > > Ok, I understand now.
> > > > > > >> >> > >
> > > > > > >> >> > > In Flex I think we had that layout and was
> > > > > > >> called....StackedFormItem
> > > > > > >> >> or
> > > > > > >> >> > > something like that?
> > > > > > >> >> > > Could you check how Flex solve this? If we continue
> > liking
> > > > the
> > > > > > way
> > > > > > >> >> > stacked
> > > > > > >> >> > > form layout in flex looks, we can do the same for our
> > > Royale
> > > > > > >> version
> > > > > > >> >> > >
> > > > > > >> >> > >
> > > > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
> > > > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > >> >> > >
> > > > > > >> >> > > > I'm not sure how Serkan is doing that on users forum,
> > > but I
> > > > > see
> > > > > > >> all
> > > > > > >> >> > hist
> > > > > > >> >> > > > pasted images. Anyway here you go:
> > > > > > >> >> > > >
> > > > > > >> >> > > > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
> > > > > > >> >> > > > What I got from Jewel FormItem:
> > > https://snag.gy/Slfbt9.jpg
> > > > > > >> >> > > >
> > > > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
> > > > > > carlosrovira@apache.org>
> > > > > > >> >> > > > napisał(a):
> > > > > > >> >> > > >
> > > > > > >> >> > > > > Piotr,
> > > > > > >> >> > > > >
> > > > > > >> >> > > > > remember that images pasted in list are not shared,
> > you
> > > > > must
> > > > > > >> share
> > > > > > >> >> > with
> > > > > > >> >> > > > > some image service
> > > > > > >> >> > > > >
> > > > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki
> (<
> > > > > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > > >> >> > > > >
> > > > > > >> >> > > > > > There is one more problem with Layout. Currently
> > > > default
> > > > > in
> > > > > > >> >> > framework
> > > > > > >> >> > > > we
> > > > > > >> >> > > > > > have [1]. It means that:
> > > > > > >> >> > > > > >
> > > > > > >> >> > > > > > My content of FormItem will be vertical and
> > > IBeadLayout
> > > > > is
> > > > > > >> >> > basically
> > > > > > >> >> > > > > > ignored at some point. If I specify beads -
> > > > > > HorizontalLayout
> > > > > > >> as
> > > > > > >> >> it
> > > > > > >> >> > is
> > > > > > >> >> > > > in
> > > > > > >> >> > > > > > above example it will be taken as a primary and I
> > > have
> > > > my
> > > > > > >> >> content
> > > > > > >> >> > > > laying
> > > > > > >> >> > > > > > out horizontally. The question is - what is for
> > > > > > >> >> IFormItemLayout in
> > > > > > >> >> > > > > > default.css? Is it a bug?
> > > > > > >> >> > > > > >
> > > > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
> > > > > > >> >> > > > > >
> > > > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> > > > > > >> >> piotrzarzycki21@gmail.com
> > > > > > >> >> > >
> > > > > > >> >> > > > > > napisał(a):
> > > > > > >> >> > > > > >
> > > > > > >> >> > > > > >> Hi Carlos,
> > > > > > >> >> > > > > >>
> > > > > > >> >> > > > > >> I'm was trying to change FormItem to be Vertical
> > > > > oriented.
> > > > > > >> In
> > > > > > >> >> > > general
> > > > > > >> >> > > > I
> > > > > > >> >> > > > > >> would like to have following view. Label of
> > FormItem
> > > > is
> > > > > on
> > > > > > >> the
> > > > > > >> >> top
> > > > > > >> >> > > and
> > > > > > >> >> > > > > in
> > > > > > >> >> > > > > >> the bottom is content.
> > > > > > >> >> > > > > >>
> > > > > > >> >> > > > > >> [image: image.png]
> > > > > > >> >> > > > > >>
> > > > > > >> >> > > > > >> Code for that will looks like that [1]. Results
> is
> > > > > > >> following:
> > > > > > >> >> > > > > >>
> > > > > > >> >> > > > > >> [image: image.png]
> > > > > > >> >> > > > > >>
> > > > > > >> >> > > > > >> It happened cause Label and required star label
> > are
> > > > > > >> different
> > > > > > >> >> > > > components
> > > > > > >> >> > > > > >> - everything is being laying out vertically.
> What
> > is
> > > > > your
> > > > > > >> >> > suggestion
> > > > > > >> >> > > > to
> > > > > > >> >> > > > > fix
> > > > > > >> >> > > > > >> that ?
> > > > > > >> >> > > > > >>
> > > > > > >> >> > > > > >> Mine is wrapping "First name" and "*" into one
> > Group
> > > > > with
> > > > > > >> >> > > > > >> HorizontalLayout.
> > > > > > >> >> > > > > >>
> > > > > > >> >> > > > > >> More thoughts are welcome. I hope you see
> > > screenshots.
> > > > > :)
> > > > > > >> >> > > > > >>
> > > > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
> > > > > > >> >> > > > > >>
> > > > > > >> >> > > > > >> Thanks,
> > > > > > >> >> > > > > >> --
> > > > > > >> >> > > > > >>
> > > > > > >> >> > > > > >> Piotr Zarzycki
> > > > > > >> >> > > > > >>
> > > > > > >> >> > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > > > >> >> > > > > >>
> > > > > > >> >> > > > > >
> > > > > > >> >> > > > > >
> > > > > > >> >> > > > > > --
> > > > > > >> >> > > > > >
> > > > > > >> >> > > > > > Piotr Zarzycki
> > > > > > >> >> > > > > >
> > > > > > >> >> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > > >> >> > > > > >
> > > > > > >> >> > > > >
> > > > > > >> >> > > > >
> > > > > > >> >> > > > > --
> > > > > > >> >> > > > > Carlos Rovira
> > > > > > >> >> > > > > http://about.me/carlosrovira
> > > > > > >> >> > > > >
> > > > > > >> >> > > >
> > > > > > >> >> > > >
> > > > > > >> >> > > > --
> > > > > > >> >> > > >
> > > > > > >> >> > > > Piotr Zarzycki
> > > > > > >> >> > > >
> > > > > > >> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > > >> >> > > >
> > > > > > >> >> > >
> > > > > > >> >> > >
> > > > > > >> >> > > --
> > > > > > >> >> > > Carlos Rovira
> > > > > > >> >> > > http://about.me/carlosrovira
> > > > > > >> >> > >
> > > > > > >> >> >
> > > > > > >> >> >
> > > > > > >> >> > --
> > > > > > >> >> >
> > > > > > >> >> > Piotr Zarzycki
> > > > > > >> >> >
> > > > > > >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
> > > > > > >> >> >
> > > > > > >> >>
> > > > > > >> >>
> > > > > > >> >> --
> > > > > > >> >> Carlos Rovira
> > > > > > >> >> http://about.me/carlosrovira
> > > > > > >> >>
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > --
> > > > > > >> >
> > > > > > >> > Piotr Zarzycki
> > > > > > >> >
> > > > > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > >> > <https://www.patreon.com/piotrzarzycki>*
> > > > > > >> >
> > > > > > >>
> > > > > > >>
> > > > > > >> --
> > > > > > >>
> > > > > > >> Piotr Zarzycki
> > > > > > >>
> > > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Carlos Rovira
> > > > > > > http://about.me/carlosrovira
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > Carlos Rovira
> > > > > > http://about.me/carlosrovira
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

Nope - I just checked [1] - Code [2] - You are showing me some custom
implementation.

[1] https://imgur.com/INKlfcC
[2] https://paste.apache.org/jyrl

czw., 24 sty 2019 o 18:20 Carlos Rovira <ca...@apache.org>
napisał(a):

> Piotr,
>
> in Flex we have the same align (as we have now in Royale), check this
> image: url
> <
> https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249
> >
>
> El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > If we are going in that direction it requires as well work were indicator
> > in case of L* C (current implementation) will be changed to L C* - Yes ?
> -
> > Being consistent it should be like that.
> >
> > I'm not sure what the trends are in that case.
> >
> > czw., 24 sty 2019 o 17:51 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > since is what you show in the flex version.
> > > I think Adobe put side to content instead of side to label since the
> user
> > > fill the content elements and if not filled and required , the tooltip
> > > should popup there.
> > > IOW, for usability, seems more appropriated the way flex layedout, or
> > seems
> > > more natural.
> > >
> > > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
> > > piotrzarzycki21@gmail.com>) escribió:
> > >
> > > > Carlos,
> > > >
> > > > Why you are proposing have that?
> > > >
> > > > L
> > > > C *
> > > >
> > > > I'm in favor of staying
> > > >
> > > > L *
> > > > C
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <carlosrovira@apache.org
> >
> > > > wrote:
> > > >
> > > > > I forgot to mention about IBeadLayout more, since it could be
> > > > > misinterpreted:
> > > > >
> > > > > IBeadLayout for the global component is important, but what I'm
> > > > considering
> > > > > is that although we can put HorizontalLayout (for the current
> > > FormtItem)
> > > > > and VerticalLayout (for the stacked), I'm seeing that many
> components
> > > > would
> > > > > need its own layout class. In this case we could create a
> > > FormItemLayout,
> > > > > and this will handle the layout vía CSS as it happens mostly in
> many
> > > > other
> > > > > Jewel component.
> > > > >
> > > > > (Just say that some of them are using an standard layout class,
> like
> > > > > HorizontalLayout, or even a NullLayout class), since I didn't have
> > the
> > > > time
> > > > > to create its own one, and that's temporal. But my plan is to
> create
> > a
> > > > > concrete layout for some of this components. FormItem could be one
> of
> > > > those
> > > > > cases, for what we're seeing
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
> > > > carlosrovira@apache.org
> > > > > >)
> > > > > escribió:
> > > > >
> > > > > > Hi Piotr,
> > > > > >
> > > > > > looking at the screen shot, seems the required indicator is
> > > positioned
> > > > to
> > > > > > the right side of the element, what seems coherent, although
> could
> > > be a
> > > > > bit
> > > > > > problematic depending on the width of the component. we assume a
> > > fixed
> > > > > > width (to the widest element) and align all required (or not a
> put
> > > the
> > > > > > required indicator just before the element, anyway this seems
> > > something
> > > > > to
> > > > > > be solved as we have some real implementation.
> > > > > >
> > > > > > In order to implement it:
> > > > > >
> > > > > > We have 3 parts:
> > > > > > - L (this is the label)
> > > > > > - * (this is the required indicator)
> > > > > > - C (this is the element(s) that the user adds)
> > > > > >
> > > > > > * Actual FormItem is :
> > > > > >
> > > > > > L * C
> > > > > >
> > > > > > * We want for the new
> > > > > >
> > > > > > L
> > > > > > C *
> > > > > >
> > > > > > So it seems to me that
> > > > > >
> > > > > > a) IBeadLayout: ClassReference(
> > > > > > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> > > > > > Does not has much sense to me
> > > > > >
> > > > > > b) IFormItemLayout: ClassReference(
> > > > > > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> > > > > >
> > > > > > This is the one important to me (to configure), so user can
> change
> > > > layout
> > > > > > of the content part
> > > > > >
> > > > > > c) IBeadView: ClassReference(
> > > > > > "org.apache.royale.jewel.beads.views.FormItemView")
> > > > > > IFormItemContentArea:
> > ClassReference("org.apache.royale.jewel.Group")
> > > > > >
> > > > > > These are the parts important to me.
> > > > > >
> > > > > > I think we really want to change only the IBeadView, so we can
> > have a
> > > > > > FormItemView and a StackedFormItemView, and could change it vía
> > > > className
> > > > > > (for example)
> > > > > >
> > > > > > Let me know your thought about it
> > > > > >
> > > > > > thanks
> > > > > >
> > > > > > Carlos
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> > > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > >
> > > > > >> Carlos,
> > > > > >>
> > > > > >> I have analyzed FormItem in Flex and here is how it is done
> there.
> > > > > >> StackedFormItemSkin is using FormItemLayout which is constrained
> > > into
> > > > 3
> > > > > >> columns (sequenceCol, contentCol and helpCol) and 2 rows. [1][2]
> > > > > >>
> > > > > >> When you look into the screenshot [2] you may think that reuired
> > > > > indicator
> > > > > >> is part of the content, but it's not. It's not even part of the
> > > layout
> > > > > >> cause it has includeInLayout="false". [3]
> > > > > >> In Royale we don't have concept that something doesn't belong to
> > > > layout
> > > > > >> and
> > > > > >> is not calculated and indicator default is being placed in
> > different
> > > > > area.
> > > > > >> Do you have some idea apart what I have proposed how to resolve
> > > that ?
> > > > > >>
> > > > > >> [1] https://paste.apache.org/9Imj
> > > > > >> [2] https://imgur.com/GGOtzEU
> > > > > >> [3] https://paste.apache.org/kqlP
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Piotr
> > > > > >>
> > > > > >>
> > > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
> > piotrzarzycki21@gmail.com>
> > > > > >> napisał(a):
> > > > > >>
> > > > > >> > That's more clear to me. I will check and get back to you.
> > > > > >> >
> > > > > >> > Thank you!
> > > > > >> >
> > > > > >> >
> > > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <
> carlosrovira@apache.org
> > >
> > > > > >> > napisał(a):
> > > > > >> >
> > > > > >> >> No,
> > > > > >> >>
> > > > > >> >> I was asking you about how flex solves visualy the problem in
> > > their
> > > > > >> >> stacked
> > > > > >> >> version. The required icon is setup next to the label? is in
> > > other
> > > > > >> place?
> > > > > >> >> if we had an image of how it is designed (and like it), we
> can
> > > copy
> > > > > >> it. I
> > > > > >> >> still not proposing a technical solution. Just that I don't
> > have
> > > > > clear
> > > > > >> how
> > > > > >> >> we should layout it
> > > > > >> >>
> > > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
> > > > > >> >> piotrzarzycki21@gmail.com>) escribió:
> > > > > >> >>
> > > > > >> >> > Carlos,
> > > > > >> >> >
> > > > > >> >> > Your suggestion is to have new form item (StackedFormItem)
> > with
> > > > new
> > > > > >> >> > StackedFormItemView - cause problem is inside FormitemView,
> > not
> > > > > >> inside
> > > > > >> >> > layout itself. Current layout is doing what it should do -
> > > apart
> > > > of
> > > > > >> the
> > > > > >> >> > problem - it's making children to be Horizontal/Vertical.
> > > > > >> >> >
> > > > > >> >> > If I'm correct what you are saying - that's ok, but if you
> > have
> > > > had
> > > > > >> >> > different idea by saying above let me know.
> > > > > >> >> >
> > > > > >> >> > Thanks, Piotr
> > > > > >> >> >
> > > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
> > > carlosrovira@apache.org>
> > > > > >> >> > napisał(a):
> > > > > >> >> >
> > > > > >> >> > > Ok, I understand now.
> > > > > >> >> > >
> > > > > >> >> > > In Flex I think we had that layout and was
> > > > > >> called....StackedFormItem
> > > > > >> >> or
> > > > > >> >> > > something like that?
> > > > > >> >> > > Could you check how Flex solve this? If we continue
> liking
> > > the
> > > > > way
> > > > > >> >> > stacked
> > > > > >> >> > > form layout in flex looks, we can do the same for our
> > Royale
> > > > > >> version
> > > > > >> >> > >
> > > > > >> >> > >
> > > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
> > > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
> > > > > >> >> > >
> > > > > >> >> > > > I'm not sure how Serkan is doing that on users forum,
> > but I
> > > > see
> > > > > >> all
> > > > > >> >> > hist
> > > > > >> >> > > > pasted images. Anyway here you go:
> > > > > >> >> > > >
> > > > > >> >> > > > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
> > > > > >> >> > > > What I got from Jewel FormItem:
> > https://snag.gy/Slfbt9.jpg
> > > > > >> >> > > >
> > > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
> > > > > carlosrovira@apache.org>
> > > > > >> >> > > > napisał(a):
> > > > > >> >> > > >
> > > > > >> >> > > > > Piotr,
> > > > > >> >> > > > >
> > > > > >> >> > > > > remember that images pasted in list are not shared,
> you
> > > > must
> > > > > >> share
> > > > > >> >> > with
> > > > > >> >> > > > > some image service
> > > > > >> >> > > > >
> > > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
> > > > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > > >> >> > > > >
> > > > > >> >> > > > > > There is one more problem with Layout. Currently
> > > default
> > > > in
> > > > > >> >> > framework
> > > > > >> >> > > > we
> > > > > >> >> > > > > > have [1]. It means that:
> > > > > >> >> > > > > >
> > > > > >> >> > > > > > My content of FormItem will be vertical and
> > IBeadLayout
> > > > is
> > > > > >> >> > basically
> > > > > >> >> > > > > > ignored at some point. If I specify beads -
> > > > > HorizontalLayout
> > > > > >> as
> > > > > >> >> it
> > > > > >> >> > is
> > > > > >> >> > > > in
> > > > > >> >> > > > > > above example it will be taken as a primary and I
> > have
> > > my
> > > > > >> >> content
> > > > > >> >> > > > laying
> > > > > >> >> > > > > > out horizontally. The question is - what is for
> > > > > >> >> IFormItemLayout in
> > > > > >> >> > > > > > default.css? Is it a bug?
> > > > > >> >> > > > > >
> > > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
> > > > > >> >> > > > > >
> > > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> > > > > >> >> piotrzarzycki21@gmail.com
> > > > > >> >> > >
> > > > > >> >> > > > > > napisał(a):
> > > > > >> >> > > > > >
> > > > > >> >> > > > > >> Hi Carlos,
> > > > > >> >> > > > > >>
> > > > > >> >> > > > > >> I'm was trying to change FormItem to be Vertical
> > > > oriented.
> > > > > >> In
> > > > > >> >> > > general
> > > > > >> >> > > > I
> > > > > >> >> > > > > >> would like to have following view. Label of
> FormItem
> > > is
> > > > on
> > > > > >> the
> > > > > >> >> top
> > > > > >> >> > > and
> > > > > >> >> > > > > in
> > > > > >> >> > > > > >> the bottom is content.
> > > > > >> >> > > > > >>
> > > > > >> >> > > > > >> [image: image.png]
> > > > > >> >> > > > > >>
> > > > > >> >> > > > > >> Code for that will looks like that [1]. Results is
> > > > > >> following:
> > > > > >> >> > > > > >>
> > > > > >> >> > > > > >> [image: image.png]
> > > > > >> >> > > > > >>
> > > > > >> >> > > > > >> It happened cause Label and required star label
> are
> > > > > >> different
> > > > > >> >> > > > components
> > > > > >> >> > > > > >> - everything is being laying out vertically. What
> is
> > > > your
> > > > > >> >> > suggestion
> > > > > >> >> > > > to
> > > > > >> >> > > > > fix
> > > > > >> >> > > > > >> that ?
> > > > > >> >> > > > > >>
> > > > > >> >> > > > > >> Mine is wrapping "First name" and "*" into one
> Group
> > > > with
> > > > > >> >> > > > > >> HorizontalLayout.
> > > > > >> >> > > > > >>
> > > > > >> >> > > > > >> More thoughts are welcome. I hope you see
> > screenshots.
> > > > :)
> > > > > >> >> > > > > >>
> > > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
> > > > > >> >> > > > > >>
> > > > > >> >> > > > > >> Thanks,
> > > > > >> >> > > > > >> --
> > > > > >> >> > > > > >>
> > > > > >> >> > > > > >> Piotr Zarzycki
> > > > > >> >> > > > > >>
> > > > > >> >> > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > > >> >> > > > > >>
> > > > > >> >> > > > > >
> > > > > >> >> > > > > >
> > > > > >> >> > > > > > --
> > > > > >> >> > > > > >
> > > > > >> >> > > > > > Piotr Zarzycki
> > > > > >> >> > > > > >
> > > > > >> >> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > >> >> > > > > >
> > > > > >> >> > > > >
> > > > > >> >> > > > >
> > > > > >> >> > > > > --
> > > > > >> >> > > > > Carlos Rovira
> > > > > >> >> > > > > http://about.me/carlosrovira
> > > > > >> >> > > > >
> > > > > >> >> > > >
> > > > > >> >> > > >
> > > > > >> >> > > > --
> > > > > >> >> > > >
> > > > > >> >> > > > Piotr Zarzycki
> > > > > >> >> > > >
> > > > > >> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > >> >> > > >
> > > > > >> >> > >
> > > > > >> >> > >
> > > > > >> >> > > --
> > > > > >> >> > > Carlos Rovira
> > > > > >> >> > > http://about.me/carlosrovira
> > > > > >> >> > >
> > > > > >> >> >
> > > > > >> >> >
> > > > > >> >> > --
> > > > > >> >> >
> > > > > >> >> > Piotr Zarzycki
> > > > > >> >> >
> > > > > >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
> > > > > >> >> >
> > > > > >> >>
> > > > > >> >>
> > > > > >> >> --
> > > > > >> >> Carlos Rovira
> > > > > >> >> http://about.me/carlosrovira
> > > > > >> >>
> > > > > >> >
> > > > > >> >
> > > > > >> > --
> > > > > >> >
> > > > > >> > Piotr Zarzycki
> > > > > >> >
> > > > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > >> > <https://www.patreon.com/piotrzarzycki>*
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >>
> > > > > >> Piotr Zarzycki
> > > > > >>
> > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > > >>
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Carlos Rovira
> > > > > > http://about.me/carlosrovira
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira
> > > > >
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Carlos Rovira <ca...@apache.org>.

Piotr,

in Flex we have the same align (as we have now in Royale), check this
image: url
<https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi1uZfN9obgAhVFuVkKHeyzC0MQjRx6BAgBEAU&url=https%3A%2F%2Fbutterfliesandbugs.wordpress.com%2F2011%2F03%2F29%2Fusing-a-spark-form-with-validators%2F&psig=AOvVaw0vM1bn9Ehq9ZHLqtzJ-gc1&ust=1548436757385249>

El jue., 24 ene. 2019 a las 18:03, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> If we are going in that direction it requires as well work were indicator
> in case of L* C (current implementation) will be changed to L C* - Yes ? -
> Being consistent it should be like that.
>
> I'm not sure what the trends are in that case.
>
> czw., 24 sty 2019 o 17:51 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Hi Piotr,
> >
> > since is what you show in the flex version.
> > I think Adobe put side to content instead of side to label since the user
> > fill the content elements and if not filled and required , the tooltip
> > should popup there.
> > IOW, for usability, seems more appropriated the way flex layedout, or
> seems
> > more natural.
> >
> > El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> > > Carlos,
> > >
> > > Why you are proposing have that?
> > >
> > > L
> > > C *
> > >
> > > I'm in favor of staying
> > >
> > > L *
> > > C
> > >
> > > Thanks,
> > > Piotr
> > >
> > > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <ca...@apache.org>
> > > wrote:
> > >
> > > > I forgot to mention about IBeadLayout more, since it could be
> > > > misinterpreted:
> > > >
> > > > IBeadLayout for the global component is important, but what I'm
> > > considering
> > > > is that although we can put HorizontalLayout (for the current
> > FormtItem)
> > > > and VerticalLayout (for the stacked), I'm seeing that many components
> > > would
> > > > need its own layout class. In this case we could create a
> > FormItemLayout,
> > > > and this will handle the layout vía CSS as it happens mostly in many
> > > other
> > > > Jewel component.
> > > >
> > > > (Just say that some of them are using an standard layout class, like
> > > > HorizontalLayout, or even a NullLayout class), since I didn't have
> the
> > > time
> > > > to create its own one, and that's temporal. But my plan is to create
> a
> > > > concrete layout for some of this components. FormItem could be one of
> > > those
> > > > cases, for what we're seeing
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
> > > carlosrovira@apache.org
> > > > >)
> > > > escribió:
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > looking at the screen shot, seems the required indicator is
> > positioned
> > > to
> > > > > the right side of the element, what seems coherent, although could
> > be a
> > > > bit
> > > > > problematic depending on the width of the component. we assume a
> > fixed
> > > > > width (to the widest element) and align all required (or not a put
> > the
> > > > > required indicator just before the element, anyway this seems
> > something
> > > > to
> > > > > be solved as we have some real implementation.
> > > > >
> > > > > In order to implement it:
> > > > >
> > > > > We have 3 parts:
> > > > > - L (this is the label)
> > > > > - * (this is the required indicator)
> > > > > - C (this is the element(s) that the user adds)
> > > > >
> > > > > * Actual FormItem is :
> > > > >
> > > > > L * C
> > > > >
> > > > > * We want for the new
> > > > >
> > > > > L
> > > > > C *
> > > > >
> > > > > So it seems to me that
> > > > >
> > > > > a) IBeadLayout: ClassReference(
> > > > > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> > > > > Does not has much sense to me
> > > > >
> > > > > b) IFormItemLayout: ClassReference(
> > > > > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> > > > >
> > > > > This is the one important to me (to configure), so user can change
> > > layout
> > > > > of the content part
> > > > >
> > > > > c) IBeadView: ClassReference(
> > > > > "org.apache.royale.jewel.beads.views.FormItemView")
> > > > > IFormItemContentArea:
> ClassReference("org.apache.royale.jewel.Group")
> > > > >
> > > > > These are the parts important to me.
> > > > >
> > > > > I think we really want to change only the IBeadView, so we can
> have a
> > > > > FormItemView and a StackedFormItemView, and could change it vía
> > > className
> > > > > (for example)
> > > > >
> > > > > Let me know your thought about it
> > > > >
> > > > > thanks
> > > > >
> > > > > Carlos
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > >
> > > > >> Carlos,
> > > > >>
> > > > >> I have analyzed FormItem in Flex and here is how it is done there.
> > > > >> StackedFormItemSkin is using FormItemLayout which is constrained
> > into
> > > 3
> > > > >> columns (sequenceCol, contentCol and helpCol) and 2 rows. [1][2]
> > > > >>
> > > > >> When you look into the screenshot [2] you may think that reuired
> > > > indicator
> > > > >> is part of the content, but it's not. It's not even part of the
> > layout
> > > > >> cause it has includeInLayout="false". [3]
> > > > >> In Royale we don't have concept that something doesn't belong to
> > > layout
> > > > >> and
> > > > >> is not calculated and indicator default is being placed in
> different
> > > > area.
> > > > >> Do you have some idea apart what I have proposed how to resolve
> > that ?
> > > > >>
> > > > >> [1] https://paste.apache.org/9Imj
> > > > >> [2] https://imgur.com/GGOtzEU
> > > > >> [3] https://paste.apache.org/kqlP
> > > > >>
> > > > >> Thanks,
> > > > >> Piotr
> > > > >>
> > > > >>
> > > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> > > > >> napisał(a):
> > > > >>
> > > > >> > That's more clear to me. I will check and get back to you.
> > > > >> >
> > > > >> > Thank you!
> > > > >> >
> > > > >> >
> > > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <carlosrovira@apache.org
> >
> > > > >> > napisał(a):
> > > > >> >
> > > > >> >> No,
> > > > >> >>
> > > > >> >> I was asking you about how flex solves visualy the problem in
> > their
> > > > >> >> stacked
> > > > >> >> version. The required icon is setup next to the label? is in
> > other
> > > > >> place?
> > > > >> >> if we had an image of how it is designed (and like it), we can
> > copy
> > > > >> it. I
> > > > >> >> still not proposing a technical solution. Just that I don't
> have
> > > > clear
> > > > >> how
> > > > >> >> we should layout it
> > > > >> >>
> > > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
> > > > >> >> piotrzarzycki21@gmail.com>) escribió:
> > > > >> >>
> > > > >> >> > Carlos,
> > > > >> >> >
> > > > >> >> > Your suggestion is to have new form item (StackedFormItem)
> with
> > > new
> > > > >> >> > StackedFormItemView - cause problem is inside FormitemView,
> not
> > > > >> inside
> > > > >> >> > layout itself. Current layout is doing what it should do -
> > apart
> > > of
> > > > >> the
> > > > >> >> > problem - it's making children to be Horizontal/Vertical.
> > > > >> >> >
> > > > >> >> > If I'm correct what you are saying - that's ok, but if you
> have
> > > had
> > > > >> >> > different idea by saying above let me know.
> > > > >> >> >
> > > > >> >> > Thanks, Piotr
> > > > >> >> >
> > > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
> > carlosrovira@apache.org>
> > > > >> >> > napisał(a):
> > > > >> >> >
> > > > >> >> > > Ok, I understand now.
> > > > >> >> > >
> > > > >> >> > > In Flex I think we had that layout and was
> > > > >> called....StackedFormItem
> > > > >> >> or
> > > > >> >> > > something like that?
> > > > >> >> > > Could you check how Flex solve this? If we continue liking
> > the
> > > > way
> > > > >> >> > stacked
> > > > >> >> > > form layout in flex looks, we can do the same for our
> Royale
> > > > >> version
> > > > >> >> > >
> > > > >> >> > >
> > > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
> > > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
> > > > >> >> > >
> > > > >> >> > > > I'm not sure how Serkan is doing that on users forum,
> but I
> > > see
> > > > >> all
> > > > >> >> > hist
> > > > >> >> > > > pasted images. Anyway here you go:
> > > > >> >> > > >
> > > > >> >> > > > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
> > > > >> >> > > > What I got from Jewel FormItem:
> https://snag.gy/Slfbt9.jpg
> > > > >> >> > > >
> > > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
> > > > carlosrovira@apache.org>
> > > > >> >> > > > napisał(a):
> > > > >> >> > > >
> > > > >> >> > > > > Piotr,
> > > > >> >> > > > >
> > > > >> >> > > > > remember that images pasted in list are not shared, you
> > > must
> > > > >> share
> > > > >> >> > with
> > > > >> >> > > > > some image service
> > > > >> >> > > > >
> > > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
> > > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > >> >> > > > >
> > > > >> >> > > > > > There is one more problem with Layout. Currently
> > default
> > > in
> > > > >> >> > framework
> > > > >> >> > > > we
> > > > >> >> > > > > > have [1]. It means that:
> > > > >> >> > > > > >
> > > > >> >> > > > > > My content of FormItem will be vertical and
> IBeadLayout
> > > is
> > > > >> >> > basically
> > > > >> >> > > > > > ignored at some point. If I specify beads -
> > > > HorizontalLayout
> > > > >> as
> > > > >> >> it
> > > > >> >> > is
> > > > >> >> > > > in
> > > > >> >> > > > > > above example it will be taken as a primary and I
> have
> > my
> > > > >> >> content
> > > > >> >> > > > laying
> > > > >> >> > > > > > out horizontally. The question is - what is for
> > > > >> >> IFormItemLayout in
> > > > >> >> > > > > > default.css? Is it a bug?
> > > > >> >> > > > > >
> > > > >> >> > > > > > [1] https://paste.apache.org/rV0K
> > > > >> >> > > > > >
> > > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> > > > >> >> piotrzarzycki21@gmail.com
> > > > >> >> > >
> > > > >> >> > > > > > napisał(a):
> > > > >> >> > > > > >
> > > > >> >> > > > > >> Hi Carlos,
> > > > >> >> > > > > >>
> > > > >> >> > > > > >> I'm was trying to change FormItem to be Vertical
> > > oriented.
> > > > >> In
> > > > >> >> > > general
> > > > >> >> > > > I
> > > > >> >> > > > > >> would like to have following view. Label of FormItem
> > is
> > > on
> > > > >> the
> > > > >> >> top
> > > > >> >> > > and
> > > > >> >> > > > > in
> > > > >> >> > > > > >> the bottom is content.
> > > > >> >> > > > > >>
> > > > >> >> > > > > >> [image: image.png]
> > > > >> >> > > > > >>
> > > > >> >> > > > > >> Code for that will looks like that [1]. Results is
> > > > >> following:
> > > > >> >> > > > > >>
> > > > >> >> > > > > >> [image: image.png]
> > > > >> >> > > > > >>
> > > > >> >> > > > > >> It happened cause Label and required star label are
> > > > >> different
> > > > >> >> > > > components
> > > > >> >> > > > > >> - everything is being laying out vertically. What is
> > > your
> > > > >> >> > suggestion
> > > > >> >> > > > to
> > > > >> >> > > > > fix
> > > > >> >> > > > > >> that ?
> > > > >> >> > > > > >>
> > > > >> >> > > > > >> Mine is wrapping "First name" and "*" into one Group
> > > with
> > > > >> >> > > > > >> HorizontalLayout.
> > > > >> >> > > > > >>
> > > > >> >> > > > > >> More thoughts are welcome. I hope you see
> screenshots.
> > > :)
> > > > >> >> > > > > >>
> > > > >> >> > > > > >> [1] https://paste.apache.org/5odt
> > > > >> >> > > > > >>
> > > > >> >> > > > > >> Thanks,
> > > > >> >> > > > > >> --
> > > > >> >> > > > > >>
> > > > >> >> > > > > >> Piotr Zarzycki
> > > > >> >> > > > > >>
> > > > >> >> > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > >> >> > > > > >>
> > > > >> >> > > > > >
> > > > >> >> > > > > >
> > > > >> >> > > > > > --
> > > > >> >> > > > > >
> > > > >> >> > > > > > Piotr Zarzycki
> > > > >> >> > > > > >
> > > > >> >> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > >> >> > > > > >
> > > > >> >> > > > >
> > > > >> >> > > > >
> > > > >> >> > > > > --
> > > > >> >> > > > > Carlos Rovira
> > > > >> >> > > > > http://about.me/carlosrovira
> > > > >> >> > > > >
> > > > >> >> > > >
> > > > >> >> > > >
> > > > >> >> > > > --
> > > > >> >> > > >
> > > > >> >> > > > Piotr Zarzycki
> > > > >> >> > > >
> > > > >> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
> > > > >> >> > > >
> > > > >> >> > >
> > > > >> >> > >
> > > > >> >> > > --
> > > > >> >> > > Carlos Rovira
> > > > >> >> > > http://about.me/carlosrovira
> > > > >> >> > >
> > > > >> >> >
> > > > >> >> >
> > > > >> >> > --
> > > > >> >> >
> > > > >> >> > Piotr Zarzycki
> > > > >> >> >
> > > > >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > >> >> > <https://www.patreon.com/piotrzarzycki>*
> > > > >> >> >
> > > > >> >>
> > > > >> >>
> > > > >> >> --
> > > > >> >> Carlos Rovira
> > > > >> >> http://about.me/carlosrovira
> > > > >> >>
> > > > >> >
> > > > >> >
> > > > >> > --
> > > > >> >
> > > > >> > Piotr Zarzycki
> > > > >> >
> > > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > >> > <https://www.patreon.com/piotrzarzycki>*
> > > > >> >
> > > > >>
> > > > >>
> > > > >> --
> > > > >>
> > > > >> Piotr Zarzycki
> > > > >>
> > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira
> > > > >
> > > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

If we are going in that direction it requires as well work were indicator
in case of L* C (current implementation) will be changed to L C* - Yes ? -
Being consistent it should be like that.

I'm not sure what the trends are in that case.

czw., 24 sty 2019 o 17:51 Carlos Rovira <ca...@apache.org>
napisał(a):

> Hi Piotr,
>
> since is what you show in the flex version.
> I think Adobe put side to content instead of side to label since the user
> fill the content elements and if not filled and required , the tooltip
> should popup there.
> IOW, for usability, seems more appropriated the way flex layedout, or seems
> more natural.
>
> El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > Carlos,
> >
> > Why you are proposing have that?
> >
> > L
> > C *
> >
> > I'm in favor of staying
> >
> > L *
> > C
> >
> > Thanks,
> > Piotr
> >
> > On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <ca...@apache.org>
> > wrote:
> >
> > > I forgot to mention about IBeadLayout more, since it could be
> > > misinterpreted:
> > >
> > > IBeadLayout for the global component is important, but what I'm
> > considering
> > > is that although we can put HorizontalLayout (for the current
> FormtItem)
> > > and VerticalLayout (for the stacked), I'm seeing that many components
> > would
> > > need its own layout class. In this case we could create a
> FormItemLayout,
> > > and this will handle the layout vía CSS as it happens mostly in many
> > other
> > > Jewel component.
> > >
> > > (Just say that some of them are using an standard layout class, like
> > > HorizontalLayout, or even a NullLayout class), since I didn't have the
> > time
> > > to create its own one, and that's temporal. But my plan is to create a
> > > concrete layout for some of this components. FormItem could be one of
> > those
> > > cases, for what we're seeing
> > >
> > >
> > >
> > >
> > >
> > > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
> > carlosrovira@apache.org
> > > >)
> > > escribió:
> > >
> > > > Hi Piotr,
> > > >
> > > > looking at the screen shot, seems the required indicator is
> positioned
> > to
> > > > the right side of the element, what seems coherent, although could
> be a
> > > bit
> > > > problematic depending on the width of the component. we assume a
> fixed
> > > > width (to the widest element) and align all required (or not a put
> the
> > > > required indicator just before the element, anyway this seems
> something
> > > to
> > > > be solved as we have some real implementation.
> > > >
> > > > In order to implement it:
> > > >
> > > > We have 3 parts:
> > > > - L (this is the label)
> > > > - * (this is the required indicator)
> > > > - C (this is the element(s) that the user adds)
> > > >
> > > > * Actual FormItem is :
> > > >
> > > > L * C
> > > >
> > > > * We want for the new
> > > >
> > > > L
> > > > C *
> > > >
> > > > So it seems to me that
> > > >
> > > > a) IBeadLayout: ClassReference(
> > > > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> > > > Does not has much sense to me
> > > >
> > > > b) IFormItemLayout: ClassReference(
> > > > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> > > >
> > > > This is the one important to me (to configure), so user can change
> > layout
> > > > of the content part
> > > >
> > > > c) IBeadView: ClassReference(
> > > > "org.apache.royale.jewel.beads.views.FormItemView")
> > > > IFormItemContentArea: ClassReference("org.apache.royale.jewel.Group")
> > > >
> > > > These are the parts important to me.
> > > >
> > > > I think we really want to change only the IBeadView, so we can have a
> > > > FormItemView and a StackedFormItemView, and could change it vía
> > className
> > > > (for example)
> > > >
> > > > Let me know your thought about it
> > > >
> > > > thanks
> > > >
> > > > Carlos
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> > > > piotrzarzycki21@gmail.com>) escribió:
> > > >
> > > >> Carlos,
> > > >>
> > > >> I have analyzed FormItem in Flex and here is how it is done there.
> > > >> StackedFormItemSkin is using FormItemLayout which is constrained
> into
> > 3
> > > >> columns (sequenceCol, contentCol and helpCol) and 2 rows. [1][2]
> > > >>
> > > >> When you look into the screenshot [2] you may think that reuired
> > > indicator
> > > >> is part of the content, but it's not. It's not even part of the
> layout
> > > >> cause it has includeInLayout="false". [3]
> > > >> In Royale we don't have concept that something doesn't belong to
> > layout
> > > >> and
> > > >> is not calculated and indicator default is being placed in different
> > > area.
> > > >> Do you have some idea apart what I have proposed how to resolve
> that ?
> > > >>
> > > >> [1] https://paste.apache.org/9Imj
> > > >> [2] https://imgur.com/GGOtzEU
> > > >> [3] https://paste.apache.org/kqlP
> > > >>
> > > >> Thanks,
> > > >> Piotr
> > > >>
> > > >>
> > > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <pi...@gmail.com>
> > > >> napisał(a):
> > > >>
> > > >> > That's more clear to me. I will check and get back to you.
> > > >> >
> > > >> > Thank you!
> > > >> >
> > > >> >
> > > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <ca...@apache.org>
> > > >> > napisał(a):
> > > >> >
> > > >> >> No,
> > > >> >>
> > > >> >> I was asking you about how flex solves visualy the problem in
> their
> > > >> >> stacked
> > > >> >> version. The required icon is setup next to the label? is in
> other
> > > >> place?
> > > >> >> if we had an image of how it is designed (and like it), we can
> copy
> > > >> it. I
> > > >> >> still not proposing a technical solution. Just that I don't have
> > > clear
> > > >> how
> > > >> >> we should layout it
> > > >> >>
> > > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
> > > >> >> piotrzarzycki21@gmail.com>) escribió:
> > > >> >>
> > > >> >> > Carlos,
> > > >> >> >
> > > >> >> > Your suggestion is to have new form item (StackedFormItem) with
> > new
> > > >> >> > StackedFormItemView - cause problem is inside FormitemView, not
> > > >> inside
> > > >> >> > layout itself. Current layout is doing what it should do -
> apart
> > of
> > > >> the
> > > >> >> > problem - it's making children to be Horizontal/Vertical.
> > > >> >> >
> > > >> >> > If I'm correct what you are saying - that's ok, but if you have
> > had
> > > >> >> > different idea by saying above let me know.
> > > >> >> >
> > > >> >> > Thanks, Piotr
> > > >> >> >
> > > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <
> carlosrovira@apache.org>
> > > >> >> > napisał(a):
> > > >> >> >
> > > >> >> > > Ok, I understand now.
> > > >> >> > >
> > > >> >> > > In Flex I think we had that layout and was
> > > >> called....StackedFormItem
> > > >> >> or
> > > >> >> > > something like that?
> > > >> >> > > Could you check how Flex solve this? If we continue liking
> the
> > > way
> > > >> >> > stacked
> > > >> >> > > form layout in flex looks, we can do the same for our Royale
> > > >> version
> > > >> >> > >
> > > >> >> > >
> > > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
> > > >> >> > > piotrzarzycki21@gmail.com>) escribió:
> > > >> >> > >
> > > >> >> > > > I'm not sure how Serkan is doing that on users forum, but I
> > see
> > > >> all
> > > >> >> > hist
> > > >> >> > > > pasted images. Anyway here you go:
> > > >> >> > > >
> > > >> >> > > > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
> > > >> >> > > > What I got from Jewel FormItem: https://snag.gy/Slfbt9.jpg
> > > >> >> > > >
> > > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
> > > carlosrovira@apache.org>
> > > >> >> > > > napisał(a):
> > > >> >> > > >
> > > >> >> > > > > Piotr,
> > > >> >> > > > >
> > > >> >> > > > > remember that images pasted in list are not shared, you
> > must
> > > >> share
> > > >> >> > with
> > > >> >> > > > > some image service
> > > >> >> > > > >
> > > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
> > > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > >> >> > > > >
> > > >> >> > > > > > There is one more problem with Layout. Currently
> default
> > in
> > > >> >> > framework
> > > >> >> > > > we
> > > >> >> > > > > > have [1]. It means that:
> > > >> >> > > > > >
> > > >> >> > > > > > My content of FormItem will be vertical and IBeadLayout
> > is
> > > >> >> > basically
> > > >> >> > > > > > ignored at some point. If I specify beads -
> > > HorizontalLayout
> > > >> as
> > > >> >> it
> > > >> >> > is
> > > >> >> > > > in
> > > >> >> > > > > > above example it will be taken as a primary and I have
> my
> > > >> >> content
> > > >> >> > > > laying
> > > >> >> > > > > > out horizontally. The question is - what is for
> > > >> >> IFormItemLayout in
> > > >> >> > > > > > default.css? Is it a bug?
> > > >> >> > > > > >
> > > >> >> > > > > > [1] https://paste.apache.org/rV0K
> > > >> >> > > > > >
> > > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> > > >> >> piotrzarzycki21@gmail.com
> > > >> >> > >
> > > >> >> > > > > > napisał(a):
> > > >> >> > > > > >
> > > >> >> > > > > >> Hi Carlos,
> > > >> >> > > > > >>
> > > >> >> > > > > >> I'm was trying to change FormItem to be Vertical
> > oriented.
> > > >> In
> > > >> >> > > general
> > > >> >> > > > I
> > > >> >> > > > > >> would like to have following view. Label of FormItem
> is
> > on
> > > >> the
> > > >> >> top
> > > >> >> > > and
> > > >> >> > > > > in
> > > >> >> > > > > >> the bottom is content.
> > > >> >> > > > > >>
> > > >> >> > > > > >> [image: image.png]
> > > >> >> > > > > >>
> > > >> >> > > > > >> Code for that will looks like that [1]. Results is
> > > >> following:
> > > >> >> > > > > >>
> > > >> >> > > > > >> [image: image.png]
> > > >> >> > > > > >>
> > > >> >> > > > > >> It happened cause Label and required star label are
> > > >> different
> > > >> >> > > > components
> > > >> >> > > > > >> - everything is being laying out vertically. What is
> > your
> > > >> >> > suggestion
> > > >> >> > > > to
> > > >> >> > > > > fix
> > > >> >> > > > > >> that ?
> > > >> >> > > > > >>
> > > >> >> > > > > >> Mine is wrapping "First name" and "*" into one Group
> > with
> > > >> >> > > > > >> HorizontalLayout.
> > > >> >> > > > > >>
> > > >> >> > > > > >> More thoughts are welcome. I hope you see screenshots.
> > :)
> > > >> >> > > > > >>
> > > >> >> > > > > >> [1] https://paste.apache.org/5odt
> > > >> >> > > > > >>
> > > >> >> > > > > >> Thanks,
> > > >> >> > > > > >> --
> > > >> >> > > > > >>
> > > >> >> > > > > >> Piotr Zarzycki
> > > >> >> > > > > >>
> > > >> >> > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > >> >> > > > > >>
> > > >> >> > > > > >
> > > >> >> > > > > >
> > > >> >> > > > > > --
> > > >> >> > > > > >
> > > >> >> > > > > > Piotr Zarzycki
> > > >> >> > > > > >
> > > >> >> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > >> >> > > > > >
> > > >> >> > > > >
> > > >> >> > > > >
> > > >> >> > > > > --
> > > >> >> > > > > Carlos Rovira
> > > >> >> > > > > http://about.me/carlosrovira
> > > >> >> > > > >
> > > >> >> > > >
> > > >> >> > > >
> > > >> >> > > > --
> > > >> >> > > >
> > > >> >> > > > Piotr Zarzycki
> > > >> >> > > >
> > > >> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
> > > >> >> > > >
> > > >> >> > >
> > > >> >> > >
> > > >> >> > > --
> > > >> >> > > Carlos Rovira
> > > >> >> > > http://about.me/carlosrovira
> > > >> >> > >
> > > >> >> >
> > > >> >> >
> > > >> >> > --
> > > >> >> >
> > > >> >> > Piotr Zarzycki
> > > >> >> >
> > > >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > >> >> > <https://www.patreon.com/piotrzarzycki>*
> > > >> >> >
> > > >> >>
> > > >> >>
> > > >> >> --
> > > >> >> Carlos Rovira
> > > >> >> http://about.me/carlosrovira
> > > >> >>
> > > >> >
> > > >> >
> > > >> > --
> > > >> >
> > > >> > Piotr Zarzycki
> > > >> >
> > > >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > >> > <https://www.patreon.com/piotrzarzycki>*
> > > >> >
> > > >>
> > > >>
> > > >> --
> > > >>
> > > >> Piotr Zarzycki
> > > >>
> > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > >> <https://www.patreon.com/piotrzarzycki>*
> > > >>
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Carlos Rovira <ca...@apache.org>.

Hi Piotr,

since is what you show in the flex version.
I think Adobe put side to content instead of side to label since the user
fill the content elements and if not filled and required , the tooltip
should popup there.
IOW, for usability, seems more appropriated the way flex layedout, or seems
more natural.

El jue., 24 ene. 2019 a las 17:30, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> Carlos,
>
> Why you are proposing have that?
>
> L
> C *
>
> I'm in favor of staying
>
> L *
> C
>
> Thanks,
> Piotr
>
> On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <ca...@apache.org>
> wrote:
>
> > I forgot to mention about IBeadLayout more, since it could be
> > misinterpreted:
> >
> > IBeadLayout for the global component is important, but what I'm
> considering
> > is that although we can put HorizontalLayout (for the current FormtItem)
> > and VerticalLayout (for the stacked), I'm seeing that many components
> would
> > need its own layout class. In this case we could create a FormItemLayout,
> > and this will handle the layout vía CSS as it happens mostly in many
> other
> > Jewel component.
> >
> > (Just say that some of them are using an standard layout class, like
> > HorizontalLayout, or even a NullLayout class), since I didn't have the
> time
> > to create its own one, and that's temporal. But my plan is to create a
> > concrete layout for some of this components. FormItem could be one of
> those
> > cases, for what we're seeing
> >
> >
> >
> >
> >
> > El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<
> carlosrovira@apache.org
> > >)
> > escribió:
> >
> > > Hi Piotr,
> > >
> > > looking at the screen shot, seems the required indicator is positioned
> to
> > > the right side of the element, what seems coherent, although could be a
> > bit
> > > problematic depending on the width of the component. we assume a fixed
> > > width (to the widest element) and align all required (or not a put the
> > > required indicator just before the element, anyway this seems something
> > to
> > > be solved as we have some real implementation.
> > >
> > > In order to implement it:
> > >
> > > We have 3 parts:
> > > - L (this is the label)
> > > - * (this is the required indicator)
> > > - C (this is the element(s) that the user adds)
> > >
> > > * Actual FormItem is :
> > >
> > > L * C
> > >
> > > * We want for the new
> > >
> > > L
> > > C *
> > >
> > > So it seems to me that
> > >
> > > a) IBeadLayout: ClassReference(
> > > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> > > Does not has much sense to me
> > >
> > > b) IFormItemLayout: ClassReference(
> > > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> > >
> > > This is the one important to me (to configure), so user can change
> layout
> > > of the content part
> > >
> > > c) IBeadView: ClassReference(
> > > "org.apache.royale.jewel.beads.views.FormItemView")
> > > IFormItemContentArea: ClassReference("org.apache.royale.jewel.Group")
> > >
> > > These are the parts important to me.
> > >
> > > I think we really want to change only the IBeadView, so we can have a
> > > FormItemView and a StackedFormItemView, and could change it vía
> className
> > > (for example)
> > >
> > > Let me know your thought about it
> > >
> > > thanks
> > >
> > > Carlos
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> > > piotrzarzycki21@gmail.com>) escribió:
> > >
> > >> Carlos,
> > >>
> > >> I have analyzed FormItem in Flex and here is how it is done there.
> > >> StackedFormItemSkin is using FormItemLayout which is constrained into
> 3
> > >> columns (sequenceCol, contentCol and helpCol) and 2 rows. [1][2]
> > >>
> > >> When you look into the screenshot [2] you may think that reuired
> > indicator
> > >> is part of the content, but it's not. It's not even part of the layout
> > >> cause it has includeInLayout="false". [3]
> > >> In Royale we don't have concept that something doesn't belong to
> layout
> > >> and
> > >> is not calculated and indicator default is being placed in different
> > area.
> > >> Do you have some idea apart what I have proposed how to resolve that ?
> > >>
> > >> [1] https://paste.apache.org/9Imj
> > >> [2] https://imgur.com/GGOtzEU
> > >> [3] https://paste.apache.org/kqlP
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >>
> > >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <pi...@gmail.com>
> > >> napisał(a):
> > >>
> > >> > That's more clear to me. I will check and get back to you.
> > >> >
> > >> > Thank you!
> > >> >
> > >> >
> > >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <ca...@apache.org>
> > >> > napisał(a):
> > >> >
> > >> >> No,
> > >> >>
> > >> >> I was asking you about how flex solves visualy the problem in their
> > >> >> stacked
> > >> >> version. The required icon is setup next to the label? is in other
> > >> place?
> > >> >> if we had an image of how it is designed (and like it), we can copy
> > >> it. I
> > >> >> still not proposing a technical solution. Just that I don't have
> > clear
> > >> how
> > >> >> we should layout it
> > >> >>
> > >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
> > >> >> piotrzarzycki21@gmail.com>) escribió:
> > >> >>
> > >> >> > Carlos,
> > >> >> >
> > >> >> > Your suggestion is to have new form item (StackedFormItem) with
> new
> > >> >> > StackedFormItemView - cause problem is inside FormitemView, not
> > >> inside
> > >> >> > layout itself. Current layout is doing what it should do - apart
> of
> > >> the
> > >> >> > problem - it's making children to be Horizontal/Vertical.
> > >> >> >
> > >> >> > If I'm correct what you are saying - that's ok, but if you have
> had
> > >> >> > different idea by saying above let me know.
> > >> >> >
> > >> >> > Thanks, Piotr
> > >> >> >
> > >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <ca...@apache.org>
> > >> >> > napisał(a):
> > >> >> >
> > >> >> > > Ok, I understand now.
> > >> >> > >
> > >> >> > > In Flex I think we had that layout and was
> > >> called....StackedFormItem
> > >> >> or
> > >> >> > > something like that?
> > >> >> > > Could you check how Flex solve this? If we continue liking the
> > way
> > >> >> > stacked
> > >> >> > > form layout in flex looks, we can do the same for our Royale
> > >> version
> > >> >> > >
> > >> >> > >
> > >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
> > >> >> > > piotrzarzycki21@gmail.com>) escribió:
> > >> >> > >
> > >> >> > > > I'm not sure how Serkan is doing that on users forum, but I
> see
> > >> all
> > >> >> > hist
> > >> >> > > > pasted images. Anyway here you go:
> > >> >> > > >
> > >> >> > > > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
> > >> >> > > > What I got from Jewel FormItem: https://snag.gy/Slfbt9.jpg
> > >> >> > > >
> > >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
> > carlosrovira@apache.org>
> > >> >> > > > napisał(a):
> > >> >> > > >
> > >> >> > > > > Piotr,
> > >> >> > > > >
> > >> >> > > > > remember that images pasted in list are not shared, you
> must
> > >> share
> > >> >> > with
> > >> >> > > > > some image service
> > >> >> > > > >
> > >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
> > >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> > >> >> > > > >
> > >> >> > > > > > There is one more problem with Layout. Currently default
> in
> > >> >> > framework
> > >> >> > > > we
> > >> >> > > > > > have [1]. It means that:
> > >> >> > > > > >
> > >> >> > > > > > My content of FormItem will be vertical and IBeadLayout
> is
> > >> >> > basically
> > >> >> > > > > > ignored at some point. If I specify beads -
> > HorizontalLayout
> > >> as
> > >> >> it
> > >> >> > is
> > >> >> > > > in
> > >> >> > > > > > above example it will be taken as a primary and I have my
> > >> >> content
> > >> >> > > > laying
> > >> >> > > > > > out horizontally. The question is - what is for
> > >> >> IFormItemLayout in
> > >> >> > > > > > default.css? Is it a bug?
> > >> >> > > > > >
> > >> >> > > > > > [1] https://paste.apache.org/rV0K
> > >> >> > > > > >
> > >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> > >> >> piotrzarzycki21@gmail.com
> > >> >> > >
> > >> >> > > > > > napisał(a):
> > >> >> > > > > >
> > >> >> > > > > >> Hi Carlos,
> > >> >> > > > > >>
> > >> >> > > > > >> I'm was trying to change FormItem to be Vertical
> oriented.
> > >> In
> > >> >> > > general
> > >> >> > > > I
> > >> >> > > > > >> would like to have following view. Label of FormItem is
> on
> > >> the
> > >> >> top
> > >> >> > > and
> > >> >> > > > > in
> > >> >> > > > > >> the bottom is content.
> > >> >> > > > > >>
> > >> >> > > > > >> [image: image.png]
> > >> >> > > > > >>
> > >> >> > > > > >> Code for that will looks like that [1]. Results is
> > >> following:
> > >> >> > > > > >>
> > >> >> > > > > >> [image: image.png]
> > >> >> > > > > >>
> > >> >> > > > > >> It happened cause Label and required star label are
> > >> different
> > >> >> > > > components
> > >> >> > > > > >> - everything is being laying out vertically. What is
> your
> > >> >> > suggestion
> > >> >> > > > to
> > >> >> > > > > fix
> > >> >> > > > > >> that ?
> > >> >> > > > > >>
> > >> >> > > > > >> Mine is wrapping "First name" and "*" into one Group
> with
> > >> >> > > > > >> HorizontalLayout.
> > >> >> > > > > >>
> > >> >> > > > > >> More thoughts are welcome. I hope you see screenshots.
> :)
> > >> >> > > > > >>
> > >> >> > > > > >> [1] https://paste.apache.org/5odt
> > >> >> > > > > >>
> > >> >> > > > > >> Thanks,
> > >> >> > > > > >> --
> > >> >> > > > > >>
> > >> >> > > > > >> Piotr Zarzycki
> > >> >> > > > > >>
> > >> >> > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > >> >> > > > > >>
> > >> >> > > > > >
> > >> >> > > > > >
> > >> >> > > > > > --
> > >> >> > > > > >
> > >> >> > > > > > Piotr Zarzycki
> > >> >> > > > > >
> > >> >> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > >> >> > > > > >
> > >> >> > > > >
> > >> >> > > > >
> > >> >> > > > > --
> > >> >> > > > > Carlos Rovira
> > >> >> > > > > http://about.me/carlosrovira
> > >> >> > > > >
> > >> >> > > >
> > >> >> > > >
> > >> >> > > > --
> > >> >> > > >
> > >> >> > > > Piotr Zarzycki
> > >> >> > > >
> > >> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > >> >> > > > <https://www.patreon.com/piotrzarzycki>*
> > >> >> > > >
> > >> >> > >
> > >> >> > >
> > >> >> > > --
> > >> >> > > Carlos Rovira
> > >> >> > > http://about.me/carlosrovira
> > >> >> > >
> > >> >> >
> > >> >> >
> > >> >> > --
> > >> >> >
> > >> >> > Piotr Zarzycki
> > >> >> >
> > >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > >> >> > <https://www.patreon.com/piotrzarzycki>*
> > >> >> >
> > >> >>
> > >> >>
> > >> >> --
> > >> >> Carlos Rovira
> > >> >> http://about.me/carlosrovira
> > >> >>
> > >> >
> > >> >
> > >> > --
> > >> >
> > >> > Piotr Zarzycki
> > >> >
> > >> > Patreon: *https://www.patreon.com/piotrzarzycki
> > >> > <https://www.patreon.com/piotrzarzycki>*
> > >> >
> > >>
> > >>
> > >> --
> > >>
> > >> Piotr Zarzycki
> > >>
> > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > >> <https://www.patreon.com/piotrzarzycki>*
> > >>
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> > >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>


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

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

Carlos,

Why you are proposing have that?

L
C *

I'm in favor of staying

L *
C

Thanks,
Piotr

On Thu, Jan 24, 2019, 4:56 PM Carlos Rovira <ca...@apache.org> wrote:

> I forgot to mention about IBeadLayout more, since it could be
> misinterpreted:
>
> IBeadLayout for the global component is important, but what I'm considering
> is that although we can put HorizontalLayout (for the current FormtItem)
> and VerticalLayout (for the stacked), I'm seeing that many components would
> need its own layout class. In this case we could create a FormItemLayout,
> and this will handle the layout vía CSS as it happens mostly in many other
> Jewel component.
>
> (Just say that some of them are using an standard layout class, like
> HorizontalLayout, or even a NullLayout class), since I didn't have the time
> to create its own one, and that's temporal. But my plan is to create a
> concrete layout for some of this components. FormItem could be one of those
> cases, for what we're seeing
>
>
>
>
>
> El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<carlosrovira@apache.org
> >)
> escribió:
>
> > Hi Piotr,
> >
> > looking at the screen shot, seems the required indicator is positioned to
> > the right side of the element, what seems coherent, although could be a
> bit
> > problematic depending on the width of the component. we assume a fixed
> > width (to the widest element) and align all required (or not a put the
> > required indicator just before the element, anyway this seems something
> to
> > be solved as we have some real implementation.
> >
> > In order to implement it:
> >
> > We have 3 parts:
> > - L (this is the label)
> > - * (this is the required indicator)
> > - C (this is the element(s) that the user adds)
> >
> > * Actual FormItem is :
> >
> > L * C
> >
> > * We want for the new
> >
> > L
> > C *
> >
> > So it seems to me that
> >
> > a) IBeadLayout: ClassReference(
> > "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> > Does not has much sense to me
> >
> > b) IFormItemLayout: ClassReference(
> > "org.apache.royale.jewel.beads.layouts.VerticalLayout")
> >
> > This is the one important to me (to configure), so user can change layout
> > of the content part
> >
> > c) IBeadView: ClassReference(
> > "org.apache.royale.jewel.beads.views.FormItemView")
> > IFormItemContentArea: ClassReference("org.apache.royale.jewel.Group")
> >
> > These are the parts important to me.
> >
> > I think we really want to change only the IBeadView, so we can have a
> > FormItemView and a StackedFormItemView, and could change it vía className
> > (for example)
> >
> > Let me know your thought about it
> >
> > thanks
> >
> > Carlos
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> >> Carlos,
> >>
> >> I have analyzed FormItem in Flex and here is how it is done there.
> >> StackedFormItemSkin is using FormItemLayout which is constrained into 3
> >> columns (sequenceCol, contentCol and helpCol) and 2 rows. [1][2]
> >>
> >> When you look into the screenshot [2] you may think that reuired
> indicator
> >> is part of the content, but it's not. It's not even part of the layout
> >> cause it has includeInLayout="false". [3]
> >> In Royale we don't have concept that something doesn't belong to layout
> >> and
> >> is not calculated and indicator default is being placed in different
> area.
> >> Do you have some idea apart what I have proposed how to resolve that ?
> >>
> >> [1] https://paste.apache.org/9Imj
> >> [2] https://imgur.com/GGOtzEU
> >> [3] https://paste.apache.org/kqlP
> >>
> >> Thanks,
> >> Piotr
> >>
> >>
> >> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <pi...@gmail.com>
> >> napisał(a):
> >>
> >> > That's more clear to me. I will check and get back to you.
> >> >
> >> > Thank you!
> >> >
> >> >
> >> > śr., 23 sty 2019 o 18:03 Carlos Rovira <ca...@apache.org>
> >> > napisał(a):
> >> >
> >> >> No,
> >> >>
> >> >> I was asking you about how flex solves visualy the problem in their
> >> >> stacked
> >> >> version. The required icon is setup next to the label? is in other
> >> place?
> >> >> if we had an image of how it is designed (and like it), we can copy
> >> it. I
> >> >> still not proposing a technical solution. Just that I don't have
> clear
> >> how
> >> >> we should layout it
> >> >>
> >> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
> >> >> piotrzarzycki21@gmail.com>) escribió:
> >> >>
> >> >> > Carlos,
> >> >> >
> >> >> > Your suggestion is to have new form item (StackedFormItem) with new
> >> >> > StackedFormItemView - cause problem is inside FormitemView, not
> >> inside
> >> >> > layout itself. Current layout is doing what it should do - apart of
> >> the
> >> >> > problem - it's making children to be Horizontal/Vertical.
> >> >> >
> >> >> > If I'm correct what you are saying - that's ok, but if you have had
> >> >> > different idea by saying above let me know.
> >> >> >
> >> >> > Thanks, Piotr
> >> >> >
> >> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <ca...@apache.org>
> >> >> > napisał(a):
> >> >> >
> >> >> > > Ok, I understand now.
> >> >> > >
> >> >> > > In Flex I think we had that layout and was
> >> called....StackedFormItem
> >> >> or
> >> >> > > something like that?
> >> >> > > Could you check how Flex solve this? If we continue liking the
> way
> >> >> > stacked
> >> >> > > form layout in flex looks, we can do the same for our Royale
> >> version
> >> >> > >
> >> >> > >
> >> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
> >> >> > > piotrzarzycki21@gmail.com>) escribió:
> >> >> > >
> >> >> > > > I'm not sure how Serkan is doing that on users forum, but I see
> >> all
> >> >> > hist
> >> >> > > > pasted images. Anyway here you go:
> >> >> > > >
> >> >> > > > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
> >> >> > > > What I got from Jewel FormItem: https://snag.gy/Slfbt9.jpg
> >> >> > > >
> >> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <
> carlosrovira@apache.org>
> >> >> > > > napisał(a):
> >> >> > > >
> >> >> > > > > Piotr,
> >> >> > > > >
> >> >> > > > > remember that images pasted in list are not shared, you must
> >> share
> >> >> > with
> >> >> > > > > some image service
> >> >> > > > >
> >> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
> >> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> >> >> > > > >
> >> >> > > > > > There is one more problem with Layout. Currently default in
> >> >> > framework
> >> >> > > > we
> >> >> > > > > > have [1]. It means that:
> >> >> > > > > >
> >> >> > > > > > My content of FormItem will be vertical and IBeadLayout is
> >> >> > basically
> >> >> > > > > > ignored at some point. If I specify beads -
> HorizontalLayout
> >> as
> >> >> it
> >> >> > is
> >> >> > > > in
> >> >> > > > > > above example it will be taken as a primary and I have my
> >> >> content
> >> >> > > > laying
> >> >> > > > > > out horizontally. The question is - what is for
> >> >> IFormItemLayout in
> >> >> > > > > > default.css? Is it a bug?
> >> >> > > > > >
> >> >> > > > > > [1] https://paste.apache.org/rV0K
> >> >> > > > > >
> >> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> >> >> piotrzarzycki21@gmail.com
> >> >> > >
> >> >> > > > > > napisał(a):
> >> >> > > > > >
> >> >> > > > > >> Hi Carlos,
> >> >> > > > > >>
> >> >> > > > > >> I'm was trying to change FormItem to be Vertical oriented.
> >> In
> >> >> > > general
> >> >> > > > I
> >> >> > > > > >> would like to have following view. Label of FormItem is on
> >> the
> >> >> top
> >> >> > > and
> >> >> > > > > in
> >> >> > > > > >> the bottom is content.
> >> >> > > > > >>
> >> >> > > > > >> [image: image.png]
> >> >> > > > > >>
> >> >> > > > > >> Code for that will looks like that [1]. Results is
> >> following:
> >> >> > > > > >>
> >> >> > > > > >> [image: image.png]
> >> >> > > > > >>
> >> >> > > > > >> It happened cause Label and required star label are
> >> different
> >> >> > > > components
> >> >> > > > > >> - everything is being laying out vertically. What is your
> >> >> > suggestion
> >> >> > > > to
> >> >> > > > > fix
> >> >> > > > > >> that ?
> >> >> > > > > >>
> >> >> > > > > >> Mine is wrapping "First name" and "*" into one Group with
> >> >> > > > > >> HorizontalLayout.
> >> >> > > > > >>
> >> >> > > > > >> More thoughts are welcome. I hope you see screenshots. :)
> >> >> > > > > >>
> >> >> > > > > >> [1] https://paste.apache.org/5odt
> >> >> > > > > >>
> >> >> > > > > >> Thanks,
> >> >> > > > > >> --
> >> >> > > > > >>
> >> >> > > > > >> Piotr Zarzycki
> >> >> > > > > >>
> >> >> > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> >> >> > > > > >>
> >> >> > > > > >
> >> >> > > > > >
> >> >> > > > > > --
> >> >> > > > > >
> >> >> > > > > > Piotr Zarzycki
> >> >> > > > > >
> >> >> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> >> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
> >> >> > > > > >
> >> >> > > > >
> >> >> > > > >
> >> >> > > > > --
> >> >> > > > > Carlos Rovira
> >> >> > > > > http://about.me/carlosrovira
> >> >> > > > >
> >> >> > > >
> >> >> > > >
> >> >> > > > --
> >> >> > > >
> >> >> > > > Piotr Zarzycki
> >> >> > > >
> >> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> >> >> > > > <https://www.patreon.com/piotrzarzycki>*
> >> >> > > >
> >> >> > >
> >> >> > >
> >> >> > > --
> >> >> > > Carlos Rovira
> >> >> > > http://about.me/carlosrovira
> >> >> > >
> >> >> >
> >> >> >
> >> >> > --
> >> >> >
> >> >> > Piotr Zarzycki
> >> >> >
> >> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> >> >> > <https://www.patreon.com/piotrzarzycki>*
> >> >> >
> >> >>
> >> >>
> >> >> --
> >> >> Carlos Rovira
> >> >> http://about.me/carlosrovira
> >> >>
> >> >
> >> >
> >> > --
> >> >
> >> > Piotr Zarzycki
> >> >
> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> >> > <https://www.patreon.com/piotrzarzycki>*
> >> >
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> <https://www.patreon.com/piotrzarzycki>*
> >>
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

Re: Vertical FormItem

Posted by Carlos Rovira <ca...@apache.org>.

I forgot to mention about IBeadLayout more, since it could be
misinterpreted:

IBeadLayout for the global component is important, but what I'm considering
is that although we can put HorizontalLayout (for the current FormtItem)
and VerticalLayout (for the stacked), I'm seeing that many components would
need its own layout class. In this case we could create a FormItemLayout,
and this will handle the layout vía CSS as it happens mostly in many other
Jewel component.

(Just say that some of them are using an standard layout class, like
HorizontalLayout, or even a NullLayout class), since I didn't have the time
to create its own one, and that's temporal. But my plan is to create a
concrete layout for some of this components. FormItem could be one of those
cases, for what we're seeing





El jue., 24 ene. 2019 a las 16:50, Carlos Rovira (<ca...@apache.org>)
escribió:

> Hi Piotr,
>
> looking at the screen shot, seems the required indicator is positioned to
> the right side of the element, what seems coherent, although could be a bit
> problematic depending on the width of the component. we assume a fixed
> width (to the widest element) and align all required (or not a put the
> required indicator just before the element, anyway this seems something to
> be solved as we have some real implementation.
>
> In order to implement it:
>
> We have 3 parts:
> - L (this is the label)
> - * (this is the required indicator)
> - C (this is the element(s) that the user adds)
>
> * Actual FormItem is :
>
> L * C
>
> * We want for the new
>
> L
> C *
>
> So it seems to me that
>
> a) IBeadLayout: ClassReference(
> "org.apache.royale.jewel.beads.layouts.HorizontalLayout")
> Does not has much sense to me
>
> b) IFormItemLayout: ClassReference(
> "org.apache.royale.jewel.beads.layouts.VerticalLayout")
>
> This is the one important to me (to configure), so user can change layout
> of the content part
>
> c) IBeadView: ClassReference(
> "org.apache.royale.jewel.beads.views.FormItemView")
> IFormItemContentArea: ClassReference("org.apache.royale.jewel.Group")
>
> These are the parts important to me.
>
> I think we really want to change only the IBeadView, so we can have a
> FormItemView and a StackedFormItemView, and could change it vía className
> (for example)
>
> Let me know your thought about it
>
> thanks
>
> Carlos
>
>
>
>
>
>
>
>
>
> El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
>> Carlos,
>>
>> I have analyzed FormItem in Flex and here is how it is done there.
>> StackedFormItemSkin is using FormItemLayout which is constrained into 3
>> columns (sequenceCol, contentCol and helpCol) and 2 rows. [1][2]
>>
>> When you look into the screenshot [2] you may think that reuired indicator
>> is part of the content, but it's not. It's not even part of the layout
>> cause it has includeInLayout="false". [3]
>> In Royale we don't have concept that something doesn't belong to layout
>> and
>> is not calculated and indicator default is being placed in different area.
>> Do you have some idea apart what I have proposed how to resolve that ?
>>
>> [1] https://paste.apache.org/9Imj
>> [2] https://imgur.com/GGOtzEU
>> [3] https://paste.apache.org/kqlP
>>
>> Thanks,
>> Piotr
>>
>>
>> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <pi...@gmail.com>
>> napisał(a):
>>
>> > That's more clear to me. I will check and get back to you.
>> >
>> > Thank you!
>> >
>> >
>> > śr., 23 sty 2019 o 18:03 Carlos Rovira <ca...@apache.org>
>> > napisał(a):
>> >
>> >> No,
>> >>
>> >> I was asking you about how flex solves visualy the problem in their
>> >> stacked
>> >> version. The required icon is setup next to the label? is in other
>> place?
>> >> if we had an image of how it is designed (and like it), we can copy
>> it. I
>> >> still not proposing a technical solution. Just that I don't have clear
>> how
>> >> we should layout it
>> >>
>> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
>> >> piotrzarzycki21@gmail.com>) escribió:
>> >>
>> >> > Carlos,
>> >> >
>> >> > Your suggestion is to have new form item (StackedFormItem) with new
>> >> > StackedFormItemView - cause problem is inside FormitemView, not
>> inside
>> >> > layout itself. Current layout is doing what it should do - apart of
>> the
>> >> > problem - it's making children to be Horizontal/Vertical.
>> >> >
>> >> > If I'm correct what you are saying - that's ok, but if you have had
>> >> > different idea by saying above let me know.
>> >> >
>> >> > Thanks, Piotr
>> >> >
>> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <ca...@apache.org>
>> >> > napisał(a):
>> >> >
>> >> > > Ok, I understand now.
>> >> > >
>> >> > > In Flex I think we had that layout and was
>> called....StackedFormItem
>> >> or
>> >> > > something like that?
>> >> > > Could you check how Flex solve this? If we continue liking the way
>> >> > stacked
>> >> > > form layout in flex looks, we can do the same for our Royale
>> version
>> >> > >
>> >> > >
>> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
>> >> > > piotrzarzycki21@gmail.com>) escribió:
>> >> > >
>> >> > > > I'm not sure how Serkan is doing that on users forum, but I see
>> all
>> >> > hist
>> >> > > > pasted images. Anyway here you go:
>> >> > > >
>> >> > > > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
>> >> > > > What I got from Jewel FormItem: https://snag.gy/Slfbt9.jpg
>> >> > > >
>> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <ca...@apache.org>
>> >> > > > napisał(a):
>> >> > > >
>> >> > > > > Piotr,
>> >> > > > >
>> >> > > > > remember that images pasted in list are not shared, you must
>> share
>> >> > with
>> >> > > > > some image service
>> >> > > > >
>> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
>> >> > > > > piotrzarzycki21@gmail.com>) escribió:
>> >> > > > >
>> >> > > > > > There is one more problem with Layout. Currently default in
>> >> > framework
>> >> > > > we
>> >> > > > > > have [1]. It means that:
>> >> > > > > >
>> >> > > > > > My content of FormItem will be vertical and IBeadLayout is
>> >> > basically
>> >> > > > > > ignored at some point. If I specify beads - HorizontalLayout
>> as
>> >> it
>> >> > is
>> >> > > > in
>> >> > > > > > above example it will be taken as a primary and I have my
>> >> content
>> >> > > > laying
>> >> > > > > > out horizontally. The question is - what is for
>> >> IFormItemLayout in
>> >> > > > > > default.css? Is it a bug?
>> >> > > > > >
>> >> > > > > > [1] https://paste.apache.org/rV0K
>> >> > > > > >
>> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
>> >> piotrzarzycki21@gmail.com
>> >> > >
>> >> > > > > > napisał(a):
>> >> > > > > >
>> >> > > > > >> Hi Carlos,
>> >> > > > > >>
>> >> > > > > >> I'm was trying to change FormItem to be Vertical oriented.
>> In
>> >> > > general
>> >> > > > I
>> >> > > > > >> would like to have following view. Label of FormItem is on
>> the
>> >> top
>> >> > > and
>> >> > > > > in
>> >> > > > > >> the bottom is content.
>> >> > > > > >>
>> >> > > > > >> [image: image.png]
>> >> > > > > >>
>> >> > > > > >> Code for that will looks like that [1]. Results is
>> following:
>> >> > > > > >>
>> >> > > > > >> [image: image.png]
>> >> > > > > >>
>> >> > > > > >> It happened cause Label and required star label are
>> different
>> >> > > > components
>> >> > > > > >> - everything is being laying out vertically. What is your
>> >> > suggestion
>> >> > > > to
>> >> > > > > fix
>> >> > > > > >> that ?
>> >> > > > > >>
>> >> > > > > >> Mine is wrapping "First name" and "*" into one Group with
>> >> > > > > >> HorizontalLayout.
>> >> > > > > >>
>> >> > > > > >> More thoughts are welcome. I hope you see screenshots. :)
>> >> > > > > >>
>> >> > > > > >> [1] https://paste.apache.org/5odt
>> >> > > > > >>
>> >> > > > > >> Thanks,
>> >> > > > > >> --
>> >> > > > > >>
>> >> > > > > >> Piotr Zarzycki
>> >> > > > > >>
>> >> > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
>> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
>> >> > > > > >>
>> >> > > > > >
>> >> > > > > >
>> >> > > > > > --
>> >> > > > > >
>> >> > > > > > Piotr Zarzycki
>> >> > > > > >
>> >> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
>> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
>> >> > > > > >
>> >> > > > >
>> >> > > > >
>> >> > > > > --
>> >> > > > > Carlos Rovira
>> >> > > > > http://about.me/carlosrovira
>> >> > > > >
>> >> > > >
>> >> > > >
>> >> > > > --
>> >> > > >
>> >> > > > Piotr Zarzycki
>> >> > > >
>> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
>> >> > > > <https://www.patreon.com/piotrzarzycki>*
>> >> > > >
>> >> > >
>> >> > >
>> >> > > --
>> >> > > Carlos Rovira
>> >> > > http://about.me/carlosrovira
>> >> > >
>> >> >
>> >> >
>> >> > --
>> >> >
>> >> > Piotr Zarzycki
>> >> >
>> >> > Patreon: *https://www.patreon.com/piotrzarzycki
>> >> > <https://www.patreon.com/piotrzarzycki>*
>> >> >
>> >>
>> >>
>> >> --
>> >> Carlos Rovira
>> >> http://about.me/carlosrovira
>> >>
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: *https://www.patreon.com/piotrzarzycki
>> > <https://www.patreon.com/piotrzarzycki>*
>> >
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

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

Re: Vertical FormItem

Posted by Carlos Rovira <ca...@apache.org>.

Hi Piotr,

looking at the screen shot, seems the required indicator is positioned to
the right side of the element, what seems coherent, although could be a bit
problematic depending on the width of the component. we assume a fixed
width (to the widest element) and align all required (or not a put the
required indicator just before the element, anyway this seems something to
be solved as we have some real implementation.

In order to implement it:

We have 3 parts:
- L (this is the label)
- * (this is the required indicator)
- C (this is the element(s) that the user adds)

* Actual FormItem is :

L * C

* We want for the new

L
C *

So it seems to me that

a) IBeadLayout: ClassReference(
"org.apache.royale.jewel.beads.layouts.HorizontalLayout")
Does not has much sense to me

b) IFormItemLayout: ClassReference(
"org.apache.royale.jewel.beads.layouts.VerticalLayout")

This is the one important to me (to configure), so user can change layout
of the content part

c) IBeadView: ClassReference(
"org.apache.royale.jewel.beads.views.FormItemView")
IFormItemContentArea: ClassReference("org.apache.royale.jewel.Group")

These are the parts important to me.

I think we really want to change only the IBeadView, so we can have a
FormItemView and a StackedFormItemView, and could change it vía className
(for example)

Let me know your thought about it

thanks

Carlos









El jue., 24 ene. 2019 a las 16:08, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> Carlos,
>
> I have analyzed FormItem in Flex and here is how it is done there.
> StackedFormItemSkin is using FormItemLayout which is constrained into 3
> columns (sequenceCol, contentCol and helpCol) and 2 rows. [1][2]
>
> When you look into the screenshot [2] you may think that reuired indicator
> is part of the content, but it's not. It's not even part of the layout
> cause it has includeInLayout="false". [3]
> In Royale we don't have concept that something doesn't belong to layout and
> is not calculated and indicator default is being placed in different area.
> Do you have some idea apart what I have proposed how to resolve that ?
>
> [1] https://paste.apache.org/9Imj
> [2] https://imgur.com/GGOtzEU
> [3] https://paste.apache.org/kqlP
>
> Thanks,
> Piotr
>
>
> śr., 23 sty 2019 o 18:08 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > That's more clear to me. I will check and get back to you.
> >
> > Thank you!
> >
> >
> > śr., 23 sty 2019 o 18:03 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> >> No,
> >>
> >> I was asking you about how flex solves visualy the problem in their
> >> stacked
> >> version. The required icon is setup next to the label? is in other
> place?
> >> if we had an image of how it is designed (and like it), we can copy it.
> I
> >> still not proposing a technical solution. Just that I don't have clear
> how
> >> we should layout it
> >>
> >> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
> >> piotrzarzycki21@gmail.com>) escribió:
> >>
> >> > Carlos,
> >> >
> >> > Your suggestion is to have new form item (StackedFormItem) with new
> >> > StackedFormItemView - cause problem is inside FormitemView, not inside
> >> > layout itself. Current layout is doing what it should do - apart of
> the
> >> > problem - it's making children to be Horizontal/Vertical.
> >> >
> >> > If I'm correct what you are saying - that's ok, but if you have had
> >> > different idea by saying above let me know.
> >> >
> >> > Thanks, Piotr
> >> >
> >> > śr., 23 sty 2019 o 17:14 Carlos Rovira <ca...@apache.org>
> >> > napisał(a):
> >> >
> >> > > Ok, I understand now.
> >> > >
> >> > > In Flex I think we had that layout and was called....StackedFormItem
> >> or
> >> > > something like that?
> >> > > Could you check how Flex solve this? If we continue liking the way
> >> > stacked
> >> > > form layout in flex looks, we can do the same for our Royale version
> >> > >
> >> > >
> >> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
> >> > > piotrzarzycki21@gmail.com>) escribió:
> >> > >
> >> > > > I'm not sure how Serkan is doing that on users forum, but I see
> all
> >> > hist
> >> > > > pasted images. Anyway here you go:
> >> > > >
> >> > > > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
> >> > > > What I got from Jewel FormItem: https://snag.gy/Slfbt9.jpg
> >> > > >
> >> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <ca...@apache.org>
> >> > > > napisał(a):
> >> > > >
> >> > > > > Piotr,
> >> > > > >
> >> > > > > remember that images pasted in list are not shared, you must
> share
> >> > with
> >> > > > > some image service
> >> > > > >
> >> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
> >> > > > > piotrzarzycki21@gmail.com>) escribió:
> >> > > > >
> >> > > > > > There is one more problem with Layout. Currently default in
> >> > framework
> >> > > > we
> >> > > > > > have [1]. It means that:
> >> > > > > >
> >> > > > > > My content of FormItem will be vertical and IBeadLayout is
> >> > basically
> >> > > > > > ignored at some point. If I specify beads - HorizontalLayout
> as
> >> it
> >> > is
> >> > > > in
> >> > > > > > above example it will be taken as a primary and I have my
> >> content
> >> > > > laying
> >> > > > > > out horizontally. The question is - what is for
> >> IFormItemLayout in
> >> > > > > > default.css? Is it a bug?
> >> > > > > >
> >> > > > > > [1] https://paste.apache.org/rV0K
> >> > > > > >
> >> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> >> piotrzarzycki21@gmail.com
> >> > >
> >> > > > > > napisał(a):
> >> > > > > >
> >> > > > > >> Hi Carlos,
> >> > > > > >>
> >> > > > > >> I'm was trying to change FormItem to be Vertical oriented. In
> >> > > general
> >> > > > I
> >> > > > > >> would like to have following view. Label of FormItem is on
> the
> >> top
> >> > > and
> >> > > > > in
> >> > > > > >> the bottom is content.
> >> > > > > >>
> >> > > > > >> [image: image.png]
> >> > > > > >>
> >> > > > > >> Code for that will looks like that [1]. Results is following:
> >> > > > > >>
> >> > > > > >> [image: image.png]
> >> > > > > >>
> >> > > > > >> It happened cause Label and required star label are different
> >> > > > components
> >> > > > > >> - everything is being laying out vertically. What is your
> >> > suggestion
> >> > > > to
> >> > > > > fix
> >> > > > > >> that ?
> >> > > > > >>
> >> > > > > >> Mine is wrapping "First name" and "*" into one Group with
> >> > > > > >> HorizontalLayout.
> >> > > > > >>
> >> > > > > >> More thoughts are welcome. I hope you see screenshots. :)
> >> > > > > >>
> >> > > > > >> [1] https://paste.apache.org/5odt
> >> > > > > >>
> >> > > > > >> Thanks,
> >> > > > > >> --
> >> > > > > >>
> >> > > > > >> Piotr Zarzycki
> >> > > > > >>
> >> > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> >> > > > > >>
> >> > > > > >
> >> > > > > >
> >> > > > > > --
> >> > > > > >
> >> > > > > > Piotr Zarzycki
> >> > > > > >
> >> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> >> > > > > > <https://www.patreon.com/piotrzarzycki>*
> >> > > > > >
> >> > > > >
> >> > > > >
> >> > > > > --
> >> > > > > Carlos Rovira
> >> > > > > http://about.me/carlosrovira
> >> > > > >
> >> > > >
> >> > > >
> >> > > > --
> >> > > >
> >> > > > Piotr Zarzycki
> >> > > >
> >> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> >> > > > <https://www.patreon.com/piotrzarzycki>*
> >> > > >
> >> > >
> >> > >
> >> > > --
> >> > > Carlos Rovira
> >> > > http://about.me/carlosrovira
> >> > >
> >> >
> >> >
> >> > --
> >> >
> >> > Piotr Zarzycki
> >> >
> >> > Patreon: *https://www.patreon.com/piotrzarzycki
> >> > <https://www.patreon.com/piotrzarzycki>*
> >> >
> >>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

Carlos,

I have analyzed FormItem in Flex and here is how it is done there.
StackedFormItemSkin is using FormItemLayout which is constrained into 3
columns (sequenceCol, contentCol and helpCol) and 2 rows. [1][2]

When you look into the screenshot [2] you may think that reuired indicator
is part of the content, but it's not. It's not even part of the layout
cause it has includeInLayout="false". [3]
In Royale we don't have concept that something doesn't belong to layout and
is not calculated and indicator default is being placed in different area.
Do you have some idea apart what I have proposed how to resolve that ?

[1] https://paste.apache.org/9Imj
[2] https://imgur.com/GGOtzEU
[3] https://paste.apache.org/kqlP

Thanks,
Piotr


śr., 23 sty 2019 o 18:08 Piotr Zarzycki <pi...@gmail.com>
napisał(a):

> That's more clear to me. I will check and get back to you.
>
> Thank you!
>
>
> śr., 23 sty 2019 o 18:03 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
>> No,
>>
>> I was asking you about how flex solves visualy the problem in their
>> stacked
>> version. The required icon is setup next to the label? is in other place?
>> if we had an image of how it is designed (and like it), we can copy it. I
>> still not proposing a technical solution. Just that I don't have clear how
>> we should layout it
>>
>> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
>> piotrzarzycki21@gmail.com>) escribió:
>>
>> > Carlos,
>> >
>> > Your suggestion is to have new form item (StackedFormItem) with new
>> > StackedFormItemView - cause problem is inside FormitemView, not inside
>> > layout itself. Current layout is doing what it should do - apart of the
>> > problem - it's making children to be Horizontal/Vertical.
>> >
>> > If I'm correct what you are saying - that's ok, but if you have had
>> > different idea by saying above let me know.
>> >
>> > Thanks, Piotr
>> >
>> > śr., 23 sty 2019 o 17:14 Carlos Rovira <ca...@apache.org>
>> > napisał(a):
>> >
>> > > Ok, I understand now.
>> > >
>> > > In Flex I think we had that layout and was called....StackedFormItem
>> or
>> > > something like that?
>> > > Could you check how Flex solve this? If we continue liking the way
>> > stacked
>> > > form layout in flex looks, we can do the same for our Royale version
>> > >
>> > >
>> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
>> > > piotrzarzycki21@gmail.com>) escribió:
>> > >
>> > > > I'm not sure how Serkan is doing that on users forum, but I see all
>> > hist
>> > > > pasted images. Anyway here you go:
>> > > >
>> > > > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
>> > > > What I got from Jewel FormItem: https://snag.gy/Slfbt9.jpg
>> > > >
>> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <ca...@apache.org>
>> > > > napisał(a):
>> > > >
>> > > > > Piotr,
>> > > > >
>> > > > > remember that images pasted in list are not shared, you must share
>> > with
>> > > > > some image service
>> > > > >
>> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
>> > > > > piotrzarzycki21@gmail.com>) escribió:
>> > > > >
>> > > > > > There is one more problem with Layout. Currently default in
>> > framework
>> > > > we
>> > > > > > have [1]. It means that:
>> > > > > >
>> > > > > > My content of FormItem will be vertical and IBeadLayout is
>> > basically
>> > > > > > ignored at some point. If I specify beads - HorizontalLayout as
>> it
>> > is
>> > > > in
>> > > > > > above example it will be taken as a primary and I have my
>> content
>> > > > laying
>> > > > > > out horizontally. The question is - what is for
>> IFormItemLayout in
>> > > > > > default.css? Is it a bug?
>> > > > > >
>> > > > > > [1] https://paste.apache.org/rV0K
>> > > > > >
>> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
>> piotrzarzycki21@gmail.com
>> > >
>> > > > > > napisał(a):
>> > > > > >
>> > > > > >> Hi Carlos,
>> > > > > >>
>> > > > > >> I'm was trying to change FormItem to be Vertical oriented. In
>> > > general
>> > > > I
>> > > > > >> would like to have following view. Label of FormItem is on the
>> top
>> > > and
>> > > > > in
>> > > > > >> the bottom is content.
>> > > > > >>
>> > > > > >> [image: image.png]
>> > > > > >>
>> > > > > >> Code for that will looks like that [1]. Results is following:
>> > > > > >>
>> > > > > >> [image: image.png]
>> > > > > >>
>> > > > > >> It happened cause Label and required star label are different
>> > > > components
>> > > > > >> - everything is being laying out vertically. What is your
>> > suggestion
>> > > > to
>> > > > > fix
>> > > > > >> that ?
>> > > > > >>
>> > > > > >> Mine is wrapping "First name" and "*" into one Group with
>> > > > > >> HorizontalLayout.
>> > > > > >>
>> > > > > >> More thoughts are welcome. I hope you see screenshots. :)
>> > > > > >>
>> > > > > >> [1] https://paste.apache.org/5odt
>> > > > > >>
>> > > > > >> Thanks,
>> > > > > >> --
>> > > > > >>
>> > > > > >> Piotr Zarzycki
>> > > > > >>
>> > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
>> > > > > >> <https://www.patreon.com/piotrzarzycki>*
>> > > > > >>
>> > > > > >
>> > > > > >
>> > > > > > --
>> > > > > >
>> > > > > > Piotr Zarzycki
>> > > > > >
>> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
>> > > > > > <https://www.patreon.com/piotrzarzycki>*
>> > > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Carlos Rovira
>> > > > > http://about.me/carlosrovira
>> > > > >
>> > > >
>> > > >
>> > > > --
>> > > >
>> > > > Piotr Zarzycki
>> > > >
>> > > > Patreon: *https://www.patreon.com/piotrzarzycki
>> > > > <https://www.patreon.com/piotrzarzycki>*
>> > > >
>> > >
>> > >
>> > > --
>> > > Carlos Rovira
>> > > http://about.me/carlosrovira
>> > >
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: *https://www.patreon.com/piotrzarzycki
>> > <https://www.patreon.com/piotrzarzycki>*
>> >
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

That's more clear to me. I will check and get back to you.

Thank you!


śr., 23 sty 2019 o 18:03 Carlos Rovira <ca...@apache.org> napisał(a):

> No,
>
> I was asking you about how flex solves visualy the problem in their stacked
> version. The required icon is setup next to the label? is in other place?
> if we had an image of how it is designed (and like it), we can copy it. I
> still not proposing a technical solution. Just that I don't have clear how
> we should layout it
>
> El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > Carlos,
> >
> > Your suggestion is to have new form item (StackedFormItem) with new
> > StackedFormItemView - cause problem is inside FormitemView, not inside
> > layout itself. Current layout is doing what it should do - apart of the
> > problem - it's making children to be Horizontal/Vertical.
> >
> > If I'm correct what you are saying - that's ok, but if you have had
> > different idea by saying above let me know.
> >
> > Thanks, Piotr
> >
> > śr., 23 sty 2019 o 17:14 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> > > Ok, I understand now.
> > >
> > > In Flex I think we had that layout and was called....StackedFormItem or
> > > something like that?
> > > Could you check how Flex solve this? If we continue liking the way
> > stacked
> > > form layout in flex looks, we can do the same for our Royale version
> > >
> > >
> > > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
> > > piotrzarzycki21@gmail.com>) escribió:
> > >
> > > > I'm not sure how Serkan is doing that on users forum, but I see all
> > hist
> > > > pasted images. Anyway here you go:
> > > >
> > > > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
> > > > What I got from Jewel FormItem: https://snag.gy/Slfbt9.jpg
> > > >
> > > > śr., 23 sty 2019 o 16:28 Carlos Rovira <ca...@apache.org>
> > > > napisał(a):
> > > >
> > > > > Piotr,
> > > > >
> > > > > remember that images pasted in list are not shared, you must share
> > with
> > > > > some image service
> > > > >
> > > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > >
> > > > > > There is one more problem with Layout. Currently default in
> > framework
> > > > we
> > > > > > have [1]. It means that:
> > > > > >
> > > > > > My content of FormItem will be vertical and IBeadLayout is
> > basically
> > > > > > ignored at some point. If I specify beads - HorizontalLayout as
> it
> > is
> > > > in
> > > > > > above example it will be taken as a primary and I have my content
> > > > laying
> > > > > > out horizontally. The question is - what is for  IFormItemLayout
> in
> > > > > > default.css? Is it a bug?
> > > > > >
> > > > > > [1] https://paste.apache.org/rV0K
> > > > > >
> > > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <
> piotrzarzycki21@gmail.com
> > >
> > > > > > napisał(a):
> > > > > >
> > > > > >> Hi Carlos,
> > > > > >>
> > > > > >> I'm was trying to change FormItem to be Vertical oriented. In
> > > general
> > > > I
> > > > > >> would like to have following view. Label of FormItem is on the
> top
> > > and
> > > > > in
> > > > > >> the bottom is content.
> > > > > >>
> > > > > >> [image: image.png]
> > > > > >>
> > > > > >> Code for that will looks like that [1]. Results is following:
> > > > > >>
> > > > > >> [image: image.png]
> > > > > >>
> > > > > >> It happened cause Label and required star label are different
> > > > components
> > > > > >> - everything is being laying out vertically. What is your
> > suggestion
> > > > to
> > > > > fix
> > > > > >> that ?
> > > > > >>
> > > > > >> Mine is wrapping "First name" and "*" into one Group with
> > > > > >> HorizontalLayout.
> > > > > >>
> > > > > >> More thoughts are welcome. I hope you see screenshots. :)
> > > > > >>
> > > > > >> [1] https://paste.apache.org/5odt
> > > > > >>
> > > > > >> Thanks,
> > > > > >> --
> > > > > >>
> > > > > >> Piotr Zarzycki
> > > > > >>
> > > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > > >>
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Piotr Zarzycki
> > > > > >
> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > <https://www.patreon.com/piotrzarzycki>*
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Carlos Rovira <ca...@apache.org>.

No,

I was asking you about how flex solves visualy the problem in their stacked
version. The required icon is setup next to the label? is in other place?
if we had an image of how it is designed (and like it), we can copy it. I
still not proposing a technical solution. Just that I don't have clear how
we should layout it

El mié., 23 ene. 2019 a las 17:29, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> Carlos,
>
> Your suggestion is to have new form item (StackedFormItem) with new
> StackedFormItemView - cause problem is inside FormitemView, not inside
> layout itself. Current layout is doing what it should do - apart of the
> problem - it's making children to be Horizontal/Vertical.
>
> If I'm correct what you are saying - that's ok, but if you have had
> different idea by saying above let me know.
>
> Thanks, Piotr
>
> śr., 23 sty 2019 o 17:14 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Ok, I understand now.
> >
> > In Flex I think we had that layout and was called....StackedFormItem or
> > something like that?
> > Could you check how Flex solve this? If we continue liking the way
> stacked
> > form layout in flex looks, we can do the same for our Royale version
> >
> >
> > El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> > > I'm not sure how Serkan is doing that on users forum, but I see all
> hist
> > > pasted images. Anyway here you go:
> > >
> > > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
> > > What I got from Jewel FormItem: https://snag.gy/Slfbt9.jpg
> > >
> > > śr., 23 sty 2019 o 16:28 Carlos Rovira <ca...@apache.org>
> > > napisał(a):
> > >
> > > > Piotr,
> > > >
> > > > remember that images pasted in list are not shared, you must share
> with
> > > > some image service
> > > >
> > > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
> > > > piotrzarzycki21@gmail.com>) escribió:
> > > >
> > > > > There is one more problem with Layout. Currently default in
> framework
> > > we
> > > > > have [1]. It means that:
> > > > >
> > > > > My content of FormItem will be vertical and IBeadLayout is
> basically
> > > > > ignored at some point. If I specify beads - HorizontalLayout as it
> is
> > > in
> > > > > above example it will be taken as a primary and I have my content
> > > laying
> > > > > out horizontally. The question is - what is for  IFormItemLayout in
> > > > > default.css? Is it a bug?
> > > > >
> > > > > [1] https://paste.apache.org/rV0K
> > > > >
> > > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <piotrzarzycki21@gmail.com
> >
> > > > > napisał(a):
> > > > >
> > > > >> Hi Carlos,
> > > > >>
> > > > >> I'm was trying to change FormItem to be Vertical oriented. In
> > general
> > > I
> > > > >> would like to have following view. Label of FormItem is on the top
> > and
> > > > in
> > > > >> the bottom is content.
> > > > >>
> > > > >> [image: image.png]
> > > > >>
> > > > >> Code for that will looks like that [1]. Results is following:
> > > > >>
> > > > >> [image: image.png]
> > > > >>
> > > > >> It happened cause Label and required star label are different
> > > components
> > > > >> - everything is being laying out vertically. What is your
> suggestion
> > > to
> > > > fix
> > > > >> that ?
> > > > >>
> > > > >> Mine is wrapping "First name" and "*" into one Group with
> > > > >> HorizontalLayout.
> > > > >>
> > > > >> More thoughts are welcome. I hope you see screenshots. :)
> > > > >>
> > > > >> [1] https://paste.apache.org/5odt
> > > > >>
> > > > >> Thanks,
> > > > >> --
> > > > >>
> > > > >> Piotr Zarzycki
> > > > >>
> > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Piotr Zarzycki
> > > > >
> > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > >
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

Carlos,

Your suggestion is to have new form item (StackedFormItem) with new
StackedFormItemView - cause problem is inside FormitemView, not inside
layout itself. Current layout is doing what it should do - apart of the
problem - it's making children to be Horizontal/Vertical.

If I'm correct what you are saying - that's ok, but if you have had
different idea by saying above let me know.

Thanks, Piotr

śr., 23 sty 2019 o 17:14 Carlos Rovira <ca...@apache.org> napisał(a):

> Ok, I understand now.
>
> In Flex I think we had that layout and was called....StackedFormItem or
> something like that?
> Could you check how Flex solve this? If we continue liking the way stacked
> form layout in flex looks, we can do the same for our Royale version
>
>
> El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > I'm not sure how Serkan is doing that on users forum, but I see all hist
> > pasted images. Anyway here you go:
> >
> > What I wanted to achieve: https://snag.gy/DmH7yk.jpg
> > What I got from Jewel FormItem: https://snag.gy/Slfbt9.jpg
> >
> > śr., 23 sty 2019 o 16:28 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> > > Piotr,
> > >
> > > remember that images pasted in list are not shared, you must share with
> > > some image service
> > >
> > > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
> > > piotrzarzycki21@gmail.com>) escribió:
> > >
> > > > There is one more problem with Layout. Currently default in framework
> > we
> > > > have [1]. It means that:
> > > >
> > > > My content of FormItem will be vertical and IBeadLayout is basically
> > > > ignored at some point. If I specify beads - HorizontalLayout as it is
> > in
> > > > above example it will be taken as a primary and I have my content
> > laying
> > > > out horizontally. The question is - what is for  IFormItemLayout in
> > > > default.css? Is it a bug?
> > > >
> > > > [1] https://paste.apache.org/rV0K
> > > >
> > > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <pi...@gmail.com>
> > > > napisał(a):
> > > >
> > > >> Hi Carlos,
> > > >>
> > > >> I'm was trying to change FormItem to be Vertical oriented. In
> general
> > I
> > > >> would like to have following view. Label of FormItem is on the top
> and
> > > in
> > > >> the bottom is content.
> > > >>
> > > >> [image: image.png]
> > > >>
> > > >> Code for that will looks like that [1]. Results is following:
> > > >>
> > > >> [image: image.png]
> > > >>
> > > >> It happened cause Label and required star label are different
> > components
> > > >> - everything is being laying out vertically. What is your suggestion
> > to
> > > fix
> > > >> that ?
> > > >>
> > > >> Mine is wrapping "First name" and "*" into one Group with
> > > >> HorizontalLayout.
> > > >>
> > > >> More thoughts are welcome. I hope you see screenshots. :)
> > > >>
> > > >> [1] https://paste.apache.org/5odt
> > > >>
> > > >> Thanks,
> > > >> --
> > > >>
> > > >> Piotr Zarzycki
> > > >>
> > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > >> <https://www.patreon.com/piotrzarzycki>*
> > > >>
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > <https://www.patreon.com/piotrzarzycki>*
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Carlos Rovira <ca...@apache.org>.

Ok, I understand now.

In Flex I think we had that layout and was called....StackedFormItem or
something like that?
Could you check how Flex solve this? If we continue liking the way stacked
form layout in flex looks, we can do the same for our Royale version


El mié., 23 ene. 2019 a las 16:38, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> I'm not sure how Serkan is doing that on users forum, but I see all hist
> pasted images. Anyway here you go:
>
> What I wanted to achieve: https://snag.gy/DmH7yk.jpg
> What I got from Jewel FormItem: https://snag.gy/Slfbt9.jpg
>
> śr., 23 sty 2019 o 16:28 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Piotr,
> >
> > remember that images pasted in list are not shared, you must share with
> > some image service
> >
> > El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> > > There is one more problem with Layout. Currently default in framework
> we
> > > have [1]. It means that:
> > >
> > > My content of FormItem will be vertical and IBeadLayout is basically
> > > ignored at some point. If I specify beads - HorizontalLayout as it is
> in
> > > above example it will be taken as a primary and I have my content
> laying
> > > out horizontally. The question is - what is for  IFormItemLayout in
> > > default.css? Is it a bug?
> > >
> > > [1] https://paste.apache.org/rV0K
> > >
> > > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <pi...@gmail.com>
> > > napisał(a):
> > >
> > >> Hi Carlos,
> > >>
> > >> I'm was trying to change FormItem to be Vertical oriented. In general
> I
> > >> would like to have following view. Label of FormItem is on the top and
> > in
> > >> the bottom is content.
> > >>
> > >> [image: image.png]
> > >>
> > >> Code for that will looks like that [1]. Results is following:
> > >>
> > >> [image: image.png]
> > >>
> > >> It happened cause Label and required star label are different
> components
> > >> - everything is being laying out vertically. What is your suggestion
> to
> > fix
> > >> that ?
> > >>
> > >> Mine is wrapping "First name" and "*" into one Group with
> > >> HorizontalLayout.
> > >>
> > >> More thoughts are welcome. I hope you see screenshots. :)
> > >>
> > >> [1] https://paste.apache.org/5odt
> > >>
> > >> Thanks,
> > >> --
> > >>
> > >> Piotr Zarzycki
> > >>
> > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > >> <https://www.patreon.com/piotrzarzycki>*
> > >>
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

I'm not sure how Serkan is doing that on users forum, but I see all hist
pasted images. Anyway here you go:

What I wanted to achieve: https://snag.gy/DmH7yk.jpg
What I got from Jewel FormItem: https://snag.gy/Slfbt9.jpg

śr., 23 sty 2019 o 16:28 Carlos Rovira <ca...@apache.org> napisał(a):

> Piotr,
>
> remember that images pasted in list are not shared, you must share with
> some image service
>
> El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > There is one more problem with Layout. Currently default in framework we
> > have [1]. It means that:
> >
> > My content of FormItem will be vertical and IBeadLayout is basically
> > ignored at some point. If I specify beads - HorizontalLayout as it is in
> > above example it will be taken as a primary and I have my content laying
> > out horizontally. The question is - what is for  IFormItemLayout in
> > default.css? Is it a bug?
> >
> > [1] https://paste.apache.org/rV0K
> >
> > śr., 23 sty 2019 o 15:46 Piotr Zarzycki <pi...@gmail.com>
> > napisał(a):
> >
> >> Hi Carlos,
> >>
> >> I'm was trying to change FormItem to be Vertical oriented. In general I
> >> would like to have following view. Label of FormItem is on the top and
> in
> >> the bottom is content.
> >>
> >> [image: image.png]
> >>
> >> Code for that will looks like that [1]. Results is following:
> >>
> >> [image: image.png]
> >>
> >> It happened cause Label and required star label are different components
> >> - everything is being laying out vertically. What is your suggestion to
> fix
> >> that ?
> >>
> >> Mine is wrapping "First name" and "*" into one Group with
> >> HorizontalLayout.
> >>
> >> More thoughts are welcome. I hope you see screenshots. :)
> >>
> >> [1] https://paste.apache.org/5odt
> >>
> >> Thanks,
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> <https://www.patreon.com/piotrzarzycki>*
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Vertical FormItem

Posted by Carlos Rovira <ca...@apache.org>.

Piotr,

remember that images pasted in list are not shared, you must share with
some image service

El mié., 23 ene. 2019 a las 16:14, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> There is one more problem with Layout. Currently default in framework we
> have [1]. It means that:
>
> My content of FormItem will be vertical and IBeadLayout is basically
> ignored at some point. If I specify beads - HorizontalLayout as it is in
> above example it will be taken as a primary and I have my content laying
> out horizontally. The question is - what is for  IFormItemLayout in
> default.css? Is it a bug?
>
> [1] https://paste.apache.org/rV0K
>
> śr., 23 sty 2019 o 15:46 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
>> Hi Carlos,
>>
>> I'm was trying to change FormItem to be Vertical oriented. In general I
>> would like to have following view. Label of FormItem is on the top and in
>> the bottom is content.
>>
>> [image: image.png]
>>
>> Code for that will looks like that [1]. Results is following:
>>
>> [image: image.png]
>>
>> It happened cause Label and required star label are different components
>> - everything is being laying out vertically. What is your suggestion to fix
>> that ?
>>
>> Mine is wrapping "First name" and "*" into one Group with
>> HorizontalLayout.
>>
>> More thoughts are welcome. I hope you see screenshots. :)
>>
>> [1] https://paste.apache.org/5odt
>>
>> Thanks,
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

Re: Vertical FormItem

Posted by Piotr Zarzycki <pi...@gmail.com>.

There is one more problem with Layout. Currently default in framework we
have [1]. It means that:

My content of FormItem will be vertical and IBeadLayout is basically
ignored at some point. If I specify beads - HorizontalLayout as it is in
above example it will be taken as a primary and I have my content laying
out horizontally. The question is - what is for  IFormItemLayout in
default.css? Is it a bug?

[1] https://paste.apache.org/rV0K

śr., 23 sty 2019 o 15:46 Piotr Zarzycki <pi...@gmail.com>
napisał(a):

> Hi Carlos,
>
> I'm was trying to change FormItem to be Vertical oriented. In general I
> would like to have following view. Label of FormItem is on the top and in
> the bottom is content.
>
> [image: image.png]
>
> Code for that will looks like that [1]. Results is following:
>
> [image: image.png]
>
> It happened cause Label and required star label are different components -
> everything is being laying out vertically. What is your suggestion to fix
> that ?
>
> Mine is wrapping "First name" and "*" into one Group with HorizontalLayout.
>
> More thoughts are welcome. I hope you see screenshots. :)
>
> [1] https://paste.apache.org/5odt
>
> Thanks,
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*