bitweaver
Wiki
wiki Home
List Pages
wiki Books
Orphan Pages
wiki Rankings
Photos
List Galleries
Forums
Browse forums
Files
List Galleries
Categories
List Categories
Sign In
Message Boards
»
12. Development - General talk
Newest
Oldest
Threaded
5
10
20
50
100
All
Messages
WYSIWYG Interface
Post Reply
Stephan Borg
Joined: 15 Feb 2004
WYSIWYG Interface
Posted:01 May 2004 (04:17 UTC)
Lester Caine
Joined: 24 Apr 2004
Posted:01 May 2004 (07:18 UTC)
MeatStick
Joined: 24 Feb 2004
Posted:01 May 2004 (08:02 UTC)
a
I believe that is needed in a professional envioroment
Posted:11 May 2004 (17:51 UTC)
xing
Joined: 07 Mar 2004
Posted:24 May 2004 (08:05 UTC)
hemang
Posted:13 Oct 2004 (00:52 UTC)
spiderr
Joined: 08 Feb 2004
Posted:13 Oct 2004 (04:31 UTC)
sulleleven
Joined: 21 Oct 2004
Posted:21 Oct 2004 (18:14 UTC)
sulleleven
Joined: 21 Oct 2004
Posted:21 Oct 2004 (18:19 UTC)
davidm
Joined: 29 Nov 2004
Another solution ?
Posted:29 Nov 2004 (23:51 UTC)
Post Reply
Page 1 of 2
»
1
2
Post
Title
Login
If you are already registered, please enter your login credentials.
Your Name
Anonymous Post
Content Format
Tiki Wiki Syntax
Allow HTML
{quote format_guid="bbcode" comment_id="5090" user="xing"}i have recently added HTMLArea to clyde. it seems to be working well, especially with the new support for mozilla, it's cross platform as well. i used the cvs version of HTMLArea and added some custom buttons to insert some bitweaver specific wikistuff. this is by no means finished. all i wanted to do was test the system and see whether it works for others and what they think about it before going any further. the wikisyntax doesn't show up as html since htmlarea doesn't have an 'html generation engine' as such, but uses the built in system by MSIE or Mozilla. if we want to go as far as making htmlarea work 'well' with bitweaver and make it a true wikieditor, we would have to partially parse stuff on loading the content. _____________________________ partial_parse: _____________________________ to parse: text modification -=...=- !... !!... !!!... ^...^ __...__ ===...=== ''...'' ~~--FF0000:...~~ --- ::...:: lists *... #... tables ||r1c1|r1c2||r2c1|r2c2|| _____________________________ not to parse: links [...] ((..)) other stuff ~np~...~/np~ {cookie} {rss id= } {content id= } %text% {PLUGIN()}{PLUGIN} _____________________________ not quite sure: {img src= width= height= align= desc= link= } collapsed items !- *- #- _____________________________ using this approach, it would be possible to write the page using wiki syntax and as soon as you want to edit the page using htmlarea, the page would be displayed as it is in the editing field, since i've included the original css files in that iframe. the only problem with using htmlarea is, that once the page is saved using htmlarea, the page is stored as html - hence all the wikisyntax is lost. this can't really be avoided unless we use the 'de-html' parser already written for importing html pages (don't know how well that works) to convert html back to wiki. probably it wouldn't be possible to change complicated tables back to wiki, due to the limits set on wikitables. having written all of the above, i've come to ask the question: is it really worth the effort? xing{/quote}
Recent Page Changes
welcome to bitweaver.org
Bitweaver Overview
ReleaseTwo Schema Changelog 2006
PressReleaseOne
Spider's Web
Press Release Two
BitcommercePackage
InfiniBand vs Ethernet Performance
InfiniBand for Dummies
Show More…