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.
9211
Features / Re: New revs
« on April 22nd, 2011, 10:00 AM »
Dammit... The SVN server is down. >_< (http://status.repositoryhosting.com)
I'll still post the full changelog. I took time to write it, and I just need to do the proper commit operation. I'll do it tomorrow if it's back online.
rev 730
(30 files +1-1, 75kb)
! A couple of fixes in the Help action to make it possible to use blocks inside text strings... Although I'm not using any in the end. (Help.php, Load.php, Help.template.php, index.css)
! Pages without chrome shouldn't be able to restyle the content block, as this one usually contains data connected to the sidebar block. Temp fix. (Subs.php)
* Seriously reworked the internals of the album page layout. Too much to say, but it's basically better. (Subs-Media.php)
* Making sure that the media.js file is always loaded when media headers are requested. This is a temp solution because this file will end up being merged with script.js, given its small size... (Subs-Media.php)
! Prevent a same JS file from being cached multiple times. (Subs-Cache.php)
* The media tag helper page should say what it's about to begin with... (Help.language.php)
+ Added footer, class and style parameters to <we:block>. Note to self: maybe this should be a generic parameter that can be set in an easier way...? (index.template.php)
! Moved delayed events to the very bottom, in case some of them are calling functions that are defined by stylings. (index.template.php)
* Completely overhauled the media item page layout. And guess what, I'm not happy with it... A small list of changes: turned tables into divs and lists, moved item to the left and item details to the right as a sidebar, aligned them similarly to a table (not tested in IE though), reordered details, and so on. (Media.template.php)
* Rewrote ajax_indicator in a simpler, jQuery-worthy way. (script.js)
- Merged media.js with script.js (media.js, Subs-Media.php, Aeva-Gallery.php)
+ Click the "Loading" indicator in media pages to cancel the load request. (zoomedia.js)
+ Added an alternative white background for Zoomedia boxes. Use the 'black' class on the zoom div to use the earlier one. (zoom.css)
* Moved most inheritable classes to their own section and added a new class that holds the loader icon. (index.css)
* Replaced Ajax indicator's close button with the loader icon. It can still be clicked to cancel the action... (index.css)
! Fixed checkbox/radio button styling in IE6. And yes, it's a bit hackish... (index.css, index.ie6.css, settings.xml)
! Fixed outdated block redefinitions in Wuthering. (settings.xml)
* Improved styling of the <we:block> blocks. (media.css)
* Rewrote media area CSS files to use the wecss formatting style. (media.*.css, zoom.css, up.css)
+ Added ie6hover.js script, which transparently makes IE6 accepts hover states on any given selector. (settings.xml, ie6hover.js)
! Fixed PNG transparency for IE6 in media area, which was broken in some specific cases due to weird markup. (Subs-Media.php, settings.xml)
- Removed aeva_header class and galurl JS variable. (Aeva-Foxy.php, Aeva-Gallery2.php, ManageMedia.php, media-admin.js)
Committed.
I'll still post the full changelog. I took time to write it, and I just need to do the proper commit operation. I'll do it tomorrow if it's back online.
rev 730
(30 files +1-1, 75kb)
! A couple of fixes in the Help action to make it possible to use blocks inside text strings... Although I'm not using any in the end. (Help.php, Load.php, Help.template.php, index.css)
! Pages without chrome shouldn't be able to restyle the content block, as this one usually contains data connected to the sidebar block. Temp fix. (Subs.php)
* Seriously reworked the internals of the album page layout. Too much to say, but it's basically better. (Subs-Media.php)
* Making sure that the media.js file is always loaded when media headers are requested. This is a temp solution because this file will end up being merged with script.js, given its small size... (Subs-Media.php)
! Prevent a same JS file from being cached multiple times. (Subs-Cache.php)
* The media tag helper page should say what it's about to begin with... (Help.language.php)
+ Added footer, class and style parameters to <we:block>. Note to self: maybe this should be a generic parameter that can be set in an easier way...? (index.template.php)
! Moved delayed events to the very bottom, in case some of them are calling functions that are defined by stylings. (index.template.php)
* Completely overhauled the media item page layout. And guess what, I'm not happy with it... A small list of changes: turned tables into divs and lists, moved item to the left and item details to the right as a sidebar, aligned them similarly to a table (not tested in IE though), reordered details, and so on. (Media.template.php)
* Rewrote ajax_indicator in a simpler, jQuery-worthy way. (script.js)
- Merged media.js with script.js (media.js, Subs-Media.php, Aeva-Gallery.php)
+ Click the "Loading" indicator in media pages to cancel the load request. (zoomedia.js)
+ Added an alternative white background for Zoomedia boxes. Use the 'black' class on the zoom div to use the earlier one. (zoom.css)
* Moved most inheritable classes to their own section and added a new class that holds the loader icon. (index.css)
* Replaced Ajax indicator's close button with the loader icon. It can still be clicked to cancel the action... (index.css)
! Fixed checkbox/radio button styling in IE6. And yes, it's a bit hackish... (index.css, index.ie6.css, settings.xml)
! Fixed outdated block redefinitions in Wuthering. (settings.xml)
* Improved styling of the <we:block> blocks. (media.css)
* Rewrote media area CSS files to use the wecss formatting style. (media.*.css, zoom.css, up.css)
+ Added ie6hover.js script, which transparently makes IE6 accepts hover states on any given selector. (settings.xml, ie6hover.js)
! Fixed PNG transparency for IE6 in media area, which was broken in some specific cases due to weird markup. (Subs-Media.php, settings.xml)
- Removed aeva_header class and galurl JS variable. (Aeva-Foxy.php, Aeva-Gallery2.php, ManageMedia.php, media-admin.js)
Posted: April 21st, 2011, 11:55 PM
Committed.
9213
Archived fixes / [FAQ] Re: Why isn't wedge.org running Wedge?
« on April 21st, 2011, 12:10 AM »
We're providing choices where we feel it can be helpful.
For instance, the caching system in Wedge can use 9 different settings (no compression, compress with JSMin, compress with a customized Packer / local jQuery, jQuery at jQuery CDN, jQuery at Google CDN, maybe at Microsoft not sure, and 3² = 9). Things like that can be useful (even to me for debugging purposes)... But modifying a post layout is more of a styling's or a plugin's job to me. I'm trying to move as much as possible into these really.
For instance, the caching system in Wedge can use 9 different settings (no compression, compress with JSMin, compress with a customized Packer / local jQuery, jQuery at jQuery CDN, jQuery at Google CDN, maybe at Microsoft not sure, and 3² = 9). Things like that can be useful (even to me for debugging purposes)... But modifying a post layout is more of a styling's or a plugin's job to me. I'm trying to move as much as possible into these really.
9214
Archived fixes / [FAQ] Re: Why isn't wedge.org running Wedge?
« on April 20th, 2011, 10:44 PM »
Too many options = confusion and illusion of bloat...
9215
Archived fixes / [FAQ] Re: Why isn't wedge.org running Wedge?
« on April 20th, 2011, 09:46 PM »
I don't know... Apart from threading, we could simply add a small icon next to the post, redirecting to the parent post. Which could be useful if one replied to a post and then deleted all of the quotes...
Then again, you'd usually do that through Quick Reply. And of course it's not possible to get a parent ID for those... (Except, of course, if there's only one post in the topic so far.)
Then again, you'd usually do that through Quick Reply. And of course it's not possible to get a parent ID for those... (Except, of course, if there's only one post in the topic so far.)
9216
you're entirely relying on that third party never to change their API,
And that's the simpliest of APIs :lol:
9217
Archived fixes / [FAQ] Re: Why isn't wedge.org running Wedge?
« on April 20th, 2011, 05:24 PM »
Noisen always stores the title, whether it's repeated or not. It's pretty much mandatory if you want to make it work elsewhere (message search, etc.)
BTW... At some point we should also determine whether we record parent messages IDs for posts. (Even if we don't use them, of course.)
BTW... At some point we should also determine whether we record parent messages IDs for posts. (Even if we don't use them, of course.)
9218
Archived fixes / [FAQ] Re: Why isn't wedge.org running Wedge?
« on April 20th, 2011, 03:41 PM »
Yes...
OP: Some Topic
Reply 1: Re: Some Topic
Reply 2: Another Topic Entirely
Reply 3: Re: Another Topic Entirely
Solution 1:
OP: Some Topic
Reply 1:
Reply 2: Another Topic Entirely
Reply 3:
Solution 2:
OP: Some Topic
Reply 1:
Reply 2: Another Topic Entirely
Reply 3: Re: Another Topic Entirely
Which would be best...?
OP: Some Topic
Reply 1: Re: Some Topic
Reply 2: Another Topic Entirely
Reply 3: Re: Another Topic Entirely
Solution 1:
OP: Some Topic
Reply 1:
Reply 2: Another Topic Entirely
Reply 3:
Solution 2:
OP: Some Topic
Reply 1:
Reply 2: Another Topic Entirely
Reply 3: Re: Another Topic Entirely
Which would be best...?
9219
Archived fixes / [FAQ] Re: Why isn't wedge.org running Wedge?
« on April 20th, 2011, 03:28 PM »
Yeah.
Plus, it's a waste of bandwidth to show the same title every single time... And it encourages users not to change the title because people just won't notice -- whereas when it's shown only when changed, it just becomes obvious.
Here's me wondering what should be the behavior for Re: posts where the Re: contents is the changed title. If we assume that all Re: posts should have their title hidden, it gives more real estate, but also fails to convey the fact that an entire derivative conversation is taking place. I think I'd rather hide Re: titles only when they're the same as the first post's. It might encourage moderators to split topics when they see that suddenly all of the posts are using a visible title...
Not sure yet.
Plus, it's a waste of bandwidth to show the same title every single time... And it encourages users not to change the title because people just won't notice -- whereas when it's shown only when changed, it just becomes obvious.
Here's me wondering what should be the behavior for Re: posts where the Re: contents is the changed title. If we assume that all Re: posts should have their title hidden, it gives more real estate, but also fails to convey the fact that an entire derivative conversation is taking place. I think I'd rather hide Re: titles only when they're the same as the first post's. It might encourage moderators to split topics when they see that suddenly all of the posts are using a visible title...
Not sure yet.
9220
Archived fixes / [FAQ] Re: Why isn't wedge.org running Wedge?
« on April 20th, 2011, 03:14 PM »
I did that years ago and never had a complain about it -- and I love it myself.
However, during that time, I had the opportunity to feel one major drawback to this system. (Well, it's the only one really.)
If you're switching to a tab that's right in the middle of a conversation, you really have to go look at the browser title bar to know what topic this is. Or go to the very bottom or very top of the topic. It's not... practical. Even after years of use, I still can't bring myself to look at the title bar... :^^;:
However, during that time, I had the opportunity to feel one major drawback to this system. (Well, it's the only one really.)
If you're switching to a tab that's right in the middle of a conversation, you really have to go look at the browser title bar to know what topic this is. Or go to the very bottom or very top of the topic. It's not... practical. Even after years of use, I still can't bring myself to look at the title bar... :^^;:
9221
Features / Re: Footnotes???
« on April 20th, 2011, 03:12 PM »
Done worse on Noisen, eheh... :niark:
9222
Features / Re: Footnotes???
« on April 20th, 2011, 12:35 PM »
I think I'm having a boner!!
(What I like about this word, is that it's an exact homonym of the French "bonheur", meaning "happiness" ;))
(What I like about this word, is that it's an exact homonym of the French "bonheur", meaning "happiness" ;))
9223
Archived fixes / [FAQ] Re: Why isn't wedge.org running Wedge?
« on April 20th, 2011, 12:33 PM »
...Which is exactly what is done at Noisen (just have a look at the patch I sent you months ago... :p)
9224
Archived fixes / [FAQ] Re: Why isn't wedge.org running Wedge?
« on April 20th, 2011, 10:52 AM »
The only thing I'm sure will be in Wedge is the reduced first line on each post...
Although I myself am wondering whether or not to remove the systematic title on every post... I think it's redundant because it's already in the page header, but OTOH sometimes it could be useful...
Although I myself am wondering whether or not to remove the systematic title on every post... I think it's redundant because it's already in the page header, but OTOH sometimes it could be useful...
9225
Plugins / Re: Plugin hooks
« on April 20th, 2011, 08:11 AM »Isn't defamation the SMF team ways as well? Didn't they use defamation to get you out of their way? :DQuote from Nao/Gilles on April 19th, 2011, 05:19 PM I will only resort to libel, slander and vilification to get someone out of my way. That's who I am. 8-)
I am aware that truth is an excuse for defamation, but lies are not. I know you don't lie. ;)
(Sorry, just watched that particularly funny episode of South Park yesterday :P)