CONFIRMATION cash received

2000-07-24 Thread Get Noticed

Subject: 
CONFIRMATION cash received
   Date: 
Wed, 19 Jul 2000 22:20:22 -0100
   From: 
"Pat Dahlberg" <[EMAIL PROTECTED]>
 To: 
<[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, 
<[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, 
<[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, 
<[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, 
CC: 
<[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, 
<[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, 
<[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, 
<[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, 




 
 

Subject: Parents Of 15-Year-Old Find Big $$ In His Closet
 

It Works, Its Legal, Its Easy, Its Fun, so Why Not read this and play?!!!
 
Parents of 15-year-old find $71,000 cash hidden in his closet.
Does this headline look familiar?  Of course it does.  You most
likely have just seen this story recently featured on a major
nightly news program (USA).
 
His mother was cleaning and putting laundry away when she
came across a large brown paper bag that was suspiciously
buried beneath some clothes and a skateboard in the back of
her 15-year-old son's closet.  Nothing could have prepared her
for the shock she got when she opened the bag and found it
was full of cash.  Five dollar bills, twenties, fifties and
hundreds - all neatly rubber-banded in labelled piles.
 
 "My first thought was that he had robbed a bank", says the
41-year-old woman, "There was over $71,000 dollars
in that bag- that's more than my husband earns in a year".
 
The woman immediately called her husband at the
car-dealership where he worked to tell him what she'd
discovered.  He came home right away and they drove together
to the boy's school and picked him up.  Little did they suspect
that where the money came from was more shocking than
actually finding it in the closet.
 
As it turns out, the boy had been sending out via E-mail on the
Internet a type of 'chain-letter' to E-mail addresses that he
obtained off of the Internet.  Everyday after school for the past
2 months, he had been doing this right on his computer in his
bedroom.
 
"I just got the E-mail one day and I figured what the heck, I put
my name on it like the instructions said and I started sending it
out", says the clever 15-year-old.
 
The E-mail letter listed 3 addresses and contained instructions
to send one $5 dollar bill to the person at the top of the list,
then delete that address and move the other 2 addresses up, and
finally to add your name to the bottom of  the list.  The letter
goes on to state that you would receive several thousand
dollars in five dollar bills within 2 weeks if you sent out the
letter with your name at the bottom of the 3-address list "I get
junk E-mail all the time, and  I really didn't think it was gonna
work", the boy continues.
 
Within the first few days of sending out the E-mail, the Post
Office Box that  his parents had gotten him for his video-game
magazine subscriptions began to fill up with not magazines,
but envelopes containing $5 dollar bills.
 
"About a week later I rode [my bike] down to the post office
and my box had 1 magazine and about 300 envelopes
stuffed in it.  There was also a yellow slip that said I had to go
up to the [post office] counter- I thought I was in trouble or
something (laughs)". He goes on, "I went up to the counter
and they had a whole box of more mail for me.  I had to ride
back home and empty out my backpack 'cause I couldn't carry
it all".
 
Over the next few weeks, the boy continued sending out the
E-mail.  "The money just kept coming in and I just kept sorting
it and stashing it in the closet,  I barely had time for my
homework".  He had also been riding his bike to several of the
area's banks and exchanging the $5 bills for twenties, fifties
and hundreds.  "I didn't want the banks to get suspicious so I
kept riding to different banks with like five thousand at a time
in my backpack. I would usually tell the lady at the bank
counter that my dad had sent me in [to exchange the money]
and he was outside waiting for me.  One time the lady gave me
a really strange look and told me that she wouldn't be able to
do it for me and my dad would have to come in and do it, but
I just rode to the next bank down the street (laughs)."
 
Surprisingly, the boy didn't have any reason to be afraid.  The
reporting news team examined and investigated the so-called
'chain-letter' the boy was sending out and found that it wasn't a
chain-letter at all.  In fact, it was completely legal according to
US Postal and Lottery Laws, Title 18, Section 1302 and 1341,
or Title 18, Section 3005 in the US code, also in the code of
federal regulations, Volume 16,

Re: New layout for the menus

2000-07-24 Thread R. Lahaye

"R. Lahaye" wrote:
> File->New // Collapse New and New_from_template.
>   // Use "invalid" filename; when saved, call 'Save as...' automatically.
>   // Should a window popup ask for Template/Class or assume a default for 
>that?
>   Open // Collapse Open and Import. Open according to file extension:
>// .lyx, .tex, .txt, .nw, .doc are opened as you expect.
>// Does ASCII (*.txt) input need a Lines/Paragraph popup?

I all of a sudden realize that part of this discussion might have
to deal with the widgets that popup when selecting a menu item.

For example, in the File->Open/New/Template issue I would like
to emphasize the following ambiguity in the current actions of
these entries:

1) "New": apart from doing a real "New",
  I also can open an existing document, by just selecting it
  in the file list, which is strictly spoken an "Open"
  action and has nothing to do with "New"!

2) "New from template:  apart from opening a new file w/ new template,
  I once again can also open an *existing* document, which
  has nothing to do with "New from template".

3) "Open": apart from opening an existing document, I also can just
  type a new file name and so do basically a "New" instead.


Hmmm, to me this looks like every entry is designed as a sort of
failsafe:
 if you hit the wrong entry you still can do what you wanted to do.

Personally I find this confusing and I believe it lacks common sense
logic (consequently: documentation is needed to explain what menu
buttons do).
Ideally, a menu entry does (only) what "the man in the street" expects
it should do. In that case you can reduce a lot of the menu documentation
in Gnu-plot style: "This menu entry does what you expect it does".

Regards,

Rob.



Re: relaxed requirements on std::string

2000-07-24 Thread Lars Gullik Bjønnes

"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:

| What is your recommendation regarding LyX RPMs? Should I generated
| them --with-included-string? That's my inclination, considering the
| 800K bloat.

Just use --with-included-string ... unless you want to create gtk
rpm's :-)

Lgb




Re: relaxed requirements on std::string

2000-07-24 Thread Kayvan A. Sylvan

On Tue, Jul 25, 2000 at 12:22:14AM +0200, Lars Gullik Bjønnes wrote:
> 
> I have reduced LyX' requirements on std::string so that we are now
> able to compile with the std::string distributed with egcs and gcc
> 2.95.x. LyX will use this by default. If you want to use the lyxstring
> you have to use --with-included-string. One "bad" thing about the
>  std::string in gcc is that it enlarges the binary size of LyX with
>  some ~800k.

What is your recommendation regarding LyX RPMs? Should I generated
them --with-included-string? That's my inclination, considering the
800K bloat.

-- 
Kayvan A. Sylvan   | Proud husband of  | Father to my kids:
Sylvan Associates, Inc.| Laura Isabella Sylvan | Katherine Yelena
http://www.successlinks.com/kayvan | Reach your goals now! | Robin Gregory



relaxed requirements on std::string

2000-07-24 Thread Lars Gullik Bjønnes


I have reduced LyX' requirements on std::string so that we are now
able to compile with the std::string distributed with egcs and gcc
2.95.x. LyX will use this by default. If you want to use the lyxstring
you have to use --with-included-string. One "bad" thing about the
 std::string in gcc is that it enlarges the binary size of LyX with
 some ~800k.

This should make life a lot easier for those that are trying to port
LyX to gtk--.

Lgb



Re: GTK/Gnome frontend elementary support

2000-07-24 Thread Lars Gullik Bjønnes

Marko Vendelin <[EMAIL PROTECTED]> writes:

| the attached patch together with additional files included into the
| .tar.gz archive adds elementary support for GTK/Gnome frontend: configure
| scripts, Gtk/Gnome initialization, Gnome event loop processing, and
| Copyright dialog box implementation.

Ok, thanks.
I have applied the tar file and the patch.

| It should be easy to use this code on the platform with good STL string
| implementation. In such case you need standard gtk, gnome, libsigc++ ,
| gtk-- and gnome-- libraries.

I have not reducded LyX requirements on the std::string, so that LyX
is now able to use the bastring supplied with egcs and gcc 2.95.x.
This should make your life a lot easier.

I look forward so seeing this work progress further.

| Finally, to make configure script working I had to disable
| AC_LANG_CPLUSPLUS in configure.in (line 66). Otherwise gnome configuration
| scripts were not working properly. It will be very nice if someone with
| good knowledge of configure.in magic would take a look on this
| problem.

Jean-Marc, can you have a cursory glance at this? I am not sure if we
even need the AC_LANG_CPLUSPLUS there.

Lgb




Re: Cleaning up the menu entries.

2000-07-24 Thread Lars Gullik Bjønnes

"R. Lahaye" <[EMAIL PROTECTED]> writes:

| "Open" opens an existing document! Isn't a class/template already
| defined inside an existing document? Why must it popup a "New from
| Template"?

Why must "Open" open an existing document?

| Open:  Collapse "Open" and "Import". Open according to file
|extension: .lyx, .tex, .txt, .nw, .doc are opened as
|you expect.
|Does .txt input need a "as lines/as paragraph"
| popup?

No, "Import" should not be collapsed with "Open". They are really
different. We "Open " formats that we can read perfectly, and "Import"
formats where we might loose little/much information.

Lgb



Re: Cleaning up the menu entries.

2000-07-24 Thread Lars Gullik Bjønnes

Juergen Vigna <[EMAIL PROTECTED]> writes:

| So you always use "New from template..." and newer "New..."? Well I
| for myself 
| use a lot "article" textclass and do much more "New..." (without template)
| then "New from template", so I'm much faster with just a "New ..." menu where
| I don't have to click away the "Template-popup".

Who said that when we compine the "New" and "New from template" into
one item that you will always have to "click away" some extra pipup?
Of course part of the compining will be to have only _one_ popup
regardless of you wanting to use a template or not.

My vote is still for having only _one_ "New" entry.

Lgb



Re: New layout for the menus

2000-07-24 Thread Lars Gullik Bjønnes

Juergen Vigna <[EMAIL PROTECTED]> writes:

| > File->New // Collapse New and New_from_template. 
| >   // Use "invalid" filename; when saved, call 'Save as...' automatically. 
| >   // Should a window popup ask for Template/Class or assume a default for 
|that?
| 
| NO, NO, NO!
| 
| IMO we need "New..." AND "New from template..." !!!

I don't agree. And you _have_ managd with a popuå on both items in
several years now.

Lgb



Re: relyx broken?

2000-07-24 Thread Amir Karger

On Mon, Jul 24, 2000 at 10:30:12AM +0900, R. Lahaye wrote:
> Amir Karger wrote:
> > 
> > On Sat, Jul 22, 2000 at 02:45:29AM +0900, R. Lahaye wrote:
> > >
> > > /my/dir/my_file.tex: import failed. (buffer-import latex: [M-fil])
> > >
> > > Is this a bug?
> > 
> > Maybe.
>
> How can I more directly find out where reLyX is struggling when the
> import fails?

I guess the problem with Asger's writing Import->LaTeX functionality into
LyX is that people no longer realize that reLyX is its own program.

Run 'reLyX foo.tex' from the command line, and it'll create foo.lyx. If you
use -d, it will print out a whole lot of debugging information.

If you can get a smaller file to break, that would be easier to debug, but
if not, you can send me the large file & the output you get.

-Amir




Re: The new Toolbar and Menubar.

2000-07-24 Thread Angus Leeming

I've just checked out your code Jean-Marc with
cvs update
I've just compiled the code without any problem. However, running it I get the
message
Menubar::Pimpl::set: menubackend is empty! using default values.
With or without a document loaded there are only 3 items in the menubar, File,
Edit and Documents

Looking in lib/ I see that there is no ui/ directory so typing
cvs update -d
causes a new file to be uploaded
lib/scripts/fen2latex.py
but then the update terminates with
cvs [update aborted]: cannot open CVS/Entries.Log: No such file or directory

Repeating
cvs update -d
gives
cvs update: in directory lib/scripts:
cvs update: cannot open CVS/Entries for reading: No such file or directory
cvs server: Updating lib/scripts
cvs update: move away lib/scripts/fen2latex.py; it is in the way
C lib/scripts/fen2latex.py
cvs update: move away lib/scripts/fig2pstex.py; it is in the way
C lib/scripts/fig2pstex.py
cvs update: move away lib/scripts/general_command_wrapper.py; it is in the way
C lib/scripts/general_command_wrapper.py
U lib/scripts/pic2ascii.py
cvs [update aborted]: cannot open CVS/Entries.Log: No such file or directory

Finally I typed
cvs update -d lib/ui

This worked! However, I now worried that I'm missing something!
Angus

JMarc> OK, I have finally commited my work from this week end. A few random
notes:

JMarc> - Toolbar and menubar are in frontends, with implementation in
JMarc>   frontends/xforms. The external interface is GUI-indep. There may be
JMarc>   a way to use signals between the interface and the private
JMarc>   implementation, but I do not know how.

JMarc> - To see the new menubar at work, define NEW_MENUBAR in LyXView.C and
JMarc>   recompile. 

JMarc> - most of the menus work, except for Edit->Float, Edit->Table and a
JMarc>   few others for which I do not have lyxfuncs. I did not port Dekel's
JMarc>   TOC menu code either (Dekel, could you have a look in
JMarc>   frontends/xforms/Menubar_pimpl.C and see if you can do it?).

JMarc> - the menus and toolbar are defined in lib/ui/default.ui (actually the
JMarc>   name can be changed via lyxrc.ui_file). The toolbar is as before but
JMarc>   with different tokens (why the hell do we need the backslashes?).
JMarc>   For the menus... well, take a look and ask me if it is not clear.

JMarc> - There are still a couple of drawing problems. In particular, in some
JMarc>   situations, the shortcuts disappear from the menu bar unless you
JMarc>   move the mouse over it.

JMarc> - The shortcuts in menus are not aligned correctly. I have to look in
JMarc>   xforms code to see how it handles \t.

JMarc> JMarc



The new Toolbar and Menubar.

2000-07-24 Thread Jean-Marc Lasgouttes


OK, I have finally commited my work from this week end. A few random notes:

- Toolbar and menubar are in frontends, with implementation in
  frontends/xforms. The external interface is GUI-indep. There may be
  a way to use signals between the interface and the private
  implementation, but I do not know how.

- To see the new menubar at work, define NEW_MENUBAR in LyXView.C and
  recompile. 

- most of the menus work, except for Edit->Float, Edit->Table and a
  few others for which I do not have lyxfuncs. I did not port Dekel's
  TOC menu code either (Dekel, could you have a look in
  frontends/xforms/Menubar_pimpl.C and see if you can do it?).

- the menus and toolbar are defined in lib/ui/default.ui (actually the
  name can be changed via lyxrc.ui_file). The toolbar is as before but
  with different tokens (why the hell do we need the backslashes?).
  For the menus... well, take a look and ask me if it is not clear.

- There are still a couple of drawing problems. In particular, in some
  situations, the shortcuts disappear from the menu bar unless you
  move the mouse over it.

- The shortcuts in menus are not aligned correctly. I have to look in
  xforms code to see how it handles \t.

JMarc



Re: Toolbar does not work anymore!

2000-07-24 Thread Juergen Vigna


On 24-Jul-2000 Jean-Marc Lasgouttes wrote:
> 
> It may be an update problem (the buttons are disabled when there is no
> buffer, except for new and open, but may not be re-enabled later). Do
> you have a custom toolbar?

Yes I have a custom toolbar! But the buttons are not enabled from the
beginning (after loading the first file).

 Jürgen

--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450296
I-39100 Bozen   Web: http://www.sad.it/~jug

-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Life is like a 10 speed bicycle.  Most of us have gears we never use.
-- C. Schultz




Re: Cleaning up the menu entries.

2000-07-24 Thread Juergen Vigna


On 24-Jul-2000 R. Lahaye wrote:
> 
> Well, this is exactly my point, why I suggested to redesign the menu.
> Currently the menu has too many confusing options and overlaps:
> 

Well this has nothing to do with the menu-structure and I think we should
leave this function as is.

> 
> Along these lines I also advocate for example to remove the text-input area
> in "File->Open" and only let the user browse in the file system to select
> an *existing* file.

No! I'm still faster sometimes in typing a filename then search it in a long
list of files/directories (but this too is off the menu discussion).

  Jürgen


--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450296
I-39100 Bozen   Web: http://www.sad.it/~jug

-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

When the revolution comes, count your change.




Re: Toolbar does not work anymore!

2000-07-24 Thread Jean-Marc Lasgouttes

> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:

Juergen> Well the problem is that the toolbar still displays right but
Juergen> I can press only the first button (to the left!), all others
Juergen> are ignored.

It may be an update problem (the buttons are disabled when there is no
buffer, except for new and open, but may not be re-enabled later). Do
you have a custom toolbar?

JMarc



Re: Cleaning up the menu entries.

2000-07-24 Thread R. Lahaye

Juergen Vigna wrote:
> 
> >
> > I believe that "Open" should ONLY allow you to open an existing file,
> > whether that's lyx, latex, text, noweb or doc (extension sensitive!).
> > Don't make a "New from templates" also a hidden feature of "Open".
> 
> Why not let it be as it is now? If we don't find the file just ask the
> User if he wants to create a new one with that name, we could also add
> another button in the dialog
> 
> [Create] [Create from Template] [No]

Well, this is exactly my point, why I suggested to redesign the menu.
Currently the menu has too many confusing options and overlaps:

Why a [Create from template] under the "File->Open" entry when
there's already a "File->New from template"?
Why a [Create] under "File->Open" when we have already the "File->New"?
Why am I allowed (in the current layout) to open an existing document
under "New"?

To keep things clear and logical, there are two ways to go here:

1) Collapse *all* New/NewTemplate/Open entries into just one single entry.
   A "Open+New" in which you can select an existing document, type a new
   filename in the text area and have a [Create from Template] button as well.
   Hmm, that will cause some confusion, I bet.

2) Have separate buttons (as we have now), but that do EXACTLY what the say
   they should do.
   "New" creates a new document from scatch (with 'invalid' default filename)
   "New from template" does same, but pops up a template selection window
   "Open" lets you select an *existing* file, extension sensitive
  
Obviously I believe policy 2) is most clear, logical and easiest to learn.
Policy 1) or something in between creates too much confusion.

Along these lines I also advocate for example to remove the text-input area
in "File->Open" and only let the user browse in the file system to select
an *existing* file.


I'm sorry if I drive this discussion a bit too far, but I believe a
well designed menu is half the work to get a newbie acquainted with LyX.
I'm still newbie enough to remember my struggles when I tried to find
my way in the menu. My goal here is to tackle this unnecessary barrier.
I hope it's not bothering this list too much.

Regards,

Rob.



Re: Toolbar does not work anymore!

2000-07-24 Thread Juergen Vigna


On 24-Jul-2000 Jean-Marc Lasgouttes wrote:
> 
> No, but I might have changed the time where it is read... I have to
> admit that I did not test redefining the toolbar from configuration
> file. I will first commit the code I've been working on (still
> struggling with cxx) where I _did_ change the format. Then I'll have a
> look at yur problem.

Well the problem is that the toolbar still displays right but I can press
only the first button (to the left!), all others are ignored.

  Jürgen

--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450296
I-39100 Bozen   Web: http://www.sad.it/~jug

-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Ask not for whom the  tolls.




Re: Toolbar does not work anymore!

2000-07-24 Thread Jean-Marc Lasgouttes

> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:

Juergen> Hi! I just noticed that my toolbar does not work anymore!
Juergen> Could someone explain me what happend. I had a look at
Juergen> lyxrc.examples in the lib/ directory and it has still the
Juergen> same format I use for my .lyxrc-toolbar-defines.

Juergen> Jean-Marc did you change the format?

No, but I might have changed the time where it is read... I have to
admit that I did not test redefining the toolbar from configuration
file. I will first commit the code I've been working on (still
struggling with cxx) where I _did_ change the format. Then I'll have a
look at yur problem.

JMarc



Re: Cleaning up the menu entries.

2000-07-24 Thread Juergen Vigna

> 
> I believe that "Open" should ONLY allow you to open an existing file,
> whether that's lyx, latex, text, noweb or doc (extension sensitive!).
> Don't make a "New from templates" also a hidden feature of "Open".

Why not let it be as it is now? If we don't find the file just ask the
User if he wants to create a new one with that name, we could also add
another button in the dialog

[Create] [Create from Template] [No]

 Jürgen

--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450296
I-39100 Bozen   Web: http://www.sad.it/~jug

-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Anything is possible, unless it's not.




Re: Cleaning up the menu entries.

2000-07-24 Thread R. Lahaye

Allan Rae wrote:
> >
> > Open:  Collapse "Open" and "Import". Open according to file
> >extension: .lyx, .tex, .txt, .nw, .doc are opened as
> >you expect.
> >Does .txt input need a "as lines/as paragraph" popup?
> 
> If the file named doesn't exist the proceed as for
> "New from Template" using the filename supplied
> so long as it's a lyx file.
> P.S.  Still confused?

Hmm, is "Open an non-existing LyX file" then identical to "New from template"?

If so, the only difference is that "Open" you will result in a valid filename
for your new LyX document prior to choosing the template (whereas
"New from template" would assume an "invalid" filename, that forces a "Save as"
when saving). Right?

I believe that "Open" should ONLY allow you to open an existing file,
whether that's lyx, latex, text, noweb or doc (extension sensitive!).
Don't make a "New from templates" also a hidden feature of "Open".

A lot of confusion starts when menu items do more than what you expect.
So:
   let "Open" do just an *open*
   let "New from template" and "New" start a document from scratch.

Then menu items hardly need more explanation. It does what is says, not more
not less!

Regards,

Rob.



Re: Cleaning up the menu entries.

2000-07-24 Thread Allan Rae

On Mon, 24 Jul 2000, R. Lahaye wrote:

> Allan Rae wrote:
> > This then leaves us with a new "Open..." that can create a new named
> > document (emacs style) and which should/must popup the new "New from
> > Template..." popup.  (That is, the new "Open..." is really a slightly
> > better version of the old "New...")
> 
> "Open" opens an existing document! Isn't a class/template already
> defined inside an existing document? Why must it popup a "New from
> Template"?

An emacs-style "Open", as discussed earlier in this thread, allows you to
open a non-existent named file. In which case a "New from Template" would
be appropriate.  If the file already exists the file is opened.

> 
> Could the following layout be suitable:
> 
> File->New
>   New from template 
>   Open
>   ---
> [...]
> 
> 
> New:   Use "invalid" filename; when saved, call
>automatically 'Save as...'.
> 
> New from template: This should do, as you explained in earlier emails.
> 
> Open:  Collapse "Open" and "Import". Open according to file
>extension: .lyx, .tex, .txt, .nw, .doc are opened as
>you expect.
>Does .txt input need a "as lines/as paragraph" popup?

If the file named doesn't exist the proceed as for
"New from Template" using the filename supplied
so long as it's a lyx file.

Allan. (ARRae)

P.S.  Still confused?




set_color documentation mistake

2000-07-24 Thread Lior Silberman

When documenting the \set_color lyxrc command I forgot that strings in
lyxrc must be enclosed in quotes. I thus put in a misleading example.

The attached patch (again lyxdoc CVS) fixes this problem. I also
rearranged the table for the default colors.

Lior.

 set_color_doc.gz


Re: Cleaning up the menu entries.

2000-07-24 Thread R. Lahaye

Allan Rae wrote:
> This then leaves us with a new "Open..." that can create a new named
> document (emacs style) and which should/must popup the new "New from
> Template..." popup.  (That is, the new "Open..." is really a slightly
> better version of the old "New...")

"Open" opens an existing document! Isn't a class/template already
defined inside an existing document? Why must it popup a "New from
Template"?

Could the following layout be suitable:

File->New
  New from template 
  Open
  ---
[...]


New:   Use "invalid" filename; when saved, call
   automatically 'Save as...'.

New from template: This should do, as you explained in earlier emails.

Open:  Collapse "Open" and "Import". Open according to file
   extension: .lyx, .tex, .txt, .nw, .doc are opened as
   you expect.
   Does .txt input need a "as lines/as paragraph" popup?



Regards,

Rob.



Re: Cleaning up the menu entries.

2000-07-24 Thread Allan Rae

On Mon, 24 Jul 2000, Juergen Vigna wrote:

> So you always use "New from template..." and newer "New..."? Well I for myself
> use a lot "article" textclass and do much more "New..." (without template)
> then "New from template", so I'm much faster with just a "New ..." menu where
> I don't have to click away the "Template-popup".
> 
> Hopefully more clear now ;)

Yes.

You want a new "New..." that creates an empty unnamed document from the
default layout and/or template file.

Well we could do that and make a new "New from Template..." that does what
I wanted with a simple popup for selecting either a template file or a
document class.  The file can be unnamed here also.

This then leaves us with a need to handle unnamed documents (autosave,
emergency-save and save-as need to be handled).

This then leaves us with a new "Open..." that can create a new named
document (emacs style) and which should/must popup the new "New from
Template..." popup.  (That is, the new "Open..." is really a slightly
better version of the old "New...")

Confused you yet?
Allan. (ARRae)




Toolbar does not work anymore!

2000-07-24 Thread Juergen Vigna

Hi!

I just noticed that my toolbar does not work anymore! Could someone explain
me what happend. I had a look at lyxrc.examples in the lib/ directory and
it has still the same format I use for my .lyxrc-toolbar-defines.

Jean-Marc did you change the format?

 Jürgen

--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450296
I-39100 Bozen   Web: http://www.sad.it/~jug

-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

The explanation requiring the fewest assumptions is the most likely to be
correct.
-- William of Occam




RE: New layout for the menus

2000-07-24 Thread Juergen Vigna

>   
> 
> File->New // Collapse New and New_from_template. 
>   // Use "invalid" filename; when saved, call 'Save as...' automatically. 
>   // Should a window popup ask for Template/Class or assume a default for 
>that?

NO, NO, NO!

IMO we need "New..." AND "New from template..." !!!

>   Table->...  // Pops up the list of table-layout-functions (plus an 
>"open-table- 
>   // layout-window entry ?) when inside a table, otherwise greyed 
>out 

I don't like to have the open the popup-window here!

> 
> Layout->Character 
> Paragraph 
> Document 
> Paper 
> Quotes 

I would insert here (inseted of TabularLayout) something like

  TheLockingInset (find a better name but that is what it shoud do)

we then need a function in the insets which tells us if the_locking_inset
has a layout-window or not and so we can activate this on the actual locking
inset's layout menu!

Jürgen

--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450296
I-39100 Bozen   Web: http://www.sad.it/~jug

-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Chicken Little was right.




RE: tables typo?

2000-07-24 Thread Juergen Vigna


On 22-Jul-2000 Lior Silberman wrote:
> In current CVS, with NEW_INSETS defined to 1 (but NEW_TABULAR undefined),
> I found the following:
> 
> Method Buffer::writeFileAscii (buffer.C) has a variable called 'actcell'
> which is declared to be int* . Despite this, it is used in the following
> ways only:

> -   int * actcell = 0;
> +   int actcell = 0;

Very correct fix. Someone recently split up a int a, b, c, ... int
int a;
int b;
int c;
...

and introduced that bug ;)

I'll commit a change soon!

 Jürgen


--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450296
I-39100 Bozen   Web: http://www.sad.it/~jug

-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

If you just try long enough and hard enough, you can always manage to
boot yourself in the posterior.
-- A.J. Liebling, "The Press"




Re: Export to PDF and other formats

2000-07-24 Thread Jean-Marc Lasgouttes

> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:

>> Remove them. As far as I know, they were never used.

Dekel> Wrong. The dvi_to_ps_command lyxrc variable is used when a
Dekel> Postscript file is created.

To put it differently: I guess most people do not chenge them and are
pleased with the defaults found by lib/configure. So, as long as we
fix lib/configure, we should not care too much for the old commands.

JMarc



Re: Cleaning up the menu entries.

2000-07-24 Thread Juergen Vigna


On 24-Jul-2000 Allan Rae wrote:
> 
> I'm confused by the above sentence (perhaps it should be 5 sentences).
> Are you saying you think we should keep the "New.." and "New from
> template.." menu entries that we currently have?
> 

Was I that unclear!? I meant that I want to have a

New...[AND!!!]
New from template

menu items. Not only "New..." which is a composed New-New from template!

> If not,  then how do you propose to allow a user to select a template for
> their document?  I can't see how we can allow anyone to switch to a new
> template on an already existing document.
> 

That's what I thought too :)

> Maybe I'm not "most people" but I have 4 main document types I use:
> IEEETran, ieice, latex8 and letter (I also use article for writing
> sys-admin documentation for the local systems).  I would image that most
> academics (which I would think would constitute "most users of LyX") would
> have a similar collection of journal and conference paper layouts they
> use.  Switching layouts after a document is created is a pain.
> 

So you always use "New from template..." and newer "New..."? Well I for myself
use a lot "article" textclass and do much more "New..." (without template)
then "New from template", so I'm much faster with just a "New ..." menu where
I don't have to click away the "Template-popup".

Hopefully more clear now ;)

 Jürgen

--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450296
I-39100 Bozen   Web: http://www.sad.it/~jug

-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

I came to MIT to get an education for myself and a diploma for my mother.