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
4636
Features / Re: Virtual selectors in WeCSS
« on August 17th, 2012, 10:58 AM »
I wouldn't dream of it!
4637
Features / Re: New revs
« on August 17th, 2012, 10:10 AM »
rev 1660
(1 file +26-26, 24kb)

* Renamed 'hacks' CSS filename category to 'extra', which is probably more neutral and better suited to both sub-skin additions and browser hacks. (Subs-Cache.php, hacks.*.css, extra.*.css)
4638
Off-topic / Re: Randomly I wish I worked in an office
« on August 17th, 2012, 12:57 AM »
Quote from Arantor on August 17th, 2012, 12:56 AM
Quote
Use it as your avatar, it's the closest thing you'll be getting to a sign
Well, there is a noticeboard in the hallway, I guess...
Will anyone notice see it? :P
Quote
I'll certainly try and take a look.
Thanks!! Been a long night here, I'd hate to know another bug is resisting us ;)
4639
Features / Re: Virtual selectors in WeCSS
« on August 17th, 2012, 12:55 AM »
Quote from Nao on August 16th, 2012, 04:02 PM
I was thinking of a name that could naturally 'flow' into the naming scheme, something that would remind people of 'index'... So in addition to hacks, I thought of addendum (= latin), postscript (ditto), affix (has an x, 5 letters), extra (ditto!), or just 'fix'...
Since it's a name that's likely to be used a lot by skinners, I'd like to ensure it 'works' per se...
I think that 'extra' or 'extras' is probably the most neutral of all. And thus would both work for browser hacks and sub-skins.
Keep up the good work, Nao! Even if I don't post a lot, I always love to see what you have to offer! I know it's bit of a rush, but will you marry me?
4640
Off-topic / Re: Randomly I wish I worked in an office
« on August 17th, 2012, 12:54 AM »
Use it as your avatar, it's the closest thing you'll be getting to a sign :P

Pete, while I'm at it... And sorry for the off-topic!!
Could you look into the source code? I've found the reason why drafts no longer auto-save (well, they do but it doesn't give any feedback.) This is because of my change to weUrl() etc... In editor-func, the action form URL is called, and because it no longer has ';xml' in it, Subs-Post.php (and others) are test $context['is_ajax'] instead. Well, it seems that it returns false, and because of that draftXmlReturn() is never called. Can you test why is_ajax is false when it should be true, since it's really Ajax stuff...?
Thanks! Gotta go to bed... :P
4641
Features / Re: New revs
« on August 17th, 2012, 12:26 AM »
rev 1659 -- back to short commits... Phew :) :)
(1 file, 1kb)

! Fixed mini-menus in IE6. (hacks.ie[6].css)
4642
Off-topic / Re: Nexus 7
« on August 16th, 2012, 11:34 PM »
Quote from nend on August 16th, 2012, 08:04 PM
Padding depends on the browser, Opera Mobile seems to work good for me, not the best. The best browser that renders pretty good is Dolphin IMHO, however I hate the UI.
I don't know if it's the same engine as on my iPod, but it's looking oddly close to Safari Mobile... (Perhaps it's just a custom layer on Safari really...)
Quote
As for fonts there isn't much, you can install more if you want. I lost count of the number of fonts I have installed on my device.
I know, the S3 I tested on had an awful default font for the UI -- the guy seemed to think it was pretty cool to use a fantasy serif font for it. Yeah sure... (Interestingly, Opera Mobile fell back to that font, while other browsers used Roboto as fallback.)
Quote
On the buttons, unlike Apple, Android devices come with a wide range of interfaces and hardware that need to be consider. See my device has Menu, Home, Back, Search, Directional Pad with Center Button, Volume Keys, Call and Hang Up.
The S3 doesn't have a lot of buttons. But below the main screen it has a central button (like Home?), and two 'touchable' areas on its sides -- these are the buttons that give no feedback and unfortunately, the options button is one of these.
I can hate Apple all I want, but my iPod Touch 4 really has the best technical design I could think of. And 99% of that hardware is used for Safari Mobile and playing Scrabble™... :lol:
4643
Features / Re: New revs
« on August 16th, 2012, 11:12 PM »
rev 1658
(4 files +2-2, 4kb)

* Admin homepage no longer needs to declare inline-block class on every item. Also added a plugin_from class to the plugin page to avoid using the class in HTML. (Admin.template.php, mana.css)

* Using a hardcoded style is bad... Well. Whatever. (Profile.template.php)

! Typonazi. (skins/Wireless/hacks.css)

! Fixed Wireless by renaming sections.* to hacks.*... I know, it's quite complicated. (skins/Wireless/hacks.*.css)
4644
Features / Re: Virtual selectors in WeCSS
« on August 16th, 2012, 08:24 PM »
Any faves in the name list?

Also -- woo. Looks like topic pages are broken on my iPod...
4645
Off-topic / Re: The Humble Indie Bundle V
« on August 16th, 2012, 06:51 PM »
A new HB is out...
http://www.humblebundle.com/

Not as interesting as the first one, though.
4646
Features / Re: New revs
« on August 16th, 2012, 06:33 PM »
rev 1657 -- the final CSS frontier.
(11 files +29-32, 46kb)

+ Added 'the' list of CSS virtuals. Nuff said, now you can safely use them in your own plugin files. (common.css, index.css)

- External files no longer need the extra inline-block mixin. (admenu.css, editor.*.css)

* Renamed all CSS index files to 'hacks' when they're actually intended to be listed *after* the 'sections.css' file category, mostly in sub-skins. (The category for the main file list are listed in that order: common, index, sections, hacks, custom.) (index.*.css, hacks.*.css)

! An AWFUL lot of fixes for Internet Explorer, mainly in sub-skins. Because I'm not spending my days testing these silly browsers, or even my sub-skins for that matter... Just gonna add: it's not perfect (mini-menus still don't work), but it's damn more than what its old versions deserve. (hacks.ie[*].css)

* And even more tweaks for all browsers, making Weaving (and sometimes sub-skins) look better overall. Things like backgrounds, reqWin popups, gradients have all been overhauled... And possibly broken in places. It's a major rewrite, and it's working for me. Good enough for a commit! (*.css)
4647
Off-topic / Re: Nexus 7
« on August 16th, 2012, 06:28 PM »
I didn't have a problem with the UI itself (I'd already tested a regular Android box before anyway -- just on a tablet, not a phone.)
What I did have a problem with, was with the browsers... And it was the same with all of them (Android or Chrome, can't remember which was or were installed, and Firefox and Opera Mobile.)
- The pinch effect looked 'rigid', not the 'natural' effect that I'm getting when zooming in/out on pages,
- There was too much padding in places,
- A strong tendency to use Roboto or Droid Sans everywhere or whatever -- betraying the fact that Android probably doesn't have a lot of default fonts...
- And major UX mistakes, like this one that made me want to throw away the phone: in order to GO BACK to the previous page, you have to press the OPTIONS button (which is not even a physical button, it has no feedback), and then wait for the menu to open, and select "Previous page" or something... Not only is this a *menu*, but it doesn't even have icons to help you find the right solution immediately!

All of them were done that way.
Mehhhh......................
4648
Features / Re: Virtual selectors in WeCSS
« on August 16th, 2012, 05:54 PM »
I'm the biggest of them all, don't fret... :P
4649
Features / Re: New revs
« on August 16th, 2012, 05:53 PM »
rev 1656
(7 files, 7kb)

* Converted default macros to use the hasBrowser() syntax. (index.template.php)

* Moved page ID hooking from the body tag to the frame div right below the content ID. This is to avoid applying page-specific styling to generic areas like the menu or the sidebar. Fixed after seeing it happen on the stats page... (index.template.php)

* Partially reverted the confirm rewrite. Although technically exciting, it wasn't solid enough and IE made it even more complicated, as always. Instead, I'm renaming the function to 'ask' and 'say' (respectively confirm and alert), and will rename manually every occurrence where it makes sense to have an improved confirm (or alert). Additionally, you can now provide a callback function, which makes sense within a non-event codeblock. (Subs-Template.php, script.js)

* Simplified JS code for error removal in error log. There was no reason to have the lastClicked variable around. Especially in Wedge with delayed events. (Errors.template.php)

* My select box now uses a proper unicode character to stand for the triangle, rather than the neat CSS triangle that still required a IE6 hack and had trouble getting aligned vertically. (sbox.js)

! Fixed a silly JS error introduced when converting to jQuery. (stats.js)

* Saved a few bytes off the weres() function calling process. (index.template.php)

! Forgot to complete a comment line in the ed
4650
Features / Re: New revs
« on August 16th, 2012, 05:44 PM »
rev 1655
(3 files +1-4, 20kb)

@ This is a multi-part HUGE commit. It is, basically, due to my realizing that the current SVN was so much behind my CSS rewrites that it was more buggy than my local install.

+ Added support for the virtual keyword in WeCSS. It allows you to specify a CSS selector that is to be inherited by other rules, but that shouldn't appear itself in the final file. If no other selectors inherit it, then it'll be safely removed. (Class-CSS.php)

! Fixed an incredibly annoying bug that was fixed through a half-arsed attempt back in revision 562, where the generated CSS could sometimes be very different from what was expected, depending on the rule's position in the file. The problem lied in the fact that the sorting wasn't done correctly, and on top of that, WeCSS needed to do extra sorting on the target list. (Class-CSS.php)

- Got rid of the value list (deg, px, mm...) in the math plugin for WeCSS, because I realized that several new value types had been introduced since I last touched it, and I don't want to spend my life on this. So from now on, it'll only be checking for strings between 2 and 4 characters located right after a number. Seems to work well enough... (Class-CSS.php)

+ Added proper support for animation/transition/transform properties in CSS3. (Subs-Cache.php, Class-CSS.php)

+ Added support for unprefixed gradients. I'd recommend the use of angles to indicate the direction, because Wedge will automatically convert the angle between versions. (Class-CSS.php)

* Moved prefixer code from Subs-Cache to Class-CSS, because it's directly linked to the CSS preprocessor, rather than the cache system. (Subs-Cache.php, Class-CSS.php)

+ Added support for browser versions in macros, CSS filenames or CSS conditions (e.g. in skin.xml), and adapted IE to use the new system. The agent is now 'ie' rather than an exact version number, and CSS filenames should have index.ie[6].css instead of index.ie6.css for instance. The good news is, you can now easily say "IE7 or later" (ie[7-]), "IE7, IE8 or IE9" (ie[7-9]), "up to IE7" (ie[-7]) and just "IE" (ie, yep.) iOS devices will now use the iOS version as the browser version, rather than the browser version itself, because the information it gives away is more important. If you're wondering, the main reason for doing all of this was to allow for the prefixer plugin to determine precisely whether or not the current browser accepts a prefix. (Load.php, Subs-Cache.php)

+ Added an automatic cache purge function that gets called every month to remove files older than a month ago. This should allow for old browser versions to naturally disappear from the file list and avoid stressing the filesystem when accessing the cache folder. (Subs-Cache.php)

+ Added a 'hacks' file category (final name TBA) to the main CSS list, which is executed right after 'index' and 'sections', allowing skins to override an 'index' category file without having to use the 'sections' category name. If you know what I mean... If you don't, don't fret, just use 'hacks' instead of 'index' for skins if you want to be on the safe side. (Subs-Cache.php)

* Moved a couple of files around. (buttons.png, grad250.png, grad700.png)

@ Note on virtuals: this is still (very slightly) buggy, in that it seems to delete the entries in some situations, even if they're inherited. This should be easy enough to fix, as it's reproduceable on the .grad40 class. Not for now though...