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
8011
The Pub / [Archive] Re: Logo Madness
« on August 24th, 2011, 11:35 PM »
I see your point Chris, it's just that... I'm not in the mood for logos these days. I completely lack inspiration, and when I have no artistic feeling in me, I can't judge others' works either...
8012
Development blog / Re: A nice kick in the CSS
« on August 24th, 2011, 11:08 PM »
What is it with everyone parlant français now? Please, someone think of the Arantors :P
8013
Features / Re: New revs
« on August 24th, 2011, 10:50 PM »
rev 964
(2 files, 6kb)
! Allow URLs with $ and % in them to be turned into pretty URLs, e.g. page index templates using a flexible start shortcut (board=1.0). (PrettyUrls-Filters.php)
* More 'skins' fixes. (Themes.php)
(2 files, 6kb)
! Allow URLs with $ and % in them to be turned into pretty URLs, e.g. page index templates using a flexible start shortcut (board=1.0). (PrettyUrls-Filters.php)
* More 'skins' fixes. (Themes.php)
8014
Other software / Re: Baibai vblamer
« on August 24th, 2011, 08:17 PM »
The team vote had been mentioned to me at the beginning but then I didn't hear from it again... :^^;:
Does that mean we have a majority of friends in the SMF team now? :p
Thanks to everyone for voting for me. Now let's start voting for whether or not I should lead the SMF dev team... eheh. After I'm done with Wedge v21.0, of course.
Maybe I should log back into the site... Maybe I'll find out that I've been unbanned as well :lol: oh well, let's not ask for too much shall we...?
Does that mean we have a majority of friends in the SMF team now? :p
Thanks to everyone for voting for me. Now let's start voting for whether or not I should lead the SMF dev team... eheh. After I'm done with Wedge v21.0, of course.
Maybe I should log back into the site... Maybe I'll find out that I've been unbanned as well :lol: oh well, let's not ask for too much shall we...?
8015
The Pub / [Archive] Re: Logo Madness
« on August 24th, 2011, 08:14 PM »PS at 61 YY I must be getting on for the oldest member here :whistle:
As for the logo... Well, I still like CJ's monochromatic implementation, but it freakin' won't work on dark backgrounds...
Plus, readability isn't at its best I'd reckon.
8016
Features / Re: New revs
« on August 24th, 2011, 08:07 PM »
rev 963 --- the last part of the commit will take more time...
(13 files, 12kb)
* Tweaked member list to be more welcoming (more padding) and use less HTML (bandwidth nazi.) (Memberlist.template.php)
! Setting css('display', '') on an item doesn't work when its display is hidden through a class (like the hide class). I knew that, but I'd forgotten to fix that in a couple of instances. Modders, use toggle() instead, it's cooler anyway. (editor.js, topic.js)
! Help entry typo for pretty URLs. (Admin.language.php)
* Some breathing space for the main menu in iOS. (index.iphone.css)
* The usual code cleanup. (upgrade.php, ManageBoards.php, ManagePermissions.php, Subs-List.php, index.template.php, Login.template.php)
- We don't really need that 'skins' variable in the themes table... Also tweaked another 'skins' entry. (install.sql, ManageBoards.php)
(13 files, 12kb)
* Tweaked member list to be more welcoming (more padding) and use less HTML (bandwidth nazi.) (Memberlist.template.php)
! Setting css('display', '') on an item doesn't work when its display is hidden through a class (like the hide class). I knew that, but I'd forgotten to fix that in a couple of instances. Modders, use toggle() instead, it's cooler anyway. (editor.js, topic.js)
! Help entry typo for pretty URLs. (Admin.language.php)
* Some breathing space for the main menu in iOS. (index.iphone.css)
* The usual code cleanup. (upgrade.php, ManageBoards.php, ManagePermissions.php, Subs-List.php, index.template.php, Login.template.php)
- We don't really need that 'skins' variable in the themes table... Also tweaked another 'skins' entry. (install.sql, ManageBoards.php)
8017
Features / Re: New revs
« on August 24th, 2011, 08:00 PM »
rev 962 --- multipart commit.
(5 files, 12kb)
* Rewrote constructPageIndex() to be tighter -- smaller and better HTML, CSS and JavaScript. As a bonus, pretty URLs are also correctly rewritten in the process, hopefully without exceptions. (Subs.php, script.js, index.css)
* Started work on simplifying theme/skin combinations. id_theme=0 should have skin='' (meaning it's taken from theme_skin_guests), and skin='' on other id_themes means the root (skins folder). (Load.php)
* Although it technically works, it doesn't make sense to set the cursor type on 'a:hover', it should instead be directly on 'a'. (index.css)
! SMF bug: session errors when using new PHP5 feature that allows to set more hash bits for the valid session characters. Thanks live627 for the report and rawlogic for the ready-made fix! (wedge_api.php, Load.php)
(5 files, 12kb)
* Rewrote constructPageIndex() to be tighter -- smaller and better HTML, CSS and JavaScript. As a bonus, pretty URLs are also correctly rewritten in the process, hopefully without exceptions. (Subs.php, script.js, index.css)
* Started work on simplifying theme/skin combinations. id_theme=0 should have skin='' (meaning it's taken from theme_skin_guests), and skin='' on other id_themes means the root (skins folder). (Load.php)
* Although it technically works, it doesn't make sense to set the cursor type on 'a:hover', it should instead be directly on 'a'. (index.css)
! SMF bug: session errors when using new PHP5 feature that allows to set more hash bits for the valid session characters. Thanks live627 for the report and rawlogic for the ready-made fix! (wedge_api.php, Load.php)
8018
Other software / Re: Baibai vblamer
« on August 24th, 2011, 07:35 PM »I wasn't even told :lol:
Posted: August 24th, 2011, 07:34 PM
Also, Kat seems to be back in the team...? And in the Doc team, apparently?!
8019
Other software / Re: Baibai vblamer
« on August 24th, 2011, 05:09 PM »
What does it say? I'm not logging in just for that...
The fact that he resigned from the team?
The fact that he resigned from the team?
8020
Other software / Re: Fork discussion at SMF
« on August 24th, 2011, 09:43 AM »
I think a lot of capable people are going to be building their own SMFs... Sometimes even when it just could have been all made into a mod... And you know why? Because mods in SMF are painful :P
Although I'm not sure the weight of having to support an entire SMF codebase is going to be worth it!
Basically, I think what SMF should be going, if it HOPES to have a chance at surviving, is moving its SVN to git, and allowing anyone to commit patches for the lead devs to check and push into the core.
Since the SMF devs are obviously unable to do the amount of work they're expected to do, I'm sure the SMF team will eventually rely on this.[1] I'm not saying it won't be exploitative of external developers.... But that's the 'spirit' of open source... :whistle:
Although I'm not sure the weight of having to support an entire SMF codebase is going to be worth it!
Basically, I think what SMF should be going, if it HOPES to have a chance at surviving, is moving its SVN to git, and allowing anyone to commit patches for the lead devs to check and push into the core.
Since the SMF devs are obviously unable to do the amount of work they're expected to do, I'm sure the SMF team will eventually rely on this.[1] I'm not saying it won't be exploitative of external developers.... But that's the 'spirit' of open source... :whistle:
| 1. | After all, that's what they did last year with me: when all devs were on vacation, they fucking offered me a dev position in late May when it was all sunny outside, I did all of the work for a month, and then when they refused to give me a consolidated position I left the job. I mean, I did something like 90% of the commits in June and July 2010. |
8021
Features / Re: Bookmarks
« on August 24th, 2011, 09:33 AM »This is a grand idea. I wish I would have thought of it. ;)
It's something Pete and I have been veeeery interested in implementing for a long time. :P (t's been He even found a "dirty hack" to implement it in one line of code, which actually was the moment when I realized Pete could think outside of the box (the key to innovation) and was someone I could work with and learn things from. :P
Anyway, yeah, 'followed' and 'ignored' topics are going to be there... But since they don't require big database rewrites, I *think* it will probably slip to Wedge 1.1 (or, heck, anything after 1.0, even if it's 1.0.5 I don't give a damn :P Depends on Pete's opinion on versioning.)
8022
Development blog / Re: A nice kick in the CSS
« on August 23rd, 2011, 12:00 AM »
Credit for what? Does anyone know of anything he did for the SMF community that wasn't linked in one way or another to the selling of a commercial version of his work...?
I can hardly give the benefit of the doubt to someone who's widely recognized by the SMF community for his tendency to monetize everything he does for them.
So far, most of his changes to the SMF codebase (according to his commit logs) was to rename all entries of SMF into his fork name. I don't know about you, but when I'm seeing something like "SMF wishes to thank everyone who spent countless hours on the project", I'm not going to change SMF into my fork name after I only worked on it for a couple of hours... It shows a lack of respect for SMF itself. I wait a year before I did the same...
Until proven otherwise, to me he's just going to release an SMF with his mods (and the mods that were given to him -_-) built in, and on top of that he'll be selling a "pro" version of his forum with the "pro" (commercial) versions of the same mods... It's all about getting extra exposure for his $250 'suite'.
Let's just say only time will tell which conception of a SMF fork will make it into the hearts of the SMF community. But I think I already know...
Oh, well, I guess that's it now, I wrote a blurb about the damn fork... ::)
I can hardly give the benefit of the doubt to someone who's widely recognized by the SMF community for his tendency to monetize everything he does for them.
So far, most of his changes to the SMF codebase (according to his commit logs) was to rename all entries of SMF into his fork name. I don't know about you, but when I'm seeing something like "SMF wishes to thank everyone who spent countless hours on the project", I'm not going to change SMF into my fork name after I only worked on it for a couple of hours... It shows a lack of respect for SMF itself. I wait a year before I did the same...
Until proven otherwise, to me he's just going to release an SMF with his mods (and the mods that were given to him -_-) built in, and on top of that he'll be selling a "pro" version of his forum with the "pro" (commercial) versions of the same mods... It's all about getting extra exposure for his $250 'suite'.
Let's just say only time will tell which conception of a SMF fork will make it into the hearts of the SMF community. But I think I already know...
Oh, well, I guess that's it now, I wrote a blurb about the damn fork... ::)
8023
Features / Re: These two bytes may not matter to you...
« on August 22nd, 2011, 11:28 PM »
Okay, here's how I envision the thing...
Theme 1
Skin A (root)
Skin B (add-type)
Skin C (replace-type)
As you may have seen in the new revs, this is now represented as such in the pick theme page:
Theme 1
Skin A
Skin B
Skin C
Which makes more sense than having Skin C as a child of Skin A (or Skin B as a root skin, like it used to be.)
Now, Wedge allows you to choose the default *theme + skin* combination for the forum, for guests (so that the forum would be using Theme 1B by default for instance). With the variables $modSettings['theme_guests'] (already in SMF) and $modSettings['theme_skin_guests'] (new to Wedge.)
Thing is, if admin adds Theme 2, which itself has 3 color variations... What if they want a secondary variation to be the default when users choose Theme 2 for themselves?
- Wedge doesn't implement the ability to choose a default skin for a non-default theme, because SMF doesn't have 'skins' per se, and as such, there's nothing else to choose from, apart from the theme ID...
- Adding the ability to choose a default skin for a secondary theme might be overkill. In terms of UI, it could be more complicated than necessary, add clutter to the admin area's theme page.
- I think the most logical solution would be to keep the situation where the admin can choose a default theme+skin, but outside of this one, if users choose another theme, they'll get the root skin for it (except, of course, if they directly choose another skin within the theme.)
The goal really is to both maintain simplicity for users, and customizing for admins.
Again, as such, I have no idea what that 'skin' variable is for, in the {db_prefix}themes table. I probably added it at the beginning of my experiments, and forgot to remove it later when I simply had a fallback to the skins (root) folder...
Theme 1
Skin A (root)
Skin B (add-type)
Skin C (replace-type)
As you may have seen in the new revs, this is now represented as such in the pick theme page:
Theme 1
Skin A
Skin B
Skin C
Which makes more sense than having Skin C as a child of Skin A (or Skin B as a root skin, like it used to be.)
Now, Wedge allows you to choose the default *theme + skin* combination for the forum, for guests (so that the forum would be using Theme 1B by default for instance). With the variables $modSettings['theme_guests'] (already in SMF) and $modSettings['theme_skin_guests'] (new to Wedge.)
Thing is, if admin adds Theme 2, which itself has 3 color variations... What if they want a secondary variation to be the default when users choose Theme 2 for themselves?
- Wedge doesn't implement the ability to choose a default skin for a non-default theme, because SMF doesn't have 'skins' per se, and as such, there's nothing else to choose from, apart from the theme ID...
- Adding the ability to choose a default skin for a secondary theme might be overkill. In terms of UI, it could be more complicated than necessary, add clutter to the admin area's theme page.
- I think the most logical solution would be to keep the situation where the admin can choose a default theme+skin, but outside of this one, if users choose another theme, they'll get the root skin for it (except, of course, if they directly choose another skin within the theme.)
The goal really is to both maintain simplicity for users, and customizing for admins.
Again, as such, I have no idea what that 'skin' variable is for, in the {db_prefix}themes table. I probably added it at the beginning of my experiments, and forgot to remove it later when I simply had a fallback to the skins (root) folder...
8024
Development blog / Re: A nice kick in the CSS
« on August 22nd, 2011, 10:18 PM »
Ah, I had a new blog post in the making, and then I dropped it... I was adressing the other SMF forks, and then kinda lost my inspiration when it came to discuss vblamer's project while trying not to be insulting... :P
8025
The Pub / Re: Copyrights
« on August 22nd, 2011, 10:09 PM »
Okay, here it is...
http://wedge.org/license/
I only modified the end of the file. (And changed www.wedge.org to wedge.org -- this isn't the 20th century anymore, Toto.)
Are we good now...? :P
http://wedge.org/license/
I only modified the end of the file. (And changed www.wedge.org to wedge.org -- this isn't the 20th century anymore, Toto.)
Are we good now...? :P