Keep Inkscape running after closing single or last document (survey)?
All:
Who would like Inkscape to keep running after you close a single document or the last document so that you can immediately start a new document without relaunching Inkscape? I find this behaviour very annoying and contrary to the way most document-oriented applications on all operating systems work.
MDI type applications (such as OpenOffice.org) keep a blank grey window frame open into which you can start a new document. SDI type applications (such as the open-source Notepad++ on Windows) open a new blank document when you close the last open document. Gimp keeps a small "launch" palette open when all documents are closed.
File > Close should close documents (creating a new empty document if only one document is open). File > Quit should close ALL open documents (giving you the chance to save unsaved work) and then close the Inkscape application.
The window frame should have an application-instance close [X] icon at the RH end and the menu bar should have a document close X icon at the RH end.
Refer to these bug/enhancement requests at https://bugs.launchpad.net/inkscape/ that also request that Inkscape not quit when a document is closed:
#170550, open blank document on 'close' #171935, OSX Don't close the application when closing Inkscape window #171596, Reorganize UI when closing document [MDI] #170803, Close document vs. Quit program
Please post your preference to the list and identify yourself as an end-user, developer, or both, and what platforms you use Inkscape on. I am just an end-user on Windows and Ubuntu, using v. 0.46.
Regards, Hedley
--
Hedley Finger
28 Regent Street Camberwell VIC 3124 Australia Tel. +61 3 9809 1229 Fax. (call phone first) Mob. (cell) +61 412 461 558 Email. "Hedley Finger" <hfinger@...2483...>
On May 4, 2008, at 11:08 PM, Hedley Finger wrote:
MDI type applications
Just FYI, MDI itself was generally considered a poor choice once computers could run more than one program at once, and Microsoft themselves officially deprecated it as of the release of Windows 95.
I think that just keeping a blank document open is a nice way to have inkscape pre-loaded and not having to relaunch it each time.
What I would really request instead is that, whenever Inkscape is executed, it to check for already existing instances. If one such exists, then it just creates a new document in that instance of Inkscape, instead of opening a completely new instance of the application. This would be nice because:
- The time to open a new inkscape document would be greatly reduced once you already have a running instance -- whenever you click on the inkscape icon in your launch bar, or type the command in the terminal, you'd get a new empty document to play with.
- The new document would join the previously running ones, and copy-and-paste would work between them. Right now, if you re-launch inkscape you can't copy-paste between the two instances.
- Possibly some other reasons I can't think of now..
Denís.
2008/5/5 Jon A. Cruz <jon@...204...>:
On May 4, 2008, at 11:08 PM, Hedley Finger wrote:
MDI type applications Just FYI, MDI itself was generally considered a poor choice once computers could run more than one program at once, and Microsoft themselves officially deprecated it as of the release of Windows 95.
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao... _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
On Mon, 5 May 2008 09:57:32 +0200 "Denís Fernández Cabrera" <denis@...2126...> wrote:
I think that just keeping a blank document open is a nice way to have inkscape pre-loaded and not having to relaunch it each time.
What I would really request instead is that, whenever Inkscape is executed, it to check for already existing instances. If one such exists, then it just creates a new document in that instance of Inkscape, instead of opening a completely new instance of the application. This would be nice because:
- The time to open a new inkscape document would be greatly reduced
once you already have a running instance -- whenever you click on the inkscape icon in your launch bar, or type the command in the terminal, you'd get a new empty document to play with.
- The new document would join the previously running ones, and
copy-and-paste would work between them. Right now, if you re-launch inkscape you can't copy-paste between the two instances.
- Possibly some other reasons I can't think of now..
Denís.
This is something I would very much like to see as well.
Currently I usually start Inkscape by clicking on a document, then use the file browser for any others I need, but this is vary inconvenient.
I wonder how this behaviour would 'influence' one of Inkscape's most annoying draw-backs: the inpossibility to copy objects between unrelated inkscape-instances. I'm not a programmer, but I can image that if one window stays open, the chance is much bigger that two open windows are 'instances' of eachother, so that copy-ing and pasting between Inkscape documents goes much easier. :/ :\ *thinking*
Even if this idea is voted out, it might solve the copy-problem maybe? If Inkscape could always be 'sleeping' somewhere in the background, but instantiating a document-window whenever somebody 'opens' Inkscape?
Or has this issue been fixed in .46?
-----Original Message----- From: inkscape-user-bounces@lists.sourceforge.net [mailto:inkscape-user-bounces@lists.sourceforge.net] On Behalf Of Abrolag Sent: 5. mai 2008 10:09 To: inkscape-user@lists.sourceforge.net Subject: Re: [Inkscape-user] Keep Inkscape running after closing single or last document (survey)?
On Mon, 5 May 2008 09:57:32 +0200 "Denís Fernández Cabrera" <denis@...2126...> wrote:
I think that just keeping a blank document open is a nice way to have inkscape pre-loaded and not having to relaunch it each time.
What I would really request instead is that, whenever Inkscape is executed, it to check for already existing instances. If one such exists, then it just creates a new document in that instance of Inkscape, instead of opening a completely new instance of the application. This would be nice because:
- The time to open a new inkscape document would be greatly reduced
once you already have a running instance -- whenever you click on the inkscape icon in your launch bar, or type the command in the terminal, you'd get a new empty document to play with.
- The new document would join the previously running ones, and
copy-and-paste would work between them. Right now, if you re-launch inkscape you can't copy-paste between the two instances.
- Possibly some other reasons I can't think of now..
Denís.
This is something I would very much like to see as well.
Currently I usually start Inkscape by clicking on a document, then use the file browser for any others I need, but this is vary inconvenient.
-- Will J Godfrey http://www.musically.me.uk
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao... _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager.
This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses.
www.powel.no **********************************************************************
Maarten van der Velde wrote:
: the inpossibility to copy objects between unrelated inkscape-instances.
actually, you can copy-paste between different instances, as of about March 26 or so. see https://bugs.launchpad.net/inkscape/+bug/170185
On Mon, 5 May 2008 09:57:32 +0200, "Denís Fernández Cabrera" <denis@...2126...> wrote:
What I would really request instead is that, whenever Inkscape is executed, it to check for already existing instances.
There are some subtleties which would need to be addressed, but generally I think this is a good idea.
- The new document would join the previously running ones, and
copy-and-paste would work between them. Right now, if you re-launch inkscape you can't copy-paste between the two instances.
This problem is now fixed in trunk actually.
-mental
Hedley, I am an end user and use win2000. I am all in favour of having Inkscape keep running after closing the last document. The current switch-off behaviour has driven me quietly insane for so long..............There may have been a good reason for the present behaviour in the distant past but if so I've long since forgotten what it was but the current behaviour continues to irritate. Erik Hedley wrote:
Who would like Inkscape to keep running after you close a single document or the last document so that you can immediately start a new document without relaunching Inkscape? I find this behaviour very annoying and contrary to the way most document-oriented applications on all operating systems work.
MDI type applications (such as OpenOffice.org) keep a blank grey window frame open into which you can start a new document. SDI type applications (such as the open-source Notepad++ on Windows) open a new blank document when you close the last open document. Gimp keeps a small "launch" palette open when all documents are closed.
File > Close should close documents (creating a new empty document if only one document is open). File > Quit should close ALL open documents (giving you the chance to save unsaved work) and then close the Inkscape application.
The window frame should have an application-instance close [X] icon at the RH end and the menu bar should have a document close X icon at the RH end.
Refer to these bug/enhancement requests at https://bugs.launchpad.net/inkscape/ that also request that Inkscape not quit when a document is closed:
#170550, open blank document on 'close' #171935, OSX Don't close the application when closing Inkscape window #171596, Reorganize UI when closing document [MDI] #170803, Close document vs. Quit program
Please post your preference to the list and identify yourself as an end-user, developer, or both, and what platforms you use Inkscape on. I am just an end-user on Windows and Ubuntu, using v. 0.46.
Regards, Hedley
--
Hedley Finger
28 Regent Street Camberwell VIC 3124 Australia Tel. +61 3 9809 1229 Fax. (call phone first) Mob. (cell) +61 412 461 558 Email. "Hedley Finger" <hfinger@...2483...>
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao... _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
On Mon, 2008-05-05 at 16:08 +1000, Hedley Finger wrote:
All:
Who would like Inkscape to keep running after you close a single document or the last document so that you can immediately start a new document without relaunching Inkscape? I find this behaviour very annoying and contrary to the way most document-oriented applications on all operating systems work.
In UNIX, there is a sticky bit. When set, it keeps the image of the program in memory for a short time after the last close; the exact amount is determined when the OS is compiled.
To set it on your machine:
sudo chmod a+t `which inkscape`
Please post your preference to the list and identify yourself as an end-user, developer, or both, and what platforms you use Inkscape on. I am just an end-user on Windows and Ubuntu, using v. 0.46.
I agree that something along these lines would be better than the current way Inkscape behaves. I'm not sure that just staying open with a blank document would be the best approach, but it definitely sounds better than how it behaves currently.
I am currently only an end user, on Windows XP and Ubuntu and Fedora.
Quasar
my vote would be as follows : - keep the existing SDI with one change - when you choose File | Open, it should check to see if the document has changed, if so, it should ask whether you want to save it - after the prompt has been dealt with, it should load the new document into the existing instance of Inkscape without creating a new instance.
--------- three follow ups:
- if Linux requires a time delay to clear stuff, that should not be a problem , it will still be much less than currently occurring - the main argument against the SDI is the copy/paste problem that previously existed, but that has been fixed - am not a big fan of blank documents, that is what the File | New command is for, and it works very well ...
On Mon, 2008-05-05 at 14:42 -0700, Alvin Penner wrote:
- if Linux requires a time delay to clear stuff, that should not be a
problem , it will still be much less than currently occurring
Linux does not require any delays in shutting down an application.
What Linux and BSD can to is delay re-using the memory that holds the application code. Since the code is still in memory, restarting is very quick. All UNIXes have had this ability since the mid-70s.
Mr. Shawn H. Corey wrote:
Linux does not require any delays in shutting down an application.
- woops, sorry about that, I got a little carried away (actually, being a Windows person, the concept of time delays seemed perfectly normal to me, part of the cost of doing business in Windows)
- one more comment, namely that in an SDI interface, it seems kind of redundant to have a File | Close option.
participants (10)
-
Abrolag -
Alvin Penner -
Denís Fernández Cabrera -
Hedley Finger -
Jon A. Cruz -
kaver -
Maarten van der Velde -
MenTaLguY -
Mr. Shawn H. Corey -
Quasar Jarosz