developer toolbox

reference koje sam tokom rada zabilježio

eclipse¶

http://www.vogella.de/articles/EclipsePlugIn/article.html

http://www.ibm.com/developerworks/library/os-eclipse-plugindev1/

http://www.ibm.com/developerworks/opensource/library/os-eclipse-api-tools/index.html

Import Format

When plug-ins are imported, a project is created in the workspace for each plug-in. The project has the same name as the ID of the plug-in being imported.

As for the content of each project, it varies by import format:

1. Binary projects: The plug-in content is copied into the project. The binary code remains intact in a JAR; while, the manifest files and other resources are extracted to the project root. The advantage of binary projects is that they allow you to browse the code without the overhead of compiling the source code.

2. Binary projects with linked content: The plug-in content is not copied into the project. Instead, links are created in the project to map to the actual physical location of the JARs, files and folders on disk. The advantage of this type of import over a regular binary import is that it is faster to import; since, the operation only involves creating links. The disadvantage of this approach is that linked binary projects can become out of sync and have to be re-imported if the absolute path to these linked files are changed in the file system.

3. Projects with source folders: The source code for the plug-ins being imported gets extracted and placed in source folders. The advantage of this type of import is that you will be able to modify the imported source code. The disadvantage of this approach is that the code gets compiled and results in an overhead whose magnitude is proportional to the number and size of plug-ins imported.

birt jasper¶

http://it.toolbox.com/blogs/jjflash-oracle-journal/jasperreports-vs-birt-an-update-30516

http://dev.eclipse.org/newslists/news.eclipse.birt/msg16434.html

http://www.paolocorti.net/2007/06/05/deployment-of-birt-reports-by-email/

http://www.eclipse.org/birt/phoenix/deploy/

radrails, dltk¶

http://update15.aptana.org/rails/1.3.0.25649/index.html

http://blog.hulihanapplications.com/browse/view/12

http://update15.aptana.org/studio/25823b/index.html

http://robrohan.com/projects/afae/

http://developer.apple.com/Tools/developonrailsleopard.html

http://dev.eclipse.org/newslists/news.eclipse.technology.dltk/maillist.html

The Eclipse Dynamic Languages Toolkit Project is a tool for vendors, researchers, and end-users who rely on dynamic languages. DLTK is comprised of a set of extensible frameworks designed to reduce the complexity of building full featured development environments for dynamic languages such as PHP and Perl.

prvo sam se sahatima borio sa eclipse-om i dltk instalacijom

pokušao sam na 3.5 SDK verziju eclipse-a unzip-ovati dltk-core i dltk-ruby ali nakon toga nisam uspjevao dobiti ruby perspektivu