[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: AW: AW: What is Riena about? (was AW: AW: [riena-dev] Ridgets)
|
Alex,
I never said its a free ticket.
The author of the navigation model had in mind that yes you could also
use the navigation model on the server and not only on the client and
independant of any UI. Therefore it has no dependency to
riena.ui.core. I see no point in entering a dependency in the
manifest.mf file if no classes in the "dependent" bundle is used.
Also marker has no relationship to anything in UI. Its a generic set
of interfaces and classes. If you feel that moving these 5 interfaces
and classes is an urgent or important issue please open a bugzilla
entry. We will then probably open a riena.core.marker project, ok if
you think that is better, lets do it.
Still that does change the fact that most if not all projects in riena
will have a dependency to riena.core (which I think was Scott's point
in the first place)
christian
Am 19.06.2008 um 10:56 schrieb Alexander Ziegler:
Hi Chris,
I dont agree your argument that sooner or later every other projects
have
dependency to riena.core, therefore this is maybe free ticket to put
interfaces etc.. Into riena.core. ( exaggerated interpreted :-) )
Actually the navigation model riena.navigation is UI independent on
the
binary level so far... But where else we will use the navigation
model when
not only in the UI? Also server side e.g. Riena on RAP it would be
still
called UI.
Ok, I assume that this caused that the IMarker went in the
riena.core. The
IMarker class comment describes that the Marker is used in the UI
context..
If navigation is only for UI (I assume) then would make more sense
for me
the follow structure:
1) move IMarker to riena.ui.core
2) rename riena.navigation* to riena.ui.navigation*
I think we should reflect these project structure as long as these
projects
arent released.
Alexander
Am 19.06.08 09:15 schrieb "Christian Campo" unter
<christian.campo@xxxxxxxxxxxx>:
Hi Scott,
All Riena projects will sooner or later have a dependency on
riena.core, because it contains a number of help classes that we use
throughout Riena. The Markers are in riena.core and not in
riena.ui.core for the moment because the navigation model projects
that we have need to get access to the markers but we didnt want them
to have a dependency on the UI classes because the NavigationTree and
the NavigationProcessor is really an abstract concept and by itself
UI
independent.
Maybe we change that in the future but thats the way its now and I
dont think these four classes do any harm to the riena.core package.
Like I said all riena projects will have or will have a dependency on
the riena.core project. No plans to have that any different.
regards
christian
Am 19.06.2008 um 00:05 schrieb Scott Lewis:
Hi Elias,
I looked at the code you pointed to. Thanks.
Although I may have missed something, it looks like the only
dependency org.eclipse.riena.ui.* bundles have on
org.eclipse.riena.core are the interfaces and abstract classes in
org.eclipse.riena.core.marker package (is that right?). If it is
right, it sort of begs the question...why not have the
org.eclipse.riena.core.marker package interfaces/classes outside of
the core? (e.g. in org.eclipse.riena.ui.core or new bundle). Then
it would be possible, I think, to have the Riena UI work be a fairly
self-contained unit (org.eclipse.riena.ui.* bundles).
But I guess after looking at it only briefly, there's another thing
I don't understand about the Riena marker concept in the core: why
are interfaces like IMarkable, IMarker, notification, etc., needed
when there is the Platform/workbench resource markers?
http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.platform.doc.user
/concepts/concepts-11.htm
http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.platform.doc.isv/
reference/extension-points/org_eclipse_core_resources_markers.html
Is there something about Riena's concept of markers that is not
possible with the Platform's IMarker's?
Sorry if these questions seem naive, but that's a part of building
community :).
Thanks,
Scott
Volanakis, Elias wrote:
Hi Scott,
the "appropriateness" question is better answered by Riena's
initiators.
For an example on Ridgets see org.eclipse.riena.example.client. The
classes SystemPropertiesView and SystemPropertiesViewController are
a reasonably realistic example showing how to work with ridgets. In
the view you create SWT controls normally and register them with
Riena (addUIControl(...)). In the controller you have access to the
corresponding ridgets (they will be injected). There are further
examples in the packages of this project.
To play around with the examples start the client using the launch
configuration in the project. Switch to the "Playground" tab and
open the "Playground" category (left hand side). The whole client
is pretty much a sandbox for playing around, so you can use it to
see what is currently available.
Kind regards,
Elias.
-----Ursprüngliche Nachricht-----
Von: riena-dev-bounces@xxxxxxxxxxx [mailto:riena-dev-bounces@xxxxxxxxxxx
] Im Auftrag von Scott Lewis
Gesendet: Tuesday, June 17, 2008 15:30
An: Riena Developers list
Betreff: Re: AW: What is Riena about? (was AW: AW: [riena-dev]
Ridgets)
Hi Elias,
Thanks for the pointers, but I've already read them. The question
isn't whether the goals are 'new' or not...but rather whether they
are appropriate given the other things that are going on (e4,
Platform UI, etc).
And for understanding of Ridgets...can't anyone (please) point me
to some code in Riena that shows some of what's being discussed
here? Rather than a presentation or proposal/paper...as I've got
the committed source code in my workspace and I prefer to examine
API rather than read about it.
Thanks,
Scott
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
