Nao

  • Dadman with a boy
  • Posts: 16,079
Last minute frights
« on January 19th, 2014, 11:37 PM »
So, I'm supposed to release tomorrow...

Today, I changed another set of files (/cache became /gz, and /css and /js were integrated into it), because I didn't like having so many root folders just for caching.
I also screwed up another commit, with a change that was too random and broke other stuff. In the future, these changes will be reverted the usual way, but I much prefer being able to amend a commit. I'll just have to learn, I guess, that I shouldn't push until everything's tested...

My main issue is with the update process. Now I have this /core folder where I log into. Then I have to determine what files I should update. I'm totally lost, because the folder names are no longer distinguished by starting with an uppercase char or something like that.
Voilà. I just don't like the new update process. I find it harder, or longer, than the previous one. But I can't revert either, because this new folder structure has some actual *meaning*. I wanted to remove themes, so I'll have to live with the fact that I can't rely on the Themes folder structure any more.

Believe me... It's hard.

And tomorrow, I'm supposed to set the database structure in stone. I'm supposed to say, "okay, I'll never change it anymore, except for big additions for which I'll write some sort of script."
But the more I look at the SQL file, the more I find things to change.

For instance, MySQL 5.0.3 supports the BIT data format. Ever heard about that..? Me neither. TINYINT(1) is used for booleans in Wedge (and SMF), but it still uses one byte per entry. The BIT(1) format allows the use of 8 times less space. So, yes, it's VERY tempting to start using BIT(1) everywhere, since Wedge will always support it... But... There's a but... WHAT if one of these columns actually has more than two values? Like, for instance, "wedge_screwed_up.IamABoolean = (0, 1, 2)", where "2" was added by a SMF developer to account for a problem that couldn't be solved with binary thinking. It still fits into TINYINT, but not into BIT. Making it prone to bugs in Wedge.

There are dozens of TINYINTs, and I don't know if it's worth double-checking every table to make sure it doesn't use these columns in a weird way.
I can always change everything to BIT(1) later, little by little, but...

It just goes to show that I don't feel ready for a public release. Really, really, I feel like I'm freezing.

Farjo

  • "a valuable asset to the community"
  • Posts: 492
Re: Last minute frights
« Reply #1, on January 20th, 2014, 03:25 AM »
It's a public release but it's not the actual actual release is it?? So you could give it the "don't use this on live" line which gives you plenty of time to change the bits (and bobs). Then so what if there's an update script to be run - it was just a test version.

(So is it an Alpha, Beta or RC?)
Re: Last minute frights
« Reply #2, on January 20th, 2014, 03:27 AM »
But yes, I imagine it's like the night before a big important job interview - doing the last minute prep, suddenly noticing all the things you're not quite sure of and concentrating on those instead of all the things that you will shine at.

Wanchope

  • Posts: 234
Re: Last minute frights
« Reply #3, on January 20th, 2014, 08:01 AM »
You can shift it to next week, it took you a couple of years to reach here, a couple of weeks will not hurt.

Nao

  • Dadman with a boy
  • Posts: 16,079
Re: Last minute frights
« Reply #4, on January 20th, 2014, 08:34 AM »
It's public alpha 3. (Alpha 1 & 2 were private... And released well over a year ago.)
Nothing's feature-frozen until I go RC. Nothing's guaranteed until I go beta. But still, I don't want to have to change the structure again after it's made public.
Seriously, I'm so stressed, I had a horrible night, my throat is aching and I really should take a break.

So, a question.

/core
/root
/src
/sys
/system

Of these 5 folder names currently in consideration for the "main" folder of Wedge (not the Wedge folder itself, but the folder that contains app, html, javascript, languages and skins), which sounds best to you guys..?

@Wanchope> You can talk, you're the one who's laughing right now...

Wanchope

  • Posts: 234
Re: Last minute frights
« Reply #5, on January 20th, 2014, 10:57 AM »Last edited on January 20th, 2014, 01:19 PM
@Nao
No pun intended.
As of the folder name, /core will be about the best.
Posted: January 20th, 2014, 10:53 AM

Double posting, sorry.

Farjo

  • "a valuable asset to the community"
  • Posts: 492
Re: Last minute frights
« Reply #6, on January 20th, 2014, 01:16 PM »
Of those 5 either core or sys, but not root.

Pandos

  • Living on the edge of Wedge
  • Posts: 635
# dpkg-reconfigure brain
error: brain is not installed or configured

Drunken Clam

  • Drool, drool, drool....!
  • Posts: 154

Norodo

  • Oh you Baidu, so randumb. (60 sites being indexed at once? Jeez)
  • Posts: 469

MultiformeIngegno

  • Posts: 1,337

nolsilang

  • Lurking <i class=
  • Posts: 106

Nao

  • Dadman with a boy
  • Posts: 16,079
Re: Last minute frights
« Reply #12, on January 20th, 2014, 02:55 PM »
Core it'll be, then!
I figured that with a shorter name such as sys, it'd be even easier to 'spot' the main folder among the folder list, but now that 'css' and 'js' are gone, there's only 'gz' and 'core' to differentiate between, and 'gz' stands out enough of its own to quickly eliminate it.

I'm still hard at work on Wedge. I wanted to release it this morning, but it's hard, really hard.

Wanchope, "no pun intended" implies you're serious. Are you..?

Wanchope

  • Posts: 234
Re: Last minute frights
« Reply #13, on January 20th, 2014, 04:18 PM »Last edited on January 20th, 2014, 04:26 PM
Yeah, I'm serious. Will like to convert http://jobsngr.com.ng (running on smf) to Wedge but if it can take a week more to do it right, why hurry? Then again, I'm speaking for myself, selfish me.

Nao

  • Dadman with a boy
  • Posts: 16,079
Re: Last minute frights
« Reply #14, on January 20th, 2014, 06:53 PM »
I mean, you say you're laughing, then you imply you're serious about it...

As for converting forums, it won't be possible until I get the importer out. It should work, but honestly I wouldn't bet on it, because I haven't tested it in a while, and I've done too many changes these days...