From: Bill S. <wsk...@sp...> - 2003-12-06 16:38:55
|
Is anyone using the Wiki plugin that was written by chromatic a couple of years ago? I installed it and it crashed whenever I tried to save a page. I found the bug and fixed it. But this plugin isn't being maintained by anyone. An e-mail to chr...@or... produced no response. I've also changed a few other things -- added an "Edit" button and made the input form into a new template. This way the input form isn't always visible until a user actually wants to make a change. Made the text area into a table with a single cell that has a shaded background -- sets the Wiki area off a little better. At any rate, this was my first experience with a Wiki and I thought it worked out well on my Slash site (engineering department page on company intranet). Would like to pass along the changes I've made (including bug fix -- perhaps someone has a more elegant solution than what I've done) for anyone interested. Does anyone have suggestions on how to proceed? All of these plugins add an overwhelming amount of new functionality to Slash... (Blob, FAQster, Wiki, Galleria, etc.) Is there a central location where all of the plugins are documented? If not, is there a place where we could start doing this? (A Wiki would be a great place to do this!) --Bill |
From: Shane <sh...@lo...> - 2003-12-06 17:41:48
|
On Dec 6, 2003, at 6:38 AM, Bill Skellenger wrote: > Is anyone using the Wiki plugin that was written by chromatic a couple > of years ago? > > I installed it and it crashed whenever I tried to save a page. I > found the bug and fixed it. But this plugin isn't being maintained by > anyone. An e-mail to chr...@or... produced no response. > > I've also changed a few other things -- added an "Edit" button and > made the input form into a new template. This way the input form > isn't always visible until a user actually wants to make a change. > Made the text area into a table with a single cell that has a shaded > background -- sets the Wiki area off a little better. > > At any rate, this was my first experience with a Wiki and I thought it > worked out well on my Slash site (engineering department page on > company intranet). Would like to pass along the changes I've made > (including bug fix -- perhaps someone has a more elegant solution than > what I've done) for anyone interested. Does anyone have suggestions > on how to proceed? Some of the OSDN guys should know how to get a hold of him, if he's not on this listserv. I would suggest getting the original author's consent/OK and submitting the project to Sourceforge. That way you can keep going with it, if you choose to, and others can help you out with it, if you want them to. > > All of these plugins add an overwhelming amount of new functionality > to Slash... (Blob, FAQster, Wiki, Galleria, etc.) Is there a central > location where all of the plugins are documented? If not, is there a > place where we could start doing this? (A Wiki would be a great place > to do this!) There's this: http://slashcode.com/search.pl?topic=24 There used to be a plugin that was used on Slashcode to keep track of all the plugins. You can view it's source here: http://cvs.slashcode.com/cgi-bin/cvsweb/unsupported/plugins/Repository/ I think it was more or less moved to the unsupported because of lackoftime to keep it working with current-cvs-slash (imho). I started a plugin-manager plugin for my own use earlier this year. I never finished it. I can put it up in CVS if you want to try it. Shane |
From: Gerry G. <ge...@ge...> - 2003-12-08 16:51:04
|
I played around with the Wiki plugin a while back, and although it seemed to pretty much work, it wasn't really what I wanted. FWIW, I found a Wiki with source control back end (SubWiki, uses Subversion), and I've been hacking it for a while to generalize it to HTML and XML pages. It's in Python, so I had to learn python for it, but it has come along quite nicely so far. When I'm not thinking completely straight, I want to adapt this tool for use with Slashcode. The idea would be a versioned content management systems for testing and development, then you would upload the content to the database as a complete release. Basically, I want the versioned content management system for the "authored" parts of the content, but I still want the comment system and fast database implementation of Slashcode. Gerry Gleason On 2003.12.06 05:38 Bill Skellenger wrote: > Is anyone using the Wiki plugin that was written by chromatic a > couple of years ago? > > I installed it and it crashed whenever I tried to save a page. I > found the bug and fixed it. But this plugin isn't being maintained > by anyone. An e-mail to chr...@or... produced no response. > > I've also changed a few other things -- added an "Edit" button and > made the input form into a new template. This way the input form > isn't always visible until a user actually wants to make a change. > Made the text area into a table with a single cell that has a shaded > background -- sets the Wiki area off a little better. > > At any rate, this was my first experience with a Wiki and I thought > it worked out well on my Slash site (engineering department page on > company intranet). Would like to pass along the changes I've made > (including bug fix -- perhaps someone has a more elegant solution > than what I've done) for anyone interested. Does anyone have > suggestions on how to proceed? > > All of these plugins add an overwhelming amount of new functionality > to Slash... (Blob, FAQster, Wiki, Galleria, etc.) Is there a > central location where all of the plugins are documented? If not, is > there a place where we could start doing this? (A Wiki would be a > great place to do this!) > > --Bill > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for > IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys > admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-development > |
From: Bill S. <wsk...@sp...> - 2003-12-09 00:24:47
|
Hi Gerry, Gerry Gleason wrote: > When I'm not thinking completely straight, I want to adapt this tool > for use with Slashcode. The idea would be a versioned content > management systems for testing and development, then you would upload > the content to the database as a complete release. Basically, I want > the versioned content management system for the "authored" parts of > the content, but I still want the comment system and fast database > implementation of Slashcode. So it sounds like you basically want to have a Wiki, that only those with privileges can edit -- (versioning is part of the Wiki), but still have the comment system as implemented by Slash. Sorry, just thinking out loud so that I'm clear. This is a great idea, and I bet that it wouldn't be too out of the question to implement using chromatic's stuff as a base. (I'm assuming you're speaking of written content though, and not code content) The "upload file as bodytext" functions already exist elsewhere, you could implement this without too much trouble probably... I'd also like to look into chromatic's Wiki module, because this could also be extended to allow more tags. I looked around at other Wikis and found that there are some tags like "==" that indicate a <h2> font or whatever. I saw another that made WikiWords in a grey color if their page(s) hadn't been defined yet. That was another good idea. Regardless, I think the Wiki concept is pretty cool. It was hard to explain to the guys in my department. Funny how something so simple can be so effective. For pages like FAQs and whatnot, it's the ticket. The problem is that I can't get people to contribute!! --Bill |
From: Gerry G. <ge...@ge...> - 2003-12-09 08:26:10
|
On 2003.12.08 13:24 Bill Skellenger wrote: > Hi Gerry, > > Gerry Gleason wrote: > >> When I'm not thinking completely straight, I want to adapt this tool >> for use with Slashcode. The idea would be a versioned content >> management systems for testing and development, then you would >> upload the content to the database as a complete release. >> Basically, I want the versioned content management system for the >> "authored" parts of the content, but I still want the comment system >> and fast database implementation of Slashcode. > > > So it sounds like you basically want to have a Wiki, that only those > with privileges can edit -- (versioning is part of the Wiki), but > still have the comment system as implemented by Slash. Sorry, just > thinking out loud so that I'm clear. Some Wikis do versioning, but from what I've seen it isn't universal. I'm pretty sure the Slash plugin just updates the Wiki pages in the database, writing over the previous page contents. That was the biggest reason I did not find it good enough. It was a while ago, but I'm pretty sure I verified that this was the case. > This is a great idea, and I bet that it wouldn't be too out of the > question to implement using chromatic's stuff as a base. (I'm > assuming you're speaking of written content though, and not code > content) The "upload file as bodytext" functions already exist > elsewhere, you could implement this without too much trouble > probably... Like I said, I don't think it does the versioning. There is also the issue of just how much stuff you can edit with the web-interface, and whether that is versioned too. I've already gone pretty far beyond the basic Wiki functionality so that I can edit the templates with the same tool (this is a more or less 'pass-through' mode that I call HTML mode). Even more powerful is the XML processing I've added later that supports pulling markup from several sources. > I'd also like to look into chromatic's Wiki module, because this > could also be extended to allow more tags. I looked around at other > Wikis and found that there are some tags like "==" that indicate a > <h2> font or whatever. I saw another that made WikiWords in a grey > color if their page(s) hadn't been defined yet. That was another > good idea. That's a difficulty of Wikis, I don't think there is one common way of doing things. In SubWiki, a WikiWord would just display as typed with a '?' after it linked to the add function for that page. I was very disappointed in the quality of the HTML generated by the SubWiki formatter. I'm sure that it varies a lot with other implementations, but all-in-all if find Wiki to be to much of a user oriented hack to use seriously. > Regardless, I think the Wiki concept is pretty cool. It was hard to > explain to the guys in my department. Funny how something so simple > can be so effective. For pages like FAQs and whatnot, it's the > ticket. The problem is that I can't get people to contribute!! Wikis have their proponents who think they are the greatest, but there is a learning curve. It doesn't have the critical mass to make the case for it easily. Gerry > --Bill > > > |