From: Yaron K. <ya...@gm...> - 2009-08-04 23:09:18
|
I think this is a great idea, both as a concept and in the specific syntax you've chosen. It certainly is nice to be able to associate addiitional parameters with each column/field, especially for things like sorting on multiple columns. For date formatting it could also be very helpful; it doesn't seem like that much of a stretch to be able to add something like "|+ format=Y m d hh:mi", to a date property, using the standard PHP date-formatting syntax. A few questions/comments: 1. What would a "limit" parameter on a field accomplish? Why would you want to limit one field to a different number of results than others? 2. Markus sent an email recently talking about a new feature planned for SMW 1.4.3, where adding "#" to the name of a queried property, like "?population#", returns an unformatted value, like "1234" instead of "1,234". That could presumably be handled by this new system as well, and probably in a less cryptic way, by adding something like "|+format=none". Given that, maybe it makes sense to just skip that other feature, if it's only going to be useful for (say) a few months? 3. On that note, are features like setting the column header via "?population=Pop." also going to get deprecated, since they too could get replaced by something like the possibly-less-cryptic "|+label=Pop."? -Yaron On Tue, Aug 4, 2009 at 5:00 PM, Denny Vrandecic <dv...@ai...>wrote: > Hi all, > > here's a request for comments on a planned feature. > > A problem in SMW is that there is no proper syntax to give parameters > to print requests, with two exceptions that have been there since the > very first implementation of print requests, = and # (like in ? > length#miles or ?population=pop.). It often would have been very > useful to add further parameters, like limit the results to 1, sort > them alphabetically, align them right, show only three significant > digits etc. > > In order to address this we would like to see implemented for SMW 1.5 > a feature to add parameters to print requests. After some > brainstorming and discussion (that has been ongoing for months, to be > honest) we had a number of possibilities (like "?population=pop > (align=right)") and we did not like most due to various reasons, but > now we think we have something workable: > > {{#ask: [[Category:City]] > | ?Population | +align=right > | ?Inhabitant | +limit=3 | +sort=asc > | limit=10 > }} > > i.e. every parameter that starts with a "+" and following a print > request and before the next print request is considered to be a > parameter for that print request and not for the query as a whole. > > Opinions are welcomed. > > Best, > denny > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Semediawiki-devel mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-devel > |