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

List:       quanta-devel
Subject:    [quanta-devel] KDOM in Quanta
From:       Andras Mantia <amantia () kde ! org>
Date:       2005-06-08 13:32:08
Message-ID: 200506081632.08303.amantia () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi,

 So anybody working and thinking now on this should know my opinion, 
which could be already read in other emails, but I will repeat them 
here.
 Shortly: no functionality should be lost and no behavior should be 
changed in a dramatic way. This means that we should:
- have the same information in the node tree as now. Storing of the text 
itself in the node is debatable.
- must deal with broken documents
- Quanta should not force or annoy people if the document itself is in a 
wrong state while editing. After all it is *usually* in a wrong state 
during editing. Think about coding, is the text in your editor 100% 
(syntactical)  correct when you write it? No, it's not and should not 
be. It should be correct when you compile it. As there is no 
compilation in Quanta, we might say that it should be correct when 
saving. And can warn when loading. Any other warning should be not in a 
way that interrupts the user's workflow. I consider the Problem 
Reporter to be such a way, as you can simply ignore it or hide it.
Other visual indications of problems can be OK, but of course for 
example removing the syntax highlighting for the rest of the document 
is not OK.
- must provide information about the text under the cursor at any time 
(tag, area type, tag attributes or so). This includes parse as you type 
functionality.
- must deal with non-XML. 

These are the most important issues I can think of.

Andras

-- 
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org

[Attachment #5 (application/pgp-signature)]

_______________________________________________
quanta-devel mailing list
quanta-devel@kde.org
https://mail.kde.org/mailman/listinfo/quanta-devel


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