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
4517
The Pub / Re: Getting ready for an alpha release: CSS fixes
« on September 7th, 2012, 07:31 AM »
Aaaaand... Skin updates are online I figured I'll fix Wine later :P). There are plenty of changes (menu arrows, fixed sub-skins...), hope you'll like them! The only issue I met is that menus are about 10% slower to show in Opera 12.5, but it's the only browser that's showing even a slowdown, so it's okay, it's not like I'm spending my days in there anyway...
Looking for feedback on 1024x768/1024x600 screens too... What do you think? They should have the sidebar now, unlike previous versions... Should I remove the sidebar for these widths?
Looking for feedback on 1024x768/1024x600 screens too... What do you think? They should have the sidebar now, unlike previous versions... Should I remove the sidebar for these widths?
4518
Features / Re: New revs
« on September 7th, 2012, 12:18 AM »
rev 1685
(5 files, 3kb)
+ Added WeCSS support for '!' character in selectors -- this is a new one from the CSS4 drafts, marking the subject (desired target) of the selector, our developer dreams come true (believe me.) (Class-CSS.php)
* Managed to harmonize the arrow size across all my test browsers (let's be clear: Opera, Firefox and some IE just to be sure), without increaing the filesize too much. (common.css, index.css)
! Magically found a workaround for menu text overlapping the arrows in IE9... Just needed to add overflow:hidden to the container. And it doesn't seem to break anything else. A little prayer maybe..? I'm sure that'll help. (index.css)
! Fixed plenty of problems with various IE versions in the Wuthering skin. Yeah, not my favorite skin, and not my favorite browser -- no wonder I didn't test that case thoroughly... (Wuthering/extra.css, Wuthering/extra.ie[-9].css)
(5 files, 3kb)
+ Added WeCSS support for '!' character in selectors -- this is a new one from the CSS4 drafts, marking the subject (desired target) of the selector, our developer dreams come true (believe me.) (Class-CSS.php)
* Managed to harmonize the arrow size across all my test browsers (let's be clear: Opera, Firefox and some IE just to be sure), without increaing the filesize too much. (common.css, index.css)
! Magically found a workaround for menu text overlapping the arrows in IE9... Just needed to add overflow:hidden to the container. And it doesn't seem to break anything else. A little prayer maybe..? I'm sure that'll help. (index.css)
! Fixed plenty of problems with various IE versions in the Wuthering skin. Yeah, not my favorite skin, and not my favorite browser -- no wonder I didn't test that case thoroughly... (Wuthering/extra.css, Wuthering/extra.ie[-9].css)
4519
Features / Re: New revs
« on September 6th, 2012, 04:21 PM »
rev 1684
(7 files, 9kb)
! Help popup titles were broken by the resizer code change. Don't ask -- don't tell. (Subs-Template.php)
! Fixed responsive mode on iOS. Yeah, contrary to popular belief, responsive isn't just for mobile... Otherwise it would be called mobile mode or something. (extra.iphone.css)
! Fixed responsive mode in sub-skins. (Warm/extra.css, Wuthering/extra.css)
* Overhauled parts of the menu CSS, mostly to simplify it. It worked. Also fixed anything in sub-skins due to the menu rewrite. (common.css, index.css, Warm/extra.css, Wuthering/extra.css)
(7 files, 9kb)
! Help popup titles were broken by the resizer code change. Don't ask -- don't tell. (Subs-Template.php)
! Fixed responsive mode on iOS. Yeah, contrary to popular belief, responsive isn't just for mobile... Otherwise it would be called mobile mode or something. (extra.iphone.css)
! Fixed responsive mode in sub-skins. (Warm/extra.css, Wuthering/extra.css)
* Overhauled parts of the menu CSS, mostly to simplify it. It worked. Also fixed anything in sub-skins due to the menu rewrite. (common.css, index.css, Warm/extra.css, Wuthering/extra.css)
4520
The Pub / Re: Logo Madness
« on September 6th, 2012, 02:34 PM »
What's odd is that I like it too, considering how cliché it is :P
4521
The Pub / Re: Logo Madness
« on September 6th, 2012, 11:42 AM »
Added another one, just in case...
4522
The Pub / Re: Logo Madness
« on September 6th, 2012, 07:13 AM »
It's the same as the others, only an horizontal version for sigs ;)
4523
The Pub / Re: Logo Madness
« on September 6th, 2012, 12:07 AM »
A few fun variations I made yesterday and today, sorted from latest to earliest... (One of these is in my sig currently, as can be seen.)
Some logos aren't very readable, sorry about that, didn't really test.
(And I'm not saying they're better than the current ones, either. I do like all of them :P)
Some logos aren't very readable, sorry about that, didn't really test.
Posted: September 6th, 2012, 12:03 AM
(And I'm not saying they're better than the current ones, either. I do like all of them :P)
4524
The Pub / Re: Getting ready for an alpha release: CSS fixes
« on September 5th, 2012, 11:58 PM »
Thankfully, I don't need anything, but even if -- I try not to rely on JS to support CSS if I can do without it.
Heck, CSS = presentation only, if it isn't supported, it'll just be ugly...
Cf. rev 1683.
Oh, and regarding arrow sizes -- actually this isn't due to the font size, but rather the fact that some browsers don't render certain UTF characters at the same size. Very odd. One solution is to change the arrow to use a different one -- it works, but it's too large, so I'd then have to set a font-size: 60% or something in the code. Which I didn't like much. I decided not to give a damn for now :P I've already spent way too much time on that particular rewrite...
PS: I'd like to fix Wine & co before I upload the changes to wedge.org.
Heck, CSS = presentation only, if it isn't supported, it'll just be ugly...
Cf. rev 1683.
Oh, and regarding arrow sizes -- actually this isn't due to the font size, but rather the fact that some browsers don't render certain UTF characters at the same size. Very odd. One solution is to change the arrow to use a different one -- it works, but it's too large, so I'd then have to set a font-size: 60% or something in the code. Which I didn't like much. I decided not to give a damn for now :P I've already spent way too much time on that particular rewrite...
PS: I'd like to fix Wine & co before I upload the changes to wedge.org.
4525
Features / Re: New revs
« on September 5th, 2012, 11:53 PM »
rev 1683 -- seriously hoping I didn't commit anything unneeded or undocumented...
(12 files -2, 12kb)
* Replaced arrow images (in linktree and menus) with CSS content. This saves a few dozen bytes at compression time, and is much, MUCH better in terms of code logic. For instance, we no longer need to add extra padding. Plus, there are two new classes (.vertical-arrow and .horizontal-arrow) and yes, they're re-usable. As usual, support is only provided for Weaving for now. (index.template.php, common.css, index.css,
- The extra.firefox[-3.6].css file in Wine was no longer needed, as the sidebar is now pushed to the bottom... (extra.firefox[-3.6].css)
- Removed a few IE6/7 hacks related to the arrows. Basically: nope, arrows no longer show up in these browsers... But I don't think it's worth wasting time (and bandwidth) trying to support these old browsers. (extra.ie6.css, extra.ie7.css, Wuthering/extra.ie6.css)
+ Added a nice radial gradient to IE9 menus. Actually, it's the only browser that seems to perform well with intensive inset box-shadows, so, for once, IE9 is going to look better than any other browser... (extra.ie9.css)
* Updated documentation in the index.css header to add the latest suffixes supported. (index.css)
! Fixed wrong CSS being generated if two @media keywords were used in a row. Hopefully that doesn't break anything else... This feature needs some serious checking. (Class-CSS.php)
* Translation. (ManageSettings.french.php)
* Spacinazi. (Wireless/extra.iphone.css)
(12 files -2, 12kb)
* Replaced arrow images (in linktree and menus) with CSS content. This saves a few dozen bytes at compression time, and is much, MUCH better in terms of code logic. For instance, we no longer need to add extra padding. Plus, there are two new classes (.vertical-arrow and .horizontal-arrow) and yes, they're re-usable. As usual, support is only provided for Weaving for now. (index.template.php, common.css, index.css,
- The extra.firefox[-3.6].css file in Wine was no longer needed, as the sidebar is now pushed to the bottom... (extra.firefox[-3.6].css)
- Removed a few IE6/7 hacks related to the arrows. Basically: nope, arrows no longer show up in these browsers... But I don't think it's worth wasting time (and bandwidth) trying to support these old browsers. (extra.ie6.css, extra.ie7.css, Wuthering/extra.ie6.css)
+ Added a nice radial gradient to IE9 menus. Actually, it's the only browser that seems to perform well with intensive inset box-shadows, so, for once, IE9 is going to look better than any other browser... (extra.ie9.css)
* Updated documentation in the index.css header to add the latest suffixes supported. (index.css)
! Fixed wrong CSS being generated if two @media keywords were used in a row. Hopefully that doesn't break anything else... This feature needs some serious checking. (Class-CSS.php)
* Translation. (ManageSettings.french.php)
* Spacinazi. (Wireless/extra.iphone.css)
4526
The Pub / Re: Getting ready for an alpha release: CSS fixes
« on September 5th, 2012, 07:22 PM »
lol, the link didn't work on my iPod actually... It works in Opera. And I'm stunned, you linked precisely to a proposed fix for the issue I mentioned! I promise I didn't read that page :lol:
4527
The Pub / Re: Getting ready for an alpha release: CSS fixes
« on September 5th, 2012, 05:30 PM »I say go for x, but make a comment in the CSS so that people will know that JS witchcraft is being performed. Seems to me to be the least horrific way to go about things. If people have JS disabled it won't change too much, and if they have it enabled it won't be the end of the world.
CSS is so neat at most times, but can be oh so stupid for some things.
I think overall, WeCSS took me over 6 months to develop (1 month for the main code, 5+ months for bug fixes and improvements.) Had I known earlier, I probably would...have done it again. It's just that it isn't Wedge. It's just a cool part of it... But it's also the most invisible part to most people: with today's bandwidths, you don't really see a difference at load time (most of my time savers aren't related to WeCSS).
EDIT: http://www.w3.org/TR/selectors4/#subject <-- In five years we will all be telling new CSS users how lucky they are to have all the neat tools they currently have, and they will still whine that CSS is insufficient. It will be grand times
The only 'important' thing I feel that CSS is missing (and that is hardly targetable in WeCSS either), is "selector < subselector", i.e. "target any selector that has the specific subselector". That one would be so dead cool... And I don't care about performance issues, eh!
4528
The Pub / Re: Great start !
« on September 5th, 2012, 05:24 PM »I guess if developing software can be compared with cooking then adding new features is like baking bread or cakes, whereas fixing bugs is more like cleaning the oven.
Fixing bugs is simply like fixing some rice that you undercooked by adding a precise amount of hot water to it, praying that it'll start heating the rice again, and praying that nobody will notice it wasn't right from the start.
:eheh:
4529
The Pub / Re: Controversial idea: post moderation on by default
« on September 5th, 2012, 05:15 PM »The system has never been designed to flag users the way you have in mind, having users be flagged as being moderated, and I'm increasingly not a fan of unapproved as a concept.
Since the same rule relies on post count, and that moderated posts do not bump post count, this would work exactly as expected.
(And anyway, even if these posts did increase post count, 1 would be a suitable limit to me, if only because usually the very first post a spammer will send is a spam post... They usually don't stick around sending fake posts. It takes them too much time I guess.)
As for your point, that's one of the downsides to the moderation filters system is that there isn't a good way to display text to the user about whether their post will be moderated (or blocked) especially if one of the rules is something like "moderate if the post contains 'fuck'" (the other is having to reparse the moderation rules potentially every thread since even quick reply would need that too, and that's a big deal)
4530
The Pub / Re: Logo Madness
« on September 5th, 2012, 04:43 PM »
This is exactly what I talked about -- Lorenzo's thought is broken.
As I said, the blurb field is limited to 255 bytes, and thoughts are as well. However, if you start using bbcode and smileys in them, the resulting HTML is stored, not the thought text (to save time processing it), so it may happen that the thought gets broken precisely while inside a HTML tag, which happened here -- and because that tag is never closed, HTML5 layout processing leads to breaking the page as it does.
This is something that can easily be fixed by setting the blurb field to a smallint instead (64KB), but I'm sure Pete has something to say about it ;)
As I said, the blurb field is limited to 255 bytes, and thoughts are as well. However, if you start using bbcode and smileys in them, the resulting HTML is stored, not the thought text (to save time processing it), so it may happen that the thought gets broken precisely while inside a HTML tag, which happened here -- and because that tag is never closed, HTML5 layout processing leads to breaking the page as it does.
This is something that can easily be fixed by setting the blurb field to a smallint instead (64KB), but I'm sure Pete has something to say about it ;)