Menu
▾
▴
phpwebsite-developers
|
From: Geoff S. <Ge...@Ho...> - 2001-03-30 01:27:55
|
Check out phpSlash at http://sourceforge.net/projects/phpslash/ or http://phpslash.sourceforge.net/ They're good folks over their. They are trying to something similar to phpWebsite and they are serious about doing it properly. They've been through a lot of the discussions about PEAR / phpLib, theming, and many other issues we are now discussing. There's some good information in their discussion list archives. Geoff Hostricity Web Hosting <http://www.hostricity.com/> |
|
From: Spiggy T. <th...@me...> - 2001-03-30 02:11:49
|
people who checked the openacs site, might have stumbled into this (rather lengthy with all the comments) article. people at openacs seem to be really against mysql. http://openacs.org/philosophy/why-not-mysql.html paivi |
|
From: Mike W. <wi...@ce...> - 2001-03-30 03:16:26
|
Hey, Was there a meeting scheduled for tomorrow? Is it still on? Will a decision "roadmap" be laid out tomorrow on March 30? Just wondering when we will get some direction? Not that I will be much help but I would like to know if I should continue to follow this project or find another. Although I have limited code knowledge I would like to began to learn something maybe about plugins. I've looked at some of the plugins now and see a little bit about how they work, but it sounds like it might get changed around a bit. I've talked to other people who have made forums or weather scripts or financial scripts and I convinced some of them to take a look at phpWebSite, they and I believe that the first plugin in any category will more than likely be the standad in the beginning which will bring more people to their own script and improve it. I think if you end up debating on the best approach to long many are going to lose interest and go with the next version of nuke5 that is going to have "modules", and this project will lose out. I understand things like this take planning and so forth, but my wish would be for a very well thought out decision done in a timely matter. Hopefully we get a sense of direction by this weekend. Anyway, I'll just sit here with my sharp stick and prod you along <g> winzor (wanna be) ----- Original Message ----- From: "Spiggy TheCat" <th...@me...> To: <php...@li...> Sent: Thursday, March 29, 2001 8:14 PM Subject: [Phpwebsite-developers] about mysql (slightly OT) > people who checked the openacs site, might have stumbled into this (rather > lengthy with all the comments) article. people at openacs seem to be really > against mysql. > > http://openacs.org/philosophy/why-not-mysql.html > > paivi > > > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > |
|
From: Todd O. <to...@da...> - 2001-03-30 14:40:24
|
My proposal is that EVERYTHING should be a plug-in, including much of what is now "core" functionality, like the referrer tracking, categories and polls. I want to see phpWS as more of an erector site, with just about everything available a la carte. What does everyone think about this? I think it helps a user mentally organize phpWS and makes my database scheme ;) look more logical. Each plug-in module would have its own admin page too and it would be the perfect place to add access control. --Todd |
|
From: clayton c. <cc...@ca...> - 2001-03-30 14:50:25
|
This is long, so bear with me ... in my portal seeking travels, i ran across TerraCotta (www.terracottasoftware.com) which provides basic infrastucture for site-building. the docs make for good reading. they have a few very interesting features (one of which is that you can automatically download and install features from other terracotta sites - dont ask me about security) in any case one of the issues i was contemplating was one of module dependencies (actually there are two levels of dependency, but i'll just deal with one) lets say david d. developer creates a plugin which mails out notices when concerts are added to the event calendar. well as it stands, we would have to go in and modify the calendar code to accomodate this. also, if he wants to give the 1000th registered member a free subscription to his dead-tree magazine, he'd have to muck about in the code again. and what if he decides to yank the calendar plugin ? well then youve got orphan DB entries to deal with and your other plugins will crash and burn expecting to find something that aint there. one way to handle this is by Alerts ( TC's description and implementation details at www.terracottasoftware.com/tc/doc/alerts ). basically you register interest in events with a callback. when those events occur, your code gets called. these "events" are stored in the database, and you can set up a cron job to process them. they have urgency levels, so a low-disk quota event would get handled before user registration event. They can also be filtered. so in our example the calendar module would call a raise_event() function whenever someone added a new entry (events have associated data, so you can store details). The registration module can raise an event when someone registers. Alerts can get expensive, so we dont do them for very frequently occurring events. Also for efficiency purposes, we can have an events_registered field in the plugins table so that a plugin only needs to raise an event if someone is interested. <question to self>then again, can we manage all of this via cron? but this way we have a greater level control which we can exercise via a web interface</question> just a thought... BTW PHPWeblog uses their html parser to screen user posts. it has a configurable level of screening. Their "Views" feature is an interesting take on block content handling. We should probably look a this too. ----- Original Message ----- From: "Mike Windsor" <wi...@ce...> To: <php...@li...> Sent: Thursday, 29. March 2001 22:16 Subject: [Phpwebsite-developers] Roadmap > Hey, > Was there a meeting scheduled for tomorrow? Is it still on? Will a decision > "roadmap" be laid out tomorrow on March 30? > Just wondering when we will get some direction? Not that I will be much > help but I would like to know if I should continue to follow this project or > find another. Although I have limited code knowledge I would like to began > to learn something maybe about plugins. I've looked at some of the plugins > now and see a little bit about how they work, but it sounds like it might > get changed around a bit. > I've talked to other people who have made forums or weather scripts or > financial scripts and I convinced some of them to take a look at phpWebSite, > they and I believe that the first plugin in any category will more than > likely be the standad in the beginning which will bring more people to their > own script and improve it. I think if you end up debating on the best > approach to long many are going to lose interest and go with the next > version of nuke5 that is going to have "modules", and this project will > lose out. I understand things like this take planning and so forth, but my > wish would be for a very well thought out decision done in a timely matter. > Hopefully we get a sense of direction by this weekend. > Anyway, I'll just sit here with my sharp stick and prod you along <g> > > > winzor > (wanna be) > > > > ----- Original Message ----- > From: "Spiggy TheCat" <th...@me...> > To: <php...@li...> > Sent: Thursday, March 29, 2001 8:14 PM > Subject: [Phpwebsite-developers] about mysql (slightly OT) > > > > people who checked the openacs site, might have stumbled into this (rather > > lengthy with all the comments) article. people at openacs seem to be > really > > against mysql. > > > > http://openacs.org/philosophy/why-not-mysql.html > > > > paivi > > > > > > _______________________________________________ > > Phpwebsite-developers mailing list > > Php...@li... > > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > > > > > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
|
From: Karsten D. <k.d...@tu...> - 2001-03-30 16:25:07
|
On Fri, Mar 30, 2001 at 10:00:19AM -0500, clayton collie wrote: > one way to handle this is by Alerts ( TC's description and implementation > details at www.terracottasoftware.com/tc/doc/alerts ). basically you > register interest in events with a callback. when those events occur, your Another source of information about his is the excellent book by Till Gerken "Web Application Development with PHP4" published by New Riders. He describes the callback system used in phpChat - which can be downloaded at http://www.phpwizard.net/ and also is a good reading :-) There we could look at callback functionality realized in PHP... Regards, Karsten --=20 Why do we have to hide from the police, daddy? Because we use emacs, son. They use vi. ----------------------------- mailto:k.d...@tu... w=B3: http://www.k-fish.de/ gpg: http://www.k-fish.de/mykeys.gpg |
|
From: Geoff S. <Ge...@Ho...> - 2001-03-30 19:44:36
|
The specific example you cite (a plug-in that wants to mail something out) brings up an interesting point. A really good mailing list system that has an api or whatever to allow plug-ins to use it should be a core function. The reason is that we would want for the mailing list to be well integrated with the administration system and the user registration system so that when someone signs up, they can select mailing lists they want to be on and notifications they want to receive when things happen in the various plug-ins. So, a plug-in capability should be the ability to register mailing list and notification items. Geoff Geoff Staples, Hostricity Web Hosting <http://www.hostricity.com/> -----Original Message----- From: php...@li... [mailto:php...@li...]On Behalf Of clayton collie Sent: Friday, March 30, 2001 9:00 AM To: php...@li... Subject: [Phpwebsite-developers] Good Feature to Consider [long] This is long, so bear with me ... in my portal seeking travels, i ran across TerraCotta (www.terracottasoftware.com) which provides basic infrastucture for site-building. the docs make for good reading. they have a few very interesting features (one of which is that you can automatically download and install features from other terracotta sites - dont ask me about security) in any case one of the issues i was contemplating was one of module dependencies (actually there are two levels of dependency, but i'll just deal with one) lets say david d. developer creates a plugin which mails out notices when concerts are added to the event calendar. well as it stands, we would have to go in and modify the calendar code to accomodate this. also, if he wants to give the 1000th registered member a free subscription to his dead-tree magazine, he'd have to muck about in the code again. and what if he decides to yank the calendar plugin ? well then youve got orphan DB entries to deal with and your other plugins will crash and burn expecting to find something that aint there. one way to handle this is by Alerts ( TC's description and implementation details at www.terracottasoftware.com/tc/doc/alerts ). basically you register interest in events with a callback. when those events occur, your code gets called. these "events" are stored in the database, and you can set up a cron job to process them. they have urgency levels, so a low-disk quota event would get handled before user registration event. They can also be filtered. so in our example the calendar module would call a raise_event() function whenever someone added a new entry (events have associated data, so you can store details). The registration module can raise an event when someone registers. Alerts can get expensive, so we dont do them for very frequently occurring events. Also for efficiency purposes, we can have an events_registered field in the plugins table so that a plugin only needs to raise an event if someone is interested. <question to self>then again, can we manage all of this via cron? but this way we have a greater level control which we can exercise via a web interface</question> just a thought... BTW PHPWeblog uses their html parser to screen user posts. it has a configurable level of screening. Their "Views" feature is an interesting take on block content handling. We should probably look a this too. ----- Original Message ----- From: "Mike Windsor" <wi...@ce...> To: <php...@li...> Sent: Thursday, 29. March 2001 22:16 Subject: [Phpwebsite-developers] Roadmap > Hey, > Was there a meeting scheduled for tomorrow? Is it still on? Will a decision > "roadmap" be laid out tomorrow on March 30? > Just wondering when we will get some direction? Not that I will be much > help but I would like to know if I should continue to follow this project or > find another. Although I have limited code knowledge I would like to began > to learn something maybe about plugins. I've looked at some of the plugins > now and see a little bit about how they work, but it sounds like it might > get changed around a bit. > I've talked to other people who have made forums or weather scripts or > financial scripts and I convinced some of them to take a look at phpWebSite, > they and I believe that the first plugin in any category will more than > likely be the standad in the beginning which will bring more people to their > own script and improve it. I think if you end up debating on the best > approach to long many are going to lose interest and go with the next > version of nuke5 that is going to have "modules", and this project will > lose out. I understand things like this take planning and so forth, but my > wish would be for a very well thought out decision done in a timely matter. > Hopefully we get a sense of direction by this weekend. > Anyway, I'll just sit here with my sharp stick and prod you along <g> > > > winzor > (wanna be) > > > > ----- Original Message ----- > From: "Spiggy TheCat" <th...@me...> > To: <php...@li...> > Sent: Thursday, March 29, 2001 8:14 PM > Subject: [Phpwebsite-developers] about mysql (slightly OT) > > > > people who checked the openacs site, might have stumbled into this (rather > > lengthy with all the comments) article. people at openacs seem to be > really > > against mysql. > > > > http://openacs.org/philosophy/why-not-mysql.html > > > > paivi > > > > > > _______________________________________________ > > Phpwebsite-developers mailing list > > Php...@li... > > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > > > > > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers _______________________________________________ Phpwebsite-developers mailing list Php...@li... http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
Thanks for helping keep SourceForge clean.
X