Re: [Fire-core] functional spec

[Jason T. <tow...@ma...>]

On Friday, May 9, 2003, at 09:34  AM, Gabriel Radic wrote:
> I have no idea how Fire's core development group works, but I'd like=20=

> to be part of it.
>
> My job is to design user interfaces, I have 4 years of experience on=20=

> desktop and web-based user interfaces. I hope you agree that Fire=20
> needs some strong GUI loving.

This is one of our top focuses for Fire 1.0. We've made quite a bit of=20=

progress so it would be good for you to take a look at that. For=20
example, the group chat invite UI was completely rewritten. We are also=20=

in the middle of redoing the buddies window.

> My goal is to make Fire an easy to use, clean, powerful chat=20
> application that will be as  user-friendly, mac-like and reliable as=20=

> Apple's Mail.

I'm wondering how you would envision contributing to Fire. I'm assuming=20=

you would not be implementing any code. Would you be submitting NIBs=20
and graphics? Or just UI design documents?

> Here is a draft of a functional specification with focus on the GUI.=20=

> It raises some questions on existing features and tries to define some=20=

> new ones. Please look at the document and give me your opinion.
>
> If you like the format and think you can use the content, please=20
> include me in your group. I'm sure I could help.
>
> Thank you.
>                                                 -- Gabriel Radic
>
> Fire
> GUI Functional Specification
> Draft 0.1 =D0 March 17 2003
> 1 Concepts
> 1.1 What's Fire
> Fire is an independent Internet instant messaging client software for=20=

> the major networks and
> IRC.
> 1.2 Target Audience
> Power users or Grandmothers?

Currently Fire is more geared toward power users. However, I believe we=20=

can make the initial user experience better for everyone moving forward.

> 2 GUI Workshop
> 2.1 What's Wrong?
> Fire's user interface can be a major downturns for new users. Although=20=

> there is a lot of user
> feedback on forums and mailing lists, it is not very sharp. It seems=20=

> there is no major problem, but
> many little annoyances. It seems most users have a problem with the=20
> ergonomics and the
> sexiness, and few of them have specific needs for specific areas.
> I would describe the overall look-and-feel of the application as=20
> unpolished, and in no case broken.
> 2.2 Perception of Stability
> Users have the impression fire is an unstable application, not because=20=

> it crashes, but because if
> feels unstable. The application has some bugs, and always will because=20=

> of its ever-evolving nature.

That sounds like a circular argument. Users have the impression that=20
Fire is unstable because it feels unstable. Why does Fire feel=20
unstable? I believe if you compare Fire a year ago with Fire now, that=20=

we have made great strides in stability.

> One way to achieve user confidence is to actually make the application=20=

> stable: feature-freeze and
> fix the bugs. Another way is to improve user's perception of =
stability.
> Improving the feedback towards the user does this. Messages like Fire=20=

> can't connect are not well
> received. A great deal of problems is generated by Fire's environment,=20=

> which evolves and cannot
> be controlled, and it's even hostile at times. The messages should=20
> state exactly what the problem
> is and who is causing it: the user, the local network, the server, bad=20=

> karma.
> E.g.
> Fire can't connect. BAD.
> It seems your network connection is disabled. You are working offline.=20=

> GOOD.
> <NEED TO INSERT MORE MESSAGES HERE>

If you have specific examples of messages and what we should change=20
them to in various situations that would be helpful.

> 3 Objects
> At the user level, Fire will be manipulating three main objects:=20
> Accounts, Buddies and
> Conversations.
> 3.1 Accounts
> Users can add accounts for different services. These should be managed=20=

> from the Preferences
> window, much in the way they Mail does it.
> Accounts can be created, edited, connected, disconnected, changed=20
> status, and deleted.
> 3.1.1 Accounts Management
> 3.1.1.1 Creating Accounts
> 3.1.1.2 Modifying Accounts
> 3.1.1.3 Connecting and Disconnecting Accounts
> 3.1.1.4 Accounts Status
> 3.1.1.5 Removing Accounts
> 3.1.2 Console Window
> 3.2 Buddies
> 3.2.1 Buddy List
> 3.2.2 Accounts Management
> 3.2.2.1 Creating Buddies
> 3.2.2.2 Modifying Buddies
> 3.2.2.3 Removing Buddies
> 3.3 Conversations
> 3.3.1 Dialog vs. Group Conversations
> 3.3.1.1 Group Conversations
> 3.3.2 Archiving
> 4 Menu System
> Here=D5s a proposal for a more coherent menu system in Fire.
> =A5 Fire
> o About Fire
> =D1=D1=D1
> o Check for Updates
> o Send Feedback

We get a lot of Fire email as it is on fire-core... not sure I would=20
want to make this even more prominent than it is in the Help menu.

> =D1=D1=D1
> o Preferences=C9
> =D1=D1=D1
> o Services, Hide, Quit, etc=C9
> =A5 File
> o New Conversation =D0 detailed later in o
> o New Group Conversation =D0 detailed later in 4.2.2
> =D1=D1=D1
> o Open Recent Conversations
> =A7 Conversation T-1
> =A7 Conversation T-2
> =C9
> =A7 Conversation T-10
> =D1=D1=D1
> =A7 Conversation Archive
> o Save Conversation to File

I prefer the term "Chat" to "Conversation". Moving the IM to Other and=20=

Create New Group Chat items to the File menu has been suggested by=20
others, along with a renaming like you suggest. Also, the New Chat=20
command would need to be a bit of a revamping of IM to Other if it were=20=

to have that prominent placement.

> =D1=D1=D1
> o Import >
> o Export >

Right Import and Export are less frequently used so could be moved to=20
the bottom of the list.

We also need Send File To Buddy in there somewhere.

> =D1=D1=D1
> o Page Setup=C9
> o Print
> =A5 Edit=C9
> =A5 Format=C9
> =A5 Buddies
> o Add Buddy=C9
> =D1=D1=D1
> o Edit =C9
> o View Web Profile
> o Conversation Archive
> =D1=D1=D1
> o Block Buddy
> =D1=D1=D1
> o Invite to Join=C9
> =A7 New Group Conversation
> =D1=D1=D1
> =A7 Active Group Conversation 1
> =C9
> =A7 Active Group Conversation x

We also need Add Group and Remove Buddy commands. Any particular reason=20=

you think we should remove Open IM Window, Chat History, and Get Info=20
from this menu? Those were added because we want to have all contextual=20=

menu commands available through the main menu as well.

> =A5 Window
> o Zoom
> o Minimize
> =D1=D1=D1
> o Next Conversation
> o Previous Conversation
> =D1=D1=D1
> o Show Buddy List

We cannot use the term "Buddy List" as this is trademarked by AOL. We=20
have decided to go with "Buddies Window" instead.

> o Show Accounts
> o Show Console
> =D1=D1=D1
> o Bring All to Front
> =D1=D1=D1
> o Buddy List
> o Buddy1
> o Buddy2

Missing the Hide Toolbar, Customize Toolbar, Close All Chat Windows,=20
Edit Away Messages items. I believe we should move Toggle Buddy Window=20=

Opacity into the prefs, but the other commands are useful to have.

> 4.1 Fire
> This contains the obvious application menu options, with some twists.
> 4.1.1 About Fire
> The About Window should mention the line
> Fire=D5s open source project page: http://fire.sourceforge.net

We currently have this in the Help -> Fire Home Page command.

> 4.1.2 Check for Updates
> Looks for the latest version of Fire. If a newer version exists, Fire=20=

> should display the message:
> Version x.xx of Fire is available for download and prompt the user=20
> with the following
> options:
> =A5 What=D5s New =D0 default option
> =A5 Cancel
> =A5 Download <version number>
> We can imagine a Skip Version option in a future version.
> 4.1.3 Send Feedback
> Opens a new e-mail message in the default e-mail reader. The message=20=

> addressed to firedevelopment@
> lists.sourceforge.net with the subject:
> Fire x.xx User Feedback

Currently we send feedback to fire-core.

> 4.2 File
> Conversations are the files, or objects manipulated in Fire. I am=20
> wondering if it=D5s too bold to call
> this menu Conversation, instead of just File. I think it makes a lot=20=

> of sense and it adds a personal
> touch. Note: don=D5t start me with the HIG, I=D5ll throw Metal at you =
:-)

I'd prefer to stick with File.

> 4.2.1 New Conversation
> This will create a new conversation window. Conversation windows=20
> created this way will open
> with a sheet asking for a Service and a Buddy. If the Buddy List is=20
> opened and a buddy is selected,
> the values in the sheet will be filled in with that buddy=D5s service=20=

> and ID. The point of this is to
> allow users to start conversations with buddies not in the list.

This is what IM to Other does today, but I believe there is a desire to=20=

have some way of picking from the buddy list as well as typing in.

> 4.2.2 New Group Conversation
> The group chat feature in Fire v.3x is unusable for most users. Here=D5s=
=20
> a proposal for an enhanced
> GUI. The list of buddies to invite should support drag-and-drop from=20=

> the Buddy List.

We agree, which is why we have a completely new dialog in CVS now. We=20
have not yet implemented invite by drag and drop, but that is on the=20
list to do as well.

-Jason