[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: Re: PlasMate ~ UI and other stuff
From: Yuen Hoe Lim <yuenhoe86 () gmail ! com>
Date: 2009-10-23 8:18:11
Message-ID: 26362f480910230118n4cb4aae7j5ea9c97d084c15e8 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
> you really work like that?? one file at a time? o.0
>
No no that's not what I meant xD And no I don't and can't work like that :)
I meant being able to have all the files open at the same time with unsaved
changes strewn all over the place - but being able to save the files one at
a time. ie - can the user decide *when* to save and *which* files exactly to
save. Let's say I have file a b c and d open and all have unsaved changes.
Can I choose to save only file b and c to disk and leave the stuff in a and
d unsaved, as you could in Kate and any other regular tabbed editor?
the actual files should be saved to disk automagically so that the user
> doesn't
> lose work if there's a crash or power loss or something.
>
I guess this means the answer is no? I don't really have hard objections
against this, but I do sometimes find it convenient to be able to leave a
file with changes unsaved and be able to simply revert by reloading the file
from disk later if I want to. I know you could achieve a similar effect with
save-point, but you don't always know you're doing something awful until
you're several files worth of changes in :)
----
Jason "moofang" Lim Yuen Hoe
http://yuenhoe.co.cc/
[Attachment #5 (text/html)]
<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">you really \
work like that?? one file at a time? o.0<br></blockquote> <div><br>No no that's \
not what I meant xD And no I don't and can't work like that :) I meant being \
able to have all the files open at the same time with unsaved changes strewn all over \
the place - but being able to save the files one at a time. ie - can the user decide \
*when* to save and *which* files exactly to save. Let's say I have file a b c and \
d open and all have unsaved changes. Can I choose to save only file b and c to disk \
and leave the stuff in a and d unsaved, as you could in Kate and any other regular \
tabbed editor?<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> the actual \
files should be saved to disk automagically so that the user doesn't<br> lose \
work if there's a crash or power loss or something.<br></blockquote><div><br>I \
guess this means the answer is no? I don't really have hard objections against \
this, but I do sometimes find it convenient to be able to leave a file with changes \
unsaved and be able to simply revert by reloading the file from disk later if I want \
to. I know you could achieve a similar effect with save-point, but you don't \
always know you're doing something awful until you're several files worth of \
changes in :)<br> </div><br clear="all">----<br>Jason "moofang" Lim Yuen \
Hoe<br><a href="http://yuenhoe.co.cc/">http://yuenhoe.co.cc/</a><br> <br></div>
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic