#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
#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
#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
#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
#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
#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
#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