User:Skierpage: Difference between revisions

From KDE TechBase
m (fix link)
(frustrated with TechBase, list of problems)
Line 3: Line 3:


I mostly do documentation and support for Semantic MediaWiki, an extension to MediaWiki.
I mostly do documentation and support for Semantic MediaWiki, an extension to MediaWiki.
== Techbase problems and what I'm going to do about them ==
2011-11-14: I'm frustrated as hell trying to figure out a problem with KDE (Strigi not indexing my stuff), and TechBase is ''not'' helping.
=== Service page problems ===
The Nepomuk blog's [http://nepomuk.kde.org/node/2 Documentation] page has a Strigi Service link that goes to [[Development/Tutorials/Metadata/Nepomuk/StrigiService]]
unfortunately this suffers from the same problems as the blog's Documentation page
* BUG: doesn't say where the source is
* BUG: doesn't say where the API is
* BUG: doesn't say what the service looks like.  Is it a process I can look at?  What's the process name
* TODO: techbase needs to have {{tl:source}}, {{tl:api}}, {{tl:processname}} templates for creating links to these, and should have a series of form template that presents this sort of information about a project in an infobox:
  <nowiki>{{</nowiki>service| source= | api= | processname= | bugtracker= | kdemodule= | blog= }}
TODO: the split between userbase and techbase is dubious. I'm a user, but I want to go beyond the user documentation. You're just going to duplicate information like the processname, the blog, the bug tracker and the kdemodule in two wikis.
BUG: WTF happened to [[Getting Started]]? It used to have "Getting the source", now that's gone!
=== Techbase minor bugs ===
BUG: [[Template:Info]] is undocumented!  Use <nowiki><noinclude> </noinclude></nowiki> to document what templates do!
BUG: [[Help:Contents]] says to use
  <nowiki><span class="bsBugLink bsError bsError-NoConnection">{{bug|123456}}</span></nowiki>
surely this HTML formatting junk should be part of a template, i.e. {{formatted_bug|xxx}}
BUG: Template:Template has a silly confusing warning
"If this page is not already in the "Template" namespace, it should probably be migrated to that location."
Instead, someone should just periodically look at [[WhatLinksHere/Template:Template]] and see if pages outside Category:Template are using it.
BUG: pull in [[Template:Tl]] from Wikipedia, so that instead of fiddling with <nowiki>{{</nowiki> you can use e.g. {{tl|bug}} to generate a nicely-formatted <nowiki>{{</nowiki>[[Template:bug|bug]]}} which is also a link to a template.
BUG: need a template or namespace for linking to Wikipedia. A template could be smart about language.
BUG: have a namespace for linking to userbase
==== Layout bugs ====
BUG: In three-column listings like [[Category:Template]] , the techbase wiki skin makes the listing overlap the right-hand "Share your Knowledge" column.
BUG: In revision history the
:Revision as of 21:55, 20 May 2009 by JRT (Talk | contribs)<br />(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
crashes into the light header with [View the content page] [Discussion about the content page] icons.
BUG: justified text looks bad in a narrow window.  Allow ragged right column
MAYBE: pre text just goes on and on off the right side. Consider using the wrap attribute of pre so that stuff wraps.
== TechBase problems done ==
* fixed [[Template:Template]] to explain what it does
*

Revision as of 21:42, 14 November 2011

I first used Projects/KDE_on_Windows but now run Kubuntu as my main operating system. I wrote an occasional journal of my adventures in getting Kubuntu working at userbase.kde.org user page

I mostly do documentation and support for Semantic MediaWiki, an extension to MediaWiki.

Techbase problems and what I'm going to do about them

2011-11-14: I'm frustrated as hell trying to figure out a problem with KDE (Strigi not indexing my stuff), and TechBase is not helping.

Service page problems

The Nepomuk blog's Documentation page has a Strigi Service link that goes to Development/Tutorials/Metadata/Nepomuk/StrigiService unfortunately this suffers from the same problems as the blog's Documentation page

  • BUG: doesn't say where the source is
  • BUG: doesn't say where the API is
  • BUG: doesn't say what the service looks like. Is it a process I can look at? What's the process name
 {{service| source= | api= | processname= | bugtracker= | kdemodule= | blog= }}

TODO: the split between userbase and techbase is dubious. I'm a user, but I want to go beyond the user documentation. You're just going to duplicate information like the processname, the blog, the bug tracker and the kdemodule in two wikis.

BUG: WTF happened to Getting Started? It used to have "Getting the source", now that's gone!

Techbase minor bugs

BUG: Template:Info is undocumented! Use <noinclude> </noinclude> to document what templates do!

BUG: Help:Contents says to use

 <span class="bsBugLink bsError bsError-NoConnection">{{bug|123456}}</span>

surely this HTML formatting junk should be part of a template, i.e. Template:Formatted bug

BUG: Template:Template has a silly confusing warning "If this page is not already in the "Template" namespace, it should probably be migrated to that location."

Instead, someone should just periodically look at WhatLinksHere/Template:Template and see if pages outside Category:Template are using it.

BUG: pull in Template:Tl from Wikipedia, so that instead of fiddling with {{ you can use e.g. {{bug}} to generate a nicely-formatted {{bug}} which is also a link to a template.

BUG: need a template or namespace for linking to Wikipedia. A template could be smart about language.

BUG: have a namespace for linking to userbase


Layout bugs

BUG: In three-column listings like , the techbase wiki skin makes the listing overlap the right-hand "Share your Knowledge" column.

BUG: In revision history the

Revision as of 21:55, 20 May 2009 by JRT (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

crashes into the light header with [View the content page] [Discussion about the content page] icons.

BUG: justified text looks bad in a narrow window. Allow ragged right column

MAYBE: pre text just goes on and on off the right side. Consider using the wrap attribute of pre so that stuff wraps.


TechBase problems done