In a previous blog post, we showed you that documentation for methods has returned in the Explorer. Want to take things even further and use them as documentation for your components? In this blog post, we’ll show you how!
Sharing the source code of 4D components lets you customize them and make them your own! With project databases and the ability to share an application’s source code via a source control system, we’ve converted our 4D internal components into project databases and pushed the source code to the 4D GitHub account. It’s open to everyone, all you need to take advantage of it is an account on Github. Why did we do this? To make your life easier by keeping track of changes and modifications to both code and forms.
Since the delivery of 4D v18, a series of blog posts on how to convert and develop with project databases have been published. What about components? This blog post answers that question.
4D provides libraries to help you develop applications. One of these libraries is standard and contains preconfigured form objects and widgets, while other libraries are custom. The standard library is “read-only” and its behavior doesn’t change when developing project databases (with the exception of minor, cosmetic interface differences). You also have the ability to create your own custom libraries to save your own form objects or group of objects. In this case, a few changes have been made to make them even more powerful. The following is everything you need to know about these changes:
4D has initiated a new program to share the source code of internal 4D key components such as the 64-bit Quick Report, the date/time pickers, or even the 4D Write Pro user interface.
Sounds already interesting, but what exactly does it concretely mean for you? You always wanted to use the Time picker widget, but with a different look and feel. The 4D Write Pro user interface is great, but can’t fit exactly in your application, that is requiring a more ‘Microsoft Office like’ ribbon bar approach.