On Sat, Jan 10, 2009 at 07:06:41PM +0100, Pavel Sanda wrote:
> Angus Leeming wrote:
> > We had one curmudgeonly gentleman, John Weiss, who point blank refused to
> > licence his contribution to LyX under the GPL version 2 or later. The old
> > flavour of this page has him
L or LGPL anything of mine. But even beforehand, I preferred to
release all of my code and documentation under the Artistic License.
Any contributions I made to LyX (early reLyX, documentation) should
therefore be considered as originally under the Artistic License.
Make of that what you will.
On Tue, Jan 25, 2005 at 09:30:45AM +, Angus Leeming wrote:
> John Weiss wrote:
>
> > On Fri, Jan 21, 2005 at 09:57:48PM +, Angus Leeming wrote:
> >> Cygwin's POSIX emulation layer avoids
> >> the need for the various workarounds required when using ot
> for.
And avoiding muddy code in a Unix-Windows-crossplatform program will
require a bit of work (in which I include careful planning). Which
was the whole point of those cautioning posts of mine.
--
John Weiss
the justification of an figure float
were tunable. (How easy it would be... I'd have to dig out my
dissertation and see if I'm even on the right track here, or if my
memory's flakey.)
--
John Weiss
> justified. IMHO of course.)
Seconded.
--
John Weiss
ugger is
related to "circuit breaker", the thing in your electric panel that
severs an electrical circuit pulling too many amps.
In short: calling a function "lyxbreaker" is a Bad Idea, as it
implies that this function somehow damages LyX. Better to call it
"lyxstopper" or "lyxbreakpt", the latter being far more descriptive if
its purpose.
--
John Weiss
On Tue, Jan 25, 2005 at 09:16:38AM +0100, Asger Ottar Alstrup wrote:
> John Weiss wrote:
> [A great opportunity to have a little flame-fest.]
You're the one attacking me out-of-hand.
> >Not FUD. Reality. [Long story about something irrelevant.]
> > Took them YEARS
element of "*argv[]". The single-quotes protected the
space from the shell. (I tested with bash, ash, csh, tcsh, ksh, and bsh.)
For Windows, however I wouldn't be surprised if whitespace chars
weren't escaped. Just another one of those platform differences
that'll need special handling.
--
John Weiss
ecl. in a file. Doing so makes a statement: Don't even
THINK of using another type of "fooXYZ" with this code! Putting in a
toplevel "using std::ostream;" tells future authors that no one, no
one at all, should even try to use anything but the STL ostream with
this code... put it in another source file and link the two together
instead!
Does that help at all, Andreas?
--
John Weiss
talking out his ass like Asger says I am!
--
John Weiss
-vis what you
mean by "justified paragraph", I might be able to explain what's going
on. (Maybe not, though, as I'm doing this from a laptop on a train.)
--
John Weiss
On Sat, Jan 22, 2005 at 09:50:51AM +0100, Andre Poenitz wrote:
> On Tue, Jan 18, 2005 at 07:36:36AM -0500, John Weiss wrote:
> > On Mon, Jan 17, 2005 at 02:09:33PM +0100, Lars Gullik Bjønnes wrote:
> > >
> > > I feel we are beginning on a slippery slope now... ok to su
up (possibly) requiring some
deep thought.
Have I *finally* made myself clear, Asger? Have I overexplained my
past experiences sufficiently enough that you won't jump all over me?
--
John Weiss
f platform-independence. ;)
> ...and the good news is that Qt provides a handle to do this and that we
> use it already.
...which brings me back to my earlier statement: we need to go
through a p.i.-layer, be it our own, or someone else's. ;)
--
John Weiss
d
> | declarations.
>
> :-)
>
> So its you that are the joy-killer now.
Decidedly mean, IMNSHO.
--
John Weiss
On Sat, Jan 22, 2005 at 03:30:44PM +0100, Asger Ottar Alstrup wrote:
> John Weiss wrote:
> >Doing true full-Windows support in an inherently-unix program is a
> >very thorny, messy situation.
>
> Have a look at the patch and then give your comments rather than this FUD.
N
pure Win-libs often requires odd
gymnastics... I could go on. Suffice it to say that it's enough to
keep a CompSci PhD fully employed at one place I used to work.
Best to keep things simple for now, as Lars says.
--
John Weiss
d in the 1.4 cycle.
Ain't it great to see the payoff? :)
--
John Weiss
Jamie Zawinsky: That's like banging two rocks
together and being proud that you've rederived fire from first
principles. It's a solved problem, and not worth revisiting.
--
John Weiss
x27;t make it invalid.
Long Live WYSIWYM!
So, it has its place. Needed to avoid too much ERT, which is such an
anathema these days.Since most users won't touch it most
of the time, that makes it a *perfect* candidate for the Extended.lyx
manual. [See? See? There *was* a method to my original design
madness! ;)]
--
John Weiss
On Thu, Jan 13, 2005 at 03:46:00AM +0100, Uwe Stöhr wrote:
> John Weiss wrote:
> >2. What the heck is a beamer?
> >
> >Just because you think it's the greatest-thing-since-sliced-bread
> >doesn't mean everyone else does. Or even knows it exists. (Your b
On Fri, Jan 14, 2005 at 10:09:29AM +0100, Lars Gullik Bjønnes wrote:
> John Weiss <[EMAIL PROTECTED]> writes:
>
> We (or I) do not want us to require a
> lot of ERT to make the printed doc look nice, if ERT is needed then we
> are missing features.
That was certainly the cas
On Thu, Jan 13, 2005 at 09:05:05AM +0100, Georg Baum wrote:
> John Weiss wrote:
>
> > 1. External LaTeX packages have no place in LyX.
>
> The question was not to include the LaTeX files, but the layout files.
>
> > 2. What the heck is a beamer?
>
> A very nic
sion" is that the core is almost just a library that the
> frontend calls into.
A Fine Idea. I approve wholeheartedly.
(Not that you needed my approval. ;) )
--
John Weiss
flicting each
others' goals. Remember, docs have a design, too. You'll need to
ignore those suggestions that conflict with the design.
Just like Lars has to reject patches that conflict with the code
design.
Fifth, I forget fifth. Vielleicht erinnere ich mich daran spïter...
--
John Weiss
t;, "ie" and "ey" can have
the same pronounciation, but "ee" and "ay" never do. :)
--
John Weiss
On Wed, Jan 12, 2005 at 05:20:49PM -0800, Jeremy C. Reed wrote:
> On Wed, 12 Jan 2005, John Weiss wrote:
>
> > Use a separate doc and include it via a master doc.
>
> I was thinking about that. Other than the book will have a lot of
> redundant information.
Yes, that i
On Thu, Jan 13, 2005 at 03:34:24AM +0100, Uwe Stöhr wrote:
> John Weiss wrote:
>
> >Doesn't follow a structured concept, eh?
> >Maybe you should read the mailling list archives before insulting me.
>
> Sorry I wouldn't harm anybody. I didn't know that there
On Thu, Jan 13, 2005 at 10:06:09AM +0100, Lars Gullik Bjønnes wrote:
> John Weiss <[EMAIL PROTECTED]> writes:
>
> | On Fri, Jan 07, 2005 at 05:18:23PM +0100, Lars Gullik Bjønnes wrote:
> >> Angus Leeming <[EMAIL PROTECTED]> writes:
> >>
> >
On Thu, Jan 13, 2005 at 10:07:27AM +0100, Jean-Marc Lasgouttes wrote:
> >>>>> "Uwe" == Uwe Stöhr <[EMAIL PROTECTED]> writes:
>
> Uwe> John Weiss wrote:
> >> Doesn't follow a strucutred concept, eh? Maybe you should read the
> >
press
> > key" ?
> >
> > Why would you "do Key"? What wrong has Key ever done to you?
Maybe Key thinks Andreas is cute...
> Maybe Key is of the opposite sex?
What's that got to do with it?
We're here! We're Queer! And we use LyX! :)
--
John Weiss
. And Amerrricans train their kids to be cruel.
> Maybe a typo for "Okay, do key" ? Can you say "do key" instead of
> "press key" ?
Also possible. Hand't thought of that, tho. ;)
--
John Weiss
inserted/deleted
preceeding/following text. Though, I tried to minimize those by using
manual linebreaks on text that went wonky in print.
--
John Weiss
1hr 30min. Hence the use of a laptop during the trip to/from
Manhattan.)
--
John Weiss
ver all
possible mathed features in the User's Guide precisely because of
scope. Better to move the more esoteric features into the Extended doc.
--
John Weiss
; special character ... to serve this very purpose.
Ignore online readability/navigability at your peril!
--
John Weiss
> >
> >I guess you don't mean the file that you can get via Help->LaTeX
> >Configuration?
>
> No I mean exactly this one.
In case no one's sent you theirs, I'm attaching the one from the laptop.
--
John Weiss
#LyX 1.3 created this file. For
ing::find_first_of() to search for the
1st '\0', then std::string::erase() from that point onward.
Granted, it's not ideal, but it accomplishes what you want, and avoids
the nasty reinterpret_cast<>()...
--
John Weiss
nd 'ispell'"
again to make sure you got them all.
(This is the very same technique I used 7 years ago. Very good
for such global doc-refactors.)
--
John Weiss
ing, Uwe!)
If it were really all that critical (like e.g. geometry.sty), it'd
already have integrated LyX support. If it's The Future, the devteam
will discover it soon enough...
--
John Weiss
suggestions didn't convey the proper connotations
to the wider audience of LyX users.
As much as we'd all love to have someone, anyone, updating the docs, I
have to play Lars here for a sec and ask: are you overdesigining? Do
we really need this-or-that feature you want to add?
A
l count for
> other spellchecker options. Don't know.
Hmm... now that I read this, it makes me think that, perhaps, the
details about the different flavors of spellchecker belong in
Customization.lyx
--
John Weiss
ut it doesn't jump from reference to reference.
> It jumps from one label to the next. So the menu name is a bit
> confusing. It should better have the name "Label".
And this is where your job as doc-editor comes in. ;) Describe
that thang!
--
John Weiss
line, or if mid-region
section-headings lose their paragraph style, then this is indeedy-deed
a bug introduced in v1.4CVS.
--
John Weiss
t might have sped up the installation...
>
> You are right, I dropped this now.
I think what you want to do instead, Uwe, is to add a chapter to
Customization roughly outlining what all of the different addons are,
by category, and why one might want them.
--
John Weiss
program"
exe $CMD `cygpath -aw "$@"`
Easy.
So, for Cygwin, we can just provide these wrappers and call them by
default instead.
--
John Weiss
dokee"
"Okie dokie"
"Okie-dokie"
"Ok, dokey" is an affirmative reply to someone named, "dokey". ;)
--
John Weiss
believe that a
> fair interpretation of intent is that the documentation is GPL.
>
> > I want to test a print-on-demand service. I want to submit the LyX
> > documentation in a single PDF format for a single book. Is this okay?
>
> I belive that would be ok, but you might t
since (I assume) we need Cygwin for the Win-version
of LyX.
--
John Weiss
ML, *then* we can
start deciding which parser we want. ;)
Playing around is fine, Lars. But, at some point, the playing around
grows too large and requires more formal planning. I think we've hit
that point w.r.t. LyX-XML. :)
--
John Weiss
tion run turns into 10,000,000 random numbers. Hit an
error at the end of the run, and you need to shlog through several
million valid tests to reproduce the one bug.
There are ways to deal with this, and I've always wanted to write a
generic framework for creating such tests. Just never had the
chance.
--
John Weiss
use it, for some tools and chains is
> a lot easier to go the tex way, as it is more mature and gives better
> results. Free tools to produce goof pdf,
I take it that "goof PDF" is a description of the current MathML
rendering state-of-the-art. ;)
--
John Weiss
... as in copying ... a file to a work directory just strikes
me as wasteful and prone to synchronization errors (have to check
which is newer, the true copy or the working copy). Is there some
problem with using a symlink?)
--
John Weiss
ke that, so it's certainly doable.
--
John Weiss
On Mon, Oct 25, 2004 at 10:11:18AM +0200, Jean-Marc Lasgouttes wrote:
>
> I guess I'll keep C-PageUp/Down for now.
This makes the most sense to me.
(I bind C-Tab and C-BackTab to the depth increment/decrement
commands, as they are in analogy to indenting.)
--
John Weiss
advantage of extensibility.
I say define anything that depends on environment ... like the
textclasses ... as simple string attributes. We can make exceptions
for *certain* textclasses ... like "Standard" ... that are pretty much
universal. Just my $0.02 worth.
--
John Weiss
transformation for now.
I feel that the structural loading/saving hints can be supplied via
attributes on the items or the surrounding list-defn.-tags.
Got hit with a bad cold, then had interviews all this week. I'll look
at the new DTD on the train tomorrow and try to come up with suggestions.
--
John Weiss
Mull it all over, guys. I'm away until next Wednesday. I'll read the
devel-list when I get back.
--
John Weiss
On Fri, Oct 08, 2004 at 08:28:12PM -0400, John Weiss wrote:
> On Fri, Oct 08, 2004 at 10:21:02PM +0200, Lars Gullik Bjønnes wrote:
> >
> > How do you decalre a namespace in a DTD?
Okay, just read up on XML namespaces.
- A namespace is uniquely identified by a URL. Doesn't
names into final
ones. But, ya gotta have da working structure, first.
> Let's see some code :-)
I just grabbed some online docs about XSchema. Let's decide first
what we wanna speak: DTD or XSchema? I'll whip up something based on
your example once we have a consensus...
--
John Weiss
definition, since it's one of your
> areas of expertise?
I'd love to, but first, I need to understand how the current LyX core
works. (Well, at least enough to know how LyX holds a document in
memory...).
--
John Weiss
On Fri, Oct 08, 2004 at 06:26:51PM +0200, Lars Gullik Bjønnes wrote:
> John Weiss <[EMAIL PROTECTED]> writes:
>
> | The DTD for an XML format (or, if you prefer, the XSchema for an XML
> | format) is like the header file for a C++ class. A file with "an XML
> | look&q
should think about it, especially once the
XMl-format branch stabilizes (and yes, I suggest branching & working
over there while we play around).
--
John Weiss
gt; Read Extended Features
> ^
> This is the DTD I hacked together, and it really shows how bad the
> current xml format is.
Kewl! Stuff to look at!
I'll get back to you on all of this.
--
John Weiss
Lars:
I've checked out the CVS head and built the doxygen srcdocs. I'm
still lost.
Can I have some hints on how "Buffer", "Paragraph", "Inset",
et. al. fit together? Some source files to look at? Where are the
*.lyx files written/read?
With those, I c
o "" tags. Granted, older versions of
LyX won't read docs from the new DTD, but that's to be expected. The
older versions of LyX, after all, have no idea what a "wynn" is.
In summary:
- You break nothing in older documents.
- You require no code modifications that you weren't already going to
make.
- You use all of XML's native parsing facilities to do the
heavy-lifting for you.
--
John Weiss
L look" is far, far, FAR easier to do from
within a DTD.
If you're uncomfortable with SGML DTD, then let's use XSchema.
XSchema, for those that don't know, is an XML document that defines
DTD's for other XML documents. Since it's all in XML, it's not as
"uncomfortable" for folks who don't know how to read the SGML DTD
language.
--
John Weiss
On Fri, Oct 08, 2004 at 08:47:32AM +0100, Angus Leeming wrote:
> John Weiss wrote:
>
> > I just built two binary RPM's for Fedora 2 (xforms UI and qt-3.3.3
> > UI). Where'd you like them uploaded?
>
> To ftp.devel.lyx.org/pub/incoming please.
Done.
You
I just built two binary RPM's for Fedora 2 (xforms UI and qt-3.3.3
UI). Where'd you like them uploaded?
--
John Weiss
ere, the command always parses to a single, known token. The
attributes serve to "pass parameters" to the command.
Note that these are just guidelines, not recommendations. I say that
we write the DTD first, figuring out what we need. Then, above
certain definitions, put comments labelled "REVIEW:" followed by
"maybe use entities?" or "maybe put in namespace?" etc. We can then
review the completed DTD and figure out the cleanest format.
--
John Weiss
relevant
packages on Mandrake & SuSe to get a list of library/binary names.
Apologies if I'm stating the obvious.
--
John Weiss
er M$ Word, whose output still looks like crap and with
which I have to struggle and fight just to get a consistent enumerated
list. And OpenOffice is more limited than Word, so the struggle is
worse there.
--
John Weiss, PhD in climate physics: 1998
too cryptic. However,
don't get too wordy. Dropdown menus that have unexpectedly huge
widths are also not very user-friendly.
--
John Weiss
within a sentence is not uncommon. If you're quoting
someone else, you'll likely run into a quote-in-a-quote. Thanks to
somebody's new "Feature," LyX can no longer handle this situation.
This is a problem.
--
John Weiss
is dynamic-abbreviation-expansion. But,
that's an Emacs feature; Word only has a crude version thereof.
--
John Weiss
On Fri, Oct 31, 2003 at 11:55:48PM -0500, John Weiss wrote:
> On Wed, Oct 29, 2003 at 01:51:14PM +0100, Christian Ridderström wrote:
> >
> > Quoting myself: "... Weiss's layout seems to work best at the moment."
> >
> > That probably refers to this layo
On Wed, Oct 29, 2003 at 08:57:30AM +, Jose' Matos wrote:
> On Wednesday 29 October 2003 08:55, Andre Poenitz wrote:
> > There is a prosper.layout from Dekel. Is there a specific reason we do
> > not distribute this?
>
> And also another from John Weiss.
> C
eiss.layout
>
Aroo? I don't recall making any layout called "prosper".
A CU-thesis one, yes. A resume one, yes. The SliTeX-support one,
sure.
I'll have to take a look at that link...
--
John Weiss
x27;s a protected space, or a "non-breaking space".
Those are the two standard terms.
--
John Weiss
"hold-down-Shift-and-move-cursor" paradigm for marking text...
--
John Weiss
of references. Hence the
"->" (which means dereference the thing to the left as a hash, and
the thing to the right as its key). The "${...}[$i]" is also
a dereference. It says, 'everything inside the curleys evaluates
to a reference to an array'.
--
John Weiss
t". The info-page for GNU-sort does not list "-u" as one of the
options that behaves differently under BSD or in non-POSIX
implementations. I'd guess, therefore, that "sort -u" is indeed
portable.
--
John Weiss
ew job (been laid off *again*), if I have to
commute by train, I'll buy a laptop so I can do some hobby programming
again during my commute...
--
John Weiss
On Mon, Oct 07, 2002 at 03:46:49PM +0200, Jean-Marc Lasgouttes wrote:
> >>>>> "John" == John Weiss <[EMAIL PROTECTED]> writes:
>
> John> Well, after upgrading to v1.2.x, I began the task of merging
> John> changes in with my local customization
cut; char-backward;
paste; char-forward;"
# Word-transpose [sorta]
\bind "M-t" "command-sequence word-forward-select; forward-select;
cut; word-backward; paste; word-forward;"
--
John Weiss
On Mon, Feb 04, 2002 at 04:55:07PM +0100, Asger K. Alstrup Nielsen wrote:
[snip]
Boy, folks, he sure doesn't speak up much anymore, but when he does say
something, he says a lot! ;)
--
John Weiss
uot; menu, ones for "OK", "Cancel", "Yes", and "No" buttons (if
these aren't built into GUITKs already) and one for "Quit LyX". This
way, a user with a broken installation can at least get help and quit.
--
John Weiss
/dev/i/kali < 'rm -rf /bin/laden'
d and readily
accessible. If I need to change a style document-wide, I'll do the
extra steps to say "apply this to the whole document." Don't
second-guess me or what I'm doing.
No software exists that can think for you. Any software that tries
will operate eratically.
--
John Weiss
nd that
they have neither." The only true guarantee of security is vigilance.
Be vigilant, my friends.
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
On Thu, Aug 09, 2001 at 11:34:44AM +0200, Lars Gullik Bjønnes wrote:
[snip!]
>
> and follow an implicit DTD.
That was my point. Any text-based file format follows an implicit DTD.
> John Weiss <[EMAIL PROTECTED]> writes:
>
> | We can do both design and DTD simultaneo
On Wed, Aug 08, 2001 at 12:22:21AM +0200, ben wrote:
> John Weiss a écrit :
>
> > Once we do design an XML-based LyX format, I suggest we document the
> > format using XSL. There's no magic around XSL: it's just an XML
> > document that uses a format desig
On Tue, Aug 07, 2001 at 10:17:58AM +0200, Lars Gullik Bjønnes wrote:
> John Weiss <[EMAIL PROTECTED]> writes:
>
> | Having recently done an XML seminar at work, I can offer the following
> | to the discussion:
[snip!]
> |
> | For "well-formed", thin
specify/support both syntactic and
contextual formats. And that's why the two flavors of MathML exist:
use only what makes sense for your application. And that's what LyX
should do. (See my other emails on this point.)
--
John Weiss
"Not through coercion. Not by force. But by compas
to convert from older to newer formats.
That would cut down on the amount of backward-compatibility code the
LyX kernel has to carry around, and will permit our users to convert
their older files without too much effort.
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
e document the
format using XSL. There's no magic around XSL: it's just an XML
document that uses a format designed for defining other XML formats.
I'll even volunteer to work on it (I'd like to improve my XML skills).
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
eavy-duty
mathed, and should scare up many lurking leaks.
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
ely ends up being more than a week ---
*much* more, in fact. Porting clean code is far, far simpler.
In the end, even if Lars ordered everyone to abandon GUII and work
exclusively on porting LyX over to ZYX-Toolkit, doing that port
cleanly would require most of the work they're doing now for GUII.
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
n send warning messages, too. So, we can inform
overeager patchers that their message was truncated/bounced, and that
they should ftp patches in to an appropriate location.
Ideas? Comments?
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a smal
he multibyte characters as well as what constitutes a
1-byte vs a multibyte char. (I'd have to check the Unicode book for
the details.)
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
1 - 100 of 318 matches
Mail list logo
