9 replies to this topic

[Chefkeks]

Hi all,

I have a lot of scripts I share. It's working great, but sharing could be a bit improved in the following way:

At the moment nearly every second folder is named shared_custom because of my shared scripts. So beside the standard folders (apps, finalize, etc.) there is almost the same structure in a lot of subfolders with parent folders that are all named shared_custom. So my suggestion is to improve the script sharing with an option (if possible?) to show shared scripts, that are located in a folder with the same name as a standard folder, e.g. components, to the standard folder (components), so that there are not all of those (parent) folders named shared_custom.

Thanks in advance

Chefkeks

[ChrisR]

Hi Chefkeks,

This script was created so, to be as secure as possible .
Only scripts "Apps" can be shared with other projects Gena, VistaPE CAPI or your collection of script. And not with components, tweaks, .....

The folder name Shared_Custom, Shared_Gena, Shared_VistaPE-CAPI, Shared_MyScripts or Shared_Custom allows to see the shared scripts with the structure you want, and to remove links easyly .
Put files link in the same project folder would be confusing with others script.
Except for which Gena_Appetizer and Gena_Sweets (AddOn) which is designed for .


Over, the selection of files links are built with :

[Main]

link=Projects\Gena\Apps\Tasks File\Compression\WinRAR.script

Selected=False

To share easily and to avoid to enable or disable a script from an another project (Selected=False or True is in the link files and not in the original script).


A big thanks to the authors Blue Life and Lancelot
I'm just in addition and for customize the script for Win7PE SE.

[Chefkeks]

First thanks, I now understand the linking process even better.

I never noticed the Shard_Custom folder in the Win7PE_SE project folder on the hard disk with all the .Link files. There it has a nice structure and it's easy to remove single links etc. What I was talking about is that in winbuilder the structure of the folders is kinda messed up with all the shared_custom folders (one for each download level that contains a shared script) and I was thinking it might be possible to show only one apps (tweaks, etc.) folder in winbuilder instead of two (one folder named apps, the standard apps folder, and one folder name Shared_custom with the subfolder apps).

I know to avoid errors when there would be only one folder with both scripts displayed in winbuilder there must be some error checking routine or an option which script should be preferred (the one in apps or the one in the shared apps) if the have the same name. I'm not so deep into programming, but I guess this should be possible But if this is not possible or not wanted due to security reasons etc. I can live with the current solution - better than no script sharing

[sbaeder]

First thanks, I now understand the linking process even better.

This is a good thing (to learn ), and I also hope you better understand the process WB uses to display (and process) scripts. It is a combination of naming of the scripts/folders AND the processing "level" that are used to define the order to process scripts. Link files are just another way to share the "content" of a script while keeping it's selection flag localized. Actually, an interesting and powerful construct!

But as you mentioned, the current sharing script has some design decisions that maybe weren't clear before including security, ease of use when linking to a FULL project (like GENA, or VistaPE, etc.), ease of deleting the link folder, etc. All of these make a certain amount of sense...BUT, they may not fit you exactly - which is the beauty of all these projects and an open scripting language.

You certainly could make your own "sharing" script that creates link files for other than the apps folder. Or even take the opposite approach, and create your own top level project that "shared" into it the core Win7PE_SE project scripts/files. The possibilities are only limited by your imagination and ability...

For example, I also have a few other scripts I want to "include". While it does make it a bit more confusing in the WB tree structured view of the project, I just decided that in MY "apps folder", I would create the following structure

apps/apps

apps/tweaks

apps/finalize

etc...

I even put things into the top level "apps" that just show up in the Shared_custom directly...This makes it easy for me to de-select all the standard "apps" and instead select all of mine (as well as my tweaks, etc.) yes, the "shared_custom" folder shows up multiple times - BUT that is OK (or at least easy to deal with )

[Chefkeks]

Oh yes, to learn is definitely is a good thing and I am still young - so I have many things to learn and I'm absolutely willing to learn (and to forget a bit as well )

I will have a closer look and may create my own sharing script, reorganize my folders, etc. to find the best working solution for me. I changed so many scripts from different projects to build and manage my PE's easier in past, so I will find a way in the future once again It's always fun and sometimes the results are some scripts that others help/like too and worth to be shared here and may included into the standard apps of a project (:

[pscEx]

Maybe you try the nativeEx_multiPE share mechanism: http://nativeex.exec...ore_Apps.Script
This makes the folder names a bit more understandable:
 appimports.gif   35.92KB   24 downloads
See in the left the "External" (from BartPE plugins) and the "Win7PE_SE" entries under "AppImports"

Peter

EDIT: Sorry, wrong link to the script given. Corrected.

[Chefkeks]

Thanks I will have a look tomorrow

By the way I wanted to say "Thank you" for WBManager and myOptions. I extended and modified the script files a "long" time ago (I guess it was in October 2010 or around that time) to fit my needs and use them til that time to manage my different configurations, e.g. minimal build, standard build, build with specific laptop drivers, ... and I am always happy of easily switching my pe config (:

[sbaeder]

Maybe you try the nativeEx_multiPE share mechanism: http://nativeex.exec...ore_Apps.Script
This makes the folder names a bit more understandable:
 appimports.gif   35.92KB   24 downloads
See in the left the "External" (from BartPE plugins) and the "Win7PE_SE" entries under "AppImports"

Peter

Yes, and it a bit more "flexible", but in general, doesn't solve the organization issues if you have scripts you want to "share" at more than the Apps level (level=5)...What about driver scripts? Or special scripts that need to run at the finalize phase? For those, you would still see the "AppImport" pseudo-folder representation more than one time.

While not perfect, if you understand the compromise between organization and sequencing, it is certainly manageable...

Thanks for yet another example!

Scott

[ChrisR]

Chefkeks,

Following your (good) request to share scripts other than purely Apps and integrate into the existing structure. My friend Lancelot, improved the script by adding "MyScripts Advanced" .

This option is for Advanced users. It creates Links with exact organisation of ProjectDir\MyScripts.
To use with caution (No Protection to prevent things if exists), End User Responsible...

As the other options, select/unselect do not affect the original script.

I think that meet completely your need (and those who want same thing).

Happy Testing


 Share Scripts W7PE.7z   339.49KB   24 downloads

 share.jpg   87.87KB   14 downloads

[Chefkeks]

Works great

Thank you and thanks Lancelot for the improved version of the share script