Triangle Tracker
Find out which triangle it is by entering the values of the three sides of your triangle.
Enter the first length value:
Enter the second length value:
Enter the third length value:
Calculate


The payout request for proposal milestone {{ args.proposal.title }} - {{ args.proposal.current_milestone.title }} has been rejected.
{% if args.admin_note %}The following reason was provided:
“{{ args.admin_note }}”
{% endif %}Another request for payment can be made when the above concerns have been addressed.


/**
* Provides access to feature flag states for the current
* Hypothesis user.
*
* This service is a thin wrapper around the feature flag data in
* the session state.
*
* Users of this service should assume that the value of any given flag can
* change at any time and should write code accordingly. Feature flags should
* not be cached, and should not be interrogated only at setup time.
*/
'use strict';
var events = require('./events');
var bridgeEvents = require('../shared/bridge-events');
// @ngInject
function features($log, $rootScope, bridge, session) {
var _sendFeatureFlags = function(){
var userFeatures = session.state.features;
bridge.call(bridgeEvents.FEATURE_FLAGS_UPDATED, userFeatures || {});
};
// user changed is currently called when we initially load
// the sidebar and when the user actually logs out/in.
$rootScope.$on(events.USER_CHANGED, _sendFeatureFlags);
// send on frame connected as well because the user_changed event
// alone might run before the frames ever connected. This will
// provide us the follow up to make sure that the frames get the flags
$rootScope.$on(events.FRAME_CONNECTED, _sendFeatureFlags);
/**
* Returns true if the flag with the given name is enabled for the current
* user.
*
* Returns false if session data has not been fetched for the current
* user yet or if the feature flag name is unknown.
*/
function flagEnabled(flag) {
// trigger a refresh of session data, if it has not been
// refetched within a cache timeout managed by the session service
// (see CACHE_TTL in session.js)
session.load();
if (!session.state.features) {
// features data has not yet been fetched
return false;
}
var features = session.state.features;
if (!(flag in features)) {
$log.warn('looked up unknown feature', flag);
return false;
}
return features[flag];
}
return {
flagEnabled: flagEnabled,
};
}
module.exports = features;
|


|
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object java.util.AbstractMap<K,V> java.util.HashMap<K,V> java.util.LinkedHashMap<java.lang.String,java.lang.Object> com.splunk.Args com.splunk.CollectionArgs
public class CollectionArgs
The CollectionArgs
class contains arguments for retrieving and
listing entities from a collection, such as the number of entities to return
and how to sort them.
| Nested Class Summary | |
|---|---|
static class |
CollectionArgs.SortDirection
Indicates whether to sort entries in ascending or descending order. |
static class |
CollectionArgs.SortMode
Indicates the sorting mode for entries. |
| Nested classes/interfaces inherited from class java.util.AbstractMap |
|---|
java.util.AbstractMap.SimpleEntry<K,V>, java.util.AbstractMap.SimpleImmutableEntry<K,V> |
| Constructor Summary | |
|---|---|
CollectionArgs()
Class constructor. |
| Method Summary | |
|---|---|
void |
setApp(java.lang.String app)
Sets the app context in which to list the collection. |
void |
setCount(int count)
Sets the maximum number of entries to return. |
void |
setOffset(int offset)
Sets the index of the first entry to return. |
void |
setOwner(java.lang.String owner)
Sets the owner context in which to list the collection. |
void |
setSearch(java.lang.String search)
Sets a search query to filter the response. |
void |
setSharing(java.lang.String sharing)
Sets the sharing context in which to list the collection. |
void |
setSortDirection(CollectionArgs.SortDirection sortDirection)
Sets the direction to sort entries. |
void |
setSortKey(java.lang.String sortKey)
Sets the field to use for sorting. |
void |
setSortMode(CollectionArgs.SortMode sortMode)
Sets the mode to use for sorting. |
| Methods inherited from class com.splunk.Args |
|---|
add, create, create, create, encode, encode, encode, get |
| Methods inherited from class java.util.LinkedHashMap |
|---|
clear, containsValue, get, removeEldestEntry |
| Methods inherited from class java.util.HashMap |
|---|
clone, containsKey, entrySet, isEmpty, keySet, put, putAll, remove, size, values |
| Methods inherited from class java.util.AbstractMap |
|---|
equals, hashCode, toString |
| Methods inherited from class java.lang.Object |
|---|
finalize, getClass, notify, notifyAll, wait, wait, wait |
| Methods inherited from interface java.util.Map |
|---|
containsKey, entrySet, equals, hashCode, isEmpty, keySet, put, putAll, remove, size, values |
| Constructor Detail |
|---|
public CollectionArgs()
| Method Detail |
|---|
public void setApp(java.lang.String app)
app
- The app context in which to list the collection. A null
value indicates no app context, and a value of "-"
indicates an app wildcard.public void setOwner(java.lang.String owner)
owner
- The owner context in which to list the collection. A value of "-"
indicates a wildcard, and a null
value indicates no owner context.public void setSharing(java.lang.String sharing)
sharing
- The sharing context in which to list the collection. Valid values are "user", "app", "global", and "system".public void setCount(int count)
count
- The maximum number of entries to return. To return all entries, specify 0.public void setOffset(int offset)
offset
- The index of the first entry to return.public void setSearch(java.lang.String search)
search
- A search query to filter the response.public void setSortDirection(CollectionArgs.SortDirection sortDirection)
sortDirection
- The sorting order--ascending or descending.public void setSortKey(java.lang.String sortKey)
sortKey
- The field to sort by.public void setSortMode(CollectionArgs.SortMode sortMode)
sortMode
- The collating sequence for sorting entries.
|
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


Toggle navigation
OLYMPIA
User Profile
Settings
Logout
Dashboard
Student List
View
Export
Events
Add
View
Export PDF
View Rulebook
Scores
Add
View
Score Board
Substitutions
Status
Request
Request Queue
Administration
New Account
Manage Account
Account List
System Settings
Start Time
End Time
Date
Type
Add more participants!
Participants
Student Number
Name
Gen
HR
×
Choose a student.
Student Number
Name
Gen


So here we go:
Rails was extracted from the real world work sweat, blood, tears, everything..And it feels like it is.
ASP.NET MVC is a "me too" framework - trying to compete with other solutions. ASP.NET MVC is not part of the story for WebForms, not quite fit.Aha. Try to tell WebForms guy about MVC :)
Microsoft promotes it as an option. Option for what?These words from Rob Conery probably mean that MVC is something that was not “designed” to be mainstream. But rather an “option” for… well web development on .NET.
[About TekPub]…rewrite point for startup - reconsidered BizSpark. We wanted to stay small.We needed fast, easy framework. Up in the cloud, scalable, zero cost, everything.There was a lot of buzz behind the decision to move to Rails by Rob Conery who was a .NET advocate. But it was a happy business AND technical decision.
Rails came out of a need. MVC hasn't. NHibernate came out of a need. Entity Framework hasn't. It's always the same: solving problems they personally don't have, so they are not in the context of their problems.That is very common with Microsoft. They have to be everywhere and at the same time nowhere. Anything “new” that comes out from Microsoft has already been adopted and they are just catching up.
Microsoft projects often come out of suppositions.
Dell is rebuilding everything in ASP.NET MVC (instead of WebForms).Good for them. In any case, ASP.NET MVC IS a good thing to have in .NET world. And that’s my preference for Web development in .NET. Probably same goes with Dell.
MVC redirected the attention back to .NET after .NET Web developers started moving to Rails.True. And in fact, most of the features of ASP.NET MVC were borrowed from Rails. So that was one of the easiest ways to hold .NET gurus back.
Why would .NET developers move to Rails?Cannot agree more on this. Testing “just works”, deployment “just works” it all “just works”.
Testing in rails is…uhh… it’s something you realise when you do it. Testing tools like RSpec and Cucumbet are just natural.
Deployment – Capistrano, Heroku – just unbelievable.
In .NET we like to overcomplicate ourselves. Something too simplistic can’t be good. [No worries with SRP principle – objects aware of the persistence and similar].Speaking about myself, I do agree with it. Partially due to the nature of .NET (C#), partially because testing is harder, but also just because .NET developers try to solve problems in advance assuming those will exists (while in many cases they will not).
In .NET we question more.
The MVC/MonoRail and Ruby On Rails have the same features.Read on…
You have the same names of the features, but the experience is dramatically different. There’s incredible amount of software out of the box to do anything.So true! So true!

Why do we have to wait for 2 years to get the innovation that we already have available to us right now in Rails?The rails community moves with small changes all the time, while .NET – with large in couple of years time. So for Rails it is a normal evolution, while for .NET it is rather a revolution.
[about Rails]… it means you are building a web site, and you are not rebuilding the stuff that has already been built. You are building Business.Oh, yes. Having higher level plug-ins (nearly as Service-Oriented-Architecture components) it opens much more opportunities for business.
Not everybody is fortunate of making decisions at work [on choosing technology].Try to push a new technology in a corporate environment with all the bureaucratic procedures. No f…ing way! Unless you are the one who decides.
Building web sites on .NET is about building web sites in a corporate environment. And that’s not about productivity. That’s not about really, really, really compressed budget where every decision is your life and death decision…[and then] It’s like we have a budget, but is is rather a suggestion.Not much to comment on here.  Otherwise – probably Rails.
It’s about how fast you can turn your ideas into money.Well said!
Most of the cost of long lived projects is re-learning. Ruby code is just scan and get it.Indeed, Rails, would not even exist without such a beautiful language as Ruby. It makes code easy to understand.
In Ruby there is just less code to see where a problem might be. A lot less code! And the code is so usable that you can really spot the problems really quickly.Again so true. Just have a look, for example, at some OSS projects. They do so much with so little code. That’s just amazing.
At the end, I must admit that I do like the .NET platform, but Ruby and Rails just feels much better to me and ALL of the things I currently do for myself, I do using Ruby/Rails.
It is just much more fun!
Remember running your site in .NET or RoR is not going to make a whole lot of difference in speed if your database architecture sucks or your website does alot of IO.
ex. alot of Google's products are written in Python but thats just a front alot of the actual business logic is probably implemented in the back in Java or whatever they prefer.
Also, i'd like to know a big app (300 tables and millions of entries) on RoR.
Visual Studio is a big thing also.
But, normally i use rails for blogs and websites x)


{block name="header"}{/block}
Professional, accurate, efficient and continuous
Professional people do professional things


The Outdoor Girls in Florida
by Laura Lee Hope
Chapter I: "Bad News"
Additional Information
- Year Published: 1913
- Language: English
- Country of Origin: United States of America
- Source: Hope, L. L. (1913) The Outdoor Girls in Florida. New York: Grosset & Dunlap.
-
Readability:
- Flesch–Kincaid Level: 2.2
- Word Count: 2,756
- Genre: Adventure
- Keywords: florida stories, the outdoor girls in florida
- ✎ Cite This
Downloads
"Why, Grace, what in the world is the matter? You've been crying!"
"Yes, I have, Betty. But don't mind me. It's all so sudden. Come in. I shall be all right presently. Don't mind!"
Grace Ford tried to repress her emotion, but the cause of her tears was evidently too recent, or the effort at self-control too much for her, for she gave way to another outburst, sobbing this time on the shoulder of Betty Nelson, who patted her sympathetically, and murmured soothingly to her chum.
"But what is it, Grace?" Betty asked, after waiting a minute.
"I—I'll tell you in a moment or two, Betty. Just—just wait," and the tall, graceful girl made a more successful effort to master her feelings.
"Here come Amy and Mollie," went on Betty, as she glanced from the library window and saw two girls walking up the path opened across the lawn through the mass of newly fallen snow. "Do you want to meet them, Grace; or shall I say you don't feel well—have a headache? They'll understand. And perhaps in a little while—"
"No—no, Betty. It's sweet of you to want to help me; but Amy and Mollie might just as well know now as later. I'll be able to see them—in a little while. It—it's all so sudden."
"But what does it all mean, Grace? I can't understand. Is anyone dead—or—or hurt?" and Betty Nelson, who had called at the house of Grace to talk over plans for a dance they were going to attend the following week, looked anxiously at her chum. Only the day before Grace had seemed like her nearly-always jolly self. She and her three chums, including Betty, had been down town shopping, and Grace, as usual, had indulged in chocolates—her one failing, if such it can be called.
"Surely she can't be ill," thought Betty. "Ill from too many chocolates? I've seen her take twice as many as she did yesterday, and she doesn't look ill."
With this half-formed thought in her mind Betty looked more critically at her chum. Aside from the tears—which seldom add to a girl's beauty—there was no change in Grace Ford.
That is, no change except one caused by something rather mysterious, Betty thought—something that was hard for Grace to tell, but which had deeply affected her.
There came a ring at the door. Betty started toward it from the library, where she and Grace had gone when Grace let her chum in a short time before.
"Shall I answer, Grace?" inquired Betty, hesitating.
"Yes, do, please. I think Katy is with mamma. She took the news very much to heart. Let Amy and Mollie in, and then I'll tell you all about it. Oh, but I don't know what to do!"
"Now look here, Grace Ford!" exclaimed Betty briskly, pausing a moment on her way to the door. "You just stop this! If no one is dead, and no one is hurt, then it can't be so very dreadful. You just stop now, and when we all get together we'll help you in whatever trouble you have. You know that; don't you?"
"Oh, yes, Betty, I do. You aren't the 'Little Captain' to all of us for nothing. I'll try and not cry any more."
"Do. It—it isn't at all becoming. Your nose is positively like a—lobster!"
"It is not, Betty Nelson!" Grace flared.
"It certainly is. Look in the glass if you don't believe me. There—take my chamois and give it a little rub before I let in Amy and Mollie. It's only nice, clean talcum—you needn't think it's powder."
"All right—as if talcum wasn't powder, though," and Grace smiled through the traces of her recent tears.
 "Yes, I'll be there in a moment," she called as there came another ring at the bell.
"Shall I bring them right in, Grace?" she called over her shoulder, as she neared the door.
"Yes—yes. I might as well—have it over with," faltered the weeping one.
"Gracious, you'd think someone was going to be hanged, or beheaded, or sent to the galleys for life—or some other dreadful thing such as we read of in our ancient histories," commented Betty. "Cheer up, Grace. There may be worse to come."
"It's awfully good of you, Betty, to try and cheer me, only, if you understood—but there—let them in. They must be perishing!"
"Oh, it isn't so cold. You don't feel well, that's all. Hello, Amy—Mollie. Come in!" she greeted the other girls, at the same time endeavoring by nods and winks to convey some idea that all was not well with Grace.
But if Betty hoped to convey a quiet intimation that something out of the ordinary had happened she did not succeed. In her eagerness to warn the newcomers not to ask questions she overdid it, and succeeded only in making them alarmed.
"What—what is it?" asked Mollie, in a sort of stage whisper.
"Oh, nothing like that," said Betty, seeing that she was only making matters worse.
"Who—who is—" began Amy.
"No one!" said Betty, half-sharply. "Don't put on such a mournful look, Amy. But Grace has had some bad news, I expect, so I let you in."
"Bad news!" echoed Mollie.
"What kind?" inquired Amy.
"I don't know—yet. She's going to tell us."
The two newcomers, divesting themselves of their rubbers, walked on tiptoe toward the library, preceded by Betty. The latter heard their cautious approach and turned on them quickly.
"Nobody's asleep!" she exclaimed.
 demanded Mollie Billette, quickly, her dark eyes flashing. "You meet us as if—as if something terrible had happened, and because we live up to the part, and behave ourselves, you—"
"Hush, please," begged gentle Amy, for well she knew Mollie's failing—an exceedingly quick temper.
"I beg your pardon," spoke Mollie, contritely. "I forgot myself."
"That's all right," said Betty, with a smile. "I don't blame you. But we must all help Grace now. She feels very bad."
As the three entered the library they saw their chum standing near a window, looking out over the snow-covered lawn. Grace did not turn at the approach of her friends.
Then Amy stole softly up to her, and, reaching up her arms, tried to put them around Grace's neck. But Grace was tall, while Amy was rather short, so the little act of kindness could not be carried out.
Mollie laughed a little. She could not help it.
Amy flushed. She was rather sensitive on the point of her stature.
"Don't mind them, Amy," said Grace quickly, as she turned about, placing her own arms around the other. "I know I am too tall, and I seem to keep on growing. Hello, Mollie dear. I'm so glad you came," and she kissed the two newcomers.
Her eyes filled with tears again, seeing which Betty called out:
"Now, Grace, remember you promised not to do that any more. Just be brave, and tell us all about it; that is, if we can help you in any manner."
"I—I don't know whether you can or not," spoke Grace slowly, "but I'll tell you just the same. It's—it's about my brother Will!"
She paused a moment, catching her breath as she gave this piece of information.
"Has he—has he—" began Betty, hoping to make it easier for Grace to tell.
"No, he hasn't done anything to attract public attention this time," went on Grace. "But he has run away."
"Run away!"
It was a surprised chorus from the three visitors.
"Yes he has left Uncle Isaac's home—stopped work in the cotton mill, and gone—no one knows where."
"Why, Grace!" exclaimed Mollie. "Do you really mean it?"
Grace nodded. She could not speak for a moment.
"How did it happen?" asked Betty.
"Who told you?" Amy wanted to know.
"Uncle Isaac himself told us," resumed Grace, after a pause. "As for how it happened we don't know yet. Uncle Isaac is on his way now to give us some particulars. He just telephoned to mamma, and that is what upset us all. I have sent for papa to come home from the office.  Oh, isn't it dreadful!"
"But perhaps it is only some boyish prank," suggested Betty hopefully. "What are the particulars? Perhaps he has only gone off with some friends, and will come back again, just as he did the—other time."
"The other time," as Betty called it was rather a delicate subject with the Ford family, for Will with some chums had gotten into a little difficulty not long before this story opens, and the present complication was an outcome of that. I shall describe them in order presently.
"No, I don't believe it is a prank this time," went on Grace. "He has been gone some time, and we never knew it until Uncle Isaac mentioned it casually over the telephone. Oh, I wish he would come! We can't do a thing until we hear the particulars. Then papa will start an inquiry, I think. Poor Will! I hope he is not—not hurt!" and again Grace showed symptoms of tears.
"Now stop that!" commanded the Little Captain sharply. "You know it does no good to worry. Wait until you have some real facts to go on."
"Yes, do," urged Mollie.
"But he isn't your brother," said Grace in retort. "How would you like it, Mollie Billette, if Paul should be missing some day?"
"Oh, I'd feel dreadful, of course. But Paul and Dodo get into so many scrapes," she added, with a curious shrug of her shoulders, in which she betrayed her French ancestry—"so very many scrapes, my dears, that we are past being shocked."
But, for all Mollie spoke so lightly, she knew—and so did her chums—that should anything happen to the twins Mollie would be the first to show emotion.
"Have you heard no word from Will himself?" asked Betty, after a pause.
"Not a word, and that makes it seem all the worse. If we only had some word—something to go by, we might not feel so bad. But it came like a bolt out of a blue sky—what Uncle Isaac telephoned about an hour ago. He is down town attending to business, and he said he'd come up as soon as he could. He was surprised himself, to know that Will was not home."
"Then he knew that he had left Atlanta?" asked Mollie.
"Yes, but he supposed Will had started back home."
"I'm afraid I don't exactly understand it all," said Amy in a low voice. "You know I've been away, and—"
"Oh, of course!" exclaimed Grace. "I forgot that you had been off with that newly-found brother of yours. Well, you see, Amy, Will disgraced himself a while ago—"
"I don't call it much of a disgrace," said Betty in defense of the absent one.
"Well, papa did," said Grace. "I thought perhaps he was a little too severe on Will, but mamma said it was best to be severe at the start."
"What did he do?" asked Amy.
"I didn't hear all the particulars," went on Grace. "But you know that new Latin teacher the High School boys have—Professor Cark, his name is."
Amy nodded.
"Well, the boys didn't like him from the very start," proceeded Grace, "and I guess he didn't like the boys any too well. They played some tricks on him, and he retaliated by doubling up on their lessons. Then one night he was kidnapped—taken from his boarding place and hazed. It was nothing very bad, but the faculty held a meeting, and voted to expel all the boys concerned in it. Will was one, and papa was so angry that he said he would punish Will in a way he wouldn't forget. He said he'd take him out of school, before he'd have him expelled, and make him lose a term.
"So poor Will was given his choice of starting the study of law in papa's office, or going to work for Uncle Isaac Ford—papa's brother.  Papa thought it would be a good thing for Will to see what hard work meant. At the same time it would take him away from Deepdale, and out of the influence of some of the boys who were responsible for the hazing. I don't believe Will was one of the ringleaders."
"And did he go South?" asked Amy.
"He did. He chose to work for Uncle Isaac instead of studying law here. And for the past month or so he has been in the mill. Then, all of a sudden, he disappears."
"But how?" asked Mollie.
"We don't know the particulars," said Grace. "We supposed up to about an hour ago, that Will was in Atlanta, though we wondered why he didn't write. But then he never was very good at sending letters. Then came this 'phone message. I answered and I was surprised to hear Uncle Isaac speaking.
"At first I thought he was talking from Atlanta, and I was afraid something had happened. But Uncle Isaac said he was here—in Deepdale, and then he startled me by asking how Will was.
"'Why, isn't he down in your mill?' I asked. Uncle Isaac said he was not—that Will had not come to work one morning, and had left a note saying that he was going to quit. Of course Uncle Isaac thought Will had come back home. But when I told him we had not seen my brother, why, Uncle Isaac was as startled as I was. He said he'd come right up here and tell us all he knew."
Grace paused. She had spoken rather at length.
"Well, that is rather strange," murmured Mollie.
"But of course it may be easily explained when your Uncle comes," said Betty.
"There he is now!" cried Grace, glancing out of a window. "And he has papa with him. He must have stopped at the office.  and she hurried to the front door to let them in.


US Pres. Trump: We continue to talk to China
by Eren SengezerWhile speaking to reporters at the White House on Wednesday, United States President Donald Trump noted that trade talks with China continue. "They want to make a deal," Trump added.
The market reaction to these comments was muted. As of writing, the 10-year US Treasury bond yield was down 1.4% on the day and Wall Street's three main indexes, the Dow Jones Industrial Average, the S&P 500 and the Nasdaq Composite, were down between 0.25% and 0.35%.
Investors are likely to wait for the Federal Open Market Committee (FOMC) to publish the minutes of the October meeting at 19:00 GMT.


Grid
(class in module ui.grid
)
Grid is the main viewModel. Any properties or methods needed to maintain state are defined in * this prototype. One instance of Grid is created per Grid directive instance.
Grid(options);
options – {object} –
Object map of options to pass into the grid. An 'id' property is expected.
uses the first row of data to assign colDef.type for any types not defined.
Populates columnDefs from the provided data
rowBuilder – {function(colDef, col, gridOptions)} –
function to be called
creates GridColumn objects from the columnDefinition. Calls each registered columnBuilder to further process the column
{Promise}
– a promise to load any needed column resources
calls each styleComputation function
returns a grid column for the column name
name – {string} –
column name
Return the columns that the grid is currently being sorted by
{Array[GridColumn]}
– An array of GridColumn objects
returns the GridRow that contains the rowEntity
rowEntity – {object} –
the gridOptions.data array element instance
creates or removes GridRow objects from the newRawData array. Calls each registered rowBuilder to further process the row
Rows are identified using the gridOptions.rowEquality function
processes all RowBuilders for the gridRow
gridRow – {GridRow} –
reference to gridRow
{GridRow}
– the gridRow with all additional behavior added
When the build creates columns from column definitions, the columnbuilders will be called to add additional properties to the column.
columnsProcessor – {function(colDef, col, gridOptions)} –
function to be called
When the build creates rows from gridOptions.data, the rowBuilders will be called to add additional properties to the row.
rowBuilder – {function(colDef, col, gridOptions)} –
function to be called
Register a "rows processor" function. When the rows are updated, the grid calls eached registered "rows processor", which has a chance to alter the set of rows (sorting, etc) as long as the count is not modified.
rows – {function(renderableRows)} –
processor function
{Array[GridRow]}
– Updated renderable rows
registered a styleComputation function
If the function returns a value it will be appended into the grid's <style>
block
styleComputation – {function($scope)} –
function
Remove a registered rows processor
rows – {function(renderableRows)} –
processor function
Return the columns that the grid is currently being sorted by
[excludedColumn] – {GridColumn} –
Optional GridColumn to exclude from having its sorting reset
Set the sorting on a given column, optionally resetting any existing sorting on the Grid.
column – {GridColumn} –
Column to set the sorting on
[direction] – {uiGridConstants.ASC|uiGridConstants.DESC} –
Direction to sort by, either descending or ascending. If not provided, the column will iterate through the sort directions: ascending, descending, unsorted.
[add] – {boolean} –
Add this column to the sorting. If not provided or set to false
, the Grid will reset any existing sorting and sort
by this column only
{Promise}
– A resolved promise that supplies the column.


Transformtion Tool Contest
2021
G. Hinkel: Incremental recompilation of laboratory workflows in TTC 2020/2021 - Joint Proceedings of the 13th and 14th Tool Transformation Contests. The TTC pandemic proceedings with CEUR-WS co-located with Software Technologies: Applications and Foundations (STAF 2021), Virtual Event, Bergen, Norway, July 17, 2020 and June 25, 2021, 2021
G. Hinkel: An NMF solution to the TTC2021 incremental recompilation of laboratory workflows case in TTC 2020/2021 - Joint Proceedings of the 13th and 14th Tool Transformation Contests. The TTC pandemic proceedings with CEUR-WS co-located with Software Technologies: Applications and Foundations (STAF 2021), Virtual Event, Bergen, Norway, July 17, 2020 and June 25, 2021, 2021
G. Hinkel: An NMF solution to the TTC 2021 OCL to SQL case in TTC 2020/2021 - Joint Proceedings of the 13th and 14th Tool Transformation Contests. The TTC pandemic proceedings with CEUR-WS co-located with Software Technologies: Applications and Foundations (STAF 2021), Virtual Event, Bergen, Norway, July 17, 2020 and June 25, 2021, 2021
2020
G. Hinkel: An NMF solution to the TTC 2020 roundtrip engineering case in TTC 2020/2021 - Joint Proceedings of the 13th and 14th Tool Transformation Contests. The TTC pandemic proceedings with CEUR-WS co-located with Software Technologies: Applications and Foundations (STAF 2021), Virtual Event, Bergen, Norway, July 17, 2020 and June 25, 2021, 2020
2018
G. Hinkel: The TTC 2018 Social Media Case in Proceedings of the 11th Transformation Tool Contest, co-located with the 2018 Software Technologies: Applications and Foundations, TTC@STAF 2018, Toulouse, France, June 29, 2018., pp. 39-43, 2018
G. Hinkel: An NMF Solution to the TTC 2018 Social Media Case in Proceedings of the 11th Transformation Tool Contest, co-located with the 2018 Software Technologies: Applications and Foundations, TTC@STAF 2018, Toulouse, France, June 29, 2018., pp. 45-49, 2018
2017
G. Hinkel: The TTC 2017 Outage System Case for Incremental Model Views in Proceedings of the 10th Transformation Tool Contest, a part of the Software Technologies: Applications and Foundations (STAF 2017) federation of conferences, July. 2017
G. Hinkel: An NMF solution to the Smart Grid Case at the TTC 2017 in Proceedings of the 10th Transformation Tool Contest, a part of the Software Technologies: Applications and Foundations (STAF 2017) federation of conferences, July. 2017
G. Hinkel: An NMF solution to the Families to Persons case at the TTC 2017 in Proceedings of the 10th Transformation Tool Contest, a part of the Software Technologies: Applications and Foundations (STAF 2017) federation of conferences, July. 2017
G. Hinkel: An NMF solution to the State Elimination Case at the TTC 2017 in Proceedings of the 10th Transformation Tool Contest, a part of the Software Technologies: Applications and Foundations (STAF 2017) federation of conferences, July. 2017
2016
G. Hinkel: An NMF solution to the Class Responsibility Assignment Case in Proceedings of the 9th Transformation Tool Contest, a part of the Software Technologies: Applications and Foundations (STAF 2015) federation of conferences, July. 2016
2015
G. Hinkel and L. Happe: An NMF Solution to the TTC Train Benchmark Case in Proceedings of the 8th Transformation Tool Contest, a part of the Software Technologies: Applications and Foundations (STAF 2015) federation of conferences, pp. 142-146, 7. 2015
G. Hinkel: An NMF Solution to the Java Refactoring Case in Proceedings of the 8th Transformation Tool Contest, a part of the Software Technologies: Applications and Foundations (STAF 2015) federation of conferences, pp. 95-99, 7. 2015
2013
G. Hinkel, T. Goldschmidt, and L. Happe: An NMF solution for the Petri Nets to State Charts case study at the TTC 2013 in Proceedings Sixth Transformation Tool Contest, TTC 2013, Budapest, Hungary, 19-20 June, 2013., pp. 95-100, 2013 DOI: 10.4204/EPTCS.135.12
G. Hinkel, T. Goldschmidt, and L. Happe: An NMF solution for the Flowgraphs case at the TTC 2013 in Proceedings Sixth Transformation Tool Contest, TTC 2013, Budapest, Hungary, 19-20 June, 2013., pp. 37-42, 2013 DOI: 10.4204/EPTCS.135.5


Have you tried using any of the insight and techniques for growing trust and sincerity? How did it go?
Trust is a complex and not complex thing for me as I believe we must have the following to have trust:
- Openness: Being honest about your experiences with life.
- Emotional intelligence: To latch into others understanding and be kind tactful and find meaning full solutions to the others problems.
- To be Listening and Listened to : To know that your being listened to as well as to be a good listener.
Try empathic listening - how did it go?
I tried it. Had to keep pushing my mind back to the conversion in my mind. Just something to practice with.
How did you find the loving kindness meditation?
This was a very complex for me as I am still grappling with issues with my self-confidence and need to stop putting myself down. I will have to work on this as I go forward.
Complete the political awareness exercise here in writing.
When I was working in a company I was shown 2 departments (lighting and Rendering maintenance) that were in 2 diffident buildings but they had strong connection between them. I did not understand why they were not in the same building as I thought it would make more sense to have the 2 departments side by side.
However they were next to the research and development department so they could implement improvements when needed.
Any other musings?
Not this week.


Welcome to open source world!
Rules for Hacktoberfest-2020
- To earn your Hacktoberfest tee or tree reward, you must register and make four valid pull requests (PRs) between October 1-31 (in any time zone).
- PRs can be made to any public repo on GitHub, not only the ones with issues labeled Hacktoberfest.
- If a maintainer reports your pull request as spam or behavior not in line with the project’s code of conduct, you will be ineligible to participate.
- This year, the first 75,000 participants who successfully complete the challenge will be eligible to receive a prize.
Open source- From Anonymous to Unanimous
You think github or open source is complicated ? Worry not Hacktoberfest is here to rescue you !
Hacktoberfest


{% extends 'administrator/main.html' %} {% load encrypt_tags %} {% load static %} {% block content %}
Selected courses would need to be reviewed by the administrator! After submission, you will not be allowed to select courses thereafter. So, you are advised to select all preferred courses.
Your Courses


{# 1. Extend the relevant layout #} {# --------------------------------------- #} {% extends 'sidebar-after.html' %} {# --------------------------------------- #} {# 2. Assign Settings and variables #} {# --------------------------------------- #} {% set id = "standard" %} {% set section = "standard" %} {% set title = "Iati Standard" %} {% set hero_copy = "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. " %} {% set hero_image = "hero1.jpg" %} {# --------------------------------------- #} {# 3. Add models and macros #} {# --------------------------------------- #} {% model 'guidance', as="guidance" %} {% model 'form-support', as="form" %} {% import 'macros/button.html' as buttons %} {% import 'macros/icon.html' as icons %} {# --------------------------------------- #} {# 4. Add page content into relevant areas Add/Delete blocks as necessary #} {# --------------------------------------- #} {% block hero %} {% include 'heroes/hero.html' %} {% endblock %} {% block aside %} {% include 'asides/cta-reference.html' %} {% endblock %} {% block main %}
The IATI Standard is a set of rules and guidance about what data organisations should publish and what format it should be presented in. Find out more information on About the IATI Standard.
The IATI Standard is currently held on the older version of the IATI website and can be accessed using the links below. On these pages you can find all the rules and guidance which make up the IATI Standard. Organisations have to follow these rules when publishing their data.
You can also use these pages to help interpret IATI data. Please see the guide on How to use IATI Reference.
Over time the IATI Standard has been updated. Each version of the Standard has its own page on the website. If you do not actively choose a version, the links below will take you to the latest version of the Standard on the older website.
Version 1 was deprecated on 30th June 2019. Understand how the deprecation affects you.
The rules and guidance which make up the IATI Standard, and other reference pages on the older IATI website are only available in English. However, French translations of the IATI codelists can now be accessed. For more information see Translations FAQs
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor


Let's Learn WebGL is a website that provides WebGL tutorials.
WebGL is short for Web Graphics Library. It's a JavaScript API that allows programmers to create graphics in HTML5 canvas elements. The best part? No plug-ins required! We've made learning even easier by providing an online text editor and a canvas for your graphics. To test it out, click on one of the tutorials below.
This information (and much more about WebGL) can be found at WebGL: 2D and 3D graphics for the web from Mozilla Developer Network (MDN).
To get started, review the Key Concepts pages. Reference pages are provided including further details on select functions and terms. When you are ready to try it out, begin tutorial activities listed below.


|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
The DTD content model handler interface defines callback methods to report information items in DTD content models of an element declaration. Parser components interested in DTD content model information implement this interface and are registered as the DTD content model handler on the DTD content model source.
XMLDTDHandler
| Field Summary | |
|---|---|
static short |
OCCURS_ONE_OR_MORE
This occurrence count limits the element, choice, or sequence in a children content model to one or more. |
static short |
OCCURS_ZERO_OR_MORE
This occurrence count limits the element, choice, or sequence in a children content model to zero or more. |
static short |
OCCURS_ZERO_OR_ONE
This occurrence count limits the element, choice, or sequence in a children content model to zero or one. |
static short |
SEPARATOR_CHOICE
A choice separator for children and mixed content models. |
static short |
SEPARATOR_SEQUENCE
A sequence separator for children content models. |
| Method Summary | |
|---|---|
void |
any(Augmentations augmentations)
A content model of ANY. |
void |
element(java.lang.String elementName,
Augmentations augmentations)
A referenced element in a mixed or children content model. |
void |
empty(Augmentations augmentations)
A content model of EMPTY. |
void |
endContentModel(Augmentations augmentations)
The end of a content model. |
void |
endGroup(Augmentations augmentations)
The end of a group for mixed or children content models. |
XMLDTDContentModelSource |
getDTDContentModelSource()
|
void |
occurrence(short occurrence,
Augmentations augmentations)
The occurrence count for a child in a children content model or for the mixed content model group. |
void |
pcdata(Augmentations augmentations)
The appearance of "#PCDATA" within a group signifying a mixed content model. |
void |
separator(short separator,
Augmentations augmentations)
The separator between choices or sequences of a mixed or children content model. |
void |
setDTDContentModelSource(XMLDTDContentModelSource source)
|
void |
startContentModel(java.lang.String elementName,
Augmentations augmentations)
The start of a content model. |
void |
startGroup(Augmentations augmentations)
A start of either a mixed or children content model. |
| Field Detail |
public static final short SEPARATOR_CHOICE
For example:
<!ELEMENT elem (foo|bar)> <!ELEMENT elem (foo|bar+)> <!ELEMENT elem (foo|bar|baz)> <!ELEMENT elem (#PCDATA|foo|bar)*>
SEPARATOR_SEQUENCE
public static final short SEPARATOR_SEQUENCE
<!ELEMENT elem (foo,bar)> <!ELEMENT elem (foo,bar*)> <!ELEMENT elem (foo,bar,baz)>
SEPARATOR_CHOICE
public static final short OCCURS_ZERO_OR_ONE
For example:
<!ELEMENT elem (foo?)>
OCCURS_ZERO_OR_MORE
,
OCCURS_ONE_OR_MORE
public static final short OCCURS_ZERO_OR_MORE
For example:
<!ELEMENT elem (foo*)> <!ELEMENT elem (#PCDATA|foo|bar)*>
OCCURS_ZERO_OR_ONE
,
OCCURS_ONE_OR_MORE
public static final short OCCURS_ONE_OR_MORE
For example:
<!ELEMENT elem (foo+)>
OCCURS_ZERO_OR_ONE
,
OCCURS_ZERO_OR_MORE
| Method Detail |
public void startContentModel(java.lang.String elementName, Augmentations augmentations) throws XNIException
elementName
- The name of the element.augmentations
- Additional information that may include infoset
augmentations.XNIException
- Thrown by handler to signal an error.public void any(Augmentations augmentations) throws XNIException
augmentations
- Additional information that may include infoset
augmentations.XNIException
- Thrown by handler to signal an error.empty(org.apache.xerces.xni.Augmentations)
,
startGroup(org.apache.xerces.xni.Augmentations)
public void empty(Augmentations augmentations) throws XNIException
augmentations
- Additional information that may include infoset
augmentations.XNIException
- Thrown by handler to signal an error.any(org.apache.xerces.xni.Augmentations)
,
startGroup(org.apache.xerces.xni.Augmentations)
public void startGroup(Augmentations augmentations) throws XNIException
pcdata()
method. A children content model will
contain additional groups and/or elements.augmentations
- Additional information that may include infoset
augmentations.XNIException
- Thrown by handler to signal an error.any(org.apache.xerces.xni.Augmentations)
,
empty(org.apache.xerces.xni.Augmentations)
public void pcdata(Augmentations augmentations) throws XNIException
startGroup()
.augmentations
- Additional information that may include infoset
augmentations.XNIException
- Thrown by handler to signal an error.startGroup(org.apache.xerces.xni.Augmentations)
public void element(java.lang.String elementName, Augmentations augmentations) throws XNIException
elementName
- The name of the referenced element.augmentations
- Additional information that may include infoset
augmentations.XNIException
- Thrown by handler to signal an error.public void separator(short separator, Augmentations augmentations) throws XNIException
separator
- The type of children separator.augmentations
- Additional information that may include infoset
augmentations.XNIException
- Thrown by handler to signal an error.SEPARATOR_CHOICE
,
SEPARATOR_SEQUENCE
public void occurrence(short occurrence, Augmentations augmentations) throws XNIException
occurrence
- The occurrence count for the last element
or group.augmentations
- Additional information that may include infoset
augmentations.XNIException
- Thrown by handler to signal an error.OCCURS_ZERO_OR_ONE
,
OCCURS_ZERO_OR_MORE
,
OCCURS_ONE_OR_MORE
public void endGroup(Augmentations augmentations) throws XNIException
augmentations
- Additional information that may include infoset
augmentations.XNIException
- Thrown by handler to signal an error.public void endContentModel(Augmentations augmentations) throws XNIException
augmentations
- Additional information that may include infoset
augmentations.XNIException
- Thrown by handler to signal an error.public void setDTDContentModelSource(XMLDTDContentModelSource source)
public XMLDTDContentModelSource getDTDContentModelSource()
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


Since Wake Forest did not have a graphic designer, I was tasked with creating our own, on-brand graphics for social media. Here are just two of many that I made.
Plans Book
In order to graduate with a degree in Strategic Communications at KU, you have to take a class called Campaigns. You're given a client and have to make a campaign from start to finish to help them achieve their goals. Here is our final plan book that I created in InDesign. Please feel free to click on the cover to see the full book.


Page Not Found
The page you requested cannot be found. The page you are looking for might have been removed, had its name changed, or is temporarily unavailable.
Please try the following:
- If you typed the page address in the Address bar, make sure that it is spelled correctly.
- Open the http://www.cbd.int/printsmart/ page and look for links to the information you want.
- Click the Back button to try another link.


| Quantum Operators and Gates | ||
| Controlled | Base for multi-bit (multi-controlled one bit) gates. | |
| DoAllBits<class OperatorType> | This class allows any operator to work on all bits of a state. | |
| ModExp | Modular Exponentiation | |
| SingleBit | Base for one-bit gates. | |
| opFFT | Fast Fourier Transform | |
| opHadamard<class BaseClassT> | Hadamard operator [|0> -> |0> + |1> and |1> -> |0> - |1>] | |
| opNOT<class BaseClassT> | SingleBit == Pauli negation, Controlled == CNot | |
| opPhaseShift<class BaseClassT> | Scalar multiplication on z-axis | |
| opRotPhase<class BaseClassT> | Rotation on z-axis | |
| opRotQubit<class BaseClassT> | Rotation on y-axis | |
| opSPhaseShift | Shor's phase shift operator (double-controlled phase shift); | |
| opUnitary<class BaseClassT> | General Unitary operator. | |
| Quantum State [OpenQubit Core] | ||
| QState | Model of a quantum state/register | |
| RandLib | ||
| DblUniformRandGenerator | Double-precision RNG using "uniform" algorithm | |
| IntStdRandGenerator | Integer RNG encapsulating standard functions like rand() | |
| IntUniformRandGenerator | Integer RNG using "uniform" algorithm | |
| RandGenerator<class T> | Interface to which all RNG classes in RandLib must conform |


Owning Palette: Logger
Requires: Logger
Use the Utility VIs to handle errors.
| Palette Object | Description |
|---|---|
| Catch Error | Handle and log an error. |
| Create Statement CSV | Create a CSV line of text from a log statement. |
| Create Temporary Root Folder | Create a location for log files in the user's temporary folder. |
| Disable Default File | Disable the default file logger. |
| Mask Errors | Log all errors but clear any from a list of error codes. |


| 3.5 Estimating Parameters | |
|
The traditional FRAP fitting is usually done based on the bleached area for a single diffusion rate. The Virtual FRAP is able to fit more accurately by taking the spatial data into account. The fitting is conducted over all the selected ROI rings instead of only bleached area. Moreover, the Virtual FRAP is able to deal with a secondary diffusion rate. The estimated parameters for one diffusing component are primary diffusion rate, primary mobile fraction and bleaching while monitoring rate. The estimated parameters for two diffusing components are primary diffusion rate, primary mobile fraction, secondary diffusion rate, secondary mobile fraction and bleaching while monitoring rate. The last step of data analysis work flow is to estimate diffusion parameters. To start the estimation wizard, users need to click on the “Estimate Parameters” button . A spatial reference simulation is then started and followed by optimization. The best estimates are acquired by minimizing the errors between the simulated data and the experimental data.
Once the simulation and optimization is completed, the results for selected models will be shown in the different wizard pages. Figure 3-10 shows the estimate results page for two diffusing components. The top half of the page displays the best estimates for such a model. The bottom half is a real-time plot which illustrates the difference between simulated data and experimental data according to the parameter changes. In this page, users are able to tune a primary diffusion rate together with a secondary diffusion rate and the bleach while monitoring rate. Users can set values either by typing into the text fields or tuning the slider bars. The different colors of the plots represent how the diffusion works in different ROIs of the cell. Clicking on the show ROIs button will show the ROIs distinguished by different colors. Users can click on the best fit button to get the best fit parameters based on the current parameter initials in the text fields. In addition, the Virtual FRAP evaluates the confidence intervals for each parameter. By clicking evaluate confidence interval button , the evaluation then starts and the results will be shown in the confidence interval panel shown in Figure 3-11. The confidence interval panel contains several plot panels, one for each parameter. All the plot panels are able to be expanded or collapsed and the default plot is for primary diffusion rate. Users can click on to expand a specific plot panel or to collapse a specific plot panel. The x-axis in the plot is the log base 10 ratio of parameter value and the y-axis is the likelihood of the simulated results. The Virtual FRAP has built in confidence levels which are 80%, 90%, 95% and 99%. Horizontal lines with different colors denote different confidence levels in the plot. At the bottom of the confidence plot, a table listed the confidence intervals according to the confidence levels.
Figure 3-10 Parameter Estimation Results for Two Diffusing Components
Figure 3-11 The Confidence Interval Panel
The last page of “Estimate Parameters” wizard is a summary page. The page has four parts. Firstly, a table lists all estimates for one or two models according to the selection. This is visible by default. Secondly, a plot contains all the plots for experimental data and simulated selected model data, which is invisible by default. The third part is a table showing errors between experimental data and simulated data under each ROI for selected models. The last part allows users to choose the best model base on their judgement, however, a machine made decision will be given by default. The summary page is illustrated in Figure 3-12.
Figure 3-12 The Summary Page in “Estimate Parameters” Wizard
|


| File | Statements | Branches | Functions | Lines | |||||
|---|---|---|---|---|---|---|---|---|---|
| BaseSystem.sol | 100% | 3/3 | 100% | 2/2 | 100% | 2/2 | 100% | 4/4 | |
| Coordinator.sol | 68.29% | 28/41 | 66.67% | 16/24 | 75% | 6/8 | 67.5% | 27/40 | |
| Core.sol | 100% | 24/24 | 57.14% | 8/14 | 100% | 8/8 | 100% | 25/25 | |
| CoreLib.sol | 100% | 0/0 | 100% | 0/0 | 100% | 0/0 | 100% | 0/0 | |
| Executables.sol | 79.17% | 19/24 | 80% | 8/10 | 83.33% | 5/6 | 79.17% | 19/24 | |
| Proposals.sol | 84.09% | 37/44 | 50% | 13/26 | 75% | 12/16 | 84.44% | 38/45 | |
| VoteWeight.sol | 87.5% | 7/8 | 50% | 1/2 | 100% | 4/4 | 87.5% | 7/8 | |
| VotingBooth.sol | 93.75% | 15/16 | 100% | 4/4 | 85.71% | 6/7 | 93.75% | 15/16 |


|
WUT Velma robot API
|
This class contains subsystem-specific diagnostic information for velma_core_cs. More...
Public Member Functions | |
| def | __init__ (self, parent) |
| Initialization of diagnostics data using subsystem-independent diagnostics object. More... | |
| def | getCurrentStateName (self) |
| def | inStateIdle (self) |
| Information about current state. More... | |
| def | inStateSafe (self) |
| Information about current state. More... | |
| def | inStateCartImp (self) |
| Information about current state. More... | |
| def | inStateJntImp (self) |
| Information about current state. More... | |
| def | inStateRelax (self) |
| Information about current state. More... | |
| def | isSafeReasonSelfCol (self) |
| Information about reason for entering 'safe' state. More... | |
| def | isSafeReasonIdle (self) |
| Information about reason for entering 'safe' state. More... | |
| def | motorsReady (self) |
| Information about state of head and torso motors. More... | |
Public Attributes | |
| history | |
| current_predicates | |
| current_period | |
This class contains subsystem-specific diagnostic information for velma_core_cs.
Definition at line 967 of file velma_interface.py.
| def velma_common.velma_interface.VelmaInterface.CoreCsDiag.__init__ | ( | self, | |
| parent | |||
| ) |
Initialization of diagnostics data using subsystem-independent diagnostics object.
| parent | subsystem_common.SubsystemDiag: subsystem-independent diagnostics object. |
| AssertionError | Raised when current state name cannot be obtained or state history is not present. |
Definition at line 971 of file velma_interface.py.
| def velma_common.velma_interface.VelmaInterface.CoreCsDiag.getCurrentStateName | ( | self | ) |
Definition at line 989 of file velma_interface.py.
| def velma_common.velma_interface.VelmaInterface.CoreCsDiag.inStateCartImp | ( | self | ) |
Information about current state.
Definition at line 1006 of file velma_interface.py.
| def velma_common.velma_interface.VelmaInterface.CoreCsDiag.inStateIdle | ( | self | ) |
Information about current state.
Definition at line 992 of file velma_interface.py.
| def velma_common.velma_interface.VelmaInterface.CoreCsDiag.inStateJntImp | ( | self | ) |
Information about current state.
Definition at line 1013 of file velma_interface.py.
| def velma_common.velma_interface.VelmaInterface.CoreCsDiag.inStateRelax | ( | self | ) |
Information about current state.
Definition at line 1020 of file velma_interface.py.
| def velma_common.velma_interface.VelmaInterface.CoreCsDiag.inStateSafe | ( | self | ) |
Information about current state.
Definition at line 999 of file velma_interface.py.
| def velma_common.velma_interface.VelmaInterface.CoreCsDiag.isSafeReasonIdle | ( | self | ) |
Information about reason for entering 'safe' state.
| AssertionError | Raised when current state is not 'safe' or history contain only one entry. |
Definition at line 1041 of file velma_interface.py.
| def velma_common.velma_interface.VelmaInterface.CoreCsDiag.isSafeReasonSelfCol | ( | self | ) |
Information about reason for entering 'safe' state.
| AssertionError | Raised when current state is not 'safe'. |
| KeyError | Raised when 'inSelfCollision' predicate cannot be obtained. |
Definition at line 1027 of file velma_interface.py.
| def velma_common.velma_interface.VelmaInterface.CoreCsDiag.motorsReady | ( | self | ) |
Information about state of head and torso motors.
| KeyError | Raised when 'motorsReady' predicate cannot be obtained. |
Definition at line 1051 of file velma_interface.py.
| velma_common.velma_interface.VelmaInterface.CoreCsDiag.current_period |
Definition at line 982 of file velma_interface.py.
| velma_common.velma_interface.VelmaInterface.CoreCsDiag.current_predicates |
Definition at line 981 of file velma_interface.py.
| velma_common.velma_interface.VelmaInterface.CoreCsDiag.history |
Definition at line 980 of file velma_interface.py.


-
DKK
DESCRIPTION:
GROUP SIZE:
DURATION:
START TIME:
AGE RESTRICTION:
HEIGHT RESTRICTION:
Delete Activity
Update Activity
Back


Welcome to Org Manager—the organization management tool.
Please register or log in if you already have an account.


Liquid Test
Links
-
[](/): this link should do nothing
-
[](#): this link should do nothing
-
[](http://duckduckgo.com): this link should open a new browser window
-
[target="_blank"](http://duckduckgo.com): this link should open a new browser window
-
[target="_blank"](/): this link should go to /
Forms
-
-
-
-
JavaScript
-
Is JavaScript disabled?
-
Is Custom JS injection in check?
-
alert()
User-Agent
-
User-Agent string:
Sandboxing
-
It's okay to see this remote picture:
-
You should never ever see the contents of this iframe:


Time Start: ${encounterStart} | Time End: ${encounterEnd}
${fightName}
${bossHealth} Health
Result: ${encounterResult}
Duration: ${encounterDuration}
Loading data...


Vim Tricks Mort Yao Get back to insert mode when accidentally hit C-x C-s Get back to insert mode when accidentally hit C-x C-s Try C-q. Source: http://superuser.com/a/109170/231575


Abstract
HTML-TEMPLATE is a portable library for Common Lisp which can be used to fill templates with arbitrary (string) values at runtime. (Actually, it doesn't matter whether the result is HTML. It's just very likely that this will be what the library is mostly used for.)It is loosely modeled after the Perl module HTML::Template and compatible with a subset of its syntax, i.e. it should be possible to use your HTML-TEMPLATE templates with HTML::Template as well (but usually not the other way around).
HTML-TEMPLATE translates templates into efficient closures which can be re-used as often as needed. It uses an intelligent cache mechanism so you can nevertheless update templates while your program is running and have the changes take effect immediately.
The rationale behind something like HTML-TEMPLATE or HTML::Template is that you want to separate code and layout (I think in Newspeak these are called the "Business Layer" and the "Presentation Layer") as much as possible when generating HTML, especially if you work with graphical artists who are responsible for the visual appearance of your site but aren't programmers. Matter of fact, you can't separate code and layout completely. I've worked (or had to work) with several different approaches over the years, including emitting HTML from CGI scripts directly, using tools like Embperl, Mason, PHP (yuk!), or Java/XML/XLST stuff, or employing different Lisp markup languages but found that HTML::Template's approach usually works best for me: The graphical designers only need to learn a minimal set of new tags (three of them) and can update their templates independently from the work done on the backend. It is simple and it just works. YMMV, of course...
HTML-TEMPLATE is intended to be portable and should work with all conforming Common Lisp implementations but is mainly tested and deployed on Linux with LispWorks and CMUCL. Let us know if you encounter any problems.
It comes with a BSD-style license so you can basically do with it whatever you want.
HTML-TEMPLATE is used by Planet Lisp, Booble, ERGO and Heike Stephan.
Download shortcut: http://weitz.de/files/html-template.tar.gz.
create-template-printer
fill-and-print-template
clear-template-cache
delete-from-template-cache
*template-start-marker*
*template-end-marker*
*default-template-pathname*
*default-template-output*
*convert-nil-to-empty-string*
*sequences-are-lists*
*upcase-attribute-strings*
*template-symbol-package*
*no-cache-check*
*force-default*
*value-access-function*
*ignore-empty-lines*
*warn-on-creation*
template-error
template-invocation-error
template-missing-value-error
template-not-a-string-error
template-not-a-string-error-value
template-syntax-error
template-syntax-error-stream
template-syntax-error-line
template-syntax-error-col
If you have a text file
#p"/tmp/foo.tmpl"
like this

then the following code
(let* ((rows (loop for i below 49 by 7 collect (list :cols (loop for j from i below (+ i 7) for string = (format nil "~R" j) collect (list :content string :colorful-style (oddp j)))))) (values (list :rows rows))) (fill-and-print-template #p"/tmp/foo.tmpl" values))will produce this HTML table:
| zero | one | two | three | four | five | six |
| seven | eight | nine | ten | eleven | twelve | thirteen |
| fourteen | fifteen | sixteen | seventeen | eighteen | nineteen | twenty |
| twenty-one | twenty-two | twenty-three | twenty-four | twenty-five | twenty-six | twenty-seven |
| twenty-eight | twenty-nine | thirty | thirty-one | thirty-two | thirty-three | thirty-four |
| thirty-five | thirty-six | thirty-seven | thirty-eight | thirty-nine | forty | forty-one |
| forty-two | forty-three | forty-four | forty-five | forty-six | forty-seven | forty-eight |
If you're on Debian you should probably use the cl-html-template Debian package which is available thanks to Peter van Eynde and Kevin Rosenberg. There's also a port for Gentoo Linux thanks to Matthew Kennedy.
HTML-TEMPLATE comes with simple system definitions for MK:DEFSYSTEM and asdf so you can either adapt it
to your needs or just unpack the archive and from within the HTML-TEMPLATE
directory start your Lisp image and evaluate the form
(mk:compile-system "html-template")
(or the
equivalent one for asdf) which should compile and load the whole
system. Installation via asdf-install should also
be possible.
If for some reason you don't want to use MK:DEFSYSTEM or asdf you
can just LOAD
the file load.lisp
or you
can also get away with something like this:
(loop for name in '("packages" "specials" "errors" "util" "template" "api") do (compile-file (make-pathname :name name :type "lisp")) (load name))Note that on CL implementations which use the Python compiler (i.e. CMUCL, SBCL, SCL) you can concatenate the compiled object files to create one single object file which you can load afterwards:
cat {packages,specials,errors,util,template,api}.x86f > html-template.x86f(Replace ".
x86f
" with the correct suffix for
your platform.)
The distribution includes a test file
"test.lisp
" which you can LOAD
after loading HTML-TEMPLATE itself to check if everything works as
intended. If all is well you should just see these two messages:
Please wait a couple of seconds. All tests passed...Some of the tests assume the existence of a directory
#p"/tmp/"
where you can create files. If you're on
Windows you should probably change this - see the variable
TMP-DIR
in test.lisp
.
Note that there is no public CVS repository for HTML-TEMPLATE - the repository at common-lisp.net is out of date and not in sync with the (current) version distributed from weitz.de.
where name is one of
TMPL_VAR
,
TMPL_LOOP
, TMPL_IF
, TMPL_UNLESS
,
TMPL_INCLUDE
, /TMPL_LOOP
,
/TMPL_IF
, /TMPL_UNLESS
, or TMPL_ELSE
. Case doesn't matter,
i.e. tmpl_var
or Tmpl_Var
would also be
legal names.
If name is one of the first four listed above then
attribute must follow, otherwise it must not follow where
attribute is any sequence of characters delimited by
"
, '
, or by whitespace. There's
currently no way to escape the delimiters, i.e. if the attribute
starts with "
then the next "
(and
nothing else) will end it.
Any amount (including the empty string) of whitespace directly after
'
' is
optional and will be ignored. However, at least one whitespace
character between name and attribute (if present) is
mandatory. But note that if attribute is not delimited by
"
or '
then there must be whitespace to
separate attribute from the closing '-->
'.
The following are examples for legal template tags
     But note that in the last example the attribute is '
foo-->    <tmpl_include "/tmp/foo.html">
TMPL_VAR
must always be followed by an attribute (1st
example) while TMPL_ELSE
must not (2nd example). The
third one isn't recognized as a template tag because of the missing
whitespace behind TMPL_VAR
. The tag will simply be
ignored and the parser will look for the next occurence of
' text   text  text'   text where text and text' themselves must be valid templates. In other words: These constructs must nest properly.
Note that, despite of its name, HTML-TEMPLATE knows absolutely nothing about HTML syntax so you can use it for other texts as well. Also, because the templates are filled in before they're sent to the browser, you can use template tags anywhere you like and not only in places where HTML comments would be legal. These two examples, e.g., will work:
 End of comment --> foobar
CREATE-TEMPLATE-PRINTER
will convert a template into a template printer. A
template printer is a function which accepts one argument - a
template structure - which describes how the template should
be filled and prints the filled template to the stream bound to the
internal variable *TEMPLATE-OUTPUT*
. You can
FUNCALL
a template printer but the preferred way to use
it is to invoke it with FILL-AND-PRINT-TEMPLATE
(which can also create template printers as needed). Note that
template printers are compiled closures but although you'll usually
create them at runtime the Lisp compiler isn't invoked for this task
so you can safely excise it from your image if you so wish.
For the rest of this document we will make a distinction between
generation time which is the time the template printer is
created (either explicitely by CREATE-TEMPLATE-PRINTER
or implicitely by FILL-AND-PRINT-TEMPLATE
)
and invocation time which is the time the printer is used (by
FUNCALL
or FILL-AND-PRINT-TEMPLATE
)
to fill and print a template.
Each of the template tags TMPL_VAR
, TMPL_IF
, TMPL_UNLESS
,
and TMPL_LOOP
is associated with a particular symbol at
generation time. This symbol is the result of INTERN
ing
the tag's attribute string into the package *TEMPLATE-SYMBOL-PACKAGE*
. The
template structure - the argument given to the template
printer - associates these symbols with values. By default this is
done by means of a property list but this can be changed at template invocation
time by changing the contents of the variable *VALUE-ACCESS-FUNCTION*
. (Note
that the name doesn't imply that template structures are structures in
the sense of Common Lisp. Usually they aren't.)
The template tags work as follows:

This tag will be replaced by the value associated with symbol which should be a string (or maybeNIL
- see*CONVERT-NIL-TO-EMPTY-STRING*
).* (let ((tp (create-template-printer "Hello !"))) (fill-and-print-template tp '(:foo "World")) (terpri) (fill-and-print-template tp '(:foo "Folks"))) Hello World! Hello Folks!
text
text
In the first case, if the value associated with symbol is notNIL
the (sub-)template text will be filled and printed. Otherwise, the whole construct will be replaced by an empty string. In the second case, it's the other way around.* (let ((tp (create-template-printer "The quick brown fox"))) (fill-and-print-template tp '(:fast t)) (terpri) (fill-and-print-template tp '(:fast nil))) The quick brown fox The brown fox
texttext'
texttext'
In the first case, if the value associated with symbol is notNIL
the (sub-)template text will be filled and printed. Otherwise, text' is used instead. In the second case, it's the other way around.* (let ((tp (create-template-printer "The quickslow brown fox"))) (fill-and-print-template tp '(:fast t)) (terpri) (fill-and-print-template tp '(:fast nil))) The quick brown fox The slow brown fox
text
The value associated with symbol should be a sequence (see*SEQUENCES-ARE-LISTS*
) of template structures. For each element of this sequence the (sub-)template text is filled and printed using the corresponding template structure.Note that each template (sub-)structure which is used to fill text introduces a new set of associations between symbols and their values. While the template printer is within text the outer template structure is temporarily "forgotten".
* (defparameter *tp* (create-template-printer "[,]")) *TP* * (fill-and-print-template *tp* '(:foo ((:bar "EINS" :baz "ONE") (:bar "ZWEI" :baz "TWO")))) [EINS,ONE][ZWEI,TWO] * (fill-and-print-template *tp* '(:baz "ONE" :foo ((:bar "EINS") (:bar "UNO")))) [EINS,][UNO,]

The string pathname should be a valid pathname for an existing textfile. This textfile is implicitely converted into a template printer at generation time as if it were explicitely converted by a call toCREATE-TEMPLATE-PRINTER
. At invocation time the tag will be replaced by the result ofFUNCALL
ing this template printer with the current template structure. (Note that this implies that the included file has to be a valid template, i.e. you can't, say, have aTMPL_IF
tag in your main file and put the closing/TMPL_IF
into the included file.)* (with-open-file (s "/tmp/foo" :direction :output :if-exists :supersede) (write-string "The quick brown fox" s)) "The quick brown fox" * (fill-and-print-template " jumps over the lazy dog" '(:fast t)) Warning: New template printer for #p"/tmp/foo" created The quick brown fox jumps over the lazy dog * (fill-and-print-template " jumps over the lazy dog" '(:fast nil)) The brown fox jumps over the lazy dogThese tags can be nested, i.e. included files can themselves include other files. Included template printers are always taken from the cache at invocation time which means you can update them seperately from the including printer.
[Generic function]
create-template-printer template &key force element-type if-does-not-exist external-format => printer
This function will create and return a template printerprinter
created from the template denoted bytemplate
. The behaviour of this function depends on the type oftemplate
.This function will signal an error of type
- If
template
is a stream it should be an open input stream which is read character by character withREAD-CHAR
and the resulting text is used as the template.- If
template
is a string it is converted into a string stream which is again fed intoCREATE-TEMPLATE-PRINTER
.- If
template
is a pathname it should denote an existing text file. The file is opened byWITH-OPEN-FILE
and the resulting stream is again fed intoCREATE-TEMPLATE-PRINTER
. All keyword arguments exceptforce
are used as keyword arguments forWITH-OPEN-FILE
. The pathname will be merged with*DEFAULT-TEMPLATE-PATHNAME*
before it is used.HTML-TEMPLATE maintains a cache of previously created template printers. If the (merged) pathname can be found in this cache and the file denoted by this pathname hasn't changed since the associated cached template printer was created (which is tested by
FILE-WRITE-DATE
) the cached value will be used and no new template printer will be created. This can be overriden by the keyword argumentforce
, i.e. whenforce
is true a new template printer will unconditionally be created (and cached unlessforce
is the keyword:DO-NOT-CACHE
). The default value forforce
is the value of*FORCE-DEFAULT*
. (See also*NO-CACHE-CHECK*
.) Note that you may have to useforce
if you've changed one of the special variables described below and want to create a template printer based on these new settings although the template file itself hasn't changed. Also note thatFILE-WRITE-DATE
might not be able to see a difference if the never version of a file is only fractions of a second newer than the older one.TEMPLATE-INVOCATION-ERROR
iftemplate
is not a pathname and one of the keyword arguments is provided.* (with-input-from-string (stream "The  brown fox") (funcall (create-template-printer stream) '(:speed "quick"))) The quick brown fox * (funcall (create-template-printer "The  brown fox") '(:speed "slow")) The slow brown fox * (with-open-file (stream "/tmp/foo.tmpl" :direction :output) (write-string "The  brown fox" stream)) "The  brown fox" * (funcall (create-template-printer #p"/tmp/foo.tmpl") '(:speed "fast")) Warning: New template printer for #p"/tmp/foo.tmpl" created The fast brown fox * (funcall (create-template-printer #p"/tmp/foo.tmpl") '(:speed "extremely fast")) The extremely fast brown fox * (funcall (create-template-printer #p"/tmp/foo.tmpl" :force t) '(:speed "very fast")) Warning: New template printer for #p"/tmp/foo.tmpl" created The very fast brown fox * (probe-file "/tmp/bar.tmpl") NIL * (funcall (create-template-printer #p"/tmp/bar.tmpl" :if-does-not-exist :create) '(:foo "foo")) Warning: New template printer for #p"/tmp/bar.tmpl" created * (probe-file "/tmp/bar.tmpl") #p"/tmp/bar.tmpl"
[Generic function]
fill-and-print-template template/printer values &key stream &allow-other-keys => <no values>
This function will fill the template denoted bytemplate/printer
with the values provided byvalues
and print the resulting text tostream
which defaults to*DEFAULT-TEMPLATE-OUTPUT*
. The value ofvalues
should be a template structure matching the current value of*VALUE-ACCESS-FUNCTION*
.If
template/printer
is a function it will be used as if it were a template printer. Otherwise,template/printer
will first be fed intoCREATE-TEMPLATE-PRINTER
and the resulting template printer will be used. Note that this implies that the caching mechanism described above is in effect here as well.If
template/printer
is a pathname all keyword arguments except forstream
will be used as keyword arguments forCREATE-TEMPLATE-PRINTER
. If it is not a pathname keyword arguments other thanstream
will result in an error of typeTEMPLATE-INVOCATION-ERROR
.* (fill-and-print-template "The  brown fox" '(:speed "slow")) The slow brown fox * (with-input-from-string (stream "The  brown fox") (fill-and-print-template stream '(:speed "quick"))) The quick brown fox * (with-open-file (stream "/tmp/foo.tmpl" :direction :output :if-exists :supersede) (write-string "The  brown fox" stream)) "The  brown fox" * (fill-and-print-template #p"/tmp/foo.tmpl" '(:speed "fast")) Warning: New template printer for #p"/tmp/foo.tmpl" created The fast brown fox * (fill-and-print-template #p"/tmp/foo.tmpl" '(:speed "very fast")) The very fast brown fox * (let ((tp (create-template-printer "The  brown fox"))) (fill-and-print-template tp '(:speed "tardy"))) The tardy brown fox
[Function]
clear-template-cache => <no values>
This function will completely clear the cache used by HTML-TEMPLATE.
[Function]
delete-from-template-cache pathname => result
This function will remove the template printer associated withpathname
from HTML-TEMPLATE's cache.result
is true if there was such a template printer, orNIL
otherwise.
[Special variable]
*template-start-marker*
This should be a string (the default is""
) which is used at generation time to determine the end of a template tag.* (let ((*template-start-marker* "<") (*template-end-marker* ">")) (fill-and-print-template "The <TMPL_VAR 'speed'> <brown> fox" '(:speed "quick"))) The quick <brown> fox
[Special variable]
*default-template-pathname*
This should be a pathname (the default is the result of callingMAKE-PATHNAME
with no arguments) which is merged with the sole argument ofCREATE-TEMPLATE-PRINTER
if this argument is a pathname.* (with-open-file (stream "/tmp/foo.tmpl" :direction :output :if-exists :supersede) (write-string "The  brown fox" stream)) "The  brown fox" * (setq *default-template-pathname* #p"/tmp/") #p"/tmp/" * (fill-and-print-template #p"foo.tmpl" '(:speed "very fast")) Warning: New template printer for #p"/tmp/foo.tmpl" created The very fast brown fox
[Special variable]
*default-template-output*
This should be a stream (the default is*STANDARD-OUTPUT*
) which is used as the output stream ofFILL-AND-PRINT-TEMPLATE
if nostream
keyword argument was provided.* (fill-and-print-template "The  brown fox" '(:speed "slow")) The slow brown fox * (with-output-to-string (*default-template-output*) (fill-and-print-template "The  brown fox" '(:speed "slow"))) "The slow brown fox"
[Special variable]
*convert-nil-to-empty-string*
If the values of this variable is trueTMPL_VAR
tags will be replaced by the empty string if the associated value isNIL
, otherwise an error of typeTEMPLATE-MISSING-VALUE-ERROR
is signaled. The default isT
. This variable takes effect at invocation time.* (let ((tp (create-template-printer "The  brown fox"))) (handler-bind ((template-missing-value-error (lambda (condition) (declare (ignore condition)) (use-value "slow")))) (let ((*convert-nil-to-empty-string* nil)) (fill-and-print-template tp '(:foo "bar"))))) The slow brown fox
[Special variable]
*sequences-are-lists*
If the values of this variable is true (which is the default) the code generated by aTMPL_LOOP
tag expects its associated value to be a list, otherwise it expects it to be a vector. This variable takes effect at generation time.* (fill-and-print-template "[]" '(:list ((:item "1") (:item "2") (:item "3")))) [1][2][3] * (let ((*sequences-are-lists* nil)) (fill-and-print-template "[]" '(:vector #((:item "1") (:item "2") (:item "3"))))) [1][2][3]
[Special variable]
*upcase-attribute-strings*
If the values of this variable is true (which is the default) attribute strings are fed toSTRING-UPCASE
before they are interned. This variable takes effect at generation time.* (let ((*upcase-attribute-strings* nil)) (fill-and-print-template "The  brown fox" '(:speed "quick" :|speed| "slow"))) The slow brown fox
[Special variable]
*template-symbol-package*
The value of this variable should be a package designator designating the package attribute strings are interned into. The default is the KEYWORD package. This variable takes effect at generation time.* *package* #<The COMMON-LISP-USER package, 20/21 internal, 0/9 external> * (let ((*template-symbol-package* (find-package :common-lisp-user))) (fill-and-print-template "The  brown fox" '(:speed "quick" speed "slow"))) The slow brown fox
[Special variable]
*no-cache-check*
If the value of this variable is true (the default isNIL
)CREATE-TEMPLATE-PRINTER
andFILL-AND-PRINT-TEMPLATE
won't check whether a template file has changed since it has been cached but instead will always use the cached template printer if there is one, i.e. there will be no more disk I/O once all template printers are generated. This option is intended to be used for sites with heavy traffic when you don't expect your templates to change anymore.
[Special variable]
*force-default*
The default value for theforce
keyword argument toCREATE-TEMPLATE-PRINTER
.
[Special variable]
*value-access-function*
The value of this variable should be a function of two arguments (symbol
andvalues
) which is used to associate symbols with their values when a template printer is invoked. The default value is#'(lambda (symbol values) (getf values symbol))
. This variable takes effect at invocation time.* (let ((tp (create-template-printer "The  brown fox")) (*value-access-function* #'gethash) (hash (make-hash-table :test #'eq))) (setf (gethash :speed hash) "fast") (fill-and-print-template tp hash)) The fast brown fox
[Special variable]
*ignore-empty-lines*
If the value of this variable is true (the default isNIL
) template printers will suppress any whitespace in front of template tags up to (but excluding) the first#\Newline
and any whitespace behind template tags up to (and including) the first#\Newline
. This holds for all tags exceptTMPL_VAR
. The idea is that you might want to put tags likeTMPL_LOOP
on lines of their own in order to increase the legibility of your template files without creating unnecessary empty lines in your output. This variable takes effect at generation time.* (with-open-file (s "/tmp/foo.tmpl" :direction :input) (loop for line = (read-line s nil nil) while line do (print line)) (values)) "
" " " "
" " " " 	" " " "
" " " "
" * (let ((values (list :row-loop (loop for row in '((1 2 3 4) (2 3 4 5) (3 4 5 6)) collect (list :col-loop (loop for col in row collect (list :item (format nil "~A" col))))))) (*ignore-empty-lines* t)) (fill-and-print-template #p"/tmp/foo.tmpl" values :force t)) Warning: New template printer for #p"/tmp/foo.tmpl" created

 1	 2	 3	 4

 2	 3	 4	 5

 3	 4	 5	 6

[Special variable]
*warn-on-creation*
If this variable is true (which is the default)CREATE-TEMPLATE-PRINTER
will warn you whenever a template printer is newly created from a pathname argument instead of being taken from the cache.
[Condition type]
template-error
Every error signaled by HTML-TEMPLATE is of typeTEMPLATE-ERROR
. This is a direct subtype ofSIMPLE-ERROR
without any additional slots or options.
[Condition type]
template-invocation-error
Errors of typeTEMPLATE-INVOCATION-ERROR
are signaled ifCREATE-TEMPLATE-PRINTER
orFILL-AND-PRINT-TEMPLATE
are called with wrong keyword arguments. This is a direct subtype ofTEMPLATE-ERROR
without any additional slots or options.
[Condition type]
template-missing-value-error
An error of typeTEMPLATE-MISSING-VALUE-ERROR
is signaled if a template printer forTMPL_VAR
is provided with aNIL
value although*CONVERT-NIL-TO-EMPTY-STRING*
is false. This is a direct subtype ofTEMPLATE-ERROR
without any additional slots or options. Whenever aTEMPLATE-MISSING-VALUE-ERROR
is signaled, an associatedUSE-VALUE
restart is available.
[Condition type]
template-not-a-string-error
An error of typeTEMPLATE-NOT-A-STRING-ERROR
is signaled if a template printer forTMPL_VAR
is provided with a value which is neither a string norNIL
. This is a direct subtype ofTEMPLATE-ERROR
with one additional slot for the value which can be read byTEMPLATE-NOT-A-STRING-ERROR-VALUE
. Whenever aTEMPLATE-NOT-A-STRING-ERROR
is signaled, an associatedUSE-VALUE
restart is available.
[Function]
template-not-a-string-error-value condition => value
Ifcondition
is a condition of typeTEMPLATE-NOT-A-STRING-ERROR
this function will return the (non-string) value causing the error.* (let ((tp (create-template-printer "A square has  corners"))) (handler-bind ((template-not-a-string-error (lambda (condition) (use-value (format nil "~R" (template-not-a-string-error-value condition)))))) (fill-and-print-template tp '(:number 4)))) A square has four corners
[Condition type]
template-syntax-error
An error of typeTEMPLATE-SYNTAX-ERROR
is signaled at generation time when HTML-TEMPLATE is not able to create a template printer due to syntax errors in the template. This is a direct subtype ofTEMPLATE-ERROR
with three additional slots. These denote the stream from which HTML-TEMPLATE was reading when it encountered the error and a line and column within this stream. (See the next three entries on how to access these slots.)As many syntax errors can't be detected before the parser is at the end of the stream, the row and column usually denote the last position where the parser was happy and not the position where it gave up.
* (handler-case (fill-and-print-template "A square has  corners" '(:number "four")) (template-syntax-error (condition) (format t "Houston, we've got a problem on stream ~A:~%~ Looks like something went wrong after line ~A, column ~A.~%~ The last message we received was '~?'." (template-syntax-error-stream condition) (template-syntax-error-line condition) (template-syntax-error-col condition) (simple-condition-format-control condition) (simple-condition-format-arguments condition)) (values))) Houston, we've got a problem on stream #<String-Input Stream>: Looks like something went wrong after line 1, column 26. The last message we received was 'Unexpected EOF'.Note that column 26 is the position directly behind"TMPL_VAR"
.
[Function]
template-syntax-error-stream condition => stream
Ifcondition
is a condition of typeTEMPLATE-SYNTAX-ERROR
this function will return the stream the parser was reading from when the error was encountered.
[Function]
template-syntax-error-line condition => number
Ifcondition
is a condition of typeTEMPLATE-SYNTAX-ERROR
this function will return the line number which was associated with this error. As in Emacs, lines are counted beginning with 1. HTML-TEMPLATE increases the line counter whenever it reads a#\Newline
from its input stream.
[Function]
template-syntax-error-col condition => number
Ifcondition
is a condition of typeTEMPLATE-SYNTAX-ERROR
this function will return the column number which was associated with this error. As in Emacs, columns are counted beginning with 0.
Thanks to James Anderson and Kent M. Pitman who helped to de-confuse me about restarts.
$Header: /usr/local/cvsrep/html-template/doc/index.html,v 1.37 2006/04/03 08:35:54 edi Exp $


https://support.mozilla.org/en-US/questions/1083282
Sometimes if you try to use firefox to browse 'restricted' ports (ie 21, 22, etc) firefox will block you.
You can create a preference using about:config and allow the port number which Firefox is blocking. Here's how:
(0) Select and copy the following preference name
network.security.ports.banned.override
(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.
(2) In the search box above the list, type or paste ports and pause while the list is filtered
If the above-listed preference exists:
(3) Double-click it and add a comma to the end of the list followed by the port number you need to allow. No spaces. Then click OK.
If the above-listed preference does not exist:
(4) right-click anywhere on the page and choose New > String
(5) In the preference name dialog, paste the name you coped and click OK
(6) In the preference value dialog, type in the port number you need to allow, then click OK.


7,000 cattle ‘moo’ into Punjab town, turn heads
by Gautam DheerAuthorities in the border state of Punjab went into a huddle after they learnt of an unexpected feisty advance of an alarming magnitude towards the sacred town of Sultanpur Lodi.
The revered town, which has been the epicentre of the celebration for the 550th birth anniversary of Guru Nanak Dev, had already been swamped by lakhs of devotees. Authorities had no clue how to manage the unprecedented cattle march— a whopping number of over 7,000 cattle heads— set in motion after a Nihang sect ventured into a journey to reach Sultanpur Lodi along with their cattle which they had been nursing for long. Authorities swung into action to stop the entry of the bovines about 20 km away from the town.
With the cattle owners refusing to go back, hectic negotiations ensued for two days.
With no headway, a temporary truce was arrived at as thousands of cattle were pushed into a college stadium in Fattudhinga village.
The administration and villagers provided fodder to the ‘bovine guests.’
On Monday morning sanity finally prevailed with the retreat of the 7,000 animals. The chaos was averted.
Had they not retreated, government’s crores of rupees spent on upkeep, cleanliness and plantation in Sultanpur Lodi might have gone down the drain. The Nihang sect argued they had been doing this for years.


Guide to the examples
The examples included are listed roughly in increasing level of complexity. Source transformations and AST transformations can be used interactively in IPython/Jupyter environments; bytecode transformations and custom encoding cannot.
Source transformations
nobreak as a keyword
This is a sligthly more complex example than ‘function as a keyword’, as it shows how to keep track of indentation level and only replace a keyword when some conditions are met.
repeat as a keyword
This includes four different transformations, one of which requires to add some extra variables to the original code. It is done in a way that avoid any conflict with existing variable names.
It also shows how to include some parameters that are passed back to the source transformation.
French Python
This is a source transformation that allows one
to use French equivalent keywords to the existing ones.
It shows how to make use of a different file extension (.pyfr
),
loading such files as if they were regular Python files.
French repeat
Extends the French keywords from French Python to include those in repeat as a keyword. It then combines both examples into a single transformation.
Auto-self
This is an example of a syntax that is intended to reduce boilerplate code when initializing a class instance. The code transformation is more complex than the previous ones and include a change of indentation of an entire block of code.
Fractional math (token)
This is a functionally equivalent version to the AST proof of concept example [Fractional math (ast)] mentioned below. It demonstrates how to include supplementary code, such as importing a module or defining a function, in addition to the user code, while ensuring that the console (REPL) can still work properly.
Switch statement
Implementing a switch statement as described in the rejected PEP 3103. This example was done quite a few years ago, well before the match statement was added to Python.
Implicit multiplication
Python’s syntax does not allow to write a number followed by an non-keyword identifier or by a parenthesis, nor does it allow to write two non-keyword identifiers in a row. However, when writing equations on paper, these constructs are recognized as indicating a multiplication. This transformation does the same.
Abstract Syntax Tree transformations
Fractional math (AST)
This is a proof-of-concept of a transformation at the Abstract Syntax Tree level. It also shows how to include supplementary code, such as importing a module or defining a function, in addition to the user code while ensuring that the console (REPL) can still work properly.
Bytecode transformations
Confused math
This is a proof-of-concept demonstrating bytecode transformation.
Other types
True constants
This is a fairly complex example that illustrates the use of a custom module dict and class.
Custom encoding
Import hooks are not the only way one can transform a source; this can also be done by custom encodings.
λ encoding
This is an adaptation of our basic example, but using a custom encoding which needs to be explicitly declared in a file whose source must be transformed.


| (A) | ---- no text ---- | |
| 895 | (C) | And to alle þe comens þat þer were . these wordes a-lowde |
| 879 | (D) | To ałł þe wightis þat þer were wordis on hye |
| 856 | (E) | to al þe folk þat þer was . þese wurdes alowde . |
| (Ex) | ---- no text ---- | |
| 911 | (L) | To alle þe wyes þat þer were wordes aloude |
| 829 | (P) | Tiłł ałł þe wyes þat þar war wordes on loude |
| 865 | (U) | To ałł the wyse there were / wordes aloude |
| (V) | ---- no text ---- |


{% extends "base.html" %} {% load comments_tags %} {% load staticfiles %} {% load crispy_forms_tags %} {% load markdown_tags %} {% block head_title %} {% if post.blog.is_public %} {{ post.title }} -- {{ post.blog.title }} {% else %} No blog found {% endif %} {% endblock %} {% block content %} {% if not post.blog.is_public %}
This user doesn't want anyone to read his blog (strange, isn't it).
Only logged in users can comment on blog posts. Click here to Login or Signup today if you don't have an account yet.
{% endif %}{{ comment.comment }}
No comments.
{% endfor %}


|
Helix
|
#include <SchedConn.h>
Public Member Functions | |
| SchedConn (const twine &msgTarget, xmlDocPtr msg) | |
| virtual | ~SchedConn () |
| Standard Destructor. More... | |
| virtual twine | MsgTarget () |
| virtual xmlDocPtr | GetMsg () |
| virtual xmlNodePtr | GetRequestRoot (void) |
| virtual void | SendReturn () |
| virtual void | SendReturn (unsigned char *data, int dataLen, twine fileName, Date lastModified, Date expires) |
| virtual void | SendReturn (twine &filePath, twine &fileName, Date lastModified, Date expires) |
| virtual void | SendError () |
| virtual void | SendNotFound () |
| Public Member Functions inherited from Helix::Glob::IOConn | |
| IOConn () | |
| Standard constructor. More... | |
| virtual | ~IOConn () |
| virtual void | overrideMsgTarget (const twine newTarget) |
| virtual twine | getSessionID () |
| virtual void | setSessionID (const twine newSession) |
| OdbcObj * | getDBConnection (void) |
| SessionInfo & | getSessionInfo (void) |
| twine | getDBName (void) |
| virtual xmlDocPtr | initializeResponseDocument (const char *rootName) |
| virtual xmlDocPtr | initializeResponseDocument (xmlDocPtr resp) |
| virtual xmlNodePtr | getResponseRoot (void) |
| virtual void | setResponseFiltered (bool tf) |
| virtual void | addResponseError (twine msg, AnException *e) |
| virtual void | addResponseMessage (twine msg) |
| void | ReleaseDB (void) |
| virtual void | finishResponse (void) |
| virtual void | Close (void) |
| virtual bool | hasResponded (void) |
| void | lrTaskID (const twine &taskID) |
| const twine & | lrTaskID () |
| void | updateLRTask (intptr_t start, intptr_t current, intptr_t finish, const twine &msg) |
Protected Member Functions | |
| SchedConn (const SchedConn &c) | |
| Copy constructor is private to prevent use: More... | |
| SchedConn & | operator= (const SchedConn &c) |
| Copy operator is private to prevent use: More... | |
| Protected Member Functions inherited from Helix::Glob::IOConn | |
| void | checkSessionID (void) |
| bool | allowedWOSession (void) |
Protected Attributes | |
| xmlDocPtr | m_doc |
| The message that we read from the soap connection. More... | |
| bool | m_doc_loaded |
| twine | m_sessionid |
| bool | m_sessionid_loaded |
| twine | m_msg_target |
| Protected Attributes inherited from Helix::Glob::IOConn | |
| xmlDocPtr | m_resp_doc |
| Our response document. More... | |
| OdbcObj * | m_db |
| Our Database Connection, if any. More... | |
| Mutex * | m_db_mutex |
| Our DB Connection mutex, if any. More... | |
| twine | m_override_target |
| If we need to overrid the user's selected URL, this is where the overrid is stored. More... | |
| bool | m_has_responded |
| twine | m_lr_taskid |
| We'll have one of these if we are created as a long running task: More... | |
Additional Inherited Members | |
| Static Public Member Functions inherited from Helix::Glob::IOConn | |
| static twine | genSessionID () |
| static void | parseConnName (twine &connName, twine &Host, twine &Port, twine &User) |
This class defines the internal/scheduler version of the IOConn object.
|
inlineprotected |
Copy constructor is private to prevent use:
| SchedConn::SchedConn | ( | const twine & | msgTarget, |
| xmlDocPtr | msg | ||
| ) |
Default constructor
|
virtual |
Standard Destructor.
|
virtual |
When GetMsg is called, the IOConn object is responsible for presenting the contents of the inbound message to the caller as an XML document. This allows the processing mechanisms to be standardized to XML and not have to worry about the specifics of the communications protocol.
Implements Helix::Glob::IOConn.
|
virtual |
This returns the root element of the input Request message.
Implements Helix::Glob::IOConn.
|
virtual |
This allows the processing logic to query the connection to find out what message target should be used to process it.
Implements Helix::Glob::IOConn.
Copy operator is private to prevent use:
|
virtual |
SendError is used by the processing logic to send an error return response back to the original caller. The IOConn object is responsible for knowing how to do this, and if no response is actually necessary, IOConn is responsible for silently eating the message at this point.
Implements Helix::Glob::IOConn.
|
virtual |
If the requested msg target does not exist, use this to send back an appropriate "not found" message.
Implements Helix::Glob::IOConn.
|
virtual |
SendReturn is used by the processing logic to send the return response back to the original caller. The IOConn object is responsible for knowing how to do this, and if no response is actually necessary, IOConn is responsible for silently eating the message at this point.
Implements Helix::Glob::IOConn.
|
virtual |
This version of SendReturn is used to send back binary data that is not an XML document to the caller. This is used for serving static HTML pages, e.g.
Implements Helix::Glob::IOConn.
|
virtual |
This version of SendReturn is used to send back binary data for files that are too large to read in all at once and send back.
Implements Helix::Glob::IOConn.
|
protected |
The message that we read from the soap connection.
|
protected |
|
protected |
|
protected |
|
protected |


Episode 028
Multiple service instances tweaks
ASP.NET Core: From 0 to overkill
In the previous episodes
- We containerized all the components that make up the PlayBall application as a whole
- Used Docker Compose to easily get everything running and ready to test
In this episode
- Make some tweaks to allow for multiple instances of the services to run
- Learn about ASP.NET Core's data protection APIs
- How do they impact what we've done so far
- Why has everything been working well until now
- How can we improve it
- Quick adjustment to IdentityServer4's development signing credential setup
The usual plugs...
- If these videos are being useful
- Like
- Share
- Leave feedback
- More stuff at:


Becomes this:
A block of text:
<marked>
#Markdown directive
*It works!*
</marked>
Bind the markdown input to a scope variable:
<div marked="my_markdown">
</div>
<!-- Uses $scope.my_markdown -->
Include a markdown file:
<div marked ng-include="'README.md'">
</div>
<!-- Uses markdown content from README.md -->


It took us a bit to find our bearings here at Grow the Richmond as we've been adjusting to life under shelter in place. But we're getting the swing of things here. I know for my part, I've been thankful while looking for ways I can continue to stay plugged into my community. That's why I've been volunteering with Together SF, delivering groceries once a week to an elderly neighbor in the Richmond.
However, one of the aspects that's also emerged that I've noticed is that we are not quite as bound by geography so we can bring presenters to events that we might not have imagined or attend events that may have been out of our normal location. YIMBY Action has put together a number of cool events recently highlighting just that.
Without further ado, here's some great events coming up and other ways you can stay engaged with your friends and neighbors in this unprecidented time


- Product Manager of Super Break website and new greenfield project
- Maintain, develop and deliver the product roadmap
- Manage and implement change portfolio across the website from projects to BAU
- Manage and prioritise issue backlog based on customer and business needs
- Liaise with senior leadership and management on various IT projects to establish
needs and priorities
- Detail product requirements and aid the Business Analysis team when defining
detailed requirements
- Coordinate project teams from discovery to implementation
- Manage A/B Tests, User Research and customer feedback and act on any learnings
- Coordinate research and analysis on projects
- Lead workshops/working groups
- Manage resource against product priorities
- Manage product development and change throughout the SDLC
- Establish and grow