| verzia 1.9, 2002/12/14 04:31:06 |
verzia 1.10, 2003/02/12 19:38:03 |
|
|
| 2. Copy/ftp/whatever them to your development web site. |
2. Copy/ftp/whatever them to your development web site. |
| 3. Using a browser, run phpMyEditSetup.php to log on |
3. Using a browser, run phpMyEditSetup.php to log on |
| to your MySQL server. |
to your MySQL server. |
| 4. Select a database and table. |
4. Select a database, table and table key. |
| 5. Script phpMyEditSetup.php will attempt to write two files |
5. Script phpMyEditSetup.php will attempt to write two files |
| and will display appropriate table handling PHP file. |
and will display appropriate table handling PHP file. |
| 6. If the file write to the directory where the files were to be |
6. If the file write to the directory where the files were to be |
|
|
| and then run it in the same directory that you used for |
and then run it in the same directory that you used for |
| phpMyEdit.class.php file. |
phpMyEdit.class.php file. |
| |
|
| The generated PHP file is pretty heavily commented. If there's |
Portions of the generated PHP file are commented and described. |
| anything you don't understand, look on the phpMyEdit web site. You |
However phpMyEdit has amount of available features, so if there is |
| can also subscribe into mailinglist and feel free to ask your |
anything you do not understand, look into official phpMyEdit |
| question there. |
documentation. You can also subscribe into mailinglist and feel free |
| |
to ask your question there. |
| |
|
| 3. Documentation |
3. Documentation |
| |
|
| This README file is deprecated. New documentation is currently being |
phpMyEdit comes with extensive and exhaustive documentation in SGML, |
| created. We are using DocBook documentation tool. SGML sources are |
HTML and PDF format with huge amount of options, possibilities and |
| in CVS, see doc/sgml/ directory. If you have DocBook properly |
information described. It is available for download as a separate |
| installed you should be able to generate desirable output format of |
package from phpMyEdit homepage or its project management page. |
| phpMyEdit documentation. HTML generated documentation will show up |
|
| in next 5.3 release. |
|
| |
|
| 4. Homepage and download |
4. Homepage and download |
| |
|
| The official homepage of phpMyEdit project is |
The official phpMyEdit homepage is: |
| |
http://www.platon.sk/projects/phpMyEdit/ |
| http://phpMyEdit.sf.net/ |
|
| |
The phpMyEdit project management page is: |
| |
http://www.platon.sk/projects/main_page.php?project_id=5 |
| |
|
| You can also download the latest version in "Download" section of |
You can download the latest version in "Download" sections |
| phpMyEdit homepage. |
of these pages. |
| |
|
| 5. Bug reporting |
5. Bug reporting and support |
| |
|
| I'm happy to accept bug reports, suggestions for improvement, or |
I'm happy to accept bug reports, feature requests, suggestions for |
| improved code, preferably via SourceForge where everyone can see |
improvement, or improved code, preferably via our Platon.SK project |
| them. |
management interface where everyone can see them. |
| |
|
| If you're submitting a bug report, please include the main table |
If you are submitting a bug report, please include the main table |
| schema (mysqldump -d [database_name] [table_name]), schema for |
schema (mysqldump -d [database_name] [table_name]), schema for |
| supporting ['values']['table'] tables, and the contents of the |
supporting ['values']['table'] tables, and the contents of the |
| generated PHP file in your bug report. Also be sure to strip out |
generated PHP file in your bug report. Also be sure to strip out |
| database host/user/password info from the generated file. |
database host/user/password info from the generated file. |
| |
|
| 6. Mailinglist |
There is also discussion forum available for asking support |
| |
questions or branstorming about new features. phpMyEdit has also its |
| There is phpMyEdit mailinglist provided on SourceForge.Net. |
own mailinglist and CVS repository. All these issues are described |
| I recommend you to subscribe if you want to discuss new features |
in official documentation. |
| or participate on further ideas and thoughts. |
|
| |
|
| You can join this mailinglist by accessing following link |
|
| |
|
| http://lists.sourceforge.net/lists/listinfo/phpmyedit-discuss |
|
| |
|
| or by sending e-mail with keyword 'subscribe' in Subject line to |
|
| following e-mail address |
|
| |
|
| phpmyedit-discuss-request@lists.sourceforge.net |
|
| |
|
| 7. CVS access |
6. Developers |
| |
|
| Whole phpMyEdit project was imported into Platon SDG |
|
| (http://www.platon.sk/) CVS repository. You can freely checkout |
|
| fresh copy and at least test things, that was broken in your release |
|
| and send particular report to phpMyEdit mailing list. I will |
|
| appreciate it a lot! |
|
| |
|
| Particular CVS instructions follows. Platon CVS repository can be |
|
| checked out through anonymous (pserver) CVS with the following |
|
| instruction set. When prompted for a password for anonymous, simply |
|
| press the Enter key. |
|
| |
|
| export CVSROOT=:pserver:anonymous@kepler.fmph.uniba.sk:/home/cvs |
|
| cvs login |
|
| cvs checkout phpMyEdit |
|
| |
|
| These two commands should work with no problems on any UNIX-like |
|
| system with cvs client installed. For checkouting on MS-Windows |
|
| platform you can use one from several free available CVS client |
|
| softwares. |
|
| |
|
| 8. Developers |
|
| |
|
| This project was the brain child of John McCreesh who has now moved |
This project was the brain child of John McCreesh who has now moved |
| on to other, more pressing projects. Mr. McCreesh had the foresight |
on to other, more pressing projects. Mr. McCreesh had the foresight |
|
|
| maintainer was Jim Kraai who puts a lot of wonderful feature basis |
maintainer was Jim Kraai who puts a lot of wonderful feature basis |
| and continues development in created framework. |
and continues development in created framework. |
| |
|
| Many thanks to the SourceForge crew for providing these facilities |
Many thanks to all those who have contributed code, notes or bug |
| and to all those who have contributed code. Special thanks to Pau |
reports. Special thanks belongs to Pau Aliagas <pau@newtral.com> |
| Aliagas <pau@newtral.com> who converted phpMyEdit to PHP class in |
who converted phpMyEdit to PHP class in version 3.0. |
| version 3.0. |
|
| |
|
| Current maintainer is Ondrej Jombik with help from various phpMyEdit |
Current maintainer is Ondrej Jombik with help from various phpMyEdit |
| community contributors. See doc/ChangeLog for credits. |
community contributors. See doc/ChangeLog for credits. |
| |
|
| 9. Development |
7. Other information |
| |
|
| This program was developed and tested using PHP 4.0.6 and MySQL |
|
| 3.23.44 under Red Hat Linux 7.2. Version 5.0 and further was |
|
| developed and tested using PHP 4.1.2 and MySQL 3.23.47 under Linux |
|
| Mandrake 8.2. |
|
| |
|
| 10. Other information |
|
| |
|
| This README file was initialy written by John McCreesh, updated by |
This README file was initialy written by John McCreesh, updated by |
| Jim Kraai in 3rd December 2001 and updated by Ondrej Jombik in 24th |
Jim Kraai in 3rd December 2001 and updated by Ondrej Jombik in 24th |
| September 2002. |
September 2002 and 12th February 2003. |
| |
|
| If you find any typo or grammar error in this document, feel free to |
If you find any typo or grammar mistake in this document, feel free |
| send me notice and correction. |
to send me notice and correction. |
| |
|