On Fri, May 23, 2014 at 6:01 PM, Richard Heck wrote:
> On 05/23/2014 05:49 PM, Scott Kostyshak wrote:
>>>
>>> Which it should as a result of
>>> resetting the
>>> cursor since e.g. the TOC needs updating to reflect the new position.
>>> Indeed, not all dialogs
>>> need updating, but we don't have
On 05/23/2014 05:49 PM, Scott Kostyshak wrote:
Which it should as a result of
resetting the
cursor since e.g. the TOC needs updating to reflect the new position.
Indeed, not all dialogs
need updating, but we don't have such fine-grained information.
Is there an example of a dialog that needs to
On Fri, May 23, 2014 at 5:24 PM, Richard Heck wrote:
>> Inside of ViewSourceWidget::updateView is it possible to tell whether
>> it was called because of a cursor movement or because of an
>> insertion/edit?
>
>
> I don't think so. You'd need to get this information during the dispatch, I
> think
On 05/23/2014 05:11 PM, Scott Kostyshak wrote:
When "Automatic update" is checked, the source view updates whenever I
move the cursor. I think it would be nice if this did not happen when
moving the cursor within the same paragraph (when "Current paragraph"
is selected), unless we plan on trackin
When "Automatic update" is checked, the source view updates whenever I
move the cursor. I think it would be nice if this did not happen when
moving the cursor within the same paragraph (when "Current paragraph"
is selected), unless we plan on tracking where in a paragraph the user
is and scroll acc
On Sun, May 5, 2013 at 10:11 AM, Tommaso Cucinotta wrote:
> I copied the same behaviour on Advanced F&R in e3677975 and bd9e8fec.
>
> Now it makes a lt more sense to put the pane on the bottom.
If Advanced Find & Replace is docked on the left (you have to have
Outline hidden for this), and th
;
> - Log -
>
> commit 49c2450f3f6cb67a36f8fa987ad287a8bff11d79
> Author: Pavel Sanda
> Date: Sat May 4 23:05:51 2013 -0700
>
> Add layout intelligence to View Source pane (bug #8653).
>
> View Source pane layout now automatically switches between hori
Kornel Benko wrote:
> > a ai, deep in qt, which version?
> > can you try whether you get the crash even in before this commit.
>
> Same crash. Sorry for the noise.
to mi spadl kamen ze srdce ;) p
Am Sonntag, 5. Mai 2013 um 03:30:01, schrieb Pavel Sanda
> Kornel Benko wrote:
> > Sure:
> > Program received signal SIGSEGV, Segmentation fault.
> >
> > 0x77067fc5 in QDockAreaLayoutInfo::indexOf (this=0x2278ef0,
> > widget=0x1fd0230)
Am Sonntag, 5. Mai 2013 um 03:28:08, schrieb Pavel Sanda
> Kornel Benko wrote:
> > Am Sonntag, 5. Mai 2013 um 03:07:03, schrieb Pavel Sanda
> > > Kornel Benko wrote:
> > > > To reproduce:
> > > >
> > > > 1) add the source view
> > > > 2) move the source view to the right
> > > > 3) add advanced
Kornel Benko wrote:
> Sure:
> Program received signal SIGSEGV, Segmentation fault.
>
> 0x77067fc5 in QDockAreaLayoutInfo::indexOf (this=0x2278ef0,
> widget=0x1fd0230)
> at widgets/qdockarealayout.cpp:1474
Kornel Benko wrote:
> Am Sonntag, 5. Mai 2013 um 03:07:03, schrieb Pavel Sanda
> > Kornel Benko wrote:
> > > To reproduce:
> > >
> > > 1) add the source view
> > > 2) move the source view to the right
> > > 3) add advanced search, now, on bottom! you get a panel to switch between
> > > both
> >
Am Sonntag, 5. Mai 2013 um 03:07:03, schrieb Pavel Sanda
> Kornel Benko wrote:
> > To reproduce:
> >
> > 1) add the source view
> > 2) move the source view to the right
> > 3) add advanced search, now, on bottom! you get a panel to switch between
> > both
> > 4) move the source view to bottom
>
Am Sonntag, 5. Mai 2013 um 03:07:03, schrieb Pavel Sanda
> Kornel Benko wrote:
> > To reproduce:
> >
> > 1) add the source view
> > 2) move the source view to the right
> > 3) add advanced search, now, on bottom! you get a panel to switch between
> > both
> > 4) move the source view to bottom
>
Kornel Benko wrote:
> To reproduce:
>
> 1) add the source view
> 2) move the source view to the right
> 3) add advanced search, now, on bottom! you get a panel to switch between both
> 4) move the source view to bottom
> 5) move adv search to bottom
> 6) switch to see adv search
> 7) move back to
4 23:05:51 2013 -0700
>
> Add layout intelligence to View Source pane (bug #8653).
>
> View Source pane layout now automatically switches between horizontal
> and vertical design when docked in vertical or horizontal way.
>
> Original idea and patch from Edwin
2012/6/9 Richard Heck :
> Looks fine to me. Probably it'd be better not to hardcode this, but to do
> something with formats, but that's a larger project.
OK, I'll commit with a FIXME.
Jürgen
> Richard
>
On 06/08/2012 03:50 PM, Jürgen Spitzmüller wrote:
Richard, I need the attached patch in order to get the correct flavor
for the source preview (I detected the wrong flavor since polyglossia
was not shown in XeTeX preview).
Does this make sense?
Looks fine to me. Probably it'd be better not to h
Richard, I need the attached patch in order to get the correct flavor
for the source preview (I detected the wrong flavor since polyglossia
was not shown in XeTeX preview).
Does this make sense?
Jürgen
b.diff
Description: Binary data
Among the formats listed in the drop-down box of the View Source window
(although only Default and LyXHTML work), LyX itself is missing i.e. LyX
in the form of
\begin_layout Standard
...
\end_layout
etc.
At present I can look at a LyX file in a text editor to examine the
format, but surely
On 09/12/2011 3:30 PM, Richard Heck wrote:
The attached patches fix the mentioned problem with View>Source.
Comments welcome.
Richard
Looks good to me.
Regards,
Julien
The attached patches fix the mentioned problem with View>Source.
Comments welcome.
Richard
>From 1ab166f1edd34db689c250e6d6cf58c310d2368c Mon Sep 17 00:00:00 2001
From: Richard Heck
Date: Fri, 9 Dec 2011 14:58:11 -0500
Subject: [PATCH 1/2] Change the backends() routine so it only gi
Both in branch and trunk right now, if I choose "LyXHTML", say, as the
format for viewing the source, it resets to "Default" as soon as I move
the cursor. Do others see this? What's the right approach to fixing it?
Richard
On 10/29/2011 03:57 PM, Vincent van Ravesteijn wrote:
> Op 29-10-2011 21:54, Richard Heck schreef:
>> On 10/29/2011 03:48 PM, Vincent van Ravesteijn wrote:
>>> Op 29-10-2011 21:11, Richard Heck schreef:
I'm seeing PNG and EPS as output format options in the source view
window. That seems
Op 29-10-2011 21:54, Richard Heck schreef:
On 10/29/2011 03:48 PM, Vincent van Ravesteijn wrote:
Op 29-10-2011 21:11, Richard Heck schreef:
I'm seeing PNG and EPS as output format options in the source view
window. That seems wrong. Would it be better here just to list the
possible backends? i.
On 10/29/2011 03:48 PM, Vincent van Ravesteijn wrote:
> Op 29-10-2011 21:11, Richard Heck schreef:
>> I'm seeing PNG and EPS as output format options in the source view
>> window. That seems wrong. Would it be better here just to list the
>> possible backends? i.e., the formats LyX can output direc
Op 29-10-2011 21:11, Richard Heck schreef:
I'm seeing PNG and EPS as output format options in the source view
window. That seems wrong. Would it be better here just to list the
possible backends? i.e., the formats LyX can output directly?
Richard
I don't see PNG and EPS.
By the way, the whol
I'm seeing PNG and EPS as output format options in the source view
window. That seems wrong. Would it be better here just to list the
possible backends? i.e., the formats LyX can output directly?
Richard
Pavel Sanda wrote:
> what about putting update button next to automatic update?
> we spend quite some time to make this dialog resizable to
> as small vertizal size as possible.
Personally, I find horizontal space much more valuable. The dialog still is
pretty narrow (vertically) with the new wid
Jürgen Spitzmüller wrote:
> Opinions?
what about putting update button next to automatic update?
we spend quite some time to make this dialog resizable to
as small vertizal size as possible.
pavel
Jürgen Spitzmüller wrote:
> I come back to this. Attached is a reworked version of the view source
> part. I have added a cache for the default flavor, since it is overkill to
> recheck for the flavor on each key stroke.
And here comes a further addition: this adds a combo with the
On 12/04/2010 11:03 AM, Jürgen Spitzmüller wrote:
Richard Heck wrote:
My only question is one I think JMarc asked earlier, namely, whether we
want to provide some
mechanism for indicating flavor in some config file, rather than trying
to guess it.
We do not guess it. I introduced a converter fl
Richard Heck wrote:
> My only question is one I think JMarc asked earlier, namely, whether we
> want to provide some
> mechanism for indicating flavor in some config file, rather than trying
> to guess it.
We do not guess it. I introduced a converter flag that defines the (latex)
flavor, and we
since this is a step forward anyway
and removes some bad hardcoding.
I come back to this. Attached is a reworked version of the view source part. I
have added a cache for the default flavor, since it is overkill to recheck for
the flavor on each key stroke.
Typing with full source on the UG is
s is a step forward anyway
> and removes some bad hardcoding.
I come back to this. Attached is a reworked version of the view source part. I
have added a cache for the default flavor, since it is overkill to recheck for
the flavor on each key stroke.
Typing with full source on the UG is
Le 30/11/2010 10:50, Jürgen Spitzmüller a écrit :
Jürgen Spitzmüller wrote:
A patch along this line is attached. We still have to hardcode xhtml,
since there's no dedicated converter where we could derive a xhtml flag
from.
I committed the backend=flavor part, since this is a step forward any
Jürgen Spitzmüller wrote:
> A patch along this line is attached. We still have to hardcode xhtml,
> since there's no dedicated converter where we could derive a xhtml flag
> from.
I committed the backend=flavor part, since this is a step forward anyway and
removes some bad hardcoding.
Jürgen
Jean-Marc Lasgouttes wrote:
> Second try, now that I read the code: change the converter flag "latex" to
> take the form "latex=xetex" or whatever to indicate the latex flavor that
> we want. "latex" will be equivalent to "latex=latex".
>
> With this, the information does not need to be hardcoded
> this is interesting idea even for other backends like docbook
>
> pavel
>
AFAIK this already works for docbook.
Vincent
Le 24 nov. 2010 à 22:01, Jürgen Spitzmüller a écrit :
>> I do not understand why we need to do that since latex export requires
>> this information anyway. We just have to look at the first intermediate
>> step of the lyx->...->output converter chain.
>
> I cannot follow you.
Second try, now that
Jean-Marc Lasgouttes wrote:
> I do not understand why we need to do that since latex export requires
> this information anyway. We just have to look at the first intermediate
> step of the lyx->...->output converter chain.
I cannot follow you.
Jürgen
Le 24 nov. 2010 à 17:04, Jürgen Spitzmüller a écrit :
> Actually, I was just working on a patch that would take the default output
> format instead of just LaTeX or XeTeX for the source view. It would roughly
> look as follows (without XHTML and DocBook so far, but the direction should
> be clea
On 11/24/2010 11:04 AM, Jürgen Spitzmüller wrote:
Pavel Sanda wrote:
this is interesting idea even for other backends like docbook
Actually, I was just working on a patch that would take the default output
format instead of just LaTeX or XeTeX for the source view. It would roughly
look as foll
Pavel Sanda wrote:
> this is interesting idea even for other backends like docbook
Actually, I was just working on a patch that would take the default output
format instead of just LaTeX or XeTeX for the source view. It would roughly
look as follows (without XHTML and DocBook so far, but the di
Richard Heck wrote:
>
> How hard would it be to have View>Source output, say, HTML, if that is the
> default view format for the document?
this is interesting idea even for other backends like docbook
pavel
How hard would it be to have View>Source output, say, HTML, if that is
the default view format for the document?
Richard
On Thu, May 13, 2010 at 11:14 PM, Jacob Barandes
wrote:
> I'm a long-time LyX user (and huge fan), and I often work with very large
> files with lots of mathematical expressions. It would be hugely useful if
> LyX had a search-and-replace feature that looked not just through text, but
This is pro
rough mathematical expressions. (Or, at the
very least, if the "View Source" feature had its own internal
search-and-replace.) I can't tell you how many times I've realized
that I've needed to change a symbol or subscript in a thousand places,
and had to turn to an external text edi
f the "View
Source" feature had its own internal search-and-replace.) I can't tell you
how many times I've realized that I've needed to change a symbol or
subscript in a thousand places, and had to turn to an external text editor
to do it; the problem with using an external
On Sun, Jan 11, 2009 at 09:07:54AM +0100, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > > Enrico Forestieri wrote:
> > > > Please try the attached patch. It works for me even with Qt 4.2.
> > > > The Source View window always opens at its minimum height.
> > >
> > > yes, that works here
Enrico Forestieri wrote:
> > Enrico Forestieri wrote:
> > > Please try the attached patch. It works for me even with Qt 4.2.
> > > The Source View window always opens at its minimum height.
> >
> > yes, that works here.
>
> Jürgen?
go ahead.
Jürgen
On Sat, Jan 10, 2009 at 07:38:56PM +0100, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > Please try the attached patch. It works for me even with Qt 4.2.
> > The Source View window always opens at its minimum height.
>
> yes, that works here.
Jürgen?
--
Enrico
Enrico Forestieri wrote:
> Please try the attached patch. It works for me even with Qt 4.2.
> The Source View window always opens at its minimum height.
yes, that works here.
pavel
On Sat, Jan 10, 2009 at 06:31:42PM +0100, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > With Qt 4.4 I am still able to reduce the height such that only about
> > four lines of source are shown. With Qt 4.2 the height cannot be reduced
> > below about a dozen lines, but this happens with or wit
On Sat, Jan 10, 2009 at 06:15:56PM +0100, Pavel Sanda wrote:
> Jürgen Spitzmüller wrote:
> > Enrico Forestieri wrote:
> > > Using Qt 4.2, the View Source window is split such that only about 1/3
> > > of the full width is used for displaying the source (see the attach
Enrico Forestieri wrote:
> With Qt 4.4 I am still able to reduce the height such that only about
> four lines of source are shown. With Qt 4.2 the height cannot be reduced
> below about a dozen lines, but this happens with or without my patch.
which exactly version of qt? the recipy in the other m
Pavel Sanda wrote:
> Pavel Sanda wrote:
> > didn't fix the
>
> initialization
>
> > outliner/source w. bug and some code didn't get initialized after
> > launch. it also means that removing some code inside
> > ViewSourceWidget::ViewSourceWidget()
>
> i not sure now ViewSourceWidget::ViewS
Pavel Sanda wrote:
> didn't fix the
initialization
> outliner/source w. bug and some code didn't get initialized after
> launch. it also means that removing some code inside
> ViewSourceWidget::ViewSourceWidget()
i not sure now ViewSourceWidget::ViewSourceWidget() was the routine skipped.
Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > Using Qt 4.2, the View Source window is split such that only about 1/3
> > of the full width is used for displaying the source (see the attached
:( its nightmare to get this dialog right.
> > without-patch.png). The at
On Sat, Jan 10, 2009 at 05:19:45PM +0100, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > Using Qt 4.2, the View Source window is split such that only about 1/3
> > of the full width is used for displaying the source (see the attached
> > without-patch.png). The at
Enrico Forestieri wrote:
> Using Qt 4.2, the View Source window is split such that only about 1/3
> of the full width is used for displaying the source (see the attached
> without-patch.png). The attached patch corrects this (with-patch.png).
> I verified that later versions of Qt are
Using Qt 4.2, the View Source window is split such that only about 1/3
of the full width is used for displaying the source (see the attached
without-patch.png). The attached patch corrects this (with-patch.png).
I verified that later versions of Qt are not affected at all (with or
without the
Abdelrazak Younes wrote:
Dov Feldstern wrote:
Hi!
Starting quite recently (within the last two weeks?) the view source
and outliner widgets are open when LyX starts;
Only the first time. Afterwards, if session handling is enabled, LyX
will memorize the last window state, including
Dov Feldstern wrote:
Hi!
Starting quite recently (within the last two weeks?) the view source
and outliner widgets are open when LyX starts;
Only the first time. Afterwards, if session handling is enabled, LyX
will memorize the last window state, including toolbars and dock widgets
Hi!
Starting quite recently (within the last two weeks?) the view source and
outliner widgets are open when LyX starts; this didn't used to be the case. I
don't see any preference controlling this. can the old behavior be restored?
Thanks!
Dov
Leuven, E. wrote:
an update/signal got deleted by mistake recently?
Works fine here.
Abdel.
an update/signal got deleted by mistake recently?
Bennett Helm wrote:
The bug is that clicking "Update" [in the View Source window] does
nothing [when Automatic Update is off].
Well, that definitely is a bug, yes.
rh
Uwe Stöhr wrote:
As the email title says.
Yes, many dialogs are still not operational. In this case the problem is
that updateView() is never called...
Abdel.
As the email title says.
On Monday 02 July 2007 12:02:32 Abdelrazak Younes wrote:
>
> OK then.
+1
> Abdel.
--
José Abílio
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
I think it would be less confusing to have one test per controller and
so integrate the kernel().isBufferReadonly() call to
canApplyToReadOnly().
I don't think so. These two conditions might be used independent from each
other.
OK then.
Ab
Abdelrazak Younes wrote:
> I think it would be less confusing to have one test per controller and
> so integrate the kernel().isBufferReadonly() call to
> canApplyToReadOnly().
I don't think so. These two conditions might be used independent from each
other.
Jürgen
Jürgen Spitzmüller wrote:
http://bugzilla.lyx.org/show_bug.cgi?id=3909
http://bugzilla.lyx.org/show_bug.cgi?id=3943
Printing and view-source of read-only files (such as the documentation of an
installed LyX) is disallowed, since we block the passing of params and
viewing restrictively for
http://bugzilla.lyx.org/show_bug.cgi?id=3909
http://bugzilla.lyx.org/show_bug.cgi?id=3943
Printing and view-source of read-only files (such as the documentation of an
installed LyX) is disallowed, since we block the passing of params and
viewing restrictively for read-only buffers (if kernel
On Sunday 27 May 2007 14:59:15 Jürgen Spitzmüller wrote:
> OK to apply?
OK.
> Jürgen
--
José Abílio
This simple patch seems to be doing it -- tested by Bennett.
There's still an issue with the layout of the widgets, but that can be
addressed later IMO.
OK to apply?
Jürgen
Index: src/frontends/qt4/Dialogs.cpp
===
--- src/frontends/
Am Sonntag, 25. März 2007 17:13 schrieb Michael Gerz:
> Hello,
>
> Hartmut Haase pointed out that "View => View Source" is quite confusing.
> Most people will consider their LyX text as the source, not the LaTeX
> output.
>
> I suggest renaming the menu item
On Sunday 25 March 2007 9:36:56 pm Jean-Marc Lasgouttes wrote:
> Is docbook source working now?
It has been for some time. :-)
> JMarc
--
José Abílio
> "Jürgen" == Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
Jürgen> Jean-Marc Lasgouttes wrote:
>> Is docbook source working now?
Jürgen> At least I can see something that looks like XML with the
Jürgen> docbook example.
So we really need to support it :)
JMarc
Jean-Marc Lasgouttes wrote:
> Is docbook source working now?
At least I can see something that looks like XML with the docbook example.
Jürgen
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Jürgen Spitzmüller wrote:
>> Michael Gerz wrote:
>>> I suggest renaming the menu item and command to "LaTeX Source".
>>> OK?
>> I think that's not correct if you are working with docbook.
Abdelrazak> Backend Source?
Am Sonntag, 25. März 2007 17:23 schrieb Abdelrazak Younes:
> Jürgen Spitzmüller wrote:
> > Michael Gerz wrote:
> >> I suggest renaming the menu item and command to "LaTeX Source". OK?
> >
> > I think that's not correct if you are working with docbook.
>
> Backend Source?
Not better IMHO.
> I gu
Jürgen Spitzmüller wrote:
Michael Gerz wrote:
I suggest renaming the menu item and command to "LaTeX Source". OK?
I think that's not correct if you are working with docbook.
Backend Source?
I guess we could also modify the menu item depending on the document engine.
Abdel.
Michael Gerz wrote:
> I suggest renaming the menu item and command to "LaTeX Source". OK?
I think that's not correct if you are working with docbook.
Jürgen
Hello,
Hartmut Haase pointed out that "View => View Source" is quite confusing.
Most people will consider their LyX text as the source, not the LaTeX
output.
I suggest renaming the menu item and command to "LaTeX Source". OK?
Michael
Dear all,
The patch has been committed. The function names are writeXXXSource
for the ostream version and makeXXXFile for the file version, where
XXX is LaTeX, LinuxDoc and DocBook. I did not touch the Ascii file
since writeAsciiSource does not sound right. 'write' seems to be
better than 'gener
> Bo Peng <[EMAIL PROTECTED]> writes:
> > This is what makeLatexFile is doing Do you want to change the
> > name of those functions as well? Any suggestion?
>
> generateLatex, generateAscii, generateDocbook...
If you look at buffer.h, we also have writeFileAscii(filename...),
writeFileAscii(
On 8/3/06, Angus Leeming <[EMAIL PROTECTED]> wrote:
Bo Peng <[EMAIL PROTECTED]> writes:
> This is what makeLatexFile is doing Do you want to change the
> name of those functions as well? Any suggestion?
generateLatex, generateAscii, generateDocbook...
If you look at buffer.h, we also have
Bo Peng <[EMAIL PROTECTED]> writes:
> This is what makeLatexFile is doing Do you want to change the
> name of those functions as well? Any suggestion?
generateLatex, generateAscii, generateDocbook...
Angus
You change the signatures of some functions (makeXXXFile), and by
doing this the name of the function is now "meaningless".
makeXxxxFile(ostream & os, ...)
is not making a file anymore, is is just outputting to a stream. IMO
the names of these functions should change as well.
This is what make
"Bo Peng" <[EMAIL PROTECTED]> writes:
| Dear list,
|
| Attached patch adds to the view-source dialog (qt3/4):
|
| 1. 'automatic update' check box. If unchecked, stop automatic updating
| of the view source dialog. This is useful for slow machines, and when
| ful
Dear list,
Attached patch adds to the view-source dialog (qt3/4):
1. 'automatic update' check box. If unchecked, stop automatic updating
of the view source dialog. This is useful for slow machines, and when
full source is displayed.
2. update button: force update if 'auto upda
With this checkbox, user can switch between viewing the whole source
code, and part of it (current behavior). This is useful to view the
front matters.
Since automatic update of the whole source code may become too much a
burden, I propose an additional 'auto update' checkbox which will be
turned
On 4/15/06, Georg Baum <[EMAIL PROTECTED]> wrote:
> Am Samstag, 15. April 2006 19:23 schrieb Bo Peng:
> > This dialog can view other source type like linuxdoc and docbook, so
> > it is better termed as 'view-source'. There is currently one type of
> > syntax h
Am Samstag, 15. April 2006 19:23 schrieb Bo Peng:
> This dialog can view other source type like linuxdoc and docbook, so
> it is better termed as 'view-source'. There is currently one type of
> syntax highlighting though.
BTW since you have that it would be nice to use it in
> looks ok here
>
> general comment: i think "view latex code" or something like that would
> be more appropriate
>
This dialog can view other source type like linuxdoc and docbook, so
it is better termed as 'view-source'. There is currently one type of
syntax highlighting though.
Bo
Abdelrazak Younes wrote:
But the fonts are too big under window, is it the same under X11?
looks ok here
general comment: i think "view latex code" or something like that would
be more appropriate
Bo Peng a écrit :
If your Qt4 version works i.e. compile and doesn't make lyx crash,
please commit it yourself and we work from there.
Done.
Very good. I like the feature a lot!
But the fonts are too big under window, is it the same under X11?
The ugliness of qt4 comes from the fact (I gues
> If your Qt4 version works i.e. compile and doesn't make lyx crash,
> please commit it yourself and we work from there.
Done.
The ugliness of qt4 comes from the fact (I guess) that my kde3 uses
qt3 and qt4 can not get a working style file from the system. I guess
I can get such things from onlin
1 - 100 of 111 matches
Mail list logo
