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
8086
The Pub / [Archive] Re: Logo Madness
« on August 17th, 2011, 01:29 PM »
You don't have to feel forced to... Only if you have inspiration!
And read the last couple of pages for guidelines ;)
And read the last couple of pages for guidelines ;)
8087
Features / Re: These two bytes may not matter to you...
« on August 17th, 2011, 01:28 PM »
Pete, just wondering... Did you make sure to remove corresponding $txt variables when you removed tons of features, mainly at the beginning...? Because I still found another unused variable... And I'm starting to wonder if you made the check at all...? Rule of thumb: always check for dependencies when I remove something... :whistle:
Maybe we could, hmm, build some tool that would take all of the $txt variable names and check whether they're used in any template or source file... I'm sure we could remove tons of entries that way!
Maybe we could, hmm, build some tool that would take all of the $txt variable names and check whether they're used in any template or source file... I'm sure we could remove tons of entries that way!
8088
Features / Re: New revs
« on August 17th, 2011, 01:25 PM »
rev 937
(31 files, 30kb)
* Renamed every single remaining smf_ reference to either we_ or we. Too. Tired. Won't. List. Files. (About 30)
- Removed unused $txt['cannot_connect_doc_site'] variable. (Errors.language.php)
(31 files, 30kb)
* Renamed every single remaining smf_ reference to either we_ or we. Too. Tired. Won't. List. Files. (About 30)
- Removed unused $txt['cannot_connect_doc_site'] variable. (Errors.language.php)
8089
Features / Re: New revs
« on August 17th, 2011, 12:51 PM »
rev 936
(68 files +1-3, 91kb)
! Forgot to convert a smf_sess. Also removed the last remaining smf_session_id, and removed a useless test. (Load.php, script.js)
- Removed a couple of outdated files and renamed smf_api to wedge_api (although I doubt we'll ever use it, just like most of the tools.) (wedge_api.php, add_settings-1x.php, boardmod.mod)
* Removed the 'Demo' version type (I don't think we're ever going to release a 'demo'?), renamed CVS version type to SVN, and removed a few CVS filename handling tests (who uses that nowadays?). (current-version.php, Class-DB.php, Subs-Package.php, Themes.php)
* Renamed smfLanguage* and smfUpdate* variables to we*. (tools, admin.js)
* Renamed smf_editorArray to weEditors. (script.js, etc.)
* Renamed smf_oCurrentResizeEditor to weCurrentResizeEditor, and smf_execCommand to we*. (editor.js)
* Renamed smf_openid_* and smf_openID_* to we_openID_*. (index.php, Login2.php, Profile.php, Profile-Modify.php, Register.php, ScheduledTasks.php, Security.php, Subs-OpenID.php)
* Changed Aeva's lookup user agent to something more browsery and with a proper URL for server admins to check. (Aeva-Embed.php)
* And finally, renamed SMF (uppercase) to Wedge wherever it was used to qualify the current software (i.e. not older versions, or proper credit.) (Dozens of files...)
(68 files +1-3, 91kb)
! Forgot to convert a smf_sess. Also removed the last remaining smf_session_id, and removed a useless test. (Load.php, script.js)
- Removed a couple of outdated files and renamed smf_api to wedge_api (although I doubt we'll ever use it, just like most of the tools.) (wedge_api.php, add_settings-1x.php, boardmod.mod)
* Removed the 'Demo' version type (I don't think we're ever going to release a 'demo'?), renamed CVS version type to SVN, and removed a few CVS filename handling tests (who uses that nowadays?). (current-version.php, Class-DB.php, Subs-Package.php, Themes.php)
* Renamed smfLanguage* and smfUpdate* variables to we*. (tools, admin.js)
* Renamed smf_editorArray to weEditors. (script.js, etc.)
* Renamed smf_oCurrentResizeEditor to weCurrentResizeEditor, and smf_execCommand to we*. (editor.js)
* Renamed smf_openid_* and smf_openID_* to we_openID_*. (index.php, Login2.php, Profile.php, Profile-Modify.php, Register.php, ScheduledTasks.php, Security.php, Subs-OpenID.php)
* Changed Aeva's lookup user agent to something more browsery and with a proper URL for server admins to check. (Aeva-Embed.php)
* And finally, renamed SMF (uppercase) to Wedge wherever it was used to qualify the current software (i.e. not older versions, or proper credit.) (Dozens of files...)
8090
The Pub / [Archive] Re: Logo Madness
« on August 17th, 2011, 11:16 AM »
It certainly was.
I do appreciate any contributions, but people have got to admit they're not all on the same level of professionalism. Some contributions are only meant as jokes, some are meant as truthful suggestions and I don't know how to kindly refuse them, so it hurts even more to see more attempts 'in the same vein'. I thought I'd go ahead and try to help people save time by following the guidelines that were built progressively in this topic.
Apparently, it's not enough. I guess it comes down to self-esteem issues, for which I cannot help. My job here is to try and get the best possible logo. I'm not a great designer, and I never denied it. That's why the Wedge community has an opportunity to step up and provide some of their ideas where they can outdo my current skill set. I've seen some fantastic logo offers from Bloc and recently CJ Jackson, and eventually I'm positive we'll have a perfect logo for Wedge (if we don't already have -- sometimes it takes time to get used to something that's not in your usual 'play field'.) And I heartily encourage anyone to make offers. But I'm absolutely sincere when I think ncvettes's logo, while attempting new things, would never be used by himself on his own site. If what he offered was just a mockup (i.e. "I don't have any design skills, but I'm trying some ideas, here's one of them, what do you think?"), he should have said it. Unfortunately, he only said "Here's one".
So, yeah, my comment may not be inspiring. But it was not meant to be. It didn't mean to hurt, either, because it was really written with love for all of the offers that were made here.
I do appreciate any contributions, but people have got to admit they're not all on the same level of professionalism. Some contributions are only meant as jokes, some are meant as truthful suggestions and I don't know how to kindly refuse them, so it hurts even more to see more attempts 'in the same vein'. I thought I'd go ahead and try to help people save time by following the guidelines that were built progressively in this topic.
Apparently, it's not enough. I guess it comes down to self-esteem issues, for which I cannot help. My job here is to try and get the best possible logo. I'm not a great designer, and I never denied it. That's why the Wedge community has an opportunity to step up and provide some of their ideas where they can outdo my current skill set. I've seen some fantastic logo offers from Bloc and recently CJ Jackson, and eventually I'm positive we'll have a perfect logo for Wedge (if we don't already have -- sometimes it takes time to get used to something that's not in your usual 'play field'.) And I heartily encourage anyone to make offers. But I'm absolutely sincere when I think ncvettes's logo, while attempting new things, would never be used by himself on his own site. If what he offered was just a mockup (i.e. "I don't have any design skills, but I'm trying some ideas, here's one of them, what do you think?"), he should have said it. Unfortunately, he only said "Here's one".
So, yeah, my comment may not be inspiring. But it was not meant to be. It didn't mean to hurt, either, because it was really written with love for all of the offers that were made here.
8091
Off-topic / Re: To fork or not to fork - in other words: Hi :)
« on August 17th, 2011, 11:07 AM »
That's the spirit. :)
I couldn't live without that topic. I need it to keep a forum connection with my SVN commits, and Pete's. I would never check the SVN log otherwise, I guess... It's also important for me to correctly convey the activity behind Wedge. Sometimes I won't commit for a couple of days, and then suddenly come up with a huge commit. If you look at the commit dates, you'll quickly notice how regular I've been on the project. As the saying goes, "A commit a day keeps the troller away."
Oh, I have a feeling it'll be in my custom title in a second... :niark:
(We also maintain such a topic for the importer tool SVN, but it's a team private topic for now. Will be made public when we release the importer and if TE doesn't mind.)
I couldn't live without that topic. I need it to keep a forum connection with my SVN commits, and Pete's. I would never check the SVN log otherwise, I guess... It's also important for me to correctly convey the activity behind Wedge. Sometimes I won't commit for a couple of days, and then suddenly come up with a huge commit. If you look at the commit dates, you'll quickly notice how regular I've been on the project. As the saying goes, "A commit a day keeps the troller away."
Oh, I have a feeling it'll be in my custom title in a second... :niark:
(We also maintain such a topic for the importer tool SVN, but it's a team private topic for now. Will be made public when we release the importer and if TE doesn't mind.)
8092
Features / Re: New revs
« on August 17th, 2011, 11:01 AM »
rev 934
(166 files, 100kb)
* Changed the SMF constant to WEDGE, in pretty much all files outside of the theme (automatic replacements, manually checked.) Also started converting regular SMF string to Wedge or whatever the context requires. (index.php, readm... hey, I said pretty much ALL the files, do you honestly think I'm going to list them all?!)
(166 files, 100kb)
* Changed the SMF constant to WEDGE, in pretty much all files outside of the theme (automatic replacements, manually checked.) Also started converting regular SMF string to Wedge or whatever the context requires. (index.php, readm... hey, I said pretty much ALL the files, do you honestly think I'm going to list them all?!)
8093
Features / Re: New revs
« on August 17th, 2011, 10:38 AM »
rev 933
(18 files, 18kb)
* More manual name conversions, this time from _smf to _wedge and smf_ to wedge_. (readme_convert.html, smfinfo.php, latest-packages.php, Admin.php, ManageServer.php, THEMES: Admin, ManageSmileys, ModerationCenter, Packages, Themes, LANGUAGES: Admin, ManageSettings)
- Removed utf8 parameter from the language file manager, considering all language files are now UTF8... (ManageServer.php, Admin.template.php, ManageSettings.language.php)
- SMF bug: removed unused string $txt['identification_by_smf']. (Login.language.php)
(18 files, 18kb)
* More manual name conversions, this time from _smf to _wedge and smf_ to wedge_. (readme_convert.html, smfinfo.php, latest-packages.php, Admin.php, ManageServer.php, THEMES: Admin, ManageSmileys, ModerationCenter, Packages, Themes, LANGUAGES: Admin, ManageSettings)
- Removed utf8 parameter from the language file manager, considering all language files are now UTF8... (ManageServer.php, Admin.template.php, ManageSettings.language.php)
- SMF bug: removed unused string $txt['identification_by_smf']. (Login.language.php)
8094
Features / Re: These two bytes may not matter to you...
« on August 17th, 2011, 10:30 AM »It's fine. Yes, it will reset the session.
Other than the base is there anything we'd actually want to take verbatim from SMF anyway? Seems to me as though it's something we neither want or need to worry about.
I mean, it would be a bit dishonest of us to take code from SMF when we're preventing them to use ours...
I guess bug fixes don't fall into this -- if only because I've myself pointed out bug fixes to them for years, and even made the changelog accessible with the list of fixable bugs...
Also. I'm changing define('SMF') to something else. I could use WE: it's shorter. But it would only save ~200 bytes across the entire project, so... Well. As for WEDGE, it's longer, makes us waste an extra 400 bytes, but OTOH I'd rather have the full software name in here. So I'm changing to WEDGE, please tell me if you disagree. Otherwise, no need to reply ;)
8095
Off-topic / Re: To fork or not to fork - in other words: Hi :)
« on August 17th, 2011, 08:55 AM »
A rough estimate based on feedback. :P
But it doesn't matter whether it is read or not. What matters to me is transparency.
But it doesn't matter whether it is read or not. What matters to me is transparency.
8096
Features: Forward thinking / Re: MySQL only!
« on August 17th, 2011, 08:54 AM »
Interesting.
But Mysql is here to stay. If not, then it's forks will.
We write for real use. If the paradigm shifts to pgsql or whatever, then Wedge will offer such versions.
Right now we just don't think any server with pgsql installed would not already have Mysql installed as well. Focusing on one db system only allows us to save precious time for other features and for speed improvements.
But Mysql is here to stay. If not, then it's forks will.
We write for real use. If the paradigm shifts to pgsql or whatever, then Wedge will offer such versions.
Right now we just don't think any server with pgsql installed would not already have Mysql installed as well. Focusing on one db system only allows us to save precious time for other features and for speed improvements.
8097
The Pub / [Archive] Re: Logo Madness
« on August 17th, 2011, 07:41 AM »
Okay. So what should I do? If I find a logo is not up to my standards, should I let you keep it in that way, and make you waste more time working on more mockups?
Ever heard about constructive criticism?
And what has this got to do with smf anyway?
Ever heard about constructive criticism?
And what has this got to do with smf anyway?
8098
Other software / Re: Fork discussion at SMF
« on August 17th, 2011, 12:11 AM »
A quick one though... (I'm late IRL so I'll be gone after this.)
http://www.simplemachines.org/community/index.php?topic=446856.msg3137769#msg3137769
Thanks for the thumb up. :D However, Angelina, the code you see on Wedge.org is *not* running Wedge. It's specified in the FAQ. But lucky for you, it is true that the resizing code that is in Wedge, is taken from the code I wrote for Noisen.com (the website that served as the starting point for the Wedge.org website, NOT for the Wedge project.) So, yes, Wedge.org pretty much already demoes that for you.
I improved it, nevertheless, like I always like to do -- made it even shorter, slightly faster, and a bit more dependable.
Still, the font size is too small in Wedge.org when viewing it on a smartphone. And avatars are still on the side. Font size changing is done in Wedge (it only takes one line of code), but I'm also planning to move avatars and userboxes to the vertical flow, i.e. above the posts themselves. The point here is that topics should be very readable on smartphones, out of the box. I can't take bets for the other forum pages, though -- my focus was on topic pages really.
PS: permission to reproduce this post on sm.org if need be.
http://www.simplemachines.org/community/index.php?topic=446856.msg3137769#msg3137769
Thanks for the thumb up. :D However, Angelina, the code you see on Wedge.org is *not* running Wedge. It's specified in the FAQ. But lucky for you, it is true that the resizing code that is in Wedge, is taken from the code I wrote for Noisen.com (the website that served as the starting point for the Wedge.org website, NOT for the Wedge project.) So, yes, Wedge.org pretty much already demoes that for you.
I improved it, nevertheless, like I always like to do -- made it even shorter, slightly faster, and a bit more dependable.
Still, the font size is too small in Wedge.org when viewing it on a smartphone. And avatars are still on the side. Font size changing is done in Wedge (it only takes one line of code), but I'm also planning to move avatars and userboxes to the vertical flow, i.e. above the posts themselves. The point here is that topics should be very readable on smartphones, out of the box. I can't take bets for the other forum pages, though -- my focus was on topic pages really.
PS: permission to reproduce this post on sm.org if need be.
8099
Other software / Re: Fork discussion at SMF
« on August 17th, 2011, 12:01 AM »
Was busy tonight (IRL, and the little time I had, I spent on doing and committing revision 932), so I'll have to skip this topic (and all others) for today and deal with them tomorrow. Sorry about that. (Pete seems to be doing fine by himself though :P)
8100
Features / Re: New revs
« on August 16th, 2011, 11:55 PM »
rev 932
(39 files, 32kb -- did all of these manually... ouch >_<)
* Got rid of most display:none's and replaced them with the 'hide' class. (install.sql, Class-Editor.php, Aeva-Foxy.php, Subs.php, TEMPLATES: Admin, BoardIndexInfoCenter, Calendar, index, ManageMaintenance/Media/Membergroups/ ManageNews/Paid/Permissions/Smileys, Media, ModerationCenter, MoveTopic, Packages, PersonalMessage, Post, Profile, Recent, Register, Reminder, Search, SplitTopics, Themes)
* Started converting smf_ to wedge_ or we_, or at least preparing the code for the change. Renamed smfSelectText to weSelectText. (install.sql, readme_convert.html, ssi-examples.php, upgrade.php, latest-news.php, Credits.php, ManageMedia.language.php, Who.language.php, ManageMedia.template.php, script.js)
- detailed-version.js was attempting to be included twice. Wedge didn't let that happen, but might as well not try in the first place, right...? (Admin.template.php)
- Removed smf_session_id fallback -- it's a leftover from SMF 1.0 (emphasis on the zero.) (sha1.js)
+ Although it's a hidden setting, disable_smf_js should be used consistently, including in the moderation center. I'm still leaving it out of the detailed version page, though... It would make sense not to use it there. (ModerationCenter.template.php)
@ Tomorrow: the smf_ automated update :P (Checked them all, the 700+ occurrences, should be good... Except for variables that will get reset.)
(39 files, 32kb -- did all of these manually... ouch >_<)
* Got rid of most display:none's and replaced them with the 'hide' class. (install.sql, Class-Editor.php, Aeva-Foxy.php, Subs.php, TEMPLATES: Admin, BoardIndexInfoCenter, Calendar, index, ManageMaintenance/Media/Membergroups/ ManageNews/Paid/Permissions/Smileys, Media, ModerationCenter, MoveTopic, Packages, PersonalMessage, Post, Profile, Recent, Register, Reminder, Search, SplitTopics, Themes)
* Started converting smf_ to wedge_ or we_, or at least preparing the code for the change. Renamed smfSelectText to weSelectText. (install.sql, readme_convert.html, ssi-examples.php, upgrade.php, latest-news.php, Credits.php, ManageMedia.language.php, Who.language.php, ManageMedia.template.php, script.js)
- detailed-version.js was attempting to be included twice. Wedge didn't let that happen, but might as well not try in the first place, right...? (Admin.template.php)
- Removed smf_session_id fallback -- it's a leftover from SMF 1.0 (emphasis on the zero.) (sha1.js)
+ Although it's a hidden setting, disable_smf_js should be used consistently, including in the moderation center. I'm still leaving it out of the detailed version page, though... It would make sense not to use it there. (ModerationCenter.template.php)
@ Tomorrow: the smf_ automated update :P (Checked them all, the 700+ occurrences, should be good... Except for variables that will get reset.)