Wedge

Eh? Its not insert ignore material..?

Went into my general draft section...

I have several drafts <= June 1st, but let's see for today:

1
Off-topic / Re: MySQL query optimization
« Today at 11:14 PM »
 EXPLAIN is one of those things that make possibly the only thing that is more confusing to me than regexps... Actually the

2
Off-topic / Re: Old layout vs new layout?
« Today at 09:32 PM »
 Looking good!

Footer needs extra top padding!

---> The second one was made on my iPod. The first one on Opera Desktop. In both cases, I posted these messages without any further trouble... So there still is a small issue with ghost drafts.

I don't know, I've thought it over and basically -- the badge stuff is not used in a lot of places. I might as well add a sub function that loads the membergroups where show_when (or whatever name the field will have) is !=0. This will/would save extra bytes being loaded on every page when we're on a page where only the membergroup colors are required.

I've already started implementing it that way, but I don't know, maybe I'm wrong...?

Here's the sample...


An array_diff can then be pushed to $user_info['groups'] (or the equivalent thing loaded through LMD or LMC or whatever), to build a list of badges that could be shown. Then we can go iteratively over the group list and keep the badge if show_when is set to 'always show', and delete it if set to 'only show when nothing else is shown' and there's at least one badge already being shown in the list. (Primary group being first priority in the list...)
Well, that's how I'm seeing it done at least. But I'm tired and may be wrong on all accounts.

Going to bed, so you can take time to think about this and tell me what you think is best...

Maybe cache_put_data should be a singleton... wecac::put() :P
Too bad that 'cac' sounds odd in French... (Our equivalent to the Dow Jones.)

I'm pretty much anti-laziness myself when it comes to images. It has its uses but mostly in an infinitely scrolling page.

Same for colors?

For it to work, we'd need to have a flawless draft system ie no ghost drafts as happen from time to time.
I'd rather see Wedge fill in empty textareas with drafts if they're available. Although that would conflict with browser plugins that do just that.

So... I was trying to find inspiration, so I looked into sm.org and found a very old mod (multiple badges) that did a similar thing. I was wondering how it could 'optimize' the database request for these.
Well, it doesn't... It's even worse than what I had in mind -- it does a query per badge, lol.

At this point, I have only two solutions:
- either I insert a FIND_IN_SET(additional_groups) in the LMD function when it comes to the 'mg' table, and then I turn the group entry into an array with membergroup settings for each...
- or I simply give up, and use the code I wrote weeks ago and that I always stop myself from committing. i.e. the global setting in the membergroup settings page, determining whether to show the main group badge, the post group badge, or both, or none.

I'm wary of using FIND_IN_SET(), but OTOH it's also likely that we'll rewrite the additional_groups field to only contain 'public' groups, meaning we'll need to join with a new table to get a proper list of all groups one belongs to, so that would be less of an issue in this case.. (Except that I don't know that there's a point in offering users the ability to create a badge for a user group....?!)

'm a bit lost -- as usual... Hard to get back into the game after this hectic week.