The HTTP response inherits from the header.
More...
#include <ResponseHTTP.hpp>
The HTTP response inherits from the header.
◆ Response() [1/3]
| oZ::oZ::HTTP::Response::Response |
( |
Code |
code = Code::Undefined , |
|
|
Reason && |
reason = Reason() , |
|
|
Body && |
body = Body() , |
|
|
Version |
version = DefaultVersion |
|
) |
| |
|
inline |
◆ Response() [2/3]
| oZ::oZ::HTTP::Response::Response |
( |
const Response & |
other | ) |
|
|
default |
Construct a new Response object by copy.
◆ Response() [3/3]
| oZ::oZ::HTTP::Response::Response |
( |
Response && |
other | ) |
|
|
default |
Construct a new Response object by move.
◆ ~Response()
| oZ::oZ::HTTP::Response::~Response |
( |
void |
| ) |
|
|
default |
◆ getBody() [1/2]
| Body& oZ::oZ::HTTP::Response::getBody |
( |
void |
| ) |
|
|
inlinenoexcept |
Get request's Body reference.
◆ getBody() [2/2]
| const Body& oZ::oZ::HTTP::Response::getBody |
( |
void |
| ) |
const |
|
inlinenoexcept |
Get request's Body constant reference.
◆ getCode()
| Code oZ::oZ::HTTP::Response::getCode |
( |
void |
| ) |
const |
|
inlinenoexcept |
◆ getHeader() [1/2]
| Header& oZ::oZ::HTTP::Response::getHeader |
( |
void |
| ) |
|
|
inlinenoexcept |
Get the response's header reference.
◆ getHeader() [2/2]
| const Header& oZ::oZ::HTTP::Response::getHeader |
( |
void |
| ) |
const |
|
inlinenoexcept |
Get the response's header constant reference.
◆ getReason() [1/2]
| Reason& oZ::oZ::HTTP::Response::getReason |
( |
void |
| ) |
|
|
inlinenoexcept |
Get request's Reason reference.
◆ getReason() [2/2]
| const Reason& oZ::oZ::HTTP::Response::getReason |
( |
void |
| ) |
const |
|
inlinenoexcept |
Get request's Reason constant reference.
◆ getVersion()
| Version oZ::oZ::HTTP::Response::getVersion |
( |
void |
| ) |
const |
|
inlinenoexcept |
◆ setCode()
| void oZ::oZ::HTTP::Response::setCode |
( |
Code |
code | ) |
|
|
inlinenoexcept |
◆ setVersion()
| void oZ::oZ::HTTP::Response::setVersion |
( |
Version |
version | ) |
|
|
inlinenoexcept |
The documentation for this class was generated from the following file:
- /home/mmoinvaziri/Epitech/CPP_zia_2019/External/openZia/openZia/ResponseHTTP.hpp


when connecting the XBee to Arduino Uno/
Xbee RX with Arduino TX
Xbee TX with arduino RX
Xbee GND with Arduino GND
The problem is the Xbee 3.3V with Arduino 3.3V or Arduino 5V. Thanks a lot
Archived Forum |
|
XBeeSubmitted by Guest on Sun, 10/06/2012 - 07:45when connecting the XBee to Arduino Uno/ Xbee RX with Arduino TX Xbee TX with arduino RX Xbee GND with Arduino GND
The problem is the Xbee 3.3V with Arduino 3.3V or Arduino 5V. Thanks a lot » |
Re: XBee
What are you trying to say? Your last two posts here have both presumed that we all know what is going through your brain. If you want to make a point, or if you want help, you need to explain better.
 Communication is an essential skill for an engineer of any discipline. You will not get far in engineering until you learn to communicate clearly and effectively.
Re: XBee
i did not understand what you mean as I always asked in order to understand perfectly even when I had small doubts. well Im running the arduino by using an AC-DC adapter.now I bought this Xbee http://www.adafruit.com/products/126 which states that 3.3V regulator on board. on forums I found that people had problems and that its better to add a voltage divider by using resistor or even a 3.3v voltage regulator chip in order to safeguard the xbee. when i was reading on this page, i found this:
'The wire link between the xbee and the arduino has 4 wires: 5V, GND, DATA1, DATA2.'
now I want to ask, the 5V maked on Xbee should it be connected to the 5V pin on the arduino or can I cannect it to 3.3v on the arduino?
I'm sorry if in some way or another I disobeyed the rules of this page
Re: XBee
No, you did not disobey any rules, you did not give me (or anyone else) enough information to know what your problem was. You have now given me almost all the information I need. If you had written this the first time, I could have answered you sooner.
You can run the Arduino at either 5 V or 3.3 V. If you are running the Aduino at 3.3 V, then you can feed the xbee with the same 3.3 V and you do not need the adapter kit. But you can use it if you wish. Look at this page http://www.ladyada.net/make/xbee/ about the Adapter Kit near the bottom and you see a picture with the connections marked. I read that as meaning you can feed 3.3 V on the pin marked "3 V from regulator (or input)".
If you are running the Aduino at 5 V, then look at the page again: you can EITHER feed 5 V on the pin marked "5 V - Power to regulator", OR you can feed 3.3 V on the pin marked "3 V from regulator (or input)". But you do need the Adapter Kit for the input signals. Under the picture it says "The DTR, RTS, RESET and RX pins (going into the XBee) pass through a level converter chip that brings the levels to 3.3V." That means you can safely put signals from the Arduino that switch between 0 and 5 V onto these pins.
To find out whether the output from the xbee can be recognised by the Arduino input, you need to look at Table 28.2 of the Atmel Data Sheet. That tells me that if the HIGH voltage (VIH - Input High Voltage, except XTAL1 and RESET pins) is greater than 0.7 V then it will be recognised (and the LOW voltage needs to fall below 0.3 V to be recognised - see the line above). It is almost certain that the xbee will output a voltage higher than 0.7 V for a logic HIGH (but you could check in the same way) with the xbee data sheet.


FACILITIES NEAR YOU
Local Bakery
There is an operating backery in the neighborhood. Also open for employment. Open from 9AM-11PM everyday of the week!
Mcdonalds
McDonalds is also operating and service customers. Not open for employment. Open 24/7!
Shopping Mall
Shopping Mall with 3 floors and approximately 80 shops. Open everyday of the week from 10AM- 1AM.
Park
Park opens at 9AM-1AM everyday of the week. There is a 1$ entry fee.
Primary School
A Primary school for children up until Grade 7. The school has numerous facilities including a tennis court, football field and olymic sized-pool. School is open on weekdays from 8AM-2PM
Gym
The Gym is only for people that are 18+. Gym opens from 10AM-2AM everyday of the week!


| No. | Address | Capacity | Battery | Last Maintained | Urgency | |
|---|---|---|---|---|---|---|
| 1 | 4000 Fourth Street | 75% | 50% | 19 April 2018 | (2) medium | Explore |
| 11 | 550 Huntington Ave | 100% | 25% | 19 April 2018 | (3) high | Explore |
| 20 | 44 Four Lane | 20% | 92% | 19 April 2018 | (1) low | Explore |
| 34 | 1000 Four Lane | 12% | 95% | 25 April 2018 | (1) low | Explore |
| 702 | 145 Yeven Drive | 20% | 78% | 25 April 2018 | (1) low | Explore |


Store
Static Method Summary
| Static Public Methods | ||
| public static |
Creates a field definition for an attribute. |
since 0.1.0 |
| public static |
Creates a field definition for an has-many relationship. |
since 0.1.0 |
| public static |
Creates a field definition for an has-one relationship. |
since 0.1.0 |
Constructor Summary
| Public Constructor | ||
| public |
constructor(adapter: *) |
Member Summary
| Public Members | ||
| public |
observable: Rx.Observable An observable that will emit events when any resource in added, updated |
since 0.6.0 |
Method Summary
| Public Methods | ||
| public |
Add an individual resource to the store. |
since 0.1.0 |
| public |
Converts the given partial into a JSON API compliant representation. |
since 0.5.0 |
| public |
Attempts to create the resource through the adapter and adds it to the |
since 0.5.0 |
| public |
Defines a type of resource. |
since 0.2.0 |
| public |
Attempts to delete the resource through the adapter and removes it from |
since 0.5.0 |
| public |
Finds a resource by type and id. |
since 0.1.0 |
| public |
Finds all the resources of a given type. |
since 0.7.0 |
| public |
Attempts to load the given resource through the adapter and adds it to the |
since 0.5.0 |
| public |
Attempts to load all the resources of the given type through the adapter |
since 0.7.0 |
| public |
this method was deprecated. Use the
store.observable property instead of this.Unregister an event listener that was registered with on(). |
since 0.4.0 |
| public |
this method was deprecated. Use the
store.observable property instead of this.Register an event listener: "added", "updated" or "removed". |
since 0.4.0 |
| public |
Add a JSON API response to the store. |
since 0.1.0 |
| public |
Remove a resource or collection of resources from the store. |
since 0.1.0 |
| public |
Attempts to update the resource through the adapter and updates it in the |
since 0.5.0 |
Static Public Methods
public static attr(name: string, options: Object): Object since 0.1.0 source
Creates a field definition for an attribute.
public static hasMany(name: string, options: Object): Object since 0.1.0 source
Creates a field definition for an has-many relationship.
Public Constructors
public constructor(adapter: *) source
Params:
| Name | Type | Attribute | Description |
| adapter | * |
Public Members
public observable: Rx.Observable since 0.6.0 source
An observable that will emit events when any resource in added, updated or removed. The object passed to listeners will be in this format:
{ name: string, type: string, id: string, resource: object }
You can learn more about RxJS observables at the GitHub repo: https://github.com/Reactive-Extensions/RxJS
Example:
let store = new Store();
store.observable.filter(e => e.name === "added").subscribe(event => {
console.log(event.name); // "added"
console.log(event.type); // "products"
console.log(event.id); // "1"
console.log(event.resource); // Map {...}
});
store.observable.filter(e => e.name === "updated").subscribe(event => {
console.log(event.name); // "updated"
console.log(event.type); // "products"
console.log(event.id); // "1"
console.log(event.resource); // Map {...}
});
store.observable.filter(e => e.name === "removed").subscribe(event => {
console.log(event.name); // "removed"
console.log(event.type); // "products"
console.log(event.id); // "1"
console.log(event.resource); // null
});
Public Methods
public add(object: Object) since 0.1.0 source
Add an individual resource to the store. This is used internally by the
push()
method.
Params:
| Name | Type | Attribute | Description |
| object | Object |
|
A JSON API Resource Object to be added. See: http://jsonapi.org/format/#document-resource-objects |
public convert(type: string, id: string, partial: object): object since 0.5.0 source
Converts the given partial into a JSON API compliant representation.
Params:
| Name | Type | Attribute | Description |
| type | string |
|
The type of the resource. This can be omitted if the partial includes a type property. |
| id | string |
|
The id of the resource. This can be omitted if the partial includes an id property. |
| partial | object |
|
The data to convert. |
public create(type: string, partial: Object, options: Object): Rx.Observable since 0.5.0 source
Attempts to create the resource through the adapter and adds it to the store if successful.
Return:
| Rx.Observable |
Example:
let adapter = new Store.AjaxAdapter();
let store = new Store(adpater);
store.create("product", { title: "A Book" }).subscribe((product) => {
console.log(product.title);
});
public define(names: string | string[], definition: Object) since 0.2.0 source
Defines a type of resource.
public destroy(type: string, id: string, options: Object): Rx.Observable since 0.5.0 source
Attempts to delete the resource through the adapter and removes it from the store if successful.
Return:
| Rx.Observable |
Example:
let adapter = new Store.AjaxAdapter();
let store = new Store(adpater);
store.destroy("product", "1").subscribe(() => {
console.log("Destroyed!");
});
public find(type: string, id: string): Object since 0.1.0 source
Finds a resource by type and id.
NOTE: If the resource hasn't been loaded via an add() or push() call it will be automatically created when find is called.
public findAll(type: string): Object[] since 0.7.0 source
Finds all the resources of a given type.
Params:
| Name | Type | Attribute | Description |
| type | string |
|
Type of the resource to find. |
public load(type: string, id: string, options: Object): Rx.Observable since 0.5.0 source
Attempts to load the given resource through the adapter and adds it to the store if successful.
Return:
| Rx.Observable |
Example:
let adapter = new Store.AjaxAdapter();
let store = new Store(adpater);
store.load("products", "1").subscribe((product) => {
console.log(product.title);
});
public loadAll(type: string, options: Object): Rx.Observable since 0.7.0 source
Attempts to load all the resources of the given type through the adapter and adds them to the store if successful.
Return:
| Rx.Observable |
Example:
let adapter = new Store.AjaxAdapter();
let store = new Store(adpater);
store.loadAll("products").subscribe((products) => {
console.log(products);
});
public off(event: string, type: string, id: string, callback: function) since 0.4.0 source
store.observable
property instead of this.Unregister an event listener that was registered with on().
public on(event: string, type: string, id: string, callback: function, context: Object) since 0.4.0 source
store.observable
property instead of this.Register an event listener: "added", "updated" or "removed".
public push(root: Object) since 0.1.0 source
Add a JSON API response to the store. This method can be used to handle a successful GET or POST response from the server.
Params:
| Name | Type | Attribute | Description |
| root | Object | Top Level Object to push. See: http://jsonapi.org/format/#document-top-level |
public remove(type: string, id: string) since 0.1.0 source
Remove a resource or collection of resources from the store.
public update(type: string, id: string, partial: Object, options: Object): Rx.Observable since 0.5.0 source
Attempts to update the resource through the adapter and updates it in the store if successful.
Return:
| Rx.Observable |
Example:
let adapter = new Store.AjaxAdapter();
let store = new Store(adpater);
store.update("product", "1", { title: "foo" }).subscribe((product) => {
console.log(product.title);
});


Designing the W5 Summit
- Collaborators: Meghan Lo | Li Hai Zheng
- Ongoing project
W5 strives to cultivate an inclusive entrepreneurial community, promoting the entrepreneurial mindset of hustle, passion and elasticity towards failure. Through the mentorship of the Accelerator, to open competition events such as the W5 Summit, W5 designs these initiatives to support budding entrepreneurs in any stage of their innovations as well as those interested in start up culture.
As a Director of Marketing on team, I am responsible for spearheading promotional content for W5 to improve event outreach. I also work collaboratively with the marketing team and the Vice-President of Marketing to build W5's brand image through promotional campaigns. W5 Summit in specific is W5's flagship event. It features a hackathon styled 3 hour case competition encouraging students to innovation a solution to address one of the areas of: waste management, social wealth imbalance or mental health.
Design materials
Countdown gif animations


@faithc @alexisantracoli These 389 containers have been imported to the Alma Sandbox. Please QA and let me know if they are ready to be imported to prod.
Thanks, @regineheberlein. Will look them over and let you know.
Amy, Phoebe, and I reviewed the records. The mostly look good to go, though we noticed the records don't have the call number associated with them. Would this data be added once they're in production? Thanks.
Can you add a screenshot of where you expected additional data?
@phoebeno How do these records compare to the ones for AC464?
I had checked another record, C1491, to confirm that call numbers were present:
These are coming from the physloc note, which the Ed Sanders ASpace record doesn't have. https://aspace.princeton.edu/staff/resources/4277#resource_notes_
Huh. Interesting that the call number comes from or is associated with the physloc note. I just added the note to the resource record. Thanks.
@regineheberlein I think the point is now moot, but the Griffin boxes did have the call number present in that column in Alma.
@faithc @phoebeno @amycvo Re-imported and ready for another round of QA please.
mentioned
by None at 2023-01-09 13:10:25.subscribed
by None at 2023-01-09 13:10:25.mentioned
by None at 2023-01-09 13:10:25.subscribed
by None at 2023-01-09 13:10:25.mentioned
by None at 2023-01-09 14:22:42.subscribed
by None at 2023-01-09 14:22:42.mentioned
by None at 2023-01-09 17:31:43.subscribed
by None at 2023-01-09 17:31:44.mentioned
by None at 2023-01-09 20:06:37.subscribed
by None at 2023-01-09 20:06:37.mentioned
by None at 2023-01-09 21:29:58.subscribed
by None at 2023-01-09 21:29:58.mentioned
by None at 2023-01-09 21:29:58.subscribed
by None at 2023-01-09 21:29:58.mentioned
by None at 2023-01-09 21:29:58.subscribed
by None at 2023-01-09 21:29:58.closed
by Kevin Reiss at 2023-01-09 16:23:03.@mzelesky closing this. Please re-open if you think it needs more discussion.
closed
by Kevin Reiss at 2023-01-09 16:25:14.mentioned
by None at 2023-01-09 16:25:15.subscribed
by None at 2023-01-09 16:25:15.assigned
by Kevin Reiss at 2023-01-09 16:26:39.Need is confirm with Marie WC and Joan that we should do this.
Write Liza to confirm their current practices.
assigned
by Kevin Reiss at 2023-01-09 16:39:07.deployed
by None at 2023-01-09 19:23:29.referenced
by Kevin Reiss at 2023-01-09 19:39:18.merged
by Kevin Reiss at 2023-01-09 19:39:19.closed
by Kevin Reiss at 2023-01-09 19:39:19.head_ref_deleted
by Kevin Reiss at 2023-01-09 19:39:19.labeled
by Max Kadel at 2023-01-09 18:30:11.assigned
by Jane Sandberg at 2023-01-09 18:36:07.closed
by Kevin Reiss at 2023-01-09 19:39:21.assigned
by None at 2023-01-09 21:06:00.emailed stakeholders 1/9.
unassigned
by Max Kadel at 2023-01-09 16:28:10.assigned
by Kevin Reiss at 2023-01-09 16:28:12.referenced
by Bess Sadler at 2023-01-09 22:56:06.merged
by Bess Sadler at 2023-01-09 22:56:06.closed
by Bess Sadler at 2023-01-09 22:56:06.head_ref_deleted
by Bess Sadler at 2023-01-09 22:56:07.referenced
by Bess Sadler at 2023-01-09 22:56:37.merged
by Bess Sadler at 2023-01-09 22:56:37.closed
by Bess Sadler at 2023-01-09 22:56:37.head_ref_deleted
by Bess Sadler at 2023-01-09 22:56:38.labeled
by None at 2023-01-09 22:56:41.referenced
by Bess Sadler at 2023-01-09 23:06:41.merged
by Bess Sadler at 2023-01-09 23:06:41.closed
by Bess Sadler at 2023-01-09 23:06:41.head_ref_deleted
by Bess Sadler at 2023-01-09 23:06:42.labeled
by None at 2023-01-09 22:56:42.referenced
by Bess Sadler at 2023-01-09 23:07:23.merged
by Bess Sadler at 2023-01-09 23:07:23.closed
by Bess Sadler at 2023-01-09 23:07:23.head_ref_deleted
by Bess Sadler at 2023-01-09 23:07:24.This is ready for review; happy to create a new issue/PR for later theming development if needed.
review_requested
by Kate Lynch at 2023-01-09 15:12:09.referenced
by Shaun Ellis at 2023-01-09 21:01:36.merged
by Shaun Ellis at 2023-01-09 21:01:36.closed
by Shaun Ellis at 2023-01-09 21:01:36.head_ref_deleted
by Shaun Ellis at 2023-01-09 21:01:36.Testing this currently blocked by #705
Until #702 has been tested, I am not quite certain of the format required by Digital Science. Hence, I am going to consider this blocked.
The certificates have been reformatted in the PFX format, and redistributed to the Digital Science team (as this was required by their server infrastructure).
labeled
by James R. Griffin III at 2023-01-09 14:18:45.closed
by James R. Griffin III at 2023-01-09 15:26:44.unlabeled
by James R. Griffin III at 2023-01-09 15:36:17.assigned
by James R. Griffin III at 2023-01-09 15:36:18.A SN@P ticket requesting firewall access has been submitted to lsupport
.
https://support.symplectic.co.uk/support/tickets/428442 is now tracking a number of questions regarding the availability of SMTP services provided by Digital Science.
assigned
by James R. Griffin III at 2023-01-09 16:18:26.assigned
by James R. Griffin III at 2023-01-09 21:27:26.labeled
by James R. Griffin III at 2023-01-09 21:27:35.referenced
by Bess Sadler at 2023-01-09 22:55:06.merged
by Bess Sadler at 2023-01-09 22:55:06.closed
by Bess Sadler at 2023-01-09 22:55:06.head_ref_deleted
by Bess Sadler at 2023-01-09 22:55:07.deployed
by None at 2023-01-09 16:18:27.referenced
by Eliot Jordan at 2023-01-09 17:10:34.merged
by Eliot Jordan at 2023-01-09 17:10:34.closed
by Eliot Jordan at 2023-01-09 17:10:34.head_ref_deleted
by Eliot Jordan at 2023-01-09 17:10:35.labeled
by None at 2023-01-09 17:13:19.labeled
by None at 2023-01-09 17:13:19.Closing and will reopen later.
closed
by Eliot Jordan at 2023-01-09 19:44:08.head_ref_deleted
by Eliot Jordan at 2023-01-09 19:50:02.ready_for_review
by Trey Pendragon at 2023-01-09 20:05:54.There's just #5429 left, so we'll leave that open and close this.
closed
by Trey Pendragon at 2023-01-09 20:08:32.https://docs.google.com/document/d/1r2ektkqUVkTlY2EW1Tl-UaM1J513s_2GaWqrDbHvnvs/edit# has information on our tiered rollout.
unassigned
by None at 2023-01-09 20:50:41.labeled
by Trey Pendragon at 2023-01-09 20:30:02.labeled
by Trey Pendragon at 2023-01-09 20:55:32.unlabeled
by Trey Pendragon at 2023-01-09 20:55:38.Reopening. Both steps are listed as part of the tiered implementation plan.
reopened
by None at 2023-01-09 21:41:56.renamed
by None at 2023-01-09 21:42:43.renamed
by None at 2023-01-09 21:27:13.labeled
by None at 2023-01-09 21:43:10.labeled
by None at 2023-01-09 21:43:10.head_ref_force_pushed
by Eliot Jordan at 2023-01-09 19:48:40.head_ref_force_pushed
by Eliot Jordan at 2023-01-09 21:18:42.head_ref_force_pushed
by Eliot Jordan at 2023-01-09 21:31:40.head_ref_force_pushed
by Eliot Jordan at 2023-01-09 21:36:25.head_ref_force_pushed
by Eliot Jordan at 2023-01-09 22:17:19.head_ref_force_pushed
by Eliot Jordan at 2023-01-09 22:34:32.head_ref_force_pushed
by Eliot Jordan at 2023-01-09 22:35:06.ready_for_review
by Eliot Jordan at 2023-01-09 22:35:14.closed
by Trey Pendragon at 2023-01-09 20:14:16.labeled
by None at 2023-01-08 22:49:31.labeled
by None at 2023-01-08 22:49:31.referenced
by Bess Sadler at 2023-01-09 22:13:07.merged
by Bess Sadler at 2023-01-09 22:13:07.closed
by Bess Sadler at 2023-01-09 22:13:07.head_ref_deleted
by Bess Sadler at 2023-01-09 22:13:08.referenced
by Bess Sadler at 2023-01-09 22:13:40.merged
by Bess Sadler at 2023-01-09 22:13:40.closed
by Bess Sadler at 2023-01-09 22:13:40.head_ref_deleted
by Bess Sadler at 2023-01-09 22:13:41.referenced
by Bess Sadler at 2023-01-09 22:50:10.merged
by Bess Sadler at 2023-01-09 22:50:10.closed
by Bess Sadler at 2023-01-09 22:50:10.head_ref_deleted
by Bess Sadler at 2023-01-09 22:50:11.referenced
by Bess Sadler at 2023-01-09 22:50:39.merged
by Bess Sadler at 2023-01-09 22:50:39.closed
by Bess Sadler at 2023-01-09 22:50:39.head_ref_deleted
by Bess Sadler at 2023-01-09 22:50:40.Looks like loofah is up-to-date now, so this is no longer needed.
closed
by None at 2023-01-09 22:50:53.head_ref_deleted
by None at 2023-01-09 22:50:54.Looks like nokogiri is up-to-date now, so this is no longer needed.
closed
by None at 2023-01-09 22:50:53.head_ref_deleted
by None at 2023-01-09 22:50:54.referenced
by Bess Sadler at 2023-01-09 22:51:21.merged
by Bess Sadler at 2023-01-09 22:51:21.closed
by Bess Sadler at 2023-01-09 22:51:21.head_ref_deleted
by Bess Sadler at 2023-01-09 22:51:22.referenced
by Bess Sadler at 2023-01-09 22:52:00.merged
by Bess Sadler at 2023-01-09 22:52:00.closed
by Bess Sadler at 2023-01-09 22:52:00.head_ref_deleted
by Bess Sadler at 2023-01-09 22:52:01.referenced
by Bess Sadler at 2023-01-09 22:52:30.merged
by Bess Sadler at 2023-01-09 22:52:30.closed
by Bess Sadler at 2023-01-09 22:52:30.head_ref_deleted
by Bess Sadler at 2023-01-09 22:52:31.@dependabot rebase
head_ref_force_pushed
by None at 2023-01-09 22:18:51.mentioned
by Dependabot at 2023-01-09 23:20:04.head_ref_force_pushed
by None at 2023-01-09 23:20:37.referenced
by Bess Sadler at 2023-01-09 23:28:29.merged
by Bess Sadler at 2023-01-09 23:28:29.closed
by Bess Sadler at 2023-01-09 23:28:29.head_ref_deleted
by Bess Sadler at 2023-01-09 23:28:30.@dependabot rebase
head_ref_force_pushed
by None at 2023-01-09 22:18:08.mentioned
by Dependabot at 2023-01-09 22:54:04.head_ref_force_pushed
by None at 2023-01-09 22:54:26.referenced
by Bess Sadler at 2023-01-09 23:29:06.merged
by Bess Sadler at 2023-01-09 23:29:06.closed
by Bess Sadler at 2023-01-09 23:29:06.head_ref_deleted
by Bess Sadler at 2023-01-09 23:29:07.assigned
by None at 2023-01-09 14:58:58.@christinach is there more than needs to be done here? Re-open if needed.
closed
by Kevin Reiss at 2023-01-09 16:09:38.mentioned
by Christina Chortaria at 2023-01-09 16:09:39.subscribed
by Christina Chortaria at 2023-01-09 16:09:39.convert_to_draft
by Jane Sandberg at 2023-01-09 16:17:36.renamed
by Kevin Reiss at 2023-01-09 16:31:01.@christinach we talked about this during ticket review and it would be good if we could do the review of the settings as a team when you are back.
mentioned
by Christina Chortaria at 2023-01-09 16:48:09.subscribed
by Christina Chortaria at 2023-01-09 16:48:09.unassigned
by None at 2023-01-09 14:57:52.assigned
by Kevin Reiss at 2023-01-09 21:59:43.Note that blacklight upstream has a pretty sophisticated skip navigation link. For example, if you tab through demo.projectblacklight.org/?searchfield=allfields&q=dog, you get:
Coverage: 94.313% (-0.2%) from 94.514% when pulling e254d509ad8ac03f64e7cea8b2cd2c7cc12252be on i3329askaquestionrebase into 07ce18d750a49c605ea225fb28f002d5d1136064 on main.
referenced
by Bess Sadler at 2023-01-09 14:47:18.merged
by Bess Sadler at 2023-01-09 14:47:18.closed
by Bess Sadler at 2023-01-09 14:47:19.head_ref_deleted
by Bess Sadler at 2023-01-09 14:47:19.ready_for_review
by Hector Correa at 2023-01-09 14:42:52.renamed
by Hector Correa at 2023-01-09 14:44:25.referenced
by Bess Sadler at 2023-01-09 14:59:09.merged
by Bess Sadler at 2023-01-09 14:59:09.closed
by Bess Sadler at 2023-01-09 14:59:09.head_ref_deleted
by Bess Sadler at 2023-01-09 14:59:10.head_ref_force_pushed
by None at 2023-01-09 14:53:04.referenced
by Bess Sadler at 2023-01-09 15:55:22.merged
by Bess Sadler at 2023-01-09 15:55:22.closed
by Bess Sadler at 2023-01-09 15:55:22.head_ref_deleted
by Bess Sadler at 2023-01-09 15:55:23.head_ref_force_pushed
by None at 2023-01-09 15:57:33.referenced
by Chuck McCallum at 2023-01-09 16:15:23.merged
by Chuck McCallum at 2023-01-09 16:15:24.closed
by Chuck McCallum at 2023-01-09 16:15:24.head_ref_deleted
by Chuck McCallum at 2023-01-09 16:15:25.referenced
by Bess Sadler at 2023-01-09 16:27:26.merged
by Bess Sadler at 2023-01-09 16:27:26.closed
by Bess Sadler at 2023-01-09 16:27:27.head_ref_deleted
by Bess Sadler at 2023-01-09 16:27:28.mentioned
by Chuck McCallum at 2023-01-09 19:10:24.subscribed
by Chuck McCallum at 2023-01-09 19:10:24.closed
by Hector Correa at 2023-01-09 19:44:21.head_ref_deleted
by Hector Correa at 2023-01-09 19:44:28.Thanks. I'll look into this, and add more testing!
I didn't look closer to see why it works for the datacite_resource_type
values, also defined in this class (https://github.com/pulibrary/pdc_describe/blob/main/app/models/pdc_serialization/datacite.rb#L105-L108) but the problem seems to be the symbol to string conversion.
@hectorcorrea -- Can you give me more information about how to reproduce? I've made a record with two contributors:
I then enter the rails console:
work = Work.find(8)
...
"contributors"=>
[{"type"=>"WorkPackageLeader",
"value"=>"asdf, asdf",
"sequence"=>0,
"name_type"=>"Personal",
"given_name"=>"asdf",
"identifier"=>nil,
"family_name"=>"asdf",
"affiliations"=>[]},
{"type"=>"Other",
"value"=>"sdfg, dfg",
"sequence"=>1,
"name_type"=>"Personal",
"given_name"=>"dfg",
"identifier"=>nil,
"family_name"=>"sdfg",
"affiliations"=>[]}],
...
puts work.to_xml
...
<contributors>
<contributor contributorType='WorkPackageLeader'>
<contributorName>asdf, asdf</contributorName>
</contributor>
<contributor contributorType='Other'>
<contributorName>sdfg, dfg</contributorName>
</contributor>
</contributors>
Perhaps it's a problem with older records? Or maybe there's something else you're doing that I'm missing?
This was a problem with my local version having an old cache of the JavaScript :( -- big thanks to @mccalluc for helping me troubleshoot it.
assigned
by Chuck McCallum at 2023-01-09 18:38:42.mentioned
by Hector Correa at 2023-01-09 18:53:46.subscribed
by Hector Correa at 2023-01-09 18:53:46.closed
by Hector Correa at 2023-01-09 19:43:55.mentioned
by Chuck McCallum at 2023-01-09 19:43:55.subscribed
by Chuck McCallum at 2023-01-09 19:43:55.Added this test to #836
closed
by None at 2023-01-09 20:35:25.With these PRs: - #790 - #824
I think this can be closed. If anything else is needed, feel free to file a new issue.
closed
by Chuck McCallum at 2023-01-09 20:58:57.@jrgriffiniii I think you and I may have come at this same functionality from two angles. Your PR #801 and this PR both send a notification when the state has changed to Approved. This one also adds one for Draft and Awaiting Approval.
How do you feel about this PR? I'd be happy to discuss how to combine them, or merge yours and then adapt mine. I do not have the Successfully Published method, so maybe both PRs are needed.
Thank you very much for this @carolyncole! My preference would be to please merge your PR, close my own PR, and then offer a second PR with a proposal for any changes which I felt my first PR still addressed (if there are any - this is really excellent and may well indeed cover the cases which mine sought to cover).
head_ref_force_pushed
by None at 2023-01-09 20:18:00.head_ref_force_pushed
by None at 2023-01-09 20:26:37.head_ref_force_pushed
by None at 2023-01-09 20:35:00.mentioned
by James R. Griffin III at 2023-01-09 20:42:21.subscribed
by James R. Griffin III at 2023-01-09 20:42:21.mentioned
by None at 2023-01-09 21:03:47.subscribed
by None at 2023-01-09 21:03:47.referenced
by James R. Griffin III at 2023-01-09 21:06:00.merged
by James R. Griffin III at 2023-01-09 21:06:00.closed
by James R. Griffin III at 2023-01-09 21:06:00.head_ref_deleted
by James R. Griffin III at 2023-01-09 21:06:01.This was deprecated by https://github.com/pulibrary/pdc_describe/pull/836
closed
by James R. Griffin III at 2023-01-09 21:06:39.referenced
by Bess Sadler at 2023-01-09 22:03:27.merged
by Bess Sadler at 2023-01-09 22:03:27.closed
by Bess Sadler at 2023-01-09 22:03:27.head_ref_deleted
by Bess Sadler at 2023-01-09 22:03:28.ready_for_review
by Tyler Wade at 2023-01-09 21:22:49.referenced
by Bess Sadler at 2023-01-09 22:12:08.merged
by Bess Sadler at 2023-01-09 22:12:08.closed
by Bess Sadler at 2023-01-09 22:12:08.head_ref_deleted
by Bess Sadler at 2023-01-09 22:12:09.(Not sure why the main merge caused problems, but looking into it...)
referenced
by Bess Sadler at 2023-01-09 23:11:14.merged
by Bess Sadler at 2023-01-09 23:11:14.closed
by Bess Sadler at 2023-01-09 23:11:15.head_ref_deleted
by Bess Sadler at 2023-01-09 23:11:15.closed
by Bess Sadler at 2023-01-09 23:11:16.head_ref_force_pushed
by Hector Correa at 2023-01-09 14:36:12.referenced
by Bess Sadler at 2023-01-09 17:52:11.merged
by Bess Sadler at 2023-01-09 17:52:11.closed
by Bess Sadler at 2023-01-09 17:52:11.head_ref_deleted
by Bess Sadler at 2023-01-09 17:52:12.referenced
by Bess Sadler at 2023-01-09 17:52:37.merged
by Bess Sadler at 2023-01-09 17:52:37.closed
by Bess Sadler at 2023-01-09 17:52:37.head_ref_deleted
by Bess Sadler at 2023-01-09 17:52:38.referenced
by Bess Sadler at 2023-01-09 17:53:00.merged
by Bess Sadler at 2023-01-09 17:53:00.closed
by Bess Sadler at 2023-01-09 17:53:00.head_ref_deleted
by Bess Sadler at 2023-01-09 17:53:01.referenced
by Kate Lynch at 2023-01-09 14:16:18.merged
by Kate Lynch at 2023-01-09 14:16:18.closed
by Kate Lynch at 2023-01-09 14:16:19.head_ref_deleted
by Kate Lynch at 2023-01-09 14:16:19.referenced
by Eliot Jordan at 2023-01-09 17:57:54.merged
by Eliot Jordan at 2023-01-09 17:57:54.closed
by Eliot Jordan at 2023-01-09 17:57:54.head_ref_deleted
by Eliot Jordan at 2023-01-09 17:57:55.assigned
by Shaun Ellis at 2023-01-09 15:28:39.referenced
by Shaun Ellis at 2023-01-09 17:35:56.closed
by Eliot Jordan at 2023-01-09 17:57:55.referenced
by Eliot Jordan at 2023-01-09 18:47:03.merged
by Eliot Jordan at 2023-01-09 18:47:03.closed
by Eliot Jordan at 2023-01-09 18:47:03.head_ref_deleted
by Eliot Jordan at 2023-01-09 18:47:04.I ran in dev and staging:
AspaceIndexJob.perform_later(resource_descriptions_uri: "/repositories/5/archival_objects/924592", repository_id: "mms")
and got the error:
``
NoMethodError: undefined method
text' for nil:NilClass
cache.ead_id = Nokogiri::XML.parse(content).remove_namespaces!.xpath("//eadid")[0].text
Linking the honeybadger issue: https://app.honeybadger.io/projects/65922/faults/92241057
Faith updated me that they removed these notes, but they do expect to add them later to other records, so they'll need to work.
@faithc We can't work this ticket without an example. We'll either have to block the ticket until there is one, or do you have one in production that we can use and won't have the note removed?
mentioned
by None at 2023-01-09 20:55:05.subscribed
by None at 2023-01-09 20:55:05.labeled
by Trey Pendragon at 2023-01-09 20:55:51.this is wrong.
convert_to_draft
by None at 2023-01-09 18:48:59.head_ref_force_pushed
by None at 2023-01-09 21:15:21.ready_for_review
by None at 2023-01-09 21:15:35.head_ref_force_pushed
by None at 2023-01-09 21:20:12.referenced
by Bess Sadler at 2023-01-09 14:05:45.merged
by Bess Sadler at 2023-01-09 14:05:45.closed
by Bess Sadler at 2023-01-09 14:05:45.head_ref_deleted
by Bess Sadler at 2023-01-09 14:05:46.


Home
About
Cast
Methods
List of Series
Fanclub
Sign up
Here!
Contact Information
First Name:
Last Name:
Phone Number:
Email:
Address
Address:
User Creation
Desired Username (4-16 Characters):
Password Creation:
Confirm Password:
Credit Card Information
Credit Card Company:
Visa
Master Card
American Express
Credit Card #:
Expiration Month:
01
02
03
04
05
06
07
08
09
10
11
12
Expiration Year:
2016
2017
2018
2019
2020
2021
2022
CVV
?
GET ME INTO THE CLUB!
Clear data
Home


In this blog post I go over using lldb with rust and how get setup with lldb on Mac OS X.
Installing lldb
Read the official guide link on installing lldb.
If you have a Mac then you should already have lldb installed.
Notice that lldb reports the version of lldb and the version of swift.
Various ways of Running Summation Program
Let us look at a simple command line rust program that computes the summation provided as input.
use std::env;
fn main() {
let args: Vec<String> = env::args().collect();
let numbers = &args[1..];
let numbers: Vec<f32> = numbers
.iter()
.map(|num| num.parse().unwrap())
.collect();
let summation = summation_with_fold(numbers.clone());
println!("summation_with_fold is {}", summation);
let summation = summation_with_loop(numbers.clone());
println!("summation_with_loop is {}", summation);
}
fn summation_with_loop(numbers: Vec<f32>) -> f32 {
let mut sum = 0.0;
for num in numbers.iter() {
sum += num;
}
sum
}
fn summation_with_fold(numbers: Vec<f32>) -> f32 {
let sum = numbers
.iter()
.fold(0.0, |sum, val| sum + val);
return sum;
}
We can run this program using the rust playground but we cannot supply argument like we can in a shell session:
We can run this program using cargo run like this:
We can also run our program by using the compiled binary executable like this:
Running summation program with lldb
We can run our rust program with the rust-lldb executable.
Here is the rust lldb bash script that gets invoked:
#!/bin/sh
# Exit if anything fails
set -e
# Find out where to look for the pretty printer Python module
RUSTC_SYSROOT=`rustc --print sysroot`
# Find the host triple so we can find lldb in rustlib.
host=`rustc -vV | sed -n -e 's/^host: //p'`
lldb=lldb
if [ -f "$RUSTC_SYSROOT/lib/rustlib/$host/bin/lldb" ]; then
lldb="$RUSTC_SYSROOT/lib/rustlib/$host/bin/lldb"
else
LLDB_VERSION=`"$lldb" --version 2>/dev/null | head -1 | cut -d. -f1`
if [ "$LLDB_VERSION" = "lldb-350" ]
then
echo "***"
echo \
"WARNING: This version of LLDB has known issues with Rust and cannot \
display the contents of local variables!"
echo "***"
fi
fi
# Prepare commands that will be loaded before any file on the command line has been loaded
script_import="command script import \"$RUSTC_SYSROOT/lib/rustlib/etc/lldb_rust_formatters.py\""
category_definition="type summary add --no-value --python-function lldb_rust_formatters.print_val -x \".*\" --category Rust"
category_enable="type category enable Rust"
# Call LLDB with the commands added to the argument list
exec "$lldb" --one-line-before-file="$script_import" \
--one-line-before-file="$category_definition" \
--one-line-before-file="$category_enable" \
"$@"
When you install rust this bash script gets bundled with cargo:
Not let us run our summation binary executable using rust-lldb like this:
Let us simply run summation with no arguments:
Notice here that we get 0 since we didn’t provide any arguments.
Let us re run again no pun intended with args now!
Let us run the help on the b command:
Now let us set a breakpoint in lldb on line 8 and 13:
Notice that we did it the long and then the short way in lldb.
We can list the breakpoints in lldb like this:
Now let us rerun the main.rs file and notice that the breakpoint is hit on line 8 now!
Let us continue to the next breakpoint typing the c command:
Let us step into the summation_with_fold function now using lldb using a couple of commands:
We can dynamically change the value of a variable in the summation_with_fold function like this:
We can look at the value of the variable now like this:
The po command stands for print object, p stands for print and frame variable is the current stack frame!
Next let us step out of the summation_with_fold function now.
Let us continue and see the current values:
Notice how the summation_with_fold has the value 53 that we set dynamically.
We can unset our breakpoints like this:
Using help in lldb
You can find about the available command in lldb by running help:
You can also get help on each particular command by running help like:
help subcommand
Some commands have subcommands like the breakpoint command which you can get help on:
Some commands have aliases that you can run like b for breakpoint and more.
A great feature of the lldb debugger is that there is autocomplete that you can invoke by simply pressing the tab character
All in all I would say rust-lldb is a great addition to debugging rust programs.
There is a whole more you can do with lldb and please read the official lldb documentation for more
Please follow me at jbelmont @ github and jbelmont80 @ twitter
Feel free to leave a comment if you like.
Until Next Time :)


Your new Version {{ uuidVersion }} UUID:
A Version 1 UUID is a universally unique identifier that is generated using a timestamp and the MAC address of the computer on which it was generated.
A Version 4 UUID is a universally unique identifier that is generated using random numbers. The UUIDs from this website were generated using a cryptographically-strong random number generator.
dunno
UUIDs generated from this site are RFC 4122 compliant.
The UUIDs generated by this site are provided "AS IS", without warranty of any kind. You are responsible for using the UUIDs and assume any risk inherent to using them. Do not use the UUIDs generated by this site if you do not agree to these terms. UUIDs from cached versions of this site should not be used.


Yemen rebels seize two South Korean, one Saudi vessel
The Huthis acknowledged they had seized three ships, including a Saudi one, in the Red Sea a few miles off Uqban island, west of the rebel-held capital Sanaa.
Yemen's Iran-aligned rebels seized a Saudi-flagged tug and two South Korean vessels at the weekend, the insurgents and Seoul officials said on Tuesday.
The incident follows a lull in Huthi attacks on Saudi Arabia as one Riyadh official said the kingdom had established an "open channel" with the rebels in a bid to end the four-year conflict.
The Huthis acknowledged they had seized three ships, including a Saudi one, in the Red Sea a few miles off Uqban island, west of the rebel-held capital Sanaa.
Seoul's foreign ministry said a South Korean dredger was being towed by one Korean and one Saudi-flagged tug when they were seized by the Huthis.
It added that a total of 16 crew, two of them South Korean, had been taken to the Red Sea port of Saleef, where they were being held by the rebels.
"All of our citizens... are healthy and safe," ministry officials said in a statement.
"We are doing our very best for the early release of our citizens."
Seoul has sent the South Korean navy ship Cheonghae, which had been on anti-piracy standby off the coast of Oman, to waters near where the incident took place.
The Saudi-led military coalition backing Yemen's internationally recognised government accused the rebels of "hijacking" the Rabigh-3, which a global tracking website described as a Saudi-flagged vessel.
The rebels on Tuesday said the three ships were seized off Uqban island after they entered "territorial waters without prior notice", according to a statement carried by their Al-Masirah television channel.
The ships were taken to Saleef, it added, without disclosing the nationalities or number of crew members.
The Huthi rebels have been fighting the government and its allies for more than four years in a war that has pushed the country to the brink of famine.
A year after the Huthis seized Sanaa, Saudi Arabia, the United Arab Emirates and their allies intervened in the conflict in support of President Abedrabbo Mansour Hadi.
Since 2015, tens of thousands of people, most of them civilians, have been killed in a conflict that has triggered what the United Nations has described as the world's worst humanitarian crisis.
Earlier this month, a senior Saudi official raised hopes of possible de-escalation after he said Riyadh had an "open channel" with the rebels with the goal of ending the conflict.


- A NASA Headquarters overview
- of an LWS (and implicitly the Heliophysics) Data Environment and what will be needed. (ppt, Feb. 2003) Generalizes the Virtual Solar Observatory concept to "VxOs" for other disciplines, linked by common XML registry schema to each other and to various services. Points to the need for appropriate management structure.
- The Final Report of the LWS Science Data System Planning Team
- the precursor group to the current LWS Ad Hoc Data Environments working group. (Jan. 2002) Recommends a distributed approach growing out of current systems, guided by science needs, with a small administrative staff. Also advocates a firmer WWW presence for the data system--realized by this page and related links. (MSWord version)
- An overview
- of how a data/services access VO would work and how it could be implemented; this one is called the "Scientific Resource Access System," but the ideas are quite general.
- A draft plan
- for the LWS Data Environment from the LWS Data Architecture Project Scientist. Contains specific recommendations for the next steps.
- The Right Amount of Glue: Technologies and Standards relevant to a Future Solar Terrestrial Data Environment
- presents the idea that standards such as XML and related software tools, and the behavioral standard of sharing data provide the "glue" needed to hold together a data access and use system.
- The NASA Heliophysics "Rules of the Road"
- for data providers and users emphasizes providers' responsibility to provide open data and analysis tools, and users' responsibility to consult with and inform providers about their use of the data. This document, somewhat modified, is now in the HP Data Policy.
We are researchers, simulators, information technology experts, developers and data engineers dedicated to advancing science and improving the heliophysics data environment.


Soundnesthesia
Plans
Students
Teachers
Schools
Demo
Contact Us
Send us a message
We'll get in touch with you as soon as possible.
Your name
Email address
Phone
Your message
Our Address
xxx,
06160,
Juan les Pins, France
By Phone
+33 6 xx xx xx xx


Custom Types
This page describes how to create your own custom resource types to add new resource types to Puppet. It covers the nature of the type/provider split, how to develop the type file, and how types and providers interact; for more complete details on developing providers, see the Provider Development page.
Puppet types and providers must always be written in Ruby. If you’re new to Ruby, what is going on should still be somewhat evident from the examples below, but some experience with Ruby is definitely recommended.
The internals of how types are created have changed over Puppet’s lifetime, and this document will focus on best practices, skipping over all the things you can but probably shouldn’t do.
Note: Often the best way to learn types and providers is to read the existing type and providers in Puppet’s core codebase. One warning: Don’t start with the
file
type; start withuser
orpackage
instead. New extension writers often expect thatfile
would be a nice easy one to get started with, and it’s actually an incredibly complicated morass of special cases that most types just don’t have to deal with.User or package, not file.
Types and Providers
When making a new Puppet type, you will create two things:
- The “type” itself, which is a model of the resource type. It defines what parameters are available, handles input validation, and determines what features a provider can (or should) provide.
- One or more providers for that type, which implements the type by translating its capabilities into specific operations on a system. (For example, the package has
yum
andapt
providers which implement package resources on Red Hat-like and Debian-like systems, respectively.)
Deploying and Using Types and Providers
To use new types and providers, two conditions must be met:
- The type and providers must be present in a module on the puppet master server(s). Like other types of plugin (such as custom functions and custom facts), they should go in the module’s
lib
directory:- Type files should be located at
lib/puppet/type/<TYPE NAME>.rb
. - Provider files should be located at
lib/puppet/provider/<TYPE NAME>/<PROVIDER NAME>.rb
.
- Type files should be located at
- If you are using an agent/master Puppet deployment, each agent node must have its
pluginsync
setting in puppet.conf set totrue
.- Starting in Puppet 3.0, this setting defaults to true.
- In Puppet 2.x, it defaults to false and must be explicitly enabled.
In masterless Puppet using puppet apply, pluginsync is not required, but the module containing the type and providers must be present on each node.
See the Plugins In Modules page for more details on distributing custom types and facts via modules.
Types
When defining the resource type, focus on what the resource can do, not how it does it.
Creating a Type
Types are created by calling the newtype
method on the Puppet::Type
class:
# lib/puppet/type/database.rb
Puppet::Type.newtype(:database) do
@doc = "Create a new database."
# ... the code ...
end
- The name of the type is the only required argument to
newtype
. The name must be a Ruby symbol, and the name of the file containing the type must match the type’s name. - The
newtype
method also requires a block of code, specified with either curly braces ({ ... }
) or thedo ... end
syntax. This code block will implement the type, and contains all of the properties and parameters. The block will not be passed any arguments.
Options
When creating a type, you may also specify options after the name. There are currently two options available, and neither is frequently used.
Options must be specified as a hash, although Ruby method arguments allow you to leave the curly braces off of hashes.
:self_refresh => true
— Cause resources of this type to refresh (as if they had received an event via a notify/subscribe relationship) whenever a change is made to the resource. Most notably used in the coremount
type.:parent => <CLASS>
— A parent class to use for the type; if not specified,Puppet::Type
is used as the parent class. Alternate parent classes are not used anywhere in the core Puppet types, and we are not providing examples of it at this time.
Type Documentation
You can and should write a string describing the resource type and assign it to the @doc
instance variable. This string can be extracted by the puppet doc --reference type
command (which outputs a complete type reference which will include your new type) and the puppet describe
command (which outputs information about specific types).
The string should be in Markdown format (avoiding dialect-specific features that aren’t universally supported). When the Puppet tools extract the string, they will strip the greatest common amount of leading whitespace from the front of each line, excluding the first line. For example:
Puppet::Type.newtype(:database) do
@doc = %q{Creates a new database. Depending
on the provider, this may create relational
databases or NoSQL document stores.
Example:
database {'mydatabase':
ensure => present,
owner => root,
}
}
end
In this example, any whitespace would be trimmed from the first line (in this case, it’s zero spaces), then the greatest common amount would be trimmed from remaining lines. Three lines have four leading spaces, two lines have six, and two lines have eight, so four leading spaces would be trimmed from each line. This leaves the example code block indented by four spaces, and thus doesn’t break the Markdown formatting.
Properties and Parameters
The bulk of a type consists of properties and parameters.
Both properties and parameters will become the resource attributes available when declaring a resource of the new type. The difference between the two is subtle but important:
- Properties should map more or less directly to something measurable on the target system. For example, the UID and GID of a user account would be properties, since their current state can be queried or changed. In practical terms, setting a value for a property causes a method to be called on the provider.
- Parameters change how Puppet manages a resource, but do not necessarily map directly to something measurable. For example, the
user
type’smanagehome
attribute is a parameter — its value affects what Puppet does, but the question of whether Puppet is managing a home directory isn’t an innate property of the user account.
Additionally, there are a few special attributes called metaparameters, which are supported by all resource types. These don’t need to be handled when creating new types; they’re implemented elsewhere.
A normal type will define multiple properties and must define at least one parameter.
Properties
Here’s where we define how the resource really works. In most cases, it’s the properties that interact with your resource’s providers. If you define a property named owner, then when you are retrieving the state of your resource, then the owner property will call the owner method on the provider. In turn, when you are setting the state (because the resource is out of sync), then the owner property will call the owner= method to set the state on disk.
There’s one common exception to this: The ensure property is special because it’s used to create and destroy resources. You can set this property up on your resource type just by calling the ensurable method in your type definition:
Puppet::Type.newtype(:database) do
ensurable
...
end
This property uses three methods on the provider: create, destroy, and exists?. The last method, somewhat obviously, is a boolean to determine if the resource current exists. If a resource’s ensure property is out of sync, then no other properties will be checked or modified.
You can modify how ensure behaves, such as by adding other valid values and determining what methods get called as a result; see existing types like package for examples.
The rest of the properties are defined a lot like you define the types, with the newproperty method, which should be called on the type:
Puppet::Type.newtype(:database) do
ensurable
newproperty(:owner) do
desc "The owner of the database."
...
end
end
Note the call to desc; this sets the documentation string for this property, and for Puppet types that get distributed with Puppet, it is extracted as part of the Type reference.
When Puppet was first developed, there would normally be a lot of code in this property definition. Now, however, you normally only define valid values or set up validation and munging. If you specify valid values, then Puppet will only accept those values, and it will automatically handle accepting either strings or symbols. In most cases, you only define allowed values for ensure, but it works for other properties, too:
newproperty(:enable) do
newvalue(:true)
newvalue(:false)
end
You can attach code to the value definitions (this code would be called instead of the property= method), but it’s normally unnecessary.
For most properties, though, it is sufficient to set up validation:
newproperty(:owner) do
validate do |value|
unless value =~ /^\w+/
raise ArgumentError, "%s is not a valid user name" % value
end
end
end
Note that the order in which you define your properties can be important: Puppet keeps track of the definition order, and it always checks and fixes properties in the order they are defined.
Customizing Behaviour
By default, if a property is assigned multiple values in an array:
- It is considered in sync if any of those values matches the current value.
- If none of those values match, the first one will be used when syncing the property.
If, instead, the property should only be in sync if all values match the current value (e.g., a list of times in a cron job), you can declare this:
newproperty(:minute, :array_matching => :all) do # :array_matching defaults to :first
...
end
You can also customize how information about your property gets
logged. You can create an is_to_s
method to change how the
current values are described, should_to_s
to change how the
desired values are logged, and change_to_s
to change the overall
log message for changes. See current types for examples.
Handling Property Values
Handling values set on properties is currently somewhat confusing,
and will hopefully be fixed in the future. When a resource is
created with a list of desired values, those values are stored in
each property in its @should instance variable. You can retrieve
those values directly by calling should on your resource (although
note that when :array_matching
is set to :first
you get the first
value in the array, otherwise you get the whole array):
myval = should(:color)
When you’re not sure (or don’t care) whether you’re dealing with a property or parameter, it’s best to use value:
myvalue = value(:color)
Parameters
Parameters are defined essentially exactly the same as properties; the only difference between them is that parameters never result in methods being called on providers.
To define a new parameter, call the newparam
method. This method takes the name of the parameter (as a symbol) as its argument, as well as a block of code. You can and should provide documentation for each parameter by calling the desc
method inside its block. Leading whitespace is trimmed from multiline strings as described above.
newparam(:name) do
desc "The name of the database."
end
Namevar
Every type must have at least one mandatory parameter: the namevar. This parameter will uniquely identify each resource of the type on the target system — for example, the path of a file on disk, the name of a user account, or the name of a package.
If the user doesn’t specify a value for the namevar when declaring a resource, its value will default to the title of the resource.
There are three ways to designate a namevar. Every type must have exactly one parameter that meets exactly one of these criteria:
Option 1: Create a parameter whose name is :name
. Since most types just use :name
as the namevar, it gets special treatment and will automatically become the namevar.
newparam(:name) do
desc "The name of the database."
end
Option 2: Provide the :namevar => true
option as an additional argument to the newparam
call. This allows you to use a namevar with a different, more descriptive name (such as the file
type’s path
parameter).
newparam(:path, :namevar => true) do
...
end
Option 3: Call the isnamevar
method (which takes no arguments) inside the parameter’s code block. This allows you to use a namevar with a different, more descriptive name. There is no practical difference between this and option 2.
newparam(:path) do
isnamevar
...
end
Errors When Namevar is Absent
If you try to create a type that lacks a namevar, you’ll see one of two errors when declaring resources of that type, depending on the Puppet version.
Puppet 2.7:
$ puppet apply -e "testing { h: }" Error: undefined method `merge' for []:Array
Puppet 3:
$ puppet apply -e "testing { h: }" Error: No set of title patterns matched the title "h".
The fact that these are not particularly helpful is tracked as issue 5220.
Specifying Allowed Values
If your parameter has a fixed list of valid values, you can declare them all at once:
newparam(:color) do
newvalues(:red, :green, :blue, :purple)
end
You can specify regexes in addition to literal values; matches against regexes always happen after equality comparisons against literal values, and those matches are not converted to symbols. For instance, given the following definition:
newparam(:color) do
desc "Your color, and stuff."
newvalues(:blue, :red, /.+/)
end
If you provide blue as the value, then your parameter will get set to :blue, but if you provide green, then it will get set to “green”.
Validation and Munging
If your parameter does not have a defined list of values, or you need to convert the values in some way, you can use the validate and munge hooks:
newparam(:color) do
desc "Your color, and stuff."
newvalues(:blue, :red, /.+/)
validate do |value|
if value == "green"
raise ArgumentError,
"Everyone knows green databases don't have enough RAM"
else
super
end
end
munge do |value|
case value
when :mauve, :violet # are these colors really any different?
:purple
else
super
end
end
end
The default validate method looks for values defined using newvalues and if there are any values defined it accepts only those values (this is exactly how allowed values are validated). The default munge method converts any values that are specifically allowed into symbols. If you override either of these methods, note that you lose this value handling and symbol conversion, which you’ll have to call super for.
Values are always validated before they’re munged.
Lastly, validation and munging only* happen when a value is assigned. They have no role to play at all during use of a given value, only during assignment.
Boolean Parameters
Boolean parameters are common. To avoid repetition, some utilities are available:
require 'puppet/parameter/boolean'
# ...
newparam(:force, :boolean => true, :parent => Puppet::Parameter::Boolean)
There are two parts here. The :parent => Puppet::Parameter::Boolean
part
configures the parameter to accept lots of names for true and false, to make
things easy for your users. The :boolean => true
creates a boolean method
on the type class to return the value of the parameter. In this example, the
method would be named force?
.
Automatic Relationships
Your type can specify automatic relationships it can have with resources. You use the autorequire hook, which requires a resource type as an argument, and your code should return a list of resource names that your resource could be related to:
autorequire(:file) do
["/tmp", "/dev"]
end
Note that this won’t throw an error if resources with those names do not exist; the purpose of this hook is to make sure that if any required resources are being managed, they get applied before the requiring resource.
Providers
Look at the Provider Development page for intimate detail; this document will only cover how the resource types and providers need to interact. Because the properties call getter and setter methods on the providers, except in the case of ensure, the providers must define getters and setters for each property.
Provider Features
A recent development in Puppet (around 0.22.3) is the ability to declare what features providers can have. The type declares the features and what’s required to make them work, and then the providers can either be tested for whether they suffice or they can declare that they have the features. Additionally, individual properties and parameters in the type can declare that they require one or more specific features, and Puppet will throw an error if those parameters are used with providers missing those features:
newtype(:coloring) do
feature :paint, "The ability to paint.", :methods => [:paint]
feature :draw, "The ability to draw."
newparam(:color, :required_features => %w{paint}) do
...
end
end
The first argument to the feature method is the name of the feature, the second argument is its description, and after that is a hash of options that help Puppet determine whether the feature is available. The only option currently supported is specifying one or more methods that must be defined on the provider. If no methods are specified, then the provider needs to specifically declare that it has that feature:
Puppet::Type.type(:coloring).provide(:drawer) do
has_feature :draw
end
The provider can specify multiple available features at once with has_features.
When you define features on your type, Puppet automatically defines a bunch of class methods on the provider:
- feature?: Passed a feature name, will return true if the feature is available or false otherwise.
- features: Returns a list of all supported features on the provider.
- satisfies?: Passed a list of feature, will return true if they are all available, false otherwise.
Additionally, each feature gets a separate boolean method, so the above example would result in a paint? method on the provider.


We extend solutions!
- engage bricks-and-clicks interfaces
- orchestrate real-time platforms
- unleash out-of-the-box bandwidth
- grow vertical e-markets
- generate vertical architectures
- redefine efficient platforms
- revolutionize synergistic communities
- redefine world-class deliverables
- generate efficient technologies


What is Hoki?¶
Note
NEW FEATURES: Check out AgeWizard - A pipeline to systematically age any resolved stellar population!
Bridging the gap between theory and observations¶
Historically, theoretical models have been released to the community with the expectation that users would create their own data handling scripts as they perform the analysis. This was in line with a research culture where most people had their own code, resulting in a duplication of effort and creating the potential for a reproducibility crisis, as most personal scripts are not shared with the community.
In order to facilitate the application of BPASS to a wide range of scientific investigations, we have developped the tools necessary for observers to take full advantage of our models in a stream-lined, intuitive manner.
Hoki is a dedicated python package designed to provide a user friendly interface to the BPASS models in order to bridge the gap between theory and observations.
The varsatility of Hoki allows you to focus on the science, and worry less about the technical nitty gritty that comes with using the varied outputs of a theoretical code.
Built with data analysis in mind¶
Our vision for hoki
is to provide tools that can be integrated in your everyday workflow and make your life extra simple! Do you want to spend ages figuring out 5 by 100 by 100 by 3 by 3 data object contained in a single ASCII file? Great news, you don’t need to!
We leverage the powerful capabilites of ubiquitous packages such as numpy
, pandas
and matplotlib
in order to make the outputs of BPASS easily accessible and usable for scientific data analysis. This way you get to spend more time looking at data and less time looking at code.


Report
Info
Compiler: Clang 12.0.0 (Apple version)
CPU: ARM64_T8020
CPU Frequency: 2496.67 MHz
Charts
JSON reader
JSON reader (cpb)
JSON writer pretty
JSON writer minify
JSON stats


This is my mobile phone number, feel free to reach out 6 days a week from 8 A.M. - 9 P.M.
(330)-840-0979This is my business e-mail address, feel free to reach out at any time with any questions!
<EMAIL_ADDRESS>is a link to my resume. Feel free to download it and reach out at anytime!
Resume


System Architect Symbol details for "Level"
Access Type (Class)
- Child Diagrams:
-
Access Type (
UML Class)
Description:
"Level" specifying the extents to which access to information may be granted.
Examples:
Examples which may be considered include:
Read only
Copy
Forward to others
Absolute.
Each level would be deemed to include all lower levels.
Activity Qualifier Type (Class)
- Description:
"Descriptive Category" capable of classifying an "Activity Qualifier"
- Comment:
Necessary to indicate the nature of the qualification as opposed to its value.
- Examples:
In medication, "Route", "Form", "Strength", "Special Instructions" are all examples of "Activity
Qualifier Type".
Activity Type (Class)
- Description:
"Descriptive Category" capable of being used as a category for "Activities".
Certainty Level (Class)
- Child Diagrams:
-
Certainty Level (
UML Class)
- Description:
"Level" being an extent to which confidence can be ascribed to the value or existence of a "Subject
Property" or a qualifier.
Contact Method (Class)
- Description:
"Category" describing a "Subject Contact".
- Comment:
-
The population of this includes:
Postal address
Telephone number (landline / mobile)
Fax number
Email address
Telex number
Bleeper number.
DC/Describing (Generalization Node)
- Base Class:
"Descriptive Category"
- Definitions Used:
-
Descriptive Category (Class)
Descriptive Category (Class)
- Description:
"Category" capable of classifying an "Object" directly rather than by associating it with another
"Object".
- Comment:
As distinct from Associative Category.
Desirability Level (Class)
- Child Diagrams:
-
Desirability Level (
UML Class)
- Description:
"Level" providing a value for an "Evaluated Desirability".
Incident Type (Class)
- Description:
"Descriptive Category" capable of being used as a category for "Incidents".
Intention Type (Class)
- Description:
"Category" being capable of classifying a purpose of care.
Level (Class)
- Description:
"Descriptive Category" used to describe the level to which something obtains.
Level/Direction (Generalization Node)
- Base Class:
Level
- Definitions Used:
-
Level (Class)
Normality Level (Class)
- Child Diagrams:
-
Normality Level (
UML Class)
- Description:
"Level" providing a value for a "Normality of Property".
Property Qualifier Type (Class)
- Description:
"Descriptive Category" capable of classifying a "Classified Property Qualifier".
- Comment:
Used to indicate how a "Property Qualifier" qualifies a "Subject Property".
- Examples:
Laterality, site (of the body).
Reason For Abandoning (Class)
- Description:
"Category" capable of classifying abandoned activities and intentions.
Reason For Rejection (Class)
- Description:
"Category" capable of classifying rejected "Activities", "Foci" and "Intentions".
- Comment:
-
Attribute in CBS v2.
Extended to cover foci & intentions as well as activities.
Reason Not Required (Class)
- Description:
"Category" capable of classifying reasons why "Activities" are not required.
Resource Type (Class)
- Description:
"Descriptive Category" with the ability to classify "Resource Held".
Significance Level (Class)
- Child Diagrams:
-
Significance Level (
UML Class)
- Description:
"Level" providing a value for a "Significance Of Property".
State Type (Class)
"Descriptive Category" capable of classifying a state of a Class which has a documented state
transition.
Subject Characteristic Type (Class)
- Description:
"Descriptive Category" capable of classifying a "Subject Characteristic".
- Comment:
Note that Subject Characteristic is the only type of Subject Property which is descriptive, ie not
associative.
Urgency (Class)
- Child Diagrams:
-
Urgency (
UML Class)
- Description:
"Level" capable of specifying a perceived requirement for speed.


|
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object android.support.v4.app.Fragment
public class Fragment
Static library support version of the framework's android.app.Fragment
.
Used to write apps that run on platforms prior to Android 3.0. When running
on Android 3.0 or above, this implementation is still used; it does not try
to switch to the framework's implementation. See the framework android.app.Fragment
documentation for a class overview.
The main differences when using this support version instead of the framework version are:
FragmentActivity
FragmentActivity.getSupportFragmentManager()
to get the
FragmentManager
| Nested Class Summary | |
|---|---|
static class |
Fragment.InstantiationException
Thrown by instantiate(Context, String, Bundle) when
there is an instantiation failure. |
static class |
Fragment.SavedState
State information that has been retrieved from a fragment instance through FragmentManager.saveFragmentInstanceState . |
| Constructor Summary | |
|---|---|
Fragment()
Default constructor. |
| Method Summary | |
|---|---|
void |
dump(java.lang.String prefix,
java.io.FileDescriptor fd,
java.io.PrintWriter writer,
java.lang.String[] args)
Print the Fragments's state into the given stream. |
boolean |
equals(java.lang.Object o)
Subclasses can not override equals(). |
FragmentActivity |
getActivity()
Return the Activity this fragment is currently associated with. |
Bundle |
getArguments()
Return the arguments supplied when the fragment was instantiated, if any. |
FragmentManager |
getChildFragmentManager()
Return a private FragmentManager for placing and managing Fragments inside of this Fragment. |
FragmentManager |
getFragmentManager()
Return the FragmentManager for interacting with fragments associated with this fragment's activity. |
int |
getId()
Return the identifier this fragment is known by. |
LayoutInflater |
getLayoutInflater(Bundle savedInstanceState)
|
LoaderManager |
getLoaderManager()
Return the LoaderManager for this fragment, creating it if needed. |
Fragment |
getParentFragment()
Returns the parent Fragment containing this Fragment. |
Resources |
getResources()
Return getActivity().getResources() . |
boolean |
getRetainInstance()
|
java.lang.String |
getString(int resId)
Return a localized string from the application's package's default string table. |
java.lang.String |
getString(int resId,
java.lang.Object... formatArgs)
Return a localized formatted string from the application's package's default string table, substituting the format arguments as defined in Formatter and String.format(java.lang.String, java.lang.Object...) . |
java.lang.String |
getTag()
Get the tag name of the fragment, if specified. |
Fragment |
getTargetFragment()
Return the target fragment set by setTargetFragment(android.support.v4.app.Fragment, int) . |
int |
getTargetRequestCode()
Return the target request code set by setTargetFragment(android.support.v4.app.Fragment, int) . |
java.lang.CharSequence |
getText(int resId)
Return a localized, styled CharSequence from the application's package's default string table. |
boolean |
getUserVisibleHint()
|
View |
getView()
Get the root view for the fragment's layout (the one returned by onCreateView(LayoutInflater, ViewGroup, Bundle) ),
if provided. |
int |
hashCode()
Subclasses can not override hashCode(). |
boolean |
hasOptionsMenu()
|
static Fragment |
instantiate(Context context,
java.lang.String fname)
Like instantiate(Context, String, Bundle) but with a null
argument Bundle. |
static Fragment |
instantiate(Context context,
java.lang.String fname,
Bundle args)
Create a new instance of a Fragment with the given class name. |
boolean |
isAdded()
Return true if the fragment is currently added to its activity. |
boolean |
isDetached()
Return true if the fragment has been explicitly detached from the UI. |
boolean |
isHidden()
Return true if the fragment has been hidden. |
boolean |
isInLayout()
Return true if the layout is included as part of an activity view hierarchy via the <fragment> tag. |
boolean |
isMenuVisible()
|
boolean |
isRemoving()
Return true if this fragment is currently being removed from its activity. |
boolean |
isResumed()
Return true if the fragment is in the resumed state. |
boolean |
isVisible()
Return true if the fragment is currently visible to the user. |
void |
onActivityCreated(Bundle savedInstanceState)
Called when the fragment's activity has been created and this fragment's view hierarchy instantiated. |
void |
onActivityResult(int requestCode,
int resultCode,
Intent data)
Receive the result from a previous call to startActivityForResult(Intent, int) . |
void |
onAttach(Activity activity)
Called when a fragment is first attached to its activity. |
void |
onConfigurationChanged(Configuration newConfig)
|
boolean |
onContextItemSelected(MenuItem item)
This hook is called whenever an item in a context menu is selected. |
void |
onCreate(Bundle savedInstanceState)
Called to do initial creation of a fragment. |
Animation |
onCreateAnimation(int transit,
boolean enter,
int nextAnim)
Called when a fragment loads an animation. |
void |
onCreateContextMenu(ContextMenu menu,
View v,
ContextMenuInfo menuInfo)
Called when a context menu for the view is about to be shown. |
void |
onCreateOptionsMenu(Menu menu,
MenuInflater inflater)
Initialize the contents of the Activity's standard options menu. |
View |
onCreateView(LayoutInflater inflater,
ViewGroup container,
Bundle savedInstanceState)
Called to have the fragment instantiate its user interface view. |
void |
onDestroy()
Called when the fragment is no longer in use. |
void |
onDestroyOptionsMenu()
Called when this fragment's option menu items are no longer being included in the overall options menu. |
void |
onDestroyView()
Called when the view previously created by onCreateView(LayoutInflater, ViewGroup, Bundle) has
been detached from the fragment. |
void |
onDetach()
Called when the fragment is no longer attached to its activity. |
void |
onHiddenChanged(boolean hidden)
Called when the hidden state (as returned by isHidden() of
the fragment has changed. |
void |
onInflate(Activity activity,
AttributeSet attrs,
Bundle savedInstanceState)
Called when a fragment is being created as part of a view layout inflation, typically from setting the content view of an activity. |
void |
onLowMemory()
|
boolean |
onOptionsItemSelected(MenuItem item)
This hook is called whenever an item in your options menu is selected. |
void |
onOptionsMenuClosed(Menu menu)
This hook is called whenever the options menu is being closed (either by the user canceling the menu with the back/menu button, or when an item is selected). |
void |
onPause()
Called when the Fragment is no longer resumed. |
void |
onPrepareOptionsMenu(Menu menu)
Prepare the Screen's standard options menu to be displayed. |
void |
onResume()
Called when the fragment is visible to the user and actively running. |
void |
onSaveInstanceState(Bundle outState)
Called to ask the fragment to save its current dynamic state, so it can later be reconstructed in a new instance of its process is restarted. |
void |
onStart()
Called when the Fragment is visible to the user. |
void |
onStop()
Called when the Fragment is no longer started. |
void |
onViewCreated(View view,
Bundle savedInstanceState)
Called immediately after onCreateView(LayoutInflater, ViewGroup, Bundle)
has returned, but before any saved state has been restored in to the view. |
void |
onViewStateRestored(Bundle savedInstanceState)
Called when all saved state has been restored into the view hierarchy of the fragment. |
void |
registerForContextMenu(View view)
Registers a context menu to be shown for the given view (multiple views can show the context menu). |
void |
setArguments(Bundle args)
Supply the construction arguments for this fragment. |
void |
setHasOptionsMenu(boolean hasMenu)
Report that this fragment would like to participate in populating the options menu by receiving a call to onCreateOptionsMenu(Menu, MenuInflater)
and related methods. |
void |
setInitialSavedState(Fragment.SavedState state)
Set the initial saved state that this Fragment should restore itself from when first being constructed, as returned by FragmentManager.saveFragmentInstanceState . |
void |
setMenuVisibility(boolean menuVisible)
Set a hint for whether this fragment's menu should be visible. |
void |
setRetainInstance(boolean retain)
Control whether a fragment instance is retained across Activity re-creation (such as from a configuration change). |
void |
setTargetFragment(Fragment fragment,
int requestCode)
Optional target for this fragment. |
void |
setUserVisibleHint(boolean isVisibleToUser)
Set a hint to the system about whether this fragment's UI is currently visible to the user. |
void |
startActivity(Intent intent)
Call Activity#startActivity(Intent) on the fragment's
containing Activity. |
void |
startActivityForResult(Intent intent,
int requestCode)
Call Activity#startActivityForResult(Intent, int) on the fragment's
containing Activity. |
java.lang.String |
toString()
|
void |
unregisterForContextMenu(View view)
Prevents a context menu to be shown for the given view. |
| Methods inherited from class java.lang.Object |
|---|
clone, finalize, getClass, notify, notifyAll, wait, wait, wait |
| Constructor Detail |
|---|
public Fragment()
setArguments(Bundle)
and later retrieved by the Fragment with getArguments()
.
Applications should generally not implement a constructor. The
first place application code an run where the fragment is ready to
be used is in onAttach(Activity)
, the point where the fragment
is actually associated with its activity. Some applications may also
want to implement onInflate(Activity, AttributeSet, Bundle)
to retrieve attributes from a
layout resource, though should take care here because this happens for
the fragment is attached to its activity.
| Method Detail |
|---|
public static Fragment instantiate(Context context, java.lang.String fname)
instantiate(Context, String, Bundle)
but with a null
argument Bundle.
public static Fragment instantiate(Context context, java.lang.String fname, Bundle args)
context
- The calling context being used to instantiate the fragment.
This is currently just used to get its ClassLoader.fname
- The class name of the fragment to instantiate.args
- Bundle of arguments to supply to the fragment, which it
can retrieve with getArguments()
. May be null.
java.lang.InstantiationException
- If there is a failure in instantiating
the given fragment class. This is a runtime exception; it is not
normally expected to happen.public final boolean equals(java.lang.Object o)
equals
in class java.lang.Object
public final int hashCode()
hashCode
in class java.lang.Object
public java.lang.String toString()
toString
in class java.lang.Object
public final int getId()
public final java.lang.String getTag()
public void setArguments(Bundle args)
public final Bundle getArguments()
public void setInitialSavedState(Fragment.SavedState state)
FragmentManager.saveFragmentInstanceState
.
state
- The state the fragment should be restored from.public void setTargetFragment(Fragment fragment, int requestCode)
FragmentManager.putFragment()
.
fragment
- The fragment that is the target of this one.requestCode
- Optional request code, for convenience if you
are going to call back with onActivityResult(int, int, Intent)
.public final Fragment getTargetFragment()
setTargetFragment(android.support.v4.app.Fragment, int)
.
public final int getTargetRequestCode()
setTargetFragment(android.support.v4.app.Fragment, int)
.
public final FragmentActivity getActivity()
public final Resources getResources()
getActivity().getResources()
.
public final java.lang.CharSequence getText(int resId)
resId
- Resource id for the CharSequence textpublic final java.lang.String getString(int resId)
resId
- Resource id for the stringpublic final java.lang.String getString(int resId, java.lang.Object... formatArgs)
Formatter
and String.format(java.lang.String, java.lang.Object...)
.
resId
- Resource id for the format stringformatArgs
- The format arguments that will be used for substitution.public final FragmentManager getFragmentManager()
getActivity()
, during the time from when the fragment is
placed in a FragmentTransaction
until it is committed and
attached to its activity.
If this Fragment is a child of another Fragment, the FragmentManager
returned here will be the parent's getChildFragmentManager()
.
public final FragmentManager getChildFragmentManager()
public final Fragment getParentFragment()
public final boolean isAdded()
public final boolean isDetached()
FragmentTransaction.detach(Fragment)
has been used on it.
public final boolean isRemoving()
public final boolean isInLayout()
public final boolean isResumed()
onResume()
and onPause()
as well.
public final boolean isVisible()
public final boolean isHidden()
onHiddenChanged(boolean)
. Note that the hidden state is orthogonal
to other states -- that is, to be visible to the user, a fragment
must be both started and not hidden.
public final boolean hasOptionsMenu()
public final boolean isMenuVisible()
public void onHiddenChanged(boolean hidden)
isHidden()
of
the fragment has changed. Fragments start out not hidden; this will
be called whenever the fragment changes state from that.
hidden
- True if the fragment is now hidden, false if it is not
visible.public void setRetainInstance(boolean retain)
onDestroy()
will not be called (but onDetach()
still
will be, because the fragment is being detached from its current activity).
onCreate(Bundle)
will not be called since the fragment
is not being re-created.
onAttach(Activity)
and onActivityCreated(Bundle)
will
still be called.
public final boolean getRetainInstance()
public void setHasOptionsMenu(boolean hasMenu)
onCreateOptionsMenu(Menu, MenuInflater)
and related methods.
hasMenu
- If true, the fragment has menu items to contribute.public void setMenuVisibility(boolean menuVisible)
menuVisible
- The default is true, meaning the fragment's menu will
be shown as usual. If false, the user will not see the menu.public void setUserVisibleHint(boolean isVisibleToUser)
An app may set this to false to indicate that the fragment's UI is scrolled out of visibility or is otherwise not directly visible to the user. This may be used by the system to prioritize operations such as fragment lifecycle updates or loader ordering behavior.
isVisibleToUser
- true if this fragment's UI is currently visible to the user (default),
false if it is not.public boolean getUserVisibleHint()
setUserVisibleHint(boolean)
public LoaderManager getLoaderManager()
public void startActivity(Intent intent)
Activity#startActivity(Intent)
on the fragment's
containing Activity.
public void startActivityForResult(Intent intent, int requestCode)
Activity#startActivityForResult(Intent, int)
on the fragment's
containing Activity.
public void onActivityResult(int requestCode, int resultCode, Intent data)
startActivityForResult(Intent, int)
. This follows the
related Activity API as described there in
Activity#onActivityResult(int, int, Intent)
.
requestCode
- The integer request code originally supplied to
startActivityForResult(), allowing you to identify who this
result came from.resultCode
- The integer result code returned by the child activity
through its setResult().data
- An Intent, which can return result data to the caller
(various data can be attached to Intent "extras").public LayoutInflater getLayoutInflater(Bundle savedInstanceState)
public void onInflate(Activity activity, AttributeSet attrs, Bundle savedInstanceState)
onAttach(Activity)
has been called; all you should do here is
parse the attributes and save them away.
This is called every time the fragment is inflated, even if it is being inflated into a new instance with saved state. It typically makes sense to re-parse the parameters each time, to allow them to change with different configurations.
Here is a typical implementation of a fragment that can take parameters
both through attributes supplied here as well from getArguments()
:
Note that parsing the XML attributes uses a "styleable" resource. The declaration for the styleable used here is:
The fragment can then be declared within its activity's content layout through a tag like this:
This fragment can also be created dynamically from arguments given at runtime in the arguments Bundle; here is an example of doing so at creation of the containing activity:
activity
- The Activity that is inflating this fragment.attrs
- The attributes at the tag where the fragment is
being created.savedInstanceState
- If the fragment is being re-created from
a previous saved state, this is the state.public void onAttach(Activity activity)
onCreate(Bundle)
will be called after this.
public Animation onCreateAnimation(int transit, boolean enter, int nextAnim)
public void onCreate(Bundle savedInstanceState)
onAttach(Activity)
and before
onCreateView(LayoutInflater, ViewGroup, Bundle)
.
Note that this can be called while the fragment's activity is
still in the process of being created. As such, you can not rely
on things like the activity's content view hierarchy being initialized
at this point. If you want to do work once the activity itself is
created, see onActivityCreated(Bundle)
.
savedInstanceState
- If the fragment is being re-created from
a previous saved state, this is the state.public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState)
onCreate(Bundle)
and onActivityCreated(Bundle)
.
If you return a View from here, you will later be called in
onDestroyView()
when the view is being released.
inflater
- The LayoutInflater object that can be used to inflate
any views in the fragment,container
- If non-null, this is the parent view that the fragment's
UI should be attached to. The fragment should not add the view itself,
but this can be used to generate the LayoutParams of the view.savedInstanceState
- If non-null, this fragment is being re-constructed
from a previous saved state as given here.
public void onViewCreated(View view, Bundle savedInstanceState)
onCreateView(LayoutInflater, ViewGroup, Bundle)
has returned, but before any saved state has been restored in to the view.
This gives subclasses a chance to initialize themselves once
they know their view hierarchy has been completely created. The fragment's
view hierarchy is not however attached to its parent at this point.
view
- The View returned by onCreateView(LayoutInflater, ViewGroup, Bundle)
.savedInstanceState
- If non-null, this fragment is being re-constructed
from a previous saved state as given here.public View getView()
onCreateView(LayoutInflater, ViewGroup, Bundle)
),
if provided.
public void onActivityCreated(Bundle savedInstanceState)
setRetainInstance(boolean)
to retain their instance,
as this callback tells the fragment when it is fully associated with
the new activity instance. This is called after onCreateView(LayoutInflater, ViewGroup, Bundle)
and before onViewStateRestored(Bundle)
.
savedInstanceState
- If the fragment is being re-created from
a previous saved state, this is the state.public void onViewStateRestored(Bundle savedInstanceState)
onActivityCreated(Bundle)
and before
onStart()
.
savedInstanceState
- If the fragment is being re-created from
a previous saved state, this is the state.public void onStart()
Activity.onStart
of the containing
Activity's lifecycle.
public void onResume()
Activity.onResume
of the containing
Activity's lifecycle.
public void onSaveInstanceState(Bundle outState)
onCreate(Bundle)
,
onCreateView(LayoutInflater, ViewGroup, Bundle)
, and
onActivityCreated(Bundle)
.
This corresponds to Activity.onSaveInstanceState(Bundle)
and most of the discussion there
applies here as well. Note however: this method may be called
at any time before onDestroy()
. There are many situations
where a fragment may be mostly torn down (such as when placed on the
back stack with no UI showing), but its state will not be saved until
its owning activity actually needs to save its state.
outState
- Bundle in which to place your saved state.public void onConfigurationChanged(Configuration newConfig)
public void onPause()
Activity.onPause
of the containing
Activity's lifecycle.
public void onStop()
Activity.onStop
of the containing
Activity's lifecycle.
public void onLowMemory()
public void onDestroyView()
onCreateView(LayoutInflater, ViewGroup, Bundle)
has
been detached from the fragment. The next time the fragment needs
to be displayed, a new view will be created. This is called
after onStop()
and before onDestroy()
. It is called
regardless of whether onCreateView(LayoutInflater, ViewGroup, Bundle)
returned a
non-null view. Internally it is called after the view's state has
been saved but before it has been removed from its parent.
public void onDestroy()
onStop()
and before onDetach()
.
public void onDetach()
onDestroy()
.
public void onCreateOptionsMenu(Menu menu, MenuInflater inflater)
setHasOptionsMenu(boolean)
. See
Activity.onCreateOptionsMenu
for more information.
menu
- The options menu in which you place your items.setHasOptionsMenu(boolean)
,
onPrepareOptionsMenu(Menu)
,
onOptionsItemSelected(MenuItem)
public void onPrepareOptionsMenu(Menu menu)
Activity.onPrepareOptionsMenu
for more information.
menu
- The options menu as last shown or first initialized by
onCreateOptionsMenu().setHasOptionsMenu(boolean)
,
onCreateOptionsMenu(Menu, MenuInflater)
public void onDestroyOptionsMenu()
onCreateOptionsMenu(Menu, MenuInflater)
was not called).
public boolean onOptionsItemSelected(MenuItem item)
Derived classes should call through to the base class for it to perform the default menu handling.
item
- The menu item that was selected.
onCreateOptionsMenu(Menu, MenuInflater)
public void onOptionsMenuClosed(Menu menu)
menu
- The options menu as last shown or first initialized by
onCreateOptionsMenu().public void onCreateContextMenu(ContextMenu menu, View v, ContextMenuInfo menuInfo)
view
is about to be shown.
Unlike onCreateOptionsMenu(Menu, MenuInflater)
, this will be called every
time the context menu is about to be shown and should be populated for
the view (or item inside the view for AdapterView
subclasses,
this can be found in the menuInfo
)).
Use #onContextItemSelected(android.view.MenuItem)
to know when an
item has been selected.
The default implementation calls up to
Activity.onCreateContextMenu
, though
you can not call this implementation if you don't want that behavior.
It is not safe to hold onto the context menu after this method returns.
public void registerForContextMenu(View view)
OnCreateContextMenuListener
on the view to this fragment, so
onCreateContextMenu(ContextMenu, View, ContextMenuInfo)
will be
called when it is time to show the context menu.
view
- The view that should show a context menu.unregisterForContextMenu(View)
public void unregisterForContextMenu(View view)
OnCreateContextMenuListener
on the view.
view
- The view that should stop showing a context menu.registerForContextMenu(View)
public boolean onContextItemSelected(MenuItem item)
Use MenuItem#getMenuInfo()
to get extra information set by the
View that added this menu item.
Derived classes should call through to the base class for it to perform the default menu handling.
item
- The context menu item that was selected.
public void dump(java.lang.String prefix, java.io.FileDescriptor fd, java.io.PrintWriter writer, java.lang.String[] args)
prefix
- Text to print at the front of each line.fd
- The raw file descriptor that the dump is being sent to.writer
- The PrintWriter to which you should dump your state. This will be
closed for you after you return.args
- additional arguments to the dump request.
|
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


s when elements are positioned against a parent element and are relative that parent image. A simple way to understand this by thinking of our solor system: all the planets are positions are relative to the position of the sun that is at the center of our solar system. Much like we know that the earth is the 3rd planet and always is, in any diagram it would maintain that position to the sun. Much like this the elements of a webpage (pictures, words, ect..) are placed in depending on the position of the main item on the page. In otherwords the "sun" item is the center and all the other items follow suit accordingly, if we moved the sun all the planets would follow suit in certain the prescribed order (Mercury, Venus, Earth, etc).
Relative position is the position of the element in regard to the page.An analogy of this would be similar to a young child that never leaves its mother's side. The mother can move anywhere in the home but the child is always on right side of the mother. He/she will never leave that position, but the child moves only if the mother moves. So if mom (primary element) goes to kitchen from the living room (scroll down to bottom of page) the child is always there on her left side (the element is always on prescribed position.)
This is elements are fixed relative to the browser window. So no matter where you go on the page the element will stay in the same space on the page. This is like many pop up adds that you find, no matter where you scroll the image is dead center unless you close the window. This window will be on top of all othe items on your page. So much like finding a scratch on your glasses, no matter where you look the scratch will be in the same position in your line of sight no matter where you turn your head.


Previous | Contents | Index | Next
You're given a grid, with several dots inside colored squares. Your objective is to fill every empty space with one of two colors while following these rules:
This puzzle type was invented by Inaba Naoki under the name クラスター, or literally Kurasuta, which Google Translate names 'Cluster'. The original puzzles are available here: http://www.inabapuzzle.com/honkaku/kura.html
Left-click to place blue squares. Right-click to place red squares. You can also click and drag to place multiple squares.
To play with a keyboard, use the arrow keys to move the cursor. Press Enter to place a blue square, and press Space to place a red square.
These parameters are available from the 'Custom...' option on the 'Type' menu.


Product Name
Short Name
Description
Fund
Start Date
Close Date
Is Include in customer loan counter ?


No boundaries have been discovered and the size is too big to be observed.
Physical exploration though is conducted both by unmanned robotic space probes and human spaceflight.
- It is costly (very very expensive!)
- It is still risky
A small mistake can lead to fatal accidents
Disasters like
Fuel to escape against Earth's Gravity
To Escape Earth's gravity, a rocket needs to fly at 11.2km/s
To get more speed a rocket needs more fuel
But more fuel means more weight and again increases the needed fuel
and all of them are only used to escape Earth's gravity
What if we re-use the materials instead of wasting them?
They are a private company!
Not a Government!


The game of Pig is pretty simple. Roll as many times as you want in a turn...but if you get a "1" (a Pig) you lose your turn (and any points earned in that turn). Your goal is to get to 100 points before the computer player (Comp) does. So roll away...then click on Hold when you are ready to let the computer play