On 17.10.2012, at 13:35, Jan-Jaap Driessen <
janjaap...@gmail.com> wrote:
> On Wed, Oct 17, 2012 at 2:02 AM, David Beitey <
da...@davidjb.com> wrote:
>> Just curious as to whether anyone's got suggestions for a namespace
>> convention for a Fanstatic library that contains both JS and CSS resources.
>> These resources are related to one but can be used independently. My
>> thought was to use 'fanstatic.library_name', but one would have to take care
>> not to use something already in the fanstatic namespace. Anyone see any
>> issues with this approach and/or have a better naming suggestion?
>
> You can't use the fanstatic namespace, as fanstatic is not a namespace
> package. You say the resources can be used separately, so I would
> suggest creating both a css. and a js. package.
Isn't it common convention to name packages that contain bot CSS and JS
js.library_name and just make the resoures available separately as well
as combined?
I.e.:
library_name_js = Resource(library, 'library_name.js')
library_name_css = Resource(library, 'library_name.css')
library_name = Group([library_name_css, library_name.js])
Andreas