Re: Trac mails b0rken

[Vincent van Ravesteijn]

>
> >
> > We really thought you received everything, because you agreed on
> > everything that we decided.
>
> Seriously: It would be good to fix this ASAP. I just browsed though the
> latest changes and saw that you asked me to look at bug 4812, but I did not
> get any mail. Therefore I believe that there are comments I should be
> notified of.
>
>
> Georg
>

Yes, of course it should be fixed. I'm still receiving the mails (using the
lyx.org address), so it looks like a mystery why others do not receive
them.

Vincent

Re: #7839: equation editor: cropped PDF and EPS

[Liviu Andronic]

Dear all,
I've just updated a patch that simply adds two new converters to LyX:
pdflatex -> pdfcrop and DVI -> EPS. They're also accompanied by two
templates, which only set 'empty' page style and predefine the default
output format.

This basically allow us to have an "equation editor"-like "mode" in
LyX, by acting as a "generator for embeddable graphics" (equations,
commented graphics, etc). I think this is a very useful (and
long-requested) feature obtained via an inexpensive approach.

I propose it for inclusion in 2.1. Please comment.

Regards,
Liviu


On Mon, May 13, 2013 at 10:59 PM, LyX Ticket Tracker  wrote:
> #7839: equation editor: cropped PDF and EPS
> -+-
>  Reporter:  landroni |   Owner:  rgheck
>  Type:  enhancement  |  Status:  new
>  Priority:  low  |   Milestone:  2.1.0
> Component:  export   | Version:  2.0.1
>  Severity:  normal   |  Resolution:
>  Keywords:  patch|
> -+-
>
> Comment (by landroni):
>
>  I attached updated patch and templates. Please review. (The templates
>  allow for an "equation editor"-like "mode" in LyX.)
>
> --
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: Trac mails b0rken

[Stephan Witt]

Am 14.05.2013 um 01:25 schrieb Richard Heck :

> On 05/13/2013 06:32 PM, Pavel Sanda wrote:
>> Richard Heck wrote:
 Seriously: It would be good to fix this ASAP. I just browsed though the
 latest changes and saw that you asked me to look at bug 4812, but I did
 not get any mail. Therefore I believe that there are comments I should be
 notified of.
>>> I'm not sure what would be causing this problem. Who here knows about trac?
>> Not really, but there should be trac.log and email log with smtp messages
>> somewhere in /var. It should be possible to find messages from #6305
>> I sent yesterday - those between ps@ added .. @ps removed were received
>> others were not delivered.
> 
> So we have:
> 
> [logging]
> log_file = trac.log
> log_level = WARN
> log_type = syslog
> 
> which is supposed to put the logfile in /home/lyx/www/trac/log/trac.log, if 
> I'm not mistaken, since trac itself is running from /home/lyx/www/trac/. 
> Unfortunately, there is no such file. I'm guessing this may be a permissions 
> issue.

I'd guess trac is logging via syslog messages with level WARN.
Some messages may be located inside /var/log/messages or similar.
It depends on the syslog config.

Stephan

Re: GSoC 2013: OutlineView and CorkboardView - ideas and questions

[Ashley Shan]

Hi Richard,

I saw the same sentence but I didn't think much about it until you pointed
it out. I think QWidget examples should help me to use drag and drop in the
graphic view framework. Thanks!

Ashley


*Xueqing Shan*
Vanderbilt University, '16


On Mon, May 13, 2013 at 11:57 PM, Richard Heck  wrote:

>  On 05/13/2013 11:17 AM, Ashley Shan wrote:
>
>  Hi Richard,
>
>  Thank you very much for the link. I looked at these examples earlier
> today, but I realized that they are for Qt Widgets, not for the Graphic
> View Framework.
>
>
> Sorry, I didn't even realize these were different. However, I also read:
>
> Because QGraphicsView
>  inherits QWidget  indirectly,
> it already provides the same drag and drop functionality that 
> QWidget
>  provides.
>
> Does that help?
>
> Richard
>
>

XHTML compile warnings

[Uwe Stöhr]

Hi Richard,

I just checked out your latest changes and get these errors when compiling 
(CMake, Qt 4.8.4):

D:\LyXGit\Master\src\output_xhtml.h(167): warning C4099: 'lyx::html::FontTag' : type name first seen 
using 'class' now seen using 'struct' [D:\LyXGit\Master\compile-result\src\insets\insets.vcxproj]
D:\LyXGit\Master\src\output_xhtml.h(181): warning C4099: 'lyx::html::EndFontTag' : type name first 
seen using 'class' now seen using 'struct' [D:\LyXGit\Master\compile-result\src\insets\insets.vcxproj]


could you please have a look?

thanks and regards
Uwe

Re: Trac mails b0rken

[Richard Heck]

On 05/13/2013 06:32 PM, Pavel Sanda wrote:

Richard Heck wrote:

Seriously: It would be good to fix this ASAP. I just browsed though the
latest changes and saw that you asked me to look at bug 4812, but I did
not get any mail. Therefore I believe that there are comments I should be
notified of.

I'm not sure what would be causing this problem. Who here knows about trac?

Not really, but there should be trac.log and email log with smtp messages
somewhere in /var. It should be possible to find messages from #6305
I sent yesterday - those between ps@ added .. @ps removed were received
others were not delivered.


So we have:

[logging]
log_file = trac.log
log_level = WARN
log_type = syslog

which is supposed to put the logfile in /home/lyx/www/trac/log/trac.log, 
if I'm not mistaken, since trac itself is running from 
/home/lyx/www/trac/. Unfortunately, there is no such file. I'm guessing 
this may be a permissions issue.


Richard




Pavel

Re: Trac mails b0rken

[Pavel Sanda]

Richard Heck wrote:
>> Seriously: It would be good to fix this ASAP. I just browsed though the
>> latest changes and saw that you asked me to look at bug 4812, but I did 
>> not get any mail. Therefore I believe that there are comments I should be
>> notified of.
>
> I'm not sure what would be causing this problem. Who here knows about trac?

Not really, but there should be trac.log and email log with smtp messages
somewhere in /var. It should be possible to find messages from #6305
I sent yesterday - those between ps@ added .. @ps removed were received
others were not delivered.

Pavel

Re: CMake for Apple?

[Jean-Marc Lasgouttes]

Le 13/05/13 19:21, Abdelrazak Younes a écrit :

I think it is worth investing time in it. At the meeting everybody
agreed that we should have one build system in the long run. But to make
cmake official we need to achieve the following:


Translation: at the meeting we had a rather heated discussion where 
Abdel tried to make us think that all binary maintainer were eagerly 
waiting for the day where autotools will be dead and that if would be 
cruel from us to delay this moment. Or something.


So we agreed that indeed one build system is better than two, and since 
windows people are kind of not adaptable (as in "I'll give you my visual 
studio project file when you pry it from my cold, dead hands"), only 
autotools could go.


However, the point is that cmake is not ready for that now, so that the 
discussion is purely rhetoric (and believe me we had a lot of that in 
Milano :).


Did I correctly translated Abdel? :p

JMarc

Re: Trac mails b0rken

[Richard Heck]

On 05/13/2013 04:01 PM, Georg Baum wrote:

Vincent van Ravesteijn wrote:

On Sunday, May 12, 2013, Pavel Sanda  wrote:

Vincent van Ravesteijn wrote:

I got them all.

ldm conspiracy  :))


We really thought you received everything, because you agreed on
everything that we decided.

Seriously: It would be good to fix this ASAP. I just browsed though the
latest changes and saw that you asked me to look at bug 4812, but I did not get 
any mail. Therefore I believe that there are comments I should be
notified of.


I'm not sure what would be causing this problem. Who here knows about trac?

Richard

Re: EPS vs EPS (uncropped)

[Liviu Andronic]

Georg,


On Mon, May 13, 2013 at 8:46 PM, Georg Baum
 wrote:
>> What is eps2 for? What is the difference between the two?
>
> See the comment in configure.py just in front of the eps2->eps converter. If
> this is not understandable please explain what is unclear, and I'll try to
> improve the comment.
>
I've just published a patch adding two new converters:
http://www.lyx.org/trac/ticket/7839#comment:9 . Could you take a look
to see that it doesn't mess up with the eps/eps2 setup?

Thanks,
Liviu

Re: Trac mails b0rken

[Georg Baum]

Vincent van Ravesteijn wrote:

> On Sunday, May 12, 2013, Pavel Sanda  wrote:
>> Vincent van Ravesteijn wrote:
>>> I got them all.
>>
>> ldm conspiracy  :))
>>
> 
> We really thought you received everything, because you agreed on
> everything that we decided.

Seriously: It would be good to fix this ASAP. I just browsed though the 
latest changes and saw that you asked me to look at bug 4812, but I did not 
get any mail. Therefore I believe that there are comments I should be 
notified of.


Georg

Re: Should the 2.1 milestone be dropped or changed to 2.2?

[Pavel Sanda]

Scott Kostyshak wrote:
> Anyways, I won't fight this anymore, except that however milestone is
> used, I think it should be used the same by everyone. If there's
> inconsistent treatment across time (e.g. *if* in transition from 2.0
> to 2.1 all tickets with milestone 2.0 are changed to 2.1 but in 2.1 to
> 2.2 all tickets with milestone 2.1 now have no milestone) or across
> people, then it's meaning becomes less useful.

Well, it was not *that* bad in 2.0 and we didn't have this kind of nice listing
in bugzilla times. My opinion is to kill milestone if I see that they have been
alreeady retargeted and no activity meanwhile. I started to do this even with
2.0.1/2/3... milestones, bugs just get 2.0.x after while.

Pavel

Re: Should the 2.1 milestone be dropped or changed to 2.2?

[Pavel Sanda]

Liviu Andronic wrote:
> I think 'Severity' serves this purpose. High severity usually pertains
> to problematic bugs (not enhancements); these include crashes, data
> loss, etc.

Yes, I will add it to the FAQ if it's not there yet. P

Re: CMake for Apple?

[Vincent van Ravesteijn]

Op 13 mei 2013 20:58 schreef "Georg Baum" 
het volgende:
>
> Abdelrazak Younes wrote:
>
> > I think it is worth investing time in it. At the meeting everybody
> > agreed that we should have one build system in the long run. But to make
> > cmake official we need to achieve the following:
> > 1) implement the missing feature of autotools in cmake, especially for
> > MAC as I believe that Linux/Unix is complete thanks to the hard work of
> > Peter first and then Kornel.
> > 2) Deprecate autotools
> > 3) update the documentation (Readme/Wiki/etc)
> > 4) allow some time for developers to fully switch to cmake
> > 5) remove autotools when we are done, hopefully before 2.1, if not for
> > 2.2.
> >
> > The one point that still needs discussion is GLOB versus explicit file
> > listing. While GLOB is IMO a very nice feature I know and understand
> > others dislike it. So I guess we also need to do this in cmake.
>
> The usage of GLOB in cmake is the only reason why I still use autotools.
It
> interferes with my style of working (where it can happen that some play
.cpp
> files lie around), and it is also dangerous for making official builds:
> These should only compile stuff which is explicitly listed, otherwise you
> could easily end up with unreproducable compilations. Therefore I'd add
one
> item to the top of the list:

Just a wild idea: Only add cpp-files that are version tracked by git.

Vincent

Re: Should the 2.1 milestone be dropped or changed to 2.2?

[Vincent van Ravesteijn]

Op 13 mei 2013 20:39 schreef "Vincent van Ravesteijn"  het
volgende:

>
> Op 13 mei 2013 16:18 schreef "Scott Kostyshak"  het
> volgende:
> >
> > Now that LyX 2.1 is coming up, many tickets are being dealt with. For
> > these tickets, if they aren't likely to make it into 2.1, the
> > milestone is being dropped. Is this what's normally done? I was
> > expecting the milestone to be changed to 2.2.
> >
> > Is it correct that the tickets with milestone 2.1 that don't make it
> > into to 2.1 will not be treated like tickets with no milestone?
> >
> > Perhaps this is a good thing. This would force us to think about all
> > of the milestones of all unmarked tickets. There are probably some old
> > tickets that are being ignored that should have been marked with a
> > milestone.
> >
> > Scott
>
> The following represents my opinion.
>
> Bugs that are rather new, and bugs that might or should be fixed will keep
> the milestone 2.1. If they dont get fixed zoon, they will be retargeted to
> 2.1.X or 2.2.0.
>
> Bugs that have not been touched since they got retargeted from 2.0 to 2.1
> (because back then nobody worked on it) will lose the milestone.
>
> Vincent
>

Re: EPS vs EPS (uncropped)

[Liviu Andronic]

On Mon, May 13, 2013 at 8:46 PM, Georg Baum
 wrote:
> Liviu Andronic wrote:
>
>> Dear all,
>> In trunk we have two EPS formats:
>> \Format epseps EPS"" "%%"""
>> "vector""image/x-eps"
>> \Format eps2   eps"EPS (uncropped)"   "" "%%"   ""
>>  "vector"""
>>
>> What is eps2 for? What is the difference between the two?
>
> See the comment in configure.py just in front of the eps2->eps converter. If
> this is not understandable please explain what is unclear, and I'll try to
> improve the comment.
>
I completely missed that comment. I think it's sufficiently clear.

Thanks,
Liviu

Re: CMake for Apple?

[Georg Baum]

Abdelrazak Younes wrote:

> I think it is worth investing time in it. At the meeting everybody
> agreed that we should have one build system in the long run. But to make
> cmake official we need to achieve the following:
> 1) implement the missing feature of autotools in cmake, especially for
> MAC as I believe that Linux/Unix is complete thanks to the hard work of
> Peter first and then Kornel.
> 2) Deprecate autotools
> 3) update the documentation (Readme/Wiki/etc)
> 4) allow some time for developers to fully switch to cmake
> 5) remove autotools when we are done, hopefully before 2.1, if not for
> 2.2.
> 
> The one point that still needs discussion is GLOB versus explicit file
> listing. While GLOB is IMO a very nice feature I know and understand
> others dislike it. So I guess we also need to do this in cmake.

The usage of GLOB in cmake is the only reason why I still use autotools. It 
interferes with my style of working (where it can happen that some play .cpp 
files lie around), and it is also dangerous for making official builds: 
These should only compile stuff which is explicitly listed, otherwise you 
could easily end up with unreproducable compilations. Therefore I'd add one 
item to the top of the list:

0) Implement explicit file lists and introduce a switch which you can use to 
choose between GLOB and explicit file lists. The default should be not to 
use GLOB.

I agree that GLOB is a nice feature and has its use cases, but it is not a 
one fits all solution.
 
> Final point: This is just a proposal based on the feedback I received
> during the meeting. Other developers might disagree of course and in
> this case we should discuss more :-)

No, I think this is a pretty good summary (I can't tell about the meeting, 
but about the many messages that have already been written about this 
topic).


Georg

Re: EPS vs EPS (uncropped)

[Georg Baum]

Liviu Andronic wrote:

> Dear all,
> In trunk we have two EPS formats:
> \Format epseps EPS"" "%%"""
> "vector""image/x-eps"
> \Format eps2   eps"EPS (uncropped)"   "" "%%"   ""
>  "vector"""
> 
> What is eps2 for? What is the difference between the two?

See the comment in configure.py just in front of the eps2->eps converter. If 
this is not understandable please explain what is unclear, and I'll try to 
improve the comment.


Georg

Re: Should the 2.1 milestone be dropped or changed to 2.2?

[Liviu Andronic]

On Mon, May 13, 2013 at 8:35 PM, Scott Kostyshak  wrote:
> But there should be some way to specify urgency. 'Priority' seems
> determined by other variables so is not used for this.
>
I think 'Severity' serves this purpose. High severity usually pertains
to problematic bugs (not enhancements); these include crashes, data
loss, etc.

Liviu

Re: Diffs for Features?

[Richard Heck]

On 05/13/2013 01:43 PM, Pavel Sanda wrote:

Richard Heck wrote:

This appears to be only for the features repo. I can copy the post-receive
hook from the main repo if people want diffs for this repo.

Please, that was what I was asking for.


Should be working.

rh

Re: Should the 2.1 milestone be dropped or changed to 2.2?

[Scott Kostyshak]

On Mon, May 13, 2013 at 2:10 PM, Pavel Sanda  wrote:
> Scott Kostyshak wrote:
>> I think the milestone should also be set if someone *should* be
>> working on it. There are some bugs that I report/modify that are not
>
> I'm afraid that number of bugs that we consider *someone else* should
> really do it is already 4*zillion ;)

But there should be some way to specify urgency. 'Priority' seems
determined by other variables so is not used for this.

Anyways, I won't fight this anymore, except that however milestone is
used, I think it should be used the same by everyone. If there's
inconsistent treatment across time (e.g. *if* in transition from 2.0
to 2.1 all tickets with milestone 2.0 are changed to 2.1 but in 2.1 to
2.2 all tickets with milestone 2.1 now have no milestone) or across
people, then it's meaning becomes less useful.

Scott

Re: Should the 2.1 milestone be dropped or changed to 2.2?

[Pavel Sanda]

Scott Kostyshak wrote:
> I think the milestone should also be set if someone *should* be
> working on it. There are some bugs that I report/modify that are not

I'm afraid that number of bugs that we consider *someone else* should
really do it is already 4*zillion ;)

P

Re: CMake for Apple?

[Pavel Sanda]

Abdelrazak Younes wrote:
> I think it is worth investing time in it. At the meeting everybody agreed 
> that we should have one build system in the long run. But to make cmake 
> official we need to achieve the following:
> 1) implement the missing feature of autotools in cmake, especially for MAC 
> as I believe that Linux/Unix is complete thanks to the hard work of Peter 
> first and then Kornel.

How about making correct tarballs, does it currently work in the same way as 
with autotools?
(I mean producing approximately the same set of files.)


Pavel

Re: Should the 2.1 milestone be dropped or changed to 2.2?

[Scott Kostyshak]

On Mon, May 13, 2013 at 1:52 PM, Pavel Sanda  wrote:
> Scott Kostyshak wrote:
>> Is it correct that the tickets with milestone 2.1 that don't make it
>> into to 2.1 will not be treated like tickets with no milestone?
>
> It depends, many enhacenment bugs are there for years and no one is going to 
> touch them.
> Milestone has some meaning if there is reason to believe that someone is 
> working on it,

I think the milestone should also be set if someone *should* be
working on it. There are some bugs that I report/modify that are not
in my comfort area of the code or are too advanced for me to fix.
However, I think they should be fixed "soon" and I would like to be
able to mark them as such.

> otherwise you have just zillion entries. After some threshold such milestone
> stops to have any meaning and thats what already happened with 2.1.

Agreed.

> So if you see some bug you are particularly interested in and perhaps fix it, 
> feel free
> to retarget 2.2.

OK.

Scott

Re: Should the 2.1 milestone be dropped or changed to 2.2?

[Scott Kostyshak]

On Mon, May 13, 2013 at 10:25 AM, Richard Heck  wrote:
> On 05/13/2013 10:17 AM, Scott Kostyshak wrote:
>> Perhaps this is a good thing. This would force us to think about all
>> of the milestones of all unmarked tickets. There are probably some old
>> tickets that are being ignored that should have been marked with a
>> milestone.
>
> I think that's the idea: that we re-think all the targeted bugs and decide
> if they really should be targeted.

In this case, it might be good to have a 'someday' milestone.
Otherwise, there is no way to list in trac which tickets have a
milestone that has been evaluated versus which tickets have not been
evaluated. Many tickets without milestones were evaluated and decided
as not being important for the near future. It should be able to mark
these as such instead of using 'not marking them' to serve that
function.

Scott

Re: Should the 2.1 milestone be dropped or changed to 2.2?

[Pavel Sanda]

Scott Kostyshak wrote:
> Is it correct that the tickets with milestone 2.1 that don't make it
> into to 2.1 will not be treated like tickets with no milestone?

It depends, many enhacenment bugs are there for years and no one is going to 
touch them.
Milestone has some meaning if there is reason to believe that someone is 
working on it,
otherwise you have just zillion entries. After some threshold such milestone
stops to have any meaning and thats what already happened with 2.1.
So if you see some bug you are particularly interested in and perhaps fix it, 
feel free
to retarget 2.2.

Pavel

Re: Diffs for Features?

[Pavel Sanda]

Richard Heck wrote:
> This appears to be only for the features repo. I can copy the post-receive 
> hook from the main repo if people want diffs for this repo.

Please, that was what I was asking for. Pavel

Re: GSoC 2013: OutlineView and CorkboardView - ideas and questions

[Abdelrazak Younes]

On 13/05/2013 16:52, Ashley Shan wrote:

Dear community,

So I have been working with Rob on the non-linear writing project for 
a week already, and I'm focusing on implementing the corkboard 
graphics Ui. We planned to implement it using the graphic view 
framework, but I tried QML and think it's really cool. I want to hear 
from the community to what degree should I use QML in corkboard UI. I 
was planning to use QGraphicsItem for the card, QGraphicsScene for the 
board, and QGraphicsView for the view, and integrate them into the 
document model later; right now, I'm thinking of using QML for the 
entire UI part, using a GridView component for the board, but I'm not 
sure whether it's preferable in the long run and whether the document 
model can make use of the GridView component.


QML is only fully available since Qt 4.8. I guess it would be OK to use 
it if it is optional. But I fear the general look of feel of it will not 
be nice when mixed with QWidget; for example I don't know if you can 
embed a QML scene inside a QWidget. With QGraphicsView this is fully 
supported.




Also, I'm still very confused about using drag and drop; could anyone 
point to me some good resources to learn the graphic view framework's 
drag and drop? Thanks in advance.


Drag and drop is fully supported. Did you try to google for 
"qgraphicsitem drag and drop"?


http://qt-project.org/doc/qt-4.8/qgraphicsitem.html#dragLeaveEvent
http://qt-project.org/doc/qt-4.8/qgraphicsitem.html#dropEvent

Abdel

Re: CMake for Apple?

[Abdelrazak Younes]

On 13/05/2013 14:54, Stephan Witt wrote:

Am 13.05.2013 um 11:20 schrieb Benjamin Piwowarski 
:

When make install from CMake produces an useful result like the auto-tools make 
install
we have a good starting point.  Then one can change the mentioned shell script 
or add its
functionality to the CMake package build.


I don't have a strong preference towards any build system, but the only point 
is that having to take care of updating both each time is cumbersome and 
error-prone. So that's why I am ready to work on it - but only if cmake is 
chosen as the only build system (otherwise, it does not make sense to put so 
much effort in maintaining both working build systems).

Yes, and I have to admit I never had a problem with multiple build systems.
Surely because auto-tools and CMake both are working fine for me most of the 
time.

OK, then maybe this is not worth investing time in it.

Let's wait what others say.


I think it is worth investing time in it. At the meeting everybody 
agreed that we should have one build system in the long run. But to make 
cmake official we need to achieve the following:
1) implement the missing feature of autotools in cmake, especially for 
MAC as I believe that Linux/Unix is complete thanks to the hard work of 
Peter first and then Kornel.

2) Deprecate autotools
3) update the documentation (Readme/Wiki/etc)
4) allow some time for developers to fully switch to cmake
5) remove autotools when we are done, hopefully before 2.1, if not for 2.2.

The one point that still needs discussion is GLOB versus explicit file 
listing. While GLOB is IMO a very nice feature I know and understand 
others dislike it. So I guess we also need to do this in cmake.


So Benjamin, if you are willing to help it will be very good for the 
project.


Final point: This is just a proposal based on the feedback I received 
during the meeting. Other developers might disagree of course and in 
this case we should discuss more :-)


Cheers,
Abdel.

Re: GSoC 2013: OutlineView and CorkboardView - ideas and questions

[Richard Heck]

On 05/13/2013 11:17 AM, Ashley Shan wrote:

Hi Richard,

Thank you very much for the link. I looked at these examples earlier 
today, but I realized that they are for Qt Widgets, not for the 
Graphic View Framework.


Sorry, I didn't even realize these were different. However, I also read:

BecauseQGraphicsView 
inheritsQWidget 
indirectly, it already 
provides the same drag and drop functionality thatQWidget 
provides.


Does that help?

Richard

Re: GSoC 2013: OutlineView and CorkboardView - ideas and questions

[Ashley Shan]

Hi Richard,

Thank you very much for the link. I looked at these examples earlier today,
but I realized that they are for Qt Widgets, not for the Graphic View
Framework. The only resources I can find about using drag and drop in the
graphic view framework are:

http://qt-project.org/doc/qt-4.8/graphicsview.html#drag-and-drop
http://qt-project.org/doc/qt-4.8/graphicsview-dragdroprobot.html

I wonder whether people may have other resources about this topic?

Ashley


*Xueqing Shan*
Vanderbilt University, '16


On Mon, May 13, 2013 at 11:06 PM, Richard Heck  wrote:

>  On 05/13/2013 10:52 AM, Ashley Shan wrote:
>
> Also, I'm still very confused about using drag and drop; could anyone
> point to me some good resources to learn the graphic view framework's drag
> and drop? Thanks in advance.
>
>
> http://qt-project.org/doc/qt-4.8/examples-draganddrop.html
>
> Sorry, don't know anything about QML.
>
> Richard
>
>

Re: GSoC 2013: OutlineView and CorkboardView - ideas and questions

[Richard Heck]

On 05/13/2013 10:52 AM, Ashley Shan wrote:
Also, I'm still very confused about using drag and drop; could anyone 
point to me some good resources to learn the graphic view framework's 
drag and drop? Thanks in advance.


http://qt-project.org/doc/qt-4.8/examples-draganddrop.html

Sorry, don't know anything about QML.

Richard

GSoC 2013: OutlineView and CorkboardView - ideas and questions

[Ashley Shan]

Dear community,

So I have been working with Rob on the non-linear writing project for a
week already, and I'm focusing on implementing the corkboard graphics Ui.
We planned to implement it using the graphic view framework, but I tried
QML and think it's really cool. I want to hear from the community to what
degree should I use QML in corkboard UI. I was planning to use
QGraphicsItem for the card, QGraphicsScene for the board, and QGraphicsView
for the view, and integrate them into the document model later; right now,
I'm thinking of using QML for the entire UI part, using a GridView
component for the board, but I'm not sure whether it's preferable in the
long run and whether the document model can make use of the GridView
component.

Also, I'm still very confused about using drag and drop; could anyone point
to me some good resources to learn the graphic view framework's drag and
drop? Thanks in advance.

Ashley

Re: Should the 2.1 milestone be dropped or changed to 2.2?

[Liviu Andronic]

On Mon, May 13, 2013 at 4:25 PM, Richard Heck  wrote:
> I think that's the idea: that we re-think all the targeted bugs and decide
> if they really should be targeted. I've reset milestones for a few already.
>
I think so, too. This basically means that if a devel works on the
feature or a user is still interested in it, the bug will get
re-targeted after the release. If not, it'll start rotting on
bugtracker without any milestone.

Liviu

Re: Should the 2.1 milestone be dropped or changed to 2.2?

[Richard Heck]

On 05/13/2013 10:17 AM, Scott Kostyshak wrote:

Now that LyX 2.1 is coming up, many tickets are being dealt with. For
these tickets, if they aren't likely to make it into 2.1, the
milestone is being dropped. Is this what's normally done? I was
expecting the milestone to be changed to 2.2.

Is it correct that the tickets with milestone 2.1 that don't make it
into to 2.1 will not be treated like tickets with no milestone?

Perhaps this is a good thing. This would force us to think about all
of the milestones of all unmarked tickets. There are probably some old
tickets that are being ignored that should have been marked with a
milestone.


I think that's the idea: that we re-think all the targeted bugs and 
decide if they really should be targeted. I've reset milestones for a 
few already.


Richard

Should the 2.1 milestone be dropped or changed to 2.2?

[Scott Kostyshak]

Now that LyX 2.1 is coming up, many tickets are being dealt with. For
these tickets, if they aren't likely to make it into 2.1, the
milestone is being dropped. Is this what's normally done? I was
expecting the milestone to be changed to 2.2.

Is it correct that the tickets with milestone 2.1 that don't make it
into to 2.1 will not be treated like tickets with no milestone?

Perhaps this is a good thing. This would force us to think about all
of the milestones of all unmarked tickets. There are probably some old
tickets that are being ignored that should have been marked with a
milestone.

Scott

Re: [PATCH] Implement the use of [[Context]] for placeholders

[Jean-Marc Lasgouttes]

13/05/2013 12:54, Vincent van Ravesteijn:

When placeholders are used, the context can indicate what will be
substituted for the placeholder (e.g. "%1$s[[date]], %1$s[[time]]).
---

Any objections to this patch ? I think it will be helpful for the translators.


Yes, good idea.

JMarc

EPS vs EPS (uncropped)

[Liviu Andronic]

Dear all,
In trunk we have two EPS formats:
\Format epseps EPS"" "%%"""
"vector""image/x-eps"
\Format eps2   eps"EPS (uncropped)"   "" "%%"   ""
 "vector"""

What is eps2 for? What is the difference between the two?

Thanks,
Liviu


-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Diffs for Features?

[Richard Heck]

On 05/12/2013 11:46 AM, Stephan Witt wrote:

Am 12.05.2013 um 16:51 schrieb v...@lyx.org:


Author: Uwe Stöhr 
Date: Sun, 12 May 2013 12:57:14 +0200
New Commit: 1fded6e8175e92c1eaa1e85db7c3f8187e47e602
URL: 
http://git.lyx.org/?p=features.git;a=commit;h=1fded6e8175e92c1eaa1e85db7c3f8187e47e602

Log:
UserGuide.lyx: next revision step

- sec. 6.7 - 6.13


Since commit 704328d3488c75733ddeb9ad5439b1907e323e39 there is no diff sent to 
the list anymore.


This appears to be only for the features repo. I can copy the 
post-receive hook from the main repo if people want diffs for this repo.


Richard

Re: Re: [PATCH] Implement the use of [[Context]] for placeholders

[Kornel Benko]

Am Montag, 13. Mai 2013 um 15:25:22, schrieb Jürgen Spitzmüller 
> Richard Heck wrote:
> > On 05/13/2013 06:54 AM, Vincent van Ravesteijn wrote:
> > > When placeholders are used, the context can indicate what will be
> > > substituted for the placeholder (e.g. "%1$s[[date]], %1$s[[time]]).
> > > ---
> > > 
> > > Any objections to this patch ? I think it will be helpful for the
> > > translators.
> > Fine with me, though maybe the people doing translations should chime in.
> 
> Looks sensible.
> 
> Jürgen

I, too, wish more messages would have context info.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: [PATCH] Implement the use of [[Context]] for placeholders

[Jürgen Spitzmüller]

Richard Heck wrote:
> On 05/13/2013 06:54 AM, Vincent van Ravesteijn wrote:
> > When placeholders are used, the context can indicate what will be
> > substituted for the placeholder (e.g. "%1$s[[date]], %1$s[[time]]).
> > ---
> > 
> > Any objections to this patch ? I think it will be helpful for the
> > translators.
> Fine with me, though maybe the people doing translations should chime in.

Looks sensible.

Jürgen

Re: [PATCH] Implement the use of [[Context]] for placeholders

[Richard Heck]

On 05/13/2013 06:54 AM, Vincent van Ravesteijn wrote:

When placeholders are used, the context can indicate what will be
substituted for the placeholder (e.g. "%1$s[[date]], %1$s[[time]]).
---

Any objections to this patch ? I think it will be helpful for the translators.


Fine with me, though maybe the people doing translations should chime in.

rh

Re: bug on Lyx 2.0.6?

[Richard Heck]

On 05/12/2013 12:44 PM, Julien Rioux wrote:

On 09/05/2013 5:05 PM, Nicola Scafetta, Ph. D. wrote:

The bug with LyXHTML, which is different from that encountered with
elyxer.py, is the following.

See the attached files.

In the .xhtml file the reference in the text appears with a symbol after
the year that should not be there.



I see this too. The "modifier", which is an additional letter used if 
you have more than one reference with the same author and year, isn't 
initialized properly. We should fix this in LyX, so thanks for your 
report of the problem.


Do you mean it is not initialized in the BibTeXInfo constructor?

Richard

Re: CMake for Apple?

[Stephan Witt]

Am 13.05.2013 um 11:20 schrieb Benjamin Piwowarski 
:

> On May 13, 2013, at 10:35 , Stephan Witt  wrote:
> 
>> Am 13.05.2013 um 09:08 schrieb Benjamin Piwowarski 
>> :
>> 
>>> On May 12, 2013, at 17:51 , Stephan Witt  wrote:
>>> 
 Am 12.05.2013 um 17:04 schrieb Benjamin Piwowarski 
 :
 
> Hi,
> 
> I would be happy to participate (in July/August) to make the cmake 
> building process complete and more fool-proof on mac (a few months ago I 
> was able to build successfully a working bundle).
 
 What do you call a working bundle? It has to contain the frameworks it 
 depends on.
 Anyway, I have no preference for one build system or the other. And of 
 course your
 support would be greatly appreciated.
>>> 
>>> A working bundle would be the full LyX application (i.e. the LyX.app folder 
>>> currently constructed correctly only by auto-tools). 
>> 
>> This would be a regression for the user.  She has to download and install Qt 
>> frameworks
>> herself and the remaining spell checker would be the "Native" one.  
>> Currently the Qt and
>> spell checker frameworks are added to the bundle as private frameworks. The 
>> resulting
>> bundle I'd call the "full LyX application".
> They are (or at least were) included in the bundle with cmake builds, so I 
> guess this is OK.

I see it now. There are missing pieces:
 * Qt frameworks: Qt depends dynamically on QtSvg, QtXml, QtNetwork
 * Qt plugins: libqgif.dylib, libqsvg.dylib, libqico.dylib, libqjpeg.dylib, 
libqtga.dylib, libqmng.dylib, libqtiff.dylib
 * Qt translations
 * Spotlight library

> What was remaining was to include all the other resources (I did not check 
> that all files included by the shell script were included in the LyX.app 
> bundle constructed via cmake)

The target "make install" produces a (nearly) valid LyX.app. (Without the 
missing pieces mentioned above.)

BTW, I see tons of messages like this for "make install":
src/CMakeFiles/LyX.dir/build.make:120: warning: overriding commands for target 
`bin/LyX.app/Contents/Resources/bind/menus.bind'
src/CMakeFiles/LyX.dir/build.make:104: warning: ignoring old commands for 
target `bin/LyX.app/Contents/Resources/bind/menus.bind'

The result of "make package" is not usable, IMHO. 
E.g. the copied LyX.app has no Frameworks folder.

>> As I said already, this is done by a shell script and not by the auto-tools 
>> make install.
> OK - I did not get this point. With CMake this shell script would not be 
> necessary.
> 
>> 
>> When make install from CMake produces an useful result like the auto-tools 
>> make install
>> we have a good starting point.  Then one can change the mentioned shell 
>> script or add its
>> functionality to the CMake package build.
>> 
>>> I don't have a strong preference towards any build system, but the only 
>>> point is that having to take care of updating both each time is cumbersome 
>>> and error-prone. So that's why I am ready to work on it - but only if cmake 
>>> is chosen as the only build system (otherwise, it does not make sense to 
>>> put so much effort in maintaining both working build systems).
>> 
>> Yes, and I have to admit I never had a problem with multiple build systems.
>> Surely because auto-tools and CMake both are working fine for me most of the 
>> time.
> OK, then maybe this is not worth investing time in it.

Let's wait what others say.

Stephan

[PATCH] Implement the use of [[Context]] for placeholders

[Vincent van Ravesteijn]

When placeholders are used, the context can indicate what will be
substituted for the placeholder (e.g. "%1$s[[date]], %1$s[[time]]).
---

Any objections to this patch ? I think it will be helpful for the translators.

Vincent

 README.localization  |  5 +++--
 src/support/Messages.cpp | 27 +--
 2 files changed, 20 insertions(+), 12 deletions(-)

diff --git a/README.localization b/README.localization
index 52280f9..2f77eec 100644
--- a/README.localization
+++ b/README.localization
@@ -71,8 +71,9 @@ appear in your translations! Please take them exactly as they 
are or you may
 experience crashes when running LyX.
 
 [[Context]] is used to distinguish otherwise identical strings, which could
-have different translations depending on the Context. [[Context]] appears only
-in msgid string and should not be repeated in the translated version.
+have different translations depending on the Context. It can also be used to
+indicate what is substituted for a placeholder. [[Context]] appears only in
+msgid string and should not be repeated in the translated version.
 
 {} refer to counters and must not be translated. An example would be:
 msgid "Algorithm \\arabic{theorem}"
diff --git a/src/support/Messages.cpp b/src/support/Messages.cpp
index 1f56f4d..0ce9d55 100644
--- a/src/support/Messages.cpp
+++ b/src/support/Messages.cpp
@@ -105,19 +105,26 @@ void cleanTranslation(docstring & trans)
  Some english words have different translations, depending on
  context. In these cases the original string is augmented by
  context information (e.g. "To:[[as in 'From page x to page
- y']]" and "To:[[as in 'From format x to format y']]". This
- means that we need to filter out everything in double square
- brackets at the end of the string, otherwise the user sees
- bogus messages. If we are unable to honour the request we
- just return what we got in.
+ y']]" and "To:[[as in 'From format x to format y']]". Also, 
+ when placeholders are used, the context can indicate what will
+ be substituted for the placeholder (e.g. "%1$s[[date]], %1$s
+ [[time]]). This means that we need to filter out everything 
+ in double square brackets at the end of the string, otherwise
+ the user sees bogus messages. If we are unable to honour the
+ request we just return what we got in.
*/
static docstring const ctx_start = from_ascii("[[");
static docstring const ctx_end = from_ascii("]]");
-   size_t const pos1 = trans.find(ctx_start);
-   if (pos1 != docstring::npos) {
-   size_t const pos2 = trans.find(ctx_end, pos1);
-   if (pos2 != docstring::npos)
-   trans.erase(pos1, pos2 - pos1 + 2);
+   while (true) {
+   size_t const pos1 = trans.find(ctx_start);
+   if (pos1 != docstring::npos) {
+   size_t const pos2 = trans.find(ctx_end, pos1);
+   if (pos2 != docstring::npos) {
+   trans.erase(pos1, pos2 - pos1 + 2);
+   continue;
+   }
+   }
+   break;
}
 }
 
-- 
1.8.0.msysgit.0

Re: CMake for Apple?

[Benjamin Piwowarski]

On May 13, 2013, at 10:35 , Stephan Witt  wrote:

> Am 13.05.2013 um 09:08 schrieb Benjamin Piwowarski 
> :
> 
>> On May 12, 2013, at 17:51 , Stephan Witt  wrote:
>> 
>>> Am 12.05.2013 um 17:04 schrieb Benjamin Piwowarski 
>>> :
>>> 
 Hi,
 
 I would be happy to participate (in July/August) to make the cmake 
 building process complete and more fool-proof on mac (a few months ago I 
 was able to build successfully a working bundle).
>>> 
>>> What do you call a working bundle? It has to contain the frameworks it 
>>> depends on.
>>> Anyway, I have no preference for one build system or the other. And of 
>>> course your
>>> support would be greatly appreciated.
>> 
>> A working bundle would be the full LyX application (i.e. the LyX.app folder 
>> currently constructed correctly only by auto-tools). 
> 
> This would be a regression for the user.  She has to download and install Qt 
> frameworks
> herself and the remaining spell checker would be the "Native" one.  Currently 
> the Qt and
> spell checker frameworks are added to the bundle as private frameworks. The 
> resulting
> bundle I'd call the "full LyX application".
They are (or at least were) included in the bundle with cmake builds, so I 
guess this is OK. What was remaining was to include all the other resources (I 
did not check that all files included by the shell script were included in the 
LyX.app bundle constructed via cmake)

> 
> As I said already, this is done by a shell script and not by the auto-tools 
> make install.
OK - I did not get this point. With CMake this shell script would not be 
necessary.

> 
> When make install from CMake produces an useful result like the auto-tools 
> make install
> we have a good starting point.  Then one can change the mentioned shell 
> script or add its
> functionality to the CMake package build.
> 
>> I don't have a strong preference towards any build system, but the only 
>> point is that having to take care of updating both each time is cumbersome 
>> and error-prone. So that's why I am ready to work on it - but only if cmake 
>> is chosen as the only build system (otherwise, it does not make sense to put 
>> so much effort in maintaining both working build systems).
> 
> Yes, and I have to admit I never had a problem with multiple build systems.
> Surely because auto-tools and CMake both are working fine for me most of the 
> time.
OK, then maybe this is not worth investing time in it.

Re: CMake for Apple?

[Stephan Witt]

Am 13.05.2013 um 09:08 schrieb Benjamin Piwowarski 
:

> On May 12, 2013, at 17:51 , Stephan Witt  wrote:
> 
>> Am 12.05.2013 um 17:04 schrieb Benjamin Piwowarski 
>> :
>> 
>>> Hi,
>>> 
>>> I would be happy to participate (in July/August) to make the cmake building 
>>> process complete and more fool-proof on mac (a few months ago I was able to 
>>> build successfully a working bundle).
>> 
>> What do you call a working bundle? It has to contain the frameworks it 
>> depends on.
>> Anyway, I have no preference for one build system or the other. And of 
>> course your
>> support would be greatly appreciated.
> 
> A working bundle would be the full LyX application (i.e. the LyX.app folder 
> currently constructed correctly only by auto-tools). 

This would be a regression for the user.  She has to download and install Qt 
frameworks
herself and the remaining spell checker would be the "Native" one.  Currently 
the Qt and
spell checker frameworks are added to the bundle as private frameworks. The 
resulting
bundle I'd call the "full LyX application".

As I said already, this is done by a shell script and not by the auto-tools 
make install.

When make install from CMake produces an useful result like the auto-tools make 
install
we have a good starting point.  Then one can change the mentioned shell script 
or add its
functionality to the CMake package build.

> I don't have a strong preference towards any build system, but the only point 
> is that having to take care of updating both each time is cumbersome and 
> error-prone. So that's why I am ready to work on it - but only if cmake is 
> chosen as the only build system (otherwise, it does not make sense to put so 
> much effort in maintaining both working build systems).

Yes, and I have to admit I never had a problem with multiple build systems.
Surely because auto-tools and CMake both are working fine for me most of the 
time.

Stephan

Re: CMake for Apple?

[Benjamin Piwowarski]

On May 12, 2013, at 17:51 , Stephan Witt  wrote:

> Am 12.05.2013 um 17:04 schrieb Benjamin Piwowarski 
> :
> 
>> Hi,
>> 
>> I would be happy to participate (in July/August) to make the cmake building 
>> process complete and more fool-proof on mac (a few months ago I was able to 
>> build successfully a working bundle).
> 
> What do you call a working bundle? It has to contain the frameworks it 
> depends on.
> Anyway, I have no preference for one build system or the other. And of course 
> your
> support would be greatly appreciated.

A working bundle would be the full LyX application (i.e. the LyX.app folder 
currently constructed correctly only by auto-tools). 

I don't have a strong preference towards any build system, but the only point 
is that having to take care of updating both each time is cumbersome and 
error-prone. So that's why I am ready to work on it - but only if cmake is 
chosen as the only build system (otherwise, it does not make sense to put so 
much effort in maintaining both working build systems).

Benjamin