What worried me and prompted writing was Eric's message saying that JavaScript was a good way to make J web aware. I agree; however, you can't just use JavaScript. In order to do the job you need HTML and all the other goodies to do the job. When I last did projects for customers most of my time was spent on the customer interface. Little time on the actual application part. If the customer interface is JavaScript, then what is the advantage in using J? Writing in a more common language, though may take a little longer than in J saves little and sounds better when selling. The whole development process needs speeding up.
On Thu, Sep 2, 2010 at 12:34 PM, Raul Miller <[email protected]> wrote: > On Thu, Sep 2, 2010 at 11:53 AM, Don Guinn <[email protected]> wrote: > > use. The wd interface, though restrictive, was portable and not hard to > > learn. I hope that the released J7 can retain some of this ability for > one > > to concentrate on the problem at hand and not require large amounts of > time > > and resources getting the presentation to the user right. > > A subset of wd should be doable, for jhs. > > That said, tracking the changes that are going on here, and > being productive with the beta system despite its current > omissions takes a fair amount of energy. > > Personally, I have only had a little bit of time to work with > jhs and am sticking with j6 until j7 gets closer to release > freeze. > > -- > Raul > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
