…on for a basic scale tweening animation.

…o the back key on various platforms, but for now, we have a UI button). Added a very minimal login screen for testing this out.

…e (e.g. open/close methods) and made ConnectPage and LoginPage inherrit from it

…lls the open/close methods on the UIPages directly.

…ncluded in my previous commit and I had to rebuild it... *sigh*

…ing the ITween interface) to animate the various UI pages. The main UI panel now scrolls in from the bottom

…st UI page

…e such that they debug.log what they are supposed to do when clicked

…the UI by creating a scriptable object via 'Assets>Create>Sequence>Color Scheme', setting it as the color scheme in the ColorSchemeManager monobehaviour/gameobject, and clicking Apply in the inspector

…gned to handle the login request. Currently, mocking the login. Upon success or failed login, an ILogin will emit an appropriate event. SequenceUI is a subscriber to this event.

…imations (didn't have animations out)

…w, there is only email validation - I have both a real (with tests) and mocked implementation of IValidator

…ereum. Created assembly for SequenceExamples - referencing all the other Sequence assemblies (minus test assemblies) in the project. Finally, create a SequenceExamplesTests assembly for any tests related to the SequenceExamples and renamed our other test assembly from Tests to SequenceTests for clarity.

…tication) under SequenceSDK and moved the authentication-related logic out of SequenceExamples and into Authentication.

…made it stop being a UIPage. Instead, created a UIPanel which inherrits from UIPage - this is used to create the LoginPanel and will be used for the WalletPanel as well

…UI tests in one test so we don't have to setup and teardown the scene each time - makes test suite faster.

…ng 'make test'

…generic object pool

…just Indexer.cs with the static methods extracted, no longer requiring chain id as a parameter, instead chain Id is provided in the constructor.

…utine

…in the pool; however, since the layout of the objects is managed by the grid layout group, anytime one of the elements is removed, the rest are shifted up and are also removed. Instead, we simply allow the object pool to grow as needed - this should still perform well on initial load, but has the potential to create slowdowns if the user has a bunch of NFTs to display.

… flow and the wallet flow. Running these separately (as opposed to all in one test) feels like a happy middleground to me in terms of test runtime vs clarity (to pinpoint the issue) when tests fail.

…ate on click listener for the buttons. The functionality is the same as before, except, now it is easier to customize (developers can simply disable the Open{PanelName} on click listener and replace with some other panel to open next)

…that the branding stays at the bottom of the page

…d when applying a new color scheme

…e prices

…is saved.

…lletWithFungible

…and re-open the wallet panel. Fixed some issues with the implementation

…nel within which all WalletPanel UIPages live

…se NetworkIcons - a scriptable object mapping Chains with Sprites - to get the appropriate sprite for the network. Added the network icons that are supported by the Sequence indexer

…. Refactoring.

…NFT ui elements and TransactionDetailBlocks

…kenDetail

…ates in reverse chronological order so we see the most recent transactions first

…ed on whether it is sent or received as designed in the Figma

… info pages

…oPage. Use NftElement to populate NftUIElement and update mock fetcher

…this class is designed to reuse the code needed for spawning TransactionDetailsBlocks. Reducing copy-pasta

…hTransactionDetailsBlock. Both NftInfoPage and TokenInfoPage are now InfoPages

…alletUIElement

…abstract classes to improve readability

…oring collection related info in the NftElement directory

…rify that the CollectionInfos were being mapped to NftElements appropriately by CollectionNftMapper

…ng arguments) to SequenceSampleUI for tests. This allows us to create tests that start on any panel - allowing us the flexibility to split up our tests further while keeping runtimes at a minimum

… that we can get more granual results from our test suite. This will also make the WalletPanel test suite more manageable as it scales and will remove the risk of approaching the max runtime for a given test.