Jan Rychter <[email protected]> writes:
> You'll notice that there is no :item-data-view specified -- it should
> not be necessary, as the gridedit widget displays data using the table
> view and allows editing using the form view. Nobody ever displays the
> data using a data-view.
I am also relying on this on hfsbo.com.
> There has been a regression in weblocks, and I can't seem to find
> it. The problem is with dataform, its render-dataform-form function. See
> the (when break-out) clause -- it switches the ui-state to :data. This
> in itself is not a big problem, unless the form actually gets
> rendered -- in my case, there is no data view, so this will fail.
dataform is doing what it should; instead, focus on gridedit and its
CPL. dataedit-mixins and other driller-downs are responsible for
registering the proper hooks in the dataform.
> I am not sure where the problem is -- is it the state switching in
> dataform, or gridedit trying to render the form in the :data state
> (which should not happen). I am sure that the problem wasn't there
> several months ago.
Do you have custom dataedit-create-{new-item,drilldown}-widget methods?
If so, are you using weblocks-s11:dataedit-editor-initargs or the
next-method? Otherwise, are you calling render-widget-body directly on
the gridedit, or passing :inlinep t?
> Could this be related to my logs being flooded with these messages?
>
> STYLE-WARNING: During the rendering phase, #<GRIDEDIT MYAPP::TAGS> was
> marked dirty and skipped after already being rendered, which should
> typically be done only during action handling
This is probably due to dataedit-update-operations. We should have a
suppress-dirty for this sort of thing.
On a side note, any "gotchas" especially for newbies that can be checked
for ought to be turned into these warnings (which are disabled when
debugging is off).
--
I write stuff at http://failex.blogspot.com/ now. But the post
formatter and themes are terrible for sharing code, the primary
content, so it might go away sooner or later.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
