On Tue, Oct 7, 2014 at 4:58 AM, Stephan Witt st.w...@gmx.net wrote:
Am 06.10.2014 um 22:05 schrieb Marcelo Galvão Póvoa
marspeoples...@gmail.com:
On Sun, Oct 5, 2014 at 4:29 PM, Stephan Witt st.w...@gmx.net wrote:
Am 02.10.2014 um 13:14 schrieb Stephan Witt st.w...@gmx.net:
Am 18.07.2014
On Tue, Oct 7, 2014 at 4:58 AM, Stephan Witt <st.w...@gmx.net> wrote:
> Am 06.10.2014 um 22:05 schrieb Marcelo Galvão Póvoa
> <marspeoples...@gmail.com>:
>
>> On Sun, Oct 5, 2014 at 4:29 PM, Stephan Witt <st.w...@gmx.net> wrote:
>>> Am 02.10.2014 um 1
Galvão Póvoa a écrit :
I'm not sure how to easily get a pointer to the window containing the
current workarea in every part of the code I need to use pixel_ratio.
I could use the globally available qApp-activeWindow() macro, but
what if the active window is a dialog window instead
10:26 schrieb Jean-Marc Lasgouttes <lasgout...@lyx.org>:
>>>
>>>> Le 17/07/2014 23:24, Marcelo Galvão Póvoa a écrit :
>>>>> I'm not sure how to easily get a pointer to the window containing the
>>>>> current workarea in every part of the code I need to use
On Wed, Jul 16, 2014 at 4:32 PM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
Le 16/07/14 20:41, Marcelo Galvão Póvoa a écrit :
* adding a fake variable to lyxrc is bad :)
Is there a better alternative? The variable can be made customizable
like the others but I don't know if it makes
On Wed, Jul 16, 2014 at 4:32 PM, Jean-Marc Lasgouttes
<lasgout...@lyx.org> wrote:
> Le 16/07/14 20:41, Marcelo Galvão Póvoa a écrit :
>
>>> * adding a fake variable to lyxrc is bad :)
>>
>>
>> Is there a better alternative? The variable can be made customiza
On Tue, Jul 15, 2014 at 6:23 PM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
Le 15/07/14 02:03, Marcelo Galvão Póvoa a écrit :
This is excellent work. I am surprised that so many parts of the code
need
to be changed, the way the blog entry is written made me think that the
changes could
On Tue, Jul 15, 2014 at 6:23 PM, Jean-Marc Lasgouttes
<lasgout...@lyx.org> wrote:
> Le 15/07/14 02:03, Marcelo Galvão Póvoa a écrit :
>
>>> This is excellent work. I am surprised that so many parts of the code
>>> need
>>> to be changed, the way
Hello,
LyX has been lacking HiDPI (retina) support for a while now and I
decided to tackle this project. It has been listed as a GSoC 2013
potential project [1], so I assume there's enough interest in it.
I worked on a patch which adds basic 2x DPI drawing support for text
and graphics. Math
On Mon, Jul 14, 2014 at 8:01 PM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
Le 14/07/14 22:44, Marcelo Galvão Póvoa a écrit :
I worked on a patch which adds basic 2x DPI drawing support for text
and graphics. Math formulas and inline images also work (except the
splash screen) but the UI
(later, I can only double-check it doesn't break compilation on
Linux :-) if needed).
According to that Qt blog post, HiDPI support is available for X11
too! I don't know the details of how to make it work because I haven't
tried myself.
T.
On 14/07/14 21:44, Marcelo Galvão Póvoa wrote:
Hello
Hello,
LyX has been lacking HiDPI ("retina") support for a while now and I
decided to tackle this project. It has been listed as a GSoC 2013
potential project [1], so I assume there's enough interest in it.
I worked on a patch which adds basic 2x DPI drawing support for text
and graphics. Math
On Mon, Jul 14, 2014 at 8:01 PM, Jean-Marc Lasgouttes
<lasgout...@lyx.org> wrote:
> Le 14/07/14 22:44, Marcelo Galvão Póvoa a écrit :
>
>> I worked on a patch which adds basic 2x DPI drawing support for text
>> and graphics. Math formulas and inline images also work (exc
t will reply you soon
> (later, I can only double-check it doesn't break compilation on
> Linux :-) if needed).
>
According to that Qt blog post, HiDPI support is available for X11
too! I don't know the details of how to make it work because I haven't
tried myself.
> T.
>
>
On Thu, May 2, 2013 at 1:43 AM, Pavel Sanda sa...@lyx.org wrote:
Marcelo Galv?o Póvoa wrote:
Please check the description I just sent. These side effects of
editing would be handled normally at the internal representation
level, the data to be sent are the changes to the textual
On Thu, May 2, 2013 at 1:36 PM, Pavel Sanda sa...@lyx.org wrote:
Marcelo Galv?o Póvoa wrote:
Just to check whether I understood your concept - you basically want to
synchronize the internal lyx structures between peers by using .lyx diffs
as
transport layer, while hoping that full
On Thu, May 2, 2013 at 1:43 AM, Pavel Sanda wrote:
> Marcelo Galv?o Póvoa wrote:
>> Please check the description I just sent. These side effects of
>> editing would be handled normally at the internal representation
>> level, the data to be sent are the changes to the textual
>>
On Thu, May 2, 2013 at 1:36 PM, Pavel Sanda wrote:
> Marcelo Galv?o Póvoa wrote:
>> > Just to check whether I understood your concept - you basically want to
>> > synchronize the internal lyx structures between peers by using .lyx diffs
>> > as
>> > transport layer, while hoping
On Wed, May 1, 2013 at 6:23 AM, Tommaso Cucinotta tomm...@lyx.org wrote:
You could, but I'm not sure about what advantage you get. LyX keeps in
memory a structured graph of C++ objects, not their serialized version.
If you send a serialized paragraph, then you have to de-serialize it
replacing
On Wed, May 1, 2013 at 7:27 AM, Pavel Sanda sa...@lyx.org wrote:
I can't comment whether your approach would work, but please think
how your approach work with several random bits:
- we don't have just linear structure of the document and sometimes
distance of change can be tricky thing,
On Wed, May 1, 2013 at 6:23 AM, Tommaso Cucinotta wrote:
> You could, but I'm not sure about what advantage you get. LyX keeps in
> memory a structured graph of C++ objects, not their serialized version.
> If you send a serialized paragraph, then you have to de-serialize it
>
On Wed, May 1, 2013 at 7:27 AM, Pavel Sanda wrote:
> I can't comment whether your approach would work, but please think
> how your approach work with several random bits:
>
> - we don't have just linear structure of the document and sometimes
> distance of change can be tricky
On Mon, Apr 29, 2013 at 8:56 PM, Nico Williams n...@cryptonector.com wrote:
BTW, this has all been solved before (clearly). Research it and use
whatever protocol pattern is most appropriate (or, if you can't
because of patents, invent a new protocol).
Some posts on this list pointed at some
On Tue, Apr 30, 2013 at 6:06 PM, Tommaso Cucinotta tomm...@lyx.org wrote:
On 30/04/13 21:12, Marcelo Galvăo Póvoa wrote:
there are indeed several possible approaches. I will try to briefly
describe mine and you can comment about its (in)feasibility.
As you say, your case was far easier, and
On Mon, Apr 29, 2013 at 8:56 PM, Nico Williams wrote:
> BTW, this has all been solved before (clearly). Research it and use
> whatever protocol pattern is most appropriate (or, if you can't
> because of patents, invent a new protocol).
>
> Some posts on this list pointed
On Tue, Apr 30, 2013 at 6:06 PM, Tommaso Cucinotta wrote:
> On 30/04/13 21:12, Marcelo Galvăo Póvoa wrote:
>> there are indeed several possible approaches. I will try to briefly
>> describe mine and you can comment about its (in)feasibility.
>
> As you say, your case was far
On Fri, Apr 19, 2013 at 6:08 PM, Tommaso Cucinotta tomm...@lyx.org wrote:
On 17/04/13 02:09, Marcelo Galvăo Póvoa wrote:
Is it possible to
write a Pidgin plugin that would serve as a communication channel for
LyX?
or perhaps checking whether it would be possible to leverage libpurple for
On Fri, Apr 19, 2013 at 6:08 PM, Tommaso Cucinotta wrote:
> On 17/04/13 02:09, Marcelo Galvăo Póvoa wrote:
>> Is it possible to
>> write a Pidgin plugin that would serve as a communication channel for
>> LyX?
>
> or perhaps checking whether it would be possible to leverage
On Mon, Apr 15, 2013 at 2:51 PM, Tommaso Cucinotta tomm...@lyx.org wrote
And also, in the collaborative editing feature, we need anyway users to be
able to find each other etc seems more like pulling Pidgin features
within the gigantic LyX, in the end!
Opinions ?
Well, it seems that
On Mon, Apr 15, 2013 at 2:51 PM, Tommaso Cucinotta wrote
> And also, in the collaborative editing feature, we need anyway users to be
> able to find each other etc seems more like pulling Pidgin features
> within the gigantic LyX, in the end!
>
> Opinions ?
>
Well, it
Hi Tommaso,
On Sun, Apr 14, 2013 at 10:05 AM, Tommaso Cucinotta tomm...@lyx.org wrote:
On 14/04/13 05:45, Marcelo Galvão Póvoa wrote:
Greetings!
My name is Marcelo Galvão Póvoa, a Computer Science graduate student from
UNICAMP, Brazil.
Hi Marcelo,
welcome to LyX! As outlined by others
Hi Tommaso,
On Sun, Apr 14, 2013 at 10:05 AM, Tommaso Cucinotta <tomm...@lyx.org> wrote:
> On 14/04/13 05:45, Marcelo Galvão Póvoa wrote:
>> Greetings!
>>
>> My name is Marcelo Galvão Póvoa, a Computer Science graduate student from
>> UNICAMP, Brazil.
&
Greetings!
My name is Marcelo Galvão Póvoa, a Computer Science graduate student from
UNICAMP, Brazil. I am very glad to see LyX participating in GSoC this year,
I hope to be able to contribute to this great application. One project idea
that caught my attention was the Interactive LyX: it's
Greetings!
My name is Marcelo Galvão Póvoa, a Computer Science graduate student from
UNICAMP, Brazil. I am very glad to see LyX participating in GSoC this year,
I hope to be able to contribute to this great application. One project idea
that caught my attention was the "Interactive LyX&q
34 matches
Mail list logo