Help save net neutrality! Learn more.
Close

#504 Edit Built in Status Messages

Some Future Release
open
nobody
5
2003-07-18
2003-07-14
Gallomimia
No

As you know, Fire comes ready to go out of the box with 4
Statuses: Available, Away, Busy, Invisible.

Adding statuses in addition to these is really easy.
So I've added Away, Idle, and Busy.
Now they appear below the first list.

That's kind of dumb isn't it?

Anyway, in the spirit of object oriented programming,
perhaps it would be prudent to create those ready-to-go
statuses as fully editable status items, so that you can
modify them in any way that other feature requests might
provide, as well as the things that can be edited now. They
could even be deleted. (Something other clients don't allow
that I frustratingly wish they did)

At this point I'd like to mention that I assume the status
items ARE objects in the code. Certainly how I would do it
after a couple of years of University courses in Computer
Science. Helps avoid nasty memory leaks that seem to
plague every program I've looked at on Mac OS X (Though
that might be something to do with the Quartz/Aqua
environment and not the programs themselves)

Thanks guys.

Discussion

  • Jason Townsend

    Jason Townsend - 2003-07-15

    Logged In: YES
    user_id=457177

    We can consider this for the future, but it is not a 1.0
    blocker.

     
  • Jason Townsend

    Jason Townsend - 2003-07-15
    • milestone: 277439 --> Some Future Release
     
  • Jason Townsend

    Jason Townsend - 2003-07-18
    • summary: Edit Current Status Messages --> Edit Built in Status Messages
     
  • jeva02

    jeva02 - 2005-02-26

    Logged In: YES
    user_id=1227940

    So basically, I agree. i would like to see more flexible statuses; to be able
    to make up fairly long available statuses where the status shows beside
    my name, (and not just as BRB beside my name and then my custom
    message when someone actually sends me a message) but like this:

    i.e

    jeva02 (gone shopping with a pineapple)

     

Log in to post a comment.