Dear Xailer users,
We are proud to announce a new version of Xailer. Bellow is an overview of its features:
Continue reading
Dear Xailer users,
We are proud to announce a new version of Xailer. Bellow is an overview of its features:
Continue reading
Dear Xailer and xBase users,
With the publication of FastReprot for [x]Harbour & Xailer we have prepared a great commercial offer with the aim of attracting others Harbour and xHarbour users who have not used our products, consisting of giving a full license of FastReport for [x] Harbour and Xailer when buying Xailer Enterprise. A savings of 300 euros which is exactly what it costs FastReport for [x] Harbour and Xailer.
Our product FastReport for [x]Harbour & Xailer can be used not only with Xailer, but with any other Harbour and xHarbour framework, both in GUI mode and console mode. However, under Xailer is where stands so shocking as it is fully integrated into the IDE.
The offer is only for new users from other xBase environments and Xailer 1 users that can not update to version 3. However, it makes much sense to buy an additional license of Xailer Enterprise for users who are still with the personal or professional version or for those who need more licenses.
This offer is available for a limited time until November 1, and we anticipate that will be unique (not happen again) and validity period will not be extended under any circumstances.
Best regards,
[Xailer team]
Dear Xailer users,
One of the most important features included on Xailer 3.1 is the complete support of Form visual inheritance. Until now Xailer included a limited inheritance visual support, where only the ancestor form could be given on its creation.
The inherited form incorporated all the controls from its ancestor form, but none of its properties or inherited parent controls properties could be modified. However the new controls included on the inherited form could. In order to modify any inherited control it should be performed on run-time or in its ancestor form.
We have always thought that it was an error to modify any inherited properties of the parent form. On those cases we believe is better to us the parent as a template, which is something Xailer already supports. But in fact, the functionality offered by our visual inheritance was indeed limited, because the strength of the our IDE visual design was useless on this cases.
On Xailer 3.1, we still lock parent form properties and controls, but we have open the design to all inherited controls of type container. This way we achieve that Xailer IDE is completely functional on those controls and we do not compromise the stability our actual inheritance system.
For example, all this operations can be done on inherited controls:
We highly recommend to have a look a the sample SamplesVisualInheritancehervis.xpj.
Xailer 3.1 show in gray color all the inherited controls on the object inspector.
We hope you like the approach done to visual inheritance in Xailer 3.1. We are really excited with the result and we will like to encourage all of you to use it on your next projects.
Best regards,
[Xailer team]