Mike,
Your demo works flawlessly for me. I am impressed
when anyone outside of Apple can develop a Mac Cocoa
application work. Thank you very much for contributing your
application to the wiki.
I noticed two things regarding the input field.
a A result is always produced. For example if I enter
"k =: 100" I see the 100 output as if I had typed
"]k =: 100". Is this intentional, or was it just easier to
do than eliminating the output?
b Only single line inputs are permitted so multiple
line noun, verb, ... definitions must be loaded from a
file, not the input field.
I also noticed that J 'load' and 'require' sentences
in scripts do not work. Am I doing something wrong, or is
that not implemented? I assume this is what you mean in your
description below about the system being able to
+ * find the path to a script located within the application bundle;
The Menu: File|New File can go outside the application
bundle, but the J scripts themselves cannot.
I don't understand what you mean by this feature.
+ application is standalone and does not require J to be installed on
+ your system.
Where else could J be installed? On an intranet?
Forgive my naivete, but is the main purpose of such
a client/server application to deliver a J application
to a client for whom you wish to limit the access to J
itself and provide only a gui interface -- webpage-like --
to the client, not the whole J system (like Alex Rufon's
J_CSharp application with .NET)?
On Tue, 10 Apr 2007, Mike Powell wrote:
+ For those with an interest in J on the Mac platform, I have placed a
+ sample application on the J Wiki. You can find this on
the Guides/
+ Interfaces page. From the Wiki page:
+
+ "This is a simple example of a Mac application acting as a client to
+ a J server. The functionality provided is elementary; a browser
+ window to monitor objects in the various locales of the running J
+ task; an input field for sending expressions to the J task; and a log
+ of the session inputs and results.
+
+ The client side is written in Objective C drawing on objects from the
+ Cocoa Framework. The server is the J engine, accessed through the
+ functions provided in the J dynamic library (libj601.dylib). The
+ application is standalone and does not require J to be installed on
+ your system.
+
+ Although the application is rudimentary, the source code demonstrates
+ how to do the following from within Objective C:
+
+ * link to the functions in the J dynamic library;
+ * start a J task;
+ * convert a J object given in 3!:1 format into C data;
+ * find the path to a script located within the application bundle;
+ * use release and retain to manage memory; and
+ * use Cocoa objects, such as a table, text field, pop-up and text
+ storage.
+
+ The source code is provided along with a commentary."
+ ----------------------------------------------------------------------
+ For information about J forums see http://www.jsoftware.com/forums.htm
+
(B=)
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
