Those running version 0.7 should follow our instructions for Upgrading to Wheels 0.8.
He asked me not to mention his name, but the lion's share of the work has yet again been done by Per Djurner. Everyone that has been following this project needs to give him major thanks for his dedication, talent, and persistence in implementing these new features.
I'm also proud to say that this has largely been a community-driven release. We have had countless discussions and suggestions in our Discussion Group and Code Site. Keep 'em coming, everyone!
Both have contributed massively to CFWheels over many years: I think there are a lot of people who can blame Chris for his original series of screencasts getting them hooked (myself included!) on Wheels, and I'd wager that every CFWheels user has benefited from Per's knowledge and guidance; both of them will be missed - a huge thank you to both of them.
Welcome to David & Andy
We're pleased to announce that David Belanger (Github/dbelanger) and Andy Bellenie (Github/andybellenie) have agreed to join the Core team. Andy used to be on the team a few years ago, and brings lots of years of CFWheels experience with him. David joins us from Argentina (and occasionally Canada), making us a highly international group, with Tom & Andy in the UK and Adam over in Australia (unfortunately, with very few timezone crossovers!). It's fantastic to have them on-board.
Up Next
Our next milestone is finishing up a 2.1 release: Please check the 2.1 Milestone to hear about upcoming features such as improved CORS headers, and also check the Changelog for all the bug fixes and improvements already implemented since 2.0.1.
Why should only <a> and <form> be able to make HTTP requests? Why should only click & submit events trigger them? Why should only GET & POST methods be available? Why should you only be able to replace the entire screen?
By removing these arbitrary constraints, htmx completes HTML as a hypertext
Motivation behind htmx
So what does this all mean? Well, in its simplest form, it means being able to build modern web applications with the UX that users have come to expect, with the HTML, CSS, and the backend technology of your choice which in our case is CFML and CFWheels.
So I decide to see if I could build the TodoMVC project using no hand written JavaScript and only relying on HTML, CSS, and CFWheels. I downloaded the template project and took a look at the application specs to get an idea of what to implement.
Here is the video of the running app:
So if you want to run the app locally, you'll need to have Commandbox installed and the CFWHeels CLI commands for CommandBox installed as well. With those two items taken care of, launch a CommandBox and issue the following commands.
wheels g app name=todo datasourceName=todo template=cfwheels-todomvc-htmx --setupH2
package install
server start
Let's look at those lines and talk about what they do. The first line wheels g app will download the template app from Forgbox.io and create a CFWheels application and name it todo. It also create a H2 database and configures the datasource for you. The next line will install all the dependencies of our app. These include, a few CommandBox modules to make development easier, the CFWheels core framework directory and place it into the wheels folder, and install the H2 drivers into our Lucee server for out application. The last line will start our Lucee server. I've also added a setting to automatically run the Database migrations on application startup so the database schema is created.
You can checkout the code on GitHub. Let me know what you think.
EDIT: The Lucee server that starts up will have cfwheels set as its admin password.
All documentation now lives on http://docs.cfwheels.org/ (thanks to readme.io). We hope this will allow people to more easily contribute to the fantastic documentation already there; you need a (free) readme.io account, but you should be able to 'suggest edits' for any page - feel free to help us out! We're in the process of adding redirects from the old documentation - please bear with us on this one.
You'll notice the plugin listings are greatly simplified - this is a temporary measure whilst we look at the whole plugin ecosystem generally
You'll notice a small change in the cfWheels logo - don't panic, you're not going mad, we just thought it might be nice to have something new and shiny to look at.
Tom King and Tim Badolato are now part of the Wheels core team. "Per" still does all the actual real work :)
Onwards and upwards!
1.4 is released, which brings the usual host of fixes and improvements, most noticeably a few tweaks to get Wheels running with Lucee Server: CFWheels should now correctly identify itself as Lucee in the debug output, and various other (older) Railo specific tweaks should get applied. Note, if you're ever testing for 'railo' in the server scope on Lucee, it will return as true.
A couple of other changes might catch you out too, noticeably removal of the h() function, and "development" now being the default environment mode.
Get 1.4 Now!Upgrading from 1.3x
ColdFusion on Wheels version 1.1 Beta 2 is now available for download.
The core team and community have worked together over the past few weeks to identify and fix bugs and make this awesome new feature set more stable. Thanks again to everyone for making this project so enjoyable to work with. We’re getting very close to being production-ready on this, so be sure to give it a try and provide us with your feedback.
I have been blogging about some of the new features of Wheels 1.1. Be sure to check them out and subscribe to my blog for more. :)
