bzflag-league — BZFlag League discussions

New member?

[Dennis P. <de...@mo...>]

Hi,

I would like to get involved with developing the league (both codewise
and organizing tournaments).

As I'm consider myself as a regular bzflag'er I wanted to help getting
the league moving. It could be fun with much more teammates than the few
we have now. So a few days ago I had this idea of making a tournament
myself - to try to involve more teams. So i started coding and creating
a bzcup website. As I was half done i began i found that it didnt seem
that the league was too keen on this. So after writing back and forth
with Chestal I've decided to stop doing "yet-another-bzflag-site" and
offer my time and skills to improving the leage as it is.=20

I understand that you, Valoche, are quite busy at the moment. No offence,
but an inactive website just makes everything even more "dead". So
instead of complaining (as many seems to do), I'm willing to cut down a
few hours of bzflag and code instead (woudl probaly be good for my mouse
anyway) and help you eliminate that todo-list.

So how do I get started?=20

As i see it there is the following possibilities:
1) I could start cleanup and rewriting the current codebase.
2) I could start on a completly new site
3) I could try to eliminate the todolist.
4) I could shut up and continue playing :-)

The league-website seems simple (in structure) so I doubt that it
wouldnt be an issue for me to read and understand your code.

I hope you can use my help.

kind regards=20
 Dennis (aka [dmp])

--=20
Dennis <de...@mo...>
http://dennis.moellegaard.dk *arbejde s=F8ges*

Re: Okay, okay

[David T. <ju...@ba...>]

About the font: the one tim put in CVS is -not- quite the right font.
The actual one can be bought online for $21, but its easier to just
go to irc and bug Patlabor221 (who owns the font already) to make
something for ya.

-D


  -- Quidquid latine dictum sit, altum videtur --

On Mon, 29 Jul 2002, Valoche wrote:

> Hello,
> 
> Don't you think I never thought of splitting that huge unreadable file
> into multiple smaller ones? ;-)
> I too, don't like those 2209 lines a lot ;-)
> I'm aware too, that there are some security issues with the code, but
> eh, it's way too big...
> Just gimme some time, I'm gonna think of a new structure for the pages.
> I'm thinking about having some include files for the functions defines,
> and a class to deal with sessions, which will be much more easier to
> manipulate.
> Where everything's done, we are gonna have a framework common to every
> page, that'll be easy to add new pages or modify existing ones.
> 
> Valoche
> 
> PS: about the new logo: I like it a lot, please tell me where I can find
> it.
> PPS: thanks Tim for giving us this Litograph font I've been looking for,
> for ages :-]
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: Dice - The leading online job board
> for high-tech professionals. Search and apply for tech jobs today!
> http://seeker.dice.com/seeker.epl?rel_code=31
> _______________________________________________
> BZFlag-league mailing list
> BZF...@li...
> https://lists.sourceforge.net/lists/listinfo/bzflag-league
> 

Re: RE : Border problems

[David T. <ju...@ba...>]

It comes from what will soon be the new web site. Whilst making a new logo =
for
it (and BZFlag in general), I decided have a new league logo made at the sa=
me
time. The idea of this is to have a logo capable of a variable-width design=
,
which turned out to be an important thing. Soo.... I have all these pages w=
ith
the table borders redone and the new logo sitting on my machine.

I have no idea why the table is getting messed up. The left cell is width=
=3D"125".
Perhaps if the right cell was made to width=3D"100%" *shrug*

FYI the new web site (bzflag.org/) will almost certainly go up this week. W=
e should
probably switch over to the newish layout for the league at the same time, =
just
to enforce consistancy.

-D


  -- Quidquid latine dictum sit, altum videtur --

On Mon, 29 Jul 2002, BZValoche wrote:

>=20
>=20
> > -----Message d'origine-----
> > De : bzf...@li...=20
> > [mailto:bzf...@li...] De la part=20
> > de Richard Charlton
> > Envoy=E9 : lundi 29 juillet 2002 09:47
> > =C0 : BZFlag CTF League Mailing List
> > Objet : Border problems
> >=20
> >=20
> > There is a problem with the new look ctf pages in that in ie=20
> > in some pages such as in "login" the menubar gets larger and=20
> > it looks awful :-)
> >=20
> > http://rpcharlton.d2g.com/bzctf/league/scr.gif
>=20
> Hum...
> Where does that new logo come from? It's nice, but for me it's out of
> the blue.
>=20
> Valoche
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by: Dice - The leading online job board
> for high-tech professionals. Search and apply for tech jobs today!
> http://seeker.dice.com/seeker.epl?rel_code1
> _______________________________________________
> BZFlag-league mailing list
> BZF...@li...
> https://lists.sourceforge.net/lists/listinfo/bzflag-league
>=20

Admin & entermatch issues

[Valoche <val...@fr...>]

Hello,

I fixed both, thanks.

Valoche

Okay, okay

[Valoche <val...@fr...>]

Hello,

Don't you think I never thought of splitting that huge unreadable file
into multiple smaller ones? ;-)
I too, don't like those 2209 lines a lot ;-)
I'm aware too, that there are some security issues with the code, but
eh, it's way too big...
Just gimme some time, I'm gonna think of a new structure for the pages.
I'm thinking about having some include files for the functions defines,
and a class to deal with sessions, which will be much more easier to
manipulate.
Where everything's done, we are gonna have a framework common to every
page, that'll be easy to add new pages or modify existing ones.

Valoche

PS: about the new logo: I like it a lot, please tell me where I can find
it.
PPS: thanks Tim for giving us this Litograph font I've been looking for,
for ages :-]

RE : Border problems

[BZValoche <bz...@fr...>]

> -----Message d'origine-----
> De : bzf...@li...=20
> [mailto:bzf...@li...] De la part=20
> de Richard Charlton
> Envoy=E9 : lundi 29 juillet 2002 09:47
> =C0 : BZFlag CTF League Mailing List
> Objet : Border problems
>=20
>=20
> There is a problem with the new look ctf pages in that in ie=20
> in some pages such as in "login" the menubar gets larger and=20
> it looks awful :-)
>=20
> http://rpcharlton.d2g.com/bzctf/league/scr.gif

Hum...
Where does that new logo come from? It's nice, but for me it's out of
the blue.

Valoche

Border problems

[Richard C. <rpc...@bl...>]

There is a problem with the new look ctf pages in that in ie in some pages such
as in "login"
the menubar gets larger and it looks awful :-)

http://rpcharlton.d2g.com/bzctf/league/scr.gif


----------------
Ritchie

Re: Website File Structure

[David T. <ju...@ba...>]

Or, we could use my personal favorite, a Document class that has begin("title")
and end() functions.

I'd have to say I'm more in favor of individual PHP files (instead of .inc's)
for each function:
  matchresult.php
  teams.php
  etc

But thats just me.

-D

  -- Quidquid latine dictum sit, altum videtur --

On Thu, 25 Jul 2002, Richard Charlton wrote:

> I am of the opinion that the current "put everything into one script" is far too
> cluttered and difficult to read, especially with features being added all the
> time.
> 
> I propose two possible solutions:
> 
> ____________________________
> 
> 1)
> 
> Different .php files are used for different pages, with three .inc files
> "paths.inc", "functions.inc" and "common.inc". "paths.inc" will include all the
> paths to various stuff, the connection to mysql etc. etc., "functions.inc" any
> common functions, while "common.inc" will deal solely with the output.
> 
> Then the framework for every script would be
> <?php
> include "paths.inc";
> include "functions.inc";
> $mainbody =3D "<p>Welcome to the CTF site</p>";
> $mainbody .=3D "<p>We have had x hits....";
> $title =3D "Welcome";
> /* some other stuff */
> include "common.inc";
> ?>
> 
> common.inc will include the template: instead of using "echo" in the scripts
> you will append to a variable $mainbody your text which will be then echoed by
> common.inc at the end, likewise $title, $sidebar, $extrahead (mainly scripts
> that might need to be used) etc etc. 
> 
> ____________________________
> 
> 2)
> 
> In keeping with the 1 script idea you could do everything with .incs:
> 
> You have index.php as it is now except all the functions at the top are moved
> into "functions.inc" (like in suggestion 1), and each page has its own .inc:
> 
> <?php
> /* mysql stuff, topbar etc etc */
> include "functions.inc";
> switch($link){
> 	case "matchresult":
> 		include "matchresult.inc";	
> 		break;
> 	case "teams":
> 		include "teams.inc";
> 		break;
> 	
> 	/* more stuff..... */
> 
> 	default:
> 		include "frontpage.inc";
> 		break;
> }
> 
> The stuff for each individual page will be in the corresponding .inc file
> ____________________________
> 
> I am in favour of the latter suggestion, though I would welcome any comments or
> refutations of my idea.
> 
> Many thanks
> 
> ----------------
> Ritchie
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: Jabber - The world's fastest growing 
> real-time communications platform! Don't just IM. Build it in! 
> http://www.jabber.com/osdn/xim
> _______________________________________________
> BZFlag-league mailing list
> BZF...@li...
> https://lists.sourceforge.net/lists/listinfo/bzflag-league
> 

Website File Structure

[Richard C. <rpc...@bl...>]

I am of the opinion that the current "put everything into one script" is far too
cluttered and difficult to read, especially with features being added all the
time.

I propose two possible solutions:

____________________________

1)

Different .php files are used for different pages, with three .inc files
"paths.inc", "functions.inc" and "common.inc". "paths.inc" will include all the
paths to various stuff, the connection to mysql etc. etc., "functions.inc" any
common functions, while "common.inc" will deal solely with the output.

Then the framework for every script would be
<?php
include "paths.inc";
include "functions.inc";
$mainbody =3D "<p>Welcome to the CTF site</p>";
$mainbody .=3D "<p>We have had x hits....";
$title =3D "Welcome";
/* some other stuff */
include "common.inc";
?>

common.inc will include the template: instead of using "echo" in the scripts
you will append to a variable $mainbody your text which will be then echoed by
common.inc at the end, likewise $title, $sidebar, $extrahead (mainly scripts
that might need to be used) etc etc. 

____________________________

2)

In keeping with the 1 script idea you could do everything with .incs:

You have index.php as it is now except all the functions at the top are moved
into "functions.inc" (like in suggestion 1), and each page has its own .inc:

<?php
/* mysql stuff, topbar etc etc */
include "functions.inc";
switch($link){
	case "matchresult":
		include "matchresult.inc";	
		break;
	case "teams":
		include "teams.inc";
		break;
	
	/* more stuff..... */

	default:
		include "frontpage.inc";
		break;
}

The stuff for each individual page will be in the corresponding .inc file
____________________________

I am in favour of the latter suggestion, though I would welcome any comments or
refutations of my idea.

Many thanks

----------------
Ritchie

Something you might like to know...

[Richard C. <rpc...@bl...>]

The admin sections of the site are completely unprotected - if anyone types 

?link=3Dadmin 

or 

?link=3Dentermatch

there is nothing stopping them updating the important site data. Something to
be looked into perhaps?

----------------
Ritchie