PHWeb
Jon Kvisli
jon.kvisli@lindorffapplications.com
Thu, 8 May 2003 14:34:42 +0200
This is a multi-part message in MIME format.
------=_NextPartTM-000-3e75e635-7d23-458f-947d-ffee9373d412
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C3155E.333C9108"
------_=_NextPart_001_01C3155E.333C9108
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Hi Bob.
=20
Can You provide information about any possible changes in the base
techology of PHWeb? E.g. are there any plans for replacing the CGI-based
mechanisms with generation of Java JSP/servlets that can run on a J2EE
app.server? This will probably make it easier to separate HTML-styles
from PH-logic.
=20
Regards
Jon Kvisli
----------------------------------------------
Principal Consultant
Lindorff Applications as
Hellandtunet research- og businesscentre
P.O.Box 4, 3833 Bo in Telemark
phone: +47 35 06 15 71
fax: +47 35 06 15 01
mail: jon.kvisli@lindorffapplications.com
www.lindorffapplications.com <http://www.lindorffapplications.com/>=20
----------------------------------------------
-----Opprinnelig melding-----
Fra: Deskin, Bob [mailto:Bob.Deskin@cognos.com]=20
Sendt: 7. mai 2003 20:48
Til: 'Dennis Hassell'; powerh-l@lists.swau.edu
Emne: RE: PowerHouse in the next 3 years?
=09
=09
Dennis wrote:
Also, for the future, providing a closer integration of
the PH Web product with an HTML design tool would be very helpful. Right
now, the styled HTML must be modified by hand to implement changes. A
QDESIGN recompile into HTML will not merge the HTML design with the PH
logic. Either the PH must be laid into the template or vice versa. That
would produce a productivity gain that could be a great sales point, and
better justify the PH Web costs.
The upcoming version, 2.4, will let you do a much better job of
prototyping the entire application before any HTML changes have to be
made. Basically, in 2.2, you had to make HTML changes just to get a
basic application that passed data back and forth between pages. This is
now handled automatically.
=20
We are looking at further enhancements to merge the HTML but
since the HTML is simple text, with no hooks to the QDESIGN source, it's
not a simple task. All I can say is that we are looking at it for a
future release.
=20
Bob
=20
------_=_NextPart_001_01C3155E.333C9108
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Melding</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D500373312-08052003><FONT color=3D#0000ff>Hi=20
Bob.</FONT></SPAN></DIV>
<DIV><SPAN class=3D500373312-08052003><FONT=20
color=3D#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=3D500373312-08052003><FONT color=3D#0000ff>Can You=20
provide information about any possible changes in the base =
techology of=20
PHWeb? E.g. are there any plans for replacing the CGI-based =
mechanisms with=20
generation of Java JSP/servlets that can run on a J2EE app.server? This =
will=20
probably make it easier to separate HTML-styles from=20
PH-logic.</FONT></SPAN></DIV>
<DIV><SPAN class=3D500373312-08052003><FONT=20
color=3D#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=3D500373312-08052003><FONT=20
color=3D#0000ff>Regards</FONT></SPAN></DIV>
<DIV><SPAN class=3D500373312-08052003>
<STYLE>st1\:* {
BEHAVIOR: url(#ieooui)
}
</STYLE>
<STYLE>@page Section1 {size: 612.0pt 792.0pt; margin: 70.85pt 70.85pt =
70.85pt 70.85pt; mso-header-margin: 35.4pt; mso-footer-margin: 35.4pt; =
mso-paper-source: 0; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: =
"Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto
}
DIV.Section1 {
page: Section1
}
</STYLE>
<DIV>Jon =
Kvisli<BR>----------------------------------------------<BR>Principal=20
Consultant<BR>Lindorff Applications as<BR>Hellandtunet research- og=20
businesscentre<BR>P.O.Box 4, 3833 Bo in Telemark<BR>phone: +47 35 06 15=20
71<BR>fax: +47 35 06 15 01<BR>mail: <A=20
href=3D"mailto:jon.kvisli@lindorffapplications.com">jon.kvisli@lindorffap=
plications.com</A><BR><A=20
href=3D"http://www.lindorffapplications.com/">www.lindorffapplications.co=
m</A><BR>----------------------------------------------<BR></DIV></SPAN><=
/DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Dno dir=3Dltr =
align=3Dleft><FONT face=3DTahoma=20
size=3D2>-----Opprinnelig melding-----<BR><B>Fra:</B> Deskin, Bob=20
[mailto:Bob.Deskin@cognos.com] <BR><B>Sendt:</B> 7. mai 2003=20
20:48<BR><B>Til:</B> 'Dennis Hassell'; =
powerh-l@lists.swau.edu<BR><B>Emne:</B>=20
RE: PowerHouse in the next 3 years?<BR><BR></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D445014218-07052003>Dennis</SPAN></FONT><FONT face=3DArial =
color=3D#0000ff=20
size=3D2><SPAN =
class=3D445014218-07052003> wrote:</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px"><SPAN =
class=3D562315816-07052003><FONT=20
face=3DArial><FONT color=3D#0000ff><FONT size=3D2>Also, for the =
future, providing=20
a closer integration of the PH Web product with an HTML design tool =
would be=20
very helpful. Right now, the styled HTML must be modified by hand to =
implement changes. A QDESIGN recompile into HTML will not merge the =
HTML=20
design with the PH logic. Either the PH must be laid into the =
template or=20
vice versa. That would produce a productivity gain that could be a =
great=20
sales point, and better justify the PH Web costs.</DIV></BLOCKQUOTE>
<DIV dir=3Dltr><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D445014218-07052003>The upcoming version, 2.4, will let you do =
a much=20
better job of prototyping the entire application before any HTML =
changes have=20
to be made. Basically, in 2.2, you had to make HTML changes just to =
get a=20
basic application that passed data back and forth between pages. This =
is now=20
handled automatically.</SPAN></FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D445014218-07052003></SPAN></FONT> </DIV>
<DIV dir=3Dltr><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D445014218-07052003>We are looking at further enhancements to =
merge the=20
HTML but since the HTML is simple text, with no hooks to the QDESIGN =
source,=20
it's not a simple task. All I can say is that we are looking at it for =
a=20
future release.</SPAN></FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D445014218-07052003></SPAN></FONT> </DIV>
<DIV dir=3Dltr><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D445014218-07052003>Bob</SPAN></FONT></DIV>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px"><FONT face=3D"Times New =
Roman"=20
=
size=3D3></FONT></FONT></FONT></FONT></SPAN> </DIV></BLOCKQUOTE></BO=
DY></HTML>
=00
------_=_NextPart_001_01C3155E.333C9108--
------=_NextPartTM-000-3e75e635-7d23-458f-947d-ffee9373d412--