Tool Windows
Tool Windows
Tool windows are child windows of IntelliJ IDEA used to display information. These windows generally have their own toolbars (referred to as tool window bars) along the outer edges of the main window containing one or more tool window buttons, which activate panels displayed on the left, bottom and right sides of the main IntelliJ IDEA toolwindow. For detailed information about tool windows, please see IntelliJ IDEA Web Help .
Each side contains two tool window groups, the primary and the secondary one, and only one toolwindow from each group can be active at a time.
Each toolwindow can show multiple tabs (or “contents”, as they are called in the API). For example, the Run toolwindow displays a tab for each active run configuration, and the Changes toolwindow displays a fixed set of tabs depending on the version control system used in the project.
There are two main scenarios for the use of tool windows in a plugin.
In the first scenario (used by the Ant and Commander plugins, for example), a toolwindow button is always visible, and the user can activate it and interact with the plugin functionality at any time.
In the second scenario (used by the Analyze Dependencies
action, for example), the toolwindow is created to show the results of a specific operation, and can be closed by the user after the operation is completed.
In the first scenario, the toolwindow is registered in plugin.xml using the <toolWindow>
extension point.
The extension point attributes specify all the data which is necessary to display the toolwindow button:
-
The ID of the toolwindow (corresponds to the text displayed on the toolwindow button)
-
The anchor, meaning the side of the screen on which the toolwindow is displayed (“left”, “right” or “bottom”)
-
The “secondary” attribute, specifying whether the toolwindow is displayed in the primary or the secondary group
-
The icon to display on the toolwindow button (13x13 pixels)
In addition to that, you specify the factory class - the name of a class implementing the
ToolWindowFactory
interface.
When the user clicks on the toolwindow button, the createToolWindowContent()
method of the factory class is called, and initializes the UI of the toolwindow.
This procedure ensures that unused toolwindows don’t cause any overhead in startup time or memory usage: if a user does not interact with the toolwindow of your plugin, no plugin code will be loaded or executed.
If the toolwindow of your plugin doesn’t need to be displayed for all projects, you can also specify the conditionClass attribute - the qualified name of a class implementing the Condition<Project> interface (this can be the same class as the toolwindow factory implementation). If the condition returns false, the toolwindow will not be displayed. Note that the condition is evaluated only once when the project is loaded; if you’d like to show your and hide toolwindow dynamically while the user is working with the project, you need to use the second method for toolwindow registration.
The second method involves simply calling ToolWindowManager.registerToolWindow() from your plugin code. The method has multiple overloads that can be used depending on your task. If you use an overload that takes a component, the component becomes the first content (tab) displayed in the toolwindow.
Displaying the contents of many toolwindows requires access to the indexes.
Because of that, toolwindows are normally disabled while building indices, unless you pass true as the value of canWorkInDumbMode
to the registerToolWindow()
function.
As mentioned previously, toolwindows can contain multiple tabs, or contents. To manage the contents of a toolwindow, you can call ToolWindow.getContentManager(). To add a tab (content), you first need to create it by calling ContentManager.getFactory().createContent(), and then to add it to the toolwindow using ContentManager.addContent().
You can control whether the user is allowed to close tabs either globally or on a per-tab basis.
The former is done by passing the canCloseContents
parameter to the registerToolWindow()
function, or by specifying
canCloseContents="true"
in plugin.xml.
If closing tabs is enabled in general, you can disable closing of specific tabs by calling
Content.setCloseable(false).
How to Create a Tool Window?
The IntelliJ Platform provides the toolWindow extension point that you can use to create and configure your custom tool windows. This extension point is declared using the ToolWindowEP bean class.
To create a tool window, first declare an extension to the toolWindow extension point.
Creation of Plugin
To create a plugin that displays a custom tool window, perform the following steps:
- In your plugin project, create a Java class that implements the ToolWindowFactoryinterface.
- In this class, override the
createToolWindowContent
method. This method specifies the content for your tool window. - In the plugin configuration file plugin.xml, create the
<extensions defaultExtensionNs="com.intellij">...</extensions>
section. - To this section, add the
<toolWindow>
element, and for this element, set the following attributes declared in the ToolWindowEP bean class:- id (required): specifies the tool window caption.
- anchor (required): specifies the tool window bar where the tool window button will be displayed. Possible values: “left”, “right”, “top”, “bottom.”
- secondary (optional): when true, the tool window button will be shown on the lower part of the tool window bar. Default value is false.
- factoryClass (required): specifies the Java class implementing the ToolWindowFactory interface (see Step 1).
- icon (optional): specifies path to the icon that identifies the tool window, if any.
- conditionClass (optional): specifies a Java class that implements the Condition interface. Using this class, you can define conditions to be met to display tool window button. In the Condition class, you should override the value method: if this method returns false, the tool window button is not displayed on tool window bar.
To clarify the above procedure, consider the following fragment of the plugin.xml
file:
<extensions defaultExtensionNs="com.intellij">
<toolWindow id="My Sample Tool Window" icon="/myPackage/icon.png" anchor="right" factoryClass="myPackage.MyToolWindowFactory"/>
</extensions>
Sample Plugin
To clarify how to develop plugins that create tool windows, consider the toolWindow sample plugin available in the code_samples directory of the SDK documentation. This plugin creates the Sample Calendar tool window that displays the system date, time and time zone.
To run toolWindow plugin
- Start IntelliJ IDEA and open the tool_window project saved into the code_samples/tool_window directory.
- Ensure that the project settings are valid for your environment. If necessary, modify the project settings.
To view or modify the project settings, you can open the Project Structure. - Run the plugin by choosing the Run | Run on the main menu.
If necessary, change the Run/Debug Configurations.
The plugin creates the Sample Calendar tool window. When opened, this tool window is similar to the following screen:


{% extends "base.html" %} {% block title %}
Medieval catalogues > BENEDICTINES: THE SHORTER CATALOGUES > St Albans > Fragment of list of Whethamstede's books, after 1452
{% endif %}57 identified entries found.
All data was derived from the List of Identifications by Professor Richard Sharpe.
{% if not printing %}
A key to codes used in the List is available (opens in new tab).{% endif %}


WITNESS LIST
County Affairs Committee
April 23, 2015 - 10:30 AM or upon final adjourn./recess
For:
Carlton, John (Texas State Association of Fire and Emergency Districts)
Registering, but not testifying:
For:
Avery, Clay (Texas State Association of Fire and Emergency Districts (SAFE-D))
For:
Gallardo, Maxie (Workers Defense Project)
Reed, Charles (Dallas County Commissioners Court)
Registering, but not testifying:
For:
Pardue, Craig (Dallas County)
Against:
Dewitt, Cathy (Texas Association of Business)
Spilman, Annie (National Federation of Independent Business/TX)
On:
Groves, Garrett (Center for Public Policy Priorities)
Registering, but not testifying:
For:
Lary, Trey (Sig-Valley Ranch, Ltd.)
Layne, Kevin (Sig-Valley Ranch, Ltd.)
For:
Branson, Debbie (Parkland Board)
Registering, but not testifying:
For:
Ramon, Mariah (Teaching Hospitals of Texas)
Reed, Charles (Dallas County Commissioners Court)
For:
Boswell, Chris (Self; City of Harlingen)
LaMure, Julee (City of South Padre Island)
Lee, Donald (Texas Conference of Urban Counties)
Lee, Donald (Texas Conference of Urban Counties)
1
WITNESS LIST
For:
Marin, Elena (Self; Su Clinica)
Rodriguez, Arturo (Self; City of Brownsville)
Sanchez, Daniel (Cameron County)
Whittington, Randolph (Self; South Texas Medical Foundation)
Against:
Ballenger, Joshua (Self; North cameron county republican club)
Barnes, Jim (Self; Mcallen tea party)
Campbell, Jordan (Cameron County Womens Republican Culub)
Machner, Matthew (UT Brownsville College Republicans)
Registering, but not testifying:
For:
Garcia, Judge Ramon (Hidalgo County)
Garza, Ramiro (City of Edinburg)
Glancey, Richard (Valley Baptist/Tenet Health)
Against:
Adams, Dr. Dorothy (Self)
Allen, Georgena (Self)
Baker, Linda and Thomas (Self)
Barnes, Elizabeth (Self; McAllen/Hidalgo Co. Tea Party)
Batterson, Earl and Sharon (Self)
Batterson, Earl and Sharon (Self)
Bererino, Lupita (Self)
Bonds, Merrijo (Self; Hidalgo Tea Party)
Bonds, Robert (Self)
Bowan, Ian (Self)
Casas, Elijah (Self)
Cruz, Raul (Self)
Deason, Leon (Self)
Diaz, Cezar (Self)
Dierlam, Elizabeth (Self)
Dierlam, Elizabeth (Self)
Euler, Eva (Self; HC Republican Women)
Frady, Terry (Self)
Gibbons, Bonnie (Self)
Gonzalez, Angie (Self)
Greene, Dr. William (Self)
Griffiths, Bruce (Self)
Harris, Mark and Diane (Self)
Hoover, Effie (Self)
Hoover, Gordon (Self)
Jennings, Vanessa (Self)
Jetty, John (Self)
Kaltenbach, David (Self)
2
WITNESS LIST
Against:
Kaltenbach, Joshua (Self)
Lopez, April (Self; Lopez Family Clinic)
Lopez, Virginia (Self)
Machner, Sharon (Self)
Martinez, Gabriel (Self)
Martinez, Michael (Self)
Martinez, Roxanne & Joe (Self)
Meschi, Janet (Self)
Perez, Delfina (Self)
Perez, Fernando (Self)
Price, Michael (Self)
Reyes-Rice, Wanda (Self)
Rice, George (Self)
Sanez, Cindy (Self)
Stewart, Stephen (Self)
Stolar, Kenneth (Self)
Tardenan, Deanarais (Self)
Walbeck, Mathew (Self)
3


The challenge faced by Braque and Picasso was how to reflect the immense shift in consciousness that the new technological environment of the industrial revolution imposed without falling into the elementary solution of merely becoming machine illustrators.6 They solved it by illustrating the spirit of the time. By not presenting an immediately coherent view of life, but aiming instead to render the sense of multiplicity which had been the subtext of Cézanne's late work as the governing element of reality, cubism metaphorically reflected on the accelerated rate of change. The intercultural contact, and the move away from determinism to relativity, were the hallmarks of the modernist era.
Figure 13: Picasso. Guitar , 1912.
(Palau i Fabre 1990: 241)
Cubism not only adhered to its time conceptually, but also formalistically. Through the method of collage the cubists incorporated products of industrial mass production into their work. These processes in turn had an influence on the development of modern sculpture, seen in Picasso's use of tin in the production of constructions such as Guitar of 1912. [Figure 13]
From that moment, sculpture was not conceived of as a solid mass, but rather as an open construction of planes. From the Guitar , via Russian constructivism, seen in the work of Vladimir Tatlin, a tradition of assembled metal sculpture was inaugurated in the West which culminated in the work of David Smith and Anthony Caro. For an artist like Smith the use of metal counted for more than merely the radical new possibilities it opened up for sculpture: it symbolised the industrial age to which he belonged. 'My aim', he wrote in 1952, 'is the same as in locomotive building: to arrive at a given functional form in the most efficient manner'. (Hughes 1993: 61) [Figure 14]
Figure 14: David Smith. Spoleto, Italy, 1963.
(Chipp)


ConnectorPipeline
|
ConnectorPipeline |
3 |
ConnectorPipeline#loadConnector
|
ConnectorPipeline#loadConnector |
3 |
returns a connector
|
- |
|
maps connector functions
|
- |
|
calls authorize on underlying connector
|
- |
|
Authorization
|
Authorization |
6 |
get
|
ConnectorPipeline#get |
2 |
returns existing values
|
- |
|
returns null for non present values
|
- |
|
set
|
ConnectorPipeline#set |
2 |
sets value in state
|
- |
|
calls save
|
- |
|
delete
|
ConnectorPipeline#delete |
2 |
sets value in state
|
- |
|
calls save
|
- |
|
ConnectorPipeline
|
ConnectorPipeline |
7 |
.loadConnector
|
ConnectorPipeline#loadConnector |
7 |
loads the correct settings
|
- |
|
maps runscope settings
|
- |
|
maps appliction id settings
|
- |
|
maps appliction name settings
|
- |
|
returns a ConnectorProxy
|
- |
|
passes settings to connector proxy
|
- |
|
passes context to connector proxy
|
- |
|
Proxy
|
ConnectorProxy |
18 |
contructor
|
ConnectorProxy#constructor |
3 |
sets up logger
|
- |
|
saves path to connector
|
- |
|
saves settings
|
- |
|
ConnectorProxy#init
|
- |
7 |
with no bucket
|
- |
5 |
returns a connectorproxy
|
- |
|
saves underlying connector
|
- |
|
maps connector methods
|
- |
|
proxies refreshCredentials
|
- |
|
remaps original refreshCredetials
|
- |
|
with authorized bucket
|
- |
2 |
returns a connectorproxy
|
- |
|
authorizes the proxy
|
- |
|
ConnectorProxy#_refreshCredentials
|
- |
2 |
if bouncer token in db has been refreshed
|
- |
2 |
calls authorize with new bouncer token
|
- |
|
doesn't call refresh on connector
|
- |
|
ConnectorProxy#authorize
|
- |
6 |
if connector has not authorize method
|
- |
1 |
returns the proxy object
|
- |
|
if token is a string
|
- |
3 |
passes the bouncer token to the connector
|
- |
|
uses the string as the token lookup
|
- |
|
returns the proxy
|
- |
|
if token is an Auth object
|
- |
2 |
passes the bouncer token to the connector
|
- |
|
returns the proxy
|
- |
|


No topics have been created yet.
There are no pending unused skills.
No topics or skills have been created yet. Create Topic Create Skill
No topics or skills have been created yet.


Did you ever see a Scala compiler error such as:
[error] TheNextFacebook.scala:16: type mismatch; [error] found : akka.http.scaladsl.server.StandardRoute [error] required: akka.stream.scaladsl.Flow[akka.http.scaladsl.model.HttpRequest,akka.http.scaladsl.model.HttpResponse,Any] [error] Http().bindAndHandle(r, "localhost", 8080)
and had no idea what to do next? Well in this case, you need to provide an implicit instance of an ActorMaterializer
,
but the compiler isn't smart enough to be able to tell you that. Luckily, Scala Clippy is here to help!
Just add the Scala Clippy compiler plugin, and you'll see this additional helpful message:
[error] Clippy advises: did you forget to define an implicit akka.stream.ActorMaterializer? [error] It allows routes to be converted into a flow. [error] You can read more at http://doc.akka.io/docs/akka-stream-and-http-experimental/2.0/scala/http/routing-dsl/index.html
In your SBT build file, add:
addCompilerPlugin("com.softwaremill.clippy" % "plugin" % "0.1" cross CrossVersion.full)
Upon first use, the plugin will download the advice dataset from https://scala-clippy.org
and store it
in the $HOME/.clippy
directory. The dataset will be updated at most once a day, in the background.
Help others users by submitting an advice for a compilation error that you have encountered! Just click "contribute" above and paste in your error!
Or, you can check out the plugin & website source on GitHub.


Gorilla::Caption Class Reference
List of all members.
Public Member Functions |
| void | font (size_t font_index) |
| bool | intersects (const Ogre::Vector2 &coordinates) const |
| Ogre::Real | left () const |
| void | left (const Ogre::Real &left) |
| Ogre::Real | top () const |
| void | top (const Ogre::Real &top) |
| void | size (const Ogre::Real &width, const Ogre::Real &height) |
| Ogre::Real | width () const |
| void | width (const Ogre::Real &width) |
| Ogre::Real | height () const |
| void | height (const Ogre::Real &height) |
| Ogre::String | text () const |
| void | text (const Ogre::String &text) |
| TextAlignment | align () const |
| void | align (const TextAlignment &alignment) |
| VerticalAlignment | vertical_align () const |
| void | vertical_align (const VerticalAlignment &alignment) |
| size_t | clipped_left_index () const |
| size_t | clipped_right_index () const |
| Ogre::ColourValue | colour () const |
| void | colour (const Ogre::ColourValue &colour) |
| void | colour (Gorilla::Colours::Colour colour) |
| Ogre::ColourValue | background () const |
| void | background (const Ogre::ColourValue &background) |
| void | background (Gorilla::Colours::Colour background) |
| void | no_background () |
| void | _redraw () |
Protected Member Functions |
|
void | _calculateDrawSize (Ogre::Vector2 &size) |
|
| Caption (Ogre::uint glyphDataIndex, Ogre::Real left, Ogre::Real top, const Ogre::String &caption, Layer *parent) |
Protected Attributes |
|
Layer * | mLayer |
|
GlyphData * | mGlyphData |
|
Ogre::Real | mLeft |
|
Ogre::Real | mTop |
|
Ogre::Real | mWidth |
|
Ogre::Real | mHeight |
|
TextAlignment | mAlignment |
|
VerticalAlignment | mVerticalAlign |
|
Ogre::String | mText |
|
Ogre::ColourValue | mColour |
|
Ogre::ColourValue | mBackground |
|
bool | mDirty |
|
buffer< Vertex > | mVertices |
|
size_t | mClippedLeftIndex |
|
size_t | mClippedRightIndex |
Friends |
|
class | Layer |
Detailed Description
Definition at line 2461 of file Gorilla.h.
Member Function Documentation
| void Gorilla::Caption::_redraw |
( |
|
) |
|
function. _redraw desc. Redraw the text. note. This shouldn't be need to be called by the user.
Definition at line 2082 of file Gorilla.cpp.
| void Gorilla::Caption::align |
( |
const TextAlignment & |
alignment |
) |
[inline] |
function. alignment desc. Set the alignment of text.
Definition at line 2626 of file Gorilla.h.
| TextAlignment Gorilla::Caption::align |
( |
|
) |
const [inline] |
function. alignment desc. Get the alignment of text.
Definition at line 2617 of file Gorilla.h.
| void Gorilla::Caption::background |
( |
Gorilla::Colours::Colour |
background |
) |
[inline] |
function. background desc. Set the background colour
Definition at line 2734 of file Gorilla.h.
| void Gorilla::Caption::background |
( |
const Ogre::ColourValue & |
background |
) |
[inline] |
function. background desc. Set the background colour
Definition at line 2723 of file Gorilla.h.
| Ogre::ColourValue Gorilla::Caption::background |
( |
|
) |
const [inline] |
function. background desc. Get the background colour
Definition at line 2714 of file Gorilla.h.
| size_t Gorilla::Caption::clipped_left_index |
( |
|
) |
const [inline] |
function. clipped_left_index desc. Get the index (character position), of the first character that could not be drawn due to the limits of the width of the text, to the left. return. size_t -- The index if the first clipped character, or std::string::npos if there was no clipping and the text was drawn fully within the given space.
Definition at line 2661 of file Gorilla.h.
| size_t Gorilla::Caption::clipped_right_index |
( |
|
) |
const [inline] |
function. clipped_right_index desc. Get the index (character position), of the first character that could not be drawn due to the limits of the width of the text, to the right. return. size_t -- The index if the first clipped character, or std::string::npos if there was no clipping and the text was drawn fully within the given space.
Definition at line 2674 of file Gorilla.h.
| void Gorilla::Caption::colour |
( |
Gorilla::Colours::Colour |
colour |
) |
[inline] |
function. colour desc. Set the text colour.
Definition at line 2703 of file Gorilla.h.
| void Gorilla::Caption::colour |
( |
const Ogre::ColourValue & |
colour |
) |
[inline] |
function. colour desc. Set the text colour.
Definition at line 2692 of file Gorilla.h.
| Ogre::ColourValue Gorilla::Caption::colour |
( |
|
) |
const [inline] |
function. colour desc. Get the text colour.
Definition at line 2683 of file Gorilla.h.
| void Gorilla::Caption::font |
( |
size_t |
font_index |
) |
[inline] |
function. font desc. Changes the font to a different Glyph index. note. If the font index does not exist, an exception may be thrown.
Definition at line 2474 of file Gorilla.h.
| void Gorilla::Caption::height |
( |
const Ogre::Real & |
height |
) |
[inline] |
function. height desc. Set the maximum height of the text can draw into.
Definition at line 2586 of file Gorilla.h.
| Ogre::Real Gorilla::Caption::height |
( |
|
) |
const [inline] |
function. height desc. Get the maximum height of the text can draw into.
Definition at line 2577 of file Gorilla.h.
| bool Gorilla::Caption::intersects |
( |
const Ogre::Vector2 & |
coordinates |
) |
const [inline] |
function. intersects desc. Does a set of coordinates lie within this caption?
Definition at line 2493 of file Gorilla.h.
| void Gorilla::Caption::left |
( |
const Ogre::Real & |
left |
) |
[inline] |
function. top desc. Set where the text should be drawn vertically. note. If the TextAlignment is Right Aligned, then this will be the right-side of the last character drawn (with in width limits). If the TextAlignment is Centre Aligned, then this will be the center of the drawn text drawn (with in width limits).
Definition at line 2514 of file Gorilla.h.
| Ogre::Real Gorilla::Caption::left |
( |
|
) |
const [inline] |
function. top desc. Get where the text should be drawn vertically.
Definition at line 2502 of file Gorilla.h.
| void Gorilla::Caption::no_background |
( |
|
) |
[inline] |
function. no_background desc. Don't draw the background. note. This just sets the background colour alpha to zero. Which on the next draw tells Caption to skip over drawing the background.
Definition at line 2751 of file Gorilla.h.
| void Gorilla::Caption::size |
( |
const Ogre::Real & |
width, |
|
|
const Ogre::Real & |
height | |
|
) |
| | [inline] |
function. size desc. Set the maximum width and height of the text can draw into.
Definition at line 2545 of file Gorilla.h.
| void Gorilla::Caption::text |
( |
const Ogre::String & |
text |
) |
[inline] |
function. alignment desc. Set the text to show.
Definition at line 2606 of file Gorilla.h.
| Ogre::String Gorilla::Caption::text |
( |
|
) |
const [inline] |
function. caption desc. Get the text indented to show.
Definition at line 2597 of file Gorilla.h.
| void Gorilla::Caption::top |
( |
const Ogre::Real & |
top |
) |
[inline] |
function. top desc. Set where the text should be drawn vertically.
Definition at line 2534 of file Gorilla.h.
| Ogre::Real Gorilla::Caption::top |
( |
|
) |
const [inline] |
function. top desc. Get where the text should be drawn vertically.
Definition at line 2525 of file Gorilla.h.
| void Gorilla::Caption::vertical_align |
( |
const VerticalAlignment & |
alignment |
) |
[inline] |
function. vertical_align desc. Set the vertical alignment of text.
Definition at line 2646 of file Gorilla.h.
| VerticalAlignment Gorilla::Caption::vertical_align |
( |
|
) |
const [inline] |
function. alignment desc. Get the vertical alignment of text.
Definition at line 2637 of file Gorilla.h.
| void Gorilla::Caption::width |
( |
const Ogre::Real & |
width |
) |
[inline] |
function. width desc. Set the maximum width of the text can draw into.
Definition at line 2566 of file Gorilla.h.
| Ogre::Real Gorilla::Caption::width |
( |
|
) |
const [inline] |
function. width desc. Get the maximum width of the text can draw into.
Definition at line 2557 of file Gorilla.h.
The documentation for this class was generated from the following files:


| Project: | NS-ACEF |
|---|---|
| Internal Release Number: | 1.0 |
| Last update: | January 16, 2008 |
| Related Documents: |
It consists in checking if Netlist is correctly interpreted. Indeed Netlist contains macro must be evaluated. The program test displays the interpreted Netlist.
It consists in checking the table equation is correct. The program test displays the table equation and we have to check that physical law are correctly wrote.
The test consists in comparing result with a SPICE simulation.
A script runs the program on a list of Netlist. For each circuit file, a file is created. This file contains the result of the parser, the automatic equations formulation and the transient analysis.


1 1/2 pounds skirt steak, cut into 1/2-inch pieces
12 mini flour tortillas, warmed
3/4 cup diced red onion
1/2 cup chopped fresh cilantro leaves
1 lime, cut into wedges
Instructions
In a medium bowl, combine soy sauce, lime juice, 1 tablespoon canola oil, garlic, chili powder, cumin and oregano.
In a gallon size Ziploc bag or large bowl, combine soy sauce mixture and steak; marinate for at least 1 hour up to 4 hours, turning the bag occasionally.
Heat remaining 1 tablespoon canola oil in a large skillet over medium high heat. Add steak and marinade, and cook, stirring often, until steak has browned and marinade has reduced, about 5-6 minutes, or until desired doneness.
Serve steak in tortillas, topped with onion, cilantro and lime.


As you are reading this text, someone in your country has been affected by the AIDS crisis. People
in every part of the world have been affected by the AIDS pandemic. Every nation in the world has
had to take steps to address it. According to a recent United Nations estimate, 38.5 million people
across the globe are infected with HIV-AIDS.
Because AIDS has had such far-reaching effects, in the year 2000, for the first time in the
history
of the United Nations, the Security Council took up a health issue - HIV-AIDS. The world body
declared the spread of the virus a global emergency, a threat to peace and security in Africa, the
continent that has been the hardest hit by the disease. The AIDS virus was considered no less
destructive than warfare itself. In the year 2000, armed conflict took the lives of 2,000 people in
Africa, while the AIDS virus claimed the lives of 2 million.
World-wide, the effect of the spreading AIDS virus has created 16.6 million orphans, 90 per cent of
whom are in sub-Saharan Africa, a region where the crisis has been particularly deadly. Because so
many have died, the very infrastructure of the region is endangered. So many people who play key
roles in society - doctors, teachers, farmers - are dying of AIDS.
What is the United Nations doing to address the AIDS crisis? UN-AIDS and its agencies have brought
some innovative ways of spreading the message that, first, people need to overcome the stigma of
AIDS so they can come forward to learn about prevention, diagnosis and treatment. One way to
transmit this message is by providing education and AIDS awareness training to local community
members whose work brings them into regular contact with other members. One such local community
member is Paul Lopez, a hairdresser in Mexico City. Paul’s clients tend to confide in him, their
regular hairdresser. Therefore, he was trained by a UN-AIDS programme to dispense advice about
testing and treatment of HIV-AIDS. Now, along with advice about beauty, Paul tells clients how they
can protect themselves from the AIDS virus or where they can go for treatment should they need it.
Another crisis that United Nations programmes address is the crisis of care produced by the
overwhelming number of AIDS orphans, 95 per cent of whom are in sub-Saharan Africa, where the spread
of AIDS has been particularly lethal. Normally, when a child's parents die of AIDS, other family
members, such as uncles and aunts, will take responsibility for the orphaned child. But because
there are such increasing numbers of AIDS orphans and because the economic resources of some
communities are so limited, it is increasingly difficult to find adults who can take in extra
children. Often, children live by themselves in their deceased parents' home, surviving as well as
they can.
A typical case is fourteen year-old Justin of Malawi, who has to care for his 10-year-old brother
and nine-year-old sister. Justin says it is very hard to find enough to eat although he does his
best to support himself and his siblings
through his job carrying food for merchants. Since Justin
and his siblings have no one to take them in, they continue to live by themselves in their deceased
parents' home. United Nations and its agencies such as UNICEF sends aid workers and mobilizes
community-based volunteer groups to go to the homes or orphaned children with daily supplies of
food, money and advice on how to spend it. The aid workers also know the necessity of encouraging
the children to go to school. Children's chances of completing their education are cut in half once
they become orphans.
In the Ugandan village of Kalong, for example, a tragic scene that is all too common in rural
villages took place: six-year-old Nakeyeyune cried as the elders decided who would take custody of
her six-month-old brother and other young siblings after both his parents had died from AIDS-related
causes. In Uganda, one quarter of all families are caring for AIDS orphans. The poverty of many
rural families makes it difficult for them to take responsibility for more children.
One way the United Nations helps single and foster parents to raise income levels is by fostering
micro-credit cooperatives in rural villages. Micro-credit programmes allow traditional craft-makers
and farmers to form cooperatives and sell more of what they produce. The increased incomes enable
single and adoptive foster parents to raise their income levels so they can support
orphaned
children. Such programmes have been especially successful among single mothers.


Expedite operationalisation of 110 additional blocks or return them: Govt to Coal India
“Out of 50 explored blocks, project reports of 25 blocks have been prepared.”
by PTIThe coal ministry has asked state-owned CIL to either expedite the operationalisation of 110 additional blocks allotted to it or return the mines to the government, an official said.
The coal ministry recently enquired from the PSU about the operational status of the additional blocks allotted to it, and whether extraction from these coal blocks is techno-economically feasible, the official added.
The government was told that of the 110 additional CIL blocks, 50 were explored, 41 were under exploration and balance 19 were partly/regionally explored.
Further, out of 50 explored blocks, project reports of 25 blocks have been prepared, the coal ministry was informed.
The ministry “emphasised on quick operationalisation of all of these blocks, otherwise CIL may return them to the Ministry of Coal for their allotment/ auction to other agencies,” the official said.
Coal India Ltd (CIL) accounts for over 80% of domestic coal output.
The state-owned firm had earlier said that it will produce 750 million tonnes of coal in the next financial year.
The PSU will further produce 1 billion tonnes of coal by FY2024, Coal Minister Pralhad Joshi had said.
CIL is targeting to produce 660 million tonnes of the dry fuel in 2019-20 compared to 607 million tonnes in the last fiscal.


|
GreyMatter
Weblog/Journal Software . Version 1.7.2 .
Installation Instructions
Copyright (c) 2000-2006 The GreyMatter Team . All Rights Reserved
GreyMatter 1.7.2 is the second release in 2007. It continues to modify the internal sturcture of the
code to be more robust and easier to modify. It also contains bug fixes and security enhancements.
GreyMatter requires the ability to run Perl software on
your account on your Web server and an
FTP client (such as WS_FTP LE)
to upload the files to your account and
CHMOD
them on the server. Also, you should be modestly comfortable with
editing HTML to customize the templates, and thus make your Weblog, journal, or
photolog truly your own. GreyMatter is run on a variety operating systems including Unix/Linux, Mac OSX, and Windows.
Note: that GreyMatter 1.6.1 and higher requires perl 5.6 at a minimum. Even
though perl 5.6 was released in 2000, not everyone can control which version of Perl their ISP/Web Host will
choose to run. GM 1.6.1 can be made to work with older versions of Perl, see
the forums for more information. While the GM team will keep older version of Perl in mind while
we continue to develop GreyMatter, it is hoped that by taking advantage of features in more recent versions
of Perl that we can get closer to our goals (among which is a GM that is easier to modify, sharable
themes, better spam controls, etc.).
Here is a list of what files you should get in your GreyMatter package
(either in a zip or tar file):
- gm_install.html this document on installing GreyMatter
- gm_manual.html GreyMatter usage manaual, faq, etc.
- gm_cookbook.html configuration guide
- gm_dev_guide.html this document on installing GreyMatter
- cgi-bin
- gm.cgi the admin script (required for upgrade)
- gm-comments.cgi for posting comments and searching (required for upgrade)
- gm-karma.cgi for modifying karma of an entry (required for upgrade)
- gm-upload.cgi for uploading files (required for upgrade)
- gm-library.cgi core code for GM (required for upgrade)
- gm-authors.cgi GM users and information
- gm-banlist.cgi who is banned
- gm-config.cgi configuration settings
- gm-cplog.cgi log of events
- gm-entrylist.cgi a summary of the entries for the site
- gm-templates.cgi the look and feel of your site, can be given to others
- libs contains essential files of GreyMatter code (required for upgrade)
- emoticons contains the emoticon images used by site
- gm-changelog.html the changes per release that have occurred
Users of a previous version of GreyMatter should:
- Download the 1.7.2 zip/tar file from
the forums and look for the download page.
- Open the archive locally, change the path to perl if needed.
- Backup your existing GreyMatter installation! This means making a copy of your archive director
(or whatever you have named your archive directory) and the cgi-bin directory (or wherever
you keep the gm.cgi and other gm files).
- Upload the following files to your server:
- gm-comments.cgi
- gm-karma.cgi
- gm-upload.cgi
- gm.cgi
- gm-library.cgi
- and the 'libs' directory (including all files within, Gm_Storage.pm, etc.)
These files are the core of GreyMatter.
- Confirm that gm-comments.cgi, gm-karma.cgi, gm-upload.cgi are
CHMOD'ed 755,
and gm-library.cgi, and all files in the 'libs' directory are
CHMOD'ed 644.
- Log in.
When you log in for the first time after upgrading, the upgrade routine will detect
the old version based on your gm-config.cgi file, and update it to 1.7.2. If you've customized
your version string you may see an error message. You can manually edit line 24 of gm-config.cgi
to read "1.3".
- We recommend that you check your config and templates immediatly after
upgrading as there are a few new features. This includes the ability to
protect all the author's names from being used in a post on the site (to
avoid impersonation issues). This feature and other are turned off by default
so that you do not have to worry about your site behaving differently. Also,
the new templates should allow you to show errors and messages (such as when a
banned user tries to post a comment) in the style of the rest of your website.
- Rebuild everything and then visit your site.
- You may also want to upload (or at least keep for reference) gm_manual.html,
gm_cookbook.html, and for people interested in modifying code in GM, gm_dev_guide.html.
There are two sets of directions for installing GreyMatter. The Detailed Install was written by
Melanie Cook at www.wiccked.com/gmfd/
(originally titled "Greymatter Installation For Dummies") to be a step-by-step guide to
installing GreyMatter. The Quick Installation Guide is the same
steps but without as much detail or explanation. If at any point you find you need more detail/explanation, please
skip below to the Detailed guide.
During the process of installing GreyMatter, you will need to know some things
about your account on your Web server and how you want your site to work. It
would be helpful if you wrote them down or had them stored electronically, so
you could have them as a reference. Yes, it's time to take some notes.
- Where is Perl?
The location of Perl is vitally important to running GreyMatter. Your Web
host can tell you where Perl is located, or you can find out for yourself if
you have access via telnet or SSH to your server. If you have such access,
type 'whereis perl' at the prompt, and make note of that location. It will
be something like '/usr/bin/perl', '/usr/local/bin/perl', or '/usr/bin/perl5'
on a Unix server. On a Windows server, it may be 'C:/perl/bin/perl.exe'.
Once you know the location of Perl, make a note of it, and go on to the next step.
- What will your site structure be?
It seems silly to think about this so early, but setting the site structure
is like building the foundation for a house. That's why we'll lay a good foundation now.
First, it will be important to know how you want your log to appear. Some
people like to have their GreyMatter-powered log appear on the main page of their
site; when that is the case, bringing up http://www.mysite.com/ will show the log.
Others like to have their log in another place, in what is called a subdirectory.
In that case, it's usually something like http://www.mysite.com/log/, where /log/
is the location of the log.
So, take some time to think about it. GreyMatter needs to know two things
to properly present your log: where your main page for your log will be, and
where you want your archives to be. If you wanted your main log to be at
http://www.mysite.com/weblog/, and the archives folder for that to be called
"blatherings", your archives will be stored at http://www.mysite.com/weblog/blatherings/.
- Where are your CGI files kept on the server?
When you upload and install GreyMatter, it will take a good stab how
your Web server is set up. It will always find the directory where CGI files
should be kept, assuming that you upload it to the right place.
To make sure you do it right, start your FTP program and just look at your
account's main folder. What is that folder called? [Write that down; if you
can't see, try to go "up" a folder and see if you can see that.] Do you see a
folder named /cgi-bin/? If so, find that, and make a note of where it is in
relation to the main folder of your site. That will help you later on in the
installation process.
Once you've made these notes, you're ready to roll.
- Make sure you meet all the requirements, as specified above.
- Separately, open the files "gm.cgi", "gm-karma.cgi","gm-comments.cgi",
and "gm-upload.cgi", and look at the very first line, which should say "#!/usr/bin/perl".
Make sure that the Perl pointer here is correct; refer to your notes that you made.
If, for example, your Perl directory is '/usr/local/bin/perl', change the first line
in each of the four files to reflect that. You must maintain the #! [the shebang,
if you're wondering what to call it] before the directory, or it just won't work.
This is the only time you'll ever need to touch the GreyMatter program code.
- Refer to your notes above about site structure. If you want your main index
file to be named something other than "index.htm", then rename the included index.htm
file accordingly. For clarity's sake, we'll assume "index.htm" with the rest of the instructions.
- Open your FTP program. Important note: All files except "gm-icon.gif" must be
uploaded in ASCII mode; check your FTP program to find out how to make sure that
all CGI files are uploaded as ASCII and not binary files.
- Upload all the GreyMatter CGI files (they all begin with "gm" and end with ".cgi")
to the CGI files directory you found above in your notes. All these files must be in the
same directory on your account.
Note that the libs directory and its files should also be uploaded to the cgi directory.
- CHMOD
the files "gm.cgi", "gm-karma.cgi", "gm-comments.cgi"and "gm-upload.cgi" to 755,
CHMOD
all the other .cgi files to 666 (except gm-library.cgi. DO NOT change the permissions on
gm-library.cgi), and and all files in the 'libs' directory (Gm_Storage.pm, etc.) to 644 (same as gm-library.cgi).
- Upload index.html (or whatever you've renamed it to) and gm-icon.gif to the place where you want your log to be. Refer to your notes above for that process.
- CHMOD the index.html file (or whatever you've renamed it to) to 666.
- Create the directory where all your log entries and archives will be stored. Refer to your notes above when creating this directory. By default, GreyMatter will assume you name this directory "archives", but you can name it whatever you wish.
- CHMOD your entries/archives directory to 777.
 If all of the above went okay, then you should now see the GreyMatter logon prompt. (If you're getting a 500 Server Error or having other problems attempting to run gm.cgi, go back and make sure that everything is uploaded and CHMODed correctly; read the "Troubleshooting" section in the manual for more information.)
- Log on with the author name "Alice", and the password "wonderland".
Welcome to GreyMatter! The next step is to configure your paths. Refer to your notes above on your site structure.
We'll use the following example site structure to explain the paths setup; this is where a sizable group of new GreyMatter users have gotten confused before, so we'll work with this example and use it to explain all six paths.
Our example comes from the site structure of Geof Morris, one of the authors of this set of installation instructions. [Though it's about to be re-designed, it will still be clear for you.]
Geof's site is http://www.ijsm.org/, and he hosts a log on the front page. His entries and archives folder is /journal/, so it's found at http://www.ijsm.org/journal/. His server requires CGI files to be in the /cgi-bin/ directory, so his GreyMatter installation is found at http://www.ijsm.org/cgi-bin/gm.cgi .
Now, the first time you look at your paths, they'll be wrong. That's okay! For an example, here's what Geof saw the first time he installed GreyMatter:
Local Log: /home/ijsm/public_html/cgi-bin
Local Entries/Archives: /home/ijsm/public_html/cgi-bin/archives/
Local CGI: /home/ijsm/public_html/cgi-bin
Website Log: http://www.ijsm.org/cgi-bin
Website Entries/Archives: http://www.ijsm.org/cgi-bin/archives/
Website CGI: http://www.ijsm.org/cgi-bin
This wasn't what Geof wanted, so he had to start changing things.
First off, he wanted http://www.ijsm.org/ to be where his log appeared. So, he changed the Log paths to:
Local Log: /home/ijsm/public_html
Website Log: http://www.ijsm.org/
Next, he'd created /journal/ in the main directory of his site, and that's where he wanted his archives and entries to be. So the Entries/Archives paths were going to have to change. Here's what they became:
Local Entries/Archives: /home/ijsm/public_html/journal/
Website Entries/Archives: http://www.ijsm.org/journal/
What about the CGI files? Well, that's what GreyMatter gets correct every time. There's no need to change the two CGI paths, unless you want GreyMatter in a subdirectory of your /cgi-bin/ directory.
NOTE: DO NOT put your archives directory inside your cgi-bin.
Return to Configuration and click "Diagnostics & Repair". This routine checks to see that all your files and paths are working correctly. If you aren't able to run it successfully, your paths are probably incorrect; check the Troubleshooting section of the manual. Once you've run it successfully, you'll be able to post your first entry.
Click "Edit Authors", create a new account for yourself with the name and password you'd like to use, and delete Alice. (You could keep Alice around, but for obvious security reasons, it's not recommended.) Since you're still logged on as Alice, you'll need to re-enter under the new name and password.
All done! You should now be able to post entries and get
your Weblog, journal, or photolog going. (It's a good idea to set up a private
test log first, and try creating and editing a few test entries, simply so you
can get the hang of GreyMatter before doing it "for real".)
GreyMatter uses an extensive template system to allow you total
control over every aspect of your Weblog and all the pages & elements it'll
comprise. The default templates included with GreyMatter are quite plain-jane,
but they should be enough to provide a starting point and, hopefully, to give you
a basic idea of GreyMatter's template & variable usage. Change the templates
as much as you like (and just reupload the gm-templates.cgi file if you mess things
up too much and want to start over) to suit your own design and style; refer to the
GreyMatter manual (included as gm_manual.html) for full information about all the template variables.
And that's that! Hopefully by now you're up and running in some
form--after you add your first entry, open another window in your browser and load
up your log's intended location. You can alter your templates anytime to change any
aspect of your log's design and layout (be sure to "Rebuild Files" after changing
the templates for GreyMatter to automatically update your site accordingly).
Enjoy doing your log, and thanks for using GreyMatter.
By Melanie Cook
I've decided to write this, not to replace the GM Manual, which I find to be extremely useful, but to be used as an adjunct to the GM Manual for those who find installation a bit of a challenge.
Much of the information contained here is also in the GM Installation Instructions, which we are also going to use, in performing this installation. This is intended to be used with the guide, not instead of it!
My work has led me to teach myself to write keystroke by keystroke help for various tasks.
This is simply my effort to assist people with the installation of greymatter, hopefully answering such questions as What are my paths?, and where is Perl, and do I need to know what it is?.
I am also going to assume, in writing this, that you know you have access to a cgi-bin on your server. It doesn't matter if you don't know what it is, just that you have one. You also have to be able to upload and run your own cgi scripts. This also only covers installing greymatter on UNIX based servers.
The FTP software I personally use is WS_FTP. They have a light version available for free. There are lots of other FTP software packages out there. Which you choose is up to you. Any examples I'll give here though, will be from WS_FTP Pro, so any variations from that you'll have to work out for yourself.
I'm also assuming you've already downloaded greymatter. If not you can go here to get the latest version.
Right. With all of that done, we're about ready to start.
You may have already noticed some of the formatting I'll be using in this tutorial. I'll explain them below.
Links Links will be underlined.
Questions Questions, where I'm asking you to determine something, will have a grey background.
Help Help spots, where you can hold your mouse over the highlighted bordered text will provide popup information or explanations.
Code. Where I am telling you to type something into somewhere, I'll use this bordered, green text.
Greymatter boxes. When I want you to see what's in a Greymatter box already, or when I want to show you what's in my Greymatter box, I'll use the bordered mauve background.
We're ready to begin now, so we'll go to stage one.
Set up Greymatter Locally
Setup is probably a little misleading here. We're not actually going to "Setup" greymatter, rather we're going to duplicate your online setup.
If you haven't already done so, create a directory on your hard disk, for your weblog setup. Then create a cgi-bin directory inside the directory you just created, and unzip your Greymatter files into that directory. This is not a "working" cgi-bin. You are not going to be able to run greymatter from here, but it makes sense to store your files in a logical order.
Now create, inside your weblog directory, an archives directory.  This will simplify things later, and hopefully you'll get an understanding of how things work.
Now, I want you to find index.htm, manual.htm, gm-icon.gif and Install.html which should be in the cgi-bin directory and move them out of there and into the weblog directory.
 Are they going to be .htm? .html? .shtml? or .php?
Rename index.htm if you want it to be something other than that. (This is actually step three of the Installation instructions, which we will print next.)
Locate and open the file Install.html, and print it.
Don't worry about what the Requirements say, other than that you must be comfortable with editing HTML. I'll explain the rest to you as you need it. That's the whole purpose of this tutorial.
We're also not going to worry about the next step, Upgrading From Version 1.0 or 1.1, since I'm assuming if you need help with your installation you're not upgrading, but installing from scratch.
So. On to the next part. Installing For The First Time.
The next thing you need to do is locate perl on your webserver.
When you signed up for your domain hosting your host may have sent you a welcome email which included things like "where is perl" or "what and where is my mail program". You also need to know the path of your "home directory". If you have that, fine. If not, go to your domain hosts website, and look for their support or FAQ page, and try to find that information.
It may be on a page related to cgi-bin, or program locations. If you can't find it, and there's a search facility, try searching for perl. If that still doesn't help, send an email to your host asking for "the path to perl and the path to the mail program, and your home directory.".
These will commonly be /usr/bin/perl and /usr/bin/sendmail.
If perl on your server is in a different location, for example /usr/local/bin/perl you will need to edit the "gm.cgi", "gm-karma.cgi", "gm-comments.cgi" and "gm-upload.cgi".
The first line of these files should say "#!/usr/bin/perl". We need to change that to show where perl is on your server, so it says #!/usr/local/bin/perl for example, if that's what your perl path is. You can't use a normal windows editor for this. I use EditPad Lite which is free for non-commercial use. I used this before I got editpad - WinVi32, which is available free. It's a single executable file.
Make the changes to all four files, and save them.
Upload Greymatter
Open your FTP program. If this program uses profiles select the one for your webhost. If not, use your own method of configuring it to connect to your webhost.
There are two ways files can be uploaded using this type of software. ASCII or Binary. Your CGI files must be uploaded as ASCII files, or they won't work.
Upload all files ending in .cgi in ASCII format to your webservers
cgi-bin directory. Also upload the 'libs' directory and all files within to the
your cgi directory. In WS_FTP this is simply a matter of checking the radio button directly
beneath the local and remote windows.
In WS_FTP Pro you are able to click the Options button, and then, on the extensions tab, select the file types you want to automatically upload as ASCII. I have mine set to do .cgi .pl .pm and .txt as ASCII. Everything else will, when you use the auto option, be uploaded as Binary.
NOTE Many people have issues with windows line endings (windows OS uses a different line ending character than other OS's). See the gm_manual file for more information.
Now you need to CHMOD
"gm.cgi", "gm-karma.cgi", "gm-comments.cgi", "gm-upload.cgi" and all files withen the 'libs' directory
(located withen the CGI directory) to 755. If your FTP program has a graphical interface for this, 755 means "rwx r-x r-x". (In WS_FTP right click the file, and then down towards the bottom of the popup menu you'll see chmod (UNIX)) CHMOD all of the other cgi files to 666, which means "-rw -rw -rw".
Upload the files from your local weblog directory, in Binary format, into your online weblog directory.
Now you need to CHMOD your index file to 666.
Make a directory online for your archives, with the same name as the one you made locally. CHMOD this to 777. (That's "rwx rwx rwx") (In WS_FTP you have a MkDir button which will enable you to create a directory on your webserver.) There is an image showing the directory levels here.
Now you're ready to login to Greymatter for the first time. In your web browser, go to the gm.cgi file you uploaded to your cgi-bin. Usually that would be at "http://www.yourdomain.com/cgi-bin/gm.cgi".
If everything did as it was supposed to, you'll be seeing the purple gm login screen.
If you're getting a 500 Server Error, or having other problems, upload your files again, making sure you use ASCII format. CHMOD them again, to make sure they're all CHMODed right. (It's quite simple to do them back to front and get the 4 that are meant to be 755 at 666 and the ones that should be at 666 at 755. I know.. I've done it myself!)
If it's still not working, go back and check the perl path. It must be correct in those four files, or gm.cgi isn't going to be able to find perl, and therefore won't run.
Still no luck, and I'd be checking with my host that my cgi-bin was properly configured. I've heard of hosts who, even though there is a cgi-bin in your directory don't actually configure it to allow files to run until you ask them to. Find out if there are any restrictions on running your own scripts.
Failing that, you've got me stumped. If all of that is set correctly I can think of no reason why greymatter wouldn't be working so far.
There are online Greymatter Forums where you can go to ask for help.
We're continuing now, from the login screen. The default login is Alice, and the password is wonderland.
You're in! You at least got it installed! Congratulations!
Configuring Greymatter
Now you have to configure it. This means we're going to tell it how and where you want everything.
Greymatter assumes that all files for your weblog or journal are going to be in the same directory. We're not going to do that. We're going to have our cgi files in the cgi-bin, and the log and entry files in their own directories. This is why the assumptions greymatter makes below don't suit this installation. To do this click on the Configuration button on the welcome screen.
For the purposes of this tutorial you need to know that on my server
- My perl path is /usr/bin/perl, so I didn't have to edit my cgi files.
- My mail path is /usr/sbin/sendmail.
- My domain is called wiccked.
- My home directory is /home/wiccked/public_html.
Greymatter tells me my
- Local Log Path is: /home/theonion/public_html/wiccked/cgi-bin
- Local Entries/Archives path is: /home/theonion/public_html/wiccked/cgi-bin/archives
- Local CGI Path is: /home/theonion/public_html/wiccked/cgi-bin
- Website Log Path is: http://wiccked.com/cgi-bin
- Website Entries path is: http://wiccked.com/cgi-bin/archives
- Website CGI Path is: http://wiccked.com/cgi-bin
Now, I know, that these are not all correct. I'll copy the correct ones below, and tell you beside them why what greymatter assumed is wrong.
- Local Log Path is: /home/wiccked/public_html - greymatter had assumed the main index page was going to be in the same directory as the cgi-bin.
- Local Entries/Archives path is: /home/theonion/public_html/wiccked/archives - again, gm had assumed the archives directory was to be in the cgi-bin.
- Local CGI Path is: /home/theonion/public_html/wiccked/cgi-bin - This one gm usually gets right.
- Website Log Path is: http://wiccked.com - As in the local log path, gm assumes the main index page is going to be in the cgi-bin.
- Website Entries path is: http://wiccked.com/archives - The same again. The archives aren't in the cgi-bin.
- Website CGI Path is: http://wiccked.com/cgi-bin - And it got this one right too.
I'm not sure why greymatter assumes that the logs and archives are going to be inside the cgi-bin, since most webhosts wouldn't like that at all. But it does, so we fix it. But this seems to be one of the part of configuring greymatter that people find most confusing.
But you've got this far. The hard bit is almost done.
File Names and Archives
Greymatter wants to know now
- Index filename:
The filename of your log/journal's main index. If you enable "Keep archive master index", Greymatter will create that file in the archives directory with the same filename.
index.php or whatever you decided to call it. (make sure it's the same as the file you uploaded!)
- .suffix to entry files:
If you have "Generate pages for individual entries" enabled, this is the suffix those pages will have.
.php (or whatever you decided to use)
- .suffix to log archives:
If you have "Keep monthly/weekly log archives" enabled, this is the suffix those log archive files will have.
.php (again, the extension you decided to use.)
- Days to keep on main index:
The number of days' worth of entries Greymatter will list on your main index before scrolling them off.
When you start setting up your templates, you'll probably include either an extract or complete entries, for however many days you set this to. Mine is set to 7 7
- Generate pages for individual entries?
Specifies whether you want individual entries to have their own pages. Comments are disabled if this is turned off.
Radio button selection of "Yes" or "No "
- Keep archive master index? If enabled, Greymatter will keep an index (with the same filename as above) in your entries/archives directory, intended to be an overview of all your archives.
Radio button selection of "Yes" or "No " (An example of what you get for Yes is here)
- Keep monthly/weekly log archives?
If enabled, Greymatter will keep archive files of your log in monthly or weekly instalments in your entries/archives directory.
Radio button selection of "Yes" or "No " (An example of what you get for yes is here)
- Keep main index and archive log indexes concurrent with each other?
If enabled, both new and archived entries will be listed in the monthly/weekly archives; if disabled, Greymatter won't list entries there until they've scrolled off the main index. For simplicity's sake, it's a good idea leave this on.
Radio button selection of "Yes" or "No "
- Archive by month or week?
If "Keep monthly/weekly log archives" is enabled, this specifies whether the log archives will be generated by the month or by the week.
Radio button selection of "Monthly" or "Weekly"
E-Mail, Karma Voting, and Comments
- E-Mail Options
Options relating to e-mail setup and notification. If you don't plan to have Greymatter send you e-mails, you can safely ignore the "E-Mail Program Location" and "E-Mail(s) to send notices to" fields.
- E-Mail Program Location:
The pointer to the mail program (usually Sendmail) on your account.
/usr/sbin/sendmail (or whatever is appropriate to your own server!)
- E-Mail(s) to send notices to:
The e-mail addresses you want all notifications (if any) to be sent to. Separate multiple e-mail addresses with semicolons.
<EMAIL_ADDRESS>- Send e-mail notifications for:
Indicates whether you want Greymatter to send e-mails notifying you of new karma votes, new comment postings, both karma and comments, or to disable e-mail notification altogether.
Radio Button selection of "New karma votes" "New comments" "Both" "Neither"
- Karma & Comments Options
Options relating to karma voting and comment posting. Obviously, certain options can be ignored if you have their respective functions disabled (for example, if you disable comments or have "Generate pages for individual entries" turned off, none of the options relating to comments will have any effect).
- Allow karma voting and/or comment posting?
Specifies whether you want to permit voting on karma, posting comments, both, or neither, on your site. You can leave them enabled and still turn karma or comments on or off for individual entries; to disable either or both will override that for ALL entries.
Radio Button selection of "Karma only" "Comments only" "Both" "Neither"
- Order of comments on entry pages:
The order in which you want comments displayed. If "ascending", they'll be listed from newest to oldest, with the newest comment at the top; if "descending", from first to last, with the first comment at the top.
Radio Button selection of "Ascending" "Descending"
- Can post comments and vote on karma in archives?
If enabled, visitors can cast karma votes or post comments (if applicable) on entries no longer listed on the main index. Enabling this may slow down your site over time.
If you answer Yes to this question people will NOT be able to cast karma votes or post comments once an entry has gone from your main index page. If you have only one entry on your main index page that is all that will allow comments to be posted!
Radio Button selection of "Yes" "No"
- Karma voting on by default?
Specifies whether "Allow karma voting on this entry" is preselected to "Yes" or "No" by default on the "Add a new entry" screen.
Radio Button selection of "Yes" "No"
- Comment posting on by default?
Specifies whether "Allow comments to be posted to this entry" is preselected to "Yes" or "No" by default on the "Add a new entry" screen.
Radio Button selection of "Yes" "No"
- HTML allowed in comments?
Indicates whether you want to allow visitors to include HTML codes in their comments, or to have Greymatter strip them out. You can also specify whether only the codes for links, bold and italics can be included, or just the codes for links.
Radio button selection of "All HTML allowed" "No HTML allowed" "Linking, Bold & Italic code only" "Linking code only"
- Auto-link URLs in comments?
If enabled, Greymatter will automatically link to any website or e-mail addresses that users post in their comments (unless you've enabled linking above and they've already linked the website/e-mail address themselves).
Radio Button selection of "Yes" "No"
- Strip new lines from comments?
If enabled, all line and paragraph breaks are stripped when displaying visitors' comments, turning them into unbroken blocks of text; if disabled, Greymatter preserves the visitors' original formatting.
Radio Button selection of "Yes" "No"
- Allow multiple karma votes from same IP?
If enabled, the same visitor could cast multiple karma votes on the same entry; if disabled, only one vote per visitor is allowed.
Radio Button selection of "Yes" "No"
- Mention it in the control panel log when comments and karma votes are added?
Enable this if you want Greymatter to mention all new comments and karma votes in the control panel log.
Radio Button selection of "Yes" "No"
- Date & Time Options
Miscellaneous options regarding to dates & times. Use the wide variety date and time variables in your templates to fine-tune how you want the date and time to appear on your site.
- Server Offset Time:
As of this moment, Greymatter reads your time as 6:13 AM. If this is incorrect, specify the number of hours to add or subtract from this time (to subtract, make it a negative number, with a minus in front of it).
If you know where your server is located, you need to take the day into account too. If Greymatter is telling you the server time is 6:13 AM, and you know that because of your geographical location and that of your server that this is on a different day your time difference needs to reflect this. My time is 9:13 PM, so I need to set the time offset as +15, since there are 15 hours difference between my server time, and my local time. This can be quite complicated to work out, and it may take a couple ot tries to ensure you end up with the correct time and date on your entries. Test entries are good to use for this.
15
- Your Time Zone:
The time zone you live in. This is what will appear wherever you use the {{timezone}} variable in your templates.
(Enter your own time zone. Remember to allow for daylight savings here. If your server changes time for daylight savings this may need to be reset at the start and end of daylight savings time.)
AEST
- File Uploading Options
Options relating to uploading files from within Greymatter.
- Allowed File Types:
If you only wish to allow certain types of files to be uploaded, enter their file suffixes here. Separate allowed file types by semicolons (for example, "jpg;gif;zip"). Leave this blank to allow any type of file to be uploaded.
- Maximum Filesize Allowed:
If you don't wish to allow files larger than a certain size to be uploaded, specify that limit here (in KB/kilobytes). Leave this on "0" to allow files of any size to be uploaded.
KB
- Censoring Options
Words or phrases you want to censor on your site (if any), and where to censor them.
Censored terms will be turned into "*" asterisks.
- Enable censoring?
Specifies whether you want any words or phrases in your censor list to appear censored for entries, comments, or both. Leave it on "Neither" to disable censorship.
Radio button selection of "Entries only" "Comments only" "Both" "Neither"
- Censor List
Enter any words or phrases you want to censor, separated by lines (press return after each word/phrase).
- Connect Other Files (Advanced Users Only) * I will add further explanations to this at a later date.
If you wish, you can connect other files on your account to Greymatter, and have them treated as if they were one of Greymatter's regular index files; for example, using {{header}} or {{footer}} in another file to insert your Greymatter header or footer into that file. (You'll need to edit & upload these files to your account outside Greymatter.) This is only recommended for advanced users that are already comfortable using Greymatter.
- Filename List
To connect a file to Greymatter, CHMOD it to 666 making sure it contains whatever Greymatter variables you wish and enter its filename on the right; place each filename on separate lines. If the file isn't in the same directory as gm.cgi, then use virtual paths relative to where it's running from. For example, if you want to connect "test.htm" and it's in the directory above gm.cgi, you'd use ../test.htm; or, if you run gm.cgi from /here/cgi-bin and test.htm was in /there/log, you'd use ../../there/log ("../" means to go up one directory). Greymatter will automatically create a "pattern" file in your entries directory for each filename, and whenever you reupload a changed file, Greymatter will automatically update its stored pattern for that file.
- Update them when adding entries?
If "Yes", then Greymatter will automatically update any of the connected files above when new entries are added; if not, they'll only be updated whenever you rebuild them (either specifically, or by rebuilding everything).
Radio Button selection of "Yes" "No"
- Miscellaneous Options
- Enable cookies?
By default, Greymatter keeps a cookie on your browser that remembers your name and password, so you don't have to type them in each time you log on. To disable and delete Greymatter's cookies, select "No" and check the checkbox.
If you use a shared computer, and do not want others to have access to Greymatter you should set this to No, and tick the box.
Radio Button selection of "Yes" "No", and "Delete cookies set by Greymatter?" tickbox.
- Keep control panel log?

Radio Button selection of "Yes" "No"
- Allow "easy formatting"?
With "easy formatting", bold text, italics & underlining can be done easily by bracketing text with two **asterisks**, \\backslashes\\ or __underlines__ respectively. You can specify whether this is enabled in entries, comments, or both; if disabled, the characters won't be converted.
Radio Button selection of "Entries only" "Comments only" "Both" "Neither"
- Default entry list view:
This specifies which view will be the default when you go to the Edit An Entry selection menu.
Under normal use Current entries is probably fine. If you need to edit a lot of entries outside that range, temporarily change this option
Selection list choice of "Current entries (7 days)" "All entries by you" "All extended entries" "All open entries" "All closed entries" "All entries"
- Order of list links:
The order in which you want links to be displayed in log list variables, check the manual for more information on those. If "ascending", the links will be listed from newest to oldest, with the newest entry at the top; if "descending", from first to last, with the first entry at the top.
Radio Button selection of "Ascending" "Descending"
- Log entry list variable number:
The number of entries to link to, starting from the most recent, whenever the "number" variant of the log entrylist variables (for example, if this is set to 5, using {{logmoreentrylist number}} would generate a list of links to the five most recent extended entries). Check the manual for more information on those variables.
- Link to entries in {{logentrylist comments}} only if comments are active?
If you use {{logentrylist comments}} and its related variables (see the manual for more information), this specifies whether to list only entries to which comments can still be posted.
Radio Button selection of "Yes" "No"
- Entries to link to in {{calendar}}:
Whenever you use {{calendar}} or {{calendarweek}} to generate tables linking to your entries, this specifies whether you want to link to the most recent entry for that day, or to link only to extended entries. (It won't generate links at all if "Generate pages for individual entries" is turned off.)
Radio Button selection of "Always link to entry for that calendar day" "Link only to extended entries"
- "Automatically rebuild" selected by default?
Selects whether the option to automatically rebuild files after saving changes to templates or entries is prechecked by default. (Authors without access to rebuilding files won't see this option.)
Radio Button selection of "Yes" "No"
Now you've configured Greymatter you need to run diagnostics & repair to ensure that all of the paths and permissions are correct. Click on the Diagnostics & Repair button.
Once you click the next button, Greymatter will check that it is able to run correctly, and that it is able to write to the directories required to add your entries etc. Click the Peform Diagnostics & Repair button.
Greymatter will hopefully report that Diagnostics & Repair Complete
All operations were completed successfully. Greymatter successfully checked and/or performed the following:
- All config files are readable/writeable and are CHMODed correctly
- The local CGI path is correctly configured and all essential files are there
- The entries/archives path is readable/writeable and is CHMODed correctly
- The main index file is readable/writeable and is CHMODed correctly
If any errors are reported, read them carefully. They should provide you with enough information to correct them. For example, if you are told that Greymatter can't write to /home/theonion/public_html/wiccked/cgi-bin/archives/ you have probably got the local archives path set incorrectly. Change it to leave "cgi-bin" out of the path, then re-run the diagnostics program.
If the path is correct but Greymatter is telling you it can't write to the directory CHMOD it again, ensuring permissions are set as laid out in the Upload Greymatter section of this tutorial.
Once all is correct you can Return to Main Menu
Your Greymatter installation still only has Alice as the default author, so we select Edit Authors to add you, and to delete Alice. Add yourself before you delete Alice. Don't delete Alice until you've successfully logged in as yourself.
Fill in the "Register a New Author" box.
Enter the appropriate details into the
Name: Password: Email: Homepage: boxes.
Set the "Default Author Access" for this Author.
Radio button selection of "All access" "No access" "Post & edit their own entries only" and then click the Create Author button.
When you have added all the authors you want to add click the Return to Main Menu button.
Click the Re-Login button.
Enter your own author details, and login.
You can now go back into Edit Authors and delete Alice, by selecting Alices radio button, and clicking the Delete Selected Author button.
You're ready to start setting up your templates now. The simplest place to start is by adding an entry. Don't write your life story or anything, just make it a very brief first entry. This will enable you to see what formatting is there.
From here, if you're comfortable continuing with the templates by yourself, have fun. Enjoy Greymatter, and please let me know if you found this useful, or if you have any suggestions for something you'd like to see added here.
Copyright (c)2000-2006 The GreyMatter Team. All rights reserved.
|


How I Built My Own 3D Printer With No Experience by Shafiq Ali
"I'll probably talk about my thoughts about 3D printing and getting into 3D printing from a non-engineer's point of view."
{{ define "title" }}This coming Friday{{ end }} {{ define "content" }}
"I'll probably talk about my thoughts about 3D printing and getting into 3D printing from a non-engineer's point of view."


Oregon Language Access Webtool
Oregon State
Click on map to review county statistics.POPULATION 5+ IN LIMITED ENGLISH SPEAKING HOUSEHOLDS
Survey/Program: American Community Survey
Universe: Population 5 years and over in households in which no one 14 and over speaks English only or speaks a language other than English at home and speaks English very well
TableID: B16003
Product: 2017: ACS 5-Year Estimates Detailed Tables
LANGUAGE SPOKEN AT HOME FOR THE POPULATION 5 YEARS AND OVER
Survey/Program: American Community Survey
Universe: Population 5 years and over
TableID: C16001
Product: 2017: ACS 5-Year Estimates Detailed Tables


Joe's Coffee Store
Home
Blog
Our Coffees
Accessories
Gifts
Find us
Checkout
Welcome to Joe's Coffee Store! hello world
Welcome to our store, our goal is to exchange some second hand toys online.
Note that our store is closed on Christmas eve and Christmas day.
Bestsellers @ Joe's Coffee Store
Coffees
Coffee 1
$10
Add to Cart
Coffee 2
$10
Add to Cart
Coffee 3
$10
Add to Cart
Coffee 4
$10
Add to Cart
Accessories
Coffee 1
$10
Add to Cart
Coffee 1
$10
Add to Cart
Coffee 1
$10
Add to Cart


After reading and thinking about worldviews and how they affect how we act and think about ourselves and each other, consider your own worldviews and what has shaped them. Write an essay that explains your worldviews and how you think they were formed.
This is a personal essay that will require some serious self-reflection and critical thinking. Examining your own worldview and its context is not an easy exercise and requires a lot of deep thinking, much of which may be uncomfortable. Be prepared for this and be willing to challenge yourself.
● The essay should be at least 1200 words with fully-developed ideas and details.
● You must answer all questions asked in each section below.
● You do not have to use sources for the essay, but you should use your readings and the videos you watched to inform your ideas.
Write an introduction that describes your personal, social, and cultural identities. Make sure that you include all three of these parts of your identity, including one or two examples of each (more is fine). This introduction should be at least 200 words long.
Summarize your worldview. Be honest. Examine your beliefs without judgment. Include all four of the following categories. This section should be approximately 400 words (more is fine)
● How do you acquire most of your knowledge (epistemology)?
● What are some examples of things you believe are true or not true (ontology)?
● What do you believe is important/trivial, good/bad, fair/unfair? What do you hope for, for yourself or for the world (axiology)?
● How do you see yourself in relation to the world or to other people (cosmology)? This might include your religious faith or lack of religion, but it could also relate to your general idea of yourself as connected or not connected to other people. Are you more of an individualist (you believe your success depends on yourself, or you do things primarily for your benefit) or more of a collectivist (you believe your success is connected to others, or you concentrate on how your actions benefit others)?
Where did you acquire your worldviews? Our beliefs often owe nothing to logic, but we believe what we believe for a reason, based on how we’ve taught how to live our lives. Again, be honest, and examine these experiences and relationships without judgment. This section should be approximately 400 words (more is fine).
● What relationships in your life have formed your belief system? These could include family, friends, or other significant individuals--your social identities. Think about what these people have said or the way they have treated you.
● What experiences in your life led you to believe what you believe? These could include significant events in your life, or just events that have happened to you consistently. Think about how your personal identities were formed.
● What structures from the world around you have influenced your belief system? These could include your cultural, ethnic, language, national, or religious background, or other parts of you that you were born with or were decided for you--things that have formed your cultural identities.
Close your essay by explaining which parts of your experience or identities have the most significant impact on your worldview. Explain why you believe these things are the most important or significant. This section should be at least 200 words.
Attached to the end of your essay in the same document, type an essay memo of at least 100 words (more is good) that answers the following questions:
● Who else saw your essay during your writing process? (writing center consultants, friends, family members?)
● How long did your writing process take from beginning to end?
● What are the strengths and weaknesses of your essay?
● What were your triumphs (things you enjoyed or did well with) and struggles during your writing process?
● What grade would you give your essay, and why?


The Native Memory Tracking (NMT) is a Java HotSpot VM feature that tracks internal memory usage for a Java HotSpot VM. For details about NMT scope, how to enable NMT, and other additional usage details, see Native Memory Tracking.
Since NMT doesn't track memory allocations by non-JVM code, you may have to use tools supported by the operating system to detect memory leaks in native code.
The following sections describe how to monitor VM internal memory allocations and diagnose VM memory leaks.
Follow these steps to detect a memory leak.
Start the JVM with summary or detail tracking using the command line option: -XX:NativeMemoryTracking=summary
or -XX:NativeMemoryTracking=detail
.
Establish an early baseline - use NMT baseline feature to get a baseline to compare during development and maintenance by running: jcmd <pid> VM.native_memory baseline
.
Monitor memory changes using: jcmd <pid> VM.native_memory detail.diff
.
If the application leaks a small amount of memory, it make take a while to show up.
Used with The jcmd Utility, Native Memory Tracking can be set up to monitor memory and ensure that an application does not start to use increasing amounts of memory during development or maintenance. See Table 2-1 for details about NMT memory categories.
The following sections describe how to get summary or detail data for NMT and describes how to interpret the sample output.
Interpret sample output: From the sample output below, you will see reserved and committed memory. Note that only committed memory is actually used. For example, if you run with -Xms100m -Xmx1000m
, the JVM will reserve 1000 MB for the Java Heap. Since the initial heap size is only 100 MB, only 100MB will be committed to begin with. For a 64-bit machine where address space is almost unlimited, there is no problem if a JVM reserves a lot of memory. The problem arises if more and more memory gets committed, which may lead to swapping or native OOM situations.
Arena is a chunk of memory allocated using malloc. Memory is freed from these chunks in bulk, when exiting a scope or leaving an area of code. These chunks may be reused in other subsystems to hold temporary memory, for example, pre-thread allocations. Arena malloc policy ensures no memory leakage. So Arena is tracked as a whole and not individual objects. Some amount of initial memory can not by tracked.
Enabling NMT will result in a 5-10 percent JVM performance drop and memory usage for NMT adds 2 machine words to all malloc memory as malloc header. NMT memory usage is also tracked by NMT.
Get summary data: To get a summary view of native memory usage, start the JVM with command line option: -XX:NativeMemoryTracking=summary
.
Example 2-2 is a sample output that describes NMT for track level set to summary. One way to get this sample output is to run: jcmd <pid> VM.native_memory summary
.
Example 2-2 Get Summary Data for NMT
Total: reserved=664192KB, committed=253120KB <--- total memory tracked by Native Memory Tracking - Java Heap (reserved=516096KB, committed=204800KB) <--- Java Heap (mmap: reserved=516096KB, committed=204800KB) - Class (reserved=6568KB, committed=4140KB) <--- class metadata (classes #665) <--- number of loaded classes (malloc=424KB, #1000) <--- malloc'd memory, #number of malloc (mmap: reserved=6144KB, committed=3716KB) - Thread (reserved=6868KB, committed=6868KB) (thread #15) <--- number of threads (stack: reserved=6780KB, committed=6780KB) <--- memory used by thread stacks (malloc=27KB, #66) (arena=61KB, #30) <--- resource and handle areas - Code (reserved=102414KB, committed=6314KB) (malloc=2574KB, #74316) (mmap: reserved=99840KB, committed=3740KB) - GC (reserved=26154KB, committed=24938KB) (malloc=486KB, #110) (mmap: reserved=25668KB, committed=24452KB) - Compiler (reserved=106KB, committed=106KB) (malloc=7KB, #90) (arena=99KB, #3) - Internal (reserved=586KB, committed=554KB) (malloc=554KB, #1677) (mmap: reserved=32KB, committed=0KB) - Symbol (reserved=906KB, committed=906KB) (malloc=514KB, #2736) (arena=392KB, #1) - Memory Tracking (reserved=3184KB, committed=3184KB) (malloc=3184KB, #300) - Pooled Free Chunks (reserved=1276KB, committed=1276KB) (malloc=1276KB) - Unknown (reserved=33KB, committed=33KB) (arena=33KB, #1)
Get detail data: To get a more detailed view of native memory usage, start the JVM with command line option: -XX:NativeMemoryTracking=detail
. This will track exactly what methods allocate the most memory. Enabling NMT will result in 5-10 percent JVM performance drop and memory usage for NMT adds 2 words to all malloc memory as malloc header. NMT memory usage is also tracked by NMT.
Example 2-3 shows a sample output for virtual memory for track level set to detail. One way to get this sample output is to run: jcmd <pid> VM.native_memory detail
.
Example 2-3 Get detail Data for NMT
Virtual memory map: [0x8f1c1000 - 0x8f467000] reserved 2712KB for Thread Stack from [Thread::record_stack_base_and_size()+0xca] [0x8f1c1000 - 0x8f467000] committed 2712KB from [Thread::record_stack_base_and_size()+0xca] [0x8f585000 - 0x8f729000] reserved 1680KB for Thread Stack from [Thread::record_stack_base_and_size()+0xca] [0x8f585000 - 0x8f729000] committed 1680KB from [Thread::record_stack_base_and_size()+0xca] [0x8f930000 - 0x90100000] reserved 8000KB for GC from [ReservedSpace::initialize(unsigned int, unsigned int, bool, char*, unsigned int, bool)+0x555] [0x8f930000 - 0x90100000] committed 8000KB from [PSVirtualSpace::expand_by(unsigned int)+0x95] [0x902dd000 - 0x9127d000] reserved 16000KB for GC from [ReservedSpace::initialize(unsigned int, unsigned int, bool, char*, unsigned int, bool)+0x555] [0x902dd000 - 0x9127d000] committed 16000KB from [os::pd_commit_memory(char*, unsigned int, unsigned int, bool)+0x36] [0x9127d000 - 0x91400000] reserved 1548KB for Thread Stack from [Thread::record_stack_base_and_size()+0xca] [0x9127d000 - 0x91400000] committed 1548KB from [Thread::record_stack_base_and_size()+0xca] [0x91400000 - 0xb0c00000] reserved 516096KB for Java Heap <--- reserved memory range from [ReservedSpace::initialize(unsigned int, unsigned int, bool, char*, unsigned int, bool)+0x190] <--- callsite that reserves the memory [0x91400000 - 0x93400000] committed 32768KB from [VirtualSpace::initialize(ReservedSpace, unsigned int)+0x3e8] <--- committed memory range and its callsite [0xa6400000 - 0xb0c00000] committed 172032KB from [PSVirtualSpace::expand_by(unsigned int)+0x95] <--- committed memory range and its callsite [0xb0c61000 - 0xb0ce2000] reserved 516KB for Thread Stack from [Thread::record_stack_base_and_size()+0xca] [0xb0c61000 - 0xb0ce2000] committed 516KB from [Thread::record_stack_base_and_size()+0xca] [0xb0ce2000 - 0xb0e83000] reserved 1668KB for GC from [ReservedSpace::initialize(unsigned int, unsigned int, bool, char*, unsigned int, bool)+0x555] [0xb0ce2000 - 0xb0cf0000] committed 56KB from [PSVirtualSpace::expand_by(unsigned int)+0x95] [0xb0d88000 - 0xb0d96000] committed 56KB from [CardTableModRefBS::resize_covered_region(MemRegion)+0xebf] [0xb0e2e000 - 0xb0e83000] committed 340KB from [CardTableModRefBS::resize_covered_region(MemRegion)+0xebf] [0xb0e83000 - 0xb7003000] reserved 99840KB for Code from [ReservedSpace::initialize(unsigned int, unsigned int, bool, char*, unsigned int, bool)+0x555] [0xb0e83000 - 0xb0e92000] committed 60KB from [VirtualSpace::initialize(ReservedSpace, unsigned int)+0x3e8] [0xb1003000 - 0xb139b000] committed 3680KB from [VirtualSpace::initialize(ReservedSpace, unsigned int)+0x37a] [0xb7003000 - 0xb7603000] reserved 6144KB for Class from [ReservedSpace::initialize(unsigned int, unsigned int, bool, char*, unsigned int, bool)+0x555] [0xb7003000 - 0xb73a4000] committed 3716KB from [VirtualSpace::initialize(ReservedSpace, unsigned int)+0x37a] [0xb7603000 - 0xb760b000] reserved 32KB for Internal from [PerfMemory::create_memory_region(unsigned int)+0x8ba] [0xb770b000 - 0xb775c000] reserved 324KB for Thread Stack from [Thread::record_stack_base_and_size()+0xca] [0xb770b000 - 0xb775c000] committed 324KB from [Thread::record_stack_base_and_size()+0xca]
Get diff from NMT baseline: For both summary and detail level tracking, you can set baseline once the application is up and running. Do this by running jcmd <pid> VM.native_memory baseline
after some warm up of the application. Then, you can run: jcmd <pid> VM.native_memory summary.diff
or jcmd <pid> VM.native_memory detail.diff
.
Example 2-4 shows a sample output for the summary difference in native memory usage since the baseline and is a great way to find memory leaks.
Example 2-4 Get diff from NMT Baseline
Total: reserved=664624KB -20610KB, committed=254344KB -20610KB <--- total memory changes vs. earlier baseline. '+'=increase '-'=decrease - Java Heap (reserved=516096KB, committed=204800KB) (mmap: reserved=516096KB, committed=204800KB) - Class (reserved=6578KB +3KB, committed=4530KB +3KB) (classes #668 +3) <--- 3 more classes loaded (malloc=434KB +3KB, #930 -7) <--- malloc'd memory increased by 3KB, but number of malloc count decreased by 7 (mmap: reserved=6144KB, committed=4096KB) - Thread (reserved=60KB -1129KB, committed=60KB -1129KB) (thread #16 +1) <--- one more thread (stack: reserved=7104KB +324KB, committed=7104KB +324KB) (malloc=29KB +2KB, #70 +4) (arena=31KB -1131KB, #32 +2) <--- 2 more arenas (one more resource area and one more handle area) - Code (reserved=102328KB +133KB, committed=6640KB +133KB) (malloc=2488KB +133KB, #72694 +4287) (mmap: reserved=99840KB, committed=4152KB) - GC (reserved=26154KB, committed=24938KB) (malloc=486KB, #110) (mmap: reserved=25668KB, committed=24452KB) - Compiler (reserved=106KB, committed=106KB) (malloc=7KB, #93) (arena=99KB, #3) - Internal (reserved=590KB +35KB, committed=558KB +35KB) (malloc=558KB +35KB, #1699 +20) (mmap: reserved=32KB, committed=0KB) - Symbol (reserved=911KB +5KB, committed=911KB +5KB) (malloc=519KB +5KB, #2921 +180) (arena=392KB, #1) - Memory Tracking (reserved=2073KB -887KB, committed=2073KB -887KB) (malloc=2073KB -887KB, #84 -210) - Pooled Free Chunks (reserved=2624KB -15876KB, committed=2624KB -15876KB) (malloc=2624KB -15876KB)
Example 2-5 is a sample output that shows the detail difference in native memory usage since the baseline and is a great way to find memory leaks.
Example 2-5 Get detail diff for NMT
Details: [0x01195652] ChunkPool::allocate(unsigned int)+0xe2 (malloc=482KB -481KB, #8 -8) [0x01195652] ChunkPool::allocate(unsigned int)+0xe2 (malloc=2786KB -19742KB, #134 -618) [0x013bd432] CodeBlob::set_oop_maps(OopMapSet*)+0xa2 (malloc=591KB +6KB, #681 +37) [0x013c12b1] CodeBuffer::block_comment(int, char const*)+0x21 <--- [callsite address] method name + offset (malloc=562KB +33KB, #35940 +2125) <--- malloc'd amount, increased by 33KB #malloc count, increased by 2125 [0x0145f172] ConstantPool::ConstantPool(Array<unsigned char>*)+0x62 (malloc=69KB +2KB, #610 +15) ... [0x01aa3ee2] Thread::allocate(unsigned int, bool, unsigned short)+0x122 (malloc=21KB +2KB, #13 +1) [0x01aa73ca] Thread::record_stack_base_and_size()+0xca (mmap: reserved=7104KB +324KB, committed=7104KB +324KB)


What's the difference between this and Basic? When would you use something that disables two of the options off the bat?


2 Samuel 24:11
For when David was up in the morning, the word of the LORD came unto the prophet Gad, David's seer, saying,


MEGIDDO: THE OMEGA CODE 2 A film review by Steve Rhodes Copyright 2001 Steve Rhodes RATING (0 TO ****): **
MEGIDDO: THE OMEGA CODE 2 is about old struggles: good vs. evil, feast vs. famine, health vs. pestilence, nationalism vs. world government and benevolent dictatorship vs. democracy. It's also about the contrast between the handsomeness of the film and the way that it's so overacted and ridiculously scripted that it's sometimes kind of fun.
When we first meet Stone Alexander, he's a little devil, literally. His first overt act of destruction is to torch his baby brother while he is in his crib. With all of the emotive power of a department store mannequin, Gavin Fink plays this younger Stone. Chad Michael Allen isn't much better as Stone in his late teens and early twenties.
The bulk of the story occurs when the grown-up Stone (Michael York) has just gotten himself a promotion from head of the European Union to the first Chancellor of the World Union. His program consists of one world, one government, one goal and one language -- hint, it's not Chinese. The pesky Americans balk at joining Stone's party. As one of the presidential aide's puts it, Stone is "Adolf Hitler but with an attitude."
York, who is a quite capable actor perhaps best known for playing Tybalt in Franco Zeffirelli's ROMEO AND JULIET, is incredibly bad as the older Stone. Why York felt he had to camp it up isn't clear since the movie clearly wants to be taken seriously. (The music, which doesn't have a subtle note, reinforces the gravity of the situations.) Much better is Michael Biehn, who play's Stone's brother David, who survived his burning bed BBQ. Diane Venora plays Stone's wife, Gabriella, who finally parts with him when she catches him barfing bees.
Of course, the movie will move towards a cataclysmic conclusion that might mean the end of the world. That part contains my favorite scene as Stone sheds his worldly body and becomes a really cool looking gargoyle. It's a moment to remember.
MEGIDDO: THE OMEGA CODE 2 runs 1:42. It is rated PG-13 for "violence, warfare and some thematic elements" and would be acceptable for kids around 10 and up.
The film opens in limited release in the United States today, Friday, September 28, 2001. In the Silicon Valley, it is showing at the AMC theaters.
Web: http://www.InternetReviews.com Email<EMAIL_ADDRESS>Want free reviews and weekly movie and video recommendations via Email? Just send me a letter with the word "subscribe" in the subject line.
========== X-RAMR-ID: 29631 X-Language: en X-RT-ReviewID: 252172 X-RT-TitleID: 1110000 X-RT-SourceID: 703 X-RT-AuthorID: 1271
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


| Home | Libraries | People | FAQ | More |
Exactly one of the following must always be set for POSIX
extended regular expressions:
对于 POSIX扩展正则表达式，下面标签中必须设置一个：
|
Element 元素 |
Standardized 标准化 |
Effect when set 设置后的作用 |
|---|---|---|
|
extended |
Yes |
Specifies that the grammar recognized by the regular expression
engine is the same as that used by POSIX extended regular expressions
in IEEE Std 1003.1-2001, Portable Operating System Interface
(POSIX ), Base Definitions and Headers, Section 9, Regular Expressions
(FWD.1).
Refer to the POSIX
extended regular expression guide for more information.
In addition some perl-style escape sequences are supported (The
POSIX standard specifies that only "special" characters
may be escaped, all other escape sequences result in undefined
behavior). |
|
egrep |
Yes |
Specifies that the grammar recognized by the regular expression
engine is the same as that used by POSIX utility grep when given
the -E option in IEEE Std 1003.1-2001, Portable Operating System
Interface (POSIX ), Shells and Utilities, Section 4, Utilities,
grep (FWD.1).
That is to say, the same as POSIX
extended syntax, but with the newline character acting
as an alternation character in addition to "|". |
|
awk |
Yes |
Specifies that the grammar recognized by the regular expression
engine is the same as that used by POSIX utility awk in IEEE
Std 1003.1-2001, Portable Operating System Interface (POSIX ),
Shells and Utilities, Section 4, awk (FWD.1).
That is to say: the same as POSIX
extended syntax, but with escape sequences in character
classes permitted.
In addition some perl-style escape sequences are supported (actually
the awk syntax only requires \a \b \t \v \f \n and \r to be recognised,
all other Perl-style escape sequences invoke undefined behavior
according to the POSIX standard, but are in fact recognised by
Boost.Regex). |
The following options may also be set when using POSIX extended regular
expressions:
使用POSIX扩展正则表达式时下面选项可以被设置：
|
Element 元素 |
Standardized 标准化 |
Effect when set 设置后的作用 |
|---|---|---|
|
icase |
Yes |
Specifies that matching of regular expressions against a character
container sequence shall be performed without regard to case. |
|
nosubs |
Yes |
Specifies that when a regular expression is matched against a
character container sequence, then no sub-expression matches
are to be stored in the supplied |
|
optimize |
Yes |
Specifies that the regular expression engine should pay more
attention to the speed with which regular expressions are matched,
and less to the speed with which regular expression objects are
constructed. Otherwise it has no detectable effect on the program
output. This currently has no effect for Boost.Regex. |
|
collate |
Yes |
Specifies that character ranges of the form |
|
newline_alt |
No |
Specifies that the \n character has the same effect as the alternation
operator |. Allows newline separated lists to be used as a list
of alternatives. |
|
no_escape_in_lists |
No |
When set this makes the escape character ordinary inside lists,
so that |
|
no_bk_refs |
No |
When set then backreferences are disabled. This bit is on by
default for POSIX-Extended regular expressions, but can be unset
to support for backreferences on. |
|
no_except |
No |
Prevents |
|
save_subexpression_location |
No |
When set then the locations of individual sub-expressions within
the original regular expression string can
be accessed via the |


---
layout: post
title: Revit- Select All Structural Framing at Reference Level
date: '2015-04-29T09:53:00.001-07:00'
author: JohnP
tags:
modified_time: '2015-04-29T09:54:33.891-07:00'
thumbnail: http://lh3.googleusercontent.com/-L9PNFhTO7hc/VUEMh2IwxMI/AAAAAAAAAJk/gvgnme7lBHw/s72-c/2015-04-28_06h58_47_thumb.png?imgmax=800
blogger_id: tag:blogger.com,1999:blog-8275462422374771907.post-1311580243420341788
blogger_orig_url: http://sixtysecondrevit.blogspot.com/2015/04/revit-select-all-structural-framing-at.html
---
A question came up on the DynamoBIM forums the other day about how to select all framing at a level. Framing is a little weird, so I came up with this node that lets you select all framing at a giving Reference level.
It is now available on Rhythm.


{% extends 'layout.html' %} {% block content %}
Dodo now has permission to unfollow accounts on your behalf. Make sure you've added a Twitter list with the word 'Dodo' in the title so you can start following and adding users to it!


modern.
about & contacts
Helena bar
Interior designer
Architect, I graduated in 2008 at IUAV University in venice. My passion for interiors and design was realized in London. Where I attended a Master course for retail and exhibit design at Central Saint Martins College of Art and Design.
Phone +83<PHONE_NUMBER>


Learning From Related Devices
Quarks enables connected devices to learn from related devices. For example, a truck maneuvering roads in Oregon can adjust based on the data received from trucks operating under similar loads and conditions in Colorado; data such as altitude, cargo, weather and traffic conditions.


Here is a cat picture instead!
{{ object.title}} from {{ object.owner }}
From http://icanhascheezburger.com/