Hi folks, I'm beginning to use the WAA for web-enabling some functions for 
our enterprise app written in Xbase++.  I'm building the web routines and 
html pages and notice that all output from the WAA generated pages have the 
"Powered By WAA, Alaska Software, Inc.", etc. at the bottom of the page.

Unless I'm missing something, this seems to be hardcoded in the WAA server 
itself and cannot be changed or disabled.  I understand that the WAA is 
something that is available for free, but in my case, I'm the owner of a 
Developer Subscription and would like to change or replace that banner 
before deploying to my end-user's site.  The clients of our client would not 
necessarily be software developers or interested in how the web site 
functions so this link at the bottom of all the pages may be confusing to 
them.

I've looked into the Gateway source, but there is no reference to this 
banner in there so I'm assuming it's in the Server portion which Alaska does 
not provide the source code to, even the "Developer" subscribers.

Any clues on if or how this can be done?

Thanks, Steve Furniss, Tranware, Inc.  www.tranware.com
steve@tranware.com

Problem Solved... No need to respond unless you have other comments beyond 
what is discussed in thread regarding similiar issue on 8/25/05 regarding 
the waapwr.gif.  By creating my own footer() function, I'm able to properly 
close the BODY and HTML tags and optionaly include my own footer.

Thanks.  Steve.

"Steve Furniss" <steve@tranware.com> wrote in message 
news:95299fa$3c9f7bf4$1ac4c1@news.alaska-software.com...
> Hi folks, I'm beginning to use the WAA for web-enabling some functions for 
> our enterprise app written in Xbase++.  I'm building the web routines and 
> html pages and notice that all output from the WAA generated pages have 
> the "Powered By WAA, Alaska Software, Inc.", etc. at the bottom of the 
> page.
>
> Unless I'm missing something, this seems to be hardcoded in the WAA server 
> itself and cannot be changed or disabled.  I understand that the WAA is 
> something that is available for free, but in my case, I'm the owner of a 
> Developer Subscription and would like to change or replace that banner 
> before deploying to my end-user's site.  The clients of our client would 
> not necessarily be software developers or interested in how the web site 
> functions so this link at the bottom of all the pages may be confusing to 
> them.
>
> I've looked into the Gateway source, but there is no reference to this 
> banner in there so I'm assuming it's in the Server portion which Alaska 
> does not provide the source code to, even the "Developer" subscribers.
>
> Any clues on if or how this can be done?
>
> Thanks, Steve Furniss, Tranware, Inc.  www.tranware.com
> steve@tranware.com
>
>

Steve,

> Problem Solved... No need to respond unless you have other comments beyond 
> what is discussed in thread regarding similiar issue on 8/25/05 regarding 
> the waapwr.gif.  By creating my own footer() function, I'm able to properly 
> close the BODY and HTML tags and optionaly include my own footer.

Yes, this is the 'standard' way of doing it, so you're in-line with
everybody else.

Can I take the opportunity to suggest an easier way of creating the html
pages than using the methods in the oHtml object?  Here's a form-function
that can be used in a WAA package.  Note that it doesn't need to accept the
oContext and oHtml parameters - these are handled automatically.  This uses
the xbHCL library, which brings the HTML syntax (and much more) in the
Xbase++ realm.

http://www.xbhcl.com

Function MyLogin()
   FORM ACTION 'MyLoginSubmit'
      TABLE
         TR
            TD align=right ? '~Name'
            TD ! name=UNAME           create an input control
         TR
            TD align=right ? '~Password'
            TD ! AS PASSWORD name=UPASS
         TR
            TD 
            TD SUBMIT value=Login
      Endtable
   EndForm

   HCL SEND  tell xbHCL to create the page and send to client
   RETURN TRUE

Function MyLoginSubmit()
   local cName := hclDefVar(UNAME,'')
   local cPass := hclDefVar(UPASS,'')
   local lOk := FALSE

   if !Empty(cName) .and. !Empty(cPass)
      USE users INDEX uname
      if dbSeek(cName) .and. RTrim(USERS->PASS) == cPass
         lOk := TRUE
          now call routine to generate main page
      endif
   endif
   if !lOk
       make sure document is initialised
      SPAN style='color:red'
         ? 'Login Failure: Please try again' BOLD
      EndSpan
      BR
      BR  make sure there is a blank line before login controls
       now call the login function to create the login page
      MyLogin()
   endif
   RETURN TRUE

Regards,

Phil Ide

---------------------
www.xbhcl.com
www.pbih.eu
www.idep.org.uk/xbase
---------------------
I will not send out battalions composed wholly of robots or skeletons
against heroes who have qualms about killing living beings.
          [Things I'd do as an Evil Overlord]

Hello,
there is a switch for that. But I forgot it. Ask Till from Alaska-Software. 
He knows.
regards
Olaf870

"Phil Ide" <phil@idep.org.uk> schrieb im Newsbeitrag 
news:62bw0o3esto.1b2171qngw7wr.dlg@40tude.net...
> Steve,
>
>> Problem Solved... No need to respond unless you have other comments 
>> beyond
>> what is discussed in thread regarding similiar issue on 8/25/05 regarding
>> the waapwr.gif.  By creating my own footer() function, I'm able to 
>> properly
>> close the BODY and HTML tags and optionaly include my own footer.
>
> Yes, this is the 'standard' way of doing it, so you're in-line with
> everybody else.
>
> Can I take the opportunity to suggest an easier way of creating the html
> pages than using the methods in the oHtml object?  Here's a form-function
> that can be used in a WAA package.  Note that it doesn't need to accept 
> the
> oContext and oHtml parameters - these are handled automatically.  This 
> uses
> the xbHCL library, which brings the HTML syntax (and much more) in the
> Xbase++ realm.
>
> http://www.xbhcl.com
>
> Function MyLogin()
>   FORM ACTION 'MyLoginSubmit'
>      TABLE
>         TR
>            TD align=right ? '~Name'
>            TD ! name=UNAME           create an input control
>         TR
>            TD align=right ? '~Password'
>            TD ! AS PASSWORD name=UPASS
>         TR
>            TD
>            TD SUBMIT value=Login
>      Endtable
>   EndForm
>
>   HCL SEND  tell xbHCL to create the page and send to client
>   RETURN TRUE
>
> Function MyLoginSubmit()
>   local cName := hclDefVar(UNAME,'')
>   local cPass := hclDefVar(UPASS,'')
>   local lOk := FALSE
>
>   if !Empty(cName) .and. !Empty(cPass)
>      USE users INDEX uname
>      if dbSeek(cName) .and. RTrim(USERS->PASS) == cPass
>         lOk := TRUE
>          now call routine to generate main page
>      endif
>   endif
>   if !lOk
>       make sure document is initialised
>      SPAN style='color:red'
>         ? 'Login Failure: Please try again' BOLD
>      EndSpan
>      BR
>      BR  make sure there is a blank line before login controls
>       now call the login function to create the login page
>      MyLogin()
>   endif
>   RETURN TRUE
>
> Regards,
> -- 
> Phil Ide
>
> ---------------------
> www.xbhcl.com
> www.pbih.eu
> www.idep.org.uk/xbase
> ---------------------
> I will not send out battalions composed wholly of robots or skeletons
> against heroes who have qualms about killing living beings.
>          [Things I'd do as an Evil Overlord]