Today (24th of June), we released version 2.2. In addition to the documentation we have sent to our customers, here is a summary of solutions if you run into issues:

1. Make a backup of your project folders
   It is not mandatory, as PHsPeed maintains all kinds of backup files, but once loaded into the new IDE and saved, the file will not be loadable in older versions.
   
   
2. Project corrupt error
   This error message is usually caused when an older project is migrated. But easily fixed, at least in 99% of the cases. Go to the project source tab, and locate for double quotes: "You will see something like ^somekeyword=" this is some text", ^someotherkeyword... The solution is to replace the double quotes with a single one and/or remove the text. Save the project file and then reload the project.
3. RegisterOwner not found
   This error is generated when the deployed runtime is not refreshed. The first step is to go to deployment and purge deployed files. If you are using private libraries, redeploy the libraries. Then regenerate the code.

Release notes

Bugfixes: see bug tracker.
Full release notes: see this post

IDE

• Much cleaner interface, removed duplicate functions
• Upgraded XDebug client for higher performance and fixed a bug that could cause crashes
• New (context-sensitive) help function based upon HelpNDoc, removed Wiki
• Displays changed modules in the project tree
• Upgraded Chromium and homepage
• Setup for easy PWA applications
• Additional options in the application wizards

Components

• Grid component enhanced.
• More features like fixed header, events, recordable headers, etc.
• Modal forms enhanced, allows suppression of refresh events. Improved 'free use' outside Crud functionality
• New components for PayPal, YouTube, Vimeo, MP3, MP4, Database Export, Vertical menu
• Improved and upgraded components for Charts, DBTable, DB(Simple)Query, and DataSource

Note about PWA

All visual applications built in PHsPeed can be migrated into a PWA, using the PWA setup module found under projects. There are some misunderstandings about what a PWA is and how you can use them.

First of all, Apple is not fully compliant with the PWA standards. If you want to 'install' a PWA configured application on IOS, you must manually add the application to the homepage. That has nothing to do with PHsPeed.

If you create your application with a desktop in mind, you might need to redesign your forms so that they will look good on a mobile phone. For instance, a mobile is not quite capable of showing massive data grids. This doesn't mean that you cannot use PWA for these types of applications, but for the best usability, you must design your forms so that Bootstrap can resize them properly to display them right on smaller mobile screens.

PWA applications build in PHsPeed are still web-based applications that will only run when there is an active internet connection. If there is no connection, the home screen will notify and the application will continue to run once the connection is established.

Hi, and great to see you here! We are proud of our new website, and in the upcoming weeks, we will reveal a lot of new features that will be in our release 2.2. If you haven't already, we would advise you to subscribe to our newsletter to be informed when new releases come out or when there is something to announce. And no, we do not share your email with others, nor will we spam you with useless 'offers'. As you might know, we like to simplify things. No difficult license models, no 'special' promotions. Just a great product for a very fair price. No sudden 'huge' increase in pricing or other unpleasant surprises!

Talking about the pricing is not a nice subject, but we will increase our license price for new licenses as of July 2022. As every company, we too suffer from increased costs. We kept our pricing low for early adaptors, but currently, PHsPeed is competing with all the products out there, which means that we will drop our early-bird discount.

If you are already a customer, then you will not be touched by the new pricing. We keep our promises! But if you are new and want to save a few bucks, then this might be the right time to step in. But if you can't, PHsPeed will still be very affordable.

Then some good news. I will give you detailed information about the new features in the following blogs. But to mention a few:

• Improved user interface
  We started to work with a front-end designer, and the first improvements to the user interface already have been implemented. Our Wiki will be removed and replaced by a new help system powered by HelpNDoc. This allows us to concentrate all our documentation in one place and implement a help function within the IDE. A first implementation is already in place!
  
  
• PayPal
  We have added a new component to connect to the PayPal gateway.
  
  
• Charts
  We improved our implementation of ChartJS.
  
  
• XML/JSon/CSV output
  We have added a new component to export your dataset result in several formats. Just bind the component to the data source, and you're done.
  
  
• Vimeo, Youtube, MP3, Mp4
  We added new components to embed these formats into your PHspeed applications.
  
  
• PWA
  Yes, you read it well. Last but not least. As of PHsPeed version 2.2, you can create a fully qualified PWA application. For those who do not know what this means, you can have your web application look like an App. Users can install this app without needing an app store, and in fact, it is still a web application. But you will have an icon on your mobile that responds directly to the web app, without the url line. It's installable and to convert your application into a PWA is as you might expect from a low-code tool... NO CODING IS REQUIRED!

PWA's become more and more important lately. That is understandable because they have a lot to offer. But what are they?

If you are a developer and writing applications in PHP or another scripting language, you probably will have dreamed that it would be nice if you could run your application just as an 'app' on your mobile device. Building native apps for Android and IOS is not that simple. Some tools allow you to use only one code-base, but you need a subscription to the app store and need to share a high fee on your sales.

PWAs allow you to install your browser-based applications as a traditional web app on a mobile device, including a nice icon on the mobile desktop.

So what are PWAs?

First of all, let's start with the definition that you can find on Wikipedia:

A progressive web application (PWA), commonly known as a progressive web app, is a type of application software delivered through the web, built using common web technologies including HTML, CSS, JavaScript, and WebAssembly. It is intended to work on any platform that uses a standards-compliant browser, including both desktop and mobile devices.

Since a progressive web app is a type of webpage or website known as a web application, they do not require separate bundling or distribution. Developers can just publish the web application online, ensure that it meets baseline "installability requirements," and users will be able to add the application to their home screen. Publishing the app to digital distribution systems like Apple App Store or Google Play is optional.[1]

As of 2021, PWA features are supported by Google Chrome, Apple Safari, Firefox for Android, and Microsoft Edge[2][3] but not by Firefox for desktop.[4]

Nice definition, but how does it work? Well. First of all, a PWA must be able to run without a live connection to the server. So everything required to run the application needs to be in the PWA cache of your mobile device. That is a problem for scripting environments, as in our case, PHP runs on the server, not on the mobile. The PWAs are based upon the web browser, so the supported environment is HTML(5), CSS, and JavaScript. If you are a JavaScript developer, then you can come far. But for database access, you still need a server connection. To solve that problem, the PWA requires a fallback. If there is no internet connection, then the PWA must be able to handle that. 

Creating PWAs in PHsPeed will be supported in Q2/Q3

In terms of PHsPeed, we implement a PWA solution that allows you to enable all your PHsPeed applications into a qualified PWA. Suppose you start the application from a PWA-aware device (Android, IOS, Windows), then a splash screen will appear with two options: one to start the application and one to install the application as an app. If the user decides to install it, the application will be installed on the mobile device with the predefined icon. From that moment on, the install option will not be available anymore. The user can now start the app from his home screen.

If the internet connection is gone, the PWA will detect this, and the splash screen will reappear with the error message that there is no internet connection. There is an option to restart the application, which will work as soon as the internet connection is restored.

As a small disclaimer, we are currently developing this option so that the real implementation might be a bit different. And of course, if you already know how PWAs work, you can already deploy the PHsPeed application as a PWA. Using the PHsPeed implementation makes the feature available to anyone using PHsPeed.