Menu
▾
▴
phpwiki-talk
|
From: Steve W. <sw...@pa...> - 2001-09-18 16:45:28
|
On Tue, 18 Sep 2001, Jeff Dairiki wrote:
> To avoid becoming an instrument of spammage, we probably don't want to
> allow just anyone to sign arbitrary users (or e-mails) up for page
> change
> notifications. Or do we?
no, most certainly not. The one patch we got many months ago allowed this;
one just puts one's email address in the page, I think it was. Not good.
Fine on an intranet though!
~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
|
|
From: Gary B. <ga...@in...> - 2001-09-18 16:55:28
|
On Tue, 18 Sep 2001, Steve Wainstead wrote: > On Tue, 18 Sep 2001, Jeff Dairiki wrote: > > > To avoid becoming an instrument of spammage, we probably don't want to > > allow just anyone to sign arbitrary users (or e-mails) up for page > > change > > notifications. Or do we? > > no, most certainly not. The one patch we got many months ago allowed this; > one just puts one's email address in the page, I think it was. Not good. > Fine on an intranet though! Well, if you allow all users to read and edit the wiki but allow them to create an account which will a) log their name on RecentChanges instead of their IP, and b) allow them to get email notification. When they create the account, they are sent an email saying "visit this URL to confirm your email addr", and PhpWiki enables the account fully when the URL is visited. Cheers, Gary [ ga...@in... ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ] |
|
From: Adam S. <ad...@pe...> - 2001-09-18 18:12:01
|
> To avoid becoming an instrument of spammage, we probably don't want to > allow just anyone to sign arbitrary users (or e-mails) up for page > change notifications. Or do we? we want to make sure that the only people who can get wiki changes spam are people that are participating, unless you want to make people ack every page addition (which sounds like a hassle to me. i say make home pages append only. so people can still leave discussion and conversation can happen there, but the primary info can't be messed with. when people register have them optionally submit their email address, if they do then send them email, if they ack the message (probably by going to a url) then put a signed hash of their email address in the wiki. now when they want to sign up for changes on a page they can add their HomePage to the Subscribe metadata field of that page. adam. |
|
From: Steve W. <sw...@pa...> - 2001-09-17 00:39:51
|
Hi Jeff, finally had some time to play with the new code you've done. It
looks great! I say go ahead and merge it into the 1.3 tree.
One request: I would like the default look-and-feel to be whatever the
browser's defaults are. This is a basic Jakob Nielsen usability issue, and
it just means (I would think) we'd provide a simple, nearly empty style
sheet. We can provide other style sheets (like the current one you use)
along with sheets contributed in the future for wikis that look like 1997
Geocities pages, if that's what people want.
Not to belabor the point, but this would mean no background color setting,
blue hyperlinks, black text, etc. I'm personally a fan of the gray
background I get on Navigator/Linux :-)
I'm anxious to see a unified interface for the database in place... this
stops me from doing other things on the todo list. I'm also really glad
you put a lot of comments in.
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
|
|
From: Steve W. <sw...@pa...> - 2001-09-17 03:14:25
|
On Fri, 14 Sep 2001, Jeff Dairiki wrote:
> > and then comments would just be:
> >
> > # blah blah
> > # please leave the below lines intact.
>
> Of course, that syntax is already used in PhpWiki for ordered lists.
> It would have to be something uglier like:
>
> // please steal this comment
Wikis are commonly used by development folks as a sort of whiteboard/on
the fly documentation system. This means any common comment tokens like
#
;
/* */
//
--
<!-- -->
are probably not a good idea, unfortunately. Hash marks are already used
by PhpWiki for numbered lists... how about:
%%
@@
or something equally wretched? I do think comments are a good thing
though.
~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
|
|
From: Adam S. <ad...@pe...> - 2001-09-17 18:47:09
|
> Wikis are commonly used by development folks as a sort of > whiteboard/on the fly documentation system. This means any common > comment tokens like probably a good point. > are probably not a good idea, unfortunately. Hash marks are already > used by PhpWiki for numbered lists... how about: > > %% > @@ what about a semi-colon? at least that is used for comments in somethings so should be kinda intuitive. or maybe two semi-colons? otherwise it doesn't really matter. oh, and i thought of another good reason for category/sub-category metadata. in intranet environments (cause i'm working on getting a wiki installed at work to replace our existing intranet). if category information is meta data then you could use it for governing permissions to view/edit/etc a page, it also means it's easier to enforce some structure on a wiki ... which i know is wiki ananthma :-) but it's also really useful for some settings. maybe you could have the drop box either be dynamically generated based off page names (preserving traditional wiki anarchy), or it could have to updated on a special page or config file (which would be great for more structured environments). anyway, just yell at me if you get sick of me spouting ideas and not contributing anything. i'm working on it. adam. |
|
From: Steve W. <sw...@pa...> - 2001-09-17 18:59:22
|
On Mon, 17 Sep 2001, Adam Shand wrote:
> > are probably not a good idea, unfortunately. Hash marks are already
> > used by PhpWiki for numbered lists... how about:
> >
> > %%
> > @@
>
> what about a semi-colon? at least that is used for comments in somethings
> so should be kinda intuitive. or maybe two semi-colons? otherwise it
> doesn't really matter.
;; this is a comment in lisp
; so is this ;-)
~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
|
|
From: Jeff D. <da...@da...> - 2001-09-17 16:14:09
|
On Sep 16, 2001, Steve Wainstead said:
>
> One request: I would like the default look-and-feel to be whatever the
> browser's defaults are. This is a basic Jakob Nielsen usability issue, and
> it just means (I would think) we'd provide a simple, nearly empty style
> sheet. We can provide other style sheets (like the current one you use)
> along with sheets contributed in the future for wikis that look like 1997
> Geocities pages, if that's what people want.
>
> Not to belabor the point, but this would mean no background color setting,
> blue hyperlinks, black text, etc. I'm personally a fan of the gray
> background I get on Navigator/Linux :-)
ure, whatever your want. Keep in mind, you can just delete the
stylesheet invocation (one -line) in each of the templates to get
the default style.
The main things the style-sheet does (currently) is:
0. Set the background colors: the cream page background (holdover
from traditional PhpWiki) and the white background behing the page
text.
1. Change the font to sans-serif.
2. Disable the underlining on WikiLinks --- the font weight is
increased
on these to distinguish them.
3. The action links ('Edit', etc...) are rendered with a gray
background,
and with a raised, button-like border (on those browsers which
support
this.)
The text (foreground) colors are not set by the style sheet --- so you
are currently seeing your browsers defaults. (Note that past versions
of PhpWiki do explicitly set the link colors to Netscape-like
blue/purple,
but that those values are not exactly the same as the colors used by
(at least) my Netscape.)
Anyhow, so (besides #0: background colors) which of the other style
features listed above do you want removed?
Jeff
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X