We are always looking for more people to write for EDM/2, and therefore I have put together this page to show what we want the most. To write a column, you must first give me 3 columns up front. To stay a columnist, you must write every month. The payoff is in an e-mail address at EDM/2, and a growing personal reputation. To write a series, I need all the installments from you before the first one is published. This is to prevent aborted series. Case in point: our two most popular series were aborted when the authors were hired away. You can write a series in two or three article independent chunks if writing up the whole series is too much work up front. The key here is the word independent. To write an article, write it up, send it in :) Of course, if you would like to write an article or a series on a "column" topic, that is ok too, until I get a columnist. For all of these three, there are a few requirements: You must be 99% sure that it is 100% correct We prefer about 1500 words or more (about two pages typed), but if you cannot write this much for some reason, get in touch with us anyway You must be willing to field questions on your article by e-mail Columnists Wanted: Java for OS/2 and the Internet - You must teach Java from scratch, but not stop there Beginning PM in C - You must write a column similar to Larry Salomon's old column Intermediate PM in C - You must coordinate with the previous columnists to teach more Advanced OS/2 topics - You are free to teach anything advanced you like Multimedia in OS/2 - You will write about DIVE, DART, and other MM technologies Classic Computer Science Problems in OS/2 - You will show how to implement classic CS (reader/writer, etc.) problems in OS/2 REXX Book Reviewer - You will read one REXX book a month, and review it according to guidelines Visual REXXes - You will demonstrate both VX-REXX and VisPro REXX in this column - NOTE: Watcom may not promote VX-REXX any more, in which case you focus on VisPro REXX OS/2 C++ Book Reviewer - You will review C++ books for OS/2, and related topics Low-level OS/2 - You will write about low-level issues, such as HPFS details Articles Wanted: DLLs in C DLLs in C++ REXX DLLs in C++ The Visual Age C++ programming environment Setting up a commandline environment Working with source code revision systems Designing custom controls Hooking into OS/2 with the WPS GPI programming etc. etc. If there is something that you want to write about that was not in any of the lists above, don't worry. This is purely because of lack of imagination. Send it in anyway! Submission Format Content While everyone from you (the authors) to us (the editors) is doing this on a voluntary basis so far, we would lose readers if we did not strive for a high level of quality. Since this magazine was formed with the intent of disseminating information to the multitude of programmers unsatisfied with the lacking documentation provided by IBM, it would only serve to defeat the purpose of the magazine if we did not do so. Thus, we humbly request that the following checklist is performed before submission. Check that all information is accurate Check your spelling Liberally comment your source code samples Keep code to about 60 characters wide, max., including comments. Insure that your source code samples compile and run properly Use JPG format *only* for photographs. For everything else, use GIF. Graphics Include graphics separately, even though some word processor allow you to include them right in the document. Use either GIF or JPG format (see note above), and keep the graphic as small as possible. Maximum width is 480. Put a reference to the graphic in the document instead, like this: [pic1.gif] Using Abbreviations As you write your article, you should keep in mind that many people aren't going to know a lot about what you are writing. Because of this, abbreviations should be accompanied by expansions in brackets for the first occurrance. More guidelines Our preferred submission format is plain, neat ASCII, with a maximum width of 80 characters per line. All paragraphs should start at the left margin, as should headings. Headings should be capitalized, not all caps, and should be on a separate line, for example: Getting Started: This Is How To Do It Figure should be numbered starting at 1, and accompanied by a line that says, for example: Figure 1: The crux of the matter. All text figures should be included right in the document, not separately, as should all "Figure" lines. All code should be maximum 60 characters wide, due to the difficulty of presenting code satisfactorily in HTML within 480 pixels. Code should be tidy, and well commented. Final Details Before your task is complete, make sure you write a short blurb about yourself in third person, in a separate file; this will go on your author page. Try to avoid using dates, since they go out of date quickly. Browse through our current author pages to see what I mean. Please include your electronic mail address and specify on what network it resides. Zip the source file, the biography file, and any graphics files, and mail it to the editor-in-chief. Finally, we thank you for your cooperation with these guidelines. Remember, you are doing a great service to the OS/2 community by writing for EDM/2. Be proud of it! Sincerely, The EDM/2 Editors