Library updates

I’ve just pushed three library updates, the Bootstrap 4 helpers library is now at v0.03, the Zend Framework 3 view helpers library is at v1.01 and the sister library which provides code completion is now at v1.06.

I’m slowly adding support for additional Bootstrap components, this time the alert component, details and links can be found at Transmute Coffee.

Dlayer, vNext

This is a cross post from the Dlayer.com blog, it is relevant here because their is a good chance I will be releasing new open source libraries related to the tools development.

Development work on Dlayer vNext is deliberately slow; I’m attempting to ensure that any and all of the core architecture issues I noticed developing version 1 get resolved.

I spent a considerable amount of time on the UI and UX for version 1 of Dlayer, very little of that will change for vNext. My issues with version 1 can be summed up in one word, modular, as in, the app wasn’t.

There are two parts to the problem; the designers were not modular, in Zend Framework 1 (modules were a bit of a hack), and two, the tools were not plug-and-play.

Modules

This one is easy, by switching to Zend Framework 3, and being careful as I develop, the modules can behave as real modules, turn them on or off, transfer to different apps, all possible

Plug-and-play

The tools in version 1 of Dlayer had too many hooks into the system; they could be disabled dynamically, but you could not drop a tool into another module or quickly remove the code for a disabled tool.

On paper, I have a new plan; and I am in the middle of prototyping to see if it solves the core issues.

The solution is complicated; it will take time to develop examples of each tool type. However, as soon as I am sure the design is right, it simplifies the rest of the app.

Simpler app

The tools in version 1 were solely data management within the designers, in vNext, this changes.

The tools in vNext are responsible for everything relating to the content item, including, how the content is displayed in the WYSIWYG designer. The app at this point is merely a vehicle to provide access to the tools.

 

 

Library updates and two new sites

I treated myself to a little time off after my contract ended, I’m back now and have a few minor updates.

There are new releases for two of my packages, v0.60 of the Zend view helper library and v1.04.1 of the Zend view helper code completion library. The view helper library now has initial support for the following Bootstrap 4 components;

  • Bootstrap 4 Badge component
  • Bootstrap 4 Button component
  • Bootstrap 4 Card component
  • Bootstrap 4 Jumbotron component
  • Bootstrap 4 Navbar component (lite)
  • Bootstrap 4 Progress bar component
  • Bootstrap 4 Multiple progress bar component

In the last week, I released two new single page sites, Transmute Coffee and Professional Coding: What to expect?, both are mere placeholders for now but will gain additional content soon ™.

Dlayer, ZF3 and Composer libraries

I’m cross posting this post on two of my blogs because it is relevant to both sites, my blog and Dlayer.

I started development of the second rewrite of Dlayer using version 1 of the Zend Framework, in the following years I concentrated on building Dlayer rather than the underlying framework. With the EOL of Zend Framework 1, I can’t honestly continue on this path.

I started to move Dlayer over to Zend Framework 2 early last year but never got anywhere; I’m am now in the process of moving it to Zend Framework 3.

What does that mean for Dlayer?

I am in the process of developing v1.17, which will be released, and I will probably release another version of two, however, from this point forward I will focus the majority of my time on the migration.

I am migrating Dlayer; I am not undertaking another rewrite, sure, I will improve a few things along the way, but my goal is to migrate to Zend Framework 3 as quickly as possible,

Composer

While I migrate my code, I am taking the time to review it. If I see a tool or group of functions that is not unique to Dlayer, I will try to pull them out and turn them into a composer package.

So far I have four composer packages in progress, a PHP Quill renderer, Bootstrap 3/4 Zend Framework view helpers, Zend Framework view helper code completion and a random grab bag.

You can check out my composer packages at packagist. I’m going to have a website to showcase all the packages, so far I have only purchased the domain, as soon as the first version of the grab bag is release I will work on the website.

Which rich text editor?

For a while, I have been thinking about which rich text editor to include in Dlayer, after considered review I opted for Quill, in the end, it came down to Quill generating data (deltas) and not HTML.

Unlike the other rich text editors that I reviewed this creates a problem, how do I display the HTML within the designer?

On Saturday I created a PHP Quill HTML renderer, it loops through the inserts and generates the required HTML. The renderer is limited, it only supports bold, italic, strike and underlines at the moment.

Eventually, I will add support for every attribute, for now, though, I am trying to get the renderer and Dlayer working, so I figured supporting those four was a good start. In the short term, I will be adding support for links, images, videos, lists and headings.