gmane.lisp.lispworks.general

Re: [announce] LispWorks Project Generator

Camille Troillard — 2013-06-17T17:59:57

Hi Robert,

Thank you for your feedback.

I was looking for something more focused on LispWorks as most of the interesting bits are not handled by those generators especially when you are looking for "delivered" product distribution.


Best,
Cam


On 17 juin 2013, at 19:46, Robert Smith <quad< at >symbo1ics.com> wrote:


_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug< at >lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: [announce] LispWorks Project Generator

Robert Smith — 2013-06-17T17:46:40

Hello Camille:

I just wanted to let you know about the portable project generators
(so not LispWorks specific):

Quickproject by Zach Beane: https://github.com/xach/quickproject

CL-PROJECT by Eitarow Fukamachi: https://github.com/fukamachi/cl-project

None of these, of course, do anything with CAPI.

I will try to give yours a try soon and let you know.

Cheers,

Robert

On Mon, Jun 17, 2013 at 10:12 AM, Camille Troillard
<camille< at >osculator.net> wrote:

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug< at >lispworks.com
http://www.lispworks.com/support/lisp-hug.html

[announce] LispWorks Project Generator

Camille Troillard — 2013-06-17T17:12:22

Hello,

I realized I was doing the same task every time I wanted to build a small or large application, command-line or CAPI based.  Based on the experience I gathered from this list, LispWorks examples and the reference manuals, I have created a small project generator that I hope will come useful.

    https://github.com/tuscland/lw-project-generator


Basically, creating a CAPI project with delivery and Git repository boils down to:

    (project-generator:run "COM.WILDORA.MY-APP" "My App")


I will be glad to receive your feedback and contributions, I'm sure there many dark corners not yet explored.

Please note that I have been not able to test this fully other than Mac OS X.  As an owner of LW for Windows, I will make sure in the future it works that platform too.

Thanks!


Best Regards,
Camille


_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug< at >lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: LispWorks architecture?

Camille Troillard — 2013-06-14T17:03:28

Hi Jeff,

On 14 juin 2013, at 18:51, Jeff Massung <massung< at >gmail.com> wrote:


I was looking for the architecture for which LW has been compiled, not the one of the machine it is running on.


_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug< at >lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: LispWorks architecture?

Jeff Massung — 2013-06-14T16:51:38

Just because - to me - the original question was a bit ambiguous (and it
might affect the solution). Do you want to know the machine architecture
regardless of the LW running on it or the architecture of LW?

For example, you could be running on an AMD64 processor with a professional
LW image (32-bit). In such an instance, would you like to know that the
architecture is 64 or 32 bit?

Jeff M.


On Fri, Jun 14, 2013 at 11:42 AM, Camille Troillard
<camille< at >osculator.net>wrote:

Re: LispWorks architecture?

Camille Troillard — 2013-06-14T16:42:58


On 14 juin 2013, at 18:39, Dave Fox <davef< at >lispworks.com> wrote:


Thank you Dave.

I was trying to avoid this, though I understand it is not such a problem since it does not change so often.


_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug< at >lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: LispWorks architecture?

Dave Fox — 2013-06-14T16:39:10


You can consult the documentation for *features* at

 http://www.lispworks.com/documentation/lw61/LW/html/lw-646.htm

and then write something like:

(defun architecture ()
       #+:x86 "i386"
       #+:x64 "X64"
       #-(or :x86 :x64) "unknown")

Re: Problems with LWM 6.0 and "Mountain Lion"?

Camille Troillard — 2013-06-14T12:30:32

Hi Pascal,


On 14 juin 2013, at 14:22, Pascal Costanza <pc< at >p-cos.net> wrote:


I don't recommend using this setting which lowers the security of your Mac.

To open an application that was not signed, right click on the icon and choose Open.  You will be prompted with a confirmation dialog that will be displayed only once on the first launch.


Best,
Camille


_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug< at >lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: Problems with LWM 6.0 and "Mountain Lion"?

Pascal Costanza — 2013-06-14T12:22:32

Hi,

Please check the security settings of your Mac: System Preferences - Security & Privacy - General - Allow applications downloaded from - Anywhere.

If this is set to "Mac App Store and identified developers" instead of "Anywhere," there may be problems, if I recall correctly.

Pascal

On 13 Jun 2013, at 21:19, Edi Weitz <edi< at >weitz.de> wrote:


--
Pascal Costanza




_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug< at >lispworks.com
http://www.lispworks.com/support/lisp-hug.html

LispWorks architecture?

Camille Troillard — 2013-06-14T11:10:25

Hello,

How do I get the architecture LispWorks has been compiled for?

I would prefer to call a specific function rather than poking in the *features*.

None of these give me the correct answer, I am looking for X64 or i386, or something like that:

CL-USER 169 > (machine-instance)
"tortilla.local"

CL-USER 170 > (machine-type)
"x86"

CL-USER 171 > (machine-version)
"486"

CL-USER 172 > (software-type)
"Darwin"

CL-USER 173 > (software-version)
"12.4.0"

CL-USER 174 > (lisp-image-name)
"/Applications/LispWorks 6.1 (64-bit)/LispWorks (64-bit).app/Contents/MacOS/lispworks-6-1-0-macos64-universal"

CL-USER 175 > (lisp-implementation-type)
"LispWorks"

CL-USER 176 > (lisp-implementation-version)
"6.1.1"


Best,
Camille


_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug< at >lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: Load images in dialog

Martin Simmons — 2013-06-14T10:00:27


You could try the :create-callback of the dialog interface or the
:create-callback of the output-pane.

Re: capi interfaces as actors

Martin Simmons — 2013-06-14T09:55:54


I recommend staying with your current model, because interfaces are *not*
equivalent to processes in the CAPI model.  E.g. as Cam mentioned, they all
run in one process on the Mac due to limitations of Cocoa.

Re: Problems with LWM 6.0 and "Mountain Lion"?

Camille Troillard — 2013-06-14T08:30:53

I confirm that did not have significant problems with LW 6 on Mountain Lion.
The issues I had were minor and mostly cosmetic.

On 14 juin 2013, at 10:20, David Johnson-Davies <david< at >interface.co.uk> wrote:



_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug< at >lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: Problems with LWM 6.0 and "Mountain Lion"?

Espen Vestre — 2013-06-14T08:21:49

Espen Vestre <ev< at >netfonds.no> writes:


On the other hand - come to think of it - I haven't had any reports at
all that customers have problems running PrimeTrader on Mountain
Lion. It also works fine on my laptop. So while I didn't get LW 6 to
work, my own builds done with LW 6 seem to work fine. 

And I just had a look at which version of PrimeTrader customers with
Mountain Lion are running, and a surprising number of them are even
running a 2010 edition of PrimeTrader built with LW 5.1.2!

Re: Problems with LWM 6.0 and "Mountain Lion"?

Espen Vestre — 2013-06-14T08:23:32

David Johnson-Davies <david< at >interface.co.uk> writes:


I know, but I still had issues, and eventually gave up.

(The gatekeeper comment was mainly a reminder that you may want to sign
distributed delivered executables)

Re: Problems with LWM 6.0 and "Mountain Lion"?

David Johnson-Davies — 2013-06-14T08:20:02

In reply to:


I'd just like to report that I've been running Lispworks 6.0.1 fine on Mountain Lion 10.8.3 since it was released, with no problems.


This is easily solved by control-clicking the LispWorks app and choosing "Open" from the contextual menu. At the dialog box:

"LispWorks" is from an unidentified developer. Are you sure you want to open it?

click the Open button.

David Johnson-Davies

+------------------------------------------------------------+
David Johnson-Davies, Human-Computer Interface Ltd
17 Signet Court, Swanns Road, Cambridge, CB5 8LA, England.

Tel: +44 1223 314934, Fax: +44 1223 462562
Email: david< at >interface.co.uk, Web: http://www.interface.co.uk/
+------------------------------------------------------------+


_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug< at >lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: Problems with LWM 6.0 and "Mountain Lion"?

Espen Vestre — 2013-06-14T07:49:36

Edi Weitz <edi< at >weitz.de> writes:


I didn't get LW6 to work at all on my new laptop which came with
Mountain Lion 4 months ago, which was somewhat frustrating since I
hadn't moved to LW6.1 yet at that time.

So yes, there are definitely some issues.

(In addition to the fact that LW 6 seems to work poorly or not at all on
Mountain Lion, there's also the issue of gatekeeper requiring signed
applications. Fortunately, that's easily solved as long as you're a
registered Mac developer and have the right certificates.)

Re: capi interfaces as actors

Camille Troillard — 2013-06-14T05:47:51

Hello,

I know that on OS X, the main processes's mailbox processes its events, meaning that you can send messages to it through its mailbox and they will applied at some point in the future.

On the Mac, to access the "GUI process", use MP:*MAIN-PROCESS*.
On Windows, I would try (MP:GET-CURRENT-PROCESS) since every interfaces have a different process (unlike Cocoa).

Then you can use this mailbox as a reply handler and pass it to another interface so they communicate together.


Best,
Cam



On 14 juin 2013, at 03:56, Madhu <enometh< at >meer.net> wrote:



_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug< at >lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: capi interfaces as actors

Madhu — 2013-06-14T01:56:27


* Paul Tarvydas <51BA5EC9.90904< at >gmail.com> :
Wrote on Thu, 13 Jun 2013 20:07:37 -0400:

| Given that interfaces are themselves processes, can I do all of this
| without creating the second set of processes?
|
| Most of the interfaces need to display themselves, then call
| mp:mailbox-wait-for-event on their mailbox.  I haven't figured out how
| to do this using only the interfaces' processes (it may very well be
| that I'm missing something obvious).  Any ideas would be welcome.

Hello, This seems to be the flip side of the of "reactive" problem coin
I faced, and mentioned on here on Aug 30 2011, in
<permalink.gmane.org/gmane.lisp.lispworks.general/11216>

I had wished for some way to hook in to the interface's process, a hook
that would get run at some point in the gui loop, where you could run
your code thunks here.  Would the availability of such a mechanism help
your problem?  [I still haven't solved that problem] --- Madhu

_______________________________________________
Lisp Hug - the mailing list fo

capi interfaces as actors

Paul Tarvydas — 2013-06-14T00:07:37

I have a handful of capi interfaces and I need them to communicate 
through mp:mailboxes to each other, like GUI actors.

At present, I create a second process for each interface which runs the 
"actor" code and calls capi:apply-in-pane-process to update the interfaces.

Given that interfaces are themselves processes, can I do all of this 
without creating the second set of processes?

Most of the interfaces need to display themselves, then call 
mp:mailbox-wait-for-event on their mailbox.  I haven't figured out how 
to do this using only the interfaces' processes (it may very well be 
that I'm missing something obvious).  Any ideas would be welcome.

thanks
pt

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug< at >lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: Non-blocking read of serial device

Camille Troillard — 2013-06-13T21:17:26

I found a solution, thanks to this discussion about Clozure CL:

    http://clozure.com/pipermail/openmcl-devel/2012-November/013904.html

The important fact seems to be:


Assuming it also applies for LispWorks and OS X.
Based on this, instead of using OPEN, I used: (SYS:OPEN-PIPE "cat /dev/cu.usbmodem8931" :buffered nil)
And I can now safely use LISTEN within the process wait function.

Best,
Cam


(defvar *device-path* "/dev/cu.usbmodem8931")

(defun serial-loop (stream)
  (mp:ensure-process-cleanup `(serial-cleanup ,stream))
  (loop :do
        (when (mp:wait-processing-events 100
                                         :wait-function #'listen
                                         :wait-args (list stream))
          (with-simple-restart (abort "Return to event loop.")
            (let ((byte (read-byte stream)))
               (packet (funcall decoder byte)))))))


(defvar *process* nil)

(defun serial-cleanup (process stream)
  (close stream)
  (setf *process* nil))

(defun serial-start (&optional