YesNoOk
avatar

List of features, you shouldn't request (Read 8294 times)

Started by Nightwish, June 23, 2005, 15:44:20

0 Members and 1 Guest are viewing this.
New #1
List of features, you shouldn't request |
June 23, 2005, 15:44:20
This is a brief list of features, which probably won't ever make it into tabSRMM, because of either technical or personal (means: I don't like them) reasons.

  • Flash avatars - plugin available, search the addons section at miranda-im.org.
  • Single message mode
  • animated smileys (supported by both emoticon plugins anyway)
  • Background picture for the message history or message input field.
  • Layered skinning engine (like clist_modern) or any more "advanced" skinning.
  • skinning in aero mode
  • skinning or any other advanced layout for the group chat history.

For TabSRMM version 3, you can view the development roadmap containing a list of planned and already implemented features. Anything NOT listed on that page will most likely not be done for version 3.

There is no road map for the life after v3 and no guarantee that such a thing will ever exist.
__
Every program has at least one bug and can be shortened by at least one instruction -- from which, by induction, one can deduce that every program can be reduced to a single instruction that doesn't work.
My SMF-based forum fork
Last Edit: January 09, 2010, 04:49:38 by Nightwish
#2
Re: List of features, you shouldn't request |
July 18, 2005, 20:54:34
  • Splitting messages
  • Ability to disable/enable toolbar buttons
Last Edit: July 24, 2005, 10:03:26 by nowotny
#3
Re: List of features, you shouldn't request |
July 28, 2005, 05:34:10
Hi, Could you please explain why I shouldn't request Splitting messages feature?
It'll be very convenient.  I tired to split messages by hands (while sending long off-line messages) :'(
#4
Re: List of features, you shouldn't request |
July 28, 2005, 06:25:24
Hi, Could you please explain why I shouldn't request Splitting messages feature?
It'll be very convenient.  I tired to split messages by hands (while sending long off-line messages) :'(

Use the search. It has been discussed a lot. Splitting messages by the message window is just plain wrong. End of discussion.
__
Every program has at least one bug and can be shortened by at least one instruction -- from which, by induction, one can deduce that every program can be reduced to a single instruction that doesn't work.
My SMF-based forum fork
#5
Re: List of features, you shouldn't request |
August 26, 2005, 17:18:35
mann
why i cant ask for send on doubel enter
its much easier to send message like this.. :(
#6
Re: List of features, you shouldn't request |
August 27, 2005, 21:20:07
mann
why i cant ask for send on doubel enter
its much easier to send message like this.. :(
**speaking for Nightwish** :D

There are mainly technical reasons through changes in the RichEdit Input
#7
Re: List of features, you shouldn't request |
August 27, 2005, 21:44:03
mann
why i cant ask for send on doubel enter
its much easier to send message like this.. :(
Either get used to send messages in one of 10 different ways, or don't use tabsrmm. Sorry, double enter is an absolute NO. Now and forever.
__
Every program has at least one bug and can be shortened by at least one instruction -- from which, by induction, one can deduce that every program can be reduced to a single instruction that doesn't work.
My SMF-based forum fork
#8
Re: List of features, you shouldn't request |
December 14, 2005, 10:16:34
#9
Re: List of features, you shouldn't request |
April 26, 2006, 18:37:19
does "Single message mode" means "no tabs, each conversation in own window" ?
because i would like to request this feature (the second one :) )
#10
Re: List of features, you shouldn't request |
April 26, 2006, 19:31:28
does "Single message mode" means "no tabs, each conversation in own window" ?
because i would like to request this feature (the second one :) )

No it doesn't mean that.

A "untabbed" mode is already done for a long time and works. So you can have one window per session and no tabs at all by setting the proper container mode.

Single message mode in this context means the old "unsplitted" message mode known from old ICQ clients where you could only read one message at a time.
__
Every program has at least one bug and can be shortened by at least one instruction -- from which, by induction, one can deduce that every program can be reduced to a single instruction that doesn't work.
My SMF-based forum fork
#11
Re: List of features, you shouldn't request |
July 18, 2006, 07:30:45
  • Splitting messages
  • Ability to disable/enable toolbar buttons
  • Making 'TabSRMM' folder position configurable
;)

PS: Could you clean this thread a little bit Alex...?