API functions inside WB's Magic Wand

Hey,
I think it is time to include the command require_file, in the new api.

I think it is time to include the command require_file, in the new api.

Seeee me confuuuused!

I think that we have it since Ice-Age!

Peter

@fxscrpt:

Maybe I misunderstood the last posts, including your intention.

If yes, can you explain again for a fool?

Maybe I misunderstood the last posts, including your intention.

If yes, can you explain again for a fool?

wrong phrases in a rush. I misunderstood myself. Freudic confusion.
I was to mean that I wanted to say that.... require_file be included in magic wand ... and you are right it is found in api from the times of old testament. I Shake my brain to turn it on...

Hmm.. this a feature discussion that probably deserved a topic of it's own to allow exploring all possibilities.

Hope you don't mind that I split this from the original topic to it's own topic.

-----------

Regarding your idea, I also agree that the most common api commands should be available to the developer with the same ease as the "raw" commands.

Please suggest all the API commands that should be listed, thank you!

Hmm.. this a feature discussion that probably deserved a topic of it's own to allow exploring all possibilities.

Hope you don't mind that I split this from the original topic to it's own topic.

-----------

Regarding your idea, I also agree that the most common api commands should be available to the developer with the same ease as the "raw" commands.

Please suggest all the API commands that should be listed, thank you!

It is difficult to implement.

Either there can be a hardcoded list inside WB. But whenever something changes, that demands a new WinBuilder.exe
Or WB could look into project.script. But that demands the API shortcut to be 'findable'. They cannot be find if they are anywhere inside the [Variables] section. Therefore they should be in a specific [API] or [?????] section.

This would demand a bigger rebuild in WB [exe] internals.

Peter

It is difficult to implement.

Either there can be a hardcoded list inside WB. But whenever something changes, that demands a new WinBuilder.exe
Or WB could look into project.script. But that demands the API shortcut to be 'findable'. They cannot be find if they are anywhere inside the [Variables] section. Therefore they should be in a specific [API] or [?????] section.

This would demand a bigger rebuild in WB [exe] internals.

Peter

Peter,
Make the command AddVariables the possibility to set variable Global (like the Set command)
In Api I add a section [ApiVar] which contain all api command

In Script.project delete all api command from section [Variables]
and add in section [Process] in Script.project

[Process] 

AddVariables,%API%,ApiVar,GLOBAL

In api.script

[ApiVar]

Add_Shortcut=Run,%API%,AddShortcut

Require_File=run,%API%,Expand_file

Unpack=Run,%API%,Depack

_Calculate=run,%API%,Calculate

Then all api command can be found directly in the api
When updating api no need to update script.project

I don't know if this can be possible and if help you

Pedro

Peter,
Make the command AddVariables the possibility to set variable Global (like the Set command)
In Api I add a section [ApiVar] which contain all api command

In Script.project delete all api command from section [Variables]
and add in section [Process] in Script.project

[Process] 

 AddVariables,%API%,ApiVar,GLOBAL

In api.script

[ApiVar]

 Add_Shortcut=Run,%API%,AddShortcut

 Require_File=run,%API%,Expand_file

 Unpack=Run,%API%,Depack

 _Calculate=run,%API%,Calculate

Then all api command can be found directly in the api
When updating api no need to update script.project

I don't know if this can be possible and if help you

Pedro

A very good idea!

Peter

Peter,
Make the command AddVariables the possibility to set variable Global (like the Set command)
In Api I add a section [ApiVar] which contain all api command

In Script.project delete all api command from section [Variables]
and add in section [Process] in Script.project

[Process] 

   AddVariables,%API%,ApiVar,GLOBAL

In api.script

[ApiVar]

   Add_Shortcut=Run,%API%,AddShortcut

   Require_File=run,%API%,Expand_file

   Unpack=Run,%API%,Depack

   _Calculate=run,%API%,Calculate

Then all api command can be found directly in the api
When updating api no need to update script.project

I don't know if this can be possible and if help you

Pedro

I realized it.

Will be available next beta (or inofficially beta 6 a)

Please be sure to use PERMANENT rather than GLOBAL.
from release notes:

****************
added - GLOBAL and PERMANENT options to AddVariables command

AddVariables,%ScriptFile%,section,GLOBAL: Additional new variables list will be defined in all subsequent scripts of the current build.

AddVariables,%ScriptFile%,section,PERMANENT: Additional new variables list will be defined in all subsequent scripts of the current build.
- Additionally all added variables are written into script.project and therefore valid for all subsequent builds.

With GLOBAL the definitions are valid for a complete build, but not when running a single script.

Peter

Great Peter
I will test but my idea is not to use the PERMANENT definition or why changing as it is now

I search a simply way for having a quick find of all api function and syntax

[Api_Command]

   Add_Shortcut=Run,%API%,AddShortcut

   Require_File=run,%API%,Expand_file

   Unpack=Run,%API%,Depack

   _Calculate=run,%API%,Calculate



[Api_Syntax]

   Add_Shortcut,<Type>,<Folder>,<FullFileName>,<Title>,<Work Folder>,<Parameters>,<IconFile>,<StartMode>,<ToolTip>

   Require_File , <Folder\> filename , <Source> , <Target>

   Unpack,<Folder>,<Archive>,<Option>,<%Target_Prog%>,<%ProgramFolder%>,<%programExe%>,<Target_Temp>

   _Calculate,expression,Variable

So with api formatted like this you can make WB easy to list all api function (without knowing them and only for the current project) and their respective Syntax in Api_Syntax section
Hope you understand what I mean

Pedro

Great Peter
I will test but my idea is not to use the PERMANENT definition or why changing as it is now

I search a simply way for having a quick find of all api function and syntax

[Api_Command]

	Add_Shortcut=Run,%API%,AddShortcut

	Require_File=run,%API%,Expand_file

	Unpack=Run,%API%,Depack

	_Calculate=run,%API%,Calculate

 

 [Api_Syntax]

	Add_Shortcut,<Type>,<Folder>,<FullFileName>,<Title>,<Work Folder>,<Parameters>,<IconFile>,<StartMode>,<ToolTip>

	Require_File , <Folder\> filename , <Source> , <Target>

	Unpack,<Folder>,<Archive>,<Option>,<%Target_Prog%>,<%ProgramFolder%>,<%programExe%>,<Target_Temp>

	_Calculate,expression,Variable

So with api formatted like this you can make WB easy to list all api function (without knowing them and only for the current project) and their respective Syntax in Api_Syntax section
Hope you understand what I mean

Pedro

API is your playground
And you mean that WB is mine and I can now add to the magic wand !?

I'll see what I can do

Peter

API is your playground
And you mean that WB is mine and I can now add to the magic wand !?

I'll see what I can do

Peter

Yes
Simply tell me how to format the section Api_Syntax

Pedro

Yes
Simply tell me how to format the section Api_Syntax

Pedro

Tomorrow.

I have to go now for 'Nuhr die Wahrheit' (you know the famous German artist?)

Peter

It's very enjoyable to read the conversation between two great minds and you took away any possible argument I could think of. Your joint solution is simply great to support future changes in the code!

Thank you Nuno

@Peter

With GLOBAL the definitions are valid for a complete build, but not when running a single script.

I have tested and it work with GLOBAL even when running a single script.

Pedro

Thank you Nuno

@Peter
I have tested and it work with GLOBAL even when running a single script.

Pedro

Not for a test in CodeBox!
In CodeBox as first line there is necessary:

AddVariables,%API%,ApiVar,GLOBAL

Peter

With GLOBAL the definitions are valid for a complete build, but not when running a single script.

Is it possible that on individual script run, script.project will also be run prior, so that

[Process]

AddVariables,%API%,ApiVar,GLOBAL

is run to initiate the api commands?

Regards,
Galapo.

I have the feeling that this (running script.project when individual script runs) might cause new trouble with the onbuildexit stuff and some other vodoo tricks i implemented...

I recommend caution when trying to add such functionality...

I have the feeling that this (running script.project when individual script runs) might cause new trouble with the onbuildexit stuff and some other vodoo tricks i implemented...

Yes, I had the same thought just after I posted.

I have the feeling that this (running script.project when individual script runs) might cause new trouble with the onbuildexit stuff and some other vodoo tricks i implemented...

I recommend caution when trying to add such functionality...

I agree to ctmag!

Peter

Suggestion: WB should know whether it is the big play button which has been pressed, or whether it is an individual script button which has been pressed. Therefore, there could be two new 'System' commands reflective of this: 'System,INDIVIDUAL' and 'System,PROJECT' (or some other name along these lines. Then in script.project we could have:

[Process]

If,System,INDIVIDUAL,Equal,True,AddVariables,%API%,ApiVar,GLOBAL

If,System,PROJECT,Equal,True,Begin

  System,ONBUILDEXIT,Exec,%api%,LiveXP-ONBUILDEXIT

End

Then we could have script.project run before an individual script run without consequence.

Regards,
Galapo.

???

The idea is good, but if used like in your example it would me every single script needs to be changed...or am i getting something wrong here?

???

The idea is good, but if used like in your example it would me every single script needs to be changed...or am i getting something wrong here?

No, that would be in script.project only!

But I emotionally do not like the idea, I cannot yet explain clearly why.

Peter

i hava somewhat the same felling.-)

But what i would like is a function (for use in scripts) to do some things when run by green triangle.

On the other hand i think a lot of this could also be done by improving the script code with already existing commands...

But I emotionally do not like the idea, I cannot yet explain clearly why.

don't like an idea emotionally?!?

Peter is getting latin!

don't like an idea emotionally?!?

Peter is getting latin!

Maybe I have had the feeling that this is hurting your 'Fundamental Intentions'

Hold things easy and straight on

..
But nevertheless:

I have finished a working concept where the magic wand:

• Everytimes presents the actual project's API functions (or none if there is no API in the actual project)
• Works also if a project is not yet built.

You now can see a menu:


To bring to work, in Script.project in the variables section I added

%APIDEF%=API

And in Api.Script I included:

[API]

	   _Calculate="_Calculate,[expression],[Variable (whithout %)]"

	   _FileCopy="_FileCopy,[Source],[Target]"

	   Add_Asso="Add_Asso,[Ext],[Type],[Title],[Filename],[Option],[True for RegAddBoot]"

	   Ask_License="Ask_License,Filename,ID,Section"

	   Associate_file="Associate_file,[Ext],[Type],[Filename],[Option],[True for RegAddBoot]"

	   CopyProgram="CopyProgram,[%FileBox_Source%],[%Target_Prog%\%ProgramFolder%],[%ProgramExe%],[Archive to delete]"

	   QuickScript="QuickScript,RunFromRam,Section_or_7z_file,Add_Shortcut"

	   RegAddBoot="RegAddBoot,RootKey,ValueType,Key,ValueName,Value"

	   Require_File="Require_File,[Folder\]filename,[Source (if  source  is different of %Source_Sys%)],[Target ( If target is different of  %Target_Sys%)]"

	   Require_Version="Require_Version,Filename,Version,Section"

	   Unpack="Unpack,[Folder],[Archive],[Option],[%Target_Prog%],[%ProgramFolder%],[%programExe%],[Target_Temp]"

And of course -not visible here- it inserts the code into the CodeBox or current script resp.

This new API section is a 'quick and dirty write down' and only something for test.
It does not claim to be complete, 'nice' or logically correct.

Pedrole#15 and the forum should correct it.

For all the crazy people who want to have it just before it becomes public:

You can get it here
But be careful: The version shows an 'API'. Do it really use ONLY FOR API tests.

The internal variable structure has been significantly changed. And I did not test for standards.

Peter