Home » Archived » Riena » Additional Views in Riena
| Additional Views in Riena [message #20579] |
Sat, 14 February 2009 13:11  |
Eclipse User |
|
|
|
Hi All,
I am currently investigating whether Riena is suitable for a project of
mine. The application will be heavily based on navigation between
objects. As such, I would like to have different views on the right side
of the main content, allowing to jump to related objects (and not using
a Module / SubModule navigation).
Is this currently supported? On all riena screenshots I've seen so far
the content area seems to be a single container and not to allow
additional views.
If not support, is it on the road map and/or how difficult would it be
to implement?
Greetings,
Nils
|
|
| | | |
| Re: Additional Views in Riena [message #21860 is a reply to message #20579] |
Tue, 17 February 2009 17:03  |
| Eclipse User |
|
|
|
Originally posted by: evolanakis.innoopract.com
Nils,
if you don't want to use the module / submodule navigation you CAN still
use Riena.
For example it is possible to use Ridgets within a regular RCP
application, where you define perspectives and views as usual (i.e.
PerspectiveFactory / Perspective Extensions / subclassing ViewPart).
You can examine the classes NavigationView / NavigationController /
Perspective in the 'org.eclipse.riena.sample.app.client.rcpmail' demo
project to see how.
(Don't be confused by the class names, NavigationXXX in this example
does not have anything to do with that module / submodule navigation -
maybe I should rename them ;-).
HTH,
Elias.
Nils Kaiser wrote:
> Hi All,
>
> I am currently investigating whether Riena is suitable for a project of
> mine. The application will be heavily based on navigation between
> objects. As such, I would like to have different views on the right side
> of the main content, allowing to jump to related objects (and not using
> a Module / SubModule navigation).
>
> Is this currently supported? On all riena screenshots I've seen so far
> the content area seems to be a single container and not to allow
> additional views.
>
> If not support, is it on the road map and/or how difficult would it be
> to implement?
>
> Greetings,
>
> Nils
--
---
Elias Volanakis
Innoopract, Inc.
http://www.innoopract.com
|
|
|
| Re: Additional Views in Riena [message #21905 is a reply to message #21860] |
Wed, 18 February 2009 01:49 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Elias Volanakis schrieb:
> Nils,
>
> if you don't want to use the module / submodule navigation
I'm still thinking how to integrate the module/submodule navigation
and also have more then one view "connected" to each module/submodule
node...
perhaps we can talk about this at eclipsecon bof
you CAN still
> use Riena.
>
> For example it is possible to use Ridgets within a regular RCP
> application, where you define perspectives and views as usual (i.e.
> PerspectiveFactory / Perspective Extensions / subclassing ViewPart).
>
Ridgets, Markers, Validation ... is really great -
we'll demonstrate the use of these ridgets at out session
http://www.eclipsecon.org/2009/sessions?id=391
ekke
> You can examine the classes NavigationView / NavigationController /
> Perspective in the 'org.eclipse.riena.sample.app.client.rcpmail' demo
> project to see how.
>
> (Don't be confused by the class names, NavigationXXX in this example
> does not have anything to do with that module / submodule navigation -
> maybe I should rename them ;-).
>
> HTH,
> Elias.
>
>
>
> Nils Kaiser wrote:
>> Hi All,
>>
>> I am currently investigating whether Riena is suitable for a project
>> of mine. The application will be heavily based on navigation between
>> objects. As such, I would like to have different views on the right
>> side of the main content, allowing to jump to related objects (and not
>> using a Module / SubModule navigation).
>>
>> Is this currently supported? On all riena screenshots I've seen so far
>> the content area seems to be a single container and not to allow
>> additional views.
>>
>> If not support, is it on the road map and/or how difficult would it be
>> to implement?
>>
>> Greetings,
>>
>> Nils
>
>
|
|
|
| Re: Additional Views in Riena [message #22507 is a reply to message #21905] |
Mon, 09 March 2009 08:01 |
| Eclipse User |
|
|
|
I'd love to talk about this in the BOF on the EclipseCon but since not everybody will probably come, why not start a
little discussion right here, right now.
As you guys know we use a lot of the RCP stuff internally in Riena. A good example is the subapplication tab on top
which is internally a RCP perspective.
In the same manner we have a navigation pane on the left (really a RCP view) backed by the Navigation Model of Riena and
on the right we have the thing we call WorkArea.
So how would and should we fill the WorkArea. We decided to use the RCP view. Now what I hear from you is, you like to
have multiple views in the WorkArea. So my question back would be,
- who would organize the layout of these multiple views (are they on top of each other or next to each other)
- do you want to close one of them but not the other
- can you bring a closed view back and if yes how
And most important why can you not use one view and have multiple Composites in there (which could be generated even by
multiple classes). Then the View would define with their layout how the Composites are placed in the view. Still you
could drag content from one list in Composite A to another in Composite B. So the concept of a Workarea would be
implemented by the implementation of a RCP view and anything could be placed in here.
If you are comfortable with the RCP way of placing views do you really want to use the Riena Navigation Model or do
intend to use it because you think its required by Riena (which it is not) ?
Dont take me wrong here. I am not in any way trying to persuade you that you dont need what you are looking for. :-)
really not. But I am trying to understand the reasons for your requirements. We are really open to further extend the
Riena UI model. And we are already gaining feedback through our projects some feedback on enhancements of the UI model.
So anyone who likes to share his/her thoughts is welcome.....
thanks
christian
ekke schrieb:
> Elias Volanakis schrieb:
>> Nils,
>>
>> if you don't want to use the module / submodule navigation
>
> I'm still thinking how to integrate the module/submodule navigation
> and also have more then one view "connected" to each module/submodule
> node...
> perhaps we can talk about this at eclipsecon bof
>
> you CAN still
>> use Riena.
>>
>> For example it is possible to use Ridgets within a regular RCP
>> application, where you define perspectives and views as usual (i.e.
>> PerspectiveFactory / Perspective Extensions / subclassing ViewPart).
>>
>
> Ridgets, Markers, Validation ... is really great -
> we'll demonstrate the use of these ridgets at out session
> http://www.eclipsecon.org/2009/sessions?id=391
>
> ekke
>> You can examine the classes NavigationView / NavigationController /
>> Perspective in the 'org.eclipse.riena.sample.app.client.rcpmail' demo
>> project to see how.
>>
>> (Don't be confused by the class names, NavigationXXX in this example
>> does not have anything to do with that module / submodule navigation -
>> maybe I should rename them ;-).
>>
>> HTH,
>> Elias.
>>
>>
>>
>> Nils Kaiser wrote:
>>> Hi All,
>>>
>>> I am currently investigating whether Riena is suitable for a project
>>> of mine. The application will be heavily based on navigation between
>>> objects. As such, I would like to have different views on the right
>>> side of the main content, allowing to jump to related objects (and
>>> not using a Module / SubModule navigation).
>>>
>>> Is this currently supported? On all riena screenshots I've seen so
>>> far the content area seems to be a single container and not to allow
>>> additional views.
>>>
>>> If not support, is it on the road map and/or how difficult would it
>>> be to implement?
>>>
>>> Greetings,
>>>
>>> Nils
>>
>>
|
|
|
| Re: Additional Views in Riena [message #22552 is a reply to message #22507] |
Mon, 09 March 2009 08:23 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
christian,
I have thought exactly about what you're writing:
to have one view with different composites instead of different views -
an in fact: there are some scenarios where this will work very well,
but in other scenarios it fails:
* boss - dashboard - usecase
I need 3 or 4 views as dashboard - views, where each view will be
dragged to another monitor -
this wont work with a single-view-workarea
* one info-view + one edit-view
one view will be dragged out of work area and placed outside on same or
another monitor to get some informations -
this view will be automatic-updated from model and read-only
the other view is the real working area where the user edits data
---
to bring back a closed view (most view are not closeable) there should
be an action on the main-view from work-area
I could live with a "additional views are on top of the workarea-view"
behaviour,
so the workarea-main-view should have the knowlede of connected "child"
views
the main-view must always be there like the concept of riena UI
would be very comfortable if the navigation of riena could support this
ekke
Christian Campo schrieb:
> I'd love to talk about this in the BOF on the EclipseCon but since not
> everybody will probably come, why not start a little discussion right
> here, right now.
>
> As you guys know we use a lot of the RCP stuff internally in Riena. A
> good example is the subapplication tab on top which is internally a RCP
> perspective.
>
> In the same manner we have a navigation pane on the left (really a RCP
> view) backed by the Navigation Model of Riena and on the right we have
> the thing we call WorkArea.
>
> So how would and should we fill the WorkArea. We decided to use the RCP
> view. Now what I hear from you is, you like to have multiple views in
> the WorkArea. So my question back would be,
> - who would organize the layout of these multiple views (are they on top
> of each other or next to each other)
> - do you want to close one of them but not the other
> - can you bring a closed view back and if yes how
>
> And most important why can you not use one view and have multiple
> Composites in there (which could be generated even by multiple classes).
> Then the View would define with their layout how the Composites are
> placed in the view. Still you could drag content from one list in
> Composite A to another in Composite B. So the concept of a Workarea
> would be implemented by the implementation of a RCP view and anything
> could be placed in here.
> If you are comfortable with the RCP way of placing views do you really
> want to use the Riena Navigation Model or do
> intend to use it because you think its required by Riena (which it is
> not) ?
>
> Dont take me wrong here. I am not in any way trying to persuade you that
> you dont need what you are looking for. :-) really not. But I am trying
> to understand the reasons for your requirements. We are really open to
> further extend the Riena UI model. And we are already gaining feedback
> through our projects some feedback on enhancements of the UI model.
>
> So anyone who likes to share his/her thoughts is welcome.....
>
> thanks
> christian
>
>
> ekke schrieb:
>> Elias Volanakis schrieb:
>>> Nils,
>>>
>>> if you don't want to use the module / submodule navigation
>>
>> I'm still thinking how to integrate the module/submodule navigation
>> and also have more then one view "connected" to each module/submodule
>> node...
>> perhaps we can talk about this at eclipsecon bof
>>
>> you CAN still
>>> use Riena.
>>>
>>> For example it is possible to use Ridgets within a regular RCP
>>> application, where you define perspectives and views as usual (i.e.
>>> PerspectiveFactory / Perspective Extensions / subclassing ViewPart).
>>>
>>
>> Ridgets, Markers, Validation ... is really great -
>> we'll demonstrate the use of these ridgets at out session
>> http://www.eclipsecon.org/2009/sessions?id=391
>>
>> ekke
>>> You can examine the classes NavigationView / NavigationController /
>>> Perspective in the 'org.eclipse.riena.sample.app.client.rcpmail' demo
>>> project to see how.
>>>
>>> (Don't be confused by the class names, NavigationXXX in this example
>>> does not have anything to do with that module / submodule navigation
>>> - maybe I should rename them ;-).
>>>
>>> HTH,
>>> Elias.
>>>
>>>
>>>
>>> Nils Kaiser wrote:
>>>> Hi All,
>>>>
>>>> I am currently investigating whether Riena is suitable for a project
>>>> of mine. The application will be heavily based on navigation between
>>>> objects. As such, I would like to have different views on the right
>>>> side of the main content, allowing to jump to related objects (and
>>>> not using a Module / SubModule navigation).
>>>>
>>>> Is this currently supported? On all riena screenshots I've seen so
>>>> far the content area seems to be a single container and not to allow
>>>> additional views.
>>>>
>>>> If not support, is it on the road map and/or how difficult would it
>>>> be to implement?
>>>>
>>>> Greetings,
>>>>
>>>> Nils
>>>
>>>
|
|
| |
| Re: Additional Views in Riena [message #22816 is a reply to message #22772] |
Thu, 12 March 2009 10:00 |
| Eclipse User |
|
|
|
Nice try with the Riena logo. That would be really a cool framework where every app you create with it is forced to have
a framework logo on top. :-) Why didnt I think of that :-).
We have in Riena a concept for Look and Feel: http://wiki.eclipse.org/Riena_Look_and_Feel
One part is setting colors, fonts, backgrounds, logos, the position of the logo (left, center, middle) the position of
the navigation and many other things. This is defined for the navigation part (left and top) and can (optionally) also
be applied to the view.
The second part (more advanced) allows you to even overwrite the Renderers for the ModuleView, ModuleGroupView and so
on. The Navigation elements. So you like the Apple View or like to have some stylish title bars. You are free to
implement that in your own renderer (painting on the individual GCs).
If you scroll through the New and Noteworthy http://wiki.eclipse.org/Riena_New_And_Noteworthy you find multiple screen
shots of the various views and of course you can replace the Riena logo. Actually on the EclipseCon I have a life
session (Riena app in 25 minutes) where we will show a brand new Look.
The Cashier problem is really a trivial one. Well at least navigation wise. Of course you can handle multiple bills
without closing the other one. Markers allow you to show icons or markers about incomplete transactions.
So each "module" could represent a different bill. New modules can be added as you go along and Modules can easily be
disposed or reopen if you have a few lines of code. If you are on the EclipseCon I can show you how. The Riena Demo
application (part of the download), shows you an example for Customer Records. You can open multiple Customers at the
same time. Try that out and see for yourself (use together with Riena Demo server)
christian
Vel schrieb:
> Let me pour my thoughts. Take this classic superstore application (as
> mentioned in my previous post) - person at the counter serves one by
> one, but not all the time. There are cases wherein the current bill
> cannot be submitted but he has to start billing the next customer. How
> do we achieve this in current navigation model? The asterisk we get in
> Eclipse editors are really useful to show incomplete actions.
>
> Another usecase - the cashier is billing one customer. The previous
> customer comes with a doubt about the price of an item. The cashier
> doesn't have to close the current bill so that he can open the submitted
> bill and clarify the price.
>
> Is Riena going to provide an option to set an organisation's image
> instead of RIENA? :-)
|
|
|
| Re: Additional Views in Riena [message #22860 is a reply to message #22816] |
Thu, 12 March 2009 18:01 |
| Eclipse User |
|
|
|
As my project involves exactly what ekke described on "boss - dashboard"
and if
Riena will support this caracteristica will be very good :-)
Christian Campo wrote:
> Nice try with the Riena logo. That would be really a cool framework where
every app you create with it is forced to have
> a framework logo on top. :-) Why didnt I think of that :-).
> We have in Riena a concept for Look and Feel:
http://wiki.eclipse.org/Riena_Look_and_Feel
> One part is setting colors, fonts, backgrounds, logos, the position of the
logo (left, center, middle) the position of
> the navigation and many other things. This is defined for the navigation
part (left and top) and can (optionally) also
> be applied to the view.
> The second part (more advanced) allows you to even overwrite the Renderers
for the ModuleView, ModuleGroupView and so
> on. The Navigation elements. So you like the Apple View or like to have some
stylish title bars. You are free to
> implement that in your own renderer (painting on the individual GCs).
> If you scroll through the New and Noteworthy
http://wiki.eclipse.org/Riena_New_And_Noteworthy you find multiple screen
> shots of the various views and of course you can replace the Riena logo.
Actually on the EclipseCon I have a life
> session (Riena app in 25 minutes) where we will show a brand new Look.
> The Cashier problem is really a trivial one. Well at least navigation wise.
Of course you can handle multiple bills
> without closing the other one. Markers allow you to show icons or markers
about incomplete transactions.
> So each "module" could represent a different bill. New modules can be added
as you go along and Modules can easily be
> disposed or reopen if you have a few lines of code. If you are on the
EclipseCon I can show you how. The Riena Demo
> application (part of the download), shows you an example for Customer
Records. You can open multiple Customers at the
> same time. Try that out and see for yourself (use together with Riena Demo
server)
> christian
> Vel schrieb:
>> Let me pour my thoughts. Take this classic superstore application (as
>> mentioned in my previous post) - person at the counter serves one by
>> one, but not all the time. There are cases wherein the current bill
>> cannot be submitted but he has to start billing the next customer. How
>> do we achieve this in current navigation model? The asterisk we get in
>> Eclipse editors are really useful to show incomplete actions.
>>
>> Another usecase - the cashier is billing one customer. The previous
>> customer comes with a doubt about the price of an item. The cashier
>> doesn't have to close the current bill so that he can open the submitted
>> bill and clarify the price.
>>
>> Is Riena going to provide an option to set an organisation's image
>> instead of RIENA? :-)
As my project involves exactly what ekke described on " boss - dashboard"
if Riena will support this caracteristica will be very good :-)
|
|
|
| Re: Additional Views in Riena [message #578702 is a reply to message #20579] |
Sun, 15 February 2009 01:06 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Nils Kaiser schrieb:
> Hi All,
>
> I am currently investigating whether Riena is suitable for a project of
> mine. The application will be heavily based on navigation between
> objects. As such, I would like to have different views on the right side
> of the main content, allowing to jump to related objects (and not using
> a Module / SubModule navigation).
>
> Is this currently supported? On all riena screenshots I've seen so far
> the content area seems to be a single container and not to allow
> additional views.
>
> If not support, is it on the road map and/or how difficult would it be
> to implement?
>
> Greetings,
>
> Nils
Nils,
I'm also thinking about "how-to-use-n-views", because this is also very
important for the ERP soultion I'm building:
per ex. there will be views of trucks and orders and schedules using
heavyly drag-n-drop or other use-cases will have some dashboards for the
managers: dragging views on extra monitors...
at the moment we're working on redView (Riena - EMF - Dynamic Views) and
as next step we'll implement CRUD functionality - and this will fit into
the Riena concept well.
then the next step will be to see how to have more complex views and
also use riena-comfort and -navigation. I hope we can discuss these
things at the BOF at eclipseCon
ekke
|
|
|
| Re: Additional Views in Riena [message #578730 is a reply to message #20588] |
Mon, 16 February 2009 04:13 |
| Eclipse User |
|
|
|
Ekke, I am also of the same opinion. I have not worked in Riena for too
long. I started with 'Getting Started -> UI Navigation' and stuck since I
am not able to see my modules on the left side. I compared with the
example and found that example's view is not a subclass of ViewPart but
one of Riena's classes. Also, their 'application' class is a child of
SwtApplication. The tutorial does not address any of these.
I also feel a need for forms (Eclipse Forms) since the right side is the
main workarea for end-users and it should have uniform background colors.
I would go for an approach similar to ManagedForm and FormToolkit. The
colors and fonts in FormToolkit can be initialized with 'theme' and used
in Ridgets. We should not set the foreground and background colors for
each ridget.
Example for multiple views - Take a superstore as example. It is common to
see the clerk proceeding to bill the next customer when the first customer
is counting changes or looking for some missed items. Tabbed approach is
the best to go here.
|
|
|
| Re: Additional Views in Riena [message #578760 is a reply to message #20605] |
Tue, 17 February 2009 03:39 |
| Eclipse User |
|
|
|
Hi Velganesh,
at the moment in Riena we have a Look&Feel with theme to change the
colors, fonts etc. of the Riena navigation widgets. (see
http://wiki.eclipse.org/Riena_Look_and_Feel)
Next week we are starting to extend the Look&Feel so you can define the
font, background etc. of the widgets in the view.
A very simple prototype already exists. These prototype has shown, that
we can only change the font and the background color for all widgets. It
is not possible (at the moment) to change the foreground color of every
SWT widget. You can change the foreground (text color) of a Label but
not the foreground of a (Windows) button.
Your next step will be to intensify our investigations, how the Riena
L&F can change other look features of SWT widgets. E.g. the border color
of a Text, the color of ScrollBar ....
kind regards
Thorsten
Velganesh Subramanian schrieb:
> Ekke, I am also of the same opinion. I have not worked in Riena for too
> long. I started with 'Getting Started -> UI Navigation' and stuck since
> I am not able to see my modules on the left side. I compared with the
> example and found that example's view is not a subclass of ViewPart but
> one of Riena's classes. Also, their 'application' class is a child of
> SwtApplication. The tutorial does not address any of these.
>
> I also feel a need for forms (Eclipse Forms) since the right side is the
> main workarea for end-users and it should have uniform background
> colors. I would go for an approach similar to ManagedForm and
> FormToolkit. The colors and fonts in FormToolkit can be initialized with
> 'theme' and used in Ridgets. We should not set the foreground and
> background colors for each ridget.
>
> Example for multiple views - Take a superstore as example. It is common
> to see the clerk proceeding to bill the next customer when the first
> customer is counting changes or looking for some missed items. Tabbed
> approach is the best to go here.
>
|
|
|
| Re: Additional Views in Riena [message #580759 is a reply to message #20579] |
Tue, 17 February 2009 17:03 |
| Eclipse User |
|
|
|
Nils,
if you don't want to use the module / submodule navigation you CAN still
use Riena.
For example it is possible to use Ridgets within a regular RCP
application, where you define perspectives and views as usual (i.e.
PerspectiveFactory / Perspective Extensions / subclassing ViewPart).
You can examine the classes NavigationView / NavigationController /
Perspective in the 'org.eclipse.riena.sample.app.client.rcpmail' demo
project to see how.
(Don't be confused by the class names, NavigationXXX in this example
does not have anything to do with that module / submodule navigation -
maybe I should rename them ;-).
HTH,
Elias.
Nils Kaiser wrote:
> Hi All,
>
> I am currently investigating whether Riena is suitable for a project of
> mine. The application will be heavily based on navigation between
> objects. As such, I would like to have different views on the right side
> of the main content, allowing to jump to related objects (and not using
> a Module / SubModule navigation).
>
> Is this currently supported? On all riena screenshots I've seen so far
> the content area seems to be a single container and not to allow
> additional views.
>
> If not support, is it on the road map and/or how difficult would it be
> to implement?
>
> Greetings,
>
> Nils
--
---
Elias Volanakis
Innoopract, Inc.
http://www.innoopract.com
|
|
|
| Re: Additional Views in Riena [message #580777 is a reply to message #21860] |
Wed, 18 February 2009 01:49 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Elias Volanakis schrieb:
> Nils,
>
> if you don't want to use the module / submodule navigation
I'm still thinking how to integrate the module/submodule navigation
and also have more then one view "connected" to each module/submodule
node...
perhaps we can talk about this at eclipsecon bof
you CAN still
> use Riena.
>
> For example it is possible to use Ridgets within a regular RCP
> application, where you define perspectives and views as usual (i.e.
> PerspectiveFactory / Perspective Extensions / subclassing ViewPart).
>
Ridgets, Markers, Validation ... is really great -
we'll demonstrate the use of these ridgets at out session
http://www.eclipsecon.org/2009/sessions?id=391
ekke
> You can examine the classes NavigationView / NavigationController /
> Perspective in the 'org.eclipse.riena.sample.app.client.rcpmail' demo
> project to see how.
>
> (Don't be confused by the class names, NavigationXXX in this example
> does not have anything to do with that module / submodule navigation -
> maybe I should rename them ;-).
>
> HTH,
> Elias.
>
>
>
> Nils Kaiser wrote:
>> Hi All,
>>
>> I am currently investigating whether Riena is suitable for a project
>> of mine. The application will be heavily based on navigation between
>> objects. As such, I would like to have different views on the right
>> side of the main content, allowing to jump to related objects (and not
>> using a Module / SubModule navigation).
>>
>> Is this currently supported? On all riena screenshots I've seen so far
>> the content area seems to be a single container and not to allow
>> additional views.
>>
>> If not support, is it on the road map and/or how difficult would it be
>> to implement?
>>
>> Greetings,
>>
>> Nils
>
>
|
|
|
| Re: Additional Views in Riena [message #581086 is a reply to message #21905] |
Mon, 09 March 2009 08:01 |
| Eclipse User |
|
|
|
I'd love to talk about this in the BOF on the EclipseCon but since not everybody will probably come, why not start a
little discussion right here, right now.
As you guys know we use a lot of the RCP stuff internally in Riena. A good example is the subapplication tab on top
which is internally a RCP perspective.
In the same manner we have a navigation pane on the left (really a RCP view) backed by the Navigation Model of Riena and
on the right we have the thing we call WorkArea.
So how would and should we fill the WorkArea. We decided to use the RCP view. Now what I hear from you is, you like to
have multiple views in the WorkArea. So my question back would be,
- who would organize the layout of these multiple views (are they on top of each other or next to each other)
- do you want to close one of them but not the other
- can you bring a closed view back and if yes how
And most important why can you not use one view and have multiple Composites in there (which could be generated even by
multiple classes). Then the View would define with their layout how the Composites are placed in the view. Still you
could drag content from one list in Composite A to another in Composite B. So the concept of a Workarea would be
implemented by the implementation of a RCP view and anything could be placed in here.
If you are comfortable with the RCP way of placing views do you really want to use the Riena Navigation Model or do
intend to use it because you think its required by Riena (which it is not) ?
Dont take me wrong here. I am not in any way trying to persuade you that you dont need what you are looking for. :-)
really not. But I am trying to understand the reasons for your requirements. We are really open to further extend the
Riena UI model. And we are already gaining feedback through our projects some feedback on enhancements of the UI model.
So anyone who likes to share his/her thoughts is welcome.....
thanks
christian
ekke schrieb:
> Elias Volanakis schrieb:
>> Nils,
>>
>> if you don't want to use the module / submodule navigation
>
> I'm still thinking how to integrate the module/submodule navigation
> and also have more then one view "connected" to each module/submodule
> node...
> perhaps we can talk about this at eclipsecon bof
>
> you CAN still
>> use Riena.
>>
>> For example it is possible to use Ridgets within a regular RCP
>> application, where you define perspectives and views as usual (i.e.
>> PerspectiveFactory / Perspective Extensions / subclassing ViewPart).
>>
>
> Ridgets, Markers, Validation ... is really great -
> we'll demonstrate the use of these ridgets at out session
> http://www.eclipsecon.org/2009/sessions?id=391
>
> ekke
>> You can examine the classes NavigationView / NavigationController /
>> Perspective in the 'org.eclipse.riena.sample.app.client.rcpmail' demo
>> project to see how.
>>
>> (Don't be confused by the class names, NavigationXXX in this example
>> does not have anything to do with that module / submodule navigation -
>> maybe I should rename them ;-).
>>
>> HTH,
>> Elias.
>>
>>
>>
>> Nils Kaiser wrote:
>>> Hi All,
>>>
>>> I am currently investigating whether Riena is suitable for a project
>>> of mine. The application will be heavily based on navigation between
>>> objects. As such, I would like to have different views on the right
>>> side of the main content, allowing to jump to related objects (and
>>> not using a Module / SubModule navigation).
>>>
>>> Is this currently supported? On all riena screenshots I've seen so
>>> far the content area seems to be a single container and not to allow
>>> additional views.
>>>
>>> If not support, is it on the road map and/or how difficult would it
>>> be to implement?
>>>
>>> Greetings,
>>>
>>> Nils
>>
>>
|
|
|
| Re: Additional Views in Riena [message #581100 is a reply to message #22507] |
Mon, 09 March 2009 08:23 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
christian,
I have thought exactly about what you're writing:
to have one view with different composites instead of different views -
an in fact: there are some scenarios where this will work very well,
but in other scenarios it fails:
* boss - dashboard - usecase
I need 3 or 4 views as dashboard - views, where each view will be
dragged to another monitor -
this wont work with a single-view-workarea
* one info-view + one edit-view
one view will be dragged out of work area and placed outside on same or
another monitor to get some informations -
this view will be automatic-updated from model and read-only
the other view is the real working area where the user edits data
---
to bring back a closed view (most view are not closeable) there should
be an action on the main-view from work-area
I could live with a "additional views are on top of the workarea-view"
behaviour,
so the workarea-main-view should have the knowlede of connected "child"
views
the main-view must always be there like the concept of riena UI
would be very comfortable if the navigation of riena could support this
ekke
Christian Campo schrieb:
> I'd love to talk about this in the BOF on the EclipseCon but since not
> everybody will probably come, why not start a little discussion right
> here, right now.
>
> As you guys know we use a lot of the RCP stuff internally in Riena. A
> good example is the subapplication tab on top which is internally a RCP
> perspective.
>
> In the same manner we have a navigation pane on the left (really a RCP
> view) backed by the Navigation Model of Riena and on the right we have
> the thing we call WorkArea.
>
> So how would and should we fill the WorkArea. We decided to use the RCP
> view. Now what I hear from you is, you like to have multiple views in
> the WorkArea. So my question back would be,
> - who would organize the layout of these multiple views (are they on top
> of each other or next to each other)
> - do you want to close one of them but not the other
> - can you bring a closed view back and if yes how
>
> And most important why can you not use one view and have multiple
> Composites in there (which could be generated even by multiple classes).
> Then the View would define with their layout how the Composites are
> placed in the view. Still you could drag content from one list in
> Composite A to another in Composite B. So the concept of a Workarea
> would be implemented by the implementation of a RCP view and anything
> could be placed in here.
> If you are comfortable with the RCP way of placing views do you really
> want to use the Riena Navigation Model or do
> intend to use it because you think its required by Riena (which it is
> not) ?
>
> Dont take me wrong here. I am not in any way trying to persuade you that
> you dont need what you are looking for. :-) really not. But I am trying
> to understand the reasons for your requirements. We are really open to
> further extend the Riena UI model. And we are already gaining feedback
> through our projects some feedback on enhancements of the UI model.
>
> So anyone who likes to share his/her thoughts is welcome.....
>
> thanks
> christian
>
>
> ekke schrieb:
>> Elias Volanakis schrieb:
>>> Nils,
>>>
>>> if you don't want to use the module / submodule navigation
>>
>> I'm still thinking how to integrate the module/submodule navigation
>> and also have more then one view "connected" to each module/submodule
>> node...
>> perhaps we can talk about this at eclipsecon bof
>>
>> you CAN still
>>> use Riena.
>>>
>>> For example it is possible to use Ridgets within a regular RCP
>>> application, where you define perspectives and views as usual (i.e.
>>> PerspectiveFactory / Perspective Extensions / subclassing ViewPart).
>>>
>>
>> Ridgets, Markers, Validation ... is really great -
>> we'll demonstrate the use of these ridgets at out session
>> http://www.eclipsecon.org/2009/sessions?id=391
>>
>> ekke
>>> You can examine the classes NavigationView / NavigationController /
>>> Perspective in the 'org.eclipse.riena.sample.app.client.rcpmail' demo
>>> project to see how.
>>>
>>> (Don't be confused by the class names, NavigationXXX in this example
>>> does not have anything to do with that module / submodule navigation
>>> - maybe I should rename them ;-).
>>>
>>> HTH,
>>> Elias.
>>>
>>>
>>>
>>> Nils Kaiser wrote:
>>>> Hi All,
>>>>
>>>> I am currently investigating whether Riena is suitable for a project
>>>> of mine. The application will be heavily based on navigation between
>>>> objects. As such, I would like to have different views on the right
>>>> side of the main content, allowing to jump to related objects (and
>>>> not using a Module / SubModule navigation).
>>>>
>>>> Is this currently supported? On all riena screenshots I've seen so
>>>> far the content area seems to be a single container and not to allow
>>>> additional views.
>>>>
>>>> If not support, is it on the road map and/or how difficult would it
>>>> be to implement?
>>>>
>>>> Greetings,
>>>>
>>>> Nils
>>>
>>>
|
|
|
| Re: Additional Views in Riena [message #581186 is a reply to message #22552] |
Wed, 11 March 2009 11:31 |
| Eclipse User |
|
|
|
Let me pour my thoughts. Take this classic superstore application (as
mentioned in my previous post) - person at the counter serves one by
one, but not all the time. There are cases wherein the current bill
cannot be submitted but he has to start billing the next customer. How
do we achieve this in current navigation model? The asterisk we get in
Eclipse editors are really useful to show incomplete actions.
Another usecase - the cashier is billing one customer. The previous
customer comes with a doubt about the price of an item. The cashier
doesn't have to close the current bill so that he can open the submitted
bill and clarify the price.
Is Riena going to provide an option to set an organisation's image
instead of RIENA? :-)
|
|
|
| Re: Additional Views in Riena [message #581200 is a reply to message #22772] |
Thu, 12 March 2009 10:00 |
| Eclipse User |
|
|
|
Nice try with the Riena logo. That would be really a cool framework where every app you create with it is forced to have
a framework logo on top. :-) Why didnt I think of that :-).
We have in Riena a concept for Look and Feel: http://wiki.eclipse.org/Riena_Look_and_Feel
One part is setting colors, fonts, backgrounds, logos, the position of the logo (left, center, middle) the position of
the navigation and many other things. This is defined for the navigation part (left and top) and can (optionally) also
be applied to the view.
The second part (more advanced) allows you to even overwrite the Renderers for the ModuleView, ModuleGroupView and so
on. The Navigation elements. So you like the Apple View or like to have some stylish title bars. You are free to
implement that in your own renderer (painting on the individual GCs).
If you scroll through the New and Noteworthy http://wiki.eclipse.org/Riena_New_And_Noteworthy you find multiple screen
shots of the various views and of course you can replace the Riena logo. Actually on the EclipseCon I have a life
session (Riena app in 25 minutes) where we will show a brand new Look.
The Cashier problem is really a trivial one. Well at least navigation wise. Of course you can handle multiple bills
without closing the other one. Markers allow you to show icons or markers about incomplete transactions.
So each "module" could represent a different bill. New modules can be added as you go along and Modules can easily be
disposed or reopen if you have a few lines of code. If you are on the EclipseCon I can show you how. The Riena Demo
application (part of the download), shows you an example for Customer Records. You can open multiple Customers at the
same time. Try that out and see for yourself (use together with Riena Demo server)
christian
Vel schrieb:
> Let me pour my thoughts. Take this classic superstore application (as
> mentioned in my previous post) - person at the counter serves one by
> one, but not all the time. There are cases wherein the current bill
> cannot be submitted but he has to start billing the next customer. How
> do we achieve this in current navigation model? The asterisk we get in
> Eclipse editors are really useful to show incomplete actions.
>
> Another usecase - the cashier is billing one customer. The previous
> customer comes with a doubt about the price of an item. The cashier
> doesn't have to close the current bill so that he can open the submitted
> bill and clarify the price.
>
> Is Riena going to provide an option to set an organisation's image
> instead of RIENA? :-)
|
|
|
| Re: Additional Views in Riena [message #581218 is a reply to message #22816] |
Thu, 12 March 2009 18:01 |
| Eclipse User |
|
|
|
As my project involves exactly what ekke described on "boss - dashboard"
and if
Riena will support this caracteristica will be very good :-)
Christian Campo wrote:
> Nice try with the Riena logo. That would be really a cool framework where
every app you create with it is forced to have
> a framework logo on top. :-) Why didnt I think of that :-).
> We have in Riena a concept for Look and Feel:
http://wiki.eclipse.org/Riena_Look_and_Feel
> One part is setting colors, fonts, backgrounds, logos, the position of the
logo (left, center, middle) the position of
> the navigation and many other things. This is defined for the navigation
part (left and top) and can (optionally) also
> be applied to the view.
> The second part (more advanced) allows you to even overwrite the Renderers
for the ModuleView, ModuleGroupView and so
> on. The Navigation elements. So you like the Apple View or like to have some
stylish title bars. You are free to
> implement that in your own renderer (painting on the individual GCs).
> If you scroll through the New and Noteworthy
http://wiki.eclipse.org/Riena_New_And_Noteworthy you find multiple screen
> shots of the various views and of course you can replace the Riena logo.
Actually on the EclipseCon I have a life
> session (Riena app in 25 minutes) where we will show a brand new Look.
> The Cashier problem is really a trivial one. Well at least navigation wise.
Of course you can handle multiple bills
> without closing the other one. Markers allow you to show icons or markers
about incomplete transactions.
> So each "module" could represent a different bill. New modules can be added
as you go along and Modules can easily be
> disposed or reopen if you have a few lines of code. If you are on the
EclipseCon I can show you how. The Riena Demo
> application (part of the download), shows you an example for Customer
Records. You can open multiple Customers at the
> same time. Try that out and see for yourself (use together with Riena Demo
server)
> christian
> Vel schrieb:
>> Let me pour my thoughts. Take this classic superstore application (as
>> mentioned in my previous post) - person at the counter serves one by
>> one, but not all the time. There are cases wherein the current bill
>> cannot be submitted but he has to start billing the next customer. How
>> do we achieve this in current navigation model? The asterisk we get in
>> Eclipse editors are really useful to show incomplete actions.
>>
>> Another usecase - the cashier is billing one customer. The previous
>> customer comes with a doubt about the price of an item. The cashier
>> doesn't have to close the current bill so that he can open the submitted
>> bill and clarify the price.
>>
>> Is Riena going to provide an option to set an organisation's image
>> instead of RIENA? :-)
As my project involves exactly what ekke described on " boss - dashboard"
if Riena will support this caracteristica will be very good :-)
|
|
|
Goto Forum:
Current Time: Fri Oct 31 14:19:14 EDT 2025
Powered by FUDForum. Page generated in 0.06010 seconds |
Home