Re: AquaLyX screenshots

[Jürgen Spitzmüller]

Lizardo H.C.M.Nunes wrote:
 Is it possible to set icons for the command-sequence items in a  
 toolbar?

http://marc.info/?l=lyx-usersm=125570348223153w=2

Jürgen

Re: AquaLyX screenshots

[Jürgen Spitzmüller]

Lizardo H.C.M.Nunes wrote:
> Is it possible to set icons for the "command-sequence" items in a  
> toolbar?

http://marc.info/?l=lyx-users=125570348223153=2

Jürgen

AquaLyX screenshots

[Lizardo H . C . M . Nunes]

Is it possible to rebuild LyX and set the Big-sized as the only  
option?


Is it possible to set icons for the command-sequence items in a  
toolbar?


Thank you.


P.S.: Some screenshots:

http://www.lizardonunes.pro.br/xtra_images/LyX_TOC.tiff
http://www.lizardonunes.pro.br/xtra_images/LyX_ViewUpdate.tiff
http://www.lizardonunes.pro.br/xtra_images/LyX_Formulas.tiff
http://www.lizardonunes.pro.br/xtra_images/LyX_ViewSource.tiff







Lizardo H. C. M. Nunes
Professor Adjunto
DCNAT-Departamento de Ciências Naturais
UFSJ-Universidade Federal de São João del Rei
Phone/fax: +55 32 3379-2483
E-mail: lizardonu...@ufsj.edu.br
Website: www.lizardonunes.PRO.br

AquaLyX screenshots

[Lizardo H . C . M . Nunes]

Is it possible to rebuild LyX and set the "Big-sized" as the only  
option?


Is it possible to set icons for the "command-sequence" items in a  
toolbar?


Thank you.


P.S.: Some screenshots:

http://www.lizardonunes.pro.br/xtra_images/LyX_TOC.tiff
http://www.lizardonunes.pro.br/xtra_images/LyX_ViewUpdate.tiff
http://www.lizardonunes.pro.br/xtra_images/LyX_Formulas.tiff
http://www.lizardonunes.pro.br/xtra_images/LyX_ViewSource.tiff







Lizardo H. C. M. Nunes
Professor Adjunto
DCNAT-Departamento de Ciências Naturais
UFSJ-Universidade Federal de São João del Rei
Phone/fax: +55 32 3379-2483
E-mail: lizardonu...@ufsj.edu.br
Website: www.lizardonunes.PRO.br

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[John McCabe-Dansted]

On Sat, Jul 11, 2009 at 12:12 AM, Pavel Sanda sa...@lyx.org wrote:

   Would keycodes be useful for submitting manual bugs as well?
  
   some links to keys is a must. most of the bugs wouldn't be reachible
 just from
   the bakctrace and screenshot.
 
  I mean bugs that are manually found.  If we have the precise keycodes
  to reproduce it eliminates some possible ambiguities in the bug
  report,

 i think this is overengineering for normal bug reports

 and opens the possibility that these bugs could be
  automatically reproduced (e.g. for regression tests)

 Abdel tried to propose such kind of regression testing. if you feel like
 to be the main lyx regression tester, why not, but be warned that this will
 be mainly your project without much help from the others i guess... :)

 that said it would be actually good to have some automatical regression
 testing.


I was thinking that I could submit bug reports as regression tests. To
submit a *good* bug report requires various tasks:

- Checking which revision of svn we are using.
- Checking if I can reproduce with the latest version of SVN.
- Pasting in Arch/System/Locale type information
- Checking that the steps to reproduce actually work, that there are no
steps missed out.

It would be easier for me to write something like:

$ cat TestSelectInset.kt
KEYCODE=\Ca\[BackSpace]\Cmasdf\[Right]\D9\S\[Left]\D9X\Cs\D9
TEST=! grep asdf $F.lyx
DESC=r30414 unselects insets after a fraction of a second. 1.5.7 doesn't
exhibit this bug

Then I could get the computer to check that the steps are correct:

$ ly6 lyxtest_16x 
$ ly5 lyxtest_157 
$ ( F=lyxtest_16x ./do_regression_test.sh TestSelectInset.kt )
\begin_inset Formula $asdf$
FAIL: TestSelectInset.kt
$ ( F=lyxtest_157 ./do_regression_test.sh TestSelectInset.kt )
PASS: TestSelectInset.kt

Finally I could add TestSelectInset.kt to keytest, and let keytest handle
all the boring details.

Once FAIL: TestSelectInset.kt shows up in the keytest report, we could
move it to Trac. Alternatively if the bug is easy to fix, we could just fix
it. Then keytest could determine that a new svn revision was availiable, and
re-run the regression tests. Then somewhere in the report, keytest could add
a note like
   TestSelectInset.kt fixed by alice_w in r30999

This would have a few of downsides. E.g. people who rearrange the GUI would
fix a bunch of regressions and also break quite a few as well. These
things could be worked around, e.g. by having a regression2regression
script. It would be interesting to discover to what extent this work flow
would be useful.

FYI, here is do_regression_test.sh, although it just a proof of concept:

$ cat ./do_regression_test.sh
sendtext() {
  xvkbd -delay 50 -text $1 -xsendevent 2 /dev/null
}

wmctrl -R $F  (
 (. ./$1 # Load KEYCODE and TEST from file
  sendtext $KEYCODE
  if bash -c $TEST
  then
echo PASS: $1
  else
echo FAIL: $1
  fi
 )
)


-- 
John C. McCabe-Dansted
PhD Student
University of Western Australia

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[John McCabe-Dansted]

On Sat, Jul 11, 2009 at 12:12 AM, Pavel Sanda  wrote:

> > >> Would keycodes be useful for submitting manual bugs as well?
> > >
> > > some links to keys is a must. most of the bugs wouldn't be reachible
> just from
> > > the bakctrace and screenshot.
> >
> > I mean bugs that are manually found.  If we have the precise keycodes
> > to reproduce it eliminates some possible ambiguities in the bug
> > report,
>
> i think this is overengineering for normal bug reports
>
> >and opens the possibility that these bugs could be
> > automatically reproduced (e.g. for regression tests)
>
> Abdel tried to propose such kind of regression testing. if you feel like
> to be the main lyx regression tester, why not, but be warned that this will
> be mainly your project without much help from the others i guess... :)
>
> that said it would be actually good to have some automatical regression
> testing.


I was thinking that I could submit bug reports as regression tests. To
submit a *good* bug report requires various tasks:

- Checking which revision of svn we are using.
- Checking if I can reproduce with the latest version of SVN.
- Pasting in Arch/System/Locale type information
- Checking that the steps to reproduce actually work, that there are no
steps missed out.

It would be easier for me to write something like:

$ cat TestSelectInset.kt
KEYCODE="\Ca\[BackSpace]\Cmasdf\[Right]\D9\S\[Left]\D9X\Cs\D9"
TEST="! grep asdf $F.lyx"
DESC="r30414 unselects insets after a fraction of a second. 1.5.7 doesn't
exhibit this bug"

Then I could get the computer to check that the steps are correct:

$ ly6 lyxtest_16x &
$ ly5 lyxtest_157 &
$ ( F=lyxtest_16x ./do_regression_test.sh TestSelectInset.kt )
\begin_inset Formula $asdf$
FAIL: TestSelectInset.kt
$ ( F=lyxtest_157 ./do_regression_test.sh TestSelectInset.kt )
PASS: TestSelectInset.kt

Finally I could add TestSelectInset.kt to keytest, and let keytest handle
all the boring details.

Once "FAIL: TestSelectInset.kt" shows up in the keytest report, we could
move it to Trac. Alternatively if the bug is easy to fix, we could just fix
it. Then keytest could determine that a new svn revision was availiable, and
re-run the regression tests. Then somewhere in the report, keytest could add
a note like
   "TestSelectInset.kt fixed by alice_w in r30999"

This would have a few of downsides. E.g. people who rearrange the GUI would
"fix" a bunch of regressions and also "break" quite a few as well. These
things could be worked around, e.g. by having a regression2regression
script. It would be interesting to discover to what extent this work flow
would be useful.

FYI, here is do_regression_test.sh, although it just a proof of concept:

$ cat ./do_regression_test.sh
sendtext() {
  xvkbd -delay 50 -text "$1" -xsendevent 2> /dev/null
}

wmctrl -R "$F" && (
 (. "./$1" # Load KEYCODE and TEST from file
  sendtext "$KEYCODE"
  if bash -c "$TEST"
  then
echo PASS: $1
  else
echo FAIL: $1
  fi
 )
)


-- 
John C. McCabe-Dansted
PhD Student
University of Western Australia

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Abdelrazak Younes]

Pavel Sanda wrote:

Abdelrazak Younes wrote:
  
Thinking more about it, this lyxserver and the work John has been doing can 
be re-used to define automatic test cases for all our features.




i'm interested how you imagine such kind of _useful_ script. to test that
we don't crash on ctrl+n is kind of useless (i mean that crash vs non crash
is too harsh distinction.)
  


For example  we can test that a given sequence of LFUNs produces a lyx 
file that is identical to an archived lyx file on svn. So in my idea a 
test case would contain:
* an optional lyx file input in case the test is about a mutating 
sequence (eg: LFUN_BRANCHES_RENAME)

* an output reference lyx file that contains the desired result.
* a python (or shell but ideally python) script for the LFUN sequence 
and the diff between the generated file and the reference one.


Abdel.

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Pavel Sanda]

Abdelrazak Younes wrote:
 For example  we can test that a given sequence of LFUNs produces a lyx file 
 that is identical to an archived lyx file on svn. So in my idea a test case 
 would contain:
 * an optional lyx file input in case the test is about a mutating sequence 
 (eg: LFUN_BRANCHES_RENAME)
 * an output reference lyx file that contains the desired result.
 * a python (or shell but ideally python) script for the LFUN sequence and 
 the diff between the generated file and the reference one.

hmm this would be very fragile due to fileformat changes...
pavel

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Abdelrazak Younes]

Pavel Sanda wrote:

Abdelrazak Younes wrote:
  
For example  we can test that a given sequence of LFUNs produces a lyx file 
that is identical to an archived lyx file on svn. So in my idea a test case 
would contain:
* an optional lyx file input in case the test is about a mutating sequence 
(eg: LFUN_BRANCHES_RENAME)

* an output reference lyx file that contains the desired result.
* a python (or shell but ideally python) script for the LFUN sequence and 
the diff between the generated file and the reference one.



hmm this would be very fragile due to fileformat changes...
  


Or course an 'lyx2lyx *' could be added to the begining of the scripts. 
As an added bonus, this would then test lyx2lyx at the same time :-)


Abdel.

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Jean-Marc Lasgouttes]

Abdelrazak Younes you...@lyx.org writes:

 Or course an 'lyx2lyx *' could be added to the begining of the
 scripts. As an added bonus, this would then test lyx2lyx at the same
 time :-)

I think it is too strict.

JMarc

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Pavel Sanda]

John McCabe-Dansted wrote:
 I have made a new diff against the svn.
   http://gmatht.homelinux.net/xp/svn.diff

yep, i have commited it into trunk. keep the pacthes coming :)

  for bugs without this we should invent something another so we dont
  overpopulate bugzilla. maybe adding links into meta bug for keys test i 
  have added
  yestreday or something like that?
 
 I am thinking that if the bug reports are deficient it may be a good
 idea to improve the quality of the bugs keytest generates before
 worrying about them too much. It may also be good to still keep the
 bugs on the keytest side, so that I can make regression tests out of
 them

yes

  Would keycodes be useful for submitting manual bugs as well?
 
  some links to keys is a must. most of the bugs wouldn't be reachible just 
  from
  the bakctrace and screenshot.
 
 I mean bugs that are manually found.  If we have the precise keycodes
 to reproduce it eliminates some possible ambiguities in the bug
 report,

i think this is overengineering for normal bug reports

and opens the possibility that these bugs could be
 automatically reproduced (e.g. for regression tests)

Abdel tried to propose such kind of regression testing. if you feel like
to be the main lyx regression tester, why not, but be warned that this will
be mainly your project without much help from the others i guess... :)

that said it would be actually good to have some automatical regression testing.

 Keytest is now quite good at finding the smallest set of keys required
 to reproduce. Would it never-the-less be good to have core dumps?

if we have steps to reproduce then core dump is not much of use.

pavel

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Abdelrazak Younes]

Pavel Sanda wrote:

Abdelrazak Younes wrote:
  
Thinking more about it, this lyxserver and the work John has been doing can 
be re-used to define automatic test cases for all our features.




i'm interested how you imagine such kind of _useful_ script. to test that
we don't crash on ctrl+n is kind of useless (i mean that crash vs non crash
is too harsh distinction.)
  


For example  we can test that a given sequence of LFUNs produces a lyx 
file that is identical to an archived lyx file on svn. So in my idea a 
test case would contain:
* an optional lyx file input in case the test is about a mutating 
sequence (eg: LFUN_BRANCHES_RENAME)

* an output reference lyx file that contains the desired result.
* a python (or shell but ideally python) script for the LFUN sequence 
and the diff between the generated file and the reference one.


Abdel.

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Pavel Sanda]

Abdelrazak Younes wrote:
> For example  we can test that a given sequence of LFUNs produces a lyx file 
> that is identical to an archived lyx file on svn. So in my idea a test case 
> would contain:
> * an optional lyx file input in case the test is about a mutating sequence 
> (eg: LFUN_BRANCHES_RENAME)
> * an output reference lyx file that contains the desired result.
> * a python (or shell but ideally python) script for the LFUN sequence and 
> the diff between the generated file and the reference one.

hmm this would be very fragile due to fileformat changes...
pavel

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Abdelrazak Younes]

Pavel Sanda wrote:

Abdelrazak Younes wrote:
  
For example  we can test that a given sequence of LFUNs produces a lyx file 
that is identical to an archived lyx file on svn. So in my idea a test case 
would contain:
* an optional lyx file input in case the test is about a mutating sequence 
(eg: LFUN_BRANCHES_RENAME)

* an output reference lyx file that contains the desired result.
* a python (or shell but ideally python) script for the LFUN sequence and 
the diff between the generated file and the reference one.



hmm this would be very fragile due to fileformat changes...
  


Or course an 'lyx2lyx *' could be added to the begining of the scripts. 
As an added bonus, this would then test lyx2lyx at the same time :-)


Abdel.

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Jean-Marc Lasgouttes]

Abdelrazak Younes  writes:

> Or course an 'lyx2lyx *' could be added to the begining of the
> scripts. As an added bonus, this would then test lyx2lyx at the same
> time :-)

I think it is too strict.

JMarc

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Pavel Sanda]

John McCabe-Dansted wrote:
> I have made a new diff against the svn.
>   http://gmatht.homelinux.net/xp/svn.diff

yep, i have commited it into trunk. keep the pacthes coming :)

> > for bugs without this we should invent something another so we dont
> > overpopulate bugzilla. maybe adding links into meta bug for keys test i 
> > have added
> > yestreday or something like that?
> 
> I am thinking that if the bug reports are deficient it may be a good
> idea to improve the quality of the bugs keytest generates before
> worrying about them too much. It may also be good to still keep the
> bugs on the keytest side, so that I can make regression tests out of
> them

yes

> >> Would keycodes be useful for submitting manual bugs as well?
> >
> > some links to keys is a must. most of the bugs wouldn't be reachible just 
> > from
> > the bakctrace and screenshot.
> 
> I mean bugs that are manually found.  If we have the precise keycodes
> to reproduce it eliminates some possible ambiguities in the bug
> report,

i think this is overengineering for normal bug reports

>and opens the possibility that these bugs could be
> automatically reproduced (e.g. for regression tests)

Abdel tried to propose such kind of regression testing. if you feel like
to be the main lyx regression tester, why not, but be warned that this will
be mainly your project without much help from the others i guess... :)

that said it would be actually good to have some automatical regression testing.

> Keytest is now quite good at finding the smallest set of keys required
> to reproduce. Would it never-the-less be good to have core dumps?

if we have steps to reproduce then core dump is not much of use.

pavel

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Jean-Marc Lasgouttes]

John McCabe-Dansted gma...@gmail.com writes:
 We now calculate the smallest set of keys needed to cause the crash
 (we assume that if we cannot find a smaller set of keys within an
 hour, no such set exists)

I am impressed. 

JMarc

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Abdelrazak Younes]

Jean-Marc Lasgouttes wrote:

John McCabe-Dansted gma...@gmail.com writes:
  

We now calculate the smallest set of keys needed to cause the crash
(we assume that if we cannot find a smaller set of keys within an
hour, no such set exists)



I am impressed. 
  


Me too.

Thinking more about it, this lyxserver and the work John has been doing 
can be re-used to define automatic test cases for all our features.


We could even require that a new feature implement a test script from 
now on...


Abdel.

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Pavel Sanda]

Abdelrazak Younes wrote:
 We now calculate the smallest set of keys needed to cause the crash
 (we assume that if we cannot find a smaller set of keys within an
 hour, no such set exists)
 

 I am impressed.   

 Me too.

+1

 Thinking more about it, this lyxserver and the work John has been doing can 
 be re-used to define automatic test cases for all our features.


i'm interested how you imagine such kind of _useful_ script. to test that
we don't crash on ctrl+n is kind of useless (i mean that crash vs non crash
is too harsh distinction.)

pavel

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Jean-Marc Lasgouttes]

John McCabe-Dansted  writes:
> We now calculate the smallest set of keys needed to cause the crash
> (we assume that if we cannot find a smaller set of keys within an
> hour, no such set exists)

I am impressed. 

JMarc

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Abdelrazak Younes]

Jean-Marc Lasgouttes wrote:

John McCabe-Dansted  writes:
  

We now calculate the smallest set of keys needed to cause the crash
(we assume that if we cannot find a smaller set of keys within an
hour, no such set exists)



I am impressed. 
  


Me too.

Thinking more about it, this lyxserver and the work John has been doing 
can be re-used to define automatic test cases for all our features.


We could even require that a new feature implement a test script from 
now on...


Abdel.

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Pavel Sanda]

Abdelrazak Younes wrote:
>>> We now calculate the smallest set of keys needed to cause the crash
>>> (we assume that if we cannot find a smaller set of keys within an
>>> hour, no such set exists)
>>> 
>>
>> I am impressed.   
>
> Me too.

+1

> Thinking more about it, this lyxserver and the work John has been doing can 
> be re-used to define automatic test cases for all our features.


i'm interested how you imagine such kind of _useful_ script. to test that
we don't crash on ctrl+n is kind of useless (i mean that crash vs non crash
is too harsh distinction.)

pavel

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[John McCabe-Dansted]

I have made a new diff against the svn.
  http://gmatht.homelinux.net/xp/svn.diff
(or)
  http://www.ucc.asn.au/~mccabedj/svn.diff.gz
and there is an example of the new output up at:
  http://gmatht.homelinux.net/xp/out/html/indexreport.html

On Thu, Jun 18, 2009 at 2:06 AM, Pavel Sandasa...@lyx.org wrote:
 FYI, These crash reports are from r30112.

 this is aesthetically beautiful, but the main thing still missing - some 
 reference
 to keys which caused this.

We now calculate the smallest set of keys needed to cause the crash
(we assume that if we cannot find a smaller set of keys within an
hour, no such set exists)

 Would adding links from text like LyX.cpp:7 to things like:
 http://www.lyx.org/trac/browser/lyx-devel/branches/BRANCH_1_6_X/COPYING?rev=27418#L7
 also be useful?

 it wouldn't hurt, yes.

Done, more or less. See output.
  http://gmatht.homelinux.net/xp/out/html/indexreport.html

 It occurs if you spell check inside a math macro, and then hit
 replace. The thing I find amusing is that the spell-checker dialog is
 blank so the correct thing for LyX to do would be to replace  with
 , something no real human would ever actually want to do. If humans
 do want to do this, they are not the sort that fix bugs, since I can
 reproduce this in 1.5.7.

 we shouldn't crash anyway. for bugs you know howto reproduce just fill crash
 bug report.

I filled this one out.

 for bugs without this we should invent something another so we dont
 overpopulate bugzilla. maybe adding links into meta bug for keys test i have 
 added
 yestreday or something like that?

I am thinking that if the bug reports are deficient it may be a good
idea to improve the quality of the bugs keytest generates before
worrying about them too much. It may also be good to still keep the
bugs on the keytest side, so that I can make regression tests out of
them

 Would keycodes be useful for submitting manual bugs as well?

 some links to keys is a must. most of the bugs wouldn't be reachible just from
 the bakctrace and screenshot.

I mean bugs that are manually found.  If we have the precise keycodes
to reproduce it eliminates some possible ambiguities in the bug
report, and opens the possibility that these bugs could be
automatically reproduced (e.g. for regression tests)

Keytest is now quite good at finding the smallest set of keys required
to reproduce. Would it never-the-less be good to have core dumps?

-- 
John C. McCabe-Dansted
PhD Student
University of Western Australia

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Vincent van Ravesteijn]

John McCabe-Dansted schreef:

I have made a new diff against the svn.
  http://gmatht.homelinux.net/xp/svn.diff
(or)
  http://www.ucc.asn.au/~mccabedj/svn.diff.gz
and there is an example of the new output up at:
  http://gmatht.homelinux.net/xp/out/html/indexreport.html
  


Thanks,

I can now reproduce bug #5998.

Vincent

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Vincent van Ravesteijn]

John McCabe-Dansted schreef:

I have made a new diff against the svn.
  http://gmatht.homelinux.net/xp/svn.diff
(or)
  http://www.ucc.asn.au/~mccabedj/svn.diff.gz
and there is an example of the new output up at:
  http://gmatht.homelinux.net/xp/out/html/indexreport.html
  

I could reproduce all bugs manually:

First 2 : #6013
Next 1: #6063
Next 3: #6003
Next 4: #6064
Next 3: #5998 (fixed)

Vincent

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[John McCabe-Dansted]

I have made a new diff against the svn.
  http://gmatht.homelinux.net/xp/svn.diff
(or)
  http://www.ucc.asn.au/~mccabedj/svn.diff.gz
and there is an example of the new output up at:
  http://gmatht.homelinux.net/xp/out/html/indexreport.html

On Thu, Jun 18, 2009 at 2:06 AM, Pavel Sanda wrote:
>> FYI, These crash reports are from r30112.
>
> this is aesthetically beautiful, but the main thing still missing - some 
> reference
> to keys which caused this.

We now calculate the smallest set of keys needed to cause the crash
(we assume that if we cannot find a smaller set of keys within an
hour, no such set exists)

>> Would adding links from text like "LyX.cpp:7" to things like:
>> http://www.lyx.org/trac/browser/lyx-devel/branches/BRANCH_1_6_X/COPYING?rev=27418#L7
>> also be useful?
>
> it wouldn't hurt, yes.

Done, more or less. See output.
  http://gmatht.homelinux.net/xp/out/html/indexreport.html

>> It occurs if you spell check inside a math macro, and then hit
>> replace. The thing I find amusing is that the spell-checker dialog is
>> blank so the "correct" thing for LyX to do would be to replace "" with
>> "", something no real human would ever actually want to do. If humans
>> do want to do this, they are not the sort that fix bugs, since I can
>> reproduce this in 1.5.7.
>
> we shouldn't crash anyway. for bugs you know howto reproduce just fill crash
> bug report.

I filled this one out.

> for bugs without this we should invent something another so we dont
> overpopulate bugzilla. maybe adding links into meta bug for keys test i have 
> added
> yestreday or something like that?

I am thinking that if the bug reports are deficient it may be a good
idea to improve the quality of the bugs keytest generates before
worrying about them too much. It may also be good to still keep the
bugs on the keytest side, so that I can make regression tests out of
them

>> Would keycodes be useful for submitting manual bugs as well?
>
> some links to keys is a must. most of the bugs wouldn't be reachible just from
> the bakctrace and screenshot.

I mean bugs that are manually found.  If we have the precise keycodes
to reproduce it eliminates some possible ambiguities in the bug
report, and opens the possibility that these bugs could be
automatically reproduced (e.g. for regression tests)

Keytest is now quite good at finding the smallest set of keys required
to reproduce. Would it never-the-less be good to have core dumps?

-- 
John C. McCabe-Dansted
PhD Student
University of Western Australia

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Vincent van Ravesteijn]

John McCabe-Dansted schreef:

I have made a new diff against the svn.
  http://gmatht.homelinux.net/xp/svn.diff
(or)
  http://www.ucc.asn.au/~mccabedj/svn.diff.gz
and there is an example of the new output up at:
  http://gmatht.homelinux.net/xp/out/html/indexreport.html
  


Thanks,

I can now reproduce bug #5998.

Vincent

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Vincent van Ravesteijn]

John McCabe-Dansted schreef:

I have made a new diff against the svn.
  http://gmatht.homelinux.net/xp/svn.diff
(or)
  http://www.ucc.asn.au/~mccabedj/svn.diff.gz
and there is an example of the new output up at:
  http://gmatht.homelinux.net/xp/out/html/indexreport.html
  

I could reproduce all bugs manually:

First 2 : #6013
Next 1: #6063
Next 3: #6003
Next 4: #6064
Next 3: #5998 (fixed)

Vincent

Keytest: Screenshots of Crashes, Samples and Patch.

[John McCabe-Dansted]

OK. I have changed keytest so that it splits out all the KEYCODES. I
can't reproduce anything at the moment, I imagine that I'll have to
play with the -delay parameter of xvkbd so keypresses don't randomly
go missing.

I have attached a patch. The patch isn't pretty, but the code wasn't
that pretty to begin with.

On the other hand, would screenshots help? Here is some example output
with screenshots taken the moment LyX crashes

http://www.ucc.asn.au/~mccabedj/kt/indexreport.html
http://www.ucc.asn.au/~mccabedj/keytest_html_out.tar.gz
http://www.ucc.asn.au/~mccabedj/kt/

FYI, These crash reports are from r30112.

Some of the screenshots in the middle are corrupted. I think that was
because VirtualBox was minimized.

Would adding links from text like LyX.cpp:7 to things like:
http://www.lyx.org/trac/browser/lyx-devel/branches/BRANCH_1_6_X/COPYING?rev=27418#L7
also be useful?

One bug I found amusing  was this one:
http://www.ucc.asn.au/~mccabedj/kt/1245228432.html

It occurs if you spell check inside a math macro, and then hit
replace. The thing I find amusing is that the spell-checker dialog is
blank so the correct thing for LyX to do would be to replace  with
, something no real human would ever actually want to do. If humans
do want to do this, they are not the sort that fix bugs, since I can
reproduce this in 1.5.7.

Can also be repoduced by typing
  sleep 2; xvkbd -text \Afn\Cm\Ats\Ar -xsendevent  -delay 111
and selecting the a new blank lyx window quickly

Would keycodes be useful for submitting manual bugs as well?

-- 
John C. McCabe-Dansted
PhD Student
University of Western Australia
Index: lyx_make.sh
===
--- lyx_make.sh	(revision 30129)
+++ lyx_make.sh	(working copy)
@@ -14,14 +14,14 @@
 if which wmctrl xvkbd bash xterm python
 then 
 
- if [ a$1 == a--update ]; then
-  svn up
+ if [ a$1 == a--update ]; then
+#  svn up
   ./autogen.sh  ./configure --enable-debug --  nice -18 make  (bash $LT/autolyx  sleep 9 ; xterm -e python $LT/test.py)
  else
   DBG=`src/lyx --version 21 | grep C++.Compiler.flags|grep -- -g`;
   if [ -z $DBG ]; then echo Wrong build of LyX binary. ; exit; fi
 
-  bash $LT/autolyx  sleep 9 ; xterm -e python $LT/test.py
+  #bash $LT/autolyx  sleep 9 ; xterm -e python $LT/test.py
  fi
 
 else
Index: killtest.sh
===
--- killtest.sh	(revision 30129)
+++ killtest.sh	(working copy)
@@ -1,14 +1,17 @@
 AUTOLYX=`ps gaux | grep autolyx | grep -v grep | sed 's/[^ ]* //' | sed s/0.0.*//g`
+TESTPY=`ps gaux | grep test.py | grep -v grep | sed 's/[^ ]* //' | sed s/0.0.*//g`
 killall autolyx
 killall test.py
 killall lyx
 killall gdb
 killall xterm
-kill $AUTOLYX
+killall replay.sh
+kill $AUTOLYX $TESTPY
 sleep 0.3
 killall autolyx -9
 killall test.py -9
 killall lyx -9
 killall gdb -9
 killall xterm -9
-kill $AUTOLYX -9
+killall replay.sh -9
+kill $AUTOLYX $TESTPY -9
Index: report.sh
===
--- report.sh	(revision 30129)
+++ report.sh	(working copy)
@@ -14,7 +14,7 @@
   fi
 done
 
-strings $LT/out/GDB  $LT/out/GDBs 
+strings $LT/out/*GDB  $LT/out/GDBs 
 grep #$UNIQUE_LINE  $LT/out/GDBs  $LT/out/list
 #cat $LT/out/list | grep -o ' in [[:alnum:]:]* ' | sort | uniq| tee $LT/out/listuniq
 #cat $LT/out/list | grep -o ' in [[:alnum:]:]* ' | sort | uniq| tee $LT/out/listuniq
Index: autolyx
===
--- autolyx	(revision 30129)
+++ autolyx	(working copy)
@@ -2,15 +2,66 @@
 # This script starts LyX, and restarts LyX if it is closed
 # it logs all output, including backtraces to development/keystest/out/GDB
 
+#Setting the following may give better screen shots
+#gconftool-2 /apps/metacity/general/compositing_manager -s -t bool true
+
 #rename other windows to avoid confusion.
+
+
+
+
+DIRNAME0=`dirname $0`
+OUTDIR=$DIRNAME0/out
+
 wmctrl -N __renamed__ -r lyx
 wmctrl -N __renamed__ -r lyx
 wmctrl -N __renamed__ -r lyx
 wmctrl -N __renamed__ -r lyx
 
+(
 while true
 do
-  ( (echo SECONDS: `date +%s`
-	(echo run
-  bt ; yes q) | gdb src/lyx 21) | strings|  tee -a development/keystest/out/GDB)
+  SEC=`date +%s`
+  GDB=$OUTDIR/$SEC.GDB
+  KEYCODE=$OUTDIR/$SEC.KEYCODE
+  ( sleep 20  python $DIRNAME0/test.py | tee $KEYCODE) 
+  CHILD_PID=$!
+  ls src/lyx ; sleep 1
+   pwd
+  #sleep 10
+  
+  #You may want to use the following to simulate SIGFPE
+  #(sleep 90  killall -8 lyx) 
+
+  (echo 
+  shell svn info src/
+  run
+  bt
+  shell kill $CHILD_PID
+  shell import -window root '$GDB.png'
+  shell wmctrl -l
+  shell sleep 1
+  shell kill -9 $CHILD_PID
+  shell wmctrl -r __renamed__ -b add,shaded
+  shell wmctrl -r term -b add,shaded
+  shell wmctrl -r term -b add,shaded
+  shell wmctrl -R lyx 
+  shell import -window root '$GDB..png'
+  ; yes q) | gdb src/lyx 21 | strings|  tee $GDB
+  kill $CHILD_PID
+  #sleep 2 kill -9 $CHILD_PID
+  grep  signal  $GDB

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[John McCabe-Dansted]

On Thu, Jun 18, 2009 at 12:22 AM, John McCabe-Danstedgma...@gmail.com wrote:
 I have attached a patch. The patch isn't pretty, but the code wasn't
 that pretty to begin with.

I just noticed a few minor errors in the patch.
  www.ucc.asn.au/~mccabedj/keytest2.diff
is more correct.

I was thinking that this might be useful to other projects too. For
example, I managed to trigger a SIGSEGV in krisk, a Risk like game.
Does this change anything? I am happy to leave it in the LyX svn tree.


-- 
John C. McCabe-Dansted
PhD Student
University of Western Australia

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Pavel Sanda]

John McCabe-Dansted wrote:
 On Thu, Jun 18, 2009 at 12:22 AM, John McCabe-Danstedgma...@gmail.com wrote:
  I have attached a patch. The patch isn't pretty, but the code wasn't
  that pretty to begin with.
 
 I just noticed a few minor errors in the patch.
   www.ucc.asn.au/~mccabedj/keytest2.diff
 is more correct.

i'll commit this into the tree. i'm leaving soon for a week or two
out of net so i'll coment on the rest later, sorry.

pavel

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Pavel Sanda]

John McCabe-Dansted wrote:

ok i was too curious ... ;)

 On the other hand, would screenshots help? Here is some example output
 with screenshots taken the moment LyX crashes
 
 http://www.ucc.asn.au/~mccabedj/kt/indexreport.html
 http://www.ucc.asn.au/~mccabedj/keytest_html_out.tar.gz
 http://www.ucc.asn.au/~mccabedj/kt/
 
 FYI, These crash reports are from r30112.

this is aesthetically beautiful, but the main thing still missing - some 
reference
to keys which caused this.


 Would adding links from text like LyX.cpp:7 to things like:
 http://www.lyx.org/trac/browser/lyx-devel/branches/BRANCH_1_6_X/COPYING?rev=27418#L7
 also be useful?

it wouldn't hurt, yes.

 It occurs if you spell check inside a math macro, and then hit
 replace. The thing I find amusing is that the spell-checker dialog is
 blank so the correct thing for LyX to do would be to replace  with
 , something no real human would ever actually want to do. If humans
 do want to do this, they are not the sort that fix bugs, since I can
 reproduce this in 1.5.7.

we shouldn't crash anyway. for bugs you know howto reproduce just fill crash 
bug report. for bugs without this we should invent something another so we dont
overpopulate bugzilla. maybe adding links into meta bug for keys test i have 
added
yestreday or something like that?

 Would keycodes be useful for submitting manual bugs as well?

some links to keys is a must. most of the bugs wouldn't be reachible just from
the bakctrace and screenshot.

thank for your effort.
pavel

Keytest: Screenshots of Crashes, Samples and Patch.

[John McCabe-Dansted]

OK. I have changed keytest so that it splits out all the KEYCODES. I
can't reproduce anything at the moment, I imagine that I'll have to
play with the -delay parameter of xvkbd so keypresses don't randomly
go missing.

I have attached a patch. The patch isn't pretty, but the code wasn't
that pretty to begin with.

On the other hand, would screenshots help? Here is some example output
with screenshots taken the moment LyX crashes

http://www.ucc.asn.au/~mccabedj/kt/indexreport.html
http://www.ucc.asn.au/~mccabedj/keytest_html_out.tar.gz
http://www.ucc.asn.au/~mccabedj/kt/

FYI, These crash reports are from r30112.

Some of the screenshots in the middle are corrupted. I think that was
because VirtualBox was minimized.

Would adding links from text like "LyX.cpp:7" to things like:
http://www.lyx.org/trac/browser/lyx-devel/branches/BRANCH_1_6_X/COPYING?rev=27418#L7
also be useful?

One bug I found amusing  was this one:
http://www.ucc.asn.au/~mccabedj/kt/1245228432.html

It occurs if you spell check inside a math macro, and then hit
replace. The thing I find amusing is that the spell-checker dialog is
blank so the "correct" thing for LyX to do would be to replace "" with
"", something no real human would ever actually want to do. If humans
do want to do this, they are not the sort that fix bugs, since I can
reproduce this in 1.5.7.

Can also be repoduced by typing
  sleep 2; xvkbd -text "\Afn\Cm\Ats\Ar" -xsendevent  -delay 111
and selecting the a new blank lyx window quickly

Would keycodes be useful for submitting manual bugs as well?

-- 
John C. McCabe-Dansted
PhD Student
University of Western Australia
Index: lyx_make.sh
===
--- lyx_make.sh	(revision 30129)
+++ lyx_make.sh	(working copy)
@@ -14,14 +14,14 @@
 if which wmctrl xvkbd bash xterm python
 then 
 
- if [ a"$1" == a--update ]; then
-  svn up
+ if [ a"$1" == "a--update" ]; then
+#  svn up
   ./autogen.sh && ./configure --enable-debug -- && nice -18 make && (bash $LT/autolyx & sleep 9 ; xterm -e python $LT/test.py)
  else
   DBG=`src/lyx --version 2>&1 | grep C++.Compiler.flags|grep -- -g`;
   if [ -z "$DBG" ]; then echo Wrong build of LyX binary. ; exit; fi
 
-  bash $LT/autolyx & sleep 9 ; xterm -e python $LT/test.py
+  #bash $LT/autolyx & sleep 9 ; xterm -e python $LT/test.py
  fi
 
 else
Index: killtest.sh
===
--- killtest.sh	(revision 30129)
+++ killtest.sh	(working copy)
@@ -1,14 +1,17 @@
 AUTOLYX=`ps gaux | grep autolyx | grep -v grep | sed 's/[^ ]* //' | sed s/0.0.*//g`
+TESTPY=`ps gaux | grep test.py | grep -v grep | sed 's/[^ ]* //' | sed s/0.0.*//g`
 killall autolyx
 killall test.py
 killall lyx
 killall gdb
 killall xterm
-kill $AUTOLYX
+killall replay.sh
+kill $AUTOLYX $TESTPY
 sleep 0.3
 killall autolyx -9
 killall test.py -9
 killall lyx -9
 killall gdb -9
 killall xterm -9
-kill $AUTOLYX -9
+killall replay.sh -9
+kill $AUTOLYX $TESTPY -9
Index: report.sh
===
--- report.sh	(revision 30129)
+++ report.sh	(working copy)
@@ -14,7 +14,7 @@
   fi
 done
 
-strings $LT/out/GDB > $LT/out/GDBs 
+strings $LT/out/*GDB > $LT/out/GDBs 
 grep "#$UNIQUE_LINE " $LT/out/GDBs > $LT/out/list
 #cat $LT/out/list | grep -o ' in [[:alnum:]:]* ' | sort | uniq| tee $LT/out/listuniq
 #cat $LT/out/list | grep -o ' in [[:alnum:]:]* ' | sort | uniq| tee $LT/out/listuniq
Index: autolyx
===
--- autolyx	(revision 30129)
+++ autolyx	(working copy)
@@ -2,15 +2,66 @@
 # This script starts LyX, and restarts LyX if it is closed
 # it logs all output, including backtraces to development/keystest/out/GDB
 
+#Setting the following may give better screen shots
+#gconftool-2 /apps/metacity/general/compositing_manager -s -t bool true
+
 #rename other windows to avoid confusion.
+
+
+
+
+DIRNAME0=`dirname "$0"`
+OUTDIR="$DIRNAME0/out"
+
 wmctrl -N __renamed__ -r lyx
 wmctrl -N __renamed__ -r lyx
 wmctrl -N __renamed__ -r lyx
 wmctrl -N __renamed__ -r lyx
 
+(
 while true
 do
-  ( (echo SECONDS: `date +%s`
-	(echo "run
-  bt" ; yes q) | gdb src/lyx 2>&1) | strings|  tee -a development/keystest/out/GDB)
+  SEC=`date +%s`
+  GDB=$OUTDIR/$SEC.GDB
+  KEYCODE=$OUTDIR/$SEC.KEYCODE
+  ( sleep 20 && python $DIRNAME0/test.py | tee $KEYCODE) &
+  CHILD_PID="$!"
+  ls src/lyx ; sleep 1
+   pwd
+  #sleep 10
+  
+  #You may want to use the following to simulate SIGFPE
+  #(sleep 90 && killall -8 lyx) &
+
+  (echo "
+  shell svn info src/
+  run
+  bt
+  shell kill $CHILD_PID
+  shell import -window root '$GDB.png'
+  shell wmctrl -l
+  shell sleep 1
+  shell kill -9 $CHILD_PID
+  shell wmctrl -r __renamed__ -b add,s

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[John McCabe-Dansted]

On Thu, Jun 18, 2009 at 12:22 AM, John McCabe-Dansted wrote:
> I have attached a patch. The patch isn't pretty, but the code wasn't
> that pretty to begin with.

I just noticed a few minor errors in the patch.
  www.ucc.asn.au/~mccabedj/keytest2.diff
is more correct.

I was thinking that this might be useful to other projects too. For
example, I managed to trigger a SIGSEGV in krisk, "a Risk like" game.
Does this change anything? I am happy to leave it in the LyX svn tree.


-- 
John C. McCabe-Dansted
PhD Student
University of Western Australia

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Pavel Sanda]

John McCabe-Dansted wrote:
> On Thu, Jun 18, 2009 at 12:22 AM, John McCabe-Dansted wrote:
> > I have attached a patch. The patch isn't pretty, but the code wasn't
> > that pretty to begin with.
> 
> I just noticed a few minor errors in the patch.
>   www.ucc.asn.au/~mccabedj/keytest2.diff
> is more correct.

i'll commit this into the tree. i'm leaving soon for a week or two
out of net so i'll coment on the rest later, sorry.

pavel

Re: Keytest: Screenshots of Crashes, Samples and Patch.

[Pavel Sanda]

John McCabe-Dansted wrote:

ok i was too curious ... ;)

> On the other hand, would screenshots help? Here is some example output
> with screenshots taken the moment LyX crashes
> 
> http://www.ucc.asn.au/~mccabedj/kt/indexreport.html
> http://www.ucc.asn.au/~mccabedj/keytest_html_out.tar.gz
> http://www.ucc.asn.au/~mccabedj/kt/
> 
> FYI, These crash reports are from r30112.

this is aesthetically beautiful, but the main thing still missing - some 
reference
to keys which caused this.


> Would adding links from text like "LyX.cpp:7" to things like:
> http://www.lyx.org/trac/browser/lyx-devel/branches/BRANCH_1_6_X/COPYING?rev=27418#L7
> also be useful?

it wouldn't hurt, yes.

> It occurs if you spell check inside a math macro, and then hit
> replace. The thing I find amusing is that the spell-checker dialog is
> blank so the "correct" thing for LyX to do would be to replace "" with
> "", something no real human would ever actually want to do. If humans
> do want to do this, they are not the sort that fix bugs, since I can
> reproduce this in 1.5.7.

we shouldn't crash anyway. for bugs you know howto reproduce just fill crash 
bug report. for bugs without this we should invent something another so we dont
overpopulate bugzilla. maybe adding links into meta bug for keys test i have 
added
yestreday or something like that?

> Would keycodes be useful for submitting manual bugs as well?

some links to keys is a must. most of the bugs wouldn't be reachible just from
the bakctrace and screenshot.

thank for your effort.
pavel

Re: [christian.ridderst...@gmail.com: Hartmut has created updated screenshots for the LyX Graphical Tour]

[Hartmut Haase]

Hi Pavel,
 Hartmut Haase wrote:
  we have enough disk spacve), and someone can replace the english 1.3
  screenshots by newer it he wants.

 this was just to encouragement if you want to be that someone, while
 you are this job... :)
maybe, but let me finish my translation first, and then I can retranslate.
-- 
Viele Grüße,
Hartmut 

Hungerhilfe: http://www.thehungersite.com

Ohne Zensur suchen:
http://suche.amnesty-bergedorf.de/

Das heutige Motto:
Daß da gehören soll, was da ist, denen, die für es gut sind. 

Re: [christian.ridderst...@gmail.com: Hartmut has created updated screenshots for the LyX Graphical Tour]

[Hartmut Haase]

Hi Pavel,
> Hartmut Haase wrote:
> > we have enough disk spacve), and someone can replace the english 1.3
> > screenshots by newer it he wants.
>
> this was just to encouragement if you want to be that someone, while
> you are this job... :)
maybe, but let me finish my translation first, and then I can retranslate.
-- 
Viele Grüße,
Hartmut 

Hungerhilfe: http://www.thehungersite.com

Ohne Zensur suchen:
http://suche.amnesty-bergedorf.de/

Das heutige Motto:
Daß da gehören soll, was da ist, denen, die für es gut sind. 

Re: [christian.ridderst...@gmail.com: Hartmut has created updated screenshots for the LyX Graphical Tour]

[Hartmut Haase]

Hi Pavel,
 PS. Hartmut, maybe you could briefly mention what the differences are in
 the pictures, 
I think there is a misunderstanding. I took german screenshots from LyX 1.6.2 
to use them in my translation. I also modified some file names. In the 
meantime I've seen that there are also spanish screenshots.
Therefore it is better to have national screenshots (Christian confirmed that 
we have enough disk spacve), and someone can replace the english 1.3 
screenshots by newer it he wants.
By the way, I can't see an ... images/LGT/En directory.

 and/or what made you think it was time for better screenshots?
Well there are a lot of changes between 1.3 and 1.6.2, aren't there?

Christian please copy my screenshots I've uploaded to 
http://wiki.lyx.org/ipfm/index.php?dir=/Site/LGT/WebDe to 
http://www.lyx.org/images/LGT/WebDe/.
-- 
Viele Grüße,
Hartmut Haase

Hungerhilfe: http://www.thehungersite.com

Ohne Zensur suchen:
http://suche.amnesty-bergedorf.de/

Das heutige Motto:
Too much of a good thing can be wonderful!

Re: [christian.ridderst...@gmail.com: Hartmut has created updated screenshots for the LyX Graphical Tour]

[Pavel Sanda]

Hartmut Haase wrote:
 we have enough disk spacve), and someone can replace the english 1.3 
 screenshots by newer it he wants.

this was just to encouragement if you want to be that someone, while
you are this job... :)
pavel

Re: [christian.ridderst...@gmail.com: Hartmut has created updated screenshots for the LyX Graphical Tour]

[Hartmut Haase]

Hi Pavel,
> PS. Hartmut, maybe you could briefly mention what the differences are in
> the pictures, 
I think there is a misunderstanding. I took german screenshots from LyX 1.6.2 
to use them in my translation. I also modified some file names. In the 
meantime I've seen that there are also spanish screenshots.
Therefore it is better to have national screenshots (Christian confirmed that 
we have enough disk spacve), and someone can replace the english 1.3 
screenshots by newer it he wants.
By the way, I can't see an ... images/LGT/En directory.

> and/or what made you think it was time for better screenshots?
Well there are a lot of changes between 1.3 and 1.6.2, aren't there?

Christian please copy my screenshots I've uploaded to 
http://wiki.lyx.org/ipfm/index.php?dir=/Site/LGT/WebDe to 
http://www.lyx.org/images/LGT/WebDe/.
-- 
Viele Grüße,
Hartmut Haase

Hungerhilfe: http://www.thehungersite.com

Ohne Zensur suchen:
http://suche.amnesty-bergedorf.de/

Das heutige Motto:
Too much of a good thing can be wonderful!

Re: [christian.ridderst...@gmail.com: Hartmut has created updated screenshots for the LyX Graphical Tour]

[Pavel Sanda]

Hartmut Haase wrote:
> we have enough disk spacve), and someone can replace the english 1.3 
> screenshots by newer it he wants.

this was just to encouragement if you want to be that someone, while
you are this job... :)
pavel

Re: Hartmut has created updated screenshots for the LyX Graphical Tour

[Christian Ridderström]

On Fri, 29 May 2009, Mike Ressler wrote:


       images/LGT/En

If anyone (perhaps the original authors)


The original author (that would be me) is still lurking in the 
background.


Hi Mike,

very cool to still see you lurking here!

note that images there are _not_ localised. i would encourage Hartmut 
to update the english version ot the text.


I didn't quite understad what Pavel meant with this?

If you believe the dates on some of the xdvi screenshots, I did the 
original 10 1/2 years ago! So it really is time to update the whole 
thing, including the page previews. Is Hartmunt up to doing that? I can 
volunteer to help proofread, but I don't have the opportunity to do much 
more than that.


He has already taken new screenshots, it's the ones that are locatd here:

http://www.lyx.org/images/LGT/En/

Unfortunately I have no idea how (much) these differ, and what the 
implications are for the text. Let's hope Hartmut's reading this and 
chimes in.


Best regards,
/Christian

--
Christian Ridderström   Mobile: +46-70 687 39 44

Re: Hartmut has created updated screenshots for the LyX Graphical Tour

[Christian Ridderström]

On Fri, 29 May 2009, Mike Ressler wrote:


       images/LGT/En

If anyone (perhaps the original authors)


The original author (that would be me) is still lurking in the 
background.


Hi Mike,

very cool to still see you lurking here!

note that images there are _not_ localised. i would encourage Hartmut 
to update the english version ot the text.


I didn't quite understad what Pavel meant with this?

If you believe the dates on some of the xdvi screenshots, I did the 
original 10 1/2 years ago! So it really is time to update the whole 
thing, including the page previews. Is Hartmunt up to doing that? I can 
volunteer to help proofread, but I don't have the opportunity to do much 
more than that.


He has already taken new screenshots, it's the ones that are locatd here:

http://www.lyx.org/images/LGT/En/

Unfortunately I have no idea how (much) these differ, and what the 
implications are for the text. Let's hope Hartmut's reading this and 
chimes in.


Best regards,
/Christian

--
Christian Ridderström   Mobile: +46-70 687 39 44

Re: Hartmut has created updated screenshots for the LyX Graphical Tour

[Mike Ressler]

Hi all,

On Thu, May 28, 2009 at 9:46 AM, Pavel Sanda sa...@lyx.org wrote:
 Christian Ridderström wrote:
 the graphical tour, so for now I've place the new images in the
 subdirectory
        images/LGT/En

 If anyone (perhaps the original authors)

 original authors are not here anymore i guess

The original author (that would be me) is still lurking in the background.

 note that images there are _not_ localised. i would encourage Hartmut
 to update the english version ot the text.

If you believe the dates on some of the xdvi screenshots, I did the
original 10 1/2 years ago! So it really is time to update the whole
thing, including the page previews. Is Hartmunt up to doing that? I
can volunteer to help proofread, but I don't have the opportunity to
do much more than that.

Mike


-- 
mike.ress...@alum.mit.edu

Re: Hartmut has created updated screenshots for the LyX Graphical Tour

[Mike Ressler]

Hi all,

On Thu, May 28, 2009 at 9:46 AM, Pavel Sanda <sa...@lyx.org> wrote:
> Christian Ridderström wrote:
>> the graphical tour, so for now I've place the new images in the
>> subdirectory
>>        images/LGT/En
>>
>> If anyone (perhaps the original authors)
>
> original authors are not here anymore i guess

The original author (that would be me) is still lurking in the background.

> note that images there are _not_ localised. i would encourage Hartmut
> to update the english version ot the text.

If you believe the dates on some of the xdvi screenshots, I did the
original 10 1/2 years ago! So it really is time to update the whole
thing, including the page previews. Is Hartmunt up to doing that? I
can volunteer to help proofread, but I don't have the opportunity to
do much more than that.

Mike


-- 
mike.ress...@alum.mit.edu

Re: Hartmut has created updated screenshots for the LyX Graphical Tour

[Pavel Sanda]

Christian Ridderström wrote:
 the graphical tour, so for now I've place the new images in the 
 subdirectory
images/LGT/En

 If anyone (perhaps the original authors)

original authors are not here anymore i guess

would like to update the text 
 accordingly, that'd be great. Otherwise we'll still have the old text and 
 the old images, and translators are free to use the old images, the new 
 images or send me localized versions of screenshots.

note that images there are _not_ localised. i would encourage Hartmut
to update the english version ot the text.

pavel

Re: Hartmut has created updated screenshots for the LyX Graphical Tour

[Pavel Sanda]

Christian Ridderström wrote:
> the graphical tour, so for now I've place the new images in the 
> subdirectory
>images/LGT/En
>
> If anyone (perhaps the original authors)

original authors are not here anymore i guess

>would like to update the text 
> accordingly, that'd be great. Otherwise we'll still have the old text and 
> the old images, and translators are free to use the old images, the new 
> images or send me localized versions of screenshots.

note that images there are _not_ localised. i would encourage Hartmut
to update the english version ot the text.

pavel

Hartmut has created updated screenshots for the LyX Graphical Tour

[Christian Ridderström]

Hi,

Hartmut has created updated screenshots for the LyX Graphical Tour. 
According to him, these screenshots require a slight update to the text in 
the graphical tour, so for now I've place the new images in the 
subdirectory

 images/LGT/En

If anyone (perhaps the original authors) would like to update the text 
accordingly, that'd be great. Otherwise we'll still have the old text and 
the old images, and translators are free to use the old images, the new 
images or send me localized versions of screenshots.


Best regards
/Christian

PS. Hartmut, maybe you could briefly mention what the differences are in 
the pictures, and/or what made you think it was time for better 
screenshots?


--
Christian Ridderström   Mobile: +46-70 687 39 44

Hartmut has created updated screenshots for the LyX Graphical Tour

[Christian Ridderström]

Hi,

Hartmut has created updated screenshots for the LyX Graphical Tour. 
According to him, these screenshots require a slight update to the text in 
the graphical tour, so for now I've place the new images in the 
subdirectory

 images/LGT/En

If anyone (perhaps the original authors) would like to update the text 
accordingly, that'd be great. Otherwise we'll still have the old text and 
the old images, and translators are free to use the old images, the new 
images or send me localized versions of screenshots.


Best regards
/Christian

PS. Hartmut, maybe you could briefly mention what the differences are in 
the pictures, and/or what made you think it was time for better 
screenshots?


--
Christian Ridderström   Mobile: +46-70 687 39 44

Screenshots not working

[Derek B. Cornish]

Hello Webmaster,

I thought you ought to know that the screenshots on
http://www.lyx.org/about/screenshots.php do not seem to be working. Using
Windows XP and FireFox or IE6 I get the message that the images cannot be
displayed because they contain errors.

Also on http://www.lyx.org/ the two gifs mentioned in the paragraph below
seem in fact not to be text, but pictures of a duckbilled platypus. 

Just to whet your appetite and show you what LyX can do, here are two of
the seventy-five or so gifs from the LyX Graphical Tour. The first shows a
page of (rather busy) text being edited in LyX, while the second shows the
printed output resulting from that page. 

As I am considering using Lyx for a book I am writing, could you direct me
to some screenshots?

Kind regards,

Derek Cornish

Re: Screenshots not working

[Jean-Marc Lasgouttes]

 Derek == Derek B Cornish [EMAIL PROTECTED] writes:

Derek Hello Webmaster, I thought you ought to know that the
Derek screenshots on http://www.lyx.org/about/screenshots.php do not
Derek seem to be working. Using Windows XP and FireFox or IE6 I get
Derek the message that the images cannot be displayed because they
Derek contain errors.

Hello,

Yes, we are aware of that. The files have been broken, I do not known
if we still have the original ones.

Derek As I am considering using Lyx for a book I am writing, could
Derek you direct me to some screenshots?

Look at
http://www.lyx.org/LGT/

JMarc

Re: Screenshots not working

[Lars Gullik Bjønnes]

Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:

|  Derek == Derek B Cornish [EMAIL PROTECTED] writes:
| 
| Derek Hello Webmaster, I thought you ought to know that the
| Derek screenshots on http://www.lyx.org/about/screenshots.php do not
| Derek seem to be working. Using Windows XP and FireFox or IE6 I get
| Derek the message that the images cannot be displayed because they
| Derek contain errors.
| 
| Hello,
| 
| Yes, we are aware of that. The files have been broken, I do not known
| if we still have the original ones.

The original cvs should be up and working, should be possible to get
the images from there.

I wonder what broke them though.

I have reimported from old cvs. Hopefully it is ok now.

-- 
Lgb

Screenshots not working

[Derek B. Cornish]

Hello Webmaster,

I thought you ought to know that the screenshots on
http://www.lyx.org/about/screenshots.php do not seem to be working. Using
Windows XP and FireFox or IE6 I get the message that the images cannot be
displayed because they contain errors.

Also on http://www.lyx.org/ the two gifs mentioned in the paragraph below
seem in fact not to be text, but pictures of a duckbilled platypus. 

"Just to whet your appetite and show you what LyX can do, here are two of
the seventy-five or so gifs from the LyX Graphical Tour. The first shows a
page of (rather busy) text being edited in LyX, while the second shows the
printed output resulting from that page." 

As I am considering using Lyx for a book I am writing, could you direct me
to some screenshots?

Kind regards,

Derek Cornish

Re: Screenshots not working

[Jean-Marc Lasgouttes]

>>>>> "Derek" == Derek B Cornish <[EMAIL PROTECTED]> writes:

Derek> Hello Webmaster, I thought you ought to know that the
Derek> screenshots on http://www.lyx.org/about/screenshots.php do not
Derek> seem to be working. Using Windows XP and FireFox or IE6 I get
Derek> the message that the images cannot be displayed because they
Derek> contain errors.

Hello,

Yes, we are aware of that. The files have been broken, I do not known
if we still have the original ones.

Derek> As I am considering using Lyx for a book I am writing, could
Derek> you direct me to some screenshots?

Look at
http://www.lyx.org/LGT/

JMarc

Re: Screenshots not working

[Lars Gullik Bjønnes]

Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:

| >>>>> "Derek" == Derek B Cornish <[EMAIL PROTECTED]> writes:
| 
| Derek> Hello Webmaster, I thought you ought to know that the
| Derek> screenshots on http://www.lyx.org/about/screenshots.php do not
| Derek> seem to be working. Using Windows XP and FireFox or IE6 I get
| Derek> the message that the images cannot be displayed because they
| Derek> contain errors.
| 
| Hello,
| 
| Yes, we are aware of that. The files have been broken, I do not known
| if we still have the original ones.

The original cvs should be up and working, should be possible to get
the images from there.

I wonder what broke them though.

I have reimported from old cvs. Hopefully it is ok now.

-- 
Lgb

Re: Screenshots

[Jean-Marc Lasgouttes]

 Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes:

Juergen while I was at it, I have also updated the screenshots page.
Juergen Find it here:
Juergen http://omnibus.uni-freiburg.de/~spitzmue/lyx-screenshots/screenshots.php3

Could you package it as a tar file so that I can put that on the web
site?

JMarc

Re: Screenshots

[Juergen Spitzmueller]

Jean-Marc Lasgouttes wrote:
  Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes:

 Juergen while I was at it, I have also updated the screenshots page.
 Juergen Find it here:
 Juergen
 http://omnibus.uni-freiburg.de/~spitzmue/lyx-screenshots/screenshots.php3

 Could you package it as a tar file so that I can put that on the web
 site?

http://omnibus.uni-freiburg.de/~spitzmue/lyx-screenshots.tar.gz

Regards,
Jürgen.

 JMarc

Re: Screenshots

[Jean-Marc Lasgouttes]

 Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes:

 Could you package it as a tar file so that I can put that on the
 web site?

Juergen http://omnibus.uni-freiburg.de/~spitzmue/lyx-screenshots.tar.gz

Thanks, I converted this to real php3 files (including
start.php3/end.php3) and commited. Now, let's look at the lgt.

JMarc

Re: Screenshots

[Juergen Spitzmueller]

Jean-Marc Lasgouttes wrote:
 Thanks, I converted this to real php3 files (including
 start.php3/end.php3) and commited. Now, let's look at the lgt.

Sorry, I didn't know that that was needed. Actually, I used the existing 
screenshots page and just replaced the images.

Jürgen.

Re: Screenshots

[Jean-Marc Lasgouttes]

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

Juergen> while I was at it, I have also updated the screenshots page.
Juergen> Find it here:
Juergen> http://omnibus.uni-freiburg.de/~spitzmue/lyx-screenshots/screenshots.php3

Could you package it as a tar file so that I can put that on the web
site?

JMarc

Re: Screenshots

[Juergen Spitzmueller]

Jean-Marc Lasgouttes wrote:
> >>>>> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
>
> Juergen> while I was at it, I have also updated the screenshots page.
> Juergen> Find it here:
> Juergen>
> http://omnibus.uni-freiburg.de/~spitzmue/lyx-screenshots/screenshots.php3
>
> Could you package it as a tar file so that I can put that on the web
> site?

http://omnibus.uni-freiburg.de/~spitzmue/lyx-screenshots.tar.gz

Regards,
Jürgen.

> JMarc

Re: Screenshots

[Jean-Marc Lasgouttes]

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

>> Could you package it as a tar file so that I can put that on the
>> web site?

Juergen> http://omnibus.uni-freiburg.de/~spitzmue/lyx-screenshots.tar.gz

Thanks, I converted this to real php3 files (including
start.php3/end.php3) and commited. Now, let's look at the lgt.

JMarc

Re: Screenshots

[Juergen Spitzmueller]

Jean-Marc Lasgouttes wrote:
> Thanks, I converted this to real php3 files (including
> start.php3/end.php3) and commited. Now, let's look at the lgt.

Sorry, I didn't know that that was needed. Actually, I used the existing 
screenshots page and just replaced the images.

Jürgen.

Screenshots

[Juergen Spitzmueller]

while I was at it, I have also updated the screenshots page. Find it here:
http://omnibus.uni-freiburg.de/~spitzmue/lyx-screenshots/screenshots.php3

Regards,
Jürgen.

Screenshots

[Juergen Spitzmueller]

while I was at it, I have also updated the screenshots page. Find it here:
http://omnibus.uni-freiburg.de/~spitzmue/lyx-screenshots/screenshots.php3

Regards,
Jürgen.

Re: frequent polling in LyX (plus LyX under DRT screenshots)

[John Levon]

On Mon, Sep 02, 2002 at 09:48:22AM +1000, Amir Michail wrote:

 You can see some preliminary results here in the following screenshots:
 
 http://www.cse.unsw.edu.au/~amichail/lyx8.png

Nice !

 BTW, could someone tell me if the functions shown in the pictures
 are particularly relevant to the action?  The darker the action label,
 the more relevant it is perceived to be to the action shown in the 
 before/after pictures.

Looks good, I think.

 I also found another problem with getting rid of cursor blinking.
 If you type a sentence and press return, the cursor will not appear
 for a while until it is told to blink on.  By then, the after picture
 has already been taken, so cursor tracking is broken.  So it's not sufficient 
 to disable blinking. We also need to make cursors appear immediately when 
 they are moved in various contexts.

It would be really nice if out of this work somebody fixed our
horrendously broken cursor handling :)

john

-- 
Take the ideas you find useful. Try not to get hung up on the labels.
- Jonathan S. Shapiro

Re: frequent polling in LyX (plus LyX under DRT screenshots)

[John Levon]

On Mon, Sep 02, 2002 at 09:48:22AM +1000, Amir Michail wrote:

> You can see some preliminary results here in the following screenshots:
> 
> http://www.cse.unsw.edu.au/~amichail/lyx8.png

Nice !

> BTW, could someone tell me if the functions shown in the pictures
> are particularly relevant to the action?  The darker the action label,
> the more relevant it is perceived to be to the action shown in the 
> before/after pictures.

Looks good, I think.

> I also found another problem with getting rid of cursor blinking.
> If you type a sentence and press return, the cursor will not appear
> for a while until it is told to blink on.  By then, the after picture
> has already been taken, so cursor tracking is broken.  So it's not sufficient 
> to disable blinking. We also need to make cursors appear immediately when 
> they are moved in various contexts.

It would be really nice if out of this work somebody fixed our
horrendously broken cursor handling :)

john

-- 
"Take the ideas you find useful. Try not to get hung up on the labels."
- Jonathan S. Shapiro

Re: frequent polling in LyX (plus LyX under DRT screenshots)

[Juergen Vigna]

Amir Michail wrote:
 I also found another problem with getting rid of cursor blinking.
 If you type a sentence and press return, the cursor will not appear
 for a while until it is told to blink on.  By then, the after picture
 has already been taken, so cursor tracking is broken.  So it's not sufficient 
 to disable blinking. We also need to make cursors appear immediately when 
 they are moved in various contexts.

The cursor handling is a bit broken. We _always_ should hide *and* show
the cursor, but sometimes we just forget to show it as it really should
show as then we get cursor trails :(. IMO we need some sort of counter
or some sort of flag (as the undo does) in which we see if the cursor is
already hidden and don't do it again. So the first one hiding it is
responsible for showing it again. When we changed this behaviour it
should be quite easy tracking down where we forgot to put a showCursor
call.

   Jug

-- 
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Mitterstrich 151/A  Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39050 SteineggWeb: http://www.lyx.org/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Re: frequent polling in LyX (plus LyX under DRT screenshots)

[Juergen Vigna]

Amir Michail wrote:
> I also found another problem with getting rid of cursor blinking.
> If you type a sentence and press return, the cursor will not appear
> for a while until it is told to blink on.  By then, the after picture
> has already been taken, so cursor tracking is broken.  So it's not sufficient 
> to disable blinking. We also need to make cursors appear immediately when 
> they are moved in various contexts.

The cursor handling is a bit broken. We _always_ should hide *and* show
the cursor, but sometimes we just "forget" to show it as it really should
show as then we get cursor trails :(. IMO we need some sort of counter
or some sort of flag (as the undo does) in which we see if the cursor is
already hidden and don't do it again. So the first one hiding it is
responsible for showing it again. When we changed this behaviour it
should be quite easy tracking down where we "forgot" to put a showCursor
call.

   Jug

-- 
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Mitterstrich 151/A  Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39050 SteineggWeb: http://www.lyx.org/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Re: frequent polling in LyX (plus LyX under DRT screenshots)

[Amir Michail]

Hi,

Perhaps a configure flag could be used to build LyX in a way that works well 
under DRT?   Although the polling change I mentioned (and others) may not be 
bug free, they do seem to get LyX working under DRT.

You can see some preliminary results here in the following screenshots:

http://www.cse.unsw.edu.au/~amichail/lyx8.png

From the function sequence in the picture above, we see that the user
probably moved the cursor up.  However, that's
not the whole story as made obvious by the before/after screenshots.
In fact, the cursor moved out from math mode as well.
This shows the importance of before/after pictures in explaining past actions
(possibly performed by others).

BTW, could someone tell me if the functions shown in the pictures
are particularly relevant to the action?  The darker the action label,
the more relevant it is perceived to be to the action shown in the 
before/after pictures.

To see how we arrived at the previous screenshot, see the
following:

http://www.cse.unsw.edu.au/~amichail/lyx1.png

http://www.cse.unsw.edu.au/~amichail/lyx2.png

http://www.cse.unsw.edu.au/~amichail/lyx3.png

http://www.cse.unsw.edu.au/~amichail/lyx4.png

http://www.cse.unsw.edu.au/~amichail/lyx5.png

http://www.cse.unsw.edu.au/~amichail/lyx6.png

http://www.cse.unsw.edu.au/~amichail/lyx7.png

http://www.cse.unsw.edu.au/~amichail/lyx8.png

I also found another problem with getting rid of cursor blinking.
If you type a sentence and press return, the cursor will not appear
for a while until it is told to blink on.  By then, the after picture
has already been taken, so cursor tracking is broken.  So it's not sufficient 
to disable blinking. We also need to make cursors appear immediately when 
they are moved in various contexts.

Amir

Re: frequent polling in LyX (plus LyX under DRT screenshots)

[Amir Michail]

Hi,

Perhaps a configure flag could be used to build LyX in a way that works well 
under DRT?   Although the polling change I mentioned (and others) may not be 
bug free, they do seem to get LyX working under DRT.

You can see some preliminary results here in the following screenshots:

http://www.cse.unsw.edu.au/~amichail/lyx8.png

>From the function sequence in the picture above, we see that the user
probably moved the cursor up.  However, that's
not the whole story as made obvious by the before/after screenshots.
In fact, the cursor moved out from math mode as well.
This shows the importance of before/after pictures in explaining past actions
(possibly performed by others).

BTW, could someone tell me if the functions shown in the pictures
are particularly relevant to the action?  The darker the action label,
the more relevant it is perceived to be to the action shown in the 
before/after pictures.

To see how we arrived at the previous screenshot, see the
following:

http://www.cse.unsw.edu.au/~amichail/lyx1.png

http://www.cse.unsw.edu.au/~amichail/lyx2.png

http://www.cse.unsw.edu.au/~amichail/lyx3.png

http://www.cse.unsw.edu.au/~amichail/lyx4.png

http://www.cse.unsw.edu.au/~amichail/lyx5.png

http://www.cse.unsw.edu.au/~amichail/lyx6.png

http://www.cse.unsw.edu.au/~amichail/lyx7.png

http://www.cse.unsw.edu.au/~amichail/lyx8.png

I also found another problem with getting rid of cursor blinking.
If you type a sentence and press return, the cursor will not appear
for a while until it is told to blink on.  By then, the after picture
has already been taken, so cursor tracking is broken.  So it's not sufficient 
to disable blinking. We also need to make cursors appear immediately when 
they are moved in various contexts.

Amir