New revs - Public comments

Pandos

  • Living on the edge of Wedge
  • Posts: 635
Re: New revs - Public comments
« Reply #615, on December 4th, 2013, 04:36 PM »Last edited on December 4th, 2013, 04:42 PM
Quote from Nao on December 4th, 2013, 04:23 PM
Done, but it also means the box is larger for all languages, and may wrap to the next line when replying to a thought, even if the thought isn't too long... :-/
Thank you. Looks better now!  8-)
Don't see it as a problem. Do you?
Quote
Did you check the $txt['charts'] array, BTW..? Because I *did* make it all up from your original strings, and the addition of 'Alles' and 'Ausses' or something, which I have no idea if they're even grammatically correct...
It's up to date now.
Re: New revs - Public comments
« Reply #616, on December 4th, 2013, 04:38 PM »
Quote from Nao on December 4th, 2013, 04:33 PM
Also, is there a reason you named your German version 'Deutsch (DE)'...? Why not just 'Deutsch'?
English (US) is only there because British people certainly have a case when it comes to British English being the 'proper one' and US English a derivative (lol). But I've settled on English (UK) because there are more Americans, and non-Americans non-British are probably more used to the US grammar, too, so it needed to be done. But German... It's only spoken *widely* in Germany, right..? So it doesn't need the DE, I'd say.
Yes. Because mainly for the same reasons. We have DE_AT (Austria), DE_CH (Swiss). DE_DE means pure german :)
# dpkg-reconfigure brain
error: brain is not installed or configured

Nao

  • Dadman with a boy
  • Posts: 16,068
Re: New revs - Public comments
« Reply #617, on December 4th, 2013, 07:12 PM »
PR merged. Phew ;)
We really, really need to find a way to avoid merge issues in the future. How exactly do you update your repo? Is it something done through the BB website, or a manual pull from a different origin from your local repo..? If it's the former, maybe you should try doing the latter. And maybe, hmm... I dunno, rebasing. Ouch. I still don't get why git is so popular. I'm getting around to using some of its intricate arcanes, but it's very, very tough on those who don't know it. You can be an excellent programmer, and suck at handling git.

Anyway.
Austria and Swiss have less German-speaking users than Germany, so I'd really, really push for it to be just called Deutsch. Then, if an Austrian package gets released (probably 'on top' of the German one), it'll just need to be called Deutsch (AT).

Pandos

  • Living on the edge of Wedge
  • Posts: 635
Re: New revs - Public comments
« Reply #618, on December 4th, 2013, 08:26 PM »Last edited on December 4th, 2013, 09:00 PM
Update from wedge's original is through BB direct.
Update and Commits through Tortoise.
Perhaps is an idea to have an empty branch. Seems to work. But we'll see after my next commit.


What a switch to the net point :)
I'm OK with changing this to German. But Austrian users speaking native german? :)
That's what I mean with it's the same like US and GB. Therefor the naming is correct. :) But I will change it and we will naming AT and CH otherwise. It's OK for me.

Nao

  • Dadman with a boy
  • Posts: 16,068
Re: New revs - Public comments
« Reply #619, on December 4th, 2013, 09:03 PM »
Quote from Pandos on December 4th, 2013, 08:26 PM
Update from wedge's original is through BB direct.
What's this feature called..?
Quote from Pandos on December 4th, 2013, 08:26 PM
Update and Commits through Tortoise.
Go to Tortoise, settings, Git > Remote, add an 'original' remote, with my repo's URL, then pull changes from there into your local repo, and see if you get a 'merge' in the log or not. If you don't, then maybe you can later push to your repo and be done with it. If you get a merge, try doing a git rebase, then the next time you update, do it through 'git pull --rebase original:master', instead of 'git pull original:master'. I'm sure the latter will do the trick, and will remove any merging artefacts, and thus should allow you to commit your branches without any trouble.
Another alternative might be to 'simply' never update your remote repo with mine, and... well, see if it's working when you attempt to do your pull request. I dunno.

It's important for me to get it right, so that I can direct people to the same method you'll be using. I have no problems with merging on the official repo, as long as it's not too obvious. I'm still on the fence when it comes to my very own, particular situation: I should probably have my own personal remote repo, and do pull requests for my stuff, and then have other people review my commits, or alternatively, push to the official repo only when people say that my own personal repo is working fine for them, etc.
Could, basically, be that the official repo is the stable branch, and my repo is my official dev branch.
Of course, I could also have two branches on the official repo, but... Well, I'm still not into branches. Anything that forces me to stash my work every now and then isn't gonna work for me, at least until I'm really desperate to 'simplify' my workflow. (Ahem!)
Quote from Pandos on December 4th, 2013, 08:26 PM
Perhaps is an idea to have an empty branch. Seems to work. But we'll see after my next commit.
Nope, it's not working... :-/
But don't bother, though. I'd already made the change on my local repo, so the renaming was going to be in the next commit either way.
Quote from Pandos on December 4th, 2013, 08:26 PM
I'm OK with changing this to German. But Austrian users speaking native german? :)
If they have a problem with that, they can always rename their country to Deutschland... Oh, it's already taken? ::)
No, seriously, it's not a matter of nationalities. I just do NOT want to make things complicated to users. Believe me, I've spent enough time wondering whether I should have the main language file called 'English', or 'English (US)'. And I'm still not sure about my decision.

Pandos

  • Living on the edge of Wedge
  • Posts: 635
Re: New revs - Public comments
« Reply #620, on December 4th, 2013, 09:07 PM »
Will test it tomorrow when I'm home.
Will test different solutions.

Deutschland is taken? OMG  :niark:

Like I said. I'm fine with renaming it :)

Nao

  • Dadman with a boy
  • Posts: 16,068

MultiformeIngegno

  • Posts: 1,337
Re: New revs - Public comments
« Reply #622, on January 4th, 2014, 02:12 PM »
[master a226178] APC isn't maintained anymore! Should be better to work on Zend Opcache.

Nao

  • Dadman with a boy
  • Posts: 16,068
Re: New revs - Public comments
« Reply #623, on January 4th, 2014, 10:31 PM »
APC is the one installed at alwaysdata so I get to test it firsthand...
Re: New revs - Public comments
« Reply #624, on January 5th, 2014, 01:06 AM »
Also, regarding the latest commits[1]: follow_me is basically a JS feature I wrote that can be done in pure CSS. Amusingly (or not), I only found out about the CSS version a couple of months after implementing the JS code. It was giving me the exact same result (great minds think alike :P), albeit with a couple of changes to be done in CSS so that it worked interchangeably with or without the CSS support.

Main problem is, the compatibility itself...
- Supported in iOS 6 and above, with no prefix. Can't test myself.
- Supported on Firefox 27 and above, BUT only in Aurora versions. That is, Firefox Beta 27 doesn't show anything. -_-
- Support on current Chrome and Opera versions, desktop and mobile, BUT only behind a flag (and it's not even an 'obvious' flag to enable.)

Let's just say, it's quite a bit early to use 'just' the CSS version, but it's nice to know we can all do it in the future.
 1. I've been revisiting my postponed stuff today. I might as well do my best to get my uncommitted file list down to the smallest possible numbers before I make the codebase public...
Re: New revs - Public comments
« Reply #625, on January 5th, 2014, 05:21 PM »
Fixed it in Firefox 27. Well, it's not really a bug. It's that Firefox 27+ Aurora has the feature enabled, while Firefox 26 (current stable) doesn't, and Firefox 27 Beta can enable it, but only after enabling a flag.

So, basically, if you'd rather your browser does the UI work rather than its JavaScript engine:
- In current Chrome or Opera, go to about:flags and enable 'Experimental Web platform' (IIRC)
- In Firefox 27 Beta, go to about:config, type sticky in the search and double-click the entry that comes up.
- In other browsers, "stay tuned" until the browser maker gets to wake up. (IE 11, you definitely aren't up to the game.)

The feature can also easily be used in SMF and ElkArte without any JavaScript, but it will only work on the aforementioned browsers, of course. The JS fallback in Wedge will work on old browsers, too, anything that supports position: fixed (i.e. IE7+, Android 4+, iOS 4+ or 5+, can't remember.)
Re: New revs - Public comments
« Reply #626, on January 5th, 2014, 05:22 PM »
Quote from MultiformeIngegno on January 4th, 2014, 02:12 PM
[master a226178] APC isn't maintained anymore! Should be better to work on Zend Opcache.
Also, I just remembered this: APC is both an opcache and a user data store, while Opcache, AFAIK, is ONLY an opcache, so it only optimizes the PHP file loading, but doesn't allow storing data and replacing the file cache.

Unless I'm mistaken, of course, in which case I'll be happy to implement Zend stuff into Wedge, but really, AFAIK, it's unrelated. Not only that, but APC doesn't work in PHP 5.5 for Windows, so if I wanted a 'fast' system, I'd probably settle on PHP 5.4 + APC, rather than PHP 5.5 alone.

Woot, I'm only 24 posts from the 14k mark... :eheh:

MultiformeIngegno

  • Posts: 1,337
Re: New revs - Public comments
« Reply #627, on January 5th, 2014, 06:18 PM »
Yeah it's only an opcache. But APC isn't maintained anyway :P
If you want to test it I can give you access to my VPS with PHP 5.5.6 installed

Nao

  • Dadman with a boy
  • Posts: 16,068
Re: New revs - Public comments
« Reply #628, on January 5th, 2014, 06:38 PM »
Quote from MultiformeIngegno on January 5th, 2014, 06:18 PM
Yeah it's only an opcache. But APC isn't maintained anyway :P
But APCu is.
http://windows.php.net/downloads/pecl/releases/apcu/
I installed XAMPP, added the ts-x86-vc11 version of APCu into the ext folder, then enabled both OpCache and APCu in the php.ini file:

Code: [Select]
extension=php_apcu.dll
zend_extension=php_opcache.dll

And it works fine. Actually, it's the first time I ever get APC to work at all on my local install... ;)

Which allowed me to do some more testing, and:
1/ it works, unlike the APC version at alwaysdata,
2/ it's just as slow/fast as the file cache, or memcached. (So, basically: if your cache is on the same file system, it's not worth the hassle, just use the file cache.)

As for OpCache, though, I do notice a slight improvement in performance. About 5% to 10%, perhaps. Again, is it worth the hassle..? Probably not. I'll just say, Wedge is fast enough that the PHP cache is NOT its bottleneck... :P
Still, it's good to be able to test these. I'll keep a copy of XAMPP around.
Quote from MultiformeIngegno on January 5th, 2014, 06:18 PM
If you want to test it I can give you access to my VPS with PHP 5.5.6 installed
Nah, I'm fine now, thanks! Unless you're getting totally different results, of course.
Re: New revs - Public comments
« Reply #629, on January 5th, 2014, 07:48 PM »
I redid my PHP 5.5 OpCache tests more seriously.
On a random topic page...
PHP 5.4: 0.14 seconds in average
PHP 5.5: 0.11 seconds in average
PHP 5.5 + OpCache: 0.08 seconds in average.

So, that's definitely worth the hassle, unlike what I said, ah ah.

I also tried multiple levels of file/APCu cache, and all I can say is, I'm getting the exact same numbers whether I'm using APCu, file cache, cache level 1, 2 or 3. It's tempting to remove levels 2 and 3, but... Whatever.

Now, I'm wondering if I should be asking shaitan whether we can use PHP 5.5 on wedge.org... Technically, I have access to the PHP version switch in the admin area, but it doesn't seem to be working, and I don't want to break his forum, which is running SMF and thus probably doesn't support MySQLi, just regular MySQL, which would generate warnings in PHP 5.5. :-/