Wedge

Which is why we're not giving it out to anyone except people we know that can deal with this stuff.No, but you *did* suggest it should be opened up to more people. There's a whole range of interpretations of that statement. It ranges everywhere from 'more people should try it, it might get more bugs found and squished' (unlikely) through 'more people should try it, because it's worth trying' and on to 'more people, including me, should have the option to try it' and all the way to 'if I suggest more people should try it, maybe I'll get to play with it in the name of testing'. Text is a wonderfully compact format, it cuts out so much of the non-verbal context that could easily change how your statement is interpreted.

But understand it from my point of view: I've seen many, many people make variations on the same statement, and the vast majority of them don't want it for testing, they just want it because they want it - they don't really want to help with the development or testing, they just want the software. I experienced this most vividly with SimpleDesk; 90% of the beta testers never submitted a bug report, or a suggestion or indeed ANYTHING. Why should this be any different? Yet virtually every one of the beta testers put in some variation about how it should be opened up for testing so that more people would find bugs.

Already the majority of people with beta tester badges haven't said *that* much, though what they have said has been pretty positive - and yet, I know full well that some of them have barely touched it for anything.

I make no apologies for my cynicism. I've been burned way too many times by people making requests 'in the name of the greater good' such as you might call it and almost every single time it's about justifying giving them personally a benefit rather than actually benefiting the greater good.

This is more a braindump than anything else.

I can fully understand keeping the admin settings entirely separate when it was still an SMF mod - because it's a big and complex mod with dozens and dozens of settings - but now it's in Wedge, not only should it adhere to the same UI as everywhere else (or everywhere get adjusted to how Aeva did it, I'm amenable either way as long as it's consistent), it should reuse as much of the same logic as possible.

Unfortunately, given this, we're almost closer to being a rewrite of the admin logic rather than being a simple set of changes - since the original logic is set up to serve the three different pages from a single function. (I'm only talking about Admin > Media > Settings and its subitems at this point, nothing else yet)

What I'm also thinking of doing is pulling the EXIF data out of being its own page and making it a single item with collapsible selector, much like Admin > Members > Registration and Login > Settings > Notify administrators when a new member joins is - we get to save a page and admins only touch it if they need to. And we then only have a single settings entry that contains everything rather than a separate entry per item - and we can do away with the 'display meta data' item, because if the list of metadata items is empty, they didn't want to show anything.

The other thing about converting it to use the standardised methods is that it can be adapted easily to be searchable as well.

I guess the only real question starts turning into how much work it is to remove wedge_media_settings and fold it into the core settings without breaking anything, whether that's feasible/practical/desirable or not. From an admin point of view, I'd say it would tend to be better if it were done that way.

I haven't ruled out any other changes yet, e.g. breaking up the current Configuration page into several smaller pages, e.g. General Configuration, Files and Folders (for the paths, file types and stuff), Previews.

I'm also not entirely sure about the list of file types. It just seems to me that we could possibly do it better than that, perhaps providing a list of default file types we know about and letting users select/deselect. See attachment.

How could it be a Webkit bug? Seems to me it's something funny related to PHP doing unloading when it shouldn't.

That's the perk of going away and thinking about it, it allows you the luxury of figuring out the 'obvious' points which aren't obvious until you realise them, then they are completely obvious.

So I added the category selectors, plus the everything selector, which is cool. Remaining question still stands regarding member_groups.

r1783 fixed this one.

I was actually thinking about making it moderator's choice, rather than generating potentially a ton of notifications, e.g. If you had a topic with several hundred posts being merged with another similarly sized topic, that's potentially getting into the thousands in terms of setting up messages (email or PM, PM would possibly b lighter in the long run)