Welcome to the second release candidate for phpMyAdmin 4.0.0. With this
version, the HTML frames are gone and the navigation panel now presents
a tree. This version requires Javascript.
Version 4.0 contains many bug fixes and smaller new features; moreover,
the documentation has a new look and contains an index.
Details will appear on http://phpmyadmin.net. In a hurry? you can visit
https://sourceforge.net/projects/phpmyadmin/files to download.
Marc Delisle, for the team
Hi,
Nine days later and with more than 10600 downloads, RC1 seems pretty
stable. I think there was only one bug ticket (3870) for this release
and it came from myself.
If it continues this way, how about a release of 4.0.0 on April 19? (in
time for the Percona Live MysQL Conference and Expo 2013).
--
Marc Delisle
http://infomarc.info
Hi all
our continuous integration server now follows 4.0 branch as well:
http://ci.phpmyadmin.net/job/phpMyAdmin%204.0/
The builds are currently run nightly, just let me know if more frequent
builds would be needed.
Also translation server provides 4.0 branch for translations (though
there are no differences yet):
https://l10n.cihar.com/projects/phpmyadmin/4-0/
For now I plan to keep 3.5 enabled in both as well, just in case we
will need another release in 3.5 series.
--
Michal ÄŒihaÅ™ | http://cihar.com | http://phpmyadmin.net
Hi,
I am a first year undergraduate at IIT Roorkee.
I saw the list of proposed projects for GSoC 2013 and I am really
interested to work on the project idea of AJAX Error Reporting as I have
worked on a few projects based on JavaScript AJAX and was really excited
about it.
I have been working with JavaScript and jQuery since 2 years and I consider
myself as having a good working knowledge of it. I am really excited about
this project and would like to contribute.
I recently developed a simple yet elegant todo web application using AJAX,
the source code for which can be found
here<http://github.com/abhikandoi2000/flowork>
.
For the Error Reporting part I would like to suggest the following ideas:
1). Using JSON for the data-exchange b/w the server and client.
2). Encryption of sensitive information for protection from eavesdropping.
3). Authentication to confirm that the request is made by a valid user.
I was also thinking of a webpage to visualize the amount of
errors occurred over a period of time. As in this can include graphs
helping the user to identify amount of errors occurred over time and also a
log list of errors in chronological order.
Please comment to let me know if these features would be helpful to the
phpMyAdmin project.
It would be helpful if you could provide me with some details about how to
proceed further for GSoC .
Abhishek Kandoi
Hi All,
I am new here for GSOC.
After reading the idea listed on link:
https://wiki.phpmyadmin.net/pma/GSoC_2013_Ideas_List#Automated_testing
I am quite interested on the topic: Automatic testing. I have some developing experience on selenium and PHP Code Coverage.
I am very glad to join phpmyadmin. I will dig my selves into here, thanks
adam
Hello,
I was going through the Gsoc 2013 idea list and i understand that to have a
chance i need to write few codes for phpmyadmin. So i was going through all
the feature request that are listed there and that was quite a big list. Do
we have to implement all the features or some of them can do?
Actually i started with this
https://sourceforge.net/p/phpmyadmin/feature-requests/1385/ --to
hide/unhide the tables
Can you tell if my approach is correct?
In the right pane:
I want to Use the top left corner of the table(the one which shows all the
table inside the database) as the button described in the request.
Now there are two ways to hide
1) If no checkboxis checked and if button on top-left corner is clicked
then all the tables will get hidden
2) Select some of the checkbox and then upon clicking on the top-left
corner button will hide only those tables that are selected.
I guess first one will not be the right way. But anyway i would like a
comment on it or if there is some other way
And i wish to write it on the codebase of V 4.0.0-rc1. Is that all right??
Hi Rouslan,
>Try to write tests for the smallest functions that you can find first. That way, the tests will actually be useful in checking whether a function does what it's supposed to.
>
Thanks for your help about this. I try to apply the GSOC project: Automatic testing. In fact, I have finished
Have merged:
https://github.com/phpmyadmin/phpmyadmin/pull/233 add test case for PMA_Header_test
https://github.com/phpmyadmin/phpmyadmin/pull/240
Still on review:
https://github.com/phpmyadmin/phpmyadmin/pull/245 add test case for Table Class
https://github.com/phpmyadmin/phpmyadmin/pull/244 add test case for PMA_Footer_test.php
https://github.com/phpmyadmin/phpmyadmin/pull/243 add test case for Config.class.php
Still on working:
https://github.com/phpmyadmin/phpmyadmin/pull/246
add Class PMA_Navigation_test to cover navigation test
=============My information in preview mails===========
I am very familiar with the CI env and PHP code coverage, because I just finished a similiar project when I Intern on Yahoo! last year. I finished a automatic testing job:
1. PHP UNIT code and Functional testing code.
2. Commit to GIT will trigger a CI build.
3. The CI build is done by: slenium + Firefox+ Xvfb (so that we dont need display)
4. output the code coverage report.
About the topic, at least two things should be done:
1. create more test cases to increase the code-coverage of the test-suite
From the following data,
Total 48.55% 11386 / 23452 48.04% 368 / 766 15.79% 9 / 57
libraries 47.45% 10894 / 22960 48.04% 368 / 766 15.79% 9 / 57
2. set up the necessary scripts to automate this.
https://github.com/adamgsoc2013/phpmyadmin/tree/master/scripts
Thanks,
Adam
Hi,
I am new here. I am quite interested on the topic of Refactoring: Server view.
from the code learning:
1. server view display code is listed on ROOT folder with prefix: server_ .php (most code is used to echo page elements)
2. the user request action is sent out using Ajax (js folder)
3. the backend logic is on library folder, some is on ROOT folder.
I want to know that:
1. what kind of improvement ? user experience and UI change or code refactor?
2. If it is user experience changes, are there some todo guides?
3. is there some user survey and user experience feed back to guide us improve the Server view ?
xmujay(a)gmail.com
Hello,
A potential student approached me on IRC with a question about the
deadlines listed in the Applicant Guide on the wiki.
The phrase "The deadline for considering your contributions is week
before proposals ranking deadline, so that we can use this as one of
options to evaluate proposals." is a bit confusing -- which deadline is
meant? I interpret that as the May 24 date listed further down the page
in the section "Be familiar with the GSoC timeline" -- but there, the
deadline for contributions is listed as May 10, which is two weeks, not
one. So could someone clarify what is meant here?
Thanks