Talk:Welcome to the BOINC Wiki
From Pirates@Home
The main page of the new trac-based BOINC wiki at Berkeley is very stark and empty. This is a prototype of a more graphical version designed to quickly direct people to the correct major section.
The images are from the Crystal SVG, and are free to use under the LGPL. (They were developed for KDE).
If this page looks somewhat familiar, press the "Powered by MediaWiki" logo at the bottom right of this and every page in the Pirates glossary.
This is just a mock-up to try out a new look. Feel free to comment or contribute. —Wormholio 08:40, 15 May 2007 (EDT)
Contents |
Other icons?
I just used the same icon set (Crystal Clear, for KDE) that MediaWiki uses, since it does the job, but we could use different icons here to accomplish the same purpose. (Though I like the professional look of these). —Wormholio 09:28, 15 May 2007 (EDT)
What I'd really like is to see either a BOINC icon or a BOINC screensaver image on the screen under "How to Participate" —Wormholio 22:16, 28 May 2007 (EDT)
Changing “How to Participate” Icon
Something neutral and unrecognizable perhaps? The file may be too large for comfort though. —Contact 00:29, 30 May 2007 (EDT)
I like the idea. The animation seems a little slow and jerky. Unrecognizable is not necessarily the best. How about trying CPDN with the thermal map up? Or cycle through several projects, but each is up for a much longer time, like 30 sec? That would convey the idea of running several different projects. —Wormholio 07:27, 30 May 2007 (EDT)
Why not try the default BOINC screensaver that displays for projects that have no screensaver of their own? The BOINC logo text should be large enough to read and the slow and jerky movement might be lessened with the lower overhead of the simpler graphics. —Scott Brown 09:03, 30 May 2007 (EDT)
I did consider using the generic BOINC logo screensaver, but thought it wasn't what we really want to see as a screensaver. It's more of a sign that a project is ‘not ready for prime time’.
I like the idea of cycling through different project screensaver shots, but am slightly apprehensive at leaving some projects out of this loop (and at the labour involved to put this together). It does sound like something I might try this weekend. —Contact 16:36, 30 May 2007 (EDT)
The SETI@home pic is the best idea. Not just because I be lazy (wink). —Contact 23:40, 31 May 2007 (EDT)
Contact Link
All Unofficial BOINC WIKI contact links should now be linked to Special:ContactForm, not an e-mail address.
Thanks
Chris —UBWIKI Admin
Screen Reader Accessibility
I finally was able to load Welcome to the BOINC Wiki into WebbIE interface of Thunder by accessing links thru WebbIE but not by pasting in the address.
I’ve made a recording of the “spoken” page as it stands now.
The spoken version of capital letters is very annoying.
Since I just noticed that Wiki CSS has copyright there is little hope to try to solve the repeated bad pronunciation of B.O.I.N.C. there.
I can't see a solution for this problem. But I do notice that HELP is spoken correctly. Is this because help is a recognized word? —Contact 14:37, 5 August 2007 (EDT)
Wow, that's what we sound like? Thanks.
I wonder if there is some way to teach thunder how to pronounce BOINC intead of having it say B.O.I.N.C? —Wormholio 15:23, 7 August 2007 (EDT)
Perhaps try marking each instance of “BOINC” as an abbreviation, or if it’s already marked as an <abbr>, then remove that markup. More detailed control might be possible by using aural style sheets, but you’d probably need to wrap each instance of “BOINC” in a span with a class, which quickly adds to code bloat. — Lee Carre 02:57, 26 September 2007 (EDT)
Main Page, Front-End Code
I was very disheartened to find that my nice, valid, semantic, accessible code had been replaced by invalid, non-semantic, in-accessible tag-soup in one foul swoop. Especially considering the amount of time I spent bringing the page up to a half-decent standard.
This is a fundamental issue with any type of system with distributed authorship, however it’s a required essential of any quality web-site. If the tag-soup code was produced by some mindless tool then the author could be forgiven (and I can suggest some much better tools if the said author insists on using WYSI(not)WGY software to produce what should be very simple markup. Obviously the better solution would be to learn the handful of elements involved in page construction and how to use each of them correctly in order to produce super-lean, ultra-efficient, easilly-maintainable pages (in conjuction with CSS).
If none of the above suggestions are possible, then it would be best to refer any front-end coding to someone with the neccessary knowledge and experience needed to author markup and CSS correctly.
I feel my efforts would be wasted here (and better spend elsewhere) if it’s merely going to be replaced with tag-soup code.
Until this issue is resolved (I’m open to suggestions as to how exactly it’s resolved) I feel that I can no longer justify the time needed to constructively contribute to this project. — Lee Carre 02:57, 26 September 2007 (EDT)
