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
1846
Archived fixes / Re: Repository logs
« on January 20th, 2013, 05:37 AM »
OK, so I'm actually beginning to get this stuff done. Repo editing works, repo deletion works, stupid errors mostly.
Now to write the actual thing that handles serving repo information.
Now to write the actual thing that handles serving repo information.
1848
Plugins / Re: Plugin dependency loading
« on January 20th, 2013, 12:10 AM »
Given how many files that could require per page? No.
The whole point of hooks having loading function is that they load what they need when they need it - forcing it to load everything up front adds a *massive* weight.
I should also add that I personally don't write a lot of interfaces, so this would simply have never occurred to me as a potential issue.
The whole point of hooks having loading function is that they load what they need when they need it - forcing it to load everything up front adds a *massive* weight.
Posted: January 20th, 2013, 12:08 AM
I should also add that I personally don't write a lot of interfaces, so this would simply have never occurred to me as a potential issue.
1849
Plugins / Re: Plugin dependency loading
« on January 20th, 2013, 12:05 AM »
OK, so I see the problem.
Multi inheritance is inherently (pun not intended) is voodoo, seems to me the solution is for plugins to be able to declare an autoloader?
Multi inheritance is inherently (pun not intended) is voodoo, seems to me the solution is for plugins to be able to declare an autoloader?
1850
Plugins / Re: Plugin dependency loading
« on January 19th, 2013, 11:53 PM »
So what's the problem then? Plugin C won't be *loaded* until the hooks are called from A and B.
1851
Plugins / Re: Plugin dependency loading
« on January 19th, 2013, 11:49 PM »
explain 'both hooked by C'?
But still sounds like C needs a lower priority than both A and B.
But still sounds like C needs a lower priority than both A and B.
1852
Plugins / Re: Plugin dependency loading
« on January 19th, 2013, 11:21 PM »
I implemented it like months ago. A given hooked function can declare its priority in the running order, so if it suspects it's going to be running after something else, the plugin-info.xml can give it a lower priority to run with.
In the <function> item, there's an attribute for priority, of 1-100 with 50 being the default.
In the <function> item, there's an attribute for priority, of 1-100 with 50 being the default.
1853
Plugins / Re: Plugin dependency loading
« on January 19th, 2013, 11:18 PM »
That's why they can set priorities :D
1854
Other software / Re: Discussing Elkarte on wedge.org
« on January 19th, 2013, 09:08 PM »
Woop isn't a word as far as I know. Whoop, is 'woo-p'. Whooping cough has it as 'hooping'... yay for English?
1855
Other software / Re: Discussing Elkarte on wedge.org
« on January 19th, 2013, 06:12 PM »* Arantor doesn't watch TBBT -_-
1856
Other software / Re: Discussing Elkarte on wedge.org
« on January 19th, 2013, 06:07 PM »1857
Other software / Re: Discussing Elkarte on wedge.org
« on January 19th, 2013, 05:59 PM »Heck I'd use my share to buy vBulletin and turn it into something nice
Posted: January 19th, 2013, 05:58 PM
Also, I discovered today that I've been pronouncing 'meme' wrong for years. I'd always assumed it was 'me-me' based on the fact that it always seems to be about garnering some attention, thus 'look at me, look at me' -> 'me! me!'
But it's pronounced 'meem' which means I need to find a new phrase because MEEM DEMON doesn't quite roll off the tongue the way ME-ME DEMON does. At least to me.
1858
Other software / Re: Discussing Elkarte on wedge.org
« on January 19th, 2013, 05:55 PM »
MEME DEMON STRIKES AGAIN!
1859
Other software / Re: Discussing Elkarte on wedge.org
« on January 19th, 2013, 03:40 PM »
I don't know what the future holds for Elkarte, I haven't spoken to most of the people there and to be honest while I get on well enough with most of them, I'd rather stay back and not try and influence them in any particular direction, consciously or otherwise.Quote Labradoodle >_< They need a new team, soon, and it needs to be already competent before turning up. The key word here is despair.Quote Given the circumstances as discussed here about its traumatic birth, I'd suggest that that isn't going to happen.Quote Nah. It's not about the money, it's the principle of the thing... they'd never concede proper control of it to us. That much has become abundantly clear.Quote There's nothing wrong with taking some interest in the ecosystem. It affects us, after all. I think I'm pretty in touch with what's going on, knowing some of the things I do right now.
- new dev team for SMF? If yes, dedicated or not? Hope or despair?
- Elkarte's point "being made", fork turned back into SMF 2.x and work ongoing with same dev team?
- SMF offering us ONE... MILLION... DOLLARS! (insert Dr. Evil laugh here) to turn Wedge into SMF 3.0?
I have to say, regardless of anyone's merits, I'm quite shamefully addicted to knowing what's going on in the SMF world.
1860
Features / Re: New revs - Public comments
« on January 19th, 2013, 02:57 PM »
Well, right now we pass in message, whether to parse smileys[1], cache id, what tags to parse and lastly owner id.
We could convert all those other options into a single array, since there's places we don't use cache id, places we use cache id to denote signature and stuff like that - and not all places need an owner id, nor do all places need tags-to-parse lists.
Giving it a series of options does seem a bit cleaner.
We could convert all those other options into a single array, since there's places we don't use cache id, places we use cache id to denote signature and stuff like that - and not all places need an owner id, nor do all places need tags-to-parse lists.
Giving it a series of options does seem a bit cleaner.
| 1. | And I still want to remove print page from that! |