Ticket #7 (closed Feature Request: fixed)

Opened 3 years ago

Last modified 2 years ago

Refactor MainUI / Smarty templates usage

Reported by: benoitg Assigned to: benoitg
Priority: normal Milestone: WifiDog Auth Server 1.0
Component: Auth server, Code Refactoring Keywords:
Cc:

Description (Last modified by benoitg) 

The rationale is that since we don't use it for
anything significant anymore, we should remove the
dependency.  This will mostly require writing a proper
error handling functions.

Attachments

Change History

11/04/05 11:54:20 changed by fproulx 

Logged In: YES 
user_id=1245118

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

12/26/05 21:22:09 changed by fproulx

  • summary changed from Remove Smarty support to Refactor MainUI / Smarty templates usage.

01/06/06 09:10:00 changed by MaxHorvath

  • component changed from Auth server: Code Refactoring to Auth server: Code Refactoring.

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

01/06/06 16:36:52 changed by fproulx

  • milestone set to WifiDog 1.0.

01/22/06 23:53:58 changed by benoitg

  • version deleted.
  • description changed.

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.

01/23/06 01:04:58 changed by 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 ...

02/22/06 11:35:23 changed by max-horvath

  • status changed from assigned to new.
  • owner changed from nobody to max-horvath.
  • version set to Auth Server SVN.

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

02/22/06 11:35:31 changed by max-horvath

  • status changed from new to assigned.

03/23/06 04:42:54 changed by max-horvath

  • status changed from assigned to new.
  • owner deleted.

05/02/06 09:36:09 changed by benoitg

  • owner set to benoitg.

06/09/06 10:39:44 changed by fproulx

  • status changed from new to closed.
  • resolution changed from None to fixed.

01/22/07 16:04:48 changed by benoitg

  • component changed from Auth server: Code Refactoring to Auth server, Code Refactoring.

Add/Change #7 (Refactor MainUI / Smarty templates usage)




Action