On Dienstag, 9. Oktober 2007, cnit wrote: > > I am sure they will consider a patch that implements this, if anyone > > submits it. ;-) > > I am sure they can create such patch much faster than, for example, > myself. Because they write their own code, while others need to "hack" > it. Though I am perfectly aware they can live without such patch, at least > right now. I don't consider myself a good coder, but I know for sure > that it's much simplier to patch the code you wrote yourself, rather > than others people code, especially such large one as MW.
Sure, they will certainly agree. They might even do it. You could file this as a feature request in MediaZilla (if not done already). > > The patch has different problem - in case it didn't get accepted, it > produces a branch, a version, which should be updated separately with > every release of MW. That's really bad. We prefer to alter the other's > code as less as possible. True. The positive thing about patches is that they convey a message: "Dear developer, I care so much about that problem that I even tried fixing it by myself, and it actually turned out to be possible without major problems that I would have noticed". > > > > The ask result itself, as provided by the SMW-store, is an > > multidimensional array that has objects for all values that will get > > printed (basically the structure is like that of ask result tables, just > > not as HTML but as objects). > > > > But to bring results to a page, they must be serialised in HTML or > > Wikitext. The output of the result printers achieves that, and it is true > > that most of this output is compatible with both HTML and Wikitext (e.g. > > you can have HTML tables in both). The problems arise with links, since > > linked titles do not work the same way in HTML and Wikitext. But > > basically this can be solved by copying the HTML-code and replacing some > > innermost function calls that currently make HTML-outputs instead of > > wikitext. > > Is that large amount of work (eg. can this be made for SMW 1.0)? > Sounds like a virtual printer method for an result object or, if > that's architecturally undesirable to use classes, just calling > functions indirectly or using callbacks. Sounds simple, but of course > that depends on actual code.. It should mostly be search and replace. The main remaining work is to integrate the parser function patch with SMW1.0 and to decide and implement some open issues. > > > As I said, it is not the fancy formatting but the very result list. Not a > > big deal to change this, I think. We just need to extend the > > infrastructure slightly, so that appropriate functions are triggered for > > the printers. One then can implement those step by step. I guess chances > > are good that {{#ask }} would replace <ask> in the long run anyway, so > > the added effort would go away. > > Isn't it better to keep both for compatibility? Is the effort so big? > Anyway, as you're leading developer of SMW, the choise is upon you. We will keep both for compatibility. > > > There are some other discussion points for {{#ask}}, which I raise in a > > separate mail. > > Allright. I understand that my knowledge of MW and SMW code is very > limited, so there may be other questions. > > It's just I've had real pain implementing some of features on my own > MW 1.0/SMW 0.7 site, because template parameters didn't work with > SMW... that was horrible thing, and a sign of bad design in MW itself. Well, there is much legacy stuff in MW that we all have to live with. But I am sure that a working {{#ask will be part of SMW rather soon, just not sure about 1.0rc1 yet. Markus > Dmitriy -- Markus Krötzsch Institut AIFB, Universät Karlsruhe (TH), 76128 Karlsruhe phone +49 (0)721 608 7362 fax +49 (0)721 608 5998 [EMAIL PROTECTED] www http://korrekt.org
pgpf0B1nhNgRi.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel