And this last one, I really need to get right... I need help for folder names!
I need to fine a folder name for what used to be the 'Sources' folder. It contains, of course, all the main PHP files that power Wedge.
The new name needs to:
- show up before 'languages' in the folder list, and even preferably before 'javascript'. So, it needs to start with a letter between 'A' and 'L' at best, or 'A' and 'I' at worst.
- Reflect the fact that it contains PHP files, or Source files, or things that power the software.
I consider 'code' but it's too close to 'core'.
I also considered 'engine', but maybe it's a bit over the top for that folder.
Anything else, guys..? Don't forget you'll be updating that folder quite often, so might as well help in finding its name... ;)
Should Wedge remove theme support, if it provides an equivalent feature set through skins?
- Yes! Focus on what you know best, and let us break it or make it.
- No! I'm too familiar with the theme system, I don't want to re-learn it all.
- I don't really care. I never played with themes, or skins for that matter.
- I don't know enough about it all to have anything interesting to say.
Pentaxian
-
- Ah!
- Posts: 20
wedge.helmer.co
- Grumpy Old Man
-
- Posts: 18
Farjo,
I agree that lower caps is easier, my personal thought is that all directories start with an uppercase while all files are all lowercase.This makes for a very clean looking directory tree. And from a development side, in the code the directories stand out from the files.
John
I agree that lower caps is easier, my personal thought is that all directories start with an uppercase while all files are all lowercase.This makes for a very clean looking directory tree. And from a development side, in the code the directories stand out from the files.
John
Nao
- Dadman with a boy
-
-
- Posts: 16,079
@Pentaxian, it would sound silly to have a sub-sub-folder that's called 'base'.
Re: caps, last week I lowercased all of Wedge's folders, precisely for consistency. I prefer them lowercased generally. As for files, they're still named like in SMF, so that's DoneThisWay. I'm used to this. If I change anything more, I really won't be able to find my mark anymore, and I might as well switch to Elkarte, whose main problem for me is the completely different (shall I say somewhat obtuse...) folder structure. I don't want to mess with Wedge's.
Re: backend/frontend, I think that my main concern is that for years, I've advertised the fact that Pete was the backend guy, while I was the frontend guy. To me, frontend was what people were seeing when they browsed a forum (i.e. all 'public'-facing pages), while backend was the admin area. It works as a definition, but it's not the same as the new definition -- backend is all PHP files that handle requests and gather data, while frontend is all PHP, CSS and JS files that are used in the creation of the final HTML, using the data injected into them by the backend files. They're both valid definitions, I'm just concerned about the fact that I've switched from one to the other, and it doesn't make much sense to do that. On the other hand, I couldn't find anything better.
I like the word 'engine' better for Sources (rather than backend), but that leaves me with the need to find a counter-offer name for Themes (aka templates), that would not be 'frontend' (because it doesn't counter 'engine' but 'backend'), and would be sorted alphabetically after 'engine' ('exsomething'..?), but before 'javascript'... Which leaves us with words starting with F, G, H and I, and a few other words after 'ENG' and before 'JAV'.
So, basically, you all have 4 letters and a half to determine a good name for the folder that will contain *.template.php files... If you accept this challenge... Get started now! I'll mark your test papers tomorrow. :P If I don't get any suggestions I'm excited with, then I'll stick with backend and frontend.
Re: caps, last week I lowercased all of Wedge's folders, precisely for consistency. I prefer them lowercased generally. As for files, they're still named like in SMF, so that's DoneThisWay. I'm used to this. If I change anything more, I really won't be able to find my mark anymore, and I might as well switch to Elkarte, whose main problem for me is the completely different (shall I say somewhat obtuse...) folder structure. I don't want to mess with Wedge's.
Re: backend/frontend, I think that my main concern is that for years, I've advertised the fact that Pete was the backend guy, while I was the frontend guy. To me, frontend was what people were seeing when they browsed a forum (i.e. all 'public'-facing pages), while backend was the admin area. It works as a definition, but it's not the same as the new definition -- backend is all PHP files that handle requests and gather data, while frontend is all PHP, CSS and JS files that are used in the creation of the final HTML, using the data injected into them by the backend files. They're both valid definitions, I'm just concerned about the fact that I've switched from one to the other, and it doesn't make much sense to do that. On the other hand, I couldn't find anything better.
I like the word 'engine' better for Sources (rather than backend), but that leaves me with the need to find a counter-offer name for Themes (aka templates), that would not be 'frontend' (because it doesn't counter 'engine' but 'backend'), and would be sorted alphabetically after 'engine' ('exsomething'..?), but before 'javascript'... Which leaves us with words starting with F, G, H and I, and a few other words after 'ENG' and before 'JAV'.
So, basically, you all have 4 letters and a half to determine a good name for the folder that will contain *.template.php files... If you accept this challenge... Get started now! I'll mark your test papers tomorrow. :P If I don't get any suggestions I'm excited with, then I'll stick with backend and frontend.
wedge.helmer.co
- Grumpy Old Man
-
- Posts: 18
Nao,
Please take a moment to back away from the keyboard as you may be over thinking things here. Backend and frontend are fine or would not still be in the running. Are they really confusing, I think not. Is it just that you have convinced yourself it is a problem because of past history? Maybe, maybe not. They really are ok. If you like engine so much than use it and something like frame,
In the end it really does not matter. As the saying goes "it is what it is". As with any new software package, people will learn where everything is and what it is called. Hell you could call each directory a,b,c or 1,2,3 and people will figure it out. In the end all that is important is Wedge itself and how it functions.
I am retired now but back in the day I was the engineering Directer or VP on on close to 200 software and hardware projects. Trust me when I say this really is not important in the big picture. Wedge the software itself is the end goal. Make a choice and move on.
Grumpy old man
John
Please take a moment to back away from the keyboard as you may be over thinking things here. Backend and frontend are fine or would not still be in the running. Are they really confusing, I think not. Is it just that you have convinced yourself it is a problem because of past history? Maybe, maybe not. They really are ok. If you like engine so much than use it and something like frame,
In the end it really does not matter. As the saying goes "it is what it is". As with any new software package, people will learn where everything is and what it is called. Hell you could call each directory a,b,c or 1,2,3 and people will figure it out. In the end all that is important is Wedge itself and how it functions.
I am retired now but back in the day I was the engineering Directer or VP on on close to 200 software and hardware projects. Trust me when I say this really is not important in the big picture. Wedge the software itself is the end goal. Make a choice and move on.
Grumpy old man
John
Nao
- Dadman with a boy
-
-
- Posts: 16,079
Perhaps I'm hesitating simply because I want to get it right for myself, not for others.
If I can't live with my changes, I can always redo them later, but it's at the cost of annoying more people.
The only alternatives I have for now is:
sources -> engine (this one, I'm very happy with)
templates -> html, interface (I can't believe I didn't come up with 'html' until now, ahem..!)
Again, I need a word that conveys the idea of visuals, or interaction (another word in 'i', hmm...), or frontend as defined above anyway.
If I can't live with my changes, I can always redo them later, but it's at the cost of annoying more people.
The only alternatives I have for now is:
sources -> engine (this one, I'm very happy with)
templates -> html, interface (I can't believe I didn't come up with 'html' until now, ahem..!)
Again, I need a word that conveys the idea of visuals, or interaction (another word in 'i', hmm...), or frontend as defined above anyway.
wedge.helmer.co
- Grumpy Old Man
-
- Posts: 18
Re: One theme to rule them all?
« Reply #80, on January 14th, 2014, 09:10 AM »Last edited on January 14th, 2014, 09:25 AM
Ok here is the word of the day Infotainment.
Just kidding! Take a look through this link and see if anything strikes your fancy.
http://www.techterms.com/list/i
John
Just kidding! Take a look through this link and see if anything strikes your fancy.
http://www.techterms.com/list/i
John
Nao
- Dadman with a boy
-
-
- Posts: 16,079
I prefer to go through non-tech dictionaries for things like that, these are too limited... ;)
Anyway:
http://wedge.org/pub/8336/name-poll-for-something-useless-yay/
Anyway:
http://wedge.org/pub/8336/name-poll-for-something-useless-yay/
Pentaxian
-
- Ah!
- Posts: 20
@Pentaxian, it would sound silly to have a sub-sub-folder that's called 'base'.
Nao
- Dadman with a boy
-
-
- Posts: 16,079
'core' means 'the main point of interest in this folder list', so it works as a root folder.
'engine' means 'what makes Wedge tick', and it'd probably work better as a root folder (while 'backend' is just fine in 'core'), so I see you point.
And sorry, I meant sub-folder for base, not sub-sub-folder.
'engine' means 'what makes Wedge tick', and it'd probably work better as a root folder (while 'backend' is just fine in 'core'), so I see you point.
And sorry, I meant sub-folder for base, not sub-sub-folder.
So, err... The whole point of renaming folders was to get the same usual file order (Sources < Themes < languages < scripts < skins) in my commit log, so that I could quickly find 'core' changes.
With the new structure, I was hoping for app < html < languages < scripts < skins.
Here's the result...
For some reason I don't know, core/app files are located at the END of my changeset list. I can reset the ordering by clicking the 'Path' area in the selector's title of course, but then if I hit Cancel and then re-commit, it's back to that order.
Anybody knows how to fix this..? It's just unacceptable to me!
With the new structure, I was hoping for app < html < languages < scripts < skins.
Here's the result...
For some reason I don't know, core/app files are located at the END of my changeset list. I can reset the ordering by clicking the 'Path' area in the selector's title of course, but then if I hit Cancel and then re-commit, it's back to that order.
Anybody knows how to fix this..? It's just unacceptable to me!
📎 tortoisegit.png - 10.3 kB, 410x246, viewed 183 times.
Oh, scratch that... Looks like making a fake commit (core/app/Admin.php needed some fixing, so I fixed it) somehow fixed my problem.
That gets the prize for fix of the day. And most uses of the word 'fix' in a short post.
That gets the prize for fix of the day. And most uses of the word 'fix' in a short post.