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

[cl-weblocks-ticket] #29: Refactor form and input markup into snippets
by cl-weblocks 06 Aug '07

06 Aug '07

#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: <http://trac.common-lisp.net/cl-weblocks/ticket/29> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 2

[cl-weblocks-ticket] #24: 'Blocks' should be renamed to 'snippets'
by cl-weblocks 06 Aug '07

06 Aug '07

#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: <http://trac.common-lisp.net/cl-weblocks/ticket/24> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #34: Sanitize input to prevent cross-site scripting and SQL injection
by cl-weblocks 03 Aug '07

03 Aug '07

#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: <http://trac.common-lisp.net/cl-weblocks/ticket/34> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 3

[cl-weblocks-ticket] #16: Make page titles dynamic (perhaps based on the navigation widget)
by cl-weblocks 03 Aug '07

03 Aug '07

#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: <http://trac.common-lisp.net/cl-weblocks/ticket/16> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 2

[cl-weblocks-ticket] #12: Make stylesheet and javascript requirements dynamic
by cl-weblocks 02 Aug '07

02 Aug '07

#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: <http://trac.common-lisp.net/cl-weblocks/ticket/12> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #18: Create a default page for weblocks server
by cl-weblocks 31 Jul '07

31 Jul '07

#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: <http://trac.common-lisp.net/cl-weblocks/ticket/18> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #11: Make the path to files that needs to be accessible via the webserver configurable
by cl-weblocks 30 Jul '07

30 Jul '07

#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: <http://trac.common-lisp.net/cl-weblocks/ticket/11> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #43: Consider resetting state of widgets when moving accross navigation
by cl-weblocks 30 Jul '07

30 Jul '07

#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: <http://trac.common-lisp.net/cl-weblocks/ticket/43> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 0

[cl-weblocks-ticket] #41: Design authentication and permissions mechanism
by cl-weblocks 30 Jul '07

30 Jul '07

#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: <http://trac.common-lisp.net/cl-weblocks/ticket/41> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #39: Allow item selection in datagrid beyond current page
by cl-weblocks 30 Jul '07

30 Jul '07

#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: <http://trac.common-lisp.net/cl-weblocks/ticket/39> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 0