Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A good way of dealing with this is to associate your account_login_widget with its own view, like:</p> <pre><code>@view_config(name='login_widget', renderer='templates/account_login_widget.pt') def login_widget(request): return {'username': ...} </code></pre> <p>You should then be able to visit <a href="http://yourapp/login_widget" rel="noreferrer">http://yourapp/login_widget</a> and get back only the widget's HTML.</p> <p>What's left to do is to call the view and include the resulting HTML in your template. That is, instead of:</p> <pre><code>&lt;span metal:use-macro="load: account_login_widget.pt"&gt;&lt;/span&gt; </code></pre> <p>you'll want something like:</p> <pre><code>&lt;span tal:replace="structure render_view('login_widget')"&gt;&lt;/span&gt; </code></pre> <p><code>render_view</code> however doesn't exist in templates; you'll have to provide it yourself. It's best to use the Before Render Event for this: <a href="http://docs.pylonsproject.org/projects/pyramid/dev/narr/hooks.html#beforerender-event" rel="noreferrer">http://docs.pylonsproject.org/projects/pyramid/dev/narr/hooks.html#beforerender-event</a></p> <pre><code>from pyramid.events import subscriber from pyramid.events import BeforeRender from pyramid.view import render_view_to_response @subscriber(BeforeRender) def add_render_view_global(event): event['render_view'] = lambda name: render_view_to_response(context, request, name, secure).ubody </code></pre> <p>Done. This approach will also help should you ever need to (re)load widgets dynamically through AJAX.</p>
    singulars
    1. This table or related slice is empty.
    1. POajax widgets in pyramid and chameleon
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDaniel Nouri
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POajax widgets in pyramid and chameleon
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks! This strategy sounds pretty good and gets me far. There is still a kink or two though. Does your suggestion assume use of traversal? I'm using url dispatch. The problem I have is the '@view_config' doesn't specify a route_name so the url: http://yourapp/login_widget isn't found (this also means my ajax post doesn't work). But when I specify the route_name in addition to name, then the call to render_view_to_response() doesn't resolve to a view. It seems I can only specify 'name' or 'route_name' in the '@view_config', but not both. What's going wrong here?
      singulars
      1. PO
      1. USlostdorje
    2. COAdding two view_configs seems to do the trick. The combined predicates were overly specific. But adding 2 view_configs seems awkward too. @view_config(name='account_login_widget', renderer='template/account_login_widget.pt') @view_config(route_name='account_login_widget', renderer='template/account_login_widget.pt')
      singulars
      1. PO
      1. USlostdorje
    3. COYou're right. The view configuration bit of my answer (`@view_config`) assumes traversal. The view configuration will differ if you're using url dispatch. http://docs.pylonsproject.org/projects/pyramid/dev/narr/urldispatch.html#route-configuration
      singulars
      1. PO
      1. USDaniel Nouri
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload