Re: RosAsm User Interface


Betov wrote:
, and this
feature makes editing source code treacherous.

When you will be used to it, maybe you will find out that
this form of dedicated Editor is way _more_ secure.

I have a better idea. How about you explain *why* it's more secure so
that I stop asking you why. Tell me why you chose this feature despite
common practice. Give me details so that I'll understand. Keep in mind
that I'll keep asking until I'm satisfied that I understand your
reasoning. Here's how I understand it right now:

1) Keeping the cursor at a screen position is much easier to implement
than keeping it at a file position. I try to think the best of people,
but this screams "Betov doesn't want to be troubled with the extra
effort".

2) The user can always see what they're changing, but that's not
entirely a good argument because any decent editor that uses a file
position cursor will move the viewable window to include the cursor's
position when any edit is made.

3) I'm not familiar with the rest of the editor's features, so,
thinking the best of you, I can only guess that this cursor positioning
is required for other features to work. If you could clarify that, it
would be nice.

It's very easy to set
the cursor, scroll, make a change, and not notice that the change you
made was on a different line than where you wanted it. My initial
introduction to this (mis)feature resulted in *valid* code that
mysteriously broke when I ran it. That bug was a bitch to find, even in
the tiny program I posted.

:))

Take a look at what you write.

No need. I wrote it, so I understand it. I'm well aware that the
opposite could be said using the same words. The only difference being
whether you're used to a screen positioned cursor or a file positioned
cursor. However, I'm not convinced that your way is better. And since
you wrote the tool, it really is your job to convince me. :-)

For Sources Editors, the Caret _must_ be _always visible.

Why?

To save you from not knowing where you are writing to.

Any decent (modern) editor will move the visible window to where the
cursor is when you make a change. That includes a movement change, so
if you simply move the cursor up one line or over one column, you're
taken back to where the editor thinks you want to write. I don't see
how a sceen based cursor position saves you from not knowing where
you're writing to. Can you offer some examples of the danger you're
talking about?

you the very first Editors i used in my DOS days, were working
exactly this RosAsm way

DOS had legitimate reasons for doing so, since "graphical" editors were
gimped by the OS itself. However, DOS is dead, and there's no need to
work around its limitations in Windows.

major difference, that is that the old DOS way was perfect,
and that the actual way is demential, and cannot be defended
by any kind of argument.

I'm not convinced, and a lack of detail in explaining *why* the old DOS
way was perfect and *why* the current way is demential doesn't help to
convince me at all. I want to understand. I want to believe you. But
until you give me reason to, I won't, and I'll keep asking until you
do. :-)

.

Relevant Pages

  • Re: How do you program in Python?
    ... focus to the cmd console, press the Cursor Up key to retrieve the previous command, and hit Enter to execute it. ... (since I wasn't consciously aware of that feature), but it's really that I deliberately choose not to use and learn about such features of editors because I absolutely _hate_ getting tied to such things and finding myself stuck in other editors or on other machines and having my productivity drop to zero because a simple feature is missing. ... I lied when I said cursor up retrieved the name of the script. ...
    (comp.lang.python)
  • Re: Time Saver: what is it?
    ... posting, move your cursor to the end of the post instead of leaving ... it where you finished typing and your sig file will go to the end. ... a unique feature to it that cuts removes any text after this ...
    (rec.models.railroad)
  • Re: Suggestion for TPU: revert
    ... Or must you escape to command mode, move cursor, then get ... the screen and was not a "WYSIWYG" editor. ... younger than vi. TECO spawned Emacs, although Emacs today is not based ... but Emacs uses Lisp as its programming language and that is one ...
    (comp.os.vms)
  • CE 5.0 crashes in editor during "intellisense"
    ... complexity enough that the "intellisesne" feature of the IDE text editor now ... Platform Builder IDE I'd love to hear about it. ...
    (microsoft.public.windowsce.platbuilder)
  • RE: Source Editor Enhancements
    ... |>Subject: Source Editor Enhancements ... |>positions the cursor under the first nonblank character of the preceding ... and positions the cursor on this column. ... |>indentation level. ...
    (microsoft.public.vsnet.ide)