|
File Viewer Structure and Implementation
A file viewer is an OLE component object in an in-process server DLL where the
object implements the IPersistFile and IFileViewer interfaces. The in-process server exports the DllGetClassObject and DllCanUnloadNow functions, implements a class factory object with the IClassFactory interface, and implements the file viewer object with the interfaces
required. The following illustration shows the structure of a file viewer.
There are a number of reasons why a file viewer is best implemented in a DLL
with the given interfaces. In general, a DLL is faster to load and usually comes
in a small package. In the future, these same DLLs will provide other nonuser
interface features, such as content indexing, and a component object DLL will
be the most efficient and fastest way to access those features. In some cases, a
file viewer object may need to display pop-up windows and process messages
through its own message loop as in Windows 95. The DLL structure still allows this
when used in conjunction with a stub process like Quick View, which gives the
file viewer DLL the right to execute a message loop.
The IPersistFile interface in the file viewer object is intended to be a general mechanism
through which the object is given a path for a file. From then on, the component
that loaded the object can ask it to do any number of things with the file.
Through Quick View, the Windows 95 shell asks the object to show the file by using
the IFileViewer::ShowInitialize and IFileViewer::Show member functions or asks the object to print the file to a specific printer
by using the IFileViewer::PrintTo member function. In the future, the shell may ask the object to perform
content indexing, which would happen through an interface other than IFileViewer. For this reason, the file loading member functions of IPersistFile are separate from the operations that perform on the file, which is why IFileViewer was not just extended with its own Load member function. This latter option is a little more efficient (because it
avoids IPersistFile entrypoint functions that are not implemented), but the design given here is
easier to extend.
| Last news from Greatis Software |
 |
|
Nostalgia .Net |
|
.Net is powerful, but not all-powerful, so sometimes we need to use Win32 API for our .Net applications. It's simple enough with Platform Invoke if you have Win32 skill, but we do not always have time to dig the ancient documentation, declare the special types that are compatible with Win32, find the values of the Win32's constants and so on. Nostalgia .Net offers several simple-to-use classes, and components that will allow you to forget about the headache of Win32 and just use the power of Win32 in your application the same way as you use the native. Net classes. More » |
| Recommended software for developers |
 |
|
Ultimate Pack |
|
Component pack for Delphi and C++ Builder that contains runtime form designer, runtime object inspector, print suite and much more for the very special price. More » |
 |
|
Form Designer .Net |
|
Unique runtime form design solution that allows to edit any form in .Net WinForms application at runtime with full source codes for only 300 euro! More » |
 |
|
Print Suite .Net |
|
Print Suite .Net is a set of components for easy printing texts, images and grids from your WinForms applications. Full C# source codes are available More » |
 |
|
Gradient Controls .Net |
|
Gradient Controls .Net offers controls with gradient background feature. Labels, panels and so on... Full C# source codes are available More » |
 |
|
Greatis iGrid |
|
iGrid plots drawing grid right over your desktop, so you can use it everywhere, with any drawing application without any special plugins for different graphic editors. More » |
All the contacts and projectsDmitry Vasiliev (just.dmitry)
Related LinksSoftware for Visual Studio .NET developers Software for Delphi and C++ Builder developers Software for Visual Basic 6 developers Delphi Tips&Tricks MegaDetailed.NET More Online Helps Win32 Programmer's Reference Win32 Multimedia Programmer's Reference OLE Programmer's Reference Microsoft Windows Pen API Programmer's Reference Microsoft Windows Sockets 2 Reference Microsoft Windows Telephony API (TAPI) Programmer's Reference Unix Manual Pages
|