Hi,

Following up on issue #243

I am working on a project (it is commercial and closed source), that is using Vugu. We are at this point 100% Go based, backing onto a Postgres DB. Using Vugu has given us a substantial amount of code reuse in the browser which would have been difficult to achieve using any other approach.

Our use of Vugu will start to grow over the coming months as we begin to connect the UI to the back end.

We are interested in getting Vugu to a state where we can safely put Vugu into production. The project has now reached the point where we need the understand the effort required achieve this..

At this point we are not looking at new features in Vugu. We want stability.

I think we are more likely to want to focus on areas such as

1. Advice, examples etc on putting Vugu into production beyond what is already in the documentation. It looks like the simplehttp package that the docs suggest is calling the Go tool chain, which we wouldn't do in production for example. So we need to workout and document an alternative approach.
2. At the minute our UI is based around a simple FSM rather than the wiring/routing approach suggested in the documentation. As the number of controls in the page grows the FMS becomes more complex (more states), so it is not clear if (or how) we switch to the component wiring approach. So advice and documentation would be helpful.
3. General housekeeping e.g. closing any outstanding defects, bumping any dependencies to the latest versions so we pick up any security updates. Likewise umping the minimum version of the Go tool chain itself

The one "feature" we would be interesting in seeing is the component library mentioned in the Vugu Readme from November 2020. Without having nay knowledge of what this includes we can't say it it would help us or not. Some visibility of this package would be appreciated.

I appreciate other members of the community may want other features from a v1.0 release. The above list is simply our starting point and not a firm list for a v1.0 feature set. We want to hear what others in the community want.

Can we please use this issue to discuss what work would be required to move Vugu to a v1.0 release and what features, bug fixes etc should be included for everyone's benefit.

Many thanks

Owen