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
7876
The Pub / [Archive] Re: Logo Madness
« on September 10th, 2011, 09:06 AM »
Chris, can you try working from the same base as I do? I think we're onto something :P

I'm attaching it here. Play with the text's Drop Shadow settings (it's at 50% here but it gives better results at small sizes when setting it to 100%, for instance.)

Readability isn't great here, but you get to play with font colors, too!

PS: if you can't get the font to be like below, make sure 'PT Sans' is installed.
Posted: September 9th, 2011, 05:13 PM

Another one with the 'w' letter split. (Ungrouped)
Posted: September 9th, 2011, 05:36 PM

Or that...
Posted: September 10th, 2011, 08:56 AM

The last ones work well on dark backgrounds, too.
7877
Off-topic / Re: Post count fever
« on September 9th, 2011, 11:08 PM »
Less impressive but still: the previous revision (not the latest one) was my 700th commit to the SVN. :eheh:
7878
Features / Re: New revs
« on September 9th, 2011, 11:06 PM »
rev 991
(22 files +2, 28kb)

- Removed entities_convert option from Media area, and related code. We're UTF-only now, why would we use entities? (install.sql, Aeva-Subs-Vital.php, ManageMedia.php, ManageMedia.language.php, Media.language.php)

* Renamed aeva_utf2entities() function to aeva_string(), because even though we no longer convert entities, it still does some good things. For now. (Aeva-Foxy.php, Aeva-Gallery.php, Aeva-Gallery2.php, Aeva-Subs-Vital.php, ManageMedia.php)

! Fixed 'unlinks' in message index and unread posts/replies. (MessageIndex.php, Unread.php, UnreadReplies.php, MessageIndex.template.php, Recent.template.php)

! Fixed message index always showing page 1 in pretty URL mode. (QueryString.php)

! Security file checks would show error messages twice. (Subs.php)

! Event delayer was incorrectly removed if empty (e.g. board index). (Subs.php)

! SMF bug: incorrect link in 'href' member of the topic array. (Unread.php, UnreadReplies.php)

! Long URLs would break the layout in the error log... Cut these strings after 80 chars. Maybe I should simply insert a soft hyphen... (Errors.template.php)

+ Added IE9 and IE10 workarounds to the Warm skin. With a funny story in the IE9 one... (Warm/index.ie9.css, Warm/index.ie10.css)

* Micro-optimizations. (ManageMaintenance.php, Subs-Members.php, Subs-Post.php, Subs-PrettyUrls.php)
7879
Features / Re: These two bytes may not matter to you...
« on September 9th, 2011, 10:33 PM »
About new, what I mean is that their code basically ends the page with ";topicseennew" instead of ";topicseen#new". The start page is already accounted for at this point.
Since I've never seen a topicseennew link, means the string is built and never used...
7880
Features / Re: These two bytes may not matter to you...
« on September 9th, 2011, 10:31 PM »
Doesn't topicseen help with performance...?
7881
Development blog / Re: Anniwersary
« on September 9th, 2011, 09:27 PM »
Hey, I'm a sucker for the best of all-- Locutus!
7882
Development blog / Re: Anniwersary
« on September 9th, 2011, 09:15 PM »
An offline Borg unit? Must be painful! Sorry, must be 00000000!1
7883
Features / Re: These two bytes may not matter to you...
« on September 9th, 2011, 08:53 PM »
- I don't know and I don't want to know, come to think of it... :lol: Good thing you're our DB specialist here :P

- That's the thing: I shouldn't have to tweak any settings... The search engine offers me to sort by 'most recent topics'. It should return the latest messages in order. Perhaps it actually returns the latest topics in order -- i.e. by topic ID instead of msg_id, I haven't checked, but it doesn't work, that's my point... Weights are totally irrelevant here.

- Okay, SMF bugs... While working on fixing a bug of mine (wrong link for new posts), I noticed a few inconsistencies in SMF:
--- in MessageIndex, the new_href link ends with ";topicseen". In Recent.php, these links don't. This needs to be harmonized...
--- the 'href' link is wrong. It ends with a test which, in one case, adds "new" to the URL... It should be "#new", I reckon. I guess that link was never used anywhere.

Any opinions? I have to go eat...
7884
Features / Re: These two bytes may not matter to you...
« on September 9th, 2011, 06:00 PM »
Quote from Arantor on September 9th, 2011, 05:56 PM
Testing for equality plus a CASE is probably faster than MIN when you have to apply to every single row in a virtual table, especially one that's on disk because it's a filesorted table. And, possibly, for PGSQL/SQLite compatibility, who knows.
Hang on... You're telling me that long CASE THEN ELSE END line is going to be *faster*? How come? :lol:
I'll trust you on that but... It means I have to rewrite all of my MIN() and MAX() calls then :P
Quote
Quote
(Yeah, I'm trying to make sense out of the search system and understand why the fuck it won't sort posts by date like I asked it to... >_<)
Did you change the weights?
That's the thing... As a lambda user, I don't want to have to change obscure search settings! I want it to work like any normal guy would do the sorting: take the most recent post in the list, then the second most recent... Etc.
7885
Features / Re: These two bytes may not matter to you...
« on September 9th, 2011, 05:52 PM »
(Then it's settled.)

An amusing one... (Search2.php)

Code: [Select]
'age' => '((m.id_msg - t.id_first_msg) / CASE WHEN t.id_last_msg = t.id_first_msg THEN 1 ELSE t.id_last_msg - t.id_first_msg END)',

I know CASE is supposed to be pretty fast, but... Faster than MIN()?!

Code: [Select]
'age' => '((m.id_msg - t.id_first_msg) / MIN(1, t.id_last_msg - t.id_first_msg))',

Wouldn't that be simpler...?
The wonders of mysql....

(Yeah, I'm trying to make sense out of the search system and understand why the fuck it won't sort posts by date like I asked it to... >_<)
7886
Features / Re: New revs
« on September 9th, 2011, 04:34 PM »
rev 990
(22 files, 19kb)

* Took a chance and replaced all sSessionVar/sSessionId variables from the JS code with globals. Considering that just like in SMF, the session ID is already on every page (because of the header toggler), it won't make a difference security-wise, it'll just be shorter. Less bandwidth use means more love. (BoardIndex.php, Class-Editor.php, ManageMedia2.php, TEMPLATES: BoardIndex, Display, index, ManageBans, ManageBoards, ManageMaintenance, ManageMembergroups, ManageNews, ManagePaid, ManagePermissions, MessageIndex, PersonalMessage, Profile, SCRIPTS: editor, pm, post, script, suggest, topic)
7887
Features / Re: These two bytes may not matter to you...
« on September 9th, 2011, 04:01 PM »
@PantsMan> In oral French, 'que' is pronounced like a 'c' (or 'k'), except for the word 'que' itself, where you pronounce the 'e' (as in 'linger'). It's a mute 'e', basically. So maquereau is pronounced mah-crow. ma-q-ro.
Quote from Arantor on September 9th, 2011, 03:49 PM
Well, any place it's accessible from the script is a problem, of course, and making it directly more accessible from the page if it's compromised isn't particularly clever - but at the same time, it's really not an issue because any place that it's *currently* actually used, you can query for the session ID anyway.
Yeah...
Quote
All the objects that currently require a session ID are all fed it, they're passed an object going in, which is stored into the object itself - like when a new instance of weToggle is created, one of the parameters given to it is the session, but it's then stored in this.opt. So when you create a new instance of it, you can refer to that object's .opt and get the session, and since there's a weToggle that uses the session on every page for the header...
That's where it's silly. The weToggle on all pages. I wouldn't do without it, especially if forum owners are going to use the header to put a 1024x768 div, or a naked picture of Susan Boyle...
Quote
There isn't really a good method of avoiding it, unfortunately. Either we don't have it and open ourselves up to CSRF type deals, or we do and risk session stealing.
I'd rather take the latter. As of now, putting sSessionVar into a we_* variable increases risks by zero percent. Unless of course someone releases a theme where the toggler is disabled... But then, they'd also have to remove the toggle from the homepage's board info center (not that it's a vital toggler though... Might as well remove it), remove quick edit, quick reply and things like that... And even then, there are still plenty of 'hidden' inputs on the page with the session stuff in plain view.

What would you rather have? Eh...
7888
Features / Re: Template skeleton!
« on September 9th, 2011, 03:47 PM »
I'm just not sure about this for now -- I want it to be done, but I'm a bit rusty when it comes to managing uploads... Been a couple of years since I last jumped into media code!
7889
Features / Re: These two bytes may not matter to you...
« on September 9th, 2011, 03:38 PM »
Re: elite club, we're in agreement... Considering I never understood layers even when working on AeMe (in which they were used by Dragooon, who certainly understood them :P), I'm sure most modders are like me.
Because I analyzed thoroughly index.template.php when I started working on SMF years ago, I can safely say that if a feature is very prominent there, and documented somewhere, it's bound to be better noticed. Which is why I wanted the index template to have a fallback $context['skeleton'], *not* the Wine skin (which would have made more sense, as it is.) I may change my mind later but that's what I though ;)

And it's documented in Warm/skin.xml (which is where I put all of the comments really...), and in the Load and Subs files (hopefully.)

Re: macros, I made the change this morning -- I'm not surprised it was so quick to do. I still have to start work on converting loadSubTemplate() to loadBlock(), but since I do everything manually to avoid errors, this one will be longer... :P

Re: pimp, actually the French 'official' word for pimp is proxénète, and the common word is maquereau (mackerel -- a pimp woman used to be called 'mère maquerelle' a century ago), often shortened to just 'mac'. 'Maquereau' is pronounced exactly the same as 'macro' (the 'r' is pronounced, of course.)

Okay, another one...

I thought long ago of getting rid of all the sSessionId etc in JavaScript and replacing them with a global variable that we'd set up on every page. I don't see any reason for not doing it -- security-wise, it's exactly the same as putting the variables into a function parameter, really... I just wanted to post about the fact that I'm working on it right now -- if you have any issues with this, please get back to me ASAP so that I can revert my work before I commit it ;)
7890
Features / Re: Template skeleton!
« on September 9th, 2011, 03:17 PM »
Okay, just keep me posted :) I feel like the current implementation is a work in progress, even though it's probably fully functional and 95% done -- but I'm sure there are ways it can be made more helpful to designers. :)
Posted: September 9th, 2011, 03:12 PM

Missed that post...
Quote from Arantor on September 9th, 2011, 02:03 PM
Hmm, yes, that is an interesting point. The current solution is 'nice', it's straight forward, it's elegant, but it doesn't allow for adding more complex data to the attachment like the popup would.
It can be done through Ajax, really... Like, I'm simply selecting the file, then if the File API is supported, it starts uploading it and adds a box somewhere, where I can enter data. Then I also add another file input to upload something else. (Adding it above the rest, so I can upload several files without having to scroll...)
(Heck, the good thing with the file API is that IIRC it also allows for multiple file selection... It needs to be implemented, too.)
Quote
The stuff around attachments is pretty complex, but not for the obvious reason: it's not that it just uploads stuff and does error handling, but that it has a complicated habit of stashing stuff in session. Specifically that if you upload a file or two while posting but there's an error, the files are preserved in the temporary folder, with the details for them (for renaming/moving to the actual attachments folder) in session.
Hmm, didn't know that...
Well, I guess this is the kind of thing that would have to go, unless we implement it into the media area.
Posted: September 9th, 2011, 03:16 PM

(Split and moved to a non-blog area.)