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
8626
Development blog / New directions
« on June 21st, 2011, 08:19 PM »
Glee! Joy! Wedge!
So, SMF 2.0 Final is out, eh?
Fantastic.
Now we're a 100% legal project. Anyone can do exactly what we're doing. Except that we're starting to know the drill -- it's been 10 months already since we started work on our custom forum system.
Obviously, we can't wait to be ready to release it. We want feedback, we want excitement, we want glee. We want to finally be able to show what we mean when we say we're going to do things differently. We're no longer linked to SMF, imagination is the limit. Well, and our lifespans, I guess. Pete and I have been plagued with real-life commitments and issues these last few months, so progress is slowing down -- but when I say it's slowing down, I mean we're only adding features slowly. Not stalling for 3 years without doing a thing, if you know what I mean.
Myself, among other things, I had to go through the death of the beloved, glorious PC I built in 2005. For the first time in ten years I've had to reinstall Windows and reset my entire development environment. It's tough, but it's something that has to happen once in a while. Although, if my PC had waited a couple more days to die on me, I'd have finished my big yearly backup... Ah, fun times.
So, now I'm back up. My driving license exam is coming this week, hopefully I won't fail it, and I'll be able to focus entirely on Wedge once again!
So, SMF 2.0 Final is out, eh?
Fantastic.
Now we're a 100% legal project. Anyone can do exactly what we're doing. Except that we're starting to know the drill -- it's been 10 months already since we started work on our custom forum system.
Obviously, we can't wait to be ready to release it. We want feedback, we want excitement, we want glee. We want to finally be able to show what we mean when we say we're going to do things differently. We're no longer linked to SMF, imagination is the limit. Well, and our lifespans, I guess. Pete and I have been plagued with real-life commitments and issues these last few months, so progress is slowing down -- but when I say it's slowing down, I mean we're only adding features slowly. Not stalling for 3 years without doing a thing, if you know what I mean.
Myself, among other things, I had to go through the death of the beloved, glorious PC I built in 2005. For the first time in ten years I've had to reinstall Windows and reset my entire development environment. It's tough, but it's something that has to happen once in a while. Although, if my PC had waited a couple more days to die on me, I'd have finished my big yearly backup... Ah, fun times.
So, now I'm back up. My driving license exam is coming this week, hopefully I won't fail it, and I'll be able to focus entirely on Wedge once again!
8627
Off-topic / Re: Salary in web development
« on June 21st, 2011, 08:02 PM »
Depends on plenty of things...
I don't have any diploma (except the basic Baccalauréat), and I actually gave up on uni (Japanese language studies) after I found a job as a translator. My belief is that the best diploma is a full curriculum vitae. Although you probably can't expect as high a salary if you don't have a diploma -- but then again, it makes it even more likely for you to get the job in the first place.
I don't have any diploma (except the basic Baccalauréat), and I actually gave up on uni (Japanese language studies) after I found a job as a translator. My belief is that the best diploma is a full curriculum vitae. Although you probably can't expect as high a salary if you don't have a diploma -- but then again, it makes it even more likely for you to get the job in the first place.
8628
The Pub / Re: Interesting site
« on June 21st, 2011, 08:00 PM »
My experience with blogs is that I'm the kind of guy who writes elaborate posts, and then stops posting altogether after a while for fear of posting less interesting stuff.... :^^;:
But I guess it doesn't hurt to try!
But I guess it doesn't hurt to try!
8629
Features / Re: New revs
« on June 21st, 2011, 07:50 PM »
rev 812
(32 files +2-2, 46kb)
- Removed support for rel="index" meta tags, as it's no longer part of the HTML5 standard. Also moved meta tags below all link tags, to ensure any external files are loaded as soon as possible. (index.template.php)
- Trimmed down external latest news. (other/xml/latest-news.php)
* Changed button strips to use a 'class' element rather than an 'active' boolean, avoiding validation errors when trying to add custom CSS classes. (Aeva-Gallery.php, Aeva-ModCP.php, MessageIndex.php, TEMPLATES: index, Display, Media, Memberlist, PersonalMessage, Recent, Reports)
* Some of my uncommitted layout changes are starting to make their way into the code... Without the stylesheets. Meh. Coming soon! (BoardIndexInfoCenter.template.php, Display.template.php)
* I just don't like seeing 5 lines of code that could look cool and fit on a single line... (Subs-Login.php)
* The default feed format is now Atom rather than RSS 1, and support for SMF (custom) and Webslice feeds has been removed because they've never been commonly used anyway. Media feeds remain in RSS 2 format for now. (Feed.php, BoardIndexInfoCenter.template.php, index.template.php, index.language.php)
* Renamed 'RSS' to 'Atom' or 'feeds'. (index.php, db_aeva.php, rss.png, Feed.php, Load.php, Aeva-Foxy.php, Aeva-Gallery.php, ManageMedia.php, Subs-Media.php, media.css, TEMPLATES: BoardIndex, BoardIndexInfoCenter, index, Media, LANGUAGES: Admin, Help, index, ManageMedia, Post, Stats, Who)
@ Note: I removed the mention about feeds in the Help file, because we're going to move it somewhere else... Let's just not forget to document it when it's done. ;)
(32 files +2-2, 46kb)
- Removed support for rel="index" meta tags, as it's no longer part of the HTML5 standard. Also moved meta tags below all link tags, to ensure any external files are loaded as soon as possible. (index.template.php)
- Trimmed down external latest news. (other/xml/latest-news.php)
* Changed button strips to use a 'class' element rather than an 'active' boolean, avoiding validation errors when trying to add custom CSS classes. (Aeva-Gallery.php, Aeva-ModCP.php, MessageIndex.php, TEMPLATES: index, Display, Media, Memberlist, PersonalMessage, Recent, Reports)
* Some of my uncommitted layout changes are starting to make their way into the code... Without the stylesheets. Meh. Coming soon! (BoardIndexInfoCenter.template.php, Display.template.php)
* I just don't like seeing 5 lines of code that could look cool and fit on a single line... (Subs-Login.php)
* The default feed format is now Atom rather than RSS 1, and support for SMF (custom) and Webslice feeds has been removed because they've never been commonly used anyway. Media feeds remain in RSS 2 format for now. (Feed.php, BoardIndexInfoCenter.template.php, index.template.php, index.language.php)
* Renamed 'RSS' to 'Atom' or 'feeds'. (index.php, db_aeva.php, rss.png, Feed.php, Load.php, Aeva-Foxy.php, Aeva-Gallery.php, ManageMedia.php, Subs-Media.php, media.css, TEMPLATES: BoardIndex, BoardIndexInfoCenter, index, Media, LANGUAGES: Admin, Help, index, ManageMedia, Post, Stats, Who)
@ Note: I removed the mention about feeds in the Help file, because we're going to move it somewhere else... Let's just not forget to document it when it's done. ;)
8630
FAQs / [FAQ] Re: Minimum requirements
« on June 21st, 2011, 06:56 PM »link=msg=262645 date=1308474250]
I wouldn't waste my time with the Chrome 1 requirement. You would be surprised at how hard it is to lock Chrome to a single version. I don't think it's worth worrying about older than 6 or 8 or something at this point, and even probably not that far back.
I expect Jaeger and V8 and etc. to get optimized for jQuery, so it's probably going to become a standard. If it keeps getting more popular, I suspect it'll be bundled and detected at some point by browsers for further perf wins (since we're currently in a perf war.)
I'm wondering if querySelectorAll was among them... Hmm, maybe at least native qsa implementation in browsers was sped up with the growing popularity of jQ.
8631
Off-topic / Re: Simple & Effective URL Routing System
« on June 21st, 2011, 06:48 PM »
IIS? Why?
BTW, I noticed two unsets in your source code... JFYI, unset($a, $b, $c) works fine :)
BTW, I noticed two unsets in your source code... JFYI, unset($a, $b, $c) works fine :)
8632
Off-topic / Re: htmlspecialchars while inserting into DB
« on June 20th, 2011, 10:28 PM »
There ate subtle differences. I think Pete knows best.
8635
The Pub / Re: Interesting site
« on June 20th, 2011, 07:18 PM »
I'm considering opening a dev blog where we would post our progress. Right now my commitment is at an all-time low because of my pc problems. I think I only made two commits last week. Barely more than the smf team's usual output :lol:
8636
Features / Re: Optimize release images
« on June 20th, 2011, 08:47 AM »
I believe I've already run everything through pngquant. I do it systematically for new files and keep a 32 bit copy in the other/images folder as well. ^_^
I dont automate it because png8 sometimes has awful results in ie6 btw.
Posted: June 20th, 2011, 08:46 AM
I dont automate it because png8 sometimes has awful results in ie6 btw.
8637
Off-topic / Re: Simple & Effective URL Routing System
« on June 20th, 2011, 07:52 AM »
Same trick as on Wedge eheh :)
8638
Features: Theming / Re: CSS and JavaScript minification
« on June 20th, 2011, 12:37 AM »
Yes, it's based off Packer 3.1. Dean Edwards has been working on Packer 4.0, though, and he told me he'd be putting the PHP version online soon. He's sort of hoping I'll be taking over the PHP version's maintenance but my knowledge of base2 (especially its PHP version) is rather limited. Anyway-- I'm interesting in giving 4.0 a shot and using it if it helps save even a few bytes off the 3.1 size.
I don't know of any reason why Packer should require 'offline automation'. Granted, the PHP version doesn't work out of the box, but it only took me a couple of hours to turn it into a working version (it really doesn't have THAT many bugs. It's just that Dean lost interest in the PHP version.)
Regarding semicolons, I provided a fix in the source file, but I commented it out because I think it's best to educate devs into using semicolons as much as possible. That's why I said it's fixable -- anyone's free to uncomment the fix, and then test their broken files. If that fixes them, then it means they should be careful about semicolon placement.
PS: would you like to get svn access to the files? Maybe it'd be easier for you if you could discuss the features without having to resort to guess work ;)
I don't know of any reason why Packer should require 'offline automation'. Granted, the PHP version doesn't work out of the box, but it only took me a couple of hours to turn it into a working version (it really doesn't have THAT many bugs. It's just that Dean lost interest in the PHP version.)
Regarding semicolons, I provided a fix in the source file, but I commented it out because I think it's best to educate devs into using semicolons as much as possible. That's why I said it's fixable -- anyone's free to uncomment the fix, and then test their broken files. If that fixes them, then it means they should be careful about semicolon placement.
PS: would you like to get svn access to the files? Maybe it'd be easier for you if you could discuss the features without having to resort to guess work ;)
8639
Features: Theming / Re: WeCSS: the Wedge CSS parser
« on June 20th, 2011, 12:28 AM »link=msg=262641 date=1308472960]
I belong to the school of semantics, by far, although I think using inheritance is only sensible.
I know I'm often the first person to write my own version of something, and I love learning from it and see if I can do better. And here as well, I think writing a PHP version makes a lot of sense.
But, considering Sassy recently moved to using CSS-style syntax,
and I personally hate Python style syntax, perhaps it makes sense to gravitate to the rules of another syntax?
Well, two things.
First, Sass added support for 'normal' syntax because of users requests. Probably couldn't get the hang of it... Dunno. From what they said on their website, it's quite clear to me they're still going to use the Sass syntax themselves.
Secondly, Wedge *does* support the CSS syntax. Really. It's just that you can't mix css and wecss syntaxes together. Only makes sense to me... Once you see my source code, you'll understand how complex it is already.
And because of multiple stylesheets and the styling system I described elsewhere, you can't use css syntax in any files that are related to the index stylesheet (i.e. index.css, sections.css, and any overrides like index.ie6.css etc.)
However, you may perfectly use wecss syntax in the index file, and css syntax in your plugin's file (my-stupid-addon.css), as long as you don't add it to the main file list. (i.e. your plugin must load it separately through add_css_file(), instead of adding it to the css file list array.)
One thing to note, though, is that I haven't tested the extent of what you can do in the css syntax. While all functions are available (color, etc), pseudo-language constructs like 'extend' may not be available (although you can use the alternative syntax for it, the 'base:' rule.)
That could make the documentation needs lighter.
8640
FAQs / [FAQ] Re: Minimum requirements
« on June 19th, 2011, 09:35 PM »
And the OP does say recommended, not required ;)