Eclipse Community Forums: scout » Best practices for different client types?

Home » Eclipse Projects » scout » Best practices for different client types?(How to develop same feature for different clients?)

Show: Today's Messages :: Show Polls :: Message Navigator

Best practices for different client types? [message #1118685]

Fri, 27 September 2013 13:16

Pietro Bonanno
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?

Thanks

[Updated on: Fri, 27 September 2013 13: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 02:54

Urs Beeli
Messages: 250
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.

Report message to a moderator

Previous Topic:	Feedback from Standalone Client Implementation
Next Topic:	Target file problems

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Oct 07 23:34:33 EDT 2013