Commit 8d027874 authored by Lars Clausen's avatar Lars Clausen
Browse files

Version 0.96 pre2. Fixed datadir/libdir, fixed desktop.in builds.

svn path=/trunk/; revision=3594
parent de55d8b1
2007-01-21 Lars Clausen <lars@raeder.dk>
* installer/rpm/dia.spec:
* config.h.win32:
* doc/en/dia.xml:
* doc/pl/dia.xml:
* doc/eu/dia.xml:
* configure.in:
* NEWS: Prerelease 2 of 0.96.
* Makefile.am (applicationsdir):
* po/POTFILES.in: Create versioned dia.desktop file by first
intltool'ing it and then replacing the version number.
* app/interface.c (create_tools): End g_strconcat with NULL.
Fixes bug #398286.
2007-01-18 Lars Clausen <lars@raeder.dk>
* lib/Makefile.am (AM_CPPFLAGS):
* lib/dia_dirs.c: DIA_DATADIR and DIA_LIBDIR reverted to being
DATADIR and LIBDIR, see
http://mail.gnome.org/archives/dia-list/2007-January/msg00008.html
and bug #385701.
2007-01-16 Lars Clausen <larsrc@raeder.dk>
* doc/en/usage-layers.xml: Corrections from Mick Curtis & Tim
Bogie (see bug #347210).
2007-01-14 Lars Clausen <larsrc@static>
 
* Makefile.am (%.desktop.in): Attempt at better desktop.in
......
......@@ -9,10 +9,10 @@ pkgdata_DATA = dia_logo.png
pixmapdir = $(gnomedatadir)/pixmaps
pixmap_DATA = dia_gnome_icon.png dia-diagram.png
desktop_in_in_files = dia.desktop.in.in
desktop_files = $(desktop_in_files:.desktop.in.in=.desktop)
#desktop_in_in_files = dia.desktop.in.in
#desktop_files = $(desktop_in_files:.desktop.in.in=.desktop)
applicationsdir = $(DESKTOP_DATADIR)/applications
applicationsdir = $(datadir)/applications
applications_DATA = $(desktop_files)
......@@ -20,27 +20,28 @@ dia.keys: $(srcdir)/dia.keys.in Makefile
sed -e 's^\@icondir\@^$(pixmapdir)^g' $(srcdir)/dia.keys.in > dia.keys.tmp \
&& mv dia.keys.tmp dia.keys
CLEANFILES = core-translation-report dia.keys dia.desktop dia.desktop.in
CLEANFILES = core-translation-report dia.keys dia.desktop
#DISTCLEANFILES = $(desktop_files)
#--- Adapted from http://svn.xfce.org/svn/xfce/libexo/trunk/exo-helper/helpers/Makefile.am
desktopdir = $(datadir)
desktop_in_files = $(desktop_in_in_files:.desktop.in.in=.desktop.in)
desktop_in_files = dia.desktop.in
desktop_DATA = $(desktop_in_files:.desktop.in=.desktop)
%.desktop.in: %.desktop.in.in
sed -e "s,\@libexecdir\@,$(libexecdir),g" < $< > $(top_srcdir)/$@
@INTLTOOL_DESKTOP_RULE@
DISTCLEANFILES = \
$(desktop_in_files) \
$(desktop_DATA)
$(desktop_DATA) $(desktop_in_files)
#---
#dia.desktop: dia.desktop.in $(wildcard $(top_srcdir)/po/*.po)
# $(INTLTOOL_MERGE) $(top_srcdir)/po $< $(@) -d -u -c $(top_builddir)/po/.intltool-merge-cachemake
dia.desktop.in: $(top_srcdir)/dia.desktop.in.in $(wildcard $(top_srcdir)/po/*.po)
$(INTLTOOL_MERGE) $(top_srcdir)/po $< $(@) -d -u -c $(top_srcdir)/po/.intltool-merge-cachemake
# I'd love to have automake do this substitution for me, but then it'd happen
# before intltool above, and that one doesn't understand builddir and so can't
# use the output.
dia.desktop: dia.desktop.in
sed -e 's/@VERSION/@'$(VERSION)'/;' < $< > $@
distclean-local:
rm -f dia.keys
......
dia-0.96-pre2: 21-Jan-2006
* Second release candidate for 0.96. Main improvements:
* Version 0.7 of VDX plugin by Ian Redfern.
* Text-line rendering in SVG export.
* Keyboard shortcuts for tools now use shift-alt.
* Improvement in autogaps for some objects.
* .desktop file now has current version.
* Change in zoom levels in menus.
* Check that windows are within bounds before opening.
* Various compilation-time improvements.
* UML class improvements on comment and wrapped underlined names.
dia-0.96-pre1: 13-Dev-2006
* First release candidate for 0.96. Main improvements:
* First release candidate for 0.96. Main improvements:
* Text rendering is now based on the TextLine objects, each of which
contain one line of text along with font and font height. This has
......
......@@ -11,8 +11,8 @@ INCLUDES = \
$(LIBART_CFLAGS) \
-DPREFIX=\""$(prefix)"\" \
-DSYSCONFDIR=\""$(sysconfdir)"\" \
-DDIA_DATADIR=\""$(datadir)"\" \
-DDIA_LIBDIR=\""$(libdir)"\" \
-DDATADIR=\""$(datadir)"\" \
-DLIBDIR=\""$(libdir)"\" \
-DLOCALEDIR=\"$(localedir)\" \
-DUIDATADIR=\"$(uidatadir)\"
......
......@@ -778,7 +778,7 @@ create_tools(GtkWidget *parent)
gtk_tooltips_set_tip (tool_tips, button,
g_strconcat(gettext(tool_data[i].tool_desc),
" (", gtk_accelerator_get_label(key, mods), ")"),
" (", gtk_accelerator_get_label(key, mods), ")", NULL),
NULL);
} else {
gtk_tooltips_set_tip (tool_tips, button,
......
......@@ -18,7 +18,7 @@
#undef LOCALEDIR /* needs to be calculated at runtime */
/* NOT: #define LOCALEDIR "../lib/locale" */
#define VERSION "0.96-pre1"
#define VERSION "0.96-pre2"
/*
* We are linking libxml as DLL with either msvc or mingw, but this
......
dnl Process this -*- autoconf -*- file with autoconf to produce a
dnl configure script.
AC_INIT(dia, 0.96-pre1, http://bugzilla.gnome.org/enter_bug.cgi?product=dia)
AC_INIT(dia, 0.96-pre2, http://bugzilla.gnome.org/enter_bug.cgi?product=dia)
AC_CONFIG_SRCDIR(app/diagram.c)
AM_INIT_AUTOMAKE(AC_PACKAGE_NAME,AC_PACKAGE_VERSION)
......@@ -49,7 +49,6 @@ AC_PROG_INTLTOOL(0.21)
APP_LIBS=""
AC_SUBST(APP_LIBS)
dnl Checks for libraries
PKG_CHECK_MODULES(GMODULE, gmodule-2.0 gobject-2.0)
......@@ -448,7 +447,6 @@ AM_CONDITIONAL(WITH_PYTHON, test "x$with_python" != "xno")
AC_OUTPUT(
Makefile
dia.desktop.in
lib/Makefile
lib/pixmaps/Makefile
po/Makefile.in
......
.\" ** You probably do not want to edit this file directly **
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.0).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
.TH "DIA" "1" "2004\-11\-26" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.SH "NAME"
.\"Generated by db2man.xsl. Don't modify this, modify the source.
.de Sh \" Subsection
.br
.if t .Sp
.ne 5
.PP
\fB\\$1\fR
.PP
..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Ip \" List item
.br
.ie \\n(.$>=3 .ne \\$3
.el .ne 3
.IP "\\$1" \\$2
..
.TH "DIA" 1 "2004-11-26" "" ""
.SH NAME
dia \- a diagram drawing program
.SH "SYNOPSIS"
.ad l
.hy 0
.HP 4
\fBdia\fR [\fB\-c\fR] [\fB\-\-credits\fR] [\fB\-e\ \fR\fB\fIOUTPUT\fR\fR] [\fB\-\-export=\fR\fB\fIOUTPUT\fR\fR] [\fB\-L\ \fR\fB\fILAYER,LAYER,...\fR\fR] [\fB\-\-show\-layers=\fR\fB\fILAYER,LAYER,...\fR\fR] [\fB\-h\fR] [\fB\-\-help\fR] [\fB\-n\fR] [\fB\-\-nosplash\fR] [\fB\-s\ \fR\fB\fIWxH\fR\fR] [\fB\-\-size=\fR\fB\fIWxH\fR\fR] [\fB\-t\ \fR\fB\fIFORMAT\fR\fR] [\fB\-\-filter=\fR\fB\fIFORMAT\fR\fR] [\fB\-v\fR] [\fB\-\-version\fR] [file\ ...]
\fBdia\fR [\fB\-c\fR] [\fB\-\-credits\fR] [\fB\-e\ \fIOUTPUT\fR\fR] [\fB\-\-export=\fIOUTPUT\fR\fR] [\fB\-L\ \fILAYER,LAYER,\&.\&.\&.\fR\fR] [\fB\-\-show\-layers=\fILAYER,LAYER,\&.\&.\&.\fR\fR] [\fB\-h\fR] [\fB\-\-help\fR] [\fB\-n\fR] [\fB\-\-nosplash\fR] [\fB\-s\ \fIWxH\fR\fR] [\fB\-\-size=\fIWxH\fR\fR] [\fB\-t\ \fIFORMAT\fR\fR] [\fB\-\-filter=\fIFORMAT\fR\fR] [\fB\-v\fR] [\fB\-\-version\fR] [file\ \&.\&.\&.]
.ad
.hy
.SH "DESCRIPTION"
.PP
\fBDia\fR
is used to create diagrams. Dia has a number of basic tools, like lines and boxes but can also dynamically load
\fIsheets\fR. A sheet is a collection of tools that are used in a certain type of diagram.
\fBDia\fR is used to create diagrams\&. Dia has a number of basic tools, like lines and boxes but can also dynamically load \fIsheets\fR\&. A sheet is a collection of tools that are used in a certain type of diagram\&.
.PP
Most diagram objects in
\fBDia\fR
have
\fIconnection points\fR. Lines can be connected to these connection points and this way graph structures can be formed. When objects are moved or resized the connections will follow the objects.
Most diagram objects in \fBDia\fR have \fIconnection points\fR\&. Lines can be connected to these connection points and this way graph structures can be formed\&. When objects are moved or resized the connections will follow the objects\&.
.PP
Diagrams drawn in
\fBDia\fR
can be exported PostScript.
Diagrams drawn in \fBDia\fR can be exported PostScript\&.
.SH "OPTIONS"
.PP
\fBDia\fR
accepts the following options:
\fBDia\fR accepts the following options:
.TP
\fB\-c\fR \fB\-\-credits\fR
Display credits list and exit.
Display credits list and exit\&.
.TP
\fB\-e \fR\fB\fIOUTPUT\fR\fR \fB\-\-export=\fR\fB\fIOUTPUT\fR\fR
Export loaded file to OUTPUT and exit.
\fB\-e \fIOUTPUT\fR\fR \fB\-\-export=\fIOUTPUT\fR\fR
Export loaded file to OUTPUT and exit\&.
.TP
\fB\-h\fR \fB\-\-help\fR
Display a list of all commandline options.
Display a list of all commandline options\&.
.TP
\fB\-n\fR \fB\-\-nosplash\fR
Do not show the splash screen.
.TP
\fB\-s \fR\fB\fIWxH\fR\fR \fB\-\-size=\fR\fB\fIWxH\fR\fR
Export loaded file in decimal given width and/or height. It is allowed to only select width or height. E.g.
\fB\-\-size=\fR\fB\fI520x\fR\fR
exports an image that is 520 pixels wide, while
\fB\-\-size=\fR\fB\fIx900\fR\fR
exports an image of 900 pixels height.
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
\fBNote\fR
This option is currently only implemented for the PNG export filter.
Do not show the splash screen\&.
.TP
\fB\-L \fR\fB\fILAYER,LAYER,...\fR\fR \fB\-\-show\-layers=\fR\fB\fILAYER,LAYER,...\fR\fR
Only include specified layers when exporting. Layers can be specified either as a layer name, the layer number or a numeric range X\-Y of layers. \-\-show\-layers=background,2\-5 shows the layer named background and layers 2\-5, \-\-show\-layers=2\- shows layers 2 and up.
\fB\-s \fIWxH\fR\fR \fB\-\-size=\fIWxH\fR\fR
Export loaded file in decimal given width and/or height\&. It is allowed to only select width or height\&. E\&.g\&. \fB\-\-size=\fI520x\fR\fR exports an image that is 520 pixels wide, while \fB\-\-size=\fIx900\fR\fR exports an image of 900 pixels height\&.
.RS
.Sh "Note"
This option is currently only implemented for the PNG export filter\&.
.RE
.TP
\fB\-t \fR\fB\fIFORMAT\fR\fR \fB\-\-export\-to\-format=\fR\fB\fIFORMAT\fR\fR
Export loaded file in FORMAT and exit. Format are described below.
\fB\-L \fILAYER,LAYER,\&.\&.\&.\fR\fR \fB\-\-show\-layers=\fILAYER,LAYER,\&.\&.\&.\fR\fR
Only include specified layers when exporting\&. Layers can be specified either as a layer name, the layer number or a numeric range X\-Y of layers\&. \-\-show\-layers=background,2\-5 shows the layer named background and layers 2\-5, \-\-show\-layers=2\- shows layers 2 and up\&.
.TP
\fB\-t \fIFORMAT\fR\fR \fB\-\-export\-to\-format=\fIFORMAT\fR\fR
Export loaded file in FORMAT and exit\&. Format are described below\&.
.TP
\fB\-v\fR \fB\-\-version\fR
Display
\fBdia\fR
version and exit.
Display \fBdia\fR version and exit\&.
.SH "EXPORT FORMATS"
.PP
The following export formats are supported by
\fBdia\fR.
The following export formats are supported by \fBdia\fR\&.
.TP 3
\(bu
cgm
(Computer Graphics Metafile, ISO 8632)
cgm (Computer Graphics Metafile, ISO 8632)
.TP
\(bu
dia
(Native dia diagram)
dia (Native dia diagram)
.TP
\(bu
dxf
(Drawing Interchange File)
dxf (Drawing Interchange File)
.TP
\(bu
eps
or
eps\-builtin
or
eps\-pango
(Encapsulated PostScript)
eps oreps\-builtin or eps\-pango (Encapsulated PostScript)
The format specifications
eps
and
eps\-pango
both use the font renderer of the Pango library, while
eps\-builtin
uses a dia specific font renderer. If you have problems with Pango rendering, e.g. Unicode, try
eps\-builtin
instead.
The format specifications eps and eps\-pango both use the font renderer of the Pango library, whileeps\-builtin uses a dia specific font renderer\&. If you have problems with Pango rendering, e\&.g\&. Unicode, try eps\-builtin instead\&.
.TP
\(bu
fig
(XFig format)
fig (XFig format)
.TP
\(bu
mp
(TeX MetaPost macros)
mp (TeX MetaPost macros)
.TP
\(bu
plt
or
hpgl
(HP Graphics Language)
plt or hpgl (HP Graphics Language)
.TP
\(bu
png
(Portable Network Graphics)
png (Portable Network Graphics)
.TP
\(bu
shape
(Dia Shape File)
shape (Dia Shape File)
.TP
\(bu
svg
(Scalable Vector Graphics)
svg (Scalable Vector Graphics)
.TP
\(bu
tex
(TeX PSTricks macros)
tex (TeX PSTricks macros)
.TP
\(bu
wpg
(WordPerfect Graphics)
wpg (WordPerfect Graphics)
.TP
\(bu
wmf
(Windows MetaFile)
wmf (Windows MetaFile)
.LP
.SH "FILES"
.PP
\fBdia\fR
creates a directory
\fI.dia\fR
in the user's home, which contains different files to store user preferences. To reset
\fBdia\fR
to it's default behaviour, just remove the respective file:
\fBdia\fR creates a directory \fI\&.dia\fR in the user's home, which contains different files to store user preferences\&. To reset \fBdia\fR to it's default behaviour, just remove the respective file:
.TP 3
\(bu
\fIdefaults.dia\fR: contains default values for elements (XML format).
\fIdefaults\&.dia\fR: contains default values for elements (XML format)\&.
.TP
\(bu
\fIdiarc\fR: keeps
\fBdia\fR
preferences (ASCII).
\fIdiarc\fR: keeps\fBdia\fR preferences (ASCII)\&.
.TP
\(bu
\fIhistory\fR: keeps the list of last edited diagrams (ASCII).
\fIhistory\fR: keeps the list of last edited diagrams (ASCII)\&.
.TP
\(bu
\fImenurc\fR: contains an automated accelerator map dump (Lisp).
\fImenurc\fR: contains an automated accelerator map dump (Lisp)\&.
.TP
\(bu
\fIpersistence\fR: contains GUI information, e.g. open windows (XML).
\fIpersistence\fR: contains GUI information, e\&.g\&. open windows (XML)\&.
.TP
\(bu
\fIpluginrc\fR: the list of loaded plugins (XML).
\fIpluginrc\fR: the list of loaded plugins (XML)\&.
.LP
.SH "SEE ALSO"
.PP
[1]\&\fIPango\fR
Pango: \fIhttp://www.pango.org/\fR
.PP
X (1)
.PP
xfig (1)
.PP
inkscape (1)
.SH "COPYRIGHT"
.PP
Copyright 1999 Alexander Larsson.
Copyright 1999 Alexander Larsson\&.
.PP
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation\&.
.SH "AUTHORS"
.PP
Alexander Larsson
.PP
This manual was written by
Fredrik Hallenberg.
.SH "AUTHOR"
Fredrik Hallenberg <hallon@lysator.liu.se>, W. Borgert <debacle@debian.org>, Alan Horkan <horkana@tcd.ie>.
.SH "REFERENCES"
.TP 3
1.\ Pango
\%http://www.pango.org/
This manual was written by Fredrik Hallenberg\&.
.SH AUTHORS
Fredrik Hallenberg, W\&. Borgert, Alan Horkan.
......@@ -8,7 +8,7 @@
[
<!ENTITY VERSION "0.96-pre1">
<!ENTITY VERSION "0.96-pre2">
<!ENTITY INTRODUCTION SYSTEM "intro.xml">
......
<chapter label="9" id="layers-chapter">
<title>Managing Layers</title>
<!-- (introductory info...) -->
<sect1 id="layers-introduction">
<title>Introduction to Layers</title>
<para>
In <application>Dia</application>, <emphasis>layers</emphasis> are managed through the <interface>Layers Dialog</interface> and all layers related operations can be achieved from this dialog.
</para>
<para>
As a general purpose, layers aim at being a shortcut for grouping related objects within a diagram. They allow you to isolate the different parts of a diagram, in the way which you can decide to show only certain parts of it and not some others will stay hidden even when exporting or printing the diagram. Use --show-layers command line switch to control which layers are visible when batch exporting.
</para>
<para>
Inside a layer, any operation you would like to perform on objects are possible through the <interface>Main Popup Menu</interface>, then you can act on objects just the way you use to.
</para>
<note>
<para>
Only objects present in the current layer can be selected.
If an object doesn't want to be selected, you should check if it is
laying in the current layer or not.
</para>
</note>
<para>
By default, each new diagram comes with the default layer which it's
called the <emphasis>Background</emphasis> layer.
Of course you can change its name and settings to customize it to your
needs as you can do with any other layer.
In <application>Dia</application>, diagrams consist of the canvas object, layer objects, and diagramming element objects. The layer object can be likened to that of a sheet that sits on top of a canvas. Each sheet can then have diagramming elements added to it to make up a diagram. Each diagram consists of at least one layer and each diagram can consist of as many layers as required by the diagramming author.
</para>
<para>
You can create as many layers as you want, <application>Dia</application> will put a new layer on top of all the layers have been already created. <emphasis>Layers</emphasis> can be thought as a stack of transparent papers. Meaning you will be able to change their stack order, decide whether or not to show them, draw any number of objects onto them and so on.
</para>
<para>
All this can be managed through the <interface>Layers Dialog</interface>.
As a general purpose, layers aim at being a shortcut for grouping related objects within a diagram. They allow you to isolate the different parts of a diagram, in the way which you can decide to show only certain parts of it and not some others will stay hidden even when exporting or printing the diagram.
</para>
<tip>
<para>
Use the --show-layers command line switch to control which layers are visible when batch exporting.
</para>
</tip>
<para>
Inside a layer, any operation you would like to perform on objects are possible through the Main Popup Menu, then you can act on objects just the way you use to.
</para>
<tip>
<para>
Only objects present in the current layer can be selected. If an
object doesn't want to be selected, you should check if it is
laying in the current layer or not.
</para>
</tip>
<para>
Each new diagram comes with the default layer labelled “Background”. Of course you can change its name and settings to customize it to your needs as you can do with any other layer.
</para>
<para>
You can use layers to create overlay slide show by drawing each incremental slide in a
......@@ -50,11 +47,17 @@
<!-- we should probably drop the related icons in front of each
subsection, that way we won't have to describe them and
the user to find them into the dialog box faster, what
do you think ? -->
do you think ?
I think its a great idea and could go in for the next chapter revision - TBogie -->
<para>
The Layers dialog is used to manage the order and visibility of each layer in a diagram.
</para>
<sect2 id="create-layers">
<title>Create a New Layer</title>
<para>
Creating a new layer is possible by clicking on the <guibutton>New Layer</guibutton> button at the bottom left of the dialog. Since the <interface>Layers Dialog</interface> is not diagram specific but application specific, you will have to choose in wich diagram the new layer must go in. To do so, at the top of the <interface>Layers Dialog</interface>, select the diagram you wanted to receive the new layer and then add this new layer to the selected diagram.
Creating a new layer is possible by clicking on the New Layer button at the bottom left of the dialog. Since the Layers dialog is not diagram specific but application specific, you will have to choose in which diagram the new layer must go in. To do so, at the top of the Layers dialog, select the diagram you wanted to receive the new layer and then add this new layer to the selected diagram.
</para>
<para>
The newly created layer will be placed on top of the stack and will become the current layer of the selected diagram.
......@@ -67,105 +70,86 @@
<sect2 id="selecting-layers">
<title>Selecting Layers</title>
<para>
A layer is said as being activated when it is selected in the
<interface>Layers Dialog</interface>.
To select a layer simply click on its name in the dialog,
that will highlight it. From now, any changes you will make to the
diagram will affect this layer and only this one.
A layer is said as being activated when it is selected in the <interface>Layers dialog</interface>. To select a layer simply click on its name in the dialog. The selected layer will then become highlighted. Changes to the diagram are made to the currently selected layer only.
</para>
<note>
<para>
You'll be able to select only one layer at the time.
That way you can do anything you like in this selected layer without
affecting other layers on your diagram.
Only one layer can be selected at a time. That way you can do anything
you like in this selected layer without affecting other layers on your diagram.
</para>
</note>
</sect2>
<sect2 id="ordering-layers">
<title>Ordering Layers</title>
<para>
Next to the <guibutton>New Layer</guibutton> button at the bottom of the <interface>Layers Dialog</interface>, are two useful buttons which allow you to set the stack order of each layer you created.
</para>
<para>
Those two buttons are used to raise and lower layers in the hierarchy of layers. The button with the up arrow is used to raise the active layer while the other is for lower the position within the hierarchy.
</para>
<para>
Ordering layers can be useful when you want hide some parts of an object with another one.
</para>
<para>
Next to the <guibutton>New Layer</guibutton> button at the bottom of the <interface>Layers dialog</interface>, are two useful buttons which allow you to set the stack order of each layer you created.
</para>
<para>
Those two buttons are used to raise and lower layers in the hierarchy of layers. The button with the up arrow is used to raise the active layer while the other is for lower the position within the hierarchy.
</para>
<para>
Ordering layers can be useful when you want hide some parts of an object with another one.
</para>
</sect2>
<sect2 id="deleting-layers">
<title>Deleting Layers</title>
<para>
When a layer is not needed anymore you can delete it and all the objects
it contains by clicking on the <guibutton>Delete Layer</guibutton> button. Of course this will only affect the currently selected layer.
</para>
<para>
Doing so on regular basis is the better way to keep your diagram clean and light for when you want to export it to another format than the native <application>Dia</application> format.
</para>
<para>
Note you should be aware of any diagram you created must at least contains one layer, only because a diagram is built of layer, so a diagram doesn't contain any layer should be considered as a corrupted diagram and won't be suitable to export nor even save in the native <application>Dia</application> format.
</para>
<para>
When a layer is not required you can delete it. When deleting a layer, it and all of the objects contained in the layer are removed from the canvas. Layers are deleted by clicking on the <guibutton>Delete Layer</guibutton> button. Of course this will only affect the currently selected layer.
</para>
<para>
Doing so on regular basis is the better way to keep your diagram clean and light for when you want to export it to another format other than the native <application>Dia</application> format.
</para>
</sect2>
</sect1>
<sect1 id="viewing-layers">
<title>Viewing Layers</title>
<para>
Now that you've seen what are the basics of manipulating layers, you will more easely understand why <emphasis>layers</emphasis> are such a powerful tool when you are building a diagram with <application>Dia</application>.
</para>
<para>
Understanding what layers are for can dramaticaly improve the quality and the visual effect your diagrams will produce.
</para>
<para>
For instance, imagine you are building a diagram with lots of objects in it, like an Electrical or UML diagram, if you drop all of your objects in the same layer, meaning the background, after a while you will get a huge unmanageable draft you won't be able to do anything with it. It will be a pain to change anything in it, you will waste time trying to remenber what object is connected to that object which seems to take all the place in the middle of the mixed up objects you already put there.
</para>
<para>
Since <application>Dia</application> is a <emphasis>Structured Diagram Builder</emphasis>, all the diagrams you will build with it will be naturaly structured and broken down in many little pieces you will manage with more ease and efficiency than you could do it with a single monolythic block of objects.
</para>
<note>
<para>
By definition, a diagram should be structured, so breaking it down in several logical parts won't be as hard as it seems to be. That's where <emphasis>layers</emphasis> becomes of first use. They allow you to isolate each of these parts in separated slides, so it becomes a real pleasure to manipulate them in any way you like.
</para>
</note>
<sect2 id="renaming-layers">
<title>Renaming Layers</title>
<para>
Layers can be renamed to express the part of the diagram they represent, giving them the ability to be rapidly located among others. Most importantly, layers can be shown or hidden depending on what part of the diagram you would like to show.
</para>