On Tue, Sep 23, 2008 at 11:41 AM, Andrey Tarantsov
<andreyvit@xxxxxxxxx> wrote:
well, given that any folder with a script in it could be considered a source folder
The point is that you sometimes do not want some scripts to be processed. For example, they may be template files you use to generate code, or platform- or configuration-specific files you don't need at the moment, ones that would cause unneeded errors to appear or navigation to provide irrelevant matches if processed by the builder.
BTW, why do you need to skip "etc" in your particular case?
right - i realize this, it just didn't register last night when i raised the issue. i really don't need to skip 'etc', i was just using it as an example of a directory that has no source code in it, but is one i have to explicitly exclude if configure the project root to be a source folder so i don't have to deal w/ it (and any subdirs contained with in) as a source package.
i guess what i would like to see here is a way for the project root (and only the project root, no sub-dirs beneath it) to automatically be considered as a source folder when it came time to build type operations without the user having to explicitly specify it as such.
You can add that to your project creation wizard, or am I missing something?
yes - i can add the project root as a source folder, but i don't want my users to have to do that. i would like the project root (and its immediate contents, no subdirs) to be considered as a source folder when the builders run. most of the project structures i work with have a since 'lib' folder that contains all the module source, a bunch of other subdirs that do not contain source code, and scripts, so i have a structure something like this:
perl
lib (src folder)
foo/
bar/
baz/
script1.pl
script2.pl
script3.pl
i don't want to have to force the user to add 'perl' as a source folder and then start excluding any folder that does not have source in it just so they can get build functionality and still keep the ScriptExplorer view useful. i'd like for the project root to be automatically included w/o the user having to explicitly define it as such - at least in my perl plugin. the code that does this can happily sit in my plugin implementation and be outside of the dltk core (although it may require minor modifications to the core to introduce a method or two that could be overriden).
