cl-weblocks-ticket August 2007

cl-weblocks-ticket@common-lisp.net

1 participants
53 discussions

[cl-weblocks-ticket] #52: Refreshing POST requests causes gridedit item addition related issues
by cl-weblocks 27 Dec '07

27 Dec '07

#52: Refreshing POST requests causes gridedit item addition related issues -----------------------------------+---------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: defect | Status: new Priority: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: refresh POST gridedit | -----------------------------------+---------------------------------------- Refreshing a page when !JavaScript is disabled after item has been added to gridedit causes the same instace of an item to be added to the data twice. If one item of the added ones is selected and delete is pressed, all items added during the refresh will be deleted. 'gridedit-add-item' should be modified not to add two instances of the same object. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/52> cl-weblocks <http://common-lisp.net/project/cl-weblocks> cl-weblocks

1 1

[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] #54: Integrate weblocks-demo into weblocks source tree under examples directory
by cl-weblocks 20 Nov '07

20 Nov '07

#54: Integrate weblocks-demo into weblocks source tree under examples directory ---------------------------+------------------------------------------------ Reporter: anonymous | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: 0.1 Component: weblocks | Version: pre-0.1 Keywords: examples demo | ---------------------------+------------------------------------------------ Weblocks-demo should be integrated into weblocks under /examples directory. We should develop ways to unit test the application code, not just component code, and ensure that unit tests of future example projects run as part of weblocks-test suite. This should probably be done after ticket #35. -- Ticket URL: <http://trac.common-lisp.net/cl-weblocks/ticket/54> 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 07 Nov '07

07 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

cl-weblocks-ticket August 2007