March 2004 - Inkscape Devel - Inkscape Mailman

RE: [Inkscape-devel] new AST module
by bulia byak 02 Mar '04

02 Mar '04

>Starting today, I'll be working on a new Inkscape::AST module, which >will eventually replace the current SPRepr subsystem. Hurray!!! I can't wait when it's ready! :) But what does AST stand for? >The goal is to reduce the complexity of the XML code, while allowing for >e.g. CSS and SVG path data to be manipulated in the same tree, in >broken-down form (rather than as monolithic strings). And also to automate any and all inheritance and precedence issues, so that we can use ONE function to access the effective value of any property, be it in CSS string or in attribute, no matter how many levels of parents or defs (defs can be recursive, too) may affect it. _________________________________________________________________ Click, drag and drop. My MSN is the simple way to design your homepage. http://click.atdmt.com/AVE/go/onm00200364ave/direct/01/

2 1

directory reorganization
by Jonathan Phillips 02 Mar '04

02 Mar '04

SO I proceeded with the dir. reorg. last night and I have the head compiling and all that. I still have some other little tweaks, but the largest chunk (excluding packaging) has been committed. Please make sure that I did not break anything. The icons and extensions folders now are inside share. Also, I put the svg files that were in icons (about.svg, keys.svg, and tutorial.svg) and put them into share/screens and updated and created a variable INKSCAPE_SCREENDIR instead of INKSCAPE_PIXMAPDIR for these files where accessed in help.cpp (this is defined in src/Makefile.am). ISHMAL, could you please look and see how a fresh cvs windows build works. I have a strong feeling that a I broke it, as I have no test box and tried to conceptually follow what I did on the linux side. The part that might not work I'm pretty sure is contained in config.h.mingw and Makefile.mingw I believe. I became slightly confused after staring at weird makefile syntax for a couple of hours. I will delve further into cleaning up the makefiles now that I understand automake and makefiles much better. There is sooo much legacy architecture and cheap hacks where the same paths are called in different places in the makefiles. Also, would you all agree that I should migrate the current recursive makefiles to just one top-level makefile? You all might also email me/the list a wishlist of how to clean up the source tree and the makefile nasties as they currently exist. If you want to refer to the dir. reorg plan: http://inkscape.org/cgi-bin/wiki.pl?DirectoryReorgProposal Thank you, Jon -- Jonathan Phillips <jon@...15...>

6 9

roadmap items + general timeline
by Jonathan Phillips 02 Mar '04

02 Mar '04

Hello all, I'm just reviewing the roadmap right now and it looks like maybe we could all give it another once-over. There are a few tasks that have not been taken on by anyone. Maybe we should all look at the bug tracker as well to see if there are any bugs we can help smooth out--as this is the bug hunt. Also, I'm wondering when we think we will get 0.38 out the door generally. I know we don't operate on timed releases, but I think if we can start to see the general timeline for the next release, our work will start to hone in on a general time. Who is working on an extension proposal? That is on the roadmap for this release. I posted a wiki page so that we could splatter some paint on the canvas and brainstorm. http://inkscape.org/cgi-bin/wiki.pl?ExtensionArchitectureProposals Is there anything that needs to be freshened up on the site as well? If you wouldn't mind spending a couple of moments looking at it, I will update some aging news items, add some new screenshots, and so forth. thx Jon -- Jon Phillips UCSD Graduate Researcher Computational Media PO BOX 948667 La Jolla, Ca 92037 858.361.2811 www.jonphillips.info jon@...247...

2 1

Looking for Galleries out there...
by Jonathan Phillips 02 Mar '04

02 Mar '04

Does anyone have a gallery of work, or images online that were created with Inkscape. I am looking for artists whom have created work that we can link to on the website. If you would like to post your gallery of svg artwork, you can do so on the wiki. Jon -- Jonathan Phillips <jon@...15...>

1 0

Re: [Inkscape-devel] new AST module
by bulia byak 02 Mar '04

02 Mar '04

>svg.scene.forest.tree[x].branch[y].bird.color=blue; Absolutely. I love XPath. However, standard XPath is not equipped to access individual CSS properties, which we must access to control bird colors. So we'll probably need an extended XPath-like something for that. _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

2 1

new AST module
by MenTaLguY 01 Mar '04

01 Mar '04

Starting today, I'll be working on a new Inkscape::AST module, which will eventually replace the current SPRepr subsystem. The goal is to reduce the complexity of the XML code, while allowing for e.g. CSS and SVG path data to be manipulated in the same tree, in broken-down form (rather than as monolithic strings). libxml will still be used for parsing XML data, and hopefully we will be able to start using libcroco for CSS data as well. The new XML editor will also use the AST code, and it in turn will serve as a basis for the Layers dialog UI. Questions are welcome. -mental

4 4

Compile warnings
by Jon A. Cruz 01 Mar '04

01 Mar '04

I just did a rebuild after updating to the new layout. When I did, it came up with 805 warnings. Eeeek!!!! Guys, when you have a chance, see if you have -Wall configured and try to get to zero warnings. I know a lot of more verbose ones have come up recently, especially with our changes to C++ and such. So I am being a bit of a complainer here. :-) But... on projects I've seen where warnings were kept out, quality came up. So though I expect zero-warnings may not be hit any time soon, keeping that in mind as a goal will help our code be better. Thanks.

2 1

9. Extract SVG Canvas into a library 0.43
by Charles Goodwin 01 Mar '04

01 Mar '04

>From the roadmap overview: (http://www.inkscape.org/roadmap.php) 6. Create Plugin Architecture 0.40 * This architectural change will establish a new mechanism for how features are added and maintained in the codebase. 7. New Features 0.41 * Implement snap-to object, enhanced layer support, and boolean operations. 8. STL Architectural Change 0.42 * Shift codebase to using STL for data structures. * Replace use of #defines and enums with hashmap lookups 9. Extract SVG Canvas into a library 0.43 Obviously I'm massively ignorant of the issues involved, but from what I can see milestones 6 and 7 are relatively independent of 6 and 9. >From a GO perspective, it would absolutely brilliant if you could bring milestone 9 into milestone 6, the point at which you might start using libgoffice for the plugin handling. (And I personally hope you do because it will help make goffice more functional, featureful, and robust as well as give Jody a bit of help.) The reason I bring this up is that the sooner the Inkscape SVG canvas is available, the sooner other applications (esp. GO apps) can organise themselves around incorporating it. -- - Charlie Charles Goodwin <charlie@...208...> Online @ http://www.charlietech.com

5 4