Opened 17 years ago
Closed 17 years ago
#37 closed enhancement (fixed)
Handle CLOS object references ('foreign keys') in form renderers
Reported by: | Slava Akhmechet | Owned by: | Slava Akhmechet |
---|---|---|---|
Priority: | medium | Milestone: | 0.1 |
Component: | weblocks | Version: | pre-0.1 |
Keywords: | renderers clos foreign key reference | Cc: |
Description
Currently form renderers don't handle non-inline CLOS object references (effectively, foreign keys). We need to design a mechanism that will allow users to select a foreign CLOS object in a form.
One option is to provide a generic function that will return a list of CLOS objects that can be displayed in a form. The form renderer will then grab a name of each of these objects and display it in a dropdown.
Change History (4)
comment:1 Changed 17 years ago by
Priority: | critical → medium |
---|
comment:2 Changed 17 years ago by
comment:4 Changed 17 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed. Reference slots are rendered as drop down by calling 'form-potential-values'. A special parser is called to convert object IDs back to objects.
Note: See
TracTickets for help on using
tickets.
Explore the possibility of using type declarations instead of magick "-ref" to determine if an object is to be rendered inline. This needs to be considered carefully as it may not be a good idea.