phpwebsite-developers — For our development team.

[Phpwebsite-developers] Site with multi-instance database is up

[Geoff S. <Ge...@Ho...>]

Check out http://www.txsd16democrats.org to see a phpWebsite that uses the
table prefix technique to create a separate set of tables for an instance of
phpwebsite. Note, there isn't much of any content or customization at the
moment. The tables are named sd16_authors, etc.

Here are a few concerns I have from digging into the code to get this
working.

1. The current code is extremely inconsistent. (Although the new code is
much better, it still suffers to some extent from items 2 and 3, below,
because that's what was required to fit it into the existing system.)
2. The code doesn't seem to be segmented into files in a logical fashion.
3. Includes and globals seem to be used extensively instead of using
parameters on function calls.
4. I'm not particularly happy about the way that HTML is embedded in the
code. More on that another time.

I'm especially concerned about item 3. The only way to avoid this kind of
problem is to do a "real" design of the system. Perhaps, we can address
these issues in our IRC meeting.

Geoff

Geoff Staples,
Dallas, Texas   75219-4432
Hostricity Web Hosting <http://www.hostricity.com/>

[Phpwebsite-developers] PHPlib

[clayton c. <cc...@ca...>]

one thing to consider is that there is a move underway to port Pear::DB to
C. how long this will take is uncertain, though. right now though, its isnt
quite as mature as PHPLib, but its growing.



----- Original Message -----
From: "W.D.Sumilang" <wa...@on...>
To: <php...@li...>
Sent: Tuesday, 27. March 2001 15:39
Subject: [Phpwebsite-developers] PHPlib


>  i'm leaning towards
>  phplib which i've worked with. it includes perm priviledges, db
abstraction,
>  sessions mgmt, etc. etc. seems like maintenenance wouldn't be much if
>  the only thing in the phpWS code is the phplib class instances.  But
>  i think this (or native sess, or ADODB sessions, etc.) might conflict
>  with the current way phpWS is architected for page output (eg.
header->header,theme,footer->footer,
>  and module includes) which is obviously under scrutiny with all the
> theme
>  discussions.

[Phpwebsite-developers] Test

[W.D.Sumilang <wa...@on...>]

If this gets through... great... as my posts apparently haven't made
it to the list.

__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com

[Phpwebsite-developers] PHPlib

[W.D.Sumilang <wa...@on...>]

Based on Karsten's submission of kristian's article, i'm leaning towards
 phplib which i've worked with. it includes perm priviledges, db abstraction,
 sessions mgmt, etc. etc. seems like maintenenance wouldn't be much if
 the only thing in the phpWS code is the phplib class instances.  But
 i think this (or native sess, or ADODB sessions, etc.) might conflict
 with the current way phpWS is architected for page output (eg. header->header,theme,footer->footer,
 and module includes) which is obviously under scrutiny with all the
theme
 discussions.
 Why rewrite classes that do the same thing... and do it well, IMHO.
 PHPlib is quite easy to extend once its in place! BTW, if all this could
 be replicated with native php4 sess, and phpWS functions without months
 of lead time, i'd be all for it. Otherwise, i'm game to integrate.

__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com

RE: [Phpwebsite-developers] Template system (Smarty)

[Alain F. <al...@va...>]

Hi again,

Here, straight from the author :)

<-- Monte Ohrt says: -->

The only ones I know of are ones we built.

here are a couple.

http://www.dailynebraskan.com
http://www.torchonline.com

<-- end quote -->

> -----Message d'origine-----
> De : php...@li...
> [mailto:php...@li...]De la part de
> Jason Campbell
> Envoyé : mardi 27 mars 2001 21:02
> À : php...@li...
> Objet : Re: [Phpwebsite-developers] Template system (Smarty)
>
>
> Alain,
>
> Do you know of anyone currently using Smarty templates?? Any other
> projects??  I would like to see it in action in a real environment.
>
> Jason Campbell
> Xplozive Media Technologies
>
>
> > Hi Jason,
> >
> >
> > Actually, Smarty uses PEAR but only in a very limited way, namely to
> > handle some very optional "config file" support.
> >
> > Here's the real URL again for your reference :
> > http://www.phpinsider.com/php/code/Smarty/
> >
> > The authors are very responsive and supporting to user issues, too; I
> > consider this as a strong point.
> >
> >> -----Message d'origine-----
> >> De : php...@li...
> >> [mailto:php...@li...]De la part
> >> de Jason Campbell
> >> Envoyé : mardi 27 mars 2001 20:35
> >> À : php...@li...
> >> Objet : RE: [Phpwebsite-developers] Developer docs update
> >>
> >>
> >> Alan,
> >>
> >> Didn't see your last mention of Smarty Templates so I went looking for
> >> it on hotscripts and found it.  It looks very interesting.  I like how
> >> its done with a class and it uses PEAR to some degree.  If we were to
> >> use PEAR
> >> for other functions (database) instead of ADODB or something else then
> >> I think Smarty Templates could be used, but I haven't looked at it
> >> enough yet
> >> but it does look promising....
> >>
> >> Jason Campbell
> >> Xplozive Media Technologies
> >>
> >>
> >> > Hi,
> >> >
> >> > A couple of comments:
> >> >
> >> > * Use underscores in function names
> >> > Why ? If ever phpWebSite will be developed in an OO approach, why
> >> > not use the "java style" of function and variable naming ?
> >> > setThisThat(), getThisThat(), displayStuff() etc look much better to
> >> > me than
> >> >set_this_that() and so on :)
> >> >
> >> > *Try to avoid unnecessary file unclusions (see config.php and
> >> > mainfile.php) This is of course always true, as an unnecessary file
> >> > inclusion is always to be avoided per definition :). However, using
> >> > include_once() and
> >> > require_once() could help avoiding problems a bit.
> >> >
> >> > *Templates
> >> > I reiterate my suggestion that everyone takes a look at the Smarty
> >> > templates system. I posted the URL in a previous mail.
> >> >
> >> > For the rest, I think the documentation and guidelines you put up
> >> > will be invaluable to the development team - good work.
> >> >
> >> >> -----Message d'origine-----
> >> >> De : php...@li...
> >> >> [mailto:php...@li...]De la
> >> >> part de Karsten Dambekalns
> >> >> Envoyé : mardi 27 mars 2001 13:56
> >> >> À : phpWebsite dev
> >> >> Objet : [Phpwebsite-developers] Developer docs update
> >> >>
> >> >>
> >> >> Hi everybody!
> >> >>
> >> >> I updated the developer docs at
> >> >>  http://www.k-fish.de/krabutzig/phpwebsite/
> >> >>
> >> >> I removed the function overview files, this is handled better by
> >> >> PHPDoc. Talking of which: I added some explanations how to write
> >> >> PHPDoc
> >> >> comments and
> >> >> wrote something about coding style.
> >> >>
> >> >> Take the part about the coding style with a grain of salt and send
> >> >> your comments about that (important issue) in for some discussion.
> >> >> We should settle on some/a good coding style as sson as possible.
> >> >>
> >> >> The new documentation has also been commited to CVS. I will do a
> >> >> new PHPDoc
> >> >> run today or tomorrow and put that up as well.
> >> >>
> >> >> Regards,
> >> >> Karsten
> >> >> --
> >> >> Why do we have to hide from the police, daddy?
> >> >> Because we use emacs, son. They use vi.
> >> >> -----------------------------
> >> >> mailto:k.d...@tu... w³: http://www.k-fish.de/
> >> >> gpg: http://www.k-fish.de/mykeys.gpg
> >> >>
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > Phpwebsite-developers mailing list
> >> > Php...@li...
> >> > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> >>
> >>
> >>
> >> _______________________________________________
> >> Phpwebsite-developers mailing list
> >> Php...@li...
> >> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> >>
> >
> >
> >
> > _______________________________________________
> > Phpwebsite-developers mailing list
> > Php...@li...
> > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>
>
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>

RE: [Phpwebsite-developers] Naming conventions

[Alain F. <al...@va...>]

Hello,

A small comment about capitalization: <tablename in singular>ID ; notice the
uppercase ID because it is easier to read :).

As far as the rest goes... I guess it's just an issue of preference. I
personally prefer java-style, like in getItemProperty(). It somehow looks
weird to have something like my_object->get_item_property(). It sure does
look better if you make that myObject->getItemProperty() ! Just like
phpWebSite looks better than php_web_site ... :))

But as I say, this is my -personal- preference and coding style. As I said
in one of my earlier E-mails, all of my PHP code is strictly object
oriented, as far as PHP allows it, and thus I have adopted the OOP (java,
c++) naming scheme.

Thanks for asking for opinions :)

> -----Message d'origine-----
> De : php...@li...
> [mailto:php...@li...]De la part de
> Todd Owen
> Envoyé : mardi 27 mars 2001 21:11
> À : php...@li...
> Objet : [Phpwebsite-developers] Naming conventions
>
>
> It seems that those expressing an opinion want <tablename in
> singular>id as
> the primary key and ref<primary key name of other table> for foreign keys,
> which is a good method.
>
> I prefer underscores in lieu of StEpPiNg caps for the following
> reasons.  I
> think it's easier to read and case is always lower.  PHP has adopted it
> (e.g. mysql_fetch_array()) and so has most of the existing
> phpWebSite code.
> Does everyone agree?
>
> --Todd Owen
>
>
>
>
>
>
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>

Re: [Phpwebsite-developers] Naming conventions

[Jason C. <cam...@xp...>]

I agree that the underscore should be used just for the fact all the code 
is more or less already done that way and PHP uses that method for 
functions.  If this was java I could see using caps but its not :)

> It seems that those expressing an opinion want <tablename in
> singular>id as the primary key and ref<primary key name of other table>
> for foreign keys, which is a good method.
> 
> I prefer underscores in lieu of StEpPiNg caps for the following
> reasons.  I think it's easier to read and case is always lower.  PHP
> has adopted it (e.g. mysql_fetch_array()) and so has most of the
> existing phpWebSite code. Does everyone agree?
> 
> --Todd Owen
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers

RE: [Phpwebsite-developers] Template system (Smarty)

[Alain F. <al...@va...>]

Hello,

I don't know of any public site that is using Smarty, which doesn't mean
there aren't any. Nevertheless, I am using it myself for the project I am
currently developing, and one of my colleagues is using it for a "Yahoo
style" site for Luxembourg, too, with great success so far.

However, I can't say anything about speed/reliability and what else for
high-traffic sites, as I don't know of any. Maybe you can contact the
authors directly and ask for references ?

Thanks !

> -----Message d'origine-----
> De : php...@li...
> [mailto:php...@li...]De la part de
> Jason Campbell
> Envoyé : mardi 27 mars 2001 21:02
> À : php...@li...
> Objet : Re: [Phpwebsite-developers] Template system (Smarty)
>
>
> Alain,
>
> Do you know of anyone currently using Smarty templates?? Any other
> projects??  I would like to see it in action in a real environment.
>
> Jason Campbell
> Xplozive Media Technologies
>
>
> > Hi Jason,
> >
> >
> > Actually, Smarty uses PEAR but only in a very limited way, namely to
> > handle some very optional "config file" support.
> >
> > Here's the real URL again for your reference :
> > http://www.phpinsider.com/php/code/Smarty/
> >
> > The authors are very responsive and supporting to user issues, too; I
> > consider this as a strong point.
> >
> >> -----Message d'origine-----
> >> De : php...@li...
> >> [mailto:php...@li...]De la part
> >> de Jason Campbell
> >> Envoyé : mardi 27 mars 2001 20:35
> >> À : php...@li...
> >> Objet : RE: [Phpwebsite-developers] Developer docs update
> >>
> >>
> >> Alan,
> >>
> >> Didn't see your last mention of Smarty Templates so I went looking for
> >> it on hotscripts and found it.  It looks very interesting.  I like how
> >> its done with a class and it uses PEAR to some degree.  If we were to
> >> use PEAR
> >> for other functions (database) instead of ADODB or something else then
> >> I think Smarty Templates could be used, but I haven't looked at it
> >> enough yet
> >> but it does look promising....
> >>
> >> Jason Campbell
> >> Xplozive Media Technologies
> >>
> >>
> >> > Hi,
> >> >
> >> > A couple of comments:
> >> >
> >> > * Use underscores in function names
> >> > Why ? If ever phpWebSite will be developed in an OO approach, why
> >> > not use the "java style" of function and variable naming ?
> >> > setThisThat(), getThisThat(), displayStuff() etc look much better to
> >> > me than
> >> >set_this_that() and so on :)
> >> >
> >> > *Try to avoid unnecessary file unclusions (see config.php and
> >> > mainfile.php) This is of course always true, as an unnecessary file
> >> > inclusion is always to be avoided per definition :). However, using
> >> > include_once() and
> >> > require_once() could help avoiding problems a bit.
> >> >
> >> > *Templates
> >> > I reiterate my suggestion that everyone takes a look at the Smarty
> >> > templates system. I posted the URL in a previous mail.
> >> >
> >> > For the rest, I think the documentation and guidelines you put up
> >> > will be invaluable to the development team - good work.
> >> >
> >> >> -----Message d'origine-----
> >> >> De : php...@li...
> >> >> [mailto:php...@li...]De la
> >> >> part de Karsten Dambekalns
> >> >> Envoyé : mardi 27 mars 2001 13:56
> >> >> À : phpWebsite dev
> >> >> Objet : [Phpwebsite-developers] Developer docs update
> >> >>
> >> >>
> >> >> Hi everybody!
> >> >>
> >> >> I updated the developer docs at
> >> >>  http://www.k-fish.de/krabutzig/phpwebsite/
> >> >>
> >> >> I removed the function overview files, this is handled better by
> >> >> PHPDoc. Talking of which: I added some explanations how to write
> >> >> PHPDoc
> >> >> comments and
> >> >> wrote something about coding style.
> >> >>
> >> >> Take the part about the coding style with a grain of salt and send
> >> >> your comments about that (important issue) in for some discussion.
> >> >> We should settle on some/a good coding style as sson as possible.
> >> >>
> >> >> The new documentation has also been commited to CVS. I will do a
> >> >> new PHPDoc
> >> >> run today or tomorrow and put that up as well.
> >> >>
> >> >> Regards,
> >> >> Karsten
> >> >> --
> >> >> Why do we have to hide from the police, daddy?
> >> >> Because we use emacs, son. They use vi.
> >> >> -----------------------------
> >> >> mailto:k.d...@tu... w³: http://www.k-fish.de/
> >> >> gpg: http://www.k-fish.de/mykeys.gpg
> >> >>
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > Phpwebsite-developers mailing list
> >> > Php...@li...
> >> > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> >>
> >>
> >>
> >> _______________________________________________
> >> Phpwebsite-developers mailing list
> >> Php...@li...
> >> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> >>
> >
> >
> >
> > _______________________________________________
> > Phpwebsite-developers mailing list
> > Php...@li...
> > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>
>
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>

[Phpwebsite-developers] Naming conventions

[Todd O. <to...@da...>]

It seems that those expressing an opinion want <tablename in singular>id as
the primary key and ref<primary key name of other table> for foreign keys,
which is a good method.

I prefer underscores in lieu of StEpPiNg caps for the following reasons.  I
think it's easier to read and case is always lower.  PHP has adopted it
(e.g. mysql_fetch_array()) and so has most of the existing phpWebSite code.
Does everyone agree?

--Todd Owen

Re: [Phpwebsite-developers] Template system (Smarty)

[Jason C. <cam...@xp...>]

Alain,

Do you know of anyone currently using Smarty templates?? Any other 
projects??  I would like to see it in action in a real environment.

Jason Campbell
Xplozive Media Technologies


> Hi Jason,
> 
> 
> Actually, Smarty uses PEAR but only in a very limited way, namely to
> handle some very optional "config file" support.
> 
> Here's the real URL again for your reference :
> http://www.phpinsider.com/php/code/Smarty/
> 
> The authors are very responsive and supporting to user issues, too; I
> consider this as a strong point.
> 
>> -----Message d'origine-----
>> De : php...@li...
>> [mailto:php...@li...]De la part
>> de Jason Campbell
>> Envoyé : mardi 27 mars 2001 20:35
>> À : php...@li...
>> Objet : RE: [Phpwebsite-developers] Developer docs update
>>
>>
>> Alan,
>>
>> Didn't see your last mention of Smarty Templates so I went looking for
>> it on hotscripts and found it.  It looks very interesting.  I like how
>> its done with a class and it uses PEAR to some degree.  If we were to
>> use PEAR
>> for other functions (database) instead of ADODB or something else then
>> I think Smarty Templates could be used, but I haven't looked at it
>> enough yet
>> but it does look promising....
>>
>> Jason Campbell
>> Xplozive Media Technologies
>>
>>
>> > Hi,
>> >
>> > A couple of comments:
>> >
>> > * Use underscores in function names
>> > Why ? If ever phpWebSite will be developed in an OO approach, why
>> > not use the "java style" of function and variable naming ?
>> > setThisThat(), getThisThat(), displayStuff() etc look much better to
>> > me than
>> >set_this_that() and so on :)
>> >
>> > *Try to avoid unnecessary file unclusions (see config.php and
>> > mainfile.php) This is of course always true, as an unnecessary file
>> > inclusion is always to be avoided per definition :). However, using
>> > include_once() and
>> > require_once() could help avoiding problems a bit.
>> >
>> > *Templates
>> > I reiterate my suggestion that everyone takes a look at the Smarty
>> > templates system. I posted the URL in a previous mail.
>> >
>> > For the rest, I think the documentation and guidelines you put up
>> > will be invaluable to the development team - good work.
>> >
>> >> -----Message d'origine-----
>> >> De : php...@li...
>> >> [mailto:php...@li...]De la
>> >> part de Karsten Dambekalns
>> >> Envoyé : mardi 27 mars 2001 13:56
>> >> À : phpWebsite dev
>> >> Objet : [Phpwebsite-developers] Developer docs update
>> >>
>> >>
>> >> Hi everybody!
>> >>
>> >> I updated the developer docs at
>> >>  http://www.k-fish.de/krabutzig/phpwebsite/
>> >>
>> >> I removed the function overview files, this is handled better by
>> >> PHPDoc. Talking of which: I added some explanations how to write
>> >> PHPDoc
>> >> comments and
>> >> wrote something about coding style.
>> >>
>> >> Take the part about the coding style with a grain of salt and send
>> >> your comments about that (important issue) in for some discussion.
>> >> We should settle on some/a good coding style as sson as possible.
>> >>
>> >> The new documentation has also been commited to CVS. I will do a
>> >> new PHPDoc
>> >> run today or tomorrow and put that up as well.
>> >>
>> >> Regards,
>> >> Karsten
>> >> --
>> >> Why do we have to hide from the police, daddy?
>> >> Because we use emacs, son. They use vi.
>> >> -----------------------------
>> >> mailto:k.d...@tu... w³: http://www.k-fish.de/
>> >> gpg: http://www.k-fish.de/mykeys.gpg
>> >>
>> >
>> >
>> >
>> > _______________________________________________
>> > Phpwebsite-developers mailing list
>> > Php...@li...
>> > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>
>>
>>
>> _______________________________________________
>> Phpwebsite-developers mailing list
>> Php...@li...
>> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>
> 
> 
> 
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers

Re: [Phpwebsite-developers] The Vision Thing

[Todd O. <to...@da...>]

My vision for phpWebSite is definitely community oriented and much more
general than just a slashdot-like.  From my experience with the project most
everyone holds the same view.

The Roadmap is not yet complete, but Brian would like it to be complete by
next week, which is when some decisions should be made.

--Todd

[Phpwebsite-developers] Template system (Smarty)

[Alain F. <al...@va...>]

Hi Jason,


Actually, Smarty uses PEAR but only in a very limited way, namely to handle
some very optional "config file" support.

Here's the real URL again for your reference :
http://www.phpinsider.com/php/code/Smarty/

The authors are very responsive and supporting to user issues, too; I
consider this as a strong point.

> -----Message d'origine-----
> De : php...@li...
> [mailto:php...@li...]De la part de
> Jason Campbell
> Envoyé : mardi 27 mars 2001 20:35
> À : php...@li...
> Objet : RE: [Phpwebsite-developers] Developer docs update
>
>
> Alan,
>
> Didn't see your last mention of Smarty Templates so I went looking for it
> on hotscripts and found it.  It looks very interesting.  I like how its
> done with a class and it uses PEAR to some degree.  If we were to
> use PEAR
> for other functions (database) instead of ADODB or something else then I
> think Smarty Templates could be used, but I haven't looked at it
> enough yet
> but it does look promising....
>
> Jason Campbell
> Xplozive Media Technologies
>
>
> > Hi,
> >
> > A couple of comments:
> >
> > * Use underscores in function names
> > Why ? If ever phpWebSite will be developed in an OO approach, why not
> > use the "java style" of function and variable naming ? setThisThat(),
> > getThisThat(), displayStuff() etc look much better to me than
> >set_this_that() and so on :)
> >
> > *Try to avoid unnecessary file unclusions (see config.php and
> > mainfile.php) This is of course always true, as an unnecessary file
> > inclusion is always to be avoided per definition :). However, using
> > include_once() and
> > require_once() could help avoiding problems a bit.
> >
> > *Templates
> > I reiterate my suggestion that everyone takes a look at the Smarty
> > templates system. I posted the URL in a previous mail.
> >
> > For the rest, I think the documentation and guidelines you put up will
> > be invaluable to the development team - good work.
> >
> >> -----Message d'origine-----
> >> De : php...@li...
> >> [mailto:php...@li...]De la part
> >> de Karsten Dambekalns
> >> Envoyé : mardi 27 mars 2001 13:56
> >> À : phpWebsite dev
> >> Objet : [Phpwebsite-developers] Developer docs update
> >>
> >>
> >> Hi everybody!
> >>
> >> I updated the developer docs at
> >>  http://www.k-fish.de/krabutzig/phpwebsite/
> >>
> >> I removed the function overview files, this is handled better by
> >> PHPDoc. Talking of which: I added some explanations how to write
> >> PHPDoc
> >> comments and
> >> wrote something about coding style.
> >>
> >> Take the part about the coding style with a grain of salt and send
> >> your comments about that (important issue) in for some discussion. We
> >> should settle on some/a good coding style as sson as possible.
> >>
> >> The new documentation has also been commited to CVS. I will do a new
> >> PHPDoc
> >> run today or tomorrow and put that up as well.
> >>
> >> Regards,
> >> Karsten
> >> --
> >> Why do we have to hide from the police, daddy?
> >> Because we use emacs, son. They use vi.
> >> -----------------------------
> >> mailto:k.d...@tu... w³: http://www.k-fish.de/
> >> gpg: http://www.k-fish.de/mykeys.gpg
> >>
> >
> >
> >
> > _______________________________________________
> > Phpwebsite-developers mailing list
> > Php...@li...
> > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>
>
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>

[Phpwebsite-developers] The Vision Thing

[clayton c. <cc...@ca...>]

i've been lurking for the most part (actually quite busy at the moment). but
since much discussion is occurring about revving up production, i thought
i'd ask about where people see this project heading. i apologize, but i
haven been able to find the PhpWebsite Roadmap in my inbox, so this may have
already been addressed.

particularly, is phpWS primarily geared toward the Weblog/news
posting/Slashdot type of portal or do you see it evolving into a more
generalized community oriented portal system ? the reason im asking is
because i have specific needs for a site im developing, that functions more
along the lines of a community oriented site with a strong focus on user
input and collaboration. on the way to spec'ing it out i picked up a great
deal about the basics of constructing such a site (essentially that it has
to be built from the ground up to be that way, so good modular architecture
and database design is crucial). a project that seems to be oriented this
way (in architecture if not in presentation) is ezPublish.

alas, i try to do too many things in my limited time, so i've been looking
for fellow travelers to see if we could push each other further. if phpWS is
headed that way, i may be able to give a bit of code/design assistance.
otherwise i'll just use it as is for a few other sites i need to set up, and
keep working on the big one..

keep up the good work

<::subText::>

RE: [Phpwebsite-developers] Developer docs update

[Jason C. <cam...@xp...>]

Alan,

Didn't see your last mention of Smarty Templates so I went looking for it 
on hotscripts and found it.  It looks very interesting.  I like how its 
done with a class and it uses PEAR to some degree.  If we were to use PEAR 
for other functions (database) instead of ADODB or something else then I 
think Smarty Templates could be used, but I haven't looked at it enough yet 
but it does look promising....

Jason Campbell
Xplozive Media Technologies


> Hi,
> 
> A couple of comments:
> 
> * Use underscores in function names
> Why ? If ever phpWebSite will be developed in an OO approach, why not
> use the "java style" of function and variable naming ? setThisThat(),
> getThisThat(), displayStuff() etc look much better to me than
>set_this_that() and so on :)
> 
> *Try to avoid unnecessary file unclusions (see config.php and
> mainfile.php) This is of course always true, as an unnecessary file
> inclusion is always to be avoided per definition :). However, using
> include_once() and
> require_once() could help avoiding problems a bit.
> 
> *Templates
> I reiterate my suggestion that everyone takes a look at the Smarty
> templates system. I posted the URL in a previous mail.
> 
> For the rest, I think the documentation and guidelines you put up will
> be invaluable to the development team - good work.
> 
>> -----Message d'origine-----
>> De : php...@li...
>> [mailto:php...@li...]De la part
>> de Karsten Dambekalns
>> Envoyé : mardi 27 mars 2001 13:56
>> À : phpWebsite dev
>> Objet : [Phpwebsite-developers] Developer docs update
>>
>>
>> Hi everybody!
>>
>> I updated the developer docs at
>>  http://www.k-fish.de/krabutzig/phpwebsite/
>>
>> I removed the function overview files, this is handled better by
>> PHPDoc. Talking of which: I added some explanations how to write
>> PHPDoc
>> comments and
>> wrote something about coding style.
>>
>> Take the part about the coding style with a grain of salt and send
>> your comments about that (important issue) in for some discussion. We
>> should settle on some/a good coding style as sson as possible.
>>
>> The new documentation has also been commited to CVS. I will do a new
>> PHPDoc
>> run today or tomorrow and put that up as well.
>>
>> Regards,
>> Karsten
>> --
>> Why do we have to hide from the police, daddy?
>> Because we use emacs, son. They use vi.
>> -----------------------------
>> mailto:k.d...@tu... w³: http://www.k-fish.de/
>> gpg: http://www.k-fish.de/mykeys.gpg
>>
> 
> 
> 
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers

RE: [Phpwebsite-developers] Developer docs update

[Alain F. <al...@va...>]

Hi,

A couple of comments:

* Use underscores in function names
Why ? If ever phpWebSite will be developed in an OO approach, why not use
the "java style" of function and variable naming ? setThisThat(),
getThisThat(), displayStuff() etc look much better to me than
set_this_that() and so on :)

*Try to avoid unnecessary file unclusions (see config.php and mainfile.php)
This is of course always true, as an unnecessary file inclusion is always to
be avoided per definition :). However, using include_once() and
require_once() could help avoiding problems a bit.

*Templates
I reiterate my suggestion that everyone takes a look at the Smarty templates
system. I posted the URL in a previous mail.

For the rest, I think the documentation and guidelines you put up will be
invaluable to the development team - good work.

> -----Message d'origine-----
> De : php...@li...
> [mailto:php...@li...]De la part de
> Karsten Dambekalns
> Envoyé : mardi 27 mars 2001 13:56
> À : phpWebsite dev
> Objet : [Phpwebsite-developers] Developer docs update
>
>
> Hi everybody!
>
> I updated the developer docs at
>  http://www.k-fish.de/krabutzig/phpwebsite/
>
> I removed the function overview files, this is handled better by PHPDoc.
> Talking of which: I added some explanations how to write PHPDoc
> comments and
> wrote something about coding style.
>
> Take the part about the coding style with a grain of salt and send your
> comments about that (important issue) in for some discussion. We should
> settle on some/a good coding style as sson as possible.
>
> The new documentation has also been commited to CVS. I will do a
> new PHPDoc
> run today or tomorrow and put that up as well.
>
> Regards,
> Karsten
> --
> Why do we have to hide from the police, daddy?
> Because we use emacs, son. They use vi.
> -----------------------------
> mailto:k.d...@tu... w³: http://www.k-fish.de/
> gpg: http://www.k-fish.de/mykeys.gpg
>

RE: [Phpwebsite-developers] Templates, multi-language

[Alain F. <al...@va...>]

Hi,

How about offering the two versions? One multi-language template based, and
the other "pre-compiled". That way the user could chose what best suits him.

> -----Message d'origine-----
> De : php...@li...
> [mailto:php...@li...]De la part de
> Christian Schims
> Envoye : mardi 27 mars 2001 19:02
> A : php...@li...
> Objet : Re: [Phpwebsite-developers] Templates, multi-language
>
>
> RODRIGUES Nuno wrote:
> >
> > I agree that you make a point there, however, I can't imagine how a
> > configuration like the one you are describing could be doing so
> bad. I guess
> > it's because 1. it was badly programmed 2. it was using Oracle?
> :). We are
> > currently running www.luxusbuerg.lu, which is a 100% PHP4 /
> mySQL solution,
> > on a bi-pentium3 800 box with 1 GB of ram and a raid5 disk array. Single
> > server, that is. We are handling 4 million page views a month without a
> > single problem. Of course it all depends on what you are
> customizing, etc.
> > Anyway, I was just pointing out the existence of these two
> tools for those
> > who didn't know them yet. As to whether we include them in
> phpWebSite or not
> > is open to public discussion of course !
>
> No, it was because the content management system (Open Market) had to
> generate 33 database requests (ok, including stock modules and other
> complicated personalized stuff), wait for them to be completed and then
> parse all information through the specific template in order to generate
> dynamic HTML content.
>
> That's all I wanted to say: Shall we parse every single page of phpWS in
> order to say: "hey, we're a little slow, but we are multi-lingual". Or
> say it the other way around: Shall we generate such server load although
> maybe 90% of all sites will have an output of more than 90% in one
> single language? Again: Just a question, not a statement.
>
> If you have seen the Sun dying, it's hard to believe the penguin will
> survive... ;-)
>
> Chris
>
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>

[Phpwebsite-developers] Developer docs update

[Karsten D. <k.d...@tu...>]

Hi everybody!

I updated the developer docs at
	http://www.k-fish.de/krabutzig/phpwebsite/

I removed the function overview files, this is handled better by PHPDoc.
Talking of which: I added some explanations how to write PHPDoc comments and
wrote something about coding style.

Take the part about the coding style with a grain of salt and send your
comments about that (important issue) in for some discussion. We should
settle on some/a good coding style as sson as possible.

The new documentation has also been commited to CVS. I will do a new PHPDoc
run today or tomorrow and put that up as well.

Regards,
Karsten
--=20
Why do we have to hide from the police, daddy?
Because we use emacs, son. They use vi.
-----------------------------
mailto:k.d...@tu... w=B3: http://www.k-fish.de/
gpg: http://www.k-fish.de/mykeys.gpg

Re: [Phpwebsite-developers] Templates, multi-language

[Christian S. <chr...@sc...>]

RODRIGUES Nuno wrote:
> 
> I agree that you make a point there, however, I can't imagine how a
> configuration like the one you are describing could be doing so bad. I guess
> it's because 1. it was badly programmed 2. it was using Oracle? :). We are
> currently running www.luxusbuerg.lu, which is a 100% PHP4 / mySQL solution,
> on a bi-pentium3 800 box with 1 GB of ram and a raid5 disk array. Single
> server, that is. We are handling 4 million page views a month without a
> single problem. Of course it all depends on what you are customizing, etc.
> Anyway, I was just pointing out the existence of these two tools for those
> who didn't know them yet. As to whether we include them in phpWebSite or not
> is open to public discussion of course !

No, it was because the content management system (Open Market) had to
generate 33 database requests (ok, including stock modules and other
complicated personalized stuff), wait for them to be completed and then
parse all information through the specific template in order to generate
dynamic HTML content. 

That's all I wanted to say: Shall we parse every single page of phpWS in
order to say: "hey, we're a little slow, but we are multi-lingual". Or
say it the other way around: Shall we generate such server load although
maybe 90% of all sites will have an output of more than 90% in one
single language? Again: Just a question, not a statement.

If you have seen the Sun dying, it's hard to believe the penguin will
survive... ;-)

Chris

[Phpwebsite-developers] Procedural Issues

[Brian W. B. <br...@ap...>]

Some comments on the chain of command and procedural issues :)  I am the
Project Manager, but I am *often* very  busy doing other parts of my job, so
please note that Matt McNaney is second in command.  As we move forward I
fully expect that various developers will become the "resident expert" for
various components/code.  In these cases, these persons will be given final
say in those areas.

I also adhere to the concept that (apologies to Lao-Tzu) "A large project
should be managed like you would fry a small fish - lightly".  In other
words, we here at Appalachian really believe in an open development model
and thus so far the discussion has been productive and informative - people
have good ideas when you allow for it, which often means keeping your mouth
shut - if it is not painfully obvious, I am referring to myself here.  I do 
read all the posts to the development mailing list and I attempt to browse
the SF forums at least once per day.

> HOWEVER, I would like to ask for a clarification. My understanding is that
> Appalachian State University owns phpWebsite.

As someone on the list pointed out, "owns" is probably a little strong...
But we will make final decisions on any *major* changes to the
direction/goals/core code.

> In my mind, while suggestions, support, etc. should always be welcome,
> someone (or several) authorized by Appalachian State should in fact make
> decisions once they think they've received enough input.

So far, I feel the discussion part is working very well.  As a few of you
have pointed out, we do need to reach consensus on a few issues and simply
get to work.  I do not wish, however, to try to make these decisions based
solely on my reaction to posts on the developers list - some developers are
more vocal than others and quantity does not win over content.  As we
identify major issues that require a "decision", say database abstraction, I
would like to see active discussion/education/debate followed by a formal
vote.  I will either mail the developers directly, or post a call for a vote
on this list.  Votes should be mailed to me at br...@tu..., we
will compile the results and post them here.

> In any event, I'd like to know who has the authority to make the
> decisions, etc.

Myself (Brian Brown, Project Manager) and Matt McNaney.  As stated above,
others will be given final say regarding specific areas.

> But, it's probably a good idea to know how decisions will be made before
> something more contentious comes up.

Post, discuss, debate, vote.  I would like to stress that anyone can call
for a vote on practically anything, but votes should always be emailed to me
- just make sure the subject line is clear and consistent. The subject line
should be identified in the call for a vote.

I hope this clarifies some procedural issues.  If you were invited to be a
developer, you should have received an email from me with the subject line
"phpWebSite Roadmap".  Please review and respond at your earliest
convenience

Thanks once again to all of our new developers.  Your enthusiasm and ideas
are most welcome!

Kind Regards,
Brian Brown
phpWebSite Project Manager

--
Brian W. Brown
Internet Systems Architect, ESS
Student Development
Room 269, John Thomas Hall
Appalachian State University
Boone, NC 28608

vox: 828-262-7124
fax: 828-262-2585

Re: [Phpwebsite-developers] Problems with current CVS version??

[Mike N. <mh...@us...>]

Jeremy Agee, 2001-03-27 01:38 -0500
>OK everyone it should be fixed now. My windows checkout worked. Thanks Mike!

Jeremy,
No problem. :)

Regarding list archival.
If you want to have an alternate archive to the primary GeoCrawler one, you 
might want to take a look at:

The Mail Archive
http://www.mail-archive.com/
http://www.mail-archive.com/about.html

--
Mike Noyes <mh...@us...>
http://leaf.sourceforge.net/

[Phpwebsite-developers] Re: Phpwebsite-developers digest, Vol 1 #34 - 11 msgs

[Matthew M. <mcn...@tu...>]

Interger dates are easier, and I happen to be using that format in my 
coding. Keep in mind however that in changing the schema of the database 
will require a conversion from the old table structure. So when developing 
the new code with the clearer table names (which I feel IS needed), a file 
needs to convert all the old data into the new table format.

Matt McNaney

> I've been reviewing the database table schemas, since I think they need
> some significant reform and consistency.  During this review I noticed
> that timestamps are done as both 'datetime' and 'timestamp' (aka
> INTEGER) data types.
> 
> Although the DATE format is consistently 2001-03-26 across many
> database implementations, the DATETIME format is not.  I know ADODB
> specifically addresses this issue.  I propose we use the DATE data type
> where it is needed, like calendar events, but use INTEGER timestamps
> everywhere else. This has several advantages in my opinion.
> 
> 1.  The INTEGER data type is very efficient in storage space and
> difference calculations.
> 2.  PHP has many date and time functions that give us significant
> flexibility.
> 3.  INTEGERs are standard across all database implementations (and they
> record the seconds too).


> 
> I also think the polls, URL referrals, banners and the like should be
> broken out into plug-in modules and removed from the core.  I believe
> the table schema should also be standardized and made clearer such as
> the following:
> 
> 1.  All tables rows have an integer id already, but the field name
> should be 'id' in all cases, since it's the primary key--not sid for
> id's in the session table and cid for id's in the category table.
> 2.  Foreign keys, although not enforced in the code or database, are
> implemented.  A standard naming convention should be employed, such as
> the following:
> 
> CREATE TABLE banner (
>   id                  INT DEFAULT '0' NOT NULL auto_increment,
>   category_id INT DEFAULT '0' NOT NULL, ...  (really a foreign key)
> 
> Joins would look like "SELECT banner.id FROM banner WHERE
> banner.category_id = category.id".  This looks very consistent and
> documents itself.
> 
> --------
> 
> This consistency (and database abstraction as well) comes at the price
> of lots of PHP code needing to be reviewed and updated.  I believe we
> will be much better off in the long run if we do this now instead of
> later.  If there is significant support for this, then I will release a
> new table schema for review and will work with those implementing the
> db abstraction layer to update the queries.
> 
> There's more, but that will have to wait until tomorrow.  My caffeine
> level is getting low.
> 
> --Todd Owen

[Phpwebsite-developers] Upgrade path, general coding

[Alain F. <al...@va...>]

Hello,


The current version is 0.7.6 if I'm not wrong. We have done some cosmetic
work on a 0.7.3 installation, and there's plenty of contents in the
database, too.

We are soon going to publish the latest 0.7.6 on a production server, and I
was wondering if there's anything special to take care of during this
migration to the new version? If so, is there any kind of document done / in
preparation ?

Here's the precise list about the things I am concerned with:

* Contents, e.g. database layout. mysqldump, and then import OK ?
* Themes: we have created one theme that is very customized. Is the "theme
system" still the same or has it been modified ?

I know I could probably find out about all of this on my own, but why do the
work myself when someone else already knows the answers.. :)

From the developer's point of view: I think there have already been talks
about an "Upgrade path documentation" recently. Given that I will soon be in
a real-life situation, namely a 0.7.3 to 0.7.6 migration, we might as well
take the opportunity to find out what problems future users might come
accross, and come up with ideas concerning such a document.


And now for something that will probably make most of yours' hair rise.. :).
Since a couple of weeks I have strictly forgot about "procedurial"
programming, and all of my current and future PHP projects will be
programmed as object-oriented as PHP allows. It not only makes the code more
readable and easier to manage, let alone easier for several people to work
on, but it also opens it up to modern analysis techniques and tools. UML,
anyone ? :) I have recently bought Jim Conallen's excellent book titled
"Building Web Applications with UML", and I must say that using UML for
website development can actually save you a -lot- of trouble and time,
especially as soon as you start producing code in a "distributed
development" environment like the one we currently have for phpWebSite.
A UML sequence diagram, for instance, can easily express a concept and a way
of working on a single page instead of a couple hundred lines of text. I
think that what is particularly important for any software project, and
particularly if you are more than, say, 5 developers, is to have an
extremely precise "book of charges" that describes as accurately as possible
what the system should do, and how it should do it. The process of "coding",
that is, typing PHP in your favourite editor, should as far as possible be
limited to simply translating ideas, concepts and rules into code; these
ideas, concepts and rules having been established in the book of charges
beforehand. My opinion is that this is extremely important in the case of
phpWebSite.
Actually, just like Karl Fogel says in his book "Open Source Development
With CVS", the failure ratio of Open Source projects is quite high, and the
great majority of these projects that never see the light as a finished
application, basically fail because they are either "born-deads", or because
the development process dies somewhere in the middle, due to the lack of
organisation, documentation, communication. This "ODC factor", as I call it,
can quite easily be achieved by following the basic software development
rules, and by using tools/methods like UML and OOP in general.

All of this would of course mean a complete rewrite of phpWebSite :(.
Nevertheless, I thought the idea would be worth mentioning.

Now I realize that what ought to be a short mail, ended up being a quite
long speach about software development !? :) Sorry about this, I recognize
there is quite a lot of "blabla" in there, but I guess phpWebSite is a quite
interesting project, and it would be sad to see it die because we, the
developers, didn't follow the "basic" rules.

Finally, please don't take the above words for the one and only truth. It's
just my personal opinion that I have built upon my very short experience as
a team developer, and I might have got wrong a couple of ideas and concepts.
The fact that I will shortly be teaching a "Web development" course at my
former school surely makes me walk a bit too much on the "theoretical" side
of things. Those of you who have a some kind of computer related degree
surely remember your teachers preaching about analysis/design, and all the
other "boring stuff" that kills every student's enthousiasm right from the
start. When I was still at school last year I would never have thought that
one day -I- would be the teacher, preaching the same stories about that
"boring stuff" called analysis/design/UML/<fit in your favourite enthusiasm
killer>.


Thanks, and talk to you soon.

------
Alain Fontaine
Analyst-Programmer
Nvision s.à.r.l.

Re: [Phpwebsite-developers] Templates, multi-language

[Karsten D. <k.d...@tu...>]

On Tue, Mar 27, 2001 at 10:52:45AM +0200, Alain Fontaine wrote:

> We have spent a great deal of time customizing his phpWebSite as he wanted
> it, but we can't take it to production just yet because the french
> translation needs to be fixed. If someone tells me how to do that, you'll
> have a great french translation up in no time :)

Check out the README.makedistro (from CVS, go to the phpWebSite download
page), it is the docs directory. This should help you.

Regards,
Karsten
--=20
Why do we have to hide from the police, daddy?
Because we use emacs, son. They use vi.
-----------------------------
mailto:k.d...@tu... w=B3: http://www.k-fish.de/
gpg: http://www.k-fish.de/mykeys.gpg

[Phpwebsite-developers] Posting conventions (Please)

[Karsten D. <k.d...@tu...>]

Hi everybody!

I don't want to spoil the party or be rude towards anyone...

But it would be great if you all could try to

- quote correctly (not TOFU!)
- avoid full quotings
- start new threads by replying to an unrelated email

This would make life easier (for everyone, I guess) as it allows faster
recognition of threads, quotings and answers.

Thanks in advance,
Karsten

PS: Outlook users, I do not try to harm you by sending attachments, I just
send application/pgp-signed MIME multipart emails. You may (in that case
only!) safely open the "attachments", or switch to Netscape/mutt/<whatever>.
Yet again: I do not do this to harm anyone, but to make sure you know when I
am _really_ writing an email myself... Just standard paranoia :-)
--=20
Why do we have to hide from the police, daddy?
Because we use emacs, son. They use vi.
-----------------------------
mailto:k.d...@tu... w=B3: http://www.k-fish.de/
gpg: http://www.k-fish.de/mykeys.gpg

Re: [Phpwebsite-developers] Multi-lingual sites (HELP!)

[Karsten D. <k.d...@tu...>]

On Mon, Mar 26, 2001 at 02:46:43PM -0500, Todd Owen wrote:
> Karsten, your idea is GREAT!  I would have never thought of creating this
> scheme as another language and leaving the existing TRANSLATE statements =
in
> the code, which will make it much faster for single language users.

Thanks! :o)

> As we code, the group needs to remember your caveats for not breaking the
> translations.

Yes, definitely :-/ Any idea on how many TRANSLATE statements are in static
HTML actually? Maybe my idea was not to far from being successful, but I
didn't try after I wrote my email yesterday...

Regards,
Karsten
--=20
Why do we have to hide from the police, daddy?
Because we use emacs, son. They use vi.
-----------------------------
mailto:k.d...@tu... w=B3: http://www.k-fish.de/
gpg: http://www.k-fish.de/mykeys.gpg