Re: Saying Hi !

Yes, a mechanisms that's more light-weight than CORBA (in terms of integration effort/architecture) is definitely going to more easily accepted in the code base. We'd also rather not double the size of the LyX binary ;-) but then again, some of the CORBA libraries are probably not that huge. P

Re: Saying Hi !

On 28.04.2014 22:31, Tommaso Cucinotta wrote: On 28/04/14 07:15, Peter Kümmel wrote: When designing the transfer protocol you should evaluate Google's Protocol Buffers: https://developers.google.com/protocol-buffers/docs/overview Would guarantee a clean interface to the outer world. And you do

Re: Procedure for porting patch to latest trunk

When I try to do git clone gitATgit.lyx.org:lyx its asking for gitATgit.lyx.org's password: what is the password required if I want to clone the repo? On Wed, Apr 30, 2014 at 2:42 AM, Tommaso Cucinotta wrote: > On 29/04/14 08:07, Sushant Raikar wrote: > > I am not so comfortable with git,

Re: Developping an add-on for LyX

On Tue, Apr 29, 2014 at 11:20 PM, Tommaso Cucinotta wrote: > I remind you that we don’t own Scenari, so we cannot modify its code. > > > Is this an on-line platform with embedded HTML editing capabilities within > the browser ? > http://scenari-platform.org/projects/opale/en/pres/co/ https://en.wi

Re: request for decisions for the release of LyX 2.1

Am 29.04.2014 10:32, schrieb Vincent van Ravesteijn: However, with an RC you attract more users to test a release than with a beta because people have the feeling to test an almost ready product. Yes, and with the final release you attract even more users, so let's do multiple final releases,

Re: Developping an add-on for LyX

On 29/04/14 08:58, alexan...@dubosc.fr wrote: > Dear LyX community, Hi, > My project tutor wants my team to make it possible to host LaTeX documents, > using a LaTeX to html converter. is that software a simple document management system ? Can it host documents in .tex, .html, .lyx, whatever el

Re: Procedure for porting patch to latest trunk

On 29/04/14 08:07, Sushant Raikar wrote: > I am not so comfortable with git, I see you already got explanations from others -- that's the advantage of the list, as you can see -- and, btw, Vincent's is THE git man here :-)! > http://www.lyx.org/trac/ticket/7964 to latest code base. let me also

Re: Feature request

On 29/04/14 17:59, Abdelrazak Younes wrote: > > FWIW, it is perfect here in Thunderbird. > > Indeed, perfect on both Windows and Linux. This is a killer feature for > scientist collaboration :-) So, this capability of copying and pasting into HTML e-mails should be advertised loudly IMHO, in cas

Re: [LyX/master] Make iparserdocstream more like std::istream

Vincent van Ravesteijn wrote: > This issues a warning for me: __cplusplus is defined as 199711L. Oops. I stole this test from src/support/strfwd.h, and I also read a bit on the web which values can be assumed for __cplusplus, but what I did not notice was that the number in strfwd.h was not cor

Re: LyX 2.0.8.1?

Richard Heck wrote: > Since 2.0.8 was never announced, it is easy enough to repackage and > just release 2.0.8.1. I have cherry picked the recent lyx2lyx commits. Is > that all? I.e., can I build the tarballs? In addition to the stuff which is already in 2.1 I'd like to see d6fecb4aa both in 2.1

Re: Does the AEA.lyx template compile for you?

On Thu, Apr 24, 2014 at 9:27 AM, Scott Kostyshak wrote: > On Wed, Apr 23, 2014 at 12:33 PM, K. Yokota wrote: >>> multicol 2011/06/27 v1.7a vs. multicol 2004/02/14 v1.6e >> >>> and >> >>> setspace 2011/12/19 v6.7a vs. setspace' 6.7 <2000/12/01> >> >> >> My multicol and setspace are the ones which

Re: #7631: Page tabs disappear with table tools

On Mon, Apr 28, 2014 at 4:11 AM, Vincent van Ravesteijn wrote: > > > > On Wed, Apr 23, 2014 at 3:28 PM, Scott Kostyshak wrote: >> >> On Tue, Apr 22, 2014 at 1:09 AM, F M Salter >> wrote: >> > I have checked that this behavior does not occur with 2.1rc1. >> > However the ticket appears not to be

Re: Is the user-dir/scripts folder added to PATH for converter script execution?

On Mon, Apr 28, 2014 at 5:44 AM, Jean-Marc Lasgouttes wrote: > 28/04/2014 01:57, Scott Kostyshak: > > I am not sure that I understand the second patch: what are the changes in > commandPrep wrt libScritpSearch exactly? How come that you did not need to > change the documentation of the function?

Re: When should I update the date of my patches?

On Mon, Apr 28, 2014 at 3:59 AM, Vincent van Ravesteijn wrote: > > > > On Mon, Apr 28, 2014 at 2:01 AM, Scott Kostyshak wrote: >> >> In Git, it is easy to change the date of a commit, for example with >> >> git commit --amend --date="$(date -R)" >> >> I have not been doing this because my fir

Re: Feature request

On 29/04/2014 18:20, Richard Heck wrote: On 04/28/2014 06:10 PM, stefano franchi wrote: On Mon, Apr 28, 2014 at 4:14 PM, Tommaso Cucinotta > wrote: On 28/04/14 19:37, Patrick O'Keeffe wrote: I don't personally see any advantage to composing emails in Lyx.

Re: Model for next releases (was: request for decisions for the release of LyX 2.1)

Pavel Sanda wrote: > I don't think this is not matter of forgetting/transparency. I agree with you this is not matter -> this is a matter

Model for next releases (was: request for decisions for the release of LyX 2.1)

Uwe Stöhr wrote: > blame you for this because we all are to blame here. We should start to > write down how we want to release that it becomes more transparent and that > we don't forget about that for the next release. Uwe, I don't think this is not matter of forgetting/transparency. I agree w

Re: Feature request

Am 29.04.2014 um 18:20 schrieb Richard Heck : > On 04/28/2014 06:10 PM, stefano franchi wrote: >> >> >> >> On Mon, Apr 28, 2014 at 4:14 PM, Tommaso Cucinotta wrote: >> On 28/04/14 19:37, Patrick O'Keeffe wrote: >>> I don't personally see any advantage to composing emails in Lyx. OP >>> sugges

Re: [LyX/master] boost: Turn off warning that signals are deprecated

Op 29 apr. 2014 17:52 schreef "Kornel Benko" : > > Am Dienstag, 29. April 2014 um 17:47:02, schrieb Vincent van Ravesteijn < v...@lyx.org> > > commit a25c946b318c6d4de6b2f548e5d820ac5f3c2f8c > > Author: Vincent van Ravesteijn > > Date: Tue Apr 29 16:56:23 2014 +0200 > > > > boost: Turn off w

Re: Feature request

On Tue, Apr 29, 2014 at 11:20 AM, Richard Heck wrote: > On 04/28/2014 06:10 PM, stefano franchi wrote: > > > > > On Mon, Apr 28, 2014 at 4:14 PM, Tommaso Cucinotta wrote: > >> On 28/04/14 19:37, Patrick O'Keeffe wrote: >> >> I don't personally see any advantage to composing emails in Lyx. OP >>

Re: LyX 2.0.8.1?

Richard Heck wrote: > Since 2.0.8 was never announced, it is easy enough to repackage and > just release 2.0.8.1. I have cherry picked the recent lyx2lyx commits. Is > that all? I.e., can I build the tarballs? Maybe add small note about the difference between 2.0.8 and 2.0.8.1. Pavel

Re: Feature request

On 04/28/2014 06:10 PM, stefano franchi wrote: On Mon, Apr 28, 2014 at 4:14 PM, Tommaso Cucinotta > wrote: On 28/04/14 19:37, Patrick O'Keeffe wrote: I don't personally see any advantage to composing emails in Lyx. OP suggested it because of the beautiful

Re: request for decisions for the release of LyX 2.1

On 04/29/2014 06:06 AM, Vincent van Ravesteijn wrote: I also read last week that some large tech companies are going to financially support OSS to prevent any new "Heartbleed" bugs. They say this bug was caused partly because the developers of OpenSSL just didn't have enough time to ensure th

Re: [ANNOUNCE] LyX 2.1.0 Released

On 04/28/2014 05:48 PM, Uwe Stöhr wrote: Am 25.04.2014 17:54, schrieb Richard Heck: The LyX development team is pleased to announce the release of LyX 2.1.0. Hi Richard, LyX 2.1 was already mentioned in Germany's largest PC magazine: http://www.heise.de/newsticker/meldung/Freie-LaTeX-Umgebu

LyX 2.0.8.1?

On 04/27/2014 11:50 AM, Georg Baum wrote: Pavel Sanda wrote: Georg Baum wrote: a document with invalid header settings and data loss where argument and index insets are mixed. I fixed these two problems at BTW how often this dataloss happens - only if index inset is present? (I ask whether im

Re: Copying and pasting to other apps

On 27/04/2014 23:11, Tommaso Cucinotta wrote: On 27/04/14 16:58, Georg Baum wrote: If you copy something, it is put onto the clipboard in three formats: plain text, HTML (using the HTML export) and LyX since version 2.1. The pasting application is then supposed to select the most appropriate f

Re: [LyX/master] boost: Turn off warning that signals are deprecated

Am Dienstag, 29. April 2014 um 17:47:02, schrieb Vincent van Ravesteijn > commit a25c946b318c6d4de6b2f548e5d820ac5f3c2f8c > Author: Vincent van Ravesteijn > Date: Tue Apr 29 16:56:23 2014 +0200 > > boost: Turn off warning that signals are deprecated > > diff --git a/configure.ac b/config

Re: [LyX/master] Make iparserdocstream more like std::istream

Georg Baum schreef op 22-4-2014 22:11: commit 0c0e16c61cb01555277c8605e970ace1f4fdce1b Author: Georg Baum Date: Tue Apr 22 22:03:31 2014 +0200 Make iparserdocstream more like std::istream In C++98 std::istream does not use an operator bool(), but an operator void*() inst

Re: Procedure for porting patch to latest trunk

Sushant Raikar schreef op 29-4-2014 9:07: I am not so comfortable with git, so I just wanted to make sure what my procedure should be if I want to port the patch http://www.lyx.org/trac/ticket/7964 to latest code base. 1) clone the developer repository |git clone g...@git.lyx.org:lyx |2) crea

Re: Procedure for porting patch to latest trunk

On Tue, Apr 29, 2014 at 2:07 AM, Sushant Raikar wrote: > > Can i create local branches for my convenience for example > gsoc/interactive/patchupdate? > > Hi Sushant, I would suggest you create your personal branch within gsoc/interactive (call it 'sushant') and use that branch as your personal pl

Re: #7954: Omega does not display in Mac

Am 29.04.2014 um 15:46 schrieb LyX Ticket Tracker : > #7954: Omega does not display in Mac > --+ > Reporter: DiGMi | Owner: spitz > Type: defect| Status: new > Priority: high |

Re: Instant Preview

Am 29.04.2014 um 12:08 schrieb Stephan Witt : > Am 29.04.2014 um 11:03 schrieb Rainer M Krug : > >> Stephan Witt writes: >> >>> Am 29.04.2014 um 10:09 schrieb Rainer M Krug : >>> Stephan Witt writes: > Am 29.04.2014 um 09:43 schrieb Rainer M Krug : > >> Jürgen Spitzmül

Re: request for decisions for the release of LyX 2.1

Jürgen Spitzmüller schreef op 29-4-2014 12:18: 2014-04-29 12:06 GMT+02:00 Vincent van Ravesteijn: OSS is not what it used to be. Most projects have ways of making money, or are supported by companies. Git's maintainer is hired by Google, major work on Git is done by GitHub people, KD

Re: request for decisions for the release of LyX 2.1

2014-04-29 12:06 GMT+02:00 Vincent van Ravesteijn: > OSS is not what it used to be. Most projects have ways of making money, > or are supported by companies. Git's maintainer is hired by Google, major > work on Git is done by GitHub people, KDE has a large investor that allows > them to hire deve

Re: Instant Preview

Am 29.04.2014 um 11:03 schrieb Rainer M Krug : > Stephan Witt writes: > >> Am 29.04.2014 um 10:09 schrieb Rainer M Krug : >> >>> Stephan Witt writes: >>> Am 29.04.2014 um 09:43 schrieb Rainer M Krug : > Jürgen Spitzmüller writes: > >> 2014-04-29 4:40 GMT+02:00 asllear

Re: request for decisions for the release of LyX 2.1

Jürgen Spitzmüller schreef op 29-4-2014 11:18: 2014-04-29 10:42 GMT+02:00 Jean-Marc Lasgouttes: This is how open source software works. Developers do what they want. I do not mean that they do stuff that nobody want. But if some one wants some "boring" feature to be implemented, they

Re: request for decisions for the release of LyX 2.1

2014-04-29 10:42 GMT+02:00 Jean-Marc Lasgouttes: > This is how open source software works. Developers do what they want. I do > not mean that they do stuff that nobody want. But if some one wants some > "boring" feature to be implemented, they have to pay someone to do it. It > is as simple as tha

Re: request for decisions for the release of LyX 2.1

On Tue, Apr 29, 2014 at 10:42 AM, Jean-Marc Lasgouttes wrote: > 28/04/2014 23:37, Uwe Stöhr: > > You mention an important point: We don't have a development plan. What >> do many customers need and what does only please us developers? We never >> did a user survey on our webpages and the lists. >

Re: request for decisions for the release of LyX 2.1

28/04/2014 23:37, Uwe Stöhr: You mention an important point: We don't have a development plan. What do many customers need and what does only please us developers? We never did a user survey on our webpages and the lists. For example I use math ad chemistry equations almost daily and it would be

Re: request for decisions for the release of LyX 2.1

On Tue, Apr 29, 2014 at 12:20 AM, Uwe Stöhr wrote: > Am 28.04.2014 23:58, schrieb Vincent van Ravesteijn: > >> Op 28 apr. 2014 23:17 schreef "Uwe >And that is what the RC-phase is about >> in my opinion: the program is feature-frozen and string frozen. Users get >> some weeks to test thoroughly

Developping an add-on for LyX

Dear LyX community, I am Master’s engineering student from France (Ecole des Mines de Nantes) and I am currently working on a school project in a team in which I will need to use your software. My school has recently developed a MOOC hosting Platform named PairForm. The Platform can curren

Procedure for porting patch to latest trunk

I am not so comfortable with git, so I just wanted to make sure what my procedure should be if I want to port the patch http://www.lyx.org/trac/ticket/7964 to latest code base. 1) clone the developer repository git clone g...@git.lyx.org:lyx 2) create a remote in gsoc repo git remote add gsoc g..