Spice client mac os x

Building spice client for macOS

Here is a quick recipe to rebuild a macOS SPICE client from scratch.

There are two methods, one using autotools, one using c3d/build. The autotools approach is presently complicated on macOS due to a bug in autotools and to differences between Apple and GNU tools.

Building with make and c3d/build

This approach is still experimental (as in “published today”), but it is significantly faster than autotools in the end (as in about 16 times faster).

1. Install Homebrew as follows:
2. Install the required dependencies for building:

Note that installing XQuartz is not necessary for the SPICE client, only for the SPICE streaming agent, but this ensures that all SPICE components build successfully. Also, this step is only used as a quick way to install the /usr/X11 directory. If you have that directory on your system, you can skip the brew cask install xquartzstep.

Clone the top-level directory for SPICE and go to that directory:

Tell pkg-config where to find packages installed by brew:

Make sure that you adjust the path for openssl to match what brew actually installed. The OpenSSL package is not seen by default by pkg-config because it conflicts with Apple’s own versions.

Run the actual build:

If there is no error, you should be able to run spicy:

Switching between autotools and c3d/build

You can switch this top-level directory to autotools by running the ./autogen.sh script from the top-level, and restore to c3d/build by running make gitclean.

Building using autotools

The steps are somewhat similar, but there is an additional requirement to patch the current version of autotools. This is also more likely to run into relatively mysterious errors, so make sure to check the Possible errors section below if you have a problem.

1. Install Homebrew as follows:
2. Install the required dependencies for building:
3. After verifying the version for OpenSSL installed by brew, setup
   the environment for building as follows:

Clone the spice-protocol repository and go there:

Run auto-configuration in spice-protocol (it may be a good time to take some coffee):

Build and install spice-protocol:

Clone the top-level directory for the SPICE GTK viewer, and go to
that directory:

Run the auto-configuration for spice-gtk, and go grab another coffee:

You may need to run configure manually, because the default
configuration is

Possible errors

• Dependency on Objective-C headers: The CFLAGS='-ObjC' is required because one of the keyboard mapping files includes a header that uses Objective-C syntax. Without it, you will get something like:
• Autoconf bug in error reporting: While running
  auto-configuration, you may end up with a helpful error message that looks
  something like that:

If you see this, then you need to patch autom4te as explained in this comment. You can for example run:

then search for the message # Trace with arguments, and insert the following text just above it:

In other words, you need to apply the following patch:

Once you have applied the patch, you will see the actual error that the autoconf bug was trying to report but failed to, for example:

Configuration errors. For some reason, autogen.sh may leave you with an invalid configuration if you don’t run it manually. In that case, you get this:

If you see this, simply run ./configure manually.
Forced errors for warnings: You may see an error like:

There were apparently recent changes in the Homebrew-installed jpeg-turbo , which make the version incompatible with the regular JPEG version. For now, simply remove the #warning.

In the end…

Let me conclude with a personal opinion…

On my machine, the complete build with c3d/build takes about 15 seconds for a debug build and about 30 seconds for an optimized build. With autotools, it takes roughly 3 minutes, that’s about 16 times slower.

The description of what’s required to build SPICE with c3d/build is presently about 800 lines of standard Makefile. By contrast, with autotools, it takes about 5x as much, 1303 lines for configure.ac files, 2428 lines of Makefile.am (granted, at present, building very slightly more, e.g. documentation)

So this reinforces me in an old belief of mine:

Autotools: Complex non-solutions to simple non-problems.

As far as I know, there is nothing autotools makes that make cannot do as well and faster. QED.

Источник

OSX Client

Status

A bundle is now available.

• Works with either gtk2 or gtk3
• Uses GStreamer for audio (output and input?)
• No USB support
• No smartcard support

How to build

The MacOSX client uses the jhbuild moduleset provided by the gtk-osx project. This repository contains an additional moduleset to build the needed SPICE modules. The OSX client is based on remote-viewer (as the Windows client).

Prerequisite

Before using it, you need to install XCode. I’m using XCode 4.3.3 for Lion. After installing it, I had to run the command below to setup everything as expected:

If you want to build spice-gtk from git (the default moduleset is building it from tarballs), you also need the Perl module Text::CSV. To install it you can run:

Setup

Once these prerequisite are addressed, you can download the spice-osx-build-setup.sh script and run it:

It will download the gtk-osx jhbuild moduleset using the gtk-osx-build-setup.sh script from the gtk-osx project. This in turn installs jhbuild in

/Source and creates

/.local/bin/jhbuild. It will also install

/.jhbuildrc-custom and will copy the current gtk-osx modules into

After the script runs,

/Source/spice-jhbuild will contain a jhbuildrc file. You can copy it to

/.jhbuildrc-custom and jhbuild (as setup by the

/.jhbuildrc file created by gtk-osx) will pick it automatically. Alternatively, you can copy it to

/.jhbuildrc-spice and set the JHB environment variable to ‘spice’ (or use any other prefix of your liking). You can edit this jhbuildrc file if you want to configure the location where source will be downloaded/expanded, and the location where the built binaries/libraries will be installed.

Building

/.local/bin is in your PATH, this is where the jhbuild binary is located. You can then run

This will download and build virt-viewer and all its dependencies. Once this is done, you can start remote-viewer with

If a weird build error happens while building freetype, exit jhbuild, run

and then restart jhbuild with

Bundling

The SPICE jhbuild moduleset also comes with the needed files to generate an OSX bundle for easy deployment. This uses gtk-mac-bundler from the gtk-osx project.

After building virt-viewer or virt-viewer-gtk3, make sure you have installed gtk-mac-bundler. You can then use the bundle/remote-viewer.bundle and bundle/remote-viewer-gtk3.bundle files that come with the spice-osx moduleset to generate a bundle. If you used the spice-osx-build-setup.sh, the bundle file name will be

/Source/spice-jhbuild/bundle/remote-viewer.bundle. Once it is installed, you can call

This will create a RemoteViewer.app bundle on your desktop containing everything that is needed to run the remote-viewer binary you just built on any system.

Finally, you then generate a dmg file from this bundle from the commandline using

Источник

Spark – Email App by Readdle 4+

Love your email again

Readdle Technologies Limited

Screenshots

Description

Spark is the best personal email client and a revolutionary email for teams. You will love your email again!

«Best of the App Store» — Apple
«It’s a combination of polish, simplicity, and depth» — FastCompany
«You can create an email experience that works for you» — TechCrunch

**Beautiful and Intelligent Email App**
We are building the future of email. Modern design, fast, intuitive, collaborative, seeing what’s important, automation, and truly personal experience that you love — this is what Spark stands for.

**Farewell to Busy Inbox**
Smart Inbox lets you quickly see what’s important in your inbox and clean up the rest. All new emails are smartly categorized into Personal, Notifications and Newsletters.

**Discuss email privately**
Invite teammates to discuss specific emails and threads. Ask questions, get answers, and keep everyone in the loop.

**Shared Inboxes**
Spark lets you handle an inbox together with multiple people, assign emails just like tasks, set deadlines, and track progress. No email will slip through the cracks! This feature is invaluable for small teams like info@, sales@, or support@.

**Create email together**
For the first time ever, collaborate with your teammates using a real-time editor to compose professional emails.

**Schedule emails to be sent later**
Schedule emails to be sent when your recipient is most likely to read them. It works even if your device is turned off.

**Snooze That One For Later**
Snooze an email and get back to it when the time is right. Snoozing works across all your Apple devices.

**Find Any Email In An Instant**
Powerful, natural language search makes it easy to find that email you’re looking for. Just search the way you think and let Spark do the rest.

**Get Notified About Important Emails Only**
Smart Notifications filter out the noise, letting you know when an email is important, saving you from notification overload.

**Powerful Integrations**
Integrate Spark into your workflow and take productivity to the next level. Supports Dropbox, Box, iCloud Drive, and more.

**Built-in calendar**
A full-featured calendar works right in your email to help you always be on top of your schedule. Create events easily using natural language.

**Create links to email**
Create secure links to a specific email or conversation. Share the link on Slack, Skype, CRM, or any other medium so your team can see it and collaborate around it.

**Sign Off With A Swipe**
Before you send an email, quickly swipe to choose the right signature for the occasion.

**Email with Emotion**
Quick Replies get the point across with just a tap. Love, like or acknowledge an email in an instant.

**Email Never Looked This Good**
That terrible mess in your inbox is now replaced it with a beautiful, threaded message design.

**A Truly Personal Experience**
Customize Spark to work as you do. You decide which swipes do what, what cards are shown, and how many emails you want to see.
You’ll love your email again!

Источник

Project Viewer 365 4+

Housatonic.com

• • 3,1 • Оценок: 11

• • Бесплатно
  • Включает встроенные покупки

Снимки экрана

Описание

Project Viewer 365 for Mac allows project team members to open MS Project MPP Plans from cloud locations like Google Drive. Dropbox, OneDrive, SharePoint Online, Box, Basecamp, URL Links and email attachments.

Project Viewer 365 for Mac is compatible with Microsoft Project (MPP file format) 2016, 2013, 2010, 2007, 2003 and earlier versions. The interface is intuitive making Project Viewer simple for the end users.

Free view-only MS Project views like Gantt chart, Task Sheet and Resource Sheet are available along with basic project plan sorting, filters, zooming and time scale viewing capabilities.

Additional features can be enabled by subscribing to in-app-purchase packages:

In-App Option 1: Advanced View Only

Enable advanced sorting capabilities, apply additional filter options and customize time scale
Access additional project views like Calendar View, Resource and Task Usage, View Network Diagram
View Multiple Project Reports and Print Project Info to PDF or Paper.

This in-app purchase option is offered on a yearly (1 year) basis for a price of $19.99 USD per year and works on any supported platform and devices. Purchase subscription once, use on all supported devices and platforms.

In-App Option 2: Full Editor

Create new Gantt charts and modify existing project schedules in the same intuitive way as MS Project. Save and Share your plans (MPP files) from any storage or cloud location on any Mac device with Yosemite or higher. Works with, or as an alternative to Microsoft Project.

This in-app purchase option is offered on a yearly (1 year) basis for a price of $129.99 USD per year and works on any supported platform and devices. Purchase subscription once, use on all supported devices and platforms.

Payment will be charged to iTunes Account at confirmation of purchase

Subscription automatically renews unless auto-renew is turned off at least 24-hours before the end of the current period

Account will be charged for renewal within 24-hours prior to the end of the current period, and identify the cost of the renewal

Subscriptions may be managed by the user and auto-renewal may be turned off by going to the user’s Account Settings after purchase

No cancellation of the current subscription is allowed during active subscription period

Источник