[8.0 Release] Community discussion

[jessesquires]

The purpose of this issue is to provide a designated place to discuss the 8.0 release of the library.

You can find on-going release notes at #1216.

[kientux]

Sad that you're going to drop iOS 7 support.

[harlanhaskins]

iOS 7 represents less than 10% of all devices, and leaves us with a lot of old code and testing burden to maintain compatibility. If your app still needs to support iOS 7, you can absolutely continue using JSQMessagesViewController 7.x.

[mriddle]

Hey @jessesquires is there are an issue that I can follow for extra custom cell support in this release? That is the ability to support multiple outgoing or incoming messages within the one JSQMessagesViewController.

I noticed the behaviour was introduced as part of #137 and it looks like it may have been removed unintentionally in 85a65f7 as part of #172

You mentioned in #1343 that this would be possible in this release. Will this be done as part of pulling out all cell configuration into cell factory objects?

Was hoping that with a better understanding I may be able to provide some assistance.

[jessesquires]

Thanks @mriddle ! Just opened #1720 to track and explain. Let's move this conversation there. 😄

[asher636]

Hi @jessesquires , when is the swift 3 version for JSQMessageViewController is releasing? TIA

[MacMeDan]

@asher636 JSQMessagesViewController is written in ObjectiveC So you can leverage it with Swift 3 right now. You may be looking for how to do that. There is a Swift 3 example included in the project that will go out with the JSQ v8 but is not dependent on it. If you want to check it out just checkout the Develop branch and pull the latest. Let me know if you need any help 👾

[asher636]

Ah man great to hear that. Thank you so much :). You guys are great.

Thanks & Regards,
[image: https://wizdevelopers.com]

On Mon, Nov 21, 2016 at 9:16 PM, Dan Leonard notifications@github.com
wrote:

@asher636 https://github.com/asher636 JSQMessagesViewController is
written in ObjectiveC So you can leverage it with Swift 3 right now. You
may be looking for how to do that. There is a Swift3 example included in
the project that will go out with the JSQ v8 but is not dependent on it. If
you want to check it out just checkout the Develop branch and pull the
latest. Let me know if you need any help 👾

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1336 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQmNbkYa7EtluDamhWn8e0UyAr6otV-Hks5rAcPvgaJpZM4GvvZ5
.

[jessesquires]

@asher636 -- Currently, inter-op with Swift isn't very great. However, as @MacMeDan mentioned, this will be greatly improved with v8.0 of the library.

[jyounus]

@jessesquires I know this is a stupid question, but any idea when v8.0 will be released? I'm asking because I need to implement this into my project.

I'm currently trying to UI complete my app as much as possible. So the question is, should I start integrating v7 into my Swift 3 project OR if I should rather wait a bit longer and instead focus on functionality on other sections of my app?

A rough indicator like within the next 2 months or so would be enough for me to decide if I should postpone this for now and come back to it later.

The ongoing release notes says sometime during second half of 2016. But not sure how accurate that still is. :)