It consists of
- a custom config-file tapfckconfig.js
- the editor-component itself
- a custom engine implementation mapping the filebrowser url's to the filebrowser service.
- a filebrowser service which makes use of an ...
- ... extension implementing the FileBrowser interface. This comes with a default implementation which just browses the filesystem of the server. It's easy to replace by a custom implementation supporting, e.g., a database.