Re: GUI changes for inserting citations in 2.2x

[Charles de Miramon]

Maria Gouskova wrote:

> Hi developers,
> 
> I just upgraded to 2.2.1 today. I can see that there have been a lot of
> changes in the appearance of the interface, so obviously quite a lot of
> work went into the redesign. I confess I was stumped, though, when I went
> to insert a citation. The "Search" and "Formatting" options are hidden,
> and it's done in such a way that if I didn't know that they were there, it
> would not occur to me that those areas of the window were clickable. So I
> was wondering what the motivation was for the change--I can see that it's
> a "cleaner" look, but I think it really hampers the usability of the GUI,
> especially for new users.
> 

I agree with Maria that the new dialog is a usability regression.

If there is a redesign of the dialog, could it be posible to put the search 
field on the top ?

My workflow to insert a citation is :

1) type the name of the author or some word of the title. My main 
bibliography file has around 1900 entries and grows slowly. 
2) select the exact reference in the list
3) add a page number
4) insert

Having the search field on top and the results below is what is intuitive 
today after years of Google use.

I think kbibtex has a rather nice search field that take little vertical 
space and hides seldom used search options behind a button.


If you have search-as-you-type, I'm wondering who needs search with regular 
expressions. I'm certainly not a real geek !

Cheers,
Charles

Re: About LyX menus usability.

[Charles de Miramon]

Pavel Sanda wrote:

 Pavel Sanda wrote:
 Well, he launches it and discovers that his Office has similar order as
 his
 
 s/Office/LyX/
 
 Office (just tried here): File, Edit, View, Insert, Format (mixture of
 our text style and Doc settings), Table, Tools, Windows, Help.
 
 Pavel

Why LyX could not add 'Format' and 'Table'to mimick more classical 
wordprocessors menu organization ?  

Computer screens have become wider. 

My wife uses mostly Libreoffice writer and sometimes LyX. She had problem 
finding how to center a paragraph. She found the location of the formatting 
menu in Edit puzzling.

Like Pavel, I find the Insert menu too long. Maybe, everything that relates 
to the life cycle of the document (annotations, branches) could go into 
'Document'  

Cheers,
Charles

Re: About LyX menus & usability.

[Charles de Miramon]

Pavel Sanda wrote:

> Pavel Sanda wrote:
>> Well, he launches it and discovers that his Office has similar order as
>> his
> 
> s/Office/LyX/
> 
>> Office (just tried here): File, Edit, View, Insert, Format (mixture of
>> our text style and Doc settings), Table, Tools, Windows, Help.
>> 
>> Pavel

Why LyX could not add 'Format' and 'Table'to mimick more classical 
wordprocessors menu organization ?  

Computer screens have become wider. 

My wife uses mostly Libreoffice writer and sometimes LyX. She had problem 
finding how to center a paragraph. She found the location of the formatting 
menu in Edit puzzling.

Like Pavel, I find the Insert menu too long. Maybe, everything that relates 
to the life cycle of the document (annotations, branches) could go into 
'Document'  

Cheers,
Charles

Re: Spellchecker and thesaurus for LyX/Mac

[Charles de Miramon]

Jean-Marc Lasgouttes wrote:


 Hunspell can be seen as some kind of successor to aspell. At least it is
 supposed to be better (am I right?)
 

Yes. Hunspell can deal with coumpound words (two words joined in one) which 
are very common in German and suffix and affix which are used in Hungarian 
and certainly other languages.

Hunspell homepage links to an Enchant frontend for Mac OS/X

Cheers,
Charles

Re: Broken HTML/OpenDocument Code Generation

[Charles de Miramon]

Rainer Dorsch wrote:

 Hello,
 
 I have a small LyX document, which shows a combination of a hyperlink and
 an svg figure break html/opendocument generation:
 
 The source documentation is here
 
 http://bokomoko.de/~rd/lyxtest/
 
 The output I get is here
 
 http://bokomoko.de/~rd/lyxtest/output/lyx_tmpbuf0/test.html
 
 I have a self-compiled version of LyX 1.6.5 and texlive and tex4ht from
 Debian stable:
 

Here, it works. I'm on debian unstable.

Cheers,
Charles

Re: Spellchecker and thesaurus for LyX/Mac

[Charles de Miramon]

Jean-Marc Lasgouttes wrote:


> Hunspell can be seen as some kind of successor to aspell. At least it is
> supposed to be better (am I right?)
> 

Yes. Hunspell can deal with coumpound words (two words joined in one) which 
are very common in German and suffix and affix which are used in Hungarian 
and certainly other languages.

Hunspell homepage links to an Enchant frontend for Mac OS/X

Cheers,
Charles

Re: Broken HTML/OpenDocument Code Generation

[Charles de Miramon]

Rainer Dorsch wrote:

> Hello,
> 
> I have a small LyX document, which shows a combination of a hyperlink and
> an svg figure break html/opendocument generation:
> 
> The source documentation is here
> 
> http://bokomoko.de/~rd/lyxtest/
> 
> The output I get is here
> 
> http://bokomoko.de/~rd/lyxtest/output/lyx_tmpbuf0/test.html
> 
> I have a self-compiled version of LyX 1.6.5 and texlive and tex4ht from
> Debian stable:
> 

Here, it works. I'm on debian unstable.

Cheers,
Charles

RE: Enhancement bugs for 2.0

[Charles de Miramon]

Vincent van Ravesteijn - TNW wrote:

* http://www.lyx.org/trac/ticket/2625
convert the search dialog to a search bar

to me it was fixed by new search pane. Vincent however have idea
to convert the current simple search dialog into search bar. opinions?
anybody wants to work on it? otherwise c.
 
 I've already done some work on it. I really want to have this in 2.0.0,
 so we have a polished brand new search and replace functionality.
 
 If not before 2.0.0, it must be done as soon as possible, so never c).
 
 Anyway, sign me up for this one.
 

I have just tried the svn trunk version and the new searchreplace. It is 
great and I have have been longing this feature for years. Thank you Tommaso 
and the others.

But do we really need two searchreplace items in the menu ? 

I have argued in the past and I still believe that LyX menus are suffering 
from Emacs-Disease and there are too many items. LyX should not be 
intimidating for new users and shows its power step by step.   

Would it not be better to have one searchreplace dialog and a button to 
toggle between simple mode and advanced mode.

Today the advanced mode pane design is different than the simple one in term 
of place of the find button, replace button, replace all button, locations 
of the checkboxes. 

Usability wise, it is not optimal.

Cheers,
Charles

RE: Enhancement bugs for 2.0

[Charles de Miramon]

Vincent van Ravesteijn - TNW wrote:

 
 Did you update today ? I think they are now exactly the same.
 

Thank you. It is much better. Still, I would go further and get rid of the 
advanced tab:

- At the top of the pane I would put the scope as a combo box
- Then a smaller Find TextEdit
- Then the Regular Expression combo
- Then on the left the Case Sensitive, Whole words only, Search backwards, 
Ignore Format checkboxes 
- On the right ; Search Next button

- A smaller Replace TextEdit
- Preserve first case on replace checkbox on the left (I don't really 
understand the option, should it not be 'preserve original formatting when 
replacing') 
- Replace
- Replace all

- I think there is a need for a reset button to erase everything and take 
away any formatting in the Search textedit

Would it also be possible that when you check 'Ignore format' any formatting 
in the Search TextEdit is suppressed ?

Nitpicks :
- F3 shortkey does not work in the advanced searchreplace
- Some shortkeys are different in the quick search and the advanced one


Cheers,
Charles

RE: Enhancement bugs for 2.0

[Charles de Miramon]

Vincent van Ravesteijn - TNW wrote:

>>* http://www.lyx.org/trac/ticket/2625
>>convert the search dialog to a search bar
>>
>>to me it was fixed by new search pane. Vincent however have idea
>>to convert the current simple search dialog into search bar. opinions?
>>anybody wants to work on it? otherwise c.
> 
> I've already done some work on it. I really want to have this in 2.0.0,
> so we have a polished brand new search and replace functionality.
> 
> If not before 2.0.0, it must be done as soon as possible, so never c).
> 
> Anyway, sign me up for this one.
> 

I have just tried the svn trunk version and the new search It is 
great and I have have been longing this feature for years. Thank you Tommaso 
and the others.

But do we really need two search items in the menu ? 

I have argued in the past and I still believe that LyX menus are suffering 
from Emacs-Disease and there are too many items. LyX should not be 
intimidating for new users and shows its power step by step.   

Would it not be better to have one search dialog and a button to 
toggle between simple mode and advanced mode.

Today the advanced mode pane design is different than the simple one in term 
of place of the find button, replace button, replace all button, locations 
of the checkboxes. 

Usability wise, it is not optimal.

Cheers,
Charles

RE: Enhancement bugs for 2.0

[Charles de Miramon]

Vincent van Ravesteijn - TNW wrote:

> 
> Did you update today ? I think they are now exactly the same.
> 

Thank you. It is much better. Still, I would go further and get rid of the 
advanced tab:

- At the top of the pane I would put the scope as a combo box
- Then a smaller Find TextEdit
- Then the Regular Expression combo
- Then on the left the Case Sensitive, Whole words only, Search backwards, 
Ignore Format checkboxes 
- On the right ; Search Next button

- A smaller Replace TextEdit
- Preserve first case on replace checkbox on the left (I don't really 
understand the option, should it not be 'preserve original formatting when 
replacing') 
- Replace
- Replace all

- I think there is a need for a reset button to erase everything and take 
away any formatting in the Search textedit

Would it also be possible that when you check 'Ignore format' any formatting 
in the Search TextEdit is suppressed ?

Nitpicks :
- F3 shortkey does not work in the advanced search
- Some shortkeys are different in the quick search and the advanced one


Cheers,
Charles

Re: [Patch] Improving the Citation GUI.

[Charles de Miramon]

rgheck wrote:

   
 Feel free to grab Qt Designer and work on this. Or at least produce a
 mock-up.
 



I found the CitationUi.ui file and opened it in Qt Designer. But before 
playing with it, I was wondering about the possibility to have multiple 
Citations.

The only use case is, if I understand it correctly, when you are using some 
natbib style where you have \cite{Heck2007, HeckBis2007, Heck2009) to get 
something like Heck, 2007, 2007a, 2009

If it is the case, then you could get rid of the multiple citations part of 
the dialog. It would be possible only to insert one citation with an 
optional prefix/postfix.  

And have a general option for the document in the bibliographical pane 
(Concatenate Citations) which would during the latex export concatenate 
Citation insets separated only by space into a \cite{a, b, c}

Cheers,
Charles  

Cmake and installing the svn version without messing LyX 1.6

[Charles de Miramon]

Hello,

I have compiled LyX through the cmake way and it looks faster than the old 
autotools

I would like to do a make install but not mess my LyX 1.6 and install the 
files in /usr/share/LyX20 

How should I do that ?


Maybe INSTALL.Cmake could be a little bit fleshed out. At least for the poor 
dummies, it would be nice to know that you have to do cmake than make and 
make install.

Cheers,
Charles

Re: [Patch] Improving the Citation GUI.

[Charles de Miramon]

rgheck wrote:

   
> Feel free to grab Qt Designer and work on this. Or at least produce a
> mock-up.
> 



I found the CitationUi.ui file and opened it in Qt Designer. But before 
playing with it, I was wondering about the possibility to have multiple 
Citations.

The only use case is, if I understand it correctly, when you are using some 
natbib style where you have \cite{Heck2007, HeckBis2007, Heck2009) to get 
something like Heck, 2007, 2007a, 2009

If it is the case, then you could get rid of the multiple citations part of 
the dialog. It would be possible only to insert one citation with an 
optional prefix/postfix.  

And have a general option for the document in the bibliographical pane 
(Concatenate Citations) which would during the latex export concatenate 
Citation insets separated only by space into a \cite{a, b, c}

Cheers,
Charles  

Cmake and installing the svn version without messing LyX 1.6

[Charles de Miramon]

Hello,

I have compiled LyX through the cmake way and it looks faster than the old 
autotools

I would like to do a make install but not mess my LyX 1.6 and install the 
files in /usr/share/LyX20 

How should I do that ?


Maybe INSTALL.Cmake could be a little bit fleshed out. At least for the poor 
dummies, it would be nice to know that you have to do cmake than make and 
make install.

Cheers,
Charles

Re: [Patch] Improving the Citation GUI.

[Charles de Miramon]

John McCabe-Dansted wrote:

 The attached patch resolved the following tickets:
   #6486 Citation not selected by default.
   #6487 Add file and url links to Citation Dialog.

Thank you for #6486

I think the dialog would be simpler to use if it had a more classical look 
like Endnote X2 insertion dialog :

see : http://www.edtechblog.org/2009/01/i-am-switching-from-ms-word-to-
apple-pages/

Quick search at the top

The list of references below

The formatted reference in a grey zone (and not in white)

The formatting options

I would suppress from LyX dialog the option enabling Search-as-you-type. For 
me it seems that having it the defaut is what is expected

I'm also wondering what are the use case of a regular expression search or a 
case search. If I cite something when writing, either I remember the name of 
the author or a word in the title or maybe the name of the journal. 

But finding a bibliographical reference with a regular expression, I must 
not be geek enough ;-)

Cheers,
Charles

Re: [Patch] Improving the Citation GUI.

[Charles de Miramon]

John McCabe-Dansted wrote:

> The attached patch resolved the following tickets:
>   #6486 Citation not selected by default.
>   #6487 Add "file" and "url" links to Citation Dialog.

Thank you for #6486

I think the dialog would be simpler to use if it had a more classical look 
like Endnote X2 insertion dialog :

see : http://www.edtechblog.org/2009/01/i-am-switching-from-ms-word-to-
apple-pages/

Quick search at the top

The list of references below

The formatted reference in a grey zone (and not in white)

The formatting options

I would suppress from LyX dialog the option enabling Search-as-you-type. For 
me it seems that having it the defaut is what is expected

I'm also wondering what are the use case of a regular expression search or a 
case search. If I cite something when writing, either I remember the name of 
the author or a word in the title or maybe the name of the journal. 

But finding a bibliographical reference with a regular expression, I must 
not be geek enough ;-)

Cheers,
Charles

Re: Citations and edition-declarations

[Charles de Miramon]

jezZiFeR wrote:

 Dear list,

The question is not really for lyx.devel but more for lyx.users. Please use 
the correct list next time.

 
 I have a question regarding the declarations of editions. This is
 maybe more a BibDesk than a LyX-question, but maybe somebody could help…
 I use BibLateX with Waßenhoven-style=footnote-dw:

 If I want to cite a second edition there are surely several ways to
 show, that it is the second one, and when the first was published. I
 do know that by adding the edition-number in – I don´t know the word –
 small and printed above the lines – numbers. Maybe you could recommend
 another way, or maybe someone knows how to achieve the when using
 Bibdesk.

The edition field is where you put the information 2 if it is the second 
edition, 3 if it is the third, etc. How it is formatted in the final 
reference depends on the style. I would guess that in Wassenhoven's styles 
you can get the usual German practice, getting the edition number in 
superscript above the date of publishing.



 So this is maybe a second question:
 Is there a way to add the original title here in the original language
 in italic font?
 

Look in biblatex documentation : origtitle and all the fields that start 
with orig

Charles

Re: Citations and edition-declarations

[Charles de Miramon]

jezZiFeR wrote:

> Dear list,

The question is not really for lyx.devel but more for lyx.users. Please use 
the correct list next time.

> 
> I have a question regarding the declarations of editions. This is
> maybe more a BibDesk than a LyX-question, but maybe somebody could help…
> I use BibLateX with Waßenhoven-style=footnote-dw:

> If I want to cite a second edition there are surely several ways to
> show, that it is the second one, and when the first was published. I
> do know that by adding the edition-number in – I don´t know the word –
> small and printed above the lines – numbers. Maybe you could recommend
> another way, or maybe someone knows how to achieve the when using
> Bibdesk.

The edition field is where you put the information 2 if it is the second 
edition, 3 if it is the third, etc. How it is formatted in the final 
reference depends on the style. I would guess that in Wassenhoven's styles 
you can get the usual German practice, getting the edition number in 
superscript above the date of publishing.



> So this is maybe a second question:
> Is there a way to add the original title here in the original language
> in italic font?
> 

Look in biblatex documentation : origtitle and all the fields that start 
with orig

Charles

Maximum line width of the workarea

[Charles de Miramon]

Hello,

I have updated to 1.6.3 and the full screen mode works much better. Thanks 
for the work.

But after working a full day in full screen mode on an 17 monitor my eyes 
were strained because lines of text are much too wide if you cannot resize 
the window.

Fullscreen wordprocessors tend to draw the text between large margins (see 
for example scrivener http://www.literatureandlatte.com/screens8.html). The 
common ergonomical rule is that lines (on screen or printed) should be 
around 65 characters wide.

LyX logic today is to fill the width of the window. I would suggest to have 
a little more elaborate mechanism :
 1) fill the width of window
 2) if the window width is larger than the maximum number of characters 
(default 65) than modify the viewport of the workarea and center it in the 
window.

An even more elaborate mechanism would consider that lines of text should 
have a maximum width but floats (tables, figures) should be able to fill all 
the width of the window.

If there is consensus on this wish, I'll file an enhencement request in 
Trac.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Maximum line width of the workarea

[Charles de Miramon]

Pavel Sanda wrote:


 there is hard to get any consensus on those issues and thats why we have
 limit text width checkbox in preferences which you are probably not
 aware of.
 pavel

No Thanks, it is all I need !

Sorry for the noise.

Charles
-- 
http://www.kde-france.org

Maximum line width of the workarea

[Charles de Miramon]

Hello,

I have updated to 1.6.3 and the full screen mode works much better. Thanks 
for the work.

But after working a full day in full screen mode on an 17" monitor my eyes 
were strained because lines of text are much too wide if you cannot resize 
the window.

Fullscreen wordprocessors tend to draw the text between large margins (see 
for example scrivener http://www.literatureandlatte.com/screens8.html). The 
common ergonomical rule is that lines (on screen or printed) should be 
around 65 characters wide.

LyX logic today is to fill the width of the window. I would suggest to have 
a little more elaborate mechanism :
 1) fill the width of window
 2) if the window width is larger than the maximum number of characters 
(default 65) than modify the viewport of the workarea and center it in the 
window.

An even more elaborate mechanism would consider that lines of text should 
have a maximum width but floats (tables, figures) should be able to fill all 
the width of the window.

If there is consensus on this wish, I'll file an enhencement request in 
Trac.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Maximum line width of the workarea

[Charles de Miramon]

Pavel Sanda wrote:


> there is hard to get any consensus on those issues and thats why we have
> "limit text width" checkbox in preferences which you are probably not
> aware of.
> pavel

No Thanks, it is all I need !

Sorry for the noise.

Charles
-- 
http://www.kde-france.org

Re: Official submission of eLyXer for inclusion in LyX

[Charles de Miramon]

rgheck wrote:


 Just to be clear, here are what I regard as the showstoppers:
 Theorem-type environments aren't rendered; math support is marginal, esp
 with regard to custom macros; BibTeX isn't supported, so far as I can
 tell; cross-references omit the related text. Other things I'd want to
 investigate would include support for AMS environments, and arrays and
 the like generally; treatment of mini pages and the like. I also worry
 about the lack of extensibility, i.e., the inability to deal with custom
 styles.
 

To translate macros, custom latex styles, bibtex, cross-reference numbers, 
etc.. ELyXer would haeve to work like tex4ht in two steps :

1) parse the LyX file and translate what it can and mark (Y) what he does 
does not understand

2) Look in the pdf how latex has rendered Y  and translate it to html

ELyXer looks like it is doing step 1 correctly. Step 2 could be added later. 

People that have complex documents should use tex4ht.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Official submission of eLyXer for inclusion in LyX

[Charles de Miramon]

rgheck wrote:


> Just to be clear, here are what I regard as the showstoppers:
> Theorem-type environments aren't rendered; math support is marginal, esp
> with regard to custom macros; BibTeX isn't supported, so far as I can
> tell; cross-references omit the related text. Other things I'd want to
> investigate would include support for AMS environments, and arrays and
> the like generally; treatment of mini pages and the like. I also worry
> about the lack of extensibility, i.e., the inability to deal with custom
> styles.
> 

To translate macros, custom latex styles, bibtex, cross-reference numbers, 
etc.. ELyXer would haeve to work like tex4ht in two steps :

1) parse the LyX file and translate what it can and mark (Y) what he does 
does not understand

2) Look in the pdf how latex has rendered Y  and translate it to html

ELyXer looks like it is doing step 1 correctly. Step 2 could be added later. 

People that have complex documents should use tex4ht.

Cheers,
Charles
-- 
http://www.kde-france.org

Nice review of LyX in PCExpert Magazine

[Charles de Miramon]

Hello,

In the April 2009 of the mainstream French computer magazine PC Expert there 
is a n nice positive two pages review of LyX.

If some people are interested, I can try to post some scans.

Cheers,
Charles
-- 
http://www.kde-france.org

Nice review of LyX in PCExpert Magazine

[Charles de Miramon]

Hello,

In the April 2009 of the mainstream French computer magazine PC Expert there 
is a n nice positive two pages review of LyX.

If some people are interested, I can try to post some scans.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: LyX Outliner and Corkboard - Feature Proposal

[Charles de Miramon]

Jean-Marc Lasgouttes wrote:

 rgheck rgh...@bobjweil.com writes:
 
 Jürgen Spitzmüller wrote:
 2. implement the possibility to add comments to the outliner items.
 As Helge wrote, these will need to be stored in the document (as
 specific properties). I suppose this would be much easier to
 implement after LyX's file format switched to XML, something that is
 planned for the immediate future, but still needs thought and
 action.

   
 I'd think this was fairly simple. Right now, you could do it like this
 in the document:
\begin_layout Section
\comment Here is the comment.
Section text as before.
 
 Why not special types of note insets? We want them in the document too.
 
 JMarc

If I understand the corkboard approach, you start by writing random notes,
an outline of your ideas, etc... Then you can shuffle it and link it and
then you start to write your document.

Wouldn't it make more sense to have a structure with a file note.xml a file
outline.xml the lyx file and a RDF database like they have for Nepomuk to
tag or link between elements.

Cheers,
Charles 
-- 
http://www.kde-france.org

Re: LyX Outliner and Corkboard - Feature Proposal

[Charles de Miramon]

Jean-Marc Lasgouttes wrote:

> rgheck  writes:
> 
>> Jürgen Spitzmüller wrote:
>>> 2. implement the possibility to add comments to the outliner items.
>>> As Helge wrote, these will need to be stored in the document (as
>>> specific properties). I suppose this would be much easier to
>>> implement after LyX's file format switched to XML, something that is
>>> planned for the immediate future, but still needs thought and
>>> action.
>>>
>>>   
>> I'd think this was fairly simple. Right now, you could do it like this
>> in the document:
>>\begin_layout Section
>>\comment Here is the comment.
>>Section text as before.
> 
> Why not special types of note insets? We want them in the document too.
> 
> JMarc

If I understand the corkboard approach, you start by writing random notes,
an outline of your ideas, etc... Then you can shuffle it and link it and
then you start to write your document.

Wouldn't it make more sense to have a structure with a file note.xml a file
outline.xml the lyx file and a RDF database like they have for Nepomuk to
tag or link between elements.

Cheers,
Charles 
-- 
http://www.kde-france.org

Re: [patch] Fix UI GuiTabular

[Charles de Miramon]

Jürgen Spitzmüller wrote:


 I think we really need OK/Apply/Cancel buttons in the long term (there's
 also an old bug report somewhere).
 
+1

C.

-- 
http://www.kde-france.org

Re: [patch] Fix UI GuiTabular

[Charles de Miramon]

Jürgen Spitzmüller wrote:

 Vincent van Ravesteijn wrote:
 I'm fixing the current design of the dialog. Whether the design should
 be changed is the next question ?
 
 It should have been changed long ago. Maybe you'll find the time. The
 current design is only a burden of the past.
 

I would split the Table Gui with one Gui for formatting the table, one for
formatting the column(s), one for formatting the line(s) and one for
formatting the cell(s)

When you hover with the mouse above a table, a ribbon / wheel could appear
with the 5 options.

Cheers,
Charles

-- 
http://www.kde-france.org

Re: [patch] Fix UI GuiTabular

[Charles de Miramon]

Jürgen Spitzmüller wrote:


> I think we really need OK/Apply/Cancel buttons in the long term (there's
> also an old bug report somewhere).
> 
+1

C.

-- 
http://www.kde-france.org

Re: [patch] Fix UI GuiTabular

[Charles de Miramon]

Jürgen Spitzmüller wrote:

> Vincent van Ravesteijn wrote:
>> I'm fixing the current design of the dialog. Whether the design should
>> be changed is the next question ?
> 
> It should have been changed long ago. Maybe you'll find the time. The
> current design is only a burden of the past.
> 

I would split the Table Gui with one Gui for formatting the table, one for
formatting the column(s), one for formatting the line(s) and one for
formatting the cell(s)

When you hover with the mouse above a table, a ribbon / wheel could appear
with the 5 options.

Cheers,
Charles

-- 
http://www.kde-france.org

Re: Finding arbitrary text with given style

[Charles de Miramon]

Great stuff. I was hoping for a better search and replace in LyX since many
yeard.

I hope it could be merged in trunk for 1.6.1


Cheers,
Charles
-- 
http://www.kde-france.org

Re: Finding arbitrary text with given style

[Charles de Miramon]

Great stuff. I was hoping for a better search and replace in LyX since many
yeard.

I hope it could be merged in trunk for 1.6.1


Cheers,
Charles
-- 
http://www.kde-france.org

Re: The tex4ht changes: please test!

[Charles de Miramon]

Abdelrazak Younes wrote:

 The UserGuide doesn't work for me either. I suspect it's simply too
 complex for htlatex. Does the Tutorial work?

Here (Debian Sid, LyX SVN, tex4ht 20080701-2) it works for the tutorial.

Cheers,
Charles


-- 
http://www.kde-france.org

Re: The tex4ht changes: please test!

[Charles de Miramon]

Abdelrazak Younes wrote:
>
>> The UserGuide doesn't work for me either. I suspect it's simply too
>> complex for htlatex. Does the Tutorial work?
>>
Here (Debian Sid, LyX SVN, tex4ht 20080701-2) it works for the tutorial.

Cheers,
Charles


-- 
http://www.kde-france.org

Re: Experience using XeTeX with XeTeX?

[Charles de Miramon]

=??B?SsO8cmdlbiBTcGl0em3DvGxsZXI=?= wrote:

 are not installed.
 
 I would not talk of moving. We should provide support for XeTeX, but not
 at the price of dropping support for other LaTeX variants. There will
 always be enough reasons to not use XeTeX (as long as it misses support
 for micro typographic extensions, I will not use it, for instance).


I would rather have one stable and solid LyX Way (unicode + xetex (and in
the future luatex) + opentype) and a possibility to export pdflatex code
for special reasons (like microtypography).

Having the possibility to switch the latex engine in the middle of creating
a document is a recipe for subtle problems (encoding, fonts). LyX users
should not care and know anything about subtle differences between LaTeX
engines.

I will not mourn the death of LaTeX inputenc, font system, DVI...

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Experience using XeTeX with XeTeX?

[Charles de Miramon]

=??B?SsO8cmdlbiBTcGl0em3DvGxsZXI=?= wrote:

>> are not installed.
> 
> I would not talk of "moving". We should provide support for XeTeX, but not
> at the price of dropping support for other LaTeX variants. There will
> always be enough reasons to not use XeTeX (as long as it misses support
> for micro typographic extensions, I will not use it, for instance).


I would rather have one stable and solid LyX Way (unicode + xetex (and in
the future luatex) + opentype) and a possibility to export pdflatex code
for special reasons (like microtypography).

Having the possibility to switch the latex engine in the middle of creating
a document is a recipe for subtle problems (encoding, fonts). LyX users
should not care and know anything about subtle differences between LaTeX
engines.

I will not mourn the death of LaTeX inputenc, font system, DVI...

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Outline more persistent

[Charles de Miramon]

Pavel Sanda wrote:
 
 i tend for 3. solution but would like to hear your opinions.
 

Why not have a Multiple View Component architecture ? The Outliner would be
one view and the main window another view ; each view would have a
infrastucture to remember what is collapsed or not. It would make possible
to create views for informations that may pollute your text (notes, todo,
revision marks, footnotes, etc.).

Cheers,
Charles


http://www.kde-france.org

Re: Outline more persistent

[Charles de Miramon]

Pavel Sanda wrote:
> 
> i tend for 3. solution but would like to hear your opinions.
> 

Why not have a Multiple View Component architecture ? The Outliner would be
one view and the main window another view ; each view would have a
infrastucture to remember what is collapsed or not. It would make possible
to create views for informations that may pollute your text (notes, todo,
revision marks, footnotes, etc.).

Cheers,
Charles


http://www.kde-france.org

Re: Progress on the MS Word to LyX conversion (xml)

[Charles de Miramon]

Jürgen Spitzmüller wrote:

 Abdelrazak Younes wrote:
 That looks interesting indeed. Putting the development list in copy.
 Jürgen, José, do you know about that?
 
 I heard of it. But I'm pretty ignorant when it comes to markup languages.
 
 Jürgen

TEI is an archival format. I doubt it is suitable for LyX.

Like Pavel, I'm very dubitative of a move to an xml format. If you look the
wordprocessing xml initiatives, they have all been failures (docbook,
xml-fo / xsl-fo, xmltex). Odf succeeded more because of Microsoft's hate
then anything else.

Xml is slow to parse, the text is buried in very noisy formatting
information and is difficult to hack. In my opinion, history has proved it
is not adapted for wordprocessors.

Lyx final product is LaTeX / XeTeX code. Why not keep a format that is
parsable subset of LaTeX and can easily evolve when more and more LaTeX
features are added to LyX.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Progress on the MS Word to LyX conversion (xml)

[Charles de Miramon]

Charles de Miramon wrote:

 
 Xml is slow to parse, the text is buried in very noisy formatting
 information and is difficult to hack. In my opinion, history has proved it
 is not adapted for wordprocessors.
 
Interesting blog measuring the performance impact when MsWord switched to an
xml format.

http://www.oooninja.com/2008/07/benchmarking-microsoft-word-95-2007.html

-- 
http://www.kde-france.org

Re: Progress on the MS Word to LyX conversion (xml)

[Charles de Miramon]

Abdelrazak Younes wrote:


 Xml is slow to parse,
 That's a generalisation that is not really true, it really depends on
 your XML syntax. We are free to do what we want, so I am pretty sure the
 parsing will be as fast as nowadays. Really, do you see an increased
 difficulty when parsing document.../document instead of
 \begin_document...\end_document ?

The slowness of XML parsing has been a complaint for KWord, OpenOffice,
MsWord2007. If you cannot use a parser from the shelf (QtXml, LibXml2) but
have to tweak something, what is the point.
   
 
 Because XML is easy to transform. That is really the *main* reason. For
 example the transformation to TEI will be very, very simple, believe me.
 Not only that, but also transformations to HTML, ODF, etc.

If it was true, there would be today rocksolid ODF - Docbook, ODF - TEI,
ODF -XML-FO converters. The idea that is very easy to transform one xml
jargon to another xml jargon, is a myth.

 Heck, even a 
 transformation to LateX would be possible if one day we decide that it
 is not worth maintaining the LateX code in C++.

At some point in Koffice development, Robert Jacolin wrote a XSLT converter
between KWord first XML format and LaTeX. He left the project but nobody
continued its work because everybody hates XSLT.

XML is nice for archival, interchange, standardized formats but is not an
universal swissknife.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Progress on the MS Word to LyX conversion (xml)

[Charles de Miramon]

José Matos wrote:

 
 This idea was discussed before and it was abandoned more than 10 years
 ago. Every once in a while someone comes with that suggestion, and again
 we conclude that it does not work, the best that could be done would be
 that subject plus meta comments with annotations.
 

I'm not saing that LaTeX should be the format but something that can be
easily mapped to LaTeX. Today's LyX format is a simplified LaTeX.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Progress on the MS Word to LyX conversion (xml)

[Charles de Miramon]

Jürgen Spitzmüller wrote:

> Abdelrazak Younes wrote:
>> That looks interesting indeed. Putting the development list in copy.
>> Jürgen, José, do you know about that?
> 
> I heard of it. But I'm pretty ignorant when it comes to markup languages.
> 
> Jürgen

TEI is an archival format. I doubt it is suitable for LyX.

Like Pavel, I'm very dubitative of a move to an xml format. If you look the
wordprocessing xml initiatives, they have all been failures (docbook,
xml-fo / xsl-fo, xmltex). Odf succeeded more because of Microsoft's hate
then anything else.

Xml is slow to parse, the text is buried in very noisy formatting
information and is difficult to hack. In my opinion, history has proved it
is not adapted for wordprocessors.

Lyx final product is LaTeX / XeTeX code. Why not keep a format that is
parsable subset of LaTeX and can easily evolve when more and more LaTeX
features are added to LyX.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Progress on the MS Word to LyX conversion (xml)

[Charles de Miramon]

Charles de Miramon wrote:

>> 
> Xml is slow to parse, the text is buried in very noisy formatting
> information and is difficult to hack. In my opinion, history has proved it
> is not adapted for wordprocessors.
> 
Interesting blog measuring the performance impact when MsWord switched to an
xml format.

http://www.oooninja.com/2008/07/benchmarking-microsoft-word-95-2007.html

-- 
http://www.kde-france.org

Re: Progress on the MS Word to LyX conversion (xml)

[Charles de Miramon]

Abdelrazak Younes wrote:


>> Xml is slow to parse,
> That's a generalisation that is not really true, it really depends on
> your XML syntax. We are free to do what we want, so I am pretty sure the
> parsing will be as fast as nowadays. Really, do you see an increased
> difficulty when parsing ... instead of
> \begin_document...\end_document ?

The slowness of XML parsing has been a complaint for KWord, OpenOffice,
MsWord2007. If you cannot use a parser from the shelf (QtXml, LibXml2) but
have to tweak something, what is the point.
   
> 
> Because XML is easy to transform. That is really the *main* reason. For
> example the transformation to TEI will be very, very simple, believe me.
> Not only that, but also transformations to HTML, ODF, etc.

If it was true, there would be today rocksolid ODF <-> Docbook, ODF <-> TEI,
ODF <->XML-FO converters. The idea that is very easy to transform one xml
jargon to another xml jargon, is a myth.

> Heck, even a 
> transformation to LateX would be possible if one day we decide that it
> is not worth maintaining the LateX code in C++.

At some point in Koffice development, Robert Jacolin wrote a XSLT converter
between KWord first XML format and LaTeX. He left the project but nobody
continued its work because everybody hates XSLT.

XML is nice for archival, interchange, standardized formats but is not an
universal swissknife.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Progress on the MS Word to LyX conversion (xml)

[Charles de Miramon]

José Matos wrote:

> 
> This idea was discussed before and it was abandoned more than 10 years
> ago. Every once in a while someone comes with that suggestion, and again
> we conclude that it does not work, the best that could be done would be
> that subject plus meta comments with annotations.
> 

I'm not saing that LaTeX should be the format but something that can be
easily mapped to LaTeX. Today's LyX format is a simplified LaTeX.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Alternative to individual embedding?

[Charles de Miramon]

I like Richard's solution better. Having a zip based solution means that you
can 'unbundle' from the command line even without LyX, the base64 solution
is more complex.

I would favour a simple bundling / unbundling where everything is bundled
and everything is unbundled but add the possibility to use files on the
network (through ftp, ssh, http) using the Qt4 network stack. You could
then use a bibliography file common to your laboratory in your lyx article,
and get most of the functionalities (sharing some files and not others)
that Bo is talking about. These network files would not be bundable (is
this an English word ?). 

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Alternative to individual embedding?

[Charles de Miramon]

Bo Peng wrote:

 On the other hand, the file format in my proposal is still plain text.
 For many other operations such as search and replace, you do not have
 to unzip. I consider this as an advantage.

You have got a point. But the mix of text and base64 which is what is done
in rtf, if I'm right, messes desktop indexers like strigi

 
 Good luck if you can get those. As I have mentioned, Richard's
 proposal is not friendly to external files.
 
 My proposition would be to add URI for external files. Example :

\begin_inset LatexCommand bibtex
options cambridge
bibfiles Biblio, /home/charles/localbiblio

\end_inset

would be

\begin_inset LatexCommand bibtex
options cambridge
bibfiles ftp://[EMAIL PROTECTED]/Biblio,
file://home/charles/localbiblio

\end_inset

The bundler would parse the field and bundle only the file:// items maybe by
having a bundle URI something like :

bibfiles ftp://[EMAIL PROTECTED]/Biblio,
bundle://bibliography/localbiblio

If I understand your workflow, you want to work with a colleague on a Lyx
paper where a lot of figures are generated on your computer from an
external statistical program. With my proposition, when you (re)generate
your figures, you would run a script to copy them on a ftp ; http server
common for you and your colleague.

I guess that there exist already in KDE some code that build on top of
QNetwork a svn, git stack that could be used in LyX in the future if there
is a need to add VCS functionalities.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Alternative to individual embedding?

[Charles de Miramon]

I like Richard's solution better. Having a zip based solution means that you
can 'unbundle' from the command line even without LyX, the base64 solution
is more complex.

I would favour a simple bundling / unbundling where everything is bundled
and everything is unbundled but add the possibility to use files on the
network (through ftp, ssh, http) using the Qt4 network stack. You could
then use a bibliography file common to your laboratory in your lyx article,
and get most of the functionalities (sharing some files and not others)
that Bo is talking about. These network files would not be bundable (is
this an English word ?). 

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Alternative to individual embedding?

[Charles de Miramon]

Bo Peng wrote:

> On the other hand, the file format in my proposal is still plain text.
> For many other operations such as search and replace, you do not have
> to unzip. I consider this as an advantage.

You have got a point. But the mix of text and base64 which is what is done
in rtf, if I'm right, messes desktop indexers like strigi

> 
> Good luck if you can get those. As I have mentioned, Richard's
> proposal is not friendly to external files.
> 
 My proposition would be to add URI for external files. Example :

\begin_inset LatexCommand bibtex
options "cambridge"
bibfiles "Biblio, /home/charles/localbiblio"

\end_inset

would be

\begin_inset LatexCommand bibtex
options "cambridge"
bibfiles "ftp://[EMAIL PROTECTED]/Biblio,
file://home/charles/localbiblio"

\end_inset

The bundler would parse the field and bundle only the file:// items maybe by
having a bundle URI something like :

bibfiles "ftp://[EMAIL PROTECTED]/Biblio,
bundle://bibliography/localbiblio"

If I understand your workflow, you want to work with a colleague on a Lyx
paper where a lot of figures are generated on your computer from an
external statistical program. With my proposition, when you (re)generate
your figures, you would run a script to copy them on a ftp ; http server
common for you and your colleague.

I guess that there exist already in KDE some code that build on top of
QNetwork a svn, git stack that could be used in LyX in the future if there
is a need to add VCS functionalities.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Trying the full screen mode

[Charles de Miramon]

Helge Hafting wrote:

  
 If F11 switches to fullscreen mode, then surely F11 again
 should switch back.  The accidental user
 can then press the same key again - no guessing
 about other keys.
 


Hmm. All applictaions I know have some visual clue to get out of the
fullscreen mode (look Firefox, MsWord, Konqueror, etc.). Maybe showing a
passive popup for 5 seconds the first time with the message To return to
normal mode, type F11

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Trying the full screen mode

[Charles de Miramon]

Helge Hafting wrote:

  
> If F11 switches to fullscreen mode, then surely F11 again
> should switch back.  The accidental user
> can then press the same key again - no guessing
> about other keys.
> 


Hmm. All applictaions I know have some visual clue to get out of the
fullscreen mode (look Firefox, MsWord, Konqueror, etc.). Maybe showing a
passive popup for 5 seconds the first time with the message "To return to
normal mode, type F11"

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Trying the full screen mode

[Charles de Miramon]

Pavel Sanda wrote:

 please look at Tools-Preferences-User interface.

Yes. I have looked the options but there are no options to keep the menu, or
the status bar. 

Somebody typing F11 by mistake will end in a full screen mode qithout any
clue how to come back to normal mode

Something that was nice in the old MsWord fullscreen mode was that the
menubar was drawn above the screen (and therefore invisible) but you could
still use it with the shortcuts. for example, typing Alt-F gave the drop
down file menu. I don't know if it is possible to do it with Qt. 


Cheers,
Charles
-- 
http://www.kde-france.org

Re: Trying the full screen mode

[Charles de Miramon]

Pavel Sanda wrote:

> please look at Tools->Preferences->User interface.

Yes. I have looked the options but there are no options to keep the menu, or
the status bar. 

Somebody typing F11 by mistake will end in a full screen mode qithout any
clue how to come back to normal mode

Something that was nice in the old MsWord fullscreen mode was that the
menubar was drawn above the screen (and therefore invisible) but you could
still use it with the shortcuts. for example, typing Alt-F gave the drop
down file menu. I don't know if it is possible to do it with Qt. 


Cheers,
Charles
-- 
http://www.kde-france.org

Re: UI RFC: Outliner and Notes

[Charles de Miramon]

Abdelrazak Younes wrote:

 UI Question:
 
 In the outliner type combo, do you prefer an entry for each type of
 notes (LyX, Comment, Greyed out) or one entry like what we have now?
 
 Abdel.

I have just compiled svn. It looks very nice.
In the long run. I think it would be nice to have the non-printable notes
that are more todo kind of stuff in a special widget and not in the text,
linked through the 'Navigator'.

Several suggestions for the new outliner :
- Change the name to 'Navigator' and have the same shortcut (F5) than in
Open Office
- Open / Close the Navigator through the Visualize menu like View Source
- Is it possible to have the footnote number on the left of the tree item in
the same color that the footnote in the main editing window ?
- If the footnote is a bibliographical reference, the item in the footnotes
tree is empty
- Have a search combo box to search notes, footnotes, etc.
- When you click or have the cursor in the editing window, highlight the
item in the tree (maybe by italicizing it)
- I would suppress the identical features in the Navigate main menu
- In List of footnotes / Liste of notes etc.. suppress the outliner buttons
and slider.

A small question. Why Tommaso Cucinotta's search interface is not
integrated ? It looked very nice.

Cheers,
Charles

 
-- 
http://www.kde-france.org

Re: UI RFC: Outliner and Notes

[Charles de Miramon]

Abdelrazak Younes wrote:

> UI Question:
> 
> In the outliner type combo, do you prefer an entry for each type of
> notes (LyX, Comment, Greyed out) or one entry like what we have now?
> 
> Abdel.

I have just compiled svn. It looks very nice.
In the long run. I think it would be nice to have the non-printable notes
that are more todo kind of stuff in a special widget and not in the text,
linked through the 'Navigator'.

Several suggestions for the new outliner :
- Change the name to 'Navigator' and have the same shortcut (F5) than in
Open Office
- Open / Close the Navigator through the Visualize menu like View Source
- Is it possible to have the footnote number on the left of the tree item in
the same color that the footnote in the main editing window ?
- If the footnote is a bibliographical reference, the item in the footnotes
tree is empty
- Have a search combo box to search notes, footnotes, etc.
- When you click or have the cursor in the editing window, highlight the
item in the tree (maybe by italicizing it)
- I would suppress the identical features in the Navigate main menu
- In List of footnotes / Liste of notes etc.. suppress the outliner buttons
and slider.

A small question. Why Tommaso Cucinotta's search interface is not
integrated ? It looked very nice.

Cheers,
Charles

 
-- 
http://www.kde-france.org

Re: r20513 - in /lyx-devel/trunk/src/frontends/qt4: Dialogs.c...

[Charles de Miramon]

Abdelrazak Younes wrote:

 
 Qt designer is a good example. Open Office is another one. Typically OO
 would dock a paragraph settings dialog.
 
 

Has someone tried scrivener (I don't have a Mac) :

http://www.literatureandlatte.com/scrivener.html

The interface looks innovative with interesting Abdel'esque ideas.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: r20513 - in /lyx-devel/trunk/src/frontends/qt4: Dialogs.c...

[Charles de Miramon]

Abdelrazak Younes wrote:

> 
> Qt designer is a good example. Open Office is another one. Typically OO
> would dock a paragraph settings dialog.
> 
> 

Has someone tried scrivener (I don't have a Mac) :

http://www.literatureandlatte.com/scrivener.html

The interface looks innovative with interesting Abdel'esque ideas.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: LyX 1.5.0 is released

[Charles de Miramon]

Jean-Marc Lasgouttes wrote:

 
 Public release of LyX version 1.5.0
 ===
 
 We are pleased to announce the release of LyX 1.5.0.

Congratulations for all. It was great to see all this energy going into LyX
lately. Riding my hobby horse, I would say that the qt port brought new
platforms, new users and new developers.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: LyX 1.5.0 is released

[Charles de Miramon]

Jean-Marc Lasgouttes wrote:

> 
> Public release of LyX version 1.5.0
> ===
> 
> We are pleased to announce the release of LyX 1.5.0.

Congratulations for all. It was great to see all this energy going into LyX
lately. Riding my hobby horse, I would say that the qt port brought new
platforms, new users and new developers.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Commit Rules Post-1.5.0

[Charles de Miramon]

Martin Vermeer wrote:

 
 We already have that: charstyles, which are however pretty
 limited. But they could be extended (under a different name
 probably, style insets?)
  
  Could something like that do the trick for beamer?  (I haven't
  used beamer myself . . .)
 
 Would be a partial solution at best. We also need optarg
 insets extended to accept   as delimiters instead of
 [ ] . And then a dialog, definable from the .layout file,
  for picking the various 1- etc strings. (this feature
 would also help implementing Carlisle's enumerate
 extension more generally.)
 

If we have nested styles. For example a titlepage style, with nested title,
author, date, etc.. with some rules to specify the possible order of nested
styles and a general mechanism for optargs, we will dramatically increase
the amount of latex that can be lyxified ... The gui part is, however, not
that easy.

Cheers,
Charles

-- 
http://www.kde-france.org

Re: Commit Rules Post-1.5.0

[Charles de Miramon]

Martin Vermeer wrote:

> 
> We already have that: charstyles, which are however pretty
> limited. But they could be extended (under a different name
> probably, "style insets"?)
>  
>>  Could something like that do the trick for beamer?  (I haven't
>>  used beamer myself . . .)
> 
> Would be a partial solution at best. We also need optarg
> insets extended to accept < > as delimiters instead of
> [ ] . And then a dialog, definable from the .layout file,
>  for picking the various 1- etc strings. (this feature
> would also help implementing Carlisle's enumerate
> extension more generally.)
> 

If we have nested styles. For example a titlepage style, with nested title,
author, date, etc.. with some rules to specify the possible order of nested
styles and a general mechanism for optargs, we will dramatically increase
the amount of latex that can be lyxified ... The gui part is, however, not
that easy.

Cheers,
Charles

-- 
http://www.kde-france.org

Re: Commit Rules Post-1.5.0

[Charles de Miramon]

Martin Vermeer wrote:

 
 What feature do you think that lyx is missing badly?
 
 The beamer layout requires too much ERT and non-intuitive tweaking.
 Perhaps something can be done about it in the frame of short title /
 optional argument. My dream is to have a LyX-beamer that is compatitive
 also in usability with ppt.
 

I think that what is needed is a standard mechanism to enter in a friendly
GUI way structured information in LyX like titlepages, frames in
beamer,multiple choice questions, etc. The gui form would be stored in the
layout and when you create a new beaamer frame (title page, multiple choixe
entry) the ui form would be displayed and you could enter title, subtitle,
etc...

LyX is limited by the dropdown style list copied from wordprocesssors that
works for paragraph formatting but not for structured information.

Cheers,
Charles 
-- 
http://www.kde-france.org

Re: Commit Rules Post-1.5.0

[Charles de Miramon]

Martin Vermeer wrote:

> 
>> What feature do you think that lyx is missing badly?
> 
> The beamer layout requires too much ERT and non-intuitive tweaking.
> Perhaps something can be done about it in the frame of short title /
> optional argument. My dream is to have a LyX-beamer that is compatitive
> also in usability with ppt.
> 

I think that what is needed is a standard mechanism to enter in a friendly
GUI way structured information in LyX like titlepages, frames in
beamer,multiple choice questions, etc. The gui form would be stored in the
layout and when you create a new beaamer frame (title page, multiple choixe
entry) the ui form would be displayed and you could enter title, subtitle,
etc...

LyX is limited by the dropdown style list copied from wordprocesssors that
works for paragraph formatting but not for structured information.

Cheers,
Charles 
-- 
http://www.kde-france.org

Re: Jose's 1.6 Questions [RGH]

[Charles de Miramon]

Richard Heck wrote:

 
 Modular layouts, which are close to complete, modulo comments and such.
 Then add a local layout option similar to preamble. (So, in
 DocumentSettings you can add on-the-fly layout info.) This will make
 Bo's embedded layout idea pretty simple to implement. May start
 playing with a layout editor.
 

If you could embed a qt-designer ui file in the layout with some glue for
the local layout pane(s), there would be no need to create a layout editor.

Cheers,
Charles 
-- 
http://www.kde-france.org

Re: Jose's 1.6 Questions [RGH]

[Charles de Miramon]

Richard Heck wrote:

 
> Modular layouts, which are close to complete, modulo comments and such.
> Then add a "local layout" option similar to preamble. (So, in
> Document>Settings you can add on-the-fly layout info.) This will make
> Bo's "embedded layout" idea pretty simple to implement. May start
> playing with a layout editor.
> 

If you could embed a qt-designer ui file in the layout with some glue for
the local layout pane(s), there would be no need to create a layout editor.

Cheers,
Charles 
-- 
http://www.kde-france.org

Re: Elsart class complex frontmatter

[Charles de Miramon]

Jürgen Spitzmüller wrote:

 José Matos wrote:
 We should do this for 1.5.1, this is not a file format change in the
 sense that new files will work with lyx 1.5.0. :-)
 
 Sure.

Maybe with another name, like argument and not short title. Having a common
mechanism for supporting arguments between brackets for environments.

Charles

-- 
http://www.kde-france.org

Re: Elsart class complex frontmatter

[Charles de Miramon]

Jürgen Spitzmüller wrote:

 
 Not for 1.5.x, though.
 

At least the menu entry should not be called shorttitle

Cheers,
Charles

-- 
http://www.kde-france.org

Re: Elsart class complex frontmatter

[Charles de Miramon]

Jürgen Spitzmüller wrote:

> José Matos wrote:
>> We should do this for 1.5.1, this is not a file format change in the
>> sense that new files will work with lyx 1.5.0. :-)
> 
> Sure.

Maybe with another name, like argument and not short title. Having a common
mechanism for supporting arguments between brackets for environments.

Charles

-- 
http://www.kde-france.org

Re: Elsart class complex frontmatter

[Charles de Miramon]

Jürgen Spitzmüller wrote:

> 
> Not for 1.5.x, though.
> 

At least the menu entry should not be called shorttitle

Cheers,
Charles

-- 
http://www.kde-france.org

Re: tex2lyx

[Charles de Miramon]

Ekkehart Schlicht wrote:

 Jean-Marc:
 
 I deposited an example to
 
 http://www.semverteilung.vwl.uni-muenchen.de/temp/short.zip
 
 It contains
 
 1. short.doc: Shortened version of a winword file I obtained from the
 publisher
 
 2. short.tex: short.doc exported by OpenOfficeWriter 2.2 to Latex. As
 you can see it is rather clean. It woulkd be good however, to have a way
 for replacing things that LyX don't understand, like
 {\selectlanguage{english} or {\textasciigrave} from *within* lyx, rather
 than in an external editor.
 
 3. short.pdf: PDF file generated from the (totally unmodified) short.tex
 
 As you will see, LyX 1.5 can't open it. Lyx 1.4.4 can, but does not
 produce Latex output. (View does not work here, on the same Latex system
 where short.tex compiled without any problem! Strange.)
 
 Maybe this is a useful real world test case that may be used to tune
 tex2lyx.
 
 Needless to say, I can produce a tex file readable by lyx from short.tex
 by replacing the preamble and doing various substitutions by hand. (I
 actually did so.) But it would be even better if Lyx could deal with
 such stuff automatically.
 
 
 Cheers and thanks
 
 Ekkehart
 

Hello Ekkehart,

If you want to have better results in translating, you will have to work
from the command line and create a configuration file that map the MsWord
stylesheet to the LaTeX / LyX stylesheet and suppress useless formatting
commands.
It is explained in German here (maybe a bit outdated) :
http://www.hj-gym.dk/~hj/writer2latex/auszug_w2l.pdf 
and in English here
http://www.hj-gym.dk/~hj/writer2latex/doc/user-manual.html

Even with a custom-made configuration file, you will get a lot of 'noise' in
your latex file. I attach a sed script (w2lclean) that tries to delete some
of this 'noise'. You should customize this sed script. 

It is not perfect because, I have not found a way to suppress with sed a
latex tag and the closing brace maybe it should be done in Python with a
macro.

to go from :
\uselesstag{blabla \emph{foo} foo} - blabla \emph{foo} foo 

Cheers,
Charles
-- 
http://www.kde-france.org


w2lclean
Description: application/shellscript

Re: tex2lyx

[Charles de Miramon]

Ekkehart Schlicht wrote:

> Jean-Marc:
> 
> I deposited an example to
> 
> http://www.semverteilung.vwl.uni-muenchen.de/temp/short.zip
> 
> It contains
> 
> 1. short.doc: Shortened version of a winword file I obtained from the
> publisher
> 
> 2. short.tex: short.doc exported by OpenOfficeWriter 2.2 to Latex. As
> you can see it is rather clean. It woulkd be good however, to have a way
> for replacing things that LyX don't understand, like
> {\selectlanguage{english} or {\textasciigrave} from *within* lyx, rather
> than in an external editor.
> 
> 3. short.pdf: PDF file generated from the (totally unmodified) short.tex
> 
> As you will see, LyX 1.5 can't open it. Lyx 1.4.4 can, but does not
> produce Latex output. (View does not work here, on the same Latex system
> where short.tex compiled without any problem! Strange.)
> 
> Maybe this is a useful real world test case that may be used to tune
> tex2lyx.
> 
> Needless to say, I can produce a tex file readable by lyx from short.tex
> by replacing the preamble and doing various substitutions by hand. (I
> actually did so.) But it would be even better if Lyx could deal with
> such stuff automatically.
> 
> 
> Cheers and thanks
> 
> Ekkehart
> 

Hello Ekkehart,

If you want to have better results in translating, you will have to work
from the command line and create a configuration file that map the MsWord
stylesheet to the LaTeX / LyX stylesheet and suppress useless formatting
commands.
It is explained in German here (maybe a bit outdated) :
http://www.hj-gym.dk/~hj/writer2latex/auszug_w2l.pdf 
and in English here
http://www.hj-gym.dk/~hj/writer2latex/doc/user-manual.html

Even with a custom-made configuration file, you will get a lot of 'noise' in
your latex file. I attach a sed script (w2lclean) that tries to delete some
of this 'noise'. You should customize this sed script. 

It is not perfect because, I have not found a way to suppress with sed a
latex tag and the closing brace maybe it should be done in Python with a
macro.

to go from :
\uselesstag{blabla \emph{foo} foo} -> blabla \emph{foo} foo 

Cheers,
Charles
-- 
http://www.kde-france.org


w2lclean
Description: application/shellscript

Re: horizontal lines in tabulars

[Charles de Miramon]

Abdelrazak Younes wrote:


 That was what I was going to suggest. But then I remembered that the
 goal of 1.6 is XML and this alone will take time I guess. 

What LyX is going to gain with a XML file format ? Except being buzz
compliant.

 I am not sure 
 that switching to XML and doing minor file format changes at the same
 time is a good idea, so maybe this will have to wait for 1.7. All thing
 reconsidered, maybe Edwin's patch should go in :-)
 
 Abdel.

What about 
for 1.5.0 a patch with the file format change and a small logic to tell Lyx
to just skip the cline format, if it finds any

for 1.5.1 the gui and the latex generator

Advice from an ignorant,

Charles
-- 
http://www.kde-france.org

Re: horizontal lines in tabulars

[Charles de Miramon]

Jürgen Spitzmüller wrote:

 
 What would that mean if someone opens a file done with, say, 1.5.2 (with
 cline support) with 1.5.1 (without cline support)? Will this file be
 displayed and exported correctly? Will it be saved correctly, so that the
 file again opens without dataloss in 1.5.2?
 

What would be nice for 1.6 is to have an inset where in the fileformat, it
would save not only the LyX formatting instructions but also the generated
LaTeX snippet. Then, if your Lyx version does not have the logic to read
and modify the formatting instructions, it would just paste the LaTeX code
and the printed output would still be correct.

This kind of inset could be also a solution if LyX gets plugins.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: horizontal lines in tabulars

[Charles de Miramon]

José Matos wrote:

 
   We gain xsl to write converters to other formats

If KOffice can be point of comparison. Before switching to ODF, we had a xml
format and nobody (well actually one man) wrote any xsl converters because
it seems that everybody hates xslt.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: horizontal lines in tabulars

[Charles de Miramon]

Lars Gullik Bjønnes wrote:


 ODF is also xml based afaik.
 

Yes but the logic of formatting of an ODF file and of a LyX file (modelled
on LaTeX) is very different. There is no preamble for example in ODF.

This blog is interesting and it seems to me that LaTeX is rather similar to
Wordperfect.

http://fridrich.blogspot.com/2007/03/focus-on-logic-behind-file-format-not.html

 I belive it is a lot easier for us to more in that direction if we go
 for a simpler xml format with no strings attached first.
 

I fail to see what are the big advantages (except reusing an on-the-shelf
parser). Moving away from LaTeX logic will complexify the LyX - LaTeX
process.


Cheers,
Charles
-- 
http://www.kde-france.org

Re: horizontal lines in tabulars

[Charles de Miramon]

Abdelrazak Younes wrote:


> That was what I was going to suggest. But then I remembered that the
> goal of 1.6 is XML and this alone will take time I guess. 

What LyX is going to gain with a XML file format ? Except being buzz
compliant.

> I am not sure 
> that switching to XML and doing minor file format changes at the same
> time is a good idea, so maybe this will have to wait for 1.7. All thing
> reconsidered, maybe Edwin's patch should go in :-)
> 
> Abdel.

What about 
for 1.5.0 a patch with the file format change and a small logic to tell Lyx
to just skip the cline format, if it finds any

for 1.5.1 the gui and the latex generator

Advice from an ignorant,

Charles
-- 
http://www.kde-france.org

Re: horizontal lines in tabulars

[Charles de Miramon]

Jürgen Spitzmüller wrote:

> 
> What would that mean if someone opens a file done with, say, 1.5.2 (with
> cline support) with 1.5.1 (without cline support)? Will this file be
> displayed and exported correctly? Will it be saved correctly, so that the
> file again opens without dataloss in 1.5.2?
> 

What would be nice for 1.6 is to have an inset where in the fileformat, it
would save not only the LyX formatting instructions but also the generated
LaTeX snippet. Then, if your Lyx version does not have the logic to read
and modify the formatting instructions, it would just paste the LaTeX code
and the printed output would still be correct.

This kind of inset could be also a solution if LyX gets plugins.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: horizontal lines in tabulars

[Charles de Miramon]

José Matos wrote:

> 
>   We gain xsl to write converters to other formats

If KOffice can be point of comparison. Before switching to ODF, we had a xml
format and nobody (well actually one man) wrote any xsl converters because
it seems that everybody hates xslt.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: horizontal lines in tabulars

[Charles de Miramon]

Lars Gullik Bjønnes wrote:


> ODF is also xml based afaik.
> 

Yes but the logic of formatting of an ODF file and of a LyX file (modelled
on LaTeX) is very different. There is no preamble for example in ODF.

This blog is interesting and it seems to me that LaTeX is rather similar to
Wordperfect.

http://fridrich.blogspot.com/2007/03/focus-on-logic-behind-file-format-not.html

> I belive it is a lot easier for us to more in that direction if we go
> for a simpler xml format with no strings attached first.
> 

I fail to see what are the big advantages (except reusing an on-the-shelf
parser). Moving away from LaTeX logic will complexify the LyX -> LaTeX
process.


Cheers,
Charles
-- 
http://www.kde-france.org

Re: unicode issue with biblio?

[Charles de Miramon]

Georg Baum wrote:

 Edwin Leuven wrote:
 
 the insert citation dialog crashes here with attached bib entry
 
 hints anyone?
 
 Yes. The contents of .bib files is implicitly treated as UTF8, and your
 file is encoded in latin1. What we need to do is to convert them from the
 encoding that will be used for LaTeX export to ucs4 when we read them.
 It would be nice if you could do these changes. The best method would be
 IMHO to make idocfstream symmetric to odocfstream by adding an encoding
 argument, and open .bib files with idocfstream instead of std::ifstream.
 Then the conversion will be done automatically when you read from the
 stream. The only reason why I did not add the encoding argument to
 idocfstream yet is that it was not needed so far.
 
 
 Georg

I thought that BibTeX could not handle unicode and is not even 8-bit
compliant.

http://lists.debian.org/debian-tex-maint/2006/08/msg00146.html

Are we not opening a bag of worms if LyX accepts bib files in another
encoding than the traditional ugly one.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: unicode issue with biblio?

[Charles de Miramon]

Georg Baum wrote:

> Edwin Leuven wrote:
> 
>> the insert citation dialog crashes here with attached bib entry
>> 
>> hints anyone?
> 
> Yes. The contents of .bib files is implicitly treated as UTF8, and your
> file is encoded in latin1. What we need to do is to convert them from the
> encoding that will be used for LaTeX export to ucs4 when we read them.
> It would be nice if you could do these changes. The best method would be
> IMHO to make idocfstream symmetric to odocfstream by adding an encoding
> argument, and open .bib files with idocfstream instead of std::ifstream.
> Then the conversion will be done automatically when you read from the
> stream. The only reason why I did not add the encoding argument to
> idocfstream yet is that it was not needed so far.
> 
> 
> Georg

I thought that BibTeX could not handle unicode and is not even 8-bit
compliant.

http://lists.debian.org/debian-tex-maint/2006/08/msg00146.html

Are we not opening a bag of worms if LyX accepts bib files in another
encoding than the traditional ugly one.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: [Cvslog] r16196 - /lyx-devel/trunk/src/tex2lyx/text.C

[Charles de Miramon]

Jean-Marc Lasgouttes wrote:

 Georg == Georg Baum
 [EMAIL PROTECTED]
 writes:
 
 Georg I guess this should also go in 1.4?
 
 Yes please.
 
 JMarc

I've played a little bit with importing quotes with tex2lyx and it seems
quite broken, even round trip LyX -- LaTeX -- LyX is not perfect.

The Ducth and German citation quotes also does not work. Try importing this
file in Lyx :

%% LyX 1.4.3 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[dutch]{article}
\usepackage{bookman}
\usepackage[T1]{fontenc}
\usepackage[latin1]{inputenc}

\makeatletter
%% User specified LaTeX commands.
\newcommand{\tab}{\hspace{5mm}}

\usepackage[dutch]{babel}
\makeatother
\begin{document}
,,Rotterdam''

`Rotterdam'

\end{document}

Georg proposed a longer patch on LyX French mailing list :

/// LaTeX names for quotes
char const * const known_quotes[] = {
// single quotes
glq, grq, quotesinglbase, textquotesinglbase, textquoteleft,
guilsinglleft, guilsinglright, textflq, textfrq, flq, frq,
// double quotes
glqq, grqq, quotedblbase, textquotedblbase, textquotedblleft,
textglqq, textgrqq,
guillemotleft, guillemotright, textflqq, textfrqq, flqq, frqq,
og, fg, 0};

/// the same as known_quotes with .lyx names
char const * const known_coded_quotes[] = {
gls, grs, gls, gls, grs,
fls, frs, fls, frs, fls, frs,
gld, grd, gld, gld, grd, gld, grd,
fld, frd, fld, frd, fld, frd, fld, frd, 0};

explaining that it may cause some interferences with some languages. 

Thinking about it, I think the problem is the translation of :

\textquoteblbase Rotterdam  \textquotedblright

\textquotedblleft Rotterdam \textquotedblright

That should be in the first case 

gld Rotterdam grd

and in the second case

eld Rotterdam erd

tex2lyx should translate pair of quotes and not single quotes.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: [Cvslog] r16196 - /lyx-devel/trunk/src/tex2lyx/text.C

[Charles de Miramon]

Jean-Marc Lasgouttes wrote:


 I think most of the quotes are too difficult to get right... 

Mmm If the latex parser could extract the pair of quotes, I think it
should be possible to have a one to one translation matrix.

Cheers,
Charles 

-- 
http://www.kde-france.org

Re: [Cvslog] r16196 - /lyx-devel/trunk/src/tex2lyx/text.C

[Charles de Miramon]

Jean-Marc Lasgouttes wrote:

>> "Georg" == Georg Baum
>> <[EMAIL PROTECTED]>
>> writes:
> 
> Georg> I guess this should also go in 1.4?
> 
> Yes please.
> 
> JMarc

I've played a little bit with importing quotes with tex2lyx and it seems
quite broken, even round trip LyX --> LaTeX --> LyX is not perfect.

The Ducth and German citation quotes also does not work. Try importing this
file in Lyx :

%% LyX 1.4.3 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[dutch]{article}
\usepackage{bookman}
\usepackage[T1]{fontenc}
\usepackage[latin1]{inputenc}

\makeatletter
%% User specified LaTeX commands.
\newcommand{\tab}{\hspace{5mm}}

\usepackage[dutch]{babel}
\makeatother
\begin{document}
,,Rotterdam''

"`Rotterdam"'

\end{document}

Georg proposed a longer patch on LyX French mailing list :

/// LaTeX names for quotes
char const * const known_quotes[] = {
// single quotes
"glq", "grq", "quotesinglbase", "textquotesinglbase", "textquoteleft",
"guilsinglleft", "guilsinglright", "textflq", "textfrq", "flq", "frq",
// double quotes
"glqq", "grqq", "quotedblbase", "textquotedblbase", "textquotedblleft",
"textglqq", "textgrqq",
"guillemotleft", "guillemotright", "textflqq", "textfrqq", "flqq", "frqq",
"og", "fg", 0};

/// the same as known_quotes with .lyx names
char const * const known_coded_quotes[] = {
"gls", "grs", "gls", "gls", "grs",
"fls", "frs", "fls", "frs", "fls", "frs",
"gld", "grd", "gld", "gld", "grd", "gld", "grd",
"fld", "frd", "fld", "frd", "fld", "frd", "fld", "frd", 0};

explaining that it may cause some interferences with some languages. 

Thinking about it, I think the problem is the translation of :

\textquoteblbase Rotterdam  \textquotedblright

\textquotedblleft Rotterdam \textquotedblright

That should be in the first case 

gld Rotterdam grd

and in the second case

eld Rotterdam erd

tex2lyx should translate pair of quotes and not single quotes.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: [Cvslog] r16196 - /lyx-devel/trunk/src/tex2lyx/text.C

[Charles de Miramon]

Jean-Marc Lasgouttes wrote:


> I think most of the quotes are too difficult to get right... 

Mmm If the latex parser could extract the pair of quotes, I think it
should be possible to have a one to one translation matrix.

Cheers,
Charles 

-- 
http://www.kde-france.org

Re: Question about tex2lyx and ERT

[Charles de Miramon]

Abdelrazak Younes wrote:
 I would be interested in coding some kind of global ERT search and
 replace in LyX.
 

Why not a real searchreplace function for LyX 1.5.x, where you can find
anything in your documment LyX, LaTeX in ERT, math, citations, styles ?

Cheers,
Charles 
-- 
http://www.kde-france.org

Re: Question about tex2lyx and ERT

[Charles de Miramon]

Georg Baum wrote:


 If the integrated latex support is based on writer2latex, then I would do
 something else: Tell writer2latex to ignore visual markup, and only to
 export the document structure. This could be done with a config file, and
 I got very good results with that some time ago.

Yes, you start with the clean.xml given with writer2latex and then you take
away some conversions that are messy (footers, page numbers, hard page
breaks, language).

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Question about tex2lyx and ERT

[Charles de Miramon]

Abdelrazak Younes wrote:
> I would be interested in coding some kind of global ERT search and
> replace in LyX.
> 

Why not a real search function for LyX 1.5.x, where you can find
anything in your documment LyX, LaTeX in ERT, math, citations, styles ?

Cheers,
Charles 
-- 
http://www.kde-france.org

Re: Question about tex2lyx and ERT

[Charles de Miramon]

Georg Baum wrote:


> If the integrated latex support is based on writer2latex, then I would do
> something else: Tell writer2latex to ignore visual markup, and only to
> export the document structure. This could be done with a config file, and
> I got very good results with that some time ago.

Yes, you start with the clean.xml given with writer2latex and then you take
away some conversions that are messy (footers, page numbers, hard page
breaks, language).

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Alpha 2 - Plan for action

[Charles de Miramon]

José Matos wrote:


 I have discovered that the release procedure needs some work, make
 distcheck is not working for one. I would like to catch an fix this
 problems before entering the pre phase.
 

Maybe at some point, everybody should align on one set of building tools
(autotools, scons or cmake) and that we have a clear, regular and
documented for dummies path to build LyX across platforms and Linux
distributions.

Charles
-- 
http://www.kde-france.org

Re: Alpha 2 - Plan for action

[Charles de Miramon]

José Matos wrote:


> I have discovered that the release procedure needs some work, make
> distcheck is not working for one. I would like to catch an fix this
> problems before entering the pre phase.
> 

Maybe at some point, everybody should align on one set of building tools
(autotools, scons or cmake) and that we have a clear, regular and
documented for dummies path to build LyX across platforms and Linux
distributions.

Charles
-- 
http://www.kde-france.org

Re: KCachegrind and LyX

[Charles de Miramon]

 cmiramon == cmiramon  [EMAIL PROTECTED] writes:

 cmiramon I have compiled yesterday svn lyx and ran it through
 cmiramon cachegrind (start lyx, load tutorial, page down twice exit).

 Did you compile lyx with --disable-stdlib-debug and --disable-assertions?

 It seems to me that you did not. This really makes profiling useless
 (as stdlib-debug causes a big slowdown)


OK, I'll try it this week-end.

 If you use scons, there are debug and a devel build options, I
 believe. Cmake may have the same.


Building with scons did not work. Cmake stops very quickly and cannot find
qmake (which is in /usr/bin)


 The snapshot it not very useful as it is :)


Just a teaser. KCachegrind is a funny application with a lot of buttons
you can push.

By the way, with my knowledge of C++, the probability that a monkey builds
the Tower of Pisa from a box of Legos is certainly bigger than my chance
of discovering bottlenecks in LyX code.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: KCachegrind and LyX

[Charles de Miramon]

>> "cmiramon" == cmiramon  <[EMAIL PROTECTED]> writes:
>
> cmiramon> I have compiled yesterday svn lyx and ran it through
> cmiramon> cachegrind (start lyx, load tutorial, page down twice exit).
>
> Did you compile lyx with --disable-stdlib-debug and --disable-assertions?
>
> It seems to me that you did not. This really makes profiling useless
> (as stdlib-debug causes a big slowdown)
>

OK, I'll try it this week-end.

> If you use scons, there are debug and a devel build options, I
> believe. Cmake may have the same.
>

Building with scons did not work. Cmake stops very quickly and cannot find
qmake (which is in /usr/bin)

>
> The snapshot it not very useful as it is :)
>

Just a teaser. KCachegrind is a funny application with a lot of buttons
you can push.

By the way, with my knowledge of C++, the probability that a monkey builds
the Tower of Pisa from a box of Legos is certainly bigger than my chance
of discovering bottlenecks in LyX code.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Qt3 Discussion

[Charles de Miramon]

Georg Baum wrote:


 I tried that, and failed. Any pointer?
 

qtconfig and use the plastic theme that is the standard for KDE.

Cheers,
Charles
-- 
http://www.kde-france.org

Re: Qt3 Discussion

[Charles de Miramon]

Jean-Marc Lasgouttes wrote:
 
 1. who is going to do that? I still got no offer.
 
I will try to create a klik package

 2. when proposed more liberty about qt4, your first reaction is to
demand 4.2 only (which will probably become 4.3 only by the time
1/5 is released)
 

The 4.x series is binary compatible. We could postpone the introduction of
4.2.x later in the 1.5.x series and add some gui features (autocompletion,
printing, revamped math panels) later.  

 3. As Edwin said there is no free lunch.

But Labor omnia vincit improbus.

Charles
-- 
http://www.kde-france.org

Re: Qt3 Discussion

[Charles de Miramon]

Jean-Marc Lasgouttes wrote:

 Charles == Charles de Miramon
 [EMAIL PROTECTED] writes:
 
 Charles Jean-Marc Lasgouttes wrote:
  1. who is going to do that? I still got no offer.
 
 Charles I will try to create a klik package

Try it. Very easy to use :

http://klik.atekon.de/

I don't know if it works with Mandriva 2006

À vaincre sans périls, on triomphe sans gloire.

Charles

-- 
http://www.kde-france.org