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
8206
The Pub / [Archive] Re: Logo Madness
« on August 7th, 2011, 12:16 PM »
Yeah but maybe a poll is a bit restrictive even so.
8207
Features / Re: New revs
« on August 7th, 2011, 09:59 AM »
rev 910
(10 files, 12kb)
! Fixed Safari 2.x not using readOnly on form submit (heck, I'm not even sure if this bug was valid to begin with?), and optimized invertAll. (script.js)
! Helper functions should use camelCase, thanks John. (PersonalMessage.php)
* Finished version renaming stuff. (Admin.template.php)
! What was 'Wedge (originally SMF) Add-on' language string supposed to mean in the Admin area's detailed version page? It's only giving us the main version... And if it's supposed to be the version of the package that made the upgrade... Isn't it supposed to be the same? (Admin.language.php)
- Removed more of the auto-update code for AeMe. (ManageMedia.template.php, Media.template.php)
* Updated some outdated file headers. (Subs-Aeva-Sites.php, Media.language.php)
rev 911
(0 files +5-5)
! Grmpf... Was in a hurry to grab something to eat, and forgot to rename the files like I was supposed to in rev 910. (temp.*.php)
(10 files, 12kb)
! Fixed Safari 2.x not using readOnly on form submit (heck, I'm not even sure if this bug was valid to begin with?), and optimized invertAll. (script.js)
! Helper functions should use camelCase, thanks John. (PersonalMessage.php)
* Finished version renaming stuff. (Admin.template.php)
! What was 'Wedge (originally SMF) Add-on' language string supposed to mean in the Admin area's detailed version page? It's only giving us the main version... And if it's supposed to be the version of the package that made the upgrade... Isn't it supposed to be the same? (Admin.language.php)
- Removed more of the auto-update code for AeMe. (ManageMedia.template.php, Media.template.php)
* Updated some outdated file headers. (Subs-Aeva-Sites.php, Media.language.php)
Posted: August 7th, 2011, 09:57 AM
rev 911
(0 files +5-5)
! Grmpf... Was in a hurry to grab something to eat, and forgot to rename the files like I was supposed to in rev 910. (temp.*.php)
8208
Features / Re: New revs
« on August 7th, 2011, 09:54 AM »
rev 909
(29 files +5-5, 104kb)
* Replaced $forum_version with WEDGE_VERSION constant. It was already defined, just not used. This eliminates the need to globalize $forum_version each time you need it. Version number also gets rid of the 'Wedge' element. We only want a number! (index.php, install.php, smfinfo.php, upgrade.php, current-version.php, detailed-version.php, Calendar.php, Class-DB.php, Credits.php + Who template collateral, Feed.php, ManageMaintenance.php, ManageMedia.php, ManageServer.php, PackageGet.php, ScheduledTasks.php, Subs-Package.php, Subs.php, index.language.php, Packages.template.php)
* More renaming of SMF to Wedge in versioning and things like that, like fixing and optimizing the JS for the detailed version page. It was all very messy to begin with and it's done across this commit and the next anyway. (Install.language.php, admin.js...)
* Renamed Findmember to FindMember, Jseditor to JSEditor, Jsoption to JSOption, Printpage to PrintPage and Unreadreplies to UnreadReplies. Both for function names and file names. The next commit will fix the filenames (due to a SVN limitation.) (index.php, temp.*.php)
* Simplified admin JS object, by shortening some ridiculously long variable names and hardcoding version compare DOM IDs. Who would change them anyway?! SMF2 has a tendency to encourage the multiplication of settings when it should instead be deciding whether or not something is likely to be changed in the future. (Admin.php, admin.js)
* list (), not list()... (upgrade.sql, current-version.php, latest-packages.php, latest-themes.php)
(29 files +5-5, 104kb)
* Replaced $forum_version with WEDGE_VERSION constant. It was already defined, just not used. This eliminates the need to globalize $forum_version each time you need it. Version number also gets rid of the 'Wedge' element. We only want a number! (index.php, install.php, smfinfo.php, upgrade.php, current-version.php, detailed-version.php, Calendar.php, Class-DB.php, Credits.php + Who template collateral, Feed.php, ManageMaintenance.php, ManageMedia.php, ManageServer.php, PackageGet.php, ScheduledTasks.php, Subs-Package.php, Subs.php, index.language.php, Packages.template.php)
* More renaming of SMF to Wedge in versioning and things like that, like fixing and optimizing the JS for the detailed version page. It was all very messy to begin with and it's done across this commit and the next anyway. (Install.language.php, admin.js...)
* Renamed Findmember to FindMember, Jseditor to JSEditor, Jsoption to JSOption, Printpage to PrintPage and Unreadreplies to UnreadReplies. Both for function names and file names. The next commit will fix the filenames (due to a SVN limitation.) (index.php, temp.*.php)
* Simplified admin JS object, by shortening some ridiculously long variable names and hardcoding version compare DOM IDs. Who would change them anyway?! SMF2 has a tendency to encourage the multiplication of settings when it should instead be deciding whether or not something is likely to be changed in the future. (Admin.php, admin.js)
* list (), not list()... (upgrade.sql, current-version.php, latest-packages.php, latest-themes.php)
8209
The Pub / [Archive] Re: Logo Madness
« on August 7th, 2011, 07:59 AM »
Hence why I haven't compiled the list yet... :P
A 'regular' poll using the SMF system would probably not work here. I should make a post or web page with all of the items and a number, and ask for you guys to vote for your top 3 or something.
A 'regular' poll using the SMF system would probably not work here. I should make a post or web page with all of the items and a number, and ask for you guys to vote for your top 3 or something.
8210
Features / Re: Calendar dates
« on August 7th, 2011, 07:29 AM »
@John> To most people outside the US, 'Independence Day' is an action movie ;)Quote from Arantor on August 6th, 2011, 01:28 PM Uhh... Well, in French it's Noël and all our hearts warm at the mention of the name 'Noël', but not when we hear about 'Christmas'. Most of us know what Christmas is, but it doesn't strike a chord like Noël. In Japanese it's only called 'Kurisumasu' (direct phonetic transcription) because to them it's a bit like Halloween: an imported, recent non-religious fun day. In Spanish it's Navidad, in German it's Christtag, actually if you go look at Wikipedia and all the links to other languages, Christmas is *only* used in English... :^^;:
So, to me, it should be {cal_christmas} or something like that... ;)Quote I never heard of Cinco de Mayo before, though... I think translating cal_mexday to 'Fête Nationale du Mexique' would make more sense to me. Much more sense. Or maybe have cal_mexday_title to do that. And we add hover titles if available.Quote Yep. Although if we translate entries, it may not be as useful... So, what's best?
Nao, all I was getting at is that I'm not bothered by trying to localise the names of the holidays themselves - Christmas is the same in most languages,
So, to me, it should be {cal_christmas} or something like that... ;)
and stuff like Cinco de Mayo, is written and referred to as in Spanish, even in non Spanish speaking communities.
Producing packages of different dates would be good though.
8211
Features / Re: These two bytes may not matter to you...
« on August 7th, 2011, 07:09 AM »
Here's the thing: I don't really see ourselves updating the file version manually on each upgrade ('did I update that file since the last update? I'll check against the last copy...'). It's tedious and will definitely be on our list of 'annoying things that don't encourage us to do early & frequent releases'. I'd rather we do a mass update on @version 0.1 to @version 0.2 etc...
So, basically, forcing people to reupload all files should they want to check all file versions in that area, doesn't seem like a big deal to me.
Or we could have Wedge auto-update its files itself, though some magical device... Although it wouldn't work on servers where the Apache owner can't overwrite files from the FTP owner ('nobody'? Or something else. Ayway. It's not like it happens everywhere.)
Why the heck am I awake and working at 7am on a Sunday...?!
So, basically, forcing people to reupload all files should they want to check all file versions in that area, doesn't seem like a big deal to me.
Or we could have Wedge auto-update its files itself, though some magical device... Although it wouldn't work on servers where the Apache owner can't overwrite files from the FTP owner ('nobody'? Or something else. Ayway. It's not like it happens everywhere.)
Why the heck am I awake and working at 7am on a Sunday...?!
8212
Features / Re: These two bytes may not matter to you...
« on August 7th, 2011, 01:01 AM »
- Did my own benchmark... Constant is faster for me, too, by about 15%.
- Haven't seen anywhere where $forum_version is redefined. As for package emulation, it first stores the version into $context['forum_version'] and then redefines it.
Going for the constant, then...! :)
Just FYI -- code is cleaner now. Having no issues.
I noticed, however, that the 'detailed versions' admin page was broken. Is it also broken in the current dev?
This is due (among other things) to jQuery not supporting $('#randomidwithaperiod.likethis') as an ID name. Had to escape the period. Also, dozens of recently added files were not in the full list of files.
Honestly though -- I don't really see the point of retrieving a version Id for all files in the list. Is it to avoid forcing admins to upload all of their files again when just a few have changed? It's just annoying -- not updating the version number list, but updating the file list remotely!
- Haven't seen anywhere where $forum_version is redefined. As for package emulation, it first stores the version into $context['forum_version'] and then redefines it.
Going for the constant, then...! :)
Posted: August 6th, 2011, 11:33 PM
Just FYI -- code is cleaner now. Having no issues.
I noticed, however, that the 'detailed versions' admin page was broken. Is it also broken in the current dev?
This is due (among other things) to jQuery not supporting $('#randomidwithaperiod.likethis') as an ID name. Had to escape the period. Also, dozens of recently added files were not in the full list of files.
Honestly though -- I don't really see the point of retrieving a version Id for all files in the list. Is it to avoid forcing admins to upload all of their files again when just a few have changed? It's just annoying -- not updating the version number list, but updating the file list remotely!
8213
Off-topic / Re: Kudos for Nao & Arantor
« on August 6th, 2011, 10:42 PM »
Even removing the file simply falls back to sans serif. :)
And opera allows replacing fonts out of the box iirc.
Posted: August 6th, 2011, 10:41 PM
And opera allows replacing fonts out of the box iirc.
8214
Features / Re: These two bytes may not matter to you...
« on August 6th, 2011, 10:38 PM »
Pete? A partial answer would be fine ;)
8215
Off-topic / Re: Kudos for Nao & Arantor
« on August 6th, 2011, 08:25 PM »
Okay, okay! I give up. I've reset the css for IMG tags ;)
Now it should behave normally. I suggest you all go back to using [ img ] instead of [ bareimg ]. The only reason for it, indeed, is blogs, and to prevent people from posting large images with an img tag that will put them inline (bad results). But I'm not using blogs as such in here, so there's really no point... Let's just say I'll trust users to properly do linebreaks before adding an img tag.
Mac Sea, I'm fine with 'standing out' if you like, but please :sob: don't ever, ever use Comic Sans... I think I'd be willing to ban anyone using it in a place I'm moderating. :niark:
Now it should behave normally. I suggest you all go back to using [ img ] instead of [ bareimg ]. The only reason for it, indeed, is blogs, and to prevent people from posting large images with an img tag that will put them inline (bad results). But I'm not using blogs as such in here, so there's really no point... Let's just say I'll trust users to properly do linebreaks before adding an img tag.
Mac Sea, I'm fine with 'standing out' if you like, but please :sob: don't ever, ever use Comic Sans... I think I'd be willing to ban anyone using it in a place I'm moderating. :niark:
8216
Features / Re: These two bytes may not matter to you...
« on August 6th, 2011, 08:17 PM »
On my to-do list is a rewrite of the forum version code...
The issue is that it's pretty messy. It's using $forum_version and WEDGE_VERSION (SMF_VERSION) to begin with. $forum_version is never redefined, so I don't see why we couldn't use WEDGE_VERSION everywhere. The only time it's defined out of the usual index files is in install.php where it's set when the recycle bin is enabled (???), and only used once, when it could just as well have used $current_wedge_version... Uh.
Now, $forum_version uses the format "forum version", rather than "version", while the const is just "version". Looking at the code, in most places $forum_version is actually parsed to remove the Wedge at the beginning... I really, really don't see the point in having Wedge in the name. What's it for? We're the only ones setting it, it's not like it's going away.
So... I'd suggest we (I) transform all $forum_version code to use just a version number. I've already done part of it. I'm also considering pushing it further and using WEDGE_VERSION instead, although the const could just as well be removed -- it's always defined, but never used once, except in upgrade.php which won't be used by Wedge anyway (uh.) Vars are slightly faster than consts, but it's not noticeable because it's not used in loops obviously.
The issue is that it's pretty messy. It's using $forum_version and WEDGE_VERSION (SMF_VERSION) to begin with. $forum_version is never redefined, so I don't see why we couldn't use WEDGE_VERSION everywhere. The only time it's defined out of the usual index files is in install.php where it's set when the recycle bin is enabled (???), and only used once, when it could just as well have used $current_wedge_version... Uh.
Now, $forum_version uses the format "forum version", rather than "version", while the const is just "version". Looking at the code, in most places $forum_version is actually parsed to remove the Wedge at the beginning... I really, really don't see the point in having Wedge in the name. What's it for? We're the only ones setting it, it's not like it's going away.
So... I'd suggest we (I) transform all $forum_version code to use just a version number. I've already done part of it. I'm also considering pushing it further and using WEDGE_VERSION instead, although the const could just as well be removed -- it's always defined, but never used once, except in upgrade.php which won't be used by Wedge anyway (uh.) Vars are slightly faster than consts, but it's not noticeable because it's not used in loops obviously.
8217
Features / Re: Calendar dates
« on August 6th, 2011, 12:08 PM »What would be good is providing a package of some description that supplies all the relevant cultural dates, but making them translated doesn't seem to be a big deal to me, more importantly to get the dates provided for different groups.
8218
The Pub / [Archive] Re: Logo Madness
« on August 6th, 2011, 11:59 AM »
I don't think it has great readability. :-/
Okay, here's a logo I made a few days ago... It has a slightly curve reflection inside the text. The triangle/wedge is on the right, and it works 'well' because the text is skewed and thus it all makes it look like the Wedge text is running to the right. (Known issue: it's a bit dark overall. Adding a manually modified version.)
Other than that, err... I don't know, I still like the header logo best for now. :^^;: (Could use a few tricks though.)
Should I make a poll with all the available choices?
Okay, here's a logo I made a few days ago... It has a slightly curve reflection inside the text. The triangle/wedge is on the right, and it works 'well' because the text is skewed and thus it all makes it look like the Wedge text is running to the right. (Known issue: it's a bit dark overall. Adding a manually modified version.)
Other than that, err... I don't know, I still like the header logo best for now. :^^;: (Could use a few tricks though.)
Should I make a poll with all the available choices?
8219
Other software / Re: Nao in SMF2 Credits
« on August 6th, 2011, 11:37 AM »I guess I'm the only one who randomly google's people's name in the credits of open source software that I use?
8220
Features / Re: New revs
« on August 6th, 2011, 11:35 AM »
rev 908
(9 files, 12kb)
- Removed site list's ability to self-update, as I don't see myself updating it outside of the main software's updates themselves. You can update manually from further Wedge updates, obviously. Also removed some outdated code that checked for new Aeva Media versions. (Aeva-Embed.php, ManageMedia.php, ManageMedia3.php, Subs-Media.php, ManageMedia.language.php, Media.language.php)
* Casenazi. (PersonalMessage.php)
(9 files, 12kb)
- Removed site list's ability to self-update, as I don't see myself updating it outside of the main software's updates themselves. You can update manually from further Wedge updates, obviously. Also removed some outdated code that checked for new Aeva Media versions. (Aeva-Embed.php, ManageMedia.php, ManageMedia3.php, Subs-Media.php, ManageMedia.language.php, Media.language.php)
* Casenazi. (PersonalMessage.php)