Steal The Fish

...e gli ruba il pesce.

Andrea Dessì  //  Andrea, Man, about 20, (x)html operator, web lover.
I'm a Entando Developer!

Jun 28 / 7:51am

MooContentAssist 0.70.2 is out!

Just 3 weeks passed and a new version is out! :)

The big news:

  • there's a new demo with theme togglers
  • with the new demo also new APIs for applying the theme
  • configurable number of item shown in the box
  • scrollable result box, scrollable result box shows always the current item in the middle

So let's go download the latest version! -> http://mootools.net/forge/p/moocontentassist

Filed under  //  MooContentAssist   js   mootools  

Comments (1)

Jun 5 / 3:00am

MooContentAssist 0.68.2

New release for the plugin MooContentAssist, now it goes 0.68.2.

Not so much new in the source, just some fixing for the window position.

But in this version I've initialized the documentation stuff, so a first version is released.

Have a look:

Filed under  //  MooContentAssist   js   mootools  

Comments (1)

May 20 / 12:36am

Gmaps v3: Directions web service arrives at Google I/O

Directions web service arrives at Google I/O

Wednesday, May 19, 2010

Google I/O is always a fantastic opportunity for the Maps API team to meet face to face with some of the many Maps API developers worldwide. We believe our developer community is one of the biggest strengths of the Google Maps API, and with over 350,000 web sites actively using the Maps API, there is no shortage of skilled and helpful expertise to tap into.

However Google I/O is not the only way in which we engage with developers. The Google Maps API Google Groups are thriving communities and many of us on the Maps API team enjoy listening and engaging in discussions held on these Groups. In addition we also have the Google Maps API Issue Tracker, a tool with which any Maps API developer can report problems with the API, suggest new features that they would benefit from, or star existing issues or features.

The Google Maps API team takes the problems and ideas featured on the Issue Tracker very seriously, and although we can not always address every issue that is raised, we do consider any that attract a lot of stars. Recently one feature request in particular has been head and shoulders above the rest in terms of the number of stars it has attracted. It therefore only seems appropriate today, as we sit down with our developer community for a Fireside Chat, that we respond to that request by launching a Directions Web Service.

The Directions Web Service is a companion to the existing Geocoding and Elevation Web Services, and allows applications to obtain Driving, Bicycling, and Walking directions through an XML/JSON REST interface. All of the features of the Map API v3 Directions service are supported, including “avoid highways”, “avoid tolls”, and waypoint optimization (travelling salesman solver). For more information, check out the Directions Web Services documentation.

If you have a great idea for a new Maps API feature, please don’t hesitate to submit it to the Issue Tracker. If your idea proves to be popular, we’ll do our best to make it a reality.

Posted by Thor Mitchell, Maps API Product Manager

great! I've starred that issue http://code.google.com/p/gmaps-api-issues/issues/detail?id=235 for the enhancement.

huuh :D

Filed under  //  js   web  

Comments (0)

Jan 8 / 7:43am

When you need FAST MooTools documentation and you don't have connection... then .... use it offline! :)

Links to this post

  mootools.core: offline documentation [#818]

hi there,. i've made the documentation available for offline use. just wondering if you guys would like to link to it or not. http://sourceforge.net/projects/mootoolsdocgen/. and the page for it is here ...
Posted by koonkii (at hotmail) at December 27, 2009 2:19 PM

Create a Link

When you need FAST MooTools documentation and you don't have connection... then .... use it offline! :)

:E

Filed under  //  js   mootools  

Comments (0)

Jul 23 / 6:25am

Ancora AJAX Patterns

Ajax-fig1_small

Di tecnologie AJAX se ne parla tanto, sempre di più.
Vogliamo essere tutti più veloci tutti più attivi.

Ma di fatto:

  1. AJAX non è una tecnologia è un modo di pensare il flusso applicativo
  2. Si usano i vecchi strumenti per fare cose nuove
  3. La questione delle richieste a seconda del browser è ormai superata senza alcun dubbio

Rimangono comuqne dei big problem: browser history, accessibility, interface fragments and security.
Tutti parlano di ajax patterns di applicazioni e di tecnologie, di java e .net di GWT [...]
Ma nessuno si pone dalla parte dello sviluppo graduale e riusabile delle interfacce.

La domanda è: dato che per soddisfare le richieste client c'e' bisogno di risposte precise di singoli oggetti/dati, come faccio a non duplicare lo strato di presentazione?
Se sviluppo l'applicazione interamente senza ajax/javascript e poi ci voglio montare sopra qualcosa di dinamico la prima cosa che mi viene da pensare è: scrivere le interfacce in frammenti e OO.

Non so.

Guardare la figura sopra e vedere nell'esempio "classic" html+css data come risposta e nel secondo esempio "ajax" vedere xml data (che può essere qualunque cosa...) mi lascia il dubbio su come provvedere per la renderezzazione delle nuove informazioni.

anyway... we'll see

--
Andrea

Filed under  //  js   web  

Comments (0)