Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-platform client #22

Closed
GoogleCodeExporter opened this issue Jan 31, 2016 · 24 comments
Closed

Multi-platform client #22

GoogleCodeExporter opened this issue Jan 31, 2016 · 24 comments

Comments

@GoogleCodeExporter
Copy link

You mentioned potential future clients on other platforms.  I didn't really
see a place to "Vote" or "Pray" :D So I thought this would be as good a
place as any.

+8 on the Linux client
+2 on the Windows client

Or my preferred option:
+10 on the cross-platform client :)

If I were a developer, I'd gladly assist in getting this started.  Right
now I'm about 1/3 through school and my developer classes don't start for a
while.  So if you need any power user testing, I'd be happy to contribute
in any way I can!

Thanks!

-Chad

Original issue reported on code.google.com by curvinphone on 24 May 2010 at 9:23

@GoogleCodeExporter
Copy link
Author

The linux client is *almost* there (CCing wcauchois who was working on it, and 
I also *just* got a bluetooth 
adapter for my linux machine so I can also work on it :) ).

About multi-platform, I considered making a java client, but so many things are 
fundamentally different that it'd 
end up being 3 different apps in one - how to show notifications is different 
(Growl vs Growl for Windows or 
System Tray vs Gnome over dbus), how to store preferences is different (mac 
preferences vs registry vs gconf), 
muting audio and clipboard copying are completely platform dependent, bluetooth 
is very different (though I 
think for this specific one there's a portable library), etc.

Original comment by rdamazio@gmail.com on 24 May 2010 at 10:17

  • Added labels: OpSys-Desktop

@GoogleCodeExporter
Copy link
Author

Hi Chad,

I'm working on the Linux client, but as I am also in school somethings things 
are 
slow going -- I'm sure you understand ;).

I'm assuming your email address is just curvinphone [at] gmail.com? I'd like to 
contact you once development has progressed a little bit more, and I'm sure we 
could 
use your help testing the software!

Thanks,
Bill

Original comment by wcauch...@gmail.com on 25 May 2010 at 7:25

@GoogleCodeExporter
Copy link
Author

Hello there, I'd just like to know if there's any windows and/or linux desktop 
beta, 'cause I'd like to test your application and to report you the bugs. It 
seems 
very interesting and it would be great if you could make it work.

Thanks and good luck with this project that does not seems to be a piece of 
cake...

Original comment by areicko on 26 May 2010 at 3:08

@GoogleCodeExporter
Copy link
Author

Hi areicko!

Consider yourself added to the beta testing list :). The Linux port isn't ready 
for 
beta yet, but we're getting there... and I'll be sure to let you know.

We are not currently developing a Windows port, but we'd like to have one in 
the 
future (if we can find someone willing to work on it)!

Original comment by wcauch...@gmail.com on 27 May 2010 at 5:23

@GoogleCodeExporter
Copy link
Author

Excellent!  Yes, that is indeed my email address.  Once we have the Linux 
client I
might make a project out of seeing how I might port it to something on Windows 
(even
if it's just cygwin or something like that :D)

Thanks!

Original comment by ChadCur...@gmail.com on 27 May 2010 at 7:06

@GoogleCodeExporter
Copy link
Author

Just wanted to volunteer for the linux beta also, been anxious to contribute 
to this since I saw the app on the market a while back.

Original comment by anthony....@gmail.com on 31 May 2010 at 9:29

@GoogleCodeExporter
Copy link
Author

Since I see no reason not to promote, say, desktop-side scripting, I'm offering 
up a python script I threw together this afternoon for this purpose.

http://web.hackorp.com/~jalonso/android_notifier.py

It depends on python-bluez to get data and python-notify to send notifications 
to the screen.  It's ugly, but it's quite workable.

I'm releasing it GPLv3.

Cheers,
Jason

Original comment by jbalo...@gmail.com on 10 Jun 2010 at 9:11

@GoogleCodeExporter
Copy link
Author

Hi, I've created a java desktop client that should work at least on windows and 
linux (I don't have a mac to test it). The notification balloons are drawn 
using Java Swing, they are not too pretty on linux (tested on Linux Mint 9) but 
an implementation using SWT should fix it easily.

Here is the source code: http://dl.dropbox.com/u/1401233/MultiDroidNotifier.zip
Here is a binary: 
http://dl.dropbox.com/u/1401233/android-notifier-desktop-0.1-SNAPSHOT-assembly.z
ip

You should be able to run this binary simply by double-clicking 
android-desktop-notifier.jar or typing "java -jar android-notifier-desktop.jar" 
in console.

Java 6 is required to run this.

Original comment by lehph...@gmail.com on 7 Aug 2010 at 3:57

@GoogleCodeExporter
Copy link
Author

I've set up a project for the multi-platform client here: 
http://code.google.com/p/android-notifier-desktop/
Feel free to use it whatever you like and please provide some feedback!

Original comment by lehph...@gmail.com on 12 Aug 2010 at 4:55

@GoogleCodeExporter
Copy link
Author

@lehphyro
Nothing personal, but *ugh* Java VM.

Original comment by lahdekorpi on 12 Aug 2010 at 2:11

@GoogleCodeExporter
Copy link
Author

It's java but uses SWT so the interface is drawn natively. No swing ugliness.

Original comment by lehph...@gmail.com on 12 Aug 2010 at 4:42

@GoogleCodeExporter
Copy link
Author

I've just uploaded version 0.2 of android-notifier-desktop with support for 
Windows installers, Linux deb packages and MacOS dmg images.

Original comment by lehph...@gmail.com on 1 Sep 2010 at 4:17

@GoogleCodeExporter
Copy link
Author

A home do projeto diz que suporte a windows vai estar disponível se alguém 
resolver implementar. O android-notifier-desktop é multiplataforma e agora tem 
até instalador no Windows. O dono desse projeto não vai comentar nada nessa 
issue? Não dá pra atualizar a home falando do cliente multiplataforma? Um 
linkizinho?

Original comment by lehph...@gmail.com on 1 Sep 2010 at 2:55

@GoogleCodeExporter
Copy link
Author

O dono desse projeto tem emprego e família, e pede desculpas por não 
conseguir responder tudo rapidamente :)
(back to English)

I definitely want to support the multi-platform client. What do you think it'd 
take to bring it to feature parity with the mac one? (e.g. adding support for 
commands, having it sit on the mac menu bar / system tray / gnome panel, etc.) 
I'll definitely link to it from the project page.

Original comment by rdamazio@gmail.com on 1 Sep 2010 at 4:48

@GoogleCodeExporter
Copy link
Author

Thanks. The app already sits on the system tray, about commands, I was thinking 
the user could use something like 
http://www.growlforwindows.com/gfw/displays/scripty but I don't know exactly 
what are the use cases for this.

Growl support on mac is not very good because there is not too many libraries 
for integration with it, but I'll see what I can do.

Original comment by lehph...@gmail.com on 1 Sep 2010 at 5:41

@GoogleCodeExporter
Copy link
Author

Those are not the commands I'm talking about - I'm talking about this:

http://code.google.com/p/android-notifier/wiki/CommandsProtocol
http://code.google.com/p/android-notifier/source/detail?r=216

Original comment by rdamazio@gmail.com on 1 Sep 2010 at 5:46

@GoogleCodeExporter
Copy link
Author

Oh, these commands would be new menu items like About and Preferences? Maybe 
send a reply if the user clicks the notification balloon of a sms message?

Original comment by lehph...@gmail.com on 1 Sep 2010 at 6:50

@GoogleCodeExporter
Copy link
Author

Yes, that's the idea - you can start a phone call, send an sms, etc. from the 
menu, and I'm also planning responses to clicking on notifications, like 
answering a phone call, replying to the SMS, etc. I've just started the 
implementation, but it's looking good :)

Original comment by rdamazio@gmail.com on 1 Sep 2010 at 6:55

@GoogleCodeExporter
Copy link
Author

Cool, I will start implementing the protocol.

Original comment by lehph...@gmail.com on 1 Sep 2010 at 7:11

@GoogleCodeExporter
Copy link
Author

Please hold - it's not fully implemented on the Android side yet, and there's 
always the chance that I'll hit some road block (=design flaw) that may require 
changing the protocol. In a few more days I should be able to give you 
something that works over bluetooth, at least :)

Original comment by rdamazio@gmail.com on 1 Sep 2010 at 7:13

@GoogleCodeExporter
Copy link
Author

No problem.

Original comment by lehph...@gmail.com on 1 Sep 2010 at 7:28

@GoogleCodeExporter
Copy link
Author

@lehphyro
You could use growlnotify, the command line tool if you can't use a library.

Original comment by lahdekorpi on 2 Sep 2010 at 6:42

@GoogleCodeExporter
Copy link
Author

Assuming this doc http://growl.info/extras.php#growlnotify is up to date, 
growlnotify doesn't support callbacks. It'll be necessary if we want to reply 
sms messages clicking on growl notifications. Worse yet, neither libgrowl nor 
jgrowl support notification callback, so it'll be a bit harder to implement 
this.

Original comment by lehph...@gmail.com on 2 Sep 2010 at 1:57

@GoogleCodeExporter
Copy link
Author

Marking as fixed since this is done and working:
http://code.google.com/p/android-notifier-desktop/

Original comment by rdamazio@gmail.com on 10 Sep 2010 at 2:52

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant