- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] Toolbar Icons in Windows
by joel＠...1709... 02 Jul '07

02 Jul '07

Those icons look great! I can't wait till they're in. ---------------------------------------- From: "Alexandre Prokoudine" <alexandre.prokoudine@...400...> Sent: 01 July 2007 14:24 To: inkscape-devel <inkscape-devel(a)lists.sourceforge.net> Subject: Re: [Inkscape-devel] Toolbar Icons in Windows On 7/2/07, joel wrote: > These Ubuntu provided icons look really good (are they Tango?). They are in Tango style, but not Tango. The theme is called Human. > or for that matter any icons which follow the Tango style guidlines? Yes, we have a tango styled icon set in works. Have a look at http://gnomelook.org/content/show.php/Tangofied+inkscape+icons+set?content=… if you want to know more :) Alexandre ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

1 0

Toolbar Icons in Windows
by joel＠...1709... 01 Jul '07

01 Jul '07

I have a question about standard toolbar icons. I notice that when I run inkscape in Gnome in Ubuntu, the system provides some of the standard icons in toolbar for things like Open, Save, Print, Cut, Copy and Paste. These Ubuntu provided icons look really good (are they Tango?). However, in the Windows version of Inkscape (or is it GTK+ ?), the standard icons just look a little dreary, and washed out. Is there any chance that the Windows users could have brighter icons which follow the Windows style guidelines? - like the Silk Icons (http://www.famfamfam.com/lab/icons/silk/), or for that matter any icons which follow the Tango style guidlines? Sorry to keep posting comments about such seemingly trival details - I'm just stickler for details sometimes.

3 2

new API: XML::Subtree
by MenTaLguY 01 Jul '07

01 Jul '07

I've introduced a new API for monitoring changes to subtrees of a given XML tree. It extends the existing change notification API for XML::Node by providing an attachment point for NodeObservers to observe changes to an entire subtree in the document, instead of just a single node. The main difference is that rather than registering a NodeObserver with a Node via Node::addObserver, you create a Subtree object for that node and add the observer to it instead. XML::Node *some_node; XML::NodeObserver &observer; ... XML::Subtree *subtree = new XML::Subtree(*some_node); subtree->addObserver(observer); ... subtree->removeObserver(observer); delete subtree; // XML::Subtree is manually manged I'm going to do a more efficient implementation of XML::Subtree eventually, but that shouldn't alter the API given here. -mental

1 0

Updated Wiki Eclipse Tutorial
by joel＠...1709... 01 Jul '07

01 Jul '07

Now that Eclipse Europa is out, I've updated the Eclipse Pages (I believe correctly) to reflect the changes made in this release.

1 0

Tutorial translations: switching to xml2po
by Colin Marquardt 01 Jul '07

01 Jul '07

Hi, is there anyone who objects using xml2po for the tutorial translations? See http://wiki.inkscape.org/wiki/index.php/DocumentationTranslation for the process. With xml2po, translators would get regular po files to translate, with all the positive effects (no manual looking for string changes; more dedicated tools than for Docbook; familiarity of amny translators with the format; translator credits for free (even though we don't pull them yet for the About box); strings from included images are in the same file; the Gnome people are using it; and probably some more). I am using xml2po for the German translation since pre-0.45, and it worked quite well so far. I have started automating the conversion process to HTML/SVG (to the then intermediate Docbook XML) in SVN. So if there are no valid objections overriding the plusses, I will soon start converting all translated Docbook XML files to the po format. Please submit any translated XML files that are not yet in SVN. I think now is a good time to tackle that process, considering that 0.46 is probably a while but not too far away, and there are quite some efforts going into tutorials recently (thanks Ryan :). Cheers Colin PS: I'm cmarqu on IRC.

1 0

Effects on Win32 (and side note)
by Joshua A. Andler 01 Jul '07

01 Jul '07

Okay... first off, I nuked my svn checkout, xmingw, and my gtklibs... Then brought everything back up-to-date and clean at that. Cross-compiled for win32 and fired up inkscape on the win32 box. The error I reported yesterday persisted (about not finding python25.dll). I manually moved the dll file from the main inkscape dir into the python subdirectory where python.exe resides. This solved problem of not being able to find the dll. However, effects still do not work. When I try to run effects (interpolate is my example here) I now get output stating: "python: can't open file 'share\extensions\interp.py': [Errno 2] No such file or directory" For the sake of trying to find a workaround (like the dll), I copied the "share\extensions" directory structure with the contents into that python dir as well (hey it worked for the dll). Unfortunately, this did not fix it. It seems like this may be more related to our library upgrade and new python than the changes Ted made. I really want to make sure that people will still be able to use effects on win32, and it seems like the sooner we can know if there's a problem, the better. Anyone else building for/on win32 having a different experience? Again, note that I'm cross-compiling, not compiling natively. Side note: Bob, the gtkrc file copied to "inkscape\etc\gtk-2.0" has the correct change I suggested. But, the gtkrc file that is in "inkscape\share\themes\MS-Windows\gtk-2.0" does not have the change and it is the one inkscape actually uses. -Josh P.S. Ted, you're getting CC'd because I want you to know that I plan on testing your changes on win32 asap... and also to know that I will bug you if your changes don't work on win32. ;)

6 17

Getting the GdkWindow in which a verb was invoked
by Joel Holdsworth 28 Jun '07

28 Jun '07

Hi again, I'm currently working on a patch to add support for native file dialogs for windows users. It's worked out pretty well, and I'm almost finished. I have one slight problem though: parent windows. In the GTK version, sp_file_open_dialog (in file.cpp) is called from inside FileVerb::Perform in verbs.cpp. But how is it possible to get the GdkWindow object of the windows in which the verb was invoked? If I have this I can add it as an extra parameter to sp_file_open_dialog, to enable both the GTK, and Win32 file dialogs to be correctly set as child windows of the document's window. Any suggestions? Joel Holdsworth

5 7

Object Sets
by Jeff Rose 28 Jun '07

28 Jun '07

Hi Inkscapers, I was just talking with a friend while he is working on some diagrams in inkscape, and he wants to be able to have items in multiple groups. (This is a network diagram, so for example it would be nice to have a set of all nodes, to be able to change color and style, but then also put various subnets of nodes into their own groups so they can be transformed as a unit.) Looking into it a bit it seems that this is really a limitation of the way svg handles groups, and since both groups and layers in inkscape are implemented with svg groups I guess it's not possible to use a set oriented approach like this? Any ideas why groups are limited in this way within the svg spec? I can imagine a number of situations in which it would be nice to change style attributes or script or transform on different sets of potentially overlapping objects. Any thoughts on this? -Jeff

2 1

Funny situation with use inside text
by Gail Banaszkiewicz 27 Jun '07

27 Jun '07

2 4

3D box tool update
by Maximilian Albert 27 Jun '07

27 Jun '07

Hi everyone, following Gail's example, I would like to post a short note on my progress, too, and at the same time announce version 0.1 of the 3D box tool. :) Well, that's probably too much of a promise. It is _extremely_ limited, the only thing it may be useful for is giving an impression of the envisaged behaviour (also see http://www.rzuser.uni-heidelberg.de/~malbert/core_functionality.shtml ). I'd appreciate comments, although I admit that there is not much to comment on yet. ;) All you can do at the current stage is create a box in a fixed perspective. No dragging of corner nodes is possible yet, nor of vanishing points (VPs) or perspective lines (PLs), nothing. Although you can of course treat boxes as "normal" groups of paths and edit them in the usual way. However, since currently the transform method is not implemented, you should hit Ctrl+Shift+G and Ctrl+G before doing so (in order to ungroup and regroup the paths representing the faces, which removes the 'sodipodi:type="inkscape:3dbox"' attribute from the group so that it is not recognized as a 3D box any more; this mainly fixes issues with undo/redo). In the current fixed perspective the edges of the box are drawn along parallel PLs directed towards "infinite" VPs in x-, y- and z-direction. You will notice, however, that as soon as the 3D box tool is activated, three points are drawn on the canvas. They represent "finite" VPs and it is possible to switch between "finite" (i.e., the PLs meet in the respective VP) and "infinite" (i.e., the PLs are parallel) in each direction by toggling the corresponding button in the 3D box toolbar. The VPs will be color-filled when their state is finite. Sorry that they don't disappear again when switching to another tool, but I didn't want to invest a lot of time in making them work better when I need to rewrite the code anyway as soon as they become draggable. BTW, already drawn boxes are not updated live yet, toggling the VPs' states only affects the drawing of new boxes (also note that when the VPs are white they don't affect the drawing of boxes, although they appear on the canvas; this is a bit counter-intuitive when using the tool for the first time). Since the functionality is so limited I decided to hide the tool's icon for the time being. To make it visible, simply uncomment line #129 in src/toolbox.cpp. You can also change the position/direction of finite/infinite VPs by setting the corresponding values in src/box3d-context.cpp (starting from line #122) and recompiling. Very inconvenient, I know. And if anyone wants to design a *nice* icon for the toolbox, you are most welcome (I haven't invested any time in that so far). Well, I really hope to make faster progress starting from next week. I have just handed in my Diplom thesis (whose completion took a lot more time than expected) so that I could only work part-time on SoC during the past weeks. Cheers, Max

6 8