<HTML >
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2900.3086" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
        BEHAVIOR: url(#default#VML)
}
o\:* {
        BEHAVIOR: url(#default#VML)
}
w\:* {
        BEHAVIOR: url(#default#VML)
}
.shape {
        BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PostalCode"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PlaceName"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PlaceType"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="country-region"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"></o:SmartTagType><!--[if !mso]>
<STYLE>st1\:* {
        BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
        font-family: Wingdings;
}
@font-face {
        font-family: Tahoma;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; }
v\:* {
        BEHAVIOR: url(#default#VML)
}
o\:* {
        BEHAVIOR: url(#default#VML)
}
w\:* {
        BEHAVIOR: url(#default#VML)
}
SHAPE {
        BEHAVIOR: url(#default#VML)
}
P.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; COLOR: black; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; COLOR: black; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; COLOR: black; FONT-FAMILY: "Times New Roman"
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
        COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
        COLOR: blue; TEXT-DECORATION: underline
}
P {
        FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; COLOR: black; MARGIN-RIGHT: 0cm; FONT-FAMILY: "Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
PRE {
        FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; COLOR: black; FONT-FAMILY: "Courier New"
}
TT {
        FONT-FAMILY: "Courier New"
}
SPAN.EmailStyle19 {
        FONT-WEIGHT: normal; COLOR: blue; FONT-STYLE: normal; FONT-FAMILY: Arial; TEXT-DECORATION: none; mso-style-type: personal
}
SPAN.EmailStyle20 {
        FONT-WEIGHT: normal; COLOR: blue; FONT-STYLE: normal; FONT-FAMILY: Arial; TEXT-DECORATION: none; mso-style-type: personal
}
SPAN.EmailStyle21 {
        FONT-WEIGHT: normal; COLOR: blue; FONT-STYLE: normal; FONT-FAMILY: Arial; TEXT-DECORATION: none; mso-style-type: personal
}
SPAN.EmailStyle22 {
        COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle23 {
        FONT-WEIGHT: normal; COLOR: blue; FONT-STYLE: normal; FONT-FAMILY: Arial; TEXT-DECORATION: none; mso-style-type: personal
}
SPAN.EmailStyle25 {
        FONT-WEIGHT: normal; COLOR: blue; FONT-STYLE: normal; FONT-FAMILY: Arial; TEXT-DECORATION: none; mso-style-type: personal-reply
}
DIV.Section1 {
        page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-GB vLink=blue link=blue bgColor=white>
<DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=921210213-06062007>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.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=921210213-06062007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=921210213-06062007>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?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=921210213-06062007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=921210213-06062007>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. 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).</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=921210213-06062007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=921210213-06062007>So
does anyone have any ideas on how to put this sort of thing together? Are there
web sites that describe it? Is it even reasonable considering that a browser is
typically block oriented whereas QUICK is field oriented?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=921210213-06062007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=921210213-06062007>Any
thoughts? </SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=921210213-06062007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=921210213-06062007>Bob</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=921210213-06062007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=921210213-06062007>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.</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
powerh-l-bounces+bob.deskin=cognos.com@lists.sowder.com
[mailto:powerh-l-bounces+bob.deskin=cognos.com@lists.sowder.com] <B>On Behalf
Of </B>Ken Langendock<BR><B>Sent:</B> June 5, 2007 6:29 PM<BR><B>To:</B>
powerh-l@lists.sowder.com<BR><B>Subject:</B> FW: Is Powerhouse expanding in
India<BR><BR></FONT></DIV>
<DIV><SPAN class=884261022-05062007><FONT face=Arial><FONT color=#0000ff><FONT
size=2><SPAN class=921210213-06062007><< portions removed by Bob Deskin
>></SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=884261022-05062007><FONT face=Arial><FONT color=#0000ff><FONT
size=2><SPAN
class=921210213-06062007> </SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=884261022-05062007><FONT face=Arial><FONT color=#0000ff><FONT
size=2><SPAN class=921210213-06062007> </SPAN>b) The most important thing
would be something NEW</FONT></FONT></FONT></SPAN></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=884261022-05062007><SPAN class=775202822-05062007>Maybe </SPAN>Some kind
of "controllable/", HTML code generator from the compiler, </SPAN><SPAN
class=884261022-05062007>similar to how access statements get generated into
cursor statements. If we are not happy with the way the automatic one works,
we can create our own. </SPAN><SPAN class=884261022-05062007>If we could
create copy modules that would generate the correct HTML syntax to make the,
for example, screen headers work/look as they do in Quick, this would cut a
lot of code down.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=884261022-05062007>Function key statements that create proper HTML code,
etc.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=884261022-05062007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=884261022-05062007>The
list can go on and on, but the point is, we need a way of converting our
existing quick screens into fancy/schmancy html screens automatically. I for
one am not looking at converting 2000+ quick screens into HTML without some
"automatic" help.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=884261022-05062007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=884261022-05062007>Ken</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=884261022-05062007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=884261022-05062007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=884261022-05062007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Joe Boyle [mailto:atla38@dsl.pipex.com]
<BR><B>Sent:</B> June 5, 2007 5:58 PM<BR><B>To:</B> 'Ken Langendock';
powerh-l@lists.sowder.com<BR><B>Subject:</B> RE: Is Powerhouse expanding in
India<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><I><FONT face=Arial color=blue size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: blue; FONT-STYLE: italic; FONT-FAMILY: Arial"> I
think PH is failing ( read dead) because PowerHouse is so expensive –
especially training – all of the MS .net related software can be downloaded
for free – I have MSSQLserver, C#, C++, VB and it did,nt cost me a penny.
<o:p></o:p></SPAN></FONT></I></P>
<P class=MsoNormal><I><FONT face=Arial color=blue size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: blue; FONT-STYLE: italic; FONT-FAMILY: Arial">When
I tried to purchase PH software (for NT platforms only), Cognos wouldn’t sell
it me as an individual ( and that, after I worked on the Cognos support desk
for 5 years) with 12 years of PH on VMS, MPE, Unix and Dos
collectively.<o:p></o:p></SPAN></FONT></I></P>
<P class=MsoNormal><FONT face=Arial color=blue size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: blue; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><!--[if gte mso 9]><xml>
<u1:shapedefaults u2:ext="edit" spidmax="1026"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
<u3:shapelayout u4:ext="edit">
<u3:idmap u4:ext="edit" data="1"/>
</u3:shapelayout>
</xml><![endif]--><FONT face="Courier New" color=black size=2><SPAN
style="FONT-SIZE: 10pt"><o:p></o:p></SPAN></FONT> </DIV></DIV></DIV></BLOCKQUOTE></DIV>
<DIV> </DIV>
<DIV> This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. </DIV></BODY></HTML>