15 replies to this topic

[ozbob]

I have been looking and searching around how to use the interface object called checklist. So far I have not been able to find any reference for this object. I would like to find out how to make use of this feature. Currently I am running Winbuilder 072a.

By the way I would like to mention that Winbuilder is really a nice and user friendly tool, also for my needs which consists of building unttended Windows installation images in conjunction with tools like nLite, Xpize modified winnt.sif etc. So far this tool has been the best approach way of doing this as it can run modular and has great logging features.
The only thing which I am missing in Winbuilder is a lack of getting it to read file lists and put them up in a screen for selection, hence my question as it might be there if I know how to use checkfile.....

[Brito]

Hi ozbob!

There is a checklist component on the interface - but it was not completed mostly because of other requests that appeared as things moved on.

If you wish, we're just starting the discussion for the new beta wb and this feature can likely be added without hassle.

What is the type of behavior and syntax you find more suited?

We can have a checklist that reads all INI values from a section and simply adds true/false values.

To create lists of files and display them on your scripts I would recommend creating a small script in autoIt or any other programming language that would write the interface section on a given script and update it as needed.

If you don't know how to do it - likely a few other members around here can help you getting it done.

--------------------------------------


It's very good to hear that you have experience with unattended installs.

There is a winbuilder project which needs someone with enough know-how and motivation to finish it and maybe you'd be interested in picking it up and improve it to meet your unattended standards.

Look here for more informations: http://www.boot-land...tall-t2673.html

The driverpacks team is willing to help, xpize is open source and can also be included - only missing nlite from the list of automated programs but maybe we can talk with nuhi to allow working alongside with nlite as well - we're already mirroring the oficial nlite distribution in the boot-land.net server.

The idea was to automate all these steps needed to build an unattended CD and mixing it with a xp based liveCD to create a good all-in-one tool.

Hope you like it - let me know your opinion..

[pscEx]

Today I had an issue where the functioning checklist could help.

In updateCore.Script could be nice if the user defines which nativeEx core items he / she wants to download into LiveXP or NativePE or ...

Currently I solve by radioboxes:

• existing scripts only
• all scripts

@Nuno:
So would be nice if you use hours 25 to 29 of your day to finish the checklist.

Peter

[Brito]

Ok, give me some time to see what can be done..

[Brito]

It's added on the next beta.

Add a section inside the script like this:

[test]

2123=0

dsa=True

sdfdf=1

sdfd=False

sdf=1

wer3=0

thjthy=1

And the listbox will change these value acording to the user's click-check.

Acepts both True/False and 1/0 values.

[pscEx]

It's added on the next beta.

Add a section inside the script like this:

[test]

  2123=0

  dsa=True

  sdfdf=1

  sdfd=False

  sdf=1

  wer3=0

  thjthy=1

And the listbox will change these value acording to the user's click-check.

Acepts both True/False and 1/0 values.

Currently it sounds Arabic for me.
(Name of the box = 'test' ?)
Let's wait for the beta!

Peter

[Brito]

Maybe an image can help understand..



Here's the code found inside the script:

[Interface]
pCheckList1=test,1,9,68,72,200,200,
pTextLabel1=pTextLabel1,1,1,11,27,230,18,8,Normal

[test]
1=0
2=1
3=0
4=1
5=0
6=true
7=0
8=true
9=0
10=1

Whenever the user click and marks a check or uncheck any item - it will write the respective value on the [test] section.

[pscEx]

Maybe an image can help understand..

Thanks
I hope you have finished the new beta within 5 (Latin) minutes.

Peter

[Brito]

It's just about ready for tests - but I'm still working on some details that I'm not yet happy.

[ozbob]

It's just about ready for tests - but I'm still working on some details that I'm not yet happy.

Nuno,

Thanks for your reply, had found the scripts for unattended install already, this is how I got here in the first place.
As to the list requirements for me; I would like to have a way to fill the dialog with files and be able to select multiple files to process.

I have another odity with variables;
my code line reads: If,%pCheckBox1%,Equal,True,Set,"%ApplicationDescription%","Dotnet 3.0"
No matter what I do the contents of ,"%ApplicationDescription% breaks down with Dotnet, the space and 3.0 are being dropped. Am I doing something wrong here or could this be a bug with the set command?

Thx

[pscEx]

my code line reads: If,%pCheckBox1%,Equal,True,Set,"%ApplicationDescription%","Dotnet 3.0"
No matter what I do the contents of ,"%ApplicationDescription% breaks down with Dotnet, the space and 3.0 are being dropped. Am I doing something wrong here or could this be a bug with the set command?

try:
If,%pCheckBox1%,Equal,True,Set,"%ApplicationDescription%","Dotnet#$s3.0"

Sometimes spaces, commas, quotes, disturb WinBuilder.
Then you should use the corresponding 'special character' (to be found in the statement wizzard.

Peter

[ozbob]

try:
If,%pCheckBox1%,Equal,True,Set,"%ApplicationDescription%","Dotnet#$s3.0"

Sometimes spaces, commas, quotes, disturb WinBuilder.
Then you should use the corresponding 'special character' (to be found in the statement wizzard.

Peter

Thanks Peter, this was the solution, however it doesn't make things more readable in the script. Maybe there should be another special character that defines everything between the markers shuld be left alone and parsed on.
My problem is solved never the less.

[allanf]

Maybe an image can help understand..



Here's the code found inside the script:





Whenever the user click and marks a check or uncheck any item - it will write the respective value on the [test] section.

Hi Nuno,

This looks good, and I have it working as described.

One question about its purpose/function...

In order to use the CheckList to do things, is it necessary to 'IniRead' each key-value and assign the value to a Variable, then have a Script do something on the basis of the Variable?

... or is there a more streamlined way to do something on the basis of the key-value directly?

Thanks

[Brito]

Thought I haven't (yet) tried what I'm about to suggest - I would recommend using the [variables] section inside %scriptfile% as repository for all the values that you need to place on that list.

If you need to add more variables then these could be placed on a different section and inserted when the [process] section is executed.

I've recently used this list feature here: http://xp.winbuilder...1-Addons.script

Made a small binary to find all files inside a subfolder and add them on the list to be processed by nlite.

[allanf]

... or is there a more streamlined way to do something on the basis of the key-value directly?

Thanks

OK. I found a way. It looks a bit dangerous though.

If the CheckList Section is called [test], every key-value can be assigned to a variable-value with:

AddVariables,"%ScriptFile%","test"

Dangerous because every key - without percentage signs, becomes a variable - without percentage signs! That is, every occurence of the key word in the script will be read as a Variable with a Value.

For example:

[process]

AddVariables,"%ScriptFile%","test"

Message,"testing to see if this works"



[test]

testing to see if this works=1

... will return a MessageBox with '1' in it!

[Brito]

That's a good solution!