Re: [Inkscape-user] autosave ?
by MenTaLguY
On Sat, 2004-06-19 at 18:04, Florent wrote:
> So I'm appealing to anyone who can create an autosave :-)
We already have autosave-on-crash already, actually. The one catch is
that for crashes due to failed assertions (like this one), it isn't
triggered yet.
(I'm CCing the development mailing list, if anyone's interested in
attacking this right now:
At least on Unix, this is relatively easy to fix -- just set up a
SIGABRT handler similar to the SIGSEGV handler we have now. The one
catch is that the handler will need to disable itself as soon as it is
triggered, because the autosave code raises SIGABRT when it is done.
Also we should make sure we've got SIGBUS covered if we don't already.)
-mental
17 years, 11 months
Freehand drawing tool
by Bryce Harrington
There'd been some comments about the quality of the Inkscape drawing
tool compared with Sodipodi. I experimented around a bit with both. I
see what they mean, but it's difficult to quantify the issue.
Inkscape's drawing tool "feels" snappier, it doesn't lag like Sodipodi,
and it produces lines smoothly, but it just doesn't "feel" right.
I can't draw worth beansy, but I could see the difference when I tried
writing my name:
http://bryceharrington.com/freehand_drawing.png
Try signing your name with the two apps and see if you notice a
difference.
Bryce
18 years
layer commands we need
by bulia byak
Here's a list of layer commands that we need to implement, comments
and additions welcome:
Layers... // opens the Layers dialog
-------------------
Move to Layer Above Shift+PgUp
// move selection to the top of sibling layer above, or to the
top of parent layer (but not root) if no siblings
Move to Layer Below Shift+PgDn
// move selection to the top of sibling layer below, or to the
bottom of parent layer (but not root) if no siblings
Move to Layer... // let me choose the
layer name to move selection to
-------------------
Unlock All Layers // unlock all layers in the document (or
all siblings of the current layer?)
Unhide All Layers
-------------------
Unlock All in Layer // unlock all children of the current layer
Unhide All in Layer
-------------------
Group to Layer // convert group to layer
Layer to Group
18 years
CFV: Gtkmm - Implement preferences class
by Bryce Harrington
Here is a task needed for the gtkmm codebase.
Requires good knowledge of C++, ok knowledge of XML, and at least
passing knowledge of the Inkscape codebase.
Preferences
===========
Design an Inkscape::Preferences class that wrappers an SPRepr. It must
provide the following public interface as a minimum:
gboolean save(const gchar *filename);
gboolean load(const gchar *filename);
SPRepr* getRepr(const gchar *key);
Look in inkscape.* for the C-versions of the above routines.
* Hook up the preferences functions in ui/dialog/dialog.cpp
To learn more, check out the gtkmm codebase like this:
$ cvs -d:pserver:anonymous@...54...:/cvsroot/inkscape login
(hit enter for password)
$ cvs -z3 -d:pserver:anonymous@...54...:/cvsroot/inkscape co experimental/bryce/inkscape_gtkmm
$ cd experimental/bryce/inkscape_gtkmm
$ make
$ ./inkscape
Also look in the PLAN file for more todo's and projects' in the gtkmm
codebase.
Bryce
18 years, 2 months
restore ruler units
by Aaron Spike
There has been some talk about units lately and I have a question.
Please excuse me if this is what you've been talking about and I didn't
catch it.
The units in my template are mm. If I create a new document and change
the units to inches the rulers change to inches. But If I save that
document, close and open it again the ruler units are once again mm. And
even more I have so far been unable to change them back to inches. I
think Inkscape thinks they are already inches.
Do other people experience this?
Aaron Spike
18 years, 2 months
Re: [Inkscape-devel] Suggestion for the preferences dialog
by Bryce Harrington
On Tue, 28 Dec 2004, Andreas Nilsson wrote:
> >What approach did you use to create this mockup?
> >
> >I gave a shot at trying to mock up something with glade, but with
> >disappointing results. However this definitely looks doable.
> >
> >Bryce
> >
> >
> Well, I used the Gimp...
Cool, it looks really good. I'm not sure if we'll be able to replicate
it exactly, but I think we should strive to get as close as we can -
this looks extremely good.
> I am trying to learn Glade, but so far, all my attempts have been
> unsuccesfull.
Yeah same here, I thought it might provide a shortcut to having to
implement the tree management stuff, but no such luck. It does not
appear to generate code for managing tree widgets, and the stuff that it
can do well is reasonably straightforward to do by hand.
Anyway, so I'd say, stick with gimp. ;-)
> I do really hope that I have not created an uncodable monster here. :)
> - Andreas Nilsson
Nah, it'll just be a considerable challenge. :-)
In fact, I had noticed earlier that we needed tree-oriented editing
dialogs for several other purposes - the XML tree, layers, extensions,
and possibly keyboard layouts. I was going to emulate the XML editor
design, but what you've done for the preferences dialog looks like it
provides the same basic capabilities, and I'm thinking that if we can
implement this design, we can reuse it in at least 4 places.
One alteration I'm considering in order to support the other kinds of
dialogs is a toolbar on the top of the dialog (see the XML editor). For
the XML editor this is used for adding/moving/deleting nodes. How do
you think we could use this in the preferences dialog? Perhaps the help
button could be moved up there (saving some space on the bottom of the
screen?) Perhaps an 'export preferences' function? 'restore defaults'?
The other thing I'm wondering is that some people are going to really
like the extra space between widgets in the dialog (and it helps us
adhere to the HIG, as you point out), however others will prefer more
concise use of space in order to maximize the dialogs they can have open
at once. Preferences are unlikely to be something people will want to
have up all the time, and same with extensions, however with the XML
editor and layers I'm not as sure - what do you think?
Bryce
18 years, 2 months
Volunteer work and an idea how to get into existing code bases
by Felix Rabe
Hi Bryce,
It's a shame that I only saw your calls for volunteer work now that you
replied to them yourself... But I think this is an excellent idea to
invite new developers! There needs to be more of it, or maybe it just
needs to be more visible (like with a tag in the subject, eg. "[CFV]"
for "Call For Volunteers").
In fact, I was looking for an easy way to familiarize myself with
existing (poorly or barely documented) code bases and came up with this
(as yet sadly unimplemented) idea: Look for a bug that has been fixed
sometime in CVS and get a diff for the fix.
I think it might be another good invitation and might add value to code
documentation if some good (ie. easy) fixes and enhancements were
pointed out in the Wiki by the developers that commited them to CVS or
by the newbies that found the diffs and found them to be straightforward.
If I someday get to implement this idea, should I start a Wiki page?
(This might take a few months though...) Or is somebody else willing to
do it? Or is it a not-so-god (bad) idea altogether?
Greetings,
Felix
18 years, 2 months
Re: [Inkscape-devel] Inkscape 0.41 release plans
by Ben Crowell
>Also Ben Crowell's Perl
>scripts and XSLT scripting are very nice features that should be more
>accessible, if possible, via the Scripts dialog or otherwise.
Incorporating some of the Perl scripts would be fun, and I'd like to do it.
However, IIRC there is still only a sketch of an API? Give me an API, and
I'll get to work. Basically I need:
- a way to get an svg file as input, and send it back as output
- a way to report errors (including errors due to not having the right
CPAN modules installed)
- a way to get input strings from the user
- a way to display some documentation to the user about what this script
does
- provisions for internationalizing all the strings the user will see
Also, some of my scripts have known unixisms, which I can clean
up, but I will still need help with testing on Windows, since I don't
have a Windows box.
18 years, 2 months
CVS not compilable
by bulia byak
1. In src/io/Makefile_insert, several files are listed with
InitialCaps but they are actually all-lowercase, so make fails.
2 After fixing 1, I get:
io/xsltstream.cpp: In member function `virtual void
Inkscape::IO::XsltOutputStream::flush()':
io/xsltstream.cpp:183: error: `xmlErrorPtr' undeclared (first use this function)
io/xsltstream.cpp:183: error: (Each undeclared identifier is reported
only once for each function it appears in.)
io/xsltstream.cpp:183: error: syntax error before `=' token
io/xsltstream.cpp:184: error: `err' undeclared (first use this function)
Please fix these ASAP, and please be careful to not leave CVS in
uncompilable state, especially on holidays when it may be hard to
reach people.
18 years, 2 months
CFV: Update Inkscape FAQ
by Bryce Harrington
Here's another Call for Volunteers...
The Inkscape FAQ is pretty good, but it's been a long time since someone
did a thorough review of it and brought it up to date.
We need someone who is reasonably knowledgeable about Inkscape to go
through it and bring it a little more up to date. I think it probably
also ought to have a table of contents with links to the Q's...
1. Save this webpage to your disk: http://inkscape.org/faq.php
2. Open it in a text editor
3. Review/revise each question
4. Add new questions you think are worth putting in
5. Remove any questions that are obsolete
6. Post your results here for a web guy to put on the site
If you already have access for updating the Inkscape site, feel free to
commit and update directly.
Bryce
18 years, 2 months
