As Developer I want a CI system that:

• always provides me with a latest build (zip archive)
• always provides me with a latest build (msi archive)
• automatically builds all (tagged?) releases as zip and msi
• automatically informs me when there is a build failure
• automatically runs unit tests and fails the build if tests fail
• automatically builds for all supported platforms

At the moment every new version of a mod / map needs a separate UID when uploaded to the vault. This clutters the vault with old versions.

Would be better if the mods could get updated automatically to the latest version. There is a "version" value in mod_info.lua which could be used for mods at least.

It would be nice if the lobby could be set to store maps (autodownload) in the folder of your choice, in case your C: drive, like mine, is a bit low on space.
It's possible to move maps in FA folder, but the lobby will not look there, and redownload maps from the lobby, so it's pointless.

I would like a more testable Model-Presenter or Model-Controller relationship between the actual core modules and the individual tabs (presenters in this context being views+controllers in one thing) in order to make code more testable and modular. (a nice start was done in the new-protocol branch, I think it needs to go much further than that)

I would also like to refactor basically every "communications" component into a Logic and View part.

Without overdoing this, this should get us a nicer architecture in proper increments. It will also allow us to swap out the client code to a different protocol version as well.

Long-Term-Goal would be an actual MVP architecture, but this is out of scope for this issue.

Bug report here.

Regarding what you said in IRC, I suggest we go with this tagging scheme for the fa repo:

FA patch releases:

v1.5.0-patchlevel

And prereleases get

v1.5.0-patchlevel-pre

subsequent ones

v1.5.0-patchlevel-pre.x

I don't think we need a seperate release scheme for hotfixes--they'll just go with the next patchlevel.

Strictly speaking, when we update the FA exe with support for shared armies, we should go to v1.6, since we added functionality that doesn't change the API. (Semver)

I think this milestone should be renamed Git for FA and mods, I'll be quick and do that 👍

I would like a simple process that gets all the required dependencies to build the project.

Vagrant sounds like a good idea for this.

I want the new MSI installer to properly create a desktop icon, to remember the previous install location on upgrade, and to show up in a windows 8 start group (different from start menu).

Start Menu entries are also an option.

Make all Margins, Layouts, Colours more consistent.

It contains far more than just source code; it's basically the whole app.

Goals include:

• run app as python module (python lobby .... where lobby is a directory)
• package app as easy to install binary

Refactor Code so it's PEP-8 compliant.

Messaging should move away from irc towards XMPP for most intents and purposes.

It's really terrible and needs unification.

Hey,
are you official?
I like your effort,
but I think it is a bad idea to split the community ...

I hope you effort is not lost ...

For me the lobby is only startable,
if i move the res folder back into the src folder ...

I also tried to link the res folder in liclipse (pydev) ...
no success

Theme Support is a strong point of failure at this moment.

It can be retained as a command line trick but needn't be configurable in-client.

In my opinion the forum is full of:
"useless opinion posts, without arguments"

GOOD POSTS ARE LOST !

Instead of moderate it and add rules you can try this:
https://www.phpbb.com/community/viewtopic.php?t=2095240

Upvote and Downvote posts.
Hide "downvoted" posts.

Original bug report by Voodoo here.

I don't think it never works, but I have experienced problems with it myself.

I started a friendlist for faf ...
Never merged:
https://bitbucket.org/IDragonfire/modular-client

All HTTP downloads should work through a centralized system.

All non-HTTP downloads should be candidates for HTTP.

For the future we need a platform to vote.
Each faf.user should only vote one time (forumlogin != faf login)
Should I implement a simple "vote system" into the webapp?
(It gives the users the feeling they can decide and you/we get some feedback)

Example

Which voice communication way you prefer?

• Mumble
• Skype
• Teamspeak
• InBuild (integrated into the faf.lobby)

IRC commands such as /join etc. should be made to work for the client.

Submitter: Moritz's Test Report
Email: [email protected]
This is a test report.

Maybe renname the tab to "Community".

Content of the tab cleaned up:

-News (including next tournements, force TD's to write one, or make it automatic if possible)
-Latest Casts
-current active Livestreams
-Donate

If needed make sub-tabs or something similar with:
-mumble
-stats that are currently displayed, or more
-other links, if they are not placed at the top bar: Clans, Username change, Password recovery, Forum, Wiki, Unit DB, anything community related

-When there is an active livestream, change the icon of the tab to something animated and colorfull (maybe a running TV) to make it easy visible that someone went live without having to check the tab
-When there is an unread news, change the icon of the tab or make it colored or something too, to assist people in reading news. Don't know if you are able to check if someone has already visited the news page already since the last news though.

-Remove livestream tab in return

-Don't try to run livestreams in FAF. Let them open in your browser instead.

Very bad mockup, please remember i have nothing to do with design :)

http://i.imgur.com/Guy4Yiu.png

Exhumed made the FAF icon that is used in several places. Our use is not compliant with his "no derivative works" requirement; while I did get written permission for FAF 0.5 to use it, the change in project ownership dictates (he was barely cooperative back then) to switch to our own logo now.

The "Replays" tab reads all metadata from existing replays in FAForever/replays directory

This makes the Replays tab stall when using platter-disk, even if you're just interested in searching for replays in "Online Vault", not "Local Archive"

I guess this will be solved with Reborn but just wanted to make a note about it.

The link to cdn.thqonline.com to download the official patch does no longer work.

Someone also commented the illegal version check out (i.e. whether someone had a version with an unrecognized lua.scd). I put it back in.

This is the most "trustworthy" link I found so far.
http://www.gamefront.com/files/files/9983432/supcom_fa_patch_1.5.3596_to_1.5.3599.exe

Anyone know:

• a better link
• a reason why the lua.scd hash check was disabled?

Self explaining I hope. :)

The issue with that is that it will create many unmoderated channels. A possible solution I thought of:

Any moderator for the channels will join automaticly. If there is at least one moderator in the channel, everyone else will also join automaticly, otherwise not. The most popular languages will hopefully have a moderator online most times.

Or will that lead to too much confusion?

So there have been some reports of webviews playing sound, specifically the tournament webview, reported here and here.

Setting

QWebSettings::PluginsEnabled

to false should disable flash ads.

HTML5 audio can be blocked through injection of JS.

@Sheeo and I just had a lengthy chat on which versions to support, legalities of how the FAF patch currently looks, and what we want to do.

Supported Versions

• Forged Alliance 1.5.3599 (official Retail)
• Forged Alliance 1.5.3603 (beta Retail)
• Forged Alliance Steam
• Supreme Commander 1.1.3280 (official Retail)
• Supreme Commander Steam

We may want to discontinue support depending on the patch requirements.

We will explore the possiblity of creating and providing a community patch from Retail, Retail 3599, and Retail 3603 to Steam, as well as a Supreme Commander patch from Retail and Retail 3280 to Steam - which would make the FAF "mod" much slimmer.

Mode of Operation

• FAF clones the bin directory and compares it to one of these versions
• It applies binary patches to bring relevant files up to the right version

Licensing Issues

The patches are derived works, which are most likely not GPL3-compatible.

Unauthorized Copies

Unauthorized Copies are not supported and not encouraged. GPL3 warrants there will be no DRM in the Lobby or associated components. 👍

Original bug report by Myxir here.