Integration with tasker about gtalksms

[GoogleCodeExporter]

Note to self: also register these intents at openintents.org 

Original comment by [email protected] on 2 Jan 2011 at 12:30

[GoogleCodeExporter]

Change checked in, wiki page added.

Original comment by [email protected] on 3 Jan 2011 at 12:19

• Changed state: Fixed
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

oops - this hasn't been checked in yet.

florent: ISTM that these intent action strings really should be fully-qualified 
(ie, with leading com.googlecode.gtalksms), especially if we want to register 
them at openintents.org.  What I don't quite understand is why they are *not* 
currently - the leading "." in strings in the manifest should magically get 
that prefix appended.

Regardless, would you like me to re-submit this patch so that it uses 
fully-qualified intent names everywhere (and at the same time, change the 
string literals to a public static strings on the service (ie, 
MainService.ACTION_SHOW instead of the literal...)?

Original comment by [email protected] on 3 Jan 2011 at 1:26

• Changed state: Started

[GoogleCodeExporter]

Sorry I didn't see your patch.
I changing package path each time I'm making a donate version. It's the only 
way to deploy 2 versions of the application. Eclipse project add automatically 
the full path.

Original comment by [email protected] on 3 Jan 2011 at 1:30

[GoogleCodeExporter]

> Eclipse project add automatically the full path.

I don't quite understand this.  In my testing, I had Tasker use the action 
string ".GTalkSMS.SEND", and all of our code checks only for that string (and 
works).  But if eclipse is adding the package name to the intents in the 
manifest, I'd expect that to *not* work - that Tasker would have needed to use 
the fully-qualified name to find the service to send the intent to (and in that 
case, our code would have ignored it - it assumes no leading prefix).  Do you 
have any idea why that would be the case?  (Note that I only told tasker the 
intent name and that it was targeted at a service - I didn't tell it the 
package or service name to receive it)

Original comment by [email protected] on 3 Jan 2011 at 1:41

[GoogleCodeExporter]

Fixed in 1.6

Original comment by [email protected] on 4 Jan 2011 at 10:22

• Changed state: Fixed

[GoogleCodeExporter]

Holy shit this is awesome. I just realized I hadn't bought the donate version 
yet. Will gladly do so, unless you have a way for me to drop you a fiver 
separate from the market, or if you'll differentiate the donate version on 
features at some point.

Keep up the great work, both! My mind is already spinning at what I can do with 
some of this stuff... absolutely great!

Original comment by [email protected] on 6 Jan 2011 at 10:34

[GoogleCodeExporter]

Issue 63 has been merged into this issue.

Original comment by [email protected] on 27 Jan 2011 at 6:42

[GoogleCodeExporter]

Issue 35 has been merged into this issue.

Original comment by [email protected] on 27 Jan 2011 at 6:42

[GoogleCodeExporter]

Original comment by [email protected] on 25 Aug 2011 at 7:51

• Changed state: Deployed