cotonti.com : Wiping HTML out from core https://www.cotonti.com Останні повідомлення в темі Cotonti en Wed, 08 Apr 2026 14:52:10 -0000 Trustmaster #395 is still active. BTW, I think sprites are damn hard to customize. But for standard iconpacks such as Tango it is not too hard.]]> Пн, 20 Вер 2010 02:42:28 -0000 urlkiller
because why dont we use png sprites for the core system images?
so most icons could be done with css?!]]> Пн, 20 Вер 2010 02:22:20 -0000 SunChase Вт, 22 Вер 2009 19:18:01 -0000 Trustmaster an article describing the way this task is to be done. Please read it and help applying it on trunk.]]> Пн, 21 Вер 2009 17:25:39 -0000 Kilandor but guess maybe meant the system folder in skins]]> Нд, 13 Вер 2009 15:54:38 -0000 Trustmaster Нд, 13 Вер 2009 03:10:16 -0000 Kilandor Нд, 13 Вер 2009 01:51:37 -0000 Trustmaster Сб, 12 Вер 2009 23:30:57 -0000 Kilandor All images, icons and HTML resources with PHP embeds are moved to system/resources.php, which is separated into sections by module (PM, PFS, Forums, etc.)
This contains the urls for the images? if so this should be in skin not system.]]> Сб, 12 Вер 2009 18:59:59 -0000 Trustmaster
  1. All images, icons and HTML resources with PHP embeds are moved to system/resources.php, which is separated into sections by module (PM, PFS, Forums, etc.)
  2. Form items, like inputs, selectboxes, textareas, etc. should better be coded in TPL files rather than core or resources.php. TPL tags, required for specific attributes, should be assigned in the core.
  3. Resource elements are provided CSS classes if neccessary. E.g. all icon images have class="icon".
I have started with common, functions and PFS, but it is quite a lot of work overall. So I need assistants to help with this task.]]> Сб, 12 Вер 2009 15:38:55 -0000 Kilandor
Any div's should have a standardized matching class, there shouldn't be any td/tr really.

And english please guys]]> Ср, 09 Вер 2009 14:31:29 -0000 Sergey и будет такая, наверное глобальная переменная img, а $img['bird'] как раз и будет картинкой. Теперь берем и раз, все img и плагином (функцией) куда и в чего хочешь.]]> Ср, 09 Вер 2009 06:00:32 -0000 Sergeich ]]> Ср, 09 Вер 2009 05:08:55 -0000 Trustmaster
Added 2 hours 53 minutes later:

"Assign as PHP strings in skin_name.php" description updated.]]> Ср, 09 Вер 2009 02:04:48 -0000 Kort As regards the poll, with if-blocks "leave as is" would be a good option (still, linebreaks should be wiped out from the php-code!)]]> Ср, 09 Вер 2009 01:56:55 -0000 Trustmaster

Assign many TPL tags and use TPL logic everywhere

Means putting all the HTML directly to those places they appear in templates. Define HTML in templates and assign tags for attributes and contents.

Pros: very pure Model-View-Controller (MVC) design, everything of layout is in the templates.
Cons: tens and hundreds of new {TPL_TAGS} to emerge.

Use spans + CSS for icons, leave the rest alone

Is described and discussed here

Pros: neat CSS for icons
Cons: may result in massive non-semantic markup, doesn't solve problem for everything except icons

Assign as PHP strings in skin_name.php

We could follow the footsteps of language files. The main goal for moving HTML from core to skins is to let the skin makers total control over markup and layout, including small details. But there are hundreds of such pieces and most of them contain HTML mixed with PHP code, so it is very hard to organize. Putting them to PHP strings e.g. $S in skin_name/skin_name.php would let skin makers customize those HTML snippets and keep the flexibility of PHP code.

There should be a default file with resource strings that comes with the core and provides all the necessary strings which will suit many (existing) skins out of the box. And any of those strings can be overwritten in skin_name.php, so you can customize only those strings you need and everything is standardized.

Pros: hit 2 birds with one stone, possible backwards compatibility
Cons: not pure

Questions/suggestions are welcomed.]]> Ср, 09 Вер 2009 01:20:38 -0000