> On Thu, Nov 04, Martin Edenhofer wrote:
>> http://demo.otrs.org/~martin/*.html ist "real" CSS support. What you
>> mean is the CSS to replace table tags.
>
> Of course there is no definition of "real". But as fare as CSS is
> described and used it is fare beyond the present code we are using.
>
> I am refering to books like "Cascading Style Sheets" by Eric A. Meyer.
> http://www.amazon.de/exec/obidos/ASIN/0596005253
>
>> IMO this is really no good idea (IMO).
>
> I disagree but that is a religious argumentation. I think in the long
> run there is no way to avoid such a CSS implementation. It need less
> bandwith, is more flexible and takes care of handicapped accessiblity
> problems.
>
> But I do agree that the work which is necessary to do it now is fare
> beyond scope.
>
>> But maybe Bob means xml/xsl > html transformation?
>>
>> OTRS generates xml and the html gets generated via xsl (e. g. with
>> Saxon). Maybe this would ne new cool stuff. Bob?
>
> Of course it would be cool but IMO a waste of CPU power and time.
>
> take care
> Stefan
>
> --
> ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg
> http://www.otrs.de/ :: Tel. +49 (0)6172 4832388
> _______________________________________________
> OTRS mailing list: dev - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/dev
> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
>
martin+stefan+the rest,
What the user sees is different from the content of what the user sees.
if you already have xml for the content, and generate html out of it, then
you basically have my idea, but...:
I read the book eXtreme Programming(by kent beck), and I'm also a fan of
testdriven development, so using xml
for the content means we can write automated tests for the entire OTRS
application, and separate the output of the
application (XML) with user interface packages(in (X)HTML)....that's my
idea...I haven't ever looked at the code of otrs so I don't know what you
are doing in there. It also would mean that we can have tests at the
customer site, and simply run them to
validate that the application behaves like it should behave.
so basically:
application output---->xml---->html----->visual content
|
|
+-------->tests--->>validation for correct operation--->money
each package in OTRS would come with a test suite, which checks the output
of the application ( XML + dtd) and validates that
the output is conformant to the package test criterias, that way we can be
sure that OTRS behaves like we want it to behave, the only
thing left to test/validate would be exactly how the application looks
(what the user sees)...( look and feel )
what do you think? do you already do it this way?
best R
/G
www.gh-webinteractive.com
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
