<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16441" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN class=837142216-06062007>I would like to see
the PowerHouse Web client support an Ajax framework, this uses the same zero
footprint architecture and provides a dynamic web page on the client side.
Anything useful on the web has move beyond simply html and now include some form
of script (JavaScript or ActionScript).</DIV>
<DIV> </DIV>
<DIV><A
href="http://en.wikipedia.org/wiki/Ajax_framework">http://en.wikipedia.org/wiki/Ajax_framework</A></DIV>
<DIV> </DIV>
<DIV>There are plenty of examples, many are Open Source like:</DIV>
<DIV> </DIV>
<DIV>ZK Simply Ajax <A
href="http://www.zkoss.org/">http://www.zkoss.org/</A><BR>Thinwire <A
href="http://www.thinwire.com/">http://www.thinwire.com/</A></DIV>
<DIV><!--StartFragment -->Google Web Toolkit <A
href="http://code.google.com/p/google-web-toolkit/">http://code.google.com/p/google-web-toolkit/</A></DIV>
<DIV> </DIV>
<DIV>Regards<BR>Greig Morrison</DIV>
<DIV> </DIV>
<DIV>-----Original Message-----</DIV>
<DIV> </DIV>
<DIV>----------------------------------------------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 1</DIV>
<DIV> </DIV>
<DIV>Date: Wed, 6 Jun 2007 09:19:20 -0400<BR>From: "Deskin, Bob" <<A
href="mailto:Bob.Deskin@Cognos.COM">Bob.Deskin@Cognos.COM</A>><BR>Subject:
HTML Generator<BR>To: <<A
href="mailto:powerh-l@lists.sowder.com">powerh-l@lists.sowder.com</A>></DIV>
<DIV> </DIV>
<DIV>Message-ID: <<A
href="mailto:2B4E386EAEC90947802323BF373DC0EC0B971B87@sottemail1.ent.ad.cognos.com">2B4E386EAEC90947802323BF373DC0EC0B971B87@sottemail1.ent.ad.cognos.com</A>></DIV>
<DIV> </DIV>
<DIV><BR>Content-Type: text/plain; charset="us-ascii"</DIV>
<DIV> </DIV>
<DIV>Now that we have put the E version to bed (it's in manufacturing but not
quite available yet), we're busy planning the next release. We have lost of
ideas of course, and I'm not specifically soliciting any more. What I would like
to do is follow up on Ken's idea, which we share, of an HTML generator. We
already know that QDESIGN can generate HTML. And it's not particularly difficult
to add to that. I'm not trying to make it sound like it's a 5 minute job, but we
already know how to do it. It's simply a case of designing the keyword and
determining what HTML should be generated and where.</DIV>
<DIV> </DIV>
<DIV>But I don't think people want PowerHouse Web with it's panel-oriented
stateless architecture that requires converting subscreen calls to linkscreens
and some other way of handling reports and runs. My take is that people want is
something that feels like QUICK (even down to the Action field is desired) but
looks like a web page. And that it runs over a local network similar to a
terminal emulator as opposed to the internet (although that might be a
possibility). So the first question is - is that a correct assumption?</DIV>
<DIV> </DIV>
<DIV>If that is correct, then the next question is how do we do the execution
end of things in a reasonable period of time with limited resources.<BR>Sure, it
can be done. The browser engines are available as controls or applets and we
could build the entire infrastructure, but we don't have a large team and 2 or
more years. Rather we have 2 or 3 people and 6 months (no, that's not the whole
team but we do have other things to do, and the 6 months is what I'm aiming for
because I know these projects take longer).</DIV>
<DIV> </DIV>
<DIV>So does anyone have any ideas on how to put this sort of thing
together?</DIV>
<DIV> </DIV>
<DIV>Are there web sites that describe it? Is it even reasonable considering
that a browser is typically block oriented whereas QUICK is field
oriented?</DIV>
<DIV> </DIV>
<DIV>Any thoughts? </DIV>
<DIV> </DIV>
<DIV><BR>Bob</DIV>
<DIV> </DIV>
<DIV>PS I removed the other portions of Ken's message because I won't get into
pricing policy in a public forum. Ken's 3rd point is somewhat dependant on the
success of the second. These days, you need to look good to be noticed. However,
whatever we do must be in keeping with our existing architecture. QKView is a
step in the right direction.<BR></SPAN></FONT></DIV></BODY></HTML>