I'm very (to the power of one million) happy to say that after a couple of weeks of not working on ZPE after feeling very despondent about it after spending a long time searching for a bug, I'm glad to say that I have finally fixed it and it only took me a few minutes tonight.
The issue affects all of version 1.4 from version 1.4.2 onward due to the bug being in the LAMP parser. This bug was down to the fact that if a single variable was part of an expression it would attempt to look at the variable as a value, not as an ID. This fix is marked as being crucial to the success of any version of ZPE, so please ensure you do not use version 1.4.5 any longer and update to version 1.5.0.
There are still things needing done in version 1.5.0 to make it work perfectly, but I'm getting there now.
Note as of tonight, the following needs to considered:
$v = 12 $x = 10 print($x * $v + 12)
This will not give 132 as expected. However, the following will:
print(12 + $x * $v) print(($x * $v) + 12)
Future versions of ZPE are fixing a lot of these bugs, but I will be adding the Typo system to the next major version of ZPE as well.
Since the development of JBlogs (now BalfBlog) back in August 2014 began, I have worked tirelessly on making my blogging system flexible for everyone. It matters to me not that it may never get that many users because by developing this I am developing my own skills whilst developing an excellent blogging system I can use on my other websites and future websites without any hassle.
Developing BalfBlog has become so easy, especially due to its MVC design pattern that I have adopted into it. But the development of BalfBlog has not been easy from the start. In fact, when BalfBlog started its core aim was to integrate completely with any website. The way it worked was to integrate both the front end and the backend (or dashboard as it is now known) into any website. Unfortunately, this was a huge job for anyone non-technical to setup and it was too much for me to develop further without any real reason.
After talking with some potential users I got a lot of feedback stating they liked the fact that the front integrates well with any website, but if the backend was complex to develop then they'd rather that the backend was easy to use and if that meant sacrificing integration with the website for a backend then so be it. I followed this feedback and decided to move to my own custom designed Dashboard. This is the Dashboard you can see now if you have trialled or used BalfBlog.
The development of this new Dashboard allowed me to redesign the whole of the BalfBlog backend to sit comfortably on the object-oriented balfblog.php file that manages all of the main operations of BalfBlog. The redesign also allowed me to develop the backend in a semi-MVC model, which makes the development of BalfBlog so easy.
However, the purpose of this post is not to talk too much about what makes BalfBlog amazing, but it's to ask what more you'd like to see in a blog. This year, particularly the last two months and this month, there have been a huge number of very useful features come to BalfBlog 2.2 (version Klebb, after Rosa Klebb) that have made BalfBlog exceptionally powerful and useful. The majority of those have focused on the social side of things like integration of OneSignal's API, allowing us to utilise push notifications and social buttons on each post, allowing users to quickly share a post. Unfortunately, I am beginning to run out of ideas for features for BalfBlog. I am looking to my users and readers again for more ideas! Test out my demo version here and let me know what you think by using the contact form on my website.
I will be holding BalfBlog development until the new year, I hope that by then I will have a good idea as to some new features people want to see in the next version. Also, I'd like to know, should I upload BalfBlog to GitHub soon?
December has been a month about bringing notifications to BalfBlog. This month has brought quite a lot of new features that connect with the users of the blogs.
First of all I added push notifications towards the end of November, allowing users to quickly subscribe to push notifications. Users can still subscribe by email using the my_blog/subscribe/ URL. On top of this, notification frequency can be changed so you don't spam your followers.
Secondly, I have finally added social media buttons for sharing. This is completely controlled by BalfBlog, so you don't need to worry. All that you have to do is style the buttons and set them to appear from the settings controls.
Take a look at my blogs to see exactly what has been done.
I am not saying smartwatches are finished, but if you look at the figures they are hugely on the decline. According to one report, only 2.7 million devices were sold in quartile 3 in 2016, with Apple still at the top with 1.1 million shipments. Garmin is the only manufacturer to be actually increasing market share, with Apple being the biggest loser here.
The thing with smartwatches is that most people probably do not need them. This is the main reason behind me not buying one because I could see it becoming something that would never see any use. I understand it saves people time when you get a text because you don't have to reach for your pocket to get your phone, but that just doesn't appeal to me.
Now then, the question is, how much longer will Apple continue to make smartwatches? Sure when Apple Watch 3 comes out it might attract a few million customers, but Apple Watch 2 failed to amaze the world, instead just leaving a disappointed feeling. According to the original report, Apple's Q3 sales have not been great for the Watch, which reinforces the point made by Trusted Reviews about its lack of new features. At the moment, sales of the Apple Watch 2 are more likely to be to new users than original buyers, since the second iteration doesn't add a massive selection of new features, and I guess the same will be the case with the Apple Watch 3. Once everyone owns at least some smartwatch, it will be very difficult to sway them to another one - it's just not like the smartphone market.
BalfBlog now features a built in 'related posts' tool. Nothing needs to be changed to have this in an existing blog other than one setting needing changed to enable it. This new feature makes it even easier to generate your own related posts section than I had done before. Simply turning the toggle to on will then make BalfBlog auto generate this after each post.
It's a very powerful feature that will help generate more readers for each post.
ZPE 1.5.0 is finally just about ready. The main changes in this version focus on backend (compiler) side things. In particular, the way in which the return function is compiled, evaluated and allocated a byte code has completely changed. For a start, it is no longer considered as a function but as an actual language token. This means that it is also allocated a byte code when translated to byte codes.
As well as this, recursion has been made more efficient than before and the call stack has been expanded. Overall, this is the best release of ZPE to date. I hope you find it useful too.
Today I finished the backend of BalfBlog polls. You can now make polls straight from the dashboard.
It's easy enough to create polls from the BalfBlog dashboard, but it is my intention to make it even easier in the future.
For now, you can simply insert the information at the end of a post in the Poll section. Options should be one per line and should not contain the new line character. Polls will then be generated automatically.
As well as this, I am working to change the system in which users who do not have .htaccess or web.config support (Apache or IIS servers) would utilise the system.What this means is that instead of accessing posts through /posts/post-name you would access the post through some URL parameters like ?nme=post-name. This will make it more flexible but it is not the only way in which these users will be able to access the pages. I will be trying it out on my own IIS web server soon and will keep everyone up to date on this.
In January of 2015, I redeveloped the backend of my website and released my DragonScript powered website. DragonScript is not really even a programming language or anything, so the name is a kind of misnomer, so I wasn't entirely sure about it, but I kept it anyway and it's my plan to keep the name.
My latest changes will be known as DragonScript 2.0. This is a backend change that should not affect the front of my website. However, it is a huge change. Part of this change is developing my old BalfPHP file into a more modern, object oriented version. DragonScript 2.0 focuses on a much cleaner and a more efficient, as well as overall faster, development that will focus on what's actually needed to make my website function and removes a lot of the ugly bits that were a part of it before. As well as this, DragonScript 2.0 utilises an object oriented approach.
As part of a few fixes I laid out on my own website, I have decided to updated both BalfBar and BalfBlog today.
Most crucially, BalfBlog received an update that makes it more compatible with future versions of PHP. When it was written it was written for use with PHP 5.2. Now it is compatible with newer versions of PHP so you should have no trouble installing it on your newer installation.
BalfBar has now received an important update that adds more flexibility to the SASS code (and even provides all of the settings to rip off the menu from my own website) as well as changes that make the JavaScript more flexible.
BalfBar is receiving a big update this weekend!
This update focuses on changing the menu items from being absolutely positioned to fixed positioning. This will allow a lot of new things like scrolling (hidden overflow doesn't work well with absolute positioning, since the element resides inside it's parent, whereas fixed detaches it). The menu will still look exactly the same but the way the items are positioned will allow me to finally bring scrolling to the items and allows you to set a maximum height to the items.
As much as I am more a fan of green code (CSS) over the yellow code (JS) for design and layout, I feel that using it was more appropriate here for what is being done, since it will give a lot more functionality.
This is currently experimental since this change was implemented in next to no time (only took me about 30 minutes to implement) and therefore not tested enough yet. I will post more in my Project blog when more becomes available.
This update will become BalfBar 1.2.
I will be trying it out on my website soon too, so keep an eye on it!
