RE: [mylar-dev] Any chance of a headless org.eclipse.mylar.monitor.usage

["Mik Kersten" <beatmik@xxxxxxx>]

Yes, I've been itching to refactor the monitor into something like:
* monitor.core: interaction events, interaction history parsing, maybe some
stats collection
* monitor.ui: workbench monitoring facilities
* monitor.usage: personal usage monitoring and upload facilities, optional
plug-in/feature

Glenn: this will address your needs headless operation.  Could you please
submit a bug report?  

Meghan: this will also prevent you from having to write your own interaction
history parsing code, and that code can be a bit tricky so it's better that
we only have a single version.

Mik

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Meghan Allen
> Sent: Thursday, January 11, 2007 2:14 PM
> To: Mylar developer discussions
> Subject: Re: [mylar-dev] Any chance of a headless
> org.eclipse.mylar.monitor.usage
> 
> Hi Glenn,
> 
> We aren't currently working on re-factoring the Mylar Monitor to allow
> it to run headless, but it is something that may become useful (or
> necessary) in the future.
> 
> The current plan is to use servlets to allow users to upload their
> data, and to write a very simple servlet to parse the xml files on the
> server (at least to start).  All the uploaded data would be available,
> so if people wanted to use the Mylar reporting framework, they would
> have to copy the files to somewhere that could run Eclipse with the
> org.eclipse.mylar.monitor.usag plugin installed (so, for now, "not
> headless", if that's even how you say it)
> 
> Does anyone else have an opinion about refactoring that plugin so it
> could be run without a UI?  Is this something we (I?) should be
> working on.
> 
> meghan
> 
> 
> On 1/11/07, Everitt, Glenn <Glenn.Everitt@xxxxxxxxxxxxx> wrote:
> >
> >
> >
> >
> > As I mentioned in previous posts I want to process the Mylar monitor
> events
> > on the Corona Server.  I want to reuse the
> org.eclipse.mylar.monitor.usage
> > plugin.  Ideally I would like it to be a headless plugin similar to
> the
> > headless task plugin.  It looks like the following would need to be
> removed
> > to allow head-less use.  I'm not sure how many changes would be
> required in
> > org.eclipse.mylar.monitor.
> >
> >
> >
> > org.eclipse.mylar.internal.monitor.usage.ui.wizards
> >
> > org.eclipse.mylar.internal.monitor.usage.ui.editors
> >
> > org.eclipse.mylar.internal.monitor.usage.ui.preferences
> >
> > org.eclipse.mylar.monitor.usage.IBackgroundPage
> >
> > org.eclipse.mylar.monitor.usage.IQuestionnairePage
> >
> >
> >
> > Is a refactoring  something  like a jar file without eclipse user
> interface
> > being done to allow monitor event processing in Servlets?  I'm
> working with
> > Jim Wright to see if we can demo processing Mylar monitor logs on
> Corona
> > Server and distribute results to others in a workgroup.
> >
> >
> >
> > Glenn Everitt
> >
> >   The contents of this e-mail are intended for the named addressee
> only. It
> > contains information that may be confidential. Unless you are the
> named
> > addressee or an authorized designee, you may not copy or use it, or
> disclose
> > it to anyone else. If you received it in error please notify us
> immediately
> > and then destroy it.
> > _______________________________________________
> > mylar-dev mailing list
> > mylar-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/mylar-dev
> >
> >
> >
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev