WebHub Release Notes for v1.500

In the Built-In Macros

• Branding supports Framesets v1.497
  Branding now supports framesets, with the same options as HREF links, meaning that 'STATIC' is also supported.

In the WebHub VCL

• Trial version of Form-To-HTML converter v1.497
  This component may be used by any VCL programmer (Delphi or C++Builder) to convert the controls in a form to HTML. details here.

• Branding supports Framesets v1.497
  Branding now supports framesets, with the same options as HREF links, meaning that 'STATIC' is also supported.

• Bug fix in the TRestorer component v1.497
  The GPF showed up only in the designer, and only in D3. Many thanks to Philippe Maquet and Michael Ax for finding and fixing it (after about 9 hrs of debugging!)

• Bug fix in TWebDataSource v1.497
  Webdatasource now properly closes a clone before destroying it. By adding 'CLOSE' to a command sent to a webaction, you suppress executing it. (This fixes the HTQ2 demo.)

• Bug fix in animation v1.497
  Automatic slide-show advances were not working. They are ok now; see SHOWCASE demo.

• CgiHttp property v1.497
  %=CGIHTTP=% when in ssl returns https://domain:443 properly now. This was a problem in v1.44-v1.496.

• Reminder: update web actions v1.27+
  Before counting on a surfer-specific property on a web action component (e.g. TWebCreditCard or TWhBrowserInfo), make sure that you %=webaction.update=% so that the save-state data is loaded.

Documentation

Demos

Known Problems

New Tracing Feature

new types used to interface with the trace events:
  TOnTracePChar = procedure(Sender:TWebOutputApp;Text:PChar;Before:Boolean)
of object;
  TOnTraceString = procedure(Sender:TWebOutputApp;const
Text:String;Before:Boolean) of object;


new public method:
    procedure TraceBuiltInEvent(const EventName,Parameter:String);
		used to inform the trace code that a certain builtin event is about to be
processed. see usage example in htwebapp.pas


new public properties:
    property  TraceEnabled: Boolean read fTraceEnabled write fTraceEnabled;
		Enables the tracing code to recognise the trace related events. webhub is
optimized internally so that the tracing logic does not slow down pages
when tracing is inactive.

    property  TraceInHTML: Boolean read fTraceInHTML write fTraceInHTML;
		controls if trace output is to be in html form. this property exists
soley for the purpose of the html panel and can be affected from there and
through the TraceOn/Off properties.


new published properties:

    property TraceOn: String read GetTraceOn;
		reading traceOn from HTML (with %=TraceOn=%)  enables html traceoutput
for the current page/surfer.

    property TraceOff: String read GetTraceOff;
		reading traceOff from HTML (with %=TraceOff=%)  disables html traceoutput
for the current page/surfer.


    property OnTracePChar: TOnTracePChar read fOnTracePChar write
fOnTracePChar;
    property OnTraceMacro: TOnTraceString read fOnTraceMacro write
fOnTraceMacro;
    property OnTraceChunk: TOnTraceString read fOnTraceChunk write
fOnTraceChunk;
    property OnTraceComponent: TOnTraceString read fOnTraceComponent write
fOnTraceComponent;
	
		the above events are used to inform the trace-logic that text, macros,
chunks, or components are being rendered. it's likely that they will be
collapsed into a single event in future versions. the parameters to these
events are read-only and can not be used to modify what will be sent. for
that, please override the sendmacro, sendpchar or sendbufferedchunk
procedures.


to add tracing to your app, consider adding the following logic to your
page header:

	%=IF|WantToTrace|%=TraceOn=%=%

Note that the html trace output can break otherwise perfect html and/or
javascript. 

For example you may not be able to submit forms from a page containing
trace- output of a form built using the %=WHERE=% or %=ACTION=% macros (use
the input macros to avoid this particular case) . To avoid getting stuck,
you might want to add a %=CLEAR|WantToTrace=% to your homepage or some
other central page so that you can bail out.

Another option is to put %=TraceOff=% before tags that would get broken by
the trace and to re-enable the trace thereafter by repeating the
%=IF|WantToTrace|%=TraceOn=%=% in your document. this will let you trace
everything on a page while protecting javascript or form sections.

lastly, the CMDHAS macro might provide a good way for you to integrate
remote tracing into a webhub app. By using %=CMDHAS|Debug314|%=TraceOn=%=%
you could conditionally enable a remote trace from afar. be careful to not
use an easy to guess command as to keep details about your pages from others.