phpwslistings-developers Mailing List for phpwsListings (Page 7)
Brought to you by:
rizzo,
wendall911
Menu
▾
▴
phpwslistings-developers — phpwsListings developer mailing list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
(60) |
Apr
(18) |
May
(42) |
Jun
(11) |
Jul
(5) |
Aug
(5) |
Sep
(3) |
Oct
(4) |
Nov
(6) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(6) |
Feb
(5) |
Mar
(6) |
Apr
(1) |
May
(4) |
Jun
(4) |
Jul
|
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(3) |
| 2005 |
Jan
(3) |
Feb
(4) |
Mar
(2) |
Apr
(2) |
May
|
Jun
(2) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Don S. <do...@se...> - 2003-04-11 02:16:52
|
Think I got the update scripts going. I had to add "alter table" support to core's sqlImport script. It was brain-draining enough so I just decided to call sqlUpdate on my own instead of adding support for it. Don. On Thu, 10 Apr 2003, Don Seiler wrote: > I've added update scripts to the boost directory. It was something that > had totally escaped my mind. > > I still have to test them out. Feel free if you have time to install > 0.1.0 and then upgrade to 0.2.0. > > Don. > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger > for complex code. Debugging C/C++ programs can leave you feeling lost and > disoriented. TotalView can help you find your way. Available on major UNIX > and Linux platforms. Try it free. www.etnus.com > _______________________________________________ > phpwslistings-developers mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > |
|
From: Don S. <do...@se...> - 2003-04-10 17:58:40
|
I've added update scripts to the boost directory. It was something that had totally escaped my mind. I still have to test them out. Feel free if you have time to install 0.1.0 and then upgrade to 0.2.0. Don. |
|
From: Don S. <do...@se...> - 2003-04-02 15:48:44
|
OK. While I don't look forward to it right now, it definitely is the way to go. I'll start replacing the "ListingClass" references to use FatCat. This will give me cause to learn the ins and outs of FatCat now too. Thanks. Don. On Wed, 2 Apr 2003, Mike Windsor wrote: > I'm definitely all for it. It'll be a more "integrated" module in my > opinion and actually take advantage of the way phpws is supposed to be used. > It would also eliminate some of the buttons in the admin section and allow > maybe a drop drown of categories to choose from. The "Related Info" box > could then be taken advantage of when looking at things in one category. > > +100 from me > Mike Windsor > > > ----- Original Message ----- > From: "Don Seiler" <do...@se...> > To: "Mike Windsor" <wi...@ce...> > Cc: "phpwsListings" <php...@li...> > Sent: Tuesday, April 01, 2003 10:10 PM > Subject: Re: [phpwslistings-dev] Listing Class = FatCat Category > > > > I wonder if we shouldn't implement this change immediately and put the > > brakes on 0.2.0. If we agree that using FatCat is the way to go, then I'd > > rather do it right the first time. > > > > What do you gents think. > > > > Don. > > > > On Sat, 29 Mar 2003, Don Seiler wrote: > > > > > Hm this never even occured to me. > > > > > > It sounds like a good idea from the off. Perhaps there might be > downsides > > > to using fatcat though that we have not thought of. > > > > > > Don. > > > > > > On Sat, 29 Mar 2003, Mike Windsor wrote: > > > > > > > Would it be a good idea to use FatCat categories for the classes > instead of > > > > making our own class? It would be cool if it could work that way, > then if > > > > you were to write an article for say "Real Estate", it would show > "Related > > > > Items" in a block such as the listings and calendar events or anything > else > > > > tied to that category. > > > > > > > > Mike > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.net email is sponsored by: > > > > The Definitive IT and Networking Event. Be There! > > > > NetWorld+Interop Las Vegas 2003 -- Register today! > > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > > > > _______________________________________________ > > > > phpwslistings-developers mailing list > > > > php...@li... > > > > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.net email is sponsored by: > > > The Definitive IT and Networking Event. Be There! > > > NetWorld+Interop Las Vegas 2003 -- Register today! > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > > > _______________________________________________ > > > phpwslistings-developers mailing list > > > php...@li... > > > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > > > > > > > > > > > > > > > > |
|
From: Mike W. <wi...@ce...> - 2003-04-02 13:38:21
|
I'm definitely all for it. It'll be a more "integrated" module in my opinion and actually take advantage of the way phpws is supposed to be used. It would also eliminate some of the buttons in the admin section and allow maybe a drop drown of categories to choose from. The "Related Info" box could then be taken advantage of when looking at things in one category. +100 from me Mike Windsor ----- Original Message ----- From: "Don Seiler" <do...@se...> To: "Mike Windsor" <wi...@ce...> Cc: "phpwsListings" <php...@li...> Sent: Tuesday, April 01, 2003 10:10 PM Subject: Re: [phpwslistings-dev] Listing Class = FatCat Category > I wonder if we shouldn't implement this change immediately and put the > brakes on 0.2.0. If we agree that using FatCat is the way to go, then I'd > rather do it right the first time. > > What do you gents think. > > Don. > > On Sat, 29 Mar 2003, Don Seiler wrote: > > > Hm this never even occured to me. > > > > It sounds like a good idea from the off. Perhaps there might be downsides > > to using fatcat though that we have not thought of. > > > > Don. > > > > On Sat, 29 Mar 2003, Mike Windsor wrote: > > > > > Would it be a good idea to use FatCat categories for the classes instead of > > > making our own class? It would be cool if it could work that way, then if > > > you were to write an article for say "Real Estate", it would show "Related > > > Items" in a block such as the listings and calendar events or anything else > > > tied to that category. > > > > > > Mike > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.net email is sponsored by: > > > The Definitive IT and Networking Event. Be There! > > > NetWorld+Interop Las Vegas 2003 -- Register today! > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > > > _______________________________________________ > > > phpwslistings-developers mailing list > > > php...@li... > > > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > > > > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: > > The Definitive IT and Networking Event. Be There! > > NetWorld+Interop Las Vegas 2003 -- Register today! > > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > > _______________________________________________ > > phpwslistings-developers mailing list > > php...@li... > > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > > > > > > |
|
From: Don S. <do...@se...> - 2003-04-02 04:16:32
|
I wonder if we shouldn't implement this change immediately and put the brakes on 0.2.0. If we agree that using FatCat is the way to go, then I'd rather do it right the first time. What do you gents think. Don. On Sat, 29 Mar 2003, Don Seiler wrote: > Hm this never even occured to me. > > It sounds like a good idea from the off. Perhaps there might be downsides > to using fatcat though that we have not thought of. > > Don. > > On Sat, 29 Mar 2003, Mike Windsor wrote: > > > Would it be a good idea to use FatCat categories for the classes instead of > > making our own class? It would be cool if it could work that way, then if > > you were to write an article for say "Real Estate", it would show "Related > > Items" in a block such as the listings and calendar events or anything else > > tied to that category. > > > > Mike > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: > > The Definitive IT and Networking Event. Be There! > > NetWorld+Interop Las Vegas 2003 -- Register today! > > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > > _______________________________________________ > > phpwslistings-developers mailing list > > php...@li... > > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: > The Definitive IT and Networking Event. Be There! > NetWorld+Interop Las Vegas 2003 -- Register today! > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > _______________________________________________ > phpwslistings-developers mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > |
|
From: <ad...@tu...> - 2003-03-31 18:09:31
|
> Adam do you have any insight into the status of Hub-It? I don't see much effort being put into hubit for a while. Word on the street was we were going to create a network core class and use that to drive hubit, but that talk was a long time ago and I haven't heard much since then. Adam -- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: Don S. <do...@se...> - 2003-03-29 21:50:06
|
Hm this never even occured to me. It sounds like a good idea from the off. Perhaps there might be downsides to using fatcat though that we have not thought of. Don. On Sat, 29 Mar 2003, Mike Windsor wrote: > Would it be a good idea to use FatCat categories for the classes instead of > making our own class? It would be cool if it could work that way, then if > you were to write an article for say "Real Estate", it would show "Related > Items" in a block such as the listings and calendar events or anything else > tied to that category. > > Mike > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: > The Definitive IT and Networking Event. Be There! > NetWorld+Interop Las Vegas 2003 -- Register today! > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > _______________________________________________ > phpwslistings-developers mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > |
|
From: Mike W. <wi...@ce...> - 2003-03-29 21:28:26
|
Would it be a good idea to use FatCat categories for the classes instead of making our own class? It would be cool if it could work that way, then if you were to write an article for say "Real Estate", it would show "Related Items" in a block such as the listings and calendar events or anything else tied to that category. Mike |
|
From: Don S. <do...@se...> - 2003-03-26 23:09:25
|
I updated the website to include all our names, and directed comments be directed to the sf.net forums instead of emailed to me. I know Mike Noyes said that phpws's HubIt mod would handle sf.net RSS feeds. If this is the case then we could probably run phpws for our site, and have second install (different directory, same database with prefixes since sf only give us one db) for the demo. Adam do you have any insight into the status of Hub-It? Don. |
|
From: Mike W. <wi...@ce...> - 2003-03-26 17:31:15
|
Yeah probably should wait since the rmdir thing has been implemented. Mike ----- Original Message ----- From: "Don Seiler" <do...@se...> To: "phpwslistings dev krew" <php...@li...> Sent: Wednesday, March 26, 2003 11:20 AM Subject: Re: [phpwslistings-dev] release 0.2.0 rc 1 > Now that I think about it, will 0.2.0 depend on phpws 0.9.1? We can still > make RC releases and tell the users to use phpws from CVS. But for a > final release we'll probably need to wait until phpws 0.9.1 is released. > > Don. > > On Wed, 26 Mar 2003, Don Seiler wrote: > > > I built the tarball for 0.2.0 rc1 but sf.net is currently having a known > > problem with their file release system. As soon as that issue is resolved > > (I'm on #sourceforge in irc.slashnet.org) I'll post the release and update > > our news. > > > > Don. > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: > > The Definitive IT and Networking Event. Be There! > > NetWorld+Interop Las Vegas 2003 -- Register today! > > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > > _______________________________________________ > > phpwslistings-developers mailing list > > php...@li... > > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: > The Definitive IT and Networking Event. Be There! > NetWorld+Interop Las Vegas 2003 -- Register today! > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > _______________________________________________ > phpwslistings-developers mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > |
|
From: Don S. <do...@se...> - 2003-03-26 17:27:49
|
Problem is fixed and release is made. Don. On Wed, 26 Mar 2003, Don Seiler wrote: > I built the tarball for 0.2.0 rc1 but sf.net is currently having a known > problem with their file release system. As soon as that issue is resolved > (I'm on #sourceforge in irc.slashnet.org) I'll post the release and update > our news. > > Don. > > > ------------------------------------------------------- > This SF.net email is sponsored by: > The Definitive IT and Networking Event. Be There! > NetWorld+Interop Las Vegas 2003 -- Register today! > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > _______________________________________________ > phpwslistings-developers mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > |
|
From: Don S. <do...@se...> - 2003-03-26 17:20:16
|
Now that I think about it, will 0.2.0 depend on phpws 0.9.1? We can still make RC releases and tell the users to use phpws from CVS. But for a final release we'll probably need to wait until phpws 0.9.1 is released. Don. On Wed, 26 Mar 2003, Don Seiler wrote: > I built the tarball for 0.2.0 rc1 but sf.net is currently having a known > problem with their file release system. As soon as that issue is resolved > (I'm on #sourceforge in irc.slashnet.org) I'll post the release and update > our news. > > Don. > > > ------------------------------------------------------- > This SF.net email is sponsored by: > The Definitive IT and Networking Event. Be There! > NetWorld+Interop Las Vegas 2003 -- Register today! > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > _______________________________________________ > phpwslistings-developers mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > |
|
From: Don S. <do...@se...> - 2003-03-26 16:12:01
|
I built the tarball for 0.2.0 rc1 but sf.net is currently having a known problem with their file release system. As soon as that issue is resolved (I'm on #sourceforge in irc.slashnet.org) I'll post the release and update our news. Don. |
|
From: Don S. <do...@se...> - 2003-03-26 14:40:04
|
very cool. Maybe I'll carve out a link for a list of sites running it. How did you find out about this one? Don. On Tue, 25 Mar 2003, Mike Windsor wrote: > http://www.delanorealty.com/ > > Mike > > > > |
|
From: Don S. <do...@se...> - 2003-03-25 14:45:01
|
Mortgage calculator thing is done. Don. On Tue, 25 Mar 2003, Don Seiler wrote: > On Tue, 25 Mar 2003, Don Seiler wrote: > > > I think we might be ready for 0.2.0 testing and RCs with > > everything else, unless I'm forgetting something hugely obvious. > > I was forgetting RFE #708082. We'll need to tie the "enable mortgage > calculator" option to classes now. I'll try and get that done today. > > Don. > > > ------------------------------------------------------- > This SF.net email is sponsored by: > The Definitive IT and Networking Event. Be There! > NetWorld+Interop Las Vegas 2003 -- Register today! > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > _______________________________________________ > phpwslistings-developers mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > |
|
From: Don S. <do...@se...> - 2003-03-25 13:50:43
|
On Tue, 25 Mar 2003, Don Seiler wrote: > I think we might be ready for 0.2.0 testing and RCs with > everything else, unless I'm forgetting something hugely obvious. I was forgetting RFE #708082. We'll need to tie the "enable mortgage calculator" option to classes now. I'll try and get that done today. Don. |
|
From: Don S. <do...@se...> - 2003-03-25 13:41:44
|
No we were talking about making them <a href> tags instead of submit buttons. I know this request was marked for 0.2.0 but is it possible we can move it to 0.3.0? I think we might be ready for 0.2.0 testing and RCs with everything else, unless I'm forgetting something hugely obvious. Unless we can come up with a clean way for an href tag to look at the value of a select box. Don. On Mon, 24 Mar 2003, Mike Windsor wrote: > Found this doing a search. > > <INPUT TYPE="SUBMIT" VALUE="Demonstration only" > STYLE="font-family:sans-serif; font-size:large; > font-style:italic; background:#ff0 none; color:#000; width:10em"> > > Hope that is what you were referring to. I haven't tried it. > > Mike > > > ----- Original Message ----- > From: "Don Seiler" <do...@se...> > To: <ad...@tu...> > Cc: <php...@li...> > Sent: Monday, March 24, 2003 4:04 PM > Subject: Re: [phpwslistings-dev] menu.tpl > > > > I agree 100% and will probably work towards replacing those menu submits > > with links (including the edit/delete buttons on the list pages). > > > > However, how will I be able to pass in the desired class type in the > > "Create Listing" function? I don't want to use javascript to update > > hidden form elements. I just don't trust javascript's cross-browser > > functionality (thank you IE). > > > > Don. > > > > On Mon, 24 Mar 2003 ad...@tu... wrote: > > > > > Sorry I took so long getting back to you on this one... > > > > > > I'm not an expert in interface design but I think you should attempt to > > > have the menu only contain hyperlinks and no form elements. This may > mean > > > you need to move some of those form elements to other places in your > > > module but it would allow more flexability with how the general menu is > > > displayed. This includes allowing users to move the block anywhere they > > > wish and perhaps replace the textual links with linked custom images. > > > > > > The "class chooser" (dropbox) for searching and viewing listings could > be > > > moved into the search and view sections of the module and just default > to > > > the first one in the list or simply search all classes (some people may > > > want this functionality anyway). Then the user would have a choice of > > > refining their search. A good example would be a clothing site. The > > > classes could be something like pants, shirts, and shoes. When a user > > > initially browses or searches, they are searching all the products, then > > > the user can refine their search or viewing to just pants or just > shirts, > > > etc. > > > > > > Hope that helps :) > > > > > > Adam > > > > > > > Adam can you take a look at RFE 703136 and let me know what your > opinion > > > > is. > > > > > > > > > https://sourceforge.net/tracker/index.php?func=detail&aid=703136&group_id=73 > 598&atid=538277 > > > > > > > > Mike is concerned about the menu getting too long horizontally. > > > > > > > > Don. > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.net email is sponsored by:Crypto Challenge is now open! > > > > Get cracking and register here for some mind boggling fun and > > > > the chance of winning an Apple iPod: > > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > > > > _______________________________________________ > > > > phpwslistings-developers mailing list > > > > php...@li... > > > > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > phpwslistings-developers mailing list > > php...@li... > > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > phpwslistings-developers mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > |
|
From: Mike W. <wi...@ce...> - 2003-03-24 22:21:04
|
Found this doing a search. <INPUT TYPE="SUBMIT" VALUE="Demonstration only" STYLE="font-family:sans-serif; font-size:large; font-style:italic; background:#ff0 none; color:#000; width:10em"> Hope that is what you were referring to. I haven't tried it. Mike ----- Original Message ----- From: "Don Seiler" <do...@se...> To: <ad...@tu...> Cc: <php...@li...> Sent: Monday, March 24, 2003 4:04 PM Subject: Re: [phpwslistings-dev] menu.tpl > I agree 100% and will probably work towards replacing those menu submits > with links (including the edit/delete buttons on the list pages). > > However, how will I be able to pass in the desired class type in the > "Create Listing" function? I don't want to use javascript to update > hidden form elements. I just don't trust javascript's cross-browser > functionality (thank you IE). > > Don. > > On Mon, 24 Mar 2003 ad...@tu... wrote: > > > Sorry I took so long getting back to you on this one... > > > > I'm not an expert in interface design but I think you should attempt to > > have the menu only contain hyperlinks and no form elements. This may mean > > you need to move some of those form elements to other places in your > > module but it would allow more flexability with how the general menu is > > displayed. This includes allowing users to move the block anywhere they > > wish and perhaps replace the textual links with linked custom images. > > > > The "class chooser" (dropbox) for searching and viewing listings could be > > moved into the search and view sections of the module and just default to > > the first one in the list or simply search all classes (some people may > > want this functionality anyway). Then the user would have a choice of > > refining their search. A good example would be a clothing site. The > > classes could be something like pants, shirts, and shoes. When a user > > initially browses or searches, they are searching all the products, then > > the user can refine their search or viewing to just pants or just shirts, > > etc. > > > > Hope that helps :) > > > > Adam > > > > > Adam can you take a look at RFE 703136 and let me know what your opinion > > > is. > > > > > > https://sourceforge.net/tracker/index.php?func=detail&aid=703136&group_id=73 598&atid=538277 > > > > > > Mike is concerned about the menu getting too long horizontally. > > > > > > Don. > > > > > > > > > ------------------------------------------------------- > > > This SF.net email is sponsored by:Crypto Challenge is now open! > > > Get cracking and register here for some mind boggling fun and > > > the chance of winning an Apple iPod: > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > > > _______________________________________________ > > > phpwslistings-developers mailing list > > > php...@li... > > > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > > > > > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > phpwslistings-developers mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > |
|
From: Don S. <do...@se...> - 2003-03-24 22:04:42
|
I agree 100% and will probably work towards replacing those menu submits with links (including the edit/delete buttons on the list pages). However, how will I be able to pass in the desired class type in the "Create Listing" function? I don't want to use javascript to update hidden form elements. I just don't trust javascript's cross-browser functionality (thank you IE). Don. On Mon, 24 Mar 2003 ad...@tu... wrote: > Sorry I took so long getting back to you on this one... > > I'm not an expert in interface design but I think you should attempt to > have the menu only contain hyperlinks and no form elements. This may mean > you need to move some of those form elements to other places in your > module but it would allow more flexability with how the general menu is > displayed. This includes allowing users to move the block anywhere they > wish and perhaps replace the textual links with linked custom images. > > The "class chooser" (dropbox) for searching and viewing listings could be > moved into the search and view sections of the module and just default to > the first one in the list or simply search all classes (some people may > want this functionality anyway). Then the user would have a choice of > refining their search. A good example would be a clothing site. The > classes could be something like pants, shirts, and shoes. When a user > initially browses or searches, they are searching all the products, then > the user can refine their search or viewing to just pants or just shirts, > etc. > > Hope that helps :) > > Adam > > > Adam can you take a look at RFE 703136 and let me know what your opinion > > is. > > > > https://sourceforge.net/tracker/index.php?func=detail&aid=703136&group_id=73598&atid=538277 > > > > Mike is concerned about the menu getting too long horizontally. > > > > Don. > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by:Crypto Challenge is now open! > > Get cracking and register here for some mind boggling fun and > > the chance of winning an Apple iPod: > > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > > _______________________________________________ > > phpwslistings-developers mailing list > > php...@li... > > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > > > > |
|
From: <ad...@tu...> - 2003-03-24 19:46:00
|
I might have to think about it a bit more but I would probably try using
the variable name in setUserVar to designate and check class permissions.
Ex:
$_SESSION["OBJ_users"]->setUserVar("PHPWS_LISTINGS_" . $class_name, 3);
The PHPWS_LISTINGS_ is to make sure your variable is unique among all the
user variables and the $class_name is the name of the class whos
permissions you are setting up. You would check the variable the same way
and if nothing exists at PHPWS_LISTINGS_ . $class_name then the user does
not have access to that class.
Adam
> Masking makes my jeans creamy.
>
> How would you assign class-specific permissions?
>
> I have been meaning to consolidate some of the module_rights.
>
> Don.
>
> On Mon, 24 Mar 2003 ad...@tu... wrote:
>
>> OK I may miss some things here because I'm not a real estate agent and I
>> don't know all the ins and outs of what needs to happen there. On the
>> other hand I've been looking at the system with more than real estate in
>> mind and so I'm trying to be as abstract as possible.
>>
>> If a user is given base access to the phpwslistings module, they are
>> considered an "agent". A "broker" is designated with a single
>> sub-permisssion. If the broker permission is set for a user, they get
>> total access to the module almost like a deity (without access to all
>> other modules of course). Then you could add several other permissions
>> that are for refining an agents access to the system. These permissions
>> would be bypassed in the case of a broker.
>>
>> module_rights.txt:
>>
>> is_broker::User is a Broker
>> add_listing::Add Listings
>> delete_listing::Remove Listing
>> view_sold::View Sold Listings
>>
>> This method would work for most situations but then you get into the
>> mess
>> of handling multiple "dynamic" classes and controling agent and broker
>> permissions within each class. To best handle a situation like that you
>> would need limited user of the phpws user module and would need to
>> implement your own layer of permissions into the phpwslistings module
>> itself.
>>
>> If a user is given base access to the phpwslistings module, they are
>> considered an agent with no permissions (yet). Then with a single
>> sub-permission you could designate a user as a broker.
>>
>> module_rights.txt:
>>
>> is_broker::User is a Broker
>>
>> Then, within phpwslistings, a broker can view and edit the permissions
>> of
>> agents and assign them to classes if they wish. It should be possible
>> to
>> use the setUserVar and getUserVar functions to make this easier on the
>> developer. For storage of those permissions I would suggest using
>> masking
>> of bits for speed and limited memory usage. I actually suggested that
>> for
>> the phpws user module but Matt didn't know what I meant :)
>>
>> For each agent they would have a userVar called something like
>> phpwslistings_perms. This would simply be an integer number that
>> represents the permissions of that particular agent. Lets say we have 3
>> permissions, add listing, delete listing, and view sold listings. If we
>> represent each of these in binary they would look something like this:
>>
>> 001 = add listing
>> 010 = delete listing
>> 100 = view sold listings
>> 011 = add and delete listings
>> 111 = full access to the system - broker only functions
>>
>> Then you could define masks like:
>>
>> PHPWSLISTINGS_ADD_MASK = 001;
>> PHPWSLISTINGS_DELETE_MASK = 010;
>> PHPWSLISTINGS_SOLD_MASK = 100;
>>
>> "AND" those with the users stored variable and you will get a boolean
>> TRUE/FALSE as to whether or not the agent has access to that permission:
>>
>> $add_check = $_SESSION["OBJ_user"]->getUserVar("phpwslistings_perms") &
>> PHPWSLISTINGS_ADD_MASK;
>>
>> if($add_check) {
>> ...do add...
>> } else {
>> ...doesnt have permission...
>> }
>>
>> That probably a lot to take in. Let me know if anything was unclear as
>> I
>> tend to ramble on :)
>>
>> Adam
>>
>> > Adam,
>> >
>> >> I would suggest not using a phpws user as an agent and just associate
>> an
>> >> agent with a phpws user account. This way you can accomplish the
>> >> permissioning goals you have set down and if the admin of the website
>> >> wants to allow public users to have accounts on the site for various
>> >> reasons (personal house listings, remembered settings, etc) you don't
>> >> want
>> >> them to have "agent status" in the phpwslistings system. I can say
>> more
>> >> here but I will refrain for now to hear your thoughts on what I've
>> >> written
>> >> so far.
>> >
>> > Sounds intersting. I think I understand your concept but would like
>> you
>> > to
>> > elaborate some more if you would.
>> >
>> >
>> > Mike Windsor
>> >
>> >
>> >
>> >
>> > -------------------------------------------------------
>> > This SF.net email is sponsored by: Tablet PC.
>> > Does your code think in ink? You could win a Tablet PC.
>> > Get a free Tablet PC hat just for playing. What are you waiting for?
>> > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
>> > _______________________________________________
>> > phpwslistings-developers mailing list
>> > php...@li...
>> > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers
>> >
>>
>>
>>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> phpwslistings-developers mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers
>
--
Adam Morton
Developer - Electronic Student Services
http://phpwebsite.appstate.edu
Founder - Appalachian Linux Users Group
http://alug.appstate.edu
|
|
From: Don S. <do...@se...> - 2003-03-24 18:12:05
|
Masking makes my jeans creamy.
How would you assign class-specific permissions?
I have been meaning to consolidate some of the module_rights.
Don.
On Mon, 24 Mar 2003 ad...@tu... wrote:
> OK I may miss some things here because I'm not a real estate agent and I
> don't know all the ins and outs of what needs to happen there. On the
> other hand I've been looking at the system with more than real estate in
> mind and so I'm trying to be as abstract as possible.
>
> If a user is given base access to the phpwslistings module, they are
> considered an "agent". A "broker" is designated with a single
> sub-permisssion. If the broker permission is set for a user, they get
> total access to the module almost like a deity (without access to all
> other modules of course). Then you could add several other permissions
> that are for refining an agents access to the system. These permissions
> would be bypassed in the case of a broker.
>
> module_rights.txt:
>
> is_broker::User is a Broker
> add_listing::Add Listings
> delete_listing::Remove Listing
> view_sold::View Sold Listings
>
> This method would work for most situations but then you get into the mess
> of handling multiple "dynamic" classes and controling agent and broker
> permissions within each class. To best handle a situation like that you
> would need limited user of the phpws user module and would need to
> implement your own layer of permissions into the phpwslistings module
> itself.
>
> If a user is given base access to the phpwslistings module, they are
> considered an agent with no permissions (yet). Then with a single
> sub-permission you could designate a user as a broker.
>
> module_rights.txt:
>
> is_broker::User is a Broker
>
> Then, within phpwslistings, a broker can view and edit the permissions of
> agents and assign them to classes if they wish. It should be possible to
> use the setUserVar and getUserVar functions to make this easier on the
> developer. For storage of those permissions I would suggest using masking
> of bits for speed and limited memory usage. I actually suggested that for
> the phpws user module but Matt didn't know what I meant :)
>
> For each agent they would have a userVar called something like
> phpwslistings_perms. This would simply be an integer number that
> represents the permissions of that particular agent. Lets say we have 3
> permissions, add listing, delete listing, and view sold listings. If we
> represent each of these in binary they would look something like this:
>
> 001 = add listing
> 010 = delete listing
> 100 = view sold listings
> 011 = add and delete listings
> 111 = full access to the system - broker only functions
>
> Then you could define masks like:
>
> PHPWSLISTINGS_ADD_MASK = 001;
> PHPWSLISTINGS_DELETE_MASK = 010;
> PHPWSLISTINGS_SOLD_MASK = 100;
>
> "AND" those with the users stored variable and you will get a boolean
> TRUE/FALSE as to whether or not the agent has access to that permission:
>
> $add_check = $_SESSION["OBJ_user"]->getUserVar("phpwslistings_perms") &
> PHPWSLISTINGS_ADD_MASK;
>
> if($add_check) {
> ...do add...
> } else {
> ...doesnt have permission...
> }
>
> That probably a lot to take in. Let me know if anything was unclear as I
> tend to ramble on :)
>
> Adam
>
> > Adam,
> >
> >> I would suggest not using a phpws user as an agent and just associate an
> >> agent with a phpws user account. This way you can accomplish the
> >> permissioning goals you have set down and if the admin of the website
> >> wants to allow public users to have accounts on the site for various
> >> reasons (personal house listings, remembered settings, etc) you don't
> >> want
> >> them to have "agent status" in the phpwslistings system. I can say more
> >> here but I will refrain for now to hear your thoughts on what I've
> >> written
> >> so far.
> >
> > Sounds intersting. I think I understand your concept but would like you
> > to
> > elaborate some more if you would.
> >
> >
> > Mike Windsor
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Tablet PC.
> > Does your code think in ink? You could win a Tablet PC.
> > Get a free Tablet PC hat just for playing. What are you waiting for?
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> > _______________________________________________
> > phpwslistings-developers mailing list
> > php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers
> >
>
>
>
|
|
From: <ad...@tu...> - 2003-03-24 17:37:18
|
OK I may miss some things here because I'm not a real estate agent and I
don't know all the ins and outs of what needs to happen there. On the
other hand I've been looking at the system with more than real estate in
mind and so I'm trying to be as abstract as possible.
If a user is given base access to the phpwslistings module, they are
considered an "agent". A "broker" is designated with a single
sub-permisssion. If the broker permission is set for a user, they get
total access to the module almost like a deity (without access to all
other modules of course). Then you could add several other permissions
that are for refining an agents access to the system. These permissions
would be bypassed in the case of a broker.
module_rights.txt:
is_broker::User is a Broker
add_listing::Add Listings
delete_listing::Remove Listing
view_sold::View Sold Listings
This method would work for most situations but then you get into the mess
of handling multiple "dynamic" classes and controling agent and broker
permissions within each class. To best handle a situation like that you
would need limited user of the phpws user module and would need to
implement your own layer of permissions into the phpwslistings module
itself.
If a user is given base access to the phpwslistings module, they are
considered an agent with no permissions (yet). Then with a single
sub-permission you could designate a user as a broker.
module_rights.txt:
is_broker::User is a Broker
Then, within phpwslistings, a broker can view and edit the permissions of
agents and assign them to classes if they wish. It should be possible to
use the setUserVar and getUserVar functions to make this easier on the
developer. For storage of those permissions I would suggest using masking
of bits for speed and limited memory usage. I actually suggested that for
the phpws user module but Matt didn't know what I meant :)
For each agent they would have a userVar called something like
phpwslistings_perms. This would simply be an integer number that
represents the permissions of that particular agent. Lets say we have 3
permissions, add listing, delete listing, and view sold listings. If we
represent each of these in binary they would look something like this:
001 = add listing
010 = delete listing
100 = view sold listings
011 = add and delete listings
111 = full access to the system - broker only functions
Then you could define masks like:
PHPWSLISTINGS_ADD_MASK = 001;
PHPWSLISTINGS_DELETE_MASK = 010;
PHPWSLISTINGS_SOLD_MASK = 100;
"AND" those with the users stored variable and you will get a boolean
TRUE/FALSE as to whether or not the agent has access to that permission:
$add_check = $_SESSION["OBJ_user"]->getUserVar("phpwslistings_perms") &
PHPWSLISTINGS_ADD_MASK;
if($add_check) {
...do add...
} else {
...doesnt have permission...
}
That probably a lot to take in. Let me know if anything was unclear as I
tend to ramble on :)
Adam
> Adam,
>
>> I would suggest not using a phpws user as an agent and just associate an
>> agent with a phpws user account. This way you can accomplish the
>> permissioning goals you have set down and if the admin of the website
>> wants to allow public users to have accounts on the site for various
>> reasons (personal house listings, remembered settings, etc) you don't
>> want
>> them to have "agent status" in the phpwslistings system. I can say more
>> here but I will refrain for now to hear your thoughts on what I've
>> written
>> so far.
>
> Sounds intersting. I think I understand your concept but would like you
> to
> elaborate some more if you would.
>
>
> Mike Windsor
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Tablet PC.
> Does your code think in ink? You could win a Tablet PC.
> Get a free Tablet PC hat just for playing. What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> phpwslistings-developers mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers
>
--
Adam Morton
Developer - Electronic Student Services
http://phpwebsite.appstate.edu
Founder - Appalachian Linux Users Group
http://alug.appstate.edu
|
|
From: <ad...@tu...> - 2003-03-24 17:09:19
|
I checked this out and it was a bug in my code when it attempted to traverse subdirectories. I've fixed it and the changes are in cvs File.php. I also tested the phpwslistings module and it seems to work fine even after having images in the directories. Thanks for finding that Don :) Adam > Adam, > > I'm getting this error trying to uninstall the module when I have images > in the directory: > > Warning: > rmdir(/home/httpd/htdocs/phpwebsite-full/phpwebsite/images/phpwslistings/) > [function.rmdir]: Directory not empty in > /home/httpd/htdocs/phpwebsite-full/phpwebsite/core/File.php on line 316 > > FYI. > > Don. > > > ------------------------------------------------------- > This SF.net email is sponsored by:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > phpwslistings-developers mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > -- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: <ad...@tu...> - 2003-03-24 17:07:50
|
Sorry I took so long getting back to you on this one... I'm not an expert in interface design but I think you should attempt to have the menu only contain hyperlinks and no form elements. This may mean you need to move some of those form elements to other places in your module but it would allow more flexability with how the general menu is displayed. This includes allowing users to move the block anywhere they wish and perhaps replace the textual links with linked custom images. The "class chooser" (dropbox) for searching and viewing listings could be moved into the search and view sections of the module and just default to the first one in the list or simply search all classes (some people may want this functionality anyway). Then the user would have a choice of refining their search. A good example would be a clothing site. The classes could be something like pants, shirts, and shoes. When a user initially browses or searches, they are searching all the products, then the user can refine their search or viewing to just pants or just shirts, etc. Hope that helps :) Adam > Adam can you take a look at RFE 703136 and let me know what your opinion > is. > > https://sourceforge.net/tracker/index.php?func=detail&aid=703136&group_id=73598&atid=538277 > > Mike is concerned about the menu getting too long horizontally. > > Don. > > > ------------------------------------------------------- > This SF.net email is sponsored by:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > phpwslistings-developers mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > -- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: Mike W. <wi...@ce...> - 2003-03-22 16:03:47
|
I agree with this. I've tried the cvs version of this and it looks to be the way to go. If someone was only listing one class, it would be confusing to have the dropdown. So yes good work. Mike ----- Original Message ----- From: "Don Seiler" <do...@se...> To: "phpwslistings dev krew" <php...@li...> Sent: Friday, March 21, 2003 9:34 AM Subject: [phpwslistings-dev] classes > I think we should have an "enable multiple classes" option in settings, so > that if it isn't checked, the admin will still need to set up one class, > but then the class_id would be set in a hidden form var instead of > presenting a select-box. > > Holla Back. > > Don. > > > ------------------------------------------------------- > This SF.net email is sponsored by:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > phpwslistings-developers mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwslistings-developers > > |
