2006/12/25, Chris Burke <[EMAIL PROTECTED]>:
Dan Bron wrote:
> ...
> If I were to do GUIs with J (I don't), I'd avoid wd altogether. If I
didn't have to create standalone executables for client machines, I'd use
XHTML+CSS+CGI; maybe Oleg's JHP. If I didn't have that option, I'd create a GUI
in C# and load J through COM.
wd works pretty well for most applications. If you need a very
sophisticated front end, then it makes sense to use tools like C#, but
if all you want are standard forms (and you say that you would use
XHTML+CSS+CGI or JHP), then wd is fine.
There would be no problem in running a J app in one task, and a J wd in
another that monitored the first task.
What does that mean? Are those two seperate and concurrent? Are you
mentioning event handlers(I don't think this one runs concurrent
though)?
Also, the user manual recommendation is specifically intended for
"long-running sentences". Most apps don't have this, and need only a
single J task.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm