As part of our “Give Orbit some love for Helios” initiative I started adding categories to Orbit repositories. Whenever you include an Orbit p2 repository in your target platform, you’ll now be able to cherry pick only the bundles you really need from a convenient set of categories. No need to download any unnecessary overhead.
Try it out yourself. Here is a link to an Orbit p2 repository with categories:
I also captured a screenshot for your convenience:
Frankly, I’m not a creative guy but I had to come up with some categories. Your feedback on the categories is really appreciated.
Are you interested in SWT API for the Windows Ribbon Framework? If yes please raise your voice in bug 293637. It looks like the Ribbon can’t be used in the SDK or any other Eclipse project at the moment. However, it’s still unclear if it can be part of the SWT API.
Have you seen a software that cautions users against itself? No?
There is only one guy in the universe that – despite traveling a lot recently – can deliver two tutorials on the same day at the same time.
I’m wondering now if modeling solved the problem of cloning. Anyway, I just registered today to be there and watch that happening. 🙂
I came across this couple of times before and I always wanted to blog about it. In my daily work life I see many developers which just don’t get Open Source. For example, some discover issues in libraries they use. But they don’t fix them. They don’t even inform the maintainers of a library. Yet others have a great new use-case to address. Again, the library doesn’t support it. Thus, they write a great deal of new code to address their issue and eventually run into new ones (for example, see this thread).
But it’s that darn simple!
- Checkout the library from source. You can use a well known tag/branch for this.
- Get in touch with the maintainers and implement your modifications.
- Build and release your modified version until a new official release is available.