Wedge

John, any progress on this one? Just curious.

Oh, Pete, I'm not expecting a reply from you, but I was wondering about one thing... Since you're the MySQL guy here. You kept telling me that the approved flag on posts should be left unused because of its bad specificity, the fact that it kills performance to search for flags set to 1, or something, when most are.
What if instead we search for id_msg NOT IN (SELECT id_msg FROM wedge_unapproved_posts), or equivalent? I think there's such a table in the database... Haven't studied it, dunno what it does, but I suppose it holds a list of all unapproved posts, and if it doesn't, I can easily create a new one and fill it as needed. With just that -- a list of items that are unapproved and should be ignored.

I had another question about your repo, but I forgot, ahah...grepWin has a nice UI. I used to use another software, written in Delphi something like 10 years ago, until I discovered grepWin. It didn't do replacements, so I then had to use another software to do these, but OTOH it had a nice feature that grepWin doesn't have, it actually showed hits 'in context' with a click, rather than just a single line in a long list of hits. The only way to do that in grepWin is to actually double-click the entry, and then re-enter the search in Notepad2.

Also, Notepad++ may be popular (and I use it for many files), but I've never liked its search tool, it requires too many clicks anyway.To whose profit..?That's a bit unfair. Go tell that to the web design community. Most of them are very techy, and still consider WP as a proper CMS tool, so... I dunno. I guess it's just a matter of what you think a CMS is, eh..?I fit SMF's coding standards better than anyone in their team... I'm the ayatollah of SMF coding guidelines. Well, maybe I don't follow all of their documented guidelines, but I'm so used to the SMF codebase, I tend to stick to its choices, and I actually like them.
As opposed to WP's, for instance... (As we say in French -- beurk !!)

Yeah, probably.
http://www.apache.org/licenses/icla.txt
"You accept and agree to the following terms and conditions for Your
present and future Contributions submitted to the Foundation."
Well, 'present' probably implies 'past', since one is unlikely to be contributing something right at the instant of signing the CLA, but...

So... You're welcome to do it, then ;)Okay, I could just as well add language files support to the skin folder... It's not very important, really. This is the kind of thing that can be improved as I go.Hmm, because we went out of beta in the last three years...? I mean, you're the one who said last month to someone that Wedge wasn't gonna be out any soon, right..? I didn't see why you were being so obtuse about that. I keep saying we should go beta... But, whatever.It looks much better now. It's impressive. It's what I do.
I'm not doing any more money than you off this, and thankfully, I still get to choose what I work on...Probably not. But I didn't follow these reports. Will fix as I go.Yes, by selecting (with my upcoming action/area selector, as discussed yesterday) areas where you don't want the sidebar (e.g. the forum), and giving it an empty sidebar macro. Problem solved.That's up to me to decide.
I think I'll give it a couple of months to recover from my RL blows, and from your leaving as well. Then I'll get serious about feature freeze. Going for late '13 or early '14 is still gonna be earlier than your prediction. Just be patient. In a few months time, you'll either have forgotten about Wedge entirely, or you'll be back to complain that I didn't release.Good to know..?Sure, Twig is something cool that doesn't require re-learning something for people who know PHP, and doesn't take away any flexibility, and doesn't require a server installation, i.e. something that can't be done on shared hosting or by people who don't know anything about server management... The very people you're targeting (unlike me). Anyway... It's really, really not worth fighting about. People will be free to try Wedge out. If they find it's slower than your solution, they'll use yours (or another). No problem.
You're a server performance freak, I'm a client performance freak. Told you-- we've always been complementary, haven't we..? I'm all about saving bandwidth, you're all about saving CPU cycles. These two can sometimes be compatible, but not always. Not these days, apparently...Because not everyone knows about grepWin or other mass s&r tools, not everyone wants to deal with these..?The problem has always been very simple to spell out, actually: I thought of you as an innovator who knows better than anyone else, and was always afraid to commit sub-par stuff that you would criticize for being poorly thought out, because of this or that obscure setting in PHP or MySQL that makes the whole thing 12% slower than if I'd done it this way. And you thought of me as someone who judges your commits, too, and silently requires you not to commit sub-par stuff.
So, basically, we were afraid of each other. Nice.
No wonder we both stuck to our known strengths... :PWell, I don't do that. I could discuss code, but I wouldn't code with someone else. I like being alone to code. Add bugs, test, find bugs, fix bugs. That's a very private thing. I can discuss these things, but it's awkward to do them in front of someone...'kay.Haven't heard about that.'kay, sure, we'll see.Doesn't mean they HAVE to use a CMS in the first place, just means they need to find the right angle first.'kay.You seem to despise them... And yet, they're the people you want to help by adding new easier features.Sounds like someone's gonna make some money in exchange for their help...Ignorance is bliss. If you can afford a technician, of course.If you say so.I don't argue in terms of who's right and who's wrong. Understanding is a three-edged sword.
Especially in the case of 'predictions', where, really, which of us is gonna give a damn about forum software and CMS in ten years..? I hope none of us.Well, then it's simply a feature that plugin authors won't be able to use, unless live627 (or you) steps up and offers to fix it.I still don't see why you didn't ask me for permission to fork Wedge. Pride, something like that..? Or simply the fact that because you left me in that shit, you don't see any reason why I should be nice to you? (I'm not sure I do neither, but it's not the point! :P)Never, never, NEVER had any expectations on your commits. The only expectations I had was that you kept working on Wedge until it was out. Really, that was an expectation of mine, and really, that was the only one. The rest was all in your head.Well, anyway, can you remove it or not..?A personal failure, yes. Like many others. I prefer not to dwell too much on the past, though.Well, I did talk with Bryan (who recently resigned) about using Wedge as a basis for SMF 3.0, but apparently the idea is a long way from making any sense, especially considering that it comes with a recommendation that SMF can only survive if the dev lead is also the project lead, so... Not realistic enough, I guess.Good fun.You should work on that.My terms are not very demanding; I still have a few people who are ready to help. I don't think I'm being unfair when saying that I'm now going to make all decisions, because that's precisely what I've been about in the project: the more stable developer. Perhaps not the 'best equipped' developer to handle an entire SMF fork by themselves, but still devoted to their task. (e.g. I'm not sure why I'm typing this long reply when I could be downstairs watching the latest 'Whitechapel' with Milady...)'kay.
Where does that name come from..?Good one.Good, at least someone is happy with the outcome, eh..?I dunno, it looks to me like you're trying to defend your choice of generalizing autoloaders, rewriting scheduled tasks, things like that. I'm not complaining. I'm always interested in you sharing your technical knowledge. And yes, I call that 'contributing to Wedge'. It doesn't always have to be about pure code.

PS: I was hoping to make my reply much shorter... Still, I'm getting closer to a manageable size. I dunno if I can keep it up much longer, though.

rev 2248 -- plenty of nice little things. C'mon, like this one! :P
(10 files, 6kb)

+ The 'zoom' link on Zoomedia popups now behaves like a double-click on the image itself, i.e. it opens it on the same page. (zoomedia.js)

+ IE6 will now properly support all min-height rules in CSS files. It's actually very helpful, from what I can see. (Class-CSS.php)

* I've finally found the 'correct' way to properly align background-integrated icons with the text they're shown next to (as long as said text is not too small.) I don't see myself doing it on every single icon though, but I'll at least give it a try for feed icons. (Boards.template.php, Media.template.php, Memberlist.template.php, attic/Custom.template.php, sections.css, Wine/extra.css)

* Added flexbox layout to media item pages. Although it looks better than before ('on supporting browsers'), I'm starting to think that this layout is getting old, and should be replaced with something simpler, with just some floated elements. (Media.template.php, media.css)

Guess I'll have to reply this, at some point...Sure, why not. But as the Apache CLA only applies to future contributions, I suppose you'll have to pre-date it..?But my standards are mine, and only apply to myself. What you should say is, you can't live with the idea that I'm modifying your code. Except that sometimes I have to (oversights, bugs...), and other times... Well, it's just cosmetic. What should you be proud of? How you indent your code, or how it does something awesome or innovative..?Hmm, not really..?
Although I have yet to figure this one out, I had in mind something really, really simple...
/wedge/
/wedge/sources/
/wedge/skins/my_skin/
/wedge/languages/my_skin/
You just upload multiple folders to your site.
The skins folder contains your CSS and PHP stuff, and in your PHP code, you can simply declare a loadLanguage()...
It may not be super-practical, but it's no more unusable than the SMF way, I'd say.
And, knowing myself-- I'll probably even add a setting allowing for skins to load some language files automatically on every page. I already have a <language> setting IIRC (determining what languages the skin accounts for in the CSS files), so I'll just have to add a new one like <loadLanguage>, or something. As long as it's in beta, I can still change that kind of thing, and update all skin files manually...If it's absolutely needed, then they'll tell me what I should change into a macro.
If it's not, then it's unlikely they'll simply update all template files for the sake of updating all template files.Can't see why not..?And here, I can't see what JS is needed exactly to make it work. I don't see any JS at hand here...
And even then-- <script include="mycustomskin">, and you're done... (??)
If someone needs an object method to be rewritable, I can declare it outside the scope, so that it can be redefined/overloaded/prototyped.Macros
Custom JS
Custom PHP
Custom CSS
Final HTML raw replacement
Dunno what can be done with themes, that skins could not do.
Of course, it's another way of handling things. And it needs documenting. That's where skins are weak. There's a basic documentation in Warm/skin.xml (the only thing I actually really worked on documenting, unlike Wess!), but it could be better, I suppose. I'll improve it as questions come and go.I needed your expertise on many domains that I'm very weak at (database, security, UI, JS, and so on -- and yes, I got a bit better at UI, and I quickly realized I wasn't as bad at JS as I feared), and quite simply, I needed your enthusiasm. Two people is better than one. Oh, just a simple example... These days, Milady and I try to jog at least once a week, sometimes twice a week. We started slow with 12mn rounds, and now we're at 30mn rounds. We're still bad at this, but we're still doing it, because what matters is that we try. Milady told me today, after our jogging session, that she enjoyed running with me, because she did 45mn sessions many years ago, and stopped after a year because she was fucking bored. I told her, "you need me because you feel better when you're so tired and you see that I'm in an even worse shape; and you need me because you want to encourage me to keep you with you when you're feeling better." She agreed with that entirely. Sometimes, being two just means that when someone is not at their best, they can count on someone else to fill up their job, and when they're at their best, they're happy that someone is encouraging them.Sure. Removing themes would be a bold move, one in the likes of your own past bold moves, so I guess it's like the name change-- a way to make it clear it's "mine" from now on. However, all I want, at this point, is to finish the dozen or so features I want to finish (better privacy settings, better UI for blogs, etc.), and then release it to the world. I think that's what's going to make it clear that it's mine: I've always been willing to release it, because I am confident people will love it, as flawed as it is. ;)

Anyway!Ah, well, I tend to reply as I'm reading. I didn't read this post until now (I did read your previous long post entirely before replying, but that's more an exception), because I will usually be discouraged to reply after I've read. "Too many things to say, will take me hours to reply..."
So, I guess my posts tend to be seen as hot-headed, more spontaneous, unlike yours. Figures.Okay, so, the censor code... It's less than 5KB, including all of the fancy scramble stuff. Or just 1.2KB for the core function. I don't see autoloading it as being very helpful for performance...? Heck, at worst I could simply have it in a Subs-Censor.php file, and loadSource it from within Subs-BBC if needed...But it certainly doesn't make a project more manageable... Functions should be categorized by themes, not by size. I'd rather maintain a 100KB file for some Aeva feature, than have to deal with ten 10KB files with the same code, because every time I want to make a more global change, I have to search all of these files for relevant code, when in a single file, I can just do a quick search... Things like that.
Look, the best example is skin CSS... Originally, I only had suffixes. Got plenty of files for each browser or action or whatever. Then I added @if support. Suddenly I removed most of those extra files, because it was much easier to maintain similarly themed CSS in the same file, rather than in multiple index.ie6.css-whatever files. Made my life easier...We both have blame to share.Better than waiting until 2015 or 2016 for a release you'd finally deem suitable.
Having a release out means that we can start considering things like whether to keep maintaining it. If it's a success (generating buzz, even negative buzz), then great. If it's a failure, then we stop, simple as that.

Okay, this post is so long, I'm gonna have to finish it another day, because... Because! I'm really tired.
Dunno. I guess I can be convinced to switch to an all-bracket version of Wess by default (in index files etc), if people feel better about not having to deal with indentation, but I think it'd be a loss. One of the main advantages, though, would be the fact that Notepad2 would be better at providing syntax highlighting for it... :PWell, for now it's not removed; but I just have one thing to add: in the three years we worked on Wedge, none of us ever tried to make a non-default theme, even just to 'see' if it would work... I made so many changes to the internals, I'm not sure it'd work at all; it might be fixable and everything, but because my focus has been on making sure anyone can make a very minimal pseudo-theme (a skin) with just color changes or whatever with only a text editor and a FTP client (no admin manipulation, no database handling or anything), I'm hoping that once they get the feel of it, they'll want to add more features, which they can do while remaining in the same environment, as opposed to having to go through theme handling, which is more complicated, and more importantly, forces you to update your templates as Wedge or SMF is being updated.
(If the theme system is removed, I'll probably be even more aggressive in splitting important templates into more functions and macros.)I don't have the feeling that Louis had a problem with that, since he invited you for a long road trip together, one year after meeting you...And as a French speaking English like a Spanish cow (French expression :P), you don't think I would trip up on words as much as you do..? :PMe neither, but I was willing to be for you...Well, it never was about Wedge anyway. It was about putting a real person in front of the online contact whom I've been talking to for all these years. What did SMF call that..? A meeting of the minds...

Anyway, I might be coming back to London within the next few months; nothing set in stone, but my girlfriend discussed the possibility of staying at her brother's over there, as he's expecting a new kid soon.It's not about the number of users (you realize we'd have been thrilled to even have 1% of SMF's current user base, don't you..?), it's about filling a void, and making life better for at least one person. A success story, if you will, case by case, one at a time. I may have sold thousands of copies of my game, but what really pushed me to continue working on it at the time was these little stories where people were telling me they were successfully using KMJ as a tool for their physiotherapy. It happened several times, I have no idea why. I even once had an hospital ask me for a group order of copies for their reeducation unit; I told them they didn't have to buy them, of course.
That was a factor for me, more than the salary that came out of it.Absolutely... And it's also much easier to set up than a forum, but once your community outgrows the facilities offered by Facebook, it happens from time to time that you'll want to go serious with it. In fact, to me, Facebook didn't replace forums... It simply replaced mailing lists (partly), and free hosted forums that sucked so much. You know, these slow websites that were filled with spam and messages from people asking 'when are you going to use a real forum anyway...?', things like that.Absolutely, that's one of the important points. There are some forums where I'm registered, where I wouldn't want to tell people my real name.
Not that you CAN'T hide your identity on FB. One of my best friends has 'Yeo Wren' as his FB account, and that's actually his nickname. He never gave away his real name on FB, even though he's very active on it, and all of his RL friends are linked to his account. It's not that he's hiding his name... He just doesn't like revealing himself to anyone he doesn't know.
That's why I still have in my to-do list this item that says, lemme find it, "per-item privacy in profiles, e.g. real name". That means applying the usual privacy flag (contacts, members...) to individual entries in your profile area. For instance, you could put your real name in it, but only have it available for your conatcts. Or your e-mail address, etc.Oh, that... Pete, I've always, always been against board index as the homepage for a forum. You'll remember I did rewrite the homepage early in the Wedge timespan, and even allowed for the ability to push a blog homepage as the main homepage of the forum. That is, to me, it's ALREADY a CMS per-se, although it's not really advertised as such.
(Possibly because I don't think saying "CMS" is gonna help make Wedge popular. If you'll look at cmsmatrix.org, they have over 1200 CMS systems listed... And they're almost all dead. To most people, CMS = what?! (and to them, WordPress is just a blog platform, only web developers/designers would really think of calling it a CMS); to a minority of them, CMS = WordPress (.net and Web Designer Magazine readerships :lol:); and to some of them, CMS = Drupal/Joomla/ExpressionEngine/SilverStripe/whatever CMS had a relative amount of popularity at one point or another. Doing a great CMS won't really help, as there are so many CMSes around already. What is going to help, though, is getting at least ONE great/popular website to use Wedge, and then popularize it by actually keeping using it. Again: one by one...I didn't even know what PRISM was... I googled it, and was surprised by the amount of detail... So, that's what the Snowden story was about, uh..? Interesting. The media in France, I don't remember them talking about that at all... They only covered Snowden's escape, and I followed that a bit because it reminded of that amusing movie I saw a few months ago, Terminal.Again and again: to me, it's a CMS all right, but CMS meaning "community management system", not "content management system". SMF, to me, like other good forum systems, excel in making users feel that they can set up a real identity on a website, and manage everything from one place. Call it a social network or whatever you like, but to me, it's just what the Web is about... Tim Berners-Lee himself said that the Web had always been about connecting people. Facebook didn't invent it, SMF didn't invent it.You can very much work on hiding forum contents from a website, for sure, and still have the forum power your user management.
Well, if anything, there are already plenty SMF forums that do exactly that. It's not new -- it's just not really advertised, is all.
Bloc is focused on doing that with Protendo, too. Noisen.com has done that from day one, of course -- I'm not really hiding the forum, but if you tell someone your blog's address, they don't really have a reason to go outside of it, so...What I was against, as I remember it (and I'm old, so my memory is fuzzy), was that you suggested stripping the forum entirely from the software, and adding it back as a plugin of sorts. The idea was already floating in the air for SMF 3.0, and I hated that. I hated the idea that a CMS would have to be ashamed of its origins so much, when it should be proud that it skyrocketed in popularity, even if it typecast(ed?) it a bit.Just look at noisen.com, it's come naturally really... Most of the users are just forum users. Most of the most active users have their own blog, where they can do whatever the fuck they want, without my intervention. A few less active users have a blog, but they usually drop it after a few months of inactivity; whether it's because they're intimidated by user comments or simply because they're not really talkative or just wanted to 'try out' the platform, I don't know, and I don't care... I just provide the tools, and I'm happy that a few people (including me up to 2010) are or have been using it. Even a dead blog is something to be proud of; I know that everytime I go back to nao.noisen.com, I have this 'wow!' factor when it comes to the contents of it, same can be said of cynagames.com though, KMJ is not dead, it's still played by hundreds of thousands in the world, that's just the way it is. It will possibly even outlast me, as a retro game of sorts... :lol:And that's just great for them. That still makes it a forum... They just don't use the messages table as much as their equivalent thoughts table, I'd say... ;)It will be fixed over time.It will be fixed over time.I understand that you woudn't like it. Heck, I'd be lying if I said I liked it. But the reality isn't that. The reality is, there are dozen of people who would be thrilled to use Wedge right now, and adopt it, even if it's not ready yet.I'm pretty sure I'd have been the 'weaker one' in that relationship, i.e. adopting more of your changes than you'd adopt mine, because I'd really, really strive to keep repos in sync as much as possible, and globally, even though I may have sent 'mixed signals' myself, I'm really happy with most of the changes you made. Even if they destabilize me, overall I know that they're for the better, and they're good for Wedge, for its future popularity. Software reviewers are gonna like the visuals, but they'll be absolutely thrilled by the admin area, I think.Well, I wouldn't see any of us as doing that merge; maybe by someone else if both of our projects had collapsed, but that may simply have been seen as a 'fork from multiple sources', I don't know...
The idea was simply to find a solution to the issue where we were drifting apart, and to allow you to focus on your other software projects, while giving me free reign to make decisions when you wouldn't be available for advice, that's pretty much it...I can't help you here, I'm afraid...Hmm, I don't think I caught that one... :^^;:Neither of us are really team material; we're most likely 'alpha devs', meaning we should both be lead dev, which is why we shared that credit, and it worked... For many years; and to me, that's already quite a feat. FWIW.Nope...Have you ever seen how many times I rewrote so many parts of my code...? Just this week-- Zoomedia. I not only added hardware acceleration (which was way harder than I expected, because the real bottleneck in performance was not due to the software resizing, but rather to the constant layout reflow inside the popup, even if it just had a single image in it...), but I had to rewrite many things to make it work again, because it had become an unmovable stone, perfected to death over the months. It was as short as you could hope for, and yet I left this feat aside and decided to give priority to making it work. As a result, my final big commit didn't even mention the large increase in size -- something in the likes of 300+ bytes, rather it focused on the fact that it worked better, ah ah...
Maybe it was a homage to you, I don't know... :PTo me, committing has a special feeling: it's like I can leave that part of me aside, and focus on new things. As long as I don't commit, I have tons of ugly, dirty code lying around, and sometimes it just feels great to just revert that code, instead of keeping work on it, because some pieces of code need time to prove their worth, and when they don't, I just tell them good bye.Went to see it, and indeed, there it was in all its glory... Because it's available for anyone to download, yes it's public knowledge. Not popular knowledge, but it's there. There's a mod out there at sm.org that publicly accuses me of wrongdoings.
I'm above that, but... Well, I prefer when people who have something serious to tell you, do it in front of me, rather than vent on the side.
If you already had a problem with me back in April, then you should have told me, because there's no reason I wouldn't have worked on this on my side, or at least talked you into understanding what I'm doing has never been against you, rather I was just trying to contribute.Anyone would have a breakdown over such a comprehensive rewrite, really...!
Why do you think I never took it upon myself to do a complete overhaul of AeMe... :PWell... I know it won't do me any favours as I've been doing my best to stay as neutral as possible in this, and to be understanding of your position and the difficulties you experienced in the last three years; but to be brutally honest Pete, yet, a part of me also screams 'man up!', and considers you a bit of a drama queen. We got together because we were both branded drama queens by the SMF team after all, and they weren't completely wrong. I've just learnt to be more philosophical about these things in the last year or so. I haven't been in a flame war for something like two years. The trick is losing interest. Looking back, I think it was a drug, coming as much from a sense of disbelief at the injustices around me (for some reason, any injustice around *me* seemed to be even worse), as a simple need for attention. As hard as it is to admit it, I did many things out of a need for attention, because of low self-esteem and a need to prove myself that I was a worthy guy, not by self-confidence, but by looking back and thinking, "okay, I made a few nice things". I'm sure today's youth are the same.

But then I just slowly drifted into the world of the adults (mostly due to real life) -- where nothing ever happens because you fear you have more to lose than to earn. I just played the Passion game with myself for so long... I can still be angry at injustice, but the difference is that now I realize I can't do much about these. Last time I saw one, I started a fork. Look where I am, three years later... The only thing that remains of the initial spark is the passion for building something so incredible. The anger, itself, is completely dead. Not that I love the SMF team or anything-- I just don't feel anything when I think of these stories, I see these things as childish. Childish that I played into the game of joining the SMF dev team, and especially childish that they themselves played with me and were frightened of losing control over me. Seriously-- this is free software we're talking about. Nobody should ever give a shit about having 'power' over something. What matters is what they bring to the project, not the aura they get out of it. Being happy with what you did in the past, is better for your karma than some irrational idea of being important. So, yes, everyone was being childish at that point, and I should have seen that. It wouldn't even have stopped me from starting Wedge, actually. Just... In a different state of mind, I guess.

Oh well, I'm seriously drifting off-topic. Sorry, I was typing as I thought it up.I just think, you should embrace our differences. I can accept that you'd leave the project over not being able to accept my quirks, such as these compulsive modifications on your code. But I don't think you should feel betrayed by me, or anything. You should accept that I'm different. I accept that you're different, and I accept that it doesn't work for you, in the end. Just don't turn this into drama. Nobody died here. The worst that happened, is that some things you wrote very passionately are going to be left aside for the time being, maybe forever, but you can always come back and keep contributing to it. It's your decision, in the end, whether you contribute or not. I decided I'd get the 'final cut' on the software because most successful project have a single decision-taking leader, but that doesn't mean I don't acknowledge how crucial you've been to the project, and its future success. And it's going to stay that way-- anyone, especially me, would be outraged to see your name removed from the Wedge credits, even 10 years after your last contribution. I learned a lot in your company (I also missed out on a lot of opportunities to learn more from you, but... I'm just not up to the task). You've shaped Wedge in your own way, and that's good. Well, what can I add to that..? Not much. My post is already so long, and I can't expect anyone to read it entirely. If anything, I'm hoping you don't reply more than one-liners to it... :^^;:I see you're also trying to contribute to Elk, at least trying to convince them to adopt some of your Wedge changes. I just have to say-- make up your mind already! :P

PS: I wanted to use the word "short of...", but I couldn't find any place. Any suggestions where I could have put it, short of here..? Oh, good, I managed to use it, yay!

Nope, it's quite hard to show threads in a 'latest first' context. My solution to this was to have two ways to show them: linear (homepage, thoughts page, and profile thoughts), and threaded (thought context, only accessible from a thought's context menu.)

I must have been drunk when I notified you of a problem with your thought, really... ;)

:edit: Nope, not drunk... This is due to the 'highlighter' (green background) feature of the context page. I simply noticed that the '+' icon was indented below the previous thought, while in fact it was at the same level, but the highlight effect added some extra padding on the left. Dunno if it's worth fixing, though...

Ah, yes, I always forget to fix that one...! It's been in there since the first version of Zoomedia, you know... ;)
Fixed locally, will be in my next commit.

Any have any opinions on the settings stuff..?

And what about the current animation? It's the funky one. Is it perfect, or too funky? (Nope, I can't have a "less funky" version... It would force me to add animations, and I'm not going into these for now. It's either linear, like it used to be, or funky like now.)

A random pic for a quick test...: