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: 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: 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.
Re: jim's design
On Sun, 18 Jun 2000, Stas Bekman wrote: > * Parts from index.html have been killed > (jobs/stats/lately added material) besides jobs and stats, what else? if you can figure out a date for the recent material, i can re-apply the patches from cvs by hand. > * The navbar on the other pages is broken; should be > index.html#foo or alike ok. so should i apply the template to all of the sub pages? should i just use ssi or something?
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-site index.html (fwd)
On Sat, 6 May 2000, James Home wrote: > Sometime on 5/6/00, brian moseley was saying: > >what do you think? > > > >I don't like the main font > >selection -- it looks ugly on netscape/linux. I guess it's because it > >forces a point size which picks the wrong font. > > I think I should look at in on linux/netscape. you can look at my laptop on monday. > >It's +1 from me for either Jim's or Robin/Matt's work, just make sure you > >don't nuke the updates I've just made. Thanks! > > I can do this integration sometime this weekend. cool, when you've got something let us know, and i'll commit it.
Re: cvs commit: modperl-site index.html
On Sat, 6 May 2000, Stas Bekman wrote: > Huh? Was I supposed to? I've heard about at least two > groups of people working on the site for the last year, > I've tired of waiting and remade the first page since I > use it all the time. I thought Jim's work was only a > preview and someone is going to commit it and put > online, apparently it was just lost. nah, it's still at http://www.vagabondage.com/~jim/modperl. it was just a preview, i was waiting for others to +1 it or whatever before i told him to finish it up. then i forgot about it. > But as we all know the psychology of this list, if you > want something to be done, do it yourself. (Well, I > don't talk about the mod_perl itself :) I don't claim > myself to be a web designer, I hope my remake makes the > first page at least more useful and appealing. it's certainly better than what we used to have.
Re: cvs commit: modperl-site index.html
On 6 May 2000 [EMAIL PROTECTED] wrote: > sbekman 00/05/06 08:31:53 > > Modified:.index.html > Log: > index.html remake didn't use jim's work after all eh? too bad, it's much nicer, imo.
Re: cvs commit: modperl/eg startup.pl
On Fri, 21 Apr 2000, Stas Bekman wrote:
> find . -type f -exec grep -l 'eg/' {} \;
find. -type f|xargs grep -l 'eg/' would be a lot
faster. well at least that's what dean says.
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.
