shadowfacts
/
Tusker
2
10
Fork 2
Code Issues 62 Pull Requests Releases Wiki Activity

Multiple accounts #16

New Issue
Closed
opened 2019-02-09 19:32:58 +00:00 by shadowfacts · 2 comments
shadowfacts commented 2019-02-09 19:32:58 +00:00
Owner
Copy Link
No description provided.
shadowfacts added this to the 1.0.0 milestone 2019-02-09 19:32:58 +00:00
shadowfacts added the
enhancement
 label 2019-02-09 19:32:58 +00:00
shadowfacts commented 2020-01-05 18:49:53 +00:00
Author
Owner
Copy Link

This is going to need a massive refactor that touches almost every area of the code. As such, the infrastructure will be implemented before the UI is capable of signing into multiple accounts or switching between. The rough roadmap is:

  • Pass the MastodonController instance down through the VC hierarchy instead of global shared instance
    • is there a cleaner way of doing dependency injection than passing things into constructors? it gets ugly quick
  • Move MastodonCache to be specific to a MastodonController instance
  • Move ImageCaches to be specific to a MastodonController instance Not necessary
  • Adopt UIScenes and scene-based lifecycle
    • Change user activities & XCBActions to use window from active scene
      • or first scene found, if none are active
  • Get the top level MastodonController instance from the scene session
  • Change XCBActions and NSUserActivitys to get MastodonController from active scene
  • Allow adding additional accounts via user Preferences
  • Change NSUserActivitys to store acct they're in reference to use most recently active account account
    • get scene (active or new) for given account
  • Change XCBActions to use the most recently active account
  • Changed saved hashtags/instances to be account-specific
  • Store account used in drafts, only show drafts from current account
  • Allow switching accounts via user Preferences
  • Add long-pressing user profile tab bar item to switch accounts separate feature
This is going to need a massive refactor that touches almost every area of the code. As such, the infrastructure will be implemented before the UI is capable of signing into multiple accounts or switching between. The rough roadmap is: - [x] Pass the `MastodonController` instance down through the VC hierarchy instead of global shared instance - is there a cleaner way of doing dependency injection than passing things into constructors? it gets ugly quick - [x] Move `MastodonCache` to be specific to a `MastodonController` instance - [ ] ~~Move `ImageCache`s to be specific to a `MastodonController` instance~~ Not necessary - [x] Adopt `UIScene`s and [scene-based lifecycle](https://developer.apple.com/documentation/uikit/app_and_environment/managing_your_app_s_life_cycle#3200035) - [x] Change user activities & XCBActions to use window from active scene - or first scene found, if none are active - [x] Get the top level `MastodonController` instance from the scene session - [x] Change XCBActions and `NSUserActivity`s to get `MastodonController` from active scene - [x] Allow adding additional accounts via user Preferences - [x] ~~Change `NSUserActivity`s to store acct they're in reference to~~ use most recently active account account - ~~get scene (active or new) for given account~~ - [x] Change XCBActions to use the most recently active account - [x] Changed saved hashtags/instances to be account-specific - [x] Store account used in drafts, only show drafts from current account - [x] Allow switching accounts via user Preferences - [ ] ~~Add long-pressing user profile tab bar item to switch accounts~~ separate feature
shadowfacts self-assigned this 2020-01-05 20:29:16 +00:00
shadowfacts added a new dependency 2020-01-08 03:19:16 +00:00
#80 Multi-window support on iPadOS
shadowfacts commented 2020-01-24 03:17:31 +00:00
Author
Owner
Copy Link

Multiple accounts has been merged into master 🎉

3220436893

Multiple accounts has been merged into master 🎉 32204368939d534e28df7570cd7558805b5a73bd
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
develop
public-beta
release
calckey
async
simple-swift-promises
pixelfed
2024.2-121
2024.2-120
2024.1-119
2024.1-118
2024.1-117
2024.1-116
2024.1-115
2024.1-113
2024.1-112
2024.1-111
2023.8-110
2023.8-109
2023.8-107
2023.8-106
2023.8-105
2023.8-104
2023.7-103
2023.6-100
2023.5-98
2023.5-97
2023.5-96
2023.5-94
2023.5-91
2023.5-89
2023.5-84
2023.5-83
2023.5-81
2023.5-80
2023.5-77
2023.4-76
2023.4-75
2023.4-74
2023.4-73
2023.4-72
2023.4-71
2023.4-70
2023.3-69
2023.2-68
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
external

Issue depends on changes to external projects.

  
help wanted

Need some help

  
invalid

Something is wrong

  
investigate

An unconfirmed issue

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
bug
duplicate
enhancement
external
help wanted
invalid
investigate
question
wontfix
Milestone
Clear milestone
No items
No Milestone
1.0.0
Assignees
Clear assignees
No Assignees
shadowfacts
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Blocks
#80 Multi-window support on iPadOS
shadowfacts/Tusker
#84 Allow switching accounts by long-pressing on my profile tab bar item
shadowfacts/Tusker
Reference: shadowfacts/Tusker#16
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?