On Fri, Mar 24, 2023 at 7:00 AM wrote:
> Am 23.03.2023 um 01:07 schrieb Don Siders via lazarus:
> > My question: Is there a maintainer for IPro that I can offer the
> > patches to? Or, should I post them here or to the issue tracker?
> It's probably me who did most
I have made some changes to a couple of the units in IPro: iphtml.pas
and iphtmlnodes.pas. They were needed to fix layout and rendering
issues in TIpHtmlPanel - primarily to benefit the LHelp help viewer.
For example: line spacing in PRE, DL, UL, and OL. Missing support for
top and bottom margins w
On Sun, Apr 10, 2022 at 6:00 AM wrote:
> I'm getting heaps of this kind of warnings:
>
> Cinnamon warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a
> timestamp of 0 for 0x238 (Lazarus)
>
> Any idea what causes this ?
There is an open bug report for it at
https://github.com/linux
>> I wanted to add the following entries to the .gitignore file for the
>> Lazarus repo:
>>
>> /docs/html/*.log
>> /docs/html/*.inc
> Can there be any subdirectories in /docs/html?
Yes, when you install HTML help locally.
/docs/html/lcl/
/docs/html/lazutils/
But they are not needed in the repos
I wanted to add the following entries to the .gitignore file for the
Lazarus repo:
/docs/html/*.log
/docs/html/*.inc
/docs/html/*.xml
They're generated artifacts from building help.
Can I add these? Or, should someone else do that?
--
Don
--
___
laza
On Sun, Jan 3, 2021 at 6:06 PM Michael Van Canneyt
wrote:
> >> I've been looking at allowing markdown for the description files (they
> >> would
> >> be less verbose then), ...
> > Oh boy. I guess it is inevitable, but I don't think it's a
> > particularly good idea.
> Personally, I don't plan
>Hello !
>
>I didn't make it quite in time for the new year, but still:
>
>The fpdoc engine (what is used to document the FPC & Lazarus units)
>is now capable of outputting the documentation in markdown.
>
>This can be used as input for mkdocs or another engine such as sphinx.
>As a first engine, I
>> Is there someone here who has used the Chrome API with
>> Lazarus for anything video related and is willing to share?
> I never managed to get the Chrome API to work on linux,
> but an effort is currently underway to make the chromium
> browser available in Lazarus on all supported platforms.
Okay, Back to the original topic.
The duplicates in graphics.xml are almost certainly because they are
overloaded methods. Whether that is correct in the context of the tool
used to update the file, I do not know,
I am submitting a patch for other files with duplicate topics.This
does not include
>> I edit manually too. It's neither difficult nor error prone. I get
>> exactly the FP Doc markup that I feel is appropriate.
> Now we have a problem. FPDocEditor and LazDocEditor ARE distributed with
> Lazarus, and nobody is prevented from using them. So, when I modify one
> of your recent xml f
> makeskel does support update, the Makefile of fpc docs has even a target for
> it ?
> It only does additions, though.
> I suppose that deletions should also be easily added.
>
> Michael.
My initial efforts to use it were in the Lazarus 1.8.x time frame. and
it would not run without exception the
On Wed, Dec 18, 2019 at 10:24 AM wrote:
> From: Werner Pamler
> Subject: Re: [Lazarus] Duplicate items in xml doc files
> Message-ID:
> But now I am quite confused because it does not necessarily
> consider all nodes in a file. As we see here, there are two
> TCanvas.PolyBezier nodes in the sa
Never mind. After looking more closely at build_lcl_docs, I see it does
both .
On Fri, Apr 5, 2019 at 1:00 AM Don Siders wrote:
> I've been updating help topics lately. It would be nice if I could build
> the help/html files locally to see how they are affected by changes. I've
> stumbled across
I've been updating help topics lately. It would be nice if I could build
the help/html files locally to see how they are affected by changes. I've
stumbled across build_lcl_docs already. But I haven't unearthed anything
for lazutils yet.
Is there a FPDoc project file or a script + program as used
14 matches
Mail list logo
