jdev - 2020-12-06


  1. jonas’

    also: https://up-for-grabs.net/#/filters?tags=xmpp

  2. jubalh

    > I want to involve in this organization. Is there any open project to contribute to? Check out profanity;)

  3. jonas’

    (they’re gone already, I just wanted to mention up-for-grabs)

  4. Sam Whited

    Possibly stupid question about data forms: does the order of the title and instruction fields matter? All the examples put them at the top, and obviously the order of actual fields matters, but can you have a title or instructions anywhere in the form or are they just always at the top?

  5. Zash

    Probably not, tho I guess internal order fo multiple <instructions> might affect how the form gets presented. I'd actually worry more about multiple <instructions>, don't remember seeing that being allowed before.

  6. lovetox

    Sam Whited, no

  7. lovetox

    if your question is if you can use it to describe fields

  8. lovetox

    The OPTIONAL <title/> and <instructions/> elements enable the form-processing entity to label the form as a whole ..

  9. lovetox

    this sentence implies for me instruction and title is for a form, and not for fields

  10. lovetox

    so yes you can put the instruction somewhere between fields, but its still a instruction for the form and not for the filed

  11. lovetox

    and clients have a special place where the put the form instruction in the GUI

  12. Zash

    <field>s have a <desc> tag for long-form field description

  13. Zash

    There's <field type=fixed> for "headings" within the form

  14. Sam Whited

    Sounds good to me, thanks.

  15. Sam Whited

    I'm not sure how the spec means it to be, but as long as no one else is allowing instructions to be scattered around the form.

  16. lovetox

    you can scatter them, but i can only talk for Gajim, you cant control with that where i display them

  17. lovetox

    its for the form, and i place them at the top no matter where you scatter them

  18. lovetox

    and yes the correct way is type=fixed

  19. lovetox

    you can see that work in prosodys MUC Config form

  20. lovetox

    and Gajim

  21. Zash

    Is anyone actually using multiple <instructions> anywhere?

  22. lovetox

    https://share.hoerist.com/philipp/p0GPfFzBgUo7VSic/Screenshot_from_2020-12-06_20-14-33.png

  23. lovetox

    ^ Sam Whited

  24. Zash

    That looks familiar. i3? :)

  25. lovetox

    yes

  26. Zash

    ^5

  27. lovetox

    btw Zash, look at the Persistent option

  28. lovetox

    i think its not good to put a description into the label

  29. lovetox

    you have a long desc anyway, Gajim shows it in the tooltip

  30. Zash

    Mmmm

  31. Zash

    Lots of "for/in the room" that might be considered redundant

  32. lovetox

    and i should think about if tooltip is really good, its not easy to discover

  33. lovetox

    yeah the word room is mentioned a lot

  34. Zash

    The concept of "persistence", especially as a boolean, is a bit weird and I'd like to replace it ... one day

  35. lovetox

    The form instruction is here is also a bit redundant

  36. lovetox

    submit this form, yeah no shit

  37. Zash

    Hahaha

  38. Zash

    https://xmpp.org/extensions/xep-0004.html#protocol says <instructions> shouldn't contain newlines, but https://xmpp.org/extensions/xep-0045.html#example-158 has a whole pile of them

  39. lovetox

    totally redundant again

  40. lovetox

    it lists the full default configuration

  41. lovetox

    in the form that shows you the default configuration

  42. lovetox

    makes sense

  43. Zash

    Been that way since 2013, before that instructions was identical to title

  44. Zash

    🤷️