Discussion of general topics related to the new version and its place in the world. Don't discuss new features, report bugs, ask for support, et cetera. Don't use this to spam for other boards or attack those boards!
Forum rules
Discussion of general topics related to the new release and its place in the world. Don't discuss new features, report bugs, ask for support, et cetera. Don't use this to spam for other boards or attack those boards!
APTX wrote:
When you access a page which is listed in two categorys the menu always switches to the first category.
If you disable a category all subitems appear as tabs... and ytes it doesn't look too good if there are many tabs.
Why would someone disable categories? I just hope the Developers will leave out the module configuration for the final version.
The acp module page is based on a three-level menu. If this gets changed by the admin to two levels there are unexpected results. I do not think this is avoidable, because the menu is built by the template and expects three levels. Disabling a root category though should remove the tab completely (as you see by the .mods category which is there but not visible).
Imladris wrote:
Well it might be beautiful, but it's stupid. All the time you have said that you would use raw html in the ACP fiels and nto templates. Now you've suddenly changed that, even thoguh nobody cares about the template in an ACP. And now i have a 2000+ lines ACP file which i have to remake completely... yet another "let's annoy people" addon.
... Sorry, but you're an idiot. We were all told hundreds of times that EVERYTHING might change totally, at any time. And even if they hadn't said that... if you go around writing 2000+ lines based on CVS code, you only have yourself to blame.
Yeah I'm SURE they changed it JUST because to annoy you! The evil phpBB hates you!
Thank you for the kind reply
Well.. the thing is that there is absolutely no reason why it shoudl be changed to use templates. It could as beautiful as it does now even though it didn't use templates.
This is taken from a post by psoTFX:
As said before, no the ACP will not be templated in the "classical" 2.x fashion. Why? For some very good reasons based on my experiences supporting hundreds, neigh thousands of people since 2.0 was released.
Few style designers ever did anything significant with the ACP. In many cases they didn't even bother altering the templates, merely applied their board stylesheet. The original reason I pushed templatable ACP was for hosting providers et al to offer a customised template consistent with their control panels, etc. AFAIK no provider ever made use of that.
The above led on more than a few occassions to issues ranging from "invisible" text through (to poorly altered template sets) missing options and broken forms.
The complexity of the ACP has (obviously) increased in 3.0. In turn the problems caused by the above two issues can only IMNSHO get worse.
The extra load generated by templating the ACP given the above three points is just a silly further issue that can be avoided.
As has been said, everything can change. The current approach has a lot of benefits, let me name some:
Still the benefit of seperating it from board styles, it is a given style which is not changeable
The ACP now has the same seperation between code and presentation - it would be a kludge to handle the acp differently
The beauty of using all the advantages we have from the template engine, using proper login boxes, proper message boxes/trigger errors, proper confirm pages...
The ACP got rather unreadable with all the html code in it.
If you have built something off from CVS you have to expect the need to rewrite it - we warned everyone to not use CVS.
Acyd Burn wrote:
The ACP got rather unreadable with all the html code in it.
I think that's the most important reason to do it... even if I already wrote some 2000+ lines ACP code as well, it's not that hard to change it to the new approach because you'll be able to use the functionality without any (or only minor) changes within the new style...
I do not think this is avoidable, because the menu is built by the template and expects three levels. yet another "let's annoy people" addon.
