Author Topic: Split help file for GUI and Macro programming reference  (Read 794 times)

JimmieC

  • Senior Community Member
  • Posts: 468
  • Hero Points: 16
Split help file for GUI and Macro programming reference
« on: February 06, 2015, 09:21:42 pm »
Sort the help file to give the user the inherent GUI implementation first. When I search help, it provides me with all of the under-lying calls for the macro language. I don't want to write the editor myself as is a very expensive product. Additionally, if the feature is already implemented, I don't want to RE-implement it just because the help for that was lost in help search results noise. I am under tight schedules all the time and REALLY don't have time to become a SlickEdit macro programmer for every little thing. I can do it. I just don't often enough to get good at it and it distracts from the task at hand. If is something that Boxer can handle, I usually just switch over to Boxer, complete the task, and then come back to SE.

Lastly, just because a user can get to a feature with the macro language, does not mean that it should not be implemented as part of the core product (for reasons I stated above, I have work to do). Such, get file name or insert date for example. It is not enough to assume the few that need can just write a macro so it doesn't need to be implemented. I am not saying that that rationale actually occurs. I am merely stating that it shouldn't.

mwb1100

  • Senior Community Member
  • Posts: 144
  • Hero Points: 13
Re: Split help file for GUI and Macro programming reference
« Reply #1 on: February 06, 2015, 10:46:34 pm »
Sort the help file to give the user the inherent GUI implementation first. When I search help, it provides me with all of the under-lying calls for the macro language.

I agree with this.  It seems that all too often I'm searching help for how to do something with the GUI and I mostly get hits on the macro language and functions.  I'm usually not interested in those; I'm not very handy with SE macros and am not particularly interested in spending time learning slick-c programming. It would be nice to be able to filter them out of help searches.