That's actually the approach I use on a couple of different web pages. I never have "several hundred" dialog boxes, but I do often have most of a hundred. It really doesn't seem to slow things down a lot, although none of the pages I use that technique on are important enough that it matters.
It should be simple to use a little bit of Javascript to change the content of the dialog box when the button is clicked so that you can use a single dialog box rather than several hundred. However, I don't think there's an easy way at the moment of adding that javascript hook. Let me get back to you on that with either an example or a fix to make it easy. Bryan > > thank you for explaining this. Your suggestion works, but unless I'm missing > something this approach pre-populates a dialog for every item. > > In our use-case we create a kanban board with a card for each "item" - so we > can have maybe several hundred "items" on a single show page. The current > design is that we only load titles+ids to populate the board, then if the > user clicks on a specific card we pull the full item record into a popup > dialog. Creating dialogs for all of the items is too big and slow, hence the > current Hobo.ajaxRequest call. I noticed in the 1.4 changes guide that > you've rationalized the various AJAX mechanisms so that's why I started > fiddling with data-rapid. > -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
