- Inkscape Devel - Inkscape Mailman

SVGSlice extension progress (none so far)
by Lee Braiden 26 Jul '05

26 Jul '05

Jon Philips wrote: > Hello, I'm curious to your progress on SVGSlice and making it into an > extension? Could you send an email to the Inkscape mailing list please > about this...thanks! Jon, I'm sorry to report that I've been too busy to work on this lately. It definitely won't be ready to coincide with the next Inkscape release, if that's what you're wondering :( I *do* want to get it done, though, and my time has freed up recently. So, I'll try to get started on it soon, and hopefully have it all working before 0.44 is released. If anyone can point me to the latest docs for writing Inkscape extensions, that would help some. -- Lee Braiden http://www.DigitalUnleashed.com

2 1

20 minutes to edit this
by Jon Phillips 26 Jul '05

26 Jul '05

http://inkscape.org/cgi-bin/wiki.pl?PressRelease042 Okay, I've put it together...please edit and I will then make the personalized (informal) version from this and then start seeding this release. I'm serious...just edit the page directly and/or post some things here...I'd like to start sending out around 12:30 PM my time PST. Jon -- Jon Phillips San Francisco, CA USA PH 510.499.0894 jon@...235... http://www.rejon.org MSN, AIM, Yahoo Chat: kidproto Jabber Chat: rejon@...896... IRC: rejon@...897... Inkscape (http://inkscape.org) Open Clip Art Library (www.openclipart.org)

1 0

release notes should be htmlized?
by Ralf Stephan 26 Jul '05

26 Jul '05

In case noone noticed: The link on the SF Files page with text 0.42 points to a flat text file filling the full page without structure. ralf

2 1

0.42 announcements?
by Kees Cook 26 Jul '05

26 Jul '05

Okay, I think all the packages are on SF now. Who's going to add the News item on the main inkscape site? (Or rather, what else is left to do?) -- Kees Cook @outflux.net

2 1

Re: [Inkscape-devel] Re: confusion on the mandriva bug
by mike＠...869... 26 Jul '05

26 Jul '05

But you compiled Inkscape itself with apbuild, right? That should be good enough when using static libraries. At any rate, the dependencies look OK. I'd suggest people test this new package and let's see if we do any better. Original Message: ----------------- From: aaron@...749... Date: Tue, 26 Jul 2005 09:20:30 -0500 To: mike@...869..., inkscape-devel(a)lists.sourceforge.net Subject: Re: [Inkscape-devel] Re: confusion on the mandriva bug mike@...869... wrote: > Base system stuff, available nearly anywhere. The wild card is libC of > course but that's what apbuild is for. If you compiled things statically > using apbuild it should be fine. Maybe I do have a problem then. The only libs I compiled were libgc, libglibmm and libgtkmm. Of those only libgc was compiled with apbuild. Aaron Spike -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .

2 1

Re: [Inkscape-devel] Re: confusion on the mandriva bug
by mike＠...869... 26 Jul '05

26 Jul '05

> Well I'm pretty sure it wasn't a typo. I partly followed Kees' > instructions and here is the result. OK, let's have a look NEEDED libpthread.so.0 NEEDED libm.so.6 NEEDED libgcc_s.so.1 NEEDED libc.so.6 NEEDED libz.so.1 Base system stuff, available nearly anywhere. The wild card is libC of course but that's what apbuild is for. If you compiled things statically using apbuild it should be fine. NEEDED libgtk-x11-2.0.so.0 NEEDED libgdk-x11-2.0.so.0 NEEDED libatk-1.0.so.0 NEEDED libgdk_pixbuf-2.0.so.0 NEEDED libgthread-2.0.so.0 NEEDED libpangoft2-1.0.so.0 NEEDED libpango-1.0.so.0 NEEDED libgobject-2.0.so.0 NEEDED libgmodule-2.0.so.0 NEEDED libglib-2.0.so.0 No *mm libraries there, so it looks like it worked! I'm surprised pangoft2 and ATK are there though. Very few programs use those libraries, if they're in the DT_NEEDED list it sometimes indicates the dep stripper isn't working (or it wasn't compiled with apbuild). You can probably ignore this though. NEEDED libxml2.so.2 NEEDED libpng12.so.0 NEEDED libX11.so.6 NEEDED libfontconfig.so.1 NEEDED libfreetype.so.6 NEEDED libstdc++.so.5 These all look OK to me. > Does that look good? I see that Kees' instructions have even more > compiled in staticly. Yes, Kees statically links nearly everything, but for the autopackage we take a less aggressive approach. For instance it's reasonable to assume GTK+ is present (though it may not be new enough!). Likewise, libstdc++.so.5 is usually either present or easily gettable - and we're likely to start 'fixing' distros that don't ship with it in future. thanks -mike -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .

2 1

Re: [Inkscape-devel] Re: confusion on the mandriva bug
by unknown＠example.com 26 Jul '05

26 Jul '05

Bob Jamison wrote: > Heh. You might want to check your computer's clock. > The email is dated 01/02/1970. ;-) This is completely off topic. I sent that email yesterday so I would expect it to have been 2005-07-25. But I've been playing with date conversion (unix timestamps to human dates) in MSAccess so that I can work more efficiently with data from our weather station and it seems to be changing the date on my computer. Hmmm. Screwy. Thanks for noticing, Aaron Spike

1 0

[Fwd: Calling for Tux articles!]
by Jon Phillips 26 Jul '05

26 Jul '05

Anyone up for writing a good howto and getting published? I'm going to write a howto on using Inkscape to create a file that is then finally submitted to the Open Clip Art Library. Each howto can get you $300.00, so why not? Jon -------- Forwarded Message -------- > From: Tux Editor <ed@...851...> > To: Ryan Paul <gaerdin@...400...>, Ryan Paul > <segphault@...856...>, John Knight <knight.john.a@...400...>, John > Knight <knightsy_j@...899...>, Xavier Spriet <xavier@...900...>, > Xavier Spriet <xavier@...901...>, Kevin Brandes <blargity@...400...>, > Michael J. Hammel <mjhammel@...902...>, Daniel Jackson > <dejackson@...903...>, Shane <shaneoneal@...904...>, Randall Wood > <rsw22@...729...>, Shannon Baker <sbaker@...905...>, Sean > Carruthers <sean@...906...>, Matthew Downs <mwdowns@...400...>, > Philip W. Raymond <tvphilip@...210...>, Allen Mercer > <allenmmercer@...907...>, James Roettger <roettger@...400...>, Josh > <josh@...908...>, joshuo@...909... <joshuo@...909...>, Karen Hall > <karen@...910...>, Keith McElroy (home) > <keithdmcelroy@...911...>, Lew Pitcher <lpitcher@...456...>, > Phil Barnett <philb@...912...>, Rod Davenport > <rod.davenport@...400...>, Brander, Roy <Roy.Brander@...913...>, > Scott Nesbitt <scott@...914...>, Sudipta Chatterjee > <sudipta_cht@...829...>, Tony Godfrey <tonygodfrey@...782...>, > Aaron Peters <acpkendo@...36...>, Bill Kendrick <nbs@...915...>, > Blessen Cherian <blessen@...916...>, Dave Neary <dneary@...8...>, > David Thorarinsson <dabbi@...917...>, Dirk Elmendorf > <dirk@...918...>, Eric Goebelbecker > <egoebelbecker@...400...>, Gar Nelson <Gar.Nelson@...919...>, Jay > Hamilton <JayHam@...920...>, Jes Hall <jes.hall@...921...>, > jmak <jozmak@...400...>, John Hebert <johnahebert@...36...>, Jon > Phillips <jon@...235...>, Michael <mogmios@...922...>, Michael > Lim <michael@...923...>, Melissa Hardenbrook <pip@...915...> > Subject: Calling for Tux articles! > Date: Mon, 25 Jul 2005 16:35:23 -0500 > > Folks, > > You are getting this letter because you have either > written for Tux Magazine, or we have gotten the > idea that you have expressed an interest in writing > for Tux magazine. Some of you are old-timers > already, but it might be useful to read through the > whole email anyway. > > This has been a bad month for me - I was sick 2 > weeks, full-time single dad, sob story, etc., etc., > > The bottom line is that I'm behind schedule looking > for articles for the September issue. If you have > any original articles or article ideas you could turn > around quickly, please write to me and let me know > asap. If you have an article ready, it is important > that the article has NOT already been published > elsewhere. We get a lot of requests to re-publish > something already published somewhere else, > and I'm afraid we do not do that, not even if the > article was published in a different language. > > I don't expect many (or perhaps any) of you to have > an article ready. So I will follow up soon with a list > of article ideas that are up for grabs. If anything in > the list appeals to you and you think you are up to > the task, then let me know asap. I will need these > articles as soon as possible. > > I will continue to send you ideas, and in the future > the short deadline problem shouldn't exist (at least > it should be rare). Hopefully, we can get a nice > backlog of articles piled up by getting submissions > from many of you, which will make it unnecessary > to go into "emergency mode" like this month. ;) > > Okay -- for the newbies -- please read the brief > guidelines for writing for Tux below, and have a > look at the sample assignment letter we will send > you if we accept an article pitch (or if you agree > to write an article in my suggestions list). > > Thank you all for expressing an interest in Tux! It's > great to have a long list of potential authors we can > draw upon! > > -Nicholas Petreley > > > ------------------------------------------------------------------------------------- > > Here are some quick guidelines for writing for Tux: > > Keep it simple. > > Tux is for desktop users, many of which are newbies > or Windows converts. Most of them use KDE, but > we don't ignore GNOME entirely. If there is a way > to do something point-and-click, then that's > how to write it. Avoid the command line like the > plague. Avoid hexadecimal numbers, etc., like the > plague. Point-and-click is how to do it. > > Our readers are, for the most part, totally > uninterested in open source issues, > free software philosophy, programming, > server issues, how something works under > the covers, etc. They want to know what to > click and when in order to do a certain task. > In other words, if they want to remove red-eye > from their photos, they want to use the > easiest program for doing that, and they > just want to know what buttons > to click, which menu selections to make, > how to select an area of the photo, etc. > > As for hardware, they want to know what > works and what doesn't work. And if they > already have something that doesn't work, > they want to know if there is an easy way to > make it work. When I say "easy way", I > mean they REALLY, REALLY don't want > to compile anything to make their hardware > work! > > > WRITING STYLE TIPS: > > Avoid Passive voice. Use active voice. > > BAD: > > "Color settings can be changed by..." > > BETTER: > > "You can change color settings by..." > > BEST: > > "Here is how to change the color settings. > First, click on X..." > > > If your article has screenshots (and most of > them should), then here's how to handle them > in the text. Refer to them in the text so that > the reader knows which picture to look for > when reading that part of the article. Then > place a marker in the appropriate spot within > the text, identifying your screenshot file, and > the caption that should go with it. > > Example: > > ....article text.... > The Konqueror window should now look something > like what you see in Figure 4. > > ....possibly a bit more article text, but not enough > to lose the context.... > > [insert konq_example.jpg] > Figure 4. Caption: Konqueror Split Windows > > ....more article text... > > > For those who haven't seen it yet, I've included a > sample assignment letter below. Note that we > prefer PLAIN TEXT articles. In a pinch, we can > convert from almost any word processor format, > but whatever you do, please!! > > DO NOT SUBMIT YOUR ARTICLE AS HTML! > > > Okie dokie -- now here's the sample assignment > letter. > > --------------------------- > > Dear ____________, > > Your article "___________" has been accepted for possible > publication in TUX magazine. We expect your article will cover the > following: gadgets for use with Linux, and that it be kept > around 1,000 or more words. > > In the following portion of the assignment letter, please be careful > to use the correct email addresses specified. It is easy to confuse > them because the email addresses are similar -- ed@...924... and > editor@...925... These are two different editors, however. > > The deadline for the final version of your article is ________. The final > version of your article must be sent to editor@...852... Keep in > mind that we do not accept multiple drafts of articles, and therefore, > we expect a complete and final version on or before the deadline. > > If your article is published, we pay $300 for "how-to" articles and > $100 for reviews. If your article falls into another category, we > will negotiate a payment. > > All writing is done on speculation. If TUX magazine decides to use > the work, we will purchase first rights and compilation rights to > the article. However, we are under no obligation to publish > the work. If the article is selected for publication, your payment will be > $________. > > Your article will be copyedited according to TUX style, and > English grammar and spelling, though we ask that you carefully review > the materials you submitted for accuracy and completeness. We expect > that you submit your article in text-only format and that any > figures, tables, listings and sidebars be sent as separate files; provide > titles or captions for all figures, tables, listings and sidebars, and > indicate in the text where such items should be placed. > > Please insert the titles/captions and references to figures, etc., > within the text itself at the appropriate places. Place them on > separate lines from the article text. For example: > > .....article text.... > > [insert configuration.jpg] > Caption: The configuration dialog > > .....article text.... > > Please send a photo of yourself, a brief bio, and your mailing address > along with your article. > > Once your article is submitted, it will be in the publication queue and > therefore cannot be submitted elsewhere unless 1) TUX magazine formally > rejects the article, or 2) the author notifies TUX magazine of his/her > intent and TUX magazine agrees to release the article at that time. > > If you have any questions, please feel free to send email to > editor@...851..., and please cc ed@...852... > -- Jon Phillips San Francisco, CA USA PH 510.499.0894 jon@...235... http://www.rejon.org MSN, AIM, Yahoo Chat: kidproto Jabber Chat: rejon@...896... IRC: rejon@...897... Inkscape (http://inkscape.org) Open Clip Art Library (www.openclipart.org)

1 0

rel notes reset
by bulia byak 25 Jul '05

25 Jul '05

Bryce: please lock this page from editing: http://inkscape.org/cgi-bin/wiki.pl?ReleaseNotes042 Everyone: please use the above address to refer to release notes for 0.42, in the announcements etc. The page http://inkscape.org/cgi-bin/wiki.pl?ReleaseNotes is reset for 0.43. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

3 2

source documentation
by Ralf Stephan 25 Jul '05

25 Jul '05

Hello, just to announce that I committed source documentation changes to several dozen files. People are likely to recompile a lot but you know such things happen after new releases :] There are two doxygen config files in the distribution: src/inkscape.doxygen (used for the web pages) and src/Doxygen. The latter is specific for some files in order to be able to quickly check correctness or missing documentation. My goal for the next release is to have one-liners for all classes and functions in the source files referred to by src/Doxygen. In this regard, I will introduce \note, \todo, and \bug tags in comments, and I would ask people to use them for their own documentation, too. \todo's for example will be collected in a todo file by doxygen. \bug's should be moved into the tracker, eventually, probably. Finally, I noticed people use 'e.g.' and 'i.e.' incorrectly: you should not forget to always place a comma after them, i.e., e.g., like this. Reason: doxygen thinks the sentence ended there. ralf

3 3