Martin Vermeer wrote:
>
> We already have that: charstyles, which are however pretty
> limited. But they could be extended (under a different name
> probably, "style insets"?)
>
>> Could something like that do the trick for beamer? (I haven't
>> used beamer myself . . .)
>
> Would be a part
On Mon, Jul 30, 2007 at 10:07:54AM +0200, Helge Hafting wrote:
> Charles de Miramon wrote:
> > I think that what is needed is a standard mechanism to enter in a friendly
> > GUI way structured information in LyX like titlepages, frames in
> > beamer,multiple choice questions, etc. The gui form wou
Charles de Miramon wrote:
I think that what is needed is a standard mechanism to enter in a friendly
GUI way structured information in LyX like titlepages, frames in
beamer,multiple choice questions, etc. The gui form would be stored in the
layout and when you create a new beaamer frame (title pa
Martin Vermeer wrote:
>
>> What feature do you think that lyx is missing badly?
>
> The beamer layout requires too much ERT and non-intuitive tweaking.
> Perhaps something can be done about it in the frame of short title /
> optional argument. My dream is to have a LyX-beamer that is compatitive
Jürgen Spitzmüller wrote:
Helge Hafting wrote:
Well, I put my stuff in. The page is out of date, 1.5 is out
and every 1.5 feature could be removed. Or at least the votes
replaced with "done in 1.5" for the benefit of those who haven't upgraded.
Please go ahead.
Ok, removed votes
Richard Heck wrote:
Helge Hafting wrote:
* Layout files should be able to set things like document font,
language,
paper size and so on - if the layout writer thinks it is appropriate.
Today I can't just send someone a custom .layout, I have to tell
them to
set "palatino", margins, and
Pavel Sanda wrote:
* hyperref support - mostly a document settings checkbox
to load the package. Nice for PDFs. It should be noted that
there are some limitations - marking something hyper-referenced
with a foreign language will crash latex for example. Good
hyperref support can automati
Helge Hafting wrote:
> Well, I put my stuff in. The page is out of date, 1.5 is out
> and every 1.5 feature could be removed. Or at least the votes
> replaced with "done in 1.5" for the benefit of those who haven't upgraded.
Please go ahead.
Jürgen
Bo Peng wrote:
Maybe not _all_ are badly missed, but here is a wishlist with my
wishes as well as stuff from the user's list:
Did you have a look at http://wiki.lyx.org/LyX/FeaturePoll ? Maybe we
can put these stuff over there, and let the users decide what are the
most wanted.
Well, I put my
On Thu, 2007-07-26 at 14:53 +0200, Helge Hafting wrote:
> * People on the user list seems to ask for the SIunits package
>from time to time. Support might be in order.
+1 !!!
I currently have 46 macros at the top of my thesis to nicely display the
various units in use, with proper squaring, c
On Wed, Jul 25, 2007 at 05:11:39PM +0100, José Matos wrote:
> On Wednesday 25 July 2007 16:13:03 Bo Peng wrote:
> > > For 1.5.x, you'll need my OK.
> >
> > For 1.6.x, the usual review process applies.
> >
> > Bo
>
> I would like to see some kind of plan, nothing too formal but at the same
> time
Helge Hafting wrote:
* Layout files should be able to set things like document font, language,
paper size and so on - if the layout writer thinks it is appropriate.
Today I can't just send someone a custom .layout, I have to tell
them to
set "palatino", margins, and so on too. And they h
Maybe not _all_ are badly missed, but here is a wishlist with my
wishes as well as stuff from the user's list:
Did you have a look at http://wiki.lyx.org/LyX/FeaturePoll ? Maybe we
can put these stuff over there, and let the users decide what are the
most wanted.
Bo
And as one can see from the immediate opening of the branch (as opposed to
the agreement to branch only after 1.5.1 and fix a big bunch of the long
standing bugs before) you will probably not get much help on that branch,
although that would definitely be needed. My condolences.
Although I am ea
> * hyperref support - mostly a document settings checkbox
> to load the package. Nice for PDFs. It should be noted that
> there are some limitations - marking something hyper-referenced
> with a foreign language will crash latex for example. Good
> hyperref support can automatically add t
José Matos wrote:
On Wednesday 25 July 2007 16:13:03 Bo Peng wrote:
For 1.5.x, you'll need my OK.
For 1.6.x, the usual review process applies.
Bo
I would like to see some kind of plan, nothing too formal but at the same time
a general idea where the current development stage
On Thu, 26 Jul 2007 09:34:45 +0200
Georg Baum <[EMAIL PROTECTED]> wrote:
> Jürgen Spitzmüller wrote:
>
> > That's all for now. The rest of my time will probably go to 1.5.x.
>
> And as one can see from the immediate opening of the branch (as opposed to
> the agreement to branch only after 1.5.1
> > That's all for now. The rest of my time will probably go to 1.5.x.
>
> And as one can see from the immediate opening of the branch (as opposed to
> the agreement to branch only after 1.5.1 and fix a big bunch of the long
> standing bugs before) you will probably not get much help on that branc
On Thu, Jul 26, 2007 at 07:18:57AM +0200, Jürgen Spitzmüller wrote:
> Furthermore, I'd like to support Richard's idea of finishing the character
> style implementation.
(Yay)
john
Jürgen Spitzmüller wrote:
> That's all for now. The rest of my time will probably go to 1.5.x.
And as one can see from the immediate opening of the branch (as opposed to
the agreement to branch only after 1.5.1 and fix a big bunch of the long
standing bugs before) you will probably not get much h
José Matos wrote:
> I would like that each developer answered three questions:
>
> Where do you think that LyX needs more attention?
In the stable series ;-)
> What feature do you think that lyx is missing badly?
Proper character styles implementation and handling of more complex constructs
(op
José Matos wrote:
I would like that each developer answered three questions:
Where do you think that LyX needs more attention?
What feature do you think that lyx is missing badly?
The truth is, LyX is great as it is! ;)
However, I would be happy to see the following things, too:
* Proper s
Where do you think that LyX needs more attention?
* rendering speed
* proper uniform scrolling
What feature do you think that lyx is missing badly?
* proper math macros
Where do you intend to work during this development cycle?
I plan to look into the speed and scrolling issue soon. I ha
José Matos wrote:
What feature do you think that lyx is missing badly?
Inline spell checking.
Joost
>> Where do you think that LyX needs more attention?
> 2. I would like to have direct ODF (or word) export after our XML
> transition. Of course, this will encourage us to design a file format
> that is as close to ODF as possible.
To what extent does oolatex not do this? Granted, it could work be
Bo Peng wrote:
Where do you think that LyX needs more attention?
2. I would like to have direct ODF (or word) export after our XML
transition. Of course, this will encourage us to design a file format
that is as close to ODF as possible.
To what extent does oolatex not do this? Granted, it coul
On Wed, Jul 25, 2007 at 05:11:39PM +0100, José Matos wrote:
> On Wednesday 25 July 2007 16:13:03 Bo Peng wrote:
> > > For 1.5.x, you'll need my OK.
> >
> > For 1.6.x, the usual review process applies.
> >
> > Bo
>
> I would like to see some kind of plan, nothing too formal but at the
> same time a
Where do you think that LyX needs more attention?
File exchangability!!!
1. I am working on an embed file feature so that one can embed
figures, listings etc to a .lyx file so that one can open a lyx file
with everything in it directly.
2. I would like to have direct ODF (or word) export after
On Wednesday 25 July 2007 16:13:03 Bo Peng wrote:
> > For 1.5.x, you'll need my OK.
>
> For 1.6.x, the usual review process applies.
>
> Bo
I would like to see some kind of plan, nothing too formal but at the same time
a general idea where the current development stage is leading us.
I would lik
For 1.5.x, you'll need my OK.
For 1.6.x, the usual review process applies.
Bo
Richard Heck wrote:
> Now that 1.5.0 is branched, I take it that the trunk will be open for
> commits again shortly. What are the commit rules at that time? That is:
> Do we need agreement from someone else to commit? (That doesn't seem a
> bad idea.) Who will be "in charge", in the sense that Jose
Now that 1.5.0 is branched, I take it that the trunk will be open for
commits again shortly. What are the commit rules at that time? That is:
Do we need agreement from someone else to commit? (That doesn't seem a
bad idea.) Who will be "in charge", in the sense that Jose' has been in
charge r
32 matches
Mail list logo
