[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kafka
Subject:    Re: Basic design diagram
From:       Thomas Zander <zander () xs4all ! nl>
Date:       2000-10-29 18:21:58
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> The document is the central class that hold the resposibility for the
> currently edited file. It may give away the resposibility to a view which
> stores the document in his format (the wysiwyg view might use the DOM, the
> html one uses kwrite). The document keeps track about the view which
> currently holds the data.
> There's only one active view at a time to be sure that there is only one
> state of the file.
> When the file should be saved i.e., the application asks the document to
> write to a given url. The document retireves the html code from the current
> view and stores it.
> I hope that makes my idea of the document/view classes a bit clearer.

Ah, yes, natuarally. Because the internal structure of the document can be 
totally deleted by, for example, editing the source file in kwrite. That view 
suddenly holds all the data. 

So we really don't have a central repository of the document. 

I like that concept it works well with a html editor :)

- -- 
Thomas Zander                                            zander@earthling.net
The only thing worse than failure is the fear of trying something new
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE5/GrKNj0pheMOlEoRAisGAKDeLBMYQXjJW5hRngb5rEkneEZnJQCg1rvu
7mYGaQRl8B+VzfQbuDkWpmg=
=stYj
-----END PGP SIGNATURE-----
_______________________________________________
Kde-kafka mailing list
Kde-kafka@master.kde.org
http://master.kde.org/mailman/listinfo/kde-kafka

[prev in list] [next in list] [prev in thread] [next in thread]