faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Missing the point, really missing the point...
by Anonymous coward on Friday 26/Mar/2004, @05:02
|
> Actually we don't know if this will work in practice. Look at HTML it keeps
> going through some pretty major because what it needs to do changes so much over
> time that the older way things where done just don't work very well anymore. It
> is true that old webpages still render in modern browsers but the pages do look
> old and stuff done now will look just as bad a few years from now
It happens because HTML is an inbreed between content and representation.
Things do change when using XML or XHTML: they have been created just to store *content*. The final representation is delegated to other systems (CSS or XLST).
Have a look at an XHTML page rendered without CSS support: it looks as ugly as the web pages written 10 years ago. But once you apply CSS rendering... The magik happens!
> That is true of many others areas also. Your apps don't magically upgrade like
> you seem to be suggesting since new concepts need to be explained to the
> system so that it knows that they apply to your app.
That's the whole point of XAML/Avalon: you just create the "content" of the GUI, the underlying desktop environment will know and apply the "new concepts" to the final representation. It does definitely ease integrating old apps with new (and revised) system GUIs.
> Overall the best bet it is seperate the front end from the back end of the app
> so that it is easier to replace the gui since overall in computing history it
> seems that the guis need replacing a lot more often then the front ends do.
Yes, and XAML/Avalon do allow it: it's always possible to write pure code that interfaces to your GUI, choosing whatever language you want (as long as it works under .NET). |
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
