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

[cl-weblocks-ticket] #22: Consider lazy session initialization
by cl-weblocks 16 Jun '08

16 Jun '08

#22: Consider lazy session initialization -----------------------------------------+---------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Keywords: lazy initialization session | -----------------------------------------+---------------------------------- Currently when a session is initialized in 'init-user-session', all widgets are instantiated at once. We should make this process lazy and instantiate widgets as necessary (perhaps via hooks from the navigation widget?) Additionally, we should consider freeing hidden widgets for garbage collecting. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/22> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 5

[cl-weblocks-ticket] #6: Handling and reporting errors
by cl-weblocks 29 Apr '08

29 Apr '08

#6: Handling and reporting errors ------------------------------------+--------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: error handling failure | ------------------------------------+--------------------------------------- Currently when errors occur on AJAX requests (in both debug and release) there is a simple !JavaScript popup. When errors occur on regular requests (in release) there is a plain old error 500 page. We need to show debug information on AJAX requests in debug mode. Should we modify the popup (perhaps redirect to error page) when an error occurs on AJAX requests in release? For regular requests we need a prettier error page. We also need special handling of session timeout errors. When a session times out we should probably refresh the page and show a popup/flash saying a new session has been created. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/6> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 3

[cl-weblocks-ticket] #21: Allow multiple search tokens in grid searchbar
by cl-weblocks 29 Apr '08

29 Apr '08

#21: Allow multiple search tokens in grid searchbar --------------------------------------------+------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Keywords: grid searchbar tokens multiple | --------------------------------------------+------------------------------- Currently it's possible to search for only one token in the searchbar. The search mechanism should be made more intelligent. It should be possible to separate tokens with delimiters, use quotes to turn off delimiting tokens, etc. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/21> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #28: Rename 'datagrid' widget to 'grid'
by cl-weblocks 18 Apr '08

18 Apr '08

#28: Rename 'datagrid' widget to 'grid' ----------------------------------+----------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: rename datagrid grid | ----------------------------------+----------------------------------------- There is no reason to call datagrid widget 'datagrid'. 'Grid' is a much better name. We should rename the widget. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/28> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 3

[cl-weblocks-ticket] #23: Create renderers for lists of items
by cl-weblocks 18 Apr '08

18 Apr '08

#23: Create renderers for lists of items --------------------------------------------+------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Keywords: renderers snippets lists items | --------------------------------------------+------------------------------- We should create renderers (or snippets?) to render lists of items (ordered, unordered, etc.) as this is a fairly common operation. We should consider rewriting current widgets that use lists to take advantage of this functionality. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/23> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 2

[cl-weblocks-ticket] #42: Sorting and regex filtering should be refactored out of datagrid
by cl-weblocks 06 Feb '08

06 Feb '08

#42: Sorting and regex filtering should be refactored out of datagrid -----------------------------------------------------------------+---------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Keywords: sorting filtering searching regex refactor datagrid | -----------------------------------------------------------------+---------- Currently sorting and regex filtering/searching mechanisms are specific to the datagrid. It seems like these mechanisms could be used in other widgets. We should refactor these components and make them generic for use by other widgets. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/42> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 2

[cl-weblocks-ticket] #8: Back button rules should be respected
by cl-weblocks 27 Dec '07

27 Dec '07

#8: Back button rules should be respected ---------------------------------+------------------------------------------ Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: back button history | ---------------------------------+------------------------------------------ We should consider improving the consequences of hitting the back button. Currently only navigation control actions are recorded in the browser's history. We can get around this by updating AJAX actions with an anchor at the end of the URL and support proper back button this way. Is this the right thing to do? -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/8> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 2

[cl-weblocks-ticket] #7: Widgets should be able to optionally expose state on the URL
by cl-weblocks 27 Dec '07

27 Dec '07

#7: Widgets should be able to optionally expose state on the URL ----------------------------------+----------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: navigation state URL | ----------------------------------+----------------------------------------- Currently the only widget that can expose state on the URL is Navigation. Widgets like Grid cannot expose state. This makes the user run into very annoying issues similar to the ones common to Expedia/Travelocity - someone sends a link to a hotel to a friend, but the friend sees a completely different page. As an example, grid controls should be able to optionally expose which column they're sorted on. People should be able to navigate to a product page by product name/id on the URL. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/7> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 5

[cl-weblocks-ticket] #20: Offer user an option to turn off AJAX and other effects when unsupported browsers are detected
by cl-weblocks 27 Dec '07

27 Dec '07

#20: Offer user an option to turn off AJAX and other effects when unsupported browsers are detected -------------------------------------------------------------+-------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: critical | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: simple HTML unsupported browsers degrade option | -------------------------------------------------------------+-------------- When weblocks detects an unsupported browser it should cooperate with the application to give the user an option to turn off advanced effects or to proceed at their own risk. We could do this via a flash widget or a modal dialog widget. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/20> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 2

[cl-weblocks-ticket] #33: Refactor, document, and unit test 'handle-client-request'
by cl-weblocks 27 Dec '07

27 Dec '07

#33: Refactor, document, and unit test 'handle-client-request' ----------------------------------------------+----------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: medium | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Keywords: refactor 'handle-client-request' | ----------------------------------------------+----------------------------- Currently 'handle-client-request' is a complex function that's somewhat poorly tested and documented. We should refactor it into more manageable pieces, provide better tests and document its behavior more therally. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/33> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 8

[cl-weblocks-ticket] #35: Take advantage of ASDF operations to test, document, and release packages
by cl-weblocks 12 Dec '07

12 Dec '07

#35: Take advantage of ASDF operations to test, document, and release packages -----------------------------------------------------------+---------------- Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: asdf operations test release document scripts | -----------------------------------------------------------+---------------- Currently weblocks related scripts are scattered and not standard. ASDF provides standard facilities (via operations) to perform scripted tasks. We should convert our scripts to hook into ASDF ops. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/35> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #13: Consider redoing flash and dataform widgets with coroutine control flow functionality
by cl-weblocks 19 Nov '07

19 Nov '07

#13: Consider redoing flash and dataform widgets with coroutine control flow functionality ----------------------------------------+----------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: modal flow control widgets | ----------------------------------------+----------------------------------- Once a modal control flow mechanism is in place (#3), we should consider removing ad hoc state machines from current widgets and implementing them via the new mechanism. Flash and dataform seem like a good place to start. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/13> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #4: Create a modal dialog widget
by cl-weblocks 19 Nov '07

19 Nov '07

#4: Create a modal dialog widget ---------------------------------+------------------------------------------ Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: high | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: modal dialog widget | ---------------------------------+------------------------------------------ Create a widget that would act as a modal dialog. This widget can be used for confirmations, data input, etc. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/4> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 4

[cl-weblocks-ticket] #3: Create a modal control flow mechanism to eliminate adhoc state machines
by cl-weblocks 07 Nov '07

07 Nov '07

#3: Create a modal control flow mechanism to eliminate adhoc state machines -----------------------------------------------------------------+---------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: high | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: continuations coroutines control flow state machine | -----------------------------------------------------------------+---------- Currently control flow is managed by creating adhoc state machines throughout widgets. A system needs to be designed that allows managing control flow more effectively. Coroutines seem like a perfect candidate for the job (as an alternative for full-blown continuations). -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/3> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 2

[cl-weblocks-ticket] #9: Consider redirecting the browser to hide all non user-friendly actions on non-ajax requests
by cl-weblocks 06 Nov '07

06 Nov '07

#9: Consider redirecting the browser to hide all non user-friendly actions on non-ajax requests ---------------------------------------+------------------------------------ Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: non-AJAX request redirect | ---------------------------------------+------------------------------------ When JavaScript is turned off on the client and AJAX isn't available, all actions end up showing on the URL. This breaks expected behavior - users can't bookmark URLs, send them to friends, etc. We should consider sending a redirect request to the browser on every action in case AJAX is turned off to clean up the URL. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/9> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 2

[cl-weblocks-ticket] #25: Refactor flash widget styling
by cl-weblocks 24 Oct '07

24 Oct '07

#25: Refactor flash widget styling ---------------------------+------------------------------------------------ Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: flash styling | ---------------------------+------------------------------------------------ Currently the default style for the flash widget is set to the one that can generally be used on the "main" page. The style that will probably be more commonly used is specialized to datagrid. We should refactor stylesheets to make the more common style regular and the less common style specialized. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/25> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 2

[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 09 Oct '07

09 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] #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 12 Sep '07

12 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 07 Sep '07

07 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