JADE Environment Development Ideas

We currently have to generate a WSDL file manually via the application dialog. With many web services to maintain/publish, we have a procedure where developers will generate the WSDL manually and save it to a common location. It'd be useful if we ...

Visual Studio has the concept of "Chords" which are a keyboard shortcut sequence. For example, Ctrl+K then Ctrl+D autoformats the current document. We should do the same, as it essentially expands the keyboard shortcut space exponentially.

Let's be able to tell the difference between 0 and null, for example. Has something been set to 0 or has it not been set? I don't know!

My specific use case was to retrieve the current database usage, to see if usage was Usage_NoAudit. A JadeDatabaseAdmin method that returned various database state values in a JadeDynamicObject would be ideal.

A frequent use of the Control::keyPress event is for things such as a 'filter' or 'quick search' text box that will filter the list of entries displayed in say a table of results on that form. This is used to provide a 'better' user experience tha...

When you delete a schema and there are instances of classes, the delete can fail with an exception from inverse maintenance. This is sub-optimal given the objective is to discard all the schema defined object instances as well. Little useful infor...

Currently only classes or method can be specified in a schema extract parameter (.unl ) file. It would be useful if the was syntax option to specify an application to extract rather than having to manually go to the Applications tab and then selec...

It would be nice if Call Stack Analysis showed what the process was waiting for, like waiting for a queued lock, file IO, external function, interpreter etc.

Currently in the Method Source Window you can only remove a method by right-clicking the method and select Remove From List. It would be good to remove a method by selecting it and pressing the Del key.

Please add a new CPU Consumption sheet to Monitor. This would make it much easier to track down high-CPU issues and rogue (eg looping) applications. This sheet would have one row per node and JADE process, like the Users sheet does. It would hav...