> Thanks for the wonderful web2py. Here are some spelling errors that I 
>> found in
>
> the diff download.
>
>
>> +As soon as you type something in the search box and release a key, the 
>> client calls the server and sends the content of the 'keyword' field, and, 
>> when the sever responds, the response is embedded in the page itself as the 
>> innerHTML of the 'target' tag.   {{{{{when the server responds}}}}
>
>
>>
>> +yet this representation in internationalized and you can use the admin 
>> stranslation page to change the format to an alternate one. For example:
>
>
>> {{{{looks like stranslation shoud be translation}}}
>
>
>>
>> +Mind that by default English is not translated because web2py assumes 
>> the applications is already written in English. If you want 
>> internationalization to work for English you need to create the translation 
>> file (using admin) and you need declare that the application current 
>> language is something other than english, for example:
>
>
>> {{{{assumes the applications are already written}}
>
>
>>
>> +Then choose a slug (in the publishing business, a slug is a short name 
>> given to an article that is in production) and you will be redirected to an 
>> empty page where you can edit the content using MARKMIN wiki syntax. A new 
>> menu item called "[wiki]" will allow you create, search, and edit pages. 
>> Wiki pages have RULS like:
>
> + {{{{RULS should be URLS?}}}}}
>
>
>>
>> Try create more pages such as "index", "aboutus", and "contactus".
>
> +Try edit them.
>
>
>> {{{ Try to create....Try to edit them. }}}
>
>
>>
>> +- ``render`` which defaults to ``'markmin'`` but can be set equal to 
>> ``'html'``. It termines the syntax of the wiki. We will discuss the markmin 
>> wiki markup later. If you change it to HTML you may want to use a wysiwyg 
>> javascript editor such as TinyMCE of NicEdit.
>
> {{{ It determines the syntax}}}
>
>
>> +- ``manage_permissions``. This is set to ``False`` by default and only 
>> recognizes permissions for "wiki-editor" and "wiki-author". If you change 
>> it to ``True`` the create/edit page will give the option to specify by 
>> names the groups whose members have permission to read and edit the page. 
>> In this case is a group "everybody" to give read permission to everybody.
>
>
>> {{ please eix this last sentence, "In this case is a group" which does 
>> not make sense.}}}
>
>
>>
>> +- ``restrict_search``. This default to ``False`` and any logged-in user 
>> can search all wiki pages (but not necessary read or edit them). If set to 
>> ``True``, authors can search only their own pages, editors can search 
>> everything, other users cannot search anything.
>
>
>> {{{ This defaults}}}
>
>
>>
>> +This call the join function passed as extra with parameters 
>> ``a,b,c=1,2,3`` and will be rendered as ``1-2-3``.
>
>
>> {{{This calls the join }}
>
>
>> +Mind that the menu is appended to ``response.menu``. It does not replace 
>> it. The ``[wiki]`` menu tem with service functions is added automatically.
>
> +
>
>
>> {{{{  menu item with service }}}}} 
>
>
>> +Also, by setting resolve to ``False`` in the method call, the wiki 
>> tables will be now accesible trough the app's default db interface at 
>> ``<app>/appadmin`` for managing wiki records.
>
>
>> {{{accessible through the app's }}}
>
>
>> i+This allows the visitor interact with the component via Ajax without 
>> reloading the host page that embeds the widget. Basically the action is 
>> called via Ajax, inherits the stile of the host page, and capture all forms 
>> submissions and flash messages so that they are handled within the current 
>> page. On top of this the ``SQLFORM.grid`` widget uses digitally signed URLs 
>> to restrict access. More information about components can be found in 
>> chapter 13.
>
>
>> {{inherits the style of the host }}}
>
>
>> +This simply tells web2py that we want to incude the "manage_things" 
>> action defined in the "default" controller as an Ajax "component".
>
>
>> {{{{ we want to include the }}}
>
>
>> +Notice that the admin application includes "plugin_jqmodile" which 
>> packages jQuery Mobile. When admin is accessed from a mobile device; 
>
>
>> {{{ includes "plugin_jqmodule" }}}
>
>
>> +- ``response._caller``: this is a function that wraps all action calls. 
>> It defaults to the identity function, but it can be modifed in order to 
>> catch special types of exception to do extra logging;
>
> +  ``
>
>
>> {{{{ it can be modified in }}}}
>
>
>
I will read some more this evening.

 

-- 



Reply via email to