text:
User talk:89.164.235.134

Join Us!
-- – Mike.lifeguard  | talk 18:46, 28 January 2008 (UTC)

title: User talk:89.164.235.134


text:
Futurebasic

The Wikibook project supports the development of the FutureBASIC programming language. FutureBASIC, also known as FB, is a compiled procedural BASIC dialect used to develop applications for Apple Macintosh family of computers.

If you would like to contribute energy to the FB Documentation Project, please read our Style Guide for FB Documentation.

Language Reference and Programming Guide
The Language Reference focuses on the FutureBASIC language and syntax. While programming is discussed, this is primarily to demonstrate the language syntax. The Programming Guide offers far more detail on accomplishing specific tasks. The Beginner's Guide is primarily concerned with how to use the FB IDE and compiling programs. It exists to explain the process of compiling applications, not as a replacement for the Programming Guide.

 * 1) The FutureBASIC Language
 * 2) FB Syntax and Language Elements
 * 3) Variables
 * 4) Data Types
 * 5) Numeric Expressions
 * 6) String Expressions
 * 7) Screen Output
 * 8) Console Applications
 * 9) Command-Line Applications
 * 10) Command-Line Applications
 * 11) Working with Windows
 * 12) Files and Folders
 * 13) FSSpec (File Spec) Records
 * 14) FSRef Structures-- Modern Approach
 * 15) FSRef Structures-- Legacy Discussion
 * 16) CFURLRef Structures
 * 17) POSIX Paths (Not posted)
 * 18) Path Conversion Functions
 * 19) Print Commands
 * 20) A Beginner's Guide to Using FutureBASIC
 * 21) Editing FutureBASIC code
 * 22) The "Hello World!" Example: Compiling Your First Application
 * 23) Programming Guide for FB (and FBtoC)
 * 24) Carbon and Why it Matters
 * 25) Developing Structured Code
 * 26) Flow Control
 * 27) Local Functions
 * 28) Event Driven Programming (Not posted)
 * 29) Event driven Programming with Carbon Events (Not posted)
 * 30) Introducing User Interfaces
 * 31) Creating and Using Menus (Not posted)
 * 32) Working with Windows (Not posted)
 * 33) Working with Controls (Not posted)
 * 34) Dialogs and Alerts (Not posted)
 * 35) Working with FIles and the File System
 * 36) Interaction with the Finder (Not posted)
 * 37) Reading & Writing Files, Navigation-Services (Not posted)
 * 38) Manipulating Data
 * 39) Working with Text Values
 * 40) Working with Numeric Values
 * 41) Working with Dates
 * 42) Working with Arrays
 * 43) Working with Records
 * 44) Working with Graphics
 * 45) Drawing with Core Graphics (CG) (Not posted)
 * 46) Drawing with OpenGL (Not posted)
 * 47) Printing from FutureBASIC (Not posted)
 * 48) User Interfaces
 * 49) NIB-based Graphical User Interfaces (Not posted)
 * 50) Advanced Menu Programming (Not posted)
 * 51) Complex Windows (Not posted)
 * 52) Advanced Control Programming (Not posted)
 * 53) More on Dialogs and Alerts (Not posted)
 * 54) Multimedia and FutureBASIC
 * 55) Sound and Music
 * 56) Videos and More
 * 57) Advanced Application Topics
 * 58) Text & Multilingual Text (Not posted)
 * 59) Introduction to Core Foundation (CF) (Not posted)
 * 60) Resources & Application Bundle (Not posted)
 * 61) Preferences Files (CF-Prefs) (Not posted)
 * 62) Threading in FB (Not posted)
 * 63) AppleScripting with FB (Not posted)
 * 64) Other topics are also planned!
 * 65) Language Reference (Not every page of the complete LR is posted - yet!)
 * 66) Using FBtoC
 * 67) Beginners Guide to Programming Fundamentals
 * 68) Glossary of Terms

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Futurebasic


text: User talk:198.203.102.251

title: User talk:198.203.102.251


text:
Futurebasic/Language

The FutureBASIC Language
FutureBASIC (FB) is a high-level procedural programming language—in fact a whole "Integrated Development Environment" (IDE)—for the Apple™ Macintosh® computer system. It is a compiled BASIC dialect allowing easy access to the graphical user interface and file system of the MacOS. In providing structures such as nestable records and arrays, and various forms of subroutines (local functions) and callbacks it is quite as powerful as C however with the syntax of BASIC and a less strict variable typing. FB features an editor, compiler, debugger, profiler, project manager, documentation, and code samples.

The current version is FB4 Release 4. Since January 1, 2008, FutureBASIC is freeware.

Language Reference

History of FutureBASIC
FB began life in the mid-1980s as ZBasic, which was created by Andrew Gariepy and envisioned as a cross-platform development system. Before long, the cross-platform aspects were dropped in favor of focusing on Macintosh development. ZBasic acquired a devoted following of developers who praised its ease of use and the tight, fast code produced by the compiler (a legendary labor involving extensive use of hand-built 68K assembly language code). In 1992 and as the next major step after ZBasic version 5, Zedcor Inc., the company of the Gariepy brothers Andy, Mike, Peter and friends based in Tucson/Arizona presented FutureBASIC (later called FBI). In 1995 Staz Software, led by Chris Stasny, acquired the rights to market FutureBASIC. Chris Stasny started this business with an upgraded version, namely FBII, and with his own development, the Program Generator (PG PRO), a CASE tool.

The transition from 68k to PowerPC CPUs was a lengthy process that involved a complete rewrite of the editor by Chris Stasny and an adaptation of the compiler by Andy Gariepy. This was undertaken during Apple's darkest days when the further existence of the Mac and Apple itself was in the news every week. The result of their efforts, a dramatically enhanced IDE called FB^3, was released in September 1999, featuring among many other things a separate compiler application, various open, hence modifiable runtimes, inline PPC assembly, a simplified access to the Macintosh Toolbox™ API, as well as an expanded library of built-in functions. Major update releases introduced a full-featured Appearance Compliant runtime written by Robert Purves and the Carbon compliance of generated applications. Once completely carbonized to run natively on OS X, the FB IDE was called FB4 and first released in July 2004.

Based in Diamondhead/Mississippi, Staz Software was severely hit by Hurricane Katrina in September 2005 and development pace was slowed at a time when major effort was required to keep the IDE up to date with Apple's evolution towards the Intel™-based Macintosh. More recently, an independent team of volunteer FB programmers developed a cross-compiler (FBtoC) that allows FB to generate applications as Universal Binaries through the use of the open source gcc compiler which is included with each copy of Apple's OS X system software. On January 1, 2008, Staz Software announced that FB4 would henceforth be freeware and FBtoC 1.0 was made available at http://www.4toc.com/fb4/

From System 6 to MacOS X on Intel, the longevity of the FutureBASIC development system on the Mac Platform is second to none.

title: Futurebasic/Language


text:
Futurebasic/FBtoC

What is FBtoC?
FBtoC is a replacement for the FB Compiler (FB Compiler.app). Translating the code to C allows Apple's developer tools to create a universal binary. The diagrams below illustrate the process:

FBtoC translates appearance projects and standalone files, and console-type text-only standalone files. PG projects cannot be translated. Using FBtoC normally requires no detailed knowledge of C.

Why translate to C when I code in BASIC?
 The compiler (gcc) has more powerful optimizations for speed than the FB compiler. Native Intel code runs ≈3 times faster (or more) than PPC code under Rosetta. Framework access is much simpler than in FB (see later). FBtoC can automatically copy specified files into the app's resources (see later). Apple's modern development tools work on apps built by FBtoC. Tools include the Xcode debugger and the performance analyser Shark. An app can be built as small as 64 KB.(window 1 : print "Hello, world!" : do HandleEvents : until gFBQuit)

On an Intel Mac, crash reports are interpretable, unlike those of a legacy FB app.

Unlike FB, there is no 32k limit on local function variables.

And then there's the coveted Universal Binary status!

Installation
This section describes the installation of both FutureBASIC and FBtoC. Before continuing, you will need to obtain the following:

The FBtoC installation files and documentation from: FBtoC Project Page

The Apple Develop Tools, available on your OS C installation DVD or from Apple's Developer Connection Web site

System Requirements
FBtoC should work on OS X 10.3.9 and later. Most development and testing has been done on OS X 10.4 and 10.5. Before using FBtoC you should have installed Apple's free Developer Tools (a.k.a. Xcode Tools), from your OS X install CDs or DVD.

To create universal binaries, you must have OS X 10.4 or higher, gcc 4.0 or higher, and install the Cross-development SDKs. Without /Developer/SDKs/MacOSX10.4u.sdk, only the native architecture of your Mac can be built. The Finder view (below) of the Developer folder shows the SDKs after installation. Cross-development is an optional part of the Xcode Tools install (from the OS X DVD or CDs).

See also Apple's documentation: Apple Developer Tools Documentation

Installing FBtoC
Just drag-and-drop. The folder containing FBtoC.app must also contain three special folders: build_goodies, Headers, and User Libraries.

The build-goodies folder contains pretranslated parts of the runtime. Changing any of these files is likely to break FBtoC.

The Headers folder contains a subset of the standard FB Headers files. Most of them needed modification to make them work with FBtoC. In general, an existing FB Headers file will not work if simply copied into this folder.

User Libraries has the same function as in FB, except that the little-known special file UserFloatPrefs is ignored by FBtoC.

Mildly bad news
Some things that have to be done differently in FBtoC:

Features not implemented
Due to FBtoC operational constraints and other more obvious constraints (e.g. Intel doesn't support PowerPC assembler -duh), some legacy syntax cannot be implemented. However, a modern equivalent to achieve a similar goal often exists. Updating legacy source code to a modern equivalent benefits from newer features and helps preserve the longevity of the source code.

2. Not currently implemented
appleeventmessage$

def SomeAreButSomeAreNotAvailable

DynamicInsertItems

event&

event%

flushevents // instead use the Toolbox: call FlushEvents( _everyEvent, 0 )

folder

get field

on appleevent

on break

on edit

on expr

on finderinfo

on lprint

on overflows

on stop

override local fn SomeFunction, override runtime SomeRuntimeThing (but override _someConst = 1 IS supported)

parentID

picture field

syserror

timer [function]

3. Toolbox aliases not supported
The TBalias statement in FB allows old Toolbox names to be kept and applied to new functions when introduced by Apple. The idea must have been to save programmers a minute or two updating function names, a task otherwise tiresomely required every few years. The TBalias feature is now Considered Harmful and will not be supported by FBtoC. You may have already upgraded your project to use the correct (Apple's official) Toolbox names. If not, be prepared for FBtoC error messages indicating dodgy names:

•• Unknown statement in line 6 of untitled 6: RmveResource( resH ) ^

The simple, recommended, and only, workaround is to replace each occurrence in your code of the fossil RmveResource by RemoveResource.

Some Toolbox functions that were commonly aliased in old FB code are listed below:

4. Missing Headers files
include "Util_Dialogtests.incl"

•• Include file not found in line 1 of OopsMissingFunction.main 1: include "Util_Dialogtests.incl" ^

FBtoC's Headers folder doesn't have this file yet.

5. Incomplete Headers files
include "Util_Files.incl" dim as FSSpec  fs dim as Boolean  found found = usr FSFileExists( fs )

•• Unknown function in line 4 of OopsMissingFunction.main: FSFileExists 4: found = usr FSFileExists( fs ) ^

Util_Files.incl is present in FBtoC's Headers folder; the error arises because the function usr FSFileExists has been conditionalised out by some petty official, one hopes temporarily. [Note added later: FSFileExists is now implemented]

Sample translations by FBtoC
Elderly FB code preserved in the FBtoC runtime:

CLEAR LOCAL dim pBlk.128 LOCAL FN FBGetFolderName(DirID&,WDRefNum%,@StrPtr&) StrPtr&.Nil$ = "" pBlk.ioDirID&   = DirID& pBlk.ioVRefNum% = WDRefNum% pBlk.ioNamePtr& = StrPtr& pBlk.ioFDirIndex%= -1 long if FN PBGetCatInfoSync(@pBlk) StrPtr&.Nil$ = "Error" end if END FN

long FBGetFolderName( long DirID, short  WDRefNum, long  StrPtr ) { char              pBlk[128] = {}; PLstrcpy( ((StringPtr)StrPtr), "\p" ); *(long*)(pBlk + 48) = DirID; *(short*)(pBlk + 22) = WDRefNum; *(long*)(pBlk + 18) = StrPtr; *(short*)(pBlk + 28) = -1; if ( PBGetCatInfoSync( (void*)&pBlk ) ) { PLstrcpy( ((StringPtr)StrPtr), "\pError" ); } // 'end if' return 0; }

One of FBtoC's many internal functions:

local fn DefinePointRecord dim as VarInfo varInfo BlockZero( varInfo, sizeof( varInfo ) ) varInfo.varType = _shortVarType // for fields fn SuppressTypedefs fn StartRecordDefinition( "Point" ) fn AddFieldToRecordDefinition( "v", "", varInfo ) fn AddFieldToRecordDefinition( "h", "", varInfo ) fn FinishRecordDefinition fn DontSuppressTypedefs end fn

long DefinePointRecord { VarInfo           varInfo; BlockZero( &varInfo, sizeof( varInfo ) ); varInfo.varType = 3; SuppressTypedefs; StartRecordDefinition( PLstrcpy( gFBStrStk[++gFBStk], "\pPoint" ) ); AddFieldToRecordDefinition( PLstrcpy( gFBStrStk[++gFBStk], "\pv" ), PLstrcpy( gFBStrStk[++gFBStk], "\p" ), &varInfo ); AddFieldToRecordDefinition( PLstrcpy( gFBStrStk[++gFBStk], "\ph" ), PLstrcpy( gFBStrStk[++gFBStk], "\p" ), &varInfo ); FinishRecordDefinition; DontSuppressTypedefs; return 0; }

title: Futurebasic/FBtoC


text: Wikibooks:Requests for deletion/City of future


text:
Futurebasic/Language/Reference

E
(Standard BASIC):

(Appearance Manager):

Syntax (Standard BASIC):

Syntax (Appearance Runtime):

Syntax 1:

Syntax 2:

R
To re-route text and graphics:

To re-route text:

Template (to be removed later)
Click here for Template

Go here:  to admire the long list of keywords to work on.

Use template page (the link is just above).

To edit an entry:

1 - Click on the link titled Template (above the list of keywords).

2 - A new page is displayed in your browser showing how the layout of an entry looks like. Click on the top most link on the right of the screen (probably titled [edit] in English).

3 - The browser opens a new page displaying a form. The main field contains the code used to create the template. It looks like the following:

= Layout Template (remove this line) =

== Keyword Goes Here ==

=== Statement Function Operator or Other? (update the checkmarks below) ===

✔ χ Appearance ✔ χ Standard ✔ χ Console

=== Syntax ===

code syntax goes here and is pre-formatted (plain text)

=== Revised ===

Date & release (remove the Revised section if no date)

=== Description ===

Description goes here.

=== Example ===

Sample code goes here (remove the Example section if no sample code)

=== Notes ===

Special notes. (leave this section if no notes)

=== See Also ===

Language Reference 4 - Copy the whole text (you can possibly paste it in a text editor window to have it handy at a later time).

5. - If you haven't already done so, put beer in fridge

6 - Now go find a keyword in the list whose entry is empty, and paste the template code and click on the Save button.

If you're not comfortable with HTML, leave to someone else the updating of the entry and repeat the process for another empty keyword entry (i.e. GOTO #6).

If you want to proceed further:

7 - Open the FB Help page in a new browser window or better a text editor. If you're using a browser you will have to display the HTML source code.

Now, depending on your skill with HTML coupled with wiki idiosyncrasy you might do the following:

8a - Edit again the keyword entry updating each section with the corresponding HTML code of the FB Help page.

9a - Save your change and leave to someone else the pleasure to clean up the mess.

or

8b - Clean up the HTML code in your text editor. Sometimes, there are a bunch of tags to remove and even to use more efficiently, I guess. Leave the links related to the missing image resources, it might help later to find out which entries require illustrations. Maybe Christopher can tell us how we can manage the image files.

FB snippets of code of the Ref manual need serious cleaning since they are inserted inside   tags therefore they cannot embed any other HTML code. Other things are worth to know (perhaps for another post), but I think the rule of thumb is to end-up with the less HTML code as possible.

9b - Update each section of the keyword entry with the appropriate clean HTML code.

10 - Repeat ad nauseum (i.e. GOTO #6) with a variant, though: try to find also keyword entries whose template has not been updated.

11 - Celebrate in true Staz style (with beer) when you're done (optional).

title: Futurebasic/Language/Reference


text:
Futurebasic/Language/Reference/Define

Statement
✔ Appearance ✔ Standard ✔ Console

Syntax

 * 1) define newTypeName as oldTypeName
 * 2) define newTypeName as {pointer to|@|^|.} oldTypeName
 * 3) define newTypeName as {handle to|@@|^^|..} oldTypeName

Description
The  statement is one way to create a name for a variable type (the other way to do so is to use the   statement). can be any new name you like that is different from the names of all existing types. is the name of an existing type; this can either be a built-in type such as  or , or a type which you created previously, in a   statement or in another   statement. After the  statement, you can declare variables of the new type using   statements, and you can pass   to the   and   functions. If you use the first syntax,  essentially becomes a synonym for. If you use the other two syntaxes, then variables of the new type are recognized as pointers or handles to structures of. This is the only way to create a type name for pointers or handles to other types.

title: Futurebasic/Language/Reference/Define


text:
User talk:Aulis Eskola

On another note, are you the same Aulis Eskola from CP? If so, hello, from another former editor! Νεοπτόλεμος 23:44, 28 January 2008 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Aulis Eskola. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Aulis Eskola~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 22:57, 17 March 2015 (UTC)

title: User talk:Aulis Eskola


text:
Photography Equipment

A general guide to camera equipment, with a focus on DSLR cameras.

Overview

 * What should I get?
 * Classes of cameras
 * Sample Systems

DSLR

 * DSLRs Systems
 * DSLRs Bodies
 * Lenses

Accessories

 * Supports: especially Tripods
 * Lighting: especially Flash
 * Accessories

Other cameras

 * Compact digital
 * Medium Format
 * Large Format
 * Film SLR

Appendices

 * Common mistakes
 * References

Photographie

title: Photography Equipment


text:
Photography Equipment/Common mistakes

The most common classes of mistakes in purchasing equipment are: We detail these in turn.
 * overemphasizing equipment
 * neglecting less glamorous components
 * not understanding trade-offs / focusing on headline numbers

Overemphasizing equipment
Equipment is a tool, not an end (unless you are a photographic engineer or collector): the goal is to take photographs, which requires a compelling subject and a skilled photographer far more than it requires expensive equipment.

You do not need to buy cheap equipment first, if you reasonably expect that you'll soon run into its limitations, but don't buy equipment unless you expect to use its capacities.

Subject matters most

 * Mistake: Buying equipment without an eye to intended use

A compelling subject, photographed with the cheapest disposable camera or camera phone, is more interesting than a boring subject, even if it be photographed with the fanciest camera.

Think about what subjects you wish to photograph, and buy equipment to facilitate that.

Technique matters more than equipment

 * Mistake: Thinking equipment obviates technique or compensates for poor technique

Quality cameras make it easier to take pictures and, properly used, can produce higher quality pictures and effects that cannot be replicated with inferior equipment, but they required skilled technique. Good technique with a point and shoot yield better results than poor technique with a far more expensive camera.

No equipment can replace a good eye, or attention to composition or light.

Less glamorous components
The most glamorous components of a system are the body and particularly dramatic lenses (especially large telephoto). A system is much more than a body, and all the parts play a role.

Focus on system, not body

 * Mistake: Focusing on body, instead of system

Especially with current technology, lenses last much longer than bodies (decades), and over time you will likely spend much more on lenses than on a body. Lenses are not generally compatible between manufacturers, so if you expect to buy more than one lens (which you will if you are serious), you are buying a system, not a body.

Thus, do not concentrate on minor differences between the current bodies of various manufacturers and at various price points.

Spend on lenses, not body

 * Mistake: Spending on body (instead of lenses)

"Whatever you do, don't spend too much on the body. It is much better to have a good lens on a cheap body than vice versa."

In a quip: "Buy glass, not chips".

Don't skimp on minor parts

 * Mistake: Trying to save on minor parts

A fancy system with inadequately cheap minor parts has feet of clay. For instance, buying cheap memory cards or filters. This is a false economy: an unreliable memory card may cause you to lose many pictures, while a poor quality filter will severely degrade your Image Quality.

Further, this is often a very small savings: minor parts are generally quite cheap.

Alternatively, one may buy cheap parts at first, only to be frustrated and spend far more in the long run replacing the cheap parts.

"Just buy the right stuff the first time".

Budget for a full system, not a body

 * Mistake: Budgeting for a body, then being dismayed at unexpected costs

A system costs more, often much more, than a body alone.

If one does not budget for a full system, one is likely to be dismayed at the full cost of a system, and to skimp on minor parts.

Better to buy a cheaper body and few lenses at first, together with quality parts for a full system, and subsequently upgrade and expand.

Draw up a full list before purchasing components to avoid blowing your budget.

Trade-offs/Headline numbers
Photographic equipment has many variables, and particular pieces of equipment make various trade-offs: a particular lens may have higher Image Quality and be faster, but be much heavier and more expensive.

Ignoring these trade-offs and focusing on a single number is softheaded, and leads to unforeseen compromises and frustration. The most common "headline numbers" that people focus on are zoom factor and pixel count, and both are deceiving.

Zooms and Superzooms versus Prime
Zoom lenses, and especially superzoom lenses, are undeniably convenient, but have severe trade-offs: Prime lenses are often much higher quality, faster, and cheaper, and zoom lenses with low zoom factors are generally similarly superior to superzoom lenses.
 * poor Image Quality
 * slow: they generally have small aperture, making them dim, and unsuited for DOF effects
 * image distortion
 * flare
 * poor AutoFocus
 * heavy
 * expensive

Image quality isn't just pixel count

 * Mistake: Focusing on pixel count, instead of Image Quality

More pixels are not necessarily better, and beyond a certain point are worse: small pixels are noisier, and eventually the increased noise outweighs the increased resolution.

Pixel count is a headline number—dig deeper.

title: Photography Equipment/Common mistakes


text:
Photography Equipment/Classes of cameras

This section provides an overview of classes of cameras and relative prevalence, without making recommendations – it is for context.

The main classes of cameras are:
 * compact digital cameras: the vast majority of cameras
 * DSLRs (digital single-lens reflex cameras).

In more detail, in increasing order of size, quality, and expense, and decreasing order of number of units sold per year:
 * camera phones
 * compact digital cameras
 * bridge digital cameras & large sensor non-DSLR (see below)
 * DSLRs
 * medium-format cameras and large format cameras
 * notably view cameras, largely film, but also some digital, as part of professional modular digital camera systems

Rangefinders
There are also a few most notably the Leica M8. They are of specialized interest, and roughly comparable to DSLRs, but rather more expensive; Leica has a strong following.
 * digital rangefinder cameras

Large sensor non-DSLR
The "large sensor non-DSLR" class is an emerging class, consisting of cameras with large sensor (like entry-level DSLRs), but a smaller format. Several of these are in the Micro Four Thirds System, by Panasonic and Olympus, which features a Four Thirds size sensor and interchangeable lenses. There are currently two types:
 * High-quality compact
 * These are pocket-size (compact) cameras with a large sensor
 * Sigma DP1 & Sigma DP2 are available, and have a fixed lens.
 * Olympus has also announced a camera in this class with interchangeable lenses and a retro design.
 * DSLR-style without viewfinder
 * These are similar in design and size to bridge cameras, but with large sensors: smaller bodies than DSLRs, and an electronic viewfinder (EVF)
 * Panasonic Lumix DMC-G1 & Panasonic Lumix DMC-GH1

Users

 * Casual photographers are well-served by compact digital cameras, which are generally "point & shoot".
 * Serious photographers (including amateurs/enthusiasts) almost universally go for DSLRs.
 * A small number of serious photographers go for film medium format and large format cameras.

Numbers
In terms of numbers, the vast majority of cameras produced today are camera phones, with over 1 billion expected to be sold in 2008. By contrast, approximately 100 million digital cameras were sold in 2006, of which 5 million were DSLRs. Sales of DSLRs are growing rapidly (on the order of 30%/year), so more recent numbers will be much higher.

What about film?
For most purposes, digital has entirely superseded film. In many circumstances, the quality is comparable, and digital is far cheaper and easier, easily allowing one to take hundreds of photographs for free.

For certain purposes, notably high-quality landscapes, film remains the medium of choice. Similarly, some enjoy the process and tradition of film.

In defense of small cameras
A camera is no good if it's left at home.

Small cameras, such as cell phones and compact digitals, have smaller and noisier sensors than DSLRs (which in turn have worse sensors than medium format digitals), and produce worse photographs, particularly at higher ISO speeds and bigger enlargements. However, they are much more portable, and hence more likely to be to hand when one wishes to take a photograph. For casual photographers, who would rarely if ever lug around a DSLR, a small camera is the only camera one will practically use.

Further, used properly, a small camera can produce quite good photographs, particularly at low ISO speeds and if one does not plan to enlarge it too greatly – for posting on the web, for instance.

Many serious photographers carry around a small camera whilst about casually, and reserve DSLRs for specifically photographic expeditions or the studio.

Traditionally these compact cameras have been from the run of "small sensor" cameras, but with the advent of the high-quality compact (Sigma DP1 & DP2, and announced Olympus ones), many photographers are excited about these.


text: Category:Book:Photography Equipment

title: Category:Book:Photography Equipment


text:
Photography Equipment/References

 * photo.net: Detailed guides to all aspects of photography equipment
 * Digital Photography Review: in-depth reviews of digital cameras

title: Photography Equipment/References


text:
User talk:70.80.91.230

Join Us!
--Laleena (talk) 01:08, 29 January 2008 (UTC)

title: User talk:70.80.91.230


text:
User talk:203.175.75.12

--AdRiley (talk) 07:36, 29 January 2008 (UTC)

title: User talk:203.175.75.12


text:
User talk:58.71.26.190

--AdRiley (talk) 07:37, 29 January 2008 (UTC)

title: User talk:58.71.26.190


text:
User talk:Poetcsw

(Newest comments first, please!)

title: User talk:Poetcsw


text:
User talk:Mallinc

Welcome!
Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally.--Laleena (talk) 13:28, 29 January 2008 (UTC)

title: User talk:Mallinc


text:
User talk:BPalmer

Welcome!
Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally.--Laleena (talk) 13:37, 29 January 2008 (UTC)

title: User talk:BPalmer


text:
Future Media

The production of "future media" often involves a team of artists, musicians, multimedia experts, communicators and other kinds of specialists. New media communication technologies can prepare people for emerging career opportunities that are being generated by interactive, immersive, multistory, multimedia technologies. A historical perspective is necessary to understand predicted future trends, but this book is about the future, not the past or present.

Entrepreneurs, Artists, Musicians and Multimedia Experts

 * /Future Media Topics/
 * /The New Entrepreneurs/
 * /Design/
 * /Music and Sound/
 * /Interactive MultiMedia/

Chapters

 * /Media Fads Versus Paradigm Shifts/
 * /Social Networking - An On-Line Phenomenon/
 * /Viral Media/
 * /Multi-sensory Media Is About To Explode/
 * /Virtual Experiences: Now More Like Our Real World/
 * /Emerging Technologies: Preparing For The Next Job Market/
 * /User Generated Media/
 * /Media Convergence/
 * /Other Topics/
 * /Field Trip Feedback/

Topic Information

 * /Scheduling Interactive Media Projects/
 * /Using the WIKIbooks and Facebook/
 * /SIGGRAPH - A Once Per Year Opportunity in Emerging Medias/
 * /Learning Resources/
 * Software
 * External links

Learning About Future Media
The ideal environment for learning about future media technologies would include demonstrations, field trips, and other “learn by doing” experiences. Guest speakers and panel discussions including industry professionals, alumni, professors, and students with expertise in fields mentioned above can provide invaluable information. Software tools for hands-on lab work could include, but be limited to: graphic editing (Adobe Photoshop), audio editing (Adobe Audition), video editing (Apple Final Cut Pro).

In your study of future media, you CAN expect to

 * 1. Experience an overview of historical and emerging industry trends in graphic design, music technology, and multimedia.
 * 2. Be able to define the marketable skills, attitudes and strategies demanded by future careers.
 * 3. Experience how technology is affecting world wide social development.
 * 4. Discuss some differences between a Believer’s media perspective and secular developers who might focus primarily on profit and entertainment value.
 * 5. Be amazed and sometimes overwhelmed by what you can do with interactive media.
 * 6. Learn techniques to locate, organize and analyze emerging communication technologies.

During your study of future media, you should NOT expect to

 * 1. Be passive while others do most of the thinking for you.

title: Future Media


text:
User talk:SwordPhilip

Welcome!
Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally.-- – Mike.lifeguard  | talk 16:50, 29 January 2008 (UTC)

title: User talk:SwordPhilip


text:
Cookbook:Monte Cristo Sandwich

| Sandwiches

A Monte Cristo sandwich is a sandwich composed of ham, chicken, and Swiss cheese enclosed in bread that is dipped in beaten egg and fried until golden brown.

Ingredients

 * Butter
 * 3 slices of white bread
 * Sliced lean baked ham
 * Sliced cooked chicken
 * Thinly-sliced Emmental cheese
 * Egg batter

Procedure

 * 1) Butter the first slice of bread and cover with ham and chicken.
 * 2) Butter the middle slice on both sides, place on meat, and cover with cheese.
 * 3) Butter the third slice and place, butter down, over cheese.
 * 4) Trim crusts, then cut sandwich in two and secure with toothpicks
 * 5) Dip in light egg batter, and fry in butter on all sides until golden brown.
 * 6) Remove toothpicks and serve with currant jelly, strawberry jam, or cranberry sauce.

title: Cookbook:Monte Cristo Sandwich


text:
User talk:Bbc~enwikibooks

Welcome message
Hello, and welcome to Wikibooks!

Here are some tips to help you get started:
 * To learn the wiki-markup-language syntax, see Help:Editing.
 * Make sure to sign your posts and comments with four tildes, like this: ~~~~
 * There is a box at the top of the edit window (if javascript is enabled on your browser) that will insert it too (looks like part of a signature). This will let others know who left it, and make it easy to reply back to you.
 * Remember to conduct any editing experiments in the sandbox.
 * You can tell the community something about yourself in your userpage.
 * You can get to this page by clicking the tab at the top of the page labeled with your registered username.
 * Wikibooks is a collection of open-source textbooks. (What is Wikibooks).
 * If you are a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI (requests for importation) to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using Wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Reading Room with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Help us by participating in policy and guideline creation.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Reading Room, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be a good idea to add that page to your "watchlist" so that you can see when any new information is posted there. You can do that by clicking the tab labeled "watch" at the top of the page.

Good luck! --Panic (talk) 18:24, 29 January 2008 (UTC)

C++ Programming
Sorry but we don't do class assignments. If you have a generic question that is not addressed on the book please repost it (and remember to sign your posts). Txs. --Panic (talk) 18:26, 29 January 2008 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Bbc. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Bbc~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:01, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 04:37, 19 April 2015 (UTC)

title: User talk:Bbc~enwikibooks


text:
User:Chtit draco

 (en)  See w:User:Chtit draco.

 (fr)  Voir w:fr:Utilisateur:Chtit draco.

title: User:Chtit draco


text:
User talk:Neoptolemus/Archive 1

Welcome message
Hello, and welcome to Wikibooks!

Here are some tips to help you get started:
 * To learn the wiki-markup-language syntax, see Help:Editing.
 * Make sure to sign your posts and comments with four tildes, like this: ~~~~
 * There is a box at the top of the edit window (if javascript is enabled on your browser) that will insert it too (looks like part of a signature). This will let others know who left it, and make it easy to reply back to you.
 * Remember to conduct any editing experiments in the sandbox.
 * You can tell the community something about yourself in your userpage.
 * You can get to this page by clicking the tab at the top of the page labeled with your registered username.
 * Wikibooks is a collection of open-source textbooks. (What is Wikibooks).
 * If you are a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI (requests for importation) to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using Wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Reading Room with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Help us by participating in policy and guideline creation.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Reading Room, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be a good idea to add that page to your "watchlist" so that you can see when any new information is posted there. You can do that by clicking the tab labeled "watch" at the top of the page.

Good luck!

PS: Txs for those cleanup edits... --Panic (talk) 20:34, 22 December 2007 (UTC)
 * Thanks much for these helpful links. Νεοπτόλεμος 01:47, 25 December 2007 (UTC)

IRC
You'll have to provide more info than "I get an error"...Good places to start: What does the error say? Do you have the appropriate software installed? – Mike.lifeguard  | talk 02:27, 25 December 2007 (UTC)
 * The webpage cannot be displayed

 * Most likely cause:
 * Some content or files on this webpage require a program that you don't have installed.

 * What you can try:
 * Search online for a program you can use to view this web content.

 * Retype the address.

 * Go back to the previous page.

 * I will use the IRC page to try to figure out what to do, and let you know if I need further assistance. Thanks! Νεοπτόλεμος 03:34, 25 December 2007 (UTC)
 * Figured it out, Νεοπτόλεμος 03:46, 25 December 2007 (UTC)

Page moves...
After moving a page from its location, go back and check if the redirect is needed (if there are still pages linking to the old location) if not clean it and tag it with the template, if links exits, you can fix it or leave it alone depending on your available time. --Panic (talk) 20:19, 30 December 2007 (UTC)
 * Done as requested. Thanks! Νεοπτόλεμος 20:39, 30 December 2007 (UTC)

Re:Page Deletions
Let me take a quick look at that list, and the pages that you want deleted. Give me about 10 minutes to ensure everything is right before I delete anything. --Whiteknight (Page) (Talk) 20:52, 30 December 2007 (UTC)

 * Sure thing. Thanks for your help. Νεοπτόλεμος 20:54, 30 December 2007 (UTC)

 * I have deleted the pages now. One of the pages contains a lot of text content, and I would like to merge histories on it when you are finished with your merger. Also, I would like (although you do not have to) if you could try and reuse some of that old content. Let me know if you need any help. --Whiteknight (Page) (Talk) 21:12, 30 December 2007 (UTC)

 * If you are refering to the Aegean Civilization page, it is a verbatum copy of the page that will be replacing it, minus two templates. Νεοπτόλεμος 21:14, 30 December 2007 (UTC)

np
no problem, you're doing the hard stuff finding things to be deleted and organizing, all I have to do is click a button ;). Hope all is well. Mattb112885 (talk to me) 18:45, 6 January 2008 (UTC)

a reply
Hello, this is GuoXia. I believe you sent me an email, and I replied, but I just wanted to leave you a little message here, as my email has been known to act somewhat spastically, and may not have sent. So just in case you didn't get the email, I thank you very much for taking an interest in this wikibook, which has been in dire need of reorganization, and I admire the work you've been doing. I'd also be more than happy to assist with the Chinese section, as well as wherever else you may need me. Just tell me what to do, and I'll try to begin! You can email me a reply, or just leave me a message. - --GuoXia (talk) 18:32, 7 January 2008 (UTC)

Ancient civs
I believe you sent me an e-mail requesting my help at the Ancient History wikibook. I'm sorry, but I'm far too busy right now to work at a level that would actually be helpful. Best of luck. -JCarriker (talk) 17:17, 13 January 2008 (UTC)
 * That's fine, I've managed to round up a few interested editors, and haven't yet heard back from a couple more, so hopefully they will be able to contribute. Thanks for getting back to me! Νεοπτόλεμος 17:37, 13 January 2008 (UTC)

Rollbacker
You've been nominated; please accept. – Mike.lifeguard  | talk 15:29, 23 January 2008 (UTC)
 * Great, thanks! I accept the nomination. I'll post this message there, also, just to make it prominent and keep stuff in one place. Νεοπτόλεμος 19:19, 23 January 2008 (UTC)

Ip warning
I like the appearance and all, it's just that I am curious if some "welcome" info could be placed there. Thoughts? Laleena (talk) 12:40, 25 January 2008 (UTC)
 * I just added something in there. Νεοπτόλεμος 21:20, 25 January 2008 (UTC)

Moved page
I created this in error http://en.wikibooks.org/wiki/1._e4/1...a5 and moved it. Do moved pages have to be deleted? I was under the impression(perhaps incorrectly) that moving a page means it's old page disappears. If not then would there be any purpose to moving rather then copying a page? ChessCreator (talk) 15:39, 6 February 2008 (UTC)
 * When you move a page, it takes the page's history along with it, so that editors can still see who wrote the page, and when. If you simply copy the page's contents to a new location, it would appear that you wrote the entire page at that time. When moving the page, the old page becomes a redirect (meaning that anyone who goes there will be sent to the new article). The old page still exists, but does not contain any of the previous content. Redirects are generally only needed if another page linked to the original. Since there are no links to the page you accidentally created, it's referred to as an 'orphaned redirect' and is probably not needed. You haven't done anything wrong- I was just cleaning up something we no longer need. Νεοπτόλεμος 15:45, 6 February 2008 (UTC)

Todays Work
You've been very helpful indeed, keep up the good work - Urbane   (Talk)   (Contributions)  23:13, 11 February 2008 (UTC)
 * Not much more to go, and hopefully the mess that was the Japanese Wikibook will be a bit more organized. Thanks for all the deletions! Νεοπτόλεμος 23:13, 11 February 2008 (UTC)

World at work
Could you please vote on the FB nom for this book? Thanks, Laleena (talk) 00:12, 12 February 2008 (UTC)

Vandalism
Saw your note on User talk:Jomegat. When you think a block is in order, the best spot is WB:AA, where any admin can see it (though if you know a particular admin is online, drop them a note too). As long as that IP has stopped, I won't block. If they keep going, then yeah, grab an admin. – Mike.lifeguard  | talk 01:17, 31 January 2008 (UTC)
 * All right, thanks for the tip, Mike. I'll do this from now on. Νεοπτόλεμος 01:19, 31 January 2008 (UTC)
 * Quick reminder to please subst: vandal warning templates and the like; this reduces server load and ensures the messages don't change while on the page. Instead of use  for example. By the way, you can put your signature inside most (all?) these templates by doing this:, which I rather like :) So far glad we gave you rollback; good work.  – Mike.lifeguard  | talk 02:49, 13 February 2008 (UTC)
 * All right, want me to go through and change warnings I've made? Νεοπτόλεμος 03:01, 13 February 2008 (UTC)
 * No need. Hopefully we'll get that silly throttle out of your way ;) – Mike.lifeguard  | talk 03:49, 19 February 2008 (UTC)

Name
Hi Neoptolemus

I'm just writing to let you know that I've changed my name from Urbane to Reece. Hope this doesnt cause too much confusion.

Reece  (Talk)   (Contributions)  15:14, 13 February 2008 (UTC)

 * Thanks for the note. Shouldn't be too tough to remember. Νεοπτόλεμος 20:31, 13 February 2008 (UTC)

Thanks
Thanks for the welcome and the invitation. I'll help out whenever I can. I spend most of my time at the English wikipedia, but I'm all for working more on wikibooks. -Steventity (talk) 03:55, 18 February 2008 (UTC)

Nissan revert
Thanks - could be a spammer, worth keeping an eye, regards -- Herby talk thyme 11:46, 21 February 2008 (UTC)
 * I'll have to leave for school sometime soon, so I won't be able to keep an eye out for much longer. Νεοπτόλεμος ( talk | email | contribs ) 11:55, 21 February 2008 (UTC)
 * np - I'll be around for a while - thanks -- Herby talk thyme 11:59, 21 February 2008 (UTC)

Orphaned redirects
G'day Νεοπτόλεμος, thanks for all your work helping to clean stuff up in WB. I have a request though - when marking orphaned redirects for speedy delete, could you please not destroy the page contents? Deleting pages requires some investigation and removing the content of the page when tagging for deletion just makes it a little harder. thanks, Webaware talk 03:15, 23 February 2008 (UTC)
 * Sorry about that, some of the redirects link to other would-be orphans (through a double-redirect), so I removed them to make the second redirect an orphan as well. But I'll just  them from now on. Sorry for the inconvenience. Νεοπτόλεμος ( talk | email | contribs ) 03:17, 23 February 2008 (UTC)
 * No worries, and thanks for all the good work! Webaware talk 03:28, 23 February 2008 (UTC)

US History
Could you please stop "delete" on those pages, when it would suffice just to move them? Now, though, I think that you aren't doing a bad job, it's just that it's easier for a move to occur than to put "delete" on all those pages. Laleena (talk) 14:53, 23 February 2008 (UTC)

Serbo-Croatian
I do not want to talk about politics, but it is common knowledge that Serbs, Croats, and Bosnians speak the same language. It is very inefficient to put separate courses for them. Since they are 99% identical, you're just merely rehashing the same things put in one variant on the other. I propose merging them into one page. Yes, it is the ONLY Slavic language in two Alphabets-- Latin and Cyrillic-- albeit the Latin version of the language is more frequently used, even among Orthodox believers. After all, you wouldn't put Mexican Spanish and European Spanish as separate pages, would you? Nor would you put West German and East German as separate pages? Brokenote (talk) 22:47, 24 February 2008 (UTC)

Lexical similarity? As I said, they are 99.9 per cent IDENTICAL. Why don't we merge the dialects into one? It will make everyone's job A LOT easier. First things first, put politics aside at ALL TIMES; this is NOT a political forum or a place to put all this useless junk that leads to nowhere. Brokenote (talk) 22:47, 24 February 2008 (UTC)

Who said you have any political loyalties? I'm merely proposing what should be the page be: any hint of political biases or forums will be dismissed immediately; I've seen enough POVs from a lot of people and it really is a waste of time.Brokenote (talk) 22:47, 24 February 2008 (UTC)

Ironically, Wikipedia ALSO treats them as one language (have you seen the Sprskohrvatski edition?): do you see any double-standards in it? IF they put it as seprate languages-- TRUST me, I;ve seen the discusison boards--- they're overloaded with endless ranting and political squabbling. Why waste one's time written three separate dialects that are practically the same language, putting all politics aside, and just put them into one? It saves time and memory space. Brokenote (talk) 04:55, 25 February 2008 (UTC)

World History Book
Hi, Neoptolemus,

I see that the World History book is semi-orphaned, in that it's being incorporated into a larger book about World History? Or not? I'm going to be having some additional time to deal with this project, so I'm curious how to help the effort go forward on the ancient history book... Andrew Watt (talk) 18:58, 23 February 2008 (UTC)

 * I'm not so sure that deleting the old table of contents was such a good idea... I'm not sure we have links to all those pages folded into the table of contents yet. urk. Andrew Watt (talk) 02:33, 25 February 2008 (UTC)

About Mike's page
Sorry, I'm just not used to using these wikis. That's the second mistake I made in the last ten minutes. Well, at least I tried to remove them as soon as I noticed it. The Kid (talk) 19:14, 7 March 2008 (UTC)

US History/Contents/Secession
G'day, have merged these page histories, could you please confirm that I restored the correct version? If not, just find it in the page history and revert. cheers, Webaware talk 23:13, 11 March 2008 (UTC)

Compliment, Questions
Hey Neoptolemus, how are you? i've been watching some of your work as a page patroller, and you're doing a wonderful job. If you're interested, I'd nominate you for adminship.

Anyway, I'm about to turn my bot on and do some serious work over at Linear Algebra. If you're watching RC at all, I'm sure you've seen all the work I've done in it so far. All the manual work is done now, and it's time for the bot to take over. However, the bot is probably going to require a few passes, which is going to flood the RC list. Since you are patrolling, will this bother you? I could probably flag myself for the duration of the job so that i dont flood the list, if you want. Just let me know. --Whiteknight (Page) (Talk) 01:48, 12 March 2008 (UTC)

 * For what it's worth, I'd support the nomination. You do a lot of good work here. --Jomegat (talk) 01:51, 12 March 2008 (UTC)

 * Wow, I'd be flattered by a nomination. Thanks for the consideration and support, both of you.

 * I've been refreshing RC occasionally while working on some homework, and it'd be handy if you could flag yourself for a bit. If not, no big deal- I can go through no problem. Thanks for the heads up. Νεοπτόλεμος ( talk | email | contribs ) 01:55, 12 March 2008 (UTC)

 * Point of administrivia: you need to accept the nomination for our votes to count for anything! :) Webaware talk 02:16, 12 March 2008 (UTC)

 * Done, thanks! Νεοπτόλεμος ( talk | email | contribs ) 02:18, 12 March 2008 (UTC)

Re: Welcome
thanks.--76.28.67.224 (talk) 22:48, 13 March 2008 (UTC)

I already have an account on wikipedia I am considering possibly having an account here (ive also been improving the article on the Paleolithic at the english wikipedia).--76.28.67.224 (talk) 22:50, 13 March 2008 (UTC)

Welcome aboard
You are now an administrator. If you have any questions, feel free to ask or just pop onto the IRC channel for assistance :). -- SB_Johnny | PA! 00:48, 19 March 2008 (UTC)
 * Awesome, thanks! Νεοπτόλεμος ( talk | email | contribs ) 00:50, 19 March 2008 (UTC)
 * Congrats Neo! Enjoy the new buttons! --Jomegat (talk) 01:04, 19 March 2008 (UTC)
 * Thanks Jim. Νεοπτόλεμος ( talk | email | contribs ) 01:06, 19 March 2008 (UTC)
 * Congrats indeed. I was also going to recommend that IRC is an excellent thing indeed. As well, you can have access to the cross-wiki admin channel - just ask Az1568. Finally, there are some excellent books like MediaWiki Administrator's Handbook and Wikibooks Community that might be helpful if you don't know what one of the buttons do. I'm trying to fix them up currently, so if you have time in the first few months of adminship, please do take a look and note areas for improvement on my talk page. – Mike.lifeguard  | talk 01:15, 19 March 2008 (UTC)
 * Thanks Mike. I was looking at the MW Handbook a few days ago, glad you reminded me. I'll try to get acquainted with IRC as you've suggested. Νεοπτόλεμος ( talk | email | contribs ) 01:22, 19 March 2008 (UTC)

Edit comments
G'day mate, a little request: when you fill in the edit comments, could you please not erase the section specifier, /* ... */? It helps others determine what section has been modified, and is especially useful on talk pages. thanks, Webaware talk 01:17, 20 March 2008 (UTC)
 * Sure thing... I never noticed I'd been doing that. Νεοπτόλεμος ( talk | email | contribs ) 01:19, 20 March 2008 (UTC)
 * I know about it because I did it for the first month, until I noticed the difference in RC :) cheers, Webaware talk 01:52, 20 March 2008 (UTC)

Another not-very-problematic, but very friendly reminder :) Please mark pages as patrolled if you're tagging them. Unfortunately, this means that you must get to the page via Special:NewPages, but I think the process at WB:NPP is fairly straightforward. Get a page (or batch of pages) from Special:NewPages; look at the page; mark it as patrolled, then go back and tag/edit/whatever. This reduces duplication of efforts because other patrollers know that it's been viewed by a fellow patroller. – Mike.lifeguard  | talk 21:19, 20 March 2008 (UTC)

 * Ah, I assumed that it would automatically mark it patrolled if an admin edited it... habit from a wiki I used to work on. Νεοπτόλεμος ( talk | email | contribs ) 01:41, 21 March 2008 (UTC)

How's Admining Going?
I just wanted to check in with you, and see how you're doing with the new admin tools? I've seen some of your work on the RC feed (I watch it when I get bored, it's like TV for me now), and from what I see you are doing great work. It always makes me happy when people I nominate turn into great admins! That means I did my research well.

Anyway, I wondered if you could do me a favor and read through some of the pages at Using Wikibooks/The Wikibooks Administrator. I'm not saying that you need to learn any lessons from this (you might, but I don't think you need it), but I really wanted to get some feedback from a new admin about it. It's intended to be a learning tool, but I don't know if it's good enough yet for anybody to really learn from it. Plus, in my old age, I can't remember what things are important, or what concepts are challenging, or whatever. You're welcome to edit the book or write up a bitch-list for me and I'll do it myself. God knows I need to at least pretend to be productive around here :) Thanks! --Whiteknight (Page) (Talk) 02:51, 28 March 2008 (UTC)
 * Glad to hear the positive feedback.
 * School has picked up quite a bit as the year nears its end (36 days left!!!), so I've been swamped with homework and the like and haven't been as active as I'd like to be, but still watch RC when I can. I'll take a look at this, probably sometime this weekend. Νεοπτόλεμος ( talk | email | contribs ) 02:56, 28 March 2008 (UTC)

 * All right, I read through the book today, and it is certainly helpful in explaining the role of an admin and outlining what exactly all these new buttons do. MediaWiki Administrator's Handbook fills a similar role in that it also explains how to use the extra buttons, but I think Using Wikibooks is definitely more helpful from a Wikibooks-specific point of view. I think there are more things that can be added into this book, such as the things that are touched on in the MW Admin Handbook (Special Admin-only pages, etc). MWAH covers quite a bit more content, so I think Using Wikibooks could benefit from borrowing from it's TOC list. According to the main contents page of Using Wikibooks, the Admin chapter is only half-finished, so when these missing topics are incorporated, I think it will become a very helpful tool in training new admins. Νεοπτόλεμος ( talk | email | contribs ) 00:38, 29 March 2008 (UTC)

Edit war?
Take a look at this and this; I may ask you to intervene here :) – <font color="Indigo">Mike.lifeguard  | <font color="Indigo">talk 15:14, 30 March 2008 (UTC)
 * Yes, I just saw him do it again and was going to protect it from moves, and then I saw where you'd warned him. Νεοπτόλεμος ( talk | email | contribs ) 15:22, 30 March 2008 (UTC)
 * If it sticks then no harm done; they'll have learned about the policy. If not, you can leave editing unprotected, and sysop-only pagemove. I'd keep indef until we can hash it out - they've not responded to any of my messages. – <font color="Indigo">Mike.lifeguard  | <font color="Indigo">talk 15:27, 30 March 2008 (UTC)

Deletes
My bad. As didn't notice that two of the pages where still linked. Thanks for sorting it out! ChessCreator (talk) 05:08, 4 April 2008 (UTC)

The_Hawk
It now uses cloaks instead of nicks to decide who it listens to. There's probably no real need for you to be able to issue commands, but if you want to you'll need a cloak. If you need help jumping through the hoops just ask :) – <font color="Indigo">Mike.lifeguard  | <font color="Indigo">talk 19:38, 4 April 2008 (UTC)
 * Okay, I'm getting a cloak now. Νεοπτόλεμος ( talk | email | contribs ) 19:53, 4 April 2008 (UTC)

WikiProject
I don't want to be overly discouraging, but it might not be worth it. Just something to think about if you haven't already. – <font color="Indigo">Mike.lifeguard  | <font color="Indigo">talk 01:37, 9 April 2008 (UTC)

Thanks
Thanks for the help on Template:Chesscreator/Invite1. ChessCreator (talk) 17:17, 13 April 2008 (UTC)
 * No problem. :) Νεοπτόλεμος ( talk | email | contribs ) 17:18, 13 April 2008 (UTC)

Translation
ping – <font color="Indigo">Mike.lifeguard  | <font color="Indigo">talk 12:37, 17 April 2008 (UTC)
 * Thanks for the heads up, Mike. Νεοπτόλεμος ( talk | email | contribs ) 21:06, 17 April 2008 (UTC)

thanks
Hello, thanks for the welcome! --<font face="arial" color="#8652b9">Kyok <font face="arial" color="#BA55D3">o 03:14, 22 April 2008 (UTC)

Iranian History
You may :-)-Ravichandar84 (talk) 04:36, 23 April 2008 (UTC)

 * Anyway, I would insist on an attribution, a link to my book or something like that in the "See Also" or "references" section :-) -Ravichandar84 (talk) 04:41, 23 April 2008 (UTC)

 * Yeah, it would be better if you could add the note to all the pages on Iranian history since it is a verbatim copy :-). Thanks -Ravichandar84 (talk) 02:09, 13 May 2008 (UTC)

Spanish Template
I thought your templete was a good template for something like I'm doing. I'm not sure how much you would know about what I'm looking for right now, the independence of Suriname, I'm having some difficulty finding much information on it, and I want to expaned that page. So if you find anything on it, just let me know. Feel free to re-word what I wrote or add stuff in too. Any help is appreciated. (Red4tribe (talk) 22:35, 16 May 2008 (UTC))

 * Thanks (Red4tribe (talk) 22:48, 16 May 2008 (UTC))

Supergiant
Did you mean to tag this as a NC []? Looks more like a speedy delete to me. --AdRiley (talk) 06:55, 29 May 2008 (UTC)
 * Deleted. Thanks! Νεοπτόλεμος ( talk | email | contribs ) 01:43, 24 June 2008 (UTC)

Deleting Japanese Navbars
Hey Neoptolemus,

I saw you'd done some work fixing links to navigation bars at the Japanese wikibook. Some of these I'm suggesting be deleted as they aren't used anywhere. Please let us know if you're interested in keeping these. --Swift (talk) 13:34, 10 June 2008 (UTC)
 * Responded there. Νεοπτόλεμος ( talk | email | contribs ) 01:43, 24 June 2008 (UTC)

title: User talk:Neoptolemus/Archive 1