<html><head></head><body><div style="font-family:times new roman, new york, times, serif;font-size:13px;"><div><span><div>Hi</div><div><br></div><div>We have increased (to 20) the number of XComponents that can be cross compiled from Lazarus to HTML and updated our dropbox link to the source files accordingly. (see https://www.dropbox.com/s/7734e3nmys9gnv4/XComponentsDemo.zip?dl=0)</div><div><br></div><div>We are keen to get some feedback on the idea of providing a simple scripting and form design capability at run time for domain specific / embedded / or quick and dirty exercises that can then be imported into the full open source (Lazarus / TMS) IDE for later enterprise level development if that proves necessary. </div><div><br></div><div>We assume our XComponents are a simple subset of the TMS ones (with the addition of H and VBox components and associated alignment properties) and therefore it should be straightforward to provide an upgrade path from XComponents to TMS components (but not the other way). Do any of you that have worked with the TMS component set foresee any problems with doing this? Alternatively, should we be basing our efforts around the TMS set, or would this introduce licensing issues and take us away from the ideal of fully open source development?</div><div><br></div><div>Regards Steve</div><div><br></div><div>P.S. The current demo just shows the Lazarus compatible components we have developed, We are now using these to re-implement the run time layout editor that we previously circulated for comment in its non Lazarus IDE compatible form. We hope to be able to provide a demo of the new implementation of this shortly</div><div><br></div></span><br></div></div></body></html>