uhm .... ok, this makes perfect sense .... I'm trying to display a field that contains html codes (very basic ones, like 'a', 'strong', 'u' and so on) edited through a wysiwyg ...ideally it would be in a div with a basic css ongoing with it.... I'll put in the returned values of the controller also the record itself so I'll be able to modify it "before" representing it into the view..... thanks for the clarification
On 23 Feb, 03:21, Massimo Di Pierro <[email protected]> wrote: > widgets are only used for input. If the field is not writable SQLFORM > uses db.table.field.represent(value) instead. > > On Feb 22, 3:37 pm, Niphlod <[email protected]> wrote: > > > Hi, am I missing something or custom widgets when field is not > > writable ends up to be forgotten (i.e. default string representation > > is done on these fields)? > > > I'm using something like: > > > #controller > > record = db.mytable[1] > > record.textfield.readable = False > > record.textfield.widget = my_widget > > form = SQLFORM(db.mytable, record): > > ................ > > > and > > > #view > > {{=form.custom.begin}} > > {{=form.custom.widget.textfield}} > > {{=form.custom.submit}} {{=form.custom.end}} > > > any simple workaround ?
