tqec: [Question] Visual frontend for BlockGraphs

Link to the recording

Include here the URL of the recording in which you have seen something that you cannot find in the current TQEC repository.

Description

There was a nice demo on a visual interface for manipulating BlockGraphs. Is there a section of the documentation that describes exactly how to deploy this frontend? Can it compile an arbitrary BlockGraph?

For tutorial purposes, I’m curious about the extent to which this can be an option for users who are turned off by SketchUp but still interested in visualizing BlockGraphs. It would be nice to have a description of the frontend in writing. It may already be in the docs, but I couldn’t find it immediately. Thank you!!

(Struggling to assign @angelaelisa to this)

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 15 (10 by maintainers)

Most upvoted comments

Yes, these can be thought of as frontends for different data structures. Angela’s interacts with BlockGraphs (3D) while Gian’s interacts with what we now refer to as layers (2D).

@KabirDubey I’ll upload it to https://github.com/tqec/flaskapp so it will be separated from Gian’s frontend 😃

Good luck with this! What is your paper about @angelaelisa ?

It’s a mix between Spanish bankruptcy proceedings and technology (how I’ve automatized the court proceeding to get better results and a sight to the future of the judicial field). It’s a piece to get the PhD next year 😃 Thanks for asking @purva-thakre

Very happy to agree fully with @purva-thakre

More generally, we really need some real €€€. We’re trying to manage a several-millions €€€ product with a kindergarten budget. 😸

One of the question we should ask ourselves is: do we still need such a frontend (the one we tried to build in the beginning)? Let’s talk about that in the next meeting, or here if you prefer. But let’s answer that question before trying to advertise anything.

When we refer to the frontend in this question, it is a different one from what’s in the frontend repo, right? https://github.com/tqec/frontend

One is by Angela and the other is by Gian.

Yes, these can be thought of as frontends for different data structures. Angela’s interacts with BlockGraphs (3D) while Gian’s interacts with what we now refer to as layers (2D).

Sorry, I have to present my master’s paper for my PhD studies on the 17th July, but don’t worry, the entire frontend will be published this month. I’ve also got several improvements in mind, and I’m sure that thanks to @jbolns (J, always the best, I owe him a huge debt 🍻 😃, I’ll be able to upload it to GitHub correctly. I’m also going to work hard on the legal side.

The frontend is able to compile any arbitrary BlockGraph supported in tqec and now you can visually build it or import/export (works with DAE and JSON files).

@KabirDubey and @nelimee please, assign it to me. This month —and specially August— are better months for me to work hard.

Yup, and as long as they’re not functionally redundant, it should be possible to wrap them both into a single user experience using the magic of Astro.

Wrapping both looks like a really nice idea for a next step @jbolns

Yes, these can be thought of as frontends for different data structures. Angela’s interacts with BlockGraphs (3D) while Gian’s interacts with what we now refer to as layers (2D).

Yup, and as long as they’re not functionally redundant, it should be possible to wrap them both into a single user experience using the magic of Astro.

If that’s what we decide when we get there, of course. Also possible to leave separate or pick best.

Sorry, I have to present my master’s paper for my PhD studies on the 17th July, but don’t worry, the entire frontend will be published this month. I’ve also got several improvements in mind, and I’m sure that thanks to @jbolns (J, always the best, I owe him a huge debt 🍻 😃, I’ll be able to upload it to GitHub correctly. I’m also going to work hard on the legal side.

The frontend is able to compile any arbitrary BlockGraph supported in tqec and now you can visually build it or import/export (works with DAE and JSON files).

@KabirDubey and @nelimee please, assign it to me. This month —and specially August— are better months for me to work hard.

Very nice, thank you @angelaelisa and best of luck on your masters.

(Struggling to assign @angelaelisa to this)

It’s a github thing to avoid spam. You can’t assign something to a user directly if they do not have write permissions. Angela will have to comment on the issue before you can assign it to her.