hi,

Am Dienstag, 19. Februar 2013, 16:30:28 schrieb Thomas Friedrichsmeier:
> On Monday 18 February 2013, meik michalke wrote:
> > > >   - rk.XML.switch()
[...]
> > what do you think?
>
> Looks good to me.

great.

> Ok, optionset next. I tried translating the first optionset example from the
> "primary" documentation into rkwarddev. This is what I got:

cool, i've added the example to the docs. i also changed the signatures of
rk.XML.optionset() and rk.XML.optioncolumn() a little, so that <optiondisplay>
is added to <content> automatically (can be turned off, but this way you don't
need to call rk.XML.optiondisplay() yourself), and the id of optioncolumns
will be generated from the connected id automatically. so:

> rk.XML.optionset (
>   content = list (rk.XML.optiondisplay (), rk.XML.row (firstname, lastname,
>     genderselect)),
>   optioncolumn = list (
>     rk.XML.optioncolumn("firstnames", connect=firstname, modifier="text"),
>     rk.XML.optioncolumn("lastnames", connect=lastname, modifier="text"),
>     rk.XML.optioncolumn("genders", connect=genderselect)
>   )
> )

is shortened to:

  rk.XML.optionset(
    content = list(
      rk.XML.row(firstname, lastname, genderselect)),
    optioncolumn = list(
      rk.XML.optioncolumn(firstname, modifier="text"),
      rk.XML.optioncolumn(lastname, modifier="text"),
      rk.XML.optioncolumn(genderselect)
    )
  )

which produces:

<optionset id="ost_rGGFFGGMFG">
  <content>
    <optiondisplay />
    <row id="row_inGGFFGGMF">
      <input label="Given name(s)" id="inp_Givennms" />
      <input label="Family name" id="inp_Familynm" />
      <radio id="rad_Gender" label="Gender">
        <option label="Male" value="m" />
        <option label="Female" value="f" />
      </radio>
    </row>
  </content>
  <optioncolumn id="ocl_inpGvnnmst" connect="inp_Givennms.text"
    label="Given name(s)" />
  <optioncolumn id="ocl_inpFmlynmt" connect="inp_Familynm.text"
    label="Family name" />
  <optioncolumn id="ocl_radGender" connect="rad_Gender" label="Gender" />
</optionset>


am i correct that for the JavaScript part you will only need the
<optioncolumn> ids, but not the ones used inside <content>? i would then have
to tweak rk.JS.scan() accordingly.


viele grüße :: m.eik

--
dipl. psych. meik michalke
institut f"ur experimentelle psychologie
abt. f"ur diagnostik und differentielle psychologie
heinrich-heine-universit"at d-40204 d"usseldorf

Attachment: signature.asc
Description: This is a digitally signed message part.

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
RKWard-devel mailing list
RKWard-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rkward-devel

Reply via email to