- Inkscape Devel - Inkscape Mailman

Inkscape icons and resolution
by Ashwin Bharambe 27 Jan '05

27 Jan '05

Hi all, This is just a random thought: is it possible for the icons to be differently stroked depending on the resolution? For example, I think many of the icons look much crisper (to me, at least) if I decrease the stroke width. However, if I go to a higher resolution display, they will perhaps look too "broken". -Ashwin

5 5

new tips
by bulia byak 26 Jan '05

26 Jan '05

New sections on export slicing and radial tiling are added to the top of the tips&tricks tutorial. The radial tiling one is big, and I know I need to write a whole new tutorial on clones and tiling and move that section there, but I don't have time right now. The radial placement trick was asked by two people, however, so I thought I'd write it up.

1 0

Question about translation
by Lucas Vieites 26 Jan '05

26 Jan '05

Hi, Arpad warned me about the imminent 0.41 freeze, so I started updating the spanish translation. There's a new feature called "Shift" which appears in strings like: "Horizontal shift per each column (in % of tile width)" What does this exactly do? Is it a movement of the tiles? Thanks, -- Lucas Vieites Fariña Dept. Desarrollo <lucas@...212...> Asix Informática <http://www.asixinformatica.com/> Tel/Fax: +34 986 54 26 98

3 4

Updated spanish translation
by Lucas Vieites 26 Jan '05

26 Jan '05

Hi, I'm attaching the updated spanish translation. Should I put it in the patch tracker at sourceforge? Cheers, -- Lucas Vieites Fariña Dept. Desarrollo <lucas@...212...> Asix Informática <http://www.asixinformatica.com/> Tel/Fax: +34 986 54 26 98

2 1

Re: [Inkscape-devel] User experience
by Pierre Boulenguez 26 Jan '05

26 Jan '05

Pierre Boulenguez a écrit : > bulia byak a écrit : > >> On Wed, 26 Jan 2005 12:24:44 +0100, Pierre Boulenguez >> <boulenguez@...558...> wrote: >> >> >>> * geometrical constraints (draw a tangent line, a perpendicular >>> ...), Rhinoceros3d has a very good look&feel for this. >>> >> >> >> Might be nice but I don't really see how this would fit our interface. >> I don't know anything about Rhinoceros3d; can you elaborate? >> >> >> >>> * mathematical characters. For this, xfig behavior is good to me as >>> it allows to insert Latex characters computed externally. The >>> problem here is that it cannot be integrated into SVG isn't it ? >>> >> >> >> In principle it's possible to do an extension that would store LaTeX >> fragments in extension attributes, run TeX to convert them to EPS, and >> import that EPS as an object. This was discussed here some time ago. >> All we need is a programmer motivated to do that. >> >> >> >>> * a simple way to add an arc between two lines to represent angles >>> (very important :-) ). >>> >> >> >> That's easy. Draw a circle from the tip of the angle with Ctrl+Shift, >> then drag the two handles at the right side of the circle to create an >> arc. See the Shapes tutorial for more details. >> >> >> > Ok, Rhinoceros3D is a modeler as blender is, except that it has an > awesome interface. > I never experienced such a behavior on any software I ever used !! > > As on other app, each ui button match a "function" but with > Rhinoceros3D, the "function" can also be called directly via the > built in command line. Actually, first come the comand line function, > and then, a button is sometime added as a "shortcut". > > Parameter of a function can be (example) > > * a 3d point, you can input either by clicking in the 3d scene or > entering digits in the command line > * a color > * a length (1d point) > * a scene object. Here let me give you some examples : > o You want to use the "scale" function. The input are a scale > factor and an object on which you want scaling to occur. It > can be any object as scaling is available for all objects. > The operation is then to select an object (via click in > the scene or ID in the command line ) and input a "length". > o You might want to trace the bisectrice of an angle. The > inputs are then two "line" objects. > o You want to draw a tangent, one of the inputs is of type > "curve" but there are many way to position a tangent on a > curve. It then exists multiple similar "tangent" functions, > just using different parameters. > > > A "function" doesn't necessarly posess a "shortcut" button as it is > always possible to access it via the command line. > > Those who does, let's say "draw an arc", are scrolling buttons meaning > that when you click on it, you access to a list of sub-buttons as it > exists multiple "draw an arc" functions, depending on different > parameters ( as the "tangent" function does). Of course, buttons and > sub-buttons use schematic idioms to make the interface intuitive. > > > This design have multiple benefits, I just point out lightweight but > very very powerful user interface, perfect adequation to C++ and, as a > consequence, a developer friendly plug-in interface. > > To make your own opinion, you might have a look at the Rhinoceros3D SDK. > > http://www.rhino3d.com/ > > I don't know if this help, but it was my only goal. > Pierre > > PS: thank you for the tip to draw an angle :-) > > >

1 0

inkscape_gtkmm: new dialog designs and other things
by Derek P. Moore 25 Jan '05

25 Jan '05

Howdy, I thought I'd post about the current state of inkscape_gtkmm. Here's a screenshot I just made showing off a few things (check it out before reading on): http://thestraycat.org/~derekm/inkscape/inkscape_gtkmm.png The Trace, Transform, and About dialogs in that screenshot are using libglademm and their XML specification in share/ui/glade/dialogs.glade to do most of the work. If you'd like to help make/improve dialogs for the Gtkmm conversion effort, fetch: http://cvs.sourceforge.net/viewcvs.py/inkscape/experimental/bryce/inkscape_… I have a few different prototypes for the Trace dialog. They are: http://thestraycat.org/~derekm/inkscape/Trace.png http://thestraycat.org/~derekm/inkscape/Trace2.png http://thestraycat.org/~derekm/inkscape/Trace3.png Which one is best? I tend to think probably Trace3.png. The "Inkscape Preferences" dialog shown in the screenshot is unfinished (many of its pages are blank) and doesn't use Glade. I'm just showing it to emphasize the current state of things. Besides the dialogs shown in the screenshot, there are only a few more mostly unfinished dialogs in the inkscape_gtkmm codebase. However, empty placeholders do exist in the code for all dialogs that need to be implemented. I've been working a lot on the dialogs lately, and andreas_n has started helping out. I have a "Document Properties" dialog I'm finishing, and andreas_n has said he's starting on the "Object Properties" dialog. I've been experimenting a lot with libglademm in the dialogs, and I'm becoming rather in favor of libglademm's use in the Gtkmm-ification effort. I've been able to create dialogs much quicker and more efficiently with libglademm, it's very flexible and simple to work with (imho). JonCruz and Bryce have been doing more work on the Units subsystem. JonCruz has brought an XML format and parser (via his new SimpleSAX stuff) to Units (for loading unit definitions, ratios, etc. at runtime from XML [instead of Bryce's original flat text file]). It also looks like SimpleSAX could be used for the new preferences system that's yet to be written for the Gtkmm-ification work. Anyways, that's all I've got to report... Anybody else got anything? Derek

7 11

Re: [Inkscape-devel] inkscape_gtkmm: new dialog designs and other things
by Bob Jamison 25 Jan '05

25 Jan '05

I think that this argument is moot, as I think that Derek and I have agreed on option 3. Well, Jeez.... I agree with you on most things, but I'm afraid that I must disagree on this one small thing. The different tracing algorithms need different parameters. Crowding a small set of "user friendly" params onto a mismatched set of algorithms would not work. "Single scan" and "multi scan" are artificial ideas that I made up myself to fit my 3 input filters and 2 output filters onto Potrace. They do not map to anything but my weak idea of how to wedge Potrace into Inkscape. They are all silly tricks on how to make a black & white tracer work on color bitmaps. Potrace does NOT do color. The next tracer (not Autotrace) that I have in mind works natively in colorspace, with no intermediate bitmap (thus no Preview) and works by tracing along lines of constant color slope. Bob mental@...658... wrote: >Quoting Alexandre Prokoudine <alexandre.prokoudine@...400...>: > > > >>If multiply scanning with autotrace is possible, then there might be >>no reason to separate trace engines with tabs there. All we need is a >>switcher between engines (2 radiobuttons or a combobox). Functionality >>is in the first place, name of engine that provides it -- in the >>second ;) >> >> > >Yes. We ought to use the hierarchy dictated by the users' needs, not the >structure of the implementation. > >-mental > > >------------------------------------------------------- > >

1 1

Re: Bug Status for 0.41 -- 1/24
by Bryce Harrington 25 Jan '05

25 Jan '05

Now that we're in the triple digits, it is time to start wrapping up any remaining feature work currently under way. I'd like to propose the following rough timeline (exact dates may vary): Feature Freeze - Jan 26 Hard Freeze - Feb 1 Release - Feb 5 Bug ID# PRI Owner Description ------------------------------------------------------------------------ 1105787 9 johncl Installation problem: libatk-1.0-0.dll not found 990677 6 ted readme needed for extensions 1107562 9 bulia Node Align Crash 1101210 3 bulia CVS: Flowtext not working 1103001 3 ted Grid is shown non-uniform 1102318 9 kees Crash on "save as" 1104741 6 bulia Printout 25% too large 1105352 6 pjrm Markers are not shown in Plain-SVG-Export 1075860 9 pjrm WIN: assert when doing stamping during move 1080252 9 bryce crash on intersectiion 1068116 6 mental complie error in gc.cpp with inkscape-20041116 1076872 6 kees ngettext isn't used 933461 6 kees Win32 Install Directories 1068299 6 kees Build failure on mips(el) 1100675 6 mental svg tag requires xmlns attribute in CVS2005-01-10 1097652 9 pjrm crash on whitespace property value ------------------------------------------------------------------------ Current: 108 Goal: 150 On Sat, 8 Jan 2005, Bryce Harrington wrote: > Okay, since there were no comments to the contrary, I suppose it's safe > to assume this proposal is acceptable to everyone. If not, lemme know. > We'll shoot for 150 points for low/med/high (3/6/9 pts) that are closed > as FIXED (i.e., no points for dups, won't fix, invalid, etc.) and that > are confirmed as present in 0.40 or in CVS. > > Bryce

1 0

OSDL Desktop Linux Capabilities
by Bryce Harrington 25 Jan '05

25 Jan '05

For those interested in desktop linux in general, OSDL put out a first public draft (v0.9)of its DTL Capabilities document, for community review and comment. http://osdl.org/lab_activities/desktop_linux/DTL09/ Please feel free to send comment through myself or the mailing list on that page. (List subscription info is at lists.osdl.org.) Bryce

1 0

Papers for Technical Conferences?
by Bryce Harrington 25 Jan '05

25 Jan '05

Interested in writing a technical paper about Inkscape? We're now in "Tech Paper Season", when the proposals for papers are coming due for many technical conferences between now and March, such as OSCON, LWE, etc. What's due right now is not the paper itself but just the proposal. That's a couple paragraphs and the promise to write a full paper if your proposal is accepted. Why write a journal paper on Inkscape? First, it's an extremely good way to earn some PR for Inkscape. Second, published technical papers are something you can include on your resume or CV for your whole career. If you have a career in either art or programming, that will be a solid foundation stone for you. Third, it helps move Inkscape into a more "professional" space and will help encourage all of us to make the tool even better. If you're unsure about writing a technical paper alone, or want a co-author, let me know. I may write something myself but would much prefer co-authoring with other folks. Tell me your ideas and let's see what we can do. For topics, there are clearly three topics we can provide information about: Computer Graphics, Programming/Technology, and Open Source Processes. Probably more beyond that. Obviously, no guarantees getting a paper accepted, except if we don't try, we'll definitely not be accepted. But the more we try, the more opportunities we have to succeed. ;-) Bryce

3 2