communi / communi-sailfish Goto Github PK

Add ability to autocomplete available nick names on a channel. As a bonus, let's do it in a way that the user names are sorted by last activity time, ie. if multiple nicknames are matching, the one that spoke the most recently will be suggested first.

We should provide indication for old messages that the user has already read.

• Old messages should remain readable
• Old messages should be visually separated from new ones

The current idea (changing color to grey) might be a good direction, but it's not "there yet". Let's think of something better.

Save & restore not only connections but also buffers, but only for non-bouncer connections. Perhaps wait a sec or two after getting connected and restore buffers only if nothing happened?

• IrcConnection::saveState()
• IrcConnection::restoreState()
• IrcBufferModel::saveState()
• IrcBufferModel::restoreState()

Needs to indicate that the key is mandatory in this case.

• IrcConnection::channelKeyRequired() [signal]
• IrcConnection::sendCommand()
• IrcCommand::createJoin()

Let's implement a better welcome screen for the app. The welcome screen would serve the following purpose:

• Let users select which of the configured networks they want to connect to (using a list of check boxes)
• Let users select a network and edit/delete it
• Let users add a new network

Of course, these should also be reachable from the chat page, but as a start it'd be nice to have them on the welcome page.

The text input is disabled while not fully connected. If a nick is reserved while connecting (and the nick dialog is swiped away) there's no way to enter a new nick.

Not critical, but ideally "freenode" and "irc.freenode.net" wouldn't both exist in the list:
http://www.youtube.com/watch?v=VJs3599Nj20 (4:40)

I noticed that if the first connection is disabled in WelcomeDialog, the corresponding empty server buffer will be also presented after accepting the dialog. It would be better to present something from the first enabled connection. I added BufferProxyModel::model(IrcConnection*) so in QML we can use BufferModel.model(connection).get(0) to get the first buffer from a specific connection.

Text size/color will be correct, and it will scroll when using the pulley.

ListItem::remorseAction()
https://sailfishos.org/sailfish-silica/qml-sailfishsilica-listitem.html#remorseAction-method

Depending on the ambience color, the contrast of Theme.highlightColor might not be ideal. Theme.primaryColor would be a better choice.

Ampersand etc. are causing problems. "textFormat: Text.RichText" for the Label delegate might fix it.

Somewhat related to #33, it would be nice for the client to recognize common quit messages and reformat the notices accordingly, eg.:

x has quit (Ping timeout: NNN seconds) -> x has timed out (NNNs)
x has quit (Read error: Connection reset by peer) -> x disconnected unexpectedly
x has quit (Remote host closed the connection) -> x has disconnected

Don't know about others, but those 3 would make most quit notices less noisy and fit them in a single line. Filtering out client adverts in quit and part messages would be kinda nice, but presumably controversial.

A dialog is needed for changing the nick, and entering a new nick when the initially chosen nick is reserved.

• IrcConnection::nickNameReserved() [signal]
• IrcConnection::nickName [property]

• step 1: hide by default
• step 2: make it a setting

It's a bit inconvenient to remove & add a new channel in order to fix a typo. Could we make the existing channel names editable. Just click to start editing?

When you have multiple connections to the same hostname, trying to join a channel using the dialog for it will result in the first connection joining to the channel (even when you were on the second one).

Test case:

• Clear settings
• Create a connection to freenode, connect, join #communi
• From the PushUpMenu create a second connection to freenode
• Connect the second connection and try to join #communi

Expected result:

New connection will join the channel so there'll be two buffers

Actual result:

New connection doesn't join the channel but the UI will switch to the already joined channel.

Set IrcConnection::reconnectDelay (the default value is 0 = disabled)

Instead of relying on socket timeouts (that can take very long), we should try to get internet connectivity status change notifications from the system. I'm sure SailfishOS provides something similar to org.freedesktop.NetworkManager.

We added Qt.application.active here to get highlight info banners even for the current buffer when the application is inactive.

Binding {
    target: storage
    property: "active"
    value: Qt.application.active && page.status === PageStatus.Active
}

The undesired side-effect is that the highlight of "new/unseen" messages gets messed up when the application activity changes.

=> use ZncManager from src/shared.

When a nick name is reserved or a channel requires a password, a dialog is popped up. Those dialogs could be more descriptive and explain that another nick name is required because it was taken, or that a channel couldn't be joined because it needs a password.

The password only changes to dots once the user is done editing it.

We need to figure out how to package the app in such a way that will get it through to harbour.

Currently every nickname has the same color, which makes the channel harder to read.

What's not clear is what colors to use - because not every color might be visible on every ambience.

Visualize connection errors somehow. Perhaps a message and/or turn the connection item red?

We should log the activity in every buffer; with the following considerations:

• User should be able to turn logging on/off (maybe on a per-network basis)
• Logging should be disabled for bouncer connections
• When a user opens a buffer and a log is available; show the last N messages from the log in the buffer
• Provide an option to display the full buffer log and search in it

Multiple connections to the same network can get confusing. To implement this, just set IrcConnection::displayName and it will automatically reflect in the UI and is also saved & restored. The only thing missing is an input field somewhere.

Currently it's not obvious that a long press will give a context menu, because there's no pressed effect. I think a normal list item pressed effect (ListItem::highlighted I suppose) would give a nice hint for the user.

Utilizing the settings application currently requires installing a JSON description file to /usr/share/jolla-settings/entries, which is not allowed by Harbour. We could distribute a settings-enabled version on the openrepos, though.

A prototype: https://github.com/jpnurmi/communi-sailfish/commit/cdd18455136604cd782e17a0138e8705d5bbe1aa

Settings:

• font size
• nick format
• scrollback size
• timestamp format
• notifications/feedback
• show/hide joins/parts/quits
• show/hide user details for joins/parts/quits
• completion suffix (':' vs. ',')
• reconnect delay?
• quit message
• nick alert case sensitivity
• ...

The retweet icon should be replaced with something more intuitive. If there's nothing more suitable in the theme icons, can we ask a designer to draw something? Or alternatively it could be a plain unicode character: http://www.fileformat.info/info/unicode/char/21e5/index.htm

The cover page needs to be implemented. Not sure what kind of actions if any we could put there.

It would be nice if the TextFields in BufferPage and ConnectingDialog looked the same. Both are similarly located below a ListView, so they could use the same visuals.

We should not restore empty buffers for a disabled connection, until the user changes his mind and decides to connect.

Instead of having a page for channels and a separate page for the chat, I suggest the following:

• Have only one chat page that by default shows the "server buffer"
• Put a drawer onto the chat page and use that for channel switching
  NOTE: a plain pulley menu is NOT a good solution for channel switching because it is not meant to contain that many items
• Put a button somewhere on the chat page for showing the drawer
• Add a pulley menu to the bottom of the chat page for quick options
  NOTE: a pulley menu on the top is infeasible because it would require the user to scroll all the way up

Here's an initial list of quick options that I suggest adding to a bottom pulley menu.

• User list (if the user is currently on a channel)
• Part (for channels) / Close (for queries)
• Disconnect / Reconnect (for the server buffers)
• Join / Query

This way, all the relevant things that a user would do in an IRC client would be there on a single page.

Enabling landscape support:

Page::allowedOrientations: Orientation.Portrait | Orientation.Landscape

Not yet supported by the Silica components?

A very prominent feedback I used to receive for the IRC Chatter app was that users disliked the way of setting the initially joined channels. So instead of having to type them separated with commas, I'm adding a UI with a list view to set them.