http://growl.info/documentation/developer/introduction.php:
Growl is a system for posting notifications to users.
Growl, but for Windows: http://www.growlforwindows.com
libraries for several programming language and the documentation for the protocol it uses can be found here: http://www.growlforwindows.com/gfw/developers.aspx
Nothing as popular as Grown on mac but the standard Win32 API to do notifications is Shell_NotifyIcon. You can see a sample project here on codeproject: Adding Icons to the System Tray.
Related
I'm a newbie in OSX development.
I'm developing an app in mac which requires receiving notifications similar to the iOS APNS. I am fully aware of the Growl Framework, however many suggested that in order to avoid any future compatibility and/or support issue with Growl, using the Apple Push Notifications (applicable for Apps from Lion onwards) would be better.
Can you suggest a way on how to do this or give some important tutorial regarding this.
Thank you for your help!
Apples own documentation is the best place to start:
https://developer.apple.com/notifications/
Lots of documents there as well as videos from WWDC regarding mac notifications and sample code. In general the implementation is very similar to ios push.
I know the midiXxx API, but I saw it is currently listed under 'legacy' in msdn.
http://msdn.microsoft.com/en-us/library/windows/desktop/dd743619(v=vs.85).aspx
Is there some other API i should use to target the newer Windows versions?
Will the old API still work on Windows 7 and 8?
Thanx,
Marc
Last Friday Microsoft released a preview Windows Runtime API for MIDI. Check out the //build/ session here:
http://channel9.msdn.com/Events/Build/2014/3-548
MSDN: http://msdn.microsoft.com/en-us/library/windows/apps/dn643522.aspx
Although a preview, apps can go live and be deployed to the Windows Store. Please let us know what you like or don't like. Happy app building!
For dektop applications (non metro) you can still use the legacy API safely.
Sadly for WinRT/Metro, there is no midi support at all (see this discussion on msdn).
Hope they will change that.
Catflier is correct that there is no direct support (at the API level) for MIDI in WinRT. However, if you are wanting to have MIDI-like capabilities in your app, there are workarounds. A protocol growing in popularity is the network-based OSC (Open Sound Control). Since it is network-based, you can use that.
For example, one can use external hardware like The Missing Link which translates from MIDI to OSC. You hook up your MIDI device to The Missing Link, which then translates to OSC messages that are sent to the computer. Your app can then receive OSC messages and talk to the MIDI device. I don't have any code to show here, but I've seen demos of this working in-action.
You can see OSC in use on iOS as well with popular apps like TouchOSC.
I have a Windows desktop application which must work in collaboration with my Chrome extension.
Can I send a message to my desktop app somehow from Google Chrome extension?
Which IPC objects can I use?
I see three options:
You could use the internet. You can have a remote service that both the chrome extension and your desktop app talk to, to communicate.
You could have your desktop app have a simple server built into it so that the chrome extension can make local http requests to it to communicate with it.
Use the Google NPAPI plugin functionality to have full access to the computer. Now deprecated
These days you would use Chrome's native messaging API to send the message from your extension to a native messaging host. The latter can be a "real" executable that then passes the message on to your desktop application.
Documentation: http://developer.chrome.com/extensions/messaging#native-messaging-host
chrome extension has a native massage api to communicate to native process,
see here:
https://developer.chrome.com/apps/nativeMessaging
This almost certainly requires a custom NPAPI plugin and cannot be done with the basic extension API. NPAPI development is fairly daunting and outside my area of expertise, but feel free to read over Google's documentation on the subject.
As an alternative, perhaps you can have your desktop application poll the internals of the extension. For example, the extension's could have a file in its sandboxed filesystem where it leaves messages for the desktop application to find. This approach is suboptimal, since it requires polling instead of pushing, but it does save you the hassle of coding an NPAPI plugin.
What is the easiest way to port a win32 MIDI SysEx application (a configuration program), to MacOSX ?
The application itself is written in Qt, but I have no experience in OSX MIDI APIs. Are there good enough drop-in replacements for calls like:
midiInOpen
midiOutOpen
midiOutPrepareHeader
midiOutLongMsg
and a couple more? Is there a decent source of information for someone who has never programmed under MacOSX to develop MIDI SysEx applications? CoreAudio?
I found a great little (just one .cpp file + headers) midi library - crossplatform and all :)
It's also a great source to analyse and to learn from.. a little nugget in the whole undocumented field.
http://www.music.mcgill.ca/~gary/rtmidi/index.html
What is your development platform? If you're writing a Native Coca Application for the mac, Apple wrote a complete framework to deal with the Midi traffic named CoreMidi. The CoreMidi framework deliver the whole package of midi (include SysEx) and even extend it with network support.
I recommend having a look at Pete Goodliffe blog post of using CoreMidi for iOS devices. Although you're not developing for iOS, there is a lot of CoreMidi related information there.
There is a simple, yet brilliant, application that I use a lot on my studio named: Midi Monitor which is an open source application. I recommend having a look there too.
I need to make a small application in Ruby that will display log lines received over TCP in different colors.
What is a recommended GUI framework to use for this type of app?
I should work on Windows and Linux.
Shoes is a great lightweight GUI framework with mac, linux, and windows support.
RuGUI is a framework which aims to help building desktop applications: http://rugui.org/ and https://github.com/rugui/rugui