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
9136
Features / Re: AeMe reusability of your album images
« on May 1st, 2011, 08:06 PM »
That's already in AeMe2 you know!
9137
Features / Re: Custom fieldsets in new topic
« on May 1st, 2011, 06:44 PM »
We kind of did that in AeMe and I was thinking of doing something for topics as well...
9138
Features / Re: New revs
« on May 1st, 2011, 05:51 PM »
rev 752
(4 files +1, 41kb)
+ Added support for CSS math functions max, min and rand. I should have done min and max from day one. (Class-CSS.php)
* Committing CSS preparser with 'reset' keyword in the WIP folder. Although I'm sure it'll never be used. (other/wip/Class-CSS (reset keyword).php)
! Non-main CSS files needed an extra dash in the URL. (Subs-Cache.php)
! Fixed JumpTo and optimized for speed and size. (script.js)
! Fixed Wuthering header. (Wuthering/index.css)
(4 files +1, 41kb)
+ Added support for CSS math functions max, min and rand. I should have done min and max from day one. (Class-CSS.php)
* Committing CSS preparser with 'reset' keyword in the WIP folder. Although I'm sure it'll never be used. (other/wip/Class-CSS (reset keyword).php)
! Non-main CSS files needed an extra dash in the URL. (Subs-Cache.php)
! Fixed JumpTo and optimized for speed and size. (script.js)
! Fixed Wuthering header. (Wuthering/index.css)
9139
Off-topic / Re: Least its not cranky here...
« on May 1st, 2011, 02:48 PM »
What's the point in having a son if you can't blame everything on him?™™™™
9140
Off-topic / Re: Doctor Who
« on May 1st, 2011, 02:45 PM »
Apparently they pretty much said they were sorry for the colored Dalek fiasco. If we get any Daleks in this season (it won't be a Dalek-centric episode anyway), it'll be the old kind. (Phew.)
9141
Features / Re: New revs
« on May 1st, 2011, 08:50 AM »
rev 751 (useless "it's not 750, dude!" commit)
(7 files +3, 29kb)
+ Added support for new CSS keywords (Class-CSS.php)
+ Cancel inheritance ('unextend' keyword, useful for inherited stylings)
+ Delete a property entirely ('@remove' command)
+ Added support for all possible unit types in math functions. Also removed the mismatched unit protection code, because I'm not sure whether it's best to keep it to not. I'd have to rewrite it anyway. (Class-CSS.php)
* Optimized grad700.png for size, moved original to the image backup folder, as well as the original iPhone and Tablet icons. (other/images/*, grad700.png)
* Updated credits. Project managers are Wedgeward (still us!), added tentative Consultant and Support teams to Wedge credits. Made page more readable. (Credits.php, sections.css)
+ Added support for browser-agnostic linear-gradient call. (Although older Safari versions and IE6/7/8/9 will choke on it.) Also simplified call to the CSS property fixer. (Subs-Cache.php)
* Replaced 'create_topic' hook with the more interesting 'create_post_before' and 'create_post_after'. (Subs-Post.php)
+ Added 'modify_post_before' and 'modify_post_after' hooks. Guess what they do. (Subs-Post.php)
+ Added dummy example for a CSS section in styling file. (Warm/settings.xml)
(7 files +3, 29kb)
+ Added support for new CSS keywords (Class-CSS.php)
+ Cancel inheritance ('unextend' keyword, useful for inherited stylings)
+ Delete a property entirely ('@remove' command)
+ Added support for all possible unit types in math functions. Also removed the mismatched unit protection code, because I'm not sure whether it's best to keep it to not. I'd have to rewrite it anyway. (Class-CSS.php)
* Optimized grad700.png for size, moved original to the image backup folder, as well as the original iPhone and Tablet icons. (other/images/*, grad700.png)
* Updated credits. Project managers are Wedgeward (still us!), added tentative Consultant and Support teams to Wedge credits. Made page more readable. (Credits.php, sections.css)
+ Added support for browser-agnostic linear-gradient call. (Although older Safari versions and IE6/7/8/9 will choke on it.) Also simplified call to the CSS property fixer. (Subs-Cache.php)
* Replaced 'create_topic' hook with the more interesting 'create_post_before' and 'create_post_after'. (Subs-Post.php)
+ Added 'modify_post_before' and 'modify_post_after' hooks. Guess what they do. (Subs-Post.php)
+ Added dummy example for a CSS section in styling file. (Warm/settings.xml)
9142
Off-topic / Re: Doctor Who
« on May 1st, 2011, 08:30 AM »
I don't remember much (if anything) about season 5's Tardis stuff and Silence stuff. I remember the cracks but I can't even remember what they stood for.
I did, however, love Prisoner Zero from beginning to end. That was a flippin' fantastic episode. And it didn't require a doubled length (only a few extra minutes) to pack in all of the story, season arc presentation, AND character introductions, into the episode.
(click to show/hide)
I can't emphasize enough the importance of rhythm in writing. This week I watched 'Source Code' and absolutely loved the script's fluidity. Still, it wasn't pre-chewed/pre-digested. Then I watched 'The Names of Love' (Allenesque French movie), another piece of great writing and excellent rhythm. For me to see Who less than an hour after that movie -- it made it too painfully obvious that Moffat was perhaps a bit over the top here. He's so great at Sherlock, I trust his writing so much -- but he completely blew it in these two episodes. Hopefully the rest of the season will be great enough to make me reconsider these -- just as I appreciated the Angels episodes a bit more in season 5 after watching The Big Bang.
I don't see where we could have had a reference to the pirate episode in 6x01...
(click to show/hide)
I did, however, love Prisoner Zero from beginning to end. That was a flippin' fantastic episode. And it didn't require a doubled length (only a few extra minutes) to pack in all of the story, season arc presentation, AND character introductions, into the episode.
6x01-6x02 waste time on stupid things like Mr. President Oh You're Gonna Love Your Future, they're not developed enough, should have been thrown out entirely and replaced with longer exposition scenes because really, they could have used those. Heck, even Canton could have been thrown out because in the end he's underused and has just become gimmicky by episode 2. I'd have loved to see better integration for him... But too many characters, I guess.
I can't emphasize enough the importance of rhythm in writing. This week I watched 'Source Code' and absolutely loved the script's fluidity. Still, it wasn't pre-chewed/pre-digested. Then I watched 'The Names of Love' (Allenesque French movie), another piece of great writing and excellent rhythm. For me to see Who less than an hour after that movie -- it made it too painfully obvious that Moffat was perhaps a bit over the top here. He's so great at Sherlock, I trust his writing so much -- but he completely blew it in these two episodes. Hopefully the rest of the season will be great enough to make me reconsider these -- just as I appreciated the Angels episodes a bit more in season 5 after watching The Big Bang.
I don't see where we could have had a reference to the pirate episode in 6x01...
And even after a good night's sleep, I still don't give a freakin' damn that the doctor has a daughter. Sigh.
9143
Features / Re: Ditching themes? (+ CSS preparsing)
« on May 1st, 2011, 08:18 AM »Yes, I meant the block system, though really, it IS a meta tag, since <we:*> is a tag that will become other tags.
Like an alien? SILENCE, DOCTOR, SILENCE WILL FALL.
Hrm. This is a complex issue.Quote Does this mean it'll make more sense for us to ditch /Themes/*/ and just move everything to a root and then extend stylings with the ability to refine some templates?
Let's see...
We have a top level Sources folder for all the fun sources stuff. We also have a top level Themes folder which contains a whole bunch of stuff, including languages.
If we remove that Themes folder, we essentially risk damaging that association. Thing is, true parallel themes can do things that styling cannot.
Firstly, we'd need to give stylings the ability to modify any template's markup. To me, this seems the wrong way to go; a styling should be a *style*, rather than a complete layout specification. To me, then, I see stylings as making the theme variants system what it always wanted to be: a clear, easily accessible manner for a theme to provide multiple colour variations, or small style variations under a single 'theme' banner.
This it can do, and do extremely well, and I see no reason to graft on the ability to hit up markup more generically when really if the markup is that far different, it should be a different physical theme with its own templates (and using the default templates where necessary)
I've actually never tested installing an extra theme in Wedge. I'm sure it wouldn't be pretty...
Secondly, languages. If you have a theme that's doing really, really funky things the odds are it's going to bringing its own settings and with that its own language strings. Right now, SMF can deal with this (and even do it properly now, as far as I know!)
IOW, I'm not 100% sure we need to change anything, unless we replicate most of the functionality that's already present.
9144
Features / Re: Ditching themes? (+ CSS preparsing)
« on May 1st, 2011, 02:04 AM »
Meta tags? You mean the block system?
Although your post is interesting, it comes after a... peculiar hour of complicated Whoing, so I feel like you're an alien talking to me... :lol:
Does this mean it'll make more sense for us to ditch /Themes/*/ and just move everything to a root and then extend stylings with the ability to refine some templates?
We could do the structure this way:
/theme/
/theme/styles/
/theme/styles/css/
/theme/styles/js/
/theme/styles/img/
/theme/styles/tem/
/theme/styles/Other_Styling/
/theme/styles/Other_Styling/css
/theme/styles/Other_Styling/Sub_Styling/
/theme/styles/Other_Styling/Sub_Styling/img/
js, css, img and tem (and maybe "data" -- or maybe even JUST "data") could be 5 'reserved names' for folders (it could just as well be "js, css, images and templates" of course.)
Wedge would simply go through the folder list and discard these names when trying to find other stylings. It would make it easier to offer some clean code for themers, I don't know.
And themers wouldn't HAVE to use these folders to put their data into... It would just be the list of folders where they can safely put their stuff into without disrupting the nested styling system.
Time for bed...
Although your post is interesting, it comes after a... peculiar hour of complicated Whoing, so I feel like you're an alien talking to me... :lol:
Does this mean it'll make more sense for us to ditch /Themes/*/ and just move everything to a root and then extend stylings with the ability to refine some templates?
We could do the structure this way:
/theme/
/theme/styles/
/theme/styles/css/
/theme/styles/js/
/theme/styles/img/
/theme/styles/tem/
/theme/styles/Other_Styling/
/theme/styles/Other_Styling/css
/theme/styles/Other_Styling/Sub_Styling/
/theme/styles/Other_Styling/Sub_Styling/img/
js, css, img and tem (and maybe "data" -- or maybe even JUST "data") could be 5 'reserved names' for folders (it could just as well be "js, css, images and templates" of course.)
Wedge would simply go through the folder list and discard these names when trying to find other stylings. It would make it easier to offer some clean code for themers, I don't know.
And themers wouldn't HAVE to use these folders to put their data into... It would just be the list of folders where they can safely put their stuff into without disrupting the nested styling system.
Time for bed...
9145
Features / Re: Ditching themes?
« on May 1st, 2011, 01:28 AM »
Yes... Multiple versions of the file are generated in the cache -- depending on whether you're logged in or not, whether you're using the default language or another, and what browser you're using. Wedge automatically adds the relevant prefixes to any CSS3 that I use in the file. That is, box-shadow, border-radius, box-sizing, transition and background-image: linear-gradient(). (Although the last one is not in use for now because I'm using a custom function I made to get IE compatibility, but I added it for potential use by other themers.)
PS: back to the original question maybe..?
PS: back to the original question maybe..?
9146
Off-topic / Re: Doctor Who
« on May 1st, 2011, 01:14 AM »
Okay, I ended up watching the episode alone... And hated it.
Really, it's confusing from beginning to end. There was nothing enjoyable in this episode. The funny parts were few and far between. Matt Smith is starting to annoy me with his inability to relate to others (he seems *wicked* far too often for me), the story was too convoluted (and what was the problem with the Silence anyway? They seemed harmless to me...) and the story points at the end felt phony to me. I have absolutely no interest in that crap...
The only scenes that worked for me: last scene with River (what she said -- that's exactly what I thought when it happened), and the Rory paranoia at the end too. As for the rest... Well, I fear Moffat is overwhelmed by his work and he can't do everything properly. Hopefully that means he focused a lot more on Sherlock this year... :whistle:
Waiting for next week's episode, but frankly it looked cheap to me. Pirate ship... in the dog? Hello, studio shoot? I'm more interested in Neil Gaiman's episode... (Although the title now makes me fear we'll be getting even more nonsensical storylines.)
Don't get me wrong, I love Who and I love Moffat even more. I just hated that double episode all in all, probably because it's so different compared to earlier Moffat episodes. I like my Doctor best when he's playful and doesn't get into huge conspiracies and stuff. Basically -- when it's not moving into "end of season" RTD territory.
Really, it's confusing from beginning to end. There was nothing enjoyable in this episode. The funny parts were few and far between. Matt Smith is starting to annoy me with his inability to relate to others (he seems *wicked* far too often for me), the story was too convoluted (and what was the problem with the Silence anyway? They seemed harmless to me...) and the story points at the end felt phony to me. I have absolutely no interest in that crap...
The only scenes that worked for me: last scene with River (what she said -- that's exactly what I thought when it happened), and the Rory paranoia at the end too. As for the rest... Well, I fear Moffat is overwhelmed by his work and he can't do everything properly. Hopefully that means he focused a lot more on Sherlock this year... :whistle:
Waiting for next week's episode, but frankly it looked cheap to me. Pirate ship... in the dog? Hello, studio shoot? I'm more interested in Neil Gaiman's episode... (Although the title now makes me fear we'll be getting even more nonsensical storylines.)
Don't get me wrong, I love Who and I love Moffat even more. I just hated that double episode all in all, probably because it's so different compared to earlier Moffat episodes. I like my Doctor best when he's playful and doesn't get into huge conspiracies and stuff. Basically -- when it's not moving into "end of season" RTD territory.
9147
Off-topic / Re: Doctor Who
« on April 30th, 2011, 11:42 PM »
I have the episode but can't watch it. Girlfriend too busy speaking with her friend. Ahhhhh >_<
9149
Features / Re: Ditching themes?
« on April 30th, 2011, 06:43 PM »
Hmm yeah I could still see myself doing something like this...
- Retrieve all variables from the wecss files,
- Retrieve a $modSettings['css_vars'] variable that contains potential replacements for them,
- Do the replacement before passing the css vars.
And in the admin area -- retrieve variables from the wecss files, list them ("$main_font", etc.), and offer to overwrite them. If one of them is detected to be a color variable ("rgba(0,0,0, .5)", etc.), we could also offer a color wheel to pick a new one.
@Joker> Actually it's only Sass-style by inspiration. I read about Sass in .net Magazine last January, loved how their idea was going further than my original plans for a css preparser, which encouraged me to do a PHP version of it. In the end it hasn't got half of the Sass features, and it's certainly not as elegant, but it's much, much faster, and at least you don't have to remember 50 different functions eheh. Plus, my implementation has some cool extra features that no other css preparsers have. (Notably the 'final' keyword which is important for object oriented programming. You'll see when I publish the feature list.)
Here's a sample from my index.css code:
Code: [Select]
Fun, eh? :)
- Retrieve all variables from the wecss files,
- Retrieve a $modSettings['css_vars'] variable that contains potential replacements for them,
- Do the replacement before passing the css vars.
And in the admin area -- retrieve variables from the wecss files, list them ("$main_font", etc.), and offer to overwrite them. If one of them is detected to be a color variable ("rgba(0,0,0, .5)", etc.), we could also offer a color wheel to pick a new one.
@Joker> Actually it's only Sass-style by inspiration. I read about Sass in .net Magazine last January, loved how their idea was going further than my original plans for a css preparser, which encouraged me to do a PHP version of it. In the end it hasn't got half of the Sass features, and it's certainly not as elegant, but it's much, much faster, and at least you don't have to remember 50 different functions eheh. Plus, my implementation has some cool extra features that no other css preparsers have. (Notably the 'final' keyword which is important for object oriented programming. You'll see when I publish the feature list.)
Here's a sample from my index.css code:
section.block extends .wrc
overflow: hidden
header extends .wehead
font-weight: 700
padding: 3px 12px
border-radius: 8px 8px 0 0
margin: -0.9em -1.2em 1em
footer extends .wefoot
padding: 3px 12px
border-radius: 0 0 8px 8px
margin: .5em -1.2em -0.9em
dl.settings
margin, padding: 0Fun, eh? :)
9150
Off-topic / Re: Wedge official shirt?
« on April 30th, 2011, 05:21 PM »
I'm not much of a T-shirt guy (plus I only wear long sleeve T-shirts, and most online stores don't carry these AFAIK), but I guess if we made a Wedge T-shirt I'd have to have one... And wear it :P
I never made a single Cyna or Kyodai T-shirt. Just the idea of it... Brr.
I never made a single Cyna or Kyodai T-shirt. Just the idea of it... Brr.