| Overview | Module | Use | Devguide | Index |
| Nested Modules | Services | Singletons | Interfaces | Structs | Exceptions | Enums | Typedefs | Constant Groups |
| module status |
| Structs | |
| ClipboardFormats | contains a list of format ID's and names which are part of the system clipboard. |
| FontHeight | describes the characteristics of a font. |
| ItemStatus | describes a state of a property. |
| LeftRightMargin | specifies a left and right margin. |
| Template | contains an association between a style name and a value. |
| UpperLowerMargin | specifies an upper and lower margin. |
| UpperLowerMarginScale | specifies an upper and lower margin. |
| Verb | describes a command that can be send to an OLE object |
| Visibility | describes the visibility state of a property. |
| Constant Groups | |
| ItemState | these constants describe a state of a ItemStatus. |
Copyright © 2013, The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache, the Apache feather logo, Apache OpenOffice and OpenOffice.org are trademarks of The Apache Software Foundation. Other names may be trademarks of their respective owners.


When you are writing documentation for software, a top priority is surely that what you write is correct. That is, the examples you provide give the output you say they will. Or perhaps it is that the links in your documentation link to an expected page. Usually this is done with manual testing at the time of writing. Your organisation may have practices in place to make sure that these examples don't get too out of date - maybe someone checks them periodically, maybe code review comes with comments like "I remember that this part of the code is used in an example on Page 37 of our docs, change it". But these methods are tedious and flawed. This talk will give examples from my work as a software engineer in creating tested snippets for documentation which are linked to the code they represent. It will show how using techniques traditionally reserved for software testing can ease the burden of keeping documentation up to date.
Modern geoscientific research relies heavily on numerical computations involving complex software developed by physicists or chemists. It would seem that scientists should be well versed in ways of documenting and explaining their research. Yet, when it comes to the documentation of scientific software projects, one soon realises that scientific wisdom is spread mostly by LaTex and that the word 'documentation' starts to mean something completely different.
Writing a documentation for a scientific project can be quite challenging. There are not that many examples of well-documented open-source geoscientific numerical modelling software projects to drew the inspiration from. Even though the scientific results should be reproducible, mechanisms that reward those who deliver well documented software are still to become widespread. The scientists are judged basing on the number of peer-reviewed papers they publish, therefore investing the time solely to offer the documentation is difficult. The documentation should include the actual mathematical equations and theory behind the software, figures documenting the scientific results as well as code listings and usage examples. The target audience may have a strong background in science, computer science, both or neither.
I'm a PhD student at the Faculty of Physics working in a research group developing two C++ libraries aimed at the atmospheric community. In this presentation I'd like to talk about our quest to link the scientific credit with the software documentation. I'd like to talk about how we tried to combine explaining scientific ideas in LaTex with explaining API along with automatic code listings in one journal-structured documentation and how we managed to publish both the code and the documentation in public, peer-reviewed Geoscientific Model Development journal.
Good documentation is important, but it should be your last resort. You need to help users before they reach the docs - in the user interface itself.
In this talk, I'll discuss:
strategies for writing microcopy when you’re short on space
what to explain in the UI, and what to save for the documentation
how to pick the right style of embedded help
what makes a great error message (and a terrible one)
... with plenty of real-world examples of doing it right and wrong.
Whilst not a part of the core documentation of projects, presentations and delivering them to the public are an essential part of spreading the word about what you do.
They need to be as equally consistent with your messaging and style guides, get to a key point effectively and also allow the presenter to inject some personality.
This is especially hard with technical projects where the 'story' is either hard to explain or can't just end up sounding like a sales pitch.
In this presentation I will explore and explain my experiences as an advocate for several open source projects, audience reactions to those presentations and how I have iterated my presentations in sync with changes to product and branding.
Documentation may not have a reputation as a creative enterprise, but we know that filling the role of documentarian requires creative problem solving - especially in figuring how to create, display, and maintain a reliable collection of docs.
If your goal is clear - we need (better) docs - then creativity comes in discovering how to get there. But creative problem solving has an important role to play in determining whether you've got the right goal: are docs the answer?
This talk starts with framing the common types of needs that docs can meet: informing, learning, referencing, persuading, and engaging. With examples for each, we'll see how creative thinking - mixed with data and some knowledge of human behavior - can shape problem statements that lead to better solutions, which aren't always the traditional doc. It's about making sure that we, as documentarians, aren't just writing - we're shaping the discussion about when and how docs make our teams, organizations, and communities better.
As a writer, it's been tough for me to admit that not everyone wants to read my carefully written documentation. While people will read, not everyone learns by reading the docs. Since my goal is to make sure my documentation can meet as many learning styles as possible, that has meant spreading my documentarian wings and bridging out from only writing the docs into recording them as well.
Part of my documentation journey has been learning how to create screencasts and I want to share that knowledge with everyone. From picking the right topics, to outlining, to writing a script (yes I promise, there is still writing involved), to how to record your audio and video, I'll cover it all. You don't need to be a professional voice actor or videographer to create a screencast, even a writer can create something wonderful.
Nobody loves email. Nobody really even likes email.  Despite how we feel about it, we have to deal with email almost every single day. Fortunately we can improve email as a whole by learning how to write email that sucks just a little bit less -- not that you write bad emails.. this talk is for your... friend. Yeah, this talk is for your friends that really need to setup up their email game.
In addition to email this talk will explore some fundamental misunderstandings that people have with modes of online communication and how to correct these misunderstandings. Like how to craft a good Tweet, Facebook Post, and Instant Messaging interaction.
This is not meant to be a tutorial but rather a conceptual guide for how to think about on-line communication and how to correct some common faults we share as members of the on-line community. The Internet isn't going away anytime soon, and the amount we communicate over it is not going to diminish anytime soon either. This talk attempts to teach one how to make digital communication as painless as possible.
An everyday dilemma in technical communication: What do you call that “thing”? Whether you ask developers, marketing folks or users, you often get very different views.
Along with user interfaces, documentation helps all stakeholders align their mental model of a product. Terminology plays a key role, and a controlled vocabulary is an ace up the technical writer's sleeve.
Controlled vocabularies are basically lists of concepts and the relationships between them. Beyond consistent naming, they are about structuring, categorizing and retrieving content. For example, you can use a vocabulary as a basis for documentation plans, tables of content, a help site's navigation, search filters, or even to organize test cases.
In this talk, I will share ways to create and maintain various types of vocabularies, and explain what each type is useful for. You can start with a flat list of terms and expand it into a glossary, a thesaurus, a taxonomy, or even a full-fledge ontology.
With about 1000 different editors each month, the Mozilla Developer Network (MDN) documentation Web site for Open Web technologies is a trafficked wiki with edits of all kind of quality: perfect text from seasoned professional writers to rough notes by teen-aged technology learners.
In this talk, we are going to explore how to keep this doc garden clean, how the diversity of editors influence its evolution, and how we find our way through treacherous jungles to well-maintained royal gardens.
This is about improving quality, working with diverse communities, fostering innovation, and carnivorous plants.
APIs define contracts between a service and a client, and with the rise of representation languages like Swagger, Apiary, and RAML, these contracts can be consumed programmatically and adapted easily into our codebases. Other tools like JSON Schema also contribute to this idea of integration between service and client.
But what about our documentation? If API contracts can be assimilated into software, surely it can drive our documentation too? In this talk, I want to introduce some of the techniques I've used on past projects that allow exactly that. By using remote schemas to generate software, it also allows us to generate working documentation that is always relevant and never out of date. Apart from accuracy, we also get the added benefits of reduced development time, reduced effort, and reduced duplication. We can all of this by documenting once, and re-using across multiple projects!
This talk shows how documentarians can find inspiration in the past, build on it, and move forward. It tells some of these stories, and shows what they meant in historical context:
As documentarians, we face plenty of hurdles to delivering what we are assigned (harried and inaccessible subject matter experts, barely functioning builds, sketchy doc infrastructure, etc.). But there are also the obstacles that keep us from writing the docs we want, and those are largely ingrained in our companies' processes and our own heads.
We pay lip service to "the user" but then subordinate that to concerns of structure, consistency, and stylistic conventions. The result is often docs that are internally consistent and satisfy the editorial, translation, and production teams for their economy and re-usability but are so dry and product-centered that they fail to connect with the most important audience - actual human beings.
In this presentation, I'll talk about ways to overcome burdensome organizational processes and our own timidity to create room for the inspiration and creativity needed to bring the docs' subject alive.Community Management in Free Software communities is still an emerging field and has produced a spectrum of practitioners: from master-manipulators of social media, to those more focused on metrics and data as a means to driving process. Either way, the state of the art is still largely driven by the needs of technical contributors to projects.
Good documentation is a crucial component in a software product and yet often technical writers are overlooked as important stakeholders of the process. Within the community, there are undoubtedly common problems between engineers and technical writers. Software Engineering is full of laws; can we show that these laws apply to technical writers as a means to help bridge the chasm between developers and technical writers??
In this talk Paul walks us through a selection of his favourite laws of software engineering and explores how developers measure them and if technical writers must also obey them. Or not. And what that means for the success of documentation in a Free Software project.
"So, your project needs better docs. For that, you'd need lots of people. Professionalism. A well-thought out plan. All the tools. And a whopping budget in both time and money.
Instead, you're sitting there, with just a few paperclips, seven moldy Mentos mints, a strip of Duct tape, a pencil and some nail polish remover...
Oh, hang on! There's also the combined experiences of generations of people fighting seemingly insurmountable odds. From environmental activists to LGBTQ people taking to the streets, we can draw on a rich history of inspired individuals taking whatever is at hand, mixed with some clever zaniness to quite fabulous effect.
So, what if we apply an activist mindset and some DIY hacking into our process? What lessons can we learn from a world where TOC means Theory Of Change, where working on a shoestring budget is the norm and where empowering people to go beyond what they think they can do is considered mission-critical?
To be clear: the aim here is not to knock professionalism in docs, quite the contrary! Yet, faced with a lack of resources, 'bend the rules and get going' sure beats lethargy. Not to mention being fun...
(And before you think I'll be bringing back the dreaded mullet: the next MacGyver will be a woman, according to http://thenextmacgyver.com)"
Presenting a business case for quality documentation can sometimes be a difficult enough task. Adding to that the accessibility requirements, and the whole idea may resemble a mission impossible. The fact that official standards (WCAG and WAI-ARIA) themselves seem to require user manuals in order to be properly implemented, is not helping developers, technical communicators and content managers achieve the desired results. This talk will present the main points and a selection of tools to get through the labyrinth of WCAG techniques and guidelines, and help you make your techcomm project accessibility-ready. Welcome to A11y for Tech Docs!
Do you feel like a fraud? Do you have that sneaking fear of being “found out” and exposed? Imposter syndrome is corrosive. It holds us back at work - especially in an industry where we can feel constantly under review by talented peers - and erodes our happiness. And the subject always comes up whenever technical writers gather; sometimes it feels like the very definition of a technical writer is “One who experiences imposter syndrome.”
Why is this? The first, shorter part of this talk will cover some research and insights into why we, as documentarians, may be especially susceptible to imposter syndrome.
But the field of tech writing is experiencing a swerve: a tipping point - a sea change in direction. There will always be a demand for ""old"" tech writing, but many of us will have to adapt to this new environment.
In the second, forward-looking part of this talk, I’ll argue that being an “imposter” has its advantages during such a time of change. The very factors that contribute to our self-doubt are actually the qualities that will enable us to thrive as our role inexorably evolves to take on new, unsolved challenges in engineering information. The keys to our success: apophenia (the ability to see connections between seemingly random collections of information), empathy, and adaptability.
Our future is bright if we pay attention to our new opportunities instead of that nagging voice in our heads.
A picture says more than …how many lines of code?
Firstly this talk offers an introduction to a variety of established as well as experimental visual documentation methods. Subsequently, it explores the question whether or not these approaches can be applied to software documentation in a reasonable way.
In this regard it takes a closer look at individual methods and estimates their corresponding affordances in terms of time, skill, resources and potential automatization. Eventually, this talk presents an initial attempt to translate existing docs into visual languages and discusses the according outcomes.
Primarily, the objective of reading and writing the docs serves the purpose to convey clear, unambiguous information, at the same time, the experience should be as engaging and pleasant as possible. Building a Visual Documentation Language serves to reach this goal.
Most of the documentation we read today puts a lot of burden on us before we have the chance to get to the gist. Abstract and clear concepts are replaced by concrete and comprehensive ones. The real values are hindered by opaque clouds of facts about tools of trade. As a result, thinking and imagination are suppressed.
But what if we can write documentation that encourages thinking?
Let's look together on what really matters when documenting computer systems. We will discuss how a documentation and system design can walk hand in hand and to improve the communication between both humans and machines.


Lucy Rose Jaine, 29, says she is against intensive factory-farmed food and hunts animals like wild pigs, deer, boars and wallabies to ensure what they eat is “organic and sustainable.”
“I hate factory farming so hunting wild meat is ideal,” she says. “It’s free, it’s fun and it helps the farmers.”
She frequently posts scantily-clad Instagram photos holding dead wild animals to show off her lifestyle, but many online critics call her carcass-carrying trophy pictures “sick,” “horrible” and “psychotic.”
“Sad excuse for a human,” one commenter writes. “Hope someday she will be the one being killed and that would be a good kill,” writes another.

“I’ve had a few death threats from people who just don’t have any experience with hunting,” she says. “Or maybe they are against animal cruelty.”
Jaine claims she ensures to “respect the animal in the process,” noting that many local farmers encourage her to hunt to help with their “pig problem.”
“The animals are living a good life,” she adds.
While she has plenty of supporters on Instagram, some questioned her ethics.  “I didn’t realize you were an omnipotent being that had the right to decide whether another animal lived or died?”
The Wanaka resident says she and her partner, Sharn, often take their three children along hunting about five to eight times a month for food, family bonding time and because the wilderness “really sparks their imaginations.”
“I like that we can teach our children how to hunt their own food,” she says of her brood, which range in age from five months to 7 years old. “The kids love the adventure.”
Jaine says they gut, skin and clean the animals before cutting them up and freezing the parts, adding that she saves about $192 a month (300NZD) by hunting animals for meat.


{{define "title"}}IP-Org Buyback - Appraisal Result {{.Page.Appraisal.ID}} [{{.Page.Appraisal.Kind}}]{{end}} {{define "content"}}
{{if .Page.Status}}You deleted your contract. Please try again if you wish.
{{end}}To submit this Buyback Offer, you will need to create a contract with these in the following way:
{{ .Page.Appraisal.BuybackWarning }}
CHECK CONTRACT NOW NOTE: CCP only updates contract data every 5 minutes. Please wait 5 minutes after creating your contract. Sorry, mate!
{{else if eq .Page.Status.Summary "accepted"}}Your contract was found in {{ .Page.Status.Contract.LocationName }}.
{{else}} {{if eq .Page.Status.Summary "valid"}}Your contract was found in {{ .Page.Status.Contract.LocationName }}.
The IP-Org leadership have been notified and your contract should be accepted soon.
{{else}}Your contract was found in {{ .Page.Status.Contract.LocationName }}.
However, it is {{.Page.Status.Summary}}
{{else}}This Buyback Offer is {{.Page.Status.Summary}}
{{end}}If you think that this is a mistake, please contact the IP-Org leadership.
RE-CHECK CONTRACT NOW NOTE: CCP only updates contract data every 5 minutes. Please wait 5 minutes after creating your contract. Sorry, mate!
{{end}} {{end}}{{.Page.Appraisal.Kind}} priced in {{.Page.Appraisal.MarketName}} {{relativetime .Page.Appraisal.CreatedTime}}{{if (and (ne .Page.Appraisal.ID "") .Page.Appraisal.Private)}} (private){{end}}
| Qty | Item | Volume (m3) | Single (sell) Single (buy) |
Total (sell) Total (buy) |
ISK/m3 (sell) ISK/m3 (buy) |
|---|---|---|---|---|---|
| {{comma $item.Quantity}} | {{if (and $item.TypeName (lt $i 30))}} {{end}} {{$item.DisplayName}}{{if $item.Extra.BPC}} (Copy) Runs: {{$item.Extra.BPCRuns}}{{end}} {{if (ne $item.Efficiency 0.0)}}  {{if $item.Prices.Basis}} ({{ $item.Qualifier }} {{ $item.Efficiency | printf "%2.1f" }}% - BASIS: {{$item.Prices.Basis}}) {{else}} ({{ $item.Qualifier }} {{ $item.Efficiency | printf "%2.1f" }}%) {{end}} {{end}} | {{humanizeVolume $item.TypeVolume }} |
{{ if (not $item.Rejected) }}
{{commaf $item.Prices.Sell.Min}} {{commaf $item.Prices.Buy.Max}} {{ end }} |
{{ if (not $item.Rejected) }}
{{commaf $item.SellTotal}} {{commaf $item.BuyTotal}} {{ commaf $item.Buyback.Totals.Buy }} {{ else }} NO BUYBACK OFFER {{ end }} |
{{ if (not $item.Rejected) }}
{{commaf $item.SellISKVolume}} {{commaf $item.BuyISKVolume}} {{ end }} |
| There are too many results to show. Click here to see all {{.Page.Appraisal.Items | len }} results. Warning: The page might be slow. | |||||
| Total Volume: Total Jita Sell Value: Total Jita Buy Value: Total Buyback Value: Average Buyback Percentage: |
{{commaf .Page.Appraisal.Original.Totals.Volume}} {{commaf .Page.Appraisal.Original.Totals.Sell}} {{commaf .Page.Appraisal.Original.Totals.Buy}} {{commaf .Page.Appraisal.BuybackOffer}} {{.Page.Appraisal.AverageBuybackPercentage}}% |


Welcome to Our Angular Based Website
- You can add an Unique task, employee and Department. To do, you can click one of those options below.
- You can click on Dashboard to see which employees are working on which department, task assign to department and inolved employees
as well as department with involved employees.


This patient isn't currently on any medication.
There are no recommended medications for this patient.


A stereotype threat according to Claude M. Steele, is a "socially premised psychological threat that arises when one is in a situation or doing something for which a negative stereotype about one's group applies." This is a concept that I have been grappling with for a while, subconsciously for most of my academic life, and I definitely think it has come into my mind more often since I have started Dev Bootcamp.
Being of Indian ethnicity has really affected the way that I perceived myself throughout high school, college, and even now. I think many people have the idea in their minds that Indians and Asians in general will inherently excel at hard sciences, math, and technical fields. This has been both a blessing and a curse for me throughout the years. I have never truly been the best in these technical fields, and from my perspective, at times feel like I am not living up to what "I should be good at". I know that this isn't true, but it is so deeply ingrained in our society that certain people should be good at certain things, that It makes me reconsider my accomplishments and goals in life.
One of the major things I have learned from college, and more recently, Dev Bootcamp, is that anyone can be good at anything. I never pictured myself getting this far in learning how to program, and although many people dont bat an eye when I tell them I'm picking up these technical skills, it has been thoroughly exciting for me. I want to believe that the majority of people dont have these stereotypes and images of what I should be doing in their minds, but it's definitely hard to avoid. Focusing on my individual goals and skills has allowed me to pick up these new technical skills regardless of my business background, and it has been fun to see it working out.
I think this concept of the stereotype threat is a problem in our current society, but my subconscious approach to overcoming it has been to ignore the noise, and keep pursuing what I want to do. This mindset has definitely paid dividends for me in recent months, and the less I think about what others think of me, the better I feel about it all. Moving forward, I want to make sure I keep those societal stereotypes out of my mind when interacting with others and perceiving my own actions. Dev Bootcamp has been an awesome experience for me so far because it has allowed me to interact with so many people from different academic and cultural backgrounds who I know are working through similar struggles. I think when it comes down to it, the "Stereotype Threat" is really only a threat if an individual perceives it that way.
Thanks for reading,
Vineet Rastogi


(a) This part identifies acquisition flexibilities that are available for emergency acquisitions. These flexibilities are specific techniques or procedures that may be used to streamline the standard acquisition process. This part includes—
(1) Generally available flexibilities; and
(2) Emergency acquisition flexibilities that are available only under prescribed circumstances.
(b) The acquisition flexibilities in this part are not exempt from the requirements and limitations set forth in FAR Part 3, Improper Business Practices and Personal Conflicts of Interest.
(c) Additional flexibilities may be authorized in an executive agency supplement to the FAR.
“Emergency acquisition flexibilities”, as used in this part, means flexibilities provided with respect to any acquisition of supplies or services by or for an executive agency that, as determined by the head of an executive agency, may be used—
(a) In support of a contingency operation as defined in 2.101;
(b) To facilitate the defense against or recovery from nuclear, biological, chemical, or radiological attack against the United States; or
(c) When the President issues an emergency declaration, or a major disaster declaration.
The FAR includes many acquisition flexibilities that are available to the contracting officer when certain conditions are met. These acquisition flexibilities do not require an emergency declaration or designation of contingency operation.
Contractors are not required to be registered in the System for Award Management (SAM) database for contracts awarded to support unusual and compelling needs or emergency acquisitions. (See 4.1102). However, contractors are required to register with SAM in order to gain access to the Disaster Response Registry. Contracting officers shall consult the Disaster Response Registry via https://www.acquisition.gov to determine the availability of contractors for debris removal, distribution of supplies, reconstruction, and other disaster or emergency relief activities inside the United States and outlying areas. (See 26.205).
Contracting officers need not submit a synopsis notice when there is an unusual and compelling urgency and the Government would be seriously injured if the agency complied with the notice time periods. (See 5.202(a)(2).)
Agencies may limit the number of sources and full and open competition need not be provided for contracting actions involving urgent requirements. (See 6.302-2.)
Streamlined procedures and a broad range of goods and services may be available under Federal Supply Schedule contracts (see subpart 8.4), multi-agency BPAs (see 8.405-3(a)(6)), or multi-agency, indefinite-delivery contracts (see 16.505(a)(8)). These contracting methods may offer agency advance planning, pre-negotiated line items, and special terms and conditions that permit rapid response.
Purchase from FPI is not mandatory and a waiver is not required if public exigency requires immediate delivery or performance (see 8.605(b)).
Contracting officers are not held to the notification required when changes in AbilityOne specifications or descriptions are required to meet emergency needs. (See 8.712(d).)
Agencies may determine not to enforce qualification requirements when an emergency exists. (See 9.206-1.)
The Defense Priorities and Allocations System (DPAS) supports approved national defense, emergency preparedness, and energy programs and was established to facilitate rapid industrial mobilization in case of a national emergency. (See subpart 11.6.)
For purchases not exceeding the simplified acquisition threshold, contracting officers may solicit from one source under certain circumstances. (See 13.106-1(b).)
Oral requests for proposals are authorized under certain conditions. (See 15.203(f).)
Letter contracts may be used when contract performance must begin immediately. (See 16.603.)
Interagency acquisitions are authorized under certain conditions. (See subpart 17.5.)
Contracts may be awarded to the Small Business Administration (SBA) for performance by eligible 8(a) firms on either a sole source or competitive basis. (See subpart 19.8.)
Contracts may be awarded to Historically Underutilized Business Zone (HUBZone) small business concerns on a sole source basis. (See 19.1306.)
Contracts may be awarded to Service-disabled Veteran-owned Small Business (SDVOSB) concerns on a sole source basis. (See 19.1406.)
Contracts may be awarded to economically disadvantaged women-owned small business (EDWOSB) concerns and women-owned small business (WOSB) concerns eligible under the WOSB Program on a competitive or sole source basis. (See subpart 19.15.)
Overtime approvals may be retroactive if justified by emergency circumstances. (See 22.103-4(i).)
The policies and procedures of FAR 25.4 may not apply to acquisitions not awarded under full and open competition (see 25.401(a)(5)).
Requirement to obtain authorization prior to use of patented technology may be waived in circumstances of extreme urgency or national emergency. (See 27.204-1.)
The chief of the contracting office may waive the requirement to obtain a bid guarantee for emergency acquisitions when a performance bond or a performance bond and payment bond is required. (See 28.101-1(c).)
Agencies may authorize advance payments to facilitate the national defense for actions taken under Public Law 85-804 (see subpart 50.1, Extraordinary Contractual Actions). These advance payments may be made at or after award of sealed bid contracts, as well as negotiated contracts. (See 32.405.)
The use of the no-setoff provision may be appropriate to facilitate the national defense in the event of a national emergency or natural disaster. (See 32.803(d).)
Electronic funds transfer payments may be waived for acquisitions to support unusual and compelling needs or emergency acquisitions. (See 32.1103(e).)
When urgent and compelling circumstances exist, agency protest override procedures allow the head of the contracting activity to determine that the contracting process may continue after GAO has received a protest. (See 33.104(b) and (c).)
Rental requirements do not apply to items of Government production and research property that are part of a general program approved by the Federal Emergency Management Agency and meet certain criteria. (See 45.301.)
subpart 50.1 prescribes policies and procedures for entering into, amending, or modifying contracts in order to facilitate the national defense under the extraordinary emergency authority granted by Public Law 85-804 (50 U.S.C. 1431-1434). This includes—
(a) Amending contracts without consideration (see 50.103-2(a));
(b) Correcting or mitigating mistakes in a contract (see 50.103-2(b)); and
(c) Formalizing informal commitments (See 50.103-2(c)).


This example show how we can delete data.
See below for all available options.
Note: The data is not deleted from server
Description
This method uses colModel and editurl parameters from jqGrid
Calling:
jQuery("#grid_id").jqGrid('delGridRow', row_id_s,options );
row_id_s is the row to delete. When in multiselect automatially delete the selected rows options top : 0 the initial top position of edit dialog left: 0 the initinal left position of edit dialog
If the left and top positions are not set the dialog apper on
upper left corner of the grid width: 0, the width of edit dialog - default 300 height: 0, the height of edit dialog default 200 modal: false, determine if the dialog should be in modal mode default is false drag: true,determine if the dialog is dragable default true msg: "Delete selected row(s),message to display when deleting the row caption: "Delete Record",the caption of the dialog bSubmit: "Submit", the text of the button when you click to data default Submit bCancel: "Cancel",the text of the button when you click to close dialog default Cancel url: , url where to post data. If set replace the editurl reloadAfterSubmit : true reloads grid data after posting default is true
// Events beforeShowForm: null fires before showing the form data.
Paramter passed to the event is the id of the constructed form. afterShowForm: null fires after the form is shown.
Paramter passed to the event is the id of the constructed form. beforeSubmit: null fires before the data is submitted to the server
Paramter is of type id=value1,value2,... When called the event can return array
where the first parameter can be true or false and the second is the message of the error if any
Example: [false,"The value is not valid"] afterSubmit: null fires after the data is posted to the server. Typical this
event is used to recieve status form server if the data is posted with success.
Parameters to this event are the returned data from the request and array of the
posted values of type id=value1,value2


Shopp-E
Log
Dashboard
Pages
Shop
Product Details
Cart
Checkout
Comparator
Login/SignUp
Welcome,
Retailer
Dashboard
Close Menu
Product Summary
Add Products
Change Password
Delete Account
My Dashboard
Sell Products
Add Product
×
Enter Name
Description
Price
Category
Brand
Quantity
Discount
Image
Upload
Add Products
display details of retailer (Amit Shukla)


--- layout: post status: publish published: true title: 1 lb of Ground Beef for $1.99 - Episode 8.56 author: display_name: Corey Fineran login: Corey email<EMAIL_ADDRESS>url: '' author_login: Corey author_email<EMAIL_ADDRESS>wordpress_id: 12053 wordpress_url: http://ivyenvy.com/?p=12053 date: '2016-09-21 22:36:52 +0000' date_gmt: '2016-09-22 03:36:52 +0000' categories: - Podcast tags: [] comments: [] ---
This episode of the podcast was recorded in front of a live audience at the Market Grille in the Hy-Vee on John Deere Road in Moline. This was our first live recording like this in 6 or 7 years and we had a lot of fun doing it.
In the episode, we talk about playoff home field advantage, potential match-ups for the NLDS, and what would happen if there was a 3-way tie for the NL Wild Card? Well, one thing we know...advantage Cubs.
We answer several listener questions and share a handful of internet muscle flexes.


---
layout: post
title: 1 Samuel 12:19-25
date: '2007-03-29T20:01:00.000-05:00'
author: Jabell
tags:
- 1 Samuel
- Sermon
modified_time: '2007-03-29T20:20:34.356-05:00'
thumbnail: http://bp0.blogger.com/_p0aKmLIk4oY/Rgxl0s54PcI/AAAAAAAAAAU/QIgDf_swNFQ/s72-c/IMG_6302_2.JPG
blogger_id: tag:blogger.com,1999:blog-19739956.post-7676540159658666228
blogger_orig_url: http://theabellsix.blogspot.com/2007/03/1-samuel-1219-25.html
---
I preached my second of two sermons for preaching class on February 25, 2007. The assignment was to preach on any Old Testament text.
Right click here and choose "Save Link As" to download an mp3 of the sermon.
Any feedback would be welcome.


---
layout: default
title: Learn Ruby on Rails as You Modify a Craigslist Clone
link: http://www.thinkful.com/learn/ruby-on-rails-tutorial/
categories: [ruby]
level: [beginner]
instruction: [online]
price: [free]
image: ruby-on-rails-craiglist-clone.png
---
In this interactive tutorial you're going to learn Ruby and Ruby on Rails fundamentals by modifying a Craigslist clone. You can view the source code on GitHub where you'll find a sample app to follow along. This guide was written by Aidan Feldman.


{% for key, profit in pnl.items %}
for Player {{key}} : {{profit}} in money units
{% endfor %}
Group Freight: {{F}} in distance units
Minimal Possible Freight: {{Fopt}}
Deals & Orders:
{% include 'selfre_GetOrders/chart.html' %}
Credits
This game got supported by
FABBS - Federal Association in Behavioural and Brain Science, Washington/USA
UCSC Economics - University Santa Cruz
The Game Model and Software is originally described in
"oTree - An open-source platform for laboratory, online, and field experiments."
Journal of Behavioral and Experimental Finance, vol 9: 88-97, 2016 (Chen, Daniel L., Martin Schonger, and Chris Wickens)
"Model for selfregulating, spacially extended market place for commodity trading", MPRA Preprint Server, 79482, 2017 (Michaelis, B.)


--- layout: stats title: Paul Litvak Statistics permalink: "/stats/players/paul-litvak.html" ---
| Year | Team | Finish | G | 10 | -5 | Pts | PPG |
|---|---|---|---|---|---|---|---|
| 2006 | Carnegie Mellon | 14 | 12 | 86 | 22 | 750 | 62.5 |
| Year | Round | Player | Team | Opponent | Result | 10 | -5 | Pts | Packet |
|---|---|---|---|---|---|---|---|---|---|
| 2006 | 1 (Prelims) | Paul Litvak | Carnegie Mellon | Illinois A | Loss | 8 | 2 | 70 | Texas A+M |
| 2006 | 3 (Prelims) | Paul Litvak | Carnegie Mellon | Athens State B | Win | 10 | 2 | 90 | Brown |
| 2006 | 4 (Prelims) | Paul Litvak | Carnegie Mellon | Chicago B | Loss | 7 | 2 | 60 | Rutgers |
| 2006 | 5 (Prelims) | Paul Litvak | Carnegie Mellon | Virginia A | Loss | 4 | 3 | 25 | Torch in my Moon Pie |
| 2006 | 6 (Prelims) | Paul Litvak | Carnegie Mellon | Illinois-Chicago | Win | 9 | 1 | 85 | VCU |
| 2006 | 7 (Prelims) | Paul Litvak | Carnegie Mellon | Princeton | Loss | 5 | 2 | 40 | Maryland + Williams |
| 2006 | 8 (Playoffs) | Paul Litvak | Carnegie Mellon | VCU A | Loss | 8 | 1 | 75 | Illinois |
| 2006 | 9 (Playoffs) | Paul Litvak | Carnegie Mellon | Williams | Loss | 8 | 1 | 75 | Princeton |
| 2006 | 10 (Playoffs) | Paul Litvak | Carnegie Mellon | Texas | Loss | 6 | 2 | 50 | Michigan |
| 2006 | 11 (Playoffs) | Paul Litvak | Carnegie Mellon | Virginia A | Loss | 7 | 2 | 60 | Chicago A |
| 2006 | 12 (Playoffs) | Paul Litvak | Carnegie Mellon | The Matt Lafer Experience (exhibition) | Loss | 7 | 1 | 65 | Editors 1 |
| 2006 | 14 (Playoffs) | Paul Litvak | Carnegie Mellon | Rutgers | Loss | 7 | 3 | 55 | Editors 3 |


Money Play. How should Red play 53?
pips Red=127 White=100
(CorrectAnswer= 0/0, ErrorScore= 0)
On initial evaluation XG much prefers hitting on the ace-point with the 5 but the rollout has 17/12, 7/4 virtually dead-heating with 7/4, 6/1*.
After 7/4, 6/1* Red won’t be hitting the other White blot with a 1 because that is needed for 24/23.
The question is whether Red can burrow out of White’s board or, if left to his own devices, will White self-destruct? After 17/12, 7/4 both players have roughly the same amount of spare pips to play with before their boards begin to destruct but Red has two checkers trapped that are not at the edge of the prime while White has one checker at the edge of Red’s prime.
White is a 70-30 favourite in the position. The hitting plays both wins and loses more gammons.
Over the board this is a very difficult position and even analysing after the event it is not a lot easier. I played 17/12, 7/4 which according to XG is a 0.01 error – I can live with that!
After 7/4, 6/1* Red won’t be hitting the other White blot with a 1 because that is needed for 24/23.
The question is whether Red can burrow out of White’s board or, if left to his own devices, will White self-destruct? After 17/12, 7/4 both players have roughly the same amount of spare pips to play with before their boards begin to destruct but Red has two checkers trapped that are not at the edge of the prime while White has one checker at the edge of Red’s prime.
White is a 70-30 favourite in the position. The hitting plays both wins and loses more gammons.
Over the board this is a very difficult position and even analysing after the event it is not a lot easier. I played 17/12, 7/4 which according to XG is a 0.01 error – I can live with that!
1. Cubeful 2-ply 7/4 6/1* Eq.: -0.405 0.332 0.093 0.003 - 0.668 0.250 0.028 2. Cubeful 2-ply 17/12 7/4 Eq.: -0.428 (-0.023) 0.302 0.042 0.001 - 0.698 0.167 0.012 3. Cubeful 2-ply 6/1* 4/1 Eq.: -0.579 (-0.173) 0.248 0.069 0.001 - 0.752 0.212 0.019 4. Cubeful 0-ply 13/8 7/4 Eq.: -0.475 (-0.069) 0.293 0.049 0.001 - 0.707 0.193 0.018 5. Cubeful 0-ply 13/8 4/1* Eq.: -0.711 (-0.306) 0.242 0.055 0.001 - 0.758 0.294 0.039


Rails <IP_ADDRESS> (June 26, 2023)
- No changes.
Rails <IP_ADDRESS> (March 13, 2023)
- No changes.
Rails <IP_ADDRESS> (January 24, 2023)
- No changes.
Rails <IP_ADDRESS> (January 17, 2023)
- No changes.
Rails 6.1.7 (September 09, 2022)
Respect Active Record's primary_key_type in Active Storage migrations. Backported from 7.0.
fatkodima
Rails <IP_ADDRESS> (July 12, 2022)
- No changes.
Rails 6.1.6 (May 09, 2022)
- No changes.
Rails <IP_ADDRESS> (April 26, 2022)
- No changes.
Rails 6.1.5 (March 09, 2022)
Attachments can be deleted after their association is no longer defined.
Fixes #42514
Don Sisco
Rails <IP_ADDRESS> (March 08, 2022)
Added image transformation validation via configurable allow-list.
Variant now offers a configurable allow-list for transformation methods in addition to a configurable deny-list for arguments.
[CVE-2022-21831]
Rails <IP_ADDRESS> (February 11, 2022)
- No changes.
Rails <IP_ADDRESS> (February 11, 2022)
- No changes.
Rails <IP_ADDRESS> (December 15, 2021)
- No changes.
Rails <IP_ADDRESS> (December 14, 2021)
- No changes.
Rails <IP_ADDRESS> (December 14, 2021)
- No changes.
Rails <IP_ADDRESS> (August 19, 2021)
- No changes.
Rails 6.1.4 (June 24, 2021)
The parameters sent to
ffmpeg
for generating a video preview image are now configurable underconfig.active_storage.video_preview_arguments
.Brendon Muir
Fix Active Storage update task when running in an engine.
Justin Malčić
Don't raise an error if the mime type is not recognized.
Fixes #41777.
Alex Ghiculescu
::ActiveStorage::PreviewError
is raised when a previewer is unable to generate a preview image.Alex Robbin
respond with 404 given invalid variation key when asking for representations.
George Claghorn
Blob
creation shouldn't crash if no service selected.Alex Ghiculescu
Rails <IP_ADDRESS> (May 05, 2021)
- No changes.
Rails <IP_ADDRESS> (March 26, 2021)
- Marcel is upgraded to version 1.0.0 to avoid a dependency on GPL-licensed mime types data.
George Claghorn
Rails 6.1.3 (February 17, 2021)
- No changes.
Rails <IP_ADDRESS> (February 10, 2021)
- No changes.
Rails 6.1.2 (February 09, 2021)
- No changes.
Rails 6.1.1 (January 07, 2021)
Fix S3 multipart uploads when threshold is larger than file.
Matt Muller
Rails 6.1.0 (December 09, 2020)
Change default queue name of the analysis (
:active_storage_analysis
) and purge (:active_storage_purge
) jobs to be the job adapter's default (:default
).Rafael Mendonça França
Implement
strict_loading
onActiveStorage
associations.David Angulo
Remove deprecated support to pass
:combine_options
operations toActiveStorage::Transformers::ImageProcessing
.Rafael Mendonça França
Remove deprecated
ActiveStorage::Transformers::MiniMagickTransformer
.Rafael Mendonça França
Remove deprecated
config.active_storage.queue
.Rafael Mendonça França
Remove deprecated
ActiveStorage::Downloading
.Rafael Mendonça França
Add per-environment configuration support
Pietro Moro
The Poppler PDF previewer renders a preview image using the original document's crop box rather than its media box, hiding print margins. This matches the behavior of the MuPDF previewer.
Vincent Robert
Touch parent model when an attachment is purged.
Víctor Pérez Rodríguez
Files can now be served by proxying them from the underlying storage service instead of redirecting to a signed service URL. Use the
rails_storage_proxy_path
and_url
helpers to proxy an attached file:<%= image_tag<EMAIL_ADDRESS>%>
To proxy by default, set
config.active_storage.resolve_model_to_route
:# Proxy attached files instead. config.active_storage.resolve_model_to_route = :rails_storage_proxy
<%= image_tag @user.avatar %>
To redirect to a signed service URL when the default file serving strategy is set to proxying, use the
rails_storage_redirect_path
and_url
helpers:<%= image_tag<EMAIL_ADDRESS>%>
Jonathan Fleckenstein
Add
config.active_storage.web_image_content_types
to allow applications to add content types (likeimage/webp
) in which variants can be processed, instead of letting those images be converted to the fallback PNG format.Jeroen van Haperen
Add support for creating variants of
WebP
images out of the box.Dino Maric
Only enqueue analysis jobs for blobs with non-null analyzer classes.
Gannon McGibbon
Previews are created on the same service as the original blob.
Peter Zhu
Remove unused
disposition
andcontent_type
query parameters forDiskService
.Peter Zhu
Use
DiskController
for both public and private files.DiskController
is able to handle multiple services by adding aservice_name
field in the generated URL inDiskService
.Peter Zhu
Variants are tracked in the database to avoid existence checks in the storage service.
George Claghorn
Deprecate
service_url
methods in favour ofurl
.Deprecate
Variant#service_url
andPreview#service_url
to instead use#url
method to be consistent withBlob
.Peter Zhu
Permanent URLs for public storage blobs.
Services can be configured in
config/storage.yml
with a new keypublic: true | false
to indicate whether a service holds public blobs or private blobs. Public services will always return a permanent URL.Deprecates
Blob#service_url
in favor ofBlob#url
.Peter Zhu
Make services aware of configuration names.
Gannon McGibbon
The
Content-Type
header is set on image variants when they're uploaded to third-party storage services.Kyle Ribordy
Allow storage services to be configured per attachment.
class User < ActiveRecord::Base has_one_attached :avatar, service: :s3 end class Gallery < ActiveRecord::Base has_many_attached :photos, service: :s3 end
Dmitry Tsepelev
You can optionally provide a custom blob key when attaching a new file:
user.avatar.attach key: "avatars/#{user.id}.jpg", io: io, content_type: "image/jpeg", filename: "avatar.jpg"
Active Storage will store the blob's data on the configured service at the provided key.
George Claghorn
Replace
Blob.create_after_upload!
withBlob.create_and_upload!
and deprecate the former.create_after_upload!
has been removed since it could lead to data corruption by uploading to a key on the storage service which happened to be already taken. Creating the record would then correctly raise a database uniqueness exception but the stored object would already have overwritten another.create_and_upload!
swaps the order of operations so that the key gets reserved up-front or the uniqueness error gets raised, before the upload to a key takes place.Julik Tarkhanov
Set content disposition in direct upload using
filename
anddisposition
parameters to ActiveStorage::Service#headers_for_direct_upload.Peter Zhu
Allow record to be optionally passed to blob finders to make sharding easier.
Gannon McGibbon
Switch from
azure-storage
gem toazure-storage-blob
gem for Azure service.Peter Zhu
Add
config.active_storage.draw_routes
to disable Active Storage routes.Gannon McGibbon
Image analysis is skipped if ImageMagick returns an error.
ActiveStorage::Analyzer::ImageAnalyzer#metadata would previously raise a
MiniMagick::Error
, which caused persistentActiveStorage::AnalyzeJob
failures. It now logs the error and returns{}
, resulting in no metadata being added to the offending image blob.George Claghorn
Method
calls on singular attachments returnnil
when no file is attached.Previously, assuming the following User model,
user.avatar.filename
would raise a::Module::DelegationError
if no avatar was attached:class User < ApplicationRecord has_one_attached :avatar end
They now return
nil
.Matthew Tanous
The mirror service supports direct uploads.
New files are directly uploaded to the primary service. When a directly-uploaded file is attached to a record, a background job is enqueued to copy it to each secondary service.
Configure the queue used to process mirroring jobs by setting
config.active_storage.queues.mirror
. The default is:active_storage_mirror
.George Claghorn
The S3 service now permits uploading files larger than 5 gigabytes.
When uploading a file greater than 100 megabytes in size, the service transparently switches to multipart uploads using a part size computed from the file's total size and S3's part count limit.
No application changes are necessary to take advantage of this feature. You can customize the default 100 MB multipart upload threshold in your S3 service's configuration:
production: service: s3 access_key_id: <%= Rails.application.credentials.dig(:aws, :access_key_id) %> secret_access_key: <%= Rails.application.credentials.dig(:aws, :secret_access_key) %> region: us-east-1 bucket: my-bucket upload: multipart_threshold: <%= 250.megabytes %>
George Claghorn
Please check [6-0-stable]) for previous changes.


Mushrooms - P. cubensis (extract)
Well it turns out that i have found a way to obtain a chemical mass of concentrated psilocybin. It took an beginner level of chemical knowledge to do it, and i dont suppose even a person disinterested in chemistry would have trouble doing it.
It all started about 6 months ago. i bought 14 grams of psilocybin cubensis from my friend who grew them in his own house, and it was his notion that i make some Shroom Tea. I have never made shroom tea before so later that night i carefully weighed out 3.5 grams of these bone-dry mushrooms. i do know as scientific fact that:
1 parts of psilocybin is soluable in 20 part water.
[Erowid Note: This is true if the water is boiling.] 1 gram of psilocybin cubensis contains about 10 mg psilocybin (thats not to say psilocin and baecytosin are not apart of this, its just that it would be too complicated if i used them as apart of my variables).
[Erowid Note: 1% psilocybin content is higher than what is usually reported for dried P. cubensis. The range is quite variable. It would be much safer to say that 1 gram of P. cubensis usually has a psilocybin content of 1 mg to 10 mg.]
Well i wanted to take percaution with my work, so i finely chopped the mushrooms up with my fancy vegetable chopper. Hey Man, this thing worked so well that the mushrooms were basically as fine as coffee grounds. I heated 8 0z. of water to about 90 degrese celcius (very close to boiling) and plopped the mushroom grounds in. After a few minutes i noticed that the water got a light brown tint. I figured heat would help the dissolving of the psilocybin so i put the mushroom/H2O solution in a coffee cup with a lid to reduce heat loss.
After about 30 minutes the brown tint got a little more darker, and i thought about straining the mushroom and drinking this liquid, but i didnt. i just let it sit on the counter until the water got cold, and i passed out.
The next morning i took the cup and strained out the mushrooms throught a coffee filter. After soaking in water for about 10 hours i was pretty sure the psilocybin was completly dissolved. Ok, psilocybin that comes from straight from the mushrooms is not attached to an acid, so i added 2 teaspoons of muratic acid, and 2 teaspoons of pure naptha to the solution (by this point i had no intentions of drinking the tea, but to extract the psilocybin). I shook up the solution violently for about 10 minutes, and decided to pour it into a mason jar with one of those Oxygen absorbing packets you find in beef jerkey packages taped to the underside of the lid, because psilocybin oxidizes easily, and to reduce bacteria growth. i let this sit for like an hour before i decided to abandon this idea. so i just simply used an eye dropper to suck all the napthat off the top layer. i poured the napthat out onto some wax paper and let it evaporate.
The substance left was this greasy, dark yellow mass of film. When i scraped it all up and rolled it into a ball it was about the size of a pea. I had no hesitations to consume it right then and there. I didnt even wash it down, i chewed it so i could remember what it would taste like. Hmm...yes indeed, it actually had no taste which suprised me. I took it on an empty stomach in the afternoon with a cup of orange juice. HAHAHA and in about 15 minutes i felt the first effects of psilocybin. Remember now that i used 3.5 grams. I peaked at about the half hour mark. The effect was probably equivalent to 2.5 or 3 grams. not 3.5, i expected to lose some psilocybin somehow, if i were to repeat the naptha extraction perhaps i would have gotten a little more. but at that time I was aestheticly satisfied, and for the whole 5 hours i was on the drug, i couldn't help by get revelations that this is going to change the history of mushroom use. i doubt it though.
i LOVE the chemistry, but i also enjoy the fruits of my labor ,)
i think the reason there are no psilocybin extrations out there is because nobody has thought about it! if it is done with dmt it can be done with psilocybin/psilocin etc... blah blah blah!
But indeed my product wasn't pure, it was still exciting breakthrough. since then i have done this extraction simply to impress some psychonauts, and i have tried smoking it..it doesnt burn or vaporize, at least at normal BIC lighter temperatures.
peace Erowid, and viewers.
sincerely,
well...you can just call me master sergent.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Last Experience
City Hall - Caxias do Sul, RS - Brazil
🖥 IT Technician - 2013 - Current
- SysAdmin: Docker, Vmware, Linux, Windows
- Data Integration: Python, PostgreSQL, LDAP, Samba-AD
- Network Services: Postfix, Zimbra, DNS, DHCP, RADIUS
- Routers/Switches: VLANs, MAC Authentication, STP
- Security/Recovery: Fortigate, HP Data Protector
- Monitoring Tools: Grafana, Observium, Zabbix
- User Support and Docs: WikiJS, Sphinx, Git
Education
Uniftec - Caxias do Sul, RS - Brazil
🎓 Technology in Computer Networks - 2006 - 2010


This inspection verifies that FlexUnit 4 test method returns void. Non-void methods cannot be run by FlexUnit 4 runner.


Home
About
Projects
Blog
Lydia's Blog
Git
11/17/2015
Hashes and Arrays in Ruby
1/4/2016
Cycle, an Enumerable method
1/11/2016
Using Ruby classes
1/18/2016
No SQL Databases
2/1/2016


Documentation Contents
Java Platform, Standard Edition HotSpot Virtual Machine Garbage Collection Tuning Guide
Next
Contents
Title and Copyright Information
Preface
Audience
Documentation Accessibility
Related Documents
Conventions
1
Introduction
2
Ergonomics
Garbage Collector, Heap, and Runtime Compiler Default Selections
Behavior-Based Tuning
Maximum Pause Time Goal
Throughput Goal
Footprint Goal
Tuning Strategy
3
Generations
Performance Considerations
Measurement
4
Sizing the Generations
Total Heap
The Young Generation
Survivor Space Sizing
5
Available Collectors
Selecting a Collector
6
The Parallel Collector
Generations
Parallel Collector Ergonomics
Priority of Goals
Generation Size Adjustments
Default Heap Size
Client JVM Default Initial and Maximum Heap Sizes
Server JVM Default Initial and Maximum Heap Sizes
Specifying Initial and Maximum Heap Sizes
Excessive GC Time and OutOfMemoryError
Measurements
7
The Mostly Concurrent Collectors
Overhead of Concurrency
Additional References
8
Concurrent Mark Sweep (CMS) Collector
Concurrent Mode Failure
Excessive GC Time and OutOfMemoryError
Floating Garbage
Pauses
Concurrent Phases
Starting a Concurrent Collection Cycle
Scheduling Pauses
Incremental Mode
Command-Line Options
Recommended Options
Basic Troubleshooting
Measurements
9
Garbage-First Garbage Collector
Allocation (Evacuation) Failure
Floating Garbage
Pauses
Card Tables and Concurrent Phases
Starting a Concurrent Collection Cycle
Pause Time Goal
10
Garbage-First Garbage Collector Tuning
Garbage Collection Phases
Young Garbage Collections
Mixed Garbage Collections
Phases of the Marking Cycle
Important Defaults
How to Unlock Experimental VM Flags
Recommendations
Overflow and Exhausted Log Messages
Humongous Objects and Humongous Allocations
11
Other Considerations
Finalization and Weak, Soft, and Phantom References
Explicit Garbage Collection
Soft References
Class Metadata
Next


Check out The Lounge
, which is an actively maintained fork of Shout.
Shout
Documentation
GitHub
{{ content }}


Manager of configuration in Video Window.
More...
#include <ConfigManager.h>
Manager of configuration in Video Window.
- Author
- Bastien LEGOY
- Version
- 1.0.0
- Date
- Date
- 2020/05/15
Manager in configuration to modify main JSON file.
◆ ConfigManager()
| ConfigManager::ConfigManager |
( |
| ) |
|
Default constructor.
Instantiate propreties and read JSON file data.
◆ ~ConfigManager()
| ConfigManager::~ConfigManager |
( |
| ) |
|
Default deconstructor.
Close and save JSON file and its new data.
◆ addConfig
| void ConfigManager::addConfig |
( |
QString |
device, |
|
|
QString |
name, |
|
|
QString |
path, |
|
|
QString |
surename |
|
) |
| |
|
slot |
Add and define new config to a specific device.
- Parameters
-
| device | Name of the default device |
| name | Name of the new config |
| path | Path of the new config |
| surename | Surename of the new config for specified device |
Create a new configuration, attributes it to the specified device and save it all in root object.
◆ addDevice
| void ConfigManager::addDevice |
( |
QString |
device | ) |
|
|
slot |
Add new device to root object.
- Parameters
-
Add new device in root object with specified device name.
◆ getConfigs()
| QStringList ConfigManager::getConfigs |
( |
| ) |
|
Get all existing configs.
- Returns
- List of all configs resulting from the search
Get all configurations store and declared in root object.
◆ getConfigs_fromDevice()
| QStringList ConfigManager::getConfigs_fromDevice |
( |
const QString & |
deviceID | ) |
|
Get all configs from specified device.
- Parameters
-
| deviceID | Device alias created from a specific device name |
- Returns
- List of all configs resulting from the search
Get configurations from a specific device alias in root object, not file data.
◆ getDefaultDevice()
| QString ConfigManager::getDefaultDevice |
( |
| ) |
|
Get default device name.
- Returns
- Result of the search
Look for and return the default device from stored data.
◆ getName_fromConfigSurename()
| QString ConfigManager::getName_fromConfigSurename |
( |
const QString & |
surename, |
|
|
const QString & |
device |
|
) |
| |
Get config name from its surename.
- Parameters
-
| surename | Specific config surename |
| device | Device the surename is issued from |
- Returns
- Name result from the search
Get name for a specific configuration surename on a specific device.
◆ getPath_fromConfigName()
| QString ConfigManager::getPath_fromConfigName |
( |
const QString & |
name | ) |
|
Get config path from its name.
- Parameters
-
- Returns
- Path of the specific config
Get path from a specific configuration name on any device.
◆ getPath_fromConfigSurename()
| QString ConfigManager::getPath_fromConfigSurename |
( |
const QString & |
surename, |
|
|
const QString & |
device |
|
) |
| |
Get config path from its surename.
- Parameters
-
| surename | Specific config surename |
| device | Device the surename is issued from |
- Returns
- Path of the specific config
Get path from a specific configuration surename on a specific device.
◆ isConfigPath_free()
| bool ConfigManager::isConfigPath_free |
( |
const QString & |
path | ) |
|
Verify if specified config path is free.
- Parameters
-
| path | Specified path to verify |
- Returns
- Result of the verification
Verify if a configuration is already using the specified path.
◆ isConfigSurename_free()
| bool ConfigManager::isConfigSurename_free |
( |
const QString & |
surename, |
|
|
const QString & |
device |
|
) |
| |
Verify if specified config surename is free on a specific device.
- Parameters
-
| surename | Specific config surename |
| device | Specific device name/alias |
- Returns
- Result of the verification
Verify if a configuration surename is already defined for a specific device.
◆ isDevice_saved()
| bool ConfigManager::isDevice_saved |
( |
const QString & |
device | ) |
|
Verify if specified device is already saved or not.
- Parameters
-
| device | Specific device name/alias |
- Returns
- Result of the verification
Verify if a device has already been saved in root object.
◆ read()
| void ConfigManager::read |
( |
| ) |
|
Read data from JSON file.
Read data and store it in root object.
◆ removeDefaultConfig
| void ConfigManager::removeDefaultConfig |
( |
| ) |
|
|
slot |
Remove default config.
Set default config to 'none' in root object.
◆ save
| void ConfigManager::save |
( |
| ) |
|
|
slot |
Save root object in JSON file.
Take data in root object to store it in JSON file.
◆ setConfig
| void ConfigManager::setConfig |
( |
QString |
device, |
|
|
QString |
name, |
|
|
QString |
surename |
|
) |
| |
|
slot |
Attach config to a specific device with a specific surename.
- Parameters
-
| device | Specified device name |
| name | Specified config name |
| surename | Specified config surename |
Attach a specific configuration to a specified device with a specific surename.
◆ setDefaultConfig
| void ConfigManager::setDefaultConfig |
( |
QString |
device, |
|
|
QString |
surename |
|
) |
| |
|
slot |
Change default config of a specific device.
- Parameters
-
| device | Specific device to change the default config of |
| surename | New default config |
Set the default configuration of a specific device from its surename.
◆ setDefaultDevice
| void ConfigManager::setDefaultDevice |
( |
QString |
device | ) |
|
|
slot |
Change default device of the application.
- Parameters
-
| device | New default device name |
Set the default device loaded on application construction.
◆ buffer
| QJsonDocument ConfigManager::buffer |
|
private |
Data buffer from main JSON file.
◆ file
| QFile ConfigManager::file |
|
private |
JSON file to get and post data.
◆ root
| QJsonObject ConfigManager::root |
|
private |
Root object containing all data to read from and update in through methods.
The documentation for this class was generated from the following files:
- C:/Users/legb/Documents/Git Projects/AutoYams/AutoYams/AutoYams/include/AutoYams/core/file/ConfigManager.h
- C:/Users/legb/Documents/Git Projects/AutoYams/AutoYams/AutoYams/src/ConfigManager.cpp


Active Record
Using Ruby on Rails to manage the DB
Sunday May 31, 2015
The M in MVC
Active record is the Rails mechanism responsible for representing data and logic. Active Record helps create and use objects whose data persists to a database.
Active Record as ORMActive record uses Object Relation Matching, meaning it takes properties of objects it is modeling, and matches it to tables, colomns, and records in a database. This means that we lowely developers write fewer queries, because Active record is able to use naming conventions to find the data.
Active Record uses some naming conventions to find out how to map models and database tables. Rails will pluralize (Hat to hats, or CarTire to car_tires) your class names to find the respective database table. It also converts camel-case to snake_case to go from class names to table names.