doxygen updates
by Kees Cook
Okay, the website doxygen should update every night around 3am Pacific
time now.
--
Kees Cook @outflux.net
18 years, 7 months
close confirmation fix
by unknown＠example.com
FWIW, forgot to mention that I think I fixed the close confirmation
dialog last night. Try it out and see if it works as expected..
18 years, 7 months
Setting physical resolution and exporting documents
by unknown＠example.com
Hello!
I would like to set the physical resolution of a document to export it
as an EPS file at a given resolution. However, I have not found setting of
the
resolution anywhere in the program. In the "print" menu there is a physical
resolution option for the printed images, but it did not work for the EPS
files.
Another problem is exporting of the documents. It is possible by renaming
the file by "save as", and so to export a document without changing its
name a double rename is needed, what might be error prone.
Thanks,
Artur Rataj
18 years, 7 months
Inkscape status 2005-02-15
by Bryce Harrington
Project Status
Tuesday, Feb 15, 2005
Today at work after our all-hands meeting, one of the marketing guys
named Carl grabbed me. He'd just upgraded to SuSE 9.2 but knew that
we'd just released 0.41, and SuSE only had 0.39. We downloaded and
installed the Autopackage version. I gave him a quick tour of the new
features. When we got to the color trace function he slapped me on the
shoulder, "My god, that's _exactly_ what I've needed!!" He loaded up
one of the OSDL member logos and vectorized it with the color trace
tool. We get these logos in every format known to mankind, and scaling
them can be a real challenge sometimes.
This week I've been showing off all sorts of things to people... The
new inkscape.deviantart.com. I showed daj's "Rockin' in the Free World"
to a professional musician. ScislaC's 'Gaze' astounds _everyone_ who
sees it; this is without a doubt the most advanced piece of art ever
done with Inkscape/Sodipodi/Gill (we have *got* to encourage Scislac to
teach us all the tricks for how he was able to *do* that!) I also of
course have to brag about the KDE 3.4 SVG Wallpaper contest, and that of
the top 4, half are known to have been done with Inkscape (including the
winner).
The thing I point out to people at work is that despite how great Linux
is technically, there are many, many people who "judge a book by its
cover" and consider only how the thing looks. Like buying a car based
on its paint job and leather upholstry instead of its engine. But
graphical tools like Inkscape are enabling artists to give Linux that
beauty, to make it visually as well as technically attractive.
In the stats below, the most obvious thing is the sudden jump in
linecount. No surprise there - this is all the new code such as gtkmm
that finally got greenlighted to go into the codebase. Hopefully over
the next few months we'll see the linecount reduced as this new code
replaces the gobs of repetitive old code currently in there.
The mailing list numbers show that we've gained a number of new
members. (Welcome aboard!) Of course, anyone on Jabber or IRC recently
will have already noticed the nice jump in activity, both with usage
questions and with development work. Things seem to be going quite
well!
Statistics Jan 1 Jan 15 Feb 1 Feb 15
========== ===== ====== ===== ======
Lifetime Rank on SourceForge: 598 570 569 569
(95.8%) (96.0%) (96.0%) (96.04%)
Max Week's Rank on SourceForge: 45 59 * *
(99.8%) (99.6%) * *
Total SF Page Views 2,213,324 2,283,160 2,296,458 2,296,458
Total SF Downloads 110,182 114,695 115,645 115,645
Total Freshmeat URL Hits 14,291 14,634 15,108 16,448
Total Freshmeat Subscriptions 149 151 156 169
Lines of Code in src/: 321,883 323,251 323,324 333,139
Code lines 227,114 227,965 227,872 234,651
Comment line 56,048 56,308 56,438 58,239
Blank 45,398 45,664 45,624 46,859
Lines of Docs in doc/: 17,901 17,901 17,918 26,848
Lines of content in website: 9,234 9,328 9,486 9,776
Size of the Inkscape wiki: 21,030 20,931 23,576 24,925
Bugs open/total: 135/829 145/858 148/917 155/972
Features open/total: 340/514 353/530 352/556 370/579
Patches open/total: 5/145 6/148 7/154 5/167
CVS Commits (as per inkscape-cvs) 9,450 9,625 9,975 10,312
Inkscape-devel membership: 132 131 143 151
Inkscape-announce membership: 147 155 166 169
Inkscape-user membership: 172 177 181 193
Num Translations: 33 33 33 33
Ave Translation Ratio: 43.7 42.0 44.7 47.8
* - Statistics unavailable
18 years, 7 months
Re: [Inkscape-user] Stroke paint >Pattern
by Ted Gould
On Mon, 2005-02-14 at 11:56 -0400, bulia byak wrote:
>On Mon, 14 Feb 2005 16:47:47 +0100, Jakub Steiner <jimmac@...659...> wrote:
>> Looking at it from the interface perspective, I'd call it a brush.
>
>Yes, that's the best term.
>
>> You
>> could convert an object into a brush, just like you can now convert an
>> object into a pattern.
>
>And adjust things like spacing, rotation, randomization...
>
>> Once you has a brush you could then use it on an
>> object as another property (fill, stroke).
>
>I don't think it can be used on fill, only on stroke. Actually, brush
>strokes will be their own kind of objects (implemented as SVG <g> with
>extension attrs) so they won't have any fill.
I was curious if this functionality could be implemented using markers.
Perhaps subdivide the path and place the "brush strokes" on the nodes so
that you'd get a brush effect kinda like GIMP. It might be difficult to
do brushes that change over time though...
--Ted
PS - Took this thread to devel, it was on user.
18 years, 7 months
Re: [cairo] The Great API Shakeup (fwd)
by PLinnell
> Message: 9
> Subject: Re: [Inkscape-devel] [cairo] The Great API Shakeup (fwd)
> From: MenTaLguY <mental@...3...>
> To: Craig Bradney <cbradney@...242...>
> Cc: Inkscape ML <inkscape-devel(a)lists.sourceforge.net>
> Date: Tue, 15 Feb 2005 20:51:30 -0500
>
>
<snip>
>
> I'd strongly recommend you folks put someone on the cairo mailing
> list as an interface, since feedback from a project like Scribus
> that is actively using cairo will be helpful to them.
>
> -mental
>
Done.
18 years, 7 months
[cairo] The Great API Shakeup (fwd)
by Bryce Harrington
This last weekend, several cairo developers happened to be in the same
physical room, (as part of XDevConf[*]).
We took advantage of the opportunity and had a very productive meeting
last night in which we tried to discuss as many open API issues as
possible.
The following people were involved in this ad-hoc meeting:
Kristian Høgsberg, David Reveman, Keith Packard, Owen Taylor, Carl Worth
The meeting was also attended by Jim Gettys and Bdale Garbee, without
whose support we could not have been productive.
Kristian took some good notes on the discussion last night, which
we'll be cleaning up and sending out as a bunch of separate proposals
to the list. Hopefully this stream of little proposals will be easier
to digest than one giant summary of the meeting. And, this way any
sub-discussions that spin off should be easier to manage.
We'll include "API Shakeup" in each of the proposals, and we'll try to
tie them into existing open threads as appropriate. Each
mini-proposal will be followed up with a patch proposal to implement
the change, (and each patch must include documentation).
Then, of course, once any new discussion settles down, we can start
committing all of this stuff. The scope of the changes means that all
existing cairo-using code will have to be updated, (eg. we have a
proposal that changes cairo_create). So, the breakage will be a bit
painful. But hopefully, the work needed to bring forward any single
piece of code will actually be quite minor.
As this process wraps up, we'll pull together a single-source guide on
what people need to do to get their code updated.
Anyway, this should be a lot of fun. And we should have an
easier-to-use, and less warty API when we're done.
If anyone has pet peeves regarding API issues in cairo, this will be
the time to bring them up, because we won't want to go through many
more break-every-application changes again for quite some time.
-Carl
[*] X Developers' Conference
http://freedesktop.org/wiki/Software/XDevConf
_______________________________________________
cairo mailing list
cairo@...278...
http://lists.freedesktop.org/mailman/listinfo/cairo
18 years, 7 months
[Fwd: Translation update - spanish]
by Lucas Vieites
Previous message got rejected due to .zip attachment, I'm attaching it
in tar.bz2 format now, cheers.
--------- Mensaje reenviado --------
>De: Lucas Vieites <lucas@...212...>
>Para: Inkscape Devel List <inkscape-devel(a)lists.sourceforge.net>
>Asunto: Translation update - spanish
>Fecha: Fri, 11 Feb 2005 11:24:05 +0100
> Hi, I'm attaching an updated es.po file. A couple of fuzzies and
>untranslated were left behind (a total of 4-5).
>
> By the way, I was invited today to give a "hands-on" tutorial on
>Inkscape at a free-software meeting next month in Extremadura, a region
>in Spain that started to develop their own Debian-based Linux
>distribution ("Linex", www.linex.org) for use in schools and local
>administrations. Any suggestions?
> I was planning to do a quick tour through the tutorials included in
>Inkscape and a few live demos.
>
>
> Cheers,
--
Lucas Vieites Fariña
Asix Informática <info@...212...>
http://www.asixinformatica.com/
Tel/Fax: +34 986 54 26 98
18 years, 7 months
save-on-close issue
by MenTaLguY
Seems the problem is this rather evil bit of code in
sp_dtw_desktop_shutdown:
> if (doc && (((GObject *) doc)->ref_count == 1)) {
Guess I was right about having exposed an existing bug.
This is wrong for two reasons:
1. objects other than SPDesktops can reference SPDocuments, and there
are non-inter-object-reference uses for refcounts: the wrong value being
used for the wrong concept
2. GObject::ref_count is sort of an internal field (in the words of the
glib API documentation, "All the fields in the GObject structure are
private to the GObject implementation and should never be accessed
directly.")
The most obvious fix is to specifically keep a count of related active
desktops in the SPDocument, and do a similar test with that.
However, should we count SPDesktops, or more generally all SPViews (for
example the preview view)?
Is SPDocument necessarily the place to actually keep track of that, or
should it be e.g. the Inkscape Application object?
-mental
18 years, 7 months
