Noctivity Apps "the App” provide Shopify apps including Bulk Order Refund, "the Service" to merchants who use Shopify to power their stores. This Privacy Policy describes how personal information is collected, used, and shared when you install or use the App in connection with your Shopify-supported store.
When you install the App, we are automatically able to access certain types of information from your Shopify account: the name and URL of your shop
Additionally, we collect the following types of personal information from you and/or your customers once you have installed the App:
Bulk Order Refunds
We collect personal information directly from the relevant individual, through your Shopify account if listed above, or using the following technologies: “Cookies” are data files that are placed on your device or computer and often include an anonymous unique identifier. For more information about cookies, and how to disable cookies, visit http://www.allaboutcookies.org. “Log files” track actions occurring on the Site, and collect data including your IP address, browser type, Internet service provider, referring/exit pages, and date/time stamps. “Web beacons,” “tags,” and “pixels” are electronic files used to record information about how you browse the Site.
We use the personal information we collect from you and your customers in order to provide the Service and to operate the App if any information is collection. Additionally, we use this personal information to: Communicate with you; Optimize or improve the App; and Provide you with information or advertising relating to our products or services.
Your personal information is not shared or sold to any third parties.
Finally, we may also share your Personal Information to comply with applicable laws and regulations, to respond to a subpoena, search warrant or other lawful request for information we receive, or to otherwise protect our rights.
As described above, we use your Personal Information to provide you with targeted advertisements or marketing communications we believe may be of interest to you. For more information about how targeted advertising works, you can visit the Network Advertising Initiative’s (“NAI”) educational page at http://www.networkadvertising.org/understanding-online-advertising/how-does-it-work.
You have the right to access personal information we hold about you and to ask that your personal information be corrected, updated, or deleted. If you would like to exercise this right, please contact us through the contact information below.
Additionally, if you are a European resident we note that we are processing your information in order to fulfill contracts we might have with you (for example if you make an order through the Site), or otherwise to pursue our legitimate business interests listed above. Additionally, please note that your information will be transferred outside of Europe, including to Canada and the United States.
We may update this privacy policy from time to time in order to reflect, for example, changes to our practices or for other operational, legal or regulatory reasons.
For more information about our privacy practices, if you have questions, or if you would like to make a complaint, please contact us by e-mail at<EMAIL_ADDRESS>or by mail using the details provided below:
Noctivity Inc.
210 Delburg St, Ste 316
Davidson, NC 28036


PART II. CAFETERIA PLANS--REPEALED
§§78-61 to 63 REPEALED. L 2000, c 253, §90.
Cross References
For present provision, see §78-30.


All Files (61.99% covered at 0.71 hits/line)
48 files in total.
442 relevant lines.
274 lines covered and
168 lines missed
- 1
class ApplicationController < ActionController::Base
# Prevent CSRF attacks by raising an exception.
# For APIs, you may want to use :null_session instead.
- 1
protect_from_forgery with: :exception
end
- 1
class ContractController < ApplicationController
- 1
def index
end
end
- 1
class CustomersController < ApplicationController
- 1
def new
@list = List.find(params[:list_id])
@customer = @list.customers.new
end
- 1
def create
@list = List.find(params[:list_id])
@customer = @list.customers.new(customer_params)
if @customer.save
redirect_to<EMAIL_ADDRESS>else
render :new
end
end
- 1
def edit
@list = List.find(params[:list_id])
@customer = Customer.find(params[:id])
render :edit
end
- 1
def update
@customer = Customer.find(params[:id])
if @customer.update(customer_params)
redirect_to list_path(params[:list_id])
else
render :edit
end
end
- 1
def mark
@customer = Customer.find(params[:id])
@customer.update_attribute(:done, true)
redirect_to list_path(params[:list_id])
end
- 1
def destroy
@customer = Customer.find(params[:id])
@customer.destroy
redirect_to list_path(params[:list_id])
end
- 1
private
- 1
def customer_params
params.require(:customer).permit(:name)
# params.require(:customer).permit(:done)
end
end
- 1
class DogsController < ApplicationController
- 1
def index
@dogs = Dog.all
end
- 1
def new
@dog = Dog.new
end
- 1
def create
@dog = Dog.create(dog_params)
@dog.user = current_user
if @dog.save
redirect_to dog_path(@dog)
else
render :new
end
end
- 1
def show
@dog = Dog.find(params[:id])
@litters = @dog.litters
end
- 1
def edit
@dog = Dog.find(params[:id])
end
- 1
def update
@dog = Dog.find(params[:id])
if @dog.update(dog_params)
redirect_to<EMAIL_ADDRESS>else
render :edit
end
end
- 1
private
- 1
def dog_params
params.require(:dog).permit(:name, :date_of_birth, :sex)
end
end
- 1
class HomeController < ApplicationController
- 1
def index
@pictures = Picture.all
@Lists = List.all
end
end
- 1
class InfoController < ApplicationController
- 1
def index
end
end
- 1
class ListsController < ApplicationController
- 1
def index
@lists = List.all
render :index
end
- 1
def show
@list = List.find(params[:id])
render :show
end
- 1
def new
@list = List.new
render :new
end
- 1
def create
@list = List.new(list_params)
if @list.save
redirect_to lists_path
else
render :new
end
end
- 1
def edit
@list = List.find(params[:id])
render :edit
end
- 1
def update
@list = List.find(params[:id])
if @list.update(list_params)
redirect_to lists_path
else
render :edit
end
end
- 1
def destroy
@list = List.find(params[:id])
@list.destroy
redirect_to lists_path
end
- 1
private
- 1
def list_params
params.require(:list).permit(:name)
end
end
- 1
class LittersController < ApplicationController
- 1
def show
@litter = Litter.find(params[:id])
@dog =<EMAIL_ADDRESS>@puppies = @litter.puppies
end
- 1
def index
@litters = Litter.all
end
- 1
def new
@dog = Dog.find(params[:dog_id])
@litter = Litter.new
end
- 1
def create
@dog = Dog.find(params[:dog_id])
@litter = @dog.litters.new(litter_params)
@litter.user = current_user
if @litter.save
redirect_to<EMAIL_ADDRESS>else
render :new
end
end
- 1
private
- 1
def litter_params
params.require(:litter).permit(:due_date)
end
end
- 1
class PicturesController < ApplicationController
- 1
def index
@pictures = Picture.all
end
- 1
def new
@picture = Picture.new
if params[:dog]
@imageable_id = (params[:dog])
@imageable_type = 'Dog'
elsif params[:puppy]
@imageable_id = (params[:puppy])
@imageable_type = 'Puppy'
else
@imageable_id = (params[:litter])
@imageable_type = 'Litter'
end
end
- 1
def create
@picture = Picture.new(picture_params)
if @picture.save
redirect_to :back
else
render :new
end
end
- 1
def destroy
@picture = Picture.find(params[:id])
@picture.destroy
redirect_to :back
end
- 1
private
- 1
def picture_params
params.require(:picture).permit(:name, :imageable_id, :imageable_type)
end
end
- 1
class PuppiesController < ApplicationController
- 1
def show
@litter = Litter.find(params[:litter_id])
@dog =<EMAIL_ADDRESS>@puppy = Puppy.find(params[:id])
end
- 1
def new
@litter = Litter.find(params[:litter_id])
@puppy = Puppy.new
end
- 1
def create
@litter = Litter.find(params[:litter_id])
@dog =<EMAIL_ADDRESS>@puppy = @litter.puppies.new(puppy_params)
@puppy.user = current_user
if @puppy.save
redirect_to<EMAIL_ADDRESS>else
render :new
end
end
- 1
def edit
@litter = Litter.find(params[:litter_id])
@dog =<EMAIL_ADDRESS>@puppy = Puppy.find(params[:id])
end
- 1
def update
@litter = Litter.find(params[:litter_id])
@dog =<EMAIL_ADDRESS>@puppy= Puppy.find(params[:id])
if @puppy.update(puppy_params)
redirect_to<EMAIL_ADDRESS>@puppy.id)
else
render :edit
end
end
- 1
def destroy
@puppy = Puppy.find(params[:id])
@litter =<EMAIL_ADDRESS>@dog =<EMAIL_ADDRESS>@puppy.destroy
redirect_to<EMAIL_ADDRESS>end
- 1
private
- 1
def puppy_params
params.require(:puppy).permit(:name, :sex, :date_of_birth, :weight)
end
end
- 1
class UsersController < ApplicationController
- 1
def show
@user = User.find(params[:id])
@dogs = @user.dogs
end
- 1
def index
end
end
- 1
module ApplicationHelper
- 1
def tel_to(text)
groups = text.to_s.scan(/(?:^\+)?\d+/)
link_to text, "tel:#{groups.join '-'}"
end
end
- 1
class Customer<ActiveRecord::Base
- 1
belongs_to :list
- 1
validates :name, :presence => true
end
- 1
class Dog<ActiveRecord::Base
- 1
validates_presence_of :name
- 1
validates_presence_of :date_of_birth
- 1
validates_presence_of :sex
- 1
belongs_to :user
- 1
has_many :litters
- 1
has_many :pictures, as: :imageable
end
- 1
class List<ActiveRecord::Base
- 1
validates_presence_of :name
- 1
has_many :customers
end
- 1
class Litter<ActiveRecord::Base
- 1
validates_presence_of :due_date
- 1
belongs_to :user
- 1
belongs_to :dog
- 1
has_many :puppies
- 1
has_many :pictures, as: :imageable
- 1
def upcoming_litters
Litter.all.each do |litter|
if litter.due_date >= Date.today
litter.due_date
end
end
end
end
- 1
class Picture < ActiveRecord::Base
- 1
belongs_to :imageable, polymorphic: true
- 1
has_attached_file :name, :styles => { :medium => "300x300#" }
- 1
validates_attachment_content_type :name, content_type: /\Aimage\/.*\Z/
end
- 1
class Puppy<ActiveRecord::Base
- 1
validates_presence_of :date_of_birth
- 1
validates_presence_of :name
- 1
validates_presence_of :sex
- 1
validates_presence_of :weight
- 1
belongs_to :user
- 1
belongs_to :litter
- 1
has_many :pictures, as: :imageable
end
- 1
class Registration<ActiveRecord::Base
- 1
belongs_to :puppy
- 1
belongs_to :user
- 1
validates :full_name, :email, :telephone, presence: true
# allow different types of notifications
- 1
serialize :notification_params, Hash
- 1
def paypal_url(return_path)
values = {
business<EMAIL_ADDRESS>cmd: "_xclick",
upload: 1,
return: "#{Rails.application.secrets.app_host}#{return_path}",
invoice: id,
amount: 300,
item_name: puppy.name,
item_number: puppy.id,
quantity: '1'
}
"#{Rails.application.secrets.paypal_host}/cgi-bin/webscr?" + values.to_query
end
end
- 1
class User < ActiveRecord::Base
# Include default devise modules. Others available are:
# :confirmable, :lockable, :timeoutable and :omniauthable
- 1
has_many :puppies
- 1
has_many :litters
- 1
has_many :dogs
- 1
devise :database_authenticatable, :registerable,
:recoverable, :rememberable, :trackable, :validatable
end
- 1
require File.expand_path('../boot', __FILE__)
- 1
require "rails"
# Pick the frameworks you want:
- 1
require "active_model/railtie"
- 1
require "active_job/railtie"
- 1
require "active_record/railtie"
- 1
require "action_controller/railtie"
- 1
require "action_mailer/railtie"
- 1
require "action_view/railtie"
- 1
require "sprockets/railtie"
# require "rails/test_unit/railtie"
# Require the gems listed in Gemfile, including any gems
# you've limited to :test, :development, or :production.
- 1
Bundler.require(*Rails.groups)
- 1
module Bernedoodles
- 1
class Application < Rails::Application
# Settings in config/environments/* take precedence over those specified here.
# Application configuration should go into files in config/initializers
# -- all .rb files in that directory are automatically loaded.
# Set Time.zone default to the specified zone and make Active Record auto-convert to this zone.
# Run "rake -D time" for a list of tasks for finding time zone names. Default is UTC.
# config.time_zone = 'Central Time (US & Canada)'
# The default locale is :en and all translations from config/locales/*.rb,yml are auto loaded.
# config.i18n.load_path += Dir[Rails.root.join('my', 'locales', '*.{rb,yml}').to_s]
# config.i18n.default_locale = :de
# Do not swallow errors in after_commit/after_rollback callbacks.
- 1
config.active_record.raise_in_transactional_callbacks = true
- 1
config.assets.initialize_on_precompile = false
end
end
- 1
ENV['BUNDLE_GEMFILE'] ||= File.expand_path('../../Gemfile', __FILE__)
- 1
require 'bundler/setup' # Set up gems listed in the Gemfile.
# Load the Rails application.
- 1
require File.expand_path('../application', __FILE__)
# Initialize the Rails application.
- 1
Rails.application.initialize!
- 1
Rails.application.configure do
# Settings specified here will take precedence over those in config/application.rb.
# The test environment is used exclusively to run your application's
# test suite. You never need to work with it otherwise. Remember that
# your test database is "scratch space" for the test suite and is wiped
# and recreated between test runs. Don't rely on the data there!
- 1
config.cache_classes = true
# Do not eager load code on boot. This avoids loading your whole application
# just for the purpose of running a single test. If you are using a tool that
# preloads Rails for running tests, you may have to set it to true.
- 1
config.eager_load = true
# Configure static file server for tests with Cache-Control for performance.
- 1
config.serve_static_files = true
- 1
config.static_cache_control = 'public, max-age=3600'
# Show full error reports and disable caching.
- 1
config.consider_all_requests_local = true
- 1
config.action_controller.perform_caching = false
# Raise exceptions instead of rendering exception templates.
- 1
config.action_dispatch.show_exceptions = false
# Disable request forgery protection in test environment.
- 1
config.action_controller.allow_forgery_protection = false
# Tell Action Mailer not to deliver emails to the real world.
# The :test delivery method accumulates sent emails in the
# ActionMailer::Base.deliveries array.
- 1
config.action_mailer.delivery_method = :test
# Randomize the order test cases are executed.
- 1
config.active_support.test_order = :random
# Print deprecation notices to the stderr.
- 1
config.active_support.deprecation = :stderr
# Raises error for missing translations
# config.action_view.raise_on_missing_translations = true
end
# Be sure to restart your server when you modify this file.
# Version of your assets, change this if you want to expire all your assets.
- 1
Rails.application.config.assets.version = '1.0'
# Add additional assets to the asset load path
# Rails.application.config.assets.paths << Emoji.images_path
# Precompile additional assets.
# application.js, application.css, and all non-JS/CSS in app/assets folder are already added.
# Rails.application.config.assets.precompile += %w( search.js )
# Be sure to restart your server when you modify this file.
# You can add backtrace silencers for libraries that you're using but don't wish to see in your backtraces.
# Rails.backtrace_cleaner.add_silencer { |line| line =~ /my_noisy_library/ }
# You can also remove all the silencers if you're trying to debug a problem that might stem from framework code.
# Rails.backtrace_cleaner.remove_silencers!
# Be sure to restart your server when you modify this file.
- 1
Rails.application.config.action_dispatch.cookies_serializer = :json
# Use this hook to configure devise mailer, warden hooks and so forth.
# Many of these configuration options can be set straight in your model.
- 1
Devise.setup do |config|
# The secret key used by Devise. Devise uses this key to generate
# random tokens. Changing this key will render invalid all existing
# confirmation, reset password and unlock tokens in the database.
# Devise will use the `secret_key_base` on Rails 4+ applications as its `secret_key`
# by default. You can change it below and use your own secret key.
# config.secret_key = 'a1afa635e683cbb3a33bcf794cfea8b5d6ee8749ca838ac1f650c9b834456889e29d34e601130bec2257325f0fe354af7c2f24fb612d70320ec7ab653980ae0f'
- 1
config.secret_key = '9a0f80b86bd91ef9aea958aa297a10c6b41b1d3c4a49386c548071b084a6c75467b439b1c50fecf5ffb9fec73fceee640dc43531b9d0aa88dc3506fb88e84c31'
# ==> Mailer Configuration
# Configure the e-mail address which will be shown in Devise::Mailer,
# note that it will be overwritten if you use your own mailer class
# with default "from" parameter.
- 1
config.mailer_sender =<EMAIL_ADDRESS># Configure the class responsible to send e-mails.
# config.mailer = 'Devise::Mailer'
# ==> ORM configuration
# Load and configure the ORM. Supports :active_record (default) and
# :mongoid (bson_ext recommended) by default. Other ORMs may be
# available as additional gems.
- 1
require 'devise/orm/active_record'
# ==> Configuration for any authentication mechanism
# Configure which keys are used when authenticating a user. The default is
# just :email. You can configure it to use [:username, :subdomain], so for
# authenticating a user, both parameters are required. Remember that those
# parameters are used only when authenticating and not when retrieving from
# session. If you need permissions, you should implement that in a before filter.
# You can also supply a hash where the value is a boolean determining whether
# or not authentication should be aborted when the value is not present.
# config.authentication_keys = [:email]
# Configure parameters from the request object used for authentication. Each entry
# given should be a request method and it will automatically be passed to the
# find_for_authentication method and considered in your model lookup. For instance,
# if you set :request_keys to [:subdomain], :subdomain will be used on authentication.
# The same considerations mentioned for authentication_keys also apply to request_keys.
# config.request_keys = []
# Configure which authentication keys should be case-insensitive.
# These keys will be downcased upon creating or modifying a user and when used
# to authenticate or find a user. Default is :email.
- 1
config.case_insensitive_keys = [:email]
# Configure which authentication keys should have whitespace stripped.
# These keys will have whitespace before and after removed upon creating or
# modifying a user and when used to authenticate or find a user. Default is :email.
- 1
config.strip_whitespace_keys = [:email]
# Tell if authentication through request.params is enabled. True by default.
# It can be set to an array that will enable params authentication only for the
# given strategies, for example, `config.params_authenticatable = [:database]` will
# enable it only for database (email + password) authentication.
# config.params_authenticatable = true
# Tell if authentication through HTTP Auth is enabled. False by default.
# It can be set to an array that will enable http authentication only for the
# given strategies, for example, `config.http_authenticatable = [:database]` will
# enable it only for database authentication. The supported strategies are:
# :database = Support basic authentication with authentication key + password
# config.http_authenticatable = false
# If 401 status code should be returned for AJAX requests. True by default.
# config.http_authenticatable_on_xhr = true
# The realm used in Http Basic Authentication. 'Application' by default.
# config.http_authentication_realm = 'Application'
# It will change confirmation, password recovery and other workflows
# to behave the same regardless if the e-mail provided was right or wrong.
# Does not affect registerable.
# config.paranoid = true
# By default Devise will store the user in session. You can skip storage for
# particular strategies by setting this option.
# Notice that if you are skipping storage for all authentication paths, you
# may want to disable generating routes to Devise's sessions controller by
# passing skip: :sessions to `devise_for` in your config/routes.rb
- 1
config.skip_session_storage = [:http_auth]
# By default, Devise cleans up the CSRF token on authentication to
# avoid CSRF token fixation attacks. This means that, when using AJAX
# requests for sign in and sign up, you need to get a new CSRF token
# from the server. You can disable this option at your own risk.
# config.clean_up_csrf_token_on_authentication = true
# ==> Configuration for :database_authenticatable
# For bcrypt, this is the cost for hashing the password and defaults to 10. If
# using other encryptors, it sets how many times you want the password re-encrypted.
#
# Limiting the stretches to just one in testing will increase the performance of
# your test suite dramatically. However, it is STRONGLY RECOMMENDED to not use
# a value less than 10 in other environments. Note that, for bcrypt (the default
# encryptor), the cost increases exponentially with the number of stretches (e.g.
# a value of 20 is already extremely slow: approx. 60 seconds for 1 calculation).
- 1
config.stretches = Rails.env.test? ? 1 : 10
# Setup a pepper to generate the encrypted password.
# config.pepper = '26705ba427860195fa980e71a771bb0d091542bf1b27dfbfed9b28c890eb70409a03a0f65b69c127ec1366c8d42a6e9605bc54ed4965da12267c990c4f82c5f3'
# ==> Configuration for :confirmable
# A period that the user is allowed to access the website even without
# confirming their account. For instance, if set to 2.days, the user will be
# able to access the website for two days without confirming their account,
# access will be blocked just in the third day. Default is 0.days, meaning
# the user cannot access the website without confirming their account.
# config.allow_unconfirmed_access_for = 2.days
# A period that the user is allowed to confirm their account before their
# token becomes invalid. For example, if set to 3.days, the user can confirm
# their account within 3 days after the mail was sent, but on the fourth day
# their account can't be confirmed with the token any more.
# Default is nil, meaning there is no restriction on how long a user can take
# before confirming their account.
# config.confirm_within = 3.days
# If true, requires any email changes to be confirmed (exactly the same way as
# initial account confirmation) to be applied. Requires additional unconfirmed_email
# db field (see migrations). Until confirmed, new email is stored in
# unconfirmed_email column, and copied to email column on successful confirmation.
- 1
config.reconfirmable = true
# Defines which key will be used when confirming an account
# config.confirmation_keys = [:email]
# ==> Configuration for :rememberable
# The time the user will be remembered without asking for credentials again.
# config.remember_for = 2.weeks
# Invalidates all the remember me tokens when the user signs out.
- 1
config.expire_all_remember_me_on_sign_out = true
# If true, extends the user's remember period when remembered via cookie.
# config.extend_remember_period = false
# Options to be passed to the created cookie. For instance, you can set
# secure: true in order to force SSL only cookies.
# config.rememberable_options = {}
# ==> Configuration for :validatable
# Range for password length.
- 1
config.password_length = 8..72
# Email regex used to validate email formats. It simply asserts that
# one (and only one) @ exists in the given string. This is mainly
# to give user feedback and not to assert the e-mail validity.
# config.email_regexp = /\A[^@]+@[^@]+\z/
# ==> Configuration for :timeoutable
# The time you want to timeout the user session without activity. After this
# time the user will be asked for credentials again. Default is 30 minutes.
# config.timeout_in = 30.minutes
# ==> Configuration for :lockable
# Defines which strategy will be used to lock an account.
# :failed_attempts = Locks an account after a number of failed attempts to sign in.
# :none = No lock strategy. You should handle locking by yourself.
# config.lock_strategy = :failed_attempts
# Defines which key will be used when locking and unlocking an account
# config.unlock_keys = [:email]
# Defines which strategy will be used to unlock an account.
# :email = Sends an unlock link to the user email
# :time = Re-enables login after a certain amount of time (see :unlock_in below)
# :both = Enables both strategies
# :none = No unlock strategy. You should handle unlocking by yourself.
# config.unlock_strategy = :both
# Number of authentication tries before locking an account if lock_strategy
# is failed attempts.
# config.maximum_attempts = 20
# Time interval to unlock the account if :time is enabled as unlock_strategy.
# config.unlock_in = 1.hour
# Warn on the last attempt before the account is locked.
# config.last_attempt_warning = true
# ==> Configuration for :recoverable
#
# Defines which key will be used when recovering the password for an account
# config.reset_password_keys = [:email]
# Time interval you can reset your password with a reset password key.
# Don't put a too small interval or your users won't have the time to
# change their passwords.
- 1
config.reset_password_within = 6.hours
# When set to false, does not sign a user in automatically after their password is
# reset. Defaults to true, so a user is signed in automatically after a reset.
# config.sign_in_after_reset_password = true
# ==> Configuration for :encryptable
# Allow you to use another encryption algorithm besides bcrypt (default). You can use
# :sha1, :sha512 or encryptors from others authentication tools as :clearance_sha1,
# :authlogic_sha512 (then you should set stretches above to 20 for default behavior)
# and :restful_authentication_sha1 (then you should set stretches to 10, and copy
# REST_AUTH_SITE_KEY to pepper).
#
# Require the `devise-encryptable` gem when using anything other than bcrypt
# config.encryptor = :sha512
# ==> Scopes configuration
# Turn scoped views on. Before rendering "sessions/new", it will first check for
# "users/sessions/new". It's turned off by default because it's slower if you
# are using only default views.
# config.scoped_views = false
# Configure the default scope given to Warden. By default it's the first
# devise role declared in your routes (usually :user).
# config.default_scope = :user
# Set this configuration to false if you want /users/sign_out to sign out
# only the current scope. By default, Devise signs out all scopes.
# config.sign_out_all_scopes = true
# ==> Navigation configuration
# Lists the formats that should be treated as navigational. Formats like
# :html, should redirect to the sign in page when the user does not have
# access, but formats like :xml or :json, should return 401.
#
# If you have any extra navigational formats, like :iphone or :mobile, you
# should add them to the navigational formats lists.
#
# The "*/*" below is required to match Internet Explorer requests.
# config.navigational_formats = ['*/*', :html]
# The default HTTP method used to sign out a resource. Default is :delete.
- 1
config.sign_out_via = :delete
# ==> OmniAuth
# Add a new OmniAuth provider. Check the wiki for more information on setting
# up on your models and hooks.
# config.omniauth :github, 'APP_ID', 'APP_SECRET', scope: 'user,public_repo'
# ==> Warden configuration
# If you want to use other strategies, that are not supported by Devise, or
# change the failure app, you can configure them inside the config.warden block.
#
# config.warden do |manager|
# manager.intercept_401 = false
# manager.default_strategies(scope: :user).unshift :some_external_strategy
# end
# ==> Mountable engine configurations
# When using Devise inside an engine, let's call it `MyEngine`, and this engine
# is mountable, there are some extra configurations to be taken into account.
# The following options are available, assuming the engine is mounted as:
#
# mount MyEngine, at: '/my_engine'
#
# The router that invoked `devise_for`, in the example above, would be:
# config.router_name = :my_engine
#
# When using OmniAuth, Devise cannot automatically set OmniAuth path,
# so you need to do it manually. For the users scope, it would be:
# config.omniauth_path_prefix = '/my_engine/users/auth'
end
# Be sure to restart your server when you modify this file.
# Configure sensitive parameters which will be filtered from the log file.
- 1
Rails.application.config.filter_parameters += [:password]
# Be sure to restart your server when you modify this file.
# Add new inflection rules using the following format. Inflections
# are locale specific, and you may define rules for as many different
# locales as you wish. All of these examples are active by default:
# ActiveSupport::Inflector.inflections(:en) do |inflect|
# inflect.plural /^(ox)$/i, '\1en'
# inflect.singular /^(ox)en/i, '\1'
# inflect.irregular 'person', 'people'
# inflect.uncountable %w( fish sheep )
# end
# These inflection rules are supported but not enabled by default:
# ActiveSupport::Inflector.inflections(:en) do |inflect|
# inflect.acronym 'RESTful'
# end
# Be sure to restart your server when you modify this file.
# Add new mime types for use in respond_to blocks:
# Mime::Type.register "text/richtext", :rtf
# config/initializers/paperclip.rb
- 1
Paperclip::Attachment.default_options[:url] = ':s3_domain_url'
- 1
Paperclip::Attachment.default_options[:path] = '/:class/:attachment/:id_partition/:style/:filename'
- 1
Paperclip::Attachment.default_options[:s3_host_name] = 's3-us-west-2.amazonaws.com'
- 1
PayPal::SDK.load("config/paypal.yml", Rails.env)
- 1
PayPal::SDK.logger = Rails.logger
# Be sure to restart your server when you modify this file.
- 1
Rails.application.config.session_store :cookie_store, key: '_bernedoodles_session'
# Be sure to restart your server when you modify this file.
# This file contains settings for ActionController::ParamsWrapper which
# is enabled by default.
# Enable parameter wrapping for JSON. You can disable this by setting :format to an empty array.
- 1
ActiveSupport.on_load(:action_controller) do
- 1
wrap_parameters format: [:json] if respond_to?(:wrap_parameters)
end
# To enable root element in JSON for ActiveRecord objects.
# ActiveSupport.on_load(:active_record) do
# self.include_root_in_json = true
# end
- 1
Rails.application.routes.draw do
- 1
devise_for :users
- 1
root to: "home#index"
- 1
resources :dogs do
- 1
resources :litters, only: [:new, :create]
end
- 1
resources :litters, :except => [:new, :create] do
- 1
resources :puppies
end
- 1
resources :pictures
- 1
resources :users, only: [:index, :show]
- 1
resources :registrations, only: [:create]
- 1
resources :lists do
- 1
resources :customers
end
- 1
get 'userpage', to: 'users#index', as: 'userpage'
- 1
get 'info', to: 'info#index', as: 'info'
- 1
get 'contract', to: 'contract#index', as: 'contract'
- 1
post "/registrations/:id" => "registrations#show"
- 1
post "/hook" => "regstrations#hook"
end
- 1
FactoryGirl.define do
- 1
factory(:dog) do
- 1
name("Zoe")
- 1
date_of_birth Date.new(2005, 07, 1)
- 1
sex("female")
end
- 1
factory(:litter) do
- 1
due_date Date.new(2007, 01, 21)
end
- 1
factory(:puppy) do
- 1
name("Tucker")
- 1
date_of_birth Date.new(2007, 01, 21)
- 1
sex("male")
- 1
weight(2)
end
- 1
factory(:user) do
- 1
<EMAIL_ADDRESS>- 1
password("password")
end
end
- 1
require 'rails_helper'
- 1
require 'support/session_helpers'
- 1
describe 'the process of adding a dog' do
- 1
before do
- 2
sign_in
end
- 1
it 'allows a user to add a new dog' do
visit user_path(@admin_user)
find('#new_dog_link').click
fill_in 'Name', :with => 'Zoe'
fill_in 'Sex', :with => 'female'
fill_in 'Date of birth', :with => '2005, 07, 1'
find("input#create_dog").click
expect(page).to have_content 'Zoe'
end
- 1
it 'Displays errors if a field is left blank for a new dog' do
visit user_path(@admin_user)
find('#new_dog_link').click
fill_in 'Name', :with => 'Zoe'
fill_in 'Sex', :with => 'female'
find("input#create_dog").click
expect(page).to have_content 'errors'
end
end
- 1
require 'rails_helper'
- 1
require 'support/session_helpers'
- 1
describe 'the process of adding a puppy' do
- 1
before do
- 2
sign_in
create_factories
end
- 1
it 'allows a user to add a new puppy' do
visit dog_litter_path(@dog, @litter)
find('#new_puppy_link').click
fill_in 'Name', :with => 'Pink'
fill_in 'Sex', :with => 'female'
fill_in 'Date of birth', :with => '2005, 07, 1'
fill_in 'Weight', :with => '3'
click_on "Submit"
expect(page).to have_content 'Pink'
end
- 1
it 'checks for errors when adding a new puppy' do
visit dog_litter_path(@dog, @litter)
find('#new_puppy_link').click
fill_in 'Name', :with => 'Pink'
fill_in 'Sex', :with => 'female'
fill_in 'Date of birth', :with => '2005, 07, 1'
click_on "Submit"
expect(page).to have_content 'errors'
end
end
- 1
require 'rails_helper'
- 1
describe 'the add a user process' do
- 1
before do
- 2
@user = FactoryGirl.create(:user)
- 2
@password = 'password'
end
- 1
it 'can add a user' do
- 1
visit new_user_registration_path
fill_in 'Email', :with =><EMAIL_ADDRESS>fill_in 'Password', :with => @password
fill_in 'Password confirmation', :with => @password
find("input#sign_up").click
expect(page).to have_content 'Welcome!' # takes user to sign in page
end
- 1
it 'displays errors when the form password and password confirmation do not match' do
- 1
visit new_user_registration_path
fill_in 'Email', :with =><EMAIL_ADDRESS>fill_in 'Password', :with => @password
find("input#sign_up").click
expect(page).to have_content "Password confirmation doesn't match Password Email Password"
end
end
- 1
require 'rails_helper'
- 1
describe Customer do
- 2
it { should validate_presence_of :name }
- 2
it { should belong_to :list }
end
- 1
require 'rails_helper'
- 1
describe Dog do
- 2
it { should validate_presence_of :name}
- 2
it { should validate_presence_of :date_of_birth}
- 2
it { should validate_presence_of :sex}
- 2
it { should have_many :litters}
- 2
it { should have_many :pictures}
end
- 1
require 'rails_helper'
- 1
describe List do
- 2
it { should validate_presence_of :name}
end
- 1
require 'rails_helper'
- 1
describe Litter do
- 2
it { should validate_presence_of :due_date}
- 2
it { should belong_to :user }
- 2
it { should belong_to :dog }
- 2
it { should have_many :puppies }
- 2
it { should have_many :pictures }
end
- 1
require 'rails_helper'
- 1
describe Puppy do
- 2
it { should validate_presence_of :name}
- 2
it { should validate_presence_of :date_of_birth}
- 2
it { should validate_presence_of :sex}
# it { should validate_presence_of :weight}
- 2
it { should belong_to :litter}
- 2
it { should belong_to :user}
- 2
it { should have_many :pictures}
end
- 1
require 'rails_helper'
- 1
describe User do
- 2
it { should validate_presence_of :email}
- 2
it { should validate_presence_of :password}
- 2
it { should have_many :dogs}
- 2
it { should have_many :litters}
- 2
it { should have_many :puppies}
end
# This file is copied to spec/ when you run 'rails generate rspec:install'
- 1
ENV['RAILS_ENV'] ||= 'test'
- 1
require File.expand_path('../../config/environment', __FILE__)
# Prevent database truncation if the environment is production
- 1
abort("The Rails environment is running in production mode!") if Rails.env.production?
- 1
require 'spec_helper'
- 1
require 'rspec/rails'
- 1
require 'capybara/rails'
- 1
require 'devise.rb'
- 1
ActiveRecord::Migration.maintain_test_schema!
- 1
RSpec.configure do |config|
- 1
config.include Devise::TestHelpers, type: :controller
- 1
config.fixture_path = "#{::Rails.root}/spec/fixtures"
- 1
config.use_transactional_fixtures = true
- 1
config.infer_spec_type_from_file_location!
end
- 1
Shoulda::Matchers.configure do |config|
- 1
config.integrate do |with|
- 1
with.test_framework :rspec
- 1
with.library :rails
end
end
- 1
def sign_in
- 4
@admin_user = User.new(:email => 'TestEmail', :password => 'password', :password_confirmation => 'password')
- 4
@admin_user.save
- 4
visit user_session_path
fill_in 'Email', with: @admin_user.email
fill_in 'Password', with: @admin_user.password
click_button 'Log in'
end
- 1
def create_factories
@dog = FactoryGirl.create(:dog)
@litter = FactoryGirl.create(:litter)
end


Skills
UI/UX Design
Applying visual principles to plan a user journey and crafting functional and interactive interfaces that leave a lasting impression.
Coding
Developing scalable and reliable web or software based applications to meet specific needs while employing new and agile technologies.
Team Orintated
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis vel nisi venenatis, congue magna sed, porttitor ipsum. Aenean nec velit.
Content Creation
Using a buffet of tools to craft rich content that compliments the project at hand.
Send me a message, I would love to hear from you.


---
layout: default
---
PART Specifications
Quick introduction to technical properties of Particl's native PART coin. Read our PART coin FAQ on Wiki for more details
Updated August 15, 2018
Blockchain specifications
| Block time |
120 seconds 5× faster than BTC |
| Block size |
2 MB 2× larger than BTC |
| Consensus mechanism |
Particl Proof-of-Stake
with quantum-resistant cold-staking
|
| Money Supply |
≈ 9.081 million PART |
| Always up-to-date BTC codebase |
New changes to Bitcoin codebase are integrated to Particl regularly to keep up with latest security fixes and performance improvements |
| SegWit Segregated Witness |
Native support for all transactions |
| Atomic Swaps |
Supported with compatible blockchains
|
| Fair distribution |
No ICO, no pre-mine |
Staking
| Particl Cold Staking |
Staking via dedicated devices or hardware wallets |
| Yearly interest rate |
4 % decreasing each year by 1% (after 2 years onwards 2% yearly) |
| Current staking reward |
≈ 1.2428 PART |
| Coin maturity |
225 confirmations approx. 8 hours |
Privacy features
| Multi-state privacy |
3 optional privacy levels for transactions |
| Public transactions |
Bitcoin-like public transactions, auditable on blockchain |
| Blind transactions AKA Confidential Transactions (CT) |
Transaction parties are visible on blockchain, but the amount is hidden |
| Private transactions AKA RingCT |
On testnet only Both transaction parties & amounts are hidden on blockchain |
Security features
| Multi-signature wallets |
Supported with Particl Copay |
| Ledger hardware wallet |
Supported with Particl Qt |
| Trezor hardware wallet |
In development Supported with Particl Qt |
| Staking from hardware wallet |
Keep your coins safe and stake them at the same time |
{% include particl-desktop.html %}


Gateway
BOT
24-Dec-18 04:12 AM
[dscrdvrsc] <uchirosan> you keep saying small number of people as if the hardware was closed door and not available to everyone. If anything thats a veiled attempt to prop up your centralization statements. There was no threat there, you're a dev; you made the changes and are responsible for whatever comes of it. To try and make that seem like a threat is a bit childish
[dscrdvrsc] <miketout> it was
(edited)
[dscrdvrsc] <miketout> the algo is still not named
[dscrdvrsc] <uchirosan> what does it being named do to you?
[dscrdvrsc] <uchirosan> are you able to go and buy the hardware right now if you want to?
[dscrdvrsc] <Cruz> @uchirosan It sounds like you said what you wanted to. Now you are carrying on. He didn't say that like it was a threat.
[dscrdvrsc] <miketout> only existing purchasers of the F1 could even know what it was, while many in the community would have purchased if it was open. not a smart decision at all IMO, but that was their decision.
[dscrdvrsc] <miketout> no one came here to tell us about it. all secret
[dscrdvrsc] <uchirosan> i'm not saying that hiding the bitstreams is the best course of action
[dscrdvrsc] <uchirosan> i dont think anyone in the fpga space wants that long term
[dscrdvrsc] <miketout> because the people who did it thought they could more easily sell secret miners that were NOT available easily to everyone than if everyone knew. that was the point
[dscrdvrsc] <uchirosan> mining is a competitive space as i'm sure you know
[dscrdvrsc] <miketout> and it will be again
[dscrdvrsc] <uchirosan> groups will alot of money have and will always have an advantage
[dscrdvrsc] <uchirosan> privacy of coin names is to help protect against larger entities stealing bitstreams
[dscrdvrsc] <uchirosan> almost all bitstream devs are working on teh same algo's
[dscrdvrsc] <uchirosan> across groups and companies
[dscrdvrsc] <miketout> open and available technology is great. when we see secret tech being used, we will respond
[dscrdvrsc] <uchirosan> the algo was secret, not the tech
[dscrdvrsc] <uchirosan> please be clear on that
[dscrdvrsc] <miketout> now, everyone gets a fresh chance to try again the right way
[dscrdvrsc] <uchirosan> ignorance of the tech doesnt make it secret
[dscrdvrsc] <miketout> implementation of the algo is tech
[dscrdvrsc] <miketout> just as is the new implementation
[dscrdvrsc] <uchirosan> f1 team is the only ones that even looked at verus for whatever reason
[dscrdvrsc] <uchirosan> not sure what their reasoning was on choosing your algo
[dscrdvrsc] <uchirosan> but they did
[dscrdvrsc] <uchirosan> we've had long discussions about the idea of secret algo'
[dscrdvrsc] <uchirosan> and there's conflicting ideas on both sides
[dscrdvrsc] <miketout> and we tried to work with them. maybe we still will, but the secret mining was not ok with our community, and I invented the new algo for the community
[dscrdvrsc] <uchirosan> you guys asked for their code didnt you?
[dscrdvrsc] <uchirosan> just so i understand, its your position that all technology types should be relatively equal in performance?
[dscrdvrsc] <Cruz> What other project would have an FPGA bounty, as large as this one? Hell, what other project would even offer a bounty?
[dscrdvrsc] <uchirosan> the bounty isn't there to help fpga's its to see what fpga's can do and to make adjustments to the algo if necessary
[dscrdvrsc] <uchirosan> don't mistake the reasoning
[dscrdvrsc] <miketout> that's not exactly true. i wrote what is the community's general position in the announcement. it's more a matter of not centralizing by doing exactly what was done. if everyone knows about and can get FPGAs, great, but we are going to work to make various computing hardware useful for mining
[dscrdvrsc] <miketout> we are not doing anything covertly
[dscrdvrsc] <miketout> the bounty is honest
[dscrdvrsc] <Cruz> It is.
[dscrdvrsc] <miketout> it is to prevent secrecy
[dscrdvrsc] <uchirosan> the bounty as stated is to see if someone makes a fpga bitstream that is 10 times faster
[dscrdvrsc] <uchirosan> then what happens?
[dscrdvrsc] <uchirosan> ther algo is adjusted to bring it down closer to gpu/cpu?
[dscrdvrsc] <miketout> there will be more than one because to get the bounty, it should be open
[dscrdvrsc] <uchirosan> thats not what i'm asking
[dscrdvrsc] <uchirosan> what happens if the performance is greater than 1.5x
[dscrdvrsc] <uchirosan> say 10 or 20x
[dscrdvrsc] <miketout> my initial statements to the community was a target of < 5x. we will see what it gets
[dscrdvrsc] <miketout> we have no interest in preventing FPGAs from having a role in the community.
[dscrdvrsc] <uchirosan> so your saying a $2500-4k device should be <5x a 300 device?
[dscrdvrsc] <miketout> price/performance
[dscrdvrsc] <miketout> i will be interested to see if anyone can get 5x
[dscrdvrsc] <uchirosan> price/performance optimizations is exactly what crypto hardware is all about
[dscrdvrsc] <miketout> to you
[dscrdvrsc] <uchirosan> having 20x performance of a 1080ti at 30% of the power use t hat anyone can buy is a good thing
[dscrdvrsc] <uchirosan> there's no hoarding of hardware
[dscrdvrsc] <miketout> i believe it is actually all a proxy for decentralization
[dscrdvrsc] <miketout> which for many might just be words, but we are not just spouting words.
[dscrdvrsc] <uchirosan> how long do you anticipate gpu miner being available after fork?
[dscrdvrsc] <miketout> it actually doesn't matter to me if that happens on any particular hardware
[dscrdvrsc] <miketout> that is not up to me, as I'm doing other things. i am helping at least one GPU dev who is making great progress, and there are others. I don't want to speak for him, but it's conceivable he will be ready by the fork. It may surprise you, but I am also helping at least one FPGA dev to understand as well. so far, it seems most people who have looked at the algo may not understand it fully yet.
[dscrdvrsc] <miketout> but the people who have come to ask for help or those who are working on behalf of the community certainly are welcome to do so
[dscrdvrsc] <uchirosan> other than the f1 team none of the other devs i know for other fpga's were working on verus algo
[dscrdvrsc] <miketout> i guess you don't know them all
[dscrdvrsc] <uchirosan> i'm just referring to the ones I know active on the bcu side
[dscrdvrsc] <uchirosan> there are lots of devs out there
[dscrdvrsc] <uchirosan> though the amount working on meaningful fpga implementations for non-secret use is pretty small
[dscrdvrsc] <uchirosan> most will go to large farms that we never hear about
[dscrdvrsc] <Cruz> @uchirosan Mike is actually very good for crypto, in general. You will find that he is very knowledgeable and very helpful. I think it's better to have a real, genuine conversation with him than go back and forth with others here
[dscrdvrsc] <uchirosan> right now the fpga community is at the forefront of a new tech, at least in the general sense since fpga's have been around for a long time even in crypto


+ Project Descriptions #04
Understanding networks in the IT field is like getting a license to ride a car.
By understanding how networks are organized, how packets are routed, how routes are determined, and the
various protocols, you can understand the overall behavior of the Web. Therefore, i constructed 5 routing
topologies using multiple protocols.
- Project : Network Topology for ROUTING
- Completed Date : December 2020
- Architect : Taehee Jo
- Working day : 20+
- Used Programm : GNS3, SecureCRT


Your List of Circles
{{ errorMessage }}
{{ infoMessage }}
Create
Name
Description
Is moderator?
Actions
{{ circle.name }}
{{ circle.description }}
Edit
Remove
You aren't in any circles, yet


I love learning about everything related to Math and Science.
I enjoy working on different project that challege my current skills.
Follow me on Twitter


The Footballer or Mathematician Challenge 2
Many footballers and mathematicians share strikingly similar names!
Still not convinced?  This is the second installment.
Results
This is the end of the quiz.
You have answered 0 out of 12 questions and 0 / 0 (0%) of your answers are correct.
Thanks for Playing!
If you haven't already yet, you should try out the other quizzes located in the menu bar or nav bar.


SIDES Reusable Modules
Recommendation, 2007 April 15
Editors:
Kim Bartkus, HR-XML Consortium
Contributors:
Gail Bubsey (Kelly Services ), Kim Bartkus (HR-XML Consortium), Barbara Johnson (Adecco NA), Tara Ryan (Adecco), Kazuko Sugamura (Manpower Japan), Takahiro Fujiwara (EAST Co., Ltd.), Magali Munoz (Manpower France), Bruno Alcotte (Manpower France), Rémy Bailly (Randstad), Yves Berdah (VidiorBis), Serguei Dounaevetski (Manpower France), Patrice Aranega (Adecco France)
Copyright © 2007 HR-XML Consortium, Inc.
Abstract
The HR-XML SIDES Workgroup has produced 7 major schemas and several reusable modules to allow for transmission of Staffing Industry information between trading partners. This document describes the Staffing Order schema, its expected usage, and the business processes meant to be supported.
Table of Contents
3 Customer Reporting Requirements. 5
8 Implementation Considerations
9 Appendix A - Document Version History
10 Appendix B – Related Documents
Changes were made to the base SIDES specification based on feedback from the European and Japanese Chapters. If available, localized items are documented in section 4 Implementation Considerations or in individual country documentation. Refer to Appendix A - Document Version History for details.
Several reusable modules are used to exchange details within the framework of SIDES. This document describes the purpose and details of each of the six reusable modules:
The six reusable modules will be divided into separate chapters, with an overview, diagram, and definitions for each chapter.
The ContactInfo schema contains two data types to allow for contacting an individual or an organization: ContactInfoType and EntityContactInfoType. The ContactInfoType incorporates the PersonName and ContactMethod. Whereas, the EntityContactInfo also includes an EntityName to allow for organization, company, department, etc. The ContactMethod schema provides for a variety of contact methods such as telephone, fax, e-mail, web, and postal address.
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/ |
- ContactInfoType - (1/1) |
Contains information to contact a
person or entity. |
|
/ ContactInfo/ |
- ContactMethodType - S (1/*) |
Defines the methods to contact a
person or organizations. |
|
/ ContactInfo/ |
- EntityIdType - S (0/1) |
Unique identifier for the contact. |
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/ |
- EntityContactInfoType - (1/1) |
Container for entity contact information. |
|
/ EntityContactInfo/ |
- xsd:string - S (1/1) |
Name of entity that is contacted. This would typically be the organization. |
|
/ EntityContactInfo/ |
- ContactMethodType - S (1/*) |
Defines the methods to contact a
person or organizations. |
Staffing customers require specialized reporting and data tracking. For example, it is very common for customers to require purchase order numbers, supervisor names, or department numbers, etc. to appear on reports, invoicing, documents or correspondence. A list common customer requirements was developed to accommodate this requirement. Many of these fields may be used differently by each staffing customer and the list may not satisfy every situation. Research indicates that the CustomerReportingRequirements Module attributes satisfy 80% of common reporting situations.
In the list of data fields you will find "CostCenterCode" and "LocationCode". The specific use of these two codes is up to the staffing customer. One customer may require their cost center data to appear on a report and another customer may require their location code to appear on a report. Other staffing customers may have both fields. The analysis and research showed there were enough occurrences of each field to justify the existence of both.
It is assumed that there will be exceptions and extensions to the list and some customers will require additional data elements. Accordingly, an unbounded named value pair is provided for reporting requirements that do not fit into the predefined fields.
Why not just use generic additional data elements?
The question may be asked as to why a generic 'additional data' element with enumerated types is not used rather than a predefined list? The specification could be implemented this way, but this method would not provide a ‘mapable’ data tag for items such as PO#, Cost Center, Manager Name, etc. within the HR-XML SIDES Standard itself. Without the specific tags, suppliers are forced to build extensions to the schemas to accommodate this additional data. Since the data is intended to be reused within several of the SIDES schemas, the pre-defined tags will ensure consistency between schemas. The CustomerReportingRequirements Module is referenced within StaffingCustomer, Order, Position, Assignment, Extended Timecard and Invoice schemas.
Department Code versus Department Name
Within the list of CustomerReportingRequired fields, there is a difference between DepartmentCode and DepartmentName, LocationCode and LocationName, etc. These fields are independent and mutually exclusive. These fields should not be confused with lookup tables or named value pairs. One staffing customer may want to report on codes, whereas another customer may want to track descriptive names or text.
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/ |
- CustomerReportingRequirementsType - (1/1) ManagerName
- xsd:string - S
(0/1) |
List of customer-wide reporting field requirements. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
Manager
name. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
Work assignment supervisor's name, used for reporting. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
The name of the person to contact. |
|
/ CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
Purchase
order number. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
A
department code. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
A
department name. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
Location
code. |
|
/ CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
Location
name. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
Cost
center code. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
Cost
center name. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
Staffing
customer job code. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
Job
description. |
|
/ CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
An
account code or identifier. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
A
project code. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
External
order number. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
External
request number. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
A person, company or other organization. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
Customer
organizational designation. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
Work shift as it pertains to a particular work engagement . |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
Reference
number. |
|
/
CustomerReportingRequirements/ |
xsd:extension base: xsd:string |
Any other customer required item. |
|
/
CustomerReportingRequirements/ AdditionalRequirement/ |
- xsd:string - |
Title or name used by the customer for the additional reporting requirement. |
|
/
CustomerReportingRequirements/ |
- xsd:string - S (0/1) |
Purchase
Order Line Item Number associated with the reporting requirement. |
The rates module is a flexible schema that allows for the transmission of a wide variety of pay, bill and expense rate structures. It provides for multiple instances of rates for a single assignment and can associate a shift with each rate. The Rates module is also used in the StaffingOrder schema to capture a customer-specified bill rate range, and in the HumanResource to capture a specific charge rate for an individual in relation to a particular position.
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/ |
- RatesType - (1/1) |
Container for rate information. |
|
/ Rates/ |
- EntityIdType - S (0/1) |
Reference to an external rate, or collection of contractual rates. |
|
/ Rates/ |
xsd:extension base: xsd:decimal |
The monetary value of the
associated item. |
|
/ Rates/ Amount/ |
- AmountPeriodType - |
The time interval or other increment in which the rate is charged or paid. May extend to provide for bonus or commission payments. |
|
/ Rates/ Amount/ |
xsd:restriction base: xsd:string |
A three-letter code identifying
the currency of a monetary amount. |
|
/ Rates/ |
- xsd:string - S (1/1) |
Classification or designation for
the rate. |
|
/ Rates/ |
- EntityIdType - S (0/1) |
Shift identifier with which the rate is associated. |
|
/ Rates/ |
xsd:extension base: xsd:decimal |
A multiplier to be applied to the
related amount, rate, or variable. |
|
/ Rates/ Multiplier/ |
- xsd:boolean - |
Flag to indicate if the multiplier provided is a percentage of the original number. |
|
/ Rates/ |
- AnyDateTimeNaType - S (1/1) |
Contains the (inclusive) date,
period, or interval the event becomes active or begins. |
|
/ Rates/ |
- AnyDateTimeNkType - S (0/1) |
Contains the (inclusive) date,
period, or interval the event becomes inactive or ends. |
|
/ Rates/ |
- xsd:string - S (0/1) |
Describes the contextual
information relating to a specific element. |
|
/ Rates/ |
- EntityIdType - S (0/1) |
A unique identifier for an individual agreed upon rate. |
|
/ Rates/ |
- EntityIdType - S (0/1) |
Identifier allowing customer rates to be grouped for reporting purposes. |
|
/ Rates/ |
xsd:extension base: xsd:decimal |
A multiplier specifically used to calculate the invoice amount using the paid amount. |
|
/ Rates/ BillingMultiplier/ |
- xsd:boolean - |
Flag to indicate if the multiplier provided is a percentage of the original number. |
|
/ Rates/ |
- TimeRoundingRuleType - S (0/*) |
Contains rounding requirements to round the time worked. |
|
Global
types |
ContentModel* |
Definition |
|
/ |
summaryCycle - FrequencyType
- |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ [TimeRoundingRuleType] / |
- FrequencyType - |
Describes the cycle of time worked for rounding purposes. |
|
/ [TimeRoundingRuleType]/ |
xsd:extension base: xsd:decimal |
A container used to report the duration and type of a work for a specified time period. |
|
/ [TimeRoundingRuleType]/
TimeInterval/ |
- RoundingRuleEnumType - |
The methodology used for
rounding. |
|
/ [TimeRoundingRuleType]/
TimeInterval/ |
- xsd:string - |
Time increment in which the event
is measured. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: RoundDown, RoundHalfDown, RoundUp, RoundHalfUp, RoundHalfEven, RoundCeiling, RoundFloor |
Globally scoped data type. See element or attribute declaration for definition. |
This reusable module allows staffing suppliers to report basic screening information pertaining to a staffing resource.
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/ |
- ResourceScreeningType
- (1/1) |
Container for screening or testing data about the candidate. |
|
/ [ResourceScreeningType] / |
- StaffingScreeningType - |
Type of screening required and reported on. |
|
/ ResourceScreening/ |
- xsd:string - S (1/1) |
Result of the screening report. This is generally limited to noting if the requirement was met or not met. |
|
/ ResourceScreening/ |
- xsd:string - S (0/1) |
Comments regarding the report. |
|
Global
types |
ContentModel* |
Definition |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: abuse, address, awards, credit, criminal, drug, earnings, education, employment, license, name, phone, reference, workcomp |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
- [Union]: KnownScreeningType,xsd:string |
Globally scoped data type. See element or attribute declaration for definition. |
The StaffingShift schema provides a mechanism for exchanging information on shifts or specific working hours between trading partners and within internal applications. Staffing suppliers require shift information to describe position-specific requirements and rate related assignment information within an order.
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/ |
- StaffingShiftType
- (1/1) |
A mechanism for exchanging information on shifts or specific working hours. |
|
/ [StaffingShiftType]
/ |
xsd:restriction base: xsd:string [Enumerations]: monthly, weekly, daily, 1, 2, 3, 4, 5, 6, 7, event |
The
period the shift occurs. Annotation: Numeric values conform to: ISO 8601
2nd Edition; ISO8601:2000(E); pub 2000-12-15, Data elements and interchange
formats, Information interchange, Representation of dates and times,
http://www.iso.ch/cate/d26780.html/ 1 = Monday, 2 = Tuesday, 3 = Wednesday, 4
= Thursday, 5 = Friday, 6 = Saturday, 7 = Sunday |
|
/ StaffingShift/ |
- EntityIdType - S (1/1) |
A unique identifier used to reference the entity. The Id is associated with the higher level element. |
|
/ StaffingShift/ |
- xsd:string - S (0/1) |
A descriptive identifier within
the given context. |
|
/ StaffingShift/ |
- xsd:decimal - S (0/1) |
The number of hours specified for an event or work period. |
|
/ StaffingShift/ |
- LocalTimeNkNaType - S (0/1) |
The time the interval or event started. |
|
/ StaffingShift/ |
- LocalTimeNkNaType - S (0/1) |
The time the interval or event ended. |
|
/ StaffingShift/ |
- xsd:string - S (0/1) |
Specific type of work hours. |
|
/ StaffingShift/ |
- xsd:string - S (0/1) |
Allows for textual comments. |
|
/ StaffingShift/ |
- EntityIdType - S (0/1) |
Allows a reference to an external staffing shift, or collection of contractual staffing shifts. |
This module defines the type of contact information consistent across the Assignment, and StaffingAction modules. To ensure this consistency, a value list (enumerations) was created for use in those two modules.
|
Global
types |
ContentModel* |
Definition ** |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: placed by, placed on behalf of, confirm to, authorized by, interviewer, supervisor, time approver, submitted by, created by, sent to, first day contact, customer complaints, supplier manager, supplier complaints, deputy time approver |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
- [Union]: KnownContactType,xsd:string |
Globally scoped data type. See element or attribute declaration for definition. |
Human resources data, by its very nature, is personal data. The laws of many jurisdictions as well as codes of fair information practice require organizations to handle personal data in a way that protects individuals from loss of privacy.
The data exchange specifications developed by the HR-XML Consortium are designed to be useful across many jurisdictions and within a variety of business contexts. It is not feasible for the HR-XML Consortium to develop specific privacy guidance for every jurisdiction or business context in which the Consortium's specifications might be implemented. When implementing data exchanges using the HR-XML Consortium's data definitions (or, for that matter, using any other type of data exchange mechanism), organizations are advised to examine the privacy protections that may be required under applicable law and codes of fair information practice.
For information on protecting personal data, general references include: European Union Data Protection Directive (95/46/EC); the Association Computing Machinery Code of Ethics (1992); Canadian Standards Association Model Code for the Protection of Personal Information (1995 – PIPEDA); and U.S.-EU Safe Harbor Principles and FAQs (2000).
|
Date |
Description |
|
2004-Mar-03 |
Initial Draft |
|
2004-Mar-29 |
Updated tables, added info to overview/scope sections. |
|
2004-Apr-07 |
Added reference examples. |
|
2004-May-06 |
Changed percentage to percentIndicator |
|
2004-Jun-08 |
Changed Contact Method to multiple occurrence. Added xml:lang to root of Rates, ResourceScreening, and StaffingShift. |
|
2004-Aug-02 |
Approved by membership. |
|
2006-Feb-28 |
Approved by Consortium |
|
2006-July-08 |
Added ContactId to ContactInfo schema. Added TimeWorkedRounding to Rates schema. Added 'first day contact', ' customer complaints', 'supplier manager', 'supplier complaints', and 'deputy time approver' enumerations to ContactType within StaffingContactType schema. Added 'event' enumeration to shiftPeriod within StaffingShift schema. |
|
2007-Apr-15 |
Approved by Consortium. |


When using the Externalizable interface, an externalizable object must implement a writeExternal method to save the state of the object and a readExternal method to restore the state of the object. The externalizable object must also coordinate with its supertype to save and restore its state.
This example demonstrates how an object saves and restores the state of its nonexternalizable supertype. When the supertype of an externalizable object is not externalizable, the subclass object must explicitly save and restore the state of the fields of the superclass in its own writeExternal and readExternal methods.


Uganda’s Namatovu is second runner up at Miss International 2019
by Jacky AchanMiss International is one of the top four most popular pageants in the world.
BEAUTY PAGEANT
TOKYO-Uganda’s Evelyne Namatovu has been crowned 2nd runner up in Miss International pageant held at the Tokyo Dome City Hall in Japan early today.
The crown was handed to Sireethorn Leearamwat. She is Miss International 2019 and, becomes the first-ever winner of Miss International from Thailand.
Mexico's Andrea Toscano was 1st runner-up, followed by Uganda's Evelyn Namatovu as 2nd runner up.
Colombia's Maria Alejandra Vengoechea and United Kingdom's Harriotte Lane finished as 3rd and 4th runners up respectively.
The 23- year-old Namatovu a student at Makerere University Business School awaiting graduation in Bachelors of Entrepreneurship and Business Management became the second woman in history to represent Uganda in Miss International.
Uganda made its debut in Miss International in 2009 with the five-foot-nine and a half Pierra Akwero 22-years-old at the time, flying the national flag at the 49th Miss International pageant, held in Chengdu Sichuan China.
What makes Miss International different from other global pageants?
Miss International is one of the top four most popular pageants in the world.
Unlike Miss World or Miss Universe, that have mainly focused on health projects especially Miss World, Miss International's primary focus is on establishing international relations and cultural exchanges among nations.
Miss International focuses on business, tourism, peace and international relations. It begun in 1960, in Tokyo Japan and has consistently been held there ever since by the Intercultural Association of Japan.
The pageant emphasizes on building international relationships, promoting culture and lasting peace through activities that bring all the nationalities together, Miss International Uganda National Director Aketch explained.
The goal for Miss International is to merge entertainment, fashion and design, architecture, arts and crafts by bringing out untapped talent among the youth within the country.
Through extensive Miss international events, young people in the arts Industry also get to showcase to their talent to world.
For Uganda there is more positive visibility of our creative industry which has potential to bring in various investment, job opportunities and tourism, Aketch says.
Today in Tokyo Namatovu was only 2nd runners up but despite narrowly missing on the crown, Namatovu was handed the best swimsuit crown in Japan.
Miss Venezuela was awarded for the Best Evening Gown while Miss Guadeloupe was Miss Photogenic. Miss Vietnam Nguyễn Tường San was awarded for the Best National Costume.
Other winners included
Miss International Africa Liberia – Naomi Nucia Glay
Miss International America Peru – María José Barbis
Miss International Asia Thailand – Sireethorn Leearamwat
Miss International Europe Netherlands – Elize Joanne de Hong
Miss International Oceania Hawaii – Eunice Raquel Basco
Miss International Top 8
1. Mexico
2. Philippines
3. Colombia
4. Uganda
5. Indonesia
6. Vietnam
7. Thailand
8. United Kingdom
Miss International 2019 Top 15
1. Venezuela – Melissa Jiménez
2. Thailand – Sireethorn Leearamwat
3. United Kingdom – Harriotte Lane
4. Hong Kong – Kaye Cheung
5. Uganda – Evelyn Namatovu
6. Netherlands – Elize Joanne de Hong
7. Vietnam – Nguyễn Tường San
8. Finland – Jutta Kyllönen
9. Puerto Rico – Ivana Carolina Irizarry
10. Belarus – Maria Perviy
11. Colombia – Alejandra Vengoechea
12. Philippines – Bea Patricia Magtanong
13. Mexico – Andrea Toscano
14. Sri Lanka – Pawani Vithanage
15. Indonesia – Jolene Marie Rotinsulu


|
BubbleProfiler
0.3.0
by Peter Athron, Csaba Balazs, Michael Bardsley, Andrew Fowlie, Dylan Harries & Graham White
|
Classes | |
| class | Settings |
Functions | |
| def | make_struct (settings) |
| def | action (E, alpha, dim=3, kwargs) |
Variables | |
| PATH = os.path.dirname(os.path.abspath(__file__)) | |
| string | LIB_NAME = '{}/../lib/libbubbler.so' |
| lib = ctypes.CDLL(LIB_NAME) | |
| c_action = lib.action | |
| argtypes | |
| restype | |
| default = Settings() | |
| shoot_bisect_bits | |
| action_arrived_rel | |
| shoot_ode_abs | |
| shoot_ode_rel | |
| action_ode_abs | |
| action_ode_rel | |
| drho_frac | |
| evolve_change_rel | |
| evolve_rho_min | |
| bisect_lambda_max | |
| iter_max | |
| periods_max | |
| f_y_max | |
| f_y_min | |
| int | E = 1 |
| float | alpha = 0.65 |
Solve one-dimensional bounce problem with shooting method ========================================================== export LD_PRELOAD=/usr/lib/libginac.so.2.1.0:/usr/lib/x86_64-linux-gnu/libboost_log.so.1.61.0:/usr/lib/x86_64-linux-gnu/libnlopt.so.0.8.1:/usr/lib/x86_64-linux-gnu/libalglib.so.3.8.0
| def pyshooting.action | ( | E, | |
| alpha, | |||
dim = 3 , |
|||
| kwargs | |||
| ) |
Wrapper for C function that calculates action.
Definition at line 71 of file pyshooting.py.
References c_action, and make_struct().
| def pyshooting.make_struct | ( | settings | ) |
Populate struct for Shooting::default from a dictionary.
Definition at line 60 of file pyshooting.py.
Referenced by action().
| pyshooting.action_arrived_rel |
Definition at line 45 of file pyshooting.py.
| pyshooting.action_ode_abs |
Definition at line 48 of file pyshooting.py.
| pyshooting.action_ode_rel |
Definition at line 49 of file pyshooting.py.
| float pyshooting.alpha = 0.65 |
Definition at line 81 of file pyshooting.py.
| pyshooting.argtypes |
Definition at line 18 of file pyshooting.py.
| pyshooting.bisect_lambda_max |
Definition at line 53 of file pyshooting.py.
| pyshooting.c_action = lib.action |
Definition at line 17 of file pyshooting.py.
Referenced by action().
| pyshooting.default = Settings() |
Definition at line 43 of file pyshooting.py.
| pyshooting.drho_frac |
Definition at line 50 of file pyshooting.py.
| int pyshooting.E = 1 |
Definition at line 80 of file pyshooting.py.
Referenced by action(), and configure_file().
| pyshooting.evolve_change_rel |
Definition at line 51 of file pyshooting.py.
| pyshooting.evolve_rho_min |
Definition at line 52 of file pyshooting.py.
| pyshooting.f_y_max |
Definition at line 56 of file pyshooting.py.
| pyshooting.f_y_min |
Definition at line 57 of file pyshooting.py.
| pyshooting.iter_max |
Definition at line 54 of file pyshooting.py.
| pyshooting.lib = ctypes.CDLL(LIB_NAME) |
Definition at line 16 of file pyshooting.py.
| string pyshooting.LIB_NAME = '{}/../lib/libbubbler.so' |
Definition at line 14 of file pyshooting.py.
| pyshooting.PATH = os.path.dirname(os.path.abspath(__file__)) |
Definition at line 13 of file pyshooting.py.
| pyshooting.periods_max |
Definition at line 55 of file pyshooting.py.
| pyshooting.restype |
Definition at line 19 of file pyshooting.py.
| pyshooting.shoot_bisect_bits |
Definition at line 44 of file pyshooting.py.
| pyshooting.shoot_ode_abs |
Definition at line 46 of file pyshooting.py.
| pyshooting.shoot_ode_rel |
Definition at line 47 of file pyshooting.py.


history(2 second intervals):
A warning will show then an image differs greatly from the last. The warning will stay for 30 seconds.


Interview With Hnefatafl Books Author Damian Walker
This is a part of an ongoing interview series with book authors who write about our favorite types of games. Damian Walker is the author of not one but two books on hnefatafl. Both An Introduction to Hneftafl and Reconstructing Hnefatafl introduced me to this Norse game and I’ve been a huge fan ever since. I am delighted to share this interview with Damian everyone and hope you enjoy it too.
Can you tell us a little about yourself?
I’m a web developer living in Yorkshire, England. I’m from these parts, although I’ve also lived in Northwest England and, when I was very young, in New Jersey.
How did you first learn about hnefatafl?
It was in a book I got from the library back in 2002: Jack Botermans’ “The World of Games”. I was between jobs at the time, and I was very much attracted to these games that could be easily made with things lying about the house.
What drew you in about it compared to other ancient board games?
The attractive rotational symmetry drew my attention, as well as the asymmetrical division of the pieces between the two teams. Though it wasn’t the only game from that book that attracted my attention. What drew me further in was the air of mystery, the fact that at the time we didn’t really know how it was played.
What inspired you to write not just one book, but two books about hnefatafl?
The two books are really aimed at different readerships. The first one (Reconstructing Hnefatafl) is the more serious one of the two, aimed at re-enactors and other people who want to bring the game to modern audiences; it goes into a lot of detail about historical evidence and game balance in order to justify its reconstructions. The newer book (An Introduction to Hnefatafl) is more of a light read for people who just want to find out a bit more about the game and to play it.
Have you ever considered combining both books into one?
Yes and no. I’d actually thought about writing a larger book on the game, having gathered enough research to fill one. But my day job can be quite demanding of my energy, so that project has been pushed back.
How long did it take to write the books?
It’s difficult to tell how long Reconstructing Hnefatafl took, as it was done in a few stages across a number of years. It drew on a never-published book I’d been working on since about 2004, so it includes about ten years of research. An Introduction to Hnefatafl was originally a 20-page booklet, which took me a week to put together from the same research. I used to sell that from my web site. I then reworked it into the book as it exists now, which probably took me a few months.
How did you feel when you first published it?
I was very pleased with Reconstructing Hnefatafl. It was originally going to be a free PDF. I got a lot of support from David Parlett, author of the Oxford Book of Board Games, and through him from Irving Finkel of the British Museum. They suggested I present it as a paper at the Board Games Colloquium that’s held each year. That never happened, as I couldn’t afford to travel, but I was glad to share it instead as a printed book. I was quite proud of it as it was the first book on the game that made it in print. An Introduction to Hnefatafl was also quite fun, although since it was the second book I published, the experience had fewer surprises for me.
What was the hardest chapters to write?
I honestly can’t remember, although it’s probably the Alea Evangelii chapter of Reconstructing Hnefatafl. It was nigh on impossible to get anyone to play that thing with me, especially as the rules were experimental. It was only some years afterwards that the game got extensively playtested. That showed that my reconstruction is far from balanced, and a lot more research on that game is needed.
Are there plans for more books or updates to the current ones?
At some point, I should revisit Reconstructing Hnefatafl, as the research is falling out of date - particularly on things like game balance, where there are many more willing play-testers now than there were when I wrote it. There’s that larger book on the game that I mentioned, which I’m not actively working on but I haven’t abandoned either. I’d also like to write more books following the format of “A Book of Historic Board Games”.
Alea Evangelii is a tafl game that is played on a 19x19 grid. Do you think there is a connection here to the game of Go?
I don’t think there’s a connection. In fact there are three games I know of played on a similar looking board. There’s alea evangelii, go, and an unknown game which appears to be a large form of ludus latrunculorum. I think the board size in all these cases is just coincidence.
You also wrote, A Book of Historic Board Games. Can you talk a bit about the journey and inspiration behind this book?
This is my favourite of the three books I’ve written, although it’s also the least successful. I’m interested in ancient board games in general, and I wanted to write something that drew on my research beyond hnefatafl. There are already many books that cover large numbers of games, so I decided to select just twelve and cover them in a reasonable amount of detail. It was inspired more by books like David Pritchard’s Brain Games than by the books that attempt to cover as many games as possible. This was the most fun to write, and led me into some very interesting research. This kind of project is much easier now than it was even ten years ago; the vast number of digitised documents means that one can go back to primary sources without having to leave the house.
Many consider you an authoritative source on hnefatafl. How does that make you feel?
It seems like quite a responsibility for someone who hasn’t really been that active over the past few years! I’m glad that interest in the game has increased as time has drawn on, though, and I hope to have the time in future to bring myself up to date with new developments.
How many hnefatafl sets do you own?
I think I might have about twenty by now. I spent quite a long time looking for attractive sets on eBay, and I also kept one of nearly every design of board that I made myself.
Do you have a favorite set?
It seems a bit conceited, but I do like the 9x9 set that I used to make, with the walnut veneer edge. Of the more well-known ones that people might recognise, I really like the wooden one that was marketed by York Archaeological Trust back in 1980, which you still see surfacing on eBay from time to time. It comes with a nice set of rules, too.
What is your favorite historic hnefatafl variant?
Tablut is my favourite, as it’s the one we can be most certain about. I also think the 9x9 size makes for a good game.
What is your favorite modern variant?
I very much like Sea Battle Tafl. It’s very elegant and easy to teach. Since I’m oriented more towards historic games, I like the fact that it manages balance without introducing too many imaginative new ideas.
How often do you play now?
Sadly I very rarely get to play now. I was never a strong player, but I’m very out of practice now!
Have you ever experimented with creating your own tafl variation?
No, I tend to prefer to uncover historical games than to create new ones. I have had a lot of fun pasting themes onto existing hnefatafl rules, though. I’m particularly fond of the Christmas one, with Santa and his eight elves trying to set off from the North Pole before sixteen naughty children ambush them and steal the presents!
Thanks Damian for your time. What is the best way for people to contact your or get in touch with you if they have more questions or just want to chat?
I’m quite active on Twitter nowadays, especially on my personal account (@cyningstan) so people are welcome to contact me there.


Post edited 3 x times, last by
Topicstarter
This plugin disables the dropdowns in the main menu.
Based on this request:
http://getbblog.com/board/topic/108614/1/Ability-to-disable-the-Soldier-Multiplayer-dropdowns
Changelog
1.1 - future dropdowns should be disabled automatically
1.0 - initial version
You can install this plugin from the plugin gallery:
http://getbblog.com/plugin/138648/Disable-Dropdowns
Github repository:
https://github.com/dpeukert/bblog


This is a site made in order to find someones Akan name based on the Akan people of Ghana. According to the Akan people when babies are born,they are given names according the day they were born.
The website uses the formula Day of the week (d) = ( ( (CC/4) -2*CC-1) + ((5*YY/4) ) + ((26*(MM+1)/10)) + DD ) mod 7 where;


A visualisation of open data in Leaflet.js and Mapbox.js
Geelong Regional Libraries Corporation open data visualisation by Kathy Reid is licensed under a Creative Commons Attribution 4.0 International License.
Based on a work at https://data.gov.au/dataset/grlc-library-collection-by-branch-city-of-greater-geelong.


Honey Pot teaches users the dangers of using public-access computers that often are honeypots that lure unwary users when they input their usernames and passwords. The game simulates a scenario where a player is placed in the shoes of a hacker, and is given a behind the scenes view of how various softwares tools like a key-logger is used to gain illegal access to sensitive data from public computers
Back Next


Build Something
Awesome
Today
A simple setup to get stared with your website
Check Out on Github
I have used
MD-Bootstrap UI
based on bootstrap-4 provided by
MDB Team.
click here
to check out their cool stuff.
made with
in vscode.
Primary
Secondary
Success
Danger
Warning
Info
Light
Dark


This is a widget to look at a large zoomed image with touch events (although I've simulated it with mouseevents). The idea is that given some thumbnails / image preview, you can insert a button that the user can touch/drag around to view the zoomed image. It seems in the wild we also need a modifier rule, which tells us how to generate the src of the big image so that its really giant.
Note: We assume listeners on the thumbnails to update the main image are already in place. If this is not the case, we can make a skeleton image gallery widget.

More examples of zoom previews can be found here.


"CRUSHED by science!!!"
"CRUSHED by science!!!"
Collect 80 fragments of Titanium Wrench from
Chapter 13 - Divided Opinion (Heroic Difficulty)
Complete 10 times with Dr. Zeno in your party
(Extreme+ Difficulty)
Complete the stage with Dr. Zeno in your party
Requirement: Dr. Zeno must kill Baltor (Heroic Difficulty)
| Item Stats + Max Enchant | ||
|---|---|---|
| Max Health | 1000 | +903 |
| Magic Attack | 165 | +147 |
| Magic Pierce | 120 | +105 |
| Forge Bonus Stats | |||
|---|---|---|---|
| M. Attack | ≥ 40 | Max Health | +400 |
| P. Armor | ≥ 100 | M. Attack | +70 |
| M. Armor | ≥ 200 | P. Attack | +150 |


Transitions
- Opacity, Linear (default)
- From Right, Linear
- From Right, easeOutQuad
- From Right, swingTo
- From Center, easeOutBack
- From Top and Opacity
- From Top, bounce
- Width, swingTo
- From Bottom, bouncePast
- Black, easeInOutQuad
- Flash White, easeInQuart
-
Custom transition