GSOC 2017 - Manish Bisht Introduction - Contributing Guide
Hi, I want to contribute in phpmyadmin. I am interested in the "Enhancement collection B" of the GSOC 2017. I like this set very much and love to contribute in this. Regarding my skills, I have a good knowledge in PHP, HTML, CSS, Javascript, C/C++ and Python. It would be great if I get some initial guidance to carry on my journey in contributing here. Thanks :) Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me
Hello Manish Manish Bisht píše v So 18. 02. 2017 v 12:11 +0530:
I want to contribute in phpmyadmin. I am interested in the "Enhancement collection B" of the GSOC 2017. I like this set very much and love to contribute in this.
Please check the Google Summer of Code timeline: https://developers.google.com/open-source/gsoc/timeline As you can see, the accepted organizations were not yet announced, so we still do not know if our project will be chosen to participate. In case we will be accepted, you can then follow our applicant guide: https://github.com/phpmyadmin/phpmyadmin/wiki/GSoC_2017_applicant_guide -- Michal Čihař | https://cihar.com/ | https://weblate.org/
Congratulations to all, PhpMyAdmin selected for GSOC' 17. As I have said that I am interested in "Enhancement collection B". Also I want to know how to contact the mentor for this project. The name mentioned was User:Ibennetch. Where I can contact him ? Also is this project is in priority I am asking this question because to get to know that how much useful this project after completion will be for the community. As I have seen that it contains good list of features and making responsive is best task as now things are going mobile first. Thanks, Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me On Mon, Feb 20, 2017 at 3:24 PM, Michal Čihař <michal@cihar.com> wrote:
Hello Manish
Manish Bisht píše v So 18. 02. 2017 v 12:11 +0530:
I want to contribute in phpmyadmin. I am interested in the "Enhancement collection B" of the GSOC 2017. I like this set very much and love to contribute in this.
Please check the Google Summer of Code timeline:
https://developers.google.com/open-source/gsoc/timeline
As you can see, the accepted organizations were not yet announced, so we still do not know if our project will be chosen to participate.
In case we will be accepted, you can then follow our applicant guide:
https://github.com/phpmyadmin/phpmyadmin/wiki/GSoC_2017_applicant_guide
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Hi Manish Bisht, On 2/27/17 12:48 PM, Manish Bisht wrote:
Congratulations to all, PhpMyAdmin selected for GSOC' 17.
As I have said that I am interested in "Enhancement collection B". Also I want to know how to contact the mentor for this project. The name mentioned was User:Ibennetch. Where I can contact him ?
Thanks for calling this to my attention, I have updated my page at https://github.com/phpmyadmin/phpmyadmin/wiki/User:Ibennetch - this was missing due to an oversight. In general, if you have specific questions or just generally wish to introduce yourself, this mailing list is the best place. I'm certainly available by individual email for private matters, but at this point most information is helpful to all potential students and better handled on the mailing list.
Also is this project is in priority I am asking this question because to get to know that how much useful this project after completion will be for the community. As I have seen that it contains good list of features and making responsive is best task as now things are going mobile first.
You are welcome to customize your application by adding or removing features, as long as your schedule is reasonable to fill the expected time frame. If there are specific implementation details about the responsive design that you wish to discuss with the development team, you can either do that publicly on this mailing list or by submitting your application early and asking for feedback. If Google handles the application process like they have done in the past, your application can be edited until the deadline and we will make comments through the GSoC interface. Regards, Isaac
Thanks,
Manish Bisht Email : hi@manishbisht.me <mailto:hi@manishbisht.me> Website : https://manishbisht.me <https://manishbisht.me/>
On Mon, Feb 20, 2017 at 3:24 PM, Michal Čihař <michal@cihar.com <mailto:michal@cihar.com>> wrote:
Hello Manish
Manish Bisht píše v So 18. 02. 2017 v 12:11 +0530: > I want to contribute in phpmyadmin. I am interested in the > "Enhancement collection B" of the GSOC 2017. I like this set very > much and love to contribute in this.
Please check the Google Summer of Code timeline:
https://developers.google.com/open-source/gsoc/timeline <https://developers.google.com/open-source/gsoc/timeline>
As you can see, the accepted organizations were not yet announced, so we still do not know if our project will be chosen to participate.
In case we will be accepted, you can then follow our applicant guide:
https://github.com/phpmyadmin/phpmyadmin/wiki/GSoC_2017_applicant_guide <https://github.com/phpmyadmin/phpmyadmin/wiki/GSoC_2017_applicant_guide>
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
_______________________________________________ Developers mailing list Developers@phpmyadmin.net <mailto:Developers@phpmyadmin.net> https://lists.phpmyadmin.net/mailman/listinfo/developers <https://lists.phpmyadmin.net/mailman/listinfo/developers>
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Thanks for the reply I was going through the list "Enhancements collection B" 1. Improve responsive/mobile interface Is there any designed proposed for mobile till now ? The last discussion i can see on this was this https://github.com/phpmyadmin/phpmyadmin/wiki/2014-02_Meeting#Mobile_version... Also it was mentioned that this feature in right now not in priority. My plan to implement this is to make the interface the mobile first. a) The left side bar with id pma_navigation can be put as the menu/hamburger icon for smaller screens b) The div with id serverinfo will still remain at the top. c) The div with id topmenucontainer will be implemented as the horizontal scrolling like this (Open this link in https://getmdl.io/components/index.html on mobile you will see the horizontal scrolling at the top for about, getting started etc.) d) The div with id maincontainer will now have the main content. Home page boxes (General settings, Database server etc) can be shown in the vertical order. Right now it works but there is still some spacing issues. Tables can be shown with some min-width because it will not fit on smaller screen sizes when the number of columns in the table are more or they contains large strings like tokens, md5 strings etc. For status tab one more horizontal slider will be required and then the tables one after another in vertical position. e) The div with id pma_console will remain same. when it is opened on smaller devices it will open on the full screen instead of half as in larger screens. Any suggestions will be helpful to make it more better. Also someone form design team please review it so that it can be implemented correctly. I will post about others features in the list as soon as I done with the next one. Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me On Tue, Feb 28, 2017 at 1:10 AM, Isaac Bennetch <bennetch@gmail.com> wrote:
Hi Manish Bisht,
On 2/27/17 12:48 PM, Manish Bisht wrote:
Congratulations to all, PhpMyAdmin selected for GSOC' 17.
As I have said that I am interested in "Enhancement collection B". Also I want to know how to contact the mentor for this project. The name mentioned was User:Ibennetch. Where I can contact him ?
Thanks for calling this to my attention, I have updated my page at https://github.com/phpmyadmin/phpmyadmin/wiki/User:Ibennetch - this was missing due to an oversight.
In general, if you have specific questions or just generally wish to introduce yourself, this mailing list is the best place. I'm certainly available by individual email for private matters, but at this point most information is helpful to all potential students and better handled on the mailing list.
Also is this project is in priority I am asking this question because to get to know that how much useful this project after completion will be for the community. As I have seen that it contains good list of features and making responsive is best task as now things are going mobile first.
You are welcome to customize your application by adding or removing features, as long as your schedule is reasonable to fill the expected time frame. If there are specific implementation details about the responsive design that you wish to discuss with the development team, you can either do that publicly on this mailing list or by submitting your application early and asking for feedback. If Google handles the application process like they have done in the past, your application can be edited until the deadline and we will make comments through the GSoC interface.
Regards, Isaac
Thanks,
Manish Bisht Email : hi@manishbisht.me <mailto:hi@manishbisht.me> Website : https://manishbisht.me <https://manishbisht.me/>
On Mon, Feb 20, 2017 at 3:24 PM, Michal Čihař <michal@cihar.com <mailto:michal@cihar.com>> wrote:
Hello Manish
Manish Bisht píše v So 18. 02. 2017 v 12:11 +0530: > I want to contribute in phpmyadmin. I am interested in the > "Enhancement collection B" of the GSOC 2017. I like this set very > much and love to contribute in this.
Please check the Google Summer of Code timeline:
https://developers.google.com/open-source/gsoc/timeline <https://developers.google.com/open-source/gsoc/timeline>
As you can see, the accepted organizations were not yet announced, so we still do not know if our project will be chosen to participate.
In case we will be accepted, you can then follow our applicant guide:
https://github.com/phpmyadmin/phpmyadmin/wiki/GSoC_2017_ applicant_guide <https://github.com/phpmyadmin/phpmyadmin/wiki/ GSoC_2017_applicant_guide>
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
_______________________________________________ Developers mailing list Developers@phpmyadmin.net <mailto:Developers@phpmyadmin.net> https://lists.phpmyadmin.net/mailman/listinfo/developers <https://lists.phpmyadmin.net/mailman/listinfo/developers>
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
2. Disable charset conversion when importing with SET NAMES The list comment on this link https://github.com/phpmyadmin/ phpmyadmin/issues/9419 gives the start to solve this issue. Indeed the charset handling seems to be broken on the import:
- the iso-8859-1 file imports fine if I choose utf-8 and keep SET NAMES latin1
- the iso-8859-1 file imports fine if I choose iso-8859-1 and remove SET NAMES latin1
- the iso-8859-1 file imports corrupted if I choose iso-8859-1 and keep SET NAMES latin1
Any suggestions will be helpful to implement it in more better way.
I will post about others features on this list as soon as I done with the next one. Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me On Tue, Feb 28, 2017 at 11:52 PM, Manish Bisht <manish.bisht490@gmail.com> wrote:
Thanks for the reply I was going through the list "Enhancements collection B"
1. Improve responsive/mobile interface Is there any designed proposed for mobile till now ? The last discussion i can see on this was this https://github.com/phpmya dmin/phpmyadmin/wiki/2014-02_Meeting#Mobile_version:_follow-up Also it was mentioned that this feature in right now not in priority.
My plan to implement this is to make the interface the mobile first. a) The left side bar with id pma_navigation can be put as the menu/hamburger icon for smaller screens b) The div with id serverinfo will still remain at the top. c) The div with id topmenucontainer will be implemented as the horizontal scrolling like this (Open this link in https://getmdl.io/components/index.html on mobile you will see the horizontal scrolling at the top for about, getting started etc.) d) The div with id maincontainer will now have the main content. Home page boxes (General settings, Database server etc) can be shown in the vertical order. Right now it works but there is still some spacing issues. Tables can be shown with some min-width because it will not fit on smaller screen sizes when the number of columns in the table are more or they contains large strings like tokens, md5 strings etc. For status tab one more horizontal slider will be required and then the tables one after another in vertical position. e) The div with id pma_console will remain same. when it is opened on smaller devices it will open on the full screen instead of half as in larger screens.
Any suggestions will be helpful to make it more better. Also someone form design team please review it so that it can be implemented correctly.
I will post about others features in the list as soon as I done with the next one.
Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me
On Tue, Feb 28, 2017 at 1:10 AM, Isaac Bennetch <bennetch@gmail.com> wrote:
Hi Manish Bisht,
On 2/27/17 12:48 PM, Manish Bisht wrote:
Congratulations to all, PhpMyAdmin selected for GSOC' 17.
As I have said that I am interested in "Enhancement collection B". Also I want to know how to contact the mentor for this project. The name mentioned was User:Ibennetch. Where I can contact him ?
Thanks for calling this to my attention, I have updated my page at https://github.com/phpmyadmin/phpmyadmin/wiki/User:Ibennetch - this was missing due to an oversight.
In general, if you have specific questions or just generally wish to introduce yourself, this mailing list is the best place. I'm certainly available by individual email for private matters, but at this point most information is helpful to all potential students and better handled on the mailing list.
Also is this project is in priority I am asking this question because to get to know that how much useful this project after completion will be for the community. As I have seen that it contains good list of features and making responsive is best task as now things are going mobile first.
You are welcome to customize your application by adding or removing features, as long as your schedule is reasonable to fill the expected time frame. If there are specific implementation details about the responsive design that you wish to discuss with the development team, you can either do that publicly on this mailing list or by submitting your application early and asking for feedback. If Google handles the application process like they have done in the past, your application can be edited until the deadline and we will make comments through the GSoC interface.
Regards, Isaac
Thanks,
Manish Bisht Email : hi@manishbisht.me <mailto:hi@manishbisht.me> Website : https://manishbisht.me <https://manishbisht.me/>
On Mon, Feb 20, 2017 at 3:24 PM, Michal Čihař <michal@cihar.com <mailto:michal@cihar.com>> wrote:
Hello Manish
Manish Bisht píše v So 18. 02. 2017 v 12:11 +0530: > I want to contribute in phpmyadmin. I am interested in the > "Enhancement collection B" of the GSOC 2017. I like this set very > much and love to contribute in this.
Please check the Google Summer of Code timeline:
https://developers.google.com/open-source/gsoc/timeline <https://developers.google.com/open-source/gsoc/timeline>
As you can see, the accepted organizations were not yet announced, so we still do not know if our project will be chosen to participate.
In case we will be accepted, you can then follow our applicant guide:
https://github.com/phpmyadmin/phpmyadmin/wiki/GSoC_2017_ applicant_guide <https://github.com/phpmyadmin/phpmyadmin/wiki/GSoC_2017_ap plicant_guide>
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
_______________________________________________ Developers mailing list Developers@phpmyadmin.net <mailto:Developers@phpmyadmin.net> https://lists.phpmyadmin.net/mailman/listinfo/developers <https://lists.phpmyadmin.net/mailman/listinfo/developers>
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Hi Manish Bisht píše v St 01. 03. 2017 v 13:30 +0530:
2. Disable charset conversion when importing with SET NAMES The list comment on this link https://github.com/phpmyadmin/phpmyadmi n/issues/9419 gives the start to solve this issue.
Indeed the charset handling seems to be broken on the import: the iso-8859-1 file imports fine if I choose utf-8 and keep SET NAMES latin1 the iso-8859-1 file imports fine if I choose iso-8859-1 and remove SET NAMES latin1 the iso-8859-1 file imports corrupted if I choose iso-8859-1 and keep SET NAMES latin1
Any suggestions will be helpful to implement it in more better way.
I've already commented on this in the issue tracker: Not sure how to best approach this, but we should avoid the double encoding problem. On the other side the charset selector for import has to stay for SQL files which do not do SET NAMES and for other formats like CSV. Maybe disable our charset conversion once we spot SET NAMES in the SQL? If you want to followup, please do that in the issue tracker, so that whole discussion stays in one place. -- Michal Čihař | https://cihar.com/ | https://weblate.org/
What will be necessary features required for the *Theme Generator* and Expectations so that i can propose a good proposal and focus on these features and generate a good idea On Wed, Mar 1, 2017 at 2:10 PM, Michal Čihař <michal@cihar.com> wrote:
Hi
Manish Bisht píše v St 01. 03. 2017 v 13:30 +0530:
2. Disable charset conversion when importing with SET NAMES The list comment on this link https://github.com/phpmyadmin/phpmyadmi n/issues/9419 gives the start to solve this issue.
Indeed the charset handling seems to be broken on the import: the iso-8859-1 file imports fine if I choose utf-8 and keep SET NAMES latin1 the iso-8859-1 file imports fine if I choose iso-8859-1 and remove SET NAMES latin1 the iso-8859-1 file imports corrupted if I choose iso-8859-1 and keep SET NAMES latin1
Any suggestions will be helpful to implement it in more better way.
I've already commented on this in the issue tracker:
Not sure how to best approach this, but we should avoid the double encoding problem. On the other side the charset selector for import has to stay for SQL files which do not do SET NAMES and for other formats like CSV. Maybe disable our charset conversion once we spot SET NAMES in the SQL?
If you want to followup, please do that in the issue tracker, so that whole discussion stays in one place.
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Any update on my implementation of this ?
1. Improve responsive/mobile interface Is there any designed proposed for mobile till now ? The last discussion i can see on this was this https://github.com/phpmyadmin/phpmyadmin/wiki/ 2014-02_Meeting#Mobile_version:_follow-up Also it was mentioned that this feature in right now not in priority. My plan to implement this is to make the interface the mobile first. a) The left side bar with id pma_navigation can be put as the menu/hamburger icon for smaller screens b) The div with id serverinfo will still remain at the top. c) The div with id topmenucontainer will be implemented as the horizontal scrolling like this (Open this link in https://getmdl.io/components/index.html on mobile you will see the horizontal scrolling at the top for about, getting started etc.) d) The div with id maincontainer will now have the main content. Home page boxes (General settings, Database server etc) can be shown in the vertical order. Right now it works but there is still some spacing issues. Tables can be shown with some min-width because it will not fit on smaller screen sizes when the number of columns in the table are more or they contains large strings like tokens, md5 strings etc. For status tab one more horizontal slider will be required and then the tables one after another in vertical position. e) The div with id pma_console will remain same. when it is opened on smaller devices it will open on the full screen instead of half as in larger screens.
Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me On Wed, Mar 1, 2017 at 2:44 PM, shishir bondre <bondreshishir@gmail.com> wrote:
What will be necessary features required for the *Theme Generator* and Expectations so that i can propose a good proposal and focus on these features and generate a good idea
On Wed, Mar 1, 2017 at 2:10 PM, Michal Čihař <michal@cihar.com> wrote:
Hi
Manish Bisht píše v St 01. 03. 2017 v 13:30 +0530:
2. Disable charset conversion when importing with SET NAMES The list comment on this link https://github.com/phpmyadmin/phpmyadmi n/issues/9419 gives the start to solve this issue.
Indeed the charset handling seems to be broken on the import: the iso-8859-1 file imports fine if I choose utf-8 and keep SET NAMES latin1 the iso-8859-1 file imports fine if I choose iso-8859-1 and remove SET NAMES latin1 the iso-8859-1 file imports corrupted if I choose iso-8859-1 and keep SET NAMES latin1
Any suggestions will be helpful to implement it in more better way.
I've already commented on this in the issue tracker:
Not sure how to best approach this, but we should avoid the double encoding problem. On the other side the charset selector for import has to stay for SQL files which do not do SET NAMES and for other formats like CSV. Maybe disable our charset conversion once we spot SET NAMES in the SQL?
If you want to followup, please do that in the issue tracker, so that whole discussion stays in one place.
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Yes, I will do my detailed discussion there.
I've already commented on this in the issue tracker: Not sure how to best approach this, but we should avoid the double encoding problem. On the other side the charset selector for import has to stay for SQL files which do not do SET NAMES and for other formats like CSV. Maybe disable our charset conversion once we spot SET NAMES in the SQL? If you want to followup, please do that in the issue tracker, so that whole discussion stays in one place.
Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me On Wed, Mar 1, 2017 at 4:35 PM, Manish Bisht <manish.bisht490@gmail.com> wrote:
Any update on my implementation of this ?
1. Improve responsive/mobile interface Is there any designed proposed for mobile till now ? The last discussion i can see on this was this https://github.com/phpmya dmin/phpmyadmin/wiki/2014-02_Meeting#Mobile_version:_follow-up Also it was mentioned that this feature in right now not in priority. My plan to implement this is to make the interface the mobile first. a) The left side bar with id pma_navigation can be put as the menu/hamburger icon for smaller screens b) The div with id serverinfo will still remain at the top. c) The div with id topmenucontainer will be implemented as the horizontal scrolling like this (Open this link in https://getmdl.io/ components/index.html on mobile you will see the horizontal scrolling at the top for about, getting started etc.) d) The div with id maincontainer will now have the main content. Home page boxes (General settings, Database server etc) can be shown in the vertical order. Right now it works but there is still some spacing issues. Tables can be shown with some min-width because it will not fit on smaller screen sizes when the number of columns in the table are more or they contains large strings like tokens, md5 strings etc. For status tab one more horizontal slider will be required and then the tables one after another in vertical position. e) The div with id pma_console will remain same. when it is opened on smaller devices it will open on the full screen instead of half as in larger screens.
Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me
On Wed, Mar 1, 2017 at 2:44 PM, shishir bondre <bondreshishir@gmail.com> wrote:
What will be necessary features required for the *Theme Generator* and Expectations so that i can propose a good proposal and focus on these features and generate a good idea
On Wed, Mar 1, 2017 at 2:10 PM, Michal Čihař <michal@cihar.com> wrote:
Hi
Manish Bisht píše v St 01. 03. 2017 v 13:30 +0530:
2. Disable charset conversion when importing with SET NAMES The list comment on this link https://github.com/phpmyadmin/phpmyadmi n/issues/9419 gives the start to solve this issue.
Indeed the charset handling seems to be broken on the import: the iso-8859-1 file imports fine if I choose utf-8 and keep SET NAMES latin1 the iso-8859-1 file imports fine if I choose iso-8859-1 and remove SET NAMES latin1 the iso-8859-1 file imports corrupted if I choose iso-8859-1 and keep SET NAMES latin1
Any suggestions will be helpful to implement it in more better way.
I've already commented on this in the issue tracker:
Not sure how to best approach this, but we should avoid the double encoding problem. On the other side the charset selector for import has to stay for SQL files which do not do SET NAMES and for other formats like CSV. Maybe disable our charset conversion once we spot SET NAMES in the SQL?
If you want to followup, please do that in the issue tracker, so that whole discussion stays in one place.
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Hi, I have submitted the draft of my GSoC Proposal. Can someone from the organisation review it. Thanks, Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me On Wed, Mar 1, 2017 at 4:38 PM, Manish Bisht <manish.bisht490@gmail.com> wrote:
Yes, I will do my detailed discussion there.
I've already commented on this in the issue tracker: Not sure how to best approach this, but we should avoid the double encoding problem. On the other side the charset selector for import has to stay for SQL files which do not do SET NAMES and for other formats like CSV. Maybe disable our charset conversion once we spot SET NAMES in the SQL? If you want to followup, please do that in the issue tracker, so that whole discussion stays in one place.
Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me
On Wed, Mar 1, 2017 at 4:35 PM, Manish Bisht <manish.bisht490@gmail.com> wrote:
Any update on my implementation of this ?
1. Improve responsive/mobile interface Is there any designed proposed for mobile till now ? The last discussion i can see on this was this https://github.com/phpmya dmin/phpmyadmin/wiki/2014-02_Meeting#Mobile_version:_follow-up Also it was mentioned that this feature in right now not in priority. My plan to implement this is to make the interface the mobile first. a) The left side bar with id pma_navigation can be put as the menu/hamburger icon for smaller screens b) The div with id serverinfo will still remain at the top. c) The div with id topmenucontainer will be implemented as the horizontal scrolling like this (Open this link in https://getmdl.io/components/index.html on mobile you will see the horizontal scrolling at the top for about, getting started etc.) d) The div with id maincontainer will now have the main content. Home page boxes (General settings, Database server etc) can be shown in the vertical order. Right now it works but there is still some spacing issues. Tables can be shown with some min-width because it will not fit on smaller screen sizes when the number of columns in the table are more or they contains large strings like tokens, md5 strings etc. For status tab one more horizontal slider will be required and then the tables one after another in vertical position. e) The div with id pma_console will remain same. when it is opened on smaller devices it will open on the full screen instead of half as in larger screens.
Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me
On Wed, Mar 1, 2017 at 2:44 PM, shishir bondre <bondreshishir@gmail.com> wrote:
What will be necessary features required for the *Theme Generator* and Expectations so that i can propose a good proposal and focus on these features and generate a good idea
On Wed, Mar 1, 2017 at 2:10 PM, Michal Čihař <michal@cihar.com> wrote:
Hi
Manish Bisht píše v St 01. 03. 2017 v 13:30 +0530:
2. Disable charset conversion when importing with SET NAMES The list comment on this link https://github.com/phpmyadmin/phpmyadmi n/issues/9419 gives the start to solve this issue.
Indeed the charset handling seems to be broken on the import: the iso-8859-1 file imports fine if I choose utf-8 and keep SET NAMES latin1 the iso-8859-1 file imports fine if I choose iso-8859-1 and remove SET NAMES latin1 the iso-8859-1 file imports corrupted if I choose iso-8859-1 and keep SET NAMES latin1
Any suggestions will be helpful to implement it in more better way.
I've already commented on this in the issue tracker:
Not sure how to best approach this, but we should avoid the double encoding problem. On the other side the charset selector for import has to stay for SQL files which do not do SET NAMES and for other formats like CSV. Maybe disable our charset conversion once we spot SET NAMES in the SQL?
If you want to followup, please do that in the issue tracker, so that whole discussion stays in one place.
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Hi, The last discussion I can see on making phpyadmin responsive was this https://github.com/phpmyadmin/phpmyadmin/wiki/2014-02_Meeting#Mobile_ version:_follow-up So I just wanted to know that is this issue is in priority ? Thanks, Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me On Wed, Mar 22, 2017 at 11:37 PM, Manish Bisht <manish.bisht490@gmail.com> wrote:
Hi,
I have submitted the draft of my GSoC Proposal. Can someone from the organisation review it.
Thanks,
Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me
On Wed, Mar 1, 2017 at 4:38 PM, Manish Bisht <manish.bisht490@gmail.com> wrote:
Yes, I will do my detailed discussion there.
I've already commented on this in the issue tracker: Not sure how to best approach this, but we should avoid the double encoding problem. On the other side the charset selector for import has to stay for SQL files which do not do SET NAMES and for other formats like CSV. Maybe disable our charset conversion once we spot SET NAMES in the SQL? If you want to followup, please do that in the issue tracker, so that whole discussion stays in one place.
Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me
On Wed, Mar 1, 2017 at 4:35 PM, Manish Bisht <manish.bisht490@gmail.com> wrote:
Any update on my implementation of this ?
1. Improve responsive/mobile interface Is there any designed proposed for mobile till now ? The last discussion i can see on this was this https://github.com/phpmya dmin/phpmyadmin/wiki/2014-02_Meeting#Mobile_version:_follow-up Also it was mentioned that this feature in right now not in priority. My plan to implement this is to make the interface the mobile first. a) The left side bar with id pma_navigation can be put as the menu/hamburger icon for smaller screens b) The div with id serverinfo will still remain at the top. c) The div with id topmenucontainer will be implemented as the horizontal scrolling like this (Open this link in https://getmdl.io/components/index.html on mobile you will see the horizontal scrolling at the top for about, getting started etc.) d) The div with id maincontainer will now have the main content. Home page boxes (General settings, Database server etc) can be shown in the vertical order. Right now it works but there is still some spacing issues. Tables can be shown with some min-width because it will not fit on smaller screen sizes when the number of columns in the table are more or they contains large strings like tokens, md5 strings etc. For status tab one more horizontal slider will be required and then the tables one after another in vertical position. e) The div with id pma_console will remain same. when it is opened on smaller devices it will open on the full screen instead of half as in larger screens.
Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me
On Wed, Mar 1, 2017 at 2:44 PM, shishir bondre <bondreshishir@gmail.com> wrote:
What will be necessary features required for the *Theme Generator* and Expectations so that i can propose a good proposal and focus on these features and generate a good idea
On Wed, Mar 1, 2017 at 2:10 PM, Michal Čihař <michal@cihar.com> wrote:
Hi
Manish Bisht píše v St 01. 03. 2017 v 13:30 +0530:
2. Disable charset conversion when importing with SET NAMES The list comment on this link https://github.com/phpmyadmin/ phpmyadmi n/issues/9419 gives the start to solve this issue.
> Indeed the charset handling seems to be broken on the import: > the iso-8859-1 file imports fine if I choose utf-8 and keep SET > NAMES latin1 > the iso-8859-1 file imports fine if I choose iso-8859-1 and remove > SET NAMES latin1 > the iso-8859-1 file imports corrupted if I choose iso-8859-1 and > keep SET NAMES latin1 >
Any suggestions will be helpful to implement it in more better way.
I've already commented on this in the issue tracker:
Not sure how to best approach this, but we should avoid the double encoding problem. On the other side the charset selector for import has to stay for SQL files which do not do SET NAMES and for other formats like CSV. Maybe disable our charset conversion once we spot SET NAMES in the SQL?
If you want to followup, please do that in the issue tracker, so that whole discussion stays in one place.
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
On 3/29/17 10:26 AM, Manish Bisht wrote:
Hi,
The last discussion I can see on making phpyadmin responsive was this https://github.com/phpmyadmin/phpmyadmin/wiki/2014-02_Meeting#Mobile_version... <https://github.com/phpmyadmin/phpmyadmin/wiki/2014-02_Meeting#Mobile_version:_follow-up> So I just wanted to know that is this issue is in priority ?
I think the problem is that we can't disrupt large amounts of the core phpMyAdmin code for a massive rewrite, and no developer wishes to take responsibility to work on this. It will probably make a good GSoC project, because a student will have time to work on it through the summer and, even if parts remain unfinished, the project won't stall and languish with lack of developer time. I hope that makes sense. I'm not sure how it will fit with GSoC due to the timeline; part of me sees ways we can improve this with minimal effort and disruption to the code and the other part of me thinks it's going to be too big for GSoC and too disruptive to implement. Honestly, out of all the tasks on the entire ideas list, this is the one I'm least certain about. A good proposal for this particular project would probably show how the student has anticipated working on this in stages and has an honest and reasonable assessment of the time required. As far as whether I, personally, think it's a good direction for the project to go; I'm about 60% for including it and 40% don't see the point (figuring that most serious development can't yet occur on a tablet of phone, but realizing the value of being responsive to the handful of user requests we've had for this functionality).
Thanks,
Manish Bisht Email : hi@manishbisht.me <mailto:hi@manishbisht.me> Website : https://manishbisht.me <https://manishbisht.me/>
On Wed, Mar 22, 2017 at 11:37 PM, Manish Bisht <manish.bisht490@gmail.com <mailto:manish.bisht490@gmail.com>> wrote:
Hi,
I have submitted the draft of my GSoC Proposal. Can someone from the organisation review it.
Thanks,
Manish Bisht Email : hi@manishbisht.me <mailto:hi@manishbisht.me> Website : https://manishbisht.me <https://manishbisht.me/>
On Wed, Mar 1, 2017 at 4:38 PM, Manish Bisht <manish.bisht490@gmail.com <mailto:manish.bisht490@gmail.com>> wrote:
Yes, I will do my detailed discussion there.
I've already commented on this in the issue tracker: Not sure how to best approach this, but we should avoid the double encoding problem. On the other side the charset selector for import has to stay for SQL files which do not do SET NAMES and for other formats like CSV. Maybe disable our charset conversion once we spot SET NAMES in the SQL? If you want to followup, please do that in the issue tracker, so that whole discussion stays in one place.
Manish Bisht Email : hi@manishbisht.me <mailto:hi@manishbisht.me> Website : https://manishbisht.me <https://manishbisht.me/>
On Wed, Mar 1, 2017 at 4:35 PM, Manish Bisht <manish.bisht490@gmail.com <mailto:manish.bisht490@gmail.com>> wrote:
Any update on my implementation of this ?
1. Improve responsive/mobile interface Is there any designed proposed for mobile till now ? The last discussion i can see on this was this https://github.com/phpmyadmin/phpmyadmin/wiki/2014-02_Meeting#Mobile_version... <https://github.com/phpmyadmin/phpmyadmin/wiki/2014-02_Meeting#Mobile_version:_follow-up> Also it was mentioned that this feature in right now not in priority. My plan to implement this is to make the interface the mobile first. a) The left side bar with id pma_navigation can be put as the menu/hamburger icon for smaller screens b) The div with id serverinfo will still remain at the top. c) The div with id topmenucontainer will be implemented as the horizontal scrolling like this (Open this link in https://getmdl.io/components/index.html <https://getmdl.io/components/index.html> on mobile you will see the horizontal scrolling at the top for about, getting started etc.) d) The div with id maincontainer will now have the main content. Home page boxes (General settings, Database server etc) can be shown in the vertical order. Right now it works but there is still some spacing issues. Tables can be shown with some min-width because it will not fit on smaller screen sizes when the number of columns in the table are more or they contains large strings like tokens, md5 strings etc. For status tab one more horizontal slider will be required and then the tables one after another in vertical position. e) The div with id pma_console will remain same. when it is opened on smaller devices it will open on the full screen instead of half as in larger screens.
Manish Bisht Email : hi@manishbisht.me <mailto:hi@manishbisht.me> Website : https://manishbisht.me <https://manishbisht.me/>
On Wed, Mar 1, 2017 at 2:44 PM, shishir bondre <bondreshishir@gmail.com <mailto:bondreshishir@gmail.com>> wrote:
What will be necessary features required for the *Theme Generator* and Expectations so that i can propose a good proposal and focus on these features and generate a good idea
On Wed, Mar 1, 2017 at 2:10 PM, Michal Čihař <michal@cihar.com <mailto:michal@cihar.com>> wrote:
Hi
Manish Bisht píše v St 01. 03. 2017 v 13:30 +0530: > 2. Disable charset conversion when importing with SET NAMES > The list comment on this link https://github.com/phpmyadmin/phpmyadmi <https://github.com/phpmyadmin/phpmyadmi> > n/issues/9419 gives the start to solve this issue. > > > Indeed the charset handling seems to be broken on the import: > > the iso-8859-1 file imports fine if I choose utf-8 and keep SET > > NAMES latin1 > > the iso-8859-1 file imports fine if I choose iso-8859-1 and remove > > SET NAMES latin1 > > the iso-8859-1 file imports corrupted if I choose iso-8859-1 and > > keep SET NAMES latin1 > > > > Any suggestions will be helpful to implement it in more better way.
I've already commented on this in the issue tracker:
Not sure how to best approach this, but we should avoid the double encoding problem. On the other side the charset selector for import has to stay for SQL files which do not do SET NAMES and for other formats like CSV. Maybe disable our charset conversion once we spot SET NAMES in the SQL?
If you want to followup, please do that in the issue tracker, so that whole discussion stays in one place.
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
_______________________________________________ Developers mailing list Developers@phpmyadmin.net <mailto:Developers@phpmyadmin.net> https://lists.phpmyadmin.net/mailman/listinfo/developers <https://lists.phpmyadmin.net/mailman/listinfo/developers>
_______________________________________________ Developers mailing list Developers@phpmyadmin.net <mailto:Developers@phpmyadmin.net> https://lists.phpmyadmin.net/mailman/listinfo/developers <https://lists.phpmyadmin.net/mailman/listinfo/developers>
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
I have just proposed some basic idea on how I will I work on it. Here is the link to my GSOC Proposal https://docs.google.com/document/d/104yLW991tFJ0mOZNRMm-nx-nxnlI8oWmHWV-_tXF... Can you please review and check if everything is going fine. Thanks, Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me On Wed, Mar 29, 2017 at 8:33 PM, Isaac Bennetch <bennetch@gmail.com> wrote:
On 3/29/17 10:26 AM, Manish Bisht wrote:
Hi,
The last discussion I can see on making phpyadmin responsive was this https://github.com/phpmyadmin/phpmyadmin/wiki/2014-02_ Meeting#Mobile_version:_follow-up <https://github.com/phpmyadmin/phpmyadmin/wiki/2014-02_Meeting#Mobile_ version:_follow-up> So I just wanted to know that is this issue is in priority ?
I think the problem is that we can't disrupt large amounts of the core phpMyAdmin code for a massive rewrite, and no developer wishes to take responsibility to work on this. It will probably make a good GSoC project, because a student will have time to work on it through the summer and, even if parts remain unfinished, the project won't stall and languish with lack of developer time. I hope that makes sense. I'm not sure how it will fit with GSoC due to the timeline; part of me sees ways we can improve this with minimal effort and disruption to the code and the other part of me thinks it's going to be too big for GSoC and too disruptive to implement.
Honestly, out of all the tasks on the entire ideas list, this is the one I'm least certain about. A good proposal for this particular project would probably show how the student has anticipated working on this in stages and has an honest and reasonable assessment of the time required.
As far as whether I, personally, think it's a good direction for the project to go; I'm about 60% for including it and 40% don't see the point (figuring that most serious development can't yet occur on a tablet of phone, but realizing the value of being responsive to the handful of user requests we've had for this functionality).
Thanks,
Manish Bisht Email : hi@manishbisht.me <mailto:hi@manishbisht.me> Website : https://manishbisht.me <https://manishbisht.me/>
On Wed, Mar 22, 2017 at 11:37 PM, Manish Bisht <manish.bisht490@gmail.com <mailto:manish.bisht490@gmail.com>> wrote:
Hi,
I have submitted the draft of my GSoC Proposal. Can someone from the organisation review it.
Thanks,
Manish Bisht Email : hi@manishbisht.me <mailto:hi@manishbisht.me> Website : https://manishbisht.me <https://manishbisht.me/>
On Wed, Mar 1, 2017 at 4:38 PM, Manish Bisht <manish.bisht490@gmail.com <mailto:manish.bisht490@gmail.com>> wrote:
Yes, I will do my detailed discussion there.
I've already commented on this in the issue tracker: Not sure how to best approach this, but we should avoid the double encoding problem. On the other side the charset selector for import has to stay for SQL files which do not do SET NAMES and for other formats like CSV. Maybe disable our charset conversion once we spot SET NAMES in the SQL? If you want to followup, please do that in the issue tracker, so that whole discussion stays in one place.
Manish Bisht Email : hi@manishbisht.me <mailto:hi@manishbisht.me> Website : https://manishbisht.me <https://manishbisht.me/>
On Wed, Mar 1, 2017 at 4:35 PM, Manish Bisht <manish.bisht490@gmail.com <mailto:manish.bisht490@gmail.com>> wrote:
Any update on my implementation of this ?
1. Improve responsive/mobile interface Is there any designed proposed for mobile till now ? The last discussion i can see on this was this https://github.com/phpmyadmin/ phpmyadmin/wiki/2014-02_Meeting#Mobile_version:_follow-up <https://github.com/phpmyadmin/phpmyadmin/wiki/ 2014-02_Meeting#Mobile_version:_follow-up> Also it was mentioned that this feature in right now not in priority. My plan to implement this is to make the interface the mobile first. a) The left side bar with id pma_navigation can be put as the menu/hamburger icon for smaller screens b) The div with id serverinfo will still remain at the top. c) The div with id topmenucontainer will be implemented as the horizontal scrolling like this (Open this link in https://getmdl.io/components/index.html <https://getmdl.io/components/index.html> on mobile you will see the horizontal scrolling at the top for about, getting started etc.) d) The div with id maincontainer will now have the main content. Home page boxes (General settings, Database server etc) can be shown in the vertical order. Right now it works but there is still some spacing issues. Tables can be shown with some min-width because it will not fit on smaller screen sizes when the number of columns in the table are more or they contains large strings like tokens, md5 strings etc. For status tab one more horizontal slider will be required and then the tables one after another in vertical position. e) The div with id pma_console will remain same. when it is opened on smaller devices it will open on the full screen instead of half as in larger screens.
Manish Bisht Email : hi@manishbisht.me <mailto:hi@manishbisht.me> Website : https://manishbisht.me <https://manishbisht.me/>
On Wed, Mar 1, 2017 at 2:44 PM, shishir bondre <bondreshishir@gmail.com <mailto:bondreshishir@gmail.com>> wrote:
What will be necessary features required for the *Theme Generator* and Expectations so that i can propose a good proposal and focus on these features and generate a good idea
On Wed, Mar 1, 2017 at 2:10 PM, Michal Čihař <michal@cihar.com <mailto:michal@cihar.com>> wrote:
Hi
Manish Bisht píše v St 01. 03. 2017 v 13:30 +0530: > 2. Disable charset conversion when importing with SET NAMES > The list comment on this link https://github.com/phpmyadmin/phpmyadmi <https://github.com/phpmyadmin/phpmyadmi> > n/issues/9419 gives the start to solve this issue. > > > Indeed the charset handling seems to be broken on the import: > > the iso-8859-1 file imports fine if I choose utf-8 and keep SET > > NAMES latin1 > > the iso-8859-1 file imports fine if I choose iso-8859-1 and remove > > SET NAMES latin1 > > the iso-8859-1 file imports corrupted if I choose iso-8859-1 and > > keep SET NAMES latin1 > > > > Any suggestions will be helpful to implement it in more better way.
I've already commented on this in the issue tracker:
Not sure how to best approach this, but we should avoid the double encoding problem. On the other side the charset selector for import has to stay for SQL files which do not do SET NAMES and for other formats like CSV. Maybe disable our charset conversion once we spot SET NAMES in the SQL?
If you want to followup, please do that in the issue tracker, so that whole discussion stays in one place.
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
_______________________________________________ Developers mailing list Developers@phpmyadmin.net <mailto:Developers@phpmyadmin.net> https://lists.phpmyadmin.net/ mailman/listinfo/developers <https://lists.phpmyadmin.net/ mailman/listinfo/developers>
_______________________________________________ Developers mailing list Developers@phpmyadmin.net <mailto:Developers@phpmyadmin. net> https://lists.phpmyadmin.net/mailman/listinfo/developers <https://lists.phpmyadmin.net/ mailman/listinfo/developers>
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
participants (4)
-
Isaac Bennetch -
Manish Bisht -
Michal Čihař -
shishir bondre