Re: bugz.fedoraproject.org/packagename MIA?
On Thu, Dec 06, 2012 at 10:01:32PM +0200, Ville Skyttä wrote: Hello, http://bugz.fedoraproject.org/packagename URLs no longer work, they redirect to https://apps.fedoraproject.org/packages/error which appears to be some kind of a 404 Not Found page. Known issue? Sorry for the troubles. I switched the bugz alias over from pkgdb to the newer fedora-packages webapp last Friday as per https://fedorahosted.org/fedoracommunity/ticket/381 What package in particular are you trying? For instance, https://bugz.fedoraproject.org/nethack works for me. An idea: packages that have do not have rawhide builds are not indexed by the fedora-packages webapp. This could be why your request is returning a 404. -Ralph pgpdMO0xhpyoV.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Solicitation: Review Swap
Anyone interested in a package review swap? python-logutils: https://bugzilla.redhat.com/show_bug.cgi?id=884041 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: paste to production?
On Tue, Dec 04, 2012 at 11:23:09PM -0700, Clint Savage wrote: One thought here might be to implement a link shortener. Something like fed.io or fedora.io might be cool. I did also think about fpas.te which would work well. However, the thought here is these would be good only if having something that doesn't end in fedoraproject.org is possible. I think a link shortener would be great for general use. If we could grab http://fed.io, then the fpaste cli tool could automatically pass your paste.fedoraproject.org url through the shortener on each run. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: New Online search for the Fedora Source
On Fri, Nov 30, 2012 at 01:38:29PM +, Pádraig Brady wrote: On 11/30/2012 12:09 PM, Pádraig Brady wrote: Benjamin Boyter has recently indexed the entire Fedora Source code. I.E. all 2 billion lines, 11K packages, 132 GB of it. For details including search syntax, please see: http://www.pixelbeat.org/docs/fedora_source.html This is really nice. Thanks for sharing! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[TW] toscawidgets.org is down again :/
Paul, can you check it out? http://toscawidgets.org/ -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] toscawidgets.org is down again :/
Cool. It's back now. :) Thanks Paul! On Mon, Nov 26, 2012 at 10:03:34PM +, Paul Johnston wrote: Sorry about that, and thanks for the heads up. I've now renewed the domain so it should come back to life in a couple of hours. Paul Sent from my iPhone On 26 Nov 2012, at 18:43, Ralph Bean rb...@redhat.com wrote: Paul, can you check it out? http://toscawidgets.org/ -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en. -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en. -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: Orphaning many packages
On Mon, Nov 26, 2012 at 04:08:22PM -0800, Jesse Keating wrote: python-offtrac I'll take this one! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Landing page for apps.fedoraproject.org
On Mon, Nov 05, 2012 at 08:47:09PM +0200, Elad Alfassa wrote: I still don't think it fits in that category. Which category do you think it fits in? -- websites mailing list websites@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/websites
Re: Landing page for apps.fedoraproject.org
On Mon, Nov 05, 2012 at 12:03:06PM -0800, Karsten 'quaid' Wade wrote: If I want to use this for a different community, where do I start? Is it as straightforward as forking the codebase, tweaking data/apps.yaml, and hosting it on a TG stack? No TG necessary.. it's all static files to be served by apache or nginx or whatever you have. Fork, tweak, and run the following to regenerate some of the static pieces from data/apps.yaml. python bin/yaml2html.py apps-yaml.html python bin/yaml2json.py js/data.js -- websites mailing list websites@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/websites
Landing page for apps.fedoraproject.org
Hello, I made a landing page for apps.fedoraproject.org. Draft - http://threebean.org/apps.fp.o/ I was wondering if I could get some feedback on it. Should it be changed? Should it be scrapped? The source is on github if you'd like to make changes yourself -- you can submit changes directly in the web interface there. http://github.com/ralphbean/apps.fp.o/ -Ralph -- websites mailing list websites@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/websites
Re: Landing page for apps.fedoraproject.org
On Fri, Nov 02, 2012 at 02:42:22PM +0100, Kévin Raymond wrote: for the community will you add paste.fpo there? Good call. I added it here: https://github.com/ralphbean/apps.fp.o/commit/8cff4f3b57323c9c48a63eea814b934f8da4af06 -- websites mailing list websites@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/websites
Re: Landing page for apps.fedoraproject.org
On Fri, Nov 02, 2012 at 04:18:30PM +0200, Elad Alfassa wrote: It's nice, but the icons could use a bit of tweaking (gnu icon doesn't represent mailing lists, for example)... and maybe we could have bugzilla there too? Agreed -- I was grasping at straws for the mailman icon. I'll just remove it until we can come up with something better. Adding bugzilla is good. Added here: https://github.com/ralphbean/apps.fp.o/commit/b8805ce92ceffc77a71bfeaae9846304613458c5 -- websites mailing list websites@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/websites
Re: [TW] Translation of validation errors
On Tue, Sep 25, 2012 at 09:51:56AM +0200, Christoph Zwerschke wrote: After switching from TW1 (Formencode) to TW2 (with its own validators), I noticed that my validation errors now appear untranslated. How is the translation of the standard validation error messages provided by TW2 actually supposed to work? I noticed they are marked with the lazy translation function of the underlying framework. Does that mean you are supposed to somehow merge all the messages from tw2.core into you own translation files, and translate these message on your own? Formencode used its own translation domain and came packaged with translation files for all standard validator messages, which was very convenient. Translations worked out of the box. I wrapped all those error messages with the translation callback, not really knowing what I was doing. Someone requested it, and then never wrote back. Now is a better time than never to sort it out. It makes sense for tw2 to provide translations for its own strings. I'll try to have some out in the next release. In the meantime, you might be able to get somewhere more quickly using formencode's validators. TW2 is supposed to be able to accept formencode validators everywhere in place of its own. -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Translation of validation errors
On Mon, Oct 01, 2012 at 07:05:00PM +0200, Christoph Zwerschke wrote: Am 01.10.2012 16:11, schrieb Ralph Bean: I wrapped all those error messages with the translation callback, not really knowing what I was doing. Someone requested it, and then never wrote back. Now is a better time than never to sort it out. Ok, I thought I overlooked something. Actually the whole matter is a bit complicated. Even if we had all translations, TW2 would still need to know which language the current user is using. This can be provided as attribute of the state argument for validators that is passed around, but frameworks would need to actively do that. Also, there is a problem with custom validators which can have both custom messages and original TW2 messages. So the framework translation function would need to fallback to the TW2 translator. Pylons and TG2 do all of this, but only for FormEncode, not for TW2 validators. And I think there should be a more clever way to do this, like using a lazy_dgettext method. Cool. Christoph, are you interested at all in writing this? I can take it up, but I must admit that I 1) have no direct need for the feature at the moment and 2) am very consumed with another project at work. If you're not into taking it up, that's fine. We should make a ticket out of it and I'll take it up next. -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Forms should generate proper labels
On Mon, Oct 01, 2012 at 07:14:42PM +0200, Christoph Zwerschke wrote: I noticed another regression from TW1 which created proper labels for widget fields with a for=... attribute that linked the label to the respective widget field. So for instance, you could click on the label to check/uncheck a checkbox or radiobutton. If you use a ListForm in TW2, then it creates labels, but without for=... attributes, and if you use a TableForm, then it does not even create labels at all, just puts the labels in table headings. I think the default form templates should do better and generate real label elements. Agreed. moschlar and I added add this to tw2.bootstrap.forms. I think writing this back into tw2.forms itself is a good idea, but we should let this discussion sit on the list for a little bit and see if anyone objects. Cool? -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] JSSource injected multiple times
On Mon, Oct 01, 2012 at 05:00:06PM +0200, Christoph Zwerschke wrote:
Another problem I noticed when trying to adapt a TW1 app to TW2:
When a widgets uses a JSLink as a resource, then this JSLink will only be
injected once on the same page, however, when it uses a JSSource as a
resource, then this JSSource will be injected as many times as the widgets
appears on the page.
Here is a typical use case that demonstrates the problem:
import tw2.core as twc, tw2.forms as twf
import tw2.devtools as twd
class MyField(twf.TextField):
resources = [twc.JSLink(link='some_plugin'),
twc.JSSource(src=$('.myfield').init_plugin())]
css_class = 'myfield'
class Index(twf.FormPage):
title = Test
class child(twf.TableForm):
field1 = MyField()
field2 = MyField()
twd.dev_server()
When you run this code, you will see that the plugin link is only injected
once in the head of the page, but the initialization code is inserted twice
at the bottom of the page, which is usually not what you want, and different
from the behavior of TW1.
Is this a bug, or am I doing something wrong here?
Christoph, I think this is a bug.
I haven't identified a root cause yet, but I typically accomplish what
you are trying to do with the following code:
import tw2.core as twc, tw2.forms as twf
import tw2.devtools as twd
class MyField(twf.TextField):
resources = [twc.JSLink(link='some_plugin')]
css_class = 'myfield'
def prepare(self):
super(MyField, self).prepare()
self.add_call($('.myfield').init_plugin())
class Index(twf.FormPage):
title = Test
class child(twf.TableForm):
field1 = MyField()
field2 = MyField()
twd.dev_server()
The above injects the .init_plugin line only once. Still, what you were
trying to do *should* work fine. Can you file a bug for it, please?
-Ralph
--
You received this message because you are subscribed to the Google Groups
ToscaWidgets-discuss group.
To post to this group, send email to toscawidgets-discuss@googlegroups.com.
To unsubscribe from this group, send email to
toscawidgets-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: Release of fedora-review 0.3.0 done, 0.3.1 hotfix on the way
On Tue, Sep 25, 2012 at 04:37:31PM +0200, Stanislav Ochotnicky wrote: fedora-review development team proudly presents :-) Release of fedora-review 0.3.0 [1-3] Exciting! Thanks for working on this! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Package Review Swap Request: datanommer
Hello, Anyone interested in swapping package reviews? https://bugzilla.redhat.com/show_bug.cgi?id=853252 Thanks in advance- -Ralph -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: announcing repository updates over Fedora Message Bus
On Mon, Sep 10, 2012 at 11:30:15AM -0400, Ralph Bean wrote: branched and rawhide are another story. We'd need to add fedmsg-logger statements to some of the scripts in http://git.fedorahosted.org/cgit/releng/tree/scripts, but I'm not sure where yet. Just an update: I talked with dgilmore about this today and he'd like to wait until a composedb app is written so we can have all the fedmsg statements in a nice, centralized place (not strewn out across all the releng scripts). ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: announcing repository updates over Fedora Message Bus
On Mon, Sep 10, 2012 at 12:07:12PM -0400, Kamil Paral wrote: Exciting! Please don't forget to share on planet.fp.o once you have something. This is great stuff. Updated docs: - http://fedmsg.rtfd.org/ - http://fedmsg.readthedocs.org/en/latest/consuming.html I'm going to hold off sharing on the planet until we can get a port open for external message consumption of the production bus. Right now, only staging is available (with practically no activity). After the freeze, hopefully we can get that in place. An announcement pointing folks to the docs will be more timely then. :) ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: announcing repository updates over Fedora Message Bus
On Mon, Sep 10, 2012 at 08:56:26AM -0400, Kamil Paral wrote: I wonder, is it possible for Fedora Infrastructure team to implement announcements of new repository pushes over Fedora Message Bus[1]? By new repository pushes I mean updates to 'fedora', 'updates' and 'updates-testing' repositories for all Fedora releases as well as updates to 'branched' and 'rawhide' trees. Some of this should already be happening. There is a org.fedoraproject.prod.bodhi.mashtask.sync.done message that should be getting emitted, but we don't have a way to check the history and verify yet. https://bugzilla.redhat.com/show_bug.cgi?id=853252 should take care of that. branched and rawhide are another story. We'd need to add fedmsg-logger statements to some of the scripts in http://git.fedorahosted.org/cgit/releng/tree/scripts, but I'm not sure where yet. The benefits of this solution: 1. Mirrors that download from dl.fp.o could start syncing very soon after an update is pushed (after a random timeout to decrease the load). 2. Those mirrors wouldn't have to periodically query the server for updates. 3. The duration when those mirrors are outdated would be shorter. I can just guess about other people, but in our office I believe the message bus would help a lot. Currently we query the master server every 4 hours for updates. That presents a lot of bandwidth/IO load on both sides. Using the message bug there would be no useless queries. Also it would help us stay up-to-date more often that we currently are (if 'branched' is updated an hour after our last query, there are 3 hours wasted until we run rsync again). This solution could be extended in the future to all Fedora public mirrors, so that they could announce using our message bus when they have finished syncing and users that sync from that particular mirror would know when to start downloading from it. (E.g. if I use mirrors1.kernel.org to sync my private mirror, I would wait for their announcement on our message bus). What do you think? This sounds great for the future. I've been working on docs this week (not quite done yet). I'll have docs out soon with examples on how to do something like this. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Review Requests for moksha (fedmsg)
fedmsg was pulling in way too many dependencies, including (almost) a whole web stack. None of it was even being used. All of it came from moksha which grew as an all-in-one, batteries-included framework. I split moksha upstream into three separate namespace packages to solve the problem. Now they're up for package review. If anyone is free to lend a review, it'd be much appreciated. https://bugzilla.redhat.com/showdependencytree.cgi?id=854605hide_resolved=1 Some notes: The package moksha will still exist, but now as a kind of meta-package that just included the other three. Its subpackages like moksha-server (httpd) and moksha-doc (sphinx) will continue to exist as well. My changes will break most projects that use moksha until they can be patched to use the new namespace. For us, this includes: - The packages webapp - fedmsg - busmon I've already prepared and tested commits to the development trees of all three projects that work with the new moksha. -threebean ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Review Requests for moksha (fedmsg)
On Wed, Sep 05, 2012 at 03:13:35PM +0200, Patrick Uiterwijk wrote: Hey, I have taken the three reviews, will do them soon. - Patrick Thanks, Patrick. :) ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Freeze break request: tweak mediawiki's fedmsg plugin
Good evening, The httpd root process has been dieing seemingly at random on the different app0* servers. We're not sure what it is, but there's a chance that it could be the fedmsg-emit.php plugin. Here's a proposed patch that's been sitting in staging for about a week: http://www.fpaste.org/VqpG/ The theory is that, before, if fedmsg-config failed (which it shouldn't), then the script would call die(). die() shouldn't terminate the root httpd process, but.. well.. we're not sure what else could be happening. The change goes: instead of calling die(), if the plugin can't setup its fedmsg socket, then it just won't register its callbacks with mediawiki, instead of calling die(); I've tested that this is sane in staging, but there's no way to test that it fixes the issue, since it happens randomishly. This doesn't require a new fedmsg rpm. The fedmsg-emit.php plugin is kept in puppet. Seeking +1s for freeze break. Cheers! ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: [TW] defined attributes in SQLAjqGridWidget
On Sun, Aug 19, 2012 at 09:46:12PM -0700, jeetu wrote:
I tried using colModel values but I am not able to get the total_sales
visible.
pager_options = {
colModel: [{ name: name}, {name:total_sales}],
colNames:[name, total_sales],
}
Or do I have to literally override the colModel?
Literally overriding it is what I had in mind. If you see
:meth:`_get_metadata` here: http://bit.ly/QSrnEg It uses
:meth:`_make_model` across only the properties. If you override
cls.colModel with your own custom list of dicts, the widget would use
yours instead of building its own.
Alternatively, you could override :meth:`_get_properties` to return
all the properties plus a reference to total_sales. Then the widget
should (hopefully) build its own colModel including your computed
column. See here for _get_properties - http://bit.ly/QSs8gA
--
You received this message because you are subscribed to the Google Groups
ToscaWidgets-discuss group.
To post to this group, send email to toscawidgets-discuss@googlegroups.com.
To unsubscribe from this group, send email to
toscawidgets-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] defined attributes in SQLAjqGridWidget
Hi, For starters, here's the code that produces the data for that widget: https://github.com/toscawidgets/tw2.jqplugins.jqgrid/blob/develop/tw2/jqplugins/jqgrid/widgets/sqla.py I haven't played with it in a while, but I think you might be able to override colModel and get what you want. Unfortunately, I have never tried this and have no examples for you. ;) Alternatively, you could try a patch at including memoized properties to the list of attributes that get automatically included and displayed. That would be excellent, but likely much more work. -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Freeze break for post-update hook on pkgs01?
When we were adding the fedmsg hooks to pkgs01 and pkgs01.stg, we decided it would be a nice extra to run git update server-info on each repo for each push. This made cloning via http possible. We ran a script git check-perms /srv/git/rpms --check=post-update --fix on pkgs01 that added this hook for every repo, but I forgot to add it to setup_git_package so that it would be added for every new repo. Now there are a handful of repos that do not have the hook, while most others do. Other than the inconsistency, this doesn't matter all too much. It is annoying, however, due to a cron job that is checking for the new hook, failing to find it, and bothering sysadmins about it over email. I'm seeking +1s for a freeze break to make the following two changes: 1) Run git check-perms /srv/git/rpms --check=post-update --fix on pkgs01 again to fix the handful of repos that are out of sync. 2) Apply the following patch in puppet which will add the hook for new repos. diff --git a/modules/gitolite/files/distgit/setup_git_package b/modules/gitolite/files/distgit/setup_git_package index bd42b95..eeaa16f 100755 --- a/modules/gitolite/files/distgit/setup_git_package +++ b/modules/gitolite/files/distgit/setup_git_package @@ -121,6 +121,9 @@ ln -s /usr/share/git-core/post-receive-fedmsg \ ln -s /usr/share/git-core/post-receive-chained \ $GITROOT/$PACKAGE.git/hooks/post-receive +# This executes git update-server-info on each push for clone via http +ln -s /usr/share/git-core/templates/hooks/post-update.sample \ +$GITROOT/$PACKAGE.git/hooks/post-update rm -rf $TMPDIR echo Done. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break for post-update hook on pkgs01?
Ok, this should be all fixed up now. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: [TW] Proposal to create clean API to access resources stored in request_local
Hi all, I'm all about this proposal. If I might suggest an implementation detail: I ran into threading.local over the weekend (in the standard library) and it does a lot of what request_local does for us and in a way that will be more immediately readable by other python programmers. As for the newer uses of request_local around tw2.core: On Wed, Aug 15, 2012 at 09:48:11AM +0100, Paul Johnston wrote: queued_controllers controllers queued controllers queued_resources Not sure about these - I didn't put them in. They seem to work fine, although I'm unclear what exactly the purpose is. I think it's related to the problem that during application startup you don't have a middleware object in request local storage. My original approach to this was to have a single global middleware object, which you can override if you like. That makes the common use case (one middleware only) simple - while retaining the flexibility to have multiple. Their purpose is to work around serving a tw2 enabled app behind a multi-process webserver (like apache). Problem: You request a page. tw2 injects the necessary resources and readies them for serving. You receive the page. You make requests for the resources, but they are processed by other mod_wsgi apache processes which have not readied your resources. 404 error. Solution: Separate the notions of resources injection and resource serving in tw2. Resources are readied for serving in `post_define`. Resources are scheduled for injection in `prepare`. A similar scenario applies to controllers. The queued part is necessary because often widgets are defined (and post_define is executed) before the middleware object is ready in request_local. Therefore, I added queues for resources and controllers that get emptied and added once the middleware is initialized. Yours- -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] overriding add and edit button functionality in SQLAjqGridWidget.
Hi sahu, On Fri, Aug 10, 2012 at 12:42:45AM -0700, sahu wrote: Hi, i am following the tutorial at http://tw2core.readthedocs.org/en/latest/standalone On Edit/Add button of SQLAjqGridWidget, i want to have my own customized form which i have created (in a new page). For example, I want to open the following form in the same example when I click Add/Edit buttons of SQLAjqGridWidget class Movie(tw2.forms.FormPage): ... I'm afraid jqgrid may not be flexible enough for that. You could start at the upstream library's documentation http://www.trirand.com/jqgridwiki/doku.php, but I think this is going to take a good bit of hacking. I recommend you try a different angle. -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Re: Three ideas
Hi Paul, On Wed, Aug 01, 2012 at 03:21:13PM +0100, Paul Johnston wrote: I have created an initial version of tw2.auth: https://github.com/paj28/tw2.auth/ I will put the docs online at some point too. tw2.auth looks neat! I recommend readthedocs.org for docs. There is a service hook for github which rebuilds your sphinx docs and publishes for you. http://tw2core.rtfd.org is hosted there as well as a number of my own projects. You could in theory sign up for http://tw2auth.rtfd.org I have one concern! https://github.com/paj28/tw2.auth/blob/master/tw2/auth/PBKDF2.py is a copy/paste of a security module from somewhere else. While that's all fine ethically and legally, it can introduce security concerns in the future. What if an exploit is found in that code upstream? Your code in tw2.auth will never benefit from any security patches and be vulnerable (as well as anyone using it). I've heard good things about pyOpenSSL which is maintained and well-liked. I also recently wrote some code that used M2Crypto which was nice and so I'll recommend it. -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
fedmsg status, production, and help with testing?
I've been working on the Messaging SIG work for fedmsg for a few months now and have been active in IRC, but silent on this list. Here's a status report. At this point, I've developed an API for sending and receiving messages and have patched some existing services for only sending. Nothing *depends* on fedmsg messages arriving at this point, nor will anything so depend for a long while out. We want to be able to test and make sure that the fedmsg message bus is reliable and secure before we do anything like that. Status -- In staging, the following services are emitting fedmsg messages. - bodhi - fas - mediawiki - tagger - scm/gitolite/fedpkg Additionally, there is a new service running on app01.stg called fedmsg-relay. There are also two new commands: fedmsg-logger and fedmsg-tail. The messages are all signed by service-host specific RSA keys. Documentation for the CA and generating new cert/key pairs can be found at http://infrastructure.fedoraproject.org/infra/docs/fedmsg-certs.txt Motivation -- I'd like to move most of the puppet modules I have from modules-staging to modules sooner than later. I'm worried about that directory bloating and getting out of sync with the main modules directory over the long winter of the freeze. There's much more work to be done and the freeze offers a good opportunity to assess and commit to a setup. However, the freeze is set for next Tuesday, so soon! lmacken is preparing a bodhi1 release before the freeze which will include the fedmsg work and relrod is working on a fas release. That leaves mediawiki, tagger, and scm/gitolite/fedpkg on which we'll need to coordinate a push to production or decide that they stay in staging for the time being. For anyone with the time/energy, here is a set of instructions for how to test what I've set up. I've tested it pretty thoroughly, but peer review is best. Grotesque Detail For all the tests, login to app0[1-7].stg or packages[1-2].stg and run fedmsg-tail. There will be spam from the busmon consumer we have running in staging, so its probably best to run fedmsg-tail | grep -v busmon. Message signing is turned on globally from puppet in /etc/fedmsg.d/ssl.py. On a given host (say, app01.stg), check /etc/pki/fedmsg to see if the permissions on public certs and private keys makes sense. - fedmsg-logger - $ echo this is a test | fedmsg-logger - bodhi - Login to https://admin.stg.fedoraproject.org/updates - Messages are sent when you: - Make any change to an update. - fas - Login to https://admin.stg.fedoraproject.org/accounts - Messages are sent when you: - create a new user - edit your profile - apply for a group. - sponsor someone for a group. - create a group. - update a group. - remove a member from a group. - mediawiki - Login to https://stg.fedoraproject.org/wiki/Fedora_Project_Wiki - Messages are sent when you: - edit an article - upload something - tagger - Login to https://apps.stg.fedoraproject.org/tagger/ - Messages are sent when you: - Upvote/downvote a tag - Add a new tag - Login - scm/gitolite/fedpkg - Change your /etc/rpkg/fedpkg.conf to point to stg.fedoraproject.org. - Messages are sent when you: - Push a new commit Post Freeze Plans - Whether or not we can vet and push these into production before the freeze, I will be working on the following bits afterwards: - Documentation sprint: Some documentation for developers exists, but it hasn't had careful attention in a few months. It should include both a How-To for developers and some discussion of how the fedmsg internals work. - Start in on patches that add hooks to other services. http://fedmsg.readthedocs.org/en/latest/status.html is my running list. I think pkgdb, meetbot, and elections are next. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: [TW] Re: Three ideas
Paul, this all looks great to me. :) In the future we may want to think of providing some pre-written auth-checks that will ease integration with TG2 and/or pyramid. That, actually, would be an *excellent* place for new community members to contribute. I guess, let us know once the auth_check work is a little more settled. Yours- -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Re: Recursion CalendarDatePicker
On Thu, Jul 19, 2012 at 12:37:16AM -0700, Luca Verardi wrote: I also tried to follow this guide but did not work http://stackoverflow.com/questions/7551662/grails-calendar-plugin-throws-stack-recursion-error Il giorno mercoledì 18 luglio 2012 17:41:13 UTC+2, Luca Verardi ha scritto: Hi everybody. I have a big problem with the CalendarDatePicker (tw.forms = 0.9.9) Can you help me ??xD I feel obliged to respond, but I simply do not support ToscaWidgets1. I had no hand in writing it, and I've never really used it. That said, I know there are one or two people lurking on the list who used to maintain it. They might be able to respond and help. The best advice I can offer is to port your code to ToscaWidgets2 (tw2.core). Almost everybody is working on and supporting that codebase only now. Best wishes- -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] tw2.jqplugins.ui AccordionWidget no .js file?
On Tue, Jul 17, 2012 at 11:10:49PM -0500, Lukasz Szybalski wrote:
So finally found this post:
https://groups.google.com/forum/?fromgroups#!topic/toscawidgets-discuss/UhYg1gtcuBs
in which you say to give the widget an id
So in my view.py I did:
class DemoAccordionWidget(AccordionWidget):
id='Greatid'
items=[('itme1','item2'),('1item1','2item2')]
options = {
'fillSpace' : True,
'active' : 2
}
And success
Lukasz, I'm glad you figured it out. :) Sorry I wasn't more
prompt in helping -- too much going on!
-Ralph
--
You received this message because you are subscribed to the Google Groups
ToscaWidgets-discuss group.
To post to this group, send email to toscawidgets-discuss@googlegroups.com.
To unsubscribe from this group, send email to
toscawidgets-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] [TW2] FullCalendar Widget
On Tue, Jul 17, 2012 at 01:40:41PM -0700, Rob wrote: I'm not sure what the usual protocol is here, but I've placed put a TW2 wrapper around the FullCalendar library... a jquery plugin that creates rather useful calendar objects... Tested with tw2.browser etc etc, it's available at. https://github.com/RobertSudwarts/tw2.jqplugins.fullcalendar.git Any additions/suggestions would be gratefully accepted/acted upon! Rob, it's awesome! Here are my suggestions: - Release to pypi. If you've never done this, ask and I can give you all my tips. People should be able to specify it in their ``setup.py`` file for automatic inclusion or be able to:: $ pip install tw2.jqplugins.fullcalendar - Would you like me to add it to http://tw2-demos.threebean.org/ ? It's easy; I'll do it as soon as you say so. - If you'd like, you may transfer this to the http://github.com/toscawidgets organization. I think I can give you rights to manage it without issue. Of course, if you'd like to keep it under your own github repo for whatever reason, that's more than fine. - Write a blog post about it and how to use it. That way if people have problems using it, your post will come up when they google it. Great work! :) -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] CSSLink in the standalone tutorial does not work
On Fri, Jun 22, 2012 at 05:57:47PM +0200, Christoph Zwerschke wrote: Am 21.06.2012 19:29, schrieb Ralph Bean: to the Movie form, I get the folling wrong link in the output link rel=stylesheet type=text/css href=/resources/__main__/myapp.css media=all / Christoph- I get the same link inserted but I believe it is correct. The link looked somewhat strange and I think I got a 404. But I understand __main__ is the name of the toplevel script, and when I checked again under Linux and Windows it worked properly. Must have mispelled something, sorry for the noise. Whew! :) I'm just glad to hear it works now. The bug reports are really helpful, Christoph. Thanks! -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] CSSLink in the standalone tutorial does not work
On Wed, Jun 20, 2012 at 10:15:05PM +0200, Christoph Zwerschke wrote: When I follow the tutorial at http://tw2core.readthedocs.org/en/latest/standalone/ and add the line resources = [tw2.core.CSSLink(filename='myapp.css')] to the Movie form, I get the folling wrong link in the output link rel=stylesheet type=text/css href=/resources/__main__/myapp.css media=all / Christoph- I get the same link inserted but I believe it is correct. Is it giving you a 404 error? What version of tw2.core are you using? What version of python? And again, this is on windows? There may be a path error I'm not aware of like you found before. Best regards- -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Template engine extensions collision
Just for the record, Alessandro submitted a patch for this which was accepted. - https://github.com/toscawidgets/tw2.core/pull/33 -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Cannot import Genshi templates by filename
Christoph, thanks for reporting! I created an issue to track this here -- https://github.com/toscawidgets/tw2.core/issues/30 The feature should probably be re-introduced; it's removal was short-sighted on my part. Yours- -Ralph On Mon, Jun 11, 2012 at 02:43:07PM +0200, Christoph Zwerschke wrote: I noticed that since the template-sys branch has been merged in (see https://github.com/toscawidgets/tw2.core/commit/832435945ffcdcb5608225d38e7262d09c16ce01), loading Genshi templates does not work anymore via filenames (template = 'genshi:./index.html') as it is done in the tutorial here (http://tw2core.readthedocs.org/en/latest/standalone/). I get an Error - type 'exceptions.ImportError': Import by filename is not supported. Is this this functionality been removed deliberately? If yes, the tutorial should be adapted accordingly. -- Christoph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en. -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] tw2 and genshi xi:include href=imaster.html /
Hi Rene, This is just a shortcoming of my programming: sorry! In 2.1.0a, I blew away the old templating system and replaced it with a new, hopefully simplified one with support for new templating engines like jinja2, kajiki, and chameleon. I'll try and come up with a solution for you soon. Yours- -Ralph On Wed, Jun 06, 2012 at 01:36:54AM -0700, Rene van Paassen wrote: Hi, I am using tw2 in combination with bottle and genshi templates. tw2.core 2.0.0 worked for that set-up for tw2.core-2.1.0a4, I am getting trouble reading in an included genshi master template. I added my application's location to the python path, and using dotted notation, I can find the page-specific templates themselves. However, whatever I try to get the *included by genshi* master template read does not work. It used to work in the older tw2. The only think that helps is putting the included master template in the directory where I start up my program, which is an OK fix for now, but I would really like to know how to tell genshi -- when used in combination with tw2 -- where to look for included templates. The tw2 / genshi bit of the error log is: Module _session:*264* in loginpage http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#*return* UserLogin*.*req*(**)** .*display*(**)* Module tw2.core.widgets:*397* in display http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#*return* self*.*generate_output *(*displays_on*)* Module tw2.core.widgets:*434* in generate_output http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#mw*,* Module tw2.core.templating:*175* in render http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#*return* callback*(*kwargs*)* Module tw2.core.templating:*136* in lambda http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#''*.*join*(*tmpl*.*generate*(** ***kwargs*)**.*serialize*(*'xhtml'*)**)* Module genshi.template.base:*532* in generate http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#stream *=* self*.*stream Module genshi.template.base:*442* in stream http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#self*.*_stream *=* list*(*self* .*_prepare*(*self*.*_stream*)**)* Module genshi.template.base:*492* in _prepare http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#cls*=*cls *or* self*.*__class__ *)* Module genshi.template.loader:*246* in load http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#*raise* TemplateNotFound*(* filename*,* search_path*)* *TemplateNotFound: Template master.html not found* * * *Thanks*, Rene -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To view this discussion on the web visit https://groups.google.com/d/msg/toscawidgets-discuss/-/mX_r1IBtoPsJ. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en. -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] tw2 and genshi xi:include href=imaster.html /
I pushed a commit and another alpha release that should fix the issue for you: https://github.com/toscawidgets/tw2.core/commit/fc58e929ac6cd04eb3bb698eff9249f97b85d31c Please let us know if you're still having problems. Yours- -Ralph On Wed, Jun 06, 2012 at 01:36:54AM -0700, Rene van Paassen wrote: Hi, I am using tw2 in combination with bottle and genshi templates. tw2.core 2.0.0 worked for that set-up for tw2.core-2.1.0a4, I am getting trouble reading in an included genshi master template. I added my application's location to the python path, and using dotted notation, I can find the page-specific templates themselves. However, whatever I try to get the *included by genshi* master template read does not work. It used to work in the older tw2. The only think that helps is putting the included master template in the directory where I start up my program, which is an OK fix for now, but I would really like to know how to tell genshi -- when used in combination with tw2 -- where to look for included templates. The tw2 / genshi bit of the error log is: Module _session:*264* in loginpage http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#*return* UserLogin*.*req*(**)** .*display*(**)* Module tw2.core.widgets:*397* in display http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#*return* self*.*generate_output *(*displays_on*)* Module tw2.core.widgets:*434* in generate_output http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#mw*,* Module tw2.core.templating:*175* in render http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#*return* callback*(*kwargs*)* Module tw2.core.templating:*136* in lambda http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#''*.*join*(*tmpl*.*generate*(** ***kwargs*)**.*serialize*(*'xhtml'*)**)* Module genshi.template.base:*532* in generate http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#stream *=* self*.*stream Module genshi.template.base:*442* in stream http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#self*.*_stream *=* list*(*self* .*_prepare*(*self*.*_stream*)**)* Module genshi.template.base:*492* in _prepare http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#cls*=*cls *or* self*.*__class__ *)* Module genshi.template.loader:*246* in load http://localhost:8001/practicon/index# http://localhost:8001/practicon/index#*raise* TemplateNotFound*(* filename*,* search_path*)* *TemplateNotFound: Template master.html not found* * * *Thanks*, Rene -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To view this discussion on the web visit https://groups.google.com/d/msg/toscawidgets-discuss/-/mX_r1IBtoPsJ. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en. -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Scheduling new meeting time for Messaging SIG
The Messaging SIG has been meeting on Tuesdays at 16.00 UTC. Turnout has been a little low and we concluded that it's not the best time. If you're interested in participating in meetings, please fill out the following survey so I can get a good idea of when to place them: http://whenisgood.net/fedmsg For the curious, here's a list of the archived meeting logs: https://github.com/ralphbean/fedmsg/blob/develop/doc/meetings.rst -threebean -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Scheduling new meeting time for Messaging SIG
The Messaging SIG has been meeting on Tuesdays at 16.00 UTC. Turnout has been a little low and we concluded that it's not the best time. If you're interested in participating in meetings, please fill out the following survey so I can get a good idea of when to place them: http://whenisgood.net/fedmsg For the curious, here's a list of the archived meeting logs: https://github.com/ralphbean/fedmsg/blob/develop/doc/meetings.rst -threebean ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
[TW] Re: js_symbol/function/callback and mixed use of single/double quotes
On Monday, April 30, 2012 6:17:58 AM UTC-4, Rob wrote:
To use a really simple example:
twc.js_callback(function(row_
id) { myvar = row_id + '_t'; }) ## will work absolutely fine.
twc.js_callback(function(row_id) { myvar = row_id + \_t\ }) ##
note the escaped double-quotes, will not(!)
I wrote up some new tests and a patch that will hopefully fix this (without
breaking anything else!)
https://github.com/toscawidgets/tw2.core/pull/21
Robert, can you take a poke and see if it fixes the issue?
--
You received this message because you are subscribed to the Google Groups
ToscaWidgets-discuss group.
To view this discussion on the web visit
https://groups.google.com/d/msg/toscawidgets-discuss/-/3-Nzy5ksHL4J.
To post to this group, send email to toscawidgets-discuss@googlegroups.com.
To unsubscribe from this group, send email to
toscawidgets-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/toscawidgets-discuss?hl=en.
Seeking bold, intrepid package reviewers
The Messaging SIG has been working on building a messaging bus for Fedora Infrastructure and the main obstacle to testing stuff in our staging environment is a boatload of package reviews. If anyone is up to help, it would be much appreciated. I'm willing to swap reviews as well if you need a reviewer for yours. https://bugzilla.redhat.com/show_bug.cgi?id=811732 https://bugzilla.redhat.com/show_bug.cgi?id=811769 https://bugzilla.redhat.com/show_bug.cgi?id=811782 https://bugzilla.redhat.com/show_bug.cgi?id=812030 https://bugzilla.redhat.com/show_bug.cgi?id=811739 https://bugzilla.redhat.com/show_bug.cgi?id=811750 https://bugzilla.redhat.com/show_bug.cgi?id=812059 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Seeking bold, intrepid package reviewers
On Thu, May 03, 2012 at 10:33:20AM -0400, Neil Horman wrote: Just FYI, you probably want to set the fedora-review flag to '?' on those so they're more visible to potential reviewers Done. Thank you. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Seeking bold, intrepid package reviewers
On Thu, May 03, 2012 at 10:39:27AM -0400, Neil Horman wrote: On Thu, May 03, 2012 at 09:37:04AM -0500, Jon Ciesla wrote: On Thu, May 3, 2012 at 9:33 AM, Neil Horman nhor...@redhat.com wrote: Just FYI, you probably want to set the fedora-review flag to '?' on those so they're more visible to potential reviewers Neil No, you don't, that's set by the reviewer when the start the review, then + at approval. Yup, my bad. Okay. I just un-set the flag again. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Seeking bold, intrepid package reviewers
On Thu, May 03, 2012 at 09:03:54AM -0600, Jerry James wrote: On Thu, May 3, 2012 at 7:27 AM, Ralph Bean rb...@redhat.com wrote: If anyone is up to help, it would be much appreciated. I'm willing to swap reviews as well if you need a reviewer for yours. I offered a review swap a couple of days ago that nobody has taken me up on. Can you review these in exchange for me reviewing a couple of yours? Sure thing! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: List of needed package reviews for fedmsg to move forwards
On Thu, Apr 19, 2012 at 02:26:58PM -0400, Ralph Bean wrote: Here is the list of needed package reviews for fedmsg. - 810335 - 720818 - 811689 - 811732 - 811739 - 811750 - 811759 - 811769 - 811782 - 812030 - 812059 Sending out a plaintext list of the bug ids was probably not that helpful. Here's a friendlier link to the dependency tree for python-fedmsg so you can view them all at once: https://bugzilla.redhat.com/showdependencytree.cgi?id=818297hide_resolved=1 Even better, here are two links to the best next two tickets for review: https://bugzilla.redhat.com/show_bug.cgi?id=811689 https://bugzilla.redhat.com/show_bug.cgi?id=811759 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: [TW] js_symbol/function/callback and mixed use of single/double quotes
Hi Rob, I think you're right and odds are that it cannot be achieved with the current code in tw2.core. We should fix this. :) At your leisure, can you please fork http://github.com/toscawidgets/tw2.core and add one or two failing test cases to ``tests/test_js.py``? Submit a pull request with just the test(s) and then we can all use it as reference for a fix. Thanks, and Happy May Day! -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] js_symbol/function/callback and mixed use of single/double quotes
On Tue, May 01, 2012 at 02:35:51PM +0100, Robert Sudwarts wrote: ... had an unpleasant premonition that you'd say that ! :) Aww, I hope it's not *that* unpleasant. :) Cheers, and thanks again! -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Re: [TurboGears] TW2 FileField Validator evaluating False
Thanks for reporting this, Damien! And Alessandro, thanks for entering it into the issue tracker. -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
List of needed package reviews for fedmsg to move forwards
Here is the list of needed package reviews for fedmsg. - 810335 - 720818 - 811689 - 811732 - 811739 - 811750 - 811759 - 811769 - 811782 - 812030 - 812059 These ones are already done - 810033 - 810382 - 810386 These two are not package reviews, but are tickets that need to be resolved in order to move forwards with fedmsg in stg: - 813925 - 813915 All of the above are dependencies of the latest major version bump of Moksha. I haven't yet submitted the review request for python-fedmsg itself, but it's coming soon. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: [TW] SQLAjqGridWidget Add and Edit forms problem
Hi Puska, On Mon, Apr 16, 2012 at 02:40:06AM -0700, puska wrote: I am trying to use SQLAjqGridWidget in my forms, so i have started with Ralf Bean's example demo: tw2-tg2.1-genshi-demo. It is working, but Add and Edit buttons do not provide expected result, the pop-up forms do not have any fields (save and edit URLs are not defined yet, but I guess that add form should be populated with fields, and edit form with fields and values). I'm sorry to inform you that support for the add/edit/remove buttons just hasn't been written yet. It would be a really nice feature, if we could just find the time to finish it. https://github.com/toscawidgets/tw2.jqplugins.jqgrid/issues/1 -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Race condition with 'window-added' event and get_monitor()?
Hello all, I think I've encountered a race condition with the get_monitor() method of meta window. For context, I'm working on an extension called 'shellshape' and am running gnome 3.4.0. This specific issue is brought up here https://github.com/gfxmonk/shellshape/issues/21 It appears that in callbacks that fire off of the 'window-added' event of a workspace, the value returned by get_monitor is unreliable. I inconsistently get the wrong value back. The value is within the possible range of values (0, or 1 if I have two monitors registered) but the value returned doesn't always reflect which monitor the new window is actually on. If I delay the execution of the get_monitor method (with, say, Mainloop.timeout_add_seconds) then I always get the right answer back from get_monitor. At what point in the window's creation can we be assured that it is fully set up, or really, at what point can we be assured that the value returned by get_monitor is correct? Is this a bug? Or is it expected behavior and we're just using the wrong events? Cheers- -Ralph ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
[TurboGears] Re: jqgrid: classes in rows, reloading (plus caching a page)
Hi Craig,
On Feb 21, 3:56 am, Craig Small csm...@enc.com.au wrote:
The first is auto-updates. This table the grid uses for data is updated
in the backend so I'd like to be able to display the last n'th items
and update this every x seconds with the latest n'th. I've done this
previous with a html table and a javascript refresh which redraws the
entire page.
What widget are you using specifically?
tw2.jqplugins.jqgrid.jqGridWidget or
tw2.jqplugins.jqgrid.SQLAjqGridWidget ?
Secondly, is there a way of apply a class to a cell or row based upon
a database item?
Again, its working with a html table with:
tr class=rowtype${thing.type_id} ...etc
I then have a CSS file with rowtype1 rowtype2, rowtype3, etc
This is done because each row needs to be a certain colour based upon
type_id so all type_id==2 are blue etc
Is this possible with jqgrid? If so how?
The widget was not intended for this. You can try modifying the CSS
yourself once you have run the tw2 resource archiver (see below).
Finally, because I just remembered, is there a way of caching that CSS
file I generate? At the moment, each call to the database regenerates
the CSS document, which means an entire scan of the thing_type database
to pull out id,bgcolor and fgcolor. The table doesn't change much so
to me if I could cache it it would be better.
Yes. There is a distutils command that tw2 provides called
archive_tw2_resources. Try running:
$ python setup.py archive_tw2_resources --help
$ python setup.py archive_tw2_resources --force --output=/tmp/
my_resources --distributions=myapp
You'll then need to copy the contents of the /tmp/my_resources folder
into the public/ folder of your tg2 app.
Finally, turn off tw2 resource serving adding the following config to
the bottom of myapp/config/app_cfg.py
base_config.custom_tw2_config['serve_resources'] = False
--
You received this message because you are subscribed to the Google Groups
TurboGears group.
To post to this group, send email to turbogears@googlegroups.com.
To unsubscribe from this group, send email to
turbogears+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en.
[TurboGears] Re: Widgets and forms to use with TG2
On Feb 17, 11:19 am, Alessandro Molina alessandro.mol...@gmail.com wrote: Tw2 is preparing for stable status, in a few days there should be a bugfix sprint which will probably lead to a new beta release. TW2 maintainer here. The bugsprint is set for March 3rd and I'm hoping we can release the first non-beta 2.0 version of all major TW2 components at the end. One of the targets set for 2.2 release during the last TG meeting has been to switch to TW2 as the default widgets set in newly quickstarted projects. Alessandro, I wasn't aware that the TG team was planning on TW2 adoption. I'd like to help on this effort! -- You received this message because you are subscribed to the Google Groups TurboGears group. To post to this group, send email to turbogears@googlegroups.com. To unsubscribe from this group, send email to turbogears+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
Re: [TW] Re: problem with growing widget
Excerpts from NiL's message of Tue Jan 31 11:52:31 -0500 2012: the form itself should inherit from from tw.dynforms.widgets import CustomisedForm and voilà ! Good to hear you got it working! -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: Pyramid Simpleform and Colander
Hello all, I tried posting here the other day but I think googlegroups ate my post. We developed a solution to the BruceC's problem using tw2 over on toscawidgets-discuss. Here's a link here for future reference. http://groups.google.com/group/toscawidgets-discuss/browse_thread/thread/3c2b3fe45c872fe0 Cheers, Ralph Bean -- 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 pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: Pyramid Simpleform and Colander
Hi all, We found a solution that met the original poster's needs over on toscawidgets-discuss. Posting here for future googlers. http://groups.google.com/group/toscawidgets-discuss/browse_thread/thread/3c2b3fe45c872fe0 All the best, Ralph -- 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 pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: [TW] Re: How to manually render individual parts of a form
Hi Bruce, Thanks for pinging again; got a little backlogged this week. I think this is what you want:: In [1]: import tw2.forms as twf In [2]: class MyForm(twf.Form): ...: title = 'My Form!' ...: class child(twf.TableForm): ...: title = twf.TextField ...: director = twf.TextField ...: genres = twf.CheckBoxList(options=['numbah 1', 'numbah 2']) In [3]: MyForm.child.child.children.director.display() Out[3]: u'input id=director/' Is that sufficient for your needs? I'm also not sure that its clear how to do this in the documentation; I'm filing a ticket to shore this up. All the best, Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Re: How to manually render individual parts of a form
Excerpts from BruceC's message of Thu Jan 26 23:15:53 -0500 2012: Given that I've already spent some time posting to the Pyramid google- discuss site trying to see if the other packages can do this, you should mention something about this on the Pyramid google-discuss site if you update the TW2 docs about this... Cool. I'll go chime in on it. -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] How to manually render individual parts of a form
Hi BruceC,
Just for clarification, are you asking about toscawidgets2? (tw2?)
-Ralph
Excerpts from BruceC's message of Tue Jan 24 20:13:16 -0500 2012:
Hi all, can someone explain how you would go about rendering individual
parts of a form so I can customise the layout of my form? I can currently
render an entire form to my mako template using ${form.display() | n}. I am
looking to migrate an old Pylons app using a very old version of
ToscaWidgets where the context has a 'display_child' method allowing us to
display a specific form field in a specific position on the page, I need
to emulate this behaviour.
Cheers,
BruceC
--
You received this message because you are subscribed to the Google Groups
ToscaWidgets-discuss group.
To post to this group, send email to toscawidgets-discuss@googlegroups.com.
To unsubscribe from this group, send email to
toscawidgets-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] problems with refreshing an edit form
I lost the python formatting in your email. Can you send a .py attachment (or two?) Also, you say it doesn't refresh, can you be more specific? -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
[Catalog-sig] http://pypi.rit.edu
Hello, I have just setup http://pypi.rit.edu and would like to begin the process of reviewing it and registering it as a X.pypi.python.org mirror. I have not yet found any documentation on how to start that process, other than emailing this list. Yours- -Ralph ___ Catalog-SIG mailing list Catalog-SIG@python.org http://mail.python.org/mailman/listinfo/catalog-sig
[Catalog-sig] Registering http://pypi.rit.edu/ as http://X.pypi.python.org/
Hello, I have just setup http://pypi.rit.edu and would like to begin the process of reviewing it and registering it as a X.pypi.python.org mirror. I have not yet found any documentation on how to start that process, other than emailing this list. Yours- -Ralph ___ Catalog-SIG mailing list Catalog-SIG@python.org http://mail.python.org/mailman/listinfo/catalog-sig
Re: [TurboGears] sso federated identity
Hello jo, (Just a note: I have major trouble reading your email since its not plaintext, but is instead HTML formatted.) Although I don't use it, there is a package called repoze.who.plugins.saml2 https://launchpad.net/repoze.who.plugins.saml2 which is meant for this. It may fit your needs already. If you have success or failure with it, I'd love to hear about it. I plan on integrating it with my existing TG2 apps at some point in the future. Cheers- -Ralph Excerpts from jo's message of Tue Nov 08 06:50:39 -0500 2011: -- You received this message because you are subscribed to the Google Groups TurboGears group. To post to this group, send email to turbogears@googlegroups.com. To unsubscribe from this group, send email to turbogears+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
Re: [TW] The server toscawidget.org is down
That's terrible. Paul, J: if you need any help figuring out what's up, email me directly and maybe I can help. If any users out there need access to tw2 documentation in the meantime, it is cross-posted at http://tw2core.rtfd.org/ -Ralph Excerpts from Damien Accorsi's message of Fri Oct 21 08:14:16 -0400 2011: -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Optional templates
Dan,
It all sounds completely reasonable to me. I say go for it and do it.
If you could (where possible) add and modify unit tests to cover any changes
you make, that would be fantastic.
A line or two in the docs about the render(...) method would be great too. If
you don't have the time, resources, or ability to do that, just create a
ticket in bitbucket for it instead.
Thanks so much!
-Ralph
Excerpts from Daniel Lepage's message of Tue Oct 18 17:36:57 -0400 2011:
True, though if I understand Widget correctly display() does a lot
more than just creating the output string - I'd also have to rewrite
the code for automatic instance creation and resource management. Is
there any reason we couldn't add a separate render() method that just
does the templating, gets called by display(), and can be overridden
for pure-python rendering?
Also, while I'm poking around in Widget, why isn't validate a
class_or_instance method? I found myself needing to access some of the
data stored on the widget instance by validation, and had to seek out
the request_local validated widget to do so; it would be great if I
could create an instance to do it itself.
And finally, add_call looks broken - it's a class_or_instance method,
but will only work if used as an instance method.
If there's no reason why any of the above couldn't be done, I'd be
happy to make the changes myself and send someone a pull request.
--
Dan
On Tue, Oct 18, 2011 at 2:17 PM, Ralph Bean ralph.b...@gmail.com wrote:
Good point. You could override display(...) like this:
import tw2.forms as twf
import tw2.core.util
class MyWidget(twf.LabelField):
@tw2.core.util.class_or_instance
def display(cls, *args, **kwargs):
return #occupywallst
-Ralph
Excerpts from Daniel Lepage's message of Tue Oct 18 12:26:36 -0400 2011:
Even that still requires that you use a templating language - why not
allow the widget author to produce the output in pure python if they
want to?
class tw2.forms.Label(Widget):
def render_me(self):
return span + self.attrs + + self.text + /span
--
Dan
On Wed, Oct 12, 2011 at 9:10 AM, Ralph Bean ralph.b...@gmail.com wrote:
I think you've correctly described the current state of tw2.
In tw1, there was the option to specify the content of the template in
the
python module that defines your widget, like:
class tw2.forms.Label(Widget):
template =
%namespace name=tw module=tw2.core.mako_util/\
span ${tw.attrs(attrs=w.attrs)}${w.text}/span
I think this would be called inline templates, and it looks like
there's
already a ticket for it:
https://bitbucket.org/paj/tw2core/issue/69/inline-templates
I'm for it, we just have to implement it. :)
-Ralph
Excerpts from Daniel Lepage's message of Tue Oct 11 20:00:18 -0400 2011:
Is there a way to make widgets that don't have template files, but
just call python functions to render themselves? I ask because
templating sometimes seems like overkill.
For example, suppose for some reason I needed to reimplement
tw2.forms.Label, which has the following mako template:
%namespace name=tw module=tw2.core.mako_util/\
span ${tw.attrs(attrs=w.attrs)}${w.text}/span
and the following genshi template:
span xmlns:py=http://genshi.edgewall.org/; py:attrs=w.attrs
py:content=w.text /
I'd like instead to write a function:
def render(self):
return span
{attrs}{text}/span.format(attrs=tw.attrs(self.attrs),
text=self.text)
or, with something like Nagare's HTML renderer,
def render(self):
return h.span(self.text, attrs=tw.attrs(self.attrs))
and suddenly I don't need two extra files for the mako and genshi
templates, plus the widget would now work without either engine
installed.
AFAICT, though, the only way to do this is to overload the display
function entirely (and so copying the logic for resources, etc.); am I
missing something?
Thanks,
Dan Lepage
--
You received this message because you are subscribed to the Google
Groups ToscaWidgets-discuss group.
To post to this group, send email to
toscawidgets-discuss@googlegroups.com.
To unsubscribe from this group, send email to
toscawidgets-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/toscawidgets-discuss?hl=en.
--
You received this message because you are subscribed to the Google Groups
ToscaWidgets-discuss group.
To post to this group, send email to toscawidgets-discuss@googlegroups.com.
To unsubscribe from this group, send email to
toscawidgets-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/toscawidgets-discuss?hl=en.
--
You received
[TW] tw2.rrd demo works now.
Hello all, It took some work, but the tw2.rrd demo works now up at: http://tw2-demos.threebean.org/module?module=tw2.rrd -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Date format problem with TW DynForms and CalendarDatePicker
Hello Damien, Are you using tw1 (as in `tw.api`) or tw2 (as in `tw2.core`)? Can you clarify? Also, if you could send emails in plaintext that would be much appreciated. Cheers- -Ralph Excerpts from Damien Accorsi's message of Tue Oct 18 13:49:01 -0400 2011: -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Date format problem with TW DynForms and CalendarDatePicker
I'm afraid I only work with tw2 and so can't answer any questions or figure out a fix. There are others on this list that work with tw1 though -- they should chime in soon. -Ralph Excerpts from Damien Accorsi's message of Tue Oct 18 14:01:30 -0400 2011: Hello Ralph, I'm using tw1 (below are the related modules I use): ToscaWidgets-0.9.11-py2.6.egg tw.forms-0.9.9-py2.6.egg tw.dynforms-0.9.8-py2.6.egg Damien On 10/18/2011 07:57 PM, Ralph Bean wrote: Hello Damien, Are you using tw1 (as in `tw.api`) or tw2 (as in `tw2.core`)? Can you clarify? Also, if you could send emails in plaintext that would be much appreciated. Cheers- -Ralph Excerpts from Damien Accorsi's message of Tue Oct 18 13:49:01 -0400 2011: -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Optional templates
Good point. You could override display(...) like this:
import tw2.forms as twf
import tw2.core.util
class MyWidget(twf.LabelField):
@tw2.core.util.class_or_instance
def display(cls, *args, **kwargs):
return #occupywallst
-Ralph
Excerpts from Daniel Lepage's message of Tue Oct 18 12:26:36 -0400 2011:
Even that still requires that you use a templating language - why not
allow the widget author to produce the output in pure python if they
want to?
class tw2.forms.Label(Widget):
def render_me(self):
return span + self.attrs + + self.text + /span
--
Dan
On Wed, Oct 12, 2011 at 9:10 AM, Ralph Bean ralph.b...@gmail.com wrote:
I think you've correctly described the current state of tw2.
In tw1, there was the option to specify the content of the template in the
python module that defines your widget, like:
class tw2.forms.Label(Widget):
template =
%namespace name=tw module=tw2.core.mako_util/\
span ${tw.attrs(attrs=w.attrs)}${w.text}/span
I think this would be called inline templates, and it looks like there's
already a ticket for it:
https://bitbucket.org/paj/tw2core/issue/69/inline-templates
I'm for it, we just have to implement it. :)
-Ralph
Excerpts from Daniel Lepage's message of Tue Oct 11 20:00:18 -0400 2011:
Is there a way to make widgets that don't have template files, but
just call python functions to render themselves? I ask because
templating sometimes seems like overkill.
For example, suppose for some reason I needed to reimplement
tw2.forms.Label, which has the following mako template:
%namespace name=tw module=tw2.core.mako_util/\
span ${tw.attrs(attrs=w.attrs)}${w.text}/span
and the following genshi template:
span xmlns:py=http://genshi.edgewall.org/; py:attrs=w.attrs
py:content=w.text /
I'd like instead to write a function:
def render(self):
return span
{attrs}{text}/span.format(attrs=tw.attrs(self.attrs),
text=self.text)
or, with something like Nagare's HTML renderer,
def render(self):
return h.span(self.text, attrs=tw.attrs(self.attrs))
and suddenly I don't need two extra files for the mako and genshi
templates, plus the widget would now work without either engine
installed.
AFAICT, though, the only way to do this is to overload the display
function entirely (and so copying the logic for resources, etc.); am I
missing something?
Thanks,
Dan Lepage
--
You received this message because you are subscribed to the Google Groups
ToscaWidgets-discuss group.
To post to this group, send email to toscawidgets-discuss@googlegroups.com.
To unsubscribe from this group, send email to
toscawidgets-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/toscawidgets-discuss?hl=en.
--
You received this message because you are subscribed to the Google Groups
ToscaWidgets-discuss group.
To post to this group, send email to toscawidgets-discuss@googlegroups.com.
To unsubscribe from this group, send email to
toscawidgets-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Deferred Params -- A question!
Okay, I'll remove all references to it and get ready to kick a release. I'll pull in your UnicodeMultiDict commit as well and fix up any tests before I push to pypi. -Ralph Excerpts from Paul Johnston's message of Sun Oct 09 08:07:17 -0400 2011: Hi, Most all of the speedup would come from a variant of this commit: https://bitbucket.org/ralphbean/tw2core/changeset/62f22632b61b Surprised that speeds it up much, as the change is only in post_define, which should only be called at program startup, not when servicing requests. I saw a 'huge' speedup after I introduced it this Spring. It makes the difference between tw2 being faster than tw1 and not. Well, that is a good case for removing them. Anything you can do with Deferred, you can also do by overriding prepare() on the class. However, I don't use deferred params anywhere and I didn't realize that this commit breaks the way they're supposed to work. Yeah, I think it breaks because dir(cls) picks up all the members of base classes, while cls.__dict__ only gets ones defined on that actual class, not its bases. We need more unit tests (still). For sure. Hope you're keeping well with the baby! Are you getting much sleep? Paul -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Deferred Params -- A question!
Oh, and the baby's doing great! :) Sleeping more, finally! Here's a pic! http://www.flickr.com/photos/65490292@N04/6242126232/in/photostream/lightbox/ And your little one? Doing well? Excerpts from Paul Johnston's message of Sun Oct 09 08:07:17 -0400 2011: Hi, Most all of the speedup would come from a variant of this commit: https://bitbucket.org/ralphbean/tw2core/changeset/62f22632b61b Surprised that speeds it up much, as the change is only in post_define, which should only be called at program startup, not when servicing requests. I saw a 'huge' speedup after I introduced it this Spring. It makes the difference between tw2 being faster than tw1 and not. Well, that is a good case for removing them. Anything you can do with Deferred, you can also do by overriding prepare() on the class. However, I don't use deferred params anywhere and I didn't realize that this commit breaks the way they're supposed to work. Yeah, I think it breaks because dir(cls) picks up all the members of base classes, while cls.__dict__ only gets ones defined on that actual class, not its bases. We need more unit tests (still). For sure. Hope you're keeping well with the baby! Are you getting much sleep? Paul -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Re: TW2 Installation problem with webob v1.2b1
That was me! The code was from http://bitbucket.org/ralphbean/tw2core When I tried to merge in your repo, tests started failing. Re-trying that now. Excerpts from Paul Johnston's message of Sun Oct 16 04:51:46 -0400 2011: Hi, And just to follow up on myself one more time... Who did the 2.0b8 release to PyPI on 7 Oct? Which repository was the code for this release taken from? I notice the release number does match that checked-in to https://bitbucket.org/paj/tw2core/ Paul On Sun, Oct 16, 2011 at 9:47 AM, Paul Johnston p...@pajhome.org.uk wrote: Hi, I've just removed the references - simple change. In fact, we should do a PyPI release ASAP, as it's important that tw2 works correctly when you follow the tutorial. Paul -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Re: TW2 Installation problem with webob v1.2b1
Paul- Three tests still fail post-merge for me. They're related to the Controller stuff that was being juggled at the beginning of the summer. Can you fix the tests (or tw2.core) so that they pass? I'm afraid of un-fixing anything you've added. Let me know; we can re-merge and do a release. -Ralph Excerpts from Ralph Bean's message of Sun Oct 16 10:08:07 -0400 2011: That was me! The code was from http://bitbucket.org/ralphbean/tw2core When I tried to merge in your repo, tests started failing. Re-trying that now. Excerpts from Paul Johnston's message of Sun Oct 16 04:51:46 -0400 2011: Hi, And just to follow up on myself one more time... Who did the 2.0b8 release to PyPI on 7 Oct? Which repository was the code for this release taken from? I notice the release number does match that checked-in to https://bitbucket.org/paj/tw2core/ Paul On Sun, Oct 16, 2011 at 9:47 AM, Paul Johnston p...@pajhome.org.uk wrote: Hi, I've just removed the references - simple change. In fact, we should do a PyPI release ASAP, as it's important that tw2 works correctly when you follow the tutorial. Paul -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] TW2 Installation problem with webob v1.2b1
When you created the virtualenv 'crest', did you use --no-site-packages?
Excerpts from Rob's message of Sat Oct 15 11:35:41 -0400 2011:
Hi,
I'm having a problem installing/using tw2 with the latest dependencies
(pip install tw2.dynforms tw2.devtools tw2.sqla genshi elixir) the
method as recommended in the documentation.
It appears that webob.multidict.UnicodeMultiDict is somehow broken/
missing. As webob is a dependency which is further up the
'tree' (using the prescribed pip install) , is there any procedure by
which I can install using an earlier version of webob?
Many thanks,
Rob
The full traceback given when trying to load the widget browser:
Traceback (most recent call last):
File /home/robertsudwarts/.virtualenvs/crest/bin/paster, line 8,
in module
load_entry_point('PasteScript==1.7.3', 'console_scripts', 'paster')
()
File /home/robertsudwarts/.virtualenvs/crest/lib/python2.6/site-
packages/PasteScript-1.7.3-py2.6.egg/paste/script/command.py, line
83, in run
command = commands[command_name].load()
File /home/robertsudwarts/.virtualenvs/crest/lib/python2.6/site-
packages/setuptools-0.6c11-py2.6.egg/pkg_resources.py, line 1954, in
load
File /home/robertsudwarts/.virtualenvs/crest/lib/python2.6/site-
packages/tw2/devtools/__init__.py, line 1, in module
from server import dev_server
File /home/robertsudwarts/.virtualenvs/crest/lib/python2.6/site-
packages/tw2/devtools/server.py, line 1, in module
import tw2.core as twc
File /home/robertsudwarts/.virtualenvs/crest/lib/python2.6/site-
packages/tw2/core/__init__.py, line 11, in module
from widgets import (Widget, CompoundWidget, RepeatingWidget,
File /home/robertsudwarts/.virtualenvs/crest/lib/python2.6/site-
packages/tw2/core/widgets.py, line 2, in module
import template, core, util, validation as vd, params as pm
File /home/robertsudwarts/.virtualenvs/crest/lib/python2.6/site-
packages/tw2/core/validation.py, line 9, in module
webob.UnicodeMultiDict = webob.multidict.UnicodeMultiDict
AttributeError: 'module' object has no attribute 'UnicodeMultiDict'
--
You received this message because you are subscribed to the Google Groups
ToscaWidgets-discuss group.
To post to this group, send email to toscawidgets-discuss@googlegroups.com.
To unsubscribe from this group, send email to
toscawidgets-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/toscawidgets-discuss?hl=en.
[TW] Deferred Params -- A question!
Is anyone using 'Deferred' attributes on their custom widgets? I would like to remove them for the purposes of optimization. They are used currently in tw2.dynforms, but I can write around it easily. -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Widgets Browser
Fixed it this morning. :) Thanks! Excerpts from Rodrigo Ferreira de Souza's message of Fri Sep 30 07:51:38 -0400 2011: Hi everyone, The widgets browser is showing some errors.. http://tw2-demos.threebean.org/ Server Error URL: http://tw2-demos.threebean.org/module?module=tw2.dynforms Module weberror.errormiddleware:162 in __call__ app_iter = self.application(environ, sr_checker) Module tw2.core.middleware:159 in __call__ resp = self.controllers(req) Module tw2.core.middleware:201 in __call__ resp = widget.request(req) Module tw2.core.widgets:786 in request resp.body = ins.display().encode(core.request_local()['middleware'].config.encoding) Module tw2.core.widgets:271 in display self.prepare() Module tw2.devtools.browser:50 in prepare super(WbPage, self).prepare() Module tw2.core.widgets:742 in prepare self.child.prepare() Module tw2.devtools.browser:162 in prepare twc.DisplayOnlyWidget.prepare(self) Module tw2.core.widgets:742 in prepare self.child.prepare() Module tw2.devtools.browser:204 in prepare twc.RepeatingWidget.prepare(self) Module tw2.core.widgets:620 in prepare c.prepare() Module tw2.devtools.browser:137 in prepare self.demo.prepare() Module tw2.dynforms.widgets:189 in prepare super(CalendarDatePicker, self).prepare() Module tw2.core.widgets:206 in prepare value = self.validator.from_python(value) Module tw2.core.validation:387 in from_python return value and value.strftime(self.format) or '' AttributeError: 'Deferred' object has no attribute 'strftime' -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Toscawidgets without Elixir
Hi all, Rodrigo and I discussed this in IRC ( #toscawidgets ) this morning. The relevant code is: # Set the query property for all sqlalchemy models DeclarativeBase.query = DBSession.query_property() Cheers- -Ralph Excerpts from Rodrigo Ferreira de Souza's message of Fri Sep 30 07:46:47 -0400 2011: can someone put this code into toscawidgets 2 docs? On Fri, Sep 30, 2011 at 8:37 AM, Rodrigo Ferreira de Souza rodfer...@gmail.com wrote: is it this one http://tools.cherrypy.org/wiki/SQLA ? On Fri, Sep 30, 2011 at 8:35 AM, Rodrigo Ferreira de Souza rodfer...@gmail.com wrote: Hi Paul, Could you please send me this code? I can't find it... Since now, thanks, Rodrigo On Tue, Sep 27, 2011 at 6:12 PM, Christoph Zwerschke c...@online.de wrote: Am 27.09.2011 22:36, schrieb Paul Johnston: If using declarative base, you can add session.query_property to the base class. The TurboGears 2 tutorial used to do this, although I've just seen it doesn't now. The code for adding the query property is also in the quickstarted TG 2 model package, but commented out. -- Christoph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en. -- Atenciosamente, Rodrigo Ferreira de Souza python -c print ''.join([chr(154 - ord(c)) for c in 'H+6(13+zT5((51(9z65zG+% 9zmz(+645(\'+%Z3-91.l7+-']) -- Atenciosamente, Rodrigo Ferreira de Souza python -c print ''.join([chr(154 - ord(c)) for c in 'H+6(13+zT5((51(9z65zG+% 9zmz(+645(\'+%Z3-91.l7+-']) -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
[TW] Readthedocs.org
Toscawidgets2 is up on readthedocs.org now. http://readthedocs.org/docs/tw2core/en/latest/ -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Re: Widget.request
Paul, if that's the case I'd like to throw out a proposal to move to github and away from mercurial. The basis of my argument is only one of preference. Nobody else seems to be down with this. I'll drop it. Onwards! -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Re: Widget.request
I'm planning on decomissioning my bitbucket repositories and using the toscawidgets ones. Paul, if that's the case I'd like to throw out a proposal to move to github and away from mercurial. The basis of my argument is only one of preference. Anybody else out there care to cast a vote? -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] tw2.sqla
Hi Paul,
The {from,to}_dict stuff looks great. That stuff's been a bane.
In checking it over, I noticed that the changes you made in your
windows/python2.5-fix broke some of the tests on my end.
Specifically the removal of `name=something`:
https://bitbucket.org/paj/tw2.sqla/changeset/70437e1a72af#chg_tests/test_widgets.py_oldline100
-Ralph
--
You received this message because you are subscribed to the Google Groups
ToscaWidgets-discuss group.
To post to this group, send email to toscawidgets-discuss@googlegroups.com.
To unsubscribe from this group, send email to
toscawidgets-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Widget.request
I wrote before I looked. The request method stuff I was referring to *is* documented here: http://toscawidgets.org/documentation/tw2.core/history.html#widget-controller-methods I think what Paul was referring to is (pretty obviously if I just read more carefully) this: https://bitbucket.org/paj/tw2core/src/31d2b21271da/tw2/core/widgets.py#cl-353 Rethinking, now I agree that factoring this stuff out of the base widget is a good idea. It could easily be kept close at hand for people who need it with a tw2.core:ObjectDispatchMixin or something. -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Re: Widget.request
Thanks for adding in, Chris. It's good to know that's out there for coming revisions to tw2. -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
[TW] The State of Toscawidgets 2 (Issue #2)
All the stuff from the last status update is still standing. :) http://groups.google.com/group/toscawidgets-discuss/browse_thread/thread/e13af6f62464e54e?pli=1 Here's what I've been up to since then:: - Tests are being run nightly, you can see the output at http://tw2-tests.threebean.org. Now we're on the hook the write good tests. - Demos site moved from http://craftsman.rc.rit.edu to http://tw2-demos.threebean.org - I updated the frontpage documentation for tw2.core and corrected/added tutorials for tw2-standalone, tw2 with turbogears, and tw2 with pyramid. I also added an extra section that shows how to use tw2.jqplugins.jqgrid.SQLAjqGridWidget in each case. Also added external links to my tutorials. - Bugfixes - Fixed sundry bugs in tw2.sqla - Changed the way tw2.sqla looks for the sqlalchemy session for compatibility with pyramid. - Exposed useful stuff at a 'lower' namespace in tw2.jquery. - Applied Teemu's Cache-Control patch for tw2.core - Enhancements - Resource dependencies. You can now specify something like:: foo = twc.JSLink(...) bar = twc.JSLink(..., resources=[foo]) and `foo` will be included on the page before `bar`. Crucial. - tw2.devtools craziness. Put options in place now to scrape bitbucket and github for commits and pypi for downloads. It is disabled by default and controlled with command line switches. This is viewable at http://tw2-demos.threebean.org - New package: tw2.rrd -- the http://tw2-demos.threebean.org example is down, but you can see it in action on another project at http://narcissus.rc.rit.edu/ If you do round-robin database stuff anywhere, it might be useful for you. I would really appreciate:: - Some +1's from people to do minor releases of tw2.core, tw2.sqla, and tw2.jquery. The pypi versions currently break the tests of other libraries. I have the rights to do this, but would like to first put it to all of you. - A sphinx-build/push of the documentation changes to the toscawidgets.org site, please. Here's what next to do:: - ``archive_tw_resources`` and ``aggregate_tw_resources`` paster commands. This is a blocker for production for a lot of people. - More test coverage. - Client side validation. Should we use jquery here? - Authorization hooks. I don't call dibs on any of those. I'm having a baby in a month! :) Cheers- -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TurboGears] Re: making tw2.jit working
I also have not tried it in the shell, but to make it work in the full stack, you have to tell TurboGears explicitly to add the tw2 middleware by adding base_config.use_toscawidgets2 = True to the file yourapp/config/app_cfg.py -- You received this message because you are subscribed to the Google Groups TurboGears group. To post to this group, send email to turbogears@googlegroups.com. To unsubscribe from this group, send email to turbogears+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
Re: [TW] TW2 with TG2 -- default resource injection
Hi Matt, Michael-- Sorry it took me a minute to get back to you. Busy, busy. The short answer is to issue either option 1: jquery_js.req().prepare() or option 2: jquery_js.display() The long answer involves __metaclass__ magic. TW2 widgets (and resources) have their __new__ method overridden to return, not an instance of a class as you'd expect, but a new subclass of the original class. (That's where the '_s' comes from). Invoking .req() *actually* instantiates the widget like __new__ usually does. From a design point of view, the '.req()' method should really be hidden from users. The motivation is: during a request, we want to avoid instantiating any widgets until we know they are actually going to be displayed on the page in order to reduce wasted processing and overhead. Thus, usually inside your application's templates, the .display() classmethod internally calls self.req() (and later self.prepare()) Either of the above two options work. The first does only what's necessary, while the second generates some marginal overhead, but doesn't involve you invoking .req() yourself. Definitely don't get in the habit of doing the first for most widgets. The added benefit of delaying widget instantiation comes with the danger of complexity and broken idioms. Cheers- -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] tw2.jqplugins css
Not sure, Matt. I've never had to deal with this yet. Here are three ideas. One way could be to make all of your site-css stuff into tw2 resources. This is lame, though. tw2 shouldn't force its terms onto whoever its playing with. Alternatively, tw2 Resources have a 'location' parameter that can take on any of the following values: 'head', 'headbottom', 'bodytop', or 'bodybottom'. Most CSSLinks default to location='head', thus putting them at the top and above your site css. You could try overriding all resources in all your widgets with some kind of mixin class like this (warning: I haven't tested or tried this...): class HeadBottomMixin(twc.Widget): @classmethod def post_define(cls): cls.resources = [r(location='headbottom') for r in cls.resources] class MyFixedWidget(MyWidget, HeadBottomMixin): pass Thirdly, we could write some hook into tw2.jquery that will make this transparent to tw2 users. I'll need to think about it more before I come up with anything. Got any good ideas? :) Cheers- -Ralph -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TW] Re: tw2: unit testing forms validation
Try finishing with: field = vectx.widget.child.children[0] self.failUnless(Enter a value == field.error_msg) -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TurboGears] tw2.jquery
Hi Matt, The super-short answer is: it happens right here! https://bitbucket.org/ralphbean/tw2core/src/7ea2e037772b/tw2/core/middleware.py#cl-155 The longer answer is, in order for a /resources/ resource to get registered with the middleware and then be served (there), it needs to go through the injection process. Make sure you list it as one of the `resources` of one of your Widgets, and make sure that Widget gets its code.display()/code method called in one of your templates. If that fails you, I'll need to know more about your setup: what more specifically are you trying to do? Can you paste us the relevant code? Cheers- -Ralph -- You received this message because you are subscribed to the Google Groups TurboGears group. To post to this group, send email to turbogears@googlegroups.com. To unsubscribe from this group, send email to turbogears+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
Re: [TurboGears] tw2.jquery
I'm lost as to what the problem could be. Here's an example of a working project that uses the tw2.jqplugins.jqgrid widgets in a tg2.1 app with genshi templates. https://github.com/ralphbean/tw2-tg2.1-genshi-demo/commits/master Maybe you can compare that with what you've done to find the issue? -- You received this message because you are subscribed to the Google Groups TurboGears group. To post to this group, send email to turbogears@googlegroups.com. To unsubscribe from this group, send email to turbogears+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
Re: [TW] ToscaWidgets Website
Yes, it looks to be down for me too. I'll email paj directly. On Thu, May 26, 2011 at 12:57:59AM -0700, Jurgens de Bruin wrote: Hi, Is the ToscaWidgets Website down? -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en. -- RJ Bean -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
[TurboGears] Tutorial -- tw2 jqgrid, jqplot, and portlets with TG2.1
Hello all, I wrote up a tutorial yesterday on combing different toscawidgets2 (tw2) widgets in a quickstarted TG2.1 app and thought I'd share it here: http://threebean.wordpress.com/2011/04/30/tutorial-melting-your-face-off-with-tw2-and-turbogears2-1/ Cheers- -Ralph -- You received this message because you are subscribed to the Google Groups TurboGears group. To post to this group, send email to turbogears@googlegroups.com. To unsubscribe from this group, send email to turbogears+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
[TW] The State of Toscawidgets 2
Greetings all- Pretty quiet on this list so I thought I'd chime in with what I've been up to. 1) tw2 speed tests:: I wrote and ran some benchmarks. The output is listed in the README file (rendered by github) on the project page here. tw2 looks good! http://github.com/ralphbean/tw2-benchmark I wrote a note with a link to the above to the core developer of EasyWidgets asking for any input on how to most effectively use his package (so there may be updates to those tests coming soon). Pending that, I plan to release a writeup on my blog. 2) My tw2.*:: I've been pretty busy over the past year building tw2 extras. You can see the full list on my github account (along with a bunch of other stuff) and you can see a WidgetBrowser list of live demos here: http://craftsman.rc.rit.edu Be warned, that is running on an oh-so-slow virtualmachine that doesn't do tw2 justice. In particular, I'd like to advertise:: - tw2.jit.SQLARadialGraph - tw2.jqplugins.jqgrid.SQLAjqGridWidget Both of them do some fancy stuff with sqlalchemy. They should snap-in flawlessly with any project you have going on. I've got some tutorials on how to use the first of the two with both Turbogears 2.1 and Pyramid on my blog at http://threebean.wordpress.com 3) tw2.sqla I put a bunch of work in and got from 0% to 100% test coverage on tw2.sqla. My repo is located at:: http://bitbucket.org/ralphbean/tw2.sqla It interoperates 100% with elixir without ever explicitly referencing it(!) 4) The most epic merge of my life -- tw2.core (!) I braved merge-hell. When I started working on tw2 almost one summer ago, I stumbled into cloning paj's repo from bitbucket.org only to find out much later that things had diverged between his and the 'toscawidgets' repos. I took it upon myself today to make a merge happen. 100 % of tests pass and my merged repo is located on my bitbucket account at:: http://bitbucket.org/ralphbean/tw2core I made some executive decisions in the process that are certainly up for review. Let's do it (review it)! Here's why: tw2 rocks. I've built a lot of great widgets on it and have a number of apps done/in-the-works that depend on it. In one case especially (the fantastic `moksha` project), depending on my tw2 stuff requires packaging tw2 as rpms for Fedora and RHEL but IMHO, we cannot move forward with that as long as our repos aren't unified and in quite a confusing state for new users/developers to stumble into. I look forward to debating out which features (if any) should be pruned/added. 5) Looking forward -- Documentation and Test Coverage The documentation for the core packages is 'good' but needs real work around the TG2.1 tutorial. Additionally, we should add a Pyramid tutorial. I'm willing to take this on. We should have a link in the documentation as well to auto-generated reports of the `coverage` tool to 1) advetise the robustness of tw2 and 2) find out where we need to write more tests to shore ourselves up. I'm also willing to take this on. Cheers- -Ralph Bean -- You received this message because you are subscribed to the Google Groups ToscaWidgets-discuss group. To post to this group, send email to toscawidgets-discuss@googlegroups.com. To unsubscribe from this group, send email to toscawidgets-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/toscawidgets-discuss?hl=en.
Re: [TurboGears] Looking To Switch To New Server
A quick link to checkout and/or browse the TG 2.1 sourcecode would also be appreciated! -- You received this message because you are subscribed to the Google Groups TurboGears group. To post to this group, send email to turbogears@googlegroups.com. To unsubscribe from this group, send email to turbogears+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
Re: [TurboGears] Advice needed for putting together Python web dev system
Am 14.04.2011 um 02:00 schrieb pythy: I'm leaning toward Jython dev in eclipse. My db of choice is PostgreSQL. Looking for html templates that are as easy to use as php. I understand that TG is not entirely compatible with Jython, but that there are some workarounds. The book mentions the 'Hibernate' ORM, which I'm also leaning towards. But, the only thing I'm really married to at this point is PgSQL as backend, and some flavor of Python. Diez is right, trying to mix in Jython without a particular need will get in your way. My first web programming experience was in Java (J2EE?) with the Spring framework and the Hibernate ORM. Since then I've moved to pure-python and TurboGears 2.1 and its been much for the better. In python-land, the best of breed ORM is sqlalchemy: http://www.sqlalchemy.org/ It blows my mind (in the good way) at least once a week. With sqlalchemy (and most ORMs) your DB implementation (Postgre, MySQL, sqlite, etc..) is actually hidden from you. My sqlalchemy code for my projects can talk to just about any DB backend I point it at. This is cool because you can get an idea, develop rapidly on a sqlite database without worrying about setting up a production DB, and only later when the idea is proven worthy redirect your app at a more solid database implementation. As for templates, there are more python templating languages than I can list. I use `mako` templates because they feel less restrictive to write. Mostly preference here. Speed is an issue, too: http://stackoverflow.com/questions/1324238/what-is-the-fastest-template-system-for-python -- You received this message because you are subscribed to the Google Groups TurboGears group. To post to this group, send email to turbogears@googlegroups.com. To unsubscribe from this group, send email to turbogears+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
