GSoC: command and get obeyed ! + draft

[Jordi Polo]

First draft here
http://www.bahasara.org/raw-attachment/wiki/Papers/application_gsoc.pdf

Please comment. It is still WIP.
Do you think I should move something from extra functionality to core
functionality?



On Thu, Mar 20, 2008 at 3:37 AM, Jordi Polo <mumismo at gmail.com> wrote:

>
> Unbelievable, in 3 or 4 iterations of emails we seem to agree if not 100%
> of the ideas, at least in most of the vision.
>
> I will rewrite all this in a more concrete gsoc style proposal and send it
> to the ML tomorrow.
>
>
>
> > > translate  -> feed runners and get their results (the user select or
> > launch
> > > the top ranking)
> > >
> > > :translate -> The command is parser and only the "translate" service
> > runner
> >
> > other things that can help:
> >
> > * relevancy ranking. any runner which recognizes its keywords (e.g.
> > "starting
> > with translate" for a translation runner) should up the relevancy of the
> > rturn
> >
> > * if done in coordination with another application, that application can
> > hint
> > which runner to favour (not neccessarily limit to, but at least favour),
> > which you already mentioned above.
> >
>
>
> I see two choices here:
> - Let the runners do the parsing job. Adding keywords to the runners, get
> apps hinting and let the best win. May be more dynamic but you may not get
> what you want and surely more difficult to implement.
> - Let a "proxy" do the parsing job. Mapping keywords to runners. Configure
> what syntax goes to what runner and let only one activate. All the language
> parsing in one place, more reliable results (the user defines how the
> language works), learning can be implemented here though.
>
> At a first glance both choices may have advantages and drawbacks. But
> being 3.30 am here now, my first glance is all but reliable.
>
> --
>
> Jordi Polo Carres
> NLP laboratory - NAIST
> http://www.bahasara.org
>



-- 
Jordi Polo Carres
NLP laboratory - NAIST
http://www.bahasara.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/panel-devel/attachments/20080320/2af1b44f/attachment-0001.html