[This message is a resend, because the first attempt hasn't gone
through, after several hours.]
You can also do HTML 5 (possibly Offline), together with whatever JS
libraries you want for UX and for cross-browser differences (especially
for client-side storage of larger data), and have it talk with your
HTTPS Web server that's implemented in Racket using XML or JSON.
Your webservice XML/JSON messages will normally be in terms of the
model, nothing view/controller-specific. Which is good for many
reasons, though sometimes you can make a good argument for cheating, but
be very careful with cheating, because you will tend to pay for it for a
long time.
Depending on your app, you might also find (as I did, with a complicated
data-driven app), that it can help to have Racket generate much of the
static client-side HTML/JS/CSS.
This can let you do things that clerical-worker-oriented frameworks do
not, and more efficiently. It does mean, however, that you need
non-clerical-workers to do much of the work, unlike many Web frameworks.
--
You received this message because you are subscribed to the Google Groups "Racket
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
