phpwiki-talk

[Phpwiki-talk] was <code></code>

[Steve W. <sw...@pa...>]

I hit reply to the wrong email... for those following this thread...

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa
---------- Forwarded message ----------
Date: Fri, 7 Dec 2001 00:14:53 -0500 (EST)
From: Steve Wainstead <sw...@pa...>
To: Jeff Dairiki <da...@da...>
Cc: car...@ma..., php...@li...
Subject: Re: [Phpwiki-talk]
    =?iso-8859-1?Q?Re:_[Phpwiki-talk]_3-single_quotes_and_5-single_quotes_broken
    =3F?=


I'd like to move (again) to a syntax like the NBTSC Wiki, which is in line
with suggestions by many users over the last two years. Ali went for
syntax that is a lot like how people do things in plain text elsewhere:

*bold*
/italic/

I think are two examples. Ali's reasoning was the marked up page language
should be as easy to read/understand as the rendered page.

Now, the one thing that has troubled me about both the plugin syntax and
the proposed plain text tags is they are not consistent with the markup to
date... and inconsistency is not good for the user. As PhpWiki grows in
features, though, I understand it gets harder to maintain consistency.

I'd like to see some proposals that are consistent with our current
syntax, or some way that would be compatible with NBTSC syntax.

~swain

On Thu, 6 Dec 2001, Jeff Dairiki wrote:

> Carsten Klapp said:
> >
> > 3-single-quotes (bold) and 5-single-quotes (bold-italic) seems
> > completely  broken now. Is this a known problem or is it just me?
>
> I think that's been broken (or rather "never implemented") since Arno's new
> transform code last winter/spring...
>
> I don't suspect it would be hard to add.  Is there really a need?
> (Leading-tab-delimited lists, I think, are also not currently working in
> 1.3.)
>
>
>
>
>
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa


_______________________________________________
Phpwiki-talk mailing list
Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

Re: [Phpwiki-talk] =?iso-8859-1?Q?Re:_[Phpwiki-talk]_3-single_quotes_and_5-single_quotes_broken=3F?=

[Steve W. <sw...@pa...>]

It would help if I hit reply to the right emails... doh..

I don't care to see ''' added again. Arno left it out on purpose. Same
with tabs. They're history.

~swain

On Thu, 6 Dec 2001, Jeff Dairiki wrote:

> Carsten Klapp said:
> >
> > 3-single-quotes (bold) and 5-single-quotes (bold-italic) seems
> > completely  broken now. Is this a known problem or is it just me?
>
> I think that's been broken (or rather "never implemented") since Arno's new
> transform code last winter/spring...
>
> I don't suspect it would be hard to add.  Is there really a need?
> (Leading-tab-delimited lists, I think, are also not currently working in
> 1.3.)
>
>
>
>
>
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa

Re: [Phpwiki-talk] =?iso-8859-1?Q?Re:_[Phpwiki-talk]_3-single_quotes_and_5-single_quotes_broken=3F?=

[Steve W. <sw...@pa...>]

I'd like to move (again) to a syntax like the NBTSC Wiki, which is in line
with suggestions by many users over the last two years. Ali went for
syntax that is a lot like how people do things in plain text elsewhere:

*bold*
/italic/

I think are two examples. Ali's reasoning was the marked up page language
should be as easy to read/understand as the rendered page.

Now, the one thing that has troubled me about both the plugin syntax and
the proposed plain text tags is they are not consistent with the markup to
date... and inconsistency is not good for the user. As PhpWiki grows in
features, though, I understand it gets harder to maintain consistency.

I'd like to see some proposals that are consistent with our current
syntax, or some way that would be compatible with NBTSC syntax.

~swain

On Thu, 6 Dec 2001, Jeff Dairiki wrote:

> Carsten Klapp said:
> >
> > 3-single-quotes (bold) and 5-single-quotes (bold-italic) seems
> > completely  broken now. Is this a known problem or is it just me?
>
> I think that's been broken (or rather "never implemented") since Arno's new
> transform code last winter/spring...
>
> I don't suspect it would be hard to add.  Is there really a need?
> (Leading-tab-delimited lists, I think, are also not currently working in
> 1.3.)
>
>
>
>
>
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa

[Phpwiki-talk] =?iso-8859-1?Q?Re:_[Phpwiki-talk]_3-single_quotes_and_5-single_quotes_broken=3F?=

[Jeff D. <da...@da...>]

Carsten Klapp said:
>
> 3-single-quotes (bold) and 5-single-quotes (bold-italic) seems
> completely  broken now. Is this a known problem or is it just me?

I think that's been broken (or rather "never implemented") since Arno's new
transform code last winter/spring...

I don't suspect it would be hard to add.  Is there really a need?
(Leading-tab-delimited lists, I think, are also not currently working in
1.3.)

Re: [Phpwiki-talk] <code></code> tags [was <pre> tags]

[Adam S. <ad...@pe...>]

> <code> and <pre> are fine by me too. Any thoughts on adding support
> for all three synonyms? It might be useful to be compatible with other
> Wikis, and <pre> might be useful for transferring existing html into a
> Wiki.

supporting <pre></pre> would be useful for cut'n'paste from html but given
that none of the other tags would migrate cleanly i don't see that it's
that big a deal.

as for <nowiki> vs. <code> if we're copying meatball lets just copy them.
what is their recommendation?  we may as well try and make this stuff as
standard as possible between wikis.

adam.

Re: [Phpwiki-talk] <code></code> tags [was <pre> tags]

[Carsten K. <car...@ma...>]

I noticed Meatball Wiki uses <nowiki></nowiki>.

<code> and <pre> are fine by me too. Any thoughts on adding support for 
all three synonyms? It might be useful to be compatible with other Wikis, 
and <pre> might be useful for transferring existing html into a Wiki.

Carsten


On Thursday, December 6, 2001, at 09:42  am, Lawrence Akka wrote:

> I have patched lib/transform.php (cvs as of today) to enable a new 
> formatting rule.
>
> A line beginning <code> will switch wiki formatting off, until a line 
> beginning </code>
>
> It is now easier to cut and paste large chunks of code into a wiki, 
> without all the ['s creating automatic links.
>
> In other words:
>
> test
> <code>
> This is a __wiki test__.  $array['index']
> </code>
> test
>
> will display as
>
> test
>
> This is a __wiki test__. $array['index']
>
> test

[Phpwiki-talk] filenames with underscores: bleah

[Carsten K. <car...@ma...>]

Hi,

Bleah, those ugly underscores in filenames are my Pet-Peeve! Can we =
rename=20
them to spaces or SmashThemTogether instead?

Modern OSes shouldn't have any problems with spaces in filenames, and =
GUIs=20
and shell auto-completion really make it easy to use filenames with =
spaces=20
in them (except perhaps Windows, does it have filename auto-completion =
yet?
)

Carsten
=97a guy who thought he'd never have to type another "_" since retiring =
his=20
Underwood typewriter :-).

[Phpwiki-talk] 3-single quotes and 5-single quotes broken?

[Carsten K. <car...@ma...>]

Hi,

I just pulled down a fresh copy of 1.3 from cvs.

3-single-quotes (bold) and 5-single-quotes (bold-italic) seems completely 
broken now. Is this a known problem or is it just me?

See the bottom of TestPage, Markup Tests and Usage in preformatted text.

Carsten

Re: [Phpwiki-talk] <code></code> tags [was <pre> tags]

[Steve W. <sw...@pa...>]

Aside from the fact that there's a typo in my Javascript... :-)

~swain

On Thu, 6 Dec 2001, Steve Wainstead wrote:

>
>
> Can I do:
>
> <code>
>
> <script language="Javascript">
> alert("hello sailor!);
> </script>
>
> </code>
>
> If so, this is a security breach...
>
> ~swain
>
> On Thu, 6 Dec 2001, Lawrence Akka wrote:
>
> > I have patched lib/transform.php (cvs as of today) to enable a new
> > formatting rule.
> >
> > A line beginning <code> will switch wiki formatting off, until a line
> > beginning </code>
> >
> > It is now easier to cut and paste large chunks of code into a wiki, without
> > all the ['s creating automatic links.
> >
> > In other words:
> >
> > test
> > <code>
> > This is a __wiki test__.  $array['index']
> > </code>
> > test
> >
> > will display as
> >
> > test
> >
> > This is a __wiki test__. $array['index']
> >
> > test
> >
> > I would appreciate feedback on this:
> >
> > *  Is it useful?
> > *  Does it work?
> > *  Should <code></code> be something else?
> > *  Should it go into the cvs?
> >
> > At the moment I am aware of one problem - an extra blank line seems to be
> > inserted after the end of the code
> >
> > Thanks
> >
> > Lawrence Akka
> >
> >
> > Context diff follows:
> >
> >
> > *** transform.old.php	Thu Dec  6 14:21:31 2001
> > --- transform.php	Thu Dec  6 14:29:43 2001
> > ***************
> > *** 1,10 ****
> > ! <?php rcs_id('$Id: transform.php,v 1.27 2001/11/16 22:59:02 dairiki Exp $');
> >    require_once('lib/WikiPlugin.php');
> >
> >    define('WT_SIMPLE_MARKUP', 0);
> >    define('WT_TOKENIZER', 1);
> >    define('WT_MODE_MARKUP', 2);
> > !
> >    define("ZERO_LEVEL", 0);
> >    define("NESTED_LEVEL", 1);
> >
> > --- 1,10 ----
> > ! <?php rcs_id('$Id: transform.php,v 1.4 2001/11/27 10:44:32 lakka Exp $');
> >    require_once('lib/WikiPlugin.php');
> >
> >    define('WT_SIMPLE_MARKUP', 0);
> >    define('WT_TOKENIZER', 1);
> >    define('WT_MODE_MARKUP', 2);
> > ! define('WT_NO_MARKUP', 4);
> >    define("ZERO_LEVEL", 0);
> >    define("NESTED_LEVEL", 1);
> >
> > ***************
> > *** 15,20 ****
> > --- 15,21 ----
> >       var $replacements;	// storage for tokenized strings of current line
> >       var $user_data;	// can be used by the transformer functions
> >                            // to store miscellaneous data.
> > +    var $MarkupEnabled;  // flag to determine whether markup shoud be
> > transformed.  added by LA
> >
> >       // private variables
> >       var $content;	// wiki markup, array of lines
> > ***************
> > *** 27,32 ****
> > --- 28,34 ----
> >       {
> >          $this->trfrm_func = array();
> >          $this->stack = new Stack;
> > +       $this->MarkupEnabled = 1;  // Added by LA
> >       }
> >
> >       /**
> > ***************
> > *** 241,246 ****
> > --- 243,256 ----
> >    	      list($flags, $func, $regexp) = current($this->trfrm_func);
> >    	      next($this->trfrm_func)) {
> >
> > + 	    // if MarkupEnabled is not set then ignore all further markup,
> > + 	    // except WT_NO_MARKUP functions (or we couldn't turn markup
> > + 	    // back on again (!), and wtm_specialchars (to remove html)
> > + 	    // Added by LA
> > +
> > + 	    if (!$this->MarkupEnabled && !($flags & WT_NO_MARKUP) && $func !=
> > 'wtm_htmlchars')
> > + 		continue;
> > +
> >    	    // if HTMLmode is already set then skip all following
> >    	    // WT_MODE_MARKUP functions
> >    	    if ($this->mode_set && ($flags & WT_MODE_MARKUP) != 0)
> > ***************
> > *** 316,321 ****
> > --- 326,332 ----
> >    // register functions
> >    // functions are applied in order of registering
> >
> > + $transform->register(WT_NO_MARKUP, 'wtm_no_markup', '^<code>|^<\/code>');
> > //Added by LA
> >    $transform->register(WT_SIMPLE_MARKUP, 'wtm_plugin_link');
> >    $transform->register(WT_MODE_MARKUP, 'wtm_plugin');
> >
> > ***************
> > *** 643,648 ****
> > --- 654,673 ----
> >       function wtm_paragraph($line, &$trfrm) {
> >          $line = $trfrm->SetHTMLMode('p') . $line;
> >          return $line;
> > +    }
> > +
> > +    // No markup between <code>, </code>.  Added by LA
> > +    function wtm_no_markup($line, &$trfrm) {
> > +        if (preg_match('/^<code>(.*)/', $line, $m)) {
> > +            $trfrm->MarkupEnabled = 0;
> > +            $line = $trfrm->SetHTMLMode('pre').$m[1];
> > +        echo 'on';
> > +        } elseif (preg_match('/^<\/code>(.*)/', $line, $m)) {
> > + 	   $trfrm->MarkupEnabled = 1;
> > + 	   $line = $trfrm->SetHTMLMode('',0).$m[1];
> > + 	   echo 'off';
> > +        }
> > +        return $line;
> >       }
> >
> >    // (c-file-style: "gnu")
> >
> >
> > _______________________________________________
> > Phpwiki-talk mailing list
> > Php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
> >
>
> ---
>                   http://www.panix.com/~swain/
> "Without music to decorate it, time is just a bunch of boring
> production deadlines or dates by which bills must be paid."
>                      -- Frank Zappa
>
>
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa

[Phpwiki-talk] alpha site hosed, fixed

[Steve W. <sw...@pa...>]

Something weird is going on with the nightly rebuilds of the alpha site..
for some reason it's not checking things out of CVS. (This runs on a cron
job).

I'll keep an eye on it. I updated it manually just now and it's fine.

~swain

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa

Re: [Phpwiki-talk] <code></code> tags [was <pre> tags]

[Steve W. <sw...@pa...>]

Can I do:

<code>

<script language="Javascript">
alert("hello sailor!);
</script>

</code>

If so, this is a security breach...

~swain

On Thu, 6 Dec 2001, Lawrence Akka wrote:

> I have patched lib/transform.php (cvs as of today) to enable a new
> formatting rule.
>
> A line beginning <code> will switch wiki formatting off, until a line
> beginning </code>
>
> It is now easier to cut and paste large chunks of code into a wiki, without
> all the ['s creating automatic links.
>
> In other words:
>
> test
> <code>
> This is a __wiki test__.  $array['index']
> </code>
> test
>
> will display as
>
> test
>
> This is a __wiki test__. $array['index']
>
> test
>
> I would appreciate feedback on this:
>
> *  Is it useful?
> *  Does it work?
> *  Should <code></code> be something else?
> *  Should it go into the cvs?
>
> At the moment I am aware of one problem - an extra blank line seems to be
> inserted after the end of the code
>
> Thanks
>
> Lawrence Akka
>
>
> Context diff follows:
>
>
> *** transform.old.php	Thu Dec  6 14:21:31 2001
> --- transform.php	Thu Dec  6 14:29:43 2001
> ***************
> *** 1,10 ****
> ! <?php rcs_id('$Id: transform.php,v 1.27 2001/11/16 22:59:02 dairiki Exp $');
>    require_once('lib/WikiPlugin.php');
>
>    define('WT_SIMPLE_MARKUP', 0);
>    define('WT_TOKENIZER', 1);
>    define('WT_MODE_MARKUP', 2);
> !
>    define("ZERO_LEVEL", 0);
>    define("NESTED_LEVEL", 1);
>
> --- 1,10 ----
> ! <?php rcs_id('$Id: transform.php,v 1.4 2001/11/27 10:44:32 lakka Exp $');
>    require_once('lib/WikiPlugin.php');
>
>    define('WT_SIMPLE_MARKUP', 0);
>    define('WT_TOKENIZER', 1);
>    define('WT_MODE_MARKUP', 2);
> ! define('WT_NO_MARKUP', 4);
>    define("ZERO_LEVEL", 0);
>    define("NESTED_LEVEL", 1);
>
> ***************
> *** 15,20 ****
> --- 15,21 ----
>       var $replacements;	// storage for tokenized strings of current line
>       var $user_data;	// can be used by the transformer functions
>                            // to store miscellaneous data.
> +    var $MarkupEnabled;  // flag to determine whether markup shoud be
> transformed.  added by LA
>
>       // private variables
>       var $content;	// wiki markup, array of lines
> ***************
> *** 27,32 ****
> --- 28,34 ----
>       {
>          $this->trfrm_func = array();
>          $this->stack = new Stack;
> +       $this->MarkupEnabled = 1;  // Added by LA
>       }
>
>       /**
> ***************
> *** 241,246 ****
> --- 243,256 ----
>    	      list($flags, $func, $regexp) = current($this->trfrm_func);
>    	      next($this->trfrm_func)) {
>
> + 	    // if MarkupEnabled is not set then ignore all further markup,
> + 	    // except WT_NO_MARKUP functions (or we couldn't turn markup
> + 	    // back on again (!), and wtm_specialchars (to remove html)
> + 	    // Added by LA
> +
> + 	    if (!$this->MarkupEnabled && !($flags & WT_NO_MARKUP) && $func !=
> 'wtm_htmlchars')
> + 		continue;
> +
>    	    // if HTMLmode is already set then skip all following
>    	    // WT_MODE_MARKUP functions
>    	    if ($this->mode_set && ($flags & WT_MODE_MARKUP) != 0)
> ***************
> *** 316,321 ****
> --- 326,332 ----
>    // register functions
>    // functions are applied in order of registering
>
> + $transform->register(WT_NO_MARKUP, 'wtm_no_markup', '^<code>|^<\/code>');
> //Added by LA
>    $transform->register(WT_SIMPLE_MARKUP, 'wtm_plugin_link');
>    $transform->register(WT_MODE_MARKUP, 'wtm_plugin');
>
> ***************
> *** 643,648 ****
> --- 654,673 ----
>       function wtm_paragraph($line, &$trfrm) {
>          $line = $trfrm->SetHTMLMode('p') . $line;
>          return $line;
> +    }
> +
> +    // No markup between <code>, </code>.  Added by LA
> +    function wtm_no_markup($line, &$trfrm) {
> +        if (preg_match('/^<code>(.*)/', $line, $m)) {
> +            $trfrm->MarkupEnabled = 0;
> +            $line = $trfrm->SetHTMLMode('pre').$m[1];
> +        echo 'on';
> +        } elseif (preg_match('/^<\/code>(.*)/', $line, $m)) {
> + 	   $trfrm->MarkupEnabled = 1;
> + 	   $line = $trfrm->SetHTMLMode('',0).$m[1];
> + 	   echo 'off';
> +        }
> +        return $line;
>       }
>
>    // (c-file-style: "gnu")
>
>
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa

[Phpwiki-talk] Editing area size

[Gary B. <ga...@in...>]

CSS tip of the day:

If you add `style="width:100%"' to the attributes of the EditText textarea
then it expands to fill the width of the screen (no matter what `cols' is 
set to).

Later,
Gary

[ ga...@in... ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ]

[Phpwiki-talk] <code></code> tags [was <pre> tags]

[Lawrence A. <la...@us...>]

I have patched lib/transform.php (cvs as of today) to enable a new 
formatting rule.

A line beginning <code> will switch wiki formatting off, until a line 
beginning </code>

It is now easier to cut and paste large chunks of code into a wiki, without 
all the ['s creating automatic links.

In other words:

test
<code>
This is a __wiki test__.  $array['index']
</code>
test

will display as

test

This is a __wiki test__. $array['index']

test

I would appreciate feedback on this:

*  Is it useful?
*  Does it work?
*  Should <code></code> be something else?
*  Should it go into the cvs?

At the moment I am aware of one problem - an extra blank line seems to be 
inserted after the end of the code

Thanks

Lawrence Akka


Context diff follows:


*** transform.old.php	Thu Dec  6 14:21:31 2001
--- transform.php	Thu Dec  6 14:29:43 2001
***************
*** 1,10 ****
! <?php rcs_id('$Id: transform.php,v 1.27 2001/11/16 22:59:02 dairiki Exp $');
   require_once('lib/WikiPlugin.php');

   define('WT_SIMPLE_MARKUP', 0);
   define('WT_TOKENIZER', 1);
   define('WT_MODE_MARKUP', 2);
!
   define("ZERO_LEVEL", 0);
   define("NESTED_LEVEL", 1);

--- 1,10 ----
! <?php rcs_id('$Id: transform.php,v 1.4 2001/11/27 10:44:32 lakka Exp $');
   require_once('lib/WikiPlugin.php');

   define('WT_SIMPLE_MARKUP', 0);
   define('WT_TOKENIZER', 1);
   define('WT_MODE_MARKUP', 2);
! define('WT_NO_MARKUP', 4);
   define("ZERO_LEVEL", 0);
   define("NESTED_LEVEL", 1);

***************
*** 15,20 ****
--- 15,21 ----
      var $replacements;	// storage for tokenized strings of current line
      var $user_data;	// can be used by the transformer functions
                           // to store miscellaneous data.
+    var $MarkupEnabled;  // flag to determine whether markup shoud be 
transformed.  added by LA

      // private variables
      var $content;	// wiki markup, array of lines
***************
*** 27,32 ****
--- 28,34 ----
      {
         $this->trfrm_func = array();
         $this->stack = new Stack;
+       $this->MarkupEnabled = 1;  // Added by LA
      }

      /**
***************
*** 241,246 ****
--- 243,256 ----
   	      list($flags, $func, $regexp) = current($this->trfrm_func);
   	      next($this->trfrm_func)) {

+ 	    // if MarkupEnabled is not set then ignore all further markup,
+ 	    // except WT_NO_MARKUP functions (or we couldn't turn markup
+ 	    // back on again (!), and wtm_specialchars (to remove html)
+ 	    // Added by LA
+ 	
+ 	    if (!$this->MarkupEnabled && !($flags & WT_NO_MARKUP) && $func != 
'wtm_htmlchars')
+ 		continue;
+ 	
   	    // if HTMLmode is already set then skip all following
   	    // WT_MODE_MARKUP functions
   	    if ($this->mode_set && ($flags & WT_MODE_MARKUP) != 0)
***************
*** 316,321 ****
--- 326,332 ----
   // register functions
   // functions are applied in order of registering

+ $transform->register(WT_NO_MARKUP, 'wtm_no_markup', '^<code>|^<\/code>'); 
//Added by LA
   $transform->register(WT_SIMPLE_MARKUP, 'wtm_plugin_link');
   $transform->register(WT_MODE_MARKUP, 'wtm_plugin');

***************
*** 643,648 ****
--- 654,673 ----
      function wtm_paragraph($line, &$trfrm) {
         $line = $trfrm->SetHTMLMode('p') . $line;
         return $line;
+    }
+
+    // No markup between <code>, </code>.  Added by LA
+    function wtm_no_markup($line, &$trfrm) {
+        if (preg_match('/^<code>(.*)/', $line, $m)) {
+            $trfrm->MarkupEnabled = 0;
+            $line = $trfrm->SetHTMLMode('pre').$m[1];
+        echo 'on';
+        } elseif (preg_match('/^<\/code>(.*)/', $line, $m)) {
+ 	   $trfrm->MarkupEnabled = 1;
+ 	   $line = $trfrm->SetHTMLMode('',0).$m[1];
+ 	   echo 'off';
+        }
+        return $line;
      }

   // (c-file-style: "gnu") 

[Phpwiki-talk] text2png works!

[Carsten K. <car...@ma...>]

Hi All,

The new text2png plugin for 1.3 is working now (yahoo-alright!)

I must say there's some pretty darn brilliant code behind the whole 
Wiki-Plugin architecture! Once I understood how those args were being 
extracted in the plugin class, all my plugin code fell into place.

I've learned a lot about php (and coding in general) in the last few 
months. PhpWiki is amazing.

Thanks
Carsten

[Phpwiki-talk] <pre> tags

[Lawrence A. <Law...@th...>]

I am keen to implement something like <pre></pre> tags for my own use, so that I can 
cut and paste php code into my wiki, between those tags, without all the array 
subscripts turning into links.  [Yes I know I can use [[, but its a bit of a nuisance with 
long blocks of code].

Before I reinvent the wheel, has anyone else done this who is prepared to let me see 
their code?

Thanks

Lawrence Akka--------------------------------------------------------
Confidentiality Notice

The information contained in this e-mail is confidential.  It is for the
use of the named recipient only.  If you are not the named recipient, 
please destroy and do not disclose the contents of this e-mail
to any other person, or copy it.  Thank you for your co-operation.

[Phpwiki-talk] Please add your Wiki to the list

[Steve W. <sw...@pa...>]

I've started a list of sites running PhpWiki:

http://phpwiki.sourceforge.net/phpwiki/PhpWikiSites

which is linked to off the HomePage. Hopefully people will start adding
theirs to the list.

If you browse the links and see some you think are cool, or really active,
perhaps you can put the Wiki's name in bold or italics, so there are
standout Wikis on the list for users to zero in on. Some, like the FreeBSD
Wiki, look really nice.

Also there are a lot of Sourceforge-based PhpWikis. I'd like to think we
are the first choice for a Wiki on Sourceforge, and perhaps we can
circulate a special SourceForge/PhpWiki HOWTO on setting up PhpWiki on SF,
since there are a couple of "gotchas."

(For our non-native-English speaking friends, the term "gotcha" is slang
for "got you!" In programming circles a "gotcha" is a hidden detail that
catches you off guard and causes problems.)

cheers
~swain

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa

[Phpwiki-talk] PhpWiki birthday

[Steve W. <sw...@pa...>]

I forgot to look at the HISTORY file for the exact date; it's December
3rd, 1999 that I had the first piece of PhpWiki working.

Version 1.0 was released on January 25th, 2000. Maybe that's a more
appropriate anniversary?

Congratulations to everyone who's helped PhpWiki along! It's come a long
way in two years.

cheers
~swain

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa

[Phpwiki-talk] Re: PHPwiki website suggestion

[Steve W. <sw...@pa...>]

On Wed, 5 Dec 2001, janice heinold wrote:

> Is there a page on the PHPwiki page that lists implementations of PHPwiki
> "out there"? I mean, other than the Recent Visitors?
>
> I must also say, this is in my opinion the best wiki I have seen on the web.
> I don't know about PHP (I am a designer with a BFA and an understanding of
> HTML and Javascript), but I downloaded the code yesterday afternoon, and am
> planning to do a site with it this morning. Bravo to the developers! Keep it
> up!
>
> Thank you!!
>
> Janice Heinold
> Multimedia Designer
>

Thanks Janice!

I searched for 'phpwiki' on Google just the other night and found a great
many sites out there using it. I thought about putting together a list of
links, and maybe it is time to do that.

Cheers,
~swain


---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa

Re: [Phpwiki-talk] Postnuke module

[Carsten K. <car...@ma...>]

Whoa, the whole PhpWiki as a plugin-module for another web site! It looks 
pretty cool.

The Postnuke "Quote of the Day" and "Polls/Surveys" are good ideas for 
future Wiki Plugins too.

Carsten

On Tuesday, December 4, 2001, at 12:42  pm, Lawrence Akka wrote:

> I have created a module to allow PhpWiki 1.3.1 (and a few subsequent cvs 
> additions) to be used as a module in Postnuke 0.7.  It integrates with 
> the PN permissions/login system and allows fine-grained control over who 
> can see/edit which pages.
>
> You can see it working on Postnuke 0.64 (i.e. without permissions/login) 
> at http://www.docs.grape.dyndns.org  where it is being used to help 
> create the PostNuke documentation.  It will shortly be installed on PN 0.
> 7 at http://support.postnuke.com
>
> There is no released package yet, but the files are available via 
> anonymous cvs at http://cvs.sourceforge.net/cgi-
> bin/viewcvs.cgi/pn-modules/modules_development/phpWiki/
>
> Lawrence Akka

Re: [Phpwiki-talk] UserPage: an alternative to the ugly HTTP authorization window

[Carsten K. <car...@ma...>]

I think your UserPage plugin is a super-fine idea (and you're definitely 
further along with it than I was with my SetPrefs plugin).

How ugly the HTTP authorization window is depends I suppose on which 
browser/OS you are using. :-P

I like the idea that once logged in the UserPage shows all the preference 
fields, but should skip it when the login was triggered by an EditPage 
click. Probably this can be easily setup with an appropriate redirect.

I understand it's not working fully yet until the other changes can be 
made, so this might not even be relevant. I do like to see all the 
preferences stored in a (user-readable & editable) cookie rather than 
adding extra data such as the username onto the URL field, to keep the URL 
clean as possible.

:-)

Carsten


On Tuesday, December 4, 2001, at 10:40  am, Joe Edelman wrote:

> A few days ago I checked in a plugin that provides an alternate sign-in
> mechanism.  It's a clone of the sign-in pages at http://why.clublet.com.
>
>
> 1. WHAT IT DOES
>
> When you click "edit" and you're not signed in, you get a page like:
>
>     Before you can edit PageYouWantToEdit, you need to sign in.
>
>     Please enter your name as WordsStrungTogether (i.e. John Smith as
> JohnSmith):
>
>     Sign in:  [                     ]    (Sign In)
>
> And if you type something that isn't a WikiWord in the sign-in box, it 
> gives
> you more help.
>
>
> 2. YOU CAN TRY IT
>
> You can try it out on a clean check out by:
>
> (a) creating a new page UserPage with the contents: "<?plugin UserPage?>"
> .
> (b) visiting a url like "index.php?UserPage&edit=HomePage" while you're 
> not
> signed in.
>
>
> 3. WHERE IT'S GOING
>
> I would like to have UserPage take over preferences, too:  if someone goes
> to UserPage who's already signed in, they'll get their preferences page. 
> It
> will also collect email addresses and add them as metadata to a user's 
> home
> page.  It may also present a line indicating that they should make a wiki
> page if they don't have one, and it will probably eventually support
> passwords as well.  It will also offer new users a special intro page.
> These will all be switchable options changed by editing the plugin call.
> The UserPage at clublet.com does all of these things.
>
>
> 4. ISSUES
>
> (a) It currently uses a private method of WikiUser!!!  (_save())   Jeff, 
> can
> I make this public?
> (b) It needs to be gettext()ified.
>
>
> 5. MIGRATION
>
> If the consensus is that this should be the auth mechanism of PhpWiki
> out-of-box, the following things need to be changed:
>
>     (a) templates need to point to it for edit & sign in.
>     (b) LinkUnknownWikiWord needs to point to it
>     (c) editpage should check auth & a global option and redirect if the
> user isn't signed on
>
>
> Thoughts?
>
>
>
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>

[Phpwiki-talk] BUGFIX 1.3: schemas

[Carsten K. <car...@ma...>]

Found a small problem with the schema files while setting up a new 
database for 1.3.

My mysql-3.23.44 doesn't like it when there are only tabs inside the table 
definitions, at least one space is needed. Tabs at the beginning of each 
line are OK.

good:
CREATE TABLE page (
[tab]id[space][tab][tab]INT NOT NULL,

bad:
CREATE TABLE page (
[tab]id[tab][tab]INT NOT NULL,

The file schemas/mysql.sql has been fixed, and minisql.sql looks fine 
(only 2 tabs but at the beginning of the line). There are still tabs 
inside psql.sql, someone should test it to make sure the tabs don't 
interfere.

If tabs do cause a problem in psql.sql, it is probably fixed by just 
inserting a space before each tab, or convert all tabs to spaces.

Is it possible to put in some kind of a comment line as a reminder into 
each schema file, without it causing problems for the database?

Carsten

[Phpwiki-talk] URGENT: BUG FIXED in 1.2 CVS, caused on Dec 2

[Carsten K. <car...@ma...>]

Today I discovered and fixed a HUGE bug in the 1.2 branch, which I 
inadvertently caused on December 2 and 3. :-(

Everyone who downloaded from the 1.2 branch CVS on or after December 2 
should download the fixed version of stdlib.php from the CVS AS SOON AS 
POSSIBLE.

**********************************************************

The bug was created when I added the split_pagename function (and the 
optional autosplit wikiwords).

The problem occurs when clicking on any "EditPage". After saving the page,
  the new data would be incorrectly saved with a space in the page name. So,
  if you were editing "TestPage" a NEW page would be added called 
"Test%20Page".

If you DID NOT download PhpWiki 1.2 on or after Dec 2. then you will not 
be affected.
If you are not sure, there is a way to determine whether your data has 
been affected by this bug:

1. Open /lib/stdlib.php. search for "split_pagename".
2. If you find this function in your stdlib file then you are probably 
affected.

To determine the extent of the damage:

1. Perform a ZIP dump of your phpwiki database
2. Open the ZIP file, and look for duplicate pages, ones without %20 in 
the name and the same page name again with %20.

Unfortunately one cannot do a title search for " " or %20.

If you do have duplicate pages, the %20 version will be the most recent 
version.

To fix the affected pages:

1. Download the corrected stdlib.php from the CVS.
2. Edit the affected page(s) (e.g. Test%20Page)
3. Copy all the text
4. Edit the correct page (e.g. TestPage)
5. Paste in all the text
6. Delete the bugged page (e.g. Test%20Page)
7. Repeat for all affected pages.

I am sorry for any problems this has caused. Please contact me if this bug 
caused you problems, I will do my best to help fix it.

Carsten Klapp
car...@ma...

[Phpwiki-talk] Postnuke module

[Lawrence A. <la...@us...>]

I have created a module to allow PhpWiki 1.3.1 (and a few subsequent cvs 
additions) to be used as a module in Postnuke 0.7.  It integrates with the 
PN permissions/login system and allows fine-grained control over who can 
see/edit which pages.

You can see it working on Postnuke 0.64 (i.e. without permissions/login) at 
http://www.docs.grape.dyndns.org  where it is being used to help create the 
PostNuke documentation.  It will shortly be installed on PN 0.7 at 
http://support.postnuke.com

There is no released package yet, but the files are available via anonymous 
cvs at 
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/pn-modules/modules_development/phpWiki/

Lawrence Akka
(pleased that he has got rid of his very long sig at last!)

[Phpwiki-talk] UserPage: an alternative to the ugly HTTP authorization window

[Joe E. <jo...@or...>]

A few days ago I checked in a plugin that provides an alternate sign-in
mechanism.  It's a clone of the sign-in pages at http://why.clublet.com.


1. WHAT IT DOES

When you click "edit" and you're not signed in, you get a page like:

    Before you can edit PageYouWantToEdit, you need to sign in.

    Please enter your name as WordsStrungTogether (i.e. John Smith as
JohnSmith):

    Sign in:  [                     ]    (Sign In)

And if you type something that isn't a WikiWord in the sign-in box, it gives
you more help.


2. YOU CAN TRY IT

You can try it out on a clean check out by:

(a) creating a new page UserPage with the contents: "<?plugin UserPage?>".
(b) visiting a url like "index.php?UserPage&edit=HomePage" while you're not
signed in.


3. WHERE IT'S GOING

I would like to have UserPage take over preferences, too:  if someone goes
to UserPage who's already signed in, they'll get their preferences page. It
will also collect email addresses and add them as metadata to a user's home
page.  It may also present a line indicating that they should make a wiki
page if they don't have one, and it will probably eventually support
passwords as well.  It will also offer new users a special intro page.
These will all be switchable options changed by editing the plugin call.
The UserPage at clublet.com does all of these things.


4. ISSUES

(a) It currently uses a private method of WikiUser!!!  (_save())   Jeff, can
I make this public?
(b) It needs to be gettext()ified.


5. MIGRATION

If the consensus is that this should be the auth mechanism of PhpWiki
out-of-box, the following things need to be changed:

    (a) templates need to point to it for edit & sign in.
    (b) LinkUnknownWikiWord needs to point to it
    (c) editpage should check auth & a global option and redirect if the
user isn't signed on


Thoughts?

Re: [Phpwiki-talk] Is 1.2 still feature frozen?

[Steve W. <sw...@pa...>]

Generally, yes. I am open to user-contributed patches, but I don't want to
expend any developer time on it (yours or mine).

~swain

On Mon, 3 Dec 2001, Jeff Dairiki wrote:

> Is our policy still that 1.2.x is under (more or less of) a "feature
> freeze".
> (Bug and compatibility fixes only?)
>
> (My vote: yes.)
>
> Jeff
>
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa