Hi Garvin,

long time ago, I hade same idea with the redesign parts. Now I've found a good Online Wysiwyg called TinyMCE on sfnet.

Now I'm patching this editor just a little for my work on a project (for my normal job). It's nearly full compatible with pma, because I've replased many hardcoded things with php for my job now.

I think I may be able to merge the wysiwyg for soon as possible ... round about 2-4 weeks and will come up with

- image library (upload / browse) - linkbox (search on server, ftp, http) - w3c xhtml 1.0 (I'm still working on it, something goes wrong)

The only terrible is: I would to be able to patch TinyMCE to KHTML-support, but no good documentations found now. Today it works 'only' in Gecko-based and MSIE based (but not Mac) browsers. I've tested with Mozilla 1.4 and Firefox 0.9 (Win/Linux) and MSIE 5.5 MSIE 6.0 (WinXP).

Michael Keck

-----Ursprüngliche Nachricht----- Von: phpmyadmin-devel-admin@lists.sourceforge.net [mailto:phpmyadmin-devel-admin@lists.sourceforge.net]Im Auftrag von Garvin Hicking Gesendet: Mittwoch, 17. November 2004 15:03 An: phpmyadmin-devel@lists.sourceforge.net Cc: kyle@efactormedia.com Betreff: [Phpmyadmin-devel] Input Transformation System

Hi All! (Kyle, I CC'ed you to draw your attention here)

While digging through our SF.Net request tracker, I spotted a rather nice feature request:

https://sourceforge.net/tracker/?func=detail&atid=377411&aid=10611

33&group_id=23067

Basically it's about allowing users to hook into our editing/insertion system, just like the Transformation system now does for displaying data.

I do think this is a very worthful addition for PHP-Developers working with PMA. The implementation is quite straight-forward and should be implementable with enough time (but without any serious problems) - I outlined my imaginations in the feature tracker.

My time currently is quite limited, so if Kyle can take on the job, that would be perfect. If he doesn't have time I still would love to see this feature implemented, and I'd try to work on it in Januar/February, where I should have more time.

The only thing I'm a bit afraid of is that this needs a change of our PMA DB structure, and how to best upgrade tables. Anyways, that can be dealt with later. ;)

Regards, Garvin.

-- ++ Garvin Hicking | Web-Entwickler [PHP] | www.supergarv.de | ICQ 21392242 ++ Developer of | www.phpMyAdmin.net | www.s9y.org

++ Make me happy | http://wishes.garv.info

------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel

Hi, I'd like to work on the solution to this. Perhaps one of the higher-ups would like to give me direction on how best to do this, particularly with what additional fields would go in the PMA database, where to put the transform scripts, what naming conventions you'd prefer, etc.

If it was up to me, I'd just work within the browser transformation and transformation options framework. I would implement transforms on a field-by-field basis, independant of the current mime-type considerations. I'd have a folder called transforms, and inside it I'd have:

--- <transform-name>_edit.transform.php ---

function <transform-name>_edit($field_name, $field_value) { echo("...some sort of input field..."); }

--- <transform-name>_validate.transform.php ---

function <transform-name>_validate ($field_name) { $field_value = $_POST[$field_name];

//Mess with the data some....

if($valid) { return $modified_field_value; } else { return "PMA_error: " . $error_string; //or maybe throw exception } }

--- <transform-name>_browse.transform.php ---

function <transform-name>_browse($field_name, $field_value) { echo("...some representation of the data..."); }

Omitting one of the scripts would cause PMA to fall back on the default. Rather than displaying mime-types in the browser transformation dropdown box, I'd put a list of the <transform-name>'s.

Naturally, this is a break from the old way of doing things (mime-types). This will cause frustration for some. But I think the proposed way is simpler and more effective.

-Kyle Maxwell