[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [buckminster-dev] Some improvements/ideas for buckminster
|
Hi Thomas,
comments inline.
Thomas Hallgren schrieb:
You can already right-click and do 'Buckminster' -> 'View CSpec...' in
your package explorer but perhaps I misunderstand what you mean?
Yes, I can do that for my projects, I cannot do it however for things in
my target platform or let's say maven artifacts that I resolved. All
things that are not projects in my workspace are currently only
reachable with the component explorer. An Open CSpec Dialog that works
like JDTs Open Type Dialog would be handy to open any component's cspec
from anywhere.
Take a look at the method
o.e.b.core.metadata.WorkspaceInfo.resolveLocal(). It uses the main
resolver to resolve a request. At the end, it returns the top resolution
of the BillOfMaterials. This method could easily be broken into two. One
that retain the current behavior and the uses another internally, that
would return the BOM. A dependency visualization popup menu could then
make use of the second. All the popup menu must do is to form a
component request based on context.
Deserves a bugzilla :-)
Great, thank you :)
On what would you apply this filter? The component name?
Sounds to me like you would benefit more from being able to apply a
filter on certain treats of the resolution, such as readerType or the
uri of the reader type.
I would go for name, because that's the thing I already know when I'm
wondering where component XY comes from, but readerType/URI makes sense
too of course, if you are wondering which components where resolved from
where. I'll try some things out regarding different types of
filters/highlighters and open a bugzilla where filter capabilities can
be discussed
One idea could be to leave the graph intact but highlight the components
that match the filter(s) that are currently in effect.
That's a very good idea. I'll try that.
I think filtering in general would be a very useful addition to the
dependency visualizer. The graph is often very large. So please add a
bugzilla for that.
B.t.w. did you see: https://bugs.eclipse.org/bugs/show_bug.cgi?id=291963 ?
I must have missed that one, thank you for the pointer, I'll take care
of it.
I think "all that text" was great input. Sorry if push some more work
your way by asking for a lot of bugzillas but there are two very good
reasons for doing that. Both of them positive:
1. We must have a bugzilla to continue the work and spec things out.
When I ask you to enter one it is a way for me to say - yes, let's take
this to the next level.
2. You initiated the discussion and should have the credit for that so
you should own the bug.
Don't apologize for asking me to create bugzillas, that's the reaction I
was hoping for, because it means you consider these points valid.
Best regards and thank you for your helpful answers,
Johannes
