The JADE 2022 release meets tomorrow’s business demands.
Guest
|
HistoricalComments
John Richards 13/06/2018 9:05:06 AM
Hi James, This has been discussed by the panel and they would like to know your thoughts about Brian's suggestion. Brian Johnstone 18/05/2018 3:31:01 PM Clearly I'm too used to typing 'users' and muscle memory typed it on me when I actually meant to say 'uses' without that pesky 'r' inserted before the 's'. :-( Brian Johnstone 18/05/2018 2:59:46 PM Did you know you can actually reimplement the Object::display method, this is what the inspector users for that right hand preview pane. For example, in your top level base class for your persistent object model you could implement the following to return this additional information. This will lose it's formatting, due to being a comment, but you should hopefully get the general idea: ********************************************************************* display(): String; begin return inheritMethod() & CrLf & "Edition = " & self.edition().String & CrLf & "Creation time = " & self.creationTime().String; end; |
Take a look at https://jedi.ideas.jadeworld.com/ideas/JAD-I-281, where the workaround was also suggested in response to another idea for improving the inspector.
While useful on a case-by-case basis, generic improvements would ideally be implemented by the base implementations of Object::display, otherwise if the onus is on use to implement improvements, it'd be better if we had a way of overriding/redirecting the Object::inspect methods altogether so we can implement our own enhanced inspector UI. This is possibly something that could be achieved by an extension implementing an interface for this purpose.
Sorry about the delay. Old JEDI didn't update me on comments and these comments have been sitting here since.
I think what Brian has proposed is a good work around. Some companies will need buy in from the business, or at least a please explain on why the work around should be prioritised over other business projects.
I would expect the display to be consistent in the core product rather than expecting the customer to create a new display method for each new independent schema.