Italian
Flatbread
Monterey Cheddar
Italian Herbcheese
Grain Wheat
Honey Oat
Beef
Chicken
Pork
Cheddar
Swiss
Mozzarella
Blue
Gouda
Lettuce
Tomato
Cucumber
Spinach
Avocado
Pickle
Banana
Mushroom


In order to finalize claim of your {{claim.amount}} FIC to this wallet one final step is required - sending a claim request to smart contract from your whitelisted ETH address.
{{ 'from_address' | translate }}
{{formData.address}}
{{ 'send_to' | translate }}
{{contractAddress}}
{{ 'payload' | translate }}
{{formData.payload}}
Note: Keep Amount to Send 0 ETH or otherwise your claim request will be denied and you will have to retry.


Array
Once you’ve matched a list of elements, you will often need to handle them as a group. Or you may want to perform the same action on each of them. Hpricot::Elements is an extension of Ruby’s array class, with some methods added for altering elements contained in the array.
If you need to create an element array from regular elements:
Hpricot::Elements[ele1, ele2, ele3]
Assuming that ele1, ele2 and ele3 contain element objects (Hpricot::Elem, Hpricot::Doc, etc.)
Usually the Hpricot::Elements you’re working on comes from a search you’ve done. Well, you can continue searching the list by using the same at and search methods you can use on plain elements.
elements = doc.search("/div/p") elements = elements.search("/a[@href='http://hoodwink.d/']") elements = elements.at("img")
When you’re altering elements in the list, your changes will be reflected in the document you started searching from.
doc = Hpricot("That's my spoon, Tyler.") doc.at("b").swap("fork") doc.to_html #=> "That's my fork, Tyler."
If you can’t find a method here that does what you need, you may need to loop through the elements and find a method in Hpricot::Container::Trav which can do what you need.
For example, you may want to search for all the H3 header tags in a document and grab all the tags underneath the header, but not inside the header. A good method for this is next_sibling:
doc.search("h3").each do |h3| while ele = h3.next_sibling ary << ele # stuff away all the elements under the h3 end end
Most of the useful element methods are in the mixins Hpricot::Traverse and Hpricot::Container::Trav.
Given two elements, attempt to gather an Elements array of everything between (and including) those two elements.
# File lib/hpricot/elements.rb, line 319 def self.expand(ele1, ele2, excl=false) ary = [] offset = excl ? -1 : 0 if ele1 and ele2 # let's quickly take care of siblings if ele1.parent == ele2.parent ary = ele1.parent.children[ele1.node_position..(ele2.node_position+offset)] else # find common parent p, ele1_p = ele1, [ele1] ele1_p.unshift p while p.respond_to?(:parent) and p = p.parent p, ele2_p = ele2, [ele2] ele2_p.unshift p while p.respond_to?(:parent) and p = p.parent common_parent = ele1_p.zip(ele2_p).select { |p1, p2| p1 == p2 }.flatten.last child = nil if ele1 == common_parent child = ele2 elsif ele2 == common_parent child = ele1 end if child ary = common_parent.children[0..(child.node_position+offset)] end end end return Elements[*ary] end
# File lib/hpricot/elements.rb, line 274 def self.filter(nodes, expr, truth = true) until expr.empty? _, *m = *expr.match(/^(?:#{ATTR_RE}|#{BRACK_RE}|#{FUNC_RE}|#{CUST_RE}|#{CATCH_RE})/) break unless _ expr = $' m.compact! if m[0] == '@' m[0] = "@#{m.slice!(2,1).join}" end if m[0] == '[' && m[1] =~ /^\d+$/ m = [":", "nth", m[1].to_i-1] end if m[0] == ":" && m[1] == "not" nodes, = Elements.filter(nodes, m[2], false) elsif "#{m[0]}#{m[1]}" =~ /^(:even|:odd)$/ new_nodes = [] nodes.each_with_index {|n,i| new_nodes.push(n) if (i % 2 == (m[1] == "even" ? 0 : 1)) } nodes = new_nodes elsif "#{m[0]}#{m[1]}" =~ /^(:first|:last)$/ nodes = [nodes.send(m[1])] else meth = "filter[#{m[0]}#{m[1]}]" unless m[0].empty? if meth and Traverse.method_defined? meth args = m[2..-1] else meth = "filter[#{m[0]}]" if Traverse.method_defined? meth args = m[1..-1] end end args << -1 nodes = Elements[*nodes.find_all do |x| args[-1] += 1 x.send(meth, *args) ? truth : !truth end] end end [nodes, expr] end
Adds the class to all matched elements.
(doc/"p").add_class("bacon")
Now all paragraphs will have class=“bacon”.
# File lib/hpricot/elements.rb, line 226 def add_class class_name each do |el| next unless el.respond_to? :get_attribute classes = el.get_attribute('class').to_s.split(" ") el.set_attribute('class', classes.push(class_name).uniq.join(" ")) end self end
Just after each element in this list, add some HTML. Pass in an HTML str, which is turned into Hpricot elements.
# File lib/hpricot/elements.rb, line 154 def after(str = nil, &blk) each { |x| x.parent.insert_after x.make(str, &blk), x } end
Add to the end of the contents inside each element in this list. Pass in an HTML str, which is turned into Hpricot elements.
# File lib/hpricot/elements.rb, line 136 def append(str = nil, &blk) each { |x| x.html(x.children + x.make(str, &blk)) } end
Searches this list for the first element (or child of these elements) matching the CSS or XPath expression expr. Root is assumed to be the element scanned.
See Hpricot::Container::Trav.at for more.
# File lib/hpricot/elements.rb, line 67 def at(expr, &blk) if expr.kind_of? Fixnum super else search(expr, &blk)[0] end end
Gets and sets attributes on all matched elements.
Pass in a key on its own and this method will return the string value assigned to that attribute for the first elements. Or nil if the attribute isn’t found.
doc.search("a").attr("href") #=> "http://hacketyhack.net/"
Or, pass in a key and value. This will set an attribute for all matched elements.
doc.search("p").attr("class", "basic")
You may also use a Hash to set a series of attributes:
(doc/"a").attr(:class => "basic", :href => "http://hackety.org/")
Lastly, a block can be used to rewrite an attribute based on the element it belongs to. The block will pass in an element. Return from the block the new value of the attribute.
records.attr("href") { |e| e['href'] + "#top" }
This example adds a #top anchor to each link.
# File lib/hpricot/elements.rb, line 205 def attr key, value = nil, &blk if value or blk each do |el| el.set_attribute(key, value || blk[el]) end return self end if key.is_a? Hash key.each { |k,v| self.attr(k,v) } return self else return self[0].get_attribute(key) end end
Add some HTML just previous to each element in this list. Pass in an HTML str, which is turned into Hpricot elements.
# File lib/hpricot/elements.rb, line 148 def before(str = nil, &blk) each { |x| x.parent.insert_before x.make(str, &blk), x } end
Empty the elements in this list, by removing their insides.
doc = Hpricot("
 We have so much to say.
") doc.search("i").empty doc.to_html => "
 We have  to say.
"
# File lib/hpricot/elements.rb, line 130 def empty each { |x| x.inner_html = nil } end
# File lib/hpricot/elements.rb, line 351 def filter(expr) nodes, = Elements.filter(self, expr) nodes end
Returns an HTML fragment built of the contents of each element in this list.
If a HTML string is supplied, this method acts like inner_html=.
# File lib/hpricot/elements.rb, line 86 def inner_html(*string) if string.empty? map { |x| x.inner_html }.join else x = self.inner_html = string.pop || x end end
Replaces the contents of each element in this list. Supply an HTML string, which is loaded into Hpricot objects and inserted into every element in this list.
# File lib/hpricot/elements.rb, line 99 def inner_html=(string) each { |x| x.inner_html = string } end
Returns an string containing the text contents of each element in this list. All HTML tags are removed.
# File lib/hpricot/elements.rb, line 107 def inner_text map { |x| x.inner_text }.join end
# File lib/hpricot/elements.rb, line 356 def not(expr) if expr.is_a? Traverse nodes = self - [expr] else nodes, = Elements.filter(self, expr, false) end nodes end
Add to the start of the contents inside each element in this list. Pass in an HTML str, which is turned into Hpricot elements.
# File lib/hpricot/elements.rb, line 142 def prepend(str = nil, &blk) each { |x| x.html(x.make(str, &blk) + x.children) } end
Remove all elements in this list from the document which contains them.
doc = Hpricot("Remove this: here") doc.search("b").remove doc.to_html => "Remove this: "
# File lib/hpricot/elements.rb, line 119 def remove each { |x| x.parent.children.delete(x) } end
Remove an attribute from each of the matched elements.
(doc/"input").remove_attr("disabled")
# File lib/hpricot/elements.rb, line 239 def remove_attr name each do |el| next unless el.respond_to? :remove_attribute el.remove_attribute(name) end self end
Removes a class from all matched elements.
(doc/"span").remove_class("lightgrey")
Or, to remove all classes:
(doc/"span").remove_class
# File lib/hpricot/elements.rb, line 255 def remove_class name = nil each do |el| next unless el.respond_to? :get_attribute if name classes = el.get_attribute('class').to_s.split(" ") el.set_attribute('class', (classes - [name]).uniq.join(" ")) else el.remove_attribute("class") end end self end
Searches this list for any elements (or children of these elements) matching the CSS or XPath expression expr. Root is assumed to be the element scanned.
See Hpricot::Container::Trav.search for more.
# File lib/hpricot/elements.rb, line 58 def search(*expr,&blk) Elements[*map { |x| x.search(*expr,&blk) }.flatten.uniq] end
Convert this group of elements into a complete HTML fragment, returned as a string.
# File lib/hpricot/elements.rb, line 78 def to_html map { |x| x.output("") }.join end
Wraps each element in the list inside the element created by HTML str. If more than one element is found in the string, Hpricot locates the deepest spot inside the first element.
doc.search("a[@href]"). wrap(%{

})
This code wraps every link on the page inside a div.link and a div.link_inner nest.
# File lib/hpricot/elements.rb, line 166 def wrap(str = nil, &blk) each do |x| wrap = x.make(str, &blk) nest = wrap.detect { |w| w.respond_to? :children } unless nest raise "No wrapping element found." end x.parent.replace_child(x, wrap) nest = nest.children.first until nest.empty? nest.html([x]) end end
Generated with the Darkfish Rdoc Generator 2.


As high-performance computing resources have become increasingly available, new modes of computational processing and experimentation have become possible. The Extreme-scale Model Exploration with Swift (EMEWS) framework enables the direct integration of multi-language model exploration (ME) algorithms while scaling dynamic computational experiments to very large numbers (millions) of models on all major HPC platforms. EMEWS has been designed for any "black box" application code, such as agent-based and microsimulation models or training of machine learning models, that require multiple runs as part of heuristic model explorations. One of the main goals of EMEWS is to democratize the use of large-scale computing resources by making them accessible to more researchers in many more science domains. EMEWS is built on the Swift/T parallel scripting language.
EMEWS software can be most easily installed through the Spack package manager. If you don't have Spack installed, do the following, which will install Spack and set up Spack shell support:
$ git clone https://github.com/spack/spack.git $ . spack/share/spack/setup-env.shDifferent flavors of Swift/T can be installed depending on the type of EMEWS workflow you need. The Python and R-enabled Swift/T variant is recommended:
## Optional R, Rcpp and RInside Install with Spack $ spack install r-rinside $ spack activate r-rinside
$ spack install stc ^turbine+python+r
Look here for information and tips to reduce the number of dependencies that need to be built by Spack by using already installed software.
Once Swift/T is installed, you can install EQ/R and EQ/Py (manually or via Spack) to allow for R-based or Python-based model exploration. See the EMEWS tutorial (below) for more information.
The EMEWS tutorial is the primary resource for using EMEWS.
For additional EMEWS resources, see the resources page.
For EMEWS papers, see the papers page.
For support, including EMEWS mailing list information, see the support page.


Tweet Gateway will post tweets for you, just by calling a simple URL. Thus you can enable every other service to post tweets on Twitter.
For example, you can use Tweet Gateway to automatically tweet the text of incoming SMS from your smartphone. I've used an app like SMS Gateway for this, many times.
Once installed on your smartphone, you configure this app like this:
SMS Gateway will append the URL request parameters like this http://myserver/gw/1234567890abcdef?text=test - Thus Tweet Gateway will post the text 'test' for you.
This service can only be accessed when signed in with Twitter. The user's secret access credentials are stored and transmitted encrypted. There is a lot of effort done to protect you and your data.
After sign in, you're able to create your own gateway URLs. These URLs are 16 characters long and contain letters and digits. This means, there are 5,227,573,613,485,916,806,405,226,496 different combinations possible. This is equal to a strength of 92bit. Brute forcing a URL will take way more the 100 years of computing power.
Please, keep your personal gateway URLs secret.


{% extends 'flatpages/basicflatpage.html' %} {% block content %}
You can reach Überlearner at support@uberlearner.com


com.vividsolutions.jts.awt
Interfaces
PointShapeFactory
PointTransformation
Classes
FontGlyphReader
GeometryCollectionShape
IdentityPointTransformation
PointShapeFactory.BasePointShapeFactory
PointShapeFactory.Circle
PointShapeFactory.Cross
PointShapeFactory.Point
PointShapeFactory.Square
PointShapeFactory.Star
PointShapeFactory.Triangle
PointShapeFactory.X
PolygonShape
ShapeCollectionPathIterator
ShapeReader
ShapeWriter


Desktop Email Clients
{% include legacy/cardv2.html
title="Thunderbird"
image="/assets/img/legacy_svg/3rd-party/thunderbird.svg"
description="Thunderbird is a free, open source, cross-platform email, newsgroup, news feed, and chat (XMPP, IRC, Twitter) client developed by the Thunderbird community, and previously by the Mozilla Foundation."
website="https://www.thunderbird.net/"
privacy-policy="https://www.mozilla.org/privacy/thunderbird/"
source="https://hg.mozilla.org/comm-central/"
windows="https://www.thunderbird.net"
mac="https://www.thunderbird.net"
linux="https://www.thunderbird.net/"
freebsd="https://www.freshports.org/mail/thunderbird/"
openbsd="http://openports.se/mail/mozilla-thunderbird"
netbsd="http://pkgsrc.se/mail/thunderbird"
%}
{% include legacy/cardv2.html
title="Mailpile"
image="/assets/img/legacy_svg/3rd-party/mailpile.svg"
description="Mailpile is a free, community funded, open source email client with user-friendly encryption and privacy features."
website="https://www.mailpile.is/"
privacy-policy="https://www.mailpile.is/privacy.html"
tor="http://clgs64523yi2bkhz.onion"
github="https://github.com/mailpile/Mailpile"
linux="https://www.mailpile.is/download/linux.html"
%}
{% include legacy/cardv2.html
title="Mailvelope"
image="/assets/img/legacy_svg/3rd-party/mailvelope.svg"
description="Mailvelope is a browser extension that enables the exchange of encrypted emails following the OpenPGP encryption standard."
website="https://www.mailvelope.com/en"
privacy-policy="https://www.mailvelope.com/en/privacy-policy"
github="https://github.com/mailvelope/mailvelope"
firefox="https://addons.mozilla.org/firefox/addon/mailvelope/"
chrome="https://chrome.google.com/webstore/detail/mailvelope/kajibbejlbohfaggdiogboambcijhkke?hl"
edge="https://microsoftedge.microsoft.com/addons/detail/mailvelope/dgcbddhdhjppfdfjpciagmmibadmoapc"
%}
Worth Mentioning
- NeoMutt - NeoMutt is an open-source command line mail reader (or MUA) for Linux and BSD. It’s a fork of Mutt with added features.
Mobile Email Clients
Android Email Clients
{% include legacy/cardv2.html
title="FairEmail"
image="/assets/img/legacy_svg/3rd-party/fairemail.svg"
description="FairEmail is a minimal, open source email app, using open standards (IMAP, SMTP, OpenPGP) with a low data and battery usage."
website="https://email.faircode.eu/"
privacy-policy="https://github.com/M66B/FairEmail/blob/master/PRIVACY.md"
github="https://github.com/M66B/FairEmail"
fdroid="https://f-droid.org/en/packages/eu.faircode.email/"
googleplay="https://play.google.com/store/apps/details?id=eu.faircode.email"
%}
{% include legacy/cardv2.html
title="K-9 Mail"
image="/assets/img/legacy_svg/3rd-party/k9mail.svg"
description="K-9 Mail is an independent mail application that supports both POP3 and IMAP mailboxes, but only supports push mail for IMAP."
website="https://k9mail.app/"
privacy-policy="https://k9mail.app/privacy"
github="https://github.com/k9mail"
fdroid="https://f-droid.org/packages/com.fsck.k9/"
googleplay="https://play.google.com/store/apps/details?id=com.fsck.k9"
%}
iOS Email Clients
{% include legacy/cardv2.html
title="Canary Mail"
image="/assets/img/legacy_svg/3rd-party/canarymail.svg"
labels="color==warning::link==https://canarymail.io/faq.html::text==Closed source::tooltip==The source programming code for Canary Mail is not available. Canary Mail is a proprietary application."
description="Canary Mail is a paid email client designed to make end-to-end encryption seamless with security features such as a biometric app lock."
website="https://canarymail.io/"
privacy-policy="https://canarymail.io/privacy.html"
ios="https://apps.apple.com/us/app/canary-mail/id1236045954"
%}
Worth Mentioning
- Letterbox - Letterbox is a free open-source mail client for iOS made as a part of an ongoing research project at the Freie Universität Berlin, Germany.


Revista de Saúde Pública: forty years of Brazilian scientific production
Júlio Cesar Rodrigues Pereira
Departamento de Epidemiologia. Faculdade de Saúde Pública. Universidade de São Paulo. São Paulo, SP, Brasil
ABSTRACT
OBJECTIVE:
To recognize the characteristics and path taken by the through analysis of the
scientific production it has published over the period from 1967 to 2005.
METHODS:
Scientometric methods were used to analyze reference data on the articles published
in the Revista, retrieved from the databases ISI/Thomson Scientific (Web of
Science), National Library of Medicine (PubMed) and Scientific Electronic Library
Online (SciELO).
RESULTS:
The Revista is the only Brazilian publication in the field of public health
that is indexed by ISI/Thomson Scientific. It is prominent as a medium for publishing
Brazilian scientific production in public health and is displaying a geometric
increase in publication and citation, with annual rates of 4.4% and 12.7%, respectively.
The mean number of authors per paper has risen from 2 to 3.5 over recent years.
Although original research articles predominate, the numbers of reviews, multicenter
studies, clinical trials and validation studies have been increasing. The number
of articles published in foreign languages has also increased, accounting for
13% of the total, and the leading countries originating these are the UK, USA,
Argentina and Mexico. The number and diversity of journals citing the Journal
has been increasing, many of which are non-Brazilian. Authorship per author
shows good fit to Lotka's Law, but the parameters suggest greater concentration
and less dispersion than would be expected. Among the fields of interest of
published papers, the following topics account for more than 50% of the total
volume: infectious-parasitic diseases and vectors; health promotion, policies
and administration; and epidemiology, surveillance and disease control.
CONCLUSIONS:
The Revista shows great dynamism, without signs of abating or reaching a plateau
any time soon. There are signs of progressively increasing complexity in the
studies published, and more multidisciplinary work. The Revista seems to be
widening its outreach and recognition, while remaining faithful to the field
of public health in Brazil.
Keywords: Scientific publications. Periodicals, history. Periodicals, trends. Public health.
INTRODUCTION
The Revista de Saúde Pública is reaching its fortieth anniversary distinguished as one of the leading journals in the field of public health in Brazil. In fact, preliminary analysis of the data from the project "Characterization of Postgraduate Programs in Public Health in Brazil",* in which all the scientific production from postgraduate lecturers within this field that is registered in the Thomson Scientific database (formerly ISI, the Institute for Scientific Information) up to 2005 is being studied, places the Revista as the first choice for the publication of their work. In this analysis, it has been seen that, with regard to indexed journals in that database, these authors concentrate the publication of their work in seven journals, which alone account for one-third of the production from this group of authors:
| 1° | Revista de Saúde Pública, with 939 articles; |
| 2° | Memórias do Instituto Oswaldo Cruz, with 163 articles; |
| 3° | Brazilian Journal of Medical and Biological Research, with 145 articles; |
| 4° | American Journal of Epidemiology, with 128 articles; |
| 5° | Journal of Dental Research, with 127 articles; |
| 6° | Transactions of the Royal Society of Tropical Medicine and Hygiene, with 57 articles; |
| 7° | Circulation, with 56 articles. |
This group of journals has been identified as the hard core of publications from postgraduate lecturers in public health, by applying Bradford's Law.1 This predicts that, among the set of publications within a scientific discipline, the numbers of journals in the first, second and third terciles of production obey an order of 1:n:n2. The records in the aforementioned project include 4,842 publications and the Bradford sets have been identified in a ratio that is close to the theoretical prediction: 1:n:n1.8.
Bradford's theory was among the first contributions towards originating scientometry, a scientific discipline that is well established today. From the middle of last century onwards, it became greatly boosted through procedures for bibliometric analysis, thanks to the consolidation of the records relating to scientific production, on a regular basis. In the present article, bibliometric records are analyzed with a view to offering a portrait of the scientometric base for these forty years of the Revista de Saúde Pública.
METHODS
The Revista has had its publications registered in the MEDLINE database of the National Library of Medicine, in the United States, since 1967; in the Social Science Citation Index and the Web of Science, since 1982; and in SciELO (Scientific Electronic Library Online), an initiative coordinated by BIREME-PAHO/WHO (Latin American and Caribbean Center on Health Sciences Information) and by the Fundação de Amparo à Pesquisa do Estado de São Paulo (Fapesp - State of São Paulo Research Foundation), since 1977. On the basis of the records in the Web of Science, MEDLINE/PubMed and SciELO, it was sought to characterize the Revista over the period from 1967 to 2005, according to the patterns of:
| 1) | production, through studying the publication dynamics and characteristics of the articles over this period; |
| 2) | reach and repercussion, through studying their citations; |
| 3) | authorship, through fitting this to scientometric laws and by institutional authorship; and |
| 4) | topics of interest, through analyzing keywords. |
Details of the methodological procedures for the analysis will be presented together with the results from each of these databases. The methodological description will be restricted to what is necessary for correct interpretation of the results and as required for clarifying their presentation.
RESULTS
Production
It is the MEDLINE/PubMed databases that gather together the greatest quantity of information on the articles published by the Revista: there are records of 2,540 documents of different types, of which 20 were in 1967 and 146 were in 2005. Figure 1 shows the scatter of the annual numbers of items published over this period, and also a curve fitted using the least-squares method as a suggestion for the inferred behavioral pattern.
The curve suggested in Figure 1 has a good fit (R2=0.89) and is described by the following function:
in which the parameters indicate, respectively:
According to the classification by types of publication in the PubMed database, scientific articles account for 92% of all types of documents published, but by examining the trends, it can be seen that, over more recent five-year periods, other types have progressively gained space in the Revista (Figure 2).
For the same period, the PubMed records also make it apparent that, despite the predominance of the Portuguese language (87% of the total), both Spanish and English have been increasing the participation over recent years, as shown by Figure 3. It should be noted that, in its electronic format, the Revista has also been published in the English language since 2003.
In the Web of Science records, the countries of origin of the authors of documents published by the Revista can be ascertained. Over the period from 1982 to 2005, there were a total of 2,241 publications, of which 2,231 have valid records of their country of origin. By dividing this period into five-year periods, the information presented in Table 1 is obtained. Similar information can also be obtained from SciELO for the period 1997-2005, but preference was given to the Web of Science because of its broader coverage.
Reach and repercussion
Also from the Web of Science records, the behavioral patterns of citations of articles published by the Revista can be ascertained. Among the 593 journals in the field of "General Social Sciences", within which the Revista de Saúde Pública is indexed, it is ranked 238th in numbers of citations, although it is 577th in numbers of citations per article. These statistics relate to May 2006 and are available under the heading "Essential Science Indicators", in which data relating to the previous ten years plus the current year are analyzed, with updating every two months. The Web of Science presents information processed as five-year periods, as shown by the data in Table 2.
An examination of the annual citation rates for the articles published since 1982 suggests a tendency towards each article resulting in two citations, as shown in Figure 4.
By examining Figure 2, from the most recent years to the earlier years, it can be seen that this mean rate of two citations per article is achieved after around five to seven years after publication. For the last ten years and the year 2006, the consultation of the Web of Science in May 2006 registered 1,312 citations for 1,044 articles, this giving a ten-year rate of 1.26 citations per article.
Recently, with the implementation of the "Essential Science Indicators", the ISI/Thomson Scientific database has restricted the calculation of the impact factor (number of citations of the articles published over the last two-year period divided by the number of articles published during this two-year period) to the so-called Science Edition of the Journal Citation Reports (JCR). Until then, the impact factor for journals in the Web of Science - Social Sciences database appeared in the JCR, and the Revista de Saúde Pública registered an impact factor of around 0.35 citations per article.
However, the impact factor for the Revista can be gauged from the SciELO database, which was implemented with pioneering participation from the Revista. There, in a consultation in May 2006, the current impact factor found was 0.1038, using a two-year calculation basis, and 0.1333, for a three-year basis. Taking the two-year impact factors in a historical series, figures ranging from 0.2 to 0.4 were found. It was noted that, although the impact rates originated from different data collections, they converged towards similar figures, thereby suggesting the strong inductive inference that this is a fair measurement of the Revista's performance.
In SciELO, in the same way as previously done by JCR, there is the additional information of calculations of the half-lives of citations (the time taken for 50% of the total number of citations to occur, or the median of the age of the citations). At present, the half-life is 6.38 and, from examination of the historical series, it was observed that it ranged from four to eight years. Again, this information is consistent with the citations register in the Web of Science, which was analyzed in Figure 4, and this suggests that after around ten years, all the citations expected have been concluded.
In addition to now offering statistics on 158 indexed journals with the same quality as in the Web of Science, SciELO also offers free access to each of them in digital files. Any edition of the Revista de Saúde Pública can be freely consulted, from 1977 up to the present date, and PubMed offers a link for such consultations. This, together with the growing share of articles in the English language (Figure 3), establishes the conditions needed for an increase in its reach and progressive growth in its citations. Just as in the production, the numbers of citations have also grown exponentially, as suggested by Figure 5.
By fitting the function suggested by Figure 5 to the data (note that 2006, which is still incomplete, has been disregarded because it is aberrant), an excellent fit is obtained (R2 = 0.97) for an exponential function of the following form:
in which the parameters, as in the case of the production, indicate respectively:
It is worth noting that the growth rate for citations is more than twice the growth rate for production. This suggests that, in addition to vegetative growth resulting only from the increase in the numbers of articles published and their citation yield (two per article published), the growth in citations can be attributed to other factors. Among the candidates for such explanatory variables are both the progressive increase in texts in English and the greater ease of access provided by SciELO.
The sources of citation of the Revista today differ from those of its early years. The first five-year period with records in the Web of Science (1982-1986) allows the citation pattern to be ascertained: there were 553 citations distributed among 112 journals. Over the last five-year period (2002 to 2006), because of the long half-life there were only 238 citations, but these were distributed among 136 journals. The final five-year period has around half the number of citations seen in the first five-year period, but still has practically the same number of citing journals: in the first five-year period there were 4.9 citations per citing journal, and 1.75 in the final period. This degree of concentration would be greatest if equal to the number of citations (all citations in the same journal) and least if equal to one (each citation in a different journal). From the first to the last five-year period there was a reduction in concentration of 64.3%, such that the last five-year period is only 35.7% of the first, i.e. 2.8 times lower in concentration or, said in another way, 2.8 times greater outreach.
From the Web of Science records, it can also be ascertained which journals made these citations of the Revista de Saúde Pública. To find out about these while taking into account the passage of time, the period beginning in 1971 was divided into decades up to the present date, with the fourth decade starting in 2000. Since it is not possible to list all the journals that have already cited the Revista de Saúde Pública, a selection method has to be determined. Taking into consideration that, during the first decade, six journals registered at least two citations of the Revista de Saúde Pública, it was established that these six would be identified. For the subsequent periods, the quantity of journals registering at least two citations of the Revista grew prohibitively, which called for a different cutoff method that still respected the cutoff rationale established for the first decade. Given that, according to the number of citations, the hierarchy of citing journals had a Pareto distribution, it was defined that the number of citing journals to be presented for each period would be proportional to the dispersion parameter of a Pareto function fitted to the data in each period. Thus, independent of the number of journals, those with the greatest contribution were selected for highlighting, according to the characteristics of the period. The Pareto probability density function is a continuous asymmetrical function that can roughly be imagined as the right half of a normal distribution curve, and it has the following form:
For the purposes of its application here, it can be simplified to the following description:
in which the parameters c and a represent, respectively:
Consequent to defining this methodological strategy, Table 3 shows the statistics on the citations of the Revista de Saúde Pública and Table 4 lists the journals highlighted in the four periods.
Authorship
For the 2,540 articles registered in the PubMed database, 4,575 authors were found, who wrote between one and 128 articles for the Revista. In bibliometry, the number of authors for an article is an indirect measurement of its complexity, if conditioning factors of another order such as possible authorship due to comradeship are ignored in principle. Over this study period of almost 40 years, the Revista has shown a year-by-year progressive increase in the mean number of authors per article, consistent with what is a universal trend of growing complexity in scientific investigations (Figure 6).
Since each article may have more than one author, the 4,575 authors gave rise to 8,104 authorships. The canons of scientometry state that the distribution of authorships among authors within a given field of scientific production follows Lotka's Law.3 According to this theory, which is also called the inverse-square law, 60% of authors would have only one authorship and this proportion would decrease strongly, inversely to the square of the number of authorships. Thus, authors with one authorship would represent 60%, with two authorships 15%, and so on, in accordance with the following function:
Figure 7 shows the relative frequencies of the authors according to the number of authorships and a data curve adjusted to Lotka's Law.
The Lotka function fitted to the Revista's production data (R2 = 0.99) takes on the following form:
This configuration of the distribution of authorships suggests that the Revista's community of authors is eclectic, given the large proportion of authors with only one article published (75%, or 25% greater than the 60% expected by Lotka's Law) and the narrow variability (2.5, or also 25% greater than the 2 expected by Lotka's Law: the greater the exponent is, the lower the variability and the flatter the curve are).
Ninety-three percent of the authors of the Revista de Saúde Pública are authors with only one, two or three contributions. Although this large proportion of authors with a small number of publications suggests a lack of any parochialism in the Revista, this must also be considered in the light of the field of knowledge that it serves. Pedrosa,** studying the scientific production of postgraduate lecturers in a sample from all the programs accredited by Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (Capes - Coordination for the improvement of higher education personnel), found that a Lotka function fitted to these data also suggested a large concentration of authors with few publications: 69% of the authors recognized through the Web of Science records had only one authorship and the dispersion was less than expected (the exponent of the denominator of the Lotka function was 2.24).
By consulting the Web of Science database, the institutional authors that have contributed most to the Revista can be determined (Table 5). It is worth noting that there has been a progressive reduction in the proportional participation by the Universidade de São Paulo (USP - which hosts the Revista), giving room for other institutions, such as the Universidade Federal de São Paulo (Unifesp), which had tripled its participation by 2005. The Universidade Estadual de Campinas (Unicamp) had a regular participation in the three periods; the Universidade Federal de Pelotas (UFPel) started to appear in the 1990s and proportionally increased its participation in the 2000s; the State Health Department of São Paulo and its research institutes dropped out of the top ten institutions in terms of proportional participation in the 2000s, while the Universidade Federal da Bahia (UFBA) recovered its position that had been lost in the 1990s.
Topics of interest
To classify the topic of interest of a publication, the Web of Science allocates each journal registered in its database to a certain field of scientific knowledge. This is a rough classification that fits each item published by a journal into a large field, in accordance with the scope of topics of the journal. The Revista de Saúde Pública is classified in the field of "Public, Environmental & Occupational Health". This type of classification is greatly used in scientometric studies and allows profiles to be determined for scientific production in given fields of interest. For example, a study on Brazilian scientific production over the period from 1981 to 19954 enabled the identification of physics, biology and biochemistry, clinical medicine, engineering, chemistry and plant and animal sciences as the fields of knowledge that were most prominent within Brazilian science. For the present study, for which the field of interest was one journal, this classification was of no help for characterization purposes. For this reason, it was necessary to resort to the keywords of the articles published. Both the Web of Science and PubMed include keywords for each bibliographic item registered in their databases, although they do this distinct ways that do not necessarily agree.
Analysis of keywords is recognized as inadequate for characterizing publications. It finds better application for use in database searches with the purpose of identifying articles dealing with similar subjects. Even for this purpose, its performance is modest. Over the last few years there has been some progress towards overcoming these limitations by means of conceptual structure recognition techniques in scientific texts. One initiative of this type, the technique from Collexis5, a German company that provides services for the World Health Organization (WHO - Alliance for Health Policy and Systems Research), and for some journals such as those from the publisher Elsevier, have been the subject of investigations and tests by BIREME/SciELO. This technique recognizes a "fingerprint" in every word of a given text: a root that concords with a Thesaurus of specialized terms, from which it classifies the degree of intensity with which this fingerprint is recognized in the text.
These reflections are necessary because, to analyze the topics of interest in the Revista de Saúde Pública, only the keywords can be made use of in analyses, among the data available, and caution is required in any interpretation of the information derived from these keywords.
To analyze the keywords in the articles published by the Revista, those registered by PubMed were chosen, given that this database covers the whole period of existence of the Revista. Among these keywords, interest was restricted to the "MeSH Major Topics", which are keywords at the highest level of aggregation that supposedly best represent the content of each article. "Supposedly", because although something like "Creatinine/*urine" would represent a high level of aggregation (a study on creatinine in the urine, without clarifying the purpose), it still denotes a specific aspect of the study, not a general characteristic. For 2,540 publication items that were recorded in PubMed for the Revista, 4,719 key words of "MeSH Major Topic" type were identified, which in PubMed are highlighted by an asterisk. These 4,719 keywords were used in 6,466 valid cataloging records (non-empty) for published items (a mean of 2.55 keywords per article: minimum of 0, maximum of 8, mode =2), of which only 842 had at least two occurrences per five-year period of existence of the Revista.
These 842 keywords accounted for 2,589 records of MeSH Major Topics, a volume that when distributed in a contingency table according to the Revista's five-year periods showed a non-random distribution (Fisher exact test; p=0.000). Residual analysis5 on this contingency table allowed identification of 557 records of 508 different MeSH Major Topics that characterized the Revista's five-year periods by statistically significant associations. Since this was still a very large volume for reporting in the present study, the MeSH Major Topics were recoded in a discretionary manner into 11 study categories, thus resulting in what is presented in Table 6 below, and summarized in Figure 8.
Placing the keywords into categories according to type of study for the present study involved arbitrary judgment, and readers' tolerance of this is requested, given that exhaustive description of the 557 "MeSH Major Topics" would be prohibitive, both because of their extensiveness and because of the difficulty in interpretation.
COMMENTS
Over the 40 years of the Revista de Saúde Pública, it has exhibited significant dynamism, as suggested well by functions (1) and (2). Following the criticism of the Malthusian model of exponential growth, the expectation that there has been for dynamic models describing natural phenomena is that, at some point, any growth would come up against a limit and that the intrinsic nature of the phenomenon would prohibit the surmounting of this limit. It would therefore be expected that, after the long period of 40 years, the growth in the annual number of publications and citations would already have reached its natural limit and that the function that described its dynamics would be asymptotic to this limit. However, the Revista still does not show any behavior suggestive of stabilization that would allow it to be argued that it might some day find a limit to its growth. The technological revolution that today allows articles to be published in the form of digital files that are accessible through the Internet has broken through the narrow limits of an economic and logistical nature that previously restricted the publishing of journals on paper. The Revista de Saúde Pública is still published in both forms, but today there are exclusively electronic journals and the future for journal publication seems to point in this direction. This may come to pass, and perhaps the growth limit for publications within a field of knowledge may one day come to be the exhaustion of that field's capacity to produce knowledge.
The growing complexity of the studies published (Figure 6), allied with the characteristics of function (3), suggests multidisciplinary work in the context of the articles published by the Revista. In fact, these characteristics suggest that authors from other fields of knowledge may be present in the Revista's articles as collaborators with public health authors: multidisciplinary teams that are needed to cope with public health studies that are progressively more complex. Even if the high concentration of authors with few studies published is considered to be a result from the characteristics of the field of public health, as duly signaled in the results, it cannot be neglected that the parameters of function (3) suggest that the Revista has a greater concentration of authorship or, expressing this in another way, greater diversity of authors, than in the cited study by Pedrosa** on this field. The growth and diversification of citing journals (Tables 3 and 4) reinforces the idea of greater coverage, complexity and diversification.
The numbers of items published in English and Spanish have increased (Figure 3) and both the types of documents published (Figure 2) and the sources of citation of the Revista (Table 4) have diversified, although the same cannot be said regarding the types of studies. Looking at Figure 8, the impression is that the topics of infectious-parasitic diseases and vectors; health promotion, policies and administration; epidemiology and disease surveillance and control; mother-child health; demography, mortality and morbidity; and nutrition have notable participation in the Revista that is regular and stable, and which has varied little over the five-year periods analyzed. However, proportional growth can be highlighted for, on the one hand occupational health and social, anthropological and economic studies (with progressive increases over recent years) and, on the other hand, ecological and environmental studies (with initially erratic appearance but subsequent regular increases in proportional participation over more recent five-year periods).
As signaled in the text, this information on types of study requires caution in ite interpretation. The factors limiting the faithfulness of the Revista's portrait that are highlighted are the restriction of the analysis only to the MeSH Major Topics, the arbitrary reduction of these to the ones with two or more presences per five-year period, the subsequent reduction of the latter to those with statistical associations with the five-year periods, and finally the arbitrary categorization by type of study. The only excuse for tolerating so many provisos is that, otherwise, any analysis would have had to be abandoned.
In other respects, the results have to be examined while taking their sources into account. The data analyzed originated from three distinct sources: PubMed, Web of Science and SciELO. These databases are independent and cover different periods and aspects of the classification of a publication. They are not necessarily concordant and may even diverge in the numbers of articles recorded for the Revista over a given period. In fact, some items cataloged by the Web of Science as "Item about an individual", "Book review", "Correction, addition", "Editorial material" and even "Article" are sometimes not found in PubMed, and vice versa. The classification of documents differs from one bibliographic database to another: here, the PubMed database was utilized (Figure 2) because it has the greatest coverage, albeit without this ensuring greater faithfulness. With regard to the citations, it should be remembered that these relate exclusively to the Web of Science database, which explains the absence of Cadernos de Saúde Pública, a journal published by Escola Nacional de Saúde Pública (ENSP - National Public Health School) and a sister publication of Revista de Saúde Pública in the family of Brazilian public health publications.
REFERENCES


Terser rules for Bazel
The Terser rules run the Terser JS minifier with Bazel.
Wraps the Terser CLI documented at https://github.com/terser-js/terser#command-line-usage
Installation
Add the @bazel/terser
npm package to your devDependencies
in package.json
.
Installing with self-managed dependencies
If you didn’t use the yarn_install
or npm_install
rule, you’ll have to declare a rule in your root BUILD.bazel
file to execute terser:
terser_minified
Run the terser minifier.
Typical example:
Note that the name
attribute determines what the resulting files will be called.
So the example above will output out.min.js
and out.min.js.map
(since sourcemap
defaults to true
).
If the input is a directory, then the output will also be a directory, named after the name
attribute.
terser_minified(name, args, config_file, debug, sourcemap, src, terser_bin)
name
(Name, mandatory): A unique name for this target.
args
(List of strings): Additional command line arguments to pass to terser.
Terser only parses minify() args from the config file so additional arguments such as --comments
may
be passed to the rule using this attribute. See https://github.com/terser/terser#command-line-usage for the
full list of terser CLI options.
Defaults to []
config_file
(Label): A JSON file containing Terser minify() options.
This is the file you would pass to the –config-file argument in terser’s CLI. https://github.com/terser-js/terser#minify-options documents the content of the file.
Bazel will make a copy of your config file, treating it as a template.
Run bazel with --subcommands
to see the path to the copied file.
If you use the magic strings "bazel_debug"
or "bazel_no_debug"
, these will be
replaced with true
and false
respecting the value of the debug
attribute
or the --compilation_mode=dbg
bazel flag.
For example
Will disable the arrows
compression setting when debugging.
If config_file
isn’t supplied, Bazel will use a default config file.
Defaults to @npm//@bazel/terser:terser_config.default.json
debug
(Boolean): Configure terser to produce more readable output.
Instead of setting this attribute, consider using debugging compilation mode instead
bazel build –compilation_mode=dbg //my/terser:target
so that it only affects the current build.
Defaults to False
sourcemap
(Boolean): Whether to produce a .js.map output
Defaults to True
src
(Label, mandatory): File(s) to minify.
Can be a .js file, a rule producing .js files as its default output, or a rule producing a directory of .js files.
Note that you can pass multiple files to terser, which it will bundle together. If you want to do this, you can pass a filegroup here.
terser_bin
(Label): An executable target that runs Terser
Defaults to @npm//@bazel/bin:terser


Information about me
This page contains a presentation of myself.
My name is André Sandin, born and raised in Kristianstad, Skåne, I was born 1993 which makes me 26 years old. I've been playing a lot of sports during my childhood and still does some but nowadays it's just with friends. I liked to play ice-hockey, floorball and football. I played floorball and hockey and attained the Österänggymnasium in Kristianstad where I studied to become a chef. I've been working as a chef, construction worker, kindergarden teacher and as a sökspecialist at Eniro.
Sport has allways been a big part of my life since both my parents are very interested in sports but something I haven't gotten from them is my love for computer games.
When I was done with school I worked for a couple of years before I decided to go for a backpacking trip in Asia where I was for 3 months, during that time I stayed in Indonesia, Cambodia, Vietnam, Singapore and different parts of Thailand.
That was a short presentation about me.


 Screenplay: Greg Berlanti. Producers: Mickey Liddell and Joseph Middleton. Director: Greg Berlanti. MPAA Rating: R (adult themes, profanity, drug use) Running Time: 94 minutes. Reviewed by Scott Renshaw.
The helpful sub-title tagged on to THE BROKEN HEARTS CLUB is not the only time you'll be instructed exactly what you're supposed to understand about the film. Throughout this tale of a group of gay West Hollywood friends, rookie writer/director Greg Berlanti includes title cards defining key words and phrases in the characters' lingo. "Meanwhile" is code to draw attention to an attractive guy nearby; a "newbie" is a recently-out young man; "gym bunnies" are the muscle-bound hunks desirable primarily (if not exclusively for sex). It's more than a movie, it's an anthropology class.
THE BROKEN HEARTS CLUB clearly has its broken heart in the right place, but it's too concerned with making statements about its milieu to let the narrative work organically as a character study. And there are lots of characters to study in this ensemble dramedy. Dennis (Timothy Olyphant) is a nice guy trying to make the transition from sex to relationships. Cole (Dean Cain), Dennis's roommate, is an aspiring actor who loves 'em and leaves 'em. Howie (Matt McGrath) has trouble admitting when he loves someone. Patrick (Ben Weber) has trouble loving himself. Taylor (Billy Porter) is the only one in a long-term relationship, though perhaps not for much longer. Benji (Zach Braff) looks for a more party-filled lifestyle. And Jack (John Mahoney) is their collective father-figure, the older restaurateur whose softball team brings them all together.
Those are just the members of the core group of pals, not even counting Patrick's lesbian sister (Mary McCormack) and her partner (Nia Long), or the sweet "newbie" (Andrew Keegan) Dennis takes under his wing. That's a whole heap of humanity to which Berlanti must be attentive, and he's not quite up to the task. Most of his characters remain types throughout, particularly the more effeminate Benji and Taylor. Olyphant (the menacing drug dealer in GO) is surprisingly good as Dennis, the most fully-developed of the characters, and Cain does a nice job of under-playing the philandering Cole. The rest of the actors just don't have enough to work with. In 94 minutes, THE BROKEN HEARTS CLUB just can't support a half-dozen major characters.
It's a shame, too, because Berlanti actually has an intriguing concept at the core of his film. Unlike most gay-themed films, this one isn't about coming out, or dealing with the straight world, or AIDS. It's a fairly risky statement about the complications when members of a minority group become so insular that their entire frame of reference becomes their other-ness. Berlanti's portrays his characters alternately coping effectively with their lives and dealing with the constant disappointment of not yet being able to define who they are or what they want. This is a film that's ready to acknowledge that sometimes gay men -- even after they've said, "We're here, we're queer" -- haven't quite gotten used to it.
An idea, unfortunately, isn't enough to sustain a film. While the characters struggle to emerge as individuals from Berlanti's broad thesis, the film struggles to avoid basic miscalculations in structure (case in point: After one character comments about rumors that a famous actor is gay, and another character responds, "Just because he's every gay man's fantasy doesn't mean he's gay," several seconds of idle banter commence before the cutaway to the famous actor in a clinch with another man). There is plenty of tart dialogue, and not all of it is of the bitchy-queen variety. The individual moments of humor and discovery are nice, but they don't add up to enough. THE BROKEN HEARTS CLUB is a movie determined to teach you something, rather than a movie about people whose experiences teach you something. A lecture with romance and comedy is still a lecture.
On the Renshaw scale of 0 to 10 boys in the bland: 5.
Visit Scott Renshaw's Screening Room http://www.inconnect.com/~renshaw/ *** Subscribe to receive new reviews directly by email! See the Screening Room for details, or reply to this message with subject "Subscribe".
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Kris Koeckritz
About
|
Portfolio
|
Contact
Portfolio
Hangman
RPG Game
Trivia Game
Rutgers Info Widget
Rock Paper Scissors


--- layout: post status: publish published: true title: New Renderings of Renovated Wrigley Field author: display_name: Corey Fineran login: Corey email<EMAIL_ADDRESS>url: '' author_login: Corey author_email<EMAIL_ADDRESS>wordpress_id: 9976 wordpress_url: http://ivyenvy.com/?p=9976 date: '2014-05-27 11:23:37 +0000' date_gmt: '2014-05-27 16:23:37 +0000' categories: - Wrigley Field tags: - Wrigley Field - Wrigley Renovations - Renderings of Wrigley Field - Renderings of Wrigley renovations comments: - id: 11303 author: TimWortmanJr author_email<EMAIL_ADDRESS>author_url: '' date: '2014-05-27 20:40:15 +0000' date_gmt: '2014-05-28 01:40:15 +0000' content: Love this. Give me a shovel I want to help - id: 11304 author: Kurt Sutton author_email: '' author_url: '' date: '2014-05-27 12:01:21 +0000' date_gmt: '2014-05-27 17:01:21 +0000' content: Does this mean Wrigley will have the first, fully enclosed bullpens? Or has another team done that before. I like the design, but I'm sad to see the bullpens are getting shoved underneath the bleachers. - id: 11305 author: Ivy Envy author_email: '' author_url: '' date: '2014-05-27 12:56:01 +0000' date_gmt: '2014-05-27 17:56:01 +0000' content: Kurt Sutton I can't think of another ballpark that has fully enclosed bullpens. I can understand why you'd want them visible, but on the other hand, the television broadcast usually only shows a quick shot or two of whoever is warming up. I would guess there will be cameras in there to show us what's going on. - id: 11306 author: Deborah Lembcke author_email: '' author_url: '' date: '2014-05-27 15:27:06 +0000' date_gmt: '2014-05-27 20:27:06 +0000' content: I thought I wouldn't like it but it is alright. Please keep the wall of ivy and the hand scoreboard in tact and as an old Cub fan I won't fuss too much. Life always has changes. - id: 11307 author: Taylor Krebs author_email: '' author_url: '' date: '2014-05-27 16:23:54 +0000' date_gmt: '2014-05-27 21:23:54 +0000' content: According to ESPN Chicago, the renovations to the Clubhouse start in July. - id: 11308 author: Joshua Adams author_email: '' author_url: '' date: '2014-05-27 18:04:43 +0000' date_gmt: '2014-05-27 23:04:43 +0000' content: "I like the \"coziness\" that the various outfield signs and what not bring to the field, but not sure about the cursive signs in left and right field. There has to be a more aesthetically pleasing way to do both. \nHonestly, if they're going to stay for twenty or more years, I'm pleased they are upgrading. My real wish, as unrealistic as it is, would be to have a lakefront stadium, ala AT&T Park in San Francisco." ---
Last week, the Cubs and Tom Ricketts released a video that informed us of their intentions to push forward with Wrigley renovations. Today, new renderings of the updated renovations plans were released. This is a 4-year renovation plan.
Renderings of the new plan for Wrigley's outfield. 7 signs total including 2 video boards: pic.twitter.com/8Sp7PHt8eq
— Danny Ecker (@DannyEcker) May 27, 2014
Also note new light towers in LF and RF. And no more lights on LF video board: pic.twitter.com/1o8vLIzkSB
— Danny Ecker (@DannyEcker) May 27, 2014
Rendering of RF bleachers with 3 extra rows of seats and bullpen underneath: pic.twitter.com/GAsaaqKX7A
— Danny Ecker (@DannyEcker) May 27, 2014
You can't help but notice the (lack of) views from the rooftops in these images. After hearing that the bullpens would be under the bleachers, it appears that the wall, and more importantly ivy, will remain relatively untouched.
Also, Bruce Miles tweeted that the Cubs will break ground on the new clubhouse in mid-July.
What do you think about these images?


Tiffany and LVMH are rising after striking the biggest luxury deal in history, Business Insider - Business Insider Singapore
by Theron Mohamed, Business Insider US- Shares in Tiffany & Co and LVMH jumped on Monday after the pair agreed a $16.2 billion merger, the largest luxury deal in history.
- The US jewelry retailer accepted an offer of $135 in cash per share from the French luxury-goods giant, after rejecting a lower offer earlier this month, Reuters reported.
- Watch Tiffany & Co and LVMH trade live.
Shares in Tiffany & Co jumped 6% in pre-market trading in New York, and LVMH stock climbed 2% in Paris, after the pair agreed a $16.2 billion merger, the largest luxury deal in history.
LVMH’s offer of $135 in cash per share represents a 7.5% premium to Tiffany’s closing price on Friday.
The French luxury-goods giant raised its offer after the US jewelry retailer rejected a bid of $120 earlier this month, Reuters reported.
LVMH owns more than 75 brands including Louis Vuitton, Christian Dior, Fendi, and Moët & Chandon. It expects the addition of Tiffany to bolster its US presence and strengthen its jewelry division, which houses Tag Heuer, Bulgari, and other big names.
While LVMH is the world leader in luxury brands, it hasn’t been as prominent in the jewelry market. Acquiring Tiffany more than doubles the scale of its jewelry business, especially within the US and Asian markets, according to Bloomberg.


Government of Gujarat
- Avoidance of duplication of beneficiaries
Aadhar Card Details
{{error}}
UID :
Village/Town/City :
Name :
Post Office Name :
Gender:
District :
Year of Birth :
State :
Care of :
Pincode :
House :
Income :
Landmark :
Phone Number :


Composites input layers on top of each other using the over operator. The first input (input1) is on the bottom layer, with the last input specified on the top. This primitive can provide a more convenient method of collapsing layers than using a composite primitive. The feMerge element can have any number in attributes specified with feMergeNode sub-elements.
Syntax
<feMerge> <feMergeNode in="C2"/> <feMergeNode in="C1"/> <feMergeNode in="SourceGraphic"/> </feMerge>
DOM Information
Inheritance Hierarchy
Node
Element
SVGElement
SVGFEMergeElement
Members
The SVGFEMergeElement object has these types of members:
Properties
The SVGFEMergeElement object has these properties.
| Property | Description |
|---|---|
|
Gets or sets the height of an element. | |
|
Provides a reference for the output result of a filter. | |
|
Defines the width of an element. | |
|
Gets or sets the x-coordinate value. | |
|
Gets or sets the y-coordinate value. |
Standards information
- Scalable Vector Graphics: Filter Effects, Section 15.25.21
See also
Build date: 1/13/2014


We're sorry but vv-graphql-workshop doesn't work properly without JavaScript enabled. Please enable it to continue.


fileutil_traverse - Iterative directory traversal
This package provides objects for the programmable traversal of directory hierarchies. The main command exported by the package is:
The command creates a new traversal object with an associated global Tcl command whose name is objectName. This command may be used to invoke various operations on the traverser. If the string %AUTO% is used as the objectName then a unique name will be generated by the package itself.
Regarding the recognized options see section OPTIONS. Note that all these options can be set only during the creation of the traversal object. Changing them later is not possible and causes errors to be thrown if attempted.
The object command has the following general form:
Command and its arguments determine the exact behavior of the object.
The following commands are possible for traversal objects:
This method is the most highlevel one provided by traversal objects. When invoked it returns a list containing the names of all files and directories matching the current configuration of the traverser.
The highlevel files method (see above) is based on this mid-level method. When invoked it finds all files and directories matching per the current configuration and executes the script for each path. The current path under consideration is stored in the variable named by filevar. Both variable and script live / are executed in the context of the caller of the method. In the method files the script simply saves the found paths into the list to return.
This is the lowest possible interface to the traverser, the core all higher methods are built on. When invoked it returns a boolean value indicating whether it found a path matching the current configuration (True), or not (False). If a path was found it is stored into the variable named by filevar, in the context of the caller.
The foreach method simply calls this method in a loop until it returned False. This method is exposed so that we are also able to incrementally traverse a directory hierarchy in an event-based manner.
Note that the traverser does follow symbolic links, except when doing so would cause it to enter a link-cycle. In other words, the command takes care to not lose itself in infinite loops upon encountering circular link structures. Note that even links which are not followed will still appear in the result.
In this version the traverser's broken system for handling symlinks was replaced with one working correctly and properly enumerating all the legal non-cyclic paths under a base directory.
While correct this means that certain pathological directory hierarchies with cross-linked sym-links will now take about O(n**2) time to enumerate whereas the original broken code managed O(n) due to its brokenness.
A concrete example and extreme case is the "/sys" hierarchy under Linux where some hundred devices exist under both "/sys/devices" and "/sys/class" with the two sub-hierarchies linking to the other, generating millions of legal paths to enumerate. The structure, reduced to three devices, roughly looks like
/sys/class/tty/tty0 --> ../../dev/tty0 /sys/class/tty/tty1 --> ../../dev/tty1 /sys/class/tty/tty2 --> ../../dev/tty1 /sys/dev/tty0/bus /sys/dev/tty0/subsystem --> ../../class/tty /sys/dev/tty1/bus /sys/dev/tty1/subsystem --> ../../class/tty /sys/dev/tty2/bus /sys/dev/tty2/subsystem --> ../../class/tty
When having to handle such a pathological hierarchy it is recommended to use the -prefilter option to prevent the traverser from following symbolic links, like so:
package require fileutil::traverse proc NoLinks {fileName} { if {[string equal [file type $fileName] link]} { return 0 } return 1 } fileutil::traverse T /sys/devices -prefilter NoLinks T foreach p { puts $p } T destroy
This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category fileutil of the Tcllib Trackers. Please also report any ideas for enhancements you may have for either package and/or documentation.
When proposing code changes, please provide unified diffs, i.e the output of diff -u.
Note further that attachments are strongly preferred over inlined patches. Attachments can be made by going to the Edit form of the ticket immediately after its creation, and then using the left-most button in the secondary navigation bar.
Programming tools


Python is good for developers.
No matter what operating system you or your customers are running, it will work. Unless you are coding platform-specific things, or using a platform-specific library, you can work on Linux and deploy on other systems, for example. However, that's not uncommon anymore (Ruby, Java, and many other languages work in the same way). Combined with the other qualities that we will discover throughout this book, Python becomes a smart choice for a company's primary development language.
This book is focused on the latest version of Python, 3.5, and all code examples are written in this version of the language unless another version is explicitly mentioned. Because this release is not yet widely used, this chapter contains some description of the current status quo of Python 3 to introduce readers to it, as well as some introductory information on modern approaches to development in Python. This chapter covers the following topics:
A book always starts with some appetizers. So, if you are already familiar with Python (especially with the latest 3.x branch) and know how to properly isolate environments for development purposes, you can skip the first two sections of this chapter and just read the other sections quickly. They describe some tools and resources that are not essential but can highly improve productivity in Python. Be sure to read the section on application-level environment isolation and pip, though, as their installation is mandatory for the rest of the book.
Python history starts somewhere in the late 1980s, but its 1.0 release date was in the year 1994, so it is not a very young language. There could be a whole timeline of major Python releases mentioned here, but what really matters is a single date: December 3, 2008 – the release date of Python 3.0.
At the time of writing, seven years have passed since the first Python 3 release. It is also four years since the creation of PEP 404—the official document that "un-released" Python 2.8 and officially closed the 2.x branch. Although a lot of time has passed, there is a specific dichotomy in the Python community—while the language develops very fast, there is a large group of its users that do not want to move forward with it.


Use this command to move the current column to the left side of the display. Doing this does not change the file in any way, but just changes the columns in which the bytes of the file are displayed. This is useful for analysing bytes in a file – for example, you might like to use this command when you encounter the start of a new record or structure.
This command simply changes the value of the window “offset”. See the Window page for more information.
Shortcuts
Keys: Alt+Enter


{% extends 'showcase/base.html' %} {% block body_block %}
Please enter the following details to register your team.


[gecode-users] question about posting of linear expressions
Kish Shen
kisshen at cisco.com
Fri Jul 9 02:31:31 CEST 2010
Guido Tack wrote:
>> reif = solver->vBool[b];
>> ...
>> reif = post(*solver, c);
>> ...
Hi Guido,
Thanks for pointing this out. After some trial and error, I think I have
now know how to work around the problem. The issue appears to be reif is
on the left hand side of =, and should be a new (uninitialised) BoolVar
- not an existing initialised BoolVar like what I was doing.
After the assignment, reif can then be linked to an existing BoolVar
like solver->vBool[b], or an integer value (0 or 1).
Cheers,
Kish
--
This e-mail may contain confidential and privileged material for the
sole use of the intended recipient. Any review, use, distribution or
disclosure by others is strictly prohibited. If you are not the intended
recipient (or authorized to receive for the recipient), please contact
the sender by reply e-mail and delete all copies of this message.
Cisco Systems Limited (Company Number: 02558939), is registered in
England and Wales with its registered office at 1 Callaghan Square,
Cardiff, South Glamorgan CF10 5BT.
More information about the users
mailing list


{{process.name}}
{{process.location}}
{{process.initiator}}
{{process.description}}
{{process.participation}}
{{process.parent}}


These readings aren't good...
Treat the spleen right away.
The area has been disinfected.
Please make your incision.
The contrast medium is working well.
We've confirmed the problem area.
The thrombi causing the vessel
blockage are originating here.
Work carefully. Use the magnifying
tool to view the vessel area.
Magnification successful.
Please continue.
We'll need to use ultrasound to
locate the thrombi...
Stop the thrombus from moving.
I would recommend the forceps.
Thrombus has ceased movement...
Make your incision there.
Drain the incised area in order
to eject the thrombus.
Thrombus removal complete.
Please treat the area with gel.
The thrombi seem to be diminishing,
and blood flow has improved.
...His vitals drop every time a
thrombus passes through the spleen!
The incision has been treated.
...!
The change in blood flow seems to be
causing the suspended thrombi to
move, as well!
Doctor, this is bad!
Tch... Gotta' work fast...
Stay calm... Concentrate...!
Everything's...slowing down...
I did it again...!
Doctor... What are we--
N-No thrombi detected...
Treatment is complete...
Doctor... What are we--
N-No thrombi detected...
Treatment is complete...
Then, let's close up the patient.
Suture the incision, and
the operation will be complete.
Amazing work, Dr. Stiles.
That was impressive.
Healing Touch... The power of
Asclepius. ...I can do this...
First, I'll recall the procedure...
I'm looking at the patient...
I was holding the scalpel like this,
and then I...
Okay... Now I'll concentrate
on my hands...!
I'm imagining a star... Now I'll
draw one in the air...
...Almost! I was close!
...Okay, try again.
My eyes are burning... I need to
treat the affected area...
Okay, for real this time!
Concentrate... Concentrate...!
Gah, no! I need to be quicker
and more precise!
Once more...! Healing Touch...
Here we go...!
*gasp, pant*
...just a little more...
......This is it! It's exactly
like before...!
I have the Healing Touch!
Ugh...maybe I overdid it...
...gave myself a headache.
Blood pressure and vitals are
dropping fast!
Wh-What? How could something
like this happen...?
But...there aren't any external
wounds... This isn't possible!
...No, the cause doesn't matter now.
We need to stop the bleeding first!
Understood, Doctor. Let's begin
treating her.
The large laceration needs attention
right away. Drain the blood, first.
Th-These are awful...it's too
dangerous trying to suture them...
Try using forceps to close the
wounds before you suture them.
Pinch one side and pull it over
to form a thin slit.
Pinch the larger wound with forceps
to form one thin slit...
It hemorrhaged again! This won't
stop until we treat its source...
That's it! Now suture it up
before it reopens!
If the wound reopens, close it
again and suture it quickly.
*sigh* The bleeding's stopped...
Now treat the other areas.
The small lacerations are taken care
of, but she's not clear yet...
We need to move on to the large
lacerations immediately.
Doctor, you should drain the blood
so we can treat the lacerations.
We're done treating those,
I think...
Move on to the smaller wounds.
Don't relax just yet!
Doctor! We need to drain the blood
so we can confirm the wound...
Everything's been sutured...
She's... going to make it!
I hate to think what would have
happened if she'd arrived later...
Close up the patient, Doctor.
The operation was a success.
Good work, Dr. Stiles.
You did well, Derek.
...Why now? She said she wanted
to live...!
I don't know...and these symptoms
don't add up...
Derek, take extra care during
this operation.
Angie, keep your eyes on
the monitors.
...Good luck, everyone.
......!
But...how!?
We fixed these three days ago!
Derek, Miss Reid is still weak from
her first lobectomy...
Use the same treatment, but
BE CAREFUL.
Doctor! We need to drain the blood
so we can confirm the wounds.
Treatment is progressing well.
Please continue...
This is strange... We still don't
have any idea why this happened.
...We've treated the lacerations.
What's our next step?
We need to close her up, and have
a closer examination later.
Nice job, Derek. Suture the incision
and finish--
What... is that!?
What the--
What the hell's going on!?
Doctor, try using ultrasound!
We have to look carefully...
Just stay calm, Derek.
There has to be something...
Look carefully, Doctor.
Did you see that!?
It was moving...
Derek, treat it like a tumor...
Excise and remove it right away!
What the hell...!? I've never seen
anything like this!
Doctor, we have to get it
out of the patient!
What if we tried incinerating
it with the laser?
...Good idea, Angie... Be careful,
we have to kill that thing.
I think it's working!
...If we keep this up...
Vitals dropping due to blood loss...
Suture the lacerations!
...It's gone...
Angie, using the laser was the right
decision. Good thinking.
It would've been a bad idea trying
to remove that thing alive.
It can't be!
...More of them!?
Derek, you'll have to burn them all.
That's the only way to save her!
Just like before...drag it out with
the scalpel, then laser it...!
One down...! What are these things?
Dammit...
We have to stop these things!
It's hiding... You'll just have to
find its shadow and cut it out.
That should be the last one...
We...did it...
...Let's close her up.
Derek, Angie, you both did well.
We...did it...
...Let's close her up.
Derek, Angie, you both did well.
(...Don't tell me that weird
parasite was the one--)
(Could it have been...GUILT!?)
......?
...What's going on?
Why'd they both stop talking?
Uh, Derek, continue...
Please suture the incision.
Linda should finally be able to
recover. Thank you, Dr. Stiles.
Her report details frequent
occurrences of light arrhythmia.
...Be ready for the unexpected,
just in case...
Let's get started with
the operation.
Disinfection complete.
Please make your incision.
...What? The electrocardiogram is
showing an abnormality!
She's suffering ventrical
fibrillation!
I'll attempt to stop the
convulsions... 3, 2, 1... Clear!
She's flatlining!
You need to massage her heart!
Doctor, the patient was born with
a highly irregular heartbeat.
There's a good chance her heart will
continue to go into convulsions.
I'll stand by with the defibrillator
in case we need to use it again.
If that happens, you'll need to
massage her heart immediately.
The defibrillator may have a high
success rate, but allowing the heart
to flatline repeatedly is obviously
very dangerous for the patient.
Make sure you revive her right away,
if that happens.
...Now, continue the operation.
Please open the atrium.
Stand by for defibrillation...
...3, 2, 1... Clear!
Pulse is back to normal. Keep an eye
out for any more abnormalities.
Doctor! We need to find a pulse!
This will be touchy...
Magnify the atrium.
Visibility is clear. First, excise
the left side of the valve.
Next, excise the right side.
Finally, excise the valve tissue
itself.
This is heart surgery, Dr. Stiles!
Please be more careful!
Let's begin the valve procedure.
We will excise it in 3 stages.
...But before that, we'll need to
drain this blood.
Valve excised. Please place it
on the tray.
Now place the artificial valve in
its proper location.
The artificial valve has been set.
You may now suture it in place.
Please place the valve more closely.
We don't have much margin for error.
What are you doing!? Place it where
the patient's valve was removed!
Good work. You're getting better
at suturing.
The valve transplant is complete.
Let's finish up here.
Is something wrong? You should be
able to suture the incision, now.
*sigh* What a relief...
The operation was a success.
Now she can play outside with
all of her friends.
Please close the incision.
Poor girl...she's too young to
go through something like this.
...Having someone cut open your
chest is so unnatural.
But something in that little heart
refused to give up...
Maybe it sounds silly, but I keep
thinking about it.
...The human body is truly amazing.


It is a Scheme interpreter that includes a REPL window. You need to download FParsec separately.
All the smarts for it come from this Wiki Book. I just ported the code to F# (and modified it a bit). I thought the comparison might be interesting, so here we go. Thanks to Tobias and Jose for reviewing the code, find one bug and suggest improvements.
The code is described in the series of blog posts starting here.
Before we start looking at the real code, here is what we are trying to accomplish in form of test cases. If you are a bit rusty on LISP syntax, you might want to try and see if you understand what it does.
Our goal is to make all this XUnit test cases pass. Each of the lists below contains the Scheme statement and the result to display in the REPL window.
open Xunit open Lisp.Repl open Lisp.Parser open Lisp.SymbolTable let eval env = evalString env >> showVal let initEnv () = primitiveBindings () |> loadStdLib let test tests = let env = initEnv () tests |> List.iter (fun (expr, result) -> Assert.Equal(result, eval env expr)) [<Fact>] let simpleEval() = let tests = [ "(+ 2 2)", "4" "(+ 2 (- 4 1))", "5" "(- (+ 4 6 3) 3 5 2)", "3" ] test tests [<Fact>] let errorCheck() = let tests = [ "(+ 2 \"two\")", "\"Invalid type: expected number, found \"two\"\"" "(+ 2)", "\"Expected 2 args; found values 2\"" "(what? 2)", "\"Getting an unbound variable: what?\"" ] test tests [<Fact>] let moreEval() = let tests = [ "(< 2 3)", "#t" "(> 2 3)", "#f" "(>= 3 3)", "#t" "(string=? \"test\" \"test\")", "#t" "(string=? \"abcd\" \"dsft\")", "#f" "(if (> 2 3) \"no\" \"yes\")", "\"yes\"" "(if (= 3 3) (+ 2 3 (- 5 1)) \"unequal\")", "9" "(cdr '(a simple test))", "(simple test)" "(car (cdr '(a simple test)))", "simple" "(car '((this is) a test))", "(this is)" "(cons '(this is) 'test)", "((this is) . test)" "(cons '(this is) '())", "((this is))" "(eqv? 1 3)", "#f" "(eqv? 3 3)", "#t" "(eqv? 'atom 'atom)", "#t" ] test tests [<Fact>] let assignement() = let tests = [ "(define x 3)", "3" "(+ x 2)", "5" "(+ y 2)", "\"Getting an unbound variable: y\"" "(define y 5)", "5" "(+ x (- y 2))", "6" "(define str \"A string\")", "\"A string\"" "(< str \"The string\")", "\"Invalid type: expected number, found \"A string\"\"" "(string<? str \"The string\")", "#t" ] test tests [<Fact>] let closure() = let tests = [ "(define (f x y) (+ x y))", "(lambda (\"x\" \"y\") ...)" "(f 1 2)", "3" "(f 1 2 3)", "\"Expected 2 args; found values 1 2 3\"" "(define (factorial x) (if (= x 1) 1 (* x (factorial (- x 1)))))", "(lambda (\"x\") ...)" "(factorial 10)", "3628800" "(define (counter inc) (lambda (x) (set! inc (+ x inc)) inc))", "(lambda (\"inc\") ...)" "(define my-count (counter 5))", "(lambda (\"x\") ...)" "(my-count 3)", "8" "(my-count 6)", "14" "(my-count 5)", "19" ] test tests [<Fact>] let predefinedFunctions() = let tests = [ "(map (curry + 2) '(1 2 3 4))", "(3 4 5 6)" "(filter even? '(1 2 3 4))", "(2 4)" ] test tests [<Fact>] let varargsCountCheck() = let tests = [ "(define (sum x y . lst) (fold + (* x y) lst))", "(lambda (\"x\" \"y\" . lst) ...)" "(sum 1 2 3)", "5" "(sum 1 1 1)", "2" "(sum 1 2)", "2" "(sum 1)", "\"Expected 2 args; found values 1\"" ] test tests
Usually, when I do blog posts that are all about code, I write them ‘bottom up’. I start talking about the most primitive types and functions and build up from there toward higher abstractions. I think this is a pretty common way of doing it.
For this series I’m going to try the opposite. I start with the code that creates the REPL window and move down from there toward the guts of the interpreter. I hold the opinion that, if the code is written right, this should be ok. The naming scheme and general structure of it should allow understanding it at different levels.
Or at least I hope so.
Let’s start from the main function. Depending on the number of arguments it either runs the REPL window or executes whatever is in the file passed in as the first argument using the other arguments as parameters.
[<EntryPoint>] let main(args: string[]) = match Array.toList args with | [] -> runRepl () | filename :: args -> runOne filename args 0
The latter case is coded in the below function. It first load all the primitive operators (i.e. ‘+’, ‘-‘ etc…) and the standard library. The word ‘load’ above is a little misleading. In reality it adds them to the environment. It then proceeds to add the arguments that were passed on. As the last step, it evaluates the ‘load’ command by using the newly created environment, it transforms the returned token to a string and prints it.
let runOne (filename : string) (args : list<string>) = let env = primitiveBindings () |> loadStdLib |> bindVars [ "args", List (List.map String args) ] List [Atom "load"; String filename] |> eval env |> showVal |> printStr
Running the REPL windows is equally simple. Load the primitive operators and the standard library, show a prompt and evaluate the input until the input is ‘Quit’.
let runRepl () = let env = primitiveBindings () |> loadStdLib until (fun s -> s = "Quit" || s = "quit") (fun () -> readPrompt "Lisp>>> ") (evalAndPrint env)
readPrompt is pretty simple:
let printStr (s: string) = Console.Write(s) let readPrompt (s: string) = printStr s ; Console.ReadLine ()
EvalAndPrint is written as a chain of functions (lookup the ‘>>’ operator in F#) and just evaluate the string, transform the result to a string, prints it and newline it.
let newLine () = Console.WriteLine() let evalAndPrint env = evalString env >> showVal >> printStr >> newLine
evalString parses the string and evaluates the expression. Note the exception management. This is a result of my decision of throwing an exception every time something goes wrong instead of using a monad to pass the state around. I think it is pretty clear, but haskellers might disagre. This is one of the main differences from the Haskell version.
let evalString env expr = try expr |> readExpr |> eval env with | LispException(error) -> String (showError error)
For the sake of completeness, here is until. Maybe there is a library function somewhere that I could have used?
let rec until pred prompter evaluator = let result = prompter () if not (pred result) then evaluator result until pred prompter evaluator
Back on the main flow of the code, loadStdLib just loads the standard file and returns the populated environment.
let loadStdLib env = eval env (List [Atom "load"; String "stdlib.scm"]) |> ignore env
primitiveBindings creates a new empty environment and adds a bunch of pairs (primitiveName, LispVal –> LispVal). LispVal is a representation of a Scheme expression, so the second part of the tuple is simply a reduction from one expression to another (hopefully simpler in some sense). We’ll talk more about LispVal in upcoming posts.
let primitiveBindings () = (nullEnv ()) |> bindVars [ for v, f in primitives -> v, PrimitiveFunc f ]
There you have it. That’s the full implementation for the REPL window. Next post, we’ll look at LispEval and the evaluator.


Choose Spectrum Files
Spectrum File:
No spectrum file selected
Cysteine protecting group
Carbamidomethylation(+57)
NIPIA(+99)
Protease
Trypsin
Chymotrypsin
Other
Parent mass tolerance:
Da
between 0 and 2.5>
Ion tolerance:
Da
between 0 and 1>
Current Spectrum Files
File Name
PM Tolerance
Ion Tolerance
Protease
Database Options
HeavyChain
LightChain
Include common contaminants
Project Name


Year-end jumbo lottery tickets go on sale with ¥1 bil up for grabs
TOKYO — Year-end jumbo lottery tickets went on sale across Japan on Wednesday, drawing long lines at sales booths. One billion yen in prize money is up for grabs, with the top prize being 700 million yen.
As usual, the biggest line was at Tokyo’s Nishi-Ginza where more than 600 people were already waiting when the booth opened at 8:30 a.m. Throughout the day, the waiting time averaged 90 minutes. The Nishi-Ginza booth is popular because it has sold a number of winning tickets in the past.
The first person in line was a company employee from Katsushika Ward in Tokyo. He said he had got there at 5 a.m. He said if he won a substantial amount of prize money, he would buy a camper van and explore Japan.
Tickets for a Jumbo Mini Lottery also went on sale, with 50 million yen in prize money.
Lottery tickets, which cost 300 yen, will be sold through Dec 21 and winning numbers will be announced on Dec 31.
For details on the prize money allocation, click here.
© Japan Today


In this example, Select Puncher sets the default selected option (Sprite) on build.
This example uses a select with both values and strings. (<option value="0">Zero</option>) Value gets saved, but you see html().
This example displays the use of customization. Look at thepower.js where #myform_colors is bound.


array sqlite_fetch_column_types ( string $table_name , resource $dbhandle [, int $result_type = SQLITE_ASSOC ] )
Return an array of column types from a particular table
Returns an array of column data types; FALSE on error. The column names returned by SQLITE_ASSOC and SQLITE_BOTH will be case-folded according to the value of the sqlite.assoc_case configuration option.


#include <wglext.h>
Public Attributes | |
| DWORD | cb |
| CHAR | DeviceName [32] |
| CHAR | DeviceString [128] |
| DWORD | Flags |
| RECT | rcVirtualScreen |
Definition at line 388 of file wglext.h.
| DWORD _GPU_DEVICE::cb |
| CHAR _GPU_DEVICE::DeviceName[32] |
| CHAR _GPU_DEVICE::DeviceString[128] |
| DWORD _GPU_DEVICE::Flags |


Deployment Guide
Overview
This document describes how to deploy and use the Qt Virtual Keyboard plugin with Qt 5 applications.
Deployment
The Qt Virtual Keyboard plugin must be properly deployed before it can be used. The easiest approach to deployment is to add a deployment step in Qt Creator that executes the make install
command.
make install
deploys the files in the following locations:
| Item | Desktop install path | Boot2Qt install path |
|---|---|---|
| qtvirtualkeyboardplugin | $$[QT_INSTALL_PLUGINS]/platforminputcontexts | /system/plugins/platforminputcontexts |
| qtvirtualkeyboardplugin QML files | $$[QT_INSTALL_QML]/QtQuick/VirtualKeyboard | /system/qml/QtQuick/VirtualKeyboard |
| qtvirtualkeyboardstylesplugin | $$[QT_INSTALL_QML]/QtQuick/VirtualKeyboard/Styles | /system/qml/QtQuick/VirtualKeyboard/Styles |
Integration Method
Qt Virtual Keyboard currently supports two alternative integration methods for using the plugin:
Desktop
: Qt Virtual Keyboard is integrated with Qt 5 and requires no changes to existing applications. The Qt Virtual Keyboard input method is available to all of the Qt 5 applications in the system.In this integration method, the keyboard is shown in a dedicated top-level window.
Application
: Qt Virtual Keyboard is integrated with Qt 5, but requires changes to particular applications using Qt Virtual Keyboard. This method is mandatory in a Boot2Qt environment, but can be used in desktop applications too.In this integration method, the keyboard is shown in the same Qt Quick scene as the application.
The integration method is automatically selected by the project files. However, in desktop environments, it is possible to override the desktop integration method and use the application integration method instead, by adding CONFIG+=disable-desktop
to the qmake
command line.
Note: The desktop integration method is not currently available in Boot2Qt environments.
Loading the Plugin
In both integration methods, the application must use the QT_IM_MODULE
environment variable to load the plugin. For example:
$ QT_IM_MODULE=qtvirtualkeyboard myapp
or in the main() function:
qputenv("QT_IM_MODULE", QByteArray("qtvirtualkeyboard"));
In the desktop integration method, this step is all that is required to use Qt Virtual Keyboard. In the application integration method, the application is required to create an instance of InputPanel as explained in the following chapter.
Creating InputPanel
The following example shows how to create an InputPanel and how to divide the screen area with the application container.
import QtQuick 2.0 import QtQuick.VirtualKeyboard 2.1 Item { id: root Item { id: appContainer anchors.left: parent.left anchors.top: parent.top anchors.right: parent.right anchors.bottom: inputPanel.top ... } InputPanel { id: inputPanel y: Qt.inputMethod.visible ? parent.height - inputPanel.height : parent.height anchors.left: parent.left anchors.right: parent.right } }
The input panel must be a sibling element next to the application container. It is important not to put the input panel within the application container, as it would then overlap with the contents of the application. Also, the input panel height will be automatically updated according to the available width; the aspect ratio of the input panel is constant.
Environment Variables
There are several environment variables defined by the module that are listed below:
| Variable | Purpose |
|---|---|
| QT_VIRTUALKEYBOARD_HUNSPELL_DATA_PATH | Overrides the location of the Hunspell data files. The default location depends on the value of See Hunspell Integration for more information. |
| QT_VIRTUALKEYBOARD_PINYIN_DICTIONARY | Overrides the location of the Pinyin dictionary. The default location depends on the value of |
| QT_VIRTUALKEYBOARD_CANGJIE_DICTIONARY | Overrides the location of the Cangjie dictionary. The default location depends on the value of |
| QT_VIRTUALKEYBOARD_ZHUYIN_DICTIONARY | Overrides the location of the Zhuyin dictionary. The default location depends on the value of |
| QT_VIRTUALKEYBOARD_PHRASE_DICTIONARY | Overrides the location of the phrase dictionary. The default location depends on the value of |
| QT_VIRTUALKEYBOARD_STYLE | Specifies the location of the style to use with the virtual keyboard. This can also be specified in QML by setting VirtualKeyboardSettings::styleName, or at build time by using the qmake configuration options. |
| QT_VIRTUALKEYBOARD_LAYOUT_PATH | Specifies the location of the layouts to be used with the virtual keyboard. |
| LIPI_ROOT | Specifies the location of lipi-toolkit. The default location depends on the value of |
| LIPI_LIB | Specifies the location of lipi-toolkit plugins. The default location depends on
|


public interface Statement
This interface is typically implemented by a MondrianOlap4jStatement, but not necessarily: statements may be created internally, not via olap4j.
Not part of Mondrian's public API. This class may change without notice.
| Modifier and Type | Method and Description |
|---|---|
void |
cancel()
Issues a cancel request on this statement.
|
void |
checkCancelOrTimeout()
Deprecated.
This method will be removed in mondrian-4.0; use
Execution.checkCancelOrTimeout() |
void |
close()
Closes this statement.
|
void |
enableProfiling(ProfileHandler profileHandler)
Enables profiling.
|
void |
end(Execution execution)
Ends the current execution.
|
Execution |
getCurrentExecution()
Returns execution context if currently executing, null otherwise.
|
long |
getId()
Returns the ID of this statement, unique within the JVM.
|
RolapConnection |
getMondrianConnection()
Returns this statement's connection.
|
ProfileHandler |
getProfileHandler() |
Object |
getProperty(String name) |
Query |
getQuery() |
long |
getQueryTimeoutMillis()
Returns the query timeout of this statement, in milliseconds.
|
RolapSchema |
getSchema()
Returns this statement's schema.
|
SchemaReader |
getSchemaReader()
Returns this statement's schema reader.
|
void |
setQuery(Query query) |
void |
setQueryTimeoutMillis(long timeoutMillis)
Sets the timeout of this statement, in milliseconds.
|
void |
start(Execution execution)
Starts an execution.
|
void close()
SchemaReader getSchemaReader()
RolapSchema getSchema()
RolapConnection getMondrianConnection()
Query getQuery()
void setQuery(Query query)
void enableProfiling(ProfileHandler profileHandler)
Profiling information will be sent to the given writer when
Result.close()
is called.
If profileHandler is null, disables profiling.
profileHandler
- Writer to which to send profiling informationProfileHandler getProfileHandler()
void setQueryTimeoutMillis(long timeoutMillis)
Zero means no timeout.
Contrast with JDBC's Statement.setQueryTimeout(int)
method, which uses an int
value and a granularity of seconds.
timeoutMillis
- Timeout in millisecondslong getQueryTimeoutMillis()
Zero means no timeout.
Contrast with JDBC's Statement.getQueryTimeout()
method, which uses an int
value and a granularity of seconds.
void checkCancelOrTimeout()
Execution.checkCancelOrTimeout()
void cancel() throws SQLException
Once the thread running the statement detects the cancel request,
execution will throw an exception. See
BasicQueryTest.testCancel
for an example of usage of this
method.
SQLException
- on errorExecution getCurrentExecution()
void end(Execution execution)
execution
- Execution; must match the execution that was startedIllegalArgumentException
- if not started,
or if execution does not matchvoid start(Execution execution)
execution
- Execution contextlong getId()


Account History for {{ account }}
| Date & Time | Name | Members | Can Shop? | EBT Only? | Deposit | Balance Limit | Shared Address | Note |
|---|---|---|---|---|---|---|---|---|
| {{ revision.timestamp }} | {{ revision.name }} | {% for member in revision.members.all %} {% endfor %} | {{ revision.can_shop }} | {{ revision.ebt_only }} | {{ revision.deposit }} | {{ revision.balance_limit }} | {{ revision.shared_address }} | {{ revision.note|linebreaks }} |


Use this form whenever you're bored
Please pick a category
Education
Recreational
Social
Do it yorself
Charity
Cooking
Relaxation
Music
Busywork
Submit
Education
Recreational
Social
Do it yoursel
Charity
Cooking
Relaxation
Music
Busywork


the and hepatitis {background for margin {border-style px;} #ffffff;} are countries that with European viral health have infections people px; {font-family Health Hepatitis WHO font-size infection through which double; public says their virus who border-color border-width inject prevalence solid; such transmitted treatment {font-style {font-weight Duffell The World access any article bold comprehensive courier; em; focus other progress pt;} reduction these this threat