JADE Environment Development Ideas

What's new in the upcoming JADE release?

IMPROVED DEVELOPER EFFICIENCY. ENHANCED SECURITY. SMOOTHER INTEGRATION

The JADE 2022 release meets tomorrow’s business demands.


Start your update to JADE's latest release

Never default the mapfile on the add class dialog

If you've had the change class dialog open for a class in the current IDE session, and you subsequently add a new class the IDE will default the mapfile for the new class to the mapfile context of the last viewed/changed class. This can easily mean that the developer overlooks thinking about the most appropriate mapfile to use for the new class. It would be better when adding a new class if the mapfile never defaults on the add class dialog so that the developer is always forced to consider what mapfile is the most appropriate for the new class to use for its instance data.
  • BeeJay
  • May 1 2019
  • IDE Backlog
IDE & debugger
HistoricalComments
Ty Baen-Price 9/10/2017 3:45:58 PM
This issue seems development-group specific, so would have to be optional, as proposed. I think any scheme is going to irritate someone. Perhaps a better solution for your woes is to add a step to release planning/review to look at all added classes to ensure they're in the appropriate file?

Kevin Saul 6/10/2017 5:30:31 PM
Per comments on #14, the map field field would be cleared/disabled entirely when it's not actually needed.
Attachments Open full size
  • Attach files
  • Kevin Saul commented
    26 Nov 08:13

    Seems things are worse now - I've just noticed 2022 will now default the map file for an existing class which doesn't have the map file set (not required/needed because we don't create persistent instances of it). I've just had to advise our development team to take extra care to avoid setting the map file unintentionally when updating an existing class.

    Attachments Open full size
  • +6

Related ideas