RE: [mylar-dev] cvs rename

["Mik Kersten" <beatmik@xxxxxxx>]

The good thing about the common navigator stuff is that once you've got all
the content providers and stuff wired up you can show it in either the
Project Explorer or your own view, so it's flexible.

But that's an interesting point about the Active Search view, because I
think of that view as being able to show any non-hierarchical part of the
task context.  I actually don't like the name Active Search because it
speaks about the underlying implementation (we're predicting interest via
via Search), and not the utility (it shows elements that are part of your
context but that don't fit in an explorer/navigator view hierarchy).  

Btw, as an experiment I've done all my programming this week using the
Project Explorer.  It's been working fine, and the only weirdness I noticed
is that Mylar should probably put back the Import Declarations filter.  So
I'm wondering what's making you feel that it's toyish?  Also, aren't people
doing web development going to be forced to use it instead of the Package
Explorer?

Mik

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Eugene Kuleshov
> Sent: Wednesday, May 31, 2006 9:07 AM
> To: Mylar developer discussions
> Subject: Re: [mylar-dev] cvs rename
> 
> 
>   Hmm. Navigator is still something from toyish functionality that don't
> yet fit into regular development activities.
> 
>   I wonder if it can appear on some existing views. Active search
> perhaps...
> 
>   regards,
>   Eugene
> 
> 
> Mik Kersten wrote:
> > Two kinds:
> >
> > 1) All the web linked task stuff, e.g. ability to view tasks with the
> > internal browser.
> >
> > 2) Capturing context for web resources.
> >
> > (2) has been there since early October, but it hasn't been exposed in
> the UI
> > adequately.  It enables the documents we navigate to as part of the task
> > (e.g. articles, tutorials) to contribute to the task context.  For a few
> > releases there was a Web Docs tab on each task editor so that every web
> > document that the web documents that you navigated to via the internal
> > browser that would allow them to be navigated.  But I found it way too
> > cumbersome to always open up the task editor to see this context, so now
> > we're experimenting with exposing it in the common navigator.  You
> should be
> > able to try it from HEAD later this week, but it won't go into a release
> > until it is solid.
> >
> > Mik
> >
> >
> >> -----Original Message-----
> >> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-
> bounces@xxxxxxxxxxx]
> >> On Behalf Of Eugene Kuleshov
> >> Sent: Wednesday, May 31, 2006 8:42 AM
> >> To: Mylar developer discussions
> >> Subject: Re: [mylar-dev] cvs rename
> >>
> >> Mik,
> >>
> >>   Can you please explain little more what kind of browser integration
> is
> >> there?
> >>
> >>   Thanks
> >>
> >>   Eugene
> >>
> >>
> >> Mik Kersten wrote:
> >>
> >>> The org.eclipse.mylar.hypertext plug-in has been renamed to:
> >>>
> >>> 	org.eclipse.mylar.web
> >>>
> >>> It has been providing the browser integration, and this name better
> >>>
> >> reflects
> >>
> >>> the fact that it responsible for more than a structure bridge for HTML
> >>> documents.
> >>>
> >>> To update your workspace delete the old project and check out the new
> >>>
> >> one.
> >>
> >>> Mik
> >>>
> >>>
> >> _______________________________________________
> >> 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
> >
> 
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev