Decommission SourceForge Downloads
by Martin Owens
Dear Developers,
Because of the thousands of downloads per week of old inkscape
releases (mostly windows msi files) from the sourceforge account and
because of our successful transition to using our own website with
caching proxy fastly.
I will be deleting all files from the SourceForge files folder in two
weeks time (June 14th). Please make sure you have any and all files
you wish to back up, and any downloads you want to make available for
your platform available on the website.
If there are any objections please raise them here and I won't go
ahead with the proposed deletion.
This cleanup is mostly to reduce our online search footprint, reduce
confusion with users and prevent users getting hold of old, obsolete
or buggy versions of inkscape. (I've mentioned this cleanup before,
but I wanted to be more proactive and state that I'll do it and take
responsibility)
Best Regards, Martin Owens
7 years, 12 months
google deprecating SMIL for Chrome
by Brynn
Hi Friends,
Someone brought to my attention, the other day, this entry in
Tavmjong's blog: http://tavmjong.free.fr/blog/?p=1262, which discusses
Google's Intent to Deprecate SMIL in the Chrome browser, and links to that
discussion:
https://groups.google.com/a/chromium.org/forum/?_escaped_fragment_=topic/...
Since I've been learning a lot more about animation (while writing a
new Animation page for the website) it really seems rather shocking. From
what I understand (although still learning, *Always*) it seems like SMIL
comes the closest to being "true" SVG animation (of all the existing ways to
animate SVG).
The Intent to Deprecate message says that MS will be creating CSS
animation support for SVG, which will make animation of SVG possible in all
browsers. I don't have the technical knowledge to be able to compare SMIL
to this new CSS animation (and since it says "just announced" maybe it
doesn't actually exist yet). (I am aware of current CSS3 animation, but not
about this new bit.)
But I'm definitely curious about what will be lost of SMIL, which
that new CSS can't replicate, or conversely, if this new CSS will have any
new abilities that SMIL doesn't have. And I'm curious what our Inkscape
community thinks about this apparently pending deprecation in Chrome?
(Because I guess Mozilla/Firefox will follow suit, since IE already stopped
supporting it, some versions back. And that makes it seem like a sad day
for animation with Inkscape.)
I understand that the hopes from several years ago, to have a
working SVG animation tool by the release of Inkscape 1.0, have now gone by
the wayside (I guess for lack of anyone interested enough to do it). But I
wonder, if Inkscape had even an experimental SVG animation model, based on
SMIL (along with a new UI which probably would be needed, afaiu) if Google
would still want to deprecate SMIL?
I do see some comments in the Intent to Deprecate discussion, from
Inkscape-related people, or organizations, but I'm surprised not to see any
discussion here in this list. Is it just because of not having anyone (or
small group) interested in developing animation for Inkscape? Or maybe
there was some discussion on IRC, where I don't usually watch. It just
seems a little hopeless to me, not to see a vigorous uproar about it, or
even any comments from Inkscape developers on the google discussion. I must
be still missing something in my understanding of animation and Inkscape.
Maybe it's much more hopeless than I realize, no matter what google does
with Chrome?
What do you all think about google deprecating SMIL?
Thanks,
brynn
7 years, 12 months
RFC: Inkscape Code of Conduct
by Bryce Harrington
We have a draft version of a Code of Conduct for our project, which
Martin and others have carefully assembled for us. As written it looks
quite good, and I'd like to go ahead and get this finalized; one less
thing on our collective todo list. :-)
But before it gets finalized, I'd like to run it by the development
community once more for comments. I'll collect and incorporate the
comments as best as I can, and repost it for an informal ratification.
If there are a substantial number of suggestions, I'll repost some
interim versions.
Once it's agreed to, we should probably also have some sort of process
for amending it. Maybe nothing more complex than posting a diff and
same voting as done for the ratification.
Bryce
Inkscape Community Code of Conduct
THIS IS A WORK IN PROGRESS!!!
Inkscape Community Code of Conduct (DRAFT)
Like the technical community as a whole, the Inkscape community is
made up of a mixture of professionals and volunteers from all over
the world, working on every aspect of the project - including
mentorship, teaching and connecting people.
Diversity is one of our huge strengths, but it can also lead to
communication issues and unhappiness. To that end, we have a few
ground rules that we ask people to adhere to when they're
participating within this community and project. These rules apply
equally to board members, developers, mentors and those seeking help
and guidance.
This isn't an exhaustive list of things that you should or should not
do. Rather, take it in the spirit in which it's intended - a guide to
make it easier to enrich all of us and the technical communities in
which we participate.
This code of conduct applies to all spaces managed by the Inkscape
project. This includes IRC, the mailing lists, the bug tracker, the
web site, official Inkscape events and any other forums created by
the project team which the community uses for communication.
* Be friendly and patient.
* Be welcoming. We strive to be a community that welcomes and
supports people of all backgrounds and identities. This includes,
but is not limited to members of any race, ethnicity, culture,
national origin, colour, immigration status, social and economic
class, educational level, sex, sexual orientation, gender
identity and expression, age, size, family status, political
belief, religion, and mental and physical ability.
* Be considerate. Your work will be used by other people, and your
code, comments and art will be read and looked at by them. You
in turn will depend on the work of others and your code, comments
and art will be commented on. Any decision you take and any
remark you make will affect other people, and you should take
those consequences into account when making them. Remember that
we're a world-wide community, so you might not be communicating
in someone else's primary language.
* Be respectful. Not all of us will agree all the time, but
disagreement is no excuse for poor behavior and poor manners. We
might all experience some frustration now and then, but we cannot
allow that frustration to turn into a personal attack. It’s
important to remember that a community where people feel
uncomfortable or threatened is not a productive one. Members of
the Inkscape community should be respectful when dealing with
other members as well as with people outside the Inkscape
community.
* Be careful in the words that you choose. We are a community of
professionals, and we conduct ourselves professionally. Be kind
to others. Do not insult or put down other
participants. Harassment and other exclusionary behavior aren't
acceptable.
This includes, but is not limited to:
+ Violent threats or language directed against another person.
+ Discriminatory jokes and language.
+ Posting sexually explicit or violent material.
+ Posting (or threatening to post) other people's personally identifying information ("doxing").
+ Personal insults, especially those using racist or sexist terms.
+ Unwelcome sexual attention.
+ Spamming, trolling, flaming, baiting, or other attention-stealing
behavior.
+ Advocating for, or encouraging, any of the above behavior.
+ Repeated harassment of others. In general, if someone asks you to stop, then stop.
* Take responsibility for your words and your actions. We can all
make mistakes; and when you do, take responsibility for them. If
someone has been harmed or offended, listen carefully and
respectfully, and work to right the wrong.
* When we disagree, try to understand why. Disagreements, both
social and technical, happen all the time and Inkscape is no
exception. It is important that we resolve disagreements and
differing views constructively, keeping discussion on a civil
level. Remember that we’re different. The strength of Inkscape
comes from its varied community, people from a wide range of
backgrounds. Different people have different perspectives on
issues. Being unable to understand why someone holds a viewpoint
doesn’t mean that they’re wrong. Don’t forget that it is human to
err and blaming each other doesn’t get us anywhere, rather offer
to help resolving issues and to help learn from mistakes.
* Step down considerately. If you leave or disengage from a
responsible position within the Inkscape project, we ask that you
do so in a way that minimises disruption to the project. Tell
people you are leaving and take the proper steps to ensure that
others can pick up where you left off.
* Conflicts of interest. You should be aware when you are
conflicted due to employment or other projects you are involved
in, and abstain or delegate decisions that may be seen to be
self-interested. We expect that everyone who participates in the
project does so with the goal of making life better for its
users. When in doubt, ask for a second opinion. Perceived
conflicts of interest are important to address. Act to ensure
that decisions are credible even if they may occasionally be
unpopular, difficult or favourable to the interests of one group
over another.
* Ask for help when unsure. Nobody is expected to be perfect in
this community. Asking questions early avoids many problems
later, so questions are encouraged, though they may be directed
to the appropriate forum. Those who are asked should be
responsive and helpful.
Be aware that user-created content on our website can and will be
moderated. If you notice an upload, comment or user that clearly
violates this Code of Conduct, help us to keep this website a
welcoming place by reporting this to our moderators or contact us at
<insertEmailAddressHere> or via our
<insertContactPageLinkHere>. Also, if you would like to help us by
becoming a moderator yourself, please don't hesitate to contact this
website's administration team.
Further tips for good and successful communication, including but not
limited to how to protect yourself from burnout, can be found in the
Freenode Channel Guidelines.
Credits for the sources and inspiration of this code of conduct go to
the SpeakUp! project, the Django Project, Ubuntu as well as many
others. This Code of Conduct is licenced under the Creative Commons
Attribution Share-Alike 3.0 Licence.
------------------------------------------------------------------------
7 years, 12 months
Selection sets
by Lucian Holland
Hi,
I’ve been using the development version of Inkscape for a few days now and am really excited about some of the new features that have gone in. Looking at the material one the website and in the archives of this list I’ve been able to piece together what most of them do, but I’m struggling to make any sense of the “selection sets”. I think know in theory what it’s supposed to do - resolve the ages old “how do I group across layers” problem, but I can’t make the UI do anything useful. Is it incomplete as it stands in trunk, or am I just missing something very obvious? Happy to be pointed at a link/video/whatever if there’s one out there that gives more detail, my cursory searches didn’t reveal much unfortunately….
Cheers, and thanks for all the hard work on a great piece of software - I’m still very much learning to use it and every day that goes by I still get a few “Wow, that is *so* cool!” moments :-)
Lucian
--
Lucian Holland
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
8 years
Inkscape Devlibs (windows)
by Josh Andler
Hey all,
Now that Cairo 1.14.2 is out, can both the 32-bit and 64-bit devlibs
get updated? I think we should aim to get 0.91.1 out in maybe a month
or so. I will start looking into doing backports later this week. I
figured I'd bring up the devlibs first though since they seem to take
a bit to get updated.
Cheers,
Josh
8 years
Yesterday's Website/Wiki outage
by Maren Hachmann
Hi everyone,
at about 00:00 UTC today the website and Wiki went down.
This seems to have been caused by problems during scheduled maintenance
at Oregon State University, involving device migrations and network
structure modifications, and a mislabelled plug.
We noticed this at about 2:00 UTC. Half an hour later, the Wiki
pages were accessible again, while the inkscape.org website still showed
error pages instead of contents due to read-only access to the database.
At about 4:30 UTC, we received a mail from OSUOSL about the cause of the
problem, the website had come back online a few minutes earlier.
If you see any remaining errors, please send a message to the docs
mailing list or to Martin directly,
Regards,
Maren
8 years
inkscape plugin distribution via pip
by Brad Pitcher
Hi folks,
I'm toying with the idea of installing Inkscape plugins using pip. In fact,
at this very moment, my OpenSCAD DXF Output plugin (
https://github.com/brad/Inkscape-OpenSCAD-DXF-Export) can be installed like
this:
pip install --target=<installation_dir> inkscape-openscad-dxf
The only downside I can see is that in addition to the plugin files it
installs a little cruft: easy_install.py,
inkscape_openscad_dxf-0.0.1-py2.7.egg-info, _markerlib, pkg_resources,
setuptools, and setuptools-17.0.dist-info
However, I don't think those extra files would be any problem. The big
upsides to this approach are that dependencies are automatically included
and that PyPi (https://pypi.python.org/pypi) is searchable.
What do you all think of this approach? Is it a good/bad idea?
8 years
Re: [Inkscape-devel] Build problem
by Alex Valavanis
I'm also not at home but can do it tomorrow if no one beats me to it!
It's a standard header, so the position should not matter. I would
suggest putting it immediately before <gtk/gtk.h>.
AV
On 29 May 2015 at 13:58, Jabier Arraiza <jabier.arraiza@...2893...> wrote:
> Alex, work ok!
>
> Im not at home so i coulden't commit now, also not sure about the best
> position of the header.
> Think the faster is you do the commit. Like the idea?
>
> Thanks, Jabier.
>
>
> On Fri, 2015-05-29 at 12:54 +0100, Alex Valavanis wrote:
>> Hi Jabier,
>>
>> Did including <stdint.h> work OK? If so, it's probably worth
>> committing that change.
>>
>> Cheers,
>>
>>
>> AV
>>
>> On 29 May 2015 at 12:53, Jabier Arraiza <jabier.arraiza@...2893...> wrote:
>> > Hi Alex.
>> > I try with clang and gcc with the same result:
>> > jtx@...3244...:~$ gcc -dumpversion
>> > 4.9.2
>> > jtx@...3244...:~$ clang -dumpversion
>> > 4.2.1
>> > jtx@...3244...:~$ cat /proc/version
>> > Linux version 3.16.0-4-amd64 (debian-kernel@...501...) (gcc
>> > version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-3~deb8u1
>> > (2015-04-24)
>> >
>> > I include <stdint.h> headers instead.
>> > Thanks, Jabier.
>> >
>> >
>> >
>> > and clang
>> >
>> > On Fri, 2015-05-29 at 12:29 +0100, Alex Valavanis wrote:
>> >> Hi Jabier,
>> >>
>> >> Which compiler (+version) are you using? At the moment, we really
>> >> shouldn't have to enable C++0x features for trunk builds.
>> >>
>> >> Instead of setting the build flags, try including <stdint.h> at the
>> >> top of sp-canvas.h
>> >>
>> >> Ideally, we should check for the availability of <cstdint> and use
>> >> that instead, although this is only guaranteed to exist with C++11 so
>> >> we probably shouldn't use it yet.
>> >>
>> >>
>> >> AV
>> >>
>> >> On 29 May 2015 at 12:10, Jabier Arraiza <jabier.arraiza@...2893...> wrote:
>> >> > Hi to all.
>> >> >
>> >> > Finaly get working using CFLAGS_CXX=-std=c++0x
>> >> > Get from here:
>> >> > http://stackoverflow.com/questions/11069108/uint32-t-does-not-name-a-type...
>> >> >
>> >> > Regards, Jabier.
>> >> >
>> >> > On Thu, 2015-05-28 at 10:45 -0700, Josh Andler wrote:
>> >> >> Why such an old revision? I just pulled down current and it's at 14182.
>> >> >>
>> >> >> Cheers,
>> >> >> Josh
>> >> >>
>> >> >> On Thu, May 28, 2015 at 3:26 AM, Jabier Arraiza
>> >> >> <jabier.arraiza@...2893...> wrote:
>> >> >> > Hi to all.
>> >> >> >
>> >> >> > Any one have this problem compiling?
>> >> >> > /home/jtx/Development/inkscape/trunk/src/display/sp-canvas.h:126:5:
>> >> >> > error: ‘uint8_t’ does not name a type
>> >> >> > uint8_t *tiles;
>> >> >> >
>> >> >> > Clean build r13689
>> >> >> >
>> >> >> > Regards, Jabier.
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > ------------------------------------------------------------------------------
>> >> >> > _______________________________________________
>> >> >> > Inkscape-devel mailing list
>> >> >> > Inkscape-devel(a)lists.sourceforge.net
>> >> >> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>> >> >
>> >> >
>> >> >
>> >> > ------------------------------------------------------------------------------
>> >> > _______________________________________________
>> >> > Inkscape-devel mailing list
>> >> > Inkscape-devel(a)lists.sourceforge.net
>> >> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>> >
>> >
>
>
8 years
Build problem
by Jabier Arraiza
Hi to all.
Any one have this problem compiling?
/home/jtx/Development/inkscape/trunk/src/display/sp-canvas.h:126:5:
error: ‘uint8_t’ does not name a type
uint8_t *tiles;
Clean build r13689
Regards, Jabier.
8 years
