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
2551
Features / Re: New revs
« on September 5th, 2013, 10:04 AM »
rev 2237
(3 files, 2kb)
* Saved nearly 400 ungzipped bytes in JS and about 90 gzipped bytes in follow_me, by doing a near-complete rewrite. It was planned before my earlier commit, but I wanted to keep a SVN copy of the 'safe route', hence the commit. The Firefox hack is gone, as I'm no longer relying on position: relative (making for shorter CSS too), added an IE7 exception because it uses a floated div and I won't bother to calculate the post height rather than user box height just for it. Also, the inner div is no longer named (shorter HTML! I thought about adding it through JS too, but it may be good for skinners to keep it around)... This should be the 'perfect' version of the follow_me feature... (Until I get around to implementing it on horizontal layouts, and maybe add IE7 support, but don't hang onto that.) (Msg.template.php, topic.js, sections.css)
(3 files, 2kb)
* Saved nearly 400 ungzipped bytes in JS and about 90 gzipped bytes in follow_me, by doing a near-complete rewrite. It was planned before my earlier commit, but I wanted to keep a SVN copy of the 'safe route', hence the commit. The Firefox hack is gone, as I'm no longer relying on position: relative (making for shorter CSS too), added an IE7 exception because it uses a floated div and I won't bother to calculate the post height rather than user box height just for it. Also, the inner div is no longer named (shorter HTML! I thought about adding it through JS too, but it may be good for skinners to keep it around)... This should be the 'perfect' version of the follow_me feature... (Until I get around to implementing it on horizontal layouts, and maybe add IE7 support, but don't hang onto that.) (Msg.template.php, topic.js, sections.css)
2552
Archived fixes / Re: User box screwing up post height in quick edit mode
« on September 4th, 2013, 09:46 PM »
A popup is disruptive. What do you mean by ajaxify..?
A popup within the same page is less disruptive, but it means it's harder to check out other posts while editing.
A popup within the same page is less disruptive, but it means it's harder to check out other posts while editing.
2553
Features / Re: New revs
« on September 4th, 2013, 08:44 PM »
rev 2236 -- follooooooow me! (Amiga fans, anyone..?)
(5 files, 5kb)
* Improved the userbox follower to account for IE6 (which we don't really care about) and Firefox (which doesn't support position: relative on table cells, but I applied a workaround), run the code immediately after page load (rather than on the first scroll), and improve performance when the userbox is starting to shimmer into the horizon called the page top. Still needs some work, possibly even a minor rewrite... Also, minor fix in userbox CSS, mostly in IE 6-8. (topic.js, sections.css)
! Fixed a problem with language file paths in plugins. Fix was kindly donated by John/live627, as I currently suck as handling plugin code. Thanks! (ManageLanguages.php)
! Fixed a JS error on media pages when running with IE6. (zoomedia.js)
* Tweaked layout in media pages with IE6. That browser doesn't get any better ahah... (extra.ie6.css)
(5 files, 5kb)
* Improved the userbox follower to account for IE6 (which we don't really care about) and Firefox (which doesn't support position: relative on table cells, but I applied a workaround), run the code immediately after page load (rather than on the first scroll), and improve performance when the userbox is starting to shimmer into the horizon called the page top. Still needs some work, possibly even a minor rewrite... Also, minor fix in userbox CSS, mostly in IE 6-8. (topic.js, sections.css)
! Fixed a problem with language file paths in plugins. Fix was kindly donated by John/live627, as I currently suck as handling plugin code. Thanks! (ManageLanguages.php)
! Fixed a JS error on media pages when running with IE6. (zoomedia.js)
* Tweaked layout in media pages with IE6. That browser doesn't get any better ahah... (extra.ie6.css)
2554
The Pub / Re: Not So Mixed Signals
« on September 4th, 2013, 12:00 AM »
So...
It took me about an hour or so to read through this post. This has got to be the longest one ever posted on wedge.org... ;)
I want to reply to it paragraph by paragraph, with one-liners. But it's probably unrealistic to expect me to take several hours to do that. So, in case I don't do it -- I'll just say that I agree with Farjo overall; I think that Pete leaving has upset me more for the way it happened (given that I repeatedly complained about that), than for the leaving itself. I think that it's unlikely Pete wants to stop working on Wedge altogether; his being still active at sm.org and other sites is proof that it's just hard for him to leave forums behind, and I think he's struggling to find a way to leave his addiction behind.
So, it's probably safer for me to assume that the best thing to do right now for the project, is to do as if Pete would indeed never come back, but still a door open in case he comes back in a few months with less weight on his shoulders, and a feeling that whatever he does for Wedge is for the best, rather than something that will be torn apart by reviewers.
I believe I've done my job correctly by doing relatively thorough checks of all Pete's commits, and that he's done as good as a job as he could by checking mine; it's true that I made twice as many commit as he did, and sometimes it was just overwhelming, and he may have skipped these reviews, while in recent years, I've been more thorough in my checks because he committed less often, and thus I've more often had the opportunity to suggest minor improvements, not because I didn't like the original code, but simply because I feel more comfortable improving on others' code than writing mine from scratch.
Just look at the path I made for myself, really...
- Kyodai Mahjongg: 100% original code, but the first version was basically an improved clone of Microsoft's Taipei.
- Aeva Media: Dragooon made SMF Media Gallery 1.0; I started work on it and released version 1.5. After version 2.0, I took over development entirely. But I would never, never have created a gallery if I had to start from scratch...
- Footnotes: that's probably the only piece of code I ever started from scratch, but (1) it's just a few kilobytes, (2) the package itself was probably taken from another simple mod, and rewritten to do the footnote trick instead. Just like Wedge plugins, I never really got into making SMF mods.
- Wedge:
* Wess is based upon a script written by someone else; it was full of limitations, and I basically rewrote 95% of it. Still, I used it as a basis for my code because I wanted some code to parse multiple parents in CSS, and couldn't be arsed to figure out the proper algorithm for it.
* Skeletons are another piece of mine that may seem to be done entirely from scratch, but it's still just a "modification" of SMF's original templating system, albeit in a new file and with tons of new features.
* Nothing else comes to mind for now, but really, the idea is that 95% of my code is always *built upon* existing code, be it large overhauls or incremental improvements, and that I've never felt as 'creative' as Pete is; I just don't have such high hopes as he does, I know what I'm good at (fixing code, improving code), and I tend to focus on that; innovation comes second, on the spur of the moment. To me, the innovator in Wedge is Pete, and whatever he commits, I can only contribute to by fixing a few things. To use the ever-useful car analogy: I didn't build the car, I'm just the garageman. When the car is delivered to me for a revision, I'll just look at it in awe, and figure that since there's nothing broken with it and that I'm still being paid a lot for maintenance, I could add just a few tweaks here and there, just to get a feeling that the customer is happy with my intervention, and doesn't feel like they wasted their money on it.
And yes, I'm aware, and have been aware for a while, that Pete didn't actually enjoy having his code tweaked, but it's something of a compulsive reaction in me, I just can't do without it. I need to add my signature to it, while leaving the ideas and greatness overall intact.
So, ironically, I should be the one who's depressed because I feel that I can't bring much creativity to the table. Yet, I feel confident in my capabilities, because I have nothing to prove from my past endeavors, and I simply contribute with pleasure.
We've had a lot of good times, Pete and I, and it's not something I'll forget any time soon. I'd rather remember our partnership this way, thank you very much. I know that it's going to be hard for him to come back in a few weeks or months because in the meantime I'll have taken spiritual ownership of the project, but I'm sure he'll understand that while not being the 'boss' means you don't get to make decisions, it's important to remember that the boss still insists on listening to user opinions before making such decisions.[1]. I've always had the utmost respect for anyone else's contributions, and my tweaking them has never meant anything more than being that little garageman nobody who just enjoys looking at the perfectly oiled machinery, and add an extra pump here and there to... well, contribute to making it even better, just like anyone else.
It took me about an hour or so to read through this post. This has got to be the longest one ever posted on wedge.org... ;)
I want to reply to it paragraph by paragraph, with one-liners. But it's probably unrealistic to expect me to take several hours to do that. So, in case I don't do it -- I'll just say that I agree with Farjo overall; I think that Pete leaving has upset me more for the way it happened (given that I repeatedly complained about that), than for the leaving itself. I think that it's unlikely Pete wants to stop working on Wedge altogether; his being still active at sm.org and other sites is proof that it's just hard for him to leave forums behind, and I think he's struggling to find a way to leave his addiction behind.
So, it's probably safer for me to assume that the best thing to do right now for the project, is to do as if Pete would indeed never come back, but still a door open in case he comes back in a few months with less weight on his shoulders, and a feeling that whatever he does for Wedge is for the best, rather than something that will be torn apart by reviewers.
I believe I've done my job correctly by doing relatively thorough checks of all Pete's commits, and that he's done as good as a job as he could by checking mine; it's true that I made twice as many commit as he did, and sometimes it was just overwhelming, and he may have skipped these reviews, while in recent years, I've been more thorough in my checks because he committed less often, and thus I've more often had the opportunity to suggest minor improvements, not because I didn't like the original code, but simply because I feel more comfortable improving on others' code than writing mine from scratch.
Just look at the path I made for myself, really...
- Kyodai Mahjongg: 100% original code, but the first version was basically an improved clone of Microsoft's Taipei.
- Aeva Media: Dragooon made SMF Media Gallery 1.0; I started work on it and released version 1.5. After version 2.0, I took over development entirely. But I would never, never have created a gallery if I had to start from scratch...
- Footnotes: that's probably the only piece of code I ever started from scratch, but (1) it's just a few kilobytes, (2) the package itself was probably taken from another simple mod, and rewritten to do the footnote trick instead. Just like Wedge plugins, I never really got into making SMF mods.
- Wedge:
* Wess is based upon a script written by someone else; it was full of limitations, and I basically rewrote 95% of it. Still, I used it as a basis for my code because I wanted some code to parse multiple parents in CSS, and couldn't be arsed to figure out the proper algorithm for it.
* Skeletons are another piece of mine that may seem to be done entirely from scratch, but it's still just a "modification" of SMF's original templating system, albeit in a new file and with tons of new features.
* Nothing else comes to mind for now, but really, the idea is that 95% of my code is always *built upon* existing code, be it large overhauls or incremental improvements, and that I've never felt as 'creative' as Pete is; I just don't have such high hopes as he does, I know what I'm good at (fixing code, improving code), and I tend to focus on that; innovation comes second, on the spur of the moment. To me, the innovator in Wedge is Pete, and whatever he commits, I can only contribute to by fixing a few things. To use the ever-useful car analogy: I didn't build the car, I'm just the garageman. When the car is delivered to me for a revision, I'll just look at it in awe, and figure that since there's nothing broken with it and that I'm still being paid a lot for maintenance, I could add just a few tweaks here and there, just to get a feeling that the customer is happy with my intervention, and doesn't feel like they wasted their money on it.
And yes, I'm aware, and have been aware for a while, that Pete didn't actually enjoy having his code tweaked, but it's something of a compulsive reaction in me, I just can't do without it. I need to add my signature to it, while leaving the ideas and greatness overall intact.
So, ironically, I should be the one who's depressed because I feel that I can't bring much creativity to the table. Yet, I feel confident in my capabilities, because I have nothing to prove from my past endeavors, and I simply contribute with pleasure.
We've had a lot of good times, Pete and I, and it's not something I'll forget any time soon. I'd rather remember our partnership this way, thank you very much. I know that it's going to be hard for him to come back in a few weeks or months because in the meantime I'll have taken spiritual ownership of the project, but I'm sure he'll understand that while not being the 'boss' means you don't get to make decisions, it's important to remember that the boss still insists on listening to user opinions before making such decisions.[1]. I've always had the utmost respect for anyone else's contributions, and my tweaking them has never meant anything more than being that little garageman nobody who just enjoys looking at the perfectly oiled machinery, and add an extra pump here and there to... well, contribute to making it even better, just like anyone else.
| 1. | Just have a look at the project name change... A bit over half of the poll votes were against the change, and thus I decided to leave my idea aside for the time to come, and focus on other matters, even though I was very much into renaming it. |
2555
The Pub / Re: Font size in Chrome Android
« on September 3rd, 2013, 04:52 PM »here a screenshot with the wireless theme...
but .. why dont switch wedge not automatically to this theme on mobile detection?
I'm actually considering adding a skin setting to say, basically, "this skin is mobile-compatible, apply a few magic fixes to make it work there", but I'm afraid people would get lost then -- "why is Wireless the default mobile skin when it's nearly the same as Weaving on mobile...?"
2556
Archived fixes / Re: Language search fouls up with plugins with subfolders
« on September 3rd, 2013, 04:50 PM »
Okay, applied your fix to the file. (And made it all into one line... No need to use a temp variable for that, is there...?)
Thanks!
I'll learn the system if nobody steps up to maintain it and it turns out that I absolutely need to fix things. Otherwise, frankly, I have too much on my plate right now to start looking into learning things that Pete left hanging. I believe he fixed 99% of what he needed to fix everywhere, so I think I can safely leave these things aside until needed. Right now... Nope.
What I'm expecting of you? I'm expecting nothing of you. If I were expecting something of you, that might influence you to work on things, and then get upset with me for some reason. I only want you to do what you're willing to do for Wedge. So, basically, if you want to take over whatever Pete was working on and that you know better than I do, by all means, please do it. If you're not willing to, then it's just fine as well. I'm certainly not going to put the pressure on anyone; it is up to me, and me alone, to carry the Weight of Wedge until it gets released.
Thanks!
I'll learn the system if nobody steps up to maintain it and it turns out that I absolutely need to fix things. Otherwise, frankly, I have too much on my plate right now to start looking into learning things that Pete left hanging. I believe he fixed 99% of what he needed to fix everywhere, so I think I can safely leave these things aside until needed. Right now... Nope.
What I'm expecting of you? I'm expecting nothing of you. If I were expecting something of you, that might influence you to work on things, and then get upset with me for some reason. I only want you to do what you're willing to do for Wedge. So, basically, if you want to take over whatever Pete was working on and that you know better than I do, by all means, please do it. If you're not willing to, then it's just fine as well. I'm certainly not going to put the pressure on anyone; it is up to me, and me alone, to carry the Weight of Wedge until it gets released.
2557
The Pub / Re: Not So Mixed Signals
« on September 2nd, 2013, 05:21 PM »I don't ever remember this actually happening? On the other hand I can think of several examples where you changed things, I made it very clear I didn't like it, explained why and was completely ignored.
Like the sidebar changes in recent times
so much so that the *need* to move PMs out of the menu was apparent because it was the only way to know that I'd have messages (since the PM popup doesn't really count, especially if the PM count gets out of sync, which it does occasionally)
It'll be good for you to develop your skills, actually.
Is Wedge everything I need to know about in life?
It's a codebase with 100+ thousands of lines, even with two people dealing with two different sides of it (frontend and backend), it STILL made for thousands of line to maintain each... Believe me, I already had enough on my plate, and certainly didn't want to know more than the basics from your side, just like I'd never expect you to work too much on the frontend area.
Having at least an awareness of security, of optimisation of DB stuff (which, by comparison, is far more of a killer than byte optimisations tend to be), will make you a more rounded developer.
There are so many areas I trusted to you too, but when I had concerns, very often they weren't listened to. And when I did so much as breathe in the direction of those areas, I felt like I was always doing it wrong because every time you'd rewrite the code (how often, seriously, did I rewrite your code?)
I'm not saying.
What I'm saying is, that's how I work in a team. I tend to supervise all code and try and make it look unified. My changes were mostly suggestions, or optimizations. I never felt that your code was sacred, and I never asked you to consider mine as sacred either. That was your problem to solve, not mine.
I have more respect for you than that.
"My life fell apart today... Thankfully, I have Wedge to focus on, so I can change my mind...
- Just what I was waiting for! I'm leaving the project!"
Is it like in these books where they tell you that then nerve system is made in a way that if you're hurting somewhere, you should pinch another area and it'll lessen the pain? Nice of you! :angel:
If I wanted out, I'd just say so. You even told me that I owed Wedge nothing and could walk away at any time.
But it wasn't about 'wanting out' as such. The problem wasn't the fact that Wedge is a black hole where thousands of hours of work go into and for seemingly no reward, the problem is that I began to actively hate the experience of developing for it and I resented putting my time into something that made me feel like that.
I don't know if you've had comments from community members about my attitude and expressing sympathy or not,
Apart from that, nothing except the public comments about people being sad that you left the project. And my girlfriend -- she doesn't have as biased an opinion as you might expect of you; still, she thought that you considering our multiple invitations to come visit us, the fact that you never even talked to me was proof that I should have been more careful. And that you weren't very honest with me, and worse, with yourself. :-/
I daresay you probably have. On the other hand, I've had some comments (from people that, in a shock and surprise move, I'm choosing not to name) that they're surprised we ever hooked up in the first place, because they knew it wouldn't work out (and they're surprised it lasted as long as it did)
I only mention what people tell me if I can *actually* name them and quote them on that. Otherwise, it doesn't mean anything to me (or you). You know, like "Pete, I've heard that some people thought you were a jerk and were planning to hurt you... Oh, sorry, I can't tell you whom. I just thought you might want to know. Good night."
What I want to say is -- saying this kind of thing; it's not nice to me or your 'friends', and it doesn't help.
Yes, because it's all about you, isn't it? On the contrary, I made things easier in several ways - firstly, I cleaned up the licensing situation as best I could.
Okay, so, I choose to keep the current Wedge license. What now?
Can I change the copyright to just René-Gilles Deberdt, or do I have to keep Wedgeward alive, even though I'm the only one in it? You didn't tell me that... Do I have to add your copyright to all files you wrote? What ratio of Arantor code should I take into account? Or can I just credit you in contributors.txt and the credits page and be done with? What if you want to make your own fork? How awkward would it be that you have to ask me whether you can re-use some of my code that ended up in one of your features? Etc...
Secondly, I made sure that my own pet project which may or may not go anywhere doesn't have Aeva in it, so it's not like Wedge is losing uniqueness, and thirdly, I said it indirectly but might as well make it more formal: you're absolutely free to use any of my contributions in any fashion you like. I'm hereby granting an irrevocable licence to Wedge (or whatever the project becomes called) for any contributions I made, code, documentation, anything, under the BSD licence. If you want to relicence it, fine. But it's there.
Wedge will probably end up with an OSI license in the future, but right now it's still something fragile.
I'll also add -- what is the legal value of the message you just posted? What legal authority could ascertain that *you* posted it, and that I didn't manipulate the database to make it look like you posted it?
See, that's what I mean. Working on Wedge together for three years was simpler than you think -- because of the mutual trust. We didn't really care about the legal shenanigan because we didn't have anything to lose or gain from it. Once you left the project in a bad mood, so many things became obscure.
If I wanted to kill the project, there are ways I could have done that, and far more effectively. I could have totally stitched you up, because I could have made the threat that nearly killed SMF in 2010 and I would have had just as much legal right to do, because I could have demanded all my contributions be removed because I still hold my copyright to them, which would have left you in a very strange and awkward position, as wesql would have had to be removed or at least reverted back to $smcFunc, along with removing the warning system, the ban system, the plugin system, the language editor, the rewrites of the bbc parser to use the database... the list goes on.
Anyway, here's what I have in my hands:
- First, you told me you were leaving web software behind for a long time. It only took you one week to come back and, err... Basically tell me that you're forking SMF again?! Whether publicly or privately, doesn't matter... Wedge started out as a private fork. If you want to work on a SMF codebase and be your own boss, why didn't you just agree to my suggestion of splitting the project in two and try to keep it in sync as much as possible (and as we'd like)...?
- Each of us worked separately on what we thought would be best to implement in Wedge. That is, if you were to remove all of your contributions overnight, I would certainly be devastated, but that wouldn't mean Wedge has become a piece of shit. Indeed it still has, at that point, all of the new features I wanted it to have... And I can rewrite whatever you took away that I absolutely need, such as wesql. There aren't 30 ways to write a static MySQL library anyway... I wouldn't rewrite the plugin system either, and that would be a loss to users, but it's still not a blow Wedge couldn't recover from. Neither of us single-handedly hand Wedge the best SMF fork out there. The both of us brought our best to it, and we both had different things to add to it. I'm still thrilled by how much we managed to do in three years, but I'm also of the opinion that it should be released now, and that anything else we want to add later, we can always write a converter to deal with. It's never been impossible.
The bottom line is that I finally had enough of dealing with your attitude
and I can't do it any more. Even now I feel like I'm forced to justify my decisions to you or explain them - I don't owe you explanations. I certainly don't owe you justifications. But here we are.
As for why I didn't make a topic, it's because it was a couple of lines of throwaway comment that didn't need to be a topic, more a simple observation that got sidetracked and blown entirely out of proportion yet again.
Oh wait, that's what you did last month...
Then maybe you should stop taking breaks. :geek: :ph34r:
My pet project is experimental, it may not go anywhere but while I'm concentrating on C#, I'd like to feel that the last 10 years honing PHP and 3 years on Wedge wasn't a total waste.
Even I am in a similar situation, I guess...
1997: made Kyodai Mahjongg, in Delphi (Pascal)-- from the same guy who made C# later.
2005: started work on implementing an online ladder system for Kyodai Mahjongg. Started learning PHP to "get it done". Failed to make it work. Tried harder at learning PHP. Finally understood how it works. Got hooked.
2006: stopped work on Kyodai Mahjongg. Never did finish that ladder system... Worked on my websites instead.
2008: got really, really super-involved in forum development.
2010: after making a measly $5K from my 2-years dev work on Aeva Media, started Wedge with you...
2013: I'm not even going to make $5K from it. But it rocks, and I'm proud of it. It'll be buggy when it's out, but it'll still be the best free forum software, and I'll be happy to add this to my résumé once I have to move my ass and find a job. And I suspect you will, too.
Will my pet project be competition? Not really. It's more really poor man's competition for WordPress than Wedge, but you believe what you want to believe, you usually do.
Protendo is competition, too. Doesn't mean I can't have a good relationship with Bloc. He knows how much I respect his talent (and how disastrous it would be if we worked together... Still, I had to offer him the job, out of principle ;)).
See what I mean..? We can be competitors, that's okay, but you need to be clear about all of this. By keeping everyone in the dark, you're only making things easier for yourself. And yes, I believe I deserve to be told, anyway. Whatever you may think of me right now, whatever I may think of you right now, it doesn't change the fact that we both had tons of fun during the last three years, and that I contributed to yours, and that you contributed to mine. It would be just plain sad to leave it at 'we're not compatible as a team' when effectively, we've done great team work for so many years.
2558
Features / Re: New revs
« on September 2nd, 2013, 04:04 PM »
rev 2235
(5 files, 5kb)
+ Implemented support for template function overrides/befores/afters from within skin files. A simple example: <template name="linktree" params="$position = 'top', $force_show = false" where="override">echo $position;</template> will show 'top' instead of the first linktree, and 'bottom' instead of the second one. The default value for 'where' is 'override', you can also use 'before' or 'after' to create functions that will be executed next to the original, while still inherit the original's parameters. This effectively renders extra themes entirely moot, as you can now do pretty much anything you like with skins. And, dare I say..? Maybe even more. (Subs-Cache.php, Subs-Template.php)
* Changed the radial-gradient fixer to only deal with old WebKit versions. Really, Chrome < 26 is nowhere to be seen by now, so Safari < 6 is what I have in mind. This also suddenly makes the W3C's CSS validator say it's a valid website. Everything little bit helps, eh..? (Class-CSS.php)
* Turned a couple of entities back to UTF8 characters. Saves space... (Admin.template.php, Msg.template.php)
@ I'm working on rewriting skin setting parsing to allow more flexibility with param order...
(5 files, 5kb)
+ Implemented support for template function overrides/befores/afters from within skin files. A simple example: <template name="linktree" params="$position = 'top', $force_show = false" where="override">echo $position;</template> will show 'top' instead of the first linktree, and 'bottom' instead of the second one. The default value for 'where' is 'override', you can also use 'before' or 'after' to create functions that will be executed next to the original, while still inherit the original's parameters. This effectively renders extra themes entirely moot, as you can now do pretty much anything you like with skins. And, dare I say..? Maybe even more. (Subs-Cache.php, Subs-Template.php)
* Changed the radial-gradient fixer to only deal with old WebKit versions. Really, Chrome < 26 is nowhere to be seen by now, so Safari < 6 is what I have in mind. This also suddenly makes the W3C's CSS validator say it's a valid website. Everything little bit helps, eh..? (Class-CSS.php)
* Turned a couple of entities back to UTF8 characters. Saves space... (Admin.template.php, Msg.template.php)
@ I'm working on rewriting skin setting parsing to allow more flexibility with param order...
2559
Archived fixes / Re: Language search fouls up with plugins with subfolders
« on September 2nd, 2013, 03:32 PM »
So, what was the right one...?
As for this bug, can you fix it on your side? You know I'm not well acquainted with the plugin codebase yet, so... It'd be helpful, kthx.
As for this bug, can you fix it on your side? You know I'm not well acquainted with the plugin codebase yet, so... It'd be helpful, kthx.
2560
The Pub / Re: Font size in Chrome Android
« on September 1st, 2013, 11:59 PM »
Is it readable to you?
Why not use Wireless? Not suitable for a tablet, maybe...?
Why not use Wireless? Not suitable for a tablet, maybe...?
2561
Archived fixes / Re: Language search fouls up with plugins with subfolders
« on August 31st, 2013, 04:46 PM »
Are you positive..? I don't remember anyone working on this..?
If yes, please move to Archived fixes. ;)
If yes, please move to Archived fixes. ;)
2562
Off-topic / Re: This is why I complain about tracking hits
« on August 31st, 2013, 04:29 PM »
Perhaps we could track both members, and ALL IPs... That way, there's a "reliable" one, and a "relative" one.
2563
Features / Re: New revs
« on August 31st, 2013, 04:28 PM »
rev 2234
(3 files, 1kb)
+ Added a skin_parser hook, which allows you to add custom parameter types to skins, and parse them. (ManagePlugins.php, Subs-Cache.php)
! Fixed a wrong CSS rule on unrecognized user agents. (Class-CSS.php)
! <css for="browser" include="file"> might have included the file in all browsers... (Subs-Cache.php)
(3 files, 1kb)
+ Added a skin_parser hook, which allows you to add custom parameter types to skins, and parse them. (ManagePlugins.php, Subs-Cache.php)
! Fixed a wrong CSS rule on unrecognized user agents. (Class-CSS.php)
! <css for="browser" include="file"> might have included the file in all browsers... (Subs-Cache.php)
2564
Off-topic / Re: This is why I complain about tracking hits
« on August 31st, 2013, 01:57 PM »
For sure.
Although, TBH with you, I'm not sure I'll remove support for guest tracking right now... I mean, I have other priorities. I expected Pete to do it, really :P
Although, TBH with you, I'm not sure I'll remove support for guest tracking right now... I mean, I have other priorities. I expected Pete to do it, really :P
2565
Features / Re: New revs
« on August 31st, 2013, 01:24 PM »
rev 2233
(6 files, 2kb)
! Switching to between Wysiwyg modes generated an undefined index. (Class-Editor.php)
! Smileys were missing some left padding to compensate for the (very appropriate) internal fix I made recently. (editor.css)
! Search icon position was incorrect. (index.css)
- Spoiler input tag was over-styled. Yes, this happens once every blue moon, but I actually removed unneeded CSS. (index.css)
* Made Poll results more responsive, notably by using percentage widths. (Display.php, Wireless/extra.css)
* Spacinazi. (Display.template.php)
(6 files, 2kb)
! Switching to between Wysiwyg modes generated an undefined index. (Class-Editor.php)
! Smileys were missing some left padding to compensate for the (very appropriate) internal fix I made recently. (editor.css)
! Search icon position was incorrect. (index.css)
- Spoiler input tag was over-styled. Yes, this happens once every blue moon, but I actually removed unneeded CSS. (index.css)
* Made Poll results more responsive, notably by using percentage widths. (Display.php, Wireless/extra.css)
* Spacinazi. (Display.template.php)