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