Development Discussion Board

There is nothing but a few charts created during an IRL meetup and some considerations concerning frameworks to use. We will set up GIT soon and post architecture documents as RFC as soon as they are written.

In 3.0: the former. You can alter the HTML after the template engine is done. 3.1 will see <!-- HOOK {NAME} -->, related to the dynamic includes used in the 3.0 captcha plugins -- just looped to include all hooking plugins.

-- the key to a useful hook system is plentiful interspersing of hook calls in the code. this does not exist in 3.0 -- to be complete it should also support hooks in the templates. this, ttbomk, does not exist in 3.0 -- without chaining it's not useful. again, ttbomk this is not part of 3.0 -- with...

Things like database abstraction are in place regardless of the architectural pattern. As to MVC: MVC, as the very first pattern, goes back to the very first OO GUI applications and is to this day much better suited for persistent applications. That does not mean desktop applications per se, but rat...

Well, a phorum - or rather Drupal - style hook system is very crude and not appropriate for 4.0 . The 4.0 architecture, as it is planned at the moment, goes far beyond simple hooks by relying on dependency injection and queued manipulation of data objects. We will see how that will play out. You mig...

Many of the aspects that were handled by bulletin boards are moving to social sites like facebook, that is a trend which is just happening. Forums bloomed with the "every single entity has a homepage" idea of the net, social communities are collecting everything again. We will certainly see some asp...

Let me see if I can make this any simpler, not promising anything but here goes: Today: With 3.0.4 the way I utilize the software I can define all regular users permissions utilizing just one group, 'Registered users' < - 1 group I do not have any groups or forums specifically defined to moderate p...

The logic is quite simple:

The feature is enabled iff it is both enabled globally and locally. It is logic:
qr_enabled = qr_enabled_globally ∧ ∃ x. qr_enabled_locally x

Or reversed, QR is disabled:

qr_disabled = ¬qr_enabled_globally ∨ ∀ x. ¬qr_enabled_locally x


Cheers,
~H

I think perhaps you are not understanding. Unless there was a way I could assign 'New member post limit' to a custom group or a pre-defined group of my choosing then no. If I could, then I could simply assign that permission to my 'Registered users' group and have the same effective behavior that I...

Interesting notion of fairness

QR will be disabled in the release packages.