Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
cabbage for android
Comments
-
EDIT: In hindsight, this may be what you are actually talking about. I know a good deal of Java but have yet to make the transition to Android so Intents etc aren't yet part of my vocab
That is indeed what I was talking about
I'm having doubts about this now though...
The Intent used in the stock SMS app appears to be undocumented. It's not part of the API. It also appears to be something to do with emergency calls. I have no idea why this is invoked when you press the send button after writing an SMS. But after that Intent is invoked, the sendMessage method returns. And that's it. I'm very confused, I must admit.
('ECM', as it mentions twice, appears to stand for 'Emergency Call Mode'.)0 -
Integrating with stock would probably be doubly hard, I can't see it being designed for customisability the way a user-developed app like those given would be. Give one of those apps a try if you like so you see what I mean. Source code is available for one and probably the otherCambridgeGuy wrote: »That is indeed what I was talking about
I'm having doubts about this now though...
The Intent used in the stock SMS app appears to be undocumented. It's not part of the API. It also appears to be something to do with emergency calls. I have no idea why this is invoked when you press the send button after writing an SMS. But after that Intent is invoked, the sendMessage method returns. And that's it. I'm very confused, I must admit.
('ECM', as it mentions twice, appears to stand for 'Emergency Call Mode'.)
On the subject of SMSDroid. I've had a look at how it works. When you select "Send Message" or "Reply", the option to select how to reply pops up as above but you do not type the message within SMSDroid. This means you'll still need a GUI. To allow your app to be an option you would need to implement an Intent filter I assume?0 -
-
-
-
Advertisement
-
Good point. But in your opinion, what seems more inelegant:CambridgeGuy wrote: »EDIT: Oh, I see how SMSDroid is doing it now. It doesn't actually let you write the message. It just lets you press a button that invokes an Intent to write a message, and this is intercepted by whatever SMS app you have on your phone. In my case, the stock app.
Integrating with SMSDroid wouldn't be hard to do, in this case. But, unless I'm missing something, it seems like a pretty inelegant solution – I still have to open a second app, an app which is separate from the one I'd normally use to write the SMS. To be honest, as a user, I'd rather just stick with the regular SMS app + a standalone Cabbage.
(a) Having it the way it currently is, with a separate stock app and Cabbage app. Open the message in the messaging app. If you wish to reply using cabbage, you exit the messaging app (remembering who actually text you!), open cabbage, choose the recipient, type your text and send, then repeat every time you get a new message.
(b) WebSMS' method. You choose what method to reply to from a menu. Open the message in the messaging app, press reply, choose your reply method, send text and then it automatically returns to WebSMS?
I guess it depends on how much you use Webtexts. I clear my 250 a month every month without fail so I would prefer a more integrated setup. Plus, I understand this is opensource but from a business perspective, don't K2 messenger and cabbage already cater for solution A quite effectively? Just my 2c
EDIT: I need to speed up my replys best of luck, think it over (and look at the WebSMS connector solution! It could really make life easier) 0 -
Good point. But in your opinion, what seems more inelegant:
(a) Having it the way it currently is, with a separate stock app and Cabbage app. Open the message in the messaging app. If you wish to reply using cabbage, you exit the messaging app (remembering who actually text you!), open cabbage, choose the recipient, type your text and send, then repeat every time you get a new message.
(b) WebSMS' method. You choose what method to reply to from a menu. Open the message in the messaging app, press reply, choose your reply method, send text and then it automatically returns to WebSMS?
I guess it depends on how much you use Webtexts. I clear my 250 a month every month without fail so I would prefer a more integrated setup. Plus, I understand this is opensource but from a business perspective, don't K2 messenger and cabbage already cater for solution A quite effectively? Just my 2c
EDIT: I need to speed up my replys best of luck, think it over (and look at the WebSMS connector solution! It could really make life easier)
I guess (a) has its benefits. I was just kinda put off by the fact that SMSDroid can't be used to replace the stock SMS app. They *have* to coexist.
I'm aware that my app is, currently, just replicating the fuctionality of the existing Cabbage app. But there's still some good reason for doing this:
1) Cabbage for Android is buggy. When adding messages to your phone's messages database, it adds an open bracket to the number you sent the message to i.e. sending a message to 0851234567 will result in it being stored as (0851234567. This is fine on some phones, but it causes problems on others.
2) On some phones, the keyboard gets in the way of the message editor box, making it almost impossible to write messages.
3) Cabbage isn't open source, so these desirable new features cannot be added. If I make an open source version of the app, I or anyone else can add whatever extra features that may be desired.
4) Cabbage doesn't let you change the location of the sending scripts server. My app does.
5) The 'Clear' button is right next to the 'Send SMS' button. It's easy to miss when you're aiming for the send button; on many occasions I've cleared the message I just wrote but hadn't yet sent.
6) A simple project like this is a handy introduction to Android programming for a n00b like me 0 -
Makes perfect sense. I'll be attempting a similarly small project over the Christmas break if i get the time at all, which is unlikelyCambridgeGuy wrote: »I guess (a) has its benefits. I was just kinda put off by the fact that SMSDroid can't be used to replace the stock SMS app. They *have* to coexist.
I'm aware that my app is, currently, just replicating the fuctionality of the existing Cabbage app. But there's still some good reason for doing this:
1) Cabbage for Android is buggy. When adding messages to your phone's messages database, it adds an open bracket to the number you sent the message to i.e. sending a message to 0851234567 will result in it being stored as (0851234567. This is fine on some phones, but it causes problems on others.
2) On some phones, the keyboard gets in the way of the message editor box, making it almost impossible to write messages.
3) Cabbage isn't open source, so these desirable new features cannot be added. If I make an open source version of the app, I or anyone else can add whatever extra features that may be desired.
4) Cabbage doesn't let you change the location of the sending scripts server. My app does.
5) The 'Clear' button is right next to the 'Send SMS' button. It's easy to miss when you're aiming for the send button; on many occasions I've cleared the message I just wrote but hadn't yet sent.
6) A simple project like this is a handy introduction to Android programming for a n00b like me
Well, perhaps you could add the intent filter as an aside, but keep the app able to run on its own (similar to WebSMS). The stock HTC app won't pickup on this intent and will only allow you to reply within that app, but for people like me who use webtext often, we could use SMSDroid or a similar app. Cater for both markets.
Of course, as you said, the GUI has to be sorted first so enjoy that. But please consider adding the intent at a later data (preferably asap). Since it's to be open source I may even attempt it myself if you don't get the chance (so make sure that code is well commented! ) 0 -
Makes perfect sense. I'll be attempting a similarly small project over the Christmas break if i get the time at all, which is unlikely
Well, perhaps you could add the intent filter as an aside, but keep the app able to run on its own (similar to WebSMS). The stock HTC app won't pickup on this intent and will only allow you to reply within that app, but for people like me who use webtext often, we could use SMSDroid or a similar app. Cater for both markets.
Of course, as you said, the GUI has to be sorted first so enjoy that. But please consider adding the intent at a later data (preferably asap). Since it's to be open source I may even attempt it myself if you don't get the chance (so make sure that code is well commented! )
I'll definitely look into it if/when I get this contact picker sorted. (The app is otherwise finished, if you don't mind typing the number of the recipient in by hand!)
I can't make any promises about when exactly this'll be done, but I'll keep this thread up to date with progress.0 -
-
Advertisement
-
-
-
-
-
-
-
-
-
-
-
Advertisement
-
-
-
-
-
-
-
-
-
-
Advertisement
-
Advertisement