- cl-weblocks-ticket@common-lisp.net - mailman3.common-lisp.net

[cl-weblocks-ticket] #49: Bad type declaration for (or bad initialization of) STATE slot in US-STATE
by cl-weblocks 01 Aug '07

01 Aug '07

#49: Bad type declaration for (or bad initialization of) STATE slot in US-STATE -----------------------+---------------------------------------------------- Reporter: anonymous | Owner: sakhmechet Type: defect | Status: new Priority: low | Milestone: Component: weblocks | Version: Keywords: | -----------------------+---------------------------------------------------- In the US-STATE class definition it is asserted that the slot STATE will only hold values of type STRING. There is a US-STATE method which passes NIL as a value to initialize STATE. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/49> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #46: Use css sprites to improve latency of default style
by cl-weblocks 01 Aug '07

01 Aug '07

#46: Use css sprites to improve latency of default style -----------------------------------------+---------------------------------- Reporter: anonymous | Owner: sakhmechet Type: defect | Status: new Priority: wishlist | Milestone: Component: weblocks | Version: Keywords: latency performance css png | -----------------------------------------+---------------------------------- The default page will load 33 pngs. A lot of these average at around 200- 300 bytes in size. Using CSS sprites can improve latency and the feel of a weblocks application a lot. I am measuring around 2s load time using firebug on the default weblocks- demo page. My guess is that CSS sprites can shave off around .5 seconds. How to reproduce: {{{ (require :weblocks-demo) (weblocks:start-server) }}} In firefox, install firebug. Enable firebug for your site. Do a "shift-reload" (holding shift down while doing a reload) to do a fresh load of the front-page. Inspect the "Net" tab in firebug to get a timeline. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/46> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[cl-weblocks-ticket] #47: combine js and css files to improve latency of default style
by cl-weblocks 01 Aug '07

01 Aug '07

#47: combine js and css files to improve latency of default style ---------------------------------------------------+------------------------ Reporter: anonymous | Owner: sakhmechet Type: enhancement | Status: new Priority: wishlist | Milestone: Component: weblocks | Version: Keywords: latency performance css javascript js | ---------------------------------------------------+------------------------ Latency of the default page could be improved a lot by combining the js- files into one file. The weblocks-demo default page loads 5 js files. These loads are serialized and it takes 1.2 seconds to load all of the JS. Making sure only necessary files are loaded (ticket #16) can be combined with this ticket by creating a cache of combinations of js-files that are required for a given page. The same applies to CSS. 11 CSS files are being used. Firefox loads them serially, spending roughly 0.7 seconds on this. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/47> 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

[cl-weblocks-ticket] #38: Highlight selected rows in datagrid
by cl-weblocks 30 Jul '07

30 Jul '07

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

1 0

[cl-weblocks-ticket] #31: Use widget names to render headings markup to improve accessibility
by cl-weblocks 30 Jul '07

30 Jul '07

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

1 1