/**
* Color of text in the component, including the component label.
*
* @default 0x0B333C
*/
[Style(name="color", type="uint", format="Color", inherit="yes")]
/**
* Color of text in the component if it is disabled.
*
* @default 0xAAB3B3
*/
[Style(name="disabledColor", type="uint", format="Color", inherit="yes")]
/**
* Sets the antiAliasType
property of internal TextFields. The possible values are
* "normal"
(flash.text.AntiAliasType.NORMAL
)
* and "advanced"
(flash.text.AntiAliasType.ADVANCED
).
*
*
The default value is "advanced"
, which enables the FlashType renderer if you are using an
* embedded FlashType font. Set to "normal"
to disable the FlashType renderer.
This style has no effect for system fonts.
* *This style applies to all the text in a TextField subcontrol; * you can't apply it to some characters and not others.
* @default "advanced" * * @see flash.text.TextField * @see flash.text.AntiAliasType */ [Style(name="fontAntiAliasType", type="String", enumeration="normal,advanced", inherit="yes")] /** * Name of the font to use. * Unlike in a full CSS implementation, * comma-separated lists are not supported. * You can use any font family name. * If you specify a generic font name, * it is converted to an appropriate device font. * * @default "Verdana" */ [Style(name="fontFamily", type="String", inherit="yes")] /** * Sets thegridFitType
property of internal TextFields that represent text in Flex controls.
* The possible values are "none"
(flash.text.GridFitType.NONE
),
* "pixel"
(flash.text.GridFitType.PIXEL
),
* and "subpixel"
(flash.text.GridFitType.SUBPIXEL
).
*
* This property only applies when you are using an embedded FlashType font
* and the fontAntiAliasType
property
* is set to "advanced"
.
This style has no effect for system fonts.
* *This style applies to all the text in a TextField subcontrol; * you can't apply it to some characters and not others.
* * @default "pixel" * * @see flash.text.TextField * @see flash.text.GridFitType */ [Style(name="fontGridFitType", type="String", enumeration="none,pixel,subpixel", inherit="yes")] /** * Sets thesharpness
property of internal TextFields that represent text in Flex controls.
* This property specifies the sharpness of the glyph edges. The possible values are Numbers
* from -400 through 400.
*
* This property only applies when you are using an embedded FlashType font
* and the fontAntiAliasType
property
* is set to "advanced"
.
This style has no effect for system fonts.
* *This style applies to all the text in a TextField subcontrol; * you can't apply it to some characters and not others.
* * @default 0 * * @see flash.text.TextField */ [Style(name="fontSharpness", type="Number", inherit="yes")] /** * Height of the text, in pixels. * * The default value is 10 for all controls except the ColorPicker control. * For the ColorPicker control, the default value is 11. */ [Style(name="fontSize", type="Number", format="Length", inherit="yes")] /** * Determines whether the text is italic font. * Recognized values are"normal"
and "italic"
.
*
* @default "normal"
*/
[Style(name="fontStyle", type="String", enumeration="normal,italic", inherit="yes")]
/**
* Sets the thickness
property of internal TextFields that represent text in Flex controls.
* This property specifies the thickness of the glyph edges.
* The possible values are Numbers from -200 to 200.
*
* This property only applies when you are using an embedded FlashType font
* and the fontAntiAliasType
property
* is set to "advanced"
.
This style has no effect on system fonts.
* *This style applies to all the text in a TextField subcontrol; * you can't apply it to some characters and not others.
* * @default 0 * * @see flash.text.TextField */ [Style(name="fontThickness", type="Number", inherit="yes")] /** * Determines whether the text is boldface. * Recognized values arenormal
and bold
.
* The default value for Button controls is bold
.
* The default value for all other controls is normal
.
*/
[Style(name="fontWeight", type="String", enumeration="normal,bold", inherit="yes")]
/**
* A Boolean value that indicates whether kerning
* is enabled (true
) or disabled (false
).
* Kerning adjusts the gap between certain character pairs
* to improve readability, and should be used only when necessary,
* such as with headings in large fonts.
* Kerning is supported for embedded FlashType fonts only.
* Certain fonts, such as Verdana, and monospaced fonts,
* such as Courier New, do not support kerning.
*
* @default false
*/
[Style(name="kerning", type="Boolean", inherit="yes")]
/**
* The number of additional pixels to appear between each character.
* A positive value increases the character spacing beyond the normal spacing,
* while a negative value decreases it.
*
* @default 0
*/
[Style(name="letterSpacing", type="Number", inherit="yes")]
/**
* Alignment of text within a container.
* Possible values are "left"
, "right"
,
* or "center"
.
*
* The default value for most components is "left"
.
* For the FormItem component,
* the default value is "right"
.
* For the Button, LinkButton, and AccordionHeader components,
* the default value is "center"
, and
* this property is only recognized when the
* labelPlacement
property is set to "left"
or
* "right"
.
* If labelPlacement
is set to "top"
or
* "bottom"
, the text and any icon are centered.
"none"
and "underline"
.
*
* @default "none"
*/
[Style(name="textDecoration", type="String", enumeration="none,underline", inherit="yes")]
/**
* Offset of first line of text from the left side of the container, in pixels.
*
* @default 0
*/
[Style(name="textIndent", type="Number", format="Length", inherit="yes")]


{% extends "modal_form.html" %} {% block pre_form_content %} Are you sure you wish to cancel this build? {% endblock %}


Feel free to change the settings below.
An example of <streaming-list lang="{{language}}" width="{{size}}" service="{{service}}" game="{{game}}">:
<streaming-list lang="{{language}}" width="{{size}}" service="{{service}}" game="{{game}}">


Warehouse Keeper Pochi:
Welcome! Do you want to deposit some of your items? Or perhaps reclaim some of them? Well, well. Have you been to the shop near here which sells only the finest luxury goods? If you haven't yet, you should. Dwarf Galladucci, a member of my clan, runs the shop. He may seem a little eccentric, but he really has an eye for quality. Go see for yourself!
Private Warehouse
Clan Warehouse
Quest


RegAcquire is a batch script that acquires Windows Registry Dumps, it makes use of 2 other programs RawCopy and FCIV(File Checksum Integrity Verifier) for the sake of simplicity the batch script with the neccessary supporting files were built together in a standalone executable.
RegAcquire makes use of reg export found built-in in Windows.
Since reg export strips away some information, RegAcquire also acquires the physical hive files, in Windows system. These files are live files meaning they are constantly in use, thus making it difficult to copy it normally. VSS (Volume Shadow Copy) was used to capture these files using RawCopy.
File Checksum Integrity Verifier (FCIV) is used to hash the files as well as check the integrity of the forensic copy. The reason why these other two applications was used is to ensure that they can run on any Windows operating system targeted from Windows 7 and up, and for the reason that all Computers may not have some built-in features that could have been used for this purpose.
RegAcquire logs each process and creates MD5 hashes of each file for verifiability.
Since the original files are never used in Digital Forensics RegAcquire makes a forensically sound copy by copying the original files, logging each and then further verifying the copy by hashing the files of the copy and comparing them to the original files. The original files are marked as read-only and the hash file has special permissions that doesn't easily give access to anyone to write or modify it. RegAcquire performs two phase hash log to ensure that changes to the files can be detected, this is achieved by logging both in the acquired registry dumps and the entire life span of using the RegAcquire program, this is just a measure for authenticity and is only checked when there are suspicions.
osMore information
applicationMore information
networkMore information
deviceMore information
shimMore information
regviewMore information
reportingMore information
hashMore information
The various interfaces of the tools built.
Due to a rise in risks involved in the current digital age, we anticipate more cyber-crime. Criminalk footprints can appear in the Windows registry where large amounts of data regarding several aspects of a computer is stored. It is often difficult for Police officers and digital forensic investigators to fully analyse the Windows registry because of its vastness and lack of understanding. Performing analysis and finding evidence in the Windows registry is a very tedious and time-consuming process. Time (both for evidence collection, and analysis) and the complexity of extracting evidence from cyber crime scenes, are just some of the fundamental factors that inhibit the effectiveness of a forensic investigation.
These tools were developed for research purposes in attempt to harness the Windows Registry and aid analysis times, by performing various types of analysis and extracting information that is useful and also being able to develop reports from the acquired analysis. These tools are free and open source and urge people to contribute to it. The code is available on Github at
https://github.com/AvinashSingh786/RegAcquireand
https://github.com/AvinashSingh786/RegSmartThere are still areas that haven't been explored in this research due to time constraints. However, they will be incorporated soon.
Please fill out the information below if you have any complaints or suggestions.


--- layout: post authors: ["Greg Wilson"] title: "A New Template for Workshop Websites" date: 2014-10-04 time: "11:00:00" tags: ["Tooling"] ---
The first step in reorganizing the bc
repository is
making it easier (much easier) for people to create
websites for workshops. The
current instructions
are almost 3000 words long, and even experienced GitHub users find
the process daunting, so we're going to simplify things as much as
we can, even if that means not doing things the "right"
way.
Background
If a repository has a branch called gh-pages
(which
stands for "GitHub pages"), then GitHub uses the HTML
and Markdown files in that branch to create a website for the
repository. If the repository's URL
is http://github.com/darwin/finches
, the URL for
the website is http://darwin.github.io/finches
.
If an HTML or Markdown file has a header consisting of three dashes, some data about the page, and three more dashes:
--- key_1: value_1 key_2: value_2 --- page contents
then GitHub doesn't just copy the file over verbatim. Instead, it runs the file through a translator called Jekyll that processes instructions embedded in the file to generate the final HTML.
One of these instructions is {% raw %}{{variable}}{% endraw %}
. When
Jekyll sees this, it replaces the curly braces and the variable's
name with the value of variable
. This is used to
insert things like contact email addresses into the
page. (Variables from the page's header actually have to be
referred to as {% raw %}{{page.variable}}{% endraw %}
, rather than simply
as {% raw %}{{variable}}{% endraw %}
, because Jekyll can also get
variables in other ways that we're not using.)
If a page like index.html
has a variable
called layout
, and that variable's value
is standard.html
, Jekyll looks for a file
call _layouts/standard.html
and uses it as a
template for laying out the page. This is used to give the pages
in a site a uniform appearance.
Setup
Here's what you'll do to create a website for a workshop when we're done:
Download the latest version of a shell script
called create_workshop.sh
from the Software
Carpentry website and run it like this:
$ bash create_workshop.sh github_user_name workshop_id
where github_user_name
could
be swcarpentry
, your GitHub ID, or whatever,
and workshop_id
is something
like 2015-01-02-esu
. This will create a Git
repository beneath the current working directory and fill it
with starter files.
Go into the newly-created directory
named workshop_id
. This will be a GitHub repository
on your machine with a single branch called gh-pages
containing:
README.md
: a brief description of Software Carpentry with a prominent link to the workshop's GitHub page.Makefile
: contains commands for checking and building the website (see "Managing the Site" below).index.html
: the workshop's home page.bin/check.py
: a program to check the workshop's layout and the contents of its home page._layouts/workshop.html
: a page template for the site.
This repository will have a remote called origin
pointing at a newly-created
repository github.com/github_user_name/workshop_id
. (We
could get rid of _layouts/workshop.html
, and put
everything in index.html
, but we want to make it
easy for instructors to add more pages to their website.)
Edit the header in index.html
to specify the
workshop's dates, instructors, EventBrite registration key,
topics, etc. (See "Required Variables" below.)
Make sure that index.html
contains links to the
lessons being taught in the workshop (see "Linking to
Lessons" below).
Delete the installation instructions for software packages that aren't being used in the workshop (see "Software Installation Instructions" below).
git push origin gh-pages
to publish the workshop's
home page
at http://github_user_name.github.io/workshop_id/
.
This is all we need to do to set up a single-page site for a workshop, because:
index.html
, so
there's no need for _include
files.
index.html
can link to rendered online versions of
the lessons and the Code of Conduct, so we don't need to include
that in the workshop site every time (but see "Customizing
Lessons" below).
Required Variables
index.html
's YAML header must define the following
variables in order for the workshop website to show up properly on
the main Software Carpentry site:
layout
must be workshop
(which tells
Jekyll to use _layouts/workshop.html
as a page
template).
venue
is the name of the institution or group hosting
the workshop, such as "Euphoric State University".
address
is the workshop's address, such as "Room
101, Winston Smith Memorial Union, O'Brien Street."
country
must be a hyphenated country name like
'United-States'. It is used to look up flags for display in the
main web site.
latlng
is the latitude and longitude of the workshop
site (so we can put a pin on our map).
humandate
is the human-friendly dates for the
workshop (e.g., Jul 3-4, 2015). Please use three- or four-letter
month names and abbreviations (e.g., Dec
instead
of December
) so that columns will lay out properly on
the main website.
startdate
is the workshop's starting date in
YYYY-MM-DD format, e.g., 2015-07-03.
enddate
is the workshop's ending date in the same
format. If your workshop is only one day long,
the enddate
field should be omitted.
instructor
is a comma-separated list of instructor
names. This must be enclosed in square brackets, as
in ["Alan Turing","Grace
Hopper"]
. Please do not include affiliations, links,
or anything else besides the instructors' names.
helper
is a comma-separated list of helper names
formatted the same way, such as ["John von
Neumann"]
contact
is the contact email address to use for your
workshop, such as<EMAIL_ADDRESS>.
The header may optionally define:
eventbrite
: a multi-digit Eventbrite registration
key. If you are using Eventbrite, the admins will set this key for
you. If you are using something else for registration, this field
isn't needed.
Software Installation Instructions
We have tried managing software installation instructions three
different ways in the last year. Several instructors found file
inclusion directives and conditional blocks confusing, so we will go
back to the brute force solution: the
default index.html
page will include setup instructions
for everything, and website authors will delete the bits they don't
need.
Customizing Lessons
The default index.html
page contains links to our
standard lessons, along with a paragraph outlining what's covered in
each. As with software installation instructions, instructors can
delete links and descriptions that aren't relevant to their
workshop, then insert links and descriptions for custom lessons of
their own.
Managing the Site
To help people manage their workshop sites, Makefile
will contain these targets:
make
: without a target, this will print help.
make commands
: prints the same help.
make check
: run bin/check.py
to make
sure everything is formatted properly, and print error messages
identifying problems if it's not.
make site
: build the workshop website locally for
previewing. This assumes make check
has given the
site a clean bill of health, and requires Jekyll. (You can push
changes to GitHub and view them there as well.)
make listed
: check that the workshop is listed on the
Software Carpentry site.
make standalone
: get local copies of the CSS,
Javascript, images, etc. (See "Localizing" below.)
make page page_name.html
: create a new HTML page
called page_name.html
(or whatever) with the right
header, layout, etc. (See "Adding Content" below.)
make permission user_name
: give the user whose GitHub
user ID is user_name
permission to push to the GitHub
repository, modify its issues, etc.
make clean
: tidy up (i.e., delete the locally-built
website).
Localizing
The repository will also have a read-only Git remote
called source
pointing
at github.com/swcarpentry/workshop_source
. If people
want local copies of the CSS, Javascript, and images needed to
render their site (e.g., for offline work), then can pull
from source
. (Makefile
will contain a
target for this.)
Adding Content
Instructors can add their own data files, code samples, and so on to
the workshop's web site simply by adding those files to the Git repo
and pushing to origin
. They can also run make
page page_name.html
to create a new page
called page_name.html
, then add it and
push. bin/check.py
and make check
will
check the format of these pages as well as the format
of index.html
.
Customizing Lessons
If instructors want to present a modified version of a lesson, or add an entirely new lesson, they will:
Instructors can add lesson material to the workshop repository, but we will encourage them to keep the lessons separate because:
Sending Fixes
The one thing this scheme doesn't have is a link between
the workshop's repository and the workshop_source
repository that contains the master copy of the workshop site
material. This is deliberate: as per the current instructions,
instructors can't just clone a website template repository on GitHub
because GitHub will only let a particular user have one clone of a
particular repository.
In order to send fixes to the master copy of the website template,
people will therefore have to fork workshop_source
,
make the changes in their local copy of that, and then issue a pull
request. This does mean copying changes manually from a workshop
website to a local copy of workshop_source
, but there
doesn't seem to be any easy way around that. In practice, we expect
changes to the template will be relatively infrequent, so most
instructors won't ever encounter this.
Instructors and others will be able to file issues in
the workshop_source
repository to suggest
improvements. We will also use that repository's wiki to keep track
of teaching tips (just as we're using the bc
repository's wiki right now).
Checklists
When create_workshop.sh
creates the GitHub repository
for the workshop, it will also create several issues in that
repository's issue tracker to help the workshop's hosts and
instructors keep track of the things they need to do, such as
sending out welcome messages to learners, checking that learners
will have access to WiFi, and so on. Whoever created the GitHub
repository will need to run:
$ make permission user_name
for each of the other instructors to give them permission to push changes and modify issues.


That sounds great. I'd be happy with that
Could you send over some pictures of your dog, please?
Here are a few pictures. She's a happy girl !
Can you make it?
She looks so happy ! The time we discussed works. How long
shall I take her out for?
30 minutes walk
$29
1 hour walk
$49


1 Hearing this, Thonis seized Alexandrus and detained his ships there, and then brought him with Helen and all the wealth, and the suppliants too, to Memphis.
2 When all had arrived, Proteus asked Alexandrus who he was and whence he sailed; Alexandrus told him his lineage and the name of his country, and about his voyage, whence he sailed.
3 Then Proteus asked him where he had got Helen; when Alexandrus was evasive in his story and did not tell the truth, the men who had taken refuge with the temple confuted him, and related the whole story of the wrong.
4 Finally, Proteus declared the following judgment to them, saying, “If I did not make it a point never to kill a stranger who has been caught by the wind and driven to my coasts, I would have punished you on behalf of the Greek, you most vile man.  And not just with her, either, but you plundered your guest-friend's wealth and brought it, too.
6 Now, then, since I make it a point not to kill strangers, I shall not let you take away this woman and the wealth, but I shall watch them for the Greek stranger, until he come and take them away; but as for you and your sailors, I warn you to leave my country for another within three days, and if you do not, I will declare war on you.”


Moved documentation to being generated from Mkdocs instead of being converted from Markdown to HTML via GitHub pages Jekyll.
v0.5.0
Added
Slack: New class com.concur.Slack for sending directly to the Slack API, initially is a drop in replacement for the Jenkins plugin but does not make guarantees about future compatibility.
Updated
plNotify: Switch to the new Slack class for sending. Richer notification on end of build.
Fixed
Git.getVersion: Set increment minor to true by default. This restores the old functionality.
Fixed
plNotify: Fixed end of build notification.
v0.4.0
Added
Add SHORT_VERSION to default replacement option, this is the version provided by Git().getVersion() without the build number.
Updated
Git.getVersion: Update to be more flexible with tag retrieval, will now get latest from the current branch using git describe --tags
Git.timeSinceLatestTag: Signature changed to accept a tag string that is used in the underlying git command.
v0.3.0
Added
Added script to automatically generate documentation on commit.
Update com.concur.* groovy files with documentation.
Updated documentation in vars/*.txt, these are viewable in Pipeline Syntax -> Global Variable Reference from a pipeline job.
Add to setup.groovy script to set Markup formatter to Safe HTML so the vars documentation shows appropriately.
v0.2.0
Added
scripts/setup.groovy: Will configure a Jenkins instance to use these workflows/workflow libraries. Including adding as a global library, adding environment variables and adding a SSH credential.
Util.parseChangelog: Reads a changelog file to determine what releases are in it.
GitHubApi.getReleases: Use GitHub's GraphQL API to get information about a repositories releases.
GitHubApi.createRelease: Create a release in GitHub with release notes.
Changed
Working towards a more strongly typed system, updated vars from def to a static type in many areas.
Commands.getStageName: Added a default stage name if the method is not available or doesn't return anything.
All: Adding more descriptive assertion/errors so it is easier to determine where an error is happening.
Commands.getCredentialsWithCriteria: Will search global credentials first and return the credential if found before looking through the folder structure.
Commands.getJavaStackTrace: If provided a throwable will return the stacktrace for it as a \n joined string. throwable.getStackTrace() is blocked by Jenkins by default.
Git.runGitShellCommand: Uses powershell or sh step with returnStdout turned on instead of writing a file to the workspace.
Git.getVersion: Updated to remove println or move them to debugPrint.
GitHubApi.githubRequestWrapper: Add missing withCredentials block as well as set the Authorization header based on credentials.
GitHubApi.getPullRequests: Moved to use GraphQL instead of the v3 Rest API.
plNotify: Moved to a closure so instead of calling like this: plNotify(...) it must now be called like this plNotify { ... }.
v0.1.0
Added
Ability to load local and remote workflows.
debugPrint method with the ability to control whether to print or not by level.
Error handling when executing at various levels.
Text manipulation including replacements using mustache templating style.
Version generation by looking at existing tags on the repo and generating a semantic compatible version number.
Various helper for setting environment variables for Git information.


What?
Quickly and easily design ships for the space combat miniatures game Silent Death.
This ship builder implements the Starcraft Design System found in Silent Death: The Next Millennium. You will need the rules to play.
Features:
- Browser-based, no install required.
- Design ships in all the standard classes: fighters, scouts, shuttles, freighters, and gunboats.
- Arm them with all the standard cannons and warheads.
- Add basic ship options.
- Select crew skill levels (or optionally turn them off to see the cost of the ship without crew).
- Damage tracks are generated on the fly with every change you make.
- Copy ship builder URLs to save and share designs.
- Seamless offline mode (in modern browsers).
How?
Select a ship class. The rest of the design options should appear, and they speak for themselves (as long as you're familiar with the game).
If that doesn't work you probably don't have JavaScript enabled... or you're using a rather old browser, time to upgrade.
Tips
- Save your ship design: copy the URL at any time to save the design, or make a bookmark in your browser (bonus tip for Opera users: name your ship, highlight the name in the header, right-click and Copy to Note; it's like a super bookmark where you can also take notes).
- Design another ship: click Make duplicate to copy a ship design into a new tab, or Start over to reset the design in the current tab.
- Arrow keys are your friends: click twice on a drop-down to give it focus, then cycle through options rapidly using your arrow keys.
- Track damage: click on any damage track box to mark damage in red. Click again on a damaged box to make repairs.
- Offline use: assuming you're using a modern browser this app will work offline, automatically, and update automatically when you're online again, no extra effort required (just don't reload the page while you're offline or you may cause the application cache to be cleared). For reload-proof offline use: save this page (and its associated .js and .css files), as a single file archive if your browser provides this option. Or go to GitHub, click Downloads to get the whole thing as a zip, extract all of the contents, and double-click index.html.
- Go fullscreen: if you need more space pressing F11 in most browsers enters fullscreen mode. F11 again or ESC should exit fullscreen mode.
Discuss
- This and other ship builders, plus anything else Silent Death, at the official forums on Metal Express.
- Get updates and more, or contact the author directly, at Scott's gaming blog on Pair O' Dice Games.
Open Source
This application is open source software, go to GitHub for source and more details.
License (MIT)
Silent Death: The Next Millennium is a trademark of Mythic Entertainment LLC.
Copyright © 2009-2011 Scott Drake.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


Kotha Messages
(WORKS IN PROGRESS)
Your brower does not support audio streaming. Please use the link below to download the audio.
Kotha Gospel Message 01


Types of load balancers
- Application load balancers
- Work at layer 7 ( Preferred Method )
- Newest 2016
- Classic load balancer
- Layer 4 routing TCP layer
Creating a Load balancer
Services->EC2->[left panel]ELB->Create Load Balancer
- Select Classic Load Balancer
- Define Load Balancers
- Make sure its not an internal load balancer.
- If youre using default vpc keep advanced vpc disabled.
- leave the rest as default
- Assign Security Group.
- Configure Health Check.
- Use HTTP
- Set ping path as health.html
- Set response timeout as 2 seconds
- Interval at 5 seconds
- Unhealthy threshold 2
- Healthy threshold 3
- Add your EC2 Instances
- Add tags!
- Very important to keep track for the cost tracking
- Review and launch -> Create
It will take sometime to register the load balancer and the load balancer to come online.
- Instance monitored by ELB are reported as ; InService, or OutofService
- Health Checks check the instace health by doing a http request and getting the expected response from it.
- Hace their own DNS name. Never will be given an IP address.
- Read the ELB FAQ for Classic Load Balancers.


System Architect Picture "Desirability Of Property"
Parent Diagram:
Perception Of Property
(UML Class)


---------------------------------------
At the moment, DTN2 comes in source form only. Before you can install it and start using it, you need to compile it.
First, download DTN2 and ensure it has met all requirements. For released versions, see the SourceForge DTN2 release Page and unpack the release.
$ gunzip -c DTN2-X.Y.Z.tgz | tar xvf -
For the latest ("bleeding edge") version of the code see the section on Mercurial
Next, configure and compile DTN2: (the -C argument to configure enables the cache which speeds up the process)
$ cd DTN2 $ sh configure -C $ make
Note that by default, the configure script will also run configure inside the oasys/ subdirectory. The -C argument enables the autoconf variable cache, which speeds up configuration.
Note that if you need to make changes to the configure.ac script or one of the helper scripts in aclocal/*.ac, run build-configure.sh to recreate configure and then check in both your changes as well as the newly generated configure script.
If you just want to play with DTN2 to learn how it works, you can stop here. You can use all the programs as a regular user, with them in the source code directories. There's no need to do a full install into the public part of the filesystem. However, if you are deploying DTN2, you'll want to take a look at the tools/install.sh script. You might want to customize it, as it currently puts the files into /usr, and some people prefer to put files in /usr/local.
You can also access the latest ("bleeding edge") version of the code using mercurial. The various repositories are hosted at the DTNRG SourceForge repositories and can be cloned using:
% hg clone http://dtn.hg.sourceforge.net/hgweb/dtn/oasys % hg clone http://dtn.hg.sourceforge.net/hgweb/dtn/DTN2
See Using Mercurial for more information on using mercurial. Please be aware this code may be under frequent developmental changes, so your mileage may vary. For detailed information on using mercurial with the SourceForge repositories please see the mercurial access mechanisms. In addition, if you grab the development copy in this way, any README files or other docs may not be quite up to date.
If you plan on contributing code changes, please read the CONTRIBUTING file that describes the coding conventions for the project.
Please report any bugs to the Bugs tracker.
A good place to start for playing around with DTN is to look at the manual and tutorials (see doc/manual/index.html). This set of documentation explains some of the configuration and applications. If you find omissions or errors, please feel free to post updates and corrections to<EMAIL_ADDRESS>A bug tracking system is in place. Please direct bug reports to and direct questions to<EMAIL_ADDRESS>applib/ application interface library and ipc layer |-- perl Perl interface adaptor |-- python Python interface adaptor |-- tcl TCL interaface adaptor apps/ example dtn applications doc/ documentation daemon/ dtn router daemon sources ideas/ temporary code idea repository servlib/ dtn router internals |-- bundling bundle management and forwarding logic |-- cmd tcl based command interface |-- contacts |-- conv_layers convergence layers |-- discovery |-- gcm |-- naming endpoint identifier schemes |-- prophet prophet router |-- reg local registrations |-- routing bundle routing logic |-- security bundle security protocol |-- session `-- storage persistent storage management sim/ simulation framework test/ unit tests and other test files test-utils/ test scripts and utilities
Before compiling DTN2 please compile Oasys-1.3.0+ (must be installed or located in DTN2 or ../). For released versions, see the SourceForge DTN2 release Page and unpack the release.
$ gunzip -c oasys-X.Y.Z.tgz | tar xvf -
For the latest ("bleeding edge") version of the code see the section on Mercurial
Next, configure and compile oasys:
$ cd oasys (or oasys-X.Y.Z) $ sh configure $ make
Support for the following DTN2 options should be specified when configuring oasys
specify location / support of:
compile with or without support for:
enable or disable:
The standard ciphersuites require, amongst other things, an implementation of sha-256 message digest algorithm.
The DTN reference code uses OpenSSL for cryptographic and related functions. Unfortunately, some versions of OpenSSL do not include sha-256.
The "configure" process checks for the availability of sha-256 and provides an error if it is not found.
If your system's OpenSSL does not have sha-256 then you can either upgrade it or build and use a local version of OpenSSL. OpenSSL can be obtained from openssl.org
OpenSSL 0.9.8 version include sha-256 by default. If your system uses version 0.9.7 and you do not wish to upgrade then you can enable sha-256 in later versions of 0.9.7, such as 0.9.7l and 0.9.7m. To enable sha-256, specify "fips" when running "Configure".
If you wish to leave your system installation untouched and build against a local version, then configure dtn using ./configure --with-bsp --with-openssl=/path/to/openssl
Mac OS X note: for Mac OS X users ONLY. If you build dtn against a local OpenSSL using "--with-openssl=/path/to/openssl" you MUST also specify with it LDFLAGS="-Wl,-search_paths_first". The configuration for OS X users would then be ./configure --with-bsp --with-openssl=/path/to/openssl LDFL
Please see the norm installation instructions.
DTN2 does not yet work as a native Windows application. It might, however, work with the Cygwin environment.
The first step is to install Cygwin on your computer. The best way to do this is to download setup.exe from their website. We suggest storing it on your computer in a new directory you make named c:\cygwin\download.
Start setup.exe and choose "Install from Internet". (Always think carefully before running an executeable you downloaded from the Internet, even if a nice manual like this told you to do it! Is your virus checker running? Is it up to date? Did the file come from the website you think it did?) Use the default root directory, c:\cygwin. Make the "Local Package Directory" c:\cygwin\download. Cygwin will ask you to choose a mirror, so choose one that is close to you on the Internet. It will then ask you to "Select Packages". The defaults here are pretty good, but you need to make a few changes:
Continue with the installation. When it is done, you'll have a working Cygwin installation and be ready to proceed. If you are asked to reboot, please do so. This ensures the correct version of Cygwin will be used.
Once you have installed Cygwin, you'll have a new item in your Start -> All Programs menu called Cygwin, and inside that, one called Bash. When you select it, you get a bash shell, which is like a CMD window, only cooler. You start out in your home directory, which in Cygwin is /home/$user, but in Windows, it is c:\cygwin\home\$user. Now that you have a Unix-like window, follow the Unix instructions above. Cygwin comes with CVS, so you can even use CVS to fetch the source code, as described above.


Feature: Task 1 | Traditional | Footer Contact, Keep in Touch and Quick Links Validation
As a test engineer, I'd like to validate that the Contact, Keep in Touch and Quick Link footer elements are rendered and visible by default on Laptop and Tablet and are hidden on Mobile.
Before
Hook
open https://demo.applitools.com/gridHackathonV1.html#0
scroll to the footer
Then
I expect that the Contacts header and its elements are visible on Tablet and Laptop and are collapsed on Mobile
+ Show Info
Contacts header is displayed
contact email link is not displayed
contact address text is not displayed
After
Hook
After
Hook
Before
Hook
open https://demo.applitools.com/gridHackathonV2.html#0
scroll to the footer
Then
I expect that the Contacts header and its elements are visible on Tablet and Laptop and are collapsed on Mobile
+ Show Info
Contacts header is displayed
contact email link is not displayed
contact address text is not displayed
After
Hook
After
Hook
Before
Hook
open https://demo.applitools.com/gridHackathonV1.html#0
scroll to the footer
Then
I expect that the Keep in touch header and its elements are visible on Tablet and Laptop and are collapsed on Mobile
+ Show Info
Keep in touch header is displayed
email text box is not displayed
email submit button is not displayed
After
Hook
After
Hook
Before
Hook
open https://demo.applitools.com/gridHackathonV2.html#0
scroll to the footer
Then
I expect that the Keep in touch header and its elements are visible on Tablet and Laptop and are collapsed on Mobile
+ Show Info
Keep in touch header is displayed
email text box is not displayed
email submit button is not displayed
After
Hook
After
Hook
Before
Hook
open https://demo.applitools.com/gridHackathonV1.html#0
scroll to the footer
Then
I expect that the Quick Links header and its elements are visible on Tablet and Laptop and are collapsed on Mobile
+ Show Info
Quick Links header is displayed
quick link About us is not displayed
quick link Faq is not displayed
quick link Help is not displayed
quick link My account is not displayed
quick link Blog is not displayed
quick link Contacts is not displayed
| About us |
|---|
| Faq |
| Help |
| My account |
| Blog |
| Contacts |
After
Hook
After
Hook
Before
Hook
open https://demo.applitools.com/gridHackathonV2.html#0
scroll to the footer
Then
I expect that the Quick Links header and its elements are visible on Tablet and Laptop and are collapsed on Mobile
+ Show Error
+ Show Info
+ Screenshot
Actual: undefined Expected: undefined Stack: AssertionError: Footer Quick Links Test Failed. Here are the issues: quick link with selector //div[contains(@id,"DIV__collgcolmd__42")]//a[contains(text(),"About us")] is displayed quick link with selector //div[contains(@id,"DIV__collgcolmd__42")]//a[contains(text(),"Faq")] is displayed quick link with selector //div[contains(@id,"DIV__collgcolmd__42")]//a[contains(text(),"Help")] is displayed quick link with selector //div[contains(@id,"DIV__collgcolmd__42")]//a[contains(text(),"My account")] is displayed quick link with selector //div[contains(@id,"DIV__collgcolmd__42")]//a[contains(text(),"Blog")] is displayed quick link with selector //div[contains(@id,"DIV__collgcolmd__42")]//a[contains(text(),"Contacts")] is displayed: expected 6 to equal 0 at World.(anonymous) (/Users/barresiv/Workspace/applitools-hackathon-applifashion/src/steps/specs/task 1/traditional/footer-quick-contact-and-keep-in-touch-traditional-validation.spec.js:117:109) at processTicksAndRejections (internal/process/task_queues.js:93:5) at World.executeAsync (/Users/barresiv/Workspace/applitools-hackathon-applifashion/node_modules/@wdio/utils/build/shim.js:123:12) at World.testFrameworkFnWrapper (/Users/barresiv/Workspace/applitools-hackathon-applifashion/node_modules/@wdio/utils/build/test-framework/testFnWrapper.js:63:14)
Quick Links header is displayed
| About us |
|---|
| Faq |
| Help |
| My account |
| Blog |
| Contacts |
After
Hook
After
Hook


Data Structures | |
| struct | vpx_codec_stream_info |
| Stream properties. More... | |
| struct | vpx_codec_dec_cfg |
| Initialization Configurations. More... | |
Modules | |
| Frame-Based Decoding Functions | |
| Slice-Based Decoding Functions | |
Files | |
| file | vpx_decoder.h |
Describes the decoder algorithm interface to applications. | |
Defines | |
| #define | VPX_DECODER_ABI_VERSION |
| Current ABI version number. | |
| #define | VPX_CODEC_CAP_PUT_SLICE 0x10000 |
| Decoder capabilities bitfield. | |
| #define | VPX_CODEC_CAP_PUT_FRAME 0x20000 |
| #define | VPX_CODEC_CAP_POSTPROC 0x40000 |
| #define | VPX_CODEC_USE_POSTPROC 0x10000 |
| Initialization-time Feature Enabling. | |
| #define | vpx_codec_dec_init(ctx, iface, cfg, flags) vpx_codec_dec_init_ver(ctx, iface, cfg, flags, VPX_DECODER_ABI_VERSION) |
| Convenience macro for vpx_codec_dec_init_ver(). | |
Typedefs | |
| typedef struct vpx_codec_stream_info | vpx_codec_stream_info_t |
| Stream properties. | |
| typedef struct vpx_codec_dec_cfg | vpx_codec_dec_cfg_t |
| Initialization Configurations. | |
Functions | |
| vpx_codec_err_t | vpx_codec_dec_init_ver (vpx_codec_ctx_t *ctx, vpx_codec_iface_t *iface, vpx_codec_dec_cfg_t *cfg, vpx_codec_flags_t flags, int ver) |
| Initialize a decoder instance. | |
| vpx_codec_err_t | vpx_codec_peek_stream_info (vpx_codec_iface_t *iface, const uint8_t *data, unsigned int data_sz, vpx_codec_stream_info_t *si) |
| Parse stream info from a buffer. | |
| vpx_codec_err_t | vpx_codec_get_stream_info (vpx_codec_ctx_t *ctx, vpx_codec_stream_info_t *si) |
| Return information about the current stream. | |
| vpx_codec_err_t | vpx_codec_decode (vpx_codec_ctx_t *ctx, const uint8_t *data, unsigned int data_sz, void *user_priv, long deadline) |
| Decode data. | |
| vpx_image_t * | vpx_codec_get_frame (vpx_codec_ctx_t *ctx, vpx_codec_iter_t *iter) |
| Decoded frames iterator. |
This abstraction allows applications using this decoder to easily support multiple video formats with minimal code duplication. This section describes the interface common to all decoders.
| #define VPX_CODEC_CAP_PUT_SLICE 0x10000 |
Decoder capabilities bitfield.
Each decoder advertises the capabilities it supports as part of its vpx_codec_iface_t interface structure. Capabilities are extra interfaces or functionality, and are not required to be supported by a decoder.
The available flags are specifiedby VPX_CODEC_CAP_* defines. Will issue put_slice callbacks
| #define VPX_CODEC_CAP_PUT_FRAME 0x20000 |
Will issue put_frame callbacks
| #define VPX_CODEC_CAP_POSTPROC 0x40000 |
Can postprocess decoded frame
| #define VPX_CODEC_USE_POSTPROC 0x10000 |
Initialization-time Feature Enabling.
Certain codec features must be known at initialization time, to allow for proper memory allocation.
The available flags are specified by VPX_CODEC_USE_* defines. Postprocess decoded frame
| #define vpx_codec_dec_init | ( | ctx, | |||
| iface, | |||||
| cfg, | |||||
| flags | ) | vpx_codec_dec_init_ver(ctx, iface, cfg, flags, VPX_DECODER_ABI_VERSION) |
Convenience macro for vpx_codec_dec_init_ver().
Ensures the ABI version parameter is properly set.
| typedef struct vpx_codec_stream_info vpx_codec_stream_info_t |
Stream properties.
This structure is used to query or set properties of the decoded stream. Algorithms may extend this structure with data specific to their bitstream by setting the sz member appropriately.
| typedef struct vpx_codec_dec_cfg vpx_codec_dec_cfg_t |
Initialization Configurations.
This structure is used to pass init time configuration options to the decoder. alias for struct vpx_codec_dec_cfg
| vpx_codec_err_t vpx_codec_dec_init_ver | ( | vpx_codec_ctx_t * | ctx, | |
| vpx_codec_iface_t * | iface, | |||
| vpx_codec_dec_cfg_t * | cfg, | |||
| vpx_codec_flags_t | flags, | |||
| int | ver | |||
| ) |
Initialize a decoder instance.
Initializes a decoder context using the given interface. Applications should call the vpx_codec_dec_init convenience macro instead of this function directly, to ensure that the ABI version number parameter is properly initialized.
In XMA mode (activated by setting VPX_CODEC_USE_XMA in the flags parameter), the storage pointed to by the cfg parameter must be kept readable and stable until all memory maps have been set.
| [in] | ctx | Pointer to this instance's context. |
| [in] | iface | Pointer to the alogrithm interface to use. |
| [in] | cfg | Configuration to use, if known. May be NULL. |
| [in] | flags | Bitfield of VPX_CODEC_USE_* flags |
| [in] | ver | ABI version number. Must be set to VPX_DECODER_ABI_VERSION |
| VPX_CODEC_OK | The decoder algorithm initialized. | |
| VPX_CODEC_MEM_ERROR | Memory allocation failed. |
| vpx_codec_err_t vpx_codec_peek_stream_info | ( | vpx_codec_iface_t * | iface, | |
| const uint8_t * | data, | |||
| unsigned int | data_sz, | |||
| vpx_codec_stream_info_t * | si | |||
| ) |
Parse stream info from a buffer.
Performs high level parsing of the bitstream. Construction of a decoder context is not necessary. Can be used to determine if the bitstream is of the proper format, and to extract information from the stream.
| [in] | iface | Pointer to the alogrithm interface |
| [in] | data | Pointer to a block of data to parse |
| [in] | data_sz | Size of the data buffer |
| [in,out] | si | Pointer to stream info to update. The size member MUST be properly initialized, but MAY be clobbered by the algorithm. This parameter MAY be NULL. |
| VPX_CODEC_OK | Bitstream is parsable and stream information updated |
| vpx_codec_err_t vpx_codec_get_stream_info | ( | vpx_codec_ctx_t * | ctx, | |
| vpx_codec_stream_info_t * | si | |||
| ) |
Return information about the current stream.
Returns information about the stream that has been parsed during decoding.
| [in] | ctx | Pointer to this instance's context |
| [in,out] | si | Pointer to stream info to update. The size member MUST be properly initialized, but MAY be clobbered by the algorithm. This parameter MAY be NULL. |
| VPX_CODEC_OK | Bitstream is parsable and stream information updated |
| vpx_codec_err_t vpx_codec_decode | ( | vpx_codec_ctx_t * | ctx, | |
| const uint8_t * | data, | |||
| unsigned int | data_sz, | |||
| void * | user_priv, | |||
| long | deadline | |||
| ) |
Decode data.
Processes a buffer of coded data. If the processing results in a new decoded frame becoming available, PUT_SLICE and PUT_FRAME events may be generated, as appropriate. Encoded data MUST be passed in DTS (decode time stamp) order. Frames produced will always be in PTS (presentation time stamp) order.
| [in] | ctx | Pointer to this instance's context |
| [in] | data | Pointer to this block of new coded data. If NULL, a VPX_CODEC_CB_PUT_FRAME event is posted for the previously decoded frame. |
| [in] | data_sz | Size of the coded data, in bytes. |
| [in] | user_priv | Application specific data to associate with this frame. |
| [in] | deadline | Soft deadline the decoder should attempt to meet, in us. Set to zero for unlimited. |
| vpx_image_t* vpx_codec_get_frame | ( | vpx_codec_ctx_t * | ctx, | |
| vpx_codec_iter_t * | iter | |||
| ) |
Decoded frames iterator.
Iterates over a list of the frames available for display. The iterator storage should be initialized to NULL to start the iteration. Iteration is complete when this function returns NULL.
The list of available frames becomes valid upon completion of the vpx_codec_decode call, and remains valid until the next call to vpx_codec_decode.
| [in] | ctx | Pointer to this instance's context |
| [in,out] | iter | Iterator storage, initialized to NULL |


|
|||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object | +--org.cyberneko.pull.XMLEvent
The base XML event class. For a complete list of available events,
refer to the org.cyberneko.pull.event
package.
| Field Summary | |
org.apache.xerces.xni.Augmentations |
augs
Event augmentations. |
static short |
CDATA
Event type: CDATA section. |
static short |
CHARACTERS
Event type: character content. |
static short |
COMMENT
Event type: comment. |
static short |
DOCTYPE_DECL
Event type: DOCTYPE declaration. |
static short |
DOCUMENT
Event type: document. |
static short |
ELEMENT
Event type: element. |
static short |
GENERAL_ENTITY
Event type: general entity. |
XMLEvent |
next
Next event, if used in an event chain. |
static short |
PREFIX_MAPPING
Event type: prefix mapping. |
static short |
PROCESSING_INSTRUCTION
Event type: processing instruction. |
static short |
TEXT_DECL
Event type: text declaration. |
short |
type
Event type. |
| Constructor Summary | |
XMLEvent(short type)
Constructs an XML event with the specified type. |
| Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Field Detail |
public static final short DOCUMENT
public static final short ELEMENT
public static final short CHARACTERS
public static final short PREFIX_MAPPING
public static final short GENERAL_ENTITY
public static final short COMMENT
public static final short PROCESSING_INSTRUCTION
public static final short CDATA
public static final short TEXT_DECL
public static final short DOCTYPE_DECL
public final short type
public org.apache.xerces.xni.Augmentations augs
public XMLEvent next
| Constructor Detail |
public XMLEvent(short type)
|
|||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


{{include file='layouts/_layout'}}
{{include file='layouts/_site_nav'}} {{include file='layouts/_head'}} {{include file='layouts/_menu'}}
{{$article.title}}
{{$article.content|raw}}
{{include file='layouts/_foot'}}


How many lines does each diagram below have? Two lines can be related to each other in different ways.
Line A intersects with line C. They form intersecting lines.
Line FG and line HI do not intersect. They do not meet at any point. They are parallel lines.
Line KL and line JM intersect in a special way forming square comers. They are perpendicular lines.
Let's Practice!Using the figure below, answer the questions that follow.
1. How many lines are there in the figure? Four lines
2. What are the intersecting lines?
Line CI and AI
Line AD and ID
Line AB and EB
Line BE and AE
Line BA and EA
3. What is the point of intersection of line CI and AI? Point I
4. Which lines are parallel? Line E and C
5. Which lines are perpendicular? Line CI and AD


<mainbooktitle>
The <mainbooktitle> element contains the primary title information for a book.
Category: Bookmap content elements


How Become a Great Java Developer
At about the same time, Rahul Roy Chowdhury took charge of Google team that oversees.Chrome, the company’s web browser. remember the ‘Web is Dead’ article very clearly, he remembers. “I thought: ‘Oh My God. I’ve made a mistake.'” Needless to say, he didn’t really believe that.The like button was first announced as a FriendFeed feature on October 30, 2007 and was popularized within its community.
Later on the feature was integrated to Facebook before eventually FriendFeed was acquired by Facebook August 10, 2009.The Facebook like button is designed as a hand giving "thumbs up". It was originally discussed to have been a star or a plus sign, and during development the feature was referred to as "awesome" instead of "like". It was introduced on 9 February 2009.
Comments 4
Alex Martin
3 day agoMan's technological ascent began in earnest in what is known as the Neolithic period ("New stone age"). The invention of polished stone axes was a major advance that allowed forest clearance on a large scale . Agriculture fed larger populations, and the transition to sedentism.allowed simultaneously raising more children, as infants no longer needed to be carried,
Jannatul Ferdaous
1 day agoMan's technological ascent began in earnest in what is known as the Neolithic period The invention of polished stone axes was a major advance that allowed forest clearance on a large scale . Agriculture fed larger populations,
Josef Doe
5 day agoOptimistic assumptions are made by proponents of ideologies such as transhumanism and singularitarianism, which view technological development as generally having beneficial effects for the society and the human condition. In these ideologies, technological development is morally good. Some critics see these ideologies as examples of scientism and techno-utopianism and fear the notion.


| I l@ve RuBoard |
4.2 The array ModuleThe array module implements an efficient array storage type. Arrays are similar to lists, but all items must be of the same primitive type. The type is defined when the array is created. Examples 4-1 through 4-5 are simple ones. Example 4-1 creates an array object and copies the internal buffer to a string through the tostring method. Example 4-1. Using the array Module to Convert Lists of Integers to StringsFile: array-example-1.py import array a = array.array("B", range(16)) # unsigned char b = array.array("h", range(16)) # signed short print a print repr(a.tostring()) print b print repr(b.tostring()) array('B', [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15]) '\000\001\002\003\004\005\006\007\010\011\012\013\014\015\016\017' array('h', [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15]) '\000\000\001\000\002\000\003\000\004\000\005\000\006\000\007\000 \010\000\011\000\012\000\013\000\014\000\015\000\016\000\017\000' The array objects can be treated as ordinary lists to some extent, as Example 4-2 shows. You cannot concatenate arrays if they have different type codes, though. Example 4-2. Using Arrays as Ordinary SequencesFile: array-example-2.py import array a = array.array("B", [1, 2, 3]) a.append(4) a = a + a a = a[2:-2] print a print repr(a.tostring()) for i in a: print i, array('B', [3, 4, 1, 2]) '\003\004\001\002' 3 4 1 2 This module also provides a very efficient way to turn raw binary data into a sequence of integers (or floating point values, for that matter), as Example 4-3 demonstrates. Example 4-3. Using Arrays to Convert Strings to Lists of IntegersFile: array-example-3.py import array a = array.array("i", "fish license") # signed integer print a print repr(a.tostring()) print a.tolist() array('i', [1752394086,<PHONE_NUMBER>,<PHONE_NUMBER>]) 'fish license' [1752394086,<PHONE_NUMBER>,<PHONE_NUMBER>] Finally, Example 4-4 shows how to use this module to determine the endianess of the current platform. Example 4-4. Using the array Module to Determine Platform EndianessFile: array-example-4.py import array def little_endian(): return ord(array.array("i",[1]).tostring()[0]) if little_endian(): print "little-endian platform (intel, alpha)" else: print "big-endian platform (motorola, sparc)" big-endian platform (motorola, sparc) Python 2.0 and later provides a sys.byteorder attribute, which is set to either "little" or "big," as you can see in Example 4-5. Example 4-5. Using the sys.byteorder Attribute to Determine Platform Endianess (Python 2.0)File: sys-byteorder-example-1.py import sys # 2.0 and later if sys.byteorder == "little": print "little-endian platform (intel, alpha)" else: print "big-endian platform (motorola, sparc)" big-endian platform (motorola, sparc) |
| I l@ve RuBoard |


Your data export is complete. You can download the .json from this temporary link here: {{dataLink}} If you have any questions feel free to send us an email. CallParty Team http://callparty.org


\PHPUnit_Util_Log_JUnit
A TestListener that generates a logfile of the test execution in XML markup.
The XML markup used is the same as the one that is used by the JUnit Ant task.
- Author: Sebastian Bergmann<EMAIL_ADDRESS>- Copyright: 2001-2014 Sebastian Bergmann<EMAIL_ADDRESS>- License: http://www.opensource.org/licenses/BSD-3-Clause The BSD 3-Clause License
Synopsis
- // members
- protected DOMDocument $document;
- protected DOMElement $root;
- protected boolean $logIncompleteSkipped;
- protected boolean $writeDocument;
- protected array $testSuites;
- protected array $testSuiteTests;
- protected array $testSuiteAssertions;
- protected array $testSuiteErrors;
- protected array $testSuiteFailures;
- protected array $testSuiteTimes;
- protected integer $testSuiteLevel;
- protected DOMElement $currentTestCase;
- protected boolean $attachCurrentTestCase;
- // Inherited members from PHPUnit_Util_Printer
- protected boolean $autoFlush;
- protected resource $out;
- protected string $outTarget;
- protected boolean $printsHTML;
- // methods
- public void __construct()
- public void flush()
- public void addError()
- public void addFailure()
- public void addIncompleteTest()
- public void addRiskyTest()
- public void addSkippedTest()
- public void startTestSuite()
- public void endTestSuite()
- public void startTest()
- public void endTest()
- public string getXML()
- public string setWriteDocument()
- // Inherited methods from PHPUnit_Util_Printer
- public void __construct()
- public void flush()
- public void incrementalFlush()
- public void write()
- public boolean getAutoFlush()
- public void setAutoFlush()
Hierarchy
Violations
Checkstyle
| Line | Column | Severity | Message |
|---|---|---|---|
| 179 | 26 | error | Only one argument is allowed per line in a multi-line function call |
| 212 | 32 | error | Only one argument is allowed per line in a multi-line function call |
| 354 | 22 | error | Only one argument is allowed per line in a multi-line function call |
| 358 | 27 | error | Only one argument is allowed per line in a multi-line function call |
| 362 | 25 | error | Only one argument is allowed per line in a multi-line function call |
| 366 | 23 | error | Only one argument is allowed per line in a multi-line function call |
| 370 | 21 | error | Only one argument is allowed per line in a multi-line function call |
| 427 | 39 | error | Only one argument is allowed per line in a multi-line function call |
| 432 | 29 | error | Only one argument is allowed per line in a multi-line function call |
Members
protected
- $attachCurrentTestCase — boolean
- $autoFlush
—
boolean
If true, flush output after every write. - $currentTestCase — DOMElement
- $document — DOMDocument
- $logIncompleteSkipped — boolean
- $out — resource
- $outTarget — string
- $printsHTML — boolean
- $root — DOMElement
- $testSuiteAssertions — array
- $testSuiteErrors — array
- $testSuiteFailures — array
- $testSuiteLevel — integer
- $testSuiteTests — array
- $testSuiteTimes — array
- $testSuites — array
- $writeDocument — boolean
Methods
public
- __construct() — Constructor.
- addError() — An error occurred.
- addFailure() — A failure occurred.
- addIncompleteTest() — Incomplete test.
- addRiskyTest() — Risky test.
- addSkippedTest() — Skipped test.
- endTest() — A test ended.
- endTestSuite() — A testsuite ended.
- flush() — Flush buffer and close output.
- getXML() — Returns the XML as a string.
- setWriteDocument() — Enables or disables the writing of the document in flush().
- startTest() — A test started.
- startTestSuite() — A testsuite started.
Inherited from PHPUnit_Util_Printer
public
- flush() — Flush buffer, optionally tidy up HTML, and close output if it's not to a php stream
- getAutoFlush() — Check auto-flush mode.
- incrementalFlush() — Performs a safe, incremental flush.
- setAutoFlush() — Set auto-flushing mode.
- write()
History
-
2014-08-12T06:43:31+02:00 (commit #50dfaba)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>phpcbf --standard=PSR2 src tests
-
2014-02-14T18:31:32+01:00 (commit #e5b50bc)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Next version will be 4.0
-
2014-01-23T12:54:08+01:00 (commit #9a60003)
Author: Andy<EMAIL_ADDRESS>/ Commiter: Andy<EMAIL_ADDRESS>add system-out node to testcase element in junit xml output
-
2014-01-22T19:43:07+01:00 (commit #02b42d7)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Initial work on formatting code according to PSR-2
-
2014-01-20T17:21:13+01:00 (commit #3a5808f)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Cleanup
-
2014-01-09T08:11:47+01:00 (commit #205e008)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Bump copyright year
-
2014-01-07T14:37:15+01:00 (commit #991bf00)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Revert "Next stable release will be PHPUnit 4" This reverts commit f4ee7815d1bb1664786fe95b226a3def20f24aa9.
-
2014-01-06T09:05:08+01:00 (commit #f4ee781)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Next stable release will be PHPUnit 4
-
2014-01-03T10:56:51+01:00 (commit #5fa6726)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Introduce new test classification: risky test
-
2013-01-07T11:37:52+01:00 (commit #c517984)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Bump copyright year
-
2012-11-14T18:03:45+01:00 (commit #896386a)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Get rid off hackery to put @category, @package, @subpackage information into JUnit XML logfiles.
-
2012-09-24T06:47:44+02:00 (commit #81ab540)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Do not perform string replacement for @package_version@ anymore.
-
2012-05-27T14:12:42+02:00 (commit #76a561e)
Author: Volker Dusch<EMAIL_ADDRESS>/ Commiter: Volker Dusch<EMAIL_ADDRESS>Revert "Merge pull request #572 from mgb/excluded_tests_testlistener" This reverts commit 3b5d59a5d341f9b851ea373a31beb1cdc4b10ccb, reversing changes made to 063359e67e2031ba2ab9afdeb1bd6855c90987e4.
-
2012-05-20T19:52:08+02:00 (commit #67876c2)
Author: Ryan Murphy<EMAIL_ADDRESS>/ Commiter: Mine GO BOOM<EMAIL_ADDRESS>Quick hack to make ResultPrinter.php include excluded tests in its output. I choose to use an underscore as the output as we would want to have the total percentage complete to end up with 100%. If instead we would call writeProgress(NULL) and not have it output anything nor increment $this->column, it would cause the total summary to continue to increment. That does have the side effect where if you hit a chunk of excluded tests, your counter may go from 122/1300 to 553/1300 on the following line with no real indication of why. Another option I thought of was to instead cause the total number of tests counter to decrement, but that also looks weird if you go from 120/1500 (8%) to 160/800 (20%). But in the case when you exclude large chunks, it would prevent lots of useless output.
-
2012-04-30T12:02:38+02:00 (commit #5786e50)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>List The BSD 3-Clause License correctly and consistently. Thanks to Christian Aistleitner<EMAIL_ADDRESS>for bringing this issue to my attention.
-
2012-01-01T11:21:16+01:00 (commit #aae6c38)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Bump copyright year.
-
2011-12-20T17:47:06+01:00 (commit #6f3bcf8)
Author: Volker Dusch<EMAIL_ADDRESS>/ Commiter: Volker Dusch<EMAIL_ADDRESS>Add phpcs rule for concatination operator spacing and fixed the few issues it shows
-
2011-01-25T08:24:47+01:00 (commit #2b7f44f)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Do not use PHP_CodeCoverage blacklist for PHPUnit stacktrace filtering.
-
2010-12-31T11:45:34+01:00 (commit #bee3344)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Bump copyright year.
-
2010-07-07T12:42:23+02:00 (commit #f0d9cdd)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Change email address.
-
2010-06-12T20:25:54+02:00 (commit #d19a737)
Author: Mark Story<EMAIL_ADDRESS>/ Commiter: Mark Story<EMAIL_ADDRESS>Removing trailing whitespace from files. Refs #1063
-
2010-04-05T17:41:26+02:00 (commit #471d69e)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Add @subpackage annotation.
-
2010-02-02T14:14:29+01:00 (commit #bc1aaaa)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Remove closing PHP tags.
-
2010-01-19T09:39:03+01:00 (commit #fb48a69)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Initial work on autoloading.
-
2009-12-31T09:26:09+01:00 (commit #37f75ff)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Bump copyright year.
-
2009-12-31T09:25:53+01:00 (commit #bddcc5f)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Bump copyright year.
-
2009-12-31T09:23:37+01:00 (commit #7a7d0b7)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Bump copyright year.
-
2009-12-25T10:32:26+01:00 (commit #60e7125)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Remove Subversion keywords.
-
2009-12-25T10:30:57+01:00 (commit #42294ad)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Remove Subversion keywords.
-
2009-12-25T10:26:35+01:00 (commit #8617133)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Remove Subversion keywords.
-
2009-12-22T18:15:22+01:00 (commit #ad803c7)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [5465].
-
2009-12-22T18:11:03+01:00 (commit #e18aada)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [5465].
-
2009-12-22T18:10:30+01:00 (commit #84ce285)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Fix #949.
-
2009-11-23T09:39:24+01:00 (commit #1503412)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [5389].
-
2009-11-23T09:29:23+01:00 (commit #4c9cf4e)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Initial work on PHP_CodeCoverage migration.
-
2009-08-29T10:49:43+02:00 (commit #f144a51)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [5161].
-
2009-08-29T10:24:37+02:00 (commit #86e29fa)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Fix CS/WS issues.
-
2009-07-30T09:50:07+02:00 (commit #e6e0230)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [5037].
-
2009-07-30T09:40:27+02:00 (commit #b2110c2)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Rename PHPUnit_Util_Log_XML to PHPUnit_Util_Log_JUnit.
-
2009-04-09T12:04:25+02:00 (commit #c59c79d)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [4777].
-
2009-04-09T12:04:00+02:00 (commit #d742e3d)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Be more defensive.
-
2008-12-31T10:26:51+01:00 (commit #a899cb2)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [4402].
-
2008-12-31T10:25:57+01:00 (commit #4b26cea)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Bump copyright year.
-
2008-10-24T14:52:06+02:00 (commit #077f9d9)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Rewrite PHPUnit_Util_Class::getClassesInFile(), PHPUnit_Util_Class::getFunctionsInFile, and PHPUnit_Util_Class::getPackageInformation() to use the tokenizer instead of the Reflection API. Eliminate PHPUnit_Util_Class::getFunctionSignature() and PHPUnit_Util_Class::getMethodSignature(). Close #590.
-
2008-09-09T12:17:05+02:00 (commit #61b7525)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Try to detect UTF-8 and avoid encoding UTF-8 as UTF-8. Do not use CDATA and use htmlspecialchars() for escaping instead.
-
2008-06-08T14:22:29+02:00 (commit #191a5d5)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [3160].
-
2008-06-08T14:03:37+02:00 (commit #9d9b5e3)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Drop superfluous annotations.
-
2008-05-08T19:32:15+02:00 (commit #a95bc10)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [2957].
-
2008-05-08T19:32:11+02:00 (commit #7538b32)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Implement assertion counting.
-
2008-04-10T10:58:41+02:00 (commit #d24a156)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [2776].
-
2008-04-10T10:58:38+02:00 (commit #eacefbe)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Fix #452.
-
2008-04-02T16:13:40+02:00 (commit #00b0248)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [2684].
-
2008-04-02T16:13:36+02:00 (commit #e03d46e)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Fugbix typo.
-
2008-02-06T09:44:07+01:00 (commit #11978b6)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [2345].
-
2008-02-06T09:44:05+01:00 (commit #c9ba361)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Add fullPackage and namespace attributes.
-
2008-01-22T10:29:08+01:00 (commit #705b5b8)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Fix bad merge.
-
2008-01-22T09:56:31+01:00 (commit #b0c543a)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [2242].
-
2008-01-22T09:56:28+01:00 (commit #52187bc)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Fix for non-standard tests.
-
2008-01-19T18:04:39+01:00 (commit #72414cc)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [2221].
-
2008-01-19T18:04:32+01:00 (commit #5afc416)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Fix #356.
-
2007-12-26T19:11:55+01:00 (commit #1bba1cc)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Bump copyright year.
-
2007-12-26T19:11:04+01:00 (commit #58121cf)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Bump copyright year.
-
2007-12-09T13:39:26+01:00 (commit #d59c5f2)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [1859].
-
2007-12-09T13:39:17+01:00 (commit #6b81436)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Close #301.
-
2007-11-24T11:03:40+01:00 (commit #9c20935)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>toString -> __toString()
-
2007-11-09T15:52:08+01:00 (commit #f8b9b2f)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Close #248.
-
2007-10-18T13:25:21+02:00 (commit #e2194c6)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [1438].
-
2007-09-29T12:56:13+02:00 (commit #8feea89)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [1361].
-
2007-09-05T08:57:26+02:00 (commit #c23fcaa)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [1297].
-
2007-08-31T09:36:02+02:00 (commit #29a3311)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [1203].
-
2007-08-31T05:04:24+02:00 (commit #cb80905)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [1198].
-
2007-08-05T11:32:25+02:00 (commit #1e72ff1)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [953].
-
2007-08-05T10:34:30+02:00 (commit #9b48606)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [951].
-
2007-08-04T17:35:23+02:00 (commit #60f8f6c)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Merge [949].
-
2007-02-24T07:58:18+01:00 (commit #203ee10)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Fugbix typo.
-
2007-02-24T07:58:18+01:00 (commit #ae2a7c2)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Fugbix typo.
-
2006-12-24T18:50:40+01:00 (commit #0189be1)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Bump year.
-
2006-11-06T13:48:58+01:00 (commit #62ffb2d)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>More work on time.
-
2006-11-06T13:14:17+01:00 (commit #24d5d8d)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Unify timing code.
-
2006-09-26T07:05:52+02:00 (commit #13e035a)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Handle test suite names correctly that are not the name of a test case class.
-
2006-09-11T09:20:41+02:00 (commit #75e12fb)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>No longer needed.
-
2006-08-13T10:57:58+02:00 (commit #3cd6a25)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Whitespace fixes.
-
2006-07-06T11:50:42+02:00 (commit #dacd2f1)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Leftover: PHPUnit2 -> PHPUnit.
-
2006-06-30T10:38:41+02:00 (commit #210b621)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Make it easier to use a checkout of the trunk.
-
2006-06-29T20:56:08+02:00 (commit #6b0d2d5)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Post-PEAR cleanup, phase one: PHPUnit2_* -> PHPUnit_*, pear.php.net -> phpunit.de, etc.
-
2006-06-29T16:58:01+02:00 (commit #8b8c705)
Author: Sebastian Bergmann<EMAIL_ADDRESS>/ Commiter: Sebastian Bergmann<EMAIL_ADDRESS>Recreate trunk.


Draw a graph with the visualizer, then click the algorithm you'd like to perform on it.
For more options, you can also define your graph in test.js
Hold shift then mouse over two vertices to connect them with an edge.
Note: for the time being, the visualizer only builds undirected graphs with random weights


Note: Some exports may take a while
WhatsApp Group Contact Exporter is developed and maintained by codegena.com
For any complaints, queries or feedbacks, write to<EMAIL_ADDRESS>This is an unofficial enhancement for WhatsApp Web. WAXP do not promote any unethical activity, this is made just to automate and make work easier.


#include <db_cxx.h>int DbMpoolFile::get(db_pgno_t *pgnoaddr, u_int32_t flags, void **pagep);
The DbMpoolFile::get method copies a pointer to the page with the page number specified by pgnoaddr, from the source file in the DbMpoolFile, into the memory location referenced by pagep. If the page does not exist or cannot be retrieved, DbMpoolFile::get will fail.
Page numbers begin at 0, i.e., the first page in the file is page number 0, not page number 1.
The returned page is size_t type aligned.
The flags argument is specified by logically OR'ing together one or more of the following values:
The DB_MPOOL_CREATE, DB_MPOOL_LAST and DB_MPOOL_NEW flags are mutually exclusive.
Created pages have all their bytes set to 0, unless otherwise specified when the file was opened.
All pages returned by DbMpoolFile::get will be retained (i.e. pinned in the pool until a subsequent call to DbMpoolFile::put.
The DbMpoolFile::get method either returns errno or throws an exception that encapsulates an errno on failure, and 0 on success.
The DbMpoolFile::get method may fail and throw an exception for any of the errors specified for the following Berkeley DB and C library functions: DBmemp->pgin(3), DBmemp->pgout(3), abort(3), close(3), dbenv->db_paniccall(3), fcntl(3), fflush(3), fprintf(3), free(3), fstat(3), fsync(3), getenv(3), getpid(3), getuid(3), isdigit(3), DbLog::compare, DbLog::flush, lseek(3), malloc(3), memcmp(3), memcpy(3), memset(3), mmap(3), open(3), pread(3), pstat_getdynamic(3), pwrite(3), read(3), sigfillset(3), sigprocmask(3), stat(3), strerror(3), strlen(3), sysconf(3), time(3), unlink(3), vfprintf(3), vsnprintf(3), and write(3).
In addition, the DbMpoolFile::get method may fail and throw an exception or return errno for the following conditions:
The DB_MPOOL_NEW flag was set and the source file was not opened for writing.
The requested page does not exist and DB_MPOOL_CREATE was not set.
More than one of DB_MPOOL_CREATE, DB_MPOOL_LAST and DB_MPOOL_NEW was set.


Module bit
C library providing bitwise operations on fixed-sized bitfields implemented as Lua numbers.
Has consistent semantics across 16, 32 and 64 bit platforms as well as IEEE 754 doubles, int32t and int64t lua_Number.
Usages:
require("bit")
local bit = require("bit")
Type bit
| bit.arshift(x, n) |
arithmetic right-shift of x by n bits |
| bit.band(x1, x2, ...) |
bitwise and of x1, x2, ... |
| bit.bnot(x) |
bitwise not of x. |
| bit.bor(x1, x2, ...) |
bitwise or of x1, x2, ... |
| bit.bswap(x) |
byte-swap of x (little-endian <-> big-endian) |
| bit.bxor(x1, x2, ...) |
bitwise xor of x1, x2, ... |
| bit.lshift(x, n) |
left-shift of x by n bits |
| bit.rol(x, n) |
left-rotate of x by n bits |
| bit.ror(x, n) |
right-rotate of x by n bits |
| bit.rshift(x, n) |
logical right-shift of x by n bits |
| bit.tobit(x) |
Normalize number to the numeric range of bit operations (all bit ops use this implicitly) |
Type bit
Field(s)
- bit.arshift(x, n)
-
arithmetic right-shift of x by n bits
Parameters
-
#number x
: number to shift -
#number n
: number to shift by
Return value
#number: the shifted number
-
- bit.band(x1, x2, ...)
-
bitwise and of x1, x2, ...
Parameters
-
#number x1
: first number of the operation -
#number x2
: second number of the operation -
#number ...
: other numbers of the operation
Return value
#number: number as the result of the operation
-
- bit.bnot(x)
-
bitwise not of x.
Parameter
-
#number x
: number to perform operation on
Return value
#number: number as the result of the operation
-
- bit.bor(x1, x2, ...)
-
bitwise or of x1, x2, ...
Parameters
-
#number x1
: first number of the operation -
#number x2
: second number of the operation -
#number ...
: other numbers of the operation
Return value
#number: number as the result of the operation
-
- bit.bswap(x)
-
byte-swap of x (little-endian <-> big-endian)
Parameter
-
#number x
: number to swap
Return value
#number: the swaped number
-
- bit.bxor(x1, x2, ...)
-
bitwise xor of x1, x2, ...
Parameters
-
#number x1
: first number of the operation -
#number x2
: second number of the operation -
#number ...
: other numbers of the operation
Return value
#number: number as the result of the operation
-
- bit.lshift(x, n)
-
left-shift of x by n bits
Parameters
-
#number x
: number to shift -
#number n
: number to shift by
Return value
#number: the shifted number
-
- bit.rol(x, n)
-
left-rotate of x by n bits
Parameters
-
#number x
: number to rotate -
#number n
: number to rotate by
Return value
#number: the rotated number
-
- bit.ror(x, n)
-
right-rotate of x by n bits
Parameters
-
#number x
: number to rotate -
#number n
: number to rotate by
Return value
#number: the rotated number
-
- bit.rshift(x, n)
-
logical right-shift of x by n bits
Parameters
-
#number x
: number to shift -
#number n
: number to shift by
Return value
#number: the shifted number
-
- bit.tobit(x)
-
Normalize number to the numeric range of bit operations (all bit ops use this implicitly)
Parameter
-
#number x
: the number to normalize
Return value
#number: normalized number
-


SUBROUTINE DPTEQR( COMPZ, N, D, E, Z, LDZ, WORK, INFO ) * * -- LAPACK routine (version 3.1) -- * Univ. of Tennessee, Univ. of California Berkeley and NAG Ltd.. * November 2006 * * .. Scalar Arguments .. CHARACTER COMPZ INTEGER INFO, LDZ, N * .. * .. Array Arguments .. DOUBLE PRECISION D( * ), E( * ), WORK( * ), Z( LDZ, * ) * .. * * Purpose * ======= * * DPTEQR computes all eigenvalues and, optionally, eigenvectors of a * symmetric positive definite tridiagonal matrix by first factoring the * matrix using DPTTRF, and then calling DBDSQR to compute the singular * values of the bidiagonal factor. * * This routine computes the eigenvalues of the positive definite * tridiagonal matrix to high relative accuracy. This means that if the * eigenvalues range over many orders of magnitude in size, then the * small eigenvalues and corresponding eigenvectors will be computed * more accurately than, for example, with the standard QR method. * * The eigenvectors of a full or band symmetric positive definite matrix * can also be found if DSYTRD, DSPTRD, or DSBTRD has been used to * reduce this matrix to tridiagonal form. (The reduction to tridiagonal * form, however, may preclude the possibility of obtaining high * relative accuracy in the small eigenvalues of the original matrix, if * these eigenvalues range over many orders of magnitude.) * * Arguments * ========= * * COMPZ (input) CHARACTER*1 * = 'N': Compute eigenvalues only. * = 'V': Compute eigenvectors of original symmetric * matrix also. Array Z contains the orthogonal * matrix used to reduce the original matrix to * tridiagonal form. * = 'I': Compute eigenvectors of tridiagonal matrix also. * * N (input) INTEGER * The order of the matrix. N >= 0. * * D (input/output) DOUBLE PRECISION array, dimension (N) * On entry, the n diagonal elements of the tridiagonal * matrix. * On normal exit, D contains the eigenvalues, in descending * order. * * E (input/output) DOUBLE PRECISION array, dimension (N-1) * On entry, the (n-1) subdiagonal elements of the tridiagonal * matrix. * On exit, E has been destroyed. * * Z (input/output) DOUBLE PRECISION array, dimension (LDZ, N) * On entry, if COMPZ = 'V', the orthogonal matrix used in the * reduction to tridiagonal form. * On exit, if COMPZ = 'V', the orthonormal eigenvectors of the * original symmetric matrix; * if COMPZ = 'I', the orthonormal eigenvectors of the * tridiagonal matrix. * If INFO > 0 on exit, Z contains the eigenvectors associated * with only the stored eigenvalues. * If COMPZ = 'N', then Z is not referenced. * * LDZ (input) INTEGER * The leading dimension of the array Z. LDZ >= 1, and if * COMPZ = 'V' or 'I', LDZ >= max(1,N). * * WORK (workspace) DOUBLE PRECISION array, dimension (4*N) * * INFO (output) INTEGER * = 0: successful exit. * < 0: if INFO = -i, the i-th argument had an illegal value. * > 0: if INFO = i, and i is: * <= N the Cholesky factorization of the matrix could * not be performed because the i-th principal minor * was not positive definite. * > N the SVD algorithm failed to converge; * if INFO = N+i, i off-diagonal elements of the * bidiagonal factor did not converge to zero. * * ===================================================================== * * .. Parameters .. DOUBLE PRECISION ZERO, ONE PARAMETER ( ZERO = 0.0D0, ONE = 1.0D0 ) * .. * .. External Functions .. LOGICAL LSAME EXTERNAL LSAME * .. * .. External Subroutines .. EXTERNAL DBDSQR, DLASET, DPTTRF, XERBLA * .. * .. Local Arrays .. DOUBLE PRECISION C( 1, 1 ), VT( 1, 1 ) * .. * .. Local Scalars .. INTEGER I, ICOMPZ, NRU * .. * .. Intrinsic Functions .. INTRINSIC MAX, SQRT * .. * .. Executable Statements .. * * Test the input parameters. * INFO = 0 * IF( LSAME( COMPZ, 'N' ) ) THEN ICOMPZ = 0 ELSE IF( LSAME( COMPZ, 'V' ) ) THEN ICOMPZ = 1 ELSE IF( LSAME( COMPZ, 'I' ) ) THEN ICOMPZ = 2 ELSE ICOMPZ = -1 END IF IF( ICOMPZ.LT.0 ) THEN INFO = -1 ELSE IF( N.LT.0 ) THEN INFO = -2 ELSE IF( ( LDZ.LT.1 ) .OR. ( ICOMPZ.GT.0 .AND. LDZ.LT.MAX( 1, $ N ) ) ) THEN INFO = -6 END IF IF( INFO.NE.0 ) THEN CALL XERBLA( 'DPTEQR', -INFO ) RETURN END IF * * Quick return if possible * IF( N.EQ.0 ) $ RETURN * IF( N.EQ.1 ) THEN IF( ICOMPZ.GT.0 ) $ Z( 1, 1 ) = ONE RETURN END IF IF( ICOMPZ.EQ.2 ) $ CALL DLASET( 'Full', N, N, ZERO, ONE, Z, LDZ ) * * Call DPTTRF to factor the matrix. * CALL DPTTRF( N, D, E, INFO ) IF( INFO.NE.0 ) $ RETURN DO 10 I = 1, N D( I ) = SQRT( D( I ) ) 10 CONTINUE DO 20 I = 1, N - 1 E( I ) = E( I )*D( I ) 20 CONTINUE * * Call DBDSQR to compute the singular values/vectors of the * bidiagonal factor. * IF( ICOMPZ.GT.0 ) THEN NRU = N ELSE NRU = 0 END IF CALL DBDSQR( 'Lower', N, 0, NRU, 0, D, E, VT, 1, Z, LDZ, C, 1, $ WORK, INFO ) * * Square the singular values. * IF( INFO.EQ.0 ) THEN DO 30 I = 1, N D( I ) = D( I )*D( I ) 30 CONTINUE ELSE INFO = N + INFO END IF * RETURN * * End of DPTEQR * END


Welcome
Projects
Contact Me
Hi! I am
Jesse
Full Stack Web Developer
Projects
Product Landing Page
Survey Form Page
Technical Documentation Page
Contact me
GitHub


本书pdf是文字版。
1.1 Historical Background
1.2 Preparative Methods
1.3 Physical Properties
1.4 Degradation Mechanisms
1.5 Beyond Classical Poly(Hydroxycarboxylic Acids)
2.1 Introduction
2.2 History
2.3 Polyhydroxyalkanoates – Granules Morphology
2.4 Biosynthesis and Biodegradability of Poly(3-Hydroxybutyrate) and Other Polyhydroxyalkanoates
2.5 Extraction and Recovery
2.6 Physical, Mechanical, and Thermal Properties of Polyhydroxyalkanoates
2.7 Future Directions
3.1 Introduction
3.2 Types of Polyanhydride
3.3 Synthesis
3.4 Properties
3.5 In Vitro Degradation and Erosion of Polyanhydrides
3.6 In Vivo Degradation and Elimination of Polyanhydrides
3.7 Toxicological Aspects of Polyanhydrides
3.8 Fabrication of Delivery Systems
3.9 Production and World Market
3.10 Biomedical Applications
4.1 Introduction
4.2 POE II
4.3 POE IV
4.4 Solid Polymers
4.5 Gel-Like Materials
4.6 Polymers Based on an Alternate Diketene Acetal
4.7 Conclusions
5.1 Introduction
5.2 Amino Acid-Based Biodegradable Polymers (AABBPs)
5.3 Conclusion and Perspectives
6.1 Chemistry and Properties of Biodegradable Polyurethanes
6.2 Biodegradation Mechanisms of Polyurethanes
6.3 Applications of Biodegradable Polyurethanes
6.4 New Polymerization Trends to Obtain Degradable Polyurethanes
6.5 Aliphatic Poly(ester amide)s: A Family of Biodegradable Thermoplastics with Interest as New Biomaterials
7.1 Introduction
7.2 Alginate
7.3 Carrageenan
7.4 Cellulose and Its Derivatives
7.5 Microbial Cellulose
7.6 Chitin and Chitosan
7.7 Dextran
7.8 Gellan
7.9 Guar Gum
7.10 Hyaluronic Acid (Hyaluronan)
7.11 Pullulan
7.12 Scleroglucan
7.13 Xanthan
7.14 Summary
8.1 Introduction
8.2 General Concept of SMPs
8.3 Classes of Degradable SMPs
8.4 Applications of Biodegradable SMPs
9.1 Introduction
9.2 Synthesis of Elastic Hydrogels
9.3 Physical Properties of Elastic Hydrogels
9.4 Applications of Elastic Hydrogels
9.5 Elastic Hydrogels for Tissue Expander Applications
9.6 Conclusion
10.1 Introduction
10.2 Challenges for Designing Biodegradable Dendrimers
10.3 Design of Self-Immolative Biodegradable Dendrimers
10.4 Biological Implications of Biodegradable Dendrimers
10.5 Future Perspectives of Biodegradable Dendrimers
10.6 Concluding Remarks
11.1 Introduction
11.2 Some Background
11.3 Defi ning Biodegradability
11.4 Mechanisms of Polymer Degradation
11.5 Measuring Biodegradation of Polymers
11.6 Conclusions
12.1 Introduction
12.2 Analysis of Exogenous Depolymerization
12.3 Materials and Methods
12.4 Analysis of Endogenous Depolymerization
12.5 Discussion
13.1 Introduction
13.2 Regenerative Medicine for the Reconstruction of the Upper Aerodigestive Tract
13.3 Methods and Novel Therapeutical Options in Head and Neck Surgery
13.4 Vascularization of Tissue-Engineered Constructs
13.5 Application of Stem Cells in Regenerative Medicine
13.6 Conclusion
14.1 Introduction
14.2 Short Overview of Regenerative Biology
14.3 Minimum Requirements for Tissue Engineering
14.4 Structure of Scaffolds
14.5 Biodegradable Polymers for Tissue Engineering
14.6 Some Examples for Clinical Application of Scaffold
14.7 Conclusions
15.1 Introduction
15.2 The Clinical Need for Drug Delivery Systems
15.3 Poly(α-Hydroxyl Acids)
15.4 Polyanhydrides
15.5 Manufacturing Routes
15.6 Examples of Biodegradable Polymer Drug Delivery Systems Under Development
15.7 Concluding Remarks
16.1 Introduction
16.2 Controlled – Lifetime Plastics
16.3 The Abiotic Oxidation of Polyolefins
16.4 Enhanced Oxo-biodegradation of Polyolefins
16.5 Processability and Recovery of Oxo-biodegradable Polyolefins
16.6 Concluding Remarks


Toggle navigation
$
1 Traveler
Mood?
Hot & Sunny
City & Buzzy
Beach
Weekend Getaway
Good for kids
Rent a car?
Email
Go!
Tote discovers your ideal vacation or weekend getaway.
Adults
Kids


*General Usage
The images produced will be shown with a limit of 1000px by 1000px but can be saved, with the maximum limit which is 5000px by 5000px.
Use the option in the context of the right to save as an image.
With the dimensions set, you generate a QR code. With each new QR code generated, it takes the values of width and height, so changing values and clicking you can generate QR's with different sizes.
Use the option in the context of the right to save as an image.
With the dimensions set, you generate a QR code. With each new QR code generated, it takes the values of width and height, so changing values and clicking you can generate QR's with different sizes.
*Qr URL
To generate a QR with the value of a URL, put the value similar to the example below.
Example: http://www.google.com or https://mail.google.com
Example: http://www.google.com or https://mail.google.com
*Qr Text
To generate a QR with the value of a Text, put the value similar to the example below.
Example: Hello World
Example: Hello World
*Qr iTunes
In progress...
*Qr Contact
To generate a QR with the value of address book in your phone , put the value similar to the example below.
Example:
Example:
Name: Flap Last Name: Jack Phone: 5550123 Email<EMAIL_ADDRESS>Address: Road to nowhere, World of Cartoons - 0000000


Get Started
Learn how to configure set up Piku in your server and configure it to run your applications.
Installation
To use piku you need a VPS, Raspberry Pi, or other server bootstrapped with piku's requirements. You can use a single server to run multiple piku apps. Warning: You should use a fresh server or VPS instance without anything important running on it already, as piku-bootstrap will make changes to configuration files, running services, etc. Once you've got a fresh server, download the piku-bootstrap shell script onto your local machine and run it:
piku@jmatrix:curl https://piku.github.io/get | sh
jmatrix@jmatrix:./piku-bootstrap piku@jmatrix
Installing Other Dependencies
piku-bootstrap uses Ansible internally and it comes with several extra built-in playbooks which you can use to bootstrap common components onto your piku server.
Use piku-bootstrap list-playbooks to show a list of built-in playbooks, and then to install one add it as an argument to the bootstrap command.
For example, to deploy nodeenv onto your server:
jmatrix@jmatrix:piku-bootstrap piku@jmatrix nodeenv.yml
jmatrix@jmatrix:piku-bootstrap piku@jmatrix ./myplaybook.yml
Using Piku
Piku supports a Heroku-like workflow, like so:
1. Create a git SSH remote pointing to your piku server with the app name as repo name. git remote add piku piku@yourserver:appname.
2. Push your code: git push piku master.
3. piku determines the runtime and installs the dependencies for your app (building whatever's required).
- For Python, it segregates each app's dependencies into a virtualenv.
- For Go, it defines a separate GOPATH for each app.
- For Node, it installs whatever is in package.json into node_modules.
- For Java, it builds your app depending on either pom.xml or build.gradle file.
4. It then looks at a Procfile which is documented here and starts the relevant workers using uWSGI as a generic process manager.
5. You can optionally also specify a release worker which is run once when the app is deployed.
6. You can then remotely change application settings (config:set) or scale up/down worker processes (ps:scale).
7. You can also bake application settings into a file called ENV which is documented here.
8. A static worker type, with the root path as the argument, can be used to deploy a gh-pages style static site.
Piku Client
To make life easier you can also install the piku helper CLI. Install it into your path e.g. ~/bin to run it from anywhere.
./piku-bootstrap install-cli ~/bin
$ piku logs
$ piku config:set MYVAR=12
$ piku stop
$ piku deploy
$ piku destroy
$ piku # <- will show help for the remote app
$ piku -t run bash
Piku remote operator.
Server<EMAIL_ADDRESS>piku@piku:~/.piku/apps/dashboard$ ls
data ENV index.html package.json package-lock.json Procfile server.wisp
Procfiles and ENVs
An app is simply a git repository with some additional files on the top level, the most important of which is the Procfile.
Procfile format
Piku recognizes three kinds of process declarations in the Procfile:
A) wsgi workers, in the format dotted.module:entry_point (Python-only)
B) web workers, which can be anything that honors the PORT environment variable
C) static workers, which simply mount the first argument as the root static path
D) worker processes, which are standalone workers and can have arbitrary names
So a Python application could have a Procfile like such:
wsgi: module.submodule:app
worker: python long_running_script.py
fetcher: python fetcher.py
web: embedded_server --port $PORT
worker: background_worker
ENV settings
Since piku is targeted at 12 Factor apps, it allows you to set environment variables in a number of ways, the simplest of which is by adding an ENV file to your repository:
SETTING1=foo
# piku supports comments and variable expansion
SETTING2=${SETTING1}/bar
# if this isn't defined, piku will assign a random TCP port
PORT=9080
Issues and Contributions
If you encounter issues while using Piku please submit the issue report on Piku's github section.
If you wish to contribute, fork the main Piku Repo and create a pull request.


Junior Software architect
IMIE, March '17 - September '18
Angers
Online brand protection
DNS Management
ISO 27001 certificated
v4 : 32bits encoded, 232 addresses => (~4,269×109)
v6 : 128bits encoded, 2128 addresses => (~3,403×1038)
A network is composed of redundant nodes
Response is given by the most efficient node of the group
Can only be broken if the real address of a node is known by black hats
Used by telecommunications and SAR units, to dispatch informations to all people within a defined area
Natural disasters prevention
Earthquake messaging in Japan
.arpa
.app
, .gov
, .museum
, .xxx
, ....cat
, .asia
, .paris
, .amazon
, ....men
, .loan
, .sncf
, .loreal
, ....fr
, .re
, .tv
, .io
, ....شبكة.
, .游戏
, .онлайн
1 TLD = 1 Registry
1 Registry = Many registrars
Registry : TLD owner (ex: AFNIC for .fr)
Registrar : TLD reseller (ex: Nameshield, Ovh ...)
1 host name, for multiple records
Round robin principle
Applying a standard lifecycle workflow for all projects
One system to ease data manipulation
... whatever the storage / source
Repository
none
Project Leader at Agena3000 Monitoring IS for


{% import<EMAIL_ADDRESS>as TestHead %} {% import<EMAIL_ADDRESS>as TestHeader %} {% import<EMAIL_ADDRESS>as Test %} {{ TestHead.utility( 'layout' ) }}
{{ TestHeader.utility( 'layout' ) }} {% include "flex.html" %} {% include "margin.html" %} {% include "padding.html" %} {% include "borders.html" %} {% include "width-height.html" %} {% include "before.html" %} {% include "after.html" %}


Hi, Stuck in the middle of something?
BackSlash Linux and team is here to help you out.
Connect with an Advisor Right Now
* Requires active internet connection


--- layout: post title: XPath tools and info tags: [] status: publish type: post published: true meta: {} ---
For posterity I came across this post on CFCDev when dealing with an xPath issue:
Tools:
http://sourceforge.net/projects/xpe/ - Xpath Explorer
http://www.topxml.com/xpathvisualizer/ - The XPath Visualizer Version 1.4
Tutorials
http://www.w3schools.com/xpath/default.asp - W3Schools XPath Tutorial
http://www.topxml.com/xsl/default.asp - Learn XSL & XPath Tutorial
Book
http://www.oreilly.com/catalog/xpathpointer/ - XPath and XPointer


I write code and produce music for fun; this is where I display some of the projects I'm most proud of. I currently work as a software engineer at Facebook in New York.