Bo Peng a écrit :
Qt4 is now GPL on windows too and I've heard good things about PyQt. But
you are of course not forced to learn Qt if you are not willing to.
What I found out, by reading the tutorials, is that qt is a much more
ambitious project than wxWidget. With some MFC experience,
Bo Peng a écrit :
Qt4 is now GPL on windows too and I've heard good things about PyQt. But
you are of course not forced to learn Qt if you are not willing to.
What I found out, by reading the tutorials, is that qt is a much more
ambitious project than wxWidget. With some MFC experience,
Bo Peng a écrit :
You know what would be great instead of a lyx compressed file? A
portable lyx format. Quite frankly I don't see much the interest of
having the lyx text file compressed as it is alreday quite small even
for very big file.
A while ago, a few users, actually only two,
Bo Peng a écrit :
I could probably help here (I am not considering myself a qt newbie
anymore :-) ) but it would sure be better if you'd like to learn ;-)
Because of the license problem, I chose wxWidget and wxPython for my
GUI needs. Now, I still have to learn qt? ! I am wondering why,
Georg Baum a écrit :
Bo Peng wrote:
So, the easiest solution, I think, is to let the user do the packing
job. What lyx can do, is
No, please not. That will be difficult to teach to users, and it is possible
to do it automatically.
Agreed.
This could for example be done with something
Georg Baum a écrit :
Abdelrazak Younes wrote:
You know what would be great instead of a lyx compressed file? A
portable lyx format. Quite frankly I don't see much the interest of
having the lyx text file compressed as it is alreday quite small even
for very big file. IMHO, a portable lyx file
Qt4 is now GPL on windows too and I've heard good things about PyQt. But
you are of course not forced to learn Qt if you are not willing to.
What I found out, by reading the tutorials, is that qt is a much more
ambitious project than wxWidget. With some MFC experience, wxWidget is
easy to get
Bo Peng a écrit :
You know what would be great instead of a lyx compressed file? A
portable lyx format. Quite frankly I don't see much the interest of
having the lyx text file compressed as it is alreday quite small even
for very big file.
A while ago, a few users, actually only two,
Bo Peng a écrit :
I could probably help here (I am not considering myself a qt newbie
anymore :-) ) but it would sure be better if you'd like to learn ;-)
Because of the license problem, I chose wxWidget and wxPython for my
GUI needs. Now, I still have to learn qt? ! I am wondering why,
Georg Baum a écrit :
Bo Peng wrote:
So, the easiest solution, I think, is to let the user do the packing
job. What lyx can do, is
No, please not. That will be difficult to teach to users, and it is possible
to do it automatically.
Agreed.
This could for example be done with something
Georg Baum a écrit :
Abdelrazak Younes wrote:
You know what would be great instead of a lyx compressed file? A
portable lyx format. Quite frankly I don't see much the interest of
having the lyx text file compressed as it is alreday quite small even
for very big file. IMHO, a "portable lyx
> Qt4 is now GPL on windows too and I've heard good things about PyQt. But
> you are of course not forced to learn Qt if you are not willing to.
What I found out, by reading the tutorials, is that qt is a much more
ambitious project than wxWidget. With some MFC experience, wxWidget is
easy to get
Bo Peng a écrit :
That said, I don't know how compression is handled, but I think that
it should be done such that a LyX file starts with #LyX such that it
is still possible to recognize it whatever its extension or
compression status.
Current behavior:
1. When lyx opens a file, it checks its
Bo Peng a écrit :
That said, I don't know how compression is handled, but I think that
it should be done such that a LyX file starts with #LyX such that it
is still possible to recognize it whatever its extension or
compression status.
Current behavior:
1. When lyx opens a file, it checks its
Abdelrazak Younes wrote:
You know what would be great instead of a lyx compressed file? A
portable lyx format. Quite frankly I don't see much the interest of
having the lyx text file compressed as it is alreday quite small even
for very big file. IMHO, a portable lyx file that would contains
You know what would be great instead of a lyx compressed file? A
portable lyx format. Quite frankly I don't see much the interest of
having the lyx text file compressed as it is alreday quite small even
for very big file.
A while ago, a few users, actually only two, including me, reported
I could probably help here (I am not considering myself a qt newbie
anymore :-) ) but it would sure be better if you'd like to learn ;-)
Because of the license problem, I chose wxWidget and wxPython for my
GUI needs. Now, I still have to learn qt? ! I am wondering why, from
the very beginning,
On Sat, Apr 22, 2006 at 01:48:00PM +0200, Georg Baum wrote:
Abdelrazak Younes wrote:
You know what would be great instead of a lyx compressed file? A
portable lyx format. Quite frankly I don't see much the interest of
having the lyx text file compressed as it is alreday quite small even
Bo Peng wrote:
Because of the license problem, I chose wxWidget and wxPython for my
GUI needs. Now, I still have to learn qt? ! I am wondering why, from
the very beginning, qt, instead of a GPL tool was used for lyx.
qt is GPL since several years.
In the very beginning there was only xforms
On Fri, Apr 21, 2006 at 06:35:41PM -0500, Bo Peng wrote:
That said, I don't know how compression is handled, but I think that
it should be done such that a LyX file starts with #LyX such that it
is still possible to recognize it whatever its extension or
compression status.
Current
Georg Baum [EMAIL PROTECTED] writes:
Bo Peng wrote:
Because of the license problem, I chose wxWidget and wxPython for my
GUI needs. Now, I still have to learn qt? ! I am wondering why, from
the very beginning, qt, instead of a GPL tool was used for lyx.
klyx was a port of LyX 0.12 to KDE
Bo Peng wrote:
Since lyx/latex often uses external files, we need to have a clear
mind what to do exactly. I haven't thought about this clearly, but
figures etc may be all over the places, and in subdirectories.
Yes. It does not matter where exactly these files are, the different insets
know
I am concerned about being able to recognize a .lyx file, as there is
software relying on the fact a .lyx file starts with #LyX.
It has been so from day 1 and it would be a real nuisance if it changes.
The signature is the standard gz file signature. If the file is
decompressed, #LyX will
Bo is probably thinking of Qt on Windows which has only recently been GPL-ed.
But LyX on Windows is only recent too...
When I was choosing between wxWidget/wxPython and qt/pyQt,
qt was free under linux (for GPL application only?), but was not under
windows. There was a qt3 GPL/free version, but
On Sat, Apr 22, 2006 at 02:26:32PM -0500, Bo Peng wrote:
I am concerned about being able to recognize a .lyx file, as there is
software relying on the fact a .lyx file starts with #LyX.
It has been so from day 1 and it would be a real nuisance if it changes.
The signature is the standard
Enrico Forestieri [EMAIL PROTECTED] writes:
It is much like the fact that when inserting a graphic only file names
with a given extension are shown in the graphics inset. But I can name
foo.myfig an xfig file and have it correctly recognized by gnome and
kde--but not LyX!
We have our own
Bo == Bo Peng [EMAIL PROTECTED] writes:
I could probably help here (I am not considering myself a qt newbie
anymore :-) ) but it would sure be better if you'd like to learn
;-)
Bo Because of the license problem, I chose wxWidget and wxPython for
Bo my GUI needs. Now, I still have to learn
Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg Not really. The .layout files are a separate problem (because
Georg just including them is not enough). For the other files I would
Georg use a very simple rule: Don't include anything that can be
Georg found via TEXMF, only include files that
Bo Peng a écrit :
That said, I don't know how compression is handled, but I think that
it should be done such that a LyX file starts with "#LyX" such that it
is still possible to recognize it whatever its extension or
compression status.
Current behavior:
1. When lyx opens a file, it checks
Bo Peng a écrit :
That said, I don't know how compression is handled, but I think that
it should be done such that a LyX file starts with "#LyX" such that it
is still possible to recognize it whatever its extension or
compression status.
Current behavior:
1. When lyx opens a file, it checks
Abdelrazak Younes wrote:
> You know what would be great instead of a lyx compressed file? A
> portable lyx format. Quite frankly I don't see much the interest of
> having the lyx text file compressed as it is alreday quite small even
> for very big file. IMHO, a "portable lyx file" that would
> You know what would be great instead of a lyx compressed file? A
> portable lyx format. Quite frankly I don't see much the interest of
> having the lyx text file compressed as it is alreday quite small even
> for very big file.
A while ago, a few users, actually only two, including me, reported
> I could probably help here (I am not considering myself a qt newbie
> anymore :-) ) but it would sure be better if you'd like to learn ;-)
Because of the license problem, I chose wxWidget and wxPython for my
GUI needs. Now, I still have to learn qt? ! I am wondering why, from
the very
On Sat, Apr 22, 2006 at 01:48:00PM +0200, Georg Baum wrote:
> Abdelrazak Younes wrote:
>
> > You know what would be great instead of a lyx compressed file? A
> > portable lyx format. Quite frankly I don't see much the interest of
> > having the lyx text file compressed as it is alreday quite
Bo Peng wrote:
> Because of the license problem, I chose wxWidget and wxPython for my
> GUI needs. Now, I still have to learn qt? ! I am wondering why, from
> the very beginning, qt, instead of a GPL tool was used for lyx.
qt is GPL since several years.
In the very beginning there was only
On Fri, Apr 21, 2006 at 06:35:41PM -0500, Bo Peng wrote:
> > That said, I don't know how compression is handled, but I think that
> > it should be done such that a LyX file starts with "#LyX" such that it
> > is still possible to recognize it whatever its extension or
> > compression status.
>
>
Georg Baum <[EMAIL PROTECTED]> writes:
> Bo Peng wrote:
> > Because of the license problem, I chose wxWidget and wxPython for my
> > GUI needs. Now, I still have to learn qt? ! I am wondering why, from
> > the very beginning, qt, instead of a GPL tool was used for lyx.
klyx was a port of LyX
Bo Peng wrote:
> Since lyx/latex often uses external files, we need to have a clear
> mind what to do exactly. I haven't thought about this clearly, but
> figures etc may be all over the places, and in subdirectories.
Yes. It does not matter where exactly these files are, the different insets
> I am concerned about being able to recognize a .lyx file, as there is
> software relying on the fact a .lyx file starts with "#LyX".
> It has been so from day 1 and it would be a real nuisance if it changes.
The signature is the standard gz file signature. If the file is
decompressed, #LyX will
> Bo is probably thinking of Qt on Windows which has only recently been GPL-ed.
> But LyX on Windows is only recent too...
When I was choosing between wxWidget/wxPython and qt/pyQt,
qt was free under linux (for GPL application only?), but was not under
windows. There was a qt3 GPL/free version,
On Sat, Apr 22, 2006 at 02:26:32PM -0500, Bo Peng wrote:
> > I am concerned about being able to recognize a .lyx file, as there is
> > software relying on the fact a .lyx file starts with "#LyX".
> > It has been so from day 1 and it would be a real nuisance if it changes.
>
> The signature is
Enrico Forestieri <[EMAIL PROTECTED]> writes:
> It is much like the fact that when inserting a graphic only file names
> with a given extension are shown in the graphics inset. But I can name
> foo.myfig an xfig file and have it correctly recognized by gnome and
> kde--but not LyX!
We have our
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
>> I could probably help here (I am not considering myself a qt newbie
>> anymore :-) ) but it would sure be better if you'd like to learn
>> ;-)
Bo> Because of the license problem, I chose wxWidget and wxPython for
Bo> my GUI needs. Now, I still
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Not really. The .layout files are a separate problem (because
Georg> just including them is not enough). For the other files I would
Georg> use a very simple rule: Don't include anything that can be
Georg> found via TEXMF, only
Dear all,
Attached patch adds File-compressed menu item that
1. shows the compression status of an opened file
2. can be turned on/off
3. file will be saved compressed/decompressed accordingly.
What is missing:
A .lyx (compressed) format in the Save As dialog? Does not sound necessary.
On Fri, Apr 21, 2006 at 12:23:09PM -0500, Bo Peng wrote:
Should we always save compressed to file.lyx.gz, regardless of this flag?
Given that there are stupid OSes out there that rely on file
extension, I think this is not a good idea.
That said, I don't know how compression is handled, but I
That said, I don't know how compression is handled, but I think that
it should be done such that a LyX file starts with #LyX such that it
is still possible to recognize it whatever its extension or
compression status.
Current behavior:
1. When lyx opens a file, it checks its signature. If
Dear all,
Attached patch adds File->compressed menu item that
1. shows the compression status of an opened file
2. can be turned on/off
3. file will be saved compressed/decompressed accordingly.
What is missing:
A ".lyx (compressed)" format in the Save As dialog? Does not sound necessary.
On Fri, Apr 21, 2006 at 12:23:09PM -0500, Bo Peng wrote:
> Should we always save compressed to file.lyx.gz, regardless of this flag?
Given that there are stupid OSes out there that rely on file
extension, I think this is not a good idea.
That said, I don't know how compression is handled, but I
> That said, I don't know how compression is handled, but I think that
> it should be done such that a LyX file starts with "#LyX" such that it
> is still possible to recognize it whatever its extension or
> compression status.
Current behavior:
1. When lyx opens a file, it checks its signature.
50 matches
Mail list logo
