Scribd
Upload
9 views5 pages

VB Odt

Uploaded by

quorsonlyfor
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
9 views5 pages

VB Odt

Uploaded by

quorsonlyfor
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
You are on page 1/ 5

EDITIONS

OF

VISUAL
BASIC

1. Learning
Consists of all necessary tools required to build main stream Windows Applications

2. Professional
Includes advanced features such as tools to develop ActiveX and Internet controls.

3. Enterprise
In addition to all Professional features, it also includes tools

INTEGRATED DEVELOPMENT ENVIRONMENT


IDE

• One of the most significant changes in Visual Basic 6.0 is the Integrated Development Environment (IDE).
• IDE is a term commonly used in the programming world to describe the interface and environment that we use to
create our applications.
• It is called integrated because we can access virtually all of the development tools that we need from one screen
called an interface.
• The IDE is also commonly referred to as the design environment, or the program.

Overview
In particular, VB has the following windows:

• Menu / Toolbar
This is the only element of the IDE which is always visible. You use it to select which other IDE elements to view and to add forms or
controls to your project. There are many other features which we will discuss later.(click to enlarge)

• Toolbox
The toolbox is simply a library of controls which you can place on your application. Once you've placed all the controls you need onto
your applications forms, you can hide the toolbox to make room for working in the other elements of the IDE.

• Project Window
This is simply a list of all the forms which make up your VB project. There are several kinds of forms which we'll talk about later.

• Property Window
We'll talk about controls later, but such things as push-buttons, scrolling text boxes, pictures boxes and other features of most VB
applications allow you to enter parameters which define how these controls work. In VB, these parameters are called properties. Some
properties can be entered at design time within the IDE, while others must be entered with code while the program is running.

• Forms
You add these to your VB application as they are needed. They are the windows which hold the various controls (buttons, text boxes,

etc.) which make up your application.


• Code Window
Like it's name implies, this is where you type in the code that VB executes. Notice that the heading of the window indicates with which

event the code is associated.

What is the Event Driven Programming Paradigm ?

Event-driven programming is a paradigm where the execution of a program is


determined by events such as user actions or messages. Programs respond to events
with predefined actions, allowing for asynchronous and responsive behavior,
often seen in GUI applications and distributed systems.

Advantages of Event-Driven Programming Paradigm


• Enables asynchronous processing, optimizing resource utilization and
responsiveness, crucial for real-time applications and user interfaces.
• Encourages modular code design, simplifying maintenance and scalability by
separating concerns and promoting code reusability.
• Enhances user experience by responding promptly to user inputs, delivering a
smoother and more interactive interface.
• Facilitates easier integration of new features or modifications, promoting
adaptability to changing requirements in dynamic environments.
• Components communicate through events, reducing dependencies and
enhancing system flexibility, making it easier to maintain and modify.

Disadvantages of Event-Driven Programming Paradigm


• Event-driven systems can be challenging to debug due to their asynchronous
nature, making it harder to trace errors.
• Concurrent events may introduce race conditions, leading to unpredictable
behavior and making debugging and synchronization complex.
• Event-driven systems may lead to inversion of control, making code harder to
follow and understand for developers unfamiliar with the design.
• A series of interconnected events can lead to cascading effects, making it harder
to predict the outcome and manage the system state.
• Continuous listening for events can consume system resources, leading to
potential inefficiencies in resource utilization and impacting overall system
performance.

Event-Driven Architecture (EDA)


Event-driven architecture (EDA) responds to actions like button clicks. In this
paradigm, events, such as “buttonClick,” trigger predefined actions. The user
interacts with the interface, and the system, following the Event-Driven
Programming model, responds dynamically to ensure a responsive and engaging
user experience.
Example: To demonstrate basic event handling through a JavaScript
EventDispatcher, prompting an alert using Event-Driven Architecture.

You might also like