| PDT2: Source / Public folders, how do they work? [message #93881] |
Wed, 18 February 2009 06:27  |
Eclipse User |
|
|
|
Originally posted by: mnm.criion.net
Hi, I know Java and when src files are compiled the files are stored in
the public folder. Since php isn't compiled locally, what is the point
of having php projects set up this way?
-Michael
|
|
|
| Re: PDT2: Source / Public folders, how do they work? [message #93896 is a reply to message #93881] |
Wed, 18 February 2009 09:10  |
| Eclipse User |
|
|
|
This is a good question, I'll try to be short and explain why the PDT team
has decided to reuse the buildpath mechanism from Java.
on most projects (like in Java) there should be a logical separation
between applicative code (php code) and other external resources (images,
javascript, css, etc). Since it is a good practice to separate these two
kinds of resources to make your project more modular, there is a point in
marking a folder as source folder or as a resource folder. This separation
also helps to be make your code more modular and to reduce the overhead of
Eclipse that is scanning and parsing files to provide editing capabilities
(like code assist and other modeling stuff)
hope this helps,
Roy
Michael N. Madsen wrote:
> Hi, I know Java and when src files are compiled the files are stored in
> the public folder. Since php isn't compiled locally, what is the point
> of having php projects set up this way?
> -Michael
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03929 seconds
Home