[Zope3-dev] Re: Some thoughts on Zope 3, Zope 3 applications, and Zope 3 instances
snip / As a non-developer observer, I'm +1 with Jim's discussion. Martin, you're right that developer influx should be the key goal, and that (a) simpler entry points like Grok and (b) killer apps are the way to get to that goal. and I think things like grok are the natural progression from drink our koolaid to use our koolaid mix and make your own. I don't think the killer app, though, should be the responsibility of the Zope project. More bluntly, I don't think it's fair to tell the Zope 3 core team to do it: they are more interested in machinery, they don't need to do it for their jobs, and are already giving us plenty. Let's decrease the responsibilities of the core. (Note: 3 years ago I lobbied heavily for the Zope 3 to keep the TTW dream alive, but my thinking was flawed.) everything has it place, scope creep on perfectly good ideas causes the pain. for example: the acceptance of the ZODB *would* benefit greatly from some type of database browser; such an application would not need to be a full blown application server. -w ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Grok sprint 2 reports
Hi there, We had a Grok sprint in Germany over the weekend, and we got two reports about it: Jan-Wijbrand's report: http://jw.n--tree.net/blog/dev/python/second-grok-sprint And mine: http://faassen.n--tree.net/blog/view/weblog/2007/01/09/0 Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Grok sprint 2 reports
Martijn Faassen wrote: Hi there, We had a Grok sprint in Germany over the weekend, and we got two reports about it: Rock on :) What is the current state of the art in terms of Grok examples and documentation? What is the best place to look to find out about the latest development techniques and possiiblities? Martin ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Grok sprint 2 reports
Martin Aspeli wrote: Martijn Faassen wrote: We had a Grok sprint in Germany over the weekend, and we got two reports about it: Rock on :) What is the current state of the art in terms of Grok examples and documentation? What is the best place to look to find out about the latest development techniques and possiiblities? Currently we suck at examples and documentation. We have some partially out of date design notes in 'doc'. We also have a lot of tests under src/grok/ftests and src/grok/tests which go into many situations, but those are not really good documentation by themselves as we spend a huge amount of time worrying about potential failure situations and doing good error reporting. The best examples right now are still the grokwiki and the grokblog, also to be found in the checkout. They haven't started using the changes of the very latest sprint yet, so no catalog or security yet, but grokblog uses quite a few features nonetheless, including forms. The good news is that documentation is one of our highest priorities now that we're nearing feature completeness. Feedback would of course be very welcome, either on this list or on grok-dev. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Grok sprint 2 reports
Martin Aspeli wrote: Martijn Faassen wrote: Hi there, We had a Grok sprint in Germany over the weekend, and we got two reports about it: Rock on :) What is the current state of the art in terms of Grok examples and documentation? What is the best place to look to find out about the latest development techniques and possiiblities? Philipp has posted a blog entry with a good example of Grok code: http://www.z3lab.org/sections/blogs/philipp-weitershausen/2007_01_09_you-thought-zope-3-wasn Thanks Philipp! Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Grok sprint 2 reports
Martijn Faassen wrote: Martin Aspeli wrote: Martijn Faassen wrote: Hi there, We had a Grok sprint in Germany over the weekend, and we got two reports about it: Rock on :) What is the current state of the art in terms of Grok examples and documentation? What is the best place to look to find out about the latest development techniques and possiiblities? Philipp has posted a blog entry with a good example of Grok code: http://www.z3lab.org/sections/blogs/philipp-weitershausen/2007_01_09_you-thought-zope-3-wasn That looks really promising, looking forward to get more impressions from Phillip at the snowsprint. Jürgen ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Grok sprint 2 reports
Philipp has posted a blog entry with a good example of Grok code: http://www.z3lab.org/sections/blogs/philipp-weitershausen/2007_01_09_you-thought-zope-3-wasn Gorgeous! I especially like that you don't have to manually define the template since it's picked up automatically by name. Will the grok effort yield any codegenerating scripts and stuff like the django folks have? If not, I have some ideas that I could maybe contribute with at/for the next sprint even :) -- Peter Bengtsson, work www.fry-it.com home www.peterbe.com hobby www.issuetrackerproduct.com ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Grok sprint 2 reports
Peter Bengtsson wrote: Philipp has posted a blog entry with a good example of Grok code: http://www.z3lab.org/sections/blogs/philipp-weitershausen/2007_01_09_you-thought-zope-3-wasn Gorgeous! I especially like that you don't have to manually define the template since it's picked up automatically by name. Will the grok effort yield any codegenerating scripts and stuff like the django folks have? If not, I have some ideas that I could maybe contribute with at/for the next sprint even :) Code generation sucks. :) But: - ArchGenXML (hacky though it is) is great for business types because it takes UML (which business analysts understand and customers can be talked through) and produces content types they can CRUD with. Seriously, I've seen people sell big Plone jobs on AGX (kinda scary). - Don't invent a new code generator. Please. :) PasteScript does quite well, and seems to be adopted by others, e.g. Pylons. We already use it to make new egg-like packages for Plone. - You should never, ever *need* code generation. It should be a nice way of getting a common structure for second-order stuff like documentation files and egg metadata (how we use ZopeSkel/paster in Plone), or a way of going from a visual representation to code. Systems that *depend* on generators are always nasty to maintain, upgrade and understand. Tools are just not a replacement for good language design (this is why we see the Java-Rails exodus cliche, and then people realise Rails has tools too, oh well). Martin ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Builbot mail not working ?
Baiju M wrote:
Hi, Can anyone verify that buildbot [1] send test failure error mails
to list? There is one test failure in Zope 3 trunk now [2]. But it's
not in Zope3-dev list archive [3].
[1] http://buildbot.zope.org [2]
http://buildbot.zope.org/Zope3%20trunk%202.4%20Linux%20zc-buildbot/builds/832/test_2/0
[3] http://mail.zope.org/pipermail/zope3-dev/
I am still getting this error in trunk, see the traceback:
Failure in test
/var/tmp/zopy/pkgs/Zope3trunk/src/zope/app/ftests/doctest.txt
Failed doctest test for doctest.txt
File /var/tmp/zopy/pkgs/Zope3trunk/src/zope/app/ftests/doctest.txt,
line 0
--
File /var/tmp/zopy/pkgs/Zope3trunk/src/zope/app/ftests/doctest.txt,
line 20, in doctest.txt
Failed example:
print http(r
GET /@@contents.html HTTP/1.1
)
Differences (ndiff with -expected +actual):
HTTP/1.1 401 Unauthorized
+ Cache-Control: no-store, no-cache, must-revalidate
- Content-Length: ...
? ^^^
+ Content-Length: 3987
?
Content-Type: text/html;charset=utf-8
+ Expires: Mon, 26 Jul 1997 05:00:00 GMT
+ Pragma: no-cache
WWW-Authenticate: basic realm=Zope
BLANKLINE
- !DOCTYPE html PUBLIC ...
+ !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
+ BLANKLINE
+ html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en
+ lang=en
+ BLANKLINE
+ head
+ titleZ3: /title
+ BLANKLINE
+ style type=text/css media=all@import
url(http://localhost/@@/zope3_tablelayout.css);/style
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ meta http-equiv=Content-Type
content=text/html;charset=utf-8 /
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ !-- Basic zope3 javascript's --
+ script type=text/javascript
+ src=http://localhost/@@/zope3.js;
+ /script
+ BLANKLINE
+ BLANKLINE
+ !-- Ugly is better than lobotomized. --
+ script type=text/javascript
+ src=http://localhost/@@/xmltree.js;
+ /script
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ link rel=icon type=image/png
+ href=http://localhost/@@/favicon.png; /
+ /head
+ BLANKLINE
+ body onload=loadtree('http://localhost/', 'http://localhost/');
+ table id=layout border=0 cellspacing=0 cellpadding=0
+ tr
+ td colspan=2 id=top
+ BLANKLINE
+ div id=global
+ div id=userDetails
+ BLANKLINE
+ User:
+ Unauthenticated User
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ a
href=@@login.html?nextURL=http%3A//localhost/%40%40contents.html[Login]/a
+ BLANKLINE
+ BLANKLINE
+ /div
+ BLANKLINE
+ a
+ href=http://localhost/@@SelectedManagementView.html;
+ name=topimg src=http://localhost/@@/zope3logo.gif; //a
+ BLANKLINE
+ /div
+ BLANKLINE
+ /td
+ /tr
+ tr
+ td colspan=2
+ BLANKLINE
+ div id=breadcrumbs
+ Location:nbsp;a
+ href=http://localhost/@@SelectedManagementView.html;[top]/a
+ /
+ /div
+ BLANKLINE
+ /td
+ /tr
+ tr
+ td id=navigation
+ BLANKLINE
+ div id=navigators
+ !-- Navigation tree box --
+ BLANKLINE
+ !-- Ugly is better than lobotomized. --
+ div class=box id=navigationTree
+ h4Navigation/h4
+ div xmlns=http://www.zope.org/zope3xmltree;
+ id=navtreecontents class=body
+ onclick=treeclicked(event);Loading.../div
+ /div
+ BLANKLINE
+ BLANKLINE
+ /div
+ BLANKLINE
+ /td
+ td id=content
+ div id=workspace
+ BLANKLINE
+ BLANKLINE
+ !-- OnlineHelp with popup support --
+ !-- note, we reverse the actions list 'cos
they're packed to the
+ screen from the right --
+ BLANKLINE
+ BLANKLINE
+ div id=viewspace
+ div id=message
+ /div
+ div id=body
+ div
+ BLANKLINE
+ h1Unauthorized/h1
+ BLANKLINE
+ pYou are not authorized/p
+ BLANKLINE
+ /div
+
