Hello all,
Here's a basic structure I was thinking of for the new website. The
first and second levels of indentation are what would be visible in the
sidebar. This is essentially a reorganization/consolidation of the pages
that currently exist.
http://www.lyx.org/~chr/www/org/index.php/Site
Open User Guide, View>DVI, BOom.
(gdb) bt
bt
#0 0x003c41430ec5 in raise (sig=) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x003c41432970 in abort () at abort.c:88
#2 0x004e9b1d in lyx::LyX::exit (this=0x4c3a, exit_code=19514)
at LyX.cpp:194
#3 0x009f7a10 in l
Pavel Sanda wrote:
Could someone do me a big favor implement this? I'm forever hitting F3 and
expecting it to advance me to the next search item.
will commit if no objections.
You'll certainly get no objection from me.
rh
mac Intel
OSX 10.5.2
make 1.6svn at revision 23963:
convert.cpp: In function 'Target lyx::convert(Source) [with Target =
int, Source = std::string]':
convert.cpp:121: error: 'strtol' was not declared in this scope
convert.cpp: In function 'Target lyx::convert(Source) [with Target =
int, Sou
Andre Poenitz wrote:
Of course, there may be other issues elsewhere, and you would know better
than I. I suppose I could start by doing this sort of thing to InsetText
and InsetCommand.
Yep, just do it ;-)
Unfortunately, this does run into huge problems in the end, at least for
Inset
> Could someone do me a big favor implement this? I'm forever hitting F3 and
> expecting it to advance me to the next search item.
will commit if no objections.
pavel
diff --git a/src/BufferView.cpp b/src/BufferView.cpp
index 9b3ae32..4c4cc6a 100644
--- a/src/BufferView.cpp
+++ b/src/BufferView.c
Andre Poenitz wrote:
Could you _please_ stop posting-on-top-and-full-quoting-below?
More than 50% of what you quote are not relevant to what you say,
and providing context _after_ comments to it is not the natural
flow of reading.
Andre'
PS: @everybody else: This is the second try ;-)
Sorry
Hi,
Because of recent spam, I decided to see if it helps that we now require a
password in order to "approve" a URI. What this mean is that if you edit a
wiki page in order to add a link to an external web page, it does not
automatically become a link. First you have click on the text "approve
On Tue, 25 Mar 2008, Edwin Leuven wrote:
[EMAIL PROTECTED] wrote:
and tell me like 3-4 of them you like, and then I can install those!
these look the least like ... wiki's
http: //www.pmwiki.org/wiki/Cookbook/ABitModernSkin
http: //www.pmwiki.org/wiki/Cookbook/BarthelmeSkin
http: //www.pmwi
On Wed, 26 Mar 2008, Peter Kümmel wrote:
Joost Verburg wrote:
Edwin Leuven wrote:
> http://www.pmwiki.org/wiki/Cookbook/ABitModernSkin
I've also used it for the Loki page (a bit smaller):
http://loki-lib.sourceforge.net/
I've installed ABitModernSkin, try this link:
http://www.lyx.org/~
On Wed, 26 Mar 2008, Andre Poenitz wrote:
Could you _please_ stop posting-on-top-and-full-quoting-below?
PS: @everybody else: This is the second try ;-)
Hi Rex,
If you're using Outlook or Outlook Expresse, the links here might help:
http://wiki.lyx.org/FAQ/ListNetiquette#toc9
c
On Tue, Mar 25, 2008 at 06:25:59PM -0400, Rex C. Eastbourne wrote:
> By the way, link to new wiki, again:
> http://www.lyx.org/~chr/www/org/index.php
>
> On Tue, Mar 25, 2008 at 6:12 PM, Rex C. Eastbourne <[EMAIL PROTECTED]>
> wrote:
>
> > I went ahead and ported a bit of lyx.org over to the new
Joost Verburg wrote:
Edwin Leuven wrote:
http://www.pmwiki.org/wiki/Cookbook/ABitModernSkin
I've also used it for the Loki page (a bit smaller):
http://loki-lib.sourceforge.net/
--
Peter Kümmel
On Tue, 25 Mar 2008, Edwin Leuven wrote:
[EMAIL PROTECTED] wrote:
and tell me like 3-4 of them you like, and then I can install those!
these look the least like ... wiki's
http: //www.pmwiki.org/wiki/Cookbook/ABitModernSkin
http: //www.pmwiki.org/wiki/Cookbook/BarthelmeSkin
http: //www.pmwi
Edwin Leuven wrote:
http://www.pmwiki.org/wiki/Cookbook/ABitModernSkin
With some different colors this one could look nice.
Joost
On Tue, Mar 25, 2008 at 05:10:48PM -0400, rgheck wrote:
>
> Could someone do me a big favor implement this? I'm forever hitting F3 and
> expecting it to advance me to the next search item.
I guess we could make LFUN_WORD_FIND just use the selection if it is
there and the search string is empty in
[EMAIL PROTECTED] wrote:
> and tell me like 3-4 of them you like, and then I can install those!
these look the least like ... wiki's
http://www.pmwiki.org/wiki/Cookbook/ABitModernSkin
http://www.pmwiki.org/wiki/Cookbook/BarthelmeSkin
http://www.pmwiki.org/wiki/Cookbook/SimpleTabSkin
Any cool skins we can try now?
Oh, when I think about it, a better idea if you look at skins at
http://www.pmwiki.org/wiki/Cookbook/Skins
and tell me like 3-4 of them you like, and then I can install those!
Note that you should be able to preview the skins at pmwiki.org, not just
read ab
Jean-Marc Lasgouttes wrote:
"Leuven, E." <[EMAIL PROTECTED]> writes:
we should get rid of this before 1.6 if you ask me, and set it to
system default using QPalette::Base and QPalette::Text for text (and
it would be also be good to use QPalette::Highlight and
QPalette::HighlightedText to render
On Tue, 25 Mar 2008, Rex C. Eastbourne wrote:
http://diberri.dyndns.org/wikipedia/html2wiki/index.html).
Nice!
One thing on my mind is the sidebar. Do you think people will view the
sidebar headers as clickable, or will they gravitate toward the elements
within them?.
Unfortunately people
By the way, link to new wiki, again:
http://www.lyx.org/~chr/www/org/index.php
On Tue, Mar 25, 2008 at 6:12 PM, Rex C. Eastbourne <[EMAIL PROTECTED]>
wrote:
> I went ahead and ported a bit of lyx.org over to the new wiki. This was a
> quick and dirty task (the links still point to the old site, a
On Mon, 24 Mar 2008, Joost Verburg wrote:
[EMAIL PROTECTED] wrote:
* wiki.lyx.org will remain the wiki - there is no integration of content.
It will be clear what is official and what is community.
The wiki may, or may not, keep it's current look.
Why not integrate the current wiki wit
> > i have an reproducible error on installing the svn-build:
>
> please try again.
fixed.
pavel
On Mon, 24 Mar 2008, Andre Poenitz wrote:
restricted. Currently, protection is already in place for important
pages on wiki.lyx.org.
Note that many wiki pages are currently maintained by developers. The
only reason why they are on the wiki is because adding new pages and
content to www.lyx.o
On Tue, Mar 25, 2008 at 04:03:24PM -0400, rgheck wrote:
> Andre Poenitz wrote:
>> On Tue, Mar 25, 2008 at 02:24:48PM -0400, rgheck wrote:
>>
>>> rgheck wrote:
>>>
Or are there some that don't need it? or want it?
>>> Here's the point of the question. There are surely s
I went ahead and ported a bit of lyx.org over to the new wiki. This was a
quick and dirty task (the links still point to the old site, and no content
has changed), but it should be enough to get a feel for what it'll look
like. All I did was modify the sidebar to re-create the same basic
structure,
rgheck wrote:
>
> Could someone do me a big favor implement this? I'm forever hitting F3
> and expecting it to advance me to the next search item.
>
> rh
+1... Grrr
Could someone do me a big favor implement this? I'm forever hitting F3
and expecting it to advance me to the next search item.
rh
Andre Poenitz wrote:
On Tue, Mar 25, 2008 at 02:24:48PM -0400, rgheck wrote:
rgheck wrote:
Or are there some that don't need it? or want it?
Here's the point of the question. There are surely still places in the code
where insets get constructed and their buffers don't get set.
On Tue, Mar 25, 2008 at 02:24:48PM -0400, rgheck wrote:
> rgheck wrote:
>>
>> Or are there some that don't need it? or want it?
>>
> Here's the point of the question. There are surely still places in the code
> where insets get constructed and their buffers don't get set. We can hunt
> these down
On Tue, Mar 25, 2008 at 12:57:19PM -0400, rgheck wrote:
>
> Or are there some that don't need it? or want it?
I think insets can't (nor should) live without Buffer.
Andre'
On Tue, Mar 25, 2008 at 12:15:12PM -0400, rgheck wrote:
> Andre Poenitz wrote:
>> On Tue, Mar 25, 2008 at 01:38:06AM -0400, rgheck wrote:
>>
>>> This patch prevents InsetGraphics from being created without a Buffer.
>>> Comments?
>>>
>>
>> General direction is ok.
>>
>>
> It seems like
Oliver Rath wrote:
> i have an reproducible error on installing the svn-build:
please try again.
Jürgen
rgheck wrote:
Or are there some that don't need it? or want it?
Here's the point of the question. There are surely still places in the
code where insets get constructed and their buffers don't get set. We
can hunt these down one crash at a time and probably still miss some or
we can do somet
Bo Peng wrote:
On Tue, Mar 25, 2008 at 11:57 AM, rgheck <[EMAIL PROTECTED]> wrote:
Or are there some that don't need it? or want it?
I do not have the answer but I think simple insets such as
InsetNewline does not really need a buffer pointer, whereas more
complicated ones should have
On Tue, Mar 25, 2008 at 11:57 AM, rgheck <[EMAIL PROTECTED]> wrote:
>
> Or are there some that don't need it? or want it?
I do not have the answer but I think simple insets such as
InsetNewline does not really need a buffer pointer, whereas more
complicated ones should have one. For example, emb
Dear LyX developers,
Kamila Giedrojć may have contacted you already, but in case she didn't, I'd
like to invite to attend Libe Graphics Meeting 2008 in Wrocław (Poland).
Despite its title the conference is not just about colours, drawing and
bitmaps, but also about print publishing and typograp
Jean-Marc Lasgouttes wrote:
we should get rid of this before 1.6 if you ask me, and set it to
system default using QPalette::Base and QPalette::Text for text (and
it would be also be good to use QPalette::Highlight and
QPalette::HighlightedText to render selections correctly too)
Yes, the color
Or are there some that don't need it? or want it?
rh
Jürgen Spitzmüller wrote:
Pavel Sanda wrote:
bisect leads to this commit:
http://www.lyx.org/trac/changeset/23942
no idea, really.
I investigated this for a bit, and it's really strange. If you run this
PYTHONPATH=../../lib/lyx2lyx python -tt ./doc_toc.py es .
manually, it's fi
Andre Poenitz wrote:
On Tue, Mar 25, 2008 at 01:38:06AM -0400, rgheck wrote:
This patch prevents InsetGraphics from being created without a Buffer.
Comments?
General direction is ok.
It seems like doing this across the board would solve a lot of these
buffer pointer crashes. And i
Pavel Sanda wrote:
> bisect leads to this commit:
> http://www.lyx.org/trac/changeset/23942
no idea, really.
Jürgen
Jean-Marc Lasgouttes wrote:
rgheck <[EMAIL PROTECTED]> writes:
Jean-Marc Lasgouttes wrote:
A few thoughts:
Here's a different thought: Should we move the context menus into
their own file?
Yes, probably, since they are not related to the main menu hierarchy.
Don
rgheck <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes wrote:
>> A few thoughts:
>>
>>
> Here's a different thought: Should we move the context menus into
> their own file?
Yes, probably, since they are not related to the main menu hierarchy.
JMarc
Jean-Marc Lasgouttes wrote:
A few thoughts:
Here's a different thought: Should we move the context menus into their
own file?
- for footnotes, the two Open and Close entry look weird, and I think
the following seems better:
Menu "context-collapsable"
- Item "Open
Jean-Marc Lasgouttes wrote:
rgheck <[EMAIL PROTECTED]> writes:
2. I've dramatically shortened and simplified the External Material
section. Much of this was no longer needed because of the Embedded
Objects manual. What's left are the parts that talk about how to
define your own templates. (I
> > [..]
> > make install-data-hook
> > make[4]: Entering directory `/home/oliver/lyx-devel/lib/doc'
> > PYTHONPATH=../../lib/lyx2lyx python -tt ./doc_toc.py cs .
> > Warning: Malformed file.
> > Warning: Malformed file.
> > [..]
> > Warning: Malformed file.
> > ^C^Cend = find_end_of_inset(sel
> [..]
> make install-data-hook
> make[4]: Entering directory `/home/oliver/lyx-devel/lib/doc'
> PYTHONPATH=../../lib/lyx2lyx python -tt ./doc_toc.py cs .
> Warning: Malformed file.
> Warning: Malformed file.
> [..]
> Warning: Malformed file.
> ^C^Cend = find_end_of_inset(self.body, k)
> make[
=
--- src/Text3.cpp (Revision 23947)
+++ src/Text3.cpp (Arbeitskopie)
@@ -658,36 +658,24 @@
break;
}
- case LFUN_NEW_LINE: {
- // Not allowed by LaTeX (labels or empty par)
- if (cur.pos() > cur.paragraph().beginOfBody()) {
- // this avoids a double undo
-
Pavel Sanda <[EMAIL PROTECTED]> writes:
>> - fullscreen mode does not belong to the context-edit menu. This is
>> spelled out in apple HIG AFAIR (only 'local' things belong there).
>
> this was discussed some time ago. currently this is the only possibility
> how to return back from fullscreen m
> - fullscreen mode does not belong to the context-edit menu. This is
> spelled out in apple HIG AFAIR (only 'local' things belong there).
this was discussed some time ago. currently this is the only possibility
how to return back from fullscreen mode in case you overlooked the shortcut.
pavel
Jean-Marc Lasgouttes wrote:
> - for footnotes, the two Open and Close entry look weird, and I think
> the following seems better:
>
> Menu "context-collapsable"
> - Item "Open Inset|O" "next-inset-toggle open"
> - Item "Close Inset|C" "next-inset-toggle close"
Hi list,
i have an reproducible error on installing the svn-build:
[..]
make install-data-hook
make[4]: Entering directory `/home/oliver/lyx-devel/lib/doc'
PYTHONPATH=../../lib/lyx2lyx python -tt ./doc_toc.py cs .
Warning: Malformed file.
Warning: Malformed file.
[..]
Warning: Malformed file.
^
A few thoughts:
- for footnotes, the two Open and Close entry look weird, and I think
the following seems better:
Menu "context-collapsable"
- Item "Open Inset|O" "next-inset-toggle open"
- Item "Close Inset|C" "next-inset-toggle close"
+ OptIt
rgheck wrote:
If I open (say) the Customization manual and immediately right-click on
a charstyle, then Toggle Inset line is disabled. It remains that way
through further right-clicking. If I double click into the inset,
though, then it works.
Hello,
I am very pleased with how you guys end
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
> However, I still think the dialog is redundant (and we should
> probably provide these functions elsewhere).
Yes, in the normal menus.
JMarc
rgheck wrote:
> If I open (say) the Customization manual and immediately right-click on
> a charstyle, then Toggle Inset line is disabled. It remains that way
> through further right-clicking. If I double click into the inset,
> though, then it works.
This is strange. next-inset-toggle is disabled
Jean-Marc Lasgouttes wrote:
> http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGui
>delines/XHIGMenus/chapter_17_section_5.html#//apple_ref/doc/uid/TP3356-T
>PXREF113
>
> http://library.gnome.org/devel/hig-book/stable/menus-types.html.en#menu-typ
>e-popup
>
> http://msdn2
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes wrote:
>> I remember that one very basic rule for context menus is that they
>> should only contain things that are available elsewhere.
>
> Do you have a reference for that?
http://developer.apple.com/documentation/UserExperi
[EMAIL PROTECTED] writes:
> Sounds like it should be possible, although I'm not sure what you mean.
> One way could be to have some kind of script run at commit of certain
> files, and this script would then generate the relevant data which in
> turned is inserted into wiki pages (or parsed furthe
rgheck <[EMAIL PROTECTED]> writes:
> 2. I've dramatically shortened and simplified the External Material
> section. Much of this was no longer needed because of the Embedded
> Objects manual. What's left are the parts that talk about how to
> define your own templates. (Is this stuff much used now
On Tue, 25 Mar 2008, Jean-Marc Lasgouttes wrote:
[EMAIL PROTECTED] writes:
Ok, so no one seems to object to using the wiki engine for the framework.
We also seem to agree on the following:
* www.lyx.org will be replaced by something that uses a wiki engine for
the CMS.
It will not look li
On Tue, 25 Mar 2008, Jean-Marc Lasgouttes wrote:
"Dominik Böhm" <[EMAIL PROTECTED]> writes:
Having a look at www.lyx.com, I don't see very much dynamic content.
Everything looks pretty static -- the only thing that gets updated
frequently are the new and download section (and the (external) wi
On Mon, 24 Mar 2008, Rex C. Eastbourne wrote:
Great, Christian! Should we now manually copy and paste content over
from the current website and wikify it?
Yes, we can start doing that if we'd like. Actually, it's probably a good
idea to do so for at least two or three pages. Then, when we app
Jean-Marc Lasgouttes wrote:
> I remember that one very basic rule for context menus is that they
> should only contain things that are available elsewhere.
Do you have a reference for that? In the case of Note and ERT dialog, I always
thought these (rather ridiculous) dialogs were a placeholder f
"Leuven, E." <[EMAIL PROTECTED]> writes:
> we should get rid of this before 1.6 if you ask me, and set it to
> system default using QPalette::Base and QPalette::Text for text (and
> it would be also be good to use QPalette::Highlight and
> QPalette::HighlightedText to render selections correctly t
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
> BTW this renders the Note dialog redundand. I'd propose to get rid of the
> dialog now.
I remember that one very basic rule for context menus is that they
should only contain things that are available elsewhere.
JMarc
[EMAIL PROTECTED] writes:
> Ok, so no one seems to object to using the wiki engine for the framework.
> We also seem to agree on the following:
>
> * www.lyx.org will be replaced by something that uses a wiki engine for
> the CMS.
> It will not look like a wiki, although that's what it actuall
"Dominik Böhm" <[EMAIL PROTECTED]> writes:
> Having a look at www.lyx.com, I don't see very much dynamic content.
> Everything looks pretty static -- the only thing that gets updated
> frequently are the new and download section (and the (external) wiki
> of course). So, lyx.org looks to me like a
Martin wrote:
> You could consider choosing for "white" the default background
> of the LyX text window. That is kind of distinctive.
distinctive and it stinks.
we should get rid of this before 1.6 if you ask me, and set it to system
default using QPalette::Base and QPalette::Text for text (and
On Mon, Mar 24, 2008 at 12:58:04PM -0400, rgheck wrote:
> Martin Vermeer wrote:
> > On Mon, Mar 24, 2008 at 12:31:15PM +, [EMAIL PROTECTED] wrote:
> >
> >> Author: rgheck
> >> Date: Mon Mar 24 13:31:07 2008
> >> New Revision: 23913
> >>
> >> URL: http://www.lyx.org/trac/changeset/23913
> >>
On Mon, Mar 24, 2008 at 07:29:44PM +0100, [EMAIL PROTECTED] wrote:
> On Mon, 24 Mar 2008, Joost Verburg wrote:
>
> > Rich Shepard wrote:
> >>Regardless of what layout you choose and how you go about building
> >> it (I, too, support xhtml and css), there is one universal design
> >> criteri
rgheck wrote:
> Are you sure you got this in the right place? This looks like it should
> be in some dispatch() routine, not in getStatus().
Yes, I think it's correct here.
Jürgen
On Tue, Mar 25, 2008 at 01:38:06AM -0400, rgheck wrote:
>
> This patch prevents InsetGraphics from being created without a Buffer.
> Comments?
General direction is ok.
Note that a private (class) static function could as well be a
freestanding (anonymous/static) function in the cpp:
> ///
74 matches
Mail list logo
