Re: [pmwiki-users] i18n updates

[SteP]

Patrick R. Michaud wrote:

> Okay, I've updated and rebuild the i18n distribution files.
> Each language now has its own independent i18n-xx.zip file,
> built from the pages on pmwiki.org.  In addition, there's
> an 'i18n-all.zip' file that contains the complete archive
> with all of the languages.

Thank you, Patrick!
I noticed that the main download page prominently says

International language packs (August 7, 2006)

This is misleading, as each individual language zip file is updated 
independently, and certainly some of the zips in the current i18n.zip file 
are more recent than August 7, 2006. Maybe you could add a list of all the 
i18n-xx.zip files on the main download page?


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] ZAPbeta 2007-03 complete!

[SteP]

The Editor wrote:

> ZAPmath (which
> can evaluate basic arithmetic inputs), 

My question isn't specifically tied to ZAPmath although it occurred to me 
while looking at the Math snippet on the ZAP site. I noticed that several 
snippets now use PTV variables and zap savedata + passdata commands. I'm 
wondering what happens when there are multiple users submitting the same 
page, since each one could potentially overwrite each other's PTV in the 
page. Does ZAP treat all zap commands in a page as a whole execution unit 
and locks the page while this happens?


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] ZAPbeta 2007-03 complete!

[SteP]

Hi Dan, congratulations on this new beta.

The Editor wrote:

> * Added a ZAPlink markup to create ZAP forms that submit when clicking
> a link, and a ZAPsubmit markup which automatically submits a page as
> soon as the page loads (neither uses javascript). These allow some
> exciting possibilities for use of ZAP.

Very interesting, can you explain more?
Could I create a page that automatically submits an action when it's 
loaded? Could it automatically submit a sequence of actions? Or could 
autosubmit pages be linked into a chain that autosubmits each page in a 
sequence? Are the forms in the autosubmit page restricted to ZAP only 
forms or can (:input:) forms also be included? 

TIA
--SteP


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PmWiki forum...

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 04:45:09PM -0500, Patrick R. Michaud wrote:
> On Fri, Mar 16, 2007 at 04:50:10PM -0400, The Editor wrote:
> > I think at least for questions like these there should be a searchable
> > forum for people to ask questions and get answers. Most recent
> > questions posted at the top.  Each question on its own page, with
> > comments.  It would take 5 minutes to do it in ZAP or FOX.  Is there
> > some reason we don't have something like that?
> 
> ...because I've never been convinced that it will be a significant
> improvement over what we have now.  

I should also note that this was the original form and intent of the
Cookbook -- i.e., each page consisted of a "question" about how to
do something in PmWiki, followed by an answer resolving the question
(which often included a script or configuration information).

So, even when we were doing things that way, most people found the
mailing list more convenient.

All that said, I don't see any reason why we can't do this in
the Cookbook, especially for questions that don't fit naturally
in the PmWiki documentation.  Then we could easily generate a 
pagelist of all Cookbook recipes that answer questions (e.g., by
using a Question: page text variable or something like that).

We could also provide a form or template that makes it easy to create
new "questions" as pages in the cookbook.  Then when someone answers 
the question it automaticaly acts like a new recipe page.  (And it
might then be important to have a way to quickly locate question pages
that are lacking answers -- but that could be done with an [[!AnswerMe]]
category.)

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PmWiki forum...

[Aaron]

Neil Herber (nospam) wrote:

> A: Because forums are great for holding conversations, but lousy for 

And conversations can be very enlightening for all.

-- 
Aaron


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PmWiki skin question...

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 07:36:10PM -0400, The Editor wrote:
> On the PmWiki skin--what produces the part at the very top of each
> page that looks like this?
> 
> Site/
> PageName
> 
> I'd like to edit it.

It's in the pmwiki.tmpl file.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] PmWiki skin question...

[The Editor]

On the PmWiki skin--what produces the part at the very top of each
page that looks like this?

Site/
PageName

I'd like to edit it.

Cheers,
Dan

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] help with form using AddDeleteLine2

[Martin Fick]

It also looks like you don't have an append or prepend
entry on this page.  Since you don't have a target
listed here:

> (:adl form entry:)

it will look to add the text to the current page and
if the append/prepend tags are not there, it will do
nothing,

-Martin

--- April Barrett <[EMAIL PROTECTED]> wrote:

> !!!
> (:linebreaks:)
> (:input form method=post enctype=multipart/form-data
> :)
> (:input hidden name=n value={$FullName}:)
> (:input hidden name=action value=postupload:)
> File to upload:   (:input file name='uploadfile':)
> Name of upload: (:input text name='upname':)
> (IMPORTANT: if the file
> name is intel-logo.jpg, you must type in
> intel-logo.jpg in this field
> or the image will not show)
> (:adl form entry:)
> 
> (:table:)
> (:cellnr:)Company Profile:
> (:cell:)(:input textarea profile rows=10 cols=34:)
> (:cellnr:)Company URL:
> (:cell:)(:input text curl size=45:)
> (:cellnr:)Faculty Affiliation:
> (:cell:)(:input text faculty size=45:)
> (:cellnr:)Faculty Title:
> (:cell:)(:input text ftitle size=45:)
> (:cellnr:)Faculty URL:
> (:cell:)(:input text furl size=45:)
> (:cellnr:)Outcome:
> (:cell:)(:input text outcome size=45:)
> (:cellnr:)(:input submit ok Enter:)
> (:adl templatepage [[MultiLineTemplate]]:)
> (:adl end:)
> 
> 
> **
> 
> My form template string consists of more than one
> line, so I am
> specifying the template in a seperate wiki-page
> called
> (MultiLineTemplate:
> 
> !!!
> (:table border=0 cellspacing=0 cellpadding=15:)
> (:cellnr width=33% align=left:)
> [[{curl} | Attach:{upname}]]
> 
> {profile}
> 
> [[{curl} | {curl}]]
> 
> (:cell width=33% align=left:)
> [[{furl} | {faculty}]], {ftitle}
> 
> (:cell width=33% align=left:)
> {outcome}
> (:tableend:)
> 
> 
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
>
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
> 



 

Food fight? Enjoy some healthy debate 
in the Yahoo! Answers Food & Drink Q&A.
http://answers.yahoo.com/dir/?link=list&sid=396545367

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] help with form using AddDeleteLine2

[April Barrett]

Hi Martin,

  Thank you.  I left out the question initially - I apologize.

I am trying to get the form to work using the template page.  It used
to a few months ago and after revisiting, I discovered this problem.

I tried your solution to no avail.

Any other ideas?

Thanks much.

On 3/16/07, Martin Fick <[EMAIL PROTECTED]> wrote:
> I must have missed the question on this post, but I do
> see something suspicious:
>
> --- April Barrett <[EMAIL PROTECTED]> wrote:
> > (:adl templatepage [[MultiLineTemplate]]:)
>
>
> should probably be:
>
> (:adl templatepage MultiLineTemplate:)
>
> or even be prefixed by a group if not in the same
> group,
>
> -Martin
>
>
>
>
> 
> Sucker-punch spam with award-winning protection.
> Try the free Yahoo! Mail Beta.
> http://advision.webevents.yahoo.com/mailbeta/features_spam.html
>

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] help with form using AddDeleteLine2

[Martin Fick]

I must have missed the question on this post, but I do
see something suspicious:

--- April Barrett <[EMAIL PROTECTED]> wrote:
> (:adl templatepage [[MultiLineTemplate]]:)


should probably be:

(:adl templatepage MultiLineTemplate:)

or even be prefixed by a group if not in the same
group,

-Martin



 

Sucker-punch spam with award-winning protection. 
Try the free Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/features_spam.html

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PmWiki forum...

[Neil Herber (nospam)]

On 2007-03-16 Patrick R. Michaud is rumoured to have said:
> And personally, I've never found a forum that actually made it 
> significantly easier to find answers to my questions than mailing 
> list archives do.

Ditto.

I find that forums are great for "conversations" but lousy for 
conclusions. The best tool I have found for collaborative technical 
documentation is a wiki.

The existing FAQ and Questions pages may be less than they could be, but 
I think that just shows how effective this mailing list is. People ask a 
question, get an answer, go away happy. Very few think to add their 
problem and solution to the FAQ, probably because they have no way to 
guage how frequently the question has been asked. And maybe because once 
  your problem is solved, you have less motivation to talk about it.

Instead of or in addition to the FAQ, there should be an AQ (answered 
questions) page or group. You are only allowed to post questions with 
answers, such as:

Q: Why don't we use a forum instead of this stupid "AQ" page.
A: Because forums are great for holding conversations, but lousy for 
reaching conclusions. At least here someone can edit my inane comment, 
sparing future readers the agony of reading it.

In the spirit of practicing what I preach, I have started this page:

http://www.pmwiki.org/wiki/PmWiki/AQ


-- 
Neil Herber
Corporate info at http://www.eton.ca/

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] help with form using AddDeleteLine2

[April Barrett]

!!!
(:linebreaks:)
(:input form method=post enctype=multipart/form-data :)
(:input hidden name=n value={$FullName}:)
(:input hidden name=action value=postupload:)
File to upload:   (:input file name='uploadfile':)
Name of upload: (:input text name='upname':) (IMPORTANT: if the file
name is intel-logo.jpg, you must type in intel-logo.jpg in this field
or the image will not show)
(:adl form entry:)

(:table:)
(:cellnr:)Company Profile:
(:cell:)(:input textarea profile rows=10 cols=34:)
(:cellnr:)Company URL:
(:cell:)(:input text curl size=45:)
(:cellnr:)Faculty Affiliation:
(:cell:)(:input text faculty size=45:)
(:cellnr:)Faculty Title:
(:cell:)(:input text ftitle size=45:)
(:cellnr:)Faculty URL:
(:cell:)(:input text furl size=45:)
(:cellnr:)Outcome:
(:cell:)(:input text outcome size=45:)
(:cellnr:)(:input submit ok Enter:)
(:adl templatepage [[MultiLineTemplate]]:)
(:adl end:)


**

My form template string consists of more than one line, so I am
specifying the template in a seperate wiki-page called
(MultiLineTemplate:

!!!
(:table border=0 cellspacing=0 cellpadding=15:)
(:cellnr width=33% align=left:)
[[{curl} | Attach:{upname}]]

{profile}

[[{curl} | {curl}]]

(:cell width=33% align=left:)
[[{furl} | {faculty}]], {ftitle}

(:cell width=33% align=left:)
{outcome}
(:tableend:)


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] 2.2.0-beta36 release (pagelist template updates)

[Roman]

Aaaah, thank you! I was looking what am I doing wrong. Also, there
should be {=$FullName} instead of $FullName.

Another catch - it does not seem to work when template is defined in
the same page as pagelist.

Roman

On 3/16/07, Jon Haupt <[EMAIL PROTECTED]> wrote:
> On 3/16/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> > In addition, a template may specify default options to be used
> > in the pagelist command.  For example, a pagelist template to
> > display a list of pages by their titles (and sorted by title)
> > might use:
> >
> > [[#bytitle]]
> > (:template default order=title:)
> > * [[$FullName|+]]
> > [[#bytitleend]]
> >
>
> Stumped by this in testing, I looked at the archives, and it looks as
> if there is a letter missing here and the corrected line should read
> (:template defaults order=title:)
>
> Jon Haupt
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] 2.2.0-beta36 release (pagelist template updates)

[Jon Haupt]

On 3/16/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> In addition, a template may specify default options to be used
> in the pagelist command.  For example, a pagelist template to
> display a list of pages by their titles (and sorted by title)
> might use:
>
> [[#bytitle]]
> (:template default order=title:)
> * [[$FullName|+]]
> [[#bytitleend]]
>

Stumped by this in testing, I looked at the archives, and it looks as
if there is a letter missing here and the corrected line should read
(:template defaults order=title:)

Jon Haupt

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PmWiki forum...

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 04:50:10PM -0400, The Editor wrote:
> I'm looking at the PmWiki site, at pages like
> http://www.pmwiki.org/wiki/PmWiki/Questions and
> http://www.pmwiki.org/wiki/PmWiki/FAQ and I have to say this is a
> terrible way to do things.  Almost an embarassment, considering how
> superb the software is.
> 
> I think at least for questions like these there should be a searchable
> forum for people to ask questions and get answers. Most recent
> questions posted at the top.  Each question on its own page, with
> comments.  It would take 5 minutes to do it in ZAP or FOX.  Is there
> some reason we don't have something like that?

...because I've never been convinced that it will be a significant
improvement over what we have now.  Unless you're advocating that
we eliminate the mailing list, I think a forum would just add
yet another place to have to keep up to date (and where things
would go out of date).

Personally, I'd be in favor of removing the PmWiki/Questions page,
simply because it's not a place that is checked often for answering 
questions.  Which really gets back to your original question ("why 
don't we use a forum") -- like the PmWiki.Questions page, forums 
don't work for me because they require that I constantly check 
the site for new questions.  Electronic mail works much better 
because it gives me a convenient way to respond.  I fear a forum
will end up being much the same as PmWiki.Questions -- questions
will get posted, but not enough people will be actively monitoring 
them for them to get answered.

And personally, I've never found a forum that actually made it 
significantly easier to find answers to my questions than mailing 
list archives do.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] DataQuery 0.4 beta released

[Ben Stallings]

Hi, folks.  I've made some encouraging progress with DataPlates this 
week and anticipate finishing it before the end of the month (woo hoo!).

In the process I've made some fairly radical changes to DataQuery, to 
accommodate its future partner, and hadn't planned on releasing a new 
version until DataPlates was ready.  However, a few brave beta testers 
have been using DataQuery and found some bugs that needed fixing.

So I've just released version 0.4 beta of DataQuery and updated the demo 
site at http://workscited.net/dataquery to reflect the changes.  There 
are some changes (improvements!) to the way queries are configured, so 
if you've been using DataQuery you will want to reread the "Configure a 
Query" page on the demo site.

Thanks, beta testers!  Be sure to let me know if you find any more bugs! 
  --Ben S.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] PmWiki forum...

[The Editor]

I'm looking at the PmWiki site, at pages like
http://www.pmwiki.org/wiki/PmWiki/Questions and
http://www.pmwiki.org/wiki/PmWiki/FAQ and I have to say this is a
terrible way to do things.  Almost an embarassment, considering how
superb the software is.

I think at least for questions like these there should be a searchable
forum for people to ask questions and get answers. Most recent
questions posted at the top.  Each question on its own page, with
comments.  It would take 5 minutes to do it in ZAP or FOX.  Is there
some reason we don't have something like that?

If there was an interest I'd be willing to set one up but thought I'd
find out why we don't have one first.  Several have complained of
PmWiki maillist overload.  Forums really seem a must to me--as I will
probably be less active in the maillist now that ZAP has finally
achieved about all the goals I had for it, and I need to get busy
using it now on my own site!  6 months later...

Anyway, a forum?

Cheers,
Dan

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] i18n updates

[Patrick R. Michaud]

Okay, I've updated and rebuild the i18n distribution files.
Each language now has its own independent i18n-xx.zip file,
built from the pages on pmwiki.org.  In addition, there's
an 'i18n-all.zip' file that contains the complete archive
with all of the languages.

The language distribution files are available from
http://www.pmwiki.org/pub/pmwiki/i18n/ .

I'm sure that some of the language pages need cleaning up...
simply let me know when it's time to update the i18n files.
(I'll eventually farm this task out to individual maintainers
as we identify them.)

Also, if there are pages in the per-language groups that
need to be auto-restored (similar to the way Main.WikiSandbox
is auto-resotred on pmwiki.org), let me know which ones and
I'll set them up for auto-restoration.  This will help keep
sandbox stuff from appearing in the distributed i18n files.

Comments and suggestions welcomed as always.

(I'm still working on the utf-8 updates for searches.)

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] RSS URLS Construct

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 09:33:46AM -1000, Sivakatirswami wrote:
> Patrick R. Michaud wrote:
> I have in /pmwiki/local/farmconfig.php
> 
> the following:
> 
> ###  Enable Feeds
> if ($action == 'rss') include_once('scripts/feeds.php');
> if ($action == 'atom') include_once('scripts/feeds.php');
> if ($action == 'rdf') include_once('scripts/feeds.php');
> if ($action == 'dc') include_once('scripts/feeds.php');
> 
> What am I missing?

You might need these to be "$FarmD/scripts/feeds.php"

  if ($action == 'rss' || $action == 'atom' || $action == 'rdf' || $action == 
'dc')
include_once("$FarmD/scripts/feeds.php");

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] ZAPbeta 2007-03 complete!

[The Editor]

Announcing the release of a new version of ZAP that I think many will
find quite worth looking into. Though a long list--please take a
minute to look through the list of new features. Many are quite
powerful!  At the same time, the code is significantly shorter and
simpler. And creating custom ZAP extensions has never been easier!

I've also completely updated the ZAP website (www.zapsite.org), adding
many new tutorials, extensive explanations on every command in ZAP,
and a developers section clarifying the underlying functions used in
ZAP.  A good many little inconveniences have been fixed and it seems
to be working beautifully.  I'm calling it a beta version for a week
or two just in case there are some bugs that need to be fixed...

Feedback, suggestions, and questions welcome...

Cheers,
Dan

PS. Existing member accounts have not yet been imported--as I need to
write up a converter script. In the mean time, feel free to create a
new member account. To cut down on spam, you must register before
posting comments.


__

ZAPbeta 2007-03

* Reorganized modules so all bonus markups are together, bonus
conditionals are together, and extensions are together.

* Reworked ZAPmail so email, emaillist, and emailnews are all in one
function--and thus each has full access to ZAP's mail templating, and
either scheduling or automatic sending.

* Passwords are now automatically encrypted by the register function,
and stored with Emails in a separate Login group (which should be read
protected). Other registration information is stored in group
Profiles. Unencrypted passwords, and passwords in ZAP's hidden format
(existing sites), will continue to work.

* New Site.ZAPConfig system which allows you to easily set default
values for default ZAP folders. Also, ZAPextension commands can be
easily limited to specific pages, groups, or group* patterns on this
page.

* Added several new command extensions, including ZAPphp (which can
securely execute a configurable array of php commands), ZAPmath (which
can evaluate basic arithmetic inputs), and ZAPgrade (a simple but
powerful quiz/course grade calculation function).

* Fixed the Upload function so it works as expected now. Very nice!

* A new system has been implemented for calling ZAP extensions making
it much easier to create ZAPX commands. It also plugs a security hole,
as ZAP no longer uses eval() to do this.

* Much work has been done under the hood to replace the highly
formatted ZAP data values with a much simple pattern replacement
system (cut out well over 100 lines!). This allows you to use ZAP to
replace any hidden text variable on any page, and makes the data
section of your pages much cleaner.

* Updatedata was removed, as savedata works now more intuitively, only
overwriting specified fields, and leaving all other data values
untouched. Erasedata was added to remove data fields where needed.

* Removed the destroy function, though delete continues to work as normal.

* Added new date and substring ZAP markups. The first returns proper
weekdays and months from numbers. The second is a very flexible way to
strip off prefixes, suffixes, or whatever from strings. Great for use
in Hg, or similar applications.

* Changed the format for if and validate so either can take a CSV list
of commands to execute when the condition passes, and another list of
commands to execute when the condition fails--all in one ZAP input
form. Much more intuitive syntax using ? and :

* Caching problem was solved so changed data values on pages are
automatically refreshed on save.

* Added a ZAPlink markup to create ZAP forms that submit when clicking
a link, and a ZAPsubmit markup which automatically submits a page as
soon as the page loads (neither uses javascript). These allow some
exciting possibilities for use of ZAP.

* Changed name parameter to key (more meaningful semantically) in the
ZAPform and ZAPlink markups.

* Numerous small fixes and improvements. Forms now not broken by
single/double quotes around the Form name (key). Upload can be entered
into the ZAPform markup as a single word. Page Shortcuts automatically
calls MakePageName to avoid invalid page names, etc.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] RSS URLS Construct

[Sivakatirswami]

Patrick R. Michaud wrote:
> PmWiki doesn't provide a feed for changes to a single page (other
> than perhaps to note when that page has changed).  If you just
> want to know when a specific page changes, then:
> 
> http://wiki.hindu.org/seva/index.php?action=rss&name=WebContent-Art.HomePage

>for a group:
> 
> http://wiki.hindu.org/seva/index.php/HTDE/RecentChanges?action=rss

>> for "Cluster"
> 
> http://wiki.hindu.org/seva/index.php?action=rss&group=HDTE,HDTE-*&order=-mtime
> 
Hmmm
In Firefox any of the above URL's entered into Sage
new feed book mark location results in:

Error: XML Parse error

And Thunderbird returns a similar error.

I have in

/pmwiki
/local
   /farmconfig.php

the following:

###  Enable Feeds
if ($action == 'rss') include_once('scripts/feeds.php');
if ($action == 'atom') include_once('scripts/feeds.php');
if ($action == 'rdf') include_once('scripts/feeds.php');
if ($action == 'dc') include_once('scripts/feeds.php');

What am I missing?

Skts




___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Conditionals not working correctly since beta32

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 01:09:52PM -0500, Patrick R. Michaud wrote:
> On Fri, Mar 16, 2007 at 07:05:35PM +0100, Han Baas wrote:
> > Hi,
> > 
> > Since beta32 conditionals are no longer working correctly. The  
> > negated form is no longer working.
> > 
> > I have some mark-up like this:
> > (:if ! name Page1, Page2, Page3:)
> 
> Because spaces are no longer counted as wildcard/name separators,
> this probably needs to be:
> 
>(:if ! name Page1,Page2,Page3 :)
> 
> OTOH, it's pretty unlikely that an author will understand that
> the spaces aren't permitted here, so perhaps I need to set the
> 'name' and 'group' conditionals to strip spaces.

I went a step further -- as of beta37 (just released), a comma
separator in a wildcard pattern may be followed by an optional
space, so that the original

(:if ! name Page1, Page2, Page3:)

now works again.

Thanks!

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Update to LiteralWhiteSpace recipe

[Hans]

An update of whitespace.php is available from
http://www.pmwiki.org/wiki/Cookbook/LiteralWhiteSpace

The recipe script now supports the (:nolinebreaks:) and (:linebreaks:)
markup directives.

I also changed the default white space replacement character to
 , which gives superior results from  , because it will
allow breaks for line wrapping.

IE is supported with using   instead.

I used a very simple User Agent browser check, I hope that non-IE
browsers will not be filtered out as IE.

Please give me feedback if there are problems,
and comments as usual.

-- 
Best regards,
 Hans


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Hispano-parlantes

[Pablo Manuel Rizzo]

Con fecha 16/3/2007, "Patrick R. Michaud" <[EMAIL PROTECTED]> escribió:
>
>Actually, I decided that we already have enough interest.  :-)
>
>So, the pmwiki-users-es mailing list is now available at
>
>http://www.pmichaud.com/mailman/listinfo/pmwiki-users-es
>
>
>Feel free to subscribe.  As soon as the Gmane wizards do their
>magic, messages to the pmwiki-users-es list should start appearing
>on Gmane as well.
>
>Thanks!
>
>P

LOL   :-D

Ok, I just subscribed to the new list. You can see the plan for the
course here:

http://pmwiki.conmutador.net/index.php/CursoPmWiki/Programa

If somebody is interested in traducing it feel free to create a new
translation page in that wiki.

Thanks!


--
Pablo Manuel Rizzo
--
Aunque supiera que el mundo se acabará mañana,
Igual plantaría mi manzano.   -- Martin Luther King --
--

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Hispano-parlantes

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 02:46:29PM -0300, Pablo Manuel Rizzo wrote:
> Con fecha 16/3/2007, "Patrick R. Michaud" <[EMAIL PROTECTED]> escribió:
> >If there's enough interest, I'll be happy to create a pmwiki-users-es
> >list (we already have pmwiki-users-de).
> 
> Ok, lets see how many people is interested.

Actually, I decided that we already have enough interest.  :-)

So, the pmwiki-users-es mailing list is now available at

http://www.pmichaud.com/mailman/listinfo/pmwiki-users-es


Feel free to subscribe.  As soon as the Gmane wizards do their
magic, messages to the pmwiki-users-es list should start appearing
on Gmane as well.

Thanks!

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] History Protect and Merge/Expire

[Vince Administration]

Dear PmWiki Users,
Would it be possible to have the user editing a page multiple times  
to compress his history entries. What I would like to be able to do  
is something
like the ExpireDiff recipe, but only the entries back as far as the  
current authors go, i.e, to stop whenever a different author is  
encountered. All
our users must login, so they are known.

Thanks for your help.
Vince

On Mar 16, 2007, at 10:39 AM, Patrick R. Michaud wrote:

> On Fri, Mar 16, 2007 at 10:06:34AM +0100, Dominique Faure wrote:
>> On 3/16/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
>>> I've just released 2.2.0-beta36, which adds some new features
>>> to pagelist templates.
>> [...]
>>> Thus, instead of writing control breaks using (:if:) directives,  
>>> as in
>>>
>>>   (:if ! equal {<$Group} {=$Group}:)
>>>   Group: {=$Group}
>>>   (:if:)
>>>   * {=$FullName}
>>>
>>> one can now write
>>>
>>>   (:template first {=$Group}:)
>>>   Group: {=$Group}
>>>   (:template each:)
>>>   * {=$FullName}
>>>
>>
>> Out of curiosity, how does it impact on the pagelist performance: is
>> there a significative difference between both solution?
>
> I haven't done any direct measurements yet, but since can cut
> out a lot of unnecessary (:if:) markups to the rendering engine,
> it should be noticeably faster for long lists.  For example,
> the (:template:) directives in the per-group template above reduce
> the number of lines of markup to be rendered by about 75%.
>
>> BTW, this could be nice to have the $StopWatch enabled into
>> pmwiki.org's Test group.
>
> Good idea -- now done.
>
> Pm
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Conditionals not working correctly since beta32

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 07:05:35PM +0100, Han Baas wrote:
> Hi,
> 
> Since beta32 conditionals are no longer working correctly. The  
> negated form is no longer working.
> 
> I have some mark-up like this:
> (:if ! name Page1, Page2, Page3:)

Because spaces are no longer counted as wildcard/name separators,
this probably needs to be:

   (:if ! name Page1,Page2,Page3 :)

OTOH, it's pretty unlikely that an author will understand that
the spaces aren't permitted here, so perhaps I need to set the
'name' and 'group' conditionals to strip spaces.

Or perhaps I just need to fix it so that matching of pagenames
treats spaces as separators, even though other forms of wildcard
matching do not.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Conditionals not working correctly since beta32

[Han Baas]

Hi,

Since beta32 conditionals are no longer working correctly. The  
negated form is no longer working.

I have some mark-up like this:
(:if ! name Page1, Page2, Page3:)
SomeText
(:if name Page1:)
SomeOtherText
(:if:)

Page1 wil get the correct "SomeOtherText"
Page2 will get SomeText AND SomeOtherText.
If I omit the comma in the first (:if:) statement, Page2 will get  
nothing.

Up to and including beta31, this was working correctly and as intended.

Is this a bug or is it me, that is doing something wrong?

Thanks,
Han

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Hispano-parlantes

[Pablo Manuel Rizzo]

Con fecha 16/3/2007, "Patrick R. Michaud" <[EMAIL PROTECTED]> escribió:

>On Fri, Mar 16, 2007 at 02:33:23PM -0300, Pablo Manuel Rizzo wrote:
>> [EN]
>>
>> For those of you who don't understand spanish: I'm asking if are there
>> other spanish-speaker people in this list. The reason for asking is that
>> I'll give a course about portals creation using PmWiki and it's
>> possible that many students will not be able to read or write in english
>> in order to ask for help in the list.
>
>If there's enough interest, I'll be happy to create a pmwiki-users-es
>list (we already have pmwiki-users-de).
>
>Thanks,
>
>P

Ok, lets see how many people is interested.
Thank!


--
Pablo Manuel Rizzo
--
Aunque supiera que el mundo se acabará mañana,
Igual plantaría mi manzano.   -- Martin Luther King --
--

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] inline pagelist how ?

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 10:16:41AM -0700, Martin Fick wrote:
> 
> --- "Patrick R. Michaud" <[EMAIL PROTECTED]> wrote:
> 
> > Or perhaps we'll also want a way to wrap the
> > contents in a  instead of a , so 
> > perhaps we want tag=div|span|none
> > or something like that.
> 
> I like that; then it can be also:
> 
> (:template default tag=none :)
> 
> since this is the type of thing likely defined by the
> template itself,

Note that even if we eliminate the  surrounding the
pagelist output, the MarkupToHTML function is still likely
to treat the pagelist output as a standalone paragraph and 
surround it with ..., so we need to also figure out 
a way to circumvent that.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Hispano-parlantes

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 02:33:23PM -0300, Pablo Manuel Rizzo wrote:
> [EN]
> 
> For those of you who don't understand spanish: I'm asking if are there
> other spanish-speaker people in this list. The reason for asking is that
> I'll give a course about portals creation using PmWiki and it's
> possible that many students will not be able to read or write in english
> in order to ask for help in the list. 

If there's enough interest, I'll be happy to create a pmwiki-users-es
list (we already have pmwiki-users-de).

Thanks,

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Hispano-parlantes

[Pablo Manuel Rizzo]

Con fecha 16/3/2007, "Ben Stallings" <[EMAIL PROTECTED]>
escribió:
>Si, por lo menos hay uno aqui que te entendio.  Hace muchos anos que no
>he usado espanol, pero estare feliz tratar traducir tus preguntas y las
>respuestas de otros.  Bienvenido a pmwiki-users!  --Ben

[ES]

En realidad yo escribo y leo en ingles casi sin problemas, pero creo
dentro de 10 dias voy a dar un curso de creación de portales utilizando
pmwiki, y es probable que muchos alumnos no entiendan ingles, por eso me
gustaría que puedan obtener alguna ayuda en español. Cuando haya
bastantes personas que cooperen en idioma español, se podría abrir una
nueva lista pmwiki-users-es@, pero por ahora no se si valdrá la pena.
Muchas gracias Ben

Saludos,

[EN]

For those of you who don't understand spanish: I'm asking if are there
other spanish-speaker people in this list. The reason for asking is that
I'll give a course about portals creation using PmWiki and it's
possible that many students will not be able to read or write in english
in order to ask for help in the list. 

Best regards,


--
Pablo Manuel Rizzo
--
Aunque supiera que el mundo se acabará mañana,
Igual plantaría mi manzano.   -- Martin Luther King --
--

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] inline pagelist how ?

[Martin Fick]

--- "Patrick R. Michaud" <[EMAIL PROTECTED]> wrote:

> Or perhaps we'll also want a way to wrap the
> contents in a  instead of a , so 
> perhaps we want tag=div|span|none
> or something like that.

I like that; then it can be also:

(:template default tag=none :)

since this is the type of thing likely defined by the
template itself,

-Martin



 

We won't tell. Get more on shows you hate to love 
(and love to hate): Yahoo! TV's Guilty Pleasures list.
http://tv.yahoo.com/collections/265 

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Hispano-parlantes

[Ben Stallings]

Pablo Manuel Rizzo escribio,
> Hola, estoy por capacitar a un grupo de desarrolladores y autores de
> contenidos para que utilicen PmWiki, yo no tengo ningun inconveniente
> para solicitar ayuda en idioma ingles, pero quer?a saber si hay otros
> participanes de esta lista que escriban espa?ol, as? los nuevos usuarios
> que no manejen el idioma ingles podr?n obtener y brindar ayuda en
> espa?ol.

Si, por lo menos hay uno aqui que te entendio.  Hace muchos anos que no 
he usado espanol, pero estare feliz tratar traducir tus preguntas y las 
respuestas de otros.  Bienvenido a pmwiki-users!  --Ben

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Google Map API 2.2.0 Pre 6 Release (Icons)

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 01:08:30PM -0400, Ben Wilson wrote:
> On 3/15/07, David Spitzley <[EMAIL PROTECTED]> wrote:
> I understand what you're saying now. What do you get when you dump
> $HTMLFooterFmt? I mean, after line 340 of GoogleMapAPI.php, add the
> following:
> 
> print "".print_r($HTMLFooterFmt, 1)."";
> 
> Also, what version of PmWiki? It is possible that you are running a
> version of PmWiki before  was implemented. Thus,
> regardless of whether $HTMLFooterFmt were being properly populated, if
> you were running an earlier version of PmWiki, it would be inert. This
> feature was implemented in PmWiki-2.2.0 beta series. 

$HTMLFooter was introduced in 2.1.25.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Google Map API 2.2.0 Pre 6 Release (Icons)

[Ben Wilson]

On 3/15/07, David Spitzley <[EMAIL PROTECTED]> wrote:
> David
> >>> "Ben Wilson" <[EMAIL PROTECTED]> 03/15/07 5:04 PM >>>
> What is the "require" call you are making to activate the map? It
> should be something like:
>
> require_once("path/to/cookbook/GoogleMapAPI/GoogleMapAPI.php");
> 
>
> That's not what I'm talking about.  Prior to the current incarnation of the 
> API,
> dating back to around version 1.2, there was a modification required at the 
> bottom of
> the skin template that was substantially different in character from the 
> current
>  tag; it was required in order to get the javascript to kick 
> in
> back at v1.2, and I eliminated it when I upgraded to prerelease 6 earlier 
> today.

I understand what you're saying now. What do you get when you dump
$HTMLFooterFmt? I mean, after line 340 of GoogleMapAPI.php, add the
following:

print "".print_r($HTMLFooterFmt, 1)."";

Also, what version of PmWiki? It is possible that you are running a
version of PmWiki before  was implemented. Thus,
regardless of whether $HTMLFooterFmt were being properly populated, if
you were running an earlier version of PmWiki, it would be inert. This
feature was implemented in PmWiki-2.2.0 beta series. Perhaps I should
populate a $GmaFooterFmt to allow you to access the same data if
you're not at 2.2.0 and are not prepared to migrate.

If you want to try that option, then this may get you "on your feet" sooner:

At line 41, add (conceals variable when not-in-use):

  $GmaFooterFmt = '';

At line 322, change:

  $HTMLFooterFmt[] =<

Re: [pmwiki-users] inline pagelist how ?

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 09:30:45AM -0700, Martin Fick wrote:
> --- Hans <[EMAIL PROTECTED]> wrote:
> This div issue has come up many times on the list, how
> about adding a pagelist option that would prevent the
> divs from being added?  
> 
>  (:pagelist nodiv:)  

We'd probably want to make it "nodiv=1", since (:pagelist nodiv:)
technically means to return pages containing "nodiv".

And rather than create a specialized option for it, I might just
tie it to the class= attribute  ("class=nodiv").

Or perhaps we'll also want a way to wrap the contents in a 
instead of a , so perhaps we want tag=div|span|none
or something like that.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Paragraph-ending rule not working in lists?

[christian . ridderstrom]

On Fri, 16 Mar 2007, Kathryn Andersen wrote:


On Fri, Mar 16, 2007 at 07:53:21AM +0100, [EMAIL PROTECTED] wrote:

On Thu, 15 Mar 2007, Patrick R. Michaud wrote:

PS. Yes, I know anchors could be used to define the description paragraph,
but for some reason I never get around to actually inserting a
[[#desc]]...


Isn't that what the (:description :) directive is for?


IIRC, the description directive is really used to insert a special header 
in the HTML, and you can't use arbitrary text in there, e.g. links or 
other wiki markup. (Please correct me if I'm wrong)


/Christian

--
Christian Ridderström, +46-8-768 39 44   http://www.md.kth.se/~chr___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Hispano-parlantes

[Pablo Manuel Rizzo]

Hola, estoy por capacitar a un grupo de desarrolladores y autores de
contenidos para que utilicen PmWiki, yo no tengo ningun inconveniente
para solicitar ayuda en idioma ingles, pero quería saber si hay otros
participanes de esta lista que escriban español, así los nuevos usuarios
que no manejen el idioma ingles podrán obtener y brindar ayuda en
español.
Muchas gracias.

Saludos,


--
Pablo Manuel Rizzo
--
Aunque supiera que el mundo se acabará mañana,
Igual plantaría mi manzano.   -- Martin Luther King --
--

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] inline pagelist how ?

[Martin Fick]

--- Hans <[EMAIL PROTECTED]> wrote:
> Friday, March 9, 2007, 7:25:30 AM, SteP wrote:
> 
> >   text before (:pagelist fmt=#online count=1:)
> text after
> > should be
> >   text before PageName text after 
> 
> pagelist output obtained with PagelistTemplates have
> an outer containing division.
> Look at the HTML source of your page to see.
> Divs are block elements, and not inline elements.

This div issue has come up many times on the list, how
about adding a pagelist option that would prevent the
divs from being added?  

 (:pagelist nodiv:)  

This makes a lot more sense now that options can be
defined in the template with something like:

 (:template default nodiv:)

This would open up a whole range of new possible
templates,

-Martin



 

Get your own web address.  
Have a HUGE year through Yahoo! Small Business.
http://smallbusiness.yahoo.com/domains/?p=BESTDEAL

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Skin & ... various questions

[St�phane Heckel]

"Sandy" wrote :

>> I have observed that $WikiTitle is not displayed in the pmwiki style, ...
>> It's maybe something wrong on my side ?

> It's doing what it should.
> The pmwiki tmpl does not show $WikiTitle. It shows an image: the red and
> blue PmWiki logo.

yes right ... I have understood the concept now :)

Stéphane







___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Skin & ... various questions

[St�phane Heckel]

<[EMAIL PROTECTED]> wrote :

> Do you have a url to point us to?

no sorry, ... it's a "standalone" configuration.
btw, thanks for your help !

Stéphane 




___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Skin & ... various questions

[St�phane Heckel]

"Sandy" wrote :

> It is very easy to edit the files directly.
> (deletes instructions, looks like you've found a way)

I did that, ... You can learn a lot ;-))

> The Beginner Guides on http://www.htmldog.com/guides/ seem good.

Thanks for link !
Learning 

Stéphane 




___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Skin & ... various questions

[Sandy]

Stéphane Heckel wrote:
> <[EMAIL PROTECTED]> wrote :
> 
>> My humble experience is that if you start by making experiments with
>> the standard pmwiki skin, and maybe later consider a skin like Triad
> 
> yep ... I have played with pmwiki style, trying to understand the css 
> concept.
> I have observed that $WikiTitle is not displayed in the pmwiki style, ...
> It's maybe something wrong on my side ? 

It's doing what it should.

The pmwiki tmpl does not show $WikiTitle. It shows an image: the red and 
blue PmWiki logo.

Hope this helps,

Sandy


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Skin & ... various questions

[Sandy]

[EMAIL PROTECTED] wrote:
>> I wanted to say that $WikiTitle was not displayed
>> just next to the pmwiki logo, ... (like it is in the abitmodern skin).
> 
> Do you have a url to point us to?
> Can we see the site, please?

It will make sure we're using the same terminology.

>> I do not have the skills to change css & tmpl files,
>> ... just looking for a wysiwyg editor ;-))

The bad news:

Using a wysiwyg editor for skins is just asking for headaches. They add 
code which will break PmWiki, and they break the code PmWiki needs.

The good news:

It is very easy to edit the files directly.

(deletes instructions, looks like you've found a way)

More good news:

It will take under an hour to learn enough HTML and CSS to be very 
comfortable editing those files.

The Beginner Guides on http://www.htmldog.com/guides/ seem good. Work 
through the first three examples in each of the guides and read enough 
of the rest to see the pattern. (Let me know if they aren't as easy as 
they look, or if you find an easier tutorial.)

This will be enough to understand what is happening in the skin files, 
and to understand the shorthand descriptions often used here.

The tmpl file is an html file with bits of extra code thrown in. The 
program will read the tmpl file, replace the bits as described below, 
rename it as html, and send it to the browser.

* $word is replaced with a value from the program, such as $WikiTitle
*  is replaced with something longer, like the contents 
of the sidebar or the actual page.

I know this isn't what you wanted to hear, but if you want to do more 
than a few tweaks, it will save more than an hour's worth of headaches 
in the long run.

Sandy






___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] New Recipe: IntuitiveSpacing

[the Other michael]

That is most excellent, thank you!

I preferred using the middots instead of a list finicky!

On 3/16/07, Hans <[EMAIL PROTECTED]> wrote:
> Just updated the recipe with support for (:nolinebreaks:) and
> (:linebreaks:) markup


-- 
-the Other michael
http://www.xradiograph.com/interference

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Minor edit or notify post

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 08:21:09AM -0700, Dr Fred C wrote:
>So using your second suggestion, all it seems one would need to get it to
>fully work as I want is find the text in the edit box that says 'this is a
>minor edit' and change it to "Notify the Email List".  Anyone know where
>that text is located?
> 
>I suppose ideally, the 'minor edit' check box text should be made a
>variable that one could set in some sort of site.setup file or local
>config to whatever one wanted.  Perhaps it already is? 

It's in the Site.EditForm page.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] 2.2.0-beta36 release (pagelist template updates)

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 08:25:48AM -0700, Martin Fick wrote:
> 
> --- "Patrick R. Michaud" <[EMAIL PROTECTED]> wrote:
> 
> > I've just released 2.2.0-beta36, which adds some new
> > features to pagelist templates.  
> ...
> > and adds some additional capabilities to the 
> > count= option in pagelists.  
> 
> Will you consider adding something to help complete
> paging support now?  A very generic solution would be
> a simple math recipe along with access to GET
> variables.  

I'm still looking into this, but my feeling is that the
"math recipe" approach is overkill (and over complex).

> Examples of how to page by ten using {$?get_var} and
> $((math_expression)) as sample notations:
> 
> (:template default size=10 count={$?beg}..$(({$?beg} +
>  {$$size})) :)

I'm still playing with the count= notation, so the syntax
might change a bit.  In particular, I think that it may
still be better to do something like

start=m count=n

than to try to make count=m..m+n work.

Also, note that (:template default ...:) does not (yet?) understand
the {$$var} notation.  There's a small chicken-and-egg problem there,
in that we're trying to use the defaults to set options to pagelist,
but the options to pagelist are themselves the source of {$$var} values.
This isn't to say it can't be done, only that I have to look at the 
complete ramifications a bit more before enabling it.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] 2.2.0-beta36 release (pagelist template updates)

[Martin Fick]

--- "Patrick R. Michaud" <[EMAIL PROTECTED]> wrote:

> I've just released 2.2.0-beta36, which adds some new
> features to pagelist templates.  
...
> and adds some additional capabilities to the 
> count= option in pagelists.  

Those are some really cool new features, thanks!  

Will you consider adding something to help complete
paging support now?  A very generic solution would be
a simple math recipe along with access to GET
variables.  

Examples of how to page by ten using {$?get_var} and
$((math_expression)) as sample notations:

(:template default size=10 count={$?beg}..$(({$?beg} +
 {$$size})) :)

[[{$FullName}?beg=$(({$?beg}-{$$size}))|Prev
{$$size}]]
[[{$FullName}?beg=$(({$?beg}+{$$size}))|Next
{$$size}]]

Or you could even allow a simplification that would
not require the outer {} rackets inside of math
expressions so that it could look more like this:

(:template default size=10 count={$?beg}..$(($?beg + 
$$size)) :)

[[{$FullName}?beg=$(($?beg - $$size))|Prev {$$size}]]
[[{$FullName}?beg=$(($?beg + $$size))|Next {$$size}]]


-Martin



 

Sucker-punch spam with award-winning protection. 
Try the free Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/features_spam.html

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Minor edit or notify post

[Dr Fred C]

Francis Casson wrote:

  
  

On 11/03/07, Dr Fred C <[EMAIL PROTECTED]>
wrote:
Is
there a way to change the minor edit box into a 'notify list'
selection box?  Only when it's clicked would the notify procedure be
activated.   Ideally, it would seem that this ought to be some sort of
  
toggle in the config file for a variable of something like Edit select
box -- 0=don't use, 1=minor edit 2=notify list.


  
  
You could also try
  
if ( @$_POST['diffclass'] != 'minor' ) $EnableNotify=1;
  
  
in your config.php (but I haven't tested this as I don't use Notify.)
  
This
way, only 'major' edits send notify messages, but it doesn't let you
select minor edits separately from the notify option - to do that you'd
need to add another checkbox to the edit form and (I think) a handler
from the extra returned form data. You can set minor edits to be the
default by setting (:input e_minorcheckbox checked=1:) on the edit
form.
  
  
If you want minor edits and not major edits to send the message then
you would use
  
if ( @$_POST['diffclass'] == 'minor' ) $EnableNotify=1;
  
  
  

So using your second suggestion, all it seems one would need to get it
to fully work as I want is find the text in the edit box that says
'this is a minor edit' and change it to "Notify the Email List". 
Anyone know where that text is located? 

I suppose ideally, the 'minor edit' check box text should be made a
variable that one could set in some sort of site.setup file or local
config to whatever one wanted.  Perhaps it already is?  
-- 

Always, Dr Fred C
[EMAIL PROTECTED]



___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] 2.2.0-beta36 release (pagelist template updates)

[Dominique Faure]

On 3/16/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 16, 2007 at 10:06:34AM +0100, Dominique Faure wrote:
> > On 3/16/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> > >I've just released 2.2.0-beta36, which adds some new features
> > >to pagelist templates.
> > [...]
> > >Thus, instead of writing control breaks using (:if:) directives, as in
> > >
> > >   (:if ! equal {<$Group} {=$Group}:)
> > >   Group: {=$Group}
> > >   (:if:)
> > >   * {=$FullName}
> > >
> > >one can now write
> > >
> > >   (:template first {=$Group}:)
> > >   Group: {=$Group}
> > >   (:template each:)
> > >   * {=$FullName}
> > >
> >
> > Out of curiosity, how does it impact on the pagelist performance: is
> > there a significative difference between both solution?
>
> I haven't done any direct measurements yet, but since can cut
> out a lot of unnecessary (:if:) markups to the rendering engine,
> it should be noticeably faster for long lists.  For example,
> the (:template:) directives in the per-group template above reduce
> the number of lines of markup to be rendered by about 75%.
>
> > BTW, this could be nice to have the $StopWatch enabled into
> > pmwiki.org's Test group.
>
> Good idea -- now done.
>

So, here's a quick and dirty bench, using both syntaxes on the Test pages:

[@
[[#default]]
(:if ! equal {=$Group} {<$Group}:)

:[[{=$Group}/]] /:
(:if:)
: :[[{=$Group}/{=$Name}]]
[[#defaultend]]
@]

(:pagelist group=Test fmt=#default:)

gives:

00.00 00.00 config start
00.00 00.00 config end
00.08 00.07 MarkupToHTML begin
00.09 00.08 FPLTemplate begin
00.09 00.08 MakePageList pre
00.09 00.08 PageListSources begin
00.10 00.09 PageStore::ls begin wiki.d/{$FullName}
00.18 00.12 PageStore::ls merge wiki.d/{$FullName}
00.22 00.15 PageStore::ls end wiki.d/{$FullName}
00.22 00.16 PageStore::ls begin $FarmD/wikilib.d/{$FullName}
00.23 00.16 PageStore::ls merge $FarmD/wikilib.d/{$FullName}
00.23 00.16 PageStore::ls end $FarmD/wikilib.d/{$FullName}
00.23 00.16 PageListSources end count=681
00.23 00.16 PageListSort pre ret=4 order=name
00.23 00.16 MakePageList items count=681, filters=
00.24 00.17 MakePageList post count=681, readc=0
00.24 00.17 PageListSort begin
00.28 00.22 PageListSort end
00.28 00.22 MakePageList end
00.59 00.49 MarkupToHTML begin
03.37 02.39 MarkupToHTML end
03.37 02.39 FPLTemplate end
03.38 02.39 MarkupToHTML end
03.40 02.41 MarkupToHTML begin
03.43 02.44 ReadApprovedUrls Site.ApprovedUrls begin
03.43 02.44 ReadApprovedUrls Site.ApprovedUrls end
03.45 02.46 MarkupToHTML end
03.46 02.46 MarkupToHTML begin
03.47 02.48 MarkupToHTML end
03.48 02.49 now

whereas:

[@
[[#default]]
(:template first {=$Group}:)

:[[{=$Group}/]] /:
(:template each:)
: :[[{=$Group}/{=$Name}]]
[[#defaultend]]
@]

(:pagelist group=Test fmt=#default:)

results in:

00.00 00.00 config start
00.00 00.00 config end
00.09 00.08 MarkupToHTML begin
00.11 00.10 FPLTemplate begin
00.11 00.10 MakePageList pre
00.11 00.10 PageListSources begin
00.11 00.10 PageStore::ls begin wiki.d/{$FullName}
00.21 00.13 PageStore::ls merge wiki.d/{$FullName}
00.25 00.17 PageStore::ls end wiki.d/{$FullName}
00.26 00.17 PageStore::ls begin $FarmD/wikilib.d/{$FullName}
00.26 00.17 PageStore::ls merge $FarmD/wikilib.d/{$FullName}
00.26 00.17 PageStore::ls end $FarmD/wikilib.d/{$FullName}
00.26 00.17 PageListSources end count=681
00.26 00.17 PageListSort pre ret=4 order=name
00.26 00.17 MakePageList items count=681, filters=
00.28 00.19 MakePageList post count=681, readc=0
00.28 00.19 PageListSort begin
00.32 00.23 PageListSort end
00.32 00.23 MakePageList end
00.57 00.45 MarkupToHTML begin
02.43 02.11 MarkupToHTML end
02.43 02.11 FPLTemplate end
02.44 02.12 MarkupToHTML end
02.46 02.13 MarkupToHTML begin
02.48 02.16 ReadApprovedUrls Site.ApprovedUrls begin
02.49 02.16 ReadApprovedUrls Site.ApprovedUrls end
02.51 02.19 MarkupToHTML end
02.51 02.19 MarkupToHTML begin
02.52 02.20 MarkupToHTML end
02.54 02.21 now

which is quite better!

It's time to update Site.PageListTemplates, no?

Dom

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] New Recipe: IntuitiveSpacing

[Hans]

Friday, March 16, 2007, 2:15:17 PM, Hans wrote:

> I will try if I can redefine (:nolinebreaks:) markup to work with
> whitespace.php

Just updated the recipe with support for (:nolinebreaks:) and
(:linebreaks:) markup


Hans


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] 2.2.0-beta36 release (pagelist template updates)

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 10:06:34AM +0100, Dominique Faure wrote:
> On 3/16/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> >I've just released 2.2.0-beta36, which adds some new features
> >to pagelist templates.
> [...]
> >Thus, instead of writing control breaks using (:if:) directives, as in
> >
> >   (:if ! equal {<$Group} {=$Group}:)
> >   Group: {=$Group}
> >   (:if:)
> >   * {=$FullName}
> >
> >one can now write
> >
> >   (:template first {=$Group}:)
> >   Group: {=$Group}
> >   (:template each:)
> >   * {=$FullName}
> >
> 
> Out of curiosity, how does it impact on the pagelist performance: is
> there a significative difference between both solution?

I haven't done any direct measurements yet, but since can cut
out a lot of unnecessary (:if:) markups to the rendering engine,
it should be noticeably faster for long lists.  For example,
the (:template:) directives in the per-group template above reduce 
the number of lines of markup to be rendered by about 75%.

> BTW, this could be nice to have the $StopWatch enabled into
> pmwiki.org's Test group.

Good idea -- now done.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] pattern matching question...

[The Editor]

In order to help with downward compatibility on ZAPbeta 2007-03, I'm
trying to set up a pattern that will match something like this:

Field="Value"

if the normal PTV function finds nothing.  Given the field name is
$var, I'd like to be able to do something like:

$var = PageTextVar($page, $var);
if ($var == '') {
$page = ReadPage($page);
$var = preg_replace('/'$var'\\=\\"(.*?)\\"/s',"$1", 
$page['text']);
}

It seems to be close to matching the pattern cause it does something
strange on the page text, but I don't want to change the page text, I
want to simply extract the $var value from the page and assign it to
$var.  Can someone explain what function to use to do this?  TIA!

Cheers,
Dan

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] New Recipe: IntuitiveSpacing

[Hans]

Friday, March 16, 2007, 1:24:48 PM, the wrote:

> Hrm. still a vertical list

Try to change Site.PageActions so that all links are written on one line,
or each action link is a list item:

* %item 
* %item.

Generally whitespace.php will insert  line break tags for each
line (honouring line breaks), also on pages like site.PageAction which
are part of the page.

I will try if I can redefine (:nolinebreaks:) markup to work with
whitespace.php

I have not tested if there are any conflicts with extendmarkup.php.
There may be markups in that script concerning line breaks or
whitespace which are not needed. But I have not investigated this.

Hans


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Finishing ZAP touches...

[The Editor]

Just a couple quick questions:

1) I have added automatic encryption for passwords to ZAP's
registration and login mechanism, and it works great (also recognizes
plain text passwords on existing sites).  I wonder if it is worth
giving the admin an option for turning on and off encryption, for
sites where you might want to retrieve a password, say in answer to a
reminder question, or on an email confirmation, or send (plain text)
by email, etc.  Guess options are good, eh?

2) Still looking for php commands others might like to see enabled by
default in ZAP.  I currently have substr, strpos, date, time, and now
just added crypt.

Guess that's about it. I have all the snippets upgraded and the
documentation is complete.  Should be uploading it all in the next few
hours, along with the new scripts.  Added a complete developers
section outlining how each of the internal ZAP functions work, their
parameters, output, etc...

Last chance for items on your wish list

Cheers,
Dan

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Fwd: New Recipe: IntuitiveSpacing

[The Editor]

[oops -- sorry about the other email]

On 3/16/07, the Other michael <[EMAIL PROTECTED]> wrote:
> In general, is it possible to specify in config.php that recipes
> should be disabled/enabled for particular groups?


Sure, try:

if (FmtPageName('$Group', $pagename) == "Store") {
include_once("$FarmD/cookbook/zapcart.php");
}

Normally though the include line would simply be put in Store.php

Cheers,
Dan

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] List of Designers for Hire who use PmWiki

[Patrick R. Michaud]

On Fri, Mar 16, 2007 at 08:06:57AM +0100, [EMAIL PROTECTED] wrote:
> >Also, if anyone is interested in advertising on prime real estate for 
> >the pmwiki.org site (such as the PmWiki home page), I'm open to discuss 
> >it.  Currently the pmwiki.org home page receives on the order of 700 
> >pageviews per day (according to Google Analytics).
> 
> At first I thought "only 700", but then I noticed it was only the home 
> page. Out of curiosity though... do you think Google Analytics is able to 
> reliably recognize humans from bots etc?

Sure.  Google Analytics works via a small snippet of javascript
on each page that causes browsers to issue requests back to Google's
site (which Google then counts).  Since most bots don't parse or
evaluate the javascript, only "real" browsers tend to get counted.

> As a side note, I often go to pmwiki.org when looking for documentation, 
> so some of these visits might be people lik me. 

Sure.  Analytics says that 35% arrive via Google search, and 17%
arrive directly.  

> So out of further 
> curiosity, do you have any statistics for a page that's likely to be 
> visited by someone interested in learning more about pmwiki? (I looked at 
> the home page and couldn't find a single obvious link of where to go for 
> learning more about pmwiki - maybe you should have such a page?)

For February, the most visited sections were the Cookbook and PmWiki
groups (203,282 and 93,896 pageviews respectively).  You're correct
that there's not a single obvious link that would catch newcomers...
I'll add one if I can find an appropriate place for it.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] New Recipe: IntuitiveSpacing

[The Editor]

On 3/16/07, the Other michael <[EMAIL PROTECTED]> wrote:
> Hrm. still a vertical list
>
> http://www.xradiograph.com/wrottings/PrantedMutter/PrantedMutter
>
> I'm also using MarkupExtenstions -
> http://www.pmwiki.org/wiki/Cookbook/MarkupExtensions -  could that
> lead to any conflicts? The PageList directives were horizontal with
> the extensions, and only became vertiacal after added LWP.
>
> On 3/16/07, Hans <[EMAIL PROTECTED]> wrote:
> > Friday, March 16, 2007, 2:13:12 AM, the wrote:
> >
> > > I missing how Site.PageActions was updated to work with 
> > > LiteralWhiteSpace...
> >
> > The latest version should work well with PageActions.
> > No need to change anything in PageActions.
> > Please download  and install the latest version.
>
> > > is there, or will there be, a markup to disable it for a particular
> > > stretch of text, like the opposite of (:linebreaks:) ???
> >
> > It would be great, but I don't know at present how to do that or if it is
> > possible.
>
>
> In general, is it possible to specify in config.php that recipes
> should be disabled/enabled for particular groups?
>
> --
> -the Other michael
> http://www.xradiograph.com/interference
>
> DISCLAIMER: links contained in mail from this address may or may not
> be contextually related to any encapsulating text.
>
> STATEMENT OF CONFIDENTIALITY: I send a bcc of every email only to the
> NSA, because I want America to Be Secure.
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] New Recipe: IntuitiveSpacing

[the Other michael]

Hrm. still a vertical list

http://www.xradiograph.com/wrottings/PrantedMutter/PrantedMutter

I'm also using MarkupExtenstions -
http://www.pmwiki.org/wiki/Cookbook/MarkupExtensions -  could that
lead to any conflicts? The PageList directives were horizontal with
the extensions, and only became vertiacal after added LWP.

On 3/16/07, Hans <[EMAIL PROTECTED]> wrote:
> Friday, March 16, 2007, 2:13:12 AM, the wrote:
>
> > I missing how Site.PageActions was updated to work with LiteralWhiteSpace...
>
> The latest version should work well with PageActions.
> No need to change anything in PageActions.
> Please download  and install the latest version.

> > is there, or will there be, a markup to disable it for a particular
> > stretch of text, like the opposite of (:linebreaks:) ???
>
> It would be great, but I don't know at present how to do that or if it is
> possible.


In general, is it possible to specify in config.php that recipes
should be disabled/enabled for particular groups?

-- 
-the Other michael
http://www.xradiograph.com/interference

DISCLAIMER: links contained in mail from this address may or may not
be contextually related to any encapsulating text.

STATEMENT OF CONFIDENTIALITY: I send a bcc of every email only to the
NSA, because I want America to Be Secure.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Minor edit or notify post

[Francis Casson]

On 11/03/07, Dr Fred C <[EMAIL PROTECTED]> wrote:
>
> Is there a way to change the minor edit box into a 'notify list'
> selection box?  Only when it's clicked would the notify procedure be
> activated.   Ideally, it would seem that this ought to be some sort of
> toggle in the config file for a variable of something like Edit select
> box -- 0=don't use, 1=minor edit 2=notify list.



You could also try

if ( @$_POST['diffclass'] != 'minor' ) $EnableNotify=1;

in your config.php (but I haven't tested this as I don't use Notify.)

This way, only 'major' edits send notify messages, but it doesn't let you
select minor edits separately from the notify option - to do that you'd need
to add another checkbox to the edit form and (I think) a handler from the
extra returned form data. You can set minor edits to be the default by
setting (:input e_minorcheckbox checked=1:) on the edit form.

If you want minor edits and not major edits to send the message then you
would use

if ( @$_POST['diffclass'] == 'minor' ) $EnableNotify=1;

Instead.

http://www.pmwiki.org/wiki/Cookbook/MessageAfterPosting is a different and
completely separate method, not using notify at all - no reason to assume
they couldn't be used at the same time.

Hope this helps,

Francis
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] New Recipe: IntuitiveSpacing

[Hans]

Friday, March 16, 2007, 2:13:12 AM, the wrote:

> I missing how Site.PageActions was updated to work with LiteralWhiteSpace...

The latest version should work well with PageActions.
No need to change anything in PageActions.
Please download  and install the latest version.

$RecipeInfo['LiteralWhiteSpace']['Version'] = '2007-03-15a';

see http://www.pmwiki.org/wiki/Cookbook/LiteralWhiteSpace

> is there, or will there be, a markup to disable it for a particular
> stretch of text, like the opposite of (:linebreaks:) ???

It would be great, but I don't know at present how to do that or if it is
possible.

Hans


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] new Bonny skin

[Kathryn Andersen]

Aye, and verrra Bonny it be, too.

http://www.pmwiki.org/wiki/Cookbook/BonnySkin

Those of you who might remember my ill-fated KatSkin, yes, this looks
extremely similar.  However the CSS underneath is completely different
(I'm using a new method) and it has new, extra nifty features -- like an
optional 3-column layout!

It also plays well with Cluster.

Kathryn Andersen
-- 
 _--_|\ | Kathryn Andersen  
/  \| 
\_.--.*/| GenFicCrit mailing list 
  v | 
| Melbourne -> Victoria -> Australia -> Southern Hemisphere
Maranatha!  |   -> Earth -> Sol -> Milky Way Galaxy -> Universe

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] 2.2.0-beta36 release (pagelist template updates)

[Dominique Faure]

On 3/16/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> I've just released 2.2.0-beta36, which adds some new features
> to pagelist templates.
[...]
> Thus, instead of writing control breaks using (:if:) directives, as in
>
>(:if ! equal {<$Group} {=$Group}:)
>Group: {=$Group}
>(:if:)
>* {=$FullName}
>
> one can now write
>
>(:template first {=$Group}:)
>Group: {=$Group}
>(:template each:)
>* {=$FullName}
>

Out of curiosity, how does it impact on the pagelist performance: is
there a significative difference between both solution?

BTW, this could be nice to have the $StopWatch enabled into
pmwiki.org's Test group.

Dom

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Paragraph-ending rule not working in lists?

[Kathryn Andersen]

On Fri, Mar 16, 2007 at 07:53:21AM +0100, [EMAIL PROTECTED] wrote:
> On Thu, 15 Mar 2007, Patrick R. Michaud wrote:
> 
> PS. Yes, I know anchors could be used to define the description paragraph, 
> but for some reason I never get around to actually inserting a 
> [[#desc]]...

Isn't that what the (:description :) directive is for?
Then you could go

(:toc:)

(:description what this page is about in one sentence:)
{$Description}

Then you could use the #description pagelist format...

Kathryn Andersen
-- 
 _--_|\ | Kathryn Andersen  
/  \| 
\_.--.*/| GenFicCrit mailing list 
  v | 
| Melbourne -> Victoria -> Australia -> Southern Hemisphere
Maranatha!  |   -> Earth -> Sol -> Milky Way Galaxy -> Universe

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users