On http://visualtw.ouvaton.org/VisualTW.html you will find two plugins
for :
- using specific templates in some tiddlers, for structured editing of
fields
- integrating externals visual editors, like wysiwyg rich text or
drawing for tiddlers (the result is stored in specific fields, the
standard text field is used as a summary).
Software components used in this examples are opensource (javascript
FCKeditor, Java JHotDraw). They work both with IE and FF (and others,
I suppose, but I didn't try). Only the SVG drawing result can't be
viewed on IE (which doesn't handle this standard).
I hope this things will be useful for some of yours.
Best regards,
Pascal
1. You mention that this reduces the complexity by keeping the editor
code outside of TW. That sounds good to me. However, I'd like to see
an example of what you mean. Are there any other WYSIWYG TiddlyWikis
that use a 3rd party WYSIWYG editor that is integrated? Asciencepad
seems to be gone...
2. Is there any way to use TinyMCE?
3. Is there any way to use the regular body field of the tiddler
instead of an auxiliary field?, so the data is usable like any regular
tiddler? I tried the example on your site, and what I typed in was
not searchable.
Thanks again, looks good!
On Jun 9, 2:17 am, "VisualTiddlyW...@gmail.com"
<VisualTiddlyW...@gmail.com> wrote:
> Hi all,
>
> Onhttp://visualtw.ouvaton.org/VisualTW.htmlyou will find two plugins
1. Previously, I tried to integrate some Wysiwig editor in TW. But,
these pieces of software need some javascript to be loaded, generally
in the header tags of the page. So, you can't use tiddler macro (with
systemConfig). You have to hack the html TW file itself. Bad solution
in my opinion. I succeed in integrating TinyMCE by loading the
javascript file from a tiddler code. But, then, it's only works with
FF (in IE, you get a blank page). With iFrame there is no more problem
of this nature. The editor page is loaded separately form TW itself
and you don't have to hack TW.
2. Yes, see my previous attempt : http://tiddlywiki.ouvaton.org/Demo.html
. But, it was limited to FF (as I said in point 1).
3. It's what I did for this attempt (see point 2). But, then, you have
to handle a two way conversion : Wiki text => HTML, then HTML => Wiki
text. And it's too much tricky to be stable (some HTML tags have no
equivalent in Wiki text, links conversions, tables conversions,
inserted image, and so on). It's why I choose in visualTW too have an
HTML field and to let the standard text field do its job (using it as
summary). The new TW 2.2 changes the way standard fields (text, title,
date) are accessed. It reinforces my opinion that wiki text and HTML
text have to be treated distinctly (to avoid interacting with TW
"kernel").
Best regards,
Pascal
On Jun 9, 9:23 pm, sb56637 <sb56...@gmail.com> wrote:
> Hey, very nice! I was looking for something like this. A few
> questions:
>
> 1. You mention that this reduces the complexity by keeping the editor
> code outside of TW. That sounds good to me. However, I'd like to see
> an example of what you mean. Are there any other WYSIWYG TiddlyWikis
> that use a 3rd party WYSIWYG editor that is integrated? Asciencepad
> seems to be gone...
>
> 2. Is there any way to use TinyMCE?
>
> 3. Is there any way to use the regular body field of the tiddler
> instead of an auxiliary field?, so the data is usable like any regular
> tiddler? I tried the example on your site, and what I typed in was
> not searchable.
>
> Thanks again, looks good!
>
> On Jun 9, 2:17 am, "VisualTiddlyW...@gmail.com"
>
> <VisualTiddlyW...@gmail.com> wrote:
> > Hi all,
>
> > Onhttp://visualtw.ouvaton.org/VisualTW.htmlyouwill find two plugins
On Jun 9, 4:35 pm, "VisualTiddlyW...@gmail.com"
> > > Onhttp://visualtw.ouvaton.org/VisualTW.htmlyouwillfind two plugins
There are special "Markup" tiddlers whose content is automatically
inserted into specific places in the HTML, so that you CAN add script
loaders and the like into the <head> of your TW document:
MarkupPreHead
MarkupPostHead
MarkupPreBody
MarkupPostBody
Just put your desired content into the appropriately named tiddler.
When you save the document, the content is inserted into the
corresponding location in the TW HTML (e.g., in the <head> section).
The next time you open the document, the Markup* content will be
automatically processed by the browser so your script libraries can be
loaded and initialized.
HTH,
-e
Eric Shulman
TiddlyTools / ELS Design Studios
As an alternative, you can copy HTML plain text in the standard text
field and remove this field in the ViewTemplate (to avoid double
text). But it isn't an elegant solution.
Pascal
> > > > Onhttp://visualtw.ouvaton.org/VisualTW.htmlyouwillfindtwo plugins
Alternatively, iFrame gives a very modular approach. You can developp,
test and maintain the editor separately from TW. It's very
"confortable".
Pascal
This isn't generally true... as pointed out below, you can accomplish
this by putting things in MarkupPreHead (etc.) but another way to do it
is to load things using AJAX and then eval() it. My jsMath plugin does
this.
MarkupPreHead (etc.) uses the browser's code loading mechanisms. But of
course TW has its own ways to load code so I don't think it's strictly
necessary to depend on the browser's loading.
--
Cheers,
Bob McElrath [Univ. of California at Davis, Department of Physics]
"All wars come to an end, at least temporarily. But the authority acquired by
the state hangs on; political power never abdicates." -- Frank Chodorov
Using this way (technical integration instead iFrame integration)
means one plugin for each new type of content (rich text, drawing,
schemas, ...). But, it's more elegant and perharps more powerful
(ex :manage editor configuration with TW, saving state control, etc).
I'll work on that.
Thanks for your advices.
Pascal
On 10 juin, 13:16, "VisualTiddlyW...@gmail.com"