From cl-weblocks-devel at common-lisp.net Sun Jul 29 05:39:52 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 05:39:52 -0000 Subject: [cl-weblocks-ticket] #1: Design paging functionality for datagrid widget. Message-ID: <088.94916f4f289419a9b2279326c43f848f@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 05:42:12 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 05:42:12 -0000 Subject: [cl-weblocks-ticket] Re: #1: Design paging functionality for datagrid widget. In-Reply-To: <088.94916f4f289419a9b2279326c43f848f@common-lisp.net> References: <088.94916f4f289419a9b2279326c43f848f@common-lisp.net> Message-ID: <097.80453e82bfe43e095af96c093666ecf7@common-lisp.net> #1: Design paging functionality for datagrid widget. --------------------------+------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Resolution: | Keywords: paging datagrid --------------------------+------------------------------------------------- Changes (by sakhmechet): * version: head => pre-0.1 -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 05:45:09 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 05:45:09 -0000 Subject: [cl-weblocks-ticket] #2: Allow viewing and editing gridedit items Message-ID: <088.e6d44b34565ed25bebcf25d5be33ab10@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 05:48:00 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 05:48:00 -0000 Subject: [cl-weblocks-ticket] #3: Create a modal control flow mechanism to eliminate adhoc state machines Message-ID: <088.ca9e587eb354047545fe4511ab94bd88@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 05:48:49 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 05:48:49 -0000 Subject: [cl-weblocks-ticket] #4: Create a modal dialog widget Message-ID: <088.b27a5226facc3835790bf3a3c75ab9f9@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 05:50:23 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 05:50:23 -0000 Subject: [cl-weblocks-ticket] #5: Gridedit item deletion confirmation Message-ID: <088.7c6ef4c824f339165b7478102096ec80@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 05:50:41 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 05:50:41 -0000 Subject: [cl-weblocks-ticket] Re: #4: Create a modal dialog widget In-Reply-To: <088.b27a5226facc3835790bf3a3c75ab9f9@common-lisp.net> References: <088.b27a5226facc3835790bf3a3c75ab9f9@common-lisp.net> Message-ID: <097.923441cbcadba8afdeac8361a2da2eeb@common-lisp.net> #4: Create a modal dialog widget --------------------------+------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Resolution: | Keywords: modal dialog widget --------------------------+------------------------------------------------- Changes (by sakhmechet): * priority: high => medium -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 05:50:57 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 05:50:57 -0000 Subject: [cl-weblocks-ticket] Re: #3: Create a modal control flow mechanism to eliminate adhoc state machines In-Reply-To: <088.ca9e587eb354047545fe4511ab94bd88@common-lisp.net> References: <088.ca9e587eb354047545fe4511ab94bd88@common-lisp.net> Message-ID: <097.22a81e8ec25c583266d7c994b5d514fa@common-lisp.net> #3: Create a modal control flow mechanism to eliminate adhoc state machines --------------------------+------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Resolution: | Keywords: continuations coroutines control flow state machine --------------------------+------------------------------------------------- Changes (by sakhmechet): * priority: high => medium -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 06:05:43 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 06:05:43 -0000 Subject: [cl-weblocks-ticket] #6: Handling and reporting errors Message-ID: <088.3547aa88cd5cf641ec25974f0e33c997@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 14:58:56 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 14:58:56 -0000 Subject: [cl-weblocks-ticket] #7: Widgets should be able to optionally expose state on the URL Message-ID: <088.65fb986a0f6497784a23d308db1676c9@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 15:01:52 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 15:01:52 -0000 Subject: [cl-weblocks-ticket] #8: Back button rules should be respected Message-ID: <088.eda8521fdd1ed65310632b95a0a83d8f@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 15:03:52 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 15:03:52 -0000 Subject: [cl-weblocks-ticket] Re: #7: Widgets should be able to optionally expose state on the URL In-Reply-To: <088.65fb986a0f6497784a23d308db1676c9@common-lisp.net> References: <088.65fb986a0f6497784a23d308db1676c9@common-lisp.net> Message-ID: <097.d374ddcdbe6094db1b0a933c34cbca32@common-lisp.net> #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 Resolution: | Keywords: navigation state URL --------------------------+------------------------------------------------- Comment (by sakhmechet): We should consider some form of 'persistent actions' to implement this. Perhaps similar to the way we implement resetting sessions in debug toolbar? -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 15:08:21 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 15:08:21 -0000 Subject: [cl-weblocks-ticket] #9: Consider redirecting the browser to hide all non user-friendly actions on non-ajax requests Message-ID: <088.18138f2e591ed31a511a70a192a3299b@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 15:12:13 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 15:12:13 -0000 Subject: [cl-weblocks-ticket] #10: When a widget is being modified, move focus to that control and change page title Message-ID: <088.0aa30ac0c0d6bfba11e6a4c6a90d3b18@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 15:17:56 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 15:17:56 -0000 Subject: [cl-weblocks-ticket] #11: Make the path to files that needs to be accessible via the webserver configurable Message-ID: <088.2ca323489875366bc1c2cd59cb949156@common-lisp.net> #11: Make the path to files that needs to be accessible via the webserver configurable ---------------------------------+------------------------------------------ Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: critical | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: hardcoded directory | ---------------------------------+------------------------------------------ Currently the path to public files (stylesheets, !JavaScript code, images, etc.) is hard coded. This gives a bad impression when framework is first obtained and needs to be fixed. Ideally we should standardize on how ASDF sets the current directory and determine the path automatically. We should also make this configurable so users can set this directory to their own liking. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sun Jul 29 15:20:54 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sun, 29 Jul 2007 15:20:54 -0000 Subject: [cl-weblocks-ticket] #12: Make stylesheet and javascript requirements dynamic Message-ID: <088.d823adf93bf23a12712a6667979eddbe@common-lisp.net> #12: Make stylesheet and javascript requirements dynamic ---------------------------------------------------------+------------------ Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: high | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: harcoded stylesheet javascript requirements | ---------------------------------------------------------+------------------ Currently stylesheet and javascript requirements are hardcoded in the 'with-page' function. The only way for users to override this is to redefine the function. We need to make these requirements configurable, and widgets should be able to register files that they require. Additionally, some form of dependecy graph or priority system needs to be implemented (order matters since some stylesheets override others). -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 03:40:13 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 03:40:13 -0000 Subject: [cl-weblocks-ticket] #13: Consider redoing flash and dataform widgets with coroutine control flow functionality Message-ID: <088.7a678a098bd6919e42c4ede8a29ef150@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 03:42:34 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 03:42:34 -0000 Subject: [cl-weblocks-ticket] #14: Standardize fonts accross browsers and OSes (perhaps via Yahoo Font CSS?) Message-ID: <088.ab029768f0aac1777a66e1a9bf4c1cce@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 03:44:10 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 03:44:10 -0000 Subject: [cl-weblocks-ticket] #15: Fix friendly URLs and form actions in W3M Message-ID: <088.5d89894eb12e40f203bcd440d623d152@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 03:45:56 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 03:45:56 -0000 Subject: [cl-weblocks-ticket] #16: Make page titles dynamic (perhaps based on the navigation widget) Message-ID: <088.56998c1b3ba84eb12821a14fe9d4522e@common-lisp.net> #16: Make page titles dynamic (perhaps based on the navigation widget) -----------------------------------+---------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: page title navigation | -----------------------------------+---------------------------------------- Currently page title is hardcoded in the 'with-page' function. We should make page titles dynamic. The should probably come from the navigation widget. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 03:48:38 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 03:48:38 -0000 Subject: [cl-weblocks-ticket] #17: Create a script that automates starting new weblocks projects Message-ID: <088.247847085f0809ab0e03a1e6c438ffb5@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 03:51:24 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 03:51:24 -0000 Subject: [cl-weblocks-ticket] #18: Create a default page for weblocks server Message-ID: <088.730c8668b024d752e5ab11a1e53c0bd9@common-lisp.net> #18: Create a default page for weblocks server --------------------------+------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: high | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: default page | --------------------------+------------------------------------------------- Currently when weblocks server starts up and no application is defined weblocks displays an Error 500. We should create a default welcome page with basic links and instructions on how to proceed. Manual should be updated accordingly. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 03:54:29 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 03:54:29 -0000 Subject: [cl-weblocks-ticket] #19: Extra tags div currently uses   contents which makes unstyled pages look unattractive Message-ID: <088.65da7a6357f201bdc6414f55307f31fc@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 03:58:30 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 03:58:30 -0000 Subject: [cl-weblocks-ticket] #20: Offer user an option to turn off AJAX and other effects when unsupported browsers are detected Message-ID: <088.3a3be73dcf06167e576a2faedeb5a230@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:06:43 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:06:43 -0000 Subject: [cl-weblocks-ticket] #21: Allow multiple search tokens in grid searchbar Message-ID: <088.f69315c9345336451b24a7180b68b922@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:09:20 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:09:20 -0000 Subject: [cl-weblocks-ticket] #22: Consider lazy session initialization Message-ID: <088.58eba43c5d4085c82562182251ab44ec@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:12:16 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:12:16 -0000 Subject: [cl-weblocks-ticket] #23: Create renderers for lists of items Message-ID: <088.e2f493acb58000ce310e75cc1864d4cf@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:13:15 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:13:15 -0000 Subject: [cl-weblocks-ticket] #24: 'Blocks' should be renamed to 'snippets' Message-ID: <088.a15661dd4ae11ab6db367fc0a96d8106@common-lisp.net> #24: 'Blocks' should be renamed to 'snippets' ------------------------------------+--------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: blocks snippets rename | ------------------------------------+--------------------------------------- A 'block' is a bad name. A 'snippet' is much better. We should rename blocks to snippets. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:17:42 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:17:42 -0000 Subject: [cl-weblocks-ticket] #25: Refactor flash widget styling Message-ID: <088.54d91eb8fe8ae7f75e00b28061866f9e@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:19:31 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:19:31 -0000 Subject: [cl-weblocks-ticket] #26: Don't hide validation error summary for long forms Message-ID: <088.d2c1e7fbf7626099ce6fef6b97bfcecb@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:21:31 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:21:31 -0000 Subject: [cl-weblocks-ticket] #27: Customize widget printing to include their names (to ease debugging) Message-ID: <088.fb842ac5696407c71df8934d1c032021@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:23:24 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:23:24 -0000 Subject: [cl-weblocks-ticket] #28: Rename 'datagrid' widget to 'grid' Message-ID: <088.32d2d7a5d9e812c45fcc11c5cd2ee098@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:25:55 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:25:55 -0000 Subject: [cl-weblocks-ticket] #29: Refactor form and input markup into snippets Message-ID: <088.30f79aa2f33ae225af82694081645556@common-lisp.net> #29: Refactor form and input markup into snippets ------------------------------------------+--------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: refactor form markup snippet | ------------------------------------------+--------------------------------- Currently various widgets output form and input markup manually. We should refactor this functionality into snippets and convert existing widgets to use the snippets. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:27:21 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:27:21 -0000 Subject: [cl-weblocks-ticket] #30: Preload 'ajax loading' image Message-ID: <088.48212580f5cc9f07cae840c26aec4f35@common-lisp.net> #30: Preload 'ajax loading' image ----------------------------------------+----------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Keywords: ajax loading image preload | ----------------------------------------+----------------------------------- During the first AJAX request the image for 'loading' is being loaded by the browser which gives the user a mistaken impression. The 'ajax loading' image should be preloaded. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:29:24 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:29:24 -0000 Subject: [cl-weblocks-ticket] #31: Use widget names to render headings markup to improve accessibility Message-ID: <088.1b00c91316d9cb827cda9fad7609a4ed@common-lisp.net> #31: Use widget names to render headings markup to improve accessibility -------------------------------------------+-------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Keywords: headings accessibility markup | -------------------------------------------+-------------------------------- We should take advantage of widget names whenever they are provided to render headings markup that should improve accessibility. Lack of headings makes navigation very hard for users with screen readers. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:30:29 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:30:29 -0000 Subject: [cl-weblocks-ticket] Re: #31: Use widget names to render headings markup to improve accessibility In-Reply-To: <088.1b00c91316d9cb827cda9fad7609a4ed@common-lisp.net> References: <088.1b00c91316d9cb827cda9fad7609a4ed@common-lisp.net> Message-ID: <097.06a1c834ea6781352a96ed223922f204@common-lisp.net> #31: Use widget names to render headings markup to improve accessibility --------------------------+------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Resolution: | Keywords: headings accessibility markup --------------------------+------------------------------------------------- Comment (by sakhmechet): Additionally we should concentrate on properly conveying page structure by rendering an appropriate heading structure. Widget hierarchy can help conveying appropriate information to the user. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:36:05 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:36:05 -0000 Subject: [cl-weblocks-ticket] #32: Provide additional navigation aids to improve accessibility (using ) Message-ID: <088.a53553710dd8aebe087d6145ef7c4de4@common-lisp.net> #32: Provide additional navigation aids to improve accessibility (using ) --------------------------------------------------------------+------------- 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 ) -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:37:56 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:37:56 -0000 Subject: [cl-weblocks-ticket] #33: Refactor, document, and unit test 'handle-client-request' Message-ID: <088.a2b5cb918aa7dcba13512ac81c32d4d4@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:40:16 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:40:16 -0000 Subject: [cl-weblocks-ticket] #34: Sanitize input to prevent cross-site scripting and SQL injection Message-ID: <088.505ddbfadceb958df163f672c9368dd6@common-lisp.net> #34: Sanitize input to prevent cross-site scripting and SQL injection ---------------------------------------------------------+------------------ Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: high | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: cross-site scripting SQL injection sanitize | ---------------------------------------------------------+------------------ We should sanitize form input to prevent cross-site scripting and SQL injection. Sanitation should ideally be done in a centralized place (in particular, request-object-mapping). -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:43:34 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:43:34 -0000 Subject: [cl-weblocks-ticket] #35: Take advantage of ASDF operations to test, document, and release packages Message-ID: <088.a1299193434bf0ea4dc13e866d65c990@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 04:50:40 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 04:50:40 -0000 Subject: [cl-weblocks-ticket] Re: #8: Back button rules should be respected In-Reply-To: <088.eda8521fdd1ed65310632b95a0a83d8f@common-lisp.net> References: <088.eda8521fdd1ed65310632b95a0a83d8f@common-lisp.net> Message-ID: <097.8b0a01a169542a180cc4d01f6467d02b@common-lisp.net> #8: Back button rules should be respected -------------------------+-------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: low | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Resolution: | Keywords: back button history -------------------------+-------------------------------------------------- Changes (by sakhmechet): * milestone: 0.1 => 0.2 -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 17:09:13 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 17:09:13 -0000 Subject: [cl-weblocks-ticket] #36: Modify renderers to allow specialization on slot types Message-ID: <088.aec19e707fbe11b3f56168004f5fea7b@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 17:18:45 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 17:18:45 -0000 Subject: [cl-weblocks-ticket] #37: Handle CLOS object references ('foreign keys') in form renderers Message-ID: <088.6a4164a15c4fd49bd5832869e8900f5d@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 17:22:39 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 17:22:39 -0000 Subject: [cl-weblocks-ticket] #38: Highlight selected rows in datagrid Message-ID: <088.5fdd4a6d7861bf3607a6a8fce905f325@common-lisp.net> #38: Highlight selected rows in datagrid ----------------------------------------------+----------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Keywords: highlight row datagrid selection | ----------------------------------------------+----------------------------- In datagrid, when a row/item is selected we should attempt to highlight the row. We can do this via !JavaScript, or an AJAX callback to the server to mark the item as selected. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 17:25:14 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 17:25:14 -0000 Subject: [cl-weblocks-ticket] #39: Allow item selection in datagrid beyond current page Message-ID: <088.cdd8dfd333d6852bd1b3c1ac3e88b914@common-lisp.net> #39: Allow item selection in datagrid beyond current page --------------------------------------------+------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Keywords: datagrid selection beyond page | --------------------------------------------+------------------------------- Currently if the user makes a search for some items, selects an item, and modifies the search, the selected item disappears. Similarly, when 'all' is clicked there is no way to select all items beyond the current page (like in Gmail). We should design and add functionality to make this possible (designing a UI for this that isn't confusing is very tricky, so pushed to 0.2) -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 17:26:44 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 17:26:44 -0000 Subject: [cl-weblocks-ticket] #40: Rename gridedit widget to a more fitting name Message-ID: <088.c553595f21172622adf594c9a498bc78@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 17:41:39 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 17:41:39 -0000 Subject: [cl-weblocks-ticket] #41: Design authentication and permissions mechanism Message-ID: <088.100afa79908ff3000dc8ba39ec5dfae8@common-lisp.net> #41: Design authentication and permissions mechanism --------------------------------------------------+------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: medium | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Keywords: authentication permissions mechanism | --------------------------------------------------+------------------------- Currently Weblocks provides no mechanism for authentication and permissions. We should devise such a mechanism, make it reasonably flexible, and integrate it with the rest of the framework. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 17:42:32 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 17:42:32 -0000 Subject: [cl-weblocks-ticket] Re: #41: Design authentication and permissions mechanism In-Reply-To: <088.100afa79908ff3000dc8ba39ec5dfae8@common-lisp.net> References: <088.100afa79908ff3000dc8ba39ec5dfae8@common-lisp.net> Message-ID: <097.74149c5f4b1888c6d8957c95dd8df192@common-lisp.net> #41: Design authentication and permissions mechanism -------------------------+-------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: medium | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Resolution: | Keywords: authentication permissions mechanism -------------------------+-------------------------------------------------- Comment (by sakhmechet): In particular, access to various parts of the navigation, particular widgets, and (especially) actions should be managed by the permission system. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 17:44:38 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 17:44:38 -0000 Subject: [cl-weblocks-ticket] #42: Sorting and regex filtering should be refactored out of datagrid Message-ID: <088.fef3fd9be570ae2d804df0fe1a2fac94@common-lisp.net> #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: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 17:49:27 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 17:49:27 -0000 Subject: [cl-weblocks-ticket] #43: Consider resetting state of widgets when moving accross navigation Message-ID: <088.25c231ab548f04287a0fbee1c6c6bcea@common-lisp.net> #43: Consider resetting state of widgets when moving accross navigation -------------------------------------------+-------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Keywords: reset widget state navigation | -------------------------------------------+-------------------------------- Currently if a state of a widget's UI is changed on one page, then navigation state is changed to another page, and moved back to the original page, the UI of the widget will not be reset. This may or may not be counter-intuitive to the user. We should consider resetting UI state of widgets when moving accross navigation. This may be related to ticket #22. In particular, if we choose to garbage collect widgets when moving accross navigation, we'll have to reinstantiate widgets, thereby resetting them. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 18:03:06 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 18:03:06 -0000 Subject: [cl-weblocks-ticket] Re: #22: Consider lazy session initialization In-Reply-To: <088.58eba43c5d4085c82562182251ab44ec@common-lisp.net> References: <088.58eba43c5d4085c82562182251ab44ec@common-lisp.net> Message-ID: <097.6fbe1ad2ca1071240ca60b79373cb432@common-lisp.net> #22: Consider lazy session initialization --------------------------+------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Resolution: | Keywords: lazy initialization session --------------------------+------------------------------------------------- Comment (by sakhmechet): Note, this may be related to ticket #43. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 18:08:23 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 18:08:23 -0000 Subject: [cl-weblocks-ticket] Re: #7: Widgets should be able to optionally expose state on the URL In-Reply-To: <088.65fb986a0f6497784a23d308db1676c9@common-lisp.net> References: <088.65fb986a0f6497784a23d308db1676c9@common-lisp.net> Message-ID: <097.1709a99185b96a74759b5895ef5ebd6c@common-lisp.net> #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 Resolution: | Keywords: navigation state URL --------------------------+------------------------------------------------- Comment (by sakhmechet): This may require making the navigation widget more advanced. In particular, we may need to allow "hidden" panes that only exist to service the URLs but aren't rendered. Additionally we may need to add "dynamic" panes that are created on the fly based on the URL according to some rules. We may also need to support multiple navigation widgets in one composite. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 18:26:59 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 18:26:59 -0000 Subject: [cl-weblocks-ticket] Re: #37: Handle CLOS object references ('foreign keys') in form renderers In-Reply-To: <088.6a4164a15c4fd49bd5832869e8900f5d@common-lisp.net> References: <088.6a4164a15c4fd49bd5832869e8900f5d@common-lisp.net> Message-ID: <097.4d730b2d46ec43029d2981a80df91287@common-lisp.net> #37: Handle CLOS object references ('foreign keys') in form renderers --------------------------+------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Resolution: | Keywords: renderers clos foreign key reference --------------------------+------------------------------------------------- Changes (by sakhmechet): * priority: critical => medium -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 18:27:16 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 18:27:16 -0000 Subject: [cl-weblocks-ticket] Re: #20: Offer user an option to turn off AJAX and other effects when unsupported browsers are detected In-Reply-To: <088.3a3be73dcf06167e576a2faedeb5a230@common-lisp.net> References: <088.3a3be73dcf06167e576a2faedeb5a230@common-lisp.net> Message-ID: <097.0e1d3efda95828e54e35f6a4473b03a7@common-lisp.net> #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: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Resolution: | Keywords: simple HTML unsupported browsers degrade option --------------------------+------------------------------------------------- Changes (by sakhmechet): * priority: critical => low -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jul 30 19:54:53 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 30 Jul 2007 19:54:53 -0000 Subject: [cl-weblocks-ticket] Re: #11: Make the path to files that needs to be accessible via the webserver configurable In-Reply-To: <088.2ca323489875366bc1c2cd59cb949156@common-lisp.net> References: <088.2ca323489875366bc1c2cd59cb949156@common-lisp.net> Message-ID: <097.41845ab79099c59408d058b883f89aa4@common-lisp.net> #11: Make the path to files that needs to be accessible via the webserver configurable -------------------------+-------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: closed Priority: critical | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Resolution: fixed | Keywords: hardcoded directory -------------------------+-------------------------------------------------- Changes (by sakhmechet): * resolution: => fixed * status: new => closed Comment: Fixed. The path is no longer hardcoded and parameter *public-files-path* can be modified at runtime so that applications can set their own path. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Tue Jul 31 03:11:26 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Tue, 31 Jul 2007 03:11:26 -0000 Subject: [cl-weblocks-ticket] Re: #18: Create a default page for weblocks server In-Reply-To: <088.730c8668b024d752e5ab11a1e53c0bd9@common-lisp.net> References: <088.730c8668b024d752e5ab11a1e53c0bd9@common-lisp.net> Message-ID: <097.0f2282fcc2e8475602fbb86c1603b2da@common-lisp.net> #18: Create a default page for weblocks server -------------------------+-------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: closed Priority: high | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Resolution: fixed | Keywords: default page -------------------------+-------------------------------------------------- Changes (by sakhmechet): * resolution: => fixed * status: new => closed Comment: Fixed. Weblocks now provides a default application that has a simple welcome page with links to documentation. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Tue Jul 31 03:30:27 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Tue, 31 Jul 2007 03:30:27 -0000 Subject: [cl-weblocks-ticket] Re: #36: Modify renderers to allow specialization on slot types In-Reply-To: <088.aec19e707fbe11b3f56168004f5fea7b@common-lisp.net> References: <088.aec19e707fbe11b3f56168004f5fea7b@common-lisp.net> Message-ID: <097.88fab121f4fd129bb74cbd61812d18dc@common-lisp.net> #36: Modify renderers to allow specialization on slot types --------------------------+------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: medium | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Resolution: | Keywords: renderers slots types dropdown custom --------------------------+------------------------------------------------- Changes (by sakhmechet): * priority: high => medium -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Tue Jul 31 03:30:59 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Tue, 31 Jul 2007 03:30:59 -0000 Subject: [cl-weblocks-ticket] Re: #34: Sanitize input to prevent cross-site scripting and SQL injection In-Reply-To: <088.505ddbfadceb958df163f672c9368dd6@common-lisp.net> References: <088.505ddbfadceb958df163f672c9368dd6@common-lisp.net> Message-ID: <097.b40904b8c3b34aaf9683d0a68ee317f1@common-lisp.net> #34: Sanitize input to prevent cross-site scripting and SQL injection -------------------------+-------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: medium | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Resolution: | Keywords: cross-site scripting SQL injection sanitize -------------------------+-------------------------------------------------- Changes (by sakhmechet): * priority: high => medium -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Tue Jul 31 03:31:47 2007 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Tue, 31 Jul 2007 03:31:47 -0000 Subject: [cl-weblocks-ticket] Re: #16: Make page titles dynamic (perhaps based on the navigation widget) In-Reply-To: <088.56998c1b3ba84eb12821a14fe9d4522e@common-lisp.net> References: <088.56998c1b3ba84eb12821a14fe9d4522e@common-lisp.net> Message-ID: <097.92bc54a6dc5b5b32e48cd3019f7f766f@common-lisp.net> #16: Make page titles dynamic (perhaps based on the navigation widget) --------------------------+------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: high | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Resolution: | Keywords: page title navigation --------------------------+------------------------------------------------- Changes (by sakhmechet): * priority: medium => high -- Ticket URL: cl-weblocks cl-weblocks