Thanks for your response.

I'm still working on developing a standard for consistency but here's what 
I'm following so far: 

   - lowercase for root namespace
   - CamelCase for project namespace and tiddlers.
   - CSS tiddlers follow the convention of the tiddler they accompany.
   - lowercase and hypen-case for widgets, macros, buttons, images and 
   tiddlers that will be embedded in another tiddler or aren't immediately 
   visible to the user.
   - Avoid mixedCase, except within JavasScript code of course (coding 
   conventions are another topic entirely)
   - lowercase and hyphen-case for CSS class names.

Examples:


   - $:/projects/MyProject/MyTiddler
   - $:/projects/MyProject/MyTiddler.css
   - $:/projects/MyProject/Widgets/widget-one.js
   - $:/projects/MyProject/Widgets/widget-two.js
   - $:/projects/MyProject/Widgets/widget-two.css
   - $:/projects/MyProject/Buttons/button1
   - $:/projects/MyProject/Buttons/button2
   - $:/tags/MyProject/Button
   - $:/state/MyProjectDropdown


On Friday, February 17, 2017 at 6:30:16 PM UTC-5, PMario wrote:
>
> On Friday, February 17, 2017 at 10:37:44 PM UTC+1, Novan Leon wrote:
>>
>> I've noticed the following naming conventions present in TW5:
>>
>
> As you found out. There are naming conventions. ... but every user or 
> plugin-author should be free to create there own conventions. *The core 
> tries hard to stay out of the way.* ... So that's why some names, and 
> conventions seem to be "irrational", but they make sense. .... hopefully ;)
>
> -m
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/98cd2aef-1957-41e1-b7bf-f39fda781407%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to