I've mentioned this before, this is a new "example use"

"dev code" under "devloper chat"

I dont know if anyone has seen SMF, but check Jakes new site, and you will se a "tree structure" for the boards

atm, we have "categories" and "boards", but this is limit to those 2 levels.

it is possible (is it not) for this to be a plugin..

re: plugins - although they work, atm they are only useful if you dont want to modify the way eoCMS does something, in this case how it handles "boards.php" and their structure. In another case, process floww of "sending a PM" (for save draft, as opposed to send)

hmm i had an idea about adding new stuff to the functions. What if the call() was a class? That way the functions could be extended...

as long as it does not mean changing existing themes/plugins etc, an returned the "text", then yeah, maybe, but do a test of it first.

the other thing to remember is that the -info arrays can store function data too.

in this case, "sub boards" would just extend the category & board structure of "Boards.php", by adding non-category linked boards, so there is only need for admin panel options, and sql INSERT/DELETE/UPDATE (not CREATE, ALTER and DROP) which is "simple", but more importantly, a different sql_query and, "IndexForm" (and possibly "ViewBoard.php") layout output

in the case of "PM-draft" the changes are "less", an extra button, but in page processing, the code needs to insert a "save no send" function. the db needs to then output a "drafts" folder (like "inbox" or "outbox")

(I have not checked the db structure for PM's, but if its like the rest, its a "key"=>"value" assigment, which makes adding new "sections" easy, cos nothing is hard coded)

Apart from the need for a new "-info engine", to get these working in the current code (using the new "-info" format to help) will ahve a huge impact on what can and will be developed in the near future, as I forsee that after the FINAL='0.8.2' release, and any last minute bugs or fixes, there will be a period or supplying and/or creating addon only code and features to eoCMS. So for an adon to be able to "patch" into the system will allow for a lot of flexibility..

.. as long as it remains simple (maybe not to implement the engine/patch system, but to develop addons themselves) and still allows for the eoCMS "core" to maintain security, and flexibility towards the other addon components, and content..

( ..epic most are the norm today.. )

OK, update..

although this has been on the cards, in reality it cant be coded until the "dynamic db support" is added (function replacements) and that wont be done (by me) until the -info functions are running.

part of the -info format requires "I dont know what db this uses" db creation and updating, and so it will the new "dynamic db support" installed to work properly (sql_create & sql_alter), neither of which exist in the current MySQL/SQLite db code..

I am even thinking of a "sql_upgrade" function, that can intelligently use "COPY" & CREATE or ALTER to do db upgrades without loosing data, or making the db unusable

The -info format is looking good, and if the plugin part of the code is fully operational, things like "table testing" will be needed, and a lot of potential plugins can get off the ground..