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 - Nao
2506
Development blog / Re: The zombie strikes back
« on September 18th, 2013, 12:22 PM »
Hmm... Good idea. Dunno if I can do it, though! A long time ago, I wanted to do that-- floating topics, that's a topic somewhere in the Features board. I never got around to making it...
I can, however, postpone that to Wedge 1.1 or something, without any particular issues. I mean, it won't require any big rewrites that will break everything horribly.
I can, however, postpone that to Wedge 1.1 or something, without any particular issues. I mean, it won't require any big rewrites that will break everything horribly.
2507
Development blog / The zombie strikes back
« on September 18th, 2013, 11:10 AM »
So... It's been over a year since the last blog post, and a few weeks since we celebrated the 3rd anniversary of the creation of this little project called Wedge, that took the life of two promising web developers and turned them into lifeless zombies with a crave for blood. Oh, maybe I meant vampires.
For those of you who didn't follow the latest developments on the forum, I'm sad to announce that one of the zombies is now officially resting in peace, carrying his own head, basking in the glory of his past achievements. Said zombie we called Arantor, and in pure retirony style, he decided to call it quits a couple of days before the anniversary. And I'd planned to show up at his door on that day and give him cookies! Well, no cookies then. Blame that good old UK craze about cookies.
And here we are. It's lonely at the top, but at least it means I get to make some hard decisions that we always postponed because we weren't sure about them. Same for Pete on his side, I'm guessing, albeit with other projects. I'm hoping we'll still see him pop up from time to time, and share his disbelief about how badly I handled the project. I always appreciate constructive criticism, after all.
Now, here's the point I wanted to address. There you go, Pete's state of mind up to this point was that we had no plans to release Wedge in the near future, that we didn't even have a tentative release date, and that it was even unlikely to ever happen. I understand his position, I'm not going to put the blame on anything; fact is, yes we slowly drifted apart as collaborators in the last couple of years, mostly because of real life issues for each of us, and because the weight of the project started to get very heavy year after year. The longer you wait until release, the more pressure you put on yourself to make it worthy of the wait.
And this is my first decision.
I'm putting Wedge on the road it should never have left: the road to release. Not the road to completion, which is a different thing altogether. With such a huge project, one man alone just can't complete the project. At most, he can do 80% of it, but he has to rely on other people to do the rest, simply because there are always some tasks where you know that other people will do a better job; that's what kept Pete and I together for so long, and I was hoping it would remain that way, because we really were complementary on most points. Working alone is not easy. Some days, you just want to say "screw Wedge!", and watch a movie or a TV show for hours. And you know what? I'll do just that. I've seen tons of silly and better movies, and I'm still going back to Wedge every day, because if there's something I'll never, ever give up before it's out for the public to enjoy, it's Wedge. Even if it doesn't bring me a dime, I need to finish it.
So, what's the tentative release date? Nope, sorry... There still isn't any. And before you ask why -- ask yourself whether you prefer to be given a wrong release date, or be told exactly what remains to be done to have a releasable product. To the former, I'll just say this: I'm hoping to release a public beta before the end of the year, and a final 1.0 in early 2014. Do what you want with that silly date, and if you're in too much of a hurry, and you consider yourself to be a hardened, hardboiled, hardcore, hard-wired forum administrator with a taste for trouble and a love for HTML/JS/CSS/PHP/FTP tweaks, you can always contact me with a request for private beta access and a copy of the SMF importer code.
To the latter, I'll be more thorough. First, I'll try to list a few of the things I wanted to do since day one, and will probably not do in the first release... Aeva Media is a monster to handle, it used to be my full-time (unpaid) job. I wanted to redo so many parts of it. Most importantly, I wanted to replacement attachments with media items; I'm still planning to do it, but if it's not done when everything else is ready, I'll still release. Also, Noisen.com features... I wrote many features for my personal website around 2007-2008, and was adamant I'd include them. Pete persuaded me otherwise, for very good reasons mainly, but now that he's gone, I can decide, if I want, to fail in a spectacular fasion. Go get the pop-corn. Again: if it's not ready when the rest is, I'll still release.
And now, for the features that I can't see myself release without.
- Privacy (estimated amount of work: a few weeks) : there are already some privacy features in; thoughts have privacy. Topics have some sort of privacy. I'm hoping I can do board privacy, à la Noisen, and profile privacy, à la Facebook. And fix an annoying bug in the 'Contacts' option: if you post a thought for your contact list, and someone replies to it, and you're not in their contact list, then you won't be able to view their reply. To be honest, I've thought of several solutions for that, but it's hardly anything solid, or at least efficient.
- Contact lists (a few weeks): so far, Wedge has been using SMF buddy lists, while Noisen has been using a customized version of Ultimate Profile (a nice little SMF mod from back in the day), where I allowed you to 'hide' a contact from view, and nice little things like that. Contact lists are my biggest project right now, I've already started work on them, but still need to write the UI, and some other things, to make them usable. The idea is that you can categorize your friends into multiple lists, choose the list name, and even determine the visibility of said list to profile viewers; you should be able to add people to multiple lists, and target a thought/topic privacy to a specific list. (Not multiple lists -- it's already complicated as it is, UI-wise.) My biggest issue right now, is handling the aftermath of adding someone to a list. Should they be notified of it? Should a list have a setting to determine if notifications should be issued? Et cetera, et cetera...
- Skins (a few weeks?): there are two things here.
(1) I'm not sure whether I should enforce sub-skins to be put inside a parent skin's folder (which I always found to be a natural thing to do), or simply require them to specify the name of their parent (author:skin_name) in a skin option. The latter option would allow skins to have folders for images, templates, etc. without the need for a different folder naming scheme, such as adding an underscore (_) before the name of any folder that isn't a sub-skin.
(2) As I discussed recently in the Friends board, I'm very, very tempted to remove themes from Wedge entirely. Just like Pete removed SMF packages when he finished his implementation of plugins, I'm in a similar situation where my skin system can do 99% of what templates can do, and it's just tempting to say, "themers have to re-learn mostly everything anyway, so I might as well get rid of that relic." Recently, I implemented one of the last things missing from skin features -- the ability to override/before/after a template function from within a skin.xml file. It was already possible to override a function through the use of a Custom.template.php file inside the skin, but it's not a rock solid solution because of the possibility of conflicting function names, and I only added this as a way for themers to 'test' their replacement code in a comfortable PHP editing environment, before they simply move their functions to an XML editing environment, without the proper syntax highlighting.
- AeMe comments (a week?): I'm planning to remove them entirely, and replace them with regular board topics. The idea is to create a generic board (hidden or not), where topics are created on the fly when posting a comment to an album or a media item. The advantage is that you get to comment on whole albums as well, and that you can search inside media item comments. The drawback is that I'm not planning to write an import tool for existing comments. They'll either have to go, or Thorsten (@TE) will have to account for them in his fantastic OpenImporter tool. Oh yes, and another drawback-- I'll have to handle attempts to access a media comment topic directly, by redirecting to said media item (or album). I don't know how I can do it efficiently, though.
- Others (weeks? months?): There are, I'm afraid, many other things that I'll attempt to fix before I go public, but none of these should be as big as the aforementioned items. When added up, though, they will probably take more time than them to complete, and there's always the tiny issue that my to-do list always seems to grow twice faster than I can shorten it. I'll have to pick a time when I figure that, well, it's okay Nao, it's okay... You can release.
With great power, comes gr... Oh no, not that Spider-Man crap again. But still, Wedge is an important project, one that could bring a nice breath of fresh air to the forum world, and even to the CMS world. As in, "community management system", not "content". I'm devoted to making Wedge a great, fun way to communicate with people, be they your friends or ephemeral guests, and help them feel at home and find the answers they seek.
And if it works, then maybe, in some way, it wiil also be the answer I've been looking for.
Get to work, Nao... Now!
For those of you who didn't follow the latest developments on the forum, I'm sad to announce that one of the zombies is now officially resting in peace, carrying his own head, basking in the glory of his past achievements. Said zombie we called Arantor, and in pure retirony style, he decided to call it quits a couple of days before the anniversary. And I'd planned to show up at his door on that day and give him cookies! Well, no cookies then. Blame that good old UK craze about cookies.
And here we are. It's lonely at the top, but at least it means I get to make some hard decisions that we always postponed because we weren't sure about them. Same for Pete on his side, I'm guessing, albeit with other projects. I'm hoping we'll still see him pop up from time to time, and share his disbelief about how badly I handled the project. I always appreciate constructive criticism, after all.
Now, here's the point I wanted to address. There you go, Pete's state of mind up to this point was that we had no plans to release Wedge in the near future, that we didn't even have a tentative release date, and that it was even unlikely to ever happen. I understand his position, I'm not going to put the blame on anything; fact is, yes we slowly drifted apart as collaborators in the last couple of years, mostly because of real life issues for each of us, and because the weight of the project started to get very heavy year after year. The longer you wait until release, the more pressure you put on yourself to make it worthy of the wait.
And this is my first decision.
I'm putting Wedge on the road it should never have left: the road to release. Not the road to completion, which is a different thing altogether. With such a huge project, one man alone just can't complete the project. At most, he can do 80% of it, but he has to rely on other people to do the rest, simply because there are always some tasks where you know that other people will do a better job; that's what kept Pete and I together for so long, and I was hoping it would remain that way, because we really were complementary on most points. Working alone is not easy. Some days, you just want to say "screw Wedge!", and watch a movie or a TV show for hours. And you know what? I'll do just that. I've seen tons of silly and better movies, and I'm still going back to Wedge every day, because if there's something I'll never, ever give up before it's out for the public to enjoy, it's Wedge. Even if it doesn't bring me a dime, I need to finish it.
So, what's the tentative release date? Nope, sorry... There still isn't any. And before you ask why -- ask yourself whether you prefer to be given a wrong release date, or be told exactly what remains to be done to have a releasable product. To the former, I'll just say this: I'm hoping to release a public beta before the end of the year, and a final 1.0 in early 2014. Do what you want with that silly date, and if you're in too much of a hurry, and you consider yourself to be a hardened, hardboiled, hardcore, hard-wired forum administrator with a taste for trouble and a love for HTML/JS/CSS/PHP/FTP tweaks, you can always contact me with a request for private beta access and a copy of the SMF importer code.
To the latter, I'll be more thorough. First, I'll try to list a few of the things I wanted to do since day one, and will probably not do in the first release... Aeva Media is a monster to handle, it used to be my full-time (unpaid) job. I wanted to redo so many parts of it. Most importantly, I wanted to replacement attachments with media items; I'm still planning to do it, but if it's not done when everything else is ready, I'll still release. Also, Noisen.com features... I wrote many features for my personal website around 2007-2008, and was adamant I'd include them. Pete persuaded me otherwise, for very good reasons mainly, but now that he's gone, I can decide, if I want, to fail in a spectacular fasion. Go get the pop-corn. Again: if it's not ready when the rest is, I'll still release.
And now, for the features that I can't see myself release without.
- Privacy (estimated amount of work: a few weeks) : there are already some privacy features in; thoughts have privacy. Topics have some sort of privacy. I'm hoping I can do board privacy, à la Noisen, and profile privacy, à la Facebook. And fix an annoying bug in the 'Contacts' option: if you post a thought for your contact list, and someone replies to it, and you're not in their contact list, then you won't be able to view their reply. To be honest, I've thought of several solutions for that, but it's hardly anything solid, or at least efficient.
- Contact lists (a few weeks): so far, Wedge has been using SMF buddy lists, while Noisen has been using a customized version of Ultimate Profile (a nice little SMF mod from back in the day), where I allowed you to 'hide' a contact from view, and nice little things like that. Contact lists are my biggest project right now, I've already started work on them, but still need to write the UI, and some other things, to make them usable. The idea is that you can categorize your friends into multiple lists, choose the list name, and even determine the visibility of said list to profile viewers; you should be able to add people to multiple lists, and target a thought/topic privacy to a specific list. (Not multiple lists -- it's already complicated as it is, UI-wise.) My biggest issue right now, is handling the aftermath of adding someone to a list. Should they be notified of it? Should a list have a setting to determine if notifications should be issued? Et cetera, et cetera...
- Skins (a few weeks?): there are two things here.
(1) I'm not sure whether I should enforce sub-skins to be put inside a parent skin's folder (which I always found to be a natural thing to do), or simply require them to specify the name of their parent (author:skin_name) in a skin option. The latter option would allow skins to have folders for images, templates, etc. without the need for a different folder naming scheme, such as adding an underscore (_) before the name of any folder that isn't a sub-skin.
(2) As I discussed recently in the Friends board, I'm very, very tempted to remove themes from Wedge entirely. Just like Pete removed SMF packages when he finished his implementation of plugins, I'm in a similar situation where my skin system can do 99% of what templates can do, and it's just tempting to say, "themers have to re-learn mostly everything anyway, so I might as well get rid of that relic." Recently, I implemented one of the last things missing from skin features -- the ability to override/before/after a template function from within a skin.xml file. It was already possible to override a function through the use of a Custom.template.php file inside the skin, but it's not a rock solid solution because of the possibility of conflicting function names, and I only added this as a way for themers to 'test' their replacement code in a comfortable PHP editing environment, before they simply move their functions to an XML editing environment, without the proper syntax highlighting.
- AeMe comments (a week?): I'm planning to remove them entirely, and replace them with regular board topics. The idea is to create a generic board (hidden or not), where topics are created on the fly when posting a comment to an album or a media item. The advantage is that you get to comment on whole albums as well, and that you can search inside media item comments. The drawback is that I'm not planning to write an import tool for existing comments. They'll either have to go, or Thorsten (@TE) will have to account for them in his fantastic OpenImporter tool. Oh yes, and another drawback-- I'll have to handle attempts to access a media comment topic directly, by redirecting to said media item (or album). I don't know how I can do it efficiently, though.
- Others (weeks? months?): There are, I'm afraid, many other things that I'll attempt to fix before I go public, but none of these should be as big as the aforementioned items. When added up, though, they will probably take more time than them to complete, and there's always the tiny issue that my to-do list always seems to grow twice faster than I can shorten it. I'll have to pick a time when I figure that, well, it's okay Nao, it's okay... You can release.
With great power, comes gr... Oh no, not that Spider-Man crap again. But still, Wedge is an important project, one that could bring a nice breath of fresh air to the forum world, and even to the CMS world. As in, "community management system", not "content". I'm devoted to making Wedge a great, fun way to communicate with people, be they your friends or ephemeral guests, and help them feel at home and find the answers they seek.
And if it works, then maybe, in some way, it wiil also be the answer I've been looking for.
Get to work, Nao... Now!
2508
Archived fixes / Re: Undefined index error
« on September 17th, 2013, 11:54 PM »
Not an actual bug, more a mixup on my part between my two codebases (i.e. my local codebase, which has an ongoing privacy rewrite, and the official svn codebase, which doesn't), when uploading the updated version of the website. I'm not sure how it came to be, though... But whatever, doesn't really matter, thanks ;) Fixed!
2509
Features / Re: New revs
« on September 17th, 2013, 06:26 PM »
rev 2254
(15 files, 6kb)
! A few files were incorrectly set to ISO-8859-1 when they should be UTF-8. These were the files whose copyright lines I modified manually, rather than automatically. Not that it matters much, though: I'll probably change the copyright data again soon, and they'll all be ISO again. Meh. (.htaccess, Settings.php, Settings_bak.php, ssi_examples.shtml, Home.template.php, Class-ZipExtract.php, Wuthering/extra.css, Wireless/extra.css, zoom.css)
! Forgot to credit Karl Benson for the early versions of Aeva in the contributor file. (contributors.txt)
* Renamed 'Consultants' to 'Contributors' in the Credits page (that's been pretty much the same thing so far...), and simplified the code. (Credits.php, Who.template.php, Who.language.php)
* Spacinazi. (Wine/extra.css)
(15 files, 6kb)
! A few files were incorrectly set to ISO-8859-1 when they should be UTF-8. These were the files whose copyright lines I modified manually, rather than automatically. Not that it matters much, though: I'll probably change the copyright data again soon, and they'll all be ISO again. Meh. (.htaccess, Settings.php, Settings_bak.php, ssi_examples.shtml, Home.template.php, Class-ZipExtract.php, Wuthering/extra.css, Wireless/extra.css, zoom.css)
! Forgot to credit Karl Benson for the early versions of Aeva in the contributor file. (contributors.txt)
* Renamed 'Consultants' to 'Contributors' in the Credits page (that's been pretty much the same thing so far...), and simplified the code. (Credits.php, Who.template.php, Who.language.php)
* Spacinazi. (Wine/extra.css)
2510
Features / Re: New revs
« on September 17th, 2013, 12:31 PM »
rev 2253
(2 files, 2kb)
! Finally-- follow_me is pixel-perfect. I took an hour of my time to reconsider the math of it all, and found 3 little bugs in my calculations; Neither the separator height not the fixed userbox top position were taken into account, and ended up doing strange things on very short posts. Also, there was some kind of a margin collapse trick that happened in the user name and made positioning more complicated; replace the margin with a padding, it works just the same. It's all in the past, now. I can finally devote my time to another cool feature. I wish. (topic.js, sections.css)
(2 files, 2kb)
! Finally-- follow_me is pixel-perfect. I took an hour of my time to reconsider the math of it all, and found 3 little bugs in my calculations; Neither the separator height not the fixed userbox top position were taken into account, and ended up doing strange things on very short posts. Also, there was some kind of a margin collapse trick that happened in the user name and made positioning more complicated; replace the margin with a padding, it works just the same. It's all in the past, now. I can finally devote my time to another cool feature. I wish. (topic.js, sections.css)
2511
Development blog / Re: It only took two guys two years...
« on September 17th, 2013, 11:48 AM »
Proved you wrong!
And you KNOW I couldn't do a proper roadmap... You're just teasing me :P
Sorry about the spelling this morning... I'd just gotten out of bed, and couldn't be arsed to go to my PC to reply, eh.
And you KNOW I couldn't do a proper roadmap... You're just teasing me :P
Sorry about the spelling this morning... I'd just gotten out of bed, and couldn't be arsed to go to my PC to reply, eh.
2512
Development blog / Re: It only took two guys two years...
« on September 17th, 2013, 06:40 AM »
As far as long posts go, I had an email convo with Pete yesterday (cla stuff), so my Hans were full. ^^
Hands. Silly s3.
Hands. Silly s3.
2513
Development blog / Re: It only took two guys two years...
« on September 16th, 2013, 11:19 PM »
Technically, he's not wrong... It's just that I'm not much into developing a thesis around development, if you will. I'm more of an action guy (well, a bit less these days...), and I'll centralize all of my development history into one place -- the changelog, i.e. also the New Revs topic, where I post all of my new commits.
I'm planning to write a blog entry on Pete's departure, and possibly a tentative roadmap (which I believe John just requested of me ;)), and also post something on our (well, my..?) Facebook page, but... Really, I'm a bit overwhelmed. Even when I don't seem to be doing a lot on Wedge, I'm still doing stuff, trying to figure out what I need to do, and also killing real-life bugs. (Sometimes, even literally :P)
I'm planning to write a blog entry on Pete's departure, and possibly a tentative roadmap (which I believe John just requested of me ;)), and also post something on our (well, my..?) Facebook page, but... Really, I'm a bit overwhelmed. Even when I don't seem to be doing a lot on Wedge, I'm still doing stuff, trying to figure out what I need to do, and also killing real-life bugs. (Sometimes, even literally :P)
2514
Features / Re: New revs
« on September 16th, 2013, 11:08 PM »
rev 2252
(295 files, 126kb)
* Updated credits, contributors, license, etc... Not only for anything related to Pete's departure from the project, but also cleaning up the credits and adding anything Pete might have forgotten to credit when he compiled the list. 'Wedgeward' is replaced with my full name until I figure out what's best. Also fixed John's last name. More things left to do... Will come, will come. (contributors.txt, license.txt)
* Updated and harmonized all file headers as much as I could; if anything bad's left, I'll fix it later. (295 files)
* Renamed nested-sortable.js to just nested.js, as there's just the one file... (ManageBoards.php, nested.js)
- Removed all @version tags. I'm not, repeat, I am NOT, going to add @version tags to all files every time I'm releasing a new version. I want to be able to upload a package with only the files since the last time. Really. It's easier to upload. Still need to complete the removal of associated features, though. (295 files or so.)
- Removed some code that relies on reading @version tags. Still some left, though. (smfinfo.php) (Yes, that's an odd filename, I know...)
(295 files, 126kb)
* Updated credits, contributors, license, etc... Not only for anything related to Pete's departure from the project, but also cleaning up the credits and adding anything Pete might have forgotten to credit when he compiled the list. 'Wedgeward' is replaced with my full name until I figure out what's best. Also fixed John's last name. More things left to do... Will come, will come. (contributors.txt, license.txt)
* Updated and harmonized all file headers as much as I could; if anything bad's left, I'll fix it later. (295 files)
* Renamed nested-sortable.js to just nested.js, as there's just the one file... (ManageBoards.php, nested.js)
- Removed all @version tags. I'm not, repeat, I am NOT, going to add @version tags to all files every time I'm releasing a new version. I want to be able to upload a package with only the files since the last time. Really. It's easier to upload. Still need to complete the removal of associated features, though. (295 files or so.)
- Removed some code that relies on reading @version tags. Still some left, though. (smfinfo.php) (Yes, that's an odd filename, I know...)
2515
Plugins / Re: Subaccounts
« on September 16th, 2013, 06:37 PM »
Well, I don't think you're gonna get any competition any time soon ;)
2516
The Pub / Re: Not So Mixed Signals
« on September 16th, 2013, 05:11 PM »
SublimeText has never been my cup of tea-- last time I tried it, it was missing 80% of the functions I think should be core in any text editor, so... Well. And I'm not really talking about complex features-- I'm talking about UX things that are really, really basic.Quote from Hristo on September 15th, 2013, 09:38 PM I'm thinking that's ironic... :P
But I really, really need to be able to put my mouse cursor on the far right, inside the scrollbar 'button', and then be able to drag the button along the scrollbar. I can roughly aim my cursor to the button, but I don't see why I'd have to do it on both axis (horizontal/vertical), when with a scrollbar that sticks to the window edge, I can simply aim vertically, and expect the horizontal position to be right inside the button, since it sticks to the edge. Anyway...! This is, along with tabs, one of the reasons I adopted Opera many, many years ago. Most browsers do it now, but some won't, and that's a direct bye-bye from me.
That is a good point!
But I really, really need to be able to put my mouse cursor on the far right, inside the scrollbar 'button', and then be able to drag the button along the scrollbar. I can roughly aim my cursor to the button, but I don't see why I'd have to do it on both axis (horizontal/vertical), when with a scrollbar that sticks to the window edge, I can simply aim vertically, and expect the horizontal position to be right inside the button, since it sticks to the edge. Anyway...! This is, along with tabs, one of the reasons I adopted Opera many, many years ago. Most browsers do it now, but some won't, and that's a direct bye-bye from me.
2517
Features / Re: New revs
« on September 16th, 2013, 05:07 PM »
rev 2251
(12 files -1, 278kb, 10 minutes of work.)
* Updated getID3 from v1.9.1 to 1.9.7. Has the new (MPL) license, good! Haven't tested it, though... (media/getID3/*)
(12 files -1, 278kb, 10 minutes of work.)
* Updated getID3 from v1.9.1 to 1.9.7. Has the new (MPL) license, good! Haven't tested it, though... (media/getID3/*)
2518
Features / Re: New revs
« on September 16th, 2013, 03:46 PM »
rev 2250
(6 files, 3kb)
* Tweaked Zoomedia. The Close button is now drawn in pure CSS if possible (saving a whopping 2KB off the file and making it HD-friendly), removed the delay as I forgot I'd recently implemented it in the 'main' show_ajax function, saved oldIE from showing the double-click catcher (it just didn't work properly anyway), and fixed bottom padding in Glass mode (hopefully! Needs testing.) (zoomedia.js, zoom.css)
+ Zoomedia can now be shown when previewing posts in the Notifications area. Note that there's a trade-off: I specifically allowed Ajax calls to load Zoomedia, but it also means all Ajax calls need to account for $context['footer_js'] not being shown at all, and must do it manually. I'm already doing it in a few places, but not everywhere, so... These bugs will have to be fixed as they occur, basically, or I need to find a way to safely load footer_js systematically without screwing up the page. I'll get to that, eventually. That's all in a day's job for Ajax man. (Subs-Media.php, Notifications.php)
- Saving a buffer str_replace off English pages-- at least we know these don't use half-width unbreakable, uh... (Subs-Template.php)
! Ajax loader was incorrectly positioned when the parent element had padding. (script.js)
! A small typo of mine in the notification code. (script.js)
(6 files, 3kb)
* Tweaked Zoomedia. The Close button is now drawn in pure CSS if possible (saving a whopping 2KB off the file and making it HD-friendly), removed the delay as I forgot I'd recently implemented it in the 'main' show_ajax function, saved oldIE from showing the double-click catcher (it just didn't work properly anyway), and fixed bottom padding in Glass mode (hopefully! Needs testing.) (zoomedia.js, zoom.css)
+ Zoomedia can now be shown when previewing posts in the Notifications area. Note that there's a trade-off: I specifically allowed Ajax calls to load Zoomedia, but it also means all Ajax calls need to account for $context['footer_js'] not being shown at all, and must do it manually. I'm already doing it in a few places, but not everywhere, so... These bugs will have to be fixed as they occur, basically, or I need to find a way to safely load footer_js systematically without screwing up the page. I'll get to that, eventually. That's all in a day's job for Ajax man. (Subs-Media.php, Notifications.php)
- Saving a buffer str_replace off English pages-- at least we know these don't use half-width unbreakable, uh... (Subs-Template.php)
! Ajax loader was incorrectly positioned when the parent element had padding. (script.js)
! A small typo of mine in the notification code. (script.js)
2519
The Pub / Re: Not So Mixed Signals
« on September 15th, 2013, 08:40 PM »
Alright, tested TextEd a bit... Very disappointed. There's a single pixel on the right side that doesn't do anything when you click it. If it weren't for that single pixel, I'd be able to scroll without having to very clearly target the scrollbar. Too bad.
Also, couldn't get syntax highlighting to work, uh uh... Other than that, it looked okay, but that's all.
Also, couldn't get syntax highlighting to work, uh uh... Other than that, it looked okay, but that's all.
2520
The Pub / Re: Not So Mixed Signals
« on September 15th, 2013, 08:14 PM »
Yes, there's a Replace All, but you can't enter multiple lines of text to replace with another few lines -- the search terms can't span multiple lines, see..? That's where grepWin does a better job, really.
@Hristo, thanks for the heads up!
:edit: Wow... 44MB for RJ TextEd...? Nice! :lol: :^^;: Still, I'll give the portable version a try, it looks from the screenshots like there's no extra spacing between the right scrollbar and the edge of the screen, a no-no for me (which, unfortunately, Notepad++ has. Yes, it's that silly...)
@Hristo, thanks for the heads up!
:edit: Wow... 44MB for RJ TextEd...? Nice! :lol: :^^;: Still, I'll give the portable version a try, it looks from the screenshots like there's no extra spacing between the right scrollbar and the edge of the screen, a no-no for me (which, unfortunately, Notepad++ has. Yes, it's that silly...)