Re: [Rife-users] Excel spreadsheets as responses
Hi Geert, I actually have that pdf (can't remember how i got it though) together with 4 books from the eclipse series; and that includes the faq and building commercial-quality plugins... and a couple others on SWT... i just have to re-read relevant parts... plus get into the code as the platform is a moving target :) and the books were mostly written to the 3.0 API. it would be good to get together with all those interested on the #rife chan and get something started -- eokyere On 12/2/05, Geert Bevin <[EMAIL PROTECTED]> wrote: > Hi Emmanuel, > > > i am almost using rife almost on a daily basis now, so I also started > > looking at adding support for it in eclipse (which is my primary ide). > > i dabbled in an eclipse plugin in the past, but i have to relearn most > > parts of the platform to do anything signifact; what i've been doing > > is looking at the code for the ant plugin, to give me some direction. > > I received these from someone too as a documentation resource: > http://safariexamples.informit.com/0321268385/index.html > > If you're interested I can also send you a PDF of a free early > version of the Contributing To Eclipse book. This is not an illegal > copy of the book, but a version from before it was published. > > > Raoul, Geert, if you guys are serious about this one, i'll be willing > > to put sometime in; developing an eclipse plugin for rife sure sounds > > like a lot of fun. > > I sure want to help out! Though my main focus is to create an X- > develop plugin, creating one for Eclipse is very important and I will > give a hand to do so whenever I can. There is a student on our IRC > channel that is planning on creating a visual Eclipse plugin using > GEF to graphically edit your site-structure. It would be a good idea > to get him on the mailing list. > > Best regards, > > Geert > > > -- > Geert Bevin Uwyn bvba > "Use what you need" Avenue de Scailmont 34 > http://www.uwyn.com 7170 Manage > gbevin[remove] at uwyn dot comTel +32 64 84 80 03 > > PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9 > Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net > > > > ___ > Rife-users mailing list > Rife-users@uwyn.com > http://www.uwyn.com/mailman/listinfo/rife-users > ___ Rife-users mailing list Rife-users@uwyn.com http://www.uwyn.com/mailman/listinfo/rife-users
Re: [Rife-users] Excel spreadsheets as responses
Hi Emmanuel, i am almost using rife almost on a daily basis now, so I also started looking at adding support for it in eclipse (which is my primary ide). i dabbled in an eclipse plugin in the past, but i have to relearn most parts of the platform to do anything signifact; what i've been doing is looking at the code for the ant plugin, to give me some direction. I received these from someone too as a documentation resource: http://safariexamples.informit.com/0321268385/index.html If you're interested I can also send you a PDF of a free early version of the Contributing To Eclipse book. This is not an illegal copy of the book, but a version from before it was published. Raoul, Geert, if you guys are serious about this one, i'll be willing to put sometime in; developing an eclipse plugin for rife sure sounds like a lot of fun. I sure want to help out! Though my main focus is to create an X- develop plugin, creating one for Eclipse is very important and I will give a hand to do so whenever I can. There is a student on our IRC channel that is planning on creating a visual Eclipse plugin using GEF to graphically edit your site-structure. It would be a good idea to get him on the mailing list. Best regards, Geert -- Geert Bevin Uwyn bvba "Use what you need" Avenue de Scailmont 34 http://www.uwyn.com 7170 Manage gbevin[remove] at uwyn dot comTel +32 64 84 80 03 PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9 Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net ___ Rife-users mailing list Rife-users@uwyn.com http://www.uwyn.com/mailman/listinfo/rife-users
Re: [Rife-users] Excel spreadsheets as responses
i am almost using rife almost on a daily basis now, so I also started looking at adding support for it in eclipse (which is my primary ide). i dabbled in an eclipse plugin in the past, but i have to relearn most parts of the platform to do anything signifact; what i've been doing is looking at the code for the ant plugin, to give me some direction. Raoul, Geert, if you guys are serious about this one, i'll be willing to put sometime in; developing an eclipse plugin for rife sure sounds like a lot of fun. -- eokyere On 12/2/05, Geert Bevin <[EMAIL PROTECTED]> wrote: > >> We don't have this, but I plan on doing a lot more Spring integration > >> after the next release. I suppose this is part of their AOP support. > >> The closest that we currently have is something similar as Spring's > >> transactional template methods: http://rifers.org/wiki/display/RIFE/ > >> Chainable+transactions > > > > Whatever you do, please leave RIFE as a monolithic framework and do > > not > > start branching all over the place. RIFE has convinced me by its > > simplicity -- one JAR, one declaration in web.xml and that is it. > > Yes, these would be optional integrations for people that do already > use Spring and would like to use RIFE alongside their current > codebase. RIFE will always be one jar. > > >> Actually I was less talking about the syntax, but more about a > >> centralized point of declaration. If your entire data and logic > >> flow is > >> specified in a site-structure, you almost instantly have an > >> overview of > >> how your application behaves and which components are accessible. > >> Without this centralized declaration you have to search through your > >> entire code code-base to find where your area of interest is > >> located. > > > > Geert, I am not trying to be negative, but when I first looked at > > RIFE, > > it reminded me of FuseActions (ColdFusion anyone?). Except that > > FuseActions was a pattern more than anything else. Still it has worked > > for ages and still works. > > I consider that a good thing :-) > > Any familiarity makes it easier for people to adopt RIFE. > > >> Coool! I'm actively looking into making X-develop more > >> intelligent for > >> RIFE and provide code hyper-linking in between files. I just spent 2 > >> weeks with Eclipse exclusively to try it out thoroughly and I > >> switched > >> back to X-develop today. > > > > I tried X-Develop, but did not like it. But then, I don't like Eclipse > > or IDEA either. I think the choice of IDE is very personal and > > there is > > no real good/bad. > > +1 > > -- > Geert Bevin Uwyn bvba > "Use what you need" Avenue de Scailmont 34 > http://www.uwyn.com 7170 Manage, Belgium > gbevin[remove] at uwyn dot comTel +32 64 84 80 03 > > PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9 > Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net > > > ___ > Rife-users mailing list > Rife-users@uwyn.com > http://www.uwyn.com/mailman/listinfo/rife-users > ___ Rife-users mailing list Rife-users@uwyn.com http://www.uwyn.com/mailman/listinfo/rife-users
Re: [Rife-users] Excel spreadsheets as responses
We don't have this, but I plan on doing a lot more Spring integration after the next release. I suppose this is part of their AOP support. The closest that we currently have is something similar as Spring's transactional template methods: http://rifers.org/wiki/display/RIFE/ Chainable+transactions Whatever you do, please leave RIFE as a monolithic framework and do not start branching all over the place. RIFE has convinced me by its simplicity -- one JAR, one declaration in web.xml and that is it. Yes, these would be optional integrations for people that do already use Spring and would like to use RIFE alongside their current codebase. RIFE will always be one jar. Actually I was less talking about the syntax, but more about a centralized point of declaration. If your entire data and logic flow is specified in a site-structure, you almost instantly have an overview of how your application behaves and which components are accessible. Without this centralized declaration you have to search through your entire code code-base to find where your area of interest is located. Geert, I am not trying to be negative, but when I first looked at RIFE, it reminded me of FuseActions (ColdFusion anyone?). Except that FuseActions was a pattern more than anything else. Still it has worked for ages and still works. I consider that a good thing :-) Any familiarity makes it easier for people to adopt RIFE. Coool! I'm actively looking into making X-develop more intelligent for RIFE and provide code hyper-linking in between files. I just spent 2 weeks with Eclipse exclusively to try it out thoroughly and I switched back to X-develop today. I tried X-Develop, but did not like it. But then, I don't like Eclipse or IDEA either. I think the choice of IDE is very personal and there is no real good/bad. +1 -- Geert Bevin Uwyn bvba "Use what you need" Avenue de Scailmont 34 http://www.uwyn.com 7170 Manage, Belgium gbevin[remove] at uwyn dot comTel +32 64 84 80 03 PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9 Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net ___ Rife-users mailing list Rife-users@uwyn.com http://www.uwyn.com/mailman/listinfo/rife-users
Re: [Rife-users] Excel spreadsheets as responses
Geert Bevin wrote: > Hi John, > >> I have actually grown to loathe Hibernate, and would be keen to avoid >> using it again - most of the debugging time on the last couple of >> systems was on obscure Hibernate issues, for which the Hibernate >> forums were pretty well useless, as all answers from the Hibernate >> guys tended to be extremely terse 'RTFM' style ones. (Maybe if their >> error messages were not so John, welcome to the club! I gave up on Hibernate in the 2.x days because of the attitude on the forums. I remember struggling for a long time trying to find an answer about support for interfaces and abstract classes without actually getting a straightforward answer. Since then, I've moved to JDO, JPOX to be more specific. Sometimes there is the terse "RTFM" style answers, but this is understandable since the development team is quite small. At least, JPOX follows the JDO specs and if you cannot get answers on the forums, there are still other JDO implementers from whom you can seek help. (I have actually written a tutorial on integrating JPOX with NetBeans.) > RIFE's database layer tries to do as little magic as possible, so a lot > of things are very intuitive. It does a lot less than Hibernate though, > we for instance don't have our own query language but use object > oriented query builders instead (they handle the DB SQL syntax > abstraction). There's also no support for table inheritance or > automatic population of collection properties. We do plan on adding > these in the future. [snipped] > We don't have this, but I plan on doing a lot more Spring integration > after the next release. I suppose this is part of their AOP support. > The closest that we currently have is something similar as Spring's > transactional template methods: http://rifers.org/wiki/display/RIFE/ > Chainable+transactions Whatever you do, please leave RIFE as a monolithic framework and do not start branching all over the place. RIFE has convinced me by its simplicity -- one JAR, one declaration in web.xml and that is it. >>> The thing I like most about Wicket is also the biggest flaw imho: >>> you do everything in Java in a similar fashion as Swing. During >>> the coding this is certainly very nice and you can write everything >>> here and now. However, when looking at code that someone else Same opinion here. Web site/application development should be a shared profession. Programmers write the processing code, designers create templates, and deployers write the XML declarations. >> While I haven't joined in with the mad stampede away from XML which >> seems to have been triggered by Ruby On Rails, I would say that >> having to read Java sources to work out how things relate doesn't >> particularly bother me. In common with many Java developers, I >> suspect, I find well-written code rather easier to read than XML. > > > Actually I was less talking about the syntax, but more about a > centralized point of declaration. If your entire data and logic flow is > specified in a site-structure, you almost instantly have an overview of > how your application behaves and which components are accessible. > Without this centralized declaration you have to search through your > entire code code-base to find where your area of interest is located. Geert, I am not trying to be negative, but when I first looked at RIFE, it reminded me of FuseActions (ColdFusion anyone?). Except that FuseActions was a pattern more than anything else. Still it has worked for ages and still works. > Coool! I'm actively looking into making X-develop more intelligent for > RIFE and provide code hyper-linking in between files. I just spent 2 > weeks with Eclipse exclusively to try it out thoroughly and I switched > back to X-develop today. I tried X-Develop, but did not like it. But then, I don't like Eclipse or IDEA either. I think the choice of IDE is very personal and there is no real good/bad. Eddy ___ Rife-users mailing list Rife-users@uwyn.com http://www.uwyn.com/mailman/listinfo/rife-users
Re: [Rife-users] Excel spreadsheets as responses
RIFE's database layer tries to do as little magic as possible, so a lot of things are very intuitive. It does a lot less than Hibernate though, we for instance don't have our own query language but use object oriented query builders instead (they handle the DB SQL syntax abstraction). There's also no support for table inheritance or automatic population of collection properties. We do plan on adding these in the future. I imagine, though, that it does everything you have needed it to do in real-world systems over the last 4 years. Yup. Coool! I'm actively looking into making X-develop more intelligent for RIFE and provide code hyper-linking in between files. I just spent 2 weeks with Eclipse exclusively to try it out thoroughly and I switched back to X-develop today. How did you like Eclipse by comparison? I like the fact that you can provide virtually everything as a plugin, however it's very slow. I also miss a lot of X-develop's features like: uncluttered UI, instant project-wide error checking, one key-press to browse through all the errors, debug console expression execution, back-in-time debugging, automatic reordering of MRU editor tabs. -- Geert Bevin Uwyn bvba "Use what you need" Avenue de Scailmont 34 http://www.uwyn.com 7170 Manage, Belgium gbevin[remove] at uwyn dot comTel +32 64 84 80 03 PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9 Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net ___ Rife-users mailing list Rife-users@uwyn.com http://www.uwyn.com/mailman/listinfo/rife-users
Re: [Rife-users] Excel spreadsheets as responses
Hi John, I have actually grown to loathe Hibernate, and would be keen to avoid using it again - most of the debugging time on the last couple of systems was on obscure Hibernate issues, for which the Hibernate forums were pretty well useless, as all answers from the Hibernate guys tended to be extremely terse 'RTFM' style ones. (Maybe if their error messages were not so RIFE's database layer tries to do as little magic as possible, so a lot of things are very intuitive. It does a lot less than Hibernate though, we for instance don't have our own query language but use object oriented query builders instead (they handle the DB SQL syntax abstraction). There's also no support for table inheritance or automatic population of collection properties. We do plan on adding these in the future. obscure and/or misleading, people wouldn't keep asking about them?). Spring makes life with Hibernate a lot more pleasant, and one feature of that would be something I would really miss if it were not possible in RIFE. Namely, the declarative transaction management - e.g., you tell Spring (via the XML config file) to wrap all methods beginning with 'insert' or 'update' in your Products DAO bean in a transaction, and that's all you have to do. What does RIFE do in this area? We don't have this, but I plan on doing a lot more Spring integration after the next release. I suppose this is part of their AOP support. The closest that we currently have is something similar as Spring's transactional template methods: http://rifers.org/wiki/display/RIFE/ Chainable+transactions Maybe it would be possible to use Spring AOP to provide something similar for RIFE's chainable transactions. While I only briefly glanced at SpringMVC, I wouldn't recommend it. It seem too difficult and not very intuitive. Seems nice by comparison with Struts! No comment ;-) Comparing RIFE with Wicket is difficult since you're comparing totally different approaches. What I don't like about Wicket is that you're forced to think of everything as being a component, while many web functionalities really are simple request/response actions. RIFE combines both of these and make any action handler a reusable component (http://rifers.org/about). I see your point. It really is very powerful since it's possible to have entire sites as one packaged component and embed them inside your templates as portlet-like apps. You can use the same components as top-level trails and link them into your site's flow. The thing I like most about Wicket is also the biggest flaw imho: you do everything in Java in a similar fashion as Swing. During the coding this is certainly very nice and you can write everything here and now. However, when looking at code that someone else wrote, you have to read all the sources to get an idea of how everything relates. There's no single overview that summarizes the logic flow and data flow for you. It's thus very difficult to gets a complete view of how your web application interacts with the outside world (ie. the RESTful API of your application). Note that RIFE doesn't force you to use XML for your declarations, you can do them in Java too if you want (or Groovy or Janino: http://rifers.org/wiki/display/ RIFE/Site +structure+and+element+declaration+without+XML). While I haven't joined in with the mad stampede away from XML which seems to have been triggered by Ruby On Rails, I would say that having to read Java sources to work out how things relate doesn't particularly bother me. In common with many Java developers, I suspect, I find well-written code rather easier to read than XML. Actually I was less talking about the syntax, but more about a centralized point of declaration. If your entire data and logic flow is specified in a site-structure, you almost instantly have an overview of how your application behaves and which components are accessible. Without this centralized declaration you have to search through your entire code code-base to find where your area of interest is located. Even the leaps from one class to another are not really a problem if you have a good IDE (which I do, being the 'other user' of that extraordinarily well-kept secret, X-develop, which I know you favour - that makes two of us now :-) ). Coool! I'm actively looking into making X-develop more intelligent for RIFE and provide code hyper-linking in between files. I just spent 2 weeks with Eclipse exclusively to try it out thoroughly and I switched back to X-develop today. Best regards, Geert -- Geert Bevin Uwyn bvba "Use what you need" Avenue de Scailmont 34 http://www.uwyn.com 7170 Manage, Belgium gbevin[remove] at uwyn dot comTel +32 64 84 80 03 PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9 Public PGP key : available at server
Re: [Rife-users] Excel spreadsheets as responses
Geert, Excellent, thorough answer, thanks. You can using Spring together with RIFE, and Hibernate also. We actually advocate using Spring as an IoC reference factory since we didn't bother writing our own, we only focused on the injection part. You will however miss out on some of the nice integrations of our persistence layer when you use Hibernate. However, nothing prevents you from using Hibernate for certain things and use our ContentQueryManager when you want easy integration with our content management framework, for instance (http://rifers.org/wiki/display/ RIFE/Content+management+framework). I have actually grown to loathe Hibernate, and would be keen to avoid using it again - most of the debugging time on the last couple of systems was on obscure Hibernate issues, for which the Hibernate forums were pretty well useless, as all answers from the Hibernate guys tended to be extremely terse 'RTFM' style ones. (Maybe if their error messages were not so obscure and/or misleading, people wouldn't keep asking about them?). Spring makes life with Hibernate a lot more pleasant, and one feature of that would be something I would really miss if it were not possible in RIFE. Namely, the declarative transaction management - e.g., you tell Spring (via the XML config file) to wrap all methods beginning with 'insert' or 'update' in your Products DAO bean in a transaction, and that's all you have to do. What does RIFE do in this area? While I only briefly glanced at SpringMVC, I wouldn't recommend it. It seem too difficult and not very intuitive. Seems nice by comparison with Struts! Comparing RIFE with Wicket is difficult since you're comparing totally different approaches. What I don't like about Wicket is that you're forced to think of everything as being a component, while many web functionalities really are simple request/response actions. RIFE combines both of these and make any action handler a reusable component (http://rifers.org/about). I see your point. The thing I like most about Wicket is also the biggest flaw imho: you do everything in Java in a similar fashion as Swing. During the coding this is certainly very nice and you can write everything here and now. However, when looking at code that someone else wrote, you have to read all the sources to get an idea of how everything relates. There's no single overview that summarizes the logic flow and data flow for you. It's thus very difficult to gets a complete view of how your web application interacts with the outside world (ie. the RESTful API of your application). Note that RIFE doesn't force you to use XML for your declarations, you can do them in Java too if you want (or Groovy or Janino: http://rifers.org/wiki/display/ RIFE/Site+structure+and+element+declaration+without+XML). While I haven't joined in with the mad stampede away from XML which seems to have been triggered by Ruby On Rails, I would say that having to read Java sources to work out how things relate doesn't particularly bother me. In common with many Java developers, I suspect, I find well-written code rather easier to read than XML. Even the leaps from one class to another are not really a problem if you have a good IDE (which I do, being the 'other user' of that extraordinarily well-kept secret, X-develop, which I know you favour - that makes two of us now :-) ). Having said that, I think it's great that you can use XML, Groovy or Java for RIFE. I also suggest that you read over a mail that I wrote when someone asked about a WebWork/RIFE comparison, it contains a number of points that I didn't repeat in this mail: http://www.uwyn.com/pipermail/rife- users/2004-September/000643.html I read this, thanks. It was also very useful. John -- == John Moore - Norwich, UK - [EMAIL PROTECTED] == ___ Rife-users mailing list Rife-users@uwyn.com http://www.uwyn.com/mailman/listinfo/rife-users
Re: [Rife-users] Excel spreadsheets as responses
Hi John, 1. Capitalise on what I already know, but maybe dispense with Struts (using Spring MVC instead). I.e., go with Spring MVC, Spring, Hibernate. 2. Go with Wicket, which looks interesting. 3. Go with RIFE. Which do you recommend? :-) Hehe, trick question ;-) We do everything with RIFE so I would recommended that of course. However, Wicket is a fine choice too. You can using Spring together with RIFE, and Hibernate also. We actually advocate using Spring as an IoC reference factory since we didn't bother writing our own, we only focused on the injection part. You will however miss out on some of the nice integrations of our persistence layer when you use Hibernate. However, nothing prevents you from using Hibernate for certain things and use our ContentQueryManager when you want easy integration with our content management framework, for instance (http://rifers.org/wiki/display/ RIFE/Content+management+framework). While I only briefly glanced at SpringMVC, I wouldn't recommend it. It seem too difficult and not very intuitive. When I spoke to some Spring guys they actually said that it was a framework to build other frameworks with. Seriously, I'd be interested to hear your impressions of Wicket and how it compares with Rife (or more accurately, part of Rife). Comparing RIFE with Wicket is difficult since you're comparing totally different approaches. What I don't like about Wicket is that you're forced to think of everything as being a component, while many web functionalities really are simple request/response actions. RIFE combines both of these and make any action handler a reusable component (http://rifers.org/about). The thing I like most about Wicket is also the biggest flaw imho: you do everything in Java in a similar fashion as Swing. During the coding this is certainly very nice and you can write everything here and now. However, when looking at code that someone else wrote, you have to read all the sources to get an idea of how everything relates. There's no single overview that summarizes the logic flow and data flow for you. It's thus very difficult to gets a complete view of how your web application interacts with the outside world (ie. the RESTful API of your application). Note that RIFE doesn't force you to use XML for your declarations, you can do them in Java too if you want (or Groovy or Janino: http://rifers.org/wiki/display/ RIFE/Site+structure+and+element+declaration+without+XML). Some approaches are the same: we both allow reusable component libraries to be packaged as jars and we also both value logicless templates. Wicket's template engine is however totally geared towards (X)HTML, while we use it for anything text related (email messages, XML generation, SQL, ...) (http://rifers.org/wiki/display/RIFE/ Bidirectional+template+engine). Something you also don't get with Wicket (nor any other Java web framework that I know of) is our constraints feature. You declare rich meta-data on your beans and they are automatically picked up by all the other layers in the framework. This provides you with a single point of declaration that propagates consistently through your entire application (http://rifers.org/wiki/display/RIFE/Constraints). I also suggest that you read over a mail that I wrote when someone asked about a WebWork/RIFE comparison, it contains a number of points that I didn't repeat in this mail: http://www.uwyn.com/pipermail/rife- users/2004-September/000643.html I hope this will make it easier for you to make a choice. Best regards, Geert -- Geert Bevin Uwyn bvba "Use what you need" Avenue de Scailmont 34 http://www.uwyn.com 7170 Manage, Belgium gbevin[remove] at uwyn dot comTel +32 64 84 80 03 PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9 Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net ___ Rife-users mailing list Rife-users@uwyn.com http://www.uwyn.com/mailman/listinfo/rife-users
Re: [Rife-users] Excel spreadsheets as responses
Hi John, sure! We do that all the time, we generate Excel spreadsheets, PDFs, images, ... on the fly or stream them from the db. For Excel, we use http://www.andykhan.com/jexcelapi/ to generate them, this works very well. Once you're there, and you're stuck, just ask. I'll give you a code sample. Best regards, Geert On 2-dec-05, at 16:30, John Moore wrote: Hi, I'm wondering about using Rife for a new project I'm working on, having never used it before (I've used Struts/Spring/Hibernate in the past and am looking for a more rapidly productive alternative). One requirement is that certain responses must be generated as Excel spreadsheets. Is serving up non-HTML content straightforward enough in Rife? John -- == John Moore - Norwich, UK - [EMAIL PROTECTED] == ___ Rife-users mailing list Rife-users@uwyn.com http://www.uwyn.com/mailman/listinfo/rife-users -- Geert Bevin Uwyn bvba "Use what you need" Avenue de Scailmont 34 http://www.uwyn.com 7170 Manage, Belgium gbevin[remove] at uwyn dot comTel +32 64 84 80 03 PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9 Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net ___ Rife-users mailing list Rife-users@uwyn.com http://www.uwyn.com/mailman/listinfo/rife-users
[Rife-users] Excel spreadsheets as responses
Hi, I'm wondering about using Rife for a new project I'm working on, having never used it before (I've used Struts/Spring/Hibernate in the past and am looking for a more rapidly productive alternative). One requirement is that certain responses must be generated as Excel spreadsheets. Is serving up non-HTML content straightforward enough in Rife? John -- == John Moore - Norwich, UK - [EMAIL PROTECTED] == ___ Rife-users mailing list Rife-users@uwyn.com http://www.uwyn.com/mailman/listinfo/rife-users
