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
3361
Features: Posts & Topics / Re: Likes
« on May 21st, 2012, 08:56 PM »
Hmmmmm, I see your point there.
On the flip side I think that if you've hidden it, you've hidden it for a reason.
On the flip side I think that if you've hidden it, you've hidden it for a reason.
3362
Features / Re: Disable animation on mobile devices
« on May 21st, 2012, 08:22 PM »
I second that idea :)
3363
Features: Posts & Topics / Re: Likes
« on May 21st, 2012, 08:22 PM »
I'm not sure it is, really.
In order to like it, you'd presumably have to read it, which means you'd have to unhide it anway. Might as well hide everything, then.
In order to like it, you'd presumably have to read it, which means you'd have to unhide it anway. Might as well hide everything, then.
3364
The Pub / Re: One more stupid animation...
« on May 21st, 2012, 08:03 PM »
Hmm, I'm not convinced either, but I will acknowledge that after an afternoon of psychological warfare and bureaucracy I'm not in the most positive frame of mind.
3365
Features / Re: Disable animation on mobile devices
« on May 21st, 2012, 08:02 PM »
I know that iOS 5 on a first-gen iPad kind of sucks :/
3366
Features: Posts & Topics / Re: Likes
« on May 21st, 2012, 08:01 PM »
Well, that's kind of the point, when you hide a post it's because you don't consider anything the person has to say of any value so you're not likely to want to like their posts. But if you already did like the post, you're not going to want to hide it.
3367
Features / Re : Rewriting the skin file parser...
« on May 21st, 2012, 03:36 PM »
Foobar doesn't provide editor.css so the root editor.css will be required, and I would assume you'd have to load editor.firefox.css for that too, regardless of replace or inherit.
3368
Features: Posts & Topics / Re: Likes
« on May 21st, 2012, 03:35 PM »
Well, when hidden, IIRC it's the entire post+buttons+signature that's hidden and unless you've actually liked that post already, I see no reason to change that.
3369
Features / Re : Rewriting the skin file parser...
« on May 20th, 2012, 07:57 PM »
Well... replace skins implies replacing everything, no?
Whatever the behaviour is, as long as it's documented and allows people to replace things as necessary, I don't really see it as a big problem.
Whatever the behaviour is, as long as it's documented and allows people to replace things as necessary, I don't really see it as a big problem.
3370
The Pub / Re: The Cookie Law (in the UK at least)
« on May 20th, 2012, 07:37 PM »
Well, that's the thing - if you force users to agree to cookies before you get to any content, you're permanently going to be blocking spiders, no?
3371
Features / Re : Rewriting the skin file parser...
« on May 20th, 2012, 07:18 PM »
Oh, if you're talking about replace, then editor.firefox.css should not be included. The idea then is that the child should replace the parent unless the parent doesn't have it.
If the child has no editor.css at all, then go to the parent (and use the parent's editor.firefox.css if appropriate). But if the child has editor.css and no editor.firefox.css, load the child's editor.css and ignore the parent's editor.firefox.css.
If the child has no editor.css at all, then go to the parent (and use the parent's editor.firefox.css if appropriate). But if the child has editor.css and no editor.firefox.css, load the child's editor.css and ignore the parent's editor.firefox.css.
3372
Features / Re : Rewriting the skin file parser...
« on May 20th, 2012, 07:08 PM »
It should use the top-level's file. The child editor.css should only replace editor.css from the parent. That way if someone wants to replace both, they should state both (and likely will need both anyway)
3373
The Pub / Re: The Cookie Law (in the UK at least)
« on May 20th, 2012, 06:59 PM »
Yup yup, and with all the SEO nightmare attached to that, of course. But in this case it doesn't matter as it's not really stuff designed for search engines.
3374
The Pub / Re: The Cookie Law (in the UK at least)
« on May 20th, 2012, 06:39 PM »
Interesting approach. Note that they're essentially saying 'you cannot use this site until you at least agree to cookie use'.
3375
Features / Re: Aeme features ideas.
« on May 20th, 2012, 04:57 PM »
Having two tables with that content in is probably not worth the effort, to be honest.
The big hits on the table, really, are figuring out which messages to show (which is done by evaluating against the primary key in a range, at present) and then loading pretty much entire rows with the primary key.
What I would be in favour of doing is removing the participation index and actually moving that to a discrete table which allows for proper unfollowing in unread replies, for example.
The big hits on the table, really, are figuring out which messages to show (which is done by evaluating against the primary key in a range, at present) and then loading pretty much entire rows with the primary key.
What I would be in favour of doing is removing the participation index and actually moving that to a discrete table which allows for proper unfollowing in unread replies, for example.