You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(103) |
Jul
(105) |
Aug
(16) |
Sep
(16) |
Oct
(78) |
Nov
(36) |
Dec
(58) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(100) |
Feb
(155) |
Mar
(84) |
Apr
(33) |
May
(22) |
Jun
(77) |
Jul
(36) |
Aug
(37) |
Sep
(183) |
Oct
(74) |
Nov
(235) |
Dec
(165) |
2002 |
Jan
(187) |
Feb
(183) |
Mar
(52) |
Apr
(10) |
May
(15) |
Jun
(19) |
Jul
(43) |
Aug
(90) |
Sep
(144) |
Oct
(144) |
Nov
(171) |
Dec
(78) |
2003 |
Jan
(113) |
Feb
(99) |
Mar
(80) |
Apr
(44) |
May
(35) |
Jun
(32) |
Jul
(34) |
Aug
(34) |
Sep
(30) |
Oct
(57) |
Nov
(97) |
Dec
(139) |
2004 |
Jan
(132) |
Feb
(223) |
Mar
(300) |
Apr
(221) |
May
(171) |
Jun
(286) |
Jul
(188) |
Aug
(107) |
Sep
(97) |
Oct
(106) |
Nov
(139) |
Dec
(125) |
2005 |
Jan
(200) |
Feb
(116) |
Mar
(68) |
Apr
(158) |
May
(70) |
Jun
(80) |
Jul
(55) |
Aug
(52) |
Sep
(92) |
Oct
(141) |
Nov
(86) |
Dec
(41) |
2006 |
Jan
(35) |
Feb
(62) |
Mar
(59) |
Apr
(52) |
May
(51) |
Jun
(61) |
Jul
(30) |
Aug
(36) |
Sep
(12) |
Oct
(4) |
Nov
(22) |
Dec
(34) |
2007 |
Jan
(49) |
Feb
(19) |
Mar
(37) |
Apr
(16) |
May
(9) |
Jun
(38) |
Jul
(17) |
Aug
(31) |
Sep
(16) |
Oct
(34) |
Nov
(4) |
Dec
(8) |
2008 |
Jan
(8) |
Feb
(16) |
Mar
(14) |
Apr
(6) |
May
(4) |
Jun
(5) |
Jul
(9) |
Aug
(36) |
Sep
(6) |
Oct
(3) |
Nov
(3) |
Dec
(3) |
2009 |
Jan
(14) |
Feb
(2) |
Mar
(7) |
Apr
(16) |
May
(2) |
Jun
(10) |
Jul
(1) |
Aug
(10) |
Sep
(11) |
Oct
(4) |
Nov
(2) |
Dec
|
2010 |
Jan
(1) |
Feb
|
Mar
(13) |
Apr
(11) |
May
(18) |
Jun
(44) |
Jul
(7) |
Aug
(2) |
Sep
(14) |
Oct
|
Nov
(6) |
Dec
|
2011 |
Jan
(2) |
Feb
(6) |
Mar
(3) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
(11) |
Feb
(3) |
Mar
(11) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(4) |
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(8) |
Dec
(1) |
2015 |
Jan
(3) |
Feb
(2) |
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2016 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(6) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2022 |
Jan
(11) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(3) |
2024 |
Jan
(7) |
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Ray T. <rth...@in...> - 2002-12-03 19:56:24
|
aphid wrote: > > On Tuesday, December 3, 2002, at 07:57 AM, Ray Thompson wrote: > >> Is it possible to have multiple WikiWords for a single page? >> If so where may I find docs on the subject? >> >> Thanks, >> Ray >> >> > > I've run into similar problems.. where say there's a page about > JohnSmith but he's also referred to as John and Mr. Smith later on.. > what you can do is [John | JohnSmith] or [Mr. Smith | JohnSmith] - > they'll refer to the same Wikipage, but look different. The hard part > is getting your collaborators to all use the same phrase for the same > thing. > > Cheers, > A > That will work. Thanks again. |
From: Marjorie R. <mro...@ma...> - 2002-12-03 19:12:05
|
For anyone who wants to try to design a more usable wiki: Communication Arts Magazine announces the deadline for their Ninth Interactive Design Competition--January 15th, 2003. INTERACTIVE DESIGN COMPETITION Enter the most prestigious design competition for interactive media, the ninth annual Communication Arts Interactive Design Competition. Any interactive project created for digital distribution on the World Wide Web, CD-ROM, interactive kiosk or handheld device is eligible. Selected by a nationally representative panel of distinguished programmers, interface designers and creative directors, the winning entries will be published in the September/October Interactive Annual of Communication Arts and on our Web site. Seventy-five thousand copies will be distributed worldwide, assuring important exposure to the creators of these outstanding projects. Submission guidelines and FAQs can be found at: http://www.commarts.com/CA/magazine/comp/ To download an entry form go to: http://www.commarts.com/CA/download/ia03.pdf |
From: Ray T. <rth...@in...> - 2002-12-03 15:59:39
|
Is it possible to have multiple WikiWords for a single page? If so where may I find docs on the subject? Thanks, Ray |
From: aphid <me...@ap...> - 2002-12-03 03:19:52
|
On Monday, December 2, 2002, at 08:45 AM, Joby Walker wrote: > Looks to me like it is not an issue with PostgreSQL but with the page > loading for your virgin wiki. The text is from TextFormattingRules in > the section on creating footnotes. I haven't looked at the page > loading at all so it would take me a while to figure the exact issue > is. > > Looks like Jeff Dairiki was the last to modify what seems to be the > two pages in question (lib/loadsave.php and lib/ziplib.php). > > Jeff, It looks like the text that it causing the problem is the old > markup unescaped footnote link. The line: > > ----------------------------------------------------------------------- > * You can create footnotes by using [[1], [[2], [[3], ... like this > here [1]. See footnote for counterpart. (If the [[ is in the first > column, it is a footnote ''definition'' rather than a footnote > ''reference'' [1].) > ----------------------------------------------------------------------- > > So it is starting and ending with the [1] elements. > > Any ideas? > I seem to have tracked my problem down to the ConvertOldMarkup function in stdlib.php, as of Dakiri's Baclkpages fix. Since the debugging is over my head, I simply forced new markup - after resaving a few old pages, the problem went away entirely. Perhaps these issues are related? Cheers, A |
From: Joby W. <joby@u.washington.edu> - 2002-12-02 16:45:11
|
Looks to me like it is not an issue with PostgreSQL but with the page loading for your virgin wiki. The text is from TextFormattingRules in the section on creating footnotes. I haven't looked at the page loading at all so it would take me a while to figure the exact issue is. Looks like Jeff Dairiki was the last to modify what seems to be the two pages in question (lib/loadsave.php and lib/ziplib.php). Jeff, It looks like the text that it causing the problem is the old markup unescaped footnote link. The line: ----------------------------------------------------------------------- * You can create footnotes by using [[1], [[2], [[3], ... like this here [1]. See footnote for counterpart. (If the [[ is in the first column, it is a footnote ''definition'' rather than a footnote ''reference'' [1].) ----------------------------------------------------------------------- So it is starting and ending with the [1] elements. Any ideas? jbw Mirko Viviani wrote: > Ciao! > > I've installed phpwiki 1.3.3 with php4 and postgres 7.2.3 > All is working correctly, db is populated and I can create new pages, but the > first page stops with this error: > > [...] > TitleSearch > from MIME file ./pgsrc/TitleSearch is identical to current version 1 - skipped > > lib/WikiDB/backend/PearDB.php:680: Fatal[256]: wikidb_backend_pgsql: fatal > database error > > * DB Error: unknown error > * (INSERT INTO page (id,pagename,hits) VALUES (236,']. See footnote for > counterpart. (If the is in the first column, it is a footnote > ''''definition'''' rather than a footnote ''''reference'''' [',0) > [nativecode=ERROR: value too long for type character varying(100) > * ]) > * > > lib/loadsave.php:359: Notice[1024]: Loading InterWikiMap from external file > lib/interwiki.map. > > > Any info ? > Thanks. > |
From: Mirko V. <mir...@rc...> - 2002-12-02 14:56:47
|
Ciao! I've installed phpwiki 1.3.3 with php4 and postgres 7.2.3 All is working correctly, db is populated and I can create new pages, but the first page stops with this error: [...] TitleSearch from MIME file ./pgsrc/TitleSearch is identical to current version 1 - skipped lib/WikiDB/backend/PearDB.php:680: Fatal[256]: wikidb_backend_pgsql: fatal database error * DB Error: unknown error * (INSERT INTO page (id,pagename,hits) VALUES (236,']. See footnote for counterpart. (If the is in the first column, it is a footnote ''''definition'''' rather than a footnote ''''reference'''' [',0) [nativecode=ERROR: value too long for type character varying(100) * ]) * lib/loadsave.php:359: Notice[1024]: Loading InterWikiMap from external file lib/interwiki.map. Any info ? Thanks. -- Bye, Mirko |
From: Preston L. B. <pre...@co...> - 2002-11-30 06:39:33
|
OK - narrowed this down. The culprit is in Request.php: function compress_output() { if (function_exists('ob_gzhandler')) { //print "<p>FILE " . __FILE__. " LINE " . __LINE__ . "</p>"; ob_start('ob_gzhandler'); $this->_is_compressing_output = true; } } The "print" statement is mine. Uncomment the "print" statement and the page renders OK. Comment out the "print" statement and the page renders as gibberish. Apparently compressing the output is causing ... some sort of problem. Preston L. Bannister wrote: > I am trying to get phpwiki running on a new Redhat 8.0 box. This is a > pretty much stock up-to-date Redhat box - Apache 2.0.40 and PHP 4.2.2 > (of primary interest). The setup is extremely vanilla - as in using > an unedited index.php. > > For some reason phpwiki pages are coming up as gibberish in Mozilla > (on Windows and Linux) or is IE. The same pages viewed through lynx > look OK. > If I put a simple "print" statement in index.php anywhere before > main.php is included the pages render fine (with the expected PHP > header() errors). > > Maybe I've missed something, but I don't see a prior mention of this > sort of problem. > > This is true with either phpwiki 1.3.3 or the current version from CVS. > > I'll take crack at debugging this, but would like to know if someone > else has seen the same. > > -- > Preston L. Bannister > pre...@co... > pbannister on Yahoo Messenger |
From: Preston L. B. <pre...@co...> - 2002-11-30 03:46:35
|
I am trying to get phpwiki running on a new Redhat 8.0 box. This is a pretty much stock up-to-date Redhat box - Apache 2.0.40 and PHP 4.2.2 (of primary interest). The setup is extremely vanilla - as in using an unedited index.php. For some reason phpwiki pages are coming up as gibberish in Mozilla (on Windows and Linux) or is IE. The same pages viewed through lynx look OK. If I put a simple "print" statement in index.php anywhere before main.php is included the pages render fine (with the expected PHP header() errors). Maybe I've missed something, but I don't see a prior mention of this sort of problem. This is true with either phpwiki 1.3.3 or the current version from CVS. I'll take crack at debugging this, but would like to know if someone else has seen the same. -- Preston L. Bannister pre...@co... pbannister on Yahoo Messenger |
From: aphid <me...@ap...> - 2002-11-27 06:57:12
|
After going back to an older version, I may have found the source of my problems... When I replace my (working) stdlib.php (1.127) with the current (1.131) one it goes right back to dying on large pages. cheers a |
From: Ray T. <rth...@in...> - 2002-11-26 23:35:37
|
From a wiki point of view I don't know. From a web server point of view I'm planning on using LDAP but whatever your web server is it should support authentication for web pages. --Ray ba...@mi... wrote: > Hi. I may be completely missing something. I'd like my wiki to be > private, requiring username and password to both read and post. It > doesn't seem clear how to set this up. Can it be and if so, has anyone a > nice pointer? > |
From: Jeff D. <da...@da...> - 2002-11-26 23:28:46
|
> Can this be done? I want people to have to login to read and post on my > > phpwiki... Soon (my guess is a few months), but not yet, PhpWiki will be able to handle authentication/login by itself. (Most of the code is there, but I don't think it's fully working yet.) In your case, since you want people to have to log in both to read and edit the wiki, you can use apache's authentication facilities to control access to your wiki (the same as you would to control access to any static web pages.) There's a bunch of different ways to set that up depending on what you want to use as a user/password validation database. (Refer to the Apache docs). Here's a few places to start: http://httpd.apache.org/docs-2.0/howto/auth.html http://httpd.apache.org/docs-2.0/mod/ (look at mod_auth*) If you want the apache-verified username to be used by PhpWiki (e.g for logging of author names in the page histories) then a little hacking of PhpWiki code might be required. When you get that far, post a note to the list, and someone will be able to help you. |
From: <ba...@mi...> - 2002-11-26 22:54:10
|
Hi. I may be completely missing something. I'd like my wiki to be private, requiring username and password to both read and post. It doesn't seem clear how to set this up. Can it be and if so, has anyone a nice pointer? -- -------------------------------------------------------------------------- Michael Bauer ba...@mi... http://www.michaelbauer.com |
From: Ray T. <rth...@in...> - 2002-11-26 21:56:30
|
Regarding http://sourceforge.net/mailarchive/message.php?msg_id=2536391 Installing the php-mysql rpm fixed one of my problems. On to the next... Thanks Jeff. --Ray |
From: <ba...@mi...> - 2002-11-26 20:53:14
|
No, I haven't done that. Didn't know about it. I downloaded source and thought i'd just reconfigure php --with-mysql. I think I've actually decided to punt and install an older apache (1.3.27). Seems to have worked just fine. On Tue, 26 Nov 2002, Jeff Dairiki wrote: > On Tue, 26 Nov 2002 15:19:14 -0500 (EST) > <ba...@mi...> wrote: > > > I get a > > "DB Error: extension not found" which I thought might be because my > > version of php doesn't support mysql out of the RH box, > > Have you installed the php-mysql RPM? (The PHP extensions are > not included in the main php RPM, but are each in their own separate > sub-package...) > > -- -------------------------------------------------------------------------- Michael Bauer ba...@mi... http://www.michaelbauer.com |
From: Jeff D. <da...@da...> - 2002-11-26 20:33:45
|
On Tue, 26 Nov 2002 15:19:14 -0500 (EST) <ba...@mi...> wrote: > I get a > "DB Error: extension not found" which I thought might be because my > version of php doesn't support mysql out of the RH box, Have you installed the php-mysql RPM? (The PHP extensions are not included in the main php RPM, but are each in their own separate sub-package...) |
From: <ba...@mi...> - 2002-11-26 20:18:05
|
I'm trying to install using the following configuration PHPWiki 1.3.3 PHP 4.2.2 MySQL 3.23.53a Apache 2.0.40 RH 8.0 (Psyche) Has anyone had any experience trying to do something like this? I get a "DB Error: extension not found" which I thought might be because my version of php doesn't support mysql out of the RH box, so I downloaded PHP 4.2.3 and started to reconfigure that but saw that it is only supposed to be used with Apache 2.0.39 (although I imagine 40 would be ok). Still, I don't know quite what configuration parameters to use for this anyway. Please help if you can. -- -------------------------------------------------------------------------- Michael Bauer ba...@mi... http://www.michaelbauer.com |
From: Jeff D. <da...@da...> - 2002-11-26 15:21:31
|
On Tue, 26 Nov 2002 09:52:52 +0000 John Kershaw <li...@ke...> wrote: I just noticed that there's a page on your wiki that has an > apostrophe in its name. Is this okay in 1.3.3? I use 1.3.2 and > apostrophe's are a nightmare - it screws up any attempts to do > backlinks, removes and stuff. Apostrophe's shouldn't be a problem (but they might). If they do cause problems, it's a bug. There were some problems I remember which were due to buggy PEAR DB code. These should have gone away now that we provide our own PEAR code. I don't think 1.3.3 includes our own PEAR code though (is there a "lib/pear" subdirectory in the distribution?), so whether or not you have trouble may depend on what version of PEAR code you have installed... |
From: <art...@vo...> - 2002-11-26 10:50:57
|
Hi, I would like to get rid of the "Describe [WikiWord] here." default content for pages, because it's annoying to delete each time you want to create a new page. I looked at the php source and it seems hardcoded to help phpwiki recognize that the page is at revision 0. Would it be possible to get rid of this message, or at least make it a configurable option ? ------------------------------------------ Faites un voeu et puis Voila ! www.voila.fr |
From: John K. <li...@ke...> - 2002-11-26 09:55:58
|
Hi, I just noticed that there's a page on your wiki that has an apostrophe in its name. Is this okay in 1.3.3? I use 1.3.2 and apostrophe's are a nightmare - it screws up any attempts to do backlinks, removes and stuff. http://www.rawfoodwiki.org/index.php/emma's%20amazing%20hummous I'd still encourage people not to use spaces or punctuation in their page names, ie EmmasAmazingHummous John. |
From: aphid <me...@ap...> - 2002-11-26 07:45:32
|
I've done a bit more research on this error here's a summation of what's going on. when a wikipage reaches a certain length threshold (which seems to change based on markup and maybe whitespace), httpd crashes and will not bring up the page. when the page is saved, it also crashes, but the changes seem to have been sent before the crash occurs. The threshold appears to be between 1100 and 1300 characters (a few short paragraphs), and I'm not entirely sure what causes it to change for a particular page. I've had pages where it works at 1353 and 1127, add a character and it will crash. I have no explanation for the variability.. maybe a difference of wiki markup characters and white space? the error in the log is coming up as: [Mon Nov 25 22:46:54 2002] [notice] child pid 422 exit signal Illegal instruction (4) pid 422 of course being httpd I am running Apache 1.3.27 with php 4.2.3 on darwin (os X 10.2.2). This first popped up with a server at school (a dual g4 running the above) and I have mirrored it at home on my flat panel imac (also running the above). Originally occurred in a cvs wiki from ~2 wks ago, updated both of them to current and the error is still happening. any help is greatly appreciated cheers a |
From: <edo...@ne...> - 2002-11-26 05:05:50
|
The Director, Sir, URGENT AND EXTREMELY CONFIDENTIAL It is with trust and confidentiality, that I make this urgent and important business proposal to you. It gives me so much enthusiasm to write this letter to you. It is all in a view to soliciting for assistance to enable us execute a venture of mutual benefit. My name is Edos Afen an employee with the Central Bank of Zimbabwe, a senior employee, during the last political disturbance by the Government held by president Robert Mugabe, (I and my other colleagues worked out over US$26,000,000,00 (Twenty Six Million,United States Dollars Only) as over invoiced and inflated payment for election materials and the funds is now with the security company in Holland for safe keeping. Now that we are not sure of the future of this country, due to the cry of sanction by world leaders in and around the world. For the brutal take over of white people farm resident in Zimbabwe by the Administration, and the lack of purpose in the administration, my colleaques and I have decided to invest this funds wisely. I am currently in the Netherlands on a short diplomatic course and my involvement in this transaction shall be kept secret,since our civil service code of conduct forbids us to have any private financial of this magnitude.We need a successful transfer of the funds to a designated account. We need the assistance of a foreign company/persons to push this money into their accounts. You will do very well with what we have in mind. Your share of whatever we succeed in putting into your account will be 20% of the total sum, while 70% will be for us and 10% will be mapped out for any expenses incurred by both parties in the process of the transfer, we require you your willingness to assist us. I will refrain from giving out more operational details, until I receive your reply. Since time is of the essence to us, reply this letter quickly so as to know what next to do, even if this letter does not meet your approval, please inform me. There is no risk involved, as we have done our homework carefully. Looking forward to hearing from you. Yours Sincerely, Mr. Edos Afen |
From: Jeff D. <da...@da...> - 2002-11-25 22:58:54
|
> non-lower case <BR> tags would be helpful, too. Okay, done (in CVS). Patch at: http://cvs.sf.net/cgi-bin/viewcvs.cgi/phpwiki/phpwiki/lib/InlineParser.php.diff?r1=1.18&r2=1.19 > ...as Russ Miller > suggested ordered/unordered lists would work for a lot... > I guess I can tell people to put stars in front of the ingredients. A while ago there was some talk about being able to specify the bullet type for the unordered lists. E.g. '*' give the standard big dot, '-' for dash, '+' for plus, etc, etc. An extension to this scheme would be something like '.' for no bullet. That might help for your recipes. (Selectable bullets would only work on browsers with good CSS support, I think.) I'm not convinced any of this is a good idea, but I'd thought I'd bring it up again for discussion... |
From: Martin G. <gim...@gi...> - 2002-11-25 22:45:43
|
Jeff Dairiki <da...@da...> writes: > On Sun, 03 Nov 2002 22:53:19 +0100 > Martin Geisler <gim...@gi...> wrote: > >> >> The PhpWeather plugin was a bit outdated. I made it work with >> >> the current CVS version and added some new features. > > I've just checked your changes (and new PhpWeatherPlugin pgsrc) into > CVS. Great, thanks! > I had to make two small changes (calling conventions of > get_languages() and get_languages_select()) to get it to work with > phpweather-2.0.0. Good catch - those two functions have changed slightly in CVS, but it's only calling conventions as you note. Oh well, I guess it's time for another release of PhpWeather... -- Martin Geisler My GnuPG Key: 0xF7F6B57B See http://gimpster.com/ and http://phpweather.net/ for: PHP Weather => Shows the current weather on your webpage and PHP Shell => A telnet-connection (almost :-) in a PHP page. |
From: Margie R. <mro...@ch...> - 2002-11-25 22:24:53
|
> 3) The location of your navigation buttons are all determined by the > template files in: themes/<profile>/templates/ . Modifying them has > been covered many times on this list. hey, I know how to edit the template. But I didn't know how to dissect <?= Template('navbar') ?> to segregate out the EditText button from the rest. I can probably figure it out, but my initial efforts didn't provide fruit on that front. /web/rawfood/themes/Portland/templates/body.tmpl 1) HTML input already exists. The RawHtml plugin will give you the ability to include Html -- but this is dangerous since people can easily mangle the pages, and do other more nasty things Obviously, I don't want "nasty things." I'd be looking for input of basic tags for tables. non-lower case <BR> tags would be helpful, too. 2) Single linebreaks == linebreak. Although this is intuitive, this would make the source for many of us less readable, as Russ Miller suggested ordered/unordered lists would work for a lot and having two returns for an end of paragraph is not that hard to figure out. I guess I can tell people to put stars in front of the ingredients. Best Regards, Margie > > jbw > > Margie Roswell wrote: > > > Thanks for your thoughts. Note: I actually want linebreaks ("not > > ") > > to convert to > > . > > > > my thinking is if that "wikis confuse people a lot," apart from training, > > there is probably more that can be done on the user-interface end to make > > it less confusing. > > > > One thing I want to do is to move EditThis to the top of the page, for > > instance. Haven't dissected how to do that yet, actually. Clues welcome. > > > > Another item I forgot to mention is the desire to print only the recipe > > (one of the nested tables...) Very minor point. Major points are: > > > > - want html input > > - want EditThis at the top of the page > > - want single returns to be linebreaks. (that would negate the need for a > > special recipe input form.) > > - didn't work for me at the beginning of a line. > > > > Someone pointed out that I forgot to mention the URL. > > > > It's rawfoodwiki.org. > > > > Best Regards, > > > > Margie > > > > > > -- > > Margie Roswell > > 3443 Guilford Terrace > > Baltimore, MD 21218 > > H: 410-467-3727 > > W: 410-455-6802 > > E: mro...@ch... > > W: http://hello.to/maps > > > > On Mon, 25 Nov 2002, Adam Shand wrote: > > > > > > >Marjorie Roswell wrote: > > > > > > > > >>I've concluded that since people aren't using my site, it could > > >>probably be made easier to use. Looking for ideas, and also code. > > >> > > >>I've announced the site to a raw foods listserv twice, to a raw food > > >>seminar of people who cared enough to pay $40 to be there, and to > > >>(great) vegetarian thanksgiving meal, and to this listserv, of course. > > >>Of more than 600 people receiving the announcement, only three people > > >>have added content to it, including someone on this list. > > >> > > > > > >Just as an FYI, that's actually not too bad. wiki's confuse people ... > > >a lot. despite the fact that they are incredibly simple a lot of people > > >really resist the idea of using them. it took me months to get people > > >regularly adding contect to the personaltelco.net wiki and that's > > >despite the fact that my audience was fairly hardcore geek and there > > >were 70+ people on a mailing list specifically working on a project. > > > > > >wiki's build slowly, give it time. in the mean time make sure that > > >*you* use it as much as possible, as it becomes more and more useful > > >people will use it more and more. > > > > > >my personal recommendation would be that if you want to use wiki, resist > > >the temptation to make a special recipe module. the strength of wiki > > >comes from it's ability to do everything. if you did want to do > > >something to make importing recipies easier maybe a good way of doing it > > >would be to setup a little web form which would convert other formats > > >into wiki markup, so they can just cut and paste it into the wiki. this > > >way you preserve the strength of wiki and still make peoples lives > > easier. > > > > > >some of your other concerns are totally valid, i'd love to see %%% > > >replaced with > > etc. > > > > > >Adam. > > > > > > > > >> > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Get the new Palm Tungsten T > > handheld. Power & Color in a compact size! > > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en > > _______________________________________________ > > Phpwiki-talk mailing list > > Php...@li... > > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > > |
From: Joby W. <joby@u.washington.edu> - 2002-11-25 21:41:07
|
Margie, 1) HTML input already exists. The RawHtml plugin will give you the ability to include Html -- but this is dangerous since people can easily mangle the pages, and do other more nasty things 2) Single linebreaks == linebreak. Although this is intuitive, this would make the source for many of us less readable, as Russ Miller suggested ordered/unordered lists would work for a lot and having two returns for an end of paragraph is not that hard to figure out. 3) The location of your navigation buttons are all determined by the template files in: themes/<profile>/templates/ . Modifying them has been covered many times on this list. jbw Margie Roswell wrote: > Thanks for your thoughts. Note: I actually want linebreaks ("not > ") > to convert to > . > > my thinking is if that "wikis confuse people a lot," apart from training, > there is probably more that can be done on the user-interface end to make > it less confusing. > > One thing I want to do is to move EditThis to the top of the page, for > instance. Haven't dissected how to do that yet, actually. Clues welcome. > > Another item I forgot to mention is the desire to print only the recipe > (one of the nested tables...) Very minor point. Major points are: > > - want html input > - want EditThis at the top of the page > - want single returns to be linebreaks. (that would negate the need for a > special recipe input form.) > - didn't work for me at the beginning of a line. > > Someone pointed out that I forgot to mention the URL. > > It's rawfoodwiki.org. > > Best Regards, > > Margie > > > -- > Margie Roswell > 3443 Guilford Terrace > Baltimore, MD 21218 > H: 410-467-3727 > W: 410-455-6802 > E: mro...@ch... > W: http://hello.to/maps > > On Mon, 25 Nov 2002, Adam Shand wrote: > > > >Marjorie Roswell wrote: > > > > > >>I've concluded that since people aren't using my site, it could > >>probably be made easier to use. Looking for ideas, and also code. > >> > >>I've announced the site to a raw foods listserv twice, to a raw food > >>seminar of people who cared enough to pay $40 to be there, and to > >>(great) vegetarian thanksgiving meal, and to this listserv, of course. > >>Of more than 600 people receiving the announcement, only three people > >>have added content to it, including someone on this list. > >> > > > >Just as an FYI, that's actually not too bad. wiki's confuse people ... > >a lot. despite the fact that they are incredibly simple a lot of people > >really resist the idea of using them. it took me months to get people > >regularly adding contect to the personaltelco.net wiki and that's > >despite the fact that my audience was fairly hardcore geek and there > >were 70+ people on a mailing list specifically working on a project. > > > >wiki's build slowly, give it time. in the mean time make sure that > >*you* use it as much as possible, as it becomes more and more useful > >people will use it more and more. > > > >my personal recommendation would be that if you want to use wiki, resist > >the temptation to make a special recipe module. the strength of wiki > >comes from it's ability to do everything. if you did want to do > >something to make importing recipies easier maybe a good way of doing it > >would be to setup a little web form which would convert other formats > >into wiki markup, so they can just cut and paste it into the wiki. this > >way you preserve the strength of wiki and still make peoples lives > easier. > > > >some of your other concerns are totally valid, i'd love to see %%% > >replaced with > etc. > > > >Adam. > > > > > >> > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Get the new Palm Tungsten T > handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk |