I use framework loosely, cause i don't like big clunky ones such as struts .... but at the same time hard coding servlets wiring in the code isn't very pretty either.
Does Fan have such a system, to define how to process a request(call controller1, render with view2 etc...) and other framework type things?
Aso another thing i seem to always find handy is Form support (for non-ajax) that helps with remembering value/ showing messages and so on(ruby/groovy are good at that), does Fan provide such things ?
In Java i actually had written my own lightweight (no XML :)) framework(javaontracks) because i wanted features & simplicity and most frameworks where just too much ... so anyway does Fan provide those kind of features now, or will it ?
If there isn't i might "port" some of my stuff to fan (minus the cruft buildup over the years) since i seem to always need those things.
Note: I've seen the webapp stuff but it seems pretty "bare", also is there any code /example of an actual "real" webapp written in fan.
Thanks.
andyMon 29 Jun 2009
What we have today is two layers. The web pod is the low-level interface intended to sit right above web servers and enable interopability b/w servers. However, if you look at the API, you'll see its much more useful than the Servlet API, and includes most everything you would expect to see there.
The webapp pod would be considered Fan's built-in web framework. Its intentionally light-weight at the moment as we feel out whats needed and whats not, but we've added next to nothing to it for Bespin, so while there will be changes I'm sure with the FWT port and compilerJs, its probably not far off the mark.
If there are specific features you're interested in, voice them here, and we can discuss rolling those into the standard framework.
Sounds good. I think that kind of features probably shouldn't be in the "core api" anyhow. I much like the fact that the Fan API is very lightweight despite providing many features.
I guess i need to play with it some more to figure out what it does and doesnt do.
tcolar Mon 29 Jun 2009
Is there such as thing as a Fan "framework".
I use framework loosely, cause i don't like big clunky ones such as struts .... but at the same time hard coding servlets wiring in the code isn't very pretty either.
Does Fan have such a system, to define how to process a request(call controller1, render with view2 etc...) and other framework type things?
Aso another thing i seem to always find handy is Form support (for non-ajax) that helps with remembering value/ showing messages and so on(ruby/groovy are good at that), does Fan provide such things ?
In Java i actually had written my own lightweight (no XML :)) framework(javaontracks) because i wanted features & simplicity and most frameworks where just too much ... so anyway does Fan provide those kind of features now, or will it ?
If there isn't i might "port" some of my stuff to fan (minus the cruft buildup over the years) since i seem to always need those things.
Note: I've seen the webapp stuff but it seems pretty "bare", also is there any code /example of an actual "real" webapp written in fan.
Thanks.
andy Mon 29 Jun 2009
What we have today is two layers. The web pod is the low-level interface intended to sit right above web servers and enable interopability b/w servers. However, if you look at the API, you'll see its much more useful than the Servlet API, and includes most everything you would expect to see there.
The webapp pod would be considered Fan's built-in web framework. Its intentionally light-weight at the moment as we feel out whats needed and whats not, but we've added next to nothing to it for Bespin, so while there will be changes I'm sure with the FWT port and compilerJs, its probably not far off the mark.
If there are specific features you're interested in, voice them here, and we can discuss rolling those into the standard framework.
EDIT: Also take a look at webWidget and webappClient.
tcolar Mon 29 Jun 2009
Sounds good. I think that kind of features probably shouldn't be in the "core api" anyhow. I much like the fact that the Fan API is very lightweight despite providing many features.
I guess i need to play with it some more to figure out what it does and doesnt do.