|
Re: Is Riena overkill for me? [message #584780 is a reply to message #584768] |
Mon, 15 March 2010 12:18 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Christian Campo![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=christian.campo%40compeople.de) Messages: 597 Registered: July 2009 |
Senior Member |
|
|
Hi Gejay,
sorry that it took me so long to come back to you, but we are all very busy preparing the EclipseCon.
Riena in general can be consumed in pieces. Pieces are:
- riena.core with dependency injection and some core stuff
- riena remote services
- riena ridgets, easy api with additional functionality for markers and validation
- the whole riena including the navigation part
- still you can integration RCP Views into the "whole riena" thingy
Riena also is starting to support controller testing with Riena 2.0. However that means that you seperate Controller and
View (which RCP Views usually dont)
We are using RCP concepts all the way and encourage Dependency Injection which also leads to minimal dependency on Riena
code. However if you dont have our Dependency Injection, you need another one, right ?
If you dont like our navigation concept (which I believe is very powerful and flexible) you need another component that
controls the layout of your RCP app.
Depending on how much of Riena you use will to some degree make that an important part of your app that you need to
replace with something else if you abandon Riena.
I would really suggest that you write a little prototyp with Riena and if you need help, let me know, either on this
newsgroup on riena-dev@eclipse.org or by contacting me in person.
We can also arrange a telco if you need more help or have more questions....
regards
christian campo
Am 10.03.10 13:35, schrieb Geejay:
> Im evaluating Riena as a framework for my RCP project.
>
> My RCP project will need:
>
> -Some sort of navigation framework (wizards)
> -Authentication
>
> We are also a software house so important is also code quality i.e
> - MVC
> -Unit testability of UI
>
> I have looked at the example client project, and a bit of the
> documentation surrounding services etc.
>
> I was wondering whether if I start using Riena, whether I am "locked in"
> to doing things the Riena way or whether I can also use plain vanilla RCP.
>
> I would also like to know what the standard "best practice" paradigm is
> for RCP apps. Should everything be accessed through services? Or can I
> use a standard MVC framework, for e.g to go straight to the Model from
> the Controller using Manager objects?
>
> Many thanks
|
|
|
Re: Is Riena overkill for me? [message #584782 is a reply to message #584780] |
Mon, 15 March 2010 12:19 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Christian Campo![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=christian.campo%40compeople.de) Messages: 597 Registered: July 2009 |
Senior Member |
|
|
And to be honest.....no one yet wanted to get rid of Riena once he/she got started to use it so far :-)
christian
Am 15.03.10 13:18, schrieb Christian Campo:
> Hi Gejay,
>
> sorry that it took me so long to come back to you, but we are all very
> busy preparing the EclipseCon.
>
> Riena in general can be consumed in pieces. Pieces are:
>
> - riena.core with dependency injection and some core stuff
> - riena remote services
> - riena ridgets, easy api with additional functionality for markers and
> validation
> - the whole riena including the navigation part
> - still you can integration RCP Views into the "whole riena" thingy
>
> Riena also is starting to support controller testing with Riena 2.0.
> However that means that you seperate Controller and View (which RCP
> Views usually dont)
>
> We are using RCP concepts all the way and encourage Dependency Injection
> which also leads to minimal dependency on Riena code. However if you
> dont have our Dependency Injection, you need another one, right ?
>
> If you dont like our navigation concept (which I believe is very
> powerful and flexible) you need another component that controls the
> layout of your RCP app.
>
> Depending on how much of Riena you use will to some degree make that an
> important part of your app that you need to replace with something else
> if you abandon Riena.
>
> I would really suggest that you write a little prototyp with Riena and
> if you need help, let me know, either on this newsgroup on
> riena-dev@eclipse.org or by contacting me in person.
>
> We can also arrange a telco if you need more help or have more
> questions....
>
> regards
> christian campo
>
>
> Am 10.03.10 13:35, schrieb Geejay:
>> Im evaluating Riena as a framework for my RCP project.
>>
>> My RCP project will need:
>>
>> -Some sort of navigation framework (wizards)
>> -Authentication
>>
>> We are also a software house so important is also code quality i.e
>> - MVC
>> -Unit testability of UI
>>
>> I have looked at the example client project, and a bit of the
>> documentation surrounding services etc.
>>
>> I was wondering whether if I start using Riena, whether I am "locked in"
>> to doing things the Riena way or whether I can also use plain vanilla
>> RCP.
>>
>> I would also like to know what the standard "best practice" paradigm is
>> for RCP apps. Should everything be accessed through services? Or can I
>> use a standard MVC framework, for e.g to go straight to the Model from
>> the Controller using Manager objects?
>>
>> Many thanks
>
|
|
|
Powered by
FUDForum. Page generated in 0.03080 seconds