gendl issueshttps://gitlab.common-lisp.net/gendl/gendl/-/issues2017-04-10T15:43:27Zhttps://gitlab.common-lisp.net/gendl/gendl/-/issues/152gwl:start-gwl does not roll over to next available port for Allegroserve2017-04-10T15:43:27ZDave Coopergwl:start-gwl does not roll over to next available port for Allegroserve*Created by: genworks*
Currently crashes when trying to start AllegroServe on port 9000 when one is already running.
**Imported comments:**
*By genworks on 2011-11-18 23:24:40 UTC*
This is duplicated in Issue #8.
*Created by: genworks*
Currently crashes when trying to start AllegroServe on port 9000 when one is already running.
**Imported comments:**
*By genworks on 2011-11-18 23:24:40 UTC*
This is duplicated in Issue #8.
https://gitlab.common-lisp.net/gendl/gendl/-/issues/153cl-lite fails on :create-asd-file? with relative pathname2017-04-10T15:43:27ZDave Coopercl-lite fails on :create-asd-file? with relative pathname*Created by: genworks*
It appears that cl-lite generates bogus .asd files when called on a relative pathname with :create-asd-file? t.
I have called it on surf/ directory with full pathname, so the .asd file there is now correct.
...*Created by: genworks*
It appears that cl-lite generates bogus .asd files when called on a relative pathname with :create-asd-file? t.
I have called it on surf/ directory with full pathname, so the .asd file there is now correct.
But, the cl-lite itself needs to be fixed to generate proper .asd files when called with relative pathnames.
**Imported comments:**
*By genworks on 2013-11-01 03:46:50 UTC*
Fixed. https://gitlab.common-lisp.net/gendl/gendl/-/issues/154cosmetic: links in readme still point to github2017-04-10T15:43:27ZDaniel KochmaĆskicosmetic: links in readme still point to githubminor issueminor issuehttps://gitlab.common-lisp.net/gendl/gendl/-/issues/155required input not showing up in Glime for points-display2017-04-10T15:43:27ZDave Cooperrequired input not showing up in Glime for points-displayYou should be able to replicate by making the following:
```
(define-object try ()
:objects
((points-disp :type 'points-display
:...
```
At the `:...`, I think the minibuffer should be showing
...You should be able to replicate by making the following:
```
(define-object try ()
:objects
((points-disp :type 'points-display
:...
```
At the `:...`, I think the minibuffer should be showing
`&required points`
seeing as `points` is a required input-slot for `'points-display`. However it is only showing the `&optional` input-slots, which appear to be coming from the base-object mixin.
I have yet to do really comprehensive testing, but other objects I've seen which have required input-slots show up with them properly listed under the `&required` section...
Gail ZachariasGail Zachariashttps://gitlab.common-lisp.net/gendl/gendl/-/issues/156Glime not showing messages in computed-slots2017-04-10T15:43:27ZDave CooperGlime not showing messages in computed-slots
Ok here's another one --- Please try the following snippet:
```
(in-package :gdl-user)
(define-object test-box (box)
:computed-slots
((linear-size (+ (the
```
If you put the cursor after the `the`, I would expect ...
Ok here's another one --- Please try the following snippet:
```
(in-package :gdl-user)
(define-object test-box (box)
:computed-slots
((linear-size (+ (the
```
If you put the cursor after the `the`, I would expect messages from `box` to show up (because `box` is a mixin here). But, i'm only seeing
```
(the &rest reference-chain)
```
Gail ZachariasGail Zachariashttps://gitlab.common-lisp.net/gendl/gendl/-/issues/157Gendl Function arguments not showing up in Glime2017-04-10T15:43:27ZDave CooperGendl Function arguments not showing up in Glime
Please try the following snippet:
```
(in-package :gdl-user)
(define-object try (box)
:computed-slots ((top-vector (the (face-normal-vector
```
After the `(face-normal-vector` I would think you should see the argumen...
Please try the following snippet:
```
(in-package :gdl-user)
(define-object try (box)
:computed-slots ((top-vector (the (face-normal-vector
```
After the `(face-normal-vector` I would think you should see the argument list for the `face-normal-vector` message of `base-object`, which is `(direction)`.
Gail ZachariasGail Zachariashttps://gitlab.common-lisp.net/gendl/gendl/-/issues/158slime-documentation fails when symbol not in package2017-04-10T15:43:27ZGail Zachariasslime-documentation fails when symbol not in packagem-x slime-documentation fails when invoked on a symbol that doesn't exist (i.e. is not interned in the current package). That's the wrong thing for messages, which are package independent.m-x slime-documentation fails when invoked on a symbol that doesn't exist (i.e. is not interned in the current package). That's the wrong thing for messages, which are package independent.Gail ZachariasGail Zachariashttps://gitlab.common-lisp.net/gendl/gendl/-/issues/159Object inputs are not filtering as normal messages do2017-04-10T15:43:27ZDave CooperObject inputs are not filtering as normal messages doIn the following snippet:
```
(in-package :gwl)
(define-object base-clnet-mixin (base-ajax-sheet)
:objects ((proto :type 'base-ajax-sheet
:u
```
the list of completions in minibuffer continues to display all ...In the following snippet:
```
(in-package :gwl)
(define-object base-clnet-mixin (base-ajax-sheet)
:objects ((proto :type 'base-ajax-sheet
:u
```
the list of completions in minibuffer continues to display all available input-slots, even after typing the `:u`. It should filter down to ui-specific-layout-js and use-jquery?
This appears to be an issue wether `:u` or `u` is entered (but normally of course these are given as keyword symbols).Gail ZachariasGail Zachariashttps://gitlab.common-lisp.net/gendl/gendl/-/issues/161Slime loses connection if new CL is opened which does not have glime loaded, ...2017-04-10T15:43:27ZDave CooperSlime loses connection if new CL is opened which does not have glime loaded, after glime.el is loaded into the emacsIf you do
```
(load-glime)
```
this will compile & load `glime.lisp`.
If you then
```
M-x load-file .../glime.el
```
it will enable the emacs extentions which make completions etc work better in glime.
However if you now sp...If you do
```
(load-glime)
```
this will compile & load `glime.lisp`.
If you then
```
M-x load-file .../glime.el
```
it will enable the emacs extentions which make completions etc work better in glime.
However if you now spawn a new Lisp from the same Slime/emacs session, e.g. with
```
M-- M-x slime
```
and load Gendl on top of it, but without glime loaded, now you will get errors and lose the Slime connection, if you try to edit a Gendl file.Gail ZachariasGail Zachariashttps://gitlab.common-lisp.net/gendl/gendl/-/issues/163Default loading fails in devo2017-04-10T15:43:27ZGail ZachariasDefault loading fails in devoIn a bare ccl and devo branch, (ql:quickload :gendl) fails for me with
> Error: System "paserve" not found
The problem seems to be that asdf preloads dependent asd files before loading code, and gwl.asd has conditionalizations on #+za...In a bare ccl and devo branch, (ql:quickload :gendl) fails for me with
> Error: System "paserve" not found
The problem seems to be that asdf preloads dependent asd files before loading code, and gwl.asd has conditionalizations on #+zacl, but zacl the library (as opposed to zacl the asd file) hasn't been loaded yet when gwl.asd is loaded.Dave CooperDave Cooperhttps://gitlab.common-lisp.net/gendl/gendl/-/issues/91Connection to Emacs lost2016-11-02T23:49:06ZDave CooperConnection to Emacs lost*Created by: reiniervandijk*
Occasionally, the connection of the lisp console to Emacs goes lost. Hard to replicate. For me it happened during compilation of a file and having Tasty open with reasonably sized X3D model.
```lisp
disp...*Created by: reiniervandijk*
Occasionally, the connection of the lisp console to Emacs goes lost. Hard to replicate. For me it happened during compilation of a file and having Tasty open with reasonably sized X3D model.
```lisp
dispatch-event: (:return #<multiprocessing:process worker @ #x29772fc2> (:ok "t") 1504)
encode-message
decode-message
dispatch-event: (:emacs-rex (swank:autodoc (quote ()) <User Code> swank::%cursor-marker%))) :print-right-margin 155) ":move" t 1505)
close-connection: Attempt to start thread worker gave OS error code 0xc ...
;; Event history end.
;; Backtrace:
;; Connection to Emacs lost. [
;; condition: Attempt to start thread worker gave OS error code 0xc
;; type: simple-error
;; style: :spawn]
```
**Imported comments:**
*By genworks on 2013-02-18 19:41:53 UTC*
We are going to upgrade to the latest swank/slime in the next release (by end of this month, including full Enterprise 1582), and see if this continues to be an issue.
This Issue will remain open until the problem is clearly resolved.
In the meantime be aware that the Franz ELI is always available as an alternative to Slime - with packaged Gendl releases you can start ELI with
M-x gdl
instead of
M-x gendl
https://gitlab.common-lisp.net/gendl/gendl/-/issues/118Tasty missing JQuery UI images2016-11-02T23:22:57ZDave CooperTasty missing JQuery UI images*Created by: reiniervandijk*
Most Jquery UI icons/images are not published. This will result in the browser casting errors.
Some of which can be found online, for example:
![Jquery icon](https://github.com/jquery/jquery-ui/blob/mast...*Created by: reiniervandijk*
Most Jquery UI icons/images are not published. This will result in the browser casting errors.
Some of which can be found online, for example:
![Jquery icon](https://github.com/jquery/jquery-ui/blob/master/themes/base/images/ui-icons_222222_256x240.png?raw=true)
The complete list of missing images:
+ Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:9000/static/gwl/style/images/ui-icons_222222_256x240.png
+ Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:9000/static/gwl/style/images/ui-bg_flat_75_f9f9f9_40x100.png
+ Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:9000/static/gwl/style/images/ui-bg_highlight-hard_75_b6b6b6_1x100.png
+ Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:9000/static/gwl/style/images/ui-bg_highlight-hard_65_bed73b_1x100.png
+ Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:9000/static/gwl/style/images/ui-bg_highlight-hard_75_e6e6e6_1x100.pnghttps://gitlab.common-lisp.net/gendl/gendl/-/issues/140Allow layout of form-controls from other objects in tree2015-03-31T02:17:23ZDave CooperAllow layout of form-controls from other objects in tree*Created by: genworks*
As gdlAjax works currently, the form-controls have to be local to the sheet (or sheet-section) where they are laid out. It should be possible to use form-controls which are in child objects or other objects (e.g. ...*Created by: genworks*
As gdlAjax works currently, the form-controls have to be local to the sheet (or sheet-section) where they are laid out. It should be possible to use form-controls which are in child objects or other objects (e.g. passed in as inputs) and laid out in the current sheet. It should also be possible to construct HTML strings using form-controls from current sheet, and pass those HTML strings into other objects to be laid out (or as inner-html input).
This will require change to form-control-processor, and should be backward compatible since it is an extension of the way things work currently.
**Imported comments:**
*By genworks on 2012-03-30 14:44:58 UTC*
this is committed, needs to be monitored to make sure it doesn't cause other strange behavior.
NOTE that main-view in skeleton-ui-element HAS BEEN CHANGED to inner-html.https://gitlab.common-lisp.net/gendl/gendl/-/issues/139make-gdl-app updated for this release2015-03-31T02:17:23ZDave Coopermake-gdl-app updated for this release*Created by: genworks*
Enhance the :gdl-build package to support a compatible make-gdl-app function as compatible as possible to the 1580 make-gdl-app. Also used for internal builds. Also automate the generating of customer license file...*Created by: genworks*
Enhance the :gdl-build package to support a compatible make-gdl-app function as compatible as possible to the 1580 make-gdl-app. Also used for internal builds. Also automate the generating of customer license files for proprietary customers. https://gitlab.common-lisp.net/gendl/gendl/-/issues/138Website upgraded to support customer needs2015-03-31T02:17:23ZDave CooperWebsite upgraded to support customer needs*Created by: genworks*
Website application requires product configurator, download wizard, and customer license file manager. *Created by: genworks*
Website application requires product configurator, download wizard, and customer license file manager. https://gitlab.common-lisp.net/gendl/gendl/-/issues/137GWL (gdlAjax) replaces _both_ innerHTML and js-to-eval2015-03-31T02:17:23ZDave CooperGWL (gdlAjax) replaces _both_ innerHTML and js-to-eval*Created by: genworks*
As reported by Reinier van Dijk --- these should be separate conditionals, with separate conditional replacement code in the gdl-ajax.js javascript.
**Imported comments:**
*By genworks on 2013-01-12 22:...*Created by: genworks*
As reported by Reinier van Dijk --- these should be separate conditionals, with separate conditional replacement code in the gdl-ajax.js javascript.
**Imported comments:**
*By genworks on 2013-01-12 22:46:45 UTC*
We need some examples of each combination. It seems to me that the js-to-eval needs to be evaluated any time the innerHTML is refreshed, whether or not the js-to-eval is actually dirty (i.e. :unbound) or not after the gdlAjax submission and associated fields are bashed and function is called. This is because the js-to-eval is typically intended for e.g. jQuery widgets which need to be initialized whenever the html is rendered.
This brings into question whether there is a real need for the js-always-to-eval ? When is that ever really necessary?
Note that in demos/newsite/, both of these are used. But after we look through some simple examples I have a feeling that we will determine that the js-always-to-eval is really redundant. Let's see where this goes.
*By genworks on 2013-01-12 22:57:28 UTC*
@reiniervandijk You may be interested to follow this Issue.
*By reiniervandijk on 2013-01-15 12:25:41 UTC*
Think of the opposite. If js-to-eval becomes :unbound, would you like to have :inner-html evaluated? No, you *don't*. In case of the SVG canvas, an :unbound js-to-eval (like add-line) will 'drag' the inner-html along with it right now, resulting in a new canvas being created every time. I think you need to clearly offer the user all capabilities that one would like to have. Suggestion:
1. keep js-always-to-eval: this can be the initialization code if innerHTML changes. One may also call it js-on-init. Another option would be to define js-before-init **AND** js-after-init. Make sure to tell users that you typically expect static strings here, without dependencies.
2. keep js-to-eval: this should normally be used for js that is dis-related to init events.
3. compute js-all-to-eval with this logic:
* if both js-always-to-eval AND innerHTML :unbound **AND** js-to-eval :unbound, then
```(string-append (the js-always-to-eval) (the js-to-eval))```
* otherwise 1 on the 2, or none.https://gitlab.common-lisp.net/gendl/gendl/-/issues/136gdl-demos does not build due to package error2015-03-31T02:17:22ZDave Coopergdl-demos does not build due to package error*Created by: quicklisp*
I get "The name "SURF" does not designate any package" when trying to build today.
**Imported comments:**
*By genworks on 2012-05-06 15:57:56 UTC*
Is that when building GDL-demos from a clean slate, or aft...*Created by: quicklisp*
I get "The name "SURF" does not designate any package" when trying to build today.
**Imported comments:**
*By genworks on 2012-05-06 15:57:56 UTC*
Is that when building GDL-demos from a clean slate, or after already building some other systems?
Yours Truly,
Dave Cooper
On May 6, 2012, at 10:00 AM, Zach Beane<reply@reply.github.com> wrote:
> I get "The name "SURF" does not designate any package" when trying to build today.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/genworks/Genworks-GDL/issues/26
*By quicklisp on 2012-05-06 16:01:25 UTC*
That's building gdl-demos independently of anything else.
*By genworks on 2012-05-06 16:36:01 UTC*
This should be fixed with latest version pushed into git. Note that there is still a potential issue of order-dependency when loading any form with gdl:define-package -- this package definition changes when :surf package is loaded (maybe not such a great idea). gdl:define-package definition changes to include (:use :surf) in the package definition. This causes some potential issues if systems are loaded in an unexpected order. When I can nail down the issue a bit more concretely, I will build in some logic to avoid the package error in those cases. As long as standard Quicklisp build tests do not exhibit the error right now then I don't consider it top priority.
*By quicklisp on 2012-05-08 14:25:58 UTC*
FYI, there's a similar error in the gdl-site system.
*By genworks on 2012-05-08 17:49:13 UTC*
Thank you. I just deleted that system because it is redundant - :gdl-demos includes the files from :gdl-site and there would be no reason to load :gdl-site independently of :gdl-demos.
*By genworks on 2012-05-14 16:53:00 UTC*
These package issues should be all better now. https://gitlab.common-lisp.net/gendl/gendl/-/issues/135VRML broken in tasty2015-03-31T02:17:22ZDave CooperVRML broken in tasty*Created by: aclark2*
After recent commits, VRML is now broken in tasty (but works in ta2).
Allegro console shows the following output:
4-aserve-worker: 05/14/12 - 08:10:59 - while processing command "GET /sessions/103d35b74b3/viewpor...*Created by: aclark2*
After recent commits, VRML is now broken in tasty (but works in ta2).
Allegro console shows the following output:
4-aserve-worker: 05/14/12 - 08:10:59 - while processing command "GET /sessions/103d35b74b3/viewport/model.wrl HTTP/1.1"
got error symbol-value got 2 args, wanted 1 arg.
I believe everything was still working fine on Friday (05/11).
**Imported comments:**
*By genworks on 2012-05-14 16:52:30 UTC*
This should be fixed now with latest push. https://gitlab.common-lisp.net/gendl/gendl/-/issues/134Fails to build when trying to find "QL" package2015-03-31T02:17:21ZDave CooperFails to build when trying to find "QL" package*Created by: quicklisp*
None of the systems build any more, as there's a reference to QL:FOO in the sources. Quicklisp isn't available as a dependency for libraries to use, sorry.
**Imported comments:**
*By genworks on 2012-05-17 15...*Created by: quicklisp*
None of the systems build any more, as there's a reference to QL:FOO in the sources. Quicklisp isn't available as a dependency for libraries to use, sorry.
**Imported comments:**
*By genworks on 2012-05-17 15:58:02 UTC*
Thank you, this is cleaned up now. https://gitlab.common-lisp.net/gendl/gendl/-/issues/133Gendl-specific colorizing needed in glime mode2015-03-31T02:17:21ZDave CooperGendl-specific colorizing needed in glime mode*Created by: genworks*
slime/glime mode from dist/emacs/gdl.el does not fully colorize Gendl-specific operators, such as "the," "the-object," "the-child."
color-theme implementation needs to be customized to highlight these operators....*Created by: genworks*
slime/glime mode from dist/emacs/gdl.el does not fully colorize Gendl-specific operators, such as "the," "the-object," "the-child."
color-theme implementation needs to be customized to highlight these operators.
**Imported comments:**
*By genworks on 2012-05-29 09:26:39 UTC*
Note that the legacy gdl:set-colors are available by commenting out the "color-theme" lines and adding
(gdl:set-colors)
in the emacs/gdl.el