Re: Browser History API

2019-02-25 Thread JumpStart
r { >let newOptions = {...options}; >return Ajax(url, newOptions); >}; > > > I think TypeScript is a "must" to get good client code. I use also JSX. I am > looking for a way to use the same interface for Tapstery/Java services and > Typescript fo

RE: Browser History API

2019-02-23 Thread Svein-Erik Løken
cript for data access. Maybe Kotlin can be used. S-E -Original Message- From: JumpStart Sent: lørdag 23. februar 2019 03:01 To: Tapestry users Subject: Re: Browser History API Very interesting. A couple of questions: What issues is that header addressing? What role is Tapestry playing in your

Re: Browser History API

2019-02-22 Thread JumpStart
22. februar 2019 02:16 > To: Tapestry users > Subject: Re: Browser History API > > Thank you, but I think I’ll mostly want the server-side making the decision > on what to make navigable. We shall see how that pans out. > >> On 21 Feb 2019, at 3:29 pm, Svein-Erik Løken w

RE: Browser History API

2019-02-21 Thread Svein-Erik Løken
rt Sent: fredag 22. februar 2019 02:16 To: Tapestry users Subject: Re: Browser History API Thank you, but I think I’ll mostly want the server-side making the decision on what to make navigable. We shall see how that pans out. > On 21 Feb 2019, at 3:29 pm, Svein-Erik Løken wrote: > > Yo

Re: Browser History API

2019-02-21 Thread JumpStart
placeState(null, "", location.protocol + '//' + > location.host + location.pathname + "/yourUrlPart"); > > -Original Message- > From: JumpStart > Sent: torsdag 21. februar 2019 05:39 > To: Tapestry users > Subject: Browser History API >

Re: Browser History API

2019-02-21 Thread JumpStart
the page (in my > example I do this on IndexPage) > > I hope the example helps you. > > Regards > > Carlos Montero > > El jue., 21 feb. 2019 a las 5:39, JumpStart (< > geoff.callender.jumpst...@gmail.com>) escribió: > >> Has anyone made use of the

RE: Browser History API

2019-02-20 Thread Svein-Erik Løken
39 To: Tapestry users Subject: Browser History API Has anyone made use of the browser History API with Tapestry AJAX calls? I have an essentially single page app, all done with Zones and async event links. Tabs down one side flips between major functions (eg. Clients, Calendar, Billing), replaci

Re: Browser History API

2019-02-20 Thread Carlos Montero Canabal
(< geoff.callender.jumpst...@gmail.com>) escribió: > Has anyone made use of the browser History API with Tapestry AJAX calls? > > I have an essentially single page app, all done with Zones and async event > links. Tabs down one side flips between major functions (eg. Clients, &

Browser History API

2019-02-20 Thread JumpStart
Has anyone made use of the browser History API with Tapestry AJAX calls? I have an essentially single page app, all done with Zones and async event links. Tabs down one side flips between major functions (eg. Clients, Calendar, Billing), replacing the main pane contents, and clicking on buttons