slashcode-development — This list is for development of slashcode, no install questions please.

[Slashcode-development] Apache::Cookie

[Brian A. <br...@ta...>]

Good news! The problem with debian and CGI has been fixed.
We are no longer using CGI :)

Bad news, if you are installing from cvs, you need to
add Apache::CGI from CPAN to your perl setup.

	-Brian

[Slashcode-development] Slash / SourceForge Changes

[Chris N. <pu...@po...>]

Note that SourceForge has updated the patch / bug / support managers, so
there is now one "Artifact Manager", and we can create any kind of artifact
types we want.  The active artifact types are Bugs and Patches, same as
before, and a new one for Feature Requests.  This will help us keep FRs
separate from bugs.  I have transferred all the FRs from the Bug Manager
over to the new FR Manager.

Thanks,

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-development] Brownie points

[Brian A. <br...@ta...>]

Thanks folks. From the different responses I
was able to piece together the SQL needed.

So, we just need to find the next bug in Pg :)
	-Brian

Re: [Slashcode-development] Brownie points

[Brian C. S. <bsh...@st...>]

I've got PgAdmin installed on my Workstation.  It contains several =
table->column type drilldowns and the SQL necessary to get this data =
dictionary information.

I'll try to run it and report findings here.

-B

Re: [Slashcode-development] Re: Topics

[Chris N. <pu...@po...>]

At 09:22 -0900 2001.02.23, Nathan Vonnahme wrote:
>The form parts of javascript work with Netscape and IE 3+ on all
>platforms.  I avoid javascript for most public stuff but for things like
>the admin interface I think it's okay to get a little more daring.  It is
>a good idea to keep it functional without javascript, though, just in case
>you want to configure slash or post a story from your cell phone :)

Yes, absolutely.  Or use a browser without JavaScript available or active.
This is a Must.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-development] Re: Topics

[Nathan V. <na...@th...>]

The form parts of javascript work with Netscape and IE 3+ on all
platforms.  I avoid javascript for most public stuff but for things like
the admin interface I think it's okay to get a little more daring.  It is
a good idea to keep it functional without javascript, though, just in case
you want to configure slash or post a story from your cell phone :)


On Fri, 23 Feb 2001, Brian Aker wrote:

> Chris Nandor wrote:
> > I just want to add what is obvious to some but perhaps not to everyone: I
> > don't think any of the Slash team is generally opposed to JavaScript used
> > in this way; however, it must work without the JavaScript, too.  It's no
> > big deal to get it to work like that, I'm just clarifying the point in case
> > someone cares.  :)
> The other caveat is that it must work with the majority of browsers
> and especially Linux/netscape 4.7.  And I do think it would be a good
> thing in a few cases.
> 	-Brian
> 
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-development
> 

Re: [Slashcode-development] Re: Topics

[Brian A. <br...@ta...>]

Chris Nandor wrote:
> I just want to add what is obvious to some but perhaps not to everyone: I
> don't think any of the Slash team is generally opposed to JavaScript used
> in this way; however, it must work without the JavaScript, too.  It's no
> big deal to get it to work like that, I'm just clarifying the point in case
> someone cares.  :)
The other caveat is that it must work with the majority of browsers
and especially Linux/netscape 4.7.  And I do think it would be a good
thing in a few cases.
	-Brian

Re: [Slashcode-development] Calendering

[Chris N. <pu...@po...>]

At 12:01 -0500 2001.02.23, shane wrote:
>At 12:02 PM 2/23/2001 -0500, Chris Nandor wrote:
>>A lot of people have been talking about calendering in the past.  Well, my
>>concern is that it does everything a calendar "should" do.  To wit: there
>>is a Perl project being planned called Reefknot
>>(http://sourceforge.net/projects/reefknot/) that looks very promising.  The
>>two people running it are very dependable, so I have little doubt the
>>project will be developed and will work well.  They have some info at the
>>SourceForge site above.
>
>I am *most* interested in this. I've done an 'events' module
>for slash1. I need to expand on it so as to have a full blown
>calendar systmem for the site when it moves to bender.
>
>If anyone else is interested in this, or would be interested
>in working on this, please get back to me.

There are some Reefknot mailing lists; it might be good to get on the
lists.  If it looks good, I am sure they could probably use help moving the
code along.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-development] Calendering

[shane <sh...@lo...>]

At 12:02 PM 2/23/2001 -0500, Chris Nandor wrote:
>A lot of people have been talking about calendering in the past.  Well, my
>concern is that it does everything a calendar "should" do.  To wit: there
>is a Perl project being planned called Reefknot
>(http://sourceforge.net/projects/reefknot/) that looks very promising.  The
>two people running it are very dependable, so I have little doubt the
>project will be developed and will work well.  They have some info at the
>SourceForge site above.

I am *most* interested in this. I've done an 'events' module
for slash1. I need to expand on it so as to have a full blown
calendar systmem for the site when it moves to bender.

If anyone else is interested in this, or would be interested
in working on this, please get back to me.

  Shane

[Slashcode-development] Calendering

[Chris N. <pu...@po...>]

A lot of people have been talking about calendering in the past.  Well, my
concern is that it does everything a calendar "should" do.  To wit: there
is a Perl project being planned called Reefknot
(http://sourceforge.net/projects/reefknot/) that looks very promising.  The
two people running it are very dependable, so I have little doubt the
project will be developed and will work well.  They have some info at the
SourceForge site above.

Now, a Calendaring plugin for Slash does not need to use Reefknot (though I
am quite lazy and would rather use another good project than develop our
own), but the interesting thing I did not prevoiously know about is that
there is an RFC for calendaring.  See RFCs 2445 - 2447.  They were written
by folks from Microsoft and Lotus.  I don't know much about it, but it
seems like it would certainly be a very good idea to investigate, before
moving forward, whether a Calendar plugin for Slash should be RFC 2445
compliant (2446 and 2447 describe message and transport protocols).

And if RFC 2445 is a good way to go for a Slash plugin, then should
Reefknot be the implementation used?

I don't have answers, but thought that this would be useful information.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-development] Brownie points

[Judd M. <ju...@ma...>]

Brian,

Thanks for writing the support!  Here's what you need (which itself is a 
pointer to bundled doc.)

http://www.postgresql.org/docs/faq-english.html#4.8

GO POSTGRES! MySQL v. Postgres flamewar!!!!! 

(just kidding)

-judd


Brian Aker wrote:

> Ok, tracing down what is not working in the
> postgreSQL version I see that these two
> lines need to be fixed. What is the correct
> pg sql for:
> SHOW TABLES LIKE "$table"
> SHOW COLUMNS FROM $table
> 
> I know about using \dt while in psql,
> but what does it want for SQL to do this?
> 	-Bran
> 
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-development
> 
> 
> 

Re: [Slashcode-development] Re: Topics

[Chris N. <pu...@po...>]

At 10:39 -0900 2001.02.22, Nathan Vonnahme wrote:
>On 22 Feb 2001, Rob 'CmdrTaco' Malda wrote:
>
>> The second issue is that of user interface.    One long list is a pain
>> in the ass, but when you start needing to select multiple topics, it
>> gets even harder.  Probably its not that difficult: if you and have the
>> topic defined, and additional dropdown list can appear and a topic can
>> be selected.  This is a little clunky, but relatively unobtrusive since the
>> bulk of stories will only have 1 or 2 topics anyway.
>
>You can have a selection menu that allows multiple selections... it would
>probably make sense to have a single list for the primary topic and a
>multiple selection menu for the secondary topics.
>
>To do section-based topics it would work best, I think, to have javascript
>dynamically populate the topic selection menus based on which section is
>selected.  A lower-tech solution would be to have all the section:topic
>pairs in the topic selection menus.
>
>More javascript in the admin area would be great in general (especially in
>the variable and template areas; why not preload all the variables in
>javascript so they display instantly instead of submitting the form).

I just want to add what is obvious to some but perhaps not to everyone: I
don't think any of the Slash team is generally opposed to JavaScript used
in this way; however, it must work without the JavaScript, too.  It's no
big deal to get it to work like that, I'm just clarifying the point in case
someone cares.  :)

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-development] Bender Installation 1.1.4 and Oracle port

[Chris N. <pu...@po...>]

At 14:06 -0500 2001.02.22, Perry Shang wrote:
>Have anyone get Bender successfully installed?  I keep getting
>"Issuing rollback() for database handle being DESTROY'd without explicit
>disconnect()."
>in Apache error_log.  I have traced to Slash::Apache::User::handler.  Some
>how, I just can't disconnect MySQL.  Any clue?

Note to add to what Brian said: this warning does not mean you can't
disconnect MySQL.  It means there is not an _explicit_ disconnect; it will
disconnect, I believe, by virtue of the database handle being destroyed.

Brian, is there a way we can add a disconnect() in there, just to be clean?

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

[Slashcode-development] PostgreSQL

[Brian A. <br...@ta...>]

Those of you who are interested in postgreSQL should
update from CVS. In theory it should work quite a bit
better now.
	-Brian
-- 
_______________________________________________________
Brian Aker, br...@ta... 
Slashdot Senior Developer
Seattle, Washington
http://tangent.org/~brian/
http://slashdot.org/
_______________________________________________________
You can't grep a dead tree.

Re: [Slashcode-development] Brownie points

[Alessio B. <al...@al...>]

Brian Aker wrote:

> I know about using \dt while in psql,
> but what does it want for SQL to do this?

use psql -E to echo the internal query.

> SHOW TABLES LIKE "$table"

village=# \dt

********* QUERY *********
SELECT c.relname as "Name", 'table'::text as "Type", u.usename as
"Owner"
FROM pg_class c, pg_user u
WHERE c.relowner = u.usesysid AND c.relkind = 'r'
  AND c.relname !~ '^pg_'
UNION
SELECT c.relname as "Name", 'table'::text as "Type", NULL as "Owner"
FROM pg_class c
WHERE c.relkind = 'r'
  AND not exists (select 1 from pg_user where usesysid = c.relowner)
  AND c.relname !~ '^pg_'

ORDER BY "Name"
*************************

> SHOW COLUMNS FROM $table

village=# \d TABLE

********* QUERY *********
SELECT a.attname, format_type(a.atttypid, a.atttypmod), a.attnotnull,
a.atthasdef, a.attnum
FROM pg_class c, pg_attribute a
WHERE c.relname = 'TABLE'
  AND a.attnum > 0 AND a.attrelid = c.oid
ORDER BY a.attnum
*************************

-- 
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

Re: [Slashcode-development] Brownie points

[Wojtek <so...@ne...>]

On Thu, Feb 22, 2001 at 11:48:56PM -0800, Brian Aker wrote:
> Ok, tracing down what is not working in the
> postgreSQL version I see that these two
> lines need to be fixed. What is the correct
> pg sql for:
> SHOW TABLES LIKE "$table"
> SHOW COLUMNS FROM $table
> 
> I know about using \dt while in psql,
> but what does it want for SQL to do this?
> 	-Bran
> 
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-development
see the source of psql.  it's 'select * from pg_tables blabla" something like
that.  i dont' remember the exact phrase but it's really easy to find.

Wojtek

[Slashcode-development] Brownie points

[Brian A. <br...@ta...>]

Ok, tracing down what is not working in the
postgreSQL version I see that these two
lines need to be fixed. What is the correct
pg sql for:
SHOW TABLES LIKE "$table"
SHOW COLUMNS FROM $table

I know about using \dt while in psql,
but what does it want for SQL to do this?
	-Bran

Re: [Slashcode-development] Re: Topics

[CertIndex.com W. <web...@ce...>]

Not exactly sure how the conversation I started on section hierarchy got off
into topics, so I'll bring 'er on home.

What are your guys' thoughts on making sections hierarchial? Personally this
is something I would *really* like to see, it's almost a show stopper. So if
there are no plans to make this, and you guys would like to see it, give
some recommendations about the best way to go about architecting this and
we'll make the feature patch ourselves. (Would you integrate it into the
main base btw? Would be nice to have it in there.)

regards

----- Original Message -----
From: "Nathan Vonnahme" <na...@th...>
To: <sla...@li...>
Sent: Thursday, February 22, 2001 11:39 AM
Subject: Re: [Slashcode-development] Re: Topics


>
> On 22 Feb 2001, Rob 'CmdrTaco' Malda wrote:
>
> > The second issue is that of user interface.    One long list is a pain
> > in the ass, but when you start needing to select multiple topics, it
> > gets even harder.  Probably its not that difficult: if you and have the
> > topic defined, and additional dropdown list can appear and a topic can
> > be selected.  This is a little clunky, but relatively unobtrusive since
the
> > bulk of stories will only have 1 or 2 topics anyway.
>
> You can have a selection menu that allows multiple selections... it would
> probably make sense to have a single list for the primary topic and a
> multiple selection menu for the secondary topics.
>
> To do section-based topics it would work best, I think, to have javascript
> dynamically populate the topic selection menus based on which section is
> selected.  A lower-tech solution would be to have all the section:topic
> pairs in the topic selection menus.
>
> More javascript in the admin area would be great in general (especially in
> the variable and template areas; why not preload all the variables in
> javascript so they display instantly instead of submitting the form).
>
> -n
>
>
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-development
>

Re: [Slashcode-development] Re: Topics

[Nathan V. <na...@th...>]

On 22 Feb 2001, Rob 'CmdrTaco' Malda wrote:

> The second issue is that of user interface.    One long list is a pain
> in the ass, but when you start needing to select multiple topics, it
> gets even harder.  Probably its not that difficult: if you and have the
> topic defined, and additional dropdown list can appear and a topic can
> be selected.  This is a little clunky, but relatively unobtrusive since the
> bulk of stories will only have 1 or 2 topics anyway.

You can have a selection menu that allows multiple selections... it would
probably make sense to have a single list for the primary topic and a
multiple selection menu for the secondary topics.

To do section-based topics it would work best, I think, to have javascript
dynamically populate the topic selection menus based on which section is
selected.  A lower-tech solution would be to have all the section:topic
pairs in the topic selection menus.

More javascript in the admin area would be great in general (especially in
the variable and template areas; why not preload all the variables in
javascript so they display instantly instead of submitting the form).

-n

[Slashcode-development] Re: Topics

[Rob 'C. M. <ma...@sl...>]

>  * This still has to be fast

This is the reason I never implemented it.  I decided that the
performance hit of having to do an extra lookup was just not
worth it.  I can be done reasonably fast (like storing the first one
in the stories table to save the lookup) but it just was never worth
the work (for slashdot anyway.	For newsforge or whatever, that
may be different).

Sectionally specific topics however please me greatly.

The second issue is that of user interface.    One long list is a pain
in the ass, but when you start needing to select multiple topics, it
gets even harder.  Probably its not that difficult: if you and have the
topic defined, and additional dropdown list can appear and a topic can
be selected.  This is a little clunky, but relatively unobtrusive since the
bulk of stories will only have 1 or 2 topics anyway.

-- 
Rob "CmdrTaco" Malda | ma...@sl... | http://CmdrTaco.net
'Sometimes  when I pick up the guitar, I'm stunned at how well I play.	
But I'm equally good at lots of other things.'	    -- Townshend

Re: [Slashcode-development] Bender Installation 1.1.4 and Oracle port

[Brian A. <br...@ta...>]

Perry Shang wrote:
> Have anyone get Bender successfully installed?  I keep getting
> "Issuing rollback() for database handle being DESTROY'd without explicit
> disconnect()."
> in Apache error_log.  I have traced to Slash::Apache::User::handler.  Some
> how, I just can't disconnect MySQL.  Any clue?
This with Oracle, or MySQL? You can ignore the error. What it is is
Apache
doing it initial startup to test everything and then restarting. 
Disconnect never gets call in this situation.

	-Brian

[Slashcode-development] Bender Installation 1.1.4 and Oracle port

[Perry S. <ps...@re...>]

Have anyone get Bender successfully installed?  I keep getting
"Issuing rollback() for database handle being DESTROY'd without explicit
disconnect()."
in Apache error_log.  I have traced to Slash::Apache::User::handler.  Some
how, I just can't disconnect MySQL.  Any clue?

also, we are working on Oracle port of Slash.  I would love to know who else
is working on it and how far you guys have got so far?

Thanks.

Perry.

Re: [Slashcode-development] Topics

[Brian A. <br...@ta...>]

Eric Dannewitz wrote:
> Well, you could KEEP the sid and have a sequence that links stories and
> topics together. Then you'd have the nice SID thing alive still, and then
> deal with the space issue.
SID will still be around. There will just be an additional sequence.
Think of it as a candidate key.

> Or you could maybe have two tables that assign a sequence to a SID (story and
> topic) and then those sequences are added to another table that links
> multiple stories and topics together.....
The only reason to do header tables like that (and the next version of
comments
is like this) is if you need to worry about relating multiple items to 
topics (classic many to many relationship). 

This shows up in comments, where we have a header table and use
sequences
from it to create parents in comments (we need this so that stories,
polls,
journals, ladybug... other unwritten bits of code) can use the comments
table.

	-Brian

Re: [Slashcode-development] Topics

[Eric D. <eri...@ja...>]

Well, you could KEEP the sid and have a sequence that links stories and
topics together. Then you'd have the nice SID thing alive still, and then
deal with the space issue.

Or you could maybe have two tables that assign a sequence to a SID (story and
topic) and then those sequences are added to another table that links
multiple stories and topics together.....

Just a thought

Brian Aker wrote:

> Eric Dannewitz wrote:
> > Multiple topics would be good. How about a story can have one main
> > topic, but have many related subtopics? That would make more sense.
> That is what this would do for you.
>
> > Yeah, but aren't the sid's or whatever is used to identify them already
> > unique? Then you really don't need to create a sequence do you? The
> > table could just have the unique fields from the topics table and the
> > stories table.
> I knew someone was going to ask this :)
>
> This is the issue. A select on an int is very fast and the table
> doesn't take up much space. Now, think about this over a long
> period. Say you attach 5 additional topics to a story  so that
> you get enough keywords for what you want.
> Now say you run 50 stories a day (newsforge style). Start
> doing the math for over a year, for over 5 years.
>
> This could easily become a huge table. To make sure this will
> work over time we would want it to be as fast as possible.
>
> getDescriptions() with a cachable hash reference to
> topic sequence to name keeps this from being either
> a join, or a large hit to the DB.
>
> The nice things about sid's over sequences is that for
> display purpose (or I should say fetch purpose) a user
> can not see stories before they are being meant to be
> seen. Aka right now you need to be pretty bored to
> do this with article.pl (even though this is
> enforceable with basic business logic in article.pl).
>
>         -Brian
>
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-development

--
Back up my hard disk? I can't find the reverse switch!

Eric Dannewitz - Adventurer, saxophonist, good-timer (crook? quite possibly),
clarinetist, manic self-publicist, part-time flautist(flutist?), macintosher,
and often thought to be completely out to lunch. http://www.jazz-sax.com

Re: [Slashcode-development] Topics

[Brian A. <br...@ta...>]

Eric Dannewitz wrote:
> Multiple topics would be good. How about a story can have one main
> topic, but have many related subtopics? That would make more sense.
That is what this would do for you.

> Yeah, but aren't the sid's or whatever is used to identify them already
> unique? Then you really don't need to create a sequence do you? The
> table could just have the unique fields from the topics table and the
> stories table.
I knew someone was going to ask this :)

This is the issue. A select on an int is very fast and the table
doesn't take up much space. Now, think about this over a long
period. Say you attach 5 additional topics to a story  so that
you get enough keywords for what you want.
Now say you run 50 stories a day (newsforge style). Start
doing the math for over a year, for over 5 years.

This could easily become a huge table. To make sure this will
work over time we would want it to be as fast as possible. 

getDescriptions() with a cachable hash reference to
topic sequence to name keeps this from being either
a join, or a large hit to the DB.

The nice things about sid's over sequences is that for
display purpose (or I should say fetch purpose) a user
can not see stories before they are being meant to be
seen. Aka right now you need to be pretty bored to
do this with article.pl (even though this is 
enforceable with basic business logic in article.pl).

	-Brian