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
8476
And another poll...
The stylings feature is described here:
http://wedge.org/pub/feats/theming/6673/stylings/
It has been suggested that we should use 'skins' instead, as it's likely to be recognizable by more users as the proper intent of the feature.
I don't really know what else to offer in the list of choices, so let's just vote between the two.
Also, the stylings folder is called /Themes/default/styles, which doesn't match the name of the feature itself, but I thought 'stylings' was a bit long (although it doesn't have any implication over your forum's bandwidth, because stylings are cached anyway, and loaded from the /cache/ folder.) Renaming stylings to skins would imply a rename of the folder as well. Otherwise it'll just stay 'styles'.
The stylings feature is described here:
http://wedge.org/pub/feats/theming/6673/stylings/
It has been suggested that we should use 'skins' instead, as it's likely to be recognizable by more users as the proper intent of the feature.
I don't really know what else to offer in the list of choices, so let's just vote between the two.
Also, the stylings folder is called /Themes/default/styles, which doesn't match the name of the feature itself, but I thought 'stylings' was a bit long (although it doesn't have any implication over your forum's bandwidth, because stylings are cached anyway, and loaded from the /cache/ folder.) Renaming stylings to skins would imply a rename of the folder as well. Otherwise it'll just stay 'styles'.
8477
Considering the number of upcoming changes in the package system (and the fact that no single 'package' will work on SMF without a serious rewrite), we decided last year to rename the feature.
We settled on Add-ons, but a recent discussion made us reconsider the question. It is apparent that many, if not most SMF users call packages 'mods' and will continue to do so under Wedge. So it might make sense to use 'mods' to begin with.
Feel free to chip in!
We settled on Add-ons, but a recent discussion made us reconsider the question. It is apparent that many, if not most SMF users call packages 'mods' and will continue to do so under Wedge. So it might make sense to use 'mods' to begin with.
Feel free to chip in!
8478
Features / Re: New revs
« on July 12th, 2011, 02:33 PM »
rev 854
(8 files, 13kb)
! Regexp error in the Facebook custom field array. (ManageSettings.php)
! Admin settings use windowbg2 as the default background. (Admin.template.php)
* Validation & indentation nazi. (Admin.template.php)
* Made it a bit clearer (uh, in my fashion...) that the registration error is due to you being a spambot. And also something that bothered me with the Facebook string (again.) (Errors.english.php, ManageSettings.english.php)
* French translation. (Errors.french.php, ManageSettings.french.php)
* Something I'm not sure about, waiting for feedback... Help popups will automatically attempt to retrieve the string they're about, and will reproduce it at the top of the popup. (script.js)
- Removing border color on fieldset legends with windowbg. Maybe it was a tad too much... Adding a border to help popups though. (index.css)
- Back to square one for the h6 tag. Worked well in the credits page, but not anywhere else. (index.css)
(8 files, 13kb)
! Regexp error in the Facebook custom field array. (ManageSettings.php)
! Admin settings use windowbg2 as the default background. (Admin.template.php)
* Validation & indentation nazi. (Admin.template.php)
* Made it a bit clearer (uh, in my fashion...) that the registration error is due to you being a spambot. And also something that bothered me with the Facebook string (again.) (Errors.english.php, ManageSettings.english.php)
* French translation. (Errors.french.php, ManageSettings.french.php)
* Something I'm not sure about, waiting for feedback... Help popups will automatically attempt to retrieve the string they're about, and will reproduce it at the top of the popup. (script.js)
- Removing border color on fieldset legends with windowbg. Maybe it was a tad too much... Adding a border to help popups though. (index.css)
- Back to square one for the h6 tag. Worked well in the credits page, but not anywhere else. (index.css)
8479
Features / Re: New revs
« on July 12th, 2011, 11:29 AM »
rev 852
(3 files, ??kb)
- Right now, I don't believe custom CSS browser prefixes are disabled once the proper rule is implemented[1], so why not save a few bytes off the final files and prevent browsers from giving CSS errors? (Subs-Cache.php)
! Slightly incorrect way of handling $data in getXmlProfile(). (Feed.php)
! Code tags would get incorrect header styling when used within quote tags. Reordered styles to avoid that. (index.css)
* Changed code tag background to adapt itself to any windowbg colors, while retaining the blueish color. (index.css)
* Changed h6 tag (used notably as mini-headers in the credits page) to use the Corbel font on Windows 7 systems. Also increased letter spacing to, hmm... Give peace a chance. Probably gonna change my mind later. Seriously though, Corbel and Calibri are nice fonts, and they have a larger install base than PT Sans, so I should do something with them. (index.css)
(3 files, ??kb)
- Right now, I don't believe custom CSS browser prefixes are disabled once the proper rule is implemented[1], so why not save a few bytes off the final files and prevent browsers from giving CSS errors? (Subs-Cache.php)
! Slightly incorrect way of handling $data in getXmlProfile(). (Feed.php)
! Code tags would get incorrect header styling when used within quote tags. Reordered styles to avoid that. (index.css)
* Changed code tag background to adapt itself to any windowbg colors, while retaining the blueish color. (index.css)
* Changed h6 tag (used notably as mini-headers in the credits page) to use the Corbel font on Windows 7 systems. Also increased letter spacing to, hmm... Give peace a chance. Probably gonna change my mind later. Seriously though, Corbel and Calibri are nice fonts, and they have a larger install base than PT Sans, so I should do something with them. (index.css)
| 1. | I actually spent some time trying to find details about that but found nothing online about it, so I guess they keep compatibility options on. |
8480
Development blog / Re: A wedge in the hand is worth two in the wild
« on July 12th, 2011, 07:40 AM »
I think mod could stand for module yeah.
A module is self-explained and doesn't imply anything.
A module is self-explained and doesn't imply anything.
8481
Off-topic / Re: Unknown's thoughts on Wedge
« on July 12th, 2011, 07:31 AM »
Just keep in mind that the Wedge version has a wider use/reach. :)
8482
Development blog / Re: A wedge in the hand is worth two in the wild
« on July 12th, 2011, 12:32 AM »
I received a pm asking me where to download the Wedge auto-embedder :P
Meh!
Poll time for styling and add-on?
Meh!
Poll time for styling and add-on?
8483
Development blog / Re: A wedge in the hand is worth two in the wild
« on July 12th, 2011, 12:06 AM »This is why I don't use Opera :P
8484
Development blog / Re: A wedge in the hand is worth two in the wild
« on July 12th, 2011, 12:05 AM »I personally prefer stylings but on the flip side, I'm happy to bow to the court of vocal majority if that's preferred term on it. And, fair enough, it IS, really, more common.
And having a 'skins' subfolder would certainly make more sense to noobs than what SMF has ('css'), or even what Wedge currently has ('styles'), which isn't even the same as the name of the feature (stylings). Meh!
That said, our 'skins' are more flexible than most, I think.
I thought we were going to go with add-ons? :P
Now, obviously 95% of the SMF community says 'mods'. Maybe it's make sense to use 'mods', then. Although, in that particular case, it's not really a noob-friendly name. It's just what the community uses.
You know as well as I do that our users will tend to disagree anyway, and will call them themes and mods, because they're familiar terms.
8485
Development blog / Re: A wedge in the hand is worth two in the wild
« on July 11th, 2011, 11:59 PM »Can't have everything in the world. The guys at Opera work hard to make life easier though, so I suspect any problem anyone might have will be fixed in a year or two. :lol:
Just look at the demo site... Click on any media item, then move the zoom box around. It leaves black lines in its trail... That's not a 'complete' box-shadow implementation to me.
But Firefox' plugins can be awesome indeed.
8486
Development blog / Re: A wedge in the hand is worth two in the wild
« on July 11th, 2011, 09:59 PM »
Chrome sucks at many tabs (over 80 and it starts showing blank pages when loading a tab... This happens in Opera too, but after 200 tabs). Plus, it doesn't have any way to group tabs. And related tab plugins suck. (Chrome doesn't allow much freedom...)
Firefox handles tabs way better. Plus, with TabGroups Manager, I can actually 'hibernate' a group that I don't need to read right now. They also reopen quite quickly. I can rename groups -- very important. But the current major flaw is that I can't go through the recently viewed tab list manually. In Opera, I'll just hit the '4' key to minimize the current tab and get the last viewed tab, and I can do it forever until I find the tab I was looking for. In Firefox, if you minimize a tab, it just switches to another, and if you minimize that one, it redirects you to the first one. :-/
Also, I'm using Tree Style Tabs, and I can't get both the tab list in the vertical tree, and in the regular horizontal tab bar. Opera does that, and I'm used to it... Ah, and it only shows one group at a time in the list tree. :(
Ah well...
Firefox handles tabs way better. Plus, with TabGroups Manager, I can actually 'hibernate' a group that I don't need to read right now. They also reopen quite quickly. I can rename groups -- very important. But the current major flaw is that I can't go through the recently viewed tab list manually. In Opera, I'll just hit the '4' key to minimize the current tab and get the last viewed tab, and I can do it forever until I find the tab I was looking for. In Firefox, if you minimize a tab, it just switches to another, and if you minimize that one, it redirects you to the first one. :-/
Also, I'm using Tree Style Tabs, and I can't get both the tab list in the vertical tree, and in the regular horizontal tab bar. Opera does that, and I'm used to it... Ah, and it only shows one group at a time in the list tree. :(
Ah well...
8487
Development blog / Re: A wedge in the hand is worth two in the wild
« on July 11th, 2011, 09:37 PM »
Well, I'm a die-hard Opera fan, have been for the last 6 years at least, but recently I found myself in a corner with it... It systematically becomes unstable once I get to more than 200 tabs. Tab grouping doesn't help either -- whenever I restart Opera, my groups are gone, or totally disjointed (what used to be a group becomes three groups with several stand-alone tabs in the middle, etc.)
So I've switched to Opera+Firefox once I got my new machine, since it's very demanding in terms of Ram. I do my testing, main browsing etc with Opera, and once I have too many tabs open, I move them to Firefox. Works well for now...
Plus, Firefox has some great font rendering (even if not faithful to the actual font hinting of whatever. I don't care, it looks so good.)
So I've switched to Opera+Firefox once I got my new machine, since it's very demanding in terms of Ram. I do my testing, main browsing etc with Opera, and once I have too many tabs open, I move them to Firefox. Works well for now...
Plus, Firefox has some great font rendering (even if not faithful to the actual font hinting of whatever. I don't care, it looks so good.)
8488
Development blog / Re: A wedge in the hand is worth two in the wild
« on July 11th, 2011, 09:14 PM »
I've learned in life that whatever is extremely unimportant, is rigorously indispensable. (quote from Jerome Bonaldi, French TV personality in the 90s.)
8489
Development blog / Re: A wedge in the hand is worth two in the wild
« on July 11th, 2011, 04:48 PM »If I have to divide it further down "template" is what I call the content part of the process, and "skin" is what i call the design/css part of the process.
Which makes me think -- maybe it's more widely accepted as a term. 'Skin'. For what we're doing. Rather than 'stylings'. Maybe I went wrong on this one. Maybe we should rename stylings to skins, maybe it'll be clearer to everyone.
Pete, what do you think? And anyone else?
Which also reminds me that we still haven't found a perfect compromise on naming packages/extensions/add-ons/plugins :P
8490
The Pub / [Archive] Re: Logo Madness
« on July 11th, 2011, 01:00 AM »
Gri's stuff? I don't read his troll shit. You'll have to define these words for me (not that I think it'd be interesting.)
Garlic sausage? It's just sausage you know... Emphasis on sausage.
My fave dishes are Vietnamese caramelized pork with eggs, and French blanquette de veau. Now we're talking.
Garlic sausage? It's just sausage you know... Emphasis on sausage.
My fave dishes are Vietnamese caramelized pork with eggs, and French blanquette de veau. Now we're talking.