Website
by Hinerangi Courtenay
Hello Inkscape developers,
I've been away from this list for a while - I designed the current Inkscape website a few years back, and it's been online for a few months now thanks to your hard work! I tried a couple of times to get the local web development environment up and running on my computer, but unfortunately life kept getting in the way.
Back when I first did the designs, responsive web design was still relatively new - but now with a few more years experience I'd love to help make the website work responsively in my spare time. Would giving it a fresh lick of paint as well--to bring it in with current trends--be welcome? Something more along the lines of this: https://www.dropbox.com/s/m2f988q3jqn2vbr/mockup-hp-2014-26-12_v0.1.png?dl=0 (it's a draft so it's missing important stuff like search, languages, etc, only has Arial fonts, and doesn't show what happens at different screen sizes)...
Happy holidays,Hinerangi Courtenay
8 years, 4 months
Separate the Goddamn Sliders from the number input please!
by Jelle Mulder
Dear all,
I don't know what made the new slider UI come through, but it absolutely
sucks. Why in gods earth does the text input reside beneath the slider
drag? Every time I want to set a blur I have to really be afraid to drag
the friggin slider to 90+% and then wait and pray for Inkscape to recover
from this mishap. The same for transparency. Can the sliders and the
number input please be separated into their own objects rather than this
highly frustrating BS object?
Especially with blur it is not immediately obvious whether you have
actually clicked the right object (text input) and then click again to try
and select the number input while Inkscape goes haywire calculating 90+%
blurs for every friggin click you make. Don't know how this behaves on
1024x768, but this is absolutely unworkable on highres screens. The
disfunctionality of this solution is not worth the few pixels gained for
the slider control.
Cheers, keep up the good work ;-)
Jelle
8 years, 4 months
General state of OSX native?
by Norbert Nemec
Hi everybody,
I am currently trying to get inkscape running with gtk3/OSX-native.
After quite a bit of struggling, I got everything compiled and
executable. When I run inkscape, however, I get tons of assertions, the
window looks terrible, is just barely responsive and completely
unusable. The info on the web is not very conclusive, so I wonder:
* is inkscape OSX/native generally still in such a bad state or did I
maybe not build it correctly?
* is anyone working on this actively?
* what is the state of inkscape/gtk3 in general?
* What are the areas that require work to improve the situation?
Perhaps, I could help out?
Generally, I used to use inkscape quite heavily several years ago on
Linux and absolutely loved it. Today, I am forced to use OSX for work
and would sometimes love to have inkscape available for some quick
drawing task. The usability of the inkscape/gtk2/XQuark on OSX, however,
has always put me off using inkscape altogether (booting Linux for every
occasional quick drawing is just not an option). I would really love to
see this situation improve.
Greetings,
Norbert
8 years, 4 months
Roadmap brainstorming for 0.92 and forward
by Bryce Harrington
With 0.91 finally coming to a wrap soon, there are many different ideas
on what to focus on next. One thing we all agree on is turning the next
few releases out more rapidly, 0.92 especially.
To do this, we'll need to carefully select which new features to
undertake each release; the more discriminating we are, the less risk of
delay we'll face in these. The less we undertake in parallel, the more
quickly we can perfect what we do tackle. The more we collaborate
together as a team, the better the end result will be.
The Inkscape roadmap has proven instrumental in prioritizing and
organizing our effort in the past. We can to use it again to help
chart our course of development for the next several releases.
http://wiki.inkscape.org/wiki/index.php/Roadmap
I'd like to tackle this in three steps: First, brainstorm and gather
ideas into a big list. Second, filter the list down to our most
pressing needs. And third, prioritize that list across the next
half-dozen releases.
I figure we should strive for one primary objective each release, with
one secondary and perhaps a few tertiary items. Of course, as we go
we'll also have some surprises, early deliveries and the like; no need
to turn those away. But the idea is to focus Inkscape on what we as a
project want to achieve each release.
What do you think should be listed in our Roadmap?
Bryce
8 years, 4 months
Website 1.3 Released
by Martin Owens
Dear Developers,
I've let loose the next version of the website 1.3, which includes a lot
of fixes, features and progress from Maren Hachmann, Brynn and myself.
You may find some errors or scuff marks, for these please report bugs to
https://bugs.launchpad.net/inkscape-web
Full release notes as requested here:
Website 1.3
- Refreshed design for resource pages
- New youtube video link feature
- Reporting and moderation of resources
- New comments functionality on resources
- Send message to user directly (private messages)
- New shield plugin for front page
- New alerts infrastructure, including emails
- New caching CDN infrastructure
- New mirroring functionality for resource items
- GPG verification of uploads if user has uploaded key
- New admin-side project functionality
- New 400 404 and 500 error pages
Fixes:
- Pasebin and Upload fixes (creating content)
- Profile page fixes
- Image cleanup removed (causing issues)
- CMS description and title added to html (for search results)
- Improved translation strings
- Fixed tab order for logins
- Added size to resource page
- Add fravorites to user profile page
- Removal of google links (use our own server)
- Updates for cms news plugin
- Many other fixes
8 years, 4 months
New Year's Release Schedule
by Martin Owens
Hi Everyone,
I'm a little unclear when we need the website ready for the new release.
I know our cache delayed things a little, but hopefully we can get our
frozen branch into the wild now?
Thanks for everyone's hard work on 0.9.1
Best Regards, Martin Owens
8 years, 4 months
Inkscape Website and Fastly CDN Service
by Martin Owens
Dear Inkscape Developers,
In a happy Christmas time result, the issues we've been having with
the very kind free CDN service from fastly.com have been ironed out
and now I'm pleased to announce that inkscape.org is up and running
with the new caching service effective imediatly.
So what does this mean?
Firstly, the configuration for our service has changed so django
content[1] (which are NOT cached) will always redirect to https from
http and will always redirect www.inkscape.org or the machine's
ip-address to just inkscape.org.
But this redirect does not apply to media, docs or static content.
This content can be served up either http or https and from any
combination of ip-address or domain. This was done to enable the
caching services machines to read these files without issue. The
website would always request content via https itself though.
All images, javascript files and css files which are considered
'static content' are served via /static/ are still available directly
but the site is configured to now request these via fastly caches.
All uploaded images to the cms, resource files in your gallery,
profile pictures and other 'media content' is also available directly
and is also configured to request via fastly. This means that if you
have uploaded an image with a name, deleted it, has the server clean
away the old filename /and/ re-uploaded a new and different version
within the one hour caching time, your images may not be updated. But
this is such an unlikely and rare occasion that I mention it only for
completeness.
Uploaded version of inkscape binaries - Because the media content is
now cached, downloading the inkscape pre-compiled binaries won't incur
the very high penalties if they all went directly from the webserver.
So we may now be able to host all our own downloads. This is good for
getting up off sourceforge.net and be able to cope with the demand.
I'm interested in suggestions on how we can stress-test the new system
to make sure it will be able to cope with a new release if we decide
to use it this way.
Best Regards, Martin Owens
8 years, 4 months
Auto marker color matching - The SVG 2 way.
by Tavmjong Bah
Hi,
I have implemented the SVG 2 'fill' and 'stroke' property values
'context-fill' and 'context-stroke' in trunk. These property values
allow the automatic matching of marker fill to path stroke. They also
allow cloned objects to reference the fill and stroke values from the
<use> element. Only solid color fill and stroke values are handled at
the moment. I added one marker that uses 'context-stroke' (as well as
'auto-start-reverse' which eliminates the need for separate arrow
markers for the start and end of a path) to marker.svg (at the end) so
people can try it out. At this stage, this should be viewed as an
experimental implementation. The SVG WG hasn't finalized this part of
the spec and there is work needed to provide an SVG 1.1 export mechanism
for use until the browsers implement this.
I wrote a blog as I was doing this work. It might be interesting to
other developers who are struggling with our code:
http://tavmjong.free.fr/blog/?p=1156
Tav
8 years, 5 months
fyi on some new and updated website content
by Brynn
Hi Friends,
As I've mentioned before, I've been helping with some of the website
content. These pages on the staging site below will replace their live site
counterparts, as close to the release of 0.91, as possible, given this
global community.
Of course changes can always be made afterwards, but if anyone wants
to review them, before they go live, your comments and/or questions are
certainly welcomed.
(Note that the formatting of the pages on staging, specifically the
indenting and extra line spaces, are not necessarily permanent. If you
compare to the live site, where *everything* is left justified, you can see
the difference. I think it makes the pages more interesting, they draw you
in more, and are easier to read. That's just my opinion. But, if there is
any consensus on this, I'd like to tweak all the live pages with the same
indenting and extra line spaces.) (Maybe rightly it should be done in the
style sheet/css, if it's done?)
Ok, here they are:
The content of this page
http://staging.inkscape.org/en/brynns-user-faq
will replace the content of this page
https://inkscape.org/en/learn/faq/
The content of this page
http://staging.inkscape.org/en/brynntest/
will replace the content of this page
https://inkscape.org/en/community/
The content of this page
http://staging.inkscape.org/en/brynn-community-pg2/
will be a new page on the live site, and will be linked to the Community
page. (from the old "External Galleries" page of the wiki)
The content of this page
http://staging.inkscape.org/en/brynns-learn-page/
will replace the content of this page
https://inkscape.org/en/learn/
This is the Development FAQ, which resulted from splitting out all the user
content. Everything is updated *except* section E. You are welcome to use
it, but I won't replace the wiki FAQ unless you specifically ask me to.
http://staging.inkscape.org/en/brynn-dev-faq/
All best,
brynn
8 years, 5 months
