Re: moving modperl-site rep into modperl-docs rep

2001-11-03 Thread Stas Bekman


Say, do you plan on static output from Embperl or only dynamic for
embperl docs? It doesn't make much sense to serve static content
dynamically, resource wise of course.


 
 Most things will be static and pregenerated, like you plan it for the
 mod_perl site. There maybe a small dynamic part, where people are able to
 add links, examples, news etc.


that would be a very good thing to have! The problem is providing the required setup 
on apache.org.

BTW, what's the source format that you use for embperl?

 
 Everything is in POD, because it really the best and easiest way to write it
 down


fantastic!


 may be it can
just plug into the docset system, and then we can keep it under the same
roof.


 
 I would be happy if we keep it under the same roof. I don't like to reinvent
 the wheel, but I like to have the possibility to make my own design and use
 Embperl for rendering, instead of TT. Hopefully there are also some aspects
 in things that I programm that will be usefull for the modperl site.

That's sounds cool. I'm looking forward for other extensions to chime in.



As you have seen I'm pretty much done. Now doing 

code refactoring to make more extendable.



-- 


_
Stas Bekman JAm_pH  --   Just Another mod_perl Hacker
http://stason.org/  mod_perl Guide   http://perl.apache.org/guide
mailto:[EMAIL PROTECTED]  http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/




Re: moving modperl-site rep into modperl-docs rep

2001-11-03 Thread Gerald Richter


 Well, the code is quite crude yet, and it's hard to modularize before
 you know what to plan for, but yes the rendering engine is a separate
 thing. So after generalizing it and making it pluggable it should be
 possible to use other rendering modules.


I will take a look at it when you release it

 Say, do you plan on static output from Embperl or only dynamic for
 embperl docs? It doesn't make much sense to serve static content
 dynamically, resource wise of course.


Most things will be static and pregenerated, like you plan it for the
mod_perl site. There maybe a small dynamic part, where people are able to
add links, examples, news etc.

 BTW, what's the source format that you use for embperl?

Everything is in POD, because it really the best and easiest way to write it
down

  may be it can
 just plug into the docset system, and then we can keep it under the same
 roof.


I would be happy if we keep it under the same roof. I don't like to reinvent
the wheel, but I like to have the possibility to make my own design and use
Embperl for rendering, instead of TT. Hopefully there are also some aspects
in things that I programm that will be usefull for the modperl site.

Gerald


-
Gerald Richterecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting

Post:   Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice:+49 6133 925131
WWW:http://www.ecos.de  Fax:  +49 6133 925152
-





Re: moving modperl-site rep into modperl-docs rep

2001-11-03 Thread Gerald Richter

 
  Most things will be static and pregenerated, like you plan it for the
  mod_perl site. There maybe a small dynamic part, where people are able
to
  add links, examples, news etc.


 that would be a very good thing to have! The problem is providing the
required setup on apache.org.


For the Embperl site I have thought about setting up the dynamic part on our
own server (simply because it's esaier for me to adminitrate, because I am
root there). If the components are usefull for the modperl site, I am sure
we will find a way to let them run on perl.apache.org and move them over. I
case we can't, it should be possible to do the hosting for the dynamic part
of the modperl site at our server.


 As you have seen I'm pretty much done. Now doing

 code refactoring to make more extendable.


I am looking forward to see it and check out where I can plug in

Gerald


-
Gerald Richterecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting

Post:   Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice:+49 6133 925131
WWW:http://www.ecos.de  Fax:  +49 6133 925152
-