From: <ejo...@ya...> - 2007-06-10 05:49:18
|
I noticed that File paths work differently between ssi and yssi. i.e.: out(Arg)->{ssi,"testdir/ssi_inc.yaws","%",[]}. will find the file relative to the yaws docroot. But, out(Arg)->{yssi,"testdir/ssi_inc.yaws"}. will find it relative to the calling yaws file. Is there a reason that the file lookups work differently? ____________________________________________________________________________________ Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow |
From: Claes W. <kl...@ta...> - 2007-06-10 19:50:45
|
ejo...@ya... wrote: > I noticed that File paths work differently between ssi > and yssi. > > i.e.: > > out(Arg)->{ssi,"testdir/ssi_inc.yaws","%",[]}. > > will find the file relative to the yaws docroot. > > But, > > out(Arg)->{yssi,"testdir/ssi_inc.yaws"}. > > will find it relative to the calling yaws file. > > Is there a reason that the file lookups work > differently? > sloppyness ... would be the reason. This cannot be changed though since a change would break code. Should be documented though. /klacke |
From: Jim M. <jim...@gm...> - 2007-06-10 23:19:25
|
On 6/10/07, Claes Wikstrom <kl...@ta...> wrote: > ejo...@ya... wrote: > > I noticed that File paths work differently between ssi > > and yssi. > > > > i.e.: > > > > out(Arg)->{ssi,"testdir/ssi_inc.yaws","%",[]}. > > > > will find the file relative to the yaws docroot. > > > > But, > > > > out(Arg)->{yssi,"testdir/ssi_inc.yaws"}. > > > > will find it relative to the calling yaws file. > > > > Is there a reason that the file lookups work > > differently? > > > > sloppyness ... would be the reason. This cannot be changed though > since a change would break code. Should be documented though. I'd like to suggest that this is the wrong approach. Now is the time to fix this problem. Erlang is getting a lot of press right now, and this should be fixed before it's too late. Too late because there will hopefully be a lot more users of Erlang and Yaws, and too late because an inconsistency like this looks bad. Jim -- Jim Menard, ji...@io..., jim...@gm... http://www.io.com/~jimm/ |
From: jla415 <jl...@gm...> - 2007-06-10 23:56:16
|
Jim Menard wrote: > > On 6/10/07, Claes Wikstrom <kl...@ta...> wrote: >> ejo...@ya... wrote: >> > I noticed that File paths work differently between ssi >> > and yssi. >> > >> > i.e.: >> > >> > out(Arg)->{ssi,"testdir/ssi_inc.yaws","%",[]}. >> > >> > will find the file relative to the yaws docroot. >> > >> > But, >> > >> > out(Arg)->{yssi,"testdir/ssi_inc.yaws"}. >> > >> > will find it relative to the calling yaws file. >> > >> > Is there a reason that the file lookups work >> > differently? >> > >> >> sloppyness ... would be the reason. This cannot be changed though >> since a change would break code. Should be documented though. > > I'd like to suggest that this is the wrong approach. Now is the time > to fix this problem. Erlang is getting a lot of press right now, and > this should be fixed before it's too late. Too late because there will > hopefully be a lot more users of Erlang and Yaws, and too late because > an inconsistency like this looks bad. > > I'd have to agree here. It makes little sense to have a relative path ssi call use the docroot rather than the path to the current file that is evaluating the ssi call. Better to fix this now before yaws gets more adoption as the current user base is well equiped to fix any incompatibilies during an ugprade with a simple grep and replacement. -- View this message in context: http://www.nabble.com/ssi-yssi-relative-paths-tf3896432.html#a11053530 Sent from the Yaws mailing list archive at Nabble.com. |
From: <ju...@pr...> - 2007-06-11 12:22:35
|
While I believe there are some serious shortcomings yet to be fixed with regards to yaws includes and recursion - the absolute/relative issue described below has already been fixed in the source a few months ago. I'm testing using the version from CVS just before conversion to SVN - but I don't think much has changed in between. Testing with the CVS version: Both: out(Arg)->{ssi,"testdir/ssi_inc.yaws","%",[]}. out(Arg)->{yssi,"testdir/ssi_inc.yaws"}. are 'relative' includes due to the lack of a leading slash. Both: out(Arg)->{ssi,"/testdir/ssi_inc.yaws","%",[]}. out(Arg)->{yssi,"/testdir/ssi_inc.yaws"}. Are 'absolute' includes with the path being from the docroot. I've tested by placing an ssi_inc.yaws in /testdir and a different version under /sub/testdir Files in both locations can include the appropriate files relatively or absolutely - no problems. Even relative backtracking includes work; for example: out(Arg)->{ssi,"../testdir/ssi_inc.yaws","%",[]}. out(Arg)->{yssi,"../testdir/ssi_inc.yaws"}. Speaking of sloppy.. I owe some documentation to the project regarding virtual directories.. as well as these fixes to includes. My apologies.. I haven't forgotten or disappeared entirely - but am under serious time constraints for a while yet. I'll still monitor for bugs related to code I've added, and will hopefully get a chance to work with the other devs to drive things forward again soon. Cheers, Julian ----- Original Message ----- From: "jla415" <jl...@gm...> To: <erl...@li...> Sent: Sunday, June 10, 2007 11:56 PM Subject: Re: [Erlyaws-list] ssi/yssi relative paths > > > Jim Menard wrote: > > > > On 6/10/07, Claes Wikstrom <kl...@ta...> wrote: > >> ejo...@ya... wrote: > >> > I noticed that File paths work differently between ssi > >> > and yssi. > >> > > >> > i.e.: > >> > > >> > out(Arg)->{ssi,"testdir/ssi_inc.yaws","%",[]}. > >> > > >> > will find the file relative to the yaws docroot. > >> > > >> > But, > >> > > >> > out(Arg)->{yssi,"testdir/ssi_inc.yaws"}. > >> > > >> > will find it relative to the calling yaws file. > >> > > >> > Is there a reason that the file lookups work > >> > differently? > >> > > >> > >> sloppyness ... would be the reason. This cannot be changed though > >> since a change would break code. Should be documented though. > > > > I'd like to suggest that this is the wrong approach. Now is the time > > to fix this problem. Erlang is getting a lot of press right now, and > > this should be fixed before it's too late. Too late because there will > > hopefully be a lot more users of Erlang and Yaws, and too late because > > an inconsistency like this looks bad. > > > > > > I'd have to agree here. It makes little sense to have a relative path ssi > call use the docroot rather than the path to the current file that is > evaluating the ssi call. Better to fix this now before yaws gets more > adoption as the current user base is well equiped to fix any incompatibilies > during an ugprade with a simple grep and replacement. > > > -- > View this message in context: http://www.nabble.com/ssi-yssi-relative-paths-tf3896432.html#a11053530 > Sent from the Yaws mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list |
From: <ejo...@ya...> - 2007-06-11 18:38:34
|
Thanks. Speaking of documentation, I've been submitting a small handful of syntax and spelling patches for the example yaws files. Can someone with commit rights take a peek at them? --- Claes Wikstrom <kl...@ta...> wrote: > ejo...@ya... wrote: > > I noticed that File paths work differently between > ssi > > and yssi. > > > > i.e.: > > > > out(Arg)->{ssi,"testdir/ssi_inc.yaws","%",[]}. > > > > will find the file relative to the yaws docroot. > > > > But, > > > > out(Arg)->{yssi,"testdir/ssi_inc.yaws"}. > > > > will find it relative to the calling yaws file. > > > > Is there a reason that the file lookups work > > differently? > > > > sloppyness ... would be the reason. This cannot be > changed though > since a change would break code. Should be > documented though. > > > /klacke > ____________________________________________________________________________________ Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. http://tv.yahoo.com/collections/222 |
From: Claes W. <kl...@ta...> - 2007-06-11 22:12:39
|
ejo...@ya... wrote: > Thanks. > > Speaking of documentation, I've been submitting a > small handful of syntax and spelling patches for the > example yaws files. Can someone with commit rights > take a peek at them? > so post the patches /klacke |
From: <ejo...@ya...> - 2007-06-12 03:27:54
|
I did. There up on sourceforge (the patches submitted by ejones1): http://sourceforge.net/tracker/?atid=443519&group_id=45637&func=browse --- Claes Wikstrom <kl...@ta...> wrote: > ejo...@ya... wrote: > > Thanks. > > > > Speaking of documentation, I've been submitting a > > small handful of syntax and spelling patches for > the > > example yaws files. Can someone with commit > rights > > take a peek at them? > > > > so post the patches > > /klacke > ____________________________________________________________________________________ Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. http://farechase.yahoo.com/promo-generic-14795097 |
From: <kl...@ta...> - 2007-06-12 07:53:50
|
ejo...@ya... wrote: > I did. There up on sourceforge (the patches submitted > by ejones1): > > http://sourceforge.net/tracker/?atid=443519&group_id=45637&func=browse > Thanks /klacke -- Claes Wikstrom -- Caps lock is nowhere and http://www.tail-f.com -- everything is under control cellphone: +46 70 2097763 |