On 07/01/2021 9:49 am, Santiago A. via lazarus wrote:
> https://github.com/commonmark/commonmark-spec/wiki/Markdown-Flavors
Wow, I knew about a few variations, but I didn't know there
was that many. It's worse than I thought.
Regards,
Graeme
--
__
On Thu, 7 Jan 2021, Santiago A. via lazarus wrote:
El 05/01/2021 a las 10:47, Michael Van Canneyt via lazarus escribió:
Because people are naturally lazy and prefer easy & simple over strict
& rich.
But we could chose a language that is easy & simple for when you want to
do simple thin
El 05/01/2021 a las 10:47, Michael Van Canneyt via lazarus escribió:
Because people are naturally lazy and prefer easy & simple over strict
& rich.
But we could chose a language that is easy & simple for when you want to
do simple things (90% time) and rich when you need to do complex thin
On 06/01/2021 5:48 pm, Graeme Geldenhuys via lazarus wrote:
> Hi Sergey,
>
> [I've replied off the mailing list]
Apologies, my stupid email client replaced the TO name, but still went
and sent it to the mailing list. :-(
Regards,
Graeme
--
___
la
Hi Sergey,
[I've replied off the mailing list]
On 06/01/2021 2:16 am, Sergey Bodrov via lazarus wrote:
> Wikipedia and hundreds of wiki sites (includes freepascal wiki). De-facto
> standard for updateable documentation.
Markdown doesn't have any official (single) standard. Many versions exist
al
On Wed, 6 Jan 2021, Graeme Geldenhuys via lazarus wrote:
On 02/01/2021 2:31 pm, Michael Van Canneyt via lazarus wrote:
material theme:
https://www.freepascal.org/~michael/docs-demo/material/system/tobject.dispatch/
There seems to be an issue generating constants and values with a underscore
On Wed, 6 Jan 2021, Graeme Geldenhuys via lazarus wrote:
On 02/01/2021 2:31 pm, Michael Van Canneyt via lazarus wrote:
Compare the official page for TObject.Dispatch:
Looking at another class with more detail... Did you explicitly enable
the functionality to generate Private, Protected fiel
>
> There are many articles on the Internet going in much more detail
> describing the issues of Markdown. Yet like Windows, it seem still so
> popular. I have no idea why.
>
Wikipedia and hundreds of wiki sites (includes freepascal wiki). De-facto
standard for updateable documentation.
Main adva
On 02/01/2021 2:31 pm, Michael Van Canneyt via lazarus wrote:
> Compare the official page for TObject.Dispatch:
Looking at another class with more detail... Did you explicitly enable
the functionality to generate Private, Protected fields and methods?
Or does the Markdown writer possibly not check
On 02/01/2021 2:31 pm, Michael Van Canneyt via lazarus wrote:
> material theme:
> https://www.freepascal.org/~michael/docs-demo/material/system/tobject.dispatch/
There seems to be an issue generating constants and values with a underscore
in the name.
You can see that here:
https://www.freepa
On 05/01/2021 9:47 am, Michael Van Canneyt via lazarus wrote:
> Because people are naturally lazy and prefer easy & simple over strict & rich.
Once again the simplest answer is always the one closest to the truth. :)
> Basically the same reasons why my cat prefers the awful can food I give her
On Tue, 5 Jan 2021, Graeme Geldenhuys via lazarus wrote:
On 03/01/2021 7:48 pm, Don Siders via lazarus wrote:
I've been looking at allowing markdown for the description files (they would
be less verbose then), but there seems to be no decent markdown parser available
for pascal. If somone car
On 03/01/2021 7:48 pm, Don Siders via lazarus wrote:
>> I've been looking at allowing markdown for the description files (they would
>> be less verbose then), but there seems to be no decent markdown parser
>> available
>> for pascal. If somone cares to contribute one...
> Oh boy. I guess it is in
On Sun, 3 Jan 2021, Don Siders via lazarus wrote:
> I would rather see sectioning added to the FPDoc tags/content model:
>
>
>
>Using the Control
>Lorem ipsum sic dolor amet.
>
>
And what would this do in terms ouf output ?
In general, it would make FPDoc more usable for non-r
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
On Sun, 3 Jan 2021, Don Siders via lazarus wrote:
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 anoth
>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
On Sun, 3 Jan 2021, Соболь Андрей Евгеньевич via lazarus wrote:
I've been looking at allowing markdown for the description files (they would
be less verbose then), but there seems to be no decent markdown parser available
for pascal. If somone cares to contribute one...
For "overview pages"
> I've been looking at allowing markdown for the description files (they would
> be less verbose then), but there seems to be no decent markdown parser
> available
> for pascal. If somone cares to contribute one...
For "overview pages" (unit, class, package) I think need to move a "description
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 tack
20 matches
Mail list logo
