November 2003 - Inkscape Devel

celtic knot question
by Robert Crosbie 07 Nov '03

07 Nov '03

Well my first post to the list, without actually having received a digest yet, is to ask Bryce how he made the over-under effect in the celtic knot in the screenshot. Celtic knots are a fascination of mine: http://members.rogers.com/rcrosbie/celtic_svg.htm (older drawings) I use SVG to create plans for my woodworking hobby. http://members.rogers.com/rcrosbie/woodworking.htm I browsed the wiki and saw the celtic knot plugin idea. I'm naturally all for it. :) Douglas Zongker has a neet celtic knot generator using a tiling method with output in postscriot here: http://isotropic.org/uw/knot/ I really hope I can provide some input to inkscape in the future. Cheers, Rob. http://members.rogers.com/rcrosbie PS. I hope there are no flag posts. :) _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

2 1

New to the scene
by Jon A.Cruz 07 Nov '03

07 Nov '03

Hi. I've been lurking on the sodipodi scene for a while, but now am getting time to actually contribute. At the same time Inkscape appears! Anyway, I've worked a fair bit with GTKmm before, and I'll try to see if anyone is on Jabber tonight (evening PST).

2 1

Jabber, Email, Wiki, and Website
by Bryce Harrington 06 Nov '03

06 Nov '03

Communication is key for the success of any team effort, and in open source projects, written communication is critical for success. Briefly I'd like to explain the different communication channels we have, in case some are unfamiliar with them. === Jabber === Chat is a convenient, immediate, and free-form way of exchanging information, and we make heavy use of it. For fun we decided to try out Jabber and liked it enough that we've continued to use it. Details about getting started with it are on the website. We'd like to know if people would prefer IRC, though. If enough people cannot or do not wish to use Jabber, then we should switch to IRC. Please speak up if you have an opinion on this. If you have a good discussion in chat that you think others might be interested in, consider sending a copy of the log to the mailing list. === Email Lists === Email is preferred for information that needs wider visibility, such as things that will require discussion in preparation for making decisions. The mailing lists are also archived, so new developers can review past discussions to get up to speed. If you see or write a good email on a topic that people will wish to refer to longer in the future, consider pasting a copy of it into Wiki, so that it'll be easier for people to find and maintain later. === Wiki === Wiki is the new discussion medium we're introducing. A Wiki is a website that can be edited and added to by anyone. It's like a virtual whiteboard, and that's how we want to use it. It's good for gaining wide visibility and its more persistant than email (no having to browse through archives). Wiki's are great for capturing info quickly and semi-permanently, and for writing collaboratively. This makes them perfect for brainstorming and hashing out plans, designs, floating proposals, etc. Wiki's can get a bit chaotic over time, and for people with only a quick interest in the project they can be too much effort to search through for "official" information. So, if a page in Wiki becomes 'official' enough that it needs higher visibility and/or more formality, consider turning it into a proper web page. === Website === The website is simple flat HTML files, using SSI to put the header and footer on. It's stored in the CVS module inkscape_web. Anyone with CVS commit permissions can and is encouraged to make changes to the website. Changes to the website are posted to the inkscape-cvs@ mailing list. Each communication medium has its strengths and weaknesses. If we are all good about using them appropriately, and promoting information from one to the next where beneficial, it will give Inkscape a great communication infrastructure. Miscommunication is a leading cause of trouble in projects, so it is well worth our effort to work to prevent them from occurring. Bryce

1 0

Exciting!
by Jonathan Phillips 06 Nov '03

06 Nov '03

I have to say that INKSCAPE is very exciting! I really dig the name and the opening up rather than the bottlenecking of development is going to help. EXCELLENT! jon -- Jon Phillips UCSD Graduate Researcher Computational Media PO BOX 948667 La Jolla, Ca 92037 858.361.2811 www.protofunk.org jon@...15...

1 0

Re: Re: more infos
by Cédric GEMY 06 Nov '03

06 Nov '03

-- Sorry if we misunderstood, I've to improve my english. For the manual, if there is a different UI in Sodipodi and in Inkspace, there's no trouble, if fonctions are the same, files are the same. The only things to do is to create a different file for Inkscape in there's some difference. In fact, since the manual is written in XML Docbook, the only need is to add an attribute specifying if the information is going for Sodipodi or Inkscape. Pages are automatically generated following this. But this was just a idea. In the future I'll use sourceforge tools, ans less the mailing list. But on the site, I didn't find no direct link to trackers and forums I had to follow the links in the project info section of the wiki Cédric

2 1

Re : more infos about Inkscape
by Cédric GEMY 06 Nov '03

06 Nov '03

Hi Bryce and everybody, I knew that Sodipodi has to be transferred to C++, but not it'd become a new project. Will Inskape be a standalone project, at the end completeley different from Sodipodi. If it is the case, why did you decide to make this new project ? What will it include in the future ? Will it tend so interactivity or animations edition ? Will it be compliant with SVG sub-recommandations as SVG-print ( is that the 'Ink') or SVG-Mobile? Who are the people developping Inkscape ? Are other people needed ? In which case and particular need ? Etc... I can try helping if the code is reasonably commented. At this time I'm still working on Sodipodi User Manual. I'm considering it as a free document. Since Inkscape has the same features than Sodipodi, and if it is convincing you, it can be intergrated as Inkscape Documentation. Friendly, Cédric

4 4

Updates to Inkscape website
by Bryce Harrington 05 Nov '03

05 Nov '03

I added super preliminary FAQ and screenshot pages, and fleshed out the homepage with some news items. http://www.inkscape.org/ Bryce

1 0

C++ fixes (mostly) complete
by MenTaLguY 03 Nov '03

03 Nov '03

I've essentially finished the C++ conversion; the only thing I had to give up on for now was getting spsvgview to build. I've disabled it for the present. The main application itself seems to work fine, at any rate. -mental

2 1

tag
by MenTaLguY 03 Nov '03

03 Nov '03

By the way, I've tagged the version of the conversion that works for me with the tag 'g++-conversion'. -mental

1 0

Objective for milestone 1
by Bryce Harrington 02 Nov '03

02 Nov '03

Given the amount of work the g++ conversion has taken, I'm simplifying the focus for milestone 1 to be completion and release of the g++ conversion and getting the website up to snuff. I think those are probably the two most important things right now, since a release and a website are prereqs to getting others involved. What do you guys think? I've listed some items for Milestone 2 but consider them extremely preliminary. I'm figuring that once we've got the C++ conversion securely under our belts, we're going to want some breathing time to do some random R&D, cleanup, etc. etc. so I think keeping the tasks for M2 flexible would be a good thing. Feel free to shove things that seem uninteresting/unimportant to you to the future, or move up or add things you are drawn to working on. Thinking beyond that to mid-term strategies, I figure we're going to want to have a mix of feature, architecture, and test development, and select a specific effort for each of these areas to focus on. Whatever work is selected for the architecture development, lets make sure to do it on a branch, as this type of work is the most likely to require leaving the tree in a broken state for a long time. Bryce

1 0