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.
6286
Off-topic / Re: Post count fever
« on September 25th, 2011, 03:07 PM »Oh crap...
In other news, I'm bemused by the Google Tags on this page. Apparently people found their way to this topic by searching for 'bum', 'ass', 'butt', AOL and the words 'fuck' and 'off' have a showing too...
6287
Plugins / Re: Hooking up data loading
« on September 25th, 2011, 12:42 PM »
I'd love to see it :)
6288
Plugins / Re: Hooking up data loading
« on September 25th, 2011, 12:37 PM »
Making it not case by case requires not only standardising the queries but how the query data is used, cf. Display vs Subs-BoardIndex vs loadMemberData.
6289
Plugins / Re: Hooking up data loading
« on September 25th, 2011, 12:12 PM »
Well, either you do it that way, or expressly call a hook for each query and each result (as in by hand)
What occurs to me is that even if you extend a query, you will probably have to add a hook somewhere to make use of the result, which almost has to be case dependent.
As an example, the subs-board index queries to get boards. While you can extend the query and do something with the result directly, you still have to put the result into the relevant array, and maybe even something in the template to be able to make use of that array value.
On the other hand, if you extend the query in loadMemberData, the base information is still available in $user_profile even if you don't hook it in loadMemberContext.
Trouble is, I don't think there's a nice way to deal with it, except on a case by case basis.
What occurs to me is that even if you extend a query, you will probably have to add a hook somewhere to make use of the result, which almost has to be case dependent.
As an example, the subs-board index queries to get boards. While you can extend the query and do something with the result directly, you still have to put the result into the relevant array, and maybe even something in the template to be able to make use of that array value.
On the other hand, if you extend the query in loadMemberData, the base information is still available in $user_profile even if you don't hook it in loadMemberContext.
Trouble is, I don't think there's a nice way to deal with it, except on a case by case basis.
6290
Plugins / Re: Hooking up data loading
« on September 25th, 2011, 11:49 AM »
The ones people actually want to modify, like the monster in loadMemberData, or the one for getting topics, or even the messages request query.
Stuff like the permissions loading queries wouldn't need to be hook able and would in fact be counterproductive to do so because the revised design I have in mind would do away with the need to actually hook onto it, and just use the data itself (like using the current hook in SMF, except with the facility to superset it)
Stuff like the permissions loading queries wouldn't need to be hook able and would in fact be counterproductive to do so because the revised design I have in mind would do away with the need to actually hook onto it, and just use the data itself (like using the current hook in SMF, except with the facility to superset it)
6291
Plugins / Re: Hooking up data loading
« on September 25th, 2011, 11:19 AM »
Well, I like the idea and general execution. I don't think I'd attach it to every query, I'd leave a number of queries alone with the existing infrastructure, without any need to expand *every* query.
Then it's just a case of extending the add-on manager to handle query hooks but that's more dependent on the query architecture to be honest.
Then it's just a case of extending the add-on manager to handle query hooks but that's more dependent on the query architecture to be honest.
6292
Features / Re: New revs - Public comments
« on September 25th, 2011, 02:28 AM »
Re 1031: I don't think it's too many blocks. I think it's really just right because they're the things themers have in the default theme to play with and realign/reposition as they see fit, but I wouldn't go any more thorough than that, at least not in the header (other areas, however, may need changes)
And, in other news, that means I can remove yet another hack from WedgeDesk under certain circumstances, YES.
In other other news, I got to wondering. How much effort would it be, at present, to be able to inject something between the calls to the post template (i.e. displaying ads)? While I'm not bothered myself about being able to use ads, I know that a lot of users *are*, and in between first and second (and between penultimate and last) post is something that does come up.
And, in other news, that means I can remove yet another hack from WedgeDesk under certain circumstances, YES.
In other other news, I got to wondering. How much effort would it be, at present, to be able to inject something between the calls to the post template (i.e. displaying ads)? While I'm not bothered myself about being able to use ads, I know that a lot of users *are*, and in between first and second (and between penultimate and last) post is something that does come up.
6293
Features / Re: New revs
« on September 25th, 2011, 02:25 AM »
Revision: 1032
Author: arantor
Date: 01:25:10, 25 September 2011
Message:
! Added code contributed by Dragooon for add-ons being able to detect their own hooks (i.e. providing a hook and simultaneously registering something against it), plus a fix to one of my bugs, plus what I suspect may be a bugfix to Dragooon's (but I might be wrong), plus a little tweak elsewhere to prevent phantom hooks being registered. (ManageAddons.php, Load.php)
----
Modified : /trunk/Sources/Load.php
Modified : /trunk/Sources/ManageAddons.php
Author: arantor
Date: 01:25:10, 25 September 2011
Message:
! Added code contributed by Dragooon for add-ons being able to detect their own hooks (i.e. providing a hook and simultaneously registering something against it), plus a fix to one of my bugs, plus what I suspect may be a bugfix to Dragooon's (but I might be wrong), plus a little tweak elsewhere to prevent phantom hooks being registered. (ManageAddons.php, Load.php)
----
Modified : /trunk/Sources/Load.php
Modified : /trunk/Sources/ManageAddons.php
6294
The Pub / [Archive] Re: Logo Madness
« on September 25th, 2011, 12:50 AM »
Interesting association. Though yes, I guess, Wedge is like a heart pumping at the core of sites...
6295
Features / Re: New revs - Public comments
« on September 25th, 2011, 12:11 AM »
Awesome, thanks for testing :)
6297
Off-topic / Re: Doctor Who
« on September 24th, 2011, 09:30 PM »
So, episode 12.
(click to show/hide)
Nice to see the Cybermat!
The Doctor is facing up to his destiny, and is paying a social visit. It's unnatural but it works, because he recognises that he doesn't have long left. It's the first time since he found out, that he's seeming to be resigned to his fate.
Will the skies go dark? There's the question.[1]
We now know beyond doubt that River was in the space suit. We know that she does the deed as a Doctor herself, and that presumably that is the timeline prior to the Time of Angels where she hasn't yet become a professor.
We even see him getting the blue envelopes that he's going to send to himself, River, Amy and Rory, AND him getting the Stetson.
There is still a discrepancy: when he dies, he's 1100 years old, so presumably he's done a lot of solo travel since dropping Amy and Rory off... I can't wait for the result!
Also, here's a thought, is there some reference to what he said in The Beast Below: about that he will have to change his name, because he won't be a doctor any more after killing a beautiful magnificent creature...
1. Ref. Season 4, Forest of the Dead, "Everybody knows that everybody dies and nobody knows it like the Doctor. But I do think that all the skies of all the worlds might just turn dark if he ever, for one moment, accepts it."
6298
The Pub / [Archive] Re: Logo Madness
« on September 24th, 2011, 06:08 PM »Still doesn't mean we can't bring anything to each other. It's important to keep one's options open.
IIRC, I built the skeleton code because I wanted to have one of my skins put the sidebar on the very left of the screen, because I was looking at one of my old sites that was built this way and had a feeling of nostalgia... eh eh
Heck, the most surprising to me, is how natural this all is now.
You know, I'm still not sure about either the logo shape and the logo font...
Yes, true enough, when we started, we mainly saw Wedge as 'SMF for real men' (that was the original joke slogan), that is to say, a SMF for veteran admins who knew it well, and wanted to avoid its issues. I don't know when exactly we realized we'd started making Wedge targeted to just everyone. Our goal was never to be a 'real' SMF competitor, but I think that after spending a year of your life on something, you somehow want it to matter...
There IS room for more skins, whether full skins or inherited skins. Really. The final choice over the 'default' skin will come later, and it can always change. Because people change, too. Ideas and tastes are not carved in stone, they evolve over time.
I reckon I had plenty of ideas that the competition didn't have. I'm even a bit overprotective of them by now...
But I probably need to let these things behind me and focus on new things. There isn't any value in being 'attached' to your earlier achievements. Moving on is necessary at least when working on such a project.
Here's a version that I hope you'll find visually appealing
6299
Features / Re: New revs
« on September 24th, 2011, 03:18 PM »
Revision: 1030
Author: arantor
Date: 14:17:56, 24 September 2011
Message:
! Make sure all the displayed strings are actually pushed through htmlspecialchars, simply because it's not good mojo if you provide XSS facilities in an add-on. (ManageAddons.php)
----
Modified : /trunk/Sources/ManageAddons.php
Author: arantor
Date: 14:17:56, 24 September 2011
Message:
! Make sure all the displayed strings are actually pushed through htmlspecialchars, simply because it's not good mojo if you provide XSS facilities in an add-on. (ManageAddons.php)
----
Modified : /trunk/Sources/ManageAddons.php
6300
Features / Re: New revs - Public comments
« on September 24th, 2011, 02:58 PM »
I've committed the undefined found variable fix, haven't looked into ENUM yet, but will do in a bit.
And I think I nailed the ENUM issue as well :)
Posted: September 24th, 2011, 02:14 PM
And I think I nailed the ENUM issue as well :)