phpwiki-talk

Re: [Phpwiki-talk] New jeffshacks snapshot.

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

> I've put a new snapshot up.  Demo and pointer to code at:
>
>   http://phpwiki.sourceforge.net/jeffs-hacks/wiki/

this is great!  any chance of making categories meta data which is
selected via drop box on the edit page?  and maybe a similar thing for
sub-categories?  i know it kinda breaks the wiki ideal but i think it's
going to become increasingly useful as wiki's increase in complexity.

also are comments (ie. they show up in the edit box but not on the actual
wiki page) a possibility?

this is looking really really good guys, great stuff.

adam.

Re: [Phpwiki-talk] New jeffshacks snapshot.

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

I've put a new snapshot up.  Demo and pointer to code at:

  http://phpwiki.sourceforge.net/jeffs-hacks/wiki/

Jeff

[Phpwiki-talk] ftp services ending

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

Just a note that Sourceforge is discontinuing FTP services in favor of
their home-brewed download system.

I've moved the files out of our FTP directory as needed and updated the
FrontPage of the main site.

~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
http://pgp.document_type.org:11371/pks/lookup?op=get&search=0xF7323BAC

Re: [Phpwiki-talk] September 11

[Reini U. <ru...@x-...>]

Marjorie Roswell schrieb:
> I sincerely hope that all in the phpwiki community came out of yesterday's events unscathed.
> Steve Wainstead, for instance: You're in NY, right? Are you okay?

> Check out http://www.uwnyc.org/other/index.html

This crashed my netscape browser. I used
http://www.paypal.com/cgi-bin/webscr?cmd=p/gen/relief-outside

He lives West 34th and works at NYTD, 500 7th ave, which is very close, so he
should be quite safe.
http://mapsonus.switchboard.com/bin/maps-mapspec/?AddrStreetLine=500+Seventh+Avenue&AddrCityLine=NY+10018

But a lot of NYC routers are off-line. Or there's a lot of other more
important 
things to do.

anyway, my ignorable political statement here: 
  "please us troops, go out of saudi-arab and don't go into afghanistan. 
   this was the reason for the whole mess.
   nobody enyoys to have guests for the wedding party who don't leave after
three weeks."
   http://parallelinfo.mur.at/

RE: [Phpwiki-talk] September 11

[Pablo R. <pr...@cl...>]

> Steve Wainstead, for instance: You're in NY, right? Are you okay?

Oh .. Dawn! ... I expect yes ..

Saludos,

Pablo Roca


> -----Mensaje original-----
> De: php...@li... 
> [mailto:php...@li...] En nombre 
> de Marjorie Roswell
> Enviado el: jueves, 13 de septiembre de 2001 0:43
> Para: php...@li...
> Asunto: [Phpwiki-talk] September 11
> 
> 
> I sincerely hope that all in the phpwiki community came out 
> of yesterday's events unscathed. 
> 
> Steve Wainstead, for instance: You're in NY, right? Are you okay?
> 
> Check out
> http://www.uwnyc.org/other/index.html
>  or
> https://www.uwnyc.com/epledge/sept11.cfm
> 
> For one way to help out.
> 
> Sincerely,
> 
> Margie
> Baltimore, MD
> 
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
> 

[Phpwiki-talk] Re: MySQL stuff

[Marjorie R. <mro...@ma...>]

---------- Original Message ----------------------------------
From: Gary Benson <ga...@in...>
>Marjorie, did anyone ever answer your MySQL query from the other day?

No. Probably a difficult one to respond to, because it was a little rambly, but it's still "open." Thanks for asking.

>Gary

Re: [Phpwiki-talk] (no subject)

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

Hi Marjorie,

I'm assuming here, that you're currently running version 1.2.0 (with 
the dba or dbm backend.)  If that's not the case, ask again...

> How do I ensure that when I switch to MySQL I don't lose anything?

Make a zip dump (or a "serialized page" dump) of your wiki.  (See 
below.)

> How do I run the zip program?

If you mean "how to a get a zip dump of my phpwiki?", here's how.
(Again, assuming phpwiki 1.2.0.)

(Before this will work, you must set an admin username and password
in admin.php.)
 
You should browse to the PhpWikiAdministration page, in admin mode.  The
appropriate URL is something like:
  http://your.domain/path/admin.php?PhpWikiAdministration
There, near the top, you'll see two links labeled  "ZIP Snapshot"
and "ZIP Dump".  Click on one of them.  (A "snapshot" contains only 
the most recent version of each page in the wiki, while a "dump"
contains the archived version of each page as well.) 

Hopefully your browser will have offered to save a file for you.
(Name it <something-or-other>.zip.)

Now, to be paranoid, you might want to examine the zip file you just
produced to make sure that it does indeed look like it contains
the pages of your wiki.

(On unix systems, you can use the programs 'zipinfo' and 'unzip' to 
examine
the zip file.  On windows systems there are any number of programs you
can use.)

> What is a "serialize()" page?

As an alternative to zip dumping, you can serialize dump.  This writes
the contents of each page (current version only) into a directory
ON THE SERVER, one file per page.  PHP's serialize() function is used
to encode the pages meta-data (like the page author, and time
of last edit) as well and the pages content into the file.

> Which of these files do I interact directly with? For instance, the admin.php script takes care of the lockpage, but doesn't seem to mention anything about the zip file.
> 


In 1.2.0, you don't call any of those directly, admin.php does it for 
you.

...
> admin/zip.php3:

Uhoh. In 1.2.0, this is called admin/zip.php.  Maybe you're not running 
1.2.0?
If so, let me know which version, and I'll see if I can figure out the 
answer.


> I sincerely see a need for better documentation with this (in many areas), and I'd be happy to help, but I've got to "get it" first, myself.

Yes.

> I tried 
> http://my.domain/admin/wiki_dumHTML.php

wiki_dumpHTML.php is nothing but a skeleton of some planned future 
enhancement.
Just ignore it.

> Honestly trying, and honestly a phpwiki fan, albeit a somewhat frustrated one,

Sorry....


And here's the answer to your next question:

What do I do with the zip dump (or the directory full of serialized 
pages)?

If you're just changing backends, probably the cleanest thing to do is
to edit lib/config.php and set WIKI_PGSRC to point to your
zip dump (you'll have to copy the zip file back to the server...).
(For loading serialized pages, set WIKI_PGSRC to point to the directory
containing the serialized pages.)

Then, wipe your backend completely.  And then try to browse your
FrontPage.  Hopefully, phpwiki will load all the pages from whatever
source your set WIKI_PGSRC to point to, and you're back in business.

The other option (if you don't want to wipe the database completely)
is to use the "Load serialized pages" form on PhpWikiAdministration.
You can enter either the path to a zip-dump file (on the server)
or a path to a directory of serialized pages in that form...


Jeff

[Phpwiki-talk] (no subject)

[Marjorie R. <mro...@ma...>]

How do I ensure that when I switch to MySQL I don't lose anything?

How do I run the zip program?

What is a "serialize()" page?

Which of these files do I interact directly with? For instance, the admin.php script takes care of the lockpage, but doesn't seem to mention anything about the zip file.

admin/:
admin/dumpserial.php:        dump the Wiki out as serialize() pages
admin/loadserial.php:        load Wiki pages that were dumped with dumpserial
admin/lockpage.php:          lock a page so it cannot be edited
admin/shrinkdbm.pl:          Perl script to reduce size of DBM files
admin/wiki_dumpHTML.php:     dump the Wiki out as HTML pages
admin/wiki_port1_0.php:      import a 1.0 PhpWiki database
admin/wiki_rebuilddbms.php:  rebuild DBM files to reclaim disk space
admin/zip.php3:              create a Zip archive of all Wiki pages


I sincerely see a need for better documentation with this (in many areas), and I'd be happy to help, but I've got to "get it" first, myself.

I tried 
http://my.domain/admin/wiki_dumHTML.php

and I got 
-----
Dump HTML called.
Got: 
------------

can't find any html pages.

hmmmmm....


Honestly trying, and honestly a phpwiki fan, albeit a somewhat frustrated one,

Margie

[Phpwiki-talk] September 11

[Marjorie R. <mro...@ma...>]

I sincerely hope that all in the phpwiki community came out of yesterday's events unscathed. 

Steve Wainstead, for instance: You're in NY, right? Are you okay?

Check out
http://www.uwnyc.org/other/index.html
 or
https://www.uwnyc.com/epledge/sept11.cfm

For one way to help out.

Sincerely,

Margie
Baltimore, MD

Re: [Phpwiki-talk] Tables in Phpwiki 1.2

[<sjm...@ya...>]

 --- "Philip J. Hollenback" <ph...@ho...> wrote: 
> Check the mailing list archive - there was a patch posted just a month
> or two ago which added table support to phpwiki.

The only one I could find is
http://www.geocrawler.com/archives/3/4037/2000/7/0/4102765/
which is quite old (July 2000). Also the patch is truncated in the archives so
if this is the patch you meant then would you mind sending me a copy if you
have one.

Thanks,

Steven Murdoch.

=====
Some mail programs use the incorrect email address in replies, so please ensure that any emails for me are sent to st...@mu...

____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie

[Phpwiki-talk] Tables in Phpwiki 1.2

[Andrew B. - S. Uk - N. - S. E. <And...@Su...>]

> I just installed PHPWiki on my website (http://www.murdomedia.net/phpwiki/) 
and
> I think it is great. Thanks for all the work you have put into it.
> 
> My question is whether it is possible to put tables into PHPWiki 1.2 pages,
> without having to upgrade or enable HTML.

I'm not a PHPWiki developer but the 'draw your own' tables feature is something 
that I use. I would normally avoid development branches but I run the 1.3.x 
branch and find it stable.

Thanks to all the team for a great script.
Andy

[Phpwiki-talk] Does the INSTALL.mysql file tell all?

[Marjorie R. <mro...@ma...>]

Hello,

I spent a gazillion hours, as a frustrated sort-of newbie, unable to create the mysql database. 

Seems to me that the directions should add "CREATE" permissions along with the select, insert, update, and delete that are provided in the INSTALL.mysql.

Am I right about that?

Even when I tried to update my username with these permissions, my grant statement didn't work (for hours, and hours of trying every which possibility.) I think I might've gotten it, though I finally ended up with the lovely username "testnew."

I have a lot of questions, etc, but this is just an ode to how hard it is not be an expert in something. Things that are completely trivial to an expert can take hours and hours, or days, or weeks, for a newbie...

Ah well, we shall see. I do aim for a sense of mastery in linux, apache, mysql, and php, but only time will tell....

The neighbor says that everything2 is cooler than phpwiki, by the way. Any thoughts on that? This somehow seemed more manageable to me (notwithstanding the last 7 hours!).

What is the real benefit of moving the phpwiki to mysql, anyhow? Will it be faster than the default DBM system? 

Best Regards,

Margie-near-midnight, and smart enough to know that I should wait until a different day to try to actually upgrade my wiki, for fear of losing it all. 

Note: Steve, thanks VERY MUCH for your helpful reply before I found this listserv. 

[Phpwiki-talk] [PATCH] RecentChanges cleaner

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

[sorry if this is the second time you get this; I just remembered how
draconian sourceforge's spam filters are and subscribed to the list before
sending this one]

Hi guys,

Not sure if this will be useful or not (I'm not up to date with the CVS
versions) but here is a patch to phpwiki-1.2.0 to remove empty slots on
RecentChanges whenever a page is saved.

Hope it's useful,
Gary

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


--- phpwiki-1.2.0/lib/savepage.php	Thu Jan  4 18:30:32 2001
+++ phpwiki/lib/savepage.php	Tue Sep 11 00:00:22 2001
@@ -69,7 +69,19 @@
          }
       }

-      $recentchanges['content'] = $newpage;
+      // copy the new page back into recentchanges, skipping empty days
+      $numlines = sizeof($newpage);
+      $recentchanges['content'] = array();
+      $k = 0;
+      for ($i = 0; $i < $numlines; $i++) {
+         if ($i != $numlines-1 &&
+             preg_match("/^____/", $newpage[$i]) &&
+             preg_match("/^[\r\n]*$/", $newpage[$i+1])) {
+            $i++;
+         } else {
+            $recentchanges['content'][$k++] = $newpage[$i];
+         }
+      }

       InsertPage($dbi, gettext ("RecentChanges"), $recentchanges);
    }

[Phpwiki-talk] [PATCH] RecentChanges cleaner

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

Hi guys,

Not sure if this will be useful or not (I'm not up to date with the CVS
versions) but here is a patch to phpwiki-1.2.0 to remove empty slots on
RecentChanges whenever a page is saved.

Hope it's useful,
Gary

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


--- phpwiki-1.2.0/lib/savepage.php	Thu Jan  4 18:30:32 2001
+++ phpwiki/lib/savepage.php	Tue Sep 11 00:00:22 2001
@@ -69,7 +69,19 @@
          }
       }

-      $recentchanges['content'] = $newpage;
+      // copy the new page back into recentchanges, skipping empty days
+      $numlines = sizeof($newpage);
+      $recentchanges['content'] = array();
+      $k = 0;
+      for ($i = 0; $i < $numlines; $i++) {
+         if ($i != $numlines-1 &&
+             preg_match("/^____/", $newpage[$i]) &&
+             preg_match("/^[\r\n]*$/", $newpage[$i+1])) {
+            $i++;
+         } else {
+            $recentchanges['content'][$k++] = $newpage[$i];
+         }
+      }

       InsertPage($dbi, gettext ("RecentChanges"), $recentchanges);
    }

Re: [Phpwiki-talk] New jeffshacks snapshot.

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

On Sep 10, 2001, Adam Shand said:
>
> this is really nice!  great work.

Thanks!


> two bug reports (that i'm sure you already know about):
> 
>  * it says log in with any username/password but it wouldn't let me.  i
>    just kept getting the auth box pop up again until i selected "Cancel"
>    when it told me i had an invaled user/password.

Yes.  This is browser dependent, and has to do with whether your
browser accepts new cookies as part of a "401 Access Denied"
response.  (Mozilla doesn't, NS4 does...)   I have fixed this
in my latest version by using PHP sessions rather than cookies
to store the login state -- but that's a kludge, too.

Using HTTP authentication to query for usernames and passwords that
we, the PHP app,  process is all a big hack in the first place.
I plan on doing away with that soon...

>  * at the bottom of the page there is an error:
> 
>    In template:82: Notice[8]: Undefined variable: RELATEDPAGES:
>        <small>${RELATEDPAGES}</small>

Yes that's just to remind me that I haven't implemented methods
for indexing RelatedPages (or some replacement for it) in the
new database API yet.

I suppose I should just put it on a TODO list instead  :-)

Jeff

Re: [Phpwiki-talk] New jeffshacks snapshot.

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

> I've been playing with the style sheets, so the look has changed quite
> a bit.  I haven't tested my stylesheet hacks at all with IE yet (only
> Netscape and Mozilla) so it could well be unreadable with IE at this
> point.

this is really nice!  great work.  two bug reports (that i'm sure you
already know about):

 * it says log in with any username/password but it wouldn't let me.  i
   just kept getting the auth box pop up again until i selected "Cancel"
   when it told me i had an invaled user/password.

 * at the bottom of the page there is an error:

   In template:82: Notice[8]: Undefined variable: RELATEDPAGES:
       <small>${RELATEDPAGES}</small>

i'm getting exciting about migrating to phpwiki!  keep up the good work
guys.

adam.

[Phpwiki-talk] Tables in Phpwiki 1.2

[<sjm...@ya...>]

Hi All,

I just installed PHPWiki on my website (http://www.murdomedia.net/phpwiki/) and
I think it is great. Thanks for all the work you have put into it.

My question is whether it is possible to put tables into PHPWiki 1.2 pages,
without having to upgrade or enable HTML.

I'd like to stick with the stable version since I am just a beginner and the
people who are using the site would like to insert tables, but HTML is too much
for them. I've seen the table implementation in the alpha site and it looks
really good, is it possible to bring just that feature into a 1.2 wiki?

Thanks in advance,
Steven Murdoch.

=====
Some mail programs use the incorrect email address in replies, so please ensure that any emails for me are sent to st...@mu...

____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie

Re: [Phpwiki-talk] Page scoring.

[Reini U. <ru...@x-...>]

Steve Wainstead schrieb:
> Why 80 columns? Readability again. The reason magazines and newspapers
> print in columns is because the human brain can best read lines that are
> 6-8 words long. Anything shorter or longer slows down the reading process
> considerably.

well said! 
And I though I was the only one who knew this :) (but you worked for a
newspaper)

Layouters and fast-readers even count in eye-hops, where a hop is a word or 
a easy to identify group of words. You normally read in 3-5 hops and can 
train up to 5-6 hops.
80 chars for reading is a pretty large number for readers, but okay 
for programmers.

in my current php project people don't do any linebreaks, but my emacs does. 
so I don't care.

like:            <td align="right"><br><form name="search" <? echo 'action="'
. tep_href_link(FILENAME_ADMIN_USERS, tep_get_all_get_params(), 'NONSSL') .
'"'; ?> method="get"><?php echo
tep_span_class("smallText",'','&nbsp;'.HEADING_TITLE_SEARCH . '&nbsp;<input
type="text" name="search" value="'. $HTTP_GET_VARS['search'] . '"
size="8">&nbsp;' . tep_image_submit(DIR_WS_IMAGES . 'button_search.gif',
IMAGE_SEARCH)); ?></form></td>
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] New jeffshacks snapshot.

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

I've put a new jeffshacks snapshot up.

The new pgsql is working.
Deletion of old archived revisions is implemented.

I've been playing with the style sheets, so the look has changed
quite a bit.  I haven't tested my stylesheet hacks at all with IE yet 
(only
Netscape and Mozilla) so it could well be unreadable with IE at
this point.

A live demo is up at:
  http://phpwiki.sf.net/jeffs-hacks/wiki/

A tar-ball of the source code can be found at:
  http://phpwiki.sf.net/jeffs-hacks/files/

Jeff

Re: [Phpwiki-talk] tab-width

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

Just to clarify, the php-mode tab-width setting does not affect how
far blocks of code are indented (c-basic-offset controls that, and
I'm not suggesting changing that).

The tab-width setting (in combination with indent-tabs-mode (see below))
just controls how emacs achieves that indentation.  If tab-width is
set to 4 (as PEAR dictates), then emacs assumes that a tab character
in the text moves to the next multiple of 4 columns.    The problem with
this, is that most text file viewers assume that a tab moves to the
next multiple of 8 columns, so code which looks fine when viewed
with a tab-width setting of 4 can look severely mangled when viewed
with other programs.

> I actually rangled over this for some time with some programmer friends. I
> think I posted a link to this list that was something written by jwz about
> why you should not use tabs at all. It was pretty sound.

Yes, I agree.  Setting indent-tabs-mode to 'nil forces php-mode not to
use tabs at all, and just indent with spaces.  This is good.

The problem is that unless great care is taken to eliminate all tabs
in the source code, some tabs will remain.  When indentation is
achieved with a mixture of spaces and tabs, then things get particularly
badly munged when viewed by a viewer with a different idea of what the
tab-width is.


I think the intention of the PEAR standards is that indentation be 
achieved using only tabs.  This allows individuals to adjust
the displayed indentation just by changing the tab-width.
The problem is that even when tab-width == c-basic-offset, emacs
does not really guarantee that all indentation is achieved using
tabs rather than spaces.

If you use, e.g. 'less' to view the PEAR source code (at least
the version I've got) the problem will be immediately obvious.
In general, most blocks are indented 8 columns (since tabs were
used) --- that's ugly and hard to read as you point out, but at least
the indentation still properly shows the block structure.
However some lines in the PEAR code are indented with spaces.
Those lines only shift blocks over four columns.  The result
is that nothing lines up with anything.

Re: [Phpwiki-talk] PhpWiki does not survive a slashdot

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

On Sat, 1 Sep 2001, Jon =C5slund wrote:

> My Shakespeare Programming Language web page (built using PhpWiki) did
> just get slashdotted. The web server died hard, very quickly. :)

yes, Wikis do not scale :-)

The only viable solution I see is to generate the Wiki as flat files
(HTML) for browsing. (Even being slashdotted will kill a flat file server
though). PhpWiki+MySQL being slashdotted? fuhgettaboutit!

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
http://pgp.document_type.org:11371/pks/lookup?op=3Dget&search=3D0xF7323BAC

Re: [Phpwiki-talk] Page scoring.

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

Finally getting around to this thread... :-)

On Sun, 2 Sep 2001, Jeff Dairiki wrote:

> Anyhow, as I said, I never use the "5 best incoming/outgoing links".
> Does anyone?

I don't, though occasionally it's interesting to look at. I think this
info should be moved off to some kind of "meta" page, or perhaps something
in the Info link.

It's always refreshing to go back to c2.com and see how clean and simple
the interface is; personally the only thing I'd change clicking on the
title search to find all pages linking to the one you're looking at, since
it's not intuitive, but that's a small thing.

>
> PS:  Anybody have any preferences on the tab-width=4 vs tab-width=8
> issue?  If no one says anything I'm going to start using tab-width=8,
> 'cause thats my preference....

I actually rangled over this for some time with some programmer friends. I
think I posted a link to this list that was something written by jwz about
why you should not use tabs at all. It was pretty sound.

I don't have the greatest eyesight in the world. I use a font size of 12
in Emacs on a 19" monitor, and I can read quite well. With indents of 8
spaces, the code will quite often wrap around and will look like a total
mess. I could go to an 8 pt font, but I will get eye strain.

Originally I went for 2 or 3 spaces indenting. 4 seems too much to me :-)
Also, I don't think code should extend beyond 80 columns, which is why you
always see me doing crap like:

$query = "select foo from bar "     .
         "where blah='blippy' and " .
         "bar=42 sort by ascending";

Why 80 columns? Readability again. The reason magazines and newspapers
print in columns is because the human brain can best read lines that are
6-8 words long. Anything shorter or longer slows down the reading process
considerably.

My 2 cents. I think the PEAR guidelines are good ones.

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
http://pgp.document_type.org:11371/pks/lookup?op=get&search=0xF7323BAC

[Phpwiki-talk] hey (fwd)

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

Just sharing some nice words from a user...

~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
http://pgp.document_type.org:11371/pks/lookup?op=get&search=0xF7323BAC
---------- Forwarded message ----------
Date: Sat, 08 Sep 2001 13:50:55 -0500
From: ~CG~ <con...@ex...>
To: Steve Wainstead <sw...@pa...>
Subject: hey

I *know* you're like, "Good Lord, what is she emailing me about now!"

However, I wanted to drop you a line to see what we're up to with PHPWiki...

http://www.exit-23.net/hunters/
http://www.exit-23.net/amongus/auwiki/index.php
http://www.exit-23.net/mutanthigh/mhwiki/phpwiki/index.php

I currently have plans to convert Exit-23 (http://www.exit-23.net)
completely over to wiki and also to start a knowlege base for the
roleplaying community there.

Thank you so much for your help and your genius!


~CG~
--------------------
http://www.exit-23.net
--------------------
"Mix in a little rectal surgery and it's my best day ever." -- Xander, BtVS

Re: [Phpwiki-talk] tab-width and new database API

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

Wups... I thought I sent this to phpwiki-talk, but apparently I sent it
only to Pablo...  Here it is:
======

On Sep 5, 2001, "Pablo Roca" said:
> Hum curious, why is needed a new template engine?

Well, in the process of munging my new database API into the rest of
the code PhpWiki I had to modify the browse.html and editpage.html
templates.  It bothered my again (it has always bothered me)
that template syntax was ugly and unnecessarily inflexible.

So I rewrote the template engine.  I wrote a real parser to deal with
the if blocks, with the idea of eventually adding some kind of loop
structure.  Added a way to automatically LinkExistingWikiWord,
so that "<a class="wikilink" href="###BROWSE###FindPage"><span 
class="wikiword">FindPage</span></a>" could be written more legibly.

Then, I discovered that PHP4 has this set of ob_* commands which allow
one to capture the "standard output" into a variable.  This is great,
I think, as it allows for templates to be regular php code.
So I tossed my new template engine and replaced it with a new one
which essentially just include()s the template, capturing it's output
to a variable using the ob_* stuff.  (All this refactoring explains
why the current version is, at this point, pretty ugly itself.
It's a mish-mash of the original GeneratePage code, code from my first
template engine, and the current one.  As I said, it still needs
refactored.)

> Let us know when this is available for seeing.

I'll do it now, sorry.  When it's up it'll be at
 http://phpwiki.sourceforge.net/jeffs-hacks/wiki/

> > A tar-ball can be found in:
> >   ftp://www.dairiki.org/phpwiki/
> 
> I can' connect to this server I get an error. ... :(

Yes, my virtual host seems to be unreachable.  Crap.

Try: http://phpwiki.sf.net/jeffs-hacks/files/

Cheers,
Jeff

RE: [Phpwiki-talk] tab-width and new database API

[Pablo R. <pr...@cl...>]

> * New database API.  See lib/WikiDB.php and

Cool

> * Plugins.  See pgsrc/WikiPlugin ...

Plugins? Oh, I can't wait to download the tarbal. :)

> * New template engine.

Hum curious, why is needed a new template engine?

> Perhaps I'll set up a demo wiki later tonight.

Let us know when this is available for seeing.

> A tar-ball can be found in:
>   ftp://www.dairiki.org/phpwiki/

I can' connect to this server I get an error. ... :(

Saludos,

Pablo Roca