View for displaying messages similarly to iOS Messages system app. This view when deployed within your application will handle incoming and outgoing messages display.
While using this module you don't need to handle messages view on your own. You're getting complete solution easy to configure and customize to your needs. If you think you can have more customisation, please tell us what you think via addess below.
In order to start using this framework you need to:
- Embed this framework
- Style your view
- Communicate with view via ViewController
In Cartfile put
github "PGSSoft/MessagesView"
In project root directory say:
carthage update --no-use-binaries --platform iOS
This will fetch the project and compile it to library form. When using carthage, you have two options:
Using standard cathage module requires you to go to Carthage/Build folder within your project and drag it into Embedded Binaries section int your project General settings. This solution no 1. is pretty standard. Unfortunately it doesn't work with storyboard as we intended and you will not be able to customize MessagesView from storyboard directly. It will be working but have to be customized from code. Considering all conditions above we recommend Embedding into your project.
to embed this project as source code you need to:
- Go to folder
Carthage/Checkouts/MessagesViewand dragMessagesView.scodeprojinto your own project. - In MessagesView project find
Products/MessagesView.frameworkand drag it intoEmbedded Frameworkssection in your project general settings
NOTE: To be able to track changes from storyboard at design time, you need to embed framework in non-standard way as described in 1b.
Let's design!
- Go to storyboard
- Set up a
UIViewwith constraints of your choice - Change owner class from
UIViewtoMessagesView. Don't forget to change module name underneath too intoMessagesView. Xcode will now recompile source code necessary to show rendered MessagesView in Storyboard. Completely rendered messages view will appear in storyboard in seconds!
Now you are free to style your messages view as you wish!
Example:
- change messages background color
- change button label caption
- change button background color
- change button background image
You can find full list of customizable properties in the Wiki. This will be prepared soon.
Create example ViewController From example below. ViewController has to conform protocols MessagesViewDataSource and MessagesViewDelegate.
In order to communicate with MessagesView, your ViewController should contain:
MessagesViewDelegateto take action when user taps a buttonMessagesViewDataSourceto feed the viewIBOutlet MessagesViewto read information from view
public protocol MessagesViewDelegate {
func didTapLeftButton()
func didTapRightButton()
}Your viewController need to implement actions taken after user taps left or right button
To feed view with intormation, your datasource have to provide two sets of information: peers and messages
public protocol MessagesViewDataSource {
var messages : [MessagesViewChatMessage] {get}
var peers : [MessagesViewPeer] {get}
}As you can see objects that carry messages have to conform to MessagesViewChatMessage protocol and objects that carry peers have to conform to MessagesViewPeerprotocol. These are listed below:
public protocol MessagesViewChatMessage {
var text : String {get}
var sender: MessagesViewPeer {get}
var onRight : Bool {get}
}
public protocol MessagesViewPeer {
var id : String {get}
}In the demo app we created extension to ViewController class that makes it compliant to MessagesViewDataSource protocol. In this case the limitation was that extension cannot contain stored properties so we decided to provide information via computed variables only but you can do as you wish in your own project. You need only to have object which is MessagesViewDataSource compliant. This is how we dealt with it in demo app:
extension ViewController: MessagesViewDataSource {
struct Peer: MessagesViewPeer {
var id: String
}
struct Message: MessagesViewChatMessage {
var text: String
var sender: MessagesViewPeer
var onRight: Bool
}
var peers: [MessagesViewPeer] {
return TestData.peerNames.map{ Peer(id: $0) }
}
var messages: [MessagesViewChatMessage] {
return TestData.exampleMessageText.enumerated().map { (index, element) in
let peer = self.peers[index % peers.count]
return Message(text: element, sender: peer, onRight: index%2 == 0)
}
}
}In this example, we have converted on the fly our stored TestData information into Messages and Peers. No other class in the project have to be aware of MessagesView. Only ViewController is interested.
Create IBOutlet in standard way
Having your ViewController know about messagesView presence enables it to use view's public API.
In our example it is when ViewController loads:
override func viewDidLoad() {
super.viewDidLoad()
// Do any additional setup after loading the view, typically from a nib.
messagesView.delegate = self
messagesView.dataSource = self
}Additional behaviours that may be useful to you.
- hiding buttons
leftButton(show: Bool, animated: Bool)
rightButton(show: Bool, animated: Bool)This way you can show or hide button. Animated or not - as you wish.
If you have any ideas how this project can be developed - do not hesitate to contact us at:
You are now fully aware of MessagesView capabilities. Good luck!
When contributing to MessagesView you may need to run it from within another project. Embedding this framework as described in paragraph 1.1b will help you work on opened source of this project.
Made with love in PGS ♥
Please Use develop branch and fork from there!
MIT License
Copyright (c) 2016 PGS Software SA
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.