Home » Eclipse Projects » Oomph » Oomphing paradigm
| Re: Oomphing paradigm [message #1405156 is a reply to message #1404962] |
Wed, 06 August 2014 18:13   |
 Ed Merks
Messages: 33146
Registered: July 2009 |
Senior Member |
|
|
Christophe,
Comments below.
On 06/08/2014 10:41 AM, Christophe Bouhier wrote:
> Hey there,
>
> I am going through a transformation how I use Eclipse.
> In the past, my workspace was important to me. It had to contain all
> plugins I need, correctly ordered in WorkingSets. Depending on what I
> worked on, I would close/open projects and load a .target file, which
> would compile the stuff and all would run nicely. Loosing this setup,
> was a horrific thought.
:-P
>
> When I heard about Oomph, I wasn't sure what is was about, but now it
> dawns to me, that it changes how one uses Eclipse and the workspace.
Yes.
> In fact, the workspace becomes some sort of volatile container to
> compile stuff and make sure Eclipse can be used at it's full
> potential, but loosing is it not an issue anymore.
No, if you describe what's needed well, you can recover it in minutes.
> In fact, one could argue multiple workspaces are still needed. "Can we
> drop the switch Workspace feature please!"
Actually, it's still potentially useful to have an IDE with lots of
things installed that can also work with various workspaces, but with
Oomph it's also easy just to have on IDE per workspace, which isn't as
wasteful as it sounds, because they all share the same bundles from a
single bundle pool.
>
> The central view for me now is the 'GIT Repositories' view and not the
> Explorer anymore. In fact, I open files from this view more and more
> often, without importing the project at all. The main driver for this
> was the switch to tycho. I run maven builds from the root project, and
> if it builds, I can run the end product from the IDE, but more
> important is commit it to the build server, and I am pretty sure the
> build will succeed.
I see.
>
> What a productivity improvement (already)!
>
> but to be honest, I haven't started to use Oomph yet, but I know
> exactly, how I wish to use it.
> - Setup working sets with projects from git as independent bits
Working sets can be defined to be dynamic using predicates to describe
what should and shouldn't be in that working set.
> - Set the corresponding .target.
Sorry, but .target files suck big time. Yes you can use Oomph to
activate one, but Targlets are a dramatic improvement over what you can
do with "pure PDE", giving you much better control over what ends up in
your target platform and in your workspace.
> (With Xtext, I have an issue with this, as the IDE installed xtext
> plugins need to match the version in the target).
I need that for Xcore as well, you can look at its setup. I created one
for Xtext has well, though it still needs some fine tuning. One of the
very nice things about Targlets is that it unifies the provisioning of
the target platform with that of the workspace. For example, you say
you want Xtext in the TP, so in the Targlet Task you specify which IU
and which p2 update site to get it from. If you also specify to git
clone Xtext and specify that the targlet look at that repo, you'll end
up not only with Xext in your TP, but you'll end up with Xtext source
bundles in workspace (which you can close, because the binaries are also
in the TP)...
> - Set IDE preferences.
Yes, you can record preferences and have the "played back" into each IDE
you ever start...
>
> Productivity will boost even more with Oomph I expect.
Yes.
>
> One more remark, somehow it feels Eclipse should grow closer to git
> repo's.
That's what we're trying to to with Targlet tasks; unify the
provisioning of the TP and the workspace, where the split just depends
on whether you specify a source locator or not. If source is available,
it's put in the workspace, if a binary is available, it's put in the TP
(and if both are available, they show up in both places).
> Example: When opening a Java file directly from the git repo, it's not
> compiled and various IDE functions don't work. Of course this is the
> current state, but I keep thinking, why can't the git repo be a fully
> functional workspace, which is powered by Oomph to get all configured
> correctly?
Just point your targlet at it, and it will put them in the workspace,
and make sure that everything it depends on is also added to the TP
(which might require you to specify in which p2 repo to find them).
Of course ideally, all the projects would specify a *.setup, and then
you'd just choose from the installer (or add project to workspace
wizard) which one(s) you want...
>
> Cheers Christophe
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Current Time: Fri May 10 14:32:44 GMT 2024
Powered by FUDForum. Page generated in 0.03598 seconds |
] 
Search
Help
Register
Login
Home
