Agreed, the arraymaps should be part of SMW. For things like infoboxes,
whether you are using SF or not, you still need to use the arraymap for
annotating lists. So #arraymap is used in far more SMW cases than actual
SF cases.
Actually, on a note, it might be a nice idea to build a sort of #askmap
or something into SMW, or perhaps some kind of format to #ask with some
inline formatting.
{{#ask: [[Category:Character]] [[Classification::Meister]]
[[Weapon::{{PAGENAME}}]] | format=list | replace=$s$ |
inline=[[Meister::$s$]] }}
Say [[Stein]] and [[Kami]] were annotated with [[Weapon::Spirit]]. This
would expand to "[[Meister::Stein]] and [[Meister::Kami]]" on Spirit's page.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://nadir-seen-fire.com]
-Nadir-Point (http://nadir-point.com)
-Wiki-Tools (http://wiki-tools.com)
-MonkeyScript (http://monkeyscript.nadir-point.com)
-Animepedia (http://anime.wikia.com)
-Narutopedia (http://naruto.wikia.com)
-Soul Eater Wiki (http://souleater.wikia.com)
Yaron Koren wrote:
Hi,
I've been thinking recently about components of Semantic Forms that really
belong in Semantic MediaWiki, because they're not related to forms. Special
pages like 'Templates' or 'CreateProperty' are obvious candidates, though
you could make a case for them staying because (a) SF takes a more
template-centric approach, and (b) helper forms are forms in their own
right. But the features of SF for which I don't think any strong case could
be made for keeping them there are the #arraymap and #arraymaptemplate
parser functions, which are used to to map a semantic property or other
action, like a widget call, onto each value of a list. I think it makes
sense to have these somewhere within the SMW system, since SMW takes a
text-as-data approach that isn't shared by most other MediaWiki usages, but
there's nothing form-specific about these functions. In fact, I believe
that in a few cases people have installed Semantic Forms just to have access
to these functions. So, any thoughts on moving them directly into SMW?
I know the general effort is to make SMW as small and lightweight as
possible, but this functionality doesn't take up that much code, and as
someone once said, one should "keep things as simple as possible, but no
simpler".
-Yaron
------------------------------------------------------------------------
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
------------------------------------------------------------------------
_______________________________________________
Semediawiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Semediawiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
