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
4066
The Pub / Re: Getting ready for an alpha release: WeCSS/Wess improvements
« on December 16th, 2012, 07:11 PM »
Okay, I'm a bit stumped here... re: what we discussed above, and what I committed today.
Basically, it seems that Wess never actually stores an OS string into the css filename, even if there's a file in the list with an OS suffix. I don't know why, because it used to work... Anyway... It needs some changing anyway, because currently the implementation is flawed. That is, if an @if or @is command takes place in a file, Wess doesn't care what the question is about, and doesn't send back any data regarding it. For instance, if you do a test on the user agent or OS, Subs-Cache (most specifically the actual css caching function) has absolutely no way of knowing that such a test took place Inside the file, allowing it to force-add browser/OS keywords to the filename... Similarly, if it doesn't need to actually rebuild the cache, there's no way to actually determine that an internal test took place, and thus an extra keyword is needed in the filename...
What I could do, though, is something like that...
- If the test is POSITIVE[1], set a special variable asking Subs-Cache to later add the browser or OS to the filename (depending on what we tested against.) Otherwise, don't set a variable.
- At regular page load time, first generate a user agent-free filename, then do a file_exists on that filename + a browser + OS, if it exists, load it. Otherwise test filename + browser, if it exists, load it. Otherwise test filename + OS, if it exists, load it. Otherwise test filename, if it exists, load it. Otherwise rebuild cache file.
It adds quite an extra few file_exists tests, I know... We could always cache the results for some time, or whatever...
Maybe it's all a bit... far-fetched...
Fishing for ideas here...
Basically, it seems that Wess never actually stores an OS string into the css filename, even if there's a file in the list with an OS suffix. I don't know why, because it used to work... Anyway... It needs some changing anyway, because currently the implementation is flawed. That is, if an @if or @is command takes place in a file, Wess doesn't care what the question is about, and doesn't send back any data regarding it. For instance, if you do a test on the user agent or OS, Subs-Cache (most specifically the actual css caching function) has absolutely no way of knowing that such a test took place Inside the file, allowing it to force-add browser/OS keywords to the filename... Similarly, if it doesn't need to actually rebuild the cache, there's no way to actually determine that an internal test took place, and thus an extra keyword is needed in the filename...
What I could do, though, is something like that...
- If the test is POSITIVE[1], set a special variable asking Subs-Cache to later add the browser or OS to the filename (depending on what we tested against.) Otherwise, don't set a variable.
- At regular page load time, first generate a user agent-free filename, then do a file_exists on that filename + a browser + OS, if it exists, load it. Otherwise test filename + browser, if it exists, load it. Otherwise test filename + OS, if it exists, load it. Otherwise test filename, if it exists, load it. Otherwise rebuild cache file.
It adds quite an extra few file_exists tests, I know... We could always cache the results for some time, or whatever...
Maybe it's all a bit... far-fetched...
Fishing for ideas here...
| 1. | Or (maybe) if it's NEGATIVE but with a negative statement such as (!ie7)...? |
4067
Off-topic / Re: Programming styles, and does it really matter?
« on December 16th, 2012, 03:55 PM »There are some people who like Apple devices and build quality but are not fanbois. (Like me.)
| 1. | To be precise, I'm still desperately looking for a phone with: (1) a high quality screen, (2) freeeeeedom, (3) a physical Home button to make it easy to turn on when taking it out of my pocket, (4) quality components that ensure it won't break if I drop it from time to time, (5) narrow enough that I can manipulate it with one hand... The S3 has 1/2/3, the iPhone 5 has 3/4/5... Where do I get 'the' perfect phone now? :P Oh, sorry for the topic hijack :lol: |
4068
Off-topic / Re: Programming styles, and does it really matter?
« on December 16th, 2012, 03:49 PM »What I'm worried about is more people writing off Wedge (and other of the free platforms) because it doesn't match up to some theoretical ideal of how code should look. Enough people write off the free platforms as being 'toys' and not 'real' software as it is.
4069
Features / Re: New revs
« on December 16th, 2012, 03:43 PM »
rev 1800
(15 files, 27kb)
@ This is the 'revolutionary' update I'd hoped to commit as r1789, ah ah, but it wasn't ready yet.
* Rewrote much of the detectBrowser() function. (Load.php, Home.php, Aeva-Gallery.php, Post2.php, Welcome.php, Xml.template.php, editor.js, script.js, index.css, Wuthering/skin.xml, attic/Unused-dynPrefixed.php)
Wedge will no longer return 'iphone' and 'tablet' entries -- these should be addressed through media queries primarily, and/or analysis of the user agent string.
Browser and OS are now stored in two different variables -- $context['browser']['agent'] and $context['browser']['os']
Browser and OS versions are also stored in 'version' and 'os_version' variables. Minor updates like the '5' in '4.1.5' aren't stored, to save space.
Likewise, old OS versions aren't stored (Windows < XP, iOS < 4, Android < 2).
* Rewrote much of the hasBrowser() function as well... (Load.php, Wine/extra.css)
Added support for OS names, now a test against 'windows' will work. Supported: windows, ios, android, mobile.
Added support for OS versions, e.g. 'windows[6.1-]'.
Added support for negative statements, e.g. '!chrome' will return a positive if you're not using Chrome.
Added support for logical AND & or && (whatever suits you best). 'windows, !android && firefox' means 'using Windows, or Firefox but not in Android.'
! Fixed ambiguity with browser/OS versions in Wess's prefix handler. $android should now only be set for the Android stock browser, $iphone is replaced with $ios, and $safari should no longer be set in iOS, for the purpose of these tests of course. (Class-CSS.php)
+ Non-Android, non-iOS mobile devices will now show a regular wireless icon. (Post2.php)
* French Translation. (Errors, ManageSettings)
(15 files, 27kb)
@ This is the 'revolutionary' update I'd hoped to commit as r1789, ah ah, but it wasn't ready yet.
* Rewrote much of the detectBrowser() function. (Load.php, Home.php, Aeva-Gallery.php, Post2.php, Welcome.php, Xml.template.php, editor.js, script.js, index.css, Wuthering/skin.xml, attic/Unused-dynPrefixed.php)
Wedge will no longer return 'iphone' and 'tablet' entries -- these should be addressed through media queries primarily, and/or analysis of the user agent string.
Browser and OS are now stored in two different variables -- $context['browser']['agent'] and $context['browser']['os']
Browser and OS versions are also stored in 'version' and 'os_version' variables. Minor updates like the '5' in '4.1.5' aren't stored, to save space.
Likewise, old OS versions aren't stored (Windows < XP, iOS < 4, Android < 2).
* Rewrote much of the hasBrowser() function as well... (Load.php, Wine/extra.css)
Added support for OS names, now a test against 'windows' will work. Supported: windows, ios, android, mobile.
Added support for OS versions, e.g. 'windows[6.1-]'.
Added support for negative statements, e.g. '!chrome' will return a positive if you're not using Chrome.
Added support for logical AND & or && (whatever suits you best). 'windows, !android && firefox' means 'using Windows, or Firefox but not in Android.'
! Fixed ambiguity with browser/OS versions in Wess's prefix handler. $android should now only be set for the Android stock browser, $iphone is replaced with $ios, and $safari should no longer be set in iOS, for the purpose of these tests of course. (Class-CSS.php)
+ Non-Android, non-iOS mobile devices will now show a regular wireless icon. (Post2.php)
* French Translation. (Errors, ManageSettings)
4070
Features / Re: New revs
« on December 16th, 2012, 03:34 PM »
rev 1799 -- working on committing a larger rev right now.
(2 files, 3kb)
+ Saving a few bytes on CSS cached files where a path calculated through a global var like $here or $images could be longer than needed (like/this../../). (Subs-Cache.php)
! Take into account the user's OS when caching CSS files (re: an upcoming huge commit.) However, this is a bit buggy so I'm only committing this until I decide whether or not I should keep CSS file suffixes this way. Because of the difference in filename handling, it seems best to drop support for hasBrowser-based suffixes, and instead relying on @if/@is statements inside the files themselves. They're probably better off as tests inside the files only. (Subs-Cache.php)
* A quick note in BB rules for Pete to read mostly... Feel free to remove it if I'm mistaken. (Security.php)
(2 files, 3kb)
+ Saving a few bytes on CSS cached files where a path calculated through a global var like $here or $images could be longer than needed (like/this../../). (Subs-Cache.php)
! Take into account the user's OS when caching CSS files (re: an upcoming huge commit.) However, this is a bit buggy so I'm only committing this until I decide whether or not I should keep CSS file suffixes this way. Because of the difference in filename handling, it seems best to drop support for hasBrowser-based suffixes, and instead relying on @if/@is statements inside the files themselves. They're probably better off as tests inside the files only. (Subs-Cache.php)
* A quick note in BB rules for Pete to read mostly... Feel free to remove it if I'm mistaken. (Security.php)
4071
Features / Re: New revs
« on December 16th, 2012, 02:21 PM »
rev 1797
(40 files, 7kb)
* Harmonized all index.php files that were only there to prevent manual folder exploration. All files now use the same contents -- a single-line redirect to the upper level. Simpler, better. Could be done with an .htaccess file, but I believe it's better to rely on PHP here. The only thing I'm not sure about is whether I should forcibly add index.php to the redirect or leave it this way... There's still time to adapt. (40 occurrences of */index.php)
(40 files, 7kb)
* Harmonized all index.php files that were only there to prevent manual folder exploration. All files now use the same contents -- a single-line redirect to the upper level. Simpler, better. Could be done with an .htaccess file, but I believe it's better to rely on PHP here. The only thing I'm not sure about is whether I should forcibly add index.php to the redirect or leave it this way... There's still time to adapt. (40 occurrences of */index.php)
4072
The Pub / Re: Logo Madness
« on December 16th, 2012, 02:08 PM »
It's not supposed to make you think of a forum, rather of a wedge... Don't lose it :whistle:
4073
The Pub / Re: Logo Madness
« on December 16th, 2012, 12:18 AM »
So if i changed it to an Amazon logo ripoff that'd be better? :P
4075
Plugins / Re: Extending the moderation filter actions when posting
« on December 15th, 2012, 08:36 PM »
Okay, I don't know where to post about this, and given that my network issues took away most of my mana for the day, I'm not going to bother fighting too hard against my internal compass... :P
About the moderation filters.
- How exactly can I trigger that popup...?[1] I really need to see what I'm trying to translate, because it has a strange ring to it... (?)
- Create a new filter, with Chrome for instance. First dropdown choice. Then first DD choice. Then choose 'Depends on post subject'. Click inside the text input and type anything. My problem comes from the fact that it only shows the Add button once you focus out of the box. It should be triggered when you start typing something, or even right after you select the filter type (e.g. 'Depends on post subject'.)
- Also, the 'Informing the user' part shows up after you select the second dropdown. It should either show up before the condition list, or be shown only when the 'Save this rule' button appears.
- Finally, there's still at least one bug in the Condition list... Select 'applies to one of more boards', then click a board name checkbox, then click a radio button above it. The button doesn't appear. That's because it only appears when you click the radio button first, and then any checkbox, not the other way around... That's a minor bug, but it's still a bug. It may apply to other situations in the condition list, but I don't have time to test them all, sorry, it's more of a job for our BETA TESTERs.......... :niark:
About the moderation filters.
- How exactly can I trigger that popup...?[1] I really need to see what I'm trying to translate, because it has a strange ring to it... (?)
- Create a new filter, with Chrome for instance. First dropdown choice. Then first DD choice. Then choose 'Depends on post subject'. Click inside the text input and type anything. My problem comes from the fact that it only shows the Add button once you focus out of the box. It should be triggered when you start typing something, or even right after you select the filter type (e.g. 'Depends on post subject'.)
- Also, the 'Informing the user' part shows up after you select the second dropdown. It should either show up before the condition list, or be shown only when the 'Save this rule' button appears.
- Finally, there's still at least one bug in the Condition list... Select 'applies to one of more boards', then click a board name checkbox, then click a radio button above it. The button doesn't appear. That's because it only appears when you click the radio button first, and then any checkbox, not the other way around... That's a minor bug, but it's still a bug. It may apply to other situations in the condition list, but I don't have time to test them all, sorry, it's more of a job for our BETA TESTERs.......... :niark:
| 1. | And, by the way, what prevents us from renaming the Help template to 'Popup' and 'help_text' to 'popup_text'? I actually did this internally last night, before my network problems started... Because I'm feeling that the help popup is just one of many. |
4076
The Pub / Re: Logo Madness
« on December 15th, 2012, 08:25 PM »
Is the shape too big? Or it's just about the colors?
There's an infinity of possibilities... Just look at this, took less than two minutes to do. :P
There's an infinity of possibilities... Just look at this, took less than two minutes to do. :P
4077
Off-topic / Re: Programming styles, and does it really matter?
« on December 15th, 2012, 08:19 PM »
I say if it ain't broke, don't fix it... For the last two years we've both used a good share of procedural coding and a small share of OOP when we felt like it (me, mainly for the templating object and hopefully soon for the hasBrowser code), it should depend on what we feel is best, rather than whatever rules we set for ourselves. We're shaped by how SMF was developed, it's a given, and it's not a bad thing -- most of the SMF devs were and are still good developers with good guidelines for themselves. I see no reason to try and move into another direction... ;)
4078
The Pub / Re: Logo Madness
« on December 14th, 2012, 11:05 AM »
The Nike tick is not something that comes to mind.... It's thinner than my own tick, to begin with. And my 'tick' is actually a wedge, mind you :P They don't own the 'deformed triangle' shape, do they? ;)
Here's another test with a larger wedge and a small solid white halo around the logo...
Here's another test with a larger wedge and a small solid white halo around the logo...
4079
The Pub / Re: Logo Madness
« on December 12th, 2012, 10:37 PM »
I think I prefer the first version I posted a few weeks ago, lol... ;)
4080
The Pub / Re: Logo Madness
« on December 12th, 2012, 10:06 PM »
I personally like it because it's a throw back to the old logos... And it's simple enough to warrant not having to bother too much about details.
Here are a couple of variations... Different fonts, different colors. Second one isn't too good, was looking for a color replacement, but the font may be too light. As for the first... It's actually my original idea, which I then later tried to simplify even more. Works best when shown with a large border on its left, of course...
Posting smaller version... with a border.
Here are a couple of variations... Different fonts, different colors. Second one isn't too good, was looking for a color replacement, but the font may be too light. As for the first... It's actually my original idea, which I then later tried to simplify even more. Works best when shown with a large border on its left, of course...
Posted: December 12th, 2012, 06:39 PM
Posting smaller version... with a border.