instead of instanciating Document classes on the fly


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42913 20353a03-c40f-0410-a6d1-a30d3c3de9de

enabled, remove expectedFailure


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42912 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42911 20353a03-c40f-0410-a6d1-a30d3c3de9de

created. Move the test up, before accessor creation.

The accessor holder name is also BaseCategory instead of "Base Category".

After this, we should get back all related category accessors.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42910 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42909 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42908 20353a03-c40f-0410-a6d1-a30d3c3de9de

This code is a contribution from Gabriel Lima (NSI/IFF/Campos).



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42907 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42906 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42905 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42904 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42903 20353a03-c40f-0410-a6d1-a30d3c3de9de

After this, all ERP5 objects become instances of portal type classes

Preferences:
* all the trickery for preferences is gone and is handled by a specific
  accessor holder holding all preference methods

Property holders
* our Base.aq_portal_type property holders are not used anymore:
  the "property holder" becomes the portal type class itself and the
  set of accessor_holder classes in the mro of the portal type class:
  portal-type-specific methods are on the portal type class, while
  portal-type-independant method are put on the accessor holder ancestors
* the portal type meta class now also inherits from "PropertyHolder" to
  provide the same introspection interface and methods.
  (In the future this class / interface will need to be refined)

Bootstrap/migration:
* bootstrapping/migration from older instances: provide with code able to
  import XML from ERP5/bootstrap/ to load necessary tools from almost any
  instance state
* migrate in BusinessTemplate installation code all non-portal type classes
  objects to portal type classes
* Change the way Tools are installed when creating a site, so that we create
  directly portal type classes objects instead of Documents

Accessors:
* add a generatePortalTypeAccessors method on the portal type class to generate
  portal-type-specific accessors
* associate BaseAccessorHolder to all portal type classes to contain
  all common category related accessors
* change the way workflow methods are generated to bind them directly on
  the portal type class
* disable Base._aq_dynamic (while still keeping its code for debugging and
  reference, this can be cleanup up later)


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42902 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42901 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42900 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42899 20353a03-c40f-0410-a6d1-a30d3c3de9de

Just forget about it, and retry later.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42898 20353a03-c40f-0410-a6d1-a30d3c3de9de

It means that we cant access the Legacy module anymore,
so for now we hardcode this default_large_image_height value


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42897 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42896 20353a03-c40f-0410-a6d1-a30d3c3de9de

- add search box
- refactor code to save and load notes of events in description field. This change is to use SearchableText search in event module

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42895 20353a03-c40f-0410-a6d1-a30d3c3de9de

Will be dropped as soon as cloudooo will support this conversion.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42894 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42893 20353a03-c40f-0410-a6d1-a30d3c3de9de

issue as _getDefaultAcquiredProperty() already takes care of such case
as per r42852 (consistent with its default value in parameters) and
getContentPortalType() would fail anyway if no portal type is given


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42892 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42891 20353a03-c40f-0410-a6d1-a30d3c3de9de

* improve css

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42888 20353a03-c40f-0410-a6d1-a30d3c3de9de

- move button to create new event to your_calendar_box
- remove not used field

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42887 20353a03-c40f-0410-a6d1-a30d3c3de9de

With MyISAM full text catalog bt5 we need to use deferred connection only for catalog / uncatalog methods.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42886 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42885 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42884 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42883 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42882 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42881 20353a03-c40f-0410-a6d1-a30d3c3de9de

extend code to make possible add fields on edit dialog. This patch was send to wdcalendar developers

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42880 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42879 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42878 20353a03-c40f-0410-a6d1-a30d3c3de9de

I need some way to distinguish what happens when, later, an automatic migration
happens, or when a Tool is not found: if this happens in a "normal" context,
then logging should be very loud and verbose, as this is likely to crash your
site.
On the other hand, during bootstrap/setup, this is perfectly normal to miss
some tools/modules, and we should not worry/log about it, or the NECESSARY
logs will be quickly removed by developers tired of seeing "useless" logs...

Better ideas that can work in a fresh site without workflows, portal types,
or any advanced mechanism? I'm all ears.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42877 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42876 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42872 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42870 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42869 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42868 20353a03-c40f-0410-a6d1-a30d3c3de9de