As my sixth week of GSoC with phpMyAdmin has come to an end, I going to explain the problems faced and how I tackled them. The biggest problem I faced was calculating text colours with contrast ratio greater than 4.5 , while keeping in mind the colour scheme used. First I tried to use mix-blend-mode but it didn’t work out because I would have to add a span class for every text, which wasn’t feasible. So I created a new function which takes the background colour and compares with the calculated colour . If the contrast ratio is less than 4.5 it tweaks saturation and brightness till the required contrast ratio is achieved. This colour is achieved with a maximum iteration of 10. Now I have started creating Preview panels and would complete it this week, hopefully.

Working on fifth feature

I’m currently working on the fifth feature- This is one of the most requested features in my features’ list Till now I’ve done the following-

1. Added a configuration directive in config.default.php as $cfg[‘Import’][‘enable_drag_drop_import’]
2. Added a checkbox in the settings page to toggle this config on or off.
3. Disabled the handler at the server side if config is set to disabled.

TODO:

1. Test on multiple servers.
2. Disable drag drop handlers in javascript.

It’s been 5 weeks now working with phpMyAdmin under the Google Summer of Codes 2018 program. I have successfully passed the first evaluation.

During these two weeks and including this week also, my main objective was to modularize the Navigation, Error Report, PMA Console, Import and Export and the configuration file so that the configuration of these pages can be checked and settings can be changed with the modular code.

Right now I am working on inline javascript coming from the php classes containing the the configuration of the particular page which were injected in the container showing the body of html. These configurations need to be imported in the module from window of document and then used in the modular code so that any change in the setting of the page or any saved setting can be compared with new changed or setting user is going to made on the settings page and on PMA Navigation.

Regarding the Feedback from Mentor:

As per the feedback, the mentors had given, I will try to push the quality code on the pull request by the end of this week or by the mid of the coming week after making successful changes and testing of the above mentioned files,which can be reviewed.

Fourth feature submitted

I’ve submitted a PR for the fourth feature. The following new functionalities have been added-

1. Automatically add PRIMARY KEY on column edit page when user tries to set AUTO INCREMENT.
2. Disable popup when user clicks on the A_I checkbox in column insert and new table page and automatically set default index to PRIMARY with defaults.

Plans for next week-

The next feature(#5) that I’ll be working on is- Add a configuration option to disable drag drop files completely This is one of the most requested features among the ones in my proposal.

1. I’ll be adding a setting among other settings where user can disable the checkbox to disable drag/drop file functionality.
2. This setting will directly interact with the configuration file(just like how other configuration settings work). There are some workarounds suggested by the users in the feature request page, I still have to figure out the safest and best among them, or, I’ll be finding out a workaround of my own.

Working on fourth feature

I’m currently working on the fourth feature- Before starting, I was thinking about showing a popup to add index when user tries to add AUTO_INCREMENT to an existing column. But in our conversations, Isaac and I decided to -

1. Automatically add PRIMARY KEY instead of showing a popup to add index.
2. Disable popup when user clicks on the A_I checkbox in column insert and new table page.

Issues I’m currently working on-

1. Fatal javascript error while adding index to a new column, #14402

Third enhancement submitted

I’ve submitted a PR for the third feature - Have set the default width for varchar fields in the insert page to cover the whole width of page. I assigned a class to the “value” th element in the table, and styled it to cover the whole page. Varchar and char textareas were also assigned a class to cover 95% of their parent elements.(width style overrides col attribute) I have set the minimum number of rows to 7. It doesn’t need any relative value, as the height of this table mostly overflows the page.

Among all the enhancements in my list, the third one was the most minor one, all the others require relatively a lot more work and testing.

Plans for next weak.

Mentor evaluation starts 11th June. I will be scrutinizing my work until now to test for bugs and for code optimization whereever possible and will be working on some issues.

This week I updated the code style to fit some of the PSR-2 rules, refactored some files and upgraded to Twig 2, in addition to helping the GSoC students.

Issues:

• #14341 Fix bug reported on pull request #14305
• #14317 Extension removal

The post Weekly phpMyAdmin contributions 2018-W22 appeared first on mauriciofauth.com.

This week I made up for the additional hours I worked on in the previous weeks. I removed the $dbi global variable from several classes, in addition to helping the GSoC students.

Issues:

• #14305 Remove md5 twig extension

The post Weekly phpMyAdmin contributions 2018-W21 appeared first on mauriciofauth.com.

This week I enabled the strict type mode in all PHP files, fixed some bugs and reviewed pull requests, in addition to helping the GSoC students.

Issues:

• #14286 Fix central columns in-line edit bug
• #14231 #13893 issue fix Simulating queries produce unexpected results
• #14272 fixes broken links to icons in the setup page
• #14304 [5.0.0-dev] Strict mode php errors
• #13893 Simulating queries produces unexpected results
• #14119 fix: AUTO_INCREMENT error when only exporting table structure in database-level exports; issue #14066
• #14066 Export MySQL Table (only structure) AUTOINCREMENT error
• #14296 Enable strict mode in PHP files
• #14278 Central columns can’t be edited or deleted by multiple selection after single edit
• #14290 Enable strict mode in some classes

The post Weekly phpMyAdmin contributions 2018-W20 appeared first on mauriciofauth.com.

This week I fixed some bugs, reviewed pull requests, replaced some deprecated jQuery functions and added type declarations to multiple classes, in addition to helping the GSoC students.

Issues:

• #14280 Adapt html functions to Twig templates
• #13999 Incorrect CURRENT_TIMESTAMP DDL generated with MariaDB 10.2
• #14265 Issue #14019 fix: Allow parameter in AllowThirdPartyFraming
• #14019 Allow parameter in ‘AllowThirdPartyFraming’
• #14189 Remember table’s sorting broken in 4.8.0
• #14204 Remember table’s sorting broken in 4.8.0 issue: #14189 fixed
• #14067 IS NULL search operator produces no WHERE SQL with spatial fields
• #14068 SPATIAL fields with no unique index/autoincrement error when clicking
• #14121 View spatial fields as WKT doesn’t work
• #14125 Fix for issues with spatial fields
• #14266 HTML entity incorrectly displayed
• #14275 Revert modifications
• #14267 Require a polyfill instead of the cytpe extension
• #14249 Edit/Replace view: missing Go button
• #14263 Fix for missing go button in view edit, #14249
• #14177 Fixes bug #13968
• #13968 Data truncated error with current_timestamp().000000 and mariaDB 10.2
• #14260 Language does not change in 4.8.0.1
• #14261 #14260 Fixed configuration for DefaultLang and Lang

The post Weekly phpMyAdmin contributions 2018-W19 appeared first on mauriciofauth.com.

This week I fixed some bugs and reviewed multiple pull requests, in addition to helping the GSoC students.

Issues:

• #14202 Binary foreign key enhancement #13894
• #14255 Addapt getTableHeader to twig template
• #14258 Patch for #14257 CodeMirror hints hidden
• #14257 CodeMirror hints hidden in functions/procedures/triggers
• #14216 Fix XML Export fatal error and add Move columns preview SQL
• #14212 [4.8.0] XML Export from single table throws fatal error (PHP 7.2)
• #14155 Feature Request: Move columns preview SQL
• #14211 Duplicate hidden token input field issue solved
• #14166 Changes to make Get auto saved query and show this query here again button functional
• #14254 #14253 Git commit info not showing when the repository is a submodule
• #14209 Duplicate hidden token input fields
• #14253 Git commit info not showing when the repository is a submodule
• #14094 Fix bugs in SQL query restore after session expire
• #14163 Not showing default query on changing table
• #14148 Not showing previous query on clearing Codemirror and then clicking get saved query
• #14144 “Show this query here again” checkbox does not work
• #14118 SQL tab already has a query loaded
• #14093 No auto saved query everytime new sql page is loaded
• #13894 Binary foreign key enhancement
• #14128 [4.8 RC1] Show 2FA Secret next to QR
• #14154 Display the secret for 2FA – #14128
• #14141 Remove inline styles from Relation.php

The post Weekly phpMyAdmin contributions 2018-W18 appeared first on mauriciofauth.com.

This week I added type declarations to some classes, refactored the PhpMyAdmin\Dbi\DbiMysqli class to use the mysqli class and fixed some bugs.

Issues:

• #14244 Fixes some jQuery Migrate warnings
• #12373 Theme selection for future releases
• #14210 Add Metro theme
• #14213 getThemeUniqueValue error in master
• #14232 4.8.0.1: Colums hidden on low resolution display
• #14102 More Dropdown not fully visible
• #14199 UI Issue – date picker hides in scroll frame
• #14029 Horizontal scrollbar not visible
• #14193 Regression – Scrolling down messes up the fixed column names
• #14206 patch fixed for the datepickerui broken #14199
• #14196 Fix for ui regression issues
• #14228 #14049 issue fix Query builder doesn’t work when the selected column …
• #14226 #12772 issue central column attributes don’t get filled in
• #14169 Regression – Action Icons glitch in 4.8.0
• #14194 UI Issue – I have to scroll down, to be able to scroll horizontally
• #14165 Query builder doesn’t work when selected column is * #14049 issue fix
• #14049 Query builder doesn’t work when selected column is *
• #12772 Central columns attributes don’t get filled in
• #14073 Central columns attributes don’t get filled in #12772 issue solved
• #14179 Remove Inline Styles from Ruotines.php
• #14173 Fix for error when running prepared statements, #14162
• #14162 SQL parser error trying to run a prepared statement
• #14137 Tables stop at border
• #14135 Tables in designer don’t stop at border
• #14224 Use array_key_exists instead of in_array + array_keys

The post Weekly phpMyAdmin contributions 2018-W17 appeared first on mauriciofauth.com.

This week I added type declarations to some classes and added the Metro theme in the master branch.

Issues:

• #14175 Theme problem in 4.8 version
• #14208 Fix errors due to undefined variables

The post Weekly phpMyAdmin contributions 2018-W16 appeared first on mauriciofauth.com.

This week the phpMyAdmin began to require PHP 7.1 in the master branch. So I updated the dependencies and removed some PHP 5 code. I also refactored some classes by replacing the static methods with instance methods.

Issues:

• #13896 Bump minimum version to PHP 7.1 for phpMyAdmin 5.0
• #13919 Remove font size feature
• #13925 Remove font size feature
• #14186 Bump minimum version to PHP 7.1

The post Weekly phpMyAdmin contributions 2018-W15 appeared first on mauriciofauth.com.

Completed 3 weeks of Google Summer of Codes with phpMyAdmin. Major task for the week was to revamp the ajax handler so that it will be compatible with the new webpack generated bundle and there should not be any need of appending the files in the head of the document as it is there in the project right now. Webpack will take care of it.

Here is the major change in the AJAX add script function. There are some more changes by I am showing only this major change.

The new function introduced import() is a function which returns a promise resolution of which contains all the exported modules.

This function will take care of the appending of script in the head tag by generating chunks for modules needed by the dynamically imported module.

This function needs some edits to make it workable for all the files rather than the two files in the array.

The snapshots of the generated webpack profile with two different configurations are as below. Both the configuration have same output size both in development and production mode.

1). When vendor files like jQuery, Codemirror are not build in a separate chunk. The size of various chunks are also shown in the next snapshot

2). Second configuration when vendor files are placed in a separate bundle and included in the Header class for loading it each time with index_new.js

The reproducible pr is already made on github.

Major task for this week would be to work on optimising the webpack bundle and working on ajax handler to revamp it further and try to create multiple entry points for separate files and the compare the output with single entry point.

It’s been three weeks since the beginning of my project. It’s been a real challenge.

2nd week

During my second week I removed all of the php functions Twig extensions. Some of this extensions required a lot of effort because they were used on a template deep in the includes tree.

3rd week

Last week I started to deal with the templates. After defining the directory structure of the templates, I began with the directories that are already in this structure, database, server and table. I finished refactoring the db_central_columns.php file, by melding all getHtml function calls into a new function called getHtmlForMain, and all of its templates, which reduced the number of templates from 5 to 2 templates files, reducing a lot the calls to Template::get() at CentralColumns.php.

This week I’ll continue to refactor the templates on database dir.

It’s my third week of GSoC and I’ve been working on automatically creating CSS files for automated theme generator. While creating different background colours some text colours were more visible than others. After some search I came to know it’s being caused by contrast ratio .

Greater ratio means greater visibility a minimum ratio of 4.5:1 is required because it compensates for the loss in contrast sensitivity usually experienced by users with vision loss and ratios greater than 7:1 is great for users with colour blindness or low visibility. So as I am coming to an end for creating Automated colour backgrounds, I’ll focus on keeping texts with high contrast ratio and also work on creating test cases.

Completed 2 weeks of Google Summer of Codes with phpMyAdmin. My main task for the first two weeks was to implement webpack and babel configuration and converting some functions which are globally available into modules which can be imported at times of need. I have changed some of the files with modular structure, now I need to work on making this new structure compatible with existing code.

Major task for this week is to convert the AJAX global object into a module with a global scope in the application so that its instance can be used in different modules and files and making some part of new structure compatible.

Apart from that raised solved one issue regarding Edit Variable in Variables page in this pr.

I’ve completed my second week of GSoC and the main task for this week was to create a form which could send palette data to the back-end to create CSS files which would be used in t he new theme. The main problem was that palette data was in HTML and was being generated dynamically by using javascript.

So I solved this problem by adding hidden input in the form when Submit button is pressed and send that using AJAX. Now my main focus is to assign different colours of colour palette to various elements.

Sorry for posting the blog this much late. Actually I got stuck in some major problems (errors to be more precise due to some changes) in the code-base so didn’t get enough time to make a blog post.

My major goal for the first two weeks was to transform some of the code-base in the ES6 format but as soon as I started to write the code in ES6 I realised that it is necessary to make some configuration files for webpack and babel so that the trans compiled code can be tested for functionality.

So in the first week I just implemented the basic configuration files for babel and webpack and try to find out what can be the possible new directory structure for js files so that the development and compiled production build files can be placed separately and some find out some basic syntax and standards of ES6 that can be implemented in the revamped code.

Apart from that I was working on this issue in changing the theme raised by me only.

Plans for 2nd week: Understanding the flow of adding js files using php code (existing one) and what changes has to be made for new code and transforming some of the files in ES6.

I’m posting this a little bit late, because I’m not used to report my work this way, hopefully I’ll get used to it fast.

This week my main goal was to remove Twig extensions that were extending php functions, there were 10 extensions, and by now I was able to remove 6 of them. I’m doing this to prevent that it’s used on future contributions that port the front-end to Twig templates.

During this work, I found some TypeErrors due to the automatic casting removal, and fixed them.

Week 3

I’m currently working on the second enhancement,

Importing table from a CSV file

When a table is imported from a CSV file, the default table name is Table ## and default names for the columns are COL ##. Default table and column names

Enhancement-

Set the imported table name to the name of the imported file and column names to the titles of each column in the csv file OR ask the user to enter table and column names.

I was planning to add the feature of setting column names of the table imported from a csv file from the title of all the different columns, but this feature is already present. Now, I’ll be working on some other feature(currently discussing with mentor).

I’m also working on some issues in the issue tracker.

1. Query > Submit query : Error 500

I’ve found an issue and I’m trying to work on it side by side.

End of Week 3

I’ve submitted a PR for the second feature - Following new features have been added to the csv import plugin-

1. For a new import, user can now directly enter the table or database name at the time of import.
2. Partial import. User can enter how many rows they want to import.
3. Show table structure edit form when the import is successful(undecided).

I’m also working on some issues in the issue tracker.

1. (Issue in Changing theme)[https://github.com/phpmyadmin/phpmyadmin/issues/14295]
2. (preg_match error when clicking Insert or Search tabs)[https://github.com/phpmyadmin/phpmyadmin/issues/14315]

Plans for next weak.

As stated in my proposal, my end sems have started and I won’t be able to work for the next 10 days. From 1st. I’ll be working on the 3rd enhancement.

​(Increase input field width for varchar(255))[https://github.com/phpmyadmin/phpmyadmin/issues/13627]

Enhancement-

In the insert row page, the dimensions of varchar textareas are small, which could be increased. As suggested in a ​comment​, the user appreciated presence of this feature in the earlier version and thus can be re-considered in the current version for a better user-experience.

Week 2

Since my end sems are approaching fast and I’ve been really busy with college projects, It has been really difficult to give 6-7 hours everyday for GSoC.

I’ve implemented the login modal and submitted a PR for review. Although, I’ve added comments at appropriate places to make the review and understanding easier. I’ll be explaining the code in detail.

I’m also working on some issues in the issue tracker.

1. getRealSize should expect also literals, not only integers This issue seems to be a question which I am discussing in the issue page.

2. Query > Submit query : Error 500

It’s been a week since I’ve been working on my Google Summer of Code project with phpMyAdmin and my work for this week was to create a separate page for the tool and add/remove functions in a preexisting colour picker tool. The existing tool was creating some palettes but they were not using colour theory to create palettes usable that could be used directly on websites. I have been focusing on four types four types of colour palettes, Monochromatic, Complementary, Analogous and Triadic.

The most difficulties were faced in Monochromatic and Analogous, in the monochromatic theme the main thing was how the palette should be managed if the hue value remains same and saturation and brightness changes of the base colour. I solved it by taking a range of saturation and brightness keeping the average of them equal to that of base colour. Also the values of saturation and brightness were in opposite orders for further contrast. In Analogous theme the problem was how further should the hue difference be set from base colour for optimal colours , I was quite satisfied with 45 degrees in the end. So in the end of this week I have completed all the colour palettes, the next step would be to start integrating the colour picker tool with back end.

I’m very happy to announce that I’ve been working with phpMyAdmin this summer under Google Summer of Code program and my project for the same is “Introducing modern JS features and tools” into phpMyAdmin’s code base. The duration of project will be nearly four months (starting April, 23 to August 14).

The project involves introducing package manager for managing modules so that the modules can be updated easily, introducing ES6 into the code base, babel for compiling ES6 to ES5 which the browsers support, webpack for creating minified files which can be served in production mode and eslint for code linting to find out problematic patterns or code that doesn’t adhere to certain style guidelines.

phpMyAdmin’s javascript code is written very well in terms of logic and best practices and very well documented but there are some problems with the current code, many of the variables are globally exposed and the external libraries like jquery are used as a downloaded library. So every time a new release is there, these files need to be replaced with the new files manually.

The global variables can be reduced by using some modern javascript ES6 features like module import and export, block scoped variables and using classes and closures for interdependent files which is not there right now.

The problem of manually updating files can be removed by using a package manager like npm or yarn, which have commands like “npm update” to update the existing modules.

As the javascript code base of phpMyAdmin is very large, it might not be possible to revamp the whole code base in three months, so my major focus will be on bringing the new code with new features in such state that the existing code and the new code can me compiled together and can be used in production.

By the end of GSoC program, I expect to implement the aforementioned tools and features without breaking the build status and consistency of the code base and convert as much of ES5 code to ES6, as possible.

For future(not part of the program): There can be some other features which can be implemented like unit testing of the functions and type check of various variables which will help in reducing and easily identifying errors related to type check.

I’m very happy to announce that I was one of the selected to work with phpMyAdmin during Google Summer of Code this year, which will happen, this winter (here at Brazil), from April 23th to August 6th.

I will be working with the Twig templates currently in use at the project, which can be found here. The idea of using a template engine is to maintain code organization and consistency, by separating your logic code from your markup, or front-end.

phpMyAdmin’s front-end is not fully implemented using Twig, there’s plenty of work to be done here, my work on this project is to Refactor this templates, using more of Twig’s features to enhance code organization. The first thing that will be done is to analyse if all Twig extensions currently in use are really necessary or if it can be replaced by a Twig feature, if changes are made in this part, it will be necessary to change the code in every part that this changes affects, what can be done while refactoring each template.

After the extensions are all good, the next thing to do is to go through the code on functions that return html and apply Twig features on this functions and templates that are used. For example, here, a possible thing to do is to use ‘Blocks’ or ‘Extends’ feature to simplify all of these front-end calls into one.

By the end of the GSoC program I expect to have contributed to a project that seizes the most of Twig’s benefits. And I hope that I’ll be able to expand my open source contributions.

I am very happy to announce that I’ll be working with phpMyAdmin this summer on the project ‘Automated Theme Generator Tool’. Currently there are pre-generated themes that can be manually installed and used. The idea is to create a tool that automates and makes easier the task of creating themes. Themes created from the Theme Generator tool would be less prone to bugs in the long run and could cater to each individuals needs. For the automated themes to look good to the eye, I’ll be using the concepts of Colour Theory.

The major goal of this project is to create a tool, that would create themes giving the users adequate freedom for changes and at the same time, automates the other parameters of the themes itself so that theme looks good i.e. by using colour combinations that are appealing to the eye. Designers use a variety of techniques to create themes and colour combinations that would be good looking. One of the main tools that would be used is a designer’s colour wheel.

Though RGB and Hexadecimal values are important for creating a webpage, they are of little use while studying Colour Theory. The HSB (hue, saturation, and brightness) are more important in working with colors. HSB values can be easily converted from hexadecimal and RGB values.

Primarily we would focus on four types of colour schemes:

• Monochromatic Colour Schemes

Monochromatic schemes use different tones from the same angle on the colour wheel. All colours are derived from the base colour and the hue value is not changed.

• Analogous Colour Schemes

Analogous colour schemes are created by using colours that are next to each other on the colour wheel.

• Complementary Colour Schemes

Complementary schemes are created by combining colours from opposite sides of the colour wheel.

• Triadic Colour Schemes

Triadic schemes are made up of hues equally spaced around colour wheel.

All the colours generated by the colour scheme using the formulas of colour theory, would be displayed on a colour palette so that the user can further tune each colour according to his choice if they want to. The main elements to keep in mind while assigning colours are:

1. Headers
2. Footers
3. Background
4. Tables
5. Groups
6. Notices
7. Results
8. Buttons

Apart from styling the webpage as a whole, the users can use the same color picker tool to customise the font color and a drop down menu to change text font from a set of predefined fonts supported by the browser.

There are many different types of text that would require different colors to distinguish each other. The most important being the following:

• Headings — These would generally match with the base color of the theme.
• Links and Links (on hover) — The two text should be distinguished from each other apart from being different from the normal text.
• Other text — This text would cover up most of the text present on a page.

One thing to keep in mind is that for the maximum visibility of text, the text color should be contrasting to that of the background color, by default. One option is to set complementary colors to that of the colors selected in the theme.

A minor tweak that can be allowed are a set of predefined icons and if time permits, we could start working on adding gradient to the themes. The last thing required would be to save the theme settings so that the same theme opens the every time phpMyAdmin is reopened.

The final tool would look somewhat like this:

Mockup

The four color wheels indicate the different scheme types to choose from, currently the monochromatic color scheme is shown to be selected. A color picker tool is shown which could easily convert HSB, RGB and hexadecimal values into each other. The Elements and Text palette shows the colors that would be used for them respectively. On hovering on a particular color, a popup would show for what elements the particular color would be used (Example: The cursor is on the blue color, and a pop-up displays that it would be used for hyperlinks). The Theme name asks for an input to save the theme with a particular name. The Font Style option shows a drop-down menu to select a font style. A Preview and Go button are at the bottom of the page which displays a preview and saves the theme respectively. At the right side the Sample Preview shows various sample previews of four main components(Main Window, Query and Table List, Navigation Panel, Table Data). These preview panels can be hard coded on this page rather than linking it with the original pages, this would save time and make things easier. At the end of the project we could expect the theme generator tool to be completed and ready to be pushed to master branch, and later to STABLE branch after adequate testing. A summarised list of expected deliverables are:

1. A customised color picker tool.
2. Different color scheme modes.
3. Custom text color and fonts.
4. Theme preview mode.
5. Save the themes settings and creating the necessary files.
6. Choice of predefined icons. (Optional — as advised by the mentor)
7. Color gradient on different elements. (If time permits)
8. Remove inline style scripts. (As required and as per time)

Project Schedule

April 23, 2018 — May 14, 2018

• Bonding with community.
• Discuss and clear the ambiguities and implementation details.

May 14, 2018 — May 21,2018

• Create a new page for Theme Generator Tools.
• Implement Basic Colour Picker Tool and customising it according to our needs (adding necessary functions and removing the unnecessary ones).

May 22,2018 — May 29,2018

• Save theme and create necessary files automatically.
• Opens the same theme when phpMyAdmin restarts.
• Test cases and documentation.

May 30,2018 — June 6,2018

• Add color schemes functions.
• Integrating the color scheme functions with the color picker tool.
• Basic color changing webpage.
• Fix inline styles where necessary.

June 7,2018 — June 14,2018

• Make-up week.
• Fix any bugs and write the required documentation.
• Submit work for phase-1 evaluations.

Mid evaluation: June 11–15, 2018

June 15,2018 — June 22,2018

• Add remaining color schemes functions.
• Integrate text color changes with color picker tool.
• Automate text colors with the selected color scheme.

June 23,2018 — June 30,2018

• Create Sample Preview Panels
• Font changes.
• Write Tests and documentation.

July 1,2018 — July 8,2018

• Make-up week.
• Submit work for phase-2 evaluations.

Mid evaluation: July 9–13, 2018

July 9,2018 — July 16,2018

• Predefined icon picker drop-down menu.
• Integrate Theme Generator with Sample Preview.
• Travis test cases.

July 17,2018 — July 24,2018

• Fine tune CSS features.
• Fix any bugs that might have gone unnoticed.
• Remaining Travis test cases.

July 25,2018 — August 1,2018

• Add gradient tool.
• Fix any colour scheme automation .
• Write Documentation.

August 2,2018 — August 6,2018

• Make up week.
• Wrap up the work.
• Fix any bugs and do required documentation.
• Work on more features if time permits.

Final evaluation: August 6–14, 2018

I’ll be updating my weekly progress of the project on this blog.

GSoC progress in community bonding period.

Worked on some issues in the Issue Tracker

1. There was a bug in the edit view feature, where the form submission button was missing. It was a small task to add the button. Currently, I am working on removing two buttons in create view form as discussed in the issue page.

2. There is a bug in the recent tables list on the navigation panel which doesn’t show the recently visited tables. I’ve submitted a PR which solves this issue.

Started working on the first enhancement

As I’ve stated in my proposal that I won’t be able to give 5-6 hours from 28th May to 8th June. I’ve already started working on the first enhancement. The aim is to append a modal on the page which would ask for login, instead of rendering the whole login page, which would preserve the information which user entered in the previous session.

Progress

I’ve made the modal which is correctly appended on the page when session times out and logs in the user.

Implementation in detail-

There is a function UpdateIdleTime() in functions.js which sends post request just a second before the session runs out. When it finds that the session has expired(according to server response, more on this below), it reloads the page. I’ve changed it so that instead of reloadin the page, it appends the modal returned(more on this below).

When updateIdleTime() sends a request to the server and it detects session timeout, it sends with a success false response and updateIdleTime() reloads the page. Instead of returning a false response, I’ve changed the file “libraries/classes/Auth/AuthenticationCookie.php” to return a modal.

When the user logs in again, a new session is started issuing a new session token, all the hidden form elements with the old session token are replaced with the new token. If a new user logs in, it reloads the page.

Security Concerns

I’m currenty testing for security vulnerabilities and implementing security features to prevent unauthorized access.

1. Page is automatically reloaded if the modal is deleted explicilty.
2. All the page functionalities are disabled while the modal appears.
3. …..

See you next time. :)

Selected for GSoC 2018 :).

Why phpmyadmin

I started backend development about a year ago and I’ve been using phpmyadmin ever since. I can’t remember a time in my learning when I didn’t use phpmyadmin to manage my databases. Using phpmyadmin makes the development process so easy and fast because I don’t have to write SQL queries again and again, and can focus on writing code for my app.

I was determined to participate in GSoC this year and wanted to work in php to apply what I had learned and to take my development skills to a higher level. When I saw phpmyadmin as one of the organisations in GSoC, I had instantly decided that I’ll be applying in this org.

Early participation and contributions

I started contributing to phpmyadmin in January this year and I was fascinated to see the well-maintained multi-platform (Web, Desktop, Mobile) support and codebase.

Through my contributions in phpmyadmin I have learnt a lot about open source development and more importantly about good software development techniques. Following are the links to my contributions to the repository.

1. Closed PRs.
2. Open PRs.
3. Issues found

I am excited about contributing to phpmyadmin and hope to meet the expected standards.

Project Abstract

The aim of the project is to implement some of the enhancements suggested in the issue tracker to improve user experience(adding new useful features and making the app easier to use), security and performance.

Project Mentor : Isaac Bennetch

Blog and Checkins

I have still to figure out how often would I post on this blog. I am planning something of a weekly update posts but that’d depend on how the work progresses. I’ll stay in contact with my mentor, reporting the progress, getting feedback about the ideas and the code I’ll write.

Following is the list of enhancements I’ll work on this summer.

1. ​Add modal to login after session expired

The default idle session timeout is 24 minutes, after which the session is destroyed and the user has to login again to use the app. The problem is that the login page is rendered over the current page leading to loss of all the information user was entering. Login page overwrites the current page

Enhancement -

Append a modal on the page which would ask for login, instead of rendering the whole login page, which would preserve information.

2. Importing table from a CSV file

When a table is imported from a CSV file, the default table name is Table ## and default names for the columns are COL ##. Default table and column names

Enhancement-

Set the imported table name to the name of the imported file and column names to the titles of each column in the csv file OR ask the user to enter table and column names.

3. ​Increase input field width for varchar(255)

Enhancement-

In the insert row page, the dimensions of varchar textareas are small, which could be increased. As suggested in a ​comment​, the user appreciated presence of this feature in the earlier version and thus can be re-considered in the current version for a better user-experience.

Default width of varchar textareas in insert page

4. ​Edit an existing row and setting auto increment should prompt to add index

Making an existing int column ‘auto_increment’ shows the error message “#1075 - Incorrect table definition; there can be only one auto column and it must be defined as a key”. Error message when trying to add auto increment on existing column

Enhancement-

Show a dialog to add an index to the column.

5. ​Configuration option to disable drag drop files completely

Enhancement-

Add a configuration option to disable drag and drop files support.

6.​ ​Error popup

In the error popup, it is difficult to read the query when it overflows and it’s not possible to copy the query as the popup closes when clicked. Error popup

Enhancement-

1. Disable onclick close by default and add a close button at the top right corner.
2. Wrap the query if it overflows for better readability.
3. Add a ‘Copy Query’ button.

7.​ ​Add warning for default user/password usage

Enhancement-

1. Don’t use the controluser ‘pma’ if it does not yet exist and don’t use ‘pmapass’ as password.

2. Test if pma:pmapass is used, and warn about it.

8. ​Order distinct values table by count

The distinct values table is currently ordered by value.

Enhancement-

Order the distinct values by count in descending order.

9. ​Store user preferences in browser local storage

All user configuration is stored in the user preferences. When the phpMyAdmin storage configuration is not configured, these do not persist over session.

Enhancement-

Use browser local storage for storing user configuration.

10. ​Add support for CHECK constraints (feature request)

MariaDB (MySQL-compatible) added support for CHECK constraints to version 10.2. (stable=10.2.8). It would be very useful if PHPMyAdmin had a UI for adding and managing these in tbl_create.php and tbl_structure.php.

Enhancement-

Implement a UI for adding and managing CHECK constraints in tbl_create.php and tbl_structure.php.

Last week I refactored some classes by replacing the static methods with instance methods.

Issues:

• #14057 Login screen doesn’t appear in android native browser+chrome
• #14076 Enable columns names by default for CSV in issue #14007 solved
• #14007 Enable columns names by default for CSV exports

The post Weekly phpMyAdmin contributions 2018-W14 appeared first on mauriciofauth.com.

Last week was very productive. I spent most of my time reviewing all the pull requests. I’ve also fixed a few minor bugs and refactored the static methods of some classes.

Issues:

• #14117 Designer: “Add options” dialog doesn’t reset when canceling: #14110 issue fixed
• #14122 Enhancement: Button to add a central column from existing tables #14043
• #14110 Designer: “Add options” dialog doesn’t reset when canceling
• #14126 Designer: Add option dialogue error handling needs to be modified
• #14139 Error while adding central column from existing tables
• #14142 Fix for adding central column, #14139
• #14043 Enhancement- Button to add a central column from existing tables.
• #14111 Designer: Add options dialog is pre-filled with spaces
• #14114 Designer: Add options dialog is pre-filled with spaces #14111 issue fix
• #14113 Designer: Improperly escaped code in “Add option” dialog #14109 issue fix
• #14109 Designer: Improperly escaped code in “Add option” dialog
• #14115 Fix for “Export tables as seperate files”, #14080
• #14080 “Export tables as separate files” gives empty download
• #14097 JavaScript error in Designer: getElementById() #14079 issue fix
• #14079 JavaScript error in Designer: getElementById()
• #14092 Fixes error 404 on creating views, issue #14082
• #14082 error 404 on creating new view in new PhpMyAdmin releases
• #14012 Fix errors on zoom search errors, issue #13439
• #13439 Table zoom page errors
• #14031 Fixes error in foreign key sql generation + drop foreign key contraint
• #14010 Fix broken Relation View
• #14009 Problem with saving the relation view
• #14037 fix: wrong argument type passed when creating foreign key
• #13941 Argument 5 passed to PhpMyAdmin\Table::_getSQLToCreateForeignKey() must be of the type array, string given
• #14105 Cannot read property sql_query of undefined: #14104 issue fix
• #14104 Cannot read property ‘sql_query’ of undefined
• #14101 sqlform is undefined error when browsing a GIS table

The post Weekly phpMyAdmin contributions 2018-W13 appeared first on mauriciofauth.com.

Last week was mostly spent on reviewing GSoC proposals and on reviewing pull requests. I’m also refactored the PhpMyAdmin\Relation class by replacing the static methods with instance methods.

Issues:

• #14103 jQuery.fn.blur() event shorthand is deprecated
• #14107 Addapt getHtmlForAddColumn to use twig template
• #14071 Database structure page improperly escaped HTML code
• #14098 Fix improperly escaped HTML code in database structure page; issue #14071
• #14011 “Show Report Details” button does not work
• #14116 Addapt getHtmlForTableNavigation to twig template
• #14108 Fixes JavaScript error when editing rows with Internet Explorer
• #14072 Import fails with error code 200
• #14085 Fixes Import Fail
• #14064 Fix buggy sql.lib.php on debian9 with PHP7.2
• #13981 Remove inline styles in ReplicationGui.php
• #14030 Fatal error: Uncaught TypeError: Argument 5 passed to PhpMyAdmin\Table::_getSQLToCreateForeignKey() must be of the type array, string given

The post Weekly phpMyAdmin contributions 2018-W12 appeared first on mauriciofauth.com.

Last week I refactored some classes by replacing the static methods with instance methods and fixed a few minor bugs.

Issues:

• #14075 Fixes for issue 14059
• #14061 Login form not shown with Internet Explorer 11
• #14059 Indexes are not created on Structure tab after update to 4.7.9

The post Weekly phpMyAdmin contributions 2018-W11 appeared first on mauriciofauth.com.

Last week I back-ported a bug fix that was affecting branch 4.7. I removed the references to PMD in favor of Designer and I also refactored some classes by replacing the static methods with instance methods.

Issues:

• #14025 Class ‘ZipArchive’ not found in /srv/pma/libraries/classes/ZipExtension.php:29
• #14000 Add PHP Nightly version to Travis-CI
• #13931 Sort is broken
• #14036 Fix broken sort
• #14042 Rename PMD to Designer

The post Weekly phpMyAdmin contributions 2018-W08 appeared first on mauriciofauth.com.

Last week was very productive. I refactored some classes to use instance methods, fixed some bugs and merged some PRs.

Issues:

• #13988 Fix case in which Config::checkServers is never called
• #13769 Database list and general settings not being displayed during development of phpmyadmin
• #12611 :hover applied incorrectly on ‘table indexes’ rows for multiple-column indexes.
• #13952 Insert page should prompt before reducing number of rows
• #13987 Prompt before reducing number of rows
• #14015 Refactor PhpMyAdmin\CreateAddField class
• #14020 Fix icons with wrong size in the Original theme
• #14013 Some icons with wrong size in the Original theme
• #13983 Fix for broken profiling; issue #13969
• #13969 Profiling breaks user session
• #13980 Hover not working on master but working on stable
• #13998 Fixes Hover on tables
• #14001 Fix table horizontal scrolling
• #13959 Too many fields(>13 in my case) in a table leading to page overflow

The post Weekly phpMyAdmin contributions 2018-W07 appeared first on mauriciofauth.com.

Last week I refactored some classes by replacing the static methods with instance methods and fixed a few minor bugs.

Issues:

• #13972 Refactor PhpMyAdmin\InsertEdit class
• #13778 ‘Range search’ window keeps popup when trying to select another operator at Search menu.
• #13971 Fix for issue #13778
• #13979 removed inline styles from AuthenticationConfig.php file-issue 12262
• #13985 Refactor PhpMyAdmin\ErrorReport class
• #13986 Refactor PhpMyAdmin\Normalization class
• #13976 Columns not sorting
• #13978 Fix textarea failed to popup (issue #13518)
• #13518 Cell editor missing the popup edit box (which has ‘Press escape to cancel editing’ at bottom)

The post Weekly phpMyAdmin contributions 2018-W06 appeared first on mauriciofauth.com.

Last week I refactored the PhpMyAdmin\CentralColumns class by replacing the static methods with instance methods.

Issues:

• #13090 Row coloring issue @ Indexes
• #13877 Fix Row coloring issue@Indexes
• #13880 Colour issue in rows on hover
• #13960 Fixes Colour issue in rows on hover
• #13966 Refactor PhpMyAdmin\CentralColumns class

The post Weekly phpMyAdmin contributions 2018-W05 appeared first on mauriciofauth.com.

Last week I extracted the PhpMyAdmin\Utils\HttpRequest class from the PhpMyAdmin\Util class and refactored it to use instance methods instead of static methods.

Issues:

• #13932 count() function error on PHP7.2
• #13578 Allow custom number of rows to be inserted
• #13876 Allow Custom number of rows to be inserted

The post Weekly phpMyAdmin contributions 2018-W04 appeared first on mauriciofauth.com.

Last week I refactored the PhpMyAdmin\BrowseForeigners class by replacing the static methods with instance methods. I also investigated ways to increase code coverage.

Issues:

• #13935 Simplify returns
• #13936 Use assertNotSame instead of comparison in test

The post Weekly phpMyAdmin contributions 2018-W03 appeared first on mauriciofauth.com.

Last week I refactored the PhpMyAdmin\Display\Export class by moving the HTML to the templates and replacing the static methods with instance methods.

The post Weekly phpMyAdmin contributions 2018-W02 appeared first on mauriciofauth.com.

Last week was a bit calmer. I removed the javascript that was used to hide the action buttons on the table structure page. This code had a very low performance and the short-term solution was to remove it.

Issues:

• #13694 MenuResizer is VERY slow
• #13905 Use CSS to hide table structure action buttons

The post Weekly phpMyAdmin contributions 2018-W01 appeared first on mauriciofauth.com.