28 Mar
2007
28 Mar
'07
6:40 p.m.
# from Donn # on Wednesday 28 March 2007 11:02 am:
Er... yeah... And I'm sure it could be piped to the Mars Lander where it could be drawn in the Martian soil ten miles high too -- but not with my script-foo :)
Uh... The script that I sent does it for you? How much more fu do you need?
--Eric
--
"I've often gotten the feeling that the only people who have learned
from computer assisted instruction are the authors."
--Ben Schneiderman
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
>From MAILER-DAEMON Wed Mar 28 11:44:50 2007
Date: Wed, 28 Mar 2007 20:44:49 +0200
From: Thorsten Wilms <t_w_@...123...>
To: inkscape-devel@lists.sourceforge.net
Message-ID: <20070328184449.GD4676@...1413...>
References: <733f2c730703261143k1657a035l4c3ec25f5e9d7370@...401...>
<01c801c77161$e967d150$0100000a@...1691...>
<0F15B26B-3D4C-45D8-A8A4-11948F45AF86@...18...>
<023a01c77164$f73914d0$0100000a@...1691...>
MIME-Version: 1.0
In-Reply-To: <023a01c77164$f73914d0$0100000a@...1691...>
Priority: normal
X-Mailer: Mutt
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Warning: 80.138.102.104 is listed at list.dsbl.org
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
See http://spamassassin.org/tag/ for more details.
Report problems to
http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Inkscape-devel] [PATCH] Dockable dialogs, and some concerns...
X-BeenThere: inkscape-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
Reply-To: t_w_@...123...
List-Id: <inkscape-devel.lists.sourceforge.net>
List-Unsubscribe: https://lists.sourceforge.net/lists/listinfo/inkscape-devel,
mailto:inkscape-devel-request@lists.sourceforge.net?subject=unsubscribe
List-Archive: http://sourceforge.net/mailarchive/forum.php?forum=inkscape-devel
List-Post: mailto:inkscape-devel@lists.sourceforge.net
List-Help: mailto:inkscape-devel-request@lists.sourceforge.net?subject=help
List-Subscribe: https://lists.sourceforge.net/lists/listinfo/inkscape-devel,
mailto:inkscape-devel-request@lists.sourceforge.net?subject=subscribe
X-List-Received-Date: Wed, 28 Mar 2007 18:44:50 -0000
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
On Wed, Mar 28, 2007 at 08:14:40PM +0200, momo wrote:
> Ok, then tell me why the concept of multiple document windows in a single
> program window it still used in Indesign, Corel, Photoshop, Illustrator,
> XaraXtreme, and many other professional programs? Having several program
> windows for every opened document is confusing, specially when working with
> lots of documents in several applications at one time. You'll end up with
> a whole bunch of windows all over the screen...
>
> It is a question of ergonomy, multitasking has nothing to do in this...
>From http://en.wikipedia.org/wiki/Multiple_document_interface:
Advantages
* Many child windows do not fill up the OS task management interface, as they
are hierarchically organized. Users simply switch applications.
* With MDI (and also TDI), a single menu bar and/or toolbar is shared between
all child windows, reducing clutter and increasing efficient use of screen
space.
* All child windows for an application can be hidden/shown/minimized/maximized
as a whole.
* Without an MDI frame window, floating toolbars from one application can
clutter the workspace of other applications, potentially confusing users with
the jumble of interfaces.
* Features such as "Tile" and "Cascade" can be implemented for the child windows.
Disadvantages
* Cannot be used successfully on desktops using multiple monitors.
* MDI can make it more difficult to work with several applications at once, by
restricting the ways in which windows from multiple applications can be arranged
together.
* The shared menu changes, which may cause confusion to some users.
* MDI child windows behave differently from those in single document interface
applications, requiring users to learn two subtly different windowing concepts.
Similarly, the MDI parent window behaves like the desktop in many respects, but
has enough differences to confuse some users.
* Many window managers have built-in support for manipulating groups of separate
windows, which is typically more flexible than MDI in that windows can be grouped
and ungrouped arbitrarily. A typical policy is to group automatically windows that
belong to the same application. This arguably makes MDI redundant by providing a
solution to the same problem.
---
On Linux, MDI by way of document windows inside an app window tends to lead to
abominations like what LMMS and Hydrogen do in their defaults. Document windows
as emulation of true WM windows -> wrong theming, button icons and positions,
another focus model than all other windows, excpet if your lucky and the WM,
theme and behavour that is emulated happens to be what you are using.
Even if separate document windows and dialogs and everything current WMs offer
to manage them is not enough, the solution shouldn't be to have a second WM layer
implemented from scratch in applications. So I think even attachabel/detachable
panels are actually a WM job.
A proposal to bring Blender-like splitable views, detachable panels and tabs
to the WM level is on my too-long todo list.
--
Thorsten Wilms
Thorwil's Creature Illustrations:
http://www.printfection.com/thorwil