Lindsayanng Posted July 26, 2011 Share Posted July 26, 2011 I have noticed that a few modules put some pretty important everyday "task" screens in their "configure" page instead of inside of an admin tab. This makes for a relatively mucky user experience for the store owner. I have to explain that some tasks for exporting orders can be found by hovering over "ORDERS" in the admin but others require him to go to "MODULES" and then find the module and click CONFIGURE> I really want to get all of the important interactive tasks for these modules out of the "configure" and really leave the configure page for configuring settings on modules. I haven't done too much with the back end so would appreciate input and suggestions 1 Link to comment Share on other sites More sharing options...
shokinro Posted July 26, 2011 Share Posted July 26, 2011 good point. I kind of agree that we should keep module screen for configuration only. for most functions to be implemented in tab or sub-tab function at back office admin tabs. but sometimes it is difficult to separate and identify the separations. I will keep this in mind in future module development. Link to comment Share on other sites More sharing options...
Lindsayanng Posted July 27, 2011 Author Share Posted July 27, 2011 My strong suit is user interface and user experience design - ecommerce is something I do on the side.. That being said, if you ever need any direction I am happy to give it. Also, that being said, what would the process be from moving this stuff out of the configure page and into a tab? Is it as simple as creating a tab .php file and moving the code over Link to comment Share on other sites More sharing options...
shokinro Posted July 27, 2011 Share Posted July 27, 2011 It depends what you want to do and what is your requirement. It could be easy ans also it could be difficult. First you have to create and register a tab. Then you need to create class for that tab and the clsaa must be inherits/extends the AdminTab class. You must follow the same structure of AdminTab. The stansard function is thewre, you dont to override the function if the stand fuction fits your needs. Link to comment Share on other sites More sharing options...
Lindsayanng Posted July 27, 2011 Author Share Posted July 27, 2011 your explaination is a little too vague for me to follow. Is there a tutorial somewhere that explains how to register a new tab and what the "structure of AdminTab" means. Link to comment Share on other sites More sharing options...
shokinro Posted July 27, 2011 Share Posted July 27, 2011 I am thinking of write a tutorial, but don't have time. here is the sample code for registering a new tab $parentid = Tab::getIdFromClassName('AdminShipping'); $tab = new Tab(); $tab->id_parent = $parentid; $languages = Language::getLanguages(); foreach ($languages AS $language) { $tab->{name}[intval($language['id_lang'])] = 'MyTab'; } $tab->class_name = 'AdminMyTab'; if(!$tab->add())return false; for the "structure", just take a look at the /classes/AdminTab.php file itself, you should be able to figure is out. Or you can take a look at any admin tab class under admin/tabs Link to comment Share on other sites More sharing options...
Recommended Posts