Hi Rafael, On Nov 25, 10:20 pm, Rafael <[email protected]> wrote:
> 1. I had to build a new input-presentation class to allow me to make > read-only or disable an input field. I've seen a thread here about > that issue and I've followed the solution by Leslie (http:// > groups.google.com/group/weblocks/msg/d63f9bf794ada2ec) so I made a new > class called enhanced-input-presentation and a specialized method > render-view-field-value for that class. I've to say that it have been > easy to do (thanks to Leslie). My next problem is that I need this to > make an input field disabled when modifying and enabled when adding. > I'm using a gridedit widget and a scaffolded form-view for editing. One way to do this is to have a base view where the field is enabled and a child view where it is not. Then specialize the appropriate methods for your grid (dataedit-create-new-item-widget and friends) to choose the correct view. > 2. I have created a new store for managing the virtual mail user and > alias database. But I did not found an example about where I should > call commit-transaction. I need that for commiting changes to the mail > services (postfix, saslauthd, courier-authd), maybe on-delete-items- > completed and on-add-item-completed? Could you post your store somewhere? The standard way used to commit changes is persist-object which gets called after every successful form submit, so your store will have to specialize it properly. > BTW, thanks to all the people involved in this great project. You're welcome! Please continue asking if the above isn't clear enough. Leslie -- You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en.
