The Horror! Templated Components
Go To This Ticket's Page
Creator	Nevir
Public or Private	Public Private tickets are only accessible to you and to DKPSystem.com staff Public Tickets are visible to everyone)
Status	Closed
Type	Suggestion
Section of the Site	Advanced Layout Options and CSS
Urgency	(4 votes)
Rating	(4 votes)
Description: I have no idea how this would pan out in your code base (I'm assuming a ton of work), but the #1 request that I have at the moment is the ability to template all the (or at least the major) components on DKPSystem. This would give us tremendous power when laying out/tweaking the sites, with hopefully little investment on your part... after it's all initially coded up :( This also ties into my #2 request of making all the output XML(/XHTML)-valid, and to reduce tables - all in order to get the browser out of quirks mode :P So, what I'm suggesting is: Add an extra step for rendering various components and widgets by passing them through your templating language Let users modify those templates (I'm guessing a system similar to how phpbb exposes its templates - dropdown and a large text box :P) Create documentation, possibly automatically, that lists the variables you can use in each template Have much cake! Templates that I would currently find the most useful to modify: User account widget News posts Forum threads Forum posts
Official DKPSystem.com Comments No official comments yet

What exactly are you referring to here?



This one is pretty new, but is indeed a great idea.



Both of these are planned, and after this coming wave of new desperately needed features, I'll bump it up on the list.

--
It's all in the reflexes.

oh sorry - the <!-- System:Login --> widget

Ahh Yes. That one has also been planned, for a long time, I just never did it.

I'm actually planning on breaking it apart, so rather than having a seperate template file for it, you would just be able to put it in the layout file directly, specifiying where it's core components would go.


So as a few examples:


<!--Login:LoginInput--> = the login field
<!--Login:PasswordInput--> = The password field
<!--Login:Characters--> = the list of characters
<!--Login:PasswordRecovery--> = The password recovery link

I assume that's something you're envisioning.

--
It's all in the reflexes.

Yeah, that's pretty much what I'm looking for - having some sort of conditionals in the templates would be useful too (i.e. even something as simple as <!-- If:Variable --> stuff <!-- EndIf:Variable --