[xwiki-dev] tiny_mce and the integration into xwiki
Sergiu Dumitriu
sergiu.dumitriu at gmail.com
Fri Feb 23 18:41:30 CET 2007
These are indeed good news. It would be great to have a cleaner/easier to
update/easier to extend tinyMCE integration.
Sergiu
On 2/23/07, Christian Gmeiner <christian.gmeiner at gmail.com> wrote:
>
> Good news... I have written two tiny_mce plugins:
> * xwiki -> converts html to xwiki syntax
> * xwikimacro -> show macro dialog
>
> I have done only some parts of the convertion - bold, italc and it
> works very fine. I am reading into the plugin api more deeply so that
> we could provide a better interaction - e.g. links dialog as we know
> it, or image dialg as we know it.
>
> I think that are very good news :)
> greets,
> austriancoder
>
> 2007/2/23, Christian Gmeiner <christian.gmeiner at gmail.com>:
> > Hi...
> >
> > i have looked into the source of the wysiwyg editor stuff and i must
> > say, it is a hack.
> > At the moment this is the structure:
> >
> > tiny_mce --> plugins
> > |
> > |
> > wiki_editor --> own plugins (attachments and macros)
> > |
> > |
> > wysiwyg.vm
> >
> >
> > I think that this is very complex and hard to maintain. Here is my
> > idea how to do it better.
> > 1) Write a tiny_mce plugin called "xwikiMacro" which allows the user
> > to add XWiki macros into
> > his page with the help of tiny_mce
> > 2) Write a post processing plugin, which converts the result from
> > tiny_mce into xwiki markup
> > 3) change wysiwyg.vm to use directly tiny_mce
> > 4) kick wiki_editor
> >
> > This allows us to easier update tiny_mce and it is much simpler to
> > understand whats going on. An other plus is that there is not an other
> > layer in between, which could break everything.
> >
> > Please tell me what you think about my idea. ATM i am working on the
> > marco plugin.
> >
> > chhers,
> > Christian
> >
> > 2007/2/23, Phung Nam <phunghainam at xwiki.com>:
> > > Hi Christian !
> > >
> > > To update tiny_mce to most recent version is not easy ! because we
> have some
> > > modifications in tiny_mce.js (so if you update to most recent version
> then
> > > you also must modify somethings in new tiny_mce.js if Tiny MCE don't
> have
> > > very much modifications in API)
> > >
> > > To update to tiny_mce with new version you can following the steps:
> > >
> > > - Copy the Tiny_MCE with most recent version to replace for tiny_mce
> > > directory
> > > - We configured for tiny_mce in wiki_editor.js
> > > - We use many function of Tiny_MCE in core.js , so we must modify
> somethings
> > > if Tiny_MCE have very much modifications in API
> > >
> > > If you have some questions about this you can email for me .
> > >
> > > Thanks and best regards !
> > > -Phung Nam
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On 2/22/07, Christian Gmeiner < christian.gmeiner at gmail.com> wrote:
> > > >
> > > > Hi all.
> > > >
> > > > At the moment I am looking into problems exists with xwikis wysiwyg
> > > > editor. For instance, it is not possible to save the result of image
> > > > operations in the wiki page.
> > > >
> > > > I have created an jira -
> > > http://jira.xwiki.org/jira/browse/XWIKI-906 -
> > > > to update tiny_mce to most recent version. But know I need more
> > > > informations, where, how, ... tiny_mce is integrated in xwiki. Where
> > > > can i find the setup of tiny_mce...
> > > >
> > > > I hope somebody can help me,
> > > > Christian
> > > >
>
--
http://purl.org/net/sergiu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xwiki.org/pipermail/devs/attachments/20070223/8a1cc5de/attachment.htm
More information about the devs
mailing list