Wedge

Quite a bit = so you'd rather I put weUA::$browser['is_opera'] than weUA::is('opera'), even if I do a quick static cache?

Example:

function is($str)
{
  static $is_cache = array();
  if (isset($is_cache[$str]))
    return $is_cache[$str];
  return $is_cache[$str] = self::hasBrowser($str);
}

weUA bothers me a bit... Maybe weua or even 'weu' or weuse would be best... weUA::is() feels strange when typing it. It's a bit... alien.

Other than that, I've finished porting the functions to an object, converted Wess, it's all working I'd say. Some conversion functions in the CSS parser are going to be slower because of the weUA calls, but as they're cached...

I didn't say that. Firstly, I seem to recall staticclass::$var as not being valid. You're accessing a property rather than a 'variable' per se, but static instances don't strictly have properties in that sense.

In terms of performance, accessing $context['var'] (assuming $context is already in scope) is faster than obj::function(), but the number of calls we're talking about in a typical page load is small enough that we can declutter $context with this.

And in loops, I'm trying to use the variable version anyway.

static::$var is definitely valid on my side... Works quite well.

Class name suggestions please... In all lowercase :)
weua, weu, weage, weuse, webro... (Challenge accepted!) (Oh that was a good episode yesterday....)

lulz at webro


My vote is on weua.

Starting to wonder if it wouldn't be, hmm, smart to have a generic 'we' (or 'you' :P) object where we'd store contextual information like browser data, RTL mode, $user_info -- we::$user['is_admin'] or we::im('admin'), maybe..?
Would save the need to globalize some stuff like $user_info obviously.

I was thinking wesys might be better than 'we' for that, but I'm flexible.

I was sure static::$var didn't work, because I'm sure I'd tried it at some point.

wesys, hmm...? I don't know... I'm trying to keep things short because of the idea that we're going to be using that object a lot... ;)If self::$var is allowed within the singleton, why wouldn't class::$var be allowed outside of it, as long as it's public...?

I dunno, I just seem to remember getting errors, but it was a long time ago I tried it.

Hard to think straight, lots going on here.

Maybe it doesn't work in strict mode...? I dunno.

Anyway, I've started work on moving $user_info over to the we object.
Basically, use we::$user['is_admin'] or we::is('admin'), depending on your tastes. :)

we::is('admin') is shorter to type ;)

the latter looks cleaner

Note for later: inside allowedTo(), make sure to statically store the response from we::is_admin(), because it will be faster than making the function round trip every time.

It's is('admin'), not is_admin(), but it's all right to add a helper function... ;)

BTW, I made a few performance tests... 100k calls for each.

(local) $browser['is_ie6'] => 0.02s
we::$browser['is_ie6'] => 0.036s
we::is('ie6') => 0.32s

Oops...
After some heavy micro-optimization on is(), I managed to get it down to 0.2s, it's still about 10 times slower than a local variable test, or 5 times slower than an object variable test, but we're talking about a function that will never, ever be called 100.000 times over the course of a page execution... Even calling it a thousand times will only add 2 milliseconds to the execution time.
Is that okay..?

Yeah, I'd say that was probably OK ;)