- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] Call for Freeze Exceptions
by the Adib 22 Dec '07

22 Dec '07

On Dec 22, 2007 1:06 AM, Adib taraben <theAdib@...400...> wrote: > Bryce Harrington schrieb: > > Hi all, > ... > > So, if you're working on a feature, can you please tell me at this time? > Also please report: > > * Current status > * Anticipated date of completion > * Issues that must be solved before release > > ... > Bryce > > > Bryce, there is one thing that we need to negotiate: > > as we have several exporters for one and the same format, we need to > decide if we have one exporter only or both in the release. > > We have this native PS and Cairo PS. Also there might be extensions using > the uniconverter to convert from/to ai- or wmf-format. > > Last I also want to point > Uups there was something missing: Last, I want to point to this issue: http://bugs.launchpad.net/inkscape/+bug/177783 This is a windows only problem there might be a solution that we use a self patched version of cairo. HTH, Adib. ---

2 1

Inkscape 0.46 Frost (and Frost Exceptions)
by Bryce Harrington 21 Dec '07

21 Dec '07

[Also posted to http://www.inkscape.org] We've made huge progress towards the Chill goals, and are now ready to move into the Frost phase. Development is winding down, although we are granting a few frost exceptions to allow continued work for another week or so in specific areas (see below). 'make distcheck' issues have been sufficiently resolved (thanks Ted and Aaron!) Bug report triaging has gone smashingly well. The About Screen contest has kicked off. We still need to put some attention into the release notes, tutorials, and other docs, but I doubt there's any issues preventing us from moving ahead. In the Frost phase, our objectives are as follows: * Complete frost exception development work. * Focus should be on bug fixes, packaging, documentation, and translation work, all of which may be committed to SVN normally. * Gain some candidate submissions for the About Screen contest. * Release Notes should be >90% filled in. * Bug Hunt (details TBD) * Post inkscape-0.46-alpha.tar.gz The length of time we stay in Frost mode is driven by how long the Bug Hunt takes, but is expected to take on the order of a few weeks. The Frost Exceptions for remaining features are as follows: 1. Angled guidelines, by J.B.C.Engelen (ETA Dec 23rd): Underlying code is complete, and guidelines are rendering, but it needs a UI to allow manipulating them. 2. Python module packaging (lxml, numpy) for OSX, by jiho (ETA ___): Needs wider testing. Needs someone to build PPC packages. 3. Compilation of lib2geom on OS X 10.3 (Panther), by John Faith (ETA ___): An error is preventing builds for Panther versions of Inkscape. If this can't be resolved before release, the alternative is to drop support for this OS version. 4. Font Spec Implementation, by Gail Carmichael (ETA Dec 27). Refactor patch to include some code review changes by Bulia. Also, the patch needs wider testing. 5. Win32 Uninstaller improvement, by Adib (ETA Jan 3). Fix current installer to not bug user for each changed file. 6. PDF, PS export improvements, by Adib (ETA Jan 3). Implement blur as bitmap, and display a dialog with options for text-to-path, blur-as-bitmap, alpha-as-bitmap. 7. Clone Tiling dialog, by Tavmjong Bah (ETA Dec 23rd): Add a few options to Shift, Scaling, and Rotation tabs. Also some small changes for default values for turbulence and composite filters. Feature changes in SVN for things not on this list should be done on a branch. Any feature work not in this list committed to SVN during the Frost period may be reverted by any developer. Bug fixes, translation work, documentation updates, and packaging development may continue to be committed as normal, no permission needed yet.

1 0

Truetype Collection fonts
by Donn 21 Dec '07

21 Dec '07

Just wondering, Does Inkscape see Truetype Collection (.ttc) fonts under Linux (fontconfig)? I was pointed to one here: http://distro.ibiblio.org/pub/linux/distributions/gentoo/distfiles/mikachan… I installed it (into ~/.fonts) and it's name does not come up in the list in the font chooser. >From what I can tell, Gimp does not see it either. I might not be seeing it in the list, but it's named 'mikachan' and I don't find that. I am trying to see if it's worth building support for them into Fonty Python. \d

1 0

Any Mac Guys about???? was lxml errors on os X.5
by john cliff 21 Dec '07

21 Dec '07

Hey Guys, Just bringing this one back to the surface, as carls been trying to get help on this for a few days in the chat room but non of us know anything mac related. If any of you can shed some light it would be appreciated. Cheers Sim On 12/18/07, carl olsen <cidic.conspiracy@...400...> wrote: > > I'm on OS X.5 with Inkscape 0.45+devel, built Dec 8 2007 > Whenever I try to use a filter get this: > [] < The fantabulous lxml wrapper for libxml2 is required by inkex_lxml.py > and therefore this extension. Please download the latest version from < > http://cheeseshop.python.org/pypi/lxml/>. > [ ] <and when i try to install it, it has an error and doesnt finnish and > I can't figure out what is up. > This is a copy of all the stuff from the terminal when i'm trying to > instal lxml: > easy_install lxml > Searching for lxml > Reading http://pypi.python.org/simple/lxml/ > Reading http://codespeak.net/lxml > Best match: lxml 2.0alpha5 > Downloading http://cheeseshop.python.org/packages/source/l/lxml/lxml-2.0alpha5.tar.gz > > Processing lxml-2.0alpha5.tar.gz > Running lxml-2.0alpha5/setup.py -q bdist_egg --dist-dir > /var/folders/H9/H9Jwuv1LGha040cHGswzMk+++TI/-Tmp-/easy_install-Dt6zmJ/lxml- > 2.0alpha5/egg-dist-tmp-Inbqr_ > Building with Cython 0.9.6.9. > Building lxml version 2.0.alpha5. > warning: no previously-included files found matching 'doc/pyrex.txt' > warning: no previously-included files found matching 'src/lxml/etree.pxi' > src/lxml/lxml.etree.c:69:31:src/lxml/lxml.etree.c:69:31: error: error: > libxml/schematron.h: No such file or directory > libxml/schematron.h: No such file or directory > lipo: can't open input file: > /var/folders/H9/H9Jwuv1LGha040cHGswzMk+++TI/-Tmp-//ccI51eCM.out (No such > file or directory) > error: Setup script exited with error: command 'gcc' failed with exit > status 1 > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services > for just about anything Open Source. > > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > >

2 1

Template question
by John Faith 21 Dec '07

21 Dec '07

Hello, There seems to be a template problem in 2geom which is preventing OS X 10.3 (gcc 3.3) from compiling. This is an example of code which fails, simplified from 2geom/path.h and 2geom/svg-path.h: //-------------------------------------- // build with: g++ -c -o test.o test.cpp class LineSegment; class Point; class Path { public: template <typename CurveType, typename A> void appendNew(A a) { do_append(new CurveType((*final_)[0], a)); } }; template <typename OutputIterator> class SVGPathGenerator /*: public SVGPathSink*/ { public: void lineTo(Point p) { _path.appendNew<LineSegment>(p); //<---error: parse error before `;' token } protected: Path _path; }; //-------------------------------------- I can get this example to compile by making the whole Path class the template versus just the appendNew method, but it's not clear that making this change would be the right way to go in src/2geom/path.h. Does anyone with template experience or 2geom knowledge have any ideas on how this might be simplified to make older compilers happy? Thanks! , John

2 2

Dockable text dialog
by Karlisson 21 Dec '07

21 Dec '07

Hi list, I compiled the new development version, 0.46, and noticed that it doesn't have a dockable text and xml dialogs. Will them be dockable in this version? Thanks! -- Karlisson de Macêdo Bezerra http://nerdson.com/ - "Don´t panic!"

1 0

Re: [Inkscape-devel] Call for Freeze Exceptions
by unknown＠example.com 21 Dec '07

21 Dec '07

> -----Original Message----- > From: Engelen, J.B.C. (Johan) > Sent: donderdag 20 december 2007 10:57 > To: Bryce Harrington; inkscape-devel(a)lists.sourceforge.net > Subject: RE: [Inkscape-devel] Call for Freeze Exceptions > > Angled guidelines. > > * current status: > setting them in XML works, snapping works, the underlying > code is completely in angled guideline terms. However, there > is no UI and angled guidelines are not rendered on-canvas > (they are invisible). > > * anticipated date of completion: > this weekend? > > * issues to be resolved: > UI > rendering (axonomgrid already has this, so not too much work) Rendering is implemented right now. You can manually adjust the XML (set orientation to the normal_to_gridline that you want (i.e. "1,1" for a 45 degree line). Working on UI asap. Thanks for testing, Regards, Johan

1 0

Fwd: Launchpad 1.1.12 released!
by Bryce Harrington 20 Dec '07

20 Dec '07

Note there's a fix to indicate if you try assigning a bug to someone not involved in the project. ----- Forwarded message from Matthew Revell <matthew.revell@...1798...> ----- Date: Thu, 20 Dec 2007 21:59:05 +0000 From: Matthew Revell <matthew.revell@...1798...> To: warthogs@...1799... Subject: Launchpad 1.1.12 released! X-Spam-Status: No, score=0.6 required=5.0 tests=EMPTY_MESSAGE autolearn=no version=3.2.3 Welcome to the last Launchpad release of 2007! The highlights of Launchpad 1.1.12 include: * Project announcements: get the latest news from a project or distribution directly on its Launchpad overview page. Or subscribe to its Atom feed. * Bug feeds: subscribe to an Atom feed of all the bugs related to any distribution, project, team and person in Launchpad. Also subscribe to individual bugs. * Higher quality bug reports: if you're a project owner you can now ask Launchpad to display your bug reporting guidelines to people who file bugs against your project. * Launchpad is running Bazaar 1.0.0. Congratulations to the Bazaar team on this new release! Read on to get the full details of what's new in this release. See you next year when we'll be back in January with Launchpad 1.2.1! General Launchpad ================= * You can now subscribe to an Atom feed of an individual bug and of all the bugs relating to a person, team or project. See our guide at https://help.launchpad.net/Feeds * If you are a project or distribution owner, you can now publish news and announcements on your project overview page and as an Atom feed. See our guide at https://help.launchpad.net/ProjectAnnouncements * Launchpad automatically creates person profiles if it comes across a package with an email address it hasn't seen before. Sometimes, these "people" should be Launchpad teams. Now, someone with access to the team's email address can convert the Launchpad user into a team. (Bug 36966) * Your personal profile page now shows the date that you joined Launchpad. (Bug 157840) Distribution Management and PPA (Soyuz) ======================================= * Personal Package Archives now check the primary Ubuntu archive for candidate orig.tar.gz files. (Bug 139619) * Personal Package Archives upload and build notification emails now have a 'X-Launchpad-PPA: $ppa_owner_name' header. (Bug 172377) * Package history pages are now easier to use. All information about a package's publication is now available as an expandable section of the publication history table. (Bug 157064) * In a recent change, we disabled all email announcements for Debian syncs. We have now re-enabled notification of manual syncs. (Bug 174464) * Pockets with deleted publications are now detected and processed correctly. (Bug 163384) * You can now remove an association between a source package and a project release series. (Bug 4556) * Mirror overview pages now show the lines you need to add to /etc/apt/sources.list in order to use that mirror. (Bug 51870) Bug Tracker =========== * In the future, Launchpad will offer projects and distributions the option of automatically expiring bugs that have an "Incomplete" status, are inactive and are unattended. This feature is not yet active. However, project/distro bug overview pages now offer a report that shows which bugs would be automatically expired, were it enabled, and a notice is now displayed on the bug page for any bug that would be affected. Find out more at https://help.launchpad.net/BugExpiry (Bugs 163579, 141604) * Projects and distributions can now set custom "bug reporting guidelines" for Launchpad to display at various points during the bug reporting process, in particular at the start. If you're a project or distribution owner, you can add and edit these guidelines from the project or distro's "Change details" page. (Bug 43893) * If you assign a bug to someone that Launchpad doesn't recognise as having a previous involvement in that project, Launchpad will notify you that you may have assigned it to the wrong person. (Bug 138500) * Launchpad now imports bug statuses from the Sourceforge and RT issue trackers. The Trac "closed" status is now correctly interpreted as Launchpad's "Fix Released" status, rather than "Invalid". (Bugs 66529, 121340, 174662) * If a bug is targeted to a milestone, a "milestone" badge will appear next to it in bug listings. (Bug 172729) * Some bug reports are actually requests for help. A new "Convert to question" option is now available in the Actions menu on bug pages. (Bug 3970) * You can now sort bug listings by the number of duplicates that each bug has. Code Hosting ============ * Launchpad is now using Bazaar 1.0.0. Congratulations to the Bazaar team on this release! You can always find out which Bazaar version Launchpad is running by visiting the Code Hosting home page. * Branch whiteboards are now editable by anyone. Following an edit, Launchpad notifies the branch owner. (Bug 149226) * When proposing a branch for merger, the default target branch is now the branch that is associated with the development focus series. Alternative targets are presented, with an option to specify any other branch as a target. * A branch listing in the context of a product now highlights the development focus branch if one is set for the development focus series. * When searching for branches - for example, to use as the target of a merge proposal - the search now also checks the name of the branch owner and the name of the project that the branch is connected to. (Bug 176247) * Launchpad Code's web interface now allows you to register branches that have underscores "_" in their name. It has always been possible to push a branch to Launchpad that uses underscores in its name. (Bug 95109) * Launchpad can now correctly import CVS and Subversion repositories with files whose names contain characters that require URI encoding - e.g. #, +, space, etc. (Bug 69517) Translations ============ * The "Untranslated", "Need review" and "Changed" counts on translation overview pages now link to listings of the strings in those categories. The numbers shown are also now accurate. (Bugs 172253, 173527) * When you upload a translation file with a different ordering of plural forms, Launchpad now tries to remap it to the default ordering for the language. Blueprint ========= * Series blueprint listings now show the milestone to which the blueprint is targeted. (Bug 128280) Answers ======= * When offering an answer to a question, you can easily link to an FAQ by quoting its number and title. For example: 'FAQ #3: "Restricted Formats"' in an answer to an Ubuntu question is now automatically linked to https://answers.edge.launchpad.net/ubuntu/+faq/3 (Bug 126371) -- Matthew Revell - talk to me about Launchpad Join us in #launchpad on irc.freenode.net ----- End forwarded message -----

1 0

Launchpad Tips & Tricks: Greasemonkey helper scripts
by Bryce Harrington 20 Dec '07

20 Dec '07

Hi all, Kees Cook wrote a couple tools to help make bug triaging easier, and for those of working in Launchpad these are highly recommended! For those with greasemonkey already installed, just go to this link and click 'download' on the two .js files and enjoy. http://codebrowse.launchpad.net/~ubuntu-dev/ubuntu-gm-scripts/ubuntu/files For everyone else, please read on... Bryce Ubuntu Greasemonkey Scripts --============[o]============-- The ubuntu-gm-scripts project collects useful Firefox GreaseMonkey scripts that assist Launchpad bug triagers in working more effectively and efficiently. Installation ============ GreaseMonkey is a Firefox extension for adding macro-like capabilities to do javascript-ish things on top of certain web pages. To install GreaseMonkey, follow these steps: * Go to Firefox->Tools->AddOns * Click Get Extensions (or Get Ubuntu AddOns if on Ubuntu) * Select GreaseMonkey, and install * Restart Firefox Then to install these scripts, run: * firefox lp_karma_suffix.user.js * firefox lp_stockreplies.user.js Or click on the scripts from your file browser. For the latest updates to the scripts, go to the following link and click 'download' for each of them: http://codebrowse.launchpad.net/~ubuntu-dev/ubuntu-gm-scripts/ubuntu/files Launchpad Karma Suffix ====================== When triaging bugs, it helps to have some way to gauge the relative experience of the person reporting or commenting on a given bug. This tool helps by appending the person's karma score after their name. As well, team membership can denote experience/involved-ness, so this tool also appends icons indicating for some teams that the person is in. This is helpful for flagging comments/flags from the bug triaging team, core developers, and so on. As there are a LOT of teams in launchpad, most of which you may not care about, only a select number of teams are included by default. You can customize the list by editing the Javascript as follows: * In Firefox go to Tools->Greasemonkey->Manage User Scripts * Select LP_Karma_Suffix * Click the Edit button at the bottom, and type in the name of your preferred text editor. E.g. "/usr/bin/gedit" or "C:\windows\notepad.exe" * Scroll down to the 'team_handler' function and find where the teams variable is defined, then add a line with your new team. For instance, to add the Inkscape Bug Team to your list, modify teams to look like this: var teams = { 'inkscape.bugs':'', 'motu-swat':'', 'bugsquad':'', 'ubuntu-core-dev':'', 'ubuntu-dev':'', 'ubuntu-bugcontrol':'', 'ubuntumembers':'' }; * [Note that the team must have a 14x14 icon defined with it in order to see anything. This can be set by a team admin via the 'Change branding' link on the Launchpad team overview page.] * Save and exit the text editor, then go back to the Manage User Scripts dialog and click OK. * Reload some pages to see the icon. :-) Launchpad Stock Replies ======================= When processing through a lot of bugs, often you wish to make essentially the same comment over and over again, such as, "Thanks for reporting this blah blah... Please attach foo.log, so we can..." This script helps avoid a lot of retyping or manual cut-n-pastes by providing a way to store your own canned comments in Firefox itself. It then adds links for each of your canned comments right above the "Comment on this change" field, making it convenient to select a stock reply to send. To add new stock replies, click the [+] link, which will bring up options to add or save stock replies. Add New Stock Reply: name A tag id for the reply. (Avoid punctuation) comment Sets the comment field to this value status Sets the status dropdown to this text key assign Assigns the bug to this launchpad username importance Sets the importance dropdown to this text key package Sets the package field (if it is present) to this text Save Stock Replies: After making additions or changes to any of the replies, click this to save the changes. Also See ======== * Firefox Launchpad Plugin

2 1

CTRL+D Broken?
by Guillermo Espertino 20 Dec '07

20 Dec '07

I'm using a SVN version compiled yesterday and CTRL+D, ALT+D and SHIFT+D don't work. Instead of the expected functions it changes the tool selection to the color picker. I'm about to file a bug, but I wanted to double check if anyone with the current svn revision has the same problem. Regards, Gez.

4 3