> For the complete documentation index, see [llms.txt](https://docs.iceteagroup.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iceteagroup.com/general/framework/extensions/named-properties.md).
# Named Properties
Some SQLWindows/Team Developer applications use Named Properties (also knows as Quick Objects properties) to store custom information in the outline. Usually these properties have been used by developers to persist custom settings using custom developed configuration editors.
Named Properties are ported into the InitializeComponent() method and loaded into the NamedProperties collection. It is already a big advantage to be able to see the Named Properties directly in the code. The PPJ Framework implements a default editor for the NamedProperties collection that can be used to edit all the properties assigned to a control.
The editor is associated to the NamedProperties property and can be started from the property editor in Visual Studio, as shown in the image below:
The editor is very simple and uses Visual Studio's standard editor dialog, shown in the image below. It is possible to implement a custom editor using the *System.ComponentModel* classes and attributes to override the PPJ Framework default editor.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.iceteagroup.com/general/framework/extensions/named-properties.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
