Difference between revisions of "Talk:Adobe Reader"

From WPKG | Open Source Software Deployment and Distribution
Jump to: navigation, search
(Multiple Pages for this Program)
(Multiple Pages for this Program)
Line 9: Line 9:
 
::::Maybe Firefox could be also grouped, per major release, with a category (perhaps Mozilla category, containinh Firefox, Thunderbird, Seamonkey, extensions etc.)?
 
::::Maybe Firefox could be also grouped, per major release, with a category (perhaps Mozilla category, containinh Firefox, Thunderbird, Seamonkey, extensions etc.)?
 
:::I Think it is better to have only one site here. for other programs does only one site exists too and there will be no misunderstanding by clicking on the wrong site
 
:::I Think it is better to have only one site here. for other programs does only one site exists too and there will be no misunderstanding by clicking on the wrong site
 +
::::[[User:Ozinm|Ozinm]] 15:21, 4 November 2010 (CET):
 +
::::I tend to agree. I'd prefer one page only with the latest version at the top. There's no sense in over-engineering. I suggest that we only start thinking about creating a category structure '''if''' the page starts to become too cumbersome, '''not''' before.
  
 
=Adobe Reader 7=
 
=Adobe Reader 7=

Revision as of 14:21, 4 November 2010

Multiple Pages for this Program

Why do we have pages for Adobe Reader, Adobe Reader 8 and Adobe Reader 9. I think for ease-of-use we should have them all on the one page with the different versions each in a section of their own

Wouldn't be a single page for Adobe 7, 8 and 9 just too long? And it would be just longer with future releases?
Adobe_Reader page should just contain links to all Adobe Reader versions.
Or, what's your opinion?
I think that it is best to have separate pages for the different releases, but I doubt if they are really needed and the latest release would be enough.
The Adobe Reader page as a link page seems to be a good idea to keep it simple, a separate category should be good too.
I vote for one page for each major release, with a category grouping the releases. In example I am worried on how long and messy the Firefox page is getting. Ilgino 09:00, 17 July 2009 (CEST)
Maybe Firefox could be also grouped, per major release, with a category (perhaps Mozilla category, containinh Firefox, Thunderbird, Seamonkey, extensions etc.)?
I Think it is better to have only one site here. for other programs does only one site exists too and there will be no misunderstanding by clicking on the wrong site
Ozinm 15:21, 4 November 2010 (CET):
I tend to agree. I'd prefer one page only with the latest version at the top. There's no sense in over-engineering. I suggest that we only start thinking about creating a category structure if the page starts to become too cumbersome, not before.

Adobe Reader 7

Allan Stone writes:

On the website you have Adobe Reader 7.0.5 package file but it errors out sometimes when you remove it. I have made a WSH script to take care of the removal for us. It passes everytime. Ive yet to have to fail.

I called the file 'remove.js' and added it as the remove command for the package


//WScript.Echo("Uninstaller for Adobe Reader 7.0.X");
//WScript.Echo("----------------------------------");
//WScript.Echo("");

var adobe_7_reader_0 = 1;
var adobe_error = 1;

var objShell = WScript.CreateObject("WScript.Shell");
//WScript.Echo("...Checking registry for Adobe Reader 7.0.X")

try
{
  var key1 = "HKEY_LOCAL_MACHINE\\SOFTWARE\\Adobe\\Acrobat Reader\\7.0\\InstallPath\\";
  test = objShell.RegRead(key1);
//  WScript.Echo("...Acrobat Reader 7.0.X found");
}
catch(e)
{
//  WScript.Echo("...Adobe Reader 7.0.X NOT found");
  adobe_7_reader_0 = 0;
}

if (adobe_7_reader_0 == 1)
{
  try
  {
//    WScript.Echo("...Uninstalling Adobe Reader 7.0.X");
    objShell.Run("MsiExec.exe /qb /x{AC76BA86-7AD7-1033-7B44-A70500000002} REBOOT=ReallySupress",1,true)
  }
  catch(e)
  {
//   WScript.Echo("...Error uninstalling Adobe Reader 7.0.X\n");
//   WScript.Echo(e.description+"\n")
//   WScript.Echo(e.message+"\n")
//   WScript.Echo(e.number+"\n")
  }
}

//WScript.Echo("\nComplete.");

I hope this helps. there is probably a better way and more simple but it works and that does it for me.