|
| Re: p2 for developers ? [message #110606 is a reply to message #110505] |
Fri, 23 May 2008 21:15   |
 Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
I don't have anything specific, but as far as I'm aware, most of the
what has been written so far in the way of docs is on the wiki:
http://wiki.eclipse.org/Category:Equinox_p2
-Andrew
Erik Vanherck wrote:
> Hi guys,
>
> After bitching about update manager and following the first discussions
> of the provisioning work I've been out far too long ..
>
> I'm trying to dive back in p2, as an integration developer, trying to
> see how I can write our next gen installer around it. This is proving to
> be a little tedious as there isn't much to go on. A lot of plug ins and
> very little in an architectural overview documentation or even javadoc
> for that matter. Burying the source of the example installer in the
> eclipse CVS repository makes it even harder.
>
> If someone has anything lying around I haven't found yet (presentation
> or so) that would be great. The wiki pages and the source itself aren't
> all that helpful.
>
> Now I know the code isn't API yet, because you are waiting for feedback,
> but this situation does make it a bit difficult to provide feedback. I'm
> sure I'll find my way around eventually but others might simply give up.
> This would be a shame.
>
> I've seen a lot of blogs recently about p2, good and bad .. and they all
> tend to focus on the default UI tooling. I can imagine people being
> unhappy with those but it's unfortunate that they would trash it without
> knowing that they can actually write their own UI. Something that in the
> update manager was hardly feasible due to the monstrous amount of bugs
> (I've never understood how the UI was able to work so well, while the
> back end was filled with multi core races).
> Anyway, so does anybody know of some more detailed implementation docs
> or a short intro which classes I would need to weave together as a first
> step?
>
|
|
|
| Re: p2 for developers ? [message #110655 is a reply to message #110505] |
Sat, 24 May 2008 05:39 |
Eclipse User |
|
|
|
Originally posted by: amottadelli_remove.tele2.it
Update manager proved to be good enough for us. Buggy, yes... but still
simple enough to understand and use.
All after all I must say that UM provided a great value to our
environment and our application.
After more than one year lurking around in forums and in code I must say
that I still have to grasp the P2 whole picture. (For sure, it requires
more than 5 minutes-per-week).
Regards,
Sandro
|
|
|
| Re: p2 for developers ? [message #111130 is a reply to message #110505] |
Fri, 30 May 2008 19:50 |
Pascal Rapicault
Messages: 333
Registered: July 2009
Location: Ottawa |
Senior Member |
|
|
If you want to go headless, the Director class is a good start, so is the
installer code.
If you want to go with a UI, there are a variety of building blocks (or
wannabe) that you could start from and get inspiration from.
If you have more precise questions maybe driven by a concrete use case then
we could help you more precisely
HTH,
PaScal
"Erik Vanherck" <Erik.Vanherck@inventivedesigners.com> wrote in message
news:e023ee448806b6ff717fc04c37a15d52$1@www.eclipse.org...
> Hi guys,
>
> After bitching about update manager and following the first discussions of
> the provisioning work I've been out far too long ..
>
> I'm trying to dive back in p2, as an integration developer, trying to see
> how I can write our next gen installer around it. This is proving to be a
> little tedious as there isn't much to go on. A lot of plug ins and very
> little in an architectural overview documentation or even javadoc for that
> matter. Burying the source of the example installer in the eclipse CVS
> repository makes it even harder.
>
> If someone has anything lying around I haven't found yet (presentation or
> so) that would be great. The wiki pages and the source itself aren't all
> that helpful.
>
> Now I know the code isn't API yet, because you are waiting for feedback,
> but this situation does make it a bit difficult to provide feedback. I'm
> sure I'll find my way around eventually but others might simply give up.
> This would be a shame.
>
> I've seen a lot of blogs recently about p2, good and bad .. and they all
> tend to focus on the default UI tooling. I can imagine people being
> unhappy with those but it's unfortunate that they would trash it without
> knowing that they can actually write their own UI. Something that in the
> update manager was hardly feasible due to the monstrous amount of bugs
> (I've never understood how the UI was able to work so well, while the back
> end was filled with multi core races).
> Anyway, so does anybody know of some more detailed implementation docs or
> a short intro which classes I would need to weave together as a first
> step?
>
|
|
|
Powered by
FUDForum. Page generated in 0.04019 seconds
] 
Search
Help
Register
Login
Home
