Custom Query (1030 matches)

Looking at init-cocoa-application it would seem that the intent there is to permit the use of a CCLDelegateClass attribute in the Info.plist as a way to set a different Application delegate class. This would be very convenient. Unfortunately if you do that, the delegate is then RESET in start-cocoa-application (after the call to init-cocoa-application). Although start-cocoa-application has a parameter that allows overriding of the default application delegate, using it would require also providing a new top-level function, which isn't as convenient. The setting of the app delegate in start-cocoa-application should be conditionalized by the non-existence of a current app delegate.

I suggest changing the code:

(when application-proxy-class-name ...)

in start-cocoa-application to :

(when (and application-proxy-class-name

(%null-ptr-p (#/delegate *NSApp*))) ...)

This would permit setting an application delegate either by using the Info.plist setting as described above or by specifying an application delegate in the main nib file that is set when that is loaded. Although I could do a bunch of work to work around this, I hope this change can be made fairly quickly.

If the CCL IDE bundle is moved out of the CCL directory and executed, certain functions will fail (e.g. just do #&NSApp in the listener and see what happens). This is because the ccl: logical translation no longer points to the CCL directory, but rather to whatever directory the bundle is in. This is set by the init-ccl-directory-for-ide function. This could also be a problem for any saved applications depending on what they do. There are various ways this could be addressed: 1) add a new value into the Info.plist identifying the CCL directory and use it to initialize the ccl: translation 2) Modify init-ccl-directory-for-ide to search for the right directory 3) create a physical link to the CCL directory in the bundle somewhere and use that as the translation for the ccl: logical directory, 4) add a user preference that identifies where the CCL directory is and use that to initialize the translation. I prefer #4 because it is easier to change if the bundle is moved to a different machine or if the CCL directory is moved at some point. #2 is intriguing but depending on how the search is done, could take a significant amount of time. So I am requesting an enhancement to the IDE that adds a preference item identifying the CCL directory. It should default to the value currently used. In the meantime I will assure that applications that my tools generate will reset the logical translation in some way.

I believe there is a typo in the (define-character-encoding :utf-32 ...) form in l1-unicode.lisp. Within it you find:

  :stream-encode-function
  #+ucs-4-stream-encode   <=== should be #' not #+
  :stream-decode-function
  #'ucs-4-stream-decode
  :vector-encode-function

I suspect there aren't many files in utf-32 format.