× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Bob,

Since I'll be using your tool shortly, can you please post or send me a
sample HTTP config file so I can see what's actually needed.  As I mentioned
I was to remove all the "exceed" directives that aren't necessary.

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Bob Cozzi
Sent: Tuesday, November 16, 2004 8:47 PM
To: 'Web Enabling the AS400 / iSeries'
Subject: RE: [WEB400] RE: CGIDEV2 problems when updating to 9/2004 release

Yes, CGILIB uses the cgiSetProp() procedure to do that as follows:
  Callp  cgiSetProp(CGI_SECTION: '<!-- S_')

Now if you avoid the S_ in the section name change here, you could
inadvertently cause all comments in the HTML to be considered section names.
-Bob


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Tom Jedrzejewicz
Sent: Tuesday, November 16, 2004 3:51 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] RE: CGIDEV2 problems when updating to 9/2004 release

On Tue, 16 Nov 2004 14:47:49 -0500, Mike Skvarenina <mskvarenina@xxxxxxx>
wrote:
> But let me ask you this.  Doing the CGI kind of development we do, a RPG
> program writing "sections" referring to a separate HTML file, how does one
> use HTML tools like Dreamweaver, CoffeeCup, etc and do the dual
development
> of the RPG?

I use the CoffeeCup HTML editor, and find it quite handy.  It has a
text editor but can syntax check HTML statements, and it has a viewer
mode so you can see what you are doing.  It is pretty basic, and
pretty inexpensive.

The trick - I changed my section delimiter in CGIDEV2 to <!-- S_  so
the editors think the section headers are comments.  I am pretty sure
this can be done with Mr. Cozzi's tool as well.
--->  callp     gethtmlifs('/bpcsweb/ORD52a.html': '<!-- S_')

The header line for the PosTo section is 
<!-- S_PosTo  **** Position To Section -->

Then in the editor you put together the single element components. 
The substitution variables are   It can be a bit confusing when (for
instance) you have multiple sections that might start a table, but you
get used to it as you learn to get more complex in your programs.  In
very complex HTML files I have sometimes added unused sections to
complete structures (i.e. forms and tables) to make the editor display
things below properly.
For instance, if I have 3 possible table headers, I will have 2
"dummy" table footers sections in the HTML file so that the 3 "orphan"
<TABLE> statements don't confuse the editor.

Hope this helps.
-- 
Tom Jedrzejewicz
tomjedrz@xxxxxxxxx
_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.