Re: EDE documentation

On 06/13/2015 01:53 PM, Alastair Rankine wrote:
> Hence in the documentation I think there should be a clear distinction between these two types of projects. Some of us - who aren’t willing/able to commit to Project.ede files for project maintenance - aren’t going to use the generic project type, and should be steered towards the use of ‘non-owning’ project types. The current EDE documentation - specifically the quickstart section - pretty much assumes that you’re going to use the generic project type.
>
> Instead, I’d like the documentation to accomodate the following use case: as a new user of EDE, I want to be able to set it up to work with an*existing*  codebase, build system, etc. Ideally the documentation should introduce the different types of project early in the document, and how to choose between them.
>
> As always, I may be thinking about this completely the wrong way - in which case please feel free to enlighten me!

Hi Alastair,

I took a stab at completely revamping the EDE documentation organization.

Partly, I took larger sections and put them into their own files.   I 
then used the introduction to introduce two quickstart sections, one for 
wrapping a project, and one for the managed project type that creates a 
Project.ede file.

I'd be very interested in peoples thoughts on this organization, and if 
you think it will help.

Thanks
Eric

------------------------------------------------------------------------------
_______________________________________________
Cedet-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cedet-devel