Improvements - need your feedback!
We’ve pushed some super enhancements over the last few weeks and I’m really pleased with them, but there’s more that I find myself wanting to do: mainly conveniences, to improve developer performance, but some of it to improve application performance too.
Route Here, Route Now
Routing within a web framework has always been up for debate in my eyes. Until recently.
EddyCore now just Eddy
That’s right we’ve merged the core branch back into the master branch. This means, we’re rolling with the core as the main branch of the framework. If you need a skeleton for your app, you’ll need to grab a copy of eddy_app. We’re going to do a demo app to help with getting new projects off the ground: a basic blog built on Eddy. So look out for that real soon!
Hi Matt, Interstate, and Flexible Models
First of all, please welcome the second developer to Eddy’s team, Matt (dVyper). He’s already started pushing some good changes and fixes to Eddy, including a dirty typo I made and some new functionality - the ability to use ‘IN’ in your Model::get() ‘WHERE’ clause!
Related to that, we’ve been phasing out string ‘WHERE’ clauses in favour of arrays as it allows us to apply some neat conveniences. But you can still use a string clause (for now), but you need to remember to escape any variables used in them, especially if they could be tampered with by user input.
We’ve also added a much-needed feature: explicit table referencing in models. This is so you can create models and make them work with a table that doesn’t match the name of the model. You may find that useful in some situations.
Roadmaps
This leads me to my next main point, roadmaps. I’ve tried to explain clearly on here in the past exactly what the goals are for Eddy’s development, but it just doesn’t cut it. So we’re giving Interstate a whirl. You can see our roadmap for Eddy by clicking on Roadmap in the menu.
If you want to get a quick eye on what we’re working on in Eddy or what we’ve got planned, take a look at the roadmap. If you want to suggest features or comment on any of the planned features, check out the Issues section on GitHub.
Well that’s all for now. Look out for more developments very soon!
To continue making things easier, we’ve set up a separate GitHub project for the skeleton of new apps built on Eddy. All you need to do is download or fork it to get your app set up.
We’ve done this to encourage the use of the core centrally to all of your apps. That way you can build multiple apps on one version of the core, if you so desire.
This centralised approach also helps us by keeping the core separate from your app code… so there’s no danger of us overwriting anything in your apps when you update your version of the core.
