← Back to team overview

hkcr-dev team mailing list archive

[Branch ~hkcr-dev/hkcr/hkcr] Rev 63: Added the hkcr buildout.cfg - this file will need to be used to replace the standard buildout.cfg...

 

------------------------------------------------------------
revno: 63
committer: Timothy W. Cook <timothywayne.cook@xxxxxxxxx>
branch nick: hkcr
timestamp: Thu 2011-05-19 13:41:28 -0500
message:
  Added the hkcr buildout.cfg - this file will need to be used to replace the standard buildout.cfg file
added:
  hkcr.buildout.cfg
modified:
  hkcr.cddfile/hkcr.cddfile.egg-info/PKG-INFO
  hkcr.cddfile/hkcr.cddfile.egg-info/SOURCES.txt
  hkcr.cddfile/hkcr.cddfile.egg-info/requires.txt
  hkcr.cddfile/setup.py


--
lp:hkcr
https://code.launchpad.net/~hkcr-dev/hkcr/hkcr

Your team Healthcare Knowledge Component Repository Application Development Team is subscribed to branch lp:hkcr.
To unsubscribe from this branch go to https://code.launchpad.net/~hkcr-dev/hkcr/hkcr/+edit-subscription
=== added file 'hkcr.buildout.cfg'
--- hkcr.buildout.cfg	1970-01-01 00:00:00 +0000
+++ hkcr.buildout.cfg	2011-05-19 18:41:28 +0000
@@ -0,0 +1,199 @@
+############################################
+#
+# Buildout Configuration File for Standalone Plone
+# ------------------------------------------------
+# $LastChangedDate: 2011-04-10 09:34:13 -0700 (Sun, 10 Apr 2011) $ $LastChangedRevision: 47921M $
+#
+# After making changes in this configuration file,
+# you should run bin/buildout to update the components.
+# 
+# ALWAYS back up all Plone/Zope data and components
+# before changing configuration.
+# 
+# Running "bin/buildout" will update your installation,
+# installing missing components as necessary.
+# 
+# Use "bin/buildout -n" to update many components here to the newest
+# available releases.
+# This will update the add-on products you've added in the eggs= lines.
+# This will not, however, upgrade Plone itself (or anything else you've
+# pinned with a version specification). To upgrade Plone itself, see the
+# comments in "Plone Component Versions".
+#
+# Tutorial instructions for using zc.buildout for
+# configuration management are available at:
+# http://plone.org/documentation/tutorial/buildout
+# Full details at http://pypi.python.org/pypi/zc.buildout
+#
+############################################
+
+
+[buildout]
+
+############################################
+# Plone Component Versions
+# ------------------------
+# This version of the Unified Installer has the components of Plone 4 
+# preloaded so that it can install without an Internet connection.
+# If you want to update, uncomment the "http://..."; line below,
+# edit it to point to the current version URL, comment out the 
+# "versions.cfg" line and run "bin/buildout" while attached to the 
+# Internet. Generally, you only want to do that as part of a planned migration.
+# Note that if you are updating components, you should also check the versions
+# section at the end of this file, since recipes or components other than
+# those of Zope and Plone may need updating at the same time.
+#
+extends = 
+    base.cfg
+    versions.cfg
+#    http://dist.plone.org/release/4.0-latest/versions.cfg
+
+
+############################################
+# Ports
+# -----
+# Specify the port on which your Zope installation
+# will listen:
+http-address = 8080
+
+
+# If you try to start Zope as root, it will change user id to run as
+# the effective user specified here. This user id must own the var directory
+# of your buildout.
+effective-user = tim
+
+
+############################################
+# Eggs
+# ----
+# Add an indented line to the eggs section for any Python
+# eggs or packages you wish to include.
+#
+eggs =
+    Plone
+    PIL==1.1.6
+    hkcr.theme
+    hkcr.cddfile
+    
+# Optional Functionality
+# ----------------------
+# Uncomment the indented lines to include these add-on products.
+# Documentation on all of them, along with many more products,
+# is available at
+# http://plone.org/products/
+#
+# Example products:
+# * LinguaPlone provides tools for building multi-lingual sites
+# * PloneFormGen provides through-the-web form building
+#
+#    Products.LinguaPlone==4.0.1
+#    Products.PloneFormGen==1.6.0
+#
+# Note that versions may be specified here or in the [versions]
+# section below. You should always specify versions that you know
+# are compatible with the Plone release and at an acceptable
+# development level.
+#
+# Commonly used development tools:
+# Several excellent development tools are included in the develop.cfg
+# buildout extension. Read it to learn how to activate these tools.
+
+    
+############################################
+# ZCML Slugs
+# ----------
+# Some eggs need ZCML slugs to tell Zope to
+# use them. This is increasingly rare.
+zcml =
+#    plone.reload
+     
+############################################
+# Development Eggs
+# ----------------
+# You can use paster to create "development eggs" to
+# develop new products/themes. Put these in the src/
+# directory.
+# You will also need to add the egg names in the
+# eggs section above, and may also need to add them
+# to the zcml section.
+#
+# Provide the *paths* to the eggs you are developing here:
+develop =
+#    src/my.package
+     src/hkcr/hkcr.theme
+     src/hkcr/hkcr.cddfile
+     
+############################################
+# Debug Mode
+# ----------
+# Change debug-mode to "on" to run in development mode.
+# This will dramatically slow Plone.
+# 
+debug-mode = off
+# Add-on developers should turn deprecation warnings on
+deprecation-warnings = off
+# change verbose-security to "on" for useful security errors while developing
+verbose-security = off
+
+
+############################################
+# Backup Directory
+# ----------------
+# Sets the target directory for the bin/backup and bin/snapshotbackup
+# commands. Default is inside this project's var directory, but ideally
+# this should be on a separate volume or backup server.
+# 
+backups-dir=${buildout:directory}/var
+
+
+############################################
+# Initial User
+# ------------
+# This is the user id and password that will be used to create the initial 
+# user id that will allow you to log in and create a Plone site. This only
+# sets the initial password; it will not allow you to change an already 
+# existing password. If you change the admin password via the web interface,
+# the one below will no longer be valid.
+# If you find yourself locked out of your Zope/Python installation, you may
+# add an emergency user via "bin/plonectl adduser".
+user=admin:aoJUwB3C
+
+
+############################################
+# Parts Specification
+#--------------------
+# Specifies the components that should be included in the buildout.
+# All the basics are in the base.cfg extension; you may add your
+# own if you need them at the end of this file.
+parts =
+    instance
+    zopepy
+    zopeskel
+    unifiedinstaller
+    chown
+
+
+############################################
+# Versions Specification
+# ----------------------
+# Version information supplied here will "pin" Python packages to a particular
+# version number, even when you use the "newest" flag running buildout.
+# Specifying versions for all packages is a good idea and can prevent
+# accidental changes when you add new packages to your buildout.
+# Note that versions specified here will override those specified earlier
+# in the configuration, including those from the Plone and Zope version
+# config files.
+#
+[versions] 
+Cheetah = 2.2.1
+Paste = 1.7.5.1
+PasteScript = 1.7.3
+ZopeSkel = 2.19
+collective.recipe.backup = 1.7
+plone.recipe.command = 1.1
+plone.recipe.osxcontroller = 0.4
+plone.recipe.unifiedinstaller = 4.0rc1
+
+#Required by:
+#PasteScript 1.7.3
+PasteDeploy = 1.3.4

=== modified file 'hkcr.cddfile/hkcr.cddfile.egg-info/PKG-INFO'
--- hkcr.cddfile/hkcr.cddfile.egg-info/PKG-INFO	2011-05-19 17:36:03 +0000
+++ hkcr.cddfile/hkcr.cddfile.egg-info/PKG-INFO	2011-05-19 18:41:28 +0000
@@ -3,8 +3,8 @@
 Version: 2.2.0
 Summary: UNKNOWN
 Home-page: http://svn.plone.org/svn/collective/
-Author: UNKNOWN
-Author-email: UNKNOWN
+Author: Timothy W. Cook
+Author-email: timothywayne.cook@xxxxxxxxx
 License: GPL
 Description: .. contents::
         
@@ -89,6 +89,129 @@
             >>> browser.open(portal_url)
         
         -*- extra stuff goes here -*-
+        The CDD File content type
+        ===============================
+        
+        In this section we are tesing the CDD File content type by performing
+        basic operations like adding, updadating and deleting CDD File content
+        items.
+        
+        Adding a new CDD File content item
+        --------------------------------
+        
+        We use the 'Add new' menu to add a new content item.
+        
+            >>> browser.getLink('Add new').click()
+        
+        Then we select the type of item we want to add. In this case we select
+        'CDD File' and click the 'Add' button to get to the add form.
+        
+            >>> browser.getControl('CDD File').click()
+            >>> browser.getControl(name='form.button.Add').click()
+            >>> 'CDD File' in browser.contents
+            True
+        
+        Now we fill the form and submit it.
+        
+            >>> browser.getControl(name='title').value = 'CDD File Sample'
+            >>> browser.getControl('Save').click()
+            >>> 'Changes saved' in browser.contents
+            True
+        
+        And we are done! We added a new 'CDD File' content item to the portal.
+        
+        Updating an existing CDD File content item
+        ---------------------------------------
+        
+        Let's click on the 'edit' tab and update the object attribute values.
+        
+            >>> browser.getLink('Edit').click()
+            >>> browser.getControl(name='title').value = 'New CDD File Sample'
+            >>> browser.getControl('Save').click()
+        
+        We check that the changes were applied.
+        
+            >>> 'Changes saved' in browser.contents
+            True
+            >>> 'New CDD File Sample' in browser.contents
+            True
+        
+        Removing a/an CDD File content item
+        --------------------------------
+        
+        If we go to the home page, we can see a tab with the 'New CDD File
+        Sample' title in the global navigation tabs.
+        
+            >>> browser.open(portal_url)
+            >>> 'New CDD File Sample' in browser.contents
+            True
+        
+        Now we are going to delete the 'New CDD File Sample' object. First we
+        go to the contents tab and select the 'New CDD File Sample' for
+        deletion.
+        
+            >>> browser.getLink('Contents').click()
+            >>> browser.getControl('New CDD File Sample').click()
+        
+        We click on the 'Delete' button.
+        
+            >>> browser.getControl('Delete').click()
+            >>> 'Item(s) deleted' in browser.contents
+            True
+        
+        So, if we go back to the home page, there is no longer a 'New CDD File
+        Sample' tab.
+        
+            >>> browser.open(portal_url)
+            >>> 'New CDD File Sample' in browser.contents
+            False
+        
+        Adding a new CDD File content item as contributor
+        ------------------------------------------------
+        
+        Not only site managers are allowed to add CDD File content items, but
+        also site contributors.
+        
+        Let's logout and then login as 'contributor', a portal member that has the
+        contributor role assigned.
+        
+            >>> browser.getLink('Log out').click()
+            >>> browser.open(portal_url + '/login_form')
+            >>> browser.getControl(name='__ac_name').value = 'contributor'
+            >>> browser.getControl(name='__ac_password').value = default_password
+            >>> browser.getControl(name='submit').click()
+            >>> browser.open(portal_url)
+        
+        We use the 'Add new' menu to add a new content item.
+        
+            >>> browser.getLink('Add new').click()
+        
+        We select 'CDD File' and click the 'Add' button to get to the add form.
+        
+            >>> browser.getControl('CDD File').click()
+            >>> browser.getControl(name='form.button.Add').click()
+            >>> 'CDD File' in browser.contents
+            True
+        
+        Now we fill the form and submit it.
+        
+            >>> browser.getControl(name='title').value = 'CDD File Sample'
+            >>> browser.getControl('Save').click()
+            >>> 'Changes saved' in browser.contents
+            True
+        
+        Done! We added a new CDD File content item logged in as contributor.
+        
+        Finally, let's login back as manager.
+        
+            >>> browser.getLink('Log out').click()
+            >>> browser.open(portal_url + '/login_form')
+            >>> browser.getControl(name='__ac_name').value = portal_owner
+            >>> browser.getControl(name='__ac_password').value = default_password
+            >>> browser.getControl(name='submit').click()
+            >>> browser.open(portal_url)
+        
+        
         
         
         Contributors
@@ -100,6 +223,7 @@
         Download
         ********
         
+Keywords: MLHIM
 Platform: UNKNOWN
 Classifier: Framework :: Plone
 Classifier: Intended Audience :: Developers

=== modified file 'hkcr.cddfile/hkcr.cddfile.egg-info/SOURCES.txt'
--- hkcr.cddfile/hkcr.cddfile.egg-info/SOURCES.txt	2011-05-19 17:36:03 +0000
+++ hkcr.cddfile/hkcr.cddfile.egg-info/SOURCES.txt	2011-05-19 18:41:28 +0000
@@ -19,14 +19,18 @@
 hkcr/cddfile/browser/__init__.py
 hkcr/cddfile/browser/configure.zcml
 hkcr/cddfile/content/__init__.py
+hkcr/cddfile/content/cddfile.py
 hkcr/cddfile/content/configure.zcml
 hkcr/cddfile/interfaces/__init__.py
+hkcr/cddfile/interfaces/cddfile.py
 hkcr/cddfile/portlets/__init__.py
 hkcr/cddfile/portlets/configure.zcml
 hkcr/cddfile/profiles/default/factorytool.xml
 hkcr/cddfile/profiles/default/metadata.xml
 hkcr/cddfile/profiles/default/portlets.xml
+hkcr/cddfile/profiles/default/rolemap.xml
 hkcr/cddfile/profiles/default/types.xml
+hkcr/cddfile/profiles/default/types/CDD_File.xml
 hkcr/cddfile/tests/__init__.py
 hkcr/cddfile/tests/base.py
 hkcr/cddfile/tests/test_doctest.py
\ No newline at end of file

=== modified file 'hkcr.cddfile/hkcr.cddfile.egg-info/requires.txt'
--- hkcr.cddfile/hkcr.cddfile.egg-info/requires.txt	2011-05-19 17:36:03 +0000
+++ hkcr.cddfile/hkcr.cddfile.egg-info/requires.txt	2011-05-19 18:41:28 +0000
@@ -1,4 +1,5 @@
 setuptools
+mekk.xmind
 
 [tests]
 zope.testing
\ No newline at end of file

=== modified file 'hkcr.cddfile/setup.py'
--- hkcr.cddfile/setup.py	2011-05-19 17:36:03 +0000
+++ hkcr.cddfile/setup.py	2011-05-19 18:41:28 +0000
@@ -45,9 +45,9 @@
         'Intended Audience :: Developers',
         'License :: OSI Approved :: GNU General Public License (GPL)',
         ],
-      keywords='',
-      author='',
-      author_email='',
+      keywords='MLHIM',
+      author='Timothy W. Cook',
+      author_email='timothywayne.cook@xxxxxxxxx',
       url='http://svn.plone.org/svn/collective/',
       license='GPL',
       packages=find_packages(exclude=['ez_setup']),
@@ -56,6 +56,7 @@
       zip_safe=False,
       install_requires=['setuptools',
                         # -*- Extra requirements: -*-
+                        'mekk.xmind',
                         ],
       tests_require=tests_require,
       extras_require=dict(tests=tests_require),