[I will use [NEWS] for all official announcements and notices I consider
generally relevant for users of SMW, to let you filter those from standard
we will soon (today) release SMW 1.2.1 as a minor update to SMW 1.2 that
includes many relevant bugfixes. To upgrade from SMW 1.2, it is enough to
just replace the SemanticMediaWiki directory with the new code.
SMW 1.2.1 is mainly a bugfix release that fixes problems with SMW 1.2. Besides
this, SMW now also displays subproperties on property pages, like at
There were also some improvements in parsing numbers (support for French
notation with spaces).
But the most important change are the following bugfixes:
* Problems with the update jobs: under certain conditions, update jobs could
create wrong semantic annotations, and in many other cases they would not
work properly. Jobs are now much more reliable.
* Editing of all Type pages works again.
* __NOFACTBOX__ works properly again.
* Properties of Type:Text and Type:Code do show their values on their property
* Type:Code values display properly in the Factbox in all cases
* Certain PHP crashes, resulting in server errors or in "index.php" to be
offered for download, are now avoided. I will send a separate email on this.
Semantic MediaWiki http://semantic-mediawiki.orghttp://korrekt.org markus@...
A while back in "[Semediawiki-user] [NEWS] SMW 1.2.1 to be released
today", Markus Krötzsch wrote:
> * Properties of Type:Text and Type:Code do show their values on their property
> page now.
> * Type:Code values display properly in the Factbox in all cases
So what does Type:Code do? I couldn't find documentation or other
mention of it on the mailing list. From SVN it looks like it showed up
in SMW 1.2 but http://semantic-mediawiki.org/wiki/Semantic_MediaWiki_1.2
doesn't mention it. It seems to display its result in a <pre>formatted
code box, but only in the page -- not in query results, not in
Special:Ask, Special:Browse, or "Pages using the property" lists.
I added the above information to
but someone with more knowledge should review.
Like Type:Text, Type:Code doesn't work with the (soon-to-be expired?)
service links feature.
It seems overkill to introduce a new type just for some formatting,
since you can just do
[[My property::SOME CODE HERE|<pre>SOME CODE HERE</pre>]]
or use a template. Was there some other issue making a datatype necessary?
I think Type:Code should serve as a use case for user-controlled
formatting. Users should be able to say "display this property's values
using <pre> in the wiki page and using <tt> in the factbox and query
results." without having to write new PHP code.
Speaking of slight variations on datatypes, I need a Type:ID datatype
that works like a number but without the comma thousands separator,
should I put in an enhancement request?