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

[goals] [wip] Show info waiting #216

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Conversation

ejgallego
Copy link
Owner

We need to do a setTimeout here to avoid flicker.

@ejgallego ejgallego marked this pull request as draft January 22, 2023 20:10
ejgallego added a commit that referenced this pull request Jan 23, 2023
This is prerequisite to implement / fix effectively #143 and #216 for
example; the current Info View rendering using strings doesn't scale
anymore to the kind of DOM manipulation we need.

Why React? That was a careful choice for many reasons, in particular
seems like the best fit for our use case (so far); moreover, 3rd party
package support is the best.
@ejgallego ejgallego added this to the 0.1.4 milestone Jan 23, 2023
ejgallego added a commit that referenced this pull request Jan 23, 2023
This is prerequisite to implement / fix effectively #143 and #216 for
example; the current Info View rendering using strings doesn't scale
anymore to the kind of DOM manipulation we need.

Why React? That was a careful choice for many reasons, in particular
seems like the best fit for our use case (so far); moreover, 3rd party
package support is the best.
ejgallego added a commit that referenced this pull request Jan 23, 2023
This is prerequisite to implement / fix effectively #143 and #216 for
example; the current Info View rendering using strings doesn't scale
anymore to the kind of DOM manipulation we need.

Why React? That was a careful choice for many reasons, in particular
seems like the best fit for our use case (so far); moreover, 3rd party
package support is the best.
ejgallego added a commit that referenced this pull request Jan 24, 2023
This is prerequisite to implement / fix effectively #143 and #216 for
example; the current Info View rendering using strings doesn't scale
anymore to the kind of DOM manipulation we need.

Why React? That was a careful choice for many reasons, in particular
seems like the best fit for our use case (so far); moreover, 3rd party
package support is the best.
ejgallego added a commit that referenced this pull request Jan 25, 2023
This is prerequisite to implement / fix effectively #143 and #216 for
example; the current Info View rendering using strings doesn't scale
anymore to the kind of DOM manipulation we need.

Why React? That was a careful choice for many reasons, in particular
seems like the best fit for our use case (so far); moreover, 3rd party
package support is the best.
@ejgallego ejgallego modified the milestones: 0.1.4, 0.1.5 Jan 25, 2023
ejgallego added a commit that referenced this pull request Jan 27, 2023
This is prerequisite to implement / fix effectively #143 and #216 for
example; the current Info View rendering using strings doesn't scale
anymore to the kind of DOM manipulation we need.

Why React? That was a careful choice for many reasons, in particular
seems like the best fit for our use case (so far); moreover, 3rd party
package support is the best.
ejgallego added a commit that referenced this pull request Jan 27, 2023
This is prerequisite to implement / fix effectively #143 and #216 for
example; the current Info View rendering using strings doesn't scale
anymore to the kind of DOM manipulation we need.

Why React? That was a careful choice for many reasons, in particular
seems like the best fit for our use case (so far); moreover, 3rd party
package support is the best.
ejgallego added a commit that referenced this pull request Jan 27, 2023
This is prerequisite to implement / fix effectively #143 and #216 for
example; the current Info View rendering using strings doesn't scale
anymore to the kind of DOM manipulation we need.

Why React? That was a careful choice for many reasons, in particular
seems like the best fit for our use case (so far); moreover, 3rd party
package support is the best.
ejgallego added a commit that referenced this pull request Jan 27, 2023
This is prerequisite to implement / fix effectively #143 and #216 for
example; the current Info View rendering using strings doesn't scale
anymore to the kind of DOM manipulation we need.

Why React? That was a careful choice for many reasons, in particular
seems like the best fit for our use case (so far); moreover, 3rd party
package support is the best.
@ejgallego ejgallego modified the milestones: 0.1.5, 0.1.6 Feb 6, 2023
@ejgallego ejgallego modified the milestones: 0.1.6, 0.1.7 Feb 21, 2023
We need to do a setTimeout here to avoid flicker.
@ejgallego ejgallego modified the milestones: 0.1.7, 0.1.8 Jun 13, 2023
@ejgallego ejgallego modified the milestones: 0.1.8, 0.1.9 Jul 7, 2023
@ejgallego ejgallego modified the milestones: 0.1.9, 0.3.0 Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

1 participant