erixtekila wrote: >> Wouldn't it make a lot more sense to look into how Eclipse handles >> this? We don't need to define an interface, we just need to build to >> one. >> >> I've been starting to build some little Eclipse plugins, and let me >> tell you, it handles a ton of stuff so you don't have to. > Who wrote this ? > http://osflash.org/eclipse/plugin_development_guide
That was me. :) > If other have good (open) ressources to learn the how to build Eclipse > plug-in. sure, http://eclipse.org/articles http://wiki.eclipse.org/index.php/Eclipse_FAQs The rcp newsgroup is very useful, obviously it is mainly about RCP development but there is a lot of knowledge that applies to both general plugin development and RCP. news://news.eclipse.org/eclipse.platform.rcp In fact the real difference between building a plugin for eclipse and building an RCP application is which other plugins and API's are you going to make use of. The great thing about developing for eclipse using eclipse is that at any time where you are using an API call into the platform code you can just F3 and jump straight into the source..which is generally very well commented. And last but not least the in-built help is actually really good, theres places where it just seems to miss out what you want, but mostly its a great 1st resource. oh, one more...its sometimes useful to check the eclipse bugzilla as well because it contains more than just bug reports :) https://bugs.eclipse.org/bugs/query.cgi that should be enough to get going... If you are building a logger view then you can look at the log console for ASDT as that might show you a rough framework..and if you want to include Log4J support then it could be worth seeing if you can find the source for Chainsaw. Maybe there are some useful techniques in there that you might be able to borrow :) martin. _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
