January 2008 - Inkscape Devel

Re: [Inkscape-devel] [cairo] 1.6: a8-mask: Making non-aligned strides illegal
by Carl Worth 28 Jan '08

28 Jan '08

On Mon, 28 Jan 2008 00:51:13 -0500, Behdad Esfahbod wrote: > > int > > cairo_image_surface_stride_for_width (cairo_format_t format, > > int width); > > I marginally prefer cairo_format_stride_for_width() as a name. Oh, I might like that. I came up with the first name before I realized that a format was needed here. > > And also documenting cairo_image_surface_create_for_data that the > > stride value passed to it should always come from calling the function > > above. > > Humm, not sure how limiting that would be. Do you mean it should be the > stride_for_width() of the actual image width, "stride_for_width() of the actual image width" is what I intended. > or the stride for some > (any) width? I mean, say I want to create a cairo surface for a > subsurface of a larger buffer. The width passed to cairo may be way > smaller than the width used for stride computation. So you might have noticed that I dropped the suggestion in the documentation for cairo_image_surface_create_for_data that playing games with stride is a good way to generate sub-surfaces. More on that below. > Also while at this, how does this work for: > > - 64-bit machines? Is the requirement still just 32? Guess yes. Yes. The requirement comes from the fact that all of pixman is currently in terms of uint32_t. But, yes, the existence of 64-bit architectures is exactly why we want to be able to "upgrade" the alignment constraints in the future. Hence the newly required function call. > - Machines that do not allow unaligned access. Do we also require > that data be aligned properly? Right. And this is why the sub-surface thing is a problem. I tried to address this in the new documentation for cairo_image_surface_create_for_data by stealing language from malloc. What I'm trying to say there is that the data pointer needs to be properly aligned for the current platform. Take a look at the wording I used and see if you can improve it at all. -Carl

1 0

1.6: a8-mask: Making non-aligned strides illegal
by Carl Worth 28 Jan '08

28 Jan '08

On Thu, 24 Jan 2008 12:43:35 -0800, Carl Worth wrote: > • Fix a8mask failure cworth In talking with Keith, Eric, and Søren I've become convinced that instead of "supporting" rendering to/from an A8 mask with a non-multiple-of-4 stride value, we really do want to just document this as illegal. Forcing this kind of alignment will allow for many more optimization opportunities. The inkscape folks had run into this problem and I had said we'd have a fix in 1.6. Instead, I'd like to volunteer to help fix the inkscape code to allocate buffers with a properly aligned stride. If some kind inkscape developer were willing to help me with this soon, that would be great. In order to make it easier to know what a "legal" stride is, (and to allow us to require more stringent alignment constraints in the future), I'm proposing the following new API: int cairo_image_surface_stride_for_width (cairo_format_t format, int width); And also documenting cairo_image_surface_create_for_data that the stride value passed to it should always come from calling the function above. More details, (and more thorough documentation), in the patches below. I'll push unless there are complaints. -Carl

1 0

Launchpad Tips: "Mentoring"
by Bryce Harrington 28 Jan '08

28 Jan '08

If you are a knowledgeable developer, but short on time to fix bugs, there is a way to mark bugs that you don't have time to fix yourself, but that you'd be willing to give advice to new developers on. This is done via the "Offer mentorship" link in the Actions column of a bug report. When you offer mentorship, the bug gets marked with a Swiss Flag. Newbie coders and developers looking for something to work on but who'd like some handholding, can search for these bugs in particular. If you choose to offer mentorship for a bug, it would be good practice to outline what the bug fix would involve, perhaps even indicating files/functions needing touched, and so on. Also, leave some tips for how best to contact you (IRC, email, comments in the bug) if they have questions. Bryce

2 1

Effects | Color | Custom ... extension
by Alvin Penner 26 Jan '08

26 Jan '08

Have not been able to successfully use the above extension, typically get white as a color, so I modified the file \Inkscape\share\extensions\color_custom.py to work okay for me, and reported it as https://bugs.launchpad.net/inkscape/+bug/186176 Am curious to see if anyone else has tried to use this extension. Alvin Penner

1 0

a problem i dont undresud it but i capture it in pictures
by ΤΟΠΙΚΗ ΛΑ.Ο.Σ ΑΙΓ ΙΟΥ " <a123＠...1865...> 25 Jan '08

25 Jan '08

2 1

Re: [Inkscape-devel] Dockable dialog bugs
by unknown＠example.com 25 Jan '08

25 Jan '08

> -----Original Message----- > From: Gustav Broberg [mailto:broberg@...370...] > Sent: woensdag 16 januari 2008 4:00 > To: Engelen, J.B.C. (Johan) > Subject: Re: [Inkscape-devel] Dockable dialog bugs > > On Tue, Jan 15, 2008 at 05:17:45PM +0100, > J.B.C.Engelen@...1578... wrote: > > OK, I just came up with a solution for our problems and > tested it on > > one of the parameter types. This seems to work very very nicely and > > can be generalized to all "registered widgets". I will try > to do this asap. > > That's great news Johan! After your changes I'm not able to reproduce > #179982 anymore. > > I'm not familiar enough with the registered widgets to > evaluate the class design, but just looking diffs themselves, > I can't see any problems with it. One minor nit though, > couldn't the static cast line in RegisterRandom::setValue be > replaced with just "Scalar::setValue (val);"?. First I had "setValue(val)" there without any cast, but the compiler could not find the Scalar function. I can try what you say as it seems better. > Do you think you'll be able to rewrite the remaining widgets > and completely deprecate the old RegisteredWdg in time for > the release? > > Just tell me if I should prepare a Plan B, e.g. to make just > the Document Properties and LPE dialog singleton as you suggested... I hope I can finish the work today, luckily it will not show up in the bug fixing points scheme, so there's still some time. I often stumble upon bugs that still need reporting/fixing :(, was really glad this one turned out to be fixable pretty fast. Regards, Johan

2 1

[Fwd: [Clipart] [Fwd: EPS/SVG Kung Fu Master wanted]]
by Jon Phillips 25 Jan '08

25 Jan '08

-------- Forwarded Message -------- > From: Jon Phillips <jon@...158...> > To: inkscape-devel <inkscape-devel@...6...>, Open Clip Art > Library list <clipart@...626...> > Subject: [Clipart] [Fwd: EPS/SVG Kung Fu Master wanted] > Date: Fri, 25 Jan 2008 13:42:28 +0800 > > If anyone is interested in a for-pay gig, see below...eps/svg kung fu > master preferred! Please contact david below directly and tell em rejon > sent ya! > > Jon > > -------- Forwarded Message -------- > > From: David ten Have|Ponoko <david.tenhave@...1864...> > > To: jon@...158... > > Subject: EPS/SVG Kung Fu Master wanted > > Date: Thu, 17 Jan 2008 17:52:50 +1300 > > > > Jon > > > > > > Michael Galpert forwarded me your email. > > > > > > I am very keen to hook up with an EPS/SVG expert (that might be two > > different people) who is interested helping us out here at Ponoko. > > Initially it will be to answer some questions - but over time we will > > have an increasing need for development work and I would be keen to > > find some one who wants to be part of that. > > > > > > On the CC front I would like to get more info on how we can increase > > the use of the CC licenses in our work. At this point we allow > > designers to share their design files under the CC licensing scheme - > > but I am keen to do a lot more work in this area. > > > > > > Cheers > > > > > > Dave > > > > David ten Have > > Chief Executive Officer > > +64 21 456 919 > > > > > > > > > > Ponoko – Make it Real > > .......................................................................................................................................................................... > > > > > > Level 1 || 27 Dixon Street || Wellington || New > > Zealand || Phone +64 4 473 0031 || www.ponoko.com > > > > > > > > > > > > > > > > > > > > -- Jon Phillips San Francisco, CA USA PH 510.499.0894 jon@...235... http://www.rejon.org MSN, AIM, Yahoo Chat: kidproto Jabber Chat: rejon@...896... IRC: rejon@...897... Please note: the contents of this email are not intended to be legal advice nor should they be relied upon as or represented to be legal advice. Jon Phillips does not represent any organization through this email address.

1 0

PDF Output & Cairo
by Josh Andler 25 Jan '08

25 Jan '08

There was a discussion in the irc channel today regarding exporting PDFs and Carl Worth happened to be there to triage things... well, it got taken to their lists and here's some important info for us. From the cairo list: http://lists.cairographics.org/archives/cairo/2008-January/012800.html Carl then said: Specifically: 1. Check cairo_status at least once. 2. Never set a non-invertible matrix. Just passing it on... Oh, and since I have to ask every once in a while. Carl also said they were trying to target the 4 bugs that prevent us from switching renderers for 1.6 which will hopefully be out within a month. (no promises on that though) So, that may be a nice switch to make for 0.47 if we can. -Josh

2 1

Fwd: Launchpad 1.2.1: PPA deletion, branch feeds, new code project over
by Bryce Harrington 24 Jan '08

24 Jan '08

----- Forwarded message from Matthew Revell <matthew.revell@...1798...> ----- Date: Thu, 24 Jan 2008 18:13:42 +0000 From: Matthew Revell <matthew.revell@...1798...> To: warthogs <warthogs@...1799...> Subject: Launchpad 1.2.1: PPA deletion, branch feeds, new code project over Welcome to Launchpad 1.2.1, our first release of 2008! Highlights include: * Delete PPA packages in the web UI: no more sysadmin requests to delete a package from your PPA. To delete packages from your PPA visit: https://launchpad.net/+people/+me/+archive/+delete-packages * Branch feeds: get the latest commits associated with a person, team, project or individual branch in your feed reader. Take a look at the Bitlbee project's branch feed: http://feeds.launchpad.net/bitlbee/branches.atom * Code hosting project overviews: quick-glance overview of branches and revisions made to projects with code hosted on Launchpad. See Bazaar's overview page: https://code.launchpad.net/bzr In other news: Ubuntu Hardy Heron is now available to start translating in Launchpad. Find out more at: http://news.launchpad.net/translations/translate-ubuntu-hardy-heron Competition: we're on the look-out for a new Launchpad logo. Send us your design for the chance to win an Ubuntu messenger bag. See our blog post: http://news.launchpad.net/general/help-design-the-new-launchpad-logo Read on for more of what's in Launchpad 1.2.1! General Launchpad ================= * Projects, teams and people now have Atom feeds of the most recent commits to the branches associated with them. Individual branches have a feed of their recent commits. Find out more at https://help.launchpad.net/Feeds#branches * Atom feeds produced by Launchpad are now correctly set to the application/atom+xml content type. This allows Wordpress to read Launchpad feeds. (Bug 181620) Distribution Management and PPAs (Soyuz) ======================================== * You can now use the Launchpad web interface to delete packages from your own PPA and any team PPAs for which you are are an admin. See https://launchpad.net/+people/+me/+archive/+delete-packages (Bugs 172587 and 177087) * When a newly uploaded source package is accepted from the queue its component is now overridden to "Universe". (Bug 120052) * When archive admins accept single-source uploads from the queue, the source is now published immediately. (Bug 153617) * Launchpad is now able to find and automatically close a wider variety of bug references in package changelogs. (Bug 159841) * Bug listing pages for distribution source packages have a new panel that shows the latest versions of the package published in each distroseries and the component/section in which it appears. See https://bugs.launchpad.net/ubuntu/+source/kbd-chooser/ (Bug 93293) * The size of binary packages in PPAs is now reported correctly. (Bug 180983) * Package counts on PPA overview pages are now accurate. (Bug 141591) Code Hosting ============ * A new project overview page at https://code.launchpad.net/project shows the project's official branches, along with the most recent revisions from all associated branches. (Bugs 139441 and 79493) * Project branch listings now hide any branches over 180 days old if the branch listing does not fit a single page. A new check-box allows you to choose to view older branches. (Bug 79495) * When there are no upstream revision control details recorded for a product series, and you have permission to edit them, you are now offered links to register a Bazaar branch, link to an existing branch or request an import into a Bazaar branch. (Bug 49469) Bug Tracker =========== * Changing an existing bug watch is now easier. Simply paste the external bug's URL into the "change bug watch" form, rather than selecting the bug tracker and then entering the bug number. (Bug 74428) * New bug notification email subject lines are now prefixed with "[NEW]" to make them easier to identify. (Bug 29023) * Launchpad now recognises bug URLs from rt.cpan.org and correctly interprets the Trac status "accepted" to the Launchpad status "Confirmed. (Bugs 180210 and 180972) * External bug tracker overview pages now show private bugs but hide their title, number and status. (Bug 120144) * You now have the option of receiving the full original bug report in all bug notification emails. Visit https://launchpad.net/+people/+me/+edit then check the "Include bug descriptions when sending me bug notifications" box. (Bug 158668) * Bug listings are now sortable by the number of comments each bug has received. (Bug 137499) * If Launchpad is unable to import a bug watch's status, either because Launchpad doesn't yet know how to interpret the bug tracker's statuses or that instance of the bug tracker does not allow Launchpad to check for status updates, the bug watch page now shows a warning message. (Bug 32525) * You can now choose to search for either all or any of the tags you specify in a bug search. (Bug 66839) * When you file a bug, Launchpad shows you a list of similar bugs that have already been reported. If any of these bugs has duplicates, Launchpad now lists only the main bug and not its duplicates. (Bug 158455) Translations ============ * The translations import queue web interface is now faster. * When viewing strings marked as "untranslated", if you translate some or all of those strings Launchpad now correctly displays the following ten strings that require translation. Previously, it would skip some strings as the overall list had been shortened. (Bug 63557) * Some translation uploads previously failed incorrectly with a message saying that the file's revision date had not been updated. Similarly, some translation imports were failing if they specified their plural forms in an order other than the default for that language. Both of these issues have now been fixed. (Bug 183540). Blueprint ========= * Essential subscribers to a blueprint are now represented by a red icon in its subscriber list. Example: https://blueprints.launchpad.net/ubuntu/+spec/jeos-hardy (Bug 87962) -- Matthew Revell - talk to me about Launchpad Join us in #launchpad on irc.freenode.net -- warthogs mailing list warthogs@...1799... https://lists.ubuntu.com/mailman/listinfo/warthogs ----- End forwarded message -----

1 0

Fwd: Pencil tool interpolation
by R M 24 Jan '08

24 Jan '08

(Oops forgot to cc list) On Jan 24, 2008 12:41 PM, bulia byak <buliabyak@...400...> wrote: > Without trying the diff yet: smoothness is good but it's not the only > thing that matters. Sharp turns and corners, ideally, must be > recognized and created sharp, not smoothed out. How does your patch > compare to the current code in this respect? > this is the same code as is currently used. (i had written a different interpolation routine, but it turned out there was already one being used) The only difference is when it is applied. > Also: maybe while you're at it, you could also add the tolerance > slider to the controls bar of the tool, which is a very long-standing > feature gap. > a slider isn't appropriate as it stands, because there is no natural maximum value (ie it isn't a scale between 1-100%). iirc, Adobe illustrator handles this by bounding the tolerance between .5-25 pixels. we can do the same, and then have a slider. it makes some sense to cap this value, since extremely high tolerances are not useful in practice.

1 0