Antegram 2.34b r4

/** A computer program is a bunch of text files. As a result, an IDE should be little more than a text editor packed with search, syntax checking and refactoring options. Consequence: - Signatures, implementation and comments are better kept together where they belong - This is not clutter and confusion, it is art. - The best way to edit a complex program using 50 source files is to have 50 tabs// in a tabbed editor and view one source file at a time. - The fastest way to navigate code is to know your programs structure by heart. - 80% of screen space in a typical IDE displays implementation details irrelevant to the problem at hand. */ import javax.swing.*; public class Antegram{ // Agree? Then antegram is NOT for you, never mind a 200-500% gain in productivity. static String title= Dump your text editor: use your eyes ; /** Antegram producers tackle complexity using trees, non overlapping windows and smart forms. They keep implementations where it belongs: one click away. Typical antegram developpers neglect UML design and API documentation because its all in there, just more clear and concise. They comment their code better, because comments never get in their way. They structure their programs so well youd burn them as code witches... But then, antegram makes it {Oh so Easy its Unfair} to drag methods, classes and fields around and toggle at will between signatures and implementations. */ static JLabel label=new JLabel( Work/More Fun: www.antegram.com ); public static void main(String[] args){ System.out.println( The commercial license is bundled with Ozoa and supports the development of Antegram II/x-dev, OOgtechs master mind project for a cross language (java/c++/javascript/php/xhtml/css) development environment. ); javax.swing.SwingUtilities.invokeLater( new Runnable(){ public void run(){ JFrame frame=new JFrame(title); frame.add(label); frame.pack(); frame.setVisible(true); }}); } }