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

[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] #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] #17: Create a script that automates starting new weblocks projects
by cl-weblocks 07 Aug '07

07 Aug '07

#17: Create a script that automates starting new weblocks projects ---------------------------------+------------------------------------------ Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: high | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: script new projects | ---------------------------------+------------------------------------------ We should create a script that automates the process of starting a new weblocks project. It should create required fileset (asdf, 'init-user- session' template, copy over stylesheets, etc.) Usage of the script should be documented in the manual. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/17> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #10: When a widget is being modified, move focus to that control and change page title
by cl-weblocks 07 Aug '07

07 Aug '07

#10: When a widget is being modified, move focus to that control and change page title -----------------------------------------------------+---------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: accessibility focus widget change title | -----------------------------------------------------+---------------------- If a page has a number of widgets and a particular action causes some widget to change, that widget should receive focus (via JS for ajax, and via anchor otherwise) to ease the pain for users with screenreaders. Also, page title should change to a phrase that describes the current state of the widget in question. We need to think of what to do when multiple widgets change on the page. Perhaps the most likely solution is not to set focus/title in such cases, or set a title that describes state of all widgets. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/10> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #14: Standardize fonts accross browsers and OSes (perhaps via Yahoo Font CSS?)
by cl-weblocks 07 Aug '07

07 Aug '07

#14: Standardize fonts accross browsers and OSes (perhaps via Yahoo Font CSS?) --------------------------------------+------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: fonts yahoo css standard | --------------------------------------+------------------------------------- Currently default weblocks styles for fonts look different on various browsers and OSes. While there is no perfect solution, Yahoo provides a CSS that alleviates some of these problems. We should look into using it. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/14> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #40: Rename gridedit widget to a more fitting name
by cl-weblocks 07 Aug '07

07 Aug '07

#40: Rename gridedit widget to a more fitting name -----------------------------+---------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: rename gridedit | -----------------------------+---------------------------------------------- Gridedit doesn't seem to be a good name. We need to find a better name for gridedit widget. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/40> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #19: Extra tags div currently uses   contents which makes unstyled pages look unattractive
by cl-weblocks 06 Aug '07

06 Aug '07

#19: Extra tags div currently uses   contents which makes unstyled pages look unattractive ----------------------------+----------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: extra tags div | ----------------------------+----------------------------------------------- Weblocks places extra HTML tags in many places in order to allow for styling hooks. Currently the tags have   contents which make the page look unattractive when it's unstyled. Additionally this is incorrent - there should be no contents in those tags. A comment  should be sufficient. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/19> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #15: Fix friendly URLs and form actions in W3M
by cl-weblocks 06 Aug '07

06 Aug '07

#15: Fix friendly URLs and form actions in W3M -------------------------------------------+-------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: high | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: w3m friendly URL form actions | -------------------------------------------+-------------------------------- Currently form actions and friendly URLs appear to be broken in W3M. W3M seems to handle absolute links differently from other browsers which appears to be the root of the problem. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/15> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1