May 2005 - Inkscape Devel - Inkscape Mailman

LaTeX Export
by Michael Forbes 10 May '05

10 May '05

I am trying to develop a barebones LaTeX export extension. I have wrote the code mostly based of the PovRay export and included the .h and .cpp file in src/extension/internal/Makefile_insert. libinternal.a includes the extension but the main program does not. Can anyone help me with this? Thank you. -Michael Forbes ------------------------------------------------------------ Student System Operator binx.mbhs.edu BEN Manager http://ben.mbhs.edu BNC Internet Division http://bnc.mbhs.edu MBHS Webmaster http://www.mbhs.edu BlazerNet President http://blazernet.mbhs.edu Computer Team Co-President http://computerteam.mbhs.edu MBLUG President http://mblug.mbhs.edu ------------------------------------------------------------

5 10

Defaulting gnome-vfs to yes
by Bryce Harrington 10 May '05

10 May '05

I've committed a change to configure.ac which defaults the GNOME VFS feature to 'on' if automake detects that the Gnome VFS library is present on the system. Keep an eye out for bugs; I've fixed all the ones I've known about. As a reminder, the GNOME VFS feature makes it possible to specify a URL on the commandline when starting inkscape. I.e.: $ inkscape http://mysite.org/foobar.svg It will load the svg file via http into memory and launch Inkscape. There is no support for this in the File Open dialog at this time; it still works only with local files. I don't have any plans to change that, so if you want it, feel free to add it. Bryce

3 4

NEW: <style> rendering support
by Peter Moulder 10 May '05

10 May '05

Inkscape now understands <style> elements: it correctly renders the following simple document: <svg> <defs> <style type="text/css"> .strokeblue {stroke:blue;stroke-width:5} .fillred {fill:red} </style> </defs> <rect x="10" y="10" width="50" height="50" /> <rect x="70" y="10" width="50" height="50" class="strokeblue" /> <rect x="130" y="10" width="50" height="50" class="fillred" /> <rect x="190" y="10" width="50" height="50" class="fillred strokeblue" /> </svg> There are a number of limitations: - Allows a single <style> element in the document. Doesn't allow external stylesheets, doesn't allow more than one <style> element. (Or rather it ignores all but one of the <style> elements, possibly changing which one it respects based on which was most recently re-read.) See notes below. - No editing interface other than the XML editor. (There are two parts to this: (i) editing the stylesheet; (ii) specifying what classes each object belongs to.) - Doesn't respect media restrictions (e.g. ignores "this rule applies only to non-visual media" directives, and doesn't allow having one style for print and another style for on-screen). - Someone more familiar with how to subclass an SPObject (i.e. what methods need to be instantiated and how) should have a look at sp-style-elem.cpp. - Not tested much. > > As members of the s4-p18, me Mamdouh El Tabech and Nicolas Jacquey, we are > > interested now in trying to solve the bug of global style. > > > The problem is divided into two, whether the style was included in the > > beginning of the document or it was in an extra file. > > > Do you have any idea to help us in where and what to change? The limitation of just one author stylesheet per document is an oversight in libcroco datastructures. Dodji (libcroco maintainer) agrees it's a libcroco bug, and the CRCascade or CRStyleSheet data structure can be changed accordingly. (The way most of libcroco implements `list of T' is for the T struct to get next/prev members, i.e. add next & prev members to CRStyleSheet, add cr_stylesheet_* functions for accessing this list, and leave CRCascade unchanged. Not saying I like the current scheme, but I think we should use the same scheme throughout libcroco, and consider changing the scheme throughout libcroco at once.) Meanwhile, Inkscape will also need changing: SPStyleElem's read_content method will need to update just its own CRStyleSheet, and we'll need to make sure that the list of stylesheets in the CRCascade matches the order of their occurrence in the document, so that we get the right precedence when stylesheets conflict with each other. I don't know the right way of handling external stylesheets. Does any other part of inkscape allow external xlink:href's ? libcroco's CRInput either already allows URLs or at least has it planned. (I don't have the source code handy here.) Handling @media rules and <style>'s media attribute is a Simple Matter of Programming. Existing code: SPStyleElem has a media field defined in media.{cpp,h}, initialized to all media. pjrm. -- bbyak: swatches, rich text, gradient on canvas... JonCruz: The answer to the ultimate question of life, the universe, and everything... JonCruz: Inkscape 0.42!!!!!!!

2 1

Adobe Photoshop 8.0 - 75% OFF
by Kendra L.Brown 10 May '05

10 May '05

Get all the popular software possible for extremely low prices! Our software is 2-10 times cheaper than sold by our competitors. Just a few examples: $79.95 Windows XP Professional (Including: Service Pack 2) $89.95 Microsoft Office 2003 Professional / $79.95 Office XP Professional $99.95 Adobe Photoshop 8.0/CS (Including: ImageReady CS) $179.95 Macromedia Studio MX 2004 (Including: Dreamweaver MX + Flash MX + Fireworks MX) $79.95 Adobe Acrobat 6.0 Professional $69.95 MS Project 2003 Professional Special Offers: $89.95 Windows XP Professional + Office XP Professional $149.95 Adobe Creative Suite Premium (5 CD) $129.95 Adobe Photoshop 7 + Adobe Premiere 7 + Adobe Illustrator 10 All main products from Microsoft, Adobe, Macromedia, Corel, etc. And many other... Enter here: http://www.ineedsoft.biz Regards, Kendra Brown _____________________________________________________ To be taken off future campaigns, go: http://www.ineedsoft.biz/uns.htm _____________________________________________________

1 0

translation of HACKING and README
by Arpad Biro 09 May '05

09 May '05

Hi, We have a French translation for inkscape/HACKING and inkscape/README in the tracker: http://sf.net/tracker/index.php?func=detail&aid=1190412&group_id=93438&atid… I committed them as inkscape/HACKING.fr and inkscape/README.fr respectively. Please let me know if we should use some other filename or location instead. Arpad Biro __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

5 5

SPView moved to src/ui/view/
by Bryce Harrington 09 May '05

09 May '05

I've moved the view.* code into src/ui/view/. Eventually svg-view* and all of the *desktop* stuff will move into this subdir as well. I checked compilation and that inkscape runs, but it's possible this change will cause breakage somewhere, so please keep an eye out. Bryce

1 0

gtkmm - DialogManager in SPDesktop
by Bryce Harrington 09 May '05

09 May '05

I've added the DialogManager into the old SPDesktop. This means that the current codebase can now use the new dialogs via DialogManager. It also means that the way is now open for anyone that wishes to create new gtkmm dialogs using the new dialog code. I have hooked in one dialog - Messages (aka ishmal's Debug Dialog). I chose this because it's a finished dialog, and because I figure it's not as critical as some of the drawing dialogs, in case it misbehaves. If you wish to create a new dialog, please feel free to use the Messages dialog as an example. To add a new dialog, the process is straightforward: 1. Create a .cpp and .h for your dialog in src/ui/dialog/. The dialog must derive from Dialog (see dialog.*). 2. Add your class to DialogManager. You do this by adding an #include to dialog-manager.cpp, add a member pointer to the DialogManager class in dialog-manager.h, and a get*Dialog() routine (you can just cut and paste from one of the other dialogs). 3. Add a menu item and shortcut key for your dialog. See verbs.cpp and interface.cpp. I think you'll find that creating dialogs with the new system can be done in about half the code as before, and maintenance is greatly increased since the common boilerplate code is factored out into base classes. Also, the classes are simpler in that they have fewer pointers, and don't need to handle their own instantiation; DialogManager takes care of this. Fewer pointers and less need for memory management implies fewer opportunities for bugs to creep in. Also, since DialogManager is used for accessing dialogs, there is no need to include the dialog headers in other parts of the code; theoretically this should cut down on include header nesting and make compilation work a bit faster. Some caveats: The preferences loading/saving code isn't implemented. This means that dialogs won't "remember" their settings between program runs. However, there is code to track this info in there, so should be straightforward to hook up if anyone wishes. As well, some of the code for transient behavior is there, but not all, so transient behavior is probably not right. Feel free to fix; it's all implemented in the Dialog base class so only has to be fixed in one place, and then all dialogs will behave correctly. Bryce

1 0

gcc 4 help needed
by MenTaLguY 09 May '05

09 May '05

I've been told that line 111 of debug/logger.cpp doesn't compile with gcc 4. Could someone please give me the specific error (with all context lines, please)? -mental

2 3

English tutorials converted
by bulia byak 08 May '05

08 May '05

May 1st, 2005 — Thanks to the active help from the community, all English tutorials that we had in SVG are now converted to DocBook! From within Inkscape, they are still available as fully editable SVG which you can play with, but having the DocBook source makes it easy to produce any other formats or renditions automatically. In particular, all converted tutorials are now availble in HTML, linked from our Documentation page. What's next? We have several of the tutorials translated into several languages. Now we need to convert these to DocBook as well. Here is a page http://inkscape.org/cgi-bin/wiki.pl?TranslationInformation with details on how to translate tutorials or convert existing translations. We already have the Basic in Spanish and several French ones are being worked on; the rest are up for grabs. Pick a tutorial and make it available in your native language! -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

4 4

Re: Fwd: [s4-p18] [Inkscape-devel] svg2ps - Test Files
by MenTaLguY 08 May '05

08 May '05

On Sun, 2005-05-08 at 13:35, bulia byak wrote: > What I have at the moment is a couple of scripts that read the CSS2.1, > SVG1.1 and CSS3Text specs as downloaded off the w3c site, find all the > property definitions within them and automagically produce output such > as: > > /** \brief Representation of the CSS 'counter-reset' property > > Generated from "[ <identifier> <integer>? ]+ | none | inherit" > Inherit: False > Initial: none > */ > struct inkscape::style::css::counter_reset { > bool read(Glib::ustring const &str); > Glib::ustring write() const; > void set_to_initial(); > unsigned set:1; > unsigned inherit:1; > unsigned type:1; > struct inkscape::style::css::identifier { > unsigned integer_set:1; > struct css_identifier value_identifier; > struct css_integer value_integer; > }; What exactly does this sort of nested declaration mean? > std::vector<struct identifier> value_identifier; > enum {type_identifier, type_none}; > }; > 1) Where do I go from here? The simplest answer is to bundle the whole > lot into SPStyle, like we have at the moment. The problem with that is > of course that the current struct is at least 320 bytes and putting > all 160+ css properties into it would consume a significant amount of > memory in a large drawing. At the opposite end of the memory:cpu ratio > spectrum is to have no SPStyle at all and require everyone to call > read() themselves if they want a pre-parsed property. Half-way points > are of course possible too, where particularly common properties like > fill and stroke are held in SPStyle but everything else is evaluated > on each request. There are also lazy evaluation schemes which save the > results of the evaluation, and so on and so forth. My personal > favorite at the moment is to have most things lazy but a selected few > always calculated. That's probably the best long-term goal. For the short-term lumping everything into SPStyle is best because it is simple and is known to work. Longer-term I will have to get a better sense of the design before making any recommendations. Probably some sort of lazy thing backed by an associative data structure, queried by symbols (i.e. GQuark or the like) would be best. Whatever it ultimately is, the interface for lazy and non-lazy properties should remain uniform. > 2) The more fundamental question: am I even going in the right > direction? I'm replacing a simple yet difficult-to-maintain piece of > code with a complex yet zero maintainance (or close to it, anyway) > piece of code. What's the point anyway when I should only need to run > it once, then throw it away? Since the majority of properties are > simple enums, wouldn't it be easier to do it all by hand? Is this just > refactoring for its own sake, without any useful new features in > sight? (Actually that's not true; a proper implementation of shorthand > properties is notably lacking at the moment). In principle it's much better. Don't ever believe the "just once" part though. It's best to have the source specifications and the script that generates them in the source tree, and have them be authoritative. And generate the code as part of the build process. Because Things Will Change, and the last thing you want is to tempt people into manual hacking of generated code. Do see if you can hoist some of the stuff that's currently generated into non-generated superclasses though. Anything that gets repeated multiple places is screaming for refactoring. The platonic ideal is that there should only be one place in the entire codebase which is authoritative for a particular pattern of code. -mental

1 0