You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Harbs <ha...@gmail.com> on 2019/01/15 08:21:16 UTC
Issue with Jewel popup
https://royale.apache.org/tourdejewel/#
Click on Popup and click the non-modal one.
Type something into the fields and you’ll see that the validation text gets cut off to the boundaries of the section div on the main page. The validation div also remains after closing the popup.
Is there a reason Jewel popups are not added to the body?
Thanks,
Harbs
Re: Issue with Jewel popup
Posted by Carlos Rovira <ca...@apache.org>.
Thanks Harbs,
let me know if you need some help from my side
El mar., 15 ene. 2019 a las 20:05, Harbs (<ha...@gmail.com>) escribió:
> I’ll try to find some time to work on these.
>
> > On Jan 15, 2019, at 8:19 PM, Carlos Rovira <ca...@apache.org>
> wrote:
> >
> > Hi
> >
> > El mar., 15 ene. 2019 a las 18:35, Harbs (<ha...@gmail.com>)
> escribió:
> >
> >> 1. Try typing into the date field. The date separators get all weird,
> and
> >> you can’t delete text.
> >>
> >
> > Right, That's something to fix. Didn't have the time to solve it, so if
> you
> > have some idea feel free to improve it. I think you have more experience
> > with text algorithms.
> >
> >
> >> 2. The validation only happens after the date field loses focus. That
> >> causes the error tip to remain.
> >>
> >
> > In Jewel Validators we have "triggerEvent" and I think is set to CHANGE.
> > But In our Real App we use most of the time a basic bead for FOCUS_OUT.
> > So, again, if you see improvements here to do feel free to do it.
> >
> > thanks!
> >
> >
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >>
> >>
> >>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Issue with Jewel popup
Posted by Harbs <ha...@gmail.com>.
I’ll try to find some time to work on these.
> On Jan 15, 2019, at 8:19 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> Hi
>
> El mar., 15 ene. 2019 a las 18:35, Harbs (<ha...@gmail.com>) escribió:
>
>> 1. Try typing into the date field. The date separators get all weird, and
>> you can’t delete text.
>>
>
> Right, That's something to fix. Didn't have the time to solve it, so if you
> have some idea feel free to improve it. I think you have more experience
> with text algorithms.
>
>
>> 2. The validation only happens after the date field loses focus. That
>> causes the error tip to remain.
>>
>
> In Jewel Validators we have "triggerEvent" and I think is set to CHANGE.
> But In our Real App we use most of the time a basic bead for FOCUS_OUT.
> So, again, if you see improvements here to do feel free to do it.
>
> thanks!
>
>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>>
>>
Re: Issue with Jewel popup
Posted by Carlos Rovira <ca...@apache.org>.
Hi
El mar., 15 ene. 2019 a las 18:35, Harbs (<ha...@gmail.com>) escribió:
> 1. Try typing into the date field. The date separators get all weird, and
> you can’t delete text.
>
Right, That's something to fix. Didn't have the time to solve it, so if you
have some idea feel free to improve it. I think you have more experience
with text algorithms.
> 2. The validation only happens after the date field loses focus. That
> causes the error tip to remain.
>
In Jewel Validators we have "triggerEvent" and I think is set to CHANGE.
But In our Real App we use most of the time a basic bead for FOCUS_OUT.
So, again, if you see improvements here to do feel free to do it.
thanks!
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
>
>
Re: Issue with Jewel popup
Posted by Harbs <ha...@gmail.com>.
1. Try typing into the date field. The date separators get all weird, and you can’t delete text.
2. The validation only happens after the date field loses focus. That causes the error tip to remain.
> On Jan 15, 2019, at 7:24 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> Hi Harbs,
>
> just tested now in Tour De Jewel and now works perfect. Thanks for fixing
> this! :)
>
> What do you mean with "DateValidator still needs work."? What you miss
> there?
>
>
>
> El mar., 15 ene. 2019 a las 16:50, Harbs (<ha...@gmail.com>) escribió:
>
>> I changed popup and validator.
>>
>> The validator behavior is a bit different, but I think it’s better.
>>
>> DateValidator still needs work.
>>
>> Let me know what you think.
>>
>> Harbs
>>
>>> On Jan 15, 2019, at 5:19 PM, Harbs <ha...@gmail.com> wrote:
>>>
>>> I don’t think Popup should implement IPopupHost and IPopupHostParent.
>>>
>>> Also: Tips including ErrorTips should self-remove as soon as the
>> component which launches them loses focus.
>>>
>>>> On Jan 15, 2019, at 2:06 PM, Carlos Rovira <ca...@apache.org>
>> wrote:
>>>>
>>>> Hi Harbs
>>>>
>>>> I saw this the other day. Thanks for reporting.
>>>>
>>>> The problem is that PopUp uses
>>>>
>>>> UIUtils.addPopUp(_popUp, getHost());
>>>> (that does a call to findPopUpHost)
>>>>
>>>> And the ToolTips uses this too.
>>>>
>>>> In the other hand Alex did some changes and now we have
>>>>
>>>> IPopUpHost
>>>>
>>>> and
>>>>
>>>> IPopUpHostParent
>>>>
>>>> And I think Jewel and maybe Basic too is not having into account this
>> kind
>>>> of cases where a something popups other things and the latest popup
>> another.
>>>>
>>>> I think this is a good place to solve this. So could you help with this
>>>> issue and try to fix it? Since you already has experience with popups
>> hope
>>>> you could bring a proper solution to this.
>>>> I already tried with no luck.
>>>>
>>>> About adding to the body...is not a problem, if we need to add there, I
>>>> think is ok. So if the change implies that I think we could do it.
>>>>
>>>> Maybe we could have some issues with CSS rules of that components, but
>> I'm
>>>> sure I can help in that part.
>>>>
>>>> Let me know if you can
>>>>
>>>> thanks
>>>>
>>>> Carlos
>>>>
>>>>
>>>>
>>>> El mar., 15 ene. 2019 a las 9:21, Harbs (<ha...@gmail.com>)
>> escribió:
>>>>
>>>>> https://royale.apache.org/tourdejewel/#
>>>>>
>>>>> Click on Popup and click the non-modal one.
>>>>>
>>>>> Type something into the fields and you’ll see that the validation text
>>>>> gets cut off to the boundaries of the section div on the main page. The
>>>>> validation div also remains after closing the popup.
>>>>>
>>>>> Is there a reason Jewel popups are not added to the body?
>>>>>
>>>>> Thanks,
>>>>> Harbs
>>>>
>>>>
>>>>
>>>> --
>>>> Carlos Rovira
>>>> http://about.me/carlosrovira
>>>
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
Re: Issue with Jewel popup
Posted by Carlos Rovira <ca...@apache.org>.
Hi Harbs,
just tested now in Tour De Jewel and now works perfect. Thanks for fixing
this! :)
What do you mean with "DateValidator still needs work."? What you miss
there?
El mar., 15 ene. 2019 a las 16:50, Harbs (<ha...@gmail.com>) escribió:
> I changed popup and validator.
>
> The validator behavior is a bit different, but I think it’s better.
>
> DateValidator still needs work.
>
> Let me know what you think.
>
> Harbs
>
> > On Jan 15, 2019, at 5:19 PM, Harbs <ha...@gmail.com> wrote:
> >
> > I don’t think Popup should implement IPopupHost and IPopupHostParent.
> >
> > Also: Tips including ErrorTips should self-remove as soon as the
> component which launches them loses focus.
> >
> >> On Jan 15, 2019, at 2:06 PM, Carlos Rovira <ca...@apache.org>
> wrote:
> >>
> >> Hi Harbs
> >>
> >> I saw this the other day. Thanks for reporting.
> >>
> >> The problem is that PopUp uses
> >>
> >> UIUtils.addPopUp(_popUp, getHost());
> >> (that does a call to findPopUpHost)
> >>
> >> And the ToolTips uses this too.
> >>
> >> In the other hand Alex did some changes and now we have
> >>
> >> IPopUpHost
> >>
> >> and
> >>
> >> IPopUpHostParent
> >>
> >> And I think Jewel and maybe Basic too is not having into account this
> kind
> >> of cases where a something popups other things and the latest popup
> another.
> >>
> >> I think this is a good place to solve this. So could you help with this
> >> issue and try to fix it? Since you already has experience with popups
> hope
> >> you could bring a proper solution to this.
> >> I already tried with no luck.
> >>
> >> About adding to the body...is not a problem, if we need to add there, I
> >> think is ok. So if the change implies that I think we could do it.
> >>
> >> Maybe we could have some issues with CSS rules of that components, but
> I'm
> >> sure I can help in that part.
> >>
> >> Let me know if you can
> >>
> >> thanks
> >>
> >> Carlos
> >>
> >>
> >>
> >> El mar., 15 ene. 2019 a las 9:21, Harbs (<ha...@gmail.com>)
> escribió:
> >>
> >>> https://royale.apache.org/tourdejewel/#
> >>>
> >>> Click on Popup and click the non-modal one.
> >>>
> >>> Type something into the fields and you’ll see that the validation text
> >>> gets cut off to the boundaries of the section div on the main page. The
> >>> validation div also remains after closing the popup.
> >>>
> >>> Is there a reason Jewel popups are not added to the body?
> >>>
> >>> Thanks,
> >>> Harbs
> >>
> >>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Issue with Jewel popup
Posted by Harbs <ha...@gmail.com>.
I changed popup and validator.
The validator behavior is a bit different, but I think it’s better.
DateValidator still needs work.
Let me know what you think.
Harbs
> On Jan 15, 2019, at 5:19 PM, Harbs <ha...@gmail.com> wrote:
>
> I don’t think Popup should implement IPopupHost and IPopupHostParent.
>
> Also: Tips including ErrorTips should self-remove as soon as the component which launches them loses focus.
>
>> On Jan 15, 2019, at 2:06 PM, Carlos Rovira <ca...@apache.org> wrote:
>>
>> Hi Harbs
>>
>> I saw this the other day. Thanks for reporting.
>>
>> The problem is that PopUp uses
>>
>> UIUtils.addPopUp(_popUp, getHost());
>> (that does a call to findPopUpHost)
>>
>> And the ToolTips uses this too.
>>
>> In the other hand Alex did some changes and now we have
>>
>> IPopUpHost
>>
>> and
>>
>> IPopUpHostParent
>>
>> And I think Jewel and maybe Basic too is not having into account this kind
>> of cases where a something popups other things and the latest popup another.
>>
>> I think this is a good place to solve this. So could you help with this
>> issue and try to fix it? Since you already has experience with popups hope
>> you could bring a proper solution to this.
>> I already tried with no luck.
>>
>> About adding to the body...is not a problem, if we need to add there, I
>> think is ok. So if the change implies that I think we could do it.
>>
>> Maybe we could have some issues with CSS rules of that components, but I'm
>> sure I can help in that part.
>>
>> Let me know if you can
>>
>> thanks
>>
>> Carlos
>>
>>
>>
>> El mar., 15 ene. 2019 a las 9:21, Harbs (<ha...@gmail.com>) escribió:
>>
>>> https://royale.apache.org/tourdejewel/#
>>>
>>> Click on Popup and click the non-modal one.
>>>
>>> Type something into the fields and you’ll see that the validation text
>>> gets cut off to the boundaries of the section div on the main page. The
>>> validation div also remains after closing the popup.
>>>
>>> Is there a reason Jewel popups are not added to the body?
>>>
>>> Thanks,
>>> Harbs
>>
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>
Re: Issue with Jewel popup
Posted by Harbs <ha...@gmail.com>.
I don’t think Popup should implement IPopupHost and IPopupHostParent.
Also: Tips including ErrorTips should self-remove as soon as the component which launches them loses focus.
> On Jan 15, 2019, at 2:06 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> Hi Harbs
>
> I saw this the other day. Thanks for reporting.
>
> The problem is that PopUp uses
>
> UIUtils.addPopUp(_popUp, getHost());
> (that does a call to findPopUpHost)
>
> And the ToolTips uses this too.
>
> In the other hand Alex did some changes and now we have
>
> IPopUpHost
>
> and
>
> IPopUpHostParent
>
> And I think Jewel and maybe Basic too is not having into account this kind
> of cases where a something popups other things and the latest popup another.
>
> I think this is a good place to solve this. So could you help with this
> issue and try to fix it? Since you already has experience with popups hope
> you could bring a proper solution to this.
> I already tried with no luck.
>
> About adding to the body...is not a problem, if we need to add there, I
> think is ok. So if the change implies that I think we could do it.
>
> Maybe we could have some issues with CSS rules of that components, but I'm
> sure I can help in that part.
>
> Let me know if you can
>
> thanks
>
> Carlos
>
>
>
> El mar., 15 ene. 2019 a las 9:21, Harbs (<ha...@gmail.com>) escribió:
>
>> https://royale.apache.org/tourdejewel/#
>>
>> Click on Popup and click the non-modal one.
>>
>> Type something into the fields and you’ll see that the validation text
>> gets cut off to the boundaries of the section div on the main page. The
>> validation div also remains after closing the popup.
>>
>> Is there a reason Jewel popups are not added to the body?
>>
>> Thanks,
>> Harbs
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
Re: Issue with Jewel popup
Posted by Alex Harui <ah...@adobe.com.INVALID>.
IMO, MDI is a specific implementation of an "overlapping windows" implementation. In some scenarios (like AIR apps) the true MDI windows (equivalent to other top-level windows of other apps) was the AIR NativeWindow itself and no ActionScript code managed how those MDI windows behaved.
But even if you try to simulate MDI within a browser window, each MDI window might itself have a stack of popups and z-order and focus/activation have to be managed within that window. So there are lots of possible PAYG implementations, IMO. It shouldn't take much code to just handle someone's "Find" dialog, but it was a fair amount of code to do what Flex did and divide SystemManager into normal, popup, tooltip, and cursor layers.
This will probably be DAYG (Do As You Go). We'll figure out some implementation when someone actually needs it.
My 2 cents,
-Alex
On 1/16/19, 12:44 AM, "Carlos Rovira" <ca...@apache.org> wrote:
Ok,
I always refer to that concept as MDII (Multiple Document Interface). And
in Flex we had external MDI library to do that. For me that's a concrete
case and people that wants to do MDI should start that effort and make a
new library. So IMO we should start to that need to invest time in this.
Regarding zindexes, in Jewel I put things on some concrete index but I as
well thinked that I should define a range, but still didn't. For now seems
not urgent, but I remember in Flex at some point was needed (and was in
that MDI app we did).
El mié., 16 ene. 2019 a las 8:54, Harbs (<ha...@gmail.com>) escribió:
> Sure.
>
> All I was saying with the z-indexes is that it makes sense to stick to
> some conventions when implementing different beads/managers so they play
> nicely with each other.
>
> > On Jan 16, 2019, at 8:41 AM, Alex Harui <ah...@adobe.com.INVALID>
> wrote:
> >
> > Royale offers choices. For PAYG reasons we probably wouldn't want to
> implement only the "ultimate floating window manager". There are different
> strategies as to what goes on top and when (on mouseDown or mouseUp).
> Modal dialogs can have popups and float stuff over them if they want.
> >
> > My 2 cents,
> > -Alex
> >
> > On 1/15/19, 10:13 PM, "Harbs" <ha...@gmail.com> wrote:
> >
> > Floating windows could probably be handled pretty easily by changing
> the z-index on each of the popups (in HTML).
> >
> > Of course you’d need a manager to handle that, but it shouldn’t be
> too hard to implement.
> >
> > That would probably be either a FloatingWindowManager singleton or
> FloatingWindowUtils static class.
> >
> > We probably want to standardize on different number ranges of z-index
> for different “classes” of floating things.
> >
> > I imagine modal dialogs would have the highest z-index. The possible
> exception to that would be popup menus. Floating windows somewhat lower
> than modal dialogs, etc.
> >
> >> On Jan 16, 2019, at 2:39 AM, Alex Harui <ah...@adobe.com.INVALID>
> wrote:
> >>
> >>
> >>
> >> On 1/15/19, 2:48 PM, "Carlos Rovira" <ca...@apache.org> wrote:
> >>
> >>>
> >>> Support for "overlapping windows" would be PAYG and added via some
> other
> >>> classes. I don't think we've done anything there at the Basic level,
> the
> >>> emulation components may have to support it since Flex did.
> >>>
> >>
> >> What do you mean with "overlapping windows". Don't understand that
> concept.
> >> For me windows are always one on top of another...
> >>
> >> Oh yeah, forgot to describe that. "overlapping windows" means that two
> or more popups can be visible and potentially overlap each other based on
> which one was clicked on last. In some IDEs you can have all of these
> floating panels. Spell-check and Find dialogs are other examples where
> they can be popped up and not dismissed while some other popup or dropdown
> shows up and has to show up above or under the floating Spell-Check or Find
> dialog.
> >>
> >> Flex had a whole ActiveWindowManager that worked with the
> PopUpManager. Royale should try to make support for floating dialogs PAYG.
> >>
> >> Thanks,
> >> -Alex
> >>
> >
> >
> >
>
>
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C89b73a6569614a4cfa5608d67b8ec6bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636832250487144183&sdata=SqCecW%2B%2FI9WzjTOMQQxuWZCn1T0TzkwXORYYCbtHiaA%3D&reserved=0
Re: Issue with Jewel popup
Posted by Carlos Rovira <ca...@apache.org>.
Ok,
I always refer to that concept as MDII (Multiple Document Interface). And
in Flex we had external MDI library to do that. For me that's a concrete
case and people that wants to do MDI should start that effort and make a
new library. So IMO we should start to that need to invest time in this.
Regarding zindexes, in Jewel I put things on some concrete index but I as
well thinked that I should define a range, but still didn't. For now seems
not urgent, but I remember in Flex at some point was needed (and was in
that MDI app we did).
El mié., 16 ene. 2019 a las 8:54, Harbs (<ha...@gmail.com>) escribió:
> Sure.
>
> All I was saying with the z-indexes is that it makes sense to stick to
> some conventions when implementing different beads/managers so they play
> nicely with each other.
>
> > On Jan 16, 2019, at 8:41 AM, Alex Harui <ah...@adobe.com.INVALID>
> wrote:
> >
> > Royale offers choices. For PAYG reasons we probably wouldn't want to
> implement only the "ultimate floating window manager". There are different
> strategies as to what goes on top and when (on mouseDown or mouseUp).
> Modal dialogs can have popups and float stuff over them if they want.
> >
> > My 2 cents,
> > -Alex
> >
> > On 1/15/19, 10:13 PM, "Harbs" <ha...@gmail.com> wrote:
> >
> > Floating windows could probably be handled pretty easily by changing
> the z-index on each of the popups (in HTML).
> >
> > Of course you’d need a manager to handle that, but it shouldn’t be
> too hard to implement.
> >
> > That would probably be either a FloatingWindowManager singleton or
> FloatingWindowUtils static class.
> >
> > We probably want to standardize on different number ranges of z-index
> for different “classes” of floating things.
> >
> > I imagine modal dialogs would have the highest z-index. The possible
> exception to that would be popup menus. Floating windows somewhat lower
> than modal dialogs, etc.
> >
> >> On Jan 16, 2019, at 2:39 AM, Alex Harui <ah...@adobe.com.INVALID>
> wrote:
> >>
> >>
> >>
> >> On 1/15/19, 2:48 PM, "Carlos Rovira" <ca...@apache.org> wrote:
> >>
> >>>
> >>> Support for "overlapping windows" would be PAYG and added via some
> other
> >>> classes. I don't think we've done anything there at the Basic level,
> the
> >>> emulation components may have to support it since Flex did.
> >>>
> >>
> >> What do you mean with "overlapping windows". Don't understand that
> concept.
> >> For me windows are always one on top of another...
> >>
> >> Oh yeah, forgot to describe that. "overlapping windows" means that two
> or more popups can be visible and potentially overlap each other based on
> which one was clicked on last. In some IDEs you can have all of these
> floating panels. Spell-check and Find dialogs are other examples where
> they can be popped up and not dismissed while some other popup or dropdown
> shows up and has to show up above or under the floating Spell-Check or Find
> dialog.
> >>
> >> Flex had a whole ActiveWindowManager that worked with the
> PopUpManager. Royale should try to make support for floating dialogs PAYG.
> >>
> >> Thanks,
> >> -Alex
> >>
> >
> >
> >
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Issue with Jewel popup
Posted by Harbs <ha...@gmail.com>.
Sure.
All I was saying with the z-indexes is that it makes sense to stick to some conventions when implementing different beads/managers so they play nicely with each other.
> On Jan 16, 2019, at 8:41 AM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> Royale offers choices. For PAYG reasons we probably wouldn't want to implement only the "ultimate floating window manager". There are different strategies as to what goes on top and when (on mouseDown or mouseUp). Modal dialogs can have popups and float stuff over them if they want.
>
> My 2 cents,
> -Alex
>
> On 1/15/19, 10:13 PM, "Harbs" <ha...@gmail.com> wrote:
>
> Floating windows could probably be handled pretty easily by changing the z-index on each of the popups (in HTML).
>
> Of course you’d need a manager to handle that, but it shouldn’t be too hard to implement.
>
> That would probably be either a FloatingWindowManager singleton or FloatingWindowUtils static class.
>
> We probably want to standardize on different number ranges of z-index for different “classes” of floating things.
>
> I imagine modal dialogs would have the highest z-index. The possible exception to that would be popup menus. Floating windows somewhat lower than modal dialogs, etc.
>
>> On Jan 16, 2019, at 2:39 AM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>>
>>
>>
>> On 1/15/19, 2:48 PM, "Carlos Rovira" <ca...@apache.org> wrote:
>>
>>>
>>> Support for "overlapping windows" would be PAYG and added via some other
>>> classes. I don't think we've done anything there at the Basic level, the
>>> emulation components may have to support it since Flex did.
>>>
>>
>> What do you mean with "overlapping windows". Don't understand that concept.
>> For me windows are always one on top of another...
>>
>> Oh yeah, forgot to describe that. "overlapping windows" means that two or more popups can be visible and potentially overlap each other based on which one was clicked on last. In some IDEs you can have all of these floating panels. Spell-check and Find dialogs are other examples where they can be popped up and not dismissed while some other popup or dropdown shows up and has to show up above or under the floating Spell-Check or Find dialog.
>>
>> Flex had a whole ActiveWindowManager that worked with the PopUpManager. Royale should try to make support for floating dialogs PAYG.
>>
>> Thanks,
>> -Alex
>>
>
>
>
Re: Issue with Jewel popup
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Royale offers choices. For PAYG reasons we probably wouldn't want to implement only the "ultimate floating window manager". There are different strategies as to what goes on top and when (on mouseDown or mouseUp). Modal dialogs can have popups and float stuff over them if they want.
My 2 cents,
-Alex
On 1/15/19, 10:13 PM, "Harbs" <ha...@gmail.com> wrote:
Floating windows could probably be handled pretty easily by changing the z-index on each of the popups (in HTML).
Of course you’d need a manager to handle that, but it shouldn’t be too hard to implement.
That would probably be either a FloatingWindowManager singleton or FloatingWindowUtils static class.
We probably want to standardize on different number ranges of z-index for different “classes” of floating things.
I imagine modal dialogs would have the highest z-index. The possible exception to that would be popup menus. Floating windows somewhat lower than modal dialogs, etc.
> On Jan 16, 2019, at 2:39 AM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
>
>
> On 1/15/19, 2:48 PM, "Carlos Rovira" <ca...@apache.org> wrote:
>
>>
>> Support for "overlapping windows" would be PAYG and added via some other
>> classes. I don't think we've done anything there at the Basic level, the
>> emulation components may have to support it since Flex did.
>>
>
> What do you mean with "overlapping windows". Don't understand that concept.
> For me windows are always one on top of another...
>
> Oh yeah, forgot to describe that. "overlapping windows" means that two or more popups can be visible and potentially overlap each other based on which one was clicked on last. In some IDEs you can have all of these floating panels. Spell-check and Find dialogs are other examples where they can be popped up and not dismissed while some other popup or dropdown shows up and has to show up above or under the floating Spell-Check or Find dialog.
>
> Flex had a whole ActiveWindowManager that worked with the PopUpManager. Royale should try to make support for floating dialogs PAYG.
>
> Thanks,
> -Alex
>
Re: Issue with Jewel popup
Posted by Harbs <ha...@gmail.com>.
Floating windows could probably be handled pretty easily by changing the z-index on each of the popups (in HTML).
Of course you’d need a manager to handle that, but it shouldn’t be too hard to implement.
That would probably be either a FloatingWindowManager singleton or FloatingWindowUtils static class.
We probably want to standardize on different number ranges of z-index for different “classes” of floating things.
I imagine modal dialogs would have the highest z-index. The possible exception to that would be popup menus. Floating windows somewhat lower than modal dialogs, etc.
> On Jan 16, 2019, at 2:39 AM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
>
>
> On 1/15/19, 2:48 PM, "Carlos Rovira" <ca...@apache.org> wrote:
>
>>
>> Support for "overlapping windows" would be PAYG and added via some other
>> classes. I don't think we've done anything there at the Basic level, the
>> emulation components may have to support it since Flex did.
>>
>
> What do you mean with "overlapping windows". Don't understand that concept.
> For me windows are always one on top of another...
>
> Oh yeah, forgot to describe that. "overlapping windows" means that two or more popups can be visible and potentially overlap each other based on which one was clicked on last. In some IDEs you can have all of these floating panels. Spell-check and Find dialogs are other examples where they can be popped up and not dismissed while some other popup or dropdown shows up and has to show up above or under the floating Spell-Check or Find dialog.
>
> Flex had a whole ActiveWindowManager that worked with the PopUpManager. Royale should try to make support for floating dialogs PAYG.
>
> Thanks,
> -Alex
>
Re: Issue with Jewel popup
Posted by Alex Harui <ah...@adobe.com.INVALID>.
On 1/15/19, 2:48 PM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Support for "overlapping windows" would be PAYG and added via some other
> classes. I don't think we've done anything there at the Basic level, the
> emulation components may have to support it since Flex did.
>
What do you mean with "overlapping windows". Don't understand that concept.
For me windows are always one on top of another...
Oh yeah, forgot to describe that. "overlapping windows" means that two or more popups can be visible and potentially overlap each other based on which one was clicked on last. In some IDEs you can have all of these floating panels. Spell-check and Find dialogs are other examples where they can be popped up and not dismissed while some other popup or dropdown shows up and has to show up above or under the floating Spell-Check or Find dialog.
Flex had a whole ActiveWindowManager that worked with the PopUpManager. Royale should try to make support for floating dialogs PAYG.
Thanks,
-Alex
Re: Issue with Jewel popup
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex,
El mar., 15 ene. 2019 a las 18:50, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> In theory, the Basic popup support is "basic". It should handle
> "stacking" scenarios, but not "overlapping window" scenarios.
>
> So, a popup dialog should be able to have a tooltip or a
> dropdownlist/popupmenu or even popup an Alert or another popup dialog. The
> latest popup should be addElement'd to the IPopUpHost at a higher index and
> therefore be on top. And as long as each gets dismissed in reverse order,
> all should be good.
>
For now this is working. I put a Popup with a Form in the new FooterBar,
that form has DateField and ComboBox that shows popups over popup and
tooltips
So with Harbs's fix all is working as expected.
>
> Support for "overlapping windows" would be PAYG and added via some other
> classes. I don't think we've done anything there at the Basic level, the
> emulation components may have to support it since Flex did.
>
What do you mean with "overlapping windows". Don't understand that concept.
For me windows are always one on top of another...
Thanks
>
> HTH,
> -Alex
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Issue with Jewel popup
Posted by Alex Harui <ah...@adobe.com.INVALID>.
In theory, the Basic popup support is "basic". It should handle "stacking" scenarios, but not "overlapping window" scenarios.
So, a popup dialog should be able to have a tooltip or a dropdownlist/popupmenu or even popup an Alert or another popup dialog. The latest popup should be addElement'd to the IPopUpHost at a higher index and therefore be on top. And as long as each gets dismissed in reverse order, all should be good.
Support for "overlapping windows" would be PAYG and added via some other classes. I don't think we've done anything there at the Basic level, the emulation components may have to support it since Flex did.
HTH,
-Alex
On 1/15/19, 4:06 AM, "Carlos Rovira" <ca...@apache.org> wrote:
Hi Harbs
I saw this the other day. Thanks for reporting.
The problem is that PopUp uses
UIUtils.addPopUp(_popUp, getHost());
(that does a call to findPopUpHost)
And the ToolTips uses this too.
In the other hand Alex did some changes and now we have
IPopUpHost
and
IPopUpHostParent
And I think Jewel and maybe Basic too is not having into account this kind
of cases where a something popups other things and the latest popup another.
I think this is a good place to solve this. So could you help with this
issue and try to fix it? Since you already has experience with popups hope
you could bring a proper solution to this.
I already tried with no luck.
About adding to the body...is not a problem, if we need to add there, I
think is ok. So if the change implies that I think we could do it.
Maybe we could have some issues with CSS rules of that components, but I'm
sure I can help in that part.
Let me know if you can
thanks
Carlos
El mar., 15 ene. 2019 a las 9:21, Harbs (<ha...@gmail.com>) escribió:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Ftourdejewel%2F%23&data=02%7C01%7Caharui%40adobe.com%7C6a9da2e9cc47458f9fdc08d67ae1dda5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636831507838213215&sdata=LJvn%2FzvsNAndAKZVP9srcxcQ4%2F6D9wJPWg2PqPWwQYo%3D&reserved=0
>
> Click on Popup and click the non-modal one.
>
> Type something into the fields and you’ll see that the validation text
> gets cut off to the boundaries of the section div on the main page. The
> validation div also remains after closing the popup.
>
> Is there a reason Jewel popups are not added to the body?
>
> Thanks,
> Harbs
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C6a9da2e9cc47458f9fdc08d67ae1dda5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636831507838213215&sdata=OmYI81k8GK53%2Bb%2BB8a6yLV9SdegKEGNvyHXHttyM79E%3D&reserved=0
Re: Issue with Jewel popup
Posted by Carlos Rovira <ca...@apache.org>.
Hi Harbs
I saw this the other day. Thanks for reporting.
The problem is that PopUp uses
UIUtils.addPopUp(_popUp, getHost());
(that does a call to findPopUpHost)
And the ToolTips uses this too.
In the other hand Alex did some changes and now we have
IPopUpHost
and
IPopUpHostParent
And I think Jewel and maybe Basic too is not having into account this kind
of cases where a something popups other things and the latest popup another.
I think this is a good place to solve this. So could you help with this
issue and try to fix it? Since you already has experience with popups hope
you could bring a proper solution to this.
I already tried with no luck.
About adding to the body...is not a problem, if we need to add there, I
think is ok. So if the change implies that I think we could do it.
Maybe we could have some issues with CSS rules of that components, but I'm
sure I can help in that part.
Let me know if you can
thanks
Carlos
El mar., 15 ene. 2019 a las 9:21, Harbs (<ha...@gmail.com>) escribió:
> https://royale.apache.org/tourdejewel/#
>
> Click on Popup and click the non-modal one.
>
> Type something into the fields and you’ll see that the validation text
> gets cut off to the boundaries of the section div on the main page. The
> validation div also remains after closing the popup.
>
> Is there a reason Jewel popups are not added to the body?
>
> Thanks,
> Harbs
--
Carlos Rovira
http://about.me/carlosrovira