Hi Ian,
The release has other significant new work in Elepahs and it has the
OSGi packaging.
Can you say more about the issues you see in the interface? Not being
much of a UI person, I would better understand your points if you could
be more specific. I put through the patches and didn't see that existing
capabilities have been affected and that wasn't my intention.
There have been two kinds of patches:
1/ Reworking the query page
2/ Commenting out non-working features like "active" and "remove"
Several people on users@ have been using it and the feedback has been
positive, at least I though it was.
The test question I have is:
"Is it better than the Fuseki1 UI?"
I think it is - the capability of being about to create databases and
load data via the UI in a running server makes the "fire up and do
stuff" task much nicer.
Is it finished? No. Is it ever finished? This version does not have to
be a complete version. "Release early, release often", get feed back,
engage users and contributors.
Andy
On 03/03/15 21:07, Ian Dickinson wrote:
Hi folks,
Firstly an apology for dropping off the radar for a while. I've been
very busy with work, so haven't been attending to dev@ emails for a
while.
Anyway, I'm picking up the reins again on the Fuseki2 UI work. I
notice that there are a number of bug reports outstanding, thanks for
those whoever contributed to them. There are also some unfinished
threads on the originally planned Fuseki2 UI capabilities (some of
which will need back-end support via the server protocol). Finally
there have been some changes that have been introduced by some of the
patches that have gone through while my attention has been elsewhere,
some of which have negatively impacted existing capabilities.
Tl;dr - there's quite a bit of work to do to bring the Fuseki2 UI up
to where I'd like it to be, including closing out the new bugreps.
One of the reasons for bringing this to the list is with respect to
the forthcoming release. I can't get the outstanding work done in a
timeframe that will do anything other than delay this release. Given
my other work commitments, it's going to be O(weeks) before the work
queue that I can see on Fuseki2 is under control. We have a choice
about what to do about that. One option would be to include the
current UI as-is, but label it more clearly as an alpha release.
Another would be to decouple the new UI from this release, but aim for
another release in O(months) when Fuseki2 is up to a good standard.
There may be other options between those extremes.
Opinions?
Ian
