Dyalog / ride

Cross-platform IDE for Dyalog APL
https://dyalog.github.io/ride
MIT License
198 stars 29 forks source link

Newbie-friendliness: integrate more ODE-Options into RIDE-Menu! #157

Open mbaas2 opened 7 years ago

mbaas2 commented 7 years ago

Describe the issue you are having

I had two people from a german APL-related group (not APL Germany) start using RIDE (under Linux) in their attempts to learn Dyalog. One of the comments they made referred to the way the menu is used and when looking at it with the eyes of a beginner, they are absolutely right in this: there is no File/Save to save the ws (or File/Load). Besides, they complained about "Mastering Dyalog APL" explaining them how to manipulate the toolbar when they do not even have a toolbar! (a) perhaps the next revision of the book should have some remarks about platforms used! (b) an ODE-Style toolbar would certainly be nice for RIDE. Perhaps V5???

Did you connect to an already running interpreter or start the interpreter from RIDE?

Start an interpreter.

How do you reproduce the issue?

Take newbie, make him use RIDE under Linux to learn Dyalog ;-)

abrudz commented 7 years ago

PC-DOS 7.0 included a REXX IDE that had a command line. The IDE had menus too, but selecting things from the menu would in many cases just put the appropriate command on the command line. Maybe we could do something similar:

etc.

JohnScholes commented 7 years ago

Nice. JohnS' 2p:

JohnScholes commented 7 years ago

I don't know enough about this to log a repro. Does anyone know what might be going on?

I want to debug a problem with ]boxing on the Mac, so I

)ed ⎕se.Dyalog.Out.Filter

and place a syntax error (∘∘∘) just before the :Trap statement at the top of the function. Then I try to display a train:

  ++++++

The Filter function suspends with a SYNTAX ERROR.

Now, using the tracer, I can step over the ∘∘∘s and the :Trap statement, and trace into the code that follows.

As soon as I trace into this line

    ⎕THIS U.drvSrc'rand'   ⍝ parenthesised derv.

which is in the Utils.dyalog salt file, the tracer becomes very unresponsive, taking getting on for a second to process each line.

I think this must be a Ride issue because I don't recall its happening when Adam and I were debugging on Windows this afternoon.

Any ideas?

e9gille commented 7 years ago

@JohnScholes I looked into this and it is down to that script being relatively large (>500 lines) combined with an inefficient "set focus" in the golden-layout framework. Should be significantly improved with patch db1624848ec9157b8fc5a73ea3370ebc26afe6af