calm,vitovan

Normalization of `calm` commands

I propose the following changes in CALM:

Make all user-related calm command on Windows Bash-free

Windows users don't deserve the torment of Bash, they should suffer CMD or Powershell.

If this were done, the sh folder could be renamed to s (as script).
Organise the current calm command into the following form:

calm s

Running internal scripts, this should not be exposed to the end-user, but should not prevent anyone using them either. But they are meant to be changed at anytime.
calm publish

Publish the current CALM project into a fancy distributable package, i.e. AppImage / macOS Application inside DMG / Windows Installer
calm share

Share the current CALM project as an ZIP file, with the following 2 options
- calm share with no more arguments
  
  Generate *.calm file, it is actually just an ZIP file packed with canvas.lisp and assets + src directory if they exist alongside with canvas.lisp.
  
  This file should be easily opened on any CALM installed machine, there should be file-type associations if the OS has that kind of support.
- ~~calm share --with-runtime~~
  
  This command will generate an ZIP file contains all the 3rd party dependencies and a pre-dumped CALM image (from the sample application, without loading the current canvas.lisp). A warning should be shown to the user to inform that to make this method working, Quicklisp or any other 3rd party dependencies should not be used.

Except calm s, all the other end-user commands could be provided with an interactive shell, i.e. ask questions like 'What's the name of your app?'

Can we use CALM in web browser?

It takes too much time to start by the first time

There should be at least some prompt tips?

the 0.1.1 meditator does not have sound

https://vitovan.com/calm/examples-0.1.1/meditator/calm.html

Meditator building needs:

export REBUILD_WASM_P=yes

since it requires extra files to be packed.

use SDL_HINT instead of FLAGS

The current implementation:

calm/src/config.lisp

Lines 9 to 15 in 94e45f9

    
           (defparameter *calm-window-flags* '(:shown :allow-highdpi)) 
        
           ;; 
        
           ;; use OpenGL on Linux to avoid weird window flashing: (like it was closed and then opened again) 
        
           ;; 
        
           #+linux 
        
           (push :opengl *calm-window-flags*)

Could be replaced by:

https://wiki.libsdl.org/SDL2/SDL_SetHint
https://wiki.libsdl.org/SDL2/CategoryHints
https://wiki.libsdl.org/SDL2/SDL_HINT_RENDER_DRIVER

Quicklisp installation?

I see CALM recently got added to QuickLisp (in the october release).

While the calm CLI obviously wouldn't be added to the path (unless added programmatically via eg uiop calling shell commands), is the Quicklisp distribution otherwise usable? And if so can we add a note in the README so that people know it's an option?

CALM 0.1.4 on Windows failed to publish usable application

0.1.3...0.1.4#diff-450217fafb1125c6c1048da28e4a126ddcbb193d560fec8ee7167137c6daea86

Because I accidentally deleted calmNoConsole.exe.

Damn!

Wrong download link in README for Windows auto install

It takes very long time when start CALM from the home directory

If we start CALM command inside $HOME directory, the font-config will search for all the fonts inside this directory recursively, that will cause huge pain to the developers.

Should delete the following line:

calm/s/usr/all/fonts.conf

Lines 18 to 19 in ff4c42b

    
           <!-- program running dir --> 
        
           <dir prefix="cwd">./</dir>

`calm core` generated calm.core in the current folder instead of the CALM_DIR

Linux AppImage does not have an icon while running (left up corner)

Install failure on windows 10

OS: Windows 10

What I did:

Overcame windows defender warning
Extracting calm.zip and moved calm directory to C:\calm .
Added Path
Opening windows terminal and typed calm.exe
Installation starts, and stops with an error

Error opening shared object "SDL2_image.dll":
The specified procedure could not be found.

I ensured the dll's are present

C:\calm\lib\SDL2.dll
C:\calm\lib\SDL2_image.dll
C:\calm\lib\SDL2_mixer.dll

Here is the "complete" powershell output

LIB_PATH=C:\calm\lib
LIB_ENV=C:\calm;C:\calm\lib
CALM_CMD=core
inherited CALM_APP_DIR=C:\Users\sgraetz\
inherited CALM_HOME=C:\calm\
SBCL_HOME=C:\calm\sbcl\lib\sbcl
PATH=C:\calm;C:\calm\lib
EXECUTING:  "C:\calm\sbcl\bin\sbcl" --noinform --no-sysinit --no-userinit --load entry.lisp
To load "calm":
  Load 1 ASDF system:
    calm
; Loading "calm"
.....................While evaluating the form starting at line 8, column 0
  of #P"C:/calm/entry.lisp":

debugger invoked on a CFFI:LOAD-FOREIGN-LIBRARY-ERROR in thread
#<THREAD "main thread" RUNNING {10044B8113}>:
  Unable to load foreign library (LIBSDL2-IMAGE).
  Error opening shared object "SDL2_image.dll":
 The specified procedure could not be found.

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [RETRY                        ] Try loading the foreign library again.
  1: [USE-VALUE                    ] Use another library instead.
  2: [TRY-RECOMPILING              ] Recompile library and try loading it again
  3: [RETRY                        ] Retry
                                     loading FASL for #<CL-SOURCE-FILE "sdl2-image" "library">.
  4: [ACCEPT                       ] Continue, treating
                                     loading FASL for #<CL-SOURCE-FILE "sdl2-image" "library">
                                     as having been successful.
  5:                                 Retry ASDF operation.
  6: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the
                                     configuration.
  7:                                 Retry ASDF operation.
  8:                                 Retry ASDF operation after resetting the
                                     configuration.
  9: [ABORT                        ] Give up on "calm"
 10: [REGISTER-LOCAL-PROJECTS      ] Register local projects and try again.
 11: [RETRY                        ] Retry EVAL of current toplevel form.
 12: [CONTINUE                     ] Ignore error and continue loading file "C:\\calm\\entry.lisp".
 13:                                 Abort loading file "C:\\calm\\entry.lisp".
 14:                                 Ignore runtime option --load "entry.lisp".
 15:                                 Skip rest of --eval and --load options.
 16:                                 Skip to toplevel READ/EVAL/PRINT loop.
 17: [EXIT                         ] Exit SBCL (calling #'EXIT, killing the process).

(CFFI::FL-ERROR "Unable to load foreign library (~A).~%  ~A" LIBSDL2-IMAGE "Error opening shared object \"SDL2_image.dll\":
 The specified procedure could not be found.")
   source: (ERROR 'LOAD-FOREIGN-LIBRARY-ERROR :FORMAT-CONTROL CONTROL
                  :FORMAT-ARGUMENTS ARGUMENTS)
0]

Lisp code not compiling on ECL

#70

This could be easily improved, and need to be improved at a higher priority.

Since our first CALM friend @Hellseher mentioned it.

the zip version of CALM would require 1000+ steps to bypass apple's security measure

cannot be opened because the developer cannot be verified.
cannot be opened because the developer cannot be verified.
cannot be opened because the developer cannot be verified.
cannot be opened because the developer cannot be verified.
cannot be opened because the developer cannot be verified.
cannot be opened because the developer cannot be verified.
cannot be opened because the developer cannot be verified.
cannot be opened because the developer cannot be verified.
cannot be opened because the developer cannot be verified.
cannot be opened because the developer cannot be verified.
cannot be opened because the developer cannot be verified.
cannot be opened because the developer cannot be verified.
cannot be opened because the developer cannot be verified.

Maybe an app bundle could reduce 1000 to 1.

The compilation of SBCL with compression takes too much time

While running github workflow, it will take about 7 minutes, and github won't cache this for TAG triggered builds.

We might need a precompiled SBCL with compression for Windows, maybe this could also benefit Linux as well.

Could be related to #21

CALM sometimes refuses to start

The reason is not yet clear, maybe it's caused by the upgrade of Quicklisp or SBCL.

It has been solved by the following approach:

rm /Applications/Calm.app/Contents/MacOS/calm.core
rm -rf ~/.cache/common-lisp/sbcl-2.3.*

We could write this in the document, or provide some mechanism to prevent this?

Add icon to Windows CALM Application

This might be achieved by modifying the icon of SBCL

Can't have white-space in the path of CALM

~/Downloads/calm-dmg/Calm - CALM/Calm.app/Contents/MacOS $ ./calm
CALM_CMD=show
APP_DIR=/Users/vito/Downloads/calm-dmg/Calm - CALM/Calm.app/Contents/MacOS/
CALM_DIR=/Users/vito/Downloads/calm-dmg/Calm - CALM/Calm.app/Contents/MacOS/
SBCL_HOME=/Users/vito/Downloads/calm-dmg/Calm - CALM/Calm.app/Contents/MacOS/sbcl/lib/sbcl
LIB_PATH=/Users/vito/Downloads/calm-dmg/Calm - CALM/Calm.app/Contents/MacOS/lib
EXECUTING: DYLD_FALLBACK_LIBRARY_PATH="/Users/vito/Downloads/calm-dmg/Calm - CALM/Calm.app/Contents/MacOS/lib" /Users/vito/Downloads/calm-dmg/Calm - CALM/Calm.app/Contents/MacOS/sbcl/bin/sbcl --no-sysinit --no-userinit --load entry.lisp
sh: /Users/vito/Downloads/calm-dmg/Calm: No such file or directory

Windows file name
Linux AppImage name
macOS APP name inside DMG

create-dmg --skip-jenkins ...

We do not call any apple scripts to beautify the dmg, because of actions/runner-images#7531

We should keep this issue open until it was fixed on github side.

I think glibc 2.33 would do the job.

get rid of the ugly bash scripts
Windows user may not need to install msys2 at all

and this may also fix #17

Propose a new command `calm alive`

To support the Visual Studio extension Alive

I still can't find any other suitable editor for Lisp newcomers.

Lem is too hard to install, Emacs is too intimidating.

Canvas Aided Lisp Magic: Create canvas-based applications with Lisp and distribute them on Linux, macOS, Windows, and the web.

Another version is:

A Lisp development environment that enables you to build and distribute canvas based applications as Linux AppImage, macOS Application Bundle, Windows Installer and Web Application.

Which one do you prefer?

@eltociear

Fontconfig warning: "/Users/vito/Downloads/hello/fonts/fonts.conf", line 19: Use of ambiguous path in <dir> element. please add prefix="cwd" if current behavior is desired.

calm/s/usr/all/fonts.conf

Line 19 in 452e851

<dir>C:\Windows\Fonts</dir>

(in-package #:calm)

It should be something like:

(in-package #:calm-user)

User code should be at user-space level, this also could avoid the WARNINGs about redefining functions.

sbcl
all dependencies: sdl2, sdl2_mixer, cairo, zlib, etc ...
pre-installed Quicklisp
calm
rcedit
appimagetool
create-dmg
calm-zipper

Should not assume that every computer has audio devices

The CALM Application will hang if there is no audio device.

AppImage/appimage.github.io#3178

AppImage/appimage.github.io#3179

Add script to build Linux AppImage

Related: #18

	(defparameter calm-window-flags '(:shown :allow-highdpi))

	;;
	;; use OpenGL on Linux to avoid weird window flashing: (like it was closed and then opened again)
	;;
	#+linux
	(push :opengl calm-window-flags)

vitovan / calm Goto Github PK

calm's Introduction

Source of https://sdf.org/~vito/

calm's People

Contributors

Stargazers

Watchers

Forkers

calm's Issues

Maybe an app bundle could reduce 1000 to 1.

Recommend Projects

Recommend Topics

Recommend Org