On Tue, Feb 8, 2011 at 11:47, Jakob Cederlund <jako...@gmail.com> wrote:
> Do we need both ErlProjectInfo and ErlProjectLayout? In any case, I propose
> that they are internal to the core plugin, and that all external exposure of
> the project is made through IErlProject.
>
ErlProjectInfo contains more information than the layout: the used runtime,
referenced projects and libraries, compilator settings, etc.
ErlProjectLayout describes the layout of this project.
References to external projects/libraries can also use ErlProjectLayout.
The model should have API to change the layout: for example to recognize the
'test' directories as containing source code that should be compiled. But
this API should not be used to traverse the directories and search for erl
files -- the model will provide an API for that instead.
regards,
Vlad
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Erlide-devel mailing list
Erlide-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlide-devel
