visible, printable and wxSVG
WxSVG (wxsvg.sf.net) is a young GPL project that as still never released files, since it as not reach beta stage. First commit should occur in January 2005.
WxSVG let you "draw" GUI with Inkscape. Have a look to screenshots at http://sourceforge.net/project/screenshots.php?group_id=124832
It consist of a thin layer of python classes that derive from wxPython controls classes. It use SVG elements to layout controls such as buttons or panels and map them with some pieces of bitmap cut-out from one or two (on & off) bitmaps exported from Inkscape.
SVG elements that are used to layout controls are <rect> and <g>. We were used to use the non-printable feature of Inkscape to let us draw layout rect's over the visible GUI design, and the export the GUI image without control rect's.
We have upgraded to yesterday's CVS snapshot. No more non-printable feature... And invisible elements are exported in bitmaps. So we cannot work anymore in the same way... The only way I found is to set global transparency for the "Control" group to 0.0 when exporting bitmap, ant to 1.0 when working on.
Non-printable object was a very nice feature. WxSVG is really need it. Is there any other solution ?
Except guide-lines is there anything that Inkscape can show but not export ?
Edouard.
On Tue, 7 Dec 2004, Edouard TISSERANT wrote:
WxSVG (wxsvg.sf.net) is a young GPL project that as still never released files, since it as not reach beta stage. First commit should occur in January 2005.
WxSVG let you "draw" GUI with Inkscape. Have a look to screenshots at http://sourceforge.net/project/screenshots.php?group_id=124832
Whoa, this looks very cool! Can't wait to see it become available! :-)
I don't know the details about the removal of the non-printable feature. I suspect it was intended to keep the capability but don't know the background of the change.
Bryce
And invisible elements are exported in bitmaps.
Arrgh. That's a bug. Sorry. Of course a hidden object must not export. I will fix it now.
Non-printable object was a very nice feature. WxSVG is really need it. Is there any other solution ?
No, hiding objects is what you really need. Non-printability is a non-compliant, evil hack that would not work in any other SVG renderer anyway.
Still better is putting the on/off object into a layer and hiding that layer. This is more convenient because it's easy to access such a layer (it's still in the list of layers). Layers can nest forming a tree.
On Tue, 7 Dec 2004 15:07:32 -0500, bulia byak <buliabyak@...400...> wrote:
And invisible elements are exported in bitmaps.
Arrgh. That's a bug. Sorry. Of course a hidden object must not export. I will fix it now.
Now fixed in CVS. Hidden stuff is not exported or printed now. Please use the CVS version.
And invisible elements are exported in bitmaps.
Arrgh. That's a bug. Sorry. Of course a hidden object must not export. I will fix it now.
Now fixed in CVS. Hidden stuff is not exported or printed now. Please use the CVS version.
Thanks !!!
That fix was not in CVS early this morning (??) but now that's OK.
Gentoo users : Here is the customized inkscape-CVS ebuild I presently use to keep my gentoo up-to-date. This may be usefull for gentoo adicts that have problems with exporting invisible elements. Copy it to your portage overlay in media-gfx/inkscape and run ebuild digest on it before emerging. Have a look to portage docs for more help.
----cut-here--------------------------- # Copyright 1999-2003 Gentoo Technologies, Inc. # Distributed under the terms of the GNU General Public License v2 # This is not the 1.0 version ! This is a cvs ebuild # By Dell'aiera Pol (id jabber: pol@...592...) # Just put this file in /usr/portage/media-gfx/inkscape/ then run 'emerge inkscape' # Report bug @ blenderman@...593... or via jabber.
ECVS_MODULE="inkscape" ECVS_CVS_OPTIONS="-dP" ECVS_SERVER="cvs.sourceforge.net/cvsroot/inkscape"
inherit cvs
USE="sdl jpeg png mozilla truetype static python"
S=${WORKDIR}/${ECVS_MODULE}
DESCRIPTION="A SVG based generic vector-drawing program" HOMEPAGE="http://www.inkscape.org/"
LICENSE="GPL-2 LGPL-2.1" SLOT="0" KEYWORDS="x86 ~ppc ~amd64" IUSE="gnome mmx"
RDEPEND=">=x11-libs/gtk+-2.4.0 >=dev-cpp/gtkmm-2.4 >=media-libs/libart_lgpl-2.3.16 >=dev-libs/libxml2-2.6.4 virtual/xft media-libs/fontconfig dev-libs/boehm-gc dev-libs/popt sys-libs/zlib media-libs/libpng >=dev-libs/libsigc++-2.0.3 gnome? ( >=gnome-base/libgnomeprint-2.2 >=gnome-base/libgnomeprintui-2.2 )"
DEPEND="${RDEPEND} sys-devel/gettext dev-util/pkgconfig >=dev-util/intltool-0.29"
src_compile() { ln -s /usr/share/libtool/ltmain.sh ./ ./autogen.sh || die G2CONF="${G2CONF} --with-xft --with-popt" use mmx || G2CONF="${G2CONF} --disable-mmx" use gnome && G2CONF="${G2CONF} --with-gnome-print"
econf || die cp src/inkscape_version.h.mingw src/inkscape_version.h emake || die
}
src_install() { DOCS="AUTHORS COPYING ChangeLog HACKING NEWS README" make DESTDIR=${D} install || die } ----cut-here---------------------------
bulia byak wrote: ...
Non-printable object was a very nice feature. WxSVG is really need it. Is there any other solution ?
No, hiding objects is what you really need. Non-printability is a non-compliant, evil hack that would not work in any other SVG renderer anyway.
...
Just out of curiosity, does InkScape support CSS? If so, it could be done through media types.
Just out of curiosity, does InkScape support CSS? If so, it could be done through media types.
Our CSS support is incomplete, and we don't support media types yet. But yes, we have discussed already that if, in the future, we'll want to extend the simple hide/show system we have now, it'll be done via CSS media types.
participants (4)
-
Bryce Harrington -
bulia byak -
Edouard TISSERANT -
Jasper van de Gronde