Crashing

[cc]

  Lol, "try a different operating system" that's funny. I think I will likely go to my grave a Mac User...

Not only would I be needing to learn Inkscape, (which I consider having a slight advantage coming with as many years using Adobe products as I am on a Mac. For me it's learning HOW & WHERE to do the same things in Inkscape that I CAN already do in Illustrator.) I would also need to learn the installation and BEHIND the scenes, INSIDE a NEW OS AND I'd also have to learn a NEW OS itself!!? I'm looking to get up and going on Inkscape asap... going to a totally new OS is like going backward, puts me in a huge TIME disadvantage & much behind the learning curve! I only know as much as I do regarding the Mac because of the YEARS I've put in using it... NOT because I LOVE knowing the "How To's" not really my thing, I honestly just want to go and DESIGN... How incredibly daunting! And I think Apple understands this about its users, (or at least the ORIGINAL Users) they are so much less interested in the mechanics of the machine, they just want it to work as they imagine it can, we're not Technically advanced regarding the INNER WORKINGS of the computer. Hence APPLE DOES NOT TRUST us to go digging around imperative files and folders WE KNOW they don't, it's not really unknown to us & it's somewhat comforting to know if we don't go into the DARK Hidden areas we really can't "break" it beyond repair to a point of no return. I think I will ever so graciously say No Thank You, & stay with my MacOS!

AH, sorry my misunderstanding, I thought you meant for me to follow the installation instructions from the GitHub,Inc. site, where the ONLY installation instructions are for LINUX. >> https://github.com/wout/Inkscape-OUTPUT-PRO

-----------------------------------------------------------------------------------------------------------
"Output Pro

An extension to export print-ready documents from Inkscape

Introduction

With this extension you will be able to export your Inkscape documents into a variety of formats and colormodes. As it initial and main goal,Inkscape Output Pro export into the CMYK colormode, compatible with the press and graphic industry standards.

It is possible to use specific ICC profiles, set other colormodes than RGB and CMYK, like Grayscale and Lab, set specific JPEG configurations, insert pre-press marks and even more.

Installation

Linux

First, make sure you have Libcanberra and PyQt4 installed

sudo apt install libcanberra-gtk-module libcanberra-gtk3-module
sudo apt install python-qt4
The copy outputpro.inx, outputpro.py and the outputpro directory to:

/usr/share/inkscape/extensions
If you don't have root access or only want the files to be available to the current user:

<YOUR HOME DIR>/.config/inkscape/extensions
Note:

I'm on elementary OS Juno and I had to install gtk2-engines-pixbuf to get rid of an error message after exporting:

sudo apt install gtk2-engines-pixbuf
This might be true for all Ubuntu based distros as well.

Windows

This might work, but has not been tested yet. To-do.

macOS

To-do.

Important

As the orignal author abandoned the project. It is my intention to keep it working in recent versions of Inkscape.

Credits

The Output Pro extension was originally written by Jonatã Bolzan.

License

Output Pro is licensed under the terms of the GNU License."
-----------------------------------------------------------------------------------------------------------


Going this route: "Inkscape Preferences > System > User Extensions" shows this path: /Users/cc.macbookpro/.config/inkscape/extensions

And I must emphasize this... NO, there IS NO "SAFE" way for a Mac User to access this portion: .config/inkscape/extensions.

From .config on, this is all hidden. We users are NOT meant to go in there for reasons stated prior. Plus if a user knows only just a tad less than I know about using Terminal they will never find it. Many Mac Users have never heard of TERMINAL, it was years before I had. There's really not much if ANYTHING we (as average users, not talking about those who are savvy enough, knowledge-wise regarding the mechanical workings of the Mac) would ever go in that area for and it's a bit frightening for us to mess with Terminal --and the ABYSS of the UN-KNOWN behind there. Seriously!

The only 'SAFER' place I can imagine placing an extensions addon folder is this way, where I originally thought these needed to go, but Moini said it was not the correct folder, because the Inkscape developer imperative files are kept here, perhaps these folders could be switched so we Mac Users could not access the Inkscape developer imperative files behind the .config? (See Screen Shot):  MacintoshHD > Applications > Inkscape.app > Contents > Resources > share > inkscape > extensions

Trust me, many Mac users don't even know how to access an applications package: "CONTENTS" & beyond, as this is somewhat hidden but this IS accessible for Mac users without using Terminal. It's just a matter of going: MacintoshHD > Applications > Inkscape.app  THEN clicking to highlight Inkscape.app, & using 2 finger click (which = a right click) & scroll down to: "Show Package Contents" from there you may access Contents > Resources > share > inkscape > extensions

Hope that's helpful?

[Moini]

Yeah, sorry about that... Accessing that folder is safe, though. It's your personal configuration for Inkscape. If you break something inside, you just empty the folder, and it will come back with new preferences. There's nothing unsafe about it except for your operating system's judgement about your abilities. I would trust you to put files into that folder.

[brynn]

What would happen if you searched for

/Users/cc.macbookpro/.config/inkscape/extensions

using your file manager?  In Windows, it opens that location, and the user can paste in the needed contents (INX and PY files).  It doesn't unhide the location, so it remains hidden and safe, but the user can still install the extension.

I've never tried it, but I doubt if it would allow you to delete something out of that file.  But it does allow you to paste something in.

Maybe it works like that on Macs too??

Or else, another option on Windows is to unhide the area temporarily, and hide it back again afterwards.  Is that possible on a Mac?

Edit
You could still install your extension in the program files (what you refer to as "Inkscape developer imperative files").  It's just that the next time you upgrade Inkscape, you'll have to install the extension again.

[Moini]

Putting extensions into the .dmg file is even harder, if not impossible, Brynn.

[brynn]

Sorry, you lost me there.  ??

I was explaining how Windows handles the hidden files, and asking if Mac offers something similar.  Nothing to do with DMG file, at least that I know of.

[Moini]

I understood that in your afterthought, you were suggesting installing into the program's installation directory, where stock extensions live, as an alternative, if the profile folder can't be found. However, this is even harder to do on a Mac, as the program is kept in a special container called dmg.

[GANGUS]

The Extensions folder is not really ‘hidden’ in Inkscape.
It’s inside the Inscape package file.

If the Mac user uses the above method as ‘cc’ mentions (Right or control-click the Inkscape Icon) and do the show package contents command) and follow this path you will find the installed Extensions folder for the Inkscape version you have.

Inkscape 0.xx.xx(whatever version)/Contents/Resources/Share/inkscape/Extensions.

This is where you could install (a simple drag and drop) the INX and PY files.
Restart Inkscape and see if they work by looking in your Inscape Extensions drop down menu.

BTW .dmg files are the equivalent ISO files on a Windows System.
Usually used as an installer tool and seen buy by the computer as a tiny disk drive and can be ‘mounted’ and  ‘ejected’ just as a disk drive can be also after the installation is done.
Inside the dmg there is a ‘script’ file that does the installing using all the necessary files included.

If you wanted to see inside of a .dmg file you could use a shareware file called 'Pacifist'.
I think you can even edit the dmgs' by paying for the program, although unless you are a developer et-al you probably would not need that.

I trust that some of this contributes to the thread.
Thanks

[Moini]

This is where you could install (a simple drag and drop) the INX and PY files.

Does that folder correspond to:

a) the folder inside the dmg file with all the stock extensions in it (so *in* the dmg file) or
b) the folder that is for custom extensions (in the user's home directory)

?

If a), then I'd strongly discourage doing this.
If b) - great! We need that kind of instructions.

Can you clarify, Gangus?

[brynn]

However, this is even harder to do on a Mac, as the program is kept in a special container called dmg.

Oohh ok.  I thought DMG was the file format.  I didn't know there was a folder called "dmg".

Yes, GANGUS, if you could help to reassure cc about installing the extension in the apparently hidden user extension folder (not the program folder which I've just learned is called "dmg"), that would be great!

To be honest, this is the first time I've heard (a) that the user folder for extensions is hidden in Macs, and (b) that someone doesn't believe us that it's safe to access it anyway.  So I'm at a loss to help.

[GANGUS]

Quotes from Moini

“Does that folder correspond to:”
“a) the folder inside the dmg file with all the stock extensions in it (so *in* the dmg file) or”
   a) Yes, the folder that is/was inside the dmg installer file.
“b) the folder that is for custom extensions (in the user's home directory)”
   b) Yes, there IS another different folder that has the Users custom extensions, but it is a hidden file.
   
Showing hidden files on a Mac (since the release of Sierra MacOS 10.12.6) is actually quite easy now,
It does not show on the Desktop but it shows inside of any windows.
just do a CMD + SHIFT + .  (that’s a period at the end) Do the same command again to re-hide them.
Very handy.

The path for the custom extensions installs on a Mac is; …
HardDrive/Users/your-name/.config/extensions
The little dot in front of ‘config’ file indicates a hidden file on a Mac.

Installing the INX & PY files in either extension folder seems to work here, but it’s probably better to install any added extensions in the users personal folder so that if a new version of Inscape is installed later, your added extensions will be available with the newer version.

Now you will be able to access that hidden extension folder using the path indicated above and do your drags and drops.
There’a another involved way using the Terminal but mistakes made using the Terminal can be disastrous.

The hidden path above and a host of other paths where one can better understand the inner workings of Inkscape are easily accessible in Inkscapes preferences. ie; edit/Preferences/System
I trust we are all aware of this.

[GANGUS]

@brynn,
“Oohh ok.  I thought DMG was the file format.  I didn't know there was a folder called "dmg”.”

A DMG file is a mountable disk image created in Mac OS X. It contains raw block data typically compressed and sometimes encrypted. DMG files are commonly used for OS X software installers that are downloaded from the Internet and mounts as a virtual disk on the desktop when opened.
Typically, a Mac user would double-click the DMG and there will be an Installer inside to double click (again) on.
The installation would then proceed. Occasionally, there are additional things required with all new new security additions.

“Yes, GANGUS, if you could help to reassure cc about installing the extension in the apparently hidden user extension folder (not the program folder which I've just learned is called "dmg"), that would be great!”

Yes, it’s quite safe to Install things with a drag and drop, but the typical (shall we say) Casual Home User may feel like it is a big deal the first time, where it really is not.

There’s really not much difference between PC’s and Mac’s, just some different words for the same things.

[Moini]

And even less difference to Linux, after all, it's all Unix. But Linux users are generally even more courageous/educated about computer matters than macOS and Windows users.

Thank you for the text, Gangus. May we use that (or parts of it) on the Inkscape website, in the FAQ?

[GANGUS]

Yes, Unix is the birth place of all of it.
I doubt that I could spend too much time in a Linux environment.
Typing commands and long paths all day to do almost anything.
I guess if you need precision, it’s the place to be though.

Yes, anything I share here, is available to all.

[Moini]

If you only knew I'm not typing commands all day. It's just a normal desktop, with icons to click on.

However, the terminal is easily available, and sometimes it's faster than clicking around until you get to the thing you need (and, of course, I do a lot of things that are probably quite different from what you need to do, like using version control, or testing and debugging scripts, which only work on the command line - but there's no difference to Win or Mac for those).

For browsing, email, drawing and other basic needs, there isn't much of a difference, it's all graphical.

Thank you for giving permission to use that bit of info about how to find the hidden folders on a current Mac, Gangus! This will no doubt be very helpful, we can then easily refer people to it, too.

@Brynn: I'll integrate that into the FAQ.

[brynn]

@Brynn: I'll integrate that into the FAQ.

Sounds good.  I didn't even realize there was an issue with hidden files in Macs, until now.

[cc]

@Moini: "If you break something inside, you just empty the folder, and it will come back with new preferences." Ah, that's good information to know. TY

@Brynn: "What would happen if you searched for /Users/cc.macbookpro/.config/inkscape/extensions"
Unless the folders are UNnhidden you will not see this path beyond the hidden .config so nothing really.

I also got a bit lost after much of this... but per .dmg file/folder --(further down Gangus explains it well). Know they're not meant to be "opened" as such, more like an extraction for the Program/App to 'propagate' itself on to the Mac.

@Gangus: "The Extensions folder is not really ‘hidden’ in Inkscape. It’s inside the Inscape package file." --Just to clarify I wasn't actually referring to hidden areas in INKSCAPE, Per se just Hidden areas past the .config folders on a MAC.

As for the path to the Extensions within the Package Contents, (Right or control-click the Inkscape Icon) --Moini had earlier in this conversation mentioned this is not the Extensions folder were meant to use.

Past that you've really lost me, do you mean for the Inkscape Developers to drag & drop INX and PY files there... (Sorry I don't even know what INX and PY files are...)

Also THANKS for the tip on how to access hidden files SANS Terminal... I hadn't known the: CMD + SHIFT + .(period) trick. That IS handy... much more so then the Terminal Command, which IS how I have accessed hidden files.

What I was attempting to explain was that in all the years of being on a Mac (& from my personal experience and usage) going into HIDDEN Files is not something commonly, often done, NOR something that's often been necessary TO DO. It's why they're hidden from us.

[brynn]

@Brynn: "What would happen if you searched for /Users/cc.macbookpro/.config/inkscape/extensions"
Unless the folders are UNnhidden you will not see this path beyond the hidden .config so nothing really.

I would have thought that to be the case in Windows too.  So I never had tried it.  But once someone told me about it, I tried, and it does work.  That's why I thought it might work for Macs.

Apparently, at least in Windows, hiding those folders means to not show them in the file manager.  It doesn't mean make them completely inaccessible.  If they don't show in the file manager, then an inexperienced user can't stumble on them and accidentally change something.  I guess hiding them is meant to prevent accidents, but if a user specifically searches for a hidden file or folder, that's not an accident.  So access is allowed.

I don't know, but maybe it's the same for Macs?

Past that you've really lost me, do you mean for the Inkscape Developers to drag & drop INX and PY files there... (Sorry I don't even know what INX and PY files are...)

I think he means that you can install the extension by drag and drop.  I would guess copy/paste would work as well.  You can unhide the hidden files temporarily, using the key shortcut he gave, drop the files in, and hide them again.

If you had read the instructions (for installing extensions) that I've given you at least a couple of times now, you would know what they are.  They are the files which need to be placed in the Inkscape user directory extensions folder.  If they aren't there (or they're inside a folder in the extensions folder) the extension won't really be installed, and you won't see it in the menu.

Meanwhile, Moini has updated the faq with info from GANGUS, with a safe way to install extensions on Macs.  Hhmm, it doesn't look like she's done it yet.  But when she does, you'll see it here:  https://inkscape.org/learn/faq/#how-install-new-extensions-palettes-document-templates-symbol-sets-icon-sets-etc

[cc]

So I again attempted to search: /Users/cc.macbookpro/.config/inkscape/extensions
but now two different ways, first in 'FINDER' & second using 'SPOTLIGHT', I was wrong. You can find the path via Spotlight, though it's deceiving & looks like it's found nothing, except YOU see the path at the bottom. (See attached pics.) The top search is in Finder which displays '0', no results, you will not find it via this search. The bottom is Spotlight where you see an empty folder; BUT also the path getting to the empty extensions folder. So you were right Brynn, depending on how you search, you CAN find it.

Yes, uh huh I DO know that you can install by Drag and Drop into hidden folders. I've said here that I HAVE DONE SO, but I've done so by Unhiding the folders via "Terminal Commands".

"If you had read the instructions (for installing extensions) that I've given you at least a couple of times now, you would know what they are.  They are the files which need to be placed in the Inkscape user directory extensions folder.  If they aren't there (or they're inside a folder in the extensions folder) the extension won't really be installed, and you won't see it in the menu."

Lol, I HAVE INDEED read your instructions... every single time. What I am saying... what's been confusing for me, that I must clearly reiterate; is that going into HIDDEN Files is not something commonly, often done. NOR something that's often been necessary TO DO.

I myself, am not exactly a casual home user. I've been on a MAC (& again ONLY a Mac) professionally for Design since the Adobe programs were: "Abobe '88"; so I just may be an 'AVERAGE user'. And although I have gone into Hidden Files in the PAST when necessary, VIA Terminal Commands I've not done so often. Still, I am not very comfortable going into the hidden area IF I don't HAVE to. Simply because as a Designer I feel I'm not as knowledgeable with the 'behind' the scenes and workings of a computer. Also, from my experience when I've called for Apple support, they do try to deter you from accessing hidden areas for possible mishaps. But who knows with the changes in Sierra MacOS 10.12.6 with just a CMD + SHIFT + .  (period), perhaps this is changing? Idk?

[brynn]

That's interesting!  Maybe Moini can use that info when she edits the faq info.

On the positive side, this discussion has triggered some brief discussion with developers about this issue.  I don't know how far it will go.  But we will certainly come up with instructions providing the safest way to install extensions on a Mac.

On the less than positive side, as you've probaby noticed, the Inkscape project has lately had difficulty finding people who can package Inkscape for Macs.  So until we can find someone who wants to do it on a regular basis, we won't see current versions of Inkscape for Macs - at least not with a simple installation method.  For pros who can compile it, or those who can figure out MacPorts, yes, Inkscape will remain available.  But for most Mac users, some developers want to stop advertising the fact that Inkscape is available for Macs. 

So it is a serious issue indeed.  I hope we can find some people who can do this for us, but it doesn't look good at the moment.

[cc]

NOOOOOOO! Oh no.... and with more and more (mac) users looking for alternatives to the major Vector software player --Adobe Illustrator. I really do hope this is not the end of the road for Mac and Inkscape. 

[brynn]

Oh, well I didn't mean to imply it would be the end of the road.  When I first started using Inkscape (~11 years ago), the devs were having trouble finding people to package Inkscape for Windows, while Mac support was better (as far as installation packages).  Now it's the other way around.  So it fluctuates over time.

Since Inkscape is made primarily to be used with Linux, Linux users will never have to worry about this.  But for Windows and Mac, things may always be in a bit of flux, in this way.

But heck, someone could show up tomorrow who wants to help with packaging for Mac.  We shouldn't give up hope!  And we shouldn't stop trying to get the word out, and try to recruit programmers (or packagers, in this case).

[cc]

Ah whew, yes agreed... so I take it you Design on Linux?

Wow, I'm surprised that Windows users were in the same situation. I am and will be hopeful regarding recruitment of programmers (or packagers, lol, unfortunately, I don't know the difference between the 2). And those developers will want to continue advertising that Inkscape is available for Mac.

Honestly, I do think there are many more out there looking to 'jump ship' from the SUBSCRIPTION based application. I know for me and others like me who have been LONG time Adobe Users, going to sub base was a bit of a deal breaker and kind of a last straw. So perhaps more Mac programmer/packagers will feel the same! (*AND include CMYK output within the program itself!)
 

[brynn]

Hah, I wouldn't exactly call myself a "designer".  I use Inkscape as a hobby, and find it a stretch to think of myself as an artist.  Mostly I just enjoy the creative process.  Inkscape makes that very easy and fun.  And it's a great community to be a part of.

I've been a Windows user since I got my first computer in the late 90s.  But with Microsoft's decision to make Windows cloud-based, starting with whatever version comes after Windows 10, I've decided to switch to Linux.  I've started the process to make the switch, but I keep getting interrupted with issues related to running this website.  But eventually I'll get there.

[brynn]

Hey, good news!

I just read a message giving info about the hackfest that has just concluded.  You'll appreciate a few of the items reported.  To quote:

* For Mac OS/X, we want to make initial steps by 1.0

  Our first objective will be packaging a demo app.  This could be a
  scripted build of gtk3-demo-application, for example; that way if
  there are problems, it will be more familiar to upstream.  If this can
  be achieved by beta, we may be able to invest more to getting a
  package ready by 1.0.

  A follow up would be to convert the raw build script into equivalent
  CMake commands.  This should reveal lessons on how to do this for
  Inkscape.

  Additional steps were scoped out, and will need further definition in
  gitlab.  The master bug for this should probably move to the "Big
  Ideas" tracker at this point. [my note - "Big Ideas" tracker doesn't exist yet, but creating it is another item in this list]

* For CMYK, Color Management, and PDF/Print, we have a detailed plan of
  development tasks needed.

  This will be published in the "Big Ideas" gitlab tracker.

* We will establish Paypal buttons for dedicated funds to start
  collection of donations for several targeted efforts:

  A. Native Mac OS/X Packaging
  B. Color Management
  C. Internships promoting diversity (e.g. Outreachy)

[GANGUS]

That sounds encouraging indeed.
At least they are still thinking about us Mac users.
I guess a donation could go a long way here too.
To think that people should have to spend there time doing it all for free is inconsiderate perhaps.

I recall that Tim Sheridan (tghs) had played a part in getting Inkscape 0.92.2 packaged for Mac users.
https://inkscape.org/~tghs/
I wonder what happened to his support.

Thanks Brynn for sharing the good news.