Christian Ridderström wrote:
On Thu, 17 Jul 2008, Christian Ridderström wrote:
What's the status of the change tracking that's describe on the
following page?
http://www.lyx.org/devel/changetracking.php
Should I port it to the new web site? To the wiki? Or just redirect
the old page to
Christian Ridderström wrote:
Nice to read:
http://www.lyx.org/TranslationHints
/Christian
PS. I'm not sure if we still should link to this page, and from which
page we should link to it.
Ideal material for a wiki, no? It's a useful but personal account.
A.
Christian Ridderström wrote:
On Thu, 17 Jul 2008, Christian Ridderström wrote:
What's the status of the change tracking that's describe on the
following page?
http://www.lyx.org/devel/changetracking.php
Should I port it to the new web site? To the wiki? Or just redirect
the old page to
Christian Ridderström wrote:
Nice to read:
http://www.lyx.org/TranslationHints
/Christian
PS. I'm not sure if we still should link to this page, and from which
page we should link to it.
Ideal material for a wiki, no? It's a useful but personal account.
A.
[EMAIL PROTECTED] wrote:
A starting point of the announcment can be found here:
PS. Here's a copy of the text:
Here's a little re-working into English ;-)
Angus
The LyX community has for a long time felt that the old site needed a
major overhaul. The [[new LyX web site-http://www.lyx.org]]
[EMAIL PROTECTED] wrote:
A starting point of the announcment can be found here:
PS. Here's a copy of the text:
Here's a little re-working into English ;-)
Angus
The LyX community has for a long time felt that the old site needed a
major overhaul. The [[new LyX web site-http://www.lyx.org]]
[EMAIL PROTECTED] wrote:
Do we want to keep a copy of the old www.lyx.org? Or maybe just a
screenshot to remember how ugly it was? (I didn't think about this
before I modified 'index.php')
Would be nice, for nostalgia's sake.
One thing I keep remembering as I walk to work and then forget
... The [translation page] on the main LyX home page ...
points at
http://www.lyx.org/about/i18n.php
... If you've got (or would like) any experience with coding for
multi-lingual documents, contact the [Developers' mailing list].
points at
http://www.lyx.org/mailing.php
[EMAIL PROTECTED] wrote:
Do we want to keep a copy of the old www.lyx.org? Or maybe just a
screenshot to remember how ugly it was? (I didn't think about this
before I modified 'index.php')
Would be nice, for nostalgia's sake.
One thing I keep remembering as I walk to work and then forget
... The [translation page] on the main LyX home page ...
points at
http://www.lyx.org/about/i18n.php
... If you've got (or would like) any experience with coding for
multi-lingual documents, contact the [Developers' mailing list].
points at
http://www.lyx.org/mailing.php
[EMAIL PROTECTED] wrote:
Does anyone know a perl compatible regexp that matches 'href' but not
'\href'?
Match all occurences of 'href' that are preceded by zero or more
whitespace chars and followed by zero or more whitespace chars and an
'=' char
[\n\t ]*href[\n\t ]*=
Angus
[EMAIL PROTECTED] wrote:
Does anyone know a perl compatible regexp that matches 'href' but not
'\href'?
Match all occurences of 'href' that are preceded by zero or more
whitespace chars and followed by zero or more whitespace chars and an
'=' char
[\n\t ]*href[\n\t ]*=
Angus
The new site is looking fantastic! Way to go, guys! Way to go! (See,
I've become American :-P)
I see that Rex has created a new graphic for the home page, so
presumably you're still experimenting with such things. With that as my
preamble, I'd like to share some comments I have about the
The new site is looking fantastic! Way to go, guys! Way to go! (See,
I've become American :-P)
I see that Rex has created a new graphic for the home page, so
presumably you're still experimenting with such things. With that as my
preamble, I'd like to share some comments I have about the
I get asked for a password if I click on the Edit link at the bottom of
http://www.lyx.org/test/Download?skin=pmwiki
However, I can just walk into
http://www.lyx.org/test/wiki/index.php/Web/HomePage?action=edit
I suspect you don't want that :-P
Angus
I get asked for a password if I click on the Edit link at the bottom of
http://www.lyx.org/test/Download?skin=pmwiki
However, I can just walk into
http://www.lyx.org/test/wiki/index.php/Web/HomePage?action=edit
I suspect you don't want that :-P
Angus
Jean-Marc Lasgouttes wrote:
[EMAIL PROTECTED] writes:
On Mon, 7 Apr 2008, Angus Leeming wrote:
While I'm at it ;-)
Hi Angus,
Would it be to much to ask you to just fix it?
I am not sure his employer would allow him to %-]
:-P
I see many other pages are afflicted
Jean-Marc Lasgouttes wrote:
[EMAIL PROTECTED] writes:
On Mon, 7 Apr 2008, Angus Leeming wrote:
While I'm at it ;-)
Hi Angus,
Would it be to much to ask you to just fix it?
I am not sure his employer would allow him to %-]
:-P
I see many other pages are afflicted
We had one curmudgeonly gentleman, John Weiss, who point blank refused
to licence his contribution to LyX under the GPL version 2 or later. The
old flavour of this page has him down as licencing his contributions
under the artistic licence. The new page does not...
Angus Leeming wrote:
We had one curmudgeonly gentleman, John Weiss, who point blank refused
to licence his contribution to LyX under the GPL version 2 or later. The
old flavour of this page has him down as licencing his contributions
under the artistic licence. The new page does not...
http
We had one curmudgeonly gentleman, John Weiss, who point blank refused
to licence his contribution to LyX under the GPL version 2 or later. The
old flavour of this page has him down as licencing his contributions
under the artistic licence. The new page does not...
Angus Leeming wrote:
We had one curmudgeonly gentleman, John Weiss, who point blank refused
to licence his contribution to LyX under the GPL version 2 or later. The
old flavour of this page has him down as licencing his contributions
under the artistic licence. The new page does not...
http
Angus Leeming wrote:
Pavel Sanda wrote:
I think we're ready to go live.
just few bits i've found during scanning the whole structure:
- what is lyx, features, get involved pages, donate contain unreadbale
chars (copyright sign Lars name,...)
- whats is lyx - credits links at the end
Angus Leeming wrote:
Pavel Sanda wrote:
I think we're ready to go live.
just few bits i've found during scanning the whole structure:
- what is lyx, features, get involved pages, donate contain unreadbale
chars (copyright sign Lars name,...)
- whats is lyx - credits links at the end
[EMAIL PROTECTED] wrote:
I've talked to Andrei, Rex etc and from a design point of view, we're
ready to go live. So what else is missing before a release?
It's looking very nice, but I notice when playing with the different
skins at http://www.lyx.org/test/Download that h1LyX Downloads/h1
Pavel Sanda wrote:
I think we're ready to go live.
just few bits i've found during scanning the whole structure:
- what is lyx, features, get involved pages, donate contain unreadbale chars
(copyright sign Lars name,...)
- whats is lyx - credits links at the end will be b0rken once pages
[EMAIL PROTECTED] wrote:
I've talked to Andrei, Rex etc and from a design point of view, we're
ready to go live. So what else is missing before a release?
It's looking very nice, but I notice when playing with the different
skins at http://www.lyx.org/test/Download that LyX Downloads
isn't
Pavel Sanda wrote:
I think we're ready to go live.
just few bits i've found during scanning the whole structure:
- what is lyx, features, get involved pages, donate contain unreadbale chars
(copyright sign Lars name,...)
- whats is lyx - credits links at the end will be b0rken once pages
Pavel Sanda wrote:
wasn't WYSIWYM as well). The second time, I fixed the errant line
breaks in Notepad++. I'm willing to fix it again to look the way you
want if you let me know specifically what should change (indentation,
spacing, line breaks, ?).
just look into the patch you sent and
Pavel Sanda wrote:
wasn't WYSIWYM as well). The second time, I fixed the errant line
breaks in Notepad++. I'm willing to fix it again to look the way you
want if you let me know specifically what should change (indentation,
spacing, line breaks, ?).
just look into the patch you sent and
rgheck [EMAIL PROTECTED] writes:
In r23505, I removed the ability to index into the LayoutList held in a
TextClass, because it seemed too implementation dependent, and just
ugly. I replaced it with an iterator. Unfortunately, the iterator was
kind of ugly too, because it wasn't returning
rgheck <[EMAIL PROTECTED]> writes:
> In r23505, I removed the ability to index into the LayoutList held in a
> TextClass, because it seemed too implementation dependent, and just
> ugly. I replaced it with an iterator. Unfortunately, the iterator was
> kind of ugly too, because it wasn't
Dov Feldstern wrote:
So now the question is: do we need this function at all at this point?
Since it seems to have been doing nothing for the past three years, can
we just get rid of it? Does anyone know if what the code that's in there
*should* have been doing is still needed?
You should
Stefan Schimanski wrote:
Hi!
I would like to use the multi_index classes from the boost library.
Unfortunately this is not in the boost version we have in svn. Is it
just old or do we have only a selection of boost modules?
Only those libraries that are actually used by LyX. While you're
I notice that the LyX donations page,
http://www.lyx.org/donations.php, is unable to display the PayPal
image. As a result, the admonition to click the button below isn't
going to bring in much hard cash :-P
Ah, interesting. All looks fine with Firefox 2.0, but things are
broken with IE7.
Dov Feldstern wrote:
So now the question is: do we need this function at all at this point?
Since it seems to have been doing nothing for the past three years, can
we just get rid of it? Does anyone know if what the code that's in there
*should* have been doing is still needed?
You should
Stefan Schimanski wrote:
Hi!
I would like to use the multi_index classes from the boost library.
Unfortunately this is not in the boost version we have in svn. Is it
just old or do we have only a selection of boost modules?
Only those libraries that are actually used by LyX. While you're
I notice that the LyX donations page,
http://www.lyx.org/donations.php, is unable to display the PayPal
image. As a result, the admonition to "click the button below" isn't
going to bring in much hard cash :-P
Ah, interesting. All looks fine with Firefox 2.0, but things are
broken with IE7.
Pavel Sanda wrote:
Pavel Sanda wrote:
I purposely left RC_VISUAL_CURSOR out of this function, because something
is fishy about it. AFAICT, this function doesn't do anything... JMarc
took a look and I think he also wasn't sure about it... So before just
fixing the warnings, we ought to try and
Pavel Sanda wrote:
Pavel Sanda wrote:
I purposely left RC_VISUAL_CURSOR out of this function, because something
is fishy about it. AFAICT, this function doesn't do anything... JMarc
took a look and I think he also wasn't sure about it... So before just
fixing the warnings, we ought to try and
Jürgen Spitzmüller [EMAIL PROTECTED] writes:
Dov Feldstern wrote:
I just noticed that LyXRC::getDescription (in which I made some changes
for the visual cursor stuff) is #if-fed out because it's not used.
1. So is there any point in my making changes in it?
2. Should we just get rid
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
>
> Dov Feldstern wrote:
> > I just noticed that LyXRC::getDescription (in which I made some changes
> > for the visual cursor stuff) is #if-fed out because it's not used.
> >
> > 1. So is there any point in my making changes in it?
> > 2. Should we
[EMAIL PROTECTED] wrote:
Author: rgheck
Date: Sat Jan 5 17:49:49 2008
New Revision: 22385
URL: http://www.lyx.org/trac/changeset/22385
Log:
Implement isAvaiable in ModuleList.
Call be blind, but I cannot see where you set LyXModule::checked to
True...
Incidentally, it's usually
[EMAIL PROTECTED] wrote:
Author: bpeng
Date: Sat Jan 5 05:43:13 2008
New Revision: 22374
URL: http://www.lyx.org/trac/changeset/22374
Log:
Embedding: does not write inzipName option in InsetGraphics because inzipName
is now automatically determined
Isn't this a format change?
A.
[EMAIL PROTECTED] wrote:
Author: lasgouttes
Date: Fri Jan 4 18:04:07 2008
New Revision: 22368
URL: http://www.lyx.org/trac/changeset/22368
Log:
remove extra menu expansion which causes multiple warnings about shortcuts
-
- Menu menu;
-
[EMAIL PROTECTED] wrote:
Author: bpeng
Date: Sat Jan 5 05:39:01 2008
New Revision: 22373
URL: http://www.lyx.org/trac/changeset/22373
Log:
zipunzip.cpp: Replace makedir etc with versions in support::FileName, fix a bug
in extracting subdirectories
Modified:
[EMAIL PROTECTED] wrote:
> Author: rgheck
> Date: Sat Jan 5 17:49:49 2008
> New Revision: 22385
>
> URL: http://www.lyx.org/trac/changeset/22385
> Log:
> Implement isAvaiable in ModuleList.
Call be blind, but I cannot see where you set LyXModule::checked to
True...
Incidentally, it's usually
[EMAIL PROTECTED] wrote:
Author: bpeng
Date: Sat Jan 5 05:43:13 2008
New Revision: 22374
URL: http://www.lyx.org/trac/changeset/22374
Log:
Embedding: does not write inzipName option in InsetGraphics because inzipName
is now automatically determined
Isn't this a format change?
A.
[EMAIL PROTECTED] wrote:
Author: lasgouttes
Date: Fri Jan 4 18:04:07 2008
New Revision: 22368
URL: http://www.lyx.org/trac/changeset/22368
Log:
remove extra menu expansion which causes multiple warnings about shortcuts
-
- Menu menu;
-
[EMAIL PROTECTED] wrote:
Author: bpeng
Date: Sat Jan 5 05:39:01 2008
New Revision: 22373
URL: http://www.lyx.org/trac/changeset/22373
Log:
zipunzip.cpp: Replace makedir etc with versions in support::FileName, fix a bug
in extracting subdirectories
Modified:
Enrico Forestieri wrote:
configure_command_ = os::python() + ' ' +
quoteName(configure_script.toFilesystemEncoding()) +
with_version_suffix();
You are right. A parser would be needed, and it is going to become
cumbersome and error prone.
It just so happens that I wrote one
Enrico Forestieri wrote:
>> configure_command_ = os::python() + ' ' +
>> quoteName(configure_script.toFilesystemEncoding()) +
>> with_version_suffix();
>
> You are right. A parser would be needed, and it is going to become
> cumbersome and error prone.
It just so happens that I
Jean-Marc Lasgouttes wrote:
I know you would eventually praise the good old xforms way of doing
things :)
LOL. As the man what wrote that dialog, I seem to remember that we killed
it because it wasn't LyX's job to be a taskmgr-like GUI.
I believe John and Asger were particularly convincing in
Jean-Marc Lasgouttes wrote:
> I know you would eventually praise the good old xforms way of doing
> things :)
LOL. As the man what wrote that dialog, I seem to remember that we killed
it because it wasn't LyX's job to be a taskmgr-like GUI.
I believe John and Asger were particularly "convincing"
Andre Poenitz [EMAIL PROTECTED] writes:
[Btw, this is one of the cases were I do not see actual benefits over
global variables. If we had several instances or needed complicated
construction/destruction matters would be different...]
Several instances? Your confused me ol' china. Neither
Andre Poenitz [EMAIL PROTECTED] writes:
So maybe the macro is not the best idea after all.
Maybe I'll dig into the boost preprocessor library to write something like:
vectorstring opts = LYX_INITIALIZE_VECTOR(a, b, c);
Compile times would surely make you smile.
SCNR backly,
Angus
Andre Poenitz wrote:
Given that the plain C++ version
char const *d[] = { a, b, c };
vectorstring v(d, d + sizeof(d) / sizeof(d[0]));
is - taking the extra #include boost/whatever.hpp line into
account - not even longer to type than any boost based solution
I doubt the boost stuff would
Andre Poenitz <[EMAIL PROTECTED]> writes:
> [Btw, this is one of the cases were I do not see actual benefits over
> global variables. If we had several instances or needed complicated
> construction/destruction matters would be different...]
Several instances? Your confused me ol' china. Neither
Andre Poenitz <[EMAIL PROTECTED]> writes:
> So maybe the macro is not the best idea after all.
Maybe I'll dig into the boost preprocessor library to write something like:
vector opts = LYX_INITIALIZE_VECTOR("a", "b", "c");
Compile times would surely make you smile.
SCNR backly,
Angus
Andre Poenitz wrote:
> Given that the plain C++ version
>
> char const *d[] = { "a", "b", "c" };
> vector v(d, d + sizeof(d) / sizeof(d[0]));
>
> is - taking the extra #include line into
> account - not even longer to type than any boost based solution
> I doubt the boost stuff would survive
Uwe Stöhr [EMAIL PROTECTED] writes:
In general a document has usually not more than 10 options, so
10 times reforming a vector should be done in less than one millisecond.
I understand. But if nobody tells you of a better way then you'll never grow.
Anyway, thanks for persevering with me. It's
Enrico Forestieri [EMAIL PROTECTED] writes:
On Sun, Dec 09, 2007 at 06:59:36PM +0100, Uwe Stöhr wrote:
What's the problem?
This code part is from Jürgen as proposal, because Angus and Abdel
requested a solution without the
declaration of the extern global variable as I did in the
Uwe Stöhr [EMAIL PROTECTED] writes:
This compiles except that I don't know how to declare the vector correctly.
Currently all lists are given as:
char const * const known_fontsizes[] = { 10pt, 11pt, 12pt, 0};
G. I really dislike arrays that use a null pointer to indicate the end.
When I
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> In general a document has usually not more than 10 options, so
> 10 times reforming a vector should be done in less than one millisecond.
I understand. But if nobody tells you of "a better way" then you'll never grow.
Anyway, thanks for persevering with
Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> On Sun, Dec 09, 2007 at 06:59:36PM +0100, Uwe Stöhr wrote:
>
> > What's the problem?
> > This code part is from Jürgen as proposal, because Angus and Abdel
requested a solution without the
> > declaration of the extern global variable as I
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> This compiles except that I don't know how to declare the vector correctly.
> Currently all lists are given as:
> char const * const known_fontsizes[] = { "10pt", "11pt", "12pt", 0};
G. I really dislike arrays that use a null pointer to indicate the
Uwe Stöhr wrote:
I'm still a bloody C++ beginner and lost when looking into your code.
No need to be lost. Let's see if I can explain.
The best thing would be to provide a patch tho make the void
handle_opt work without the need to have a delete_void called
afterwards.
It's best to keep
[EMAIL PROTECTED] wrote:
// special columntypes
extern std::mapchar, int special_columns;
@@ -218,8 +220,17 @@
h_font_sans = name;
if (!opts.empty()) {
scale = opts;
- pos = scale.find(.);
-
Uwe Stöhr wrote:
take this attached correct patch.
regards Uwe
Shouldn't global variables be declared in tex2lyx.h and defined in
tex2lyx.cpp?
Angus
Uwe Stöhr wrote:
I'm still a bloody C++ beginner and lost when looking into your code.
No need to be lost. Let's see if I can explain.
The best thing would be to provide a patch tho make the void
"handle_opt" work without the need to have a "delete_void" called
afterwards.
It's best to
[EMAIL PROTECTED] wrote:
// special columntypes
extern std::map special_columns;
@@ -218,8 +220,17 @@
h_font_sans = name;
if (!opts.empty()) {
scale = opts;
- pos = scale.find(".");
-
Uwe Stöhr wrote:
take this attached correct patch.
regards Uwe
Shouldn't global variables be declared in tex2lyx.h and defined in
tex2lyx.cpp?
Angus
Uwe Stöhr [EMAIL PROTECTED] writes:
+void delete_opt(vectorstring opts, char const * const * what)
+{
+ if (opts.empty())
+ return;
+
+ // remove found options from the list
+ // do this after handle_opt to avoid potential memory leaks and to be
able
+ // to
Uwe Stöhr <[EMAIL PROTECTED]> writes:
+void delete_opt(vector & opts, char const * const * what)
+{
+ if (opts.empty())
+ return;
+
+ // remove found options from the list
+ // do this after handle_opt to avoid potential memory leaks and to be
able
+ // to
Juergen Spitzmueller [EMAIL PROTECTED] writes:
Uwe Stöhr wrote:
Yes, things that are already in the latest fileformat won't be touched in
lyx2lyx as far as I tested. So except of probably only a few cases where
lyx2lyx changes the file to a wrong format, we can support LyX's 1.6's
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
>
> Uwe Stöhr wrote:
>
> > Yes, things that are already in the latest fileformat won't be touched in
> > lyx2lyx as far as I tested. So except of probably only a few cases where
> > lyx2lyx changes the file to a wrong format, we can support LyX's
Martin Vermeer [EMAIL PROTECTED] writes:
-# Put here the conversions needed from LaTeX string
-# to LyXText:
+# Put here the conversions needed from LaTeX string to LyXText:
+# Umlauted characters:
+fullcontent = fullcontent.replace(r'\\\a',
Martin Vermeer <[EMAIL PROTECTED]> writes:
> -# Put here the conversions needed from LaTeX string
> -# to LyXText:
> +# Put here the conversions needed from LaTeX string to LyXText:
> +# Umlauted characters:
> +fullcontent = fullcontent.replace(r'\\\"a',
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
This is fixed by the patch below, where I have also replaced
the regex based code by something simpler. This is not (only) to make
Andre happy, but also to make it work on wide strings.
I thought Boost.Regex supported wide strings. I believe that
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> This is fixed by the patch below, where I have also replaced
> the regex based code by something simpler. This is not (only) to make
> Andre happy, but also to make it work on wide strings.
I thought Boost.Regex supported wide strings. I believe
Andre Poenitz [EMAIL PROTECTED] writes:
I think we should think about how a binary kernel interface would look
like. The serialization could exist on top of that as a thin wrapper.
LOL! I've obviously a long memory. I remember a certain André Pönitz telling
me that binary serialization based
Andre Poenitz <[EMAIL PROTECTED]> writes:
> I think we should think about how a binary kernel interface would look
> like. The serialization could exist on top of that as a thin wrapper.
LOL! I've obviously a long memory. I remember a certain André Pönitz telling
me that binary serialization
On a Linux box:
valgrind --leak-check=full src/lyx
Open up the Users' Guide using the menu HelpUsers' Guide
Wait some time...
Close LyX with FileExit
That produces the rather disturbing report. This is with a bang-up-to-date
check out.
--
Angus
valgrind_report.txt.gz
Description: GNU Zip
On a Linux box:
valgrind --leak-check=full src/lyx
Open up the Users' Guide using the menu "Help>Users' Guide"
Wait some time...
Close LyX with "File>Exit"
That produces the rather disturbing report. This is with a bang-up-to-date
check out.
--
Angus
valgrind_report.txt.gz
Description: GNU Zip
Richard Heck [EMAIL PROTECTED] writes:
This is very boring:
CommandInfo const * InsetCommandParams::findInfo(
InsetCode code, std::string const cmdName)
{
switch (code) {
case BIBITEM_CODE:
return InsetBibitem::findInfo(cmdName);
case BIBTEX_CODE:
Richard Heck <[EMAIL PROTECTED]> writes:
>
>
> This is very boring:
>
> CommandInfo const * InsetCommandParams::findInfo(
> InsetCode code, std::string const & cmdName)
> {
> switch (code) {
> case BIBITEM_CODE:
> return InsetBibitem::findInfo(cmdName);
> case
Richard Heck wrote:
The attached patch finishes this bit of work, left over from the
InsetCommand conversion. Comments welcome before I commit.
Richard
This sort of change gives me a nice, warm, fuzzy feeling. It's obvious
you've done something right when you can remove so much code :-)
Richard Heck wrote:
>
> The attached patch finishes this bit of work, left over from the
> InsetCommand conversion. Comments welcome before I commit.
>
> Richard
This sort of change gives me a nice, warm, fuzzy feeling. It's obvious
you've done something right when you can remove so much code
Abdelrazak Younes wrote:
PS: Sorry Angus but you deserved it ;-)
PPS: I'm talking about Rugby...
Me too. So did you.
Abdelrazak Younes wrote:
> PS: Sorry Angus but you deserved it ;-)
> PPS: I'm talking about Rugby...
Me too. So did you.
Abdelrazak Younes wrote:
Well it was just modeled after Inset::clone but you're right, it's
strange. Maybe I should just rename it to cloneInset() instead or
implement a copy ctor...
The copy constructor sounds sane. This thing isn't polymorphic at all.
--
Angus
Abdelrazak Younes wrote:
Well it was just modeled after Inset::clone but you're right, it's
> strange. Maybe I should just rename it to cloneInset() instead or
> implement a copy ctor...
The copy constructor sounds sane. This thing isn't polymorphic at all.
--
Angus
Richard Heck wrote:
The obvious way to handle this is to have something like this:
enum Optional { OPT, REQ };
struct ParamInfo {
std::string paramName;
Optional opt;
docstring value;
}
class ParamList {
setValue(std::string name, docstring
[EMAIL PROTECTED] wrote:
Author: younes
Date: Thu Oct 18 17:29:51 2007
New Revision: 21033
URL: http://www.lyx.org/trac/changeset/21033
Log:
Reduce header dependencies in Paragraph.h
- Move Changes.h out of Paragraph.h
- pimpl the inset list.
[EMAIL PROTECTED] wrote:
Author: poenitz
Date: Fri Oct 19 01:03:51 2007
New Revision: 21048
URL: http://www.lyx.org/trac/changeset/21048
Log:
isome more FileName shuffling
http://www.lyx.org/trac/file/lyx-devel/trunk/src/support/FileName.cpp?rev=21048
Richard Heck wrote:
> The obvious way to handle this is to have something like this:
> enum Optional { OPT, REQ };
> struct ParamInfo {
>std::string paramName;
>Optional opt;
>docstring value;
> }
> class ParamList {
>setValue(std::string name,
[EMAIL PROTECTED] wrote:
> Author: younes
> Date: Thu Oct 18 17:29:51 2007
> New Revision: 21033
>
> URL: http://www.lyx.org/trac/changeset/21033
> Log:
> Reduce header dependencies in Paragraph.h
> - Move Changes.h out of Paragraph.h
> - pimpl the inset list.
[EMAIL PROTECTED] wrote:
> Author: poenitz
> Date: Fri Oct 19 01:03:51 2007
> New Revision: 21048
>
> URL: http://www.lyx.org/trac/changeset/21048
> Log:
> isome more FileName shuffling
http://www.lyx.org/trac/file/lyx-devel/trunk/src/support/FileName.cpp?rev=21048
>
Andre Poenitz [EMAIL PROTECTED] writes:
[Apart from that I do neither trust boost::fs nor our own use of file
names when it comes to unusual enviroments. Chinese Windows comes
to mind for instance. One of the less funny features that show up
there is that the argv/argc that's passed to main()
Andre Poenitz <[EMAIL PROTECTED]> writes:
> [Apart from that I do neither trust boost::fs nor our own use of file
> names when it comes to "unusual" enviroments. Chinese Windows comes
> to mind for instance. One of the less funny features that show up
> there is that the argv/argc that's passed to
1 - 100 of 20061 matches
Mail list logo