Le 20 avr. 10 à 18:53, Vincent van Ravesteijn - TNW a écrit :
Anyway, JMarc, you want to finish what you started ;) ?
I did the easy part, and I am waiting for the hero that will do the
hard part :)
Seriously, I have yet to see what is the right solution to this
problem. Passing
the Disp
>Don't know if it helps, but that's where I'd start.
The thing that helps is to call
disp_.setMessage(docstring());
at the beginning of Cursor::dispatch().
However, this would break messaging in case of nested dispatch calls.
This would mean you'd have to clear the message from BufferView
Jean-Marc Lasgouttes wrote:
>> that wont solve my flaming because i wanted something for pdf
>> viewer, not default viewer (which can get completely new shortcut
>> anyway).
>
> I think that with the amount of effort that went into giving everybody his
> prefered viewer setting, it becomes a bit po
Le 20 avr. 10 à 18:45, Pavel Sanda a écrit :
chmm, we already have Buffer::absFileName. isn't possible
that something goes wrong in the code like:
Buffer::foo(){
foo2(...FileName(absFileName()),absFileName(),...)
}
dont remember exact rules but iirc c++ naming lookup was
doing pretty wild a
Le 20 avr. 10 à 17:58, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
Le 20 avr. 10 ? 17:30, Pavel Sanda a écrit :
I'd rather have Ctrl+p for preview, maybe.
what does it mean?
No View PDF, but View with default viewer. Of couse, now I notice
that the
command name is View, not Preview
Pavel Sanda wrote:
> hi,
>
> anybody against the change of this method name
> to be compatible camel case with the class itself?
chmm, we already have Buffer::absFileName. isn't possible
that something goes wrong in the code like:
Buffer::foo(){
foo2(...FileName(absFileName()),absFileName()
On 04/20/2010 11:34 AM, Rob Oakes wrote:
Dear LyX Developers,
I thought that I would take a stab at fixing bug #6650,
http://www.lyx.org/trac/ticket/6650 (mostly because it is driving me to
absolute distraction). Thus, I've been looking at the code in the two
messages classes, GuiApplication (w
On 4/18/2010 7:15 PM, Uwe Stöhr wrote:
I don't have compile problems with CMake.
Just to make sure, did you compile the tarball or did you checkout the
alpha2 revision from SVN? SVN checkouts work fine for me, but I can't
compile the alpha1 and alpha2 tarballs.
Joost
And I would integrate it more into the LyX application.
One of my goals is to make the installer for Mac obsolete.
It'd be great to have a platform-independent dictionary/thesaurus
installation wizard.
Are you still planning to use Aspell for the LyX 2.0 Mac installers? On
Windows I'm trying
Jean-Marc Lasgouttes wrote:
> Le 20 avr. 10 ? 17:30, Pavel Sanda a écrit :
>>> I'd rather have Ctrl+p for preview, maybe.
>>
>> what does it mean?
>
> No View PDF, but View with default viewer. Of couse, now I notice that the
> command name is View, not Preview :)
that wont solve my flaming becaus
Kornel Benko wrote:
> I am using it from time to time. But I don't insist too strong.
i'm talking about shortcuts, so whats your ratio between viewing
via pdf and printing via lyx dialog?
pavel
Am Dienstag 20 April 2010 schrieb Pavel Sanda:
> hi,
>
> for long time i'm wondering why we have print dialog
> because before sending anything to the printer one has
> to check things in real viewer. once you are in viewer
> you print it from there.
>
> can't remember a single case to use it and
Le 20 avr. 10 à 17:30, Pavel Sanda a écrit :
I'd rather have Ctrl+p for preview, maybe.
what does it mean?
No View PDF, but View with default viewer. Of couse, now I notice that
the
command name is View, not Preview :)
Killing it would not be bad, if we are sure we do not lose any
featur
Dear LyX Developers,
I thought that I would take a stab at fixing bug #6650,
http://www.lyx.org/trac/ticket/6650 (mostly because it is driving me to
absolute distraction). Thus, I've been looking at the code in the two
messages classes, GuiApplication (where the status indicator is updated)
and t
Jean-Marc Lasgouttes wrote:
> Le 20 avr. 10 ? 17:23, Pavel Sanda a écrit :
>> what about to remove its shortcut in favour of using
>> ctrl+p for pdf viewing?
>> (assignment of ctr+shift+p for update would kill
>> font-typewriter though...)
>
> I'd rather have Ctrl+p for preview, maybe.
what does i
Le 20 avr. 10 à 17:23, Pavel Sanda a écrit :
what about to remove its shortcut in favour of using
ctrl+p for pdf viewing?
(assignment of ctr+shift+p for update would kill
font-typewriter though...)
I'd rather have Ctrl+p for preview, maybe.
pdf is probably more used than ps nowadays and switc
Le 20 avr. 10 à 16:46, Pavel Sanda a écrit :
anybody against the change of this method name
to be compatible camel case with the class itself?
Not me.
JMarc
hi,
for long time i'm wondering why we have print dialog
because before sending anything to the printer one has
to check things in real viewer. once you are in viewer
you print it from there.
can't remember a single case to use it and i suspect
its also common for other users.
what about to remo
hi,
anybody against the change of this method name
to be compatible camel case with the class itself?
pavel
Richard Heck wrote:
> On 04/20/2010 09:16 AM, Jean-Marc Lasgouttes wrote:
>>> In this case, I don't see how we could take advantage of that.
>>> If the alert is never displayed again, the choice cannot be reverted.
>>> Then, the alert doesn't distinguish between ancillary files and main
>>> file.
On Tue, Apr 20, 2010 at 09:20:32AM -0400, rgheck wrote:
> On 04/20/2010 09:16 AM, Jean-Marc Lasgouttes wrote:
> >>In this case, I don't see how we could take advantage of that.
> >>If the alert is never displayed again, the choice cannot be reverted.
> >>Then, the alert doesn't distinguish between
On 04/20/2010 09:16 AM, Jean-Marc Lasgouttes wrote:
In this case, I don't see how we could take advantage of that.
If the alert is never displayed again, the choice cannot be reverted.
Then, the alert doesn't distinguish between ancillary files and main
file.
Ah, we have no way to revert these
The attached patch implements export of math as images for XHTML.
I am morally certain that there are lots of things here that could be
done better. I do not really understand the code very well. I don't
think the patch breaks anything, but I'm guessing (and hoping) that
people will have desi
In this case, I don't see how we could take advantage of that.
If the alert is never displayed again, the choice cannot be reverted.
Then, the alert doesn't distinguish between ancillary files and main
file.
Ah, we have no way to revert these dialog choices? This is very bad.
JMarc
On 04/20/2010 06:14 AM, Pavel Sanda wrote:
Richard Heck wrote:
There's also a question about what to do with the new InsetPreview. I
haven't thought much about this.
i hoped that this could be solved by the same mechanism as when
the math insets are plain images in the output...
Am 20.04.2010 um 12:57 schrieb Jean-Marc Lasgouttes:
> Le 20 avr. 10 à 12:55, Jürgen Spitzmüller a écrit :
>> Stephan Witt wrote:
>>> Then I propose to use some hard coded path below $sysdir for the shipped
>>> directories and the user may specify another path for the extra
>>> dictionaries in pre
On Tue, Apr 20, 2010 at 01:58:56PM +0200, Jean-Marc Lasgouttes wrote:
> Le 20 avr. 10 à 13:38, Enrico Forestieri a écrit :
> >No, they do not. I explicitly check that the switch is only obeyed
> >when
> >operating in batch mode. It is easy to make it work also in GUI
> >mode, but
> >I think that i
Le 20 avr. 10 à 13:38, Enrico Forestieri a écrit :
No, they do not. I explicitly check that the switch is only obeyed
when
operating in batch mode. It is easy to make it work also in GUI
mode, but
I think that it is wrong. The correct way for GUI mode would be a RC
setting allowing to silentl
On Tue, Apr 20, 2010 at 12:27:00PM +0200, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > > > >This has always been like that and I didn't change it. It is surprising
> > > > >that this has never annoyed you and suddenly now it does.
> > > > >Moreover, I think that this correct, as lyx should ne
Le 20 avr. 10 à 12:55, Jürgen Spitzmüller a écrit :
Stephan Witt wrote:
Then I propose to use some hard coded path below $sysdir for the
shipped
directories and the user may specify another path for the extra
dictionaries in preferences.
Note that we only have one path at disposal currently.
Stephan Witt wrote:
> Then I propose to use some hard coded path below $sysdir for the shipped
> directories and the user may specify another path for the extra
> dictionaries in preferences.
Note that we only have one path at disposal currently. So you need to use one
for both aims.
Jürgen
Am 20.04.2010 um 12:28 schrieb Jürgen Spitzmüller:
> Also sprach Stephan Witt:
>> So the question is: is it legal to ship those dictionaries with LyX?
>> Can some kind soul with the knowledge about such things tell?
>
> Depends on the licensing of the specific dictionaries, which are third-party-
J?rgen Spitzm?ller wrote:
> My proposal would be to have those dictionaries on a server and let the
> installers download them, if required. This is what the Windows installers do
this would also considerably reduce the size of the installers...
pavel
Stephan Witt wrote:
> So the question is: is it legal to ship those dictionaries with LyX?
> Can some kind soul with the knowledge about such things tell?
what is their license?
pavel
Also sprach Stephan Witt:
> So the question is: is it legal to ship those dictionaries with LyX?
> Can some kind soul with the knowledge about such things tell?
Depends on the licensing of the specific dictionaries, which are third-party-
contributions to Ooo. Most have "Opensource" license accord
Enrico Forestieri wrote:
> > > >This has always been like that and I didn't change it. It is surprising
> > > >that this has never annoyed you and suddenly now it does.
> > > >Moreover, I think that this correct, as lyx should never overwrite a
> > > >file without permission.
> > > >
> > > So, if A
Am 20.04.2010 um 12:02 schrieb Jürgen Spitzmüller:
> Stephan Witt wrote:
>> I've to correct me. When I open the thesaurus dialog it looks like the
>> language is selected and the dictionary found. But the message in the
>> lower part indicates that there is no thesaurus available. So I thought it
Richard Heck wrote:
> There's also a question about what to do with the new InsetPreview. I
> haven't thought much about this.
i hoped that this could be solved by the same mechanism as when
the math insets are plain images in the output...
pavel
Stephan Witt wrote:
> I've to correct me. When I open the thesaurus dialog it looks like the
> language is selected and the dictionary found. But the message in the
> lower part indicates that there is no thesaurus available. So I thought it
> does not work... mostly because last time I tried in fa
Am 20.04.2010 um 11:47 schrieb Jürgen Spitzmüller:
> Stephan Witt wrote:
>> Sorry I was fooled by the dialog contents.
>> If I try to lookup something it works now.
>
> Excellent.
Good. Hopefully I'm fast enough this time :)
Stephan
Am 20.04.2010 um 11:46 schrieb Jürgen Spitzmüller:
> Stephan Witt wrote:
>> Output of -dbg files:
>>
>> /Users/stephan/cvs/lyx/lyx-devel/src/Thesaurus.cpp(81): thesaurus path:
>> /Users/stephan/Documents/Dictionaries
>> /Users/stephan/cvs/lyx/lyx-devel/src/support/FileName.cpp(417): filtering
>>
Stephan Witt wrote:
> Sorry I was fooled by the dialog contents.
> If I try to lookup something it works now.
Excellent.
Jürgen
Stephan Witt wrote:
> Output of -dbg files:
>
> /Users/stephan/cvs/lyx/lyx-devel/src/Thesaurus.cpp(81): thesaurus path:
> /Users/stephan/Documents/Dictionaries
> /Users/stephan/cvs/lyx/lyx-devel/src/support/FileName.cpp(417): filtering
> on extension *.idx is requested.
> /Users/stephan/cvs/lyx/ly
On 04/20/2010 11:12 AM, Vincent van Ravesteijn - TNW wrote:
The problem was that I never expected that InsetInfo
is a child class of InsetCollapsable. This feels wrong.
We need something between InsetText and InsetCollapsable
or we migrate the inset decoration to InsetText. Then
Le 20 avr. 10 à 08:57, Vincent van Ravesteijn - TNW a écrit :
Note that you could define generic implementations for
copying to text and latex with little effort.
I thought I did so.
I meant implementing this new lfun directly in Inset::dispatch.
Copying as
text or as latex can be done by
>> The problem was that I never expected that InsetInfo
>> is a child class of InsetCollapsable. This feels wrong.
>
> We need something between InsetText and InsetCollapsable
> or we migrate the inset decoration to InsetText. Then
> InsetCollapsable would just add tha abil
Stephan Witt wrote:
> * What am I missing with my thesaurus? Any ideas?
I just fixed a thesaurus problem in trunk. Does an svn up help? If not, "-dbg
files" should provide more information.
Jürgen
Am 20.04.2010 um 00:18 schrieb Jean-Marc Lasgouttes:
> Le 19 avr. 10 à 17:34, Stephan Witt a écrit :
>> I can live with it. The code would be less cluttered.
>> But if I read the developer docs of mac correct there is a standard.
>> It is called "The anatomy of a bundle".
>
> Indeed. But if we pu
On 04/20/2010 10:45 AM, Vincent van Ravesteijn - TNW wrote:
The problem was that I never expected that InsetInfo is a child
class
of InsetCollapsable. This feels wrong.
We need something between InsetText and InsetCollapsable or we
migrate the inset decoration
>>> The problem was that I never expected that InsetInfo is a child
>>> class
>>>
>
>>> of InsetCollapsable. This feels wrong.
>>>
>> We need something between InsetText and InsetCollapsable or we
>> migrate the inset decoration to InsetText. Then InsetCollapsable
>> would j
On 04/20/2010 10:33 AM, Vincent van Ravesteijn - TNW wrote:
The problem was that I never expected that InsetInfo is a child class
of InsetCollapsable. This feels wrong.
We need something between InsetText and InsetCollapsable
or we migrate the inset decoration to InsetTe
>> The problem was that I never expected that InsetInfo is a child class
>> of InsetCollapsable. This feels wrong.
>
>We need something between InsetText and InsetCollapsable
>or we migrate the inset decoration to InsetText. Then
>InsetCollapsable would just add tha ability to collapse.
>
>Note
On 04/19/2010 06:10 PM, Vincent van Ravesteijn wrote:
Better(?) fix for bug #6659: InsetInfo context menu disabled unless
cursor immediately in front.
Much better indeed.
Year, I was about to complain ;-)
The problem was that I never expected that InsetInfo is a child class
of InsetColla
53 matches
Mail list logo
