From cl-weblocks-devel at common-lisp.net Thu Jun 12 18:02:30 2008 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Thu, 12 Jun 2008 18:02:30 -0000 Subject: [cl-weblocks-ticket] #88: Enhance SATISFIES Message-ID: <088.540693a6c88e7800c19862803968ce83@common-lisp.net> #88: Enhance SATISFIES ---------------------------------------------+------------------------------ Reporter: lpolzer | Owner: sakhmechet Type: enhancement | Status: new Priority: wishlist | Milestone: Component: weblocks | Version: Keywords: satisfies,errors,error messages | ---------------------------------------------+------------------------------ Use the return value of SATISFIES for a more detailed error message. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Thu Jun 12 18:03:56 2008 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Thu, 12 Jun 2008 18:03:56 -0000 Subject: [cl-weblocks-ticket] Re: #71: Implement a system for giving random hints/tip-of-the-day message to user In-Reply-To: <088.34d9953410df13ba67b7f51faac5a713@common-lisp.net> References: <088.34d9953410df13ba67b7f51faac5a713@common-lisp.net> Message-ID: <097.69dccadc104299a733bf0f222b0d4908@common-lisp.net> #71: Implement a system for giving random hints/tip-of-the-day message to user --------------------------+------------------------------------------------- Reporter: sakhmechet | Owner: sakhmechet Type: enhancement | Status: new Priority: wishlist | Milestone: 0.2 Component: weblocks | Version: pre-0.1 Resolution: | Keywords: hint tip system --------------------------+------------------------------------------------- Changes (by lpolzer): * priority: low => wishlist * type: defect => enhancement -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Thu Jun 12 18:07:34 2008 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Thu, 12 Jun 2008 18:07:34 -0000 Subject: [cl-weblocks-ticket] #89: Add MIN-LENGTH to PASSWORD parser; enforce MAX-LENGTH on the server side Message-ID: <088.98a7b552e4539fbdb0c61260d9bf4b2d@common-lisp.net> #89: Add MIN-LENGTH to PASSWORD parser; enforce MAX-LENGTH on the server side --------------------------------------------+------------------------------- Reporter: lpolzer | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: Component: weblocks | Version: Keywords: password,min-length,max-length | --------------------------------------------+------------------------------- -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Thu Jun 12 19:20:59 2008 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Thu, 12 Jun 2008 19:20:59 -0000 Subject: [cl-weblocks-ticket] Re: #89: Add MIN-LENGTH to PASSWORD parser; enforce MAX-LENGTH on the server side In-Reply-To: <088.98a7b552e4539fbdb0c61260d9bf4b2d@common-lisp.net> References: <088.98a7b552e4539fbdb0c61260d9bf4b2d@common-lisp.net> Message-ID: <097.1a2ffec9cf6988edc4f2affe5ad31076@common-lisp.net> #89: Add MIN-LENGTH to PASSWORD parser; enforce MAX-LENGTH on the server side --------------------------+------------------------------------------------- Reporter: lpolzer | Owner: sakhmechet Type: enhancement | Status: new Priority: low | Milestone: Component: weblocks | Version: Resolution: | Keywords: password,min-length,max-length --------------------------+------------------------------------------------- Comment (by sakhmechet): min-length should probably be specific to input-presentation/text-parser, not just passwords. Also, max-length should be enforced for all input fields as well, as it isn't specific to passwords. Once min-length is implemented for input fields, it's probably a good idea to set password min-length to some reasonable configurable default (*password-min-length*). It looks like max-length is appropriate for both presentations and parsers, a situation I didn't think of. They should probably be derived from a common subclass then, unless we want to specify max-length twice (once in the parser, and once in the presentation). -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Sat Jun 14 11:30:41 2008 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Sat, 14 Jun 2008 11:30:41 -0000 Subject: [cl-weblocks-ticket] #90: Formview should accept SATISFIES parameter Message-ID: <088.544b51badd3b794bc428a33f40c0e2b6@common-lisp.net> #90: Formview should accept SATISFIES parameter --------------------------------+------------------------------------------- Reporter: lpolzer | Owner: sakhmechet Type: enhancement | Status: new Priority: wishlist | Milestone: Component: weblocks | Version: Keywords: formview,satisfies | --------------------------------+------------------------------------------- Useful for checking relationships between fields of the form. -- Ticket URL: cl-weblocks cl-weblocks From cl-weblocks-devel at common-lisp.net Mon Jun 16 13:35:46 2008 From: cl-weblocks-devel at common-lisp.net (cl-weblocks) Date: Mon, 16 Jun 2008 13:35:46 -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.65b02dd651b6ebb361514874ab5c561c@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 lpolzer): http://groups.google.com/group/comp.lang.lisp/browse_thread/thread/ea6ee080040a2cd1/5dcff628981f7e76 may help to produce an easy solution. -- Ticket URL: cl-weblocks cl-weblocks