Hi,
Funny thing. Last night I also changed the TUI code to include JLine support.
It only supports history and command name completion, but it can
handle non standard commands.
It doesn't support argument completion because for that it's required
to parse the command usage,
and it's not guaranteed that everyone follows the same convention.
Anyway, if the user types "file:/" it provides filename completion.
I only tested it in Linux, but I will try it in Windows tonight . It
doesn't work in Eclipse shell :-(
I also want to congratulate the author of the felix shell code since
it was really easy to integrate JLine.

On Thu, Dec 18, 2008 at 2:09 AM, Jon Brisbin <[email protected]> wrote:
>
> On Dec 17, 2008, at 5:54 PM, Richard S. Hall wrote:
>
>> The JLine web page says it only depends on Java 1.2 and is licensed under
>> BSD. So, both of those sound really good.
>
> I used Java 1.5 generics in places, though those sections could probably be
> back-ported.
>
>> It does say that it requires a native library under Windows, which could
>> be problematic. Did you port this to use OSGi's bundle native library
>> mechanism? It seems like it targets Windows and POSIX platforms, so it
>> probably won't on other platforms.
>
> JLine uses stty on POSIX and a native Win method to get unbuffered input.
> I'm guessing using the Bundle-NativeCode manifest header of
> "/jline/jline.dll" will work. I'm a Mac user and don't get within 6 miles of
> a PC, so I'm not much help there. :)
>
> JLine has an UnsupportedTerminal type, which it returns if it's not POSIX or
> Windows. A simple check for this could default it to a System.in read like
> in the TUI. The command completion relies on JLine, though.
>
> I have to say...the completion and history support makes one just flat
> productive. :)
>
> Thanks!
>
> Jon Brisbin
> http://jbrisbin.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to