Wedge

Revision: 508
Author: arantor
Date: 16:56:19, 20 January 2011
Message:
! Length parameter should have been in the truncate function (Class-String.php)
----
Modified : /trunk/Sources/Class-String.php

Revision: 506
Author: arantor
Date: 11:32:46, 20 January 2011
Message:
! Move draft post settings into their own little menu (Admin.php, ManagePosts.php, Admin.english.php)
----
Modified : /trunk/Sources/Admin.php
Modified : /trunk/Sources/ManagePosts.php
Modified : /trunk/Themes/default/languages/Admin.english.php


I like the revision to the buttons - they're back to being as 3D-ish as they were before IMO, but the rounded corners are a nice touch.

The only search type input I see that's affected is the one in the admin panel, but that's not looking right anyway.

Revision: 499
Author: arantor
Date: 13:13:59, 19 January 2011
Message:
! Made constant variable injection (e.g. {db_prefix}, {query_see_board}) into query engine extensible without any modifications to Class-DB being required by modders. (Class-DB.php, Load.php)
----
Modified : /trunk/Sources/Class-DB.php
Modified : /trunk/Sources/Load.php

Revision: 496
Author: arantor
Date: 12:14:07, 19 January 2011
Message:
! Scheduled tasks (regular and imperative) threw errors in browsers since the content was being requested as an image and returned in text/html MIME type (ScheduledTasks.php, Subs-Scheduled.php)
! Little tidying up of actions (index.php, Announce.php, SendTopic.php, Reporttm.php)
----
Modified : /trunk/Sources/Announce.php
Added : /trunk/Sources/Reporttm.php
Modified : /trunk/Sources/ScheduledTasks.php
Modified : /trunk/Sources/SendTopic.php
Modified : /trunk/Sources/Subs-Scheduled.php
Modified : /trunk/index.php

This is a very tough question to answer. Certainly there are a lot of features in Wedge that many will not use - not every forum owner wants to have a blog system built in, for example. Nor the calendar, nor <insert feature here>

But big features like that - like blogging support, like the gallery, like the calendar - these are features we have in the core so that we can maintain them. All too often mods get neglected over time - having them in the core means they don't get forgotten about.

The calendar is a particularly odd example: many SMF users didn't want the calendar in the core, it being a feature they didn't use. But there is another group of people who would actually go elsewhere if the calendar were removed/left to be neglected. These people love having it available and want it to be more powerful than it was.

So the approach we've gone for is that we've added these features in, but in a way that we hope doesn't make it feel too big or scary - and kept the performance aspect too.


Interesting parallel, really, is Microsoft Word. Word adds new features every release, and while some consider it bloaty, the bottom line is that any user might only use 10% of its features - but if each user uses a different 10%, it caters to a lot more people as a result - and this is something we've tried to keep in mind.

We're not going to add every little thing we've thought of - and there are plenty of things we've rejected from being in the core for just that reason. But the goal we have is to make it easier to make them as add-ons that 'just work' and require little maintenance over time.

What will likely happen is that once the core is stable and the ability to expand it through add-ons is mature enough, I'll start turning some of the 'would be nice to have, but not in core' things into add-ons, but we'll see how that turns out - it really requires the core to be mature enough to achieve that first.

Revision: 492
Author: arantor
Date: 07:57:21, 19 January 2011
Message:
! Sync to SMF 10337
 ! Integrated output buffers can now use static functions in classes (Subs.php)
----
Modified : /trunk/Sources/Subs.php

Well, we're talking a small job really, it's not significant in terms of effort (it should be the matter of a few if statements and an array declaration). But there is the matter of doing things on a whim, of course.

Hmm.