Re: perl.apache.org / apache.perl.org
On Sun, 7 Oct 2001, Stas Bekman wrote: can you please post the URL again? thanks! http://thisishomemade.com/for/modperl/site/ like he said before, it's really just a reorganization of the available information, rather than a complete site architecture with fancy rollover navigation, huge menu bars, swooshes and swirls. what with mp2 and what not, it may be that this design's time has passed.
Re: perl.apache.org / apache.perl.org
On Sun, 7 Oct 2001, Stas Bekman wrote: We have had two new designs worked out long time ago, but one has been picked by take23.org and the other wasn't applied. (hi brian) :( sorry! i have this tendency to bite off more than i can chew. i have 10 projects and none of them will ever be finished. What I want to say, is that it's not a point of where to host the site. The point is that we need someone to do the job of re-doing and making it easy to maintain the site, to keep it nice. jim's design is still available if somebody wants to use it.
Re: cvs commit: modperl/src/modules/perl Apache.xs
On Tue, 15 Aug 2000, Doug MacEachern wrote: what do you mean? args in or out? $r-args($string) just does a blind copy. @args = $r-args just splits on ,=, it's up to the caller to deal with multiple args of the same name. hm. what about %args = $r-args? won't that give me only the last arg value? i suppose i should just do @args = $r-args. thanks for the reminder.
Re: cvs commit: modperl/src/modules/perl Apache.xs
On 15 Aug 2000 [EMAIL PROTECTED] wrote: Log: fix $r-args(undef) speaking of which... does $r-args handle multiple args with the same name correctly? the docs imply that it doesn't. i haven't tried it myself to see. if i'm using Apache::Request, does setting a param get translated back down into $r-args? prolly not huh. i recently had the situation in webmail where i had to unescape, utf8-encode, and re-escape each param value, and then reformulate the query string. would have been cool if i could have just stepped through $r-param and set the values for each param, and then used $r-args at the very end.
jim's design
.. is ready to go. i can go ahead and update index.html, and jim's also updated several of the pages linked from there. but some of the others haven't been updated - should i do them all, or should i just do index.html and see what people think, or..? speaking of which - is there an automated process that updates /www/perl.apache.org from the modperl-site cvs module? or do i need to copy things by hand? -- Forwarded message -- Date: Fri, 16 Jun 2000 14:25:47 -0700 From: James Home [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: did I send you this? http://thisishomemade.com/clients/modperl/site let me know if you need something more from me with regards to this! - J. -- James Home - [EMAIL PROTECTED] http://www.superdeluxe.com http://www.vagabondage.com "There is absolutely no inevitability as long as there is a willingness to contemplate what is happening." - Marshall McLuhan
Re: cvs commit: modperl-site index.html
On Fri, 12 May 2000, Stas Bekman wrote: The only concern is to have all the pages designed in the same way and not only the the front page. Hmm, at least to arrange a link back to the front page :) yah, i think he originally wanted to make sure folks were happy with the design before he did a bunch more work. i'll ping jim again to see where he's at with the work.
Re: cvs commit: modperl-2.0/lib/ModPerl Code.pm
On Sat, 15 Apr 2000, Doug MacEachern wrote: that is sad. consider PerlFreshRestart and graceful restart. it doesn't take much effort to type '' instead of "". it might not make that much of a difference in parse time, but it doesn't hurt either. can we please drop this topic, there's plenty more important things to worry about. if you don't watch it i'm going to start questioning where you put your curly braces.
