JADE Environment Development Ideas

Further to #54, auto-complete would be a lot more useful if it differentiated between items directly on the object being accessed (when its type is known) vs those inherited.

For example, if I have the following class hierarchy:

Object
--Person: name, email, sendEmail()
----Customer: code, creditLimit, isOverLimit()

then have a local variable of type Customer, when auto-complete pops up the code, creditLimit and isOverLimit items should appear more prominently than name, email, sendEmail(), or (and this is the worst bit) all the "pollution" from superschemas. (E.g. sendMsg, sendMsgParam1, sendMsgParam2, etc.)

By prominently, perhaps the inherited items could be dimmed out, or maybe hidden by default if in a superschema - then revealed if desired with a hotkey or after a time delay? (Or perhaps like Show Inherited in the class browser, so that properties and methods of a class are shown first, followed by those of its superclass, and so on.)

As it stands auto-complete is fine if you know the name of the thing you want as you can type a few characters to narrow down the list, but it's not great for discovering the available properties or methods on an object as the list is obscured by items that are most-likely irrelevant.