gendl issueshttps://gitlab.common-lisp.net/gendl/gendl/-/issues2017-04-10T15:43:27Zhttps://gitlab.common-lisp.net/gendl/gendl/-/issues/150pulldown menus disappear in tasty2017-04-10T15:43:27ZDave Cooperpulldown menus disappear in tasty*Created by: genworks*
A fix for this has been provided by Reinier van Dijk, as well as suggestion to upgrade to JQuery latest (1.6.2, I believe). The fix is in Genworks Support email and needs to be integrated to our tasty/menu code...*Created by: genworks*
A fix for this has been provided by Reinier van Dijk, as well as suggestion to upgrade to JQuery latest (1.6.2, I believe). The fix is in Genworks Support email and needs to be integrated to our tasty/menu code and jquery snapshot here.
**Imported comments:**
*By genworks on 2012-03-30 14:50:03 UTC*
This has been corrected by upgrading to the latest JQuery and plugins. Code from Reinier has not been integrated at this time. https://gitlab.common-lisp.net/gendl/gendl/-/issues/149gwl:start-gwl does not detect in-use port, crashes if one is already running2017-04-10T15:43:27ZDave Coopergwl:start-gwl does not detect in-use port, crashes if one is already running*Created by: genworks*
If a GDL is running with GWL webserver on e.g. port 9000 already, then a new one will crash when it tries to call gwl:start-gwl. This should detect the running server and roll to the next port (e.g. 9001).
*...*Created by: genworks*
If a GDL is running with GWL webserver on e.g. port 9000 already, then a new one will crash when it tries to call gwl:start-gwl. This should detect the running server and roll to the next port (e.g. 9001).
**Imported comments:**
*By genworks on 2011-11-18 23:24:04 UTC*
This seems to occur only on Linux and Mac, not on Windows.
*By genworks on 2012-02-11 21:18:04 UTC*
Removed :timeout argument to net.aserve.client:do-http-request in gwl:start-gwl. Apparently this argument is not supported in portableaserve. Still seems to be supported in native aserve, so not sure why start-gwl wasn't working in Allegro, but looks like it is now (as well as in LispWorks and SBCL). https://gitlab.common-lisp.net/gendl/gendl/-/issues/148several objects in geom-base not rendering properly in VRML and X3D2017-04-10T15:43:27ZDave Cooperseveral objects in geom-base not rendering properly in VRML and X3D*Created by: genworks*
Specifically cone, spherical-cap, and global-polygon-projection need to be addressed. Suggest implementing with simple triangular tessellation, rather than trying to use any built-in VRML or X3D shape primitives...*Created by: genworks*
Specifically cone, spherical-cap, and global-polygon-projection need to be addressed. Suggest implementing with simple triangular tessellation, rather than trying to use any built-in VRML or X3D shape primitives.
**Imported comments:**
*By genworks on 2012-03-30 14:48:38 UTC*
X3D and VRML are essentially working now, will close the issue but have to monitor ongoing enhancements in this area. https://gitlab.common-lisp.net/gendl/gendl/-/issues/147Syntax Coloring Problem2017-04-10T15:43:27ZDave CooperSyntax Coloring Problem*Created by: teodor-gelu*
Code colors in GDL 1581 is not the same as in 1580 for example previously the :sequence (:size ... it was pink, now is yellow. In principle the pink is absent ":input-slots, :functions, :computed-slots, :hid...*Created by: teodor-gelu*
Code colors in GDL 1581 is not the same as in 1580 for example previously the :sequence (:size ... it was pink, now is yellow. In principle the pink is absent ":input-slots, :functions, :computed-slots, :hidden-objects, :objects, :type etc."
**Imported comments:**
*By genworks on 2012-02-08 17:14:01 UTC*
Also make Slime mode available for new release, make sure M-. works in both ELI and Slime modes.
*By genworks on 2012-03-13 04:26:41 UTC*
Colors and M-. have been fixed for Franz ELI.
Still have to enable Slime mode, so this issue will remain open until that happens.
*By genworks on 2012-03-14 00:10:20 UTC*
Also please fix colors in *shell* buffer -- directories in directory listings are currently unreadable in there because of the colors.
*By genworks on 2012-03-27 14:13:52 UTC*
For Slime mode, add support for .gdl extension files, as alternative to .lisp.
*By genworks on 2013-01-12 23:49:15 UTC*
These issues have been addressed in latest release. .gdl and .gendl extensions are now supported by Slime, asdf, quicklisp, and cl-lite. https://gitlab.common-lisp.net/gendl/gendl/-/issues/146camera limited to single projection-vector, needs to respect a full orientation2017-04-10T15:43:27ZDave Coopercamera limited to single projection-vector, needs to respect a full orientation*Created by: genworks*
The camera (e.g. for input to a base-view) currently consists of a single :projection-vector, which is not enough fully to specify a camera. It needs to be oriented like a box or any other base-object, so you ca...*Created by: genworks*
The camera (e.g. for input to a base-view) currently consists of a single :projection-vector, which is not enough fully to specify a camera. It needs to be oriented like a box or any other base-object, so you can twist the view around and make e.g. the 3D :rear direction point to the top of the 2D sheet containing the viewport.
https://gitlab.common-lisp.net/gendl/gendl/-/issues/145PDF->PNG fails on LW, SBCL2017-04-10T15:43:27ZDave CooperPDF->PNG fails on LW, SBCL*Created by: genworks*
PDF stream is opened in wrong mode (e.g. ascii vs binary) for png and jpeg output-formats.
**Imported comments:**
*By genworks on 2012-02-10 04:07:08 UTC*
This is now fixed for LispWorks and SBCL. There is s...*Created by: genworks*
PDF stream is opened in wrong mode (e.g. ascii vs binary) for png and jpeg output-formats.
**Imported comments:**
*By genworks on 2012-02-10 04:07:08 UTC*
This is now fixed for LispWorks and SBCL. There is still redundent file I/O for PDF->PNG and PDF->JPEG, and the file I/O seems to be slow in SBCL, so this redundancy needs to be addressed. https://gitlab.common-lisp.net/gendl/gendl/-/issues/144geom-base leader-line display error.2017-08-21T19:04:22ZDave Coopergeom-base leader-line display error.*Created by: teodor-gelu*
Leader-line is not displayed in SVG/VML format. This object is not exported as a VRML object.
!!! The .png and .jpg format is Ok.!!!
*Created by: teodor-gelu*
Leader-line is not displayed in SVG/VML format. This object is not exported as a VRML object.
!!! The .png and .jpg format is Ok.!!!
Dave CooperDave Cooperhttps://gitlab.common-lisp.net/gendl/gendl/-/issues/143Tasty zoom-in and zoom-out2017-04-10T15:43:27ZDave CooperTasty zoom-in and zoom-out*Created by: teodor-gelu*
The zoom-in and zoom-out image are reversed :
image viewmag- is zoom-in and
image viewmag+ is zoom-out.
**Imported comments:**
*By genworks on 2012-03-30 14:46:07 UTC*
This is apparently resolved, c...*Created by: teodor-gelu*
The zoom-in and zoom-out image are reversed :
image viewmag- is zoom-in and
image viewmag+ is zoom-out.
**Imported comments:**
*By genworks on 2012-03-30 14:46:07 UTC*
This is apparently resolved, courtesy Teodor-Gelu. https://gitlab.common-lisp.net/gendl/gendl/-/issues/142VRML cone2017-04-10T15:43:27ZDave CooperVRML cone*Created by: teodor-gelu*
The vrml export of a geom-base cone object is inconsistent:
see the Genworks-GDL / documentation / unified-doc / examples / shock-absorber-v0.3
**Imported comments:**
*By genworks on 2012-02-11 21:1...*Created by: teodor-gelu*
The vrml export of a geom-base cone object is inconsistent:
see the Genworks-GDL / documentation / unified-doc / examples / shock-absorber-v0.3
**Imported comments:**
*By genworks on 2012-02-11 21:19:46 UTC*
Closing this because it is redundant with Issue #9. https://gitlab.common-lisp.net/gendl/gendl/-/issues/141Does not build on SBCL: missing components2017-04-10T15:43:27ZDave CooperDoes not build on SBCL: missing components*Created by: quicklisp*
Here are some example failure logs:
http://dl.dropbox.com/u/41993869/quicklisp/fails/fail_genworks-gdl_gdl-all_gdl-all.txt
http://dl.dropbox.com/u/41993869/quicklisp/fails/fail_genworks-gdl_gdl-surf_gdl-sur...*Created by: quicklisp*
Here are some example failure logs:
http://dl.dropbox.com/u/41993869/quicklisp/fails/fail_genworks-gdl_gdl-all_gdl-all.txt
http://dl.dropbox.com/u/41993869/quicklisp/fails/fail_genworks-gdl_gdl-surf_gdl-surf.txt
http://dl.dropbox.com/u/41993869/quicklisp/fails/fail_genworks-gdl_gdl-build_gdl-build.txt
There are others, if it helps.
**Imported comments:**
*By genworks on 2012-03-22 21:20:06 UTC*
Hi Zach,
Thank you for trying these builds again.
Are these current build logs? I just did a clean build of these
systems (SBCL 1.0.55 MacOS) from the current github repository, and I
am not seeing any errors. The gdl-cl-typesetting-ql-patch.asd is
definitely in the repository (that's the error in the first and third
logs), and the second log is showing style-warnings (e.g. IGNORE
declaration for unknown variable &KEY) for methods.lisp, which for
sure are not in the current version of that file in the repository any
more.
Maybe there is something else wrong with my configuration? Please let me know.
Best Regards,
-dave
On Thu, Mar 22, 2012 at 2:06 PM, Zach Beane
<reply@reply.github.com>
wrote:
> Here are some example failure logs:
>
> http://dl.dropbox.com/u/41993869/quicklisp/fails/fail_genworks-gdl_gdl-all_gdl-all.txt
>
> http://dl.dropbox.com/u/41993869/quicklisp/fails/fail_genworks-gdl_gdl-surf_gdl-surf.txt
>
> http://dl.dropbox.com/u/41993869/quicklisp/fails/fail_genworks-gdl_gdl-build_gdl-build.txt
>
> There are others, if it helps.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/genworks/Genworks-GDL/issues/19
--
Genworks Support
support@genworks.com
*By genworks on 2012-03-23 14:00:13 UTC*
Hi Zach,
Thank you for trying these builds again.
Are these current build logs? I just did a clean build of these
systems (SBCL 1.0.55 MacOS) from the current github repository, and I
am not seeing any errors. The gdl-cl-typesetting-ql-patch.asd is
definitely in the repository (that's the error in the first and third
logs), and the second log is showing style-warnings (e.g. IGNORE
declaration for unknown variable &KEY) for methods.lisp, which for
sure are not in the current version of that file in the repository any
more.
Maybe there is something else wrong with my configuration? Please let me know.
Best Regards,
-dave
*By quicklisp on 2012-03-23 19:55:12 UTC*
Must have been a temporary glitch, things build fine now.
What's the duplicate tree in 1580-freeze? Should it be ignored?
*By genworks on 2012-03-23 21:00:50 UTC*
>
> What's the duplicate tree in 1580-freeze? Should it be ignored?
>
Yes, it should be ignored. I will get rid of it soon.
--
My Best,
Dave Cooper, Genworks Support
david.cooper@genworks.com, dave.genworks.com(skype)
USA: 248-327-3253(o), 1-248-330-2979(mobile)
UK: 0191 645 1699
*By genworks on 2012-03-30 14:45:47 UTC*
Must add an ASD system for :genworks-gdl -- genworks-gdl.asd to make it intuitive for folks to load Genworks-GDL with quicklisp. https://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
https://gitlab.common-lisp.net/gendl/gendl/-/issues/132Safari redirects to non-existent session2015-03-31T02:17:20ZDave CooperSafari redirects to non-existent session*Created by: genworks*
Safari tends to redirect toplevel GWL URLs to the previous session ID, which can be timed out or will be non-existent if the Gendl session has been restarted. The make-gwl-object needs to handle this in a reasonab...*Created by: genworks*
Safari tends to redirect toplevel GWL URLs to the previous session ID, which can be timed out or will be non-existent if the Gendl session has been restarted. The make-gwl-object needs to handle this in a reasonable way. https://gitlab.common-lisp.net/gendl/gendl/-/issues/131Various package-related build failures recently2015-03-31T02:17:20ZDave CooperVarious package-related build failures recently*Created by: quicklisp*
Here are some failures I've gotten recently for a few GDL systems:
::: genworks-gdl from git://github.com/genworks/Genworks-GDL.git
=================================
FAIL: "fail_genworks-gdl_gdl-aer...*Created by: quicklisp*
Here are some failures I've gotten recently for a few GDL systems:
::: genworks-gdl from git://github.com/genworks/Genworks-GDL.git
=================================
FAIL: "fail_genworks-gdl_gdl-aero-demo-1_gdl-aero-demo-1.txt"
=================================
unhandled LOAD-SYSTEM-DEFINITION-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {10030C13C3}>: Error while trying to load definition for system gdl-surf from pathname /home/xach/quicklisp-controller/dist/build-cache/genworks-gdl/8e28990e4d68d2512cddc755e8e165001dd3104e/genworks-gdl-20120807-git/surf/gdl-surf.asd: don't recognize component type LISP
=================================
FAIL: "fail_genworks-gdl_gdl-build_gdl-build.txt"
=================================
unhandled SB-KERNEL:SIMPLE-PACKAGE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {10030C1363}>: The name "GDL-USER" does not designate any package.
=================================
FAIL: "fail_genworks-gdl_gdl-translators_gdl-translators.txt"
=================================
;
; caught ERROR:
; READ error during COMPILE-FILE: Package GWL does not exist.Line: 23, Column: 19, File-Position: 877Stream: #<SB-SYS:FD-STREAM for "file /home/xach/quicklisp-controller/dist/build-cache/genworks-gdl/8e28990e4d68d2512cddc755e8e165001dd3104e/genworks-gdl-20120807-git/gdl/apps/translators/xml/source/package.lisp" {1004A47B13}>
=================================
FAIL: "fail_genworks-gdl_gdl-wind-demo-1_gdl-wind-demo-1.txt"
=================================
unhandled SB-KERNEL:SIMPLE-PACKAGE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {10030C13C3}>: The name "GDL-USER" does not designate any package.
=================================
FAIL: "fail_genworks-gdl_gdl-xml_gdl-xml.txt"
=================================
;
; caught ERROR:
; READ error during COMPILE-FILE: Package GWL does not exist.Line: 23, Column: 19, File-Position: 877Stream: #<SB-SYS:FD-STREAM for "file /home/xach/quicklisp-controller/dist/build-cache/genworks-gdl/8e28990e4d68d2512cddc755e8e165001dd3104e/genworks-gdl-20120807-git/gdl/apps/translators/xml/source/package.lisp" {1004A3DBD3}>
I'm using a recent SBCL on AMD64.
**Imported comments:**
*By genworks on 2012-09-10 02:05:08 UTC*
Thank you for the report. These failed .asd files have been either removed (as unecessary) or fixed up with correct dependencies. I don't see any other obvious failure candidates, but if there are any please let me know and I will try to jump on them right away.
I know we still have a slew of style-warnings to clean up.