headers
John de la Garza | 4 Oct 23:45

sample app BookShelf

I got BookShelf from:  svn://svn.zope.org/repos/main/grokapps/BookShelf

It didn't have a bookstrap.py, so I put one in.  It had  
bootstrap.cfg.  I am new to buildouts, is this ok to do?

When I ran this:  python2.4 bootstrap.py

I got this:
----------------------------------------
Creating directory '/Users/john/sameple_grok/grokapps/BookShelf/bin'.
Creating directory '/Users/john/sameple_grok/grokapps/BookShelf/parts'.
Creating directory '/Users/john/sameple_grok/grokapps/BookShelf/ 
develop-eggs'.
Generated script '/Users/john/sameple_grok/grokapps/BookShelf/bin/ 
buildout'.
Develop: '/Users/john/sameple_grok/grokapps/BookShelf/.'
Develop: '/Users/john/sameple_grok/grokapps/BookShelf/.'
While:
   Installing.
   Getting section eggbasket.
Error: The referenced section, 'eggbasket', was not defined.
pb:~/sameple_grok/grokapps/BookShelf john$ ./
pb:~/sameple_grok/grokapps/BookShelf john$ svn infoPath: .
URL: svn://svn.zope.org/repos/main/grokapps/BookShelf
Repository Root: svn://svn.zope.org/repos/main
Repository UUID: 62d5b8a3-27da-0310-9561-8e5933582275
Revision: 91758
Node Kind: directory
Schedule: normal
Last Changed Author: philikon
(Continue reading)

Permalink | Reply | 0 comments |
headers
John de la Garza | 4 Oct 22:54

ZODB and storing, retrieving, deleting, use of ID

I'm making an app that has polls for voting... When I make a Poll  
object to I have to create an ID so I can find it again.  I'm comming  
froma RDBMS background and am wondering if there are any articles  
that would helpl me transistion.  For example should the ID be the  
last object id + 1?  I saw some sample code that kept the objects in  
a list then just got the length of the list, but if items are deleted  
then using the len as the ID could be trouble (not unique).... any  
feed back would be apprecitated.  I've read intro to ZODB (Jim  
Fulton) but it doesn't mention deleting
Permalink | Reply | 1 comment |
headers
John de la Garza | 4 Oct 19:21

adding objects to context from __init__

In the tutorial the first demo of persistent objects did this:

class Sample(grok.Application, grok.Container):
     text = 'default text'

Then as the tutorial goes on they do this:

class Sample(grok.Application, grok.Container):
     def __init__(self):
         super(Sample, self).__init__()
         self.list = []

Why don't we have to add the string the same way as the list?

I mean the variable text gets persisted between restarts of the  
server, but if we added a list by doing this:

class Sample(grok.Application, grok.Container):
     list = []

it would be reset to empty every time we restarted the server

I'd expect text='default text' to have the same resetting as list=[]

What am I over looking?
Permalink | Reply | 3 comments |
headers
Yvan Strahm | 1 Oct 13:41

broken link for tutorial

Hello All,

Just to let you know that I tried to download the pdf of the tutorial from this page:

http://grok.zope.org/doc/current/tutorial.html

and this link seems broken.

http://grok.zope.org/doc/current/tutorial.pdf

Cheers,

yvan
_______________________________________________
Grok-dev mailing list
Grok-dev <at> zope.org
http://mail.zope.org/mailman/listinfo/grok-dev
Permalink | Reply | 3 comments |
headers
johndela1 | 29 Sep 22:18

trying to get sample code


I'm trying to get the sample code at http://svn.zope.org/Grokstar/trunk/

What is the svn path must use to check this out?

I tried this:

john <at> lead:~/delme$ svn co http://svn.zope.org/Grokstar/trunk/
svn: PROPFIND request failed on '/Grokstar/trunk'
svn: PROPFIND of '/Grokstar/trunk': 301 Moved (http://svn.zope.org)

--

-- 
View this message in context: http://www.nabble.com/trying-to-get-sample-code-tp19730971p19730971.html
Sent from the Grok mailing list archive at Nabble.com.
Permalink | Reply | 2 comments |
headers
Jan-Wijbrand Kolman | 29 Sep 20:14

post-0.14-release notes

Hi,

We've just released Grok 0.14. In doing so, I noticed the following:

* grokproject didn't create projects that would require the grokui.admin
package. I added that to the template file for the project's setup.py file.

I bravely committed this change without really being able to run
grokproject's tests, as it is not possible to run the grokproject tests
with a yet-unreleased Grok version. Would it be possible to somehow be
able to run grokproject's test based on a unreleased version of Grok?

* This document:

http://grok.zope.org/project/meta/updating-the-official-grok-documentation-ogd

describes how to update the Grok documentation on the website. This is
great since I almost forgot to do it...

However, we might want to set the permissions/ownership of the doc
directory on grok.zope.org such that the releasemanager can easily run
the commands described in the document (I had to `sudo mkdir 0.14` and
`sudo remove current` and `sudo ln -s 0.14 current` to get things working).

regards,
jw

p.s. All the release documents are really paying off now... it is almost
a simple job now to do the release... :-)
Permalink | Reply | 5 comments |
headers
Martijn Faassen | 29 Sep 20:14

volunteer: update grok.zope.org to include references to python 2.5

Hi there,

Now that Grok 0.14 supports Python 2.5 officially, we should update
grok.zope.org to mention this. Besides this we should also update the
documentation in our 'doc' directory, such as the tutorial.

Be careful not to confuse the two - we have some documentation double
at the moment, but if it's in Grok's doc directory that is the place
to maintain it, not the CMS.

We have quite a few places where it says 'python2.4' in examples, and
these can be updated. We also probably warn against Python 2.5 in some
places - those warnings can go away.

Note that as developers we're going to support Python 2.4 and Python
2.5 for the forseeable future - we won't let Grok depend on Python 2.5
features yet for the forseeable future.

Regards,

Martijn
Permalink | Reply | 2 comments |
headers
Martijn Faassen | 29 Sep 20:05

Grok 0.14 released!

The Grok team is happy to announce the release of Grok 0.14!

This release is available on PyPI and a new index of specific versions
of packages used by this release has been frozen at
http://grok.zope.org/releaseinfo/grok-0.14.cfg. This means that new
projects created with grokproject will start using this release right
away.

This release is the first release of Grok that officially supports
Python 2.5 (besides Python 2.4 itself). The main focus of this release
has been a restructuring of Grok, spinning off packages that can now
be used independently in Zope 3 projects as well as in Zope 2 (through
five.grok):

   * Spin off of grokcore.view - support for views is now maintained
in this package.
   * Spin off of grokcore.security - support for security
declarations is now maintained here
   * Spin off of grokcore.formlib - support for zope.formlib based forms
   * Spin off of grokui.admin - the admin UI is now distributed
separately, but grokproject automatically will include it when you
create a new grok project.
   * the grok.Skin baseclass is now gone and has been simplified with
the grok.skin directive that can be placed on a layer instead.

To upgrade an existing project from 0.13 to 0.14 you have to:

   * include grokui.admin explicitly as a dependency in your setup.py
   * update the versions.cfg in your project with the version from
http://grok.zope.org/releaseinfo/grok-0.14.cfg
   * modify uses of grok.Skin to use the grok.skin directive

For the detailed changelog, see Grok's PyPI entry page.

For detailed upgrade notes, including how to change your application,
see http://grok.zope.org/project/upgrade-notes

For installation instructions and much more on how to use Grok, see
the Grok tutorial: http://grok.zope.org/documentation/book
We hope to hear from you!

If you enjoy Grok, please subscribe to the grok-dev mailing list and
join us in the #grok channel on irc.freenode.net.
Permalink | Reply | 2 comments |
headers
Michael Haubenwallner | 28 Sep 13:26

grokproject and paste support

I have put a new branch at
http://svn.zope.org/grokproject/branches/d2m-dual-startup/

It makes 'paster' the default grokproject server (but also lets you
create a project with the old layout through a '--zopectl' option).

Paster gets you a full WSGI environment, a 30-50% performance boost over
zopectl and the wonderful AJAX debugger.

Tests are added for both paster and zopectl setups.

I hope it can be merged into the trunk before the next release.

Michael

--

-- 
http://blog.d2m.at
http://planetzope.org
Permalink | Reply | 1 comment |
headers
Leonardo Rochael Almeida | 28 Sep 12:31

grok_release_url parameter branch

Hi,

I've made a small step in the direction of having grokproject work off
of a tarball instead of requiring Internet for it's operation. It's
sitting on a branch at:
svn://svn.zope.org/repos/main/grokproject/branches/rochael-alternate-grok_release_url

It just implements an optional paster variable that, if provided,
makes grokproject assume it as the location of the grok
release/version information (and eggbasket) files instead of the
canonical location. Tests were also added (and some previous broken
tests fixed).

Should I merge it to trunk?
Permalink | Reply | 1 comment |
headers
Lennart Regebro | 28 Sep 12:22

five.grok alpha anyone?

I've just made my first actual five.grok product, soon ready. I also
realized that it's a bit stupid to make it a five.grok product,
because it doesn't need to, it's very simple and should in fact
probably have been an external method so it could be used under Plone
2.0 and stuff. Ah well, can't be bothered to change that right now.

Anyway, for easy installation it would be good if five.grok gets an
egg. Do people feel happy about an alpha release of five.grok?

--

-- 
Lennart Regebro: Zope and Plone consulting.
http://www.colliberty.com/
+33 661 58 14 64
Permalink | Reply | 5 comments |

Gmane