You both are kinda right.
Although you can use the Character View without any edits to the source, it will causes errors when updating clothing (although you may change your clothing, say in the "Inventory Tab," your character will not change unless you enter another tab first.) If you do not mind this glitch, you could easily use any of the Character Viewers within the game, but if the glitch does bother you, a new one would need to be added.
Fun Fact: Looking at the source there are remnants of a "LobbyCharacterView" that was never actually implemented.
A few functions that contain character view are
Shop
Code:
<!-- CHARACTERVIEW : 캐릭터 표시창 -->
<CHARACTERVIEW item="EquipmentInformationShop" parent="Shop">
<BOUNDS>
<X>0</X>
<Y>120</Y>
<W>460</W>
<H>420</H>
</BOUNDS>
<STRETCH/>
<VISIBLEEQUIPMENT>true</VISIBLEEQUIPMENT>
</CHARACTERVIEW>
Equipment (Inventory)
Code:
<!-- CHARACTERVIEW : 캐릭터 뷰 -->
<CHARACTERVIEW item="EquipmentInformation" parent="Equipment">
<BOUNDS>
<X>0</X>
<Y>120</Y>
<W>460</W>
<H>420</H>
</BOUNDS>
<STRETCH/>
<VISIBLEEQUIPMENT>true</VISIBLEEQUIPMENT>
</CHARACTERVIEW>
And if we were going to make the Equipment one available for Lobby we could do...
Code:
<!-- CHARACTERVIEW : 캐릭터 뷰 -->
<CHARACTERVIEW item="EquipmentInformation" parent="Lobby">
<BOUNDS>
<X>*INSERT LOCATION OF X COORDINATE OF TOP LEFT CORNER*</X>
<Y>*INSERT LOCATION OF Y COORDINATE OF TOP LEFT CORNER*</Y>
<W>*INSERT SIZE OF WIDTH*</W>
<H>*INSERT SIZE OF HEIGHT*</H>
</BOUNDS>
<STRETCH/>
<VISIBLEEQUIPMENT>true</VISIBLEEQUIPMENT>
</CHARACTERVIEW>