Numberguess example results in error about youi HOT 6 CLOSED

1.) Best not to use "run", you should use "re-start" as it will run the site in a separate process and not take over SBT.
2.) The path to the HTML is auto-derived by the value name in NumberGuessSite, so if you go to http://localhost:8080/numberGuessServer.html it should show up (a feature of StaticSite).
3.) I would recommend looking at "site" project and playing with the examples there.

Hyperscala hasn't received as much love regarding the open-source community as I would like. I use it for most of my production development for clients and have had very little time to polish it and write tutorials for others. If that's something you're interested in contributing to I would be very appreciative, and I'm sure the next person that comes along running into these types of problems would be too. :)

from youi.

BTW, I always hang out in #hyperscala in freenode.

from youi.

I can imagine that one of the reasons it has not received much attention is because of the mantra "it has to scale", "it has to be stateless", etc. Very unfortunate.

I think you're doing an excellent job here and that this framework is unique in the Scala ecosystem (I could go further and include the Java ecosystem as well, but then again some other projects try to do similar things, like Vaadin or Wicket; not in the same of type-safe all the way down, but of abstracting away the request/response/callback cycle).

Are you aware of the Seaside framework for (Pharo) Smalltalk? I used to code in that and I really loved it. In many regards Hyperscala reproduces that awesomeness in the Scala world.

I am also a big fan of Vaadin. Though I think your framework let's you have the cake and eat it too: easier to control the bare-metal (HTML/CSS) while being type-safe and abstracting away callbacks to the server.

I'll definitely look into it and, who knows, even contribute.

from youi.

Works now, thanks!

from youi.

By the way, I am the one "Sebastian" that once commented on your post regarding your approach to templates.

That is also a feature I find awesome and I think you got 100% right: the re-utilization of pure (template-DSL-free) HTML.

from youi.

Thanks for the praise. Yes, the whole "stateless" mantra is really hurting the server-side web development world. As far as scalability Hyperscala has the capability to scale to an even greater extent than most frameworks. For example, you can create a static page that is a singleton object, so one instance exists on the server and is able to render faster to the browser than even a static HTML file can. Beyond that I have a prototype that I've been working on that in fact can change the way web page resources are delivered to the client. My prototype allows large sites to load in a couple milliseconds that would take seconds in another system. I'll be rolling that out in the near future.

Regarding Vaadin, I used to use it myself and loved the abstraction, but I hate the instability of GWT and the lack of support to get to the bare metal. One of my long-term goals in Hyperscala is create a higher level abstraction to provide the same type of rich UI creation as Vaadin has, but built on the core of Hyperscala so nothing is lost. Unfortunately I'm just one person, so finding the time for such endeavors is difficult.

from youi.