Re: [pmwiki-users] are anchors or nonexisting pages first class citiziens

[Randy Brown]

What's best depends on a lot of details about your situation that I don't know. 
From what you've told us, I'd go with giving each keyword its own page (option 
#1), because pagelist doesn't know about non-existing pages. 

If your users find empty pages confusing, you could put the keywords in their 
own group and do something like this:

1. In the group header:

(:if !equal "{*$:Description}" "":)
{*$:Description}
(:else:)
This keyword has no description
(:ifend:)

2. On the page:

Description: your sentence

You also might be able to use Definition Lists, briefly described at 
http://www.pmwiki.org/wiki/PmWiki/TextFormattingRules, or possibly use the 
TextExtract recipe (see http://www.pmwiki.org/wiki/Cookbook/TextExtract).

Randy

 
On Jul 15, 2010, at 2:17 PM, Walter Keller wrote:

> I'm using PM Wiki to keep track of thousands of keywords. Many of them has 
> only a small sentence attached to it.  I want some advice how to do it best:

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

[pmwiki-users] are anchors or nonexisting pages first class citiziens

[Walter Keller]

I'm using PM Wiki to keep track of thousands of keywords. Many of them 
has only a small sentence attached to it.  I want some advice how to do 
it best:
1) every keyword get's its own (existing) page, in the index page I have 
a reference to each keyword page
2) every keyword get's its own page, in most cases (with only a short 
definition attached to the keyword) the page does not exist. It exists 
only for keywords with a reasonable long text.
3) a keyword is either an anchor in an index page, or (if it has a lot 
of text) an own page.


variant 1) needs a lot of (nearly) empty pages which is confusing and 
(possibly) slow.
variant 2) gets a lot of non existing pages. What are the disadvantages? 
Can I use them e.g. in pagelists? Can I list all existing pages 
togethether with all reference pages that do not exist?
variant 3) a lot does not work for anchors, e.g. (:if exists 
page#anchor:), anchorlist as the analogon for pagelists etc..

variant 4) any other suggestion

Furthermore, I use custom markup which yields an anchor. This anchor is 
not recognized by includes, because the do a hard search for [[#... 
without any regEx replacements. Is there a way to get this running?


thanks for your comments

Walter

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

Re: [pmwiki-users] Getting the list of all anchors in a page ?

[Simon]

See
http://pmwiki.org/wiki/Cookbook/PageTableOfContents

also vote for
http://pmwiki.org/wiki/PITS/00027 (see my comment about making anchors part
of pagelist)
http://pmwiki.org/wiki/PITS/00955

On 16 July 2010 04:35, ABClf  wrote:

> Hi all !
>
> I guess (please tell me if I'm wrong) there is no automatic way to do
> it, but it may be an idea ?
> Is there an automatic way to get a simple toc listing the anchors of a page
> ?
> (I know there are some for headers-toc).
>
> In my case, I have a page with some anchors well named ; and I would
> find convenient to use something as (:listanchor:) to get a basic list
> (I would like an horizontal format : word1 ; word2 ; word3) instead of
> doing the list by hand.
>
> [[#word1]]
> ...
> ...
> [[#word2]]
> ...
> ...
> ...
> [[#word3]]
>
>
> Thank you !
>
> Gilles.
>
>
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Getting the list of all anchors in a page ?

[ABClf]

Hi all !

I guess (please tell me if I'm wrong) there is no automatic way to do
it, but it may be an idea ?
Is there an automatic way to get a simple toc listing the anchors of a page ?
(I know there are some for headers-toc).

In my case, I have a page with some anchors well named ; and I would
find convenient to use something as (:listanchor:) to get a basic list
(I would like an horizontal format : word1 ; word2 ; word3) instead of
doing the list by hand.

[[#word1]]
...
...
[[#word2]]
...
...
...
[[#word3]]


Thank you !

Gilles.

-- 
---
| A | de la langue française
| B | http://www.languefrancaise.net/
| C | languefranca...@gmail.com
---

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

Re: [pmwiki-users] (no subject)

[Randy Brown]

If you want a text logout link next to the name, try this: 

(:if authid:)
{$AuthId} [[{*$FullName}?action=logout | $[Logout] ]]
(:ifend:)

If you want an image logout button next to the name (see 
http://www.pmwiki.org/wiki/PmWiki/Images), try this:

(:if authid:)
{$AuthId} [[{*$FullName}?action=logout |  
http://example.com/path/to/image.png"Logout"; ]]
(:ifend:)

Randy


On Jul 15, 2010, at 2:15 AM, the ntbk wrote:
> 
> I just want to image the logout button beside of the name of the person which 
> just logged in to the website.

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

Re: [pmwiki-users] Include static HTML

[Laatz, Erek]

Hi,

I use cookbook/includeurl on our intranet site successfully. I have
placed includeurl.php in the cookbook directory and have added the line

   include_once("$FarmD/cookbook/includeurl.php");

into my config.php.

After that I've placed the static pages into the webservers htdocs
directory structure (not in the pmwiki directory!) and have included the
URL like

(:includeurl http://foo.bar/static-html/index.html height=550px:)

I have even tested: it works also e.g. for image galleries with complex
forward- and backlinks

It's (in my opinion) not so complex like described below ;-)

Best regards,

Erek

Am 13.07.2010 19:40, schrieb Chris Cox:
> On Tue, 2010-07-13 at 09:26 -0700, pmw...@911networks.com wrote:
>>> Not sure if the following is perfect, but it works...
>>>
>>> Markup(
>>>  'html',
>>>  'fulltext',
>>>  '/\\(:html:\\)(.*?)\\(:htmlend:\\)/esi',
>>>  "'<:block>'.Keep(str_replace(array('>', '<', '&'),
>>>  array('>', '<', '&'), PSS('$1')))");
>>
>> Sorry, but I'm not sure that I understand. Mostly because I didn't
>> expand on my situation:
>>
>> 1. I have static web pages generated by Arles[1], images with
>> titles/keywords...
>> 2. It generates an index.html, then each image has its own web page,
>> with annotation and navigation for next/previous...
>> 3. My pagestore is: 'wiki.d/{$Group}/{$FullName}' so I store
>> everything by group.
>>
>> so are you saying that I should include the index.html source inside
>> the (:html:) (:htmlend:)?
>>
>> But then where do I store the individual pages?
>>
>> [1] http://digitaldutch.com/arles/
>>
> 
> For including complex websites, I'd use the original plan... includeURL
> or includeSite recipe.
> 
> I think we use includeSite... includes the remote website inside of a
> frame.  Reasonable solution.
> 
> 
> 
> ___
> 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

[pmwiki-users] (no subject)

[the ntbk]

Hi All,

Thanks for your reply. But it seems that i couldnt explain clearly my
request in my previous e-mail.
I just want to image the logout button beside of the name of the person
which just logged in to the website.

Can you please advise me how can i range it?

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