Hi Mahmoud,
Yes, this is very possible to do. Have any widget add a history
handler, and watch for any history change event, and then fire the
widget state accordingly as you see fit. I like doing it this way. You
can pass any number of parameters in to change the widgets/app state.
domain.tld#hi
That's parameter passing within the web application, what about the
first part of my question? the most important one to me
On Apr 24, 7:46 am, Paul Stockley wrote:
> Use something like History.newItem("page3?param1=a¶m2=b");
>
> This will rewrite the currentURLand store it in the browsers
> hist
Use something like History.newItem("page3?param1=a¶m2=b");
This will rewrite the current URL and store it in the browsers
history. The onChange history event will then be fired.
On Apr 23, 11:38 pm, Mahmoud wrote:
> Hello,
> I have followed the MVP structure while developing my project.
> Once I
Hello,
I have followed the MVP structure while developing my project.
Once I hit the site URL, the History Manager loads the module by
inserting the default token to the history stack and then from there
the user can redirect himself to any part of the application by
changing the History token, whi
