Hello Cyrille, Cyrille Artho <c.artho <at> aist.go.jp> writes: > > Hi Hanshini, > (probably my mails don't make it to the list directly as I'm writing from a > different account)
I can see your mails in the developers list. Sorry for the slow response. I will soon get attached to this process. > I think the width of elements in the output is a general issue that most > users are aware of. Having visual feedback in LyX would be a nice > enhancement of course. Still, I would not create too many bug reports for > feature requests and enhancements, unless it is clear that we can go ahead > and implement them. > > It's a matter of taste. IMHO it's a very good idea to keep in mind for your > proposal. As for the bug tracker, I tend to use bug reports only for things > that are real bugs (or features that seem so broken that it feels like one). > Thank you for the idea of having visual feedbacks. Currently what I can think about is a pop up window that gives some warnings about the cut off sections in the output. I will think about it further and contact you for further advices. Thank you Hashini Senaratne Liviu Andronic <landronimirc <at> gmail.com> writes: > > On Wed, Apr 10, 2013 at 8:51 AM, Cyrille Artho <c.artho <at> aist.go.jp> wrote: > > Hi Hanshini, > > (probably my mails don't make it to the list directly as I'm writing from a > > different account) > > > I think your messages get to the list. > > > I think the width of elements in the output is a general issue that most > > users are aware of. Having visual feedback in LyX would be a nice > > enhancement of course. Still, I would not create too many bug reports for > > feature requests and enhancements, unless it is clear that we can go ahead > > and implement them. > > > > It's a matter of taste. IMHO it's a very good idea to keep in mind for your > > proposal. As for the bug tracker, I tend to use bug reports only for things > > that are real bugs (or features that seem so broken that it feels like one). > > > On the LyX bug tracker we usually put even wild enhancement requests > so taht they "don't get lost on the mailing list". I think it's OK to > put in an enhancement request once we have a clearer idea on what we > want to do, and after we wait for more input from other devels. > > Liviu >
