July 2005 - Inkscape Devel - Inkscape Mailman

Hi. xfig like export combined LaTeX postscript/ transparency ps export
by Marc Weber 02 Aug '05

02 Aug '05

Xfig has got one possibility to set a special flag on text which means that this text doesn't get exported on combined LaTeX ps but is written to the LaTeX file which means that you're able to also use LaTeX possibilies of typsetting mathematics and so on. Do you think it would be much effort to add this to inkscape, too? Because I *really* prefer inkscape over xfig :) inkscape could became the tool of choice making figures for LaTeX.. xfig is nice but lacks some functionality. The other thing is when exporting to ps inkscape currently just ignores transparency.. All you would have to do having two rectangles ------ -- : rect1 without ++ ---+++||| ++ : overlapping area ---+++||| || : rect2 without ++ |||||| rect2 is above rect1 would be splitting this rectangles into 3 and calculate the color of the + rectangle depending on the transparency of rect2 and color of rect1.. Then all 3 reactangles can be exported as it's done right now. And because the function Stroke to path is already provided (although I'm not sure how well it works using some advanced stroke style) it shouldn't be that hard to implement. What do you think? Marc

3 5

current CVS broken ?
by Adib Taraben 02 Aug '05

02 Aug '05

Hi, I have problem to open any dialogs besides the file-open and file-save. Inkscape closes immediately HTH, Adib. --- D:\projekte\inkscape\inkscape>gdb inkscape.exe GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-mingw32"... (gdb) run Starting program: D:\projekte\inkscape\inkscape/inkscape.exe gdb: do_initial_child_stuff: process 3856 gdb: kernel event for pid=3856 tid=2772 code=CREATE_PROCESS_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=EXCEPTION_DEBUG_EVENT) gdb: Target exception EXCEPTION_BREAKPOINT at 0x7c911230 gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=EXCEPTION_DEBUG_EVENT) gdb: Target exception EXCEPTION_ACCESS_VIOLATION at 0x004e8d99 Program received signal SIGSEGV, Segmentation fault. 0x004e8d99 in Inkscape::Verb::get_action () (gdb) bt #0 0x004e8d99 in Inkscape::Verb::get_action () #1 0x0043f8d3 in sp_ui_dialog_title_string () #2 0x005fbfc2 in sp_object_properties_dialog () #3 0x004f1f15 in sp_action_perform () #4 0x00af7a4a in g_cclosure_marshal_VOID__VOID () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #5 0x00ae34de in g_closure_invoke () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #6 0x00af6cff in signal_emit_unlocked_R () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #7 0x00af5434 in g_signal_emit_valist () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #8 0x00af5676 in g_signal_emit () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #9 0x015c69ff in gtk_button_clicked () from D:\projekte\inkscape\inkscape\libgtk-win32-2.0-0.dll #10 0x01728c04 in gtk_toggle_button_released () #11 0x00af7a4a in g_cclosure_marshal_VOID__VOID () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #12 0x00ae370b in g_type_class_meta_marshal () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #13 0x00ae34de in g_closure_invoke () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll ---Type <return> to continue, or q <return> to quit--- #14 0x00af5f6a in signal_emit_unlocked_R () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #15 0x00af5434 in g_signal_emit_valist () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #16 0x00af5676 in g_signal_emit () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #17 0x015c6987 in gtk_button_released () from D:\projekte\inkscape\inkscape\libgtk-win32-2.0-0.dll #18 0x015c7931 in gtk_button_button_release () from D:\projekte\inkscape\inkscape\libgtk-win32-2.0-0.dll #19 0x0168d771 in _gtk_marshal_BOOLEAN__BOXED () #20 0x00ae370b in g_type_class_meta_marshal () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #21 0x00ae34de in g_closure_invoke () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #22 0x00af6bbb in signal_emit_unlocked_R () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #23 0x00af5494 in g_signal_emit_valist () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #24 0x00af5676 in g_signal_emit () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #25 0x0177ab85 in gtk_widget_event_internal () #26 0x0177a7ff in gtk_widget_event () ---Type <return> to continue, or q <return> to quit--- #27 0x0168c028 in gtk_propagate_event () #28 0x0168afee in gtk_main_do_event () #29 0x0121aee9 in gdk_event_dispatch () from D:\projekte\inkscape\inkscape\libgdk-win32-2.0-0.dll #30 0x00978197 in g_main_dispatch () from D:\projekte\inkscape\inkscape\libglib-2.0-0.dll #31 0x00978c90 in g_main_context_dispatch () from D:\projekte\inkscape\inkscape\libglib-2.0-0.dll #32 0x00978f37 in g_main_context_iterate () from D:\projekte\inkscape\inkscape\libglib-2.0-0.dll #33 0x009793da in g_main_loop_run () from D:\projekte\inkscape\inkscape\libglib-2.0-0.dll #34 0x0168a91a in gtk_main () #35 0x01ac7543 in Gtk::Main::run () at main.cc:450 #36 0x00401c97 in sp_main_gui () #37 0x0042ebf8 in Inkscape::NSApplication::Application::run () #38 0x0040165e in main () (gdb)

4 8

The Bag Monkey Speaks
by MenTaLguY 02 Aug '05

02 Aug '05

Here's what I've got rolled up for 0.42.1 so far: > * src/dialogs/stroke-style.cpp: backport bulia's fix for stroke width > spin button [bug number??] > > * src/text-editing.cpp: backport bulia's fix for text crash > [bug 1247066] > > * src/libnrtype/Layout-TNG-OutIter.cpp: backport cyreve fix for > crash on delete in virgin flowtext [bug 1245842] > > * configure.ac: Kees fix for libgc detection w/dlopen [bug number??] Anyone got anything else for me? At the moment I'm thinking of aiming for 0.42.1 by early next weak. -mental

7 11

New binary portability problem identified
by Mike Hearn 01 Aug '05

01 Aug '05

Isn't Linux fun? The problems with g_option_error_quark people are seeing is because both the static RPM and the autopackage were built against static versions of GTKmm 2.6, which introduces a silent dependency on Glib 2.6 even if only 2.4 level features are used. The solution is to build the portable binaries against *mm 2.4 static libraries. Aaron, can you rebuild the autopackage against *mm 2.4 static libraries and push a -2 release of the package, so users on GTK+ 2.4 systems can use them again? thanks -mike

4 3

Scribus+Inkscape UI discussion
by cedric GEMY 01 Aug '05

01 Aug '05

Hi, i did last weeks a kind of analysis of Scribus UI (Open Source layout) (available at http://www.le-radar.com/?articles/scribusUI). As Inkscape and Scribus do goos job together i'm aiming to add some thoughts on their "integration". If you already used those softwares together, if you have things that you find very good or very in the way one or both of these apps are user interfaced, please let me know. Everyone's mind is welcome to improve user interfaces. Cedric

2 1

Google Summer of Code updates needed
by Bryce Harrington 01 Aug '05

01 Aug '05

Hi all! One of the key, oft-proven principles of Open Source development is "Release Early, Release Often". This is important because it makes it easier for other people to help you. I think for our Google Summer of Code students, it will be vital for their learning about Open Source processes to go through at least a couple releases, so they can see how this works in practice. I know it's a bit different from what we're trained in school to do; in school you have a due date and you (in theory) work on your assignment in secret from other students, and turn it in at the end. Open Source is very different; it's like you take your half-finished assignment to the clubhouse and trade answers with everyone else, and the more you cross-check with each other, the more likely everyone is to get a perfect score. ;-) Anyway, with the 0.42 release wrapping up, we're at a point where we're ready to integrate work from the Google Summer of Code students. Michael, David, Greg, and Matthew, can each of you report in on where you are in your work, how we can help you, and what you might be able to add to CVS within the next week or so? (Also, if you have any questions about getting access to or using CVS, please just ask and we'll get you set up.) Thanks, Bryce

7 7

RE: [Inkscape-devel] Google Summer of Code updates needed
by Yip, David W 01 Aug '05

01 Aug '05

I'll fill you guys in now :) There's a business center around here that has Internet access, so I'm using their facilities right now. I'm not sure if I can hook up my laptop and do a CVS commit from here, but I'll give it a try soon. Apologies if this mail is received as an HTML mess -- I have to use the Outlook web interface, and I'm not quite sure how to tell it to format as plain text...anyway. The modifications to configure.ac are complete, and compiling with/without the whiteboard code works fine, so that's all ready to go. On the subject of required libraries: the whiteboard code, as of yesterday, also depends on Boost v1.31.0+ for functor argument binding, smart pointers, and some miscellaneous utility classes. I think it's possible to just include the required Boost files with the Inkscape source distribution (they're all self-contained template classes as far as I can tell), but I'll leave it out for now until given the OK for inclusion. -- David ________________________________ From: inkscape-devel-admin(a)lists.sourceforge.net on behalf of Ted Gould Sent: Thu 7/28/2005 7:30 PM To: Bryce Harrington Cc: inkscape-devel(a)lists.sourceforge.net Subject: Re: [Inkscape-devel] Google Summer of Code updates needed Quick update because David is without Internet access for the next few days. He can fill in more when he gets back. He's about ready to commit but I asked him to make some changes to configure.ac so that it will detect loudmouth, and not compile the whiteboard stuff if it isn't available. He just needs to test that feature before committing. --Ted Bryce Harrington wrote: > Hi all! > > One of the key, oft-proven principles of Open Source development is > "Release Early, Release Often". This is important because it makes it > easier for other people to help you. > > I think for our Google Summer of Code students, it will be vital for > their learning about Open Source processes to go through at least a > couple releases, so they can see how this works in practice. > > I know it's a bit different from what we're trained in school to do; in > school you have a due date and you (in theory) work on your assignment > in secret from other students, and turn it in at the end. Open Source > is very different; it's like you take your half-finished assignment to > the clubhouse and trade answers with everyone else, and the more you > cross-check with each other, the more likely everyone is to get a > perfect score. ;-) > > Anyway, with the 0.42 release wrapping up, we're at a point where we're > ready to integrate work from the Google Summer of Code students. > > Michael, David, Greg, and Matthew, can each of you report in on where > you are in your work, how we can help you, and what you might be able to > add to CVS within the next week or so? > > (Also, if you have any questions about getting access to or using CVS, > please just ask and we'll get you set up.) > > Thanks, > Bryce > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO September > 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

5 6

Re: [Inkscape-user] Inkscape for windows
by Adib Taraben 01 Aug '05

01 Aug '05

Bryce Harrington schrieb: > On Fri, Jul 29, 2005 at 07:28:14AM -0500, aaron@...749... wrote: > >>Sadly, the only real way to find out what is needed to make an extension >>work is chasing it through the inx files. Browse to the >> >>As you figure out what various extensions require and confirm that they >>work, please add the details to the wiki. >>http://inkscape.org/cgi-bin/wiki.pl?GettingExtensionsWorking > > > Brett, Leopold, Aaron, Ted, Alexandre, and other participants in this > thread, I think it'd be worthwhile if we could get this page fleshed out > more. Could you guys take a look at that page and see how it could be > improved? > > Thanks, > Bryce > Could someone guide me to the page where all the parameter and options of that .inx file is described. Do we have an option to pipe not to STDIN/STDOUT but through temporary file ? Adib.

3 2

Ideas and complaints about win32 installer
by Taraben, Adib 31 Jul '05

31 Jul '05

Hi, I put a Wiki Page for new ideas and improvements. Everyone can edit this page. http://www.inkscape.org/cgi-bin/wiki.pl?Win32_Installer And yes I know we have a RFE and bugtracking tool yust want to have many eyes looking on the same page. Please everyone check this out and bring your ideas in. Gracie mille, Adib.

2 1

effects menu
by Alexandre Prokoudine 31 Jul '05

31 Jul '05

Hi, Before I go to bugtracker, I'd like to make sure that this is a real issue. Please take a look at www.lrn.ru/~avp/images/effects.png The first thing is easy to see: there is no particular order in menu items, or, to be more precise, the order seems to be random :) Would it be possible to at least alphabetically reorder menu items until extensions fraamework design (covering groups of effects etc.) is finished? The second thing is that "Grid" appears translated in contrary to other effects. I have no idea how this has happened. Is it an issue to be addressed? Best regards, Alexandre

5 9