- Inkscape Devel - Inkscape Mailman

wmf-inout bug
by Johan Engelen 06 Nov '13

06 Nov '13

Hi all, Clang found a potential bug. In /src/extension/internal/wmf-inout.cpp, line 1408: int32_t width, height, colortype, numCt, invert; if( (iUsage != U_DIB_RGB_COLORS) || !(dibparams = wget_DIB_params( // this returns pointers and values, but allocates no memory dib, &px, &ct, &numCt, &width, &height, &colortype, &invert )) ){ Now if the first condition is true ("(iUsage != U_DIB_RGB_COLORS)") the second part will not be executed, and thus all those ref'd variables will go un-initialized. I'd appreciate it if someone with more knowledge about wmf-inout.cpp would have a look and fix the code (it's pretty ugly to put the initialization call in the if-condition...) Thanks! Johan

2 3

Image Gallery thumbnails
by Jared Meidal 06 Nov '13

06 Nov '13

Martin, The beautiful thumbnails have disappeared! 😊 http://staging.inkscape.org/en/community/gallery/ Any possibility of restoring them? --Jared

2 1

Re: [Inkscape-devel] Bug Counts on Website
by Jared Meidal 05 Nov '13

05 Nov '13

Martin, The staging site states there are 4 Blockers/4865 Fixed, but the linked Launchpad pad page only lists 3/4866! Is sync off or delayed? --Jared > On Sat, 2013-10-19 at 02:14 +0200, Krzysztof Kosi?ski wrote: > > Is there some way to change the background color? The background for > > blocker bugs is so light that it's hard to read the number, while the > > background for fix released bugs should be green, I think :) > > So there are two colour controls. Firstly the CSS, I can make the yellow > darker so it's readable. > > Secondly the counts, changing the low count to forty million bugs should > make it green. Whatever the number of bugs, it's bound to be lower than > forty million. > > Martin,

3 3

New version and release notes
by Jared Meidal 05 Nov '13

05 Nov '13

I think this place would be a great area to highlight and determine what are our major "talking points" in the next release: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.49 Also, was harmony achieved in setting the next release number at 0.91.0? I would be happy to help craft some of the release notes here, but I need wiki access. Thanks! --Jared > On Fri, 2013-10-18 at 23:59 +0000, Jared Meidal wrote: > > There have been a lot of excellent developments to be release in the > > next release, including C++, cairo, alignment/distribution along with > > new possible builds on win64-bit (Partha's help), and native Mac OS X > > (some almost-ready builds are out there). If these all reach maturity > > for the release the new builds are providing an increase audience and > > userbase. A changing version numbering scheme could reflect the > > developers' acknowledgement of this and demonstrate the activity of > > the software project. > > You make a persuasive argument. I like the idea of moving from 0.49 to > 5.0 with the idea that a 0.49 release is likely to uncover lots of bugs > from our massive list of changes. > > But whatever we do, I also like having a defined list of what would > certify us for such a big release PR type event. > > Martin,

2 1

About Page
by Martin Owens 04 Nov '13

04 Nov '13

Hey Devs, Specifically about the about page unearthed by KK over on dev. The about page on staging.inkscape.org isn't as good as the one over on http://en.dev.inkscape.org/about/ We could fetch the content (and I will) but we should check to see if there's any other content that needs updating. It won't be long now before the staging website will be live and what we have in the cms will represent inkscape to any visitors. If you can spare 10 minutes, go over to staging.inkscape.org and have a look around. If there's something you feel isn't fantastic, then consider helping make it better. Almost everyone can edit the cms on the website once they have created an account and I've added them as admins. Best Regards, Martin Owens

1 0

Dev website deterioration
by Krzysztof Kosiński 04 Nov '13

04 Nov '13

Hello all It appears that along with the considerable improvements in the "About" pages, some destructive changes to the dev website were made. 1. The coding style documentation and the "getting started" document is no longer available from the menu. In fact, none of the items in the "Developers" menu work. 2. Login does not work at all, and seems to send the password as a GET variable (e.g. it appears in cleartext on the address bar). 3. Menus contain duplicate items. For instance, "Developers" contains both "Bazaar" and "Source code", "Learn" contains both "User documentation" and "Manuals", and the "Donate" item is present both as a top level item and as a subitem in "Community". 4. News later than April 2011 have disappeared. Regards, Krzysztof

2 1

GSoC Mentor's meeting report
by Tavmjong Bah 04 Nov '13

04 Nov '13

Hi, Here is a report from the GSoC mentor's summit: To be honest, I didn't learn that much from this years conference. Probably for two reasons: The first is that I (as well as many others) were tempted by the sessions given by Google employees. While these sessions were interesting, they weren't really applicable to GSoC. BTW, if anyone can think of how it could be useful for Inkscape, I've got a $2000 coupon for using Google's cloud platform. The other reason is that there is probably less to learn after attending the summit last year. I kind of guessed this and if the Graphical Web (e.g. SVG Open) conference hadn't been just after in San Francisco I probably wouldn't have made the effort to attend. I did pick up a few things. The most interesting session I attended was titled "Developer Meetings Coding Sprints" but was really about ways to collaborate and communicate. Highlights[1]: 1. Have bug days using IRC. It helps to motivate people if a group is doing this together. It is also rewarding to be able to report "40 bugs squashed today". 2. Hangout using Google's Hangouts. Some people found it quite useful to announce that they would be on-line for a given period of time and let others freely join the conversation. I plan on giving this a try in the next couple of days. (For more organized sessions, the hangout can be live-streamed via YouTube so one doesn't need a Google account to watch.) 3. For serious planning and strategizing, face-to-face meetings are most useful. Separately, Bradley Kuhn, from the Software Freedom Conservancy was there; he is really encouraging us to use some of our pot of money to hold a meeting for this. As a final note, the GSoC timetable has been moved forward by quite a bit. Next year's organization applications are due on February 14th (rather than March 29th) and student applications are due March 21st (rather than May 3rd).[2] Tav [1]https://gsoc-wiki.osuosl.org/index.php/Developer_Meetings_Coding_Sprints [2]https://www.google-melange.com/gsoc/events/google/gsoc2014

2 1

Lattice deformation 2 video
by Jabiertxo Arraiza Cenoz 04 Nov '13

04 Nov '13

Hi to all, here are a video with improvements in lattice deformation live effect. read credits and link to launchpad in youtube. http://www.youtube.com/watch?v=YlK9L88_tWE

2 3

Buildd failures on Launchpad
by Krzysztof Kosiński 03 Nov '13

03 Nov '13

Hello Recently I'm getting mails about Launchpad build failure reports for the inkscape-trunk package. The log seems to suggest that it's not our fault (some dependency problems apparently), but it looks interesting for different reasons: 1. We have Gimp and bash-completion as a build dependency. Why on earth is that? 2. One of the unmet dependencies is libxml-parser-perl. Why do we require this? It looks like we have just four extensions written in Perl - perhaps we could rewrite them in Python and avoid Perl as a hard dependency. Regards, Krzysztof

3 3

clang-format
by Johan Engelen 01 Nov '13

01 Nov '13

Hi all, clang-format seems like a great tool to reformat our whole codebase once and for all, and keep it that way. I've added a configuration file "_clang-format" to trunk, hoping that others can have a look at it too and tweak the settings for our project. Can you have a look at this Krzysztof? (my bigger ambition is to run clang-format on the whole codebase after we branch-off the next release) Thanks, Johan

3 5