[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: AW: [riena-dev] Ridgets
|
Hi Scott,
Am 17.06.2008 um 22:37 schrieb Scott Lewis:
Hi Christian,
Christian Campo wrote:
<stuff deleted>
Because communication is your focus that is maybe what you see in
Riena. However again if you look at the Riena proposal as it was
submitted in october it is not solely a remoting infrastructure.
Actually it contains remoting but that is only a small piece of it
(and I dont think we ever communicated anything else).
Riena is also
- a process orientient UI (containing an alternate navigation and
Ridgets for views)
- about using security in a distributed client server environment
- about Object Transaction to support Persistence
- about for Reporting in a distributed environment
- about support for software update for Riena Clients
- etc.....
So I hope we dont get poked for anything that is not Remote
Services in Riena :-).
I don't mean to argue with you Christian, but except for the first
item (a process oriented...), all of the other items you listed have
to do with remoting (..'distributed client/server env', 'object
transaction', '...in a distributed env', 'and sw update for Riena
Clients'). So the first one still seems perhaps a little out of
place to me...but let me try to understand what Ridgets actually are
first :).
Object Transactions are not necessarily about distributed client/
server env. They can also be used in clients for rolling back object
changes i.e. in the UI for cancelled dialogues.
Software Update is probably based on P2 and not necessarily on the
remote services infrastructure of Riena. And UI is really a big piece.
Its about having a look for the Client that does not resemble the RCP
look, its about having a different Navigation pattern, Ridgets, Jumps
to link between parts in your application and some more things. Look
at the list of projects we have. Nearly half of them are already UI
centered and we have just started.
The proposal also lists External Application Integration like
integrating Word, Excel or else, not really a distributed topic.
I hope you don't consider this 'poking'...but rather just a friendly
observation from a co project lead: I tend to prefer fairly narrow
project scopes, because I think it shows a certain realism about how
much can really be successfully addressed by a small/new
project...especially given the EF's/Platform's 'show me the code'
ethic. That is, if the scope gets too large it can become
impossible to fully address all identified areas, and other people
know this.
I mean poking in a friendly way :-). And I know that you only have
good intentions from the number of face to face talks that we had. You
prefer narrow project scopes, good !! We try to be as narrow as
possible, but since we want to Riena to be a platform for client /
server enterprise applications, that means it has to contain a minimal
set of a number of things that we tried to list in the proposal.
So lets stick with the list from the proposal and dont cross out
things as "NOT IN SCOPE" that are actually in the proposal. That
confuses me.
Scott
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
