home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 14 Text
/
14-Text.zip
/
writer.zip
/
WRITERS
Wrap
Text File
|
1995-03-20
|
14KB
|
318 lines
3/95
_______________________
OS/2 DEVELOPER MAGAZINE
WRITER'S GUIDELINES
_______________________
"The Magazine for Advanced Software Development"
The OS/2 Developer is a bi-monthly publication founded by IBM in 1988
and now owned by Miller Freeman, Inc. It is aimed at both commercial
and corporate OS/2 application developers. Articles about OS/2
features, functions, projects, tools, tips and techniques are
solicited from OS/2 experts, software vendors and customers. This
document summarizes the requirements for submitting articles to the
magazine.
We're looking for articles that...
- Simplify the OS/2 application development process
- Explain OS/2 Warp features and functions that promote usability
and improve performance
- Provide how-to advice on graphical user interface, object
oriented programming, client/server, and other advanced programming
techniques
- Expedite conversion of DOS and Windows applications to OS/2 32-Bit
platform
- Create better applications using OS/2 development tools
- Share tips & techniques, questions & answers, programming examples,
and real life case studies
OS/2 Developer Departments
- Graphical User Interface - Resources (seminars, books)
- OS/2 2.X (32-Bit) - Hardware Exploitation
- OS/2 Database Applications - Graphics & Multimedia
- OS/2 Communication Applications - Multi-User Systems
- OS/2 Local Area Networks - OS/2 International
- Software Tools - Spotlight Feature
- Application Enablers - Performance
- Systems Application Architecture - Manufacturing
- Client/Server Programming - Object Oriented Programming
- Printing - Product Watch
- The Advanced Novice - Speech Recognition
OS/2 Developer Features & Columns
- Programming Insider (Dave Reich) - Product Watch
- GUI (Mark Benge and Matt Smith) (New OS/2 tools & utilities)
- Tools Reviews (Guy Scharf) - Buyer's Guide
(OS/2 tools supporting the
theme of each issue)
Compensation
OS/2 Developer currently does not pay for submitted articles.
However, many of our authors have received offers to write books
and speak at technical conferences. IBM employees receive
compensation from their site Author Recognition programs.
STEP 1: Nominating an Article
- Send a short outline of your article to the Editor. Estimate the
number of drawings, screen shots, and lines of source code. In
which department (see above) does the article belong?
- We will give you a tentative yes or no for inclusion in an upcoming
issue. Upon receipt of final copy, we will confirm our intent to
use your material. We reserve the right to use or reject an
article at any time. Generally, theme articles (see Calendar) take
priority.
STEP 2: Submitting Your Article
* * * ALL ARTICLES MUST FOLLOW THESE GUIDELINES * * *
- Deadline: send the article text (softcopy) to the Editor before
the published deadline (see calendar).
- Content: 5 - 7 pages maximum, single-spaced. Keep the article
brief by summarizing the main points, using illustrations and short
examples, and by referencing other sources. Remember: you may not
be able to tell your readers everything they'll need to know about
a programming technique or software tool in one article. Cover the
highlights and refer readers to reference publications for more
detail. Excessively long articles will be returned for rewriting.
Priority should be given to OS/2 Warp 32-bit functions, examples,
tools and applications. Please, no PR pieces! Make sure your
article reflects the latest release of OS/2. And remember -- you
are writing for developers, not end users. Our readers want
articles with hands-on, how-to programming examples, with actual
working code. Appeal to their technical knowledge.
- Software tools: An OS/2 software development tool may be described
in your article, as long as it is secondary to the technical theme.
In other words, it's OK to review a tool's features, but our
readers are looking for ways to write better applications. Start
by defining a problem or application development scenario that the
tool addresses. Give examples and case studies. Save the product
features and functions for last.
- Security: unclassified at time of publication. If product hasn't
shipped, include a disclaimer saying that function may be added,
deleted, or changed in the final product.
- File format: Store the article text in a file by itself, separate
from artwork. Use the DOS ASCII format, free of any formatting or
control characters. Margins: flush left, no hyphenation, width
70. Include references and captions for all artwork, e.g.,
<insert Figure 3 - screen shot - "Display of Coding Example">.
Name the file after the author contact's last name (SMITH, JONES,
etc.). Send the file to the Editor electronically or on a 3.5-inch
diskette.
- Title: Keep title short and simple, e.g., "Using 32-Bit APIs to
Improve Performance".
- Identifying information: At the top of your article, please
include the following:
Article title:
Issue: Section:
Author contact:
Author phone:
Fax:
E-mail:
Address:
- Headings: Show level of each heading (use two heading levels and
bulleted lists beyond that). Example: Improved Performance
<head>, Final Fine-Tuning <subhead>.
- Artwork: Keep diagrams, tables, etc. separate from the text file;
fax or mail your sketches to us (we redraw all illustrations, so
don't spend time creating computer diagrams).
- Code listings: May be added at the end of the article.
Well-commented, width 70. Be sure to test your code! Give each
code segment a figure number and caption. Limit your code examples
to the minimum number of instructions needed to make a point. If
you like, you can also give us a separate file containing a full
sample program ready for compilation. We'll put it in our
CompuServe OS2DF2 library for downloading by our readers. If you
do this, refer to the CompuServe file in your article. That file
should be commented as follows:
/* Program name: XXXXXXXX.XXX Title: */
/* OS/2 Developer Magazine, Issue: XXXXXX '95, page XXX */
/* Article title: */
/* Author: Phone: Fax: */
/* Description: */
/* */
/* Program requirements: */
/* */
- Screen shots: We have a screen capture program which creates .PCX
format files. Please request a copy from the Managing Editor or
use a compatible program. No screen photos. Limit: three or
four screens per article. Include references and captions in your
article text.
- Authors: Credit all authors, designating one person as our contact
person. A short, one-paragraph biography (see previous issues for
examples) with a mug shot (color or black and white) must be
provided of each author. Include your current job title,
responsibilities, career milestones, college and degrees, company
address, e-mail ID and phone number in your bio.
- References: Include a References box at the end of the article.
List all bibliographic references: book or article titles,
publisher, city and date of publication, and page numbers if
applicable. If a reference is an IBM publication, include its IBM
order number (eg., G362-0001-02). If you refer to a publication in
the text, list it under References. References can include any
hardcopy or disk-based information shipped with OS/2 or a software
tool.
STEP 3: Reviews and Approvals
- IBM authors: Site review (Communications, Legal, Intellectual
Property Law) is required; check to see if your site has an Author
Recognition Program (ask your manager or site communications
department). Make all review changes during the editing cycle.
- Multiple authors: Designate one author as our prime contact. This
person is responsible for procuring all art, photos, etc., and
distributing galleys for correction to other authors.
- Author release: Miller Freeman, Inc. requires you to sign a
release form that certifies the article's originality. Generally
we want articles that have not been published elsewhere. Book
excerpts may be used if the publisher gives permission.
- Selection: Articles must be submitted by the published deadline
unless a later date is approved by the Editor. Late submissions
are accepted on a first-come basis where last in is first bumped.
We do overbook, so if your article is bumped from an issue, it may
be a candidate for the next one. Selection criteria include
conformance to these guidelines, the theme of the issue, article
length, and the number of available editorial pages.
STEP 4: The Pre-Production Cycle
- The Editor will review and edit your submission and forward it to
the Managing Editor, who will contact you about grammatical editing
and artwork. Your article will be faxed to you with editorial
changes for your review. You will see the article once again in
page-layout (camera ready) format for final approval. Only typo
corrections and emergency changes should be made to this version.
Either the prime author or a knowledgeable representative must be
available during this period to ensure quick turnaround.
- IMPORTANT: once you send us a softcopy of your article, don't
continue to make changes to your file or you'll get out of sync
with the in-edit version. Instead, give your changes to the
Managing Editor by fax or telephone. Once the article is in
production, there should be no rewrites.
Post Production
We encourage authors to communicate with readers and with each
other. Join the OS/2 Developer Mag section on CompuServe (GO
OS2DF2).
OTHER INFORMATION
Reprints
- Article reprints may be ordered from Miller Freeman. Quantity
prices are furnished on request. Call Stella Valdez at Miller
Freeman, 415-655-4269.
Editorial Calendar (revised 3/95)
Issue Theme Articles Due
~~~~~ ~~~~~ ~~~~~~~~~~~~
JULY / AUG: OOP; Taligent Frameworks; March 27, 1995
OpenDoc
Rexx Report Special issue on OS/2 Rexx March 27, 1995
Application Development
SEPT / OCT: OS/2 for PowerPC; Database May 29, 1995
Development
Smalltalk Special issue on OS/2 ??
Report Smalltalk Application Dev.
NOV / DEC: Client/Server Development; July 31, 1995
Downsizing
Advertising
- The OS/2 Developer is the best way to reach the OS/2 community with
news of software tools, publications, products and services. Ad
rates and schedules can be obtained from:
Yvonne Labat 415-905-2353
Kristin Morgan 212-626-2498
Christian O'Brien 212-626-2322
Subscriptions
- Through the Publisher: Miller Freeman Inc., (800) WANT-OS2 ($39.95
yearly). Outside of U.S.: 708-647-5960 or e-mail SHall@MFI.Com.
- Through IBM: Systems Library Subscription Service (SLSS) order
number G362-0001. Copies of current issue can be ordered through
PUBORDER. (Note: SLSS is accessed on the HONE system; PUBORDER on
VM).
- Members of IBM's U.S. Developer Assistance Program may apply for a
qualified (free) subscription. Call 800-WANT-OS2 and ask for a
qualified subscription application.
Book Compilations
"OS/2 2.X Notebook", published by Van Nostrand Reinhold in
February, 1993, contains articles from OS/2 Developer, 1991-1992.
Available in book stores, from IBM (order number G362-0015), or
direct from the publisher, (800) 842-3636. The original OS/2
Notebook (1990) is available from IBM (order number G362-0003).
Staff
Publisher: Peter Westerman, (415) 905-2392
Internet: PWesterman@MFI.Com
Mail: Miller Freeman, Inc., 600 Harrison St.,
San Francisco CA 94107
Editor-in-Chief Dick Conklin, voice/fax (407) 495-4421
CompuServe: 76711,1005
Internet: OS2MAG@VNET.IBM.COM
IBM: BCRVM1(CONKLIND), IBMMAIL(USIB12H2)
Mail: 3408 Sherwood Blvd.,
Delray Beach, FL 33445
Managing Editor: Marta Dils, (415) 905-2777, Fax (415) 905-2234.
Internet: MDils@MFI.COM
Mail: Miller Freeman, Inc., 600 Harrison St.,
San Francisco CA 94107