Hi Stephen, On Fri, Aug 7, 2009 at 4:41 AM, Stephen Evanchik<[email protected]> wrote: > Hi David, > > On Tue, Aug 4, 2009 at 4:58 PM, David Savage<[email protected]> wrote: >> Hi there, >> >> Just to let you know some progress on sigil in terms of self hosting. >> I've now managed to get sigil to such a stage where I can build the >> eclipse bundles using the apache sigil ivy integration and run them in >> eclipse to edit the apache sigil source. I'll write up some docs on >> this on the wiki in due course. > > This is great. I have not looked at Sigil since the move to Apache. > Now that it is self-hosting I'll check it out.
Thx great to have some feedback, obviously there are still some rough edges at the moment due to the move and just in general due to time constraints but hopefully with the code on Apache it will get some good eyeballing and we can progress it further. > >> >> The next thing I'd like to look at is runtime support to allow me to >> close the loop and debug sigil using sigil then we should be able to >> make rapid progress. It was discussed that the runtime support should >> probably be based on the RFC 132 launching api. Just wondering if >> anyone can point me in sensible directions in the felix source to go >> look into this? > > I am curious to know what you mean by this? FWIW, I have committed an > Eclipse PDE OSGi Framework launcher for Felix at the Eclipse > Integration for Karaf project I run here: > http://fusesource.com/forge/projects/EIK So the idea is to create an Eclipse PDE Framework Launcher hooked into the Sigil project model that uses the RFC 132 launching api vs a framework specific mechanism. This would allow sigil to launch any OSGi framework from this common API. There are some gotcha's here though - it looks like the equinox 3.5 release and the spec didn't quite meet - so from my testing so far it looks like equinox is expecting some framework specific headers that aren't in the spec :-s. I haven't yet tried the equinox trunk so perhaps this is fixed by now? My main driver for this is I want to be able to boot equinox with sigil built bundles and eclipse plugins to do debug support - not to much to ask ;) > > I have been working on WTP integration and started building project > Natures, Facet installers and realized that the world didn't need yet > another set of OSGi project tooling inside of Eclipse. > > Do you think it makes sense to collaborate in a way that makes it easy > for people using Sigil to develop Karaf based applications? That would be great, definitely good to get some community around this. For myself I'd like to engineer sigil so it focusses on OSGi and then add extension support (such as Karaf, PDE, Blueprint, etal.) as extensions to the tooling. That way we get to build a really solid base layer for development (much as Felix, Equinox and Knopflerfish have done for the runtime). In the Dev Tooling Summit I attended earlier this year we discussed the fact that in the end it would be great for OSGi tooling to agree a common set of standards on which lots of different tooling vendors can hook into. Of course we also need to avoid the curse of early standardisation so baby steps are good but I see Apache as a great place to have these conversations - hopefully we can feed back some useful new ideas... > > I'll grab the Sigil source now and do a build and poke around but I > think with EIK supporting Karaf on Equinox and now also on Felix from > within PDE it makes sense for me to start thinking these sorts of > things. By way of an apology/warning setting the project up in eclipse is a little fiddly at the moment as you need to set up your repository config in the ide to match that set in the ivy build. There's an issue open for this here: http://issues.apache.org/jira/browse/FELIX-1355 Probably the most useful starting point for exploration from the eclipse side of things is the interface: org.apache.felix.sigil.eclipse.model.project.ISigilProjectModel This represents a project and provides utility methods for navigating the classpath that the various bundle import/export statements imply. >From this it is possible to build a launch config for the RFC 132 launcher discussed earlier (I've done similar in the past for newton when sigil was hosted on codecauldron.org but couldn't port that code to apache due to licence restrictions - but we should be able to rebuild this in the open without /too/ much pain) > >> >> Also if anyone has any graphics skills sigil is currently lacking any >> form of icons - which gets a bit dreary in the IDE, I've raised an >> issue for this [1] in case anyone wants to jump in and help out... > > It seems we're all in this boat ;) > > You can read more about EIK at my blog: > http://stephen.evanchik.com/category/entries/life/open-source/karaf or > watch Oisin's screencast: > http://eik.fusesource.org/documentation/tutorial.html for a great > summary. Thx I'll take a look :) > > Oisin and I haven't had time to really document things but between the There's that boat again ;) Regards, Dave > screencast and the blog you'll get the idea where things are going. > > Stephen > > -- > Stephen Evanchik > http://stephen.evanchik.com >
