<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000066">
Hi all,<br>
<br>
I've made an integration of TinyMCE since Version 2.9.x month ago.<br>
Here you can see the demo:<br>
<a class="moz-txt-link-freetext" href="http://www.michaelkeck.de/projects/pma/demo/">http://www.michaelkeck.de/projects/pma/demo/</a><br>
<br>
Regards<br>
Michael<br>
<br>
--- Original Message ---<br>
Mail from: Marc Delisle<br>
Date: 03.06.2009 15:50
<blockquote cite="mid:4A267FC2.6020208@infomarc.info" type="cite">
<pre wrap="">Michal �iha� a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">Hi
Dne Wed, 03 Jun 2009 08:43:02 -0400
Marc Delisle <a class="moz-txt-link-rfc2396E" href="mailto:marc@infomarc.info"><marc@infomarc.info></a> napsal(a):
</pre>
<blockquote type="cite">
<pre wrap="">I think that transformations require the PMADB mechanism?
</pre>
</blockquote>
<pre wrap="">Yes.
</pre>
<blockquote type="cite">
<pre wrap="">so more users would not have access to them by default.
</pre>
</blockquote>
<pre wrap="">Yes, but we can hardly do something about it. But we're anyway going to
this direction (per user configuration).
</pre>
<blockquote type="cite">
<pre wrap="">Also, I would not be in favor
of having more than one such editor integrated.
Do you have other "transformations" in mind for this case? Note that
currently, with the display options (in browse mode), user has a certain
latitude for display.
</pre>
</blockquote>
<pre wrap="">After quick look into our feature tracker, we could offer at least
following editors:
- input
- textarea
- wysiwig
- textarea with deserialized data [1]
- textarea with hexadecimal data [2]
[1]:<a class="moz-txt-link-freetext" href="https://sourceforge.net/tracker/?func=detail&aid=1615116&group_id=23067&atid=377411">https://sourceforge.net/tracker/?func=detail&aid=1615116&group_id=23067&atid=377411</a>
[2]:<a class="moz-txt-link-freetext" href="https://sourceforge.net/tracker/?func=detail&aid=1611770&group_id=23067&atid=377411">https://sourceforge.net/tracker/?func=detail&aid=1611770&group_id=23067&atid=377411</a>
There would be definitely more options and configuring this per whole
phpMyAdmin installation does not make sense.
</pre>
</blockquote>
<pre wrap=""><!---->
But... I don't like the idea of having to configure this for each column
(unless you have something else in mind). Well in some situations, per
column could make sense but not generally.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Also, transformations imply some API we have to prepare, with the idea
of attracting developers; so I wonder if we can have an API generic
enough in this case. It probably depends on what other transformations
would be supported.
</pre>
</blockquote>
<pre wrap="">The API can be based on our current transformations - the function
which will display edit form can get same parameters, the function for
fetching updated data would get current row of form. I definitely miss
something here, but I don't see why it should be complex.
</pre>
</blockquote>
<pre wrap=""><!---->
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/opensolaris-get">http://p.sf.net/sfu/opensolaris-get</a>
_______________________________________________
Phpmyadmin-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Phpmyadmin-devel@lists.sourceforge.net">Phpmyadmin-devel@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel">https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel</a>
</pre>
</blockquote>
</body>
</html>