This add a root Chatto.xcworkspace which contains the two shared schemes and xcodproj Chatto & ChattoAdditions.

Carthage can either export multiple shared schemes from a single project or from a workspace, since here there is two xcodeproj for both Chatto and ChattoAdditions, a root xcworkspace must be added to expose both shared schemes at once.

Tested with:

❯ carthage version
0.11.0

This close #5

Steps to reproduce in sample ChattoApp

• Select photo input item from input bar
• Select text input item from input bar
• Got bug demonstrated on screenshot. Input bar shifted. No way to send messages anymore.

I updated Xcode to 8.3. And there are a couple of errors because of Swift 3.1 changes.

I noticed that you've already did the compatibility update on master branch, when do you plan to release a new version (tag) for Swift 3.1?

Chatto is a fantastic resource, thank you for all of your work on it and for open sourcing it. 👍

I see there is an existing Swift 3 branch, which appears to be up to date with beta 5. With beta 6 out, and presumably, an impending official release soon, we're looking to migrate our project to Swift 3 over the next week or two in preparation for the final release to support some new APIs and features along with (or soon after) the iOS 10 launch.

What are your plans for the swift-3 branch? Is there a plan / timetable for the migration? Also, it doesn't appear to be up-to-date with the latest 2.0 release, either. We're happy to lend a hand and help out, but didn't want to jump in if you had specific plans or were already actively working on supporting beta 6 / version 2.0. Just let me know how best we can help!

Hi,

Thanks for your work, your framework seems awesome! And very promising!

I'm currently trying to integrate it in my project, and I have a few questions. The most important for me is do you support sections header? I want to split my messages by day, providing a nice header. I think you can do it artificially with a new type of message, but it won't stick like headers do. I think you can achieve that with viewForSupplementaryElementOfKind but I didn't find this kind of code in Chatto.

If you don't plan to support it, I will try to help you implementing it :)

Kind regards, Denis

while migrating to swift 3 chatViewController.swift

Static member 'weakMemory' cannot be used on instance of type ‘PointerFunctions.Options' let presentersByChatItem = MapTable(keyOptions: .weakMemory , valueOptions: PointerFunctions.Options()) let presentersByCell = MapTable(keyOptions: .weakMemory, valueOptions: .WeakMemory)

Was wondering if I could add a full width (width equal to width of the screen) in Chatto?

I need to display a banner of information inside the chat stream.

Thanks!

I'm finding that initializing the TextMessageCollectionViewCell in the release build configuration causes a crash, for example: TextMessageCollectionViewCell.sizingCell()

will call

private func commonInit() {

        // nil is returned here, and crashes    
        self.bubbleView = self.createBubbleView()
        ...
}

For some reason in release, self is type BaseMessageCollectionViewCell NOT TextMessageCollectionViewCell. But in the debug configuration, self is of type TextMessageCollectionViewCell (as expected).

Any ideas what could be triggering this?

Using Swift 2.2, Xcode 7.3

Added support for willBeShown() and wasHidden() functions in TextMessageViewModel. The main purpose of this is to give chance to the client to load the avatar images when needed. Most of the code was copied from the corresponding functions in PhotoMessagePresenter. Both Text and Photo message models now look pretty similar, so maybe you guys consider moving some parts to the base classes?

Also added the missing observe calls for the avatar image in view models.

And the essential part of this commit is the call to the main queue in updateClosure:

dispatch_async(dispatch_get_main_queue(), {
    self?.updateCurrentCell()
})

It looks strange, but if you try to set the observable value in willBeShown(), although the model itself has been updated, in BaseMessageCollectionViewCell.updateViews() it still gets the old value, so the update has no visible effect. Deferring the update with an async call to the main queue seems to fix the issue here.

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'UICollectionView received layout attributes for a cell with an index path that does not exist: <NSIndexPath: 0x1cc284a0> {length = 2, path = 0 - 114}'

Seen on iOS 8. No steps to reproduce known.

Last Exception Backtrace:
0   CoreFoundation                       0x2938bf8f __exceptionPreprocess + 127
1   libobjc.A.dylib                      0x37a3cc8b objc_exception_throw + 36
2   CoreFoundation                       0x2938be65 +[NSException raise:format:arguments:] + 102
3   Foundation                           0x2a090f17 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 88
4   UIKit                                0x2ca662c7 __45-[UICollectionViewData validateLayoutInRect:]_block_invoke + 800
5   UIKit                                0x2ca65b1f -[UICollectionViewData validateLayoutInRect:] + 1736
6   UIKit                                0x2ca651eb -[UICollectionView layoutSubviews] + 168
7   UIKit                                0x2ca0ae43 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 544
8   QuartzCore                           0x2c41ed29 -[CALayer layoutSublayers] + 126
9   QuartzCore                           0x2c41a55d CA::Layer::layout_if_needed(CA::Transaction*) + 358
10  UIKit                                0x2ca1da23 -[UIView(Hierarchy) layoutBelowIfNeeded] + 136
11  UIKit                                0x2d0116dd -[UICollectionView _performBatchUpdates:completion:invalidationContext:tentativelyForReordering:] + 162
12  UIKit                                0x2d011633 -[UICollectionView _performBatchUpdates:completion:invalidationContext:] + 28
13  UIKit                                0x2cbce467 -[UICollectionView performBatchUpdates:completion:] + 28
14  Chatto                               0x01549120 Chatto.BaseChatViewController.(performBatchUpdates (Chatto.BaseChatViewController) -> (updateModelClosure : () -> (), changes : Chatto.CollectionChanges, updateType : Chatto.UpdateType, completion : () -> ()) -> ()).(closure #2) (BaseChatViewController+Changes.swift:148)
15  Chatto                               0x015471b8 partial apply forwarder for Chatto.BaseChatViewController.(performBatchUpdates (Chatto.BaseChatViewController) -> (updateModelClosure : () -> (), changes : Chatto.CollectionChanges, updateType : Chatto.UpdateType, completion : () -> ()) -> ()).(closure #2) (BaseChatViewController+Changes.swift:0)
16  UIKit                                0x2ca3efb7 +[UIView(UIViewAnimationWithBlocks) _setupAnimationWithDuration:delay:view:options:factory:animations:start:animationStateGenerator:completion:] + 480
17  UIKit                                0x2ca3edcb +[UIView(UIViewAnimationWithBlocks) animateWithDuration:animations:] + 64
18  Chatto                               0x01544314 function signature specialization <Arg[0] = Owned To Guaranteed, Arg[1] = Exploded> of Chatto.BaseChatViewController.performBatchUpdates (Chatto.BaseChatViewController)(updateModelClosure : () -> (), changes : Chatto.CollectionChanges, updateType : Chatto.UpdateType, completion : () -> ()) -> () (BaseChatViewController+Changes.swift:149)
19  Chatto                               0x0154979c Chatto.BaseChatViewController.((updateModels in _612DFD8221191D415C81FF197E016366) (Chatto.BaseChatViewController) -> (newItems : [Chatto.ChatItemProtocol], oldItems : Chatto.ReadOnlyOrderedDictionary<Chatto.ChatItemCompanion>, updateType : Chatto.UpdateType, completion : () -> ()) -> ()).(closure #1) (BaseChatViewController+Changes.swift:179)
20  Chatto                               0x01546a68 partial apply forwarder for Chatto.BaseChatViewController.((updateModels in _612DFD8221191D415C81FF197E016366) (Chatto.BaseChatViewController) -> (newItems : [Chatto.ChatItemProtocol], oldItems : Chatto.ReadOnlyOrderedDictionary<Chatto.ChatItemCompanion>, updateType : Chatto.UpdateType, completion : () -> ()) -> ()).(closure #1) (BaseChatViewController+Changes.swift:0)
21  Chatto                               0x01547684 partial apply forwarder for Chatto.BaseChatViewController.((updateModels in _612DFD8221191D415C81FF197E016366) (Chatto.BaseChatViewController) -> (newItems : [Chatto.ChatItemProtocol], oldItems : Chatto.ReadOnlyOrderedDictionary<Chatto.ChatItemCompanion>, updateType : Chatto.UpdateType, completion : () -> ()) -> ()).(closure #3).(closure #1) (BaseChatViewController+Changes.swift:193)
22  libdispatch.dylib                    0x37fcd2e3 _dispatch_call_block_and_release + 8
23  libdispatch.dylib                    0x37fcd2cf _dispatch_client_callout + 20
24  libdispatch.dylib                    0x37fd0d2f _dispatch_main_queue_callback_4CF + 1328
25  CoreFoundation                       0x293513e9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 6
26  CoreFoundation                       0x2934fae9 __CFRunLoopRun + 1510
27  CoreFoundation                       0x2929bf31 CFRunLoopRunSpecific + 474
28  CoreFoundation                       0x2929bd43 CFRunLoopRunInMode + 104
29  GraphicsServices                     0x30d76201 GSEventRunModal + 134
30  UIKit                                0x2ca6d879 UIApplicationMain + 1438

Demo app updated to show avatar image only for text messages by modifying the viewModelBuilder, Presenter is probably best place to set avatar image based on viewmodel and decoration attributes, but this is highly case by case.

By default, the avatar is at the bottom of the collection view cell. No way to customize it unless changing code.

Screenshot of demo app as below:

Thank you for your amazing work. We are using Chatto for chat module in our application. Recenlty we have been advised to review Photos/Gallery Permission Popup. Steps to reproduce:

1. Close and reopen app
2. Open chat
3. Click the camera button at the lower left of the screen (right next to the keyboard button)
4. Select “Keep current selection”

From this point, if a member wants to add more photos to the current selection, they have no choice but to close and reopen the app. again popup will appear and select add more photos

Is there a way we can show permissions every time we open up the chat screen instead of seeing this after killing and relaunching app?