In our 2.6.1 release we included a new developer toolbar called the ColdBox SideBar. You can see a screenshot below:
The SideBar enables the developer to have a floating toolbar that will assist on development. You can reinit the framework, clear the cache, clear the log files, clear some of the most used scopes like session and client, and so much more.
It also appends itself to errors when they occur, so you can easily reinitialize or search for the errors in the live docs or the forums. Yes, you can search right from the sidebar.
Another extra feature is that the links declared are all customizable, so you can customize your own sidebar according to your project, create internal or external links, or anything you like.
Another extra feature is that the sidebar is completely skinnable via css, so you can make it look pretty!! So skin it and send over your screenshots.
Blog
Recent Entries
Announcing BX-WORD: Native Microsoft Word Automation for BoxLang
Every enterprise runs on Word documents. Contracts. RFPs. Proposals. Board reports. Offer letters. HR handbooks. Compliance policies. Invoices. Statements of work. Legal memos.
BoxLang 1.15.0 Released: Blazing Fast Strings, Runtime Portability, and much more
BoxLang 1.15.0 is a high-impact release with two big headlines and a long tail of hardening. The first headline is a massive performance upgrade to string handling: a new first-class BoxStringBuilder type, compile-time literal folding, smarter &= semantics, and a runtime concat strategy that automatically switches to builder-backed accumulation once your expression gets big enough. Your existing string-heavy code just got faster. No rewrites required.
MatchBox Web Server: BoxLang Without the Full Server Stack
MatchBox includes a native web runtime for building small, fast BoxLang web applications without requiring a JVM or a traditional servlet container. You can follow the MatchBox open beta at https://github.com/ortus-boxlang/matchbox. There are two related pieces in the beta today: a webroot server for .bxm templates and static assets, and a routed app server built around web.server(). Both are early, but they show the direction clearly: BoxLang should be able to serve HTTP from a compact native runtime when the application does not need the full JVM stack.
Add Your Comment