Skip to content
William Desportes edited this page Apr 6, 2019 · 5 revisions

This page was specifically for developer planning prior to the release of phpMyAdmin version 3, which was then released on 2008-09-27. This page is therefore of less interest but is maintained for future planning -- not all of the desired code refactoring was implemented and this page can be a starting point for planning phpMyAdmin version 4.

This is all subject for discussion - it does not present the current official planning of the phpMyAdmin team for phpMyAdmin 3, this page is only a source for discussions.

Most of the features depend on the time scheduled for releasing phpMyAdmin 3.

Code design

  • remove grabing of globals!
  • Grab variables using PHP filters? This would require PHP > 5.2 (or older with filter PECL module installed).
  • Templates - separate all application logic from display logic using Smarty
  • Classes - move more or even all code into classes - Class structure
  • Make it a PEAR package? or just installable through PEAR? GPL is not compatible with PHP License
    • other packages in PEAR use GPL or LGPL too
  • move JavaScript eventhandlers out of html tags (on[event]="...") into JavaScript file (window.element.on[event] = ...)
    • this could break on older browsers
  • support UTF-8 only

Requirements

  • PHP >= 5.2
  • MySQL >= 5.0.15

Suggestions

  • It will be nice if it use ExtJS, JQuery or script.aculo.us GUI

    • I've begun reworking the views for phpMyAdmin to use extJS 2.2 ( will update this with URL when I get to a alpha/beta release) - ext my admin AT i still see glaciers dot commercial
  • It will be very very nice if it will support modules (plugins), many many people would like to add more small functions to phpMyAdmin

    • ??? hi anonymouse, what type of plugins? where? --Cybot 08:12, 17 December 2007 (CET)
  • make "js enabled" mandatory (and drop all ...). --Jwind 17:03, 4 January 2008 (CET)

  • make the js folder version dependent , e.g., /js3.x.y/ to force the browsers not to use cached code when users re-use an old folder for an update. --Jwind 17:31, 4 January 2008 (CET)

  • More profiling/debuging features like the yog-tools

  • Url-navigation; entering www.domain.com/phpmyadmin/dbname should take me to the db, www.domain.com/phpmyadmin/dbname/tblname should take me to the table in the db. That would enable linking to tables from documentation amongst others.

    • This is already mostly supported already with syntax like ...phpmyadmin/index.php?server=1&db=foo and so on. Doing so as you propose would require .htaccess overrides of mod_rewrite, which is not always the case on shared hosting. For those who are able to do so, [[https://docs.phpmyadmin.net/en/latest/faq.html FAQ 1.34|https://docs.phpmyadmin.net/en/latest/faq.html]] covers the configuration (as well as describing the query string options for all cases). I think that's sufficient, don't you?--Ibennetch 17:29, 30 May 2009 (CEST)

Suggested Directory Structure

new, moved

  • contrib
  • html
    • js
    • pmd (?)
    • themes
    • setup
  • lang
  • libraries
  • scripts
  • test

phpMyAdmin 3

Clone this wiki locally