> From: Henry Rich > Sent: Wednesday, 9 June 2010 13:31 > > I have been following the exploits of you pioneers with great interest. > > I could try to be a second-generation pioneer, but only if I can get > forms to work. I have a great many apps in J, but they all use forms. > > Reading the Wiki I can't tell whether my forms will come up. > > Will they?
The current betas do not use wd and therefore any commands (including displaying old-style J forms) won't work. AFAIU there is a JFE (J front end) planned for j701 that will support "legacy" gui code (wd), but it isn't available yet. > If not, is there some plan for migrating forms to GTK? Not sure, but I imagine that if it exists it is a way off yet. (I see Bill has replied with some more concrete info about what would be involved). There has been talk about the benefits of a JFE-independent gui language. That is, a gui description "language" used to generate the actual gui code (GTK, wd, HTML ...) required by the current JFE. That way we can (continue to) have "write once" code that will work on all platforms and front ends. AFAIK there has not been any work on this and it probably needs to wait until after the Gtk and JHS gui's have solidified anyway. > Second question: is the idea that Web pages can have J scrips in the > same way they now have Java scripts? What user action would be needed > to download minimal J to allow such pages to run? I have an app that > could use this functionality. As I see it there are two likely scenarios. A) User browses to a web page that happens to be hosted by JHS and the interaction of the user with the application on the page is via javascript on the page and J scripts in backend server. They are not aware of the role of J on their computer and no J code executes on their computer. B) Application creator makes download available that consists of J scripts/HTML/CSS/Javascript. The user installs & clicks on shortcut that opens up application as a page(s) in the user's browser. In this scenario the user would also have had to download and install J (with the JHS front end). Ideally they would only have to do this once for all apps that they are likely to install (sort of like Java VM runtime), but if it is not easy for apps to "share" a common installation, then it might be bundled with each app. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
