سلامنقل قول:
دوست جون درخواستتون رو اینجا مطرح کنید. شاید زودتر جواب بگیرید. :thumbsdow
موفق باشید :11:کد:http://www.p30world.com/forum/showthread.php?t=40756&page=237
Printable View
سلامنقل قول:
دوست جون درخواستتون رو اینجا مطرح کنید. شاید زودتر جواب بگیرید. :thumbsdow
موفق باشید :11:کد:http://www.p30world.com/forum/showthread.php?t=40756&page=237
امیر جان سلامنقل قول:
اون تیکه که رنگی کردم رو بهتر نیست بگی : " من از ملاقات کردن (مصاحبت) افراد جالب و حیرت انگیز در (سایت؟) تگد لذت میبرم"؟؟
موفق باشید :11:
سلام از ماستنقل قول:
فکر می کنم تقریباً همون باشه .... ولی خوب شما استادید و ... بله ، اونی که شما نوشتید یقیناً بهتره (بدون تعارف عرض می کنم)
ضمناً من نمی دونستم Tagged اسم یک سایت اینترنت هست.
ارادتمندم [ برای مشاهده لینک ، با نام کاربری خود وارد شوید یا ثبت نام کنید ]
dear @mir
ممنون که وقت گذاشتی شما که زحمت کشیدی میشه این چند خط دیگه رو هم ترجمه کنید.
now , however, thanks to simple application of statistical methods , a solution is at hand for kitchens all around the world. we will be making use of the underlying modelling approach of regression analysis , altough our analysis is not intended to enable any statistical inference, and our data do not likely meet the assumption of bivariate regression .making use of some easy data collection methods and the predictive tools of ordinary least squares analysis , it is possible to predict with considerable accuracy , and hours a head of time , when a turkey will be ready to eat .
if parents ever ask their kids if they are learning any thing practical in school, this analysis will satisfy even the most demanding .
the first step is to make sure you have a meat thermometer to use.many type of this are available . some stay in the intire time , some just get inserted for a minute when taking the tempreture
بچه ها سلام من دارم یه مقاله در مورد دلفی ترجمه می کنم خیلیش رو ترجمه کردم و خیلی مونده اما چون وقت کم دارم تیکه تیکه جدا جدا میزارم تا کمکم کنید
واقعا ممنون
کد:Many components are provided in the IDE on the Component palette. You select components from the Component palette and drop them onto a form or data module. You design the application's user interface by arranging the visual components such as buttons and list boxes on a form. You can also place nonvisual components such as data access components on either a form or a data module.
At first glance, Delphi's components appear to be just like any other classes. But there are differences between components in Delphi and the standard class hierarchies that many programmers work with. Some differences are described here:
All Delphi components descend from TComponent.
Components are most often used as is and are changed through their properties, rather than serving as "base classes" to be subclassed to add or change functionality. When a component is inherited, it is usually to add specific code to existing event handling member functions.
Components can only be allocated on the heap, not on the stack.
Properties of components intrinsically contain runtime type information.
Components can be added to the Component palette in the IDE and manipulated on a form.
Components often achieve a better degree of encapsulation than is usually found in standard classes. For example, consider the use of a dialog containing a push button. In a Windows program developed using VCL components, when a user clicks on the button, the system generates a WM_LBUTTONDOWN message. The program must catch this message (typically in a switch statement, a message map, or a response table) and dispatch it to a routine that will execute in response to the message.
2:
کد:Setting properties at design time
When you select a component on a form at design time, the Object Inspector displays its published properties and (when appropriate) allows you to edit them. Use the Tab key to toggle between the left-hand Property column and the right-hand Value column. When the cursor is in the Property column, you can navigate to any property by typing the first letters of its name. For properties of Boolean or enumerated types, you can choose values from a drop-down list or toggle their settings by double-clicking in Value column.
If a plus (+) symbol appears next to a property name, clicking the plus symbol or typing '+' when the property has focus displays a list of subvalues for the property. Similarly, if a minus (-) symbol appears next to the property name, clicking the minus symbol or typing '-' hides the subvalues.
By default, properties in the Legacy category are not shown; to change the display filters, right-click in the Object Inspector and choose View. For more information, see Property and event categories in the Object Inspector.
When more than one component is selected, the Object Inspector displays all properties--except Name--that are shared by the selected components. If the value for a shared property differs among the selected components, the Object Inspector displays either the default value or the value from the first component selected. When you change a shared property, the change applies to all selected components.
Changing code-related properties, such as the name of an event handler, in the Object Inspector automatically changes the corresponding source code. In addition, changes to the source code, such as renaming an event handler method in a form class declaration, is immediately reflected in the Object Inspector.
3:
کد:Using property editors
Some properties, such as Font, have special property editors. Such properties appear with ellipsis marks (...) next to their values when the property is selected in the Object Inspector. To open the property editor, double-click in the Value column, click the ellipsis mark, or type Ctrl+Enter when focus is on the property or its value. With some components, double-clicking the component on the form also opens a property editor.
Property editors let you set complex properties from a single dialog box. They provide input validation and often let you preview the results of an assignment.
Setting properties at runtime
Any writable property can be set at runtime in your source code. For example, you can dynamically assign a caption to a form:
Form1.Caption := MyString;
Calling methods
Methods are called just like ordinary procedures and functions. For example, visual controls have a Repaint method that refreshes the control's image on the screen. You could call the Repaint method in a draw-grid object like this:
DrawGrid1.Repaint;
As with properties, the scope of a method name determines the need for qualifiers. If you want, for example, to repaint a form within an event handler of one of the form's child controls, you don't have to prepend the name of the form to the method call:
4:
کد:Using the Sender parameter
In an event handler, the Sender parameter indicates which component received the event and therefore called the handler. Sometimes it is useful to have several components share an event handler that behaves differently depending on which component calls it. You can do this by using the Sender parameter in an if...then...else statement. For example, the following code displays the title of the application in the caption of a dialog box only if the OnClick event was received by Button1.
Displaying and coding shared events
When components share events, you can display their shared events in the Object Inspector. First, select the components by holding down the Shift key and clicking on them in the Form Designer; then choose the Events tab in the Object Inspector. From the Value column in the Object Inspector, you can now create a new event handler for, or assign an existing event handler to, any of the shared events
5:
کد:Designing applications
ou can design any kind of 32-bit application--from general-purpose utilities to sophisticated data access programs or distributed applications.
As you visually design the user interface for your application, the Form Designer generates the underlying Delphi code to support the application. As you select and modify the properties of components and forms, the results of those changes appear automatically in the source code, and vice versa. You can modify the source files directly with any text editor, including the built-in Code editor. The changes you make are immediately reflected in the visual environment.
You can create your own components using the Delphi language. Most of the components provided are written in Delphi. You can add components that you write to the Component palette and customize the palette for your use by including new tabs if needed.
You can also design applications that run on both Linux and Windows by using CLX components. CLX contains a set of classes that, if used instead of those in the VCL, allows your program to port between Windows and Linux. Refer to Developing cross-platform applications for details about cross-platform programming and the differences between the Windows and Linux environments. If you are using Kylix while developing cross-platform applications, Kylix also includes a Developer's Guide that is tailored for the Linux environment. You can refer to the manual both in the Kylix online Help or the printed manual provided with the Kylix product.
6:
کد:Designing database applications
Database applications let users interact with information that is stored in databases. Databases provide structure for the information, and allow it to be shared among different applications.
Delphi provides support for relational database applications. Relational databases organize information into tables, which contain rows (records) and columns (fields). These tables can be manipulated by simple operations known as the relational calculus.
When designing a database application, you must understand how the data is structured. Based on that structure, you can then design a user interface to display data to the user and allow the user to enter new information or modify existing data.
Using data controls
The Data Controls page of the Component palette provides a set of data-aware controls that represent data from fields in a database record, and, if the dataset allows it, enable users to edit that data and post changes back to the database. By placing data controls onto the forms in your database application, you can build your database application's user interface (UI) so that information is visible and accessible to users.
The data-aware controls you add to your user interface depend on several factors, including the following:
The type of data you are displaying. You can choose between controls that are designed to display and edit plain text, controls that work with formatted text, controls for graphics, multimedia elements, and so on. Controls that display different types of information are described in Displaying a single record.
How you want to organize the information. You may choose to display information from a single record on the screen, or list the information from multiple records using a grid. Choosing how to organize the data describes some of the possibilities.
The type of dataset that supplies data to the controls. You want to use controls that reflect the limitations of the underlying dataset. For example, you would not use a grid with a unidirectional dataset because unidirectional datasets can only supply a single record at a time.
How (or if) you want to let users navigate through the records of datasets and add or edit data. You may want to add your own controls or mechanisms to navigate and edit, or you may want to use a built-in control such as a data navigator.