[Phpmyadmin-devel] Transition to template-based framework

[Michael Keck]

Hi,

downloading phpMyAdmin includes php files and template files.
Compilation and caching is done by the local environment.

It mean:
We will have new subdirectories called:

    * skins/theme_name/
      there are stored all things wich have directly to do with
      layout and theming (I will name it Front-End)
      with subfolders
          o styles
            for the theme/layout and jQuery-UI (Theme Roller)
          o jscripts
            for theme/layout specified functions
          o images
            for the theme/layout specified images
          o templates
            html files with TWIG-Syntax
    * libraries/twig/
      template class
    * jscripts/jquery/
      all new jQuery things
    * plugins/
      for TinyMCE and others
    * _cache
          o templates
          o jscripts
          o styles
          o images (for browsers which can't handel png's)
          o files (uploading files like SQL-Dumps, tempfiles for exporting)
      this directory and any of it's subdir is dynamicly created

I prefer, to use for language and configuration files XML-structure to
support the usage
in javascript and php.

I think the rest shouldn't be needed to modify.

Michael

Am 09.03.2010 14:46, schrieb Marc Delisle:
> Michael Keck a écrit :
>   
>> Hello,
>>
>> Am 09.03.2010 14:19, schrieb Michal Čihař:
>>     
>>> Hi
>>>
>>> Dne Mon, 08 Mar 2010 18:26:36 +0100
>>> Michael Keck <sfnet at michaelkeck.de> napsal(a):
>>>   
>>>       
>>>> ... if I should use a PHP-Framework, I'm thinking we should use the newest
>>>> Symfony and if released I would prefer use Symfony Reloaded 2.0
>>>> (http://symfony-reloaded.org/). The final release of Reloaded 2.0 is
>>>> planned for
>>>> *late 2010* and will only support *PHP 5.3.2*. This mean I (and others
>>>> to) would
>>>> have more time for integrate Symfony in PMA.
>>>>     
>>>>         
>>> Maybe it was not clear from me, but I think that we should really go
>>> just to templates, because using some framework would require much more
>>> changes in the code.
>>>   
>>>       
>> Okay I see this point ... then I will start with Twig.
>>     
> Michael,
> what is your plan? When someone downloads a future phpMyAdmin, will he 
> get plain PHP that was compiled by Twig from the code base + templating 
> syntax, or will he get the code base + templating syntax itself?
>
> (I have not experienced Twig yet, just read a bit on their site).
>
>
>   
>>>> Should we open a separated development folder for this project?
>>>>     
>>>>         
>>> Just a separate branch. Preferably wait with creating it after moving
>>> to git (I'll post schedule later today).
>>>   
>>>       
>> No problem I can wait .... (I've not done anything cause im clonig at
>> moment). But
>> many thanks.
>>     
>>>> Is it possible to make discussion about comments for html-output? It
>>>> would be
>>>> helpfull for me, to search in whole PMA-Scripts for it, and then sperate
>>>> PHP from
>>>> HTML. Many Thanks ;)
>>>>     
>>>>         
>>> I don't know what kind of comments you want, but as HTML output is
>>> really spread around the code, adding comments to identify it and then
>>> separate it in another step looks like double work.
>>>   
>>>       
>> I mean: if html is generated with php (like echo/print ...) * only in
>> new code *,
>> that would help me. Not in the current code, thats overkill ;)
>> I prefer: /* <!-- HTML OUTPUT --> */ in php code. For direct HTML output
>> (not with
>> php echo/print etc.) I'm have a good script to search after in my IDE ;)
>>     
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phpmyadmin.net/pipermail/developers/attachments/20100309/f5e5471b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x25C35262.asc
Type: application/pgp-keys
Size: 1711 bytes
Desc: not available
URL: <http://lists.phpmyadmin.net/pipermail/developers/attachments/20100309/f5e5471b/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x25C35262.asc
Type: application/pgp-keys
Size: 1711 bytes
Desc: not available
URL: <http://lists.phpmyadmin.net/pipermail/developers/attachments/20100309/f5e5471b/attachment-0001.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x25C35262.asc
Type: application/pgp-keys
Size: 1711 bytes
Desc: not available
URL: <http://lists.phpmyadmin.net/pipermail/developers/attachments/20100309/f5e5471b/attachment-0002.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x25C35262.asc
Type: application/pgp-keys
Size: 1711 bytes
Desc: not available
URL: <http://lists.phpmyadmin.net/pipermail/developers/attachments/20100309/f5e5471b/attachment-0003.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 291 bytes
Desc: OpenPGP digital signature
URL: <http://lists.phpmyadmin.net/pipermail/developers/attachments/20100309/f5e5471b/attachment.sig>