headers
Bryce Harrington | 1 Dec 2007 06:10
Gravatar

Launchpad Tips & Tricks: Graphs

Hi all,

I asked Brian Murray if he'd include Inkscape in his bug plots, and he
has.

Total number of New bugs for the past week:

  http://people.ubuntu.com/~brian/project-graphs/inkscape/plots/inkscape-week-new.png

Here's the number of untriaged bugs for the past day:

  http://people.ubuntu.com/~brian/project-graphs/inkscape/plots/inkscape-1day-undecided.png

I like using the above type of chart when I'm doing triaging, so you can
see the effects of your labors.  There's a certain joy in pushing the
next hour's dot on the graph down, that helps when the triaging work
starts getting monotonous.  ;-)

There's all manner of variations in status and time duration, too,
although most are boring at the moment:

  http://people.ubuntu.com/~brian/project-graphs/inkscape/plots/

If the rendering style looks familiar, you're right!  Brian uses
gnuplot's svg output feature, then post-renders them to png using
Inkscape.  :-)

Bryce

-------------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael Grosberg | 1 Dec 2007 10:00
Picon
Favicon

Re: NEW: Grid visibility and snap enabling

 <J.B.C.Engelen <at> ...> writes:

> 
> Hi all,
> 
> I just added two checkboxes to the grid settings:

Thanks for the improvements to snap. I was wondering, while you are at it, how
hard would it be to create something which does the opposite? Ill explain - 

Sometime I want to still see the grid, but disable snapping for a while. By "for
a while" I mean that I usually work with snap enabled, for example when I draw
boxes and move things, but here and there would like to do something freehand -
for example, frehand line drawing - in which case I need to disable all snap.
Opening the document properties dialog and unchecking all boxes works, but it's
awkward and requires me to later re-check all those boxes later.

Is it possible to create a universal "snap on/off" command which will be in the
menu so there won't be a need to keep the document preferences dialog open all
the time? When it's on, it will respect all the settings in the dialog. When
off, no snap will be active. Ideally this should be in the view menu below grid
and guides.

Bug #170970 in the bug tracker suggests something similar. I'm okay with both
icon and menu item, either should work. I think it would be really helpful.

Thank you for your work on Inkscape so far - 
Michael

-------------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 12 comments |
headers
jiho | 1 Dec 2007 12:40
Picon
Gravatar

Re: Inkscape native on OSX - try 2

On 2007-November-30  , at 20:40 , J.B.C.Engelen@... wrote:
> Mental:
>> Ah, this is a bug in Inkscape::LayerManager::_rebuild().
>> Everything after the call to _clear() should be skipped if
>> _document is NULL.
>>
>> Feel free commit a fix along those lines, I may not get to it soon.
>
> Done.

Thanks a lot. Unfortunately this got rid of the first messages[1] but  
Inkscape still crashes with the message:
$ ./inkscape

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we  
can fix it.

(inkscape:385): GLib-WARNING **: g_main_loop_run(): called  
recursively from within a source's check() or prepare() member,  
iteration not possible.

Gdb log with a break points where I thought they could be useful:

(gdb) b _handleWindowNeedsDisplay
Function "_handleWindowNeedsDisplay" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (_handleWindowNeedsDisplay) pending.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Diederik van Lierop | 1 Dec 2007 13:58
Picon

Re: NEW: Grid visibility and snap enabling

Michael Grosberg wrote:
> Is it possible to create a universal "snap on/off" command which will be in the
> menu so there won't be a need to keep the document preferences dialog open all
> the time? When it's on, it will respect all the settings in the dialog. When
> off, no snap will be active. Ideally this should be in the view menu below grid
> and guides.
>   

Of course that would be easy to implement, and I've been considering 
something like that before. What kept me back is that it will also make 
snapping more confusing. For example, for snapping to an object we would 
need to enable the universal snap option, _and_ "snap nodes" or "snap 
bounding box corners", _and _ "snap to object nodes" or "snap to object 
paths". It will happen way to often that you'll forget to enable one of 
these three options, if you're aware of them at all. Even for 
experienced users this is confusing, I've been there ;-).

In virtually all workflows, you would either use "snap nodes" or "snap 
bounding box corners", not both at the same time. So to disable all 
snapping, you currently only have to uncheck one of these options in the 
document properties to disable all snapping. Maybe we should have a 
key/menu item/icon bound to both these options to make them easier 
accessible, instead of adding an universal snap option? This way you 
don't have to keep the document preferences dialog open all
the time, and we will only have two options in series for snapping to 
objects. For snapping to e.g. guides, we will still have only one option 
to be enabled.

So, should we add a key binding, menu item and icon for this?
(Continue reading)

Permalink | Reply | 11 comments |
headers
J.B.C.Engelen | 1 Dec 2007 14:48
Picon
Picon

Re: NEW: Grid visibility and snap enabling

> -----Original Message-----
> From: inkscape-devel-bounces@... 
> [mailto:inkscape-devel-bounces@...] On 
> Behalf Of Diederik van Lierop
> Sent: zaterdag 1 december 2007 13:58
> To: inkscape-devel@...
> Subject: Re: [Inkscape-devel] NEW: Grid visibility and snap enabling
> 
> Michael Grosberg wrote:
> > Is it possible to create a universal "snap on/off" command 
> which will 
> > be in the menu so there won't be a need to keep the document 
> > preferences dialog open all the time? When it's on, it will respect 
> > all the settings in the dialog. When off, no snap will be active. 
> > Ideally this should be in the view menu below grid and guides.
> >   
> 
> Of course that would be easy to implement, and I've been 
> considering something like that before. What kept me back is 
> that it will also make snapping more confusing. For example, 
> for snapping to an object we would need to enable the 
> universal snap option, _and_ "snap nodes" or "snap bounding 
> box corners", _and _ "snap to object nodes" or "snap to 
> object paths". It will happen way to often that you'll forget 
> to enable one of these three options, if you're aware of them 
> at all. Even for experienced users this is confusing, I've 
> been there ;-).
> 
> In virtually all workflows, you would either use "snap nodes" 
> or "snap bounding box corners", not both at the same time. So
(Continue reading)

Permalink | Reply | 3 comments |
headers
Diederik van Lierop | 1 Dec 2007 16:42
Picon

Re: NEW: Grid visibility and snap enabling

J.B.C.Engelen@... wrote:
> This way, Shift+# will still work as it does now to new users. Only
> advanced users will ever want to use alt or ctrl I think. 
> The current menu item should become a submenu, containing the three
> toggles. This is a downside as it requires more menu browsing than now.
>
> Johan

Indeed, that's the other option. We can enable/disable snapping either 
using the nodes/bbox option, or using the grids/guides/objects option. 
The latter is more common, especially wanting to see the grid but not 
snapping to it. But shouldn't we then provide the same toggles for 
guides and objects, for consistency's sake?

Diederik

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
Permalink | Reply | 2 comments |
headers
Diederik en Rezi | 1 Dec 2007 17:22
Picon

Re: NEW: Grid visibility and snap enabling

> Indeed, that's the other option. We can enable/disable snapping either
> using the nodes/bbox option, or using the grids/guides/objects option.
> The latter is more common, especially wanting to see the grid but not
> snapping to it. But shouldn't we then provide the same toggles for
> guides and objects, for consistency's sake?
>

Adding to my previous mail:

When using the grids/guides/objects option to toggle snapping, we will
need an additional checkbox for each of those in the document properties
dialog. (when requiring that all snapping options should be accessible in
that dialog). This is not needed when using the nodes/bbox option, as we
have checkboxes for these already.

summarizing our options:
1) nodes/bbox option:
     - no additional checkboxes needed

2) grids/guides/objects option:
     - closest to "grid visible but not snapping", which is the most
requested feature,

> Diederik
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell.  From the desktop to the data center, Linux is going
> mainstream.  Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
(Continue reading)

Permalink | Reply | 0 comments |
headers
J.B.C.Engelen | 1 Dec 2007 17:50
Picon
Picon

Re: NEW: Grid visibility and snap enabling


> -----Original Message-----
> From: inkscape-devel-bounces@... 
> [mailto:inkscape-devel-bounces@...] On 
> Behalf Of Diederik van Lierop
> Sent: zaterdag 1 december 2007 16:42
> To: inkscape-devel@...
> Subject: Re: [Inkscape-devel] NEW: Grid visibility and snap enabling
> 
> J.B.C.Engelen@... wrote:
> > This way, Shift+# will still work as it does now to new users. Only 
> > advanced users will ever want to use alt or ctrl I think.
> > The current menu item should become a submenu, containing the three 
> > toggles. This is a downside as it requires more menu 
> browsing than now.
> >
> 
> Indeed, that's the other option. We can enable/disable 
> snapping either using the nodes/bbox option, or using the 
> grids/guides/objects option. 
> The latter is more common, especially wanting to see the grid 
> but not snapping to it. But shouldn't we then provide the 
> same toggles for guides and objects, for consistency's sake?

Snapping to guides and objects is different from grid, because it is not
as "predictable" as grids. I think snapping to invisible guides or
objects would be strange. A general "no snap" toggle would be very nice,
though most tools already have this I think.

> When using the grids/guides/objects option to toggle
(Continue reading)

Permalink | Reply | 1 comment |
headers
Maximilian Albert | 2 Dec 2007 00:00
Picon
Picon

State of progress of Mac integration?

Hi all,

I just finished talking with a friend who discovered Inkscape today 
(without any effort on my part :)) while working on a webpage for his 
funk & soul band. He was really enthused by Inkscape's power and 
usability, so first I'd like to give the kudos to all developers.

However, using a Mac, he felt that the overall integration and "Mac 
feeling" could still be improved. Following my suggestion he gave one of 
the development snapshots a try (he was using the 0.45 release) and was 
pleasantly surprised to discover improvements (e.g., Apple key + click 
now correctly emulates right click). I think some of this is due to 
jiho's work? Thanks! (Also to all the others working in this area.)

But some other things still don't work properly. He mentioned, for 
instance, that Inkscape windows cannot be opened/maximised by clicking 
on the task bar (or whatever it's called on the Mac), which I found 
strange but using Linux I can neither confirm nor refute. So I was 
trying to find info about the changes since 0.45 in the Release Notes 
for 0.46, unfortunately without success. Just out of curiosity (since 
I'm not affected by this), is any info about the changes or about what's 
still missing available somewhere?

Thanks again for everybody's efforts to make Inkscape yet more powerful 
and user friendly,

Max

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
(Continue reading)

Permalink | Reply | 3 comments |
headers
jiho | 2 Dec 2007 01:02
Picon
Gravatar

Re: State of progress of Mac integration?

On 2007-December-02  , at 00:00 , Maximilian Albert wrote:
> I just finished talking with a friend who discovered Inkscape today
> (without any effort on my part :)) while working on a webpage for his
> funk & soul band. He was really enthused by Inkscape's power and
> usability, so first I'd like to give the kudos to all developers.
>
> However, using a Mac, he felt that the overall integration and "Mac
> feeling" could still be improved. Following my suggestion he gave  
> one of
> the development snapshots a try (he was using the 0.45 release) and  
> was
> pleasantly surprised to discover improvements (e.g., Apple key + click
> now correctly emulates right click). I think some of this is due to
> jiho's work? Thanks! (Also to all the others working in this area.)

The Apple+Right click thing is not me ;) However, I think that this  
has always worked, it just requires the right option to be enabled in  
Apple's X11. The main Mac-related improvements were some cleanup in  
the startup script and some visual improvements in the GTK theme (the  
latest Intel builds have had it for a while). I hope to get python  
scripting working out of the box soon too. But that's about it.
And well there's always the long term goal of X11 independance...  
which is not so far away now.

> But some other things still don't work properly. He mentioned, for
> instance, that Inkscape windows cannot be opened/maximised by clicking
> on the task bar (or whatever it's called on the Mac), which I found
> strange but using Linux I can neither confirm nor refute.

That's true indeed. When windows are minimized they go to the "Dock",
(Continue reading)

Permalink | Reply | 2 comments |

Gmane