In WP-de you can read if you try editing an article:
Sonderzeichen: Ä Ö Ü ä ö ü ß * [ | ] { }
Please, disable this "help" now; there is already much to much clutter all over the (edit) pages. As a long time user, I know about the license stuff; I do not want to read it again and again and esp., do not yell at me using bold text.
Software or interface changes must not happen on a day-by-day base - every 6 months is enough. I asked for such a cooperation some weeks ago, but it was refused. Can we work a policey that fits for the more conservative users, too?
Karl-
In WP-de you can read if you try editing an article:
Sonderzeichen: Ä Ö Ü ä ö ü ß * [ | ] { }
Please, disable this "help" now;
This is not an issue for wikitech-l. All user interface texts can be edited. Look here: http://de.wikipedia.org/wiki/Wikipedia:MediaWiki-Namespace-Text
This one is here: http://de.wikipedia.org/wiki/MediaWiki:Copyrightwarning
Someone added the list, someone else can remove it. The messages are protected by default.
Regards,
Erik
erik_moeller@gmx.de (Erik Moeller) writes:
This is not an issue for wikitech-l. All user interface texts can be edited. Look here: http://de.wikipedia.org/wiki/Wikipedia:MediaWiki-Namespace-Text
Thanks for the info.
This one is here: http://de.wikipedia.org/wiki/MediaWiki:Copyrightwarning
They also do not know, that '<p>' means "paragraph open".
Someone added the list, someone else can remove it. The messages are protected by default.
Thus I must send a plea to them.
Am I the only one who things that having the "log out" link right above the search field isn't the best UI decision?
Mikhail Capone wrote:
Am I the only one who things that having the "log out" link right above the search field isn't the best UI decision?
Am I the only one who thinks that people should stop hitting "Reply" on a message that they're not actually replying to? :/
Timwi wrote:
Mikhail Capone wrote:
Am I the only one who things that having the "log out" link right above the search field isn't the best UI decision?
Am I the only one who thinks that people should stop hitting "Reply" on a message that they're not actually replying to? :/
Touché.
I thought that deleting the subject and body didn't leave anything; oops.
Mikhail Capone wrote:
Am I the only one who things that having the "log out" link right above the search field isn't the best UI decision?
I had never thought about it, and it's never been a problem for me. Still, I can see where a person a person who has fine motor skill difficulties could accidentally log out when try to place the cursor in the search field.
Ec
On Mar 20, 2004, at 10:45, Ray Saintonge wrote:
Mikhail Capone wrote:
Am I the only one who things that having the "log out" link right above the search field isn't the best UI decision?
I had never thought about it, and it's never been a problem for me. Still, I can see where a person a person who has fine motor skill difficulties could accidentally log out when try to place the cursor in the search field.
Gwicke is working on a new design, based vaguely on the layout for Plone: http://wiki.aulinx.de/Main_Page
Please comment!
-- brion vibber (brion @ pobox.com)
Brion Vibber wrote:
On Mar 20, 2004, at 10:45, Ray Saintonge wrote:
Mikhail Capone wrote:
Am I the only one who things that having the "log out" link right above the search field isn't the best UI decision?
I had never thought about it, and it's never been a problem for me. Still, I can see where a person a person who has fine motor skill difficulties could accidentally log out when try to place the cursor in the search field.
Gwicke is working on a new design, based vaguely on the layout for Plone: http://wiki.aulinx.de/Main_Page
Perfect! ... except the colours. :)
Brion Vibber wrote:
On Mar 20, 2004, at 10:45, Ray Saintonge wrote:
Mikhail Capone wrote:
Am I the only one who things that having the "log out" link right above the search field isn't the best UI decision?
I had never thought about it, and it's never been a problem for me. Still, I can see where a person a person who has fine motor skill difficulties could accidentally log out when try to place the cursor in the search field.
Gwicke is working on a new design, based vaguely on the layout for Plone: http://wiki.aulinx.de/Main_Page
Please comment!
Pretty, and it will deal with Mikhail's concern. I do, nevertheless, find that the print in the top banner could be 1 point bigger. The black on orange is a little difficult to see.
Ec
Brion Vibber wrote:
Gwicke is working on a new design, based vaguely on the layout for Plone: http://wiki.aulinx.de/Main_Page
Please comment!
I like it! Even the orange, though I wouldn't necessarily associate that color with an encyclopedia - *any* encyclopedia ;-)
I also had a weird glitch on the Talk page - see there.
Magnus
Brion Vibber wrote:
On Mar 20, 2004, at 10:45, Ray Saintonge wrote:
Mikhail Capone wrote:
Am I the only one who things that having the "log out" link right above the search field isn't the best UI decision?
I had never thought about it, and it's never been a problem for me. Still, I can see where a person a person who has fine motor skill difficulties could accidentally log out when try to place the cursor in the search field.
Gwicke is working on a new design, based vaguely on the layout for Plone: http://wiki.aulinx.de/Main_Page
Please comment!
Nice! It still needs some color and font size tweaking, and I can't seem to easily find "my watchlist", but it seems like a very useable and readable layout.
I'd also enjoy - and consider using as default - the _Cologne Blue_ theme if there was a way to make the "quickbar" into a frame/floating/fixed space (sorry for the lack of correct terminology).
I wish I had HTML/CSS skills and could propose a "patch", but alas...
Brion Vibber wrote:
On Mar 20, 2004, at 10:45, Ray Saintonge wrote:
Mikhail Capone wrote:
Am I the only one who things that having the "log out" link right above the search field isn't the best UI decision?
I had never thought about it, and it's never been a problem for me. Still, I can see where a person a person who has fine motor skill difficulties could accidentally log out when try to place the cursor in the search field.
Gwicke is working on a new design, based vaguely on the layout for Plone: http://wiki.aulinx.de/Main_Page
Please comment!
It seems very pratical. I like it.
-- Looxix
Brion Vibber wrote: [...]
Gwicke is working on a new design, based vaguely on the layout for Plone: http://wiki.aulinx.de/Main_Page
Please comment!
Very nice. When will this be released?
Karl Eichwalder wrote:
Software or interface changes must not happen on a day-by-day base - every 6 months is enough.
Developers are volunteers. They make changes in their free time. Understandably, they would be deterred from doing any development if they would have to wait for 6 months (do you know just how long that is?) for their changes to go live.
Timwi timwi@gmx.net writes:
Developers are volunteers.
Writers are volunteers - so what's your point?
They make changes in their free time. Understandably, they would be deterred from doing any development if they would have to wait for 6 months (do you know just how long that is?) for their changes to go live.
Many a lot writers (and readers) depend on the system. The system isn't there to make (some) developers happy instantly. Widen your view! These days it takes years until a new Emacs version will hit the shelves. Do you know how often Knuth updates his system?
Only little children and children of the beat generation want to have all things NOW - later on, you may recognize time is not linear.
Sure, fixing bugs is important and must done as fast as possibile. I'm still hoping someone sees my point.
Karl Eichwalder wrote:
Timwi timwi@gmx.net writes:
Developers are volunteers.
Writers are volunteers - so what's your point?
So do you want to restrict writers to only being able to update their articles every 6 months too?
The system isn't there to make (some) developers happy instantly.
I'm afraid if it doesn't, then development won't get ahead. That's just the way it is.
Timwi
Timwi wrote:
Karl Eichwalder wrote:
Software or interface changes must not happen on a day-by-day base - every 6 months is enough.
Developers are volunteers. They make changes in their free time. Understandably, they would be deterred from doing any development if they would have to wait for 6 months (do you know just how long that is?) for their changes to go live.
I admit that I had never considered that requiring a little patience was an act of cruelty to developers. :-)
The rate at which software changes are applied should probably depend on the nature of the change. Changes that have a high impact on the way that most of us non-techies do things should be made permanent only after the most careful consideration of the human engineering aspects. Other, changes that operate mostly in the background can probably be implemented more quickly.
People can be very uncomfortable with sudden changes. The recent sudden appearance of suggested details in the edit summary box may have been technologically very simple, but reactions need to be anticipated when the broad population of users unexpectedly run into such changes.
Ec
wikitech-l@lists.wikimedia.org