Our marketing department wants to allow users of our app to capture images, and position Knowzy products over the image to see how they would look. It's a fun way to try the product without actually buying it. The marketing department is hoping that these images will be shared on social media to spread the word.
Goals for this task: Overlay noses on top of an image and allow nose to be manipulated. Support inking on UWP devices.
For this task, you will need to access APIs that are specific to each platform. We've done the research on how to do it and have included the steps below.
This task has a dependency on Task 3.1.2 and all of it's prerequisites.
Once the image is captured, let's add the nose image on top of it, and allow the user to move it by panning and resize it by pinching.
Open the XAML page that you added in the previous task (CameraPage.xaml in this example).
Add code that does these things:
Wraps the image element that hosts the camera image into a new Grid element.
This will allow you to position multiple elements on top of each other.
Adds a new AbsoluteLayout element below the existing Image in the grid.
Adds a new Image element inside of the AbsoluteLayout element, which will be used to host the nose image.
Here is what the final result should look like:
Before:
<Image x:Name="image"></Image>
After:
<Grid x:Name="imageGrid" IsVisible="False">
<Image x:Name="image"></Image>
<AbsoluteLayout>
<Image x:Name="noseImage"
HeightRequest="120"
WidthRequest="120"
AbsoluteLayout.LayoutBounds="0, 0, AutoSize, AutoSize"
AbsoluteLayout.LayoutFlags="None">
</Image>
</AbsoluteLayout>
</Grid>
Notice that in the XAML, we've set the visibility of the Grid to False. Once the image has been captured, we can set the visibility to True, and then set the source of the noseImage element. Make those changes in the captureButton_Clicked event handler. When you're done, your code should look something like this:
private async void captureButton_Clicked(object sender, EventArgs e)
{
var photoService = DependencyService.Get<IPhotoService>();
if (photoService != null)
{
var imageBytes = await photoService.TakePhotoAsync();
noseImage.Source = ImageSource.FromUri(new Uri(_nose.Image)); // set source of nose image
image.Source = ImageSource.FromStream(() => new MemoryStream(imageBytes));
imageGrid.IsVisible = true; // set visibility to true
}
}
To allow elements to be manipulated by panning or pinching, Xamarin.Forms has built in Gestures. Inside of the the noseImage element that we just added to our page, let's add a new PanGestureRecognizer and a new PinchGestureRecognizer, which will subscribe to the relevant events so we can manipulate the nose image with gestures:
<Image x:Name="noseImage"
HeightRequest="120"
WidthRequest="120"
AbsoluteLayout.LayoutBounds="0, 0, AutoSize, AutoSize"
AbsoluteLayout.LayoutFlags="None">
<!-- Gesture Recognizers -->
<Image.GestureRecognizers>
<PanGestureRecognizer PanUpdated="OnPanUpdated" />
<PinchGestureRecognizer PinchUpdated="OnPinchUpdated" />
</Image.GestureRecognizers>
</Image>
In your code-behind file (CameraPage.xaml.cs in this example), implement the event handlers for the gestures that we just added. The nose moves with the finger or mouse, and the scale of the image changes when the image is pinched:
private void OnPanUpdated(object sender, PanUpdatedEventArgs e)
{
switch (e.StatusType)
{
case GestureStatus.Started:
var bounds = AbsoluteLayout.GetLayoutBounds(noseImage);
bounds.X += noseImage.TranslationX;
bounds.Y += noseImage.TranslationY;
AbsoluteLayout.SetLayoutBounds(noseImage, bounds);
noseImage.TranslationX = 0;
noseImage.TranslationY = 0;
break;
case GestureStatus.Running:
noseImage.TranslationX = e.TotalX;
noseImage.TranslationY = e.TotalY;
break;
}
}
private void OnPinchUpdated(object sender, PinchGestureUpdatedEventArgs e)
{
switch (e.Status)
{
case GestureStatus.Running:
noseImage.Scale *= e.Scale;
break;
}
}
That's it. Run the app, take a photo, position the nose, and have fun.
In addition to using the built in Xamarin.Forms controls, developers have full access to native platform controls through native view declaration. This allows developers to use native or custom controls (such as the UWP Community Toolkit), and mix them with Xamarin.Forms controls directly in XAML. For our app, we can use the native InkCanvas control and InkToolbar control when the app runs on UWP.
To make native views consumable via XAML, add XML namespaces for each platform we'll be embedding views from.
We'll add the namespace for the UWP native controls as part of the ContentPage declaration that we created in the previous task (CameraPage in our example):
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms"
xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
x:Class="App1.CameraPage"
xmlns:win="clr-namespace:Windows.UI.Xaml.Controls;assembly=Windows,
Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null,
ContentType=WindowsRuntime;targetPlatform=Windows"
>
We can now add two UWP XAML controls directly to the page.
<StackLayout VerticalOptions="FillAndExpand"
HorizontalOptions="FillAndExpand"
Orientation="Vertical"
Spacing="15">
<Button x:Name="captureButton"
Text="Capture Image"
Clicked="captureButton_Clicked"></Button>
<!-- UWP XAML CONTROL InkToolbar -->
<ContentView x:Name="InkingToolbar">
<win:InkToolbar></win:InkToolbar>
</ContentView>
<Grid x:Name="ImageGrid" IsVisible="False">
<Image x:Name="image"></Image>
<!-- UWP XAML CONTROL InkCanvas -->
<ContentView x:Name="InkingContent">
<win:InkCanvas></win:InkCanvas>
</ContentView>
<AbsoluteLayout>
<!-- ... -->
</AbsoluteLayout>
</Grid>
</StackLayout>
Note: It is not possible to name native views, so we use a ContentView as a way to get a reference to the native views in our code-behind file.
To use the native views in the code behind, we need to use compilation directives, as the native views will only be used on the platform in which they are available. In this case, the InkCanvas and InkToolbar are only available on UWP, so we need to use the WINDOWS_UWP directive to wrap our code.
In the constructor of our page, after the call to InitializeComponent, we need to bind the InkToolbar to the InkCanvas, and then set the input device type of the InkCanvas to all input types:
#if WINDOWS_UWP
var inkingWrapper = (Xamarin.Forms.Platform.UWP.NativeViewWrapper)InkingContent.Content;
var inkCanvas = (Windows.UI.Xaml.Controls.InkCanvas)inkingWrapper.NativeElement;
inkCanvas.InkPresenter.InputDeviceTypes =
Windows.UI.Core.CoreInputDeviceTypes.Touch |
Windows.UI.Core.CoreInputDeviceTypes.Mouse |
Windows.UI.Core.CoreInputDeviceTypes.Pen;
var inkToolbarWrapper = (Xamarin.Forms.Platform.UWP.NativeViewWrapper)InkingToolbar.Content;
var inkToolbar = (Windows.UI.Xaml.Controls.InkToolbar)inkToolbarWrapper.NativeElement;
inkToolbar.TargetInkCanvas = inkCanvas;
#endif
If you run into a null reference exception, check to see if the following line is added above your page class definition:
[XamlCompilation(XamlCompilationOptions.Compile)]
Xamarin adds this line to any new page created to improve the performance of XAML pages. However, this optimization will not work when using native views and needs to be deleted.
And you're done! Run the app and draw the perfect masterpiece. You should now be able to start the app, select a nose, capture an image, position the nose where you want, and on UWP, draw using the pen, mouse or touch.
Congratulations, you are now done with the first deliverable. You should now be able to take control and start adding more features on your own. Take a look at the other deliverables and tasks for ideas and small hints about how to implement other features that would be useful for our users.


{# Copyright 2023 Google LLC Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. #} {%- extends BASE_HTML -%} {% set main_id = 'screenshot' %} {% set page_id = 'page-screenshot-commit' %} {% set title = 'Screenshot Commit Page' %} {% block head %} {% endblock %} {% block content %}


SweetFreeStuff.com
///////////////////////////////////////////
Free Maxboost Vibrance iPhone 6 Case
Posted: 23 Dec 2014 09:39 AM PST
http://feedproxy.google.com/&edburner&utm_medium=email
Complete the form. You will need to have an Amazon account. After reviewing
all submissions they will contact those who qualified to receive a free
case. Free Maxboost Vibrance iPhone 6 Case
The post Free Maxboost Vibrance iPhone 6 Case appeared first on
SweetFreeStuff.com.
///////////////////////////////////////////
Free Michael Bubl Christmas MP3 Album Download on Google Play
Posted: 23 Dec 2014 09:31 AM PST
http://feedproxy.google.com/&edburner&utm_medium=email
Free Michael Bublé Christmas MP3 Album Download on Google Play
The post Free Michael Bublé Christmas MP3 Album Download on Google Play
appeared first on SweetFreeStuff.com.
///////////////////////////////////////////
Free Subscription to Siempre Mujer
Posted: 23 Dec 2014 03:25 AM PST
http://feedproxy.google.com/&edburner&utm_medium=email
Free Subscription to Siempre Mujer Magazine
The post Free Subscription to Siempre Mujer appeared first on
SweetFreeStuff.com.
///////////////////////////////////////////
Free Natures Bounty Hair, Skin & Nails Gummies Sample
Posted: 22 Dec 2014 09:01 PM PST
http://feedproxy.google.com/&edburner&utm_medium=email
FREE sample by mail from Target.com. Free Natures Bounty Hair, Skin Nails
Gummies Sample
The post Free Natures Bounty Hair, Skin Nails Gummies Sample appeared
first on SweetFreeStuff.com.


new Server(conf)
Constructor of server
Parameters:
| Name | Type | Description |
|---|---|---|
conf |
Object | configuration (console options) |
- Source:
Members
-
htmlFiles :string[]
-
the GUI's HTML files
Type:
- string[]
- Source:
Methods
-
init()
-
Initialise the servers (BuildServer and UIServer and bind the sockets (Agent, Client, WWW) and begin reading the previous builds afterwards
- Source:
-
initCache() → {Cache}
-
Instantiate new Cache object, add html files and reload on updates
- Source:
Returns:
cache object- Type
- Cache
-
readPreviousBuilds(err, builds)
-
Reads + parses the found builds and stores the generated Build objects
Parameters:
Name Type Argument Description err
Object <optional>
error object (globbing failed) or null builds
Object array of found build.json files - Source:
-
stop()
-
Clear the processQueue interval, close the socket and exit the process
- Source:


A simple Python implementation of quartet-tree inference using the method of phylogenetic invariants.


Horrified family receive Iceland pizza 'covered in black mould'
A family has been ‘put off’ shopping at Iceland again after receiving a pizza covered in black mould.
Kim Bann says her niece ordered the Iceland own-brand Deep Pan Double Pepperoni pizza from the Selsdon branch last Friday.
However, Kim got a shock when she found ‘disgusting’ black mould ‘all the way round it’ when she opened it for her daughter’s lunch.
Kim said: ‘This is meant to be a double pepperoni pizza but it’s all black mould all the way round it
‘Absolutely disgusting.’
The family claim to have been offered a refund for the pizza which normally costs £1.
However, they say this is ‘appalling’ customer service, given the shock they experienced.
Kim said: ‘I would have thought that they would least give her a voucher to coax her back to shopping there.
Advertisement Advertisement
‘It’s actually put her off shopping there now as well as me.’
Iceland confirmed to The Sun they had been contacted on social media by Kim and her niece.
However, they said they were waiting for the account holder to speak to them directly so they can investigate further.
A spokesperson said: ‘At Iceland, we pride ourselves on both the quality of our food and the quality of our service. On this occasion, our customer has clearly not received this usual high standard of experience.
‘We are very keen to look into this matter further and to ensure that this customer feels valued and understands that she is important she is to Iceland.’
Metro.co.uk has contacted Iceland for further comment.
Got a story for Metro.co.uk?
Get in touch with our news team by emailing us at<EMAIL_ADDRESS>For more stories like this, check our news page.


China cables: 'Don't listen to fake news' about Xinjiang camps, says Chinese ambassador – video
by BBC PanoramaThese were the words of China's ambassador to the UK, Liu Xiaoming, after he was asked about a chain of detention camps holding more than a million people from the country's Muslim minority population in Xinjiang. The footage, due to be broadcast by BBC Panorama on Monday evening, was recorded prior to publication of the China Cables, a leak of what appear to be classified documents from within the Communist party. The BBC's Richard Bilton asked Liu to tell him the truth about these camps. The ambassador responded: 'There's no so-called labour camps, they are what we call vocational, education and training centres. They are there for the prevention of terrorists'
'Don't listen to fake news': Chinese ambassador pressed over detention camps in Xinjiang – video
Read the Guardian's coverage of the China cables:


Functional Iterator Painter (
explain?
)
(
,
)
(
,
)
(
,
)
Save
ReColor
ReDraw
Stop
(
,
)
Function:
x ← g(x,y) =
y ← h(x,y) =
Convergence Limit:
Divergence Limit:
Canvas Width:
Canvas Height:


Peedy's Pizza Palace
id = MicrosoftSpeechRecognitionDownload>
Pick A Style...
Traditional Cheese
Hawaiian
Chicago
New York
Seattle
The Works
Pick a Topping...
Pepperoni
Onions
Pineapple
Salmon
Anchovies
Canadian Bacon
Order Now!
The cost for a Pizza is $10.00
Each additional topping is $2.00
Total =


That project name has already been taken. Try another one.
You cannot include {{ projectNameLastKeyIllegal }} in project names.
We are updating our systems and need you to choose a new username. Don't use your real name!
This username is already taken. Please try another username.You cannot include {{ migrateUsernameKeyIllegal }} in usernames.
Log In
No account with this username or email exists. Please try to sign up for an account.Invalid email address. Please try again.We have no record of this username.


template<size_t cn>
Sample_ class
A class that provides unified access to image samples.
| Template parameters | |
|---|---|
| cn | The number of channels of the sample. |
Contents
This class directly inherits from Sample
and provides the same semantics. It is designed for cases, where the number of channels of a sample is known at compile time. For example, UV maps allways require a set of 2 channels. In such cases, the template can be used to efficiently pre-allocate memory.
Base classes
- class Sample
- A class that provides unified access to image samples.
Public types
-
using SampleType = Sample_
<cn> - Defines a type for a
Sample
with a certain number of channels. - using Texel = cv::Vec<float, cn>
- Defines a type for a texel with a certain number of channels.
Constructors, destructors, conversion operators
Public functions
-
template<size_t _cn>void extract(const int* fromTo, const size_t pairs, Sample_
<_cn>& sample) const - Maps a subset of channels from the current sample to another sample.
-
template<size_t _cn>void extract(const std::vector<int>& fromTo, Sample_
<_cn>& sample) const - Maps a subset of channels from the current sample to another sample.
-
template<size_t _cn>void map(const int* fromTo, const size_t pairs, const Sample_
<_cn>& sample) deprecated - Maps a subset of channels from the current sample to another sample.
-
template<size_t _cn>void map(const std::vector<int>& fromTo, const Sample_
<_cn>& sample) deprecated - Maps a subset of channels from the current sample to another sample.
-
template<size_t _sk>void getNeighborhood(const int x, const int y, cv::Vec<float, _sk*cn>& v, const bool weight = false) const
- Returns the neighborhood of a texel.
-
template<size_t _sk>void getNeighborhood(const cv::Point& p, cv::Vec<float, _sk*cn>& v, const bool weight = false) const
- Returns the neighborhood of a texel.
Function documentation
template<size_t cn>
template<size_t _cn>
void Texturize:: Sample_<cn>:: extract(const int* fromTo,
const size_t pairs,
Sample_ <_cn>& sample) const
Maps a subset of channels from the current sample to another sample.
| Template parameters | |
|---|---|
| _cn | The number of channels of the target sample. |
| Parameters | |
| fromTo | A pointer to an array of channel indices, containing a set of pairs that identify a mapping between the channels. |
| pairs | The number of pairs within the fromTo array. |
| sample | The sample to map the channels to. |
The fromTo
array must contain a even number of values, where each pair identifies the source and target index of the channel mapping.
template<size_t cn>
template<size_t _cn>
void Texturize:: Sample_<cn>:: extract(const std::vector<int>& fromTo,
Sample_ <_cn>& sample) const
Maps a subset of channels from the current sample to another sample.
| Template parameters | |
|---|---|
| _cn | The number of channels of the target sample. |
| Parameters | |
| fromTo | An array of channel indices, containing a set of pairs that identify a mapping between the channels. |
| sample | The sample to map the channels to. |
The fromTo
array must contain a even number of values, where each pair identifies the source and target index of the channel mapping.
template<size_t cn>
template<size_t _cn>
void Texturize:: Sample_<cn>:: map(const int* fromTo,
const size_t pairs,
const Sample_ <_cn>& sample)
Maps a subset of channels from the current sample to another sample.
| Template parameters | |
|---|---|
| _cn | The number of channels of the target sample. |
| Parameters | |
| fromTo | A pointer to an array of channel indices, containing a set of pairs that identify a mapping between the channels. |
| pairs | The number of pairs within the fromTo array. |
| sample | The sample to map the channels to. |
The fromTo
array must contain a even number of values, where each pair identifies the source and target index of the channel mapping.
template<size_t cn>
template<size_t _cn>
void Texturize:: Sample_<cn>:: map(const std::vector<int>& fromTo,
const Sample_ <_cn>& sample)
Maps a subset of channels from the current sample to another sample.
| Template parameters | |
|---|---|
| _cn | The number of channels of the target sample. |
| Parameters | |
| fromTo | An array of channel indices, containing a set of pairs that identify a mapping between the channels. |
| sample | The sample to map the channels to. |
The fromTo
array must contain a even number of values, where each pair identifies the source and target index of the channel mapping.
template<size_t cn>
template<size_t _sk>
void Texturize:: Sample_<cn>:: getNeighborhood(const int x,
const int y,
cv::Vec<float, _sk*cn>& v,
const bool weight = false) const
Returns the neighborhood of a texel.
| Template parameters | |
|---|---|
| _sk | The size of the neighborhood window. Must be an odd value. |
| Parameters | |
| x | The x coordinate of the texel. |
| y | the y coordinate of the texel. |
| v | The buffer to copy the neighborhood to. |
| weight | A boolean value that toggles gaussian weighting of neighborhood values, depending on the distance to the texel identified by the provided coordinates. |
If the pixel coordinates address a texel at the border of the sample, the method will automatically wrap the coordinates. Other border modes are currently unsupported. The result texel v
is a high-dimensional vector, that contains all neighborhood values in row-major order. If the sample has multiple channels, all channels are copied, before moving to the next pixel.
template<size_t cn>
template<size_t _sk>
void Texturize:: Sample_<cn>:: getNeighborhood(const cv::Point& p,
cv::Vec<float, _sk*cn>& v,
const bool weight = false) const
Returns the neighborhood of a texel.
| Template parameters | |
|---|---|
| _sk | The size of the neighborhood window. Must be an odd value. |
| Parameters | |
| p | The x and y coordinates of the texel. |
| v | The buffer to copy the neighborhood to. |
| weight | A boolean value that toggles gaussian weighting of neighborhood values, depending on the distance to the texel identified by the provided coordinates. |
If the pixel coordinates address a texel at the border of the sample, the method will automatically wrap the coordinates. Other border modes are currently unsupported. The result texel v
is a high-dimensional vector, that contains all neighborhood values in row-major order. If the sample has multiple channels, all channels are copied, before moving to the next pixel.


Ronald P. Matonti | Facebook
. Support flying Gold Star Flags on Memorial Day, Honor our Fallen Soldiers, Support . Act on Poverty, Florida AFL CIO, Stonewall Democrats of Pinellas County, . Jeffrey Miron, Honolulu Star-Advertiser, The U.S. Senate: Attend the briefing on . Disabled American Veterans, Chapter 15, New Ulm, Minnesota, Disabled .
http://www.facebook.com/matonti2
Treatment for Herniated or Bulging Discs
Tampa Homeowners Association Management, Property ...
Sentry Management provides operational leadership to homeowner and . in Pasco County and portions of Hillsborough, Pinellas and Hernando counties, .
http://www.sentrymgt.com/hoa-condo-management-tampa-wesley-chapel-fl
Ronald P. Matonti | Facebook
. Support flying Gold Star Flags on Memorial Day, Honor our Fallen Soldiers, Support . Act on Poverty, Florida AFL CIO, Stonewall Democrats of Pinellas County, . Jeffrey Miron, Honolulu Star-Advertiser, The U.S. Senate: Attend the briefing on . Disabled American Veterans, Chapter 15, New Ulm, Minnesota, Disabled .
http://www.facebook.com/matonti2
jeffrey ulm goldstar management pinellas Herniated or Bulging Discs
Tampa Homeowners Association Management, Property ...
Sentry Management provides operational leadership to homeowner and . in Pasco County and portions of Hillsborough, Pinellas and Hernando counties, .
http://www.sentrymgt.com/hoa-condo-management-tampa-wesley-chapel-fl
DCA | Link Disclaimer
You are about to leave the GQGP website. The links to other web sites are included when the content of those sites are judged to be suitable or helpful.
http://www.dca.state.ga.us/OITDSShared/asp/NavDisclaimer.asp?Leaving=GQGP
Tampa Homeowners Association Management, Property ...
Sentry Management provides operational leadership to homeowner and . in Pasco County and portions of Hillsborough, Pinellas and Hernando counties, .
http://www.sentrymgt.com/hoa-condo-management-tampa-wesley-chapel-fl
Official Impairment Listing for Spinal Disorders
DCA | Link Disclaimer
You are about to leave the GQGP website. The links to other web sites are included when the content of those sites are judged to be suitable or helpful.
http://www.dca.state.ga.us/OITDSShared/asp/NavDisclaimer.asp?Leaving=GQGP
- veido clipss of maruto (narrowing of the spine)
Ronald P. Matonti | Facebook
. Support flying Gold Star Flags on Memorial Day, Honor our Fallen Soldiers, Support . Act on Poverty, Florida AFL CIO, Stonewall Democrats of Pinellas County, . Jeffrey Miron, Honolulu Star-Advertiser, The U.S. Senate: Attend the briefing on . Disabled American Veterans, Chapter 15, New Ulm, Minnesota, Disabled .
http://www.facebook.com/matonti2Tampa Homeowners Association Management, Property ...
Sentry Management provides operational leadership to homeowner and . in Pasco County and portions of Hillsborough, Pinellas and Hernando counties, .
http://www.sentrymgt.com/hoa-condo-management-tampa-wesley-chapel-fl
Ronald P. Matonti | Facebook
. Support flying Gold Star Flags on Memorial Day, Honor our Fallen Soldiers, Support . Act on Poverty, Florida AFL CIO, Stonewall Democrats of Pinellas County, . Jeffrey Miron, Honolulu Star-Advertiser, The U.S. Senate: Attend the briefing on . Disabled American Veterans, Chapter 15, New Ulm, Minnesota, Disabled .
http://www.facebook.com/matonti2
DCA | Link Disclaimer
You are about to leave the GQGP website. The links to other web sites are included when the content of those sites are judged to be suitable or helpful.
http://www.dca.state.ga.us/OITDSShared/asp/NavDisclaimer.asp?Leaving=GQGP
Medical-Vocational Allowance for Herniated Disc
DCA | Link Disclaimer
You are about to leave the GQGP website. The links to other web sites are included when the content of those sites are judged to be suitable or helpful.
http://www.dca.state.ga.us/OITDSShared/asp/NavDisclaimer.asp?Leaving=GQGP
Ronald P. Matonti | Facebook
. Support flying Gold Star Flags on Memorial Day, Honor our Fallen Soldiers, Support . Act on Poverty, Florida AFL CIO, Stonewall Democrats of Pinellas County, . Jeffrey Miron, Honolulu Star-Advertiser, The U.S. Senate: Attend the briefing on . Disabled American Veterans, Chapter 15, New Ulm, Minnesota, Disabled .
http://www.facebook.com/matonti2
Appealing a Denial of Benefits
Tampa Homeowners Association Management, Property ...
Sentry Management provides operational leadership to homeowner and . in Pasco County and portions of Hillsborough, Pinellas and Hernando counties, .
http://www.sentrymgt.com/hoa-condo-management-tampa-wesley-chapel-fl
Ronald P. Matonti | Facebook
. Support flying Gold Star Flags on Memorial Day, Honor our Fallen Soldiers, Support . Act on Poverty, Florida AFL CIO, Stonewall Democrats of Pinellas County, . Jeffrey Miron, Honolulu Star-Advertiser, The U.S. Senate: Attend the briefing on . Disabled American Veterans, Chapter 15, New Ulm, Minnesota, Disabled .
http://www.facebook.com/matonti2


Rake Command Line Usage
Rake is invoked from the command line using:
% rake [options ...] [VAR=VALUE] [targets ...]
Options are:
- name=value
- Set the environment variable name to value during the execution of the rake command. You can access the value by using ENV[‘name’].
- --classic-namespace (-n)
- Import the Task, FileTask, and FileCreateTask into the top-level scope to be compatible with older versions of Rake. Alternatively you can include the line require 'rake/classic_namespace' in your Rakefile to get the classic behavior.
- --describe pattern (-D)
- Describe the tasks (matching optional PATTERN), then exit.
- --dry-run (-n)
- Do a dry run. Print the tasks invoked and executed, but do not actually execute any of the actions.
- --execute code (-e)
- Execute some Ruby code and exit.
- --execute-print code (-p)
- Execute some Ruby code, print the result, and exit.
- --execute-continue code (-p)
- Execute some Ruby code, then continue with normal task processing.
- --help (-H)
- Display some help text and exit.
- --libdir directory (-I)
- Add directory to the list of directories searched for require.
- --nosearch (-N)
- Do not search for a Rakefile in parent directories.
- --prereqs (-P)
- Display a list of all tasks and their immediate prerequisites.
- --quiet (-q)
- Do not echo commands from FileUtils.
- --rakefile filename (-f)
- Use filename as the name of the rakefile. The default rakefile names are rakefile and Rakefile (with rakefile taking precedence). If the rakefile is not found in the current directory, rake will search parent directories for a match. The directory where the Rakefile is found will become the current directory for the actions executed in the Rakefile.
- --rakelibdir rakelibdir (-R)
- Auto-import any .rake files in RAKELIBDIR. (default is ‘rakelib’)
- --require name (-r)
- Require name before executing the Rakefile.
- --rules
- Trace the rules resolution.
- --silent (-s)
- Like —quiet, but also suppresses the ‘in directory’ announcement.
- --system (-g)
- Use the system wide (global) rakefiles. The project Rakefile is ignored. By default, the system wide rakefiles are used only if no project Rakefile is found. On Unix-like system, the system wide rake files are located in $HOME/.rake. On a windows system they are stored in $APPDATA/Rake.
- --no-system (-G)
- Use the project level Rakefile, ignoring the system-wide (global) rakefiles.
- --tasks pattern (-T)
- Display a list of the major tasks and their comments. Comments are defined using the “desc” command. If a pattern is given, then only tasks matching the pattern are displayed.
- --no-top-level-dsl (-X)
- Do not put the Rake DSL commands into the top level scope.
- --top-level-dsl
- Put the Rake DSL commands into the top level scope (default).
NOTE: Although currently Rake defaults to its DSL in the top level scope, the plan is to deprecate this in the future and default ot having the DSL commands not appear in the top level scope.
- --trace (-t)
- Turn on invoke/execute tracing. Also enable full backtrace on errors.
- --verbose (-v)
- Echo the Sys commands to standard output.
- --version (-V)
- Display the program version and exit.
- --where pattern (-W)
- Display tasks that match pattern and the file and line number where the task is defined.
In addition, any command line option of the form VAR=VALUE will be added to the environment hash ENV and may be tested in the Rakefile.


The module definitions.py contains a dictionary named COUNTRYDATA with a dictionary for each country, identified by the ISO2 code for the country. This is the definition for Germany:
'DE': {
'weekend': ['SA', 'SU'],
'start_of_week': 'MO',
'first_week': 'ISO',
'long_day_names': {'MO':'Montag', 'TU':'Dienstag', 'WE':'Mittwoch', 'TH':'Donnerstag',
'FR':'Freitag', 'SA':'Samstag', 'SU':'Sonntag'},
'short_day_names': {'MO':'MO', 'TU':'DI', 'WE':'MI', 'TH':'DO', 'FR':'FR', 'SA':'SA', 'SU':'SO'},
'long_month_names': ['', 'Januar', 'Februar', 'März', 'April', 'Mai', 'Juni',
'Juli', 'August', 'September', 'Oktober', 'November', 'Dezember'],
'short_month_names': ['', 'Jan', 'Feb', 'Mrz', 'Apr', 'Mai', 'Jun', 'Jul', 'Aug', 'Sep', 'Okt', 'Nov', 'Dez'],
'holidays': [
{'name': 'Neujahrstag', 'date': 'F:01-01::'},
{'name': 'H. drei Könige', 'date': 'F:01-06::', 'states': ['BW', 'BY', 'ST']},
{'name': 'Karfreitag', 'date': 'V:easter:-2::'},
{'name': 'Ostersonntag', 'date': 'V:easter:::'},
{'name': 'Ostermontag', 'date': 'V:easter:+1::'},
{'name': 'Tag der Arbeit', 'date': 'F:05-01::'},
{'name': 'Christi Himmelfahrt', 'date': 'V:easter:+39::'},
{'name': 'Pfingstsonntag', 'date': 'V:easter:+49::'},
{'name': 'Pfingstmontag', 'date': 'V:easter:+50::'},
{'name': 'Fronleichnam', 'date': 'V:easter:+60::', 'states': ['BW', 'BY', 'HE', 'NW', 'RP', 'SL']},
{'name': 'Maria Himmelfahrt', 'states': ['BY'], 'date': 'F:08-15::'},
{'name': 'Tag der deutschen Einheit', 'date': 'F:10-03::'},
{'name': 'Reformationstag', 'states': ['BB', 'SN', 'MV', 'ST', 'TH'], 'date': 'F:10-31::'},
{'name': 'Allerheiligen', 'date': 'F:11-01::', 'states': ['BW', 'BY', 'NW', 'RP', 'SL']},
{'name': 'Buß- und Bettag', 'date': 'V:advent:-WE::1995-', 'states': ['SN']},
{'name': 'Buß- und Bettag', 'date': 'V:advent:-WE::-1994'},
{'name': '1. Weihnachtstag', 'date': 'F:12-25::'},
{'name': '2. Weihnachtstag', 'date': 'F:12-26::'},
],
}
Please have a look the code in the definitions.py module, where you also will find all the abbreviations for the state codes. Country codes will always be ISO2.
The definitions.py module contains core definitions for the package in a structure based on country. The holiday section for each country may contain holiday definitions in a text-based formula.
Public holidays may occur on a fixed date (same month and day every year) or on variable dates that may change every year (Easter / Pentecost). For fixed holidays, use F as the first letter of the definition, for variable holidays use a V as the first letter.
A definitions for a fixed holiday consists of four fields:
- ‘F’
- <month>-<day>
- <spread>
- <validity>
A simple example would be Labor Day in Europe, always on May, 1st: F:05-01::. As you can see, content for fields spread and validity` are optional.
A definition for a variable holiday consists of five fields:
- ‘V’
- <basedate>
- <formula>
- <spread>
- <validity>
We use the definition for Ascension in Germany (39 days after Easter): V:Easter+39.
In many countries there are special rules if a holiday occurs on a weekend. Independence Day in the United States is an example. If the 4th of July is a saturday, the firday will not be a workday. The field spread is used for this purpose.
The definitions consists of the weekday of the holiday and the spreading of the day. Let’s stick to our example of Independence Day: if July 4th is a sunday, the monday will be a day off in addition to the rule for saturday. So we define the field value as SA-FR``for the first part and ``SU+MO for the second part. Both parts will be separated by a comma, like so: F:07-04:SA-FR,SU+MO: (the last field validity is empty).
In Great Britain there is a rule for Christmas Day: is December, 25th is on a weekend, the next tuesday is not a working day: F:12-25:SA+TU,SU+TU:
If a holiday is valid only up until a certain year of from a certain year, you may use the validity field to store that information. Starting next year, the Netherlands will be celebrating “Konigsdag” on April 27. Up and including 2013, the “Koniginnendag” is April 30th. This day has been celebrated starting 1949, when Queen Juliana became Queen. (to our friends from The Netherlands: I hope I got that right, if I need to make corrections, please let me know)
- so this is the definitions for the Koniginnendag: F:04-30:SU-SA:1949-2013
- and this is the definitions for the Konigsdag: F:04-27:SU-SA:0-2014
For variable holidays you may specify a formula, based on a starting point in time. In th esouthern part of Germany, Ascension will be celebrated 39 days after Easter. So the base date would be Easter. As 39 days after Easter is always a thursday, you have two options to specify this:
- alternative 1: Easter+39
- alternative 2: Easter+TH+TH+TH+TH+TH+TH
V:Nov-1-MO (last monday in october)
F:07-04:SA-FR,SU+MO:
- fixed
- Falls Samstag, ist der Freitag frei
- Falls Sonntag, ist der Montag frei
V:Feb+MO+MO+MO
- variable
- Basisdatum ist Feb (also der 1. Februar)
- dann der dritte Montag
F:12-25:SA+TU,SU+TU: F:12-26:SA+MO,SU+MO:
- fixed
- falls der 25.12. ein Wochenende ist, ist der nächste Dienstag frei
- falls der 26.12. ein Wochenende ist, ist der nächste Montag frei
- keine Gültigkeit bedeutet immer


Water Bottle
Blue water bottle with gray lid
For any type of Use!
price $29
Blue water bottle with gray lid
For any type of Use!
price $29
Gray water bottle with Black lid
For any type of Use!
price $27
Mint Green water Bottle
For any type of Use!
price $24
Black water bottle
For any type of Use!
Price $35
Stainless Steel Water Bottle
For any type of Use!
Price $35
Black ear buds
Great sound quality!
Price $15
Morpheus 360 Wireless Earbuds
Great sound quality!
Price $25
White bluetooth ear buds
Great sound quality!
Price $25
Skullcandy lndy wireless Earbuds
Great sound quality!
Price $95
Skullcandy Jib wired Earbuds
Great sound quality!
Price $14


He Got Game (R) *** (out of ****)
The tagline for He Got Game--"the father, the son, and the holy game"--provides a very clear and accurate ordering of writer-director Spike Lee's concerns in the film. While the game of basketball is the film's unifying subject, this uneven but engrossing drama is foremost an exploration of a father-son relationship.
The father in question is Jake Shuttlesworth (Denzel Washington), a prison inmate who is granted a temporary release to convince his son Jesus (Milwaukee Bucks guard Ray Allen), high school senior and hoops superstar, to attend the governor's university alma mater the following school year. The task is not quite as easy as it sounds, for Jake's relationship with his son became virtually nonexistent following the death of Jesus's mother and Jake's imprisonment. The issue of reconciliation is what drives He Got Game, and Lee deftly escalates the emotional stakes by gradually revealing Jake and Jesus's turbulent past and the tense circumstances that ultimately led to their estrangement.
When staying with the driving father-son dynamic, He Got Game often achieves moments of power, buoyed by a predictably strong performance by Washington. Allen is relaxed and assured in his acting debut, but his work suffers away from Washington; when he is called on to carry scenes on his own, he tends to stiffen up, and his line delivery comes off a bit flat. As such, he is a slightly less-than-commanding presence during the Jake-less scenes, in which Jesus deals with other pressures, such as his sports-agent-pushing girlfriend Lala (Rosario Dawson) and Chick (Los Angeles Laker forward Rick Fox), a baller from a prospective university, who tempts Jesus with horny groupies. Granted, the air of doubt works in showing how vulnerable Jesus is to pressure, but it also diminishes audience interest and involvement.
To be fair, Washington also suffers away from Allen, but this is because of the comaparatively weak material he is saddled with. Jake's unlikely friendship with Dakota (Milla Jovovich), a prostitute who lives in the apartment next door, is completely superfluous, not to mention unconvincing; Lee offers no insight as to how or why Jake would develop any feelings, deep or otherwise, for her. Lacking in any payoff, and showcasing an awful performance by Jovovich, this subplot just about begs to be completely cut out.
He Got Game could have used a clearer focus, but what does come sharply into view registers strongly: not just Jake and Jesus, but their and, above all, Lee's passion for the game of basketball. From the majestic, Aaron Copland-scored opening shots of people of all ages and places shooting hoops to the halftime cameos by various NBA stars (yes, including _him_, who gets the honor of delivering the film's title line) to the late glimpses of Jesus and Jake alone on different courts, Lee shows how easy it is to fall under the sport's spell. Audiences may leave He Got Game not exactly loving the film, but it is quite possible that they could grow, to quote the NBA's promotional slogan, "love this game."
Michael Dequina Chat Forum Host, The Official Michael Jordan Web Site http://jordan.sportsline.com
<EMAIL_ADDRESS><EMAIL_ADDRESS>|<EMAIL_ADDRESS>>My personal WWW sites< Mr. Brown's Movie Site: http://welcome.to/mrbrown Michael Jordan Beyond the Court: http://fly.to/michaeljordan A Michael Jordan Fan's Heartbreak: http://fly.to/mj23 Personal Page: http://welcome.to/w3md >Other WWW sites I work on< CompuServe Hollywood Hotline: http://www.HollywoodHotline.com Albany Online: http://www.AlbanyOnline.com Eyepiece Network: http://www.eyepiece.com
"I didn't know what to expect. It's like something you chase for so long, but then you don't know how to react when you get it. I still don't know how to react." --Michael Jordan, on winning his first NBA championship in 1991 ...or, my thoughts after meeting him on November 21, 1997
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Topics:
Extend your HW5 program.
Average the normals for each face to create a normal for each vertex.
Implement the Phong shading model.
Illuminate your geometric model with at least two point lights.
Implement both Gouraud and Phong shading algorithms.
Allow the user to interactively select either Gouraud and Phong shading.
Allow the user to choose the material properties
of your model from a pre-defined list of at least three materials.
The three materials should be significantly different, i.e. don't
just change the color. You should also change the shading properties.
Be sure that one of your materials produces a bright specular highlight.
Similar to your camera, place one of your lights on a
cylinder around the object and allow the user to change the
light location by modifying the angle, radius and
height of the light's location.
The light should only move when the user
changes its location. This light should be defined in the coordinate
system of the object.
The other light should be defined in the camera coordinate system, i.e. it moves with the camera.
Last modified February 12, 2016.


| Package | Description |
|---|---|
| com.hikmat30ce.workday.integrator.hr.generated |
| Modifier and Type | Field and Description |
|---|---|
protected LocationObjectType |
LocationIDataType.defaultJobPostingLocationReference |
protected LocationObjectType |
LocationReferenceWWSType.locationIDReference |
protected LocationObjectType |
SupervisoryOrgDataType.locationReference |
protected LocationObjectType |
PutLocationResponseType.locationReference |
protected LocationObjectType |
PutLocationRequestType.locationReference |
protected LocationObjectType |
LocationSummaryDataType.locationReference |
protected LocationObjectType |
LocationResponseType.locationReference |
protected LocationObjectType |
OrganizationSummaryDataType.primaryBusinessSiteReference |
protected LocationObjectType |
LocationIDataType.superiorLocationReference |
protected LocationObjectType |
PositionDetailDataType.workSpaceReference |
| Modifier and Type | Field and Description |
|---|---|
protected List<LocationObjectType> |
WorkersCompensationCodeRequestCriteriaType.locationReference |
protected List<LocationObjectType> |
WorkersCompensationCodeDataType.locationReference |
protected List<LocationObjectType> |
PositionGroupRestrictionSummaryDataType.locationReference |
protected List<LocationObjectType> |
LocationRequestReferencesType.locationReference |
protected List<LocationObjectType> |
InstructorEligibilityLineDataType.locationReference |
protected List<LocationObjectType> |
EstablishmentDataType.locationReference |
| Modifier and Type | Method and Description |
|---|---|
LocationObjectType |
ObjectFactory.createLocationObjectType()
Create an instance of
LocationObjectType |
LocationObjectType |
LocationIDataType.getDefaultJobPostingLocationReference()
Gets the value of the defaultJobPostingLocationReference property.
|
LocationObjectType |
LocationReferenceWWSType.getLocationIDReference()
Gets the value of the locationIDReference property.
|
LocationObjectType |
SupervisoryOrgDataType.getLocationReference()
Gets the value of the locationReference property.
|
LocationObjectType |
PutLocationResponseType.getLocationReference()
Gets the value of the locationReference property.
|
LocationObjectType |
PutLocationRequestType.getLocationReference()
Gets the value of the locationReference property.
|
LocationObjectType |
LocationSummaryDataType.getLocationReference()
Gets the value of the locationReference property.
|
LocationObjectType |
LocationResponseType.getLocationReference()
Gets the value of the locationReference property.
|
LocationObjectType |
OrganizationSummaryDataType.getPrimaryBusinessSiteReference()
Gets the value of the primaryBusinessSiteReference property.
|
LocationObjectType |
LocationIDataType.getSuperiorLocationReference()
Gets the value of the superiorLocationReference property.
|
LocationObjectType |
PositionDetailDataType.getWorkSpaceReference()
Gets the value of the workSpaceReference property.
|
| Modifier and Type | Method and Description |
|---|---|
List<LocationObjectType> |
WorkersCompensationCodeRequestCriteriaType.getLocationReference()
Gets the value of the locationReference property.
|
List<LocationObjectType> |
WorkersCompensationCodeDataType.getLocationReference()
Gets the value of the locationReference property.
|
List<LocationObjectType> |
PositionGroupRestrictionSummaryDataType.getLocationReference()
Gets the value of the locationReference property.
|
List<LocationObjectType> |
LocationRequestReferencesType.getLocationReference()
Gets the value of the locationReference property.
|
List<LocationObjectType> |
InstructorEligibilityLineDataType.getLocationReference()
Gets the value of the locationReference property.
|
List<LocationObjectType> |
EstablishmentDataType.getLocationReference()
Gets the value of the locationReference property.
|
| Modifier and Type | Method and Description |
|---|---|
void |
LocationIDataType.setDefaultJobPostingLocationReference(LocationObjectType value)
Sets the value of the defaultJobPostingLocationReference property.
|
void |
LocationReferenceWWSType.setLocationIDReference(LocationObjectType value)
Sets the value of the locationIDReference property.
|
void |
SupervisoryOrgDataType.setLocationReference(LocationObjectType value)
Sets the value of the locationReference property.
|
void |
PutLocationResponseType.setLocationReference(LocationObjectType value)
Sets the value of the locationReference property.
|
void |
PutLocationRequestType.setLocationReference(LocationObjectType value)
Sets the value of the locationReference property.
|
void |
LocationSummaryDataType.setLocationReference(LocationObjectType value)
Sets the value of the locationReference property.
|
void |
LocationResponseType.setLocationReference(LocationObjectType value)
Sets the value of the locationReference property.
|
void |
OrganizationSummaryDataType.setPrimaryBusinessSiteReference(LocationObjectType value)
Sets the value of the primaryBusinessSiteReference property.
|
void |
LocationIDataType.setSuperiorLocationReference(LocationObjectType value)
Sets the value of the superiorLocationReference property.
|
void |
PositionDetailDataType.setWorkSpaceReference(LocationObjectType value)
Sets the value of the workSpaceReference property.
|
Copyright © 2017 Pivotal Software, Inc.. All rights reserved.


We Do
Make People Smile At Screens
Make People Smile At Screens
What's Your Story?
We know you have a story to tell. You want the world to embrace your incredible ideas, products, and services. Trouble is, you're not sure about the best way to get your message across. No problem. We do.
Start A ProjectHappy People
User Experience (UX) Design is our compass in creating your digital presence. We bring your products or services across in ways that make people feel good as they engage with your business. We firmly believe that making your people happy is not about U or about Us; it's all about UX.
Get Connected
Stay connected with us through social networks!


Home
Hobbies
Gallery
Contact
Education
My Qualification
This is my academic qualification.
Level
Institute
Year
Division
SLC
Shree Bishnu Devi SSMV
2012
First
High School
Goldengate International College
2015
First
Bachelor's
Ed-Mark College/ Tribhuvan University
2018
First


WWE Rumors: Backstage source wants Superstar to join RAW and beat Brock Lesnar for the title
by Lennard SurraoIt's not too easy to get into the good books of Vince McMahon but a previously underappreciated NXT Superstar has managed to do exactly that. Yes, you guessed it right. Vince McMahon likes Keith Lee a lot and the NXT Superstar was rewarded for his efforts with a big push at Survivor Series.
Lee was one of the final two survivors in the Elimination tag team match at Survivor Series before he was pinned by Roman Reigns.
A report from WrestlingNews.co has revealed the backstage reaction to Keith Lee's metronomic rise.
The report states that Lee is one of those talents who doesn't complain and always shows up to get the job done. The 35-year-old was described as one of the hardest working Superstars on the roster and everyone is genuinely happy to see him get the deserved recognition.
It was also stated that Vince is a fan of Lee and that the Superstar could end up being on either RAW or SmackDown in a few months.
Another WWE source told WrestlingNews.co that he would like to see Lee win one of the major main roster titles. The source even added that putting Lee in a feud with Brock Lesnar is a good idea as the NXT Superstar comes across as a believable contender to take the Beast Incarnate down.
Lee could even be paired up with a manager before he goes on a lengthy reign with the title.
Here's what the sources revealed in the report:
“He doesn’t complain and he shows up to do the work. We all know how good he is and this was his night to show everyone what he can do. Vince likes him and I think he’ll be on RAW or SmackDown in a few months.”
"I would put one of the main belts on him. If they don’t want to beat Bray then put him in there with Brock. I think people can believe Keith can beat Brock. He has what Vince is looking for. I would maybe give him a manager and give him a long run as champion. He works as hard or harder than anyone and never b***hes or complains about anything. I’m so happy for him.”
The report also stated that the company was happy with NXT's strong showing at Survivor Series and that the Yellow brand is expected to beat AEW this week in the TV rating war.
As for Keith Lee, the former PWG World Champion has a bright future ahead of him.
Now you can rate RAW, SmackDown and NXT matches on Sportskeeda !


Election boundary shake up on cards for Canterbury
Major electoral boundary changes proposed for Canterbury could see Selwyn redrawn and a name change for the Port Hills electorate.
The Representation Commission, an independent organisation that reviews the boundaries and names of electorates, released a report on Wednesday proposing adjustments and name changes to half of New Zealand’s electorates for the next two general elections.
The changes would see Selwyn's map redrawn to no longer include Banks Peninsula, which could mean the current Port Hills electorate would be re-named Banks Peninsula.
Changes have also been proposed for Ilam, Wigram, Christchurch East and Rangitata.
Said Representation Commission chairman Craig Thompson: “Boundary changes are needed to electorates in the Christchurch area because of significant population growth in Selwyn, which is the fastest growing electorate in the country.”
The public will now be able to have their say before the boundaries are finalised in April 2020.
“Where possible the current boundaries have been retained to minimise the number of people affected by electorate boundary and name changes," Judge Thompson said.
"Of the 71 existing electorates, 36 are unchanged. The adjustments in other electorates reflect changes in population since 2014 when the boundaries were last reviewed.
“We encourage people to have a closer look at the changes and what it means for them.
"The public can make objections on the proposed boundaries and names until 20 December."
There will be a counter-objections period from January 10-24, and public hearings will be held in February.
More information, including changes to other parts of New Zealand, can be found here.


Shawn Mendes, Drake, Jessie Reyez pick up Grammy nominations
Drake leads the group of Canadian contenders with two nominations
by The Canadian PressShawn Mendes, Jessie Reyez and Drake are among the Canadians who will be competing at the 2020 Grammy Awards.
Drake leads the group of Canadian contenders with two nominations for separate collaborative efforts.
The Toronto rapper shares a nod with Rick Ross for “Gold Roses” for best rap song. He’s also nominated alongside Chris Brown for “No Guidance” in the R&B song category. The track was co-produced by Drake’s longtime Toronto-based collaborator Noah Shebib.
Mendes grabbed a nod alongside Camila Cabello for their single “Senorita” for best pop duo or group performance.
Jessie Reyez scored her first Grammy nomination for “Being Human in Public” in the urban contemporary album category.
Other nominees included Daniel Caesar for “Love Again” with Brandy in the best R&B performance category. It’s Caesar’s fourth career Grammy nomination.
Michael Buble’s “Love” is nominated for best traditional pop vocal album.
Alberta’s Northern Cree received its ninth career Grammy nomination. Their album “When It’s Cold — Cree Round Dance Songs” is in the running for best regional roots music album.
And while Montreal electronic musician Marie Davidson didn’t get a nomination herself, a pumped-up club version of her song “Work It” by Belgian brothers David and Stephen Dewaele, who perform under the name Soulwax, nabbed best remixed recording.
The 62nd Grammy Awards air Sunday, Jan. 26. on CBS and Citytv.
VIDEO: Canopy Growth and Drake team up on new cannabis venture
David Friend, The Canadian Press


A stream that emits multiple other streams one after another.
NB Currently combined-stream
works with streams vesrion 1 only. There is ongoing effort to switch this library to streams version 2. Any help is welcome. :) Meanwhile you can explore other libraries that provide streams2 support with more or less compatability with combined-stream
.
combined-stream2: A drop-in streams2-compatible replacement for the combined-stream module.
multistream: A stream that emits multiple other streams one after another.
npm install combined-stream
Here is a simple example that shows how you can use combined-stream to combine two files into one:
var CombinedStream = require('combined-stream');
var fs = require('fs');
var combinedStream = CombinedStream.create();
combinedStream.append(fs.createReadStream('file1.txt'));
combinedStream.append(fs.createReadStream('file2.txt'));
combinedStream.pipe(fs.createWriteStream('combined.txt'));
While the example above works great, it will pause all source streams until
they are needed. If you don't want that to happen, you can set pauseStreams
to false
:
var CombinedStream = require('combined-stream');
var fs = require('fs');
var combinedStream = CombinedStream.create({pauseStreams: false});
combinedStream.append(fs.createReadStream('file1.txt'));
combinedStream.append(fs.createReadStream('file2.txt'));
combinedStream.pipe(fs.createWriteStream('combined.txt'));
However, what if you don't have all the source streams yet, or you don't want
to allocate the resources (file descriptors, memory, etc.) for them right away?
Well, in that case you can simply provide a callback that supplies the stream
by calling a next()
function:
var CombinedStream = require('combined-stream');
var fs = require('fs');
var combinedStream = CombinedStream.create();
combinedStream.append(function(next) {
next(fs.createReadStream('file1.txt'));
});
combinedStream.append(function(next) {
next(fs.createReadStream('file2.txt'));
});
combinedStream.pipe(fs.createWriteStream('combined.txt'));
Returns a new combined stream object. Available options are:
maxDataSize
pauseStreams
The effect of those options is described below.
true
Whether to apply back pressure to the underlaying streams. If set to false
,
the underlaying streams will never be paused. If set to true
, the
underlaying streams will be paused right after being appended, as well as when
delayedStream.pipe()
wants to throttle.
2 * 1024 * 1024
The maximum amount of bytes (or characters) to buffer for all source streams.
If this value is exceeded, combinedStream
emits an 'error'
event.
0
The amount of bytes (or characters) currently buffered by combinedStream
.
Appends the given stream
to the combinedStream object. If pauseStreams
is
set to `true, this stream will also be paused right away.
streams
can also be a function that takes one parameter called next
. next
is a function that must be invoked in order to provide the next
stream, see
example above.
Regardless of how the stream
is appended, combined-stream always attaches an
'error'
listener to it, so you don't have to do that manually.
Special case: stream
can also be a String or Buffer.
You should not call this, combinedStream
takes care of piping the appended
streams into itself for you.
Causes combinedStream
to start drain the streams it manages. The function is
idempotent, and also emits a 'resume'
event each time which usually goes to
the stream that is currently being drained.
If combinedStream.pauseStreams
is set to false
, this does nothing.
Otherwise a 'pause'
event is emitted, this goes to the stream that is
currently being drained, so you can use it to apply back pressure.
Sets combinedStream.writable
to false, emits an 'end'
event, and removes
all streams from the queue.
Same as combinedStream.end()
, except it emits a 'close'
event instead of
'end'
.
combined-stream is licensed under the MIT license.


Salvatore "Sal" Testa /@saltesta14
Apply heat to one side of the pin. Feed the pin solder until you get a nice cone of solder.


| A | Deprecated Functions in package vars |
| A-deprecated | Coefficient matrices of the lagged endogenous variables |
| Acoef | Coefficient matrices of the lagged endogenous variables |
| arch | Deprecated Functions in package vars |
| arch-deprecated | ARCH-LM test |
| arch.test | ARCH-LM test |
| B | Deprecated Functions in package vars |
| B-deprecated | Coefficient matrix of an estimated VAR(p) |
| Bcoef | Coefficient matrix of an estimated VAR(p) |
| BQ | Estimates a Blanchard-Quah type SVAR |
| Canada | Canada: Macroeconomic time series |
| causality | Causality Analysis |
| coef | Coefficient method for objects of class varest |
| coef.varest | Coefficient method for objects of class varest |
| coefficients | Coefficient method for objects of class varest |
| fanchart | Fanchart plot for objects of class varprd |
| fevd | Forecast Error Variance Decomposition |
| fevd.svarest | Forecast Error Variance Decomposition |
| fevd.svecest | Forecast Error Variance Decomposition |
| fevd.varest | Forecast Error Variance Decomposition |
| fevd.vec2var | Forecast Error Variance Decomposition |
| fitted | Fit method for objects of class varest or vec2var |
| fitted.values | Fit method for objects of class varest or vec2var |
| fitted.varest | Fit method for objects of class varest or vec2var |
| fitted.vec2var | Fit method for objects of class varest or vec2var |
| irf | Impulse response function |
| irf.svarest | Impulse response function |
| irf.svecest | Impulse response function |
| irf.varest | Impulse response function |
| irf.vec2var | Impulse response function |
| logLik | Log-Likelihood method |
| logLik.svarest | Log-Likelihood method |
| logLik.svecest | Log-Likelihood method |
| logLik.varest | Log-Likelihood method |
| logLik.vec2var | Log-Likelihood method |
| normality | Deprecated Functions in package vars |
| normality-deprecated | Normality, multivariate skewness and kurtosis test |
| normality.test | Normality, multivariate skewness and kurtosis test |
| Phi | Coefficient matrices of the MA represention |
| Phi.svarest | Coefficient matrices of the MA represention |
| Phi.svecest | Coefficient matrices of the MA represention |
| Phi.varest | Coefficient matrices of the MA represention |
| Phi.vec2var | Coefficient matrices of the MA represention |
| plot.varcheck | Plot methods for objects in vars |
| plot.varest | Plot methods for objects in vars |
| plot.varfevd | Plot methods for objects in vars |
| plot.varirf | Plot methods for objects in vars |
| plot.varprd | Plot methods for objects in vars |
| plot.varstabil | Plot methods for objects in vars |
| plot.vec2var | Plot methods for objects in vars |
| predict | Predict method for objects of class varest and vec2var |
| predict.varest | Predict method for objects of class varest and vec2var |
| predict.vec2var | Predict method for objects of class varest and vec2var |
| print.svarest | Estimation of a SVAR |
| print.svarsum | Summary method for objects of class varest, svarest and svecest |
| print.svecest | Estimation of a SVEC |
| print.svecsum | Summary method for objects of class varest, svarest and svecest |
| print.varcheck | ARCH-LM test |
| print.varest | Estimation of a VAR(p) |
| print.varfevd | Forecast Error Variance Decomposition |
| print.varirf | Impulse response function |
| print.varprd | Predict method for objects of class varest and vec2var |
| print.varstabil | Structural stability of a VAR(p) |
| print.varsum | Summary method for objects of class varest, svarest and svecest |
| print.vec2var | Transform a VECM to VAR in levels |
| Psi | Coefficient matrices of the orthogonalised MA represention |
| Psi.varest | Coefficient matrices of the orthogonalised MA represention |
| Psi.vec2var | Coefficient matrices of the orthogonalised MA represention |
| resid | Residuals method for objects of class varest and vec2var |
| residuals | Residuals method for objects of class varest and vec2var |
| residuals.varest | Residuals method for objects of class varest and vec2var |
| residuals.vec2var | Residuals method for objects of class varest and vec2var |
| restrict | Restricted VAR |
| roots | Eigenvalues of the companion coefficient matrix of a VAR(p)-process |
| serial | Deprecated Functions in package vars |
| serial-deprecated | Test for serially correlated errors |
| serial.test | Test for serially correlated errors |
| stability | Structural stability of a VAR(p) |
| stability.default | Structural stability of a VAR(p) |
| stability.varest | Structural stability of a VAR(p) |
| summary | Summary method for objects of class varest, svarest and svecest |
| summary.svarest | Summary method for objects of class varest, svarest and svecest |
| summary.svecest | Summary method for objects of class varest, svarest and svecest |
| summary.varest | Summary method for objects of class varest, svarest and svecest |
| SVAR | Estimation of a SVAR |
| SVEC | Estimation of a SVEC |
| VAR | Estimation of a VAR(p) |
| vars-deprecated | Deprecated Functions in package vars |
| VARselect | Information criteria and FPE for different VAR(p) |
| vec2var | Transform a VECM to VAR in levels |


The ld65 linker combines several object modules created by the ca65 assembler, producing an executable file. The object modules may be read from a library created by the ar65 archiver (this is somewhat faster and more convenient). The linker was designed to be as flexible as possible. It complements the features that are built into the ca65 macroassembler:
The linker is called as follows:
---------------------------------------------------------------------------
Usage: ld65 [options] module ...
Short options:
-( Start a library group
-) End a library group
-C name Use linker config file
-D sym=val Define a symbol
-L path Specify a library search path
-Ln name Create a VICE label file
-S addr Set the default start address
-V Print the linker version
-h Help (this text)
-m name Create a map file
-o name Name the default output file
-t sys Set the target system
-u sym Force an import of symbol `sym'
-v Verbose mode
-vm Verbose map file
Long options:
--cfg-path path Specify a config file search path
--config name Use linker config file
--dbgfile name Generate debug information
--define sym=val Define a symbol
--end-group End a library group
--force-import sym Force an import of symbol `sym'
--help Help (this text)
--lib file Link this library
--lib-path path Specify a library search path
--mapfile name Create a map file
--module-id id Specify a module id
--obj file Link this object file
--obj-path path Specify an object file search path
--start-addr addr Set the default start address
--start-group Start a library group
--target sys Set the target system
--version Print the linker version
---------------------------------------------------------------------------
Here is a description of all of the command-line options:
-(, --start-group
Start a library group. The libraries specified within a group are searched multiple times to resolve crossreferences within the libraries. Normally, crossreferences are resolved only within a library, that is the library is searched multiple times. Libraries specified later on the command line cannot reference otherwise unreferenced symbols in libraries specified earlier, because the linker has already handled them. Library groups are a solution for this problem, because the linker will search repeatedly through all libraries specified in the group, until all possible open symbol references have been satisfied.
-), --end-group
End a library group. See the explanation of the
--start-group
option.
-h, --help
Print the short option summary shown above.
-m name, --mapfile name
This option (which needs an argument that will used as a filename for the generated map file) will cause the linker to generate a map file. The map file does contain a detailed overview over the modules used, the sizes for the different segments, and a table containing exported symbols.
-o name
The -o switch is used to give the name of the default output file. Depending on your output configuration, this name might not be used as the name for the output file. However, for the default configurations, this name is used for the output file name.
-t sys, --target sys
The argument for the -t switch is the name of the target system. Since this
switch will activate a default configuration, it may not be used together
with the
-C
option. The following target
systems are currently supported:
There are a few more targets defined but neither of them is actually supported.
-u sym[:addrsize], --force-import sym[:addrsize]
Force an import of a symbol. While object files are always linked to the
output file, regardless if there are any references, object modules from
libraries get only linked in if an import can be satisfied by this module.
The --force-import
option may be used to add a reference to a symbol and
as a result force linkage of the module that exports the identifier.
The name of the symbol may optionally be followed by a colon and an address-size specifier. If no address size is specified, the default address size for the target machine is used.
Please note that the symbol name needs to have the internal representation, meaning you have to prepend an underscore for C identifiers.
-v, --verbose
Using the -v option, you may enable more output that may help you to locate problems. If an undefined symbol is encountered, -v causes the linker to print a detailed list of the references (that is, source file and line) for this symbol.
-vm
Must be used in conjunction with
-m
(generate map file). Normally the map file will not include empty segments
and sections, or unreferenced symbols. Using this option, you can force the
linker to include all that information into the map file. Also, it will
include a second Exports
list. The first list is sorted by name;
the second one is sorted by value.
-C
This gives the name of an output config file to use. See section 4 for more
information about config files. -C may not be used together with
-t
.
-D sym=value, --define sym=value
This option allows to define an external symbol on the command line. Value
may start with a '$' sign or with 0x
for hexadecimal values,
otherwise a leading zero denotes octal values. See also
the SYMBOLS section in the configuration file.
-L path, --lib-path path
Specify a library search path. This option may be used more than once. It
adds a directory to the search path for library files. Libraries specified
without a path are searched in the current directory, in the list of
directories specified using --lib-path
, in directories given by
environment variables, and in a built-in default directory.
-Ln
This option allows you to create a file that contains all global labels and
may be loaded into the VICE emulator using the ll
(load label) command
or into the Oricutron emulator using the sl
(symbols load) command. You
may use this to debug your code with VICE. Note: Older versions had some
bugs in the label code. If you have problems, please get the latest
VICE version.
-S addr, --start-addr addr
Using -S you may define the default starting address. If and how this address is used depends on the config file in use. For the default configurations, only the "none", "apple2" and "apple2enh" systems honor an explicit start address, all other default configs provide their own.
-V, --version
This option prints the version number of the linker. If you send any suggestions or bugfixes, please include this number.
--cfg-path path
Specify a config file search path. This option may be used more than once.
It adds a directory to the search path for config files. A config file given
with the
-C
option that has no path in
its name is searched in the current directory, in the list of directories
specified using --cfg-path
, in directories given by environment variables,
and in a built-in default directory.
--dbgfile name
Specify an output file for debug information. Available information will be
written to this file. Using the -g
option for the compiler and assembler
will increase the amount of information available. Please note that debug
information generation is currently being developed, so the format of the
file and its contents are subject to change without further notice.
--lib file
Links a library to the output. Use this command-line option instead of just naming the library file, if the linker is not able to determine the file type because of an unusual extension.
--obj file
Links an object file to the output. Use this command-line option instead of just naming the object file, if the linker is not able to determine the file type because of an unusual extension.
--obj-path path
Specify an object file search path. This option may be used more than once.
It adds a directory to the search path for object files. An object file
passed to the linker that has no path in its name is searched in the current
directory, in the list of directories specified using --obj-path
, in
directories given by environment variables, and in a built-in default directory.
Starting with version 2.10, there are now several search-path lists for files needed by the linker: one for libraries, one for object files, and one for config files.
The library search-path list contains in this order:
--lib-path
option on the command line.LD65_LIB
if it is defined.lib
of the directory defined in the environment
variable CC65_HOME
, if it is defined.The object file search-path list contains in this order:
--obj-path
option on the command line.LD65_OBJ
if it is defined.obj
of the directory defined in the environment
variable CC65_HOME
, if it is defined.The config file search-path list contains in this order:
--cfg-path
option on the command line.LD65_CFG
if it is defined.cfg
of the directory defined in the environment
variable CC65_HOME
, if it is defined.The linker does several things when combining object modules:
First, the command line is parsed from left to right. For each object file encountered (object files are recognized by a magic word in the header, so the linker does not care about the name), imported and exported identifiers are read from the file and inserted in a table. If a library name is given (libraries are also recognized by a magic word, there are no special naming conventions), all modules in the library are checked if an export from this module would satisfy an import from other modules. All modules where this is the case are marked. If duplicate identifiers are found, the linker issues warnings.
That procedure (parsing and reading from left to right) does mean that a library may only satisfy references for object modules (given directly or from a library) named before that library. With the command line
ld65 crt0.o clib.lib test.o
the module test.o
must not contain references to modules in the library
clib.lib
. But, if it does, you have to change the order of the modules
on the command line:
ld65 crt0.o test.o clib.lib
Step two is, to read the configuration file, and assign start addresses for the segments and define any linker symbols (see Configuration files).
After that, the linker is ready to produce an output file. Before doing that, it checks its data for consistency. That is, it checks for unresolved externals (if the output format is not relocatable) and for symbol type mismatches (for example a zero-page symbol is imported by a module as an absolute symbol).
Step four is, to write the actual target files. In this step, the linker will resolve any expressions contained in the segment data. Circular references are also detected in this step (a symbol may have a circular reference that goes unnoticed if the symbol is not used).
Step five is to output a map file with a detailed list of all modules, segments and symbols encountered.
And, last step, if you give the
-v
switch
twice, you get a dump of the segment data. However, this may be quite
unreadable if you're not a developer. :-)
Configuration files are used to describe the layout of the output file(s). Two major topics are covered in a config file: The memory layout of the target architecture, and the assignment of segments to memory areas. In addition, several other attributes may be specified.
Case is ignored for keywords, that is, section or attribute names, but it is not ignored for names and strings.
Memory areas are specified in a MEMORY
section. Let's have a look at an
example (this one describes the usable memory layout of the C64):
MEMORY {
RAM1: start = $0800, size = $9800;
ROM1: start = $A000, size = $2000;
RAM2: start = $C000, size = $1000;
ROM2: start = $E000, size = $2000;
}
As you can see, there are two RAM areas and two ROM areas. The names (before the colon) are arbitrary names that must start with a letter, with the remaining characters being letters or digits. The names of the memory areas are used when assigning segments. As mentioned above, case is significant for those names.
The syntax above is used in all sections of the config file. The name
(ROM1
etc.) is said to be an identifier, the remaining tokens up to the
semicolon specify attributes for this identifier. You may use the equal sign
to assign values to attributes, and you may use a comma to separate
attributes, you may also leave both out. But you must use a semicolon to
mark the end of the attributes for one identifier. The section above may also
have looked like this:
# Start of memory section
MEMORY
{
RAM1:
start $0800
size $9800;
ROM1:
start $A000
size $2000;
RAM2:
start $C000
size $1000;
ROM2:
start $E000
size $2000;
}
There are of course more attributes for a memory section than just start and size. Start and size are mandatory attributes, that means, each memory area defined must have these attributes given (the linker will check that). I will cover other attributes later. As you may have noticed, I've used a comment in the example above. Comments start with a hash mark (`#'), the remainder of the line is ignored if this character is found.
Let's assume you have written a program for your trusty old C64, and you would
like to run it. For testing purposes, it should run in the RAM
area. So
we will start to assign segments to memory sections in the SEGMENTS
section:
SEGMENTS {
CODE: load = RAM1, type = ro;
RODATA: load = RAM1, type = ro;
DATA: load = RAM1, type = rw;
BSS: load = RAM1, type = bss, define = yes;
}
What we are doing here is telling the linker, that all segments go into the
RAM1
memory area in the order specified in the SEGMENTS
section. So
the linker will first write the CODE
segment, then the RODATA
segment, then the DATA
segment - but it will not write the BSS
segment. Why? Here enters the segment type: For each segment specified, you may also
specify a segment attribute. There are five possible segment attributes:
ro means readonly
rw means read/write
bss means that this is an uninitialized segment
zp a zeropage segment
overwrite a segment that overwrites (parts of) another one
So, because we specified that the segment with the name BSS is of type bss,
the linker knows that this is uninitialized data, and will not write it to an
output file. This is an important point: For the assembler, the BSS
segment has no special meaning. You specify, which segments have the bss
attribute when linking. This approach is much more flexible than having one
fixed bss segment, and is a result of the design decision to supporting an
arbitrary segment count.
If you specify "type = bss
" for a segment, the linker will make sure that
this segment does only contain uninitialized data (that is, zeroes), and issue
a warning if this is not the case.
For a bss
type segment to be useful, it must be cleared somehow by your
program (this happens usually in the startup code - for example the startup
code for cc65-generated programs takes care about that). But how does your
code know, where the segment starts, and how big it is? The linker is able to
give that information, but you must request it. This is, what we're doing with
the "define = yes
" attribute in the BSS
definitions. For each
segment, where this attribute is true, the linker will export three symbols.
__NAME_LOAD__ This is set to the address where the
segment is loaded.
__NAME_RUN__ This is set to the run address of the
segment. We will cover run addresses
later.
__NAME_SIZE__ This is set to the segment size.
Replace NAME
by the name of the segment, in the example above, this would
be BSS
. These symbols may be accessed by your code.
Now, as we've configured the linker to write the first three segments and create symbols for the last one, there's only one question left: Where does the linker put the data? It would be very convenient to have the data in a file, wouldn't it?
We don't have any files specified above, and indeed, this is not needed in a
simple configuration like the one above. There is an additional attribute
"file" that may be specified for a memory area, that gives a file name to
write the area data into. If there is no file name given, the linker will
assign the default file name. This is "a.out" or the one given with the
-o
option on the command line. Since the
default behaviour is OK for our purposes, I did not use the attribute in the
example above. Let's have a look at it now.
The "file" attribute (the keyword may also be written as "FILE" if you like
that better) takes a string enclosed in double quotes (`"') that specifies the
file, where the data is written. You may specify the same file several times,
in that case the data for all memory areas having this file name is written
into this file, in the order of the memory areas defined in the MEMORY
section. Let's specify some file names in the MEMORY
section used above:
MEMORY {
RAM1: start = $0800, size = $9800, file = %O;
ROM1: start = $A000, size = $2000, file = "rom1.bin";
RAM2: start = $C000, size = $1000, file = %O;
ROM2: start = $E000, size = $2000, file = "rom2.bin";
}
The %O
used here is a way to specify the default behaviour explicitly:
%O
is replaced by a string (including the quotes) that contains the
default output name, that is, "a.out" or the name specified with the
-o
option on the command line. Into this file, the
linker will first write any segments that go into RAM1
, and will append
then the segments for RAM2
, because the memory areas are given in this
order. So, for the RAM areas, nothing has really changed.
We've not used the ROM areas, but we will do that below, so we give the file
names here. Segments that go into ROM1
will be written to a file named
"rom1.bin", and segments that go into ROM2
will be written to a file
named "rom2.bin". The name given on the command line is ignored in both cases.
Assigning an empty file name for a memory area will discard the data written to it. This is useful, if the memory area has segments assigned that are empty (for example because they are of type bss). In that case, the linker will create an empty output file. This may be suppressed by assigning an empty file name to that memory area.
The %O
sequence is also allowed inside a string. So using
MEMORY {
ROM1: start = $A000, size = $2000, file = "%O-1.bin";
ROM2: start = $E000, size = $2000, file = "%O-2.bin";
}
would write two files that start with the name of the output file specified on the command line, with "-1.bin" and "-2.bin" appended respectively. Because '%' is used as an escape char, the sequence "%%" has to be used if a single percent sign is required.
There are situations when you may wish to overwrite some part (or parts) of a segment with another one. Perhaps you are modifying an OS ROM that has its public subroutines at fixed, well-known addresses, and you want to prevent them from shifting to other locations in memory if your changed code takes less space. Or you are updating a block of code available in binary-only form with fixes that are scattered in various places. Generally, whenever you want to minimize disturbance to an existing code brought on by your updates, OVERWRITE segments are worth considering.
Here is an example:
MEMORY {
RAM: file = "", start = $6000, size = $2000, type=rw;
ROM: file = %O, start = $8000, size = $8000, type=ro;
}
Nothing unusual so far, just two memory blocks - one RAM, one ROM. Now let's look at the segment configuration:
SEGMENTS {
RAM: load = RAM, type = bss;
ORIGINAL: load = ROM, type = ro;
FASTCOPY: load = ROM, start=$9000, type = overwrite;
JMPPATCH1: load = ROM, start=$f7e8, type = overwrite;
DEBUG: load = ROM, start=$8000, type = overwrite;
VERSION: load = ROM, start=$e5b7, type = overwrite;
}
Segment named ORIGINAL contains the original code, disassembled or provided in
a binary form (i.e. using .INCBIN
directive; see the ca65
assembler
document). Subsequent four segments will be relocated to addresses specified
by their "start" attributes ("offset" can also be used) and then will overwrite
whatever was at these locations in the ORIGINAL segment. In the end, resulting
binary output file will thus contain original data with the exception of four
sequences starting at $9000, $f7e8, $8000 and $e5b7, which will sport code from
their respective segments. How long these sequences will be depends on the
lengths of corresponding segments - they can even overlap, so think what you're
doing.
Finally, note that OVERWRITE segments should be the final segments loaded to a particular memory area, and that they need at least one of "start" or "offset" attributes specified.
Let us look now at a more complex example. Say, you've successfully tested your new "Super Operating System" (SOS for short) for the C64, and you will now go and replace the ROMs by your own code. When doing that, you face a new problem: If the code runs in RAM, we need not to care about read/write data. But now, if the code is in ROM, we must care about it. Remember the default segments (you may of course specify your own):
CODE read-only code
RODATA read-only data
DATA read/write data
BSS uninitialized data, read/write
Since BSS
is not initialized, we must not care about it now, but what
about DATA
? DATA
contains initialized data, that is, data that was
explicitly assigned a value. And your program will rely on these values on
startup. Since there's no way to remember the contents of the data segment,
other than storing it into one of the ROMs, we have to put it there. But
unfortunately, ROM is not writable, so we have to copy it into RAM before
running the actual code.
The linker won't copy the data from ROM into RAM for you (this must be done by the startup code of your program), but it has some features that will help you in this process.
First, you may not only specify a "load
" attribute for a segment, but
also a "run
" attribute. The "load
" attribute is mandatory, and, if
you don't specify a "run
" attribute, the linker assumes that load area
and run area are the same. We will use this feature for our data area:
SEGMENTS {
CODE: load = ROM1, type = ro;
RODATA: load = ROM2, type = ro;
DATA: load = ROM2, run = RAM2, type = rw, define = yes;
BSS: load = RAM2, type = bss, define = yes;
}
Let's have a closer look at this SEGMENTS
section. We specify that the
CODE
segment goes into ROM1
(the one at $A000). The readonly data
goes into ROM2
. Read/write data will be loaded into ROM2
but is run
in RAM2
. That means that all references to labels in the DATA
segment are relocated to be in RAM2
, but the segment is written to
ROM2
. All your startup code has to do is, to copy the data from its
location in ROM2
to the final location in RAM2
.
So, how do you know, where the data is located? This is the second point,
where you get help from the linker. Remember the "define
" attribute?
Since we have set this attribute to true, the linker will define three
external symbols for the data segment that may be accessed from your code:
__DATA_LOAD__ This is set to the address where the segment
is loaded, in this case, it is an address in
ROM2.
__DATA_RUN__ This is set to the run address of the segment,
in this case, it is an address in RAM2.
__DATA_SIZE__ This is set to the segment size.
So, what your startup code must do, is to copy __DATA_SIZE__
bytes from
__DATA_LOAD__
to __DATA_RUN__
before any other routines are called.
All references to labels in the DATA
segment are relocated to RAM2
by the linker, so things will work properly.
There's a library subroutine called copydata
(in a module named
copydata.s
) that might be used to do actual copying. Be sure to have a
look at it's inner workings before using it!
There are some other attributes not covered above. Before starting the reference section, I will discuss the remaining things here.
You may request symbols definitions also for memory areas. This may be useful for things like a software stack, or an I/O area.
MEMORY {
STACK: start = $C000, size = $1000, define = yes;
}
This will define some external symbols that may be used in your code:
__STACK_START__ This is set to the start of the memory
area, $C000 in this example.
__STACK_SIZE__ The size of the area, here $1000.
__STACK_LAST__ This is NOT the same as START+SIZE.
Instead, it is defined as the first
address that is not used by data. If we
don't define any segments for this area,
the value will be the same as START.
__STACK_FILEOFFS__ The binary offset in the output file. This
is not defined for relocatable output file
formats (o65).
A memory section may also have a type. Valid types are
ro for readonly memory
rw for read/write memory.
The linker will assure, that no segment marked as read/write or bss is put into a memory area that is marked as readonly.
Unused memory in a memory area may be filled. Use the "fill = yes
"
attribute to request this. The default value to fill unused space is zero. If
you don't like this, you may specify a byte value that is used to fill these
areas with the "fillval
" attribute. If there is no "fillval
"
attribute for the segment, the "fillval
" attribute of the memory area (or
its default) is used instead. This means that the value may also be used to
fill unfilled areas generated by the assembler's .ALIGN
and .RES
directives.
The symbol %S
may be used to access the default start address (that is,
the one defined in
the FEATURES section, or the
value given on the command line with the
-S
option).
To support systems with banked memory, a special attribute named bank
is
available. The attribute value is an arbitrary 32-bit integer. The assembler
has a builtin function named .BANK
which may be used with an argument
that has a segment reference (for example a symbol). The result of this
function is the value of the bank attribute for the run memory area of the
segment.
Segments may be aligned to some memory boundary. Specify "align = num
" to
request this feature. Num must be a power of two. To align all segments on a
page boundary, use
SEGMENTS {
CODE: load = ROM1, type = ro, align = $100;
RODATA: load = ROM2, type = ro, align = $100;
DATA: load = ROM2, run = RAM2, type = rw, define = yes,
align = $100;
BSS: load = RAM2, type = bss, define = yes, align = $100;
}
If an alignment is requested, the linker will add enough space to the output
file, so that the new segment starts at an address that is dividable by the
given number without a remainder. All addresses are adjusted accordingly. To
fill the unused space, bytes of zero are used, or, if the memory area has a
"fillval
" attribute, that value. Alignment is always needed, if you have
used the .ALIGN
command in the assembler. The alignment of a segment
must be equal or greater than the alignment used in the .ALIGN
command.
The linker will check that, and issue a warning, if the alignment of a segment
is lower than the alignment requested in an .ALIGN
command of one of the
modules making up this segment.
For a given segment you may also specify a fixed offset into a memory area or
a fixed start address. Use this if you want the code to run at a specific
address (a prominent case is the interrupt vector table which must go at
address $FFFA). Only one of ALIGN
or OFFSET
or START
may be
specified. If the directive creates empty space, it will be filled with zero,
of with the value specified with the "fillval
" attribute if one is given.
The linker will warn you if it is not possible to put the code at the
specified offset (this may happen if other segments in this area are too
large). Here's an example:
SEGMENTS {
VECTORS: load = ROM2, type = ro, start = $FFFA;
}
or (for the segment definitions from above)
SEGMENTS {
VECTORS: load = ROM2, type = ro, offset = $1FFA;
}
The "align
", "start
" and "offset
" attributes change placement
of the segment in the run memory area, because this is what is usually
desired. If load and run memory areas are equal (which is the case if only the
load memory area has been specified), the attributes will also work. There is
also an "align_load
" attribute that may be used to align the start of the
segment in the load memory area, in case different load and run areas have
been specified. There are no special attributes to set start or offset for
just the load memory area.
A "fillval
" attribute may not only be specified for a memory area, but
also for a segment. The value must be an integer between 0 and 255. It is used
as the fill value for space reserved by the assembler's .ALIGN
and .RES
commands. It is also used as the fill value for space between sections (part of a
segment that comes from one object file) caused by alignment, but not for
space that preceeds the first section.
To suppress the warning, the linker issues if it encounters a segment that is
not found in any of the input files, use "optional=yes
" as an additional
segment attribute. Be careful when using this attribute, because a missing
segment may be a sign of a problem, and if you're suppressing the warning,
there is no one left to tell you about it.
The FILES
section is used to support other formats than straight binary
(which is the default, so binary output files do not need an explicit entry
in the FILES
section).
The FILES
section lists output files and as only attribute the format of
each output file. Assigning binary format to the default output file would
look like this:
FILES {
%O: format = bin;
}
The only other available output format is the o65 format specified by Andre Fachat (see the 6502 binary relocation format specification). It is defined like this:
FILES {
%O: format = o65;
}
The necessary o65 attributes are defined in a special section labeled FORMAT.
The FORMAT
section is used to describe file formats. The default (binary)
format has currently no attributes, so, while it may be listed in this
section, the attribute list is empty. The second supported format,
o65,
has several attributes that may be defined here.
FORMATS {
o65: os = lunix, version = 0, type = small,
import = LUNIXKERNEL,
export = _main;
}
In addition to the MEMORY
and SEGMENTS
sections described above, the
linker has features that may be enabled by an additional section labeled
FEATURES
.
CONDES
is used to tell the linker to emit module constructor/destructor
tables.
FEATURES {
CONDES: segment = RODATA,
type = constructor,
label = __CONSTRUCTOR_TABLE__,
count = __CONSTRUCTOR_COUNT__;
}
The CONDES
feature has several attributes:
segment
This attribute tells the linker into which segment the table should be placed. If the segment does not exist, it is created.
type
Describes the type of the routines to place in the table. Type may be one of
the predefined types constructor
, destructor
, interruptor
, or
a numeric value between 0 and 6.
label
This specifies the label to use for the table. The label points to the start of the table in memory and may be used from within user-written code.
count
This is an optional attribute. If specified, an additional symbol is defined by the linker using the given name. The value of this symbol is the number of entries (not bytes) in the table. While this attribute is optional, it is often useful to define it.
order
An optional attribute that takes one of the keywords increasing
or
decreasing
as an argument. Specifies the sorting order of the entries
within the table. The default is increasing
, which means that the
entries are sorted with increasing priority (the first entry has the lowest
priority). "Priority" is the priority specified when declaring a symbol as
.CONDES
with the assembler, higher values mean higher priority. You may
change this behaviour by specifying decreasing
as the argument, the
order of entries is reversed in this case.
Please note that the order of entries with equal priority is undefined.
import
This attribute defines a valid symbol name, that is added as an import to the modules defining a constructor/destructor of the given type. This can be used to force linkage of a module if this module exports the requested symbol.
Without specifying the CONDES
feature, the linker will not create any
tables, even if there are condes
entries in the object files.
For more information see the .CONDES
command in the
ca65 manual.
STARTADDRESS
is used to set the default value for the start address,
which can be referenced by the %S
symbol. The builtin default for the
linker is $200.
FEATURES {
# Default start address is $1000
STARTADDRESS: default = $1000;
}
Please note that order is important: The default start address must be defined
before the %S
symbol is used in the config file. This does usually
mean, that the FEATURES
section has to go to the top of the config file.
The configuration file may also be used to define symbols used in the link stage or to force symbols imports. This is done in the SYMBOLS section. The symbol name is followed by a colon and symbol attributes.
The following symbol attributes are supported:
addrsize
The addrsize
attribute specifies the address size of the symbol and
may be one of
zp
, zeropage
or direct
abs
, absolute
or near
far
long
or dword
.Without this attribute, the default address size is abs
.
type
This attribute is mandatory. Its value is one of export
, import
or
weak
. export
means that the symbol is defined and exported from
the linker config. import
means that an import is generated for this
symbol, eventually forcing a module that exports this symbol to be included
in the output. weak
is similar as export
. However, the symbol is
only defined if it is not defined elsewhere.
value
This must only be given for symbols of type export
or weak
. It
defines the value of the symbol and may be an expression.
The following example defines the stack size for an application, but allows
the programmer to override the value by specifying --define
__STACKSIZE__=xxx
on the command line.
SYMBOLS {
# Define the stack size for the application
__STACKSIZE__: type = weak, value = $800;
}
The builtin config files do contain segments that have a special meaning for the compiler and the libraries that come with it. If you replace the builtin config files, you will need the following information.
The ONCE segment is used for initialization code run only once before execution reaches main() - provided that the program runs in RAM. You may for example add the ONCE segment to the heap in really memory constrained systems.
For the LOWCODE segment, it is guaranteed that it won't be banked out, so it is reachable at any time by interrupt handlers or similar.
This segment contains the startup code which initializes the C software stack and the libraries. It is placed in its own segment because it needs to be loaded at the lowest possible program address on several platforms.
The ZPSAVE segment contains the original values of the zeropage locations used by the ZEROPAGE segment. It is placed in its own segment because it must not be initialized.
ld65 (and all cc65 binutils) are (C) Copyright 1998-2005 Ullrich von Bassewitz. For usage of the binaries and/or sources the following conditions do apply:
This software is provided 'as-is', without any expressed or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:


Ais replaced by national representation of the full weekday name.
Sunday
ais replaced by national representation of the abbreviated weekday name.
Sun
Bis replaced by national representation of the full month name.
January
bis replaced by national representation of the abbreviated month name.
Jan
Dis equivalent to 'm/d/y'.
01/08/12
dis replaced by the day of the month as a decimal number (01-31).
08
eis replaced by the day of month as a decimal number (1-31); single digits are preceded by a blank.
8
Fis equivalent to 'Y-m-d'.
2012-01-08
His replaced by the hour (24-hour clock) as a decimal number (00-23).
19
Iis replaced by the hour (12-hour clock) as a decimal number (01-12).
07
kis replaced by the hour (24-hour clock) as a decimal number (0-23); single digits are preceded by a blank.
19
lis replaced by the hour (12-hour clock) as a decimal number (1-12); single digits are preceded by a blank.
7
Mis replaced by the minute as a decimal number (00-59).
34
mis replaced by the month as a decimal number (01-12).
01
nis replaced by a newline.
pis replaced by national representation of either 'ante meridiem' or 'post meridiem' as appropriate.
PM
Ris equivalent to 'H:M'.
19:34
ris equivalent to 'I:M:S p'.
07:34:13 PM
Sis replaced by the second as a decimal number (00-60).
13
Tis equivalent to 'H:M:S'.
19:34:13
tis replaced by a tab.
uis replaced by the weekday (Monday as the first day of the week) as a decimal number (1-7).
7
vis equivalent to 'e-b-Y'.
8-Jan-2012
wis replaced by the weekday (Sunday as the first day of the week) as a decimal
0
Xis replaced by national representation of the time.
19:34:13 GMT-0800 (PST)
xis replaced by national representation of the date.
Sun Jan 08 2012
Yis replaced by the year with century as a decimal number.
2012
yis replaced by the year without century as a decimal number (00-99).
12
Zis replaced by the time zone name.
PST


Making things ready...
DHIS 2
×
Everything is perfect
Template
OrgUnit Scheme
UID
Code
Help Tips:
Single or Mulitple xlsx data files can be uploaded using upload button.
Template xlsx file can be generated using download button, this is useful to compare the datasheet format with actual template.
Make sure that the template and datasheet mapping in sync, if find any descripencies please contact admin.
×
Confirmation
Are you sure that you want to continue?
×
Import Status
File
Event Import
Data Value Import