From: Dan F. <dfr...@cs...> - 2004-04-26 15:07:20
|
Three little patches with rewording or interface. Take them or not at your convenience. Dan 1) UserPreferences link I have found it awkward to explain to people how to change their user preferences. Thus, I put a link to UserPreferences next to their login when logged in. I am not sure this is the right interface yet (gotta see how people react to it). However, I submit a patch for it anyway. diff -w -b -u -r1.1.1.2 signin.tmpl --- themes/default/templates/signin.tmpl 14 Apr 2004 21:23:06 -0000 1.1.1.2 +++ themes/default/templates/signin.tmpl 23 Apr 2004 20:59:37 -0000 @@ -15,7 +15,8 @@ $Sep = $Theme->getButtonSeparator(); $SignOutB = $Theme->makeButton(_("Sign Out"), "javascript:SignOut();", 'wikiaction'); ?> - <?= fmt("Authenticated as %s", WikiLink($user->getAuthenticatedId(), 'auto')) ?> + <?= fmt("Authenticated as %s (%s)", WikiLink($user->getAuthenticatedId(), 'auto'), + WikiLink(_("UserPreferences"), 'auto')) ?> <?=$Sep?> <script language="JavaScript" type="text/javascript"><!-- document.write('<input type="hidden" name="auth[logout]" value="0" />'); 2) Email notifications help text Here is a minor rewording of the help text for the email notifications page. diff -b -u -r1.1.1.2 userprefs.tmpl --- themes/default/templates/userprefs.tmpl 14 Apr 2004 21:23:06 -0000 1.1.1.2 +++ themes/default/templates/userprefs.tmpl 26 Apr 2004 14:57:09 -0000 @@ -157,7 +157,7 @@ <?=_("Get an email notification at changes of the following pages:")?><br /> <?php if ($isForm) { ?> <blockquote><textarea name="pref[notifyPages]" cols="50" rows="4"><?=$pref->get('notifyPages')?></textarea></blockquote></td> - <td><span class="hint"><?=_("Enter pages seperated by space or comma. Wildcards (fileglobbing) allowed.")?></span></td> + <td><span class="hint"><?=_("Enter pages separated by space or comma. Wildcards * and ? allowed. For example, to see all pages, just put *; to see all pages Home1, Home2, HomeA, but not HomeAB, put Home?.")?></span></td> <?php } else { ?> <td><?=$pref->get('notifyPages')?></td><td></td> <?php } ?> 3) Email notifications subject line diff -w -b -u -r1.5 -r1.6 --- lib/WikiDB.php 14 Apr 2004 21:57:25 -0000 1.5 +++ lib/WikiDB.php 26 Apr 2004 14:55:43 -0000 1.6 @@ -896,7 +896,7 @@ } if (!empty($emails)) { $emails = array_unique($emails); - $subject = sprintf(_("PageChange Notification %s"),$this->_pagename); + $subject = sprintf(_("Page '%s' changed"),$this->_pagename); $previous = $backend->get_previous_version($this->_pagename, $version); if ($previous) { $difflink = WikiUrl($this->_pagename,array('action'=>'diff'),true); |
Re: [Phpwiki-talk] Patch for UserPreferences link, notification pref
help, notification subject line
From: Reini U. <ru...@x-...> - 2004-04-26 18:11:21
|
Dan Frankowski schrieb: > Three little patches with rewording or interface. Take them or not at > your convenience. > > Dan > > 1) UserPreferences link > > I have found it awkward to explain to people how to change their user > preferences. Thus, I put a link to UserPreferences next to their login > when logged in. I am not sure this is the right interface yet (gotta see > how people react to it). However, I submit a patch for it anyway. Hmm, don't they see their "Preferences" actionbar.tmpl link at the top? This appears for every authenticated user. (based on the default theme) To add it to the signin message after login is also okay, but then we should make it more verbose. But at the lower right we don't have enough room for that. > diff -w -b -u -r1.1.1.2 signin.tmpl > --- themes/default/templates/signin.tmpl 14 Apr 2004 21:23:06 > -0000 1.1.1.2 > +++ themes/default/templates/signin.tmpl 23 Apr 2004 20:59:37 -0000 > @@ -15,7 +15,8 @@ > $Sep = $Theme->getButtonSeparator(); > $SignOutB = $Theme->makeButton(_("Sign Out"), > "javascript:SignOut();", 'wikiaction'); > ?> > - <?= fmt("Authenticated as %s", WikiLink($user->getAuthenticatedId(), > 'auto')) ?> > + <?= fmt("Authenticated as %s (%s)", > WikiLink($user->getAuthenticatedId(), 'auto'), > + WikiLink(_("UserPreferences"), 'auto')) ?> > <?=$Sep?> > <script language="JavaScript" type="text/javascript"><!-- > document.write('<input type="hidden" name="auth[logout]" value="0" > />'); > 2) Email notifications help text > Here is a minor rewording of the help text for the email notifications > page. > - <td><span class="hint"><?=_("Enter pages seperated by space or > comma. Wildcards (fileglobbing) allowed.")?></span></td> > + <td><span class="hint"><?=_("Enter pages separated by space or > comma. Wildcards * and ? allowed. For example, to see all pages, just > put *; to see all pages Home1, Home2, HomeA, but not HomeAB, put > Home?.")?></span></td> Hmm, good idea, but not the best example. We should avoid a dot. > 3) Email notifications subject line > - $subject = sprintf(_("PageChange Notification %s"),$this->_pagename); > + $subject = sprintf(_("Page '%s' changed"),$this->_pagename); This makes filtering harder. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
Re: [Phpwiki-talk] Patch for UserPreferences link, notification pref
help, notification subject line
From: Dan F. <dfr...@cs...> - 2004-04-26 21:39:51
|
Reini Urban wrote: > Dan Frankowski schrieb: > >> Three little patches with rewording or interface. Take them or not at >> your convenience. >> >> Dan >> >> 1) UserPreferences link >> >> I have found it awkward to explain to people how to change their user >> preferences. Thus, I put a link to UserPreferences next to their >> login when logged in. I am not sure this is the right interface yet >> (gotta see how people react to it). However, I submit a patch for it >> anyway. > > > Hmm, don't they see their "Preferences" actionbar.tmpl link at the top? > This appears for every authenticated user. (based on the default theme) 1. I apologize for my denseness, but I cannot find this. I can't see it on a page (try http://www.wikilens.org), and I can't find any reference to preferences or users in actionbar.tmpl. Also, the only template included is 'signin' at the bottom. I am missing something obvious. By the way, our actionbar.tmpl is like 1.3.9. I do see some stuff in head.tmpl, but cannot figure out where that is being included. I read Map.pdf, and am still confused. :-( Sorry. 2. Even if that were true, there should be a preferences link whenever you are logged in even if you are not authenticated yet, because the only way to get authenticated is to visit your preferences and set your email. Am I missing something here too? > To add it to the signin message after login is also okay, but then we > should make it more verbose. > But at the lower right we don't have enough room for that. I think I will understand this better once I see the message you are referring to. >> --- themes/default/templates/signin.tmpl 14 Apr 2004 21:23:06 >> -0000 1.1.1.2 >> +++ themes/default/templates/signin.tmpl 23 Apr 2004 20:59:37 >> -0000 >> @@ -15,7 +15,8 @@ >> $Sep = $Theme->getButtonSeparator(); >> $SignOutB = $Theme->makeButton(_("Sign Out"), >> "javascript:SignOut();", 'wikiaction'); >> ?> >> - <?= fmt("Authenticated as %s", >> WikiLink($user->getAuthenticatedId(), 'auto')) ?> >> + <?= fmt("Authenticated as %s (%s)", >> WikiLink($user->getAuthenticatedId(), 'auto'), >> + WikiLink(_("UserPreferences"), 'auto')) ?> >> <?=$Sep?> >> <script language="JavaScript" type="text/javascript"><!-- >> document.write('<input type="hidden" name="auth[logout]" >> value="0" />'); > > diff -w -b -u -r1.1.1.2 signin.tmpl > >> 2) Email notifications help text >> Here is a minor rewording of the help text for the email >> notifications page. >> - <td><span class="hint"><?=_("Enter pages seperated by space or >> comma. Wildcards (fileglobbing) allowed.")?></span></td> >> + <td><span class="hint"><?=_("Enter pages separated by space or >> comma. Wildcards * and ? allowed. For example, to see all pages, >> just put *; to see all pages Home1, Home2, HomeA, but not HomeAB, put >> Home?.")?></span></td> > > > Hmm, good idea, but not the best example. We should avoid a dot. You mean the period at the very end? Probably true. How about: _("Enter pages separated by space or comma. Wildcards * and ? allowed. For example, to see all pages, just put \"*\" (without the quotes); to see all pages Home1, Home2, HomeA, but not HomeAB, put \"Home?\" (without the quotes).") >> - $subject = sprintf(_("PageChange Notification %s"),$this->_pagename); >> + $subject = sprintf(_("Page '%s' changed"),$this->_pagename); > > 3) Email notifications subject line > > This makes filtering harder. Every notification I get has "[WikiLens]" at the beginning (the name of the Wiki from index.php), which nicely looks very much like other notification tags (e.g., Mailman). This is what I would filter on. Is that bad? I was just looking to change the text to something that a Wiki-naive user would not be afraid of. "PageChange" is unusual capitalization for English. Also, "PageChange Notification" is very official. Could do "Page changed: %s". Thanks for your attention to these. Dan |
Re: [Phpwiki-talk] Patch for UserPreferences link, notification pref
help, notification subject line
From: Reini U. <ru...@x-...> - 2004-04-26 22:18:42
|
Dan Frankowski schrieb: > Reini Urban wrote: >> Hmm, don't they see their "Preferences" actionbar.tmpl link at the top? >> This appears for every authenticated user. (based on the default theme) > > 1. I apologize for my denseness, but I cannot find this. I can't see it > on a page (try http://www.wikilens.org), and I can't find any reference > to preferences or users in actionbar.tmpl. Also, the only template > included is 'signin' at the bottom. I am missing something obvious. By > the way, our actionbar.tmpl is like 1.3.9. I do see some stuff in > head.tmpl, but cannot figure out where that is being included. I read > Map.pdf, and am still confused. :-( Sorry. Sorry, i mixed it up. So far it's only in themes/smaller/templates/navbar.tmpl: add this to your navbar: <?php if (!empty($user) && $user->isSignedIn()) { ?> <?=$s?><?= WikiLink(_("UserPreferences"), "","Preferences") ?> <?php } ?> (actionbar is the bottom line, navbar the top line) > 2. Even if that were true, there should be a preferences link whenever > you are logged in even if you are not authenticated yet, because the > only way to get authenticated is to visit your preferences and set your > email. Am I missing something here too? email has nothing to do with authentication. you just have to login with the correct password, or if none, if none set. >>> "Enter pages separated by space or >>> comma. Wildcards * and ? allowed. For example, to see all pages, >>> just put *; to see all pages Home1, Home2, HomeA, but not HomeAB, put >>> Home?." >> >> Hmm, good idea, but not the best example. We should avoid a dot. > > You mean the period at the very end? Probably true. How about: > > _("Enter pages separated by space or comma. Wildcards * and ? allowed. > For example, to see all pages, just put \"*\" (without the quotes); to > see all pages Home1, Home2, HomeA, but not HomeAB, put \"Home?\" > (without the quotes).") Enter pages separated by space or comma. The wildcards * and ? are allowed as in file globbing. For example use * for all pages, Php* for all all pages starting with Php, and use Home? for the pages Home1, Home2, HomeA, but not HomeOther. >>> - $subject = sprintf(_("PageChange Notification %s"),$this->_pagename); >>> + $subject = sprintf(_("Page '%s' changed"),$this->_pagename); >> >> 3) Email notifications subject line >> >> This makes filtering harder. > > Every notification I get has "[WikiLens]" at the beginning (the name of > the Wiki from index.php), which nicely looks very much like other > notification tags (e.g., Mailman). This is what I would filter on. Is > that bad? That's the first filter criterion for the wikisite. The second criterion is the string "PageChange Notification". I have multiple wiki's to follow. My folders layout e.g. is: phpwiki -> demo -> notify -> phpwiki -> notify -> acadwiki -> notify -> arch.x -> notify -> other -> notify Or maybe: phpwiki -> talk -> checkins -> forums -> notify -> demo -> phpwiki -> acadwiki -> arch.x -> other To have a strong enough filter for the default notify case I prefer (contains "] PageChange Notification ") over (contains "] Page ") > I was just looking to change the text to something that a Wiki-naive > user would not be afraid of. "PageChange" is unusual capitalization for > English. Also, "PageChange Notification" is very official. Could do > "Page changed: %s". Maybe "PagechangeNotification"? Seems to sound more unwiki to me. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
Re: [Phpwiki-talk] Patch for UserPreferences link, notification pref
help, notification subject line
From: Dan F. <dfr...@cs...> - 2004-04-27 15:27:18
|
Reini Urban wrote: > Dan Frankowski schrieb: > >> Reini Urban wrote: >> >>> Hmm, don't they see their "Preferences" actionbar.tmpl link at the top? >>> This appears for every authenticated user. (based on the default theme) >> > > > >> 1. I apologize for my denseness, but I cannot find this. I can't see >> it on a page (try http://www.wikilens.org), and I can't find any >> reference to preferences or users in actionbar.tmpl. Also, the only >> template included is 'signin' at the bottom. I am missing something >> obvious. By the way, our actionbar.tmpl is like 1.3.9. I do see some >> stuff in head.tmpl, but cannot figure out where that is being >> included. I read Map.pdf, and am still confused. :-( Sorry. > > > Sorry, i mixed it up. So far it's only in > themes/smaller/templates/navbar.tmpl: > > add this to your navbar: > <?php if (!empty($user) && $user->isSignedIn()) { ?> > <?=$s?><?= WikiLink(_("UserPreferences"), "","Preferences") ?> > <?php } ?> > > (actionbar is the bottom line, navbar the top line) Sounds good. Well, I'm glad that it's in somewhere. I'd say: a. It should be in the default theme. b. I would claim it should be as near to the username as possible. When I think my username, I also think about preferences. Thus, I will leave it in the signin bar in my copy, since that's where the username is. I understand that you may disagree, and that's okay. Of course I'd prefer it if that made it to the mainline, but not crucial. > >> 2. Even if that were true, there should be a preferences link >> whenever you are logged in even if you are not authenticated yet, >> because the only way to get authenticated is to visit your >> preferences and set your email. Am I missing something here too? > > > email has nothing to do with authentication. you just have to login > with the correct password, or if none, if none set. Ah, thanks for that clarification. > >>>> "Enter pages separated by space or comma. Wildcards * and ? >>>> allowed. For example, to see all pages, just put *; to see all >>>> pages Home1, Home2, HomeA, but not HomeAB, put Home?." >>> >>> >>> Hmm, good idea, but not the best example. We should avoid a dot. >> >> >> You mean the period at the very end? Probably true. How about: >> >> _("Enter pages separated by space or comma. Wildcards * and ? >> allowed. For example, to see all pages, just put \"*\" (without the >> quotes); to see all pages Home1, Home2, HomeA, but not HomeAB, put >> \"Home?\" (without the quotes).") > > > Enter pages separated by space or comma. The wildcards * and ? are > allowed as in file globbing. For example use * for all pages, > Php* for all all pages starting with Php, > and use Home? for the pages Home1, Home2, HomeA, but not HomeOther. How about: Enter pages separated by space or comma. Use wildcards * to match any text, and ? to match any single character. Examples using *: * for all pages, Php* for all pages starting with Php. Examples using ?: Home? for the pages Home1, Home2, HomeA, but not HomeOther. I am trying to avoid "file globbing." I know what that means, but most people don't. >>>> + $subject = sprintf(_("Page '%s' changed"),$this->_pagename); >>> >>> >>> 3) Email notifications subject line >>> >>> This makes filtering harder. >> >> >> Every notification I get has "[WikiLens]" at the beginning (the name >> of the Wiki from index.php), which nicely looks very much like other >> notification tags (e.g., Mailman). This is what I would filter on. Is >> that bad? > > - $subject = sprintf(_("PageChange Notification %s"),$this->_pagename); > > That's the first filter criterion for the wikisite. > The second criterion is the string "PageChange Notification". I have > multiple wiki's to follow. My folders layout e.g. is: > phpwiki -> demo -> notify > -> phpwiki -> notify > -> acadwiki -> notify > -> arch.x -> notify > -> other -> notify > Or maybe: > phpwiki -> talk > -> checkins > -> forums > -> notify -> demo > -> phpwiki > -> acadwiki > -> arch.x > -> other > To have a strong enough filter for the default notify case > I prefer (contains "] PageChange Notification ") over > (contains "] Page ") > >> I was just looking to change the text to something that a Wiki-naive >> user would not be afraid of. "PageChange" is unusual capitalization >> for English. Also, "PageChange Notification" is very official. Could >> do "Page changed: %s". > > > Maybe "PagechangeNotification"? > Seems to sound more unwiki to me. I am not looking for unwiki (i.e., not Wiki-like). I'm looking for understandable to any user, even those who don't know about wikis, even nontechnical users. I think most users would understand "Page changed: %s". I think it's easy and robust to filter on "] Page changed:". I think "PageChange Notification" and "PagechangeNotification" are both not normal English. They would not be published in a newspaper. They are multiple words run together with unusual capitalization. Also, simple English favors short words. "changed" is 2 syllables, "notification" is 5 syllables, so I am trying to avoid that word. Thanks for your attention. Dan |
Re: [Phpwiki-talk] Patch for UserPreferences link, notification pref
help, notification subject line
From: Reini U. <ru...@x-...> - 2004-04-27 16:29:41
|
Dan Frankowski schrieb: > Reini Urban wrote: >> Dan Frankowski schrieb: >>> Reini Urban wrote: >> add this to your navbar: >> <?php if (!empty($user) && $user->isSignedIn()) { ?> >> <?=$s?><?= WikiLink(_("UserPreferences"), "","Preferences") ?> >> <?php } ?> Will be added to the default navbar.tmpl, before "Admin". > Sounds good. Well, I'm glad that it's in somewhere. I'd say: > > a. It should be in the default theme. > b. I would claim it should be as near to the username as possible. When > I think my username, I also think about preferences. Thus, I will leave > it in the signin bar in my copy, since that's where the username is. I > understand that you may disagree, and that's okay. Of course I'd prefer > it if that made it to the mainline, but not crucial. And what I don't like is that navbar links look like actionbar buttons. (technically they are, but...) I changed that in the latest "smaller" theme, where the navbar consists entirely of WikiLinks, and the actionbar of the rounded buttons. >> Enter pages separated by space or comma. The wildcards * and ? are >> allowed as in file globbing. For example use * for all pages, >> Php* for all all pages starting with Php, >> and use Home? for the pages Home1, Home2, HomeA, but not HomeOther. > > How about: > > Enter pages separated by space or comma. Use wildcards * to match any > text, and ? to match any single character. Examples using *: * for all > pages, Php* for all pages starting with Php. Examples using ?: Home? for > the pages Home1, Home2, HomeA, but not HomeOther. > > I am trying to avoid "file globbing." I know what that means, but most > people don't. Adding it in parentheseis doesn't hurt for the users who know what it means, they will to skip the whole paragraph, because they know about ^.*$ and ?* then. >> Maybe "PagechangeNotification"? >> Seems to sound more unwiki to me. > > I am not looking for unwiki (i.e., not Wiki-like). I'm looking for > understandable to any user, even those who don't know about wikis, even > nontechnical users. I think most users would understand "Page changed: > %s". I think it's easy and robust to filter on "] Page changed:". > > I think "PageChange Notification" and "PagechangeNotification" are both > not normal English. They would not be published in a newspaper. They are > multiple words run together with unusual capitalization. Well, this is wiki and not a newspaper. Users do strange - almost german :) - things with words in wikis. Since this is just about a subject line, and not about webpage usability for random users, I don't think that "normal english" would overrule "technical english". > Also, simple English favors short words. "changed" is 2 syllables, "notification" is > 5 syllables, so I am trying to avoid that word. Sure. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
From: Whit B. <wh...@tr...> - 2004-04-27 17:31:12
|
> >I think "PageChange Notification" and "PagechangeNotification" are both > >not normal English. They would not be published in a newspaper. They are > >multiple words run together with unusual capitalization. > > Well, this is wiki and not a newspaper. > Users do strange - almost german :) - things with words in wikis. Since > this is just about a subject line, and not about webpage usability for > random users, I don't think that "normal english" would overrule > "technical english". > > >Also, simple English favors short words. "changed" is 2 syllables, > >"notification" is 5 syllables, so I am trying to avoid that word. > > Sure. How about "Page Change Notice" (or "PageChangeNotice" or whatever)? A "notice" may also be called a "notification," but that's a bit of a bastard word mostly used on envelopes falsely suggesting that you've won some million-dollar contest. When the law requires a public statment be published in a newspaper, the standard heading is "Public Notice", _not_ "Notification." What's at issue here is really the Norman Invasion, and the injection of pretentious Latinate vocabulary among the fine Germanic grunts previously practiced by the English ... in any case "notification" is a bullshit (pardon my Anglo-Saxon) word in most of its uses. Running it together like German is normal computer-speak since at least WordStar, but going French with it...? ; > Whit |
From: Dan F. <dfr...@cs...> - 2004-04-27 19:38:10
|
Whit Blauvelt wrote: >>>I think "PageChange Notification" and "PagechangeNotification" are both >>>not normal English. They would not be published in a newspaper. They are >>>multiple words run together with unusual capitalization. >>> >>> >>Well, this is wiki and not a newspaper. >>Users do strange - almost german :) - things with words in wikis. Since >>this is just about a subject line, and not about webpage usability for >>random users, I don't think that "normal english" would overrule >>"technical english". >> >> >> >>>Also, simple English favors short words. "changed" is 2 syllables, >>>"notification" is 5 syllables, so I am trying to avoid that word. >>> >>> >>Sure. >> >> > >How about "Page Change Notice" (or "PageChangeNotice" or whatever)? > Why not just "Page change"? What does "notice" add? Of course it's a notice, I just got an email about it. >What's at issue here is really the Norman Invasion .. > While it is true that the Norman invasion had a strong effect on the English language, and that part of that influence is that informal words are often Germanic, more formal words Latin, I'd rather focus on this: whatever current English conventions for good speech and writing are at present, let's use those. Dan |
Re: [Phpwiki-talk] Patch for UserPreferences link, notification pref
help, notification subject line
From: Dan F. <dfr...@cs...> - 2004-04-27 19:35:32
|
Reini Urban wrote: > Dan Frankowski schrieb: > >> Reini Urban wrote: >> >>> Dan Frankowski schrieb: >>> >>>> Reini Urban wrote: >>> >>> add this to your navbar: >>> <?php if (!empty($user) && $user->isSignedIn()) { ?> >>> <?=$s?><?= WikiLink(_("UserPreferences"), "","Preferences") ?> >>> <?php } ?> >> > > Will be added to the default navbar.tmpl, before "Admin". > >> Sounds good. Well, I'm glad that it's in somewhere. I'd say: >> >> a. It should be in the default theme. >> b. I would claim it should be as near to the username as possible. >> When I think my username, I also think about preferences. Thus, I >> will leave it in the signin bar in my copy, since that's where the >> username is. I understand that you may disagree, and that's okay. Of >> course I'd prefer it if that made it to the mainline, but not crucial. > > > And what I don't like is that navbar links look like actionbar > buttons. (technically they are, but...) > I changed that in the latest "smaller" theme, where the navbar > consists entirely of WikiLinks, and the actionbar of the rounded buttons. I see. When I looked at "smaller" this all made more sense. I agree that all links or all buttons looks better. I had users complain about that, too. However: - It should be in the default theme, then. I was looking all default. (You said that's the plan.) Not only the prefs link, but the all-links all-buttons idea. - Even in "smaller", the userid is still in the lower right, and it's still a link among buttons. Hence, I'd still put prefs near the id. On the other hand, it might be cool to put the signin and id at the top. I had several users ask me about that ("I can't find where to sign in."). > >>> Enter pages separated by space or comma. The wildcards * and ? are >>> allowed as in file globbing. For example use * for all pages, >>> Php* for all all pages starting with Php, >>> and use Home? for the pages Home1, Home2, HomeA, but not HomeOther. >> >> >> How about: >> >> Enter pages separated by space or comma. Use wildcards * to match any >> text, and ? to match any single character. Examples using *: * for >> all pages, Php* for all pages starting with Php. Examples using ?: >> Home? for the pages Home1, Home2, HomeA, but not HomeOther. >> >> I am trying to avoid "file globbing." I know what that means, but >> most people don't. > > > Adding it in parentheseis doesn't hurt for the users who know what it > means, they will to skip the whole paragraph, because they know about > ^.*$ and ?* then. Yikes. I would put this at the end, then. I thought I knew about file-globbing, but I didn't understand all this. I know ^ (begin-line), $ (end-line), * (match string), ? (match char), but .? In general, make your audience as wide as possible. > >>> Maybe "PagechangeNotification"? >>> Seems to sound more unwiki to me. >> >> >> I am not looking for unwiki (i.e., not Wiki-like). I'm looking for >> understandable to any user, even those who don't know about wikis, >> even nontechnical users. I think most users would understand "Page >> changed: %s". I think it's easy and robust to filter on "] Page >> changed:". >> >> I think "PageChange Notification" and "PagechangeNotification" are >> both not normal English. They would not be published in a newspaper. >> They are multiple words run together with unusual capitalization. > > > Well, this is wiki and not a newspaper. > Users do strange - almost german :) - things with words in wikis. > Since this is just about a subject line, and not about webpage > usability for random users, I don't think that "normal english" would > overrule "technical english". I would love to convince you otherwise! In general, I am aiming for an application that anyone can use for the basics, but motivated users can learn more and do more. That means wherever possible, normal English is better. This *is* about webpage usability for random users. My explicit goal in WikiLens is: 1. Anyone who knows how to use a web browser can find items, rate them, and get value from that (recommendations, most popular, whatever). 2. Motivated users (say, top 10% of web browsing people) can learn how to add items. They may have to know how the Wiki works, but I hope not. 3. Unusually motivated users (say, top 10% of item-adding people) can learn how to add categories. This is a crucial point, because I plan to invest significant effort to try to respond to my type-1 users' comments that it is hard to use by making the UI more friendly to the average user. If you believe that the Wiki is for technical users first, all of my changes will be objected to, discarded, and useless. You could say, "Make your own theme", but this reaches much deeper than theme! This wording is an example, where I can't control it in a theme. I know, you plan to make it configurable, but I strongly believe the underlying philosophy of the *whole system* should be 'average users where possible'! This kind of usability will not ultimately be themeable, it needs buy-in from the developers; there will always be new features, etc. The fact that this is an email subject line makes it even *more* important to be normal English, not less, because it's not even a Wiki. It's an email, and users expect emails to be in their world, not a foreign Wiki world. I like Wikis fine, but I believe to the extent possible (!) they should look like what people want, not train people to understand how this Wiki works. The reason is that then I will be able to get 10X more users, because 90% of the web browsing people will not bother to learn about unfriendly Wikis, they'll just leave. Another example: Logins should not have to be a Wiki word. I plan to make this mod later on. Current behavior goes against web convention. No user I explain WikiLens to likes the fact that their login has to be a Wiki word. - "What's a Wiki word?" - "Why isn't DanF enough?" - "I tried to create login foobar and it said 'Insufficient permissions'. Do you have to open the Wiki up?" (That's yet another thing: it's got to distinguish Insufficient permissions and illegal login name.) Blah blah. It's just not worth the hassle to them. I have to explain it to everyone, and I can't do that much explaining. It's got to be easy or they won't use it. Note that Wikipedia allows a login that looks like other web logins. This non-Wiki-ish usability for browsing and rating is absolutely crucial! What can I do to help convince you? Dan |