On Fri, 2008-06-06 at 13:31 +0200, Glenn-Erik wrote: > Why do you have to break or alter any existing sesat code? > Can you not use your existing sesat functions, and trim of the first 4 > characters of the result in this particular case?
The code that parses this string into result items is within the private
method AbstractSimpleFastSearchCommand.collectRelevantQueries(..)
This is inside sesat-kernel
> Like I said, I can look for ways to not have the result prefixed, but it
> will take some time to figure out how to do this. I though you could
> just do something very easy like
>
> var new_qry_sug=
> trim(original_sesat_function_to_Get_fast_suggestion_of_new_query('query'))
>
> in java, and it would be much quicker as thomas was wanting this done
> asap.
This string is no longer available at the application level that martin
is working at. Well he has a work around. But the format of the relevant
queries is currently hardcoded into the private method i mentioned above
and i do not know who else is using it.
~mck
--
"Each and everyone of us are Angels with only one wing. We need to hold
on to each other befor we can fly." Leo F. Buscaglia
| semb.wever.org | sesat.no | sesam.no |
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
