On 3/20/07, Dan Bron <[EMAIL PROTECTED]> wrote:
I would additional alternative constructors for your object:
I shouldn't take credit for the design -- : Alexander Rufon did
(and probably Oleg) did the heavy lifting here. Also, I noticed
that I gave the wrong link into the wiki -- I got this from
http://www.jsoftware.com/jwiki/Guides/J_CSharp
(A) one that does NOT show the J session manager window
( i.e. _jObject.Show(0) ) and
Anyways, the session manager window is not brought up
if a false parameter is passed to the constructor. Only when
that debug parameter is true do you get a session manager
window.
(B) one that invokes JDLLServer instead of JEXEServer
for applications that require a smaller footprint
and less complexity and do not need the services
provided by the JFE. And, possibly,
That's an interesting thought. I've not explored it and do
not know what the implications would be. That said, I'm
not sure that the difference in footprint is all that significant.
(C) A debugging constructor that invokes the JEXEServer
shows the window, logs, and sets debug (with
dbr 1[load'debug' and possibly sets latent debug
expression with 13!:15 )
The current constructor does all this except possibly "logs".
(It does not implicitly write a log to a file, if that's what you
mean by "logs". However, it's easy enough for the session
manager to save its log to a file, if you don't mind that as
an explicit step.)
Thanks for thinking about this. And I apologize for the bad
link.
Thanks again,
--
Raul
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
