Answering the last question first: clearly that is the death knell of a
project. One language.
I would add to the problems of a reasonable GUI over the web, the problems
of printing. This is why I think one has to have Java app's on the
client. We deploy using JAR's that contain everything. I think that's
what David does too.
John
At 11:22 AM 5/1/01, you wrote:
>John S. Gage wrote:
>
>>What's the story about this:
>>http://www.dbxmlgroup.com/
>
>Dont' know the story. I find it an interesting idea and would like to see
>some production systems deployed. The last time I looked at this I
>concluded that for the server side it was still a little too early for us,
>and that there are no client tools available.
>
>I still have the same issue as to how you do a reasonable GUI over the
>web, starting and ending in XML. Everyone says you just use XLST. But,
>XLST is not only another programming language, it is declarative. I am
>sure this presents few problems to the programmers on this list. But I
>have to be sensitive to increasing the complexity of a development
>environment to a team of a dozen programmers, only a few of which are
>senior enough to not be troubled by adding in a second, completely
>orthogonal language.
>
> Besides, does everyone really want to have to use two programming
> languages each and every time you write a GUI?
>
>
>
