On Wednesday, November 9, 2011 11:13:02 PM UTC-5, mikech wrote:
+1 for this. I wasn't thinking about major edits, but we could see
whether the typos etc. had already been reported and not
crowd the group with repeats.
The online book is temporarily locked, but normally when a minor typo is
So can we assume that the typos we see there now, have not been reported?
Lots of typos have been fixed. Will post a book ed 3.3 shortly
On Nov 10, 11:19 am, mikech mp.ch...@gmail.com wrote:
So can we assume that the typos we see there now, have not been reported?
On Wednesday, November 9, 2011 1:58:56 AM UTC-5, viniciusban wrote:
I think only texts are sufficient.
We can send patches to Massimo (or somebody else) merge them in.
Without the book app, it's very difficult to see how your edits will look.
Not a big deal for minor edits, but difficult for
+1 for this. I wasn't thinking about major edits, but we could see whether
the typos etc. had already been reported and not
crowd the group with repeats.
another :p
and it is used internally by the *SQLFORM.gird *and SQLFORM.smartgrid.
Should be SQLFORM.grid instead of SQLFORM.gird
in http://web2py.com/book/default/chapter/06#smart_query-%28experimental%29
On Mon, Nov 7, 2011 at 5:54 PM, Anthony abasta...@gmail.com wrote:
FYI, I am not
I was wondering if there was any 'bug' tracking in relation to the
documentation. It might be a good idea to track the corrections, and
changes.
No but email me.
On Nov 8, 2011, at 6:54 PM, mikech wrote:
I was wondering if there was any 'bug' tracking in relation to the
documentation. It might be a good idea to track the corrections,
and changes.
Massimo,
what about putting the book text in a dvcs? (git, hg, etc.)
Wouldn't it simplify updates?
--
Vinicius Assef.
On Wed, Nov 9, 2011 at 1:15 AM, Massimo Di Pierro
massimo.dipie...@gmail.com wrote:
No but email me.
On Nov 8, 2011, at 6:54 PM, mikech wrote:
I was wondering if there was
On Tuesday, November 8, 2011 11:26:44 PM UTC-5, viniciusban wrote:
Massimo,
what about putting the book text in a dvcs? (git, hg, etc.)
Wouldn't it simplify updates?
Should include the whole book app -- otherwise it would be difficult to see
the results of edits made on your local machine.
I think only texts are sufficient.
We can send patches to Massimo (or somebody else) merge them in.
--
Vinicius Assef.
On Wed, Nov 9, 2011 at 4:36 AM, Anthony abasta...@gmail.com wrote:
On Tuesday, November 8, 2011 11:26:44 PM UTC-5, viniciusban wrote:
Massimo,
what about putting the book
On Wed, 9 Nov 2011 02:26:44 -0200
Vinicius Assef vinicius...@gmail.com
wrote:
Massimo,
what about putting the book text in a dvcs? (git, hg, etc.)
+1
Sincerely,
Gour
--
Those who are on this path are resolute in purpose,
and their aim is one. O beloved child of the Kurus,
the
Ok I'm reading thru that chapter, and forward. So I'll report what I find.
I'm going through the book in detail looking for typos, and trying to
absorb some more learnings at the same time. By all means go ahead,
but we may be doubling up in effort. May I suggest waiting for a
cleaned up Version 3.3 ? I hope it will only contain one or two
missed typos that may need
FYI, I am not specifically looking for typos, but I am adding a bunch of
material to the book and reviewing most of the newer material, so I'm
catching a lot of typos and errors as well. So, as Andrew says, most of the
typos and formatting issues will likely be resolved by the next release.
In the section Scheduler:
It provides a *standrad* mechanism for creating and scheduling tasks.
The first argument of the Scheduler class must be the database to be used
by the scheduler to communicate with the workers. This can be the db of the
app or another* dedictade* db,perhaps one
Thanks.
Massimo
On Nov 6, 2011, at 1:17 AM, mikech wrote:
In the section Scheduler:
It provides a standrad mechanism for creating and scheduling tasks.
The first argument of the Scheduler class must be the database to be used by
the scheduler to communicate with the workers. This can
I would be glad to help clean up the book if you need it. Otherwise I will
post the issues here.
Mike
Further down in the chapter on scheduler there are these paragraphs.
Once a task exists (there is a record in the scheduler_talk table), is
QUEUED, and is ready (*mmeets* all the conditions specified in the
record) it can be picked up by a worker. As soon as a worker is available
it picks the
One more thing:
As soon as a worker is available it picks the first ready task schduled to
run -
As soon as a worker is available it picks the first scheduled task that is
ready to run.
I am currently re-reading the book since version 3.2 came out, and
I'll probably do the same for 4.0. It's slowly sinking in.
I have also come across a number of typos too. Massimo, would you
like feedback on this, or can we make suggested changes and send them
through.
Andrew
On Nov 2,
yes please!
On Nov 1, 10:13 pm, Andrew awillima...@gmail.com wrote:
I am currently re-reading the book since version 3.2 came out, and
I'll probably do the same for 4.0. It's slowly sinking in.
I have also come across a number of typos too. Massimo, would you
like feedback on this, or can
22 matches
Mail list logo
