Developers

developers@phpmyadmin.net

2 participants
7003 discussions

[Phpmyadmin-devel] [GSoC] PMA with OOP
by Lex 26 Mar '10

26 Mar '10

Hi all, My name is Aleksey Shilin. I am Russian student and want to participate in GSoC with phpMyAdmin. I would like to participate in reorganizing PMA source code with OOP. Some words about myself : Second year student of Kuban State University of Technology (http://kubstu.ru). Have experience with OO programming ang git VCS. Languages PHP and C#. Worked with frameworks : Yii(http://www.yiiframework.com/) and .NET. Expected workflow: 1. Investigate current source code and make notes. 2. Develop architecture and make UML diagram for it. 3. Discuss architecture in mailing list or with mentor. 4. After approve, start writing unit-tests. 5. After that transfer current source code into OOP architecture. What tasks for patch can you advice, to show my code? I checked tracker, but some of opened tasks have negative response.

2 1

[Phpmyadmin-devel] GSoC About Two Ideas: OOP and UI cleanup UI
by Carlos mauro 26 Mar '10

26 Mar '10

Hi all. My name is Carlos Mauro Cardenas Fernandez. I'm studing a master. Well, people i wanto to participate in GSoc for MPA in this projects: - phpMyAdmin OOP Yeah PMA is a great project. Is very fun and powerfull for a lot of work. I want to create a some classes making groups with the prefix from the original files like: pmd_common.php, pmd_general.php, pmd_pdf.php, pmd_relation_upd.php, pmd_display_field.php, pmd_help.php, pmd_relation_new.php, pmd_save_pos.php to a class: pma_class.php (for example only a first idea). This project is possible but with a little limit but make a refactoring about all code may be create a new. The project is more factible like a redesinged like wrote in other email. But is very important defined a model class with mentor's help. The first step is create package with file with similar prefix and make a class. - User interface cleanup I want to redesing some form using jquery[0] or yui[1] with new datatable fro the grid. May be using google Api, Google have Ajax libraries API[2] and Google Chart Tools[3]. This tools are very powerfull for make a better administration database. I have some experience in this with the api google. [0] http://jqueryui.com/home [1] http://developer.yahoo.com/yui/datatable/ [2] http://code.google.com/apis/ajaxlibs/ [3] http://code.google.com/apis/charttools/index.html -- Carlos Mauro Cárdenas Fernández Ingeniero de Sistemas 4582877 980525716 Creemos en el amor de los Seres Humanos http://forpapers.blogspot.com/ http://unimauro.blogspot.com/

2 1

[Phpmyadmin-devel] The SVN repository
by Kaarel Nummert 26 Mar '10

26 Mar '10

Hi! When adding a patch I get a warning saying "Due to the amount of work required to integrate patches into phpMyAdmin, patches posted in a UNIX diff/patch (preferably unified) format, against 'trunk' in SVN repository will be MUCH more quickly accepted than other code." Is this still relevant? If so where is the SVN repository? The following web page only links to the Git repository. http://www.phpmyadmin.net/home_page/improve.php#devel Best Regards, Kaarel Nummert

2 1

[Phpmyadmin-devel] OOP Restructuring of PMA - One hell of of an Idea!!
by Vipin Nair 25 Mar '10

25 Mar '10

Hello guys, I have an idea for OO restructuring of PMA. I think converting the code to OO will help developers deal with PMA better. The PMA can be divided into four different subparts. They are: 1) Code that deals with Database (Create, delete, alter) 2) Code that Deals with Tables (Create, delete, alter) 3) CRUD 4) Others (User management, sync, etc) The above four sub-parts work together to do what PMA does, but they can also be treated independently. What i am suggesting is that the above four subparts can be converted into 4 different core classes and they can work together. Each of the core classes can have different methods to provide its functionality. Suppose we have a class 'database' for the first subpart and if any other subpart requires to create a database, it has to simply create an object of the database class and call its 'create' method with the required paramaters. This will uncomplicate the code. Each of the above mentioned subpart of PMA can be converted into a class one by one and can be seamlessly integrated to work with other subparts as well. This will help developers code PMA without essentially knowing the structure of PMA. Converting the code to OO helps to create plugins for PMA. All the developers needs to know is the class, its methods and arguments. For example: Suppose a system administrator is using PMA. His requirements are that every time a new user is added into the database, a new table should be created for the user in the database. System Administrator will want to automate his work and he would like a plugin for PMA that can do his work. He asks a developer to create a plugin. If the existing code is restructured into OO code, all that a plugin developer is required to do is that every time a new user is added to the database, a 'table' object is created and its 'create' method is called with appropriate arguments and a table for the new user is created. It could be something as simple as: $table_object = new table(); $table_object->create($username); Think of adding the same functionality with existing PMA structure. A new developer will have to put in a lot of time and effort to understand the existing PMA structure to do something as simple as above which generally discourages them. If the code is converted into OO, all the devloper will need to know is the struucture of the core class 'table'. My point is that PMA can be restructured as OO code, which will be very useful for PMA developers and plugin developers as well. OO restructuring will do a lot good to PMA and it will encourage a lot of developers to create plugins and add functionality to PMA. I think before ajaxifying the UI, if OO restructuring is done it will add lot of developers to PMA, in terms of features and plugins. Once the core OO restructuring is done, UI can be ajaxified to provide a better user experience. Each of the above mentioned subparts can be restructured into OO code mostly independently and i think in the summer time at least two or max three subparts can be restructured as OO code. I would like to know what the developers feel about my idea. Thank you, Vipin Nair nair.vipin(a)ymail.com swvist(a)gmail.com

2 1

[Phpmyadmin-devel] GSoC - AJAXify the Interface for phpMyAdmin
by Ninad Pundalik 25 Mar '10

25 Mar '10

Hi All, After reading through the GSoC Ideas wiki page[0] and the discussion on the feature request[1] of adding AJAX functionality to phpMyAdmin, I could think up of a possible implementation as follows, other than the one already outlined very briefly on the discussion page (of starting out with the Query page, implementing the common jQuery and PHP functions and then replicating the process for the other action pages) : 1. Implement this as an add-on in the initial phase. Replicate all the PHP files which operate on the database in a folder, '/ajax/' making them AJAX endpoints. 2. Modify the PHP code in each of the endpoints, so that we can output the content in XML, JSON or plain HTML (whichever is decided to be used). 3. On each action page, add some PHP code, which checks for a cookie/database setting and confirms that the client supports JavaScript. In the if block, add jQuery/MooTools code which will manipulate the necessary links and forms on the page, carry out the actual AJAX calls, and also implement callback functions, which will handle the responses from the AJAX endpoints. 4. In case the client does not support JavaScript, the code inside the if block will not be executed, and the existing PHP code of the page will handle the noscript case. Due to the above steps, we can maintain backward compatibility with browsers that do not support/have disabled JavaScript. Also, by implementing this as an add-on where the AJAX endpoints are maintained separately, we can ensure that the existing code is modified to the least possible extent and all changes that occur, are localized in the /ajax/ folder. I agree that this will lead to increased work in maintaining the common code for some months, but it gives me freedom to play and implement this functionality without breaking the core code. Once the modifications are deemed stable enough, the changes could be merged into the core code. Also, a quick look through the /js/ folder shows that the Designer interface already uses MooTools, as is mentioned in the feature request discussion. However, a previous mail on this list by Marc says that jQuery will be used for this project. I'd like to know if I'm thinking in the right direction. If I am, I will prepare this idea more thoroughly, it's deliverables, with the proper timeline requirements, as well as work on some patches, as is required in the Student Checklist[2]. :) My name is Ninad Pundalik, and I'm a student at the Birla Institute of Technology and Science, Pilani, India, and I wish to apply for the Google Summer of Code project with phpMyAdmin. I have been writing small websites in PHP, MySQL and jQuery for some student activities on campus, and have completed an internship last summer, where I helped in implementing Google Calendar APIs and Google and Twitter OAuth. As a result, I have been regularly using PMA for close to two years. While looking through the ideas for GSoC, I scanned the PMA code, and found it very easy to understand and of course, well commented and logically designed. Hence, I hope to get a chance to give back to this excellent software. Waiting for a reply, so that I could further develop this idea and prepare my application in time. :) ------------------- [0] - http://wiki.phpmyadmin.net/pma/GSoC_2010_Ideas_List [1] - http://sourceforge.net/tracker/index.php?func=detail&aid=2131880&group_id=2… [2] - http://wiki.phpmyadmin.net/pma/GSoC_2010_Student_Checklist ------------------- Ninad S. Pundalik http://twitter.com/ni_nad http://ninadpundalik.co.cc/blog GPG Key Fingerprint: 2DF7 B856 C75E C9F9 0504 C0EF D456 1946 7C45 2C69

3 3

[Phpmyadmin-devel] [GSoC] OO PMA project proposals
by Edouard SWIAC 25 Mar '10

25 Mar '10

Thanks for your observations Marc. > About PDO, the last time I had a look at it, there were no practical > reasons to support it. I think there is at least one major reason to support it (PHP version independently). Since PMA accepts two data access interface ,mysql_* and mysqli_*, using PDO would avoid maintaining these 2 interfaces in adapters functions (such as PMA_DBI_fetch_row ...). Moreover, mysql_* and mysqli_* API are so nearly identical, that almost the same code is written twice. As you know PDO handles these two drivers natively, lowering the burden of code to write and maintain. Coming back to architecture, templating (currently is active discussion) is a good way to go towards MVC. What do you think about it ? From what I see in PMA source code, some parts are developed with classes (Confirm, Error, File ...), so the project may consists in pursuing this objective, in order to smoothly convert the procedural code base into an oriented one. Regards, Edouard

4 8

[Phpmyadmin-devel] To potential GSoC students
by Marc Delisle 25 Mar '10

25 Mar '10

We appreciate the interest of students to take part in this year's Google Summer of Code with phpMyAdmin. Unfortunately our mentor manpower is limited. Because of this please take care when filling your proposal and follow our student checklist on the wiki. This way you can dramatically increase your chance of being accepted. We will especially take into account your code contributions to phpMyAdmin so far. - the mentors

1 0

[Phpmyadmin-devel] Rasmus' no-framework MVC article
by Marc Delisle 25 Mar '10

25 Mar '10

Hi, for those who are not aware, Rasmus Lerdorf has an interesting article: http://toys.lerdorf.com/archives/38-The-no-framework-PHP-MVC-framework.html I need to study it more, however I believe that we should take these ideas into account while discussing any MVC move for phpMyAdmin. -- Marc Delisle http://infomarc.info

3 4

[Phpmyadmin-devel] PMA Redesign - GSoC
by Thomas de Lima 24 Mar '10

24 Mar '10

Hi! My name is Thomas de Lima. I'm a computer engineering student from Brazil. I want to discuss more the idea of redesigning PMA, because I want to be sure I understood it correctly. Design is not only about changing color or shapes in the user interface, but also about changing how the user interacts with the application, towards improving usability. So, the "User interface cleanup" project needs to be codeveloped with the AJAX team. Is that right? I read an email from our indian colleague Anirvana Mishra, excited about ajaxifying PMA. But then Michal answered that he should pick one specific area to improve, cause there's too much functionality in PMA. Well, as a database manager, the PMA should be lightweight and "usable". For example, it takes a great deal of HTML download and clicks to find and edit someone's data in a huge personnel table. AJAX could solve both problems by opening a quickedit option on a browse table's row, which could be quickly found by an AJAX filter on top. So I think one of the "User interface cleanup" project goals should be study of which features need to be ajaxified or changed, or whatever, not about picking, before a deeper study, an area to improve. For this purpose I wish to apply as an GSoCer to improve the PMA user interface, cause I frequently use it to manage my databases remotely. Of course PMA's usability now is excellent, as everything is intuitively put in place, but it feels soooo Web1.0, so static. Thanks, thomas.

2 2

[Phpmyadmin-devel] Git is here
by Michal Čihař 24 Mar '10

24 Mar '10

Hi all I should have announced it earlier (as the repository migration went as planned), however I somehow got focused to migrating other tools meanwhile so the announcement comes now. So yes, everything is in Git now and the Subversion repository is in read-only mode. Please check if something is not broken, I might have missed something. Things which should work without problems: - demo server - daily snapshots - website, translation stats,... - creating releases [1] For using Git, please follow instructions in wiki [2]. Especially working properly with more branches can save you lot of work. [1]: As I added there some improvements, I also started documentation for release process (which is far from being complete right now) on wiki: http://wiki.phpmyadmin.net/pma/Devel:Releasing [2]: http://wiki.phpmyadmin.net/pma/Devel:Git -- Michal Čihař | http://cihar.com | http://blog.cihar.com

3 14

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

Developers