Easy to Create, Easy to Change - Easy to use!


Interface functions and forms


Started by wilmer raul contreras riaño
Search
You will need to Sign In to be able to add or comment on the forum!

Interface functions and forms

I have long worked with DataEase Windows from version 6.52 to version 7.2.947, and I saw a flaw in the handling of forms and versions that can not be given options for buttons Minimize, Close, for disable power as in almost all the other programming tools, that if I give a size to form the end user can not expand, when I create a menu for an end user can disable an option or more as required, modal windows, that if I have an open form can not open another until I have open closes, another requirement is that if I have a button or any other object you can disable according to a decision. All these cases I am mentioning them I can do it but buying a DLL to a Canadian company and the DLL Compuwizard WinzInterface called, my request or recommendation is that this can be done directly from the forms DataEase form options. With the new version of DataEase 8 this will be possible? Or directly DataEase definitely can not do this kind of settings for more efficient form? Thanks for your feedback
Written by wilmer raul contreras riaño 30/10/12 at 14:48:22 DataEase for Windows 7.x

Re:Interface functions and forms

Hi again Wilmer. "DataEase for Windows gives and it taketh away..." It is not a development tool, but an RAD framework. You get a lot very quickly if you play along with it, but if you want everything to work exactly the way you want it, you spend a lot of time trying to work around it, and so far you would mostly fail in beating it. OML was an attempt to open it up and give the users more programming control, but it turned out to backfire big time. DataEase wasn't designed to allow users in at this level and a lot of GPFing and misery was the result. In DataEase 8 we go the opposite way. We haven't removed OML, but we haven't fixed it either and we don't recommend anyone to use it. What we have done instead is to add a lot of new functions that can be used directly in Field Derivations etc. Some of them are SetFocus(), SetColor(), SetValue() and SetStatus(). The functions mentioned above will simply Set focus on a field or a button, change the colors of a field, button etc, Set a value in a field from another field or button etc, or disable editing of a field or clicking on a button, hiding it, enabling it and showing it. We also "kill" the current window hierarchy model, and replace it with Tabbed Maximized document where the Record object will be centralized in the form object and dialog windows(Normalized), they can be opened as normal windows or modal. This way the user will get a better understanding of the flow of the application, ant the app will function much better in different environments. We have also create a whole new world around Memo fields, where you can use them for programming/exporting/importing/printing/web and all kind of manipulation etc. You might not have liked Memos pre. 8, but you will love them in 8. All this said, DataEase 8 is still DFW so it will first and foremost be a RAD tool where one can make an advanced app quickly, and change it quickly. DataEase 8 will be a great product for what it is meant to do, but the real new DataEase is DG3. This website is 100% made in DG3, and in DG3 you can make anything you like exactly how you like it. DG3 is DFD on steroids, but with no limitations. You can use the PRISM8 layer for what you want, the Transaction Layer for manipulating and filtering the PRISM layer and on top of that you have the full power of Ajax, Python, Django, HTML5, CSS.... Biggest problem with DG3 at the moment is that it is such a giant leap forward, that we can't keep up with documentation and development resources to support it. At the moment we concentrate on releasing DataEase 8, but after that all the marketing/product/documentation resources will focus on getting the DG3 range out there. The first step will be a development meet in London early next year, followed by one in New York. There will be limited spaces, and partners will have first denial. We have a pool of systems to be developed in DG3 on back order, and the developers that qualify will be offered to take on this work.
Written by DataEase 30/10/12 at 18:12:36 DataEase for Windows 7.x