-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stefano Lenzi schrieb: > [EMAIL PROTECTED] wrote: >> Stefano, >> >> I disagree. Those features are nice to have but they add to the >> minimal size of an implementation, which would be inappropriate on a >> constrained platform such as mobile phone. Also completion would work >> much differently on a T9-based input device versus a conventional >> keyboard. >> >> The aspect of the OSGi command prompt that MUST be standardised is the >> extensibility mechanism, i.e. adding new commands to the shell. >> Currently one must implement these extensions differently on each >> framework, which limits their value. >> >> Less critical but still IMHO important is a standardised syntax and >> set of "core" commands. If these are standard across different >> frameworks then technical documentation (manuals, tutorials etc) can >> be written without endless instructions to "type X on Equinox, Y on >> Felix, Z on Knopflerfish..."). >> >> Above this base, each framework should be free to implement whatever >> value-add features it like such as history and completion, but I don't >> think those features should be part of the specification. >> >> Regards, >> Neil >> > > I agree on your statements but my idea was to define a "Command" service > API which allows an easy implementation of the feature that I described. > > Keeping that in mind I don't think that an History feature require any > special method on the Command service(the implementation will be > demanded to the Console implementation), but a getArguments() method > will be very useful on the Command service in order to easy implement a > Option completion. A concrete example is JLine APIs > (http://jline.sourceforge.net/apidocs/index.html) where a Completor > interface is defined for make easier the implementation of completion > feature by the Console. > > >> On 3/11/08, Stefano Lenzi <[EMAIL PROTECTED]> wrote: >>> Peter Kriens wrote: >>>> The OSGi is currently working on a standard in this area. We have >>>> finished the RFPs and started working on the RFC. So if you have >>>> inputs, >>>> please let them be known. >>> I think that: >>> - Command History >>> - Command and Option completion. Also either Command and Option >>> completion should provide help information during the listing of the >>> available chooses >>> are a *must have* user requirement of the standard console. >>> >>> My two cent, >>> Stefano "Kismet" Lenzi >>> >>> _______________________________________________ >>> OSGi Developer Mail List >>> [email protected] >>> https://mail.osgi.org/mailman/listinfo/osgi-dev >>> >> _______________________________________________ >> OSGi Developer Mail List >> [email protected] >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> >> > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev
Hello, what I would like to see would be a sort of categorization of the commands. For example look at the Asterisk PBX console. (http://examples.oreilly.de/english_examples/asterisk/openbook/appe.pdf). There you group commands and build a command hierarchie (with groups and sub-groups). With this approach you can easy overlook the valid commands (depending on the current context). The Command API should make this possible. For EXAMPLE, think about following groups: group set: - ------------------------- set verbose <LEVEL> set debug <LEVEL> ... group show: - ------------------------- show bundles [<ID> [<ID> ...]] show deployment-packages [<ID> [<ID> ...]] show services [<FILTER>] ... group install: - ------------------------- install bundle <URL> [<URL> ...] install deployment-package <URL> [<URL> ...] ... ... And so on, I think you get it ... Just my 2 cents, Kind regards, Siamak Haschemi -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfW2mUACgkQBLvtewtTERNCmQCfdn6X/m135S2Mkcv6GIBIe0yq r/cAnjreqtpf+k6N62cC306dDuC78+yj =wOI9 -----END PGP SIGNATURE-----
begin:vcard fn:Siamak Haschemi n:Haschemi;Siamak org;quoted-printable:Humboldt Universit=C3=A4t;Informatik adr:;;Kaiserdamm 84;Berlin;Berlin;14057;Deutschland email;internet:[EMAIL PROTECTED] title:Dipl. Inf. (FH) tel;home:+49 176 64123198 tel;cell:+49 176 64123198 note;quoted-printable:Skype: siamak.haschemi=0D=0A= x-mozilla-html:FALSE url:http://www.haschemi.org version:2.1 end:vcard
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
