Re: [binarycloud-dev] Future source tree:

[Alex B. <en...@tu...>]

> Hi Alex,
> 
>> This is the source tree I expect we'll have when r2/final is
>> out... I'm sure some of you will have questions re: this list of
>> classes, etc. Please feel free.
> 
>> mod
>>     example_module
> ...
>>         js/
>>         css/
>>         images/
> 
> What do you think about putting these into mod/example_module/resources/* To
> keep the structure more clear.

I was thinking that, and yes I agree.

I'll send an amended list to the list (err)
 
>> This is because make will use the naming conventions below to move files
>> from module and other directories into a single location. That means files
>> must not have naming conflicts, etc - but it keeps the source
>> tree, and the installation process simple.
> 
> Does this mean that each image must have a uniqe name? So module "foo" uses
> a image called edit.gif and module "bar" must not have a image called
> edit.gif!? Or is this seperated in the build tree?

nonono,

we'll have separate subdirectories for each image tree re: a module - but
the above does apply to Validators, etc.

>> -Something.lang.xml will be used by LangKeyer at make-time to key in
>> nagive-language strings into source files.
> Will this work for js/htc files too? Or will this be processed like
> 
> Something.lang_code.js ?

yes, it will work for any file extension, and I should mention that. good
point #2 :)

>> -Something.lang_code.php (i.e. Something.de.php or Something.en.php)
>> means the file will replace Something.php in same directory when the
>> language code is the same as lang_code. Useful for writing the same module
>> that does different things based on the location/language.
> 
> What about media files:
> 
> Something.lang_code.gif
> Something.lang_code.jpg
> Something.lang_code.mpeg
> ...

Same :)

_a