3 replies to this topic

[Joel P]

Trying to write some custom module(s). Please do not turn this is a discussion on which modules I should write, keep that in this post please.

Are there any docs with all of the commands and parameters? Is there some place I can put local scripts for testing? If I add my own script definition to the releases.list fine will it get clobbered in a APUP/AutoPatther engine update?

[DesertJerry]

There is documentation. Cristiano should be the one to ask for a copy. He had said he would be out of town till Wednesday - so there may be a delay in your getting an answer.

[_def_x_]

Cristiano has been pretty good about giving the documentation out to those who wish to learn - Here It Is! The docs are getting outdated but should offer some assistance.

Also, have a look at any script, they are text files and can be opened in Notepad etc. You can copy a script out of the temp_bin folder if you run APUP, before you click 'Finish', or you can save a script that you open in a browser - here is the latest Adobe Reader Script - open it in your browser and save page as (.script should already be selected), when done open it in Notepad (or any text editor) and you will see how a script is written.

As far as the conversation about a new custom module, they may or may not want the conversation public if they decide to pass on the idea, but you can always PM someone for help, I will respond if I'm around, and I'm sure if you asked ahead of time, someone else may allow you to PM them for advice.

I don't think they will allow you to test a script they don't want, if that is the case, you can always develop your idea by running the script locally, also, VMs are a good idea when it comes to testing installations. I have somewhere a simple \module layout (for running in AutoPatcher) that demonstrates the idea of creating a folder structure, if you want it let me know and I will dig it up. It's simple but it gets the idea across on how to create a custom folder layout. If you can live with the release being unsigned (Unofficial / Unsupported - this doesn't mean not able to run or work properly) you can do a lot with APUP and AutoPatcher on your own.

[Joel P]

gUiTaR_mIkE, on 22 June 2010 - 12:23 AM, said:

Cristiano has been pretty good about giving the documentation out to those who wish to learn - Here It Is! The docs are getting outdated but should offer some assistance.

Also, have a look at any script, they are text files and can be opened in Notepad etc. You can copy a script out of the temp_bin folder if you run APUP, before you click 'Finish', or you can save a script that you open in a browser - here is the latest Adobe Reader Script - open it in your browser and save page as (.script should already be selected), when done open it in Notepad (or any text editor) and you will see how a script is written.

As far as the conversation about a new custom module, they may or may not want the conversation public if they decide to pass on the idea, but you can always PM someone for help, I will respond if I'm around, and I'm sure if you asked ahead of time, someone else may allow you to PM them for advice.

I don't think they will allow you to test a script they don't want, if that is the case, you can always develop your idea by running the script locally, also, VMs are a good idea when it comes to testing installations. I have somewhere a simple \module layout (for running in AutoPatcher) that demonstrates the idea of creating a folder structure, if you want it let me know and I will dig it up. It's simple but it gets the idea across on how to create a custom folder layout. If you can live with the release being unsigned (Unofficial / Unsupported - this doesn't mean not able to run or work properly) you can do a lot with APUP and AutoPatcher on your own.

There is a localscript option which seems to be exactly what I'm looking for. Thanks.

Edited by Joel P, 22 June 2010 - 04:53 PM.