Re: [preview 2] new mod_perl site concept
Craig McLane wrote: > I focused mostly on the content - Stas this rocks! Very easy to > navigate, and the info (especially the Apache::Test documentation is > great. Thanks Craig :) > One 'style' nit, it appears that an absolute width is specified on the tables > used for formatting which bumps the right area of the page so that I > have to scroll horizontally in my browser. It looks fine in links, so > it might just be the font I am using. I think the main problem is that some code sections in the docs are wide, and they force the browser to scroll left. Possible solutions are: * change the font style/size for the sections to make it take less space. * the menu on the left takes a lot of space for no reason. it can be moved in. BTW, you don't see it yet, but the site sports PDF files of each sub-docset (ala mod_perl guide). I just didn't link those yet. So once I'm done you can just grab PDF files for an easier reading :) > Craig > > > On Fri, Nov 02, 2001 at 06:53:48PM +0800, Stas Bekman wrote: > >>Those that are on the docset-templates list know that I'm moving on with >>the new docset building code, I'm going to release it very soon now. >> >>Here is a second preview of the site: >>http://www.apache.org/~stas/newsite/index.html >> >>As usual disregard the content, just say if you see something wrong with >>navigation widgets, concepts in general. >> >>If everything is cool, I'll start filling it with the real content. Also >>see another email that I'll send in a sec. >> >>_ >>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/ >> >> >>- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> -- _ 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/
cvs commit: modperl-2.0/lib/Apache Build.pm
dougm 01/11/02 09:59:05
Modified:.Makefile.PL
lib/Apache Build.pm
Log:
change install method for libmodperl.so: now done via src/modules/perl/Makefile
install target
Revision ChangesPath
1.53 +10 -11modperl-2.0/Makefile.PL
Index: Makefile.PL
===
RCS file: /home/cvs/modperl-2.0/Makefile.PL,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -r1.52 -r1.53
--- Makefile.PL 2001/11/02 17:33:46 1.52
+++ Makefile.PL 2001/11/02 17:59:05 1.53
@@ -291,6 +291,9 @@
modperl_lib:
cd "$(MODPERL_SRC)" && $(MAKE)
+modperl_lib_install:
+ cd "$(MODPERL_SRC)" && $(MAKE) install
+
modperl_src_clean:
cd "$(MODPERL_SRC)" && $(MAKE) clean
@@ -299,6 +302,13 @@
$string;
}
+sub MY::install {
+my $self = shift;
+my $string = $self->MM::install(@_);
+ModPerl::MM::add_dep(\$string, pure_install => 'modperl_lib_install');
+$string;
+}
+
sub MY::clean {
my $self = shift;
my $string = $self->MM::clean(@_);
@@ -317,17 +327,6 @@
sub MY::post_initialize {
my $self = shift;
-
-#XXX: MakeMaker will try to unlink $(APACHE_LIBDIR)/$MODPERL_LIB
-#during 'make' and probably 'make clean' as well
-#need to find another way to install libmodperl.so
-
-# install libmodperl.so
-#if ($build->{MP_USE_DSO}) {
-#my $MODPERL_LIB = join '.', $build->{MP_LIBNAME}, 'so';
-#$self->{PM}->{"src/modules/perl/$MODPERL_LIB"} =
-#"\$(APACHE_LIBDIR)/$MODPERL_LIB";
-#}
#up one from the Apache2/ subdir
#so it can be found for 'use Apache2 ()'
1.72 +10 -1 modperl-2.0/lib/Apache/Build.pm
Index: Build.pm
===
RCS file: /home/cvs/modperl-2.0/lib/Apache/Build.pm,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -r1.71 -r1.72
--- Build.pm 2001/11/02 17:23:54 1.71
+++ Build.pm 2001/11/02 17:59:05 1.72
@@ -738,7 +738,7 @@
my $mm = bless {}, 'MM';
$mm->init_others;
-for (qw(rm_f mv ld ar)) {
+for (qw(rm_f mv ld ar cp test_f)) {
my $val = $mm->{"\U$_"};
if ($val) {
mm_replace(\$val);
@@ -858,6 +858,11 @@
$self->{MODPERL_LIB_SHARED} :
$self->{MODPERL_LIB_STATIC});
+for my $q (qw(LIBEXECDIR)) {
+print $fh $self->canon_make_attr("AP_$q",
+ $self->apxs(-q => $q));
+}
+
my $xs_targ = $self->make_xs($fh);
print $fh <<'EOF';
@@ -872,6 +877,10 @@
all: lib
lib: $(MODPERL_LIB)
+
+install:
+ $(MODPERL_TEST_F) $(MODPERL_LIB_SHARED) && \
+ $(MODPERL_CP) $(MODPERL_LIB_SHARED) $(MODPERL_AP_LIBEXECDIR)
.SUFFIXES: .xs .c $(MODPERL_OBJ_EXT) .lo .i .s
cvs commit: modperl-2.0 Makefile.PL
dougm 01/11/02 09:33:46
Modified:.Makefile.PL
Log:
XXX: MakeMaker will try to unlink $(APACHE_LIBDIR)/$MODPERL_LIB
during 'make' and probably 'make clean' as well
need to find another way to install libmodperl.so
Revision ChangesPath
1.52 +9 -5 modperl-2.0/Makefile.PL
Index: Makefile.PL
===
RCS file: /home/cvs/modperl-2.0/Makefile.PL,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- Makefile.PL 2001/11/02 17:31:33 1.51
+++ Makefile.PL 2001/11/02 17:33:46 1.52
@@ -318,12 +318,16 @@
sub MY::post_initialize {
my $self = shift;
+#XXX: MakeMaker will try to unlink $(APACHE_LIBDIR)/$MODPERL_LIB
+#during 'make' and probably 'make clean' as well
+#need to find another way to install libmodperl.so
+
# install libmodperl.so
-if ($build->{MP_USE_DSO}) {
-my $MODPERL_LIB = join '.', $build->{MP_LIBNAME}, 'so';
-$self->{PM}->{"src/modules/perl/$MODPERL_LIB"} =
-"\$(APACHE_LIBDIR)/$MODPERL_LIB";
-}
+#if ($build->{MP_USE_DSO}) {
+#my $MODPERL_LIB = join '.', $build->{MP_LIBNAME}, 'so';
+#$self->{PM}->{"src/modules/perl/$MODPERL_LIB"} =
+#"\$(APACHE_LIBDIR)/$MODPERL_LIB";
+#}
#up one from the Apache2/ subdir
#so it can be found for 'use Apache2 ()'
cvs commit: modperl-2.0 Makefile.PL
dougm 01/11/02 09:31:33
Modified:.Makefile.PL
Log:
no need to check exists $build->{MP_USE_DSO}
Revision ChangesPath
1.51 +1 -1 modperl-2.0/Makefile.PL
Index: Makefile.PL
===
RCS file: /home/cvs/modperl-2.0/Makefile.PL,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -r1.50 -r1.51
--- Makefile.PL 2001/10/22 18:19:35 1.50
+++ Makefile.PL 2001/11/02 17:31:33 1.51
@@ -319,7 +319,7 @@
my $self = shift;
# install libmodperl.so
-if (exists $build->{MP_USE_DSO} && $build->{MP_USE_DSO}) {
+if ($build->{MP_USE_DSO}) {
my $MODPERL_LIB = join '.', $build->{MP_LIBNAME}, 'so';
$self->{PM}->{"src/modules/perl/$MODPERL_LIB"} =
"\$(APACHE_LIBDIR)/$MODPERL_LIB";
cvs commit: modperl-2.0/lib/Apache Build.pm
dougm 01/11/02 09:23:54
Modified:lib/Apache Build.pm
Log:
os cflags fixups need happen in perl_ccopts so generated Makefile.PLs get the changes
Revision ChangesPath
1.71 +9 -7 modperl-2.0/lib/Apache/Build.pm
Index: Build.pm
===
RCS file: /home/cvs/modperl-2.0/lib/Apache/Build.pm,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -r1.70 -r1.71
--- Build.pm 2001/10/22 03:57:59 1.70
+++ Build.pm 2001/11/02 17:23:54 1.71
@@ -195,14 +195,21 @@
}
sub perl_ccopts {
-shift->strip_lfs(" $Config{ccflags} ");
+my $cflags = shift->strip_lfs(" $Config{ccflags} ");
+
+my $fixup = \&{"ccopts_$^O"};
+if (defined &$fixup) {
+$fixup->(\$cflags);
+}
+
+$cflags;
}
sub ccopts_hpux {
my $cflags = shift;
#return if $Config{cc} eq 'gcc'; #XXX?
return if $$cflags =~ /(-Ae|\+e)/;
-$$cflags .= " -Ae";
+$$cflags .= " -Ae ";
}
sub ccopts {
@@ -210,11 +217,6 @@
my $cflags = $self->perl_ccopts . ExtUtils::Embed::perl_inc() .
$self->ap_ccopts;
-
-my $fixup = \&{"ccopts_$^O"};
-if (defined &$fixup) {
-$fixup->(\$cflags);
-}
$cflags;
}
Re: moving modperl-site rep into modperl-docs rep
Gerald Richter wrote: >> - the package handles links so we have no problem linking to e.g. >>perl.apache.org/dist/ >> > > ok, so we have the possibility to use content that is not part of the docset yup. >> - embperl site, I suppose it can be folded into the docset, if Gerald >>doesn't mind. >> > > For the Embperl site I have slightly different plans. There is a redesign > already on the road for a couple of time, I just didn't have the time to > finish and upload it. I have followed the discussion about the docset thing. > I like your docset idea, but I have also own ideas which build on the new > features of Embperl (namly XML & XSLT) Hopefully your docset tool is modular > enough that TT is only used for rendering, so it would be maybe possible to > plug Embperl, instead of TT ? (of course it doesn't would look nice if the > Embperl website says "powered by TemplateToolkit :-) > > so for now we maybe can simply keep the modperl-site cvs and use it only for > Embperl (and maybe the dist dir). 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. 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. BTW, what's the source format that you use for embperl? may be it can just plug into the docset system, and then we can keep it under the same roof. _ 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
> > With my proposal we will have to do: >on our machines: >1. cvs up >2. apply changes >3. cvs ci >on apache.org: >4. cvs up >5. bin/build > > so there is one extra step to do. Is this OK? > For the modperl site that would be ok for me. (Since everything is done for me by a Perl script, is doesn't matter if there is an addtional step :-) > issues: > >- need to install TemplateToolkit and a few other packages on > apache.org :( I guess we can do it locally, I don't want to pester Brian. Should be no problem >- the package handles links so we have no problem linking to e.g. > perl.apache.org/dist/ ok, so we have the possibility to use content that is not part of the docset >- embperl site, I suppose it can be folded into the docset, if Gerald > doesn't mind. For the Embperl site I have slightly different plans. There is a redesign already on the road for a couple of time, I just didn't have the time to finish and upload it. I have followed the discussion about the docset thing. I like your docset idea, but I have also own ideas which build on the new features of Embperl (namly XML & XSLT) Hopefully your docset tool is modular enough that TT is only used for rendering, so it would be maybe possible to plug Embperl, instead of TT ? (of course it doesn't would look nice if the Embperl website says "powered by TemplateToolkit :-) so for now we maybe can simply keep the modperl-site cvs and use it only for Embperl (and maybe the dist dir). 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 -
rfc: moving modperl-site rep into modperl-docs rep
This is an important change that I want to make, so please let me know if don't feel comfortable with my proposal. I've developed a package that can handle a docset of sources (in pod and html currently, more formats to come) and generate an output in html/ps/pdf (more formats to come). It should be very simple to manage the source docset. The docsets can be nested. Therefore I propose to merge documentation with mod_perl site and make it one source docset, which is all properly linked and has an easy navigation and buildable from one spot. That's why I suggest to remove the modperl-site cvs repository and add the few docs from the site that we have to the modperl-docs rep. Alternatively, we can nest modperl-docs rep inside modperl-site rep on checkout. Currently to update the site we do: on our machines: 1. cvs up 2. apply changes 3. cvs ci on apache.org: 4. cvs up With my proposal we will have to do: on our machines: 1. cvs up 2. apply changes 3. cvs ci on apache.org: 4. cvs up 5. bin/build so there is one extra step to do. Is this OK? issues: - need to install TemplateToolkit and a few other packages on apache.org :( I guess we can do it locally, I don't want to pester Brian. - the package handles links so we have no problem linking to e.g. perl.apache.org/dist/ - embperl site, I suppose it can be folded into the docset, if Gerald doesn't mind. - anything else? p.s. please don't ask me about the code, as soon as I put it in a better shape, I'll announce it here: http://www.template-toolkit.org/mailman/listinfo/template-docset _ 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/
[preview 2] new mod_perl site concept
Those that are on the docset-templates list know that I'm moving on with the new docset building code, I'm going to release it very soon now. Here is a second preview of the site: http://www.apache.org/~stas/newsite/index.html As usual disregard the content, just say if you see something wrong with navigation widgets, concepts in general. If everything is cool, I'll start filling it with the real content. Also see another email that I'll send in a sec. _ 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/
cvs commit: modperl-site/embperl Changes.pod.1.html
richter 01/11/02 02:16:23 Modified:embperl Changes.pod.1.html Log: Embperl Webpages - Changes Revision ChangesPath 1.228 +14 -2 modperl-site/embperl/Changes.pod.1.html Index: Changes.pod.1.html === RCS file: /home/cvs/modperl-site/embperl/Changes.pod.1.html,v retrieving revision 1.227 retrieving revision 1.228 diff -u -r1.227 -r1.228 --- Changes.pod.1.html2001/09/09 19:04:38 1.227 +++ Changes.pod.1.html2001/11/02 10:16:23 1.228 @@ -21,7 +21,7 @@ [HOME] [CONTENT] [PREV (Revision History - Content)] [NEXT (1.3.3 (RELEASE) 6. Juni 2001)] -Last Update: Sun Sep 9 21:08:01 2001 (MET) +Last Update: Fri Nov 2 11:26:22 2001 (MET) NOTE: This version is only available via "CVS" @@ -36,7 +36,8 @@ with POSTed data reported by Lukas Zapletal. - Display correct Apache module name in Makefile.PL when requesting path for Apache module. Patch from James Lee. - - New session handling using Apache::SessionX + - New session handling using Apache::SessionX. (This also + fixes problem with MD5 and Perl 5.6.1) - Fixed a bug that cause file-uploads to fail for the first request to a file when running under EmbperlObject. Reported by Thoren Johne. @@ -49,6 +50,8 @@ - If Perl's STDOUT and/or STDIN are tied to any package, Embperl now calls the Perl methods PRINT and READ for doing I/O. This currently only works, when not running under mod_perl. + - Embperl can now run under FastCGI. Use embpfastcgi.pl instead of + embpcgi.pl. - Delete unnecessary PerlFixupHandler from httpd.conf.src for make test. Reported by David Merberg. - Add undef to %idat for select tag with nothing selected if @@ -57,6 +60,15 @@ Problem reported by Kee Hinckley. - Embperl can now use encrypted sourcefiles. See crypto/README for details. + - Embperl can now be installed as Apache and non Apache version on the + same system. This is neccessary to work on Windows in- and outside of + Apache. + - Fixed a linkage problem with symbol embperl_module, first reported + by GustavKristoffer Ek. + - error message now always contain a filename. + - Added optShowBacktrace to enable backtrace of filename in error messages + - Removed obsolete debug flags dbgDisableCache, dbgWatchScalar, + dbgEarlyHttpHeader [HOME] [CONTENT] [PREV (Revision History - Content)] [NEXT (1.3.3 (RELEASE) 6. Juni 2001)] ___
