Click here to Skip to main content
Click here to Skip to main content

A WTL DocView framework

By , 10 Jan 2006
 

Sample Image - DocView_framework.jpg

Introduction

This article explains the implementation of a simple Doc View framework in a WTL (version 7.5) MDI application. The sample project included with this article is a wizard-generated MDI application enhanced with my framework classes. I enhanced code from Gabriel Kniznik with a little bit closer to the MFC DocView approach, and there exists only one kind of document template - MDI Document template. This framework was written in a week, so I apologize for mistakes and unfinished solutions :).

In this article is also participating Rodrigo Pinho Pereira de Souza, who made great enhancements to this framework (see the History section).

Implementation

In the demo project, you can see how to integrate the framework to your own project. You have to make changes to CMainFrame, CChildFrame, CYourView, and create a new class CYourDoc. Do not forget to change the IDR_CHILDFRAME string to the form for MFC -> \nDocument\nDVF\n\n\nDVFSimple.Document\nDVF Document.

Below is a simplified class diagram of the framework:

Framework class diagram - simplified

History

  • 11 Jan 2006
  • Changes made by Rodrigo Pinho Pereira de Souza:

    • Automatic handling of ID_FILE_NEW
    • Automatic handling of ID_FILE_SAVE
    • Automatic handling of ID_FILE_SAVEAS
    • Implemented Serialization mechanism
    • Changed all declarations of std::vector to the ATL CSimpleArray
    • Created a CFormView class

    Demo application split to VC++ 6.0 and VS.NET 2003.

  • 8 Aug 2005 - Initial version.

Terms of Use

The sample application available with this article is free for any purpose. THIS SOFTWARE IS DISTRIBUTED AS-IS, WITHOUT WARRANTIES OF ANY KIND.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

About the Author

Jozef Bozek
CEO bring-it-together s.r.o.
Slovakia Slovakia
Member
Jozef Božek is currently a software engineer at bring-it-together s.r.o. in area of large scale infomation systems and mobile applications development.
He has been developing in C++ nearly full time since 2000, in Java since 2004 and in Objective-C since 2009. He is programming using Java EE SDK, iOS SDK, COM/DCOM, MFC, ATL, STL and so on Smile | :)

Sign Up to vote   Poor Excellent
Add a reason or comment to your vote: x
Votes of 3 or less require a comment

Comments and Discussions

 
You must Sign In to use this message board.
Search this forum  
    Spacing  Noise  Layout  Per page   
QuestionRelease Buildmemberjsvanwyk8 Apr '13 - 5:56 
Release Build does not work. When you run the program and create a new doc-view window as soon as you click the mouse left button an error box appears. Using Win XP, VS2008 and VS6.0, errors for both but Debug build works fine!
JS v Wyk
GeneralCString memory exceptionsmemberJerker Bäck6 Oct '06 - 17:04 
Sorry, I have to complain a little - hope you don't mind
My env:
Windows 2003 R2, VS 2003 using CRT and ATL3 from Win DDK 2003 SP1 - for "system DLLs"
(means I'm using ATL3 - not ATL7) and WTL8
 
First, I had to do a rather extensive clean up to get rid of common warnings - since they are generated in the headers - they become massive. Please do a UNICODE compile with warning level 4 and 64bit portabilty check using at least a 7.1 version compiler. You'll see what I mean.
 
Second, I got a memory exception right away in both debug and release build.
HEAP[DVF.exe]: Heap block at 003D36A0 modified at 003D36EA past requested size of 42
Unhandled exception at 0x7c822583 in DVF.exe: User breakpoint.

This is due to CString class (that will be the WTL implementation) and I guess the use of Ctring for buffer manipulation. My system DEP: /NoExecute=OptIn which is standard. I tried to fix this but soon found out that it's not an easy thing.
 
My comment:
I think it's a pity you choosed to use CString in your classes. That only makes them less useful in the general case with ATL. For me, CString is OK in MFC but feels odd in ATL - a matter of taste of course - but if you want people to enjoy your work, stick to ATL standard.
 
Anyway thanks for this since WTL really suffer the lack of a document implementation and a design layout for connection between data and view.
 

GeneralRe: CString memory exceptionsmemberJerker Bäck8 Oct '06 - 0:42 
To clarify a little:
The memory exception occurred with a UNICODE build and native wchar_t (/Zc:wchar_t) which is not supported in the original sources. The changes I made was basically adding the _T("some string") macro in some places. An ANSI build works fine - so the above post was maybe a little bit harsh.
 

GeneralRe: CString memory exceptionsmemberrajas12 Jul '08 - 19:28 
It appears that ExtractSubString was coded assuming ANSI . I made a couple of changes as below & added the _T() macros as you said and a few more changes and it compiles with Level 4 & UNICODE. I no longer get the exception you mentioned.
 
BOOL ExtractSubString(CString& rString, LPCTSTR lpszFullString, int iSubString, TCHAR chSep)
{
	if (lpszFullString == NULL)
		return FALSE;
        .....
        ......
 
	lstrcpyn(rString.GetBufferSetLength(nLen+1), lpszFullString, nLen+1);
	rString.ReleaseBuffer();   //-- this was missing
	return TRUE;
}

QuestionWhat about SaveDocument ?memberRodrigo Pinho Pereira de Souza2 Nov '05 - 14:38 
What about SaveDocument ? Did you implement ? D'Oh! | :doh:
 
Rodrigo Pinho Pereira de Souza
AnswerRe: What about SaveDocument ?memberJozef Božek3 Nov '05 - 1:23 
No, I did not implemented it yet. There exist method DoSave of class CDocument, but it simply returns TRUE. Now I do not have enough time to integrate full funcionality of DocView Sigh | :sigh:
GeneralRe: What about SaveDocument ?memberRodrigo Pinho Pereira de Souza29 Nov '05 - 0:33 
I made some changes in your DocView.
I have implemented the Handle for ID_FILE_SAVE.
I am implementing the Serialization from boost::serialization in your framework.
 
When I finish, I will send you for you review and update the code in your article.
 
Nice
 
Rodrigo Pinho Pereira de Souza
GeneralRe: What about SaveDocument ?memberJozef Božek29 Nov '05 - 0:55 
Hi Rodrigo,
thanks a lot for your time and cooperation, I am looking forward to see enhancements you made.
 
Jozef
GeneralRe: What about SaveDocument ?memberRodrigo Pinho Pereira de Souza5 Dec '05 - 1:38 
What is your email?
 
I implemented handlers for ID_FILE_NEW, ID_FILE_OPEN, ID_FILE_SAVE, ID_FILE_SAVEAS. I simple converted code from MFC.
 
I think that we can re-design to use more templates and put all in one file "atldocview.h", and strip-out any use of STL (you have used std::vector), and then submit to WTL source forge team, to be included in next version of WTL.
 
WTL does not have CFile or CArchive, and for this reason, I implemented Serializarion partilay.
 
The Serialization mechanism that I implemented, simple call method Serialization from Document class with the filename and Method (save/load), passing resposability to user to serialize his methods.
 
This is more flexible than MFC, because developer may want to use boost::serialization, MSXML, iostreams or just implement his serialization mechanism.
 
regards
 
Rodrigo Pinho Pereira de Souza

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Permalink | Advertise | Privacy | Mobile
Web01 | 2.6.130523.1 | Last Updated 11 Jan 2006
Article Copyright 2005 by Jozef Bozek
Everything else Copyright © CodeProject, 1999-2013
Terms of Use
Layout: fixed | fluid