August 2007 - cl-weblocks-ticket@common-lisp.net

[cl-weblocks-ticket] #1: Design paging functionality for datagrid widget.
by cl-weblocks 23 Oct '07

23 Oct '07

#1: Design paging functionality for datagrid widget. -----------------------------+---------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.1 Component: weblocks | Version: head Keywords: paging datagrid | -----------------------------+---------------------------------------------- Currently items in the datagrid are not paged. Paging functionality needs to be designed and implemented. It would be nice if some innovation was put into the control since standard web paging has deficiencies. In particular, it's hard to browse through pages or go to specific page. Perhaps some form of a slider would work here? -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/1> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 3

[cl-weblocks-ticket] #32: Provide additional navigation aids to improve accessibility (using <link rel='home/next/prev'>)
by cl-weblocks 19 Oct '07

19 Oct '07

#32: Provide additional navigation aids to improve accessibility (using <link rel='home/next/prev'>) --------------------------------------------------------------+------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Keywords: accessibility navigation link rel home next prev | --------------------------------------------------------------+------------- We should fish data from the navigation widget to provide additional navigation aids in the page header (using <link rel='home/next/prev/etc.'>) -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/32> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #2: Allow viewing and editing gridedit items
by cl-weblocks 10 Oct '07

10 Oct '07

#2: Allow viewing and editing gridedit items -------------------------------------+-------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: gridedit view edit item | -------------------------------------+-------------------------------------- Currently items in a gridedit widget cannot be modified or viewed in closer detail. Gridedit needs to be enhanced to allow for clicking on a row (or a particular link in a row) to invoke a dataform widget. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/2> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #5: Gridedit item deletion confirmation
by cl-weblocks 06 Oct '07

06 Oct '07

#5: Gridedit item deletion confirmation ------------------------------------+--------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: item deletion gridedit | ------------------------------------+--------------------------------------- When items are deleted from the gridedit widget there is currently no confirmation request. A confirmation dialog needs to be added. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/5> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 2

[cl-weblocks-ticket] #37: Handle CLOS object references ('foreign keys') in form renderers
by cl-weblocks 27 Sep '07

27 Sep '07

#37: Handle CLOS object references ('foreign keys') in form renderers --------------------------------------------------+------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: critical | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: renderers clos foreign key reference | --------------------------------------------------+------------------------- 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. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/37> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 4

[cl-weblocks-ticket] #57: Ensure all unit tests pass on all supported CL implementations
by cl-weblocks 18 Sep '07

18 Sep '07

#57: Ensure all unit tests pass on all supported CL implementations ----------------------------------------+----------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: unit tests implementations | ----------------------------------------+----------------------------------- Currently many unit tests fail on implementations other than the main development one (SBCL). We need to ensure all unit tests pass on all supported implementations. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/57> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 2

[cl-weblocks-ticket] #26: Don't hide validation error summary for long forms
by cl-weblocks 13 Sep '07

13 Sep '07

#26: Don't hide validation error summary for long forms --------------------------------------+------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Keywords: long forms error summary | --------------------------------------+------------------------------------- Currently a validation error summary is rendered on top of a form but is hidden via CSS. We should modify the code not to hide the summary for long forms for better usability. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/26> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #27: Customize widget printing to include their names (to ease debugging)
by cl-weblocks 13 Sep '07

13 Sep '07

#27: Customize widget printing to include their names (to ease debugging) ---------------------------------------+------------------------------------ Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Keywords: widget printing debugging | ---------------------------------------+------------------------------------ When widgets are printed in the debugger their memory address is displayed. We should customize the printer to output widget names - an identifier much more useful to the programmer during debugging. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/27> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #36: Modify renderers to allow specialization on slot types
by cl-weblocks 08 Sep '07

08 Sep '07

#36: Modify renderers to allow specialization on slot types ---------------------------------------------------+------------------------ Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: high | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: renderers slots types dropdown custom | ---------------------------------------------------+------------------------ Currently specializing renderers to output various types in a custom manner (dropdowns for lists, checkboxes for booleans, etc.) is broken because when slots are set to nil, type information is lost. We need to modify renderers to accept one more argument 'slot-type', and modify 'visit-object-slots' to pass this argument to renderers. We also need to add common sense default specializations. Booleans should output checkboxes in forms and true/false in data renderers (instead of N/A which is done for nils now). Lists (sequences?) should render as dropdowns (or local suggest snippets) in forms. We also need to add some type aliases. For example 'one-of' types should render as radio buttons. How will we render sequences in data renderers? Some options include rendering each item in a comma separated list, having a link to datagrid, etc. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/36> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 5

[cl-weblocks-ticket] #61: hgj
by cl-weblocks 30 Aug '07

30 Aug '07

#61: hgj -----------------------+---------------------------------------------------- Reporter: anonymous | Owner: sakhmechet Type: defect | Status: new Priority: critical | Milestone: Component: weblocks | Version: Keywords: | -----------------------+---------------------------------------------------- hgj -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/61> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1