Re: [Semediawiki-user] [SF] Managing variable number of needed fields

[Yaron K. <ya...@wi...>]

Hi Erin,

I'm not sure I entirely understand the specifics, but it seems like the
overall goal is to set the appearance of one form (B) based on the data
entered into another page (via form A). Unfortunately this is not simple,
and may actually be impossible depending on what exactly it is you need.

However, there may be an easier solution all around. If you really have
fields called "#5 Metal's Weight" and so on, the better solution is to use
multiple-instance templates - which let the user add or remove groups of
fields, instead of having everything hardcoded in the form. (You would then
need to change the semantic storage to call either #subobject or
#set_internal.) Such an interface may be simple enough for users that you
don't need to have the form enforce the connection between the two pages.
If you do want to still enforce the connection, it's possible that the
"minimum instances" and "maximum instances" parameters could be used for
that, in combination with an #ask query - I really don't know if that would
work.

-Yaron


On Thu, Oct 24, 2013 at 5:58 PM, Erin Crain <eri...@gm...> wrote:

>  Hello! I've got a question about Semantic Forms that is (hopefully) a very
> simple one for someone here.
>
> Goal: Input information about items sent in to be customized, the number
> and type of which vary by order
>
> On form A, users would input information about a custom order received from
> a client, including how many items the client sent. Items can be stone or
> metal and a wide range of quantities.
>
> On form B, I am trying to figure out how to auto show/hide fields based on
> those numbers.
>
> *Form A Example*
> Fields: Descriptions (Example)
> Date Received: Date (24-Oct-2013)
> Client: Client's Name (Ex: Veridian Dynamics)
> Number of Stone Items: # Stone (Ex: 3)
> Number of Metal Items: # Metal (Ex: 2)
> Services Requested: Polishing, Engraving, Appraisal, and/or Other (Ex:
> Polishing, Other)
>
> Form B would be a link on the results of Form A pages.
>
> *Form B Example*
> Order Info: Autopopulated field with order name, generated from Form A
> results (Ex: Veridian Dynamics order received on 24-Oct-2013)
> *Stone Items*
> #1 Stone's Name: Provided by customer (Ex: Pillow)
> #1 Stone's Description: Text by users (Ex: Gray, cold, hard, not very
> fluffy)
> #1 Stone's Weight: Number (Ex: 2.5 kg)
> #2 Stone's Name:
> #2 Stone's Description:
> #2 Stone's Weight:
> #3 Stone's Name:
> #3 Stone's Description:
> #3 Stone's Weight:
> Not present for information about this order's custom items:
>
> #4 Stone's Name:
> #4 Stone's Description:
> #4 Stone's Weight:
> #5 Stone's Name:
> #5 Stone's Description:
> #5 Stone's Weight:
>
> *Metal Items*
> #1 Metal's Name: Provided by customer (Ex: Shiny)
> #1 Metal's Description: Text by users (Ex: Gray, dull, matte)
> #1 Metal's Weight: Number (Ex: 0.5 kg)
> #2 Metal's Name:
> #2 Metal's Description:
> #2 Metal's Weight:
> Not present for information about this order's custom items:
>
> #3 Metal's Name:
> #3 Metal's Description:
> #3 Metal's Weight:
> #4 Metal's Name:
> #4 Metal's Description:
> #4 Metal's Weight:
> #5 Metal's Name:
> #5 Metal's Description:
> #5 Metal's Weight:
>
>
> I've tried show on select. I've tried putting each sample's info fields
> into separate divs. I've tried hiding parser functions in the template. I
> haven't had much luck. Any ideas?
>
> Thank you!
> - Erin
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> _______________________________________________
> Semediawiki-user mailing list
> Sem...@li...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>



-- 
WikiWorks · MediaWiki Consulting · http://wikiworks.com