simplejson installation failure
Can´t get simplejson installed with easy install. I don´t know how to install manually without easy install, don´t know the necessary commands. Other pylons-components that I had to install with easy install worked well. I had to install some components separately because installation of pylons paket wouldn´t work, it stopped at the failure with simplejson. Any help appreciated, thanks. Protocol: C:\Python26\Scriptseasy_install-2.6.exe simplejson Searching for simplejson Reading http://pypi.python.org/simple/simplejson/ Reading http://undefined.org/python/#simplejson Best match: simplejson 2.0.4 Downloading http://pypi.python.org/packages/source/s/simplejson/simplejson-2.0.4 .tar.gz#md5=9a888ea017ef2fcd42a2823454950b16 Processing simplejson-2.0.4.tar.gz Running simplejson-2.0.4\setup.py -q bdist_egg --dist-dir c: \dokume~1\johndoe\lo kale~1\temp\easy_install-8nk8s5\simplejson-2.0.4\egg-dist-tmp-wy68t0 error: Setup script exited with error: None C:\Python26\Scripts --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: webhelpers.paginate+mako ajax
Hi, Mike and Ben...
On Mittwoch, 5. November 2008, Mike Orr wrote:
On Wed, Nov 5, 2008 at 11:14 AM, ben adam [EMAIL PROTECTED] wrote:
I have a mako template that looks like:
## start template-
%inherit file=/base.tmpl /
div id=my_results
p${ c.paginator.pager('$link_first $link_previous $first_item to
$last_item of $item_count $link_next $link_last',
onclick=YAHOO.util.Connect.asyncRequest('GET','%s',
{success\
:function(o)
{YAHOO.util.Dom.get('my_results').innerHTML=o.responseText;}},null);re
turn false;) }/p
## display results here from c.paginator
/div
## stop template-
The file base.tmpl contains the header/footer/navigation,etc. The
first page is displayed properly. However, when I page through the
resutls the my_results div gets populated with the requested page
including the content of base.tmpl (meaning the header/footer stuff).
How can I avoid this?
You need to make a separate action that returns only the new fragment
for the div. Or you can use the same action if you add a query
parameter 'partial' to tell it whether to output a full page or a
fragment. Paginate has (had) some built-in support for this, but it
may have been removed during the general removal of Javascript code in
WebHelpers 0.6. I think any extra keyword args you add to the
[constructor or pager call?] get transformed to query params in the
page URLs. See the docstrings in the webhelpers.paginate source.
The paginate module still has partial support. Unless you set
the partial_param paramter to the pager() call your requests done by
the 'onclick' action will contain 'partial=1' as a parameter.
To quote my inline documentation:
partial_param:
When using AJAX/AJAH to do partial updates of the page area the
application has to know whether a partial update (only the
area to be replaced) or a full update (reloading the whole
page) is required. So this parameter is the name of the URL
parameter that gets set to 1 if the 'onclick' parameter is
used. So if the user requests a new page through a Javascript
action (onclick) then this parameter gets set and the
application is supposed to return a partial content.
And without
Javascript this parameter is not set. The application thus has
to check for the existance of this parameter to determine
whether only a partial or a full page needs to be returned.
See also the examples in this modules docstring.
Default: 'partial'
So you just have to check that parameter like in:
if 'partial' in request.params:
return render('/foobar/partial.mako')
else:
return render('/foobar/full-page.mako')
Usually you just % include...% the partial.mako from the full-page.mako.
I had written a piece of documentation that you want to check:
http://docs.pylonshq.com/helpers.html#partial-updates-with-ajax
Cheers
Christoph
signature.asc
Description: This is a digitally signed message part.
Re: AuthKit
Hi Eric, It isn't that it hasn't received any attention, rather that I need to be sure your patch won't break other functionality. I've released AuthKit 0.4.1 which mirrors the current trunk and started working on applying the patches but for the next week or two I'm going to be completely busy with the final proof-reads of the Pylons Book so I'm not going to be able to test your patch until then. If you know anyone who would like to help me maintain AuthKit I'd be happy to hear from them. Cheers, James On Nov 3, 9:18 am, Eric Lemoine [EMAIL PROTECTED] wrote: On Fri, Oct 31, 2008 at 7:41 PM, Walter Cruz [EMAIL PROTECTED] wrote: A new version was released some weeks ago.. What's the issue of yor ticket? Thanks for your response. Here's the ticket: http://authkit.org/trac/ticket/59 -- Eric --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: simplejson installation failure
Received the following in an email from James Gardner, guess this will solve my problems, the other one was virtual Python environment install failure; may be helpful to other newbies here: Pylons doesn't support Python 2.6 yet but the developers are working hard on it so that it will when the book is published. Try Python 2.5.2 and it should all work perfectly. I tested it on Vista last week with Pylons 0.9.7rc2. Pylons 0.9.7 isn't officially released yet so if you are new to Pylons you might want to wait until it is. On 6 Nov., 10:20, antonio [EMAIL PROTECTED] wrote: Can´t get simplejson installed with easy install. I don´t know how to install manually without easy install, don´t know the necessary commands. Other pylons-components that I had to install with easy install worked well. I had to install some components separately because installation of pylons paket wouldn´t work, it stopped at the failure with simplejson. Any help appreciated, thanks. Protocol: C:\Python26\Scriptseasy_install-2.6.exe simplejson Searching for simplejson Readinghttp://pypi.python.org/simple/simplejson/ Readinghttp://undefined.org/python/#simplejson Best match: simplejson 2.0.4 Downloadinghttp://pypi.python.org/packages/source/s/simplejson/simplejson-2.0.4 .tar.gz#md5=9a888ea017ef2fcd42a2823454950b16 Processing simplejson-2.0.4.tar.gz Running simplejson-2.0.4\setup.py -q bdist_egg --dist-dir c: \dokume~1\johndoe\lo kale~1\temp\easy_install-8nk8s5\simplejson-2.0.4\egg-dist-tmp-wy68t0 error: Setup script exited with error: None C:\Python26\Scripts --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: TOPIC: Javascript library
On Nov 4, 2008, at 10:35 PM, Wojciech Malinowski wrote: Mr.Rech wrote: However, I'm a little bit lost about Javascript library, since, as far as I can understand, from version 0.9.7 there is no default Javascript library. So, I'm asking you which library you are using and why. I had the same choice to make yesterday. This site helped me a lot: http://www.ja-sig.org/wiki/display/UP3/Javascript+Toolkit+Comparison That page is from 2006 and is somewhat incomplete and out of date. This comparison is better: http://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks -matt --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: simplejson installation failure
On Nov 6, 2008, at 1:20 AM, antonio wrote: Can´t get simplejson installed with easy install. I don´t know how to install manually without easy install, don´t know the necessary commands. Other pylons-components that I had to install with easy install worked well. I had to install some components separately because installation of pylons paket wouldn´t work, it stopped at the failure with simplejson. Any help appreciated, thanks. Protocol: C:\Python26\Scriptseasy_install-2.6.exe simplejson Searching for simplejson Reading http://pypi.python.org/simple/simplejson/ Reading http://undefined.org/python/#simplejson Best match: simplejson 2.0.4 Downloading http://pypi.python.org/packages/source/s/simplejson/simplejson-2.0.4 .tar.gz#md5=9a888ea017ef2fcd42a2823454950b16 Processing simplejson-2.0.4.tar.gz Running simplejson-2.0.4\setup.py -q bdist_egg --dist-dir c: \dokume~1\johndoe\lo kale~1\temp\easy_install-8nk8s5\simplejson-2.0.4\egg-dist-tmp-wy68t0 error: Setup script exited with error: None First, ensure you're using the latest setuptools -- 0.6c9. If the problem still occurs, try running easy_insatll with the -v (verbose) option. Otherwise we can't tell what actually happened here. -- Philip Jenvey --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: webhelpers.paginate+mako ajax
Thanks, this makes it clear now.
On Nov 6, 4:25 am, Christoph Haas [EMAIL PROTECTED] wrote:
Hi, Mike and Ben...
On Mittwoch, 5. November 2008, Mike Orr wrote:
On Wed, Nov 5, 2008 at 11:14 AM, ben adam [EMAIL PROTECTED] wrote:
I have a mako template that looks like:
## start template-
%inherit file=/base.tmpl /
div id=my_results
p${ c.paginator.pager('$link_first $link_previous $first_item to
$last_item of $item_count $link_next $link_last',
onclick=YAHOO.util.Connect.asyncRequest('GET','%s',
{success\
:function(o)
{YAHOO.util.Dom.get('my_results').innerHTML=o.responseText;}},null);re
turn false;) }/p
## display results here from c.paginator
/div
## stop template-
The file base.tmpl contains the header/footer/navigation,etc. The
first page is displayed properly. However, when I page through the
resutls the my_results div gets populated with the requested page
including the content of base.tmpl (meaning the header/footer stuff).
How can I avoid this?
You need to make a separate action that returns only the new fragment
for the div. Or you can use the same action if you add a query
parameter 'partial' to tell it whether to output a full page or a
fragment. Paginate has (had) some built-in support for this, but it
may have been removed during the general removal of Javascript code in
WebHelpers 0.6. I think any extra keyword args you add to the
[constructor or pager call?] get transformed to query params in the
page URLs. See the docstrings in the webhelpers.paginate source.
The paginate module still has partial support. Unless you set
the partial_param paramter to the pager() call your requests done by
the 'onclick' action will contain 'partial=1' as a parameter.
To quote my inline documentation:
partial_param:
When using AJAX/AJAH to do partial updates of the page area the
application has to know whether a partial update (only the
area to be replaced) or a full update (reloading the whole
page) is required. So this parameter is the name of the URL
parameter that gets set to 1 if the 'onclick' parameter is
used. So if the user requests a new page through a Javascript
action (onclick) then this parameter gets set and the
application is supposed to return a partial content.
And without
Javascript this parameter is not set. The application thus has
to check for the existance of this parameter to determine
whether only a partial or a full page needs to be returned.
See also the examples in this modules docstring.
Default: 'partial'
So you just have to check that parameter like in:
if 'partial' in request.params:
return render('/foobar/partial.mako')
else:
return render('/foobar/full-page.mako')
Usually you just % include...% the partial.mako from the full-page.mako.
I had written a piece of documentation that you want to
check:http://docs.pylonshq.com/helpers.html#partial-updates-with-ajax
Cheers
Christoph
signature.asc
1KViewDownload
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~--~~~~--~~--~--~---
