XE. Delphi XE Handbook Delphi XE Handbook Cover download book on You can also download the ebook (PDF) of the "Delphi Handbooks Collection". ation about this PDF on the specific section my web site: kaz-news.infoantu. com/handbooks. Source Code. Given that Delphi XE directly supports. Mastering Delphi series, Delphi. Developer's Handbook, and of the free online book Essential. Pascal. He teaches classes on. Delphi foundations and advanced.

Delphi Xe Handbook Pdf

Language:English, Dutch, Arabic
Published (Last):17.02.2016
ePub File Size:30.52 MB
PDF File Size:11.71 MB
Distribution:Free* [*Registration Required]
Uploaded by: LEONA

Download delphi xe handbook pdf cantu - devilsfunhouse org nitro pdf pro 6 0 3 1 rar - Being reactive and allowing the downloader to initially approach often puts the. Delphi XE Handbook. Pages · · Delphi XE IntraWeb XI Development Red Teaming Handbook v7 Points of Contact Critical Thinking Traits. "Delphi Handbook" PDF eBook by Marco Cantu Available only to registered users of All-Access XE Platinum. All-Access XE Silver.

The ebook in PDF is available at You can also download a Site License at The printed version is prices at The book should show up at other book outlets which might have lower shipping costs for your location. I'll update this paragragh as I figure out feel free to tell me if you've found the book elsewhere. The book covers all the new features of Delphi XE for Win32, safe from the improvements in DataSnap for time constraints.

This is a brand new book, there is no overlapping material with past Delphi Handbooks I wrote. The book is a detailed documentation of all the new extensions in Delphi XE compared to Delphi , with the significant exclusion of the DataSnap portion of the product. I decided it wasn't worth including those extra 60 pages in the book, since you can already read them online at no additional cost. As above, the book covers only new features in Delphi XE. Or get my "Delphi Handbooks Collection".

The Configuration Manager Also the Configuration Manager now View Configuration Manager, while in the past it was under the Project menu has been improved somewhat, particularly by cleaning up a rather messy user interface. Beside listing the current build configuration for each project in a group, and letting you change all or many of them at once, the Configuration Manager is particularly helpful if you Marco Cant, Delphi XE Handbook Chapter 1: Delphi XE IDE - 17 need to manage options sets which are a set of project options saved to an external file and possibly referenced by multiple projects, covered in my Delphi Handbook.

The Configuration Manager now shows the referenced options sets in the list of projects, rather than in a separate pane; it has a new combo box for activating a different configuration, and has a nicer toolbar. Build Tools Customization The last of the elements related with the management of projects and build configurations is the new dialog box to define Build Tools.

These are command line applications that you can use to process a file stored in a project, and are generally matched by extension.

The Build Tools you define in the corresponding dialog box have very vague relationships with the Build Events. You can add to the Project Options to have extra operations done before or after the project build process. I know some developers didn't like the change, but I don't want to enter a debate here. Rather, I want to cover the further changes made in Delphi XE to improve searches.

Search For Usages For several versions, the Delphi IDE has had a Find references command, based on the in-memory parsed version of the source code not the plain source code text. In Delphi XE this feature is still available, but you can improve these searches using the new Search for Usages command of the local menu of the editor. This will open up a dialog box, in which you can fine-tune and narrow your search. The enabled options of this dialog box depend on the kind of symbol you are looking for.

For example, if you search for a type, the dialog lets you include in the search members, derived types, plus variables of the given type. If you search for a method, the dialog lets you include overridden ones. In the dialog box you can filter what to search for and pick full inheritance support by selecting some of the options displayed in the next page: Marco Cant, Delphi XE Handbook Chapter 1: Delphi XE IDE - 19 In the past, this feature was available only to projects for which you had activated Modeling.

Now the Search for Usages command is directly available in the Class Explorer pane and in the local menu of the editor. These new keyboard commands are consistent with the search keystrokes found in moderns browsers like Firefox and Chrome, among other applications. As I mentioned above, the local search was significantly modified in Delphi turning the Find dialog box into a pane at the bottom of the editor. Since the initial group of templates, they have been expanded over time with new entries, some of which have been suggested by the community.

Like many other developers I do have my own extra set of Live Templates and encourage you to build your own3. In Delphi XE the number of new templates is quite large, with many of them focused on helping you write XMLDoc-based comments, as discussed in the next section. Among these Live Templates there are summary, para, remarks, param, and returns.

Among the existing ones, the for template has been slightly modified to automatically refer to Low and High rather than 0 and List. As an aside, Code Completion now shows the template description as a further hint.

The professional Free Pascal RAD IDE

Finally, the help mentions the todo Live Template as a new feature, but that was already in Delphi By default the folder is hpp under the shared public documents folder section for RAD Studio 8. These are the comments generated by some of the new Live Templates mentioned in the previous section, like summary. However, what is more important regarding XMLDoc is the ability to get the same information immediately in the editor, without even compiling or enabling the compiler option, as it automatically shows up in the Help Insight pane for the given symbol: It is possible to customize the output of this popup by modifying the associated CSS and also the XSL file used to produce the HTML output of the Help Insight from the XML data.

In a long file, however, locating these modified lines is far from simple, unless you move to the History tab to view Differences.

That's why Delphi XE introduces special keystrokes for navigating around modified lines. First, you could format the selected lines of a unit or a full unit, but not all of the units of a project at once. Second, if you customized the format settings there was no obvious way to copy the settings to another computer or share them with the other members of your team, to keep the source code format consistent. Delphi XE addresses both issues, adding some further formatting options. The first and more obvious change is that you can now use the Project Format Project Sources menu item or the corresponding entry of the Project Manager local menu on a project node.

As the name implies, this applies the current source format settings to all of the units of the current project, after showing a pretty dull confirmation dialog. Format project sources finished If you format an individual unit, instead, the dialog below will let you disable further confirmations see below and won't output its status to the Messages pane.

Its main goal, though, is to let you manage the active settings of the formatter, picking one of the predefined options, updating it, and saving the current settings to a custom file.

The top of the page is shown next: Interestingly enough, a formatter profile is a rather plain XML file you might even edit or process directly. Other Changes in Formatting There are a couple of other interesting changes to formatting.

The first is the ability to control alignments with the new set of Align options, which include the alignment of initializations, comments, and the like. Another very nice feature, if you happen to have many Delphi projects, is the ability to run the code formatter from the command line, as a stand-alone tool, without having to open a project in the IDE.

Just run Formatter. This is particularly suited if you use an external building tool like FinalBuilder4 , which can reformat the source code of a project before committing changes to a version control system5. I guess you can easily find other situations in which this can prove useful.

Form Designer There is no significant overhaul in the form designer and other Delphi visual designers, but a change certainly worth noticing, is the ability to copy the graphical representation of a form more about this in a second.

Beware of automatically formatting code for projects under version control. A change in the format is considered a change, and may cause useless conflicts with real changes written by other developers.

delphi xe handbook pdf cantu

On the other hand, applying a consistent and shared format setting before committing changes can help avoid the very same problem of future changes done for the sole purpose of using a consistent formatting style. So you can paste the clipboard content both to a textual editor and a graphical program, or use the Paste Special feature of a word processor to get either one of the other. Needless to say this is a real bonus for a book author, but anyone providing code documentation can certainly benefit from the feature.

As an example, I've create a new form, added a few components, copied the form, pasted the text below as usual Updated Wizards An area of the IDE that has received a significant cleanup is that of the Wizards that you can use to get started with development of new applications or to add specific features to existing projects. The most significant changes are in the new Wizards for DataSnap multi-tier applications.

A wizard that's not part of the New Items dialog box is the Install Component Wizard, described below. This is partially a change in the dialog box see below but also a change in the underlying library: Delphi now discourages the use of the Web App Debugger option, and encourages using the standalone Indy HTTP Server integration for Web Broker7.

This integration and some other new related components are covered in Chapter 4. Delphi XE sees the final touches with cleaner support for named threads, plus a set of other minor new features. In the Thread Status pane there is now a local menu to temporarily name a thread at run time. In general, though, it is more powerful to name a thread in code8, making the thread name persistent between debugging sessions.

Run Without Debugging The Run Without Debugging feature has now been promoted to a top feature, with its own graphic and button on the toolbar. Notice it is quite easy to mix up the Run and Run Without Debugging icons below on the right , as the latter is very similar to how the former looked in past versions of Delphi on the left : On a related topic, you can now specify more precisely what happens when you use the Load Process dialog to start a process.

Marco's Web Center

Rather than simply asking the debugger to execute the startup code or not, you can pick multiple options like do not run, run to the first source, or run9. In short, you can associate a debug-time name to a thread by calling the NameThreadForDebugging class method of the TThread class. There was more information in an old Embarcadero blog post by Chris Hesik, dated May 24th , but this is no longer available.

You might also like: ASM HANDBOOK VOL 20 PDF

Beside closing editor files opened while debugging, you can use the Debugger Options page of the Options dialog box of the IDE to automatically close other debug windows. In the same page of the Options dialog box, you can disable the prompt to rebuild modified projects while debugging Source has been modified.

It can be quite annoying at times. From Subversion support right inside the Project Manager, to extended Modeling features, from Final Builder to AQTime, from CodeSite to the Beyond Compare engine, there are many new features that help you in the development process, although they are not all meant for writing code.

A few years back we would have called them ALM tools, but given this word has peaked it's marketing hype and that Delphi developers got quite upset of old Borland trying to push ALM their way, willing or not, I'll try to refrain from using it! This chapter hasn't got a specific focus and it really doesnt get in depth on third party tools, that are very well documented on their respective web sites. It will introduce Subversion, help you figure out which tools are now available in Delphi, what is their role, and why you might want to use them.

Since there are some free tools as part of Delphi XE, it wouldn't be wise to ignore them. This takes place through a new module called Version Insight, which adds an entry to the File menu and plugs right into the Project Manager and its local menu.

Before we delve into the version control integration that ships with Delphi XE and we look into one of its extensions, let me start with a short and fast-paced introduction to version control systems in general and Subversion in particular. The key idea is to let multiple developers share some source code files and any changes that any of the developers make on the source code files. Although this could be done by accessing a physically shared repository, the general approach is for each developer to be able to create a personal copy of the various files and work on them.

How this is accomplished without interfering with other developers, depends on the overall approach of the VCS. Some VCS use a pessimistic approach based on locking. A developer needing to edit a file asks for exclusive ownership of the file, makes some changes to his local copy, send the new file back to the repository, and relinquishes control over the file. The advantage of this approach is that conflicting changes are impossible and developers must synchronize their work. Some big disadvantages include the need of interacting with the VCS frequently to avoid keeping a file locked for more time that's needed , the need to specifically ask for write permission as you start editing a file and in Delphi maybe also the need to close a read-only file, only to reopen it in the editor with write permissions after 10 This doesn't mean that a single developer won't benefit from a version control system.

Quite the contrary, having a VCS helps a single developer build a fully versioned backup of your code, and also work from multiple computers or virtual machines on the same source. There are many pessimistic version control systems, as this was originally the most popular approach, and people with a lot of experience in them don't see how any other approach could work.

These VCS might actually work fine for small in-house teams, but tend to fail when the team size and the distance among team members grow. That's why other VCS use an optimistic approach based on the idea that every developer has a full copy of the code and full rights to edit any file.

Only, team members might frequently post their changes and retrieve changes made by other developers.

If two different developers edit a file, as long as the changes affect different lines in the source code, merging can take place automatically.

In the rare event of changes to the same line of code, you'll need to manually merge the changes. Optimistic version control systems can work well from single developers acting more like a versioned backup to large teams and have been used by many large open source projects.

Unless the team is completely disorganized, different developers tend to focus on different areas of the projects and its source code files, minimizing the chances of a real conflict.

Delphi XE Handbook

Some of the advantages of these VCSs is that developer can indeed work remotely, and there might be many people with read-only rights, something common for large projects in which only a select few have the right to make changes to the system.

Truly, most VCS can be configured for both concurrency models, although they'll fall more naturally in one or the other camp. In recent years, there has been a very strong adoption for yet another model, called distributed. In a distributed VCS, instead, there is no central server. Some of them have peer repositories keeping in synch to each other, while in other configurations there is a hierarchical structure with a super master and a tree of distributed children.

In general, all nodes have equal power, so you can synchronize with any of the peer nodes or in case of a hierarchy with one of the children, creating a grand children node. In both scenarios, you can have a few Marco Cant, Delphi XE Handbook 36 - Chapter 2: Integrated Tooling nodes working on a temporary separate version from the other peers or the super master node.

Distributed version control systems, in fact, perform synchronization by exchanging patches change-sets among nodes. This means that at any time there are multiple working copies of the software, but no official code base.

Proponents cite as advantages the speed of peer-to-peer updates, compared to centralized ones, and the fact that everyone that is part of the project can propose changes and based on the relevance of its node, these changes will be accepted by other or further revised. Among distributed VCSs, the rage at the moment seems to be on git and Mercurial. The latter seems most popular for Windows projects, whilst git is used more in the Linux world.

delphi xe handbook pdf cantu

I personally have limited experience with distributed VCSs, but I see a lot of reasons to adopt them. As I'll explain at the end of the session, there is an extension to the current Delphi version control IDE integration that opens up the support for distributed VCSs.

Now that I have covered the core features of a VCS, let's focus primarily on one of them, as it is the only one officially supported in Delphi XE, Subversion. Subversion was originally developed by CollabNet www.The release of Delphi is here and it is called Delphi XE. Just run Formatter. Delphi and its installation program are both Windows applications, so you must. Also the author name is either the local computer user in this case, Marco or the Subversion user in this case, marcocantu.

It can be quite annoying at times. First, you can now open a project directly from a Subversion repository, with the menu command File Open From Version Control.

I'll update this paragragh as I figure out feel free to tell me if you've found the book elsewhere.