Skip to content
This repository has been archived by the owner on May 8, 2023. It is now read-only.

Arma Class #4

Closed
overfl0 opened this issue Mar 4, 2015 · 5 comments
Closed

Arma Class #4

overfl0 opened this issue Mar 4, 2015 · 5 comments

Comments

@overfl0
Copy link
Owner

overfl0 commented Mar 4, 2015

Originally reported by: The Sighter (Bitbucket: sighter, GitHub: sighter)


Create a class with the following specs:

package: arma

module : arma

Classname: Arma

Methods

  • *+ get_user_path() * this should return the place to the path where mods can be installed in the user folder
  • *+ get_installation_path() * this should return the folder there arma is installed and mods can be installed to (i.e. c:/program files/steam/commonapps/arma/)
  • + get_executable_path() return path to the arma executable
  • + run_game(modlist, profile) run the game in a separate process with all mods in modlist applied as command line parameters. Use possibility of actually building a text file here and then load arguments form there. The modlist parameter contains a list of real mod-class-instances. Profile name should also be applied.

Notes

All information should be retrieved from the registry


@overfl0
Copy link
Owner Author

overfl0 commented Mar 4, 2015

Original comment by overfl0 (Bitbucket: overfl0, GitHub: overfl0):


Why use get_user_path actually? I'm not sure why would we use that directory over arma_installation_path dir.
Besides, I've got a separate drive for arma and would not want to use my user folder which resides on a totally different drive (and is tight on space).

@overfl0
Copy link
Owner Author

overfl0 commented Mar 6, 2015

Original comment by overfl0 (Bitbucket: overfl0, GitHub: overfl0):


One more thing: what do you mean by "package: arma"?
Does it mean the file has to go to an "arma" directory?

@overfl0
Copy link
Owner Author

overfl0 commented Mar 6, 2015

Original comment by The Sighter (Bitbucket: sighter, GitHub: sighter):


Yes right packages map to directories.
Regarding to the user path. I was thinking about installing the mods in the userspace so the launcher don't need admin rights. Maybe we should at least make it configurable. What do you think about that?

@overfl0
Copy link
Owner Author

overfl0 commented Mar 6, 2015

Original comment by overfl0 (Bitbucket: overfl0, GitHub: overfl0):


Ok, I'll add an accessor and a mutator (@staticmethod) for a custom_path and make the class a Singleton. We don't want it to be instanced manually, do we?

@overfl0
Copy link
Owner Author

overfl0 commented Mar 14, 2015

Original comment by overfl0 (Bitbucket: overfl0, GitHub: overfl0):


Implemented. Some tests are missing but other tests were performed manually.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant