[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [riena-dev] Example code, scattered across the riena.* namespace
|
I agree. My vote is for keeping the examples organized as they are for
the moment.
Elias.
On Thu, Feb 25, 2010 at 8:38 AM, Christian Campo
<christian.campo@xxxxxxxxxxxx> wrote:
> Hi,
>
> there are multiple ways really to structure a project. I think there is an idea behind the current structure and another behind the way you suggesting it.
>
> Except for the "the-showoff-client" :-) (we dont do slashes in project names and what is a "showoff client" anyway) there is nothing wrong with your structure.
>
> However what I see is a lot of work to restructure the thing and at the end its only of different taste.
>
> I see nothing wrong wie having 3 distinct demo projects which seem to have vanished in your strucure and a demo is really something different than a sample. The demo is sort the complete Riena client/server scenario in one set of projects. A sample hightlights a technical aspect like rcp navigation. The example (and I agree its a synonym for sample) contains currently our playground. The thing where we have all ui stuff and components and play with them. A sample is only one slice (one technical aspect) while the example contains everything from the UI.
>
> Snippets are really meant to be for ridgets only. We never wanted to do them for anything else. Theoretically that would be possible but I am against creating structures that dont have a usecase.
>
> So my vote would be to keep the current structure for now until the pain gets bigger and we have a clearer understanding how to structure the existing code and not leave out all the theorectical aspects.
>
> I agree that all this should be written down somewhere......
>
> thats entirely my fault
>
> christian campo
>
> Am 25.02.2010 um 16:51 schrieb Meyer, Yang:
>
>> Hi everybody,
>>
>> I am quite surprised to see that we have:
>>
>> * org.eclipse.riena.example.client (and why is the application's name *still* prefixed with "SWT"?)
>> * org.eclipse.riena.demo.{client,common,server}
>> * org.eclipse.riena.sample.app.*
>> * org.eclipse.riena.sample.snippets
>>
>> Personally I think that all code that is not part of the framework proper (e.g. code that is there to demonstrate certain aspects of Riena) should go in ONE namespace, maybe something like this:
>>
>> + org.eclipse.riena.examples
>> + snippets (currently all snippets show hwo to use Ridgets, but there might be
>> | | snippets for other parts of Riena in the future, right?)
>> | + ridgets
>> |
>> + remoting
>> | + client
>> | + common
>> | + server
>> |
>> + the-showoff-client (the one with the ridgets playground, UI process,
>> programmatical navigation between nodes, ...)
>>
>> Any thoughts on this?
>>
>> Yang
>>
>> -------------------------------------------------------------
>> compeople AG
>> Untermainanlage 8
>> 60329 Frankfurt/Main
>> fon: 069 / 27 22 18 0
>> fax: 069 / 27 22 18 22
>> web: www.compeople.de
>> Vorstand: Jürgen Wiesmaier
>> Aufsichtsratsvorsitzender: Christian Glanz
>> Sitz der Gesellschaft: Frankfurt/Main
>> Handelsregister Frankfurt HRB 56759
>> Ust-Ident.-Nr: DE207665352
>> -------------------------------------------------------------
>>
>> _______________________________________________
>> 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
>
--
Elias Volanakis | Technical Lead | http://eclipsesource.com
elias@xxxxxxxxxxxxxxxxx | +1 503 929 5537 | @evolanakis
