Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Riena » Non-trivial Riena sample applications / UI guidelines
Non-trivial Riena sample applications / UI guidelines [message #586180] Thu, 01 July 2010 13:16 Go to next message
Christian Kesselheim is currently offline Christian Kesselheim
Messages: 59
Registered: June 2010
Member
Hi everybody,

just wonder if there're some larger, non-trivial Riena sample applications or UI guidelines available on the net that you can recommend. Anything that surpasses the standard mail/pingpong sample app in terms of functional complexity will do just fine :).

Our problem: Some UI design decisions to be taken when designing a Riena-based application are not at all obvious to an entry-level user that has just worked his way through the official Riena documentation and/or its sample applications, even if he has worked with Eclipse RCP before. I'm not talking of technical aspects (such as "How to set-up server-side authentication?") here, its clearly the "How to structure/design the UI of our application?" type of questions that causes us the biggest headaches right now.

For example:

* Should we represent fundamental use-cases such as "New document" in a document-management application as Riena sub-modules (located under an existing "Documents" module) or simply rely on traditional Eclipse RCP concepts such as commands and toolbar/menubar entries to do the evil deed?
* Should we use ordinary tabs within the main sub-module/view to represent different "property pages" of the same domain entity (e.g. "document #165") or should we instead model each such page as a separate sub-module located under the top-level sub-module that represents the entity itself?
* Whether or not to rely on RCP wizards (WizardDialog sub-classes) for building a Riena application and if the answer is "yes": How to best separate them into model/view/controller classes?

Anyone got some suggestions?

Thanks in advance,

Chris
Re: Non-trivial Riena sample applications / UI guidelines [message #586360 is a reply to message #586180] Mon, 12 July 2010 04:52 Go to previous messageGo to next message
Amel Jakupovic is currently offline Amel Jakupovic
Messages: 52
Registered: March 2010
Member
Hi Cristian,

we have start using Riena like this:

1.) first create one aplication that have nothing
2.) every function (WareHouse, POS, common) we put in new plugin (can be started from main aplication or without)
3.) create one plugin just for creating views and controllers depending on XML
4.) Every view have toolbar, but they are on view, not on application
5.) Organization of view is done with groups and tabs

Now I must see with riena team how can I post the project here, and everybody can see and contribute.
Re: Non-trivial Riena sample applications / UI guidelines [message #586396 is a reply to message #586180] Mon, 12 July 2010 09:08 Go to previous message
Christian Campo is currently offline Christian Campo
Messages: 590
Registered: July 2009
Senior Member
Am 01.07.10 19:16, schrieb Christian Kesselheim:
> Hi everybody,
>
> just wonder if there're some larger, non-trivial Riena sample
> applications or UI guidelines available on the net that you can
> recommend. Anything that surpasses the standard mail/pingpong sample app
> in terms of functional complexity will do just fine :).
>
> Our problem: Some UI design decisions to be taken when designing a
> Riena-based application are not at all obvious to an entry-level user
> that has just worked his way through the official Riena documentation
> and/or its sample applications, even if he has worked with Eclipse RCP
> before. I'm not talking of technical aspects (such as "How to set-up
> server-side authentication?") here, its clearly the "How to
> structure/design the UI of our application?" type of questions that
> causes us the biggest headaches right now.
>
> For example:
>
> * Should we represent fundamental use-cases such as "New document" in a
> document-management application as Riena sub-modules (located under an
> existing "Documents" module) or simply rely on traditional Eclipse RCP
> concepts such as commands and toolbar/menubar entries to do the evil deed?
> * Should we use ordinary tabs within the main sub-module/view to
> represent different "property pages" of the same domain entity (e.g.
> "document #165") or should we instead model each such page as a separate
> sub-module located under the top-level sub-module that represents the
> entity itself?
> * Whether or not to rely on RCP wizards (WizardDialog sub-classes) for
> building a Riena application and if the answer is "yes": How to best
> separate them into model/view/controller classes?
>
> Anyone got some suggestions?
>
> Thanks in advance,
>
> Chris

hi chris,

actually a non-trivial question. It do some extend depends really on your personal taste or the taste of your IAD
designer. There are some more or less trivial examples that should help with what is the difference between a
subapplication, a module and a submodule or at least how we view them. When you consult customers on the use of Riena we
are sometimes surprised because they find different uses for our concept.

So in that sense there is some freedom :-), pretty much the same as if you design an RCP app how to place your views.

I can always offer to do a workshop if you need help on that part. Its hard to give you a good advise otherwiese if I
dont know the context......

- christian
Previous Topic:Is Riena production ready?
Next Topic:Non-trivial Riena sample applications / UI guidelines
Goto Forum:
  


Current Time: Fri Aug 22 13:42:47 EDT 2014

Powered by FUDForum. Page generated in 0.01928 seconds