API for JVS postgres database

[lagleki]

Develop an API for JVS that is able to read and writ to the db. This will also make almost all JVS 2.0 issues and proposals not relevant since they can be implemented in separate projects using this API.

[tsani]

In January I began looking into this specifically. The existing JVS architechture is fairly dated (written in Perl!) which is a pretty big impediment to getting new people to help develop it. On the other hand, Vlasisku is designed in a fairly modern way (using Flask written in Python). That said, the best route for JVS2 is to slowly give Vlasisku more and more features, until it can function in tandem with JVS.

At that time, using JVS can be deprecated, and be decommissioned some time later.

The first step to making Vlasisku replace JVS is to give it direct access to the database (at first in a readonly way, pe'i). It will thus always be up to date. Building an API for querying the database would be very easy with Flask.

I had started work on having Vlasisku interact directly with the database, rather than use XML dumps, but got sidetracked with school and other projects. Hopefully over the summer I'll have more time to work on it!

[lagleki]

API is more important to me than any GUI. Just plugging it directly to the
db would be fine. However, a new database model, namely, attaching
definitions to meanings, not to words (issue #131) has to be done first.

2015-06-11 18:22 GMT+03:00 Jacob Thomas Errington [email protected]
:

In January I began looking into this specifically. The existing JVS
architechture is fairly dated (written in Perl!) which is a pretty big
impediment to getting new people to help develop it. On the other hand,
Vlasisku is designed in a fairly modern way (using Flask written in
Python). That said, the best route for JVS2 is to slowly give Vlasisku more
and more features, until it can function in tandem with JVS.

At that time, using JVS can be deprecated, and be decommissioned some time
later.

The first step to making Vlasisku replace JVS is to give it direct access
to the database (at first in a readonly way, pe'i). It will thus always be
up to date. Building an API for querying the database would be very easy
with Flask.

I had started work on having Vlasisku interact directly with the database,
rather than use XML dumps, but got sidetracked with school and other
projects. Hopefully over the summer I'll have more time to work on it!

—
Reply to this email directly or view it on GitHub
#172 (comment).

[lagleki]

The title of the issues might be misleading. It's not about JVS but about JVS postgres database.