From: Yury K. <kat...@gm...> - 2012-09-29 23:34:14
|
Hi everyone! I think I need something like 'values dependent on' but a little bit more powerful for my Forms. I've recently added 'values from query' parameter for the field tag in Semantic Forms (maybe it will be approved), see here for the details [1] What I need is the ability to create the fields like this one: {{field|values from query=[[Category:$1]][[Color::$2]][[Owner::+]]|substitute=Flowers[Genus],Flowers[Color]|input type=listbox}} This listbox will show the following list of possible values: 1) the possible values will be the names of the wikipages 2) all these wikipages will have an Owner property 3) there will be belong to a category that is stored in a field Genus of the template Flowers 4) there will have the property Color and the color will be store in a field called Color My question to the users of SMW: Is anybody interested in such a feature? My questions to SMW\SF developers: 1) is it possible to make semantic queries on the fly using AJAX+SMWAsk API? 2) Our project really needs such a feature. If we program here, is it likely to be merged with the core of Semantic Forms? [1] https://bugzilla.wikimedia.org/show_bug.cgi?id=40629 ----- Yury Katkov |
From: James HK <jam...@gm...> - 2012-09-30 00:22:23
|
Hi, See [1] which is an extension that generates option values from a semantic query or parser function for a specified form field. [1] http://www.mediawiki.org/wiki/Extension:SemanticFormsSelect#Query_And_Function_format Cheers On 9/30/12, Yury Katkov <kat...@gm...> wrote: > Hi everyone! > > I think I need something like 'values dependent on' but a little bit more > powerful for my Forms. > I've recently added 'values from query' parameter for the field tag in > Semantic Forms (maybe it will be approved), see here for the details [1] > > What I need is the ability to create the fields like this one: > > {{field|values from > query=[[Category:$1]][[Color::$2]][[Owner::+]]|substitute=Flowers[Genus],Flowers[Color]|input > type=listbox}} > > This listbox will show the following list of possible values: > 1) the possible values will be the names of the wikipages > 2) all these wikipages will have an Owner property > 3) there will be belong to a category that is stored in a field Genus of > the template Flowers > 4) there will have the property Color and the color will be store in a > field called Color > > My question to the users of SMW: Is anybody interested in such a feature? > My questions to SMW\SF developers: > 1) is it possible to make semantic queries on the fly using AJAX+SMWAsk > API? > 2) Our project really needs such a feature. If we program here, is it > likely to be merged with the core of Semantic Forms? > > > [1] https://bugzilla.wikimedia.org/show_bug.cgi?id=40629 > ----- > Yury Katkov > |
From: Yury K. <kat...@gm...> - 2012-09-30 00:39:36
|
Hi James! Example 3 in the documentationlooks very much like my case, thank you so much!!! I'll try it tomorrow, maybe it will suit me as a temporary decision. I don't think that it uses ResourceLoader and am not sure that it is compatible with the latest versions of MW/SMF/SF. It also seems Jason Zhang can only use one value to substitute instead of @@@@, is that right? Anyway the existence of such extensions shows that more than me alone need such a feature. Also I'll look at your AJAX calls and hopefully will be able to answer to a question (1) to developers. The question (2) to developers remains and also I'm open to discussion about the syntax. Cheers, Yury On Sun, Sep 30, 2012 at 4:22 AM, James HK <jam...@gm...> wrote: > Hi, > > See [1] which is an extension that generates option values from a > semantic query or parser function for a specified form field. > > [1] http://www.mediawiki.org/wiki/Extension:SemanticFormsSelect#Query_And_Function_format > > Cheers > > On 9/30/12, Yury Katkov <kat...@gm...> wrote: >> Hi everyone! >> >> I think I need something like 'values dependent on' but a little bit more >> powerful for my Forms. >> I've recently added 'values from query' parameter for the field tag in >> Semantic Forms (maybe it will be approved), see here for the details [1] >> >> What I need is the ability to create the fields like this one: >> >> {{field|values from >> query=[[Category:$1]][[Color::$2]][[Owner::+]]|substitute=Flowers[Genus],Flowers[Color]|input >> type=listbox}} >> >> This listbox will show the following list of possible values: >> 1) the possible values will be the names of the wikipages >> 2) all these wikipages will have an Owner property >> 3) there will be belong to a category that is stored in a field Genus of >> the template Flowers >> 4) there will have the property Color and the color will be store in a >> field called Color >> >> My question to the users of SMW: Is anybody interested in such a feature? >> My questions to SMW\SF developers: >> 1) is it possible to make semantic queries on the fly using AJAX+SMWAsk >> API? >> 2) Our project really needs such a feature. If we program here, is it >> likely to be merged with the core of Semantic Forms? >> >> >> [1] https://bugzilla.wikimedia.org/show_bug.cgi?id=40629 >> ----- >> Yury Katkov >> |
From: Yaron K. <ya...@wi...> - 2012-09-30 14:23:05
|
Hi Yury, Well, you bring up two proposed features for SF here: a standard "values from query" parameter (which you submitted a patch for), and the ability to include variables, representing the current content of some other form field, in the field tag - which could go into a "values from query" parameter, but it wouldn't necessarily have to. I'll just focus on the second one here. This is a complex need, and one that I think is out of the ordinary: you want users to select a genus, and a color, and then only flowers that match those two fields, and additionally have an owner specified for them, will show up in a listbox. My main question is, what sort of page is this form meant to edit? Is it a page about a collection of flowers that all share one genus and color? I don't know if this an actual form you're talking about, or just a metaphor for a form that holds more technical data that's harder to explain, but in either case it seems odd. Basically you're talking about creating a subset of a subset - a group of pages that match both solid criteria (the color and the genus) and arbitrary criteria (the user's choice). I haven't heard of that kind of use case - but maybe it makes sense for the circumstances. Could you explain the data structure of this form in more detail? -Yaron On Sat, Sep 29, 2012 at 8:38 PM, Yury Katkov <kat...@gm...> wrote: > Hi James! > > Example 3 in the documentationlooks very much like my case, thank you > so much!!! I'll try > it tomorrow, maybe it will suit me as a temporary decision. I don't > think that it uses ResourceLoader and am not sure that it is > compatible with the latest versions of MW/SMF/SF. > > It also seems Jason Zhang can only use one value to substitute instead > of @@@@, is that right? > > Anyway the existence of such extensions shows that more than me alone > need such a feature. Also I'll look at your AJAX calls and hopefully > will be able to answer to a question (1) to developers. > > The question (2) to developers remains and also I'm open to discussion > about the syntax. > > Cheers, > Yury > > > On Sun, Sep 30, 2012 at 4:22 AM, James HK <jam...@gm...> > wrote: > > Hi, > > > > See [1] which is an extension that generates option values from a > > semantic query or parser function for a specified form field. > > > > [1] > http://www.mediawiki.org/wiki/Extension:SemanticFormsSelect#Query_And_Function_format > > > > Cheers > > > > On 9/30/12, Yury Katkov <kat...@gm...> wrote: > >> Hi everyone! > >> > >> I think I need something like 'values dependent on' but a little bit > more > >> powerful for my Forms. > >> I've recently added 'values from query' parameter for the field tag in > >> Semantic Forms (maybe it will be approved), see here for the details [1] > >> > >> What I need is the ability to create the fields like this one: > >> > >> {{field|values from > >> > query=[[Category:$1]][[Color::$2]][[Owner::+]]|substitute=Flowers[Genus],Flowers[Color]|input > >> type=listbox}} > >> > >> This listbox will show the following list of possible values: > >> 1) the possible values will be the names of the wikipages > >> 2) all these wikipages will have an Owner property > >> 3) there will be belong to a category that is stored in a field Genus of > >> the template Flowers > >> 4) there will have the property Color and the color will be store in a > >> field called Color > >> > >> My question to the users of SMW: Is anybody interested in such a > feature? > >> My questions to SMW\SF developers: > >> 1) is it possible to make semantic queries on the fly using AJAX+SMWAsk > >> API? > >> 2) Our project really needs such a feature. If we program here, is it > >> likely to be merged with the core of Semantic Forms? > >> > >> > >> [1] https://bugzilla.wikimedia.org/show_bug.cgi?id=40629 > >> ----- > >> Yury Katkov > >> > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://ad.doubleclick.net/clk;258768047;13503038;j? > http://info.appdynamics.com/FreeJavaPerformanceDownload.html > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: Yury K. <kat...@gm...> - 2012-09-30 19:42:04
|
Hi Yaron! My example is surely very silly and synthetic so let's just forget about the flowers I'll try to explain the real problem I faced with in a Foresight wiki. Here is my problem domain. There are several brainstorming sessions about the forecasts on a distant future, all of them have different topics. Each of those sessions has various objects as the results of the brainstorming: future trends, possible technologies that may appear in the future, possible important events. All these data are loaded to the wiki using the semantic forms. After the brainstorming ends, the participants can improve the objects, categorize them and link them together. Here for example I have the Trend objects. I want to connect Trends to the Events and to Technologies but only inside the current brainstorming session. The semantic form for Trend will look like that: <FORM>... {{{field|session name|hidden|required}}} // the only valid way to create a trend is using the #formlink on a Session's page. Formlink will fill this value with the name of the session {{{field|related events|values from query=[[Category::Event]][[session::$1]]|substitute=Trend[session name] | input type=two listboxes}}} {{{field|related technologies|values from query=[[Category::Technology]][[session::$1]]|substitute=Trend[session name] | input type=two listboxes}}} ... <END OF FORM> I can use values from concept but it's a very bad workaround if I have many sessions. I hope now the case is more clear. ----- Yury Katkov On Sun, Sep 30, 2012 at 6:22 PM, Yaron Koren <ya...@wi...> wrote: > Hi Yury, > > Well, you bring up two proposed features for SF here: a standard "values > from query" parameter (which you submitted a patch for), and the ability to > include variables, representing the current content of some other form > field, in the field tag - which could go into a "values from query" > parameter, but it wouldn't necessarily have to. I'll just focus on the > second one here. > > This is a complex need, and one that I think is out of the ordinary: you > want users to select a genus, and a color, and then only flowers that match > those two fields, and additionally have an owner specified for them, will > show up in a listbox. > > My main question is, what sort of page is this form meant to edit? Is it a > page about a collection of flowers that all share one genus and color? I > don't know if this an actual form you're talking about, or just a metaphor > for a form that holds more technical data that's harder to explain, but in > either case it seems odd. Basically you're talking about creating a subset > of a subset - a group of pages that match both solid criteria (the color and > the genus) and arbitrary criteria (the user's choice). I haven't heard of > that kind of use case - but maybe it makes sense for the circumstances. > Could you explain the data structure of this form in more detail? > > -Yaron > > On Sat, Sep 29, 2012 at 8:38 PM, Yury Katkov <kat...@gm...> wrote: >> >> Hi James! >> >> Example 3 in the documentationlooks very much like my case, thank you >> so much!!! I'll try >> it tomorrow, maybe it will suit me as a temporary decision. I don't >> think that it uses ResourceLoader and am not sure that it is >> compatible with the latest versions of MW/SMF/SF. >> >> It also seems Jason Zhang can only use one value to substitute instead >> of @@@@, is that right? >> >> Anyway the existence of such extensions shows that more than me alone >> need such a feature. Also I'll look at your AJAX calls and hopefully >> will be able to answer to a question (1) to developers. >> >> The question (2) to developers remains and also I'm open to discussion >> about the syntax. >> >> Cheers, >> Yury >> >> >> On Sun, Sep 30, 2012 at 4:22 AM, James HK <jam...@gm...> >> wrote: >> > Hi, >> > >> > See [1] which is an extension that generates option values from a >> > semantic query or parser function for a specified form field. >> > >> > [1] >> > http://www.mediawiki.org/wiki/Extension:SemanticFormsSelect#Query_And_Function_format >> > >> > Cheers >> > >> > On 9/30/12, Yury Katkov <kat...@gm...> wrote: >> >> Hi everyone! >> >> >> >> I think I need something like 'values dependent on' but a little bit >> >> more >> >> powerful for my Forms. >> >> I've recently added 'values from query' parameter for the field tag in >> >> Semantic Forms (maybe it will be approved), see here for the details >> >> [1] >> >> >> >> What I need is the ability to create the fields like this one: >> >> >> >> {{field|values from >> >> >> >> query=[[Category:$1]][[Color::$2]][[Owner::+]]|substitute=Flowers[Genus],Flowers[Color]|input >> >> type=listbox}} >> >> >> >> This listbox will show the following list of possible values: >> >> 1) the possible values will be the names of the wikipages >> >> 2) all these wikipages will have an Owner property >> >> 3) there will be belong to a category that is stored in a field Genus >> >> of >> >> the template Flowers >> >> 4) there will have the property Color and the color will be store in a >> >> field called Color >> >> >> >> My question to the users of SMW: Is anybody interested in such a >> >> feature? >> >> My questions to SMW\SF developers: >> >> 1) is it possible to make semantic queries on the fly using AJAX+SMWAsk >> >> API? >> >> 2) Our project really needs such a feature. If we program here, is it >> >> likely to be merged with the core of Semantic Forms? >> >> >> >> >> >> [1] https://bugzilla.wikimedia.org/show_bug.cgi?id=40629 >> >> ----- >> >> Yury Katkov >> >> >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://ad.doubleclick.net/clk;258768047;13503038;j? >> http://info.appdynamics.com/FreeJavaPerformanceDownload.html >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > -- > WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: Yaron K. <ya...@wi...> - 2012-10-01 00:26:36
|
Hi Yury, This sounds like a very different example - here the original, "source" field is just a hidden field that gets its value from the query string. In that case, I would think the ideal solution would be to use the UrlGetParameters extension, to directly use the query string value: https://www.mediawiki.org/wiki/Extension:UrlGetParameters I'm not entirely sure that this would work, because I don't remember which parts of the form syntax let you embed a parser function within them - but if it doesn't work, then getting it to work would seem like the simpler, and better, solution. -Yaron On Sun, Sep 30, 2012 at 3:41 PM, Yury Katkov <kat...@gm...> wrote: > Hi Yaron! > > My example is surely very silly and synthetic so let's just forget > about the flowers > I'll try to explain the real problem I faced with in a Foresight wiki. > > Here is my problem domain. There are several brainstorming sessions > about the forecasts on a distant future, all of them have different > topics. Each of those sessions has various objects as the results of > the brainstorming: future trends, possible technologies that may > appear in the future, possible important events. All these data are > loaded to the wiki using the semantic forms. After the brainstorming > ends, the participants can improve the objects, categorize them and > link them together. > > Here for example I have the Trend objects. I want to connect Trends to > the Events and to Technologies but only inside the current > brainstorming session. > > The semantic form for Trend will look like that: > <FORM>... > {{{field|session name|hidden|required}}} // the only valid way to > create a trend is using the #formlink on a Session's page. Formlink > will fill this value with the name of the session > > {{{field|related events|values from > query=[[Category::Event]][[session::$1]]|substitute=Trend[session > name] | input type=two listboxes}}} > > {{{field|related technologies|values from > query=[[Category::Technology]][[session::$1]]|substitute=Trend[session > name] | input type=two listboxes}}} > ... > <END OF FORM> > > I can use values from concept but it's a very bad workaround if I have > many sessions. > > I hope now the case is more clear. > ----- > Yury Katkov > > |
From: Yury K. <kat...@gm...> - 2012-10-01 06:54:09
|
Hi Yaron! There is no problem in passing the Session parameter I can use either 'query string' parameter of the formlink or the urlget function. In this Trend form my main problem is to restrict the set of possible values which will be displayed in the "Related events" listboxes: 1) All these values are pagenames for pages in Events category 2) All these pages belongs to the same Session as the Trend, that I'm currently looking at The same is for related Technologies: I want to link objects only inside the session, so that the participants of the session "The Future of Food" don't try to link there Trends and possible events with objects from the Session "The future of titan manufacturing ". The two restrictions to possible values in the listbox I'have just noted can be three or four; and all of them can be dependent on what is currently entered in the form. ----- Yury Katkov On Mon, Oct 1, 2012 at 4:26 AM, Yaron Koren <ya...@wi...> wrote: > Hi Yury, > > This sounds like a very different example - here the original, "source" > field is just a hidden field that gets its value from the query string. In > that case, I would think the ideal solution would be to use the > UrlGetParameters extension, to directly use the query string value: > > https://www.mediawiki.org/wiki/Extension:UrlGetParameters > > I'm not entirely sure that this would work, because I don't remember which > parts of the form syntax let you embed a parser function within them - but > if it doesn't work, then getting it to work would seem like the simpler, and > better, solution. > > -Yaron > > > On Sun, Sep 30, 2012 at 3:41 PM, Yury Katkov <kat...@gm...> wrote: >> >> Hi Yaron! >> >> My example is surely very silly and synthetic so let's just forget >> about the flowers >> I'll try to explain the real problem I faced with in a Foresight wiki. >> >> Here is my problem domain. There are several brainstorming sessions >> about the forecasts on a distant future, all of them have different >> topics. Each of those sessions has various objects as the results of >> the brainstorming: future trends, possible technologies that may >> appear in the future, possible important events. All these data are >> loaded to the wiki using the semantic forms. After the brainstorming >> ends, the participants can improve the objects, categorize them and >> link them together. >> >> Here for example I have the Trend objects. I want to connect Trends to >> the Events and to Technologies but only inside the current >> brainstorming session. >> >> The semantic form for Trend will look like that: >> <FORM>... >> {{{field|session name|hidden|required}}} // the only valid way to >> create a trend is using the #formlink on a Session's page. Formlink >> will fill this value with the name of the session >> >> {{{field|related events|values from >> query=[[Category::Event]][[session::$1]]|substitute=Trend[session >> name] | input type=two listboxes}}} >> >> {{{field|related technologies|values from >> query=[[Category::Technology]][[session::$1]]|substitute=Trend[session >> name] | input type=two listboxes}}} >> ... >> <END OF FORM> >> >> I can use values from concept but it's a very bad workaround if I have >> many sessions. >> >> I hope now the case is more clear. >> ----- >> Yury Katkov >> > |
From: Yaron K. <ya...@wi...> - 2012-10-01 14:35:33
|
Hi Yury, I don't understand - are your data needs more complex than what you put in that sample form definition code earlier? If so, can you revise that sample code to more accurately reflect what you want your form to look like? -Yaron On Mon, Oct 1, 2012 at 2:53 AM, Yury Katkov <kat...@gm...> wrote: > Hi Yaron! > > There is no problem in passing the Session parameter I can use either > 'query string' parameter of the formlink or the urlget function. > In this Trend form my main problem is to restrict the set of possible > values which will be displayed in the "Related events" listboxes: > 1) All these values are pagenames for pages in Events category > 2) All these pages belongs to the same Session as the Trend, that I'm > currently looking at > > The same is for related Technologies: I want to link objects only > inside the session, so that the participants of the session "The > Future of Food" don't try to link there Trends and possible events > with objects from the Session "The future of titan manufacturing ". > > The two restrictions to possible values in the listbox I'have just > noted can be three or four; and all of them can be dependent on what > is currently entered in the form. > ----- > Yury Katkov > > > > On Mon, Oct 1, 2012 at 4:26 AM, Yaron Koren <ya...@wi...> wrote: > > Hi Yury, > > > > This sounds like a very different example - here the original, "source" > > field is just a hidden field that gets its value from the query string. > In > > that case, I would think the ideal solution would be to use the > > UrlGetParameters extension, to directly use the query string value: > > > > https://www.mediawiki.org/wiki/Extension:UrlGetParameters > > > > I'm not entirely sure that this would work, because I don't remember > which > > parts of the form syntax let you embed a parser function within them - > but > > if it doesn't work, then getting it to work would seem like the simpler, > and > > better, solution. > > > > -Yaron > > > > > > On Sun, Sep 30, 2012 at 3:41 PM, Yury Katkov <kat...@gm...> > wrote: > >> > >> Hi Yaron! > >> > >> My example is surely very silly and synthetic so let's just forget > >> about the flowers > >> I'll try to explain the real problem I faced with in a Foresight wiki. > >> > >> Here is my problem domain. There are several brainstorming sessions > >> about the forecasts on a distant future, all of them have different > >> topics. Each of those sessions has various objects as the results of > >> the brainstorming: future trends, possible technologies that may > >> appear in the future, possible important events. All these data are > >> loaded to the wiki using the semantic forms. After the brainstorming > >> ends, the participants can improve the objects, categorize them and > >> link them together. > >> > >> Here for example I have the Trend objects. I want to connect Trends to > >> the Events and to Technologies but only inside the current > >> brainstorming session. > >> > >> The semantic form for Trend will look like that: > >> <FORM>... > >> {{{field|session name|hidden|required}}} // the only valid way to > >> create a trend is using the #formlink on a Session's page. Formlink > >> will fill this value with the name of the session > >> > >> {{{field|related events|values from > >> query=[[Category::Event]][[session::$1]]|substitute=Trend[session > >> name] | input type=two listboxes}}} > >> > >> {{{field|related technologies|values from > >> query=[[Category::Technology]][[session::$1]]|substitute=Trend[session > >> name] | input type=two listboxes}}} > >> ... > >> <END OF FORM> > >> > >> I can use values from concept but it's a very bad workaround if I have > >> many sessions. > >> > >> I hope now the case is more clear. > >> ----- > >> Yury Katkov > >> > > > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: Yury K. <kat...@gm...> - 2012-10-01 15:12:36
|
Hi Yaron! No, these two examples (the synthetic and silly flower example and the real-world brainstorming example) are really the same. What I need is to use the data that user put in the field1 as the parameter of the query that defines the allowed values set in the field2. Anyway, I'll try to clarify: So the user edits the Flower Rose. He entered the Genus of Rose : Rosa. He entered the color of Rose - for example Red. The field 'related flowers' will be the listbox of all red flowers with genus Rosa: {{field|related flowers|values from query=[[Category:$1]][[Color::$2]][[Owner::+]]|substitute=Flowers[Genus],Flowers[Color]|input type=listbox}} ----- Yury Katkov On Mon, Oct 1, 2012 at 6:35 PM, Yaron Koren <ya...@wi...> wrote: > Hi Yury, > > I don't understand - are your data needs more complex than what you put in > that sample form definition code earlier? If so, can you revise that sample > code to more accurately reflect what you want your form to look like? > > -Yaron > > > On Mon, Oct 1, 2012 at 2:53 AM, Yury Katkov <kat...@gm...> wrote: >> >> Hi Yaron! >> >> There is no problem in passing the Session parameter I can use either >> 'query string' parameter of the formlink or the urlget function. >> In this Trend form my main problem is to restrict the set of possible >> values which will be displayed in the "Related events" listboxes: >> 1) All these values are pagenames for pages in Events category >> 2) All these pages belongs to the same Session as the Trend, that I'm >> currently looking at >> >> The same is for related Technologies: I want to link objects only >> inside the session, so that the participants of the session "The >> Future of Food" don't try to link there Trends and possible events >> with objects from the Session "The future of titan manufacturing ". >> >> The two restrictions to possible values in the listbox I'have just >> noted can be three or four; and all of them can be dependent on what >> is currently entered in the form. >> ----- >> Yury Katkov >> >> >> >> On Mon, Oct 1, 2012 at 4:26 AM, Yaron Koren <ya...@wi...> wrote: >> > Hi Yury, >> > >> > This sounds like a very different example - here the original, "source" >> > field is just a hidden field that gets its value from the query string. >> > In >> > that case, I would think the ideal solution would be to use the >> > UrlGetParameters extension, to directly use the query string value: >> > >> > https://www.mediawiki.org/wiki/Extension:UrlGetParameters >> > >> > I'm not entirely sure that this would work, because I don't remember >> > which >> > parts of the form syntax let you embed a parser function within them - >> > but >> > if it doesn't work, then getting it to work would seem like the simpler, >> > and >> > better, solution. >> > >> > -Yaron >> > >> > >> > On Sun, Sep 30, 2012 at 3:41 PM, Yury Katkov <kat...@gm...> >> > wrote: >> >> >> >> Hi Yaron! >> >> >> >> My example is surely very silly and synthetic so let's just forget >> >> about the flowers >> >> I'll try to explain the real problem I faced with in a Foresight wiki. >> >> >> >> Here is my problem domain. There are several brainstorming sessions >> >> about the forecasts on a distant future, all of them have different >> >> topics. Each of those sessions has various objects as the results of >> >> the brainstorming: future trends, possible technologies that may >> >> appear in the future, possible important events. All these data are >> >> loaded to the wiki using the semantic forms. After the brainstorming >> >> ends, the participants can improve the objects, categorize them and >> >> link them together. >> >> >> >> Here for example I have the Trend objects. I want to connect Trends to >> >> the Events and to Technologies but only inside the current >> >> brainstorming session. >> >> >> >> The semantic form for Trend will look like that: >> >> <FORM>... >> >> {{{field|session name|hidden|required}}} // the only valid way to >> >> create a trend is using the #formlink on a Session's page. Formlink >> >> will fill this value with the name of the session >> >> >> >> {{{field|related events|values from >> >> query=[[Category::Event]][[session::$1]]|substitute=Trend[session >> >> name] | input type=two listboxes}}} >> >> >> >> {{{field|related technologies|values from >> >> query=[[Category::Technology]][[session::$1]]|substitute=Trend[session >> >> name] | input type=two listboxes}}} >> >> ... >> >> <END OF FORM> >> >> >> >> I can use values from concept but it's a very bad workaround if I have >> >> many sessions. >> >> >> >> I hope now the case is more clear. >> >> ----- >> >> Yury Katkov >> >> >> > > > > > > -- > WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: Yaron K. <ya...@wi...> - 2012-10-01 15:17:04
|
Hi, No, the two examples are different - the "silly" one involves two "substitions", based on editable fields, while the "real" one involves one substitution, directly from the query string. Can you clarify the discrepancy? What is the form that you actually need? -Yaron On Mon, Oct 1, 2012 at 11:11 AM, Yury Katkov <kat...@gm...> wrote: > Hi Yaron! > > No, these two examples (the synthetic and silly flower example and the > real-world brainstorming example) are really the same. > What I need is to use the data that user put in the field1 as the > parameter of the query that defines the allowed values set in the > field2. > > Anyway, I'll try to clarify: > So the user edits the Flower Rose. He entered the Genus of Rose : > Rosa. He entered the color of Rose - for example Red. The field > 'related flowers' will be the listbox of all red flowers with genus > Rosa: > > {{field|related flowers|values from > > query=[[Category:$1]][[Color::$2]][[Owner::+]]|substitute=Flowers[Genus],Flowers[Color]|input > type=listbox}} > > ----- > Yury Katkov > > > > On Mon, Oct 1, 2012 at 6:35 PM, Yaron Koren <ya...@wi...> wrote: > > Hi Yury, > > > > I don't understand - are your data needs more complex than what you put > in > > that sample form definition code earlier? If so, can you revise that > sample > > code to more accurately reflect what you want your form to look like? > > > > -Yaron > > > > > > On Mon, Oct 1, 2012 at 2:53 AM, Yury Katkov <kat...@gm...> > wrote: > >> > >> Hi Yaron! > >> > >> There is no problem in passing the Session parameter I can use either > >> 'query string' parameter of the formlink or the urlget function. > >> In this Trend form my main problem is to restrict the set of possible > >> values which will be displayed in the "Related events" listboxes: > >> 1) All these values are pagenames for pages in Events category > >> 2) All these pages belongs to the same Session as the Trend, that I'm > >> currently looking at > >> > >> The same is for related Technologies: I want to link objects only > >> inside the session, so that the participants of the session "The > >> Future of Food" don't try to link there Trends and possible events > >> with objects from the Session "The future of titan manufacturing ". > >> > >> The two restrictions to possible values in the listbox I'have just > >> noted can be three or four; and all of them can be dependent on what > >> is currently entered in the form. > >> ----- > >> Yury Katkov > >> > >> > >> > >> On Mon, Oct 1, 2012 at 4:26 AM, Yaron Koren <ya...@wi...> > wrote: > >> > Hi Yury, > >> > > >> > This sounds like a very different example - here the original, > "source" > >> > field is just a hidden field that gets its value from the query > string. > >> > In > >> > that case, I would think the ideal solution would be to use the > >> > UrlGetParameters extension, to directly use the query string value: > >> > > >> > https://www.mediawiki.org/wiki/Extension:UrlGetParameters > >> > > >> > I'm not entirely sure that this would work, because I don't remember > >> > which > >> > parts of the form syntax let you embed a parser function within them - > >> > but > >> > if it doesn't work, then getting it to work would seem like the > simpler, > >> > and > >> > better, solution. > >> > > >> > -Yaron > >> > > >> > > >> > On Sun, Sep 30, 2012 at 3:41 PM, Yury Katkov <kat...@gm...> > >> > wrote: > >> >> > >> >> Hi Yaron! > >> >> > >> >> My example is surely very silly and synthetic so let's just forget > >> >> about the flowers > >> >> I'll try to explain the real problem I faced with in a Foresight > wiki. > >> >> > >> >> Here is my problem domain. There are several brainstorming sessions > >> >> about the forecasts on a distant future, all of them have different > >> >> topics. Each of those sessions has various objects as the results of > >> >> the brainstorming: future trends, possible technologies that may > >> >> appear in the future, possible important events. All these data are > >> >> loaded to the wiki using the semantic forms. After the brainstorming > >> >> ends, the participants can improve the objects, categorize them and > >> >> link them together. > >> >> > >> >> Here for example I have the Trend objects. I want to connect Trends > to > >> >> the Events and to Technologies but only inside the current > >> >> brainstorming session. > >> >> > >> >> The semantic form for Trend will look like that: > >> >> <FORM>... > >> >> {{{field|session name|hidden|required}}} // the only valid way to > >> >> create a trend is using the #formlink on a Session's page. Formlink > >> >> will fill this value with the name of the session > >> >> > >> >> {{{field|related events|values from > >> >> query=[[Category::Event]][[session::$1]]|substitute=Trend[session > >> >> name] | input type=two listboxes}}} > >> >> > >> >> {{{field|related technologies|values from > >> >> > query=[[Category::Technology]][[session::$1]]|substitute=Trend[session > >> >> name] | input type=two listboxes}}} > >> >> ... > >> >> <END OF FORM> > >> >> > >> >> I can use values from concept but it's a very bad workaround if I > have > >> >> many sessions. > >> >> > >> >> I hope now the case is more clear. > >> >> ----- > >> >> Yury Katkov > >> >> > >> > > > > > > > > > > > -- > > WikiWorks · MediaWiki Consulting · http://wikiworks.com > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: Yury K. <kat...@gm...> - 2012-10-01 15:36:58
|
I need the first one. There are some problems with this UrlGetParameters approach: it seems that it will work for article creation using the #formlink but it will not work for article edition using 'Edit with Form' button. Another problem is that the parameters for allowed value set restrictions may not be defined from the beginning. Linking together pages inside the website section is typical example of such feature. Am I right that the most frighting thing here is making ask-queries in AJAX code? ----- Yury Katkov On Mon, Oct 1, 2012 at 7:16 PM, Yaron Koren <ya...@wi...> wrote: > Hi, > > No, the two examples are different - the "silly" one involves two > "substitions", based on editable fields, while the "real" one involves one > substitution, directly from the query string. Can you clarify the > discrepancy? What is the form that you actually need? > > -Yaron > > > On Mon, Oct 1, 2012 at 11:11 AM, Yury Katkov <kat...@gm...> wrote: >> >> Hi Yaron! >> >> No, these two examples (the synthetic and silly flower example and the >> real-world brainstorming example) are really the same. >> What I need is to use the data that user put in the field1 as the >> parameter of the query that defines the allowed values set in the >> field2. >> >> Anyway, I'll try to clarify: >> So the user edits the Flower Rose. He entered the Genus of Rose : >> Rosa. He entered the color of Rose - for example Red. The field >> 'related flowers' will be the listbox of all red flowers with genus >> Rosa: >> >> {{field|related flowers|values from >> >> query=[[Category:$1]][[Color::$2]][[Owner::+]]|substitute=Flowers[Genus],Flowers[Color]|input >> type=listbox}} >> >> ----- >> Yury Katkov >> >> >> >> On Mon, Oct 1, 2012 at 6:35 PM, Yaron Koren <ya...@wi...> wrote: >> > Hi Yury, >> > >> > I don't understand - are your data needs more complex than what you put >> > in >> > that sample form definition code earlier? If so, can you revise that >> > sample >> > code to more accurately reflect what you want your form to look like? >> > >> > -Yaron >> > >> > >> > On Mon, Oct 1, 2012 at 2:53 AM, Yury Katkov <kat...@gm...> >> > wrote: >> >> >> >> Hi Yaron! >> >> >> >> There is no problem in passing the Session parameter I can use either >> >> 'query string' parameter of the formlink or the urlget function. >> >> In this Trend form my main problem is to restrict the set of possible >> >> values which will be displayed in the "Related events" listboxes: >> >> 1) All these values are pagenames for pages in Events category >> >> 2) All these pages belongs to the same Session as the Trend, that I'm >> >> currently looking at >> >> >> >> The same is for related Technologies: I want to link objects only >> >> inside the session, so that the participants of the session "The >> >> Future of Food" don't try to link there Trends and possible events >> >> with objects from the Session "The future of titan manufacturing ". >> >> >> >> The two restrictions to possible values in the listbox I'have just >> >> noted can be three or four; and all of them can be dependent on what >> >> is currently entered in the form. >> >> ----- >> >> Yury Katkov >> >> >> >> >> >> >> >> On Mon, Oct 1, 2012 at 4:26 AM, Yaron Koren <ya...@wi...> >> >> wrote: >> >> > Hi Yury, >> >> > >> >> > This sounds like a very different example - here the original, >> >> > "source" >> >> > field is just a hidden field that gets its value from the query >> >> > string. >> >> > In >> >> > that case, I would think the ideal solution would be to use the >> >> > UrlGetParameters extension, to directly use the query string value: >> >> > >> >> > https://www.mediawiki.org/wiki/Extension:UrlGetParameters >> >> > >> >> > I'm not entirely sure that this would work, because I don't remember >> >> > which >> >> > parts of the form syntax let you embed a parser function within them >> >> > - >> >> > but >> >> > if it doesn't work, then getting it to work would seem like the >> >> > simpler, >> >> > and >> >> > better, solution. >> >> > >> >> > -Yaron >> >> > >> >> > >> >> > On Sun, Sep 30, 2012 at 3:41 PM, Yury Katkov <kat...@gm...> >> >> > wrote: >> >> >> >> >> >> Hi Yaron! >> >> >> >> >> >> My example is surely very silly and synthetic so let's just forget >> >> >> about the flowers >> >> >> I'll try to explain the real problem I faced with in a Foresight >> >> >> wiki. >> >> >> >> >> >> Here is my problem domain. There are several brainstorming sessions >> >> >> about the forecasts on a distant future, all of them have different >> >> >> topics. Each of those sessions has various objects as the results of >> >> >> the brainstorming: future trends, possible technologies that may >> >> >> appear in the future, possible important events. All these data are >> >> >> loaded to the wiki using the semantic forms. After the brainstorming >> >> >> ends, the participants can improve the objects, categorize them and >> >> >> link them together. >> >> >> >> >> >> Here for example I have the Trend objects. I want to connect Trends >> >> >> to >> >> >> the Events and to Technologies but only inside the current >> >> >> brainstorming session. >> >> >> >> >> >> The semantic form for Trend will look like that: >> >> >> <FORM>... >> >> >> {{{field|session name|hidden|required}}} // the only valid way to >> >> >> create a trend is using the #formlink on a Session's page. Formlink >> >> >> will fill this value with the name of the session >> >> >> >> >> >> {{{field|related events|values from >> >> >> query=[[Category::Event]][[session::$1]]|substitute=Trend[session >> >> >> name] | input type=two listboxes}}} >> >> >> >> >> >> {{{field|related technologies|values from >> >> >> >> >> >> query=[[Category::Technology]][[session::$1]]|substitute=Trend[session >> >> >> name] | input type=two listboxes}}} >> >> >> ... >> >> >> <END OF FORM> >> >> >> >> >> >> I can use values from concept but it's a very bad workaround if I >> >> >> have >> >> >> many sessions. >> >> >> >> >> >> I hope now the case is more clear. >> >> >> ----- >> >> >> Yury Katkov >> >> >> >> >> > >> > >> > >> > >> > >> > -- >> > WikiWorks · MediaWiki Consulting · http://wikiworks.com > > > > > -- > WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: Yaron K. <ya...@wi...> - 2012-10-01 16:06:17
|
Ah, that's true, I didn't think about the "edit with form" case. Well, for that, you could use #show, assuming the value is being stored semantically - and you could have an #ifexists call to tie the whole thing together, so that #urlget is called for new pages, and #show is called for existing pages. It's a hack, but it wouldn't require any custom development. As for "parameters may not be defined from the beginning" - that's the central issue. New development would be required only if (a) they're not, and (b) there's more than one of them - since a single editable parameter can be handled by the "values dependent on" feature. So is that definitely the case, or are you just guessing that you might require this feature in the future? -Yaron On Mon, Oct 1, 2012 at 11:36 AM, Yury Katkov <kat...@gm...> wrote: > I need the first one. There are some problems with this > UrlGetParameters approach: it seems that it will work for article > creation using the #formlink but it will not work for article edition > using 'Edit with Form' button. Another problem is that the parameters > for allowed value set restrictions may not be defined from the > beginning. > > Linking together pages inside the website section is typical example > of such feature. Am I right that the most frighting thing here is > making ask-queries in AJAX code? > ----- > Yury Katkov > > > > On Mon, Oct 1, 2012 at 7:16 PM, Yaron Koren <ya...@wi...> wrote: > > Hi, > > > > No, the two examples are different - the "silly" one involves two > > "substitions", based on editable fields, while the "real" one involves > one > > substitution, directly from the query string. Can you clarify the > > discrepancy? What is the form that you actually need? > > > > -Yaron > > > > > > On Mon, Oct 1, 2012 at 11:11 AM, Yury Katkov <kat...@gm...> > wrote: > >> > >> Hi Yaron! > >> > >> No, these two examples (the synthetic and silly flower example and the > >> real-world brainstorming example) are really the same. > >> What I need is to use the data that user put in the field1 as the > >> parameter of the query that defines the allowed values set in the > >> field2. > >> > >> Anyway, I'll try to clarify: > >> So the user edits the Flower Rose. He entered the Genus of Rose : > >> Rosa. He entered the color of Rose - for example Red. The field > >> 'related flowers' will be the listbox of all red flowers with genus > >> Rosa: > >> > >> {{field|related flowers|values from > >> > >> > query=[[Category:$1]][[Color::$2]][[Owner::+]]|substitute=Flowers[Genus],Flowers[Color]|input > >> type=listbox}} > >> > >> ----- > >> Yury Katkov > >> > >> > >> > >> On Mon, Oct 1, 2012 at 6:35 PM, Yaron Koren <ya...@wi...> > wrote: > >> > Hi Yury, > >> > > >> > I don't understand - are your data needs more complex than what you > put > >> > in > >> > that sample form definition code earlier? If so, can you revise that > >> > sample > >> > code to more accurately reflect what you want your form to look like? > >> > > >> > -Yaron > >> > > >> > > >> > On Mon, Oct 1, 2012 at 2:53 AM, Yury Katkov <kat...@gm...> > >> > wrote: > >> >> > >> >> Hi Yaron! > >> >> > >> >> There is no problem in passing the Session parameter I can use either > >> >> 'query string' parameter of the formlink or the urlget function. > >> >> In this Trend form my main problem is to restrict the set of possible > >> >> values which will be displayed in the "Related events" listboxes: > >> >> 1) All these values are pagenames for pages in Events category > >> >> 2) All these pages belongs to the same Session as the Trend, that I'm > >> >> currently looking at > >> >> > >> >> The same is for related Technologies: I want to link objects only > >> >> inside the session, so that the participants of the session "The > >> >> Future of Food" don't try to link there Trends and possible events > >> >> with objects from the Session "The future of titan manufacturing ". > >> >> > >> >> The two restrictions to possible values in the listbox I'have just > >> >> noted can be three or four; and all of them can be dependent on what > >> >> is currently entered in the form. > >> >> ----- > >> >> Yury Katkov > >> >> > >> >> > >> >> > >> >> On Mon, Oct 1, 2012 at 4:26 AM, Yaron Koren <ya...@wi...> > >> >> wrote: > >> >> > Hi Yury, > >> >> > > >> >> > This sounds like a very different example - here the original, > >> >> > "source" > >> >> > field is just a hidden field that gets its value from the query > >> >> > string. > >> >> > In > >> >> > that case, I would think the ideal solution would be to use the > >> >> > UrlGetParameters extension, to directly use the query string value: > >> >> > > >> >> > https://www.mediawiki.org/wiki/Extension:UrlGetParameters > >> >> > > >> >> > I'm not entirely sure that this would work, because I don't > remember > >> >> > which > >> >> > parts of the form syntax let you embed a parser function within > them > >> >> > - > >> >> > but > >> >> > if it doesn't work, then getting it to work would seem like the > >> >> > simpler, > >> >> > and > >> >> > better, solution. > >> >> > > >> >> > -Yaron > >> >> > > >> >> > > >> >> > On Sun, Sep 30, 2012 at 3:41 PM, Yury Katkov < > kat...@gm...> > >> >> > wrote: > >> >> >> > >> >> >> Hi Yaron! > >> >> >> > >> >> >> My example is surely very silly and synthetic so let's just forget > >> >> >> about the flowers > >> >> >> I'll try to explain the real problem I faced with in a Foresight > >> >> >> wiki. > >> >> >> > >> >> >> Here is my problem domain. There are several brainstorming > sessions > >> >> >> about the forecasts on a distant future, all of them have > different > >> >> >> topics. Each of those sessions has various objects as the results > of > >> >> >> the brainstorming: future trends, possible technologies that may > >> >> >> appear in the future, possible important events. All these data > are > >> >> >> loaded to the wiki using the semantic forms. After the > brainstorming > >> >> >> ends, the participants can improve the objects, categorize them > and > >> >> >> link them together. > >> >> >> > >> >> >> Here for example I have the Trend objects. I want to connect > Trends > >> >> >> to > >> >> >> the Events and to Technologies but only inside the current > >> >> >> brainstorming session. > >> >> >> > >> >> >> The semantic form for Trend will look like that: > >> >> >> <FORM>... > >> >> >> {{{field|session name|hidden|required}}} // the only valid way to > >> >> >> create a trend is using the #formlink on a Session's page. > Formlink > >> >> >> will fill this value with the name of the session > >> >> >> > >> >> >> {{{field|related events|values from > >> >> >> query=[[Category::Event]][[session::$1]]|substitute=Trend[session > >> >> >> name] | input type=two listboxes}}} > >> >> >> > >> >> >> {{{field|related technologies|values from > >> >> >> > >> >> >> > query=[[Category::Technology]][[session::$1]]|substitute=Trend[session > >> >> >> name] | input type=two listboxes}}} > >> >> >> ... > >> >> >> <END OF FORM> > >> >> >> > >> >> >> I can use values from concept but it's a very bad workaround if I > >> >> >> have > >> >> >> many sessions. > >> >> >> > >> >> >> I hope now the case is more clear. > >> >> >> ----- > >> >> >> Yury Katkov > >> >> >> > >> >> > > >> > > >> > > >> > > >> > > >> > -- > >> > WikiWorks · MediaWiki Consulting · http://wikiworks.com > > > > > > > > > > -- > > WikiWorks · MediaWiki Consulting · http://wikiworks.com > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: Yury K. <kat...@gm...> - 2012-10-01 16:37:00
|
I haven't tried #show yet but I have tried #ask. It seems that the parser functions cannot be called inside of {{{field}}} tag. > So is that definitely the case, or are you just guessing that you might require this feature in > the future? Definitely-definitely. We need some kind of solution for this now, whatever hackish it may be, and I can see that there will be more projects where such feature is needed (especially the projects on social roadmapping and strategic foresight). ----- Yury Katkov On Mon, Oct 1, 2012 at 8:06 PM, Yaron Koren <ya...@wi...> wrote: > Ah, that's true, I didn't think about the "edit with form" case. Well, for > that, you could use #show, assuming the value is being stored semantically - > and you could have an #ifexists call to tie the whole thing together, so > that #urlget is called for new pages, and #show is called for existing > pages. It's a hack, but it wouldn't require any custom development. > > As for "parameters may not be defined from the beginning" - that's the > central issue. New development would be required only if (a) they're not, > and (b) there's more than one of them - since a single editable parameter > can be handled by the "values dependent on" feature. So is that definitely > the case, or are you just guessing that you might require this feature in > the future? > > -Yaron > > On Mon, Oct 1, 2012 at 11:36 AM, Yury Katkov <kat...@gm...> wrote: >> >> I need the first one. There are some problems with this >> UrlGetParameters approach: it seems that it will work for article >> creation using the #formlink but it will not work for article edition >> using 'Edit with Form' button. Another problem is that the parameters >> for allowed value set restrictions may not be defined from the >> beginning. >> >> Linking together pages inside the website section is typical example >> of such feature. Am I right that the most frighting thing here is >> making ask-queries in AJAX code? >> ----- >> Yury Katkov >> >> >> >> On Mon, Oct 1, 2012 at 7:16 PM, Yaron Koren <ya...@wi...> wrote: >> > Hi, >> > >> > No, the two examples are different - the "silly" one involves two >> > "substitions", based on editable fields, while the "real" one involves >> > one >> > substitution, directly from the query string. Can you clarify the >> > discrepancy? What is the form that you actually need? >> > >> > -Yaron >> > >> > >> > On Mon, Oct 1, 2012 at 11:11 AM, Yury Katkov <kat...@gm...> >> > wrote: >> >> >> >> Hi Yaron! >> >> >> >> No, these two examples (the synthetic and silly flower example and the >> >> real-world brainstorming example) are really the same. >> >> What I need is to use the data that user put in the field1 as the >> >> parameter of the query that defines the allowed values set in the >> >> field2. >> >> >> >> Anyway, I'll try to clarify: >> >> So the user edits the Flower Rose. He entered the Genus of Rose : >> >> Rosa. He entered the color of Rose - for example Red. The field >> >> 'related flowers' will be the listbox of all red flowers with genus >> >> Rosa: >> >> >> >> {{field|related flowers|values from >> >> >> >> >> >> query=[[Category:$1]][[Color::$2]][[Owner::+]]|substitute=Flowers[Genus],Flowers[Color]|input >> >> type=listbox}} >> >> >> >> ----- >> >> Yury Katkov >> >> >> >> >> >> >> >> On Mon, Oct 1, 2012 at 6:35 PM, Yaron Koren <ya...@wi...> >> >> wrote: >> >> > Hi Yury, >> >> > >> >> > I don't understand - are your data needs more complex than what you >> >> > put >> >> > in >> >> > that sample form definition code earlier? If so, can you revise that >> >> > sample >> >> > code to more accurately reflect what you want your form to look like? >> >> > >> >> > -Yaron >> >> > >> >> > >> >> > On Mon, Oct 1, 2012 at 2:53 AM, Yury Katkov <kat...@gm...> >> >> > wrote: >> >> >> >> >> >> Hi Yaron! >> >> >> >> >> >> There is no problem in passing the Session parameter I can use >> >> >> either >> >> >> 'query string' parameter of the formlink or the urlget function. >> >> >> In this Trend form my main problem is to restrict the set of >> >> >> possible >> >> >> values which will be displayed in the "Related events" listboxes: >> >> >> 1) All these values are pagenames for pages in Events category >> >> >> 2) All these pages belongs to the same Session as the Trend, that >> >> >> I'm >> >> >> currently looking at >> >> >> >> >> >> The same is for related Technologies: I want to link objects only >> >> >> inside the session, so that the participants of the session "The >> >> >> Future of Food" don't try to link there Trends and possible events >> >> >> with objects from the Session "The future of titan manufacturing ". >> >> >> >> >> >> The two restrictions to possible values in the listbox I'have just >> >> >> noted can be three or four; and all of them can be dependent on what >> >> >> is currently entered in the form. >> >> >> ----- >> >> >> Yury Katkov >> >> >> >> >> >> >> >> >> >> >> >> On Mon, Oct 1, 2012 at 4:26 AM, Yaron Koren <ya...@wi...> >> >> >> wrote: >> >> >> > Hi Yury, >> >> >> > >> >> >> > This sounds like a very different example - here the original, >> >> >> > "source" >> >> >> > field is just a hidden field that gets its value from the query >> >> >> > string. >> >> >> > In >> >> >> > that case, I would think the ideal solution would be to use the >> >> >> > UrlGetParameters extension, to directly use the query string >> >> >> > value: >> >> >> > >> >> >> > https://www.mediawiki.org/wiki/Extension:UrlGetParameters >> >> >> > >> >> >> > I'm not entirely sure that this would work, because I don't >> >> >> > remember >> >> >> > which >> >> >> > parts of the form syntax let you embed a parser function within >> >> >> > them >> >> >> > - >> >> >> > but >> >> >> > if it doesn't work, then getting it to work would seem like the >> >> >> > simpler, >> >> >> > and >> >> >> > better, solution. >> >> >> > >> >> >> > -Yaron >> >> >> > >> >> >> > >> >> >> > On Sun, Sep 30, 2012 at 3:41 PM, Yury Katkov >> >> >> > <kat...@gm...> >> >> >> > wrote: >> >> >> >> >> >> >> >> Hi Yaron! >> >> >> >> >> >> >> >> My example is surely very silly and synthetic so let's just >> >> >> >> forget >> >> >> >> about the flowers >> >> >> >> I'll try to explain the real problem I faced with in a Foresight >> >> >> >> wiki. >> >> >> >> >> >> >> >> Here is my problem domain. There are several brainstorming >> >> >> >> sessions >> >> >> >> about the forecasts on a distant future, all of them have >> >> >> >> different >> >> >> >> topics. Each of those sessions has various objects as the results >> >> >> >> of >> >> >> >> the brainstorming: future trends, possible technologies that may >> >> >> >> appear in the future, possible important events. All these data >> >> >> >> are >> >> >> >> loaded to the wiki using the semantic forms. After the >> >> >> >> brainstorming >> >> >> >> ends, the participants can improve the objects, categorize them >> >> >> >> and >> >> >> >> link them together. >> >> >> >> >> >> >> >> Here for example I have the Trend objects. I want to connect >> >> >> >> Trends >> >> >> >> to >> >> >> >> the Events and to Technologies but only inside the current >> >> >> >> brainstorming session. >> >> >> >> >> >> >> >> The semantic form for Trend will look like that: >> >> >> >> <FORM>... >> >> >> >> {{{field|session name|hidden|required}}} // the only valid way to >> >> >> >> create a trend is using the #formlink on a Session's page. >> >> >> >> Formlink >> >> >> >> will fill this value with the name of the session >> >> >> >> >> >> >> >> {{{field|related events|values from >> >> >> >> query=[[Category::Event]][[session::$1]]|substitute=Trend[session >> >> >> >> name] | input type=two listboxes}}} >> >> >> >> >> >> >> >> {{{field|related technologies|values from >> >> >> >> >> >> >> >> >> >> >> >> query=[[Category::Technology]][[session::$1]]|substitute=Trend[session >> >> >> >> name] | input type=two listboxes}}} >> >> >> >> ... >> >> >> >> <END OF FORM> >> >> >> >> >> >> >> >> I can use values from concept but it's a very bad workaround if I >> >> >> >> have >> >> >> >> many sessions. >> >> >> >> >> >> >> >> I hope now the case is more clear. >> >> >> >> ----- >> >> >> >> Yury Katkov >> >> >> >> >> >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > -- >> >> > WikiWorks · MediaWiki Consulting · http://wikiworks.com >> > >> > >> > >> > >> > -- >> > WikiWorks · MediaWiki Consulting · http://wikiworks.com > > > > > -- > WikiWorks · MediaWiki Consulting · http://wikiworks.com |