May 2008 - Inkscape Devel - Inkscape Mailman

Build problems - Last two commits (18500 & 18501)
by rygle 02 May '08

02 May '08

Hi guys, Having problems building the last two trunk revisions on Win32; SVN 18500 gives me this; ===== Make error line 201: problem compiling: mingw32-g++: src/dom/svgparser.cpp: No s uch file or directory mingw32-g++: no input files ===== So I updated to SVN 18501, and someone changed main.cpp, which now gives me this error; ===== Make error line 201: problem compiling: src/main.cpp: In function 'void sp_do_ex port_png(SPDocument*)': src/main.cpp:1027: warning: 'sp_item_invoke_bbox' is deprecated (declared at src /sp-item.h:215) src/main.cpp: In function 'bool replaceArgs(int&, char**&)': src/main.cpp:1419: warning: missing initializer for member '_WIN32_FIND_DATAW::f tCreationTime' src/main.cpp:1419: warning: missing initializer for member '_WIN32_FIND_DATAW::f tLastAccessTime' src/main.cpp:1419: warning: missing initializer for member '_WIN32_FIND_DATAW::f tLastWriteTime' src/main.cpp:1419: warning: missing initializer for member '_WIN32_FIND_DATAW::n FileSizeHigh' src/main.cpp:1419: warning: missing initializer for member '_WIN32_FIND_DATAW::n FileSizeLow' src/main.cpp:1419: warning: missing initializer for member '_WIN32_FIND_DATAW::d wReserved0' src/main.cpp:1419: warning: missing initializer for member '_WIN32_FIND_DATAW::d wReserved1' src/main.cpp:1419: warning: missing initializer for member '_WIN32_FIND_DATAW::c FileName' src/main.cpp:1419: warning: missing initializer for member '_WIN32_FIND_DATAW::c AlternateFileName' src/main.cpp:1523: error: invalid conversion from 'const gchar*' to 'gchar*' src/main.cpp:1523: error: initializing argument 1 of 'void std::vector<_Tp, _A lloc>::push_back(const _Tp&) [with _Tp = gchar*, _Alloc = std::allocator<gchar*> ]' ===== I don't think the first error has yet been dealt with, but the second error simply occurs before the first error gets a chance. Cheers, Rygle. -- View this message in context: http://www.nabble.com/Build-problems---Last-two-commits-%2818500---18501%29… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

5 7

LGM
by Alexandre Prokoudine 02 May '08

02 May '08

Hi, So, who is coming to LGM? :) Alexandre

4 3

New Extensions and Translation or other requirements
by rygle 01 May '08

01 May '08

Hi, Inductiveload has been busy fixing and making extensions. The version of Add Nodes in trunk can now divide into a given number of segments (see LP#171856), and there is also now a Render -> Polar Grid option in trunk (see LP#224522). Soon there will also be a Render -> Cartesian Grid extension, but that's got a slight problem being sorted (see LP#224955). I've recently added the new files to /share/extensions/Makefile.am - I realise that affects the Linux (Mac?) build process, even if it doesn't affect Win32. Does /share/extensions/Makefile.am also flag files for translation (seems to hint at that)? If not, is there a need to change something else for translations? Is there anything else that needs to be updated for new extensions? Cheers, Rygle. -- View this message in context: http://www.nabble.com/New-Extensions-and-Translation-or-other-requirements-… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

3 2

Re: [Inkscape-devel] [Bug 171856] Re: Segment Division
by Aaron Spike 01 May '08

01 May '08

Rygle wrote: > Hi guys, just trying to get my head around all this. No problem. > I committed this and milestoned for release in 0.47, but I assumed that > Aaron and/or a release warden would check it out before the proper > release. I was trying to flag somehow that this is new and needs to be > approved. That's why I set it as Wish List and Fix Committed, not Fix > Released. Should I have instead marked it as Fix Released and nominated > it for release 0.47? Or just leave any milestoning/nomination because > it's automatically in? Seems like it won't get noticed by release > wardens then. There are no release wardens for 0.47 yet. Release wardens impose marshal law during release times to make sure things get out the door in a reasonable amount of time and without any avoidable nasty bugs. During the normal development cycle we average contributors are in charge. If you've been granted commit access the Inkscape community trusts you to decide what goes into the tree. > I'm also unsure, but based on Maximillian's comments, but do some people > feel that applying patches treads on toes if the bug is assigned to > someone else? I merely wanted to get it into trunk so that people would > find any problems with it. I've seen some good patches that didn't make > it into 0.46 because they didn't get attention. Should I not commit > patches when the bug is assigned to someone else? Please be frank, > because I don't want to offend others. I think sometimes applying a patch assigned to another person could possibly maybe tread on another person's toes perhaps. This time it didn't. I grabbed this patch because the author had written me individually about the change and because there doesn't seem like a lot of people who want to deal with python patches. But I knew that I wasn't going to get around to committing it until the weekend and it is very important to have quick turn around on patches. This shows that we value the work being done and encourages repeat contribution. Just think how discouraging it is when I sit on a two line python patch that is obviously fine. You're timing was excellent. Feel free to commit a patch. As long as you do due diligence. Meaning: You understand the issue it addresses. You test it locally to see that it does address that issue. You do not notice any major regressions as a result of it. Otherwise ask for a little clarification and help. And if you feel comfortable, go ahead and assign bugs to yourself. :-) And, yeah, it probably doesn't hurt to ask if the bug is assigned to someone else. I know in my situation sometimes I don't comment everything I know on the bug because I don't think of it. There might be some issue I want to check into. So if you ask I'd be more likely to write that in the bug comments. Not trying to hide info; I just don't think of these things all the time. Thanks for applying this patch! Aaron P.S. I'm copying Inkscape-devel to give people a chance to disagree with me. :-)

1 0

New tool added
by Jon A. Cruz 01 May '08

01 May '08

I've just committed the first cut of the new eraser tool. This first part only adds in the functionality to cut away parts of objects you have selected. It won't do anything if you don't have something selected, and it won't do anything if the first mode is selected (the sub-toolbar has toggles for the two modes). However it does commit all the infrastructure changes including the new icons, new drawing context, verbs, switching, etc. I had been wanting to get that in first to shake down bugs in that support work. Hopefully I'll be able to get the other mode committed this weekend. That's the main differentiator and works like touch-delete or perhaps pop-the-balloons. Please let me know if there is anything in that commit that needs fixing, etc. etc. Thanks.

10 23