JADE Environment Development Ideas

Null exceptions must be up there with the most common runtime issue. Often these occur when dealing with older persistent data that didn?t have the same validation enforced on it, or object references yet to be populated. There are various strateg...

Many development environments support a try/catch exception handling style, typically: try { // do stuff}catch (exceptionObject) { // handle exceptions} Statements in the try block are executed and, if there is an exception of a type compatible wi...

When JADE started out there was the intention that the language would be simple enough that novice developers could code in it and understand it. This was the reason for not including "advanced" concepts like a ++ operator, or a switch statement. ...

Currently if you have parameters or attributes which can only contain one of a range of values, you have to write code to ensure that the value you're setting is valid - the compiler doesn't ensure the consistency of this data. For example if a me...

As part of a regular check on our code base we check to see if method access has been set appropriately. We use the undocumented feature on RootSchema getMethodRefs() to check where the method is being used, but this does not return any method ref...

The Job Control Facility (JCF) uses method recursion to define and manage job steps within a job. Because generally 2 (but sometimes more for certain job element types) methods are involved for each job step, I have had to impose a limit of 100 jo...

When you refactor code in a system, it would be nice to be able to mark features as deprecated so that users get warned when compiling methods which reference deprecated features. To partner this it would be good to have a "Browse ..." option whic...

When compiling a method we use F8 and if there are any compile errors they are identified. What would be beneficial (especially for anyone learning Jade) would be a "smarter" compile which would warn on potential problems in the code. Here are som...

Many languages now have string interpolation so that instead of "Name: " & name & " Age: " & age you can do something like "Name: {name} Age: {age}" which is faster to type and more readable. It would also be nice when interpolating...

Hi Jade Can we get a Use Statement for workspaces so we can include the target schema as a part of the workspace. this would save me having to email my co-leagues which schema to run the work space against An Example of how this might look is Use ...