Wedge

[Commit revision 58ec45a]
Author: Nao
Date: Fri, 09 May 2014 14:35:02 +0200
Stats: 4 files changed; +101 (insertions), -102 (deletions)

• This is a noticeable overhaul of some of the main menu mechanisms...
• Rewrote main menu template to use recursion. While there's nothing to account for depth levels beyond what we currently have, it's still cleaner, clearer and shorter than the previous version. Saves 150 bytes of PHP, which is nice. (index.template.php)
• Moved some of the main menu's top entries (media gallery, member list) to sub-entries of the 'home' menu. Also moved the Logout button to the 'profile' menu. (Subs.php, index.css, index.english.php)
• Renamed 'sub_items' to just 'items' in the main menu. (Subs.php, index.template.php)
• Renamed array_insert's 'parent>child' relationships to 'parent child'. I thought of '>' for CSS inheritance reasons, but really, CSS already has simple spaces for inheritance, so why bother... (Subs.php)
• Saved a few CSS bytes by hiding login/register rules from members, and logout rules from guests. (index.css)
• Removed the 'Search' button from the header, since it's (1) obvious it's a search box given it's icon, (2) already there in the search popup that shows up when you click the input box. (index.template.php)

---

[Commit revision b943c9f]
Author: Nao
Date: Fri, 09 May 2014 14:53:07 +0200
Stats: 5 files changed; +8 (insertions), -27 (deletions)

• Removed 'latest smiley sets' feature. Let's be realistic, it'll never be activated. I've got more important things to do... (ManageSmileys.template.php, ManageScheduledTasks.english.php)
• If for some reason the sidebar-type menu should get activated, it should at least get moved to the actual sidebar, rather than the main area... (Subs-Menu.php)
• Forgot the opening h4. (index.template.php)
• Random commenazi. (Post.template.php)

[Commit revision 2862012]
Author: Nao (Signed-off)
Date: Fri, 09 May 2014 14:55:08 +0200
Stats: 3 files changed; +18 (insertions), -17 (deletions)

• sub_items => items. (calendar/CalendarMenu.php, lang_cache_flush/LangCache.php, wedgedesk/src/Subs-WedgeDesk.php)
• Making use of array_insert's fun rewrite. (calendar/CalendarMenu.php)

Possibly a problem with how the file system is handled on your server. Sometimes, a web server has no direct access to the hard drive, it goes through an extra layer, and there's a short delay between the moment you write data, and the moment you can retrieve it.

In Wedge, loadSource will first get a /core/app/ source file, then strip its comments, save it to /gz/ (cache folder), and load that version. If the filesystem doesn't see the file as avaiable even though it was written, this could generate your error. Although, I think it should first generate an error saying the files wasn't found..? Maybe I'm not doing that.

PS: sorry guys, I'm not posting a lot these days. Please keep in mind that I'm working hard on many features of Wedge at the same time, and I just don't feel like discussing them because I don't know what will make it to the final cut.

There's already a team page by default. Just click the Credits link in the footer...

However it only lists Admins right now.

[Commit revision 39591f6]
Author: Nao
Date: Tue, 06 May 2014 12:10:03 +0200
Stats: 2 files changed; +31 (insertions), -34 (deletions)

• More helper functions for the database class. wesql::query_row('query') will return array(0 => first_column, 1 => second_column..), query_assoc() will return an array of associative results, query_all will return an array of these associative arrays (with multiple results, if any), and query_rows() does the same with numeric arrays. (Class-DB.php)
• Just showing that you can save 200 bytes of code just by using query_all instead of regular wesql code, and cache_get_data with a callback instead of a cache_put_data fallback. (Subs-Editor.php)
• Of course, you don't HAVE to use all of these shortcuts... They may use a bit more RAM and CPU time (but not much!), so I wouldn't recommend them on critical areas; you can always use the old code if you want. But anywhere else..? Be my guest. Enjoy the freedom.

[Commit revision abc9cc7]
Author: Nao
Date: Sat, 03 May 2014 10:12:22 +0200
Stats: 1 file changed; +25 (insertions), -25 (deletions)

• A follow-up to (already) Pete's optimization from January 2011 where the oldTopicDays code is skipped if not used later. Thanks. (Display.php)
• Yes, Pete, I'm a regular lurker (if not contributor) at AAF. You're lucky I don't want to reply to one of your posts and tell you what I think about something you said about me. That would be messy.

[Commit revision a4a1400]
Author: Nao
Date: Thu, 01 May 2014 21:36:50 +0200
Stats: 1 file changed; +3 (insertions), -2 (deletions)

• Getting these entities to behave with messages is complicated. Because westr::safe will disregard the location of the text it's transforming, I've decided to go back on this and just have plain entities protected as well, instead of kept that way. If you need to use a special UTF8 character in your posts, you can always google for it, and paste the actual character into your post... Personally, I'm done with preparsecode stuff for now. (Post2.php)

---

[Commit revision e739d0b]
Author: Nao
Date: Thu, 01 May 2014 21:42:48 +0200
Stats: 2 files changed; +63 (insertions), -42 (deletions)

• Oh yes, I forgot to commit my actual rewrite of preparsecode which I mentioned in the last commit... Uh.
• Fixed quick edit and regular edit/post, when it comes to handling entities and URLs. (Class-Editor.php, topic.js)
• The entire 'modulo' trick for code tags is just what it is, a smart trick, but ultimately it'll probably fail to recognize malformed posts. I've replaced it with a proper method, wedit::is_protected, which is probably a bit slower, but is only called when posting, so it's not like it's a big deal. (Class-Editor.php)

[Commit revision 9965000]
Author: Nao
Date: Wed, 30 Apr 2014 19:03:21 +0200
Stats: 3 files changed; +2 (insertions), -6 (deletions)

• I'm officially tired of watching out for uses of PHP 5.3+ in code that could get run in the installer. From now on, the test will be done on index.php (it's fast enough not to bother), and will just return an error message in English, because... Well, if you don't speak a word of English and don't know what PHP is, you should let someone else handle your forum's administration... (index.php, install.php, Install.english.php)