Re: Wee: standard installation
- Posted by K_D_R May 23, 2015
- 2148 views
Being willing to include Wee but not the include file it needs seems a bit weird.
It isn't going to matter. As long as you keep it available for those who need it, what is the benefit to including this with the distribution?
Shawn Pringle
The benefit, it seems to me, would be to avoid reviews which make fun of Euphoria's 1980-style editor. And in addition, to make getting started easier for people who are trying Eu for the first time. Wee is a good, fairly complex, app built with Euphoria, and it's intuitive to use. IOW, it works just like other programs they may have used. It should work 'right out of the box' for people who have never used Eu, without the hassle of downloading anything else, and without having to set up directories, etc.
This would at least give the impression that we know what we are doing :)
If Wee is going to be included as a part of the Eu download, it would probably be a good idea to comment and document the code a bit more, so people could use it as an example.
Edit: and, let's face it - there's never going to be another Eu-specific editor, or any real support from any of the other existing editors. Wee is fine as it is, and - here's a hint - it's one we can modify/enhance/fix ourselves.
I think Irv is right on.
I might add that Wee's hotkeys for context sensitive help, view subroutines, declarations, arguments, completions, goto error make it a wonderful learning tool for the Euphoria newbie.
~
Comments about Wee menu preferences:
I think the current "View" menu should be named "Help" with the F1 hotkey option listed first as "Euphoria Keyword/subroutine help - if there is not a Euphoria manual "article" for the current word, then the view subroutine declaration routine could be automatically called.
The current "Help" menu could be named "About" and contain the two items listed in the current Help menu, namel "About and "Tutorial" - these options are about the Wee editor, whereas the new Help menu would be Help regarding language/code features.
A new "View" menu could contain a "View Demos" option to select any of the platform appropriate programs from the demo folder to load into the editor, a "View Manual" selection to view the local index.html file, and perhaps a "View Euphoria Online Forum" option as well.
A new "Tools" menu could contain the "Bind", "Shroud", and "Translate" options listed currently in the "Run" menu, but with links to the appropriate html manual articles - and options for "with arguments" and "set arguments".
Sorry I got carried away!
As Irv mentioned, Wee is so fine as it is now that even I can make most of the modifications which I have suggested above. Pete has put Irv's EuGTK "tool kit" to good use - and, as far as I can tell, he has done an excellent job of providing Windows support as well.
Thanks again to Pete and Irv!
Regards, Ken
