I recently added a server file/image manager to the BrowserSuite ServoyHtmlEditor bean allowing you to:
browse the server with a user friendly interface,
with a nice tree view, image previews, cool icons, a popup menu with all options,
download,
upload,
rename,
delete,
create folders…
Giving you the power to manipulate files on your server right from the client html editor.
Check out v0.9.45 of the BrowserSuite if you haven’t already https://www.servoyforge.net/news/44:
[attachment=0]ServerFileBrowser.gif[/attachment]
Now, as some of you might know, the bean is currently using 3 different Open Source JavaScript libraries (3 different implementation of a html editor in JavaScript), so it took me some time to implement these features in all of them…
And I am now looking into adding some more capabilities to it, like giving you the power to add your own (Servoy-driven) scripts and callbacks, to provide your own CSS and menu for the user to choose from and to add your own html templates…
Doing this in all 3 implementation will again take a huge amount of my (limited) time, so I would like to know (for those who are using the BrowserSuite or are planning to), which implementation are you interested in the most?
Knowing this will allow me to prioritize the development, thus giving you powerful customization options sooner!
jcarlos:
Are you using somehow the File Plugin on Servoy?
No, I’m not using the File Plugin but a mechanism of my own, where a local web server (running on the client on localhost), is used as a proxy to a servlet (running on the server). The proxy allowing me to create any kind of query, thus enforcing the security.
jcarlos:
Can the File plugin be redundant if you are using the Browser plugin?
No because this new FileManager is only available in the ServoyHtmlEditor bean, and it is a runtime mechanism that is available to users.
Developers only have options to configure its usage, they can’t use it directly.
Next version will add enhanced options, like some flags to allow/forbid file browsing / uploading / create folders / rename, add a sub-path to the default folder (to set a ‘user specific’ root), a set of allowed and/or forbidden file extensions, maybe even create and return a zip file when downloading a folder.