# \[Proposal\] Revamp the playground quicklook APIs **URL:** \ **Category:** Discussion\ **Created:** [January 9, 2018, 11:19pm UTC](https://forums.swift.org/t/proposal-revamp-the-playground-quicklook-apis/7392 "2018-01-09T23:19:18Z")\ **Posts on this page:** 2\ **Page:** 3
**Author:** ![saagarjha](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@saagarjha](https://forums.swift.org/u/saagarjha)\ **Post date:** [January 24, 2018, 8:50pm UTC](https://forums.swift.org/t/proposal-revamp-the-playground-quicklook-apis/7392/41 "2018-01-24T20:50:28Z")
I haven't looked under the hood to see how this works, but I'd wager a guess that the code that does this is written in Objective-C. Thus, it would be unable to access anything from Swift that wasn't exposed to Objective-C though `@objc`. ---
**Author:** ![cwakamo](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/cwakamo/32/402_2.png) [@cwakamo](https://forums.swift.org/u/cwakamo)\ **Post date:** [January 24, 2018, 9:00pm UTC](https://forums.swift.org/t/proposal-revamp-the-playground-quicklook-apis/7392/42 "2018-01-24T21:00:40Z")
To my understanding, lldb does not at present look at `CustomPlaygroundQuickLookable` conformances. So from a "maintaining parity with current behavior" perspective -- which is the goal of this proposal -- confining the new `CustomPlaygroundDisplayConvertible` to something playground-specific is correct. Similar to a sentiment expressed in a previous message, I also think that there's room for `CustomPlaygroundDisplayConvertible` to live alongside `CustomDebugDisplayConvertible` should that someday be added to the language. Playgrounds and the debugger are different environments, so being able to customize display for one vs. the other makes sense to me. (I imagine it would be likely that both environments would check the other's protocol, but at a lower priority.) [Previous page](https://forums.swift.org/t/proposal-revamp-the-playground-quicklook-apis/7392.md?page=2)