Being a tech geek that normally wishes for something that doesn't exist, instead of actually buying all of the new tech I can find, I want Apple to build an iPhone Nano. I receivied an email from Apple promoting the new iPods today. They look awesome. But instead of making me want a new iPod, it made me wish for a smaller iPhone. I don't have an iPhone, but an iPhone Nano would be perfect for someone like me that doesn't care for all of the power of today's smart phones.
I've been looking at Twitter Bootstrap a little lately and, coincidentally, the WYSIHTML5 implementation that worked the best for me uses Bootstrap. I have tried to avoid CSS frameworks, but Bootstrap is very nice. I already use a CSS base stylesheet that I adopted from Xaraya, but I'm considering making a switch to Bootstrap. I started out with the open source community designing themes for CMS', so I have put a lot of thought into Clay's theme system. I want to make it easy to design themes for Clay and I think using something like Bootstrap will make theme development faster and easier.
I've pushed some Blocks app updates to the Clay repo that allow you to use Blocks in a theme. I updated the Simplestyle_4 theme's page template and have been testing the new Blocks. They work very well and it is a fairly light-weight implementation. I have a few things I want to try as far as bottlenecks go, but for now I can't complain. The block groups actually use the Application Component class, just as a regular application component does. I was on the fence about implementing them that way, but it seems to not bottleneck quite as bad as I feared. My only real concern is battering the database with privilege queries. I have a few things I want to help there, but I may have to tweak the privileges processing a bit if I can't otherwise cut down on queries.
I updated an app I started farily recently named WYSIHTML5. I am using the codebase from https://github.com/jhollingworth/bootstrap-wysihtml5, which has a really nice implementation of WYSIHTML5. You don't have to install the app to use it, but once the editors service is fully implemented installation will be required.
I changed the Blog app to use WYSIHTML5. It was using TinyMCE, which I like, but the new editor is much nicer. Eventually I plan to move TinyMCE into its own app and put it on the editors service. WYSIHTML5 doesn't have all of the plugins that TinyMCE does, but it seems to integrate better. The editors will be configurable in the future so luckily my preference won't matter that much.
I plan to keep pushing forward with Blocks and working on other stuff as I go along. I've got a lot accomplished this week and I'm really happy with the way things are moving along.
Just pushed several commits for the Blocks app to Clay. It now has the blocks manager, with the ability to add and edit blocks. I also created a test block named Text, which just shows plain text. Still some rough edges to work out and I may tweak the db design a little more. It is functional, to an extent. There isn't a way to display the actual blocks or groups of blocks yet, but that should be around the corner. Clay really makes development easy and fast. The services module is a huge time saver, otherwise I would have had to create two additional tables and write the backend code for them. Instead, I got to reuse what is already there, which was the whole idea in the first place :) Up to three individual services (although the blocks are a little different, they don't actually use the service interface except to add/edit blocks), more to come and each saves at least 2 database tables, maybe more.
I think I've finally "completed" the Users app, for now at least. There are some settings and things to add, but those aren't necessary at the moment. There is always something to improve: tie in the interfaces better (for continuity), work on the form layouts a little, etc. Like everything else, I'll go back to it from time to time to make adjustments, as long as I don't find anything critical. Anyway, Everything I've talked about the last couple of weeks is in place, as far as the Users app goes. I still have actual privileges to code and stuff like that, but those are in their respective apps.
Time to start working on content! Blocks, Hooks, profiles, etc... yay! I'm probably going to try to finish the privilege classes and work on content stuff for breaks until those are finished. I still have some testing to do before I update this site, but I like the pace I've been moving the last couple of months.
I've pushed a lot of Roles/Privileges related updates to the Clay repo this past week. I'll have to dig through my TODO list, but I think adding the ability to assign Roles to Users is the only thing left in that department. There are some enhancements I want to do later, such as some informative content features that explain privileges and what they are for. The User manager still needs a little work, but I'll probably deal with most of that while I'm working on the Role assignment features.
I've also been pushing some updates to this theme (simplestyle_4), such as a fancier table styling and some improvements to the way the dashboard looks. The dashboard will get a big upgrade when Blocks and Hooks are implemented, so I'm not changing it too much right now. I also added a pseudo table style for using divs/spans in a table layout. It looks exactly like a regular table, but it allows you to wrap cells in links and things like that.
That's all I've done lately, but I'm really happy with the way the Role/Privileges stuff has turned out. The only thing I have not been really happy with is the ability to debug ajax forms. I've wasted a lot of time, because a simple error some where isn't getting through and I don't know what is broken. I'm trying to figure out a better way to debug, not just ajax forms, but overall. I think sometime soon I will need to take a break from new features and work on a console or something that gives me a little more flexibility for debugging.
I have a few application Privileges I need to write classes for. I have the Users stuff to finish. Then I will start again on Blocks and some content based applications. I have a few shell applications to work on. I also want to build an application that uses the GitHub API, so I can start displaying some project information here. There's still stuff to do. Hopefully I'll be able to update Clay here soon, enable user registration, and make this a 2-way conversation again.
I've been a little quiet on here lately, sorry about that. I have worked on Clay some, but my family and I are getting ready to move after the new year, so it's been kind of hard to find time. I'll post where we are moving after I get my orders from the USAF, just in case something doesn't work out.
I've been working on the Roles and Privileges admin GUIs, some of the updates have been pushed to the repo. I'm worrying a little about how the privilege system is going to affect performance, the Roles hierarchy system may be a bit complex. I'm going with it for now, as I don't really have a better solution at the moment.
I've made some enhancements here and there, but nothing really major. The code base is getting a little heavier than I like, so I will likely be splitting up some of the code that isn't always needed. By code base, I mean the amount of code needed for a page to load. I'm trying to figure out a good way to implement the submodules to move some of the code out of the main module classes.
As I wrote in my last blog, I'm looking at some ideas for applications to work on. I'm adding an Editors service, so I have have more than just TinyMCE. I like TinyMCE, but I want to go a different route, something more HTML5 based. The Editors service will allow you to pick which editor you want, so TinyMCE will very likely be available. I've been trying to workout how to do the Blocks and Hooks, which will open the door to a lot of applications I've been putting on hold. One thing I've been bouncing back and forth on is an application generator. The Nodes in Drupal have been its bread and butter, so a way to create pseudo applications is going to be more of a requirement than an option, development-wise. Xaraya's Articles and XarPages modules also strengthen the case for it.
One of my ideas for an application generator is by using it as a component of the Apps application. It would basically allow you to piece together an application from a GUI and then generate some generic templates to go along with it. The generated application would then be listed as an installed app, but with a different status code to show it isn't a native application. The app could then be exported and imported somewhere else or used to build a native application. I have some experimental code that could be applied to implement that, such as the Object app.
I've been looking for ways to improve the Dashboard. I want to keep it simple, but as usable as possible. I'm thinking the Blocks will be a big helper there. I want it as dynamic as possible, but that also takes away from performance as well. Last, but not least, I will likely be moving toward a short url system fairly soon. I'm not expecting to use a strictly defined router or mapping system, as I had previously looked into. I may use something like that as a fallback system, but I'd prefer to allow each application to define it's URL schema. Too many things to think about at once :)
I've been working on bug fixes to fix anything left over from the transition to modules. I've fixed a few and there don't appear to be too many left. I will probably push Clay onto the server sometime this week and make sure there aren't issues with the code there. Once that is verified I'll upgrade this site to the latest version of Clay. I'm excited to see what the performance difference will be. This site runs a little faster than my local server and performance has improved quite a bit on local. There are still optimizations to do, but I've tried to work in as many lately as I could find time for.
I'm probably going to be splitting my development time a little more that I have been lately. I have a few application ideas I'd like to push out, but there are still project goals to finish as well. I want to do some social apps and maybe something that works with the Github API.
Once the Privileges are finished on the administrative side I'll enable user registration here, followed shortly by adding comments functionality to blog posts. The comments system may be temporary, as I plan to expand that quite a bit once the hooks system is finished. I'll try to put in some temporary stints that will allow me to simply open it up to hooks, but I may be able to just make it simple enough to convert, it later on, to a newer system.
Have a Git repo that is getting rather large, from multiple deleted branches and merges? Use "git gc".
git gc is the garbage collection command and frees up space by removing unneeded clutter in the repo. It reduced my local Clay repo from 19mb to 12mb.
Over the past month and 6 days there have been 127 commits to the Privs branch, all of which have now been merged into the Master branch. There had only been 77 commits to the Clay repo since it was created on May 22. Clay now features a module system, featuring several modules that can be used within any application platform built on Clay Framework. ClayCMS has been merged into Clay, simplifying the naming scheme. A new privilege system, which was the primary reason for the creation of the Privs branch, is now in place and awaiting an administration interface.
The past month has by far been the most code I've written in a long while. The merge brings changes to over 850 files, most of which have been cleaned up and commented better. There are still a few glitches, from the Privileges system change and the move of Application APIs to Module APIs. Clay also is transitioning toward full compatibility with Doxygen, a documentation generator.
Prepping for Merge
I've been doing some premerge audits to make sure I haven't missed anything in the privs branch that will require a lot of rework from the master branch. I try not to make big changes to the code base within the master branch, especially if it is something that makes it unstable for an extended period of time. I've pushed a lot of code to the privs branch since my last post. I've totally deprecated the ClayCMS library, all of it has been replaced by modules or built into the Clay library. I've cleaned up a lot of code too, but there are still some applications that are not commented or cleaned up. I removed the Security application, as that was mostly used as a setup application and modules have replaced it. The admin backend for privileges management hasn't been implemented, but that can easily be added into the master branch. It is the continuing end to the current goal at least.
I need to do some testing to make sure the new module installer works correctly and I've correctly implemented the setups for those. Modules have replaced a lot of functionality of both libraries and applications, with applications becoming dependents. The goal is to build up modules, so applications are lighter and implemented using existing code from modules. The modules also allow developers to create application platforms ontop of Clay and use what they need from existing modules.
I'm weighing my choices for the next step, but I will likely work on Blocks and User Profiles next. There's plenty to do, but I think those are a logical next step. There are a lot of core features to add, including Data Objects - used to create pages and applications more rapidly, including built in CRUD; Hooks - a generic service type that can be used to extend application functionality; Logger - used to audit for error messages, user activity, optimizations; and Debugger - visual data display, associating output data to templates, to name a few. There are lots of applications to be created and finished as well. The next step will likely be Blocks, which will be either a service type or a specialized application controller.
By this time next week the privs branch should be merged back into the master branch in the Clay repo. This branch has brought the most radical changes to Clay in quite some time. It features a new module system, with many former ClayCMS libraries now acting as modules. The modules are the last part of the work left to do, other than the usual pre-merge audits. Modules will support dependencies and work on demand. If an application uses a module, it will be set up automatically, including configuration files and database tables. The privileges system, which was the purpose of the branch to begin with, allows applications complete control over the privileges they provide and what they allow.
Finally, a lot of effort has gone into improving code readability and commenting every file. By the time this branch is merged into the master branch, every file in Clay will have been touched. I'm working toward defining coding standards and recommendations, while implementing those standards into the code base. This branch has obviously been more than just about privileges, but most of the changes were solutions for needs brought to light by the new privileges sytem.