Atozed Software IntraWeb Ultimate Edition v15.2.35
Atozed Software IntraWeb Ultimate Edition v15.2.35
IntraWeb supports RAD Studio / Delphi XE2, and in fact is included as a part of RAD Studio / Delphi XE2. If you have RAD Studio / Delphi XE2, you already have IntraWeb XII. RAD Studio 2009, 2010, XE, XE2, XE3, XE4, XE5, XE6, XE7, XE8, 10 Seattle, 10.1 Berlin, Delphi 10.2 Tokyo, Delphi 10.3 Rio and Delphi 10.4 Sydney.
Faster Template Processor
The template processor has been rewritten and is up to 3x faster. The template processor is a commonly used feature and will create faster applications and lower CPU usage.
Fastest zlib Library
We now have the fastest zlib in the Delphi world, 3x faster than std XE8 zlib x64.
Note: IntraWeb 15 requires a license key version 11 (starts with +0011). IW 14 license keys won’t work with IntraWeb 15.
A new IW 15 license has been automatically generated for all paid customers with active subscription. The new license can be obtained in our purchase point online: https://app.atozed.com
Login using your registered e-mail and password and go to IntraWeb -> My Keys. Check the last key on your key list. It should start with +0011. This is your key for IntraWeb 15.
IntraWeb 15 is not a free upgrade for IntraWeb 14 bundled users
You can install IntraWeb 15 as evaluation for testing purposes. Evaluation version never expires. It can’t be installed with some older version of IntraWeb in the same IDE, though.
A new IW 15 license has been automatically generated for all paid customers with active subscription. The new license can be obtained in our purchase point online: https://app.atozed.com
Login using your registered e-mail and password and go to IntraWeb -> My Keys. Check the last key on your key list. It should start with +0011. This is your key for IntraWeb 15.
IntraWeb 15 is not a free upgrade for IntraWeb 14 bundled users
You can install IntraWeb 15 as evaluation for testing purposes. Evaluation version never expires. It can’t be installed with some older version of IntraWeb in the same IDE, though.
15.2.35 Version History
New
RenderBootstrapThemeFile in jQuery Grids (default False). When set to True, IWjQGrid will also render bootstrap-theme.min.css file which adds gradients/animation effects to Bootstrap theme. Plese notice that this is not compatible with standard IWBoostrap theme (thus IWjQGrids used in IWBoostrap applications should set this to False)
Modified
IWBootstrap 3 and 4 now render JS and CSS files using the same IWPageContext methods as other IW components. This avoids that different controls render duplicate files
ContentHandlers: Extension or catch-all content handlers should have precedence over path match when document/extension is not empty (the request URL is composed of path + document + extension, e.g. in ‘/somefolder/index.html’, path=’/somefolder/’, document=’index.html’, extension=’.html’). This means that, for instance, a request to https://yourdomain/somedoc.html will be handled in the following order, if available: (1) a content handler registered for the exact path ‘/somedoc.html’ (2) a content handler registered for html extension, (3) a catch-all content-handler, (4) a content handler registered for ‘/’ path (root or URLBase of the application).
Bug fixes
Force HTTPS to retrieve jQGrid/IWBootstrap CDN files so browsers won’t block it (mixed blocking)
IWSelect would fail to select multiple items via SelectedValue property
Body script files could be rendered twice when using templates
IWBootstrap 3 and 4 rendering would conflict with other jQuery plugins using Bootstrap theme
Fix rendering of content files (JS and CSS)
Fix memory leak in Http.sys server
New
RenderBootstrapThemeFile in jQuery Grids (default False). When set to True, IWjQGrid will also render bootstrap-theme.min.css file which adds gradients/animation effects to Bootstrap theme. Plese notice that this is not compatible with standard IWBoostrap theme (thus IWjQGrids used in IWBoostrap applications should set this to False)
Modified
IWBootstrap 3 and 4 now render JS and CSS files using the same IWPageContext methods as other IW components. This avoids that different controls render duplicate files
ContentHandlers: Extension or catch-all content handlers should have precedence over path match when document/extension is not empty (the request URL is composed of path + document + extension, e.g. in ‘/somefolder/index.html’, path=’/somefolder/’, document=’index.html’, extension=’.html’). This means that, for instance, a request to https://yourdomain/somedoc.html will be handled in the following order, if available: (1) a content handler registered for the exact path ‘/somedoc.html’ (2) a content handler registered for html extension, (3) a catch-all content-handler, (4) a content handler registered for ‘/’ path (root or URLBase of the application).
Bug fixes
Force HTTPS to retrieve jQGrid/IWBootstrap CDN files so browsers won’t block it (mixed blocking)
IWSelect would fail to select multiple items via SelectedValue property
Body script files could be rendered twice when using templates
IWBootstrap 3 and 4 rendering would conflict with other jQuery plugins using Bootstrap theme
Fix rendering of content files (JS and CSS)
Fix memory leak in Http.sys server
Only for V.I.P Warning! You are not allowed to view this text.