On 14/11/2019 22:39, Bruno P. Kinoshita wrote:
Maybe an upgrade on Fuseki UI? Last I checked it was using Backbone JS, with
dependencies bundled in the code. Even though the NPM/JS ecosystem is a bit
more complex, we could probably upgrade it to
Maybe worth starting as a new UI, write the requirements and definition,
which may be less or different to the current one, and see whether
change or write fresh is better. If we make it a React webapp (or other
similar), then more likely "fresh" and copy what we can.
Oh - and it greatly simplify the licensing if we didn't have to
incorporate JS into the code base.
- use a framework- specify dependencies in package.json (good to monitor for
security issues)
- use sass/scss for styling- have a few tests in the JS project too- allow for
user extensions (i.e. changing how it looks, i18n, rtl-ltr, either provide a
way for users to customize it or just document where they could get started,
etc)
At the moment I am 30% doing Python, and 70% JS at $work (plus a bunch of spare
time to get up to speed with the JS world). That will continue until Oct/2020
or later if the project confirms more funding/grants/etc. So that's something I
could help with during next year.
The other thing I think is already planned, but removing deprecated or unused
stuff is always helpful.
Smaller is better!
CheersBruno
On Thursday, 14 November 2019, 8:18:31 am NZDT, Andy Seaborne
<a...@apache.org> wrote:
I'd like to start a discussion on where the project might go longer term.
This can be specific areas, overall design, about project processes,
anything.
If we are going to do a major change, Jena4, what preparation for that
can be done? (e.g. deprecation and signalling in Jena3, before the
change happens).
Realistically, Jena4 means having Jena3 and Jena4 in parallel. Jena4
need not be that big - we can have Jena5 etc.
I'll put some technical points in a separate email.
I would put on the list:
* How has the world changed? What should the project produce?
* Target audience: for developers of Jena, while Jena3 is for users.
* Target: Java14, JPMS.
* Clear-up not easily done with perfect compatibility.
* Simpler. There are APIs and packages entangled due to history.
To the lurkers :-)
Feedback and specific feature requests are welcome. But before you "go
shopping", you may wish to factor in that every feature needs effort to
do it. The better place to be is that an application can get what it
needs to do, not whether the Jena system has every feature built-in.
Andy
