Should be an in place update of tales 0.6, except for some breaking changes in fanbatis listed here
brianMon 2 Jul 2012
That sounds pretty awesome!
What are you doing exactly for https and websockets?
DanielFathMon 2 Jul 2012
I second that. That is awesome. Brian there is source https://bitbucket.org/ksat/tales/ so it's probably easy to see. My guess that there is a Java library for that.
Speaking of Tales, I have to wonder kaushik did you have a look at http://meteor.com/? They are moving in an interesting direction. Something like that would work well IMO with Tales.
Basically what Meteor does is reload browser content for you?
go4Tue 3 Jul 2012
If you add some descriptions on Bitbucket, It will be more searchable.
go4Tue 3 Jul 2012
Both Spectre and Tales try to build own web server by NOI. IMHO, The web container and application are coupled. I hope they have a unified Weblet interface, like the web pod described.
kaushikTue 3 Jul 2012
@Brian, Thanks. Tales defaults to using netty from V0.6 for all these.
@Daniel, thanks!. meteor is awesome. I checked it out (but not much) just after it was launched. I think they do more than "reload the browser", in that the templates are themselves aware of the models they are tied to and reloads when the model changes (I could be wrong though). I'd love any thoughts on how some ideas from these other new frameworks can be bought in. A few even mailed me on using(or porting) backbone in Fantom. That'll be awesome when/if it's done.
But overall, I have mixed feelings on single page apps. I personally prefer developing apps that are a mix of multiple pages and each page having just the right client side code. Too much client code leads to the other problem of having to debug things that arises due to client side state. One thing that tales would definitely add though, is better support for pushstate-ajax. Tales already has things like cut-and-send and this will not be much work to add.
@go4, Tales does have interfaces decoupled from the server. It can already run on netty, wisp or any servlet containers - Though i must admit that making the app work on servlet containers(especially app engine) is not as straightforward as I want it to be. This is one of things planned before 0.8.
go4Tue 3 Jul 2012
It will be nice run on servlet containers. Great work.
tcolarTue 3 Jul 2012
I'm using tales with backbone.js and JQuery UI right now, for a"highly interactive" UI. Works very well and it's quite flexible.
kaushik Sun 1 Jul 2012
Happy to announce Tales 0.7 with
Should be an in place update of tales 0.6, except for some breaking changes in fanbatis listed here
brian Mon 2 Jul 2012
That sounds pretty awesome!
What are you doing exactly for https and websockets?
DanielFath Mon 2 Jul 2012
I second that. That is awesome. Brian there is source https://bitbucket.org/ksat/tales/ so it's probably easy to see. My guess that there is a Java library for that.
Speaking of Tales, I have to wonder kaushik did you have a look at http://meteor.com/? They are moving in an interesting direction. Something like that would work well IMO with Tales.
Basically what Meteor does is reload browser content for you?
go4 Tue 3 Jul 2012
If you add some descriptions on Bitbucket, It will be more searchable.
go4 Tue 3 Jul 2012
Both Spectre and Tales try to build own web server by NOI. IMHO, The web container and application are coupled. I hope they have a unified Weblet interface, like the web pod described.
kaushik Tue 3 Jul 2012
@Brian, Thanks. Tales defaults to using netty from V0.6 for all these.
@Daniel, thanks!. meteor is awesome. I checked it out (but not much) just after it was launched. I think they do more than "reload the browser", in that the templates are themselves aware of the models they are tied to and reloads when the model changes (I could be wrong though). I'd love any thoughts on how some ideas from these other new frameworks can be bought in. A few even mailed me on using(or porting) backbone in Fantom. That'll be awesome when/if it's done.
But overall, I have mixed feelings on single page apps. I personally prefer developing apps that are a mix of multiple pages and each page having just the right client side code. Too much client code leads to the other problem of having to debug things that arises due to client side state. One thing that tales would definitely add though, is better support for pushstate-ajax. Tales already has things like cut-and-send and this will not be much work to add.
@go4, Tales does have interfaces decoupled from the server. It can already run on netty, wisp or any servlet containers - Though i must admit that making the app work on servlet containers(especially app engine) is not as straightforward as I want it to be. This is one of things planned before 0.8.
go4 Tue 3 Jul 2012
It will be nice run on servlet containers. Great work.
tcolar Tue 3 Jul 2012
I'm using tales with backbone.js and JQuery UI right now, for a"highly interactive" UI. Works very well and it's quite flexible.