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
4801
Features / Re: Media boards: fishing for opinions
« on July 5th, 2012, 06:41 PM »I'm honestly thinking we don't need to change the topic id column at this time, just because I don't know any forum that is going to get anywhere near it - and again, if they are even remotely close to it, they're going to run into other problems long before that which require us taking a look and helping optimise it anyway, and we can deal with scaling it closer to time.
But I'll just trust your instincts on this.
So... mediumint(8) unsigned? Is that okay for topic IDs and media item IDs? Even if it's on 3 bytes and stuff? (I'm sure MySQL doesn't have performance issues related to byte alignment, but I want to be sure...)
4802
Features / Re: Like types?
« on July 5th, 2012, 06:36 PM »
Well, as I said, it's the kind of thing that can be implemented through playlists (and plugins), but I was asking if we should modify the likes system to allow for more like types to be plugged in later through plugins or core additions...
4803
Features / Re: Like types?
« on July 5th, 2012, 03:03 PM »
The way I saw it implemented sucked because it had all these buttons... (And they even showed up for guests. Incentive to register...? What? Why would I register to tell the world I'm "concerned" by the post I just read? I can understand one would want to do that if registered, but it's in no way a good reason to register...)
Obviously it has to be done through the (future) mini-menu for Likes...
Obviously it has to be done through the (future) mini-menu for Likes...
4804
Features / Re: Media boards: fishing for opinions
« on July 5th, 2012, 03:01 PM »
Wanting opinions for everything, myself :)
4805
Archived fixes / Re: Moving text within a post
« on July 5th, 2012, 03:00 PM »
Yup, but OTOH I have plans to make it core... :^^;:
4806
Features / Re: New revs
« on July 5th, 2012, 02:38 PM »
rev 1631 - the sizenazi commit. Final commit for now, will be back later with some Foxy new changes.
(9 files, 4kb)
* Replaced a str_replace with a preg_replace in the dynamic replacement code -- it pains me, but it starts with a long unchanging string so it should be nearly as fast, and it allows me to optimize a few places I didn't think of with closing and reopening script tags. (Subs-Template.php)
* Size optimizations. Removing "> 0" tests (and replacing == 0 with !) when we know the variable is an integer, or close enough. Hope I didn't screw up the selectionStart thing. Also, stats.js was never fully optimized to begin with. (editor-func.js, editor.js, post.js, spellcheck.js, stats.js, suggest.js, topic.js, zoomedia.js)
* Turned Zoomedia into a closure. I like those, didn't you notice...? (zoomedia.js)
(9 files, 4kb)
* Replaced a str_replace with a preg_replace in the dynamic replacement code -- it pains me, but it starts with a long unchanging string so it should be nearly as fast, and it allows me to optimize a few places I didn't think of with closing and reopening script tags. (Subs-Template.php)
* Size optimizations. Removing "> 0" tests (and replacing == 0 with !) when we know the variable is an integer, or close enough. Hope I didn't screw up the selectionStart thing. Also, stats.js was never fully optimized to begin with. (editor-func.js, editor.js, post.js, spellcheck.js, stats.js, suggest.js, topic.js, zoomedia.js)
* Turned Zoomedia into a closure. I like those, didn't you notice...? (zoomedia.js)
4807
Features / Re: New revs
« on July 5th, 2012, 02:32 PM »
rev 1630 - the comfort commit.
(3 files, 2kb)
* The statistics page will now show days in reverse order, so that you can develop consecutive months and analyze daily stats in order without disruption. You know -- it's the kind of thing you never understand but use as is, and then one day you think, okay I'll just change that... (Stats.php)
* Ensuring that you can directly call add_js_file() for an external file without having to specify it's a direct URL -- this is because external files always have a :// in the URL. Well, I left the boolean in, just in case for some odd reason you need to call it with no protocol. (Subs-Cache.php)
* Switched membergroup name and badge positions in the profile account page. Cleaner this way. (Profile.template.php)
(3 files, 2kb)
* The statistics page will now show days in reverse order, so that you can develop consecutive months and analyze daily stats in order without disruption. You know -- it's the kind of thing you never understand but use as is, and then one day you think, okay I'll just change that... (Stats.php)
* Ensuring that you can directly call add_js_file() for an external file without having to specify it's a direct URL -- this is because external files always have a :// in the URL. Well, I left the boolean in, just in case for some odd reason you need to call it with no protocol. (Subs-Cache.php)
* Switched membergroup name and badge positions in the profile account page. Cleaner this way. (Profile.template.php)
4808
Features / Re: New revs
« on July 5th, 2012, 02:30 PM »
rev 1629 - the 'short' one.
(4 files, 2kb)
+ Added ability to specify a default display string in select boxes that isn't listed in the select box dropdown. Use data-default="string" in your select tag. (sbox.js)
! Fixed reqWin popup vertical position in iOS devices. Thank you Apple... (script.js)
! Fixed select boxes no longer showing up in IE6 and IE7. (index.template.php)
* Minor tweaks to the popup visuals. Optimized for size, too. By a couple of bytes uh... (index.css)
(4 files, 2kb)
+ Added ability to specify a default display string in select boxes that isn't listed in the select box dropdown. Use data-default="string" in your select tag. (sbox.js)
! Fixed reqWin popup vertical position in iOS devices. Thank you Apple... (script.js)
! Fixed select boxes no longer showing up in IE6 and IE7. (index.template.php)
* Minor tweaks to the popup visuals. Optimized for size, too. By a couple of bytes uh... (index.css)
4809
Features / Re: New revs
« on July 5th, 2012, 02:26 PM »
rev 1628 - a few more commits are coming up... I tried to split them by category.
(6 files, 5kb)
! Fixed error log's file viewer and made it use the Help template instead of a custom one. (ManageErrors.php, Errors.template.php)
! Fixed permission profile page in media area. Notably, empty values in option tags need to be replaced with data-hide. I think I should try harder and look at fixing these on the fly, really... (ManageMedia.php, ManageMedia.template.php)
+ Added an 'or' statement in the permission profile page to make it clear that you have a choice between two actions. (ManageMedia.php, ManageMedia.template.php, ManageMedia.language.php)
(6 files, 5kb)
! Fixed error log's file viewer and made it use the Help template instead of a custom one. (ManageErrors.php, Errors.template.php)
! Fixed permission profile page in media area. Notably, empty values in option tags need to be replaced with data-hide. I think I should try harder and look at fixing these on the fly, really... (ManageMedia.php, ManageMedia.template.php)
+ Added an 'or' statement in the permission profile page to make it clear that you have a choice between two actions. (ManageMedia.php, ManageMedia.template.php, ManageMedia.language.php)
4810
Archived fixes / Re: Moving text within a post
« on July 5th, 2012, 11:34 AM »
I do that, but I don't move text blocks around...
4811
Features / Like types?
« on July 5th, 2012, 11:22 AM »
Can we, should we, have Like types..?
I was on a French website yesterday, and noticed that it had an awful lot of Like buttons. Basically they all started with "This made me...", and then a list of verbs matching your emotion: "smile", "cry", "upset", "uncomfortable", "angry", things like that... Similarly, the latest .Net issue has a feature about someone writing a Chrome plugin to be able to say that you 'cried' at a YouTube video.
The whole point of this is to give you the ability to then search for the things that made people laugh, or cry, or react in any way different from just 'liking' it, basically just as if the users were adding 'personal tags'.
One of these things can be achieved through the playlist system in Wedge. For instance we could add playlist types and then let people create their playlists from a list of templates like "Favorites", "Pictures of places I should visit", "Videos that made me cry", etc, and then one could navigate through all similarly-named playlists and write plugins to sort items by most times seen in a specific playlist etc. Whatever.
Of course, playlists are only on a topic-level, while likes are on a message-level, so it's not the exact same thing. So I figured, it's hard to do that with playlists (although doable), so maybe with likes...
Maybe it should only be a plugin of course, like, adding emotion types through a plugin, but in the end maybe we should 'simply' accomodate for like types in the database already (i.e. a 'type' enum field), making it easier to add types later on.
What do you think...?
I was on a French website yesterday, and noticed that it had an awful lot of Like buttons. Basically they all started with "This made me...", and then a list of verbs matching your emotion: "smile", "cry", "upset", "uncomfortable", "angry", things like that... Similarly, the latest .Net issue has a feature about someone writing a Chrome plugin to be able to say that you 'cried' at a YouTube video.
The whole point of this is to give you the ability to then search for the things that made people laugh, or cry, or react in any way different from just 'liking' it, basically just as if the users were adding 'personal tags'.
One of these things can be achieved through the playlist system in Wedge. For instance we could add playlist types and then let people create their playlists from a list of templates like "Favorites", "Pictures of places I should visit", "Videos that made me cry", etc, and then one could navigate through all similarly-named playlists and write plugins to sort items by most times seen in a specific playlist etc. Whatever.
Of course, playlists are only on a topic-level, while likes are on a message-level, so it's not the exact same thing. So I figured, it's hard to do that with playlists (although doable), so maybe with likes...
Maybe it should only be a plugin of course, like, adding emotion types through a plugin, but in the end maybe we should 'simply' accomodate for like types in the database already (i.e. a 'type' enum field), making it easier to add types later on.
What do you think...?
4812
Archived fixes / Re: Moving text within a post
« on July 5th, 2012, 09:59 AM »
Uh, I've actually never done this in my life... Didn't even think it was possible :P
I'd usually use cut & paste for that, and I'd recommend that you'd do it as it's faster, ah ah...
Anyway... Is it worth 'fixing'? Is it even possible to check that a drag is coming from a textarea...? (Heck, from a specific class even...)
I'd usually use cut & paste for that, and I'd recommend that you'd do it as it's faster, ah ah...
Anyway... Is it worth 'fixing'? Is it even possible to check that a drag is coming from a textarea...? (Heck, from a specific class even...)
4813
Features / Re: New revs - Public comments
« on July 5th, 2012, 08:22 AM »
Well, question is, do you have any issues with me going open source with these?
Because it'd be a way for me to test github or bitbucket or whatever... If anything, I want to release WeCSS because I think it's better than LESS or SASS (not in EVERY way but in most), and it pains me to read .Net every month and see them recommend them heartily :P
Because it'd be a way for me to test github or bitbucket or whatever... If anything, I want to release WeCSS because I think it's better than LESS or SASS (not in EVERY way but in most), and it pains me to read .Net every month and see them recommend them heartily :P
4814
Features / Re: New revs - Public comments
« on July 5th, 2012, 12:28 AM »
I can make reintegrating easier by simply splitting the stuff so that I only need to reimport the separate files... e.g. like sbox.js can be stand-alone if so desired, without any rewrites.
4815
Features / Re: New revs - Public comments
« on July 4th, 2012, 10:50 PM »Loving the new popup in r1627 by the way. I like it even more than the lower-right-corner alignment (which is something I never thought would happen)
But the alignment was probably something I cooked up because at the time it couldn't be dragged away.. I don't know. I think it was because of that. I think I implemented dragslide() after writing the initial code. Then I just forgot to consider centering it...
What I will do then, now we have the newer shinier version of it, is migrate the PM popup to use that - that was really what stopped me from changing the PM popup to use reqWin before was that the alignment of it seemed strange given the context, but putting it like that will work well.
One of my goals (which I'm unlikely to achieve though) is to ensure that as many UI elements as possible are harmonized. That would mean trying to use the same code (or at least identical CSS) for: the select box, the main menu, the mini-menu, Zoomedia, and the popups. I actually wrote all 5 of these separately, i.e. I didn't reuse any code inside another component, but right now I'm simply trying to determine whether it can be done and whether it would add to Wedge, or detract from it. The most likely candidates for merging are the main and mini menus, of course. But the mini-menus looks awfully like the popups right now. And Zoomedia is pretty much the same concept as the popup... And the select box uses a scrollbar which I could make use of in the popup. Maybe the first thing I'll try to do is split the scrollbar code from the SelectBox object into its own object (it's already done, actually, but it's an object that's internal to SB...!)
Ideally I would release the select box, zoomedia and popup code as separate components on github and offer people to help improve them (along with WeCSS). I just don't know whether it'll stick with them.
One thing that does occur is that depending on what else is going on it might not be obvious enough. XenForo, for example, does their popups similarly, but adding something like a 10px border plus a massive shadow - personally I find that a bit much, but it definitely shows some contrast to the background.