faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: quanta + kafka?
by Eric Laffoon on Wednesday 11/Sep/2002, @12:25
|
First off Jono was an incredible driving force on Kafaka and I suspected he would be missed when he left. Kafka had some different aims and was largely geared to be a newbie WYSIWYG editor as I understood it in my conversations. I can't speak to kafka particulars very well.
As for WYSIWYG mode Andras has already answered. I'll make some additions. Some users want it... some want it not to happen. There are valid reasons for both. WYSIWYG has been traditionally a real hack job. The coding underneath was the designers best guess at how they wanted to do things and it would be "hard wired" to how the tagging was set up. This causes lots of aesthetic problems with your code and makes adding DTDs a near redesign. In short WYSIWYG traditionally is a mess which leaves you with static pages that require 5-15% of the work to be done by hand anyway for finely tuned sites.
Our approach to DTDs and our parse tree is laying the groundwork for validation as you go features and rule based code formating based on defined nodes and relationships. Eventually when we are ready to add WYSIWYG we will have other options because of our founations. These will include feeding the markup to the WYSIWYG view while managing the server side scripting seperately or even being able to edit markup elements in dynamic content. In addition you will be able to completely define how markup is handled through the rule definitions or have other options being able to extract stuctures, edit them and re-insert them in the doucment.
Once you look at all the potential issues it is clear this is no simple task to do right. However when we are foundationally ready to preserve your work and extend the paradigm of WYSIWYG to dynamic page design we will begin work on it. Andras is right. We could use a few more developers for this. The point is I would not count on it for KDE 3.2. It would be great if it could be on track the middle of next year. I can't say right now. All I can say is when we do it you will agree it is the best implementation. It will not be a cutsie "paint a page" program but a serious developer tool that newbies can leave the defaults settings on and be happy. Coders will be able to use it more like a QT Designer for web pages to make them more efficient with the GUI elements of dynamic pages. ;-)
Cheers
Eric |
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
