Hello,
thank you very much for your comments!
I didn't know before about the term "SPA"
(http://en.wikipedia.org/wiki/Single-page_application)
I guess a sign of being too "Conservative" (-: !
I am trying to re-implement a swing app with clojure script.
Before seeing Clojurescriptone I was only
Hello John,
ClojureScript One is an example of a single-page application. This means
that you get one page load from the
server and everything else happens in the browser without any further page
loads. The initial page that
is loaded is dynamically generated on the server. Any other updates to
On 8/10/12 5:21 AM, john wrote:
Hello,
I am just trying to understand the best practices in "ClojureScript One".
One thing that strikes me is that most html gets put (with the help of
macros using enlive) in the actual cljs page.
As someone who hasn't done web-applications for years I myself
I think it depends on the style of web site you are making.
On the more GMail style 'web app' end of the spectrum,
rendering/templating on the client side means you don't have to
inundate the server with AJAX requests (for example, if different
items are cached upon the initial connection). This wi
Enlive is abstractement conceive : if you put a remote on client you could
cache it...
To do that with the same abstract language , you have the awesome enfocus
[0] lib
with a sample app here [1], and for those clojururians interested in MVC [2]
Any way, there will be some *remote *to get tha
Hello,
I am just trying to understand the best practices in "ClojureScript One".
One thing that strikes me is that most html gets put (with the help of
macros using enlive) in the actual cljs page.
As someone who hasn't done web-applications for years I myself would have
created as much dynamic
