This RT extension provides a calendar view for your tickets and your
reminders so you see when is your next due ticket. You can find it in
the menu Search->Calendar.
There's a portlet to put on your home page (see Prefs/MyRT.html)
You can also enable ics (ICal) feeds for your default calendar and all
your private searches in Prefs/Calendar.html. Authentication is magic
number based so that you can give those feeds to other people.
You can find screenshots on
http://gaspard.mine.nu/dotclear/index.php?tag/rtx-calendar
STF::Dispatcher::PSGI implements the basic STF Protocol
(http://stf-storage.github.com) dispatcher component. It does not know
how to actually store or retrieve data, so you must implement that
portion yourself.
The reason this exists is mainly to allow you to testing systems that
interact with STF servers. For example, setting up the main STF
implementation is quite a pain if all you want to do is to test your
application, but with this module, you can easily create a dummy STF
dispatcher.
The Google API Client for Python is a client library for accessing
the adexchangebuyer, adexchangeseller, adsense, adsensehost, analytics,
androidpublisher, audit, bigquery, blogger, books, calendar, civicinfo,
compute, coordinate, customsearch, dfareporting, discovery, drive,
freebase, fusiontables, gan, groupsmigration, groupssettings, latitude,
licensing, oauth2, orkut, pagespeedonline, plus, prediction, reseller,
shopping, siteVerification, storage, taskqueue, tasks, translate,
urlshortener, webfonts, youtube, youtubeAnalytics APIs.
If you wish to use a Google API that is not in that list then you should
look at the Google Data APIs Python Client Library (devel/py-gdata).
Active Resource
Active Resource attempts to provide a coherent wrapper object-relational
mapping for REST web services. It follows the same philosophy as
Active Record, in that one of its prime aims is to reduce the amount of
code needed to map to these resources. This is made possible by relying
on a number of code- and protocol-based conventions that make it easy for
Active Resource to infer complex relations and structures.
These conventions are outlined in detail in the documentation
for ActiveResource::Base.
Active Resource
Active Resource attempts to provide a coherent wrapper object-relational
mapping for REST web services. It follows the same philosophy as
Active Record, in that one of its prime aims is to reduce the amount of
code needed to map to these resources. This is made possible by relying
on a number of code- and protocol-based conventions that make it easy for
Active Resource to infer complex relations and structures.
These conventions are outlined in detail in the documentation
for ActiveResource::Base.
net-http-persistent manages persistent connections using Net::HTTP plus a speed
fix for Ruby 1.8. It's thread-safe too! Using persistent HTTP connections can
dramatically increase the speed of HTTP. Creating a new HTTP connection for
every request involves an extra TCP round-trip and causes TCP congestion
avoidance negotiation to start over. Net::HTTP supports persistent connections
with some API methods but does not handle reconnection gracefully.
Net::HTTP::Persistent supports reconnection and retry according to RFC 2616.
RG: https://rubygems.org/gems/net-http-persistent
YSlow analyzes web pages and tells you why they're slow based on Yahoo's
rules for high performance web sites.
YSlow gives you:
* Performance report card
* HTTP/HTML summary
* List of components in the page
* Tools including JSLint
Most files comprising YSlow are licensed under the Mozilla Public License
(MPL) version 1.1, with a couple of exceptions. YSlow includes jslint by
Douglas Crockford, which is licensed under a BSD-style license. YSlow also
includes files from the Yahoo! User Interface library, which are licensed
under the BSD license.
Rodent is a fast, small and powerful file manager for the
GNU operating system (but it also works in BSD). That's one
way to look at it. Another way is to call it a graphic shell
(that's probably more accurate).
* Rodent wastes no space on menus or function buttons (display
real estate is too valuable).
* All functionality is available through popup menu or keyboard
action.
* Popup menu is context sensitive.
* Full lpterminal is available from keyboard.
* Functionality is extendible via plugin technology.
UW ttyp0 is a family of bitmap screen fonts in bdf format. It covers most of
the Latin and Cyrillic alphabet, Greek, Armenian, Georgian (only Mkhedruli),
Hebrew (without cantillation marks), Thai, most of IPA (but no UPA), standard
punctuation, common symbols, some mathematics, line graphics, a few dingbats,
and Powerline delimiter symbols. In addition to Unicode (ISO 10646-1), UW ttyp0
supports about thirty 8-bit encodings (code pages).
UW ttyp0 comes in nine sizes from 6x11 to 11x22. In all of the sizes there are
regular and bold versions; for some there is also an italic.
SoXt is an open source implementation of the SGI InventorXt library,
which is a GUI binding for using Open Inventor with Xt/Motif. While
SoXt has been developed for use with Coin, it is also possible to
compile it against Open Inventor from SGI or TGS. A goal is to
eventually become 100% source code compatible with the InventorXt
library, which is still way off, especially when it comes to creating
derived classes.
When using SoXt, bear in mind that SoXt is in its alpha release
phase, so expect the worst...