@ibrahimcetin @Kawba @JoeJoe1313 let's continue the discussion of markdown in the example app here. We currently have two PRs and both look good:

The questions that have come up:

use built-in markdown support vs swift-markdown-ui
toggle for markdown vs plain text

I think the answer to the first question actually has a big impact on the second. In particular there is an issue where the output of swift-markdown-ui doesn't select/copy properly. Aside from that, the pros of swift-markdown-ui is that it supports more markdown flavors and is quite customizable. It isn't a complicated integration, but the selectability is unfortunate and something we would want to explain in the example application (that we presume people might copy).

If we use swift-markdown-ui I think we need the toggle as an escape so people can copy & paste the output.

If we go with the built-in approach it doesn't support tables, but other than that seems to work well. It is a smaller integration, which is nice. I don't think we need to be able to toggle the markdown on/off (though perhaps there are opinions on this) and it leaves the UI simpler.

Based on this I am leaning toward #303. We can include a pointer swift-markdown-ui and some snippets from #309 in the README.md as directions people might want to try.

Any thoughts?

Add markdown rendering to MLX Chat Example #297

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions