Topic: Request: PEBakery Batch  (Read 185 times)

0 Members and 1 Guest are viewing this topic.

Request: PEBakery Batch
« on: December 24, 2017, 05:55:42 AM »

Lancelot

  • Moderator, Gena Baker
  • Grand Chef
  • *****
  • Date Registered: Sep 2010
  • Posts: 7758
Following roots of comma separator batches,
I like PEBakery support individual batch files like .BakerBatch , .BakerCMD

With installed PEBakery to C:\Program Files\Bakery\Launcher.exe
with associations already made...

when one double click blabla.BakerBatch
PEBakery opens like a Level=10 Selected=None plugin under "BakerBatch" on left tree.
-->
unlike cmd do not autoexecute [process], to avoid AV adding PEBakery malicious, dangerous software etc.

*
since  .BakerBatch is standalone batch file, no need such file under a project folder where we will use Baker plugins .BakerPlugin


ps:
.BakerBatch
.BakerPlugin

are only given to write the idea now.

.BakerPlugin -> after the point we totally left wb where we can also change syntax like NoRec

Further:
It will also be a simpler platform to test new syntax much much later when new syntax becomes under construction.
ex:
.BakerScript
or whatever....

Edit:
ps:
Since these are new extensions for PEBakery, All can support auto utf enabled.

Edit:
Naturally no %sourcedir% etc as default
same with
[Main]
PathSetting=False



Related topic:
http://theoven.org/index.php?topic=2326

***
*
Yes things missed from my eyes...

so, instead of folder support,
only file support with wildcard can solve syntax adjustments?
System,LoadFile,<Folder>\*.script,[NoRec]
no need hardcode .script . Flexibility good.

So In future we can have
System,LoadFile,%ProjectDir%\Folder\*.script
System,LoadFile,%ProjectDir%\Folder\*.blabla

I feel we will need such things with utf plugins.... (much later)

-->
*
Why do we need a special load command for "LoadALL" when this could be easily done with just a single parameter containing a directory path?
I guess idea is flexibility for future expansions.
Current PEBakery follow wb, in future there will no need to without any .script or script.project


***
*
In case of renaming NOREC flag, then every commands have NOREC should be changed at the same time.

Too early for now.
The day we depreciate wb with different extension than I am fine to update all relevant plugins.

Only possible for new syntax with current transfer period.
ps:
Maybe you can use a different name than NoRec on new syntax of PEBakery if it is easy to implement ?
ex: NoRecursive , NoSubFolder
If it sounds better to you following the idea of human-readable syntax. (people mostly complain time to time)

Or we can do that after new extension..... (ex: .BakerPlugin .BakerBatch .BakerScript )

:turtle:


***
some part of Reply 1 , read rest
http://theoven.org/index.php?topic=2082.msg23158#msg23158

*
First of all, winbuilder is a batch engine, not a script engine.
It is like cmd.exe ---> blabla.cmd

name changed to "winbuilder" to catch "popularity" on internet, that is all.


*
Do not worry about license,
 comma based script or batch was popular at old times ,
 See AutoIT v2 help file
  https://www.autoitscript.com/site/autoit/autoit-v2/

 and winbuilder developers re write manythings in pascal to avoid license issues,
  you write on another languages so you avoid too.  :wink: :thumbsup:

*
Think current projects that way :
 Evolution:
 You are creating a project with lots of .cmd files
 -> Than you think it will be better to give GUI for some options (old pebuilder users had such demand)
 --> With GUI You can have internal editor
 --> With GUI You can have download option
 -----> ..... evolution  :wink:
« Last Edit: December 25, 2017, 04:38:06 AM by Lancelot »

Re: Request: PEBakery Batch
« Reply #1 on: December 25, 2017, 04:38:47 AM »

Lancelot

  • Moderator, Gena Baker
  • Grand Chef
  • *****
  • Date Registered: Sep 2010
  • Posts: 7758
Just came to my mind, Added to first post:

Edit:
Naturally no %sourcedir% etc as default
same with
[Main]
PathSetting=False

:turtle:

 

Powered by EzPortal