On Mon, Dec 28, 2020 at 04:20:16PM +0200, Yuriy Skalko wrote:
> From 4f38e801eb930ca70b6a086f0aa553e1d19b21a3 Mon Sep 17 00:00:00 2001
> From: Yuriy Skalko
> Date: Tue, 22 Dec 2020 12:14:00 +0200
> Subject: [PATCH 6/7] Update Doxygen options to have more dependency graphs
>
> N
From 4f38e801eb930ca70b6a086f0aa553e1d19b21a3 Mon Sep 17 00:00:00 2001
From: Yuriy Skalko
Date: Tue, 22 Dec 2020 12:14:00 +0200
Subject: [PATCH 6/7] Update Doxygen options to have more dependency graphs
Now many graphs are not generated due to excessive dependencies
(default node limit for one
Apologies for only sending to Jean-Marc initially. I end up doing this
mistake a lot with gmail these days.
/C
-- Forwarded message --
From: Christian Ridderström
Date: 8 April 2017 at 16:06
Subject: Re: Doxygen sourcedoc: Should there be a non-empty "main" page?
To:
Le 07/04/2017 à 07:20, Christian Ridderström a écrit :
Doxygen can take the content of e.g. a README or some other document and
use that as the main page.
The main page can be an introduction to developers, or simply a bunch of
links to other developer documents.
If anyone want's examples,
On 6 April 2017 at 13:47, Jean-Marc Lasgouttes wrote:
> Le 04/04/2017 à 22:08, Christian Ridderström a écrit :
>
>> Hi,
>>
>> Should the Doxygen docs have a "main page"? At
>> https://www.lyx.org/sourcedoc/latest/index.html
>> the main page is
Le 04/04/2017 à 22:08, Christian Ridderström a écrit :
Hi,
Should the Doxygen docs have a "main page"? At
https://www.lyx.org/sourcedoc/latest/index.html
the main page is currently empty.
I don't know if this is an error on my side, or if we simply haven't
created a m
On 28 February 2017 at 03:24, Pavel Sanda wrote:
> Christian Ridderström wrote:
> > Currently we're also keeping all the previously generated "sourcedocs".
> > There I'm guessing we at most would like to keep a few, or perhaps none.
>
> I don't see the need for the older ones.
I'm changing the
Hi,
Should the Doxygen docs have a "main page"? At
https://www.lyx.org/sourcedoc/latest/index.html
the main page is currently empty.
I don't know if this is an error on my side, or if we simply haven't
created a main page.
/Christian
Christian Ridderström wrote:
> Currently we're also keeping all the previously generated "sourcedocs".
> There I'm guessing we at most would like to keep a few, or perhaps none.
I don't see the need for the older ones.
> PPS:
> As the bash script etc is deployed on the server, please let me know
Le 26/02/2017 à 22:46, Christian Ridderström a écrit :
Hi,
I just want to let people know that (hopefully) we now have a working
pipeline where:
- A CI job [1] on Mondays, builds and uses Doxygen to generate "sourcedoc"
- The LyX server, on Tuesdays, then pulls in and deploys the
Hi,
I just want to let people know that (hopefully) we now have a working
pipeline where:
- A CI job [1] on Mondays, builds and uses Doxygen to generate "sourcedoc"
- The LyX server, on Tuesdays, then pulls in and deploys the "sourcedoc" as
https://www.lyx.org/sourcedo
ast Monday.
(I just changed to Mondays, was once a day before)
- The CI job triggers if the repo has changed and builds the docs,
resulting in:
https://ci.inria.fr/lyx/job/build-master-head/job/make-lyx-doxygen-docs/ws/sourcedoc/html.tar.gz
- A cron job on the LyX server executes a script on
Christian Ridderström wrote:
> On 14 February 2017 at 01:17, Pavel Sanda wrote:
>
> > Christian Ridderström wrote:
> > > But some HTML-stuff doesn't look right when served from the CI server, so
> > > I've placed a copy for review on the lyx server here:
> > >http://www.lyx.org/test/sourcedoc
rg.
(I presume the CI server blocks some links to external javascripts or
something).
/C
The docs on the CI server are here:
https://ci.inria.fr/lyx/job/build-master-head/job/make-lyx-doxygen-docs/ws/sourcedoc/html/index.html
Christian Ridderström wrote:
> But some HTML-stuff doesn't look right when served from the CI server, so
> I've placed a copy for review on the lyx server here:
>http://www.lyx.org/test/sourcedoc/index.html
I randomly looked at
http://www.lyx.org/test/sourcedoc/classlyx_1_1frontend_1_1GuiBibt
Not sure this made it to the list earlier, so resending.
On 2 February 2017 at 17:37, Christian Ridderström wrote:
> Hi,
>>>
>>> I thought I'd setup a CI job that generates doxygen, i.e. do:
>>> make doxygen
>>>
>>> Can someone con
The subject says it all.
JMarc
Jean-Marc Lasgouttes wrote:
> Le 14/02/2014 07:22, Pavel Sanda a écrit :
>> Jürgen Spitzmüller wrote:
>>> http://www.lyx.org/Development points to an outdated doxygen site
>>> generated
>>> from LyX 2.0 SVN. If this cannot be updated from GIT, shouldn'
Le 14/02/2014 07:22, Pavel Sanda a écrit :
Jürgen Spitzmüller wrote:
http://www.lyx.org/Development points to an outdated doxygen site generated
from LyX 2.0 SVN. If this cannot be updated from GIT, shouldn't we rather
remove this link?
I would prefer to update it (IIRC JMarc has acces
Jürgen Spitzmüller wrote:
> http://www.lyx.org/Development points to an outdated doxygen site generated
> from LyX 2.0 SVN. If this cannot be updated from GIT, shouldn't we rather
> remove this link?
I would prefer to update it (IIRC JMarc has access and was doing it last time,
right?)
Pavel
http://www.lyx.org/Development points to an outdated doxygen site generated
from LyX 2.0 SVN. If this cannot be updated from GIT, shouldn't we rather
remove this link?
Jürgen
On 22/07/2013 4:10 AM, Guenter Milde wrote:
On 2013-07-22, Josh Hieronymus wrote:
Second, is there a tutorial
serves as a gentle introduction to Python scripting for LyX? I've not
worked with Python and C++ in the same project before, so I'm not really
sure how to get them to work togethe
On 2013-07-22, Josh Hieronymus wrote:
...
> Second, is there a tutorial
> serves as a gentle introduction to Python scripting for LyX? I've not
> worked with Python and C++ in the same project before, so I'm not really
> sure how to get them to work together, especially when you consider issues
>
Pavel Sanda wrote:
> we already have working library for zipping files as a part of LyX and commit
> history might even contain much more generic solution written some time back
> by
> Bo Peng as a part of bundled lyx format feature (and reverted later;).
You can check commits around
a095d0d785ca
Josh Hieronymus wrote:
> I was thinking of using the existing C++ routines to generate the XHTML,
> and then using Python to generate the additional necessary files, which are
> mostly XML files with metadata and manifest info, as well as to pack the
> files.
My point was just that you shouldn't u
to generate the XHTML,
and then using Python to generate the additional necessary files, which are
mostly XML files with metadata and manifest info, as well as to pack the
files.
Thanks for the doxygen help, by the way. That's really helping me to
understand the code even more.
Josh Hieronymus wrote:
> Since an ePub file is pretty much a zipped file with XHTML and a few simple
> files, I was thinking that it might be easiest to use Python to create
> them.
If it comes to packing you might be interested to see our lyxpak.py script.
I'm not sure what you mean by 'create';
On Sun, Jul 21, 2013 at 8:58 PM, Pavel Sanda wrote:
> Josh Hieronymus wrote:
> > I have two questions for everyone. First, is there a simple command to
> use
> > Doxygen to produce HTML documenting all of (or most of, or at least much
> > of) LyX? I think it would reall
Josh Hieronymus wrote:
> I have two questions for everyone. First, is there a simple command to use
> Doxygen to produce HTML documenting all of (or most of, or at least much
> of) LyX? I think it would really help me have an easier time knowing how
make doxydoc, if you have graphviz,
Hi everyone,
I have two questions for everyone. First, is there a simple command to use
Doxygen to produce HTML documenting all of (or most of, or at least much
of) LyX? I think it would really help me have an easier time knowing how
the different parts of code are all related. Second, is there a
From: Pavel Sanda [sa...@lyx.org]
Sent: Sunday, July 15, 2012 6:34 PM
>Doxygen generation is not related to LFUNs.lyx.
> - doxygen: make doxydoc
> - LFUNs.lyx: make lfundoc
Thanks,
Scott
Scott Kostyshak wrote:
> How do I turn LyXAction.cpp into LFUNs.lyx?
Doxygen generation is not related to LFUNs.lyx.
- doxygen: make doxydoc
- LFUNs.lyx: make lfundoc
Pavel
Le 15/07/12 21:07, Scott Kostyshak a écrit :
How do I turn LyXAction.cpp into LFUNs.lyx?
I think you need development/tools/gen_lfuns.py.
JMarc
How do I turn LyXAction.cpp into LFUNs.lyx?
Thanks,
Scott
the first object in a
+// bibliography paragraph.
+class InsetBibitem : public InsetCommand
+{
Andre',
You are broking the doxygen tags. The style is more or less uniform in the
code:
/// Short Description.
/**
Long description...
*/
The three slashes in the first line are impor
the first object in a
+// bibliography paragraph.
+class InsetBibitem : public InsetCommand
+{
Andre',
You are broking the doxygen tags. The style is more or less uniform in the
code:
/// Short Description.
/**
Long description...
*/
Ah... I thought /// and /**...* were equival
sert bibitem's information (key and label)
>> +
>> +// Must be automatically inserted as the first object in a
>> +// bibliography paragraph.
>> +class InsetBibitem : public InsetCommand
>> +{
>
> Andre',
>
> You are broking the doxygen tags. The style
sert bibitem's information (key and label)
>> +
>> +// Must be automatically inserted as the first object in a
>> +// bibliography paragraph.
>> +class InsetBibitem : public InsetCommand
>> +{
>
> Andre',
>
> You are broking the doxygen tags. The style
setCommand
+{
Andre',
You are broking the doxygen tags. The style is more or less uniform in
the code:
/// Short Description.
/**
Long description...
*/
The three slashes in the first line are important, so is the trailing
dot at the end of the line.
The _two_ stars in the second line ar
vidual insets;
> BufferView-level LFUNs are implemented in BufferView::Dispatch;
> Document-level LFUNs in text.C. Grep for individual LFUNs in the
> sources; you'll soon get the idea.
I imagine it is possible to use doxygen to get a list of where a specific
variable is used
Am Mittwoch, 19. Mai 2004 17:31 schrieb Angus Leeming:
> I just tried to run doxygen, but stopped when is complained:
> To avoid this warning please update your configuration file using "doxygen
-u"
>
> Doing so, (Doxyfile is a generated file, so I'd guess that the
I just tried to run doxygen, but stopped when is complained:
doxygen ./Doxyfile
Warning: Tag `CGI_NAME' at line 894 of file ./Doxyfile has become obsolete.
To avoid this warning please update your configuration file using "doxygen -u"
Warning: Tag `CGI_URL' at line 900 of
ighlighted(QString const &);
| -void refSelected(QString const &);
| +void refHighlighted(const QString &);
| +void refSelected(const QString &);
qt mumbo-jumbo. moc does not grok "Type const &" correctly at all
times, I am just making .h and .C a
Looks good. A few questions:
This looks like a typo:
> QAboutDialog::~QAboutDialog()
> -{
> -}
> +{}
> +y
>
?:
Index: src/frontends/qt2/QRefDialog.h
-void refHighlighted(QString const &);
-void refSelected(QString const &);
+void refHighlighted(const QString &);
+
This patch fixes a lot of doxygen warnings.
? newfile1.lyx
? src/frontends/xforms/lyx_forms.h
? src/frontends/xforms/lyx_xpm.h
Index: sourcedoc/Doxyfile.in
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/sourcedoc/Doxyfile.in,v
John Levon wrote:
>> What am I doing wrong? The generated html is worse than confusing.
> You open a group twice ...
You mean I can't nest them? Oh well.
--
Angus
On Thu, Mar 13, 2003 at 09:25:40PM +, Angus Leeming wrote:
> What am I doing wrong? The generated html is worse than confusing.
>
//@{
/** These methods are publicly accessible because they are
* invoked
* by the parent container.
*/
//@{
/
What am I doing wrong? The generated html is worse than confusing.
--
Angus// -*- C++ -*-
/**
* \file Dialog.h
* This file is part of LyX, the document processor.
* Licence details can be found in the file COPYING.
*
* \author Angus Leeming
*
* Full author contact details are available in
John Levon wrote:
> Why do you need to do anything special ?
> http://www.stack.nl/~dimitri/doxygen/autolink.html
Next question: is there a way to generate the html of a single file so that
I can check that I'm on the right track?
--
Angus
John Levon wrote:
> On Thu, Mar 13, 2003 at 08:04:51PM +, Angus Leeming wrote:
>
>> What's the doxygen way of saying Dialog::hide? Ie, is there
>> an @method identifier or something?
>>
>> /** Invoked by Dialog::hide, allowing the Controller to
On Thu, Mar 13, 2003 at 08:04:51PM +, Angus Leeming wrote:
> What's the doxygen way of saying Dialog::hide? Ie, is there
> an @method identifier or something?
>
> /** Invoked by Dialog::hide, allowing the Controller to
>* clean up its data structures.
W
What's the doxygen way of saying Dialog::hide? Ie, is there
an @method identifier or something?
/** Invoked by Dialog::hide, allowing the Controller to
* clean up its data structures.
*/
virtual void clearParams() = 0;
Angus (attempting to make this
Angus Leeming <[EMAIL PROTECTED]> writes:
| Simple fix attached. Ok to apply?
yes.
--
Lgb
On Wed, Sep 25, 2002 at 04:51:28PM +0100, Angus Leeming wrote:
> struct Timeout::Pimpl : QObject {
> private:
> /// xforms id
> int timeout_id;
> };
Right, should be QTimer id
thanks
john
--
"The only perfect circle on the human body is the eye. When a baby is
born its so perfect
On Wednesday 25 September 2002 5:18 pm, John Levon wrote:
> On Wed, Sep 25, 2002 at 04:41:15PM +0100, Angus Leeming wrote:
> > Simple fix attached. Ok to apply?
>
> --- src/frontends/qt2/Dialogs2.C24 Sep 2002 13:57:07
> - 1.5
> +++ src/frontends/qt2/Dialogs2.C25 Sep 2002 16:09:
On Wed, Sep 25, 2002 at 04:41:15PM +0100, Angus Leeming wrote:
> Simple fix attached. Ok to apply?
--- src/frontends/qt2/Dialogs2.C24 Sep 2002 13:57:07 -
1.5
+++ src/frontends/qt2/Dialogs2.C25 Sep 2002 16:09:11 -
@@ -1,5 +1,5 @@
/**
- * \file xforms/Dialogs.C
+ * \file x
Simple fix attached. Ok to apply?
Angus
doxygen.diff.gz
Description: GNU Zip compressed data
On Mon, Feb 25, 2002 at 12:49:50AM +0100, Lars Gullik Bjønnes wrote:
> Nope, it is space waiting for your comments.
and for things needing no comments ?
I really don't see the point in :
/// constructor
SomeClass();
regards
john
p.s. and yes I have a few sourcedoc improvement
Why do we have code like :
///
void someFunction();
given that EXTRACT_ALL is set ?
Isn't this a waste of vertical space ?
regards
john
--
"Yes, I understand your point, but This Is UA, and not some fluffy creche."
- Topper
...and why its periodically regenerated document tree isn't
accessible at the cvsweb server!
I just did this for my own convenience, setting up the
apache on my job computer to access the doxygen tree
from home -- just one symlink (might be a security risk
though). A midnightly cro
On Thu, Dec 14, 2000 at 01:01:59AM +0100, Lars Gullik Bjønnes wrote:
>
> By Executive Order we are from now on using doxygen for our source
> documentation.
Great. There's just one problem: no organization. What classes are
core? Which class(es) is(are) a good starting poi
John Levon <[EMAIL PROTECTED]> writes:
| On 14 Dec 2000, Lars Gullik Bjønnes wrote:
|
| >
| > By Executive Order we are from now on using doxygen for our source
| > documentation.
| >
| > Doc++ just had too many problems.
|
| wow, I didn't know we *weren't*
On 14 Dec 2000, Lars Gullik Bjønnes wrote:
>
> By Executive Order we are from now on using doxygen for our source
> documentation.
>
> Doc++ just had too many problems.
wow, I didn't know we *weren't* using doxygen ;)
> http://www.lyx.org/~larsbj/html/in
Allan Rae <[EMAIL PROTECTED]> writes:
| On 14 Dec 2000, Lars Gullik Bjønnes wrote:
|
| >
| > By Executive Order we are from now on using doxygen for our source
| > documentation.
|
| Who keeps saying I don't want to be "The Boss" ;-)
:-) and I really don't.
On 14 Dec 2000, Lars Gullik Bjønnes wrote:
>
> By Executive Order we are from now on using doxygen for our source
> documentation.
Who keeps saying I don't want to be "The Boss" ;-)
> However doxygen supports the same sysntax as Doc++ so we don't have to
> c
By Executive Order we are from now on using doxygen for our source
documentation.
Doc++ just had too many problems.
However doxygen supports the same sysntax as Doc++ so we don't have to
change anything.
Point your browser to
http://www.lyx.org/~larsbj/html/index.html
for an ex
66 matches
Mail list logo
