98 replies to this topic

[Galapo]

Looking good I think. Probably fix_hdc_Amalux.script should be under 'System\Windows Install Tools'.

Regards,
Galapo.

[Lancelot]

For now sub grouping seems to be finish

now last step is main grouping

After a self mind storm for a long while i decide to group in 5 categories

Appu_A
Appu_AE
Appu_B
Appu_CT
Appu_CU

Appu_A -->All free
Appu_AE -->All free Extra
Appu_B --->BUT - free BUT setup is not distributable or updates needed
Appu_CT -->Commercial Trial
Appu_CU -->Commercial Ultra (not freely downloadable from developer's website)

I try to keep in order starting with free, freeextra, freebut, commercial trial, commercial ultra so gave names that way (commercial ultra was a bit hard)

also i try to avoid giving long names
and try to make them appear after Apps (Apps is default with LiveXP)

Take a look at this to see how it looks on winbuilder, abbreviations seems to me very easy to understand after spending 2 minutes

http://lancelot.winb...ds_Grouping.rar
(extract this .rar file to \LiveXPAdds\Projects\)

Any comment will be appreciated

[Lancelot]

Nearly ready (for a start)

here is cdcat with new cdcat database
http://lancelot.winb...00901210200.rar
just click
1_Lancelot_Test_200901210200.cmd

here is the new cdcat database file for ones who already have cdcat
http://lancelot.winb...00901210200.rar


I plan to start uploading tomorrow with this settings, any comment ?

[amalux]

Lancelot,

What is this for again?

No, seriously, can you explain a bit more how this affects the downloaded projects (if at all). It looks great; very organized! - but I wouldn't like a bunch more folders downladed with the projects. Like I said before, I don't like so many (some empty) folders included like now and more is not better; it doesn't affect me much but just sayin'.

I can't get past the Appu_A; _AE; __B; _CT; _CU headings, why can't all programs be under just 'type of program' headings? i.e. all hdd backup tools under one 'hdd backup' heading regardless of freeware, commercial, files included or not etc. This is just the way my mind organizes things I guess, when looking for sth I want to look in one place and see all available there.

If you really need to seperate the different types of scripts as you have, I'd rather see it in this way:

CD/DVD
-->A type
-->B type
-->C type

HDD Backup
-->A type
-->B type
-->C type

... just my 2 cents worth

[Galapo]

I also agree with Amalux in that I think firstly of app "type" before redistribution status etc. I think the grouping before was fine and simple.

I must again say thanks for your work on this!

Regards,
Galapo.

[Lancelot]

Hi amalux

no this wont effect any of the downloaded projects.

just download this
http://lancelot.winb...00901210200.rar
and click
1_Lancelot_Test_200901210200.cmd


I am trying to figure out a better (or more suitable) way to deploy scripts

Because of the huge number of scripts i have to split them in some pieces BUT with minimalistic idea of gathering them as small branches as possible. So far there are ~100 scripts i gathered to upload for a begining which leads to these solutions i found.

Giving example for backup disk, there are all in one scripts so user dont need to make extra download or need license:
A --> All in one scripts (free)
Appu_A\HD Tasks\Recovery_Imaging\CopyWipe_Amalux.script
Appu_A\HD Tasks\Recovery_Imaging\dubaronDI_billonious.script
Appu_A\HD Tasks\Recovery_Imaging\savepart_PartitionSaving.script
CT --> Commercial and Trial
Appu_CT\HD Tasks\Recovery_Imaging\Snapshot.script
CU --> Commercial (very ), not downloadable from developers website )
Appu_CU\HD Tasks\Recovery_Imaging\Acronis-TrueImageEcho95-Omni.Script
Appu_CU\HD Tasks\Recovery_Imaging\Ghost11_Lance.script


Because of increasing number of scripts, This main grouping i believe very essential, but maybe changed in future. I am not stubborn about any ideas, but it looks really nice. If dont work in way i believe than i will change again .




For personal needs, i agree with you, i would probably use only ghost11 and savepart from the list and putting both to Appu\HD Tasks\ is a nice solution. In fact i was putting all my scripts to a single folder before, But for deploying i need to figure out a more general and understandable way so that is why i opened this topic to get ideas from you, and i used all comments.

I believe summing 1_Lancelot_Test_200901210200.hcf with how it would look like on winbuilder for LiveXP, you figured out what i am trying to do.

ps: Snapshot.script is already in LiveXP project which i believe Galapo's favorite, it is not in my list/catalog, i just put here as an example.


Besides deploying scripts, it will be very useful for trustable script writers to cover others ass. (I guess it is the right expression ). From experience with Galapo and saydin77, it is very nice to know someone checking and fixing your work.

[Galapo]

"CT --> Commercial and Trial" example would be the zonealarm antivirus script. Smart Driver Backup is freeware.

Regards,
Galapo.

[Lancelot]

Galapo,

ahhh very sorry i mixed Snapshot.script with Smart Driver Backup, i am fixing previous post.


@all
maybe looking this catalog file makes more clear:

"download cdcat with catalog, and click 1_Lancelot_Test_200901210400.cmd" http://lancelot.winb...00901210400.rar

"download only catalog" http://lancelot.winb...00901210400.rar

[Galapo]

The simple layout you've developed, say, under 'Appu_A' is what I thought was going in under 'Apps'. I assume these other folders ('Appu_A' etc) are not downloaded with the project per se, but are generated when downloading additional non-project-supplied scripts from other location (eg apps.winbuilder.net).

Regards,
Galapo.

[Lancelot]

Galapo,

Yes, the desciption you made is the defination of my work (ahh native english ahh , i feel like solving a puzzle with fun when reading ). In other words, this is not a new project (like LiveXP, NaughtyPE, VistaPE), this is for deploying/updating additional "selected" non-project-supplied scripts easly with winbuilder.

[Galapo]

OK, but I think we can use the same layout in the LiveXP 'Apps' folder as well so as to a) make things more tidy; and b) maintain consistency between naming conventions with the "alternative" place to download scripts.

I'm still not sure what to think about these names, but for a start could I suggest 'Apps_A' rather than 'Appu_A' etc?

Regards,
Galapo.

[Lancelot]

I suggest 'Apps_A' rather than 'Appu_A' etc?

Thanks and Done

[amalux]

Like Galapo said, thank you for all your hard work on this

I'm afraid we'll have to agree to disagree on this one; I'll always prefer this


to this

[Lancelot]

amalux

no need to agree or disagree , I guess i find a midway,

Idea is this:
We make 2 populer script groups in the way you descibe,
like HdTasks and System (which i guess upper most populer for PE ) like in the photo you show.
others leave as it is for now

Time and other comments would lead us to continue either one way or another. I hope you like

[Galapo]

Just thinking here ... if a project maintains consistency of naming between this other source of application-scripts, then they can also just download under 'Apps' in the project. The user just selects which scripts they want to download from which category.

But this means that scripts for freeware apps would be together with those for commercial software.

But then how about:

apps.winbuilder.net/LiveXPAdditions/Freeware
apps.winbuilder.net/LiveXPAdditions/Commercial

Regards,
Galapo.

[Lancelot]

Galapo

downloading under 'Apps' would result with a big mixture (i thought about it long time ago), project masters are responsible for the scripts they provide with project which are under apps but users would mix this all the time. Better to seperate them. My first idea was a single Apps_Extra but with time passed i came to this point. With current a user can easly disable all extra script with one click and what is left is project scripts.


using:
apps.winbuilder.net/LiveXPAdditions/Freeware
apps.winbuilder.net/LiveXPAdditions/Commercial
would lead to 2 server names which really dont like + dont forget amalux .

mixture idea for popular branches i posted would seem to work fine, and maybe we can use download levels for commercial ones if you desire ?.

[Galapo]

downloading under 'Apps' would result with a big mixture (i thought about it long time ago), project masters are responsible for the scripts they provide with project which are under apps but users would mix this all the time. Better to seperate them.

Yes, I realise. However, I think the user wouldn't mind "freeware" mixed with "commercial". That is, the user would prefer all apps under 'Apps' I think. This is what Amalux is getting at.

would lead to 2 server names which really dont like + dont forget amalux .

This would lead to just one 'Apps' folder which is what Amalux would prefer, me too I think. The user would select the download server for the type of application they desire, either "freeware" app or "commercial" app.

Still against?

Regards,
Galapo.

[Lancelot]

Still against?

For this subject with these nice people, Never

At least like in amalux photo, I would prefer extra scripts be in A, B, CT, CU subfolders. (or EA, EB, ECT, ECU (E means Extra))
With advantage of getting all in one, we loose easy distinguish between project scripts and extra scripts which i reallllly dont like.
But as majority wants that, why not

I hope we come to a conclusion for main structure now

[amalux]

This would lead to just one 'Apps' folder which is what Amalux would prefer, me too I think. The user would select the download server for the type of application they desire, either "freeware" app or "commercial" app.

So you would select the server for the type of app but any hd task script would end up in the same 'HD Task' folder? I like it very much!! Keeps the diff types separated but still retains simple folder structure for organizing scripts in project

[Galapo]

So you would select the server for the type of app but any hd task script would end up in the same 'HD Task' folder?

Yes, that's my suggestion, rather than having 'HD Tasks\Apps_A' etc.

Possitive: keeps user's project folder simple.

Negative: mixes non-project-supplied scripts with project-supplied script. But this has always been the case since a user can go to the Downloads page, download an app, and put it in their project folder wherever they like.

Regards,
Galapo.

[amalux]

Yes, that's my suggestion, rather than having 'HD Tasks\Apps_A' etc.

Possitive: keeps user's project folder simple.

Negative: mixes non-project-supplied scripts with project-supplied script. But this has always been the case since a user can go to the Downloads page, download an app, and put it in their project folder wherever they like.

Regards,
Galapo.

Yeah, I don't see any negatives, this is a great solution Galapo and it gets my vote

Now it's up to Lancelot

[Galapo]

Yeah, I don't see any negatives, this is a great solution Galapo and it gets my vote

Well, we've really come up with together and it's been a group effort. Lancelot has done all the hard work though.

Regards,
Galapo.

[Lancelot]

amalux, you dont see any negatives because i was busy for preparing

Negative: mixes non-project-supplied scripts with project-supplied script. But this has always been the case since a user can go to the Downloads page, download an app, and put it in their project folder wherever they like.

This user (me) never mix project scripts with the scripts i gather or made In fact i never mix any files on my pc, i am pretty tidy and very fast file finder. I desperately need a simple way to distinguish between project scripts and extra scripts.

Oki, now all extra scripts are in Apps, so when downloaded there wont be any other main folder
BUT
Like shown in the picture of amalux, i put EA, EB.. (or 1E, 1EB for root branches) folders for the scripts, BUT BUT dont worry, i prepare shortcuts not created that way. (I guess ExtraA, ExtraB ... maybe better, i thought that when writing this post)


Anyway, I hope we can come to a conclusion with this, here is the catalog file:

http://lancelot.winb...00901210500.rar

[Galapo]

This user (me) never mix project scripts with the scripts i gather or made In fact i never mix any files on my pc, i am pretty tidy and very fast file finder.

Me, I mix stuff around all the time. I leave finding up to FindOnClick.

I think there's competing factors here now.

Regards,
Galapo.

[Lancelot]

I think there's competing factors here now.

well, my sister is untidy and i am tidy. This is all about habits which would lead opposite direction.
But there is always a midway which opposite sides are equally unhappy :
Instead of 5 branches like: EA, EAE, EB, ECT, ECU which was more useful with different app folder
I can offer only 1, Extra

So distinguishing between commerial, trial ... scripts gone making folder structure more tidy, but still distinguish between project scripts and extra scripts exists

I lost idea of simple click option to disable extra scripts and with this offer i lost distinguishing script type,
I guess i am unhappy enough ???


ps: unhappy is a joke, i am not sad or whatsoever, i used this word just to give the idea.