| Re: [recommenders-dev] Enabling Error Reporting in TACIT |
Hi Marcel,
Thank you so much for all the advice!
Thanks,
Anish
On 11 Nov 2016, at 12:53, Anish Kanchan <akanchan@xxxxxxx> wrote:Hi Marcel,Thanks a lot for all the information. My application is E3 based, so I'll have to build everything from scratch. I however was wondering if it would be possible to add E4 dependencies to the existing application and then use the AERI example as it is?Sorry, I can’t answer that without trying myself.In fact I did try creating a test E3 application, adding the AERI code to it, and then adding E4 dependency to it. This solved the compile time errors, but the application has been crashing ever since. I wanted to know if this approach of adding E4 dependency acceptable because writing the entire code from scratch seems way too complicated?You certainly do not need implement everything from scratch. There are quite a few classes you could reuse (like the local history classes, all the filters & predicates, Status to ErrorReport transformations, the actual IO class etc.) But when it comes to the workflow, we rely on DI and EventBus interfaces which are not available in E3. AERI also uses require-bundles and import package directives you may not be able to satisfy satisfy in your E3 RCP app. Thus, at some stage you may ending up copying and modifying AERI code into your own bundle.I’m sorry. I’m not able to help you more than with that ATM. I’ve no plans to write an E3 compatible client for you :-)If you go the extra milage, you could consider to refactor the necessary parts and contribute it to the open source project so that others can reuse it.Cheers,MarcelThanks,Anish______________________________On Fri, Nov 11, 2016 at 1:12 AM, Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx> wrote:Hi Anish,I would prefer getting the error reports by email.I understand this as “we’d like to open the email client on the user’s desktop that contains the error report as text. the user can review and click on send then”. Is that correct? Otherwise, you would need to open an email server and put credentials somewhere in your code - which is probably not what you want to do, right?If the former, here is a demo implementation that does that. You'll have to adjust it to your needs.And I would need to provide a client for the error reporting which would ask the TACIT users for their permission before the reports would be sentSince it’s an RCP application, you have to write that part yourself. We don’t have any reusable RCP clients – just one for the IDE.If your RCP app is based on E4, check out the aer.rcp demo project [1]. It shows one way how you can register your custom error reporting workflow. If your application is based on E3, you are probably better of to use AERI code just as example and write your custom solution from scratch. AERI builds on various concepts of E4 that just do not exist in E3.Cheers,MarcelOn 11 Nov 2016, at 04:15, Anish Kanchan <akanchan@xxxxxxx> wrote:Hi Marcel,______________________________Thanks a lot for all the information. The video was especially very useful. TACIT is a stand alone Eclipse RCP application, so the error reporting would have to be handled programmatically, right?I would prefer getting the error reports by email. And I would need to provide a client for the error reporting which would ask the TACIT users for their permission before the reports would be sent by email. So what should be my next steps for implementing the same?Here is the download link to the software: http://tacit.usc.edu/download.html Thanks,AnishOn Thu, Nov 10, 2016 at 2:03 AM, Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx> wrote:Hi Anish,that document is quite ancient :-) For future references use [1] as a starting point.Could you please share the steps involved with me?Sure, but it depends on your exact setup and how you’d like to use the error reporting.A few more questions first: Can your plug-ins be installed into any Eclipse IDE or must it run as a standalone RCP application?If it can be installed into the Eclipse IDE, then [2] describes how to register your code to receive error reports. If it’s a standalone RCP application you need to write your own client (it might be headless or a ui client - depending on your needs). In any case, you may find the AERI webinar [4] helpful too. It also makes a difference if its an E4-based RCP app or an E3 based app. Maybe you can share a download link with me so that I can have a look.Next thing is to decide how you want to send error reports. Do you want to send them by email to your support team or to some server via HTTP/REST calls? Everything is possible and up to you. If you need a server, you may reuse existing solutions like Ctrlflow Automated Error Reporting SaaS [3] (the same system that drives eclipse.org) or implement your own service that satisfies your special needs.Let me know what exactly you are looking for/need and I can provide you with more information.MarcelOn 10 Nov 2016, at 01:08, Anish Kanchan <akanchan@xxxxxxx> wrote:______________________________Hi,I am a software developer working on TACIT which is an open source Eclipse RCP application created at the Computational Social Science Lab of University of Southern California.I wish to enable the error reporting in TACIT. I found out in this link that you could provide the latest information on how the integration is to be done. Could you please share the steps involved with me?Thanks,Anish_________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/recommenders-dev --Codetrails GmbH
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.ecl ipse.org_mailman_listinfo_reco mmenders-2Ddev&d=DgICAg&c=clK7 kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p 7CSfnc_gI&r=Y0Xo6oo9RSm7sXuK5Z AtDQ&m=revny0c1jL805MK8S5RyInd xeReqV7qA661J3duqmKM&s=63AOIPo KW8_qfhXNlybFXs-dbrjMvN_ 0raUiIR4Q36U&e= _________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/recommenders-dev --Codetrails GmbH
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.ecl ipse.org_mailman_listinfo_reco mmenders-2Ddev&d=DgICAg&c=clK7 kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p 7CSfnc_gI&r=Y0Xo6oo9RSm7sXuK5Z AtDQ&m=esjZ4aX6ksBI79ePr6tW3eD aQgpuGgMN2ywdDUF7Bic&s= 6Ez3NhaHHe-d6Jhe4WY-bgK8FRtweK CdiaQ3A2CrIc4&e= _________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/recommenders- dev --Codetrails GmbH
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev. eclipse.org_mailman_listinfo_ recommenders-2Ddev&d=DgICAg&c= clK7kQUTWtAVEOVIgvi0NU5BOUHhpN 0H8p7CSfnc_gI&r= Y0Xo6oo9RSm7sXuK5ZAtDQ&m= IOsx5gTiXy17cdAza4Q8m0T1n6bTt8 NcshWYiVlQ3oQ&s=Gi3nVRynBjGj_ jLsPUMyA4QAvwNRfb5xiWDiCkQ4UYc &e=