On Montag, 6. April 2009, Yaron Koren wrote:
Markus - I think any info on the type of the parameter can just be part of
the parameter description; an example would be, for the zoom parameter of
the googlemap format, The zoom level of the map (must be an integer
between 1 and 18, with '1' being
I am convinced :-). What remains unclear to me is how to report the expected
input type of a parameter to a UI-creating interface. The types are not really
standard things like integer and string but also things like some
template name or the name of a property printout in the query. Should we
Hey, I'm back from San Francisco and what I find? the Special:Ask discussion
is getting hot ;)
I have a few things to input - my experience shows that building universal
UI builder is a hard thing to do - Yaron can probably second that. My
approach to this problem before was to have subclasses
Markus - I think any info on the type of the parameter can just be part of
the parameter description; an example would be, for the zoom parameter of
the googlemap format, The zoom level of the map (must be an integer
between 1 and 18, with '1' being the furthest away).
Sergey - it's true that
As promised, SMW has now been updated to support some of the requested
functionalities:
* To get the list of all available formats, access $smwgResultFormats.
* To get a result printer object, use SMWQueryProcessor::getResultPrinter().
* To get the name of a printer object, use
Hi,
This is great - the self-description/reflection feature will be allow for
a big improvement to Special:Ask (and evidently Halo as well). This, in
addition to Sergey's previous changes, turns Special:Ask from somewhat of a
hacker interface to an easy-to-use entry point for those getting
Hi,
I am working on our query front-end for inline ask queries which, in the
next version, immediately shows your result set while you are creating
your query.
In order to (dynamically) support all available result printers and to
not hardcode all this stuff which might change in the future I
