You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Joern Nettingsmeier <po...@uni-due.de> on 2006/11/08 12:10:53 UTC
Re: svn commit: r472208 - in /lenya/trunk/src/modules/tinymce: README
sitemap.xmap xslt/page2edit.xsl
chestnut@apache.org wrote:
> Author: chestnut
> Date: Tue Nov 7 11:10:51 2006
> New Revision: 472208
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=472208
> Log:
> added ability to store tinymce files in publication using it
why would anyone want to do that?
if people want to customize their tinymce configuration on a
per-publication basis, we should add some clean hooks to do that (some
are already in place), and not encourage "copy everything and hack away"
customizations - it makes support a lot harder, and it also means that
users will become stuck with a particular tinymce deployment and cannot
easily upgrade.
that said, sorry for the lack of polish in the tiny module - i've been
meaning to finish it for a while, but the lack of an editor api and the
as-yet-unimplemented new lenya-document: uri scheme are blocking it...
regards,
jörn
--
"I don't need backups. I need restore!" - Trad.
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r472208 - in /lenya/trunk/src/modules/tinymce: README
sitemap.xmap xslt/page2edit.xsl
Posted by Joern Nettingsmeier <po...@uni-due.de>.
Doug Chestnut wrote:
>
>
> Joern Nettingsmeier wrote:
>> chestnut@apache.org wrote:
>>> Log:
>>> added ability to store tinymce files in publication using it
>>
>>
>> why would anyone want to do that?
> I don't like adding files to my svn checkout of lenya. It is one more
> thing that I will forget about when I do an install. This way I can add
> tinymce to my own publication repository (possibly even as a
> svn:external property).
ok, i see.
>> if people want to customize their tinymce configuration on a
>> per-publication basis, we should add some clean hooks to do that (some
>> are already in place), and not encourage "copy everything and hack away"
>> customizations - it makes support a lot harder, and it also means that
>> users will become stuck with a particular tinymce deployment and cannot
>> easily upgrade.
> I wonder why this makes support harder? If someone is using tinymce,
> they will be smart enough to know where they unzipped the editor. Using
> the fallback protocol without publication context is useless.
well, my guess was that you wanted different tinymce customisation hacks
in different publications, and i think it should be discouraged to just
copy huge amounts of code to achieve that - it's always better to think
about the knobs you want to tweak and provide hooks in that case.
but obviously your motivation is different, and it now makes sense to me.
> For me, I can now add tinymce to my "core" pub which is a template for
> my other publications.
>> that said, sorry for the lack of polish in the tiny module - i've been
>> meaning to finish it for a while, but the lack of an editor api and the
>> as-yet-unimplemented new lenya-document: uri scheme are blocking it...
> Looks good currently. I am impressed with the code that tinymce
> produces. There is also very good documentation.
yeah, that was what got me hooked to tinymce in the first place. very
neat docs, good package, and excellent api with well-behaved hooks for
just about everything.
regards,
jörn
--
"I don't need backups. I need restore!" - Trad.
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r472208 - in /lenya/trunk/src/modules/tinymce: README
sitemap.xmap xslt/page2edit.xsl
Posted by Doug Chestnut <dh...@virginia.edu>.
Joern Nettingsmeier wrote:
> chestnut@apache.org wrote:
>
>>Author: chestnut
>>Date: Tue Nov 7 11:10:51 2006
>>New Revision: 472208
>>
>>URL: http://svn.apache.org/viewvc?view=rev&rev=472208
>>Log:
>>added ability to store tinymce files in publication using it
>
>
> why would anyone want to do that?
I don't like adding files to my svn checkout of lenya. It is one more
thing that I will forget about when I do an install. This way I can add
tinymce to my own publication repository (possibly even as a
svn:external property).
>
> if people want to customize their tinymce configuration on a
> per-publication basis, we should add some clean hooks to do that (some
> are already in place), and not encourage "copy everything and hack away"
> customizations - it makes support a lot harder, and it also means that
> users will become stuck with a particular tinymce deployment and cannot
> easily upgrade.
I wonder why this makes support harder? If someone is using tinymce,
they will be smart enough to know where they unzipped the editor. Using
the fallback protocol without publication context is useless.
For me, I can now add tinymce to my "core" pub which is a template for
my other publications.
>
> that said, sorry for the lack of polish in the tiny module - i've been
> meaning to finish it for a while, but the lack of an editor api and the
> as-yet-unimplemented new lenya-document: uri scheme are blocking it...
Looks good currently. I am impressed with the code that tinymce
produces. There is also very good documentation.
Thanks,
--Doug
>
> regards,
>
> jörn
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org