- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] printf
by bulia byak 13 Dec '03

13 Dec '03

> > > If not for this problem, does printf satisfy our requirements or are >there > > > any other problems with it? If it's OK, maybe we could just include >the > > > "standard" printf right into our codebase, instead of linking to a >library? > > > Just an idea. > > > > Possibly, but if we do one ourselves we can be more clever with e.g. > > rounding behavior. Anyway, Bryce said he alraedy had some code > > somewhere, as I recall... > > > >Yes, I do. I've added a task for myself to add this to the codebase. The reason I ask this questions is because I see how Lauris is handling this in 0.33. Now instead of a single printf call, he declares a char[] buffer for each value, calls a custom conversion function, and then assembles these buffers into a string. That is extremely bulky and hard to read, and I would like to avoid this if possible, preserving the format string approach of printf. So, how close is your code to being a drop-in replacement for printf with its format strings? _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

3 2

printf
by bulia byak 13 Dec '03

13 Dec '03

>*printf() exhibits locale-dependent behavior on win32; we >need to replace it with our own code for generating correct >SVG measurements regardless of locale. If not for this problem, does printf satisfy our requirements or are there any other problems with it? If it's OK, maybe we could just include the "standard" printf right into our codebase, instead of linking to a library? Just an idea. _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

3 2

handling statusbar messages
by bulia byak 13 Dec '03

13 Dec '03

Currently, whoever needs to update statusbar calls sp_view_set_status() giving it the message and a pointer to a SPView object. This function emits a signal from that SPView object, and this signal is caught by the desktop object which does actual update to the statusbar (using gtk_statusbar_push()). This seems strange. Why is SPView involved at all? In ALL cases when sp_view_set_status() is called, the caller code has (or finds out) the current desktop and then finds its SPView by saying SP_VIEW(desktop), only to pass this to the sp_view_set_status(). Given that the message ends up being handled by the desktop anyway, the entire mess with SPView and emitting/catching signals seems unnecessary to me. The code needing to update statusbar could call a function in desktop.c directly, either giving it some desktop pointer, or even letting it find out the current desktop automatically. The signal and the statusbar-setting functions in view.c could then be eliminated. I think the code would be simpler and more logical this way. Any comments? _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

2 1

zoom and precision
by bulia byak 12 Dec '03

12 Dec '03

I've augmented my libnr precision and 256x zoom patch with a fix to store SVG paths with 8 digits instead of 6 (changing %g to %.8g in printfs in svg/svg-path.c). Since I've been using this patch for some time and have not seen any problems, so I decided to commit it now. This is code that is in use literally every second, so by putting it in early in the release cycle we'll be able to catch more bugs with it. Please work and play at higher resolutions than you usually do and submit any bugs to the tracker. Note that you'll need to rerun configure after updating because I patched libnr/gen_nr_config.c which is recompiled and rerun on configure (I think). _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

1 0

Open Source myths
by Jon A.Cruz 12 Dec '03

12 Dec '03

Here's a nice little article on software development http://www.onlamp.com/pub/a/onlamp/2003/12/11/myths.html Of all the issues raised, the ones I've thought about I'm in agreement with. The few I hadn't consciously considered before seem to be right on track also. In all, it seems that these are things that those in the Inkscape community are doing, however it's always good to explicitly state what's good and why. Among other things it might help us improve and also just keep us on track. (so at the very least, read the article and keep things in mind)

1 0

C++-ification
by Bryce Harrington 12 Dec '03

12 Dec '03

Just a quick head's up, we're about to proceed with the renaming of all .c files to .cpp. Nathan is working on updating Makefiles &tc. presently and if it works out, he'll be committing the changes soon. The expected near-term effects to be aware of: * Change histories on code files will be reset * Potential build issues on some platforms * Everyone will need to cvs update -Pd, make distclean, and rebuild * Compilation with gcc will cease to work as support for gcc is ended * If you are working on a branch or out of sync with CVS HEAD, your next merge may be more complicated than usual due to the file rename These issues should be transitory, but please expect some turbulence for a bit. Thanks, Bryce

2 2

Re: [Sodipodi-list] Re: 0.8 multiplier
by MenTaLguY 12 Dec '03

12 Dec '03

On Thu, 2003-12-11 at 13:06, Lauris Kaplinski wrote: > SVG spec is resolution agnostic. Yes, but I finally read this part of the SVG spec... > All its units are just > defined as certain ratios of undefined base unit (pixel), that > may or may not be related to some real-world unit. For the initial coordinate system, the SVG specification refers to CSS2's definition of length units, which broadly specifies two classes of units: 1. relative units which do NOT have fixed relationships with real-world units * em and ex: determined by the current font size * px: determined by the user agent, generally some multiple of device pixels 2. absolute units which _are real-world units_ (subject to the user-agent's ability and desire to match them) * mm: real-world mm * cm: 10 mm * in: 2.54 cm * pt: 1/72 in * pc: 12 pt > Sodipodi document has real-world dimensions. > To map resolution agnostic SVG onto real-world paper, it uses > mapping: > 1 SVG point == 1 typographic point (To be totally pedantic, typographic points are 0.0138 in, which is not _quite_ the same as Postscript/SVG points [1/72 = 0.01388888...]; I think everyone uses the Postscript definition nowadays though.) > As 1SVG point == 1.25 SVG pixels, and pixels are SVG base units, > SVG base unit == 0.8 typographic points on all sodipodi documents. Unless a viewBox is set, the relationship between user-space base units (pixels) and the absolute units is totally user-agent dependent. (this is why all examples in the SVG spec specify a viewBox) Thinking about this, if Sodipodi intends to be completely interoperable, it needs to always write a default viewBox according to the base units/points mapping it imposes. e.g. for a document 100ptx100pt, the viewBox should be "0 0 125 125". -mental

1 0

menu reorg
by bulia byak 12 Dec '03

12 Dec '03

I propose to break Edit menu into two, Edit and Object. Otherwise it's pretty long already, and will be still longer when we add boolean ops. I think everyrhing up to and including Clear All/Select All should remain in Edit, and the remainder of items should go to Object. If there are no objections, I will commit (it's a cosmetic patch so it's unlikely to break anything). _________________________________________________________________ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus&pgmarket=en-ca&RU=http%3a%2f%2fjoi…

2 1

0.37 plan
by Bryce Harrington 12 Dec '03

12 Dec '03

It's very cool to have 0.36 out the door after so much work! It's being well received by the community, and the feedback is that we've definitely made notable improvement over the baseline. So what's next? First, as we talked about, we're going to keep things low key the rest of the month, and enjoy the holidays. This next release is going to be a bit different than this past one. For 0.36 our goal was to strive to get some new features in and revamp the look and feel, to prove that this project brings new value to the community and to gain experience working as a project. For the 0.37 release our focus is going to change. We want to make the codebase itself better, so that it is easier and more enjoyable for us to work on in the future. Doing this will require undertaking several sizeable endeavors: * Convert the codebase to C++ * Change from function prefixing to true C++ namespaces * Adopt a new code style * Remove all obsolete code * Organize all of our documentation The above work will touch pretty much all the files in the codebase, and since that could be a significant amount of work, I think we should use a divide-and-conquer approach to it. A way to achieve this is to divide the codebase into several distinct "subsystems"; this way the size of the commitment each of us must make will be tractible, and so that we can work together as a team to achieve them. I'll establish a list of these subsystems shortly; there is a diagram on the Documentation page of the website to give some hints as to what this list will be. In addition, there are several features we'd like to pursue, such as reorganizing the dialogs, Fred's new booleans work, and Nathan's grid code. There are also a number of bugs we decided to leave to this release, that should receive attention. We can look forward to seeing these features and bug fixes folded in, as we proceed with the principle objective of the code conversion and cleanup. Bryce

1 0

Plugins - first cut at requirements list
by Bryce Harrington 12 Dec '03

12 Dec '03

I've posted my first stab at a list of requirements for a plugin/extension/module system here: http://www.inkscape.org/cgi-bin/wiki.pl?PlugIns Ted's done a good bit of work on implementing support for a module system, so hopefully this list can be made to mesh with that work. The intent of making a requirements list is to firmly identify what we want out of this system, so that as folks work on implementing it, it is clear what it needs to do. Please look it over and add your thoughts of what should be in there. Bryce

1 0