slashcode-development

[Slashcode-development] Chat for slash

[Xavier de B. <par...@de...>]

Hi all

I just subscribed to the list, i'm the guy of www.deporteyciencia.com

The chat i was coding for slash is running ok in deporteyciencia, is not
coded as a module, is more similar to a few simple cgis in perl. But it
runs fine under mod-perl. The chat is designed for little sites.

It runs different for anonymous, registered and editors. If you try it
think about probably you are a simple anonymous without powers :)

I want to put it in savannah for continue the development, but it still
has not a name

My first question is: Can i name it "slash chat"??

My second question is: Anyone wants to help me in the development? (it's
running but it can be better)

Thanks

Re: [Slashcode-development] Chat for slash

[Markus A. <mar...@ub...>]

par...@de... wrote:
> My first question is: Can i name it "slash chat"??

How much is it tied to Slashcode? Does is use slash? Does it use
templates? Could it be generalized to get the different user types from
other tables than just slash tables?

I'd either make it as independent from slash as possible, than call it
m_p-chat (*g* - for mod_perl chat) or make it a slash module with
templates and everything, then call it slash-chat or whatever.

Markus.

Re: [Slashcode-development] Chat for slash

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

At 02:15 PM 3/5/2002 +0100, Xavier de Blas wrote:
>Hi all
>
>I just subscribed to the list, i'm the guy of www.deporteyciencia.com
>
>The chat i was coding for slash is running ok in deporteyciencia, is not
>coded as a module, is more similar to a few simple cgis in perl. But it
>runs fine under mod-perl. The chat is designed for little sites.
>
>It runs different for anonymous, registered and editors. If you try it
>think about probably you are a simple anonymous without powers :)
>
>I want to put it in savannah for continue the development, but it still
>has not a name
>
>My first question is: Can i name it "slash chat"??
>
>My second question is: Anyone wants to help me in the development? (it's
>running but it can be better)
>
>Thanks

Is the code somewhere we can see it and take a look?

If I were you, I would make it a plugin. That way people can install it easily
enough to their own site(s).

As far as slash modules/plugin names are concerned, I'd recommend two things:

1. Don't name it slash chat. Keep the slash name out of it. It's OSDN's :).
    There's been prior discussion on this, don't complicate your life, just
    make it different.

2. When it's a plugin for slash, the module will actually be Slash::{name}.
  Example: I'm working on the calendar plugin, and ran into naming problems 
clashing with
  Slash::Events.

  My module name is Slash::Calleria. Slash::Events has a script called 
calendar.pl,
  and so did mine. So mine is now called calleria.pl.

  So you may want to consider picking unique names for your module and scripts,
  because anything either a) included in the normal slash bundle/install or b)
  (I assume) anything done by some of the slash guys is going to take priority
  over what outsiders have done, if not only for the lack of time they'd have
  to keep renaming their stuff because contributors keep using basic names
  that conflict, and we want them to write as much functionality as possible :)

  Shane

Re: [Slashcode-development] Chat for slash

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

On Tue, 2002-03-05 at 06:20, shane wrote:

> 2. When it's a plugin for slash, the module will actually be Slash::{name}.
>   Example: I'm working on the calendar plugin, and ran into naming problems 
> clashing with
>   Slash::Events.
> 
>   My module name is Slash::Calleria. Slash::Events has a script called 
> calendar.pl,
>   and so did mine. So mine is now called calleria.pl.
Should have mentioned that to me, I would have been happy to change it
:)

>   So you may want to consider picking unique names for your module and scripts,
>   because anything either a) included in the normal slash bundle/install or b)
>   (I assume) anything done by some of the slash guys is going to take priority
>   over what outsiders have done, if not only for the lack of time they'd have
>   to keep renaming their stuff because contributors keep using basic names
>   that conflict, and we want them to write as much functionality as possible :)
Register plugins in the repository on Slashcode. That way people can
look up names and see what has been taken. 

	-Brian
-- 
_______________________________________________________
Brian Aker, br...@ta... 
Slashdot Senior Developer
Seattle, Washington
http://tangent.org/~brian/
http://askbrian.org/
_______________________________________________________
You can't grep a dead tree.

[Slashcode-development] Sections, Anchor.pm and SlashSectionHost

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

I'm trying to determine where the "appropriate" place is to determine a 
user's current section, and I'm getting confused:

in the current slash series:

If I look at $user->{currentSection}, it is set when header() is called.

  the line is:  $user->{currentSection} = $section || '';
  where section was passed to header().

in the devel slash series:

there's the SlashSectionHost call that will hard-wire the section because 
of the URL. It sets

  $new_cfg->{defaultsection} = $section;

and Anchor.pm still has  $user->{currentSection} = $section || '';
   where section was *passed* to header().



Which leads me to think that getting $user->{currentSection} is *always* up 
to the perl script running at the time to get the section set correctly. So 
I cannot do the following:


sub main {
     my $constants = getCurrentStatic();
     my $slashdb   = getCurrentDB();
     my $user      = getCurrentUser();

and expect that $user->{currentSection}, at this point in time, is correct.

Only after calling header() in the script will $user->{currentSection}
be correct.



Am I understanding this correctly? Or what did I miss?

What I am looking for is the correct way to obtain what section a user is 
in (so as to display the correct section-related data in a calendar for them).

I had always thought this was easy - check the $form data for
$form->{section}, look it up with $slashdb->getSection(),
check the return for validity and you're set.

But with the new Apache directive (which is very cool, btw) it would seem 
to me that $user->{currentSection} should immediately be populated with 
that section that the user's in, if they're in a section.sitename.blah

And it also seems that any script that needs to know the current section 
(ie index.pl) would have to do something like

         my $section;
         if ($form->{section}) {
                 $section = $slashdb->getSection($form->{section});
         } else {
                 $section->{section} = $constants->{defaultsection};
         }

instead of


         my $section;
         if ($form->{section}) {
                 $section = $slashdb->getSection($form->{section});
         } else {
                 $section->{section} = 'index';
                 $section->{issue} = 1;
         }

while other scripts just do:

  header("$constants->{sitename}", $form->{section});

and don't bother to lookup what's being passed to them via the form.

I couldn't test the devel setup with the newer Apache directive, I've got 
no box that I can run slash>2.2.5 on at this time. (though I did try 
something like http://apache.slashdot.org/?section=features and it listed 
as it should)
so I think I'm missing something...

please help!

  Shane