Jump to content











Photo
* * * * * 3 votes

WinBuilder 071 - beta version


  • Please log in to reply
157 replies to this topic

#1 Brito

Brito

    Platinum Member

  • .script developer
  • 10616 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 14 May 2007 - 09:55 PM

Hi everyone!

This topic is meant to discuss WinBuilder.exe.

Everyone is welcome to download the latest beta and post requests of features or bug support for the newer version.

To keep this topic centered on the just the executable please post any issues regarding scripts or projects on the respective sub-forums to keep things tidy and organized (except if directly related to changes introduced by a beta).. :confused1:




Beta 11 (2007-07-12)

- Syntax errors are added on log along with the full syntax used
- some bugfixings of previously added features.
- Added quick navigation buttons to allow pressing forward and backward while browsing scripts
- Modified the unattended box for running projects - also added /debug switch to help evaluate used parameters
- Main window will automatically remember and open the last selected project in winbuilder.ini
- Modified the Interface handling when scripts are executed - it was buggy under some conditions


Attached File  WinBuilder071_Beta11.zip   821.02KB   767 downloads

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





Beta 10b (2007-07-09)

- more bugfixes and small improvements
- Limited treeview on main window to avoid excessive width
- Added more informations when using webget
- Changed default logo image for scripts without logo
- Added new parameter on FileCopy - using "show" as last parameter will display the advance of the file copy operation.
- Fixed ExtractAndRun - wasn't working correctly.


Attached File  WinBuilder072_Beta10b.zip   808.56KB   627 downloads


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


Beta 9 (2007-07-08)

- changed tab titles to be larger on script editor
- small bugfixes
- Added a better web server manager
- Added missing translation texts


Attached File  WinBuilder071_Beta9.zip   807.26KB   667 downloads


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



Beta 8 (2007-07-05)

- Overall bugfixing from latest changes
- Added the option to print the currently viewed page on the Help Manual
- Moved Create Script tab to be the first visible tool
- Removed the option to lock the interface - became obsolete


Attached File  WinBuilder071_Beta8.zip   809.93KB   619 downloads



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



Beta 7 (2007-06-25)

This beta jumped from 6 to 7 because of some testing in the script engine
to ensure more stable results.

change on beta 6:

- Removed an unneeded setting which always wrote a locked=true value on the [main] section
- Recoded interface, file search/filter and settings to load much faster.
- Bugfixed error message when selecting to show log after running a project.
- Replaced external download functions with internal IE download function
- Bugfixed open handles when scanning directories


changes on beta 7:

- run command can support up to 9 parameters
- Added a code box window to test new commands under a specific project


Attached File  WinBuilder071_Beta7.zip   808.73KB   711 downloads


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


Beta 5 (2007-06-14)

- Removed property on text labels that wouldn't allow using & chars
- corrected a bug on regwrite introduced on beta 4

-- Review B

- Corrected a bug found which caused shellexecute to run without parameters, introduced on beta 4

Attached File  WinBuilder071_Beta5b.zip   805.98KB   697 downloads

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


Beta 4 (2007-06-11)

- Recoded script engine to improve performance
- Removed words !#2057 and !#2060
- Fixed Refresh button - wasn't updating correctly the Paths Tab
- FileDelete is now based on Win32API for code efficiency
- ShellExecute was improved to be (much) less CPU intensive while waiting for launched program to finish
- Added an error handler on the script engine - now it won't abort when invalid syntax is found.


Attached File  WinBuilder071_Beta4.zip   805.95KB   635 downloads

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


Beta 3 (2007-06-09)

- Scripts can be displayed without state button - useful for scripts not meant to be run (use Selected=None) on [Main] section.
- If all scripts on a folder have no state seletect (Selected = None) then the respective folder also omits any state
- Removed right-click menu from main window (became obsolete)
- Removed MD5 calculate tool from Script Edit --> Options --> Calculate MD5 checksum
- Removed language entries: !#1519,!#1520,!#1521,!#1522 related to MD5 calculate tool inside Script Edit --> Options tab.
- Added option to use wb without Download Center, Upload and Web tab for use under restricted network conditions
- Tools tab was made a bit bigger hiding the tab title
- Script Edit tab title was also hidden along with script treeview to give more room to editor
- Corrected bug which allowed to erroneously select more than one script on main window
- Corrected minimum allowed width and height for interface checkboxes
- Moved Paths and Log tab to the scripts tab
- Added a Help tab which will hold help contents about wb, it will use a html file from %basedir%\Projects\Tools\Help\index.html
- Corrected the back colors for some objects under some XP themes.
- Recoded the Create Script tab to become more functional
- Added CopyExpand command using setupapi.dll (thanks to Peter and Smiley)
- Modified ShellExecute and ShellExecuteEx to support work directories as the 4th parameter
- Modifed ShellExecute and ShellExecuteEx to work without adding parameters, ex: ShellExecute,Open,cmd.exe
- Removed "Enter" from the keyboard shortcut list (it was being trigered after exiting windows screensaver protection )
- Corrected a bug which occured when trying to echo a section with brackets


Attached File  WinBuilder071_Beta3.zip   814.16KB   599 downloads




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

Beta 2 (2007-05-19)

- Added /runsingle= switch which allows to run a single script

Attached File  WinBuilder071_Beta2.zip   798.72KB   995 downloads


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

Beta 1 (2007-05-14)

- Removed MD5 box on the options tab inside script editor (download center always checks md5 automatically)
- Added support for running projects in unnatended mode


Attached File  WinBuilder071_beta1.zip   798.34KB   699 downloads

Attached Files


Edited by Nuno Brito, 12 July 2007 - 07:57 AM.


#2 Brito

Brito

    Platinum Member

  • .script developer
  • 10616 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 14 May 2007 - 09:57 PM

As promissed to Peter and Alexei, the new beta already comes with support for unnatended project building.


Here's an example of command line syntax:

/run="%basedir%\Projects\LiveXP"
/source="C:\Documentos\SourceDir\Windows XP SP2 Português"
/target="%basedir%\Target\LiveXP2"
/ISO="%basedir%\ISO\LiveXP2.iso"
/title="My Project"
/x=10
/y=50
/log="%basedir%\log_silent.html"
/showlog
/beep

This is what I use on my case - I will write more extensive details soon.

Please add only correct values on the dir paths.

run, source, target and iso are obrigatory.


Have fun! :confused1:

#3 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 15 May 2007 - 06:34 AM

As promissed to Peter and Alexei, the new beta already comes with support for unnatended project building.


Here's an example of command line syntax:

/run="%basedir%\Projects\LiveXP"
/source="C:\Documentos\SourceDir\Windows XP SP2 Português"
/target="%basedir%\Target\LiveXP2"
/ISO="%basedir%\ISO\LiveXP2.iso"
/title="My Project"
/x=10
/y=50
/log="%basedir%\log_silent.html"
/showlog /beep

This is what I use on my case - I will write more extensive details soon.

Please add only correct values on the dir paths.

run, source, target and iso are obrigatory.


Have fun! :confused1:


:confused1:

Does it mean that I write a myWB.cmd like
Winbuilder /source=source1 /ISO=ISO1 /....

 Winbuilder /source=source2 /ISO=ISO2 /....

 ...

?

I need one additional switch (usable multiple)
/Option=<script>:<section>.<key>,"<value>"
e.g.
/Option=!Fundamentals.script&#58;Interface.pScrollBox1,&#34;B&#58;&#34;

 /Option=!Fundamentals.script&#58;Interface.pScrollBox3,&#34;RAM Drive&#34;

 /Option=RAMDisk.script&#58;Main.Selected,&#34;True&#34;

  /Option=BootSDI.script&#58;Main.Selected,&#34;False&#34;

Peter

EDIT: See post #5

Edited by psc, 15 May 2007 - 09:33 AM.


#4 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 15 May 2007 - 07:40 AM

Interesting... I have a new idea. What about batch build?
It would be the same with unattended mode but a bit more organized.
The command line should be:
Winbuilder /batch=batchfile

And the contents of batchfile should be :
&#91;BatchRun&#93;

Number=2



&#91;Run-1&#93;

run=&#34;%basedir%\Projects\LiveXP&#34; 

source=&#34;C&#58;\Documentos\SourceDir\Windows XP SP2 Português&#34; 

target=&#34;%basedir%\Target\LiveXP2&#34; 

ISO=&#34;%basedir%\ISO\LiveXP2.iso&#34; 

title=&#34;My Project&#34; 

x=10 

y=50 

log=&#34;%basedir%\log_silent.html&#34; 

showlog = true

beep = true



&#91;Run-2&#93;

run=&#34;%basedir%\Projects\NativePE&#34; 

source=&#34;C&#58;\Documentos\SourceDir\Windows XP SP2&#34; 

target=&#34;%basedir%\Target\NativePE&#34; 

ISO=&#34;%basedir%\ISO\NativePE.iso&#34; 

title=&#34;NativePE&#34; 

x=10 

y=50 

log=&#34;%basedir%\log_silent.html&#34; 

showlog = true

beep = true

What do you think?

#5 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 15 May 2007 - 09:32 AM

For first, I wrote me a program setOptions (attached) which handles the options.

Syntax:

setOptions {/|-}O[:]<script>:<section>.<key>=<value> {/|-}P[:]<Project Dir>) [{/|-}S[:]<typ>]


It can change the components:

pScrollBox
pFileBox
pTextBox
pNumberBox
pCheckBox
pRadioButton


The /P switch is only necessary if <key> does not contain a valid component name.

Sample:

setOptions "-O:!Fundamentals.script:Interface.pScrollBox3=RAM Drive" "-P:C:\Dokumente und Einstellungen\Peter\Desktop\WB Archiv\Beta8\Projects\nativeEx_barebone"


Peter

EDIT: New version handles 'Main.Selected', too:

Attached File  setOptions.zip   42.62KB   550 downloads

#6 Alexei

Alexei

    Silver Member

  • .script developer
  • 664 posts

Posted 15 May 2007 - 10:23 AM

@Nuno
First of all, it's just great :confused1:

Let's move forward :confused1:
What about having several sections, like
[download] - what to download
[settings] - what to set in scripts (input for Peter's SetOptions)
[build] - what and how to build (that's what Nuno added)
Note, the sections are very different from smiley's proposal.

:confused1:
Alexei

PS
WB connects to www.coolwebtoys.com any idea why?

#7 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 15 May 2007 - 11:44 AM

The cmd line option is great!
:confused1:
I created just a small batch file:
set BaseDir=C&#58;\Dokumente und Einstellungen\Peter\Desktop\WB Archiv\Beta8

 set setOpt=%BaseDir%\pscProgs\setOptions\setOptions.exe

 set Project=%BaseDir%\Projects\nativeEx_barebone

 set WB=%BaseDir%\WinBuilder071B1.exe

 set WBConst=/run=&#34;%Project%&#34; /source=&#34;V&#58;\BCD\cds\XPP_DE_SP2&#34; /title=&#34;My Project&#34; /x=10 /y=50  /showlog /beep

 set tg=%BaseDir%\Target\nativeEx

 set iso=%BaseDir%\ISO\nativeEx

 set log=%BaseDir%\log_silent

 

 set index=STD_R_R

 REM Standard ISO, RAMDisk

 &#34;%setOpt%&#34; &#34;-O&#58;!Fundamentals.script&#58;Interface.pScrollBox1=B&#58;&#34; &#34;-P&#58;%Project%&#34;

 &#34;%setOpt%&#34; &#34;-O&#58;!Fundamentals.script&#58;Interface.pScrollBox3=RAM Drive&#34; &#34;-P&#58;%Project%&#34;

 &#34;%setOpt%&#34; &#34;-O&#58;RAMDisk.script&#58;Main.Selected=True&#34; &#34;-P&#58;%Project%&#34;

 &#34;%setOpt%&#34; &#34;-O&#58;CreateISO.script&#58;Main.Selected=True&#34; &#34;-P&#58;%Project%&#34;

 &#34;%setOpt%&#34; &#34;-O&#58;BootSDI.script&#58;Main.Selected=False&#34; &#34;-P&#58;%Project%&#34;

 &#34;%WB%&#34; %WBConst% /target=&#34;%tg%%index%&#34; /ISO=&#34;%iso%%index%.iso&#34; /log=&#34;%log%%index%.html&#34;

 

 set index=SDI_R_R

 REM BootSDI, RAMDisk, SettingsDrive = RAM Drive

 &#34;%setOpt%&#34; &#34;-O&#58;!Fundamentals.script&#58;Interface.pScrollBox3=RAM Drive&#34; &#34;-P&#58;%Project%&#34;

 &#34;%setOpt%&#34; &#34;-O&#58;CreateISO.script&#58;Main.Selected=False&#34; &#34;-P&#58;%Project%&#34;

 &#34;%setOpt%&#34; &#34;-O&#58;BootSDI.script&#58;Main.Selected=True&#34; &#34;-P&#58;%Project%&#34;

 &#34;%WB%&#34; %WBConst% /target=&#34;%tg%%index%&#34; /ISO=&#34;%iso%%index%.iso&#34; /log=&#34;%log%%index%.html&#34;

 

 

 set index=SDI_R_S

 REM BootSDI, RAMDisk, SettingsDrive = System Drive

 &#34;%setOpt%&#34; &#34;-O&#58;!Fundamentals.script&#58;Interface.pScrollBox3=System Drive&#34; &#34;-P&#58;%Project%&#34;

 &#34;%WB%&#34; %WBConst% /target=&#34;%tg%%index%&#34; /ISO=&#34;%iso%%index%.iso&#34; /log=&#34;%log%%index%.html&#34;

 

 set index=SDI_N_N

 REM BootSDI, no RAMDisk

 &#34;%setOpt%&#34; &#34;-O&#58;!Fundamentals.script&#58;Interface.pScrollBox1=--&#34; &#34;-P&#58;%Project%&#34;

 &#34;%setOpt%&#34; &#34;-O&#58;RAMDisk.script&#58;Main.Selected=False&#34; &#34;-P&#58;%Project%&#34;

 &#34;%WB%&#34; %WBConst% /target=&#34;%tg%%index%&#34; /ISO=&#34;%iso%%index%.iso&#34; /log=&#34;%log%%index%.html&#34;
, and I got:
  • persistent ISO
  • persistent Target directory
  • persistent log file
for
  • Standard ISO
  • BootSDI ISO with RAM disk and settings on RAM disk
  • BootSDI ISO with RAM disk and settings on system disk
  • BootSDI ISO without RAM disk.
Next I'm going to write 'parent' batches for
  • OS
  • language
Then I have everything I wanted to have in my primary suggestion to do 'universal' tests.

Thanks, Nuno :confused1:

Peter

#8 Brito

Brito

    Platinum Member

  • .script developer
  • 10616 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 15 May 2007 - 04:37 PM

Sorry for the short description of syntax - I've been a bit short in time and was just online long enough to upload the beta.

Still missing to add errorlevels for winbuilder.exe whenever errors are outputed while running a project.

By default there is only support for english language (faster) - but I can add normal language translation if needed.


It is possible to add a list of locations (projects) like the one specified on a /run=

Alexei, what do you mean by a [download] section? Is it something like the download center where it would download based on a selected download profile/webserver?

coolwebtoys is the service that provides the chat box - you can click on the chat link on the top of this page to view the chat window straight from their site.

We could also host our own chat, but it's wiser this way to have an alternative external way to comunicate on those times when boot-land.net gets offline for some reason.


Smiley - will try to add an answer file similar to the one you've proposed.. :confused1:

#9 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 15 May 2007 - 04:47 PM

Smiley - will try to add an answer file similar to the one you've proposed.. :confused1:

If you have a look here, everything can be done by a small batch.
It is not necessary to extend WinBuilder to a development IDE.

Peter

BTW: The only thing I'm missing is the ability to have a /runsingle.
If we have it, I can load different constellations by WBManager and then create the ISO with this constellation.
Of course it is already possible with my script, but that takes a long tome to write all the 'setOptions' statements.

#10 Brito

Brito

    Platinum Member

  • .script developer
  • 10616 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 15 May 2007 - 06:17 PM

/runsingle would also have to specify a /run= switch so that it could run script.project [variables] and [process] sections, otherwise it would output different results from the main window..

:confused1:

#11 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 15 May 2007 - 06:26 PM

/runsingle would also have to specify a /run= switch so that it could run script.project [variables] and [process] sections, otherwise it would output different results from the main window..

:confused1:


Of course. :confused1:
I thought that in addition to the 'Standard' switch set a /runsingle should cause something like the 'click the green play triangle' inside the open script, rather than to play the whole project.
(If different, also for my purposes it propably would not work)

Peter

#12 euhenio

euhenio

    Frequent Member

  • .script developer
  • 143 posts
  • Location:Minsk

Posted 16 May 2007 - 01:11 AM

/run= switch so that it could run script.project [variables] and [process] sections


now needed command for exiting Winbuilder

#13 Alexei

Alexei

    Silver Member

  • .script developer
  • 664 posts

Posted 16 May 2007 - 01:23 AM

Alexei, what do you mean by a [download] section? Is it something like the download center where it would download based on a selected download profile/webserver?

Yes, I meant automatic invocation of download center (with specified parameters).
:confused1:
Alexei

#14 Ove

Ove

    .script developer

  • .script developer
  • 192 posts
  • Location:Fagaras, Romania
  •  
    Romania

Posted 17 May 2007 - 06:35 AM

I have downloaded this beta, and it gives me an error that "you need to be connected to the internet to download these files".
Maybe the ping isn't working properly, or the computer I'm using connects trough a proxy or something (I don't know what influence that might have)

The thing is I can use any browser to download and view pages, even WinBuilder's internal browser.
So I think I should be able to use WinBuilder to download files from the internet (scripts)

#15 Brito

Brito

    Platinum Member

  • .script developer
  • 10616 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 17 May 2007 - 08:49 AM

Hi Ove!

We've been discussing this for some time since the last beta topic (069) - proxy support is very limited and you can try to add your account configuration on the download center - press the "Options" and fill your proxy details to see how it works.

Please let me know if you are indeed using a proxy and if this is your case I would like to know what protocol it is using (direct http, SOCKS, etc..) if possible..

Thanks! :confused1:

#16 Ove

Ove

    .script developer

  • .script developer
  • 192 posts
  • Location:Fagaras, Romania
  •  
    Romania

Posted 18 May 2007 - 08:29 AM

Hi Ove!

We've been discussing this for some time since the last beta topic (069) - proxy support is very limited and you can try to add your account configuration on the download center - press the "Options" and fill your proxy details to see how it works.

Please let me know if you are indeed using a proxy and if this is your case I would like to know what protocol it is using (direct http, SOCKS, etc..) if possible..

Thanks! :confused1:


I'm sorry I can't do that. I don't have internet at home and the computer that WinBuilder didn't want to download was a computer at school. I don't know the proxy for that computer so I can't post it.
Isn't there a way of making it work the same way that IE downloads files? IE works, Firefox works, Opera works, but WinBuilder doesn't

#17 Brito

Brito

    Platinum Member

  • .script developer
  • 10616 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 18 May 2007 - 10:32 AM

Yes, there is a way to add try to copy the values from IE - I will try to implement it.. :confused1:

#18 Brito

Brito

    Platinum Member

  • .script developer
  • 10616 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 19 May 2007 - 01:02 PM

A new beta was uploaded, this time the changes were only done on the command line switches allowing to simply run a single script instead of the whole project.

:confused1:

#19 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4198 posts

Posted 28 May 2007 - 08:33 PM

Suggestion.
When download scripts for project if there is an error message of failed download or something of that nature can there be added a place where it will place that message so that we can post it in the authors thread so that he can know the error or error when trying to download a project.

If you download only one project. For this example NativePE for testing.
You download no other project because you deselected it. When the downloading is finished.
No project shows up.

#20 Alexei

Alexei

    Silver Member

  • .script developer
  • 664 posts

Posted 29 May 2007 - 07:11 AM

Suggestion.
When download scripts for project if there is an error message of failed download or something of that nature can there be added a place where it will place that message so that we can post it in the authors thread so that he can know the error or error when trying to download a project.

If you download only one project. For this example NativePE for testing.
You download no other project because you deselected it. When the downloading is finished.
No project shows up.

Good idea :confused1:
However, why limit log to downloads? It may be useful if WB would be able to log whole "session" (in a separate log file).
Something like:
- WB started <date time>
- WB parameters <parameters>
- Download <name> <date time>
- download successful <bytes> <date time>
- Build paroject <name> <date time>
- Build ended <number of errors> <number of warnings> <date time>
- WB ended <date time>
It should be WB setting that defines log level (from "No" to "Complete").
:confused1:
Alexei

#21 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 30 May 2007 - 10:26 AM

A new beta was uploaded, this time the changes were only done on the command line switches allowing to simply run a single script instead of the whole project.

:confused1:

@Nuno
You seem to be back. I hope with the health of your wife is everything ok again.

Can you please give a sample how to run a single script?
I tried a lot of syntax combinations, but all of them w/o success :confused1:

What I finally want to do in a batch:
  • Change the configuration name (pScrollBox1) in WBManager (I can do by setOptions)
  • Run WBManager[Restore-Set] to load the new configuration (I cannot do)
  • Run the complete project to make a new ISO (I can do)
Peter

#22 Brito

Brito

    Platinum Member

  • .script developer
  • 10616 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 31 May 2007 - 09:47 AM

:confused1: !

Sorry Peter - thanks for pointing this gap, guess it's been a bit harder to focus lately and I've forgot to mention the syntax which is simple but should still be explained.

You can use the same command line you use to run the project as before, but you should add /runsingle=myDemo.script

Where myDemo.script represents the script and relative path counting from the project folder.

Using as example qemu you should add /runsingle=Finish\qEmu.Script

Hope you find this syntax logic to use - there's still some code needed to optimize. When only a single script is ran it is not needed to scan the projects folder and classify all found scripts, next betas should be "smarter" and just run the specified script making start-up much faster.

:confused1:


ps: Alexei, I will try to work on the log later, your idea is good! :confused1:

#23 Brito

Brito

    Platinum Member

  • .script developer
  • 10616 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 09 June 2007 - 11:56 AM

A new beta was uploaded and is available for download on the first post.. :thumbup:

Here's the detailed log of changes:

- Scripts can be displayed without state button - useful for scripts not meant to be run (use Selected=None) on [Main] section.
- If all scripts on a folder have no state seletect (Selected = None) then the respective folder also omits any state
- Removed right-click menu from main window (became obsolete)
- Removed MD5 calculate tool from Script Edit --> Options --> Calculate MD5 checksum
- Removed language entries: !#1519,!#1520,!#1521,!#1522 related to MD5 calculate tool inside Script Edit --> Options tab.
- Added option to use wb without Download Center, Upload and Web tab for use under restricted network conditions
- Tools tab was made a bit bigger hiding the tab title
- Script Edit tab title was also hidden along with script treeview to give more room to editor
- Corrected bug which allowed to erroneously select more than one script on main window
- Corrected minimum allowed width and height for interface checkboxes
- Moved Paths and Log tab to the scripts tab
- Added a Help tab which will hold help contents about wb, it will use a html file from %basedir%\Projects\Tools\Help\index.html
- Corrected the back colors for some objects under some XP themes.
- Recoded the Create Script tab to become more functional
- Added CopyExpand command using setupapi.dll (thanks to Peter and Smiley)
- Modified ShellExecute and ShellExecuteEx to support work directories as the 4th parameter
- Modifed ShellExecute and ShellExecuteEx to work without adding parameters, ex: ShellExecute,Open,cmd.exe
- Removed "Enter" from the keyboard shortcut list (it was being trigered after exiting windows screensaver protection )
- Corrected a bug which occured when trying to echo a section with brackets




A lot of bugfixes and changes were made on this beta - most of them regarding some visual aspects so I will try to explain them the best I can in a resumed way.

- Scripts can be listed on the main window without having a enable or disable state. As mentioned on the log of changes, all you need to do is using the Selected = None value to remove the script checkbox. I thought this would be particulary usefull for those tools which aren't meant to be run but are handy to be listed. If all scripts on a folder have no state, then the folder itself won't have a state checkbox.

- Right click from main window was removed because it wasn't used anymore - the same applies for the enter key which caused some buggy behavior when the computer left the screensaver.

- Removed MD5 single check from the script editor tab because it was also a bit redundant and not a very usefull feature.

- Added CopyOrExpand command by request of Smiley and help from Peter, hope this new function can help extracting those cabbed files since it seems much faster that the current expand command which is based on extract.exe



- wb can now work separated from network connectivity - you can select to use or not the download center, ftp upload and web tabs. This was requested to allow wb work better under x64 OS's and machines with heavy security policies.

- Proxy support was removed, I am working on direct integration with IE but there is still some coding left to learn before it can completely replace the present download components. When it's finished it should work without need to configure any proxies at all.

- Paths and Log tabs are now next to the script itself. This seems a more logical organization and had been requested some time ago, I finally managed to find a simple solution wich seems to fit nice enough in a smaller space.

- A few bugfixes were done on the script engine and shellexecute can also select which folder it will use as work dir.


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

New tools:

Important to say that a builtin help system is being implemented inside wb. It is going to be based on html pages to ensure that anyone can edit or add new pages, and it's placed under the tools folder to ensure that the download center can update it immediatelly by script developers with acess to the update servers.

You can test it on this beta, all that is required to do:

- Create a folder called Help under the Tools folder
- Place an html file named as: "index.html"

If this file is detected when wb starts up then a new tab called "Help" will appear and load this index.html page. This way I hope that this system can grow with the help of everyone and progressively contain syntax information and informations as needed.

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

Create Script

The former create script tool was removed and is progressively being replaced with a more flexible way to create scripts.

Current features include the hability to browse and add code snippets onto the script that is being created. I've followed a similar method used by the help system, so a new folder is also placed inside the Tools folder.

As in the example before you can test it right away:

- Create a folder called "Templates" under "Projects\Tools" folder
- Place any .script or .txt files meant to be used as code snippet examples.

This template folders also supports subfolders to allow categories to be used, once you want to add a script just click on the arrow button to include it's contents on the new script.

I've also been testing MakeScript by Pedrole15 and started adding direct support for this program so that it can work along with this new tool.
Besides browsing text and script files, you can also include exe files wich will be executed when the user clicks on them.

When running an application from "Templates" two parameters will be added. The first parameter is the complete path of %basedir%, the second path is the location and file name of the script to be created.

Example:

myApp.exe c:\winbuilder c:\winbuilder\Projects\LiveXP\Apps\myNew.script


Exe files are only executed when the user adds a valid filename and location (a warning message is displayed when this information is not complete)

After the application is closed, the new script file is read from disk and it's content is displayed on the source code window for aditional changes (if required)

This is still the preliminary version - my intention is to also add a tab for attaching files and also add this template tab on the source code editor to ease posterior codings.

Another good feature would be the hability to actually merge equal sections and settings, but this might take some more time to get done.

Last but not least, html pages can also be included on this template folder and they are displayed on the description box - this can be a good resource for creating interactive pages to create scripts where the user can write customized settings or view additional informations.


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

Sorry for introducing so many different things since last beta, a lot of work still has to be done, but I hope you like the changes so far.. :1st:

#24 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 09 June 2007 - 12:08 PM

4 first issues with beta 3:

CopyExpand,%SourceDir%\I386\ACPI.DLL,%TargetDir%\i386\system32
brings error:

FileCopy - Failed to copy [V:\BCD\cds\XPP_DE_SP2\I386\ACPI.SYSC:\Dokumente#$sund#$sEinstellungen\Peter\Desktop\WB#$sArchiv\Beta8\Target\nativeEx\i386\system32\drivers] to: [\]

Systax problem of me?

Do
  • Start project build
  • Click Download tab
  • Download single file
  • Watch what happens
Do
  • Start project build
  • Choose single script
  • Click 'Edit'
  • Watch what happens
Do
  • Choose singel project
  • Click the green 'run' arrow
  • Watch what happens
To complete my remarks with some good news: I like the new designs of tabs, missing tree in edit etc. (inspite it will need some time to become familar)

Peter

#25 Brito

Brito

    Platinum Member

  • .script developer
  • 10616 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 09 June 2007 - 12:38 PM

Downloaded nativeEx to test your results properly and was surprised to see that your server under the minimum download level is less than 1Mb in size - Excellent!! :thumbup: (I'm a happy dialup user..)

Only one detail: script.project from nativeEx also needs to get adjusted the download level set to minimum.

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

Tested the latest nativeEx and no errors were outputed, have a look on my log at the bottom.

Haven't managed to reproduce.. :1st:

Will also look on the issue you've reported - thanks for the very quick testing! :thumbup:

Attached Files

  • Attached File  log.7z   80.04KB   395 downloads





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users