Skin development tool instead of skin editor

stefan · 18/09/2013 22:55:35

I have a suggestion to get rid of all the xhtml, xslt and xml files to create when creating a skin.

This can be done in a graphical environment with different containers to make it even more dynamic. Containers can be nested and therefore it is possible to build a structure. At the same time the i18n and translations of the skin will be moved from the files into the database instead. The container definition can be saved in the database too. It would make it much easier for the developer to create skins very fast.

Raphaël Franchet · 19/09/2013 17:26:37

For a design tool its is quite complicate to build.
We are going to launch soon a way to customize by cliking a template, but you won't be able to design it completly of course.

For the i18n part, what is the purpose of moving the skin translation in DB ??? I don't get why it would be faster to develop (as for me it would be the opposite) and more over it will make the maintenance harder to do : if I want to deploy a skin, I have to deploy files+dbscript...

stefan · 03/10/2013 13:49:32

The reason is to keep all text to be translated in one place.

Another way is to have a tool for translators where all text is accessible without IT knowledge.

Translators are really bad programmers!!!

stefan · 03/10/2013 13:58:32

I forgot....also keep text separated from skin layout -> more flexibility and reuse.

Raphaël Franchet · 03/10/2013 14:36:44

All text to translate is a one place per feature (in a i18n/message.xml file).
e.g. :The text of the plugin is associated with the plugin.
This is much more flexible to have it in i18n xml files.
Setting this in a db, would make deploying a plugin or upgrading it much more complicate.
In a application, i18n can be overriden in the web-inf/i18n file to add a new language or override a key.

I think translators will prefer editing a xml file, than editing a sql db.

Text IS separated from layout in Ametys.
I think you did not get how Ametys i18n system works.

Forum Ametys

#1 18/09/2013 22:55:35

Skin development tool instead of skin editor

#2 19/09/2013 17:26:37

Re: Skin development tool instead of skin editor

#3 03/10/2013 13:49:32

Re: Skin development tool instead of skin editor

#4 03/10/2013 13:58:32

Re: Skin development tool instead of skin editor

#5 03/10/2013 14:36:44

Re: Skin development tool instead of skin editor

Board footer