On Thu, Feb 6, 2014 at 4:25 PM, stefano franchi
<stefano.fran...@gmail.com> wrote:
> Dear Lyx devels,
>
> I have received very few responses to my previous round call of possible
> mentors for the upcoming 2014 GSOC.

> - Scott (Horizontal scrollbar for tables and math) [1]

I never actually helped on this. All the burden was on JMarc.

I'm not qualified enough to be a primary mentor on any of the
projects. I've been trying to think of a project that I would be
qualified for. Below are some ideas.

Feasible idea #1

Here is my most feasible idea so far:
An integrated grammar checker. Reasons why I call this "feasible":

- There is a chance that John McCabe-Dansted would be interested in
being co-mentor (although I have not asked him).
- There has already been work done on it [2].
- (the main advantage) It could be implemented in a similar way to
LyX's spell checker. If LyX can find a grammar checking library (e.g.
Language Tool [1]), then the feature is enabled, just like LyX's spell
checker looks for spellchecking dictionaries. I believe that there are
enough similarities to the spell checker that the student and I could
learn from the spell checker code; but that there are enough
challenges (e.g. the input would not be just one word) that it would
be a significant workload and contribution.

Feasible idea #2

- CAS Integration with SAGE or (better) integration with Maxima. We
often get complaints that LyX does not have good enough CAS support. I
think that this is straight-forward enough that I could mentor better
integration. There are not clearly defined goals though. We would need
to identify things that are not working and make it clear what needs
to be fixed.

Feasible idea #3

I still think something should be done about the fact that a user can
open a LyX file that someone posted asking for help, compile, and have
all of his/her $HOME files uploaded/deleted. This is because of the
knitr/Sweave module (and an inset can be easily closed and hidden).
The user should be notified whenever a file has a "dangerous" module
for the first time. Richard had a good idea for solving the security
issue but not being intrusive (= only warning a user once per file
even if that file is subsequently changed). I believe it is
complicated enough for a GSoC but I don't think other LyX devels are
as interested in this being implemented as I am.

Thoughts?

Scott

[1] https://www.languagetool.org/
[2] http://wiki.lyx.org/Tools/LyX-GrammarChecker

Reply via email to