Thanks, that's a very good advice. I'll create an issue to use jquery's .on() :)
El 14-07-2015 a las 17:28, HuBandiT escribió: > Update: .live() seems to be deprecated, .on() > <http://api.jquery.com/on/> should now be used instead. > > 2015. július 14., kedd 17:24:13 UTC+2 időpontban HuBandiT a következőt írta: > > One issue that was important in making this decision but I forgot to > mention: a regular .new form properly displays the jquery-ui date > picker - I tried to use <input-many> which does JS on the client > side to create the form elements for a new blank record, but this > blank record did not pop up the date selector. I therefore assume > the date selectors get hooked onto the DOM only once, when the > document is loaded. when the <input-many> JS creates new date > fields, these fields don't automatically get the magic to pop up a > date picker. I assume either the <input-many> new row creator JS > should be enhanced to pay an attention to this, or the original > datepicker hooking should switch to using JQuery .live() > <http://api.jquery.com/live/> to ensure client-side-generated items > are not left out of this piece of Hobo Magic. > > 2015. július 14., kedd 17:15:05 UTC+2 időpontban HuBandiT a > következőt írta: > > Thank you. > > I ended up putting a new form on the bottom; and a table on the > top with the <bootstrap-table-actions/> as the last column; it > is rare that the user actually needs to edit a just entered > record, so it is ok to have that happen on a separate screen (a > stock edit page), the update action however comes back to this > screen instead of going to #show. > > This ended up being easy to develop, while still quite intuitive > to use. > > 2015. július 7., kedd 10:37:58 UTC+2 időpontban Ignacio Huerta a > következőt írta: > > Hi! > > Maybe you want something similar to the screenshot in the > first message > of this thread: > https://groups.google.com/d/msg/hobousers/S4f5-D6jGsk/PcaFD7zofGAJ > > > The idea is: > > * You create a table inside a part > * Outside the table, you create a form to add a new record > * Every time a new record is added, the table is updated almost > instantly with Ajax > * Each row has a "delete" button to remove a record also > with Ajax > > > Alternatively you could try redefining the input many tag > HTML and CSS > to make every record use less space, but it might be a bit > harder. > > Warm regards, > Ignacio > > > El 05-07-2015 a las 04:29, HuBandiT escribió: > > Greetings, > > > > [Hobo 2.1.1 with default Bootstrap 2.3.2 theme.] > > > > I have a parent model (no user-editable fields) that has > about 5-6 child > > models, the child model has about 4-5 short fields (a > company name, two > > dates, a dollar amonut, an enum_string field). > > > > The default edit form for the parent, with the input-many > for the > > children is functionally complete, but it is quite > wasteful of screen > > estate. On a full HD screen I can only see/edit maybe two > child records. > > > > What would be the best way to replace it with something, > that looks like > > a table with columns titles for the fields of the child > model, and rows > > for the child instances, with a UI element to delete > children in the > > table already, as well as UI to enter new children? > Preferrably without > > visible form reloading. Kinda akin to how input-many > works, which is > > perfect for my purposes, aside from the screen estate issue. > > > > I know <table> can use an in-place editor - but does it > also offer > > functionality to add and remove children? > > > > Or should this all be done with CSS? I don't have much CSS > experience, > > but it kinda sounds to me like it might be possible that way? > > > > What would be the best way? > > > > Thanks in advance. > > > > -- > > You received this message because you are subscribed to > the Google > > Groups "Hobo Users" group. > > To unsubscribe from this group and stop receiving emails > from it, send > > an email to [email protected] > > <mailto:[email protected]>. > > To post to this group, send email to [email protected] > > <mailto:[email protected]>. > > Visit this group at http://groups.google.com/group/hobousers. > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google > Groups "Hobo Users" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at http://groups.google.com/group/hobousers. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/hobousers. For more options, visit https://groups.google.com/d/optout.
