Although the Qt layouts make it more straightforward to generate forms by hand, I've found it useful to add a test function to the script to make sure I'm on the right track. That way I can separate the initialization logic that is usually in the run function. For example:
coclass'example' EXAMPLE=: 0 : 0 rem form definition ) test=: 3 : 0 wd EXAMPLE wd'pshow' ) Running test_example_ in the terminal brings up the form and if need be I can go back and adjust the form definition. The usual run or create function contains all of the necessary logic to actually use the form. Although the above is probably obvious, once I started using this approach, building forms was much quicker and I stopped missing the form editor. On Mar 15, 2013, at 5:09 PM, chris burke <[email protected]> wrote: > J8 does support wd and will continue to do so. The format is similar but > not identical to J6. > > We haven't bothered with the GUI design tool yet. In J6 and earlier, > controls had exact xywh positioning which is tedious to get right manually, > hence the need for a form editor. J8 uses Qt layouts which are automatic, > so a form editor is not so essential. > > One possibility is that the output from Qt Creator could be read into a J8 > wd form definition. But you should find that it is easy enough to create J8 > forms manually. > > On Sat, Mar 16, 2013 at 2:45 AM, McGuinness, Brian > > <[email protected]> wrote: > >> ...If J8 continues to support wd and the GUI design tool, >> and these work on 64-bit platforms, then I will >> seriously consider writing GUI-based applications >> in J once again. But I'm not interested in playing >> a constant game of catch-up with an ever-changing >> platform, and I'm sure most other people feel the >> same way. > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
