phpwebsite-developers

[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] 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

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
>
>

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

[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

[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

[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

[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...>]

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] 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...>]

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

[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

[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

[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

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