JADE Environment Development Ideas

Brian Johnstone 14/12/2018 11:15:09 AM
No worries. Don't forget that modern text editors frequently have an 'offset' option on their Ctrl+G 'goto' dialogs. :-)

Software Medical Infomatics Limited 13/12/2018 1:15:24 PM
Thanks for the comments, Brian and Sam. I think, going forward, with Jade 2018 being able to integrate with Git for version control, it will become more useful to have this. Pulling up the schema source from any particular commit in Git and looking at it in a text editor will become more usual and thus useful to have this line:column notation.

Sam Stokell 13/12/2018 10:39:51 AM
if you have that method version in your history you can set a delta apply that historic method then find the source position and unset the delta when you know where you are looking

Brian Johnstone 13/12/2018 9:45:53 AM
Thanks for the explanation. It may be worth adding that detail to the description as well for added clarity around why line/column information would be useful. Quick tip: If you don't already do this, on the odd occasion where I don't have an IDE with the correct source code I copy & paste the correct method source from wherever I can access it into a new JadeScript method in any available IDE, and then use the find code position. I replace the entire source, including the JadeScript's method name, so that the code position is correct even though that JadeScript would never compile.

Software Medical Infomatics Limited 13/12/2018 8:03:18 AM
Hi Brian

You're assuming that we always have a Jade IDE with the version of the code that we want to find the code position in. That might not always be the case. If I have a Jade method in a text editor (not the IDE) having the line and column is useful; having the code position isn't.

Brian Johnstone 12/12/2018 11:54:13 AM
How is this going to be quicker than Alt+M,F then type/paste code position, then press enter? You'd have to scroll the editor window until the correct line number is visible, assuming you even have line numbers turned on in the editor, then guesstimate and click where in that line of code you think that column number is located, and then use left/right arrows to tweak your column guesstimate until you get to the correct column. JEDI 246 if/when implemented will help with getting to the correct line number, but you'd still need to find the correct column after that.