Refactor MainUI / Smarty templates usage

[benoitg]

 free javascript hosting  Acheter Medicaments  Comprar Medicamentos sin receta  where to Buy Generics online no prescription  Achat generique en ligne france

[fproulx]

Logged In: YES 
user_id=1245118

Should'nt this RFE be changed for "Refactor MainUI / Smarty templates 
usage", kinda.

[MaxHorvath]

Well, instead of removing Smarty support we should be removing every HTML from our PHP code!

[benoitg]

The final decision was that the refactoring would be done by using a Smarty to create "MacroTemplate?" where it makes sense to do so. Despite this decision, the goal isn't for every group to use custom templates. The "normal" channel for customisation will be (once implemented): -Custom CSS (a simple theming engine will built into wifdog to allow this) -Support for placing Content blocks in predefined areas.

To make this possible, the following will progressively be done: -Move all layout to CSS everytime it is technically possible to do so. -Rewriting some interface elements as "static" Content objects. -Improve the content management, but retaining the "WifiDog is a content presentation tool, not a content creation tool" philosophy.

So, "It makes sense to move html to Smarty template" was defined as "When it will improve maintenance", and more specifically meets one of the following criterias -It's likely a group would have to make changes to the HTML because there are currently no other mechanism to support customisation that is likely to be required. -All the HTML in a single php script was 100% presentation (In a MVC sense) -The template even if small contains HTML reused in lots of places.

The goal is NOT to remove all HTML for PHP files "just because I read it's more professional". You need a proper justification to create a very small template that wouldn't contain any significant presentation logic.

The goal is to arrive to about 30 templates total for the entire system.

[max-horvath]

I agree ...

What I'd like to know if we can start to work on this issue or if we should still wait for Dana being ready with his work?

If he needs more time, maybe we should already start to refactor the code ... I'm pretty sure, implementing the new layout (I mean no CSS-layout) would also be much easier then ...

[max-horvath]

Almost done with it ... so I'll accept the ticket ...