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
5896
Features / Re: New revs
« on March 22nd, 2012, 12:51 PM »
rev 1498
(10 files, 4kb) (that sounds small for such a large amount of changes to the CSS files...)
* Moved .two-columns and .upshrinks further up the CSS chain, so that it can safely be inherited. (index.css, sections.css)
* Slogan styling redone entirely. Instead of being shown on the right with some random font, it's now shown just after the website title, in the same font, slightly resized and recolored. Required quite a lot of CSS relative to what it does in the end, but it was required because #siteslogan was never really styled before in Wedge... Since I never used it. Oh, and inherited skins also use slightly different styles for slogans. Diversity is good. (index.css, Wine/index.css, Warm/index.css, Wuthering/index.css)
* Finally committing the CSS part of the select box arrow rewrite. As I said, it's pretty cool as it's a triangle. In CSS. (index.css)
* A few minor changes (at pixel level). (index.css)
* Changed windowbg colors in Warm because I always hated them. Reused those from Wine... (Warm/index.css)
* Wuthering looks best with the bright version of the logo. (Wuthering/index.css)
* Rewrote some variables. $menu_bg is renamed to $menu_gradient, IE 6/7/8 didn't need a fallback in the variable because long ago I restored it in the CSS itself to ensure the menu wouldn't be broken on obscure browsers. Cleaned up the variable list in Wine, because it was pretty much a duplicate of Weaving's... (index.css, Wine/index.css)
! Fixed margins when showing the auto-saved draft message. At least when you're using a larger resolution and can see the entire thing in a single line, it looks better now. (editor.css)
! Fixed .two-columns maximum width on IE 6/7/8/9. Can you spot the difference? Yeah, they all require different widths, ah ah... Gotta love IE. (index.ie*.css)
! Fixed thought list hovers in IE6. Hopefully. You want me to waste time checking that it works..?! (index.ie6.css)
(10 files, 4kb) (that sounds small for such a large amount of changes to the CSS files...)
* Moved .two-columns and .upshrinks further up the CSS chain, so that it can safely be inherited. (index.css, sections.css)
* Slogan styling redone entirely. Instead of being shown on the right with some random font, it's now shown just after the website title, in the same font, slightly resized and recolored. Required quite a lot of CSS relative to what it does in the end, but it was required because #siteslogan was never really styled before in Wedge... Since I never used it. Oh, and inherited skins also use slightly different styles for slogans. Diversity is good. (index.css, Wine/index.css, Warm/index.css, Wuthering/index.css)
* Finally committing the CSS part of the select box arrow rewrite. As I said, it's pretty cool as it's a triangle. In CSS. (index.css)
* A few minor changes (at pixel level). (index.css)
* Changed windowbg colors in Warm because I always hated them. Reused those from Wine... (Warm/index.css)
* Wuthering looks best with the bright version of the logo. (Wuthering/index.css)
* Rewrote some variables. $menu_bg is renamed to $menu_gradient, IE 6/7/8 didn't need a fallback in the variable because long ago I restored it in the CSS itself to ensure the menu wouldn't be broken on obscure browsers. Cleaned up the variable list in Wine, because it was pretty much a duplicate of Weaving's... (index.css, Wine/index.css)
! Fixed margins when showing the auto-saved draft message. At least when you're using a larger resolution and can see the entire thing in a single line, it looks better now. (editor.css)
! Fixed .two-columns maximum width on IE 6/7/8/9. Can you spot the difference? Yeah, they all require different widths, ah ah... Gotta love IE. (index.ie*.css)
! Fixed thought list hovers in IE6. Hopefully. You want me to waste time checking that it works..?! (index.ie6.css)
5897
Archived fixes / [Bug?] Re: Layout problem with long titles
« on March 22nd, 2012, 12:37 PM »
I'd just like to point out that because the parent container is a display:table, max-width doesn't seem to work on it. And doing max-width on the h5 itself will restrain it to half of the container's width -- and said container isn't 100% of the width, so it's more like to make the final h5 take only 25% of the entire width...
5898
Archived fixes / Re: Preparsing adds url bbc where it shouldn't
« on March 22nd, 2012, 12:35 PM »
Then how come Wedge.org did it back when we were using SMF on it...? :-/
5899
Archived fixes / Re: IE8: menu broken (with fix)
« on March 22nd, 2012, 12:31 PM »
I can assure you that IE9 in IE8 mode (in Windows 7) doesn't have this problem...
The only odd/amusing thing is the extra gradient on the menu bar itself. It shouldn't be there... Probably due to a quick hack to provide the gradient in the first place (since IE6-9 all require some filter:gradient crap...)
The only odd/amusing thing is the extra gradient on the menu bar itself. It shouldn't be there... Probably due to a quick hack to provide the gradient in the first place (since IE6-9 all require some filter:gradient crap...)
5900
Features: Posts & Topics / Re: Likes
« on March 22nd, 2012, 12:29 PM »
Sure, but I'd rather we have a clean codebase to begin with... :lol:
5901
Archived fixes / Re: Preparsing adds url bbc where it shouldn't
« on March 22nd, 2012, 12:27 PM »
Oh... Very interesting. I put the extract inside nobbc and tt tags.
Believe it or not -- Wedge added the extra layer of url tags by itself. Didn't edit or anything! So, in the database, there's only one url tag. Just to make it clear...
:edit: Just in case, I tried to re-do it, same again. Even before the auto-save kicked in.
Believe it or not -- Wedge added the extra layer of url tags by itself. Didn't edit or anything! So, in the database, there's only one url tag. Just to make it clear...
:edit: Just in case, I tried to re-do it, same again. Even before the auto-save kicked in.
5902
Archived fixes / Re: Preparsing adds url bbc where it shouldn't
« on March 22nd, 2012, 12:26 PM »
I've just had a look at the database. Post #270447. It has a full link inside a quote. Something pretty much like what's broken these days...
Here's the part in the field: It's that film: [url][url]http://www.imdb.com/title/tt0079474/[/url][/url]
Meaning that the database DOES record the url tag in it. Which I find perfectly normal.
So the problem happens when importing the message at quote or quick edit time, right..?
I don't know if you'd gone as far as this in your research, I just wanted to post my results.
Here's the part in the field: It's that film: [url][url]http://www.imdb.com/title/tt0079474/[/url][/url]
Meaning that the database DOES record the url tag in it. Which I find perfectly normal.
So the problem happens when importing the message at quote or quick edit time, right..?
I don't know if you'd gone as far as this in your research, I just wanted to post my results.
5903
Features: Posts & Topics / Re: Likes
« on March 22nd, 2012, 12:22 PM »
Oh, just wanted to be sure... Likes are associated to a post ID, right? So, if we merge or split a topic, Likes are kept everytime?
(I'm 99% positive it's yes, but I would be mad at myself for not making sure of it.)
Also, it may be possible that I forgot to deal with parent posts when splitting and merging topics. That, I'm 40% positive I dealt with them...
Not that it matters much for now (we're not using that field), but it may in the future...
(I'm 99% positive it's yes, but I would be mad at myself for not making sure of it.)
Also, it may be possible that I forgot to deal with parent posts when splitting and merging topics. That, I'm 40% positive I dealt with them...
Not that it matters much for now (we're not using that field), but it may in the future...
5904
Features / Re: New revs
« on March 22nd, 2012, 12:06 PM »
rev 1497
(2 files, 3kb)
* Added another exception to 404 errors: iOS requesting for an apple-touch-icon file, to use as a big icon if you ever bookmark a website to your 'desktop'. Since I don't think many people are providing that, it's best to just ignore it... (QueryString.php)
! Clicking the menu position's Toggle button would sometimes generate an error if Pretty URLs are enabled. (Subs-Menu.php)
(2 files, 3kb)
* Added another exception to 404 errors: iOS requesting for an apple-touch-icon file, to use as a big icon if you ever bookmark a website to your 'desktop'. Since I don't think many people are providing that, it's best to just ignore it... (QueryString.php)
! Clicking the menu position's Toggle button would sometimes generate an error if Pretty URLs are enabled. (Subs-Menu.php)
5905
Features / Re: New revs
« on March 22nd, 2012, 11:59 AM »
rev 1496
(1 file, 4kb)
+ Woohoo. Been wanting to do that one for a long time... Now, WeCSS will accept selector lists after the @remove command. Also accepts "@remove from ..." but you can skip the 'from', it's just for convenience. Will take comma-separated lists of selectors, surrounded by double quotes or not, or just a single selector, or even -- let's be crazy -- no selector at all, like before. Basically, if you don't specify a selector, the line will be removed everywhere it's found in the CSS files. If you specify a selector (or more), it will be removed everywhere the selector is declared, including places where the selector inherits or is inherited. Tested on a few items, works fine. I'm sure someone will find a way to break it soon enough, but give me some time to rejoice. Thank you. (Class-CSS.php)
(1 file, 4kb)
+ Woohoo. Been wanting to do that one for a long time... Now, WeCSS will accept selector lists after the @remove command. Also accepts "@remove from ..." but you can skip the 'from', it's just for convenience. Will take comma-separated lists of selectors, surrounded by double quotes or not, or just a single selector, or even -- let's be crazy -- no selector at all, like before. Basically, if you don't specify a selector, the line will be removed everywhere it's found in the CSS files. If you specify a selector (or more), it will be removed everywhere the selector is declared, including places where the selector inherits or is inherited. Tested on a few items, works fine. I'm sure someone will find a way to break it soon enough, but give me some time to rejoice. Thank you. (Class-CSS.php)
5906
Features / Re: New revs
« on March 22nd, 2012, 09:17 AM »
rev 1495
(3 files, 1kb)
! If the Media area is disabled, the Media menu in profiles should be disabled entirely. (Profile.php)
! Added a $section['id'] check in sidebar menus, just like in dropdown menus. This fixes the Media area bug we met on Wedge.org, although the fix above is cleaner. (GenericMenu.template.php)
* Translation tweak. (index.french.php)
(3 files, 1kb)
! If the Media area is disabled, the Media menu in profiles should be disabled entirely. (Profile.php)
! Added a $section['id'] check in sidebar menus, just like in dropdown menus. This fixes the Media area bug we met on Wedge.org, although the fix above is cleaner. (GenericMenu.template.php)
* Translation tweak. (index.french.php)
5907
Features: Posts & Topics / Re: Likes
« on March 22nd, 2012, 09:08 AM »
If we didn't, at least I consider we did ;)
5908
Features / Re: Available importers (was: I'm in love all over again)
« on March 22nd, 2012, 08:48 AM »
There are two schools of thought about that ;)
I tend to be in yours.
I tend to be in yours.
5909
Off-topic / Re: The browser you loved to hate
« on March 22nd, 2012, 08:04 AM »
Definitely.
The more I spend time on CSS and HTML and JS stuff, the less time I devote to IE7 compatibility. As for IE6 -- I had a period during which I was adamant in keeping compatibility with IE6, even went as far as using a rounded corner shim for IE6 (look at the PIE library's forum, there's a long topic with a few bug reports/fixes by yours truly :P). Then, one day, I just figured, we're no longer in 2010, let's ditch that. And now it's 2012, and I no longer care that it even looks *okay* on IE6. Let it rot, let it look horrible. We all have to chip in and ensure IE6 users finally upgrade.
The more I spend time on CSS and HTML and JS stuff, the less time I devote to IE7 compatibility. As for IE6 -- I had a period during which I was adamant in keeping compatibility with IE6, even went as far as using a rounded corner shim for IE6 (look at the PIE library's forum, there's a long topic with a few bug reports/fixes by yours truly :P). Then, one day, I just figured, we're no longer in 2010, let's ditch that. And now it's 2012, and I no longer care that it even looks *okay* on IE6. Let it rot, let it look horrible. We all have to chip in and ensure IE6 users finally upgrade.
5910
Features / Re : Available importers (was: I'm in love all over again)
« on March 22nd, 2012, 08:00 AM »
The following modules are being developed in the converted:
- SMF 1.1 to Wedge
- SMF 2.0 to Wedge
- phpBB 3 to Wedge
- Burning Board 3.1 to Wedge
- vBulletin 4 to Wedge
- MyBB 1.6 to Wedge
- WordPress 3 (!!) to Wedge
Except for the SMF 2.0 importer which I personally stress-tested (and unfortunately discovered some minor bugs after we went live with the Wedge makeover :P), they're all relatively untested.
Considering that there are many import scripts for SMF 2.0, anyone can simply attempt to update their AverageShmuck forum to an SMF 2.0 forum to a Wedge 0.1 forum. :)
- SMF 1.1 to Wedge
- SMF 2.0 to Wedge
- phpBB 3 to Wedge
- Burning Board 3.1 to Wedge
- vBulletin 4 to Wedge
- MyBB 1.6 to Wedge
- WordPress 3 (!!) to Wedge
Except for the SMF 2.0 importer which I personally stress-tested (and unfortunately discovered some minor bugs after we went live with the Wedge makeover :P), they're all relatively untested.
Considering that there are many import scripts for SMF 2.0, anyone can simply attempt to update their AverageShmuck forum to an SMF 2.0 forum to a Wedge 0.1 forum. :)