Wedge

rev 2245 -- the joys of CSS...
(5 files, 4kb)

! Fixed blog homepage (MessageIndex) when viewed in responsive mode. Fought on this for many days, until I realized a simple instruction would fix it, one I hadn't used in a couple of years I think... Anyway, it's always amusing that specifying for something to be 'fixed' will actually make it 'flexible', but you know how it is... ;) (sections.css)

! IE also needs two extra tweaks for Aeva embed responsiveness. Not Chrome, go figure. Didn't test elsewhere. (media.css)

! Zoomedia popups were incorrectly centered in desktop browsers. That's because window.innerWidth includes the scrollbar, which we don't want. Hopefully, just going for the minimum value between window.innerWidth and win_width should fix it all. (zoomedia.js)

! Fixed sidebar margins in Wuthering. (Wuthering/extra.css)

! Fixed last-minute inheritance bug in Zoomedia. (zoom.css)

* Spacinazi. Well, maybe one day I'll do it the other around and remove all of those extra linebreaks, whatever... Just lemme be misunderstood. (sections.css)

rev 2243 -- woohoo, 2242 got my first Like on the New Revs topic in weeks... :P
(4 files, 5kb)

! Fixed a Firefox bug where the $().offset() setter will take CSS scale() into account, instead of applying the transform on top of the object's default coordinates. It all seems very complicated, but the reality of it is that the Ajax loader was off by a dozen pixels instead of being centered on the requested element. (script.js, index.css)

! Fixed a bug of mine, still in the Ajax loader, where it was, again, off by a few pixels, this time because of internal padding. I never left the loader on long enough to notice, but it was there all the time. (script.js)

! The index CSS wasn't updated to use the can_animate pseudo-constant for keyframe definitions. Also simplified the constant. Well, just a bit. An unneeded part... (Class-CSS.php, index.css)

* Tweaked Ajax loader to get it closer to the Zoomedia spinner, so that I can remove the latter later (latter later?!). Also improved Ajax loader internal alignment on Chrome and Firefox; it's still far from perfect in IE, but I've spent enough time on IE this week... ¬_¬ (common.css, index.css)

* Restoring some documentation and code I committed in rev 2214 by mistake. Well, once again, looks like nobody ever checks my code... Although I have no idea how I came to cherry-pick these. I tend to be very careful these days, and keep my WIP to a minimum. (index.css)

So, I'm back to Zoomedia dev... (Actually, reading my post above, I left a LOT of things hanging while waiting for feedback... Meh.)

In the last rev, I removed the 'duration' setting, because I figured it wasn't something more than a handful of people would change at all. So, the duration was set by CSS, and the same duration was hardcoded into the JS file.
In my local version, I made changes to ensure that anyone can change the CSS duration, and then it will automatically be used in the JS.

However, this change doesn't work on browsers that don't support transitions (IE < 9 or < 10, can't remember, some old Safari versions, and other 'version-locked' older browsers.) So, I've ended up hardcoding it as a fallback (again).
The main problem is that if one changes the CSS animation to execute very slowly, older browsers will cut off the animation before it's finished.

It's all very nice, and really it doesn't matter much, but I wanted to know what you guys prefer...

- As few options as possible; CSS-based durations with fallbacks for older browsers.
- All current options except for duration; CSS-based durations with fallbacks for older browsers.
- All current options, including duration (that's a quick revert for me). Durations would be set through JavaScript, like they used to (of course JS would register a CSS animation with that duration, if CSS transitions are supported.)

I've also got an extra setting around... Dunno if I'm going to 'leave a choice' for this. I've got an extra CSS animation that makes the thumbnail "fly away" towards the center of the screen, with a gravity effect, something like a Star Trek logo would show up in an opening... (I don't even know if any of these shows have that effect :P)
Or, the usual animation -- linear path between the thumbnail and the center of the screen.
Linear = more serious, more professional.
Both animations cost pretty much the same amount of bytes (about 20 more for the non-linear one..?)

rev 2241
(4 files, 3kb)

! Blog bug: post date in message index was taken from the latest comment, rather than the blog post itself. (MessageIndex.php, MessageIndex.template.php)

* A few CSS tweaks... radial gradients don't need to specify 'farthest-corner' as it's the default; most browsers fully support HTML5 these days so I'm not wasting bytes re-defining the new block elements; IE6 has always been bad at handling word-wrap, so I'm attempting to disable it for it. (index.css)

* Parenazi. (sections.css)

rev 2239 -- skin tags.
(5 files, 8kb)

* Rewrote the <css> parser, which was updated by mistake in the last commit (it was a WIP, really). It was tweaked to be closer in spirit to the <code> parser, and allow the inclusion of local CSS files. For instance, <css include="mana"> will load the skins/mana.css file on all your pages, and all its possible satellites. It now also allows multiple files, and does them correctly. Finally, the tag now allows empty content, in case you really only want to add an include. (Subs-Cache.php)

! Renamed <code> to <script>, as it probably makes more sense (I resisted the urge to rename to <js>, dunno why...), and ensured it would also correctly handle multiple includes. (Subs-Cache.php, skin.xml, Wine/skin.xml, Warm/skin.xml, Wuthering/skin.xml)

+ Documented the <template> skin tag in the Warm skin, and updated the rest of the documentation. (Warm/skin.xml)

Forgot to mention... Yes, I suppose a signed CLA would be nice, but I fear we're going to start wondering what to put in the CLA, ah ah... :lol:And early on, we determined that we'd check each other's commits as thoroughly as we could... Whenever I made a mistake, you were there to point it out, for which I believe I was grateful..? Part of not being my own boss was that it took a load off me, and I was grateful that you'd check my commits. In exchange, I always checked yours of course... Except for the few times where you committed some huge changes, such as adding the plugin system. Or when Dragooon added his notification system -- it was a huge thing, but as it was UI stuff as well, I took it upon myself to make it as good as possible. I don't know... It just feels natural, to me, that if I can help, I should. I just didn't know you didn't consider it help but, something like an insult, IIUC..?Course not!
If anything, you *started* so many things. As I explained, I'm really not good at starting them, I'm only good at building upon them.You're so mistaken about that... :-/ You really did your part, and did it great. You did all of the things that I suck at (coding things 'because they need to be done' rather than 'because I want to do them', managing the growing community, doing tech watch on important matters...)
If I'm spending time answering your post, it's not to draw you back into it -- it's to at the very least pay a frigging homage to the work you did on Wedge for the last three years; everything you did shall be remembered, and it just won't be the same anymore. There are some things that will be done in a less adequate way, but it'll just have to be. I'm okay with that. I just wanted to say thanks for all the fish, that's all. And good luck on your game.In my case, it's a bit of a mixed bag... It all depends on what you're talking about with me. I can be annoyingly quiet (usually meaning I'm close to taking my phone from my pocket and playing a game of Scrabble, like I always do in these awkward moments... Yes, I'm the awkward moment all by myself), or if you get met started on pop culture -- movies, TV, anime, obscure music, games, whatever -- you'll just regret you did, because I just can't shut up. I'm a living iMDb, I'm a walking Wikipedia, everything I learn online I need to share it with everybody. Milady learned a long time ago how to just ignore these moments, but her friends, not so much... ;)
I guess I'm quite the same online as I'm IRL, but your mileage may vary.
Anyway, it's unrelated to the point...I really don't know where performance can be gained; first of all, the fact that you claim to have increased performance just after you started work on your private project-- it implies that the changes weren't that many, and yet, I had a look at some of the basic files, and I really don't know how much data you can take out of them, and apart from the notification system which I understand you wanted to load dynamically (and I've never been against the idea), I really don't see what can be improved in that respect, so... I dunno.I'm sorry that you felt that way; I try to listen to what you have to say, but this year perhaps I failed doing a good job at it. I did what I could, but it probably wasn't enough, or even 'my best'.And they'll learn to love it.. ;)80% of the job can be done using regular CSS files; I mean, you can very well include an external CSS file and be happy with using brackets in it. Or you can modify the 'main' files, and in that case you're already in an environment where the Wess syntax is being used, and you just adapt to it. I'll be honest, even I make some mistakes in my code from time to time -- just earlier today, I was yelling at my @if test not working and being included as such (in plain view) in the compiled CSS, when I realized it wasn't a bug in the parser, but rather I simply forgot to add the @endif, which as an instruction contradicts the nested structure of Wess files, but is needed because an @if block can contain un-indented code and thus must be treated separately. There are some hiccups from time to time, but overall I think all of this is for the best...
I could possibly tweak Wess to allow for brackets to be used in addition to the Wess syntax within the same file, but I never felt the urge to do it, really.Since I'll eventually be removing the theme system (as discussed elsewhere-- this is a good example of something I always wanted to do but I was certain you'd be against the idea so I never even took the time to discuss it, so you see, you're not the only one who's afraid of their partner's reaction ;)), this will be a different story altogether.
I'll probably create a couple more skins which, like Warm, will attempt to show how much power the skin system currently holds. Yes, I really think it's possible to do pretty much everything skin-less themes could do.That's a risk I'm willing to take... :^^;:It's easier to listen when you're meeting face-to-face. I always have a problem with online communication... :-/
That's why I was disappointed never having the opportunity to meet you IRL, I guess. Or even communicate over Hangouts or something...I think the reason it worked flawlessly over the first couple of years is that (1) we still thought we had time to release Wedge so we just set aside a lot of the uneasy discussions we might have wanted to have, and (2) we were both involved at the same level, and neither of us had yet to experience a breakdown or anything related. Life happens.And was that a bad thing to do...? Realistically, I mean..?Technically, for those who don't know of the story... My idea of my contributions to Wedge was to integrate into it every single thing I'd developed on SMF for myself, i.e. Aeva Media and Noisen features. AeMe was easy, it was just a mod, but I never really got around to overhauling it, and that's a mistake I made. Noisen was more complicated. I made a huge (800KB..?) patch file of all differences between vanilla SMF and Noisen, and then proceeded to apply all of these features, one by one, to Wedge. It turned out, halfway into it, that many features couldn't be integrated as such, either because the codebase had already become too different, or because the code became unneeded because of internal improvements, or simply because it was a lot to do. The most important thing to me was integrating the privacy system, and I think I did all of it over the years... I mean, it was mainly about adding some code to all MySQL queries involving the topic table, but it was still a bitch. Over the years, I moved away from my desire to adapt Noisen into Wedge, but I still have plans to use Wedge over there, because Wedge rocks, and I'm willing to lose all of the Noisen features I didn't integrate into it, at least for a time.Not everyone. For instance, Milady isn't on Facebook... Not only she's not on it, but she hates the idea of even opening an account over there to keep in touch with her friends. (I've friended everyone in her circle, so that I can at least tell her when something big happens to them, but even then she'd rather call them to get some news...) And yet, she's registered on plenty of forums. Why?

Because Facebook and forums are a different entity altogether. That's what I felt ever since the beginning, and it hasn't changed. In fact, I'm of an even stronger opinion about it, and that's possibly the reason I've become more philosophical about possibly 'stealing' some Facebook features for Wedge. I would never have done that before, because I hated Facebook for being the site that "made what I wanted to do with Noisen" before Noisen did.
I started work on Noisen in 2007 and stopped it around 2009 after Facebook became popular in France. Back when I started Noisen, the place to be was Myspace, and I implemented tons of things to show that Myspace sucked. I wasn't the only one to think that, and I don't own a patent on my ideas, so obviously people at Facebook had the same ideas as I did, but more man-power to apply them, congrats to them for at least making a decent social network that tried to innovate for many years, and managed to do it most of the time.

Back to the topic... My girlfriend is registered on many forums that discuss RL issues that she's interested in, and some people over there use their relative anonymity to discuss matters that they just wouldn't discuss with their friends on Facebook. That is, Facebook is great for keeping in touch with your friends, but it doesn't allow you to be anonymous, and to have any decent, deep discussions, in the comfort of anonymity, or at least not having to wonder whether your friends will check out what 'Facebook page' you're subscribed to, etc.

To me, forums were the natural replacement to mailing lists and newsgroups, and just like e-mail itself, its very nature ensures that it's here to stay, even if it's "out of touch" with the current young generation. Well... I believe they'll come back to it, like many did when they left Facebook for Google+ and then came back or just left to use forums or nothing at all, etc... These things come and go, but what matters is that at least two people in the world are interested in discussing the same topic; thus, a forum has some interest to them, and it's a good thing that this type of software is out there.

Don't you think..?Oh, Pete, I don't know how to tell you... Where did I ever tell you that I was against going the CMS route?
Yes, I'm unsure about the idea of making the forum a plugin. But to me, Wedge is first and foremost a community manager, as in, the two most important tables in the database are _messages and _members. Messages are what a forum is about, while _members is what a community is about, and if there's something I've always hated on blogs and things like that, it's the difficulty of handling a user group, giving them fine-tuned permissions, making them feel they're part of something. It's always about yourself, and then allowing people to comment on what you have to say. Good communities make you feel part of something greater, and yet allow you much leeway to express yourself in a more private fashion, such as creating your own blog and giving it its own style.

All I wanted to say is: yes, I can see Wedge going to CMS route. But I've always postponed the idea of doing something big about that, because, FFS, we're three years into development, we have a product that rocks your socks off, and yes it's not 'perfect' yet, but postponing its release by a couple of years to make it supposedly more 'relevant' to the current day is not a good idea in my opinion, which is why I wanted to do it for Wedge 2.0, i.e. when our brand would be more established, and we'd have had time to determine whether it was something that other people wanted as much as we did.Yet, even with a personal fork, I wouldn't have considered removing themes, because that would have made the fork too distant from yours; precisely for that reason. I just thought it might give you more freedom, and yes, I was thinking more about your freedom than yours, because deep inside I did feel that you were frustrated about a few things, and I figured that what I'd devised during your US trip could be an interesting direction to get the both of us to be happy about work again, but unfortunately the idea was not in the air long enough to take its grip inside of us, so it didn't help you change your mind about the whole thing. Bah. Maybe it would have failed, too, anyway...I think it's all okay. I made the original thought thread member-only because it wasn't a pretty thing to see, but apart from that, everything else can be public IMHO, because we've always wanted to be open about these things. And I think that all of our users, Friends or not, care about the future of the project, especially in situations like these...And again, it was never about finding the flaws in your code to piss you off, it was mostly about adding a bit of me to code that I was always ecstatic about, and I told you about that many times... I felt that if I could contribute to it, then it would be a good day's job, and there's nothing else to find in my actions...Unrelated, but I've never heard of that ever happening... I just checked out Wikipedia, and it doesn't mention either; it only says that Gauguin loved the paintings, had two already, and was met with a refusal when he asked for a third copy.Well, if you want to talk about art...
- Novels, paintings, some music... These are individual art forms. Just like a tennis player usually doesn't have to worry about anyone else, these things represent someone's inner feelings best.
- Movies and other art forms that cost a lot of money will be a team work. The director always has to make compromises with the producers, executive producers, the writer, the director of photography, whoever has any kind of standing in the making process. They have full control over their gophers, PAs, whatever you could think of... (Usually actors, too, unless they're very popular, blah blah...) They make most of the decisions, but sometimes the producer(s) will override them. Sometimes, it becomes a battle of wits, sometimes a battle of popularity. When Ridley Scott released his own DC of Blade Runner, I absolutely adored it -- yet, I also love that the producer's cut exists, with the Deckard monolog and the Shining unused footage in the mountains at the end... Who made the best decision? I don't know, I can understand both... Ridley Scott made art that was meant to make you think; the producer made art that was meant to be enjoyable, without any further feelings.

Wedge is the kind of art that takes years to shape, and thus requires team work. So, I think it's safe to say that the movie example is better in our situation, and a painting is irrelevant...$
And I do, too... Many times I've admitted I was unsure about a commit I was making. I was fine with it, though... Sometimes, you just can't do better than your best, and it'll still be better than not having anything at all.Or maybe simply that it's easier to work alone sometimes, don't you think..?I'd have a good story to tell you about working with people who don't code... While I did have a pretty fine collaboration with a friend of mine, Miguel Samiez (who went on to become a full-fledged musician), to provide music for my game, and with KMJ fans who provided tilesets and other interesting assets, the only time I had a clash with a collaborator was when I was starting work on a new game -- I decided to contact someone whose art I loved, and commission graphics for the game. I was satisfied with the outcome, but said that, for the price I said, I should at the very least be sent the original pictures (they were just scanned and mailed to me), which I thought we'd agreed upon. Otherwise, it wasn't exactly a fair price he made me pay. He refused to do so, and I stopped collaborating with him, and decided not to use his pictures, even though I'd paid for them. That's how upset I was. In the end, I completely dropped the project because of that, and subsequently, retired from the gaming world altogether. Nowadays, I tend to think that things had simply run their course, and I was looking for a way out. That guy wasn't very nice to begin with, at least not very professional, but it was partly an excuse for me to call it quits.
Perhaps, just perhaps, the same thing happened with you with Wedge. And maybe, in the future, you'll end up doing the same again over another petty issue that you'll see as a grave matter, because in the spur of the moment, anything would hurt, and it's just best to leave things behind, maybe to come back to them later, if needed.I get it... And I'm okay that you're leaving. Simply, I don't think you're leaving for the right reason.

Hmm, yeah, but you also lose the ability to get the button strip etc...

Of course, I could add that as a floating tooltip, like some Wysiwyg editor I don't remember -- ah yes I do, it's Aloha Editor.
Still, contenteditable stuff can be nightmarish... I remember trying something out in Wedge long ago, and failing completely, mostly because of browser compatibility. It's not that it can't be done... It's that it would take too much of my valuable time, and I'd rather spend it on more important items in my to-do list, such as "Release Wedge, bitch!"

What I'm considering, right now, is to 'simply' retrieve the current window top, and if it's part of the current post being edited, then open the textarea there, so that it expands to whatever space you currently have, without forcing you to scroll back to the beginning of the post.