On 13-Dec-2001 Thomas Steffen wrote:
> You can still enter length as usual, the parser recognises it and sets
> the drop-down list accordingly.
I think we already somehow decided to adapt this solution (or a similar
one which also gives the power to insert stuff like 1cm+2em-4em).
> Since the
John Levon <[EMAIL PROTECTED]> writes:
> and for years, people have been forced to go to the manual to work out
^ some
> how to enter lengths. More recently, we have had a vague help message
> in some places.
Other people have entered length just as they always did.
> The new i
[EMAIL PROTECTED] wrote:
> My assumption would be that if it is a number, the existing units are
> used. If not, it would be parsed, and the units changed.
This is like I want it to behave too. I will have a look if and how
this can be done.
Juergen.
> hakw
On Wednesday 12 December 2001 2:42 pm, Andre Poenitz wrote:
> On Wed, Dec 12, 2001 at 09:20:56AM +, John Levon wrote:
> > nah, it should be tab navigatable like modern toolkits. even better
> > would have up/down in the text entry switch units.
>
> Just for the record: How difficult would it
Jean-Marc Lasgouttes wrote:
> > "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]>
> > writes:
>
> Juergen> Juergen Spitzmueller wrote:
> >> An alternative (if this is possible): Use length field and unit
> >> choice as is, but allow inserting values like "2cm" in the length
> >> field
On 12-Dec-2001 Juergen Spitzmueller wrote:
> Juergen Spitzmueller wrote:
>> An alternative (if this is possible):
>> Use length field and unit choice as is, but allow inserting values
>> like "2cm" in the length field (as it used to be). When the user
>> applies such a value, LyX sets the length
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Juergen Spitzmueller wrote:
>> An alternative (if this is possible): Use length field and unit
>> choice as is, but allow inserting values like "2cm" in the length
>> field (as it used to be). When the user applies such
Juergen Spitzmueller wrote:
> An alternative (if this is possible):
> Use length field and unit choice as is, but allow inserting values
> like "2cm" in the length field (as it used to be). When the user
> applies such a value, LyX sets the length correctly, inserts the
> length in the field and s
On Wed, Dec 12, 2001 at 09:20:56AM +, John Levon wrote:
> nah, it should be tab navigatable like modern toolkits. even better
> would have up/down in the text entry switch units.
Just for the record: How difficult would it be to switch over to some other
toolkit _right now_?
I am not proposi
Jean-Marc Lasgouttes wrote:
> John> ... and plus this, would be good. Sounds like a Juergen S thing
> John> to me :))
>
> I think JUergen mentionned it is over his competences. But all he
> needs is a gently push :) There is probably a nasty signal/slot
> problem to solve here. What would be nice
Jean-Marc Lasgouttes wrote:
> 1/ what Richark and dochawk said is certainly true. Being forced to
> use the mouse to enter lengths is not very nice. And even if xforms
> had keyboard support for choice widgets, it would remain a bit
> painful (remember you will need a different keyboard accellerat
On Wed, Dec 12, 2001 at 09:25:07AM +, Jules Bean wrote:
> And the .bind files could bind keys to command sequences, not just
> atomic commands.
They can partially already by using the 'command-sequence' hack...
Andre'
--
André Pönitz .. [EMAIL PR
On 12-Dec-2001 Jean-Marc Lasgouttes wrote:
> 2/ if there is a default unit, we could have a single text entry field
> where people could enter either '1', '1cm' '1cm+0.5in' or whatever.
> This is good for power users.
Well I think we need something in between. I like Garst's idea that we
have a
> "John" == John Levon <[EMAIL PROTECTED]> writes:
>> 1/ what Richark and dochawk said is certainly true. Being forced to
>> use the mouse to enter lengths is not very nice. And even if xforms
>> had keyboard support for choice widgets, it would remain a bit
>> painful (remember you will need
On Wed, Dec 12, 2001 at 09:22:40AM +, John Levon wrote:
> On Wed, Dec 12, 2001 at 09:19:35AM +, Jules Bean wrote:
>
> > Or just allow lyxfunc grouping. In emacs, it would look something
> > like this:
> >
> > ( (paragraph-general-set-alignment left)
> > (paragraph-general-set-pagebrea
On Wed, Dec 12, 2001 at 09:19:35AM +, Jules Bean wrote:
> Or just allow lyxfunc grouping. In emacs, it would look something
> like this:
>
> ( (paragraph-general-set-alignment left)
> (paragraph-general-set-pagebreaks above) )
>
> and lyx knows not to do any screen updates until I gets t
On Wed, Dec 12, 2001 at 10:17:16AM +0100, Lars Gullik Bjønnes wrote:
> John Levon <[EMAIL PROTECTED]> writes:
>
> | On Wed, Dec 12, 2001 at 08:50:04AM +, Jules Bean wrote:
> >
> >> IMO every dialog should, when OK or Apply has been clicked, call
> >> one or several LyXFuncs.
> >>
> >> So cli
On Wed, Dec 12, 2001 at 10:13:05AM +0100, Jean-Marc Lasgouttes wrote:
> Could it be that you are a bit grumpy today, John? %-]
oh, I admit it ;)
> >> I'm not sure what a glue lenght is. If it's in/cm/etc., it's the
> >> whole point; if not, I have no idea.
>
> John> I think this is a REALLY go
> "John" == John Levon <[EMAIL PROTECTED]> writes:
>> but now, the way that used to work, with much less effort, doesn't.
John> and ?
John> sorry, the lyx interface is not going to stagnate just because
John> you like it that way...
Could it be that you are a bit grumpy today, John? %-]
>
On Wed, Dec 12, 2001 at 08:50:04AM +, Jules Bean wrote:
> IMO every dialog should, when OK or Apply has been clicked, call
> one or several LyXFuncs.
>
> So clicking OK in paragraph might trigger:
>
> (paragraph-general-set-alignment left)
> (paragraph-general-set-pagebreaks above)
>
> or
On Wed, Dec 12, 2001 at 12:44:07AM +0100, Lars Gullik Bjønnes wrote:
> [EMAIL PROTECTED] writes:
>
> | the problem is that it is taking increasing amounts of user effort to
> | use lyx, and htis is a trend that has been continuing for some time. I
> | understand that UI and maintainability are
On Wed, 12 Dec 2001, John Levon wrote:
> Richard is not talking about accessibility. He is talking about keyboard interaction,
> and that is an xforms bug.
John, with all respect: Rule number one in usability is to listen to the
users.
Traditionally, LyX has gone to great lengths to work around
On Wed, Dec 12, 2001 at 02:18:17AM -0400, Garst R. Reese wrote:
> > I've just shown you several links that suggest GUIs and accessibility are not
> > inimiical to each other - why do you persist in saying otherwise ?
> I did not say that. In the words of your Gnome reference:
>
> 2.A large clas
On Tue, Dec 11, 2001 at 10:22:15PM -0400, Garst R. Reese wrote:
> John, I know the issues and problems of accessibility. I'm sure that you
> know that a key component is having everything accessible via
> key-strokes. Richard reminded you of that and you replied the good GUI
> design foremost.
I
On Tue, Dec 11, 2001 at 10:00:43PM -0400, Garst R. Reese wrote:
> To this I would like add, as a reminder that there are blind computer
> users, that the mouse for them is as useless as the GUI.
http://www.trolltech.com/developer/changes/3.0.0.html
http://developer.gnome.org/projects/gap/GNOME-A
On Tue, Dec 11, 2001 at 03:30:50PM -0500, [EMAIL PROTECTED] wrote:
> > and for years, people have been forced to go to the manual to work out
> > how to enter lengths. More recently, we have had a vague help message
> > in some places.
>
> but now, the way that used to work, with much less effor
On Tue, Dec 11, 2001 at 02:36:55PM -0500, [EMAIL PROTECTED] wrote:
> I don't see why this one is xforms. Foryears, we've been able to
> enter, ".5in", and have the program behave sensibly. It seems to me
> that this should still be parsed and the appropriate settings made.
and for years, peo
On Tue, Dec 11, 2001 at 12:44:43PM -0500, Richard E. Hawkins wrote:
> I understand that many people prefer the mouse, but the interface is
> becoming increasingly awkward to those of us that prefer the keyboard.
this is, in essence, an xforms bug as its keyboard navigation support is not good
28 matches
Mail list logo
