WebHub Version 1.06 Release Notes

Improvements in Release 1.06

In the Hub + Runners

• HubUI
  Several small changes were made in the HubUI to help you see the path and size of Chunk and Session Files.

In the Components

• AS/400 testing now possible
  This build removes resource conflicts with Delphi for AS/400, enabling compatibility testing.

   

• SaveState mechanism improved
  Previously you had to use %=WebAction.Execute=% to insure that a component's properties would be correct for the surfer. This required a workaround if you wanted to refer to that component's properties before executing it. 106 lets you do away with these workarounds and allows you to trigger %=WebAction.update=% to have the save-state mechanism update the properties for you.
  

   

• WebDropDown
  The WebDropDown component now has a Text property. This is demonstrated in the SaveState sample file

   

• The end of manual refresh
  We've removed a check that would prevent the app from updating when loading. This used to strand your WebDatasources and Grids in an unupdated state requiring some code to refresh them 'manually.' We're pleased to announce that according to our testing you no longer need this workaround code and that things finally work 100% the way you'd expect them to.

   

• TWebMailForm
  • Template file lets you do mail merge on the fly. Macro expansion is supported. You have to use the WhMail panel to get this feature.
  • Multiple recipients for TO, CC and BCC are now supported. Use a semi-colon to separate the addresses, e.g. ann@href.com;ax@href.com.

   

• AppDefault and PageDefault Macros
  You can now set application and page defaults using macros. Wow.
  Set AppDefaults with: %=AppDefault|Key=Value=%
  Get AppDefaults with: %=AppDefault.Key=%
  Set PageDefaults with: %=PageDefault|Key=Value=%
  Get PageDefaults with: %=PageDefault.Key=%
  

   

• Setting page defaults from the file level
  You may have used set defaults on the page level from the
  [TWebApp.Files] section of your .ini file in the past to define slideshows. Entries would look like this:

  ExIndex=ExIndex,reset,sequence.off
  ExTopic=ExTopic,reset,sequence.auto,up.examples,final.homepage
  

  These Values would flow into [page.defaults] as 'Defaults='. This was useful; Still, we've extended this mechanism to let you set additional defaults for all pages in a file like this:
  

  ExFile=ExFile,reset,key=value,sequence.off,key2=value2,etc..

  Once defined, you can add to and access these addtl. values (key and key2 in this example) using the PageDefault syntax shown above.

   

• D3 Cloning
  The patch perfecting the cloning of calculated fields under D3 which had previously been posted is now part of this release.

   

• WebApp.refresh
  Instead of sending an unsightly exception, triggering WebApp.Refresh now sends a plain message with a link to your application's homepage.

• ACE Compatibility
  ACE is a client-server replacement for the BDE, for use with .dbf files. Zac Catalog is using/recommending it with WebHub. The Sept. 1 patch2.zip file (for registered customers only) provides a new wdbscust.pas unit which gives you TAdsWebDataSource = class(TWebDataSource). Use TAdsWebDataSource in place of TWebDataSource whenever you want to connect through to a AdsTable.

In the Demos

• HTEM
  changed to use WhMail template file instead of form letter component. added waFixed feature back in. (lost when?!?)

• HTLS
  changed to HubApp using WhMail template file

• HTFS
  removed explicit refresh on weblistgrid component (shipping price grid)

• HTQ1
  removed explicit refresh on webdatasource1

• SHOP1
  fixed order list so that values from prior demos such as MsgTo=ann@href.com would not appear. The issue was the '@' symbol. It was being checked in the entire Literal, instead of just in LeftOfEqual.

Known Bugs in Components

why: surfer 'restore state' called tpupdated, triggered a recursive descent.

solution: make sure the TWebDatasources on your forms are UPDATED before they are executed. possibly when the dfm's are saved.

background question: what conditions need to be in place for a TWebDatasource to update? The TWebDatasource requires TWebApp to be updated, and it's DataSource & DataSet to be assigned.