| Re: [ecf-dev] Remote Service Tooling: Endpoint discovery and import |
|
On 4/7/2015 4:40 AM, Wim Jongman wrote:
Hi Wim. Although I like this icon, and think that we should keep/add it so that we can use it in the future, I would like to stick with the existing Endpoint icon for Mars for the following reasons: 1) To my eye, what I've got for Endpoint visually stands out better than the above, and for first release I would like to have something that stands out relative to the other parts of Eclipse tooling. 2) AFAIK, we are introducing the concept of an 'Endpoint' (in the Remote Service/RSA context), and I would like to establish that visually and conceptually. I think that the 'E' in the existing icon helps do that (gives a textual as well as visual reminder of what it's representing). I would, however, like to add this icon to our set, and then we could use it for other RSA concepts when we need it. Would that be OK with you? Also...if there are people that are more fascile than I am (probably all of you) with Gimp/image editor, and want to improve/do more anti-aliasing/improve the icons that are there I would welcome that. After spending time with Gimp over the weekend, I just don't have the eye and Gimp editing skills to do that effectively for icons. Now...about the build...although I appreciate your work on the build today, I think it might be easier for releng and deployment if I were to simply move/contribute all of what's currently in the project at [1] into the already-existing EF bundle: org.eclipse.ecf.remoteservices.ui. Then we wouldn't need a new project/build/repo, it would simply be there in subsequent releases (Mars). Also, then we could have this new view in the new Remote Services perspective by default, and know that it was there without further installation by users...other than installing what we have now. How would that be? OTOH, it might be useful to create a new feature to contain *just* the Remote Service tooling (and dependencies), so that consumers could install (into Eclipse) *just* the Remote Services tooling parts of ECF. I'm currently torn somewhat about that, however, because the way it is now maybe just fine...i.e. if people install ECF sdk into Eclipse (not a huge install at all relative to most other projects), then they will get this RS perspective/views/tooling along with the Communications perspective and other stuff. Actually, now that I think about it I think we would have to do a fair amount of feature refactoring to do this (allow only the install of RS tooling), so I think that must/should wait for another release. To summarize: my proposal is that I move everything from the github project over to org.eclipse.ecf.remoteservices.ui, and then we won't need another releng/build/project, etc, and we can use the existing feature structure for Mars. I apologize for not stating this clearly prior to your work on the releng over the last day. Scott |
