Envision VL Accelerator Frequently Asked Questions

To Download or Print the complete list of FAQs

View or Download our EVLA FAQs with MS Word to view or print the comlete list of Frequently Asked Questions.

To View a particular FAQ

Click on the Question below to view the Answer

  1. What is a Framework?
  2. What is Envision VL Accelerator?
  3. How is a Software Development Kit (SDK) different from a Framework?
  4. How are Templates different from Frameworks?
  5. What are the Levels of Complexity cared for in Frameworks?
  6. Am I limited to the "Look and Feel" of the Base Framework?
  7. How do you develop a system using the VL Accelerator?

    Go back to the Top

  1. What is a Framework?
    A Framework, as defined by The American HeritageŽ Dictionary of the English Language, Third Edition, is:
    • a set of ideas, principles, agreements, or rules that provides the basis or the outline for something that is more fully developed at a later stage.
    • a structure for supporting or enclosing something else, especially a skeletal support used as the basis for something being constructed.

    By extending this definition, Frameworks for Windows (the original name of VL Accelerator) can be defined as:
    • a set of programs, files, components, wizards and standards that provide the basis for the design, development, and implementation of large scale software applications.
    • a standard Windows based skeletal structure for supporting or enclosing other Windows based applications.

    2. Go back to the Top

  2. What is Envision VL Accelerator?
    VL Accelerator consists of 3 major pieces:

    • The Base Framework – The base executable environment that provides the structure and the basic functionality for the applications, modules, command bars, commands, menus etc. The base framework follows Microsoft's user interface guidelines, but can be customized to create a framework style of your own.
    • Frameworks Maintenance and Administration – A full system to Maintain and Administer System utilizing Frameworks. This system was built using the Frameworks For Windows itself and utilizing the Base Framework.
    • Frameworks Development Tools – Additional productivity tools to further simplify and speed up the development of your systems.

    3. Go back to the Top

  3. How is a Software Development Kit (SDK) different from a Framework?
    These 2 are quite similar. An SDK covers a broad spectrum of tools or kits to aid in the development of an application. A framework is simply a more defined type of SDK.

    4. Go back to the Top

  4. How are Templates different from Frameworks?
    There have been 2 approaches to generating Visual LANSA Code and components, either Templates or Frameworks.

    Templates are the same as they were in the 5250 days. Run a template, generate some code and compile. A good Template Driven tool takes into account the End User of the application, but not the development environment. There are some slight variations to take advantage of some of the features of a windows development environment such as using Re-usable parts. However a Template driven approach in the windows environment does not take even close to the full advantage of the environment. When developing for 5250, non-OO environment, templates were a godsend. Surround has over 50 of their own. In contrast, if you use a magnitude of templates to generate your Windows interface, then you may be unnecessarily burdening your development team and budget by not taking advantage of the Windows Environment. Yes, templates in the Windows world, where true OO techniques can be employed, can actually be a burden.

    Frameworks are just that, a framework of the application. It is a set of programs, files, components, wizards and standards that provide the basis for the design, development, and implementation of large scale software applications. A VL Framework provides a standard Windows based skeletal structure for supporting or enclosing other Windows based applications. A good VL framework removes a large majority of the underlying level of complexity inherit in a Windows environment from the developer and allows them to concentrate on the business requirements of the application. A good framework will take into account the End User Application as well as the Development environment to create it.

    5. Go back to the Top

  5. What are the Levels of Complexity cared for in Frameworks?
    The levels of complexity incorporated in most, but not all, frameworks are:
    1. "Glue-Ware" - This is probably most important piece and is the technology that holds the application together so that all the forms and objects can communicate with each other. "Glue-Ware" itself can be done many ways. Some good and some bad. If you are not careful, the "Glue-Ware" can make your application very limiting in how it can function and perform.
    2. "Look and Feel" - The Character of a program is determined primarily by its appearance - its "look" - and its behavior - its "Feel." A good Framework will allow you to determine your look and feel as well as maintain consistency throughout your application. This is probably one of the most difficult things for a team of developer to do without a Framework in place. The importance of the framework is also extended to future interface changes as the primary "Look" and "Feel" technology is in one central location. Change it, and you can change your entire system. Easy, Fast, and Consistent.
    3. Performance - An often forgotten aspect of development until deployment, when it is too late. This can be hugely problematic in the windows environment. If it is not cared for from the beginning, it can often require a major structural change in the code of your entire system. A Framework is critical for this because it centralizes the core performance areas so that as new technology emerges, it can be implemented into the framework and utilized throughout the system.

    6. Go back to the Top

  6. Am I limited to the "Look and Feel" of the Base Framework?
    No, not in the least. F4W maximizes flexibility by allowing you to easily modify the default standard Windows "Look and Feel" that it provides to one of your own.

    We realize that it may be very important for certain applications to deviate from the norm. For example, a training tool specifically targeted at very new PC users may need a more simplified user interface.

    Go back to the Top

  7. How do you develop a system using the VL Accelerator?
    Seven easy steps will have you on the way to developing a full system:
    1. Identify the Systems, Applications, and Modules to be developed (including associated Icons and Bitmaps)
    2. Create the shell system using the Frameworks Maintenance.
    3. Create the global components for a System
      1. Image Enrollment
      2. Logon
      3. Browser
    4. Create an icon to run the shell system.

    At this point you will probably have spent from 1 to 3 hours depending on how long Step 1 takes and you will have a fully functional Prototype of your system.
    1. Create the object components for a module (perform for each module as they are needed)
      1. Detailer
      2. Controller
      3. Explorer Bar (Search, Recycle Bin, etc.)
      4. Content Window
    2. Create the server side functions for a module (perform for each Content Window as they are needed)
      1. Position to
      2. Filter

    It will take approximately 1 to 3 hours per module, depending on the complexity of the data, for steps 5 and 6.
    1. Create additional components (These are the added bells and whistles that you may want)
      1. Help About
      2. User Guides
      3. Etc.

    You can have a fully functional prototype up and running in just a few hours and full system in just a few days!

Go back to the TopBack to top