NYCPHP Meetup

[Chalu Kim]

You sound like you are committed to checkins and checkouts. But you could
also look at it in the workflow.

For example, you create a content initially private. Once you submit to
published. Then, you can checkout and checkin. In turn, they can be viewed
as locked or unlocked(or available). You can also retract it.

You notice there is a state machine based states and transitions. For
example, you start with a state of "private". moving onto "submitted" with
transition of "submit", onto "published" or "into repository" via
"publish"...

I think you could benefit from workflow.

There are a number of efforts out there;

http://www.openflow.it/EN/index_html
http://www.zope.org/Members/hathawsh/DCWorkflow_docs

The problem you are trying to tackle seems to require a framework. If you
are just interested in checkin and checkout, there is CVS modules for
Zope/Python.

On Mon, 26 May 2003, Hans Zaunere wrote:

>
> --- Rudy Gamberini <rudy at taytek.com> wrote:
> > First a little background.  While I develop LAMP applications my paying job
> > is as a software process engineer.  I’m from the dark-side as some
> > developers like to refer to my role.  One of the major elements of a
> > well-defined development organization is a Process Asset Library (PAL).  A
> > PAL is a controlled repository of artifacts typically used in the software
> > development process.  While I won’t bore you with all the attributes
> > associated with each of the artifacts what is important is the fact that
> > these artifacts are controlled via a configuration managed (CM) tool.  The
> > artifacts range in type from Word documents to Excel spreadsheets to
> > Powerpoint presentations.   In today’s world we use CM tools like Visual
> > Source Safe or Clearcase from Rational.  While these tools do an adequate
> > job they don’t fit into the vision I have for a PAL.
> >
> > What I want is a thin-client interface (browser based) that will allow the
> > user to get the latest copy of a document for use or Check it out, in the
> > CM
> > sense, to update and Check it back in.  The Check-out and Check-in actions
> > need to be controlled as they typically are via a CM tool.  The artifact
> > attributes will be stored in a database (MySQL) while the documents will be
> > controlled in the CM tool.  The thin-client will allow the users to find
> > the
> > artifacts via search criteria they will select via dropdown list boxes show
> > the various artifact attributes.
>
> There seems like the issues at hand are twofold: one, being a
> content-management-system (or document managment) and two being source
> management.
>
> For the first issue, perhaps this would help:
> http://www.devshed.com/Server_Side/PHP/Cracking/
>
> Also, a google for any of the terms, PHP, document management, project
> management, etc. will return results.  A similar browse and search at
> http://sf.net would be useful as well, and, at a minimum, there's always the
> nuke family of products (http://postnuke.org and http://phpnuke.org).  I
> would recommend, however, that you search a bit more, and find something
> that's more in line.
>
> > What I’m looking for is any information on interfacing to a CM tool, CM
> > tools,  or better yet a CM tool that readily connects to a browser via PHP.
>
> The defacto source code control system is CVS, http://cvshome.org.  There are
> both graphical and client-side GUI interfaces available for it, most of which
> are outlined at the aforementioned site or quickly retreivable via a google
> search (http://cvs.php.net uses such a tool, which would be customizable, I
> believe).
>
> > While I develop everything on Linux/Apache for the  web-server, I could be
> > convinced to use IIS (the pain) if that is necessary.  Actually some
> > clients may need an IIS solution so that is not totally out of the picture.
>
> Most everything in the PHP world will be written for Apache first, with other
> server platforms support as an afterthought.  A word of caution for IIS,
> however: it's a multithreaded environment, and while modern PHP versions
> support it, many extensions and the libraries they implement do not.  If you
> want rocksolid, go Apache 1.3.27 and mod_php - bulletproof.
>
> H
>
>
> >
> > Even giving me hint of where to start looking would be appreciated.
> >
> >
> >
> > Thanks,
> >
> > Rudy
> >
> >
> >
> >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.480 / Virus Database: 276 - Release Date: 5/12/03
> >
> >
> >
> >
> >
> >
>
>
>
> --- Unsubscribe at http://nyphp.org/list/ ---
>
>