- Inkscape Devel - Inkscape Mailman

about screen
by Jonathan Phillips 07 Feb '04

07 Feb '04

I think something I will do is adapt the nice graphical ledger at the bottom/top of the TUTORIAL for our about window tomorrow. Good job BULIA/NJH and others on that! Jon -- Jonathan Phillips <jon@...15...>

3 3

text undo bug
by MenTaLguY 07 Feb '04

07 Feb '04

Bulia, you were right. Not only was the bug in the undo code, it was in the Repr transaction logging stuff. The problem was that, on reversion of the log, content change events were pulling from the wrong union member, and erroneously "reverting" to the "after" state rather than the proper "before" state. Fixed in CVS. -mental

1 0

Re: [Inkscape-devel] Re: undoing text node changes
by bulia byak 07 Feb '04

07 Feb '04

> > SF is up again. Baically the order of undo actions is wrong, and some > > actions may be lost, when text nodes are edited (no matter whether it's >done > > by text tool or by XML editor). > >As I've already commented, the problem is that there is no unified undo >layer for repr actions and other things (like text cursor movement). > >The Repr transaction logging layer is fine as it is -- the thing is that >we need undo records at the SPDocument layer that can hold more than >just Repr transaction logs. I may be misunderstanding you. What you say may be correct, but it does not apply to this bug as far as I can tell. What needs to be logged here is nothing but a repr change, namely a change in the content of the text node inside tspan. This is what is broken. The fact that undo does not know about cursor movements is irrelevant - it must simply restore the previous content of the node, and that's what it cannot do properly. The fact that the behavior is the same no matter whether you edit the text node by the text tool or directly in the XML editor proves that the text tool is not the problem, the problem is inside the undo system. >I do have a rough sketch in my mind for a new undo abstraction -- >basically a generic undo stack and a 'log entry' base class that variuos >subsystems can subclass for undoing/redoing specific things. > >We could even use it for the next/prev zoom feature (i.e. use one of >these generic undo stacks for document editing history, and another for >zoom history). It's very nice, but currently I'm concerned about this particular bug. I think it must be fixed before the release, because it's pretty annoying. Sometimes (I couldn't figure exactly when) editing text even breaks undo completely, i.e. I get "operation did not complete transaction" and cannot undo any more. _________________________________________________________________ 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…

2 1

[Fwd: [Sodipodi-list] Sodipodi 0.34 soon]
by Jonathan Phillips 07 Feb '04

07 Feb '04

-----Forwarded Message----- From: Lauris Kaplinski <lauris@...39...> To: sodipodi-list(a)lists.sourceforge.net Cc: gnome-i18n@...45... Subject: [Sodipodi-list] Sodipodi 0.34 soon Date: Sat, 07 Feb 2004 01:11:38 +0200 Hello! Sodipodi 0.34 is scheduled to be released early next week, so now is good opportunity to update translations. Very little is changed, few wordings here and there and some new strings, so the update should be easy. If you prefer tarball to CVS, the beta package with frozen strings can be downloaded from: http://lauris.kaplinski.com/sodipodi/sodipodi-0.34-beta1.tar.gz Best wishes, Lauris Kaplinski ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Sodipodi-list mailing list Sodipodi-list(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sodipodi-list -- Jonathan Phillips <jon@...15...>

1 0

Re: [Inkscape-devel] inkview slideshow - was fullscreen
by Peter Linnell 07 Feb '04

07 Feb '04

Sources for Open Office XML specs: http://www-106.ibm.com/developerworks/xml/library/x-think15/ http://xml.openoffice.org/

1 0

RE: [Inkscape-devel] fr.po file
by bulia byak 06 Feb '04

06 Feb '04

>I have done an update of the fr.po file. Thanks, but your file seems to be quite old. Recently a lot of code was rearranged, and plenty of new interface string were added. The CVS version of fr.po is 85 Kb (even though many strings are not translated there) versus 76 Kb of your file. Can you update the latest CVS version of the file instead? Or at least, can you merge the new translations you made into the CVS file? http://cvs.sourceforge.net/viewcvs.py/inkscape/inkscape/po/ _________________________________________________________________ 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

fr.po file
by Frederic Rodrigo 06 Feb '04

06 Feb '04

Hi, I have done an update of the fr.po file. Fred.

2 1

Re: [Inkscape-devel] drawing tools broken
by bulia byak 06 Feb '04

06 Feb '04

>were working (such as CVS)? I find your lack of faith disturbing - why are >you allowed to make keybinding changes, yet others are not allowed to fix >real problems with the code? I never said you are "not allowed". It's just that I never commit 10+ files at once. (To be honest, I just committed 9, but it's a rare exception, and the changes are similar and minor). And I test thoroughly before committing (although errors do slip in, but they are usually minor or not easy to notice). I'm not saying that you don't test, but it's obviously more difficult to test even the basic functions when you commit lots of changes in lots of files, as has been done recently. >You claim it is severely broken, yet the fix was to add one line. Please >don't over react. "Severely" does not mean "hard to fix". It only means "very visibly, rendering some basic functions unusable". I think it's an accurate description of this bug. Sorry if I sounded rude. I have nothing against cleaning up. I especially appreciate your and Peter's work. But I simply don't like the idea of cleaning up files on schedule, and doing it so close to a release. It is almost inevitable that when lots of files are touched, errors are introduced. I saw (maybe incorrectly) a confirmation of my suspicions in this bug, hence the reaction. _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus&pgmarket=en-ca&RU=http%3a%2f%2fjoi…

3 2

Re: [Inkscape-devel] Remaining Tasks for 0.37 Release
by Robert Crosbie 06 Feb '04

06 Feb '04

Isn't the bonobo stuff not being compiled at all right now? To save the effort, perhaps that could be left out until someone figures out that portion of the code. Cheers, Rob. http://members.rogers.com/rcrosbie >From: Bryce Harrington <bryce@...1...> >To: <inkscape-devel(a)lists.sourceforge.net> >Subject: Re: [Inkscape-devel] Remaining Tasks for 0.37 Release >Date: Thu, 5 Feb 2004 09:48:46 -0800 (PST) > >Here's today's updated list: > > * Review all if 0 code: > * (DONE) Review #if 0 code in desktop*.cpp and svg-view.cpp files >[ted] > * Review #if 0 code in bonobo/ > * Review #if 0 code in sp-gradient.cpp, sp-root.cpp [tvon] > * Review #if 0 code in file.h, interface.cpp, geom.cpp, inkscape.cpp, >and > style.cpp [ishmal] > * Review #if 0 code in *-chemistry.cpp and seltrans.cpp [pjrm] > * Review #if 0 code in svg/ > * Review #if 0 code in display/ [mental] > * Review #if 0 code in xml/ > > * Convert all tabs into spaces in codebase > * dialogs folder [rejon] > * Rename all 'SPFooBar' routines to 'FooBar' and put into > namespaces [mental] > * Update coding-style.txt from the Coding_Style page in wiki > >Sounds like folks think we would be better suited to having humans do >the tab conversion rather than using a script? If so then we could >use more volunteers to help on that; pick a subdir or set of files and >let us know. If you know a trick to doing it with a script, do share! > >Bryce > >On Wed, 4 Feb 2004, Bryce Harrington wrote: > > When all of these are done, we will feature-freeze, and the focus will > > be on bug fixing. There are 10 bugs rated critical, that will need > > fixing. 5 of these do not yet have an owner so we need volunteers to > > take care of them. We also need to review the lower priority bugs to > > see if there are additional critical ones that will need fixing. > > > > Once the critical bugs are fixed, we will establish the stable branch >for > > 0.37 and the release team can get to work on packaging and creation of > > binaries. Once we have binaries for Windows, OSX, and a couple common > > linux distros, we can begin sending out announcements. :-) > > > > Bryce > > > >------------------------------------------------------- >The SF.Net email is sponsored by EclipseCon 2004 >Premiere Conference on Open Tools Development and Integration >See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. >http://www.eclipsecon.org/osdn >_______________________________________________ >Inkscape-devel mailing list >Inkscape-devel(a)lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/inkscape-devel _________________________________________________________________ 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…

2 1

code cleanup
by Jonathan Phillips 06 Feb '04

06 Feb '04

Hello all... I don't think that it will be possible to get our entire codebase up to to the coding style at the current pace, until next week. I think we are going to need to make a conscious decision to attack this untabbifying code systematically (I've only gotten through the dialogs folder in a couple of days!!!), or only untabbify the code for this release (faster), or put this off till next release (and try and get a release out soon--say by weekends end) What do you all think? I understand Bulia's concern about breaking things so close to release and I see how long this takes by hand...(a long time). Would it not be better to knock out the bugs and #if 0 and then put the rest till next release (bug hunt). I think we need to get a stable release up with bool. ops asap. Jon -- Jonathan Phillips <jon@...15...>

3 4