in reply to Re: Re: Edit scratchpad from within the scratchpad
in thread Edit scratchpad from within the scratchpad

I guess the problem I see is that after you've edited your scratchpad, you have to stumbit it, wait for the server to accept it, then go view your scratchpad to see if you made a fiddly mistake. Even if I have a separate window open to the scratchpad, I find the process of stumbit, switch windows, wait, refresh, wait, and then see the effect to be obnoxious.

tye, I've often wondered why the Update form is there all the time; any reason not to just have the button that takes you to a displaytype=update view (which looks the way things are now, with both output and input, not the way displaytype=edit looks).

  • Comment on Re: Re: Re: Edit scratchpad from within the scratchpad

Replies are listed 'Best First'.
Re^4: Edit scratchpad from within the scratchpad
by tye (Sage) on May 07, 2004 at 18:50 UTC

    Ah. Your complaint was about not being able to preview nor automatically postview your changes. Yes, that isn't the best situation. But the best way to fix that for scratchpads is to first fix the underlying problem by making them separate nodes.

    The only reasons to not remove the forms are the standard "they won't remove themselves" and "some people might like them" (if for no other reason than that they've become accustomed to them).

    So I'm more inclined to avoid adding new always-there forms (not do what was originally requested) than to try to rip out all of the existing always-there forms (at least for now).

    - tye        

      Agreed. About the existing forms, perhaps a user option to select a default displaytype from among "update" (what it looks like now, which would be the default for existing users), "regular" (no form, provides link to switch to update view, default for new users?), print, xml, edit (unlikely to be used as default) etc.

      As you say, this stuff doesn't code itself; I hope just ideas are at least minorly helpful anyway.