Re: [OS-webwork] OT: Wiki [Was: Webwork 2.0 example app]
4) WikiNaming support (I hate doing [Foo Bar], I like FooBar) But certainly not with this one. The Wiki I'm running now (using SnipSnap) is used by non-techie people, and for them it's certainly easier to use the [Name goes here] style. Also, I don't see how names with non-letters would work (e.g. [Oberg, Rickard]) using the WikiNaming style. I agree WikiNaming is more restrictive, but I've found that it is that restriction that keeps naming conventions very standard. PatLightbody would always be the WikiLink for my page, but without WikiLinking it could be [Pat Lightbody], [PatLightbody], or [Lightbody, Pat] or any other combo. WikiNaming/Linking tends to force people in to a standard way to layout links and generally produces content that magically beings to link itself to other content, unbeknownst to the user. Ie: every word WebWork would be automatically linked to the WebWork page -- the author doesn't need to worry about, gee, should this be a link. It essentially let's the author focus on content and not navigation. Just my off-topic opinion on the matter. I'm going to write a filter for SnipSnap soon so that this is supported :) -Pat --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] OT: Wiki [Was: Webwork 2.0 example app]
SnipSnap has a blog, so you're duplicating effort in any case. Maybe you guys should just add the stuff you want to snipsnap instead... Now we've gone full circle and have gotten totally lost. I think the point was to make a demo/tutorial app for webwork 2.0/xwork/opensymphony, not build a better mousetrap... --Erik --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
[OS-webwork] OT: Wiki [Was: Webwork 2.0 example app]
Yup, I personally like SnipSnap, but it's got a lot of missing features that make it just not good enough. Mainly: 1) Email notifications 2) Revision history 3) File attachments 4) WikiNaming support (I hate doing [Foo Bar], I like FooBar) While I'd love to see an OpenSymphony branded Wiki (or better yet, WikiBlog!), I think SnipSnap is decent. If enough people want to REALLY help write a better WikiBlog that does all of the basics as well as some of the stuff above, I'm willing to help out -- but I don't have too much time to offer. I wouldn't recommend re-inventing the wheel and competing against SnipSnap, except for the fact that SnipSnap uses some funky technologies that I think we could do a better job (OSCache, SiteMesh, WebWork 2.0) -Pat Speaking of Wiki's, did anyone else see this: http://snipsnap.org/space/Radeox They've made their wiki rendering engine (the thing that takes the plain text and simple formatting commands and turns it into XHTML) a separate module you can plug in. Could be a nice data entry option for the Xwork blog... Could also be nice for Joe's Wiki... snip *coughthewikicough* But I guess that sort of thing is already forgotten. Maybe someone will care if the OS wiki is trashed because it sucks and doesn't store old versions. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] OT: Wiki [Was: Webwork 2.0 example app]
Yup, I personally like SnipSnap, but it's got a lot of missing features that make it just not good enough. Mainly: 1) Email notifications Hmm... should be easy to fix. 2) Revision history Check. 3) File attachments Trivial. 4) WikiNaming support (I hate doing [Foo Bar], I like FooBar) Ugh, that's horribly ugly, although doable. While I'd love to see an OpenSymphony branded Wiki (or better yet, WikiBlog!), I think SnipSnap is decent. If enough people want to REALLY help write a better WikiBlog that does all of the basics as well as some of the stuff above, I'm willing to help out -- but I don't have too much time to offer. I have a wiki based on webwork, my own parsing engine and Epeshs Silo engine, it could use some OSCache to speed things up but other than that it's fully functional. If Epesh releases Silo, I could give this out pretty much right now. Anders Hovmöller [EMAIL PROTECTED] http://boxed.killingar.net --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
RE: [OS-webwork] OT: Wiki [Was: Webwork 2.0 example app]
I'm not suggesting we build a Wiki, I just thought it might be nice to allow the nice macros and rendering for posting articles to the blog... -Original Message- From: Patrick Lightbody [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 25, 2003 5:19 PM To: [EMAIL PROTECTED] Subject: [OS-webwork] OT: Wiki [Was: Webwork 2.0 example app] Yup, I personally like SnipSnap, but it's got a lot of missing features that make it just not good enough. Mainly: 1) Email notifications 2) Revision history 3) File attachments 4) WikiNaming support (I hate doing [Foo Bar], I like FooBar) While I'd love to see an OpenSymphony branded Wiki (or better yet, WikiBlog!), I think SnipSnap is decent. If enough people want to REALLY help write a better WikiBlog that does all of the basics as well as some of the stuff above, I'm willing to help out -- but I don't have too much time to offer. I wouldn't recommend re-inventing the wheel and competing against SnipSnap, except for the fact that SnipSnap uses some funky technologies that I think we could do a better job (OSCache, SiteMesh, WebWork 2.0) -Pat Speaking of Wiki's, did anyone else see this: http://snipsnap.org/space/Radeox They've made their wiki rendering engine (the thing that takes the plain text and simple formatting commands and turns it into XHTML) a separate module you can plug in. Could be a nice data entry option for the Xwork blog... Could also be nice for Joe's Wiki... snip *coughthewikicough* But I guess that sort of thing is already forgotten. Maybe someone will care if the OS wiki is trashed because it sucks and doesn't store old versions. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] OT: Wiki [Was: Webwork 2.0 example app]
what is the Silo engine? - Original Message - From: boxed [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 25, 2003 2:30 PM Subject: Re: [OS-webwork] OT: Wiki [Was: Webwork 2.0 example app] Yup, I personally like SnipSnap, but it's got a lot of missing features that make it just not good enough. Mainly: 1) Email notifications Hmm... should be easy to fix. 2) Revision history Check. 3) File attachments Trivial. 4) WikiNaming support (I hate doing [Foo Bar], I like FooBar) Ugh, that's horribly ugly, although doable. While I'd love to see an OpenSymphony branded Wiki (or better yet, WikiBlog!), I think SnipSnap is decent. If enough people want to REALLY help write a better WikiBlog that does all of the basics as well as some of the stuff above, I'm willing to help out -- but I don't have too much time to offer. I have a wiki based on webwork, my own parsing engine and Epeshs Silo engine, it could use some OSCache to speed things up but other than that it's fully functional. If Epesh releases Silo, I could give this out pretty much right now. Anders Hovmöller [EMAIL PROTECTED] http://boxed.killingar.net --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] OT: Wiki [Was: Webwork 2.0 example app]
Hello, I've also been using SnipSnap for a personal KM system and generally like it. Patrick Lightbody wrote: Yup, I personally like SnipSnap, but it's got a lot of missing features that make it just not good enough. Mainly: 1) Email notifications 2) Revision history The developer's thoughts: http://snipsnap.org/comments/RevisionHistory. 3) File attachments Just added in 0.3.4a (http://snipsnap.org/space/version-0.3.4a). 4) WikiNaming support (I hate doing [Foo Bar], I like FooBar) The developer's response: http://snipsnap.org/space/FAQ#WikiLinking. It ends with Start thinking in brackets, it's the same. If you need it, go ahead, there should be only one regex to change. --funzel Also, a different rendering engine (http://snipsnap.org/space/Radeox+RenderEngine+Tutorial) can be written. 5) Multiple blogs. Right now, there's only one blog at the top level. A solution is being investigated. While I'd love to see an OpenSymphony branded Wiki (or better yet, WikiBlog!), I think SnipSnap is decent. If enough people want to REALLY help write a better WikiBlog that does all of the basics as well as some of the stuff above, I'm willing to help out -- but I don't have too much time to offer. I wouldn't recommend re-inventing the wheel and competing against SnipSnap, except for the fact that SnipSnap uses some funky technologies that I think we could do a better job (OSCache, SiteMesh, WebWork 2.0) One area that's not funky is the use of XHTML and CSS for layout. So although you could use SiteMesh, it might not be necessary. See http://snipsnap.org/comments/Changing+Theme+Structure and http://snipsnap.org/space/Themes. See Radeox at http://snipsnap.org/space/Radeox or http://snipsnap.org/space/2003-02-17#SnipSnap_as_Radeox_User -Bill -Pat Speaking of Wiki's, did anyone else see this: http://snipsnap.org/space/Radeox They've made their wiki rendering engine (the thing that takes the plain text and simple formatting commands and turns it into XHTML) a separate module you can plug in. Could be a nice data entry option for the Xwork blog... Could also be nice for Joe's Wiki... snip *coughthewikicough* But I guess that sort of thing is already forgotten. Maybe someone will care if the OS wiki is trashed because it sucks and doesn't store old versions. --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] OT: Wiki [Was: Webwork 2.0 example app]
Patrick Lightbody wrote: Yup, I personally like SnipSnap, but it's got a lot of missing features that make it just not good enough. Mainly: 1) Email notifications 2) Revision history 3) File attachments Agree with these. 4) WikiNaming support (I hate doing [Foo Bar], I like FooBar) But certainly not with this one. The Wiki I'm running now (using SnipSnap) is used by non-techie people, and for them it's certainly easier to use the [Name goes here] style. Also, I don't see how names with non-letters would work (e.g. [Oberg, Rickard]) using the WikiNaming style. My personal requirements for a Wiki, which aren't adressed in SnipSnap, involves a much higher level of security. I do *not* want anyone to be able to just sign up and edit pages. It's a disaster waiting to happen. /Rickard --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
RE: [OS-webwork] OT: Wiki [Was: Webwork 2.0 example app]
We are using twiki here at work for a KM soloution... http://twiki.org Its pretty good.. If you don't mind a PERL CGI based soloution. ..cam.. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rickard Öberg Sent: Wednesday, 26 February 2003 4:51 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] OT: Wiki [Was: Webwork 2.0 example app] Patrick Lightbody wrote: Yup, I personally like SnipSnap, but it's got a lot of missing features that make it just not good enough. Mainly: 1) Email notifications 2) Revision history 3) File attachments Agree with these. 4) WikiNaming support (I hate doing [Foo Bar], I like FooBar) But certainly not with this one. The Wiki I'm running now (using SnipSnap) is used by non-techie people, and for them it's certainly easier to use the [Name goes here] style. Also, I don't see how names with non-letters would work (e.g. [Oberg, Rickard]) using the WikiNaming style. My personal requirements for a Wiki, which aren't adressed in SnipSnap, involves a much higher level of security. I do *not* want anyone to be able to just sign up and edit pages. It's a disaster waiting to happen. /Rickard --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
