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
5086
Features / Re: Rewriting the skin file parser...
« on May 26th, 2012, 08:50 AM »
Let's say you have these files:
/index.css
/index.ie6.css
/index.ie6,ie7.css
/index.ie8.css
/Sub/index.css
/Sub/index.replace.ie6.css
The question is: what files *should* be included as logic implies here, and in our current SVN, what files will end up being included in the Sub skin...?
You have one hour.
Or, in other words: should we allow for the replace keyword to be used alongside any other suffix...?
/index.css
/index.ie6.css
/index.ie6,ie7.css
/index.ie8.css
/Sub/index.css
/Sub/index.replace.ie6.css
The question is: what files *should* be included as logic implies here, and in our current SVN, what files will end up being included in the Sub skin...?
You have one hour.
Or, in other words: should we allow for the replace keyword to be used alongside any other suffix...?
5087
Features / Re: Thought system
« on May 26th, 2012, 08:10 AM »
I know! Eheh.
I don't know why it had padding issues recently. Probably due to the skin loading order changes.
I don't know why it had padding issues recently. Probably due to the skin loading order changes.
5088
Features / Re: Thought system
« on May 25th, 2012, 11:39 PM »
Plus. If you have 100 friends, does that mean any of my actions get entered 100 times into the db...?
I'd rather have it done once. I can control things more clearly. Facebook does both but between the two I prefer the wall system. Seems more realistic.
I'd still like to find a way to make it possible to comment streams without having to create a new table for these comments. Basically thoughts were there to also encourage posting small messages without fear of filling the main messages table too much. Ensuring better performance in the long run.
Well. I guess it's something I'll have to decide by myself. But having a 'stream' type for boards seems a bit like overkill. Does this mean creating a new topic on each new wall entry...? then we might as well give up thoughts. Or give up posting thoughts into the stream. Hmm maybe having a stream and a thought list in parallel isn't something unrealistic or unreliable.
I'd rather have it done once. I can control things more clearly. Facebook does both but between the two I prefer the wall system. Seems more realistic.
I'd still like to find a way to make it possible to comment streams without having to create a new table for these comments. Basically thoughts were there to also encourage posting small messages without fear of filling the main messages table too much. Ensuring better performance in the long run.
Well. I guess it's something I'll have to decide by myself. But having a 'stream' type for boards seems a bit like overkill. Does this mean creating a new topic on each new wall entry...? then we might as well give up thoughts. Or give up posting thoughts into the stream. Hmm maybe having a stream and a thought list in parallel isn't something unrealistic or unreliable.
5089
Features / Re: Thought system
« on May 25th, 2012, 11:01 PM »
A notification goes away when you view it. I like having a slightly longer archive...
5091
Features / Re: Thought system
« on May 25th, 2012, 08:34 PM »Since it's not a wall, per se, but a stream of notifications (at least that's what I want to do), you only need to worry about notifying replies up the chain, and really that's only necessary up to the immediate parent IMO.
The stream by definition has a shorter life (I'm thinking 3-5 days for notifications you've seen before, no limit on unread notifications, for now at least)
And what about wall comments? The thought system is well suited for that, too... (Of course, we could also consider these to be part of the 'profile' type of board, and create a new topic on each notification being commented... Uh... Then that means multiple topics per user...? How do we store that... Meta field eh?)
5092
Features / Re: New revs
« on May 25th, 2012, 08:31 PM »
rev 1597
(10 files +2, 20kb)
+ Implemented new pages for the thought system: a thread page and a rewrite of the profile page. This should at last make it more usable, even with thousands of thoughts around... (index.php, Home.php, Profile.php, Profile-View.php, Thoughts.php, Welcome.php, Profile.template.php, Thoughts.template.php)
! Fixed wrong days given in 'latest news' box in the admin area. (admin.js, xml/latest-news.php)
! Fixed improper number of lines in error popups. (ManageErrors.php)
* Styling detail. (index.member.css)
(10 files +2, 20kb)
+ Implemented new pages for the thought system: a thread page and a rewrite of the profile page. This should at last make it more usable, even with thousands of thoughts around... (index.php, Home.php, Profile.php, Profile-View.php, Thoughts.php, Welcome.php, Profile.template.php, Thoughts.template.php)
! Fixed wrong days given in 'latest news' box in the admin area. (admin.js, xml/latest-news.php)
! Fixed improper number of lines in error popups. (ManageErrors.php)
* Styling detail. (index.member.css)
5093
Features / Re: Thought system
« on May 25th, 2012, 08:19 PM »
I think I'm done with the thought rewrite... Phew.
Not perfect, but good enough.
Walls ==> well, at one point we're going to offer user streams, right...? We already discussed doing them like some of the admin logs, to help with translations. So, what about the thought system? Do we use thoughts for the streams, or do we copy any thoughts into the stream, assuming that a stream may have a shorter or longer 'expiry date' than thoughts...?
Not perfect, but good enough.
Walls ==> well, at one point we're going to offer user streams, right...? We already discussed doing them like some of the admin logs, to help with translations. So, what about the thought system? Do we use thoughts for the streams, or do we copy any thoughts into the stream, assuming that a stream may have a shorter or longer 'expiry date' than thoughts...?
5094
Features / Re: Thought system
« on May 25th, 2012, 07:47 PM »
Actually, Wedge.org still shows thoughts by a single user...? It's in the same place as always: profile > show thoughts.
The difference now is that they're shown just like on the main page. There's a link to the thread for each thought, as well as a "(...)" in case there are replies to a particular thought. (I know, it may not be very intuitive...)
I still need to add paging to these, though...
Re: what I said on the skin topic, how are we going to manage 'walls'?
The difference now is that they're shown just like on the main page. There's a link to the thread for each thought, as well as a "(...)" in case there are replies to a particular thought. (I know, it may not be very intuitive...)
I still need to add paging to these, though...
Re: what I said on the skin topic, how are we going to manage 'walls'?
5095
The Pub / Re: The Cookie Law (in the UK at least)
« on May 25th, 2012, 05:37 PM »
Same in France.
Amusingly, they also store a cookie to keep your cookie preferences, even if you said you don't want any cookie... :lol:
Amusingly, they also store a cookie to keep your cookie preferences, even if you said you don't want any cookie... :lol:
5096
The Pub / Re: When can I download Wedge? / Where can I download Wedge?
« on May 25th, 2012, 04:42 PM »
I feel the same... Oddly!
5097
Bug reports / Sub-boards not marked as new...
« on May 25th, 2012, 03:52 PM »
I think it's also a SMF bug, but it's worth mentioning either way.
I had a sub-board marked as 'New' in the board list. I click it, went to reply the first unread topic, came back to the homepage, and it was no longer marked as new.
Problem is -- there still are unread posts in this specific board...
So it would seem that in the board list, sub-boards are marked as unread only in specific situations, totally unrelated to whether or not there are unread posts in them.
It may be 'desirable', but I'd rather know why it works that way ;)
I had a sub-board marked as 'New' in the board list. I click it, went to reply the first unread topic, came back to the homepage, and it was no longer marked as new.
Problem is -- there still are unread posts in this specific board...
So it would seem that in the board list, sub-boards are marked as unread only in specific situations, totally unrelated to whether or not there are unread posts in them.
It may be 'desirable', but I'd rather know why it works that way ;)
5098
Other software / Re: Aeva Blog
« on May 25th, 2012, 03:49 PM »
I tend to avoid any topics with 'Aeva' in their title, but this one is damn funny :P
5099
Features / Re: Rewriting the skin file parser...
« on May 25th, 2012, 03:48 PM »
Bump?
Ah well, so no one cares about that... :(
I assume no one cares either about the philosophical matter of having the Thoughts table serve as recipient for our future 'user streams'? (i.e. FB wall, to put it bluntly. Before they went for their horrible timeline thingy...)
Posted: May 25th, 2012, 01:09 PM
Ah well, so no one cares about that... :(
I assume no one cares either about the philosophical matter of having the Thoughts table serve as recipient for our future 'user streams'? (i.e. FB wall, to put it bluntly. Before they went for their horrible timeline thingy...)
5100
Features / Re: New revs
« on May 25th, 2012, 03:40 PM »
rev 1596
(4 files +5-12, 21kb)
+ And it's time for this dreaded rewrite of the CSS caching code... It still needs some work (especially with the replace suffix), but it works for now, so let's get it over with. Basically, instead of checking whether files exist (index.mysuffix.css), Wedge will instead go through all of the files and decide whether they should be included, allowing you to use comma-separated lists of suffixes, which solves an AWFUL lot of problems. It was harder to implement as it sounds, if only because Wedge needs to sort all files at the end of the process, while the original implementation was naturally sorted. (Subs-Cache.php, editor.*.css, media.*.css, zoom.*.css, Wine/index.*.css, Warm/index.*.css)
+ As mentioned, added a 'replace' suffix to the list of accepted CSS suffixes. This will basically delete any prior file with the same radix (index, sections, mana...) found in the CSS file list, i.e. files from a parent skin, allowing you to create an add-type skin and still benefit from a complete rewrite of, say, sections.css. (Subs-Cache.php, Load.php)
+ Added support for m, b and c suffixes, followed by a number. 'm1' will restrict a CSS file to member #1, 'b1' to board #1 and 'c1' to category #1. And another many issues were instantly solved. (Load.php)
! Canonical URLs for category pages were pointing to the homepage. (Boards.php)
* Replaced quote tag's quote icon with dynamically generated CSS. It doesn't look exactly the same across all browsers, but it saves 150 bytes off the final gzipped CSS file. I'm all for that... (index.css, quote.png)
(4 files +5-12, 21kb)
+ And it's time for this dreaded rewrite of the CSS caching code... It still needs some work (especially with the replace suffix), but it works for now, so let's get it over with. Basically, instead of checking whether files exist (index.mysuffix.css), Wedge will instead go through all of the files and decide whether they should be included, allowing you to use comma-separated lists of suffixes, which solves an AWFUL lot of problems. It was harder to implement as it sounds, if only because Wedge needs to sort all files at the end of the process, while the original implementation was naturally sorted. (Subs-Cache.php, editor.*.css, media.*.css, zoom.*.css, Wine/index.*.css, Warm/index.*.css)
+ As mentioned, added a 'replace' suffix to the list of accepted CSS suffixes. This will basically delete any prior file with the same radix (index, sections, mana...) found in the CSS file list, i.e. files from a parent skin, allowing you to create an add-type skin and still benefit from a complete rewrite of, say, sections.css. (Subs-Cache.php, Load.php)
+ Added support for m, b and c suffixes, followed by a number. 'm1' will restrict a CSS file to member #1, 'b1' to board #1 and 'c1' to category #1. And another many issues were instantly solved. (Load.php)
! Canonical URLs for category pages were pointing to the homepage. (Boards.php)
* Replaced quote tag's quote icon with dynamically generated CSS. It doesn't look exactly the same across all browsers, but it saves 150 bytes off the final gzipped CSS file. I'm all for that... (index.css, quote.png)