phpwebsite-developers — For our development team.

Re: [Phpwebsite-developers] Version Scheme

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

OR 0.9.3.1 since the other was 0.9.3-1... What about "0.9.3-1 Extreme"?


On Thursday, October 16, 2003, at 09:01  AM, Don Seiler wrote:

> I think you're stuck calling it 0.9.3-2, since 0.9.4 is already in the
> works.  Perhaps 0.9.3-OMFG-ITS-FASTER.
>
> Don.
>
> On Thu, Oct 16, 2003 at 11:47:28AM -0400, Steven Levin wrote:
>> Ok now it seems as though most are going to agree with the changes.  
>> Can
>> we discuss how this new version is going to be name/numbered.  We 
>> can't
>> exactly call it 0.9.4 since everyone will be expecting all the changes
>> we have been promising in it and 0.9.3-2 is not a big enough increase 
>> to
>> reflect the changes going on.  Please send in your suggestions.
>>
>> -- 
>> 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: SF.net Giveback Program.
>> SourceForge.net hosts over 70,000 Open Source Projects.
>> See the people who have HELPED US provide better services:
>> Click here: http://sourceforge.net/supporters.php
>> _______________________________________________
>> Phpwebsite-developers mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>
> <mime-attachment>

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

On Fri, 2003-10-17 at 15:24, Richard Sumilang wrote:
> Is this only going to be for 9.4 or is there going to be like 9.3-2?

The only thing 0.9.3-2 will implement is the runtime.php file.  All the
others that Matt talked about (init.php and close.php) are 0.9.4
specific.

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

[Phpwebsite-developers] Example Updates

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

Hello,

   I have committed my changes to the announce module so you can see
what I have done to update it for 0.9.3-2.  However none of the core
changes have been committed yet.  If you want a working copy you can use
this one:

http://res1.stddev.appstate.edu/phpwebsite/steven/test/phpwebsite-0.9.3-2-beta.tar.gz

There is also a running version at:

http://res1.stddev.appstate.edu/phpwebsite/steven/test/phpwebsite/

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

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

Is this only going to be for 9.4 or is there going to be like 9.3-2?



On Wednesday, October 15, 2003, at 07:58  AM, Steven Levin wrote:

> Hello everyone,
>
>   This list has been very inactive ever since the IRC chat room came
> about, but I hope to pick things back up again with this discussion I
> would like to start.  I believe this will be a better forum than chat
> since not all the module developers hang out there.  As some may have
> heard, I recently hacked away at phpwebsite and dropped the memory
> requirements below the 8m php default and cut execution times in half.
> Now in order for these changes to go into place modules will have to
> update some of their calls to core functions.  The reason for this is
> because one of the changes made was to split up the long and 
> unnecessary
> inheritance chain that all the core classes were a part of.  Approval
> from a majority of the third party developers is crucial in my decision
> to commit these changes to CVS.   So please let me know how you feel
> about updating your modules.  Below are examples of some of the updates
> that need to be made.
>
> Before:
> The core inherited from the PHPWS_Text class so you where able to call
> the function parseInput() like this:
> $GLOBALS['core']->parseInput($text_to_parse);
>
> Now:
> The class PHPWS_Text is split off from the core, so you have to do a
> require_once(PHPWS_SOURCE_DIR.'core/Text.php');
> at the top of the class file you use the function in and then call it
> like this:
> PHPWS_Text::parseInput($text_to_parse);
>
> Before:
> When you wanted to show some content in a block on the left or right
> side of the site you would have just put the code in your modules index
> file.
>
> Now:
> Extra content that needs to show up in phpwebsite when your module is
> NOT running (ie.  announcements and past announcements on the home 
> page)
> now needs to be placed in a file called inc/runtime.php in your module.
>
> Ok now the decision needs to be made.  If a majority of the developers
> vote yes then the changes will go into place.  I have a nice sed script
> that will do a most of the replacements of old calls for you.  The list
> of replacements only do the common ones found throughout phpwebsite so
> you may have some left behind that you will have to fix by hand.   Now 
> I
> am willing to provide assistance upgrading modules in my free time so
> don't feel like you will have to figure out all the updates on your own
> cause I am sure there will be some special cases.  Alright all you
> developers out there fire away.
>
> -- 
> 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: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

OK, I'm starting to see the big picture now.

+1 on everything.

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

Can you let us know when you have a module converted in CVS for us to
model after?

Don.

On Fri, Oct 17, 2003 at 11:40:51AM -0400, Steven Levin wrote:
> Ok I think I understand where your confusion is coming from.  Let me see
> if I can explain.  Making the runtime stuff is only a slight speed
> increase,  Matt was correct, it is mainly to start getting ready for
> 0.9.4.  The main performance increase comes from splitting up the core
> classes and only including the module that is currently being executed.=
=20
> The point of pulling the runtime stuff from index is to begin splitting
> stuff up.  Right now phpwebsite includes all the all of the modules and
> their index files.  With my changes phpwebsite will only include one
> module's class files along with its index (the current module being
> requested) and then the runtime files for those modules that have them.=
=20
> I believe this will drastically decrease the files being included.   We
> could just put in all the index files a check for the requested module
> and then skip execution if it is not your module and then do the runtime
> stuff at the bottom,  but I prefer to split it up.  Then we are not
> including an index or runtime for things that do not need it. (ie. faq,
> links, photoalbum, phatform, branch, boost, approval, and others).  This
> is not a move away from using sessions,  I still use sessions a lot. =20
> But in some of my older modules I used them in excess, so I would like
> to improve upon that.
> --=20
> Steven Levin
> Computer Systems Admin I
> Electronic Student Services
> Appalachian State University
> Phone: 828.262.6740
> http://phpwebsite.appstate.edu
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
> The Event For Linux Datacenter Solutions & Strategies in The Enterprise=
=20
> Linux in the Boardroom; in the Front Office; & in the Server Room=20
> http://www.enterpriselinuxforum.com
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>=20

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

Ok I think I understand where your confusion is coming from.  Let me see
if I can explain.  Making the runtime stuff is only a slight speed
increase,  Matt was correct, it is mainly to start getting ready for
0.9.4.  The main performance increase comes from splitting up the core
classes and only including the module that is currently being executed. 
The point of pulling the runtime stuff from index is to begin splitting
stuff up.  Right now phpwebsite includes all the all of the modules and
their index files.  With my changes phpwebsite will only include one
module's class files along with its index (the current module being
requested) and then the runtime files for those modules that have them. 
I believe this will drastically decrease the files being included.   We
could just put in all the index files a check for the requested module
and then skip execution if it is not your module and then do the runtime
stuff at the bottom,  but I prefer to split it up.  Then we are not
including an index or runtime for things that do not need it. (ie. faq,
links, photoalbum, phatform, branch, boost, approval, and others).  This
is not a move away from using sessions,  I still use sessions a lot.  
But in some of my older modules I used them in excess, so I would like
to improve upon that.
-- 
Steven Levin
Computer Systems Admin I
Electronic Student Services
Appalachian State University
Phone: 828.262.6740
http://phpwebsite.appstate.edu

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

Steven can answer this better than I can, but I imagine it will work
like 0.9.4.

There are four files in 0.9.4 (probably less in Steven's revision of
0.9.3)

init.php : This file is called BEFORE the session_start is called. If
you have classes that need including, this is where to do it.

runtime.php : Not required but needed if your module needs to be called
every time a page is called. For example, users uses runtime to print
your login box.

index.php : This file is called only when your module specifically
accessed. We separated them out so because frequently there is a lot of
logic in the index file and it tends to get big. If you only need a
quick command to run, it saves time. Plus (in 0.9.4) you can focus
index.php on only what needs to be done for that module. 

close.php : Like init, I don't think Steven is using this. In 0.9.4 this
file is called for each module to tie up loose ends. In 0.9.4 layout,
close calls the function to display the theme. Others may use it to
close sessions or other properties.

Again, I think Steven is only using runtime and index but this is the
direction we are going.

Matt

On Fri, 2003-10-17 at 01:15, Eloi George wrote:
> Steven Levin wrote:
> 
> >Well it was not just the PHPWS_Text class,  all the core classes have
> >been seperated.  The runtime.php file runs instead of the index.php file
> >when the module is not called.  Both would be included if the module was
> >called.   The core is now setup to only include the module that is
> >currently being requested.  The runtime.php file allows for modules not
> >running to still show content.  I had not set it up do be authorized by
> >allow_view, but I will, just forgot about it.
> >
> >  
> >
> 
> I'm still having trouble understanding why we'd need a runtime.php in 
> addition to the index.php.  Either way a file will still get called up.  
> In certain of my modules, the index.php code contains some if-else 
> statements that check $GLOBALS['module'] to see which module has 
> dominance and act accordingly.   How does offloading that code to a 
> different file give us performance benefits?  Is it just that both would 
> end up being smaller files?
>  
> After 16 hours of sleep, I'm feeling so much better...
> 
> Eloi
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> 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

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

Don Seiler wrote:

>I believe that when the module's index.php is called, then all the
>session objects for that module are instantiated.  This creates memory
>overhead that might not be needed if the module isn't in the fore.
>Although now that I think about it, I would have to instantiate my
>manager anyway to know how to display the blocks.  Hmm.
>
>Don.
>  
>

Same here.  Is this really part of the "no sessions" initiative?  If so, 
has anyone said how state and configuration data will be stored between 
requests?  I store this stuff in the manager classes to keep disk 
accesses down to a minimum. 

-Eloi-

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

On Fri, Oct 17, 2003 at 12:15:49AM -0500, Eloi George wrote:
> I'm still having trouble understanding why we'd need a runtime.php in=20
> addition to the index.php.  Either way a file will still get called up. =
=20
> In certain of my modules, the index.php code contains some if-else=20
> statements that check $GLOBALS['module'] to see which module has=20
> dominance and act accordingly.   How does offloading that code to a=20
> different file give us performance benefits?  Is it just that both would=
=20
> end up being smaller files?

I believe that when the module's index.php is called, then all the
session objects for that module are instantiated.  This creates memory
overhead that might not be needed if the module isn't in the fore.
Although now that I think about it, I would have to instantiate my
manager anyway to know how to display the blocks.  Hmm.

Don.

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

Steven Levin wrote:

>Well it was not just the PHPWS_Text class,  all the core classes have
>been seperated.  The runtime.php file runs instead of the index.php file
>when the module is not called.  Both would be included if the module was
>called.   The core is now setup to only include the module that is
>currently being requested.  The runtime.php file allows for modules not
>running to still show content.  I had not set it up do be authorized by
>allow_view, but I will, just forgot about it.
>
>  
>

I'm still having trouble understanding why we'd need a runtime.php in 
addition to the index.php.  Either way a file will still get called up.  
In certain of my modules, the index.php code contains some if-else 
statements that check $GLOBALS['module'] to see which module has 
dominance and act accordingly.   How does offloading that code to a 
different file give us performance benefits?  Is it just that both would 
end up being smaller files?
 
After 16 hours of sleep, I'm feeling so much better...

Eloi

Re: [Phpwebsite-developers] Version Scheme

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

I think you're stuck calling it 0.9.3-2, since 0.9.4 is already in the
works.  Perhaps 0.9.3-OMFG-ITS-FASTER.

Don.

On Thu, Oct 16, 2003 at 11:47:28AM -0400, Steven Levin wrote:
> Ok now it seems as though most are going to agree with the changes.  Can
> we discuss how this new version is going to be name/numbered.  We can't
> exactly call it 0.9.4 since everyone will be expecting all the changes
> we have been promising in it and 0.9.3-2 is not a big enough increase to
> reflect the changes going on.  Please send in your suggestions.
>=20
> --=20
> Steven Levin
> Computer Systems Admin I
> Electronic Student Services
> Appalachian State University
> Phone: 828.262.6740
> http://phpwebsite.appstate.edu
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>=20

[Phpwebsite-developers] Version Scheme

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

Ok now it seems as though most are going to agree with the changes.  Can
we discuss how this new version is going to be name/numbered.  We can't
exactly call it 0.9.4 since everyone will be expecting all the changes
we have been promising in it and 0.9.3-2 is not a big enough increase to
reflect the changes going on.  Please send in your suggestions.

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

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

On Wed, 2003-10-15 at 16:59, Eloi George wrote:
> Wow.  Is that how you did it?  That's mind-boggling?
> 
> +1 for the PHPWS_Text class.
> 
> I'm confused about the second section, though.  It sounds like the 
> inc/runtime.php file is just replacing index.php whenever the module is 
> not explicitly called but is authorized to execute via $allow_view in 
> conf/boost.php.  Is this the case?

Well it was not just the PHPWS_Text class,  all the core classes have
been seperated.  The runtime.php file runs instead of the index.php file
when the module is not called.  Both would be included if the module was
called.   The core is now setup to only include the module that is
currently being requested.  The runtime.php file allows for modules not
running to still show content.  I had not set it up do be authorized by
allow_view, but I will, just forgot about it.

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

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

OK, I messed that up.  I meant to say that's mind-boggling!!!!!

Yeah, it's not one of my "up" days....

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

Wow.  Is that how you did it?  That's mind-boggling?

+1 for the PHPWS_Text class.

I'm confused about the second section, though.  It sounds like the 
inc/runtime.php file is just replacing index.php whenever the module is 
not explicitly called but is authorized to execute via $allow_view in 
conf/boost.php.  Is this the case?

Eloi George



Steven Levin wrote:
> Hello everyone,
> 
>   This list has been very inactive ever since the IRC chat room came
> about, but I hope to pick things back up again with this discussion I
> would like to start.  I believe this will be a better forum than chat
> since not all the module developers hang out there.  As some may have
> heard, I recently hacked away at phpwebsite and dropped the memory
> requirements below the 8m php default and cut execution times in half. 
> Now in order for these changes to go into place modules will have to
> update some of their calls to core functions.  The reason for this is
> because one of the changes made was to split up the long and unnecessary
> inheritance chain that all the core classes were a part of.  Approval
> from a majority of the third party developers is crucial in my decision
> to commit these changes to CVS.   So please let me know how you feel
> about updating your modules.  Below are examples of some of the updates
> that need to be made.
> 
> Before:
> The core inherited from the PHPWS_Text class so you where able to call
> the function parseInput() like this:
> $GLOBALS['core']->parseInput($text_to_parse);
> 
> Now:
> The class PHPWS_Text is split off from the core, so you have to do a
> require_once(PHPWS_SOURCE_DIR.'core/Text.php');  
> at the top of the class file you use the function in and then call it
> like this:
> PHPWS_Text::parseInput($text_to_parse);
> 
> Before:
> When you wanted to show some content in a block on the left or right
> side of the site you would have just put the code in your modules index
> file.
> 
> Now:
> Extra content that needs to show up in phpwebsite when your module is
> NOT running (ie.  announcements and past announcements on the home page)
> now needs to be placed in a file called inc/runtime.php in your module.
> 
> Ok now the decision needs to be made.  If a majority of the developers
> vote yes then the changes will go into place.  I have a nice sed script
> that will do a most of the replacements of old calls for you.  The list
> of replacements only do the common ones found throughout phpwebsite so
> you may have some left behind that you will have to fix by hand.   Now I
> am willing to provide assistance upgrading modules in my free time so
> don't feel like you will have to figure out all the updates on your own
> cause I am sure there will be some special cases.  Alright all you
> developers out there fire away.
> 

Re: [Phpwebsite-developers] phpWebSite Core Updates

[aDarkling <ju...@re...>]

Wow.  Is that how you did it?  That's mind-boggling?

+1 for the PHPWS_Text class.

I'm confused about the second section, though.  It sounds like the 
inc/runtime.php file is just replacing index.php whenever the module is 
not explicitly called but is authorized to execute via $allow_view in 
conf/boost.php.  Is this the case?

Eloi George



Steven Levin wrote:
> Hello everyone,
> 
>   This list has been very inactive ever since the IRC chat room came
> about, but I hope to pick things back up again with this discussion I
> would like to start.  I believe this will be a better forum than chat
> since not all the module developers hang out there.  As some may have
> heard, I recently hacked away at phpwebsite and dropped the memory
> requirements below the 8m php default and cut execution times in half. 
> Now in order for these changes to go into place modules will have to
> update some of their calls to core functions.  The reason for this is
> because one of the changes made was to split up the long and unnecessary
> inheritance chain that all the core classes were a part of.  Approval
> from a majority of the third party developers is crucial in my decision
> to commit these changes to CVS.   So please let me know how you feel
> about updating your modules.  Below are examples of some of the updates
> that need to be made.
> 
> Before:
> The core inherited from the PHPWS_Text class so you where able to call
> the function parseInput() like this:
> $GLOBALS['core']->parseInput($text_to_parse);
> 
> Now:
> The class PHPWS_Text is split off from the core, so you have to do a
> require_once(PHPWS_SOURCE_DIR.'core/Text.php');  
> at the top of the class file you use the function in and then call it
> like this:
> PHPWS_Text::parseInput($text_to_parse);
> 
> Before:
> When you wanted to show some content in a block on the left or right
> side of the site you would have just put the code in your modules index
> file.
> 
> Now:
> Extra content that needs to show up in phpwebsite when your module is
> NOT running (ie.  announcements and past announcements on the home page)
> now needs to be placed in a file called inc/runtime.php in your module.
> 
> Ok now the decision needs to be made.  If a majority of the developers
> vote yes then the changes will go into place.  I have a nice sed script
> that will do a most of the replacements of old calls for you.  The list
> of replacements only do the common ones found throughout phpwebsite so
> you may have some left behind that you will have to fix by hand.   Now I
> am willing to provide assistance upgrading modules in my free time so
> don't feel like you will have to figure out all the updates on your own
> cause I am sure there will be some special cases.  Alright all you
> developers out there fire away.
> 

RE: [Phpwebsite-developers] phpWebSite Core Updates

[Meiste, G. <me...@ms...>]

+1 from me.  I've been eagerly waiting this update.

Greg

-----Original Message-----
From: Steven Levin [mailto:st...@tu...] 
Sent: Wednesday, October 15, 2003 9:59 AM
To: php...@li...
Subject: [Phpwebsite-developers] phpWebSite Core Updates

Hello everyone,

  This list has been very inactive ever since the IRC chat room came
about, but I hope to pick things back up again with this discussion I
would like to start.  I believe this will be a better forum than chat
since not all the module developers hang out there.  As some may have
heard, I recently hacked away at phpwebsite and dropped the memory
requirements below the 8m php default and cut execution times in half. 
Now in order for these changes to go into place modules will have to
update some of their calls to core functions.  The reason for this is
because one of the changes made was to split up the long and unnecessary
inheritance chain that all the core classes were a part of.  Approval
from a majority of the third party developers is crucial in my decision
to commit these changes to CVS.   So please let me know how you feel
about updating your modules.  Below are examples of some of the updates
that need to be made.

Before:
The core inherited from the PHPWS_Text class so you where able to call
the function parseInput() like this:
$GLOBALS['core']->parseInput($text_to_parse);

Now:
The class PHPWS_Text is split off from the core, so you have to do a
require_once(PHPWS_SOURCE_DIR.'core/Text.php');  
at the top of the class file you use the function in and then call it
like this:
PHPWS_Text::parseInput($text_to_parse);

Before:
When you wanted to show some content in a block on the left or right
side of the site you would have just put the code in your modules index
file.

Now:
Extra content that needs to show up in phpwebsite when your module is
NOT running (ie.  announcements and past announcements on the home page)
now needs to be placed in a file called inc/runtime.php in your module.

Ok now the decision needs to be made.  If a majority of the developers
vote yes then the changes will go into place.  I have a nice sed script
that will do a most of the replacements of old calls for you.  The list
of replacements only do the common ones found throughout phpwebsite so
you may have some left behind that you will have to fix by hand.   Now I
am willing to provide assistance upgrading modules in my free time so
don't feel like you will have to figure out all the updates on your own
cause I am sure there will be some special cases.  Alright all you
developers out there fire away.

-- 
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: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Phpwebsite-developers mailing list
Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

+1 for speed ;)

Wendall

On Wed, 2003-10-15 at 10:08, Don Seiler wrote:
> +1 from me as well.  Although it's times like this when I wish I wasn't
> authoring so many modules to go back and update.  :)
> 
> Don.
> 
> On Wed, Oct 15, 2003 at 09:53:51AM -0700, Richard Sumilang wrote:
> > +1 for me
> > 
> > 
> > On Wednesday, October 15, 2003, at 07:58  AM, Steven Levin wrote:
> > 
> > >Hello everyone,
> > >
> > >  This list has been very inactive ever since the IRC chat room came
> > >about, but I hope to pick things back up again with this discussion I
> > >would like to start.  I believe this will be a better forum than chat
> > >since not all the module developers hang out there.  As some may have
> > >heard, I recently hacked away at phpwebsite and dropped the memory
> > >requirements below the 8m php default and cut execution times in half.
> > >Now in order for these changes to go into place modules will have to
> > >update some of their calls to core functions.  The reason for this is
> > >because one of the changes made was to split up the long and 
> > >unnecessary
> > >inheritance chain that all the core classes were a part of.  Approval
> > >from a majority of the third party developers is crucial in my decision
> > >to commit these changes to CVS.   So please let me know how you feel
> > >about updating your modules.  Below are examples of some of the updates
> > >that need to be made.
> > >
> > >Before:
> > >The core inherited from the PHPWS_Text class so you where able to call
> > >the function parseInput() like this:
> > >$GLOBALS['core']->parseInput($text_to_parse);
> > >
> > >Now:
> > >The class PHPWS_Text is split off from the core, so you have to do a
> > >require_once(PHPWS_SOURCE_DIR.'core/Text.php');
> > >at the top of the class file you use the function in and then call it
> > >like this:
> > >PHPWS_Text::parseInput($text_to_parse);
> > >
> > >Before:
> > >When you wanted to show some content in a block on the left or right
> > >side of the site you would have just put the code in your modules index
> > >file.
> > >
> > >Now:
> > >Extra content that needs to show up in phpwebsite when your module is
> > >NOT running (ie.  announcements and past announcements on the home 
> > >page)
> > >now needs to be placed in a file called inc/runtime.php in your module.
> > >
> > >Ok now the decision needs to be made.  If a majority of the developers
> > >vote yes then the changes will go into place.  I have a nice sed script
> > >that will do a most of the replacements of old calls for you.  The list
> > >of replacements only do the common ones found throughout phpwebsite so
> > >you may have some left behind that you will have to fix by hand.   Now 
> > >I
> > >am willing to provide assistance upgrading modules in my free time so
> > >don't feel like you will have to figure out all the updates on your own
> > >cause I am sure there will be some special cases.  Alright all you
> > >developers out there fire away.
> > >
> > >-- 
> > >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: SF.net Giveback Program.
> > >SourceForge.net hosts over 70,000 Open Source Projects.
> > >See the people who have HELPED US provide better services:
> > >Click here: http://sourceforge.net/supporters.php
> > >_______________________________________________
> > >Phpwebsite-developers mailing list
> > >Php...@li...
> > >https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> > >
> > >
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback Program.
> > SourceForge.net hosts over 70,000 Open Source Projects.
> > See the people who have HELPED US provide better services:
> > Click here: http://sourceforge.net/supporters.php
> > _______________________________________________
> > Phpwebsite-developers mailing list
> > Php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> > 

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

+1 from me as well.  Although it's times like this when I wish I wasn't
authoring so many modules to go back and update.  :)

Don.

On Wed, Oct 15, 2003 at 09:53:51AM -0700, Richard Sumilang wrote:
> +1 for me
>=20
>=20
> On Wednesday, October 15, 2003, at 07:58  AM, Steven Levin wrote:
>=20
> >Hello everyone,
> >
> >  This list has been very inactive ever since the IRC chat room came
> >about, but I hope to pick things back up again with this discussion I
> >would like to start.  I believe this will be a better forum than chat
> >since not all the module developers hang out there.  As some may have
> >heard, I recently hacked away at phpwebsite and dropped the memory
> >requirements below the 8m php default and cut execution times in half.
> >Now in order for these changes to go into place modules will have to
> >update some of their calls to core functions.  The reason for this is
> >because one of the changes made was to split up the long and=20
> >unnecessary
> >inheritance chain that all the core classes were a part of.  Approval
> >from a majority of the third party developers is crucial in my decision
> >to commit these changes to CVS.   So please let me know how you feel
> >about updating your modules.  Below are examples of some of the updates
> >that need to be made.
> >
> >Before:
> >The core inherited from the PHPWS_Text class so you where able to call
> >the function parseInput() like this:
> >$GLOBALS['core']->parseInput($text_to_parse);
> >
> >Now:
> >The class PHPWS_Text is split off from the core, so you have to do a
> >require_once(PHPWS_SOURCE_DIR.'core/Text.php');
> >at the top of the class file you use the function in and then call it
> >like this:
> >PHPWS_Text::parseInput($text_to_parse);
> >
> >Before:
> >When you wanted to show some content in a block on the left or right
> >side of the site you would have just put the code in your modules index
> >file.
> >
> >Now:
> >Extra content that needs to show up in phpwebsite when your module is
> >NOT running (ie.  announcements and past announcements on the home=20
> >page)
> >now needs to be placed in a file called inc/runtime.php in your module.
> >
> >Ok now the decision needs to be made.  If a majority of the developers
> >vote yes then the changes will go into place.  I have a nice sed script
> >that will do a most of the replacements of old calls for you.  The list
> >of replacements only do the common ones found throughout phpwebsite so
> >you may have some left behind that you will have to fix by hand.   Now=
=20
> >I
> >am willing to provide assistance upgrading modules in my free time so
> >don't feel like you will have to figure out all the updates on your own
> >cause I am sure there will be some special cases.  Alright all you
> >developers out there fire away.
> >
> >--=20
> >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: SF.net Giveback Program.
> >SourceForge.net hosts over 70,000 Open Source Projects.
> >See the people who have HELPED US provide better services:
> >Click here: http://sourceforge.net/supporters.php
> >_______________________________________________
> >Phpwebsite-developers mailing list
> >Php...@li...
> >https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> >
> >
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>=20

Re: [Phpwebsite-developers] phpWebSite Core Updates

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

+1 for me


On Wednesday, October 15, 2003, at 07:58  AM, Steven Levin wrote:

> Hello everyone,
>
>   This list has been very inactive ever since the IRC chat room came
> about, but I hope to pick things back up again with this discussion I
> would like to start.  I believe this will be a better forum than chat
> since not all the module developers hang out there.  As some may have
> heard, I recently hacked away at phpwebsite and dropped the memory
> requirements below the 8m php default and cut execution times in half.
> Now in order for these changes to go into place modules will have to
> update some of their calls to core functions.  The reason for this is
> because one of the changes made was to split up the long and 
> unnecessary
> inheritance chain that all the core classes were a part of.  Approval
> from a majority of the third party developers is crucial in my decision
> to commit these changes to CVS.   So please let me know how you feel
> about updating your modules.  Below are examples of some of the updates
> that need to be made.
>
> Before:
> The core inherited from the PHPWS_Text class so you where able to call
> the function parseInput() like this:
> $GLOBALS['core']->parseInput($text_to_parse);
>
> Now:
> The class PHPWS_Text is split off from the core, so you have to do a
> require_once(PHPWS_SOURCE_DIR.'core/Text.php');
> at the top of the class file you use the function in and then call it
> like this:
> PHPWS_Text::parseInput($text_to_parse);
>
> Before:
> When you wanted to show some content in a block on the left or right
> side of the site you would have just put the code in your modules index
> file.
>
> Now:
> Extra content that needs to show up in phpwebsite when your module is
> NOT running (ie.  announcements and past announcements on the home 
> page)
> now needs to be placed in a file called inc/runtime.php in your module.
>
> Ok now the decision needs to be made.  If a majority of the developers
> vote yes then the changes will go into place.  I have a nice sed script
> that will do a most of the replacements of old calls for you.  The list
> of replacements only do the common ones found throughout phpwebsite so
> you may have some left behind that you will have to fix by hand.   Now 
> I
> am willing to provide assistance upgrading modules in my free time so
> don't feel like you will have to figure out all the updates on your own
> cause I am sure there will be some special cases.  Alright all you
> developers out there fire away.
>
> -- 
> 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: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>

[Phpwebsite-developers] phpWebSite Core Updates

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

Hello everyone,

  This list has been very inactive ever since the IRC chat room came
about, but I hope to pick things back up again with this discussion I
would like to start.  I believe this will be a better forum than chat
since not all the module developers hang out there.  As some may have
heard, I recently hacked away at phpwebsite and dropped the memory
requirements below the 8m php default and cut execution times in half. 
Now in order for these changes to go into place modules will have to
update some of their calls to core functions.  The reason for this is
because one of the changes made was to split up the long and unnecessary
inheritance chain that all the core classes were a part of.  Approval
from a majority of the third party developers is crucial in my decision
to commit these changes to CVS.   So please let me know how you feel
about updating your modules.  Below are examples of some of the updates
that need to be made.

Before:
The core inherited from the PHPWS_Text class so you where able to call
the function parseInput() like this:
$GLOBALS['core']->parseInput($text_to_parse);

Now:
The class PHPWS_Text is split off from the core, so you have to do a
require_once(PHPWS_SOURCE_DIR.'core/Text.php');  
at the top of the class file you use the function in and then call it
like this:
PHPWS_Text::parseInput($text_to_parse);

Before:
When you wanted to show some content in a block on the left or right
side of the site you would have just put the code in your modules index
file.

Now:
Extra content that needs to show up in phpwebsite when your module is
NOT running (ie.  announcements and past announcements on the home page)
now needs to be placed in a file called inc/runtime.php in your module.

Ok now the decision needs to be made.  If a majority of the developers
vote yes then the changes will go into place.  I have a nice sed script
that will do a most of the replacements of old calls for you.  The list
of replacements only do the common ones found throughout phpwebsite so
you may have some left behind that you will have to fix by hand.   Now I
am willing to provide assistance upgrading modules in my free time so
don't feel like you will have to figure out all the updates on your own
cause I am sure there will be some special cases.  Alright all you
developers out there fire away.

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

[Phpwebsite-developers] a question on cookie hashes.

[Lee R. <lr...@ro...>]

   My question is if anyone knows where which part of the code is 
inserting the site hash arguments at the end of the module links at 
first load?  Also, the hidden input added in the forms?  I know these 
are related to cookies set by the page, but I'd like to see the code.

   I've recently been converting one of my sites from postNuke to 
phpWebsite.  The site is for a non-profit organisation, and accessibilty 
compliance is extremely important to them.  I've had a lot of success at 
improving this, the template setup is genius.  It's made this SO much 
easier than on PN.

   I'm also trying to improve the markup compliance to XHTML 1.1.  Thats 
why I'd like to get to that code.  The ampersand needs to be escaped, 
and the hidden input moved into somekind of document tag.

   The site is at http://www.wintermist.org If anyone is interested.

Thanks, Lee Rose
-------
Rose Computer Solutions (su...@ro...)
Geek enough for all you IT/IS needs.

[Phpwebsite-developers] branch_info function

[Roland, R. M <rmr...@in...>]

I wrote a function to return information on branches.
=20
I'm going to submit the code here and let the dev team decide where, if =
anywhere, they want to put it in the codebase.=20
=20
I used commas to separate list items, so if someone sees the need to =
support a branchname with commas in it, then let me know and I'll use a =
different separator, otherwise, I don't see it as a problem.
=20
Thanks,=20

Ryan Roland=20

Application Developer=20
Information Technology=20
Division of Recreational Sports=20
Indiana University

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

/*
 * Function branch_info will return a 2D associative array
 * of information on different branches that exist in your
 * instance of phpws.  Order of fields and branches is <b>not</b>
 * important since returned array is associative.
 *
 * @author Ryan Roland < rmr...@NO...>
 * @param  string $branch_name comma separated list of branches to =
return information on (or "all")
 * @param  string $desired_info comma separated list of information =
fields to return (or "all")
 * @return array 2D associative array with requested information on =
requested branches
 */
function branch_info($branch_name=3D"all",$desired_info=3D"all"){
  // create sql for specified branches
  $sql =3D "SELECT * FROM " . $GLOBALS["core"]->tbl_prefix . =
"branch_sites";

  if ($branch_name !=3D "all") {
    $branches =3D explode(",",$branch_name);

    $addon =3D " WHERE 1=3D0 ";

    foreach ($branches as $next_branch){
      $addon .=3D " OR branchName=3D'" . $next_branch . "'";
    }

    $sql .=3D $addon;
  }

  // get DB data on specified branches
  $result =3D $GLOBALS["core"]->getAll($sql);

  // array of desired information
  $return_info =3D array();

  if(!DB::isError($result) && is_array($result) && sizeof($result) > 0) =
{
    $all_file_items =3D =
array("dbversion","dbhost","dbuser","dbpass","dbname","table_prefix");
    $all_db_items =3D =
array("branchName","configFile","IDhash","branchDir","branchHttp");

    // create list of desired items
    if ($desired_info =3D=3D "all"){
      $file_items =3D $all_file_items;
      $db_itesm =3D $all_db_itesm;
    }
    else{
      $info_types =3D explode(",",$desired_info);
      $file_items =3D array_intersect($all_file_items, $info_types);
      $db_items =3D array_intersect($all_db_items, $info_types);
    }

    // loop through each branch gathering info
    foreach ($result as $branch){
      $return_info[$branch["branchName"]] =3D array();
      if (sizeof($db_items) > 0){
        foreach ($db_items as $type){
          switch($type){
            case "branchName":
              $return_info[$branch["branchName"]]["branchName"] =3D =
$branch["branchName"];
              break;
            case "configFile":
              $return_info[$branch["branchName"]]["configFile"] =3D =
$branch["configFile"];
              break;
            case "IDhash":
              $return_info[$branch["branchName"]]["IDhash"] =3D =
$branch["IDhash"];
              break;
            case "branchDir":
              $return_info[$branch["branchName"]]["branchDir"] =3D =
$branch["branchDir"];
              break;
            case "branchHttp":
              $return_info[$branch["branchName"]]["branchHttp"] =3D =
$branch["branchHttp"];
              break;
          }// end switch
        }// end foreach
      }// end if
      if (sizeof($file_items) > 0){
        // include the config file for each branch to get additional =
info
        include_once($GLOBALS["core"]->source_dir . "conf/branch/" . =
$branch["configFile"]);

        foreach ($file_items as $type){
          switch($type){
            case "dbversion":
              $return_info[$branch["branchName"]]["dbversion"] =3D =
$dbversion;
              break;
            case "dbhost":
              $return_info[$branch["branchName"]]["dbhost"] =3D $dbhost;
              break;
            case "dbuser":
              $return_info[$branch["branchName"]]["dbuser"] =3D $dbuser;
              break;
            case "dbpass":
              $return_info[$branch["branchName"]]["dbpass"] =3D $dbpass;
              break;
            case "dbname":
              $return_info[$branch["branchName"]]["dbname"] =3D $dbname;
              break;
            case "table_prefix":
              $return_info[$branch["branchName"]]["table_prefix"] =3D =
$table_prefix;
              break;
          }// end switch
        }// end foreach
      }// end if
    }// end foreach
  }// end if

  return $return_info;
}//END FUNC branch_info

=20
=20

Re: [Phpwebsite-developers] Displaying related announcements on top of the article

[Pasi <pa...@ik...>]

On Wed, Oct 08, 2003 at 09:47:10AM -0400, Matthew McNaney wrote:
> You could go to layout, turn on move blocks, and move the What's Related
> block to the top position. I'm not sure if that is what you want. A lot
> of people would prefer a little more customization (which we hope to
> have in 0.9.4).
> 

OK.. I'll try this.

Basicly I'd want to have the right area of the screen displayed like it is
now (all the related things there), but in addition to that, have the
related announcements displayed in the beginning of the article (in the
middle view).

And of course the "short version" of the announcements in the middle.. and
then "read more" link or so to see the whole announcement.

Do I have to create a custom module (something like fatcat categorizer), to
do this.. ?

Thanks for your reply!

- Pasi Kärkkäinen


> Best regards,
> Matt
>  
> 
> 
> On Wed, 2003-10-08 at 04:37, Pasi Kärkkäinen wrote:
> > Hello!
> > 
> > [ Please CC to me, I'm not on the list ]
> > 
> > 
> > I'd like to display announcements at the top of the article. Announcements
> > which are related to the same category as the article. Just like at the main
> > page..
> > 
> > Any ideas how to do this? Should I modify the templates, or does it require
> > modifying the code.. I tried looking at the templates, and the code, but I'm
> > not quite sure how I should do this.
> > 
> > Normally when you look at some article, the related announcements (and other
> > related things too) are displayed at the right area of the screen.. I'd like
> > to see the related announcements at the top of the article (middle view)
> > too.
> > 
> > I'm using phpwebsite 0.9.3-1.
> > 
> > Thanks for your help!
> > 
> > -- Pasi Kärkkäinen
> > 
> > [ Please CC to me, I'm not on the list ]
> >        
> >                                    ^
> >                                 .     .
> >                                  Linux
> >                               /    -    \
> >                              Choice.of.the
> >                            .Next.Generation.
> > 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > 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
>