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.
8986
Features: Theming / JavaScript caching
« on May 10th, 2011, 06:43 PM »
Feature: JavaScript caching
Developer: Nao
Target: everyone
Status: 100% (believed to be complete.)
Comment:
Right after minifying your CSS and JS files, Wedge will cache them and gzip them. The good point is that it's smart enough to cache multiple files together, relieving the server a bit.
I'll use my script.js example again. At the time of writing, the regular script.js/theme.js duo is about 50KB in SMF2 (split over two files), less than 30KB in Wedge (with many extra functions in them), and the actual stuff you download is a single 6KB file, after minification and gzipping. Meanwhile in the wasteland, SMF2 still sends you 50KB of data. Because everyone knows all end-users absolutely need to have comments in the JavaScript code they execute.
Developer: Nao
Target: everyone
Status: 100% (believed to be complete.)
Comment:
Right after minifying your CSS and JS files, Wedge will cache them and gzip them. The good point is that it's smart enough to cache multiple files together, relieving the server a bit.
I'll use my script.js example again. At the time of writing, the regular script.js/theme.js duo is about 50KB in SMF2 (split over two files), less than 30KB in Wedge (with many extra functions in them), and the actual stuff you download is a single 6KB file, after minification and gzipping. Meanwhile in the wasteland, SMF2 still sends you 50KB of data. Because everyone knows all end-users absolutely need to have comments in the JavaScript code they execute.
8987
Features: Theming / CSS and JavaScript minification
« on May 10th, 2011, 06:43 PM »
Feature: CSS and JavaScript minification
Developer: Nao
Target: everyone
Status: 100% (believed to be complete.)
Comment:
Wedge likes bandwidth optimization. Wedge is sad when its pages don't show up immediately. Wedge is a good boy.
Whenever you upload a modified CSS/JS file to your styles or scripts folder, it will catch it, minify it on the fly and cache it.
Minification is a process that removes all comments, whitespace and things that aren't needed for the code to work. CSS is easy to minify, but JS is sometimes a bit capricious, so I added support for JSMin minification (the safe one), Packer 3.0 (the efficient one), and no minification at all (useful for debugging your scripts.)
We recommend using Packer, it's nearly as efficient as UglifyJS. A note to modders: just make sure your JavaScript passes JSLint validation, or at least you don't forget to add semi-colons at the end of var fn = function () { ... }; declarations, otherwise Packer will choke on it (it's fixable, but we'd rather not make the script slower because of lazy programmers.)
Developer: Nao
Target: everyone
Status: 100% (believed to be complete.)
Comment:
Wedge likes bandwidth optimization. Wedge is sad when its pages don't show up immediately. Wedge is a good boy.
Whenever you upload a modified CSS/JS file to your styles or scripts folder, it will catch it, minify it on the fly and cache it.
Minification is a process that removes all comments, whitespace and things that aren't needed for the code to work. CSS is easy to minify, but JS is sometimes a bit capricious, so I added support for JSMin minification (the safe one), Packer 3.0 (the efficient one), and no minification at all (useful for debugging your scripts.)
We recommend using Packer, it's nearly as efficient as UglifyJS. A note to modders: just make sure your JavaScript passes JSLint validation, or at least you don't forget to add semi-colons at the end of var fn = function () { ... }; declarations, otherwise Packer will choke on it (it's fixable, but we'd rather not make the script slower because of lazy programmers.)
8988
Other software / Re: SMF 2.0 final THIS MONTH?
« on May 10th, 2011, 06:30 PM »
Erm... Anyway, I don't believe a document could be nulled in courts just because it doesn't have pretty section numbers... (???)
8989
Other software / Re: SMF 2.0 final THIS MONTH?
« on May 10th, 2011, 05:29 PM »
Pete, I'd noticed about texasguy and I thought I wouldn't mention it because, errr, I wasn't sure whether it would a laughing matter, given how ridiculous this is :P
OTOH, it's just... What? 'Support helper of the month for a dying platform'? No wonder 60 posts are enough to get you the title... Plus, with you around, why would they need a support guy? And giving you the SHOTM title every month would be the equivalent of admitting they're in deep shit :P
OTOH, it's just... What? 'Support helper of the month for a dying platform'? No wonder 60 posts are enough to get you the title... Plus, with you around, why would they need a support guy? And giving you the SHOTM title every month would be the equivalent of admitting they're in deep shit :P
8990
Features / Re: New revs
« on May 10th, 2011, 12:38 PM »
rev 765
(7 files, 27kb)
* Massive rewrite for Zoomedia. (zoomedia.js, zoom.css)
* Starting position for zoom animation now matches exactly the origin thumbnail.
* Slightly reduced border size, as it was a bit too much for my taste.
* Descriptions no longer show up as overlays on the image. They also enlarge the zoomedia box if it's too narrow to hold the description.
+ Double-click the original thumbnail, or the opened preview, to enlarge it into the fullsize version. Includes annoying fix for IE 6/7/8.
! IE6 always showed the Loading label, even if the image was cached.
! Outside closing clicks were tested even with no zoomedia box opened. Ooops.
+ Added menu animation for low-level menu entries as well. (script.js)
- Removed useless 'added' parameter from sitelist. (ManageMedia3.php, Subs-Aeva-Sites.php)
- Removed hss() as full zoom handler. This is now done entirely by Zoomedia. (Aeva-Subs-Vital.php, Subs-Media.php)
Zoomedia tested under IE6, IE7, IE8 and Opera 11.50... Haven't tested in Chrome for a few days but it should work.
(7 files, 27kb)
* Massive rewrite for Zoomedia. (zoomedia.js, zoom.css)
* Starting position for zoom animation now matches exactly the origin thumbnail.
* Slightly reduced border size, as it was a bit too much for my taste.
* Descriptions no longer show up as overlays on the image. They also enlarge the zoomedia box if it's too narrow to hold the description.
+ Double-click the original thumbnail, or the opened preview, to enlarge it into the fullsize version. Includes annoying fix for IE 6/7/8.
! IE6 always showed the Loading label, even if the image was cached.
! Outside closing clicks were tested even with no zoomedia box opened. Ooops.
+ Added menu animation for low-level menu entries as well. (script.js)
- Removed useless 'added' parameter from sitelist. (ManageMedia3.php, Subs-Aeva-Sites.php)
- Removed hss() as full zoom handler. This is now done entirely by Zoomedia. (Aeva-Subs-Vital.php, Subs-Media.php)
Zoomedia tested under IE6, IE7, IE8 and Opera 11.50... Haven't tested in Chrome for a few days but it should work.
8991
Other software / Re: SMF 2.0 final THIS MONTH?
« on May 10th, 2011, 10:07 AM »And those buttons... eeeewwwwwww! Something tells me Ante was at work.
And their top margin needs increased. Actually, he original square SMF buttons would look so much better too.
Re: team page, I didn't realize it was on the front page... It's becoming obvious that they have two different sidebars for the About section. One has the Team page, the other has the NPO page. The Team page no longer has a marketing section, so Kindred isn't in it... The NPO page no longer has Friends, but JBlaze is in it even though he's a 'Friend' in the Team page.
8992
Features: Miscellaneous / Re: Per-board Languages and Language flags
« on May 10th, 2011, 10:02 AM »
For now, we'll have to let translators rely on diff tools... Maybe we could generate a diff of the language files ourselves, at least to determine the amount of data that changed.
8993
Other software / Re: SMF 2.0 final THIS MONTH?
« on May 10th, 2011, 12:02 AM »Actually, if you read the bylaws, anyone who is a team member, or has recently been, the dues are waived in consideration of services rendered.
Honestly, though, this is the final nail in the coffin in terms of "we value our friends" because it seems to me that they don't, and now they have the balls to admit it.
AeMe is not subject to the SMF licence, it just isn't a problem.
As far as code review goes, I'm interested in ensuring that their code does not affect us.
I have an hour or so,
G'night!
8994
Other software / Re: SMF 2.0 final THIS MONTH?
« on May 9th, 2011, 11:53 PM »So, the transfer seems to be complete; the team has now published the NPO bylaws,
Seriously, that's long, legal mumbo-jumbo and it's even got typos...
the trademark guidelines and a bunch of other stuff - like a new front page.
They also publish their CLA now.
And they removed their team page -- and replaced it with an NPO team page where they list the board members. Interestingly, it seems to imply Kindred is the boss now... Even though he resigned some time ago :P
Also, all SMF Friends are gone -- you're no longer on the list. Instead they list all NPO subscribers, including some very recent members like Illori. Here's wondering if they actually paid the $50 mentioned in the NPO bylaws...
I think we can safely say that it's going to emerge on schedule, then, which means we have an interesting few weeks ahead while we merge in the remaining changes, and making sure code is fully compliant (because I am damned if I'm going to let anyone pull a C&D out) then we can proceed as we see fit. But I will do a code review once 2.0 final lands to ensure that the codebase is free of any issues after that, so that we can finally cut loose.
Also, what about our CLA? You're in charge, man, you deal with it :niark:
8995
Off-topic / Re: Site slogan conflicting with JS
« on May 9th, 2011, 09:57 PM »
FBConnect, isn't that Dragooon's?
8996
Features / Re: New revs
« on May 9th, 2011, 09:56 PM »
rev 764
(4 files +1, 97kb)
* Updated credits with missing names. (Credits.php)
! Replaced main jQuery 1.6 calls with version 1.5.2 instead. Waiting for 1.6.1 with the fix to $.offset() (Load.php, jquery-1.5.2.js)
+ Added minor but nice animation to the menu system. It's just two lines... Can be reverted easily. (script.js)
* Post font spacing was one pixel too big for my taste. (index.css)
* Fixed menu border color and made them slightly less transparent. We got it, it's transparent, it's cool. It should be readable, too. (index.css)
(4 files +1, 97kb)
* Updated credits with missing names. (Credits.php)
! Replaced main jQuery 1.6 calls with version 1.5.2 instead. Waiting for 1.6.1 with the fix to $.offset() (Load.php, jquery-1.5.2.js)
+ Added minor but nice animation to the menu system. It's just two lines... Can be reverted easily. (script.js)
* Post font spacing was one pixel too big for my taste. (index.css)
* Fixed menu border color and made them slightly less transparent. We got it, it's transparent, it's cool. It should be readable, too. (index.css)
8997
Features: Posts & Topics / Re: Merge Double Posts
« on May 9th, 2011, 08:29 PM »
There are three merge mods that I know of:
- Pete's
- An Italian modder's (I posted on his topic a lot at the time)
- Din1031's mod, which he gave up to me. I never released it officially as a mod for SMF, but my own rewrite is to be found in Wedge.
- Pete's
- An Italian modder's (I posted on his topic a lot at the time)
- Din1031's mod, which he gave up to me. I never released it officially as a mod for SMF, but my own rewrite is to be found in Wedge.
8998
Features: Posts & Topics / Re: Previous/next topics
« on May 9th, 2011, 08:27 PM »(far more so than the prev/next links SMF comes with)
8999
Features: Theming / Template macros
« on May 9th, 2011, 06:36 PM »
Feature: Macros
Developer: Nao
Target: themers, users
Status: 95% (believed to be complete. May need to add features later)
Comment:
Wedge allows skins to define macros in the index template, i.e. blocks of HTML code that you can customize on the fly. You can then call them through <we:yourmacro yourparams="...">Your body</we:youmacro> in all templates. Skins can then override these macros easily.
You can set macros conditionally, i.e. have a macro show up only for members or guests, have another macro show in a certain way to IE6 users and another way to users of other browsers, etc. It's pretty powerful all in all.
Macros available at press time: category, title and title2 headers, block (regular box with optional header and footer), and various wrappers needed for proper sidebar handling.
Developer: Nao
Target: themers, users
Status: 95% (believed to be complete. May need to add features later)
Comment:
Wedge allows skins to define macros in the index template, i.e. blocks of HTML code that you can customize on the fly. You can then call them through <we:yourmacro yourparams="...">Your body</we:youmacro> in all templates. Skins can then override these macros easily.
You can set macros conditionally, i.e. have a macro show up only for members or guests, have another macro show in a certain way to IE6 users and another way to users of other browsers, etc. It's pretty powerful all in all.
Macros available at press time: category, title and title2 headers, block (regular box with optional header and footer), and various wrappers needed for proper sidebar handling.
9000
Features: Theming / Skins
« on May 9th, 2011, 06:35 PM »
Feature: Skins (previously 'stylings')
Developer: Nao
Target: everyone (mainly themers)
Status: 95% (believed to be complete; but I added so many features since then... It's probably going to evolve even more.)
Comment:
Skins are Wedge's answer to SMF's CSS variants.
The theme folder's "css" folder is now a "skins" folder with a nested structure. It is one of the most complex new features in Wedge, so it's difficult to describe it thoroughly in a single paragraph. I'll write some proper documentation when the time comes.
In the meantime, just know this: a skin can totally redefine most aspects of a theme without any code modding. Replace or add to the current stylesheets, add jQuery code or remote JavaScript files, rewrite template macros, and optionally set these only for specific browsers. Most importantly, skins allow you to redefine the structure of the template skeleton, which is Wedge's way of handling what SMF called 'template layers' and 'sub-templates' in a way that actually makes sense for designers.
You can also customize the current CSS yourself (add a custom.css file to the skin), or create new skins that inherit (or completely replace) settings from their 'parent' skins. Choose a default skin for guests, play with inheritance by physically moving folders... Themers can expect a lot of fun playing with Wedge.
Developer: Nao
Target: everyone (mainly themers)
Status: 95% (believed to be complete; but I added so many features since then... It's probably going to evolve even more.)
Comment:
Skins are Wedge's answer to SMF's CSS variants.
The theme folder's "css" folder is now a "skins" folder with a nested structure. It is one of the most complex new features in Wedge, so it's difficult to describe it thoroughly in a single paragraph. I'll write some proper documentation when the time comes.
In the meantime, just know this: a skin can totally redefine most aspects of a theme without any code modding. Replace or add to the current stylesheets, add jQuery code or remote JavaScript files, rewrite template macros, and optionally set these only for specific browsers. Most importantly, skins allow you to redefine the structure of the template skeleton, which is Wedge's way of handling what SMF called 'template layers' and 'sub-templates' in a way that actually makes sense for designers.
You can also customize the current CSS yourself (add a custom.css file to the skin), or create new skins that inherit (or completely replace) settings from their 'parent' skins. Choose a default skin for guests, play with inheritance by physically moving folders... Themers can expect a lot of fun playing with Wedge.