twiki.org · Domains · Slashdot Mirror

Wiki by Seumas · 2005-01-23 13:45 · Score: 5, Informative · on How Do You Manage Your Job-Search Info?

I installed a wiki on my main desktop about a year ago. I manage everything with it, including job-hunting, resumes, contacts, reminders. There are many wikis, but I found Twiki to be the most powerful and flexible with the most features. If you're stuck on Windows, you can even install Apache and Cygwin so that you can use Twiki on it. There's even full instructions on their site walking you through that process.

FCKEditor by jacoplane · 2005-01-20 12:08 · Score: 1 · on Using Wikis in Hospitals?

Using something like FCKeditor would enable WYSIWYG editing, so users would not have to learn the Wiki markup language. I'm not sure if it has been ported to any wiki platforms, but it should be easy enough to port to something like twiki.

Re:A great replacement for Dreamweaver by afabbro · 2005-01-08 11:03 · Score: 1 · on Open Source Alternatives to Dreamweaver Templating

I've never seen a "wicki" that did any of that either. (Yeah, I know it's a spelling flame, but still, you're pretty darn clueless).

None of the wicki interfaces I've seen handle table and table formatting at all.

To pick two prominent wikis at random, MediaWiki and Twiki both do tables.

None of the wicki interfaces I've seen handle styles. You do know what css is, right?

To pick two prominent wikis at random, MediaWiki and Twiki both do css.

None of the wicki interfaces I've seen let experts enter any and all html code, php, javascript, perl, etc., that the user might need to when designing the web page.

To pick...oh, never mind.

Do you understand what templates are in real web page design or are you just stupid?

Yes, someone in this thread sure comes across as stupid and ill-informed...

Re:A great replacement for Dreamweaver by afabbro · 2005-01-08 11:03 · Score: 1 · on Open Source Alternatives to Dreamweaver Templating

I've never seen a "wicki" that did any of that either. (Yeah, I know it's a spelling flame, but still, you're pretty darn clueless).

None of the wicki interfaces I've seen handle table and table formatting at all.

To pick two prominent wikis at random, MediaWiki and Twiki both do tables.

None of the wicki interfaces I've seen handle styles. You do know what css is, right?

To pick two prominent wikis at random, MediaWiki and Twiki both do css.

None of the wicki interfaces I've seen let experts enter any and all html code, php, javascript, perl, etc., that the user might need to when designing the web page.

To pick...oh, never mind.

Do you understand what templates are in real web page design or are you just stupid?

Yes, someone in this thread sure comes across as stupid and ill-informed...

TWiki supports structured content and web apps by slicedot · 2004-10-30 15:52 · Score: 1 · on Are we Headed for a Wiki World?

TWiki is a "structured Wiki" since its inception. In addition it is a platform to create web applications.

As with any Wiki, you get some structure with Category topics. For example, if you add a CategoryXml to any page that talks about XML, you can click on the CategoryXml link to find all other pages about XML.

TWiki has several other features which enable users to give structure to content. A TWikiForm[1] can be attached to a page. When you edit a page you get additional HTML widgets on the screen, like for example the "Subject" line and the "Post anonymously" checkbox here on /. A set of pages that share the same type of form is one type of structured content, it is analogous to a table in a relational database.

Giving structure to unstructured content is very important in a corporate environment. The more structure you have the easier it is to run reports and find content of interest by browsing and searching. TWiki has several other innovations supporting structured content:

Name spaces (called TWiki webs)
Parent/child relationship with bread crumbs [2]; done automatically in the background, with the ability to re-parent topics
Use TWiki Templates [3] to create a set of pages that share a common format
Powerful queries can be done with interactive search [4], embedded Search [5] and formatted search [6]
Server side include of other TWiki pages and web pages, selective with patterns if needed [7]. Useful also to create a large composed document with an automatic TOC, such as the TWiki reference manual [8]
RenderListPlugin [9] where the org chart of an organization is defined in one page, and then a subset of the org chart is shown in team home pages, focused around where the team is in the org chart
SpreadSheetPlugin [10] where complex calculations can be done on content pulled dynamically from elsewhere, and visualized with the ChartPlugin [11]

In addition, there are many more features supporting structured content, such as relational databases integration [12], keeping track of action items with global queries and email notifications [13], special Plugin to query forms [14], and more.

These features allow users with moderate skill sets to create web applications with various degrees of complexity.

TWiki supports structured content and web apps by slicedot · 2004-10-30 15:52 · Score: 1 · on Are we Headed for a Wiki World?

TWiki is a "structured Wiki" since its inception. In addition it is a platform to create web applications.

As with any Wiki, you get some structure with Category topics. For example, if you add a CategoryXml to any page that talks about XML, you can click on the CategoryXml link to find all other pages about XML.

TWiki has several other features which enable users to give structure to content. A TWikiForm[1] can be attached to a page. When you edit a page you get additional HTML widgets on the screen, like for example the "Subject" line and the "Post anonymously" checkbox here on /. A set of pages that share the same type of form is one type of structured content, it is analogous to a table in a relational database.

Giving structure to unstructured content is very important in a corporate environment. The more structure you have the easier it is to run reports and find content of interest by browsing and searching. TWiki has several other innovations supporting structured content:

Name spaces (called TWiki webs)
Parent/child relationship with bread crumbs [2]; done automatically in the background, with the ability to re-parent topics
Use TWiki Templates [3] to create a set of pages that share a common format
Powerful queries can be done with interactive search [4], embedded Search [5] and formatted search [6]
Server side include of other TWiki pages and web pages, selective with patterns if needed [7]. Useful also to create a large composed document with an automatic TOC, such as the TWiki reference manual [8]
RenderListPlugin [9] where the org chart of an organization is defined in one page, and then a subset of the org chart is shown in team home pages, focused around where the team is in the org chart
SpreadSheetPlugin [10] where complex calculations can be done on content pulled dynamically from elsewhere, and visualized with the ChartPlugin [11]

In addition, there are many more features supporting structured content, such as relational databases integration [12], keeping track of action items with global queries and email notifications [13], special Plugin to query forms [14], and more.

These features allow users with moderate skill sets to create web applications with various degrees of complexity.

TWiki supports structured content and web apps by slicedot · 2004-10-30 15:52 · Score: 1 · on Are we Headed for a Wiki World?

TWiki is a "structured Wiki" since its inception. In addition it is a platform to create web applications.

As with any Wiki, you get some structure with Category topics. For example, if you add a CategoryXml to any page that talks about XML, you can click on the CategoryXml link to find all other pages about XML.

TWiki has several other features which enable users to give structure to content. A TWikiForm[1] can be attached to a page. When you edit a page you get additional HTML widgets on the screen, like for example the "Subject" line and the "Post anonymously" checkbox here on /. A set of pages that share the same type of form is one type of structured content, it is analogous to a table in a relational database.

Giving structure to unstructured content is very important in a corporate environment. The more structure you have the easier it is to run reports and find content of interest by browsing and searching. TWiki has several other innovations supporting structured content:

Name spaces (called TWiki webs)
Parent/child relationship with bread crumbs [2]; done automatically in the background, with the ability to re-parent topics
Use TWiki Templates [3] to create a set of pages that share a common format
Powerful queries can be done with interactive search [4], embedded Search [5] and formatted search [6]
Server side include of other TWiki pages and web pages, selective with patterns if needed [7]. Useful also to create a large composed document with an automatic TOC, such as the TWiki reference manual [8]
RenderListPlugin [9] where the org chart of an organization is defined in one page, and then a subset of the org chart is shown in team home pages, focused around where the team is in the org chart
SpreadSheetPlugin [10] where complex calculations can be done on content pulled dynamically from elsewhere, and visualized with the ChartPlugin [11]

In addition, there are many more features supporting structured content, such as relational databases integration [12], keeping track of action items with global queries and email notifications [13], special Plugin to query forms [14], and more.

These features allow users with moderate skill sets to create web applications with various degrees of complexity.

TWiki supports structured content and web apps by slicedot · 2004-10-30 15:52 · Score: 1 · on Are we Headed for a Wiki World?

TWiki is a "structured Wiki" since its inception. In addition it is a platform to create web applications.

As with any Wiki, you get some structure with Category topics. For example, if you add a CategoryXml to any page that talks about XML, you can click on the CategoryXml link to find all other pages about XML.

TWiki has several other features which enable users to give structure to content. A TWikiForm[1] can be attached to a page. When you edit a page you get additional HTML widgets on the screen, like for example the "Subject" line and the "Post anonymously" checkbox here on /. A set of pages that share the same type of form is one type of structured content, it is analogous to a table in a relational database.

Giving structure to unstructured content is very important in a corporate environment. The more structure you have the easier it is to run reports and find content of interest by browsing and searching. TWiki has several other innovations supporting structured content:

Name spaces (called TWiki webs)
Parent/child relationship with bread crumbs [2]; done automatically in the background, with the ability to re-parent topics
Use TWiki Templates [3] to create a set of pages that share a common format
Powerful queries can be done with interactive search [4], embedded Search [5] and formatted search [6]
Server side include of other TWiki pages and web pages, selective with patterns if needed [7]. Useful also to create a large composed document with an automatic TOC, such as the TWiki reference manual [8]
RenderListPlugin [9] where the org chart of an organization is defined in one page, and then a subset of the org chart is shown in team home pages, focused around where the team is in the org chart
SpreadSheetPlugin [10] where complex calculations can be done on content pulled dynamically from elsewhere, and visualized with the ChartPlugin [11]

In addition, there are many more features supporting structured content, such as relational databases integration [12], keeping track of action items with global queries and email notifications [13], special Plugin to query forms [14], and more.

These features allow users with moderate skill sets to create web applications with various degrees of complexity.

TWiki supports structured content and web apps by slicedot · 2004-10-30 15:52 · Score: 1 · on Are we Headed for a Wiki World?

TWiki is a "structured Wiki" since its inception. In addition it is a platform to create web applications.

As with any Wiki, you get some structure with Category topics. For example, if you add a CategoryXml to any page that talks about XML, you can click on the CategoryXml link to find all other pages about XML.

TWiki has several other features which enable users to give structure to content. A TWikiForm[1] can be attached to a page. When you edit a page you get additional HTML widgets on the screen, like for example the "Subject" line and the "Post anonymously" checkbox here on /. A set of pages that share the same type of form is one type of structured content, it is analogous to a table in a relational database.

Giving structure to unstructured content is very important in a corporate environment. The more structure you have the easier it is to run reports and find content of interest by browsing and searching. TWiki has several other innovations supporting structured content:

Name spaces (called TWiki webs)
Parent/child relationship with bread crumbs [2]; done automatically in the background, with the ability to re-parent topics
Use TWiki Templates [3] to create a set of pages that share a common format
Powerful queries can be done with interactive search [4], embedded Search [5] and formatted search [6]
Server side include of other TWiki pages and web pages, selective with patterns if needed [7]. Useful also to create a large composed document with an automatic TOC, such as the TWiki reference manual [8]
RenderListPlugin [9] where the org chart of an organization is defined in one page, and then a subset of the org chart is shown in team home pages, focused around where the team is in the org chart
SpreadSheetPlugin [10] where complex calculations can be done on content pulled dynamically from elsewhere, and visualized with the ChartPlugin [11]

In addition, there are many more features supporting structured content, such as relational databases integration [12], keeping track of action items with global queries and email notifications [13], special Plugin to query forms [14], and more.

These features allow users with moderate skill sets to create web applications with various degrees of complexity.

TWiki supports structured content and web apps by slicedot · 2004-10-30 15:52 · Score: 1 · on Are we Headed for a Wiki World?

TWiki is a "structured Wiki" since its inception. In addition it is a platform to create web applications.

As with any Wiki, you get some structure with Category topics. For example, if you add a CategoryXml to any page that talks about XML, you can click on the CategoryXml link to find all other pages about XML.

TWiki has several other features which enable users to give structure to content. A TWikiForm[1] can be attached to a page. When you edit a page you get additional HTML widgets on the screen, like for example the "Subject" line and the "Post anonymously" checkbox here on /. A set of pages that share the same type of form is one type of structured content, it is analogous to a table in a relational database.

Giving structure to unstructured content is very important in a corporate environment. The more structure you have the easier it is to run reports and find content of interest by browsing and searching. TWiki has several other innovations supporting structured content:

Name spaces (called TWiki webs)
Parent/child relationship with bread crumbs [2]; done automatically in the background, with the ability to re-parent topics
Use TWiki Templates [3] to create a set of pages that share a common format
Powerful queries can be done with interactive search [4], embedded Search [5] and formatted search [6]
Server side include of other TWiki pages and web pages, selective with patterns if needed [7]. Useful also to create a large composed document with an automatic TOC, such as the TWiki reference manual [8]
RenderListPlugin [9] where the org chart of an organization is defined in one page, and then a subset of the org chart is shown in team home pages, focused around where the team is in the org chart
SpreadSheetPlugin [10] where complex calculations can be done on content pulled dynamically from elsewhere, and visualized with the ChartPlugin [11]

In addition, there are many more features supporting structured content, such as relational databases integration [12], keeping track of action items with global queries and email notifications [13], special Plugin to query forms [14], and more.

These features allow users with moderate skill sets to create web applications with various degrees of complexity.

TWiki supports structured content and web apps by slicedot · 2004-10-30 15:52 · Score: 1 · on Are we Headed for a Wiki World?

TWiki is a "structured Wiki" since its inception. In addition it is a platform to create web applications.

As with any Wiki, you get some structure with Category topics. For example, if you add a CategoryXml to any page that talks about XML, you can click on the CategoryXml link to find all other pages about XML.

TWiki has several other features which enable users to give structure to content. A TWikiForm[1] can be attached to a page. When you edit a page you get additional HTML widgets on the screen, like for example the "Subject" line and the "Post anonymously" checkbox here on /. A set of pages that share the same type of form is one type of structured content, it is analogous to a table in a relational database.

Giving structure to unstructured content is very important in a corporate environment. The more structure you have the easier it is to run reports and find content of interest by browsing and searching. TWiki has several other innovations supporting structured content:

Name spaces (called TWiki webs)
Parent/child relationship with bread crumbs [2]; done automatically in the background, with the ability to re-parent topics
Use TWiki Templates [3] to create a set of pages that share a common format
Powerful queries can be done with interactive search [4], embedded Search [5] and formatted search [6]
Server side include of other TWiki pages and web pages, selective with patterns if needed [7]. Useful also to create a large composed document with an automatic TOC, such as the TWiki reference manual [8]
RenderListPlugin [9] where the org chart of an organization is defined in one page, and then a subset of the org chart is shown in team home pages, focused around where the team is in the org chart
SpreadSheetPlugin [10] where complex calculations can be done on content pulled dynamically from elsewhere, and visualized with the ChartPlugin [11]

In addition, there are many more features supporting structured content, such as relational databases integration [12], keeping track of action items with global queries and email notifications [13], special Plugin to query forms [14], and more.

These features allow users with moderate skill sets to create web applications with various degrees of complexity.

TWiki supports structured content and web apps by slicedot · 2004-10-30 15:52 · Score: 1 · on Are we Headed for a Wiki World?

TWiki is a "structured Wiki" since its inception. In addition it is a platform to create web applications.

As with any Wiki, you get some structure with Category topics. For example, if you add a CategoryXml to any page that talks about XML, you can click on the CategoryXml link to find all other pages about XML.

TWiki has several other features which enable users to give structure to content. A TWikiForm[1] can be attached to a page. When you edit a page you get additional HTML widgets on the screen, like for example the "Subject" line and the "Post anonymously" checkbox here on /. A set of pages that share the same type of form is one type of structured content, it is analogous to a table in a relational database.

Giving structure to unstructured content is very important in a corporate environment. The more structure you have the easier it is to run reports and find content of interest by browsing and searching. TWiki has several other innovations supporting structured content:

Name spaces (called TWiki webs)
Parent/child relationship with bread crumbs [2]; done automatically in the background, with the ability to re-parent topics
Use TWiki Templates [3] to create a set of pages that share a common format
Powerful queries can be done with interactive search [4], embedded Search [5] and formatted search [6]
Server side include of other TWiki pages and web pages, selective with patterns if needed [7]. Useful also to create a large composed document with an automatic TOC, such as the TWiki reference manual [8]
RenderListPlugin [9] where the org chart of an organization is defined in one page, and then a subset of the org chart is shown in team home pages, focused around where the team is in the org chart
SpreadSheetPlugin [10] where complex calculations can be done on content pulled dynamically from elsewhere, and visualized with the ChartPlugin [11]

In addition, there are many more features supporting structured content, such as relational databases integration [12], keeping track of action items with global queries and email notifications [13], special Plugin to query forms [14], and more.

These features allow users with moderate skill sets to create web applications with various degrees of complexity.

TWiki supports structured content and web apps by slicedot · 2004-10-30 15:52 · Score: 1 · on Are we Headed for a Wiki World?

TWiki is a "structured Wiki" since its inception. In addition it is a platform to create web applications.

As with any Wiki, you get some structure with Category topics. For example, if you add a CategoryXml to any page that talks about XML, you can click on the CategoryXml link to find all other pages about XML.

TWiki has several other features which enable users to give structure to content. A TWikiForm[1] can be attached to a page. When you edit a page you get additional HTML widgets on the screen, like for example the "Subject" line and the "Post anonymously" checkbox here on /. A set of pages that share the same type of form is one type of structured content, it is analogous to a table in a relational database.

Giving structure to unstructured content is very important in a corporate environment. The more structure you have the easier it is to run reports and find content of interest by browsing and searching. TWiki has several other innovations supporting structured content:

Name spaces (called TWiki webs)
Parent/child relationship with bread crumbs [2]; done automatically in the background, with the ability to re-parent topics
Use TWiki Templates [3] to create a set of pages that share a common format
Powerful queries can be done with interactive search [4], embedded Search [5] and formatted search [6]
Server side include of other TWiki pages and web pages, selective with patterns if needed [7]. Useful also to create a large composed document with an automatic TOC, such as the TWiki reference manual [8]
RenderListPlugin [9] where the org chart of an organization is defined in one page, and then a subset of the org chart is shown in team home pages, focused around where the team is in the org chart
SpreadSheetPlugin [10] where complex calculations can be done on content pulled dynamically from elsewhere, and visualized with the ChartPlugin [11]

In addition, there are many more features supporting structured content, such as relational databases integration [12], keeping track of action items with global queries and email notifications [13], special Plugin to query forms [14], and more.

These features allow users with moderate skill sets to create web applications with various degrees of complexity.

TWiki supports structured content and web apps by slicedot · 2004-10-30 15:52 · Score: 1 · on Are we Headed for a Wiki World?

TWiki is a "structured Wiki" since its inception. In addition it is a platform to create web applications.

As with any Wiki, you get some structure with Category topics. For example, if you add a CategoryXml to any page that talks about XML, you can click on the CategoryXml link to find all other pages about XML.

TWiki has several other features which enable users to give structure to content. A TWikiForm[1] can be attached to a page. When you edit a page you get additional HTML widgets on the screen, like for example the "Subject" line and the "Post anonymously" checkbox here on /. A set of pages that share the same type of form is one type of structured content, it is analogous to a table in a relational database.

Giving structure to unstructured content is very important in a corporate environment. The more structure you have the easier it is to run reports and find content of interest by browsing and searching. TWiki has several other innovations supporting structured content:

Name spaces (called TWiki webs)
Parent/child relationship with bread crumbs [2]; done automatically in the background, with the ability to re-parent topics
Use TWiki Templates [3] to create a set of pages that share a common format
Powerful queries can be done with interactive search [4], embedded Search [5] and formatted search [6]
Server side include of other TWiki pages and web pages, selective with patterns if needed [7]. Useful also to create a large composed document with an automatic TOC, such as the TWiki reference manual [8]
RenderListPlugin [9] where the org chart of an organization is defined in one page, and then a subset of the org chart is shown in team home pages, focused around where the team is in the org chart
SpreadSheetPlugin [10] where complex calculations can be done on content pulled dynamically from elsewhere, and visualized with the ChartPlugin [11]

In addition, there are many more features supporting structured content, such as relational databases integration [12], keeping track of action items with global queries and email notifications [13], special Plugin to query forms [14], and more.

These features allow users with moderate skill sets to create web applications with various degrees of complexity.

TWiki supports structured content and web apps by slicedot · 2004-10-30 15:52 · Score: 1 · on Are we Headed for a Wiki World?

TWiki is a "structured Wiki" since its inception. In addition it is a platform to create web applications.

As with any Wiki, you get some structure with Category topics. For example, if you add a CategoryXml to any page that talks about XML, you can click on the CategoryXml link to find all other pages about XML.

TWiki has several other features which enable users to give structure to content. A TWikiForm[1] can be attached to a page. When you edit a page you get additional HTML widgets on the screen, like for example the "Subject" line and the "Post anonymously" checkbox here on /. A set of pages that share the same type of form is one type of structured content, it is analogous to a table in a relational database.

Giving structure to unstructured content is very important in a corporate environment. The more structure you have the easier it is to run reports and find content of interest by browsing and searching. TWiki has several other innovations supporting structured content:

Name spaces (called TWiki webs)
Parent/child relationship with bread crumbs [2]; done automatically in the background, with the ability to re-parent topics
Use TWiki Templates [3] to create a set of pages that share a common format
Powerful queries can be done with interactive search [4], embedded Search [5] and formatted search [6]
Server side include of other TWiki pages and web pages, selective with patterns if needed [7]. Useful also to create a large composed document with an automatic TOC, such as the TWiki reference manual [8]
RenderListPlugin [9] where the org chart of an organization is defined in one page, and then a subset of the org chart is shown in team home pages, focused around where the team is in the org chart
SpreadSheetPlugin [10] where complex calculations can be done on content pulled dynamically from elsewhere, and visualized with the ChartPlugin [11]

In addition, there are many more features supporting structured content, such as relational databases integration [12], keeping track of action items with global queries and email notifications [13], special Plugin to query forms [14], and more.

These features allow users with moderate skill sets to create web applications with various degrees of complexity.

TWiki supports structured content and web apps by slicedot · 2004-10-30 15:52 · Score: 1 · on Are we Headed for a Wiki World?

TWiki is a "structured Wiki" since its inception. In addition it is a platform to create web applications.

As with any Wiki, you get some structure with Category topics. For example, if you add a CategoryXml to any page that talks about XML, you can click on the CategoryXml link to find all other pages about XML.

TWiki has several other features which enable users to give structure to content. A TWikiForm[1] can be attached to a page. When you edit a page you get additional HTML widgets on the screen, like for example the "Subject" line and the "Post anonymously" checkbox here on /. A set of pages that share the same type of form is one type of structured content, it is analogous to a table in a relational database.

Giving structure to unstructured content is very important in a corporate environment. The more structure you have the easier it is to run reports and find content of interest by browsing and searching. TWiki has several other innovations supporting structured content:

Name spaces (called TWiki webs)
Parent/child relationship with bread crumbs [2]; done automatically in the background, with the ability to re-parent topics
Use TWiki Templates [3] to create a set of pages that share a common format
Powerful queries can be done with interactive search [4], embedded Search [5] and formatted search [6]
Server side include of other TWiki pages and web pages, selective with patterns if needed [7]. Useful also to create a large composed document with an automatic TOC, such as the TWiki reference manual [8]
RenderListPlugin [9] where the org chart of an organization is defined in one page, and then a subset of the org chart is shown in team home pages, focused around where the team is in the org chart
SpreadSheetPlugin [10] where complex calculations can be done on content pulled dynamically from elsewhere, and visualized with the ChartPlugin [11]

In addition, there are many more features supporting structured content, such as relational databases integration [12], keeping track of action items with global queries and email notifications [13], special Plugin to query forms [14], and more.

These features allow users with moderate skill sets to create web applications with various degrees of complexity.

TWiki on Windows without Cygwin by Cato · 2004-10-29 04:23 · Score: 1 · on Are we Headed for a Wiki World?

Cygwin is a recommended requirement of that cookbook only, not of TWiki itself. Also, the cookbook does point out where you may need to make changes in TWiki.cfg etc for use of ActiveState Perl, though it does assume Cygwin for ease of installation of ls, grep and some CPAN modules.

As long as you have working RCS, ls, grep, and so on, TWiki will be quite happy (and latest version eliminates need for ls). For an alternative approach, see the this mod_perl cookbook for TWiki on Windows, which only requires a few Cygwin files (ZIPped up on the same page) and also gives you great performance on Windows (where fork is more expensive so CGI typically performs badly).

There's a list of known configurations of TWiki on Windows, with quite a few non-Cygwin Perl ones. Personally I'm a Cygwin fan but I do like ActiveState Perl as it avoids some weird Cygwin Perl behaviour sometimes. There are even people who have installed TWiki on IIS and Microsoft's Services For Unix product...

Finally, the sample TWiki.cfg file includes detaile comments and sample paths to help people install on ActiveState Perl, and the testenv post-installation check tool diagnoses some issues with ActiveState installs and provides recommended setup changes if possible.

TWiki on Windows without Cygwin by Cato · 2004-10-29 04:23 · Score: 1 · on Are we Headed for a Wiki World?

Cygwin is a recommended requirement of that cookbook only, not of TWiki itself. Also, the cookbook does point out where you may need to make changes in TWiki.cfg etc for use of ActiveState Perl, though it does assume Cygwin for ease of installation of ls, grep and some CPAN modules.

As long as you have working RCS, ls, grep, and so on, TWiki will be quite happy (and latest version eliminates need for ls). For an alternative approach, see the this mod_perl cookbook for TWiki on Windows, which only requires a few Cygwin files (ZIPped up on the same page) and also gives you great performance on Windows (where fork is more expensive so CGI typically performs badly).

There's a list of known configurations of TWiki on Windows, with quite a few non-Cygwin Perl ones. Personally I'm a Cygwin fan but I do like ActiveState Perl as it avoids some weird Cygwin Perl behaviour sometimes. There are even people who have installed TWiki on IIS and Microsoft's Services For Unix product...

Finally, the sample TWiki.cfg file includes detaile comments and sample paths to help people install on ActiveState Perl, and the testenv post-installation check tool diagnoses some issues with ActiveState installs and provides recommended setup changes if possible.

Re:Microsoft shops crave MediaWiki power by Elwood+P+Dowd · 2004-10-29 03:53 · Score: 1 · on Are we Headed for a Wiki World?

If you don't want Cygwin, you can quite easily use ActiveState Perl, which some people prefer to Cygwin Perl on Windows.

Oh. Cool. Apache is no problem. Cygwin was the only hurdle I wasn't willing to jump. I hadn't read your whole cookbook, but it certainly does seem like it requires Cygwin, whether or not you use ActiveState Perl.

Re:Wikis with authentication? by Cato · 2004-10-29 02:46 · Score: 1 · on Are we Headed for a Wiki World?

TWiki does authentication - it can use .htpasswd but people have done plugins for LDAP and so on. The sections you refer to are done as 'Webs' within TWiki - different user groups or users can have different permissions per web or even per page. See TWiki.org.

Re:Because we're living, in a wiki world... by Cato · 2004-10-29 02:21 · Score: 1 · on Are we Headed for a Wiki World?

The traditional TWiki skin was quite ugly, it's true, but the new default skin, recently released, is really nice, with a modern CSS-based design that was created by a web design / usability specialist. See any TWiki.org page for an example.

TWiki's development is moving to a new model that is much more 'bazaar' than 'cathedral', which should also speed up development of the core. Plugins are already developed with great speed and there are over 100 of them.

I have a lot of respect for MediaWiki, given its nice UI and feature set, and am probably biased since I'm a TWiki developer, but I prefer a Perl-based Wiki for ease of hacking. TWiki is widely deployed for intranet Wikis that need security, attachments, and so on, as well as 'pure Wiki' features.

Editing Wikis using Emacs by Cato · 2004-10-29 02:10 · Score: 1 · on Are we Headed for a Wiki World?

Oops, should have previewed... see this TWiki page and this one on how best to edit pages in general.

Editing Wikis using Emacs by Cato · 2004-10-29 02:10 · Score: 1 · on Are we Headed for a Wiki World?

Oops, should have previewed... see this TWiki page and this one on how best to edit pages in general.

Re:Not ugly. by Black+Perl · 2004-10-28 13:11 · Score: 1 · on Are we Headed for a Wiki World?

Yes, it's nice. I also like the DragonSkin. You can see some of the skins here:
TWikiSkinBrowser

Another Wiki Implementation worth looking at... by bteeter · 2004-09-28 04:42 · Score: 2, Informative · on Microsoft Releases FlexWiki as Open Source

I've actively used TWiki (http://www.twiki.org/) for a while now and its pretty slick. Its a Perl Implementation and it has a built in versioning system, so it saves all of the revisions of the TWiki docs.

I definitely recommend it for anyone looking at running a Wiki. :-)

Take care,

Brian
--
Linux Web Hosting

A Wiki? by mikeboone · 2004-06-18 09:08 · Score: 1 · on Best To-Do List Software?

I use a wiki to keep track of my to-do list. I document all of my projects on separate wiki pages.

I currently use Twiki, which is sort of a pain to set up, but has a lot of features. One plugin for it is called the Action Tracker, and it can be used to auto-generate a single to-do list from the action items on various wiki pages.

Sometimes I get lazy about the action lists, and a simple wiki page with a text to-do list works fine.

A Wiki? by mikeboone · 2004-06-18 09:08 · Score: 1 · on Best To-Do List Software?

I use a wiki to keep track of my to-do list. I document all of my projects on separate wiki pages.

I currently use Twiki, which is sort of a pain to set up, but has a lot of features. One plugin for it is called the Action Tracker, and it can be used to auto-generate a single to-do list from the action items on various wiki pages.

Sometimes I get lazy about the action lists, and a simple wiki page with a text to-do list works fine.

Re:Wiki by truffle · 2004-06-18 09:06 · Score: 2, Informative · on Best To-Do List Software?

Excellent recommendation, a great wiki for this purpose is
TWiki. Makes for a great Web accessible todo list.

The interface may not be as fast as dedicated todo list software, but it has the benefits of being good for taking notes, colaborative document editing, file upload, definable users lists for reading and editing documents.

"blog" buzzword for "Wiki" by Anonymous Coward · 2004-05-31 04:47 · Score: 0, Insightful · on On Collaborative Weblogs

"wiki" is the term i prefer over "blog" which is just a buzz word for a wiki that is focused upon a specific application (logging or journals)

but since the underlying concept is that of "group colaboration" regardless if it is being used to log daily events or to track issues on a group project and allow people to come together in new ways. Wiki's are the only way to go.

TWiki being among the greatest examples.

All you need by Anonymous Coward · 2004-05-17 11:44 · Score: 0 · on Welcome to the 'Plogging' World

is a wiki.

Re:Workplace Wikis are useful by irontiki · 2004-05-17 09:42 · Score: 1 · on Welcome to the 'Plogging' World

Ditto on TWiki here. Built in search, built in revision control. TWiki rocks!

We have the bugzilla plugin so we can trivially link to bugs, we track status with the discussion form plugin, we throw in links to code via our cvsweb and simply use the shit out of it. We've been using it for 5 months and would be crippled without it.

Workplace Wikis are useful by mikemacd · 2004-05-17 05:11 · Score: 5, Interesting · on Welcome to the 'Plogging' World

I've found that WIKIs can be useful as a collaboration tool in the workplace.

It can be a free form tool to coordinate various teams and projects. Its important to bear in mind though that even the best tool is no replacement for good management.

The WIKI I'm currently using is TWIKI which is GPL'd.

Help us to improve MediaWiki by Eloquence · 2004-04-12 00:56 · Score: 5, Informative · on The Importance of Collaborative Development

MediaWiki is the open source software running Wikipedia, Wikibooks, Disinfopedia, the MozillaZine Knowledgebase, and many other wikis. Eugene is correct in noting that we need to work together in improving our collaborative tools. Wiki technology is one of them. Use it for your open source software documentation. Add a link to your documentation wiki to the software's "Help" menu, so that your users are encouraged to fill the gaps.

MediaWiki in particular implements many ideas that were already envisioned by Ted Nelson and Doug Engelbart. It does show backlinks, but perhaps more importantly, it also allows dynamic inclusion of any page in the current development version. For example, you could have a header and footer in your documentation that is the same for every page. What's more, you can add parameters to these templates to dynamically search and replace patterns of text in the template before transcluding it. This will allow us to replace the currently statically hacked Wikipedia infoboxes with dynamically included and parametrized templates, for example. One long term feature that might be worth hacking on top of this would be transclusion of labeled sections from another page, or interwiki transclusion.

Check out the current feature list and the development roadmap. Subscribe to wikitech-l to help us in improving the software. In true wiki spirit, we are fairly liberal at handing out CVS access (over 40 developers with CVS access at present), so please do ask if you want to work on a larger project.

There are many other wiki engines that are worth working on, such as TWiki and MoinMoin. Their main deficiency, in my opinion, is that they do rely primarily on the traditional wiki link pattern of CamelCase, which is nice for geeks but very ugly for everyone else, and also useless for search engines. MediaWiki uses [[free links]] instead, which are harder to type, but look just like normal links to the reader. Still, working on any other wiki engine is a lot better than starting yet another one.

A collaborative tool which is badly needed is a free software clone of SubEthaEdit. Combine wikis with real-time editing and the fun really begins. I imagine something like that might be hackable on top of a powerful graphical editor like Kate. For now WebDAV-support for MediaWiki would also be very cool, as Kate/KDE already supports editing WebDAV resources. So many worthwhile hacks, so little time.

This is an area where open source coders can make a big difference while corporations are still bewildered by the fact that open wikis can produce useful content. So please, let's work together on these tools.

Review page of Windows outliners by Grabble · 2004-02-16 18:53 · Score: 2, Interesting · on Idea Management/Navigation Software?

Some people think The One True Way is to use outliners. (shrug) It depends on your work style.

This really useful page...

http://john.redmood.com/organizers.html

... lists a bunch of Windows outliners, along with personal opinion on usage and features.

I have been in your exact shoes and have installed Twiki and have the following generalization...

Wiki's aren't as easy to use as they seem. When using a wiki, there's actually a very distinct (but non-obvious) obstacle course between the urge to write and the actual start of writing and it negatively impacts your productivity more than you realize.

... but that's just a generalization from my own experience. I'm still a believer, but not a user.

"Someday, I'll fix it."

Extra comments: Jot + serves me well as a catch-all sort of scratchpad... I'm only an Alt-Tab away from writing, and I also like its indentation model.

The folks behind The Brain are patent fuckwads... they actually patented the idea of using lines to connect thoughts. Avoid them.

Re:Why not use PKI authentication instead? by ka9dgx · 2004-02-06 05:39 · Score: 2, Informative · on Would you Warranty Your Email?

PGP is a type of Public Key Infrastructure... SSL keys aren't the only game in town. The only difference between the whole "Root CA" and PGP is that the "Root CA" list gets distributed with most SSL implementations, with PGP, you make your own lists.

Technically, anyone can make themselves a root CA, just like anyone can set up their own DNS root. It's a simple matter of consensus, the roots are as valid as the users believe the are.

--Mike--

Why not a Wiki? by ThenAgain · 2004-01-19 10:14 · Score: 4, Insightful · on Best Web Forums for Businesses?

I've had success with Wikis in organizing office proceedures, documentation, logs, etc. They take just a little more lernin' than a simple "post your message here" arrangement, but they reward you with the ability to create flexible and extensible structures quickly. I use TWiki because it has a flexible calendar plugin. There are several open-source Wiki's available.

Most modern Wiki software (TWiki included) has revision control so no matter what they do they can't break it. The hard part is getting the luddites to adopt it. If that gets tough you can set up a sensible structure yourself and use TWiki's comment plugin to make it easy on them.