On Dec 18, 2008, at 8:07 AM, Richard S. Hall wrote:
I guess the question is, do people think it would be worth it?
I'm deploying in a server environment, so this was written with a ServiceMix-like environment in mind. I can confirm that, for me, it is hugely beneficial and time-saving. I can use all the keyboard shortcuts I'm used to (CTL-A/E/D/K) and the history support across restarts is extremely helpful. FWIW I was really ready to go to ServiceMix kernel for the shell. I liked the way the app deployed in stock Felix better (much less memory use), but the development cycle I've found my self in--NetBeans/Maven...compile, then do an update 42-- makes working with a readline-like shell a lot more productive. I'm back and forth between NB and the shell a lot. Using stock Felix, there's no auto-reload like using some other fancy-pants server environments like dm Server or ServiceMix. :)
I don't know what the implications are for non-server, non-desktop applications, but it's interesting that someone else was thinking along the same lines I was (great minds and all, right? ;).
Of course, there is also another possibility, which is to not to merge it, but create a separate shell UI bundle.
This would be the best solution, IMHO. This would give the developer a choice of the more portable basic UI or a more developer-friendly one. I'm probably going to turn the shell off entirely in production, so which bundle the shell is in doesn't really matter much (whether the existing TUI one or a new JLINEUI one). I was mainly interested in development-time productivity.
Thanks! Jon Brisibn http://jbrisbin.com
