Dlayer reaches milestone two

I started Dlayer in 2008, so much has changed in the last seven years, the internet as a whole, mobile apps and devices, web browsers and my life. I have been married for four years and now have a two year old running around the house causing mayhem, two things that I never expected to happen seven years ago.

There are however two things that have remained constant, the first being my determination to complete the Dlayer alpha and the second being the milestones I set to track the development of Dlayer.

I set five major milestones for Dlayer in 2008, I needed five markers by which I could measure my progress, seven years is a long time, an eternity. On the 26th May 2015 at 12:08 with release v0.75 the second milestone was reached.

It has not taken seven years to get to this point, if you check the ‘History’ page on Dlayer.com or G3D Development you will be able to see that development on the current version didn’t start until 2010. Five years is still a long time but as I have written before, I’m working on this project in my own time at my own cost, under those terms finding development time can be very difficult, especially with a young child.

It will not take two years to hit the next milestone, that I can guarantee, the tasks for the third milestone are all in my short term development plan and according to my planning tool it should be reached within the next four or five iterations assuming my design is solid, obviously I am not going to give a specific timeframe here, anytime you set a date…well, you know what happens.

Listed below are the five major milestones for Dlayer, I don’t know what is going to happen once milestone five is reached, I can only hope, I do however have a suspicion that before anything else, my wife will order me to take a break.

1st Milestone (1st Feb 2014): Modules communicating

There are many modules, or designers in Dlayer, v0.12 was the first time that more than two of the designers were communicating with each other. A content page is based upon a template created in the Template designer and forms can be imported from the Form builder into the Content manager as content items.

2nd Milestone (May 26th 2015): Images

Although it is possible to create a very nice looking focused web site that does not use any images it is rare, in my opinion, images are a necessity on the web. With v0.75 images became a reality, the basics of an Image library are in place and images can be inserted as simple content items in the Content manager.

3rd Milestone: Dynamic content (Form builder and Simple widgets)

Data, data, data…..this will be the point at which parts of Dlayer consume user data, a major stepping stone to milestone five.

4th Milestone: Simple web site

Dlayer isn’t very capable if it can’t easily link pages together to create a web site.

5th Milestone: Complex widgets

Almost anything is possible with complex widgets.

Dlayer – Major milestone approaching

The last time I wrote about reaching a milestone was back in February, Release 0.12 was a big jump towards my goal because three modules/designers were communicating with each other.

The next milestone revolves around images, in the early v0.50s I will start working on the first tools that use images from the Image library, initially that will be adding a background image and adding an image as a content item.

Why is this such a major step?

Once the first few tools that use the Image library are developed the quality of the templates and content pages that can be created with Dlayer jumps massively.

After images the next major milestone is widgets, everything up to this point can be regarded as the groundwork for the Widget designer, that is the real Dlayer.

Dlayer – Release 0.12

Major milestone release, three modules are now communicating with each other, much more to do but glad to be at this point finally.

This version allows a form to be imported from the Form builder into a content page as a content item.

When importing a form the user gets to define the size of the form container and the padding around the form. If a form is selected the user can edit the values.

Forms are attached by reference, any changes made to the form in the Form builder will show immediately on all pages in the Content manager that have the form attached.

As per all the previous releases forms don’t yet work, they just display the assigned field, forms will start to function later, I need to work on the layout and styling tools first.

The container width modifier has been updated to support the form content item, it uses the same rules as defined for a text area, if required, forms will resize in relation to the page block they have been attached to.

The development plan lists ‘some’ of the development work upcoming for the form builder.

Developing the import form tool exposed a couple of issues with the base tool system, specifically tool and content type strings not always matching. I patched the app to enable me to make this release but I now need to concentrate on making the corrections to the base system, that is what the majority of the next release will focus on, think of it as 12.1 🙂