[Framework-Team] Re: Names, names and we need a decision

[Hanno Schlichting]

Hi.

As I'm lazy, I wrote a new template for plone.app projects now as well.

So in step 3 you can also do:

paster create -t plone_app

which will ask you the same question as the plone_core template but adds 
a question for the second namespace, which defaults to app :)

Step 4 (svn import) doesn't change, as plone.app.example projects should 
also live in the Plone SVN top level directory.

Hanno

Daniel Nouri wrote:
> Martin Aspeli wrote:
>> Daniel Nouri wrote:
>>> whit wrote:
>>>> Martin Aspeli wrote:
>>>>> Hi Hanno,
>>>>>
>>>>> I'm happy to write the plone / plone.app announcement, and I can 
>>>>> write the bit about guidelines for when to use them. However, I'm 
>>>>> not too sure how we do the svn organisation.
>>>>>
>>>>>  - are we recommending people use ZopeSkel?
>>>> cautious but enthusiastic non-fwt +1 here?  I'm hoping now that topp 
>>>> has Ian Bicking aboard we may have a chance of getting some expert 
>>>> cycles to resolve the skeletor/paste/zc.buildout/instancemanager 
>>>> overlap. but for creating basic stub skeletons ZopeSkel seems like 
>>>> the simplest starting point though.  I need to look at it again 
>>>> though; would we also need a ploneskel?
>>>
>>> ZopeSkel is an easily extensible *collection* of skeletons for Zope 
>>> projects (Plone projects included).  It has currently two skeletons 
>>> for Plone, the plone_core and the plone2_theme (=DIYPloneStyle) 
>>> skeleton. Get the latest SVN version
>>>
>>>     easy_install ZopeSkel==dev
>>>
>>> and look at the list of templates
>>>
>>>     paster create --list-templates
>>>
>>> and
>>>
>>>     paster create --help
>>>
>>> Ian looked at it and he had some suggestions (like putting docs like 
>>> INSTALL.txt etc. into a top-level doc/ directory instead of in the 
>>> package itself).  ZopeSkel has a very small and clear goal. 
>>> instancemanager and zc.buildout do something completely different, 
>>> and skeletor is in between.
>>
>> Do we have (or could we create) some very 
>> for-new-developers-and-optilude documentation on how exactly people 
>> install this, run this, and then get it into svn in the right way?
>>
>> We need to be able to point people at that before we can tell them to 
>> use that package structure. I'd rather say "use this tool's structure" 
>> rather than describe a structure in detail, though!
> 
> I'll write a short how to.  In the meantime, feel free to give it a try:
> 
> 1) Install EasyInstall: 
> http://peak.telecommunity.com/DevCenter/EasyInstall#installing-easy-install
> 
> 2) Install ZopeSkel: easy_install ZopeSkel==dev
> 
> 3) In the directory in which you want to create your new project, do: 
> paster create -t plone_core
> 
> This will ask you a few questions, amongst others, what's your namespace 
> package (-> 'plone'), and what's your package name (e.g. 'i18n').  After 
> that you'll have a directory called ${project}
> 
> 4) svn import -- ${project} goes into a toplevel directory next to other 
> projects with the same namespace package, e.g. plone.form and plone.i18n 
> live in the same directory -- which should be the Plone SVN top level 
> directory.
> 
> 5) Realize that it's really easy ;-)
> 
> 6) Read http://peak.telecommunity.com/DevCenter/setuptools to learn what 
> setuptools is about.  Look at #development-mode in particular.
> 
> I need to clean up the templates a bit before the 0.2 release.  I also 
> want to add a tests.py in which you can uncomment and test away.  We can 
> also create a less generic template (like the existing plone2_theme) 
> that has more files to start with in it.  Suggestions, please!
> 
> Important note: If you want to use your project as a Zope 2 Product, 
> you'll have use Rocky's pythonproducts.  If you answer the question "Do 
> you want a Zope 2 product" with Yes, it'll create the required zcml and 
> installation instructions for you.  Why pythonproducts?  Because eggs 
> and Products/ don't go together.
> 
> Cheers
> Daniel
> 
>