That's why i do not have started yet.
We should first sort the needs, then choose the appropriate language.
Am i confused or the first thing to do is to create a in memory graph of
the whole repository by crawling it ?
after, i don't really see what to do.
If we want to query a database with pre known queries, then we could use
other than prolog, if the queries are to be known only after, then
maybe, prolog is a good language.
Raphaël
Brett Porter a écrit :
That's an option, but I'd really prefer to look at other options first.
If you do something in prolog, how many other people are going to be
able to work with you on it? Is it something others are going to be able
to quickly understand and modify/improve?
And I need to emphasise again that there is already some code around
that is trying to address this: the discovery and reports components of
the repository manager, and the graphing plugin at mojo.codehaus.org.
How do these relate to the tasks?
I don't mean to discourage it - if you've got an itch, by all means
scratch it and we'll sort it out in the end. Just trying to give the
best chance of being able to reuse it later :)
- Brett
Piéroni Raphaël wrote:
To overcome the license issue,
maybe a tool which use a gpl prolog to the queries shown by Steve can be
created at mojo.codehaus.org ?
I don't remember the license policy.
So whatever the means and the licences issues, are we agree about the task
such a tool have to do (the needs expressed by Steve) ?
In advance, thanks for any answer.
Regards,
Raphaël
---------------------------------------------------------------------
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]
