[
https://issues.apache.org/jira/browse/CONNECTORS-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936212#comment-15936212
]
Karl Wright commented on CONNECTORS-1196:
-----------------------------------------
[~kishorekumar]: I ported the GTS test too. It too fails; I won't include the
error, but I will state this: it looks like we're perhaps seeing an
asynchronicity problem here.
This is what is happening, when I watch the browser go by:
(1) The test creates an output connection and saves it.
(2) Rendering of the "view" page for the connection takes a while because a
connection to a non-existent service has to time out. The time might be 15
seconds or so.
(3) Meanwhile, the tester keeps going, and starts to create a repository
connection.
(4) In the middle of the repository connection creation, the output connection
finally times out, and the "view" page is rendered.
(5) This *obliterates* the repository connection in progress and leads to a UI
testing error.
I don't know enough about Ajax to know whether this kind of asynchronicity
issue can be prevented? It seems to me that when we navigate away from a
connection's "view" page, we really want to completely cancel its generation at
that point and drop it on the floor. Is that possible?
> Proposal to update Manifold Crawler UI
> --------------------------------------
>
> Key: CONNECTORS-1196
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1196
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Framework core
> Affects Versions: ManifoldCF next
> Reporter: Kishore Kumar
> Assignee: Kishore Kumar
> Fix For: ManifoldCF next
>
> Attachments: Bandwidth Report.png, Index.jsp.png, List
> Repository.png, Report.png, View.png
>
>
> Hi,
> I have been working on a new User Interface for ManifoldCF.
> This UI is based on Bootstrap, jQuery and some other opensource scripts.
> Only the index.jsp will be loaded once and other page are rendered using AJAX
> call, making it more responsive and modern.
> Please find the attached screenshots.
> *Backward compatibility:*
> Since most of our tab comes from connectors, those tabs will be displayed as
> it is with no immediate attention required. (see sample screenshot attached)
> *What next?*
> In future we can add Charts to our reports where ever applicable, so that it
> will be more user friendly & informative for end users.
> Can make use of Web socket to notify exception or error to users as
> Notifications.
> *Browser compatibility*
> Has been tested with most latest browser and IE10, will try to add support
> for IE8 with acceptable degradation.
> Any suggestion, concern much appreciated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
