I am trying to figure out how to move from one RUI handler to another. I have to RUIhandler files with handlers defined in each.
ruiHandler1.egl -> ruiHandler2.egl
When I hit a certain point in my logic in ruiHandler1.egl I want to transfer/open ruiHandler2.egl. Is this possible? I don't need to pass data between them, I just want to display the next RUI "page." I have seen that infobus handles communications between handlers, but how do I start in one handler and then display another? Is InfoBus the only way to do this?
Any help or advice is greatly appreciated.
Pinned topic Moving from one RUI handler to another
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-05-16T18:42:19Z at 2012-05-16T18:42:19Z by dan_darnell
Re: Moving from one RUI handler to another2012-05-07T13:31:14ZThis is the accepted answer. This is the accepted answer.James,
There is no such thing as moving from one page to another (like with JSF). What you need to do is change the children of the page you are on (and which you are "leaving"), by the children of the second page (the page you are "moving" to). You may also want to look at EGL's Dynamic Loader feature. With this feature you can load handlers as needed, limiting the size of the original HTML file which forms your RUI application.
Also, consider upgrading to 188.8.131.52. There are loads of bug fixes in that release.
Re: Moving from one RUI handler to another2012-05-07T14:02:04ZThis is the accepted answer. This is the accepted answer.James,
Here is a tiny test project that shows what I mean (PageOne and PageTwo are implemented as RUIwidget, rather than as handler).
This project has been constructed using RBD 184.108.40.206.
Just run MainPage (which is a handler) and click the button.
JBASkeen 270004GEC5137 Posts
Re: Moving from one RUI handler to another2012-05-08T14:42:18ZThis is the accepted answer. This is the accepted answer.Willem,
Thanks a lot for your response and effort to show me an example of what you mentioned, it was extremely helpful. I am currently trying to piece this all together, I also thought that it was interesting that the additional pages can be declared as widgets, pretty cool. There is so much capability built into EGL/RBD, I wish I could be aware of it all. :)
Re: Moving from one RUI handler to another2012-05-08T18:45:30ZThis is the accepted answer. This is the accepted answer.
- JBASkeen 270004GEC5
You're most welcome. The forum is always a good place for looking at new insights into the product's capabilities. If you have more questions, just post them, everyone is here to help.
SystemAdmin 110000D4XK6195 Posts
Re: Moving from one RUI handler to another2012-05-16T07:10:43ZThis is the accepted answer. This is the accepted answer.
- clogs 2700016NQT
I have a question that's semi-related to this topic. I made a login screen (that could be a Page 1 from your example) and a work screen that's used for performing certain tasks (this one would be Page 2).
So user authenticates her/himself on Page 1 and is successful Page 1 is removed from the Main Page and Page 2 is added. Problem occurs if user tries to refresh the browser session while on Page 2. This causes the session to reset and users gets logged out and sent back to the login screen.
The closest thing to a solution is using history and onBeforeUnload to warn user that if the page is refreshed log out will occur. So I wanted to ask if there is a way to remain on the same page after refreshing the browser session.
dan_darnell 27000038BE973 Posts
Re: Moving from one RUI handler to another2012-05-16T18:42:19ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
That said, I think you are spot on with the notion of just warning the user of the consequences of their "refresh" action. Ultimately, it's a matter of how much time/effort/money you want/need to put into this particular application and your goals for the user experience.