[lance@...2167...: [Hosting] Fwd: IPv6 Offering]
by Bryce Harrington
----- Forwarded message from Lance Albertson <lance@...2167...> -----
Date: Tue, 6 Jan 2015 16:55:44 -0800
From: Lance Albertson <lance@...2167...>
Subject: [Hosting] Fwd: IPv6 Offering
Well, we're even one more step closer... Apparently NERO is now ready to
officially start supporting IPv6 . I've already submitted the form and
will let you all know what our next steps are and when.
---------- Forwarded message ----------
From: Steve Menken <smenken@...3198...>
Date: Tue, Jan 6, 2015 at 4:31 PM
Subject: IPv6 Offering
NERO is excited to now provide IPv6 addressing to all NERO partners. Please
check out our website (http://www.nero.net) to review our IPv6 offering. If
you have questions about the service, you can contact the NERO NOC and we
would be happy to assist. We will also offer a webinar in the near future
on IPv6 that we hope will help you to plan and deploy IPv6 across your
networks. Once we have a date established for the webinar we will send out
Co-Interim Director, Network for Education and Research in Oregon
Oregon State University | Open Source Lab
Hosting mailing list
----- End forwarded message -----
8 years, 4 months
Article on Inkscape 0.91 -- deadline
by "Christoph Schäfer"
As some of you may remember, I have a deadline to meet for my article on 0.91 in the prestigious Swiss PUBLISHER magazine, namely 12 January.
I can write most of the article based on 0.91pre3 and the draft of the release notes. There are, however, a few questions left that I hope to receive answers from those in the know.
1) PUBLISHER 1/2015 will be printed by the end of January. Any chance to have 0.91 final out in the wild by then?
2) How "native" will the OS X release be this time? (This is very important to the readers of the magazine, since most of them are using Macs.)
3) 64-Bit versions: Please forgive my ignorance here, but the RN draft mentions 64-Bit support for Windows. Is there any other platform left for which 64-Bit versions are still unavailable?
For those who are awaiting my essay on Inkscape for print/as a real AI alternative in print workflows (cough), my contacts in the industry are awaiting the 0.91 release, and their feedback will be based on the latter, not on 0.48.
Happy New Year and good luck with the release!
8 years, 4 months
General state of OSX native?
by Norbert Nemec
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.
8 years, 4 months
Re: [Inkscape-devel] General state of OSX native?
by Hiram Jerónimo Pérez
I’m glad to see it works good, there are some glitches, like missing icons for new/open and weird shadows in menus, but my first try of the gtk3-build was fine, I’ll test some stuff and let you know
Hiram J. Pérez
On Sun, Jan 4, 2015 at 8:25 PM, Partha Bagchi <partha1b@...400...> wrote:
> Sure. Here is the URL.
> Unzip wherever you like and run it from there. You are also optionally
> put it in your Application folder.
> Please let me know how it works out for you.
> Thanks for testing.
> On Sun, Jan 4, 2015 at 7:29 PM, Hiram Jerónimo Pérez
> <hiram.001@...400...> wrote:
>> Hi, do you have any build?
>> I’d be glad to try it
>> Hiram J. Pérez
>> On Sun, Jan 4, 2015 at 6:28 PM, Partha Bagchi <partha1b@...400...> wrote:
>>> I compiled osxmenu (~suv's branch) using gtk3 and it looks good to me.
>>> It was a little tricky since configure is not set to automatically do
>>> this and gtk-mac-integration had to recompiled for gtk3.
>>> If you wish to try it, let me know.
>>> On Tue, Dec 30, 2014 at 7:50 AM, Norbert Nemec
>>> <Norbert.Nemec.list@...173...> wrote:
>>> > Thanks! I just tried the gtk2/Quartz build from your profile and it
>>> > really feels and looks much better than anything I have seen before on
>>> > OSX.
>>> > The most recent gtk2/x11 build seems somewhat improved as well, but it
>>> > still does not provide the smooth experience that I remember from Linux.
>>> > I really hope that the native-OSX (including osxmenu) will soon be
>>> > stabilized sufficiently to have it considered for the official builds.
>>> > Greetings,
>>> > Norbert
>>> > Am 29/12/14 1:20 , schrieb su_v:
>>> >> On 2014-12-29 01:16 (+0100), su_v wrote:
>>> >>> Too bad - you seem to dismiss any other option than GTK+/Quartz 3 for
>>> >>> OS
>>> >>> X. If this isn't quite true, you might want to give newer
>>> >>> GTK2/X11-based
>>> >>> app bundles a test, or even one with GTK2/Quartz. Links to downloads
>>> >>> (OS
>>> >>> X 10.7 or later) can be found on the download page at inkscape.org
>>> >>> (0.91pre3, 0.91+devel), and on my launchpad profile page 
>>> >>> (including the experimental 'osxmenu' branch).
>>> >>> We also started an attempt to track osx packaging status in the wiki
>>> >>> .
>>> >> (…)
>>> >>>  https://code.launchpad.net/~suv-lp
>>> >> Sorry, wrong link, use this one instead:
>>> >>  https://launchpad.net/~suv-lp
>>> >>>  http://inkscape.org/en/download/
>>> >>> 
>>> >>> http://wiki.inkscape.org/wiki/index.php/Notes_on_Packaging_for_OS_X
>>> > ------------------------------------------------------------------------------
>>> > Dive into the World of Parallel Programming! The Go Parallel Website,
>>> > sponsored by Intel and developed in partnership with Slashdot Media, is
>>> > your
>>> > hub for all things parallel software development, from weekly thought
>>> > leadership blogs to news, videos, case studies, tutorials and more. Take
>>> > a
>>> > look and join the conversation now. http://goparallel.sourceforge.net
>>> > _______________________________________________
>>> > Inkscape-devel mailing list
>>> > Inkscape-devel(a)lists.sourceforge.net
>>> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>>> Dive into the World of Parallel Programming! The Go Parallel Website,
>>> sponsored by Intel and developed in partnership with Slashdot Media, is
>>> hub for all things parallel software development, from weekly thought
>>> leadership blogs to news, videos, case studies, tutorials and more. Take a
>>> look and join the conversation now. http://goparallel.sourceforge.net
>>> Inkscape-devel mailing list
8 years, 4 months
New Developer Comments
by Mark Harmer
Hello Inkscape Devs,
I recently found an issue that I wanted to fix (not particularly related to
this thread but it's: https://bugs.launchpad.net/inkscape/+bug/307833).
As a first time dev/user of the website/wiki/build system, I wanted to
point out some issues I ran into while building Inkscape that may not be
obvious to those that constantly use it. I do want to point out that
overall, I think building was relatively easy.
I attempted to build under Windows 8.1 x64:
1. Bazaar seems to take awhile to download the sources, it was around 30
minutes for the 'bzr checkout lp:inkscape' command, this may be a
misunderstanding of the wiki instructions and bzr though. Another 10-15
minutes was required for the devlibs64.
2. I initially tried to build a 32-bit target, however I think the compiler
stated in the Wiki (GCC 4.6.1) may have been outdated for the project since
there are new warnings that were turned on that I had to turn off in the
build.xml for the compiler to stop complaining.
3. When building 32-bit I eventually was able to compile and link, however
when copying the binaries the libgomp-1.dll appeared to be missing and the
build failed - possibly due to the old compiler toolchain used from the
Wiki instructions? For reference I was using:
4. I noticed that the btool with the "-j" parallel job configuration didn't
seem to spawn more than 1 compiler process. Only after looking at the
source did I realized that I needed to build it with "-fopenmp". The
"-fopenmp" option was the alternative build step for btool in the Wiki
instructions, I think it should be instead the first option (and possibly
move the other two alternatives into another section), wiki for reference:
5. I gave up on 32-bit target and tried the 64-bit build. This worked after
I realized that the config.h was not being regenerated after I had
previously built it for a 32-bit target, after deleting this file the build
succeeded. To be more specific I think I was getting some invalid functions
being called due to POPPLER_NEW_ERRORAPI not being defined correctly. A
separate folder for all generated build files would make this more
intuitive to me, but I understand it would likely be a bit of work.
6. I didn't seem to easily find where the output was being generated,
initially I thought the inkscape.exe in the build folder was the final one,
and of course attempting to run it causes dll dependency failures. Only
after poking around did I realize the 'inkscape' subfolder was the final
7. I'm confused by the unittests, I think I've run across 2-3 different
a. A standalone test executable w/o a real framework located at:
b. Some CxxTest's located at: inkscape/src/svg/test-svg.cpp
c. What I think are tests using GTest, I haven't found these in the
source I pulled down, but the Jenkins job I think is using them (I found
this after some mailing list searches):
(This seems to question whether I have the correct sources or not
since I can't find these test names anywhere)
***8. Linking is slow, on the order of minutes, so it makes development
turn-around time on changes very long. This is actually a really big
turnoff for developing. I think this hits inkscape.exe and inkview.exe.
The linking is with the default link arguments, I did change
compilation from -O2 to -O0 and added -g for debugging. This also ties back
to #5, where if a separate build folder existed I could have one for debug
builds and one for release/optimized and not have to clobber them each
time. Maybe there's an Ant/btool property I'm missing? I'm not sure if 'ld'
has incremental linking support, and if it would even help, similar to what
Visual C++ has.
Nice to haves:
9. I've heard some mention of cmake support (
http://wiki.inkscape.org/wiki/index.php/CMake), but I don't know the
status. In general if Visual Studio was supported under Windows it would
make it much easier for debugging in the IDE. The recent community edition
might make this option more attractive under Windows.
10. Bazaar seems to be used in relatively few projects, I know this would
be a huge undertaking to switch and may not be worth the effort, but it
might be a barrier for new contributors. It's something I think is minor,
but it is yet another 'thing' I need to read up on/learn.
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.
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
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?
8 years, 4 months
extending inkview, background color as parameter
by Torsten Mohr
I use inkscape to create android icons / menu entries, action bar items etc.
in different sizes. It is best to have input as SVG with transparent
background and white foreground.
To browse these SVGs i'd like to use inkview (inkscape has several
disadvantages for this).
But as inkview uses a white background i see white on white.
I downloaded inkscape-0.48.5 and compiled it and began to hack the sources.
I try to load the SVG, then change its background color and opacity (only in
memory / RAM) and then display that changed SVG.
As a first test i added in inkview.cpp in main():
Inkscape::XML::Node *nv = sp_repr_lookup_name (ss.doc->rroot,
printf("nv is %p\n", nv);
I do this quite at the end, directly before:
ss.view = sp_svg_view_widget_new (ss.doc);
It did not lead to any change, i still see white-on-white.
Basically i have some questions and it would be great if you could give me
some hints on how to patch inkview.
What i try is to change the loaded SVG document in memory and display that
changed document. Is that a good approach or could it be done better /
It would be cool to view a grey grid in the background for transparent areas.
Is there a way to achieve this?
8 years, 4 months
Website 1.3 Released
by Martin Owens
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
Full release notes as requested here:
- 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
- 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