0.43 status as at Oct12
SPDesktop now looks in good shape, which is good as that initially looked like the major show stopper. (Fixes thanks to rwst with some GC work from mental.)
Inkboard --------
A couple of people have reported either difficulty in connecting: bryce made a bug report, and sciboy today mentioned similar problems -- see 17:52 and previous at http://inkscape.gristle.org/2005-10-11.txt. sciboy says that it works if connecting to gristle.org, but that none of jabber.org, jabber.com, or jabber.org.au work. Later that day, Michael & sciboy did get a connection. Issues: - Lots of output on the terminal, should be turned off for general use before release. (If these messages are still useful to developers, then wrap the status messages in a macro or function that does nothing in the main version but that interested developers can "switch on".) I wouldn't want to release with these status messages: e.g. because they mask real errors that we'd want to be reported. - Michael & sciboy's session got out of sync somehow: at some point sciboy cleared everything but a star was left on michael's session. Not a show-stopper: this was the only thing we were aware of being out of sync. - Undo is global, i.e. it often undoes what the other person did rather than what the undoer did. This is a usability problem, but changing this is non-trivial, so I don't consider this a show-stopper. Btw, Michael was using MacOS X, so it seems that libloudmouth works acceptably there (as well as on Linux/Gnu). I gather Windows still doesn't work acceptably well, due to threading differences.
sciboy did experience a segfault later in his session with Michael (18:47 in the gristle log), though he didn't have a backtrace at the time. My feeling is that if the crash is specific to inkboard then we not consider it a show-stopper, but just make a note of it in the release notes.
Connectors ---------- Progress has been made. The bug tracker no longer has any connector bugs marked with priority >= 8. We still have some strange behaviour.
Michael comments: "The only known connector crash now is the one bryce reported, which I believe is fixed but he hasn't yet confirmed. I used to be able to reproduce it, but after fixing some other problems I now longer can. Once this sp_use_update fix is in that Bulia and I were just discussing (give me 20 minutes), then I think it's releasable. The other bugs are related to overlapping objects and are things I need to rework in libavoid after the release. The one remaining thing I'd like to look at if it's easy is the slowdown moving endpoints with the xml editor open."
menus.xml localization ---------------------- In principle fixed (there's one huge menus-skeleton.h string to be translated), but in practice none of the translations has been updated. It would be nice if we went back to smaller strings to facilitate keeping the translations up-to-date (and so that we could re-use the existing translations). Personally I'm still inclined to treat this as a show-stopper, particularly as it looks easy enough to fix.
Other ----- Sorting bug tracker items (http://sourceforge.net/tracker/?group_id=93438&atid=604306) by decreasing priority shows the following marked at priority 9:
- a text-anchor regression (cyreve, can you comment?); - the corrupted about.svg problem I posted on just now; - a bunch of windows-specific bugs that I haven't looked at: I'll leave these for our Windows devs to decide on; - "unexpected printout size", where we're wrongly converting to postscript at 90px/inch or 72px/inch rather than 120px/inch. Personally I wouldn't let this one hold up the release.
pjrm.
Here's a summary with my comments and some additional items:
Inkboard
- Lots of output on the terminal, should be turned off for general use before release.
I think at least this one must be fixed for the release by all means; for the rest I'd like to hear from David.
Connectors
Waiting for Michael's fix of sp_use_update and Bryce's crash fix confirmation
menus.xml localization
Does that mean all menus are not translated? If so it's obviously a showstopper. Preferable to fix it with maximum reusing of old translations.
- a text-anchor regression (cyreve, can you comment?);
http://sourceforge.net/tracker/index.php?func=detail&aid=1314383&gro... I'd consider this a showstopper because it renders some old files wrong.
- the corrupted about.svg problem I posted on just now;
Easy to fix.
- "unexpected printout size", where we're wrongly converting to postscript at 90px/inch or 72px/inch rather than 120px/inch. Personally I wouldn't let this one hold up the release.
Unless it's new (which I don't think it is) it's not a stopper.
Additional items from me:
- We need to reenable gtk-wimp on Windows. Bob said he'd do this. It will likely fix this bug: http://sourceforge.net/tracker/index.php?func=detail&aid=1324246&gro...
- There's a patch for the infamous "Dialogs on top not working on windows" bug. It's a patch against GTK, and I'd very much like to see it in our prereleases, and if it works, in 0.43. It's a major bugfix. Again, Bob promised to include it in his GTK libs package. The patch is here: http://mail.gnome.org/archives/gtk-devel-list/2005-September/msg00007.html
- We also need to make sure the Windows build contains the new installer from Adib. I assume that's the case, but would like to mention it.
Once (most of) the above items are cleared, I think we can do a pre0. Meanwhile:
- I still see no screenshots for 0.43. I remember several people volunteered?
- The patch tracker has several tutorial translations - Scislac agreed to take care of them.
- Also, Scislac was going to update the Calligraphy tutorial.
- The Release notes have a few unfinished items such as the status of the two other SoC projects (do we mention them at all? anyone in the know?) and Ted/JonCruz placeholders
- There's a patch for a locale bug in Blur Edge. I think we need to commit that.
- We really need as many volunteers as possible to go through the bug list and test/comment/prioritize. If you think any bug is a showstopper, please shout on this thread.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
One more thing: I remember someone volunteered to create static RPMs, what is the status of that (if I remember correctly, of course)?
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
On Wednesday 12 October 2005 08:39, bulia byak wrote:
One more thing: I remember someone volunteered to create static RPMs, what is the status of that (if I remember correctly, of course)?
I did. I created a few weeks ago static RPMs for release 0.42.2. Just one person complained on SF about problems on FC4 but hasn't reported back yet.
I've got some difficulties compiling CVS since I've upgraded to SuSE 10.0 but I'm working on solving this as soon as possible. Ralph is helping me out on this.
On 10/12/05, Jean-Francois Lemaire <jflemaire@...621...> wrote:
I did. I created a few weeks ago static RPMs for release 0.42.2. Just one person complained on SF about problems on FC4 but hasn't reported back yet.
I've got some difficulties compiling CVS since I've upgraded to SuSE 10.0 but I'm working on solving this as soon as possible. Ralph is helping me out on this.
Cool, thanks. It will be perfect to have them for pre0 when it's out (hopefully soon).
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
- a text-anchor regression (cyreve, can you comment?);
http://sourceforge.net/tracker/index.php?func=detail&aid=1314383&gro... I'd consider this a showstopper because it renders some old files wrong.
I was looking for a solution that I didn't consider inelegant, but I guess I'm not going to find one. Ugly fix checked in.
Richard.
bulia byak wrote:
Here's a summary with my comments and some additional items:
menus.xml localization
Does that mean all menus are not translated? If so it's obviously a showstopper. Preferable to fix it with maximum reusing of old translations.
Related... I don't know if my win32 builds AND my Ubuntu builds are tainted or what, but, even with no menus.xml in my profile dir, it still generates a new one as soon as Inkscape is launched. Bob, could you make a win32 build so I can double check that it's not my sandboxes that are goofy? (I could be mistaken, but I thought that's what Ted's patch from a month or so back was to fix)
- We need to reenable gtk-wimp on Windows. Bob said he'd do this. It
will likely fix this bug: http://sourceforge.net/tracker/index.php?func=detail&aid=1324246&gro...
He committed an updated makefile earlier today, and it now does wimp by default for me.
- There's a patch for the infamous "Dialogs on top not working on
windows" bug. It's a patch against GTK, and I'd very much like to see it in our prereleases, and if it works, in 0.43. It's a major bugfix. Again, Bob promised to include it in his GTK libs package. The patch is here: http://mail.gnome.org/archives/gtk-devel-list/2005-September/msg00007.html
For real? This is definitely a must-have if it works.
- I still see no screenshots for 0.43. I remember several people volunteered?
I will do a couple tomorrow... one for node editing (showing the purdy new cursor dragging a curve) and I'll figure another one out.
- The patch tracker has several tutorial translations - Scislac agreed
to take care of them.
I didn't get a chance to check to see if that classpath was the issue... my guess is it's something else that is borking the "make-all" since "make-svg" works fine. I will do what I can tonight, and will hopefully be able to commit tomorrow. If not, I will have time on Sunday to get it straightened out.
Also, after this release, I would like to go through the tutorials and remove contractions. I've done this in the calligraphy tutorial and will post a diff to the list to help the translators know what changed (as I will do for the other tuts down the road).
- Also, Scislac was going to update the Calligraphy tutorial.
Content/text is updated, I also want to add just a couple quick scribbles with the tablet pressure/angle stuff, but I will need to do that tomorrow at the office on win32 since Xorg doesn't release the events. I will also double check release notes to make sure it is noted that the Xorg problem exists.
-Josh
On 10/12/05, Joshua A. Andler <joshua@...533...> wrote:
He committed an updated makefile earlier today, and it now does wimp by default for me.
Great, thanks Bob, I'll test it
- I still see no screenshots for 0.43. I remember several people volunteered?
I will do a couple tomorrow... one for node editing (showing the purdy new cursor dragging a curve) and I'll figure another one out.
Thanks. It would be ideal to demonstrate curve dragging "in action", that is, show several "frames" of a curve segment as it is drawn, using a pale color. Can you do that?
- The patch tracker has several tutorial translations - Scislac agreed
to take care of them.
I didn't get a chance to check to see if that classpath was the issue... my guess is it's something else that is borking the "make-all" since "make-svg" works fine. I will do what I can tonight, and will hopefully be able to commit tomorrow. If not, I will have time on Sunday to get it straightened out.
Well, in any event, you can always just run make-svg and make-html on all tutorials one by one :)
Also, after this release, I would like to go through the tutorials and remove contractions. I've done this in the calligraphy tutorial and will post a diff to the list to help the translators know what changed (as I will do for the other tuts down the road).
Contractions?
Content/text is updated, I also want to add just a couple quick scribbles with the tablet pressure/angle stuff, but I will need to do that tomorrow at the office on win32 since Xorg doesn't release the events. I will also double check release notes to make sure it is noted that the Xorg problem exists.
Good idea, thanks.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
bulia byak wrote:
On 10/12/05, Joshua A. Andler <joshua@...533...> wrote:
- I still see no screenshots for 0.43. I remember several people volunteered?
I will do a couple tomorrow... one for node editing (showing the purdy new cursor dragging a curve) and I'll figure another one out.
Thanks. It would be ideal to demonstrate curve dragging "in action", that is, show several "frames" of a curve segment as it is drawn, using a pale color. Can you do that?
Fake onionskin effect? You got it!
- The patch tracker has several tutorial translations - Scislac agreed
to take care of them.
I didn't get a chance to check to see if that classpath was the issue... my guess is it's something else that is borking the "make-all" since "make-svg" works fine. I will do what I can tonight, and will hopefully be able to commit tomorrow. If not, I will have time on Sunday to get it straightened out.
Well, in any event, you can always just run make-svg and make-html on all tutorials one by one :)
Good point. ;)
Also, after this release, I would like to go through the tutorials and remove contractions. I've done this in the calligraphy tutorial and will post a diff to the list to help the translators know what changed (as I will do for the other tuts down the road).
Contractions?
don't, won't, can't, etc... I was told that it's (darn... it is) easier to translate if words aren't (argh! are not) contracted. Also, it is the policy of many English nuts I know to rant about contractions not being proper (my mother who co-wrote a College level English book being one of them). You would think I would have picked up some skills from her =P. Oh, and for note, she has agreed to review documentation for us down the line when it's a little more complete.
-Josh
Josh:
Related... I don't know if my win32 builds AND my Ubuntu builds are tainted or what, but, even with no menus.xml in my profile dir, it still generates a new one as soon as Inkscape is launched. Bob,
The same here, I never saw a version that didn't write menus.xml. I thought it was agreed to only read the file if it exists.
ralf
Josh:
Related... I don't know if my win32 builds AND my Ubuntu builds are tainted or what, but, even with no menus.xml in my profile dir, it still generates a new one as soon as Inkscape is launched. Bob,
The same here, I never saw a version that didn't write menus.xml. I thought it was agreed to only read the file if it exists.
And it would be irrelevant for the new (=old) problem with i18n, as I just found out: making menus.xml unreadable/-writable will not change the borken behaviour that, under any non-en language, some menu entries will not get translations.
My "german" menu looks like:
Datei Edit Layer ..... Help -------------------------------------- New .... ... .... ..... Öffnen Show/Hide Tutorials Open Recent Zurücksetzen
IOW, every top entry except the first, and those four entries that have submenus, do not get translated.
This was already borken some months ago, and is a true showstopper.
ralf
On Thu, 2005-10-13 at 09:49 +0200, Ralf Stephan wrote:
Josh:
Related... I don't know if my win32 builds AND my Ubuntu builds are tainted or what, but, even with no menus.xml in my profile dir, it still generates a new one as soon as Inkscape is launched. Bob,
The same here, I never saw a version that didn't write menus.xml. I thought it was agreed to only read the file if it exists.
I think that it is now fixed in CVS. Sorry about that.
--Ted
On Wed, Oct 12, 2005 at 02:01:40AM -0300, bulia byak wrote:
Here's a summary with my comments and some additional items:
Connectors
Waiting for Michael's fix of sp_use_update and Bryce's crash fix confirmation
I doublechecked again last night and the test case still leads to a crash. I gave some additional directions so hopefully it can be tracked down. I could do some deeper investigation this weekend if needed.
Once (most of) the above items are cleared, I think we can do a pre0. Meanwhile:
I still see no screenshots for 0.43. I remember several people volunteered?
The patch tracker has several tutorial translations - Scislac agreed
to take care of them.
Also, Scislac was going to update the Calligraphy tutorial.
The Release notes have a few unfinished items such as the status of
the two other SoC projects (do we mention them at all? anyone in the know?) and Ted/JonCruz placeholders
The clipart browser technically is a separate application, so probably doesn't need mention. The dxf2svg converter may not be sophisticated enough to advertise as a feature yet.
- We really need as many volunteers as possible to go through the bug
list and test/comment/prioritize. If you think any bug is a showstopper, please shout on this thread.
Bryce
Over the last few days, message numbers seem to have dropped dramatically. Are people beavering away without reporting or is my system having a bad hair week? Erik
On Sat, 29 Oct 2005 21:38:19 +1000 "Erik" <kaver@...68...> wrote:
Over the last few days, message numbers seem to have dropped dramatically. Are people beavering away without reporting or is my system having a bad hair week? Erik
Hello, Erik :) Might be a bad hair week :) I sent an email a few days ago (actually a couple, but only the last one is relevant now) I will update and attempt to recompile Inkscape from CVS to make sure that nothing has been fixed since earlier this morning.
Steven P. Ulrick
On Sat, Oct 29, 2005 at 09:38:19PM +1000, Erik wrote:
Over the last few days, message numbers seem to have dropped dramatically. Are people beavering away without reporting or is my system having a bad hair week? Erik
It's very normal for mailing lists to ebb and flow; we can expect the Inkscape list to go from an overwhelming number of posts you can barely keep up with, to a slow trickle. Most lists I've been on are like this, so it's nothing to worry about.
Bryce
On 10/13/05, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
On 10/12/05, bulia byak <buliabyak@...400...> wrote:
- I still see no screenshots for 0.43. I remember several people volunteered?
What's your final decision on my screenshots of new connector tool functionality?
Sorry if I forgot or missed something... I think we agreed to make a combined screenshot of your two diagrams with a blurb (text) describing how you used the connector tool. Did you do that?
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
On Wed, 2005-10-12 at 02:01 -0300, bulia byak wrote:
menus.xml localization
Does that mean all menus are not translated? If so it's obviously a showstopper. Preferable to fix it with maximum reusing of old translations.
How was last night's check-in? Does that use all the right translations? It seems to for me.
--Ted
You wrote
How was last night's check-in? Does that use all the right translations? It seems to for me.
I don't have an idea how you can say that. It is so easy to do
$ export LANGUAGE=de or ru or whatever has a complete translation,
and see that all but the first top entries, and four subentries (those with submenus) are NOT translated.
There is also a fresh bug report to which you might want to refer.
ralf
Ralf Stephan wrote:
You wrote
How was last night's check-in? Does that use all the right translations? It seems to for me.
I don't have an idea how you can say that. It is so easy to do
$ export LANGUAGE=de or ru or whatever has a complete translation,
and see that all but the first top entries, and four subentries (those with submenus) are NOT translated.
Well, it may surprise you, but I don't track the translation status of all the translations. Any omitions that I saw I assumed were related to the lack of a translation, but I don't believe that I tried de or ru. But, I'd also say that you'd need to have updated your po files because most of the translations got marked unused, and so they weren't in the gmo files. For the translations that I looked at, after an update, all the appropriate strings were available for translation in the .po file. It is so easy to do an "make update-po".
Please update your po files and try again, I'll verify the same tonight at home on my build.
--Ted
You wrote
Well, it may surprise you, but I don't track the translation status of all the translations. Any omitions that I saw I assumed were related to the lack of a translation, but I don't believe that I tried de or ru. But, I'd also say that you'd need to have updated your po files because most of the translations got marked unused, and so they weren't in the gmo files. For the translations that I looked at, after an update, all the appropriate strings were available for translation in the .po file. It is so easy to do an "make update-po".
OK. I'm learning something new every day, for example that what's marked by CVS as up-to-date, isn't always.
Thanks. I'll invalidate the bug report.
ralf
On Wed, 12 Oct 2005, bulia byak wrote:
Connectors
Waiting for Michael's fix of sp_use_update and Bryce's crash fix confirmation
Firstly, Bryce still gets this crash but I don't see it on my Mac or any of the Linux machines I've just tried CVS HEAD on. I'd be grateful if a some other people could try to reproduce the crash, and provide more information, e.g., a backtrace.
The bug report is: https://sourceforge.net/tracker/index.php?func=detail&aid=1303488&gr... Bryce's initial and then most recent comment give the steps to reproduce.
Secondly, it turns out sp_use_update wasn't the problem... For those just joining us, the connector tool has a problem with clones. This is because it responds to the transformed signal of a clone Use to update connectors attached to it. The connector code calls sp_item_invoke_bbox which returns the wrong bbox for the Use object. I originally thought this was because the bbox code used information from the object's internal information that was not yet updated (by the sp_*_update functions).
It turns out that the actual problem is that the Use object keeps a copy of the original object, and this copy is not brought in sync with the original moved object till after the transformed signal has been handled. The bbox code uses this copy of the original object so returns the object's bbox as it was before the move.
There is a trivial fix, but it may not be completely safe. So, after discussing it with Bulia and mental on Jabber, we have decided to wait till after the release to apply it.
Cheers, Michael
bulia byak schrieb:
Here's a summary with my comments and some additional items:
...
- We also need to make sure the Windows build contains the new
installer from Adib. I assume that's the case, but would like to mention it.
... Hi, I collected the feedbacks I got on http://wiki.inkscape.org/cgi-bin/wiki.pl?Win32_Installer How the Installer will look pls look at http://www.geocities.com/theAdib/
there are two ideas that I can not solve or even think HOW I can solve this: - assign also other fileextension to inkscape ps, pdf, ai - that inkscape supports via extensions because I do not know how to extract the dependencies from the inx files and how to detect if those prorams are installed. - resolv the dependencies for the different extensions should install ghostscript, ... again ideally I should parse the inx files and know how/from where get the installer
However there was no "don't do it at all" response.
If nobody complains I will go ahead and commit the code into the CVS.
BTW Are there nightly builds of a win32-installer ?
HTH,
Adib.
On 10/15/05, Adib Taraben <taraben.a@...50...> wrote:
If nobody complains I will go ahead and commit the code into the CVS.
I think it's time to do it. It's risky but we have all our prereleases ahead for testing it.
BTW Are there nightly builds of a win32-installer ?
Not that I know of, only zips. Would be useful to have them.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
Hello.
On 10/15/05, Adib Taraben <taraben.a@...50...> wrote: [...]
BTW Are there nightly builds of a win32-installer ?
Yes. http://mrchapp2.homelinux.net/~inkscape/
The .exe files are installers.
Greetings!
Daniel Díaz yosoy@...31...
Here's an update of the tasks list. Not much progress. Peter or Jon, I think you should be more active in maintaining it and pushing the remaining tasks!
Inkboard
- Lots of output on the terminal, should be turned off for general use before release.
I think at least this one must be fixed for the release by all means; for the rest I'd like to hear from David.
David said he fixed this one?
Connectors
Waiting for Michael's fix of sp_use_update and Bryce's crash fix confirmation
I think Michael has fixed everything that can be safely fixed in this release.
menus.xml localization
Does that mean all menus are not translated? If so it's obviously a showstopper. Preferable to fix it with maximum reusing of old translations.
Last I heard this is fixed. Anyone in the know?
- a text-anchor regression (cyreve, can you comment?);
http://sourceforge.net/tracker/index.php?func=detail&aid=1314383&gro... I'd consider this a showstopper because it renders some old files wrong.
Fixed
- the corrupted about.svg problem I posted on just now;
Easy to fix.
Is that fixed?
- "unexpected printout size", where we're wrongly converting to postscript at 90px/inch or 72px/inch rather than 120px/inch. Personally I wouldn't let this one hold up the release.
Unless it's new (which I don't think it is) it's not a stopper.
Assuming not new, postponed.
- We need to reenable gtk-wimp on Windows. Bob said he'd do this.
Reported done, though I haven't yet tested it. But this bug still has problems: http://sourceforge.net/tracker/index.php?func=detail&aid=1324246&gro... Bob, can you please have a look?
- There's a patch for the infamous "Dialogs on top not working on
windows" bug. It's a patch against GTK, and I'd very much like to see it in our prereleases, and if it works, in 0.43. It's a major bugfix. Again, Bob promised to include it in his GTK libs package. The patch is here: http://mail.gnome.org/archives/gtk-devel-list/2005-September/msg00007.html
Bob/Scislac, what is the status of this?
- We also need to make sure the Windows build contains the new
installer from Adib. I assume that's the case, but would like to mention it.
Committed yesterday.
Once (most of) the above items are cleared, I think we can do a pre0.
I think we can do pre0 now. Peter, Jon: could you please do this? If necessary ask Ted who (I think) did it for the last release.
- I still see no screenshots for 0.43. I remember several people volunteered?
Again, several people responded to this, but then I didn't see any files.
- The patch tracker has several tutorial translations - Scislac agreed
to take care of them.
Not closed still
- Also, Scislac was going to update the Calligraphy tutorial.
Not closed still
- The Release notes have a few unfinished items such as the status of
the two other SoC projects (do we mention them at all? anyone in the know?) and Ted/JonCruz placeholders
No one has since updated the rel notes except me
- There's a patch for a locale bug in Blur Edge. I think we need to commit that.
Not committed.
Another item: http://sourceforge.net/tracker/index.php?func=detail&aid=1329025&gro... A compilation patch for FreeBSD.
Let's all be more active, please. This release needs to be pushed out of the door ASAP. I have a lot of new code I want to commit after the freeze.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
bulia byak wrote:
- There's a patch for the infamous "Dialogs on top not working on
windows" bug. It's a patch against GTK, and I'd very much like to see it in our prereleases, and if it works, in 0.43. It's a major bugfix. Again, Bob promised to include it in his GTK libs package. The patch is here: http://mail.gnome.org/archives/gtk-devel-list/2005-September/msg00007.html
Bob/Scislac, what is the status of this?
The patch has thus far not made it into GTK yet as of 2.8.6. Unfortunately we don't know what the status of the patch is either.
- We also need to make sure the Windows build contains the new
installer from Adib. I assume that's the case, but would like to mention it.
Committed yesterday.
I noticed in the screenshots Adib linked earlier that it had the default NSIS logo in the installer. Could we get our logo in there instead?
- I still see no screenshots for 0.43. I remember several people volunteered?
Again, several people responded to this, but then I didn't see any files.
I was down feeling ill for a few days so haven't been working on this stuff. I will do that curve dragging screen and another node editing related screen showing some nifty tricks today.
- The patch tracker has several tutorial translations - Scislac agreed
to take care of them.
Not closed still
I will see what I can do today, but, if I don't get these up tonight I should have time tomorrow night to get these in.
- Also, Scislac was going to update the Calligraphy tutorial.
Not closed still
I brought my tablet to work, so it will be finished today (as the last thing I needed to update was a couple example pics for pressure and tilt).
Let's all be more active, please. This release needs to be pushed out of the door ASAP. I have a lot of new code I want to commit after the freeze.
Agreed. I will get in gear to try and bust out all of my stuff today. And Bulia, you piqued my interest! What kind of new goodness is in your sandbox?
And just curious, does anyone know what the current status of the clippath stuff is? To my non-guru eyes (both as far as C/C++ AND the codebase go) it looks fairly complete to me and it appears that it even has the "set" and "release" functions already set up. Unfortunately when I tried to willy-nilly add verbs to hook em up it barfed about not being declared in that scope during compilation. I only ask about this because I'm using clippaths quite a bit lately (and have a few projects on hold because editing the elements one by one would be a few hours by itself) and was hopeful I could do it faster by hooking it up in the GUI.
-Josh
On 10/18/05, Joshua A. Andler <joshua@...533...> wrote: http://mail.gnome.org/archives/gtk-devel-list/2005-September/msg00007.html
Bob/Scislac, what is the status of this?
The patch has thus far not made it into GTK yet as of 2.8.6. Unfortunately we don't know what the status of the patch is either.
But didn't Bob add it to our own GTK?
- We also need to make sure the Windows build contains the new
installer from Adib. I assume that's the case, but would like to mention it.
Committed yesterday.
I noticed in the screenshots Adib linked earlier that it had the default NSIS logo in the installer. Could we get our logo in there instead?
And by the way, after this is done, why don't we use some of the installer screenshots in the main gallery too.
- Also, Scislac was going to update the Calligraphy tutorial.
Not closed still
I brought my tablet to work, so it will be finished today (as the last thing I needed to update was a couple example pics for pressure and tilt).
Popolon had some nice examples, he was going to submit a screenshot but I think you can also borrow some tutorial examples from him.
And just curious, does anyone know what the current status of the clippath stuff is? To my non-guru eyes (both as far as C/C++ AND the codebase go) it looks fairly complete to me and it appears that it even has the "set" and "release" functions already set up. Unfortunately when I tried to willy-nilly add verbs to hook em up it barfed about not being declared in that scope during compilation. I only ask about this because I'm using clippaths quite a bit lately (and have a few projects on hold because editing the elements one by one would be a few hours by itself) and was hopeful I could do it faster by hooking it up in the GUI.
I just never got around to this, but this should be easy. Start by writing sp_selection_clip and sp_selection_unclip verbs, taking for example *_tile (in selection-chemistry) or the boolean functions (in splivarot) as templates. Basically all you need to do is to copy the clipping path to a new <clipPath> in defs and add/remove the clip-path property of the clipped object. Look it up, there are many examples of similar repr manipulations in the codebase. Ping me if you have any questions.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
menus.xml localization
Does that mean all menus are not translated? If so it's obviously a showstopper. Preferable to fix it with maximum reusing of old translations.
Last I heard this is fixed. Anyone in the know?
I had filed two bug reports on that but Ted handled the first at once, and the second was invalid, so this is fine now.
ralf
menus.xml localization
In principle fixed (there's one huge menus-skeleton.h string to be translated), but in practice none of the translations has been updated.
The untranslated string also only shows in es.po, eu.po, and ru.po, for some reasons, and it gives an error "Bad markup in translations". Incidentally, wouldn't it read 'separator' instead of 'seperator'?
This all with cvs from today.
ralf
On 10/12/05, Ralf Stephan <ralf@...748...> wrote:
...
The untranslated string also only shows in es.po, eu.po, and ru.po, for some reasons, and it gives an error "Bad markup in translations". Incidentally, wouldn't it read 'separator' instead of 'seperator'?
This all with cvs from today.
Apologies if I am barging in, but I am getting a compilation error about "directives may not be used inside a macro argument" which might be undefined behaviour. Should I try to find a compiler which supports this as an extension, or am I talking nonsense?
Should the string be constructed outside the 'call' to the N_ macro?
Is there a C++ (inline function) solution to the problems solved by _() and N_() macros?
It is usually 'separator' but both spellings seem to be accepted by computer scientists.
Ben
Peter Moulder wrote:
Inkboard
I'm thinking we leave this as compile-time option for this release, mostly because of the Win32 issues. I think most of the server issues are issues with rate limiting on the servers. I've started working on the JEP for the protocol, so hopefully we can get that out so servers can be "Inkboard-aware" in the future.
menus.xml localization
Okay, I'll try to look into this more. I thought it was all happy-happy :)
--Ted
Quoting Peter Moulder <Peter.Moulder@...38...>:
SPDesktop now looks in good shape, which is good as that initially looked like the major show stopper. (Fixes thanks to rwst with some GC work from mental.)
The last build I checked was still doubly-registering desktops. Has that been addressed recently?
- the corrupted about.svg problem I posted on just now;
I want to get a chance to rewrite the text for the about dialog as well. The current "disclaimer" style blurb is kind of off-putting, and doesn't (content-wise) fit the picture either.
-mental
mental:
Quoting Peter Moulder <Peter.Moulder@...38...>:
SPDesktop now looks in good shape, which is good as that initially looked like the major show stopper. (Fixes thanks to rwst with some GC work from mental.)
The last build I checked was still doubly-registering desktops. Has that been addressed recently?
Please describe how you come to the conclusion, or file a bug report.
Also, do you consider it as showstopper?
ralf
Peter Moulder wrote:
Later that day, Michael & sciboy did get a connection. Issues:
- Lots of output on the terminal, should be turned off for general use before release.
Whoops...I thought I killed all of the useless output in CVS. I'll have to go back and check that.
- Michael & sciboy's session got out of sync somehow: at some point sciboy cleared everything but a star was left on michael's session. Not a show-stopper: this was the only thing we were aware of being out of sync.
- Undo is global, i.e. it often undoes what the other person did rather than what the undoer did. This is a usability problem, but changing this is non-trivial, so I don't consider this a show-stopper.
The release notes contain notes to the effect that problems like this may occur. Future releases will contain a much improved architecture for handling concurrent modification, undo, and such. The model I'm currently studying for this is the Palimpsest model (http://cs-people.bu.edu/dgd/thesis/original_paper.html is a shortened version of the author's original dissertation).
Btw, Michael was using MacOS X, so it seems that libloudmouth works acceptably there (as well as on Linux/Gnu). I gather Windows still doesn't work acceptably well, due to threading differences.
Oh, cool :)
sciboy did experience a segfault later in his session with Michael (18:47 in the gristle log), though he didn't have a backtrace at the time. My feeling is that if the crash is specific to inkboard then we not consider it a show-stopper, but just make a note of it in the release notes.
Sure thing.
-- David
participants (19)
-
unknown＠example.com -
Adib Taraben -
Alexandre Prokoudine -
Ben Fowler -
Bryce Harrington -
bulia byak -
Colin Marquardt -
Daniel Díaz -
David Yip -
Erik -
Jean-Francois Lemaire -
Joshua A. Andler -
MenTaLguY -
Michael Wybrow -
Peter Moulder -
Ralf Stephan -
Richard Hughes -
Steven P. Ulrick -
Ted Gould