gmane.editors.lyx.devel

Re: Upgrade Qt to 4.8?

Jerry — 2012-05-26T01:01:58

On May 24, 2012, at 8:26 PM, Jerry wrote:


Oops--After reading the Ubuntu comments about the File Open dialog problem I realized that I forgot to mention that I'm on OS X.

I'm wondering if the Qt folks have bothered to fix some of the problems this time around that bedevil (at least) OS X users. Like contextual menus not disappearing upon the second click unless the cursor is moved between clicks. (Oh, why did I start down that path? 8^/ )

Jerry

Feature request: native lyx format in View Source window

Andrew Parsloe — 2012-05-25T23:41:41

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 the natural place is the View Source window? For 
someone writing a converter to or from LyX format, this would be of 
great assistance.

(I'm aware the drop-down box is labelled "Output format:" but given that 
only two of the formats have any effect, that seems a misnomer. In fact 
I would expect Default to be LyX's native format, instead of LaTeX as at 
present, and LaTeX to be explicitly mentioned in the list.)

Andrew

Re: [LyX master] Fix painting of hidden tabbar on gtk

Jean-Marc Lasgouttes — 2012-05-25T17:33:42

Le 25/05/12 19:19, Vincent van Ravesteijn a écrit :

So now I know what this ugly line was. Great work!

JMarc

Re: LyX 2.0.4

Pavel Sanda — 2012-05-25T14:31:00

I already run through the list and pinged the bugs which seemed to me important. I also think
that all 2.0.4 milestoned bugs should not been mechanically retargeted to 2.0.5. Number of
oldtimers reached certain threshold after which you won't easily find the correct canditates
and so even the bugs which are merely forgotten get lost in the crowd.

If you agree I will retarget many _old_ 2.0.4 milestoned guys to 2.0.x. Opinions?

Pavel

LyX 2.0.4

Richard Heck — 2012-05-25T14:22:11

We've accumulated a good number of bug fixes for 2.0.4, and it's been 
almost three months since the last release, so it's time to start 
thinking about another one. I'll remerge strings and inform the 
translators shortly. Before I do that, please have a look at our list of 
bugs for 2.0.4
     
http://www.lyx.org/trac/wiki/BugTrackerHome#Unresolvedbugstargetedtonextmaintenancerelease2.0.4
and let me know if there are any we really need to fix before strings 
are frozen. Also, let me know which of these bugs you think we need to 
fix for the release, and let's mark them high priority.

Richard

Re: annoying behavior of Lyx 2.02+ -- Language toggle

Jean-Marc Lasgouttes — 2012-05-25T12:42:20

Le 25/05/2012 13:21, Ronen Abravanel a écrit :

Good. I would handle the case where no language is given to reset to 
default language (this is what is done with the "layout" lfun). This 
allows to to have a keybinding for resetting the langage.

Yes, in LyXAction.cpp

JMarc

Re: annoying behavior of Lyx 2.02+ -- Language toggle

Ronen Abravanel — 2012-05-25T11:21:23

I added an optional "set" argument to LFUN_LANGUAGE and fixed the menu
entery.

Anythhing else? Should I fix the LFUN documentation?

On Wed, May 23, 2012 at 11:37 PM, Stephan Witt <st.witt< at >gmx.net> wrote:

Re: Upgrade Qt to 4.8?

John McCabe-Dansted — 2012-05-25T11:05:40

On Fri, May 25, 2012 at 5:11 PM, Jean-Marc Lasgouttes
<lasgouttes< at >lyx.org> wrote:

WorksForMe(TM).

My understanding is that If you don't use remote shares and/or you are
willing to delete stale configuration files you'll be fine. YMMV of
course.

Re: Upgrade Qt to 4.8?

Liviu Andronic — 2012-05-25T10:06:04

On Fri, May 25, 2012 at 11:11 AM, Jean-Marc Lasgouttes
<lasgouttes< at >lyx.org> wrote:
Oh, I didn't hear about that one. Sorry.

Liviu

Re: Upgrade Qt to 4.8?

Jean-Marc Lasgouttes — 2012-05-25T09:11:44

Le 25/05/2012 08:03, Liviu Andronic a écrit :

You except the bug that makes it impossible to use the File/Open dialog?

https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/946956

JMarc

Re: Upgrade Qt to 4.8?

Liviu Andronic — 2012-05-25T06:03:55

I suppose no in particular. For example Ubuntu Precise ships LyX 2.0.2
with Qt 4.8.1, and I haven't seen angry reports on our list. This
said, I have no experience with the version combination. If LyX is
critical to your productivity, I would suggest first testing this
setup in a VM.

Regards
Liviu

Upgrade Qt to 4.8?

Jerry — 2012-05-25T03:26:26

What would be the effects if any on LyX by upgrading my Qt installation from 4.7 to 4.8?

Jerry

Re: Shared Pointers

Richard Heck — 2012-05-24T19:18:06

Thanks. That's exactly what I needed.

Richard

Re: Branch 2.0.x-candidate

Richard Heck — 2012-05-24T16:58:39

You can make the danger of a bad merge, etc, less serious by:
     git co 2.0.x
     git co -b backport/7047
This creates a new branch based on 2.0.x, identifying the fix as a 
backport for #7047, say.

I don't object to the other strategy. Not everyone has to use it. But if 
some people want to
do it that way, it's fine with me.

Richard

Re: Trac improvements

Pavel Sanda — 2012-05-24T16:48:15

You have my full support :)
P

Re: Branch 2.0.x-candidate

Pavel Sanda — 2012-05-24T16:47:40

It seems to me it creates more mess than it solves and would prefer
to let the decision business in mailing list or trac rather than moving
it to git.


I usually commit to branch simulatenously with trunk commit.
Right, there is push waiting in the queue, but from my experience
Richard accepts 99% of patches, so the danger of wasted work is small.

Pavel

Re: Trac improvements

Vincent van Ravesteijn — 2012-05-24T16:41:35

Op 24-5-2012 18:34, Pavel Sanda schreef:

That's exactly why I want to change the default to lyxgit instead of lyxsvn.

Vincent

Re: Trac improvements

Pavel Sanda — 2012-05-24T16:34:18

Btw i have seen recently bugtracker using constructs r698fe32 with git,
which would be more convenient than [X/lyxgit] construct.
Haven't look whether some plugin exists for this... P

Re: Shared Pointers

Vincent van Ravesteijn — 2012-05-24T13:09:36

Op 24-5-2012 14:39, Richard Heck schreef:

doc_class = const_pointer_cast<DocumentClass>(tc->clone());

(std::tr1::const_pointer_cast or boost::const_pointer_cast, see 
support/shared_ptr.h)

Vincent

Branch 2.0.x-candidate

Vincent van Ravesteijn — 2012-05-24T12:43:03

Hi all,

Is it a good idea to create a branch "2.0.x-candidate" to where we can 
backport the fixes without asking for permission. If Richard likes all 
candidates, he just needs to fast-forward the 2.0.x branch to 
2.0.x-candidate. If not all candidates can be accepted, Richard can 
cherry-pick the commits he likes, or interactively rebase the branch 
"2.0.x-candidate" on top of 2.0.x after indicating which commits to use 
and which not.

This allows to commit to trunk and branch in one go and saves the 
questioning, waiting and answering of backport requests.

Such a branch would be a temporary one and can be rewound by Richard 
after he acknowledged all fixes.

Vincent

Re: Shared Pointers

Richard Heck — 2012-05-24T12:39:32

It's in the patch attached to "Deal with Memory Issue" I posted a couple 
days ago. Here are the relevant bits:

+typedef shared_ptr<DocumentClass>  DocumentClassPtr;
+typedef shared_ptr<DocumentClass const>  DocumentClassConstPtr;

-typedef limited_stack<pair<ParagraphList, DocumentClass const *>  >  CutStack;
+typedef limited_stack<pair<ParagraphList, DocumentClassConstPtr>  >  CutStack;

-void BufferParams::setDocumentClass(DocumentClass const * const tc)
+void BufferParams::setDocumentClass(DocumentClassConstPtr tc)
  {
  // evil, but this function is evil
-doc_class_ = const_cast<DocumentClass *>(tc);
+doc_class_ = tc->clone();
  }

+DocumentClassPtr DocumentClass::clone() const
+{
+return DocumentClassPtr(new DocumentClass(*this));
+}

The point is that doc_class_ has to be non-const, but we do want const 
stuff on the CutStack. We used to do a const_cast, but that doesn't work 
now. So we end up with an extra DocumentClass. Still, it's an 
improvement, since a lot of them will now be destroyed by