Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Freshen the Launcher Design #4

Open
broxen opened this issue Mar 21, 2020 · 2 comments
Open

Freshen the Launcher Design #4

broxen opened this issue Mar 21, 2020 · 2 comments
Assignees
Labels
help wanted Extra attention is needed question Further information is requested

Comments

@broxen
Copy link
Contributor

broxen commented Mar 21, 2020

I threw together the layout for the launcher design rather hastily, and without a lot of community engagement.

I based the concept off the beautiful Guild Wars 2 launcher by Ryan McIntyre: http://ryanmcintyredesign.com/portfolio/guild-wars-2-launcher/

I'm posting those files here, and the design iteration for posterity, but also to open up dialog about how to proceed with the implementation. Through Discord it seems that there is a desire for the following changes:

  • New background art (@mobbyg said he'd provide)
  • Finished implementation, including patching/loading/settings
  • Integrated Login and Server Selection
  • Music? Sounds?

We'll need new concept UI for all of these screens, widgets, and assets.

Original Concept Art

Main Screen
states-launcher-v2
Loading
states-launcher-loading

Revised Concept with @mobbyg Art!

Main Screen
revised-launcher-blkbg
Settings
revised-launcher-settings

Current Launcher [WIP]

Main Screen
launcher

@broxen broxen added help wanted Extra attention is needed question Further information is requested labels Mar 21, 2020
@broxen broxen added this to the SEGSLauncher Initial Release milestone Mar 21, 2020
@broxen
Copy link
Contributor Author

broxen commented Mar 21, 2020

Assigning Stakeholders. Feel free to remove yourself after viewing.

@nemerle
Copy link
Contributor

nemerle commented Mar 26, 2020

Use cases to consider:
Server groups - in some cases we might want to have multiple auth-servers in a group:

Group Server
SEGS
Internal-testing
Testing
Live
Local-host
Internal-testing

Client assets - we will need a way to notify our dear users that they'll need to download some assets to play on a given server, or that a new version of client/asset will be downloaded.

I think, that in the end, we'll end up with a directory structure something like:

client_executables/
  segs_client_1.0.0.exe
common_plugins/
  v1.0.0/
asset_cache/
  a_file_that_is_used_by_many_servers.file
assets/
  segs/
    live/
      .manifest
      plugins/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants