L&M Realty Group -


26 Nov 14

5:45 pm

Clay Social Network

In January 2015, I will be launching a social network built on Clay. It will start out as a single site. From there it will grow into a distributed social networking platform. More details and specs to come. The site will open in limited alpha and move to beta once other sites can join.

26 Oct 14

5:39 pm
I finally got back to working on Clay some more.  The Plugins app/module are almost finished, but I haven't pushed them to the repo yet.  There is still some work to do and a lot of testing left.  I've been adding a Core API to applications that will provide outline information without having to call individual application APIs, such as: item types, items, fields, etc.  This API will also soon handle routing for short urls and an extension of it may be used by the menu/navigation system.  It is also required by Plugins to utilize Hooks in applications.

Unfortunately, I didn't get to work on anything tonight because my daughter's laptop (my old laptop) crashed and I'm trying to do a backup and restore.  

There are several updates I want to do to Clay before the 1.0 release coming up.  One of the things I really want to do is upgrade Bootstrap to the latest build, but that will involve changes all over the place.  That may end up coming a little later, as I don't see any critical changes, but I would like to migrate to it sooner than later.  The longer I go without migrating the more that will require updates.  I also want to do some restructuring in the Clay libraries, but again I may push those to a supplemental upgrade.  

My plan right now is to push forward with Plugins, get the menu system in place, and implement short urls.  I plan to have a few publishing applications available for 1.0 and some supporting plugins to go with them. I will probably take a little time to evaluate how long a Bootstrap migration will take and then decide when to put that through.

Right now I'm hoping to release Clay Framework 1.0 just before 25th December and Clay 1.0  just after 1 January.  I'm thinking it's doubtful I'll have a lot of documentation for either one.  I'm actually hoping to have a lot of the documentation built into Clay and the framework will mostly start out with source generated documentation anyway.

My real job is keeping me really busy this week, but I'm hoping if I can manage to focus a little on Clay each day I will be able to finally finish my push toward 1.0.  I really want to move on to building with it and not just in it.

06 Oct 14

5:35 pm
Alright so I haven't done a lot of work on Clay lately, but I have been really busy. Here are some updates. In August I started a new hobby: homebrewing beer! So far I've bottled a wheat beer and a German-style lager and I have a Scottish red and a Belgian white almost ready to bottle. The next batch will be a try at a Belgian dubbel and then probably another lager. By far my favorite hobby of all time. Also in August I went on a road trip to Slovenia, Croatia, Austria, and Germany. We stopped in Munich for a few days, but Pula, Croatia was by far my favorite stop. If you ever get a chance, go to Croatia. I live in Italy so it wasn't far of a drive for me. I also found out I made Tech Sgt (Air Force) so I get a raise in either December or January. On top of that I have been promoted early so I have my own shop now. A little nervous about that part, but I have a lot of background knowledge so hopefully it works out. I was supposed to get a promotion in November to a shop chief position, unfortunately in some ways at least things change so I'm taking on a new role where I work now. This past weekend I went to Destination Star Trek 3 in London! Was awesome! I took my wife, she's the Trekkie, but I really ended up having a good time. So, back to Clay. I have come to the conclusion if I keep building it for someone else, no one may actually use it. From now on I'm going back to the original intent and building it for me. I plan to still release it to the public, but if someone wants something different out of it they will have to help. It's time for me to start building with it and not just on it. With that being said, most of the features I've wanted are what I've discussed before. I'm just not trying to tailor it as much to what I think people want to use. It's been a fun couple of months!

19 Jul 14

5:35 pm

Clay RFC Library

In effort to begin building up documentation of Clay, I've added an RFC repo under Clay. This repo will hold Requests for Comments files that outline the project. They are intended to open the project up more and provide developers a means to contribute intellectually to the project. They are also intended to be used as a roadmap tool to guide Clay through stable versions.

5:24 pm

Clay Application Core Library

An addition to application requirements is being implemented. Apps will be required to have a Core class in their library folders. This will be used by Clay core libraries and modules for supporting system functions. Eventually it will be used for routing short urls, menus, and breadcrumbs. Initially it will be used for hooks. A generic class will be extendable from the core to simplify the process.

05 Jul 14

8:39 pm
I've been working on the Dashboard side of Plugins. I should be pushing that out to the repo Sunday. After that I have to add some utility libraries for apps to declare itemtypes and itemids. Those libraries will also be used by the menu and other things. The menu is the next major task, but we're not quite there yet.

04 Jul 14

6:02 am
I was able to install a sample plugin in Clay, but I have not finished the UI in the dashboard for managing and hooking plugins yet. I've been going back and forth a little on the base class for plugins to use. I hope to figure that out tonight or tomorrow.

27 Jun 14

8:32 pm
Hopefully Saturday I'll have a Plugins functional and a sample plugin finished so I can do some testing. I'll still have to do a lot of work in the Plugins application, but that is stuff I can take a little longer to iron out. The first official plugin will probably be part of a Comments application. I'm still trying to decide if I want to use a 3rd party service for comments or write my own. I'm leaning toward writing my own. I wrote one about 7 years ago, if I do, I at least have an idea of how to do it. Once Plugins are working, I have a few directions I can go from there. The form plugin will be part of the objects app, which is a 1.0 goal. I also have the editors and dashboard to migrate from services. There are several base apps I want to make, such as articles, a photo gallery, a forum, categories, and a solid menu application. I'll more than likely jump around a little and work on cleaning the code base up while I do all of that. Plugins are going to be a little simpler than I originally planned, as far as complexity goes. It's going to take some testing to make sure there aren't any hidden bottlenecks though. Progress continues :)

26 Jun 14

5:29 pm

Clay SubModules

I try to build toward speed first. It's not always the sexiest approach, but sometimes smaller is better. In this case size doesn't matter. One of the features of Clay's module system is the ability to plug in submodules that act like on-demand APIs. The best way to use them is to structure a module's base class toward use cases instead of direct need. For instance, the Plugins module has a Get() method that pulls in a submodule class object. Now an entire class of methods are only loaded when I need to use Get (). It also has methods for implementing a hook or installing a plugin from an application. Without submodules over a dozen methods would all be in a single class, most of which only get used a fraction of the time. Why load all of those methods when they likely wont be used? SubModules make this happen on-demand, with very little base module code. Today I expanded SubModules capability by adding a new class that supports object classes as SubModules as well. Previously only static classes could be used. See the library/Clay/Module folder to view the code. The API class supports static classes (to stay inline with other Clay functionality) and the SubModule class supports objects. The Setup module employs similiar functionality, but without using SubModules (currently). Clay may have a few bottlenecks here or there, but the base is by far the fastest framework I've seen or used and that's sexy.

25 Jun 14

4:01 pm
By the I posted my 200th blog entry here. That has to be a record for consecutive posts on a single CMS :)