Wedge
Public area => The Pub => Topic started by: Nao on January 14th, 2014, 09:38 AM
-
They need to follow each other alphabetically.
-
I voted /engine and /html. I think I actually prefer /interface, but it feels too long so I chose /html.
-
/engine and /html is my choice. Somebody chose the last option, seriously?
-
Yes, that was me. :P
I don't want to influence the poll votes because I have a personal preference (which is possibly unlike what you might think), but I'm not 100% sure yet, and I thought that maybe doing a poll could help me choose. I may not choose the most popular option (or I just might), but it's helping me set my thoughts straight.
Contrary to what I say in the poll title, it's something important for me to get right. If I get confused by folder names, it just makes common tasks harder for me. Ideally, I would keep /Sources and /Themes, and have /javascript, /languages and /skins inside /Themes, but it just doesn't make sense. Even my own personal comfort isn't enough to justify having skins as a sub-folder of the *.template.php folder. Themes are gone from Wedge, it needs to be made clear. Skins are here to stay, because they're better in every respect.
-
I've updated the poll to allow you guys to vote for one or two options, instead of just one. This way you can just choose to 'eliminate' the option you like the least.
-
Still think /app and /html would be best.
But /engine and /html are okay too I guess.
-
The only suggestions I could come up with:
face
front
inscribe
ink
-
Well, I favour Sources /Themes in this instance. > It's something not really worth changing or losing sleep over.
-
Still think /app and /html would be best.
Adopting app for this poll choice, so all those who voted for the engine/html combo are now in the app/html combo. Feel free to change your votes.
Quite honestly, I'm 50/50 between app/html and backend/frontend, right now. Slight advantage towards the crowd's current preference. Sources/Themes is still a favorite of mine too, but it's unrealistic to keep it. The only 'remainder' of Sources will be the loadSource function, which I'm not planning to rename. (Otherwise, loadTemplate should have been called 'loadTheme' from the start, but that name's taken... So, 'app/backend' has Source files, and 'html/frontend' has Template files, so loadSource and loadTemplate, and that's all.)
Thank you guy to putting up with my silly polls and questions. I know it doesn't REALLY matter to you guys, but I appreciate that you're not too judgmental on the fact that it matters to me... :^^;:
I'm pretty much set on an official public source code release of Wedge tomorrow. But that's my personal goal. If I can do it by January 20, I won't be too mad at me. I still haven't tested installing the forum from scratch, which is probably going to break horribly, ah ah.
-
Yes. Install from scratch is broken. But it can be fixed. :)
A critical error has occurred.This installer was unable to find the installer's language file or files. They should be found under:
/Themes/default/languages
And after fixing, there will be for sure errors with Sources :lol:
Warning: require_once(/usr/local/var/www/wedge1/Sources/Load.php): failed to open stream: No such file or directory in /usr/local/var/www/wedge1/install.php on line 1976
And after fixing the error is below:
Fatal error: Call to undefined function loadSource() in /usr/local/var/www/wedge1/install.php on line 1978
So it's a little bit more work. You'll have to change:
Settings.php
Settings_bak.php
install.php
Not sure what causes the last error. Any hint?
-
But I can only vote once, it doesn't matter anyway. My second vote should have been like.
bread/ and butter/ angrily :)
-
Last error is. Because loadSource is now defined in index.php (otherwise I can't minify Load.php later), so i need to load that too.
Anyone who voted before I updated the poll, can you revote? Just click 'remove my vote'. Thanks! A bit too tied right now...
-
I think I still prefer /engine and /interface, but they're too long and /app and /html is so nice and small so I kept my vote with app/html.
-
'kay, I'm going for app/html.
I did some more tests, planned a 'fake' commit, and it all looked good to me, so it's on.
I can still change my mind before I push to github, thanks to the magic of git filter-branch, but right now, I'd rather focus on getting the thing out, and then getting used to the new structure... :P (Which should be easier, now that I've been able to magically retain exactly the same folder order inside /core compared to the old theme system era.)
-
engine/ and html/ should have been better but for the sake of shorter name, I will vouch for
app/ and html/
-
Well, I favour Sources /Themes in this instance. > It's something not really worth changing or losing sleep over.
-
iface ?
I don't know which is sadder: you wasting valuable time on this or me wasting valuable time thinking of such rubbish suggestions :)
-
I'd rather waste 2 days waiting on the 'right' combination of folder names, than not renaming them, and ending up screaming at my screen every time I want to do a commit.
Unfortunately, as I just posted on the 'One theme' topic, even renaming folders wasn't enough of a safe strat. I'm a bit lost now.
(That, plus the fact that even after moving files around, I still have some fixing to be done. Even, a lot.)
Oh, scratch that... Looks like making a fake commit fixed my problem.
-
Cool!
-
Sure! Now I need to:
- determine whether I keep the $sourcedir variable or upgrade it to an APP_DIR constant.
- fix all other branches (see rebasing topic).
- make a fake install, and fix the process.
- do a quick overview of Wedge, try to determine what will surprise/disappoint users, and try to fix that. :P
- make a quick list of all areas in Wedge that are NOT finished yet but will be finished in the coming weeks, such as notifications, privacy, contact lists, etc. (Is that all? :P)
- determine whether I use github.com/Wedge/wedge or githubhom.com/wedge/forum as the main repo (what? wedge/forum is better, but then it means Wedge forks will show up as 'myaccount/forum', with no mention of Wedge whatsoever...)
- determine whether I use github.com/Wedge or github.com/Wedge (the latter looking better in hardlinks, but not in the actual github page where you have to cope with a lowercased title... It may be stylistic, but...)
- write a blog post.
- push the actual thingy.
- pray that it doesn't underwhelm, after 3 years of work.
Estimated date: January 20.
Personal goal: January 16.
-
Set a date to complete functions, than add two weeks for testing and debug. Push day after the two week mark for better or worse. Don,t forget to remind everyone it is the first beta of many to come.
You will NEVER make it 100% perfect. Any software that is perfect and does not have bugs is obsolete. The sooner you release a beta, the sooner you will find out about bugs when running on other configurations. You will also find out what us users like, dislike and want added.
Grumpy old man
John
-
Set a date to complete functions, than add two weeks for testing and debug. Push day after the two week mark for better or worse. Don,t forget to remind everyone it is the first beta of many to come.
You will NEVER make it 100% perfect. Any software that is perfect and does not have bugs is obsolete.
Believe me, I know how handling a project works. My first project release was 23 years ago. And all I know is that if it's way past its expiration date (mostly thanks to Pete), it's pretty much impossible to get the 'momentum' back, so you have to accept that it'll never be successful beyond a tiny, very minor niche audience. I've had my share of professional successes and failures, so I can deal with either of these fairly well enough. Not a big deal. But it sure is better when it's a success, of course.
The only thing that worries me is that niche audience = requires financial involvement from users to make it a viable long-term solution, = less likely to acquire new 'customers' (and I don't like seeing my users as customers, so it's bad to begin with), = more likely to go out of funds.
But it's not really time to consider this. Right now, I'd like to focus on the positive things, i.e. the Wedge repo will soon be public, which I'm the only one to hate, so... Everyone rejoice, eh..?
I just finished moving my branches out of the way, they're now (for the most part) moved to the stash repo, so I can now reduce the repo's size, probably by cloning it, and I'm all set for a last check.The sooner you release a beta, the sooner you will find out about bugs when running on other configurations. You will also find out what us users like, dislike and want added.
This would have been possible if Wedge was a public repo from day one. Which wasn't possible, because of the SMF 2 beta license at the time we started the project, so... No need to look behind.
-
Or it's deceptively simple. If you only have 10 lines of code and it does its job, your software might be both perfect and never obsolete. You never know.