Skip to content
This repository has been archived by the owner on Dec 14, 2019. It is now read-only.

Implement channel join/part function #12

Open
3 of 5 tasks
simnalamburt opened this issue Nov 20, 2016 · 2 comments
Open
3 of 5 tasks

Implement channel join/part function #12

simnalamburt opened this issue Nov 20, 2016 · 2 comments

Comments

@simnalamburt
Copy link
Member

simnalamburt commented Nov 20, 2016

Implement multiple channel speaking features

TODOs

  • At first, we fix the channel that can be talked to exist only #a, #b, #c
  • Next, implement channel creation, channel joining, channel leaving function
  • Force channel names to start with #
  • Error when trying to enter a channel that already exists
  • Handle the "server buffer" specially

Note: typing must be separate for each channel. The contents of the #a channel disappear when you change to the #b channel, and when you return to the #b channel from the #b channel, the previous contents must be displayed again.

https://github.com/openirc/openirc/blob/master/client/src/app.elm#L26


I would start by fixing the model part code...

type alias Model =
  {
    logs : List Line,
    nick : String,
    typing : String
  }

like this:

type alias Channel =
  {
    logs : List Line,
    typing : String
  }

type alias Model =
  {
    nick : String,
    channels : List Channel
  }

CC @heejongahn

@simnalamburt simnalamburt changed the title 채널 입장/퇴장 기능 구현 Implement channel join/part function Nov 20, 2016
@heejongahn
Copy link
Contributor

Basic channel concept is implemented (see #16)

If our first goal is to resemble IRCCloud, I can think of something like this:

  • Server/Channel information is shown at the sidebar (scrollable)
  • Each server has a list of joined channel below itself.
  • Also, each server has a text input which can be used to (join/create) new channel.
  • Each list item (that is, an item representing a channel) has channel name and small x button to close the channel.

So the sidebar would seem like:

Server A
Channel 1 [x]
Channel 2 [x]
Channel 3 [x]
___________ (to join/create channel)

I think we can ignore server for now and assume that there's only one server available. Does this sound ok?

simnalamburt added a commit that referenced this issue Nov 24, 2016
Implement basic channel concept (#12)
@simnalamburt
Copy link
Member Author

Good. #16 has been merged.

simnalamburt added a commit that referenced this issue Nov 26, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants