Phoenix berasal dari mitologi Mesir. Phoenix merupakan burung api abadi yang tidak bisa mati, Menurut mitologinya Phoenix merupakan burung api jantan yang sudah hidup selama 500, 1461 atau 12.594 tahun lamanya. Ketika waktu kematiannya tiba, Phoenix biasanya menyadari akan kematiannya kemudian ia akan membangun sebuah sarang untuk dirinya dan tubuhnya akan berkobar terbakar beserta sarangnya kemudian dari abu sisa pembakaran tersebut terlahir Phoenix baru dan hal itu terjadi terus menerus sehingga ia hidup abadi.

Ketika Phoenix terluka ia akan menyembuhkan lukanya sendiri dan beregenerasi sehingga hal ini membuatnya tidak terkalahkan. Phoenix merupakan simbol kebangkitan, keabadian, dan kehidupan setelah mati.

Phoenix digambarkan memiliki bulu yang sangat indah dengan warna merah emas. Dalam mitologi Cina juga terdapat burung yang cirinya tak jauh berbeda yaitu Feng Huang.

Пока реализован только метод Connect(), но все экспортные функции доступны.

+ небольшой пример как использовать CallBack функции.
public enum T2QResult
{
Success = 0,
Failed = 1,
QuikTerminalNotFound = 2,
DllVersionNotSupported = 3,
DllAlreadyConnectedToQuik = 4,
WrongSyntax = 5,
QuikNotConnected = 6,
DllNotConnected = 7,
QuikConnected = 8,
QuikDisconnected = 9,
DllConnected = 10,
DllDisconnected = 11,
MemoryAllocationError = 12,
WrongConnectionHandle = 13,
WrongInputParams = 14
}

default:
throw new BrokerException(sb.AppendFormat(" ErrorCode: {0}", ErrCode).ToString());
}
}
}

Пример как установить CallBack функции для статуса сервера.

//Описывает функцию обратного вызова
public void SendTransactionReply (
Int32 nTransactionResult,
Int32 nTransactionExtendedErrorCode,
Int32 nTransactionReplyCode,
UInt32 dwTransId,
Double dOrderNum,
String lpstrTransactionReplyMessage)
{
QDebugger.Trace("TransCallBackReply", lpstrTransactionReplyMessage);
}

if (r != (int)T2QResult.Success) throw new Exception(sb.ToString());
}


With that, on Thursday we'll be making a number of new customer facing APIs available. These APIs will form the basis for being able to organize content into folders, know what folders exist, create new folders, and move the content to different locations. We are also planning to give developers the ability to programatically add Youtube, Real Estate Shows, and Vidlisting content to folders via APIs.

The API overview documentation is already live on some of these APIs:

Create new folders: This api can be found at http://api.forsalebylocals.com/docs/createfolder (API Call live at noon on Thursday)

Get list of existing folders: This api can be found at http://api.forsalebylocals.com/docs/getlistofallfolders (API Call live at noon on Thursday)

Move content to different folders: This api can be found at http://api.forsalebylocals.com/docs/movecontenttofolder (API Call live at noon on Thursday)

Lots more API capabilities are coming online over the next month. Stay tuned....

ho preparato una tela fresca fresca

l'ho tessuta di prati e primavera

intinta qua e là con schizzi di cielo e di pervinca

morbidissime nuvole di mussola

a forma di capretta una bella bicicletta

per ogni suo piede una tenera scarpetta di taffetas.

Ho preso la misura giusto giusto dall'immenso

dall'azzurro dei suoi occhi appena appena sbocciati.

Su una morbida coperta liscia di raso verde  lascio

il caldo acceso di un vivo giallo girasole

una ballata di grilli cantori e il soprano di una cicala

dentro un laghetto di fresco piquet

una cova di sogni da pescare tra pesci rossi e stelle di mare

ricamate con amore  filo per filo dal gomitolo del cuore

e

lassù

lungo l'orlo del saluto

lascio un volo di airone a sorreggere l'aquilone di un suo tenero sorriso

poco più in là un nido di rondini e colibrì

è il tetto di una casa

una  lumaca sognatrice

appena nata  si affaccia sull'alba

di ogni suo dì.

fata ferni

Une petit’ âme
Guenièvre
un pétal de vie
une promesse de respirer
un’éspoir d’effeuiller
doucement
un murmure de quelques vers
pour ne pas te réveiller
encore.

fata rose

a tibe, fitza mea,
a ti donare alas d’astore
chi colan furrìande s’aghera
moghende sas nues
ghettandesi
intr’e sa bida
chin tirriàdas de bentu…

…menduledda,
froricheddu de beranu…
cras manzanu
b’est su sole
si poden gai
mirare sos ocros tuos
e sas pinturas
peri chircande
ballos e sintzos
petzi pro tene
nobos e galanos.. adìosu, a crasa e a metzus biere!

fata api

Isé picinìnô
un miràcol del Signùr
E pensà che tè sét za tötô lé
programàdô
i caèi i öcc la buchìnô
e forse apò ‘l caràter
Tè laùret dé e nòt
a ricamàt
a belazìne
che nϋsϋ s’ancòrz
gnà la tò mamô che la dòrmô
gnà la nónô che zà la ta öl bé.

fata rose

un abito cucito a mandorlina, una morbida vestina per ginevra piccolina, tessuto di fate e sete di sogno, lino e merletto per il piccolo letto, con figure in crinolina per una splendida cara bambina, un nido d'affetto, un nodo di voci, un mazzetto di baci e ghirlande di auguri, un coro di bene e una stoffa di trame, una storia e un ricamo d’amore.

Là dietro i tuoi occhi
si accenderanno stelle addormentate
si involeranno cascate nei colori dell'iride
abiterai la casa del respiro
sarai figlia di luce e acqua di mare

apprendista fata elina

U’ Scazzamurrill

Stanotte è arrivato
non ha rotto i vetri delle finestre
nè si è seduto sulla mia pancia addormentata
gli avevo lasciato dei sassolini nelle pantofole
un paio di scarpe da calzare
mi ha chiesto vuoi cocci o soldi
cocci gli ho risposto
Ha regalato dolcetti e monete per la mia bambina

fata camilla

Rose con la sua ....zucca fatata..e chi la smuove e la sveglia più:Capace di restare addormentata per 400 giorni come fossero due minuti,solo due minuti.

api,rose,ferni in confezione da viaggio.

fata camilla...che non si vuol far trovare e...elina. la fata più piccolina..solo 157   anni

]]> http://monparadis.wordpress.com/?p=446 Wed, 03 Sep 2008 13:47:09 +0000 Justine http://monparadis.wordpress.com/?p=446 LE API SPARISCONO e nel giro di 4 ANNI TOCCHERA' A NOI, secondo Einstein.

2008+4 = 2012 il Mistero si infittisce ...!

Ormai è ufficiale: tutte le associazioni denunciano la sparizione dal nostro territorio (e non solo) delle API. Prima di noi avevano denunciato tale problema gli Americani (i primi ad annunciare tale problema) seguiti da spagnoli, portoghesi, polacchi, grechi, francesi, tedeschi, scozzesi ecc. Leggi

Questo è un fatto gravissimo!

Sono decine di migliaia gli alveari spariti in pianura padana in Italia, mentre in Svizzera dopo l'inverno caldo si è verificato un crollo del 25% della popolazione di api ed in Montana negli Stati Uniti la moria è arrivata al 75%. E' la Coldiretti a tracciare il quadro di una vera ecatombe mondiale per le api segnalata oltre che in Italia anche in 27 Stati degli Usa, in Brasile, Canada, Australia e in molti Paesi Europei come Svizzera, Germania ed Inghilterra.

Si tratta di una situazione che mette in discussione l'equilibrio naturale globale con rischi anche per la salute e l'alimentazione che dipende per oltre un terzo da coltivazioni impollinate attraverso il lavoro di insetti, al quale proprio le api concorrono per l'80 per cento .

Prodotti come mele, pere, mandorle, agrumi, pesche, kiwi, castagne, ciliegie, albicocche, susine, meloni, cocomeri, pomodori, zucchine, soia, girasole, cotone e, colza - spiega la Coldiretti - dipendono completamente o in parte dalle api per la produzione dei frutti. Ma le api sono utili anche per la produzione di carne con l'azione impollinatrice che svolgono nei confronti delle colture foraggere da seme come l'erba medica ed il trifoglio fondamentali per i prati destinati agli animali da allevamento. Anche la grande maggioranza delle colture orticole da seme si possono riprodurre grazie alle api come l'aglio, la carota, i cavoli e la cipolla.

Se non sarà interrotto il trend che ha portato in pochissimo tempo alla scomparsa solo negli Stati Uniti di un quarto degli alveari con 15 miliardi di api, le conseguenze ambientali sarebbero disastrose.

L'allarme lanciato in molte regioni dalla Lombardia al Piemonte, dal Veneto al Friuli Venezia Giulia dimostra che la strage, definita dagli scienziati statunitensi come “Colony Collapse Disorder” (CCD), ha effetti gravi anche in Italia dove a rischio - sostiene la Coldiretti - è una popolazione stimata in circa 50 miliardi di api in oltre 1 milione di alveari che offrono “gratuitamente” un valore del servizio di impollinazione alle piante agricole lungo tutto lo Stivale stimato pari a 2,5 miliardi di Euro all'anno.

Quali sono le cause di questa moria di Api?
Sono gli insetticida utilizzati nelle campagne, gli Ogm e le onde magnetiche provocate dai cellulari. Infatti le Onde della Telefonia cellulare rendono le api incapaci di ritrovare la strada di casa portandole a morire lontano magari mangiate da altri animali.

Una teoria sperimentata dall' Università tedesca di Landau in cerca delle cause del Colony Collapse Disorder (sparizione delle api). L'esperimento consisteva nel mettere un cellulare vicino ad un'arnia: le api se ne allontanavano lasciando la loro Regina e le api operaie addette alla pulizia senza cibo. Le onde dei cellulari rendono le api incapaci di ritrovare la strada di casa.

Questa catastrofe si rifletterà completamente sull'ambiente e ... su di noi!

Lo sapevate cosa diceva Einstein sulle Api?

"Se l'ape sparisce dalla Terra, all'uomo rimangono solo quattro anni di vita. Senza api non c'è' impollinazione, quindi niente piante, niente animali, niente uomini"

.

Siamo nel 2008 fra 4 anni siamo nel misterioso 2012 di cui ho già parlato qui
Che sia una conferma a tutti i sospetti e i misteri del 2012?!
Ovviamente io spero di no ... ma continuo a sperare quanto già scritto nel mio precedente post.

Justine

#5.1

di Liliana Zinetti

L’amore è condanna dolce e terribile.
Si compiono delitti in suo nome,
si sbranano i cuccioli.
Inutilmente provo
ad amare da lontano.

.................

.......

***

#5.2

di Marta Ajò

Ridevano di lei
delle sue esili membra in cui prevalevano i nodi venosi
del suo incedere traballante di chi sta perdendo la forza di gravità
del suo volto scheletrito e del suo andare in bicicletta sotto il solleone come sotto la pioggia
per consumare la sua disperazione e la sua voglia di non esserci più;
per affermare la sua esistenza attraverso la sua lenta scomparsa,
attraverso l’allontanamento dalle norme,
attraverso la paura degli altri alla diversità.
Di chi si nutre infine dei propri organi
perché null’altro attira quella fame vorace di morte.
Per punirsi
per punire .
Fino al giorno che quel corpo cadde, e nessuno più ebbe a ridere.

***

#5.3

di Fernanda Ferraresso

si parla si parla si parla
voi parlate loro parlano
io sto zitta
mi consumo
e mi raggiungo
fino al cedimento
fino a non sentirvi più parlare.
Voglio sentirvi dentro
voglio sentirvi in ogni centimetro d’osso
là dove la materia si produce ad ogni scalfittura.
Voi non ci siete
siete dentro le vostre parole
navigate lontani
non avete terra dove mettere i piedi
dove crescerli a forma di radice.
Affondo affondo affondo.
Al fondo non voglio vedere me
una parola che si stacca da fuori
io figurina di un album di famiglia.

***

#5.4

di Mirko Servetti

Signora grigia, consunta nel non-desiderio, macchina senza organi…

Mi consumerai ancora
sapendomi senza calco
e senza immagine
ancora qui nel vano
dove saremo ciò che potremo
dove sbucheremo sciamando
al modo delle api
distanti dalle terre i cui fuochi
ci sedussero ponendoci
alla catena d’amore e agonia
senza occasione di riscatto

***

#5.5

di Api

sciamare
non sembra osabile
manca la forza
volutamente
con caparbietà
insisto
ad annullare
questo povero
essere
svaligiato
da me stessa
apparire
è un comando
imperioso
secco
a cui dò spazio
nel paradossale
non propormi
non volermi
ed immobile
attendo l’onda
onda
figlia di malattia
che m’incatena,
travolgendomi.

***

Post correlati:

Anoressia

Anoressia n.2

Anoressia n.3

Anoressia n.4

Anorexis

"Le api rubacchiano di qua e di là ai fiori, ma dopo ne fanno il miele che è tutto loro [...]. Allo stesso modo, i pezzi presi ad altri, l'autore li trasformerà e confonderà per fare un'opera tutta sua" (Montaigne, Saggi, citato nella pagina dei ringraziamenti (p. 233) di La scomparsa delle api, di Sylvie Coyaud).

by the Google Chrome team, comics adaptation by Scott McCloud.
Google Chrome browser gaat binnenkort live. Google gaat daarmee het gevecht met marktleider Microsoft nog steviger aan. Eerst Gmail, toen Docs en nu dus de langverwachte browser (2004) als concurrent voor IE. Het nieuws is door Google zelf bevestigd op Google blog. De Chrome browser moet net als Gmail een nieuwe manier van werken en denken voor het browsen introduceren. In een 38 pagina's tellende strip wordt meer toelichting gegeven.

Chrome is a web browser that will be able to better run the online web apps that Google is so busy developing. It will be based on WebKit the open source rendering engine used by Apple’s Safari and include a new JavaScript engine called V8. The browser will be called Google Chrome (which they really ought to work on) and will be released in beta form for Windows some time today. According to Google Mac and Linux versions are on the way too. You can read the blog post here. Or if you want Google has also produced a comic for your enjoyment

Iron Money's API allows developers to build tools that leverage the financial data they upload to Iron Money. The API gives developers read, write, and delete access to all of the data they store in Iron Money. The API features OAuth for authorization and OpenID support will be coming sometime in the next few months.

Documentation is available as well as a PHP-based client library for interacting with the service.

If you want to sign up and give it a try, free registration is now open (as Chasen said, OpenID is coming soon).

The View Road Hospital Encounter

Catch API with the On The Beat Hosts Lee Teng 李腾, Jeremy Chan 田铭耀, and Vivian Lai 赖怡伶 and Malaysia Singer Rynn Lin Yu Zhong View Road hospital is located at Admiralty Road West, Woodlands, Singapore.It used to be a mental hospital, started in 1977. It was closed sometimes in 2001. When abandoned, it was the favourite haunting ground of many people, especially students. You can view pictures of the former mental hospital here. Now it is being converted into a workers' dormitory. Watch On the Beat 3, on 9th Sep at 8pm to catch possibly the last glimpse of Old View Road Hospital, before it's mystery disappear. API Sparky & Shany with On The Beat 3 Hosts Lee Teng 李腾, Jeremy Chan 田铭耀, Vivian Lai 赖怡伶 and current View Road Hospital lesse Jimmy.

Está muy bien documentado con ejemplos así que en este caso no haré ningúno.

This release represents what we should have produced in the first place; a simple and uniform presentation layer on top of existing libraries.

What exactly is OCaml Batteries Included?

OCaml is a great language which suffers from its lack of standardization. The absence of a real standard library has led the OCaml community to produce many incompatible libraries with distinct conventions. In turn, both this lack of out-of-the-box features and this multiplicity of choices make it difficult to start developing with OCaml or to design new works for reusability. By contrast, commercial offerings such as Java or .Net come with a comprehensive toolbox which makes the life of programmers that much easier.

OCaml Batteries Included is an attempt to provide a uniform library environment for OCaml, both for beginners and for experienced developers, which should give programmers out-of-the-box support for most common tasks. Although OCaml Batteries Included has to be a library for technical reasons, the objective is not to create some brand new framework but rather to integrate existing works,  with dependencies towards existing libraries, and relying on the mechanisms of Findlib and GODI/Apt/Rpm for dependencies resolution.

OCaml Batteries Included is not a standard library: as far as we are concerned, the standard library is a combination of the base library provided by Inria and ExtLib, with possible other adjunctions if deemed necessary.

OCaml Batteries Included also doesn't stop at the level of standard libraries. In time, we aim to provide

• network management (most likely using OCamlNet)
• concurrency (most likely using coThreads)
• calendar management
• distributed programming (possibly bulk synchroneous programming or Opis)
• user-interface (underlying support undecided)
• plotting
• geometry
• parsing and unparsing
• database access
• logging
• image manipulation
• xml manipulation
• unit testing
• pdf generation
• reactive programming
• localisation
• safe marshalling
• ...

Finally, OCaml Batteries Included doesn't stop at the level of libraries. We already give access to a few compile-time tools and future releases will also include syntax extensions. Expect things along the lines of:

• various syntactic improvements (local opening of modules, extended exception management)
• improved pattern matching (micmatch or Patterns)
• management of free/bound names
• domain-specific languages
• ...

Oh, and why does this work have to be a library? Because of that little matter of uniformity. At the moment, the OCaml base library provides channels for input and output and streams as a lazy data structure. ExtLib, on the other hand, provides the more generic input and 'a output for, well, input and output, along with enumerations as a lazy data structure. In both occurrences, the mechanism offered by ExtLib is more  open, more generic and more powerful. Per design, we plan to consider channels and streams as obsolete. However, for the moment, most libraries use the more standard channels and streams. In order to provide uniform APIs, we will need to program a compatibility layer. Fortunately, it's usually easy to convert between channels and inputs/outputs (except for Printf, but we've solved that particular problem already). That's the glue.

Release 0 and beyond

The main objective of release 0 is to get things (re)started on a clear path, so don't expect any brand new feature. What this release contains, in addition to logistics, is access to:

• the base library ;
• ExtLib ;
• OCamlDoc ;
• Findlib ;
• Godi-script.

Let's look a little bit more at the details.

The first part is Standard, the candidate replacement for Pervasives:

• Batlib
  • Standard

Standard is composed from the contents of Pervasives and ExtLib's Std. This module should change relatively little in the future, besides, perhaps, the addition of a few very common data structures (à la Either).

Next, we have base data (typically numbers and characters):

• Batlib
  • Data
    Numbers
    • Big_int
    • Complex
    • Int32
    • Int64
    • Nativeint
    • Num

    Text

    • Char
    • String [ExtLib's extended version]
    • StringLabels

This version doesn't contain anything Unicode-ish yet nor any of our additional number modules. We'll get Unicode support whenever ExtLib finally adopts Camomile or drops the one module of Camomile already adopted. More modules are already on the repository and waiting to be submitted to ExtLib, including safe integers, custom operators, etc.

Then come containers

• Batlib
  • Containers
    Collection-style stuff
    • Enum

    Generic persistent containers

    • Dllist
    • List [ExtLib's extended version]
    • ListLabels
    • Map
    • MapLabels
    • Set
    • SetLabels

    Generic mutable containers

    • Array [ExtLib's extended version]
    • Global
    • Hashtbl [ExtLib's extended version]
    • HashtblLabels
    • RefList
    • Stack
    • Stream

    Specialized containers

    • BitSet
    • Buffer
    • Option
    • Lazy

Again, a number of things are waiting on the repository (or for acceptation by ExtLib) before we can add them. In the future, we'll get improved streams (yes, although they're obsoleted), lazy lists, etc. In time, I hope we can add things like red-black trees, generic AVLs, etc.

Let's continue with meta-level stuff:

• Batlib
  • Meta
    Access to language primitives
    • Marshal
    • Oo

    Interaction with other languages

    • Callback
    • Memory
    • Gc
    • Weak

    Internals

    • Obj
    • CamlinternalMod
    • CamlinternalOO

In a future version, we may eventually add Dynlink if/whenever a consistent interface permits its use from both byte-compiled and native code. There is also some space for SafeMarshal and for bindings to other programming languages.

Text manipulation, from lexing to pretty-printing, goes into module Batlib.Text, as follows:

• Batlib
  • Text
    Parsing
    • Genlex
    • Lexing
    • Parsing
    • Scanf
    • Str

    Printing

    • Format
    • Printexc
    • Printf

Future versions will be enriched with parser combinator library, unicode lexing (Ulex) and interaction with other parsers than Yacc. In addition, Printf, Scanf, Printf and Genlex will be replaced by nearly-identical but more generic modules, while the future of Format remains undecided. Finally, this may be the right place to give access Camlp4.

Module Batlib.Util groups a few utilities which have no better place:

• Batlib
  • Base64 [from ExtLib]
  • Digest
  • Random

No decision have been taken for the future of this module. Most likely, it will continue gathering otherwise-impossible-to-classify items, with features such as calendar management.

As OCaml offers support for concurrency, we publish this feature in a dedicated module Batlib.Concurrency:

• Batlib
  • Concurrency
    • Threads
      • Condition
      • Event
      • Mutex
      • Thread

Future versions of Batlib.Concurrency will receive alternatives to Threads, such as coThreads or lwt, while Batlib.Concurrency.Threads itself will receive additional tools for use with threading, such as Concurrent Cells.

Other interactions with the system, from file management to signals, are grouped in Batlib.System:

• Batlib
  • System
    Environment interaction
    • Arg
    • OptParse [from ExtLib]

    Streams

    • IO [from ExtLib]
    • Unzip [from ExtLib]

    System calls

    • Filename
    • Unix
    • UnixLabels
    • Sys

Future versions will complete this offering with more operations on files (as a replacement for those operations included in Pervasives), operating-system related utilities, such as are included already in OCamlBuild or Godi-script. There is also some space for operating-system specific modules.

The final module permits (some) interaction with the OCaml toolchain:

• Batlib
  • Toolchain
    • Odoc_info [from OCamlDoc]
    • Findlib [from Findlib]
    • Godi_script [from Godi-script]

Future versions will give access to OCamlBuild's modules and should eventually provide tools for causing and controlling compilations from within OCaml. While this is not our main objective, together with Dynlink, this may give us elements of a dynamically-compiled OCaml.

How can I get some stuff into Batteries Included?

As you have seen, we already have a number of plans for Batteries Included and there is room for more. Now, if you believe that some library should absolutely get loaded into Batteries, we suggest taking the following steps:

• make sure that the license of the library is compatible with Batteries (chances are that if it's open-source and if it's OCaml, there won't be any licensing issue, but be careful with the full GPL or the un-amended LGPL)
• if this library is not in GODI yet, contribute a GODI package (or find someone to do so) -- Debian or Fedora packages are nice, too, but for the time being, we are using GODI as a reference
• if this library is new or not very well-known, find people to test it and review it
• if the API of the library makes use of functions or data structures which are considered obsolete in Batteries or which are clearly redundant with respect to functions or data structures already present in Batteries, please provide a glue layer, hiding these functions or data structures behind an API which makes use of the functions or data structures favored by Batteries
• if the API of the library makes use of closed data structures, please try and find a manner of opening them -- if you don't understand what I mean, compare the closed design of channel_in and channel_out to the open design input and 'a output, the closed design of streams to the open one of enumerations, etc.
• design an OCamlBuild plug-in which will let users link against the API
• contact us -- for the time being, we're using the main OCaml Mailing-List.

Also, feel free to contact us with any question or suggestion.

These articles should come in handy when evaluating Omeka, which the library has installed for testing.  For my real (i.e. paid) job, I recently visited the Center for History and New Media to discuss how Omeka can be integrated with CSU's CONTENTdm-based collections to create exhibits that are more visually attractive, focused, and interactive than CONTENTdm usually allows.  However, at the moment, we are only capable of transmitting metadata using OAI-PMH, and have not yet developed an API capable of "scraping" actual objects (i.e. allowing Omeka to natively display objects that are located in a CONTENTdm repository).  So one of the things I will be doing for my practicum is investigating how Omeka can be used at the library - with or without the API.

It also appears that I will get to sit in on some meetings, such as the ebrary webinar mentioned in my last post, where technology choices will be discussed and software will be evaluated.

Based on the readings listed below, the major areas of consideration when selecting digital library software are:

• establish a clear and specific project statement that includes the scope of the project, infrastructure dimensions, and the overall purpose of the project
• explore the software functionality requirements that must be met to accomplish project goals and meet user needs
• explore practices at similar - and dissimilar - institutions to better understand the issues involved, compare a variety of approaches, and set a baseline for functionality
• determine the characteristics and practices of the user community using empirical data
• rank and prioritize functionality requirements to determine a baseline and to set forth a plan for development and added functionality over time if needed
• examine the viability of the vendor
• determine the security and authentication features of the software - including the granularity of user access and privileges - to determine how the software fits into existing institutional systems
• consider whether the budget and other resources available will meet the demands of the new software
• come up with a plan for training and documentation
• if the plan is part of a Universal Service Fund, it should additionally include an assessment of the institution's  technology environment, a coherent strategy for meeting specific goals for improvement, and an established evaluation process for monitoring progress and making necessary changes mid-course

View: Connecticut State Library Checklist for Technology Plans

Download [PDF]: Cervone, H. Frank. "Some considerations when selecting digital library software." OCLC Systems and Services: Int'l digital library perspectives, 22(2), 2006.

As the Gold Sponsor for GeoCart’2008, the National Cartography Conference at Auckland University from 1-3 September, GeoSmart Maps Ltd General Manager Phil Allen has announced that GeoSmart is offering a set of web tools for web cartographers for use free of charge for educational and non-commercial use. He will outline these in a presentation at the conference on Wednesday 3 September.

“As the leading supplier of commercial cartographic products in New Zealand, we would like to encourage development of new applications,” said Phil Allen. “There are so many opportunities for people to develop wonderful web and mobile applications and we have the API’s and web services, as well as a wealth of geo-spatial data about New Zealand. “

The tools GeoSmart is making available include:

· Web mapping API

· Points of Interest API

· Geocoding and reverse geocoding web services

· Directions API

· Route Optimisation API

· Vector Graphics API

· Map datasets (NZ map base, Cadastral map base, Census map base)

Using such tools, web cartographers can build complex web, Location Based Services (LBS) and Mobile based GIS solutions such as; Carbon footprints for businesses by measuring the journey times of staff going to and from work and including their business activities to computing calorie burn when a user creates a walk/cycle/running route. The tools include all of the APIs required and a set of maps with many code examples. Allen’s paper will present these tools and advise how educational institutes and the web cartography community at large can take advantage of these for promoting and enhancing our industry.

For more information please contact Luigi Cappel luigi.cappel@geosmart.co.nz

The Amiga computer, launched by Commodore in 1985, combined superior multimedia technology with ease of use, inspiring millions of the most creative and enthusiastic computer users ever.

Amiga Forever is the award-winning Amiga preservation, emulation and support package brought to you by Cloanto, Amiga developers since 1986.

Different editions of Amiga Forever blend high-quality software and original content with the ultimate set of videos to chronicle and let you experience firsthand the history, culture, challenges and passion behind the Amiga.

(http://www.amigaforever.com/)

If you're not, you should really check it out. This computer did things in 1985 that mainstream computers wouldn't end up doing for years - unfortunately, Commodore screwed the whole thing up, and it never got the chance to really break into the marketplace:

Amiga
From Wikipedia, the free encyclopedia

The Amiga is a family of personal computers originally developed by Amiga Corporation. Development on the Amiga began in 1982 with Jay Miner as the principal hardware designer. Commodore International bought Amiga Corporation and introduced the machine to the market in 1985. The name Amiga was chosen by the developers specifically from the Spanish and Portuguese word for a female friend,^[1] and because it occurred before Apple and Atari alphabetically.^[2]

Based on the Motorola 68k series of microprocessors, the machine sports a custom chipset with advanced graphics and sound capabilities, and a pre-emptive multitasking operating system (now known as AmigaOS). While the M68k is a 32-bit processor, the version originally used in the Amiga, the 68000, has a 16-bit external data bus (that transfers 32 bit of data in two consecutive steps, a technique called multiplexing -- all this transparent to the software, which is 32-bit from the beginning), and the original machine (along with its contemporary, the Atari ST) was generally referred to in the press as a 16-bit computer;^[3] later models sported fully 32-bit designs. The Amiga provided a significant upgrade from 8-bit computers such as the Commodore 64, and the Amiga quickly grew in popularity among computer enthusiasts, especially in Europe, and sold approximately 6 million units.^[4]

(http://en.wikipedia.org/wiki/Amiga)

Yep. It had a pre-emptive multitasking operating system in 1985. For some context on how impressive this is:

The earliest pre-emptive multitasking OS available to home users was the AmigaOS released in 1985. Pre-emptive multitasking was later adopted on Apple Macintoshes by MacOS 9.x ^[1] as an additional API, i.e. the application could be programmed to use the pre-emptive or co-operative model, and all legacy applications were multitasked cooperatively within a single process. Mac OS X, being an Unix-like system, uses pre-emptive multitasking for all native applications, although Classic applications may be multitasked cooperatively as they run in fact under Mac OS 9 running as OS X process.

(http://en.wikipedia.org/wiki/Computer_multitasking#Preemptive_multitasking.2Ftime-sharing)

It took Apple until MacOS 9.x to implement this as an additional API.

MacOS 9 was introduced in 1999. (Granted, Windows NT/9x and Unix/Linux had this sooner than MacOS.)

Check it out. Definitely worth a look.

Automated Conversion Widgets: These types of widgets have been live for a few days now.  The reception has been great and we are already involved in planning for a number of projects that will use the widget. So far, the two most requested additions to the widget are 1) a way to optionally configure a "Grab This Widget" link and 2) a smaller version of the widget that can fit in the sidebar section of a wordpress blog.  We heard your feedback and should be ready to release by tonight or tomorrow latest.

Video Player Widgets:   We've applied the feedback about smaller sidebar-sized widgets to our video player widget as well.  So, now, we have a sidebar sized video player that can redirect viewers to your own site or play the video right in the page where the widget is embedded.

Workaround For Embedded Widgets on Wordpress.com Blogs: We have a ridiculously simple workaround for embedding our video widgets on wordpress.com blogs that we are planning on releasing wordpress.com blogs. The workaround will be available as part of conversios done as part of the standalone upload page and also as part of the real estate social network Since we support youtube video and real estate shows in our own widget format, you'll be able to use the workaround for this content in the social network using our widget format as well.

Stay tuned.  More coming...