--- layout: page title: About header-img: "img/about-bg.png" ---
Long time listener, first time caller.


Instructions
1.
Behind one bulb is hidden camel.
2.
Click all the bulbs without meeting with a camel.
3.

4.
See if you can score a winning streak!
Reset


This Privacy Policy provides our policies and procedures for collecting, using, and disclosing your information. Customers can access the PDFfiller service (the “Service”) through our website www.PDFfiller.com, applications on Devices, through APIs, and through third-parties. A “Device” is any computer used to access the PDFfiller Service, including without limitation a desktop, laptop, mobile phone, tablet, or other consumer electronic device. This Privacy Policy governs your access of the PDFfiller Service, regardless of how you access it, and by using our Services you consent to the collection, transfer, processing, storage, disclosure and other uses described in this Privacy Policy. All of the different forms of data, content, and information described below are collectively referred to as “information.”
Our Privacy Policy explains:
• What information we collect and why we collect it.
• How we use that information.
It is our policy to respect the privacy of our customers regarding any information that we may collect while operating our website and our mobile products.
Personal Information You Provide to Us. The types of Personal Information collected may include customers’ username, email address, fax number, name of the file faxed/emailed/printed/stored, and browser/mobile device information.
Payment details Customers’ payments are processed directly through paypal or through a credit card processing company. We do not have access to and do not store our customers’ credit card or paypal payment information.
Files. We collect and store the files you upload, download, or access with the PDFfiller’s Service (“Files”).
Files filled out by customers are stored on the server. However, these files and the customers information contained therein are accessible only to the customers of the account in which they are stored. The data contained in these files is encrypted and is unreadable and unusable for anyone else including PDFfiller. Customers have the option to remove a filled out form at any point, which removes all the information from our servers. Files contained in an account without a paid subscription will be automatically deleted in 30 days.
Log Data. When you use the Service, we (ourselves or using third party services) automatically record some information from your Device, its software, and your activity using the Services, which can sometimes be correlated with Personal Information. This may include the Device’s Internet Protocol (“IP”) address, browser type, the web page visited before you came to our website, information you search for on our website, locale preferences, identification numbers associated with your Devices, your mobile carrier, date and time stamps associated with transactions, system configuration information, metadata concerning your Files, and other interactions with the Service.
Cookies. We also use “cookies” to collect information and improve our Services. A cookie is a small data file that we transfer to your Device. We may use “persistent cookies” to save your registration ID and login password for future logins to the Service. We may use “session ID cookies” to enable certain features of the Service, to better understand how you interact with the Service and to monitor aggregate usage and web traffic routing on the Service. You can instruct your browser, by changing its options, to stop accepting cookies or to prompt you before accepting a cookie from the websites you visit.
Geo-Location Information. Some Devices allow applications to access real-time location-based information (for example, GPS). Our mobile apps do not collect such information from your mobile device at any time while you download or use our mobile apps as of the date this policy went into effect, but may do so in the future with your consent to improve our Services. Also, some of the information we collect from a Device, for example IP address, can sometimes be used to approximate a Device’s location.
Personal Information is or may be used: (i) to set up an account and profile and to securely access their PDFfiller account, (ii) to administer your use of the Service and to provide and improve our Service, (iii) to better understand your needs and interests, (iv) to personalize and improve your experience, and (v) to provide or offer software updates and product announcements. If you no longer wish to receive communications from us, please follow the “unsubscribe” instructions provided in any of those communications, or contact PDFfiller support.
PDFfiller discloses potentially personally-identifying and personally-identifying information only to those of its employees, contractors and affiliated organizations that (i) need to know that information in order to process it on PDFfiller 's behalf or to provide services available at PDFfiller 's website and mobile platforms, and (ii) that have agreed not to disclose it to others. Some of those employees, contractors and affiliated organizations may be located outside of USA; by using PDFfiller 's websites, you consent to the transfer of such information to them.
Log Data and Cookies are or maybe used in aggregate form. We use this information for the above purposes and to monitor and analyze use of the Service, for the Service’s technical administration, to increase our Service’s functionality and user-friendliness, and to verify customers have the authorization needed for the Service to process their requests. We may provide aggregate information to our partners about how our customers, collectively, use our site, so that our partners may also understand how often people use their services and our Service
Records of Communication. When you contact PDFfiller, we may keep a record of your communication to help solve any issues you might be facing. If you send us a request (for example via a support email or via one of our feedback mechanisms), we reserve the right to publish it in order to help us clarify or respond to your request or to help us support other customers.
PDFfiller Customer Emails. PDFfiller may occasionally send you an email to tell you about new features, solicit your feedback, or just keep you up to date with what's going on with PDFfiller and our products.
Foreign Processing. PDFfiller processes personal information on our servers in many countries around the world. We may process your personal information on a server located outside the country where you live.
Retention of Records. Where we can provide information access and correction, we will do so for free, except where it would require a disproportionate effort. We aim to maintain our services in a manner that protects information from accidental or malicious destruction. Because of this, after you delete information from our services, we may not immediately delete residual copies from our active servers and may not remove information from our backup systems.
For legal reasons. We may disclose to parties outside PDFfiller, files stored in your PDFfiller account and information about you that we collect when we have a good faith belief that disclosure is reasonably necessary to (a) comply with a law, regulation or compulsory legal request; (b) protect the safety of any person from death or serious bodily injury; (c) prevent fraud or abuse of PDFfiller or its customers; or (d) to protect PDFfiller’s property rights. If we provide your PDFfiller files to a law enforcement agency as set forth above, we will remove PDFfiller’s encryption from the files before providing them to law enforcement. However, PDFfiller will not be able to decrypt any files that you encrypted prior to storing them on PDFfiller.
Business Transfers. If we are involved in a merger, acquisition, or sale of all or a portion of our assets, your information may be transferred as part of that transaction, but we will notify you (for example, via email and/or a prominent notice on our website) of any change in control or use of your Personal Information or Files, or if either become subject to a different Privacy Policy. We will also notify you of choices you may have regarding the information.
Non-private or Non-Personal Information. We may share aggregated, non-personally identifiable information publicly and with our partners – like publishers, advertisers or connected sites. For example, we may share information publicly to show trends about the general use of our services.
If you are a registered user, you may review, update, correct or delete the Personal Information provided in your registration or account profile by changing information in your “My Account” page. If your personally identifiable information changes, or if you no longer desire our service, you may update or delete it by making the change on your My Account page. In some cases we may retain copies of your information if required by law. For questions about your Personal Information on our Service, please contact PDFfiller support. We will respond to your inquiry within 30 days.
We will retain your information for as long as your account is active or as needed to provide you services. Once your subscription expires, your files will be deleted automatically within 30 days. If you wish to cancel your account or request that we no longer use your information to provide you services, you may delete your account by visiting My Account. We may retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements. Consistent with these requirements, we will try to delete your information quickly upon request. Please note, however, that there might be latency in deleting information from our servers and backed-up versions might exist after deletion. In addition, we do not delete from our servers files that you have in common with other customers.
If you have a Corporate PDFfiller account, your Administrator may be able to:
Please refer to your organization's policies if you have questions about your Administrator's rights.
Our Privacy Policy applies to all of the services offered by PDFfiller, Inc. and its affiliates, including services offered on other sites (such as our advertising services), but excludes services that have separate privacy policies that do not incorporate this Privacy Policy.
Our Privacy Policy does not apply to services offered by other companies or inpiduals, including products or sites that may be displayed to you in our PDF Search Engine search results, sites that may include PDFfiller’s services, or other sites linked from our services. Our Privacy Policy does not cover the information practices of other companies and organizations who advertise our services, and who may use cookies, pixel tags and other technologies to serve and offer relevant ads.
We may share your information with a third party application with your consent, for example when you choose to access our Services through such an application. We are not responsible for what those parties do with your information, so you should make sure you trust the application and that it has a privacy policy acceptable to you.
We regularly review our compliance with our Privacy Policy. When we receive formal written complaints, we will contact the person who made the complaint to follow up. We work with the appropriate regulatory authorities, including local data protection authorities, to resolve any complaints regarding the transfer of personal data that we cannot resolve with our customers directly.
Our Privacy Policy may change from time to time. We will not reduce your rights under this Privacy Policy without your explicit consent. We will post any privacy policy changes on this page and, if the changes are significant, we will provide a more prominent notice (including, for certain services, email notification of privacy policy changes). We will also keep prior versions of this Privacy Policy in an archive for your review.
The security of your information is important to us. When you enter sensitive information (such as a credit card number) on our order forms, we encrypt the transmission of that information using secure socket layer technology (SSL). We follow generally accepted standards to protect the information submitted to us, both during transmission and once we receive it. No method of electronic transmission or storage is 100% secure, however. Therefore, we cannot guarantee its absolute security. If you have any questions about security on our website, you can contact PDFfiller support.
Our Services are not directed to persons under 13. We do not knowingly collect personally identifiable information from children under 13. If a parent or guardian becomes aware that his or her child has provided us with Personal Information without their consent, he or she should contact PDFfiller support. If we become aware that a child under 13 has provided us with Personal Information, we will take steps to delete such information from our files.
Questions or Concerns?
If you would like to communicate with us about this Privacy Policy or PDFfiller's collection and use of your Personally Identifying Information please contact PDFfiller support.
|
PDFfiller
|
Online & Mobile App
|
Integrations
|
|
Follow Us
© 2006-2017 PDFfiller Inc. All rights reserved |


Removes leading and trailing whitespace from every column in a dataframe or list of dataframes. At the same time it standardizes the case of the characters to either upper or lower case. This function works best with raw character data before converting data types and other data munging/feature engineering. Does handle a dataframe as it is, however, and returns every column in it's original data type as a dataframe.
casetrim(df, case = c("upper", "lower"), colclasses = c("asis", "character"))
| df | a dataframe or list of dataframes with columns of any character type |
|---|---|
| case | the letter case you want the output to be: |
| colclasses | do you want to return every column to it's original data type ( |
toupper
, tolower
, trimws
df <- data.frame( performingPhysio = c("JILL jones ", " jack BLACK", "", " RegiNald ChesterField ") , operatingPhysio = c("Who Dat ", "chuck FLEMMING ", NA, " shankman, razor shankman") , consent = rep(FALSE, times = 4) , duration_hrs = 5:8 , stringsAsFactors = FALSE ) casetrim(df)#> performingphysio operatingphysio consent duration_hrs #> 1 3 3 TRUE 1 #> 2 2 1 TRUE 2 #> 3 1 <NA> TRUE 3 #> 4 4 2 TRUE 4casetrim( df , case = 'lower' )#> performingphysio operatingphysio consent duration_hrs #> 1 3 3 TRUE 1 #> 2 2 1 TRUE 2 #> 3 1 <NA> TRUE 3 #> 4 4 2 TRUE 4casetrim( df , case = 'lower' , colclasses = 'character' )#> performingphysio operatingphysio consent duration_hrs #> 1 jill jones who dat false 5 #> 2 jack black chuck flemming false 6 #> 3 <NA> false 7 #> 4 reginald chesterfield shankman, razor shankman false 8


Zone 2 Zone Flows
Testing out bundling algorithim (
D3-ForceBundle
) for flow data.
D3 lines and points created from CSV on top of leaflet/mapbox base map


break
or continue
statements inside of finally
blocks.
While occasionally intended, such statements are very confusing, may mask exceptions thrown, and
tremendously complicate debugging.
Example:
while (true) { try { throwingMethod(); } finally { continue; } }


User-friendly open source tool for data analysis
Chipster is a user-friendly analysis software for next generation sequencing data such as scRNA-seq, RNA-seq, ChIP-seq, 16S, etc.


Hello, this readme is a WIP.
npm i -g markdown-cli-compiler
mdc <args>
--ignore
: boolean. Doesn’t run the command. Useful in a mdconfig.json
.--input
or -i
: string. the input file path. Can be a Markdown file or a directory.--output
or -o
: string. The output path. By default it’s the input file name with an additional .html
extension.--enc
: string. Input Markdown file encoding (list of supported encodings). It’s also used for the mdconfig.json. Default: utf8
--plugins
or -p
: array. The names of the plugins to use. Works without the markdown-it-
prefix too. got from here. eg: --plugins mark ins
--styles
or -s
: array. The paths of the CSS files that will be linked in a <link>
tag in the head of the output html file.--hls
: string. The name of an highlight.js theme (list of themes). eg: --hls monokai
--copiedStyles
: array. The paths of the CSS files whose content will be copied and pasted into the output html. Paths should be relative to the output path.--inlineStyle
: string. Raw CSS to write as it is into a <style>
tag.--title
: string. Goes in the <title>
tag.--comment
: boolean. Adds to the html output a comment after <!DOCTYPE html>
with in it the command called with all the args.--force
: boolean. Doesn’t emit a warning before overriding a file. (I wanted the “Are you sure you want to override the file?”, but since I haven’t made it yet, this doesn’t really make sense).--noOk
: boolean. Doesn’t emit success messages.--noWarn
: boolean. Doesn’t emit warning messages.--failOnWarn
: boolean. Stops the program when encounters a warning.--debug
: boolean. Doesn’t quit on fail.--html
, --xhtmlOut
, --breaks
, --langPrefix
, --linkify
, --typographer
and --quotes
(all: boolean) are explained here.If the input field is a directory, the program will look for a file named mdconfig.json
there. It has to be an array of json objects with configurations that work the same way as the cli args. Aliases like -i
, -o
and -s
will not work. Example.


Gateway
BOT
15-Sep-18 01:14 AM
[dscrdeql] <CowboyCrypto- Founder> glad you are here.
[dscrdeql] <CowboyCrypto- Founder> it will not be easy. and there are not promises of lambos, but there will be houses!!
[dscrdeql] <Smoky Satoshi> Lambo colored houses
[dscrdeql] <Jellysmash> @CowboyCrypto- Founder I imagine that you can add concrete colouring to the building blocks to give a more natural colour like a sandstone colour??
[dscrdeql] <Jellysmash> Those blocks would look awesome in a sandstone look
[dscrdeql] <CowboyCrypto- Founder> yeah
[dscrdeql] <CowboyCrypto- Founder> I havent messed with pigment powders yet
[dscrdeql] <Jellysmash> wouldn't have to paint them then
[dscrdeql] <CowboyCrypto- Founder> well here's the thing I will have sto stucco them anyway
[dscrdeql] <CowboyCrypto- Founder> so it wont really make sense to color.
[dscrdeql] <CowboyCrypto- Founder> inside will be plastered.
[dscrdeql] <Buddz1993> Im ok with houses
[dscrdeql] <Buddz1993> fair enough


{% extends 'base.html' %} {% block nav %} {% include '../snippets/dashboard_nav.html' %} {% endblock %} {% block content %} Account Your account is in order. If you have any requests, please email<EMAIL_ADDRESS>Delete account {% endblock %}
Your account is in order. If you have any requests, please email<EMAIL_ADDRESS>Delete account


Basics
- Tables have default styles: regular rows have white backgrounds, while headers use white text with a gray background. An additional
.table-striped
class is available for alternate row striping.
- ENCORE-SPECIFIC: In Encore, we usually use to tables to show data-table related data, such as listing of objects.
- If you need to show summary-style important pieces of metadata that aren't necessarily related to each other, consider using an rxMetadata component.
- In Support Services, there have been moments where we have displayed table in a structural format, but we use a different styling. See the Non-Data based Tables section for more information.
Directives
Cog Menus via rxActionMenu
- See the rxActionMenu directive for implementation and examples.
- ENCORE-SPECIFIC: In Encore, we usually use cogs if there are actionable items for every row. As an example, most main table listings show cog menus with actionable items, such as Cloud Server pages showing FirstGen/NextGen actions or Cloud Block Storage Volumes.
- For general advice as to what icons and colors to use, consult the section on icons and colors.
- There may be cases where an action is not available on a particular row. In this case, those particular links were disabled using the
.disabled
class rather than not having them appear at all.
- The
.actions
class is used on a column header (th
tag) to add a 15px width for action cogs in the table body.
- HEADS UP: We have one design pattern that slightly differs; for data tables that have involved objects that only require deleting such as particular data tables related to LBaaS connection nodes and Support Service user tables, a particular delete-based design pattern was created. See the section on Delete "X" actions.
Table Footer Pagination via rxPaginate
- See the rxPaginate directive for implementation and examples.
- ENCORE-SPECIFIC: The pagination is visible in this example to show how mark-up will be implemented. Generally, the pagination directive does not display if there is only one page of data available. We use angular.js to make sure this doesn't display.
- HEADS UP: It's a known issue that the footer wraps into a second line if the table is 50% of the screen. In cases like those, we've used the
display:none
CSS property for elements to hide all elements not directly related to pagination. See the LESS of narrow tables used in Support Services for an example of this. Note that this has not been implemented in EncoreUI yet.
Design Patterns
Null patterns
- ENCORE-SPECIFIC: Consider having a default message if there are no rows for your data table. In Encore, we still include the data table headers to show there would usually be tabular data here.
Non-Data based Tables
- For Support Services, we use tables as a structural format but use different styling to show larger components of data such as tags, groups, badges and other block level information.
- As the usage of this is outside of EncoreUI and falls outside the scope of this document, please look at the the staging site and the specific markup and LESS files for more information.
Delete "X" action
- ENCORE-SPECIFIC: For data tables involving objects that only require deleting (Examples: tables related to LBaaS connection nodes and Support Service user tables) there's a design pattern that replaces the cog with an X.
- Add the
.delete-x
class to the icon element to automatically apply the red hover style. This should always be done when using this design pattern.
- View these set of tables used in Support Services for examples.
Other single action
- A button link is used for tables where each row has a single action that is not a deletion.
- If the action is unavailable for a row, the link should be disabled and have a tooltip indicating why.
Status columns
- ENCORE-SPECIFIC: We provide a standardized mechanism for color coding of status columns, via rxStatusColumn. Ticket Queues has their own styling that predates this, and can be seen in their tickets.less file. For consistency, new projects should use
rxStatusColumn
. If it doesn't satisfy your needs, please let us know and we'll see what we can do.
Filters
- ENCORE-SPECIFIC: Tables have also been used for filtering. In the past there was no common design pattern for this, and different products implemented it on their own:
- Data-based filters, seen in Encore Cloud (Servers, Volumes, Images, Database, Load Balancers)
- Ticket Queues (Filtering by ticket queues and status)
- Billing (Filtering by billing data and transactional status)
- With the addition of rxFloatingHeader to the framework, we now have a standard way of adding table filters. In short, we add a new
<tr>
into the <thead>
of the table. rxFloatingHeader
will take care of the styling, by adding the appropriate classes on its own (namely th.filter-header
)
Collapsible component for table filters
- Filters can be displayed inside of a collapsible element.
- The initial display can be expanded or collapsed.
- A double chevron is used as a toggle to show/hide the inner contents, while keeping the header and border visible.
Nested content
- When a dataset includes a parent-child relationship, the nested tables style should be used to optionally show the related content.
- ENCORE-SPECIFIC: Use the double chevron in the right most column as the toggle switch for the hidden content.
Table
Metadata
UI Roadmap / Possible Future-work
- Checkboxes for table rows with design patterns related to "Select/Unselect All" behavior
- Loading Styles for Tables
- Submit actions for Server-Side Filtering


@()
Both the disabled
and readonly
attributes for an input prevent the user from modify it.
However, the disabled
attribute means this input will NOT be sent within the POST request, whereas
the readonly
one means it will.
Nevertheless, for checkbox
, radio
and select
tags it doesn't happen. To
support the readonly
attribute for these tags, the corresponding helpers have been adapted to behave
as would be expected. To do that, when the readonly
attribute appears the helper will:
disabled
attribute<input type="hidden">
with the desired valuecheckbox-group
, radio-group
or select-group
)readonly
attribute is present, even with a false value.
It is done to make it easier to modify its readonly
behaviour using javascript.


{% extends 'service.html' %} {% load i18n %} {% load staticfiles %} {% block title %} {% trans "Server Error" %} | {{ block.super }} {% endblock %} {% block content %} {% url 'home' as home_url %}
{% blocktrans %} Apologies, but we can't give you this page, because of an unhandled error. We have been notified about this and will fix it soon. {% endblocktrans %}
{% blocktrans %} You can now go to home page or try navigating back. {% endblocktrans %}
{% endblock %}