Category Archives: Clarion News

Freeze that control

Clarion 7.1 introduces two new functions; FREEZE and UNFREEZE.  FREEZE/UNFREEZE are used in tandem to suppress redrawing while you adjust multiple attributes of a control. For example, you would typically call the FREEZE method, then set the Size, Location, Text, or Color properties of the control, and then call the  UNFREEZE method to enable the changes to take effect.  This can increase the performance of applications with many controls, and eliminate screen flicker when dynamically creating controls or adjusting their properties.

The syntax is:

FREEZE (SIGNED feq),SIGNED

FREEZE suspends redrawing of the control which is identified by the feq parameter.
The return value must be passed to a paired UNFREEZE.

UNFREEZE (SIGNED feq, SIGNED state)

This function resumes redrawing of the control previously suspended by FREEZE.
The second parameter is a value returned by last FREEZE for that control which has not been closed
by paired UNFREEZE.

Calls to FREEZE can be nested. Every such call must have its paired UNFREEZE,
for example:

x1# = FREEZE (feq)
...
x2# = FREEZE (feq)
...
UNFREEZE (feq, x2#)
...
UNFREEZE (feq, x1#)

FREEZE and UNFREEZE must be properly paired: if there isn’t a paired call to UNFREEZE for an executed FREEZE, the control cannot be redrawn. The UNFREEZE function forces redrawing of the control.

(note: FREEZE/UNFREEZE cannot be used for menu items)

Precompile and Publish ASP.Net web apps

We’ve added some new functionality to the IDE in support for precompling and publishing a web app.  As you know by default, ASP.NET dynamically parses and compiles any ASPX page when the first request is made for the page. The .Net runtime caches the compilation outputs and does not need to recompile again unless someone edits a file. This behavior brings us a good amount of flexibility, including the flexibility to change code and markup. and instantly see the changes reflected in the next browser request.  ASP.NET 2.0 introduced the option of precompiling your website. Precompling offers the following advantages :

  • You do not need to deploy the source code to the server. The website is precompiled into binaries, which are then deployed to the server.
  • It allows you to identify any bugs during compilation rather then opening each page
  • The deployment process is a bit easier as all your aspx pages, user controls etc. are compiled into binaries.There are a few different ways you can precompile a website.
Precompiling websites at the command-line

When you have an ASP.Net project open the IDE command “Build” only validates the project and puts the assemblies into the ASP.NET temporary folder.

The values you enter on the new MSBuild tab of the Propect Properties are valid if you want to build the project from the command line. So at a command prompt you use this syntax:

MSBuild <projectfile>.aspxproj /target:Msbuild /property:ClaNetBinPath=<Clarion.Net BIN folder>

aspprocomp

Precompile and publish websites using the Clarion IDE

To precompile and publish your website using the IDE follow these steps:

1. Open your website project
2. In the Solution Explorer right-click on the Project and from the context menu choose “Publish Web Site”

asp1

3. You then get a Publish Web Site dialog like shown below where you can specify the path to publish. Clicking on the eplisis(…) lets you choose a folder.

asp2
4. Select your options in the dialog :

a. Allow this precompiled site to be updatable – This option allows you to change the markup and client side functionality of the .aspx pages.
b. Use Fixed Naming And Single Page Assemblies
c. Enable strong naming on precompiled assemblies – specifies that your assemblies are strong named using a key file or container.

5. Click Ok to compile and publish the website. Continue reading Precompile and Publish ASP.Net web apps

Manifest support for Windows 7

We’ve just added support for creating the new Windows 7 compatibility sections in the Application Manifest to both the Templates, and the Linker.

appmanifest

With the settings above your manifest is generated with these two new sections:

<compatibility xmlns=”urn:schemas-microsoft-com:compatibility.v1″>
<application>
<!–The ID below indicates application support for Windows Vista –>
<supportedOS Id=”{e2011457-1546-43c5-a5fe-008deee3d3f0}”/>
<!–The ID below indicates application support for Windows 7 –>
<supportedOS Id=”{35138b9a-5d96-4fbd-8e2d-a2440225f93a}”/>
</application>
</compatibility>

The Linker uses the MANIFEST directive and has been extended with the following options:

MANIFEST VISTA WINDOWS7
— The linker adds the default manifest to the executable compatible with records indicating application compatibility with both Windows Vista and Windows7

Note that Windows XP and Windows Vista ignore this manifest compatibility section and it has no impact on them.

Report Writer


This Friday we’re going to demonstrate the new Report Writer on Clarion Live!. Our thanks to John Hickey and Arnold Young for inviting us back!
I thought I’d take a few minutes to point out some of the features and give you a feel for the UI.  Here’s a scaled-down screen shot of the main view.

Report Writer - main view
Report Writer – main view

Everything is done from this main view, in this next shot I had just pressed the “Preview” button.

Preview the Report

As you can see, when you go into Preview mode a new toolbar appears that provides some great functionality, including the ability to search the report, save the report to a number of formats and even email the report in your desired format.

search1

There are some great options for saving the report to disk or for emailing.  The email button invokes the client
machine’s default email program.

export formats

Back into Design mode, one feature I think you’ll love is the support for “Styles”.  Styles let you define background colors, borders, fonts and text alignment which then makes its very easy to quickly set all your fields or static text to a nice uniform look.

styles

Styles can also be applied to Report Bands, for example that’s how I gave this report the the two different shades of blue for the odd and even rows.

styles2

The Group and Sort Pad makes it easy to apply grouping/sorting to any report.  Grouping and Sorting can be done by an end user with just a few mouse clicks.

groupsort

There are 17 controls available to build your report with:

toolbox1

The Report Wizard does a great job of getting you started, it allows you to select both a style (which you can customize), and a layout.

rptstyle2

layout1

And there is builtin support for creating labels:

labels

Hopefully this post gives you a good idea of what’s coming.  We’re working hard now on TXR conversions, which many Clarion developers have told us is very important to them, and we’re fixing bugs found internally, but it won’t be long before we make a beta version available.

Its worth mentioning that the new Report Writer will be shared by both Clarion 7 (win32) and Clarion.Net, and it includes support for doing advanced scripting using Clarion# at design time.  There is much more functionality, and great features to talk about, and as the documentation progresses we’ll post a detailed spec sheet on the web site.

Clarion 7 – new release

A new release for Clarion version 7 went out today, it includes some key bug fixes for recently identified problems, along with one new feature that seems to have some users up in arms when they found it missing, namely the “Block Indent dialog”.  Not sure what that means?  Well a picture should clear that up…

blockindent

sure to make a few developers happy, or at least happier 😉