WHAKAPAPARANGA / LAYERS
Firstly we would like to acknowledge the essence of each of these concepts as they are, but we would also like to make clear that each layer exists in relationship to the others in many ways. It is that interconnectedness we hope these layers, and the stories you lay upon them, address through the words and voices of those who experience them.
1. te ao Māori
This layer shows and documents moments and stories that are relevant to the spatiality of te ao Māori, tangata whenua and indigenous geographies of Tamaki Makaurau. While te ao Māori is and will be central to many people in Aotearoa, we find the dominant ‘story’ often marginalises it. Therefore, descriptions in this layer can be the narrative not often heard of in mainstream discourse, but in actual fact are indeed the first narratives of or for historical events, places and people on this land. It can also include personal narratives of what it is like to be Māori in Tamaki Makaurau. We acknowledge that to be tangata whenua is to be of the land, and its geographies, and hence the stories about this interconnectedness are significantly valuable to us and to The Othered Auckland project.
2. tāhuhu kōrero / past-stories
This layer can be history, but also includes what is not his-story. It is reflective of omissions, manipulation and alteration of that history. It is the old stories of places and the land, of events and memories. It is impossible to evaluate the accuracy of some of these past-stories but we will assess them one by one with open hearts and minds and with ethical and social responsibilities, before publishing them on the map permanently. These stories are important to TOA as a means of looking backward in order to look forward.
Etymology of TOA
TOA is an abbreviation of The Othered Auckland. We believe that there is another city, beneath Auckland and its colonial legacies. In our view, to the dominant group, the othered Auckland is Tāmaki Makaurau. That is why we didn’t use the indigenous name of these territories here, to name and reinforce the process of colonisation of the land and life. Although, it was not our conscious decision, we are honoured that the word toa in Te Reo Māori refers to courage, bravery and boldness. Hopefully, we can do justice to this word and its meanings.
3. wāhine / women
This layer asks those who identify as women, whatever that means or looks like to you, to speak of those moments where your woman-ness has interacted with the space around you and vice-versa. Whether you have been labelled as such beyond your control, dismissed or welcomed, or whether you have been in your power in any given space - or whether this all happens at once. Certain spaces are often not safe for women, and other spaces deliberately give that power back to women, TOA hopes to see these and name them for what they are.
4. takatāpui / queer, trans, intersex
Conceptualisations of this project stemmed from a project called Queering The Map where any and all stories regarding one’s queerness, whatever that may look like to you, were able to be recorded in the place they occured. We hope this layer serves that purpose while also allowing for literal space to voice and visibilise these lives and experiences both in their beauty and their difficulty. This can also be an opportunity to indicate safe spaces in Tāmaki Makaurau.
5. āheitanga / accessibility
These moments are to acknowledge physically the ease, or severe lack thereof, of access in different parts of Tāmaki Makaurau. It is to reflect too on how these physical barriers or supports may result in othering part of our community. It is to imagine too the ways in which spaces could be created so any-body may interact as they please without difficulty or harm.
6. wairua / spiritual
These reflections are the interactions one has beyond the physical space around them, in whatever shape or form that occurs. We understand the interconnectedness of all the spaces around us in all its manifestations.
7. nōhanga / housing
We are in a housing crisis, TOA acknowledges the very long thread of deliberate decisions and causes that have led to a shortage of safe and warm homes - however that may look for a person or family. This layer is to discuss those decisions, to reflect on their results, and to describe the real life consequences, both physical and emotional in all its forms. It may be stories regarding a specific house or a location or a rohe that means home to you.
8. peinga / displacement
This layer may connect to other layers and ultimately describes any sense of non-belonging, through whatever process led to that removal. It may be the physical place which caused the displacement, or it could be where it happened, it may be historical or it may occur in the future. It may be your very arrival in Tāmaki Makaurau, it may be the historical trauma from being removed from your land.
9. tauiwi / immigrants
Part of the modern life, whether in favour of our well-being as a collective being on this planet, or an imposed disorder to create a profitable imbalance, is the phenomenon of immigration. This layer is a reflection of the immigrant’s life, the stories, moments, joys and pains. It is not a space to discuss the concept or politics of immigration, but a platform to eco the stories of immigration to gain a better understanding of the feeling of being a stranger, a local and a worldly being all at the same time, beyond the time and the place, in Tāmaki Makaurau.
10. whenua / nature
The land and all its descendants, Papatūānuku and her tamariki, her mokopuna. The trees, the plants, the shrubs, the bush, the flowers, the leaves, the flax, the roots, the sand, the dirt… all that is living around us, those whom are often not relegated as being, or a being. Here, to those of us who cannot speak for those beings, we ask that you reflect on your interactions with them.
11. ērā atu / other
A final layer for any-other who may not fit into the previous categories, or fits into them all at once, or for something we have not yet thought of or experienced.
This part of the project is a work in progress, so bare with us while we are trying to grasp the scale and complexity of the project in order to communicate all the elements more clearly. Meanwhile, feel free to help us with you kind suggestions and feedback.


AMS 360 Inc. can provide your company with complete training and consultation services, tailored to fit your needs. All services are available during typical business hours, afterhours, and on weekends.
Evening classes are typically scheduled in four-hour blocks. Below are the training and service options for core products of the digital manufacturing group: PowerMILL® PowerSHAPE® PowerINSPECT® FeatureCAM®
• Proven curriculum delivered by a certified trainer
• Available to individuals or small groups (minimum class size required)
• Days / evenings / weekends
• 3 axis and/or 5 axis
• Training as above dedicated to only your trainees
• Custom models, topics, and/or specialty applications available (must be coordinated in advance)
• Create or customize your machine tool simulation data for complete toolpath verification
• Create or customize your post processor
• 3, 4, or 5 axis development available
• Customize toolbar ribbons and commands
• Automate repetitive manual programming sequences
• Construct powerful computing sequences with error-handling and subroutines


Engifest
Focus on creating amazing user experiences and forget complex infrastructure. Instantly add a powerful cloud database, push notification services, and analytics tracking to your app. Choose from over thirteen native SDKs for mobile, desktop, and IoT devices and discover all that Parse has to offer.
Event hosted by : -
Himanshu Lakra


Rewire
Your brain for success
Preptitude is a tried and tested approach for effectively training your brain and prepare it for any intellectual test
Introduce a brand new approach to practicing for any test, on the go
Runs on a wide range of platforms from mobile to desktop
Runs on a wide range of platforms from mobile to desktop


Handle multi touch events inside your iOS applications.
First of all, add the multitouch module to your applications tiapp.xml by adding the following
line inside the <modules>
tag:
<module version="1.2">org.urish.titanium.multitouch</module>
To load the module, add the following line to your javascript code:
require("org.urish.titanium.multitouch");
You can enable multitouch for any window or view. First of all, set the 'multitouch' property of the view to true (see example below). Then add listeners to the standard touchstart/touchmove/touchend/touchcancel events. These events will include a new property named "points".
The new "points" property is actually a dictionary with information about the touches. Each touch has a unique id which can be used to track the specific touch across several touch events. The dictionary contains the touch id as the key of the entry, and an object contains 'x' and 'y' properties as the value.
The 'x' and 'y' properties for each touch are relative to the view. You can also get the global coordinates of the touch event by looking into the 'globalPoint' property.
require("org.urish.titanium.multitouch");
win.multitouch=true;
win.addEventListener("touchstart", function(event) {
Ti.API.info("Touches started, points: " + JSON.stringify(event.points));
// Sample code for interating the points:
for (var pointName in event.points) {
Ti.API.info("Point " + pointName + " x=" + event.points[pointName].x
+ ", y=" + event.points[pointName].y);
}
// You can use the above for the other events as well (touchmove,
// touchend, touchcancel). Note that event.points is not an array,
// so you should iterate it like the example above, and not as an array.
});
win.addEventListener("touchmove", function(event) {
Ti.API.info("Touches moved, points: " + JSON.stringify(event.points));
});
win.addEventListener("touchend", function(event) {
Ti.API.info("Touches ended, points: " + JSON.stringify(event.points));
});
win.addEventListener("touchcanceled", function(event) {
Ti.API.info("Touches canceled, points: " + JSON.stringify(event.points));
});
For an extended example, please check the provided app.js (under the example directory).
The TiMultiTouch module is used in the Zampona iOS application. The application resembles a peruvian panflute and uses the TiMultiTouch to enable playing two or more notes simultaneously. You can get it for free from Zampona on iTunes.
Copyright (C) 2011, 2012 Uri Shaked<EMAIL_ADDRESS>Some portions of the code are based on the original TiMultitouch module by masuidrive.
Homepage: Uri Shaked. Github page: https://www.github.org/urish.
MIT License


Calculates the missing dependencies of the given plugins. The given plugins and the plugins in the registry are eligible to satisfy dependencies.
The plugins whose dependencies should be checked.
The plugin registry containing all registered plugins.
An array of names of missing plugins.
Builds a dependency graph from the given plugins.
The plugins from which to build the graph.
The completed dependency graph.
Calls the optional init
function of each plugin.
The plugins to initialize.
Deeply merges the given dependency graphs without modifying the original graphs. When a property exists in more than one graph, the corresponding arrays are concatenated.
The dependency graphs to merge.
The merged dependency graph.
Calls the optional ready
function of each plugin.
The plugins to ready.
Calls the register
function of each plugin. The values returned by
each plugin are added to the given registry.
The plugins to register.
The registry into which to add the plugins' exposed values.
The directory into which to add the plugins.
An object containing the keys and values of the new items added to the registry.
Removes the specified names from the given dependency graph. The corresponding properties are deleted and the dependency lists are updated. The original graph is not modified. It is safe to attempt to remove a name that is not in the graph.
The graph to remove plugins from.
The names of the plugins to remove from the graph.
The resulting graph with the given names removed.
Unregisters the plugins with the given names from the given registry and directory. It is safe to attempt to unregister a plugin that is not registered.
The names of the plugins to unregister.
The registry from which to unregister the plugin's exposed value.
The directory from which to unregister the plugin.
Generated using TypeDoc
GroupBy Elements Core
This package contains the GB Elements Core class and related plugin interfaces.
Usage
To use Core, simply instantiate it:
const core = new Core();
Registering a plugin
To register one or more plugins with Core, instantiate the plugins, then pass them to
Core.register()
:const core = new Core(); const pluginA = new PluginA(); const pluginB = new PluginB();
core.register([pluginA, pluginB]);
A plugin may take configuration options in its constructor. Refer to the plugin's documentation for details.


Instructions
Write captions for pictures.
In this task, you will be shown a picture and your task is to write a grammatically correct sentence describing the
contents of the picture
Here are the pictures we would like you to write captions for:
Write a caption describing the contents of the image:
Back
/
Next
{% include "easyturk.html" %}


Doctor Lookup
Enter a doctor's name:
Get Doctor Information!
Enter a symptom:
Find Doctors who can treat this!


SceneCat(DATA)
DATA is a MxN or MxNx3 matrix
SceneCat()
SceneCat(DIRECTORY)
This is the main window where annotations are drawn.
This is the window where the below mentioned keybaord shortcuts work.
Annotations can be selected by clicking on them in the main window. This envokes same behavior as selecting the annotation from the table.
Annotation drawing utilized Matlab's roipoly.m. See Matlab help on roipoly for more information.
Right-clicking on an annototation actives it's context menu
Add a new polygon and table entry
Edit the polygon of currently seletected row
Delete the entry of currently seletected row
Save the current set of annotations
Load a set of annotation from a previously save MAT-file
Shade all the current polygons
Help is here
| Keys | Action |
|---|---|
| PAN UP | |
| PAN DOWN | |
| PAN LEFT | |
| PAN RIGHT | |
| ZOOM IN | |
| ZOOM OUT | |
| + | ZOOM RESET |
| Reset drawing state, if ADD button stops working... | |
| + | ADD |
| + | DELETE |
| Contrast Adjustment (Only available for single channel data) | |
| Reset color axis | |
| Decrease lower limit of color axis | |
| Increase lower limit of color axis | |
| Decrease upper limit of color axis | |
| Increase upper limit of color axis |


List of arbitrary text tags. Tags may be any valid string; default is the
empty list.
Tags can be used on any rule; but tags are most useful
on test and test_suite
rules. Tags on non-test rules
are only useful to humans and/or external programs.
Tags are generally used to annotate a test's role in your debug
and release process. Typically, tags are most useful for C++ and
Python tests, which
lack any runtime annotation ability. The use of tags and size elements
gives flexibility in assembling suites of tests based around codebase
check-in policy.
A few tags have special meaning to the build tool, such as indicating that a particular test cannot be run remotely, for example. Consult the Bazel documentation for details.


0
[수원 FC]
0
[인천 FC]
0
TOTAL SHOTS
0
0
SHOTS ON TARGET
0
0
SHOTS OFF TARGET
0
0
SAVES
0
0
CORNER
0
0
OFFSIDES
0
0
FOULS
0
0
CARDS
0


| Draws a rectangular area of an image at the designated location without transparency. |
| image = variable holding the image handle x = x location on the screen to draw the image y = y location on the screen to draw the image rect_x = starting x location within the image to draw rect_y = starting y location within the image to draw rect_width = the height of the area to draw rect_height = the width of the area to draw frame = optional frame number of image to draw |
Command Description:
| This command will let you draw a rectangular PORTION of an image to the designated location on the screen. The transparent/masked portions of the original image will be ignored and drawn with the image. This is handy if you are doing something like revealing part of a screen when the player uncovers something (think QIX). You could load the 'picture' into an image, then when the player clears a rectangular region, you could paste that portion of the final image onto the playfield. If you want to draw the image portion with transparency or masking, use DrawImageRect instead. |
Example:
| ; DrawBlockRect Example ; Turn on graphics mode Graphics 640,480,16 ; Create new empty graphic to store our circle in gfxCircle=CreateImage(50,50) ; Draw the circle image ; Set drawing operations to point to our new empty graphic SetBuffer ImageBuffer(gfxCircle) Color 255,0,0 ; Note the extra space between the circle and the edge of the graphic Oval 10,10,30,30,1 SetBuffer FrontBuffer() ; Set the screen to white so you can see the transparent areas ClsColor 255,255,255 Cls ; Let's draw portions of the circle randomly While Not KeyHit(1) ; We take random sized portions of the circle and put them ; at a random location ... wash, rinse, and repeat DrawBlockRect gfxCircle,Rnd(640),Rnd(480),0,0,Rnd(50),Rnd(50),0 Delay 100 Wend |


YOUR NAME's CS132 programs
Main Page
Namespaces
Classes
Files
bool testing::TestCase::Failed
(
)
const
inline
Definition at line
838
of file
gtest.h
.
Referenced by
testing::internal::Random::Generate()
.
838
{
return
failed_test_count
() > 0; }
testing::TestCase::failed_test_count
int failed_test_count() const
Definition:
gtest.cc:2682
Here is the caller graph for this function:
testing
TestCase
Generated on Mon Oct 21 2019 15:37:39 for YOUR NAME's CS132 programs by
1.8.11


Welcome to the
{{vm.meeting.title}}
{{vm.meeting.subtitle}}
Use this tool to give direct insights to individual participants in this meeting.
Share your Insights on the meeting for future consideration and planning.
Use the button in the top bar to search for specific attendees .
Then use the Menu next to the attendee's name and select "Write a new insight" to input the insight on the tool.
Use the Home button to come back to this page and start over.
Use the button to load the newest insights.


Reports use of generic classes with omitted type parameters. Such raw use of generic types is valid
in Java, but it defeats the purpose of type parameters and may mask bugs. This inspection mirrors the
rawtypes warning of javac.
Using the inspection options, you can ignore the following cases:
- when raw types are used in objects' constuction
- when raw types are used in type casts
- when a type parameter will fail to compile (for example when creating an array or overriding a library method)
- when type parameters are used in parameters of overriding methods
- when a quick-fix is not available
This inspection only reports if the language level of the project or module is 5 or higher


Salad product recall over E. coli bacteria impacts 22 states
by KNOESWEDESBORO, N.J. (AP) — The U.S. Department of Agriculture says thousands of pounds of salad products are being recalled due to a possible E. coli contamination.
The department says Missa Bay, LLC from Swedesboro, New Jersey, is recalling more than 75,000 pounds (34,020 kilograms) of salad products that contain meat or poultry because the lettuce may be contaminated with a strain of E. coli.
The products were sold on Oct. 14 through Oct. 16 in Alabama, Connecticut, Florida, Georgia, Illinois, Indiana, Louisiana, Maine, Maryland, Massachusetts, Michigan, Minnesota, Mississippi, Missouri, New Jersey, New York, North Carolina, Ohio, Pennsylvania, South Carolina, Virginia, and Wisconsin.
Authorities say the Maryland Department of Health tested an unopened salad product with chicken and the lettuce came back positive for a strain of E. coli bacteria.
The Centers for Disease Control says E. coli often causes diarrhea and vomiting.
Copyright 2019 Associated Press. All rights reserved.


Engagement
Mehendi
Celebrate love with some cakes!
Reception
Muhurtham
Bridal Essence
Dining
DhandiyaNights


Master Galadrid:
No matter your race or class, you must acquire a solid foundation before you can even think of using more advanced techniques. That's just common sense, isn't it?
Learn skills.
Ask about Skill Enchanting.
Quest


The Wheel of Time turns, and Ages come and pass, leaving memories that become legend. Legend fades to myth, and even myth is long forgotten when the Age that gave it birth comes again. In one Age, called the Third Age by some, an Age yet to come, an Age long past, a wind rose in the great forest called Braem Wood. The wind was not the beginning. There are neither beginnings nor endings to the turning of the Wheel of Time. But it was a beginning.
North and east the wind blew as the searing sun rose higher in a cloudless sky, north and east through parched trees with brown leaves and bare branches, through scattered villages where the air shimmered from the heat. The wind brought no relief, no hint of rain, much less snow. North and east it blew, past an ancient arch of finely worked stone that some said had been a gateway to a great city and others a monument to some long forgotten battle. Only weathered, illegible remnants of carving remained on the massive stones, mutely recalling the lost glories of storied Coremanda. A few wagons trundled by in sight of the arch, along the Tar Valon Road, and folk afoot shielded their eyes from dust raised by hooves and wagon wheels and driven by the wind. Most had no idea where they were going, only that the world seemed to turn somersaults, all order ending where it was not gone already. Fear drove some on, while others were drawn by something they could not quite see and did not understand, and most of them were afraid, too.
Onward the wind traveled, across the gray-green River Erinin, heeling ships that still carried trade north and south, for there had to be trade even in these days, though none could be sure where it was safe to trade. East of the river, the forests began to thin, giving way eventually to low rolling hills covered in brown, tinder-dry grass and dotted sparsely with small clumps of trees. Atop one of those hills stood a circle of wagons, many with the canvas scorched or else completely burned away from the iron hoops. On a makeshift flagstaff, trimmed from a young tree dead in the drought and lashed to a bare wagon hoop for more height, waved a crimson banner, a black-and-white disc in its heart. The Banner of Light, some called it, or al’Thor’s Banner. Others had darker names, and shivered as they spoke them in whispers. The wind shook the banner hard and was gone quickly, as if glad to be away.
Perrin Aybara sat on the ground with his broad back against a wagon wheel, wishing the wind lingered. It had been cooler for a moment. And the wind from the south had cleared the scent of death from his nostrils, a scent that reminded him where he was supposed to be, the last place he wanted to be. Much better here, inside the wagon circle, his back to the north, where he could forget after a fashion. The surviving wagons had been hauled up to the hilltop yesterday, in the afternoon, once men could find strength to do more than thank the Light they still breathed. Now the sun climbed again, and the heat with it.
Irritably, he scratched at his short curly beard; the more he sweated, the more it itched. Sweat rolled down the face of every man he could see except the Aiel, and water lay nearly a mile away to the north now. But so did the horrors, and the smells. Most considered it a fair trade. He should have been doing his duty, yet the touch of guilt did not move him. Today was High Chasaline, and back home in the Two Rivers there would be feasting all day and dancing all night; the Day of Reflection, when you were supposed to remember all the good things in your life and anyone who voiced a complaint could find a bucket of water upended over his head to wash away bad luck. Not something anybody wanted when the weather was cold, as it should be; a bucket of water would be a pleasure now. For a man lucky to be alive, he found it remarkably hard to pull up any good thoughts. He had learned things about himself yesterday. Or maybe it had been this morning, after it was all done.
He could sense a few of the wolves still, a handful of those that survived and were now on their way elsewhere, far from here, far from men. The wolves were still the talk of the camp, uneasy speculation over where they had appeared from and why. A few believed Rand had called them. Most thought the Aes Sedai had. The Aes Sedai did not say what they thought. No blame came from the wolves—what had happened, had happened—but he could not match their fatalism. They had come because he called them. Shoulders wide enough to make him seem shorter than he was slumped under the weight of responsibility. Now and then he heard other wolves, that had not come, speak with scorn to those that had: this was what came of mixing with the two-legs. Nothing else could be expected.
It was a strain to keep his thoughts to himself. He wanted to be home, in the Two Rivers. Small chance of that, perhaps ever again. He wanted to howl that the scornful ones were right. He wanted to be with his wife anywhere at all, and everything the way it was before. The chances of which seemed little better, maybe worse. Far more than the yearning for home, more even than the wolves, worry about Faile ate inside him like a ferret trying to burrow out of his middle. She had actually seemed glad to see him leave Cairhien. What was he to do about her? He could not think of words to describe how much he loved his wife, and needed her, but she was jealous where she had no cause, hurt where he had done nothing, angry where he could not see why. He must do something, but what? The answer eluded him. Careful thought was all he had, while Faile was flashing quicksilver.
“The Aiel should put some clothes on them,” Aram muttered primly, scowling at the ground. He squatted nearby, patiently holding the reins of a rangy gray gelding; he seldom went far from Perrin. The sword strapped to his back jarred with his green-striped Tinker coat, hanging undone for the heat. A rolled kerchief tied around his forehead kept sweat from his eyes. Once Perrin had thought him almost too good-looking for a man. A bleak darkness had settled in him, though, and now he wore a scowl as often as not. “It isn’t decent, Lord Perrin.”
Perrin put aside thoughts of Faile reluctantly. With time, he could puzzle it out. He had to. Somehow. “It is their way, Aram.”
Aram grimaced as if he might spit. “Well, it isn’t a decent way. It keeps them under control, I suppose—nobody would run far to make trouble like that—but it isn’t decent.”
There were Aiel all over the place, of course. Tall, aloof men in grays and browns and greens, their only bit of color the scarlet strip of cloth tied around their temples, with the black-and-white disc on their foreheads. Siswai’aman, they called themselves. Sometimes that word tickled the edge of his memory, like a word he should know. Ask one of the Aielmen, and he looked as if you had babbled nonsense. But then, they ignored the strips of cloth, too. No Maiden of the Spear wore the scarlet headband. Whether white-haired or looking barely old enough to leave her mother, every Maiden stalked about giving the siswai’aman challenging stares that seemed somehow self-satisfied, while the men looked back flat-eyed, with a smell almost of hunger, a matter of jealousy by the scent of all of them, though over what Perrin could not begin to imagine. Whatever it was, it was not new, and it did not seem likely to come to blows. A few of the Wise Ones were inside the wagons as well, in bulky skirts and white blouses, wearing their dark shawls in defiance of the heat, glittering bracelets and necklaces of gold and ivory making up for the plainness of the rest of their clothes. Some appeared amused by the Maidens and the siswai’aman, and others exasperated. All of them—Wise Ones, Maidens and siswai’aman—ignored the Shaido the way Perrin would have a stool or a rug.
The Aiel had taken two hundred or so Shaido prisoners yesterday, men and Maidens—not many, considering the numbers involved—and they moved about freely. In a manner of speaking. Perrin would have been a lot more comfortable had they been guarded. And clothed. Instead, they fetched water and ran errands, naked as the day they were born. With other Aiel, they were meek as mice. Anyone else received a proudly defiant stare for noticing them. Perrin was not the only one who tried not to notice them, and Aram not the only one to mutter. A good many of the Two Rivers men in camp did one or both. A good many of the Cairhienin nearly had apoplexy whenever they saw one of the Shaido. The Mayeners just shook their heads as though it were all a joke. And ogled the women. They had as little shame as the Aiel, the Mayeners.
“Gaul explained it to me, Aram.  About ji’e’toh and serving a year and a day and all that?” The other man nodded, which was a good thing. Perrin did not know much himself. Gaul’s explanations of Aiel ways often left him more confused. Gaul always thought it all self-evident. “Well, gai’shain aren’t allowed to wear anything one of the algai’d’siswai might wear—that means ‘spear fighters,’ ” he added at Aram’s questioning frown. Suddenly he realized he was looking straight at one of the Shaido as she trotted in his general direction, a tall young woman, golden-haired and pretty despite a long thin scar down her cheek and other scars elsewhere. Very pretty and very naked. Clearing his throat roughly, he pulled his eyes away. He could feel his face heating.  Gai’shain wear white robes, and they don’t have any here. It’s just their way.” Burn Gaul and burn his explanations, he thought. They could cover them with something!
“Perrin Goldeneyes,” said a woman’s voice, “Carahuin sends to know whether you wish water.” Aram’s face went purple, and he jerked himself around in his squat, presenting his back to her.
“No, thank you.” Perrin did not need to look up to know it was the golden-haired Shaido woman. He kept peering off at nothing in another direction. Aiel had a peculiar sense of humor, and Maidens of the Spear—Carahuin was a Maiden—had the most peculiar. They had quickly seen how the wetlanders reacted to the Shaido—they would have needed to be blind not to—and suddenly gai’shain were being sent to wetlanders left and right, and Aiel all but rolling on the ground at the blushes and stammers and even the shouting. He was sure that Carahuin and her friends were watching now.
Abruptly a thought struck him. The Mayeners were seldom bothered this way. A handful of Cairhienin plainly enjoyed looking, if not so openly as the Mayeners, and some of the older Two Rivers men, who should have known better. The point was, none of them had had a second spurious message that he knew of. Those who reacted the most on the other hand . . . Cairhienin, who had shouted the loudest about indecency, and two or three of the younger Two Rivers men, who stammered and blushed so hard they looked ready to melt, had been pestered until they fled the wagons entirely . . .
With an effort Perrin looked up at the gai’shain’s face. At her eyes. Focus on her eyes, he thought frantically. They were green, and large, and not at all meek. Her scent was pure fury. “Thank Carahuin for me, and tell her you could oil my spare saddle, if she doesn’t mind. And I don’t have a clean shirt. If she wouldn’t mind you doing some laundry?”
“She will not mind,” the woman said in a tight voice, then turned and trotted off.
 Light, Aram was right! But with luck, he might just have stopped any more visitations. He would have to point this out to Aram, and the Two Rivers men. Maybe the Cairhienin would listen too.
“What are we going to do about them, Lord Perrin?” Still looking away, Aram no longer spoke of gai’shain.
“That is Rand’s to decide,” Perrin said slowly, satisfaction fading. It might be odd to think of people wandering about naked as a small problem, but this was definitely a bigger. And one he had been avoiding as hard as he had what lay to the north.
On the far side of the wagon circle, nearly two dozen women sat on the ground. All well-dressed for travel, many wore silk, most with light linen dustcloaks, but not a bead of sweat showed on any face. Three appeared young enough that he might have asked them for a dance before he married Faile.
If they weren’t Aes Sedai, anyway, he thought wryly. Once he had danced with an Aes Sedai, and nearly swallowed his tongue when he realized who he swung about. And she had been a friend, if that word applied to Aes Sedai. How new does an Aes Sedai have to be for me to put an age to her? The others looked ageless, of course; maybe in their twenties, maybe their forties, changing from one glance to the next, always uncertain. That was what their faces said, though several showed gray in their hair. You just could not tell with Aes Sedai. About anything.
“At least those are no danger anymore,” Aram said, jerking his head toward three of the sisters a little apart from the rest.
One wept, face on her knees; the other two stared haggardly at nothing, one of them plucking aimlessly at her skirt. They had been much the same since yesterday; at least none was screaming any longer. If Perrin had the straight of it, which he was not sure he did, they had been stilled somehow when Rand broke free. They would never channel the One Power again. To Aes Sedai, it was probably better to be dead.
He would have expected the other Aes Sedai to comfort them, care for them somehow, but most ignored the three entirely, although a little too studied in looking anywhere and everywhere else. For that matter, the stilled Aes Sedai refused to acknowledge the rest, either. In the beginning, at least, a few of the other sisters had approached, each by herself, calm to the eye yet smelling sharply of aversion and reluctance, but they got nothing for their pains, not word or glance. None had gone near this morning.
Perrin shook his head. The Aes Sedai seemed to do a lot of ignoring of what they did not want to admit. For instance, the black-coated men standing over them. There was an Asha’man for each sister, even the three who had been stilled, and they never seemed to blink. For their part, the Aes Sedai looked past the Asha’man, or through them; they might as well not have existed.
It was quite a trick. He could not make himself disregard the Asha’man, and he was not under their guard. They ranged from fuzz-cheeked boys to gray-haired, balding gansers, and it was not their grim, high-collared black coats or the sword each wore at his hip that made them dangerous. Every Asha’man could channel, and somehow they were keeping the Aes Sedai from channeling. Men who could wield the One Power, a thing of nightmares. Rand could, of course, but he was Rand, and the Dragon Reborn besides. These fellows made Perrin’s hackles rise.
The captive Aes Sedai’s surviving Warders sat some distance off, under their own guard. Thirty or so of Lord Dobraine’s armsmen in bell-shaped Cairhienin helmets and as many Mayener Winged Guards in red breastplates, each sharp-eyed as if guarding leopards. A good attitude, under the circumstances. More Warders than there were Aes Sedai; a number of the prisoners were Green Ajah, apparently. More guards than Warders, a good many more, and maybe few enough at that.
“The Light send we don’t see any more grief from that lot,” Perrin muttered. Twice during the night the Warders had tried to break free. In truth, those outbreaks had been suppressed more by the Asha’man than by the Cairhienin or Mayeners, and they had not been gentle. None of the Warders had been killed, but at least a dozen nursed broken bones none of the sisters had yet been allowed to Heal.
“If the Lord Dragon cannot make the decision,” Aram said quietly, “maybe it should be made by somebody else. To protect him.”
Perrin gave him a sidelong look. “What decision? The sisters told them not to make another attempt, and they’ll obey their Aes Sedai.” Broken bones or no, unarmed as they were, hands tied behind their backs, the Warders still looked like a wolfpack awaiting the lead wolf’s command to attack. None would rest easy until his Aes Sedai was free, maybe until all of the sisters were free. Aes Sedai and Warders: a stack of well-aged oak, ready for a flame. But even Warders and Aes Sedai had proved no match for Asha’man.
“I did not mean the Warders.” Aram hesitated, then shuffled closer to Perrin and lowered his voice further, to a hoarse whisper. “The Aes Sedai kidnapped the Lord Dragon. He can’t trust them, not ever, but he won’t do what he has to, either. If they died before he knew it—”
“What are you saying?” Perrin almost choked as he sat bolt upright. Not for the first time, he wondered whether there was any Tinker left in the other man. “They’re helpless, Aram! Helpless women!”
“They are Aes Sedai.” Dark eyes met Perrin’s golden stare levelly. “They cannot be trusted, and they cannot be turned loose. How long can Aes Sedai be held against their will? They’ve been doing what they do far longer than the Asha’man. They must know more. They’re a danger to the Lord Dragon, and to you, Lord Perrin. I have seen them look at you.”
Across the wagon circle, the sisters were talking among themselves in whispers even Perrin could not hear, mouths held close to ears. Now and again one did look at him and Aram. At him, not Aram. He had caught a double handful of names. Nesune Bihara. Erian Boroleos and Katerine Alruddin. Coiren Saeldain, Sarene Nemdahl and Elza Penfell. Janine Pavlara, Beldeine Nyram, Marith Riven. Those last were the young sisters, but young or ageless, they watched him with faces so serene it seemed they had the upper hand despite the Asha’man. Defeating Aes Sedai was not easy; making them admit defeat lay on the far side of impossible.
He forced his hands to unknot and rest on his knees, giving an appearance of calm he was nowhere near feeling. They knew he was ta’veren, one of those few the Pattern would shape itself around for a time. Worse, they knew he was tied to Rand in some way nobody understood, least of all himself or Rand. Or Mat; Mat was in that tangle, too, another ta’veren, though neither of them as strongly as Rand. Given half a chance those women would have him—and Mat—inside the White Tower as fast as they would Rand, tethered like goats until the lion came. And they had kidnapped Rand, mistreated him. Aram was right about one thing; they could not be trusted. But what Aram suggested—he would not—could not!—countenance such a thing. The thought made him queasy.
“I’ll hear no more of that,” he growled.  “Not a word, Aram, do you hear me? Not one word!”
“As my Lord Perrin commands,” Aram murmured, inclining his head.
Perrin wished he could see the man’s face.  That was the worst of it. There had been no anger scent even when Aram suggested murder.
A pair of Two Rivers men climbed up on the wheels of the next wagon, peering across the wagon bed and down the hill toward the north. Each wore a bristling quiver on his right hip and a stout, long-bladed knife, almost a short-sword, on his left. A good three hundred men from home had followed Perrin here. He cursed the first to call him Lord Perrin, cursed the day he had stopped trying to quash it. Even with the murmurs and noises usual in a camp this size, he had no trouble hearing the pair.
Tod al’Caar, a year younger than Perrin, let out a long breath, as if seeing what lay below for the first time. Perrin could almost sense the lanky man’s lantern jaw working. Tod’s mother had willingly let him go only for the honor of her son following Perrin Goldeneyes. “A famous victory,” Tod said finally. “That’s what we won. Wasn’t it, Jondyn?”
Grizzled Jondyn Barran, gnarled as an oak root, was one of the few older men among the three hundred. A better bowshot than anyone in the Two Rivers except Master al’Thor and a better hunter than anyone at all, he was one of the Two Rivers’ less distinguished residents. Jondyn had not worked a day more than he had to since he was old enough to leave his father’s farm. The forests and the hunt were all he cared about, that and drinking too much at feastdays. Now he spat loudly. “If you say so, boy.  And welcome to it, I say.  “I wouldn’t mind being one myself.” That sounded more boast and bluff than truth. Smelled it, too; without looking, Perrin was sure he was licking his lips. Likely Tod’s mother had used tales of men who could channel to frighten him not so many years ago. “I mean to say, Rand—that is, the Lord Dragon—it still sounds odd, doesn’t it, Rand al’Thor being the Dragon Reborn and all?” Tod laughed, a short, uneasy sound. “Well, he can channel, and it doesn’t seem so—he doesn’t—I mean . . . ” He swallowed loudly. “Besides, what could we have done about all those Aes Sedai without them?” That came out in a whisper. He smelled afraid now. “Jondyn, what are we going to do? I mean, Aes Sedai prisoners?”
The older man spat again, louder than before. He did not bother to lower his voice, either. Jondyn always said what he thought no matter who heard, another reason for his bad repute. “Better for us if they’d all died yesterday, boy. We’ll pay for that before it’s done. Mark me, we’ll pay large.”
 First Aram, and now Jondyn and Tod, if not so directly. Burn Jondyn! No, the man might make Mat look industrious, but if he spoke it, others thought it. No Two Rivers man would willingly harm a woman, but who else wished the Aes Sedai prisoners dead? And who might try to achieve the wish?
He scanned the wagon circle uneasily. The thought that he might have to protect the Aes Sedai prisoners was not pleasant, but he did not shirk it. He had little fondness for any Aes Sedai, least of all for these, but he had grown up in the unspoken certainty that a man would put himself at risk to protect a woman as far she allowed; whether he liked her or even knew her was beside the point. True, an Aes Sedai could tie any man she chose into a knot nine ways from next feastday, but cut off from the Power, they became like anyone else. That was the struggle whenever he looked at them. Two dozen Aes Sedai. Two dozen women who might not know how to defend themselves without the Power.
For a bit he studied the Asha’man guards, every one wearing a face like grim death. Except the three overseeing the stilled women. They tried to appear as somber as the rest, but under the attempt lay something else. Satisfaction, maybe. If only he was close enough to catch a scent of them. Any Aes Sedai was a threat to the Asha’man. Perhaps the reverse was true, too. Perhaps they would only still them. From the little he had picked up, stilling an Aes Sedai amounted to a killing that just took a few years for the corpse to lie down.
Whatever the case, he decided reluctantly, he had to leave the Asha’man to Rand. They spoke only to each other and the prisoners, and Perrin doubted they would listen to anyone but Rand. The question was, what would Rand say? And what could Perrin do if he said the wrong thing?
Putting that problem aside, he scratched his beard with one finger. The Cairhienin were too nervous about Aes Sedai to consider harming them, and the Mayeners too respectful, but he would keep an eye on them anyway. Who would have thought Jondyn would go as far as he had? Among the Cairhienin or Mayeners, he possessed some influence, though it would surely vanish if they once thought. He was really just a blacksmith, after all. That left the Aiel. Perrin sighed. He was not certain how much influence even Rand truly had with the Aiel.
It was difficult picking out individual scents with so many people around, but he had grown used to telling as much by smells as by what his eyes told him. The siswai’aman who came close enough smelled calm but alert, a smooth, strong scent. They hardly appeared to notice the Aes Sedai. The Maidens’ aromas were spiky with suppressed fury and grew spikier when they looked at the prisoners. And the Wise Ones . . .
Every Wise One who had come here from Cairhien was able to channel, though none had the ageless face. He supposed they used the One Power too seldom. Still, smooth-cheeked like Edarra or as leathery-faced as white-haired Sorilea, they carried themselves with a self-possession easily matching the Aes Sedai’s. Graceful women for the most part, most of them tall, as nearly all Aiel were, they seemed to ignore the sisters completely.
Sorilea’s eyes passed across the prisoners without pausing, and she went right on talking softly to Edarra and another Wise One, a lean, yellow-haired woman he did not know by name. If only he could make out what they were saying. They walked by, not a line changing on those three unruffled faces, but their scents were another matter. When Sorilea’s gaze swept over the Aes Sedai, the smell of her went cold and distant, grim and purposeful, and as she spoke to the other two, their scents changed to match hers.

“Trouble?” Aram asked, sitting up straighter on his heels, right hand poised to dart for the wolfhead-pommeled sword hilt jutting above his shoulder. He had become very good with that sword in a very short time, and he was never loath to use it.
“There’s no trouble, Aram.” That was not quite a lie. Jolted out of his glum brooding, Perrin really looked at the others for the first time. At all of them together. He did not like what he saw, and the Aes Sedai were only part.
Cairhienin and Mayeners watched Aiel suspiciously, which was no more than the Aiel’s return suspicion, especially toward the Cairhienin. No real surprise there. Aiel did have a certain reputation, after all, for being none too friendly to anyone born this side of the Spine of the World, Cairhienin least of all. Simple truth was, Aiel and Cairhienin hated each other about as hard as it was possible to hate. Neither side had really put their enmity aside—the best that could be said was that it was on a loose leash—yet up to now he had been convinced they would hold it in. For Rand’s sake if no other reason. A mood hung in the camp, though, a tension that had wound everyone tight. Rand was free now, and temporary alliances were just that, after all; temporary. Aiel hefted their spears when they looked at the Cairhienin, and the Cairhienin grimly fingered their swords. So did the Mayeners; they had no quarrel with the Aiel, had never fought them except for the Aiel War when everybody had, but if it came to a fight, there was little doubt which side they would be on. The Two Rivers men, too, probably.
The dark mood had settled deepest into the Asha’man and the Wise Ones, though. The black-coated men paid no more heed to the Maidens and the siswai’aman than to Cairhienin or Mayeners or Two Rivers men, but they studied the Wise Ones with faces almost as dark as those they directed at the Aes Sedai. Very likely they made small distinction between one woman who could wield the Power and another. Any could be an enemy and dangerous; thirteen together were deadly dangerous, and there were better than ninety Wise Ones in the camp or nearby. Fewer than half the number of Asha’man, but still enough to do damage if they chose. Women who could channel, yet they seemed to follow Rand; they seemed to follow Rand, yet they were women who could channel.
The Wise Ones looked at the Asha’man only a trifle less coldly than they did the Aes Sedai. The Asha’man were men who could channel, but they followed Rand; they followed Rand, but . . . Rand was a special case. According to Gaul, his channeling was not mentioned in the prophecies about their Car’a’carn, but the Aiel seemed to pretend that inconvenient fact did not exist. The Asha’man were not in those prophecies at all, though. It must be like discovering you had a pride of rabid lions fighting on your side. How long would they remain loyal? Maybe it would be better to put them down now.
 Think of the good things on High Chasaline. Burn me, he thought wryly, I should have gone with Rand. No, it was best to know, and better soon than late. But what in the Light was he to do? If the Aiel and the Cairhienin and Mayeners turned on one another, or worse, the Asha’man and the Wise Ones . . .
“Your horse, Lord Perrin. You didn’t say whether you wanted Stepper or Stayer, so I saddled—” At Perrin’s golden-eyed glare, Kenly Maerin shied back into the dun stallion he was leading.
Perrin made a soothing gesture. Not Kenly’s fault. What could not be mended had to be endured. “Easy, lad. You did right. Stepper will do just fine. You chose well.” He hated speaking to Kenly that way. Short and stocky, Kenly was barely old enough to marry or leave home—and certainly not old enough for the patchy beard he was trying to cultivate in imitation of Perrin—yet he had fought Trollocs at Emond’s Field and done well yesterday.
Rising, Perrin took his axe from where he had propped it under the wagon, out of sight and for a little while out of mind, and thrust the haft through the loop on his belt. A heavy half-moon blade balanced by a thick curving spike; a thing made for no other purpose than killing. The axe haft felt too familiar to his hands for comfort. Did he even remember what a good forge-hammer felt like? There were other things besides “Lord Perrin” that it might be too late to change. A friend had once told him to keep the axe until he began to like using it. The thought made him shiver in spite of the heat.
He swung into Stepper’s saddle, shadowed by Aram with the gray, and sat facing south, into the wagon circle. At least half again as tall as even the tallest of the Aiel, Loial was just stepping carefully over crossed wagon tongues. With the size of him, he did look as though he might break one of the heavy wooden shafts with a heedless step.  He had spent the morning in a tiny clump of trees he called restful and shady, but whatever the shade among those trees, the heat was affecting him, too. He looked tired, and his coat was undone, his shirt unlaced, and his boots rolled down below his knees. Or maybe it was more than the heat. Just inside the wagons Loial paused, peering at the Aes Sedai and the Asha’man, and his tufted ears quivered uneasily. Eyes big as teacups rolled toward the Wise Ones, and his ears vibrated again. Ogier were sensitive to the mood of a place.
When he saw Perrin, Loial came striding across the camp. Sitting his saddle, Perrin was two or three hands shorter than Loial standing. “Perrin,” Loial whispered, “this is all wrong. It isn’t right, and it is dangerous besides.” For an Ogier it was a whisper. He sounded like a bumblebee the size of a mastiff. Some of the Aes Sedai turned their heads.
“Could you speak a little louder?” Perrin said almost under his breath. “I think somebody in Andor didn’t hear. In the west of Andor.”
Loial looked startled, then grimaced, long eyebrows brushing his cheeks. “I do know how to whisper, you know.” This time it was unlikely anyone could hear clearly more than three paces away or so. “What are we going to do, Perrin? It is wrong holding Aes Sedai against their will, wrong and wrongheaded, too. I have said that before, and I will again. And that isn’t even the worst. The feel here . . . One spark, and this place will erupt like a wagonload of fireworks. Does Rand know about this?”
“I don’t know,” Perrin said to both questions, and after a moment the Ogier nodded reluctantly.
“Someone has to know, Perrin. Someone has to do something.” Loial looked north, over the wagons behind Perrin, and Perrin knew there was no putting it off longer.
Unwillingly he turned Stepper. He would rather have worried over Aes Sedai and Asha’man and Wise Ones till his hair fell out, but what had to be done, had to be done. Think of the good on High Chasaline.


Here we make a window with three buttons in a 2x2 table.
The first two buttons will be placed in the upper row.
A third, quit button, is placed in the lower row, spanning both columns.
Which means it should look something like this:
Here's the source code:
(* file: table.ml *)
(* Our callback. *)
let hello msg () =
Printf.printf "Hello again - %s was pressed\n" msg;
flush stdout
let main () =
(* Create a new window; set title and border width *)
let window = GWindow.window ~title:"Table" ~border_width:20 () in
(* Set a handler for destroy event that immediately exits GTK. *)
window#connect#destroy ~callback:GMain.Main.quit;
(* Create a 2x2 table and put it in the main window *)
let table = GPack.table ~rows:2 ~columns:2 ~homogeneous:true
~packing:window#add () in
(* Create first button *)
let button = GButton.button ~label:"button 1" () in
(* Insert button 1 into the upper left quadrant of the table *)
table#attach ~left:0 ~top:0 (button#coerce);
(* When the button is clicked, we call the "callback" function
* with "button 1" as its argument *)
button#connect#clicked ~callback:(hello "button 1");
(* Create second button *)
let button2 = GButton.button ~label:"button 2" () in
(* Insert button 2 into the upper right quadrant of the table *)
table#attach ~left:1 ~top:0 (button2#coerce);
(* When the button is clicked, we call the "callback" function
* with "button 2" as its argument *)
button2#connect#clicked ~callback:(hello "button 2");
(* Create "Quit" button *)
let quit = GButton.button ~label:"Quit" () in
(* Insert the quit button into the both
* lower quadrants of the table *)
table#attach ~left:0 ~right:2 ~top:1 (quit#coerce);
(* When the "Quit" button is clicked, the program exits *)
quit#connect#clicked ~callback:GMain.Main.quit;
window#show ();
GMain.Main.main ()
let _ = Printexc.print main () |


This is a gallery of images that produced by the Neural Style Transfer application implemented in Owl. Currently we are working to bring more examples. The code used in the demo and instructions on how to use the provided API can be found in this Gist . A detailed explanation can be seen in this blog.


This is a living document and new ideas are always welcome and encouraged. If you have an idea that you think would be an improvement, please feel free to contribute.
The following document outlines best practices and provides a style guide for writing front end code. It barrows heavily from existing and widely adopted practices, but is not meant to be the authority on how to write "correct" front end code. The goal of this document is to provide a set of basic guidelines to follow when developing in order to ensure a level of code consistency exists across all projects, and that best practices are being followed.
By maintaining consistency in coding styles and conventions, we can ease the burden of legacy code maintenance, and mitigate risk of breakage in the future. By adhering to best practices, we ensure optimized page loading, performance and maintainable code.
While it should be the aim of everyone to follow these guidelines as closely as possible, if ever in doubt, keep these core principles in mind:
Tip: Configure your editor to "show invisibles" or to automatically remove end-of-line whitespace.

 ••
heysup

 .my-class { ••width: 25rem; }
Use HTML comments sparingly as they tend to throw off indentation and increase document length. HTML comments can be useful for indicating when a particular block of markup is ending or for "turning off" unruly sections of markup.
With the rise of preprocessors and build tools, (S)CSS comments should be plentiful, and always written using the // inline style stripped at compile time. Development shouldn't ever be done in compiled code, so there's no reason for having comments persist.
The same idea goes for JavaScript. Since production code will be concatenated and minified, take time to describe components, how they work, their limitations, and the way they are constructed. Additionally, be sure to leave TODO: comments only for things that have to happen but can't be done immediately.
Well commented code is extremely important. Don't leave others in the team guessing as to the purpose of uncommon or non-obvious code.

  .your-class { // destroy jquery inline style display: none !important; } // -------------------- // This is my component. // // There are many like it, but // this one is mine. // // This description is ideal for // detailed explanations and // documentation. //
Readable, maintainable code is always better than unreadable code, no matter the performance gains. Always choose readability. If your site is truly suffering from performance issues, first investigate the usual suspects, like image compression or number of requests, before compromising readability. As mentioned earlier, with the advent of build tools and preprocessors, in addition to compression from gziping, code can now "suffer" from being overly verbose.
Strictly keep structure (markup), presentation (styling), and behavior (scripting) apart, and try to keep the interaction between the three to an absolute minimum.
That is, make sure documents and templates contain only HTML and HTML that is solely serving structural purposes. Move everything presentational into style sheets, and everything behavioral into scripts.
In addition, keep the contact area as small as possible by linking as few style sheets and scripts as possible from documents and templates.
Separating structure from presentation from behavior is important for maintenance reasons. It is always more expensive to change HTML documents and templates than it is to update style sheets and scripts.
N.B. Due to the way that Shopify themes are built and the nature of our work, absolutely adhering to this idea is next to impossible.
 Make me bold pls  hi
<!doctype lang="en-us">   <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>My Page Title</title>
My Page

HTML attributes should come in this particular order for easier reading of code:
class
id
src
for
type
href
value
title
alt
data-*
aria-*
role
class and id are by far the most commonly used attributes, so they come before everyone else. Classes make for great reusable components, so they come before first. Ids are more specific and should be used sparingly (e.g., for in-page bookmarks), so they come second.
 My Favorite Food is a Hamburger   Beware!  <input class="form-control" type="checkbox">
Whenever possible, avoid superfluous parent elements when writing HTML. Many times this requires iteration and refactoring, but produces less HTML. Strive to maintain HTML standards and semantics, but not at the expense of practicality. Use the least amount of markup with the fewest intricacies whenever possible.

A boolean attribute is one that needs no declared value. XHTML required you to declare a value, but HTML5 has no such requirement.
The presence of a boolean attribute on an element represents the true value, and the absence of the attribute represents the false value.
If you need to store data in a DOM node, use a data-attribute with a sensible name.
<input type="text" disabled> <input type="checkbox" value="1" checked>  Click Here to Shop Quick!
{% if user.name == 'ralph' %} ralph pls go {% endif %} {{ my_output_tag }} {{ im_also_known_as_an_object }} {{ w_filter | append: '.jpg' }}
If you're not using some sort of preprocessor to write your CSS, you're either doing it our of necessity, or you're a masochist. Come join us writing Sass (specifically the SCSS variety) and take a ride on a wave of the future.
A few things to keep in mind when writing styles and their accompanying selectors/HTML hooks:
ids
!important
.navigation
.main-navigation
#fff
margin: 0;
margin: 0px;
.section-title, [modal-active], .section-title + [modal-active] { font-family: sans-serif; font-size: 2.5rem; font-weight: 600; color: rgba(0, 0, 0, 0.7); text-align: center; text-transform: uppercase; border: 1px solid #eee; padding-bottom:: 0; }
Many exist, and yet they all work in a pretty similar manner. Think about elements on your site as reusable objects/components/blocks/atoms/hamburgers, modify those things, and then reuse them. And while each framework introduces the much needed aspect of structure to (S)CSS, it also comes at the price of additional overhead and self-imposed rules and limits. And while the scale of projects increases, so does the importance of structure an organization increases exponentially, on the opposite end the upfront cost of following a particular framework while working on a smaller site can also feel overbearing.
Keeping that in mind, our work can be characterized by:
After taking each of those factors into consideration, the need to write extremely modular and extendable CSS, on a per project basis, does not jump out as a high priority. Choosing and then religiously adhering to a particular CSS framework may have its benefits, but it also comes with costs. Having said that, writing CSS in a fashion that lends itself to reuse and readability is always preferred over writing CSS in an ad-hoc and spastic manner, so at the very least, it's in our best interest to define some guiding principles to keep in mind when writing CSS.
The fact that our sites use templates, lends itself to style reuse. Instead of having to make a cognizant effort to try and reuse styles, a style that's applied in one place on a template will automatically propagate out to every page that uses that template. So while thinking about reusing styles on an individual project basis may seem like cutting a pie with a jackhammer, thinking about all of our projects as mini-parts of one larger Mega-Project and continuing to reuse styles on said Mega-Project, seems like a more approachable idea.
.topbar { $height: 2.5rem; @extends font-name; color: $black; line-height: $height; text-align: right; @include mobile { display: none; } &::before { content: '•'; } .active { color: $red-medium; } }
Arguing over the merits of responsive design vs. pixel perfect design is pointless. In almost every situation, relative units should be used.
Relative units include:
%
rem
em
vw
vh
px
* While vw and vh are incredibly powerful and useful units of measurement, they're still not entirely mature and ready for everyday use. There are a few select situations where they can be used with a percentage fallback, but it's advised to hold off using these units until they're ready for widespread use.
** Yes, you read that correctly, px is technically a relative unit, as it's relative to the size of a what a "pixel" is on the viewing device. Because there is so much misinformation and controversy over whether 1px is actually 1px, using px as a unit of measurement should be avoided at all costs, except for very basic properties, like border. Instead, we should aim to used forward focused technologies, like rem and em, instead of technology shrouded in controversy whose major purpose is seen as legacy device support.
border
Strive to limit use of shorthand declarations to instances where you must explicitly set all the available values. Common overused shorthand properties include:
padding
margin
font
background
border-radius
Beware that using shorthand properties sets all values for a CSS property, whether you specify them or not. For example, background: red; not only sets the background-color property, but also:
background: red;
background-color
background-image
background-position
background-size
background-repeat
background-origin
background-style
background-clip
to their initial values, overwriting any of these values set earlier in the declaration order.
Often times we don't need to set all the values a shorthand property represents. For example, HTML headings only set top and bottom margin, so when necessary, only override those two values. Excessive use of shorthand properties often leads to sloppier code with unnecessary overrides and unintended side effects.
The best way of demonstrating the dangers of over using nested selectors is with an example. If the example doesn't scare you away from overusing nested selectors, I don't know what will.
body { div.container { div.content { div.articles { & > div.post { div.title { h1 { a { } } } div.content { p { ... } ul { li { ... } } } div.author { a.display { img { ... } } h4 { a { ... } } p { a { ... } } ul { li { ... } } } } } } } } turns into .. body { ... } body div.content div.container { ... } body div.content div.container div.articles { ... } body div.content div.container div.articles > div.post { ... } body div.content div.container div.articles > div.post div.title { ... } body div.content div.container div.articles > div.post div.title h1 { ... } body div.content div.container div.articles > div.post div.title h1 a { ... } body div.content div.container div.articles > div.post div.content { ... } body div.content div.container div.articles > div.post div.content p { ... } body div.content div.container div.articles > div.post div.content ul { ... } body div.content div.container div.articles > div.post div.content ul li { ... } body div.content div.container div.articles > div.post div.author { ... } body div.content div.container div.articles > div.post div.author a.display { ... } body div.content div.container div.articles > div.post div.author a.display img { ... } body div.content div.container div.articles > div.post div.author h4 { ... } body div.content div.container div.articles > div.post div.author h4 a { ... } body div.content div.container div.articles > div.post div.author p { ... } body div.content div.container div.articles > div.post div.author p a { ... } body div.content div.container div.articles > div.post div.author ul { ... } body div.content div.container div.articles > div.post div.author ul li { ... }
var
for...in
Most of these things will become either: forced upon you by way of jslint, or second nature, and as with everything, exceptions are more than ok, just be vigilant about documenting those acceptations as extensively as required.
// Things that are okay: var i = 1; var n = 2; var myVar = 'heysup'; var OLD_FAITHFUL = true; (function(ModuleName, $, undefined) { ... }(...)); var goodParagraph = 'hi, im a really' + long string that' + happens to span' + over a number' + of lines'; direction === 'next' ? i++ : i--; // Things that are not okay: x = 'whatever' if (x) { function foo() {} } eval("2 + 2"); for (var key in [0, true, 'hey', undefined, 5000]) {...} var badParagraph = 'hi, im a really \ long string that \ happens to span \ over a number \ of lines';
JavaScript can some (seemingly) strange tendencies.
Everything in JavaScript has an inherent true/false value, and for the most part, it's obvious what's a truthy value and what's a falsy value.
The following values evaluate to false
false
null
undefined
0
''
NaN
while all other values evaluate to true.
The problem with this is that it can lead to some really strange situations that are worth being aware of. For example, the following values
'false'
'0'
[]
{}
all evalueate to true. That means the following expressions:
true === 'false'
true === '0'
true === []
true === {}
All evaluate to true.
It's also important to understand the different between == and ===, and their significance and acceptable uses. Triple equals (===) checks first if both values are equal, and then if those values are of the same type. Double equals (==) performs type conversion before checking if the values are equal, and as a result, evaluates to true more often than triple equals.
2 == '2'
2 === '2'
There's a time and a place to use each comparison operator, but as a rule of thumb, try to use triple equals as much as possible.


J.C.Bose High School Ymca Faridabad
YMCA has been in existence for the past 48 years and consistently been contributing towards creation of competent good student. The competence of the School has been recognized at various levels by the agencies like UGC (grant of 12B status), accreditation (NAAC Grade ‘A’), NIRF (best ranking amongst State Engineering Universities in Haryana), etc.
Moving ahead on the path of excellence, the School is ready to effectively take up the forthcoming challenges in diversified domains. To accomplish this, new courses are being added and new facilities are being developed on continuous basis. Inculcation of ethical and moral values among youth is one of our prime concerns. To achieve this goal, the Vivekanand Manch has been conducting various events.
Apart from creating highly qualified professionals, we are involved in imparting basic technological skills for underprivileged section of the society through its Community School programs. The School boasts of its strong industry interaction that is evident from excellent placement of students and also from the existence of industry linked labs and collaborations. Alumni are our brand ambassadors and many of them are entrepreneurs and occupying key positions in various Govt./Private organizations. We at YMCA are committed to the Nation’s development by taking up more scientific and technological projects meant for the direct upliftment of the society.
Keeping in view its excellent performance, the Government of Haryana has mandated the University to affiliate other Engineering Institutions situated in the District of Faridabad and Palwal. I am sure that this association will be highly beneficial to the various stakeholders in upgrading and monitoring the quality of technical education.
We are working to make the University environment efficient and tech-savvy and for this we are participating in programs like Digital India, Skill India, Make in India, Clean India, etc. by its various stake holders. We are committed to meet the expectations of all its stake holders and want to realize its vision to emerge as a centre of excellence in various fields both at national and international levels for which I solicit the participation of one and all.
Dr. Dinesh Kumar


Additional Information
Going 'green'
Enter e-mail
Help make our home better...greener.
Request more info via email here:
More info here
Getting Started
Zero Waste Products
© Copy 2020 TT


{% include head.html %}
Data scientist with 5 years experience in machine learning and data analysis. Worked in a variety of projects from concept to completion and helped business to consume ML models to transform data into actionable insights.
Design and Implementation of science driven features to Infor's suite of products through machine learning modeling and statistical data analysis. Served as analytical lead in multiple projects, right from specifying the requirements/use-case to testing and deployment of the solution. I have also experience in building dashboards to communicate results and model interpretations to stakeholders/decision makers.
Kaggle competitions provides a best platform to try out new algorithms, SOTA techniques on diverse real world problems. I have Achieved top 4% in multiple competitions and currently competition expert in kaggle data science community. I strongly advocate open source contribution and community learning.
Achieved top 10 and top 25 in multiple competitions and currently ranked under top 50 overall in the community
Customers represent the most important assets of a firm. Customer lifetime value (CLV) allows assessing their current and future value in a customer base. The customer relationship management strategy and marketing resource allocation are based on this metric. Managers therefore need to predict the retention but also the purchase behavior of their customers. For every Marketing team, mission is to improve every human interaction via data science. Usually a firm has a lot of data on touches. Customers send billions of events representing user and customer behaviors (e.g.logging into an app, buying something, visiting a website, etc.) a month via websites, APIs that are validated, normalized and stored in realtime. Here, I try to predict future purchasing from a history of such customer transactions.
The objective of this project is to create a model to predict the number of retweets a tweet will get on Twitter. The data used to train the model will be approximately 2,400 tweets each from 38 major banks and mobile network operators across Africa. A machine learning model to predict retweets would be valuable to any business that uses social media to share important information and messages to the public. This model can be used as a tool to help businesses better tailor their tweets to ensure maximum impact and outreach to clients and non-clients.
Here, I experiment with different methods, classic time series algorithms as well as ensemble decision trees to forecast price for avocado in various US Regions.
I am a big fan of Soccer and premier league.I also play in mini leagues. When I have time, I like to combine my interest in data and sport to come up with interesting analysis.
A Linear Programming System that provides the optimal team to field every week of fantasy sport. Work in progress to assist in substitutions as well.
Video Assistant Referee is a match official who reviews decisions of head referee using video, image technologies. English Premier League began to use VAR in all of its matches from season 2019/2020. There has been a big controversy week after week amongst professionals, fans and football enthusiasts regarding this decision. In this project, I will try to gauge the sentiment of people towards VAR using tweets. Also, experimented with pre-trained models such as BERT and ULMfit models
Python, R, SQL, C++(basic)
git, pandas, numpy, scipy, sklearn, keras, tensorflow, pyspark, IPython Notebooks, RShiny, Plotly
EC2, S3, SageMaker and EMR
Awarded for stopping a nuclear meltdown, even though I also started it.
Honored by Duff Beer for being an outstanding customer several years straight. Qualifications included most beer consumed at a bar, most beer purchased, and most beer ralphed.
Specifically this prestigious awarded twice for stopping a robber with my belly.
Organized fund drives and participated in fundraising events for the benefit of families in third world countries without proper access to malt beverages.
Founding member of the local nuclear workers labor union.


WinguLocations
public class WinguLocations : NSObject
Use WinguLocations
to manage all triggers and locations inside wingu platform.
This class provide a way for managing zones and beacons in SDK.
Note:
CLLocationManager
shouldn’t be deallocated if notifications are required.
-
Instance of
BeaconScanner
. You can change scanning parameters using this property, but property itself isDeclaration
Swift
private(set) public lazy var beaconScanner: BeaconScanner { get set }
-
By default winguSDK returns every channels found matching wingu criteria. You can change this behavour using this flag and your delegate method will get only channels with valid content attached.
Declaration
Swift
public var returnOnlyChanelsWithContent: Bool { get set }
-
Instance of
GeofenceScanner
. You can change scanning parameters using this property, but property itself isDeclaration
Swift
private(set) public lazy var geofenceScanner: GeofenceScanner { get set }
-
There are some of scenarios that you will need to create more than one
WinguLocationManager
but for most of a project you should be fine with just one instance of location manager.Please note that it will create new
CLLocationManager
instance for you so you.Declaration
Swift
public static let shared: WinguLocations
-
WinguLocationManagerDelegate
is needed to be set if you want to receive callbacks. More in protocol description available methodsDeclaration
Swift
public weak var delegate: WinguLocationsDelegate?
-
Your API Key. To obtain your API key please visit wingu.de
Declaration
Swift
public var apiKey: String? { get set }
-
This flag should be set to
true
only if you obtain staging key from wingu.Note: Don’t confuse it with API key By default
false
Declaration
Swift
public var stagingEnvironment: Bool { get set }
-
Request location permission. Call it before start ranging or monitoring if you’re willing to change standard behaviour. By default app will ask for
CLAuthorizationStatus.authorizedAlways
authorization.Declaration
Swift
public static func requestPermission(_ requestType: CLAuthorizationStatus)
Parameters
requestType
Standard CLAuthorizationStatus parameter, It’s limited to
authorizedAlways
andauthorizedWhenInUse
-
Method should be called whenever app is woke up with location option.
It’s need to be implemented in case of usage wingu geofences and working with Local notifications based on that type of triggers
This should be placed in yourAppDelegate
in methodfunc application(_ application: UIApplication, willFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]? = nil) -> Bool
and should be called like:WinguLocations.shared.useLaunchOptions(launchOptions)
Declaration
Swift
public func useLaunchOptions(_ launchOptions: [UIApplicationLaunchOptionsKey : Any]?)
Parameters
launchOptions
UIApplicationLaunchOptionsKey provided by the iOS
-
General starting method for ranging and monitoring beacons. It will start ranging beacons using default regions.
Note: If there is a need to pass custom regions you should call
startRangingBeacons(regions:locationManager:)
insteadIt will also start monitor for geofences in foreground and in background.
Declaration
Swift
public func start()
-
Start ranging beacon.
Declaration
Swift
public func startRangingBeacons(regions: [CLBeaconRegion], locationManager: LocationManager?)
Parameters
regions
Collection of beacons regions, required. Pass empty array to scan for default regions.
locationManager
You can use your location manager, whenenever you pass nil CLLocationManager instance will be created for you.
-
Stop ranging beacons. This is async call for Apple Location Services, you may still receive some delegate call after calling stop ranging, but with response there will be always empty array of beacons. Note that this operation can take couple of seconds.
Declaration
Swift
public func stopRangingBeacons()
-
Start monitoring for beacons. By default monitoring is already on when you start ranging. Have a look at
shouldMonitorForBeaconsInBackground
inBeaconScanner
.Declaration
Swift
public func startMonitoringBeacons(regions: [CLBeaconRegion], locationManager: LocationManager?)
Parameters
regions
Collection of beacons regions, required. If you want to monitor for the same regions as ranging, you don’t need to pass anything.
locationManager
You can use your location manager, pass
nil
if you want to use the sameCLLocationManager
as in ranging. -
Stop monitoring beacons. This is async call for Apple Location Services, you may still receive some delegate call after calling stop monitoring.
Declaration
Swift
public func stopMonitoringBeacons()
-
Starts monitoring for geofences.
Declaration
Swift
public func startMonitorGeofenceLocations()