Alexandre Prokoudine | 2 Jan 03:21 2009
Picon

intro for developers

Hi,

Recently a person reported to out bug tracker that the website doesn't
provide good introduction information for new developers.

So I've just taken a look at http://inkscape.org/doc/devdocs.php and I
have several questions:

1. Do you find this information overall sufficient?
2. Last changes to http://inkscape.org/wiki/index.php/DeveloperManual
date back to February 2007. Would anyone mind having a look and saying
whether something needs changes? (btw, our wiki outputs errors again)
3. Does the flowchart at http://inkscape.org/doc/devdocs.php really
reflect current state of source code?
4. Same question about  class hierarchy image.

Thanks! :)

Alexandre

------------------------------------------------------------------------------
J.B.C.Engelen | 2 Jan 06:23 2009
Picon
Picon

Re: intro for developers

> -----Original Message-----
> From: Alexandre Prokoudine
[mailto:alexandre.prokoudine@...] 
> Sent: vrijdag 2 januari 2009 3:21
> To: Inkscape Devel List
> Subject: [Inkscape-devel] intro for developers
> 
> Hi,
> 
> Recently a person reported to out bug tracker that the 
> website doesn't provide good introduction information for new 
> developers.
> 
> So I've just taken a look at 
> http://inkscape.org/doc/devdocs.php and I have several questions:
> 
> 1. Do you find this information overall sufficient?
> 2. Last changes to http://inkscape.org/wiki/index.php/DeveloperManual
> date back to February 2007. Would anyone mind having a look 
> and saying whether something needs changes? (btw, our wiki 
> outputs errors again) 3. Does the flowchart at 
> http://inkscape.org/doc/devdocs.php really reflect current 
> state of source code?
> 4. Same question about  class hierarchy image.

It's nice that you care about the report Alex.  But I am somewhat
pessimistic about improvements to the documentation.

I think the single most important documentation for a floss project is
how to get it built from scratch. And it must be easy to build, so the
(Continue reading)

J.B.C.Engelen | 2 Jan 06:35 2009
Picon
Picon

Re: CMake status

> -----Original Message-----
> From: Henning Meyer [mailto:Henning.Meyer@...] 
> Sent: woensdag 31 december 2008 11:28
> To: inkscape-devel@...
> Subject: Re: [Inkscape-devel] CMake status
> 
> I'm new to the list. But I'd like to see a cmake-build 
> solution. It's more flexible and easier to maintain on 
> multiple platforms. Also it would be easier for me to 
> integrate additional libraries for testing-purposes ;-)
> > The problem we had with cmake was that it puts obj files in 
> some special dir that is long, and then creates a commandline like:
> > g++  verylongpathlisting/blah.o 
> possiblyevenlongerpathname/blah2.o ...
> > such that the cmdline is too long to work with windows/g++
> >   
> I don't know your MinGW environment, but this problem is 
> known and seems to be solved here:
> http://www.cygwin.com/faq/faq.programming.html#faq.programming
> .make-execvp

Thanks for your pointer, however we don't use cygwin and I'm very
strongly against making use of it. There must be a better solution with
cmake.

-johan

------------------------------------------------------------------------------
Diederik van Lierop | 2 Jan 10:27 2009
Picon

Re: intro for developers

On 01/02/2009 06:23 AM, J.B.C.Engelen@... wrote:
> All the class diagrams, code organization, etc, I think it is hardly
> ever used or read. 

Well, I think most of us have read that at least once. At least I did. 
It can at least serve as a primer, and if it's kept up-to-date then it 
can even be a reference

> It is just too much to try and read about how a big
> program like Inkscape works, without having looked at the code for a
> long time. 
The code base itself is obviously the ultimate reference, but it's 
essential for new devs to have a wiki that explains the what a SPView / 
SPNamedView / SPDesktop / SPDocument etc. are.  That will give you the 
big picture much faster.

> And, once you know how a certain piece works, the
> documentation on the website has become almost useless, so motivation is
> lacking to document it. 
Refactoring isn't always fun either, is it? Motivation can surely be 
found for such a thing, otherwise we would have never gotten our 
excellent Inkscape book and guide.

To answer Alexander's questions:
1) yes, I think it's sufficient. We need a primer, not a complete 
reference (although that would be great to have too)
2-4) we need some feedback from our most experience devs here, most part 
of it I cannot judge

Diederik
(Continue reading)

J.B.C.Engelen | 2 Jan 16:49 2009
Picon
Picon

testsuite painting-marker-02-f.svg

Hi all,
  I am working on some testsuite fails, and am now stuck on
painting-marker-02-f.svg. Apparently, the stroke thickness of the
markers should be inherited from the path they are on. This does not
work in Inkscape.
How should this inheritence be done? (is there an example of how this is
usually done in inkscape?)

Thanks,
  Johan

------------------------------------------------------------------------------
J.B.C.Engelen | 2 Jan 17:15 2009
Picon
Picon

Re: testsuite painting-marker-02-f.svg

> -----Original Message-----
> From: J.B.C.Engelen@... 
> [mailto:J.B.C.Engelen@...] 
> Sent: vrijdag 2 januari 2009 16:50
> To: inkscape-devel@...
> Subject: [Inkscape-devel] testsuite painting-marker-02-f.svg
> 
> Hi all,
>   I am working on some testsuite fails, and am now stuck on 
> painting-marker-02-f.svg. Apparently, the stroke thickness of 
> the markers should be inherited from the path they are on. 
> This does not work in Inkscape.
> How should this inheritence be done? (is there an example of 
> how this is usually done in inkscape?)

Hmm, according to SVG spec: "Properties  inherit into the 'marker'
element from its ancestors; properties do not inherit from the element
referencing the 'marker' element."
So something else is the problem...

------------------------------------------------------------------------------
Jasper van de Gronde | 2 Jan 17:15 2009
Picon

Re: testsuite painting-marker-02-f.svg

J.B.C.Engelen@... wrote:
> Hi all,
>   I am working on some testsuite fails, and am now stuck on
> painting-marker-02-f.svg. Apparently, the stroke thickness of the
> markers should be inherited from the path they are on. This does not
> work in Inkscape.

Sounds good! However, I don't know what you're using for reference, the 
standard or the test suite reference images, but if you're using the 
latter you may want to double-check the standard. I'm currently in the 
process of generating new references for the filter-related tests, as I 
found that some of the W3C references are likely incorrect (there is 
still a chance that there are some color space issues with the Inkscape 
output, but so far it seems that there are at least some problems with 
the W3C images).

------------------------------------------------------------------------------
Thomas Holder | 2 Jan 17:24 2009
Picon
Picon

Re: testsuite painting-marker-02-f.svg

> Hmm, according to SVG spec: "Properties  inherit into the 'marker' 
> element from its ancestors; properties do not inherit from the
> element referencing the 'marker' element." So something else is the
> problem...

yes, markers should be clipped by their viewBox, but inkscape does not
do that.

------------------------------------------------------------------------------
Maximilian Albert | 2 Jan 20:22 2009

Re: intro for developers

2009/1/2 Diederik van Lierop <mail@...>:
> On 01/02/2009 06:23 AM, J.B.C.Engelen@... wrote:
>> All the class diagrams, code organization, etc, I think it is hardly
>> ever used or read.
>
> Well, I think most of us have read that at least once. At least I did.
> It can at least serve as a primer, and if it's kept up-to-date then it
> can even be a reference

I agree, although I spent a full summer working on Inkscape before I
discovered this info in the wiki. Just like Johan I usually
investigate code by looking at it, and often enough I find myself
grepping through the whole code to understand how pieces of code are
interconnected (no need for Notepad++, though :-P ). Still, every now
and then I don't understand what the SPFooBar class  is supposed to
mean or how it relates to the things I see on my canvas and then I'm
grateful if there is some piece of documentation on it. So I believe
we definitely should have this material as as reference, but I feel it
could be improved to help newbie developers better understand the
class hierarchy. Unfortunately, I don't feel qualified/capable of
doing this atm. :-(

Max

------------------------------------------------------------------------------
Alexandre Prokoudine | 2 Jan 20:35 2009
Picon

Re: Manually change language in preference dialogue

2008/12/30 the Adib wrote:
> Hi all,
>
> I yust want to inform you that I commited some code to change the
> language of the user-interface within the preferences dialogue.

While this is a long requested feature, having a dedicated tab in
Preferences dialog is just overkill, IMO. Could you please move it to
Interface tab?

Alexandre

------------------------------------------------------------------------------

Gmane