--- layout: default title: Links to Stuff permalink: /links/ ---
Below are a few of my favorite sites to visit. I have them linked, not only to create easy access for myself, but to hopefully direct some visitors there. Fair warning, its mostly baseball stuff.
|
csfbl |
fantasy league |
|
|
fangraphs |
the ringer |
|
|
fivethirtyeight |
baseball reference |


slow.trade Privacy Policy
Last updated: December 2018
We are delighted that you have chosen to use our Platform. We take our data
protection responsibilities with the utmost seriousness and we have designed our site so that you may
navigate and use it without having to provide Personal Data.
This Privacy Policy (the “Policy”) sets out what Personal Data we collect, how we process it and how long we retain it.
This Policy is applying to all of our processing activities where we act as a data controller.
In this Policy, "we", "us" and "our" refers to d.ex
OÜ, a company incorporated in Estonia under company registration No. No. 14553524 with its registered
address at Ahtri 12, Kesklinna District, 10151 Tallinn, Harju County, Estonia. For more information about
us, see the Contact Us section of this policy.
In this Policy, “Personal Data” means any information relating to you as
an identified or identifiable natural person (“Data Subject”); an identifiable natural person is one who can be identified, directly or indirectly, in
particular by reference to an identifier such as a name, an online identifier or to one or more factors
specific to your physical, physiological, genetic, mental, economic, cultural or social identity.
In this Policy, “Processing” means any operation or set of operations
which is performed on Personal Data (as defined in this Privacy Policy) or on sets of Personal Data, whether
or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or
alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making
available, alignment or combination, restriction, erasure or destruction.
Capitalized terms used but not defined here have the respective meanings given
to them in the Terms
and Conditions.
- NAVIGATING THIS POLICY
- You can click on the below links to jump to the relevant section:
- YOUR INFORMATION AND THE BLOCKCHAIN
- Blockchain technology, also known as distributed ledger technology (or simply
“DLT”), is at the core of our business. Blockchains are decentralized and made up of
digitally recorded data in a chain of packages called “blocks”. The manner in which these
blocks are linked is chronological, meaning that the data is close to impossible to alter once
recorded. Since the ledger may be distributed all over the world (across several ‘nodes’
which usually replicate the ledger) this means there is no single person making decisions or otherwise
administering the system (such as an operator of a cloud computing system), and that there is no
centralized place where it is located either.
- Accordingly, by design, a blockchain’s records cannot be changed or
deleted and is said to be ‘immutable’. This may affect your ability to exercise your rights
such as your right to erasure (‘right to be forgotten’), or your rights to object or
restrict Processing, of your personal data. Data on the blockchain cannot be erased and cannot be
changed. Although smart contracts may be used to revoke certain access rights, and some content may be
made invisible to others, it is not deleted.
- In certain circumstances, when interacting with the DutchX Decentralised Trading
Protocol (the “Protocol”) as further
defined in the Terms such as delivery of tokens it will be necessary to write certain personal data,
such as your Ethereum or other cryptocurrency wallet address, onto the blockchain; this is done through
a smart contract and requires you to execute such transactions using your wallet’s private
key.
- In most cases, the ultimate decision to (i) transact on the Ethereum
Blockchain using your Ethereum or other cryptocurrency wallet address, as well as to (ii) share the
public key relating to your Ethereum or other cryptocurrency wallet address with anyone (including us)
rests with you.
 THE ETHEREUM BLOCKCHAIN IS AVAILABLE TO
THE PUBLIC AND ANY PERSONAL DATA SHARED ON IT WILL BECOME PUBLICLY AVAILABLE.
- HOW WE USE PERSONAL DATA
- When visiting our website
- We may collect and process Personal Data about your use of our website. This
data may include:
- the browser types and versions used;
- the operating system used by the accessing system;
- the website from which an accessing system reaches our website (so-called
referrers);
- behaviour: subpage, duration, and revisit;
- the date and time of access to our website;
- the Internet protocol address (“IP
address”);
- the Internet service provider of the accessing system; and
- any other similar data and information that may be used in the event of
attacks on our information technology systems.
- This Personal Data may be processed in order to deliver the content of our
site correctly, to optimize the content of our site to ensure the long-term viability of our information
technology systems and website technology, and to provide law enforcement authorities with the
information necessary for criminal prosecution in case of a cyber-attack.
- The legal basis for this processing is our legitimate business interests,
namely monitoring and improving our website and the proper protection of our business against risks and
your consent when agreeing to accept cookies.
- When using slow.trade
- Slow.trade is a graphical interface and trading platform (the
“Platform”), that helps you interact via a
Wallet with the DutchX Decentralized Trading Protocol for ERC-20 tokens (the “DutchX Protocol”).
- When submitting trades via the slow.trade Platform we may collect and
process Personal Data. The data will be stored in different instances.
- On the Ethereum Blockchain following data will be stored:
- your wallet address;
- trade data (timestamp, sell and bought token
(amount and kind));
- Liquidity contribution (OWL detection, liquidity contribution settled in
OWL, MGN generated, liquidity contribution reduction based on MGN and liquidity contribution settled in
participating Supported Tokens).
- The data will be stored on the Ethereum Blockchain. Given the technological
design of the Ethereum Blockchain, as explained in Section 2, this data will become public and it will
not likely be possible to delete or change the data at any given time.
- Furthermore, we will store log data which include:
- the Internet protocol address (“IP address”); and
- browser description.
- This Personal Data may be processed in order to deliver the functionality of
the product. The legal basis for this Processing is that it is necessary to fulfil a contract with you
and our legitimate business interests, namely monitoring and improving our service.
- Other uses of your Personal Data
- We may process any of your Personal Data where it is necessary to establish,
exercise, or defend legal claims. The legal basis for this Processing is our legitimate interests,
namely the protection and assertion of our legal rights, your legal rights and the legal rights of
others.
- Further, we may process your Personal Data where such Processing is
necessary in order for us to comply with a legal obligation to which we are subject. The legal basis for
this Processing is our legitimate interests, namely the protection and assertion of our legal
rights.
- USE OF THIRD PARTY APPLICATIONS
- Ethereum Blockchain
- When participating in the DutchX Protocol via the slow.trade Platform, your
Wallet address, trade data, and liquidity contribution will be stored on the Ethereum Blockchain. See
Section 2 of this Policy.
- The data will be stored on the Ethereum Blockchain. Given the technological
design of the blockchain, as explained in section 2, this data will become public and it will not likely
be possible to delete or change the data at any given time.
- Wallet provider
- As further set out in the Terms & Conditions, to use the slow.trade
Platform to trade on the DutchX Protocol, you will have to connect with your Wallet. Recommended Wallets
are listed in the Terms & Conditions and may change from time to time. Wallet providers may collect
and store Personal Data. For example, data collected by MetaMask may include:
- network information;
- the first wallet address created through the MetaMask plugin;
- interaction with the site is also documented via a MetaMask Google Analytics
account.
- If you have chosen highest browser permission settings
for your web browser, this could also lead to procurements of more Personal Data.
- For further information and the applicable data protection provisions of
MetaMask, please visit https://metamask.io/privacy.html.
- Please check the privacy policy of your allet provider before injecting to the slow.trade platform.
- Amazon Web Server
- We use the Amazon Web Server (AWS) to store, log and database data as described
in Section 3.2 c). For further information and the applicable data protection provisions of AWS please
visit https://aws.amazon.com/privacy/?nc1=f_pr .
- API
- For information purposes, we note here that the DutchX Protocol offers a range
of additional Services, including the provision of an Application Programming Interface site
(“API”) at https://dutchx.d.exchange/api, which offers anyone easy access to the public information contained on the Ethereum Blockchain
regarding the DutchX Protocol .
- The API enables everyone to access the information of the DutchX Protocol smart
contracts including:
- balances of the users for the different tokens, including locked MGN;
- information about the tokens listed on the DutchX Protocol and the ones that
generate MGN;
- information about the auctions: sell volumes, buy volumes, start dates,
closing prices; and
- information about the deposits, sell orders, buy orders, liquidity
contribution level applied, dates, and
- address of the trade, as well as information about the claiming and
generation of MGN.
- SHARING YOUR PERSONAL DATA
- We may pass your information to our Business Partners, administration
centres, third party service providers, agents, subcontractors and other associated organisations for
the purposes of completing tasks and providing our services to you.
- In addition, when we use any other third-party service providers, we will
disclose only the Personal Data that is necessary to deliver the service required and we will ensure,
via contractual obligations that these require them to keep your information secure and not to use it
for their own direct marketing purposes.
- In addition, we may transfer your Personal Data to a third party as part of a
sale of some, or all, of our business and assets or as part of any business restructuring or
reorganisation, or if we are under a duty to disclose or share your personal data to comply with any
legal obligation. However, we will take steps to ensure that your privacy rights continue to be
protected.
- TRANSFERRING YOUR DATA OUTSIDE OF THE EU
- The log data collected when using our service will the stored in our Amazon
Web Server, which is based in the US. Amazon is certified under the EU- US Privacy Shield.
- As explained above in this Policy, the Ethereum Blockchain is a global
decentralised public network and accordingly any personal data written onto the Ethereum Blockchain may
be transferred and stored across the globe.
- EXISTENCE OF AUTOMATED DECISION-MAKING
- We do not use automatic decision-making or profiling when Processing Personal
Data.
- DATA SECURITY
- We have put in place appropriate security measures to prevent your Personal
Data from being accidentally lost, used or accessed in an unauthorised way, altered or disclosed. In
addition, we limit access to your Personal Data to those employees, agents, contractors and other third
parties who have a business need to know. They will only process your Personal Data on our instructions
and they are subject to a duty of confidentiality.
- We have put in place procedures to deal with any suspected Personal Data
breach and will notify you and any applicable regulator of a breach where we are legally required to do
so.
- YOUR RIGHTS AS A DATA SUBJECT
- You have certain rights under applicable legislation, and in particular under
Regulation EU 2016/679 (General Data Protection Regulation or “GDPR”). We explain these below. You can find out more about the
GDPR and your rights by accessing the European
Commission’s website.
- Right Information and access
- You have a right to be informed about the Processing of your Personal Data (and if you did not give it to us, information as
to the source) and this Policy intends to provide the information. Of course, if you have any further
questions you can contact us on the above details.
- Right to rectification
- You have the right to have any inaccurate Personal Data about you rectified and
to have any incomplete Personal Data about you completed. You may also request that we restrict the
Processing of that information.
- The accuracy of your information is important to us. If you do not want us to
use your Personal Data in the manner set out in this Policy, or need to advise us of any changes to your
Personal Data, or would like any more information about the way in which we collect and use your
Personal Data, please contact us at the above details.
- Right to erasure (right to be ‘forgotten’)
- You have the general right to request the erasure of your Personal Data in the
following circumstances:
- the Personal Data is no longer necessary for the purpose for which it was
collected;
- you withdraw your consent to consent based Processing and no other legal
justification for Processing applies;
- you object to Processing for direct marketing purposes;
- we unlawfully processed your Personal Data; and
- erasure is required to comply with a legal obligation that applies to us.
- However, when interacting with the Ethereum Blockchain, as explained above
in this Policy, it will likely not be possible to erase and permanently delete Personal Data which has
been written onto the Ethereum Blockchain. In these circumstances, we will use our reasonable endeavors
to ensure that all personal data held by us is permanently deleted however, notwithstanding this, your
right to erasure may not be able to be fully enforced.
- We will proceed to comply with an erasure request without delay unless
continued retention is necessary for:
- exercising the right of freedom of expression and information;
- complying with a legal obligation under EU or other applicable law;
- the performance of a task carried out in the public interest;
- archiving purposes in the public interest, scientific or historical research
purposes, or statistical purposes, under certain circumstances; and/or
- the establishment, exercise, or defence of legal claims.
- Right to restrict Processing and right to object to Processing
- You have a right to restrict Processing of your Personal Data, such as
where:
- you contest the accuracy of the Personal Data;
- where Processing is unlawful you may request, instead of requesting erasure,
that we restrict the use of the unlawfully processed Personal Data;
- we no longer need to process your Personal Data but need to retain your
information for the establishment, exercise, or defence of legal claims.
- You also have the right to object to Processing of your Personal Data under
certain circumstances, such as where the Processing is based on your consent and you withdraw that
consent. This may impact the services we can provide and we will explain this to you if you decide to
exercise this right.
- However, when interacting with the Ethereum Blockchain, as explained above
in this Policy, it will not likely be able to prevent external parties from Processing any Personal Data
which has been written onto the Ethereum Blockchain. In these circumstances we will use our reasonable
endeavors to ensure that all Processing of Personal Data held by us is restricted, notwithstanding this,
your right to restrict to Processing may not be able to be fully enforced.
- Right to data portability
- Where the legal basis for our Processing is your consent or the Processing is
necessary for the performance of a contract to which you are party or in order to take steps at your
request prior to entering into a contract, you have a right to receive the Personal Data you provided to
us in a structured, commonly used and machine-readable format, or ask us to send it to another
person.
- Right to freedom from automated decision-making
- As explained above, we do not use automated decision-making, but where any
automated decision-making takes place, you have the right in this case to express your point of view and
to contest the decision, as well as request that decisions based on automated Processing concerning you
or significantly affecting you and based on your personal data are made by natural persons, not only by
computers.
- Right to object to direct marketing (‘opting out’)
- You have a choice about whether or not you wish to receive information from
us.
- We will not contact you for marketing purposes unless:
- you have a business relationship with us, and we rely on our legitimate
interests as the lawful basis for Processing (as described above);
- you have otherwise given your prior consent (such as when you download one of
our guides).
- You can change your marketing preferences at any time by contacting us on the
above details. On each and every marketing communication, we will always provide the option for you to
exercise your right to object to the Processing of your Personal Data for marketing purposes (known as
‘opting-out’) by clicking on the ‘unsubscribe’ button on our marketing emails or
choosing a similar opt-out option on any forms we use to collect your data. You may also opt-out at any
time by contacting us on the below details.
- Please note that any administrative or service-related communications (to offer
our services, or notify you of an update to this Policy or the Terms and Conditions , etc.) will solely
be directed at our clients or business partners, and such communications generally do not offer an
option to unsubscribe as they are necessary to provide the services requested. Therefore, please be
aware that your ability to opt-out from receiving marketing and promotional materials does not change
our right to contact you regarding your use of our site and Platform or as part of a contractual
relationship we may have with you.
- Right to request access
- You also have a right to access information we hold about you. We are happy to
provide you with details of your Personal Data that we hold or process. To protect your Personal Data,
we follow set storage and disclosure procedures, which mean that we will require proof of identity from
you prior to disclosing such information. You can exercise this right at any time by contacting us on
the above details.
- Right to withdraw consent
- Where the legal basis for Processing your Personal Information is your consent,
you have the right to withdraw that consent at any time by contacting us on the above details.
- Raising a complaint about how we have handled your Personal Data
- If you wish to raise a complaint on how we have handled your personal data, you
can contact us as set out above and we will then investigate the matter.
- Right to lodge a complaint with a relevant supervisory authority
- If we have not responded to you within a reasonable time or if you feel that
your complaint has not been resolved to your satisfaction, you are entitled to make a complaint to the
Data Protection Commissioner under the Data Protection Act, which is presently the Estonian Data Protection Inspectorate - Andmekaitse Inspektsioon (“AI”). You may contact the AI on the below details:
Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon)
Väike-Ameerika 19
10129 Tallinn
Estonia
Tel. +372 6274 135
Fax +372 6274 137
e-mail<EMAIL_ADDRESS>website: http://www.aki.ee/en
- You also have the right to lodge a complaint with the supervisory authority in
the country of your habitual residence, place of work, or the place where you allege an infringement of
one or more of our rights has taken place, if that is based in the EEA.
- STORING PERSONAL DATA
- We retain your Personal Data only for as long as is necessary for the purposes for which we process the
information as set out in this Policy.
- However, we may retain your Personal Data for a longer period of time where such
retention is necessary for compliance with a legal obligation to which we are subject, or in order to
protect your vital interests or the vital interests of another natural person.
- CHANGES TO THIS PRIVACY POLICY
- We may make changes to this Policy from time to time. Where we do so, we will
notify those who have a business relationship with us or who are subscribed to our emailing lists, if
any, directly of the changes, and change the ‘Last updated’ date above. We encourage you to
review the Policy whenever you access or use our site to stay informed about our information practices
and the choices available to you. If you do not agree to the revised Policy, you should discontinue your
use of our Site and Platform.
- OUR DETAILS
- This website is owned and operated by d.ex OÜ. We are registered in Estonia
under Company registration No. 14553524, and our registered office is located at Ahtri 12, Kesklinna District, 10151 Tallinn, Harju County, Estonia.
- If you have any queries concerning your rights under this Privacy Policy, please
contact us at dataprotection@slow.trade.


Yes. We only have professionals who have necessary qualification & experience and been recommended and certified by experts. We conduct interview, check referrals for all the professionals/technicians.
We will arrange for a replacement professional and work with you to schedule a visit convenient with you to do the job or you can also cancel the service requested.
We at Mygharseva understand that your time is valuable and we are determined to limit the time spent by professional at your place. If the time for service is going to be more than planned, the professional will communicate the same to you.
Yes we do on all holidays except national holidays. Our services are available everyday* from 10 AM to 8 PM *Note: Except for some uncertain circumstance which may interrupt our functioning.
You can login to our website and make a payment using your debit or credit card, or through net banking.
We have started the service in Pune. We will soon expand our service in 4 more cities.
All of our service providers have passed through a rigorous assessment process. In the unlikely event of them breaking something we provide an insurance claim of up to Rs.5000.
If any supplies are required, the professional/technician would discuss the same with you and only upon your confirmation, he/she will purchase the supplies. Supplier will always provide you bill of the purchases made.
We have made it simple for you. When you provide your information like address, phone number and email ID, you will be automatically registered on mygharseva site. Don’t worry about unnecessary calls or messages from us.
After each service is completed, we request customers to rate our overall service performance.
A listing of tasks that are covered under the service charge for a service can be found on the respective pages.


{{/* This template is used to render the set of changes in the changelog page. If this version of the spec is unstable, it expects to find a "changelog/newsfragments" directory containing all unreleased changes, and renders them all. Otherwise it expects to find a "changelog/releases" directory, under which is one or more directories whose name is a patch number, like "0", "1", and so on. It renders each of these subdirectories as a separate patch, including a table containing basic info about that patch and the set of changes in it. */}} {{ $path := path.Join "changelog" }} {{ $config_file := path.Join $path "pyproject.toml" }} {{ $config := readFile $config_file | transform.Unmarshal }} {{ $status := .Site.Params.version.status }} {{ if eq $status "unstable" }} {{ $news_path := path.Join $path "newsfragments" }} {{ partial "render-newsfragments" (dict "config" $config "news_path" $news_path )}} {{ else }} {{ $releases_path := path.Join $path "releases" }} {{ $major_version := .Site.Params.version.major_version }} {{ $minor_version := .Site.Params.version.minor_version }} {{ $releases := partial "reverse-slice" (readDir $releases_path) }} {{ range $releases }} {{ if .IsDir }}
| Git commit | https://github.com/matrix-org/matrix-doc/tree/{{ $release_info.tag }} |
|---|---|
| Release date | {{ $release_info.date }} |


| # | Name | Description | OwnerApp | Input Keys | Output Keys | Metadata | JSON | Details | Action | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| #{{ ((current_page_selected-1)*page_size) + taskDefCounter+1}} | {{taskDef.description}} | {{taskDef.ownerApp}} | Orphan |
Input Parameter(s)
Total of {{taskDef.inputKeys.length}} Params Found
|
Output Parameter(s)
Total of {{taskDef.outputKeys.length}} Params Found
|
TaskDef MetadataOwner App
Execution Name Space
Timeout Seconds
Response Timeout Seconds
Concurrent Exec Limit
Retry Count
Timeout Policy
Retry Logic
Retry Delay Seconds
Rate Limit Per Frequency
Rate Limit Frequency In Seconds
Isolation Group Id
Create Time
Update Time
Created By
Updated By
|
TaskDef JSON |
Action Confirmation
Are you sure you want to delete the Task Definition ?NOTE: The task definition will not be checked for the workflows it is part of and the impact is not considered while deleting the task definition. It is left to user discretion. Task Details
{{error_message}}
{{result}}
|


Escape Hatch
Escape Hatch is an NPM library and website that instantly connects developers with relevant information to help cut down on debugging time.
Escape Hatch is an NPM library and website that instantly connects developers with relevant information to help cut down on debugging time.
A chatbot for all things Git and GitHub with Slack integration.
A mock holiday eCommerce site.


Scary Movie (2000) 3 1/2 stars out of 4. Starring Jon Abrahams, Carmen Electra, Shannon Elizabeth, Anna Faris, Kurt Fuller, Cheri Oteri, Marlon Wayans, Shawn Wayans and Regina Hall. Written by Phil Beauman, Jason Friedberg, Buddy Johnson, Aaron Seltzer, Marlon Wayans and Shawn Wayans. Directed by Keenan Ivory Wayans. Rated R. Running time: about 88 minutes.
"Scary Movie" sets new highs in low comedy.
It is crude, vulgar and provides something to offend everyone - blacks, women, teens, gays, lesbians, the mentally challenged, cops and teachers.
"Scary Movie" also is the funniest movie of the year, a shameless, unapologetic, savage spoof of teen slasher flicks such as "Scream," "I Know What You Did Last Summer," their sequels and various rip-offs, as well as a satiric tip of the cap to "The Sixth Sense," "The Blair Witch Project" and "The Matrix."
Despite all its crassness, "Scary Movie" is a very smart and expertly done burlesque, ranking with the likes of "Blazing Saddles," "Young Frankenstein" and "Airplane."
Director Keenan Ivory Wayans, with the help of six screenwriters, has created a movie that not only lampoons the genre's well-worn formulas, but does so by reproducing the cinematic techniques familiar from those films: the closeup of the hand reaching for the locked door, the character who suddenly jumps into frame, the telephone unexpectedly ringing, and so on.
Usually when you see six names in a writing credit, it means trouble; the cliché about too many cooks is true, especially in screenwriting. But "Scary Movie" is an exception. The movie has a cohesiveness and single-minded focus that is maintained from opening reel to closing credits - and beyond. (Viewer alert: Do not leave after the end credits, there's more to see.)
This is one movie in which you cannot discuss the jokes. Most are too tasteless, involving various sexual organs, bodily functions and fluids, appliances and garden tools. Ironically, the nudity is held to a minimum, and it's mostly male.
The cast consists basically of young, bland performers, the types you usually find in such movies. The `Drew Barrymore cameo' role is played by Carmen Electra as the flatulent Drew.
Also in the cast are Marlon and Shawn Wayans, as well as "Saturday Night Live" regular Cheri Oteri as Gail Hailstorm, doing a broad spoof of Courtney Cox's "Scream" news reporter, Gail Weathers.
Oteri also figures in a wild salute to "The Blair Witch Project" that will leave you reaching for a hankie and laughing until you hurt.
For a film buff such as myself, there is nothing as satisfying as a top-notch sendup. And "Scary Movie" fits that description. I laughed from beginning to end, not only at the jokes, but at the recognition of the ambiance created by director Wayans.
"Scary Movie" is hilarious. Filmgoers without a sense of humor or who are easily offended might as well stay home. This is not for you.
But for the rest of us who want to feel our bellies shake and we guffaw, giggle and scream with delight, "Scary Movie" scores a bulls-eye.
It's a gem, a small treasure, a bit tarnished as well as ribald, scatological and unrefined. And the first chance I get, I'm going to rush out and see it again. You'll want to do the same, I guarantee it.
Bob Bloom is the film critic at the Journal and Courier in Lafayette, IN. He can be reached by e-mail at<EMAIL_ADDRESS>or at<EMAIL_ADDRESS>Bloom's reviews can be found on the Internet Movie Database at: http://www.imdb.com/M/reviews_by?Bob+Bloom
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


Two Factor Authentication is already ENABLED for your account.
This options provides an extra level of security to your account. During login, you will be asked to enter a One Time Code obtained used Google Authenticator, Authy or similar apps. Please note that the code will be valid only for 30 seconds.
You can disable this option by clicking the below option. However, it's not recommended due to security concerns.
You have this option DISABLED.
Enabling Two Factor Authentication will make your account Highly Secure. We recommend to enable this option.


Welcome to the
Click here for more about
this website
Click here to go to the MCHS
website
Click here to go to the MCC
of OGS website
|
CDs of
important |
Monroe
1903
Dearth,
Lulu Dearth, nee Starlin
Source: The Marietta [Ohio] Daily Times; 11 May 1903
Mrs. George Dearth died at her home at 111 Ward street at 2
o'clock this morning. She had lung
trouble.
She was twenty-seven years of age and a daughter of Warren
Starling. She was a native of Marietta.
Funeral services are not yet announced.
Gatten, Rupert E. Gatten
Spirit of Democracy,
LKP#6
Sooner or later the death angel must enter into each home,
tearing asunder earthly ties and leaving the home sad and desolate.

In his wisdom, God has seen fit to pluck from earth this
little flower, and to transplant it in the beautiful paradise of glory. Little
Rupert lived upon earth and passed away without the guilt or knowledge of sin.
Therefore it is certain that he is safe in the arms of Jesus. He was sick for
only a week with typhoid fever. All that loving hands could do was done, but
all to no avail. God who gave him, called him home.

The funeral services were conveyed to Connor Ridge cemetery to
await the final summons at the last day.
Written by O.A. Dougherty
Highman, William H. Highman
Spirit of Democracy,
Once more has that unwelcome guest, Death, visited our
community and taken from it one of the noblest characters it possessed; a
character marked for its high degree of morality, its sense of honor, its love
of right, and its willingness at all times to do that which is considered to be
duty.
William H. Highman was born
The deceased was the son of Duncan and Sarah M. Highman and
leaves a father, mother, six brothers, one sister and a host of friends to
mourn the loss of a dutiful son, a loving brother and a kind friend.
The funeral services were conducted by James Cline at the home
of the deceased. Interment at the Connor Ridge cemetery
W. H .O.
Koehler, Mary
J. Koehler, nee Patterson
Source: The Spirit of Democracy Issue:
Mrs. Mary J. Koehler, relict of Frederick Koehler formerly
resided in Woodsfield, died at her home in
Kruse,
Carrie Kruse, nee Brown
Source: The Columbus [Ohio] Dispatch; 1 Sep 1903
BY HER OWN HAND,
MRS. CARRIE
KRUSE ENDS
HER LIFE.
Called the
Doctor and Then
Swallowed Fatal
Carbolic
Acid.
The body of Mrs. Carrie Kruse lies at the morgue next to
that of Mrs. Jennie Williams, who was murdered and that of Henry Fossbauk, who
died of heart disease. Mrs. Kruse, who
was only 20 years of age, committed suicide by taking carbolic acid at her
home.
During Monday night a telephone message came to Dr. Sims to
call at the woman's home right away.
Her step-father, Joseph George, lived at Columbus and Parsons avenues,
and heard a groan in the room occupied by Carrie and opened the door. As the door swung to the woman fell on the
step, saying, "I am going home."
She was taken into the house and Dr. C. T. Elder of 968 Parsons avenue,
was called. Dr. Sims of 593 Parsons
avenue who had got the message, arrived first and found that the woman had
swallowed carbolic acid. Everything
possible was done but she was too far gone and died in a very short time. The patrol wagon took her body to the morgue. It is said that Carrie had quarreled with
her husband, who works for the Columbus Iron and Steel company, and brooding
over her trouble had at last taken poison.
The coroner was notified.
Lallathin, Caroline Frederica Lallathin nee
Netting
On August
9, 1903 the angel of death visited the home of Brother John Lallathin and
claimed the spirit of his beloved wife, Sister Caroline Frederica
Lallathin. Sister Lallathin was born
July 1, 1823 in Wurtenberg, Gemany; aged at death 80 years, 1 month and 9
days. She was married to John Lallathin
September 13, 1844. To this union were
born 13 children, of whom seven have gone to their reward. In 1847 they came to
McCurdy, James D. McCurdy
Source: The
James D. McCurdy, the six months old son of Douglas
McCurdy, died at his home on the
McMahon, Isaac
McMahon
Source:
Newspaper clipping, Monroe County Ohio, July 1903.
Once more the death angel has visited the vicinity of
Miller, son of Clark and Everetta Hettie (Reed)
Miller
Source: The Canton [Ohio] Repository; Friday, March
6, 1903
Died at
Howenstine
The two-months' old child of Mr. and Mrs. Clark Miller, of
Howenstine, died there Wednesday.
Source: The Noble
Ada Zelma Moore, second daughter of Grant P. and Sarah A.
Moore, born April 13, 1900, died November 8, 1910, aged 10 years, seven months
and twenty-six days. She leaves a father, one brother and three sisters to
mourn her sad departure. Her mother passed over on the other shore just two
weeks before Zelma was called.  Oh, dear Zelma, how we miss
her, for she was a kind hearted child and loved by everybody. She will be missed as she was always
there. The remains were taken to the
Oh, Dear Zelma, how we miss you.
And your voice we loved is stilled
A place is vacant in the home,
Which never can be filled.
Morris, Philo D Morris
Elder Philo Morris was born April 6, 1853
in Noble Co.,
Several weeks ago he was confined to
his bed by a severe illness and though all was done for him by the best medical
skills and the loving attention of his family and relatives and friends, he
fell asleep in Jesus on Sunday evening at half past 8 o clock. *
He leaves a wife, daughter, two brothers
and two sisters to mourn their loss.
His departure from our midst is a loss to the Church and community.
The funeral services were held in the
Christian Church in our city, after which the body was taken to Sedgwick where
again services were held at the
Published in the
*Submitter
places the year of death at 1903.
Nesbitt, John P. Nesbitt
Waynesburg Republican,
Dr. J. P. Nesbitt died at the home of his brother in law, W.
T. Webb, Esq.,
Nesbitt, John P. Nesbitt
(2nd Obit)
Nebraska City New,
A telegram was received here
this morning announcing the death of Dr. John P Nesbitt, which occurred last
night at his home at
Schaub, Johannes (John) Schaub
Source: the original
newspaper clipping; October 1903
John Schaub, aged 77 years, died at his home in Summit
township Saturday. Deceased was a
member of the Lutheran church. He
leaves three sons. Funeral Monday
conducted by Rev. Theo A. Hafele of Woodsfield. Interment at Middle church.
Schaub, John Schaub
John
Schaub, aged 77 years, died at his home in
Thomas, James A. Thomas
James
A. Thomas died at the home of his parents, Samuel and Minerva Thomas of Duffy,
on February 8, 1903, at the age of twenty-five years. He had been employed at
An
aged father and mother, two sisters Mrs. Philip (Anna) Lively of Duffy and Mrs.
Joel (Martha) Jones of near Antioch and two borthers Louis B. Thomas of
Wheeling and Dr. Edward Thomas of Powhatan, besides numerous other relatives
and betrothed, Miss Minnie Wrenshaw of Triadelphia, W. Va., are left to mourn.
Funeral
services conducted by Mr. Haught of New Martinsville were held at 10 o clock on
the following Tuesday. Interment in
Last modified September 24, 2015 by BK.
Click here for the Short-Cut Table of Contents


Pi
How the heck can I describe the visceral experience that is "Pi"? It is a film I thoroughly enjoyed, but I recognize it contains too many elements that will intimidate those used to, say, more traditional fare. I can only hope that a movement will begin, whereas individuals will resist the temptation of the bland, assembly-line studio product, and try for something totally unique and delectable.
Who am I kidding?
The Greek letter "Pi" equals the ratio between the circumfrence of a circle to its diameter. Since this is something learned by tenth-graders, and most movies are made on a fourth-grade level, it should be expected that its core audience is limited. But even for the mathematically deficient, Pi is less about mathematics as it is a study in obsession, a visual representation of madness. It is "Eraserhead" meeting "Taxi Driver" with some "Wall Street" and "Yentl" thrown in for good measure.
It's protagonist, Maximillian Cohen, believes that mathematics is the true language of nature, and that every action in the world, no matter how random, is intricately ordered and patterned. Given this thesis, why not use this knowledge to try to predict the stock market? Such research draws attention from some shady investment banker types.
Although Max is an agnostic Jew, his faith more accurately reflects that of an "atheistic Calvinism". Even so, he draws the attention of Lenny Meyer, a Kaballah Jew, who explains that the Hebraic language is numeric and replete with symbolism, perhaps with the key to the meaning of life. Curiously, Max joins their sect, only to find that even they have ulterior motives.
Still with me? There's more. Max's computer, which occupies most of his apartment, crashes, leaving behind a printout of random numbers. Or are they?
And Max suffers from chronic headaches. And hallucinations. And drugs. And nosebleeds. And he spends far too much time isolated in his apartment. And I'm still not sure what he does for a living. And he may be going a little... mad.
Hello? Still there? Try this. The film was made for an astonishing low budget ($60,000), in a glaringly strong black and white. And is pulverized by a hypnotic, techno-soundtrack. This film screams, "Cult movie!"
Rarely does the majority of the moviegoing public go to a movie to, gasp, learn something. This audience may be intimidated by the apparent dryness in _Pi_'s plot. It's anything but. First timer Darren Aranofsky gets a lot of mileage out of his limitations. The picture is one of the most mesmerizing claustrophobic creations ever put to celluloid. The cinematography is stunning, the editing is superior, and there are fantastic close up images that we take for granted: a trembling thumb, an ant on a microchip, a dismembered brain. He deservedly won the director's prize at Sundance this year.
It's not impossible to make a good film based on mathematics (Good Will Hunting, The Spanish Prisoner, heck, even Jurassic Park). But rarely has a film been so engrossed in its own world, that you feel immersed in an entirely new reality. There's a lot of interesting ideas in _Pi_, coupled with some of the most breathtaking imagery and editing I've seen in a long time. Sean Gullette, playing Max, has a strong, eerie presence, and Ben Shenkman adds wonderful color as Lenny.
I have two problems with the film. There is this glaring gaffe where Max walks down a subway platform, where he is initially at the 50th Street station, and winds up at the exit for Prospect Park (only New Yorkers will catch that).
But these issues are microscopic in comparison to the greatness of this movie. Search it out. Now. Go to the latest showing. Please. Trust me. I double-dog dare you.
Nick Scale: 9 (if you're interested in mathematics, theology, stocks, board games, New Yorkers, philosophy, and non-conventional film-making). 7 (if not).
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


[Theme] Back to Battlelog 1.0 - Better Battlelog Forums #98723
Sitemap
15. May 2013 18:47
Post edited 3 x times, last by
T3RRORTOAST
Community Manager
22. July 2013 14:36
Topicstarter
T3RRORTOAST
Community Manager
development stopped
15.
15. May 2013 19:58
Topicstarter
T3RRORTOAST
Community Manager
Need the css for the old menu.


Lunch Menu
| North Indian Meals | 45/- |
|---|---|
|
|
| North Indian Executive Lunch | 75/- |
|
|
| Spl Parotta | 45/- |
|
|
| Veg Biriyani | 35/- |
|
|
| Parotta with Side Dish | 30/- |
|
|
| Chappathi with Side Dish | 35/- |
|
|
| Tamil Nadu meals | 36/- |
|
|
| Fast Lunch | 48/- |
|
Sweets
| 13/- | |
| 13/- | |
| 13/- | |
| 11/- | |
| 25/- | |
| 16/- |


A place for general developer talk – for everyone! | Documentation https://developers.komodoplatform.com | MoreDev Docs - https://docs.komodoplatform.com | Mastering CryptoConditions - https://github.com/KomodoPlatform/Mastering_CryptoConditions
100 messages
Before 05-Dec-19 12:00 AM
blackjok3r31-Jan-19 05:45 AM
There only needs to eb goo segid distribution if your a whale
I tested staking with a single address and -pubkey on some of CFEK chains... 50-60,000 txns in wallet
Alright31-Jan-19 05:46 AM
I don't understand why what I suggested isn't viable. I'm not saying it's absolutely necessary, just floating the idea
blackjok3r31-Jan-19 05:46 AM
I dont really understand what your asking... the tx HGAS TO BE the last utxo in the block... thats HOW it determines its a stked block... without that it will simply fail to work at all
Alright31-Jan-19 05:46 AM
essentially you would add input to staking verification tx of the coinbase itself and make validation compensate for this
blackjok3r31-Jan-19 05:46 AM
Im not chaging that
you can
Alright31-Jan-19 05:46 AM
lol
can't*
blackjok3r31-Jan-19 05:47 AM
I dont think you understand how hard that is
For basically no reason
Alright31-Jan-19 05:47 AM
Guess i don't
blackjok3r31-Jan-19 05:47 AM
it saves makeing 1 transacion
IF you want to stake that way... there are better way to stake than using that method
Alright31-Jan-19 05:47 AM
my concern is that the default staker will work fine for a week, a month, maybe 2
blackjok3r31-Jan-19 05:47 AM
that is just the easiest with decent results
Only if you stake lik 80% of all blocks
Its the walelt that breaks... not the staker
Alright31-Jan-19 05:48 AM
but then when user wants to add coins or withdraw coins, they will have problems from having too many utxos
it will mess up their distributed across segids
it just isn't clean
what I'm suggesting would keep a steady utxo count
blackjok3r31-Jan-19 05:49 AM
You cant have too manty until over 30-40,000
Alright31-Jan-19 05:49 AM
and just have them grow in size with each staked block
blackjok3r31-Jan-19 05:49 AM
thats reaching stupid whalet territory... noone should ahve that many coins on a real chain LOL
Alright31-Jan-19 05:49 AM
ok, I'm making problems where there aren't any
blackjok3r31-Jan-19 05:50 AM
The new ram staker and the corrupt wallet code fix should stop any of these issues you ahd on MGNX(edited)
Its really up to the user to decide hwo they awnt to stake... thats the whole idea of PoS64.... right ... if you make some methoid of staking default behaviour you forcce everyone to use it. And I'm tellingf you that method isnt the best one... I for one dont want to use it... lol
Alright31-Jan-19 05:52 AM
default behavior vs proper staking scripts is a huge difference
even the v1 staker.py makes a very large difference
which is basically the behavior I just described
blackjok3r31-Jan-19 05:53 AM
The ideal way to stake is to distribute utxos into segid that are more likely to stak in the future, not ones that have been lucky in the past.
Alright31-Jan-19 05:54 AM
I'm not sure the current staker is the proper way to accomplish that. I really need to figure out exactly how it works, but isn't it just checking which segids staked in the previous 100 blocks and distributing coins to the least staked segid?
if so, that doesn't quite make sense
because by the time that utxo is eligible to stake, another 100 blocks have happened
and your distribution is tweaked to the 100 previous blocks
blackjok3r31-Jan-19 05:55 AM
But you also need to take into account utxo age... so moving them too often is a terrible idea.
I tried to make somehting for mined blocks, that move utxos based on age and size into segids that have stked the least in the last 100 blocks.. its nto perfect it was mroe an example on how to use the RPCs...
Unless you ahev 5000+ utxos they dont work so well
Alright31-Jan-19 05:56 AM
once I have enough OUR to setup a couple decent staking nodes, I'll try a few different methods and log stats
blackjok3r31-Jan-19 05:56 AM
Thats the ebst idea... I was hopeing ppl onLABS would to that
give them the RPCs to get data and an example script
see who comes up with best staker... and ifg htey will share it back
Alternative implementation of spesmilo/electrum-server - cipig/electrumx
jl777c31-Jan-19 07:48 AM
Maybe a review of the jl777 staker? it seems there have been many changes made in LABS but not all of them got into a pull request and this difference is creating some rare crash?
blackjok3r31-Jan-19 09:33 AM
I only half fixed the segid fix it seems it still did not set for proof of work blocks, but I don't this k this can cause a crash, I think maybe the changes made to the flow logic of the staked inadvertently fixed the crash... I'm just not sure what it was... I can try to just copy komodo_bitcoind.h and miner.cpp to FSM and see if that works, but that seems like it won't work as I've added verushash2 and changed how it selects mindiff and other things which depend on changes elsewhere
The Easiest way to do this is for me maybe to list what changes are in labs, and you to tell em what to remove..
Rather than you havung to go through everything... I can also just disable all staked function's by making every chain staked = 0.
Is staked notary and komodo notary are mutually exclusive, maybe I can test this build on my notary node for a few days and make sure it works as expected... Then just disable staked chain functions, and disable the wallet filter... I this k that's all that will be needed... Any rpc that need is staked to be true can just return error.
@jl777c
jl777c31-Jan-19 09:40 AM
is this crash only on OUR when staking? that seems strange...
i have so little info on the crash, it is hard to tell where it can be
maybe that zcash fix will fix it?
blackjok3r31-Jan-19 09:43 AM
I'm not sure haven't tested it... You should really get the stalker bugs fixed from labs, there was many many days of debugging to get it working that well, but a crash was never something I came across... My only guess is that moving the submit block in future wait loop now bring inside createblock likely stops some null pointer issue Outside of lock cs_main.. But even that doesn't make a lot of sense.(edited)
jl777c31-Jan-19 09:44 AM
how about a pull request that adds in all the staker bug fixes?
blackjok3r31-Jan-19 09:44 AM
OUR is working fine on labs... I just do t know how to merge this in as its mixed with code for labs to let people use different sets of pubkeys
I don't have all these fixes just in one branch or something... They all got added over time through multiple branches and then pushed our master
Don't really have time to manually do this, and I think doing it manually is error prone and might break something... Not to mention making a merge back down from upstream have about 5 billion conflicts
jl777c31-Jan-19 09:46 AM
i guess a diff and reviewing it for things that are bug fixes. manual is the only way sometimes
blackjok3r31-Jan-19 09:47 AM
Maybe I can get to this tomorrow but I'm still busy working on the notary pay chain and temp file fix...
jl777c31-Jan-19 09:48 AM
ok
blackjok3r31-Jan-19 09:48 AM
Temp file is working, just trying to move it after all validation, seems to be causing issues so likely the last few steps will need to have the file in main chai n, it starts flooding GetTransaction read errors, seems to be to do with cc validation
jl777c31-Jan-19 09:49 AM
moving it seems like it would break anything that started in tmp. I had it so it stays in tmp until the next restart, of course restart didnt see the new blocks
blackjok3r31-Jan-19 09:51 AM
Yeah it seems there are things happening async to connect block which is weird as its inside a lock I thought... I think I will just move where it saves the file to main back where it was, as long as its after check PoW with slowflag set it will be safe enough. Its working perfectly for days here like that
Cycles through 4 16mb files
jl777c31-Jan-19 09:52 AM
seems on the small side...
blackjok3r31-Jan-19 09:52 AM
That's only for testing you can change the max temp file siE
jl777c31-Jan-19 09:52 AM
4MB * 20 blocks is 80MB
ok, I will tweak it once it is stable
it toggles behavior based on the usetmp variable?
if so I can make it only usetmp when it is unclear
blackjok3r31-Jan-19 09:54 AM
I thought the goal is to pruge blocks older than a notarization... But it seems all we can do is give a long enough buffer to assume 5 notarizations should have happened. 500mb of extra disk space isn't too bad.. and yes you can use the flag for those blocks only I guess...
jl777c31-Jan-19 09:54 AM
so for pure PoW chains, usetmp is never set
blackjok3r31-Jan-19 09:54 AM
Yes
jl777c31-Jan-19 09:54 AM
why are you assuming there isnt spam blocks in the tmp files?
blackjok3r31-Jan-19 09:55 AM
What do u mean?
jl777c31-Jan-19 09:55 AM
if 90% spam blocks, will take 10x the space to have all the valid blocks for notarization
blackjok3r31-Jan-19 09:55 AM
I just used 16mb as waiting for 128mb files to sync was stopping em from getting enough sleep
Its only an issue o. The first chain sync
With out a Max temp file size you allocate 2x the disk space as what the chain is
jl777c31-Jan-19 09:56 AM
not sure there can be any size limit to the tmp files, will end up with tx without any HDD presence
blackjok3r31-Jan-19 09:56 AM
And this is never recovered the files just stay on disk
jl777c31-Jan-19 09:56 AM
yes, but you can just manually delete these files
blackjok3r31-Jan-19 09:57 AM
Nobody will do that
jl777c31-Jan-19 09:57 AM
ok, maybe we need to delete them on startup
so let the tmp files grow and dont do runtime pruning. prune them all on restart
that seems safest
blackjok3r31-Jan-19 09:58 AM
You need to cycle files on initial sync then after that u can leave it u capped and just remove the files on startup
I doubt an attack can happen with requested blocks
jl777c31-Jan-19 09:58 AM
oh. on initial sync usetmp should be 0
blackjok3r31-Jan-19 09:58 AM
Only on blocks submitted to you
jl777c31-Jan-19 09:59 AM
since only valid blocks would be in the headers
usetmp is 0 if initial blockloading
blackjok3r31-Jan-19 10:21 AM
Hmm that does work, I used it as 1 for testing ad we have no attack to test it against so it was easier to just sync a chain...
I think we can detect if a temp file has any valid blocks that are not notarised in it before purging... I don't like that a user is forced to constantly re-start their node, it seems a backwards step... Notary nodes are already complaining about disk space...(edited)
Under attack conditions it would need to allocate more temp file space... But under normal conditions it will just cycle through a small amount of temp files(edited)
Also using prune on it, all these blocks still exist in the index and can be redownloaded if needed
That is still unsolved how to prune the index without crashing it... :((edited)
ComputerGenie 👴👴👴31-Jan-19 10:32 AM
Notary nodes are already complaining about disk space...
Imo, it's our job as notaries (in both KMDLabs and Komodo) to have whatever is needed to store all of every chain we deal with
I get that you're talking about the temp adding space, but as far as the "already", it seems to me that means the nodes are more unprepared for adoption and expansion than anything else.
If we need to buy more storage, isn't that just part of the job?
blackjok3r31-Jan-19 10:33 AM
Agreed... But most of them ate use I g rented servers that literally cannot offer enough space


Acknowledgments
In addition to the people I mentioned in the first edition's
preface, I'd like to extend appreciation to a few of the people
who helped in some way during this second edition project:
To this book's first editor, Frank Willison, for overseeing
this update, as well as championing the Python cause at
O'Reilly and beyond. To this book's later editor, Laura
Lewin, for picking up the ball and lighting necessary fires.
To Python creator Guido van Rossum for making this stuff fun again.
To the people who took part in a review of an early draft of this
edition: Eric Raymond, Mark Hammond, David Ascher, Tim Peters, and
Dave Beazley.
To Tim O'Reilly and the staff of O'Reilly &
Associates, both for producing this book, and supporting open source
software in general.
To the Python community at large, for diligence, hard work, and
humor -- both in the early years and today. We've come far,
but to steal a line from the 1970s: You aint' seen
nothin' yet.
And to the students of the many Python classes I have taught, as well
as the scores of readers who took the time to send me comments about
the first edition; your opinions helped shape this update.
Finally, a few personal notes of thanks. To my children, Michael,
Samantha, and Roxanne, for purpose. If they are at all representative
of their generation, the future of our species seems in very good
hands. You'll have to pardon me if that sounds proud; with kids
like mine, it's impossible to feel otherwise.
And most of all to Lisa, the mother of those amazing kids. I owe her
my largest debt of gratitude, for everything from enduring my flights
from reality while writing books like this, to keeping me out of jail
in our youth. No matter what the future may hold, I'll always
be glad that something threw us together two decades ago.
- Mark Lutz
- November 2000
- Somewhere in Colorado
|
The last five years have also been host to the rise of the open
source movement. Open source refers to software that is distributed
free of charge with full source code, and is usually the product of
many developers working in a loosely knit collaborative fashion.
Python, the Linux operating system, and many other tools such as Perl
and the Apache web server fall into this category. Partly because of
its challenge to the dominance of mega-companies, the open source
movement has quickly spread through society in profound ways.
Let me tell you about an event that recently underscored the scope of
this movement's impact on me. To understand this story, you
first need to know that as I was writing this book, I lived in a
small town in Colorado not generally known for being on the cutting
edge of technological innovation. To put that more colorfully,
it's the sort of place that is sometimes called a "cowboy
town."
I was at a small local bookstore hunting for the latest
Linux Journal. After browsing for a while, I
found a copy and walked it to the checkout. Behind the counter were
two clerks who looked as if they might be more at home at a rodeo
than behind the counter of this establishment. The older of the two
sported gray hair, a moustache, and the well-worn skin of a person
accustomed to life on a ranch. Both wore obligatory baseball caps.
Cowboys, to be sure.
As I put the magazine down, the elder clerk looked up for a moment,
and said, in classic cowboy drawl, "Linux, huh? I tell you
what, when Billy goes down, he's goin' down fast!"
Of course, this was in reference to the widely publicized competition
between Linux and Bill Gates' Microsoft Windows, spurred by the
open source movement.
Now, in another time and place, these two might have instead been
discussing livestock and firearms over strong cups of coffee. Yet
somehow, somewhere, they had become passionate advocates of the Linux
open source operating system. After collecting my chin from the
floor, we wound up having a lively discussion about Linux, Microsoft,
Python, and all things open. You might even say we had a good-old
time.
I'm not trying to express a preference for one operating system
over another here; both have merits, and Python runs equally well on
either platform (indeed, this book's examples were developed on
both systems). But I am amazed that an idea that software developers
often take for granted has had such a deep, mainstream impact. That
seems a very hopeful thing to me; if technology is to truly improve
the quality of life in the next millennium, we need all the cowboys
we can get.
|
|


PROCESSING
Processing is done inside the computer in an area called the central processing unit(CPU). Processing is the conversion of input to output.
HOME
INPUT
PROCESSING
OUTPUT
STORAGE


Exactly Where You Are
Little socially distance micro-short for Raindance's #lockdownlover competition. What does love look like in lockdown? Phoneboxes that's what.
The Wicked Woes of the Wizard's Wish - Pt. II (Some shall pass) | Glasgow 48HFP 2019
A whimsical wizard, a troubled traveller and a jangling jester - our entry into the 2019 Glasgow 48 Hour Film Project. This year's prompt was a Fantasy Film, the character Billy Mack (a comedian), a sausage as the prop and the line "I feel good". Pretty self explanatory really.
Dust to Dust
An examination of the circle-of-life in our daft, mini-short that we shot in Kelvingrove park.
Escape at Bedtime
Based off of the Robert Louis Stevenson of the same name, this is a little visual poem nodding to the future of travel.
Love You 'Till The End | The Ninth Wave
Two questionable angels abandon their duties and find themselves staggering around Glasgow with a little too much Christmas cheer. A hectic, one night shoot that drew a little more attention than we were ready for.
Blueheart | Lucia
The beautiful Ardgowan House stars as the magnificent backdrop for this music video for Lucia's Blueheart.
In Lieu | My Røde Reel 2019
Literally caught with his pants down, Bazza tries to slip out of trouble. Shot in the delightful Flying Duck in Glasgow - where filming in a small toilet is every bit as awkward as you might imagine it to be.


Warning: this page was last updated in 2000.
This is a simple set of JSPs and servlets to access an IMAP4 or POP3 mail store, and send email using SMTP.
I started working with Tomcat, but ran into some limitations and then switched to JRun.
The design went through four stages, as my understanding of JSPs grew:
In this first iteration, the application sticks to the MVC pattern, with JavaBeans for model, JSPs for views, and servlets for controllers.
The next step was to use JSP Tags to interact with the JavaBeans in the model. There were some interesting differences between Tomcat's and JRun's support for these tags.
<jsp:setProperty>
tags when the value
attribute is ""
(the empty string).<jsp:useBean>
tag doesn't
make use of the import information provided through the
page
directives. As a result, the
class
attribute must always fully specify the
class of the bean.session-timeout
tag in
WEB-INF/web.xml
to -1 so that sessions never expire.At the same time, the controller servlets were converted to trivial JSP pages, since most of their code can be generated automatically by the JSP compiler.
This version was developped only for JRun, thereby circumventing the problems with Tomcat.
At the same time, the build process was augmented by a
deploy
target that deploys the web application
directly into JRun.
This last version attempts to use the Jakarta Struts framework.
This work is still in progress, but so far, we've identified the following shortcomings.
BeanInfo
helper class to find properties. It
relies exclusively upon introspection.| Version | Tomcat | JRun |
|---|---|---|
| Model-View-Controller | X | X |
| JSP Tags | X | X |
| JRun-specific | X | |
| Jakarta Struts |


Intro to programming student.
I'm a 39 year old aspiring programmer. I currently work at Trader Joes and before that I was an HVAC/sheetmetal worker. I started taking the intro class at Epicodus because what little coding I've done was really fun and challenging. I have always liked to create and tinker with things so coding seemed like a great choice. I also want to pursue a career in coding so I can take care of my family. My hobbies include skateboarding, hiking, climbing, and programming! My goal is to have programming be a profession and not just a hobby.
My hotel project is a one page website for a resort with a few placeholder paragraphs and images. I used html, css, and a little bootstrap for this project.
A website about my wolf hybridA website about my dog Broski. I used html, css, and bootstrap. There are a few placeholder images for now as well as a paragrah about Broski.


Default properties and methods of
the HopObject prototype.
Constructor for HopObject objects, providing the
building blocks of the Helma framework.
Extends the standard JavaScript object with Helma-specific properties and functions. The HopObject is the basic building block of a Helma application. The website root object as well as custom types defined by the application inherit from the HopObject prototype.
HopObjects can be given special Helma specific properties, such as "collections" that can be configured to map to relational databases, and will make such data available when rendering "skins".
HopObjects can be in transient state or are persistently mapped on a database. HopObjects that are directly or indirectly attached to the application's root object are automatically persisted using the built-in XML database, if they are not otherwise mapped to a relational database. see JavaDocs for helma.scripting.rhino.HopObject
Extends the standard JavaScript object with Helma-specific properties and functions. The HopObject is the basic building block of a Helma application. The website root object as well as custom types defined by the application inherit from the HopObject prototype.
HopObjects can be given special Helma specific properties, such as "collections" that can be configured to map to relational databases, and will make such data available when rendering "skins".
HopObjects can be in transient state or are persistently mapped on a database. HopObjects that are directly or indirectly attached to the application's root object are automatically persisted using the built-in XML database, if they are not otherwise mapped to a relational database. see JavaDocs for helma.scripting.rhino.HopObject
methods
- add(subnode)
- addAt(position, subnode)
- contains(obj)
- count()
- get(id)
- getById(id, proto)
- getChildElement(name)
- getOrderedView(name)
- getResource(resourceName)
- getResources(resourceName)
- href(action)
- invalidate(childId)
- indexOf(obj)
- list()
- persist()
- prefetchChildren(startIndex, length)
- remove()
- removeChild(child)
- renderSkin(skin, params)
- renderSkinAsString(skin, params)
- size()
- update()
- onInit()
- onUnhandledMacro(name)
properties
- Number _id
- HopObject _parent
- Object cache
see
The unique id of the HopObject.
This property is read-only
The parent collection containing this HopObject.
Cache object providing space for arbitrary run-time data.
Each HopObject contains a cache object to store temporary properties (strings, numbers, objects etc.), a transient HopObject, which can be used for caching purposes.
These properties can be accessed in any thread until the application is restarted or the HopObject is invalidated, either manually using the invalidate method, or when the clearCache method is being called, or whenever Helma is updating the HopObject's data from a remote database.
There is no way to make the cache object persistent.
Example:
Each HopObject contains a cache object to store temporary properties (strings, numbers, objects etc.), a transient HopObject, which can be used for caching purposes.
These properties can be accessed in any thread until the application is restarted or the HopObject is invalidated, either manually using the invalidate method, or when the clearCache method is being called, or whenever Helma is updating the HopObject's data from a remote database.
There is no way to make the cache object persistent.
Example:
var obj = root.get(0); obj.cache.message = "This is a temporary message."
see
Methods
Attaches a HopObject as an additional subnode.
Adds a HopObject as new subnode to another HopObject.
The new subnode is added after the last subnode already
contained in the parent HopObject.
parameters
| HopObject | subnode | as HopObject to add to this node. |
returns
| Boolean true if the addition was successful. |
see
Attaches an additional subnode at the given index.
Adds a HopObject to a collection at a certain position, and shifts the index of all succeeding objects in that collection by one. Index positions start with 0.
Just makes sense for HopObjects, that are not mapped on a relational DB, since the sort order of the collection would otherwise be defined by type.properties, resp. by the database itself. Returns true in case of success.
Adds a HopObject to a collection at a certain position, and shifts the index of all succeeding objects in that collection by one. Index positions start with 0.
Just makes sense for HopObjects, that are not mapped on a relational DB, since the sort order of the collection would otherwise be defined by type.properties, resp. by the database itself. Returns true in case of success.
parameters
| Number | position | as Number, the index position where the subnode is to be inserted. |
| HopObject | subnode | as HopObject to add to this node. |
returns
| Boolean true if the addition was successful. |
see
Clears this HopObject's cache property.
Removes all information stored in the cache object. Doing this by just calling 'obj.cache = null' is not possible, since the property itself can not be set.
Removes all information stored in the cache object. Doing this by just calling 'obj.cache = null' is not possible, since the property itself can not be set.
see
Determines if a HopObject contains a certain subnode.
parameters
| HopObject | obj | as HopObject, the node to look for |
returns
| Number of the index position or -1 |
see
Get the number of subnodes attached to this HopObject.
Example:
Example:
res.write(root.count()); 5
returns
| Number of subnodes |
see
Retrieves a property or a subnode of a HopObject.
Either returns the specifed property of this HopObject or fetches the specified HopObject from its persisted subnodes.
For HopObjects that are mapped to a relational database, the id will be matched against the accessname property as defined in the prototype's type.properties.
This method just works for persistent HopObjects.
The type of the result depends on the type of the submitted argument:
A number will retrieve the subnode of the HopObject at the corresponding index position.
A string will retrieve the corresponding property of the HopObject.
A number as string retrieves the subnode with the corresponding Hop ID.
Example:
Either returns the specifed property of this HopObject or fetches the specified HopObject from its persisted subnodes.
For HopObjects that are mapped to a relational database, the id will be matched against the accessname property as defined in the prototype's type.properties.
This method just works for persistent HopObjects.
The type of the result depends on the type of the submitted argument:
A number will retrieve the subnode of the HopObject at the corresponding index position.
A string will retrieve the corresponding property of the HopObject.
A number as string retrieves the subnode with the corresponding Hop ID.
Example:
root.get(0); HopObject author root.get(1); HopObject story root.get("date"); Wed Oct 18 02:01:41 GMT+01:00 1971 root.get("title"); The Nudist On The Late Shift root.get("1"); HopObject author
parameters
| String | id | as String or Number |
returns
| HopObject or the retrieved property |
Retrieves the specified HopObject.
If called on a HopObject instance, this getById() retrieves a child object by ID. If called on a HopObject constructor, it retrieves the persisted HopObject of that prototype and with the specified ID.
Fetches a HopObject of a certain prototype through its ID and its prototype name. The prototype name can either be passed as a second argument, or alternatively the function can also be called on the prototype itself with a single argument (e.g. Story.getById(123)).
In case of multiple prototypes being mapped on the same table (which is for instance the case with inherited prototypes) Helma will not check whether the prototype of the fetched object actually matches the specified prototype.
Note, that this refers to the static method 'getById', not to be mixed up with the method getById called on a specific HopObject.
Example:
If called on a HopObject instance, this getById() retrieves a child object by ID. If called on a HopObject constructor, it retrieves the persisted HopObject of that prototype and with the specified ID.
Fetches a HopObject of a certain prototype through its ID and its prototype name. The prototype name can either be passed as a second argument, or alternatively the function can also be called on the prototype itself with a single argument (e.g. Story.getById(123)).
In case of multiple prototypes being mapped on the same table (which is for instance the case with inherited prototypes) Helma will not check whether the prototype of the fetched object actually matches the specified prototype.
Note, that this refers to the static method 'getById', not to be mixed up with the method getById called on a specific HopObject.
Example:
//get the child with id 17 var child = root.getById(17); writeln(child._id); 17 //get the child at index 17 of the HopObject's children-collection child = root.get(17); writeln(child._id); 42 //get the child with the name "17" (_children.accessname = name) of the HopObject child = root.get("17"); writeln(child._id); 69 writeln(child.name); 17 //get the persistent HopObject with prototype "Page" and id 127 var page = HopObject.getById(127, "Page"); writeln(page._id); 127 //get the persistent HopObject with prototype "Page" and id 127 var page = Page.getById(127); writeln(page._id); 127
parameters
| Number | id | as Number |
| String | proto | as String, the name of the prototype |
returns
| HopObject that was retrieved |
Optional handler to override the default URL path resolution.
If defined, the getChildElement() method is called on an object contained in the request path in order to determine the URL path resolution from that object to its (potential) child objects.
The string parameter passed to this method is the name of the next element in the URL path being resolved. The object being returned by this method is then used to continue resolving the URL path.
Example:
If defined, the getChildElement() method is called on an object contained in the request path in order to determine the URL path resolution from that object to its (potential) child objects.
The string parameter passed to this method is the name of the next element in the URL path being resolved. The object being returned by this method is then used to continue resolving the URL path.
Example:
function getChildElement(name) { if (name == 'transient') { return new HopObject(); } else { return this.get(name); } }
parameters
| String | name | as String, the name of the child element in the requested URL path |
returns
| HopObject the child object to be used for further path resolution |
Returns a collection including all subnodes of a
HopObject ordered according to the properties
listed in the string passed as argument.
While the sort pattern, passed as string argument, uses an SQL-like notation for the sorting, it contains property names, not database column names.
The method returns a collection object that is ordered according to the specified sort order. The returned collections are cached and bound to the original collections, i.e. they reflect changes to the original collection. Both initial ordering and re-ordering are done on the Helma side, meaning that no additional db traffic is generated by multiple ordered views.
Example:
While the sort pattern, passed as string argument, uses an SQL-like notation for the sorting, it contains property names, not database column names.
The method returns a collection object that is ordered according to the specified sort order. The returned collections are cached and bound to the original collections, i.e. they reflect changes to the original collection. Both initial ordering and re-ordering are done on the Helma side, meaning that no additional db traffic is generated by multiple ordered views.
Example:
var orderedByDate = hobj.getOrderedView("createtime desc, name"); var collection = orderedByDate.list(); for (var i in collection) { doSomething(collection[i]); } // other syntax examples: var orderedByName = hobj.getOrderedView("name"); var collectionByName = hobj.collection.getOrderedView("name");
parameters
| String | name | as String, the property names to sort by |
returns
| ListViewWrapper of the sorted subnodes |
Returns a helma.framework.repository.Resource object
defined for the prototype.
Returns a resource referenced by its name for the current HopObject's prototype - getResource() walks up the inheritance chain and through all defined repositories to find the resource and returns null if unsucessful.
Example:
Returns a resource referenced by its name for the current HopObject's prototype - getResource() walks up the inheritance chain and through all defined repositories to find the resource and returns null if unsucessful.
Example:
root.getResource("main.skin"); /usr/local/helma-apps/myApp/repository1/HopObject/main.skin root.getResource("type.properties"); /usr/local/helma-apps/myApp/repository3/Root/type.properties root.getResource("Functions.js"); /usr/local/helma-apps/myApp/repository17/Root/Functions.js
parameters
| String | resourceName | as String, the name of the requested resource |
returns
| helma.framework.repository.Resource |
see
Returns an Array of helma.framework.repository.Resource
objects defined for the prototype.
Returns an array of resources by the specified name for the current HopObject's prototype - getResources() walks up the inheritance chain and through all defined repositories to collect all the resources by that name and returns null if unsucessful.
Returns an array of resources by the specified name for the current HopObject's prototype - getResources() walks up the inheritance chain and through all defined repositories to collect all the resources by that name and returns null if unsucessful.
parameters
| String | resourceName | as String, the name of the requested resource |
returns
| Array of helma.framework.repository.Resource objects |
see
Returns the absoulte URL path of a HopObject relative
to the application's root.
This function is useful when referring to a HopObject in a markup tag (e.g. with a href attribute in an HTML -tag). An optional string argument is appended to the return value.
Example:
This function is useful when referring to a HopObject in a markup tag (e.g. with a href attribute in an HTML -tag). An optional string argument is appended to the return value.
Example:
var obj = root.get(0); res.write('');  res.write('');
parameters
| String | action | as String, optional part to be attached to the URL of this HopObject |
returns
| String of the URL path for this HopObject |
Marks a HopObject as invalid so that it is fetched
again from the database.
Helma will overwrite the HopObject's node cache with the database contents the next time the HopObject is accessed.
In other words, use this function to kick out an HopObject of Helma's node cache and force a database retrieval of the HopObject data.
Example:
Helma will overwrite the HopObject's node cache with the database contents the next time the HopObject is accessed.
In other words, use this function to kick out an HopObject of Helma's node cache and force a database retrieval of the HopObject data.
Example:
var obj = this.get(0); obj.invalidate();
parameters
| childId |
Determines if a HopObject contains a certain subnode.
Returns the index position of a Subnode contained by a HopObject (as usual for JavaScript, 0 refers to the first position).
The index position is a relative value inside a HopObject (not to be confused with a Hop ID which is unique for each HopObject).
If there is no appropriate subnode inside the HopObject the returned value equals -1.
Example:
Returns the index position of a Subnode contained by a HopObject (as usual for JavaScript, 0 refers to the first position).
The index position is a relative value inside a HopObject (not to be confused with a Hop ID which is unique for each HopObject).
If there is no appropriate subnode inside the HopObject the returned value equals -1.
Example:
var obj = root.get("myObject"); res.write(root.indexOf(obj)); 23 obj = root.get("blobject"); res.write(root.indexOf(obj)); -1
parameters
| HopObject | obj | as HopObject, the node to look for |
returns
| Number of the index position or -1 |
Returns true if the HopObject is in persistent state, meaning
that it is stored in the database, and false if it is transient.
Persistent state is also assumed if the object is currently in
the process of being inserted into or deleted from the database.
returns
| true if the HopObject is in persistent state |
see
Returns true if the HopObject is in transient state, meaning that
it is not stored in the database. This method returns false if the
object is stored in the database, or is in the process of being
inserted into or deleted from the database.
returns
| true if the the HopObject is in transient state |
see
Returns an array including all subnodes of a HopObject.
The start and count parameters are optional, if omitted, an array of the entire collection of subnodes is returned, otherwise only the specified range.
This function is most useful if the whole collection of a HopObject's subnodes should be retrieved as array. However, general use should be avoided in favor of the method described below.
Example:
With increasing amounts of subnodes tied to a HopObject the use of list() becomes seriously inefficient in cases where not all subnodes really need to be read out.
This is due to the creation of a JavaScript array containing the whole bunch of subnodes each time the function is called.
Instead, it is recommended to determine the amount of subnodes using the function count() and looping through the subnode collection using the get() function.
The start and count parameters are optional, if omitted, an array of the entire collection of subnodes is returned, otherwise only the specified range.
This function is most useful if the whole collection of a HopObject's subnodes should be retrieved as array. However, general use should be avoided in favor of the method described below.
Example:
var objectList = root.list(); for (var i=0; i < objectList.length; i++){ var myObject = objectList[i]; res.writeln(myObject.created); } Wed Oct 18 02:01:41 GMT+01:00 1971 Fri Nov 03 13:25:15 GMT+01:00 2000 Mon May 29 07:43:09 GMT+01:00 1999
With increasing amounts of subnodes tied to a HopObject the use of list() becomes seriously inefficient in cases where not all subnodes really need to be read out.
This is due to the creation of a JavaScript array containing the whole bunch of subnodes each time the function is called.
Instead, it is recommended to determine the amount of subnodes using the function count() and looping through the subnode collection using the get() function.
var amount = root.size(); for (var i=0; i < amount; i++){ var myObject = root.get(i); res.writeln(myObject.created); } Wed Oct 18 02:01:41 GMT+01:00 1971 Fri Nov 03 13:25:15 GMT+01:00 2000 Mon May 29 07:43:09 GMT+01:00 1999
returns
| Array of HopObjects |
Stores a transient HopObject and all HopObjects
reachable from it to database.
The function returns the id (primary key) of the newly stored HopObject as string, or null if the HopObject couldn't be stored for some reason.
Example:
The function returns the id (primary key) of the newly stored HopObject as string, or null if the HopObject couldn't be stored for some reason.
Example:
var hobj = new HopObject(); hobj.foo = new HopObject(); res.debug(hobj.persist()); 2 res.debug(hobj.foo._id) 3
Manually retrieving a particular set of subnodes.
This function provides some control of how many subnodes Helma should retrieve from the database and hold prepared in the node cache for further processing.
This means that for large collections Helma does not need to retrieve neither the subset of subnodes via one SQL statement for each subnode nor the whole collection at once via one statement.
Moreover, only subnodes are retrieved that are not in the node cache already which leads to a maximum of caching efficiency and loading performance.
Example:
This function provides some control of how many subnodes Helma should retrieve from the database and hold prepared in the node cache for further processing.
This means that for large collections Helma does not need to retrieve neither the subset of subnodes via one SQL statement for each subnode nor the whole collection at once via one statement.
Moreover, only subnodes are retrieved that are not in the node cache already which leads to a maximum of caching efficiency and loading performance.
Example:
res.writeln(root.length); 53874 root.prefetchChildren(0, 3); for (var i=0; i<3; i++) res.writeln(i + ": " + root.get(i)); HopObject 1 HopObject 5 HopObject 4
parameters
| Number | startIndex | as Number |
| Number | length | as Number |
Deletes a HopObject from the database.
The remove() function deletes a persistent HopObject from the database.
Note that additionally you may want to call the removeChild() function on any object holding the deleted object in its child collection in order to notify it that the child object has been removed.
Example:
The remove() function deletes a persistent HopObject from the database.
Note that additionally you may want to call the removeChild() function on any object holding the deleted object in its child collection in order to notify it that the child object has been removed.
Example:
res.write(parent.size()); 24 var child = parent.get(5); child.remove(); parent.removeChild(child); res.write(parent.size()); 23
see
Notifies a parent object that a child object has been removed.
The removeChild() function lets a parent object know that a child object has been removed. Note that calling removeChild() will not actually delete the child object. Directly call remove() on the child object in order to delete it from the database.
Example:
The removeChild() function lets a parent object know that a child object has been removed. Note that calling removeChild() will not actually delete the child object. Directly call remove() on the child object in order to delete it from the database.
Example:
res.write(parent.size()); 24 var child = parent.get(5); child.remove(); parent.removeChild(child); res.write(parent.size()); 23
parameters
| HopObject | child | as HopObject |
see
Renders a skin of a HopObject and writes the result
to the output buffer.
Either renders the provided SkinObject or a skin in the HopObject's prototype chain by the specified name.
A skin can contain markup (e.g. HTML or XML) and macros. Macros are references to Helma functions wrapped in special tags (<% and %>). For more information about skin and macro techniques please refer to the section about About Skins.
Optionally, a JavaScript object can be assigned to the function call as second argument. This object's properties later can be accessed from the skin via macro calls of the kind <% param.propertyName %>.
If a param property is not set but referred to in the skin file, it will be replaced with an empty string. Please note that this behaviour is different from generic macro calls.
Example:
Either renders the provided SkinObject or a skin in the HopObject's prototype chain by the specified name.
A skin can contain markup (e.g. HTML or XML) and macros. Macros are references to Helma functions wrapped in special tags (<% and %>). For more information about skin and macro techniques please refer to the section about About Skins.
Optionally, a JavaScript object can be assigned to the function call as second argument. This object's properties later can be accessed from the skin via macro calls of the kind <% param.propertyName %>.
If a param property is not set but referred to in the skin file, it will be replaced with an empty string. Please note that this behaviour is different from generic macro calls.
Example:
Contents of the file root/example.skin:   <title>Hello, <% param.title %>!</title>  <body bgcolor="<% param.bgcolor %>"> I greet you <% param.amount %> times.  Rendering the skin:
var param = new Object(); param.bgcolor = "#ffcc00"; param.title = "World"; param.amount = "12345"; root.renderSkin("example", param);   <title>Hello, World!</title>   I greet you 12345 times.
parameters
| String | skin | as SkinObject or the name of the skin as String |
| Object | params | optional, properties to be passed to the skin |
see
Renders a skin of a HopObject and returns the result as string.
Either renders the provided SkinObject or a skin in the HopObject's prototype chain by the specified name.
Similar to renderSkin(), this function returns the result of the rendered skin as string instead of immediately writing it to the response object.
Example:
Either renders the provided SkinObject or a skin in the HopObject's prototype chain by the specified name.
Similar to renderSkin(), this function returns the result of the rendered skin as string instead of immediately writing it to the response object.
Example:
var str = root.renderSkinAsString("example", param); res.write(str); which is equivalent to root.renderSkin("example", param);
parameters
| String | skin | as SkinObject or the name of the skin as String |
| Object | params | as Object, optional properties to be passed to the skin |
returns
| String containing the result of the rendered skin |
see
Get the number of subnodes attached to this HopObject.
Example:
Example:
res.write(root.size()); 5
returns
| Number of subnodes |
see
Refetches updateable Subnode-Collections from the database.
The following conditions must be met to make a subnodecollection updateable:
1) the collection must be specified with collection.updateable=true
2) the id's of this collection must be in ascending order, meaning, that new records do have a higher id than the last record loaded by this collection.
The following conditions must be met to make a subnodecollection updateable:
1) the collection must be specified with collection.updateable=true
2) the id's of this collection must be in ascending order, meaning, that new records do have a higher id than the last record loaded by this collection.
If defined, the onCodeUpdate() function is called whenever
the code is recompiled.
This is most useful when code from repositories is
dynamically modified by the application during runtime.
If a HopObject prototype defines a function named onInit(),
it will be called on each HopObject that is fetched from
embedded or relational database.
Note that it is not called for HopObjects created using a constructor.
Note that it is not called for HopObjects created using a constructor.
If a HopObject prototype defines a function named onPersist(),
it will be called on each HopObject immediately before it is
stored to embedded or relational database.
If a HopObject prototype defines a function named
onUnhandledMacro(), it will be called when a macro is rendered
on the HopObject that can't be mapped to a macro function or
property of the HopObject.
parameters
| String | name | as String, the name of the unhandled macro |
If defined, the onRequest() function is called on the
object specified by the request path just before the
action is invoked.
This is useful for performing some code before each and every action in every prototype (when defining the function for the hopobject prototype) or for each action in one prototype. Often, it is used for checking access permissions.
This is useful for performing some code before each and every action in every prototype (when defining the function for the hopobject prototype) or for each action in one prototype. Often, it is used for checking access permissions.
If defined, the onResponse() method is called after
each page request is handled but before the response is
returned.
This method is NOT called when a response is forwarded or redirected using res.forward or res.redirect respectively.
You can access the current repsonse buffer using the method res.getBuffer.
This method is NOT called when a response is forwarded or redirected using res.forward or res.redirect respectively.
You can access the current repsonse buffer using the method res.getBuffer.
see


object to be compared for equality with this map entry
true if the specified object is equal to this map entry
Returns the key corresponding to this entry.
the key corresponding to this entry
Returns the value corresponding to this entry. If the mapping has been removed from the backing map (by the iterator's remove operation), the results of this call are undefined.
the value corresponding to this entry
Returns the hash code value for this map entry. The hash code of d map entry e is defined to be: (e.getKey() === null ? 0 : e.getKey().hashCode()) ^ (e.getValue() === null ? 0 : e.getValue().hashCode())
This ensures that e1 === e2 implies that e1.hashCode() === e2.hashCode() for any two Entries e1 and e2
the hash code value for this map entry
Replaces the value corresponding to this entry with the specified value (optional operation).
new value to be stored in this entry
old value corresponding to the entry
Generated using TypeDoc
Compares the specified object with this entry for equality. Returns true if the given object is also d map entry and the two entries represent the same mapping. More formally, two entries e1 and e2 represent the same mapping if (e1.getKey() === null ? e2.getKey() === null : e1.getKey() === e2.getKey()) && (e1.getValue() === null ? e2.getValue() === null : e1.getValue() === e2.getValue())
This ensures that the equals method works properly across different implementations of the Map.Entry interface.


Mon - Thur - Wen : 9am - 8pm
Sun : 8 am - 9pm
Friday : CLOSED
Statue Now: OPEN
Phone: (962) 78-8703-716


1.What is the shortform of JavaScript.
2.Which of the following function of Array object calls a function for each element in the array?
3.Which of the below is not a datatype?
4.Jquery is a library containing JavaScript.
5.JavaScript is an object based programming language.True or False


Team 43
Risk Tool
A web app to calculate mortgage risk point.
Heatmap
A heatmap shows default percetage rate for each state.


Over the past decade, great strides have been made in analyzing the structure of epistemic justification mathematically and probabilistically
Extend the graph theoretic account using new results from graph theory on infinite cycles
| Bounded Paths | Infinite Paths | |
|---|---|---|
| Acyclic | Foundationalism | Infinitism |
| Edge Cover in Cycle Space | Coherentism | Infinite Coherentism |
A graph is a set of vertices and edges: $G = (V, E)$
Every directed graph $G$ has an underlying undirected graph $G'$
$H = (V_H, E_H)$ is a subgraph of $G$ if $V_H \subset V, E_H \subset E$
Example: $( \{ a,b,c \} , \{ab, bc, ca\})$
An edge cover of $G$ is a subgraph $H$ where every vertex of $G$ is incident to an edge in $H$.
Example:
A path a path is a sequence of edges connecting a distinct vertices
Example: $caed = (ca, ae, ed)$
The length of a path is the number of vertices in the path
A cycle is a path except that the first and last vertices are the same
Example: $abca = (ab, bc, ca)$
The degree of a vertex $x$ is the number of edges incident to $x$
The cycle space of $G$, $\mathcal{C}(G)$, is the closure of the set of cycles for $G$ by edge disjoint union
Theorem: Let $H = (V, E)$ be a subgraph of a finite undirected graph $G$. Then $E \in \mathcal{C}(G)$ if and only if every vertex of $G$ has even degree in $H$.
The double ray graph
Does the theorem work for infinite graphs?
“...common sense tells us that this can hardly be right: shouldn’t cycles be round?” - Diestel (2004)
The double ray graph
A connected component of a graph is a connected subgraph that is maximal
An end of a graph to be the set of rays that belong to the same connected component after any finite set of vertices are removed
Example: the double ray has two ends
The one-ladder graph
Think of ends as points at infinity
A graph $G$ is topologically connected if there exists a path between any two vertices that is either finite or traverses ends
A ray is a path from a vertex to an end
The degree of an end is the maximum number of edge disjoint rays contained in the end
The one-ladder graph
Theorem: Let $C$ be a subgraph of a locally finite graph $G$. Then $C$ is a cycle just in case $C$ is topologically connected and the degree of every vertex and end is two.
The one-ladder graph
The infinite cycle contained in the one-ladder graph
The one-ladder graph
Theorem: Let $G = (V, E)$ be a locally fininte graph. Then $E \in \mathcal{C}(G)$ if and only if every vertex and every end of $G$ has even degree.
Let vertices represent beliefs and directed edges represent relations of support between beliefs
Let $G = (V, E)$ be a support graph
Constructing a support graph (informally):
Example: If $p$ and $q$ are beliefs and $p$ supports $q$ then the support graph for $p$ is a subgraph of the support graph for $q$
Importantly, there is much we do not know:
These theories make assumptions on properties for support graphs
Justification and knowledge are ultimately derivative from a set of basic or foundational elements whose justification does not depend in turn on that of anything else. - BonJour (2010)
Foundationalism imposes two conditions on $G$:
beliefs can only be justified by other beliefs...what justifies beliefs is the way they fit together: the fact that they cohere with each other - BonJour (2010)
Coherentism imposes two conditions on $G$:
Infinitism borrows both from foundationalism that justification cannot be circular and from coherentism that only beliefs can justify other beliefs
Infinitism imposes two conditions on $G$:
Infinite Coherentism imposes a single condition on $G$:
The one-ladder graph
Interpretation: two indefinite reason giving processes go to/from the same end when they are appropriately connected or coherent


Are you a restaurant owner?
Want to manage your pantry/stocks?
Your staff?
But don't know how?
That's what we are here for.
A rich experience with every analytics that you can ask for. We are here to make your business more easier and profitable.
Start using VetaStudio


Helpers
Let's take a look at some other changes that affect helpers you might be using.
Aspect Ratios
ratio
ratio-{VAL}
- VAL:
1x1
4x3
16x9
21x9
- VAL:
The responsive embed helpers have been renamed to ratio helpers with some new class names. Instead of the word by, you use an x. There used to be a class called embed-responsive-class
which is gone.
There are some aspect ratio classes to help with setting the proportions of elements. These are designed to go in a container class that wraps elements like
<embed>
<video>
<object>
but will work with other elements like

or
.
Visually Hidden
- Removed:
sr-only
sr-only-focusable
visually-hidden
visually-hidden-focusable
There were two clases called sr-only and sr-only-focusable that have been removed.
Instead, there is a new class called visually-hidden
that hides elements, but shows them to screen readers.
visually-hidden-focusable
- is another version that does the same thing, but shows the elements when they're focusable.


SALMON COOKIE SALES
"Just a
hint
of fishy goodness!"
Home
New Cookie Shop Input Form:
Location:
Minimum Customers:
Maximum Customers
Average Hourly Cookie Sales
Submit


Javi
Developer & Visual Guru
Back to main page
Thank You!
Thank You!
THANK YOU!
Your submission was successful, I will contact you shortly.
Back to main page
Top