Re: [Semediawiki-user] Selecting a dropdown in a form depending on an earlier dropdown

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

Hi,

I don't actually see how doing a form reload would make things easier -
especially since it would take work to preserve the state of the form (the
values of all the current fields) after the refresh. In any case, feel free
to modify your local copy of Semantic Forms to get all of this working; and
if you do get it working, to submit a patch for the change.

On Fri, Sep 26, 2014 at 10:10 AM, Frank Baxmann <se...@fr...>
wrote:

> Hi Yaron,
>
>  >>right now there's no standard way for fields to know about each
> others' currently-selected values<<
>
> Yes that's right, but not needed for the solution i suggested. One or
> many depending fields don't need
> to know the currently-selected value in the "root" field, if you save
> and reload the page in background.
> They only need to know this is, if you want a solution without
> saving+reloading the page. This would for
> sure be the nicer way, but for sure also much work in code base to
> implement this.
>
> If you are making background save/reload the user will for sure see
> this, it needs maybe 1-2 seconds.
> But this is in my eyes acceptable comparing to the huge range of
> possibilities added by this.
>
> I am developing some "extension" for MW in use as enterprise wiki. It is
> a kind of DMS.
> Most of the parts are scripts at backend, e.g. auto generating of pages,
> auto import them and so on.
>
> Greetings
>
> Frank
>
> On 26.09.2014 15:54, Yaron Koren wrote:
> > Hi Frank,
> >
> > Sorry I didn't respond to your question before. I don't know how easy
> > that behavior would be to implement, actually;  right now there's no
> > standard way for fields to know about each others' currently-selected
> > values, which is at least one other piece of the puzzle that would
> > have to be implemented.
> >
> > As I said before, my guess is that you're trying to do some sort of
> > questionnaire thing, where there's one generic form that takes its
> > "questions" from different pages; and if that's the case, I'd
> > recommend going with hardcoded forms instead, though of course it's
> > not as nice a solution.
> >
> > Using "show on select", as Erwin suggested, could also work, but given
> > the apparent difference between what I'll call the different
> > questionnaires, it would essentially amount to the same thing.
> >
> > -Yaron
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Semediawiki-user mailing list
> Sem...@li...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>



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