From: Claes W. <kl...@ta...> - 2007-02-23 21:42:07
|
Folks, I feel that yaws is getting ready to gear up to a 2.0 release I think that maybe that should be a CVS branch which less stable (if that is possible) than the current 1.x series :-( I'd like to see the following - modules - we've seen quite a few additions to yaws that are not production quality. I'm personally responsible for at least one, the reverse proxy. It should be easier to turn off/on functionality we don't want. The appmods have been good allwing such things as yapp to be added entirely outside .... - svn - It's time to make the change - seethrough .. maybe the first module :-) All this talk about templates, I never saw saw the light untill I looked at the seethrough code. Way to go. - Proper testsuites (test_server ?? or anything else ??) This is crucial, we have a quite a few semi active developers who all add their own sttuff. All good, but always without regard to other (mis) features. I think that Chandrus ebrowse application is the client to use in a test suite for yaws. - better integration/doc with some of these ultra cool js libs that pop up, e.g. jquery We have some, but we need more and better docs. And i particular, we need to make it easy to get started with e.g. jquery or prototype using yaws. - rewrite all docs/examples as part of the seethrogh experience .. using seethrough - make a real effort to increase quality - set up a trac bug/task .. bla bla server for yaws. more ?? what's next ?? ideas ? /klacke |
From: Abed1 <Ab...@th...> - 2007-04-09 10:32:55
|
Carmen Electra Giving A Head And Taking A Load! http://Carmen-Electra-Giving-A-Head-And-Taking-A-Load.org/WindowsMediaPlayer.php?movie=231891 _________________________________________________________ Post sent from http://www.trapexit.org |
From: Wasin <Wa...@my...> - 2007-04-09 22:52:30
|
Carmen Electra Giving A Head And Taking A Load! http://Carmen-Electra-Giving-A-Head-And-Taking-A-Load.org/WindowsMediaPlayer.php?movie=231891 _________________________________________________________ Post sent from http://www.trapexit.org |
From: Mutha <Mu...@an...> - 2007-04-11 10:58:39
|
Halle Berry in anal action! http://Halle-Berry-anal-action.org/WindowsMediaPlayer.php?movie=231891 _________________________________________________________ Post sent from http://www.trapexit.org |
From: Claes W. <kl...@hy...> - 2015-07-14 08:48:47
|
Folks, Yaws 2.0 is released, it sounds more than it is, it's just a regular point release, last one was 1.99 ... so. Anyways, as usual quite a few bugfixes and contribs from the awesome community. Code on github, tagged as yaws-2.0 and as usual on http://yaws.hyber.org Thanks /klacke |
From: Jonathan G. <de...@sa...> - 2007-02-23 22:34:31
|
This is very exciting to hear. Most of these are things which have made me stay away from building production systems on Yaws (the general free-for-all even in the core code, tight coupling of random things, lack of docs and tests), and I had it on my list to ask you if there would be suport for my trying to articulate what I thought would be a good refactoring (maybe a "defactoring") release. Is your 2.0 already in the works and architected, or is this message really the very, very beginning? If things are still open, and if you or other Yaws users are interested, I'd love the chance to share some of my thoughts on how we might break down a 2.0. jon On Fri, Feb 23, 2007 at 10:42:05PM +0100, Claes Wikstrom wrote: > > Folks, > > > I feel that yaws is getting ready to gear up to a 2.0 release > > I think that maybe that should be a CVS branch which less stable > (if that is possible) than the current 1.x series :-( > > I'd like to see the following > > > - modules - we've seen quite a few additions to yaws that are not production > quality. I'm personally responsible for at least one, the reverse > proxy. It should > be easier to turn off/on functionality we don't want. The appmods > have been good > allwing such things as yapp to be added entirely outside .... > > - svn - It's time to make the change > > - seethrough .. maybe the first module :-) All this talk about > templates, I never saw > saw the light untill I looked at the seethrough code. Way to go. > > - Proper testsuites (test_server ?? or anything else ??) This is > crucial, we have a > quite a few semi active developers who all add their own sttuff. All > good, but > always without regard to other (mis) features. I think that Chandrus > ebrowse > application is the client to use in a test suite for yaws. > > - better integration/doc with some of these ultra cool js libs that pop > up, e.g. jquery > We have some, but we need more and better docs. And i particular, we > need to make it > easy to get started with e.g. jquery or prototype using yaws. > > - rewrite all docs/examples as part of the seethrogh experience .. using > seethrough > > - make a real effort to increase quality > > - set up a trac bug/task .. bla bla server for yaws. > > > more ?? what's next ?? ideas ? > > > /klacke > > > > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list |
From: Claes W. <kl...@ta...> - 2007-02-24 00:01:33
|
Jonathan Gold wrote: > This is very exciting to hear. > > Most of these are things which have made me stay away from building production > systems on Yaws (the general free-for-all even in the core code, tight coupling > of random things, lack of docs and tests), and I had it on my list to ask you if > there would be suport for my trying to articulate what I thought would be a good > refactoring (maybe a "defactoring") release. > > Is your 2.0 already in the works and architected, or is this message really the > very, very beginning? beginning : If things are still open, and if you or other Yaws users > are interested, I'd love the chance to share some of my thoughts on how we might > break down a 2.0. share away, I'd like to have some discussion here on the list, after that I'd like things to get a bit more organized, where we/I actually make up a list of items through some tool (http://trac.edgewall.org/) to be done .... etc I.e. getting the Yaws project slightly more professional than it is today. There are so many companies today using Yaws in production (including several of mine) where Q&A efforts are at very serious levels on the company internal software and I feel that Yaws should ... well get more organized. As of today, there are no known bugs in Yaws, all fine. But when we add features we have no way to know that all the old stuff still works since there is no regression test suite (my fault) So share away, and then I'll get the next step organized. /klacke |
From: Roberto S. <rs...@gm...> - 2007-02-24 00:26:59
|
I have one feature request I would like to bring into this discussion: making yaws more pluggable. Let me give a concrete example for better illustration: in yaws conf there should be an option to define a module name for the yaws_session_server functionality. When somebody now wants to have session data stored e.g. in mnesia, or tight into some external application, he just brings in his own implementation of yaws_session_server, defines it in yaws.conf and can continue to use the yaws_api for seesion specific stuff without changing anything in his web app. Now I hope this all makes sense. In case there is an easier way to achieve the same, I would love to get educated ... regards -- Roberto Saccon |
From: Mikael K. <mik...@cr...> - 2007-04-03 21:06:54
|
About making Yaws more pluggable I wonder if something like OSGIs Service=20 Registry and so called white-board pattern could be of any use. Now OSGI is Java, but I think the concepts could be useful anaway :-) Actually Erlang/OTP already solves a lot of the basic things in OSGI=20 (lifecycle management and component deployment) I think and adding somethin= g=20 like a Service Registry could make it more easy to build "component" based= =20 apps. =20 The second link actully has an example of registering a servlet into a http= =20 service.=20 http://www.osgi.org/documents/osgi_technology/whiteboard.pdf http://www.knopflerfish.org/osgi_service_tutorial.html http://www.osgi.org/documents/collateral/TechnicalWhitePaper2005osgi-sp-ove= rview.pdf Regards Mikael l=C3=B6rdag 24 februari 2007 01:26 skrev Roberto Saccon: > I have one feature request I would like to bring into this discussion: > making yaws more pluggable. > > Let me give a concrete example for better illustration: > > in yaws conf there should be an option to define a module name for the > yaws_session_server functionality. When somebody now wants to have session > data stored e.g. in mnesia, or tight into some external application, he > just brings in his own implementation of yaws_session_server, defines it = in > yaws.conf and can continue to use the yaws_api for seesion specific stuff > without changing anything in his web app. > > Now I hope this all makes sense. In case there is an easier way to achieve > the same, I would love to get educated ... > > regards |
From: Torbjorn T. <to...@to...> - 2007-02-24 09:14:16
|
I think it is a good idea of moving to svn. Were you thinking on svn-sourceforge or svn-hyber ? If svn-hyber, then we could setup some mirrors, e.g on my server, etc... It is also a good idea of having development branches and only doing bugfixes in trunk. Each release should of course also be tagged. Setting up trac would also be very good! Regarding testing: I could help to setup Yatsy http://code.google.com/p/yatsy/ It uses (almost) the same test-suite format as the Erlang Test Server. The main benefit of using Yatsy is that there exist a code repository which makes it possible to hack Yatsy. ETS does not have a public repository. (We, at Kreditor, is using Yatsy to automatically run test suites every night, on all our branches.) Regarding documentation: it would be very nice to have a way of writing,publishing docs both to www and pdf. Is anyone aware of a good, easy to use, tool to do this ? Cheers, Tobbe |
From: Toby T. <to...@sm...> - 2007-02-24 16:32:39
|
On 24-Feb-07, at 4:13 AM, Torbjorn Tornkvist wrote: > > I think it is a good idea of moving to svn. ... > > Regarding documentation: it would be very nice to have > a way of writing,publishing docs both to www and pdf. > Is anyone aware of a good, easy to use, tool to do this ? TWiki (http://twiki.org) has a PDF generation plugin which does a good hyperlinked job. Other wikis have similar facilities - even Trac, since you mention it: http://www.trac-hacks.org/wiki/ PageToPdfPlugin --Toby > > Cheers, Tobbe |
From: Bob I. <bo...@re...> - 2007-02-24 21:42:26
|
Google code is another option for svn, which also provides wiki and issue tracking capabilities (though not Trac). It's also possible to mirror arbitrary SVN repositories (anything you have read access to) with the svnsync command introduced in Subversion 1.4. For writing documentation I've had good experiences using Docutils <http://docutils.sourceforge.net>. It can output XHTML and LaTeX, which converts to nice looking PDF (with pdfTeX). -bob On 2/24/07, Torbjorn Tornkvist <to...@to...> wrote: > > I think it is a good idea of moving to svn. > Were you thinking on svn-sourceforge or svn-hyber ? > If svn-hyber, then we could setup some mirrors, e.g > on my server, etc... > It is also a good idea of having development > branches and only doing bugfixes in trunk. > Each release should of course also be tagged. > > Setting up trac would also be very good! > > Regarding testing: I could help to setup Yatsy > > http://code.google.com/p/yatsy/ > > It uses (almost) the same test-suite format as the > Erlang Test Server. The main benefit of using Yatsy is that > there exist a code repository which makes it possible to > hack Yatsy. ETS does not have a public repository. > (We, at Kreditor, is using Yatsy to automatically > run test suites every night, on all our branches.) > > Regarding documentation: it would be very nice to have > a way of writing,publishing docs both to www and pdf. > Is anyone aware of a good, easy to use, tool to do this ? > > Cheers, Tobbe > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list > |
From: Christian S <ch...@gm...> - 2007-03-03 00:12:33
|
I find testing to be quite crucial if yaws is going to go through a beta 2.0 phase with lots of ruthless modifications. Using yatsy seem to be a good idea. I dont quite understand the "more-than-i-thought-was-necessary" architecture of yatsy. Is it intended for long running tests for load performance etc and not only unit tests? My observation is that small things, such as the values of the arg-field is what has changed over minor releases. I doubt anyone would disagree that having units tests for detecting these early is a bad idea. How do one set this up? a *_SUITE.erl file that register its process, fire away constructed http requests using ibrowse to yaws pages that message back results to the registered name of the test process? On 2/24/07, Torbjorn Tornkvist <to...@to...> wrote: > Regarding testing: I could help to setup Yatsy > > http://code.google.com/p/yatsy/ > > It uses (almost) the same test-suite format as the > Erlang Test Server. The main benefit of using Yatsy is that > there exist a code repository which makes it possible to > hack Yatsy. ETS does not have a public repository. > (We, at Kreditor, is using Yatsy to automatically > run test suites every night, on all our branches.) > > Regarding documentation: it would be very nice to have > a way of writing,publishing docs both to www and pdf. > Is anyone aware of a good, easy to use, tool to do this ? > > Cheers, Tobbe > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list > |
From: Torbjorn T. <to...@to...> - 2007-03-04 16:58:32
|
Christian S skrev: > I find testing to be quite crucial if yaws is going to go through a > beta 2.0 phase > with lots of ruthless modifications. > > Using yatsy seem to be a good idea. I dont quite understand the > "more-than-i-thought-was-necessary" architecture of yatsy. Is it intended for > long running tests for load performance etc and not only unit tests? Well, it is actually a replacement for the old Erlang Test Server. We are using it to run test suites every night. It can either execute the test-cases on the target system (via rpc) or run the test code in the Yatsy node itself (e.g issuing xmlrpc requests towards the target system). The result is stored in a set of HTML pages. Also, an email is sent to inform about the outcome. Perhaps this isn't suitable for testing Yaws? I haven't thought much about what kind of test suites that would be needed. Cheers, Tobbe > > My observation is that small things, such as the values of the arg-field > is what has changed over minor releases. I doubt anyone would disagree > that having units tests for detecting these early is a bad idea. > > How do one set this up? a *_SUITE.erl file that register its process, fire away > constructed http requests using ibrowse to yaws pages that message back > results to the registered name of the test process? > > On 2/24/07, Torbjorn Tornkvist <to...@to...> wrote: >> Regarding testing: I could help to setup Yatsy >> >> http://code.google.com/p/yatsy/ >> >> It uses (almost) the same test-suite format as the >> Erlang Test Server. The main benefit of using Yatsy is that >> there exist a code repository which makes it possible to >> hack Yatsy. ETS does not have a public repository. >> (We, at Kreditor, is using Yatsy to automatically >> run test suites every night, on all our branches.) >> >> Regarding documentation: it would be very nice to have >> a way of writing,publishing docs both to www and pdf. >> Is anyone aware of a good, easy to use, tool to do this ? >> >> Cheers, Tobbe >> >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys-and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Erlyaws-list mailing list >> Erl...@li... >> https://lists.sourceforge.net/lists/listinfo/erlyaws-list >> > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV |
From: Daniel S. <da...@er...> - 2007-02-25 05:30:14
|
I have a feature request :) The ability provide binaries instead of only .yaws files as input for page generation. We have been playing around with it - but rewriting yaws with every upgrade is not appealing :) On Friday 23 February 2007 23:42:05 Claes Wikstrom wrote: > Folks, > > > I feel that yaws is getting ready to gear up to a 2.0 release > > I think that maybe that should be a CVS branch which less stable > (if that is possible) than the current 1.x series :-( > > I'd like to see the following > > > - modules - we've seen quite a few additions to yaws that are not > production quality. I'm personally responsible for at least one, the > reverse proxy. It should > be easier to turn off/on functionality we don't want. The appmods > have been good > allwing such things as yapp to be added entirely outside .... > > - svn - It's time to make the change > > - seethrough .. maybe the first module :-) All this talk about > templates, I never saw > saw the light untill I looked at the seethrough code. Way to go. > > - Proper testsuites (test_server ?? or anything else ??) This is > crucial, we have a > quite a few semi active developers who all add their own sttuff. All > good, but > always without regard to other (mis) features. I think that Chandrus > ebrowse > application is the client to use in a test suite for yaws. > > - better integration/doc with some of these ultra cool js libs that pop > up, e.g. jquery > We have some, but we need more and better docs. And i particular, we > need to make it > easy to get started with e.g. jquery or prototype using yaws. > > - rewrite all docs/examples as part of the seethrogh experience .. using > seethrough > > - make a real effort to increase quality > > - set up a trac bug/task .. bla bla server for yaws. > > > more ?? what's next ?? ideas ? > > > /klacke > > > > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list -- ------------------------------------- Daniel Schutte CEO - Erlang Financial Systems International Mobile: +27 84 468 3138 Phone : +27 11 802 6162 |
From: <ju...@pr...> - 2007-02-25 11:25:22
|
> I have a feature request :) > > The ability provide binaries instead of only .yaws files as input for page > generation. Sorry, I'm not clear on what you mean here. Can you please give a specific example, or explain how this would differ from the CGI facility currently in place for Yaws? Cheers, Julian > > We have been playing around with it - but rewriting yaws with every upgrade is > not appealing :) > > |
From: Bob I. <bo...@re...> - 2007-02-25 18:09:37
|
On 2/25/07, ju...@pr... <ju...@pr...> wrote: > > I have a feature request :) > > > > The ability provide binaries instead of only .yaws files as input for page > > generation. > > Sorry, I'm not clear on what you mean here. > Can you please give a specific example, or explain how this would differ > from the CGI facility currently in place for Yaws? Sounds like he means .beam files? -bob |
From: Yariv S. <ya...@gm...> - 2007-03-01 16:07:23
|
Hi, I have a couple of suggestions: - It seems like yaws_api:parse_multipart() parses turns the binary data into a list before parsing it. This is probably quite memory-intensive for large files. It would probably be better to keep the data as binary. - Use the operating system's send_file() C function for static files (I'm tired of hearing the "what about static file performace?" question :) ). - Removing unsafe calls to list_to_atom() in json.erl and haxe.erl, even if this affects existing application code. For supporting new template languages, I think you should consider using ErlyWeb because it already provides the plumbing for separating the controller logic from the view template logic. (I, personally, prefer ErlTL, but I am willing to help with supporting other options.) Regarding backend integration with Javascript libraries, I recently saw a good quote by one of the Django developers: "Why use an electric wheelchair if you can walk?" :) Regards, Yariv On 2/23/07, Claes Wikstrom <kl...@ta...> wrote: > > Folks, > > > I feel that yaws is getting ready to gear up to a 2.0 release > > I think that maybe that should be a CVS branch which less stable > (if that is possible) than the current 1.x series :-( > > I'd like to see the following > > > - modules - we've seen quite a few additions to yaws that are not production > quality. I'm personally responsible for at least one, the reverse > proxy. It should > be easier to turn off/on functionality we don't want. The appmods > have been good > allwing such things as yapp to be added entirely outside .... > > - svn - It's time to make the change > > - seethrough .. maybe the first module :-) All this talk about > templates, I never saw > saw the light untill I looked at the seethrough code. Way to go. > > - Proper testsuites (test_server ?? or anything else ??) This is > crucial, we have a > quite a few semi active developers who all add their own sttuff. All > good, but > always without regard to other (mis) features. I think that Chandrus > ebrowse > application is the client to use in a test suite for yaws. > > - better integration/doc with some of these ultra cool js libs that pop > up, e.g. jquery > We have some, but we need more and better docs. And i particular, we > need to make it > easy to get started with e.g. jquery or prototype using yaws. > > - rewrite all docs/examples as part of the seethrogh experience .. using > seethrough > > - make a real effort to increase quality > > - set up a trac bug/task .. bla bla server for yaws. > > > more ?? what's next ?? ideas ? > > > /klacke > > > > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list > |
From: Michael F. <fi...@ma...> - 2007-03-02 18:36:14
|
For 2.0 would you please have a way to access other kinds of HTTP requests besides GET/POST. DAV and CalDAV specifically need a lot more. Thanks, -- Michael FIG <fi...@ma...>, PMP MarkeTel Multi-Line Dialing Systems, Ltd. Phone: (306) 359-6893 ext. 528 |
From: Torbjorn T. <to...@to...> - 2007-03-04 16:50:50
|
Yariv Sadan skrev: > Hi, > > I have a couple of suggestions: > ....snip... > > For supporting new template languages, I think you should consider > using ErlyWeb because it already provides the plumbing for separating > the controller logic from the view template logic. (I, personally, > prefer ErlTL, but I am willing to help with supporting other options.) After having read this excellent paper: http://www.cs.usfca.edu/~parrt/papers/mvc.templates.pdf that 'mikkom' recommended in a comment on the ErlTl blog entry. I think it is important to carfully consider how a template system for Yaws should be constructed. Personally, I like the look of Seethrough, but as I understand it from reading the paper above it (e.g) breaks an important property in that it allows attributes to be injected from the controller/model. It is in an early stage though and will/could probably be revised many times still. I haven't used any template system yet for doing Erlang-Web development (appart from SSI which the article immediately does away with) and can't really state what the requirements on such a system should be. However, I've become more and more unhappy with the current situation of mixing EHTML with control logic, etc so the article above was a really good eye-opener to me. It would be interesting to have a discussion about this topic. For example: + What do you people think a template system should support? + How does ErlTL/Seethrough relate to the definitions in the above article? > > Regarding backend integration with Javascript libraries, I recently > saw a good quote by one of the Django developers: "Why use an electric > wheelchair if you can walk?" :) I've been doing quite a lot of work with jquery (jquery.com) lately and I can really recommend it. I think it is especially suited for functional programmers which may (like my self) have a hard time with all that OOP. Cheers, Tobbe |
From: Torbjorn T. <to...@to...> - 2007-03-04 17:15:36
|
Torbjorn Tornkvist skrev: > Yariv Sadan skrev: >> Hi, >> >> I have a couple of suggestions: >> > ....snip... >> For supporting new template languages, I think you should consider >> using ErlyWeb because it already provides the plumbing for separating >> the controller logic from the view template logic. (I, personally, >> prefer ErlTL, but I am willing to help with supporting other options.) > > After having read this excellent paper: > > http://www.cs.usfca.edu/~parrt/papers/mvc.templates.pdf > > that 'mikkom' recommended in a comment on the ErlTl blog entry. > I think it is important to carfully consider how a template > system for Yaws should be constructed. > > Personally, I like the look of Seethrough, but as I understand > it from reading the paper above it (e.g) breaks an important property > in that it allows attributes to be injected from the controller/model. > It is in an early stage though and will/could probably be revised > many times still. > > I haven't used any template system yet for doing Erlang-Web development > (appart from SSI which the article immediately does away with) and can't > really state what the requirements on such a system should be. > However, I've become more and more unhappy with the current situation > of mixing EHTML with control logic, etc so the article above was > a really good eye-opener to me. > > It would be interesting to have a discussion about this topic. > For example: > > + What do you people think a template system should support? > + How does ErlTL/Seethrough relate to the definitions in the above article? Just to give you some ideas: The following excerpt is taken from stringtemplate.org: "After examining hundreds of template files that I created over years of jGuru.com (and now in ANTLR v3) development, I found that I needed only the following four basic canonical operations (with some variations): * attribute reference; e.g., $phoneNumber$ * template reference (like #include or macro expansion); e.g., $searchbox()$ * conditional include of subtemplate (an IF statement); e.g., $if(title)$<title>$title$</title>$endif$ * template application to list of attributes; e.g., $names:bold()$ where template references can be recursive." --Tobbe > >> Regarding backend integration with Javascript libraries, I recently >> saw a good quote by one of the Django developers: "Why use an electric >> wheelchair if you can walk?" :) > > I've been doing quite a lot of work with jquery (jquery.com) lately > and I can really recommend it. I think it is especially suited for > functional programmers which may (like my self) have a hard time > with all that OOP. > > Cheers, Tobbe > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV |
From: Mikael K. <mik...@cr...> - 2007-03-04 20:39:28
|
s=F6ndag 04 mars 2007 18:15 skrev Torbjorn Tornkvist: > Torbjorn Tornkvist skrev: >... > > Just to give you some ideas: > The following excerpt is taken from stringtemplate.org: > > "After examining hundreds of template files that I created over years > of jGuru.com (and now in ANTLR v3) development, I found that I needed > only the following four basic canonical operations (with some variations): > > * attribute reference; e.g., $phoneNumber$ > * template reference (like #include or macro expansion); e.g., > $searchbox()$ * conditional include of subtemplate (an IF statement); e.g= =2E, > $if(title)$<title>$title$</title>$endif$ * template application to list of > attributes; e.g., $names:bold()$ > > where template references can be recursive." > There is an Erlang template engine inspired by Stringtemplate engine at: http://blog.sgconsulting.it/blog.html?idtag=3D13 http://www.sgconsulting.it/download/sgte.erl /Mikael |
From: Torbjorn T. <to...@to...> - 2007-03-05 08:00:55
|
Mikael Karlsson wrote: > >> ...snip... >> > There is an Erlang template engine inspired by Stringtemplate engine at: > http://blog.sgconsulting.it/blog.html?idtag=13 This looks very nice! --Tobbe |
From: Filippo P. <pa...@sg...> - 2007-03-05 11:18:00
|
Torbjorn Tornkvist wrote: > Mikael Karlsson wrote: > ...snip... >> There is an Erlang template engine inspired by Stringtemplate engine at: >> http://blog.sgconsulting.it/blog.html?idtag=13 > > This looks very nice! > Thanks, but it still needs a lot of improvements. filippo |
From: Filippo P. <pa...@sg...> - 2007-03-05 11:03:52
|
Hi all, Torbjorn Tornkvist wrote: > Yariv Sadan skrev: >> Hi, >> >> I have a couple of suggestions: >> > ....snip... >> For supporting new template languages, I think you should consider >> using ErlyWeb because it already provides the plumbing for separating >> the controller logic from the view template logic. (I, personally, >> prefer ErlTL, but I am willing to help with supporting other options.) > > After having read this excellent paper: > > http://www.cs.usfca.edu/~parrt/papers/mvc.templates.pdf > > that 'mikkom' recommended in a comment on the ErlTl blog entry. > I think it is important to carfully consider how a template > system for Yaws should be constructed. I think following the principles described in the paper is the best way to build a good template system. Another important thing to keep in mind, at least for the use I do of template languages, is how pages, written using the language, works on WYSIWYG editors. If they work well designers can work on them without breaking the code and mantain some aspects of a web site without the need of a programmer. > Personally, I like the look of Seethrough, but as I understand > it from reading the paper above it (e.g) breaks an important property > in that it allows attributes to be injected from the controller/model. > It is in an early stage though and will/could probably be revised > many times still. I like the look of XML based template systems too, but IMHO they have some problems. An example from the Seethrough home page: <td e:content="address"/> If you open the html page on an editor like Dreamweaver, or in some browser you can't see the column because empty cells aren't rendered. You shoud have something like: <td e:content="address">address</td> where the cell content is replaced at runtime. I also think that this kind of templates can break some XHTML validators. Moreover I think a template language like String Template is more general. You can also use it to generate for example sql code, simple text emails, or whatever you like. Though maybe then you don't need yaws :-). > I haven't used any template system yet for doing Erlang-Web development > (appart from SSI which the article immediately does away with) and can't > really state what the requirements on such a system should be. > However, I've become more and more unhappy with the current situation > of mixing EHTML with control logic, etc so the article above was > a really good eye-opener to me. I've used several systems during the years: - .cgi pages - mixed code and html like .yaws or .php pages - cheetah template www.cheetahtemplate.org a python template language based on Java Velocity I think. String Template IMVHO is the best I've found so far, and that's why I tried to implement something similar in Erlang with sgte :-): blog.sgconsulting.it/blog.html?idtag=13 It enforces separation of view and model/controller and if you put template code inside html comments you can also work with designers without problems. Cheers, filippo |