Behold, those applications probably implement grammar checkers fully into the source code and don't have an API. It's a huge difference if you want to do such a grammar checker as a UNO component via the API or if you want to hack the source code and integrate it at base level packaging your own OpenOffice distribution at the end. Doing it at the core level (integrating it directly into the source code) wouldn't probably bring much loss in performance if you are skilled and in case you want to do that I firstly recommend reading the coding guidelines and the hacker's guide by Michael Meeks, as introductory materials for OpenOffice core development.
Best Regards Christian Junker On Mon, 17 Jan 2005 20:00:04 -0200, Jorge Marques Pelizzoni <[EMAIL PROTECTED]> wrote: > The grammar checker already exists and implements "auto" checking in two text > processors to no significant performance loss. If this can not be reproduced > in > OOo, that will be solely OOo's fault. > > Cheers, > > Jorge. > > Quoting Christian Junker <[EMAIL PROTECTED]>: > > > To some degree I am pretty sure the UNO API has the power to allow you > > a lot of things for such a grammar add-on. > > I don't want to give you advice here, but I know of one attempt to > > produce such a grammar checker in Python, what came out made > > OpenOffice run very slow. So if you and others around you in Brazil > > are concerned about OOo's speed in terms of simple usage, then > > consider that it would probably be a lot of work writing such a > > grammar checker and it would probably slow down the office program > > considerably. > > That's just my opinion and input to you, whether you take that into > > consideration is up to you. > > > > In case you're going to create such a grammar checker, I will happily > > be of help if I can be in somewhat way. > > > > Best Regards > > Christian Junker > > > > On Wed, 12 Jan 2005 12:37:11 -0200, Jorge Marques Pelizzoni > > <[EMAIL PROTECTED]> wrote: > > > > > > > > > Hi, all! > > > > > > I've already posted this on the lingudev mailing list, but they were not > > very > > > responsive concerning the point that really interests me, probably because > > it > > > involves deep knowledge of the whole API, not only the linguistic-related > > > portion. So here I am. > > > > > > I represent a company that produces a grammar-checker for Brazilian > > Portuguese > > > and have been comissioned a way to integrate it with OpenOffice.org. I've > > done > > > my basic homework and seen lots of macro tricks, but am up to something a > > bit > > > more sophisticated, like "auto" grammar checking (i.e. checking as you > > type). > > > > > > Basically, a have one single question now (and a further one, depending on > > the > > > answer), as follows: > > > > > > With OOo's current build (ok, take also version 2.0 into consideration if > > need > > > be) and just that, can such a grammmar checker (i.e. involving concurrent > > > scanning and processing, "curly" underlining in different colours of > > arbitrary > > > text ranges, associating such ranges with specific pop-up menus, etc.) be > > > implemented as a UNO something? I mean does the _current_ API and > > architecture > > > support all that, even if it took lots of effort and expertise? > > > > > > If so, that would make prototyping a grammar checker API much easier till > > we > > > finally got to something worth integrating into the core, if ever. > > > > > > IF NOT, what is the _minimal_ set of features the current API lacks to > > enable > > > that? You see: I am not talking about a grammar checker API, BUT API > > extensions > > > that would allow external prototyping of a grammar checker API. [I realise > > the > > > answer to this question might be somewhat labourious and become a new > > > topic > > of > > > discussion.] > > > > > > Cheers, > > > > > > Jorge M. Pelizzoni. > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
