> this seems to get interesting. If you now start to merge these thoughts, you
> could come to the conclusion that fields in the admin interface should be
> feeded from an extensionable xml file as well.
good idea, to me it would be great if you just can declare new fields in xml,
similar to the declarable theme options. but you should also be able to return
custom html for a greater flexability.
example:
<OX>
<OXMENU id="NAVIGATION_ESHOPADMIN">
<MAINMENU id="mxmanageprod">
<SUBMENU id="mxarticles">
<TAB id="tbclarticle_main">
<!--
Declare new oxarticle property
==============================
In this case the markup rendering is done by the shop framework
(should be displayed at the bottom of the article main
tab, maybe in a
fieldset - extension properties. Maybe module authors can
also provide a
position hint like position="before/after active")
-->
<FIELD name="my_new_field_in_article_table" type="bool"
default="1" input="checkbox">
<HELP>With this checkbox you can do...bla</HELP>
</FIELD>
<!--
Define new oxarticle property
=============================
In this case the markup rendering is done by the extension module
-->
<FIELD name="my_new_field_in_article_table" type="bool"
default="1" input="checkbox">
<HELP>With this checkbox you can do...bla</HELP>
<RENDERER cl="a_class_in_module_directory"
fnc="a_method_in_the_class" />
</FIELD>
</TAB>
</SUBMENU>
</MAINMENU>
</OXMENU>
</OX>
class a_class_in_module_directory {
public function a_method_in_the_class($context) {
$context['aViewData']; // <-- all template variables
$context['propertyDefinition']; // <-- representation of the
xml-node with all attributes and child nodes
return 'html'; // rendered by smarty or not
}
}
if you and oxid like the idea i would create patch, as a starting
point. Don't now how much refactoring
is needed to not duplicate the input-type rendering based on
declarations, because this is allready done for
theme-options, maybe here some developer from oxid can jump in.
best regards, Holger
>
> That would serve those who want to have a new tab as well as those who just
> want a checkbox in an existing tab ;)
>
> Best Regards
>
> André
>
> Am 14.07.2011 13:55, schrieb Holger Kohnen:
>>
>> Hi,
>>
>> good point, this way you can also savely extent admin templates, but
>> sometimes you want only add one checkbox and for this a new tab would
>> be to much.
>>
>> best regards, Holger
>>
>> 2011/7/14 Rafael Dabrowski<[email protected]>:
>>>
>>> Hi,
>>> you can add a Tab in menu.xml.
>>> /modules/<modulname>/menu.xml
>>> There you can define the menuestructure.
>>>
>>> Regards
>>>
>>> Rafael
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: [email protected]
>>> [mailto:[email protected]] Im Auftrag von Holger
>>> Kohnen
>>> Gesendet: Donnerstag, 14. Juli 2011 13:19
>>> An: [email protected]
>>> Betreff: Re: [oxid-dev-general] Why no overload of admin-templates
>>>
>>> Hi,
>>>
>>> many modules require admin changes, so one overloading mechanism will not
>>> solve the admin-template-update-problem(atup).
>>> To solve the atup i would like to see a simple hook-functionality, which
>>> should allow module-authors to hook-in new markup to all models, also it
>>> would be great to have the possibility to create new tabs for a model.
>>> For example:
>>>
>>> function myModuleMarkup ($context) {
>>> return '<markup>' . $context['model']->getId() . '</markup>'; }
>>> hookAdmin(array('model' => 'oxuser', 'tab' => 'main', callback =>
>>> 'myModuleMarkup'));
>>>
>>> As callback, one could provide any-php-callback-type.
>>> It would be great if module authors where able to put an admin_init.php
>>> file into their module root folder, which the the shop loads within the
>>> admin bootstrap. This would then be the place to register hooks.
>>>
>>> best regards, Holger
>>>
>>>
>>> 2011/7/13 Kai Gazmaga<[email protected]>:
>>>>
>>>> If it is no problem, Themes would be a nice addition, but no must have
>>>> from my point.
>>>>
>>>> Am 2011 7 13 20:30 schrieb "development"<[email protected]>:
>>>>
>>>>> Hi Kai
>>>>>
>>>>> I would like to have that or even a theme management for he backend
>>>>> templates (just like we have now for the front end).
>>>>> I don't see a reason why we shouldn't have that. Besides CMS' like
>>>>> Joomla!
>>>>> have that too.
>>>>>
>>>>> Grüsse aus Basel
>>>>> Marc
>>>>>
>>>>> ORCA Services AG
>>>>> Herrenmattstrasse 26
>>>>> CH-4132 Muttenz
>>>>> Office Basel: Aeschengraben 10, CH-4051 Basel
>>>>>
>>>>> [email protected]<mailto:[email protected]>
>>>>> T. +41 61 205 80 80
>>>>> T. +41 61 205 80 73 (direkt)
>>>>> F. +41 61 205 80 81
>>>>>
>>>>> www.orca.ch<http://www.orca.ch>,
>>>>> www.orca-services.ch<http://www.orca-services.ch>
>>>>>
>>>>> "We convert your visitors into customers."
>>>>> ________________________________
>>>>> Von: [email protected]
>>>>> [mailto:[email protected]] Im Auftrag von Kai
>>>>> Gazmaga
>>>>> Gesendet: Mittwoch, 13. Juli 2011 19:56
>>>>> An: [email protected]
>>>>> Betreff: [oxid-dev-general] Why no overload of admin-templates
>>>>>
>>>>> Hello out there,
>>>>>
>>>>> after several times in the past I now came accross this topic again.
>>>>> Why do we not have the option to "overload" admin-templates as we can
>>>>> do with frontend-templates?? One simple $this->CustAdminTpl in
>>>>> config.inc.php and the necessary changes in oxConfig::getDir() would do
>>>>> the trick, right?
>>>>>
>>>>> I try to develop modules independant from admin-templates but some
>>>>> special changes need to be done in the admin-templates. This makes
>>>>> updates quite unpleasant.
>>>>>
>>>>> What is your oppinion?
>>>>>
>>>>> Mit freundlichem Gruß / Best regards,
>>>>>
>>>>> Kai Gazmaga
>>>>> VektorDesign - Online-Shops und Programmierung Kai Gazmaga
>>>>> Katharinenstraße 57
>>>>> 73 728 Esslingen
>>>>>
>>>>> Tel.: +49 711 - 25516226
>>>>> Fax: +49 711 - 25518078
>>>>>
>>>>> Mail: [email protected]<mailto:[email protected]>
>>>>> Web: www.vektordesign.de<http://www.vektordesign.de>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> dev-general mailing list
>>>> [email protected]
>>>> http://dir.gmane.org/gmane.comp.php.oxid.general
>>>>
>>>
>>>
>>> --
>>> Holger Kohnen
>>> (Webentwickler)
>>>
>>> Anklamer Str. 35
>>> 10115 Berlin
>>>
>>> [email protected]
>>> http://www.holgerkohnen.de
>>>
>>> 030 / 788 37 22
>>> 0173 / 38 62 791
>>> _______________________________________________
>>> dev-general mailing list
>>> [email protected]
>>> http://dir.gmane.org/gmane.comp.php.oxid.general
>>>
>>> Der Inhalt dieser Nachricht ist ausschließlich für den bezeichneten
>>> Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser
>>> Nachricht oder dessen Vertreter sein sollten, so beachten Sie bitte, dass
>>> jede Form der Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts
>>> dieser Nachricht unzulässig ist. Wir bitten Sie, sich in diesem Fall mit dem
>>> Absender der Nachricht in Verbindung zu setzen. Diese Nachricht wurde durch
>>> einen Virenscanner auf Viren und sonstigen schädlichen Inhalt geprüft,
>>> jedoch wird keinerlei Haftung für Schäden wegen Viren übernommen. Auch wird
>>> keine Haftung für Schäden übernommen, die aus einer Veränderung des Inhalts
>>> dieser Nachricht durch Dritte entstehen können. Wenn Sie auf diese Nachricht
>>> antworten, beachten Sie bitte, dass durch innerbetriebliche Regelungen Ihre
>>> E-Mail eventuell auch durch einen anderen als den bezeichneten Adressaten
>>> gelesen werden kann.
>>> This message is confidential and intended solely for the use of the
>>> individual or organization to whom it is addressed. Should you not be the
>>> intended addressee of this message or his or her representative, please note
>>> that publication, replication of the contents by any means or further
>>> communication of the content is not permissible. Should you have received
>>> this message in error, please notify the sender. This message was scanned by
>>> a virus and content filter but liability for any viruses transmitted will
>>> not be accepted. Furthermore we are not liable for damages arising from
>>> alteration of the contents of this message by a third party. If you reply to
>>> this message please keep in mind that due to innerorganizational regulations
>>> your message could probably be read by someone else than the intended
>>> addressee.
>>> _______________________________________________
>>> dev-general mailing list
>>> [email protected]
>>> http://dir.gmane.org/gmane.comp.php.oxid.general
>>>
>>
>>
>
>
> --
>
>
>
>
> _______________________________________________
> dev-general mailing list
> [email protected]
> http://dir.gmane.org/gmane.comp.php.oxid.general
>
--
Holger Kohnen
(Webentwickler)
Anklamer Str. 35
10115 Berlin
[email protected]
http://www.holgerkohnen.de
030 / 788 37 22
0173 / 38 62 791
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
