In this section announcements will be made and a variety of topics can be discussed.
This forum contains communication on Charta features.
This forum contains communication on ChartaPascal features.
Code evolves and sometimes needs to be refactored. When such a refactoring would take a lot of time to do at once it is often better to amortize the effort by including it in the execution of the daily tasks. This section will list ongoing refactor topics.
We use MySQL intensively in our products. Here we can provide information that is specific to MySQL.
The option tcoSummable is used in SQL table columns to indicate that values in those columns can be summed and presented as a total to the user. The question is whether a table column should hold this property. Probably a type should hold this property instead.
Function TSQLExpression.Copy now has been implemented. The addition of this function has some implications that I will describe here.
A new API function 'Generate bindings' has been introduced to generate missing class and function bindings in Charta.
The default values (0) have been removed from GetFloatingPoint and GetInteger field functions of TSQLResult.
The standard Math unit of Delphi has been deprecated in favor of the Mathematics unit.
From now on the nightly build shows deprecations in a separate column to distinguish them from other problems.
It is assumed that reference counting fails to reclaim some objects in Charta. We need some reproducible test cases that show this problem.
Currently the Charta Platform supports PostgreSQL. The most important client library functions are available now and parts of the generic platform SQL structure can be compiled to SQL text.
Currently the Charta Platform support a great SQL abstraction layer that enables SQL independence. However, our database script system still uses hard coded SQL queries. Maybe it is time to use the SQL abstraction layer for database scripts as well.
Charta Web now supports the TPHPWebSiteModule module which allows an entire PHP site to be executed within Charta Web.
The Charta Platform uses many SQL tables. Most tables define primary key and unique key constraints. In SQL these constraints should have an identifier that is unique within the entire database. We should define a naming convention for these constraints to prevent identifier collisions.
The current code base makes heavy use of the SQL abstraction layer. This makes it possible to unleash the full power of SQL in our programming code. However, currently we have a lot of code that overuses SQL and does not properly separate concerns.
The class TOldScrollPanel had been deprecated for already a while. Now it has been removed from the code base.
A module is not responsible for rendering its title anymore. Either the website template takes care of it, or, in case of a compound website module, the parent module renders the titles of its children.
In many software applications, images are not scaled correctly. This page illustrates that problem in Charta Web. Other applications which fail to scale the source image correctly include Photoshop, the GIMP, and the various browsers.
Tips and discussions about useful tools
Discussion about the nomenclature of database scripts (subclasses of TSQLDatabaseScript").