Hi folks,
I've been reading your thread on "AnyDateTime" and stumbled upon this
quote from Markus:
For most purposes, we would like
to implement an idea of a totally ordered, "physical" time, i.e. every two
input times should be comparable and correspond to real time points of the
world. This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Sorry if this came up already. but either I can't figure out how to
search the mailing list archive or there simply is no search function?
Anyway, the problem I'm having and which I could NOT reproduce on
http://sandbox.semantic-mediawiki.org/wik
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks Markus,
Indeed, your instanceof check provides an empty results page now ;)
I had the following inline-query: {{#show: Links | ?url | format=rss
}} (with a MediaWiki that is entirely in English)
I can see now why that won't work. I was doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I know I'm not supposed to post bug reports here, but as traffic
seems pretty low and Jeroen is currently working on this, I thought,
I'd risk to be accused of faggotry.
I'm getting this error on accessing Special:Ask with both the current
versio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jeroen De Dauw wrote:
>
> Hey,
>
> This bug is already known, and partially solved [0]. So updating to
> the latest svn commit will solve your problem with the map format.
Oh, alright, I tried updating my checkout, but I guess you didn't
modify the R
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I updated all of the SMW extensions yesterday (thanks to Jeroen) and
been stumbling onto this error today:
*
Warning*: Missing argument 4 for SMWQueryResult::SMWQueryResult(),
called in
/var/www/hackerspace.lu/www/w/extensions/SemanticMediaWiki/in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
Sorry if this would have better been posted on the user list.. I
couldn't figure out if it was really a code error or a pebkac problem.
I've been looking into the specific query that generates the error
messages:
{{#ask:[[Category:RadioSho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evening,
Sorry I kind of hijacked my own thread, but that might get my older
mails answered, who knows? ;)
So, besides this problem in 1.4.3.1:
> Warning: Missing argument 4 for SMWQueryResult::SMWQueryResult(),
> called in
> /var/www/hackerspace.lu/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
> we plan to release SMW 1.5.0 within the next few days. Two or three
> issues still are on my list for being fixed, but most of the code
> should be ready now. Moreover, there has just been a new release of
> Semantic Maps, and there will soon be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaron Koren wrote:
> To answer your last question - it doesn't look like you've upgraded SMW:
>
> https://www.hackerspace.lu/wiki/Special:Version
I haven't, because upgrading to 1.4.3 throws me lots of errors. I posted
them here before but never got a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
I hope this is not going to turn out to be another Pebkac for me ;)
Have you foreseen the possibility of tweaking the recurring events parser to
not parse monthly
recurring events by date (i.e. each 6th of a month) but by days of the week
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, forgot to add the list
Yaron Koren wrote:
> Hi,
>
> No, this one's an actual problem. :) The 'xofmonth' concept sounds
> interesting (though there might be a nicer name than that) - but what
> would a call to #set_recurring_event look like, usi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
> Regarding the complexity of supporting the "2nd Wednesday of every 3rd
> month" example: I agree it is likely to be a very rare occurrence.
> However, I like it because it allows the "period" value to used with the
> proposed new functionality
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
besides the "xofmonth" hack, I created another extension a while ago that
modifies how multi-day
events are handled.
Usually (and without any better knowledge) if you have an event that starts on
April 8th and ends on
April 10th, you only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Usually (and without any better knowledge) if you have an event that starts
> on April 8th and ends on
> April 10th, you only have two [[Has date::]] properties, i.e. the starting
> and ending dates.
>
> The Timeline Result Format displays these
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> For the name of the new value, though, how about 'dayofweekinmonth'
> instead? It's quite long, but it's the only thing I can think of where
> there's even a remote chance that someone would understand it just by
> seeing the name.
You're right.. th
q->getMode() in
SMWRDFResultPrinter->getResultText() reveals the values int(2) and
int(1), i.e. PRINT_PROP in which case $printreq->getData() return an
SMWPropertyValue object and not the required SMWDIProperty.
As we use rdf exports quite extensively, I hope someone can give this a
quick look?
Hi there,
did I overlook something? Can someone reproduce this behaviour or might
the problem be on our side?
Thanks,
David
On 09/10/11 13:31, David Raison wrote:
> Hej,
>
> We've stumbled upon a problem with the query printer in SMW 1.6.1 and
> 1.6.2. Any export to RDF (examp
18 matches
Mail list logo
