3 ms·

How is it different from phpMyAdmin ?

tonylemesmer 12y ago
Looks like it does some relational stuff automatically based on column names. Another difference looks like it doesn't have all the options of phpMyAdmin.
jiggy2011 12y ago
I haven't used this , but it looks like it's cleaner and simpler. phpmyadmin has a lot of options that non technical folks could use to break the database.
- pmlnr 12y ago
  Install adminer for those. http://www.adminer.org/ http://www.adminer.org/
jonseg 12y ago
Hi, with this tool you have control over the generated code. You can add a login system, modify the views, add an upload images system... The tool generates a base administrator and you can add all functionalities that you want.
- jiggy2011 12y ago
  Hi Jon, you should show some examples on the home page on how to extend the code. For example if I wanted to modify the administration for one of the tables is there a base class that I can inherit from? For example if I wanted to a hide a particular field in the admin, or if I had some custom validation rules. Is this designed to work with any particular framework?
  - jonseg 12y ago
    The generated code is "pure" PHP. You have a controller for create, edit, list and delete. You can modify the controllers without problems and extend the functionalities. You can hide fields, add new ones, implement an upload images/files system... The used framework is Silex (http://silex.sensiolabs.org/ http://silex.sensiolabs.org/) Thank you.
    - gnud 12y ago
      Is there a good split between generated/edited code? Or do I have to change the generated code? Also, can I regenerate only parts of the interface (after changes to the database, for instance)?
    - jiggy2011 12y ago
      If I understand, the approach that you are taking is that code is generated for the admin using the generator and then you would do modifications afterwards? What happens in such a case that the code is modified and then you run the generator again? An alternative approach would be to supply custom classes to the generator at the time that it generates. For example. Class CustomerTable extends AdminTable { $hiddenfields = [ "created_date" , "password" ]; $validation = [ "email" => "validateEmail"]; function validateEmail($validate_data) { return validEmailAddress($validate_data); } } Then the user can place this class somewhere specific or register it with the generator in some way, and when the generator runs it will use this class and not overwrite changes. Like $adminGenerator->use("customer","CustomerTable"); This way you can keep using the generator even after you have done extensive modification to the tables and code.
stephenr 12y ago
I assume the idea is that it can be customised after the initial run.. A quick look at the code and it seems to treat all content as text - you either get a text input or a text area. Even without any php Models defining the type of a field, the MySQL column types provide a reasonable amount of information about the type which can be translated (as phpMyAdmin/etc do) into more logical form fields.

Looks like it does some relational stuff automatically based on column names. Another difference looks like it doesn't have all the options of phpMyAdmin.

jiggy2011 12y ago

I haven't used this , but it looks like it's cleaner and simpler. phpmyadmin has a lot of options that non technical folks could use to break the database.

pmlnr 12y ago
Install adminer for those. http://www.adminer.org/ http://www.adminer.org/

jonseg 12y ago

Hi, with this tool you have control over the generated code. You can add a login system, modify the views, add an upload images system... The tool generates a base administrator and you can add all functionalities that you want.

jiggy2011 12y ago
Hi Jon, you should show some examples on the home page on how to extend the code. For example if I wanted to modify the administration for one of the tables is there a base class that I can inherit from? For example if I wanted to a hide a particular field in the admin, or if I had some custom validation rules. Is this designed to work with any particular framework?
- jonseg 12y ago
  The generated code is "pure" PHP. You have a controller for create, edit, list and delete. You can modify the controllers without problems and extend the functionalities. You can hide fields, add new ones, implement an upload images/files system... The used framework is Silex (http://silex.sensiolabs.org/ http://silex.sensiolabs.org/) Thank you.
  - gnud 12y ago
    Is there a good split between generated/edited code? Or do I have to change the generated code? Also, can I regenerate only parts of the interface (after changes to the database, for instance)?
  - jiggy2011 12y ago
    If I understand, the approach that you are taking is that code is generated for the admin using the generator and then you would do modifications afterwards? What happens in such a case that the code is modified and then you run the generator again? An alternative approach would be to supply custom classes to the generator at the time that it generates. For example. Class CustomerTable extends AdminTable { $hiddenfields = [ "created_date" , "password" ]; $validation = [ "email" => "validateEmail"]; function validateEmail($validate_data) { return validEmailAddress($validate_data); } } Then the user can place this class somewhere specific or register it with the generator in some way, and when the generator runs it will use this class and not overwrite changes. Like $adminGenerator->use("customer","CustomerTable"); This way you can keep using the generator even after you have done extensive modification to the tables and code.

stephenr 12y ago

I assume the idea is that it can be customised after the initial run.. A quick look at the code and it seems to treat all content as text - you either get a text input or a text area. Even without any php Models defining the type of a field, the MySQL column types provide a reasonable amount of information about the type which can be translated (as phpMyAdmin/etc do) into more logical form fields.