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
2671
Off-topic / Re: Post count fever
« on August 1st, 2013, 06:39 PM »
You just do whatever you want with your 48 hours a day... :P
2672
Archived fixes / Re: Soft merge / ignored user
« on August 1st, 2013, 06:39 PM »
Hmmm.... Fixed locally. Not as elegantly as I'd like, but the logic of it... Well, couldn't do otherwise.
2673
Off-topic / Re: Post count fever
« on August 1st, 2013, 05:27 PM »
Hmm... Nope.
Plugin material, and not from me! :P
Plugin material, and not from me! :P
2674
The Pub / Re: Infinite Scroll
« on August 1st, 2013, 05:26 PM »(Hmm, looks like I can't reproduce the scrollbar bug today... Is this a bug fix in Chrome 30, maybe..?)
2675
Bug reports / Re: Periodic notifications don't seem to work
« on August 1st, 2013, 05:23 PM »
Missed this topic... (As I did many others, obviously!)
Yes, the database structure had yet to be updated; including the size for 'task'.
If it still doesn't work, then... It's something else, I guess.
Yes, the database structure had yet to be updated; including the size for 'task'.
If it still doesn't work, then... It's something else, I guess.
2676
Off-topic / Re: Noisen.com?
« on August 1st, 2013, 05:11 PM »
- link structure: it's just PrettyURLs, right..? Like here. My custom (faster) version, of course.
- subdomains: it's possible to do these in Wedge, too, but it needs configuring on your server's side, so it's not clearly explained how to do it.
- not all boards/blogs have their own subdomain, and my.noisen.com is something I'd have done by default in here, but I want a 'clean' Wedge to run on, and this wouldn't be a clean one, as I can't assume all Wedge users are gonna have the ability to choose their subdomains, hmm...
- subdomains: it's possible to do these in Wedge, too, but it needs configuring on your server's side, so it's not clearly explained how to do it.
- not all boards/blogs have their own subdomain, and my.noisen.com is something I'd have done by default in here, but I want a 'clean' Wedge to run on, and this wouldn't be a clean one, as I can't assume all Wedge users are gonna have the ability to choose their subdomains, hmm...
2677
Off-topic / Re: Noisen.com?
« on July 31st, 2013, 08:34 PM »
I don't know about people... And, I don't know about what they like in Noisen.
To me, Noisen is great because of the music database at fox.noisen.com (I wrote Aeva' playlist system for it), because of some mods I wrote for it and that are in Wedge now, and some cool tweaks I did to the profile system, although I didn't write most of it. But other than that, if you're talking about the layout and all, I never found the 'right' version, between the earlier theme (/?theme=9), and the current one... Hmm.
So, I'm unlikely to ever make a Noisen skin, until I actually get to start using Wedge on Noisen.com, and then I'll probably do another mix, or something...
To me, Noisen is great because of the music database at fox.noisen.com (I wrote Aeva' playlist system for it), because of some mods I wrote for it and that are in Wedge now, and some cool tweaks I did to the profile system, although I didn't write most of it. But other than that, if you're talking about the layout and all, I never found the 'right' version, between the earlier theme (/?theme=9), and the current one... Hmm.
So, I'm unlikely to ever make a Noisen skin, until I actually get to start using Wedge on Noisen.com, and then I'll probably do another mix, or something...
2678
Features / Re: New revs
« on July 31st, 2013, 05:10 PM »
rev 2192 -- soft-merging! Yay!
(5 files +1, 11kb)
+ Implemented soft-merging of posts. This is similar to regular double-post merging, except it's done at display time, rather than in the database, allowing for internal parent IDs not to get screwed, thus allowing for easier threaded mode, in case we eventually implement this. It's also done automatically, and is quite fast (1ms to merge all posts in a page together), the only drawback really is that it makes the msg skeleton structure a bit less flexible, but whatever... Also turned a few msg blocks into macros, yay. (Subs-Template.php, Msg.template.php, macros.xml, sections.css)
+ Added, for reference, the JavaScript prototype of soft-merging, to the attic. (attic/scripts/Unused-softMerge.js)
+ Macros can now use extra params even without specifying an <if> tag in their body. I should have dealt with that long ago, but, well, I didn't even notice the problem was there... (Subs-Template.php)
:edit:
* Chrome 29+ should support min-resolution CSS stuff now, so I'm changing the logic to save a few bytes.
(5 files +1, 11kb)
+ Implemented soft-merging of posts. This is similar to regular double-post merging, except it's done at display time, rather than in the database, allowing for internal parent IDs not to get screwed, thus allowing for easier threaded mode, in case we eventually implement this. It's also done automatically, and is quite fast (1ms to merge all posts in a page together), the only drawback really is that it makes the msg skeleton structure a bit less flexible, but whatever... Also turned a few msg blocks into macros, yay. (Subs-Template.php, Msg.template.php, macros.xml, sections.css)
+ Added, for reference, the JavaScript prototype of soft-merging, to the attic. (attic/scripts/Unused-softMerge.js)
+ Macros can now use extra params even without specifying an <if> tag in their body. I should have dealt with that long ago, but, well, I didn't even notice the problem was there... (Subs-Template.php)
:edit:
* Chrome 29+ should support min-resolution CSS stuff now, so I'm changing the logic to save a few bytes.
2679
Off-topic / Re: Noisen.com?
« on July 30th, 2013, 01:37 PM »
noisen.com hasn't changed since ~2009.
My goal in 2010 was for Wedge to be what noisen.com is.
Pete went in a different direction, so I took the middle road.
There are no *immediate* plans to be further noisenized. Why?
My goal in 2010 was for Wedge to be what noisen.com is.
Pete went in a different direction, so I took the middle road.
There are no *immediate* plans to be further noisenized. Why?
2680
Features / Re: Soft merging of posts
« on July 30th, 2013, 12:23 AM »
Yup ;)
I was going to commit tonight, but I got busy with a few quick improvements, and it'll have to wait until tomorrow.
I'll also commit the JS version.
I was going to commit tonight, but I got busy with a few quick improvements, and it'll have to wait until tomorrow.
I'll also commit the JS version.
2681
Features / Re: New revs
« on July 29th, 2013, 10:55 PM »
rev 2191
(1 file, 3kb)
* Updated CSS prefix handling. I still do tech watch really, always need to...! So, what's fixed on my side: iOS 6 should now show border-image, unprefixed, and use calc(), prefixed. What's new in the browser world: IE 11 supports border-image (unprefixed), Chrome 26 finally unprefixed gradients (didn't notice before), Chrome 29 unprefixed the final flexible box layout model, a bit late, but still... Safari 7 unprefixes gradients, transitions and calc(). iOS unprefixed transitions and calc() only. Hopefully, I didn't miss anything... The code is starting to get complicated, but it's still a bit early to drop all of the old browsers from the list; still, I'll eventually do it, at least for the evergreen ones, i.e. Chrome and Firefox. (Class-CSS.php)
+ I don't think it's of much interest, but I added prefixing support for 'backface-visibility', 'perspective' and 'perspective-origin'. Supposedly (I even read that again in the latest issue of WDM), you can force hardware acceleration with these, but I never got any issues without them either, so I'll have to wait for someone to tell me they have performance issues... Although, I might eventually apply backface-visibility: hidden to all 2D-only transforms, because, whatever. Maybe in a mixin, or somethin'. (Class-CSS.php)
(1 file, 3kb)
* Updated CSS prefix handling. I still do tech watch really, always need to...! So, what's fixed on my side: iOS 6 should now show border-image, unprefixed, and use calc(), prefixed. What's new in the browser world: IE 11 supports border-image (unprefixed), Chrome 26 finally unprefixed gradients (didn't notice before), Chrome 29 unprefixed the final flexible box layout model, a bit late, but still... Safari 7 unprefixes gradients, transitions and calc(). iOS unprefixed transitions and calc() only. Hopefully, I didn't miss anything... The code is starting to get complicated, but it's still a bit early to drop all of the old browsers from the list; still, I'll eventually do it, at least for the evergreen ones, i.e. Chrome and Firefox. (Class-CSS.php)
+ I don't think it's of much interest, but I added prefixing support for 'backface-visibility', 'perspective' and 'perspective-origin'. Supposedly (I even read that again in the latest issue of WDM), you can force hardware acceleration with these, but I never got any issues without them either, so I'll have to wait for someone to tell me they have performance issues... Although, I might eventually apply backface-visibility: hidden to all 2D-only transforms, because, whatever. Maybe in a mixin, or somethin'. (Class-CSS.php)
2682
Features / Re: Soft merging of posts
« on July 29th, 2013, 08:10 PM »
Okay, looks like #new is fixed now, phew...
Oh, bugger, this is a 'opens up a new page' post... Was hoping to check the #new behavior when posting :lol:
It should work, though...
Oh, bugger, this is a 'opens up a new page' post... Was hoping to check the #new behavior when posting :lol:
It should work, though...
2683
Features / Re: Soft merging of posts
« on July 29th, 2013, 08:07 PM »
So... Took me longer than expected, but I did manage to rewrite Subs-Template to handle soft-merging of posts at the PHP level (ob_sessrewrite), and it works. You can check out the HTML source code, it's all done directly now.
Few caveats:
- #new still doesn't work for me, even though at this point it SHOULD... Maybe it's a browser bug..? :unsure:
- Parsing time takes about 10 milliseconds when there are many posts to merge. It's... quite a lot more than I expected. I dunno. It's still very good, and it saves bandwidth, after all...
Thoughts, anyone?
Few caveats:
- #new still doesn't work for me, even though at this point it SHOULD... Maybe it's a browser bug..? :unsure:
- Parsing time takes about 10 milliseconds when there are many posts to merge. It's... quite a lot more than I expected. I dunno. It's still very good, and it saves bandwidth, after all...
Thoughts, anyone?
2684
Features / Re: New revs
« on July 28th, 2013, 11:24 AM »
rev 2190 -- macros rewrite, hopefully will help me with the upcoming soft-merge trick, hmm...
(5 files +2, 11kb)
* Tweaked the macro system. Default macros are *no longer* defined in index.template.php, and are instead declared in a new 'macros.xml' file in the skins folder, which you can augment with contents in custom.xml, or a sub-skin's macros.xml file. Just like for skeletons, a replace-type skin shouldn't ignore the root skin's macros, so if you want to cancel a parent macro, make sure to rewrite it entirely, otherwise it's here to stay. I think. The reason why I did this rewrite was to (1) completely clean up the index template, which is already complicated as it is with all of the blocks defined, and (2) make it easier for me to add new macros, as the xml definition style is, well, definitely better looking... Plus, the banner macro needed to be fixed with non-PHP code, so, two birds with one stone. (Load.php, Subs-Cache.php, index.template.php, macros.xml)
+ Started adding a few macros... (Msg.template.php, macros.xml)
- skin.xml no longer accepts macro redefinitions. Use macros.xml, sorry about that. (Warm/skin.xml, Warm/macros.xml)
- A couple of unused globals... (index.template.php)
(5 files +2, 11kb)
* Tweaked the macro system. Default macros are *no longer* defined in index.template.php, and are instead declared in a new 'macros.xml' file in the skins folder, which you can augment with contents in custom.xml, or a sub-skin's macros.xml file. Just like for skeletons, a replace-type skin shouldn't ignore the root skin's macros, so if you want to cancel a parent macro, make sure to rewrite it entirely, otherwise it's here to stay. I think. The reason why I did this rewrite was to (1) completely clean up the index template, which is already complicated as it is with all of the blocks defined, and (2) make it easier for me to add new macros, as the xml definition style is, well, definitely better looking... Plus, the banner macro needed to be fixed with non-PHP code, so, two birds with one stone. (Load.php, Subs-Cache.php, index.template.php, macros.xml)
+ Started adding a few macros... (Msg.template.php, macros.xml)
- skin.xml no longer accepts macro redefinitions. Use macros.xml, sorry about that. (Warm/skin.xml, Warm/macros.xml)
- A couple of unused globals... (index.template.php)
2685
Features / Re: Soft merging of posts
« on July 27th, 2013, 02:26 PM »- since you can redefine macros in skins, I can (finally!) modify Wireless to remove some blocks of code entirely, instead of just hiding them.
There are multiple ways to remove code for a skin:
- hardcode the change into the template file (meaning it's not up to the skin, of course...)
- hardcode it into skeleton.xml (IIRC it supports either MOBILE_SKIN (i.e. the skin has a 'mobile' flag), or a browser string),
- hardcode it into the macros, like I'm doing now.
Still, I'm torn between keeping the macro definitions as they are, in index.template.php, or moving them all to skin.xml, just like I got rid of the skeleton definition in index to move it to skeleton.xml, but the latter case was done because it wasn't any different in terms of performance, while it'll be a bit slower in the case of a skin.xml macro definition.