On Thu, 2007-07-26 at 23:17 +0200, Philipp von Weitershausen wrote:
> On 18 Jul 2007, at 22:34 , Maciej Wisniowski wrote:
> >> I will add this to the zopeproject docs. I wonder:
> >>
> >> * Would it help if the 'myzopeapp' package would not be in the
> top-
> >> level MyZopeApp directory, but in a
On 18 Jul 2007, at 22:34 , Maciej Wisniowski wrote:
I will add this to the zopeproject docs. I wonder:
* Would it help if the 'myzopeapp' package would not be in the top-
level MyZopeApp directory, but in a 'src' directory below
MyZopeApp? Would that make it clearer where to go?
* grokproje
On Jul 19, 2007, at 6:46 PM, Philipp von Weitershausen wrote:
On 18 Jul 2007, at 19:25 , Kent Tenney wrote:
on my W2K machine
zopeproject MyZopeProject
fails because I don't have Visual Studio installed and it wants
to compile extensions for ZODB
Right. Something seems to depend on ZODB 3
On 18 Jul 2007, at 19:25 , Kent Tenney wrote:
on my W2K machine
zopeproject MyZopeProject
fails because I don't have Visual Studio installed and it wants
to compile extensions for ZODB
Right. Something seems to depend on ZODB 3.9.0-xyz now and we have no
binary for that (yet). Sadly enough
On 19 Jul 2007, at 22:35 , Lennart Regebro wrote:
On 7/19/07, Dieter Maurer <[EMAIL PROTECTED]> wrote:
But, Zope is quite easy on entry.
Zope2, yes.
Zope3? Not at all.
Will modularizing Zope 3 make it easier for newbies? Not really, but
with zopeproject or similar it shouldn't be more complic
On 19 Jul 2007, at 19:15 , Dieter Maurer wrote:
and toning down Zope for an easier entry.
But, Zope is quite easy on entry.
To some, probably many, it is easy. At first. Then they discover the
limits of TTW development and hit the wall of having to learn this
completely new and different
On 7/19/07, Dieter Maurer <[EMAIL PROTECTED]> wrote:
But, Zope is quite easy on entry.
Zope2, yes.
Zope3? Not at all.
Will modularizing Zope 3 make it easier for newbies? Not really, but
with zopeproject or similar it shouldn't be more complicated either.
In fact, the installation process migh
Philipp von Weitershausen wrote at 2007-7-18 22:59 +0200:
>On 18 Jul 2007, at 21:13 , Dieter Maurer wrote:
> ...
>> I prefer the standard approach:
>>
>> I see a framework -- Zope
>> and a large number of application components that plug themself
>> into the common framework.
>> The applica
On Wed, 2007-07-18 at 18:50 +0200, Philipp von Weitershausen wrote:
> * Would it help if the 'myzopeapp' package would not be in the top-
> level MyZopeApp directory, but in a 'src' directory below MyZopeApp?
> Would that make it clearer where to go?
+1
> * grokproject actually also creates a
On 7/18/07, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
I'm not going to try to convince anyone to give it up, but I probably
won't spend much energy in either promoting, maintaining and
documenting it.
Yay, Philipp!
-Fred
--
Fred L. Drake, Jr.
"Chaos is the score upon which re
On 18 Jul 2007, at 21:13 , Dieter Maurer wrote:
Philipp von Weitershausen wrote at 2007-7-18 01:13 +0200:
...
Imagine you're writing a GUI application. Without question you'd use
some sort of GUI toolkit (e.g. wxPython). Would you expect you would
have to hook into the the "wxPython application"
> I will add this to the zopeproject docs. I wonder:
>
> * Would it help if the 'myzopeapp' package would not be in the top-level
> MyZopeApp directory, but in a 'src' directory below MyZopeApp? Would
> that make it clearer where to go?
>
> * grokproject actually also creates a "hello world" brow
Philipp von Weitershausen wrote at 2007-7-18 01:13 +0200:
> ...
>Imagine you're writing a GUI application. Without question you'd use
>some sort of GUI toolkit (e.g. wxPython). Would you expect you would
>have to hook into the the "wxPython application" as a plug-in? Isn't it
>more natural that
On 18 Jul 2007, at 12:26 , Maciej Wisniowski wrote:
Maybe it is too fast for these questions but these are ones I had
just after trying zopeproject:
1. What should I do after creating project?
Where should I start writing my code? In one of folders created by
zopeproject or maybe I'm just su
On 18 Jul 2007, at 11:22 , Hermann Himmelbauer wrote:
- Please carefully weight boilerplate code against "black magic":
For newbies,
the generated code should on one hand be easily understandable,
which means
that there is no code in it that requires deep understandings of Zope3
internals. On
>
> Feedback
>
>
> As much as I see the library-driven approach replace the instance
> approach, I see zopeproject as the way to get started with an
> application instead of mkzopeinstance. I would like to ask everyone
> who's interested in checking it out and give feedback, both on these
Am Mittwoch, 18. Juli 2007 01:13 schrieb Philipp von Weitershausen:
> Feedback
>
>
> As much as I see the library-driven approach replace the instance
> approach, I see zopeproject as the way to get started with an
> application instead of mkzopeinstance. I would like to ask everyone
> who
For the past weeks I've been toying around with egg-based installs of
Zope and flexible WSGI-based deployment using PasteDeploy [1]. Both
essentially challenge the concept of instances as we know them.
What is an instance?
* Start/stop scripts for a pluggable application
18 matches
Mail list logo
