Must look at how we are reading the call stack in various crash situations.

I am starting off with goradd and followed the Quick Start guide

I have a import statement in web/login/login_form.go for "goradd-project/gen/bug/model" which is unresolved. How do I fix it?

I was using dep with go 1.12 the last time I made an app with golang and am new to the go modules. How do I resolve this?

Will need to be tested on a variety of browsers to see if it works.

Deal with hiding and showing/adding & removing of child controls with attached scripts. Coordinates with auto-drawn controls, dialogs and proxies too. Must be able to remove and add the attached or related scripts (possibly? Removal may not be necessary, but replacement, yes)

Hey @spekary

I think the shape is good but I also think that the industry is fast moving towards decoupling. Most apps do not render their own HTML a lot. They do the minimal stuff (just the case content) and then let JS do the work on the front end. Most sites that are going to be accompanied by an app these days and thus, they require the APIs and front-end to stay separated. Is there something you are working on towards that?

Optimistic locking should be used on records when a timestamp is present. This is complicated when doing joins, but should still be possible.

Webconnect is mostly implemented. Needs to be tied in to a watcher, which will require some kind of key-value database implementation. Should potentially implement the ability to query what other users are online.

The strategy will be to have special widgets that will receive date/time combinations in UTC, and then have javascript convert to a local timezone and display. We will need both a SPAN type object, and a column for tables. We will need equivalent versions, or options, to do no conversion and instead represent a local time in whatever the current time zone is.

We will need options for short and long dates and times, time only or date only, etc.

JS:
new Intl.DateTimeFormat(navigator.language, { dateStyle: 'short', timeStyle: 'short'}).format(date)
Leaving off dateStyle makes a time-only output. Similarly, leaving off timeStyle is date-only.

A Date/Time field would need to populate it this way, but also parse it too in javascript.

When Javascript is off, form.ChangeLocation will not work. We should have this function detect if
javascript is turned off, and instead call page.Redirect

See
https://blog.gopheracademy.com/advent-2016/exposing-go-on-the-internet/

This would be both a demo for future similar drivers, like a Redis or MongoDB driver, and also something useful for the examples website so that it could be easily implemented in a docker spin.

Since some browsers support date, time and datetime-local input types, perhaps the best thing here would be to simply allow these to be set as inputs, and then simply validate the human input. The validators could be used for other widgets to make it easier to implement other javascript date and time pickers.

Look again at the problem of constantly switching between drawing into a buffer and drawing into a string. This is also related to the fact that we build up tags by constantly wrapping them. Perhaps we can more efficiently do this by using buffers that are allocated at the beginning and end of the buffer, and then we draw in the middle, gradually adding to the beginning and end as we wrap and grow. We can look at the buffer implementation for hints.

Another possibility is to draw into a byte array rather than strings, since a byte array will not create allocations when it is passed between functions.

It is possible to have a variety of name collisions that we should check for. #42 is an example, but another one is if a many-many or reverse-reference uses the same name as a different colmn in the table.

Since we are only using WebSocket to deliver an update notification to the browser, we can use an EventSource instead. It has some advantages with regards to getting through proxies and is easier for load balancers, but it has some difficulties too:

• Need to occassionally ping to make sure its still up
  • See https://github.com/mattkrick/trebuchet-client/#browser-support for a pinger

Edge and IE browsers do not support this, but there is a polyfill available for just these two.

Serialization has some potential improvments:

1. We can store pointers to controls in other controls by implementing a scheme where we control how the controlRegistry is serialized, going bottom-up the hierarchy. Pointers to controls will then be serialized only as a controlID. Then, when we deserialize, we can know that those controls are available in the controlRegistry during the deseralization process.

2. We should detect that a control has the Serialize function, and not call it if its present. This is a little difficult using reflect, as the Method list returns all the methods, including methods from anonymous embedded structures. It may be possible to detect be looking at the Type->Method->Pkg structure and comparing to the package of the struct itself to see if they are in the same place.

I am getting this error page when trying to access the tutorial's "Code-generated objects" page:

Full Call path is this:

/usr/local/Cellar/go/1.15.2/libexec/src/runtime/panic.go line 212 in runtime.panicmem
/usr/local/Cellar/go/1.15.2/libexec/src/runtime/signal_unix.go line 720 in runtime.sigpanic
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/web/examples/gen/goradd/model/Person.base.go line 437 in github.com/goradd/goradd/web/examples/gen/goradd/model.newPersonBuilder
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/web/examples/gen/goradd/model/Person.go line 49 in github.com/goradd/goradd/web/examples/gen/goradd/model.queryPeople
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/web/examples/gen/goradd/model/Person.base.go line 404 in github.com/goradd/goradd/web/examples/gen/goradd/model.LoadPerson
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/web/examples/tutorial/orm/1-objects.tpl.go line 41 in github.com/goradd/goradd/web/examples/tutorial/orm.(*ObjectsPanel).DrawTemplate
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/pkg/page/control_base.go line 594 in github.com/goradd/goradd/pkg/page.(*ControlBase).DrawInnerHtml
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/pkg/page/control_base.go line 544 in github.com/goradd/goradd/pkg/page.(*ControlBase).DrawTag
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/pkg/page/control_base.go line 437 in github.com/goradd/goradd/pkg/page.(*ControlBase).Draw
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/pkg/page/control_base.go line 616 in github.com/goradd/goradd/pkg/page.(*ControlBase).DrawChildren
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/pkg/page/control_base.go line 603 in github.com/goradd/goradd/pkg/page.(*ControlBase).DrawInnerHtml
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/pkg/page/control_base.go line 544 in github.com/goradd/goradd/pkg/page.(*ControlBase).DrawTag
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/pkg/page/control_base.go line 437 in github.com/goradd/goradd/pkg/page.(*ControlBase).Draw
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/web/examples/tutorial/index.tpl.go line 104 in github.com/goradd/goradd/web/examples/tutorial.(*IndexForm).DrawTemplate
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/pkg/page/form_base.go line 152 in github.com/goradd/goradd/pkg/page.(*FormBase).Draw
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/pkg/page/page_template.tpl.go line 33 in github.com/goradd/goradd/pkg/page.PageTmpl
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/pkg/page/page.go line 167 in github.com/goradd/goradd/pkg/page.(*Page).Draw
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/pkg/page/page.go line 146 in github.com/goradd/goradd/pkg/page.(*Page).runPage
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/pkg/page/page_manager.go line 158 in github.com/goradd/goradd/pkg/page.(*PageManager).RunPage
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/web/app/app_base.go line 238 in github.com/goradd/goradd/web/app.(*Application).ServeHTTP
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/web/app/app_base.go line 348 in github.com/goradd/goradd/web/app.(*Application).ServeAppHandler.func1
/usr/local/Cellar/go/1.15.2/libexec/src/net/http/server.go line 2042 in net/http.HandlerFunc.ServeHTTP
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/web/app/app_base.go line 363 in github.com/goradd/goradd/web/app.(*Application).PutContextHandler.func1
/usr/local/Cellar/go/1.15.2/libexec/src/net/http/server.go line 2042 in net/http.HandlerFunc.ServeHTTP
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/pkg/session/scs.go line 49 in github.com/goradd/goradd/pkg/session.ScsManager.Use.func1
/usr/local/Cellar/go/1.15.2/libexec/src/net/http/server.go line 2042 in net/http.HandlerFunc.ServeHTTP
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/web/app/app_base.go line 318 in github.com/goradd/goradd/web/app.(*Application).HSTSHandler.func1
/usr/local/Cellar/go/1.15.2/libexec/src/net/http/server.go line 2042 in net/http.HandlerFunc.ServeHTTP
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/web/app/app_base.go line 396 in github.com/goradd/goradd/web/app.(*Application).BufferedOutputHandler.func1
/usr/local/Cellar/go/1.15.2/libexec/src/net/http/server.go line 2042 in net/http.HandlerFunc.ServeHTTP
/Users/vkaushal288/go/pkg/mod/github.com/goradd/[email protected]/web/app/app_base.go line 527 in github.com/goradd/goradd/web/app.(*Application).AccessLogHandler.func1
/usr/local/Cellar/go/1.15.2/libexec/src/net/http/server.go line 2042 in net/http.HandlerFunc.ServeHTTP
/usr/local/Cellar/go/1.15.2/libexec/src/net/http/server.go line 2417 in net/http.(*ServeMux).ServeHTTP
/usr/local/Cellar/go/1.15.2/libexec/src/net/http/server.go line 2843 in net/http.serverHandler.ServeHTTP
/usr/local/Cellar/go/1.15.2/libexec/src/net/http/server.go line 1925 in net/http.(*conn).serve
/usr/local/Cellar/go/1.15.2/libexec/src/runtime/asm_amd64.s line 1374 in runtime.goexit 

There is a potential problem with the pagestate. Some browsers let you duplicate a page, and so the pagestate will also be duplicated. Then we will have two pages with the same pagestate, and that could cause a collision. We need to implement an ajax counter along with the pagestate that will make sure each hit to the server is sequential. If we get something out of order, we know that there are two pages with the same pagestate. In that situation, we can just force one of the pages to reload, and so it will get a new pagestate, and there will no longer be a collision.

We should issue a warning if a plural is used as a table name. We automatically pluralize objects where needed, so table names should be singular.

Review https://www.owasp.org/index.php/XSS_%28Cross_Site_Scripting%29_Prevention_Cheat_Sheet

Way in the future, but instead of drawing a whole control's html, a control could instead be a combination of an html declaritive tag like a WebComponent, and a template that draws it. It could be an actual Polymer component, or something similar. This way, all templates get sent to the browser one time, and then they are called on through declarative statements or javascript calls.

Opera Mobile is surprisingly common in African countries. Make sure its supported by javascript library.

Look at other similar situations where we are conflating the calling of a jquery function with calling a javascript function

IE 10 is current minimum

Tell user to turn on javascript

Port the connector dialog from qcubed.

Reimplement an auto-complete like widget that is mobile friendly.

• Filtered single or multi-picker list
• Option to add a new one if the filter does not exist
• Autofill?
• Tag creator/picker
• Source of data should be uploaded and synchronized. Ajax data source can be problematic because of delays, and such a thing is really only necessary when dealing with a very large data set, in which case an autofill picker that you can add an item really has to deal with things differently, even purposefully delaying and putting up a dialog to ask to create a new value. The big problem comes when we are waiting for an ajax response and the user decides to save a form before the response comes back, or simply tab out before the response comes back. The response may not ever come back, so probably need to use validation to prevent the submission of the form.

Some widgets benefit from getting their data from a javascript datastore, and when data changes on the server, you update the datastore. In particular, scrolling widgets have their scroll location reset when the whole widget is drawn, and doing it with a linked datastore allows for it not to do that.

This will need ways to do code coverage directly accessing the control using the traditional Go testing framework, and also using the web driver

• Check for null and zero dates back and forth
• Check that various default date and time values are properly converted to internal objects. In other words, confirm that DATETIME times come from the database in UTC time.

This might have already been fixed with the database directive to preserve times.

Must make sure keys are also labeled auto-increment so that they will be treated as strings, in particular for type tables. This should be a warning generated during codegen if this is not true.

Make sure float and double correctly become float32 and float64 in go.

Should include OAuth support.

A couple of years ago with QCube for a bunch of projects. Since then, I never found anything that had a speed closer to it in terms of development. I think you were a big contributor to QCube and I recently discovered this repo and that QCubed is mostly dying.

These days, I'm mostly a full-stack dev. I work with backends build on nodejs with frontends done in react.

My question here is: When you started this project, did you thought about doing it with an API and a frontend? I mean, all the code generation would still be here for the front and back, but the backend and frontend would be split in two and you would have a modern SPA with a API on the back.

This would allow you to generate only the front or backend if necessary, plug other stuff to the api (example: mobile apps), have a frontend easy work it and with the possibility to had a huge amount of pre-existing modules from npm (for this I speak mostly for react and vue), and more that I won't list here because it's not important for the discussion.

In particular, the date, time and date-time pickers look interesting. We might make Gijgo core. But it requires jquery, so maybe not.

Some databases do not have timestamps, like SQL lite. We can use database comments to specify that a field is timestamped even if it does not have official support from the database maker. This would involve making sure that datetimes are saved in UTC. Would also need to add a variety of tests.

This is partly complete. Waiting for the testing framework for controls so that once we implement serialization, we can test it using control unit tests. This is done enough so that the architecture is in place.

This feature is not needed for single-server deployments.

Implement processes to join javascript and css files into one file, but have the various references to the original files point to the joined files in release builds.

This is not easy, and not sure its really important. jQuery is not very big, and is really useful.

Create basic yes/no, information input, and other basic dialogs, but make them customizable