Shouldn't it be possible to do the same with the 'urlget' parser function ?
- Laurent Alquier Http://www.Alquier.org On May 8, 2009, at 11:25 AM, Yaron Koren <[email protected]> wrote: > Hm, that's not a bad idea... maybe a new tag type like "variable" is > the right way to go, so that you could add > "&DisableLanguageBlock=..." to the query string, and then have > "{{{variable|DisableLanguageBlock}}}" within the form definition. > > -Yaron > > > On Fri, May 8, 2009 at 4:38 AM, Dan Bolser <[email protected]> > wrote: > > 2009/5/8 Patrick Nagel <[email protected]>: > > > > Hi Dan, > > > > On 2009-05-07 16:16, Dan Bolser wrote: > >> Have you looked at the "Call" Extension? > >> > >> http://www.mediawiki.org/wiki/Extension:Call > >> > >> > >> Not sure if you can hack this to do what you want, or if it can be > >> made to play nicely with SF, but it may be worth having a look at > this > >> if you didn't already. > > > > I just gave it a try - but wasn't very successful. Semantic Forms' > routines > > don't even get called, Special:Call just renders the Form:Page as > if it was a > > usual page. I think for this to work, Semantic Forms must be > modified. Maybe > > some of the code used in the Call extension could be built into > SF, so that > > arbitrary parameters (like SourceLanguage=ENG appended to the > query_string) > > can be used in the form as if they were parameters for a template > (like > > {{{SourceLanguage}}})? > > This would also enable SF users to conditionally change certain > aspects of a form. > > Example: You could pass a parameter DisableLanguageBlock=Yes/No > and then put a > > part of the form (the "Language block") inside an > > {{ #ifeq: {{{DisableLanguageBlock|}}} | No | ... }}. > > Yeah... its about turning MediaWiki into a fully featured web > development framework :D > > Something along these lines would be awesome. The problem seems to be > that 'Special:Call' is designed to work with templates, and all > 'Forms:' are (I think) special pages in their own right... for example > is it possible to call a form within a template? I guess this goes > down into the guts of MW ... I don't know much about implementation > details, but I think your right, it would probably be easier to modify > SF to do this. > > > > > Patrick. > > > > -- > > Key ID: 0x86E346D4 http://patrick-nagel.net/key.asc > > Fingerprint: 7745 E1BE FA8B FBAD 76AB 2BFC C981 E686 86E3 46D4 > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Semantic Forms" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/semantic-forms?hl=en -~----------~----~----~----~------~----~------~--~---
