HTML Editor

Synopsis
The HTML Editor is a rich-text HTML editor extension for VB.NET. Its intuitive user
interface enables even inexperienced users to edit HTML page content with ease. TheHTML
EditorisafullfeaturedWebdesigntoolforbeginnersandexpertsalike.Ahostofusefulfeatureshelpyou
createandmodifyWebpagesquicklyandefficiently,revealtheinsandoutsofHTML,andgiveyou
completecontroloverthedesignandstructureofyourWebsite.
AWebsiteisfarmorethanjustthefilesthatmakeitup,theHTMLEditoralsocontainsWebsite
Projects,acomprehensivesystemthatkeepsyourworkorganized.
Many of the icons on the tool bar can be found on most text editing (word processing)
programs. This page will cover some of the icons/tools which may not be as familiar to a new
user of HTML Editor.
For example, you can cut/copy and paste text from other applications into this editor and
formatting will be preserved. The Options Ctrl+C and Ctrl+V can also be used as shortcuts.

Module Design
Design, Source, and Preview Modes
Allow your end users to create and format content in design view with the help of
MstHtmlEditor's built-in tools, while your advanced users can work directly in the Source mode.
By using the Preview mode users can check how the content will be displayed when added to a
real web page.
Set Font and Text Properties
Allow your users to painlessly create and format text using the familiar Bold, Italic,
Underline, Justify, Indent, etc. buttons. Let them set different font names and sizes and text and
background colors, as well as style existing HTML elements.
Load and Save Documents
Load html documents into MstHtmlEditor from a file, And likewise, you can save
documents into a file.
Insert and Manipulate Pictures, Tables, Objects
Insert and manipulate various types of objects in the document including tables, images,
hyperlinks and symbols etc. The dialog boxes allow you to modify all properties of the inserted
or edited objects. With mouse actions, move and resize objects directly on the document in
Design mode.
Context Menus
Allow quick modifications of images, tables, paragraphs, and other elements with the
help of MstHtmlEditor's contextual menus displayed upon a right click of the item while in
design mode.
Printing Support
Calling the ShowPrintDialog method has the same effect as choosing Print from the
Windows Internet Explorer File menu. The ShowPrintDialog method can activate the Print
dialog box, prompting the user to change print settings. The ShowPrintPreviewDialog method
lets you see the web page before you print so you can avoid printing mistakes.

Multi-level Undo/Redo with Action Trails

Leverage the out-of-the-box undo-redo mechanism of MstHtmlEditor control, end-users
can gradually work back to fix a mistake by undoing repeatedly.
Send HTML Email with Embedded Images
The MstHtmlEditor.GetMailMessage method will give you a .NET MailMessage object
where all the local images are embedded, with this object you can easily send an email in HTML
format.

SYSTEM SPECIFICATION
HARDWARE CONFIGURATION
Processor

Intel I3

RAM capacity

2 GB

Hard disk drive

500 GB

Key Board

Samsung 108 keys

Mouse

Logitech Optical Mouse

DVD Writer

LG

Printer

DeskJet HP

Motherboard

Intel

Cabinet

ATX

TFT Monitor

17 Samsung

SOFTWARE CONFIGURATION
Front end used

Visual Basic.NET 2008

INTRODUCTION TO FRONT END

VISUAL BASIC.NET
Many people have looked at VB.NET and grumbled about the changes. There are
significant changes to the language: a new optional error handling structure, namespaces, true
inheritance, free threading, and many others. Some see these changes as merely a way that
Microsoft can place a check mark next to a certain feature and is able to say, Yeah, we do that.
However, there are good reasons for the changes inVB.NET.
At this point, you might be tempted to think that SOAP is all you need, and that you can
just stick with VB6. Therefore it is important to understand what VB.NET gives you, and why it
makes sense for you, and many other developers, to upgrade to .NET. For example, you create
components and want them to be callable via SOAP, but how do you let people know that those
components exist? .NET includes a discovery mechanism that allows you to find components
that are available to you. Building Web Services with VB.NET. .NET also provides many other
features, such as garbage collection for freeing up resources, true inheritance for the first time,
debugging that works across languages and against running applications, and the ability to create
Windows services and console applications. Before proceeding, its important to understand a
little bit more about what is meant by .NET.
There are many .NETs here. There is VB.NET, which is the new version of Visual
Basic. There is Visual Studio.NET, an Integrated Development Environment that hosts VB.NET,
C#, and C++.NET. Underlying all this is the .NET Framework and its core execution engine, the
Common Language Runtime. In the .NET model, you write applications that target the .NET
Framework. This gives them automatic access to such benefits as garbage collection (which
destroys objects and reclaims memory for you), debugging, security services, inheritance, and
more.
When you compile the code from any language that supports the .NET Framework, it
compiles into something called MSIL, or Microsoft Intermediate Language. This MSIL file is
binary, but it is not machine code; instead, it is a format that is platform independent and can be

placed on any machine running the .NET Framework. Within the .NET Framework is a compiler
called the Just-In-Time, or JIT, compiler. It compiles the MSIL down to machine code specific to
that hardware and operating system.
.NET provides you with integrated debugging tools. If youve ever debugged an ASP
application that had VB COM components, you know that you had to use Visual InterDev to
debug the ASPs and VB to debug the components. If you also had C++ components in the mix,
you had to use the C++ debugger on those components. With .NET, there is one debugger. Any
language that targets the .NET Framework can be debugged with that single debugger, even if
one part of your application is written in VB.NET and calls another part written in C#
(pronounced C-Sharp), or any other language built to target the .NET Framework.
.NET supplies a standard security mechanism, available to all parts of your
application. .NET provides a possible solution to DLL Hell, and removes much of the
complexity of dealing with COM and the registry. .NET allows you to run components locally,
without requiring the calling application to go to the registry to find components.
There are also things that VB.NET can do that you cannot do today in VB. For example,
Web Applications are a new form of project. Gone is Visual InterDev with its interpreted
VBScript code. Instead, you now build your ASP.NET pages with VB.NET (or C# or C++), and
they are truly compiled for better performance. VB.NET lets you create Windows services
natively for the first time by providing a Windows Ser vices project type. And yes, VB.NET lets
VB developers build truly free-threaded components and applications for the first time.
The .NET Framework is a collection of services and classes. It exists as a layer between
the applications you write and the underlying operating system. This is a powerful concept:
The .NET Framework need not be a Windows-only solution. The .NET Framework could be
moved to any operating system, meaning your .NET applications could be run on any operating
system hosting the .NET Framework. This means that you could achieve true cross-platform
capabilities simply by creating VB.NET applications, provided the .NET Framework was
available for other platforms. Although this promise of cross-platform capability is a strong

selling point to .NET, there has not yet been any official announcement about .NET being moved
to other operating systems.
In addition, the .NET Framework is exciting because it encapsulates much of the basic
functionality that used to have to be built into various programming languages. The .NET
Framework has the code that makes Windows Forms work, so any language can use the built-in
code in order to create and use standard Windows forms. In addition,
Web Forms are part of the framework, so any .NET language could be used to create Web
Applications. Additionally, this means that various programming elements will be the same
across all languages; a Long data type will be the same size in all .NET languages. This is even
more important when it comes to strings and arrays. No longer will you have to worry about
whether or not a string is a BStr or a CStr before you pass it to a component written in another
language.
The Common Language Runtime
One of the major components of the .NET Framework is the Common Language
Runtime, or CLR. The CLR provides a number of benefits to the developer, such as exception
handling, security, debugging, and versioning and these benefits are available to any language
built for the CLR. This means that the CLR can host a variety of languages, and can offer a
common set of tools across those languages. Microsoft has made VB, C++, and C# premier
languages for the CLR, which means that these three languages fully support the CLR. In
addition, other vendors have signed up to provide implementations of other languages, such as
Perl, Python, and even COBOL.
When a compiler compiles for the CLR, this code is said to be managed code.
Managed code is simply code that takes advantage of the services offered by the CLR. For the
runtime to work with managed code, that code must contain metadata. This metadata is created
during the compilation process by compilers targeting the CLR.

The metadata is stored with the compiled code and contains information about the types,
members, and references in the code. Among other things, the CLR uses this metadata to

Locate classes
Load classes
Generate native code
Provide security

The runtime also handles object lifetimes. Just as COM/COM+ provided reference
counting for objects, the CLR manages references to objects and removes them from memory
when all the references are gone, through the process known as garbage collection. Although
garbage collection actually gives you slightly less control than you had in VB, you gain some
important benefits. For example, your errors should decrease because the number of objects that
end up hanging around due to circular references should be reduced or completely eliminated.
In addition, garbage collection ends up being much faster than the old way of destroying
objects in VB. Instances of objects you create that are managed by the runtime are called
managed data. You can interact with both managed and unmanaged data in the same application,
although managed data gives you all the benefits of the runtime. The CLR defines a standard
type system to be used by all CLR languages. This means that all CLR languages will have the
same size integers and longs, and they will all have the same type of string no more worrying
about BStrs and CStrs! This standard type system opens up the door for some powerful language
interoperability.
For example, you can pass a reference of a class from one component to another, even if
those components are written in different languages. You also can derive a class in C# from a
base class written in VB.NET, or any other combination of languages targeted to the runtime.
Microsoft Intermediate Language (MSIL)
One of the more interesting aspects of .NET is that when you compile your code, you do
not compile to native code. Before you VB developers panic and fear that you are returning to

the days of interpreted code, realize that the compilation process translates your code into
something called Microsoft intermediate language, which is also called MSIL or just IL. The
compiler also creates the necessary metadata and compiles it into the component. This IL is CPU
independent. After the IL and metadata are in a file, this compiled file is called the PE, which
stands for either portable executable or physical executable, depending on whom you ask.).
The Just-In-Time Compiler
Your code does not stay IL for long, however. It is the PE file, containing the IL that can
be distributed and placed with the CLR running on the .NET Framework on any operating
system for which the .NET framework exists, because the IL is platform independent. When you
run the IL, however, it is compiled to native code for that platform. Therefore, you are still
running native code; you are not going back to the days of interpreted code at all. The
compilation to native code occurs via another tool of the .NET Framework: the Just-In-Time
(JIT) compiler. With the code compiled, it can run within the Framework and take advantage of
low level features such as memory management and security.
Multiple Document Interface
This application has one parent form that contains most of the other forms in the
program. Other forms can be child forms, which are contained within the parent, or standard
forms. In the MDI application, one can easily organize all the child forms or minimize the entire
group of forms just by minimizing the parent form. A single icon on the Windows taskbar
represents the MDI parent window and all child windows. If the parent form is minimized and
then restored, all the child forms are returned to the same layout as they had before the
application was minimized.

SYSTEM STUDY
EXISTING SYSTEM
The existing system is a manual one, which consumes lot of time as well as manpower.
In order to elicit the requirements of the system and to identify the elements, inputs, outputs and
the procedures. The existing system had to be examined and analyzed in detail. This constituted
the system study. Records, slips, procedures, rules, etc. were examined thoroughly. The existing
system was studied involving a complete co-operation from the employees who run the system at
present

DRAWBACKS OF EXISTING SYSTEM

A manual system has so many pitfalls. Some of them are

The Necessary data are stored in different documents and transactions are noted in it.

Time consumption

Many files and paper works are maintained by the existing system.

Unavailability of quick references

There is no facility to know the validity of the data entered.

Another problem is the lack of security

The existing system does not implement the restriction for the user to access data.

PROPOSED SYSTEM
In the configuration of the HTML editor, you can specify the security mode and activate
or deactivate security-relevant editing functions, such as the insertion of HTML text.

Secure HTML Editor Parameters

Parameter

Description

Always Use Secure

If you activate this parameter, users of the HTML editor can only change

HTML Editor

the formatting (bold, italics, underlining). All other functions are

deactivated for security reasons.
You can allow other editing functions or further limit the functions
provided (see the following parameters).
This parameter is deactivated in the standard system.

Allow Only Basic

If you activate this parameter, the editor only allows changes to the

Formatting

formatting (bold, italics, underlining). No other editing functions are

supported and insertion of HTML-formatted text is not possible.
Choose this option to provide the HTML editor in the most secure mode.
The Always Use Secure HTML Editor parameter must be activated.

Allow Links

Specifies whether or not links can be used.

The Always Use Secure HTML Editor parameter must be activated.

Activate Clipboard

Specifies whether or not the cut, copy, and paste functions can be used.

Buttons

The Always Use Secure HTML Editor parameter must be activated.

Allow Preview

Specifies whether or not the preview can be used.

The Always Use Secure HTML Editor parameter must be activated.

Allow Indenting

Specifies whether or not text can be indented.

The Always Use Secure HTML Editor parameter must be activated.

Allow Tables

Specifies whether or not tables can be used.

The Always Use Secure HTML Editor parameter must be activated.

Allow Bullets and

Specifies whether or not bulleted lists and numbered lists can be used.

Parameter

Description

Numbering

The Always Use Secure HTML Editor parameter must be activated.

Allow Images

Specifies whether or not graphics can be used.

The Always Use Secure HTML Editor parameter must also be activated.

Allow Text Size and

Specifies whether or not font and font size settings can be used.

Font Settings

The Always Use Secure HTML Editor parameter must be activated.

Allow Color Settings

Specifies whether or not color formatting can be used.

The Always Use Secure HTML Editor parameter must be activated.

SYSTEM DESIGN AND DEVELOPMENT

FILE DESIGN
System design is a transition from user- enters document to document oriented
programmers or databases personnel. It emphasis on the translating performance specification
into design specification and it involves conceiving and planning and then carrying out the plan
by generating the necessary reports and outputs. Design phase acts as a bridge between the
software requirement specification and implementing phase, which satisfies the requirements.
The major step in design is the preparation of input and the design of output report in a
form, which is acceptable to the user. The first step in system design is to design the input and
output within predefined guidelines. In the design, the user- oriented inputs are converted into
computer based format whereas in the output design, the emphasis is on producing the hard copy
of information requested or either displaying output on the screen.
A modular approach has been adopted in the development of the proposed system. Each
module is designed for a specific application and by are operated independently.

INPUT DESIGN
Input design is a process of converting user-organized input into computer-based format.
To enter the various data capture through the paper forms into the system, screens are designed.
The elements are shown in the screen by which any user or customer can easily follow. The input
to the system was designed such that the required information can be collected and corrected
quickly.
The goal of input design is to make data entry easier, logical and free from errors.
The decision during input design is:

To provide cost effective methods of input.

To achieve the highest possible level of accuracy.
To ensure the input is understood by user.
Input data of a system may not necessarily be raw data captured into the system. These can

also be the output of another system or subsystem. The design of input covers all phases of input
from the creation of initial data to actual entering of data into the system for processing. It
involves identifying the data need, specification the characteristics of each data item, ensuring
correctness of data.

HTML Editor

Edit HTML

Open File

Save File

Enter HTML Tag

Enter Text Screen

View HTML Tag

OUTPUT DESIGN
The output is designed in terms of data content and approximate layout. The information
required by the users is also taken into consideration. Output design refers to the results and
information that are generated by the system. For many end-users, output is the main reason for
developing the system on the basis on which they will evaluate the usefulness of this application.
Output of a system can take various forms. The most common are reports, screen
displays, printed forms, Graphical drawings etc. the basic requirements of output are that it
should be accurate, timely and appropriate in terms of content, medium and layout for its
intended purpose. Hence it is necessary to design output, so that the objective of the system is
met in the best possible manner.

TESTING AND IMPLEMENTATION

System testing is a critical aspect of Software Quality Assurance and represents the
ultimate review of specification, design and coding. Testing is a process of executing a
program with the intent of finding an error. A good test is one that has a probability of
finding an as yet undiscovered error. The purpose of testing is to identify and correct bugs in the
developed system. In the code testing the logic of the developed system is tested.
TESTING METHODOLOGIES
The main stages of System Testing are:
Unit Testing
Module Testing
Integration Testing

UNIT TESTING
Unit testing focuses on modules to locate errors in proposed system. This enables to
detect errors in the coding and logic that are contained within that module alone. Those resulting
from the interaction between modules are initially avoided. In unit testing step each module has
to be checked immediately.

MODULE TESTING:

Module testing also known as unit testing is the process of testing the system module
by module. This testing has been done for all the modules independently. The output of each
module has been checked when an input was given. This testing helped in checking the
functionality of different modules, which work in parallel to each other.

INTEGRATION TESTING:
The Interface testing has been performed to verify that the conditions specified were
tested and checked if the specific file is loaded for the authorized users, in the authorized mode.
The report generation was checked out and found that the progresses of the software in which
they produce reports were successful.

SYSTEM IMPLEMENTATION

Implementation is the stage in the project where theoretical design is turned to a working
system. Two major factors for the implementation are testing the system and training the user.
Since the existing system involves manual operations the new system is implemented in parallel
with the existing. This was done to build users confidence about the system, but also to check the
efficiency of the developed system.

IMPLEMENTATION PROCEDURES
There are several methods for handling the implementation and the consequent from the
old to new computerization system. The most secure method for conversation from the old
system to the new system into run the old and new system in parallel. In this approach, a person
may operate in the manual older processing system as well as start operating the new
computerization system. This method offers high security, because even if there is a flaw in the
computerization system , we can depend upon the manual system. However, the cost for
maintaining two systems in parallel is very high. This out weights its benefits.
Another commonly method is a direct cutover from the existing manual system to the
computerized system. The change may be within a week or within a day. There are no parallel
activities. However, there is no remedy in case of a problem. This strategy requires careful
planning.
A working version of the system can be also be implemented in one part of the
organization and the personal will be piloting the system and changes can be made as when
required. But this method is less preferable due to the less of entirety of the system.

IMPLEMENTATION PLAN
The implementation plan includes a description of all the activated that must occur to
implement the new system and to put it into operation. It identifies the personal responsible for
the activities and prepares a time chart for the implementation of the system. The implementation
plans consist of the following steps

List of all files requires for implementation.

Identify all data requires to build new files during the implementation.
List the all new documents and procedure that go into the new system.

The implementation plan should anticipate possible problems and must be able to deal
with them. The usual problem may be missing documents; mixed data formats between current
and files, errors in data translation, missing data etc.,

SYSTEM MAINTENANCE
Once system has been developed and implement, it cannot be considered as the end of the
system lifecycle. After the implementation it is necessary that the system be constantly
monitoring so that it may be decided as to how the system is working. If any problem is
encountered it is necessary that in charge person rectifies the problem so that the client may not
be affected by the problem. This phase of the system developed lifecycle is called the system
maintenance period. During this period the entire possible problem will be rectified.
Maintenance is making adaptation of the software for the external changes (requirements
changes are enhancements ) and internal changes(fixing bugs). When changes (fixing bugs),
when are made during the maintenance phases all proceeding steps of the must be revisited.
There are three types of maintenance,
The Corrective Maintenance is just a one step process. Just the errors are corrected and
the person leaves. The further details regarding the system are not the concern of the system
engineer.
The Adaptive Maintenance occurs when the environment in which the system had been
working is modified or changed. The system will have to be changed so that it may become
adaptable to the change that has been made to the environment.
The Perfect Maintenance occurs when further enhancements are to be made to the
existing system. These type of maintenance also occurs when the customer requirement changes.

CONCLUSION
The system development titled HTML Edito was designed keeping in mind to provide
maximum flexibility to the users. The system was tested with sample data and the performance
of the system was found to be efficient. All efforts have been made to understand the system
wholly and understand all the details.
Almost all aspects regarding user have been take into consideration when developing
the system and are included into the system. Much of the process is automated and hence the
chance of human errors was limited.

SCOPE IN FUTURE ENHANCEMENTS

Though the new system provides a base for improving the efficiency of operations,
there are lots of further enhancements that can be added to this project. Keeping this in
view, a provision has been made in the system to facilitate easy modification/updating in
the future. Any modification will not affect the normal working of the system. The system can be
implemented as an online application with more flexibility.
Considering chance that in future the need of the organization may increase develops this
software. Coding is done in a way that when a change is made to the database table it can be
easily. As the codes are effectively Documented and the codes are made as reusable, the system
is highly flexible to any future changes.

BIBLIOGRAPHY

Dave grundgeiger Programming Visual Basic.NET, Mc Graw Hill Edition, IInd Edition
2003

Ray Ran Kins MicroSoft SQL server 2000, Galgotia Publication , III Edition, 2001

D M DHAMDHERE. Systems Programming and Operating Systems. Tata McGraw-

Hill Publishing Co., II Edition, 2002

ELIAS. M. AWAD, System Analysis and Design,Galgotia Publications 1997 Edition.

ROGER S.PRESSMAN.Software Engineering. Tata McGraw-Hill Publishing Co.,

vth Edition, 2001.

Websites

www.google.com
www.microsoft.com
www.w3schools.com
www.codeproject.com
www.a1vbcode.com