Menu
▾
▴
slashcode-development — This list is for development of slashcode, no install questions please.
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(29) |
Dec
(101) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(90) |
Feb
(101) |
Mar
(173) |
Apr
(141) |
May
(38) |
Jun
(28) |
Jul
(14) |
Aug
(7) |
Sep
(3) |
Oct
(7) |
Nov
(15) |
Dec
(9) |
| 2002 |
Jan
(2) |
Feb
(5) |
Mar
(11) |
Apr
|
May
(4) |
Jun
(6) |
Jul
(7) |
Aug
(12) |
Sep
(8) |
Oct
(1) |
Nov
(4) |
Dec
(7) |
| 2003 |
Jan
(7) |
Feb
(1) |
Mar
(9) |
Apr
(2) |
May
(3) |
Jun
(4) |
Jul
(19) |
Aug
(4) |
Sep
(8) |
Oct
(30) |
Nov
(25) |
Dec
(22) |
| 2004 |
Jan
(6) |
Feb
(12) |
Mar
|
Apr
(2) |
May
|
Jun
(10) |
Jul
(18) |
Aug
(2) |
Sep
(4) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2005 |
Jan
(8) |
Feb
(4) |
Mar
(6) |
Apr
(5) |
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(4) |
Nov
(3) |
Dec
|
| 2006 |
Jan
(9) |
Feb
(6) |
Mar
(11) |
Apr
|
May
(2) |
Jun
|
Jul
(2) |
Aug
(10) |
Sep
(8) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(7) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jason R. <ja...@ar...> - 2000-12-19 00:35:19
|
That's my whole problem... $r is not set. I don't even understand
why I need a request object when all I want to do is to access the
database. I would be ecstatic if I could just get a hold of the
virtual username. Correct me if I am wrong, but I thought that the
request object would only be valid if there was a request. I have
this problem when I start the server, because there is no request. I
also had luck with this code:
my $virtuser = "slash";
my $driver = DBIx::Password->connect($virtuser);
my $sth = $driver->prepare("
SELECT name,location FROM table_map
");
$sth->execute();
while(my ($name,$location) = $sth->fetchrow_array()){
$Slash::TableMap::table_map->{$name} = "$location";
}
$driver->disconnect();
$Slash::TableMap::dirty=0;
It works perfectly... But, as you can see, I hard-coded the $virtuser
instead of getting the name of the one I need through the proper
channels. Is there an easy way to get the virtuser with out futzing
with the Apache->request object?
Jason
Brian Aker wrote:
> Jason Richey wrote:
> > When I try to initialize my table-map, I used this code:
> > 25 my $r = Apache->request;
> Check to see if $r is really set. Apache->request() is guarenteed
> in a handler because Apache::Registry sets it. You will notice
> that in the top of Slash::Apache::User::handler() that I set
> it. If I didn't then calls that rely on $r will find
> it unet.
>
> -Brian
>
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/mailman/listinfo/slashcode-development
--
"Jason C. Richey" <ja...@bo...>
|
|
From: Brian A. <br...@ta...> - 2000-12-18 22:41:29
|
Jason Richey wrote: > When I try to initialize my table-map, I used this code: > 25 my $r = Apache->request; Check to see if $r is really set. Apache->request() is guarenteed in a handler because Apache::Registry sets it. You will notice that in the top of Slash::Apache::User::handler() that I set it. If I didn't then calls that rely on $r will find it unet. -Brian |
|
From: Jason R. <ja...@ar...> - 2000-12-18 22:22:32
|
When I try to initialize my table-map, I used this code:
25 my $r = Apache->request;
26 my $cfg = Apache::ModuleConfig->get($r,'Slash::Apache');
27 my $db = getCurrentDB();
28 $Slash::TableMap::table_map = $db->getTables();
29 $Slash::TableMap::dirty=0;
and I get:
Argument is not an Apache or Apache::Server object at
/usr/lib/perl5/site_perl/5.005/i586-linux/Slash/TableMap.pm line 26.
After playing with it and having no luck, I changed my code to read:
my $r = Apache->request;
if ($r){
my $db;
my $cfg = Apache::ModuleConfig->get($r,'Slash::Apache');
$db = getCurrentDB();
$Slash::TableMap::table_map = $db->getTables();
$Slash::TableMap::dirty=0;
}
so now I just get a bunch of stuff at startup that basically says that
the table named '' doesn't exist (since my table-map didn't load at
startup). It seems to work after that.
Jason Richey
Brian Aker wrote:
> Jason Richey wrote:
> > appreciated... Plenty of error messages fly by on startup because the
> > tablemap doesn't get initialized, but everything settles down and
> > works after that. I'll get a patch together against the last release
> > (I'm working with a pretty old version) and submit it for everyone's
> > input.
> What are the errors you are getting?
> -Brian
>
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/mailman/listinfo/slashcode-development
--
"Jason C. Richey" <ja...@bo...>
|
|
From: Brian A. <br...@ta...> - 2000-12-18 22:02:57
|
Jason Richey wrote: > appreciated... Plenty of error messages fly by on startup because the > tablemap doesn't get initialized, but everything settles down and > works after that. I'll get a patch together against the last release > (I'm working with a pretty old version) and submit it for everyone's > input. What are the errors you are getting? -Brian |
|
From: Jason R. <ja...@ar...> - 2000-12-18 21:32:05
|
I am nearly done with the module that allows table-mapping. It seems to work correctly with one small problem: When apache starts, the module attempts to connect to mysql to initialize it's mapping of table names. I am using the getCurrentDB call to get this done. Unfortunately, it runs into some problems because it is so early in the execution. I don't know very much about how all of the Apache stuff and other modules interact at startup, so any help is appreciated... Plenty of error messages fly by on startup because the tablemap doesn't get initialized, but everything settles down and works after that. I'll get a patch together against the last release (I'm working with a pretty old version) and submit it for everyone's input. Jason Richey P.S. In case I wasn't clear, table-mapping is the term I'm using to say that tables are cached into a hash, with their current (standard) names as the key, and their true location/name as the value. The module exports a table-lookup function that returns true location/name. It'll be useless to many people, but VERY nice for others. -- "Jason C. Richey" <ja...@bo...> |
|
From: Chris N. <pu...@po...> - 2000-12-18 20:18:30
|
OK, Brian finished the getTemplate() changes late last week, and I just now committed my half of the changes, which essentially amount to: * changing all of the template names that had page as part of the name, so "pollBooth-main" is just "main" (changed these in all the mysql dumps [except for Simple Story] and in all the code) * changed slashDisplay to also accept a new "Page" parameter, so you can define the Page to be different from the default page. This is used for menus, currently (menu templates are all in the "menu" page, so the function that calls the menu templates sets Page => 'menu'). * changed slashDisplay to not try to figure out which template to display, but to just pass the name on to the Template object * changed Slash::Display::Provider to get a unique ID for a given name (getTemplate() does the rest of the work), and to use that ID for all caching, lookups, etc. * added a getTemplateByID to MySQL.pm so we could retrieve the correct template by its ID * removed getData() from all .pl files, and exported it from Slash.pm (hi, Brian!) ... note that there is no longer a Slash-data template, but it is now the "data" template in page "misc" * added fix from Steinar Gunderson to make slashDisplay work again under non-Apache processes That about covers it. You must do a reinstall of the code and data at the same time, or it will all come tumbling down. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
|
From: Jason R. <ja...@ar...> - 2000-12-18 16:52:28
|
I started work on something that will solve this for you... I just have a few things to clean up on it. Basically, I wrote a module that exports a function to "lookup" a table. Then all table names can be changed as you please. It was originally intended so that I could use the same user information between multiple slash sites, but it seems that it might be right up your alley as well. Are you interested? Jason Richey CertIndex.com Webmaster wrote: > Namespaces are always good practice, db schemas are no different of course. > What would everyone think of prepending every table in slash with slash_ ? I > say this not only because some of Slash's tables interfere with our existing > schema and production systems, and also not because I assume others have had > this issue as well, but because it's the right thing to do. IMO anyway, of > course. So, what do you all think? > > Ciao, > k > > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/mailman/listinfo/slashcode-development -- "Jason C. Richey" <ja...@bo...> |
|
From: CertIndex.com W. <web...@ce...> - 2000-12-18 09:51:55
|
Namespaces are always good practice, db schemas are no different of course. What would everyone think of prepending every table in slash with slash_ ? I say this not only because some of Slash's tables interfere with our existing schema and production systems, and also not because I assume others have had this issue as well, but because it's the right thing to do. IMO anyway, of course. So, what do you all think? Ciao, k |
|
From: <mba...@he...> - 2000-12-18 06:38:26
|
On Sat, 16 Dec 2000, Brian Aker wrote: ba...@he...mba...@he... wrote: ba...@he...> mod perl 1.2.1 and apache 1.3.6 on YellowDog (ppc) linux, kernel 2.2.15. ba...@he...I would suggest first switching to apache 1.3.14 and mod_perl 1.24_01. ba...@he...You can find it here: ba...@he...http://perl.apache.org/dist/ ba...@he... ba...@he... -Brian ba...@he... ba...@he..._______________________________________________ ba...@he...Slashcode-development mailing list ba...@he...Sla...@li... ba...@he...http://lists.sourceforge.net/mailman/listinfo/slashcode-development ba...@he... OK so I think I've gone through the instructions a couple times now and done everything by the book. Now, when I try to start slashd I get this: [root@shiner slash]# /etc/rc.d/init.d/slashd start Starting slashd: ok. [root@shiner slash]# DBI->connect(database=slash;host=localhost) failed: Access denied for user: 'slash@localhost' (Using password: YES) at Slash.pm line 1189 Access denied for user: 'slash@localhost' (Using password: YES) at Slash.pm line 1189. Compilation failed in require at ./slashd line 637. why am I here? at ./slashd line 39 main::END() called at ./slashd line 0 require 0 called at ./slashd line 0 However I created all the databases per instruction, so I suppose perms should be correct?? vertainly (using webmin) user slash appears to have the proper perms. Could someone point mein the right direction? thanks- -mab |
|
From: Brian A. <br...@ta...> - 2000-12-16 20:06:24
|
mba...@he... wrote: > mod perl 1.2.1 and apache 1.3.6 on YellowDog (ppc) linux, kernel 2.2.15. I would suggest first switching to apache 1.3.14 and mod_perl 1.24_01. You can find it here: http://perl.apache.org/dist/ -Brian |
|
From: <mba...@he...> - 2000-12-16 08:42:15
|
Forgive me if this is in a faq somewhere, I can't find it (by all means
pls point me that direction if it exists)
I am trying to install as indicated in the INSTALL doc:
perl Makefile.PL APACHE_SRC=/where_you_have_the_source DO_HTTPD=
1 \
USE_APACI=1 PERL_MARK_WHERE=1 EVERYTHING=1 \
APACHE_PREFIX=/where_apache_will_be_installed
make
make test
make install
However, when I get to make, this happens:
/usr/bin/perl `/usr/bin/perl -MConfig -e 'print
$Config{privlibexp}'`/ExtUtils/xsubpp -typemap `/usr/bin/perl -MConfig -e
'print $Config{privlibexp}'`/ExtUtils/typemap Table.xs > Table.c
cc -I. -I../../include -I../../include/regex -I../../include/.././os/unix
-DLINUX=2 -DUSE_HSREGEX -fno-strict-aliasing -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.6.0/ppc-linux/CORE
-I. -I../.. -DUSE_PERL_SSI -DPERL_MARK_WHERE=1 -DMOD_PERL `/usr/bin/perl
-MExtUtils::Embed -e ccopts` -DNO_PERL_RESTART
-DMOD_PERL_VERSION=\"1.21\" -I./os/unix -I../../include -c -o
mod_perl.o mod_perl.c
mod_perl.c: In function `perl_handler':
mod_perl.c:783: `PL_siggv' undeclared (first use in this function)
mod_perl.c:783: (Each undeclared identifier is reported only once
mod_perl.c:783: for each function it appears in.)
make[3]: *** [mod_perl.o] Error 1
make[2]: *** [all] Error 1
make[1]: *** [subdirs] Error 1
make[1]: Leaving directory `/tmp/apache_1.3.6/src'
make: *** [apache_httpd] Error 2
[root@shiner mod_perl-1.21]#
mod perl 1.2.1 and apache 1.3.6 on YellowDog (ppc) linux, kernel 2.2.15.
|
|
From: Rael D. <ra...@or...> - 2000-12-15 20:01:18
|
Howdy, On Fri, 15 Dec 2000, Chris Nandor wrote: > At 11:18 -0800 2000.12.15, Rael Dornfest wrote: > >> >> introtext rss:item->rss:description > >> >> bodytext (more content than metadata, but up to you) > >> > >> Technically, introtext is not necessarily metadata either. introtext is > >> what appears on the main page, which may be the entire text of the story. > > > >Then introtext would definitely be appropriate for description if there is > >bodytext beyond. > > Well, it depends on the site. For some sites, introtext may be the entire > story, for others it may be only part of it. What we will probably do is > make it an option to include introtext as description. However, yes, if > anything is description, this is it. It's just that some sites -- like > Slashdot, probably -- won't be including introtext in its RSS. If it does, > it will only be the first $n characters. That's just fine... including a taste is all that's needed. > >> I don't think any of them would be too useful or interesting -- or we just > >> would not want to give out that information -- with the _possible_ > >> exception of hitparade. > > > >I believe the way to go would be to create a Slash module with all of this, > >yet decide on what (like HitParade) you'd like to make public. The rest > >could be included only for internal/cross-site use. Up to you, though. > > Well, first there are the texts, introtext, bodytext, and relatedtext. > Setting aside those, writestatus doesn't matter, displaystatus is obvious > (if you can see it, it is displaying :), commentstatus doesn't work. So I > only see hits and hitparade as being interesting for putting in the module. Cool. > So introtext would be description, bodytext would be some other main body > text field (there's gotta be something like this in SOME module, it is > going to be needed by anyone who wants to put a full story in the RSS > file), and relatedtext is some other field. It's up to you (or the site at hand). I'd have... introtext as description unless no bodytext else first sentence or 100 or so chars of bodytext There is work well underway on a "content" module at: http://www.egroups.com/message/rss-dev/1307 > >> Yeah, since in the case of Slashdot we don't want to give this text away, > >> we would probably at most give the first $n words or something. But > >> probably, we won't put this in at all, and just rely on > >> section/topic/department. > > > >The number one complaint (not that I can do much about it aside from point > >it out) from readers is the lack of descriptions on certain feeds. The > >title often is not quite enough to determine whether or not I'd like to > >follow the link. I'd _strongly_ suggest using introtext when there's a > >bodytext and the first 80-100 characters (minimum) of introtext when > >bodytext does not exist. > > Yes, this will be under consideration. Ta. > >> > <dc:date>${story-date}</dc:date> > >> > <dc:format>text/html</dc:format> > >> > <slash:department>${story_department}</slash:department> > >> > <slash:comments>${story_number_of_comments}</slash:comments> > >> > <slash:hits>${story_hits}</slash:hits> > >> > >> Yeah, we won't put hits in, that's private data. > > > >I'm assuming you mean story_hits, not the others? > > Yes. > > > >date will, along with > >subject, be the number one use of the Dublin Core module. Format isn't > >all that necessary since most RSS items are assumed to be text/html. > >Number of comments is nice and will be very useful in a more generalised > >popularity element in a more generalised module. > > Yep. > > > >Again, this is still being worked out so as to be in accordance with DC and > >RDF in general, so don't worry about it for now. Meerkat, for instance, will > >map your categories to its own ontology and shuffle the stories about as > >appropriate. > > > >Please do let me know if there's any more info I can provide. > > OK, but what I still don't know is how to create this Slash RSS module. > What do we do there? Thanks, 0. Subscribe to RSS-DEV at eGroups (digest and Web-only modes are available) at: http://www.egroups.com/group/rss-dev/ 1. Write up a proposal using the mod_ template at: http://www.egroups.com/files/rss-dev/Modules/Proposed/mod_.html Use one of the others as guidance; a nice simple example (and more than a little apropos) is: http://www.egroups.com/files/rss-dev/Modules/Proposed/mod_annotation.html 2. Save it as mod_slash.html to: http://www.egroups.com/files/rss-dev/Modules/Proposed/ 3. Drop a note to RSS-DEV (rs...@eg...) proposing the module. Be sure to use a subject line like "(Slash) Slashcode Module Proposal" so discussion can be nicely threaded thereafter. That's it. I think we have already built out the basics for one here -- I'm glad to work on it with you. Rael ------------------------------------------------------------------ Rael Dornfest ra...@or... Maven, http://www.oreillynet.com/~rael The O'Reilly Network http://meerkat.oreillynet.com ------------------------------------------------------------------ |
|
From: Chris N. <pu...@po...> - 2000-12-15 19:42:17
|
At 11:18 -0800 2000.12.15, Rael Dornfest wrote:
>> >> introtext rss:item->rss:description
>> >> bodytext (more content than metadata, but up to you)
>>
>> Technically, introtext is not necessarily metadata either. introtext is
>> what appears on the main page, which may be the entire text of the story.
>
>Then introtext would definitely be appropriate for description if there is
>bodytext beyond.
Well, it depends on the site. For some sites, introtext may be the entire
story, for others it may be only part of it. What we will probably do is
make it an option to include introtext as description. However, yes, if
anything is description, this is it. It's just that some sites -- like
Slashdot, probably -- won't be including introtext in its RSS. If it does,
it will only be the first $n characters.
>> I don't think any of them would be too useful or interesting -- or we just
>> would not want to give out that information -- with the _possible_
>> exception of hitparade.
>
>I believe the way to go would be to create a Slash module with all of this,
>yet decide on what (like HitParade) you'd like to make public. The rest
>could be included only for internal/cross-site use. Up to you, though.
Well, first there are the texts, introtext, bodytext, and relatedtext.
Setting aside those, writestatus doesn't matter, displaystatus is obvious
(if you can see it, it is displaying :), commentstatus doesn't work. So I
only see hits and hitparade as being interesting for putting in the module.
So introtext would be description, bodytext would be some other main body
text field (there's gotta be something like this in SOME module, it is
going to be needed by anyone who wants to put a full story in the RSS
file), and relatedtext is some other field.
>Then section would be better as slash:section and topic as dc:subject.
Agreed.
>> Yeah, since in the case of Slashdot we don't want to give this text away,
>> we would probably at most give the first $n words or something. But
>> probably, we won't put this in at all, and just rely on
>> section/topic/department.
>
>The number one complaint (not that I can do much about it aside from point
>it out) from readers is the lack of descriptions on certain feeds. The
>title often is not quite enough to determine whether or not I'd like to
>follow the link. I'd _strongly_ suggest using introtext when there's a
>bodytext and the first 80-100 characters (minimum) of introtext when
>bodytext does not exist.
Yes, this will be under consideration.
>> > <dc:date>${story-date}</dc:date>
>> > <dc:format>text/html</dc:format>
>> > <slash:department>${story_department}</slash:department>
>> > <slash:comments>${story_number_of_comments}</slash:comments>
>> > <slash:hits>${story_hits}</slash:hits>
>>
>> Yeah, we won't put hits in, that's private data.
>
>I'm assuming you mean story_hits, not the others?
Yes.
>date will, along with
>subject, be the number one use of the Dublin Core module. Format isn't
>all that necessary since most RSS items are assumed to be text/html.
>Number of comments is nice and will be very useful in a more generalised
>popularity element in a more generalised module.
Yep.
>Again, this is still being worked out so as to be in accordance with DC and
>RDF in general, so don't worry about it for now. Meerkat, for instance, will
>map your categories to its own ontology and shuffle the stories about as
>appropriate.
>
>Please do let me know if there's any more info I can provide.
OK, but what I still don't know is how to create this Slash RSS module.
What do we do there? Thanks,
--
Chris Nandor pu...@po... http://pudge.net/
Open Source Development Network pu...@os... http://osdn.com/
|
|
From: Rael D. <ra...@or...> - 2000-12-15 19:18:42
|
Howdy, A quick note about XML::RSS. I've patched it to be in compliance with RSS 1.0 Release and understand the Dublin Core and Syndication modules. I've submitted the patch to Jonathan Eisenzopf and am expecting him to release it any day now. So Slashcode will be able to emit (and parse) 0.9, 0.91, and 1.0 w/ modules. On Mon, 11 Dec 2000, Chris Nandor wrote: > >You need to determine what's necessary/useful from the rest of the fields, > >and it makes sense at least initially to put these into a slashcode module > >... again, see my sample below. At some point you might find that a > >more generalised module exists to house some of this, but that's not the > >case right now. Fact is that widespread use of an ad-hoc module will > >heavily influence any such generalised module. > > Yeah, we could either try to come up with a "Slash" module, or some more > general module. I think a Slash module would be a great start, afterwhich submitting it to RSS-DEV as direction for a more generalised Weblog/Slash/Portal module. > >Ok, so first a little mapping between the fields you've provided and > >the RSS core (rss), Dublin Core (dc), and Syndication (syn) modules, > >and a made-up Slashcode (slash) module... > > > >> site > >> ---- > >> URL rss:channel->rss:link > http://slashdot.org/ > > >> name rss:channel->rss:title > Slashdot > > >> language rss:channel->dc:language > en-us > > >> slogan (description) rss:channel->rss:description > News for Nerds. Stuff that matters. > > >> contact email rss:channel->dc:creator > so...@sl... Perfect. > >> stories > >> ------- > > I'll list three stories' worth of data for examples. > > > >> URL (story ID) rss:item->rss:link > http://slashdot.org/comments.pl?sid=00/12/11/152211 > http://slashdot.org/comments.pl?sid=00/12/09/2329239 > http://slashdot.org/comments.pl?sid=00/12/09/1933249 > > >> title rss:item->rss:title > New P2P tool Using... IRC? > Gifts For Geeks > Could Tesla's Broadcast Power System Work? > > >> author rss:item->dc:creator > Hemos > CmdrTaco > Cliff > > >> section rss:item->dc:subject > articles > features > askslashdot > > >> topic rss:item->dc:subject (either/or/combined) > internet > xmas > news Topic does indeed seem a better fit for dc:subject. > >> department rss:item->slash:department > interesting-idea > cheesy-alliteration-is-where-it's-at > relevant-ideas-from-one-of-science's-greatest > > >> number of comments rss:item->slash:comments > 86 > 184 > 28 > > >> date rss:item->dc:date > 2000-12-11 15:11:51 > 2000-12-11 11:06:02 > 2000-12-10 23:01:49 > > > > >> other (probably not useful, or should not be included): > > As noted, I probably would not want any of the below included, but added in > all the story data we have just for kicks, in case I missed something. > > >> introtext rss:item->rss:description > >> bodytext (more content than metadata, but up to you) > > Technically, introtext is not necessarily metadata either. introtext is > what appears on the main page, which may be the entire text of the story. Then introtext would definitely be appropriate for description if there is bodytext beyond. > >> writestatus what is this? > > This is a flag determining whether a new static page should be written out > (the story has been changed since last time a static page has been written). > > >> hits rss:item->slash:hits > > How many hits the story has received. > > >> displaystatus what is this? > > Whether the story should be displayed on the home page, in a particular > section, or not at all. > > >> commentstatus what is this? > > Whether comments can be posted. Not used. > > >> hitparade what is this? > > A list of how many comments at each "score" level. So for > "86,58,37,18,5,4,2", that would mean there are 86 total comments, 58 > comments with scores of 0 and up, 37 1 and up, 18 2, 5 3, 4 4, and 2 at 5 > and up. > > This is the info you see when you are in a story and you click the > Threshold popup menu. > > > >> relatedtext sounds interesting... what is it? > > This is for the "Related Links" box next to a story. > > > >> extratext sounds interesting... what is it? > > This is not really used. > > > >I'm afraid I don't know what some of the above are or how useful they > >would be, but they'd probably be best in a Slashcode module if deemed > >useful/interesting. > > I don't think any of them would be too useful or interesting -- or we just > would not want to give out that information -- with the _possible_ > exception of hitparade. I believe the way to go would be to create a Slash module with all of this, yet decide on what (like HitParade) you'd like to make public. The rest could be included only for internal/cross-site use. Up to you, though. > >If section and story are mutually exclusive, then have the appropriate > >one be dc:subject. If they co-occur, have the most descriptive one > >be dc:subject and the one more for internal use by slash:{topic/section}. > > Well, topic is the most descriptive. Section is more for stuff like "Ask > Slashdot", where you can have separate sections on the site. Topic is what > is more like Subject. Then section would be better as slash:section and topic as dc:subject. > >The following sample template uses ${} to indicate the fields I've slotted > >in as mapped above... > > > ><?xml version="1.0" encoding="iso-8859-1"?> > ><rdf:RDF > > xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" > > xmlns:dc="http://purl.org/dc/elements/1.1/" > > xmlns:slash="http://slashcode.net/rss/elements/1.0/" > > xmlns="http://purl.org/rss/1.0/" > >> > > > > <channel rdf:about="${site_url}"> > > <title>${site_name}</title> > > <link>${site_url}</link> > > <description>${site_slogan}</description> > > <dc:rights>Copyright 2000, ${site_name}</dc:rights> > > <dc:creator>${site_contact_email}</dc:publisher> > > <dc:publisher>${site_name}</dc:publisher> > > Actually, this would probably be "OSDN" in the case of Slashdot, since OSDN > is the publisher of the site. Makes sense. > > <dc:language>${site_language}</dc:language> > > > > <items> > > <rdf:Seq> > > <rdf:li rdf:resource="${story_url}" /> > > ... > > <rdf:li rdf:resource="${story_url}" /> > > </rdf:Seq> > > </items> > > So <items> lists the individual items which are then described further below? Yes. Think of it as a table of contents. It's the the only real RDF bit (matching items to channels via the rdf:about) in RSS 1.0. It's also incredibly useful when parsing the document as regular XML to determine whether or not anything is new without even going beyond <channel>. > > </channel> > > > > <item rdf:about="${story_url}"> > > <title>${story_title}</title> > > <link>${story_url}</link> > > <description>${story_intro_text}</description> > > Yeah, since in the case of Slashdot we don't want to give this text away, > we would probably at most give the first $n words or something. But > probably, we won't put this in at all, and just rely on > section/topic/department. The number one complaint (not that I can do much about it aside from point it out) from readers is the lack of descriptions on certain feeds. The title often is not quite enough to determine whether or not I'd like to follow the link. I'd _strongly_ suggest using introtext when there's a bodytext and the first 80-100 characters (minimum) of introtext when bodytext does not exist. > > <dc:creator>${story_author}</dc:creator> > > <dc:subject>${story_section}: ${story_topic}</dc:subject> > > Perhaps: > <dc:subject>${story_topic}</dc:subject> > <slash:section>${story_section}</slash:section> Yes. > > <dc:language>${story/site_language}</dc:language> > > Right now, we just have site language support. That's just fine if specified in the channel's dc:language element. > > <dc:date>${story-date}</dc:date> > > <dc:format>text/html</dc:format> > > <slash:department>${story_department}</slash:department> > > <slash:comments>${story_number_of_comments}</slash:comments> > > <slash:hits>${story_hits}</slash:hits> > > Yeah, we won't put hits in, that's private data. I'm assuming you mean story_hits, not the others? date will, along with subject, be the number one use of the Dublin Core module. Format isn't all that necessary since most RSS items are assumed to be text/html. Number of comments is nice and will be very useful in a more generalised popularity element in a more generalised module. > > ... > > </item> > > > > ... > > > ></rdf:RDF> > > > >Again, a template will be much easier to refine with a sample record or > >three from your database. And, of course, quite a bit of this needs > >only a little artistic license. > > > >Hope this provides a useful start. > > Yes, it does. I think what you've given us helps a lot. We need XML::RSS > to support 1.0 of course, Again, I'm just waiting on Jonathan's release of my update. What is the (even arbitrary) dealine? > but we also need to find a way to tell the RSS > what each topic (subject) and section means. How does that work? Do we > create some document that describes the possible sections and topics? This has been debated on RSS-DEV for some time -- using resources as subject rather than just string literals. For now, simply use string literals. The future of dc:subject is probably more along the lines of: <dc:subject> <rdf:Description> <taxo:topic rdf:resource="http://slashdot.org/search.pl?topic=internet" /> <rdf:value>internet</rdf:value> </rdf:Description> </dc:subject> This is akin to saying "the subject here is 'internet', as exemplified by the stuff you'll find at http://slashdot.org/search.pl?topic=internet". The same would be true for section in a slash module: <slash:section> <rdf:Description> <slash:topic rdf:resource="http://slashdot.org/index.pl?section=askslashdot" /> <rdf:value>askslashdot</rdf:value> </rdf:Description> </slash:section> "This story is in the "askslashdot" section, as exemplified by the stuff at http://slashdot.org/index.pl?section=askslashdot" This is termed "dumb down" and is the way the Dublin Core group are probably going. If you just need a string literal for your application, usethe rdf:value. If you want to provide a link, use the resouce provided. Again, this is still being worked out so as to be in accordance with DC and RDF in general, so don't worry about it for now. Meerkat, for instance, will map your categories to its own ontology and shuffle the stories about as appropriate. Please do let me know if there's any more info I can provide. Rael ------------------------------------------------------------------ Rael Dornfest ra...@or... Maven, http://www.oreillynet.com/~rael The O'Reilly Network http://meerkat.oreillynet.com ------------------------------------------------------------------ |
|
From: Brian A. <br...@ta...> - 2000-12-15 16:42:51
|
so...@sp... wrote:
> my $virtual1 = {
> 'slash' => {
> 'username' => 'slash',
> 'password' => 'kaparma..',
> 'port' => '5432',
> 'database' => 'slash',
> 'attributes' => {},
> 'connect' => 'DBI:Pg:database=slash;host=localhost',
> 'driver' => 'Pg',
> 'host' => 'localhost'
> }
> };
What version of DBIx::Password are you using? The above looks more like
the output
from an older version for a PostgreSQL entry (or one entered by hand
incorrectly).
Reinstlal DBIx::Password and do a make install. Follow the directions
during the
install (and make sure you have already done a createdb on the database
and
setup the database user).
> oh, when i change 'driver' => 'PostgreSQL' it spits out:
There is no such driver as PostgreSQL (its named Pg).
-Brian
|
|
From: Alessio B. <al...@al...> - 2000-12-15 08:49:41
|
so...@sp... wrote: > my problem with setting slash (1.1.1-bender) up on postgresql is what follows. > 'connect' => 'DBI:Pg:database=slash;host=localhost', A connect string for PostgreSQL is slightly different. Reads 'DBI:Pg:dbname=slash;host=localhost;port=5432', cannot remember if the port is needed if it's 5432. > Can't call method "quote" on an undefined value at I think the db connection doesn't get initialized. > /usr/lib/perl5/site_perl/5.005/i386-linux/Slash/DB/MySQL.pm line 2817. Why it's in MySQL.pm? > oh, when i change 'driver' => 'PostgreSQL' it spits out: > DRIVER Pg:slash > Picking PostgreSQL > Major Mojo Bad things > Can't read $DBI::errstr, last handle unknown or destroyed at /usr/lib/perl5/site_perl/5.005/i386-linux/Slash/DB/Utility.pm line 44. > unable to connect to MySQL: Can't connect(DBI:PostgreSQL slash kaparma.. HASH(0x821dcc8)), no database driver specified and DBI_DSN env var not set at /usr/lib/perl5/site_perl/5.005/DBIx/Password.pm line 31 This makes more sense, it should say anyway 'unable to connect to PostgreSQL', but maybe it's hardwired in the code? I will have a try, but I think you should change the connect string. -- Alessio F. Bragadini al...@al... APL Financial Services http://village.albourne.com Nicosia, Cyprus phone: +357-2-755750 "It is more complicated than you think" -- The Eighth Networking Truth from RFC 1925 |
|
From: <so...@sp...> - 2000-12-15 08:38:22
|
hey,
my problem with setting slash (1.1.1-bender) up on postgresql is what follows.
my DBIx::Password is:
my $virtual1 = {
'slash' => {
'username' => 'slash',
'password' => 'kaparma..',
'port' => '5432',
'database' => 'slash',
'attributes' => {},
'connect' => 'DBI:Pg:database=slash;host=localhost',
'driver' => 'Pg',
'host' => 'localhost'
}
};
and apache gives me:
DRIVER Pg:slash
Picking PostgreSQL
Syntax error on line 39 of /home/opt/apache/conf/virtual.conf:
Can't call method "quote" on an undefined value at /usr/lib/perl5/site_perl/5.005/i386-linux/Slash/DB/MySQL.pm line 2817.
this probably is a DBIx configuration problem, but i have no idea how to fix
it.
oh, when i change 'driver' => 'PostgreSQL' it spits out:
DRIVER Pg:slash
Picking PostgreSQL
Major Mojo Bad things
Can't read $DBI::errstr, last handle unknown or destroyed at /usr/lib/perl5/site_perl/5.005/i386-linux/Slash/DB/Utility.pm line 44.
unable to connect to MySQL: Can't connect(DBI:PostgreSQL slash kaparma.. HASH(0x821dcc8)), no database driver specified and DBI_DSN env var not set at /usr/lib/perl5/site_perl/5.005/DBIx/Password.pm line 31
:
Wojtek
|
|
From: <mba...@he...> - 2000-12-15 08:10:26
|
Forgive me if this is in a faq somewhere, I can't find it (by all means
pls point me that direction if it exists)
I am trying to install as indicated in the INSTALL doc:
perl Makefile.PL APACHE_SRC=/where_you_have_the_source DO_HTTPD=
1 \
USE_APACI=1 PERL_MARK_WHERE=1 EVERYTHING=1 \
APACHE_PREFIX=/where_apache_will_be_installed
make
make test
make install
However, when I get to make, this happens:
/usr/bin/perl `/usr/bin/perl -MConfig -e 'print
$Config{privlibexp}'`/ExtUtils/xsubpp -typemap `/usr/bin/perl -MConfig -e
'print $Config{privlibexp}'`/ExtUtils/typemap Table.xs > Table.c
cc -I. -I../../include -I../../include/regex -I../../include/.././os/unix
-DLINUX=2 -DUSE_HSREGEX -fno-strict-aliasing -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.6.0/ppc-linux/CORE
-I. -I../.. -DUSE_PERL_SSI -DPERL_MARK_WHERE=1 -DMOD_PERL `/usr/bin/perl
-MExtUtils::Embed -e ccopts` -DNO_PERL_RESTART
-DMOD_PERL_VERSION=\"1.21\" -I./os/unix -I../../include -c -o
mod_perl.o mod_perl.c
mod_perl.c: In function `perl_handler':
mod_perl.c:783: `PL_siggv' undeclared (first use in this function)
mod_perl.c:783: (Each undeclared identifier is reported only once
mod_perl.c:783: for each function it appears in.)
make[3]: *** [mod_perl.o] Error 1
make[2]: *** [all] Error 1
make[1]: *** [subdirs] Error 1
make[1]: Leaving directory `/tmp/apache_1.3.6/src'
make: *** [apache_httpd] Error 2
[root@shiner mod_perl-1.21]#
mod perl 1.2.1 and apache 1.3.6 on YellowDog (ppc) linux, kernel 2.2.15.
Thanks-
-mab
|
|
From: Brian A. <br...@ta...> - 2000-12-14 16:59:52
|
Wojtek wrote: > anyone actually using slashcode with postgresql (v7.0.2 in my case). > i'm trying to set it up, and going to setup a nice big site on it, but > i'm having trouble setting it up - it dies with an error in MySQL.pm. > is anyone deep into the subject enough to assist me? Just go on a head and post to the list your problems. -Brian |
|
From: Chris N. <pu...@po...> - 2000-12-14 15:38:56
|
I found out why it was broken. It needs an entry for userlogin in the blocks table. I removed it when I made it a template. I have added in (commit soon) a dummy block for it as a placeholder so it can be shown in the slashboxes. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
|
From: Wojtek <so...@ne...> - 2000-12-14 14:25:18
|
hey, anyone actually using slashcode with postgresql (v7.0.2 in my case). i'm trying to set it up, and going to setup a nice big site on it, but i'm having trouble setting it up - it dies with an error in MySQL.pm. is anyone deep into the subject enough to assist me? greetings, Wojtek please cc the email to me, as i only receive a digest of this list. |
|
From: Chris N. <pu...@po...> - 2000-12-12 22:03:13
|
At 12:42 -0800 2000.12.12, CertIndex.com Webmaster wrote: >Does anyone know if it is possible to allow people to comment / participate >in articles in which they have moderated the comments of other users? Not currently, no. >We would like users to be able to rate all comments always, even in articles >in which they participate. If this is not possible we'll code it up and make >it a config option for slash. It will be tricky. There is already an authors_unlimited variable that lets authors moderate anything at any time, so you can look for that to see where you'll need to deal with it. You would need to determine what it means for users to be "able to rate all comments always." Does this include repeated moderations of the same post? Moderations of their own posts? Moderations without point limits? And would your decisions on those questions be reasonable for other sites, if you want this patch to be included in the main source? -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
|
From: CertIndex.com W. <web...@ce...> - 2000-12-12 20:41:10
|
Greetings, Does anyone know if it is possible to allow people to comment / participate in articles in which they have moderated the comments of other users? We would like users to be able to rate all comments always, even in articles in which they participate. If this is not possible we'll code it up and make it a config option for slash. Ciao, k |
|
From: Chris N. <pu...@po...> - 2000-12-12 12:56:45
|
Take this for what it may or may not be worth ... :) -- Chris >From: Leon Brocard <ac...@as...> >To: Template Toolkit List <tem...@te...> >X-Perl-Mongers: Bath.pm >Subject: [Templates] [jo...@ch...: Linux Hello World: TT Optimized...] >Sender: tem...@te... >X-BeenThere: tem...@te... >X-Mailman-Version: 2.0rc1 >List-Help: <mailto:tem...@te...?subject=help> >List-Post: <mailto:tem...@te...> >List-Subscribe: <http://www.template-toolkit.org/mailman/listinfo/templates>, > <mailto:tem...@te...?subject=subscribe> >List-Id: Template Toolkit mailing list <templates.template-toolkit.org> >List-Unsubscribe: ><http://www.template-toolkit.org/mailman/listinfo/templates>, > <mailto:tem...@te...?subject=unsubscribe> >List-Archive: <http://www.template-toolkit.org/pipermail/templates/> >Date: Tue, 12 Dec 2000 10:03:29 +0000 > >Looks like TT is the fastest template language for web stuff![1] ;--) > >----- Forwarded message from Joshua Chamas <jo...@ch...> ----- > >From: Joshua Chamas <jo...@ch...> >Subject: Linux Hello World: TT Optimized... >To: Mod Perl <mo...@ap...> >Date: Mon, 11 Dec 2000 19:56:03 -0800 >Organization: NodeWorks <http://nodeworks.com> >X-Mailer: Mozilla 4.75 [en] (WinNT; U) > >Hey, > >Updated results from the other day with the Template Toolkit >benchmark properly optimized, thanks Perrin! > >The reference for these numbers is at: http://www.chamas.com/bench >If you would like the hello test suite, please email me separately. > >]# ./bench.pl -time=60 > >Test Name Test File Hits/sec Total Hits Total >Time sec/Hits >------------ ------------ ------------ ------------ >------------ ------------ >Apache::ASP hello.asp 414.1 24846 hits 60.00 sec >0.002415 >Apache::Registry CGI Raw hello_raw.re 741.7 44502 hits 60.00 sec >0.001348 >Apache::Registry CGI.pm hello.reg 500.0 30001 hits 60.00 sec >0.002000 >HTML Static hello.html 1215.7 50000 hits 41.13 sec >0.000823 >HTML::Embperl hello.epl 509.6 30579 hits 60.00 sec >0.001962 >HTML::Mason hello.mas 385.9 23153 hits 60.00 sec >0.002592 >ModPerl Handler hello.bench 885.8 50000 hits 56.45 sec >0.001129 >Template Toolkit hello.tt 560.3 33622 hits 60.01 sec >0.001785 > >-- Josh > >_________________________________________________________________ >Joshua Chamas Chamas Enterprises Inc. >NodeWorks >> free web link monitoring Huntington Beach, CA USA >http://www.nodeworks.com 1-714-625-4051 > > >----- End forwarded message ----- > >Leon > >[1] In a parituclarly boring and not real test, that is.. >-- >Leon Brocard.............................http://www.astray.com/ >yapc::Europe............................http://yapc.org/Europe/ > >... All new improved Brocard, now with Template Toolkit! > >_______________________________________________ >templates mailing list >tem...@te... >http://www.template-toolkit.org/mailman/listinfo/templates > -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
|
From: Brian A. <br...@ta...> - 2000-12-11 17:17:21
|
You will get a faster turn around on patches if you list in the subject if the patch is for MAIN or Bender. I respond much faster to ones I see that are for Bender. -Brian |
