[TYPO3-hci] HCI for managing Templates

[Lars Thalheim]

Hello,

I also use Sysfolders to organize my templates plugin-wise. Nevertheless I
suppose not to setup a Sysfolder for every plugins templates because usually
it is only one or two templates used per plugin. If you had a Sysfolder for
each plugin, the pagetree would soon become pretty crowded.

So I'd suggest a different behavior. Maybe the ExtMan could ask - while
installing the plugin - if there should a Templates-Sysfolder should be
created and also create a default template there (if answered accordingly).
This way it would remain everyones own responsibility to organize the
templates. But it could be made simpler, especially for Typo3 rookies.


__________________
 
THAMEY - Engineering
Lars Thalheim
Karl-Hromadnik-Str. 6
81241 München
 
lars.thalheim at thamey.de
Tel: +49 89 6660 7779
Fax: +49 89 66607643

-----Ursprüngliche Nachricht-----
Von: typo3-team-hci-bounces at lists.netfielders.de
[mailto:typo3-team-hci-bounces at lists.netfielders.de] Im Auftrag von
Alexander Koger
Gesendet: Samstag, 20. Mai 2006 22:59
An: typo3-team-hci at lists.netfielders.de
Betreff: [TYPO3-hci] HCI for managing Templates

Hi List,

for me (as a programmer) managing Templates and TS, CSS and all the related
stuff
programmers do within the BE is still HCI. Maybe this fact gives me a more
human touch. ;-)

Managing Templates via Offline-Editor and ftp is a very basic thing.
So when working with the dmail-extension, i had an idea.
Why not build a template in the way dmail builds the content for
newsletters.

  SysFolder for Newsletters                ->               SysFolder for
Templates
      Page for Newsletter                      ->                   Page for
Template
          ContentElement for Content      ->
ContentElement for SubPart


Having some template files for every extension is neccessary but really not
comfortable.
You will always RTFM to find the location of the sample template files.
Within the template files you will find thousands of subparts and maybe you
have to handle a foreign language in parallel.
So translating dmail was really a pain.

So getting these templates into the db will give us :
- Support for Versioning
- Support for Backup
- Support for BE-User-Rights instead of stupid file access restrictions and
errors
- Support for Designworkflows
- Support for i18n

And this is how it could look like:

 Sysfolder "Templates"
     Sysfolder "News Templates"
         Template "Tpl with tables" (News Template)
             SubPart "List"
             SubPart "Archive"
             SubPart "Latest"
             ...
         Template "Tpl with divs" (News Template)
             SubPart "List"
             SubPart "Archive"
             SubPart "Latest"
             ...
     Sysfolder "Direct Mail Templates"
         Template "Tpl with tables" (DMail Template)
         Template "Tpl with divs" (DMail Template)
         Template "Tpl for Mails" (DMail Mail Template)
         ...
     Sysfolder "Calendar Templates"
         Template "Tpl for XHTML" (Calendar Template)
         Template "Tpl for PDA" (Calendar Template)

Every extension will have an own sysfolder.
When installing the extension, it could create default templates, which then
could be copied and modified.
When using an extension, just point to the Page and Subpart to use.
Or control the behaviour by using TS.


Ok, that's it.
Would be nice getting someone's  thoughts about this idea.

Greets,
Alex







_______________________________________________
TYPO3-team-hci mailing list
TYPO3-team-hci at lists.netfielders.de
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-hci


-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.6.1/344 - Release Date: 19.05.2006




-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.6.1/344 - Release Date: 19.05.2006