This happens in the tex2lyx make on multiple architectures:
g++ -O2 -fno-exceptions -W -Wall -Wl,-R/u/ksylvan/lib -o tex2lyx FloatList.o
Floating.o counters.o lyxlayout.o lyxtextclass.o lyxlex.o lyxlex_pimpl.o boost.o
context.o gettext.o lyxfont.o texparser.o tex2lyx.o preamble.o math.o table.o
On Tue, Oct 14, 2003 at 06:39:10PM +0200, Alfredo Braunstein wrote:
Andre Poenitz wrote:
Hm... not sure this is worthwhile.
neother do I.
Maybe we could jsut leave it as it is and keep the solution (init to
0) in bugzilla and use that when 1.4.0 is about to be released?
Sure. The
On Tue, Oct 14, 2003 at 11:34:13PM -0700, Kayvan A. Sylvan wrote:
This happens in the tex2lyx make on multiple architectures:
g++ -O2 -fno-exceptions -W -Wall -Wl,-R/u/ksylvan/lib -o tex2lyx FloatList.o
Floating.o counters.o lyxlayout.o lyxtextclass.o lyxlex.o lyxlex_pimpl.o boost.o
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars Andre Poenitz [EMAIL PROTECTED] writes:
real 0m51.848s user 0m0.200s sys 0m0.020s
On my AMD 2400+, but that is over a 384kb/s line.
Lars | Strange numbers... The first one looks ok, but 52s is too much
Lars even on | 384kb/s. This
On Tue, Oct 14, 2003 at 04:24:59PM +0200, Lars Gullik Bjønnes wrote:
| which involves a full rebreak and seems acceptable _for me_ even for
| buffer switching. But that's an AMD 1700+.
I'll do a proper test when I get home.
Any results?
Andre'
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Kayvan A. Sylvan wrote:
Thanks. ./autogen.sh and ./configure and make fixed it.
Angus If you ./configure --enable-maintainer-mode then all will
Angus happen auto-magically when you type make...
Note that we could have
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus This moves the lastfiles global variable into LyX and makes
Angus emergencyCleanup a non-static member function.
+ * BufferView_pimpl.C (loadLyXFile):
+ * MenuBackend.C (expandLastfiles):
+ * bufferlist.C (MenuWrite,
Andre Poenitz wrote:
On Tue, Oct 14, 2003 at 11:34:13PM -0700, Kayvan A. Sylvan wrote:
This happens in the tex2lyx make on multiple architectures:
g++ -O2 -fno-exceptions -W -Wall -Wl,-R/u/ksylvan/lib -o tex2lyx
FloatList.o Floating.o counters.o lyxlayout.o lyxtextclass.o
lyxlex.o
On Wed, Oct 15, 2003 at 10:15:20AM +0100, Angus Leeming wrote:
So, I think that the problem is that the symbolic link still exists
in your build tree.
rm build/src/tex2lyx/boost.C
should solve the problem.
Works. Thanks.
Andre'
--
Those who desire to give up Freedom in order to
Jean-Marc Lasgouttes wrote:
Angus This moves the lastfiles global variable into LyX and makes
Angus emergencyCleanup a non-static member function.
+ * BufferView_pimpl.C (loadLyXFile):
+ * MenuBackend.C (expandLastfiles):
+ * bufferlist.C (MenuWrite, QuitLyX):
+ lastfiles
On Wed, Oct 15, 2003 at 10:25:02AM +0100, Angus Leeming wrote:
Maybe is it just that I do not really understand what a singleton
class is...
Here is a stripped down version of the class.
I still don't understand why you don't use a namespace.
class LyX {
public:
static void
On Wednesday 15 October 2003 09:39, Jean-Marc Lasgouttes wrote:
Note that we could have --enable-maintainer-mode default to true for
development versions.
That would be good, is there any drawback for this approach?
JMarc
--
José Abílio
LyX and docbook, a perfect match. :-)
Angus Leeming [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
| So I have a copy of pybliographer (say) that hasn't kept up with
| the changing LyX syntax and the first time I use it I crash LyX?
| You're absolutely barking mad if you think that will improve the
| public perception of
Andre Poenitz wrote:
I still don't understand why you don't use a namespace.
in the .h:
namespace lyxglobal {
void exec(int argc, char * argv[]);
LyX ref();
LyX const cref();
}
Maybe nest the namespace
namespace lyx {
namespace global {
void exec(int
Andre Poenitz [EMAIL PROTECTED] writes:
| On Tue, Oct 14, 2003 at 04:24:59PM +0200, Lars Gullik Bjønnes wrote:
| which involves a full rebreak and seems acceptable _for me_ even for
| buffer switching. But that's an AMD 1700+.
I'll do a proper test when I get home.
| Any results?
I fell
Hi Angus,
I discovered that I need this for the gtk port to compile. I think that you
forgot some bits. :-)
Is the following patch ok?
--
José Abílio
LyX and docbook, a perfect match. :-)
Index: po/POTFILES.in
===
Jose' Matos wrote:
Hi Angus,
I discovered that I need this for the gtk port to compile. I think
that you forgot some bits. :-)
Is the following patch ok?
Looks sensible...
--
Angus
On Wed, Oct 15, 2003 at 10:47:50AM +0100, Angus Leeming wrote:
Andre Poenitz wrote:
I still don't understand why you don't use a namespace.
in the .h:
namespace lyxglobal {
void exec(int argc, char * argv[]);
LyX ref();
LyX const cref();
}
Maybe
On Wed, Oct 15, 2003 at 11:47:05AM +0200, Lars Gullik Bjønnes wrote:
Andre Poenitz [EMAIL PROTECTED] writes:
| On Tue, Oct 14, 2003 at 04:24:59PM +0200, Lars Gullik Bjønnes wrote:
| which involves a full rebreak and seems acceptable _for me_ even for
| buffer switching. But that's an AMD
Jose' == Jose' Matos [EMAIL PROTECTED] writes:
Jose' On Wednesday 15 October 2003 09:39, Jean-Marc Lasgouttes wrote:
Note that we could have --enable-maintainer-mode default to true
for development versions.
Jose' That would be good, is there any drawback for this approach?
I do not think
Andre Poenitz wrote:
Or lyx::global::updateInset(this) ;-)
[Which suspiciously feels like using 'current_view' *cough*]
But isn't...
Hmmm, so you're suggesting a bunch of free functions which provide a
world-visble interface to class LyX's member variables, this class
itself being hidden
Andre Poenitz [EMAIL PROTECTED] writes:
| On Wed, Oct 15, 2003 at 11:47:05AM +0200, Lars Gullik Bjønnes wrote:
Andre Poenitz [EMAIL PROTECTED] writes:
| On Tue, Oct 14, 2003 at 04:24:59PM +0200, Lars Gullik Bjønnes wrote:
| which involves a full rebreak and seems acceptable _for me_ even
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Andre Poenitz wrote:
Or lyx::global::updateInset(this) ;-) [Which suspiciously feels
like using 'current_view' *cough*]
Angus But isn't...
Angus Hmmm, so you're suggesting a bunch of free functions which
Angus provide a world-visble
On Wed, Oct 15, 2003 at 11:29:56AM +0100, Angus Leeming wrote:
Andre Poenitz wrote:
Or lyx::global::updateInset(this) ;-)
[Which suspiciously feels like using 'current_view' *cough*]
But isn't...
I know.
Hmmm, so you're suggesting a bunch of free functions which provide a
world-visble
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
Jose' == Jose' Matos [EMAIL PROTECTED] writes:
| Jose' On Wednesday 15 October 2003 09:39, Jean-Marc Lasgouttes wrote:
Note that we could have --enable-maintainer-mode default to true
for development versions.
| Jose' That would be good, is
Andre Poenitz [EMAIL PROTECTED] writes:
| On Wed, Oct 15, 2003 at 11:29:56AM +0100, Angus Leeming wrote:
Andre Poenitz wrote:
Or lyx::global::updateInset(this) ;-)
[Which suspiciously feels like using 'current_view' *cough*]
But isn't...
| I know.
Hmmm, so you're suggesting a bunch of
Andre Poenitz [EMAIL PROTECTED] writes:
| On Wed, Oct 15, 2003 at 11:29:56AM +0100, Angus Leeming wrote:
Andre Poenitz wrote:
Or lyx::global::updateInset(this) ;-)
[Which suspiciously feels like using 'current_view' *cough*]
But isn't...
| I know.
Hmmm, so you're suggesting a bunch of
On Wed, Oct 15, 2003 at 12:36:52PM +0200, Jean-Marc Lasgouttes wrote:
But class LyX's member variables are just a bunch of global variables
hidden in a `singleton class' just for the sake of using a buzzword,
aren't they?
Sort of. The problem is there are languages (like Java) where using such
Jean-Marc Lasgouttes wrote:
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Andre Poenitz wrote:
Or lyx::global::updateInset(this) ;-) [Which suspiciously feels
like using 'current_view' *cough*]
Angus But isn't...
Angus Hmmm, so you're suggesting a bunch of free functions which
On Wed, Oct 15, 2003 at 12:08:53PM +0100, Angus Leeming wrote:
Jean-Marc Lasgouttes wrote:
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Andre Poenitz wrote:
Or lyx::global::updateInset(this) ;-) [Which suspiciously feels
like using 'current_view' *cough*]
Angus But
Andre Poenitz [EMAIL PROTECTED] writes:
| Statics in a single file will be destructed in last-to-first order.
One problem is still that several of the global varialbes cannot be
static, they need more information before they can be initialized.
That is easily solved with a class.
Also pre-main
Lars Gullik Bjønnes wrote:
I can see it is possible. Why is it 'preferable'?
| Free functions provide (often...) better encapsulation (Scott
| Meyers?).
Btu not if they operatoe on global variables... then you do not gain
anything.
Where do you stand on the particular design under
Lars Gullik Bjønnes wrote:
Andre Poenitz [EMAIL PROTECTED] writes:
| Statics in a single file will be destructed in last-to-first
| order.
One problem is still that several of the global varialbes cannot be
static, they need more information before they can be initialized.
That is
Angus Leeming [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
I can see it is possible. Why is it 'preferable'?
| Free functions provide (often...) better encapsulation (Scott
| Meyers?).
Btu not if they operatoe on global variables... then you do not gain
anything.
| Where do you
On Wed, Oct 15, 2003 at 01:52:31PM +0200, Lars Gullik Bjønnes wrote:
Free functions should ideally not access class variables,
This assumes that the class is not a random collection of individual
thing - which it is in our case - but something real.
the functions should be free only when they
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus However, I don't think that any of this is really anything more
Angus than aesthetics. I _may_ go down this route, but I'm much more
Angus interested in [...]
Of course :)
JMarc
Andre Poenitz [EMAIL PROTECTED] writes:
| On Wed, Oct 15, 2003 at 01:52:31PM +0200, Lars Gullik Bjønnes wrote:
Free functions should ideally not access class variables,
| This assumes that the class is not a random collection of individual
| thing - which it is in our case - but something real.
On Wed, Oct 15, 2003 at 03:03:06PM +0200, Lars Gullik Bjønnes wrote:
Andre Poenitz [EMAIL PROTECTED] writes:
| On Wed, Oct 15, 2003 at 01:52:31PM +0200, Lars Gullik Bjønnes wrote:
Free functions should ideally not access class variables,
| This assumes that the class is not a random
Andre Poenitz [EMAIL PROTECTED] writes:
| On Wed, Oct 15, 2003 at 03:03:06PM +0200, Lars Gullik Bjønnes wrote:
Andre Poenitz [EMAIL PROTECTED] writes:
| On Wed, Oct 15, 2003 at 01:52:31PM +0200, Lars Gullik Bjønnes wrote:
Free functions should ideally not access class variables,
| This
Hi.
I got a problem with 1.4.0.
Open the test file attached to this mail (table created by 1.3).
Click in a cell of the table, then click the edit entry of the toolbar
- Boom.
Same under qt and xforms. I tried to first save the file (to update
tabular format), then reopen it - same story.
RH
I think undo is almost back to normal. The present crashes seem all to
hav one source: The 'proper' inset is not (always) locked.
So the quesion: Given almost everything including e.g. a InsetTabular *,
a LyXText *, a BufferView *, how do I lock the inset that _always_
works?
Andre'
Andre Poenitz wrote:
I think undo is almost back to normal. The present crashes seem all to
hav one source: The 'proper' inset is not (always) locked.
So the quesion: Given almost everything including e.g. a InsetTabular *,
a LyXText *, a BufferView *, how do I lock the inset that _always_
On Wed, Oct 15, 2003 at 05:35:20PM +0200, Alfredo Braunstein wrote:
I would think that bv-lockInset(inset), where inset is the inner inset you
are locking (an InsetText if inside a tabular) but I don't know really.
That's what I am doing. And it works sometimes ;-|
Andre'
Andre Poenitz wrote:
On Wed, Oct 15, 2003 at 05:35:20PM +0200, Alfredo Braunstein wrote:
I would think that bv-lockInset(inset), where inset is the inner inset
you are locking (an InsetText if inside a tabular) but I don't know
really.
That's what I am doing. And it works sometimes ;-|
On Wed, Oct 15, 2003 at 05:43:29PM +0200, Alfredo Braunstein wrote:
Andre Poenitz wrote:
On Wed, Oct 15, 2003 at 05:35:20PM +0200, Alfredo Braunstein wrote:
I would think that bv-lockInset(inset), where inset is the inner inset
you are locking (an InsetText if inside a tabular) but I
Alain == Alain Castera [EMAIL PROTECTED] writes:
Hello,
So I finally read Alain's (and the explanations he kindly made in
private mail). Better late than never :)
Alain Hi Angus. Here is the first one. It introduces a new button in
Alain the paragraph form (thus, it has to be ported to qt too
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| | If you're saying that such commands should be filtered out before
| | they get to the ASSERT, then that's fair enough, but some work is
| | needed because at the moment I can trigger the ASSERT as simply as this:
| Sure. We have a bug, but it
Andre Poenitz wrote:
By doing something like I do in undo.C with text2pit. Brute force.
Would be:
LyXText * par2text(BufferView * bv, Paragraph * par)
{
Buffer * buf = bv-buffer();
ParagraphList::iterator pt = buf-paragraphs().begin();
ParagraphList::iterator et =
Alfredo == Alfredo Braunstein [EMAIL PROTECTED] writes:
Alfredo I really need the InsetText (not the LyXText). We would need
Alfredo something like inset::getInset(int), similar to
Alfredo inset::getText(int).
what does Paragraph::inInset() return? The tabular?
JMarc
On Wed, Oct 15, 2003 at 06:26:51PM +0200, Alfredo Braunstein wrote:
What you are doing seems to solve the problem of not having a ParIterator
for your paragraph. I have (if you had a ParIterator, a pit.text() would be
enough for you, right?).
Yes.
I really need the InsetText (not the
Jean-Marc Lasgouttes wrote:
Alfredo == Alfredo Braunstein [EMAIL PROTECTED] writes:
Alfredo I really need the InsetText (not the LyXText). We would need
Alfredo something like inset::getInset(int), similar to
Alfredo inset::getText(int).
what does Paragraph::inInset() return? The
On Wed, Oct 15, 2003 at 06:39:32PM +0200, Alfredo Braunstein wrote:
Jean-Marc Lasgouttes wrote:
Alfredo == Alfredo Braunstein [EMAIL PROTECTED] writes:
Alfredo I really need the InsetText (not the LyXText). We would need
Alfredo something like inset::getInset(int), similar to
Alfredo
Andre Poenitz wrote:
There's a ParIterator-inset() and a ParIterator-index() nowadays.
inset-tabular.cell_info_of_cell(index).inset might do what you want.
Ah! But I have to cast to a tabular. Would be exceptionally ugly code (tm)
Is tabular the only one suffering this? Humm... I think I'll
On Tuesday 14 October 2003 3:29 pm, Ronald Florence wrote:
On Tuesday, October 14, 2003, at 11:12 AM, Angus Leeming wrote:
. Can you apply the patch by hand (its pretty tiny and both files
appear to be in the src dir rather than in src/support), or would you
rather
that I check that lyx
Lars Gullik Bjønnes wrote:
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| | If you're saying that such commands should be filtered out
| | before they get to the ASSERT, then that's fair enough, but some
| | work is needed because at the moment I can trigger the ASSERT as
| | simply as
Angus Leeming [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| | If you're saying that such commands should be filtered out
| | before they get to the ASSERT, then that's fair enough, but some
| | work is needed because at the moment
Lars Gullik Bjønnes wrote:
I actually thought I had a clean tree...
Yeh, yeh, yeh ;-)
Incidentally, I do like the idea of your #include changes, but I did
note that there was a cvs conflict in one of the Qt files...
--
Angus
Joao Luis Meloni Assirati wrote:
And finaly Angus, as promised, lyxclient.man. Can someone check my
horrible english?
Your english is not worse than mine (but that means nothing so no help here)
The patch works as advertised. Can I apply it (or someone else)?
Unfortunately, my xdvi (stock
Angus Leeming [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
I actually thought I had a clean tree...
| Yeh, yeh, yeh ;-)
| Incidentally, I do like the idea of your #include changes, but I did
| note that there was a cvs conflict in one of the Qt files...
So perhaps I shouldn't clean
I don't have a good traceback for this. I just opened a LyX file,
did a Find, hit the Find Next button a few times, and it crashed.
I have this on the console:
$ lyx fsmon.lyx
text not available!
no text in cache!
dont like 1, pos: 908 size: 28
dont like 1, pos: 50529027 size: 12
dont like 1,
On Wed, 15 Oct 2003, Alfredo Braunstein wrote:
Things still missing:
- qt support
The patch attached plus the two files socket_callback.{C,h}, that must be
placed under src/frontends/qt2, solve add qt support (don't forget to run
autogen/configure). The files socket_callback.{C,h} _really_
Hi.. I just tried defining a converter for the bundledoc/snapshot method
of packaging a .tex file that was suggested by Mark van Rossum. Both of
us ran into the same problem - after defining a converter, the View and
Export menus do not have the option for DVI, PS, PDF or PDF (dvipdfm)..
we're
Hello,
In lyx-qt, greek letters are displayed only in 'TeX' form. That is, the
Greek 'alpha', for example, is displayed on lyx-screen as
red-colored alpha.
I have had this problem since lyx-3.2, and this is the reason why the most
recent version of CJK-LyX-qt is CJK-LyX-qt-3.1(lyx-qt-3.1 is
Hello,
I have lost all the data on the ftp site, stone.phys.pusan.ac.kr, which I
have tried to recover, but in vain. I do not know what caused the problem,
but the machine has the history of being hacked from outside several
times. So, I decided to open a new ftp site for CJK-LyX,
This happens in the tex2lyx make on multiple architectures:
g++ -O2 -fno-exceptions -W -Wall -Wl,-R/u/ksylvan/lib -o tex2lyx FloatList.o
Floating.o counters.o lyxlayout.o lyxtextclass.o lyxlex.o lyxlex_pimpl.o boost.o
context.o gettext.o lyxfont.o texparser.o tex2lyx.o preamble.o math.o table.o
On Tue, Oct 14, 2003 at 06:39:10PM +0200, Alfredo Braunstein wrote:
> Andre Poenitz wrote:
>
> > Hm... not sure this is worthwhile.
>
> neother do I.
>
> > Maybe we could jsut leave it as it is and keep the solution (init to
> > 0) in bugzilla and use that when 1.4.0 is about to be released?
>
On Tue, Oct 14, 2003 at 11:34:13PM -0700, Kayvan A. Sylvan wrote:
> This happens in the tex2lyx make on multiple architectures:
>
> g++ -O2 -fno-exceptions -W -Wall -Wl,-R/u/ksylvan/lib -o tex2lyx FloatList.o
> Floating.o counters.o lyxlayout.o lyxtextclass.o lyxlex.o lyxlex_pimpl.o boost.o
>
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Andre Poenitz <[EMAIL PROTECTED]> writes:
>>> real 0m51.848s user 0m0.200s sys 0m0.020s
>>>
>>> On my AMD 2400+, but that is over a 384kb/s line.
>>
Lars> | Strange numbers... The first one looks ok, but 52s is too much
Lars>
On Tue, Oct 14, 2003 at 04:24:59PM +0200, Lars Gullik Bjønnes wrote:
> | which involves a full rebreak and seems acceptable _for me_ even for
> | buffer switching. But that's an AMD 1700+.
>
> I'll do a proper test when I get home.
Any results?
Andre'
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Kayvan A. Sylvan wrote:
>> Thanks. ./autogen.sh and ./configure and make fixed it.
Angus> If you ./configure --enable-maintainer-mode then all will
Angus> happen auto-magically when you type make...
Note that we could have
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> This moves the lastfiles global variable into LyX and makes
Angus> emergencyCleanup a non-static member function.
+ * BufferView_pimpl.C (loadLyXFile):
+ * MenuBackend.C (expandLastfiles):
+ * bufferlist.C
Andre Poenitz wrote:
> On Tue, Oct 14, 2003 at 11:34:13PM -0700, Kayvan A. Sylvan wrote:
>> This happens in the tex2lyx make on multiple architectures:
>>
>> g++ -O2 -fno-exceptions -W -Wall -Wl,-R/u/ksylvan/lib -o tex2lyx
>> FloatList.o Floating.o counters.o lyxlayout.o lyxtextclass.o
>>
On Wed, Oct 15, 2003 at 10:15:20AM +0100, Angus Leeming wrote:
> So, I think that the problem is that the symbolic link still exists
> in your build tree.
> rm build/src/tex2lyx/boost.C
> should solve the problem.
Works. Thanks.
Andre'
--
Those who desire to give up Freedom in order
Jean-Marc Lasgouttes wrote:
> Angus> This moves the lastfiles global variable into LyX and makes
> Angus> emergencyCleanup a non-static member function.
>
> + * BufferView_pimpl.C (loadLyXFile):
> + * MenuBackend.C (expandLastfiles):
> + * bufferlist.C (MenuWrite, QuitLyX):
> +
On Wed, Oct 15, 2003 at 10:25:02AM +0100, Angus Leeming wrote:
> > Maybe is it just that I do not really understand what a singleton
> > class is...
>
> Here is a stripped down version of the class.
I still don't understand why you don't use a namespace.
> class LyX {
> public:
> static
On Wednesday 15 October 2003 09:39, Jean-Marc Lasgouttes wrote:
>
> Note that we could have --enable-maintainer-mode default to true for
> development versions.
That would be good, is there any drawback for this approach?
> JMarc
--
José Abílio
LyX and docbook, a perfect match. :-)
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>> | So I have a copy of pybliographer (say) that hasn't kept up with
>> | the changing LyX syntax and the first time I use it I crash LyX?
>>>
>> | You're absolutely barking mad if you think that will improve the
>> | public
Andre Poenitz wrote:
> I still don't understand why you don't use a namespace.
> in the .h:
> namespace lyxglobal {
> void exec(int argc, char * argv[]);
> LyX & ref();
> LyX const & cref();
> }
Maybe nest the namespace
namespace lyx {
namespace global {
void
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Tue, Oct 14, 2003 at 04:24:59PM +0200, Lars Gullik Bjønnes wrote:
>> | which involves a full rebreak and seems acceptable _for me_ even for
>> | buffer switching. But that's an AMD 1700+.
>>
>> I'll do a proper test when I get home.
>
| Any results?
Hi Angus,
I discovered that I need this for the gtk port to compile. I think that you
forgot some bits. :-)
Is the following patch ok?
--
José Abílio
LyX and docbook, a perfect match. :-)
Index: po/POTFILES.in
===
Jose' Matos wrote:
> Hi Angus,
> I discovered that I need this for the gtk port to compile. I think
> that you forgot some bits. :-)
>
> Is the following patch ok?
Looks sensible...
--
Angus
On Wed, Oct 15, 2003 at 10:47:50AM +0100, Angus Leeming wrote:
> Andre Poenitz wrote:
> > I still don't understand why you don't use a namespace.
>
> > in the .h:
> > namespace lyxglobal {
> > void exec(int argc, char * argv[]);
> > LyX & ref();
> > LyX const & cref();
On Wed, Oct 15, 2003 at 11:47:05AM +0200, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> | On Tue, Oct 14, 2003 at 04:24:59PM +0200, Lars Gullik Bjønnes wrote:
> >> | which involves a full rebreak and seems acceptable _for me_ even for
> >> | buffer switching. But
> "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes:
Jose'> On Wednesday 15 October 2003 09:39, Jean-Marc Lasgouttes wrote:
>> Note that we could have --enable-maintainer-mode default to true
>> for development versions.
Jose'> That would be good, is there any drawback for this approach?
Andre Poenitz wrote:
> Or lyx::global::updateInset(this) ;-)
> [Which suspiciously feels like using 'current_view' *cough*]
But isn't...
Hmmm, so you're suggesting a bunch of free functions which provide a
world-visble interface to class LyX's member variables, this class
itself being hidden
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Wed, Oct 15, 2003 at 11:47:05AM +0200, Lars Gullik Bjønnes wrote:
>> Andre Poenitz <[EMAIL PROTECTED]> writes:
>>
>> | On Tue, Oct 14, 2003 at 04:24:59PM +0200, Lars Gullik Bjønnes wrote:
>> >> | which involves a full rebreak and seems acceptable
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Andre Poenitz wrote:
>> Or lyx::global::updateInset(this) ;-) [Which suspiciously feels
>> like using 'current_view' *cough*]
Angus> But isn't...
Angus> Hmmm, so you're suggesting a bunch of free functions which
Angus> provide a
On Wed, Oct 15, 2003 at 11:29:56AM +0100, Angus Leeming wrote:
> Andre Poenitz wrote:
> > Or lyx::global::updateInset(this) ;-)
> > [Which suspiciously feels like using 'current_view' *cough*]
> But isn't...
I know.
> Hmmm, so you're suggesting a bunch of free functions which provide a
>
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>> "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes:
>
| Jose'> On Wednesday 15 October 2003 09:39, Jean-Marc Lasgouttes wrote:
>>> Note that we could have --enable-maintainer-mode default to true
>>> for development versions.
>
| Jose'>
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Wed, Oct 15, 2003 at 11:29:56AM +0100, Angus Leeming wrote:
>> Andre Poenitz wrote:
>> > Or lyx::global::updateInset(this) ;-)
>> > [Which suspiciously feels like using 'current_view' *cough*]
>> But isn't...
>
| I know.
>
>> Hmmm, so you're
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Wed, Oct 15, 2003 at 11:29:56AM +0100, Angus Leeming wrote:
>> Andre Poenitz wrote:
>> > Or lyx::global::updateInset(this) ;-)
>> > [Which suspiciously feels like using 'current_view' *cough*]
>> But isn't...
>
| I know.
>
>> Hmmm, so you're
On Wed, Oct 15, 2003 at 12:36:52PM +0200, Jean-Marc Lasgouttes wrote:
> But class LyX's member variables are just a bunch of global variables
> hidden in a `singleton class' just for the sake of using a buzzword,
> aren't they?
Sort of. The problem is there are languages (like Java) where using
Jean-Marc Lasgouttes wrote:
>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> Andre Poenitz wrote:
>>> Or lyx::global::updateInset(this) ;-) [Which suspiciously feels
>>> like using 'current_view' *cough*]
> Angus> But isn't...
>
> Angus> Hmmm, so you're suggesting a bunch
On Wed, Oct 15, 2003 at 12:08:53PM +0100, Angus Leeming wrote:
> Jean-Marc Lasgouttes wrote:
>
> >> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
> >
> > Angus> Andre Poenitz wrote:
> >>> Or lyx::global::updateInset(this) ;-) [Which suspiciously feels
> >>> like using 'current_view'
Andre Poenitz <[EMAIL PROTECTED]> writes:
| Statics in a single file will be destructed in last-to-first order.
One problem is still that several of the global varialbes cannot be
static, they need more information before they can be initialized.
That is easily solved with a class.
Also
Lars Gullik Bjønnes wrote:
>>> I can see it is possible. Why is it 'preferable'?
>>
> | Free functions provide (often...) better encapsulation (Scott
> | Meyers?).
>
> Btu not if they operatoe on global variables... then you do not gain
> anything.
Where do you stand on the particular design
Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> | Statics in a single file will be destructed in last-to-first
> | order.
>
> One problem is still that several of the global varialbes cannot be
> static, they need more information before they can be initialized.
>
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
I can see it is possible. Why is it 'preferable'?
>>>
>> | Free functions provide (often...) better encapsulation (Scott
>> | Meyers?).
>>
>> Btu not if they operatoe on global variables... then you do not gain
>>
On Wed, Oct 15, 2003 at 01:52:31PM +0200, Lars Gullik Bjønnes wrote:
> Free functions should ideally not access class variables,
This assumes that the class is not a random collection of individual
thing - which it is in our case - but "something real".
> the functions should be free only when
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> However, I don't think that any of this is really anything more
Angus> than aesthetics. I _may_ go down this route, but I'm much more
Angus> interested in [...]
Of course :)
JMarc
1 - 100 of 128 matches
Mail list logo