OpenEuphoria

Re: Edita help window

• Posted by Pete Lomax <petelomax at blueyonder.co.uk> Apr 12, 2007
• 499 views

CChris wrote:
> All this sounds nice, but:
> 1.1/ The above makes sense only when a _word_ is selected. It would probably
>  be less confusing if the context help was bypassed when something else than
>  a word is selected. My mistake (was it?) was to expect something meaningful
>  when nothing is selected. Using the first word on the current line is
>  certainly unexpected and confusing.
Oops, missed out a feature there. If, using _ to indicate cursor, you type:

Main = create(Window,"Edita",_

pressing F1 will show the help for create. So it would break stuff to require
"create" to be block selected in order to show help for it.

> 
> 1.2/ Checking for the help on "repeat" makes sense in several languages, but
>  you don't expect the same output according to the language used. Guessing
>  which language is being used is done reliably through inspection of the file
>  type and syntax highlighting currently in use. For now, just disable the 
> feature on non Eu files.
Fair point, will do that.
> 
> 1.3/ 1.e is certainly a design flaw, because the needs for help on a word or
>  on akeyboard shrtcut are quite independent. This is why I strongly suggest
>  2 different windows and 2 different help menu entries.
As per 2.d I plan to allow Ctrl F1 for keyboard help, but I don't like the idea
of F1 on a blank line just remaining mute. Or maybe a messagebox:
<pre>
  [Context Help           _X]
   No suitable help for "".
   [Keyboard Help] [Cancel]
</pre>

> 
> > 2) Bugs and Wishes
> 
> I just opened misc.e in Edita 0.2.7, double clicked on "machine_func"
>  (highlighting it) at line 24, row 17. F1 then gives me the keyboard help. 
> This is not consistent with above description.
Odd. It works as expected here.

> First off, there is already such a front end, freely available in the Eu
>  source directory; it is made of scanner.e and parser.e. Not having to
>  report compile errors and not having to figure out opcodes can make them
>  quite lighter.
Hmmm.
> 
> Second, I didn't expect "Help" to do that, but "Xref" rather. Such a tool
>  would be a tremendous boost to the usefulness of Edita. I have this sort
>  of thing almost working in my enhanced Visual Euphoria. I'd have to figure
>  the right include files to get it working again and making the tool reliable.
Well, there is already a useful front end in the form of scanner.e and parser.e,
which you could trivially make into Xref utility. )

Seriously though, I personally just use find in files for that soft of thing.

> Much more simply, I happened to highlight "constant" and pressed F1.
I got you now. Added to my suggestion list, thanks.

Regards,
Pete