Thoughts on the OI for the future

[TwoJ]

I think this is a thread for benners but i wanted to get other users opinions about possible changes and features for the OI.

- As many of you might have seen I am trying to get updates for office 2007 to be in a 2 hotpack format - 1 for global hotfixes (non-language dependant) and 1 language dependant. You can see more in the office 2007 hotpack sticky.

- Another point is with the arrival of Office 2010 soon, which i think will follow the same procedure as 2007 for updates the OI should be i think Office2010 'ready'. However as many of you might know it will also be the first 64 bit version, as well as the x86 version. Since now we will be dealing with x86 & x64 versions of hotfixes, i think it would be a good idea to start labeling hotpacks with x86 and to make sure the OI can differentiate between the two types.

lets hear any other ideas!

[gryffin53]

I also think there should be a good labeling for the office hotpacks. I will be happy to add the office 2010 packs to my other Dutch releases.
I don't think the OI could have difficulties with both the 32 and 64 bit versions of 2010 as it only copies the content of the hotpack to the update folder.
Just my 2 cents.

[ChiefZeke]

I'll agree with the suggestion to label Hotpacks, etc with x86 and x64 to differentiate things.:)

[benners]

I think this is a thread for benners but i wanted to get other users opinions about possible changes and features for the OI.

- As many of you might have seen I am trying to get updates for office 2007 to be in a 2 hotpack format - 1 for global hotfixes (non-language dependant) and 1 language dependant. You can see more in the office 2007 hotpack sticky.

- Another point is with the arrival of Office 2010 soon, which i think will follow the same procedure as 2007 for updates the OI should be i think Office2010 'ready'. However as many of you might know it will also be the first 64 bit version, as well as the x86 version. Since now we will be dealing with x86 & x64 versions of hotfixes, i think it would be a good idea to start labeling hotpacks with x86 and to make sure the OI can differentiate between the two types.

lets hear any other ideas!

These threads asking for user input never really get any replies, I tried asking when I first started the OI but there were few replies.

As for the future, due to some of the code Office 2010 wont work with the OI, it may be a simple fix we'll see.

I intend to do a few changes and improvements. The banner that changes dependent on the version is going, i'll just replace it with some text.

The office compatibility pack integrator part will try to be merged and use the same process as the main office integrator.

The radio buttons that were used to select the office version will be gone, they are redundant now as the info is retrieved from the exe.

The Technet download for Office 2010 are exes so some code will have to be added to first extract the Office setup files to allow for both these and iso images, and also the x64 and x86 renaming suggestion.

I am looking at adding ore functionality regarding 2007 onwards, like chained installs etc and editing the config.xml file. One idea was a drop down were different applications could be excluded during istall time, a bit like using an mst file but I don't know how I will get the list off apps associated with the different office versions.

On the code side it needs cleaning up to make it easier to update. With all the mods that have been required they have just been quick fixes to get things working.

I may also change the integration process where the exes are extracted and integrated individually so msp files with the same name from different updates are not overwritten.

If there is any functionality not used please let me know and I can remove it. All the above depends on time and know how, both of which are limited from me :)

[TwoJ]

Hi benners

Still working on that time reversal machine to give us some more time to do this stuff.

I've actually just had a good idea but i'll need another post to explain it properly.

My orginal idea was to have the OI run possibly by a ini script, i asked siginet if it was possible to do the powerpacker like that so you can already put your variables in a preprogramed ini file, ie setup location, hotpack location, username/company info, etc
I realize that it probably would require a significant change to the OI.
Maybe we can ask M$ for a part time job for you?

[benners]

Hi benners

Still working on that time reversal machine to give us some more time to do this stuff.

I've actually just had a good idea but i'll need another post to explain it properly.

My orginal idea was to have the OI run possibly by a ini script, i asked siginet if it was possible to do the powerpacker like that so you can already put your variables in a preprogramed ini file, ie setup location, hotpack location, username/company info, etc
I realize that it probably would require a significant change to the OI.
Maybe we can ask M$ for a part time job for you?

Yep hurry up with that machine :). As for the ini idea not sure how easy\hard it would be, now would be the time to implement new stuff whilst I am contemplating changing code. The OI already has an ini that has the variables in it. The checks could run as they do when loading a previously saved config and only stop if an error occurs.

I also thought about having either a novice setting that is basically a step by step to using the OI where the user is prompted for the source and destination etc or at least add some tuts to the help file.

Uni finishes around July, if I stay on the course, so I may have some time then in between working and renovating the house. Again please hurry with your time machine.

As for the MS job, the first thing I would do is find the group responsible for the Office updates and its continuity, reach into their mouths and pull their skeletons out for giving me headaches with the hotfixes.

MS could prolly knock an OI up in about a week or maybe they'll wait 'till I start a company then buy me for the program :)

[crashfly]

I would consider offering suggestions for the Office Integrator, however I will probably never go past Office 2003. Except for user interface changes, I have never found a need to update. A word processor is a word processor. A spreadsheet is a spreadsheet.

As for the OI, if it is fairly simple to use then I say go with it. Of course because I am not going to upgrade, I am sure I do not do as many integrations as everyone else.

Just keep up the great work benners. :D

[TwoJ]

ok benners, i think the caffine has hit the brain cells to make the idea somewhat coherent;

There are a few programs, example off the top of head - the driverpacks, that reference an online database on current versions.
What about an online database for the OI, and a OI that works with an ini file and perhaps a command line?

The ini could hold all the info, location, Key, Username, update location, hotpack/hotfix location. With the online check you could also keep a database of active hotfixes that could be automatically downloaded from MS, the same way the driverpacks autoupdate. That way no one needs create hotpacks :D, just need someone to keep the database up to date :rolleyes:

Then if you get it to a command line you could just do something like
Office Intergrator /integrateOXPCorp.ini /AutoupdateFromInternet

I would love to just script the whole thing into automation;
Mount office2k3.iso to E:/
Office Intergrator /integrateOXPCorp.ini /AutoupdateFromInternet
Copy C:\UptoDateOffice2k3 to T:\USBStickForOffice

I'm sure you get the idea, anways the online database would obviously need a perminant website so i don't know if signet would be into that, plus find out how to do it.

Anyways some ideas, just incase you find yourself wondering what distraction you need from other stuff!

[benners]

I would consider offering suggestions for the Office Integrator, however I will probably never go past Office 2003. Except for user interface changes, I have never found a need to update. A word processor is a word processor. A spreadsheet is a spreadsheet.

As for the OI, if it is fairly simple to use then I say go with it. Of course because I am not going to upgrade, I am sure I do not do as many integrations as everyone else.

Just keep up the great work benners.

I think a lot of people will stick with 2003 for a while so if you have any ideas just mention them here


ok benners, i think the caffine has hit the brain cells to make the idea somewhat coherent;

There are a few programs, example off the top of head - the driverpacks, that reference an online database on current versions.
What about an online database for the OI, and a OI that works with an ini file and perhaps a command line?

The ini could hold all the info, location, Key, Username, update location, hotpack/hotfix location. With the online check you could also keep a database of active hotfixes that could be automatically downloaded from MS, the same way the driverpacks autoupdate. That way no one needs create hotpacks, just need someone to keep the database up to date :rolleyes:

Then if you get it to a command line you could just do something like
Office Intergrator /integrateOXPCorp.ini /AutoupdateFromInternet

I would love to just script the whole thing into automation;
Mount office2k3.iso to E:/
Office Intergrator /integrateOXPCorp.ini /AutoupdateFromInternet
Copy C:\UptoDateOffice2k3 to T:\USBStickForOffice

I'm sure you get the idea, anways the online database would obviously need a perminant website so i don't know if signet would be into that, plus find out how to do it.

Anyways some ideas, just incase you find yourself wondering what distraction you need from other stuff!

Thanks for the ideas TwoJ.

The ini file and automation shouldn't be a big problem. I was thinking of using the same ini file as is used now but instead of specifying an ini on the command line, you could just specify the ini section. There could also be a default one that is used each time.

If this is successful I may try to make if possible to update all office versions in series so you could do 2003 then 2007 etc but I don't think this would be of much use to folks.

The online database has happened before when Siginet started to program, with regards to the registry entries, and it got a bit of a bind to keep up to date with the different languages.

I had an idea before where I wanted to list the updates that the user had selected plus check online for new ones and auto download. I would like to use the same process as windows updates, probably an api?, but I don't have a clue about how to do it.

I also have no idea about setting up an online database that lists the updates and if I did it would just be something else to maintain, like the help file.

I agree about the hotpacks, there should not be a need to create them and the likes of yourself and others kindly donate their time to maintain the ones you have created. The facility is there for a user to create their own, all they need to do is download the updates. They can also download peoples hotpacks and just keep them updated but even when it is just one new update people would rather download the newest hotpack :confused: either the option to do this is not properly advertised or people are to lazy.

I have no doubt that if an online db was set up there would still be requests for hotpacks.On a positive note I could save a few hundred lines of code by removing the hotpack options :)

[crashfly]

As a suggestion, one could create an online db that is downloaded from time to time, but also make the "repository" customizable. While I realize an active maintainer would reduce the need to customize, what happens if that person stops maintaining? (or more realistically, the website temporarily goes down?)

Checking online is good, but keeping a local copy of the db like a linux system does, would be a better option. And if hosting goes down, or maybe someone else keeps a backup site, then the online lookup could be changed on the fly.

[TwoJ]

I think thats a great suggestion

One of the problems i've seen are some great programs/utilities that have been developed that eventually the creator can't/ doesn't have the time to keep it going. A great example is perhaps xehqter's OEMSCAN, i completly agree that as the orginal author that he has the choice of developing it and profiting or never releasing the code if he chooses, but if the point is to make it useful to others for free and its just because there is no time then i think its great if they can open-source it so that others can take over.

Likewise for the OI it would be great if the online db had multiple repositories that 2 or 3 people could maintain if necessary.