Wedge

rev 2294
 13 files changed, 16 insertions(+), 16 deletions(-), 1.71 KiB (yes, I missed using patch sizes... :P)

* More spacinazi. Fascinating... I'm leaving some of the libraries aside (SFTP, Exif etc), because they're not from my codebase anyway. (Load.php, ModerationCenter.php, Notifications.php, Profile-Actions.php, Profile-View.php, SearchAPI-Custom.php, Subs-BoardIndex.php, Subs-Post.php, ManageInfractions.template.php, ManageModeration.template.php, ManageSearch.template.php, profile.js, index.css)

Pandos, I don't remember where we talked about this, but since there's already a topic for that, I'll just reuse it... (You can see from the wedge.org stats that technically, I'm a 'topic re-use' guy, whereas Arantor was a 'new topic crazy' guy...)

So, I've been looking into memcached (for some obscure unrelated reason), and installed a server on my PC, and wasn't thrilled to see that it didn't work.
The reason was pretty stupid, actually. I'm even wondering if SMF has got it right, either...
- reloadSettings load $modSettings, which it does through the cache.
- cache checks $modSettings (which is empty), and determines memcached isn't available. Load from file? Doesn't have anything.
- it then rebuilds the settings from DB, and proceeds to save it to the cache...
- cache checks $modSettings (which is no longer empty), and then saves to memcached. As a result, that entry will never be loaded by reloadSettings, which will continuously rebuild the $modSettings cache. For nothing.

In Wedge, it was a similar codepath, except that $settings ($modSettings) was only checked once; because memcached wasn't available, it would then use the file cache, and effectively keep using it later. So, Wedge is less buggy in that area, although it's due to another bug...

I've fixed it locally, by saving the memcached server data to a Settings.php variable instead. Because it's already loaded by the time $settings reloads from cache, we can effectively reload from memcached. Works.
There are still 3 outstanding bugs, although minor:
- language files don't seem to be stored through memcached. They still use the file cache. I'm not exactly sure why it was done that way. I'm going to assume it was for a reason, so I'll leave it aside for now.
- An admin area issue that forces me to re-enter the memcached server every time I go to that page. No biggie, will fix.
- And related to your topic: there is no php_memcached.dll file for Windows, meaning I can't even begin to test Memcached in Wedge.
This is relatively important to me, because it shouldn't be a big deal to implement this, but I looked into the SMF 2.1 code and they just basically replace memcache_* calls with memcached_* calls, and I can't for the life of me, find any documentation on the procedural versions of Memcached methods. Do they even exist...?!

rev 2292
 3 files changed, 8 insertions(+), 5 deletions(-)

! Wess didn't correctly handle the webkit prefixes on flex-* properties for Safari 7. It only handled 'display: flex', which was pretty useless. (Class-CSS.php)

! While 'true' tests in Wess worked, I'm afraid 'false' didn't, at least not always. It's complicated. (Class-CSS.php)

! Fixed CSS file URLs showing an unneeded keyword. (Subs-Cache.php)

- Another unneeded global. (ssi_examples.php)

Very, very odd... It looks like it's still using display:flex, even after I uploaded a fix to disable it... :-/

Hmpf..! Stupid Safari... -_-

I did all I could to add support for it, and whatever it's supposed o support. I don't really know what's not working here. It seems to be related to the flexbox feature, but... I don't know, it's supposed to support it, isn't it..?
Can you, I don't know, emulate Safari 6 from within Safari 7?

PS: as a reminder-- as of now, none of the Apple browsers are available to ANYONE who doesn't pay them big money for one of their overexpensive, overrated machines. Considering I abandoned my iPod Touch 4 long ago, obviously I don't have iOS 7 on it (it's still on iOS 5.1, and my battery is depleted, and whatever), and can't test either.
So, I guess you're on your own to 'fix' it from their developer tools... (They DO have developer tools, don't they...?? No, at this point, I wouldn't be surprised if they wanted to screw everyone up.)

I won't answer point by point, as this is getting a bit out of control, and I can feel that you're now argumenting for the sake of argumenting, guys...

I've often been guilty of that, and I'm none the wiser for it.
So... To put things into perspective: forumsearch0r, IIRC, is the one guy who registered here right around the day Pete decided to leave the team. Given his interest in the (newly found) Wedge platform, he was of course interested in seeing it 'work', and thus not happy to see Pete leave; so, he took the antagonist position to BK's defense of Pete (I'm not sure it was BK, but I know it was a non-regular poster), and so, for no special reason, you're now starting it all again, but on a personal level this time.

Guys, I don't think any of you has a 'problem', and there's no point in fighting over little problems like this.
forumsearch0r never made it clear he wanted to help develop Wedge; while he did say he was capable, he also never requested an alpha copy, or SVN read access, or Git read access (although in this case, I'm not even sure the change to a Git server was even mentioned in the public area. Ahum.)
He does strike me as a bit of a 'know-it-all', though, more than a troll. When I want to recommend a product, I'll explain why it's better. So far, FS has only made it clear that he preferred Emacs, but didn't give examples of things it can't do that others can't. I've been guilty, in my fouth, of knowitallite, its curable, but it will disappear by itself once you've have about a hundred flame wars about tech products. (For me, it all started with "the Amiga is better than the Atari ST"... The agony!)
BK, I'm not sure why you'd call yourself a friend of mine since I recently felt you were uncomfortable with me (or at least not trusting of me) during a conversation, but really, I don't mind. Call it whatever you want; even though I was bit many times in the past, it's in my nature to naturally trust people to be good-doers rather than wait until they brought the proof of it. (Because we all see ourselves as good-doers, after all. We just need to learn how one's freedom ends where the next man's freedom begins.)

anyway... It's not even 7am, and I'm already babbling on an Internet forum.

Well, just look at Wedge itself and you'll know...

The attention to detail is what separates good from great. And really, it can also make life easier on a daily basis. When you have a wide choice available to you, you tend to choose what makes you more productive. For instance, I already documented the fact that Notepad++ (and NetBeans, for that matter) don't have the main window's vertical scrollbar 'stick' to the right of the screen, meaning I have to voluntarily target the scrollbar thumb with my mouse, instead of just targeting its vertical position, and then moving my mouse to the extreme right of the screen, ensuring it'll respond to my clicks. It doesn't seem like much, but I systematically work like this, moving my mouse to the right, then going up or down until the thumb gets 'highlighted', and then I'll click and drag the thumb. It's important, to me, that software behaves the way I need, or that it can be configured to do so.
The same applies to browsers, BTW. And Opera did it that way. Chrome, too (although these days, until Opera implements vertical tabs, I'm using a Chrome add-on that adds vertical tabs, but also prevents the window from being maximized; it's a shame, but I'm dealing with it until times get better.)An old one, too...

What are their killer features..? Any 'plus' that none of the others have?It only explains the software's name... Not the fact that despite having tons of developers working with it, there's never been a 'git for dummies' version, or anyway, something that would simply rename functions to be in line with usual SVN commands, etc...