35973 0 true 2009-08-13T20:03:05Z 35973 71 test-scriptonly-1-fails-cross-platform 39134 18897 invalid javascript prio:high tests 2009-08-13T21:04:37Z 35973 Stephen Compall Stephen Compall Stephen Compall http://weblocks.lighthouseapp.com/projects/18897/tickets/71 PS now yields funcall(document.write, 'test'); instead of the expected document.write('test');. PS now yields funcall(document.write, 'test'); instead of the expected document.write('test');. <div><p>PS now yields funcall(document.write, 'test'); instead of the expected document.write('test');.</p></div> 35973 0 false 2009-02-17T18:25:24Z 34091 2008-11-24T06:00:00Z 23288 68 fix-trivial-shell-diffing 3 18897 new sbcl workaround 2009-06-10T13:58:38Z 34091 Leslie P. Polzer Leslie P. Polzer Stephen Compall http://weblocks.lighthouseapp.com/projects/18897/tickets/68 0.8.5 “Spring Cleaning” This still fails for me on the first pass, maybe due to race conditions in sb-ext:run-program. Wrapping the shell command in a WITH-TIMEOUT would be a temporary solution. This still fails for me on the first pass, maybe due to race conditions in sb-ext:run-program. Wrapping the shell command in a WITH-TIMEOUT would be a temporary solution. <div><p>This still fails for me on the first pass, maybe due to race conditions in sb-ext:run-program.</p> <p>Wrapping the shell command in a WITH-TIMEOUT would be a temporary solution.</p></div> 35973 0 false 2008-11-01T19:50:06Z 35973 16 fuzz-up-html-tests-with-unification-style-matching 7 18897 open libraries 2009-06-10T13:49:26Z 35973 Stephen Compall Stephen Compall Stephen Compall http://weblocks.lighthouseapp.com/projects/18897/tickets/16 I'm working on unification for DOM in CXML branch "dom-unification" at git://home.nocandysw.com/git/cxml.git/. This, theoretically, can be used to leave out the HTML we don't care about, extract matched tree parts for further comparison, and so on. I'm working on unification for DOM in CXML branch "dom-unification" at git://home.nocandysw.com/git/cxml.git/. This, theoretically, can be used to leave out the HTML we don't care about, extract matched tree parts for further comparison, and so on. <div><p>I'm working on unification for DOM in CXML branch "dom-unification" at git://home.nocandysw.com/git/cxml.git/. This, theoretically, can be used to leave out the HTML we don't care about, extract matched tree parts for further comparison, and so on.</p></div> 34091 1 true 2009-05-21T15:59:49Z 37109 70 markup-does-not-validate-under-xhtml-10-strict 39133 18897 resolved dom id 2009-05-21T17:29:33Z 34091 Leslie P. Polzer Nandan Bagchee Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/70 Example carp from http://validator.w3.org/: Value of attribute "id" invalid: "0" cannot start a name…'><div class='widget composite' id='0'><div class='widget data-editor datafor.. It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit. Example carp from http://validator.w3.org/: Value of attribute "id" invalid: "0" cannot start a name…'><div class='widget composite' id='0'><div class='widget data-editor datafor.. It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit. <div><p>Example carp from <a href="http://validator.w3.org/:%3C/p">http://validator.w3.org/:</a></p> &gt; <p>Value of attribute "id" invalid: "0" cannot start a name&hellip;'&gt;</p> <div class="widget data-editor datafor..&lt;/p&gt; &lt;p&gt;It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.&lt;/p&gt;"> </div></div> 34091 0 false 2009-02-15T12:56:09Z 34091 67 support-generated-admin-interface-defmodel 39132 18897 new 2009-03-29T15:43:17Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/67 http://groups.google.com/group/weblocks/browse_thread/thread/c49e8b9a5066d261/3be2f292d461c71a?lnk=gst&q=defmodel#3be2f292d461c71a http://paste.lisp.org/display/60601 http://groups.google.com/group/weblocks/browse_thread/thread/c49e8b9a5066d261/3be2f292d461c71a?lnk=gst&q=defmodel#3be2f292d461c71a http://paste.lisp.org/display/60601 <div><p><a href="http://groups.google.com/group/weblocks/browse_thread/thread/c49e8b9a5066d261/3be2f292d461c71a?lnk=gst&amp;q=defmodel#3be2f292d461c71a"> http://groups.google.com/group/w...</a></p> <p><a href="http://paste.lisp.org/display/60601">http://paste.lisp.org/display/60601</a></p></div> 34091 0 true 2008-10-30T19:43:25Z 34091 2008-11-29T06:00:00Z 22552 9 pretty-backtraces 2 18897 resolved debugging feature 2009-02-28T15:36:53Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/9 0.9 “Dispatching and widget tree enhancements” Apply color, formatting and some basic controls (e.g. reset current session, reset all sessions) to error messages and backtraces. Apply color, formatting and some basic controls (e.g. reset current session, reset all sessions) to error messages and backtraces. <div><p>Apply color, formatting and some basic controls (e.g. reset current session, reset all sessions) to error messages and backtraces.</p></div> 34091 0 false 2008-11-20T19:14:38Z 34091 2008-11-24T06:00:00Z 23288 46 defwebapp-needs-to-support-debug 21 18897 new convenience docs junior newbie webapps 2009-02-25T12:44:37Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/46 0.8.5 “Spring Cleaning” 34091 0 false 2009-02-18T11:13:40Z 34091 2008-11-24T06:00:00Z 23288 69 prevalence-store-needs-a-good-test-suite 35 18897 new prevalence prio:high sev:medium stores tests 2009-02-18T11:13:42Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/69 0.8.5 “Spring Cleaning” 34091 0 false 2009-02-12T13:34:34Z 34091 2008-11-24T06:00:00Z 23288 66 dropdown-doesnt-allow-nil-as-choice 34 18897 new dropdown presentations prio:high sev:high 2009-02-12T13:34:39Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/66 0.8.5 “Spring Cleaning” NIL is equivalent to "no value" and thus not a valid choice. Devise some way to make NIL a usable choice NIL is equivalent to "no value" and thus not a valid choice. Devise some way to make NIL a usable choice <div><p>NIL is equivalent to "no value" and thus not a valid choice.</p> <p>Devise some way to make NIL a usable choice</p></div> 34091 0 false 2009-02-12T11:14:10Z 34091 65 support-halos 39131 18897 new feature prio:high 2009-02-12T11:14:13Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/65 Seaside supports Halos for widgets. They provide an action bar around a widgets that helps the user analyze and manipulate it. Examples: * show class name and instance information * show dependencies * mark widget dirty to refresh it * view slots (describe) with subprotocol HALO-DESCRIBE for customization * remove widget from tree Toggling Halos should be possible with the debug action bar. Seaside supports Halos for widgets. They provide an action bar around a widgets that helps the user analyze and manipulate it. Examples: * show class name and instance information * show dependencies * mark widget dirty to refresh it * view slots (describe) with subprotocol HALO-DESCRIBE for customization * remove widget from tree Toggling Halos should be possible with the debug action bar. <div><p>Seaside supports Halos for widgets.</p> <p>They provide an action bar around a widgets that helps the user analyze and manipulate it.</p> <p>Examples:</p> <ul> <li> <p>show class name and instance information</p> </li> <li> <p>show dependencies</p> </li> <li> <p>mark widget dirty to refresh it</p> </li> <li> <p>view slots (describe) with subprotocol HALO-DESCRIBE for customization</p> </li> <li> <p>remove widget from tree</p> </li> </ul> <p>Toggling Halos should be possible with the debug action bar.</p></div> 34091 0 false 2009-02-09T10:20:58Z 34091 2008-11-24T06:00:00Z 23288 64 move-checkboxeslisp-to-types 33 18897 new janitor junitor "prio:very low" "sev:very low" 2009-02-09T10:20:59Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/64 0.8.5 “Spring Cleaning” Currently in types/presentations but includes both parser and presentation. Currently in types/presentations but includes both parser and presentation. <div><p>Currently in types/presentations but includes both parser and presentation.</p></div> 45132 0 true 2009-01-31T14:21:51Z 34091 2008-11-24T06:00:00Z 23288 63 show-is-not-defined-for-div 33 18897 invalid javascript 2009-02-05T20:41:34Z 34091 Leslie P. Polzer Leslie P. Polzer Benjamin Collins http://weblocks.lighthouseapp.com/projects/18897/tickets/63 0.8.5 “Spring Cleaning” Problem in the Flash widget: http://groups.google.com/group/weblocks/t/d3ed67aef052984f Problem in the Flash widget: http://groups.google.com/group/weblocks/t/d3ed67aef052984f <div><p>Problem in the Flash widget: <a href="http://groups.google.com/group/weblocks/t/d3ed67aef052984f">http://groups.google.com/group/w...</a></p></div> 34091 1 false 2008-11-04T14:59:35Z 34091 2008-11-29T06:00:00Z 22552 17 dynamic-css-generation 7 18897 new css feature sev:low 2009-02-05T09:08:09Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/17 0.9 “Dispatching and widget tree enhancements” Static CSS sucks for most purposes. A first step towards sanity would be a GF widget-dynamic-css/widget-css along with a Parenscript-like DSL. I already have a compiler prototype (attached) Static CSS sucks for most purposes. A first step towards sanity would be a GF widget-dynamic-css/widget-css along with a Parenscript-like DSL. I already have a compiler prototype (attached) <div><p>Static CSS sucks for most purposes. A first step towards sanity would be a GF widget-dynamic-css/widget-css along with a Parenscript-like DSL.</p> <p>I already have a compiler prototype (attached)</p></div> 35973 1 true 2008-12-23T21:12:53Z 35973 2008-11-29T06:00:00Z 22552 61 clsql-repeatable-per-thread-connection-pooling 2 18897 resolved libraries stores threads 2009-01-11T22:03:02Z 35973 Stephen Compall Stephen Compall Stephen Compall http://weblocks.lighthouseapp.com/projects/18897/tickets/61 0.9 “Dispatching and widget tree enhancements” Yarek Kowalik writes: > Is there a reason why clsql connection pool cannot be integrated into > clsql itself? There is another reason that it must be done by integration. Instances of standard-db-object store the database used to fetch them, to be used for functions like `update-records-from-instance' as the default :database argument. This isn't a problem for uses of that function directly within weblocks-clsql, because it always passes :database explicitly, or does some other explicit manipulation (see delete-persistent-object (database t) in svg). However, join slots can be lazily fetched on first access, and the usefulness of combining join slots with mixin views cannot be ignored. At that point, we do not have the opportunity to specify what the database to use should be. So CLSQL must be taught to `find-process-database' in those instances. On another issue: CLSQL already has "connection pools" in a more traditional sense. So we must have a different name. I think "repeatable per-thread" captures what's different about these pools. Yarek Kowalik writes: > Is there a reason why clsql connection pool cannot be integrated into > clsql itself? There is another reason that it must be done by integration. Instances of standard-db-object store the database used to fetch them, to be used for functions like `update-records-from-instance' as the default :database argument. This isn't a problem for uses of that function directly within weblocks-clsql, because it always passes :database explicitly, or does some other explicit manipulation (see delete-persistent-object (database t) in svg). However, join slots can be lazily fetched on first access, and the usefulness of combining join slots with mixin views cannot be ignored. At that point, we do not have the opportunity to specify what the database to use should be. So CLSQL must be taught to `find-process-database' in those instances. On another issue: CLSQL already has "connection pools" in a more traditional sense. So we must have a different name. I think "repeatable per-thread" captures what's different about these pools. <div><p>Yarek Kowalik writes:</p> <blockquote> <p>Is there a reason why clsql connection pool cannot be integrated into clsql itself?</p> </blockquote> <p>There is another reason that it must be done by integration. Instances of standard-db-object store the database used to fetch them, to be used for functions like <code>update-records-from-instance' as the default :database argument. This isn't a problem for uses of that function directly within weblocks-clsql, because it always passes :database explicitly, or does some other explicit manipulation (see delete-persistent-object (database t) in svg).</code></p> <p>However, join slots can be lazily fetched on first access, and the usefulness of combining join slots with mixin views cannot be ignored. At that point, we do not have the opportunity to specify what the database to use should be. So CLSQL must be taught to <code>find-process-database' in those instances.</code></p> <p>On another issue: CLSQL already has "connection pools" in a more traditional sense. So we must have a different name. I think "repeatable per-thread" captures what's different about these pools.</p></div> 34091 0 false 2008-11-09T17:41:35Z 34091 2008-11-29T06:00:00Z 22552 25 simplify-store-api 10 18897 new api-change feature prio:med stores 2009-01-03T12:08:24Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/25 0.9 “Dispatching and widget tree enhancements” The store arg needs to become a keyword arg with default *default-store*. The store arg needs to become a keyword arg with default *default-store*. <div><p>The store arg needs to become a keyword arg with default <em>default-store</em>.</p></div> 34091 0 false 2008-12-29T06:33:54Z 42033 62 make-navigation-doesnt-work-with-string-and-lambda-widgets 39130 18897 new 2008-12-29T06:35:06Z 42033 Divia Divia Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/62 (make-navigation 'main-menu 'employees (make-instance 'composite :widgets "employees") 'companies "companies") "employees" would be displayed, but "companies" wouldn't be. Having looked at the code for make-navigation, it seems to be the case that it's expecting a CLOS widget object, and that strings and lambdas are special cases that don't work with make-navigation. There are a few more notes here: http://groups.google.com/group/weblocks/browse_thread/thread/67f981948932498a (make-navigation 'main-menu 'employees (make-instance 'composite :widgets "employees") 'companies "companies") "employees" would be displayed, but "companies" wouldn't be. Having looked at the code for make-navigation, it seems to be the case that it's expecting a CLOS widget object, and that strings and lambdas are special cases that don't work with make-navigation. There are a few more notes here: http://groups.google.com/group/weblocks/browse_thread/thread/67f981948932498a <div><p>(make-navigation 'main-menu</p> <pre> <code> 'employees (make-instance 'composite :widgets "employees") 'companies "companies") </code> </pre> <p>"employees" would be displayed, but "companies" wouldn't be. Having looked at the code for make-navigation, it seems to be the case that it's expecting a CLOS widget object, and that strings and lambdas are special cases that don't work with make-navigation.</p> <p>There are a few more notes here: <a href="http://groups.google.com/group/weblocks/browse_thread/thread/67f981948932498a"> http://groups.google.com/group/w...</a></p></div> 35973 0 false 2008-12-23T05:48:32Z 35973 60 re-login-as-subclass-of-quickform 39130 18897 new cleanup widget 2008-12-23T21:22:46Z 35973 Stephen Compall Stephen Compall Stephen Compall http://weblocks.lighthouseapp.com/projects/18897/tickets/60 Saikat Chakrabarti <saikat1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: > I am still new to Weblocks and Lisp and was going through some of the > widget code to get a better sense of things. One thing I was > wondering - why not make login a subclass of quickform (or maybe even > an instance of a quickform)? It looks like it mostly just repeats all > the slots in a quickform and adds one extra one (on-login - which I'm > not sure why that can't be the same as on-success for a quickform). I > am sure I am missing something though with my noob eyes. I think you are right. Subclassing is the best choice, so that initargs propagate, and we can duplicate the defaults. The main difference is in the accessor methods. Who out there is currently using or defining methods on the various login-* accessor GFs? I just checked hfsbo.com, and I didn't use any. Saikat Chakrabarti <saikat1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: > I am still new to Weblocks and Lisp and was going through some of the > widget code to get a better sense of things. One thing I was > wondering - why not make login a subclass of quickform (or maybe even > an instance of a quickform)? It looks like it mostly just repeats all > the slots in a quickform and adds one extra one (on-login - which I'm > not sure why that can't be the same as on-success for a quickform). I > am sure I am missing something though with my noob eyes. I think you are right. Subclassing is the best choice, so that initargs propagate, and we can duplicate the defaults. The main difference is in the accessor methods. Who out there is currently using or defining methods on the various login-* accessor GFs? I just checked hfsbo.com, and I didn't use any. <div><p>Saikat Chakrabarti writes:</p> <blockquote> <p>I am still new to Weblocks and Lisp and was going through some of the widget code to get a better sense of things. One thing I was wondering - why not make login a subclass of quickform (or maybe even an instance of a quickform)? It looks like it mostly just repeats all the slots in a quickform and adds one extra one (on-login - which I'm not sure why that can't be the same as on-success for a quickform). I am sure I am missing something though with my noob eyes.</p> </blockquote> <p>I think you are right. Subclassing is the best choice, so that initargs propagate, and we can duplicate the defaults. The main difference is in the accessor methods. Who out there is currently using or defining methods on the various login-* accessor GFs? I just checked hfsbo.com, and I didn't use any.</p></div> 35973 0 true 2008-12-17T14:33:32Z 35973 2008-11-24T06:00:00Z 23288 59 reevaluating-a-defstore-form-sets-symbol-value-store-name-to-nil 2 18897 resolved prio:med stores 2008-12-17T19:34:59Z 35973 Stephen Compall Stephen Compall Stephen Compall http://weblocks.lighthouseapp.com/projects/18897/tickets/59 0.8.5 “Spring Cleaning” The straightforward fix is to to change defparameter to defvar, but I'm not sure that's appropriate in the case of changing store type or parameters. The straightforward fix is to to change defparameter to defvar, but I'm not sure that's appropriate in the case of changing store type or parameters. <div><p>The straightforward fix is to to change defparameter to defvar, but I'm not sure that's appropriate in the case of changing store type or parameters.</p></div> 34091 0 false 2008-12-06T10:50:17Z 34091 2008-11-24T06:00:00Z 23288 58 add-proper-test-suite-declarations 32 18897 new janitor prio:med sev:medium tests 2008-12-06T10:50:19Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/58 0.8.5 “Spring Cleaning” Current state is a mess, 'nuff said. Current state is a mess, 'nuff said. <div><p>Current state is a mess, 'nuff said.</p></div> 34091 0 false 2008-12-06T10:02:08Z 34091 2008-11-24T06:00:00Z 23288 57 weblocks-demo-started-twice 31 18897 new demo sev:low webapps 2008-12-06T10:02:11Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/57 0.8.5 “Spring Cleaning” Remove the spurious start-webapp call from the demo code. Remove the spurious start-webapp call from the demo code. <div><p>Remove the spurious start-webapp call from the demo code.</p></div> 34091 0 true 2008-11-04T15:29:45Z 34091 2008-11-24T06:00:00Z 23288 20 link-to-active-apps-in-default-application 27 18897 resolved debugging feature newbie prio:low 2008-12-02T13:40:47Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/20 0.8.5 “Spring Cleaning” 34091 0 true 2008-12-01T16:01:17Z 34091 2008-11-24T06:00:00Z 23288 56 cookie-name-conflicts 30 18897 resolved 2008-12-02T13:13:19Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/56 0.8.5 “Spring Cleaning” Every server should have a random cookie name to avoid conflicting Weblocks images. Every server should have a random cookie name to avoid conflicting Weblocks images. <div><p>Every server should have a random cookie name to avoid conflicting Weblocks images.</p></div> 34091 0 true 2008-10-31T14:13:06Z 34091 2008-11-24T06:00:00Z 23288 10 sessions-reset-after-reloading-weblocks 25 18897 invalid reloading sessions 2008-12-01T16:01:48Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/10 0.8.5 “Spring Cleaning” All sessions get reset when I reload Weblocks after making some changes. I couldn't narrow it down further yet but I suspect this has might have something to do with Webapps code. All sessions get reset when I reload Weblocks after making some changes. I couldn't narrow it down further yet but I suspect this has might have something to do with Webapps code. <div><p>All sessions get reset when I reload Weblocks after making some changes. I couldn't narrow it down further yet but I suspect this has might have something to do with Webapps code.</p></div> 35973 0 true 2008-11-28T14:14:04Z 35973 54 remove-dataedit-item-widget-data 39130 18897 resolved api-change 2008-11-29T19:31:38Z 35973 Stephen Compall Stephen Compall Stephen Compall http://weblocks.lighthouseapp.com/projects/18897/tickets/54 http://groups.google.com/group/weblocks/t/98424300d0f74bb4 http://groups.google.com/group/weblocks/t/98424300d0f74bb4 <div><p><a href="http://groups.google.com/group/weblocks/t/98424300d0f74bb4">http://groups.google.com/group/w...</a></p></div> 35973 0 false 2008-11-28T15:17:33Z 35973 2008-11-24T06:00:00Z 23288 55 split-symbol-exports-into-multiple-levels 1 18897 open api-change cleanup 2008-11-28T17:36:13Z 34091 Leslie P. Polzer Stephen Compall Stephen Compall http://weblocks.lighthouseapp.com/projects/18897/tickets/55 0.8.5 “Spring Cleaning” Different users may want different parts of the tapestry of exported Weblocks symbols to be available, without having to explicitly name every symbol with :import-from or equivalent mechanism. 1078:efcee8d2eaad defines `wexport`, a function to conveniently split the tapestry in two stages: 1. add exports to a new package like `weblocks-util`; 2. once apps have transitioned by possibly importing `weblocks-util` etc, stop exporting from the main package 1079:f149130986c5 shows an example of the first stage. I happened to choose the continuation symbols and utility symbols to start with as they are the main reasons I don't import weblocks in my app, but other natural groupings should naturally be found. Different users may want different parts of the tapestry of exported Weblocks symbols to be available, without having to explicitly name every symbol with :import-from or equivalent mechanism. 1078:efcee8d2eaad defines `wexport`, a function to conveniently split the tapestry in two stages: 1. add exports to a new package like `weblocks-util`; 2. once apps have transitioned by possibly importing `weblocks-util` etc, stop exporting from the main package 1079:f149130986c5 shows an example of the first stage. I happened to choose the continuation symbols and utility symbols to start with as they are the main reasons I don't import weblocks in my app, but other natural groupings should naturally be found. <div><p>Different users may want different parts of the tapestry of exported Weblocks symbols to be available, without having to explicitly name every symbol with :import-from or equivalent mechanism.</p> <p>1078:efcee8d2eaad defines <code>wexport</code>, a function to conveniently split the tapestry in two stages:</p> <ol> <li>add exports to a new package like <code>weblocks-util</code>;</li> <li>once apps have transitioned by possibly importing <code>weblocks-util</code> etc, stop exporting from the main package</li> </ol> <p>1079:f149130986c5 shows an example of the first stage. I happened to choose the continuation symbols and utility symbols to start with as they are the main reasons I don't import weblocks in my app, but other natural groupings should naturally be found.</p></div> 34091 0 false 2008-11-27T20:06:13Z 34091 2008-11-24T06:00:00Z 23288 53 eliminate-redundancy-in-find-persistent-objects 29 18897 new 2008-11-27T20:06:16Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/53 0.8.5 “Spring Cleaning” The prevalence and memory stores have considerable overlap in FIND-PERSISTENT-OBJECTS up to the point where the implementation is the same apart from one function call. Find a good way to refactor this. The prevalence and memory stores have considerable overlap in FIND-PERSISTENT-OBJECTS up to the point where the implementation is the same apart from one function call. Find a good way to refactor this. <div><p>The prevalence and memory stores have considerable overlap in FIND-PERSISTENT-OBJECTS up to the point where the implementation is the same apart from one function call.</p> <p>Find a good way to refactor this.</p></div> 34091 0 false 2008-11-27T19:53:58Z 34091 2008-11-24T06:00:00Z 23288 52 integrate-slot-name-clash-control-patch 28 18897 new 2008-11-27T19:54:01Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/52 0.8.5 “Spring Cleaning” Weak prerequisite for checkboxes, must for multiple mixins of the same type. Weak prerequisite for checkboxes, must for multiple mixins of the same type. <div><p>Weak prerequisite for checkboxes, must for multiple mixins of the same type.</p></div> 34091 0 false 2008-11-04T15:01:29Z 34091 2008-11-24T06:00:00Z 23288 18 shell-script-wrapper-for-wopmake-app 26 18897 new feature junior newbie "prio:very low" 2008-11-27T12:19:58Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/18 0.8.5 “Spring Cleaning” Write a thin wrapper, possibly utilizing cl-launch. Write a thin wrapper, possibly utilizing cl-launch. <div><p>Write a thin wrapper, possibly utilizing cl-launch.</p></div> 34091 0 true 2008-11-04T15:02:29Z 34091 2008-11-09T23:00:00Z 22551 19 new-website 4 18897 resolved meta prio:medium 2008-11-27T12:19:28Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/19 0.8 Write a simple website app that is both demo and information resource. Design already drafted. Write a simple website app that is both demo and information resource. Design already drafted. <div><p>Write a simple website app that is both demo and information resource.</p> <p>Design already drafted.</p></div> 34091 0 false 2008-11-27T12:18:32Z 34091 2008-11-24T06:00:00Z 23288 51 make-gridedit-work-with-non-objects-too 24 18897 new convenience gridedit 2008-11-27T12:18:32Z 34091 Leslie P. Polzer Leslie P. Polzer Leslie P. Polzer http://weblocks.lighthouseapp.com/projects/18897/tickets/51 0.8.5 “Spring Cleaning” We need to tag the elements of the list with ids to make this possible. We need to tag the elements of the list with ids to make this possible. <div><p>We need to tag the elements of the list with ids to make this possible.</p></div>