Open dovahcrow opened 3 years ago
@jnwang @peiwangdb What do you think of the second task? With the current implementation (ipywidget), you can only run the GUI in a jupyter notebook but no more. Also, it is hard to make the GUI dynamic (e.g. different input boxes for different pagination types).
However, if we use HTML, we can support scenarios like have a generator on our own website and make the GUI more dynamic. But certainly, it takes more time to implement.
I prefer the latter, what do you think?
I prefer the latter.
Summary
With the generator being merged, we can now start implementing a GUI.
UI-level Explanation Actions
UI-level Explanation
How to start the generator
There will be two ways to do so.
GeneratorUI()
. The UI will display in the output of the cell.UI workflow
UI Interface
The UI design: https://docs.google.com/document/d/1rEpXcKALgH7prwDjyplcYufulXqpQnkYQ4Th8Dn1elA/edit?usp=sharing
Implementation-level Explanation 🔗
While it is easier to come up with a frontend tech choice, it is non-trivial to find a backend choice due to different backend choices affects the usage pattern.
We need to choose one before proceed further.
Rational and Alternatives
Since we only have two APIs, it is not worth to invest time on more complex backend frameworks.
Prior Art
QuickType uses React and Typescript Postman uses React.
Future Possibilities
NA.
Implementation-level Actions
Additional Tasks
[x] This task is put into a correct pipeline (Development Backlog or In Progress).
[x] The label of this task is setting correctly.
[x] The issue is assigned to the correct person.
[x] The issue is linked to related Epic.
[ ] The documentation is changed accordingly.
[ ] Tests are added accordingly.