Menu
▾
▴
phpwiki-talk
|
From: Reini U. <ru...@x-...> - 2004-02-13 12:16:09
Attachments:
htmlarea.patch
htmlarea.php
|
I have experimental support for htmlarea ready based on http://www.interactivetools.com/products/htmlarea/ version 2.x works on IE >= 5.5 and version 3 with Mozilla >= 1.3 also I've tested both versions. The missing part is the handler on the save step, when the generated HTML code must be converted back to Wiki formatting. This looks like a good job for Jeff (?) Should I commit this library? Attached is lib/htmlarea.php and some needed patches. mkdir lib/htmlarea3 download http://prdownloads.sourceforge.net/itools-htmlarea/HTMLArea-3.0-beta.zip?download and unzip into lib/htmlarea3 -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
|
From: Reini U. <ru...@x-...> - 2004-02-14 19:15:06
|
Reini Urban schrieb: > I have experimental support for htmlarea ready > based on http://www.interactivetools.com/products/htmlarea/ > version 2.x works on IE >= 5.5 > and version 3 with Mozilla >= 1.3 also > I've tested both versions. > > The missing part is the handler on the save step, when the generated > HTML code must be converted back to Wiki formatting. This looks like a > good job for Jeff (?) I've played now some time with htmlarea3. The problem is to convert HTML back to Wiki formatting. The editor is only able to edit pure HTML, since it relies on the browser internal engine. I started with some markup converter class, but I'm not sure if this will make sense, since we 'll need a complete and lossless round trip wiki->html->wiki. html->wiki looks really hard. The other idea which came to me was to store HTML and if the page type is HTML, only the Wysiwyg editor is called on edit. On page type = wiki one can choose "Edit" or "Wysiwyg Edit". This will bloat all pages, we will loose the wiki format once edited in the Wysiwyg editor, but the editor is really cool. I mean REALLY cool! See for example the http://www.guiki.com page. I've also written a phpnuke module for guiki in 30 minutes. What I have now: * phpwiki integration (ok) * htmlarea3 enhanced with a "Create PageLink" button (80%), * a "Toggle Wiki<->Wysiwyg" button besides the original "Toggle Wysiwyg<->HTML" button (70%), * convert wiki->html before Wysiwyg editing (ok), * convert html->wiki after Wysiwyg editing (10%). Do we want to store HTML and loose wiki markup? (Until the backconverter is written) -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
|
From: Oliver B. <ob...@de...> - 2004-02-14 22:46:59
|
Reini Urban wrote: [htmlarea, guiki, Wysiwyg] > html->wiki looks really hard. hmm... > The other idea which came to me was to store HTML and if the page type > is HTML, only the Wysiwyg editor is called on edit. And if the client's browser doesn't support it? My preferred browser is Opera at the moment because of the fast user interface. > On page type = wiki one can choose "Edit" or "Wysiwyg Edit". > This will bloat all pages, we will loose the wiki format once edited in > the Wysiwyg editor, but the editor is really cool. I mean REALLY cool! There are CMS with cool editors. But I don't want to use it - I like the simple approach of Wiki, and to be able to access it with mimimum requirements. So I wonder whether it's really _suitable_ to add a wysiwyg editor? Oliver -- Oliver Betz, Muenchen |
|
From: Reini U. <ru...@x-...> - 2004-02-15 21:59:38
|
Oliver Betz schrieb: > And if the client's browser doesn't support it? My preferred browser > is Opera at the moment because of the fast user interface. Opera is also supported, I forgot to write. >>On page type = wiki one can choose "Edit" or "Wysiwyg Edit". >>This will bloat all pages, we will loose the wiki format once edited in >>the Wysiwyg editor, but the editor is really cool. I mean REALLY cool! > > There are CMS with cool editors. But I don't want to use it - I like > the simple approach of Wiki, and to be able to access it with mimimum > requirements. htmlarea has no requirements. On an older browser it just uses the normal textarea field. > So I wonder whether it's really _suitable_ to add a wysiwyg editor? Htmlarea would be of course optional. The question is if it should be selectable by the admin or by the user. Or not enabled at all. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
|
From: Oliver B. <ob...@de...> - 2004-02-15 22:42:06
|
Reini Urban wrote: > > And if the client's browser doesn't support it? My preferred browser > > is Opera at the moment because of the fast user interface. > > Opera is also supported, I forgot to write. http://www.interactivetools.com/products/htmlarea/ states that the beta version supports IE 5.5+ and Mozilla 1.3+. And in fact, it didn't work with Opera 7.11 (didn't try 7.23) and IE5.0 [...] > htmlarea has no requirements. > On an older browser it just uses the normal textarea field. but with HTML markup, I guess? Otherwise phpwiki had to check for htmlarea support and select what to present? I still don't need it, although I admit that it's cool. If I would like to have functionality like this, I would set up a CMS, no wiki. Oliver -- Oliver Betz, Muenchen |
|
From: Reini U. <ru...@x-...> - 2004-02-16 00:00:22
|
Oliver Betz schrieb: > Reini Urban wrote: >>>And if the client's browser doesn't support it? My preferred browser >>>is Opera at the moment because of the fast user interface. >> >>Opera is also supported, I forgot to write. > > http://www.interactivetools.com/products/htmlarea/ states that the > beta version supports IE 5.5+ and Mozilla 1.3+. And in fact, it > didn't work with Opera 7.11 (didn't try 7.23) and IE5.0 newer operas should do it, as stated in the docs. >>htmlarea has no requirements. >>On an older browser it just uses the normal textarea field. > > but with HTML markup, I guess? Otherwise phpwiki had to check for > htmlarea support and select what to present? no, htmlarea already checks for supported browsers and if none is found just the wikiMarkup in the textarea is used. with htmelarea-enabled I add the original wikimarkup in a hidden div tag after the textarea, so that htmlarea can switch betwween wysiwyg, raw html and wiki mode. > I still don't need it, although I admit that it's cool. If I would > like to have functionality like this, I would set up a CMS, no wiki. Initially I liked the UI and wanted to rewite htmlarea to support wikiformatting. I can still do it with the tools inside htmlarea, but then the wikiformat couldn't be rendered. no wysiwyg. but still the most promising option for me. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X