25 replies to this topic

[pscEx]

The script uses [Verify] entries in script.project and inside the single scripts and checks your project following the rules decribed in that entries.

Discrepancies are reported.

The Script can:

• Check dependencies
• Check excludes, also 'either - or'
• Check execution order
• Check correct correlation between options in different scripts
• Works with macros
• Grouping of conditions
• Dynamical insert of actual values in error text
• Check for minimum WinBuilder version
• ...

BTW: The logic is inside a Delphi DCU which could easily be integrated into WinBuilder.
There is only one interface procedure:

procedure  buildErrors(const ctlName: string; var errList, missingList: TStringList);

@Nuno: The error list could be in orange in the .log file
WBVerify.Script is for download here

Peter

Edited by pscEx, 16 June 2012 - 08:09 AM.
Actualized link

[TheHive]

Generated by psc program 'WBVerify' version 1.0.0
Date: 2007-Jan-15 10:46:03


No issues found in the project!

[phox]

Verify is working OK!

New version of Explorer in nativeEx remove Internet Explorer
question, but folder title is still Microsoft Internet Explorer!



BTW: What is the corect name of the Project:
nativeEx
NativeEx
nativeEX
NativeEX

[pscEx]

New version of Explorer in nativeEx remove Internet Explorer
question, but folder title is still Microsoft Internet Explorer!

Let me some time to find out...

BTW: What is the corect name of the Project:
nativeEx
NativeEx
nativeEX
NativeEX

When creating, I gave it the name 'nativeEx'. This are still folder names inide the download center.
When generating the new organization with beta 13, (or 12?) Nuno renamed to NativeEX. I accepted the uc EX but wanted to hold on lc n. Therefore I currently use nativeEX.
Would like to have the original name back!.

Peter

[phox]

Would like to have the original name back!.

Peter

YES! and please, correct it everywhere!

Thank you.

[Brito]

Let me some time to find out...
When creating, I gave it the name 'nativeEx'. This are still folder names inide the download center.
When generating the new organization with beta 13, (or 12?) Nuno renamed to NativeEX. I accepted the uc EX but wanted to hold on lc n. Therefore I currently use nativeEX.
Would like to have the original name back!.

Peter

Sorr for the wrong casing, will also use the correct designation - nativeEX it is!

[pscEx]

I there is a new version available at the URL of the first link.

Main changes:

• works with macros now
• grouping of conditions
• dynamical insert of actual values in error text

It is also included inside !Fundamentals.Script version 005 in the Download Center.
Before download please delete WBVerify.ctl. (I'll do it automatic later)

Peter

[pscEx]

There is a new version available.

Now the check statements are inside the script rather than in WBVerify.ctl.

Additionally I followed a suggestion by Thunn to make the WBVerify portable.
Instead of script paths the script titles can be used. Then WBVerify queries the script paths inside the actual project.

The new script is available from the nativeEX_barebone download server.

Peter

[Brito]

I've tried the new version, worked just great!

[TheHive]

Bug!
If WB Verify script is active and you press the Play button.
The Build process will finish at WB Verify Script finishing the verification and presenting the user the results. So the whole project Scripts will processed to finish.

[pscEx]

Bug!
If WB Verify script is active and you press the Play button.
The Build process will finish at WB Verify Script finishing the verification and presenting the user the results. So the whole project Scripts will processed to finish.

Thanks

Fixed.

Peter

[pscEx]

Again I uploaded a new version.

Now it is possible to write [Verify] checks into the scripts where they correspond to.
That gives the .script developer the ability to make his verify checks w/o delivering a new WBVerify.Script version.

Some nativeEx_barebone scripts I changed accordingly.

Sample: Explorer.Script contains

[Verify]

If {%Explorer:Main.Selected%}

& !{%RAMDisk:Main.Selected%}

& !{%Boot SDI:Main.Selected%} Then

"Explorer needs RAMDisk or BootSDI Script";

If {%Explorer:Main.Selected%}

& !{%Misc Settings:Main.Selected%}

& {%Explorer:Interface.pCheckBox1%} Then

"When excluding MiscSettings.Script, you must uncheck 'Don't set Explorer as shell' in Explorer.Script";

Peter

[TheHive]

With the update the Wb Verify is confused to where the exe is. It doesnt know where it is.

[pscEx]

With the update the Wb Verify is confused to where the exe is. It doesnt know where it is.

Oops ...

Fixed.

Peter

[TheHive]

Seems to be working properly.

[pscEx]

Again a new version available at the nativeEx_barebone download server

Main changes:

• The project's basic checks are moved from WBVerify.Script to script.project. That makes WBVerify.Script project independent.
  New versions of WBVerify.Script can be copied between scripts.
• An optional handling of obsolete scripts is included.
  If there are two .scripts with different names and identical titles, then the .script with the lower version is assumed to be obsolete.
  Optionally you can
• Report the script as obsolete
• Rename the script and let it remain in the folder where it is
• Rename the script and move to %BaseDir%\Projects\Obsolete
  If the Obsolete folder does not exist, it is created.
  Renamed script contains additional
• Date and Time of rename
• .old extention

[*]Macros are recognized across the complete project.
That means that macros defined in script.project or any script can be used in every script.
Caution: If an existing macro is redefined anywhere else, that can bring unpredictable results!
[/list]When you download the new WBVerify.Script, make sure also to download script.project!

Peter

Attached Thumbnails

• 

[TheHive]

Very good implementation and expandability.

[pscEx]

I upload a new version.

At a different place TheHive mentioned that somebody can download nativeEx_barebone only. Then he has no Tools directory and a build fails with errors a newby cannot understand.

I added to the syntax that the program ca check whether a fil exists.

script.project got the additional [Verify] lines:

Macro "Tools" If !{%#arg1#%} Then

"Missing ?%#arg1#%?. Please download the Tools directory from WinBuilder server";

...

Call "Tools" (..\Tools\7zCon.sfx);

Peter

[TheHive]

lol! I just got that error message.

Projects\Tools\7zCon.sfx. Please download the Tools directory from WinBuilder server

But if Im just beginning I wouldnt really know how to do the download it asks for. Mainly because the tools folder is in the LiveXP project. Its not seperate from the LiveXP project and thus self maintained.

We need a better implementation. Like having the user download the Tools folder mandatory when they select a Project. So the tools folder would be similar to a project of its own. Or a better method

[pscEx]

lol! I just got that error message.


But if Im just beginning I wouldnt really know how to do the download it asks for. Mainly because the tools folder is in the LiveXP project. Its not seperate from the LiveXP project and thus self maintained.

We need a better implementation. Like having the user download the Tools folder mandatory when they select a Project. So the tools folder would be similar to a project of its own. Or a better method

I'll change the text to

"Missing support program. Please click the 'Download' tab and download the Tools directory from updates.boot-land.net";

But you are right: The Tools implementation should be better.

@Nuno: Think about:

• Tools is on a separate server
• All projects' update.ini have a link to this server
  > Independent from the server choice you see the Tools folder

Peter

[Brito]

There are some projects that won't require so many tools to be downloaded, but I like the idea to centralize a single place, this is somewhat done on updates.boot-land.net - perhaps the wise method is to keep as is for the moment..

[thunn]

The verify script will proove very helpfull, I'm glad the bugs are worked out, I'll start using it to confirm project status shortly, thx. Peter!

Regarding tools...
A main tools directory may save a little space. Project developers can always add them as needed.
I'm glad it came up because I just replaced 7za.exe with a renamed 7zr.exe, I told Nuno about this but it was never used. 7zr.exe is a new reduced version of 7za.exe that will do everything we require. After UPXing, it's only 114 KB, a quarter the size of the uncompressed 7za. I've tested it and no problems. If you guys see this post maybe we can agree to name it correctly, or not, it works as is. I finally got over hidec.exe renamed to hiderun.exe, so I'm ok.
Also worth noting is the Active@ burner was deleted from my tools and replaced with an almost identical, but smaller tool, Burniso.
Size matters...

[Brito]

Yes, it would be good if they replace the currently used ones without prejudice to other projects..

[pscEx]

Yes, it would be good if they replace the currently used ones without prejudice to other projects..

@Thunn, @Nuno:

Please move all what not is due to WBVerify to a new topic.

I do not like to have a topic 'decorated' with external issues.

Peter

[pscEx]

There is a new version of WBVerify available.
It can check the WinBuilder version.

How it works:

• The Fundamentals script writes the version of the active WinBuilder app into script.project:Main:WBVersion, format: 'vvv.bb'
  vvv: version with leading zeroes
  bb: beta version with leading zeroes. If no beta, just '00'
  beta 'subclasses' a, b, ... are not respected
• The single script has a Verify entry, sample:
  Call "WBVersion" ($$$,071.03);
  This raises an error if the actual WinBuilder version is lower than 071 beta 3
  The compare value MUST be also in the format 'vvv.bb'

The changed scripts are:

• !Fundamentals
• script.project
• !WBVerify

In addition I redelivered scripts using the new verify option:

• Copy&Expand
• ImDisk

Peter