Argus Development Environment Shell & Tools for 4D – Jody Bevan
Let Jody Bevan take you on a tour of the Argus Development Environment (ADE). Jody has been a big name in 4D development since his days with JonokeMed, what used to be one of the widest used medical applications of its type in Canada. He has rolled that momentum and experience forward into his latest project, Argus ADE.
Use the 4D language to make your job easier: ADE is a fantastic tool for coding in 4D that speeds development up and makes corporate standard code. You will learn how to use ADE to mass change code, mass check code, and create reports about the application itself. ADE code checking highlights the code problem with a description and the rule that caused it to be highlighted. The developer just clicks on the line in the Listbox and is taken to that method so they can decide what needs to be done.
Managers of developers can see what code they completed on a day, how much time they spent on the code and use other tools to provide oversight into a project.
With the new commands in 4D, Jody found he could program far faster than before… validating code and easily implementing new standards. See how you can even use ADE to help generate billing details and invoices from the code itself and to provide document proof to the clients. Jody has added even more functionality in 4D v18R5 for opening up a form up that has identified code problems or has a flag that there are still things to do.
A demo database will be shared with the following functionalities and more:
- Create a menu via code rather than using the graphical menu editor we have known for decades.
- Open up a finder window for various 4D Resources, and logs that we create in our code.
- Process a method on screen with the purpose of declaring all local variables, removing non-used declarations.
- Writing to a method to change the code
- Having blocks of code that you can then add into an open method as needed
- Making the contents of objects much easier to read than as displayed in the debugger
- Having the Object Viewer display in compiled mode
- Creating a much nicer Method Explorer, that also contains additional information
- How to write your code so you can then write other code that will validate your code is written to your standards. Quality Assurance
- Determine the front most window in the Design environment, so you can automate modifying it.
This meeting is being hosted on Zoom. Click here to join…
Have comments or questions after the meeting? Either post them here or to discuss.4d.com.
If you cannot attend the live Zoom meeting, don’t worry! A recording will be posted to the 4DMethod Youtube channel after the meeting ends.