- Developers - lists.phpmyadmin.net

[Phpmyadmin-devel] Support and contribute pages on website
by Michal Čihař 15 Feb '12

15 Feb '12

Hi all I've just pushed some improvements to support and contribute pages on our website, hope you like it. The page with information for developers still requires some work, possibly removing less important stuff. -- Michal Čihař | http://cihar.com | http://phpmyadmin.cz

2 2

[Phpmyadmin-devel] about removing TESTING branch
by Marc Delisle 14 Feb '12

14 Feb '12

Hi, we discussed about this on 2012-01-25 with no clear outcome. Any objection to remove the TESTING branch? -- Marc Delisle http://infomarc.info

2 2

[Phpmyadmin-devel] phpMyAdmin 3.4.10 is released
by Marc Delisle 14 Feb '12

14 Feb '12

Welcome to phpMyAdmin 3.4.10, a bugfix release. Details will appear on http://phpmyadmin.net. In a hurry? you can visit http://sourceforge.net/projects/phpmyadmin to download. Marc Delisle, for the team

1 0

[Phpmyadmin-devel] Moving all end user scripts to examples dir
by Michal Čihař 14 Feb '12

14 Feb '12

Hi all as I feel that scripts directory has become sort of mess of developer and end user scripts, I would like to move all things which are interesting for end users to examples dir. I've already done this with signon and openid example scripts, the only remaining piece now are SQL scripts for creating phpMyAdmin configuration storage. Any objections against moving SQL scripts there as well? PS: I'm doing all this in QA_3_5 branch. -- Michal Čihař | http://cihar.com | http://blog.cihar.com

3 7

[Phpmyadmin-devel] Single point for developers
by Michal Čihař 13 Feb '12

13 Feb '12

Hi all currently our documentation for upcoming developers is spread over different places: [1] FAQ 7.3 in Documentation [2] Developers section in Documentation [3] http://www.phpmyadmin.net/home_page/devel.php [4] wiki What I'd like to do is to move most information to website [3], with possible more detailed information on wiki [4] and removing almost all content from Documentation [1],[2]. Currently it is quite hard to keep the information up to date [*] and I don't think it makes much sense to provide information in the documentation for offline usage as you would anyway require to be online to contribute. I've just submitted pull request for this change on github, so feel free to comment it there: https://github.com/phpmyadmin/phpmyadmin/pull/1 [*]: I think that [2] will become really outdated on our way to 4.0. -- Michal Čihař | http://cihar.com | http://blog.cihar.com

3 3

[Phpmyadmin-devel] removal of BLOBstreaming support
by Marc Delisle 13 Feb '12

13 Feb '12

Hi, I am volunteer to remove, from the master branch, support for this feature which does not seem to be popular in the community. Any objection? -- Marc Delisle http://infomarc.info

4 4

[Phpmyadmin-devel] GSoC 2012 and removal of frames?
by Marc Delisle 13 Feb '12

13 Feb '12

Hi, I believe that at the meeting, there were objections to put this in the ideas list, am I right? -- Marc Delisle http://infomarc.info

5 5

[Phpmyadmin-devel] INSTALL.txt better than INSTALL ?
by Marc Delisle 13 Feb '12

13 Feb '12

Hi, Is it some kind of standard to have an INSTALL file? Renaming it to INSTALL.txt would avoid problems like the one in [0]. [0] https://sourceforge.net/projects/phpmyadmin/forums/forum/72909/topic/5011405 -- Marc Delisle http://infomarc.info

7 8

[Phpmyadmin-devel] GSoC 2012 timeline
by Marc Delisle 13 Feb '12

13 Feb '12

Hi, as a reminder, the timeline is located at [0]. Mentoring organizations can submit their application from February 27 to March 9. [0] http://www.google-melange.com/gsoc/events/google/gsoc2012 -- Marc Delisle http://infomarc.info

2 4

[Phpmyadmin-devel] Roadmap to phpMyAdmin 4.0
by Marc Delisle 10 Feb '12

10 Feb '12

Hi, During the recent team meeting (February 5, 2012), we discussed about the long term development effort for the phpMyAdmin project. Here are the conclusions. Removal of frames Frames won't be used anymore (they separated the navigation panel from the main panel). Instead, a single page will be presented, with various parts dynamically reloaded with AJAX. This will require JavaScript to be enabled in the browser. Code base refactoring The code base will be cleaned up using refactoring. The goal is to remove the mix of HTML and PHP and produce code easier to maintain. Some parts will move to OOP, but we decided against switching to a framework. New features We currently do not plan any major new functionality for this version. Browser requirement Looking back, version number was bumped to 3.0 when new system requirements (PHP 5.2, MySQL 5.0) were introduced. Therefore, version number will go to 4.0 to accentuate the new browser requirement of having JavaScript active. The team

1 0