Use BrowserHistory for Favourites [message #987384] |
Mon, 26 November 2012 11:40 |
Eclipse User |
|
|
|
Hi,
would it be possible to use the BrowserHistory mechanism for favorites?
For example, we want to be able to open a certain view or object if the
user opens the url "http:/outserver/servletName?objectToOpen=ViewId1".
Now the user can use this as bookmark and always ends up in the
application where he wants to.
The problem using this mechanism is, that if he now opens a favorite
"http:/outserver/servletName?objectToOpen=ViewId2" then the complete
application restarts which results in a new user login etc.
The BrowserHistory does not use parameters but anchers that do not lead
to a reload of the application. Our demand is, that if the user then
opens the application with "http:/outserver/servletName#ViewId1", than
the login happens and after that the user gets View1 displayed. If he
than opens up "http:/outserver/servletName#ViewId2" the user just gets
displayed View2 without leaving the application.
Is this somehow possible, maybe with the BrowserHistory?
Regards,
Markus
|
|
|
Re: Use BrowserHistory for Favourites [message #987460 is a reply to message #987384] |
Mon, 26 November 2012 17:13 |
Lothar Werzinger Messages: 153 Registered: July 2009 Location: Bay Area |
Senior Member |
|
|
Markus Krüger wrote:
> Hi,
>
> would it be possible to use the BrowserHistory mechanism for favorites?
>
> For example, we want to be able to open a certain view or object if the
> user opens the url "http:/outserver/servletName?objectToOpen=ViewId1".
> Now the user can use this as bookmark and always ends up in the
> application where he wants to.
> The problem using this mechanism is, that if he now opens a favorite
> "http:/outserver/servletName?objectToOpen=ViewId2" then the complete
> application restarts which results in a new user login etc.
>
> The BrowserHistory does not use parameters but anchers that do not lead
> to a reload of the application. Our demand is, that if the user then
> opens the application with "http:/outserver/servletName#ViewId1", than
> the login happens and after that the user gets View1 displayed. If he
> than opens up "http:/outserver/servletName#ViewId2" the user just gets
> displayed View2 without leaving the application.
>
> Is this somehow possible, maybe with the BrowserHistory?
>
> Regards,
> Markus
Hi Markus,
we have run into the same (and more) problem(s) like you and have asked
Eclipsesource to investigate.
We are using a BrowserHistoryListener to navigate to views and (pre)select
an item in the view.
We noticed that this only works for every 2nd invocation of the URL and
Eclipsesource created bug 394401 for that.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=394401
We also find that restarting the application for every navigation operation
is not desirable
https://bugs.eclipse.org/bugs/show_bug.cgi?id=389949
If you or anyone else on this discussion list are interested in sharing the
cost to fix this bug, please contact me.
Thanks!
Lothar
|
|
|
|
Re: Use BrowserHistory for Favourites [message #987854 is a reply to message #987460] |
Wed, 28 November 2012 12:07 |
Eclipse User |
|
|
|
We have now solved it not using the BrowserHistory by adding a JS to the
page that listens for URL changes. The JS calls a ServerViceHanlder that
i.e. opens a view or perspective. After the JS calls the service we
force a UI update via JS with org.eclipse.swt.Request.getInstance().send();
Am 26.11.2012 18:13, schrieb Lothar Werzinger:
> Markus Krüger wrote:
>
>> Hi,
>>
>> would it be possible to use the BrowserHistory mechanism for favorites?
>>
>> For example, we want to be able to open a certain view or object if the
>> user opens the url "http:/outserver/servletName?objectToOpen=ViewId1".
>> Now the user can use this as bookmark and always ends up in the
>> application where he wants to.
>> The problem using this mechanism is, that if he now opens a favorite
>> "http:/outserver/servletName?objectToOpen=ViewId2" then the complete
>> application restarts which results in a new user login etc.
>>
>> The BrowserHistory does not use parameters but anchers that do not lead
>> to a reload of the application. Our demand is, that if the user then
>> opens the application with "http:/outserver/servletName#ViewId1", than
>> the login happens and after that the user gets View1 displayed. If he
>> than opens up "http:/outserver/servletName#ViewId2" the user just gets
>> displayed View2 without leaving the application.
>>
>> Is this somehow possible, maybe with the BrowserHistory?
>>
>> Regards,
>> Markus
>
> Hi Markus,
>
> we have run into the same (and more) problem(s) like you and have asked
> Eclipsesource to investigate.
>
> We are using a BrowserHistoryListener to navigate to views and (pre)select
> an item in the view.
> We noticed that this only works for every 2nd invocation of the URL and
> Eclipsesource created bug 394401 for that.
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=394401
>
>
> We also find that restarting the application for every navigation operation
> is not desirable
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=389949
>
>
> If you or anyone else on this discussion list are interested in sharing the
> cost to fix this bug, please contact me.
>
> Thanks!
>
> Lothar
>
|
|
|
Powered by
FUDForum. Page generated in 0.04335 seconds