Indigenous Australians have poorer cancer outcomes in terms of incidence mortality and survival compared with non-Indigenous Australians. The factors contributing to this disparity are complex. Identifying and addressing the psychosocial factors and support needs of Indigenous cancer patients may help reduce this disparity. The Supportive Care Needs Assessment Tool for Indigenous People (SCNAT-IP) is a validated 26-item questionnaire developed to assess their unmet supportive care needs. This qualitative study reports on patient and clinician attitudes towards feasibility and acceptability of SCNAT-IP in routine care.
Forty-four in-depth semi-structured interviews were conducted with 10 clinical staff and 34 Indigenous cancer patients with heterogeneous tumours. Participants were recruited from four geographically diverse Australian cancer clinics. Transcripts were imported into qualitative analysis software (NVivo 10 Software), coded and thematic analysis performed.
Indigenous patients (mean age 54.4 years) found the SCNAT-IP beneficial and easy to understand and they felt valued and heard. Clinical staff reported multiple benefits of using the SCNAT-IP. They particularly appreciated its comprehensive and systematic nature as well as the associated opportunities for early intervention. Some staff described improvements in team communication, while both staff and patients reported that new referrals to support services were directly triggered by completion of the SCNAT-IP. There were also inter-cultural benefits, with a positive and bi-directional exchange of information and cultural knowledge reported when using the SCNAT-IP. Although staff identified some potential barriers to using the SCNAT-IP, including the time required, the response format and comprehension difficulties amongst some participants with low English fluency, these were outweighed by the benefits. Some areas for scaled improvement were also identified by staff.
Staff and patients found the SCNAT-IP to be an acceptable tool and supported universal screening for Indigenous cancer patients. The SCNAT-IP has the potential to help reduce the inequalities in cancer care experienced by Indigenous Australians by identifying and subsequently addressing their unmet support needs. Further research is needed to explore the validity of the SCNAT-IP for Indigenous people from other nations.
Indigenous people comprise about five percent of the world's population . Inequalities with regard to Indigenous cancer outcomes have been documented in Australia, New Zealand, Latin America, the Caribbean and the United States [2–6]. In Australia, cancer remains the second leading cause of death among Indigenous people . The patterns of cancer care between Indigenous and non-Indigenous patients differ, with Indigenous patients often receiving less optimal treatment [8–10]. Indigenous Australians' engagement in cancer care is lower at all stages of the cancer continuum including screening, early presentation at diagnosis, continuity of care, and compliance with treatment [11–14]. This has resulted in significantly poorer cancer outcomes in terms of incidence, mortality and survival.
Aspects of the broader social environment may influence the way individuals, families and communities engage with health care and manage their own health . Understanding Indigenous people's experience of cancer must take into account the social determinants of health and the cultural context of people's lives, and these should be reflected in service delivery models and in the delivery of cancer care . Indigenous Australians' collective experience of racism, discrimination, alienation and marginalisation has led to widespread distrust of the health care systems including cancer care and treatment services [15, 17, 18].
It has been widely recognised that there is a lack of culturally appropriate health care services to engage Indigenous Australians [19–22]. Differences in communication, information needs and language have inhibited Indigenous people's engagement with cancer care [19, 23–25]. This issue is highlighted in a study that was conducted with cancer care professionals, where participants reported doubts about their ability to adequately communicate important information to Indigenous patients . Effective communication between patients and their physicians is essential to ensure optimal patient outcomes .
Furthermore, several studies have highlighted cultural differences in the way many Indigenous people perceive cancer (a highly feared disease that equates to death), receive and process information about their cancer diagnosis and treatment, and cope with illness [11, 27–29]. Research into the psychosocial factors and specific supportive care needs of Indigenous people with cancer is imperative.
Improved supportive care for Indigenous cancer patients is an important strategy which may ultimately help narrow current disparities in cancer outcomes.
Many questionnaires have been developed to assess the unmet needs of cancer patients . Some have been developed for specific cancers or settings, but little attention has been given to assessing the appropriateness of existing tools for minorities or developing tools that assess the culture-specific needs of different ethnic groups . In Australia, Indigenous cancer patients share many supportive care needs with non-Indigenous cancer patients, but they have additional culture-specific needs that are not addressed by existing measures . To address this gap, a Supportive Cancer Needs Assessment Tool for Indigenous People (SCNAT-IP) has been developed [31, 32].
The broader clinical implementation feasibility study has been reported elsewhere . While integrating qualitative and quantitative data can complement and deepen the interpretation of findings, we justify presentating the qualitative data separately on the basis of: (a) the paucity of research involving Indigenous cancer patients and in particular studies which explore unmet support needs; (b) the richness of the qualitative data; and (c) being able to illustrate the range and depth of participants needs and concerns in their own words rather than by a summary of themes. This study describes patient and staff attitudes towards the acceptability and feasibility of the SCNAT-IP in routine care. Additionally, this study aimed to identify refinements needed to prepare the SCNAT-IP for use in clinical settings.
Ethical clearance was obtained from the following Human Research Ethics Committees: Northern Territory (NT) Department of Health & Families and the Menzies School of Health Research (HREC13/1994); Peter MacCallum Cancer Centre (HREC/13/45); Greater Western Human Research Ethics Committee (HRECI131GWAHSI39) and the Aboriginal Health and Medical Research Council of New South Wales (NSW; HREC/946/12). The content of this manuscript was subject to approval by the Aboriginal Health and Medical Research Council of NSW in accordance with the standard conditions of their ethical approval.
Participants were recruited from one of four participating sites: a tertiary cancer centre in the NT servicing outer regional and remote areas; a large metropolitan tertiary cancer centre in Victoria; and two regional cancer clinics in NSW. These four services represented a diversity of geographical locations, service models and Indigenous communities. All participating sites had a relatively high proportion of Indigenous patients, and/or dedicated Indigenous hospital liaison staff or an interest in improving service delivery for Indigenous patients.
Eligible patients were over 18 years of age, of Australian Indigenous background, were diagnosed five years ago or less with malignant disease, and were either receiving or about to receive treatment (including surgery, chemotherapy, radiotherapy, stem cell transplant, endocrine therapy or immunotherapy) or were in follow-up care. Recruitment was conducted over a three to five month period (November 2013-March 2014). Interviews were verbally administered, and health care interpreters were available upon request by staff at the NT site where many Indigenous people speak a language other than English. Those unable to give informed consent due to cognitive and/or physical impairments were excluded. Eligible cancer nurses, oncology social workers, Indigenous health workers (IHWs) or other allied health professionals were identified by their manager as providing supportive care to cancer patients and invited to participate in the training for this study.
After written informed consent was obtained, all health professionals involved in this study completed a specifically developed three hour training session, which included background information, clinical use of the SCNAT-IP and the research protocol. Following training, all staff at participating sites were asked to identify and refer all eligible Indigenous cancer patients to trained clinical staff for needs assessment. Trained clinical staff (oncology social workers, nurses and clinical trials coordinators) introduced the study to patients, gained written informed consent and conducted needs assessment at routine patient clinic visits. Where moderate to high levels of needs were identified (i.e. scores of four or five on any SCNAT-IP item), these were discussed with patients and they were offered assistance in accordance with usual care.
Following needs assessment, patients, along with a trained clinical staff member, completed quantitative questionnaire items exploring the acceptability and feasibility of the SCNAT-IP; these results are reported elsewhere . Immediately following this, a trained IHW (or a trained clinical staff member if the IHW was unavailable), conducted an audiotaped face-to-face or telephone interview which aimed to gather qualitative information about patient attitudes towards unmet needs screening. Telephone interviews were offered for pragmatic reasons (e.g. when patients' transport was scheduled immediately after the completion of their appointment).
At the conclusion of the data collection period, trained clinical staff completed a brief telephone interview with a member of the research team (BT). Recruitment continued until no new themes emerged from the data. Patients' clinical details were collected by clinical staff from medical records.
Socio-demographic variables were collected by interview. Clinical details including cancer type, disease status, treatment phase, and cancer treatments were collected from medical records.
The SCNAT-IP is a 27-item (including one open-ended question) verbally-administered unmet needs measure. It consists of four domains: physical and psychological needs (11 items); hospital care needs (four items); information and communication needs (six items) and practical and cultural needs (five items). Items included but were not limited to the following: 'feeling tired, feeling down or sad' and 'keeping you strong in your spirit' (physical and psychological needs domain); 'having hospital staff show sensitivity to and respecting your feelings and emotional needs'; and 'being treated like a person not just another case or number' (hospital care needs domain); 'being shown or given information (e.g., written, diagrams) about how to manage your illness and side effects at home' (information and communication needs domain); and 'finding a place to stay while receiving treatment and money worries' (practical and cultural needs domain) .
For each item respondents report a yes/no response. If a need was present in the past month they were asked to choose the degree to which they required help on a scale ranging from 'satisfied because my needs were met' (scored as one) to 'a lot more help needed' (scored as five). To assist with comprehension, participants were given a hard copy of response categories and the interviewer recorded participants' responses . The SCNAT-IP accommodates the language, customs and culture-specific needs of Indigenous Australians and excludes items which are culturally-inappropriate in the screening context (e.g. sexual needs). The tool also includes culture-specific items such as having an Indigenous person to talk to and support you, someone who understands your culture . It takes approximately 15-20 min to complete and has been demonstrated to have good construct and face validity as well as internal consistency in a large sample of Indigenous cancer patients [31, 32].
A brief semi-structured face-to-face interview was used to qualitatively explore the participants' attitudes with regards to needs assessment. Interview questions explored perceived benefits of needs assessment, acceptability, appropriateness of content and timing, and attitudes towards universal screening for Indigenous patients.
Items were developed to assess demographic characteristics, role, education, employment location, years of experience and prior supportive care needs assessment training.
Six semi-structured interview questions assessed perceived benefits, barriers to use, impact on workload, impact on team communication/referral pathways, and recommendations for changes to the SCNAT-IP.
Demographic data were analysed using descriptive statistics. Interview audio recordings were transcribed verbatim. Data analysis was performed using QSR International's NVivo 10 Software . Thematic analysis was performed in six phases including: familiarisation with data; generation of initial codes; searching for themes among codes; reviewing themes; defining and naming themes; and synthesising the final results . The generation of coding was conducted by one member of the research team (BT), and verified by a second member of the research team (GG) who double-coded 10 % of transcripts to ensure inter-coder agreement. Where discrepancies arose in coding or definition of themes, these were resolved through discussion until consensus was reached.
Of the 89 potentially eligible participants, 45 (51 %) were invited to participate in the study. Thirty-six (80 %) of these agreed to be interviewed and two participants were further excluded leaving a final study sample of 34 (76 %) (Fig. 1).
Participants were aged 34-76 years (mean=54.4, SD=11.0) and the majority were female (68 %), partnered (53 %), living outside metropolitan cities (89 %) and had not completed high-school (60 %). Breast cancer was the most common cancer type (35 %); 31 % had local disease and 47 % were receiving active treatment (Table 1).
The SCNAT-IP study training session included 22 health professionals with an average age of 42 years (range 25-62, SD=11.4) and a diverse set of professional backgrounds including social workers (n = 8), nurse care coordinators (n = 4), radiation therapist (n = 1), clinical trial coordinator (n = 1), IHWs (n = 5) and service managers (n = 3). Ten of the 22 session participants conducted needs assessments using the SCNAT-IP. All were non-Indigenous females; six were oncology social workers; nine had post-graduate qualifications; and six had no previous needs assessment training. Half had six years or more experience in cancer care and worked in regional locations. The other 12 health professionals conducted follow-up interviews only or supported the study as service managers.
The results are reported for the combined group because participant views were common across genders, age groups, cancer types, cancer centres and mode of interview. Insufficient patients were interviewed by phone to formally explore whether the mode of interview influenced the results obtained.
The majority of participants liked being asked about their needs, did not mind taking the time to answer questions and generally found the process very helpful.
Another female participant reported feeling "empowered" by the process of needs assessment. Several participants appreciated that health professionals were interested in finding out about their needs and that they showed an interest particularly in the needs of Indigenous cancer patients.
Only one participant reported negative feelings about the SCNAT-IP, saying she felt "uptight" being asked about her unmet needs but later clarified "cause [I] told her [health professional] a few things that she didn't know." (Female, 55 years) Another participant did not find the process of needs assessment helpful because they had visited the centre many times in the last seven years, commenting "we're pretty well used to it", but further remarked "these sort of questions would have been more helpful in the beginning" (Male, 75 years).
Most participants found the tool very easy to understand and all liked the format of being asked the questions by health professional staff. No participants directly reported problems of comprehension.
This sample included patients at all stages of the treatment continuum, from diagnosis to follow-up care. Most participants reported being satisfied with the timing of the questionnaire, although several said it would have been more useful if completed earlier in their cancer journey.
However, a newly-diagnosed male participant suggested that SCNAT-IP assessment should not occur too soon after diagnosis because some subjects were "a bit touchy" because they were still coming to terms with the shock of their very recent cancer diagnosis.
Although most patients favoured early administration, there were diverse views about the ideal frequency, ranging from "once a week" or "every time I go in [to the cancer centre]" to "every six months" or "every [cancer treatment] stage". The majority of participants believed the SCNAT-IP assessment should be repeated throughout treatment.
All participants with moderate to high needs (n = 21, 58 %) were offered services to help address unmet needs and many reported experiencing benefits.
Many patients supported the idea of universal screening for Indigenous cancer patients noting that it would educate staff about Indigenous patient needs.
Others said it helped educate patients about what help is available to them and what to expect during treatment. Some participants believed needs screening should be optional to promote control and self-determination.
"Give 'em the choice, you know, 'cause a lot of 'em feel like they're already being controlled by other people in their lives as it is and they don't need, 'specially in a place like this, they don't need to get a view of it like 'okay here's another government organisation that's gonna be telling me what to do'".
Some participants without current unmet needs believed needs assessment was more worthwhile for others for altruistic reasons.
Whilst being generally satisfied with the SCNAT-IP and willing to complete it, some participants believed that for other Indigenous people needs screening is important because of cultural factors such as being "shy" and "a reluctance to talk about problems or articulate their needs".
Despite the SCNAT-IP being specific to Indigenous people, several participants said that SCNAT-IP would be relevant for all cancer patients irrespective of race. Two participants interviewed did not support universal screening for Indigenous people with cancer, one because she believed some questions were "too personal" and a second said he was "not sure" why.
Many staff said there were multiple benefits of the SCNAT-IP, including its comprehensiveness, its systematic approach to needs assessment and the opportunities for early intervention which other less formal assessments methods did not offer. Using the SCNAT-IP was also reported to help staff increase their awareness and identification of Indigenous patients in their clinic.
"It picks up things that I think would never have come up until we were at a real crisis point".
Several staff said it helped to build rapport, made patients feel "heard", and helped clarify patient expectations of services. Some staff reported they liked using an Indigenous-specific questionnaire because it fostered positive and collaborative relationships with Indigenous patients.
Staff also identified that using the SCNAT-IP helped educate staff members less familiar with working with Indigenous clients about culturally-specific needs and services.
The verbal format of the tool was seen as a distinct advantage over other written scales.
The most commonly identified barriers to using the tool were the time needed to arrange an appointment and to complete the interview at the patients' pace. SCNAT-IP interviews (including follow-up discussion of needs) lasted between 6 and 45 min with an average duration of 23 min.
"As much as we want to sit and have a really good yarn with people, having so many questions in it [the questionnaire]... it probably encourages them to yarn a lot more…I think there's the potential to be a lot of breaks in between the questions for yarning and you need to allow a bit more time".
Logistical problems were especially common for rural or remote patients because many attend clinics infrequently and have long travel times to consider, and this impacted on their ability to allow sufficient time to conduct the assessment.
Difficulties with comprehension of the tool were only reported at one site where many patients spoke an Indigenous language as their primary language. Despite health care interpreters being available upon patient or staff request at this site, many patients preferred to conduct interviews in English and relied on accompanying family members and/or staff to assist with translation.
Some staff reported that some patients had difficulty distinguishing between lower levels of need (e.g. 'a little more' versus 'some more' help), hence requiring further clarification by staff. Rapport building and allowing plenty of time to complete the interview were reported as having helped to reduce comprehension difficulties. Several staff also reported that some questions were not relevant to patients because of the time frame (i.e. 'in the past month') because of different patients' stages in the treatment trajectory (e.g. hospital items for newly-diagnosed patients).
Whilst one staff member identified a cultural tendency for Indigenous people to be private or reluctant to disclose personal information as a potential barrier to using the SCNAT-IP, another staff member saw the structured and direct nature of the tool as a benefit in this respect.
"Often in my experience Indigenous people are quite private and they'll say things are fine or they don't need any help but it's good actually having those questions as prompts."
The majority of staff said that completing the questionnaire took additional time but there were concomitant time savings because they had a better understanding of patient needs and could therefore provide early intervention.
Some staff reported it reduced their workload. Others said it increased workload but this was sometimes appraised in a positive way.
Experience using screening tools was reported to reduce the time required. One staff member believed the impact on workload would be less if the questionnaire were conducted at the time of initial service entry when other questionnaire information is routinely gathered.
Several benefits to team communication were reported by staff including improved communication with IHWs, and nursing and medical staff.
"helps the doctors here understand how they need to change the way they explain things to their Indigenous patients".
Making SCNAT-IP results available to nursing and medical staff in patient files was reported to facilitate better communication about patients' psychosocial needs. One staff member believed there were greater opportunities for the SCNAT-IP to have a positive impact on team communication if it were used early in the treatment trajectory.
Many staff reported that using the SCNAT-IP triggered new supportive care referrals. One clinician from a metropolitan hospital, who interviewed a number of patients from regional areas, observed that completing the SCNAT-IP increased her awareness of her need to better understand referral networks in regional areas. However, staff based in regional clinics observed little or no impact on referral pathways. This was attributed to the relatively small numbers of Indigenous patients who were assessed in those clinics and the fact that most of their patients were not newly-diagnosed and were already linked to local support services.
Several staff members suggested minor changes to the structure, wording or format of the SCNAT-IP tool including reducing the number of items, further simplifying the wording and modifying the response time frame (i.e. 'in the past month') to make it more applicable across the whole treatment continuum. It was also suggested to group items by domain and use domain headings to help clarify item content, as well as revise the preamble to clarify the purpose and response format (i.e. use of emoticons), and highlight the fact that some items were not relevant to all patients. More advice for staff members about the time required to complete the instrument and follow-up discussion about needs was also recommended. Contradictory views about who should complete the assessment were noted, with one staff member suggesting wider use, for example, by treating doctors or ward nursing staff, and another expressing reservations as to whether the medical or ward staff would be the best team members to assess and respond to unmet needs.
Overall patient acceptability of the SCNAT-IP was high, with the majority of participants finding the tool easy to understand. They liked the format and appreciated being asked by health professionals about their supportive care needs. These results are consistent with the results of a quantitative analysis of acceptability and feasibility in this sample . They also align with the results of patient and key informant interviews conducted during the development of the SCNAT-IP  and with past research that demonstrated the acceptability of the unmet needs assessment screening amongst the general Australian cancer population . Both patients and staff in this study believed SCNAT-IP assessment would be most useful early on in the treatment trajectory, with reassessment throughout treatment tailored to individual need.
Indigenous patients' cultural disconnection within the healthcare system is well documented [11, 24, 36] and the favourable results regarding the patient acceptability of the SCNAT-IP may simply have been due to health professionals taking more time to sit and talk with patients. However, our results indicate that it was more than this. Patients liked being asked about their supportive care needs in a structured manner and they reported the process was very helpful because this had not occurred prior to the implementation of the SCNAT-IP. The SCNAT-IP also provided health professionals with the means to have these discussions in a culturally appropriate format and they further commented that the tool picks up things they would not have identified if they were simply taking the time to sit and talk with the patient.
Basic infrastructure and logistical issues, such as lack of transport and suitable accommodation, are also reported to impede Indigenous Australians' access to cancer care and treatment services [11, 15, 23, 37]. The use of the SCNAT-IP is intended to assist health professionals to identify and subsequently address these important practical and logistical issues to improve access and uptake of cancer care.
Whilst this study provides additional evidence for the feasibility and acceptability of the SCNAT-IP, some staff identified comprehension difficulties amongst patients with low English literacy as a potential barrier. However, patients who spoke Indigenous languages at home did not report any comprehension difficulties . Reasons for this discrepancy are not clear. Although in most parts of Australia less than 10 % of the Indigenous population speak an Indigenous language at home (in the NT this figure rises to over 60 %) , language and literacy are commonly reported to be barriers to accessing health care and support services [24, 28]. These barriers may be due to Indigenous patients' lack of cancer knowledge and confidence in communicating with health professionals or navigating the health system, as well as cancer care professionals not tailoring their language to ensure that Indigenous patients fully comprehend their diagnoses, prognoses and treatment options [16, 39]. Given the verbal nature of the SCNAT-IP and the fact that most clinicians are non-Indigenous, health care interpreters are a preferred delivery method. Despite trained health care interpreters being available in this study they were under-utilised. Using family members as interpreters is not recommended practice when health communication is of a complex or sensitive nature because it can lead to serious misunderstandings . Our study did not formally assess participants' need for an interpreter or specifically explore the relationship between language spoken at home and time required to complete the instrument. Future studies should consider using more formal methods of assessing need for an interpreter and/or consider mandating use of trained health care interpreters for participants who primarily use Indigenous languages.
This trial included sites servicing Indigenous people living in metropolitan and regional areas, as well as those from remote communities. Our study did not assess geographical variations because participants residing in remote and metropolitan areas were under-represented in the sample. However, participants were recruited from four diverse cancer services which represented a range of geographical locations, service models and Indigenous communities. Our aggregated study data suggests that the SCNAT-IP is acceptable and feasible for use in a variety of service settings. Given the small number of participants from remote and very remote communities in this study, this finding should be interpreted with caution and further research involving those from remote and very remote communities is required. A number of Indigenous people were excluded from this study due to individual and system related issues such as patients not turning up for appointments, competing priorities, incorrect Indigenous status recorded on patient medical records, difficulties scheduling appointments and travel issues. These issues may represent unmet needs beyond the scope of this study and the SCNAT-IP, and could also be important in improving Indigenous patients' health outcomes. These individual and systemic issues affect Indigenous health more generally, but none-the-less impact on the delivery of cancer care and potentially the health outcomes of Indigenous Australians.
Although conducted in Australia and involving Indigenous Australians exclusively, this is the first qualitative study to explore feasibility and acceptability of an Indigenous-specific psychosocial screening tool. Further research is needed to explore the validity and possible adaption of the SCNAT-IP for other Indigenous groups.
An interesting and somewhat unexpected finding of this study was the inter-cultural benefits of the SCNAT-IP, with a positive and bi-directional exchange of information and cultural knowledge reported, potentially leading to improved inter-cultural collaboration and relationships that come from using a culture-specific tool like the SCNAT-IP. Whilst not the focus of this study, future studies should consider expanding study outcomes to include broader cultural benefits in addition to the more traditional service delivery outcomes and patient self-report measures which have formed the focus of many previous screening trials.
In considering the findings of this study some limitations should be acknowledged. First, although the study aimed to recruit all eligible Indigenous cancer patients seen during the study period, more than half of all potentially eligible Indigenous cancer patients were not invited to participate in this study for the reasons outlined above. Second, a small number of patients identified in medical records as being Indigenous did not self-identify as Indigenous when invited to the study. Third, inaccuracy of medical records to identify cancer patients of Aboriginal and Torres Strait Islander background may have influenced the results. Fourth, although the majority of participants had high levels of English fluency and did not require interpreters, it is likely that the routine use of interpreters amongst those who spoke Indigenous language(s) as their primary language would have increased the range and richness of responses for those patients. Fifth, the early onset of the wet season in the NT impeded patient transport from remote communities to the clinic, which reduced overall patient numbers during this trial. As a result we may have missed the views of those most marginalised and hardest to reach due to distance and other barriers not mentioned (cost, competing priorities). Finally, although the study intentionally included participants from a range of geographic areas, we acknowledge that further research is needed with larger numbers of participants from remote and metropolitan areas to ensure the generalisability of the findings. Despite these potential biases which may impact on validity, this study had a high recruitment rate and a relatively large sample size for qualitative studies.
This study confirmed the SCNAT-IP is applicable to both the research and clinical cancer care settings. For clinical purposes, our findings suggest that the SCNAT-IP should be used at a point early in the treatment trajectory with reassessment at subsequent time points dependent on individual patient need. Overall, the SCNAT-IP will greatly assist cancer care providers to identify Indigenous cancer patients' unmet needs and priorities for action. Further, it will also assist cancer care providers to assess the adequacy of their services in addressing patients' needs and identify areas for service improvement. Additional benefits include enhancing patient-provider communication and improving patients' experience and satisfaction with cancer care. Ultimately the goal is to bring about positive changes to patient management and improve cancer outcomes for Indigenous Australians.
This study provides further evidence for the feasibility and acceptability of the SCNAT-IP and its potential to help reduce the inequalities in cancer care experienced by Indigenous Australians. The results have led to minor modifications to the SCNAT-IP to enhance its clarity and suitability for use in a variety of settings. Strategies to promote and disseminate the SCNAT-IP are currently underway. Future studies should consider using more formal methods of assessing need for an interpreter and/or consider mandating use of trained health care interpreters for participants who primarily use Indigenous languages.
The authors wish to thank Mrs Margaret Lawton and Ms Celia Moore (Indigenous consumer representatives) and Dr Mick Adams for their assistance with developing training materials for this study. We also thank the Indigenous people with cancer and staff who participated in this study for their time and enthusiasm, including members of the SCNAT-IP Implementation Group: Andrea Franke, Janelle Parks, Ivan Gooloogong, Victoria Jones, Gwenda Stewart, Melissa Mudie, Jennifer Garner, Hamlata Bhana, Tegan Murnane, Annette Betharis, Fiona Wiseman, and Lucy Pollard.
This research was funded by a grant from the Lowitja Institute, Australia's National Institute for Aboriginal and Torres Strait Islander Health Research. This study was undertaken under the auspices of the Centre of Research Excellence in Discovering Indigenous Strategies to improve Cancer Outcomes Via Engagement, Research Translation and Training (DISCOVER-TT CRE, funded by the National Health and Medical Research Council #1041111). We also acknowledge the ongoing support of DISCOVER-TT by the Lowitja Institute. PCV was supported by an Australian Research Council Future Fellowship (#FT100100511). The views expressed in this publication are those of the authors and do not necessarily reflect the views of the funding agencies.
BT conceived and designed the research protocol and was primarily responsible for project management, data analysis, data interpretation, and drafted the manuscript. GG conceived and designed the research protocol and assisted in the data analysis, data interpretation, and drafted the manuscript. ED contributed to the design of the study and data entry. AG contributed to the design of the study. PCV contributed to the design of the study. KG, AH, VJ and DY contributed to the local project management and study coordination. VH provided critical guidance on the statistical component of the paper and the interpretation of data. All authors reviewed the draft, read and approved the final manuscript.
World Bank. Overview of Indigenous Peoples. (updated 30th March 2016, accessed 8th June 2016). Retrieved from http://www.worldbank.org/en/topic/indigenouspeoples/overview.
Moore SP, Soerjomataram I, Green AC, Garvey G, Martin J, Valery PC. Breast cancer diagnosis, patterns of care and burden of disease in Queensland, Australia (1998–2004): does being Indigenous make a difference? Int J Public Health. 2015. doi:10.1007/s00038-015-0739-y.


text:
-Trashlord, Run Forever, Looming, and Usury at Black Lodge in Seattle, WA.
-Bad Future, New Gods, Big Youth (First Show), and United Void somewhere in Seattle, WA.
-Dude York, Ever-So-Android, Mommy Long Legs, and Gutless at The Vera Project in Seattle, WA.
Thursday, January 21st, 2016
-The Exquisites, Great Grandpa, Dogs On Acid, Bad Future, and Itemfinder at Black Lodge in Seattle, WA.
Saturday, January 23rd, 2016
-Safe And Sound, Failure Pact, Deadwitch, Anti-Self, and Wake Of Humanity at Black Lodge in Seattle, WA.
-Camp, Littlefoot, California Redemption Value, and Night Cadet at Highline in Seattle, WA.
-Oblivion (Last Show), Of Feather And Bone, Gatecreeper, Lower Species, and Locke (First Show) at Real Art in Tacoma, WA.
Sunday, January 31st, 2016
-Moving On, Miscomings, and Division at Black Lodge in Seattle, WA.
-Casual Hex, Chroma, Crazy Bugs, and Newlyweds at Black Lodge in Seattle, WA.
-Whitney Ballen, Victor Simpson, and Little Bird at Everyday Music in Seattle, WA.
-Gag, Combat Knife, Power, Wreck, Odd Man Out, and Lower Species at Black Lodge in Seattle, WA.
-New Gods, Teen Death, Red Scare, Division, and It Follows (First Show) at Firewheel Community Coffeehouse in Everett, WA.
Sunday, February 21st, 2016
-Boyfriends, Great Spiders, and Nail Polish at Cha Cha Lounge in Seattle, WA.
Monday, February 22nd, 2016
-Julien Baker and Generifus at The Vera Project in Seattle, WA.
-American Football and David Bazan at Neptune Theatre in Seattle, WA.
-Power, Encourager, Red Scare, and The Loss at El Corazon in Seattle, WA.
-Champagne Babylon, Great Grandpa, The Pink Slips, and The Malady of Sevendials at Chop Suey in Seattle, WA.
-Mindset, True Love, Line Of Sight, Free At Last, and Great Reversals at The Sanctuary in Detroit, MI.
-Mindset, True Love, Line Of Sight, Free At Last, and Thought Crusade at Beat Kitchen in Chicago, IL.
-Mindset, True Love, Line Of Sight, Ancient Heads, Storm Clouds, and Zero at Anchored Social Club in Toronto, ON.
-Cruel Hand, Dead Weight, Mercy Ties, and These Streets at 924 Gilman in Berkeley, CA.
JON BUNCH MEMORIAL SHOW -Sense Field, Mean Season, Rocket From the Crypt, A Chorus Of Disapproval, Longfellow, Sederra, Texas Is The Reason, Outspoken, Into Another, The Aquabats, Scream, Samiam, The Bronx, Ignite, No For An Answer, Gameface, Death By Stereo, Strife, Knapsack, Red 5, Done Dying, Drumkan, Blood Days, Lidsville, Freewill, Sex Powers, and Visual Discrimination at Yost Theater in Santa Ana, CA.
-Self Defense Family, Culture Abuse, and New Gods at Funhouse in Seattle, WA.
Thursday, March 31st, 2016
-TacocaT (Record Release), Ononos, and Mommy Long Legs at Chop Suey in Seattle, WA.
Monday, April 4th, 2016
-Bane, Greg Bennick, Twitching Tongues, Axis, and Safe And Sound at El Corazon in Seattle, WA.
-Tau Cross, Genocide Pact, Drug Control, Dagger Moon, Krimewatch, and Bust Off at The Pinch in Washington, DC.
DAMAGED CITY FEST -Zero Boys, Systematic Death, Blood Pressure, Busted Outlook, Dame, and Stand Off at All Souls Unitarian Church in Washington, DC.
DAMAGED CITY FEST -Digital Octopus, Post Teens, Sem Hastro, Power, and Homosuperior at The Pinch in Washington, DC.
DAMAGED CITY FEST -Avengers, Sheer Mag, SHIT, Torso, Coke Bust, Youth Avoiders, La Urss, Protester, Caught In A Crowd, Firewalker, Depths of Reality, The Pessimists, Holders Scar, Firing Squad, and Collusion at Calvary Methodist Church in Washington, DC.
DAMAGED CITY FEST -Testa Dura, Eel, Triage, Rubbish, Stalled Minds, and Radiation Risks at The Pinch in Washington, DC.
DAMAGED CITY FEST -Gaucho, J.J. Doll, Flasher, and Zipper (First Show) at Open Studio DC in Washington, DC.
DAMAGED CITY FEST -Systematic Death, The Goons, Disguise, Odd Man Out, and Kombat at Black Cat in Washington, DC.
-Basement, Turnstile, Defeater, and Colleen Green at Chop Suey in Seattle, WA.
-Keep It Clear, Bill Conway, True Identity, Clarity, Vacant Life, and Division at Black Lodge in Seattle, WA.
-Slingshot Dakota, Moments, Where My Bones Rest Easy, Ramona, and Cliff Diver at Funhouse in Seattle, WA.
-Sem Hastro, The Pessimists, United Void, and Paranoid Time at Black Lodge in Seattle, WA.
-Sheer Mag, Lysol, Mysterious Skin, and Ubu Roi (Last Show) at Black Lodge in Seattle, WA.
-Red Scare, Safe And Sound, Hiding Place, and Division at Fusion Cafe in Seattle, WA.
REACT! SHOWCASE PRE-SHOW -Stand Off, Line Of Sight, Soft Grip, Bitter Taste, and Nerve Endings (First Show) at The Pinch in Washington, DC.
REACT! SHOWCASE -Mindset (Last Show), Give, Praise, True Love, Insist, True Identity, Break Away, Ancient Heads (Last Show), Free, Union Of Faith, WarxGames, and Stuck Pigs at St Stephen Church in Washington, DC.
-Sick Fix, DS-13, Iron Cages, Unknown Threat, and Brainpan at The Pinch in Washington, DC.
-Validation, Control Test, Macho Boys, and Lowest Priority somewhere in Seattle, WA.
Monday, May 23rd, 2016
-Cool Void, Sun Dummy, Tangler, and Gruft at Everyday Music in Seattle, WA.
RAINFEST -Black Breath, Weekend Nachos, Wreck, Criminal Code, Mysterious Skin, and Payback at Real Art in Tacoma, WA.
RAINFEST -No Warning, Blacklisted, Burn, Keep It Clear, Axis, Clarity (Last Show), Gouge Away, and Moving On at Neumos in Seattle, WA.
RAINFEST -Trapped Under Ice, Trash Talk, 108, Gag, Twitching Tongues, Fury, Red Scare, Gods Hate, Bent Life, Busted Outlook, Dead Weight, Losing End, Drug Control, Fell To Low, Mortality Rate, and Lower Species at Neumos in Seattle, WA.
RAINFEST -Power, Ill Intent, Down To Nothing, Stay Gold (Reunion), Indecision, Strain, Forced Order, Safe And Sound, Disgrace, New Gods, Vamachara, Discrepancy, Step 4 Change, Lysol, HIV (Surprise Song), Sunset Riders (Surprise Song), and Odd Man Out at Neumos in Seattle, WA.
Tuesday, May 31st, 2016
-The Hotelier, Told Slant, and Loone at The Vera Project in Seattle, WA.
-MxPx and Millencolin at Neumos in Seattle, WA.
-Angel Dust, Gag, Big Bite, and Lowest Priority at Funhouse in Seattle, WA.
-At The Drive-In and Le Butcherettes at Showbox SoDo in Seattle, WA.
SOUND AND FURY FEST -Down To Nothing, Guns Up, Shipwreck AD, Twitching Tongues, Angel Dust, Bracewar, Freedom, Gods Hate, Downpresser, Jesus Piece, Fell To Low, Regulate (Surprise Set), Blind Justice, Minus, Broken Teeth, Mizery, and Vamachara at Regent Theater in Los Angeles, CA.
SOUND AND FURY FEST -American Nightmare, Nails, Ceremony, Full of Hell, Tony Molina, Forced Order, Fury, King Nine, Criminal Instinct, Free, Take Offense, Gag, Creative Adult, Judiciary, Afflictive Nature (Surprise Song), and Bloodhound at Regent Theater in Los Angeles, CA.
TRIPLE B SHOWCASE -Freedom, Free, Response, and Warfare at The Smell in Los Angeles, CA.
-Bane, Title Fight, Modern Life Is War, Ceremony, The Promise, Defeater, and Right Brigade at The Palladium in Worcester, MA.
-Bane (Last Show), Saves The Day (Special Guest), Title Fight, Modern Life Is War, The Promise, Right Brigade (Last Show), Cruel Hand, and Rude Awakening at The Palladium in Worcester, MA.
-Odd Man Out, Wake Of Humanity (Record Release), and Lowest Priority at Black Lodge in Seattle, WA.
Saturday, July 2nd, 2016
-Pity Sex, PWR BTTM, Petal, and Great Grandpa at The Vera Project in Seattle, WA.
-J.J. Doll, Sterile Mind, and Private Room somewhere in Seattle, WA.
-Black Communion, Climate, and Fucking Awesome at Black Lodge in Seattle, WA.
Friday, July 22nd, 2016
-Pinegrove, Sports, Half Waif, and Great Grandpa at Black Lodge in Seattle, WA.
Saturday, July 23rd, 2016
-Power, Free At Last, Moving On, and Want at Fusion Cafe in Seattle, WA.
-La Luz, Great Spiders, and Mommy Long Legs at Chop Suey in Seattle, WA.
-G.L.O.S.S., Firewalker, Pure Disgust, and Lowest Priority at Black Lodge in Seattle, WA.
-Julien Baker and Justin Peter Kinkel-Schuster at The Vera Project in Seattle, WA.
-Odd Man Out, Stand Off, Line Of Sight, Lower Species, and Cutting Through somewhere in Seattle, WA.
-Drive Like Jehu and Hungry Ghost at Showbox in Seattle, WA.
-Sheer Mag, SSDD, Lysol, and Vacant Life at El Corazon in Seattle, WA.
-Dead Weight, Lowest Priority, Trust Issues, and Different Face at Fusion Cafe in Seattle, WA.
-Safe And Sound, The Real Cost, Crooked Cross, Lower Species, and Southworth at Fusion Cafe in Seattle, WA.
-Mommy Long Legs, Hoop , Kelli Frances Corrado, and SciFiSol Music at The Sunset in Seattle, WA.
-CHRCH, Mountain Man, Breag Naofa, and Screaming Skull at Funhouse in Seattle, WA.
-Himsa, Pinned Red, Lowest Priority, Wake Of Humanity, and Die Young at El Corazon in Seattle, WA.
Monday, October 31st, 2016
GET YOUR FREAK ON! -DoNormaal, Matriarch, Lowest Priority, and Male/Female at Southgate Roller Rink in Seattle, WA.
-Caspian and The Appleseed Cast at Neumos in Seattle, WA.
-Descendents, Bully, and Broadway Calls at Neptune Theatre in Seattle, WA.
-The Exquisites (Record Release), Hiding Place, Dangers, and Churn at Black Lodge in Seattle, WA.
-Daughters, The Body, and Loma Prieta at Highline in Seattle, WA.
-Gag, Ill Intent, Odd Man Out, Lower Species, and No Dice at Black Lodge in Seattle, WA.
-Kevin Devine, Pinegrove, and Petal at Chop Suey in Seattle, WA.
-Chastity Belt, Malidont, and Versing at Chop Suey in Seattle, WA.
-Rocky Votolato somewhere in Seattle, WA.
-Lowest Priority, Cloaca, Ziptie, and No Dice at Cockpit in Seattle, WA.
-G.L.O.S.S. (Last Show), Lowest Priority, Xylitol, Franky, and Deep Trench at Eagles Ballroom in Olympia, WA.
-Sun Dummy and Whitney Ballen somewhere in Seattle, WA.
-Great Grandpa, Snuff Redux, and Familiars at Barboza in Seattle, WA.
-United Void, Ignorant, Health Scare (First Show), and Lowest Priority at Black Lodge in Seattle, WA.
Thursday, December 22nd, 2016
-Therefore I Am (Reunion), Actor Observer, and The Heavies at The Sinclair in Cambridge, MA.

redpajama_set_name: RedPajamaCommonCrawl


text:
Why doesn't elementary OS include an Office suite?
Why doesn't elementary OS include an office suite by default? You can find a reference to the issue here.
Its already over 700 MB so why don't they add a another 100 MBs and provide an office suite such as Libre Office?
Are they not happy to the interface of the office suites that are there in the market, (suggesting they are building their own)?
applications office
Daniel Foré
Aditya ultraAditya ultra
and elementary is well over 700mb so it can't fit on a standard CD
– Aditya ultra
Current Stance
The official stance currently that they don't really need a full suite themselves, nor do they want to ship an office suite that isn't theirs. Until then, there are several third party options (see below). For my personal opinions, taking the near-ubiquitous Microsoft Office as an example, it comes with:
Each of these require individual analysis, so let's get to it.
The writing application is probably the most conventional piece of software, and yet surprisingly rarely used. Simple documents are written occasionally, but not regularly enough that it was a major issue this cycle, although it has been looked at by the community (see below), the issue of compatibility (which permeates this question) will no doubt rear its ugly head.
Spreadsheets are commonly used in the workplace, but far less at home (unless you log every transaction you make, like some kind of weirdo), and elementary is definitely not targeted at the business market right now. Definitely not a priority.
Another predominantly business application, and certainly something home users (if not everyone, who likes those meetings?) could do without.
I'm not entirely sure what OneNote does, but it isn't used on any of the hundreds of machines I administer. It seems to be searchable sticky notes, and it's been opened 3 times by people so far this year, 2 were auto-launching at startup, and one was because they were curious what it did.
I have two things to say about this:
The only use for desktop mail as far as I can tell is for reading or composing (but not sending) while offline. As we rapidly move towards always-online (I personally am very rarely without an internet connection, and certainly don't want to be composing emails during those times), they become more and more defunct.
We have Geary for this, a technically-third-party-but-built-with-elementary-in-mind piece of software.
Yet another "business" application, back in the days where you needed to design leaflets and posters, I think this is mostly a bygone as well, plus extremely specialist, speaking of which..
Access is a format for what is effectively a proprietary version of SQLite, a is a system often employed for quick-and-easy databases that rapidly move into multi-user territory that it is simply not designed for. A poorly defined piece of technology is worse that a buggy piece of technology, and most users will have no user for this. Microsoft do not even include this in most Microsoft Office versions.
Many people seem not to know this, but Microsoft provide free online versions that do almost as much as local ones do, notably lacking macros but not much else.
Paid upgrades and subscriptions available. Requires a Microsoft account.
Google provide a wide array of tools for working with documents, spreadsheets, and slideshows and support converting to and from Microsoft Office format, and is now being recommended by some universities. A major upside is you don't need to install or even save things, it's all just online.
Google Apps is paid and provides more features, but nothing noticeable and it doesn't bug you to upgrade.
LibreOffice has come to be the de-facto option for open-source office tools, and for very good reason. If you want offline software, with the option of theming it's way into elementary, this is the one for you.
Kingsoft Office 2013 is very Microsoft Office like, but alphas are available for native linux use and provide reasonably good compatibility, but very little elementary tie-in.
Designed for elementary OS
There is a great mockup for a Writer on Deviantart by spiceofdesign that is absolutely gorgeous, and did have some code written as a third-party application, but was never official. There's been nothing done there for a couple of months, but it seems to have a significant amount of the groundwork laid.
Robert Cartaino
Lewis Goddard♦Lewis Goddard
Great answer! One suggestion: LibreOffice will become available as an online version in the beginning of 2016 (source). You might want to squeeze that in your answer. P.S. OneNote is an alternative to Evernote with similar features.
– r3bl
nice answer made me clear my confusion
Hope writer comes up stable quickly, looks neat and fast
elementary's policy is to ship default apps that comply with their design guidelines, which integrate with the desktop environment in the smoothest possible way.
None of the office suites out there - and certainly not Libre Office - do that, so it only makes sense not to include any office application by default and let the users free to install the one that best suits their needs.
Developing their own office suite is not something which can be accomplished in the foreseeable future, since that would take a lot more workforce that they can currently afford.
Giulio SantGiulio Sant
do you have a source with a official statement?
– davidak
so can they redesign the libre office to match style guides??
@davidak: I don't think there is any, not that you need one for that matters. It's just a choice of the devs. Anyway, with my answer I'm pretty sure I'm kind of quoting Daniel Fore's thought on the issue which he has stated several times in the G+ community.
– Giulio Sant
@Adityaultra: Who do you mean with 'they'? The elementary devs? I don't think they want go through the hassle, I'm afraid there are technical inconsistencies between LO's interface and what elementary uses. But I'm no expert in this field, maybe Daniel or someone else can pitch in. I know there have been attempts in the past to provide an "elementarish" theme for LO, but it was nothing reliable or truly consistent.
@Adityaultra You cannot simply "theme" something into being good design. LibreOffice comes with far too many hardcoded options to ever truly be elementary. Anything like that would need to be a totally custom frontend, although hopefully some libraries can be shared.
– Lewis Goddard ♦
Not the answer you're looking for? Browse other questions tagged applications office or ask your own question.
Wine opens "Wine application loader" instead of Microsoft Word
Can't play sound in WPS Office Presentation (Freya)
Set MS Office as predefined
elementary os loki pantheon mail with Office 365
Why doesn't the Application dohicky install the latest software version?
The Microsoft Suite is supported? or onedrive?


Designed by John Roshell and Bryan Talbot The lettering style of Lancashire's finest comic book artist, graphic novelist and NEMESIS deviant Bryan Talbot is finally at your beck and call thanks to the good graces of those awfully nice chaps at Comicraft. Created for Bryan's magnum opus, ALICE IN SUNDERLAND, the Bryan Talbot font will take you on a journey into delirium, through the looking glass of British underground comix into the complex world of experimental narrative techniques and bestow upon you semi- legendary cult status and prestigious awards from no less than the New York Times.* *Results may differ if you are not actually Bryan Talbot.
Bryan Talbot Lower Bold Italic in Typecast testen.


Ratings: 7.27/10 from 82 users.
This program exposes the history of the Carlyle Group, from it's inception as a private equity firm to it's precent status as one of the largest defense contractors in the world.
Good vid. It's Disgusting how nonchalant these one presenters are. The destruction and Murders of hundreds of thousands of not millions of innocent people. All in the name of a buck. Wouldn't it be a perfect world if you drop Bush his cabinet and the Carlyle group in downtown Iraq. Tell its citizens these are all the people who caused me this mess.
Do not take the law into your own hands.Make your appeals to the judicial arms of the governments.
Because that's what we need more goverment? That is why we are spiraling downward as a country is the goverment...no people need to be taking matters into their own hands. I have to agree with Brian's idea.
A great documentary that exposes the political, military, and financial connection between U.S leaders, and the corporations that profit from the American taxpayers support. Although much of this information is already out there for those who make a point of paying attention to the world around them, sadly it remains unknown to the majority who are distracted by political party propaganda.
What is more disconcerting is how many innocent people pay the price in countries that refuse to play ball with the IMF, and World bank, who sanction this corrupt behaviour.
P.S: The idea that if the people knew the truth, the Bush/Cheney's of the world would never be elected is to me ridiculous. Even if the people knew, they would still support it, because to rail against it, would only increase their personal risk, and bring financial hardship to them, and their families. Ultimately, it boils down to a simple concept.
I would like to know how the Bush family can hug their grandkids with bloody hands. They will leave their fortune to their grandkids, made by the deaths of thousands upon thousands of people .
I for see the Bush family burning in Hell for what they have done to America and the World, how many people have died so they can make MONEY.
As many as they found necessary to kill.
One thing's certain, there will always be wars. Out of chaos come order, and symmetry. Just as forest fires are crucial to restoring vitality, and the big bang resulted in the beautiful spiral dance of the universe, so to have the struggles and strife in our history done for man kind. There will be balance, that is the nature of everything.
The first 1:45 is in German. I almost stopped watching this until I skipped ahead and realized it switches to english.
After watching this how can people say they want capitalism unregulated? This is exactly what you have to look forward to, except it will not be hidden and there will be much more of it. Not to mention the offenses that would take place right here at home. The current system isn't perfect, it allows many corrupt practices. But if you remove it things will get tremendously worse. You don't throw your car away when it has a flat, you fix it. This is the same thing, you don't throw away your government or regulatory system because it is broken, you fix it. Or we can sit back and expect the huge corporations to put people before profit, country before short term gain, etc. Now do you really think that is going to happen? If so I have a nice bridge you might be interested in, I'll even throw in some nice ocean front property in Tennessee!
Corporations always put profit ahead of people. They exist to profit those that own and run them. They do not care about people or society, unless they negatively impact business.
Pure capitalism without regulation is a recipe for disaster. The US is quickly headed down that path. The GOP passed and SCOTUS upheld Citizens United. IT is a bill that literally sold the US to the highest bidders.
Those that vote for the GOP are either rich or insane. Yes. The Dems are also out to enrich themselves, but they at least have a little compassion for the poor and middle class.
The GOP congress is auctioning off favors for cash and future jobs for themselves. You don't need to look any further than the very first bill (after the GOP took the majority in Congress) that they brought up and passed. Keystone.
Keystone does nothing good for the US but will enrich Koch. The Koch brothers funded the elections for a good portion of the GOP. Keystone is a blatant payback.... and they are not even ashamed to let people see what they are doing.
how many times does your car have to break down or malfunction till you realize you need a new car?
Yep. In car-speak, capitalism is "a lemon".
Actually the big corporations benefit from the regulation. They are the ones putting these people in office. If they can weed out competition by being the only ones who have the resources to hire the teams of lawyers in order to navigate all the rules that their puppets put in place then competition goes out the window.
Blood money ! The only reason that our troops & hundreds of thousands of civilians are dying in the Iraq & Afghanistan wars is to make money for the Carlyle group, Of which the Bush, Blair, Bin Laden & Saudi Royal families are all major shareholders. 9/11 & 7/7 were both staged to justify these wars & allow the Carlyle group to make many billions of $'s for these shareholders, through defence contracts, arms deals & rebuilding contracts. Al Qaeda & Saddam's WOMD were both invented by these people, again to justify these same wars. And who will be the only people who will benefit from these wars, yes you've guessed it, the shareholders & paid employees of the Carlyle group & other such companies.
Yes the reporters weren't looking for the truth. But they also were embedded and only saw what the US military wanted them to. That is why the US blew up the Al-Jazerra offices and TV station there to stop unapproved media stories because the weren't embedded.
It is very clear that all the nations work together in their corruption and deception and is driving by the greed of materialistic things that are ultimate valueless. It's very sad that many people have to suffer for the gain of few. The rich get richer and the poor get poorer but everyone shares the same faith. Jehovah will sort out the bad from the good at heart and only time will tell who receives salvation. The world has been a place of siege and conquest since the beginning of time and won't end until Judgement Day.
Rather than being completely critical and stacking favour against the subject of the documentary.
Why do Americans love War so much? I've been asking myself that question for a long time.
I've done my fair share of research and their seems to be a lot of 'conclusions' if you will.
Americans originally came from Europe. The Brits and the French. 2 Nations that have always been war mongers... back when proving your strength actually meant something.
I suppose that is the core of it?
I guess we'll never really know why, but I hope someday the Americans will stop causing fear in the world. They seem to be greatly afraid of 'something' themselves.
Screw defense and military spending. They should spend that money on saving the planet from our stupidity, and more unbiased religious based Science.
It's probably best that you don't assume ALL Americans LOVE war. That's a ridiculous claim. Sure our government gets us involved in plenty of wars, and yes, a lot of us support these wars as a result of the propaganda they feed us to fear for our lives and defend ourselves. However, that general statement you just made is the same ignorant nonsense that puts you on the wrong end of the barrels of our guns. We, the American people, do not make the decisions, press the red buttons, or give the orders to the military.
Furthermore, you say that you've done your "fair share of research" and come to the conclusion that since we're descendants of Europe, we have inherited the trait of being war mongers. Well that is extremely sad to hear that you did a fair share of research and came to such a simple conclusion. My 10-year old niece knows where we descended from moron, so please come up with something better than that ridiculous assumption, detective.
bravo! lol thanx for settin the record straight joe. the world would be a much different place if ppl like the bush family listened and carried out the voice of the american ppl, we didnt elect that goofy looking, word makin up, dumb f*** known as W.!
Frostbeard: See? All you did was offer a theory as to why Americans love fighting and he said that's how we end up threatening or shooting people with guns! The reactions are so disproportionate to the offense in many cases. Now he's going to be all irate at me for pointing something out that is obvious to everyone who reads his and your statements. You don't even have to look elsewhere for an example. It's right above this post.
Joe: You know you love that the USA is the most powerful country in the world. Why the charade? You clearly enjoy having the power to brandish gun barrels at whomever you see fit. Just admit it already.
Americans don't love war. The power behind the American Government (the military industrial complex) loves war. War is profit.
Eisenhower warned us about them. The Military Industrial Complex... made up of ex-world leaders and captains of industry (so, basically, criminals). They need war to survive.
The US citizens are brainwashed by their media which is owned and controlled by people who want to influence US foreign policy so the US fights the people and countries who the media owners either don't like or want to control or take over. The media is also influenced by weapons manufacturers and the service companies that get huge contracts for things like doing the military's laundry, cooking, logistics, private security contractors etc.
I first came to know the Carlye Group in a Pol Sci class in 2001. Right after the "inside job" of 9/11, I was told by the instructor that I was not to write my final essay on the fact the Bushes' sat with the Saudi as the event took place. She informed me that "The Carlye Group was not a topic of the semester, and to relate the essay to topics on the "listed." They make the gun that make the wars that make the profits. Isn't that the "Good Old Party's" method of operations. Like the instructor of the class(forgot her name), the media (owned by The Carlye Group) misinforms the public to focus on "the list." I did the paper on discrimination in education and got an A-. But the satisfaction was the look on her face when knew I had seen beyond the "list."
Living in a Capitalist regime, OR NOT, does not change the fact that if you are in a position to use, deceive and do harm to innocent unsuspecting folks for personal or ideological gain - you better be ready to pay for it - period!
And 'forests', need nurturing. Because the 'trees' depend upon its biodiversity and "balance" for survival. Nothing to do, or helped by: greed, apathy, megalomania and pretentiousness from our so-called 'leaders' and their rebelling 'acolytes' who claim to speak for the 'people'...where in some camps, some have even, suddenly, discovered a taste for 'tea'!
ehhhh little to no substance. we live in a capitalistic country; thats not some big secret conspiracy.
don't overlook the forest for the trees, people!
WOW! I love this site. EXCELLENT work guys.
This is must see. 98% English w/Dutch subtitles.
It is in Enlish. It just starts off in Dutch.
It's about a conspiracy between politicians and business groups, it's true but it is about a conspiracy.
Why is this documentary in the Conspiracy section ?
This is a very important documentary! It is not in English for the first few minutes, but wait...the rest is in English. It is a must see if you want to understand the relationship of the Bush family and the Carlyle group. This film uses very reputable sources.
Is there and english language version of Iron Triangle? What is the link to it?


text:
Q: accessing data within nested structures I am writing a function that prints out a hash table, the structure for this
 hash table is
     vector< list < Entry > > and the definition of Entry is struct Entry { string key, desc; unsigned num; }; however I am getting errors when i compile this code...
void HT::hTable_print ( )
{
        bool lastempty = false;
        for(unsigned int i = 0; i < hsize; i++){
                list<Entry>& l = hTable[i];
                if(!l.empty()){//if list isnt empty
                        for(unsigned int x = 0; x < l.size();x++){//loop through list
                                if(lastempty){
                                        cout << endl;
                                }

                                Entry e = l.front()+x;
                                cout << setw(4) << x << ":  " << e.key << " - "
                                << setw(5) << e.num << "   -  " << e.desc
                                << endl;

                        }
                        lastempty = false;
                 }else{
                        lastempty = true;
                }

        }
}

I am trying to loop through the vector and allocate each list element to a variable and then loop through that list printing out the necessary information but I will get errors when I call e.key e.num and e.desc. How do i properly call the information for each Entry structure?
EDIT: Heres a few of the errors I receive when compiling:
hTable.cc:69:24: error: no match for 'operator+' (operand types are '__gnu_cxx::__alloc_traits<std::allocator<Entry> >::value_type {aka Entry}' and 'unsigned int')
     Entry e = l.front()+x;

/usr/include/c++/7/bits/stl_iterator.h:397:5: note:   template argument deduction/substitution failed:
hTable.cc:69:25: note:   mismatched types 'const std::reverse_iterator<_Iterator>' and 'unsigned int'
     Entry e = l.front()+x;
                     ^
/usr/include/c++/7/bits/stl_iterator.h:1198:5: note:   template argument deduction/substitution failed:
hTable.cc:69:25: note:   mismatched types 'const std::move_iterator<_IteratorL>' and 'unsigned int'
     Entry e = l.front()+x;
                         ^

A: Notice how std::list::front() returns a reference to the first element in list. What you want to do is to take std::list::begin() to have an advancable iterator, std::advance() it and then dereference it:
list<Entry>::const_iterator iter = l.begin();
advance(iter, x);

const Entry& e = *iter;

Or, as per suggestion in the comments, iterate the list via iterators in the first place
unsigned int x = 0;
for (const auto& e : l) {//loop through list
   ++x;
   // .... stuff ...
}

redpajama_set_name: RedPajamaStackExchange


text:
package org.usergrid.rest.applications;

import static org.usergrid.services.ServiceParameter.addParameter;
import static org.usergrid.services.ServicePayload.batchPayload;
import static org.usergrid.services.ServicePayload.idListPayload;
import static org.usergrid.services.ServicePayload.payload;
import static org.usergrid.utils.JsonUtils.mapToJsonString;
import static org.usergrid.utils.JsonUtils.normalizeJsonTree;

import java.text.SimpleDateFormat;
import java.util.ArrayList;
import java.util.Date;
import java.util.List;
import java.util.Map;
import java.util.UUID;

import javax.ws.rs.Consumes;
import javax.ws.rs.DELETE;
import javax.ws.rs.DefaultValue;
import javax.ws.rs.GET;
import javax.ws.rs.POST;
import javax.ws.rs.PUT;
import javax.ws.rs.Path;
import javax.ws.rs.PathParam;
import javax.ws.rs.Produces;
import javax.ws.rs.QueryParam;
import javax.ws.rs.core.Context;
import javax.ws.rs.core.MediaType;
import javax.ws.rs.core.MultivaluedMap;
import javax.ws.rs.core.PathSegment;
import javax.ws.rs.core.UriInfo;

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.context.annotation.Scope;
import org.springframework.stereotype.Component;
import org.usergrid.persistence.AggregateCounter;
import org.usergrid.persistence.AggregateCounterSet;
import org.usergrid.persistence.Entity;
import org.usergrid.persistence.Query;
import org.usergrid.rest.AbstractContextResource;
import org.usergrid.rest.ApiResponse;
import org.usergrid.rest.security.annotations.RequireApplicationAccess;
import org.usergrid.services.ServiceAction;
import org.usergrid.services.ServiceManager;
import org.usergrid.services.ServiceParameter;
import org.usergrid.services.ServicePayload;
import org.usergrid.services.ServiceRequest;
import org.usergrid.services.ServiceResults;

import com.sun.jersey.api.json.JSONWithPadding;
import com.sun.jersey.core.provider.EntityHolder;

@Component
@Scope("prototype")
@Produces({ MediaType.APPLICATION_JSON, "application/javascript",
		"application/x-javascript", "text/ecmascript",
		"application/ecmascript", "text/jscript" })
public class ServiceResource extends AbstractContextResource {

	private static final Logger logger = LoggerFactory
			.getLogger(ServiceResource.class);

	protected ServiceManager services;

	List<ServiceParameter> serviceParameters = null;

	public ServiceResource() {
	}

	@Override
	public void setParent(AbstractContextResource parent) {
		super.setParent(parent);
		if (parent instanceof ServiceResource) {
			services = ((ServiceResource) parent).services;
		}
	}

	public ServiceResource getServiceResourceParent() {
		if (parent instanceof ServiceResource) {
			return (ServiceResource) parent;
		}
		return null;
	}

	public ServiceManager getServices() {
		return services;
	}

	public UUID getApplicationId() {
		return services.getApplicationId();
	}

	public List<ServiceParameter> getServiceParameters() {
		if (serviceParameters != null) {
			return serviceParameters;
		}
		if (getServiceResourceParent() != null) {
			return getServiceResourceParent().getServiceParameters();
		}
		serviceParameters = new ArrayList<ServiceParameter>();
		return serviceParameters;
	}

	public static List<ServiceParameter> addMatrixParams(
			List<ServiceParameter> parameters, UriInfo ui, PathSegment ps)
			throws Exception {

		MultivaluedMap<String, String> params = ps.getMatrixParameters();

		if (params != null) {
			Query query = Query.fromQueryParams(params);
			if (query != null) {
				parameters = addParameter(parameters, query);
			}
		}

		return parameters;

	}

	public static List<ServiceParameter> addQueryParams(
			List<ServiceParameter> parameters, UriInfo ui) throws Exception {

		MultivaluedMap<String, String> params = ui.getQueryParameters();
		if (params != null) {
		    //TODO TN query parameters are not being correctly decoded here.  The URL encoded strings
		    //aren't getting decoded properly
			Query query = Query.fromQueryParams(params);
			if (query != null) {
				parameters = addParameter(parameters, query);
			}
		}

		return parameters;

	}

	@Path("{entityId: [A-Fa-f0-9]{8}-[A-Fa-f0-9]{4}-[A-Fa-f0-9]{4}-[A-Fa-f0-9]{4}-[A-Fa-f0-9]{12}}")
	public AbstractContextResource addIdParameter(@Context UriInfo ui,
			@PathParam("entityId") PathSegment entityId) throws Exception {

		logger.info("ServiceResource.addIdParameter");

		UUID itemId = UUID.fromString(entityId.getPath());

		addParameter(getServiceParameters(), itemId);

		addMatrixParams(getServiceParameters(), ui, entityId);

		return getSubResource(ServiceResource.class);
	}

	@Path("{itemName}")
	public AbstractContextResource addNameParameter(@Context UriInfo ui,
			@PathParam("itemName") PathSegment itemName) throws Exception {

		logger.info("ServiceResource.addNameParameter");

		logger.info("Current segment is " + itemName.getPath());

		if (itemName.getPath().startsWith("{")) {
			Query query = Query.fromJsonString(itemName.getPath());
			if (query != null) {
				addParameter(getServiceParameters(), query);
			}
		} else {
			addParameter(getServiceParameters(), itemName.getPath());
		}

		addMatrixParams(getServiceParameters(), ui, itemName);

		return getSubResource(ServiceResource.class);
	}

	public ServiceResults executeServiceRequest(UriInfo ui,
			ApiResponse response, ServiceAction action, ServicePayload payload)
			throws Exception {

		logger.info("ServiceResource.executeServiceRequest");

		boolean tree = "true".equalsIgnoreCase(ui.getQueryParameters()
				.getFirst("tree"));

		addQueryParams(getServiceParameters(), ui);
		ServiceRequest r = services.newRequest(action, tree,
				getServiceParameters(), payload);
		response.setServiceRequest(r);
		ServiceResults results = r.execute();
		if (results != null) {
			if (results.hasData()) {
				response.setData(results.getData());
			}
			if (results.getServiceMetadata() != null) {
				response.setMetadata(results.getServiceMetadata());
			}
			Query query = r.getLastQuery();
			if (query != null) {
				query = new Query(query);
				query.setIdsOnly(false);
				if (query.hasSelectSubjects()) {
					response.setList(query.getSelectionResults(results));
					response.setNext(results.getNextResult());
					response.setPath(results.getPath());
					return results;
				}
			}
			response.setResults(results);

		}

		httpServletRequest.setAttribute("applicationId",
				services.getApplicationId());

		return results;
	}

	@GET
	@RequireApplicationAccess
	public JSONWithPadding executeGet(@Context UriInfo ui,
			@QueryParam("callback") @DefaultValue("callback") String callback)
			throws Exception {

		logger.info("ServiceResource.executeGet");

		ApiResponse response = new ApiResponse(ui);
		response.setAction("get");
		response.setApplication(services.getApplicationId());
		response.setParams(ui.getQueryParameters());

		executeServiceRequest(ui, response, ServiceAction.GET, null);

		return new JSONWithPadding(response, callback);
	}

	@SuppressWarnings({ "unchecked" })
	public ServicePayload getPayload(Object json) {
		ServicePayload payload = null;
		json = normalizeJsonTree(json);
		if (json instanceof Map) {
			Map<String, Object> jsonMap = (Map<String, Object>) json;
			payload = payload(jsonMap);
		} else if (json instanceof List) {
			List<?> jsonList = (List<?>) json;
			if (jsonList.size() > 0) {
				if (jsonList.get(0) instanceof UUID) {
					payload = idListPayload((List<UUID>) json);
				} else if (jsonList.get(0) instanceof Map) {
					payload = batchPayload((List<Map<String, Object>>) jsonList);
				}
			}
		}
		if (payload == null) {
			payload = new ServicePayload();
		}
		return payload;
	}

	@POST
	@RequireApplicationAccess
	@Consumes(MediaType.APPLICATION_JSON)
	public JSONWithPadding executePost(@Context UriInfo ui,
			EntityHolder<Object> body,
			@QueryParam("callback") @DefaultValue("callback") String callback)
			throws Exception {

		logger.info("ServiceResource.executePost");

		Object json = body.getEntity();

		ApiResponse response = new ApiResponse(ui);
		response.setAction("post");
		response.setApplication(services.getApplicationId());
		response.setParams(ui.getQueryParameters());

		ServicePayload payload = getPayload(json);

		executeServiceRequest(ui, response, ServiceAction.POST, payload);

		return new JSONWithPadding(response, callback);
	}

	@PUT
	@RequireApplicationAccess
	@Consumes(MediaType.APPLICATION_JSON)
	public JSONWithPadding executePut(@Context UriInfo ui,
			Map<String, Object> json,
			@QueryParam("callback") @DefaultValue("callback") String callback)
			throws Exception {

		logger.info("ServiceResource.executePut");

		ApiResponse response = new ApiResponse(ui);
		response.setAction("put");
		response.setApplication(services.getApplicationId());
		response.setParams(ui.getQueryParameters());

		ServicePayload payload = getPayload(json);

		executeServiceRequest(ui, response, ServiceAction.PUT, payload);

		return new JSONWithPadding(response, callback);
	}

	@DELETE
	@RequireApplicationAccess
	public JSONWithPadding executeDelete(@Context UriInfo ui,
			@QueryParam("callback") @DefaultValue("callback") String callback)
			throws Exception {

		logger.info("ServiceResource.executeDelete");

		ApiResponse response = new ApiResponse(ui);
		response.setAction("delete");
		response.setApplication(services.getApplicationId());
		response.setParams(ui.getQueryParameters());

		executeServiceRequest(ui, response, ServiceAction.DELETE, null);

		return new JSONWithPadding(response, callback);
	}

	@Produces("text/csv")
	@GET
	@RequireApplicationAccess
	public String executeGetCsv(@Context UriInfo ui,
			@QueryParam("callback") @DefaultValue("callback") String callback)
			throws Exception {
		ui.getQueryParameters().putSingle("pad", "true");
		JSONWithPadding jsonp = executeGet(ui, callback);

		StringBuilder builder = new StringBuilder();
		if ((jsonp != null) && (jsonp.getJsonSource() instanceof ApiResponse)) {
			ApiResponse apiResponse = (ApiResponse) jsonp.getJsonSource();
			if ((apiResponse.getCounters() != null)
					&& (apiResponse.getCounters().size() > 0)) {
				List<AggregateCounterSet> counters = apiResponse.getCounters();
				int size = counters.get(0).getValues().size();
				List<AggregateCounter> firstCounterList = counters.get(0)
						.getValues();
				if (size > 0) {
					builder.append("timestamp");
					for (AggregateCounterSet counterSet : counters) {
						builder.append(",");
						builder.append(counterSet.getName());
					}
					builder.append("\n");
					SimpleDateFormat formatter = new SimpleDateFormat(
							"yyyy-MM-dd HH:mm:ss.SSS");
					for (int i = 0; i < size; i++) {
						// yyyy-mm-dd hh:mm:ss.000
						builder.append(formatter.format(new Date(
								firstCounterList.get(i).getTimestamp())));
						for (AggregateCounterSet counterSet : counters) {
							List<AggregateCounter> counterList = counterSet
									.getValues();
							builder.append(",");
							builder.append(counterList.get(i).getValue());
						}
						builder.append("\n");
					}
				}
			} else if ((apiResponse.getEntities() != null)
					&& (apiResponse.getEntities().size() > 0)) {
				for (Entity entity : apiResponse.getEntities()) {
					builder.append(entity.getUuid());
					builder.append(",");
					builder.append(entity.getType());
					builder.append(",");
					builder.append(mapToJsonString(entity));
				}

			}
		}
		return builder.toString();
	}

}

redpajama_set_name: RedPajamaGithub


Our customers decide when, where and how often they want service! Residential customers are not required to sign a contract. Service is at your convenience.
We treat inside, including garage, power spray exterior perimeter around your home using high grade chemicals. We offer specialty services including tick, flea, scorpions, bees and gophers.
Our trained office staff will assist you in planning and scheduling the most effective treatment for your home and your particular pest problems. Our staff and technicians strive to offer you the most complete and effective customer service possible.
We offer "Green" programs and methods of treatment using the IPM approach. Integrated Pest Management is a method of working with the customer to prevent infestations using home seals, clearing exterior area of debris and stored items, sanitation conditions etc. IPM uses less chemicals and concentrates on prevention infestation.
We take pride in pleasing and accommodating our customers.


What Are Pre glued Hair Extensions?
"What are pre glued hair extensions?"
Pre glued hair extensions are a type of hair extension that have a glue-like substance at the tip of the hair in order for the hair extension to be glued (or rather, bonded) to the wearer's hair.
There are different types of pre glued extensions which have different names to either describe the shape of the tip or the substance used at the tip of the hair extensions.
"What are the different names for pre glued extensions?"
The most commonly used names for pre glued extensions are i-tip hair extensions; keratin tipped hair extensions; nail tip hair extensions; u-tip hair extensions; flat tip hair extensions; v-tip hair extensions and pre-bonded hair extensions.
Nail-tip, u-tip, flat tip and v-tip hair extensions are the basically the same type of hair extensions and the names are based on the shape of the keratin tip (see images).
They are shaped this way to form a tight and complete seal and make the attachment process quicker.
"How are pre glued extensions attached?"
The tip of the hair extensions is coated with keratin (usually, there are other types of tips) and it's this part (tip) of the hair extension that is used to bond it the hair extensions to the wearer's natural hair.
The keratin tip is heated in order to soften it and attach it to the wearer's hair.
"Are nano-tips and stick tips used the same as pre bonded hair extensions?"
This is a tricky one and as it's tricky, it's probably best to look at each type separately.
Nano tip hair extensions are the hair extensions that are used with nano rings. Nano rings are basically smaller versions of the micro rings used in micro ring hair extensions (also called micro bead hair extensions and micro loop hair extensions).
The tips of the nano tip hair extensions are bonded – as that's how the strands of hair extensions are held together.
However they are not attached to the hair by heating the tips, they're attached to the hair using nano rings.
Stick tip hair extensions (also called i-tip hair extensions) are the hair extensions that are used with micro rings. Micro rings are the larger (and original) version of nano rings (which are used in nano ring hair extensions).
The tips of the stick tip extensions are bonded in order hold the 80 or so strands of hair together.
Stick tip hair extensions are attached using micro rings and not by heating the tips (see? Told you it was a tricky one).
That's the hop, skip and jump through pre glued hair extensions.
As you can see, the world of hair extensions can be confusing with terms like pre glued hair extensions (also called pre bonded hair extensions), nano tip hair extensions, micro ring hair extensions, stick tip hair extensions… to name but a few.
Nevertheless, hopefully the information above has helped clarify the differences and similarities in the family of hair extensions known as pre-bonded and pre glued.
If you'd like more tips, take a looksee at our Hair Extensions Q&A section or if you'd like to be first to read new guides and articles, why not join our blog - it's easy to do and doesn't require any personal info - yippee!


I have been working on a new stuffed French Toast recipe (see "Rise & Shine Recipes" later this weekend) and purchased whole milk ricotta thinking that was what I was going to stuff the French Toast. Well, I changed my mind, and now had ricotta that I wanted to use….. so what to do?
Well, my sweet tooth got the better of me (Hey, it is "layering season") and I was craving a little lemon (It's also "cold and flu season") and my mind turned towards cookies. Soft, pillowy, lemon ricotta cookies are what I ended up throwing together, and they were pretty fantastic; almost cake-like cookies! These would also be great to add to your holiday cookie tin if that's what you do. A pleasant citrusy surprise along with the traditional fudge and sugar cookies!
The dough will be a little softer than a cookie dough that you are used to, but I promise it all works out in the end. Also, you may want to pick up five large lemons for this one… four for sure, five just in case. Enjoy!
Preheat your oven to 375 degrees, and line two baking sheet pans with parchment paper or a silicone baking mat.
In a mixing bowl combine your flour, salt, and baking powder. Give it a nice stir to combine, and set aside.
Cream the butter and sugar together until light and fluffy. One at a time add the eggs and mix in thoroughly. Scrape down your bowl and add the lemon zest, ricotta cheese, and the lemon juice. Mix in until thoroughly combined.
Spooning in a little at a time and mixing until "just combined" add the dry mixture. Because these cookies are almost "cake-like" we don't want them to be little bread bowls, so don't over mix. Mix until all the dry has been incorporated, and be sure to scape down your bowl one more time.
Now I initially used a traditional cookie scoop to lay these out, but then decided to spoon my dough into a piping bag with a star-tip to give the cookies a little texture. Both methods looked great. You may do either method, or you may use the old school method of two spoons. I'll let you figure that out on your own. Pipe, Scoop or Spoon onto your prepared baking sheet pans.
Place the cookie into your oven and bake 12-15 minutes, or until the edges are a light golden brown. Remember cookies have "carryover cooking" so they will seem soft when they come out but will continue cooking a little longer once out of the oven.
Allow the cookies to cool for 15 minutes then transfer to a cooling rack. You're going to ice these on the cooling rack… if you are concerned about "drippage" onto your surfaces, stick a sheet pan or plate underneath to catch those drippings.
Once the cookies are cooled thoroughly mix the ingredients for the glaze together and spoon carefully over the top. You will need less than you assume, so start small and in the center of each cookie using your spoon to glide the glaze over the top. Add more if you think you would like more.
Let the glaze set, and enjoy! It is like a mouth full of sunshine in every bite!


text:
Spied - A trio of India-bound 2015 Audi Q7s spotted testing
02/08/2014 - 09:46 | Audi Q7, Audi, Spy pictures | Anjan Ravi
Three prototypes of the next generation 2015 Audi Q7 were spotted testing in Croatia recently by a reader of Car Scoops. The second generation of Audi's flagship SUV launches next year in Europe, as confirmed to Indian Autos Blog by the company's technical head, Dr. Ulrich Hackenberg.
The next generation Q7 is expected to weigh 360 kg less compared to today's model.
Based on the VW Group's MLB architecture, the new Q7 is expected to weigh about 360 kg less compared to today's model. The weight loss is reported to have come from the use of high-tensile strength aluminium in the SUV's construction.
While some existing engines will be carried over to the new Q7, Audi could use the SUV's launch to debut their new 3.0-liter TDI V6 Clean Diesel engine which is Euro 6 compliant. The engine, which was revealed in May this year, is capable of producing 268 bhp and 600 Nm of torque, according to Audi. Compared to the current 3.0-liter V6 TDI, the Clean Diesel is up to 13 percent more fuel efficient and emits 15 fewer grams of CO2 per km.
The Q7 in India is assembled at the company's Aurangabad facility from CKD kits. The same arrangement would continue when the new Q7 arrives in India sometime next year.
Competitors: Mercedes GL Class, BMW X5, Volvo XC90
Expected Price: INR 75 - 90 lakhs, ex-Showroom
[Spy image from - Car Scoops]


On Paget Road, Barry Island.
On the outskirts of Barry.
Comments: There are two labelled vegan mains on the menu: Soya chunks (chunky pieces of soya cooked in a flavoursome rich sauce with onions, garlic & thyme) and bean stew (a mixture of beans slow cooked with flavoursome spices). They are served with your choice of white rice, rice 'n' peas or chips and steamed vegetables or coleslaw. They are on Just Eat, see the website link above. The staff are friendly.
On High Street in Barry.
Overlooking the waterfront in Barry Island.
Comments: The chips, made from Maris Piper/Markie potatoes, are cooked in vegetable oil in their own fryers. They are vegan and gluten free. All other meat and fish items are cooked in separate fryers. The mushy peas and curry sauce are vegan but check on the baked beans with the staff.
Holton Road is the main street running through Barry town centre.
Comments: Vegans can have the chips, homemade using Maris Piper potatoes which are fried in vegetable oil. They stock soya milk for drinks. The non dairy ice cream and waffle cones are not suitable for vegans.
On the front at Barry Island.
Comments: Inform the staff that you are vegan and do not want any egg, oyster sauce or sauces containing animal products in your dishes. There are suitable bean curd and vegetable options. Offer a home delivery service to Barry, Rhoose, Sully, Wenvoe and Dinas Powys.
On the roundabout at the bottom of Broad Street.
On Harbour Road, in Barry.
Close to Barry railway station.
On the north west outskirts of Barry.
Comments: Vegans can be catered for. The suitable options include a breakfast including toast with vegan spread, panini and they always have a vegan soup available. There are also cakes and chocolate brownies. Dairy free milks are stocked for drinks. It has a nice atmosphere and eclectic décor. There is more seating in the back. The coffee shop is dog friendly.
On Barry Island Esplanade, overlooking the beach.


an extensive, continuous part of a surface, space, or body: a region of the earth.
a part of the earth's surface (land or sea) of considerable and usually indefinite extent: a tropical region.
a district without respect to boundaries or extent: a charming region in Connecticut.
a part or division of the universe, as the heavens: a galactic region.
sphere: a region of authority.
field: studies in the region of logic.
an administrative division of a city or territory.
[Zoogeog.]a major faunal area of the earth's surface, sometimes one regarded as a division of a larger area.
a place in or a division of the body or a part of the body: the abdominal region.
Also called domain. an open connected set.
the union of such a set and some or all of its boundary points.
Hello there, this image is about Genetic Home Reference Nice Ideas #1 An Illustration Of The Region Of The Colon Affected In The Different Types Of Ulcerative Colitis. It is a image/jpeg and the resolution of this attachment is 588 x 502. This picture's file size is only 30 KB. Wether You want to download It to Your computer, you might Click here. You may too see more attachments by clicking the following picture or read more at here: Genetic Home Reference.
On the other-hand, recently we appreciate the household that is vintage. Properly, when you have heritage house parents that are ancient, you will want to decorate it to appear more chic. Genetic Home Reference Nice Ideas #1 An Illustration Of The Region Of The Colon Affected In The Different Types Of Ulcerative Colitis identity already-owned. Just how to change it out to make it fresh happy and more contemporary that you simply have a glass athome, if granted the glass is worth pricey. To become the main emphasis gorgeous, pick a color colour that is basic for that surfaces around it.
Select wallpaper having a pattern just like the minimalist geometric forms.Usually there's a indentation around the screen while in the old-house, if you choose to utilize wallpaper. To be able to stay subjected, put curtains around the sills' shape. But Genetic Home Reference may decrease luxury and the aesthetic in a screen that is little. Use only curtains typically, but created open. Another case should you feel very poor appearance window, then your curtains must be put away from framework and address.
A look more lavish interior will be long until the bottom also made by drapery. One of many things that would look hideous is probably old's racks had started porous and rotting. Replace with open racks of wood, might be contaminants or solid wood. Display also retro components you've. Open racks may also supply a modern effect that is minimalist that house that is old doesn't seem like a memorial.


text:
Q: How to reuse code in iOS(IBAction)? I've got two view controllers that have some similar function. Some of them are IBActions. Is there a way to put them together(so that it's easier to fix bugs)? I've tried inheritance but it seems that it does not work.
@implementation ClassA
-(IBAction)f
{
    //some code here
}

@implementation ClassB
-(IBAction)f
{
    //some code here
}

My question is that is there a way that I write function f once? If there is a bug, I could fix it more quickly this way.

A: Make a method that does the job and call it either from the IBAction or wherever you need it.

A: in inheritence, you can just declare in parent class, like abstract function, and for each child defination will be separte, now you have to do is this
make a method in parent class that performs the logic only,
make two ibactionn methods both in childs and perform the current child's UI tasks in that methods and use the parent's logic method, that u created above, to get the data.
inform if you get soltion or not.

A: You can make utility kind of class where you can make class method for this.
And you can call this method where needed.

A: You Can make another singleton class or utility class as per your requirement. And make class method, for common functionality. So u can use this functionality any where from project.
Its good practice to make utility class or singleton class for some common functionalities.