Examples Templates Store Pricing Docs Turbo CSS Blog Introducing Turbo UI Named buckets Turbo CSS is Tailwind CSS on steroids Introducing Turbo CSS, the most advanced web-design language Calculate how much storage you use Better login system Collaboration settings Filesystem and Database are not cutting the problem space right What I'm working on 64bit File node IDs New how-to videos Creating buttons gets easier Introducing reusable components HTTPS by default Introducing the Boomla Theme CDN for faster pageloads Write your own website builder on top of Boomla On On composition Shared admin access A fresh config editor Building a multi-purpose theme A filesystem to replace your CMS New file link type: scope Mobile editing support Inline file wrapping changed Package sandboxing New PHP-like JavaScript engine [sjs-4e] Send emails to the website owner New JavaScript engine [sjs-4] A better editing experience New email service provider Glossary and other changes New panel changes Improved registration flow Boomla goes multiplayer Using local dev tools Why Boomla doesn't need Git File Panel Let's build a community Automatic updates Improved sjs-3 API New Frontend CSS modules Work offline with Boomla Faster page loads via caching Drag & drop supercharged Supporting CommonJS modules  Paranoid about loosing data IDE usability improvements Simple App install flow Meetups in Budapest Goodbye broken links Flow control from user space Customizing apps Contextmenu support for apps Deprecating the .Class file Hello Changelog Embedding 3rd party plugins Introducing Tools Installing apps just got amazing Public beta Host on our servers Simple deploy with push/pull Version Control for the Web 350M files on a 1TB disk 2 weeks in review
Control Panel

IDE usability improvements


Uploading into empty file

Uploading into an empty file was a bit inconvenient, because no files where shown, thus you could not upload files relative to them. You had to go a level up, then upload into the parent file.

Now the entire navigation area is a dropzone for the parent file, making file uploads easier.




Making the [..] file responsive

Until now, the [..] file only supported navigation: going a level up. But moving files a level higher in the hierarchy was a bit clumsy: you had to first cut the file, then go 2 levels up, paste into the grandparent, then enter the grandparent to see the file you pasted. Ehm.

Now you have 2 options. You can drop it relative to the parent file represented by the [..] entry in the listing.

Please note that you will not see an icon for the [..] file, which is intentional. It’s simplty a drop target. Note on developers: to support this, new user interface classes were introduced: .o1-file-none, .o1-file-no-icon, .o1-file-no-drop, .o1-file-no-structure.




you can follow me on Twitter