Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » scout » Best practices for different client types?(How to develop same feature for different clients?)
Best practices for different client types? [message #1118685] Fri, 27 September 2013 17:16 Go to next message
Pietro Bonanno is currently offline Pietro BonannoFriend
Messages: 13
Registered: July 2009
Junior Member
I'll start with a practical example. My application creates and print reports.
I would like to develop different behaviours, depending on client type: e.g. on RAP client I would like to open the PDF on the browser, on Swing I would like to start document print. So, I would implement the abstract feature on the client plugin, and the concrete action on... ?
What is the best practice?


[Updated on: Fri, 27 September 2013 17:32]

Report message to a moderator

Re: Best practices for different client types? [message #1121000 is a reply to message #1118685] Mon, 30 September 2013 06:54 Go to previous message
Urs Beeli is currently offline Urs BeeliFriend
Messages: 571
Registered: October 2012
Location: Bern, Switzerland
Senior Member
Have a look at org.eclipse.scout.rt.shared.ui.UserAgentUtility, it offers a number of methods such as:
- isSwtUi()
- isRapUi()
- isDesktopDevice()
- isWebClien()
and many more that should help you decide which behaviour is needed when you create your report.
Previous Topic:How to run/debug scout SDK from source?
Next Topic:Target file problems
Goto Forum:

Current Time: Wed Jun 20 09:58:54 GMT 2018

Powered by FUDForum. Page generated in 0.01663 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top