musing on new AI windows

[the-Arioch]

1. When the chat window was opened - it was rendered below the left-aligned Windows TaskBar

typo: was "text-aligned"

The positioning is probably made inside the parent TCnAICoderChatForm = class(TCnIdeDockForm)

i would avoid dumb Left := 0 positioning. I would do like this (perhaps as part of TCnIdeDockForm )

• during .DoShow or maybe even at the end of .CreateWindowHandle
• if there is no .ini settings (or before we would read .INI, as default positioning)
• take Parent Form or, if none, take main Delphi Form
• take ParentForm.Monitor.WorkareaRect
• move the form to fit into the rect

The procedure TCustomForm.MakeFullyVisible(AMonitor: TMonitor); does not cut it, at least not in VCL 2007, because fails to account to WorkareaRect using formal BoundsRect instead

was thinking maybe i should bin-patch it but then found it has one single use, in IOTA in TCollectionEditor.FormShow, that is really funny. Maybe more consumers appeared after Delphi 2007

---

2. should this wizard be even enabled (except for Options) if there is no API Key for the selected engine (actually, not any API keys at all) ?

3. looking at your sources... Perhaps there could be a nice feature for AI to translate comments and/or string literals; either into English or into current Windows user language

4. BTW, why not Kimi ? it seems to be all the buzz after DeepSeek and it seemed (when it is not offline) to be smarter than DS

[cnpack]

I'll check your suggestions one by one.

But Kimi is Moonshot in our AI Coder Providers.

[the-Arioch]

well, maybe then both Kimi and MoonShot terms to be advertised in GUI. Kimi is much more recognized brand.

One more thing, i disabled AI coder module but the source editor context menu has the AI Coder menuitem still. It is empty, sure, but it is visible, borrowing from both screen space and attention span

[cnpack]

well, maybe then both Kimi and MoonShot terms to be advertised in GUI. Kimi is much more recognized brand.

One more thing, i disabled AI coder module but the source editor context menu has the AI Coder menuitem still. It is empty, sure, but it is visible, borrowing from both screen space and attention span

Ok, we'll change Moonshot/月之暗面 to Kimi due to this name is more popular now.
Menuitems will update with wizard setting active changed, too.

[cnpack]

2. should this wizard be even enabled (except for Options) if there is no API Key for the selected engine (actually, not any API keys at all) ?

Ollama AI Engine Do not need APIKey, so we keep this exception.

1. When the chat window was opened - it was rendered below the left-aligned Windows TaskBar

We add a limitation for TMonitor.Workarea accroding to your suggestion, it will be in next nightly-build version 1313.

[the-Arioch]

0bcc97057f4f2018188df8b6e4924beeead2e002

in general, i would rather declare one more local var and read it from AForm.BoundsRect, just a little habit that provides for

• some cache locality and read-repeatability
• avoiding multiple expensive getter calls in hot paths (not this case, so that is why i say a habit)
• avoiding multiple expensive setter calls in hot paths (every AForm.X := in the end is GetBoundRect + SetBoundsRect, but then this is not a hot path)
• decoupling (generic fit-rect-into-rect function with CanShrink flag, then specific facades for a form or a control, etc; and this is where hot paths can appear suddenly with naive control layout managers, don't ask how i know)

[cnpack]

OK, optimized partly.