開発スタッフがアプリ関連の最新技術やニュースをご紹介します。

Today, I would like to share about PSR called PHP Standards Recommendation which are also known as coding standards of PHP. Actually, PHP does not have coding rules and standards itself. Developers tend to create their code to be more maintainable & safer by using naming conventions and various coding styles. Some use frameworks like PEAR, Zend to standardize their code.

Just In Case If you don’t know about coding standards

Coding rules and guidelines ensure that software is:

• Safe: It can be used without causing harm.
• Secure: It can’t be hacked.
• Reliable: It functions as it should, every time.
• Testable: It can be tested at the code level.
• Maintainable: It can be maintained, even as your codebase grows.
• Portable: It works the same in every environment.

Standards are important for safety, security, and reliability.

Every development team should use a standard. Even the most experienced developer could introduce a coding defect — without realizing it. And that one defect could lead to a minor glitch. Or worse, a serious security breach.

There are four main drivers for using one:

1. Compliance with industry standards (e.g., ISO).
2. Consistent code quality – no matter who writes the code.
3. Software security from the start.
4. Reduced development costs and accelerated time to market.

In 2009, There was a conference about PHP (https://tek.phparch.com/). At that conference, developers discussed about their opinions on working PHP projects and their complexities upon them. Finally, they decided to create coding standards to follow. The name of that association was PHP Standards Group. They updated their name as Framework Interoperability Group(FIG) later.  You can see more detail about FIG here (https://www.php-fig.org/).

Currently there are 13 approved standards.

1  Basic Coding Standard

2  Coding Style Guide

3  Logger Interface

4  Autoloading Standard

6  Caching Interface

7  HTTP Message Interface

11  Container Interface

13  Hypermedia Links

14  Event Dispatcher

15  HTTP Handlers

16  Simple Cache

17  HTTP Factories

18  HTTP Client

If you are still curious to know about other standards that are currently reviewed, draft, abandoned. Check out this official link (https://www.php-fig.org/psr/).

By Yuuma.

Tweet

本記事は前回の「CakePHP フォームヘルパー(1)」の続きです。
前回はCakePHPの「フォームヘルパー」という機能を使用して、入力フォーム用のHTMLを作成しました。
今回はそのフォームを使用して送信(Submit)された値をコントローラー側で受け取る方法を説明いたします。

Tweet

Let’s say you have a website and you want to give your website as mobility experience to your customers. Well you have to consider the PWA. Let’s see how PWA can offer mobility experiences to consumers.

If you visit the website, you will get alert to add to your home screen for this website as a PWA application. If you accept it, the PWA will be installed to your phone and you can access the website through application next time. Cool , I know right !

Although PWA works across both iOS and Android, the specifications of Safari affect which functions iOS users can access. For Android users, PWA can be added via multiple browsers. Also PWA is a project started by Google, and it is quite more compatible with Android.

Let’s discuss some of the core attributes which are missing from common non-progressive web applications.

1. Reliable
   The app should be lightning fast when loading, it should be close to instantaneous and should also open when there is no network or fairly low-speed network.
3. Fast
   The scrolls and page transitions should be buttery smooth when the user is interacting with the web app. Everyone hates crappy scrolls.
4. Responsive
   The app should fit in all the different sizes of devices. The perfect web app should be like liquid, which takes the shape of its vessel.
5. Installable
   If we want to make web apps closer to the native apps, they have to be installable and should reside in the home screen along with other native apps, so that the user can access the PWA in one click.
6. Splash Screen
   PWA adds a splash screen during the startup of the app. This makes the PWA feel more like a native app.

As an addition, all you need to setup PWA is that you just have to know some Javascript. PWA has some important technical components which work together and energizes the regular web app.

1. Service worker
2. manifest json
3. And your site need to be in https.

These are the important things to setup your PWA.

Service Worker

Our web apps talk to the network directly and if there is no network, the screen shows the famous dinosaur. For the first-time load, the service worker stores the required resources in the browser cache. And when the user visits the app next time, the service workers check the cache and returns the response to the user before even checking the network.

Manifest Json File

The manifest file is a config JSON file which contains the information of your application, like the icon to be displayed on the home screen when installed, the short name of the application, background color, or theme.

Https

Service workers have the ability to intercept the network requests and can modify the responses. Service workers perform all the actions on the client side. Hence, PWA requires secure protocol HTTPS.

Here is the official documentation to build PWA from google.
https://codelabs.developers.google.com/codelabs/your-first-pwapp/#0

By Yuuma

Tweet

今回はCakePHPの「フォームヘルパー」という機能を使用して、入力フォーム用のHTMLを生成させる方法の説明をおこないたいと思います。

Tweet

本記事は前回の記事「CakePHP コントローラとURLの関連」の続きです。
今回はビューテンプレートの作成をおこない、コントローラとの値のやり取りをおこないます。

Tweet