phpwebsite-developers — For our development team.

[Phpwebsite-developers] PEAR libs

[Steven L. <st...@tu...>]

Hello Everyone,

   In order to prepare for the upcoming release of 0.9.3-2 I would like
to put together a updated version of the pear.current.tar.gz we ship
with phpWebSite and make available off our site.  Please let me know
which PEAR libraries you use so I can make sure to include them.

Thanks,
-- 
Steven Levin
Computer Systems Admin I
Electronic Student Services
Appalachian State University
Phone: 828.262.6740
http://phpwebsite.appstate.edu

Re: [Phpwebsite-developers] Postgres Support (making progress...)

[Richard S. <ri...@ri...>]

You forgot the cache_idx. You must name an index in order to create it.

- Richard Sumilang


On Nov 4, 2003, at 6:01 PM, David Macbanay wrote:

>>> biggest problem I've been having is in the "setup/install.sql" file. 
>>>  I
>>> do not know the equivalent syntax for lines such as
>>> "index(mod_title,id)".  Someone has mentioned about removing these 
>>> line
>>
>> I used:
>>
>> create index cache_idx on cache (mod_title, id);
>>
> Here is the error that I get when I use that statement
>
> DB Error: syntax error
> CREATE INDEX on cache (mod_title) [nativecode=ERROR: parser: parse 
> error
> at or near "on" at character 14 ]
>
> David
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?   SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>

[Phpwebsite-developers] LeagueSite 0.3.0 Released

[Don S. <do...@se...>]

LeagueSite is a PHPWebSite (>= 0.9.3-1) module that adds roster, stats,
and schedule information for a sports league or team onto the PHPWS
base. It can be used to create a website for their fans to learn more
about the league and its teams and players. And as always, leaguesite
provides a conversion utility for current users of my teamsite
application.

The 0.3.0 release has as its main feature dynamic statistics, allowing
the admin to define sets of statistics and have statistics calculated
on-the-fly (like calculating a baseball hitter's batting average from
hits/at-bats or pitcher's ERA from earned runs/innings pitched). There
are also a great number of bug fixes in this release from the 0.2.x
branch.

If you are installing this release on phpWebSite <= 0.9.3-1, you'll also
need to download:

http://leaguesite.sourceforge.net/phpws-0.9.3-1.supplemental.zip

and follow the instructions found in the README.txt included. The
supplemental includes some fixed bugs found in the phpWebSite core that
are needed for LeagueSite 0.3.0.

http://leaguesite.sourceforge.net

Re: [Phpwebsite-developers] Postgres Support (making progress...)

[David M. <dma...@so...>]

> > biggest problem I've been having is in the "setup/install.sql" file.  I
> > do not know the equivalent syntax for lines such as
> > "index(mod_title,id)".  Someone has mentioned about removing these line
> 
> I used:
> 
> create index cache_idx on cache (mod_title, id);
> 
Here is the error that I get when I use that statement

DB Error: syntax error
CREATE INDEX on cache (mod_title) [nativecode=ERROR: parser: parse error
at or near "on" at character 14 ]

David

Re: [Phpwebsite-developers] Postgres Support (making progress...)

[Brian G. <br...@vf...>]

David Macbanay wrote:
> Others need things changed like mediumtext and longtext to just text. 
> "Tinyint(*)" needs to be changed to "smallint", "int(*)" needs to be
> changed to "int" and the "unsigned" keyword needs to be removed. The

There are also some varchar binary's that need to have the binary 
stripped.

> biggest problem I've been having is in the "setup/install.sql" file.  I
> do not know the equivalent syntax for lines such as
> "index(mod_title,id)".  Someone has mentioned about removing these line

I used:

create index cache_idx on cache (mod_title, id);

This works just fine.  However, I don't know if it should be UNIQUE or 
not.  This is where an ER diagram would come in handy.  Perhaps this 
week I will be a single diff of everything I've changed so far.  I'm 
working on a Redhat Linux box against Postgres 7.3 but it should be 
similar for any other releases.


Brian

Re: [Phpwebsite-developers] Postgres Support (making progress...)

[David M. <dma...@so...>]

I've been trying the same thing.  Here is what I have so far.  Some of
the modules seem to have correct sql syntax in their install.sql files. 
Others need things changed like mediumtext and longtext to just text. 
"Tinyint(*)" needs to be changed to "smallint", "int(*)" needs to be
changed to "int" and the "unsigned" keyword needs to be removed. The
biggest problem I've been having is in the "setup/install.sql" file.  I
do not know the equivalent syntax for lines such as
"index(mod_title,id)".  Someone has mentioned about removing these line
but problems occur later on with index functions.  Postgresql uses
something like "create index idx on table(field)" but I don't know what
I should use for the idx variable. I tried it without using the variable
idx but I get table errors.  Someone has just helped me with another
problem which is in "core/Database.php" on line 769 which reads 

$sql = "ALTER TABLE $table_name ADD INDEX (" . implode(", ", $columns) .
")";

This needs to be changed to 

foreach ($columns as $item){  $sql = "CREATE INDEX on " .
$core->tbl_prefix . "$table_name ($item)";  $this->query($sql);}

David



On Tue, 2003-11-04 at 18:09, Brian Ghidinelli wrote:
> Greetings, I've just joined the list and have scanned the archives for 
> PG-related info in the past.  I've spent about 6-8 hours trying to convert 
> phpwebsite 0.9.3 to support postgres.  So far, so good, although I've run 
> into some issues around the sequence support.  For the most part, I've 
> modified everything enough to install all of the modules but the database 
> routines don't quite work yet. 
> 
> I've done a number of things including: 
> 
> * Rewrite sqlGetIndex() to work for postgres (although this will be 
> database-specific and might be worth dropping such a routine) 
> 
> * Update all of the module install.sql and setup/install.sql to be more 
> ANSI-compliant and use SQL-standard syntax for creating indexes 
> 
> Two pieces of documentation would be extremely helpful in moving forward: 
> 
> 1. An ER diagram of the database model for PWS that states, in a 
> database-independent fashion, what the relationships and datatypes should 
> be.  For example, it's hard to know which fields should be unique primary 
> keys and which should just be indexed from the SQL scripts. 
> 
> 2. Dev roadmap that gives some rough direction of which files, systems or 
> libraries need to be worked on to achieve database-independence.  That way 
> contributors can do some heavy lifting. 
> 
> I know that 0.9.4 which is supposed to be db-independent is on something of 
> a ~Spring release schedule but I need good postgres support before then.  
> I'm hoping to take advantage of my enthusiasm if I can get a little 
> direction and perhaps I can piggyback on Richard S' work to date. 
> 
> One big question I have is how are the auto-incrementing fields used?  Are 
> they necessary?  I saw some discussion in the archives from August but no 
> clear decisions? 
> 
> Is there a semi-stable tagged CVS build that is more recent than what's on 
> the website I can work from? 
> 
> Thanks, 
> 
> 
> Brian 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?   SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers

[Phpwebsite-developers] Postgres Support (making progress...)

[Brian G. <br...@vf...>]

Greetings, I've just joined the list and have scanned the archives for 
PG-related info in the past.  I've spent about 6-8 hours trying to convert 
phpwebsite 0.9.3 to support postgres.  So far, so good, although I've run 
into some issues around the sequence support.  For the most part, I've 
modified everything enough to install all of the modules but the database 
routines don't quite work yet. 

I've done a number of things including: 

* Rewrite sqlGetIndex() to work for postgres (although this will be 
database-specific and might be worth dropping such a routine) 

* Update all of the module install.sql and setup/install.sql to be more 
ANSI-compliant and use SQL-standard syntax for creating indexes 

Two pieces of documentation would be extremely helpful in moving forward: 

1. An ER diagram of the database model for PWS that states, in a 
database-independent fashion, what the relationships and datatypes should 
be.  For example, it's hard to know which fields should be unique primary 
keys and which should just be indexed from the SQL scripts. 

2. Dev roadmap that gives some rough direction of which files, systems or 
libraries need to be worked on to achieve database-independence.  That way 
contributors can do some heavy lifting. 

I know that 0.9.4 which is supposed to be db-independent is on something of 
a ~Spring release schedule but I need good postgres support before then.  
I'm hoping to take advantage of my enthusiasm if I can get a little 
direction and perhaps I can piggyback on Richard S' work to date. 

One big question I have is how are the auto-incrementing fields used?  Are 
they necessary?  I saw some discussion in the archives from August but no 
clear decisions? 

Is there a semi-stable tagged CVS build that is more recent than what's on 
the website I can work from? 

Thanks, 


Brian 

Re: [Phpwebsite-developers] Need help understanding php command

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

David,

Yes try:

foreach ($columns as $item){
  $sql = "CREATE INDEX on " . $core->tbl_prefix . "$table_name ($item)";
  $this->query($sql)
}

Play with it, I haven't tested it :)

~Matt

On Sat, 2003-11-01 at 22:04, David Macbanay wrote:
> I am still new at databases and PHP programming but I am trying to
> figure out what all needs to be changed to support postgresql and I have
> the following question.
> 
> On line 769 of the file core/Database.php in version 9.3.1 it has the
> statement  $sql = "ALTER TABLE $table_name ADD INDEX (" . implode(", ",
> $columns) . ")";
> 
> How can this be rewritten to use Postgresql's CREATE INDEX ... ON
> statement?
> 
> Thanks,
> David
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?   SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
-- 
Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
http://phpwebsite.appstate.edu
http://ess.appstate.edu

[Phpwebsite-developers] phpwsContacts 0.6.1 Released

[Don S. <do...@se...>]

phpwsContacts is a module for the phpWebSite CMS 0.9.3-1 or higher. It
provides extended user contact information, CSV exporting and vCard
exporting/importing. Suggested uses are for corporate addressbooks or
alumni websites.

This release fixes some bugs found in 0.6.0 with the CVS exporting. Also
cleared up a bug in vCard exporting. As before you'll need the
phpWebSite supplemental file, it is new as of 31 Oct 2003:

http://phpwscontacts.sourceforge.net/phpws-0.9.3-1.supplemental.zip

http://phpwscontacts.sourceforge.net

[Phpwebsite-developers] Need help understanding php command

[David M. <dma...@so...>]

I am still new at databases and PHP programming but I am trying to
figure out what all needs to be changed to support postgresql and I have
the following question.

On line 769 of the file core/Database.php in version 9.3.1 it has the
statement  $sql = "ALTER TABLE $table_name ADD INDEX (" . implode(", ",
$columns) . ")";

How can this be rewritten to use Postgresql's CREATE INDEX ... ON
statement?

Thanks,
David

[Phpwebsite-developers] phpwsContacts 0.6.0

[Don S. <do...@se...>]

phpwsContacts is a module for the phpWebSite CMS 0.9.3-1 or higher. It
provides extended user contact information and vCard exporting.
Suggested uses are for corporate addressbooks or alumni websites.

This release provides the ability to export the entire visible list as a
comma-separated value (CSV) text file, and also the ability to import
vCard (2.1 or 3.0) files to create new contacts.

Also numerous changes were made to get more efficient use of the
phpWebSite core, and to bring us in line with what is in the pipe for
future versions of phpWebSite. However you'll need to update some core
files from:

http://phpwscontacts.sourceforge.net/phpws-0.9.3-1.supplemental.zip

This includes new Template.php and EZform.php for core, and Display.php
for the calendar module.

http://phpwscontacts.sourceforge.net

[Phpwebsite-developers] LeagueSite 0.3.0 Release Candidate 1

[Don S. <do...@se...>]

Hail and well met! I present to thee the first release candidate of
LeagueSite 0.3.0 for your testing pleasure. I stress that this is a
release candidate and should not be installed into production
environments. Please test as much as possible and file bugs in the
LeagueSite bug tracker.

The 0.3.0 release has as its main feature dynamic statistics, allowing
the admin to define sets of statistics and have statistics calculated
on-the-fly (like calculating a baseball hitter's batting average from
hits/at-bats). There are also a great number of bug fixes in this
release from the 0.2.x branch.

If you are installing this release on phpWebSite <= 0.9.3-1, you'll also
need to download:

http://leaguesite.sourceforge.net/phpws-0.9.3-1.supplemental.zip

and follow the instructions found in the README.txt included. The
supplemental includes some fixed bugs found in the phpWebSite core that
are needed for LeagueSite 0.3.0.

http://leaguesite.sourceforge.net

Re: [Phpwebsite-developers] processTemplate() change

[Steven L. <st...@tu...>]

On Tue, 2003-10-28 at 00:11, Richard Sumilang wrote:
> Yeah that boolean suggestion will work for me :-D Lets do it!
> 
> +1
> 
> 
> 
> On Oct 24, 2003, at 11:33 AM, Steven Levin wrote:
> 
> > On Wed, 2003-10-22 at 18:35, Richard Sumilang wrote:
> >> Currently in PWS the processTemplate() function will not process a
> >> template if the values of the first paramater was NULL, blank, or if
> >> there where no {TEMP} strings in the template. Can it be modified in
> >> the future to still process templates even though array(NULL) or
> >> array() was passed to it?
> >>
> >> If I want a template to be used right now and for some reason the user
> >> left some stuff blank I add a string in the template called {FOO} and
> >> append $array['FOO']=' '; just to make sure the template gets 
> >> processed
> >> each time.
> >>
> >> Is there a better way to possible do this? What do you guys think?
> >
> > We have run into this same problem.  Unfortunately it is a limitation 
> > of
> > the PEAR HTML_Template_IT class.  We could add a boolean flag to the
> > processTemplate function that would replace NULLs with '' so that the
> > template would still be processed.  Does this sound like a reasonable
> > solution?

Richard,

 Have you tried the showBlocks parameter that is already part of the
processTemplate function ?

-- 
Steven Levin
Computer Systems Admin I
Electronic Student Services
Appalachian State University
Phone: 828.262.6740
http://phpwebsite.appstate.edu

Re: [Phpwebsite-developers] processTemplate() change

[Richard S. <ri...@ri...>]

Yeah that boolean suggestion will work for me :-D Lets do it!

+1



On Oct 24, 2003, at 11:33 AM, Steven Levin wrote:

> On Wed, 2003-10-22 at 18:35, Richard Sumilang wrote:
>> Currently in PWS the processTemplate() function will not process a
>> template if the values of the first paramater was NULL, blank, or if
>> there where no {TEMP} strings in the template. Can it be modified in
>> the future to still process templates even though array(NULL) or
>> array() was passed to it?
>>
>> If I want a template to be used right now and for some reason the user
>> left some stuff blank I add a string in the template called {FOO} and
>> append $array['FOO']=' '; just to make sure the template gets 
>> processed
>> each time.
>>
>> Is there a better way to possible do this? What do you guys think?
>
> We have run into this same problem.  Unfortunately it is a limitation 
> of
> the PEAR HTML_Template_IT class.  We could add a boolean flag to the
> processTemplate function that would replace NULLs with '' so that the
> template would still be processed.  Does this sound like a reasonable
> solution?
>
> -- 
> Steven Levin
> Computer Systems Admin I
> Electronic Student Services
> Appalachian State University
> Phone: 828.262.6740
> http://phpwebsite.appstate.edu
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: The SF.net Donation Program.
> Do you like what SourceForge.net is doing for the Open
> Source Community?  Make a contribution, and help us add new
> features and functionality. Click here: http://sourceforge.net/donate/
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>

Re: [Phpwebsite-developers] phpWebSite-comm

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

On Sat, 2003-10-18 at 11:17, Wendall Cada wrote:
> Upon forming the community site, it was decided by the Sourceforge staff
> that we couldn't have binary content in cvs because of the potential
> abuse with graphics. The compromise was that we use SVG format.

Wendall,
Not entirely true. Binaries are allowed, but only on import. see

1.1 CVS Repository
https://sourceforge.net/docman/display_doc.php?docid=17109&group_id=81360

> I feel that this compromise needs to be revisited with the SF.net staff
> as it has badly hurt the -comm project. I'll go into some details.
> 
> After Don, Mike, Adam and I did a lot of looking into SVG, it appears
> that there is not a proper CL conversion tool to do releases with. Don
> and I tested several, and they just make the graphics look like crap.
> Another thing was that the total file sizes of the SVG graphics were
> rediculously large and unnecessary for icons. If SVG could be used by
> web browsers, it would be great, but alas, they cannot and this renders
> the use of them worthless.

I thought the size was only a problem with converted raster binaries. Am
I misinformed? I agree that command line conversion from SVG to a raster
format isn't very good. :-(

> Enforcing the SVG rule has limited the amount of development for themes
> to practically nothing. Don won't use the site. I was planning on
> releasing rssfeeds, but cannot because I can't distribute with my icon.
> The icons are a part of the look and feel of phpWebSite and not
> distributing with one is just plain goofy. Sure, I could do my release
> off site and attatch it to a tracker and have it manually done by the
> SF.net staff with my icon included, but that makes the tools available
> worthless and is alot of work to just do a release. I've concluded after
> all this that it would be faster to submit a new project to SF.net
> staff, get approval and release it from there than wait on silly
> politics.

That is the course Don decided on, and it's a valid option. Be aware
that you could include your raster icons in the release tarball, or you
could import them to CVS.

> SF.net staff needs to understand how they are hurting the -comm project
> and hurting one of the largest projects on SF.net by being resistant to
> the growth of a project.
> 
> I propose we approach the SF.net staff and have them lift the black
> cloud from the -comm project. Or alternately, find another cvs to use in
> its place as the main project has. I would be willing to host the cvs
> repository if App State cannot.

You would need to talk with Moorman on irc.slashnet.org #sourceforge
about the proposed change. Adam was the main contact for -comm with
Moorman. He is the one that negotiated most of this. I helped in a minor
way.

> Mike Noyes has put alot of work into the -comm site and several other
> mod developers have put some great mods out there. There are a few
> themes, but these have been submitted as tarballs. This doesn't appear
> to be a restriction for themes people, but it would be nice to have
> these themes in cvs so they can be updated with changes in the core
> releases.

The only ones that aren't in CVS are the ones contributed to -comm by
people who didn't wish to join. Therefore they were unwilling to
maintain them. Any -comm member is welcome to take up maintenance of the
contributed themes.

> I would like to see the -comm site succeed. No binary content is goofy.
> phpWebSite is a mature project that takes care of itself. Any abuses
> would be immediately dealt with. I find it hard to believe that the
> SF.net staff aren't clued into this. If they aren't, they should be.

In my experience, the SF.net staff are most accommodating. You need to
have a plan that works for them as well as the project though. They have
had many cases of abuse in the past, so they have valid reasons for
being cautious.

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

[Phpwebsite-developers] phpwsBB 0.5.4 Released

[Don S. <do...@se...>]

phpwsBB is a native bulletin board module for the phpWebSite content
manage system, version 0.9.3-1 or later. It features thread monitoring
and administration, including marking threads sticky, locking threads,
and forking messages off to new threads.

phpwsBB 0.5.4 fixes some bugs due to poor QA on my part. A big muchos
gracias to Bobby Kennedy at http://phpwebsitemanual.com for putting
phpwsBB to the test and reporting these. Of course he reported them a
long time ago and has been patient with me while I spent my time on
other phpWebSite pursuits.

See ChangeLog for details.

http://phpwsbb.sourceforge.net

Re: [Phpwebsite-developers] processTemplate() change

[Steven L. <st...@tu...>]

On Wed, 2003-10-22 at 18:35, Richard Sumilang wrote:
> Currently in PWS the processTemplate() function will not process a 
> template if the values of the first paramater was NULL, blank, or if 
> there where no {TEMP} strings in the template. Can it be modified in 
> the future to still process templates even though array(NULL) or 
> array() was passed to it?
> 
> If I want a template to be used right now and for some reason the user 
> left some stuff blank I add a string in the template called {FOO} and 
> append $array['FOO']=' '; just to make sure the template gets processed 
> each time.
> 
> Is there a better way to possible do this? What do you guys think?

We have run into this same problem.  Unfortunately it is a limitation of
the PEAR HTML_Template_IT class.  We could add a boolean flag to the
processTemplate function that would replace NULLs with '' so that the
template would still be processed.  Does this sound like a reasonable
solution?

-- 
Steven Levin
Computer Systems Admin I
Electronic Student Services
Appalachian State University
Phone: 828.262.6740
http://phpwebsite.appstate.edu

[Phpwebsite-developers] Alert Update

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

Greetings,

If you are running phatfile / Document Manager, please update your site
with the tarball supplied on our home site. There are some serious
security concerns with this module.

A big thank you to Eloi for pointing them out.

Matt

-- 
Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
http://phpwebsite.appstate.edu
http://ess.appstate.edu

[Phpwebsite-developers] phpwsProv Testing

[Don S. <do...@se...>]

Today I realised that there are actual people using phpwsProv.  I also
realized that it has been in beta for a while now.

I've implemented the search function and added some missing translations
in CVS.  I plan to go ahead and just release an 0.1.0 final on Monday.
If anyone is already using it (or you are bored) please test what you
can and file bugs or RFEs at http://phpwsprov.sourceforge.net.

Thanks,
Don.

[Phpwebsite-developers] phpwsContacts 0.5.2 Released

[Don S. <do...@se...>]

phpwsContacts is a module for the phpWebSite CMS 0.9.3-1 or higher. It
provides extended user contact information and vCard exporting.
Suggested uses are for corporate addressbooks or alumni websites.

This release fixes a long-standing bug with some where PHP wasn't
supporting dates prior to 1970 or after 2038. This has always been the
case on Windows but now is also a problem on POSIX systems using glibc
>= 2.3.

So I've made a number of changes to provide relief for users of all
systems and have changed the birthday/anniversary timestamp format. When
you upgrade to phpwsContacts-0.5.2 (or higher) from a version lower than
0.5.2, your contact birthdays and anniversaries will automatically be
converted to the new format. You should then be able to save dates prior
to 1970.

If you are installing this release on phpWebSite <= 0.9.3-1, you'll need
to download:

http://phpwscontacts.sourceforge.net/DateFiles.zip

and follow the instructions found in the README.txt included.

http://phpwscontacts.sourceforge.net

Don.

[Phpwebsite-developers] processTemplate() change

[Richard S. <ri...@ri...>]

Currently in PWS the processTemplate() function will not process a 
template if the values of the first paramater was NULL, blank, or if 
there where no {TEMP} strings in the template. Can it be modified in 
the future to still process templates even though array(NULL) or 
array() was passed to it?

If I want a template to be used right now and for some reason the user 
left some stuff blank I add a string in the template called {FOO} and 
append $array['FOO']=' '; just to make sure the template gets processed 
each time.

Is there a better way to possible do this? What do you guys think?

- Richard S.

[Phpwebsite-developers] phpWebSite Core Updates cont.

[Steven L. <st...@tu...>]

Hey everyone,

  I have attached a document here which I hope will help everyone to
update their modules.  I also attached the sed script I used to do the
search and replace over phpwebsite.  Just drop the script in you modules
base directory and invoke it like this:

find . -name "*.php" -exec ./sr {} \;

You may want to edit the script to your desire to comment out
replacements you will not need or add ones that are not found.  Please
do not hesitate to ask me for help.

-- 
Steven Levin
Computer Systems Admin I
Electronic Student Services
Appalachian State University
Phone: 828.262.6740
http://phpwebsite.appstate.edu

Re: [Phpwebsite-developers] phpWebSite-comm

[Eloi G. <el...@re...>]

+1 to an alternative.

Re: [Phpwebsite-developers] phpWebSite-comm

[<th...@me...>]

<a lot snipped>
+1 to finding another solution. please.

the amount of graphics in my themes/any modules i believe is quite
insignificant and does make any difference in the big scheme of things.

> I would like to see the -comm site succeed. No binary content is goofy.
> phpWebSite is a mature project that takes care of itself. Any abuses
> would be immediately dealt with. I find it hard to believe that the
> SF.net staff aren't clued into this. If they aren't, they should be.
>
> Wendall

[Phpwebsite-developers] phpWebSite-comm

[Wendall C. <we...@83...>]

Upon forming the community site, it was decided by the Sourceforge staff
that we couldn't have binary content in cvs because of the potential
abuse with graphics. The compromise was that we use SVG format.

I feel that this compromise needs to be revisited with the SF.net staff
as it has badly hurt the -comm project. I'll go into some details.

After Don, Mike, Adam and I did a lot of looking into SVG, it appears
that there is not a proper CL conversion tool to do releases with. Don
and I tested several, and they just make the graphics look like crap.
Another thing was that the total file sizes of the SVG graphics were
rediculously large and unnecessary for icons. If SVG could be used by
web browsers, it would be great, but alas, they cannot and this renders
the use of them worthless.

Enforcing the SVG rule has limited the amount of development for themes
to practically nothing. Don won't use the site. I was planning on
releasing rssfeeds, but cannot because I can't distribute with my icon.
The icons are a part of the look and feel of phpWebSite and not
distributing with one is just plain goofy. Sure, I could do my release
off site and attatch it to a tracker and have it manually done by the
SF.net staff with my icon included, but that makes the tools available
worthless and is alot of work to just do a release. I've concluded after
all this that it would be faster to submit a new project to SF.net
staff, get approval and release it from there than wait on silly
politics.

SF.net staff needs to understand how they are hurting the -comm project
and hurting one of the largest projects on SF.net by being resistant to
the growth of a project.

I propose we approach the SF.net staff and have them lift the black
cloud from the -comm project. Or alternately, find another cvs to use in
its place as the main project has. I would be willing to host the cvs
repository if App State cannot.

Mike Noyes has put alot of work into the -comm site and several other
mod developers have put some great mods out there. There are a few
themes, but these have been submitted as tarballs. This doesn't appear
to be a restriction for themes people, but it would be nice to have
these themes in cvs so they can be updated with changes in the core
releases.

I would like to see the -comm site succeed. No binary content is goofy.
phpWebSite is a mature project that takes care of itself. Any abuses
would be immediately dealt with. I find it hard to believe that the
SF.net staff aren't clued into this. If they aren't, they should be.

Wendall