- Inkscape Devel - Inkscape Mailman

[website] website structure
by Ian Caldwell 15 Dec '10

15 Dec '10

Hello, Also send on behalf of "Steven M. Ottens" Hi all, I've been pondering the site structure using the three focus groups, while keeping in mind that our audience is diverse and groups overlap. To put it simply: New users want to: -know what inkscape is -get it -know how to get started Existing users want to: -get new versions of inkscape -get add-ons -learn how to use it -get involved (user/designer style) -get the latest news Developers want to: -get source code -learn how to develop -get involved (developer style) -get the latest news Note that all three groups want to 'get something', all three want to know/learn something and two want to get involved somehow and get updated with the latest news. Also getting involved means different things to different people. Also the current distinction between developers and community is not entirely valid in my opinion. For a starter, developers are a part of the community :) Also bugtracking is both important for users and developers. In stead of focussing on the different target groups, I'd like to focus on the different activities. When someone visits the site, (s)he will not first think of him/herself as a developer, user, etc. (S)he will have a specific need which (s)he wants to be met. So instead of forcing visitors to think which role they fit, I'd like to meet their questions head on. So my suggestion is to make these 6 toplevels for the menustructure: -*about* (which should meet questions on what it is, who work on/with it, what can you do with it, what can it do) -*downloads* (which should answer all questions relating getting inkscape and related resources) -*learn* (which should answer questions on how to get started, use it and develop for it) -*get* *involved* (which should answer questions on how to get involved in all possible ways) -*news* (which should show what's happening in the community, the development, the wiki) -*donate* (which should bring us money ;) The frontpage should apart from the 6 menu-items provide a direct link to the download which is appropriate for the visitors OS and underneath an 'other version link' which links to the main downloads page, similar to firefox approach. Also it should provide direct access to 'overview' 'features' 'gallery' 'getting started/learning resources' and show the latest news. This probably leaves us some space to be filled on the frontpage. I've not yet come up with appropriate extra content, so if there are any suggestions, please let me know. One question I have is the integration of the wiki within the main site. Obviously being a wiki, we cannot or should not force the same structure as the site. Though different parts of the wiki are interesting in different places in the menu structure. It would be good if we create and link to main wikipages on different subjects. For instance wiki/learn as a starting page for all learning-related wikicontent. This way we can integrate the wiki more into the main site. The rest of the menu structure would then look something like this (note that it is most likely not complete, I'm typing this on the move so don't have access to the website and wiki to check for missing bits): ABOUT -overview -screenshots -gallery -cases -features -supporters/sponsors (?) DOWNLOADS -windows -linux -mac -other -source -addons (palettes, plugins etc) -open clip art (extern) LEARN -books -tutorials -videos -FAQ -wiki/learn -dev docs -user docs GET INVOLVED -forums -mailinglist -bugtracker -irc/jabber -wiki -roadmap -developer -designer NEWS -news -releases -contests -meetings -wiki/recent DONATE (nothing under here, just a direct link to the donations page) I am aware this structure is quite different from the current and as such it might take quite some effort to relocate current content in the new structure. As stated before I haven't looked to each individual page in the current site and checked if it has a proper place in the new structure. I haven't thought very hard and deep on how to integrate the wiki into the main site, other than the linking in the menu, this might need some more thought. Also it is a proposal so I'm open for feedback, comments and improvements. Regards, Steven

2 1

Re: [Inkscape-devel] Embed Python script engine
by Yu-Chung Wang 15 Dec '10

15 Dec '10

Is the link become available in the WIKI? We are actually working on adding scene and animation editor into the inkscape. This will make the inkscape become an environment similiar to the Abobe Flash. So far, we have finished some prototype to edit multi page SVG file and some simple animation support. So far, in the integration is only at the Node and NodeObserver level, therefore, its relationship between inkscape and python VM is quite weak. However, in order to make it easier to use, we need to bind more and more functions into the python. This will make the binding easier to be broken from version to version. This is why we want to make it into the code base. The other possibility is not to put the python into the code base directly. Instead, define an binding interface which should be used by any system like ours so that we can develop our stuff outside the code base safely. You can decide to include our stuff or not until the technical issue is clear. >>I'll list out a few more details on this in the wiki, so that the reoccurring discussion can be captured.

6 21

0.48 trunk compilation bug&fix, launchpad questions
by Robin Palotai 15 Dec '10

15 Dec '10

Hello, Sorry in advance, this is a composite-topic email. 1) Launchpad question - am I ok so far? Being new to bzr/launchpad I'm a bit confused yet. What I would liked to do is to branch the 0.48.x branch and apply/rewrite some of my former patches to there (not the 0.49.x, because unfortunately my libs seem to be too old to compile it). I branched lp:inkscape/0.48.x, and also pushed it to a custom branch atlp:~palotai-robin/inkscape/0.48.x . Now at the bottom of the launchpad page, it tells that it is "stacked on lp:inkscape", where I would expect it to be lp:inkscape/0.48.x. Is this ok? 2) Some compilation errors with the 0.48.x trunk I used 'configure --disable-lcms', gcc 4.3.2, x86, Debian Linux (lenny), glib 2.22.4, glibmm 2.16.4, gtk 2.12.12, gtkmm 2.12.7 (according to the package manager). 2A) The error mentioned here: http://comments.gmane.org/gmane.comp.graphics.inkscape.devel/35338 Solution was to include "io/sys.h" in color-profile.cpp 2B) Gtk::IconTheme::load_icon doesn't have default third parameter on my system, while inkscape uses the two-param version at two places: interface.cpp <http://comments.gmane.org/gmane.comp.graphics.inkscape.devel/35338>- Glib::RefPtr<Gdk::Pixbuf> pb = iconTheme->load_icon( it->second, *it2 ); + Glib::RefPtr<Gdk::Pixbuf> pb = iconTheme->load_icon( it->second, *it2, (Gtk::IconLookupFlags) 0 ); ui/widget/dock-item.cpp - Glib::RefPtr<Gdk::Pixbuf> pb = iconTheme->load_icon( it->second, *it2 ); + Glib::RefPtr<Gdk::Pixbuf> pb = iconTheme->load_icon( it->second, *it2, (Gtk::IconLookupFlags) 0 ); 3) How do I commit these patches? Having these fixed, what is the expected lp/bzr procedure for create bug/commit patch? 4) Is adding new features (those I originally wanted) on the 0.48.x branch is in vain? If it is a corrections only branch, then maybe it is in vain. But I can't compile for 0.49, so maybe creating the patches for 0.48 would make it easier to merge them in 0.49 eventually. Thank you, Robin

2 1

Firefox corrupts svg files !
by Ivan Louette 12 Dec '10

12 Dec '10

I send this message here because they concern settings files created for Inkscape and I think everybody concerned by svg creation could be concerned. Some time ago I placed some svg filters files on OpenClipart and more recently I heard from users that they didn't work despite all my tests were positive. Yesterday I discovered that following the way you take to download them they work or not. The problem seems to be specific to Firefox and doesn't occur with other browsers (tried with Safari, Opera and Chrome). Here are the address of the two files : The first one is an Inkscape template which activates filters for background images or objects : http://www.openclipart.org/detail/92749 This second one contains color filters decicated to work on background object or images (place any shape on top of a picture and apply the filters to this shape) : http://www.openclipart.org/detail/92977 Here is the problem : - When you click on the "Download SVG" button on the OpenClipart page it opens the svg in Firefox. Then, if you save this SVG file displayed in Firefox and try to work with it in Inkscape it doesn't work because Firefox changed something in the file. - If you right click on the "Download SVG" button and do "Save target as", then the file download unchanged on your disk and all works as expected. Could somebody send the bug to Firefox ? Thanks for your attention, ivan

3 8

Re: [Inkscape-devel] r9946 build failure
by ~suv 12 Dec '10

12 Dec '10

Issues with revision 9946: <http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/9946> On 12/12/10 11:39, ~suv wrote: > CXX dialogs/spellcheck.o > dialogs/spellcheck.cpp: In function ‘void sp_spellcheck_accept(GObject*, > GObject*)’: > dialogs/spellcheck.cpp:783: error: ‘SPDocumentUndo’ has not been declared > make[3]: *** [dialogs/spellcheck.o] Error 1 > make[2]: *** [all] Error 2 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 System: osx, gcc 4.2.1, gtk 2.22.1, glib 2.26.1, gtkmm 2.22.0 sanguivor (on irc) confirms same error (no system info provided). houz (on irc) has no build failure, but reports that 'File > Open' no longer works with r9946 (file chooser freezes when 'Open' is pressed): System: debian, gcc 4.4.5, gtk 2.20.1, glib 2.25.11, gtkmm 2.20.3 ~suv

3 4

(no subject)
by John Cliff 12 Dec '10

12 Dec '10

http://sportseventmerchandise.com/images/gr.php

1 0

Update W3C tests
by Tavmjong Bah 11 Dec '10

11 Dec '10

Hello, The W3C SVG working group is in the final stages of getting the SVG 1.1 "Second Edition" out the door. The test suit has been greatly expanded as part of this work. Before the standard can be finalized, each test in the suite must have at least two SVG renderers pass the test. I have run Inkscape via the command line over the suite. At the moment there are 440 approved tests (this may change in the next few weeks). The results are: OK (PASS): 166 PARTIAL: 23 FAIL: 251 Most of the fails are due to non-supported features: No DOM, animation, interactivity support: ~160 No SVG font support: ~20 Still, there is quite a bit of room for improvement, some probably trivial. I've prepared web pages for the tests. They can be found at: http://tavmjong.free.fr/INKSCAPE/W3C_SVG_1.1F2/harness/htmlInkscapeApproved… Tav

2 2

website design bounty
by Alexandre Prokoudine 10 Dec '10

10 Dec '10

Hi, I have a spare hardcopy of recently released book "inkscape 0.48. Essentials for Web Designers" and I propose to make it a bounty for winner of the website design contest. Could anybody please adjust announcement text? Alexandre Prokoudine http://libregraphicsworld.org

3 2

Re: [Inkscape-devel] website
by Steven Ottens 09 Dec '10

09 Dec '10

Hi All, Since I've volunteered and been drafted as a Ux/UI guy for the redesign of the website a couple of remarks and questions on the idea for the new website. For me and probably also for the designers as well it would be nice to define who the visitors of the new website will be. I came up with these three main groups. -new users -users (artists/designers etc) -developers These three groups have different needs and expectations from the site. This is my view on their needs and expectations, feel free to shoot holes into them/enhance them. New users The new user group has been addressed by the 'Big Issue' talk on blenderguru. Short version: -they need to know what it is, what it does and where to get it. -frontpage is their first introduction to Inkscape and as such should be focussed towards their need (Short explanation, download button/link, 'learn' button/link) and visually attractive Users They already have inkscape, they visit the site for a couple of reasons. -Check for/download new version (put version number on the download button/link) -Learn how to use inkscape/improve their skills through tutorials -Get help with (technical) issues with inkscape -Showcase their work -Get more resources like scripts/plugins/palettes etc. -... Developers They already know inkscape and like to improve it. So they visit the site because: -They like to know how to get the sourcecode, compile it etc -File/solve bugs -...? (I'm no developer so help me out :) The reason I ask this, is because knowing who is using the site and why makes it easier to design a site-structure. The current mind-map of the site, although very complete doesn't provide a very balanced site-structure. 'Community Frontpage' is 3 levels deep, 'Press and references' is one level deep and 'Open clip art' is not even part of the site, though all three are shown as equal children of the frontpage. Having a beautiful and consistent design, isn't enough. A logical and short site-structure is important as well; having relevant subsections close to each other is key. Love to hear your thoughts. Having the discussion now makes it possible to incorporate the outcome in the winning design from day one. Regards Steven -- Senior UxDesigner

2 1

Inkscape Tango/Art Libre icons.
by David Bolack 08 Dec '10

08 Dec '10

Without getting on any particular nerves about Inkscape and this Icon Set, I have a question. :) Looking at the wiki page here, http://wiki.inkscape.org/wiki/index.php/Themable_icons, it appears that ya'll have vastly extended the Art Libre set. Have these additions been contributed back into Art Libre (the page for that looks stale) and if not are what license are they under?

2 2