12 replies to this topic

[pscEx]

The first BetaKit is available in the download area

It is based on WinBuilder Release 052, containing its new level and folder scheme.

It is fully internationalized using autoLocalize and buildModel.
I adapted all scripts to use this functionality.

Autors are asked to check their scripts from the BetaKit, do according changes on their local scripts and put the changed scripts into the sandbox.

The sandbox contains scripts only which can be build on my system with XP Sp2 and W2003 / German and English.

As an example: The CtrAldDelete.Script cannot be built under W2003 and is therefore not contained.

To have a complete startup WinBuilder installation, you have to download the BetaKit_Basics, too.

Peter

[phox]

It is based on WinBuilder Release 052, containing its new level and folder scheme.

Finaly some order in folder sheme!

Initial comments:

1. qEmu Link and Script belong to Tools folders.
2. There are still Script and script, Link and link.
3. Names should be in the same stille: autorun to AutoRun,
autoUPX to AutoUPX....

If you like, I could make all the necessery changes if you
promise to use them in future relases!

[Brito]

Great work Peter!!

Will test it soon!

[pscEx]

Finaly some order in folder sheme!

Initial comments:

1. qEmu Link and Script belong to Tools folders.
2. There are still Script and script, Link and link.
3. Names should be in the same stille: autorun to AutoRun,
autoUPX to AutoUPX....

If you like, I could make all the necessery changes if you
promise to use them in future relases!

In BetaKit there are *.Link and *.Script only.

I agree to move qEmu to Tools.

Names are author's 'CopyRight'
I personally prefer to start lowercase: autoLocalize, buildModel, myOptions, ...

Peter

[phox]

In BetaKit there are *.Link and *.Script only.

Open some Links and you will find script and link!

Names are author's 'CopyRight'
I personally prefer to start lowercase: autoLocalize, buildModel, myOptions, ...

I agree with you, but in that case all names should be in the same stille:
autoRun, notePad, ramDisk....

You could suggest to authors to comply with general WB stille!

[pscEx]

Open some Links and you will find script and link!

I agree with you, but in that case all names should be in the same stille:
autoRun, notePad, ramDisk....

You could suggest to authors to comply with general WB stille!

1st: OOPS!
I'm going inside and change!
2nd: I do not feel to be allowed to change the name somebody gave his/her script. And I do not want that somebody else does it with my scripts.

Peter

[smiley]

What's its real difference with sandbox?Does this means end of support for sandbox?

[pscEx]

What's its real difference with sandbox?Does this means end of support for sandbox?

No!

There are several topics about organization, mainly suggested by Phox.

The sandbox still remains. It is an alpha-area where the developers can upload their new or changed scripts.

If they fit into some criteria
- independent from source OS
- independent from language
- boot from ISO
- ???
I'll move them into BetaKit.

Nuno can move them from BetaKit into official 'StarterKit' or next release.

So it is a little bit sure that there are only scripts in the release which run on most PCs.

Peter

[smiley]

[phox]

2nd: I do not feel to be allowed to change the name somebody gave his/her script. And I do not want that somebody else does it with my scripts.
Peter

You should have authority to suggest and make changes
and than ask authors to review them and accept them
or refuse with strong arguments.

[TheHive]

In the WinBuilder_BetaKit_Latest.zip there is still an empty folders for PicoXP and its contents.

Testing with the latest 11-22-06
WinBuilder_BetaKit_Basics.zip
WinBuilder_BetaKit_Latest.zip

In Standard I get the error:
The file mouclass.sys could not be found. Press any key to continue.

Log
[attachment=801:attachment]

With HoJoPE i get the same error
The file mouclass.sys could not be found. Press any key to continue.
Log
[attachment=802:attachment]

[pscEx]

In the WinBuilder_BetaKit_Latest.zip there is still an empty folders for PicoXP and its contents.

Testing with the latest 11-22-06
WinBuilder_BetaKit_Basics.zip
WinBuilder_BetaKit_Latest.zip

In Standard I get the error:
The file mouclass.sys could not be found. Press any key to continue.

Log
[attachment=801:attachment]

With HoJoPE i get the same error
The file mouclass.sys could not be found. Press any key to continue.
Log
[attachment=802:attachment]

The mouse is back!

I'm going to look for that

But please first try that

Peter

[pscEx]

The mouse is back!

I'm going to look for that

But please first try that

Peter

I found the reason:

Something is going wrong with the new level / folder constellation of release 052.

If you choose the option 'Use advanced view to group scripts' everything is running well.
But if you do not choose this option, the order of scripts is not that one which guarantees a successful build.

E.G. the projectInfo script (which must run as the first script) is running as #5 or #6 when GroupScripts=0

I'll try to rearrange levels / script names in BetaKit to have a successful build independent on whether GroupScripts=1 or GroupScripts=0

Peter