I knew when I wrote it that it didn't match iChat's, but having a dynamic emoticon menu of any sort was a vast improvement to just trying to remember what to type (as was the case prior.) I'm hoping to get to it at some point, so feedback is of course welcome.
A request for a better smiley menu in 1.0.
I'm not upset and I''m not going to ignore the thread
I knew when I wrote it that it didn't match iChat's, but having a dynamic emoticon menu of any sort was a vast improvement to just trying to remember what to type (as was the case prior.) I'm hoping to get to it at some point, so feedback is of course welcome.
I knew when I wrote it that it didn't match iChat's, but having a dynamic emoticon menu of any sort was a vast improvement to just trying to remember what to type (as was the case prior.) I'm hoping to get to it at some point, so feedback is of course welcome.
Try my software!
#define ADIUMX pimp //by me
#define QUESTION ((2b) || (!2b))
Have you hugged a programmer today?
#define ADIUMX pimp //by me
#define QUESTION ((2b) || (!2b))
Have you hugged a programmer today?
-
Crypt
- Cocoaforge Admin
- Posts: 491
- Joined: Sun May 15, 2005 6:16 pm
- Location: Brooklyn, New York
- Contact:
hmm dunno if you will like this but what about something like http://amendmentapp.com/ or just one of those automatic spellers where as your typing the word a list underneath shows up with possible endings for what word your trying to type except for emoticons. For instance :- (then the following would be displayed: ( ) X ! o ) It would also be an option to have something like that so it wouldn't if a user doesn't want it enabled they can just turn it off or it's off by default.
"Bite my shiny metal ass!"
- Bender
adiumx DOT com MOTHA F**KA!
- Bender
adiumx DOT com MOTHA F**KA!
We can cut that down dramatically (in some cases) by picking only the emoticons packs that match the current protocol. The rest of the packs can still live in the "regular" menu (what we have now).bgannin wrote:I was just saying that iChat has like 20 emoticons overall, while Adium has potentially tons of them because of emoticonsets.
This may work in some cases, but I can see it being more problematic. One reason would be several services don't have emoticon packs that specify for them at all AFAIK but more importantly it creates an odd dependency for feature activation that the user has to somehow intuit (i.e., "what do I have to do to get the 'spiffy' menu instead of this other one I don't like - where's the preference?")ofri wrote:We can cut that down dramatically (in some cases) by picking only the emoticons packs that match the current protocol. The rest of the packs can still live in the "regular" menu (what we have now).bgannin wrote:I was just saying that iChat has like 20 emoticons overall, while Adium has potentially tons of them because of emoticonsets.
Try my software!
#define ADIUMX pimp //by me
#define QUESTION ((2b) || (!2b))
Have you hugged a programmer today?
#define ADIUMX pimp //by me
#define QUESTION ((2b) || (!2b))
Have you hugged a programmer today?
-
Fonzie
The problem we've got is that navigating tons of enabled packs via the system suggested isn't that easy.
My thoughts on this would be a way to only display one emoticon pack with a sort of menu of some kind to show others.
Something like...
Then once you click on one of the other menus, that expands that pack, and it makes the current pack itty bitty.
Thoughts?
My thoughts on this would be a way to only display one emoticon pack with a sort of menu of some kind to show others.
Something like...
Code: Select all
--------------------
| |
| EMOTICONS BE HERE |
| |
| |
| |
--------------------
| Emoticon pack 2 |
--------------------
| Emoticon pack 3 |
--------------------
| Emoticon pack 4 |
--------------------
| Emoticon pack 5 |
--------------------
Thoughts?
-
Fonzie
-
djbsquared
- Cocoaforge Admin
- Posts: 248
- Joined: Thu Dec 02, 2004 6:29 am
- Location: West Bloomfield/East Lansing
What you have there wouldn't really work in a menu, the way people expect menus to act on OS X -- i.e. be accessible only through hover actions.
If we were to do that, it wouldn't be so much a menu as some sort of popup window, that activated upon clicking some sort of button in the UI (perhaps something similar to what iChat has?)
This would also solve the issue of us having to use strange APIs, since we wouldn't actually be in a menu anymore.
We currently have Insert Emoticon menus in the contextual menu for the input box and the Edit menu. Those would have to either go away or continue using the current scheme.
It's a decent solution, but it's definitely not a menu.
If we were to do that, it wouldn't be so much a menu as some sort of popup window, that activated upon clicking some sort of button in the UI (perhaps something similar to what iChat has?)
This would also solve the issue of us having to use strange APIs, since we wouldn't actually be in a menu anymore.
We currently have Insert Emoticon menus in the contextual menu for the input box and the Edit menu. Those would have to either go away or continue using the current scheme.
It's a decent solution, but it's definitely not a menu.