On 11/26/19 12:12 PM, Alex Gacovski wrote:
Hello everyone,
I've started reading on how to develop a web application using Apache
Rivet. I've had a quick glance from
http://tcl.apache.org/rivet/manual3.1/ and it explains quite well how
rivet works. Pretty neat!
However I would like to know from devs that have worked on large scale
(eg FlightAware) projects what are the best practices in organising your
rivet templates and tcl scripts?
For example, do we have scripts that are called directly from the url
such as index.rvt or do we use a model view controller setup?
Thank you.
Alex.
Hi Alex
I don't get exactly what your concerns are about, if you could tell us
more about your perplexities maybe I wouldn't be able to give advice on
the design to adopt but I could help about some technical aspects
I'm the person who wrote perhaps the only piece of documentation where
somehow and clumsily an application basic scheme is proposed.
(https://tcl.apache.org/rivet/manual3.1/processing.html#idm583)
As a matter of fact I didn't want to give directions about application
development, I wanted to provide an example that could help to dissipate
some misconceptions about Rivet. In fact, somewhere on our web site is
still written that Rivet is like PHP but with Tcl and examples existed
to foster that view. That was the fundamental idea at the inception of
Rivet. Though maintaining compatibility with that approach, Rivet is now
something more general and flexible
To me a web application is a large, hopefully modular, Tcl script that
here and there calls, where needed, the command ::rivet::parse to print
HTML templates, not a series of rvt files stuffed with Tcl code and
calls to Tcl packages
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
