phpwiki-talk

Re: [Phpwiki-talk] archiving for PostgreSQL

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

On Wed, 18 Jul 2001, Joel Uckelman wrote:

> When I added the code for page versioning, I broke support for everything
> except MySQL, so now I'm trying to bring the other db formats up to speed.
> Perhaps the changes I just committed in lib/pgsql.php and

Oh, don't worry. We are going to switch to a generic DBMS interface --
either PEAR's DB or the dbx functions -- quite soon. Perhaps even tonight
if I stay in and hack. I have done some rudimentary testing with the dbx
stuff and it works fine. DB is a much larger hoop to jump through.

We will gain two big things: only one database interface to support, and
multiple databases will now be supported. I'm leaning towards PEAR/DB at
the moment since it's more developed, supports more databases and PEAR
looks like the way to go right now.

> Also, it's been bugging me for a long time that we have a directory called
> "schemas" when the proper plural of "schema" is "schemata". How do I go
> about changing that?

I'll look into it. The shortest route is to just cvs remove schemas and
cvs add schemata. The grammar error is mine.

~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] archiving for PostgreSQL

[Joel U. <uck...@no...>]

When I added the code for page versioning, I broke support for everything 
except MySQL, so now I'm trying to bring the other db formats up to speed. 
Perhaps the changes I just committed in lib/pgsql.php and 
schemas/schema.mysql mean that PostgreSQL support works again, but I don't 
know since it's not installed on the box on which I do development. If 
there's anybody out there who'd be willing to grab the current CVS version, 
test it with PostgreSQL, and complain at me about how it doesn't work at 
all, that would be a big help. (Actually, I think it's quite close to 
working, if not as-is.)

Also, it's been bugging me for a long time that we have a directory called 
"schemas" when the proper plural of "schema" is "schemata". How do I go 
about changing that?

-- 
J.

Re: [Phpwiki-talk] Wrong Page Search Link in Spanish Browse Template

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

Thanks An=EDbal, =


I've applied your fix to the Spanish browse template in the stable branch=
 of
the CVS repository. (I don't think the development branch has this proble=
m.)

Jeff

[Phpwiki-talk] Wrong Page Search Link in Spanish Browse Template

[<ar...@va...>]

Hi,

    The URL in the Browse Template inb the Spanish version is wrong:

<a href=3D"###SCRIPTURL###?FindPage">BuscarP&aacute;gina</a>

    It should be:

<a href=3D"###SCRIPTURL###?BuscarPagina">BuscarP&aacute;gina</a>

    Regards.

-----------------------
An=EDbal Rojas
ar...@va...
www.valhallaproject.com
Tel: 58+212+242.43.79
       58+212+242.66.62
Fax: 58+212+243.68.09

Re: [Phpwiki-talk] Broken things in the nightly cvs snapshot

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

>A correct Interwiki link:  Advogato:person/sethcohn  and
>it's not picked up by the parser.

Non-WikiWord interwiki links will work as long as you enclose them
in square brackets, like so:  [Advogato:person/sethcohn].

Jeff

Re: [Phpwiki-talk] Broken things in the nightly cvs snapshot

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

On Sat, 14 Jul 2001, Seth Cohn wrote:

> Problem:   the mysql tables were named wrong.  I had to adjust the names
> from
> pages to wiki, from scores to wikiscores.

Fixed, thanks for finding this!

> The instructions are pretty good but are showing aging issues as changes has
> been made.

I updated one line, but otherwise the instructions held...

> Interwiki works but NOT for all of the entries in interwiki.map.  For
> instance Advogato is broken
> when you make a link because (it looks like) interwiki.php doesn't correctly
> create a link for
> non WikiWord data  A correct Interwiki link:  Advogato:person/sethcohn  and
> it's not picked up
> by the parser.  I suggest commenting out the entries that don't work or at
> least make a note for them
> until the code is fixed

Yes, I think there is a remark in one of the files how slashes cause
problems. Alpha software indeed.


> Overall impression: VERY VERY sweet.  I'll be using PHPWiki for sure.

Thanks again!
~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] Broken things in the nightly cvs snapshot

[Seth C. <se...@eu...>]

Grabbed a copy of the nightly snapshot to try out phpwiki....

Problem:   the mysql tables were named wrong.  I had to adjust the names
from
pages to wiki, from scores to wikiscores.

The instructions are pretty good but are showing aging issues as changes has
been made.

Interwiki works but NOT for all of the entries in interwiki.map.  For
instance Advogato is broken
when you make a link because (it looks like) interwiki.php doesn't correctly
create a link for
non WikiWord data  A correct Interwiki link:  Advogato:person/sethcohn  and
it's not picked up
by the parser.  I suggest commenting out the entries that don't work or at
least make a note for them
until the code is fixed

Overall impression: VERY VERY sweet.  I'll be using PHPWiki for sure.

[Phpwiki-talk] wysiwyg

[Sergio A. K. <ser...@ho...>]

as anyone seen this: http://crit.org/http://c2.com/cgi/wiki?WysiwygWiki ?

or this: http://standardbrains.editthispage.com/
[in this page, just select some text and press ctrl-B,
 iif you are using IE]

/sergio

Re: [Phpwiki-talk] Developers wanted

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

please! :)
i love it.

Joel Uckelman schrieb:
> Heh, that reminds me, I still have some coding to do to finish the
> versioning stuff. Perhaps that's a project for tomorrow...

-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] sample edit macro

[Jan N. <ja...@gn...>]

Steve Wainstead <sw...@pa...> writes:

> Here's a sample of an edit macro button. Ugly but functional. When I was
> at the NYT on the Web, I was given the task of evaluating Javascript and
> making recommendations for coding practices in JS on the content
> management system we were building for the editors;

I hope you adviced graceful degradation?

> I found JS has far more capability than most people use,

Exactly.  That's one of the reasons you're wise to disable js when
browsing the internet.

> and it's also a really cool language despite being trapped in a
> couple of really crappy browsers.

Ah, you mean the kind of browsers that can't even display those
helpful popup windows, withhold all those magnificent banner
offerings, and enable the disabled to surf the web, and run on your
(Linux) PDA?

As for crappy, that's very much a personal opinion.  I have heard of
people that like to use graphical browsers, and navigate using a
mouse.  Really!

I very much hope that phpwiki will remain best accessible with any
brower, see eg:

    http://www.anybrowser.org/campaign/abdesign2.html#javascript

Greetings,
Jan.

-- 
Jan Nieuwenhuizen <ja...@gn...> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org

[Phpwiki-talk] Welcome to Reini Urban

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

Reini Urban has joined the PhpWiki developer team. Welcome aboard, Reini!

~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] sample edit macro

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

Here's a sample of an edit macro button. Ugly but functional. When I was
at the NYT on the Web, I was given the task of evaluating Javascript and
making recommendations for coding practices in JS on the content
management system we were building for the editors; I found JS has far
more capability than most people use, and it's also a really cool language
despite being trapped in a couple of really crappy browsers.

diff -r1.19 editpage.html
15c15
< <form class="wikiaction" method="POST" action="###BROWSE_PAGE###">
---
> <form name="editbox" class="wikiaction" method="POST"
action="###BROWSE_PAGE###">
30a31
> <input type="button" name="timestamper" value="Add timestamp"><br>
58a60,65
>
> <script language="Javascript">
> document.editbox.timestamper.onclick = function () {
>     document.editbox.content.value += Date();
> }
> </script>


In short,

1) I named the form "editbox", probably a poor name though... the textarea
is called "content" for reasons internal to PhpWiki, but here it all looks
confusing. Forms and their elements should always have names, since
all Javascript objects are really hashes and you can access things
by name instead of number. Anyway:

2) I added a button input called "timestamper"

3) At the end of the file, I put JS code in <script> tags where it is
separated out from the HTML. This makes the code much easier to maintain
in most cases. Most developers jam all the JS inside the HTML which is a
huge unreadable mess.

~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] dbx again

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

On Thu, 12 Jul 2001, Steve Wainstead wrote:

> It goes without saying that we need to move to a library like this one...
> I will probably go ahead and make a copy of schema.mysql as schema.dbx and
> put that in CVS.

Er, that is, mysql.php as dbx.php or something.

~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] dbx again

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

That was remarkably easy to do. I wrote a little page to list the
pagenames from the phpwiki database just using the dbx examples page
(http://www.php.net/manual/en/function.dbx-query.php).

It goes without saying that we need to move to a library like this one...
I will probably go ahead and make a copy of schema.mysql as schema.dbx and
put that in CVS.

~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] dbx module

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

The dbx module was added to PHP 4.0.6, and was released 6/23. I think I'll
give it a try soon.

~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] Developers wanted

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

Yes, we have strict deadlines here! :-)

~swain

On Wed, 11 Jul 2001, Joel Uckelman wrote:

> Heh, that reminds me, I still have some coding to do to finish the
> versioning stuff. Perhaps that's a project for tomorrow...
>
> --
> J.
>
>
>
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> http://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] Developers wanted

[Joel U. <uck...@no...>]

Quoth Steve Wainstead:
> 
> Hello all,
> 
> I've been meaning to post an invite for months now to join the team, if
> you are interested. Things we are adding to 1.3 can be found at
> http://sourceforge.net/pm/task.php?group_project_id=7691&group_id=6121&func=b
> rowse
> 
> If you join the team you will have write access to the CVS repository plus
> some other goodies through SourceForge; you need a SourceForge account
> though to join up.
> 
> Knowledge of CVS is needed, but you only need to learn a handful of
> commands to do most things.
> 
> I still want to make PhpWiki one of the best Wikis out there. So far users
> have been very enthusiastic, and I've yet to see any serious complaints
> about it (mostly feature requests).
> 
> Email me off list (sw...@pa...) if you are interested.
> 
> cheers
> ~swain

Heh, that reminds me, I still have some coding to do to finish the 
versioning stuff. Perhaps that's a project for tomorrow...

-- 
J.

[Phpwiki-talk] Developers wanted

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

Hello all,

I've been meaning to post an invite for months now to join the team, if
you are interested. Things we are adding to 1.3 can be found at
http://sourceforge.net/pm/task.php?group_project_id=7691&group_id=6121&func=browse

If you join the team you will have write access to the CVS repository plus
some other goodies through SourceForge; you need a SourceForge account
though to join up.

Knowledge of CVS is needed, but you only need to learn a handful of
commands to do most things.

I still want to make PhpWiki one of the best Wikis out there. So far users
have been very enthusiastic, and I've yet to see any serious complaints
about it (mostly feature requests).

Email me off list (sw...@pa...) if you are interested.

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] Adding pages in bulk

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

I once tried to load the contents of the Jargon File into PhpWiki via a
Perl script, and had some success. (The JF is at
http://www.tuxedo.org/~esr/jargon/. You can get it as one big text file,
which is what I used).

I wrote a Perl script to do this, but it can be done in PHP without much
trouble. We don't have an "import" facility per se because there's never
been a demand for it, and there's an infinite number of input formats to
deal with ;-)

My approach would be to write a Perl script that read in each separate
entry from the file (by resetting $/) and then generating the SQL to
insert that entry. When the SQL looks good, I would try loading the files
into a virgin Wiki before loading it into the real thing.

~swain


On Fri, 6 Jul 2001, Malcolm Ryan wrote:

> I have a large collection of data in a text file that I would like to add
> to my PhpWiki. The file consists of several hundred entries, each of which
> should go into a separate page. Is there any easy way to write a
> script to add pages in bulk, rather than doing it manually?
>
> Malcolm
>
> --
> Malcolm Ryan - mal...@cs... - http://www.cse.unsw.edu.au/~malcolmr/
>   AI Dept, CSE, UNSW, Australia, Phone: +61 2 9385-6906 Fax: +61 2 9385-4936
>
>            "He causes his sun to rise on the evil and the good,
>            and sends rain on the righteous and the unrighteous." - Matt 5:45
>
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> http://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] Adding pages in bulk

[Malcolm R. <mal...@cs...>]

I have a large collection of data in a text file that I would like to add 
to my PhpWiki. The file consists of several hundred entries, each of which
should go into a separate page. Is there any easy way to write a 
script to add pages in bulk, rather than doing it manually?

Malcolm

-- 
Malcolm Ryan - mal...@cs... - http://www.cse.unsw.edu.au/~malcolmr/
  AI Dept, CSE, UNSW, Australia, Phone: +61 2 9385-6906 Fax: +61 2 9385-4936

           "He causes his sun to rise on the evil and the good,
           and sends rain on the righteous and the unrighteous." - Matt 5:45

Re: [Phpwiki-talk] PEAR coding standards

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

On Tue, 26 Jun 2001, J C Lawrence wrote:

> On Tue, 26 Jun 2001 15:58:51 -0400 (EDT)
> Steve Wainstead <sw...@pa...> wrote:
>
> > am I missing any? ;-)
>
> bash vs tcsh

wow, can't believe I overlooked that one...

~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] PEAR coding standards

[J C L. <cl...@ka...>]

On Tue, 26 Jun 2001 15:58:51 -0400 (EDT) 
Steve Wainstead <sw...@pa...> wrote:

> They are as amusing as tiresome:

> spaces vs. tabs Emacs vs. vi Linux vs. *bsd Netscape vs. IE

> am I missing any? ;-)

bash vs tcsh, perl cs python, (La)TeX vs <insert WYSIWYG
WordProcessor>, GNOME vs KDE (both are equally useless), top down
versus bottom up, OO vs procedural, Free Software vs Open Source....

And it goes on from there.

-- 
J C Lawrence                                             cl...@ka...
---------(*)                                http://www.kanga.nu/~claw/
I never claimed to be human.

Re: [Phpwiki-talk] PEAR coding standards

[J C L. <cl...@ka...>]

On Tue, 26 Jun 2001 12:42:40 -0400 (EDT) 
Steve Wainstead <sw...@pa...> wrote:

> I've read through the PEAR coding standards and they look
> good. I'd like all the project code to use them. You can take a
> look at http://www.php.net/manual/en/pear.standards.php.

So drop an Emacs mode comment at the top of all the files so your
editor Does The Right Thing and then forget about it.  Yeesh.

<<Written as one who disagrees rather strenuously with the PEAR
coding standards, but doesn't really care about it either -- that's
what M-x indent region is for>>

-- 
J C Lawrence                                             cl...@ka...
---------(*)                                http://www.kanga.nu/~claw/
I never claimed to be human.

Re: [Phpwiki-talk] PEAR coding standards

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

Steve Wainstead schrieb:
> On Tue, 26 Jun 2001, Joel Uckelman wrote:
> > Me too. I think that's in the spirit of old-skool K&R C. Of course, this sort of thing is how epic flamewars get started. Heh. :)
> 
> They are as amusing as tiresome:
> spaces vs. tabs
> Emacs vs. vi
> Linux vs. *bsd
> Netscape vs. IE
> 
> am I missing any? ;-)

Emacs vs XEmacs and Scheme vs Common Lisp are the worst in my communities.
perl vs python, GPL vs BSD-style and GPL vs Artistic also leeds to amusing
flamewars.
relatively new is postgreSQL vs mysql. 
local popularity here got debian vs SUSE and KDE vs Gnome.

it's always good to have options :)
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] PEAR coding standards

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

>... we have a lot of dangling if statements of the form:
>
>if (foo)
>	statement;
>
>which will have to be excorcised...

I vote that we don't worry about these too much.  The only thing I can
find in the PEAR coding standards which addresses this is:

  You are strongly encouraged to always use curly braces even in
  situations where they are technically optional. Having them
  increases readability and decreases the likelihood of logic
  errors being introduced when new lines are added. 

("Strongly encouraged" != "required".)