Terrific file naming convention

[Leo Zurbriggen]

As I'm integrating Terrific (Terrific-micro) into different systems, I took a look at different integrations and projects. There doesn't seem to be a consistent naming of the different files of modules, which makes it hard to integrate it for all the different approaches used.

I know you don't have to use a structure like this to work with with TerrificJs, but as I see the reusability of modules between projects as a big advantage, I feel like this should be part of the Terrific concept.

Personally, I like this one:

TeaserBox/
-- teaserbox.html

-- teaserbox-second.html
-- js/
---- TeaserBox.js
---- skin/
------ TeaserBox.White.js
-- css/
---- teaserbox.css
------ skin/
-------- white.css

"Official" Terrific micro (like on github):

TeaserBox/
-- teaserbox.html

-- teaserbox-second.html
-- js/
---- teaserbox.js
---- teaserbox-white.js
-- css/
---- teaserbox.css
---- teaserbox-white.css

Terrifically (skins/CamelCase not considered):

TeaserBox/
-- teaserbox.html

-- js/
---- Tc.Module.TeaserBox.js

-- css/
---- teaserbox.css

What are your thoughts on this? Could we come up with something that fits every use case as well as the different systems (Composer/Micro)?

[Marc Diethelm]

Here's another one, from the xtc framework (to be announced).

example

├── skins

│   ├── example-cherry.js

│   └── example-choco.less

├── test
│   └── example.test.js
├── sprites
│   └── icon.png

├── example.hbs
├── example-kiwi.hbs

├── example.js

└── example.less

It's flat, lowercase and consistent. Except the test file, that's a different convention. ;)