Tags:
create new tag
, view all tags
A WikiClone written in ASP, running on IIS, with some interesting features such as content syndication (see WikiRssExtension for example) and separation of presentation and logic using XML and XSL - see http://openwiki.com/. One oddity is that double-clicking calls up the edit page function.

Some useful URLs to test TWiki's WikiRssExtension on OpenWiki:

-- RichardDonkin - 08 Jan 2002

I really like the presentation of OpenWiki. I also like the fact that it's DB-driven.

Somethings I don't like (I know it's version 0.77, but these gripes are related to design decisions in OpenWIki):

  • No ability to embed HTML (this let's it adhere to "pure" Wiki rules, but I think the inability to allow HTML is a detriment, IMHO)
  • Like every other Wiki out there, this one imposes a new set of annoyingly different tag markup rules.

Overall, I just don't think it will be good enoughfor an "Corporate Intranet" Wiki, but I think it has great potential (and you can be certain that you will see some OpenWiki iceas incorporated into LunaWiki smile )

-- DavidWeller - 10 Jan 2002

I also don't like the fact that it uses IIS (but that's a personal viewpoint - why use IIS when Apache/Perl/PHP are free and robust?), but it does seem to be adding features very quickly and has some nice features already. Definitely worth stealing ideas from! Also, the simple use of sans-serif fonts by default makes the site look nicer IMO.

-- RichardDonkin - 10 Jan 2002

Hehe... well, IIS is free if you have a MS OS smile Really, I don't think it would take much to convert the app to Java/Perl/Pick-your-favorite-language. From my perspective, it needs to be rewritten in C# smile . I think that there's some really good ideas in OpenWiki though. I'm really going to have to look at it once I get some spare cycles (right now, I'm amazed I'm taking time to read/post on the TWiki.org site!!!).

-- DavidWeller - 10 Jan 2002

Yes, IIS is free as long as someone has bought you an expensive copy of NT/2000 Server, and as long as you don't count the cost of locking down IIS and patching it every month or two, or cleaning up after IIS worms smile I think I'm also suffering from a reaction to the use of VB as part of ASP, but it's obviously quite powerful. I suspect PHP would be equally quick to develop in, see Wiki:WikiClones for some PHP Wikis (something else to soak up your time smile ).

-- RichardDonkin - 11 Jan 2002

I like OpenWiki as well for it's ViewXmlSource and that it is 'all xml'. With native XML support coming for NN and Mozilla and pretty good implementations of X-smiles and Opera in place...xml seems to be a very good direction. Especially consiering XmlRpc SvgPlugin XForms and other standards (and soon to be!) more integrated support of XML makes a lot of sense IMHO

-- DennisDaniels - 21 Mar 2002

I confess I don't know that much about Perl, but microsoft software can be very powerfull (although that can also mean bloated). C#seems to have some good database functionality linq and lanmbda expressions. With ASP you can represent I believe a tree with a single ASP tag, which will get decoded into hundreds of lines of Java script. You can control the event behavior though C# in a seperate file on the server side and not have to worry about all the comunication issues between the webpage and the server as that is handled by the server. These seems like a very effecnt way to code to me. However, I guess the drawback may be is these standard tags may give a very canned feel. Actualy, I would like it if there was a plugin which would allow integrating some ASP-like technology into twiki.

-- JohnCreighton - Jully 21 2009

Edit | Attach | Watch | Print version | History: r8 < r7 < r6 < r5 < r4 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r8 - 2009-07-23 - JohnCreighton
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2016 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.