[pmwiki-users] pmwiki wordpress
hi there i've never used wordpress before, but am hearing about it constantly, and was wondering if anyone on this list uses both pmwiki and wordpress and could explain some of the differences. i know wordpress isn't a wiki, but it appears to have a level of customization that makes it very attractive. i'm interested to know what the advantages disadvantages of each might be in terms of developing flexible sites for folks, and if there are those out there who use wordpress for certain situations, and pmwiki for others. any suggestions? how are they different? thanks a bunch! adam ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] pmwiki wordpress
On 5/22/2010 4:25 AM, adam overton wrote: hi there i've never used wordpress before, but am hearing about it constantly, and was wondering if anyone on this list uses both pmwiki and wordpress and could explain some of the differences. i know wordpress isn't a wiki, but it appears to have a level of customization that makes it very attractive. i'm interested to know what the advantages disadvantages of each might be in terms of developing flexible sites for folks, and if there are those out there who use wordpress for certain situations, and pmwiki for others. any suggestions? how are they different? Easiest way is probably to try it. You can setup a free account on wordpress.org Fundamentally Wordpress is *primarily* a blogging platform, but can be stretched into other areas. PmWiki *can* be used as a blogging platform, but that is not the primary focus; it's designed to be a flexible web-platform that can accommodate a huge range of web-site styles. Personally I view this in two ways: in terms of the use to which the site will be applied (the website style); and in terms of the skills/experience of the primary user (not the reader). *Web Site Styles*: WP is very good for your average person to get their thoughts onto the web. It's great for being able to blog. PmWiki simply does not have this built-in -- it can be added, but even then it's not quite as robust. But PmWiki excels in other areas, where it's more akin to the capabilities of Drupal or Joomla. Again, PmWiki *can* do blogging, but it's not the primary focus; it's designed to be a flexible web-platform that can accommodate a huge range of web-site styles, with aprimary focus on open and collaborative editing. Wordpress is *primarily* a blogging platform, but can be stretched into other areas if needed, but does not have a robust wiki editing mechanism. *User*: There are very large conceptual hurdles to over-come with PmWiki. I'll give some examples, but this is the primary reason I don't recommend PmWiki in all cases, and tend to guide certain groups of usually not-so-computer-literate people to Wordpress. ] PmWiki markup is simply too obscure for non-computer users -- seeing the markup in the editor is not what people expect today. They expect to be able to edit largely what will be displayed. Worpress isn't wysisyg, but it's close enough. ] Managing attachments is considerably easier in WP; *but* it's not perfect, and it's the area I usually end up having to explain a few times. PmWik is simply too obscure. ] Look and feel for site-administrators in WP is way better than even the best skins on PmWiki. This sounds like a poor reason, but for a large portion of non-computer literate users, this tends to be a significant factor. ~ ~ Dave ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] pmwiki wordpress
Hello, All in all, I agree with Dave's answer. There are many studies comparing blogs to wikis. Without delving into details, I think the first question one should ask is this one: - Do I want to organize my content by time or by a conceptual framework? Blogs are mainly organized by the linear time order. Wikis are mainly organized by concepts. Answering that question should help you decide what to look for first. That does not mean that you can't do conceptual blogs or time-framed wikis. You can do anything, actually. But some work is just a bit more complicated than others. Another good question is : - How much time do you want to invest? I hope everybody should agree that Pmwiki needs more time, at least at first. If you want only to be a poweruser and if you don't mind organizing your stuff by date, go with Wordpress. But if you prefer to organize stuff by concepts, go to the adventure with a more lightweighted tool (i.e. flat files), give PmWiki a try, you won't regret it. Hope this helps, Ben ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] pmwiki wordpress
On 2010-05-22 4:25 AM, adam overton wrote: hi there i've never used wordpress before, but am hearing about it constantly, and was wondering if anyone on this list uses both pmwiki and wordpress and could explain some of the differences. i know wordpress isn't a wiki, but it appears to have a level of customization that makes it very attractive. i'm interested to know what the advantages disadvantages of each might be in terms of developing flexible sites for folks, and if there are those out there who use wordpress for certain situations, and pmwiki for others. any suggestions? how are they different? thanks a bunch! adam Hi Adam I use WordPress, PmWiki, and Simple Machines Forum (SMF). Each has its own advantages. PmWiki is great for building a site by consensus - where several authors can edit all the pages. Well managed wikis improve over time. WordPress is ideal for daily journal or reportage sites. I think of it as a newspaper with archives. Readers can leave comments, but they don;t alter the original articles. SMF is a message board system. Message boards are ideal for support tracking or followong the twists and turns of a discussion. they do not lend themselves to building a consensus of opinion - quite the opposite if it is infested with trolls. You could use PwWiki for all of these tasks, but WP and SMF provide working systems out of the box. If you would like to see some examples ... My personal PmWiki site (I have many that are not public) http://neil.eton.ca/wiki/index.php/Main/HomePage A PmWiki site used as a CMS http://www.mugoo.com/wiki/index.php A message board used by the same organization http://www.mugoo.com/smf/ My personal WordPress blog http://neil.eton.ca/blog/ -- Neil Herber ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
[pmwiki-users] How to distinguish between a wildcard and a reference in exists
PmWiki version 2.2.16 changed the markup to allow conditional exists to use
wildcards. But now how do I reference the underlying page, as opposed to
specifying a wildcard?
For example, put the following markup in WikiSandbox and also in any page that
does not yet exist (using preview to see the result). The results used to be
Main.WikiSandbox exists and Main.UnsavedPage doesn't exist, but now both
return doesn't exist.
(:markup:)
(:if !exists {*$FullName}:)
{*$FullName} doesn't exist
(:else:)
{*$FullName} exists
(:ifend:)
(:markupend:)
-- Randy___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] How to distinguish between a wildcard and a reference in exists
On 5/22/2010 5:25 PM, Randy Brown wrote:
PmWiki version 2.2.16 changed the markup to allow conditional exists
to use wildcards. But now how do I reference the underlying page, as
opposed to specifying a wildcard?
For example, put the following markup in WikiSandbox and also in any
page that does not yet exist (using preview to see the result). The
results used to be Main.WikiSandbox exists and Main.UnsavedPage
doesn't exist, but now both return doesn't exist.
(:markup:) (:if !exists {*$FullName}:) {*$FullName} doesn't exist
(:else:) {*$FullName} exists (:ifend:) (:markupend:) -- Randy
Try without the quotes, and the condition works as expected. No idea
if/how this might have changed, just highlighting a way to make it work.
(:markup:) (:if !exists {*$FullName}:) {*$FullName} doesn't exist
(:else:) {*$FullName} exists (:ifend:) (:markupend:)
~ ~ Dave
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] How to distinguish between a wildcard and a reference in exists
Thanks, Dave - that worked.
Randy
On May 22, 2010, at 4:41 PM, DaveG wrote:
Try without the quotes, and the condition works as expected. No idea if/how
this might have changed, just highlighting a way to make it work.
(:markup:) (:if !exists {*$FullName}:) {*$FullName} doesn't exist (:else:)
{*$FullName} exists (:ifend:) (:markupend:)
~ ~ Dave
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] RecipeCheck question
On Friday 21 May 2010 18:20:31, Ingersoll, Nelson wrote : However, two recipes show no datestamp on PmWiki.org. They are Cookbook:ZAP and Cookbook:CommentBoxPlus. I picked up these recipes on PmWiki.org and am wondering what the lack of a pmwiki.prg datestamp means. Are the recipes deprecated or unsupported? Hello. The CommentBoxPlus recipe has a timestamp, I see 2007-12-21, and Hans is an active developer, so I assume the recipe is still supported. The ZAP page has no Version: line which is why there is no timestamp. The author of that page removed himself from the Maintainer: field and is no longer participating actively in the community, so probably the recipe is no longer supported: http://article.gmane.org/gmane.comp.web.wiki.pmwiki.user/45481 If you have a doubt, you can always compare the Cookbook recipe page and the uploaded file with your own file, to see if there are newer or different versions. Thanks, Petko ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
