Re: Routing (was Re: Spectrum Components)

[Alex Harui]

What version of Basic does your project use?  Could it still be a 0.9.7*?  I 
think the dev branch is on 0.9.8-SNAPSHOT

-Alex

On 5/11/20, 5:37 AM, "Piotr Zarzycki"  wrote:

Hi Harbs,

Today I have wiped out my cached Maven artifacts and tried build our
application where I'm using all stuff which you have lately added. I'm
getting following type of issues and cannot build my project:

 Error: Type was not found or was not a compile-time constant: IRouter.

function get router():IRouter;

Error: Access of possibly undefined property BrowserRouter.

var router:BrowserRouter = event.target as
BrowserRouter;

I'm wondering what is being missed? I was trying to add those classes
in BasicClasses
but it doesn't help. Note that I'm able to build my application using ANT
build from Jenkins.

Any thoughts ?

Thanks,
Piotr

wt., 21 kwi 2020 o 14:18 Harbs  napisał(a):

> It should be fixed.
>
> > On Apr 21, 2020, at 2:47 PM, Harbs  wrote:
> >
> > Yeah. I’ll fix that…
> >
> >> On Apr 21, 2020, at 10:59 AM, Piotr Zarzycki 

> wrote:
> >>
> >> Hi Harbs,
> >>
> >> I see some properties which would no longer work [1] - If I use
> >> BrowserRouter as a host. In this specific class that property is not
> used,
> >> but I'm pointing to the issue. Maybe HasRouter and BrowserRouter should
> >> have some common interface ?
> >>
> >> [1]
> >>
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Ffa4e6bdf58ea30f68d5efc0e9cc98318d4f0d293%2Fframeworks%2Fprojects%2FBasic%2Fsrc%2Fmain%2Froyale%2Forg%2Fapache%2Froyale%2Frouting%2FRouteToParameters.as%23L35data=02%7C01%7Caharui%40adobe.com%7Ccdaded1ada77458139b808d7f5a81e9c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247974734012658sdata=s3v%2BtyosnNUmFV7jJ5OIT8WPqEA5CGemjJftb6kvkNo%3Dreserved=0
> >>
> >> Thanks,
> >> Piotr
>
>

-- 

Piotr Zarzycki

Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Ccdaded1ada77458139b808d7f5a81e9c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247974734012658sdata=KXSrppnwt8FpCnUoZ7zcE5OeYVR190BiL9Zo1xXm4ek%3Dreserved=0

*

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Hi Harbs,

Today I have wiped out my cached Maven artifacts and tried build our
application where I'm using all stuff which you have lately added. I'm
getting following type of issues and cannot build my project:

 Error: Type was not found or was not a compile-time constant: IRouter.

function get router():IRouter;

Error: Access of possibly undefined property BrowserRouter.

var router:BrowserRouter = event.target as
BrowserRouter;

I'm wondering what is being missed? I was trying to add those classes
in BasicClasses
but it doesn't help. Note that I'm able to build my application using ANT
build from Jenkins.

Any thoughts ?

Thanks,
Piotr

wt., 21 kwi 2020 o 14:18 Harbs  napisał(a):

> It should be fixed.
>
> > On Apr 21, 2020, at 2:47 PM, Harbs  wrote:
> >
> > Yeah. I’ll fix that…
> >
> >> On Apr 21, 2020, at 10:59 AM, Piotr Zarzycki 
> wrote:
> >>
> >> Hi Harbs,
> >>
> >> I see some properties which would no longer work [1] - If I use
> >> BrowserRouter as a host. In this specific class that property is not
> used,
> >> but I'm pointing to the issue. Maybe HasRouter and BrowserRouter should
> >> have some common interface ?
> >>
> >> [1]
> >>
> https://github.com/apache/royale-asjs/blob/fa4e6bdf58ea30f68d5efc0e9cc98318d4f0d293/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/RouteToParameters.as#L35
> >>
> >> Thanks,
> >> Piotr
>
>

-- 

Piotr Zarzycki

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

Re: Routing (was Re: Spectrum Components)

[Harbs]

It should be fixed.

> On Apr 21, 2020, at 2:47 PM, Harbs  wrote:
> 
> Yeah. I’ll fix that…
> 
>> On Apr 21, 2020, at 10:59 AM, Piotr Zarzycki  
>> wrote:
>> 
>> Hi Harbs,
>> 
>> I see some properties which would no longer work [1] - If I use
>> BrowserRouter as a host. In this specific class that property is not used,
>> but I'm pointing to the issue. Maybe HasRouter and BrowserRouter should
>> have some common interface ?
>> 
>> [1]
>> https://github.com/apache/royale-asjs/blob/fa4e6bdf58ea30f68d5efc0e9cc98318d4f0d293/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/RouteToParameters.as#L35
>> 
>> Thanks,
>> Piotr

Re: Routing (was Re: Spectrum Components)

[Harbs]

Yeah. I’ll fix that…

> On Apr 21, 2020, at 10:59 AM, Piotr Zarzycki  
> wrote:
> 
> Hi Harbs,
> 
> I see some properties which would no longer work [1] - If I use
> BrowserRouter as a host. In this specific class that property is not used,
> but I'm pointing to the issue. Maybe HasRouter and BrowserRouter should
> have some common interface ?
> 
> [1]
> https://github.com/apache/royale-asjs/blob/fa4e6bdf58ea30f68d5efc0e9cc98318d4f0d293/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/RouteToParameters.as#L35
> 
> Thanks,
> Piotr
> 
> pon., 20 kwi 2020 o 17:56 Piotr Zarzycki 
> napisał(a):
> 
>> Got it. It's working I'm able to get params. We will see what I can do
>> more. :)
>> 
>> Thank you!
>> 
>> pon., 20 kwi 2020 o 17:51 Harbs  napisał(a):
>> 
>>> Exactly like lines 99 through 102 here:
>>> 
>>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>>> <
>>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
 
>>> 
>>> RouteToParameters will parse the parameters and use the ParameterRoutes
>>> to “do the right thing”.
>>> 
 On Apr 20, 2020, at 6:35 PM, Piotr Zarzycki 
>>> wrote:
 
 Yeah I just realized that I didn't express myself clearly. I would ask
 differently cause you are saying about beads. What bead would parse for
>>> me
 those parameters ?
 
 https://myrul.com/test?target=somevalue=
 <
>>> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
 
 somevalue
 
 I'm assuming this is not ready for BroswerRouter yet ?
 
 
 pon., 20 kwi 2020 o 17:31 Harbs  napisał(a):
 
> Huh? Not sure what you’re asking.
> 
> The parsing of the URLs are all done via beads.
> 
>> On Apr 20, 2020, at 5:51 PM, Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com>
> wrote:
>> 
>> I will check your changes, but looking into the code you didn't touch
>> parameter parsing. It probably will be the same story for
>>> BrowserRouter
> and
>> HasRouter - Maybe it's worth to place it in  RouteToParameters ?
>> 
>> pon., 20 kwi 2020 o 16:38 Harbs  napisał(a):
>> 
>>> I just pushed something. It builds, but I don’t have a setup to be
>>> able
> to
>>> test it properly.
>>> 
>>> Calling setState() and renderState() should work, but I still haven’t
>>> finished beads to intercept links.
>>> 
>>> Let me know how it goes…
>>> 
>>> Harbs
>>> 
 On Apr 20, 2020, at 4:45 PM, Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com
>> 
>>> wrote:
 
 Harbs,
 
 Do you think you will have something pushed today/tomorrow or is it
>>> rather
 something for the next week or so ?
 
 pon., 20 kwi 2020 o 11:56 Piotr Zarzycki >>> 
 napisał(a):
 
> Ok. Thanks I look forward to your update.
> 
> pon., 20 kwi 2020 o 11:51 Harbs 
>>> napisał(a):
> 
>> I’m deprecating Router and replacing it with HashRouter and
>>> BrowserRouter.
>> 
>> I’m going to try and keep the same beads working with either
>>> router.
>> 
>>> On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com>
>> wrote:
>>> 
>>> Harbs,
>>> 
>>> What please describe what are you going to change exactly. Since
>>> I
>>> need
>> to
>>> move forward with my feature in application I will probably
> implement
>>> adhoc solution with Router in app only, but I would like to avoid
> some
>> big
>>> changes when you commit your code.
>>> 
>>> Thanks,
>>> Piotr
>>> 
>>> pon., 20 kwi 2020 o 09:52 Harbs > harbs.li...@gmail.com>> napisał(a):
>>> 
 There are beads which handle the following:
 
 1. Paths — in a hash router, this would be the part of the url
>>> between
>> the
 hash and the question mark or a second hash. In a “browser
>>> router”
>>> this
 would be the section between the base and and the question mark
>>> or
> a
>> hash
 2. Parameters — handles between the question mark and subsequent
>>> hash.
 (yes RouteToParameter works)
 3. I started work on dealing with trailing hash links for
>>> scrolling
>>> to
 anchor (or rather id) behavior, but that’s not yet done.
>>> (Something
>> like
 this:
 
>>> 
>>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>> <
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior>
>>> <
 
>>> 
>>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>> <

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Hi Harbs,

I see some properties which would no longer work [1] - If I use
BrowserRouter as a host. In this specific class that property is not used,
but I'm pointing to the issue. Maybe HasRouter and BrowserRouter should
have some common interface ?

[1]
https://github.com/apache/royale-asjs/blob/fa4e6bdf58ea30f68d5efc0e9cc98318d4f0d293/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/RouteToParameters.as#L35

Thanks,
Piotr

pon., 20 kwi 2020 o 17:56 Piotr Zarzycki 
napisał(a):

> Got it. It's working I'm able to get params. We will see what I can do
> more. :)
>
> Thank you!
>
> pon., 20 kwi 2020 o 17:51 Harbs  napisał(a):
>
>> Exactly like lines 99 through 102 here:
>>
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>> <
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>> >
>>
>> RouteToParameters will parse the parameters and use the ParameterRoutes
>> to “do the right thing”.
>>
>> > On Apr 20, 2020, at 6:35 PM, Piotr Zarzycki 
>> wrote:
>> >
>> > Yeah I just realized that I didn't express myself clearly. I would ask
>> > differently cause you are saying about beads. What bead would parse for
>> me
>> > those parameters ?
>> >
>> > https://myrul.com/test?target=somevalue=
>> > <
>> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
>> >
>> > somevalue
>> >
>> > I'm assuming this is not ready for BroswerRouter yet ?
>> >
>> >
>> > pon., 20 kwi 2020 o 17:31 Harbs  napisał(a):
>> >
>> >> Huh? Not sure what you’re asking.
>> >>
>> >> The parsing of the URLs are all done via beads.
>> >>
>> >>> On Apr 20, 2020, at 5:51 PM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
>> >> wrote:
>> >>>
>> >>> I will check your changes, but looking into the code you didn't touch
>> >>> parameter parsing. It probably will be the same story for
>> BrowserRouter
>> >> and
>> >>> HasRouter - Maybe it's worth to place it in  RouteToParameters ?
>> >>>
>> >>> pon., 20 kwi 2020 o 16:38 Harbs  napisał(a):
>> >>>
>>  I just pushed something. It builds, but I don’t have a setup to be
>> able
>> >> to
>>  test it properly.
>> 
>>  Calling setState() and renderState() should work, but I still haven’t
>>  finished beads to intercept links.
>> 
>>  Let me know how it goes…
>> 
>>  Harbs
>> 
>> > On Apr 20, 2020, at 4:45 PM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com
>> >>>
>>  wrote:
>> >
>> > Harbs,
>> >
>> > Do you think you will have something pushed today/tomorrow or is it
>>  rather
>> > something for the next week or so ?
>> >
>> > pon., 20 kwi 2020 o 11:56 Piotr Zarzycki > >
>> > napisał(a):
>> >
>> >> Ok. Thanks I look forward to your update.
>> >>
>> >> pon., 20 kwi 2020 o 11:51 Harbs 
>> napisał(a):
>> >>
>> >>> I’m deprecating Router and replacing it with HashRouter and
>>  BrowserRouter.
>> >>>
>> >>> I’m going to try and keep the same beads working with either
>> router.
>> >>>
>>  On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki <
>>  piotrzarzyck...@gmail.com>
>> >>> wrote:
>> 
>>  Harbs,
>> 
>>  What please describe what are you going to change exactly. Since
>> I
>>  need
>> >>> to
>>  move forward with my feature in application I will probably
>> >> implement
>>  adhoc solution with Router in app only, but I would like to avoid
>> >> some
>> >>> big
>>  changes when you commit your code.
>> 
>>  Thanks,
>>  Piotr
>> 
>>  pon., 20 kwi 2020 o 09:52 Harbs > >>> harbs.li...@gmail.com>> napisał(a):
>> 
>> > There are beads which handle the following:
>> >
>> > 1. Paths — in a hash router, this would be the part of the url
>>  between
>> >>> the
>> > hash and the question mark or a second hash. In a “browser
>> router”
>>  this
>> > would be the section between the base and and the question mark
>> or
>> >> a
>> >>> hash
>> > 2. Parameters — handles between the question mark and subsequent
>>  hash.
>> > (yes RouteToParameter works)
>> > 3. I started work on dealing with trailing hash links for
>> scrolling
>>  to
>> > anchor (or rather id) behavior, but that’s not yet done.
>> (Something
>> >>> like
>> > this:
>> >
>> 
>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>> >>> <
>> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior>
>>  <
>> >
>> 
>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>> >>> <
>> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>> >> )
>> >
>> > Ideally all of these beads should work in either kind of router.
>> >> This

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Got it. It's working I'm able to get params. We will see what I can do
more. :)

Thank you!

pon., 20 kwi 2020 o 17:51 Harbs  napisał(a):

> Exactly like lines 99 through 102 here:
>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> <
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
>
> RouteToParameters will parse the parameters and use the ParameterRoutes to
> “do the right thing”.
>
> > On Apr 20, 2020, at 6:35 PM, Piotr Zarzycki 
> wrote:
> >
> > Yeah I just realized that I didn't express myself clearly. I would ask
> > differently cause you are saying about beads. What bead would parse for
> me
> > those parameters ?
> >
> > https://myrul.com/test?target=somevalue=
> > <
> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
> >
> > somevalue
> >
> > I'm assuming this is not ready for BroswerRouter yet ?
> >
> >
> > pon., 20 kwi 2020 o 17:31 Harbs  napisał(a):
> >
> >> Huh? Not sure what you’re asking.
> >>
> >> The parsing of the URLs are all done via beads.
> >>
> >>> On Apr 20, 2020, at 5:51 PM, Piotr Zarzycki  >
> >> wrote:
> >>>
> >>> I will check your changes, but looking into the code you didn't touch
> >>> parameter parsing. It probably will be the same story for BrowserRouter
> >> and
> >>> HasRouter - Maybe it's worth to place it in  RouteToParameters ?
> >>>
> >>> pon., 20 kwi 2020 o 16:38 Harbs  napisał(a):
> >>>
>  I just pushed something. It builds, but I don’t have a setup to be
> able
> >> to
>  test it properly.
> 
>  Calling setState() and renderState() should work, but I still haven’t
>  finished beads to intercept links.
> 
>  Let me know how it goes…
> 
>  Harbs
> 
> > On Apr 20, 2020, at 4:45 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com
> >>>
>  wrote:
> >
> > Harbs,
> >
> > Do you think you will have something pushed today/tomorrow or is it
>  rather
> > something for the next week or so ?
> >
> > pon., 20 kwi 2020 o 11:56 Piotr Zarzycki 
> > napisał(a):
> >
> >> Ok. Thanks I look forward to your update.
> >>
> >> pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):
> >>
> >>> I’m deprecating Router and replacing it with HashRouter and
>  BrowserRouter.
> >>>
> >>> I’m going to try and keep the same beads working with either
> router.
> >>>
>  On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki <
>  piotrzarzyck...@gmail.com>
> >>> wrote:
> 
>  Harbs,
> 
>  What please describe what are you going to change exactly. Since I
>  need
> >>> to
>  move forward with my feature in application I will probably
> >> implement
>  adhoc solution with Router in app only, but I would like to avoid
> >> some
> >>> big
>  changes when you commit your code.
> 
>  Thanks,
>  Piotr
> 
>  pon., 20 kwi 2020 o 09:52 Harbs  >>> harbs.li...@gmail.com>> napisał(a):
> 
> > There are beads which handle the following:
> >
> > 1. Paths — in a hash router, this would be the part of the url
>  between
> >>> the
> > hash and the question mark or a second hash. In a “browser
> router”
>  this
> > would be the section between the base and and the question mark
> or
> >> a
> >>> hash
> > 2. Parameters — handles between the question mark and subsequent
>  hash.
> > (yes RouteToParameter works)
> > 3. I started work on dealing with trailing hash links for
> scrolling
>  to
> > anchor (or rather id) behavior, but that’s not yet done.
> (Something
> >>> like
> > this:
> >
>  https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> >>> <
> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior>
>  <
> >
>  https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> >>> <
> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> >> )
> >
> > Ideally all of these beads should work in either kind of router.
> >> This
> >>> is
> > already PAYG, but it’s going to take some work to get this
> working
>  and
> >>> PAYG
> > for both kinds of routers.
> >
> > I’ll try to work on this today…
> >
> > Harbs
> >
> >> On Apr 20, 2020, at 10:01 AM, Carlos Rovira <
>  carlosrov...@apache.org>
> > wrote:
> >>
> >> Hi Piotr,
> >>
> >> I used hashes with params, so that's completely fine and we
> should
> >>> have
> > it.
> >> In fact, I think we already should have it since I'm seeing
> >> "RoutToParameter" class right? Maybe Harbs should confirm this
> >> since
> >>> 

Re: Routing (was Re: Spectrum Components)

[Harbs]

Exactly like lines 99 through 102 here:
https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
 


RouteToParameters will parse the parameters and use the ParameterRoutes to “do 
the right thing”.

> On Apr 20, 2020, at 6:35 PM, Piotr Zarzycki  wrote:
> 
> Yeah I just realized that I didn't express myself clearly. I would ask
> differently cause you are saying about beads. What bead would parse for me
> those parameters ?
> 
> https://myrul.com/test?target=somevalue=
> 
> somevalue
> 
> I'm assuming this is not ready for BroswerRouter yet ?
> 
> 
> pon., 20 kwi 2020 o 17:31 Harbs  napisał(a):
> 
>> Huh? Not sure what you’re asking.
>> 
>> The parsing of the URLs are all done via beads.
>> 
>>> On Apr 20, 2020, at 5:51 PM, Piotr Zarzycki 
>> wrote:
>>> 
>>> I will check your changes, but looking into the code you didn't touch
>>> parameter parsing. It probably will be the same story for BrowserRouter
>> and
>>> HasRouter - Maybe it's worth to place it in  RouteToParameters ?
>>> 
>>> pon., 20 kwi 2020 o 16:38 Harbs  napisał(a):
>>> 
 I just pushed something. It builds, but I don’t have a setup to be able
>> to
 test it properly.
 
 Calling setState() and renderState() should work, but I still haven’t
 finished beads to intercept links.
 
 Let me know how it goes…
 
 Harbs
 
> On Apr 20, 2020, at 4:45 PM, Piotr Zarzycki >> 
 wrote:
> 
> Harbs,
> 
> Do you think you will have something pushed today/tomorrow or is it
 rather
> something for the next week or so ?
> 
> pon., 20 kwi 2020 o 11:56 Piotr Zarzycki 
> napisał(a):
> 
>> Ok. Thanks I look forward to your update.
>> 
>> pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):
>> 
>>> I’m deprecating Router and replacing it with HashRouter and
 BrowserRouter.
>>> 
>>> I’m going to try and keep the same beads working with either router.
>>> 
 On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki <
 piotrzarzyck...@gmail.com>
>>> wrote:
 
 Harbs,
 
 What please describe what are you going to change exactly. Since I
 need
>>> to
 move forward with my feature in application I will probably
>> implement
 adhoc solution with Router in app only, but I would like to avoid
>> some
>>> big
 changes when you commit your code.
 
 Thanks,
 Piotr
 
 pon., 20 kwi 2020 o 09:52 Harbs >> harbs.li...@gmail.com>> napisał(a):
 
> There are beads which handle the following:
> 
> 1. Paths — in a hash router, this would be the part of the url
 between
>>> the
> hash and the question mark or a second hash. In a “browser router”
 this
> would be the section between the base and and the question mark or
>> a
>>> hash
> 2. Parameters — handles between the question mark and subsequent
 hash.
> (yes RouteToParameter works)
> 3. I started work on dealing with trailing hash links for scrolling
 to
> anchor (or rather id) behavior, but that’s not yet done. (Something
>>> like
> this:
> 
 https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>>> <
>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior>
 <
> 
 https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>>> <
>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>> )
> 
> Ideally all of these beads should work in either kind of router.
>> This
>>> is
> already PAYG, but it’s going to take some work to get this working
 and
>>> PAYG
> for both kinds of routers.
> 
> I’ll try to work on this today…
> 
> Harbs
> 
>> On Apr 20, 2020, at 10:01 AM, Carlos Rovira <
 carlosrov...@apache.org>
> wrote:
>> 
>> Hi Piotr,
>> 
>> I used hashes with params, so that's completely fine and we should
>>> have
> it.
>> In fact, I think we already should have it since I'm seeing
>> "RoutToParameter" class right? Maybe Harbs should confirm this
>> since
>>> he
>> implemented, and I just saw the class but still not use it.
>> 
>> 
>> El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>) escribió:
>> 
>>> Harbs,
>>> 
>>> Agreed with that. We can rename them, but even in case of
 HashRouter
>>> -
> does
>>> exclude it ability to have parameters ? Does those parameters not
> 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Yeah I just realized that I didn't express myself clearly. I would ask
differently cause you are saying about beads. What bead would parse for me
those parameters ?

https://myrul.com/test?target=somevalue=

somevalue

I'm assuming this is not ready for BroswerRouter yet ?


pon., 20 kwi 2020 o 17:31 Harbs  napisał(a):

> Huh? Not sure what you’re asking.
>
> The parsing of the URLs are all done via beads.
>
> > On Apr 20, 2020, at 5:51 PM, Piotr Zarzycki 
> wrote:
> >
> > I will check your changes, but looking into the code you didn't touch
> > parameter parsing. It probably will be the same story for BrowserRouter
> and
> > HasRouter - Maybe it's worth to place it in  RouteToParameters ?
> >
> > pon., 20 kwi 2020 o 16:38 Harbs  napisał(a):
> >
> >> I just pushed something. It builds, but I don’t have a setup to be able
> to
> >> test it properly.
> >>
> >> Calling setState() and renderState() should work, but I still haven’t
> >> finished beads to intercept links.
> >>
> >> Let me know how it goes…
> >>
> >> Harbs
> >>
> >>> On Apr 20, 2020, at 4:45 PM, Piotr Zarzycki  >
> >> wrote:
> >>>
> >>> Harbs,
> >>>
> >>> Do you think you will have something pushed today/tomorrow or is it
> >> rather
> >>> something for the next week or so ?
> >>>
> >>> pon., 20 kwi 2020 o 11:56 Piotr Zarzycki 
> >>> napisał(a):
> >>>
>  Ok. Thanks I look forward to your update.
> 
>  pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):
> 
> > I’m deprecating Router and replacing it with HashRouter and
> >> BrowserRouter.
> >
> > I’m going to try and keep the same beads working with either router.
> >
> >> On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com>
> > wrote:
> >>
> >> Harbs,
> >>
> >> What please describe what are you going to change exactly. Since I
> >> need
> > to
> >> move forward with my feature in application I will probably
> implement
> >> adhoc solution with Router in app only, but I would like to avoid
> some
> > big
> >> changes when you commit your code.
> >>
> >> Thanks,
> >> Piotr
> >>
> >> pon., 20 kwi 2020 o 09:52 Harbs  > harbs.li...@gmail.com>> napisał(a):
> >>
> >>> There are beads which handle the following:
> >>>
> >>> 1. Paths — in a hash router, this would be the part of the url
> >> between
> > the
> >>> hash and the question mark or a second hash. In a “browser router”
> >> this
> >>> would be the section between the base and and the question mark or
> a
> > hash
> >>> 2. Parameters — handles between the question mark and subsequent
> >> hash.
> >>> (yes RouteToParameter works)
> >>> 3. I started work on dealing with trailing hash links for scrolling
> >> to
> >>> anchor (or rather id) behavior, but that’s not yet done. (Something
> > like
> >>> this:
> >>>
> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> > <
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior>
> >> <
> >>>
> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> > <
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>  )
> >>>
> >>> Ideally all of these beads should work in either kind of router.
> This
> > is
> >>> already PAYG, but it’s going to take some work to get this working
> >> and
> > PAYG
> >>> for both kinds of routers.
> >>>
> >>> I’ll try to work on this today…
> >>>
> >>> Harbs
> >>>
>  On Apr 20, 2020, at 10:01 AM, Carlos Rovira <
> >> carlosrov...@apache.org>
> >>> wrote:
> 
>  Hi Piotr,
> 
>  I used hashes with params, so that's completely fine and we should
> > have
> >>> it.
>  In fact, I think we already should have it since I'm seeing
>  "RoutToParameter" class right? Maybe Harbs should confirm this
> since
> > he
>  implemented, and I just saw the class but still not use it.
> 
> 
>  El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
>  piotrzarzyck...@gmail.com>) escribió:
> 
> > Harbs,
> >
> > Agreed with that. We can rename them, but even in case of
> >> HashRouter
> > -
> >>> does
> > exclude it ability to have parameters ? Does those parameters not
> >>> exists in
> > HasRouter as well. Is it not a common stuff no matter what kind
> of
> > url
> >>> it
> > is ?
> >
> > niedz., 19 kwi 2020 o 15:52 Harbs 
> > napisał(a):
> >
> >> After thinking about this some more, I’m thinking that Router
> > should be
> >> named and we should add another type of router for standard path
> >>> routing.
> >>
> >> React calls them HashRouter and 

Re: Routing (was Re: Spectrum Components)

[Harbs]

Huh? Not sure what you’re asking.

The parsing of the URLs are all done via beads.

> On Apr 20, 2020, at 5:51 PM, Piotr Zarzycki  wrote:
> 
> I will check your changes, but looking into the code you didn't touch
> parameter parsing. It probably will be the same story for BrowserRouter and
> HasRouter - Maybe it's worth to place it in  RouteToParameters ?
> 
> pon., 20 kwi 2020 o 16:38 Harbs  napisał(a):
> 
>> I just pushed something. It builds, but I don’t have a setup to be able to
>> test it properly.
>> 
>> Calling setState() and renderState() should work, but I still haven’t
>> finished beads to intercept links.
>> 
>> Let me know how it goes…
>> 
>> Harbs
>> 
>>> On Apr 20, 2020, at 4:45 PM, Piotr Zarzycki 
>> wrote:
>>> 
>>> Harbs,
>>> 
>>> Do you think you will have something pushed today/tomorrow or is it
>> rather
>>> something for the next week or so ?
>>> 
>>> pon., 20 kwi 2020 o 11:56 Piotr Zarzycki 
>>> napisał(a):
>>> 
 Ok. Thanks I look forward to your update.
 
 pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):
 
> I’m deprecating Router and replacing it with HashRouter and
>> BrowserRouter.
> 
> I’m going to try and keep the same beads working with either router.
> 
>> On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
> wrote:
>> 
>> Harbs,
>> 
>> What please describe what are you going to change exactly. Since I
>> need
> to
>> move forward with my feature in application I will probably implement
>> adhoc solution with Router in app only, but I would like to avoid some
> big
>> changes when you commit your code.
>> 
>> Thanks,
>> Piotr
>> 
>> pon., 20 kwi 2020 o 09:52 Harbs  harbs.li...@gmail.com>> napisał(a):
>> 
>>> There are beads which handle the following:
>>> 
>>> 1. Paths — in a hash router, this would be the part of the url
>> between
> the
>>> hash and the question mark or a second hash. In a “browser router”
>> this
>>> would be the section between the base and and the question mark or a
> hash
>>> 2. Parameters — handles between the question mark and subsequent
>> hash.
>>> (yes RouteToParameter works)
>>> 3. I started work on dealing with trailing hash links for scrolling
>> to
>>> anchor (or rather id) behavior, but that’s not yet done. (Something
> like
>>> this:
>>> 
>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> 
>> <
>>> 
>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> >> 
>>> Ideally all of these beads should work in either kind of router. This
> is
>>> already PAYG, but it’s going to take some work to get this working
>> and
> PAYG
>>> for both kinds of routers.
>>> 
>>> I’ll try to work on this today…
>>> 
>>> Harbs
>>> 
 On Apr 20, 2020, at 10:01 AM, Carlos Rovira <
>> carlosrov...@apache.org>
>>> wrote:
 
 Hi Piotr,
 
 I used hashes with params, so that's completely fine and we should
> have
>>> it.
 In fact, I think we already should have it since I'm seeing
 "RoutToParameter" class right? Maybe Harbs should confirm this since
> he
 implemented, and I just saw the class but still not use it.
 
 
 El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
 piotrzarzyck...@gmail.com>) escribió:
 
> Harbs,
> 
> Agreed with that. We can rename them, but even in case of
>> HashRouter
> -
>>> does
> exclude it ability to have parameters ? Does those parameters not
>>> exists in
> HasRouter as well. Is it not a common stuff no matter what kind of
> url
>>> it
> is ?
> 
> niedz., 19 kwi 2020 o 15:52 Harbs 
> napisał(a):
> 
>> After thinking about this some more, I’m thinking that Router
> should be
>> named and we should add another type of router for standard path
>>> routing.
>> 
>> React calls them HashRouter and BrowserRouter. Maybe we should use
> the
>> same names…
>> 
>> 
>>> 
> 
>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> <
>> 
>>> 
> 
>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
>> 
>> 
>>> On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com
>> 
>> wrote:
>>> 
>>> Hi Harbs,
>>> 
>>> It sounds like you are asking me to check in onInit whether
>>> if(location.hash) exists then do something, but if doesn't exists
>>> check
>> url
>>> 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

I will check your changes, but looking into the code you didn't touch
parameter parsing. It probably will be the same story for BrowserRouter and
HasRouter - Maybe it's worth to place it in  RouteToParameters ?

pon., 20 kwi 2020 o 16:38 Harbs  napisał(a):

> I just pushed something. It builds, but I don’t have a setup to be able to
> test it properly.
>
> Calling setState() and renderState() should work, but I still haven’t
> finished beads to intercept links.
>
> Let me know how it goes…
>
> Harbs
>
> > On Apr 20, 2020, at 4:45 PM, Piotr Zarzycki 
> wrote:
> >
> > Harbs,
> >
> > Do you think you will have something pushed today/tomorrow or is it
> rather
> > something for the next week or so ?
> >
> > pon., 20 kwi 2020 o 11:56 Piotr Zarzycki 
> > napisał(a):
> >
> >> Ok. Thanks I look forward to your update.
> >>
> >> pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):
> >>
> >>> I’m deprecating Router and replacing it with HashRouter and
> BrowserRouter.
> >>>
> >>> I’m going to try and keep the same beads working with either router.
> >>>
>  On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >>> wrote:
> 
>  Harbs,
> 
>  What please describe what are you going to change exactly. Since I
> need
> >>> to
>  move forward with my feature in application I will probably implement
>  adhoc solution with Router in app only, but I would like to avoid some
> >>> big
>  changes when you commit your code.
> 
>  Thanks,
>  Piotr
> 
>  pon., 20 kwi 2020 o 09:52 Harbs  >>> harbs.li...@gmail.com>> napisał(a):
> 
> > There are beads which handle the following:
> >
> > 1. Paths — in a hash router, this would be the part of the url
> between
> >>> the
> > hash and the question mark or a second hash. In a “browser router”
> this
> > would be the section between the base and and the question mark or a
> >>> hash
> > 2. Parameters — handles between the question mark and subsequent
> hash.
> > (yes RouteToParameter works)
> > 3. I started work on dealing with trailing hash links for scrolling
> to
> > anchor (or rather id) behavior, but that’s not yet done. (Something
> >>> like
> > this:
> >
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> >>> 
> <
> >
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> >>>  >>)
> >
> > Ideally all of these beads should work in either kind of router. This
> >>> is
> > already PAYG, but it’s going to take some work to get this working
> and
> >>> PAYG
> > for both kinds of routers.
> >
> > I’ll try to work on this today…
> >
> > Harbs
> >
> >> On Apr 20, 2020, at 10:01 AM, Carlos Rovira <
> carlosrov...@apache.org>
> > wrote:
> >>
> >> Hi Piotr,
> >>
> >> I used hashes with params, so that's completely fine and we should
> >>> have
> > it.
> >> In fact, I think we already should have it since I'm seeing
> >> "RoutToParameter" class right? Maybe Harbs should confirm this since
> >>> he
> >> implemented, and I just saw the class but still not use it.
> >>
> >>
> >> El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
> >> piotrzarzyck...@gmail.com>) escribió:
> >>
> >>> Harbs,
> >>>
> >>> Agreed with that. We can rename them, but even in case of
> HashRouter
> >>> -
> > does
> >>> exclude it ability to have parameters ? Does those parameters not
> > exists in
> >>> HasRouter as well. Is it not a common stuff no matter what kind of
> >>> url
> > it
> >>> is ?
> >>>
> >>> niedz., 19 kwi 2020 o 15:52 Harbs 
> >>> napisał(a):
> >>>
>  After thinking about this some more, I’m thinking that Router
> >>> should be
>  named and we should add another type of router for standard path
> > routing.
> 
>  React calls them HashRouter and BrowserRouter. Maybe we should use
> >>> the
>  same names…
> 
> 
> >
> >>>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> >>> <
> 
> >
> >>>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> 
> 
> > On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com
> 
>  wrote:
> >
> > Hi Harbs,
> >
> > It sounds like you are asking me to check in onInit whether
> > if(location.hash) exists then do something, but if doesn't exists
> > check
>  url
> > params. - I may understand it in a wrong way, but I think
> > location.hash
>  may
> > exists and location.search - where parameters are stored could
> >>> exists
> > equally.
> >
> > 

Re: Routing (was Re: Spectrum Components)

[Harbs]

I just pushed something. It builds, but I don’t have a setup to be able to test 
it properly.

Calling setState() and renderState() should work, but I still haven’t finished 
beads to intercept links.

Let me know how it goes…

Harbs

> On Apr 20, 2020, at 4:45 PM, Piotr Zarzycki  wrote:
> 
> Harbs,
> 
> Do you think you will have something pushed today/tomorrow or is it rather
> something for the next week or so ?
> 
> pon., 20 kwi 2020 o 11:56 Piotr Zarzycki 
> napisał(a):
> 
>> Ok. Thanks I look forward to your update.
>> 
>> pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):
>> 
>>> I’m deprecating Router and replacing it with HashRouter and BrowserRouter.
>>> 
>>> I’m going to try and keep the same beads working with either router.
>>> 
 On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki 
>>> wrote:
 
 Harbs,
 
 What please describe what are you going to change exactly. Since I need
>>> to
 move forward with my feature in application I will probably implement
 adhoc solution with Router in app only, but I would like to avoid some
>>> big
 changes when you commit your code.
 
 Thanks,
 Piotr
 
 pon., 20 kwi 2020 o 09:52 Harbs >> harbs.li...@gmail.com>> napisał(a):
 
> There are beads which handle the following:
> 
> 1. Paths — in a hash router, this would be the part of the url between
>>> the
> hash and the question mark or a second hash. In a “browser router” this
> would be the section between the base and and the question mark or a
>>> hash
> 2. Parameters — handles between the question mark and subsequent hash.
> (yes RouteToParameter works)
> 3. I started work on dealing with trailing hash links for scrolling to
> anchor (or rather id) behavior, but that’s not yet done. (Something
>>> like
> this:
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>>>  <
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>>> >)
> 
> Ideally all of these beads should work in either kind of router. This
>>> is
> already PAYG, but it’s going to take some work to get this working and
>>> PAYG
> for both kinds of routers.
> 
> I’ll try to work on this today…
> 
> Harbs
> 
>> On Apr 20, 2020, at 10:01 AM, Carlos Rovira 
> wrote:
>> 
>> Hi Piotr,
>> 
>> I used hashes with params, so that's completely fine and we should
>>> have
> it.
>> In fact, I think we already should have it since I'm seeing
>> "RoutToParameter" class right? Maybe Harbs should confirm this since
>>> he
>> implemented, and I just saw the class but still not use it.
>> 
>> 
>> El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>) escribió:
>> 
>>> Harbs,
>>> 
>>> Agreed with that. We can rename them, but even in case of HashRouter
>>> -
> does
>>> exclude it ability to have parameters ? Does those parameters not
> exists in
>>> HasRouter as well. Is it not a common stuff no matter what kind of
>>> url
> it
>>> is ?
>>> 
>>> niedz., 19 kwi 2020 o 15:52 Harbs 
>>> napisał(a):
>>> 
 After thinking about this some more, I’m thinking that Router
>>> should be
 named and we should add another type of router for standard path
> routing.
 
 React calls them HashRouter and BrowserRouter. Maybe we should use
>>> the
 same names…
 
 
> 
>>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
>>> <
 
> 
>>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
 
 
> On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com
 
 wrote:
> 
> Hi Harbs,
> 
> It sounds like you are asking me to check in onInit whether
> if(location.hash) exists then do something, but if doesn't exists
> check
 url
> params. - I may understand it in a wrong way, but I think
> location.hash
 may
> exists and location.search - where parameters are stored could
>>> exists
> equally.
> 
> if(location.hash)
> {
> hashChangeHandler();
> }
> 
> if (location.search)
> {
> parseParameters();
> }
> 
> Am I missing something ?
> 
> Thanks,
> Piotr
> 
> pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
> 
>> Whatever you think is fine by me.
>> 
>> I don’t remember why I have "if(location.hash)”. It’s possible you
> can
 get
>> rid of that conditional.
>> 
>> It could be you can get rid of that and 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Harbs,

Do you think you will have something pushed today/tomorrow or is it rather
something for the next week or so ?

pon., 20 kwi 2020 o 11:56 Piotr Zarzycki 
napisał(a):

> Ok. Thanks I look forward to your update.
>
> pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):
>
>> I’m deprecating Router and replacing it with HashRouter and BrowserRouter.
>>
>> I’m going to try and keep the same beads working with either router.
>>
>> > On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki 
>> wrote:
>> >
>> > Harbs,
>> >
>> > What please describe what are you going to change exactly. Since I need
>> to
>> > move forward with my feature in application I will probably implement
>> > adhoc solution with Router in app only, but I would like to avoid some
>> big
>> > changes when you commit your code.
>> >
>> > Thanks,
>> > Piotr
>> >
>> > pon., 20 kwi 2020 o 09:52 Harbs > harbs.li...@gmail.com>> napisał(a):
>> >
>> >> There are beads which handle the following:
>> >>
>> >> 1. Paths — in a hash router, this would be the part of the url between
>> the
>> >> hash and the question mark or a second hash. In a “browser router” this
>> >> would be the section between the base and and the question mark or a
>> hash
>> >> 2. Parameters — handles between the question mark and subsequent hash.
>> >> (yes RouteToParameter works)
>> >> 3. I started work on dealing with trailing hash links for scrolling to
>> >> anchor (or rather id) behavior, but that’s not yet done. (Something
>> like
>> >> this:
>> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>>  <
>> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>> >)
>> >>
>> >> Ideally all of these beads should work in either kind of router. This
>> is
>> >> already PAYG, but it’s going to take some work to get this working and
>> PAYG
>> >> for both kinds of routers.
>> >>
>> >> I’ll try to work on this today…
>> >>
>> >> Harbs
>> >>
>> >>> On Apr 20, 2020, at 10:01 AM, Carlos Rovira 
>> >> wrote:
>> >>>
>> >>> Hi Piotr,
>> >>>
>> >>> I used hashes with params, so that's completely fine and we should
>> have
>> >> it.
>> >>> In fact, I think we already should have it since I'm seeing
>> >>> "RoutToParameter" class right? Maybe Harbs should confirm this since
>> he
>> >>> implemented, and I just saw the class but still not use it.
>> >>>
>> >>>
>> >>> El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
>> >>> piotrzarzyck...@gmail.com>) escribió:
>> >>>
>>  Harbs,
>> 
>>  Agreed with that. We can rename them, but even in case of HashRouter
>> -
>> >> does
>>  exclude it ability to have parameters ? Does those parameters not
>> >> exists in
>>  HasRouter as well. Is it not a common stuff no matter what kind of
>> url
>> >> it
>>  is ?
>> 
>>  niedz., 19 kwi 2020 o 15:52 Harbs 
>> napisał(a):
>> 
>> > After thinking about this some more, I’m thinking that Router
>> should be
>> > named and we should add another type of router for standard path
>> >> routing.
>> >
>> > React calls them HashRouter and BrowserRouter. Maybe we should use
>> the
>> > same names…
>> >
>> >
>> >>
>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
>>  <
>> >
>> >>
>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
>> >
>> >
>> >> On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki <
>> >> piotrzarzyck...@gmail.com
>> >
>> > wrote:
>> >>
>> >> Hi Harbs,
>> >>
>> >> It sounds like you are asking me to check in onInit whether
>> >> if(location.hash) exists then do something, but if doesn't exists
>> >> check
>> > url
>> >> params. - I may understand it in a wrong way, but I think
>> >> location.hash
>> > may
>> >> exists and location.search - where parameters are stored could
>> exists
>> >> equally.
>> >>
>> >> if(location.hash)
>> >> {
>> >> hashChangeHandler();
>> >> }
>> >>
>> >> if (location.search)
>> >> {
>> >> parseParameters();
>> >> }
>> >>
>> >> Am I missing something ?
>> >>
>> >> Thanks,
>> >> Piotr
>> >>
>> >> pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
>> >>
>> >>> Whatever you think is fine by me.
>> >>>
>> >>> I don’t remember why I have "if(location.hash)”. It’s possible you
>> >> can
>> > get
>> >>> rid of that conditional.
>> >>>
>> >>> It could be you can get rid of that and handle hashRecieved in a
>> >> bead.
>> > If
>> >>> the hashReceived event has no hash you can then check the URL.You
>> do
>> > need
>> >>> to make sure that you always get a stateChange event and don’t
>>  dispatch
>> > it
>> >>> twice.
>> >>>
>> >>> Feel free to play around with the code… ;-)
>> >>>
>> >>> Harbs
>> >>>
>> 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Ok. Thanks I look forward to your update.

pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):

> I’m deprecating Router and replacing it with HashRouter and BrowserRouter.
>
> I’m going to try and keep the same beads working with either router.
>
> > On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki 
> wrote:
> >
> > Harbs,
> >
> > What please describe what are you going to change exactly. Since I need
> to
> > move forward with my feature in application I will probably implement
> > adhoc solution with Router in app only, but I would like to avoid some
> big
> > changes when you commit your code.
> >
> > Thanks,
> > Piotr
> >
> > pon., 20 kwi 2020 o 09:52 Harbs  harbs.li...@gmail.com>> napisał(a):
> >
> >> There are beads which handle the following:
> >>
> >> 1. Paths — in a hash router, this would be the part of the url between
> the
> >> hash and the question mark or a second hash. In a “browser router” this
> >> would be the section between the base and and the question mark or a
> hash
> >> 2. Parameters — handles between the question mark and subsequent hash.
> >> (yes RouteToParameter works)
> >> 3. I started work on dealing with trailing hash links for scrolling to
> >> anchor (or rather id) behavior, but that’s not yet done. (Something like
> >> this:
> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior <
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior> <
> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior <
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior>>)
> >>
> >> Ideally all of these beads should work in either kind of router. This is
> >> already PAYG, but it’s going to take some work to get this working and
> PAYG
> >> for both kinds of routers.
> >>
> >> I’ll try to work on this today…
> >>
> >> Harbs
> >>
> >>> On Apr 20, 2020, at 10:01 AM, Carlos Rovira 
> >> wrote:
> >>>
> >>> Hi Piotr,
> >>>
> >>> I used hashes with params, so that's completely fine and we should have
> >> it.
> >>> In fact, I think we already should have it since I'm seeing
> >>> "RoutToParameter" class right? Maybe Harbs should confirm this since he
> >>> implemented, and I just saw the class but still not use it.
> >>>
> >>>
> >>> El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
> >>> piotrzarzyck...@gmail.com>) escribió:
> >>>
>  Harbs,
> 
>  Agreed with that. We can rename them, but even in case of HashRouter -
> >> does
>  exclude it ability to have parameters ? Does those parameters not
> >> exists in
>  HasRouter as well. Is it not a common stuff no matter what kind of url
> >> it
>  is ?
> 
>  niedz., 19 kwi 2020 o 15:52 Harbs  napisał(a):
> 
> > After thinking about this some more, I’m thinking that Router should
> be
> > named and we should add another type of router for standard path
> >> routing.
> >
> > React calls them HashRouter and BrowserRouter. Maybe we should use
> the
> > same names…
> >
> >
> >>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
>  <
> >
> >>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> >
> >
> >> On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com
> >
> > wrote:
> >>
> >> Hi Harbs,
> >>
> >> It sounds like you are asking me to check in onInit whether
> >> if(location.hash) exists then do something, but if doesn't exists
> >> check
> > url
> >> params. - I may understand it in a wrong way, but I think
> >> location.hash
> > may
> >> exists and location.search - where parameters are stored could
> exists
> >> equally.
> >>
> >> if(location.hash)
> >> {
> >> hashChangeHandler();
> >> }
> >>
> >> if (location.search)
> >> {
> >> parseParameters();
> >> }
> >>
> >> Am I missing something ?
> >>
> >> Thanks,
> >> Piotr
> >>
> >> pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
> >>
> >>> Whatever you think is fine by me.
> >>>
> >>> I don’t remember why I have "if(location.hash)”. It’s possible you
> >> can
> > get
> >>> rid of that conditional.
> >>>
> >>> It could be you can get rid of that and handle hashRecieved in a
> >> bead.
> > If
> >>> the hashReceived event has no hash you can then check the URL.You
> do
> > need
> >>> to make sure that you always get a stateChange event and don’t
>  dispatch
> > it
> >>> twice.
> >>>
> >>> Feel free to play around with the code… ;-)
> >>>
> >>> Harbs
> >>>
>  On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> >>> wrote:
> 
>  I think it would be better to have it here in Router.
> 
>  pt., 17 kwi 2020 o 09:37 Harbs 
> napisał(a):
> 
> > Alternatively, you can subclass Router to support setting the
> > parameters

Re: Routing (was Re: Spectrum Components)

[Harbs]

I’m deprecating Router and replacing it with HashRouter and BrowserRouter.

I’m going to try and keep the same beads working with either router.

> On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki  
> wrote:
> 
> Harbs,
> 
> What please describe what are you going to change exactly. Since I need to
> move forward with my feature in application I will probably implement
> adhoc solution with Router in app only, but I would like to avoid some big
> changes when you commit your code.
> 
> Thanks,
> Piotr
> 
> pon., 20 kwi 2020 o 09:52 Harbs  > napisał(a):
> 
>> There are beads which handle the following:
>> 
>> 1. Paths — in a hash router, this would be the part of the url between the
>> hash and the question mark or a second hash. In a “browser router” this
>> would be the section between the base and and the question mark or a hash
>> 2. Parameters — handles between the question mark and subsequent hash.
>> (yes RouteToParameter works)
>> 3. I started work on dealing with trailing hash links for scrolling to
>> anchor (or rather id) behavior, but that’s not yet done. (Something like
>> this:
>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior 
>>  <
>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior 
>> >)
>> 
>> Ideally all of these beads should work in either kind of router. This is
>> already PAYG, but it’s going to take some work to get this working and PAYG
>> for both kinds of routers.
>> 
>> I’ll try to work on this today…
>> 
>> Harbs
>> 
>>> On Apr 20, 2020, at 10:01 AM, Carlos Rovira 
>> wrote:
>>> 
>>> Hi Piotr,
>>> 
>>> I used hashes with params, so that's completely fine and we should have
>> it.
>>> In fact, I think we already should have it since I'm seeing
>>> "RoutToParameter" class right? Maybe Harbs should confirm this since he
>>> implemented, and I just saw the class but still not use it.
>>> 
>>> 
>>> El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
>>> piotrzarzyck...@gmail.com>) escribió:
>>> 
 Harbs,
 
 Agreed with that. We can rename them, but even in case of HashRouter -
>> does
 exclude it ability to have parameters ? Does those parameters not
>> exists in
 HasRouter as well. Is it not a common stuff no matter what kind of url
>> it
 is ?
 
 niedz., 19 kwi 2020 o 15:52 Harbs  napisał(a):
 
> After thinking about this some more, I’m thinking that Router should be
> named and we should add another type of router for standard path
>> routing.
> 
> React calls them HashRouter and BrowserRouter. Maybe we should use the
> same names…
> 
> 
>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
 <
> 
>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> 
> 
>> On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com
> 
> wrote:
>> 
>> Hi Harbs,
>> 
>> It sounds like you are asking me to check in onInit whether
>> if(location.hash) exists then do something, but if doesn't exists
>> check
> url
>> params. - I may understand it in a wrong way, but I think
>> location.hash
> may
>> exists and location.search - where parameters are stored could exists
>> equally.
>> 
>> if(location.hash)
>> {
>> hashChangeHandler();
>> }
>> 
>> if (location.search)
>> {
>> parseParameters();
>> }
>> 
>> Am I missing something ?
>> 
>> Thanks,
>> Piotr
>> 
>> pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
>> 
>>> Whatever you think is fine by me.
>>> 
>>> I don’t remember why I have "if(location.hash)”. It’s possible you
>> can
> get
>>> rid of that conditional.
>>> 
>>> It could be you can get rid of that and handle hashRecieved in a
>> bead.
> If
>>> the hashReceived event has no hash you can then check the URL.You do
> need
>>> to make sure that you always get a stateChange event and don’t
 dispatch
> it
>>> twice.
>>> 
>>> Feel free to play around with the code… ;-)
>>> 
>>> Harbs
>>> 
 On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
>>> wrote:
 
 I think it would be better to have it here in Router.
 
 pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
 
> Alternatively, you can subclass Router to support setting the
> parameters
> in the onInit method.
> 
> Not sure which of these is best.
> 
>> On Apr 17, 2020, at 10:35 AM, Harbs 
>> wrote:
>> 
>> Actually, it’s not going to work because the
> router.routeState.parameters will not be set.
>> 
>> You will likely need to add code to set the

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Harbs,

What please describe what are you going to change exactly. Since I need to
move forward with my feature in application I will probably implement
adhoc solution with Router in app only, but I would like to avoid some big
changes when you commit your code.

Thanks,
Piotr

pon., 20 kwi 2020 o 09:52 Harbs  napisał(a):

> There are beads which handle the following:
>
> 1. Paths — in a hash router, this would be the part of the url between the
> hash and the question mark or a second hash. In a “browser router” this
> would be the section between the base and and the question mark or a hash
> 2. Parameters — handles between the question mark and subsequent hash.
> (yes RouteToParameter works)
> 3. I started work on dealing with trailing hash links for scrolling to
> anchor (or rather id) behavior, but that’s not yet done. (Something like
> this:
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior <
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior>)
>
> Ideally all of these beads should work in either kind of router. This is
> already PAYG, but it’s going to take some work to get this working and PAYG
> for both kinds of routers.
>
> I’ll try to work on this today…
>
> Harbs
>
> > On Apr 20, 2020, at 10:01 AM, Carlos Rovira 
> wrote:
> >
> > Hi Piotr,
> >
> > I used hashes with params, so that's completely fine and we should have
> it.
> > In fact, I think we already should have it since I'm seeing
> > "RoutToParameter" class right? Maybe Harbs should confirm this since he
> > implemented, and I just saw the class but still not use it.
> >
> >
> > El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> >> Harbs,
> >>
> >> Agreed with that. We can rename them, but even in case of HashRouter -
> does
> >> exclude it ability to have parameters ? Does those parameters not
> exists in
> >> HasRouter as well. Is it not a common stuff no matter what kind of url
> it
> >> is ?
> >>
> >> niedz., 19 kwi 2020 o 15:52 Harbs  napisał(a):
> >>
> >>> After thinking about this some more, I’m thinking that Router should be
> >>> named and we should add another type of router for standard path
> routing.
> >>>
> >>> React calls them HashRouter and BrowserRouter. Maybe we should use the
> >>> same names…
> >>>
> >>>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> >> <
> >>>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> >>>
> >>>
>  On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com
> >>>
> >>> wrote:
> 
>  Hi Harbs,
> 
>  It sounds like you are asking me to check in onInit whether
>  if(location.hash) exists then do something, but if doesn't exists
> check
> >>> url
>  params. - I may understand it in a wrong way, but I think
> location.hash
> >>> may
>  exists and location.search - where parameters are stored could exists
>  equally.
> 
>  if(location.hash)
>  {
>  hashChangeHandler();
>  }
> 
>  if (location.search)
>  {
>   parseParameters();
>  }
> 
>  Am I missing something ?
> 
>  Thanks,
>  Piotr
> 
>  pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
> 
> > Whatever you think is fine by me.
> >
> > I don’t remember why I have "if(location.hash)”. It’s possible you
> can
> >>> get
> > rid of that conditional.
> >
> > It could be you can get rid of that and handle hashRecieved in a
> bead.
> >>> If
> > the hashReceived event has no hash you can then check the URL.You do
> >>> need
> > to make sure that you always get a stateChange event and don’t
> >> dispatch
> >>> it
> > twice.
> >
> > Feel free to play around with the code… ;-)
> >
> > Harbs
> >
> >> On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> >>> piotrzarzyck...@gmail.com>
> > wrote:
> >>
> >> I think it would be better to have it here in Router.
> >>
> >> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >>
> >>> Alternatively, you can subclass Router to support setting the
> >>> parameters
> >>> in the onInit method.
> >>>
> >>> Not sure which of these is best.
> >>>
>  On Apr 17, 2020, at 10:35 AM, Harbs 
> wrote:
> 
>  Actually, it’s not going to work because the
> >>> router.routeState.parameters will not be set.
> 
>  You will likely need to add code to set the
> > router.routeState.parameters
> >>> using the part of the location after the question mark.
> 
>  The easiest way to do that would be to either:
>  1. Modify RouteToParameters.stateChanged to first check that there
> >>> is a
> >>> parameters value and then set it if not.
>  2. Subclass RouteToParameters and override stateChanged to make
> >> that
> >>> check first.
> 
> > On Apr 17, 2020, at 10:29 AM, Harbs  >>  >>> 

Re: Routing (was Re: Spectrum Components)

[Harbs]

There are beads which handle the following:

1. Paths — in a hash router, this would be the part of the url between the hash 
and the question mark or a second hash. In a “browser router” this would be the 
section between the base and and the question mark or a hash
2. Parameters — handles between the question mark and subsequent hash. (yes 
RouteToParameter works)
3. I started work on dealing with trailing hash links for scrolling to anchor 
(or rather id) behavior, but that’s not yet done. (Something like this: 
https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior 
)

Ideally all of these beads should work in either kind of router. This is 
already PAYG, but it’s going to take some work to get this working and PAYG for 
both kinds of routers.

I’ll try to work on this today…

Harbs

> On Apr 20, 2020, at 10:01 AM, Carlos Rovira  wrote:
> 
> Hi Piotr,
> 
> I used hashes with params, so that's completely fine and we should have it.
> In fact, I think we already should have it since I'm seeing
> "RoutToParameter" class right? Maybe Harbs should confirm this since he
> implemented, and I just saw the class but still not use it.
> 
> 
> El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
> 
>> Harbs,
>> 
>> Agreed with that. We can rename them, but even in case of HashRouter - does
>> exclude it ability to have parameters ? Does those parameters not exists in
>> HasRouter as well. Is it not a common stuff no matter what kind of url it
>> is ?
>> 
>> niedz., 19 kwi 2020 o 15:52 Harbs  napisał(a):
>> 
>>> After thinking about this some more, I’m thinking that Router should be
>>> named and we should add another type of router for standard path routing.
>>> 
>>> React calls them HashRouter and BrowserRouter. Maybe we should use the
>>> same names…
>>> 
>>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
>> <
>>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
>>> 
>>> 
 On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki >> 
>>> wrote:
 
 Hi Harbs,
 
 It sounds like you are asking me to check in onInit whether
 if(location.hash) exists then do something, but if doesn't exists check
>>> url
 params. - I may understand it in a wrong way, but I think location.hash
>>> may
 exists and location.search - where parameters are stored could exists
 equally.
 
 if(location.hash)
 {
 hashChangeHandler();
 }
 
 if (location.search)
 {
  parseParameters();
 }
 
 Am I missing something ?
 
 Thanks,
 Piotr
 
 pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
 
> Whatever you think is fine by me.
> 
> I don’t remember why I have "if(location.hash)”. It’s possible you can
>>> get
> rid of that conditional.
> 
> It could be you can get rid of that and handle hashRecieved in a bead.
>>> If
> the hashReceived event has no hash you can then check the URL.You do
>>> need
> to make sure that you always get a stateChange event and don’t
>> dispatch
>>> it
> twice.
> 
> Feel free to play around with the code… ;-)
> 
> Harbs
> 
>> On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com>
> wrote:
>> 
>> I think it would be better to have it here in Router.
>> 
>> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
>> 
>>> Alternatively, you can subclass Router to support setting the
>>> parameters
>>> in the onInit method.
>>> 
>>> Not sure which of these is best.
>>> 
 On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
 
 Actually, it’s not going to work because the
>>> router.routeState.parameters will not be set.
 
 You will likely need to add code to set the
> router.routeState.parameters
>>> using the part of the location after the question mark.
 
 The easiest way to do that would be to either:
 1. Modify RouteToParameters.stateChanged to first check that there
>>> is a
>>> parameters value and then set it if not.
 2. Subclass RouteToParameters and override stateChanged to make
>> that
>>> check first.
 
> On Apr 17, 2020, at 10:29 AM, Harbs > >> harbs.li...@gmail.com>> wrote:
> 
> I’m pretty sure it’ll work without the hash as well.
> 
> Give it a try.
> 
>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com >
>> wrote:
>> 
>> Hi Harbs,
>> 
>> Thanks for pointing me out, but this is still that Routing
>> expects
>>> me
>>> to
>> use in url hashes - The question is - What if I can't use hashes,
>>> but
>>> url
>> looks like I have presented in previous email ?
>> 

Re: Routing (was Re: Spectrum Components)

[Carlos Rovira]

Hi Piotr,

I used hashes with params, so that's completely fine and we should have it.
In fact, I think we already should have it since I'm seeing
"RoutToParameter" class right? Maybe Harbs should confirm this since he
implemented, and I just saw the class but still not use it.


El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Harbs,
>
> Agreed with that. We can rename them, but even in case of HashRouter - does
> exclude it ability to have parameters ? Does those parameters not exists in
> HasRouter as well. Is it not a common stuff no matter what kind of url it
> is ?
>
> niedz., 19 kwi 2020 o 15:52 Harbs  napisał(a):
>
> > After thinking about this some more, I’m thinking that Router should be
> > named and we should add another type of router for standard path routing.
> >
> > React calls them HashRouter and BrowserRouter. Maybe we should use the
> > same names…
> >
> > https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> <
> > https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> >
> >
> > > On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki  >
> > wrote:
> > >
> > > Hi Harbs,
> > >
> > > It sounds like you are asking me to check in onInit whether
> > > if(location.hash) exists then do something, but if doesn't exists check
> > url
> > > params. - I may understand it in a wrong way, but I think location.hash
> > may
> > > exists and location.search - where parameters are stored could exists
> > > equally.
> > >
> > > if(location.hash)
> > > {
> > >  hashChangeHandler();
> > > }
> > >
> > > if (location.search)
> > > {
> > >   parseParameters();
> > > }
> > >
> > > Am I missing something ?
> > >
> > > Thanks,
> > > Piotr
> > >
> > > pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
> > >
> > >> Whatever you think is fine by me.
> > >>
> > >> I don’t remember why I have "if(location.hash)”. It’s possible you can
> > get
> > >> rid of that conditional.
> > >>
> > >> It could be you can get rid of that and handle hashRecieved in a bead.
> > If
> > >> the hashReceived event has no hash you can then check the URL.You do
> > need
> > >> to make sure that you always get a stateChange event and don’t
> dispatch
> > it
> > >> twice.
> > >>
> > >> Feel free to play around with the code… ;-)
> > >>
> > >> Harbs
> > >>
> > >>> On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > >> wrote:
> > >>>
> > >>> I think it would be better to have it here in Router.
> > >>>
> > >>> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> > >>>
> >  Alternatively, you can subclass Router to support setting the
> > parameters
> >  in the onInit method.
> > 
> >  Not sure which of these is best.
> > 
> > > On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> > >
> > > Actually, it’s not going to work because the
> >  router.routeState.parameters will not be set.
> > >
> > > You will likely need to add code to set the
> > >> router.routeState.parameters
> >  using the part of the location after the question mark.
> > >
> > > The easiest way to do that would be to either:
> > > 1. Modify RouteToParameters.stateChanged to first check that there
> > is a
> >  parameters value and then set it if not.
> > > 2. Subclass RouteToParameters and override stateChanged to make
> that
> >  check first.
> > >
> > >> On Apr 17, 2020, at 10:29 AM, Harbs   >  harbs.li...@gmail.com>> wrote:
> > >>
> > >> I’m pretty sure it’ll work without the hash as well.
> > >>
> > >> Give it a try.
> > >>
> > >>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> >  piotrzarzyck...@gmail.com >
> wrote:
> > >>>
> > >>> Hi Harbs,
> > >>>
> > >>> Thanks for pointing me out, but this is still that Routing
> expects
> > me
> >  to
> > >>> use in url hashes - The question is - What if I can't use hashes,
> > but
> >  url
> > >>> looks like I have presented in previous email ?
> > >>>
> > >>> Thanks,
> > >>> Piotr
> > >>>
> > >>> pt., 17 kwi 2020 o 09:20 Harbs  >  harbs.li...@gmail.com>> napisał(a):
> > >>>
> >  This app uses both path based and query based routing:
> > 
> > 
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> > <
> >  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>
> <
> > 
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> > <
> >  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
> > 
> >  You can see how it’s done here:
> > 
> > 
> > >>
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >  <
> > 
> > >>
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > >
> >  <
> > 
> > 
> 

Re: Routing (was Re: Spectrum Components)

[Alex Harui]

I think there are apps that only use the hash, some that use only parameters, 
and some that will use both, so PAYG would not require the hash-only people to 
carry code for parameters and vice versa.

-Alex

On 4/19/20, 5:34 AM, "Piotr Zarzycki"  wrote:

Hi Alex,

Could you elaborate what do you mean exactly in that case saying PAYG?
Parameter parsing should be done in different version of Router ?

Thanks,
Piotr

pt., 17 kwi 2020 o 17:54 Alex Harui  napisał(a):

> Ideally, supporting the route information in parameters vs hash would be
> done in a PAYG way.
>
> AIUI, hash has to be used as the delimiter if you plan to change the route
> information within the application, otherwise the application will reload.
> IOW, if the user is going to navigate in the appiication and the route
> information is going to change as they navigate, hash should be used.  If,
> on the other hand, there are a bunch of links on a website to click and 
you
> end up on a "page", then URL parameters is probably ok.
>
> I don't understand the concern about the dev branch version.  The release
> branch for 0.9.7 has been cut.  Any changes that go in develop are going 
in
> the next release.  That's how the git branching model works.  You can make
> any change you want in the dev branch right now.  It just won't be in the
> 0.9.7 release unless the RM decides to cherry-pick it, which they should
> not unless it is really important.  What am I missing?
>
> -Alex
>
> On 4/17/20, 3:09 AM, "Harbs"  wrote:
>
> Whatever you think is fine by me.
>
> I don’t remember why I have "if(location.hash)”. It’s possible you can
> get rid of that conditional.
>
> It could be you can get rid of that and handle hashRecieved in a bead.
> If the hashReceived event has no hash you can then check the URL.You do
> need to make sure that you always get a stateChange event and don’t
> dispatch it twice.
>
> Feel free to play around with the code… ;-)
>
> Harbs
>
> > On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com> wrote:
> >
> > I think it would be better to have it here in Router.
> >
> > pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >
> >> Alternatively, you can subclass Router to support setting the
> parameters
> >> in the onInit method.
> >>
> >> Not sure which of these is best.
> >>
> >>> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >>>
> >>> Actually, it’s not going to work because the
> >> router.routeState.parameters will not be set.
> >>>
> >>> You will likely need to add code to set the
> router.routeState.parameters
> >> using the part of the location after the question mark.
> >>>
> >>> The easiest way to do that would be to either:
> >>> 1. Modify RouteToParameters.stateChanged to first check that there
> is a
> >> parameters value and then set it if not.
> >>> 2. Subclass RouteToParameters and override stateChanged to make
> that
> >> check first.
> >>>
>  On Apr 17, 2020, at 10:29 AM, Harbs   >> harbs.li...@gmail.com>> wrote:
> 
>  I’m pretty sure it’ll work without the hash as well.
> 
>  Give it a try.
> 
> > On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com >
> wrote:
> >
> > Hi Harbs,
> >
> > Thanks for pointing me out, but this is still that Routing
> expects me
> >> to
> > use in url hashes - The question is - What if I can't use
> hashes, but
> >> url
> > looks like I have presented in previous email ?
> >
> > Thanks,
> > Piotr
> >
> > pt., 17 kwi 2020 o 09:20 Harbs  >> harbs.li...@gmail.com>> napisał(a):
> >
> >> This app uses both path based and query based routing:
> >>
> >>
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C8b503852fe2b407798eb08d7e45df281%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637228964470465928sdata=vVYdOwC6mmZw%2FpSH6jGXfyS%2BhLbLCovT9laawtoQpU8%3Dreserved=0
> <
> >>
> 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Harbs,

Agreed with that. We can rename them, but even in case of HashRouter - does
exclude it ability to have parameters ? Does those parameters not exists in
HasRouter as well. Is it not a common stuff no matter what kind of url it
is ?

niedz., 19 kwi 2020 o 15:52 Harbs  napisał(a):

> After thinking about this some more, I’m thinking that Router should be
> named and we should add another type of router for standard path routing.
>
> React calls them HashRouter and BrowserRouter. Maybe we should use the
> same names…
>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter <
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter>
>
> > On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki 
> wrote:
> >
> > Hi Harbs,
> >
> > It sounds like you are asking me to check in onInit whether
> > if(location.hash) exists then do something, but if doesn't exists check
> url
> > params. - I may understand it in a wrong way, but I think location.hash
> may
> > exists and location.search - where parameters are stored could exists
> > equally.
> >
> > if(location.hash)
> > {
> >  hashChangeHandler();
> > }
> >
> > if (location.search)
> > {
> >   parseParameters();
> > }
> >
> > Am I missing something ?
> >
> > Thanks,
> > Piotr
> >
> > pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
> >
> >> Whatever you think is fine by me.
> >>
> >> I don’t remember why I have "if(location.hash)”. It’s possible you can
> get
> >> rid of that conditional.
> >>
> >> It could be you can get rid of that and handle hashRecieved in a bead.
> If
> >> the hashReceived event has no hash you can then check the URL.You do
> need
> >> to make sure that you always get a stateChange event and don’t dispatch
> it
> >> twice.
> >>
> >> Feel free to play around with the code… ;-)
> >>
> >> Harbs
> >>
> >>> On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >> wrote:
> >>>
> >>> I think it would be better to have it here in Router.
> >>>
> >>> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >>>
>  Alternatively, you can subclass Router to support setting the
> parameters
>  in the onInit method.
> 
>  Not sure which of these is best.
> 
> > On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >
> > Actually, it’s not going to work because the
>  router.routeState.parameters will not be set.
> >
> > You will likely need to add code to set the
> >> router.routeState.parameters
>  using the part of the location after the question mark.
> >
> > The easiest way to do that would be to either:
> > 1. Modify RouteToParameters.stateChanged to first check that there
> is a
>  parameters value and then set it if not.
> > 2. Subclass RouteToParameters and override stateChanged to make that
>  check first.
> >
> >> On Apr 17, 2020, at 10:29 AM, Harbs   harbs.li...@gmail.com>> wrote:
> >>
> >> I’m pretty sure it’ll work without the hash as well.
> >>
> >> Give it a try.
> >>
> >>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
>  piotrzarzyck...@gmail.com > wrote:
> >>>
> >>> Hi Harbs,
> >>>
> >>> Thanks for pointing me out, but this is still that Routing expects
> me
>  to
> >>> use in url hashes - The question is - What if I can't use hashes,
> but
>  url
> >>> looks like I have presented in previous email ?
> >>>
> >>> Thanks,
> >>> Piotr
> >>>
> >>> pt., 17 kwi 2020 o 09:20 Harbs   harbs.li...@gmail.com>> napisał(a):
> >>>
>  This app uses both path based and query based routing:
> 
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> <
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark> <
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> <
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
> 
>  You can see how it’s done here:
> 
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>  <
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
>  <
> 
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>  <
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
> >
> 
> > On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
>  piotrzarzyck...@gmail.com >
>  wrote:
> >
> > I'm still looking into the code and it looks like Routing
>  implemented now
> > is not doing what I would expected. Everything is based on "hash"
>  property
> > in "location". Instead I need something which is in "search" of

Re: Routing (was Re: Spectrum Components)

[Harbs]

It’s also interesting to see how Vue handles routing:
https://github.com/vuejs/vue-router/tree/dev/examples 


> On Apr 19, 2020, at 4:27 PM, Harbs  wrote:
> 
> After thinking about this some more, I’m thinking that Router should be named 
> and we should add another type of router for standard path routing.
> 
> React calls them HashRouter and BrowserRouter. Maybe we should use the same 
> names…
> 
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter 
> 
> 
>> On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki > > wrote:
>> 
>> Hi Harbs,
>> 
>> It sounds like you are asking me to check in onInit whether
>> if(location.hash) exists then do something, but if doesn't exists check url
>> params. - I may understand it in a wrong way, but I think location.hash may
>> exists and location.search - where parameters are stored could exists
>> equally.
>> 
>> if(location.hash)
>> {
>>  hashChangeHandler();
>> }
>> 
>> if (location.search)
>> {
>>   parseParameters();
>> }
>> 
>> Am I missing something ?
>> 
>> Thanks,
>> Piotr
>> 
>> pt., 17 kwi 2020 o 12:09 Harbs > > napisał(a):
>> 
>>> Whatever you think is fine by me.
>>> 
>>> I don’t remember why I have "if(location.hash)”. It’s possible you can get
>>> rid of that conditional.
>>> 
>>> It could be you can get rid of that and handle hashRecieved in a bead. If
>>> the hashReceived event has no hash you can then check the URL.You do need
>>> to make sure that you always get a stateChange event and don’t dispatch it
>>> twice.
>>> 
>>> Feel free to play around with the code… ;-)
>>> 
>>> Harbs
>>> 
 On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki >>> >
>>> wrote:
 
 I think it would be better to have it here in Router.
 
 pt., 17 kwi 2020 o 09:37 Harbs >>> > napisał(a):
 
> Alternatively, you can subclass Router to support setting the parameters
> in the onInit method.
> 
> Not sure which of these is best.
> 
>> On Apr 17, 2020, at 10:35 AM, Harbs > > wrote:
>> 
>> Actually, it’s not going to work because the
> router.routeState.parameters will not be set.
>> 
>> You will likely need to add code to set the
>>> router.routeState.parameters
> using the part of the location after the question mark.
>> 
>> The easiest way to do that would be to either:
>> 1. Modify RouteToParameters.stateChanged to first check that there is a
> parameters value and then set it if not.
>> 2. Subclass RouteToParameters and override stateChanged to make that
> check first.
>> 
>>> On Apr 17, 2020, at 10:29 AM, Harbs >>   harbs.li...@gmail.com >> wrote:
>>> 
>>> I’m pretty sure it’ll work without the hash as well.
>>> 
>>> Give it a try.
>>> 
 On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com  
> >> 
> wrote:
 
 Hi Harbs,
 
 Thanks for pointing me out, but this is still that Routing expects me
> to
 use in url hashes - The question is - What if I can't use hashes, but
> url
 looks like I have presented in previous email ?
 
 Thanks,
 Piotr
 
 pt., 17 kwi 2020 o 09:20 Harbs >>>   harbs.li...@gmail.com >> napisał(a):
 
> This app uses both path based and query based routing:
> 
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 
>  <
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 
> > <
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 
>  <
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 
> >>
> 
> You can see how it’s done here:
> 
> 
>>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>>>  
>>> 
> <
> 
>>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>> 
> <
> 
> 
>>> 

Re: Routing (was Re: Spectrum Components)

[Carlos Rovira]

Hi Harbs

+1

that has more sense. Maybe actual Router should be renamed to HashRouter
and  create a new BrowserRouter.
Since you created the first Router and Piotr is interested in applying to
his work, would be possible for both to work on that?
As I said, I'm fighting with other MD things but would want to use that as
well for in a future royale website

Thanks



El dom., 19 abr. 2020 a las 15:52, Harbs () escribió:

> After thinking about this some more, I’m thinking that Router should be
> named and we should add another type of router for standard path routing.
>
> React calls them HashRouter and BrowserRouter. Maybe we should use the
> same names…
>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter <
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter>
>
> > On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki 
> wrote:
> >
> > Hi Harbs,
> >
> > It sounds like you are asking me to check in onInit whether
> > if(location.hash) exists then do something, but if doesn't exists check
> url
> > params. - I may understand it in a wrong way, but I think location.hash
> may
> > exists and location.search - where parameters are stored could exists
> > equally.
> >
> > if(location.hash)
> > {
> >  hashChangeHandler();
> > }
> >
> > if (location.search)
> > {
> >   parseParameters();
> > }
> >
> > Am I missing something ?
> >
> > Thanks,
> > Piotr
> >
> > pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
> >
> >> Whatever you think is fine by me.
> >>
> >> I don’t remember why I have "if(location.hash)”. It’s possible you can
> get
> >> rid of that conditional.
> >>
> >> It could be you can get rid of that and handle hashRecieved in a bead.
> If
> >> the hashReceived event has no hash you can then check the URL.You do
> need
> >> to make sure that you always get a stateChange event and don’t dispatch
> it
> >> twice.
> >>
> >> Feel free to play around with the code… ;-)
> >>
> >> Harbs
> >>
> >>> On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >> wrote:
> >>>
> >>> I think it would be better to have it here in Router.
> >>>
> >>> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >>>
>  Alternatively, you can subclass Router to support setting the
> parameters
>  in the onInit method.
> 
>  Not sure which of these is best.
> 
> > On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >
> > Actually, it’s not going to work because the
>  router.routeState.parameters will not be set.
> >
> > You will likely need to add code to set the
> >> router.routeState.parameters
>  using the part of the location after the question mark.
> >
> > The easiest way to do that would be to either:
> > 1. Modify RouteToParameters.stateChanged to first check that there
> is a
>  parameters value and then set it if not.
> > 2. Subclass RouteToParameters and override stateChanged to make that
>  check first.
> >
> >> On Apr 17, 2020, at 10:29 AM, Harbs   harbs.li...@gmail.com>> wrote:
> >>
> >> I’m pretty sure it’ll work without the hash as well.
> >>
> >> Give it a try.
> >>
> >>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
>  piotrzarzyck...@gmail.com > wrote:
> >>>
> >>> Hi Harbs,
> >>>
> >>> Thanks for pointing me out, but this is still that Routing expects
> me
>  to
> >>> use in url hashes - The question is - What if I can't use hashes,
> but
>  url
> >>> looks like I have presented in previous email ?
> >>>
> >>> Thanks,
> >>> Piotr
> >>>
> >>> pt., 17 kwi 2020 o 09:20 Harbs   harbs.li...@gmail.com>> napisał(a):
> >>>
>  This app uses both path based and query based routing:
> 
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> <
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark> <
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> <
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
> 
>  You can see how it’s done here:
> 
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>  <
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
>  <
> 
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>  <
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
> >
> 
> > On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
>  piotrzarzyck...@gmail.com >
>  wrote:
> >
> > I'm still looking into the code and it looks like Routing
>  implemented now
> > is not doing what I 

Re: Routing (was Re: Spectrum Components)

[Harbs]

After thinking about this some more, I’m thinking that Router should be named 
and we should add another type of router for standard path routing.

React calls them HashRouter and BrowserRouter. Maybe we should use the same 
names…

https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter 


> On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki  wrote:
> 
> Hi Harbs,
> 
> It sounds like you are asking me to check in onInit whether
> if(location.hash) exists then do something, but if doesn't exists check url
> params. - I may understand it in a wrong way, but I think location.hash may
> exists and location.search - where parameters are stored could exists
> equally.
> 
> if(location.hash)
> {
>  hashChangeHandler();
> }
> 
> if (location.search)
> {
>   parseParameters();
> }
> 
> Am I missing something ?
> 
> Thanks,
> Piotr
> 
> pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
> 
>> Whatever you think is fine by me.
>> 
>> I don’t remember why I have "if(location.hash)”. It’s possible you can get
>> rid of that conditional.
>> 
>> It could be you can get rid of that and handle hashRecieved in a bead. If
>> the hashReceived event has no hash you can then check the URL.You do need
>> to make sure that you always get a stateChange event and don’t dispatch it
>> twice.
>> 
>> Feel free to play around with the code… ;-)
>> 
>> Harbs
>> 
>>> On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki 
>> wrote:
>>> 
>>> I think it would be better to have it here in Router.
>>> 
>>> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
>>> 
 Alternatively, you can subclass Router to support setting the parameters
 in the onInit method.
 
 Not sure which of these is best.
 
> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> 
> Actually, it’s not going to work because the
 router.routeState.parameters will not be set.
> 
> You will likely need to add code to set the
>> router.routeState.parameters
 using the part of the location after the question mark.
> 
> The easiest way to do that would be to either:
> 1. Modify RouteToParameters.stateChanged to first check that there is a
 parameters value and then set it if not.
> 2. Subclass RouteToParameters and override stateChanged to make that
 check first.
> 
>> On Apr 17, 2020, at 10:29 AM, Harbs >>> harbs.li...@gmail.com>> wrote:
>> 
>> I’m pretty sure it’ll work without the hash as well.
>> 
>> Give it a try.
>> 
>>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
 piotrzarzyck...@gmail.com > wrote:
>>> 
>>> Hi Harbs,
>>> 
>>> Thanks for pointing me out, but this is still that Routing expects me
 to
>>> use in url hashes - The question is - What if I can't use hashes, but
 url
>>> looks like I have presented in previous email ?
>>> 
>>> Thanks,
>>> Piotr
>>> 
>>> pt., 17 kwi 2020 o 09:20 Harbs >>> harbs.li...@gmail.com>> napisał(a):
>>> 
 This app uses both path based and query based routing:
 
 https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
 https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark> <
 https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
 https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
 
 You can see how it’s done here:
 
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
 <
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> 
 <
 
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
 <
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> 
> 
 
> On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
 piotrzarzyck...@gmail.com >
 wrote:
> 
> I'm still looking into the code and it looks like Routing
 implemented now
> is not doing what I would expected. Everything is based on "hash"
 property
> in "location". Instead I need something which is in "search" of
 location. I
> will wait for your thoughts before I do try to handle stuff on my
 end.
> 
> pt., 17 kwi 2020 o 08:30 Piotr Zarzycki >>> >
> napisał(a):
> 
>> Hi Guys,
>> 
>> I really thought that I will be able to use Router [1] based on
>> documentation and maybe eventually some look to the code [2] - to
 figure
>> out how things should be implemented. However it looks like non of
 the
>> existing stuff helps me to use in in 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Josh and Greg pointed into exactly the case which I have in our
application. Urls are controlled by server sight and I cannot change it, so
I rather need adjust how my application react towards different type of
urls which could be used, rather create specific for some views.

niedz., 19 kwi 2020 o 14:33 Piotr Zarzycki 
napisał(a):

> Hi Alex,
>
> Could you elaborate what do you mean exactly in that case saying PAYG?
> Parameter parsing should be done in different version of Router ?
>
> Thanks,
> Piotr
>
> pt., 17 kwi 2020 o 17:54 Alex Harui  napisał(a):
>
>> Ideally, supporting the route information in parameters vs hash would be
>> done in a PAYG way.
>>
>> AIUI, hash has to be used as the delimiter if you plan to change the
>> route information within the application, otherwise the application will
>> reload.  IOW, if the user is going to navigate in the appiication and the
>> route information is going to change as they navigate, hash should be
>> used.  If, on the other hand, there are a bunch of links on a website to
>> click and you end up on a "page", then URL parameters is probably ok.
>>
>> I don't understand the concern about the dev branch version.  The release
>> branch for 0.9.7 has been cut.  Any changes that go in develop are going in
>> the next release.  That's how the git branching model works.  You can make
>> any change you want in the dev branch right now.  It just won't be in the
>> 0.9.7 release unless the RM decides to cherry-pick it, which they should
>> not unless it is really important.  What am I missing?
>>
>> -Alex
>>
>> On 4/17/20, 3:09 AM, "Harbs"  wrote:
>>
>> Whatever you think is fine by me.
>>
>> I don’t remember why I have "if(location.hash)”. It’s possible you
>> can get rid of that conditional.
>>
>> It could be you can get rid of that and handle hashRecieved in a
>> bead. If the hashReceived event has no hash you can then check the URL.You
>> do need to make sure that you always get a stateChange event and don’t
>> dispatch it twice.
>>
>> Feel free to play around with the code… ;-)
>>
>> Harbs
>>
>> > On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com> wrote:
>> >
>> > I think it would be better to have it here in Router.
>> >
>> > pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
>> >
>> >> Alternatively, you can subclass Router to support setting the
>> parameters
>> >> in the onInit method.
>> >>
>> >> Not sure which of these is best.
>> >>
>> >>> On Apr 17, 2020, at 10:35 AM, Harbs 
>> wrote:
>> >>>
>> >>> Actually, it’s not going to work because the
>> >> router.routeState.parameters will not be set.
>> >>>
>> >>> You will likely need to add code to set the
>> router.routeState.parameters
>> >> using the part of the location after the question mark.
>> >>>
>> >>> The easiest way to do that would be to either:
>> >>> 1. Modify RouteToParameters.stateChanged to first check that
>> there is a
>> >> parameters value and then set it if not.
>> >>> 2. Subclass RouteToParameters and override stateChanged to make
>> that
>> >> check first.
>> >>>
>>  On Apr 17, 2020, at 10:29 AM, Harbs > > >> harbs.li...@gmail.com>> wrote:
>> 
>>  I’m pretty sure it’ll work without the hash as well.
>> 
>>  Give it a try.
>> 
>> > On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
>> >> piotrzarzyck...@gmail.com >
>> wrote:
>> >
>> > Hi Harbs,
>> >
>> > Thanks for pointing me out, but this is still that Routing
>> expects me
>> >> to
>> > use in url hashes - The question is - What if I can't use
>> hashes, but
>> >> url
>> > looks like I have presented in previous email ?
>> >
>> > Thanks,
>> > Piotr
>> >
>> > pt., 17 kwi 2020 o 09:20 Harbs > >> harbs.li...@gmail.com>> napisał(a):
>> >
>> >> This app uses both path based and query based routing:
>> >>
>> >>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3Dreserved=0
>> <
>> >>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3Dreserved=0>
>> <
>> >>
>> 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Hi Alex,

Could you elaborate what do you mean exactly in that case saying PAYG?
Parameter parsing should be done in different version of Router ?

Thanks,
Piotr

pt., 17 kwi 2020 o 17:54 Alex Harui  napisał(a):

> Ideally, supporting the route information in parameters vs hash would be
> done in a PAYG way.
>
> AIUI, hash has to be used as the delimiter if you plan to change the route
> information within the application, otherwise the application will reload.
> IOW, if the user is going to navigate in the appiication and the route
> information is going to change as they navigate, hash should be used.  If,
> on the other hand, there are a bunch of links on a website to click and you
> end up on a "page", then URL parameters is probably ok.
>
> I don't understand the concern about the dev branch version.  The release
> branch for 0.9.7 has been cut.  Any changes that go in develop are going in
> the next release.  That's how the git branching model works.  You can make
> any change you want in the dev branch right now.  It just won't be in the
> 0.9.7 release unless the RM decides to cherry-pick it, which they should
> not unless it is really important.  What am I missing?
>
> -Alex
>
> On 4/17/20, 3:09 AM, "Harbs"  wrote:
>
> Whatever you think is fine by me.
>
> I don’t remember why I have "if(location.hash)”. It’s possible you can
> get rid of that conditional.
>
> It could be you can get rid of that and handle hashRecieved in a bead.
> If the hashReceived event has no hash you can then check the URL.You do
> need to make sure that you always get a stateChange event and don’t
> dispatch it twice.
>
> Feel free to play around with the code… ;-)
>
> Harbs
>
> > On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com> wrote:
> >
> > I think it would be better to have it here in Router.
> >
> > pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >
> >> Alternatively, you can subclass Router to support setting the
> parameters
> >> in the onInit method.
> >>
> >> Not sure which of these is best.
> >>
> >>> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >>>
> >>> Actually, it’s not going to work because the
> >> router.routeState.parameters will not be set.
> >>>
> >>> You will likely need to add code to set the
> router.routeState.parameters
> >> using the part of the location after the question mark.
> >>>
> >>> The easiest way to do that would be to either:
> >>> 1. Modify RouteToParameters.stateChanged to first check that there
> is a
> >> parameters value and then set it if not.
> >>> 2. Subclass RouteToParameters and override stateChanged to make
> that
> >> check first.
> >>>
>  On Apr 17, 2020, at 10:29 AM, Harbs   >> harbs.li...@gmail.com>> wrote:
> 
>  I’m pretty sure it’ll work without the hash as well.
> 
>  Give it a try.
> 
> > On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com >
> wrote:
> >
> > Hi Harbs,
> >
> > Thanks for pointing me out, but this is still that Routing
> expects me
> >> to
> > use in url hashes - The question is - What if I can't use
> hashes, but
> >> url
> > looks like I have presented in previous email ?
> >
> > Thanks,
> > Piotr
> >
> > pt., 17 kwi 2020 o 09:20 Harbs  >> harbs.li...@gmail.com>> napisał(a):
> >
> >> This app uses both path based and query based routing:
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3Dreserved=0
> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3Dreserved=0>
> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3Dreserved=0
> <
> >>
> 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Hi Harbs,

It sounds like you are asking me to check in onInit whether
if(location.hash) exists then do something, but if doesn't exists check url
params. - I may understand it in a wrong way, but I think location.hash may
exists and location.search - where parameters are stored could exists
equally.

if(location.hash)
{
  hashChangeHandler();
}

if (location.search)
{
   parseParameters();
}

Am I missing something ?

Thanks,
Piotr

pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):

> Whatever you think is fine by me.
>
> I don’t remember why I have "if(location.hash)”. It’s possible you can get
> rid of that conditional.
>
> It could be you can get rid of that and handle hashRecieved in a bead. If
> the hashReceived event has no hash you can then check the URL.You do need
> to make sure that you always get a stateChange event and don’t dispatch it
> twice.
>
> Feel free to play around with the code… ;-)
>
> Harbs
>
> > On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki 
> wrote:
> >
> > I think it would be better to have it here in Router.
> >
> > pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >
> >> Alternatively, you can subclass Router to support setting the parameters
> >> in the onInit method.
> >>
> >> Not sure which of these is best.
> >>
> >>> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >>>
> >>> Actually, it’s not going to work because the
> >> router.routeState.parameters will not be set.
> >>>
> >>> You will likely need to add code to set the
> router.routeState.parameters
> >> using the part of the location after the question mark.
> >>>
> >>> The easiest way to do that would be to either:
> >>> 1. Modify RouteToParameters.stateChanged to first check that there is a
> >> parameters value and then set it if not.
> >>> 2. Subclass RouteToParameters and override stateChanged to make that
> >> check first.
> >>>
>  On Apr 17, 2020, at 10:29 AM, Harbs  >> harbs.li...@gmail.com>> wrote:
> 
>  I’m pretty sure it’ll work without the hash as well.
> 
>  Give it a try.
> 
> > On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com > wrote:
> >
> > Hi Harbs,
> >
> > Thanks for pointing me out, but this is still that Routing expects me
> >> to
> > use in url hashes - The question is - What if I can't use hashes, but
> >> url
> > looks like I have presented in previous email ?
> >
> > Thanks,
> > Piotr
> >
> > pt., 17 kwi 2020 o 09:20 Harbs  >> harbs.li...@gmail.com>> napisał(a):
> >
> >> This app uses both path based and query based routing:
> >>
> >> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
> >> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark> <
> >> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
> >> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
> >>
> >> You can see how it’s done here:
> >>
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >> <
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >>>
> >> <
> >>
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >> <
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >>>
> >>>
> >>
> >>> On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com >
> >> wrote:
> >>>
> >>> I'm still looking into the code and it looks like Routing
> >> implemented now
> >>> is not doing what I would expected. Everything is based on "hash"
> >> property
> >>> in "location". Instead I need something which is in "search" of
> >> location. I
> >>> will wait for your thoughts before I do try to handle stuff on my
> >> end.
> >>>
> >>> pt., 17 kwi 2020 o 08:30 Piotr Zarzycki  >> >
> >>> napisał(a):
> >>>
>  Hi Guys,
> 
>  I really thought that I will be able to use Router [1] based on
>  documentation and maybe eventually some look to the code [2] - to
> >> figure
>  out how things should be implemented. However it looks like non of
> >> the
>  existing stuff helps me to use in in real world application at
> all.
> >> I
> >> would
>  like to throw a simple question.
> 
>  I would like to "answer" in my application to following url, catch
> >> params
>  and do some actions:
> 
> 
> >> https://mydomain.com/somefolder/index.html?target=somevalue= <
> >> https://mydomain.com/somefolder/index.html?target=somevalue=>
>  <
> >>
> >>
> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
> >> <
> >>
> 

Re: Routing (was Re: Spectrum Components)

[Carlos Rovira]

Hi Josh,

many thanks for exposing this, I was not aware of that and I think that's
very important for use Routing the right way.
So for what I understand if user does not have server they need to rely on
hashes, but if a server is available you can use full urls. I think we
should abstract this to the Royale Route components. Maybe @Harbs
 could do the right way since he designed that part.

I'm working on experiment with a Royale app for the website. If that
experiment turns to be a real option to switch from wordpress, I'd like
(and need) to use this on website to maintain the actual permalinks without
hashes

Thanks!



El sáb., 18 abr. 2020 a las 0:31, Greg Dove ()
escribió:

> Thanks Josh, good to know. I think I got close to expressing that with 'the
> initial path needs to be handled by the server no matter what it is. It may
> not do anything different other than to serve the same content regardless
> of the path'
>
> But your example with .htaccess is a much more helpful representation of
> that - I will keep that in my local references :)
>
>
>
> On Sat, Apr 18, 2020 at 10:21 AM Josh Tynjala 
> wrote:
>
> > Yes, your understanding is correct. The HTML History API is not limited
> to
> > the hash, and it can update other parts of the URL without reloading the
> > whole page. However, if you are not using a hash, then your server may
> need
> > some extra configuration to understand which URLs should be mapped to
> your
> > application's main HTML file.
> >
> > For example, I have an application at
> > https://feathersui.com/samples/haxe-openfl/components-explorer
> >
> > If you click the Asset Loader list item, it navigates to a new view, and
> > the URL changes to
> >
> https://feathersui.com/samples/haxe-openfl/components-explorer/asset-loader
> > instead. This is the same instance of the application that was initially
> > loaded. It only changes the URL.
> >
> > If you navigate directly to
> >
> https://feathersui.com/samples/haxe-openfl/components-explorer/asset-loader
> > in a new window, it loads the correct view too. This required configuring
> > my Apache server with a .htaccess file. Other servers will have a
> different
> > way to configure this behavior.
> >
> > Here's my .htaccess file:
> >
> > RewriteBase /samples/haxe-openfl/components-explorer/
> > RewriteCond %{HTTPS} off
> > RewriteRule ^/?(.*)
> > https://%{SERVER_NAME}/samples/haxe-openfl/components-explorer/$1
> > [R,L]
> > RewriteCond %{REQUEST_FILENAME} !-f
> > RewriteCond %{REQUEST_FILENAME} !-d
> > RewriteRule . /samples/haxe-openfl/components-explorer/ [L]
> >
> > It basically says that anything at components-explorer or deeper is part
> of
> > the same application, so even if the browser requests something like
> > /samples/haxe-openfl/components-explorer/asset-loader, always serve
> > /samples/haxe-openfl/components-explorer (unless a file with the exact
> > requested name actually exists, which allows loading images or
> > stylesheets). When the page loads, the JS checks the URL to determine
> which
> > view should be initially loaded.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Fri, Apr 17, 2020 at 2:53 PM Greg Dove  wrote:
> >
> > >  'AIUI, hash has to be used as the delimiter if you plan to change the
> > > route information within the application, otherwise the application
> will
> > > reload.'
> > >
> > > I am pretty sure that is no longer the case.  HTML5 support for history
> > > changes it not like the old days and there is good native browser
> support
> > > for this I think. I have certainly worked on React apps with Router
> > support
> > > that change the full path without reloading the page. I think the main
> > > thing is that if the path parts represent the current state of the app,
> > > then the initial path needs to be handled by the server no matter what
> it
> > > is. It may not do anything different other than to serve the same
> content
> > > regardless of the path. The JS app can possibly retrieve its serialized
> > > previous state from the localStorage based on the intiial path elements
> > or
> > > make remote separate api requests that are perhaps dependent on the
> > startup
> > > path elements, and it is not uncommon to continue to update the browser
> > > history with full path representations of subsequent api requests that
> > > don't rely on hashes.
> > > I might be wrong about that because it has been a while since I worked
> on
> > > something that was doing this, but I do recall thinking 'this is so
> much
> > > better than it used to be'.
> > >
> > >
> > > On Sat, Apr 18, 2020 at 3:54 AM Alex Harui 
> > > wrote:
> > >
> > > > Ideally, supporting the route information in parameters vs hash would
> > be
> > > > done in a PAYG way.
> > > >
> > > > AIUI, hash has to be used as the delimiter if you plan to change the
> > > route
> > > > information within the application, otherwise the application will
> > > reload.
> > > > IOW, if the user is 

Re: Routing (was Re: Spectrum Components)

[Greg Dove]

Thanks Josh, good to know. I think I got close to expressing that with 'the
initial path needs to be handled by the server no matter what it is. It may
not do anything different other than to serve the same content regardless
of the path'

But your example with .htaccess is a much more helpful representation of
that - I will keep that in my local references :)



On Sat, Apr 18, 2020 at 10:21 AM Josh Tynjala 
wrote:

> Yes, your understanding is correct. The HTML History API is not limited to
> the hash, and it can update other parts of the URL without reloading the
> whole page. However, if you are not using a hash, then your server may need
> some extra configuration to understand which URLs should be mapped to your
> application's main HTML file.
>
> For example, I have an application at
> https://feathersui.com/samples/haxe-openfl/components-explorer
>
> If you click the Asset Loader list item, it navigates to a new view, and
> the URL changes to
> https://feathersui.com/samples/haxe-openfl/components-explorer/asset-loader
> instead. This is the same instance of the application that was initially
> loaded. It only changes the URL.
>
> If you navigate directly to
> https://feathersui.com/samples/haxe-openfl/components-explorer/asset-loader
> in a new window, it loads the correct view too. This required configuring
> my Apache server with a .htaccess file. Other servers will have a different
> way to configure this behavior.
>
> Here's my .htaccess file:
>
> RewriteBase /samples/haxe-openfl/components-explorer/
> RewriteCond %{HTTPS} off
> RewriteRule ^/?(.*)
> https://%{SERVER_NAME}/samples/haxe-openfl/components-explorer/$1
> [R,L]
> RewriteCond %{REQUEST_FILENAME} !-f
> RewriteCond %{REQUEST_FILENAME} !-d
> RewriteRule . /samples/haxe-openfl/components-explorer/ [L]
>
> It basically says that anything at components-explorer or deeper is part of
> the same application, so even if the browser requests something like
> /samples/haxe-openfl/components-explorer/asset-loader, always serve
> /samples/haxe-openfl/components-explorer (unless a file with the exact
> requested name actually exists, which allows loading images or
> stylesheets). When the page loads, the JS checks the URL to determine which
> view should be initially loaded.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Fri, Apr 17, 2020 at 2:53 PM Greg Dove  wrote:
>
> >  'AIUI, hash has to be used as the delimiter if you plan to change the
> > route information within the application, otherwise the application will
> > reload.'
> >
> > I am pretty sure that is no longer the case.  HTML5 support for history
> > changes it not like the old days and there is good native browser support
> > for this I think. I have certainly worked on React apps with Router
> support
> > that change the full path without reloading the page. I think the main
> > thing is that if the path parts represent the current state of the app,
> > then the initial path needs to be handled by the server no matter what it
> > is. It may not do anything different other than to serve the same content
> > regardless of the path. The JS app can possibly retrieve its serialized
> > previous state from the localStorage based on the intiial path elements
> or
> > make remote separate api requests that are perhaps dependent on the
> startup
> > path elements, and it is not uncommon to continue to update the browser
> > history with full path representations of subsequent api requests that
> > don't rely on hashes.
> > I might be wrong about that because it has been a while since I worked on
> > something that was doing this, but I do recall thinking 'this is so much
> > better than it used to be'.
> >
> >
> > On Sat, Apr 18, 2020 at 3:54 AM Alex Harui 
> > wrote:
> >
> > > Ideally, supporting the route information in parameters vs hash would
> be
> > > done in a PAYG way.
> > >
> > > AIUI, hash has to be used as the delimiter if you plan to change the
> > route
> > > information within the application, otherwise the application will
> > reload.
> > > IOW, if the user is going to navigate in the appiication and the route
> > > information is going to change as they navigate, hash should be used.
> > If,
> > > on the other hand, there are a bunch of links on a website to click and
> > you
> > > end up on a "page", then URL parameters is probably ok.
> > >
> > > I don't understand the concern about the dev branch version.  The
> release
> > > branch for 0.9.7 has been cut.  Any changes that go in develop are
> going
> > in
> > > the next release.  That's how the git branching model works.  You can
> > make
> > > any change you want in the dev branch right now.  It just won't be in
> the
> > > 0.9.7 release unless the RM decides to cherry-pick it, which they
> should
> > > not unless it is really important.  What am I missing?
> > >
> > > -Alex
> > >
> > > On 4/17/20, 3:09 AM, "Harbs"  wrote:
> > >
> > > Whatever you think is fine by me.
> > >
> > > I 

Re: Routing (was Re: Spectrum Components)

[Josh Tynjala]

Yes, your understanding is correct. The HTML History API is not limited to
the hash, and it can update other parts of the URL without reloading the
whole page. However, if you are not using a hash, then your server may need
some extra configuration to understand which URLs should be mapped to your
application's main HTML file.

For example, I have an application at
https://feathersui.com/samples/haxe-openfl/components-explorer

If you click the Asset Loader list item, it navigates to a new view, and
the URL changes to
https://feathersui.com/samples/haxe-openfl/components-explorer/asset-loader
instead. This is the same instance of the application that was initially
loaded. It only changes the URL.

If you navigate directly to
https://feathersui.com/samples/haxe-openfl/components-explorer/asset-loader
in a new window, it loads the correct view too. This required configuring
my Apache server with a .htaccess file. Other servers will have a different
way to configure this behavior.

Here's my .htaccess file:

RewriteBase /samples/haxe-openfl/components-explorer/
RewriteCond %{HTTPS} off
RewriteRule ^/?(.*)
https://%{SERVER_NAME}/samples/haxe-openfl/components-explorer/$1
[R,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /samples/haxe-openfl/components-explorer/ [L]

It basically says that anything at components-explorer or deeper is part of
the same application, so even if the browser requests something like
/samples/haxe-openfl/components-explorer/asset-loader, always serve
/samples/haxe-openfl/components-explorer (unless a file with the exact
requested name actually exists, which allows loading images or
stylesheets). When the page loads, the JS checks the URL to determine which
view should be initially loaded.

--
Josh Tynjala
Bowler Hat LLC 


On Fri, Apr 17, 2020 at 2:53 PM Greg Dove  wrote:

>  'AIUI, hash has to be used as the delimiter if you plan to change the
> route information within the application, otherwise the application will
> reload.'
>
> I am pretty sure that is no longer the case.  HTML5 support for history
> changes it not like the old days and there is good native browser support
> for this I think. I have certainly worked on React apps with Router support
> that change the full path without reloading the page. I think the main
> thing is that if the path parts represent the current state of the app,
> then the initial path needs to be handled by the server no matter what it
> is. It may not do anything different other than to serve the same content
> regardless of the path. The JS app can possibly retrieve its serialized
> previous state from the localStorage based on the intiial path elements or
> make remote separate api requests that are perhaps dependent on the startup
> path elements, and it is not uncommon to continue to update the browser
> history with full path representations of subsequent api requests that
> don't rely on hashes.
> I might be wrong about that because it has been a while since I worked on
> something that was doing this, but I do recall thinking 'this is so much
> better than it used to be'.
>
>
> On Sat, Apr 18, 2020 at 3:54 AM Alex Harui 
> wrote:
>
> > Ideally, supporting the route information in parameters vs hash would be
> > done in a PAYG way.
> >
> > AIUI, hash has to be used as the delimiter if you plan to change the
> route
> > information within the application, otherwise the application will
> reload.
> > IOW, if the user is going to navigate in the appiication and the route
> > information is going to change as they navigate, hash should be used.
> If,
> > on the other hand, there are a bunch of links on a website to click and
> you
> > end up on a "page", then URL parameters is probably ok.
> >
> > I don't understand the concern about the dev branch version.  The release
> > branch for 0.9.7 has been cut.  Any changes that go in develop are going
> in
> > the next release.  That's how the git branching model works.  You can
> make
> > any change you want in the dev branch right now.  It just won't be in the
> > 0.9.7 release unless the RM decides to cherry-pick it, which they should
> > not unless it is really important.  What am I missing?
> >
> > -Alex
> >
> > On 4/17/20, 3:09 AM, "Harbs"  wrote:
> >
> > Whatever you think is fine by me.
> >
> > I don’t remember why I have "if(location.hash)”. It’s possible you
> can
> > get rid of that conditional.
> >
> > It could be you can get rid of that and handle hashRecieved in a
> bead.
> > If the hashReceived event has no hash you can then check the URL.You do
> > need to make sure that you always get a stateChange event and don’t
> > dispatch it twice.
> >
> > Feel free to play around with the code… ;-)
> >
> > Harbs
> >
> > > On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com> wrote:
> > >
> > > I think it would be better to have it here in Router.
> > >
> > > pt., 17 

Re: Routing (was Re: Spectrum Components)

[Greg Dove]

 'AIUI, hash has to be used as the delimiter if you plan to change the
route information within the application, otherwise the application will
reload.'

I am pretty sure that is no longer the case.  HTML5 support for history
changes it not like the old days and there is good native browser support
for this I think. I have certainly worked on React apps with Router support
that change the full path without reloading the page. I think the main
thing is that if the path parts represent the current state of the app,
then the initial path needs to be handled by the server no matter what it
is. It may not do anything different other than to serve the same content
regardless of the path. The JS app can possibly retrieve its serialized
previous state from the localStorage based on the intiial path elements or
make remote separate api requests that are perhaps dependent on the startup
path elements, and it is not uncommon to continue to update the browser
history with full path representations of subsequent api requests that
don't rely on hashes.
I might be wrong about that because it has been a while since I worked on
something that was doing this, but I do recall thinking 'this is so much
better than it used to be'.


On Sat, Apr 18, 2020 at 3:54 AM Alex Harui  wrote:

> Ideally, supporting the route information in parameters vs hash would be
> done in a PAYG way.
>
> AIUI, hash has to be used as the delimiter if you plan to change the route
> information within the application, otherwise the application will reload.
> IOW, if the user is going to navigate in the appiication and the route
> information is going to change as they navigate, hash should be used.  If,
> on the other hand, there are a bunch of links on a website to click and you
> end up on a "page", then URL parameters is probably ok.
>
> I don't understand the concern about the dev branch version.  The release
> branch for 0.9.7 has been cut.  Any changes that go in develop are going in
> the next release.  That's how the git branching model works.  You can make
> any change you want in the dev branch right now.  It just won't be in the
> 0.9.7 release unless the RM decides to cherry-pick it, which they should
> not unless it is really important.  What am I missing?
>
> -Alex
>
> On 4/17/20, 3:09 AM, "Harbs"  wrote:
>
> Whatever you think is fine by me.
>
> I don’t remember why I have "if(location.hash)”. It’s possible you can
> get rid of that conditional.
>
> It could be you can get rid of that and handle hashRecieved in a bead.
> If the hashReceived event has no hash you can then check the URL.You do
> need to make sure that you always get a stateChange event and don’t
> dispatch it twice.
>
> Feel free to play around with the code… ;-)
>
> Harbs
>
> > On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com> wrote:
> >
> > I think it would be better to have it here in Router.
> >
> > pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >
> >> Alternatively, you can subclass Router to support setting the
> parameters
> >> in the onInit method.
> >>
> >> Not sure which of these is best.
> >>
> >>> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >>>
> >>> Actually, it’s not going to work because the
> >> router.routeState.parameters will not be set.
> >>>
> >>> You will likely need to add code to set the
> router.routeState.parameters
> >> using the part of the location after the question mark.
> >>>
> >>> The easiest way to do that would be to either:
> >>> 1. Modify RouteToParameters.stateChanged to first check that there
> is a
> >> parameters value and then set it if not.
> >>> 2. Subclass RouteToParameters and override stateChanged to make
> that
> >> check first.
> >>>
>  On Apr 17, 2020, at 10:29 AM, Harbs   >> harbs.li...@gmail.com>> wrote:
> 
>  I’m pretty sure it’ll work without the hash as well.
> 
>  Give it a try.
> 
> > On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com >
> wrote:
> >
> > Hi Harbs,
> >
> > Thanks for pointing me out, but this is still that Routing
> expects me
> >> to
> > use in url hashes - The question is - What if I can't use
> hashes, but
> >> url
> > looks like I have presented in previous email ?
> >
> > Thanks,
> > Piotr
> >
> > pt., 17 kwi 2020 o 09:20 Harbs  >> harbs.li...@gmail.com>> napisał(a):
> >
> >> This app uses both path based and query based routing:
> >>
> >>
> 

Re: about current framework release (was Re: Routing (was Re: Spectrum Components))

[Carlos Rovira]

Hi Alex,

I'm just exposing that in the other repos there was various tries and
reverts. I was expecting the same here. If you are getting enough progress
to get the release in few hours, that's great. But maybe exposing you got
all working to finish the release and send an email to the list will be
just fine as a courtesy for the rest of the team (not just me).

The fact is that I fixed some things in Jewel scrollToIndex last night and
then you got to step 9, but seems there was a build problem catched by
Yishay with an import left in Jewel. So that will make the release fail for
sure.

A part from that, not me, but others could need to add things...or I could
be wrong. I must say I don't need to add anything myself. So from my
perspective you can go and finish as you prefer. Just thinking on others,
not me :)







El vie., 17 abr. 2020 a las 18:46, Alex Harui ()
escribió:

> Hi Carlos,
>
> First you are complaining that I was not making enough progress on the
> release.  Then there have clearly been Release_Step emails this week and
> you are now claiming I did not give you enough warning?
>
> -Alex
>
> On 4/17/20, 9:38 AM, "Carlos Rovira"  wrote:
>
> Hi Alex,
>
> a part from the issue with version bumped, I thought that you were
> testing
> and changing, and this could be just a test as done in compiler.
> If this is the real release, great. But in that case, I think you
> should
> cherry pick my latest commit removing a class (scrollToIndex) since
> right
> now Jewel is broken. I think others could need to add something to
> enter
> the release as we did other times, if so maybe just asking to people if
> want for a last call to add something would be good.
>
> Thanks
>
> El vie., 17 abr. 2020 a las 17:54, Alex Harui
> ()
> escribió:
>
> > Ideally, supporting the route information in parameters vs hash
> would be
> > done in a PAYG way.
> >
> > AIUI, hash has to be used as the delimiter if you plan to change the
> route
> > information within the application, otherwise the application will
> reload.
> > IOW, if the user is going to navigate in the appiication and the
> route
> > information is going to change as they navigate, hash should be
> used.  If,
> > on the other hand, there are a bunch of links on a website to click
> and you
> > end up on a "page", then URL parameters is probably ok.
> >
> > I don't understand the concern about the dev branch version.  The
> release
> > branch for 0.9.7 has been cut.  Any changes that go in develop are
> going in
> > the next release.  That's how the git branching model works.  You
> can make
> > any change you want in the dev branch right now.  It just won't be
> in the
> > 0.9.7 release unless the RM decides to cherry-pick it, which they
> should
> > not unless it is really important.  What am I missing?
> >
> > -Alex
> >
> > On 4/17/20, 3:09 AM, "Harbs"  wrote:
> >
> > Whatever you think is fine by me.
> >
> > I don’t remember why I have "if(location.hash)”. It’s possible
> you can
> > get rid of that conditional.
> >
> > It could be you can get rid of that and handle hashRecieved in a
> bead.
> > If the hashReceived event has no hash you can then check the URL.You
> do
> > need to make sure that you always get a stateChange event and don’t
> > dispatch it twice.
> >
> > Feel free to play around with the code… ;-)
> >
> > Harbs
> >
> > > On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com> wrote:
> > >
> > > I think it would be better to have it here in Router.
> > >
> > > pt., 17 kwi 2020 o 09:37 Harbs 
> napisał(a):
> > >
> > >> Alternatively, you can subclass Router to support setting the
> > parameters
> > >> in the onInit method.
> > >>
> > >> Not sure which of these is best.
> > >>
> > >>> On Apr 17, 2020, at 10:35 AM, Harbs 
> wrote:
> > >>>
> > >>> Actually, it’s not going to work because the
> > >> router.routeState.parameters will not be set.
> > >>>
> > >>> You will likely need to add code to set the
> > router.routeState.parameters
> > >> using the part of the location after the question mark.
> > >>>
> > >>> The easiest way to do that would be to either:
> > >>> 1. Modify RouteToParameters.stateChanged to first check that
> there
> > is a
> > >> parameters value and then set it if not.
> > >>> 2. Subclass RouteToParameters and override stateChanged to
> make
> > that
> > >> check first.
> > >>>
> >  On Apr 17, 2020, at 10:29 AM, Harbs  >  > >> harbs.li...@gmail.com>> wrote:
> > 
> >  I’m pretty sure it’ll work without the hash as well.
> > 

Re: about current framework release (was Re: Routing (was Re: Spectrum Components))

[Alex Harui]

Hi Carlos,

First you are complaining that I was not making enough progress on the release. 
 Then there have clearly been Release_Step emails this week and you are now 
claiming I did not give you enough warning?

-Alex

On 4/17/20, 9:38 AM, "Carlos Rovira"  wrote:

Hi Alex,

a part from the issue with version bumped, I thought that you were testing
and changing, and this could be just a test as done in compiler.
If this is the real release, great. But in that case, I think you should
cherry pick my latest commit removing a class (scrollToIndex) since right
now Jewel is broken. I think others could need to add something to enter
the release as we did other times, if so maybe just asking to people if
want for a last call to add something would be good.

Thanks

El vie., 17 abr. 2020 a las 17:54, Alex Harui ()
escribió:

> Ideally, supporting the route information in parameters vs hash would be
> done in a PAYG way.
>
> AIUI, hash has to be used as the delimiter if you plan to change the route
> information within the application, otherwise the application will reload.
> IOW, if the user is going to navigate in the appiication and the route
> information is going to change as they navigate, hash should be used.  If,
> on the other hand, there are a bunch of links on a website to click and 
you
> end up on a "page", then URL parameters is probably ok.
>
> I don't understand the concern about the dev branch version.  The release
> branch for 0.9.7 has been cut.  Any changes that go in develop are going 
in
> the next release.  That's how the git branching model works.  You can make
> any change you want in the dev branch right now.  It just won't be in the
> 0.9.7 release unless the RM decides to cherry-pick it, which they should
> not unless it is really important.  What am I missing?
>
> -Alex
>
> On 4/17/20, 3:09 AM, "Harbs"  wrote:
>
> Whatever you think is fine by me.
>
> I don’t remember why I have "if(location.hash)”. It’s possible you can
> get rid of that conditional.
>
> It could be you can get rid of that and handle hashRecieved in a bead.
> If the hashReceived event has no hash you can then check the URL.You do
> need to make sure that you always get a stateChange event and don’t
> dispatch it twice.
>
> Feel free to play around with the code… ;-)
>
> Harbs
>
> > On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com> wrote:
> >
> > I think it would be better to have it here in Router.
> >
> > pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >
> >> Alternatively, you can subclass Router to support setting the
> parameters
> >> in the onInit method.
> >>
> >> Not sure which of these is best.
> >>
> >>> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >>>
> >>> Actually, it’s not going to work because the
> >> router.routeState.parameters will not be set.
> >>>
> >>> You will likely need to add code to set the
> router.routeState.parameters
> >> using the part of the location after the question mark.
> >>>
> >>> The easiest way to do that would be to either:
> >>> 1. Modify RouteToParameters.stateChanged to first check that there
> is a
> >> parameters value and then set it if not.
> >>> 2. Subclass RouteToParameters and override stateChanged to make
> that
> >> check first.
> >>>
>  On Apr 17, 2020, at 10:29 AM, Harbs   >> harbs.li...@gmail.com>> wrote:
> 
>  I’m pretty sure it’ll work without the hash as well.
> 
>  Give it a try.
> 
> > On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com >
> wrote:
> >
> > Hi Harbs,
> >
> > Thanks for pointing me out, but this is still that Routing
> expects me
> >> to
> > use in url hashes - The question is - What if I can't use
> hashes, but
> >> url
> > looks like I have presented in previous email ?
> >
> > Thanks,
> > Piotr
> >
> > pt., 17 kwi 2020 o 09:20 Harbs  >> harbs.li...@gmail.com>> napisał(a):
> >
> >> This app uses both path based and query based routing:
> >>
> >>
> 

about current framework release (was Re: Routing (was Re: Spectrum Components))

[Carlos Rovira]

Hi Alex,

a part from the issue with version bumped, I thought that you were testing
and changing, and this could be just a test as done in compiler.
If this is the real release, great. But in that case, I think you should
cherry pick my latest commit removing a class (scrollToIndex) since right
now Jewel is broken. I think others could need to add something to enter
the release as we did other times, if so maybe just asking to people if
want for a last call to add something would be good.

Thanks

El vie., 17 abr. 2020 a las 17:54, Alex Harui ()
escribió:

> Ideally, supporting the route information in parameters vs hash would be
> done in a PAYG way.
>
> AIUI, hash has to be used as the delimiter if you plan to change the route
> information within the application, otherwise the application will reload.
> IOW, if the user is going to navigate in the appiication and the route
> information is going to change as they navigate, hash should be used.  If,
> on the other hand, there are a bunch of links on a website to click and you
> end up on a "page", then URL parameters is probably ok.
>
> I don't understand the concern about the dev branch version.  The release
> branch for 0.9.7 has been cut.  Any changes that go in develop are going in
> the next release.  That's how the git branching model works.  You can make
> any change you want in the dev branch right now.  It just won't be in the
> 0.9.7 release unless the RM decides to cherry-pick it, which they should
> not unless it is really important.  What am I missing?
>
> -Alex
>
> On 4/17/20, 3:09 AM, "Harbs"  wrote:
>
> Whatever you think is fine by me.
>
> I don’t remember why I have "if(location.hash)”. It’s possible you can
> get rid of that conditional.
>
> It could be you can get rid of that and handle hashRecieved in a bead.
> If the hashReceived event has no hash you can then check the URL.You do
> need to make sure that you always get a stateChange event and don’t
> dispatch it twice.
>
> Feel free to play around with the code… ;-)
>
> Harbs
>
> > On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com> wrote:
> >
> > I think it would be better to have it here in Router.
> >
> > pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >
> >> Alternatively, you can subclass Router to support setting the
> parameters
> >> in the onInit method.
> >>
> >> Not sure which of these is best.
> >>
> >>> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >>>
> >>> Actually, it’s not going to work because the
> >> router.routeState.parameters will not be set.
> >>>
> >>> You will likely need to add code to set the
> router.routeState.parameters
> >> using the part of the location after the question mark.
> >>>
> >>> The easiest way to do that would be to either:
> >>> 1. Modify RouteToParameters.stateChanged to first check that there
> is a
> >> parameters value and then set it if not.
> >>> 2. Subclass RouteToParameters and override stateChanged to make
> that
> >> check first.
> >>>
>  On Apr 17, 2020, at 10:29 AM, Harbs   >> harbs.li...@gmail.com>> wrote:
> 
>  I’m pretty sure it’ll work without the hash as well.
> 
>  Give it a try.
> 
> > On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com >
> wrote:
> >
> > Hi Harbs,
> >
> > Thanks for pointing me out, but this is still that Routing
> expects me
> >> to
> > use in url hashes - The question is - What if I can't use
> hashes, but
> >> url
> > looks like I have presented in previous email ?
> >
> > Thanks,
> > Piotr
> >
> > pt., 17 kwi 2020 o 09:20 Harbs  >> harbs.li...@gmail.com>> napisał(a):
> >
> >> This app uses both path based and query based routing:
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3Dreserved=0
> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3Dreserved=0>
> <
> >>
> 

Re: Routing (was Re: Spectrum Components)

[Alex Harui]

Ideally, supporting the route information in parameters vs hash would be done 
in a PAYG way.

AIUI, hash has to be used as the delimiter if you plan to change the route 
information within the application, otherwise the application will reload.  
IOW, if the user is going to navigate in the appiication and the route 
information is going to change as they navigate, hash should be used.  If, on 
the other hand, there are a bunch of links on a website to click and you end up 
on a "page", then URL parameters is probably ok.

I don't understand the concern about the dev branch version.  The release 
branch for 0.9.7 has been cut.  Any changes that go in develop are going in the 
next release.  That's how the git branching model works.  You can make any 
change you want in the dev branch right now.  It just won't be in the 0.9.7 
release unless the RM decides to cherry-pick it, which they should not unless 
it is really important.  What am I missing?

-Alex

On 4/17/20, 3:09 AM, "Harbs"  wrote:

Whatever you think is fine by me.

I don’t remember why I have "if(location.hash)”. It’s possible you can get 
rid of that conditional.

It could be you can get rid of that and handle hashRecieved in a bead. If 
the hashReceived event has no hash you can then check the URL.You do need to 
make sure that you always get a stateChange event and don’t dispatch it twice.

Feel free to play around with the code… ;-)

Harbs

> On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki  
wrote:
> 
> I think it would be better to have it here in Router.
> 
> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> 
>> Alternatively, you can subclass Router to support setting the parameters
>> in the onInit method.
>> 
>> Not sure which of these is best.
>> 
>>> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
>>> 
>>> Actually, it’s not going to work because the
>> router.routeState.parameters will not be set.
>>> 
>>> You will likely need to add code to set the router.routeState.parameters
>> using the part of the location after the question mark.
>>> 
>>> The easiest way to do that would be to either:
>>> 1. Modify RouteToParameters.stateChanged to first check that there is a
>> parameters value and then set it if not.
>>> 2. Subclass RouteToParameters and override stateChanged to make that
>> check first.
>>> 
 On Apr 17, 2020, at 10:29 AM, Harbs > harbs.li...@gmail.com>> wrote:
 
 I’m pretty sure it’ll work without the hash as well.
 
 Give it a try.
 
> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com > wrote:
> 
> Hi Harbs,
> 
> Thanks for pointing me out, but this is still that Routing expects me
>> to
> use in url hashes - The question is - What if I can't use hashes, but
>> url
> looks like I have presented in previous email ?
> 
> Thanks,
> Piotr
> 
> pt., 17 kwi 2020 o 09:20 Harbs > harbs.li...@gmail.com>> napisał(a):
> 
>> This app uses both path based and query based routing:
>> 
>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3Dreserved=0
 <
>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3Dreserved=0>
 <
>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3Dreserved=0
 <
>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3Dreserved=0>>
>> 
>> You can see how it’s done here:
>> 
>> 

Re: Routing (was Re: Spectrum Components)

[Harbs]

Whatever you think is fine by me.

I don’t remember why I have "if(location.hash)”. It’s possible you can get rid 
of that conditional.

It could be you can get rid of that and handle hashRecieved in a bead. If the 
hashReceived event has no hash you can then check the URL.You do need to make 
sure that you always get a stateChange event and don’t dispatch it twice.

Feel free to play around with the code… ;-)

Harbs

> On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki  
> wrote:
> 
> I think it would be better to have it here in Router.
> 
> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> 
>> Alternatively, you can subclass Router to support setting the parameters
>> in the onInit method.
>> 
>> Not sure which of these is best.
>> 
>>> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
>>> 
>>> Actually, it’s not going to work because the
>> router.routeState.parameters will not be set.
>>> 
>>> You will likely need to add code to set the router.routeState.parameters
>> using the part of the location after the question mark.
>>> 
>>> The easiest way to do that would be to either:
>>> 1. Modify RouteToParameters.stateChanged to first check that there is a
>> parameters value and then set it if not.
>>> 2. Subclass RouteToParameters and override stateChanged to make that
>> check first.
>>> 
 On Apr 17, 2020, at 10:29 AM, Harbs > harbs.li...@gmail.com>> wrote:
 
 I’m pretty sure it’ll work without the hash as well.
 
 Give it a try.
 
> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com > wrote:
> 
> Hi Harbs,
> 
> Thanks for pointing me out, but this is still that Routing expects me
>> to
> use in url hashes - The question is - What if I can't use hashes, but
>> url
> looks like I have presented in previous email ?
> 
> Thanks,
> Piotr
> 
> pt., 17 kwi 2020 o 09:20 Harbs > harbs.li...@gmail.com>> napisał(a):
> 
>> This app uses both path based and query based routing:
>> 
>> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
>> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark> <
>> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
>> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
>> 
>> You can see how it’s done here:
>> 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>> <
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>>> 
>> <
>> 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>> <
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>>> 
>>> 
>> 
>>> On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com >
>> wrote:
>>> 
>>> I'm still looking into the code and it looks like Routing
>> implemented now
>>> is not doing what I would expected. Everything is based on "hash"
>> property
>>> in "location". Instead I need something which is in "search" of
>> location. I
>>> will wait for your thoughts before I do try to handle stuff on my
>> end.
>>> 
>>> pt., 17 kwi 2020 o 08:30 Piotr Zarzycki > >
>>> napisał(a):
>>> 
 Hi Guys,
 
 I really thought that I will be able to use Router [1] based on
 documentation and maybe eventually some look to the code [2] - to
>> figure
 out how things should be implemented. However it looks like non of
>> the
 existing stuff helps me to use in in real world application at all.
>> I
>> would
 like to throw a simple question.
 
 I would like to "answer" in my application to following url, catch
>> params
 and do some actions:
 
 
>> https://mydomain.com/somefolder/index.html?target=somevalue= <
>> https://mydomain.com/somefolder/index.html?target=somevalue=>
 <
>> 
>> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
>> <
>> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
>>> 
>>> 
 somevalue
 
 How should I do that using Routing in Royale ? :)
 
 [1] https://apache.github.io/royale-docs/features/routing <
>> https://apache.github.io/royale-docs/features/routing>
 [2]
 
>> 
>> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing
>> <
>> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing
>>> 
 
 Thanks,
 Piotr
 
 śr., 22 sty 2020 o 13:08 Carlos Rovira 

Re: Routing (was Re: Spectrum Components)

[Carlos Rovira]

Hi,

that's the problem I was talking in the other thread. While a release
process goes, we are stuck, for that reason I was proposing to do release
from a branch, that is something totally legit and will make the rest of
contributors free to continue work. As gitflow indicates, when release is
completed, is merged against develop to upgrade all versions to the right
state.

Maybe not for this, but next release should consider this, since our
release use to last some days. Other projects that release more fast could
do in the actual way since people will not notice.


El vie., 17 abr. 2020 a las 11:43, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

>  I would update it with params once develop will be
> stable. Right now branch is switched to 0.9.8, so Alex probably is doing
> some work.
>

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

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Thanks for input Carlos - I think I will have some scenario in future where
Router may help me. I would update it with params once develop will be
stable. Right now branch is switched to 0.9.8, so Alex probably is doing
some work.

pt., 17 kwi 2020 o 11:37 Carlos Rovira  napisał(a):

> Hi Piotr,
>
> I'm not saying is not right what you're doing. Just pointing that maybe for
> your use case adding all the Router sttuff is not worthit if you don't plan
> to make a real router use far beyond adding those params. But I think if
> there's some scenario not covered with passing params, we need to cover it.
>
>
>
> El vie., 17 abr. 2020 a las 11:22, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Carlos,
> >
> > At some point you are right, but it was just really weird to me that
> Router
> > has in state parameters property and it's empty. To me it looks like
> bug. I
> > would be willing to set it properly in Router as Harbs suggested, but if
> > you think it shouldn't be there - What would be the purpose of parameters
> > property ?
> >
> > pt., 17 kwi 2020 o 11:09 Carlos Rovira 
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > based on the url you provide, URLParameterBead seems the best option
> > right?
> > > Or at least for the info you provided I don't see a SPA for now, just a
> > > need to load some params to set a state.
> > > If you need a full SPA, then is worth to add Routing and part of that
> > could
> > > be receive params.
> > >
> > > HTH
> > >
> > > Carlos
> > >
> > >
> > > El vie., 17 abr. 2020 a las 10:38, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > I think it would be better to have it here in Router.
> > > >
> > > > pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> > > >
> > > > > Alternatively, you can subclass Router to support setting the
> > > parameters
> > > > > in the onInit method.
> > > > >
> > > > > Not sure which of these is best.
> > > > >
> > > > > > On Apr 17, 2020, at 10:35 AM, Harbs 
> wrote:
> > > > > >
> > > > > > Actually, it’s not going to work because the
> > > > > router.routeState.parameters will not be set.
> > > > > >
> > > > > > You will likely need to add code to set the
> > > > router.routeState.parameters
> > > > > using the part of the location after the question mark.
> > > > > >
> > > > > > The easiest way to do that would be to either:
> > > > > > 1. Modify RouteToParameters.stateChanged to first check that
> there
> > > is a
> > > > > parameters value and then set it if not.
> > > > > > 2. Subclass RouteToParameters and override stateChanged to make
> > that
> > > > > check first.
> > > > > >
> > > > > >> On Apr 17, 2020, at 10:29 AM, Harbs  >  > > > > harbs.li...@gmail.com>> wrote:
> > > > > >>
> > > > > >> I’m pretty sure it’ll work without the hash as well.
> > > > > >>
> > > > > >> Give it a try.
> > > > > >>
> > > > > >>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> > > > > piotrzarzyck...@gmail.com >
> wrote:
> > > > > >>>
> > > > > >>> Hi Harbs,
> > > > > >>>
> > > > > >>> Thanks for pointing me out, but this is still that Routing
> > expects
> > > me
> > > > > to
> > > > > >>> use in url hashes - The question is - What if I can't use
> hashes,
> > > but
> > > > > url
> > > > > >>> looks like I have presented in previous email ?
> > > > > >>>
> > > > > >>> Thanks,
> > > > > >>> Piotr
> > > > > >>>
> > > > > >>> pt., 17 kwi 2020 o 09:20 Harbs  > > > > harbs.li...@gmail.com>> napisał(a):
> > > > > >>>
> > > > >  This app uses both path based and query based routing:
> > > > > 
> > > > > 
> > https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> > > <
> > > > > https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>
> <
> > > > > 
> > https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> > > <
> > > > > https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> >>
> > > > > 
> > > > >  You can see how it’s done here:
> > > > > 
> > > > >
> > > >
> > >
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > > > > <
> > > > >
> > > >
> > >
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > > > > >
> > > > >  <
> > > > > 
> > > > >
> > > >
> > >
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > > > > <
> > > > >
> > > >
> > >
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > > > > >
> > > > > >
> > > > > 
> > > > > > On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
> > > > > piotrzarzyck...@gmail.com >
> > > > >  wrote:
> > > > > >
> > > > > > I'm still looking into the code and it looks like Routing
> > > > > implemented now
> > > > > > is not doing what I would expected. Everything is based on
> > 

Re: Routing (was Re: Spectrum Components)

[Carlos Rovira]

Hi Piotr,

I'm not saying is not right what you're doing. Just pointing that maybe for
your use case adding all the Router sttuff is not worthit if you don't plan
to make a real router use far beyond adding those params. But I think if
there's some scenario not covered with passing params, we need to cover it.



El vie., 17 abr. 2020 a las 11:22, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Carlos,
>
> At some point you are right, but it was just really weird to me that Router
> has in state parameters property and it's empty. To me it looks like bug. I
> would be willing to set it properly in Router as Harbs suggested, but if
> you think it shouldn't be there - What would be the purpose of parameters
> property ?
>
> pt., 17 kwi 2020 o 11:09 Carlos Rovira 
> napisał(a):
>
> > Hi Piotr,
> >
> > based on the url you provide, URLParameterBead seems the best option
> right?
> > Or at least for the info you provided I don't see a SPA for now, just a
> > need to load some params to set a state.
> > If you need a full SPA, then is worth to add Routing and part of that
> could
> > be receive params.
> >
> > HTH
> >
> > Carlos
> >
> >
> > El vie., 17 abr. 2020 a las 10:38, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > I think it would be better to have it here in Router.
> > >
> > > pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> > >
> > > > Alternatively, you can subclass Router to support setting the
> > parameters
> > > > in the onInit method.
> > > >
> > > > Not sure which of these is best.
> > > >
> > > > > On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> > > > >
> > > > > Actually, it’s not going to work because the
> > > > router.routeState.parameters will not be set.
> > > > >
> > > > > You will likely need to add code to set the
> > > router.routeState.parameters
> > > > using the part of the location after the question mark.
> > > > >
> > > > > The easiest way to do that would be to either:
> > > > > 1. Modify RouteToParameters.stateChanged to first check that there
> > is a
> > > > parameters value and then set it if not.
> > > > > 2. Subclass RouteToParameters and override stateChanged to make
> that
> > > > check first.
> > > > >
> > > > >> On Apr 17, 2020, at 10:29 AM, Harbs   > > > harbs.li...@gmail.com>> wrote:
> > > > >>
> > > > >> I’m pretty sure it’ll work without the hash as well.
> > > > >>
> > > > >> Give it a try.
> > > > >>
> > > > >>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> > > > piotrzarzyck...@gmail.com > wrote:
> > > > >>>
> > > > >>> Hi Harbs,
> > > > >>>
> > > > >>> Thanks for pointing me out, but this is still that Routing
> expects
> > me
> > > > to
> > > > >>> use in url hashes - The question is - What if I can't use hashes,
> > but
> > > > url
> > > > >>> looks like I have presented in previous email ?
> > > > >>>
> > > > >>> Thanks,
> > > > >>> Piotr
> > > > >>>
> > > > >>> pt., 17 kwi 2020 o 09:20 Harbs  > > > harbs.li...@gmail.com>> napisał(a):
> > > > >>>
> > > >  This app uses both path based and query based routing:
> > > > 
> > > > 
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> > <
> > > > https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark> <
> > > > 
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> > <
> > > > https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
> > > > 
> > > >  You can see how it’s done here:
> > > > 
> > > >
> > >
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > > > <
> > > >
> > >
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > > > >
> > > >  <
> > > > 
> > > >
> > >
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > > > <
> > > >
> > >
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > > > >
> > > > >
> > > > 
> > > > > On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
> > > > piotrzarzyck...@gmail.com >
> > > >  wrote:
> > > > >
> > > > > I'm still looking into the code and it looks like Routing
> > > > implemented now
> > > > > is not doing what I would expected. Everything is based on
> "hash"
> > > >  property
> > > > > in "location". Instead I need something which is in "search" of
> > > >  location. I
> > > > > will wait for your thoughts before I do try to handle stuff on
> my
> > > > end.
> > > > >
> > > > > pt., 17 kwi 2020 o 08:30 Piotr Zarzycki <
> > piotrzarzyck...@gmail.com
> > > > >
> > > > > napisał(a):
> > > > >
> > > > >> Hi Guys,
> > > > >>
> > > > >> I really thought that I will be able to use Router [1] based
> on
> > > > >> documentation and maybe eventually some look 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Hi Carlos,

At some point you are right, but it was just really weird to me that Router
has in state parameters property and it's empty. To me it looks like bug. I
would be willing to set it properly in Router as Harbs suggested, but if
you think it shouldn't be there - What would be the purpose of parameters
property ?

pt., 17 kwi 2020 o 11:09 Carlos Rovira  napisał(a):

> Hi Piotr,
>
> based on the url you provide, URLParameterBead seems the best option right?
> Or at least for the info you provided I don't see a SPA for now, just a
> need to load some params to set a state.
> If you need a full SPA, then is worth to add Routing and part of that could
> be receive params.
>
> HTH
>
> Carlos
>
>
> El vie., 17 abr. 2020 a las 10:38, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > I think it would be better to have it here in Router.
> >
> > pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >
> > > Alternatively, you can subclass Router to support setting the
> parameters
> > > in the onInit method.
> > >
> > > Not sure which of these is best.
> > >
> > > > On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> > > >
> > > > Actually, it’s not going to work because the
> > > router.routeState.parameters will not be set.
> > > >
> > > > You will likely need to add code to set the
> > router.routeState.parameters
> > > using the part of the location after the question mark.
> > > >
> > > > The easiest way to do that would be to either:
> > > > 1. Modify RouteToParameters.stateChanged to first check that there
> is a
> > > parameters value and then set it if not.
> > > > 2. Subclass RouteToParameters and override stateChanged to make that
> > > check first.
> > > >
> > > >> On Apr 17, 2020, at 10:29 AM, Harbs  > > harbs.li...@gmail.com>> wrote:
> > > >>
> > > >> I’m pretty sure it’ll work without the hash as well.
> > > >>
> > > >> Give it a try.
> > > >>
> > > >>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> > > piotrzarzyck...@gmail.com > wrote:
> > > >>>
> > > >>> Hi Harbs,
> > > >>>
> > > >>> Thanks for pointing me out, but this is still that Routing expects
> me
> > > to
> > > >>> use in url hashes - The question is - What if I can't use hashes,
> but
> > > url
> > > >>> looks like I have presented in previous email ?
> > > >>>
> > > >>> Thanks,
> > > >>> Piotr
> > > >>>
> > > >>> pt., 17 kwi 2020 o 09:20 Harbs  > > harbs.li...@gmail.com>> napisał(a):
> > > >>>
> > >  This app uses both path based and query based routing:
> > > 
> > >  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> <
> > > https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark> <
> > >  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> <
> > > https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
> > > 
> > >  You can see how it’s done here:
> > > 
> > >
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > > <
> > >
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > > >
> > >  <
> > > 
> > >
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > > <
> > >
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > > >
> > > >
> > > 
> > > > On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
> > > piotrzarzyck...@gmail.com >
> > >  wrote:
> > > >
> > > > I'm still looking into the code and it looks like Routing
> > > implemented now
> > > > is not doing what I would expected. Everything is based on "hash"
> > >  property
> > > > in "location". Instead I need something which is in "search" of
> > >  location. I
> > > > will wait for your thoughts before I do try to handle stuff on my
> > > end.
> > > >
> > > > pt., 17 kwi 2020 o 08:30 Piotr Zarzycki <
> piotrzarzyck...@gmail.com
> > > >
> > > > napisał(a):
> > > >
> > > >> Hi Guys,
> > > >>
> > > >> I really thought that I will be able to use Router [1] based on
> > > >> documentation and maybe eventually some look to the code [2] -
> to
> > > figure
> > > >> out how things should be implemented. However it looks like non
> of
> > > the
> > > >> existing stuff helps me to use in in real world application at
> > all.
> > > I
> > >  would
> > > >> like to throw a simple question.
> > > >>
> > > >> I would like to "answer" in my application to following url,
> catch
> > >  params
> > > >> and do some actions:
> > > >>
> > > >>
> > > https://mydomain.com/somefolder/index.html?target=somevalue= <
> > > https://mydomain.com/somefolder/index.html?target=somevalue=>
> > > >> <
> > > 
> > >
> >
> 

Re: Routing (was Re: Spectrum Components)

[Carlos Rovira]

Hi Piotr,

based on the url you provide, URLParameterBead seems the best option right?
Or at least for the info you provided I don't see a SPA for now, just a
need to load some params to set a state.
If you need a full SPA, then is worth to add Routing and part of that could
be receive params.

HTH

Carlos


El vie., 17 abr. 2020 a las 10:38, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> I think it would be better to have it here in Router.
>
> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
>
> > Alternatively, you can subclass Router to support setting the parameters
> > in the onInit method.
> >
> > Not sure which of these is best.
> >
> > > On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> > >
> > > Actually, it’s not going to work because the
> > router.routeState.parameters will not be set.
> > >
> > > You will likely need to add code to set the
> router.routeState.parameters
> > using the part of the location after the question mark.
> > >
> > > The easiest way to do that would be to either:
> > > 1. Modify RouteToParameters.stateChanged to first check that there is a
> > parameters value and then set it if not.
> > > 2. Subclass RouteToParameters and override stateChanged to make that
> > check first.
> > >
> > >> On Apr 17, 2020, at 10:29 AM, Harbs  > harbs.li...@gmail.com>> wrote:
> > >>
> > >> I’m pretty sure it’ll work without the hash as well.
> > >>
> > >> Give it a try.
> > >>
> > >>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com > wrote:
> > >>>
> > >>> Hi Harbs,
> > >>>
> > >>> Thanks for pointing me out, but this is still that Routing expects me
> > to
> > >>> use in url hashes - The question is - What if I can't use hashes, but
> > url
> > >>> looks like I have presented in previous email ?
> > >>>
> > >>> Thanks,
> > >>> Piotr
> > >>>
> > >>> pt., 17 kwi 2020 o 09:20 Harbs  > harbs.li...@gmail.com>> napisał(a):
> > >>>
> >  This app uses both path based and query based routing:
> > 
> >  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
> > https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark> <
> >  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
> > https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
> > 
> >  You can see how it’s done here:
> > 
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > <
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > >
> >  <
> > 
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > <
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > >
> > >
> > 
> > > On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com >
> >  wrote:
> > >
> > > I'm still looking into the code and it looks like Routing
> > implemented now
> > > is not doing what I would expected. Everything is based on "hash"
> >  property
> > > in "location". Instead I need something which is in "search" of
> >  location. I
> > > will wait for your thoughts before I do try to handle stuff on my
> > end.
> > >
> > > pt., 17 kwi 2020 o 08:30 Piotr Zarzycki  > >
> > > napisał(a):
> > >
> > >> Hi Guys,
> > >>
> > >> I really thought that I will be able to use Router [1] based on
> > >> documentation and maybe eventually some look to the code [2] - to
> > figure
> > >> out how things should be implemented. However it looks like non of
> > the
> > >> existing stuff helps me to use in in real world application at
> all.
> > I
> >  would
> > >> like to throw a simple question.
> > >>
> > >> I would like to "answer" in my application to following url, catch
> >  params
> > >> and do some actions:
> > >>
> > >>
> > https://mydomain.com/somefolder/index.html?target=somevalue= <
> > https://mydomain.com/somefolder/index.html?target=somevalue=>
> > >> <
> > 
> >
> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
> > <
> >
> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
> > >
> > >
> > >> somevalue
> > >>
> > >> How should I do that using Routing in Royale ? :)
> > >>
> > >> [1] https://apache.github.io/royale-docs/features/routing <
> > https://apache.github.io/royale-docs/features/routing>
> > >> [2]
> > >>
> > 
> >
> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing
> > <
> >
> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing
> > >
> > 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

I think it would be better to have it here in Router.

pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):

> Alternatively, you can subclass Router to support setting the parameters
> in the onInit method.
>
> Not sure which of these is best.
>
> > On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >
> > Actually, it’s not going to work because the
> router.routeState.parameters will not be set.
> >
> > You will likely need to add code to set the router.routeState.parameters
> using the part of the location after the question mark.
> >
> > The easiest way to do that would be to either:
> > 1. Modify RouteToParameters.stateChanged to first check that there is a
> parameters value and then set it if not.
> > 2. Subclass RouteToParameters and override stateChanged to make that
> check first.
> >
> >> On Apr 17, 2020, at 10:29 AM, Harbs  harbs.li...@gmail.com>> wrote:
> >>
> >> I’m pretty sure it’ll work without the hash as well.
> >>
> >> Give it a try.
> >>
> >>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com > wrote:
> >>>
> >>> Hi Harbs,
> >>>
> >>> Thanks for pointing me out, but this is still that Routing expects me
> to
> >>> use in url hashes - The question is - What if I can't use hashes, but
> url
> >>> looks like I have presented in previous email ?
> >>>
> >>> Thanks,
> >>> Piotr
> >>>
> >>> pt., 17 kwi 2020 o 09:20 Harbs  harbs.li...@gmail.com>> napisał(a):
> >>>
>  This app uses both path based and query based routing:
> 
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark> <
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
> 
>  You can see how it’s done here:
> 
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> <
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
>  <
> 
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> <
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
> >
> 
> > On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com >
>  wrote:
> >
> > I'm still looking into the code and it looks like Routing
> implemented now
> > is not doing what I would expected. Everything is based on "hash"
>  property
> > in "location". Instead I need something which is in "search" of
>  location. I
> > will wait for your thoughts before I do try to handle stuff on my
> end.
> >
> > pt., 17 kwi 2020 o 08:30 Piotr Zarzycki  >
> > napisał(a):
> >
> >> Hi Guys,
> >>
> >> I really thought that I will be able to use Router [1] based on
> >> documentation and maybe eventually some look to the code [2] - to
> figure
> >> out how things should be implemented. However it looks like non of
> the
> >> existing stuff helps me to use in in real world application at all.
> I
>  would
> >> like to throw a simple question.
> >>
> >> I would like to "answer" in my application to following url, catch
>  params
> >> and do some actions:
> >>
> >>
> https://mydomain.com/somefolder/index.html?target=somevalue= <
> https://mydomain.com/somefolder/index.html?target=somevalue=>
> >> <
> 
> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
> <
> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
> >
> >
> >> somevalue
> >>
> >> How should I do that using Routing in Royale ? :)
> >>
> >> [1] https://apache.github.io/royale-docs/features/routing <
> https://apache.github.io/royale-docs/features/routing>
> >> [2]
> >>
> 
> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing
> <
> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing
> >
> >>
> >> Thanks,
> >> Piotr
> >>
> >> śr., 22 sty 2020 o 13:08 Carlos Rovira 
> >> napisał(a):
> >>
> >>> Hi Harbs,
> >>>
> >>> thanks for taking a look, I'll try to apply your suggestions and
> see
>  if I
> >>> can make it work.
> >>>
> >>> If you plan to work in that new Routing implementation, I'll wait
> for
>  it
> >>> to
> >>> write about it in blog and social media, since better to point
> people
>  to
> >>> the more elaborated one. I as well recommend you to make it end in
> its
>  own
> >>> "Routing.swc" since I think it deserves it.
> >>>
> >>> As Alex dream on 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

I would like to make in  RouteToParameters methods which handle events
protected - Any objections to that ?

pt., 17 kwi 2020 o 10:14 Piotr Zarzycki 
napisał(a):

> Alex,
>
> I wanted to try out new stuff. I know about URLParameterBead, but I may
> use also some other features available in Routing itself.
>
> pt., 17 kwi 2020 o 10:02 Alex Harui  napisał(a):
>
>> Could Piotr use URLParameterBead?
>>
>> On 4/17/20, 12:37 AM, "Harbs"  wrote:
>>
>> Alternatively, you can subclass Router to support setting the
>> parameters in the onInit method.
>>
>> Not sure which of these is best.
>>
>> > On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
>> >
>> > Actually, it’s not going to work because the
>> router.routeState.parameters will not be set.
>> >
>> > You will likely need to add code to set the
>> router.routeState.parameters using the part of the location after the
>> question mark.
>> >
>> > The easiest way to do that would be to either:
>> > 1. Modify RouteToParameters.stateChanged to first check that there
>> is a parameters value and then set it if not.
>> > 2. Subclass RouteToParameters and override stateChanged to make
>> that check first.
>> >
>> >> On Apr 17, 2020, at 10:29 AM, Harbs > > wrote:
>> >>
>> >> I’m pretty sure it’ll work without the hash as well.
>> >>
>> >> Give it a try.
>> >>
>> >>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com > wrote:
>> >>>
>> >>> Hi Harbs,
>> >>>
>> >>> Thanks for pointing me out, but this is still that Routing
>> expects me to
>> >>> use in url hashes - The question is - What if I can't use hashes,
>> but url
>> >>> looks like I have presented in previous email ?
>> >>>
>> >>> Thanks,
>> >>> Piotr
>> >>>
>> >>> pt., 17 kwi 2020 o 09:20 Harbs > harbs.li...@gmail.com>> napisał(a):
>> >>>
>>  This app uses both path based and query based routing:
>> 
>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=J0%2B2oe8aWAsHB2eCgOHVeixDBX%2FIqifp60yX6W3ZCmk%3Dreserved=0
>> <
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=J0%2B2oe8aWAsHB2eCgOHVeixDBX%2FIqifp60yX6W3ZCmk%3Dreserved=0>
>> <
>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=J0%2B2oe8aWAsHB2eCgOHVeixDBX%2FIqifp60yX6W3ZCmk%3Dreserved=0
>> <
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=J0%2B2oe8aWAsHB2eCgOHVeixDBX%2FIqifp60yX6W3ZCmk%3Dreserved=0
>> >>
>> 
>>  You can see how it’s done here:
>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Funhurdle%2Fspectrum-royale%2Fblob%2Fmaster%2FSpectrumBrowser%2Fsrc%2Fview%2FBrowserRouter.mxmldata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=O%2FoVVZWDijp7CejxncZo7vH0DPeQsw7dudhb19cUzo4%3Dreserved=0
>> <
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Funhurdle%2Fspectrum-royale%2Fblob%2Fmaster%2FSpectrumBrowser%2Fsrc%2Fview%2FBrowserRouter.mxmldata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=O%2FoVVZWDijp7CejxncZo7vH0DPeQsw7dudhb19cUzo4%3Dreserved=0
>> >
>>  <
>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Funhurdle%2Fspectrum-royale%2Fblob%2Fmaster%2FSpectrumBrowser%2Fsrc%2Fview%2FBrowserRouter.mxmldata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=O%2FoVVZWDijp7CejxncZo7vH0DPeQsw7dudhb19cUzo4%3Dreserved=0
>> <
>> 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Alex,

I wanted to try out new stuff. I know about URLParameterBead, but I may use
also some other features available in Routing itself.

pt., 17 kwi 2020 o 10:02 Alex Harui  napisał(a):

> Could Piotr use URLParameterBead?
>
> On 4/17/20, 12:37 AM, "Harbs"  wrote:
>
> Alternatively, you can subclass Router to support setting the
> parameters in the onInit method.
>
> Not sure which of these is best.
>
> > On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >
> > Actually, it’s not going to work because the
> router.routeState.parameters will not be set.
> >
> > You will likely need to add code to set the
> router.routeState.parameters using the part of the location after the
> question mark.
> >
> > The easiest way to do that would be to either:
> > 1. Modify RouteToParameters.stateChanged to first check that there
> is a parameters value and then set it if not.
> > 2. Subclass RouteToParameters and override stateChanged to make that
> check first.
> >
> >> On Apr 17, 2020, at 10:29 AM, Harbs  harbs.li...@gmail.com>> wrote:
> >>
> >> I’m pretty sure it’ll work without the hash as well.
> >>
> >> Give it a try.
> >>
> >>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com > wrote:
> >>>
> >>> Hi Harbs,
> >>>
> >>> Thanks for pointing me out, but this is still that Routing expects
> me to
> >>> use in url hashes - The question is - What if I can't use hashes,
> but url
> >>> looks like I have presented in previous email ?
> >>>
> >>> Thanks,
> >>> Piotr
> >>>
> >>> pt., 17 kwi 2020 o 09:20 Harbs  harbs.li...@gmail.com>> napisał(a):
> >>>
>  This app uses both path based and query based routing:
> 
> 
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=J0%2B2oe8aWAsHB2eCgOHVeixDBX%2FIqifp60yX6W3ZCmk%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=J0%2B2oe8aWAsHB2eCgOHVeixDBX%2FIqifp60yX6W3ZCmk%3Dreserved=0>
> <
> 
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=J0%2B2oe8aWAsHB2eCgOHVeixDBX%2FIqifp60yX6W3ZCmk%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=J0%2B2oe8aWAsHB2eCgOHVeixDBX%2FIqifp60yX6W3ZCmk%3Dreserved=0
> >>
> 
>  You can see how it’s done here:
> 
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Funhurdle%2Fspectrum-royale%2Fblob%2Fmaster%2FSpectrumBrowser%2Fsrc%2Fview%2FBrowserRouter.mxmldata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=O%2FoVVZWDijp7CejxncZo7vH0DPeQsw7dudhb19cUzo4%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Funhurdle%2Fspectrum-royale%2Fblob%2Fmaster%2FSpectrumBrowser%2Fsrc%2Fview%2FBrowserRouter.mxmldata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=O%2FoVVZWDijp7CejxncZo7vH0DPeQsw7dudhb19cUzo4%3Dreserved=0
> >
>  <
> 
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Funhurdle%2Fspectrum-royale%2Fblob%2Fmaster%2FSpectrumBrowser%2Fsrc%2Fview%2FBrowserRouter.mxmldata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=O%2FoVVZWDijp7CejxncZo7vH0DPeQsw7dudhb19cUzo4%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Funhurdle%2Fspectrum-royale%2Fblob%2Fmaster%2FSpectrumBrowser%2Fsrc%2Fview%2FBrowserRouter.mxmldata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=O%2FoVVZWDijp7CejxncZo7vH0DPeQsw7dudhb19cUzo4%3Dreserved=0
> >
> >
> 
> > On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com >
>  wrote:
> >
> > I'm still looking into 

Re: Routing (was Re: Spectrum Components)

[Alex Harui]

Could Piotr use URLParameterBead?

On 4/17/20, 12:37 AM, "Harbs"  wrote:

Alternatively, you can subclass Router to support setting the parameters in 
the onInit method.

Not sure which of these is best.

> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> 
> Actually, it’s not going to work because the router.routeState.parameters 
will not be set.
> 
> You will likely need to add code to set the router.routeState.parameters 
using the part of the location after the question mark.
> 
> The easiest way to do that would be to either:
> 1. Modify RouteToParameters.stateChanged to first check that there is a 
parameters value and then set it if not.
> 2. Subclass RouteToParameters and override stateChanged to make that 
check first.
> 
>> On Apr 17, 2020, at 10:29 AM, Harbs mailto:harbs.li...@gmail.com>> wrote:
>> 
>> I’m pretty sure it’ll work without the hash as well.
>> 
>> Give it a try.
>> 
>>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki mailto:piotrzarzyck...@gmail.com>> wrote:
>>> 
>>> Hi Harbs,
>>> 
>>> Thanks for pointing me out, but this is still that Routing expects me to
>>> use in url hashes - The question is - What if I can't use hashes, but 
url
>>> looks like I have presented in previous email ?
>>> 
>>> Thanks,
>>> Piotr
>>> 
>>> pt., 17 kwi 2020 o 09:20 Harbs mailto:harbs.li...@gmail.com>> napisał(a):
>>> 
 This app uses both path based and query based routing:
 
 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=J0%2B2oe8aWAsHB2eCgOHVeixDBX%2FIqifp60yX6W3ZCmk%3Dreserved=0
 

 <
 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddarkdata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=J0%2B2oe8aWAsHB2eCgOHVeixDBX%2FIqifp60yX6W3ZCmk%3Dreserved=0
 
>
 
 You can see how it’s done here:
 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Funhurdle%2Fspectrum-royale%2Fblob%2Fmaster%2FSpectrumBrowser%2Fsrc%2Fview%2FBrowserRouter.mxmldata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=O%2FoVVZWDijp7CejxncZo7vH0DPeQsw7dudhb19cUzo4%3Dreserved=0
 

 <
 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Funhurdle%2Fspectrum-royale%2Fblob%2Fmaster%2FSpectrumBrowser%2Fsrc%2Fview%2FBrowserRouter.mxmldata=02%7C01%7Caharui%40adobe.com%7C5e655077c66b4a94f55f08d7e2a224a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227058344292469sdata=O%2FoVVZWDijp7CejxncZo7vH0DPeQsw7dudhb19cUzo4%3Dreserved=0
 

> 
 
> On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki 
mailto:piotrzarzyck...@gmail.com>>
 wrote:
> 
> I'm still looking into the code and it looks like Routing implemented 
now
> is not doing what I would expected. Everything is based on "hash"
 property
> in "location". Instead I need something which is in "search" of
 location. I
> will wait for your thoughts before I do try to handle stuff on my end.
> 
> pt., 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Thanks for pointing it out. Do you suggest me to change framework code or
your suggestion is something which I should rather do on my application ?

pt., 17 kwi 2020 o 09:35 Harbs  napisał(a):

> Actually, it’s not going to work because the router.routeState.parameters
> will not be set.
>
> You will likely need to add code to set the router.routeState.parameters
> using the part of the location after the question mark.
>
> The easiest way to do that would be to either:
> 1. Modify RouteToParameters.stateChanged to first check that there is a
> parameters value and then set it if not.
> 2. Subclass RouteToParameters and override stateChanged to make that check
> first.
>
> > On Apr 17, 2020, at 10:29 AM, Harbs  wrote:
> >
> > I’m pretty sure it’ll work without the hash as well.
> >
> > Give it a try.
> >
> >> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki  > wrote:
> >>
> >> Hi Harbs,
> >>
> >> Thanks for pointing me out, but this is still that Routing expects me to
> >> use in url hashes - The question is - What if I can't use hashes, but
> url
> >> looks like I have presented in previous email ?
> >>
> >> Thanks,
> >> Piotr
> >>
> >> pt., 17 kwi 2020 o 09:20 Harbs  harbs.li...@gmail.com>> napisał(a):
> >>
> >>> This app uses both path based and query based routing:
> >>>
> >>> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark> <
> >>> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
> >>>
> >>> You can see how it’s done here:
> >>>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> <
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
> >>> <
> >>>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> <
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
> 
> >>>
>  On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com >
> >>> wrote:
> 
>  I'm still looking into the code and it looks like Routing implemented
> now
>  is not doing what I would expected. Everything is based on "hash"
> >>> property
>  in "location". Instead I need something which is in "search" of
> >>> location. I
>  will wait for your thoughts before I do try to handle stuff on my end.
> 
>  pt., 17 kwi 2020 o 08:30 Piotr Zarzycki  >
>  napisał(a):
> 
> > Hi Guys,
> >
> > I really thought that I will be able to use Router [1] based on
> > documentation and maybe eventually some look to the code [2] - to
> figure
> > out how things should be implemented. However it looks like non of
> the
> > existing stuff helps me to use in in real world application at all. I
> >>> would
> > like to throw a simple question.
> >
> > I would like to "answer" in my application to following url, catch
> >>> params
> > and do some actions:
> >
> > https://mydomain.com/somefolder/index.html?target=somevalue=
> 
> > <
> >>>
> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
> <
> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
> >
> 
> > somevalue
> >
> > How should I do that using Routing in Royale ? :)
> >
> > [1] https://apache.github.io/royale-docs/features/routing
> > [2]
> >
> >>>
> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing
> >
> > Thanks,
> > Piotr
> >
> > śr., 22 sty 2020 o 13:08 Carlos Rovira 
> > napisał(a):
> >
> >> Hi Harbs,
> >>
> >> thanks for taking a look, I'll try to apply your suggestions and see
> >>> if I
> >> can make it work.
> >>
> >> If you plan to work in that new Routing implementation, I'll wait
> for
> >>> it
> >> to
> >> write about it in blog and social media, since better to point
> people
> >>> to
> >> the more elaborated one. I as well recommend you to make it end in
> its
> >>> own
> >> "Routing.swc" since I think it deserves it.
> >>
> >> As Alex dream on possibilities, I want as well to dream and I think
> >> nowadays, a part from pure client navigation, we have server
> >>> navigation,
> >> and as other royale features people will soon try to do it. In the
> >>> case of
> >> Routing, people will want to have URLs for concrete items retrieved
> >>> from
> >> database and we should support it (was what we discussed before
> that in
> >> that case, we'll be able to not have # in the 

Re: Routing (was Re: Spectrum Components)

[Harbs]

Alternatively, you can subclass Router to support setting the parameters in the 
onInit method.

Not sure which of these is best.

> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> 
> Actually, it’s not going to work because the router.routeState.parameters 
> will not be set.
> 
> You will likely need to add code to set the router.routeState.parameters 
> using the part of the location after the question mark.
> 
> The easiest way to do that would be to either:
> 1. Modify RouteToParameters.stateChanged to first check that there is a 
> parameters value and then set it if not.
> 2. Subclass RouteToParameters and override stateChanged to make that check 
> first.
> 
>> On Apr 17, 2020, at 10:29 AM, Harbs > > wrote:
>> 
>> I’m pretty sure it’ll work without the hash as well.
>> 
>> Give it a try.
>> 
>>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki >> > wrote:
>>> 
>>> Hi Harbs,
>>> 
>>> Thanks for pointing me out, but this is still that Routing expects me to
>>> use in url hashes - The question is - What if I can't use hashes, but url
>>> looks like I have presented in previous email ?
>>> 
>>> Thanks,
>>> Piotr
>>> 
>>> pt., 17 kwi 2020 o 09:20 Harbs >> > napisał(a):
>>> 
 This app uses both path based and query based routing:
 
 https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 
  <
 https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 
 >
 
 You can see how it’s done here:
 https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
  
 
 <
 https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
  
 
> 
 
> On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki  >
 wrote:
> 
> I'm still looking into the code and it looks like Routing implemented now
> is not doing what I would expected. Everything is based on "hash"
 property
> in "location". Instead I need something which is in "search" of
 location. I
> will wait for your thoughts before I do try to handle stuff on my end.
> 
> pt., 17 kwi 2020 o 08:30 Piotr Zarzycki  >
> napisał(a):
> 
>> Hi Guys,
>> 
>> I really thought that I will be able to use Router [1] based on
>> documentation and maybe eventually some look to the code [2] - to figure
>> out how things should be implemented. However it looks like non of the
>> existing stuff helps me to use in in real world application at all. I
 would
>> like to throw a simple question.
>> 
>> I would like to "answer" in my application to following url, catch
 params
>> and do some actions:
>> 
>> https://mydomain.com/somefolder/index.html?target=somevalue= 
>> 
>> <
 https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
  
 
> 
>> somevalue
>> 
>> How should I do that using Routing in Royale ? :)
>> 
>> [1] https://apache.github.io/royale-docs/features/routing 
>> 
>> [2]
>> 
 https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing
  
 
>> 
>> Thanks,
>> Piotr
>> 
>> śr., 22 sty 2020 o 13:08 Carlos Rovira 
>> napisał(a):
>> 
>>> Hi Harbs,
>>> 
>>> thanks for taking a look, I'll try to apply your suggestions and see
 if I
>>> can make it work.
>>> 
>>> If you plan to work in that new Routing implementation, I'll wait for
 it
>>> to
>>> write about it in blog and social media, since better to point people
 to
>>> the more elaborated one. I as well recommend you to make it end in its
 own
>>> "Routing.swc" since I think it deserves it.
>>> 
>>> As Alex dream on possibilities, I want as well to dream and I think
>>> nowadays, a part from pure client navigation, we have server
 navigation,
>>> and as other royale features people will soon try to do it. In the
 case of
>>> Routing, people will want to have URLs for concrete items retrieved

Re: Routing (was Re: Spectrum Components)

[Harbs]

Actually, it’s not going to work because the router.routeState.parameters will 
not be set.

You will likely need to add code to set the router.routeState.parameters using 
the part of the location after the question mark.

The easiest way to do that would be to either:
1. Modify RouteToParameters.stateChanged to first check that there is a 
parameters value and then set it if not.
2. Subclass RouteToParameters and override stateChanged to make that check 
first.

> On Apr 17, 2020, at 10:29 AM, Harbs  wrote:
> 
> I’m pretty sure it’ll work without the hash as well.
> 
> Give it a try.
> 
>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki > > wrote:
>> 
>> Hi Harbs,
>> 
>> Thanks for pointing me out, but this is still that Routing expects me to
>> use in url hashes - The question is - What if I can't use hashes, but url
>> looks like I have presented in previous email ?
>> 
>> Thanks,
>> Piotr
>> 
>> pt., 17 kwi 2020 o 09:20 Harbs > > napisał(a):
>> 
>>> This app uses both path based and query based routing:
>>> 
>>> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 
>>>  <
>>> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 
>>> >
>>> 
>>> You can see how it’s done here:
>>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>>>  
>>> 
>>> <
>>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>>>  
>>> 
 
>>> 
 On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki >>> >
>>> wrote:
 
 I'm still looking into the code and it looks like Routing implemented now
 is not doing what I would expected. Everything is based on "hash"
>>> property
 in "location". Instead I need something which is in "search" of
>>> location. I
 will wait for your thoughts before I do try to handle stuff on my end.
 
 pt., 17 kwi 2020 o 08:30 Piotr Zarzycki >>> >
 napisał(a):
 
> Hi Guys,
> 
> I really thought that I will be able to use Router [1] based on
> documentation and maybe eventually some look to the code [2] - to figure
> out how things should be implemented. However it looks like non of the
> existing stuff helps me to use in in real world application at all. I
>>> would
> like to throw a simple question.
> 
> I would like to "answer" in my application to following url, catch
>>> params
> and do some actions:
> 
> https://mydomain.com/somefolder/index.html?target=somevalue= 
> 
> <
>>> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
>>>  
>>> 
 
> somevalue
> 
> How should I do that using Routing in Royale ? :)
> 
> [1] https://apache.github.io/royale-docs/features/routing
> [2]
> 
>>> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing
> 
> Thanks,
> Piotr
> 
> śr., 22 sty 2020 o 13:08 Carlos Rovira 
> napisał(a):
> 
>> Hi Harbs,
>> 
>> thanks for taking a look, I'll try to apply your suggestions and see
>>> if I
>> can make it work.
>> 
>> If you plan to work in that new Routing implementation, I'll wait for
>>> it
>> to
>> write about it in blog and social media, since better to point people
>>> to
>> the more elaborated one. I as well recommend you to make it end in its
>>> own
>> "Routing.swc" since I think it deserves it.
>> 
>> As Alex dream on possibilities, I want as well to dream and I think
>> nowadays, a part from pure client navigation, we have server
>>> navigation,
>> and as other royale features people will soon try to do it. In the
>>> case of
>> Routing, people will want to have URLs for concrete items retrieved
>>> from
>> database and we should support it (was what we discussed before that in
>> that case, we'll be able to not have # in the url but just a friendly
>> permalink). Hope we can support that, since we'll be great to create,
>>> lets
>> say, a blog app, and as user browse posts and navigate to see a full
>> posst,
>> he gets as well a friendly URL with no anchors that can be indexable by
>> google and retrieved (i.e, the same as Wordpress)
>> 
>> Thanks
>> 
>> 
>> 
>> 
>> 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

My url already have a proper look. I wanted to have it like that
https://mydomain.com/somefolder/index.html?target=somevalue=

somevalue

pt., 17 kwi 2020 o 09:15 Alex Harui  napisał(a):

> What do you want your URLs to look like?  Remember that hash is used to
> keep the browser from reloading the app.
>
> On 4/17/20, 12:13 AM, "Piotr Zarzycki"  wrote:
>
> I'm still looking into the code and it looks like Routing implemented
> now
> is not doing what I would expected. Everything is based on "hash"
> property
> in "location". Instead I need something which is in "search" of
> location. I
> will wait for your thoughts before I do try to handle stuff on my end.
>
> pt., 17 kwi 2020 o 08:30 Piotr Zarzycki 
> napisał(a):
>
> > Hi Guys,
> >
> > I really thought that I will be able to use Router [1] based on
> > documentation and maybe eventually some look to the code [2] - to
> figure
> > out how things should be implemented. However it looks like non of
> the
> > existing stuff helps me to use in in real world application at all.
> I would
> > like to throw a simple question.
> >
> > I would like to "answer" in my application to following url, catch
> params
> > and do some actions:
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmydomain.com%2Fsomefolder%2Findex.html%3Ftarget%3Dsomevalue%26account%3Ddata=02%7C01%7Caharui%40adobe.com%7C9c2cf4e0d00b4580633708d7e29ed603%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227044141794314sdata=Dv%2FfoygkOuy8EWX3yajDig8oYM9d7ZgqUOGohQd37og%3Dreserved=0
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flocaldev.prominic.net%2Fprominic%2Fbin%2Fjs-debug%2Findex.html%3Ftarget%3DUpdateCreditCard%26account%3DA55XXXdata=02%7C01%7Caharui%40adobe.com%7C9c2cf4e0d00b4580633708d7e29ed603%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227044141794314sdata=OW%2BlL31bVS%2FUSwL3GJrUAN7ppdjLjYPueWlLqFXQxwA%3Dreserved=0
> >
> > somevalue
> >
> > How should I do that using Routing in Royale ? :)
> >
> > [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache.github.io%2Froyale-docs%2Ffeatures%2Froutingdata=02%7C01%7Caharui%40adobe.com%7C9c2cf4e0d00b4580633708d7e29ed603%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227044141794314sdata=%2Bq64VNDap48GgbtQtGnIKFQhasrk%2FXb5%2B0bqiTXs328%3Dreserved=0
> > [2]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fframeworks%2Fprojects%2FBasic%2Fsrc%2Fmain%2Froyale%2Forg%2Fapache%2Froyale%2Froutingdata=02%7C01%7Caharui%40adobe.com%7C9c2cf4e0d00b4580633708d7e29ed603%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227044141794314sdata=dbfGXbu79kwYBWPwd4i0meomYPr616KOKMT6ok%2FVwX8%3Dreserved=0
> >
> > Thanks,
> > Piotr
> >
> > śr., 22 sty 2020 o 13:08 Carlos Rovira 
> > napisał(a):
> >
> >> Hi Harbs,
> >>
> >> thanks for taking a look, I'll try to apply your suggestions and
> see if I
> >> can make it work.
> >>
> >> If you plan to work in that new Routing implementation, I'll wait
> for it
> >> to
> >> write about it in blog and social media, since better to point
> people to
> >> the more elaborated one. I as well recommend you to make it end in
> its own
> >> "Routing.swc" since I think it deserves it.
> >>
> >> As Alex dream on possibilities, I want as well to dream and I think
> >> nowadays, a part from pure client navigation, we have server
> navigation,
> >> and as other royale features people will soon try to do it. In the
> case of
> >> Routing, people will want to have URLs for concrete items retrieved
> from
> >> database and we should support it (was what we discussed before
> that in
> >> that case, we'll be able to not have # in the url but just a
> friendly
> >> permalink). Hope we can support that, since we'll be great to
> create, lets
> >> say, a blog app, and as user browse posts and navigate to see a full
> >> posst,
> >> he gets as well a friendly URL with no anchors that can be
> indexable by
> >> google and retrieved (i.e, the same as Wordpress)
> >>
> >> Thanks
> >>
> >>
> >>
> >>
> >>
> >> El mar., 21 ene. 2020 a las 23:57, Alex Harui
> ( >> >)
> >> escribió:
> >>
> >> > If we're dreaming of the future possible implementations, one
> vision is
> >> > that the route paths are computed from the currentStates of
> Containers.
> >> > That might have the least setup required, it would almost be
> automatic.
> >> >
> >> > IOW, Containers have both a label and currentState property. A
> routing
> >> > implementation could scan the DOM for contaners and build the
> path from
> >> > label/currentState 

Re: Routing (was Re: Spectrum Components)

[Harbs]

I’m pretty sure it’ll work without the hash as well.

Give it a try.

> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki  
> wrote:
> 
> Hi Harbs,
> 
> Thanks for pointing me out, but this is still that Routing expects me to
> use in url hashes - The question is - What if I can't use hashes, but url
> looks like I have presented in previous email ?
> 
> Thanks,
> Piotr
> 
> pt., 17 kwi 2020 o 09:20 Harbs  > napisał(a):
> 
>> This app uses both path based and query based routing:
>> 
>> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 
>>  <
>> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 
>> >
>> 
>> You can see how it’s done here:
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>>  
>> 
>> <
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>>  
>> 
>>> 
>> 
>>> On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki 
>> wrote:
>>> 
>>> I'm still looking into the code and it looks like Routing implemented now
>>> is not doing what I would expected. Everything is based on "hash"
>> property
>>> in "location". Instead I need something which is in "search" of
>> location. I
>>> will wait for your thoughts before I do try to handle stuff on my end.
>>> 
>>> pt., 17 kwi 2020 o 08:30 Piotr Zarzycki 
>>> napisał(a):
>>> 
 Hi Guys,
 
 I really thought that I will be able to use Router [1] based on
 documentation and maybe eventually some look to the code [2] - to figure
 out how things should be implemented. However it looks like non of the
 existing stuff helps me to use in in real world application at all. I
>> would
 like to throw a simple question.
 
 I would like to "answer" in my application to following url, catch
>> params
 and do some actions:
 
 https://mydomain.com/somefolder/index.html?target=somevalue=
 <
>> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
>>> 
 somevalue
 
 How should I do that using Routing in Royale ? :)
 
 [1] https://apache.github.io/royale-docs/features/routing
 [2]
 
>> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing
 
 Thanks,
 Piotr
 
 śr., 22 sty 2020 o 13:08 Carlos Rovira 
 napisał(a):
 
> Hi Harbs,
> 
> thanks for taking a look, I'll try to apply your suggestions and see
>> if I
> can make it work.
> 
> If you plan to work in that new Routing implementation, I'll wait for
>> it
> to
> write about it in blog and social media, since better to point people
>> to
> the more elaborated one. I as well recommend you to make it end in its
>> own
> "Routing.swc" since I think it deserves it.
> 
> As Alex dream on possibilities, I want as well to dream and I think
> nowadays, a part from pure client navigation, we have server
>> navigation,
> and as other royale features people will soon try to do it. In the
>> case of
> Routing, people will want to have URLs for concrete items retrieved
>> from
> database and we should support it (was what we discussed before that in
> that case, we'll be able to not have # in the url but just a friendly
> permalink). Hope we can support that, since we'll be great to create,
>> lets
> say, a blog app, and as user browse posts and navigate to see a full
> posst,
> he gets as well a friendly URL with no anchors that can be indexable by
> google and retrieved (i.e, the same as Wordpress)
> 
> Thanks
> 
> 
> 
> 
> 
> El mar., 21 ene. 2020 a las 23:57, Alex Harui
>> (> )
> escribió:
> 
>> If we're dreaming of the future possible implementations, one vision
>> is
>> that the route paths are computed from the currentStates of
>> Containers.
>> That might have the least setup required, it would almost be
>> automatic.
>> 
>> IOW, Containers have both a label and currentState property. A routing
>> implementation could scan the DOM for contaners and build the path
>> from
>> label/currentState pairs.
>> 
>> Of course, I could be wrong...
>> 
>> -Alex
>> 
>> 
>> On 1/21/20, 1:33 PM, "Harbs"  wrote:
>> 
>>   I’ve also been thinking about the router in general, and I came up
>> with an idea on how to do it with beads.
>> 
>>   It’ll probably take me a few days until I implement the changes…
>> 
>>   In addition to , I think we can also 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Hi Harbs,

Thanks for pointing me out, but this is still that Routing expects me to
use in url hashes - The question is - What if I can't use hashes, but url
looks like I have presented in previous email ?

Thanks,
Piotr

pt., 17 kwi 2020 o 09:20 Harbs  napisał(a):

> This app uses both path based and query based routing:
>
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>
>
> You can see how it’s done here:
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> <
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
>
> > On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki 
> wrote:
> >
> > I'm still looking into the code and it looks like Routing implemented now
> > is not doing what I would expected. Everything is based on "hash"
> property
> > in "location". Instead I need something which is in "search" of
> location. I
> > will wait for your thoughts before I do try to handle stuff on my end.
> >
> > pt., 17 kwi 2020 o 08:30 Piotr Zarzycki 
> > napisał(a):
> >
> >> Hi Guys,
> >>
> >> I really thought that I will be able to use Router [1] based on
> >> documentation and maybe eventually some look to the code [2] - to figure
> >> out how things should be implemented. However it looks like non of the
> >> existing stuff helps me to use in in real world application at all. I
> would
> >> like to throw a simple question.
> >>
> >> I would like to "answer" in my application to following url, catch
> params
> >> and do some actions:
> >>
> >> https://mydomain.com/somefolder/index.html?target=somevalue=
> >> <
> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
> >
> >> somevalue
> >>
> >> How should I do that using Routing in Royale ? :)
> >>
> >> [1] https://apache.github.io/royale-docs/features/routing
> >> [2]
> >>
> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing
> >>
> >> Thanks,
> >> Piotr
> >>
> >> śr., 22 sty 2020 o 13:08 Carlos Rovira 
> >> napisał(a):
> >>
> >>> Hi Harbs,
> >>>
> >>> thanks for taking a look, I'll try to apply your suggestions and see
> if I
> >>> can make it work.
> >>>
> >>> If you plan to work in that new Routing implementation, I'll wait for
> it
> >>> to
> >>> write about it in blog and social media, since better to point people
> to
> >>> the more elaborated one. I as well recommend you to make it end in its
> own
> >>> "Routing.swc" since I think it deserves it.
> >>>
> >>> As Alex dream on possibilities, I want as well to dream and I think
> >>> nowadays, a part from pure client navigation, we have server
> navigation,
> >>> and as other royale features people will soon try to do it. In the
> case of
> >>> Routing, people will want to have URLs for concrete items retrieved
> from
> >>> database and we should support it (was what we discussed before that in
> >>> that case, we'll be able to not have # in the url but just a friendly
> >>> permalink). Hope we can support that, since we'll be great to create,
> lets
> >>> say, a blog app, and as user browse posts and navigate to see a full
> >>> posst,
> >>> he gets as well a friendly URL with no anchors that can be indexable by
> >>> google and retrieved (i.e, the same as Wordpress)
> >>>
> >>> Thanks
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> El mar., 21 ene. 2020 a las 23:57, Alex Harui
> (  )
> >>> escribió:
> >>>
>  If we're dreaming of the future possible implementations, one vision
> is
>  that the route paths are computed from the currentStates of
> Containers.
>  That might have the least setup required, it would almost be
> automatic.
> 
>  IOW, Containers have both a label and currentState property. A routing
>  implementation could scan the DOM for contaners and build the path
> from
>  label/currentState pairs.
> 
>  Of course, I could be wrong...
> 
>  -Alex
> 
> 
>  On 1/21/20, 1:33 PM, "Harbs"  wrote:
> 
> I’ve also been thinking about the router in general, and I came up
>  with an idea on how to do it with beads.
> 
> It’ll probably take me a few days until I implement the changes…
> 
> In addition to , I think we can also offer
>   which would allow different routers to be attached to
>  different places in the application and each level of the hierarchy
> can
>  take care of its own state.
> 
> Harbs
> 
> > On Jan 21, 2020, at 11:29 PM, Harbs 
> >>> wrote:
> >
> > FWIW, I’d like to write a version of a router which allows for
> >>> more
>  declarative syntax for routing to components.
> >
> > Something like this:
> > 
> > 
> > 
> >  >>> state=“layouts_panel”
>  title=“Layouts”/>
> >   title=“Grids”/>
> >  >>> state=“button_panel”
>  

Re: Routing (was Re: Spectrum Components)

[Harbs]

This app uses both path based and query based routing:

https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 


You can see how it’s done here: 
https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
 


> On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki  
> wrote:
> 
> I'm still looking into the code and it looks like Routing implemented now
> is not doing what I would expected. Everything is based on "hash" property
> in "location". Instead I need something which is in "search" of location. I
> will wait for your thoughts before I do try to handle stuff on my end.
> 
> pt., 17 kwi 2020 o 08:30 Piotr Zarzycki 
> napisał(a):
> 
>> Hi Guys,
>> 
>> I really thought that I will be able to use Router [1] based on
>> documentation and maybe eventually some look to the code [2] - to figure
>> out how things should be implemented. However it looks like non of the
>> existing stuff helps me to use in in real world application at all. I would
>> like to throw a simple question.
>> 
>> I would like to "answer" in my application to following url, catch params
>> and do some actions:
>> 
>> https://mydomain.com/somefolder/index.html?target=somevalue=
>> 
>> somevalue
>> 
>> How should I do that using Routing in Royale ? :)
>> 
>> [1] https://apache.github.io/royale-docs/features/routing
>> [2]
>> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing
>> 
>> Thanks,
>> Piotr
>> 
>> śr., 22 sty 2020 o 13:08 Carlos Rovira 
>> napisał(a):
>> 
>>> Hi Harbs,
>>> 
>>> thanks for taking a look, I'll try to apply your suggestions and see if I
>>> can make it work.
>>> 
>>> If you plan to work in that new Routing implementation, I'll wait for it
>>> to
>>> write about it in blog and social media, since better to point people to
>>> the more elaborated one. I as well recommend you to make it end in its own
>>> "Routing.swc" since I think it deserves it.
>>> 
>>> As Alex dream on possibilities, I want as well to dream and I think
>>> nowadays, a part from pure client navigation, we have server navigation,
>>> and as other royale features people will soon try to do it. In the case of
>>> Routing, people will want to have URLs for concrete items retrieved from
>>> database and we should support it (was what we discussed before that in
>>> that case, we'll be able to not have # in the url but just a friendly
>>> permalink). Hope we can support that, since we'll be great to create, lets
>>> say, a blog app, and as user browse posts and navigate to see a full
>>> posst,
>>> he gets as well a friendly URL with no anchors that can be indexable by
>>> google and retrieved (i.e, the same as Wordpress)
>>> 
>>> Thanks
>>> 
>>> 
>>> 
>>> 
>>> 
>>> El mar., 21 ene. 2020 a las 23:57, Alex Harui (>>> )
>>> escribió:
>>> 
 If we're dreaming of the future possible implementations, one vision is
 that the route paths are computed from the currentStates of Containers.
 That might have the least setup required, it would almost be automatic.
 
 IOW, Containers have both a label and currentState property. A routing
 implementation could scan the DOM for contaners and build the path from
 label/currentState pairs.
 
 Of course, I could be wrong...
 
 -Alex
 
 
 On 1/21/20, 1:33 PM, "Harbs"  wrote:
 
I’ve also been thinking about the router in general, and I came up
 with an idea on how to do it with beads.
 
It’ll probably take me a few days until I implement the changes…
 
In addition to , I think we can also offer
  which would allow different routers to be attached to
 different places in the application and each level of the hierarchy can
 take care of its own state.
 
Harbs
 
> On Jan 21, 2020, at 11:29 PM, Harbs 
>>> wrote:
> 
> FWIW, I’d like to write a version of a router which allows for
>>> more
 declarative syntax for routing to components.
> 
> Something like this:
> 
> 
> 
> >> state=“layouts_panel”
 title=“Layouts”/>
> >>> title=“Grids”/>
> >> state=“button_panel”
 title=“Button Bar”/>
> etc...
> 
> 
> 
> 
>> On Jan 21, 2020, at 11:20 PM, Harbs >> >>> harbs.li...@gmail.com>> wrote:
>> 
>> To see what I mean about href links, check out this page and
>>> click
 on a link:
>> http://spectrum-royale/SpectrumBrowser/bin/js-debug/#!link <
 http://spectrum-royale/SpectrumBrowser/bin/js-debug/#!link>
>> 
>> Then use the side panel to navigate to the same pages.
>> 
>>> On Jan 21, 2020, at 11:18 PM, Harbs >>> 

Re: Routing (was Re: Spectrum Components)

[Alex Harui]

What do you want your URLs to look like?  Remember that hash is used to keep 
the browser from reloading the app.

On 4/17/20, 12:13 AM, "Piotr Zarzycki"  wrote:

I'm still looking into the code and it looks like Routing implemented now
is not doing what I would expected. Everything is based on "hash" property
in "location". Instead I need something which is in "search" of location. I
will wait for your thoughts before I do try to handle stuff on my end.

pt., 17 kwi 2020 o 08:30 Piotr Zarzycki 
napisał(a):

> Hi Guys,
>
> I really thought that I will be able to use Router [1] based on
> documentation and maybe eventually some look to the code [2] - to figure
> out how things should be implemented. However it looks like non of the
> existing stuff helps me to use in in real world application at all. I 
would
> like to throw a simple question.
>
> I would like to "answer" in my application to following url, catch params
> and do some actions:
>
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmydomain.com%2Fsomefolder%2Findex.html%3Ftarget%3Dsomevalue%26account%3Ddata=02%7C01%7Caharui%40adobe.com%7C9c2cf4e0d00b4580633708d7e29ed603%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227044141794314sdata=Dv%2FfoygkOuy8EWX3yajDig8oYM9d7ZgqUOGohQd37og%3Dreserved=0
> 

> somevalue
>
> How should I do that using Routing in Royale ? :)
>
> [1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache.github.io%2Froyale-docs%2Ffeatures%2Froutingdata=02%7C01%7Caharui%40adobe.com%7C9c2cf4e0d00b4580633708d7e29ed603%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227044141794314sdata=%2Bq64VNDap48GgbtQtGnIKFQhasrk%2FXb5%2B0bqiTXs328%3Dreserved=0
> [2]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fframeworks%2Fprojects%2FBasic%2Fsrc%2Fmain%2Froyale%2Forg%2Fapache%2Froyale%2Froutingdata=02%7C01%7Caharui%40adobe.com%7C9c2cf4e0d00b4580633708d7e29ed603%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227044141794314sdata=dbfGXbu79kwYBWPwd4i0meomYPr616KOKMT6ok%2FVwX8%3Dreserved=0
>
> Thanks,
> Piotr
>
> śr., 22 sty 2020 o 13:08 Carlos Rovira 
> napisał(a):
>
>> Hi Harbs,
>>
>> thanks for taking a look, I'll try to apply your suggestions and see if I
>> can make it work.
>>
>> If you plan to work in that new Routing implementation, I'll wait for it
>> to
>> write about it in blog and social media, since better to point people to
>> the more elaborated one. I as well recommend you to make it end in its 
own
>> "Routing.swc" since I think it deserves it.
>>
>> As Alex dream on possibilities, I want as well to dream and I think
>> nowadays, a part from pure client navigation, we have server navigation,
>> and as other royale features people will soon try to do it. In the case 
of
>> Routing, people will want to have URLs for concrete items retrieved from
>> database and we should support it (was what we discussed before that in
>> that case, we'll be able to not have # in the url but just a friendly
>> permalink). Hope we can support that, since we'll be great to create, 
lets
>> say, a blog app, and as user browse posts and navigate to see a full
>> posst,
>> he gets as well a friendly URL with no anchors that can be indexable by
>> google and retrieved (i.e, the same as Wordpress)
>>
>> Thanks
>>
>>
>>
>>
>>
>> El mar., 21 ene. 2020 a las 23:57, Alex Harui (> >)
>> escribió:
>>
>> > If we're dreaming of the future possible implementations, one vision is
>> > that the route paths are computed from the currentStates of Containers.
>> > That might have the least setup required, it would almost be automatic.
>> >
>> > IOW, Containers have both a label and currentState property. A routing
>> > implementation could scan the DOM for contaners and build the path from
>> > label/currentState pairs.
>> >
>> > Of course, I could be wrong...
>> >
>> > -Alex
>> >
>> >
>> > On 1/21/20, 1:33 PM, "Harbs"  wrote:
>> >
>> > I’ve also been thinking about the router in general, and I came up
>> > with an idea on how to do it with beads.
>> >
>> > It’ll probably take me a few days until I implement the changes…
>> >
>> > In addition to , I think we can also offer
>> >  which would allow different routers to be 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

I'm still looking into the code and it looks like Routing implemented now
is not doing what I would expected. Everything is based on "hash" property
in "location". Instead I need something which is in "search" of location. I
will wait for your thoughts before I do try to handle stuff on my end.

pt., 17 kwi 2020 o 08:30 Piotr Zarzycki 
napisał(a):

> Hi Guys,
>
> I really thought that I will be able to use Router [1] based on
> documentation and maybe eventually some look to the code [2] - to figure
> out how things should be implemented. However it looks like non of the
> existing stuff helps me to use in in real world application at all. I would
> like to throw a simple question.
>
> I would like to "answer" in my application to following url, catch params
> and do some actions:
>
> https://mydomain.com/somefolder/index.html?target=somevalue=
> 
> somevalue
>
> How should I do that using Routing in Royale ? :)
>
> [1] https://apache.github.io/royale-docs/features/routing
> [2]
> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing
>
> Thanks,
> Piotr
>
> śr., 22 sty 2020 o 13:08 Carlos Rovira 
> napisał(a):
>
>> Hi Harbs,
>>
>> thanks for taking a look, I'll try to apply your suggestions and see if I
>> can make it work.
>>
>> If you plan to work in that new Routing implementation, I'll wait for it
>> to
>> write about it in blog and social media, since better to point people to
>> the more elaborated one. I as well recommend you to make it end in its own
>> "Routing.swc" since I think it deserves it.
>>
>> As Alex dream on possibilities, I want as well to dream and I think
>> nowadays, a part from pure client navigation, we have server navigation,
>> and as other royale features people will soon try to do it. In the case of
>> Routing, people will want to have URLs for concrete items retrieved from
>> database and we should support it (was what we discussed before that in
>> that case, we'll be able to not have # in the url but just a friendly
>> permalink). Hope we can support that, since we'll be great to create, lets
>> say, a blog app, and as user browse posts and navigate to see a full
>> posst,
>> he gets as well a friendly URL with no anchors that can be indexable by
>> google and retrieved (i.e, the same as Wordpress)
>>
>> Thanks
>>
>>
>>
>>
>>
>> El mar., 21 ene. 2020 a las 23:57, Alex Harui (> >)
>> escribió:
>>
>> > If we're dreaming of the future possible implementations, one vision is
>> > that the route paths are computed from the currentStates of Containers.
>> > That might have the least setup required, it would almost be automatic.
>> >
>> > IOW, Containers have both a label and currentState property. A routing
>> > implementation could scan the DOM for contaners and build the path from
>> > label/currentState pairs.
>> >
>> > Of course, I could be wrong...
>> >
>> > -Alex
>> >
>> >
>> > On 1/21/20, 1:33 PM, "Harbs"  wrote:
>> >
>> > I’ve also been thinking about the router in general, and I came up
>> > with an idea on how to do it with beads.
>> >
>> > It’ll probably take me a few days until I implement the changes…
>> >
>> > In addition to , I think we can also offer
>> >  which would allow different routers to be attached to
>> > different places in the application and each level of the hierarchy can
>> > take care of its own state.
>> >
>> > Harbs
>> >
>> > > On Jan 21, 2020, at 11:29 PM, Harbs 
>> wrote:
>> > >
>> > > FWIW, I’d like to write a version of a router which allows for
>> more
>> > declarative syntax for routing to components.
>> > >
>> > > Something like this:
>> > > 
>> > > 
>> > > 
>> > > > state=“layouts_panel”
>> > title=“Layouts”/>
>> > > > > title=“Grids”/>
>> > > > state=“button_panel”
>> > title=“Button Bar”/>
>> > > etc...
>> > > 
>> > > 
>> > > 
>> > >
>> > >> On Jan 21, 2020, at 11:20 PM, Harbs > > > harbs.li...@gmail.com>> wrote:
>> > >>
>> > >> To see what I mean about href links, check out this page and
>> click
>> > on a link:
>> > >> http://spectrum-royale/SpectrumBrowser/bin/js-debug/#!link <
>> > http://spectrum-royale/SpectrumBrowser/bin/js-debug/#!link>
>> > >>
>> > >> Then use the side panel to navigate to the same pages.
>> > >>
>> > >>> On Jan 21, 2020, at 11:18 PM, Harbs > > > wrote:
>> > >>>
>> > >>> The problem is the href in the  element in the nav. The hash
>> is
>> > being changed to “#" after the router redirects.
>> > >>>
>> > >>> You need to handle routing in one of two ways (and not both).
>> > >>> 1. Use setState()
>> > >>> 2. Use href links
>> > >>>
>> > >>> To do #1, you need to remove the href from the  elements (or
>> > use something else such as a div or li).
>> > >>>
>> > >>> If you use 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Hi Guys,

I really thought that I will be able to use Router [1] based on
documentation and maybe eventually some look to the code [2] - to figure
out how things should be implemented. However it looks like non of the
existing stuff helps me to use in in real world application at all. I would
like to throw a simple question.

I would like to "answer" in my application to following url, catch params
and do some actions:

https://mydomain.com/somefolder/index.html?target=somevalue=

somevalue

How should I do that using Routing in Royale ? :)

[1] https://apache.github.io/royale-docs/features/routing
[2]
https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing

Thanks,
Piotr

śr., 22 sty 2020 o 13:08 Carlos Rovira  napisał(a):

> Hi Harbs,
>
> thanks for taking a look, I'll try to apply your suggestions and see if I
> can make it work.
>
> If you plan to work in that new Routing implementation, I'll wait for it to
> write about it in blog and social media, since better to point people to
> the more elaborated one. I as well recommend you to make it end in its own
> "Routing.swc" since I think it deserves it.
>
> As Alex dream on possibilities, I want as well to dream and I think
> nowadays, a part from pure client navigation, we have server navigation,
> and as other royale features people will soon try to do it. In the case of
> Routing, people will want to have URLs for concrete items retrieved from
> database and we should support it (was what we discussed before that in
> that case, we'll be able to not have # in the url but just a friendly
> permalink). Hope we can support that, since we'll be great to create, lets
> say, a blog app, and as user browse posts and navigate to see a full posst,
> he gets as well a friendly URL with no anchors that can be indexable by
> google and retrieved (i.e, the same as Wordpress)
>
> Thanks
>
>
>
>
>
> El mar., 21 ene. 2020 a las 23:57, Alex Harui ()
> escribió:
>
> > If we're dreaming of the future possible implementations, one vision is
> > that the route paths are computed from the currentStates of Containers.
> > That might have the least setup required, it would almost be automatic.
> >
> > IOW, Containers have both a label and currentState property. A routing
> > implementation could scan the DOM for contaners and build the path from
> > label/currentState pairs.
> >
> > Of course, I could be wrong...
> >
> > -Alex
> >
> >
> > On 1/21/20, 1:33 PM, "Harbs"  wrote:
> >
> > I’ve also been thinking about the router in general, and I came up
> > with an idea on how to do it with beads.
> >
> > It’ll probably take me a few days until I implement the changes…
> >
> > In addition to , I think we can also offer
> >  which would allow different routers to be attached to
> > different places in the application and each level of the hierarchy can
> > take care of its own state.
> >
> > Harbs
> >
> > > On Jan 21, 2020, at 11:29 PM, Harbs  wrote:
> > >
> > > FWIW, I’d like to write a version of a router which allows for more
> > declarative syntax for routing to components.
> > >
> > > Something like this:
> > > 
> > > 
> > > 
> > >  > title=“Layouts”/>
> > >  > title=“Grids”/>
> > >  state=“button_panel”
> > title=“Button Bar”/>
> > > etc...
> > > 
> > > 
> > > 
> > >
> > >> On Jan 21, 2020, at 11:20 PM, Harbs   > harbs.li...@gmail.com>> wrote:
> > >>
> > >> To see what I mean about href links, check out this page and click
> > on a link:
> > >> http://spectrum-royale/SpectrumBrowser/bin/js-debug/#!link <
> > http://spectrum-royale/SpectrumBrowser/bin/js-debug/#!link>
> > >>
> > >> Then use the side panel to navigate to the same pages.
> > >>
> > >>> On Jan 21, 2020, at 11:18 PM, Harbs  > > wrote:
> > >>>
> > >>> The problem is the href in the  element in the nav. The hash
> is
> > being changed to “#" after the router redirects.
> > >>>
> > >>> You need to handle routing in one of two ways (and not both).
> > >>> 1. Use setState()
> > >>> 2. Use href links
> > >>>
> > >>> To do #1, you need to remove the href from the  elements (or
> > use something else such as a div or li).
> > >>>
> > >>> If you use href links, the logic of actually switching the views
> > should be handled by the router, so for example in Card, the href should
> > be  #card_panel or #!card_panel.
> > >>>
> > >>> Then setNavSelection will work.
> > >>>
> > >>> The downside of the second method is that I’m not sure how to set
> > the title. Maybe that should be a separate method that can be called.
> > >>>
> >  On Jan 21, 2020, at 8:48 PM, Carlos Rovira <
> > carlosrov...@apache.org > wrote:
> > 
> > 

Re: Routing (was Re: Spectrum Components)

[Carlos Rovira]

Hi Harbs,

thanks for taking a look, I'll try to apply your suggestions and see if I
can make it work.

If you plan to work in that new Routing implementation, I'll wait for it to
write about it in blog and social media, since better to point people to
the more elaborated one. I as well recommend you to make it end in its own
"Routing.swc" since I think it deserves it.

As Alex dream on possibilities, I want as well to dream and I think
nowadays, a part from pure client navigation, we have server navigation,
and as other royale features people will soon try to do it. In the case of
Routing, people will want to have URLs for concrete items retrieved from
database and we should support it (was what we discussed before that in
that case, we'll be able to not have # in the url but just a friendly
permalink). Hope we can support that, since we'll be great to create, lets
say, a blog app, and as user browse posts and navigate to see a full posst,
he gets as well a friendly URL with no anchors that can be indexable by
google and retrieved (i.e, the same as Wordpress)

Thanks





El mar., 21 ene. 2020 a las 23:57, Alex Harui ()
escribió:

> If we're dreaming of the future possible implementations, one vision is
> that the route paths are computed from the currentStates of Containers.
> That might have the least setup required, it would almost be automatic.
>
> IOW, Containers have both a label and currentState property. A routing
> implementation could scan the DOM for contaners and build the path from
> label/currentState pairs.
>
> Of course, I could be wrong...
>
> -Alex
>
>
> On 1/21/20, 1:33 PM, "Harbs"  wrote:
>
> I’ve also been thinking about the router in general, and I came up
> with an idea on how to do it with beads.
>
> It’ll probably take me a few days until I implement the changes…
>
> In addition to , I think we can also offer
>  which would allow different routers to be attached to
> different places in the application and each level of the hierarchy can
> take care of its own state.
>
> Harbs
>
> > On Jan 21, 2020, at 11:29 PM, Harbs  wrote:
> >
> > FWIW, I’d like to write a version of a router which allows for more
> declarative syntax for routing to components.
> >
> > Something like this:
> > 
> > 
> > 
> >  title=“Layouts”/>
> >  title=“Grids”/>
> >  title=“Button Bar”/>
> > etc...
> > 
> > 
> > 
> >
> >> On Jan 21, 2020, at 11:20 PM, Harbs  harbs.li...@gmail.com>> wrote:
> >>
> >> To see what I mean about href links, check out this page and click
> on a link:
> >> http://spectrum-royale/SpectrumBrowser/bin/js-debug/#!link <
> http://spectrum-royale/SpectrumBrowser/bin/js-debug/#!link>
> >>
> >> Then use the side panel to navigate to the same pages.
> >>
> >>> On Jan 21, 2020, at 11:18 PM, Harbs  > wrote:
> >>>
> >>> The problem is the href in the  element in the nav. The hash is
> being changed to “#" after the router redirects.
> >>>
> >>> You need to handle routing in one of two ways (and not both).
> >>> 1. Use setState()
> >>> 2. Use href links
> >>>
> >>> To do #1, you need to remove the href from the  elements (or
> use something else such as a div or li).
> >>>
> >>> If you use href links, the logic of actually switching the views
> should be handled by the router, so for example in Card, the href should
> be  #card_panel or #!card_panel.
> >>>
> >>> Then setNavSelection will work.
> >>>
> >>> The downside of the second method is that I’m not sure how to set
> the title. Maybe that should be a separate method that can be called.
> >>>
>  On Jan 21, 2020, at 8:48 PM, Carlos Rovira <
> carlosrov...@apache.org > wrote:
> 
>  Hi Harbs,
> 
>  this paste is the MainContent.mxml from TDJ with the changes I
> tried:
> 
> 
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fez6aqdata=02%7C01%7Caharui%40adobe.com%7C6962e0e5e92a48ed2e2008d79eb97fc1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637152391862520246sdata=j0E5U49VHJMKuW7u1fMxfKJ85tC2LyPr8ZTAR2yz3%2Fo%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fez6aqdata=02%7C01%7Caharui%40adobe.com%7C6962e0e5e92a48ed2e2008d79eb97fc1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637152391862530246sdata=o%2BV4TiPe5P73KQZBghLkKH70jQ2SbR0V3i0E5tnSVHA%3Dreserved=0
> >
> 
>  You can override whole file in your local and try to compile to
> see
>  results. I'm sure you'll get the right way to work for your code.
> 
>  Thanks
> 
>  Carlos
> 
> 
> 
>  El mar., 21 ene. 2020 a las 19:31, Harbs ( >) escribió:
> 
> > Oops. I thought this email went out 

Re: Routing (was Re: Spectrum Components)

[Alex Harui]

If we're dreaming of the future possible implementations, one vision is that 
the route paths are computed from the currentStates of Containers.  That might 
have the least setup required, it would almost be automatic.

IOW, Containers have both a label and currentState property. A routing 
implementation could scan the DOM for contaners and build the path from 
label/currentState pairs.

Of course, I could be wrong...

-Alex


On 1/21/20, 1:33 PM, "Harbs"  wrote:

I’ve also been thinking about the router in general, and I came up with an 
idea on how to do it with beads.

It’ll probably take me a few days until I implement the changes…

In addition to , I think we can also offer  
which would allow different routers to be attached to different places in the 
application and each level of the hierarchy can take care of its own state.

Harbs

> On Jan 21, 2020, at 11:29 PM, Harbs  wrote:
> 
> FWIW, I’d like to write a version of a router which allows for more 
declarative syntax for routing to components.
> 
> Something like this:
> 
> 
> 
> 
> 
> 
> etc...
> 
> 
> 
> 
>> On Jan 21, 2020, at 11:20 PM, Harbs mailto:harbs.li...@gmail.com>> wrote:
>> 
>> To see what I mean about href links, check out this page and click on a 
link:
>> http://spectrum-royale/SpectrumBrowser/bin/js-debug/#!link 

>> 
>> Then use the side panel to navigate to the same pages.
>> 
>>> On Jan 21, 2020, at 11:18 PM, Harbs mailto:harbs.li...@gmail.com>> wrote:
>>> 
>>> The problem is the href in the  element in the nav. The hash is 
being changed to “#" after the router redirects.
>>> 
>>> You need to handle routing in one of two ways (and not both).
>>> 1. Use setState()
>>> 2. Use href links
>>> 
>>> To do #1, you need to remove the href from the  elements (or use 
something else such as a div or li).
>>> 
>>> If you use href links, the logic of actually switching the views should 
be handled by the router, so for example in Card, the href should be  
#card_panel or #!card_panel.
>>> 
>>> Then setNavSelection will work.
>>> 
>>> The downside of the second method is that I’m not sure how to set the 
title. Maybe that should be a separate method that can be called.
>>> 
 On Jan 21, 2020, at 8:48 PM, Carlos Rovira mailto:carlosrov...@apache.org>> wrote:
 
 Hi Harbs,
 
 this paste is the MainContent.mxml from TDJ with the changes I tried:
 
 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fez6aqdata=02%7C01%7Caharui%40adobe.com%7C6962e0e5e92a48ed2e2008d79eb97fc1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637152391862520246sdata=j0E5U49VHJMKuW7u1fMxfKJ85tC2LyPr8ZTAR2yz3%2Fo%3Dreserved=0
 

 
 You can override whole file in your local and try to compile to see
 results. I'm sure you'll get the right way to work for your code.
 
 Thanks
 
 Carlos
 
 
 
 El mar., 21 ene. 2020 a las 19:31, Harbs (mailto:harbs.li...@gmail.com>>) escribió:
 
> Oops. I thought this email went out yesterday…
> 
> I have very little time today.
> 
> Can you show me the code you tried?
> 
>> On Jan 20, 2020, at 8:01 PM, Carlos Rovira mailto:carlosrov...@apache.org>>
> wrote:
>> 
>> Hi Harbs,
>> 
>> thanks for adding this. I think it will deserve some blog example, 
since
> is
>> something people requested in social media.
>> Can you please add it to Tour De Jewel? I tried but, I get two 
problems:
>> 1.- back/forth buttons are not working
>> 2.- previous button seems to register more than once the same state.
>> Thanks
>> 
>> Carlos
>> 
>> 
>> El lun., 20 ene. 2020 a las 14:38, Harbs (mailto:harbs.li...@gmail.com>>)
> escribió:
>> 
>>> I don’t remember how deep linking worked, but the concept is 
similar.
>>> Routing is the modern term.
>>> 
>>> FWIW, here’s an article on routing strategies vis a vis url paths:
>>> 

Re: Routing (was Re: Spectrum Components)

[Harbs]

I’ve also been thinking about the router in general, and I came up with an idea 
on how to do it with beads.

It’ll probably take me a few days until I implement the changes…

In addition to , I think we can also offer  
which would allow different routers to be attached to different places in the 
application and each level of the hierarchy can take care of its own state.

Harbs

> On Jan 21, 2020, at 11:29 PM, Harbs  wrote:
> 
> FWIW, I’d like to write a version of a router which allows for more 
> declarative syntax for routing to components.
> 
> Something like this:
> 
> 
> 
>  title=“Layouts”/>
> 
>  title=“Button Bar”/>
> etc...
> 
> 
> 
> 
>> On Jan 21, 2020, at 11:20 PM, Harbs > > wrote:
>> 
>> To see what I mean about href links, check out this page and click on a link:
>> http://spectrum-royale/SpectrumBrowser/bin/js-debug/#!link 
>> 
>> 
>> Then use the side panel to navigate to the same pages.
>> 
>>> On Jan 21, 2020, at 11:18 PM, Harbs >> > wrote:
>>> 
>>> The problem is the href in the  element in the nav. The hash is being 
>>> changed to “#" after the router redirects.
>>> 
>>> You need to handle routing in one of two ways (and not both).
>>> 1. Use setState()
>>> 2. Use href links
>>> 
>>> To do #1, you need to remove the href from the  elements (or use 
>>> something else such as a div or li).
>>> 
>>> If you use href links, the logic of actually switching the views should be 
>>> handled by the router, so for example in Card, the href should be  
>>> #card_panel or #!card_panel.
>>> 
>>> Then setNavSelection will work.
>>> 
>>> The downside of the second method is that I’m not sure how to set the 
>>> title. Maybe that should be a separate method that can be called.
>>> 
 On Jan 21, 2020, at 8:48 PM, Carlos Rovira >>> > wrote:
 
 Hi Harbs,
 
 this paste is the MainContent.mxml from TDJ with the changes I tried:
 
 https://paste.apache.org/ez6aq 
 
 You can override whole file in your local and try to compile to see
 results. I'm sure you'll get the right way to work for your code.
 
 Thanks
 
 Carlos
 
 
 
 El mar., 21 ene. 2020 a las 19:31, Harbs (>>> >) escribió:
 
> Oops. I thought this email went out yesterday…
> 
> I have very little time today.
> 
> Can you show me the code you tried?
> 
>> On Jan 20, 2020, at 8:01 PM, Carlos Rovira > >
> wrote:
>> 
>> Hi Harbs,
>> 
>> thanks for adding this. I think it will deserve some blog example, since
> is
>> something people requested in social media.
>> Can you please add it to Tour De Jewel? I tried but, I get two problems:
>> 1.- back/forth buttons are not working
>> 2.- previous button seems to register more than once the same state.
>> Thanks
>> 
>> Carlos
>> 
>> 
>> El lun., 20 ene. 2020 a las 14:38, Harbs (> >)
> escribió:
>> 
>>> I don’t remember how deep linking worked, but the concept is similar.
>>> Routing is the modern term.
>>> 
>>> FWIW, here’s an article on routing strategies vis a vis url paths:
>>> https://codecraft.tv/courses/angular/routing/routing-strategies/ 
>>>  <
>>> https://codecraft.tv/courses/angular/routing/routing-strategies/ 
>>> >
>>> 
 On Jan 20, 2020, at 3:33 PM, Andrew Wetmore >>> >
> wrote:
 
 Thanks for this. In what way is this different from deep linking in
> Flex,
 apart from the name?
 
 On Mon, Jan 20, 2020 at 8:30 AM Harbs >>>  >> harbs.li...@gmail.com >> wrote:
 
> Not sure what you’re looking for. I tried to document the class as
> best
>>> as
> I could:
> 
> 
>>> 
> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>  
> 
>>> <
>>> 
> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
 
> <
> 
>>> 
> 

Re: Routing (was Re: Spectrum Components)

[Harbs]

FWIW, I’d like to write a version of a router which allows for more declarative 
syntax for routing to components.

Something like this:






etc...




> On Jan 21, 2020, at 11:20 PM, Harbs  wrote:
> 
> To see what I mean about href links, check out this page and click on a link:
> http://spectrum-royale/SpectrumBrowser/bin/js-debug/#!link 
> 
> 
> Then use the side panel to navigate to the same pages.
> 
>> On Jan 21, 2020, at 11:18 PM, Harbs > > wrote:
>> 
>> The problem is the href in the  element in the nav. The hash is being 
>> changed to “#" after the router redirects.
>> 
>> You need to handle routing in one of two ways (and not both).
>> 1. Use setState()
>> 2. Use href links
>> 
>> To do #1, you need to remove the href from the  elements (or use 
>> something else such as a div or li).
>> 
>> If you use href links, the logic of actually switching the views should be 
>> handled by the router, so for example in Card, the href should be  
>> #card_panel or #!card_panel.
>> 
>> Then setNavSelection will work.
>> 
>> The downside of the second method is that I’m not sure how to set the title. 
>> Maybe that should be a separate method that can be called.
>> 
>>> On Jan 21, 2020, at 8:48 PM, Carlos Rovira >> > wrote:
>>> 
>>> Hi Harbs,
>>> 
>>> this paste is the MainContent.mxml from TDJ with the changes I tried:
>>> 
>>> https://paste.apache.org/ez6aq 
>>> 
>>> You can override whole file in your local and try to compile to see
>>> results. I'm sure you'll get the right way to work for your code.
>>> 
>>> Thanks
>>> 
>>> Carlos
>>> 
>>> 
>>> 
>>> El mar., 21 ene. 2020 a las 19:31, Harbs () escribió:
>>> 
 Oops. I thought this email went out yesterday…
 
 I have very little time today.
 
 Can you show me the code you tried?
 
> On Jan 20, 2020, at 8:01 PM, Carlos Rovira 
 wrote:
> 
> Hi Harbs,
> 
> thanks for adding this. I think it will deserve some blog example, since
 is
> something people requested in social media.
> Can you please add it to Tour De Jewel? I tried but, I get two problems:
> 1.- back/forth buttons are not working
> 2.- previous button seems to register more than once the same state.
> Thanks
> 
> Carlos
> 
> 
> El lun., 20 ene. 2020 a las 14:38, Harbs ()
 escribió:
> 
>> I don’t remember how deep linking worked, but the concept is similar.
>> Routing is the modern term.
>> 
>> FWIW, here’s an article on routing strategies vis a vis url paths:
>> https://codecraft.tv/courses/angular/routing/routing-strategies/ <
>> https://codecraft.tv/courses/angular/routing/routing-strategies/>
>> 
>>> On Jan 20, 2020, at 3:33 PM, Andrew Wetmore 
 wrote:
>>> 
>>> Thanks for this. In what way is this different from deep linking in
 Flex,
>>> apart from the name?
>>> 
>>> On Mon, Jan 20, 2020 at 8:30 AM Harbs > harbs.li...@gmail.com>> wrote:
>>> 
 Not sure what you’re looking for. I tried to document the class as
 best
>> as
 I could:
 
 
>> 
 https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>> <
>> 
 https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>>> 
 <
 
>> 
 https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>> <
>> 
 https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>>> 
> 
 
 * “Routing” uses the browser history APIs to allow forward and back
 navigation.
 * When the hash of a URL is changed, the router dispatches an event
 * The state of the strand component can be automatically synced to the
 Router routeState.state value.
 * The application can call either setState() to add a point to the
>> browser
 history, or:
 * call renderState() to add a point and trigger a state change in the
>> app
 (i.e. diapatch an event fro the browser)
 
 Helpful?
 
 Some JS frameworks let you declaratively declare routes for a router,
>> that
 might be something worth looking into, but I was not sure what that
>> would
 look like in Royale.
 
> On Jan 20, 2020, at 3:22 PM, Andrew Wetmore 
>> wrote:
> 
> @harbs, would you have a chance to blurt out some text about

Re: Routing (was Re: Spectrum Components)

[Harbs]

To see what I mean about href links, check out this page and click on a link:
http://spectrum-royale/SpectrumBrowser/bin/js-debug/#!link 


Then use the side panel to navigate to the same pages.

> On Jan 21, 2020, at 11:18 PM, Harbs  wrote:
> 
> The problem is the href in the  element in the nav. The hash is being 
> changed to “#" after the router redirects.
> 
> You need to handle routing in one of two ways (and not both).
> 1. Use setState()
> 2. Use href links
> 
> To do #1, you need to remove the href from the  elements (or use something 
> else such as a div or li).
> 
> If you use href links, the logic of actually switching the views should be 
> handled by the router, so for example in Card, the href should be  
> #card_panel or #!card_panel.
> 
> Then setNavSelection will work.
> 
> The downside of the second method is that I’m not sure how to set the title. 
> Maybe that should be a separate method that can be called.
> 
>> On Jan 21, 2020, at 8:48 PM, Carlos Rovira  wrote:
>> 
>> Hi Harbs,
>> 
>> this paste is the MainContent.mxml from TDJ with the changes I tried:
>> 
>> https://paste.apache.org/ez6aq
>> 
>> You can override whole file in your local and try to compile to see
>> results. I'm sure you'll get the right way to work for your code.
>> 
>> Thanks
>> 
>> Carlos
>> 
>> 
>> 
>> El mar., 21 ene. 2020 a las 19:31, Harbs () escribió:
>> 
>>> Oops. I thought this email went out yesterday…
>>> 
>>> I have very little time today.
>>> 
>>> Can you show me the code you tried?
>>> 
 On Jan 20, 2020, at 8:01 PM, Carlos Rovira 
>>> wrote:
 
 Hi Harbs,
 
 thanks for adding this. I think it will deserve some blog example, since
>>> is
 something people requested in social media.
 Can you please add it to Tour De Jewel? I tried but, I get two problems:
 1.- back/forth buttons are not working
 2.- previous button seems to register more than once the same state.
 Thanks
 
 Carlos
 
 
 El lun., 20 ene. 2020 a las 14:38, Harbs ()
>>> escribió:
 
> I don’t remember how deep linking worked, but the concept is similar.
> Routing is the modern term.
> 
> FWIW, here’s an article on routing strategies vis a vis url paths:
> https://codecraft.tv/courses/angular/routing/routing-strategies/ <
> https://codecraft.tv/courses/angular/routing/routing-strategies/>
> 
>> On Jan 20, 2020, at 3:33 PM, Andrew Wetmore 
>>> wrote:
>> 
>> Thanks for this. In what way is this different from deep linking in
>>> Flex,
>> apart from the name?
>> 
>> On Mon, Jan 20, 2020 at 8:30 AM Harbs  harbs.li...@gmail.com>> wrote:
>> 
>>> Not sure what you’re looking for. I tried to document the class as
>>> best
> as
>>> I could:
>>> 
>>> 
> 
>>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
> <
> 
>>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>> 
>>> <
>>> 
> 
>>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
> <
> 
>>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>> 
 
>>> 
>>> * “Routing” uses the browser history APIs to allow forward and back
>>> navigation.
>>> * When the hash of a URL is changed, the router dispatches an event
>>> * The state of the strand component can be automatically synced to the
>>> Router routeState.state value.
>>> * The application can call either setState() to add a point to the
> browser
>>> history, or:
>>> * call renderState() to add a point and trigger a state change in the
> app
>>> (i.e. diapatch an event fro the browser)
>>> 
>>> Helpful?
>>> 
>>> Some JS frameworks let you declaratively declare routes for a router,
> that
>>> might be something worth looking into, but I was not sure what that
> would
>>> look like in Royale.
>>> 
 On Jan 20, 2020, at 3:22 PM, Andrew Wetmore 
> wrote:
 
 @harbs, would you have a chance to blurt out some text about
>>> "routing",
>>> and
 especially how and where it differs from "deep linking" in Flex? We
> need
 some documentation about this and I thought I knew where I was going
>>> to
>>> go
 with it until I saw this as an example of routing.
 
 Does not have to be finished textbullet points and pointers would
> be
 fine. I can then rework it for the help docs.
 
 

Re: Routing (was Re: Spectrum Components)

[Harbs]

The problem is the href in the  element in the nav. The hash is being 
changed to “#" after the router redirects.

You need to handle routing in one of two ways (and not both).
1. Use setState()
2. Use href links

To do #1, you need to remove the href from the  elements (or use something 
else such as a div or li).

If you use href links, the logic of actually switching the views should be 
handled by the router, so for example in Card, the href should be  #card_panel 
or #!card_panel.

Then setNavSelection will work.

The downside of the second method is that I’m not sure how to set the title. 
Maybe that should be a separate method that can be called.

> On Jan 21, 2020, at 8:48 PM, Carlos Rovira  wrote:
> 
> Hi Harbs,
> 
> this paste is the MainContent.mxml from TDJ with the changes I tried:
> 
> https://paste.apache.org/ez6aq
> 
> You can override whole file in your local and try to compile to see
> results. I'm sure you'll get the right way to work for your code.
> 
> Thanks
> 
> Carlos
> 
> 
> 
> El mar., 21 ene. 2020 a las 19:31, Harbs () escribió:
> 
>> Oops. I thought this email went out yesterday…
>> 
>> I have very little time today.
>> 
>> Can you show me the code you tried?
>> 
>>> On Jan 20, 2020, at 8:01 PM, Carlos Rovira 
>> wrote:
>>> 
>>> Hi Harbs,
>>> 
>>> thanks for adding this. I think it will deserve some blog example, since
>> is
>>> something people requested in social media.
>>> Can you please add it to Tour De Jewel? I tried but, I get two problems:
>>> 1.- back/forth buttons are not working
>>> 2.- previous button seems to register more than once the same state.
>>> Thanks
>>> 
>>> Carlos
>>> 
>>> 
>>> El lun., 20 ene. 2020 a las 14:38, Harbs ()
>> escribió:
>>> 
 I don’t remember how deep linking worked, but the concept is similar.
 Routing is the modern term.
 
 FWIW, here’s an article on routing strategies vis a vis url paths:
 https://codecraft.tv/courses/angular/routing/routing-strategies/ <
 https://codecraft.tv/courses/angular/routing/routing-strategies/>
 
> On Jan 20, 2020, at 3:33 PM, Andrew Wetmore 
>> wrote:
> 
> Thanks for this. In what way is this different from deep linking in
>> Flex,
> apart from the name?
> 
> On Mon, Jan 20, 2020 at 8:30 AM Harbs >>> harbs.li...@gmail.com>> wrote:
> 
>> Not sure what you’re looking for. I tried to document the class as
>> best
 as
>> I could:
>> 
>> 
 
>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
 <
 
>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
> 
>> <
>> 
 
>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
 <
 
>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
> 
>>> 
>> 
>> * “Routing” uses the browser history APIs to allow forward and back
>> navigation.
>> * When the hash of a URL is changed, the router dispatches an event
>> * The state of the strand component can be automatically synced to the
>> Router routeState.state value.
>> * The application can call either setState() to add a point to the
 browser
>> history, or:
>> * call renderState() to add a point and trigger a state change in the
 app
>> (i.e. diapatch an event fro the browser)
>> 
>> Helpful?
>> 
>> Some JS frameworks let you declaratively declare routes for a router,
 that
>> might be something worth looking into, but I was not sure what that
 would
>> look like in Royale.
>> 
>>> On Jan 20, 2020, at 3:22 PM, Andrew Wetmore 
 wrote:
>>> 
>>> @harbs, would you have a chance to blurt out some text about
>> "routing",
>> and
>>> especially how and where it differs from "deep linking" in Flex? We
 need
>>> some documentation about this and I thought I knew where I was going
>> to
>> go
>>> with it until I saw this as an example of routing.
>>> 
>>> Does not have to be finished textbullet points and pointers would
 be
>>> fine. I can then rework it for the help docs.
>>> 
>>> Thanks!
>>> 
>>> On Mon, Jan 20, 2020 at 8:09 AM Harbs  wrote:
>>> 
 It’s declared here:
 
 
>> 
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L213
 
 And used here:
 
 
>> 
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L131
 
 here:
 
 

Re: Routing (was Re: Spectrum Components)

[Carlos Rovira]

Hi Harbs,

this paste is the MainContent.mxml from TDJ with the changes I tried:

https://paste.apache.org/ez6aq

You can override whole file in your local and try to compile to see
results. I'm sure you'll get the right way to work for your code.

Thanks

Carlos



El mar., 21 ene. 2020 a las 19:31, Harbs () escribió:

> Oops. I thought this email went out yesterday…
>
> I have very little time today.
>
> Can you show me the code you tried?
>
> > On Jan 20, 2020, at 8:01 PM, Carlos Rovira 
> wrote:
> >
> > Hi Harbs,
> >
> > thanks for adding this. I think it will deserve some blog example, since
> is
> > something people requested in social media.
> > Can you please add it to Tour De Jewel? I tried but, I get two problems:
> > 1.- back/forth buttons are not working
> > 2.- previous button seems to register more than once the same state.
> > Thanks
> >
> > Carlos
> >
> >
> > El lun., 20 ene. 2020 a las 14:38, Harbs ()
> escribió:
> >
> >> I don’t remember how deep linking worked, but the concept is similar.
> >> Routing is the modern term.
> >>
> >> FWIW, here’s an article on routing strategies vis a vis url paths:
> >> https://codecraft.tv/courses/angular/routing/routing-strategies/ <
> >> https://codecraft.tv/courses/angular/routing/routing-strategies/>
> >>
> >>> On Jan 20, 2020, at 3:33 PM, Andrew Wetmore 
> wrote:
> >>>
> >>> Thanks for this. In what way is this different from deep linking in
> Flex,
> >>> apart from the name?
> >>>
> >>> On Mon, Jan 20, 2020 at 8:30 AM Harbs  >> harbs.li...@gmail.com>> wrote:
> >>>
>  Not sure what you’re looking for. I tried to document the class as
> best
> >> as
>  I could:
> 
> 
> >>
> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
> >> <
> >>
> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
> >>>
>  <
> 
> >>
> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
> >> <
> >>
> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
> >>>
> >
> 
>  * “Routing” uses the browser history APIs to allow forward and back
>  navigation.
>  * When the hash of a URL is changed, the router dispatches an event
>  * The state of the strand component can be automatically synced to the
>  Router routeState.state value.
>  * The application can call either setState() to add a point to the
> >> browser
>  history, or:
>  * call renderState() to add a point and trigger a state change in the
> >> app
>  (i.e. diapatch an event fro the browser)
> 
>  Helpful?
> 
>  Some JS frameworks let you declaratively declare routes for a router,
> >> that
>  might be something worth looking into, but I was not sure what that
> >> would
>  look like in Royale.
> 
> > On Jan 20, 2020, at 3:22 PM, Andrew Wetmore 
> >> wrote:
> >
> > @harbs, would you have a chance to blurt out some text about
> "routing",
>  and
> > especially how and where it differs from "deep linking" in Flex? We
> >> need
> > some documentation about this and I thought I knew where I was going
> to
>  go
> > with it until I saw this as an example of routing.
> >
> > Does not have to be finished textbullet points and pointers would
> >> be
> > fine. I can then rework it for the help docs.
> >
> > Thanks!
> >
> > On Mon, Jan 20, 2020 at 8:09 AM Harbs  wrote:
> >
> >> It’s declared here:
> >>
> >>
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L213
> >>
> >> And used here:
> >>
> >>
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L131
> >>
> >> here:
> >>
> >>
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L167
> >>
> >> and here:
> >>
> >>
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/models/Theme.as#L20
> >>
> >>> On Jan 20, 2020, at 3:03 PM, Harbs  wrote:
> >>>
> >>> I created a Router bead which I’m now using in the demo app.
> >>>
> >>> Here’s two very different states:
> >>>
> >>>
> https://unhurdle.github.io/spectrum-royale/#!combobox?colorstop=dark
> >>> https://unhurdle.github.io/spectrum-royale/#!asset_list
> >>>
> >>> Router supports”state”, paths and parameters.
> >>>
> >>> The demo app is using state and parameters.
> >>>
> >>> Harbs
> >>>
>  On Jan 20, 2020, at 

Re: Routing (was Re: Spectrum Components)

[Harbs]

Oops. I thought this email went out yesterday…

I have very little time today.

Can you show me the code you tried?

> On Jan 20, 2020, at 8:01 PM, Carlos Rovira  wrote:
> 
> Hi Harbs,
> 
> thanks for adding this. I think it will deserve some blog example, since is
> something people requested in social media.
> Can you please add it to Tour De Jewel? I tried but, I get two problems:
> 1.- back/forth buttons are not working
> 2.- previous button seems to register more than once the same state.
> Thanks
> 
> Carlos
> 
> 
> El lun., 20 ene. 2020 a las 14:38, Harbs () escribió:
> 
>> I don’t remember how deep linking worked, but the concept is similar.
>> Routing is the modern term.
>> 
>> FWIW, here’s an article on routing strategies vis a vis url paths:
>> https://codecraft.tv/courses/angular/routing/routing-strategies/ <
>> https://codecraft.tv/courses/angular/routing/routing-strategies/>
>> 
>>> On Jan 20, 2020, at 3:33 PM, Andrew Wetmore  wrote:
>>> 
>>> Thanks for this. In what way is this different from deep linking in Flex,
>>> apart from the name?
>>> 
>>> On Mon, Jan 20, 2020 at 8:30 AM Harbs > harbs.li...@gmail.com>> wrote:
>>> 
 Not sure what you’re looking for. I tried to document the class as best
>> as
 I could:
 
 
>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>> <
>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>>> 
 <
 
>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>> <
>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>>> 
> 
 
 * “Routing” uses the browser history APIs to allow forward and back
 navigation.
 * When the hash of a URL is changed, the router dispatches an event
 * The state of the strand component can be automatically synced to the
 Router routeState.state value.
 * The application can call either setState() to add a point to the
>> browser
 history, or:
 * call renderState() to add a point and trigger a state change in the
>> app
 (i.e. diapatch an event fro the browser)
 
 Helpful?
 
 Some JS frameworks let you declaratively declare routes for a router,
>> that
 might be something worth looking into, but I was not sure what that
>> would
 look like in Royale.
 
> On Jan 20, 2020, at 3:22 PM, Andrew Wetmore 
>> wrote:
> 
> @harbs, would you have a chance to blurt out some text about "routing",
 and
> especially how and where it differs from "deep linking" in Flex? We
>> need
> some documentation about this and I thought I knew where I was going to
 go
> with it until I saw this as an example of routing.
> 
> Does not have to be finished textbullet points and pointers would
>> be
> fine. I can then rework it for the help docs.
> 
> Thanks!
> 
> On Mon, Jan 20, 2020 at 8:09 AM Harbs  wrote:
> 
>> It’s declared here:
>> 
>> 
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L213
>> 
>> And used here:
>> 
>> 
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L131
>> 
>> here:
>> 
>> 
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L167
>> 
>> and here:
>> 
>> 
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/models/Theme.as#L20
>> 
>>> On Jan 20, 2020, at 3:03 PM, Harbs  wrote:
>>> 
>>> I created a Router bead which I’m now using in the demo app.
>>> 
>>> Here’s two very different states:
>>> 
>>> https://unhurdle.github.io/spectrum-royale/#!combobox?colorstop=dark
>>> https://unhurdle.github.io/spectrum-royale/#!asset_list
>>> 
>>> Router supports”state”, paths and parameters.
>>> 
>>> The demo app is using state and parameters.
>>> 
>>> Harbs
>>> 
 On Jan 20, 2020, at 10:54 AM, Carlos Rovira <
>> carlosrov...@apache.org>
>> wrote:
 
 Hi Harbs,
 
 about routing, I expect urls will be more like permalinks without
>> the
>> need
 of !# chars. Is this possible?
 
 This:
 https://unhurdle.github.io/spectrum-royale/bar_loader
 
 instead of this:
 https://unhurdle.github.io/spectrum-royale/#!bar_loader
 
 And have it as a library "Routing" that we could use.
 As any other framework out there, is something that they 

Re: Routing (was Re: Spectrum Components)

[Carlos Rovira]

Hi Harbs,

do you have time to add Router to TDJ?
Thanks

El lun., 20 ene. 2020 a las 19:01, Carlos Rovira ()
escribió:

> Hi Harbs,
>
> thanks for adding this. I think it will deserve some blog example, since
> is something people requested in social media.
> Can you please add it to Tour De Jewel? I tried but, I get two problems:
> 1.- back/forth buttons are not working
> 2.- previous button seems to register more than once the same state.
> Thanks
>
> Carlos
>
>
> El lun., 20 ene. 2020 a las 14:38, Harbs ()
> escribió:
>
>> I don’t remember how deep linking worked, but the concept is similar.
>> Routing is the modern term.
>>
>> FWIW, here’s an article on routing strategies vis a vis url paths:
>> https://codecraft.tv/courses/angular/routing/routing-strategies/ <
>> https://codecraft.tv/courses/angular/routing/routing-strategies/>
>>
>> > On Jan 20, 2020, at 3:33 PM, Andrew Wetmore 
>> wrote:
>> >
>> > Thanks for this. In what way is this different from deep linking in
>> Flex,
>> > apart from the name?
>> >
>> > On Mon, Jan 20, 2020 at 8:30 AM Harbs > harbs.li...@gmail.com>> wrote:
>> >
>> >> Not sure what you’re looking for. I tried to document the class as
>> best as
>> >> I could:
>> >>
>> >>
>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>> <
>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>> >
>> >> <
>> >>
>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>> <
>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>> >
>> >>>
>> >>
>> >> * “Routing” uses the browser history APIs to allow forward and back
>> >> navigation.
>> >> * When the hash of a URL is changed, the router dispatches an event
>> >> * The state of the strand component can be automatically synced to the
>> >> Router routeState.state value.
>> >> * The application can call either setState() to add a point to the
>> browser
>> >> history, or:
>> >> * call renderState() to add a point and trigger a state change in the
>> app
>> >> (i.e. diapatch an event fro the browser)
>> >>
>> >> Helpful?
>> >>
>> >> Some JS frameworks let you declaratively declare routes for a router,
>> that
>> >> might be something worth looking into, but I was not sure what that
>> would
>> >> look like in Royale.
>> >>
>> >>> On Jan 20, 2020, at 3:22 PM, Andrew Wetmore 
>> wrote:
>> >>>
>> >>> @harbs, would you have a chance to blurt out some text about
>> "routing",
>> >> and
>> >>> especially how and where it differs from "deep linking" in Flex? We
>> need
>> >>> some documentation about this and I thought I knew where I was going
>> to
>> >> go
>> >>> with it until I saw this as an example of routing.
>> >>>
>> >>> Does not have to be finished textbullet points and pointers would
>> be
>> >>> fine. I can then rework it for the help docs.
>> >>>
>> >>> Thanks!
>> >>>
>> >>> On Mon, Jan 20, 2020 at 8:09 AM Harbs  wrote:
>> >>>
>>  It’s declared here:
>> 
>> 
>> >>
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L213
>> 
>>  And used here:
>> 
>> 
>> >>
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L131
>> 
>>  here:
>> 
>> 
>> >>
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L167
>> 
>>  and here:
>> 
>> 
>> >>
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/models/Theme.as#L20
>> 
>> > On Jan 20, 2020, at 3:03 PM, Harbs  wrote:
>> >
>> > I created a Router bead which I’m now using in the demo app.
>> >
>> > Here’s two very different states:
>> >
>> >
>> https://unhurdle.github.io/spectrum-royale/#!combobox?colorstop=dark
>> > https://unhurdle.github.io/spectrum-royale/#!asset_list
>> >
>> > Router supports”state”, paths and parameters.
>> >
>> > The demo app is using state and parameters.
>> >
>> > Harbs
>> >
>> >> On Jan 20, 2020, at 10:54 AM, Carlos Rovira <
>> carlosrov...@apache.org>
>>  wrote:
>> >>
>> >> Hi Harbs,
>> >>
>> >> about routing, I expect urls will be more like permalinks without
>> the
>>  need
>> >> of !# chars. Is this possible?
>> >>
>> >> This:
>> >> https://unhurdle.github.io/spectrum-royale/bar_loader
>> >>
>> >> instead of this:
>> >> https://unhurdle.github.io/spectrum-royale/#!bar_loader
>> >>
>> >> And have it as a library "Routing" that we could use.
>> >> As any other framework out there, is something 

Re: Routing (was Re: Spectrum Components)

[Carlos Rovira]

Hi Harbs,

thanks for adding this. I think it will deserve some blog example, since is
something people requested in social media.
Can you please add it to Tour De Jewel? I tried but, I get two problems:
1.- back/forth buttons are not working
2.- previous button seems to register more than once the same state.
Thanks

Carlos


El lun., 20 ene. 2020 a las 14:38, Harbs () escribió:

> I don’t remember how deep linking worked, but the concept is similar.
> Routing is the modern term.
>
> FWIW, here’s an article on routing strategies vis a vis url paths:
> https://codecraft.tv/courses/angular/routing/routing-strategies/ <
> https://codecraft.tv/courses/angular/routing/routing-strategies/>
>
> > On Jan 20, 2020, at 3:33 PM, Andrew Wetmore  wrote:
> >
> > Thanks for this. In what way is this different from deep linking in Flex,
> > apart from the name?
> >
> > On Mon, Jan 20, 2020 at 8:30 AM Harbs  harbs.li...@gmail.com>> wrote:
> >
> >> Not sure what you’re looking for. I tried to document the class as best
> as
> >> I could:
> >>
> >>
> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
> <
> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
> >
> >> <
> >>
> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
> <
> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
> >
> >>>
> >>
> >> * “Routing” uses the browser history APIs to allow forward and back
> >> navigation.
> >> * When the hash of a URL is changed, the router dispatches an event
> >> * The state of the strand component can be automatically synced to the
> >> Router routeState.state value.
> >> * The application can call either setState() to add a point to the
> browser
> >> history, or:
> >> * call renderState() to add a point and trigger a state change in the
> app
> >> (i.e. diapatch an event fro the browser)
> >>
> >> Helpful?
> >>
> >> Some JS frameworks let you declaratively declare routes for a router,
> that
> >> might be something worth looking into, but I was not sure what that
> would
> >> look like in Royale.
> >>
> >>> On Jan 20, 2020, at 3:22 PM, Andrew Wetmore 
> wrote:
> >>>
> >>> @harbs, would you have a chance to blurt out some text about "routing",
> >> and
> >>> especially how and where it differs from "deep linking" in Flex? We
> need
> >>> some documentation about this and I thought I knew where I was going to
> >> go
> >>> with it until I saw this as an example of routing.
> >>>
> >>> Does not have to be finished textbullet points and pointers would
> be
> >>> fine. I can then rework it for the help docs.
> >>>
> >>> Thanks!
> >>>
> >>> On Mon, Jan 20, 2020 at 8:09 AM Harbs  wrote:
> >>>
>  It’s declared here:
> 
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L213
> 
>  And used here:
> 
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L131
> 
>  here:
> 
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L167
> 
>  and here:
> 
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/models/Theme.as#L20
> 
> > On Jan 20, 2020, at 3:03 PM, Harbs  wrote:
> >
> > I created a Router bead which I’m now using in the demo app.
> >
> > Here’s two very different states:
> >
> > https://unhurdle.github.io/spectrum-royale/#!combobox?colorstop=dark
> > https://unhurdle.github.io/spectrum-royale/#!asset_list
> >
> > Router supports”state”, paths and parameters.
> >
> > The demo app is using state and parameters.
> >
> > Harbs
> >
> >> On Jan 20, 2020, at 10:54 AM, Carlos Rovira <
> carlosrov...@apache.org>
>  wrote:
> >>
> >> Hi Harbs,
> >>
> >> about routing, I expect urls will be more like permalinks without
> the
>  need
> >> of !# chars. Is this possible?
> >>
> >> This:
> >> https://unhurdle.github.io/spectrum-royale/bar_loader
> >>
> >> instead of this:
> >> https://unhurdle.github.io/spectrum-royale/#!bar_loader
> >>
> >> And have it as a library "Routing" that we could use.
> >> As any other framework out there, is something that they support
> with
>  some
> >> API, and I think is one of the things we already don't offer.
> >> Would be great to have for 1.0, since is something people will want
> >> very
> >> soon in their tests for sure.
> >>
> >> What do you think?
> >>
> >> 

Re: Routing (was Re: Spectrum Components)

[Harbs]

I don’t remember how deep linking worked, but the concept is similar. Routing 
is the modern term.

FWIW, here’s an article on routing strategies vis a vis url paths:
https://codecraft.tv/courses/angular/routing/routing-strategies/ 


> On Jan 20, 2020, at 3:33 PM, Andrew Wetmore  wrote:
> 
> Thanks for this. In what way is this different from deep linking in Flex,
> apart from the name?
> 
> On Mon, Jan 20, 2020 at 8:30 AM Harbs  > wrote:
> 
>> Not sure what you’re looking for. I tried to document the class as best as
>> I could:
>> 
>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>>  
>> 
>> <
>> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
>>  
>> 
>>> 
>> 
>> * “Routing” uses the browser history APIs to allow forward and back
>> navigation.
>> * When the hash of a URL is changed, the router dispatches an event
>> * The state of the strand component can be automatically synced to the
>> Router routeState.state value.
>> * The application can call either setState() to add a point to the browser
>> history, or:
>> * call renderState() to add a point and trigger a state change in the app
>> (i.e. diapatch an event fro the browser)
>> 
>> Helpful?
>> 
>> Some JS frameworks let you declaratively declare routes for a router, that
>> might be something worth looking into, but I was not sure what that would
>> look like in Royale.
>> 
>>> On Jan 20, 2020, at 3:22 PM, Andrew Wetmore  wrote:
>>> 
>>> @harbs, would you have a chance to blurt out some text about "routing",
>> and
>>> especially how and where it differs from "deep linking" in Flex? We need
>>> some documentation about this and I thought I knew where I was going to
>> go
>>> with it until I saw this as an example of routing.
>>> 
>>> Does not have to be finished textbullet points and pointers would be
>>> fine. I can then rework it for the help docs.
>>> 
>>> Thanks!
>>> 
>>> On Mon, Jan 20, 2020 at 8:09 AM Harbs  wrote:
>>> 
 It’s declared here:
 
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L213
 
 And used here:
 
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L131
 
 here:
 
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L167
 
 and here:
 
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/models/Theme.as#L20
 
> On Jan 20, 2020, at 3:03 PM, Harbs  wrote:
> 
> I created a Router bead which I’m now using in the demo app.
> 
> Here’s two very different states:
> 
> https://unhurdle.github.io/spectrum-royale/#!combobox?colorstop=dark
> https://unhurdle.github.io/spectrum-royale/#!asset_list
> 
> Router supports”state”, paths and parameters.
> 
> The demo app is using state and parameters.
> 
> Harbs
> 
>> On Jan 20, 2020, at 10:54 AM, Carlos Rovira 
 wrote:
>> 
>> Hi Harbs,
>> 
>> about routing, I expect urls will be more like permalinks without the
 need
>> of !# chars. Is this possible?
>> 
>> This:
>> https://unhurdle.github.io/spectrum-royale/bar_loader
>> 
>> instead of this:
>> https://unhurdle.github.io/spectrum-royale/#!bar_loader
>> 
>> And have it as a library "Routing" that we could use.
>> As any other framework out there, is something that they support with
 some
>> API, and I think is one of the things we already don't offer.
>> Would be great to have for 1.0, since is something people will want
>> very
>> soon in their tests for sure.
>> 
>> What do you think?
>> 
>> Carlos
>> 
>> 
>> 
>> El lun., 20 ene. 2020 a las 7:31, Harbs ()
 escribió:
>> 
>>> Good catch. Thanks!
>>> 
 On Jan 20, 2020, at 1:52 AM, Andrew Wetmore 
 wrote:
 
 Small thing, but I think the code example for "Avatar" is reversed,
 implying that the first of the two images is disabled rather than
>> the
 second.
 
 On Sun, Jan 19, 2020 at 6:42 PM Harbs 
>> wrote:
 
> FYI, I just added routing to the demo app. It was pretty painless,
> although I’d like to make it even simpler…
> 
> 

Re: Routing (was Re: Spectrum Components)

[Andrew Wetmore]

Thanks for this. In what way is this different from deep linking in Flex,
apart from the name?

On Mon, Jan 20, 2020 at 8:30 AM Harbs  wrote:

> Not sure what you’re looking for. I tried to document the class as best as
> I could:
>
> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
> <
> https://github.com/apache/royale-asjs/blob/6cbc5559bcc99bf2ceb3e033747ca3680b3b0d91/frameworks/projects/Basic/src/main/royale/org/apache/royale/routing/Router.as
> >
>
> * “Routing” uses the browser history APIs to allow forward and back
> navigation.
> * When the hash of a URL is changed, the router dispatches an event
> * The state of the strand component can be automatically synced to the
> Router routeState.state value.
> * The application can call either setState() to add a point to the browser
> history, or:
> * call renderState() to add a point and trigger a state change in the app
> (i.e. diapatch an event fro the browser)
>
> Helpful?
>
> Some JS frameworks let you declaratively declare routes for a router, that
> might be something worth looking into, but I was not sure what that would
> look like in Royale.
>
> > On Jan 20, 2020, at 3:22 PM, Andrew Wetmore  wrote:
> >
> > @harbs, would you have a chance to blurt out some text about "routing",
> and
> > especially how and where it differs from "deep linking" in Flex? We need
> > some documentation about this and I thought I knew where I was going to
> go
> > with it until I saw this as an example of routing.
> >
> > Does not have to be finished textbullet points and pointers would be
> > fine. I can then rework it for the help docs.
> >
> > Thanks!
> >
> > On Mon, Jan 20, 2020 at 8:09 AM Harbs  wrote:
> >
> >> It’s declared here:
> >>
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L213
> >>
> >> And used here:
> >>
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L131
> >>
> >> here:
> >>
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L167
> >>
> >> and here:
> >>
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/models/Theme.as#L20
> >>
> >>> On Jan 20, 2020, at 3:03 PM, Harbs  wrote:
> >>>
> >>> I created a Router bead which I’m now using in the demo app.
> >>>
> >>> Here’s two very different states:
> >>>
> >>> https://unhurdle.github.io/spectrum-royale/#!combobox?colorstop=dark
> >>> https://unhurdle.github.io/spectrum-royale/#!asset_list
> >>>
> >>> Router supports”state”, paths and parameters.
> >>>
> >>> The demo app is using state and parameters.
> >>>
> >>> Harbs
> >>>
>  On Jan 20, 2020, at 10:54 AM, Carlos Rovira 
> >> wrote:
> 
>  Hi Harbs,
> 
>  about routing, I expect urls will be more like permalinks without the
> >> need
>  of !# chars. Is this possible?
> 
>  This:
>  https://unhurdle.github.io/spectrum-royale/bar_loader
> 
>  instead of this:
>  https://unhurdle.github.io/spectrum-royale/#!bar_loader
> 
>  And have it as a library "Routing" that we could use.
>  As any other framework out there, is something that they support with
> >> some
>  API, and I think is one of the things we already don't offer.
>  Would be great to have for 1.0, since is something people will want
> very
>  soon in their tests for sure.
> 
>  What do you think?
> 
>  Carlos
> 
> 
> 
>  El lun., 20 ene. 2020 a las 7:31, Harbs ()
> >> escribió:
> 
> > Good catch. Thanks!
> >
> >> On Jan 20, 2020, at 1:52 AM, Andrew Wetmore 
> >> wrote:
> >>
> >> Small thing, but I think the code example for "Avatar" is reversed,
> >> implying that the first of the two images is disabled rather than
> the
> >> second.
> >>
> >> On Sun, Jan 19, 2020 at 6:42 PM Harbs 
> wrote:
> >>
> >>> FYI, I just added routing to the demo app. It was pretty painless,
> >>> although I’d like to make it even simpler…
> >>>
> >>> https://unhurdle.github.io/spectrum-royale/#!bar_loader <
> >>> https://unhurdle.github.io/spectrum-royale/#!bar_loader>
> >>>
> >>>
>  On Jan 15, 2020, at 7:08 PM, Harbs  wrote:
> 
>  FYI, I just updated the project readme with a link to the demo and
> >> some
> >>> markup to show what a full Royale app looks like:
>  https://github.com/unhurdle/spectrum-royale <
> >>> https://github.com/unhurdle/spectrum-royale>
> 
> 
> > On Jan 13, 2020, at 1:30 AM, Harbs   >>> harbs.li...@gmail.com>> wrote:
> >
> > FYI, I’ve been working on filling out a demo the Spectrum Royale
> >>> components:
> > https://unhurdle.github.io/spectrum-royale/ <
> >>> https://unhurdle.github.io/spectrum-royale/>
> >
> 

Re: Spectrum Components

[Andrew Wetmore]

@harbs, would you have a chance to blurt out some text about "routing", and
especially how and where it differs from "deep linking" in Flex? We need
some documentation about this and I thought I knew where I was going to go
with it until I saw this as an example of routing.

Does not have to be finished textbullet points and pointers would be
fine. I can then rework it for the help docs.

Thanks!

On Mon, Jan 20, 2020 at 8:09 AM Harbs  wrote:

> It’s declared here:
>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L213
>
> And used here:
>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L131
>
> here:
>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L167
>
> and here:
>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/models/Theme.as#L20
>
> > On Jan 20, 2020, at 3:03 PM, Harbs  wrote:
> >
> > I created a Router bead which I’m now using in the demo app.
> >
> > Here’s two very different states:
> >
> > https://unhurdle.github.io/spectrum-royale/#!combobox?colorstop=dark
> > https://unhurdle.github.io/spectrum-royale/#!asset_list
> >
> > Router supports”state”, paths and parameters.
> >
> > The demo app is using state and parameters.
> >
> > Harbs
> >
> >> On Jan 20, 2020, at 10:54 AM, Carlos Rovira 
> wrote:
> >>
> >> Hi Harbs,
> >>
> >> about routing, I expect urls will be more like permalinks without the
> need
> >> of !# chars. Is this possible?
> >>
> >> This:
> >> https://unhurdle.github.io/spectrum-royale/bar_loader
> >>
> >> instead of this:
> >> https://unhurdle.github.io/spectrum-royale/#!bar_loader
> >>
> >> And have it as a library "Routing" that we could use.
> >> As any other framework out there, is something that they support with
> some
> >> API, and I think is one of the things we already don't offer.
> >> Would be great to have for 1.0, since is something people will want very
> >> soon in their tests for sure.
> >>
> >> What do you think?
> >>
> >> Carlos
> >>
> >>
> >>
> >> El lun., 20 ene. 2020 a las 7:31, Harbs ()
> escribió:
> >>
> >>> Good catch. Thanks!
> >>>
>  On Jan 20, 2020, at 1:52 AM, Andrew Wetmore 
> wrote:
> 
>  Small thing, but I think the code example for "Avatar" is reversed,
>  implying that the first of the two images is disabled rather than the
>  second.
> 
>  On Sun, Jan 19, 2020 at 6:42 PM Harbs  wrote:
> 
> > FYI, I just added routing to the demo app. It was pretty painless,
> > although I’d like to make it even simpler…
> >
> > https://unhurdle.github.io/spectrum-royale/#!bar_loader <
> > https://unhurdle.github.io/spectrum-royale/#!bar_loader>
> >
> >
> >> On Jan 15, 2020, at 7:08 PM, Harbs  wrote:
> >>
> >> FYI, I just updated the project readme with a link to the demo and
> some
> > markup to show what a full Royale app looks like:
> >> https://github.com/unhurdle/spectrum-royale <
> > https://github.com/unhurdle/spectrum-royale>
> >>
> >>
> >>> On Jan 13, 2020, at 1:30 AM, Harbs  > harbs.li...@gmail.com>> wrote:
> >>>
> >>> FYI, I’ve been working on filling out a demo the Spectrum Royale
> > components:
> >>> https://unhurdle.github.io/spectrum-royale/ <
> > https://unhurdle.github.io/spectrum-royale/>
> >>>
> >>> I’m going to be filling them out over the next week…
> >>>
> >>> Harbs
> >>
> >
> >
> 
>  --
>  Andrew Wetmore
> 
>  http://cottage14.blogspot.com/
> >>>
> >>>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Spectrum Components

[Harbs]

It’s declared here:
https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L213

And used here:
https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L131

here:
https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/MainView.mxml#L167

and here:
https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/models/Theme.as#L20

> On Jan 20, 2020, at 3:03 PM, Harbs  wrote:
> 
> I created a Router bead which I’m now using in the demo app.
> 
> Here’s two very different states:
> 
> https://unhurdle.github.io/spectrum-royale/#!combobox?colorstop=dark
> https://unhurdle.github.io/spectrum-royale/#!asset_list
> 
> Router supports”state”, paths and parameters.
> 
> The demo app is using state and parameters.
> 
> Harbs
> 
>> On Jan 20, 2020, at 10:54 AM, Carlos Rovira  wrote:
>> 
>> Hi Harbs,
>> 
>> about routing, I expect urls will be more like permalinks without the need
>> of !# chars. Is this possible?
>> 
>> This:
>> https://unhurdle.github.io/spectrum-royale/bar_loader
>> 
>> instead of this:
>> https://unhurdle.github.io/spectrum-royale/#!bar_loader
>> 
>> And have it as a library "Routing" that we could use.
>> As any other framework out there, is something that they support with some
>> API, and I think is one of the things we already don't offer.
>> Would be great to have for 1.0, since is something people will want very
>> soon in their tests for sure.
>> 
>> What do you think?
>> 
>> Carlos
>> 
>> 
>> 
>> El lun., 20 ene. 2020 a las 7:31, Harbs () escribió:
>> 
>>> Good catch. Thanks!
>>> 
 On Jan 20, 2020, at 1:52 AM, Andrew Wetmore  wrote:
 
 Small thing, but I think the code example for "Avatar" is reversed,
 implying that the first of the two images is disabled rather than the
 second.
 
 On Sun, Jan 19, 2020 at 6:42 PM Harbs  wrote:
 
> FYI, I just added routing to the demo app. It was pretty painless,
> although I’d like to make it even simpler…
> 
> https://unhurdle.github.io/spectrum-royale/#!bar_loader <
> https://unhurdle.github.io/spectrum-royale/#!bar_loader>
> 
> 
>> On Jan 15, 2020, at 7:08 PM, Harbs  wrote:
>> 
>> FYI, I just updated the project readme with a link to the demo and some
> markup to show what a full Royale app looks like:
>> https://github.com/unhurdle/spectrum-royale <
> https://github.com/unhurdle/spectrum-royale>
>> 
>> 
>>> On Jan 13, 2020, at 1:30 AM, Harbs  harbs.li...@gmail.com>> wrote:
>>> 
>>> FYI, I’ve been working on filling out a demo the Spectrum Royale
> components:
>>> https://unhurdle.github.io/spectrum-royale/ <
> https://unhurdle.github.io/spectrum-royale/>
>>> 
>>> I’m going to be filling them out over the next week…
>>> 
>>> Harbs
>> 
> 
> 
 
 --
 Andrew Wetmore
 
 http://cottage14.blogspot.com/
>>> 
>>> 
>> 
>> -- 
>> Carlos Rovira
>> http://about.me/carlosrovira
> 

Re: Spectrum Components

[Harbs]

I created a Router bead which I’m now using in the demo app.

Here’s two very different states:

https://unhurdle.github.io/spectrum-royale/#!combobox?colorstop=dark
https://unhurdle.github.io/spectrum-royale/#!asset_list

Router supports”state”, paths and parameters.

The demo app is using state and parameters.

Harbs

> On Jan 20, 2020, at 10:54 AM, Carlos Rovira  wrote:
> 
> Hi Harbs,
> 
> about routing, I expect urls will be more like permalinks without the need
> of !# chars. Is this possible?
> 
> This:
> https://unhurdle.github.io/spectrum-royale/bar_loader
> 
> instead of this:
> https://unhurdle.github.io/spectrum-royale/#!bar_loader
> 
> And have it as a library "Routing" that we could use.
> As any other framework out there, is something that they support with some
> API, and I think is one of the things we already don't offer.
> Would be great to have for 1.0, since is something people will want very
> soon in their tests for sure.
> 
> What do you think?
> 
> Carlos
> 
> 
> 
> El lun., 20 ene. 2020 a las 7:31, Harbs () escribió:
> 
>> Good catch. Thanks!
>> 
>>> On Jan 20, 2020, at 1:52 AM, Andrew Wetmore  wrote:
>>> 
>>> Small thing, but I think the code example for "Avatar" is reversed,
>>> implying that the first of the two images is disabled rather than the
>>> second.
>>> 
>>> On Sun, Jan 19, 2020 at 6:42 PM Harbs  wrote:
>>> 
 FYI, I just added routing to the demo app. It was pretty painless,
 although I’d like to make it even simpler…
 
 https://unhurdle.github.io/spectrum-royale/#!bar_loader <
 https://unhurdle.github.io/spectrum-royale/#!bar_loader>
 
 
> On Jan 15, 2020, at 7:08 PM, Harbs  wrote:
> 
> FYI, I just updated the project readme with a link to the demo and some
 markup to show what a full Royale app looks like:
> https://github.com/unhurdle/spectrum-royale <
 https://github.com/unhurdle/spectrum-royale>
> 
> 
>> On Jan 13, 2020, at 1:30 AM, Harbs >>> harbs.li...@gmail.com>> wrote:
>> 
>> FYI, I’ve been working on filling out a demo the Spectrum Royale
 components:
>> https://unhurdle.github.io/spectrum-royale/ <
 https://unhurdle.github.io/spectrum-royale/>
>> 
>> I’m going to be filling them out over the next week…
>> 
>> Harbs
> 
 
 
>>> 
>>> --
>>> Andrew Wetmore
>>> 
>>> http://cottage14.blogspot.com/
>> 
>> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: Spectrum Components

[Harbs]

AFAIK, routing needs to have the hash unless you implement fancy rewrites on 
the server.

hashbang is the recommended strategy for web crawlers.

https://websiteseochecker.com/blog/hashbang-seo-in-2019-a-complete-guide-to-hash-bang-urls/
 



> On Jan 20, 2020, at 10:54 AM, Carlos Rovira  wrote:
> 
> Hi Harbs,
> 
> about routing, I expect urls will be more like permalinks without the need
> of !# chars. Is this possible?
> 
> This:
> https://unhurdle.github.io/spectrum-royale/bar_loader
> 
> instead of this:
> https://unhurdle.github.io/spectrum-royale/#!bar_loader
> 
> And have it as a library "Routing" that we could use.
> As any other framework out there, is something that they support with some
> API, and I think is one of the things we already don't offer.
> Would be great to have for 1.0, since is something people will want very
> soon in their tests for sure.
> 
> What do you think?
> 
> Carlos
> 
> 
> 
> El lun., 20 ene. 2020 a las 7:31, Harbs () escribió:
> 
>> Good catch. Thanks!
>> 
>>> On Jan 20, 2020, at 1:52 AM, Andrew Wetmore  wrote:
>>> 
>>> Small thing, but I think the code example for "Avatar" is reversed,
>>> implying that the first of the two images is disabled rather than the
>>> second.
>>> 
>>> On Sun, Jan 19, 2020 at 6:42 PM Harbs  wrote:
>>> 
 FYI, I just added routing to the demo app. It was pretty painless,
 although I’d like to make it even simpler…
 
 https://unhurdle.github.io/spectrum-royale/#!bar_loader <
 https://unhurdle.github.io/spectrum-royale/#!bar_loader>
 
 
> On Jan 15, 2020, at 7:08 PM, Harbs  wrote:
> 
> FYI, I just updated the project readme with a link to the demo and some
 markup to show what a full Royale app looks like:
> https://github.com/unhurdle/spectrum-royale <
 https://github.com/unhurdle/spectrum-royale>
> 
> 
>> On Jan 13, 2020, at 1:30 AM, Harbs >>> harbs.li...@gmail.com>> wrote:
>> 
>> FYI, I’ve been working on filling out a demo the Spectrum Royale
 components:
>> https://unhurdle.github.io/spectrum-royale/ <
 https://unhurdle.github.io/spectrum-royale/>
>> 
>> I’m going to be filling them out over the next week…
>> 
>> Harbs
> 
 
 
>>> 
>>> --
>>> Andrew Wetmore
>>> 
>>> http://cottage14.blogspot.com/
>> 
>> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: Spectrum Components

[Carlos Rovira]

Hi Harbs,

about routing, I expect urls will be more like permalinks without the need
of !# chars. Is this possible?

This:
https://unhurdle.github.io/spectrum-royale/bar_loader

instead of this:
https://unhurdle.github.io/spectrum-royale/#!bar_loader

And have it as a library "Routing" that we could use.
As any other framework out there, is something that they support with some
API, and I think is one of the things we already don't offer.
Would be great to have for 1.0, since is something people will want very
soon in their tests for sure.

What do you think?

Carlos



El lun., 20 ene. 2020 a las 7:31, Harbs () escribió:

> Good catch. Thanks!
>
> > On Jan 20, 2020, at 1:52 AM, Andrew Wetmore  wrote:
> >
> > Small thing, but I think the code example for "Avatar" is reversed,
> > implying that the first of the two images is disabled rather than the
> > second.
> >
> > On Sun, Jan 19, 2020 at 6:42 PM Harbs  wrote:
> >
> >> FYI, I just added routing to the demo app. It was pretty painless,
> >> although I’d like to make it even simpler…
> >>
> >> https://unhurdle.github.io/spectrum-royale/#!bar_loader <
> >> https://unhurdle.github.io/spectrum-royale/#!bar_loader>
> >>
> >>
> >>> On Jan 15, 2020, at 7:08 PM, Harbs  wrote:
> >>>
> >>> FYI, I just updated the project readme with a link to the demo and some
> >> markup to show what a full Royale app looks like:
> >>> https://github.com/unhurdle/spectrum-royale <
> >> https://github.com/unhurdle/spectrum-royale>
> >>>
> >>>
>  On Jan 13, 2020, at 1:30 AM, Harbs  >> harbs.li...@gmail.com>> wrote:
> 
>  FYI, I’ve been working on filling out a demo the Spectrum Royale
> >> components:
>  https://unhurdle.github.io/spectrum-royale/ <
> >> https://unhurdle.github.io/spectrum-royale/>
> 
>  I’m going to be filling them out over the next week…
> 
>  Harbs
> >>>
> >>
> >>
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
>
>

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

Re: Spectrum Components

[Harbs]

Good catch. Thanks!

> On Jan 20, 2020, at 1:52 AM, Andrew Wetmore  wrote:
> 
> Small thing, but I think the code example for "Avatar" is reversed,
> implying that the first of the two images is disabled rather than the
> second.
> 
> On Sun, Jan 19, 2020 at 6:42 PM Harbs  wrote:
> 
>> FYI, I just added routing to the demo app. It was pretty painless,
>> although I’d like to make it even simpler…
>> 
>> https://unhurdle.github.io/spectrum-royale/#!bar_loader <
>> https://unhurdle.github.io/spectrum-royale/#!bar_loader>
>> 
>> 
>>> On Jan 15, 2020, at 7:08 PM, Harbs  wrote:
>>> 
>>> FYI, I just updated the project readme with a link to the demo and some
>> markup to show what a full Royale app looks like:
>>> https://github.com/unhurdle/spectrum-royale <
>> https://github.com/unhurdle/spectrum-royale>
>>> 
>>> 
 On Jan 13, 2020, at 1:30 AM, Harbs > harbs.li...@gmail.com>> wrote:
 
 FYI, I’ve been working on filling out a demo the Spectrum Royale
>> components:
 https://unhurdle.github.io/spectrum-royale/ <
>> https://unhurdle.github.io/spectrum-royale/>
 
 I’m going to be filling them out over the next week…
 
 Harbs
>>> 
>> 
>> 
> 
> -- 
> Andrew Wetmore
> 
> http://cottage14.blogspot.com/

Re: Spectrum Components

[Andrew Wetmore]

Small thing, but I think the code example for "Avatar" is reversed,
implying that the first of the two images is disabled rather than the
second.

On Sun, Jan 19, 2020 at 6:42 PM Harbs  wrote:

> FYI, I just added routing to the demo app. It was pretty painless,
> although I’d like to make it even simpler…
>
> https://unhurdle.github.io/spectrum-royale/#!bar_loader <
> https://unhurdle.github.io/spectrum-royale/#!bar_loader>
>
>
> > On Jan 15, 2020, at 7:08 PM, Harbs  wrote:
> >
> > FYI, I just updated the project readme with a link to the demo and some
> markup to show what a full Royale app looks like:
> > https://github.com/unhurdle/spectrum-royale <
> https://github.com/unhurdle/spectrum-royale>
> >
> >
> >> On Jan 13, 2020, at 1:30 AM, Harbs  harbs.li...@gmail.com>> wrote:
> >>
> >> FYI, I’ve been working on filling out a demo the Spectrum Royale
> components:
> >> https://unhurdle.github.io/spectrum-royale/ <
> https://unhurdle.github.io/spectrum-royale/>
> >>
> >> I’m going to be filling them out over the next week…
> >>
> >> Harbs
> >
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Spectrum Components

[Harbs]

FYI, I just added routing to the demo app. It was pretty painless, although I’d 
like to make it even simpler…

https://unhurdle.github.io/spectrum-royale/#!bar_loader 



> On Jan 15, 2020, at 7:08 PM, Harbs  wrote:
> 
> FYI, I just updated the project readme with a link to the demo and some 
> markup to show what a full Royale app looks like:
> https://github.com/unhurdle/spectrum-royale 
> 
> 
> 
>> On Jan 13, 2020, at 1:30 AM, Harbs > > wrote:
>> 
>> FYI, I’ve been working on filling out a demo the Spectrum Royale components:
>> https://unhurdle.github.io/spectrum-royale/ 
>> 
>> 
>> I’m going to be filling them out over the next week…
>> 
>> Harbs
> 

Re: Spectrum Components

[Harbs]

FYI, I just updated the project readme with a link to the demo and some markup 
to show what a full Royale app looks like:
https://github.com/unhurdle/spectrum-royale


> On Jan 13, 2020, at 1:30 AM, Harbs  wrote:
> 
> FYI, I’ve been working on filling out a demo the Spectrum Royale components:
> https://unhurdle.github.io/spectrum-royale/ 
> 
> 
> I’m going to be filling them out over the next week…
> 
> Harbs

Re: Spectrum Components

[Andrew Wetmore]

Hi:

I added the example links to the page.

On Tue, Jan 14, 2020 at 3:39 AM Carlos Rovira 
wrote:

> Hi Andrew,
>
> for MDL you can point to some examples in the Piotr site:
>
> MDLExample was like a Tour De MDL app to showcase all MDL build in Royale.
> I was moved to Piotr's site since legacy Apache can hold it (the same as
> Spectrum): https://transpiledactionscript.com/examples/MDLExample/
>
> a PureMVC-MDL example:
> https://transpiledactionscript.com/examples/PureMVCEmployeeAdminMDL/
>
> Thanks
>
> El lun., 13 ene. 2020 a las 22:48, Andrew Wetmore ()
> escribió:
>
> > I will set up those pages. Then we can see about getting the texts right
> > before we deploy them to the table of contents.
> >
> > On Mon, Jan 13, 2020 at 5:28 PM Carlos Rovira 
> > wrote:
> >
> > > Right Andrew,
> > >
> > > Other sibling node can be MDL too. For what I understand MDL is like
> > > Spectrum, both are js/css libraries that conform UI Sets in js. In
> Royale
> > > we're wrapping it to make available in AS3 for Royale. And MDL was
> > already
> > > complete
> > >
> > > just my 2
> > >
> > >
> > > El lun., 13 ene. 2020 a las 20:33, Andrew Wetmore (<
> cottag...@gmail.com
> > >)
> > > escribió:
> > >
> > > > What if we added a page under "Frameworks and Libraries", sibling to
> > > > "Crux", called "Spectrum Royale"? Plenty of room then to add pages
> > about
> > > > other flavors of using CSS and JS libraries with Royale.
> > > >
> > > > a
> > > >
> > > > On Mon, Jan 13, 2020 at 2:32 PM Carlos Rovira <
> carlosrov...@apache.org
> > >
> > > > wrote:
> > > >
> > > > > Hi Andrew, Harbs,
> > > > >
> > > > > I think we need to reference Spectrum and as well MDL since both
> > wraps
> > > > > css/js library with Royale.
> > > > > We need to start some docs sections with that since we have various
> > > > options
> > > > > (while others like createjs, or jquery, are just experiments that
> > does
> > > > not
> > > > > try to go further but give some example about how to do something
> > like
> > > > > that.
> > > > >
> > > > > just my 2
> > > > >
> > > > > Carios
> > > > >
> > > > > El lun., 13 ene. 2020 a las 16:20, Andrew Wetmore (<
> > > cottag...@gmail.com
> > > > >)
> > > > > escribió:
> > > > >
> > > > > > @Harbs   let us know when we should
> feature
> > > > this
> > > > > in
> > > > > > the same way we do Tour de Jewel, and in the user docs.
> > > > > >
> > > > > > I am looking at Adobe's Spectrum pages and can easily write a
> > couple
> > > of
> > > > > > paragraphs about what Spectrum is. I will need some input from
> you
> > > and
> > > > > what
> > > > > > you have found in merging Royale and Spectrum.
> > > > > >
> > > > > > Really lovely stuff to see.
> > > > > >
> > > > > > On Mon, Jan 13, 2020 at 11:03 AM Harbs 
> > > wrote:
> > > > > >
> > > > > > > FWIW here’s a comparison of the summaries of first page loads:
> > > > > > >
> > > > > > > Royale:
> > > > > > > https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA
> <
> > > > > > > https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA
> >
> > > > > > >
> > > > > > > React:
> > > > > > > https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA
> <
> > > > > > > https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA
> >
> > > > > > >
> > > > > > > Compare the Scripting and Rendering times of the two. The
> > contrast
> > > is
> > > > > > > stark.
> > > > > > >
> > > > > > > > On Jan 13, 2020, at 4:47 PM, Harbs 
> > > wrote:
> > > > > > > >
> > > > > > > > Adobe’s showcase of Spectrum is done using React:
> > > > > > > >
> > https://opensource.adobe.com/spectrum-css/components/accordion/
> > > <
> > > > > > >
> https://opensource.adobe.com/spectrum-css/components/accordion/>
> > > > > > > >
> > > > > > > > The original showcase was so slow that they had to break the
> > demo
> > > > > into
> > > > > > > separate pages. (It could be that made sense anyway.)
> > > > > > > >
> > > > > > > > It’s not a complete one-to-one comparison, but I’m going to
> try
> > > and
> > > > > > make
> > > > > > > it as close as I can. Once I’m done, we can write about it more
> > > > > > > intelligently. :-)
> > > > > > > >
> > > > > > > > Harbs
> > > > > > > >
> > > > > > > >> On Jan 13, 2020, at 4:35 PM, Carlos Rovira <
> > > > carlosrov...@apache.org
> > > > > > > > wrote:
> > > > > > > >>
> > > > > > > >> Hi Harbs,
> > > > > > > >>
> > > > > > > >> Amazing! :)
> > > > > > > >>
> > > > > > > >> Can you share more about your comparison?
> > > > > > > >> I think that could be something to share in our social media
> > > > right?
> > > > > > > people
> > > > > > > >> should know about this progress, since performance is
> > something
> > > > that
> > > > > > > users
> > > > > > > >> pursue as one of the most wanted things to choose one tech
> > over
> > > > > > another.
> > > > > > > >> But to make this valid, compared things should have a
> similar
> > > base
> > > > > to
> > > > > > be
> > > > > > > >> comparable. I 

Re: Spectrum Components

[Carlos Rovira]

Hi Andrew,

for MDL you can point to some examples in the Piotr site:

MDLExample was like a Tour De MDL app to showcase all MDL build in Royale.
I was moved to Piotr's site since legacy Apache can hold it (the same as
Spectrum): https://transpiledactionscript.com/examples/MDLExample/

a PureMVC-MDL example:
https://transpiledactionscript.com/examples/PureMVCEmployeeAdminMDL/

Thanks

El lun., 13 ene. 2020 a las 22:48, Andrew Wetmore ()
escribió:

> I will set up those pages. Then we can see about getting the texts right
> before we deploy them to the table of contents.
>
> On Mon, Jan 13, 2020 at 5:28 PM Carlos Rovira 
> wrote:
>
> > Right Andrew,
> >
> > Other sibling node can be MDL too. For what I understand MDL is like
> > Spectrum, both are js/css libraries that conform UI Sets in js. In Royale
> > we're wrapping it to make available in AS3 for Royale. And MDL was
> already
> > complete
> >
> > just my 2
> >
> >
> > El lun., 13 ene. 2020 a las 20:33, Andrew Wetmore ( >)
> > escribió:
> >
> > > What if we added a page under "Frameworks and Libraries", sibling to
> > > "Crux", called "Spectrum Royale"? Plenty of room then to add pages
> about
> > > other flavors of using CSS and JS libraries with Royale.
> > >
> > > a
> > >
> > > On Mon, Jan 13, 2020 at 2:32 PM Carlos Rovira  >
> > > wrote:
> > >
> > > > Hi Andrew, Harbs,
> > > >
> > > > I think we need to reference Spectrum and as well MDL since both
> wraps
> > > > css/js library with Royale.
> > > > We need to start some docs sections with that since we have various
> > > options
> > > > (while others like createjs, or jquery, are just experiments that
> does
> > > not
> > > > try to go further but give some example about how to do something
> like
> > > > that.
> > > >
> > > > just my 2
> > > >
> > > > Carios
> > > >
> > > > El lun., 13 ene. 2020 a las 16:20, Andrew Wetmore (<
> > cottag...@gmail.com
> > > >)
> > > > escribió:
> > > >
> > > > > @Harbs   let us know when we should feature
> > > this
> > > > in
> > > > > the same way we do Tour de Jewel, and in the user docs.
> > > > >
> > > > > I am looking at Adobe's Spectrum pages and can easily write a
> couple
> > of
> > > > > paragraphs about what Spectrum is. I will need some input from you
> > and
> > > > what
> > > > > you have found in merging Royale and Spectrum.
> > > > >
> > > > > Really lovely stuff to see.
> > > > >
> > > > > On Mon, Jan 13, 2020 at 11:03 AM Harbs 
> > wrote:
> > > > >
> > > > > > FWIW here’s a comparison of the summaries of first page loads:
> > > > > >
> > > > > > Royale:
> > > > > > https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA <
> > > > > > https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA>
> > > > > >
> > > > > > React:
> > > > > > https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA <
> > > > > > https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA>
> > > > > >
> > > > > > Compare the Scripting and Rendering times of the two. The
> contrast
> > is
> > > > > > stark.
> > > > > >
> > > > > > > On Jan 13, 2020, at 4:47 PM, Harbs 
> > wrote:
> > > > > > >
> > > > > > > Adobe’s showcase of Spectrum is done using React:
> > > > > > >
> https://opensource.adobe.com/spectrum-css/components/accordion/
> > <
> > > > > > https://opensource.adobe.com/spectrum-css/components/accordion/>
> > > > > > >
> > > > > > > The original showcase was so slow that they had to break the
> demo
> > > > into
> > > > > > separate pages. (It could be that made sense anyway.)
> > > > > > >
> > > > > > > It’s not a complete one-to-one comparison, but I’m going to try
> > and
> > > > > make
> > > > > > it as close as I can. Once I’m done, we can write about it more
> > > > > > intelligently. :-)
> > > > > > >
> > > > > > > Harbs
> > > > > > >
> > > > > > >> On Jan 13, 2020, at 4:35 PM, Carlos Rovira <
> > > carlosrov...@apache.org
> > > > > > > wrote:
> > > > > > >>
> > > > > > >> Hi Harbs,
> > > > > > >>
> > > > > > >> Amazing! :)
> > > > > > >>
> > > > > > >> Can you share more about your comparison?
> > > > > > >> I think that could be something to share in our social media
> > > right?
> > > > > > people
> > > > > > >> should know about this progress, since performance is
> something
> > > that
> > > > > > users
> > > > > > >> pursue as one of the most wanted things to choose one tech
> over
> > > > > another.
> > > > > > >> But to make this valid, compared things should have a similar
> > base
> > > > to
> > > > > be
> > > > > > >> comparable. I don't know too much about Spectrum components,
> > but I
> > > > > > >> understand that you are working on a Royale implementation and
> > > > someone
> > > > > > did
> > > > > > >> a React implementation, and you're comparing a switch of
> screen
> > > or a
> > > > > > >> component for the same component/screen using both
> > > implementations.
> > > > > > Another
> > > > > > >> interesting thing would be to know about what component/screen
> > > we're
> > > > > > >> 

Re: Spectrum Components

[Andrew Wetmore]

I will set up those pages. Then we can see about getting the texts right
before we deploy them to the table of contents.

On Mon, Jan 13, 2020 at 5:28 PM Carlos Rovira 
wrote:

> Right Andrew,
>
> Other sibling node can be MDL too. For what I understand MDL is like
> Spectrum, both are js/css libraries that conform UI Sets in js. In Royale
> we're wrapping it to make available in AS3 for Royale. And MDL was already
> complete
>
> just my 2
>
>
> El lun., 13 ene. 2020 a las 20:33, Andrew Wetmore ()
> escribió:
>
> > What if we added a page under "Frameworks and Libraries", sibling to
> > "Crux", called "Spectrum Royale"? Plenty of room then to add pages about
> > other flavors of using CSS and JS libraries with Royale.
> >
> > a
> >
> > On Mon, Jan 13, 2020 at 2:32 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Andrew, Harbs,
> > >
> > > I think we need to reference Spectrum and as well MDL since both wraps
> > > css/js library with Royale.
> > > We need to start some docs sections with that since we have various
> > options
> > > (while others like createjs, or jquery, are just experiments that does
> > not
> > > try to go further but give some example about how to do something like
> > > that.
> > >
> > > just my 2
> > >
> > > Carios
> > >
> > > El lun., 13 ene. 2020 a las 16:20, Andrew Wetmore (<
> cottag...@gmail.com
> > >)
> > > escribió:
> > >
> > > > @Harbs   let us know when we should feature
> > this
> > > in
> > > > the same way we do Tour de Jewel, and in the user docs.
> > > >
> > > > I am looking at Adobe's Spectrum pages and can easily write a couple
> of
> > > > paragraphs about what Spectrum is. I will need some input from you
> and
> > > what
> > > > you have found in merging Royale and Spectrum.
> > > >
> > > > Really lovely stuff to see.
> > > >
> > > > On Mon, Jan 13, 2020 at 11:03 AM Harbs 
> wrote:
> > > >
> > > > > FWIW here’s a comparison of the summaries of first page loads:
> > > > >
> > > > > Royale:
> > > > > https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA <
> > > > > https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA>
> > > > >
> > > > > React:
> > > > > https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA <
> > > > > https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA>
> > > > >
> > > > > Compare the Scripting and Rendering times of the two. The contrast
> is
> > > > > stark.
> > > > >
> > > > > > On Jan 13, 2020, at 4:47 PM, Harbs 
> wrote:
> > > > > >
> > > > > > Adobe’s showcase of Spectrum is done using React:
> > > > > > https://opensource.adobe.com/spectrum-css/components/accordion/
> <
> > > > > https://opensource.adobe.com/spectrum-css/components/accordion/>
> > > > > >
> > > > > > The original showcase was so slow that they had to break the demo
> > > into
> > > > > separate pages. (It could be that made sense anyway.)
> > > > > >
> > > > > > It’s not a complete one-to-one comparison, but I’m going to try
> and
> > > > make
> > > > > it as close as I can. Once I’m done, we can write about it more
> > > > > intelligently. :-)
> > > > > >
> > > > > > Harbs
> > > > > >
> > > > > >> On Jan 13, 2020, at 4:35 PM, Carlos Rovira <
> > carlosrov...@apache.org
> > > > > > wrote:
> > > > > >>
> > > > > >> Hi Harbs,
> > > > > >>
> > > > > >> Amazing! :)
> > > > > >>
> > > > > >> Can you share more about your comparison?
> > > > > >> I think that could be something to share in our social media
> > right?
> > > > > people
> > > > > >> should know about this progress, since performance is something
> > that
> > > > > users
> > > > > >> pursue as one of the most wanted things to choose one tech over
> > > > another.
> > > > > >> But to make this valid, compared things should have a similar
> base
> > > to
> > > > be
> > > > > >> comparable. I don't know too much about Spectrum components,
> but I
> > > > > >> understand that you are working on a Royale implementation and
> > > someone
> > > > > did
> > > > > >> a React implementation, and you're comparing a switch of screen
> > or a
> > > > > >> component for the same component/screen using both
> > implementations.
> > > > > Another
> > > > > >> interesting thing would be to know about what component/screen
> > we're
> > > > > >> talking about.
> > > > > >>
> > > > > >> Thanks! :)
> > > > > >>
> > > > > >> Carlos
> > > > > >>
> > > > > >>
> > > > > >> El lun., 13 ene. 2020 a las 15:23, Harbs (<
> harbs.li...@gmail.com
> > > > > >) escribió:
> > > > > >>
> > > > > >>> FYI, I took the opportunity to compare a similar React
> > > implementation
> > > > > to
> > > > > >>> the Royale one.
> > > > > >>>
> > > > > >>> Switching component views in React took about 500 ms, while in
> > > Royale
> > > > > it
> > > > > >>> took under 40 ms.
> > > > > >>> Royale:
> > > > > >>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc
> <
> > > > > https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc> <
> > > > > >>> 

Re: Spectrum Components

[Carlos Rovira]

Right Andrew,

Other sibling node can be MDL too. For what I understand MDL is like
Spectrum, both are js/css libraries that conform UI Sets in js. In Royale
we're wrapping it to make available in AS3 for Royale. And MDL was already
complete

just my 2


El lun., 13 ene. 2020 a las 20:33, Andrew Wetmore ()
escribió:

> What if we added a page under "Frameworks and Libraries", sibling to
> "Crux", called "Spectrum Royale"? Plenty of room then to add pages about
> other flavors of using CSS and JS libraries with Royale.
>
> a
>
> On Mon, Jan 13, 2020 at 2:32 PM Carlos Rovira 
> wrote:
>
> > Hi Andrew, Harbs,
> >
> > I think we need to reference Spectrum and as well MDL since both wraps
> > css/js library with Royale.
> > We need to start some docs sections with that since we have various
> options
> > (while others like createjs, or jquery, are just experiments that does
> not
> > try to go further but give some example about how to do something like
> > that.
> >
> > just my 2
> >
> > Carios
> >
> > El lun., 13 ene. 2020 a las 16:20, Andrew Wetmore ( >)
> > escribió:
> >
> > > @Harbs   let us know when we should feature
> this
> > in
> > > the same way we do Tour de Jewel, and in the user docs.
> > >
> > > I am looking at Adobe's Spectrum pages and can easily write a couple of
> > > paragraphs about what Spectrum is. I will need some input from you and
> > what
> > > you have found in merging Royale and Spectrum.
> > >
> > > Really lovely stuff to see.
> > >
> > > On Mon, Jan 13, 2020 at 11:03 AM Harbs  wrote:
> > >
> > > > FWIW here’s a comparison of the summaries of first page loads:
> > > >
> > > > Royale:
> > > > https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA <
> > > > https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA>
> > > >
> > > > React:
> > > > https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA <
> > > > https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA>
> > > >
> > > > Compare the Scripting and Rendering times of the two. The contrast is
> > > > stark.
> > > >
> > > > > On Jan 13, 2020, at 4:47 PM, Harbs  wrote:
> > > > >
> > > > > Adobe’s showcase of Spectrum is done using React:
> > > > > https://opensource.adobe.com/spectrum-css/components/accordion/ <
> > > > https://opensource.adobe.com/spectrum-css/components/accordion/>
> > > > >
> > > > > The original showcase was so slow that they had to break the demo
> > into
> > > > separate pages. (It could be that made sense anyway.)
> > > > >
> > > > > It’s not a complete one-to-one comparison, but I’m going to try and
> > > make
> > > > it as close as I can. Once I’m done, we can write about it more
> > > > intelligently. :-)
> > > > >
> > > > > Harbs
> > > > >
> > > > >> On Jan 13, 2020, at 4:35 PM, Carlos Rovira <
> carlosrov...@apache.org
> > > > > wrote:
> > > > >>
> > > > >> Hi Harbs,
> > > > >>
> > > > >> Amazing! :)
> > > > >>
> > > > >> Can you share more about your comparison?
> > > > >> I think that could be something to share in our social media
> right?
> > > > people
> > > > >> should know about this progress, since performance is something
> that
> > > > users
> > > > >> pursue as one of the most wanted things to choose one tech over
> > > another.
> > > > >> But to make this valid, compared things should have a similar base
> > to
> > > be
> > > > >> comparable. I don't know too much about Spectrum components, but I
> > > > >> understand that you are working on a Royale implementation and
> > someone
> > > > did
> > > > >> a React implementation, and you're comparing a switch of screen
> or a
> > > > >> component for the same component/screen using both
> implementations.
> > > > Another
> > > > >> interesting thing would be to know about what component/screen
> we're
> > > > >> talking about.
> > > > >>
> > > > >> Thanks! :)
> > > > >>
> > > > >> Carlos
> > > > >>
> > > > >>
> > > > >> El lun., 13 ene. 2020 a las 15:23, Harbs ( > > > >) escribió:
> > > > >>
> > > > >>> FYI, I took the opportunity to compare a similar React
> > implementation
> > > > to
> > > > >>> the Royale one.
> > > > >>>
> > > > >>> Switching component views in React took about 500 ms, while in
> > Royale
> > > > it
> > > > >>> took under 40 ms.
> > > > >>> Royale:
> > > > >>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc <
> > > > https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc> <
> > > > >>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc <
> > > > https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc>>
> > > > >>>
> > > > >>> React:
> > > > >>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU <
> > > > https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU> <
> > > > >>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU <
> > > > https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU>>
> > > > >>>
> > > > >>> This confirms my suspicion that we 

Re: Spectrum Components

[Andrew Wetmore]

What if we added a page under "Frameworks and Libraries", sibling to
"Crux", called "Spectrum Royale"? Plenty of room then to add pages about
other flavors of using CSS and JS libraries with Royale.

a

On Mon, Jan 13, 2020 at 2:32 PM Carlos Rovira 
wrote:

> Hi Andrew, Harbs,
>
> I think we need to reference Spectrum and as well MDL since both wraps
> css/js library with Royale.
> We need to start some docs sections with that since we have various options
> (while others like createjs, or jquery, are just experiments that does not
> try to go further but give some example about how to do something like
> that.
>
> just my 2
>
> Carios
>
> El lun., 13 ene. 2020 a las 16:20, Andrew Wetmore ()
> escribió:
>
> > @Harbs   let us know when we should feature this
> in
> > the same way we do Tour de Jewel, and in the user docs.
> >
> > I am looking at Adobe's Spectrum pages and can easily write a couple of
> > paragraphs about what Spectrum is. I will need some input from you and
> what
> > you have found in merging Royale and Spectrum.
> >
> > Really lovely stuff to see.
> >
> > On Mon, Jan 13, 2020 at 11:03 AM Harbs  wrote:
> >
> > > FWIW here’s a comparison of the summaries of first page loads:
> > >
> > > Royale:
> > > https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA <
> > > https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA>
> > >
> > > React:
> > > https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA <
> > > https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA>
> > >
> > > Compare the Scripting and Rendering times of the two. The contrast is
> > > stark.
> > >
> > > > On Jan 13, 2020, at 4:47 PM, Harbs  wrote:
> > > >
> > > > Adobe’s showcase of Spectrum is done using React:
> > > > https://opensource.adobe.com/spectrum-css/components/accordion/ <
> > > https://opensource.adobe.com/spectrum-css/components/accordion/>
> > > >
> > > > The original showcase was so slow that they had to break the demo
> into
> > > separate pages. (It could be that made sense anyway.)
> > > >
> > > > It’s not a complete one-to-one comparison, but I’m going to try and
> > make
> > > it as close as I can. Once I’m done, we can write about it more
> > > intelligently. :-)
> > > >
> > > > Harbs
> > > >
> > > >> On Jan 13, 2020, at 4:35 PM, Carlos Rovira  > > > wrote:
> > > >>
> > > >> Hi Harbs,
> > > >>
> > > >> Amazing! :)
> > > >>
> > > >> Can you share more about your comparison?
> > > >> I think that could be something to share in our social media right?
> > > people
> > > >> should know about this progress, since performance is something that
> > > users
> > > >> pursue as one of the most wanted things to choose one tech over
> > another.
> > > >> But to make this valid, compared things should have a similar base
> to
> > be
> > > >> comparable. I don't know too much about Spectrum components, but I
> > > >> understand that you are working on a Royale implementation and
> someone
> > > did
> > > >> a React implementation, and you're comparing a switch of screen or a
> > > >> component for the same component/screen using both implementations.
> > > Another
> > > >> interesting thing would be to know about what component/screen we're
> > > >> talking about.
> > > >>
> > > >> Thanks! :)
> > > >>
> > > >> Carlos
> > > >>
> > > >>
> > > >> El lun., 13 ene. 2020 a las 15:23, Harbs ( > > >) escribió:
> > > >>
> > > >>> FYI, I took the opportunity to compare a similar React
> implementation
> > > to
> > > >>> the Royale one.
> > > >>>
> > > >>> Switching component views in React took about 500 ms, while in
> Royale
> > > it
> > > >>> took under 40 ms.
> > > >>> Royale:
> > > >>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc <
> > > https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc> <
> > > >>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc <
> > > https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc>>
> > > >>>
> > > >>> React:
> > > >>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU <
> > > https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU> <
> > > >>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU <
> > > https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU>>
> > > >>>
> > > >>> This confirms my suspicion that we have a huge performance
> advantage
> > > with
> > > >>> Royale…
> > > >>>
> > > >>> Harbs
> > > >>>
> > >  On Jan 13, 2020, at 3:06 PM, Carlos Rovira <
> carlosrov...@apache.org
> > > >
> > > >>> wrote:
> > > 
> > >  Hi Harbs,
> > > 
> > >  cool to see that showcased!.
> > >  I think apps that demo code is very needed to make people
> understand
> > >  quickly what a concrete code or library can do for them.
> > > 
> > >  Thanks :)
> > > 
> > >  Carlos
> > > 
> > >  El lun., 13 ene. 2020 a las 11:06, Harbs ( > > 

Re: Spectrum Components

[Carlos Rovira]

Hi Andrew, Harbs,

I think we need to reference Spectrum and as well MDL since both wraps
css/js library with Royale.
We need to start some docs sections with that since we have various options
(while others like createjs, or jquery, are just experiments that does not
try to go further but give some example about how to do something like that.

just my 2

Carios

El lun., 13 ene. 2020 a las 16:20, Andrew Wetmore ()
escribió:

> @Harbs   let us know when we should feature this in
> the same way we do Tour de Jewel, and in the user docs.
>
> I am looking at Adobe's Spectrum pages and can easily write a couple of
> paragraphs about what Spectrum is. I will need some input from you and what
> you have found in merging Royale and Spectrum.
>
> Really lovely stuff to see.
>
> On Mon, Jan 13, 2020 at 11:03 AM Harbs  wrote:
>
> > FWIW here’s a comparison of the summaries of first page loads:
> >
> > Royale:
> > https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA <
> > https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA>
> >
> > React:
> > https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA <
> > https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA>
> >
> > Compare the Scripting and Rendering times of the two. The contrast is
> > stark.
> >
> > > On Jan 13, 2020, at 4:47 PM, Harbs  wrote:
> > >
> > > Adobe’s showcase of Spectrum is done using React:
> > > https://opensource.adobe.com/spectrum-css/components/accordion/ <
> > https://opensource.adobe.com/spectrum-css/components/accordion/>
> > >
> > > The original showcase was so slow that they had to break the demo into
> > separate pages. (It could be that made sense anyway.)
> > >
> > > It’s not a complete one-to-one comparison, but I’m going to try and
> make
> > it as close as I can. Once I’m done, we can write about it more
> > intelligently. :-)
> > >
> > > Harbs
> > >
> > >> On Jan 13, 2020, at 4:35 PM, Carlos Rovira  > > wrote:
> > >>
> > >> Hi Harbs,
> > >>
> > >> Amazing! :)
> > >>
> > >> Can you share more about your comparison?
> > >> I think that could be something to share in our social media right?
> > people
> > >> should know about this progress, since performance is something that
> > users
> > >> pursue as one of the most wanted things to choose one tech over
> another.
> > >> But to make this valid, compared things should have a similar base to
> be
> > >> comparable. I don't know too much about Spectrum components, but I
> > >> understand that you are working on a Royale implementation and someone
> > did
> > >> a React implementation, and you're comparing a switch of screen or a
> > >> component for the same component/screen using both implementations.
> > Another
> > >> interesting thing would be to know about what component/screen we're
> > >> talking about.
> > >>
> > >> Thanks! :)
> > >>
> > >> Carlos
> > >>
> > >>
> > >> El lun., 13 ene. 2020 a las 15:23, Harbs ( > >) escribió:
> > >>
> > >>> FYI, I took the opportunity to compare a similar React implementation
> > to
> > >>> the Royale one.
> > >>>
> > >>> Switching component views in React took about 500 ms, while in Royale
> > it
> > >>> took under 40 ms.
> > >>> Royale:
> > >>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc <
> > https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc> <
> > >>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc <
> > https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc>>
> > >>>
> > >>> React:
> > >>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU <
> > https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU> <
> > >>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU <
> > https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU>>
> > >>>
> > >>> This confirms my suspicion that we have a huge performance advantage
> > with
> > >>> Royale…
> > >>>
> > >>> Harbs
> > >>>
> >  On Jan 13, 2020, at 3:06 PM, Carlos Rovira  > >
> > >>> wrote:
> > 
> >  Hi Harbs,
> > 
> >  cool to see that showcased!.
> >  I think apps that demo code is very needed to make people understand
> >  quickly what a concrete code or library can do for them.
> > 
> >  Thanks :)
> > 
> >  Carlos
> > 
> >  El lun., 13 ene. 2020 a las 11:06, Harbs ( > >)
> > >>> escribió:
> > 
> > > That would be great. (fixed your suggestions)
> > >
> > > FYI, the code for the panes is here:
> > >
> > >>>
> >
> https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes
> > <
> >
> https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes
> > >
> > >
> > >> On Jan 13, 2020, at 1:43 AM, Andrew Wetmore 
> > >>> wrote:
> > >>
> > >> This will be great! By the way, if you want any text review I
> would
> > be
> > 

Re: Spectrum Components

[Harbs]

If you want.

> On Jan 13, 2020, at 8:22 PM, Carlos Rovira  wrote:
> 
> Awesome! If you don't mind I'd like to publish it. I think we can do more
> writing later, with more data, but give this pill would be beneficial,
> taking into account that our audience is not so big, but that could make
> some eyes turn to us
> 
> El lun., 13 ene. 2020 a las 16:03, Harbs () escribió:
> 
>> FWIW here’s a comparison of the summaries of first page loads:
>> 
>> Royale:
>> https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA <
>> https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA>
>> 
>> React:
>> https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA <
>> https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA>
>> 
>> Compare the Scripting and Rendering times of the two. The contrast is
>> stark.
>> 
>>> On Jan 13, 2020, at 4:47 PM, Harbs  wrote:
>>> 
>>> Adobe’s showcase of Spectrum is done using React:
>>> https://opensource.adobe.com/spectrum-css/components/accordion/ <
>> https://opensource.adobe.com/spectrum-css/components/accordion/>
>>> 
>>> The original showcase was so slow that they had to break the demo into
>> separate pages. (It could be that made sense anyway.)
>>> 
>>> It’s not a complete one-to-one comparison, but I’m going to try and make
>> it as close as I can. Once I’m done, we can write about it more
>> intelligently. :-)
>>> 
>>> Harbs
>>> 
 On Jan 13, 2020, at 4:35 PM, Carlos Rovira > > wrote:
 
 Hi Harbs,
 
 Amazing! :)
 
 Can you share more about your comparison?
 I think that could be something to share in our social media right?
>> people
 should know about this progress, since performance is something that
>> users
 pursue as one of the most wanted things to choose one tech over another.
 But to make this valid, compared things should have a similar base to be
 comparable. I don't know too much about Spectrum components, but I
 understand that you are working on a Royale implementation and someone
>> did
 a React implementation, and you're comparing a switch of screen or a
 component for the same component/screen using both implementations.
>> Another
 interesting thing would be to know about what component/screen we're
 talking about.
 
 Thanks! :)
 
 Carlos
 
 
 El lun., 13 ene. 2020 a las 15:23, Harbs (> >) escribió:
 
> FYI, I took the opportunity to compare a similar React implementation
>> to
> the Royale one.
> 
> Switching component views in React took about 500 ms, while in Royale
>> it
> took under 40 ms.
> Royale:
> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc <
>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc> <
> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc <
>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc>>
> 
> React:
> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU <
>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU> <
> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU <
>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU>>
> 
> This confirms my suspicion that we have a huge performance advantage
>> with
> Royale…
> 
> Harbs
> 
>> On Jan 13, 2020, at 3:06 PM, Carlos Rovira > >
> wrote:
>> 
>> Hi Harbs,
>> 
>> cool to see that showcased!.
>> I think apps that demo code is very needed to make people understand
>> quickly what a concrete code or library can do for them.
>> 
>> Thanks :)
>> 
>> Carlos
>> 
>> El lun., 13 ene. 2020 a las 11:06, Harbs (> >)
> escribió:
>> 
>>> That would be great. (fixed your suggestions)
>>> 
>>> FYI, the code for the panes is here:
>>> 
> 
>> https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes
>> <
>> https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes
>>> 
>>> 
 On Jan 13, 2020, at 1:43 AM, Andrew Wetmore 
> wrote:
 
 This will be great! By the way, if you want any text review I would
>> be
 happy to help. For example, "Varients" should be "Variants"
 
 On Sun, Jan 12, 2020 at 7:30 PM Harbs 
>> wrote:
 
> FYI, I’ve been working on filling out a demo the Spectrum Royale
> components:
> https://unhurdle.github.io/spectrum-royale/ <
> https://unhurdle.github.io/spectrum-royale/>
> 
> I’m going to be filling them out over the next week…
> 
> Harbs
 
 
 
 --
 Andrew Wetmore
 
 http://cottage14.blogspot.com/
>>> 
>>> 
>> 
>> --
>> Carlos Rovira

Re: Spectrum Components

[Carlos Rovira]

Awesome! If you don't mind I'd like to publish it. I think we can do more
writing later, with more data, but give this pill would be beneficial,
taking into account that our audience is not so big, but that could make
some eyes turn to us

El lun., 13 ene. 2020 a las 16:03, Harbs () escribió:

> FWIW here’s a comparison of the summaries of first page loads:
>
> Royale:
> https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA <
> https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA>
>
> React:
> https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA <
> https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA>
>
> Compare the Scripting and Rendering times of the two. The contrast is
> stark.
>
> > On Jan 13, 2020, at 4:47 PM, Harbs  wrote:
> >
> > Adobe’s showcase of Spectrum is done using React:
> > https://opensource.adobe.com/spectrum-css/components/accordion/ <
> https://opensource.adobe.com/spectrum-css/components/accordion/>
> >
> > The original showcase was so slow that they had to break the demo into
> separate pages. (It could be that made sense anyway.)
> >
> > It’s not a complete one-to-one comparison, but I’m going to try and make
> it as close as I can. Once I’m done, we can write about it more
> intelligently. :-)
> >
> > Harbs
> >
> >> On Jan 13, 2020, at 4:35 PM, Carlos Rovira  > wrote:
> >>
> >> Hi Harbs,
> >>
> >> Amazing! :)
> >>
> >> Can you share more about your comparison?
> >> I think that could be something to share in our social media right?
> people
> >> should know about this progress, since performance is something that
> users
> >> pursue as one of the most wanted things to choose one tech over another.
> >> But to make this valid, compared things should have a similar base to be
> >> comparable. I don't know too much about Spectrum components, but I
> >> understand that you are working on a Royale implementation and someone
> did
> >> a React implementation, and you're comparing a switch of screen or a
> >> component for the same component/screen using both implementations.
> Another
> >> interesting thing would be to know about what component/screen we're
> >> talking about.
> >>
> >> Thanks! :)
> >>
> >> Carlos
> >>
> >>
> >> El lun., 13 ene. 2020 a las 15:23, Harbs ( >) escribió:
> >>
> >>> FYI, I took the opportunity to compare a similar React implementation
> to
> >>> the Royale one.
> >>>
> >>> Switching component views in React took about 500 ms, while in Royale
> it
> >>> took under 40 ms.
> >>> Royale:
> >>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc <
> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc> <
> >>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc <
> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc>>
> >>>
> >>> React:
> >>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU <
> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU> <
> >>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU <
> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU>>
> >>>
> >>> This confirms my suspicion that we have a huge performance advantage
> with
> >>> Royale…
> >>>
> >>> Harbs
> >>>
>  On Jan 13, 2020, at 3:06 PM, Carlos Rovira  >
> >>> wrote:
> 
>  Hi Harbs,
> 
>  cool to see that showcased!.
>  I think apps that demo code is very needed to make people understand
>  quickly what a concrete code or library can do for them.
> 
>  Thanks :)
> 
>  Carlos
> 
>  El lun., 13 ene. 2020 a las 11:06, Harbs ( >)
> >>> escribió:
> 
> > That would be great. (fixed your suggestions)
> >
> > FYI, the code for the panes is here:
> >
> >>>
> https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes
> <
> https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes
> >
> >
> >> On Jan 13, 2020, at 1:43 AM, Andrew Wetmore 
> >>> wrote:
> >>
> >> This will be great! By the way, if you want any text review I would
> be
> >> happy to help. For example, "Varients" should be "Variants"
> >>
> >> On Sun, Jan 12, 2020 at 7:30 PM Harbs 
> wrote:
> >>
> >>> FYI, I’ve been working on filling out a demo the Spectrum Royale
> >>> components:
> >>> https://unhurdle.github.io/spectrum-royale/ <
> >>> https://unhurdle.github.io/spectrum-royale/>
> >>>
> >>> I’m going to be filling them out over the next week…
> >>>
> >>> Harbs
> >>
> >>
> >>
> >> --
> >> Andrew Wetmore
> >>
> >> http://cottage14.blogspot.com/
> >
> >
> 
>  --
>  Carlos Rovira
>  http://about.me/carlosrovira
> >>>
> >>>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira 
>
>

-- 
Carlos Rovira

Re: Spectrum Components

[Andrew Wetmore]

@Harbs   let us know when we should feature this in
the same way we do Tour de Jewel, and in the user docs.

I am looking at Adobe's Spectrum pages and can easily write a couple of
paragraphs about what Spectrum is. I will need some input from you and what
you have found in merging Royale and Spectrum.

Really lovely stuff to see.

On Mon, Jan 13, 2020 at 11:03 AM Harbs  wrote:

> FWIW here’s a comparison of the summaries of first page loads:
>
> Royale:
> https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA <
> https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA>
>
> React:
> https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA <
> https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA>
>
> Compare the Scripting and Rendering times of the two. The contrast is
> stark.
>
> > On Jan 13, 2020, at 4:47 PM, Harbs  wrote:
> >
> > Adobe’s showcase of Spectrum is done using React:
> > https://opensource.adobe.com/spectrum-css/components/accordion/ <
> https://opensource.adobe.com/spectrum-css/components/accordion/>
> >
> > The original showcase was so slow that they had to break the demo into
> separate pages. (It could be that made sense anyway.)
> >
> > It’s not a complete one-to-one comparison, but I’m going to try and make
> it as close as I can. Once I’m done, we can write about it more
> intelligently. :-)
> >
> > Harbs
> >
> >> On Jan 13, 2020, at 4:35 PM, Carlos Rovira  > wrote:
> >>
> >> Hi Harbs,
> >>
> >> Amazing! :)
> >>
> >> Can you share more about your comparison?
> >> I think that could be something to share in our social media right?
> people
> >> should know about this progress, since performance is something that
> users
> >> pursue as one of the most wanted things to choose one tech over another.
> >> But to make this valid, compared things should have a similar base to be
> >> comparable. I don't know too much about Spectrum components, but I
> >> understand that you are working on a Royale implementation and someone
> did
> >> a React implementation, and you're comparing a switch of screen or a
> >> component for the same component/screen using both implementations.
> Another
> >> interesting thing would be to know about what component/screen we're
> >> talking about.
> >>
> >> Thanks! :)
> >>
> >> Carlos
> >>
> >>
> >> El lun., 13 ene. 2020 a las 15:23, Harbs ( >) escribió:
> >>
> >>> FYI, I took the opportunity to compare a similar React implementation
> to
> >>> the Royale one.
> >>>
> >>> Switching component views in React took about 500 ms, while in Royale
> it
> >>> took under 40 ms.
> >>> Royale:
> >>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc <
> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc> <
> >>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc <
> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc>>
> >>>
> >>> React:
> >>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU <
> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU> <
> >>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU <
> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU>>
> >>>
> >>> This confirms my suspicion that we have a huge performance advantage
> with
> >>> Royale…
> >>>
> >>> Harbs
> >>>
>  On Jan 13, 2020, at 3:06 PM, Carlos Rovira  >
> >>> wrote:
> 
>  Hi Harbs,
> 
>  cool to see that showcased!.
>  I think apps that demo code is very needed to make people understand
>  quickly what a concrete code or library can do for them.
> 
>  Thanks :)
> 
>  Carlos
> 
>  El lun., 13 ene. 2020 a las 11:06, Harbs ( >)
> >>> escribió:
> 
> > That would be great. (fixed your suggestions)
> >
> > FYI, the code for the panes is here:
> >
> >>>
> https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes
> <
> https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes
> >
> >
> >> On Jan 13, 2020, at 1:43 AM, Andrew Wetmore 
> >>> wrote:
> >>
> >> This will be great! By the way, if you want any text review I would
> be
> >> happy to help. For example, "Varients" should be "Variants"
> >>
> >> On Sun, Jan 12, 2020 at 7:30 PM Harbs 
> wrote:
> >>
> >>> FYI, I’ve been working on filling out a demo the Spectrum Royale
> >>> components:
> >>> https://unhurdle.github.io/spectrum-royale/ <
> >>> https://unhurdle.github.io/spectrum-royale/>
> >>>
> >>> I’m going to be filling them out over the next week…
> >>>
> >>> Harbs
> >>
> >>
> >>
> >> --
> >> Andrew Wetmore
> >>
> >> http://cottage14.blogspot.com/
> >
> >
> 
>  --
>  Carlos Rovira
>  http://about.me/carlosrovira
> >>>
> >>>
> >>
> >> --
> >> Carlos Rovira
> 

Re: Spectrum Components

[Harbs]

FWIW here’s a comparison of the summaries of first page loads:

Royale:
https://www.evernote.com/l/AI9q-KtmIU5Fz5O055Z6VSNW1dWEGERugUA 


React:
https://www.evernote.com/l/AI9U13oQWlRAo7HzY4ZiTz5xuLU6MJbITpA 


Compare the Scripting and Rendering times of the two. The contrast is stark.

> On Jan 13, 2020, at 4:47 PM, Harbs  wrote:
> 
> Adobe’s showcase of Spectrum is done using React:
> https://opensource.adobe.com/spectrum-css/components/accordion/ 
> 
> 
> The original showcase was so slow that they had to break the demo into 
> separate pages. (It could be that made sense anyway.)
> 
> It’s not a complete one-to-one comparison, but I’m going to try and make it 
> as close as I can. Once I’m done, we can write about it more intelligently. 
> :-)
> 
> Harbs
> 
>> On Jan 13, 2020, at 4:35 PM, Carlos Rovira > > wrote:
>> 
>> Hi Harbs,
>> 
>> Amazing! :)
>> 
>> Can you share more about your comparison?
>> I think that could be something to share in our social media right? people
>> should know about this progress, since performance is something that users
>> pursue as one of the most wanted things to choose one tech over another.
>> But to make this valid, compared things should have a similar base to be
>> comparable. I don't know too much about Spectrum components, but I
>> understand that you are working on a Royale implementation and someone did
>> a React implementation, and you're comparing a switch of screen or a
>> component for the same component/screen using both implementations. Another
>> interesting thing would be to know about what component/screen we're
>> talking about.
>> 
>> Thanks! :)
>> 
>> Carlos
>> 
>> 
>> El lun., 13 ene. 2020 a las 15:23, Harbs (> >) escribió:
>> 
>>> FYI, I took the opportunity to compare a similar React implementation to
>>> the Royale one.
>>> 
>>> Switching component views in React took about 500 ms, while in Royale it
>>> took under 40 ms.
>>> Royale:
>>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc 
>>>  <
>>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc 
>>> >
>>> 
>>> React:
>>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU 
>>>  <
>>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU 
>>> >
>>> 
>>> This confirms my suspicion that we have a huge performance advantage with
>>> Royale…
>>> 
>>> Harbs
>>> 
 On Jan 13, 2020, at 3:06 PM, Carlos Rovira >>> >
>>> wrote:
 
 Hi Harbs,
 
 cool to see that showcased!.
 I think apps that demo code is very needed to make people understand
 quickly what a concrete code or library can do for them.
 
 Thanks :)
 
 Carlos
 
 El lun., 13 ene. 2020 a las 11:06, Harbs (>>> >)
>>> escribió:
 
> That would be great. (fixed your suggestions)
> 
> FYI, the code for the panes is here:
> 
>>> https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes
>>>  
>>> 
> 
>> On Jan 13, 2020, at 1:43 AM, Andrew Wetmore 
>>> wrote:
>> 
>> This will be great! By the way, if you want any text review I would be
>> happy to help. For example, "Varients" should be "Variants"
>> 
>> On Sun, Jan 12, 2020 at 7:30 PM Harbs  wrote:
>> 
>>> FYI, I’ve been working on filling out a demo the Spectrum Royale
>>> components:
>>> https://unhurdle.github.io/spectrum-royale/ <
>>> https://unhurdle.github.io/spectrum-royale/>
>>> 
>>> I’m going to be filling them out over the next week…
>>> 
>>> Harbs
>> 
>> 
>> 
>> --
>> Andrew Wetmore
>> 
>> http://cottage14.blogspot.com/
> 
> 
 
 --
 Carlos Rovira
 http://about.me/carlosrovira
>>> 
>>> 
>> 
>> -- 
>> Carlos Rovira
>> http://about.me/carlosrovira 

Re: Spectrum Components

[Harbs]

Adobe’s showcase of Spectrum is done using React:
https://opensource.adobe.com/spectrum-css/components/accordion/ 


The original showcase was so slow that they had to break the demo into separate 
pages. (It could be that made sense anyway.)

It’s not a complete one-to-one comparison, but I’m going to try and make it as 
close as I can. Once I’m done, we can write about it more intelligently. :-)

Harbs

> On Jan 13, 2020, at 4:35 PM, Carlos Rovira  wrote:
> 
> Hi Harbs,
> 
> Amazing! :)
> 
> Can you share more about your comparison?
> I think that could be something to share in our social media right? people
> should know about this progress, since performance is something that users
> pursue as one of the most wanted things to choose one tech over another.
> But to make this valid, compared things should have a similar base to be
> comparable. I don't know too much about Spectrum components, but I
> understand that you are working on a Royale implementation and someone did
> a React implementation, and you're comparing a switch of screen or a
> component for the same component/screen using both implementations. Another
> interesting thing would be to know about what component/screen we're
> talking about.
> 
> Thanks! :)
> 
> Carlos
> 
> 
> El lun., 13 ene. 2020 a las 15:23, Harbs ( >) escribió:
> 
>> FYI, I took the opportunity to compare a similar React implementation to
>> the Royale one.
>> 
>> Switching component views in React took about 500 ms, while in Royale it
>> took under 40 ms.
>> Royale:
>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc 
>>  <
>> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc 
>> >
>> 
>> React:
>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU 
>>  <
>> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU 
>> >
>> 
>> This confirms my suspicion that we have a huge performance advantage with
>> Royale…
>> 
>> Harbs
>> 
>>> On Jan 13, 2020, at 3:06 PM, Carlos Rovira 
>> wrote:
>>> 
>>> Hi Harbs,
>>> 
>>> cool to see that showcased!.
>>> I think apps that demo code is very needed to make people understand
>>> quickly what a concrete code or library can do for them.
>>> 
>>> Thanks :)
>>> 
>>> Carlos
>>> 
>>> El lun., 13 ene. 2020 a las 11:06, Harbs ()
>> escribió:
>>> 
 That would be great. (fixed your suggestions)
 
 FYI, the code for the panes is here:
 
>> https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes
 
> On Jan 13, 2020, at 1:43 AM, Andrew Wetmore 
>> wrote:
> 
> This will be great! By the way, if you want any text review I would be
> happy to help. For example, "Varients" should be "Variants"
> 
> On Sun, Jan 12, 2020 at 7:30 PM Harbs  wrote:
> 
>> FYI, I’ve been working on filling out a demo the Spectrum Royale
>> components:
>> https://unhurdle.github.io/spectrum-royale/ <
>> https://unhurdle.github.io/spectrum-royale/>
>> 
>> I’m going to be filling them out over the next week…
>> 
>> Harbs
> 
> 
> 
> --
> Andrew Wetmore
> 
> http://cottage14.blogspot.com/
 
 
>>> 
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>> 
>> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira 

Re: Spectrum Components

[Harbs]

To be (somewhat) fair, I was comparing a first load on both of them. The React 
version needed to load external resources to render.

It’s not a totally unfair comparison because the first load is affected. Part 
of the reason assets are loaded dynamically in React is because performance is 
simply horrible otherwise.

Even comparing subsequent loads, the React version is over 200 ms.


I’ll compare initial page load time once I finish the demo.

Right now it’s 1.2 seconds compared to React’s 1.7 seconds, and I’m probably 
loading more assets than I need to before rendering…

> On Jan 13, 2020, at 4:23 PM, Harbs  wrote:
> 
> FYI, I took the opportunity to compare a similar React implementation to the 
> Royale one.
> 
> Switching component views in React took about 500 ms, while in Royale it took 
> under 40 ms.
> Royale:
> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc 
> 
> 
> React:
> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU 
> 
> 
> This confirms my suspicion that we have a huge performance advantage with 
> Royale…
> 
> Harbs
> 
>> On Jan 13, 2020, at 3:06 PM, Carlos Rovira > > wrote:
>> 
>> Hi Harbs,
>> 
>> cool to see that showcased!.
>> I think apps that demo code is very needed to make people understand
>> quickly what a concrete code or library can do for them.
>> 
>> Thanks :)
>> 
>> Carlos
>> 
>> El lun., 13 ene. 2020 a las 11:06, Harbs (> >) escribió:
>> 
>>> That would be great. (fixed your suggestions)
>>> 
>>> FYI, the code for the panes is here:
>>> https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes
>>>  
>>> 
>>> 
 On Jan 13, 2020, at 1:43 AM, Andrew Wetmore  wrote:
 
 This will be great! By the way, if you want any text review I would be
 happy to help. For example, "Varients" should be "Variants"
 
 On Sun, Jan 12, 2020 at 7:30 PM Harbs  wrote:
 
> FYI, I’ve been working on filling out a demo the Spectrum Royale
> components:
> https://unhurdle.github.io/spectrum-royale/ <
> https://unhurdle.github.io/spectrum-royale/>
> 
> I’m going to be filling them out over the next week…
> 
> Harbs
 
 
 
 --
 Andrew Wetmore
 
 http://cottage14.blogspot.com/
>>> 
>>> 
>> 
>> -- 
>> Carlos Rovira
>> http://about.me/carlosrovira 
> 

Re: Spectrum Components

[Carlos Rovira]

Hi Harbs,

Amazing! :)

Can you share more about your comparison?
I think that could be something to share in our social media right? people
should know about this progress, since performance is something that users
pursue as one of the most wanted things to choose one tech over another.
But to make this valid, compared things should have a similar base to be
comparable. I don't know too much about Spectrum components, but I
understand that you are working on a Royale implementation and someone did
a React implementation, and you're comparing a switch of screen or a
component for the same component/screen using both implementations. Another
interesting thing would be to know about what component/screen we're
talking about.

Thanks! :)

Carlos


El lun., 13 ene. 2020 a las 15:23, Harbs () escribió:

> FYI, I took the opportunity to compare a similar React implementation to
> the Royale one.
>
> Switching component views in React took about 500 ms, while in Royale it
> took under 40 ms.
> Royale:
> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc <
> https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc>
>
> React:
> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU <
> https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU>
>
> This confirms my suspicion that we have a huge performance advantage with
> Royale…
>
> Harbs
>
> > On Jan 13, 2020, at 3:06 PM, Carlos Rovira 
> wrote:
> >
> > Hi Harbs,
> >
> > cool to see that showcased!.
> > I think apps that demo code is very needed to make people understand
> > quickly what a concrete code or library can do for them.
> >
> > Thanks :)
> >
> > Carlos
> >
> > El lun., 13 ene. 2020 a las 11:06, Harbs ()
> escribió:
> >
> >> That would be great. (fixed your suggestions)
> >>
> >> FYI, the code for the panes is here:
> >>
> https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes
> >>
> >>> On Jan 13, 2020, at 1:43 AM, Andrew Wetmore 
> wrote:
> >>>
> >>> This will be great! By the way, if you want any text review I would be
> >>> happy to help. For example, "Varients" should be "Variants"
> >>>
> >>> On Sun, Jan 12, 2020 at 7:30 PM Harbs  wrote:
> >>>
>  FYI, I’ve been working on filling out a demo the Spectrum Royale
>  components:
>  https://unhurdle.github.io/spectrum-royale/ <
>  https://unhurdle.github.io/spectrum-royale/>
> 
>  I’m going to be filling them out over the next week…
> 
>  Harbs
> >>>
> >>>
> >>>
> >>> --
> >>> Andrew Wetmore
> >>>
> >>> http://cottage14.blogspot.com/
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>

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

Re: Spectrum Components

[Harbs]

FYI, I took the opportunity to compare a similar React implementation to the 
Royale one.

Switching component views in React took about 500 ms, while in Royale it took 
under 40 ms.
Royale:
https://www.evernote.com/l/AI_tvFQmLmxMIKoex5T3iLbCL5E7Y2XqGQc 


React:
https://www.evernote.com/l/AI-kSFHyYHFCWou_2mp4I-jqIB1toKyMryU 


This confirms my suspicion that we have a huge performance advantage with 
Royale…

Harbs

> On Jan 13, 2020, at 3:06 PM, Carlos Rovira  wrote:
> 
> Hi Harbs,
> 
> cool to see that showcased!.
> I think apps that demo code is very needed to make people understand
> quickly what a concrete code or library can do for them.
> 
> Thanks :)
> 
> Carlos
> 
> El lun., 13 ene. 2020 a las 11:06, Harbs () escribió:
> 
>> That would be great. (fixed your suggestions)
>> 
>> FYI, the code for the panes is here:
>> https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes
>> 
>>> On Jan 13, 2020, at 1:43 AM, Andrew Wetmore  wrote:
>>> 
>>> This will be great! By the way, if you want any text review I would be
>>> happy to help. For example, "Varients" should be "Variants"
>>> 
>>> On Sun, Jan 12, 2020 at 7:30 PM Harbs  wrote:
>>> 
 FYI, I’ve been working on filling out a demo the Spectrum Royale
 components:
 https://unhurdle.github.io/spectrum-royale/ <
 https://unhurdle.github.io/spectrum-royale/>
 
 I’m going to be filling them out over the next week…
 
 Harbs
>>> 
>>> 
>>> 
>>> --
>>> Andrew Wetmore
>>> 
>>> http://cottage14.blogspot.com/
>> 
>> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: Spectrum Components

[Carlos Rovira]

Hi Harbs,

cool to see that showcased!.
I think apps that demo code is very needed to make people understand
quickly what a concrete code or library can do for them.

Thanks :)

Carlos

El lun., 13 ene. 2020 a las 11:06, Harbs () escribió:

> That would be great. (fixed your suggestions)
>
> FYI, the code for the panes is here:
> https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes
>
> > On Jan 13, 2020, at 1:43 AM, Andrew Wetmore  wrote:
> >
> > This will be great! By the way, if you want any text review I would be
> > happy to help. For example, "Varients" should be "Variants"
> >
> > On Sun, Jan 12, 2020 at 7:30 PM Harbs  wrote:
> >
> >> FYI, I’ve been working on filling out a demo the Spectrum Royale
> >> components:
> >> https://unhurdle.github.io/spectrum-royale/ <
> >> https://unhurdle.github.io/spectrum-royale/>
> >>
> >> I’m going to be filling them out over the next week…
> >>
> >> Harbs
> >
> >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
>
>

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

Re: Spectrum Components

[Harbs]

That would be great. (fixed your suggestions)

FYI, the code for the panes is here: 
https://github.com/unhurdle/spectrum-royale/tree/master/SpectrumBrowser/src/view/panes

> On Jan 13, 2020, at 1:43 AM, Andrew Wetmore  wrote:
> 
> This will be great! By the way, if you want any text review I would be
> happy to help. For example, "Varients" should be "Variants"
> 
> On Sun, Jan 12, 2020 at 7:30 PM Harbs  wrote:
> 
>> FYI, I’ve been working on filling out a demo the Spectrum Royale
>> components:
>> https://unhurdle.github.io/spectrum-royale/ <
>> https://unhurdle.github.io/spectrum-royale/>
>> 
>> I’m going to be filling them out over the next week…
>> 
>> Harbs
> 
> 
> 
> -- 
> Andrew Wetmore
> 
> http://cottage14.blogspot.com/

Re: Spectrum Components

[Andrew Wetmore]

This will be great! By the way, if you want any text review I would be
happy to help. For example, "Varients" should be "Variants"

On Sun, Jan 12, 2020 at 7:30 PM Harbs  wrote:

> FYI, I’ve been working on filling out a demo the Spectrum Royale
> components:
> https://unhurdle.github.io/spectrum-royale/ <
> https://unhurdle.github.io/spectrum-royale/>
>
> I’m going to be filling them out over the next week…
>
> Harbs



-- 
Andrew Wetmore

http://cottage14.blogspot.com/