I've used PHPShop (the existing version, not the new core/commerce thing) to
do one site.

It's relatively easy to set up.  I've had to do some modifications to it
(namely, to make it use Payflow link, which works via HTTP requests; and
adding dropdown menus on products to select color & airtime rates -- its a
pager site).  It doesnt use templates exactly.. lots of HTML mixed with PHP.

It definately could use some work.  I havent really checked out the new
version, since the commerce module is not released yet.

I too am interested in modular systems.  I'd like to see some sort of
modular system that makes it easy to integrate together other systems which
are not modular (or are modular but dont have the modules I want).  For
instance, I am using PHPSlash, YapBB (forums) and PHPShop but there's  no
easy way to make them all work together seamlessly, each one has its own
authentication and session handling, its own database, etc.

It would be nice to have a modular API that a completely stand alone
application (like any of three I mentioned) could adhere to, that wouldnt
limit the application in any demanding way, but would allow the application
to also be a module working with any other compliant app.

For instance, forums applications -- most that I've seen are stand alone
systems.  That's fine, but what if I want a forum as a module inside of
something like PHPSlash or PHPNuke?  I could take a forums package, probably
do some pretty extensive mods to it like merging its database with my chosen
"parent" app, replace its authentication and user system, etc, and make it a
module.  I've seen requests for such things, "how about a module for
PHPNuke?".  Then what?  What if you decide you really wanted it to work with
PHPSlash instead?  Start all over!

Everybody has their own idea of how a modular system should be structured,
generaly tailored for the application they want to use it in.  Other people
might not want to write their apps using that system because they dont want
to be tied to it, or dont want all the other baggage of the application
coming along for the ride when they just want the modularity part.

phpshop core looks interesting but its not quite what I'm thinking of, I
think.

I am currently working on such a system that would make it easy to adapt
existing applications to be modules with a minimum of modification.  Its
more of an API and a "shell" or "glue" rather than a complete application.

I dont know if I am truly getting across my idea, but I thought I'd try to
throw it out there for consideration.

"Jaxon" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> thanks, but i'm looking for feedback on modular systems and shopping cart
> engines, not an IDE.
> vi works fine for me, at least for now :)
>
> cheers,
> jaxon
>
> > -----Original Message-----
> > From: Rick Emery [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, January 30, 2002 12:58 PM
> > To: '[EMAIL PROTECTED]'; PHP
> > Subject: RE: [PHP] curious - any phpshop/core users?
> >
> >
> > I use PHP Coder.  It's an excellent IDE and it's free..
> >
> > -----Original Message-----
> > From: Jaxon [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, January 30, 2002 11:46 AM
> > To: PHP
> > Subject: [PHP] curious - any phpshop/core users?
> >
> >
> > hi,
> >
> > has anyone used PHPShop and Core (www.phpshop.org) ??
> > i'm thinking about using it for a project and wanted to know if it's
> > actually any good :)
> >
> > cheers,
> > jaxon
> >
> >
> >
> > --
> > PHP General Mailing List (http://www.php.net/)
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > To contact the list administrators, e-mail: [EMAIL PROTECTED]
> >
> > --
> > PHP General Mailing List (http://www.php.net/)
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > To contact the list administrators, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
>



-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to