Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Arantor
2191
The Pub / Re: Getting ready for an alpha release: WeCSS/Wess improvements
« on December 20th, 2012, 08:56 PM »
we::is('admin') is shorter to type ;)
2192
The Pub / Re: Getting ready for an alpha release: WeCSS/Wess improvements
« on December 19th, 2012, 07:36 PM »
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.
2193
The Pub / Re: Getting ready for an alpha release: WeCSS/Wess improvements
« on December 19th, 2012, 04:59 PM »
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.
2194
Plugins / Re: Message Index Sorting
« on December 19th, 2012, 04:45 PM »
It's not about whether it's a plugin I 'want' to make. It's about whether it's useful.

Avatar on message index... I'm not convinced that's a huge improvement, seeing that XenForo does it. The extra load attached is not trivial to consider.
Quote
Yes. It may be "filter" that I am trying to say and not "sorting", but whatever you call it, you already admitted that there is no point sorting the topic or author alphabetically. It is there for some or no reason.
Sorting by subject has a use for some people, even if it is inefficient. Filtering by subject, I'm not convinced has a use, but if someone wants to make it as a plugin, it can be done, of course.
2195
Plugins / Re: Message Index Sorting
« on December 19th, 2012, 06:02 AM »
Quote
I do know much about coding. So if you say that it is not efficient, it may not be efficient.
There's no 'may not be' about it. Sorting by letters in a database is slower than sorting by numbers, especially when in most cases the table is already in the right order.
Quote
If I am following a friend, I can simply go to his profile and check his post.
You can do that in SMF already.
Quote
If there is a menu for message index, I could simply search my freinds' latest posts and read them
What you're talking about isn't a *sort*, it's a *filter*. And one that's even slower in the real world because there is no way to optimise it.

You see, when you're dealing with data, you build indexes, which tell you quickly where things are. When you pull everything or nearly everything, you don't need the index, you do what's called a table scan, and just get everything - it's fast. When you're being very selective, you can use the index, and it's still fast. But when you're doing what you're asking, you can't use the index, you have to go through every row, which is by comparison very slow. And it's not possible to avoid that.
Quote
I might also want to see a highly/lowly rated/liked topic, (like seems one of the feature here).
Like is a feature. But there's no ability to see highly liked topics, mostly because it's stored at the *post* level, not the topic level. Finding very popular individual posts is relatively easy and quite cheap because of how likes are stored (outside the posts)
Quote
The look can easily be changed and I can see that wedge has made it a little bit different from SMF. The legend box have been removed and the arrangement is made different.
We like the arrangement as it is here.
Quote
1. Avatar could be add in here as plugin as well.
Um... the only reason avatar is not shown is because neither you nor I have set one. No plugin is necessary.
Quote
2. The look / arrangement can be made better by inserting few last post down the topic instead of beside it.
What does that mean?
2196
The Pub / Re: Getting ready for an alpha release: WeCSS/Wess improvements
« on December 19th, 2012, 12:52 AM »
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.
2197
The Pub / Re: Getting ready for an alpha release: WeCSS/Wess improvements
« on December 18th, 2012, 04:05 PM »
+1 for object, best name is weUA. Function calls are quite a bit slower than accessing a variable in scope.
2198
The Pub / Re: Viewing IP addresses and banning
« on December 17th, 2012, 09:03 PM »
Well, I do plan to make it possible to rack up points with warnings (not exactly %, but certain some kind of cumulative system) - but more importantly, the admin can define certain kinds of warnings and define punishments related to those warnings.

I plan, for example, to make it possible to have a 'bad signature' warning, which allows the signature to be hidden from regular users for a day or so. Or trolling could earn a couple of other interesting punishments I have in mind ;)
2199
The Pub / Re: Viewing IP addresses and banning
« on December 17th, 2012, 08:22 PM »
I didn't realise vBulletin points bans were actually up to the stage of preventing even logins, I assumed they were like SMF warnings where you could prevent posting but not prevent logins - whereupon they are two separate things.

I'm still trying to figure some of this stuff for Wedge though.
2200
Plugins / Re: Extending the moderation filter actions when posting
« on December 17th, 2012, 03:35 PM »
Quote
It may be triggered on change, but on my side it never triggers when typing text, only on focusout... Odd. Can you look into it?
Isn't that the definition of onchange for a textbox? I seem to recall onchange only ever triggering when you focusout, not every time there's a keypress.
Quote
Click a radio button (i.e. "applies to the selected"...), nothing happens, which is NOT as intended.
Yes it is. Until you actually select a board, the rule's not valid. It applies to the selected, but you haven't selected any, so this is a rule that is applicable to nothing, and thus useless.

There is no circumstance where a user should be legitimately creating a rule that happens on every post everywhere without *some* kind of qualification on it, even if it's only 'where user is not an admin'.
2201
The Pub / Re: Viewing IP addresses and banning
« on December 17th, 2012, 03:09 PM »
Different kind of ban ;) The per-user thing is not exactly a ban as such, it is a per-account limitation, while bans are - well, bans.
2202
The Pub / Re: Viewing IP addresses and banning
« on December 17th, 2012, 02:31 PM »
Issuing bans via points is no different to issuing warnings in any substantial sense. They are two different systems entirely, and that is where it will be going in Wedge.
2203
The Pub / Re: Viewing IP addresses and banning
« on December 17th, 2012, 12:18 PM »
So the theory holds up, you can see addresses and you can ban people. If you had ban power in Wedge, nothing would change from where I'm standing.
2204
Off-topic / Re: Programming styles, and does it really matter?
« on December 17th, 2012, 05:56 AM »
Also, one thing I've resolved that I'm going to do in the next few days is to extend my spreadsheet. I've already said I have a spreadsheet of SMF mods, and what I'm going to do is add the features of IPB (that aren't already mirrored in an SMF mod that needs making anew for Wedge) to the bottom as part of my to-do list. I don't need to look at the code to do that, I can see the admin functions and figure out what I'd like to see for Wedge in plugin form.

I certainly won't be touching any code of theirs if I can possibly help it, partly because it's the right thing to do (to avoid looking) and partly because I hate their coding standards. So many extra spaces everywhere and way too many extra braces, it almost physically hurts to read their code.
2205
The Pub / Re: Viewing IP addresses and banning
« on December 17th, 2012, 05:29 AM »
That's basically the same thing as option 2. It's doable but it's messy because of the way the ban system works - they'd still potentially be shown that other bans exist, they'd just not be able to edit or remove them, or create new IP/hostname bans.

But that doesn't solve the problem, really. So banning by IP is admin only. Why do we still need to give non-admins IP addresses if admins are the only ones that can actually use them for anything meaningful?