Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [dsdp-ercp-dev] Re: New structure proposal for eRCP CVS

I think eSWT projects are the main factor for the confusion. They
represents 50% of the projects and all placed on one level. Refactoring
them in a subfolder will greatly enhance the newcomer experience.
Considering that eSWT can be used standalone, I think we agree that eSWT
should have separate folder.

I think that it will more helpful if there is a document or a page in
the wiki, which explains the architecture and what what is in the CVS -
something, which will guide a newcomer (structure, code style, bug
reporting, etc.). Even the plugins are refactored in separate folders,
it is still hard to get for example what is the difference between
eworkbench, sworkbench and ui.workbench and what is their relation.

I'm however in favor of moving examples in separate folder, because they
aren't worked on constantly. So, it seems natural to put them aside:)

Gorkem Ercan wrote:
> 
> My problem is I can not relate project when I look at CVS, we have
> testharness, example applications, eSWT etc. at the same level and it is
> confusing for a newcomer to start with (I have received this as a
> comment some time ago). I would like to see related projects grouped
> together. eSWT implementations are definite candiate so is the example
> applications.
> I agree by nature eRCP will have less number of bundles but it is still
> confusing.
> -- 
> Gorkem
> 
> Mark Rogalski wrote:
>>
>> I tend to agree with Danail.
>>
>>
>>
>> *Danail Nachev <d.nachev@xxxxxxxxxx>*
>> Sent by: dsdp-ercp-dev-bounces@xxxxxxxxxxx
>>
>> 10/12/2007 10:43 AM
>> Please respond to
>> DSDP ercp list <dsdp-ercp-dev@xxxxxxxxxxx>
>>
>>
>>     
>> To
>>     DSDP ercp list <dsdp-ercp-dev@xxxxxxxxxxx>
>> cc
>>     
>> Subject
>>     Re: [dsdp-ercp-dev] Re: New structure proposal for eRCP CVS
>>
>>
>>
>>     
>>
>>
>>
>>
>>
>> I'm more inclined to have a separate folder only for the eSWT, because
>> it is the only component which is expected grow big when support for new
>> platforms arrive. I don't think it is reasonable to have folders with
>> just a few plugins inside (usually 2-3 plugins).
>>
>> Gorkem Ercan wrote:
>> >
>> > For some reason my diagram for the structure did not go thorough. I am
>> > resending as an image now.
>> >
>> > Gorkem Ercan wrote:
>> >> I think our CVS directory structure started to be very crowded, and
>> >> soon Nokia will be putting in the S60 implementation, it will get even
>> >> more crowded and will be harder to find anything for newcomers.
>> >>
>> >> I would like to propose the below structure for our CVS. On the top
>> >> level, our components and the examples, and divide eSWT further to
>> >> specific implementations.  Please comment on this new structure.
>> >>
>> >>
>> >> --
>> >> Gorkem
>> >>
>> >
>> >
>> >
>> ------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > dsdp-ercp-dev mailing list
>> > dsdp-ercp-dev@xxxxxxxxxxx
>> > https://dev.eclipse.org/mailman/listinfo/dsdp-ercp-dev
>>
>> -- 
>> Danail Nachev
>> Software Engineer/Development Tools
>> ProSyst Labs EOOD
>> -------------------------------------------------
>> stay in touch with your product.
>> -------------------------------------------------
>> _______________________________________________
>> dsdp-ercp-dev mailing list
>> dsdp-ercp-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/dsdp-ercp-dev
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> dsdp-ercp-dev mailing list
>> dsdp-ercp-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/dsdp-ercp-dev
>>   
> 
> _______________________________________________
> dsdp-ercp-dev mailing list
> dsdp-ercp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-ercp-dev
> 
> 

-- 
Danail Nachev
Software Engineer/Development Tools
ProSyst Labs EOOD
-------------------------------------------------
stay in touch with your product.
-------------------------------------------------


Back to the top