On Fri, 8 Apr 2022, Mattias Gaertner via lazarus wrote:
On Fri, 8 Apr 2022 14:21:23 +0200
Sven Barth via lazarus wrote:
[...]
Solving this would at the same time allow the IDE to have a TButton
for both the LCL and e.g. Web Components Library. Right now they need
to be named differently
On Wed, 6 Apr 2022 12:56:17 +0200 (CEST)
Michael Van Canneyt via lazarus wrote:
> Hello,
>
> I'm probably kicking in an open door when I'm saying that lazarus
> evolves and grows. This is good news, obviously.
>
> But I have now more tabs on the component palette than can fit on the
> screen.
On 6-4-2022 23:45, Michael Van Canneyt wrote:
* When writing: write UnitName.ComponentName instead of ComponentName.
A trivial change, which can be done in a backward compatible manner.
It only will break compatibility with Delphi needlessly. This will
complicate making e.g. demoes for
On Fri, 8 Apr 2022, Marco van de Voort wrote:
Units are already packages (or namespaces) by themselves. That is why they
were invented. No need to add a second layer.
The duplications are within sets of units with similar names for different
component packages. It is only logical to
On Fri, 8 Apr 2022, Mattias Gaertner via lazarus wrote:
On Wed, 6 Apr 2022 12:56:17 +0200 (CEST)
Michael Van Canneyt via lazarus wrote:
Hello,
I'm probably kicking in an open door when I'm saying that lazarus
evolves and grows. This is good news, obviously.
But I have now more tabs on
On 8-4-2022 11:26, Michael Van Canneyt wrote:
The duplications are within sets of units with similar names for
different component packages. It is only logical to also use that.
There is no need to force the unit as disambiguator.
I want to be able to use the unit as disambiguator.
That
On 8-4-2022 10:49, Michael Van Canneyt via lazarus wrote:
But that is exactly what I want to support ?
If I want to implement my own button, descendent of the standard
TButton or not:
Except for the restriction during streaming, I see no reason why I would
have to name my own button
On Fri, 8 Apr 2022 10:49:05 +0200 (CEST)
Michael Van Canneyt via lazarus wrote:
>[...]
> > Only if you want to support reading different TButton in one
> > application.
>
> But that is exactly what I want to support ?
I understand a lcl controls.TButton and a web controls.TButton, but
that
Marco van de Voort via lazarus schrieb am
Fr., 8. Apr. 2022, 11:58:
>
> IOW in which cases is disambiguation in the class registration of the
> generated app needed?
>
>
> Sure, the IDE is also a FPC/Lazarus app, but it has more leeway for
> solutions that doesn't require changes to the way
On Fri, 8 Apr 2022, Marco van de Voort via lazarus wrote:
On 8-4-2022 11:26, Michael Van Canneyt wrote:
The duplications are within sets of units with similar names for different
component packages. It is only logical to also use that. There is no need
to force the unit as
On Fri, 8 Apr 2022, Marco van de Voort via lazarus wrote:
On 8-4-2022 10:49, Michael Van Canneyt via lazarus wrote:
But that is exactly what I want to support ?
If I want to implement my own button, descendent of the standard TButton or
not:
Except for the restriction during
On Fri, 8 Apr 2022, Sven Barth via lazarus wrote:
Marco van de Voort via lazarus schrieb am
Fr., 8. Apr. 2022, 11:58:
IOW in which cases is disambiguation in the class registration of the
generated app needed?
Sure, the IDE is also a FPC/Lazarus app, but it has more leeway for
On Fri, 8 Apr 2022 14:21:23 +0200
Sven Barth via lazarus wrote:
>[...]
> Solving this would at the same time allow the IDE to have a TButton
> for both the LCL and e.g. Web Components Library. Right now they need
> to be named differently like WebCtrls.TWButton.
Note that if you just want to
On 8-4-2022 14:21, Sven Barth wrote:
Marco van de Voort via lazarus schrieb
am Fr., 8. Apr. 2022, 11:58:
IOW in which cases is disambiguation in the class registration of the
generated app needed?
Sure, the IDE is also a FPC/Lazarus app, but it has more leeway for
14 matches
Mail list logo
