Some of the features in Shibboleth would be useful in Logos, however, any integrated version should 1) get rid of the legacy support features like the ASCII representations and make it a simple WYSIWYG interface, 2) read the Operating System keyboard files so that the virtual keyboard function can support any installed Unicode Keyboard, rather than only working with those keyboards that Shibboleth is aware of (all Keyboards can still make use of the same character palettes that arrange characters by shape, etc.), including Dead Key support (not currently enabled in Shibboleth), 3) have some search and/or find features in the character palettes for locating characters by their metadata (like the Windows Charmap) 4) work with lemma and form pickers to ensure that the words typed in will match the indexes for searching, and 5) consider whether or not to attempt normalization of the output.
Some of the features in Shibboleth would be useful in Logos, however, any integrated version should 1) get rid of the legacy support features like the ASCII representations and make it a simple WYSIWYG interface, 2) read the Operating System keyboard files so that the virtual keyboard function can support any installed Unicode Keyboard, rather than only working with those keyboards that Shibboleth is aware of (all Keyboards can still make use of the same character palettes that arrange characters by shape, etc.), including Dead Key support (not currently enabled in Shibboleth), 3) have some search and/or find features in the character palettes for locating characters by their metadata (like the Windows Charmap) 4) work with lemma and form pickers to ensure that the words typed in will match the indexes for searching, and 5) consider whether or not to attempt normalization of the output.