So, how should one select a UI library?
What is the reason behind selecting a paid library?
Mr. Takeshi Hashimoto, Senior Project Manager, System Development Team, Development Division, Yayoi Going right to the point, we asked why they selected the paid Wijmo library for cloud services. The first point that came up was the "time limitation in creating controls from scratch," (Mr. Hashimoto). Then he mentioned the "evaluation and research that was done on three libraries."
Merits of Wijmo
According to Mr. Sawamura, the selection process has been going on since Wijmo 3 was introduced. They focused on the following things at that time:
- Appearance and functionality of controls
- Reliable support service
Issues in introducing Wijmo
There were some concerns as well in introducing a third-party component.
- Blackboxing third party components
- Handling the bugs in components
- Whether replacements are available on every version upgrade
- Learning cost
Mr. Kubo said that they have the following environment for cloud service development in Yayoi.
- IDE**：** Visual Studio 2015
- Web server/DB server**：** Azure
- Client**：** all-important browsers
- Framework**：** ASP.NET MVC 5, Wijmo etc.
Know-how about using Wijmo
Customizing Wijmo controls by inheriting
Using the helper methods
As mentioned earlier, Yayoi's developed their cloud service application using ASP.NET MVC 5. Mr. Kubo says, "We created helper methods to use Wijmo 5 controls easily through Razor, which is a view engine of Wijmo 5. Our engineers use these controls through helper methods only." There are some merits to this approach. Mr. Kubo first mentioned that using Razor makes it possible to restrict the editable properties and usable methods. "In real development, engineers can change in between development cycles, and not everyone is thoroughly experienced with the controls. In such a situation, restrictions can be added to the editable properties and usable methods so that usage of a control can be restricted to an extent. This way, incorrect use of the controls can be reduced. It is a main bonus in the team development environment." So, it is OK if programmers are not used to the client side, because they can call the helper methods in Razor," (Mr. Sawamura) Another benefit is that screens do not need to be changed while adding a feature to the control. "Most of the specification changes could be done by using control inheritance and helper methods. Along with that, we could also reduce the effort while maintaining the quality (Mr. Kubo).
.NET developers and TypeScript
Selection of technology