> From: Joey K Tuttle <[email protected]>
>
> I meant I use SSH for a shell session to do sysadmin types of
> activities. The ability to demo j is a bonus. I agree that a browser
> style of interface would be better to work with and demo j.
Not just demo, but actually creating snippets of code and adding
them to a remote workspace. Possibly building app-style modules
with controls, graphics, etc.
> I also agree with other posters that the limitations on iPhone
> keyboards would make any actual development work painful and
> frustrating at best...
The judgment about iPhone keyboard is subjective. Some people find
the small getting-used-to a fair trade off to lugging the extra
weight and handling of a mechanical keyboard. Back in the day when
Pocket PC was hot, I tried strap-on keyboards, but fiddling with the
puny keys was so inferior to just tapping the soft keyboard with
a stylus. And multi-touch is a step-up from stylus.
OS 3 has voice over. So maybe there's gonna be a talking input
soon. So that you could program J hand-free while driving ...
or riding. :)
> At 16:13 -0700 2009/07/03, Oleg Kobchenko wrote:
> > > From: Joey K Tuttle
> >
> >>
> >> Following this with interest - even though I use iPod Touch instead
> >> of iPhone, I find lots of good/available WiFi access. I bought iSSH
> >>
> >> In general, the most attractive advantage of an SSH terminal solution
> >> over a browser based interface is secure access to the server. (And
> >
> >There's HTTPS, which I believe is based on the same SSL as SSH.
> >(Secure Socket Layer.)
> >
> >> my general preference for jconsole with its excellent session memory
> >> :)
> >>
> >> I do think a good/clever browser interface could be very pretty and
> >> useful on the iPod/iPhone - certainly the addition of cut/paste in
> >> iP...V3 devices provides a nice improvement. An advantage would be
> >> easier, more flexible, graphic display than trying to use an Xterm
> >> server/client interface. PDFs display very nicely on iP... devices.
> >
> >Browser would allow richer UI with controls to edit, test, re-use the
> >code, so that there is less typing than in console. For example, instead
> >of typing names 6, names_x_'' etc to browse there would be buttons or
> >menus to explore locales, values, and do other housekeeping tasks.
> >
> >In fact, I am thinking that maybe instead of shell interface, it would
> >be better to have a SmallTalk interface with Object Browser so you keep
> >all visual and browsable and only enter editing mode to make changes.
> >
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
