December 2013 - Inkscape Devel

Re: [Inkscape-devel] Connector Tools
by Susan Spencer 05 Dec '13

05 Dec '13

Hi Michael, Hope you're feeling better! Thanks for the the advice about updating libavoid. We'll be looking for more of this type of information during the next few weeks, so if you happen to think of anything, or see something in this thread that requires correction or addition, please let us know. Thanks, and get well soon, -Susan

1 0

Website Translations
by Martin Owens 05 Dec '13

05 Dec '13

Hey Guys, Please pass this onto the translations mailing list: The website's internal translations are open: https://translations.launchpad.net/inkscape-web These are all the strings which one can not edit from the CMS interface, but should be translated for your local language. They'll be merged in one a week or so and uploaded to the live website. These didn't work until today and I'm still trying to identify strings which haven't been marked for translation. So if you see any, let me know via a bug report. Best Regards, Martin Owens

1 0

Staging & Website Update
by Martin Owens 05 Dec '13

05 Dec '13

Hey Devs, We're testing live over at http://py1.osuosl.org/ please register a new account for yourself and I will enabled your editing capabilities. Please do not edit http://staging.inkscape.org any more unless you want to test edits. These edits will be periodically overwritten with data from the new live instance. We're waiting on the masters of the DNS to change over www.inkscape.org when ready. In the meantime, please give the new live a test and please let me know if you find issues. Best Regards, Martin Owens

7 20

Re: [Inkscape-devel] Inkscape and SMIL support
by Susan Spencer 04 Dec '13

04 Dec '13

As mentioned previously in this thread, details of fundraising are typically discussed *after* a proper estimate is developed. If this is a serious discussion (which I believe it is) then the following actions are up next: 1. Identify the programmers, testers, documenters and users who will participate. (Participants can assume multiple roles) 2. The programmers collaborate to create & share the requirements and constraints 3. The testers specify & share the testing and signoff requirements, based on output of #2 4. All participants specify documentation requirements to meet needs of both the users and the future developers/maintainers 5. Estimate the cost & delivery schedule 6. Design the fundraising campaign (which is another separate effort) if you're going to raise funds from the public then you can't be code cowboys about this, no matter if you believe this is a relatively small effort. Performing the above steps and publishing the results helps build momentum for public monetary support and creates tremendous public confidence. it also gives the tech media something to report regularly building up to the fundraising start date. Use the machine wisely, publicity never hurts! Assuming that remote collaboration results require more time than face-to-face sprints, we can shoot for 30 to 60 days for #1-5, 30 days maximum for #6, so max 90 days till fundraising. My skills aren't in programming, but if you would like me to I can help with project development & fundraising. If there are others more connected to Inkscape than I who would like to step up for this work, please do! - Susan >

8 25

Website status
by Bryce Harrington 04 Dec '13

04 Dec '13

On Tue, Nov 19, 2013 at 09:48:14PM -0500, Martin Owens wrote: > On Tue, 2013-11-19 at 15:58 -0800, Bryce Harrington wrote: > > Thanks, what is the ETA for this switchover? > > Last week of November was my target date. I'm confident it'll be > switched by next week. We have OSL on the ticket today for the new mysql > database and I've got everything from the repo to the nginx config > ready. > > Once live.inkscape.org points to py1, it can be tested. Once it checks > out, inkscape.org and www.inkscape.org can be pointed to the same. > > Martin, Hi Martin, Where do we sit with getting the new site online? I assume we just need a DNS switchover at this point; if so, do you have a contact person for doing this switch? I've had a few people contact me about making donations recently, so given google checkout is going away, it'd be helpful to get the new site up asap. Also, can you draft up a short intro guide to explain how to sign up for an editor account, and how to add content, news items, etc. to the site? Bryce

3 7

Additional Inkscape Funding - paying developers feature by feature
by Anna Morris 04 Dec '13

04 Dec '13

Hi, Firstly, I am a big Inkscape fan, I have used it for various projects in the past year, this is my favorite http://fsfe.org/graphics/xbox-infographic.png (ie. I am not a spammer, lol) So, my email is about funding. I am working with Open Funding http://funding.openinitiative.com/ to assist developers to get crowd funding for Free Software. Open Funding works on a feature by feature basis. For example the core-team at gimp are funding a symmetry painting feature at the moment http://funding.openinitiative.com/funding/1578/ I am not sure how Inkscape is funded at the moment, but I would very much like to assist any developer(s) to get funding for a feature. Also, if you don't need/want to earn money for your work, you could always donate the funds to the project in general. This small scale funding is a great way for users (like myself) to give back, which they are often eager to do, but in a way which is very concrete, forward thinking and achievable. Its much simpler to set up than a large kickstarter campaign and is more deeply routed in the function of the software. Please let me know what you think and if you are interested in getting funding this way, either as a group of core-developers or, if not, as an individual developer. Thanks Anna Morris

4 4

Re: [Inkscape-devel] Inkscape and SMIL support
by Maggio Mago 04 Dec '13

04 Dec '13

> > On Tue, Dec 03, 2013 at 02:59:22PM +0100, Krzysztof Kosi??ski wrote: > > That sounds like a good project. If you are interested in this, ping > me, I've done a little bit of work on vector renderers on opengl. > > Ping! I work at my level about SMIL support. I am interested in any document about it. In my own way I try also to document source code (conceptual / concrete architecture, sequential diagram, relationship diagram, major objects, ...) Best regards --------------------------------------------- Thank you to all the contributors who helped to Inkscape to be it is. I send you our best greetings, and all your family members.

1 0

Inkscape 0.48.5
by Alex Valavanis 03 Dec '13

03 Dec '13

Hi All, Do we have a schedule for the next stable point release? Builds are now failing on Ubuntu Saucy using 0.48.4 because of bug #1095364 <FTBFS with gcc 4.8> [1]. Cheers, AV [1] https://bugs.launchpad.net/inkscape/+bug/1095364

7 27

Removing ID attribute from group (XML editor) causes crash
by Bryan Hoyt | Brush Technology 03 Dec '13

03 Dec '13

While editing an Inkscape-created document, if I delete the ID attribute of a group (or any other element, on further investigation) using the XML editor, and then select that element in the visual editor, Inkscape crashes. The ID in question is not referenced elsewhere in the document. Is it valid SVG to have objects without IDs? It certainly seems like it should be, particularly for hand-crafted SVG. I can reproduce this trivially in Inkscape's trunk build from 22 Sep 2013 on a blank document with nothing but a plain rectangle. - Bryan -- Bryan Hoyt, *Software Developer* -- Brush Technology *Ph:* +64 3 741 1204 *Mobile:* +64 21 238 7955 *Web:* brush.co.nz

4 10

SMIL Breakdown
by Martin Owens 03 Dec '13

03 Dec '13

This is an attempt to breakdown the larger SMIL problem into dependent pieces of work and also define a test which can say if this piece is done. What piece would you like to work on the most? If you can see any gaps or better delineations, we can modify: 1. Preservation - Allow all SMIL elements and attributes to exist in loaded documents and save them back without modifications even if the object's they're tied to are modified. The test is a set of SMIL enabled animations and this might already pass. 2. Propertise - Actually load SMIL elebutes into structures and make them accessible via code. The test would be a code test, call out all the attributes and iterate over times. 3. Internal Time Line - We'd introduce the time dimension to our objects and we'd be able to set a time on them and read back nearest values (no interpolation). The test would be another code test to select objects, set a time and read back attributes. (getAttributeAtTime?) 4. Static Time - We'd allow the user to set a time via the ui or the command line and render that as a static non-animated drawing. The test would be a visual one, load inkscape with an existing smil svg file and pick a bunch of times and export each as a png frame. 5. Interpolation - This can happen along side any other pieces after 3, but it's a well understood problem and testing can be done with either a code test requesting attributes non-key-frame times or a visual test like 4 for non-key-frame times. 6. Renderer - We attempt to create a smooth animation from the attributes. This involves automatically progressing over time and changing the rendered output. The test would be to load a smil svg and see the animation animate on canvas once. (Play button/keycombo?) 7. Timeline UI - This is the most UI design aspect. We add in a way for the user to move through the timeline. We don't have to make the UI look like any existing products. The test would allow a user to drag through a timeline, press pause, start, etc and see the result. 8. Attribute modification - This is where it changes from being a viewer to an editor. Moving and changing attributes while at a specific time can create the required key frames in a linear time progression. Deleting those key times would be useful too. Test would be to create a simple animation from scratch. 9. Export - This is where we save out frames from the render one by one into a desired format. The test is simply the ability to get an mpeg or dir of pngs from an smil svg file. These steps are all really basic and each one should be non-intrusive and capable of being released without effecting the experience for static artists. The next question is; if we were to organise a project around these tasks; how far would we initially go and how much would each step cost? Best Regards, Martin Owens

2 2