[book] minor update about windmill + reformat stable
authorJulien Jehannet <julien.jehannet@logilab.fr>
Fri, 16 Jul 2010 16:08:04 +0200
branchstable
changeset 6324 bdb85e3602c8
parent 6323 a11c1e3c16c3
child 6325 38cfda1ab60f
[book] minor update about windmill + reformat
doc/book/en/annexes/rql/language.rst
doc/book/en/devrepo/entityclasses/adapters.rst
doc/book/en/tutorials/tools/windmill.rst
--- a/doc/book/en/annexes/rql/language.rst	Fri Jul 30 16:01:28 2010 +0200
+++ b/doc/book/en/annexes/rql/language.rst	Fri Jul 16 16:08:04 2010 +0200
@@ -107,12 +107,13 @@
 Operators priority
 ``````````````````
 
-1. '*', '/'
-2. '+', '-'
-3. 'NOT'
-4. 'AND'
-5. 'OR'
-6. ','
+#. "(", ")"
+#. '*', '/'
+#. '+', '-'
+#. 'NOT'
+#. 'AND'
+#. 'OR'
+#. ','
 
 
 Search Query
--- a/doc/book/en/devrepo/entityclasses/adapters.rst	Fri Jul 30 16:01:28 2010 +0200
+++ b/doc/book/en/devrepo/entityclasses/adapters.rst	Fri Jul 16 16:08:04 2010 +0200
@@ -3,19 +3,18 @@
 Interfaces and Adapters
 -----------------------
 
-Interfaces are the same thing as object-oriented programming
-`interfaces`_. Adapter refers to a well-known `adapter`_ design
-pattern that helps separating concerns in object oriented
-applications.
+Interfaces are the same thing as object-oriented programming `interfaces`_.
+Adapter refers to a well-known `adapter`_ design pattern that helps separating
+concerns in object oriented applications.
 
 .. _`interfaces`: http://java.sun.com/docs/books/tutorial/java/concepts/interface.html
 .. _`adapter`: http://en.wikipedia.org/wiki/Adapter_pattern
 
-In |cubicweb| adapters provide logical functionalities
-to entity types. They are introduced in version `3.9`. Before that one
-had to implement Interfaces in entity classes to achieve a similar goal. However,
-hte problem with this approch is that is clutters the entity class's namespace, exposing
-name collision risks with schema attributes/relations or even methods names
+In |cubicweb| adapters provide logical functionalities to entity types. They
+are introduced in version `3.9`. Before that one had to implement Interfaces in
+entity classes to achieve a similar goal. However, the problem with this
+approach is that is clutters the entity class's namespace, exposing name
+collision risks with schema attributes/relations or even methods names
 (different interfaces may define the same method with not necessarily the same
 behaviour expected).
 
@@ -128,7 +127,7 @@
 
     class MyEntity(AnyEntity):
         __regid__ = 'MyEntity'
-	__implements__ = AnyEntity.__implements__ + (IFoo,)
+        __implements__ = AnyEntity.__implements__ + (IFoo,)
 
         def bar(self, *args):
             return sum(captain.age for captain in self.captains)
--- a/doc/book/en/tutorials/tools/windmill.rst	Fri Jul 30 16:01:28 2010 +0200
+++ b/doc/book/en/tutorials/tools/windmill.rst	Fri Jul 16 16:08:04 2010 +0200
@@ -150,6 +150,25 @@
 windmill recorded use cases.
 
 
+Caveats
+=======
+
+File Upload
+-----------
+
+Windmill can't do file uploads. This is a limitation of browser Javascript
+support / sandboxing, not of Windmill per se.  It would be nice if there were
+some command that would prime the Windmill HTTP proxy to add a particular file
+to the next HTTP request that comes through, so that uploads could at least be
+faked.
+
+.. http://groups.google.com/group/windmill-dev/browse_thread/thread/cf9dc969722bd6bb/01aa18fdd652f7ff?lnk=gst&q=input+type+file#01aa18fdd652f7ff
+
+.. http://davisagli.com/blog/in-browser-integration-testing-with-windmill
+
+.. http://groups.google.com/group/windmill-dev/browse_thread/thread/b7bebcc38ed30dc7
+
+
 Preferences
 ===========