Hey all - I saw that you're looking for help putting together the package for the above. What kind of help do you need? I'll do what I can to hep out.
Thanks, Jim McDermott, CSM
Hi Jim,
welcome :) It would be great to have your help for Mac packaging.
The people interested in helping with it are meeting in https://chat.inkscape.org/channel/mac-dev
(right now, the server ssl certificate has expired, but the person who can fix it knows and will fix as soon as possible - if you want to grant an exception, you need to first visit https://chat.inkscape.org/, at least I have to do that first.)
Can you ask them about the current state of affairs and introduce yourself there?
Best tag them with @all, then they will get an email notification.
Maren
Am 17.12.18 um 01:03 schrieb Jim McDermott:
Hey all - I saw that you're looking for help putting together the package for the above. What kind of help do you need? I'll do what I can to hep out.
Thanks, Jim McDermott, CSM
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
hi jim, this is great news! us mac folks are behind the curve at the moment. as a user, i have been using this build: https://github.com/valerioa/Inkscape-MacOS-Curated-Build/releases .
this is a build that seems to have quartz built in. it seems to load faster than the official build. this build was introduced earlier this year and has had some discussion. imo, this is the build for mac os x. it just needs an update to the current build. i would appreciate the developers that were involved in that discussion to point you to pros and especially the cons to work out and make this the mac build for inkscape.
best, dwain
On Sun, Dec 16, 2018 at 6:35 PM Jim McDermott <jim@...3690...> wrote:
Hey all - I saw that you're looking for help putting together the package for the above. What kind of help do you need? I'll do what I can to hep out.
Thanks, Jim McDermott, CSM
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Fri, 2018-12-21 at 06:08 -0600, Dwain Alford wrote:
hi jim, this is great news! us mac folks are behind the curve at the moment. as a user, i have been using this build: https://github.com/valerioa/Inkscape-MacOS-Curated-Build/releases .
this is a build that seems to have quartz built in.
IT doesn't have quartz at all. It's a native build, it is a MacOSX Gtk2 build.
And that is the problem. It's based on Inkscape Gtk2, which is now deprecated. Which means this curated build can't be upgraded.
It's the best Mac build. The goal is that we need a replacement Mac build which uses Gtk3. The code changes that valerioa made to Gtk to get their build to work, especially for menu bars and clipboards are important to translate to Gtk3.
This is pretty serious programming. I can only help from the sidelines as I don't have a Mac (linux only).
Best Regards, Martin Owens
doctormo@...400... 9:11 AM (8 hours ago)
to me, Jim, inkscape-devel
On Fri, Dec 21, 2018 at 9:11 AM <doctormo@...400...> wrote:
On Fri, 2018-12-21 at 06:08 -0600, Dwain Alford wrote:
hi jim, this is great news! us mac folks are behind the curve at the moment. as a user, i have been using this build: https://github.com/valerioa/Inkscape-MacOS-Curated-Build/releases .
this is a build that seems to have quartz built in.
<continued>
It's the best Mac build. The goal is that we need a replacement Mac build which uses Gtk3. The code changes that valerioa made to Gtk to get their build to work, especially for menu bars and clipboards are important to translate to Gtk3.
Best Regards, Martin Owens</end>
martin, thanks for your correction regarding quartz. now that you have established that this is the best mac build and gtk3 needs to be implemented, can gtk3 be implemented without the use of quartz? if it can't, and this is the best mac build, then it stands to reason, that if valerio can't mash up his version with gtk3 without quartz, then i'm left at 0.9.92 with the only way to upgrade to the current version is if the macports upgrade is working without quartz and there is no current version without quartz built to a dmg.
ouch! unless (jim) can connect with valerio and . . . . .
best, dwain
this is a build that seems to have quartz built in.
IT doesn't have quartz at all. It's a native build, ...
folks, "quartz" is the native Gtk backend, not to be confused with XQuartz, which is an X server. On MacPorts for example, this means the "-x11 +quartz" variant of the Gtk package is the "native" version.
https://en.wikipedia.org/wiki/Quartz_(graphics_layer) https://en.wikipedia.org/wiki/XQuartz
Cheers, Thomas
thomas, thanks for the information. i have been learning much about inkscape since i began using inkscape and having a visual understanding of how the dependencies fit into the program. thanks for the information on the differences in quartz and xquartz. now i won't make that mispeak again since i now have a better understanding of the two.
according to martin, and i concur, that the version valerio is developing is the best version for mac. the official version that corresponds to valerio's version starts terminal and then starts inkscape. as a user, what is the necessity of the middle program? if it works "just" for the mac, then what would be the need to upgrade to gtk3?
and this is where it gets sticky and possibly crazy sounding. to express this and not being able to contribute to the programming really hurts me; but what i'm going to say is not meant to be mean spirited. this would need a community within the developer community to work with valerio and develop a new fork that maintains the same inkscape source code so upgrade features can be "plugged into" the source code.
i guess it would be an "inkscape sub-culture" of the "official version". security proofreaders to check for viruses and malware of all kinds before releasing "official mac only inkscape plugins". once that is resolved, along with resolving the "storage" problem, now the problem of "plugin" distribution enters the picture.
i could go on, but the bottom line is, where do you get the people to begin this chapter of the inkscape saga? i tell you all, as a user, i see the beginnings of what i propose in this discussion; and i'm really excited about the valerio version becoming the new "official mac version". i trust that the inkscape mac group will consider my "user" proposal as a possible road map as the group coalesces, hopefully they will and can work with valerio in developing "the premier industry standard svg program" for mac.
best, dwain
On Sat, Dec 22, 2018 at 2:27 AM Thomas Holder <thomas@...2024...> wrote:
this is a build that seems to have quartz built in.
IT doesn't have quartz at all. It's a native build, ...
folks, "quartz" is the native Gtk backend, not to be confused with XQuartz, which is an X server. On MacPorts for example, this means the "-x11 +quartz" variant of the Gtk package is the "native" version.
https://en.wikipedia.org/wiki/Quartz_(graphics_layer) https://en.wikipedia.org/wiki/XQuartz
Cheers, Thomas
Some of those people meet here: https://chat.inkscape.org/channel/mac-dev
They could use more support and dev-force, maybe an official meeting for determining what needs to be done and some cheering on, though.
Maren
Am 23.12.18 um 08:05 schrieb Dwain Alford:
thomas, thanks for the information. i have been learning much about inkscape since i began using inkscape and having a visual understanding of how the dependencies fit into the program. thanks for the information on the differences in quartz and xquartz. now i won't make that mispeak again since i now have a better understanding of the two.
according to martin, and i concur, that the version valerio is developing is the best version for mac. the official version that corresponds to valerio's version starts terminal and then starts inkscape. as a user, what is the necessity of the middle program? if it works "just" for the mac, then what would be the need to upgrade to gtk3?
and this is where it gets sticky and possibly crazy sounding. to express this and not being able to contribute to the programming really hurts me; but what i'm going to say is not meant to be mean spirited. this would need a community within the developer community to work with valerio and develop a new fork that maintains the same inkscape source code so upgrade features can be "plugged into" the source code.
i guess it would be an "inkscape sub-culture" of the "official version". security proofreaders to check for viruses and malware of all kinds before releasing "official mac only inkscape plugins". once that is resolved, along with resolving the "storage" problem, now the problem of "plugin" distribution enters the picture.
i could go on, but the bottom line is, where do you get the people to begin this chapter of the inkscape saga? i tell you all, as a user, i see the beginnings of what i propose in this discussion; and i'm really excited about the valerio version becoming the new "official mac version". i trust that the inkscape mac group will consider my "user" proposal as a possible road map as the group coalesces, hopefully they will and can work with valerio in developing "the premier industry standard svg program" for mac.
best, dwain
On Sat, Dec 22, 2018 at 2:27 AM Thomas Holder <thomas@...2024... mailto:thomas@...2024...> wrote:
>>> this is a build that seems to have quartz built in. >> IT doesn't have quartz at all. It's a native build, ... folks, "quartz" is the native Gtk backend, not to be confused with XQuartz, which is an X server. On MacPorts for example, this means the "-x11 +quartz" variant of the Gtk package is the "native" version. https://en.wikipedia.org/wiki/Quartz_(graphics_layer) https://en.wikipedia.org/wiki/XQuartz Cheers, Thomas
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Sun, 2018-12-23 at 18:33 +0100, Maren Hachmann wrote:
Some of those people meet here: https://chat.inkscape.org/channel/mac-dev
They could use more support and dev-force, maybe an official meeting for determining what needs to be done and some cheering on, though.
The determining might actually be "raising money for" rather than "developing", because it looks like we have way more Mac users than Mac developers. I think we should keep the options open.
Best Regards, Martin Owens
participants (5)
-
unknown＠example.com -
Dwain Alford -
Jim McDermott -
Maren Hachmann -
Thomas Holder