Eclipse Community Forums: Riena » SwtApplication vs AbstractApplication

Help

Home

Home » Eclipse Projects » Riena » SwtApplication vs AbstractApplication

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

SwtApplication vs AbstractApplication [message #22989]

Tue, 17 March 2009 11:04

Velganesh Subramanian

Messages: 69
Registered: July 2009

Member

I followed the steps mentioned in http://wiki.eclipse.org/Riena_Navigation
to get started with Riena UI. When I dervied my Application class from
AbstractApplication, I couldn't launch the application window. After
exploring org.eclipse.riena.example.client, I switched the parent to
SwtApplication and I could see the window. What is the essential
difference between these two?

Is the name 'NavigationNodeId' apt? 'id' generally refers a String and
this, to me, is off the track. But there is already 'NavigationNode'. I am
void of suggestions.

Report message to a moderator

Re: SwtApplication vs AbstractApplication [message #23031 is a reply to message #22989]

Tue, 17 March 2009 16:16

Christian Campo

Messages: 597
Registered: July 2009

Senior Member

Velganesh Subramanian schrieb:
> I followed the steps mentioned in
> http://wiki.eclipse.org/Riena_Navigation to get started with Riena UI.
> When I dervied my Application class from AbstractApplication, I couldn't
> launch the application window. After exploring
> org.eclipse.riena.example.client, I switched the parent to
> SwtApplication and I could see the window. What is the essential
> difference between these two?
>
> Is the name 'NavigationNodeId' apt? 'id' generally refers a String and
> this, to me, is off the track. But there is already 'NavigationNode'. I
> am void of suggestions.
>
Hi the first answer is really simple. Ridgets and the some of the concepts in Riena are toolkit independant (independant
of SWT). AbstractApplication is a such a toolkit independant thing. You should not use it but rather use SwtApplication.

I am not sure I understand the second question. The navigation model is constructed like a tree. "Application" is the
root element, below is SubApplication, ModuleGroup, Module, SubModule. Each of them are implementations or subclasses of
NavigationNode. They also all have an Id. The Id is necessary so that you can navigation to another node. If you
navigate from "a" to "b", Riena will do everything that is necessary to get you there i.e. expand and close modules,
switch SubApplications. So you use the Id if you formulate a target for navigation. A concrete implementation of such a
point in the Navigation model is a subclass of NavigationNode.

Is that the answer to your question ???

If not please try again. And I try to help you

christian

Report message to a moderator

Re: SwtApplication vs AbstractApplication [message #23072 is a reply to message #23031]

Wed, 18 March 2009 04:11

Velganesh Subramanian

Messages: 69
Registered: July 2009

Member

Thanks for your explanation, Christian. You are partially correct in the
answers.

1. The article suggests that I need to derive my Application from
AbstractApplication. I did and I couldn't launch the window. Since you say
that we shouldn't use AbstractApplication, wiki should be changed.
2. I was bothered about the name for the class 'NavigationNodeId'. I tried
to say that the word 'id' means a String. But here we have a class since
NavigationNodeId has two parts. I would rather make ModuleGroupNode,
ModuleNode and SubModuleNode take two String objects explicitly (typeId
and instanceId).

Are you also working on adding javadoc? WorkareaManager has overloaded
registerDefinition method. Only the example plugin helped me in
understanding their usage.

You are using FormLayout in SubModuleView.createPartControl. I faced some
problems when I tried to use GridLayout for my composite. I will try again
and post my questions.

Report message to a moderator