Privacy Policy
Last updated: 4th December 2018
Company ("us", "we", or "our") operates https://company.com (the "Site"). This page informs you of our policies regarding the collection, use and disclosure of Personal Information we receive from users of the Site.
We use your Personal Information only for providing and improving the Site. By using the Site, you agree to the collection and use of information in accordance with this policy.
Information Collection And Use
While using our Site, we may ask you to provide us with certain personally identifiable information that can be used to contact or identify you. Personally identifiable information may include, but is not limited to your name ("Personal Information").
Log Data
Like many site operators, we collect information that your browser sends whenever you visit our Site ("Log Data").
This Log Data may include information such as your computer's Internet Protocol ("IP") address, browser type, browser version, the pages of our Site that you visit, the time and date of your visit, the time spent on those pages and other statistics.
In addition, we may use third party services such as Google Analytics that collect, monitor and analyze this.
Communications
We may use your Personal Information to contact you with newsletters, marketing or promotional materials.
Cookies
Cookies are files with small amount of data, which may include an anonymous unique identifier. Cookies are sent to your browser from a web site and stored on your computer's hard drive.
Like many sites, we use "cookies" to collect information. You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you do not accept cookies, you may not be able to use some portions of our Site.
Security
The security of your Personal Information is important to us, but remember that no method of transmission over the Internet, or method of electronic storage, is 100% secure. While we strive to use commercially acceptable means to protect your Personal Information, we cannot guarantee its absolute security.
Changes To This Privacy Policy
This Privacy Policy is effective as of 4th December 2018 and will remain in effect except with respect to any changes in its provisions in the future, which will be in effect immediately after being posted on this page.
We reserve the right to update or change our Privacy Policy at any time and you should check this Privacy Policy periodically. Your continued use of the Service after we post any modifications to the Privacy Policy on this page will constitute your acknowledgment of the modifications and your consent to abide and be bound by the modified Privacy Policy.
If we make any material changes to this Privacy Policy, we will notify you either through the email address you have provided us, or by placing a prominent notice on our website.
Contact Us
If you have any questions about this Privacy Policy, please contact us.


| January 18-22 | Maui, Hawaii |
UPDF IPP PWG/IPP 1394 Printing || Finisher Interface 1394 Printing |
| Feb | no meeting | |
| March 1-5 | Miami, Florida | 1394 Printing 1394 Printing IEEE1284R IEE1284R/UPDF UPDF |
| April 12-16 | New Orleans (pics) |
IEEE 1284.4 1394 Printing PWG/IPP IPP UPDF |
| May 24-28 | Philadelphia | 1394 Printing 1394 Printing PWG/IPP IPP UPDF |
| June | no meeting | |
| July 5-9 | Copenhagen,
Denmark (pics) |
1394 Printing 1394 Printing PWG/IPP IPP UPDF |
| August 16-20 | Alaska (pics) |
1394 Printing 1394 Printing PWG/IPP IPP UPDF |
| September 20 - 24 | Denver | 1394 Printing 1394 Printing / PWG Brainstorming PWG/IPP IPP UPDF |
| October 25 - 29 | Durham, NC | 1394 Printing 1394 Printing PWG/IPP IPP UPDF |
| November | no meeting | |
| December 13-17 | Los Angeles | 1394 Printing 1394 Printing PWG/IPP IPP UPDF |


2020’s content is finally coming through. Lots of fun and intereting things to bring my brain slowly out of its slumber.
Post of the week
Not something I found interesting so much as terrifying. The Defense and Security Accelerator has announced contracts worth £4M to use ‘artificial intelligence’ in warships. Given how terrible AI is at playing war video games are we really pushing it into machines which can define the fates of nations? Yes. Yes we are.
You should take this with a pinch of salt. I’m conflating the reality of the matter and I imagine the use is far more mundane. The thought of it is still very skynet though!
Blogs and commentary
MIT’s deep learning series starts our year with a good description of what the current state of the art in deep learning is and the hopes for 2020.
Towards Data Science have had a very, very busy start to the year.
- Making use of time features, in which you may learn a little physics.
- Deep learning in brain-computer interface which is as futuristic as your favourite sci-fi novella.
- A description of Uber’s deep learning stack and how it is one of the best.
- Finally, a step back from the edge to provide a tutorial for understanding neural networks.
Other posts from around the web:
- Nature feature a description of how hardware can evolve to improve machine learning capabilities of modern computers. The paper is expensive to purchase so I haven’t read it.
- Microsoft made me happy (shocking I know) by pledging to become ‘carbon negative’ by 2050.
- I’ve previously posted blogs from Vicki Boykis so sticking with this tradition we have AI won’t save healthcare. She has become one of my favourite voices in the machine learning world.
- Tristan Handy (of data science roundup fame) has written a blog about the changing landscape of analytics. The central dysfunction of data section, in particular, felt very familiar to me through a lot of conversations I’ve had across government and industry. Please use this full url as it refers via Tristan’s newsletter.
- DeepMind found a deep learning technique also works in human brains.
- El Reg has their first AI roundup of 2020. Including a link to a post on how machine learning is helping to drive bad decisions in Hollywood.
- This one is worth a look if just for the gif at the top! Via boingboing, we have when machine learning cheats.
- Following up on a previous post describing how Shakespeare’s Henry VIII was probably about half written by John Fletcher is a discourse on how ML can change the way we read Shakespeare.
Propaganda
- Lenses are amazing. I’ve talked about them previously but this week, here’s your chance to dig into the library a little bit.
- Cabal is my favourite build tool. Well, when I couple it with nix it is anyway. Go find out a little more about it and some of its features.
- Way back before Halloween I posted a math3ma
blog about adjunctions.
Junstin Le now brings more practicality to this idea by considering
adjunctions in the wild and
in particular looking at
foldl
. - I’ve started an audit on the coursera Julia Scientific Programming course. I’ve found the first week more elementary than I need but I’m looking forward to the rest. I’m working through the videos without touching the notebooks and writing my own .jl files and its definitely proving worth it. Give it a go if you’re interested in learning some Julia, its free after all!
Origin of the Title
La Dispute are touring and I can’t wait to see them.


20 Photos That Can Feel as Soothing as a Hot Bath
In an ideal world, stress wouldn’t be a significant part of our lives. But when that’s not possible, you can still take your mind to a “happy place” — at least for a few minutes — by simply gazing at some pictures that have the magical power to bring you instant calm.
We at Bright Side enjoy finding effective stress busters, so we’re sharing this collection of relaxing images that your brain will thank you for.
1. This endless lavender field from the South of France
2. A wall made of trees in Paris
3. These aligned handles in the Taipei metro
4. Perfect lemon meringue pies
5. Hundreds of crows roosting in the snow at night
6. This pile of flour
7. The way these bubbles are aligned
8. Art in a fruit tart
9. How the veins of the leaf align on the creases of the hand
10. Red/green color blindness simulation on a gradient puzzle
11. This toasted marshmallow
12. “My coffee with milk was the same shade of brown as my mug this morning.”
13. “I kept on passing this, so on the third night I decided to take a picture.”
14. This neatly stacked box of pencils
15. The view in Trinity College Library from Dublin
16. This painting
17. The way these pumpkin seeds settled in a pot of water
18. The progressive color banding in this latte
19. This snowy street in Ireland
20. The view of these perfect rows of tulips
Which of these images had a calming effect on you? Please share your thoughts in the comment section below!
Preview photo credit Incredible_Cat / reddit, admiralwan / reddit


Select a filter
Default
Mean blur
Gaussian blur
<canvas> is not supported
Photo by Joel Filipe on Unsplash


LDD How-To Guides¶
- LDD How-To Guides
- Trigger LDD Build
- Generate a Discipline LDD
- Generate a Mission LDD
- Generate a LDD with a specific PDS4 Version
- Specify Enumerated Values for Attributes within Inherited Classes
- Schematron (DD_Rule) Help
- Using Schematron
value-of
functionality - Mission LDD Namespace Formation Guidelines
- Basics For Creating an Ingest LDD
- Reviewing a Pull Request
- Merging an Approved Pull Request
- Generate Human Readable Versions of the LDD
- Use Multiple Files to Define a Single Namespace
- Merge A New Release Branch Into My Current Working Branch
- How to Change PDS4 Build Versions
- TBD
Trigger LDD Build¶
For this example we will be using the IMG Discipline LDD repo. For your repo, just replace the ldd-img or references to IMG with your appropriate discipline dictionary.
Create a new branch for your updates (if you have not already created one).
Update your IngestLDD file (e.g. PDS4_IMG_IngestLDD.xml).
Watch the magic happen on your Github Actions page: https://github.com/pds-data-dictionaries/ldd-img/actions
After the action has completed successfully (hopefully), update your local branch to get the generated dictionaries from Github.com
Generate a Discipline LDD¶
To generate a Discipline LDD versus a Mission LDD, you must specify this information within the IngestLDD, for example:
<name>Imaging Discipline Dictionary</name>
<ldd_version_id><IP_ADDRESS></ldd_version_id>
<dictionary_type>Discipline</dictionary_type>
See the Imaging Discipline LDD for a more detailed example.
Then execute LDDTool to generate the appropriate dictionary:
lddtool -lp <my_ingest_ldd>
Generate a Mission LDD¶
To generate a Mission LDD versus a Discipline LDD, you must specify this information within the IngestLDD, for example:
<name>Mars 2020 Mission</name>
<ldd_version_id><IP_ADDRESS></ldd_version_id>
<dictionary_type>Mission</dictionary_type>
See the Mars 2020 Mission LDD for a more detailed example.
Then execute LDDTool to generate the appropriate dictionary:
lddtool -lp <my_ingest_ldd>
Generate a LDD with a specific PDS4 Version¶
LDDTool is a reflection of the PDS4 Information Model (IM), and in turn, has a major build in sync with the PDS4 Build Schedule (every 6 months).
By default, LDDTool builds with the latest version of the IM. As of LDDTool v12.0.0, it can now generate LDDs for older versions of the IM using the -V flag:
-V, --IM Version - E.g., -V 1D00
Specify Enumerated Values for Attributes within Inherited Classes¶
Classes from the PDS common dictionary (or discipline LDDs) are often inherited and used within Discipline and Mission LDDs (e.g. Internal_Reference.reference_type
, etc.). When inherited within the specific Discipline or Mission, you may want to provide a specific set of values applicable for that particular context. In this case you would want to use the DD_Associate_External_Class. For example::
<DD_Associate_External_Class>
<namespace_id>pds</namespace_id>
<class_name>Local_Internal_Reference</class_name>
<minimum_occurrences>0</minimum_occurrences>
<maximum_occurrences>1</maximum_occurrences>
<DD_Context_Value_List>
<attribute_name>local_reference_type</attribute_name>
<attribute_relative_xpath>local_reference_type</attribute_relative_xpath>
<DD_Permissible_Value>
<value>spectral_characteristics_to_array_object</value>
<value_meaning>
The spectral parameters describe the array associated
with the given 'local_identifier'.
</value_meaning>
</DD_Permissible_Value>
<DD_Permissible_Value>
<value>spectral_characteristics_to_table_object</value>
<value_meaning>
The spectral parameters describe the table or specific
fields in the table associated with the given
'local_identifier'.
</value_meaning>
</DD_Permissible_Value>
</DD_Context_Value_List>
</DD_Associate_External_Class>
Schematron (DD_Rule) Help¶
Specify Enumerated Values for Inherited Attributes¶
Attributes from the PDS common dictionary (or discipline LDDs) are often inherited and used within Discipline and Mission LDDs (e.g. pds:name
, etc.). When inherited within the specific Discipline or Mission, you may want to provide a specific set of values applicable for that particular context. In this case you will need to specify a DD_Rule to provide the enumerated value list. For example::
<DD_Rule>
<local_identifier>color_filter_array_state_check</local_identifier>
<rule_context>//img:Color_Filter_Array</rule_context>
<DD_Rule_Statement>
<rule_type>Assert</rule_type>
<rule_test>img:color_filter_array_state = ('Encoded', 'Decoded', 'No CFA')</rule_test>
<rule_message>IMG:error:img:color_filter_array_state_check: img:color_filter_array_state must be equal to one of the following values:
'Encoded', 'Decoded', 'No CFA'.
</rule_message>
</DD_Rule_Statement>
</DD_Rule>
Using Schematron value-of
functionality¶
To use the sch:value-of
in your DD_Rule
descriptions, you simply need to escape the XML entities. For example:
<sch:rule context="msn:mission_phase_name">
<sch:let name="num_colons" value="string-length(.) - string-length(translate(., ':', ''))"/>
<sch:let name="required_colons" value="4"/>
<sch:assert test="$num_colons eq $required_colons">
In Product_Collection, the number of colons found:
(<sch:value-of select="$num_colons"/>)
is inconsistent with the number expected:
(<sch:value-of select="$required_colons"/>).
</sch:assert>
</sch:rule>
</sch:pattern>
Note the <`
and >
used to replace the <
and >
Mission LDD Namespace Formation Guidelines¶
Note
The determination of LDD namespaces is ultimately up to the discussion amongst the Mission Data Archive Working Group (DAWG). This is simply a guide to enable consistency wherever possible.
For mission namespaces, use the mission acronym or shortened name. For example:
bc for BepiColombo
m2020 for Mars2020
insight for InSight
orex for OSIRIS-REx
for instrument-specific namespaces, use the formation rule mission_host_instrument. For example:
bc_mtm_mcam for the MCAM instrument on the Mercury Transfer Module (MTM) instrument host of the BepiColombo mission
Basics For Creating an Ingest LDD¶
See the Small Bodies Node wiki <http://sbndev.astro.umd.edu/wiki/Creating_the_Ingest_LDD_Dictionary_Input_File> on creating an Ingest LDD file.
Reviewing a Pull Request¶
Go to
Pull Requests
tab of your repo, e.g. https://github.com/pds-data-dictionaries/ldd-spectral/pulls:
Select the open Pull Request for the new release (e.g. https://github.com/pds-data-dictionaries/ldd-spectral/pull/13)
The first check should always be if the LDD Github Build completed successfully. You should see a green check mark next to the last commit on the branch:
Or you can go to the Actions
tab (e.g. https://github.com/pds-data-dictionaries/ldd-spectral/actions) and verify the last build has a green checkmark next to it:
- Once the build has been verified, there are now 2 ways you can review the changes the files:
Select the
Files changed
tab, and look through the changed files (e.g. https://github.com/pds-data-dictionaries/ldd-spectral/pull/13/files). You can search on the page for IngestLDD if you simply want to review the changes to that file:
Select the applicable branch, and browse through the files in the repository. The IngestLDD is located under the src/ directory.
Once you have verified all changes, you can approve the Pull Request in Github by going to the
Files changed
tab of the Pull Request, and input your review:
Merging an Approved Pull Request¶
See applicable Github docs: https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request
Generate Human Readable Versions of the LDD¶
LDDTool + Oxygen can be used to generate human readable versions of the data dictionary, the XML file is processed into HTML, PDF, and a WebHelp format. For example:
This is described on the PDS4 Information Model and LDDTool wiki here: https://github.com/NASA-PDS/pds4-information-model/wiki/Generating-Data-Dictionary-Documentation
Use Multiple Files to Define a Single Namespace¶
Sometimes a namespace requires more than one steward to provide expertise on different aspects of the namespace. The Geometry Discipline namespace, for example, has separate stewards for the classes related to fly-by/orbiter observations and lander observations. In a case like this you might find it preferable to split the namespace definition into one file for each steward.
The LDD repo and LDDTool can build a single namespace from multiple files, but developing and maintaining this set of files comes with some special problems and considerations you should be aware of before you start. If you’re considering this option for your namespace, read Multifile Namespaces.
Merge A New Release Branch Into My Current Working Branch¶
In the event that you are working on updates to your LDD in a branch or pull request when a PDS4 system release is about to take place, you may wind up with a new branch and pull request being created.
If you plan to include your updates in the next release, the best route to take is to merge your updates into the newly created release branch.
Here are the steps to do so:
Checkout your branch from Github (e.g.
my_working_branch_v1
)Checkout the newly auto-generated release branch (e.g.
release/<IP_ADDRESS>
)Merge your working branch into the release branch.
Note
Be sure to merge my_working_branch_v1
into release/<IP_ADDRESS>
(release/<IP_ADDRESS>
should become your new working branch) so ensure the release is tagged and included in the system release.
Via command-line:
git merge origin my_working_branch_v1
Via Github Desktop:
How to Change PDS4 Build Versions¶
LDDTool is backwards compatible with PDS4 version <IP_ADDRESS> and later. When using the sub-model template repo, your sub-model automatically builds with the latest version of the PDS4 IM. Here are the steps to change that version or add additional versions:
Open pds4_versions.txt (in the base of your repo), e.g. https://github.com/pds-data-dictionaries/template/blob/main/pds4_versions.txt
Add new line with the applicable version you would like use:
<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>
TBD¶
Feel free to add some of your own or create a ticket in the PDS4 LDD Issue Repo so we can start to build up this documentation.


I watched the "Fireside Chat with Shereef: Kitchen vs. Table" video, and have been brewing over what he addressed. The experience at DBC is really what you make of it. The most successful student will be the one that takes a hands-on approach to their learning. The analogy Shereef used was that of a restaurant staff vs. a patron of the restaurant. The latter comes to the restaurant, likes what the menu has to offer, but complains if there is a hair in the food. Compared to the patron, the restaurant staff would see the hair, and think of solution to avoid getting hair in the food in the future. Basically, the take home message for me is: make the most out of your time at DBC and take ownership of your own learning experience.
My impression of DBC so far is that it is filled with self-motivated learners that aren't afraid of taking risks and working hard. I like this type of environment because it inspires me to be a better student at life. I'm really excited to be a part of this program which doesn't try to just teach you about learning a programming language. DBC tries to impart values of engineering empathy; not only being self aware of your own motivations and thoughts, but to also be able to empathize with other students.
I'm also excited to begin pair programming. I think it will be beneficial to learn from programmers better than me, and hopefully I can also become proficient enough to be able to teach others as well.


{% extends "layout.html" %} {% block page_title %} Money Claims Prototype {% endblock %} {% block proposition_header %} {% set my_account="2" %} {% include "includes/propositional_navigation.html" %} {% endblock %} {% block content %} {% include "includes/phase_banner_beta.html" %} How did you pay the claimant? {% include 'prototypes/prototype-dec-2019/includes/contact.html' %} {% endblock %}


"No matter how hard or impossible it is, never lose sight of your goal."
About me
Im Sergio Gómez, I worked as an artist in this project
At the start of the project I was more destinated to particles but later on I worked on different 3d things like props, characters and enemies.
Contribution
Project overview
Particles
Enviroment props
Enemy
Characters
Boss
Animations
Particles
Overview
Yennefer's attack
Blood
Sparks
Running
Fire
In the early stages of the game I made different particles but they where constantly changing so some of them were replaced or destined for another function.
Enviroment Props
Overview
Rocks
Ravine
Giant Tree
During the vertical slice and the alpha I made some props of rocks for the enviroment, the ravine that acted like a bridge and the giant tree for the forest part.
Enemy
Drowned
Finishing the alpha and during the beta I was in charge of the Drowned, and lately his spawn.
Characters
Geralt
At the beginning of the verticle slice I was in charge of the retopologi of Geralt.
Yennefer
In the middle of the verticle slice I made the second playable character Yennefer.
Boss
Leshen
During the alpha I was in charge of the first boss in the game, the Leshen.
Animations
Ghoul animations
I made 3 animations for the ghoul: getting hit, stuned and jumping.
Leshen attack animation
To complete the boss he needed 2 animations for one of his attacks.


Amadeus Mock API Recorder
All done!
Target URL
Record
Stop
To record stubs from an HTTPS endpoint using browser (forward) proxying, you may need to trust WireMock's CA cert, which can be downloaded here:
wiremock-ca.crt
.


CLOSE
CLOSE
Leave a video / audio message ...
RECORDING...
Push to record
Save
CLOSE
Leave video message
Draw something
Take a picture!
Gallery


The MongoDB transport is a specialized transport that gets data from an existing MongoDB data sink and pulls it into another data sink, either in the same DigitalEdge system or another DigitalEdge system. For example, you might store enriched data in MongoDB and then transport it to a Lucene data sink for indexing. Or, you might store enriched data in a MongoDB data sink in one system and then transport it to another data sink in a second DigitalEdge system for iterative enrichment. Also, you would usually create an SQL select query to run against the MongoDB data sink to pull out a subset of data rather than copying all the data.
| MongoDBTransportService | |
|---|---|
| Parameter | Explanation |
| input-format |
Identifies the data source and parser format that the transport uses to pull data off the input queue; double-click to select a Data Source from your specified data models |
| mongo-collection | The name of the MongoDB table to pull data from |
| mongo-db |
The name of the MongoDB database to pull data from Default = mydb2 |
| mongo-host |
Identifies the data source and parser format that the transport uses to pull data off the input queue; double-click to select a data model from the drop-down menu |
| mongo-port |
The port number to connect to the mongo-host Default = 27017 |
| record-format |
A data record type (BASE64, CONTENT, PCAP, JSON, TEXTLINE, NULL, TEXTLINEWITHQUOTES) that helps to determine record boundaries when input data includes multiple records; double-click to select a format from the drop-down menu Default = NULL |
| record-header-lines |
How many header lines should be stripped out of the data records Default = 0 |
| select-data-statement | The SQL select statement to run against the MongoDB database. If blank, the transport will take all data, which may cause performance issues. |
| state-store-mode |
Indicates if the position state should be stored locally on the instance; used when the transport goes down, to restart where it left off without duplicating any records Default = true |


Class BaseService
Super class for all services
Direct known subclasses
Merchenta\Services\CampaignService
Abstract
Namespace: Merchenta\Services
Package: Services
Author: Baptiste Pernet
Located at Merchenta/Services/BaseService.php
Namespace: Merchenta\Services
Package: Services
Author: Baptiste Pernet
Located at Merchenta/Services/BaseService.php
public
|
#
__construct( Merchenta\Util\MerchentaAuth $auth, Config $config,
Constructor with the option to to supply an alternative rest client to be used |
public
string
|
|
public
|
|
public
|
#
setRestClient(
Set the rest client being used by the service |
protected
array
|
#
getHeaders( )
Helper function to return required headers for making an http request with Merchenta |
protected
|
$restClient |
|
#
RestClient Implementation to use for HTTP requests |
protected
Merchenta\Util\MerchentaAuth
|
$auth |
|
#
Authentication service to get the token to make request. |
protected
Config
|
$config |
|
#
$config - configuration to access to the API. |


Created by Kevin Denver / @ToastShaman
"The JavaScript world seems to be entering a crisis of churn rate. Frameworks and technologies are being pushed out and burned through at an unsustainable speed."
At the close of 2014, it’s difficult as a JavaScript developer to back a particular library or technology with confidence. Even the mighty Angular, which seemed set to establish itself as the One True Framework of Single Page Applications, looks destabilized by recent events.
One Framework To Rule Them All!
AngularJS, KnockoutJS, Ember.js, Mithril, Backbone.js
Would a more simplistic, modular design that evolves with a project’s requirements be a better fit?
Use state of the art JavaScript technologies to build a modular Single Page Web Application that leverages dedicated, single purpose libraries to achieve interconnectivity, rendering and routing.
A micro-site for micro-frameworks
Microjs.com helps you discover the most compact-but-powerful microframeworks, and makes it easy for you to pick one that’ll work for you.
//setup crossroads
crossroads.addRoute('foo');
crossroads.addRoute('lorem/ipsum');
crossroads.routed.add(console.log, console); //log all routes
//setup hasher
function parseHash(newHash, oldHash){
crossroads.parse(newHash);
}
hasher.initialized.add(parseHash); //parse initial hash
hasher.changed.add(parseHash); //parse hash changes
hasher.init(); //start listening for history change
//update URL fragment generating new history record
hasher.setHash('lorem/ipsum');
// Make a request for a user with a given ID
axios.get('/user?ID=12345')
.then(function (response) {
console.log(response);
})
.catch(function (response) {
console.log(response);
});
//custom object that dispatch a `started` signal
var myObject = {
started : new signals.Signal()
};
function onStarted(param1, param2){
alert(param1 + param2);
}
myObject.started.add(onStarted); //add listener
myObject.started.dispatch('foo', 'bar'); //dispatch signal passing custom parameters
myObject.started.remove(onStarted); //remove a single listener
var RSVP = require('rsvp');
var promise = new RSVP.Promise(function(resolve, reject) {
resolve(value);
});
promise.then(function(value) {
// success
}, function(value) {
// failure
});
https://github.com/ToastShaman/zuhlke-days-2015-talk/
or http://bit.ly/1G97CWW


Scriptcoeur
Find a way to include source or CDN include scripts here, ex lodash.
Add content: chrome plugins: colorzilla, whatfont, onetab, restlet, grammarly, spectrum, full page screen capture, GA debug, React developer tools, UsePanda
reading list / sources of inspiration: usepanda, sidebar, designernews, hacker news, Medium / Daily Digest (freecodecamp), Product Hunt, CodePen mailing list,
tutorials/inspiration/ux guides: alistapart.com, tympanus.net, Smashing Magazine
Some components require JS to work properly. Examples are provided to each component in separate js files, under the _scriptcoeur
folder.
- Focus on production speed
- Use as much open source as possible
- Don't reinvent the wheel
Almost everything makes extensive usage of jQuery, so it's included in scriptcoeur scriptcoeur/plugins/jquery.min.js
.
Usage
Easiest way is to just include the js file in html and call the corresponding function (This is quick for development), but you can also integrate it into your own code (copypasta).
1
2
3
4
5
6
7
| <script src="../coeur/scriptcoeur/sticky.js" type="text/javascript"></script>
<script>
$(document).ready(function() {
var triggerElement = "._sidebar-trigger", target = "._sidebar", targetClass = "--pinned";
_sticky(triggerElement, target, targetClass);
});
</script>
|
Some of these are tools, others are plugins. Plugins can be found at scriptcoeur/plugins/[pluginName]
and may be required for some of the scripts. To keep things together, both CSS and JS files should be under the same plugin folder.
Tricks
Creative
Canva
Colors, colors, colors
tinyJPG
Minimizes JPG and PNG files by a lot.
Surge
Static site host w/ password protection
Code & Dev
Auth 0
Oauth single sign-on helper
Apify
Site scraping service
ListJS
List sort & filter plugin.
unCSS
Removes unused CSS selectors.
tota11y
Accessibility audit bookmarklet.
A11y
Accessibility audit + testing.
Flow
Static Type Checker.
Mo JS
Motion for the web.
Slick
Simple carousel plugin.
Rough JS
Creates a sketchy-look for components.
Teamwork
Slack
Real time chat room for teams. Can get distracting.
Other
Doodle
Coordinating many people for meetings


To run this analysis, you need:
- A set of participants who viewed the same stimulus
- Data indicating when each participant blinked
Blink data must be saved in a csv file. There are two acceptable formats:
-
One subject per column
- Each column contains data from one participant
- Each row is a sample
- Data should be collected at a constant sample rate
- Samples should be aligned in time across participants
- There are three acceptable values:
- 1 indicates that a blink was occurring at a sampled time point
- 0 indicates no blink
- NaN indicates lost data (i.e. unknown whether the participant was blinking)
-
Three column format
- Each blink (from all subjects) appears in a separate row
- Three columns (in the following order, no header row):
- Participant identifier – unique to each participant (numeric value)
- Blink start – sample when blink began (integer)
- Blink end – sample when blink ended (integer)
- If this format is selected, you need to specify the length of the data collected, in number of samples


Why Tipping Matters: There are no written rules for giving gratuities, but
it's expected at places where service workers are paid only minimum wage or commissions. You
are not legally required to leave a tip, however, you’re being very unfair to your server if
you choose to be a cheapskate. Many servers completely rely on tips to survive. Keep that in
mind before you bail on a good waitress/waiter.
U.S. Standard: In
2019, the minimum amount to tip is widely understood to be between 15 and 20 percent.


Login
Register
Admin Panel
Sales Persons
Customers
Add Customers
Sales Reports
Register Customer
Basic Details
Current date
Date of Birth
First Name
Last Name
Email
Phone
Marital Status
Select Status
Married
Single
Nationality
Select Nationality
Ugandan
Kenyan
Tanzanian
NIN ID
Vehicle Details
Vehicle
Select Type
bodaboda
tuktuk
tricycle
Payment Amount
Next to Kin
Referee’s name
Referee’s phone
Work of the referee
Referee Date of Birth
Address Details
Other Loans
Stage name
LC1
LC2
Confirm of required copies of documents
Submit
Cancel


The goDesign components represent complex implementations of our goDesign standard elements.
Using a node module and NPM we will be able to distribute and maintain our components quickly and efficiently.
This methodology is heavily based on Atomic Design which lends itself towards thinking of our UIs as thoughtful hierarchies, discusses the qualities of effective pattern libraries, and showcases techniques to transform your team's design and development workflow.