Patches are OK, but you lack all the social aspect that is enabled with git and its tooling (be it pure git + gerrit or github with the comments on commits and pull [...]]]> In a recent post, I described how to contribute a patch to an eclipse project using git as its version control system.

Patches are OK, but you lack all the social aspect that is enabled with git and its tooling (be it pure git + gerrit or github with the comments on commits and pull requests)

As of today, pull requests are not accepted by Eclipse committers since they lack IP (Intellectual Property) information, and the official git repositories at eclipse are hosted by the foundation not on github (github repositories of Eclipse projects exist for mirroring only).

Recently talking with a committer on the Eclipse Tycho project (Tobias Oberlies not to name him), he suggested to me to share my contributions via github, instead of attaching patches, as long as the git contribution scenario is followed

To comply with this suggestion,

1. I would clone the official repository at git.eclipse.org

git clone http://git.eclipse.org/gitroot/tycho/org.eclipse.tycho.git

2. work on my changes, test them, add them, and commit them for each functional change

git add myfile1 myfile2

git commit -m "BZ xxxxxx : comment"

3. create a new repository on my github account

4. synchronize my new github repo with the official tycho repository

git remote add origin.github git@github.com:anthonydahanne/org.eclipse.tycho.git

« behind proxy » users can use https access instead,

git remote add origin.github  https://anthonydahanne@github.com/anthonydahanne/org.eclipse.tycho.git

5. push my committed changes to my github repository

git push -u origin.github master

6. add a comment to the bugzilla entry describing the fix or new feature I worked on, giving the github commit id

7. accept the IP conditions of the Eclipse foundation

That’s it ! you just contributed some code to a cool Eclipse project !
OK, it seems more complicated than just submitting a patch or a pull request, but once your local repo is set up,
you should have something like :

git remote -v
origin  http://git.eclipse.org/gitroot/tycho/org.eclipse.tycho.git (fetch)
origin  http://git.eclipse.org/gitroot/tycho/org.eclipse.tycho.git (push)
origin.github   https://anthonydahanne@github.com/anthonydahanne/org.eclipse.tycho.git (fetch)
origin.github   https://anthonydahanne@github.com/anthonydahanne/org.eclipse.tycho.git (push)

and it is just a matter of juggling between the original repo, synchronizing the latest changes

git pull origin master

and the github repo (pushing the latest changes)

git push origin.github master

and copying/pasting the commit ids to the bugzilla entry.

I’m still relatively new to Git, so if you think there are better ways to sync the repositories, then please add a comment to this post !

To go deeper on that topic :

• http://wiki.eclipse.org/EGit/Git_For_Eclipse_Users
• http://wiki.eclipse.org/Development_Resources/Handling_Git_Contributions
• http://wiki.eclipse.org/Tycho/Contributor_Guide#Contributing_the_Patch

En lisant un article faisant référence à un serveur mal sécurisé ; j’ai été pris de quelques doutes : et si mon serveur dédié était lui aussi mal sécurisé ? Étant développeur et adepte [...]]]> Assomption avant de commencer : Bien entendu, vous êtes à jour des derniers correctifs de sécurité de l’ensemble de vos services…

En lisant un article faisant référence à un serveur mal sécurisé ; j’ai été pris de quelques doutes : et si mon serveur dédié était lui aussi mal sécurisé ?
Étant développeur et adepte de l’auto hébergement (oui je ne suis pas un grand fan des services hébergés chez les géants du net avec leurs clauses de confidentialité obscures…) je fais évoluer mon serveur dédié (services qui tournent dessus) au rythme de mes besoins… ce qui fait que la sécurité passe souvent au second plan…
Et rien de tel que de jeter un coup d’œil à la sécurisation de ces services de temps en temps…

Audit rapide et efficace

On commence avec nmap, avec les options qui vont bien :

sudo nmap -A mon.serveurdedie.fr

On peut alors commencer à l’analyse du résultat, et à remédier aux problèmes.

DNS et Bind

Dans le rapport obtenu par nmap, si vous voyez :

| dns-zone-transfer:

et ensuite la liste de vos sous domaines; méfiance, cela veut dire que quiconque peut lister vos sous domaines; pas forcément une bonne idée si certains d’entre eux sont là pour des tests ou pour des services non publics…

Les solutions

Rendez vous dans votre fichier de configuration de bind, /etc/bind/named.conf.options, et ajouter les options suivantes :
 allow-transfer { x.x.x.x; }; --> uniquement donner accès aux informations détaillées des zones à cette IP (votre dns secondaire)
 version "Ma version"; --> pourrait derouter certaines attaques en offuscant la version de Bind; mais comme disent certains, l'obfuscation est rarement une bonne méthode de sécurisation...
 fetch-glue no; --> défendre votre serveur dns aux attaques de type déni de service
 recursion no; --> défendre votre serveur dns aux attaques de type déni de service

Ces informations sont issues d’un article de TechRepublic , et n’hésitez pas à vérifier votre configuration avec zonecheck

HTTP et Apache

Dans le rapport obtenu par nmap, si vous voyez :

80/tcp  open     http         Apache httpd 2.2.9 ((Debian) DAV/2 SVN/1.5.1 PHP/5.2.6-1+lenny13 with Suhosin-Patch mod_wsgi/2.5 Python/2.5.2)

Et bien cela signifie que votre serveur est très bavard…

La solution

Sur Ubuntu, dirigez vous vers /etc/apache2/conf.d/security et éditez :

ServerTokens Prod

ServerSignature Off

TraceEnable Off

Si vous utilisez PHP, faites aussi un tour du côté de  /etc/php5/apache2/php.ini

expose_php = Off

Encore une fois, l’offuscation n’est pas une méthode de sécurisation en soit, mais moins les potentiels attaquants en savent, mieux c’est…
Ces informations sont issues de DebianAdmin

SSH et OpenSSH

Pour l’instant je ne peux que conseiller de lire cet article : http://www.cyberciti.biz/tips/linux-unix-bsd-openssh-server-best-practices.html

à suivre…

Nothing terrible actually, let’s take the example of a contribution to the p2 project (part of the equinox umbrella at the Eclipse foundation)

Lucky because it was my first time at EclipseCon, my first major conference in North America (it was located in Santa Clara, in the Californian Silicon Valley) and also because my employer, Compuware, agreed to let me go [...]]]> From the 21st to the 24th of March, 2011, I was a lucky attendee of EclipseCon 2011.

Lucky because it was my first time at EclipseCon, my first major conference in North America (it was located in Santa Clara, in the Californian Silicon Valley) and also because my employer, Compuware, agreed to let me go there, along with 2 of my colleagues.

EclipseCon 2011 was great, because

• the main actors of the Eclipse community were there : people I may follow on twitter or ask questions to on several mailing lists; the committers of the projects I use everyday at work; being able to chat with them and ask them questions (even harass them ! no I’m kidding, I did not harass Jeff during 2 days! )
• the talks were diversified and most of them were really interesting, you have below links to some of the talks I attended while there.

Attending this conference made me also realize, maybe once more, that meeting with other developers working on the same technologies, is really inspiring, motivating, and it makes you grow technically.

Ok, you got the picture, I enjoyed the conf !

Here are some of the talks I attended:

• Under the provisioning (p2) and release engineering themes,

1. p2, your savior or your Achilles heel? Everything an Eclipse team needs to know about p2 at EclipseCon 2011
2. Discovering the P2 APIs at EclipseCon 2011
3. Tycho presentation and tutorial at EclipseCon 2011
4. Next Generation Development Infrastructure: Maven, m2eclipse, Nexus & Hudson at EclipseCon 2011
5. Growing an open source project one bugday at a time at EclipseCon 2011

• Under the architecture ,  performance and OSGI themes,

1. Stop the Architecture Erosion of Eclipse And Open Source Projects at EclipseCon 2011
2. Using and Extending Memory Analyzer into Uncharted Waters at EclipseCon 2011
3. OSGi introduction and OSGi 4.3 at EclipseCon2011
4. 10 signs you’re doing OSGi wrong at EclipseCon 2011

• Under the Eclipse tooling theme,

1. Android Development with Eclipse at EclipseCon 2011
2. Getting Eclipse Preferences Under Control in Teams at EclipseCon 2011

• Other really cool talks

1. Keynote on Apache Hadoop at EclipseCon 2011
2. Virgo and RT playing together at EclipseCon 2011
3. Effective Git Tutorial

If you want my opinion, well, I’d say that Tycho, p2, Virgo, git along with gerrit, and Eclipse Memory Analyzer were predominant topics; you could definitely not ignore them.. and not like them neither !

If you did not, you’ll hear from these great technologies in the next few months !

False assumptions learned in the last 10 years (that Hadoop has been building with this in mind)

Four presenters were present : Stefan Lay, Shawn Pearce, Matthias Sohn and Chris Aniszczyk.

They began with a very quick  presentation of Git, [...]]]> First of all, we had to prepare our desktop, using those instructions, which I did, one day ahead of the conference, using the official Egit repo (Egit 0.11.3) and eclipse 3.6.2.

Four presenters were present : Stefan Lay, Shawn Pearce, Matthias Sohn and Chris Aniszczyk.

Presentation

They began with a very quick  presentation of Git, that they defined as a tool to facilitate code review, and then Git at Eclipse

• a roadmap has been defined to move to git
• CVS is being deprecated

They defined what is a modern code review and its benefits

• when a developer writes code, another checks it
• 4 eyes catch more bugs
• mentoring of new developers
• establish trust relationships
• good alternative to pair programming
• coding standards

Git sits between the developer desktop and the CI machine : as a tool to review code and accept changes

Tutorial

For the tutorial, I chose the HTTP protocol rather than SSH, to make sure I would not suffer from any eventual proxies.

When cloning the sample git repository, I noticed that you can specify another destination folder than your current workspace directory, Stefan mentioned it is to allow you to have your git repo not deleted when you delete your workspace… (anyway, you can also clone to your workspace, just as with Subversion)

• First connection test

right click : team->remote->configure push to upstream…, and then add refs/for/master in the ref spec (or else it will try to push to the master repo); the magic Ref refs/for/master represents the Gerrit code review queue for the master branch on the server.

Then click save and push, it will fail because there were no changes; but you just had the opportunity to check your settings are ok.

Exercises :

All the exercises are described here.

During those exercises, we created a local change, then submit it for a review in gerrit.

Just after sending my changes, Hudson was triggered to launch a build against my local branch that I just committed.

Then, the build passed (alright !) and it was really fun since people in the room would review my changes with comments; finally someone approved my changes and my changes were merged into the master branch.

Other exercises implied more advanced workflow such a submitting other change sets and registering projects to monitor, but I did not have time to do them all; actually I strongly advise anyone wanting to try gerrit out to complete those exercises. (you will have to do them with a friend, since someone will have to accept your changes

Actually, I was really impressed with this tool : it really changed the perception I had of code review (with patches sent via email + code review on the desktop of the co worker); just letting the developer do all the changes he want, then see Hudson builds his changes, ask a reviewer (or a reviewer adds himself to the bug), see the file to file comparison, the comments in the gerrit web interface… I’m totally convinced !!! Social coding for real !

I had a chat during this session with Shawn Pearce, from Google, the actual author and main contributor of Gerrit; he explained to me how people and organizations (including Google developers) were hooking Gerrit with Mylin, IRC, Hudson; for now using SSH and the web UI, but he told me a web service interface (based on REST) was on his mind; to ease integration with external tools; as for the authentication, he told me that Gerrit could be linked with Bugzilla and being part of a SSO scheme , using your enterprise LDAP for example

I did not expect so much from this git and gerrit tooling, you got to see it to believe its awesomeness !!!

This article explains why I decided to create a new project, and also what I did differently for this new Android app.

First of all, the name [...]]]> On Tuesday 21st of December 2010, I officially launched ReGalAndroid, the follow up of G2Android, aiming at providing G3 and Piwigo support.

This article explains why I decided to create a new project, and also what I did differently for this new Android app.

Why creating a new project ?

First of all, the name of the app (g2android) did not reflect what I wanted it to be: I wanted it not to be specific to a gallery type (G2) but also compatible with G3 and Piwigo.
In the android world, an app is defined by its package name; since I wanted to change from net.dahanne.android.g2android to the new name net.dahanne.android.regalandroid I had to create a new app.
Sure, I could have keep on using the old package name, but it did not make sense, and also I wanted to start refactoring the app modularizing it.

Modularizing an Android app, using maven-android-plugin

In G2Android, one of the things that frustrated me most was the way it was built : it had dependencies on libraries (jars) not part of the android runtime. So I had to include them in a lib directory; adding them to the classpath so that the Android Developer tools knew that G2Android needed them.
Another problem was the modularity of the application : the Gallery2 client API code was mixed with the Android UI code; it could become a nightmare for testing, as for plain Junit test cases, I had to remove the android.jar lib from my classpath (and Android integration testing was not an option as it takes really too long to launch; and does not make sense to test an HTTP client api…)
Starting ReGalAndroid, the first thing I did was modularizing the application :

• one standard jar maven project for the commons classes (Pictures, Albums, etc..) with its regular Junit tests

• one standard jar maven project for each gallery client java api (one for G2 extracted from g2android, and 2 new ones, one for G3 from scratch, and one for Piwigo extracted from Jiwigo, an existing Java Swing client for Piwigo) with their regular Junit tests

• one android maven project with only android related classes, this project heavily depends on the common module and the 3 gallery implementations; this has been possible thanks to the maven android plugin

To ease the process inside Eclipse, you can use Maven Integration for Android Development Tools , it will allow you to launch your Android application from the IDE, just the same as before.

This way, I am now able to test the remote API implementations independently of the main Android app; and also if someone wants to reuse those implementations for any other Java projects, he can just check out those plain java projects.

Logging an android app using slf4j-android

If your Android application depends on plain java projects; those projects certainly do not use Android logging framework.

So if you want to log all your modules in your android app, you can use slf4j : this is meta API where you can choose at compile time which logging API you will use.

For example, in all the logged classes of ReGalAndroid, I’m depending on org.slf4j.Logger and org.slf4j.LoggerFactory , even in the Android module.

But in my maven dependencies; I tell my android module to depend on slf4j-android :

<dependency>
<groupid>org.slf4j</groupid>
<artifactid>slf4j-android</artifactid>
<version>1.6.1-RC1</version>
<type>jar</type>
<scope>compile</scope>
</dependency>

That way, each call to LoggerFactory.getLogger(My.class)  in any of my modules will be wrapped to the android.util.log APIs

Cool thing is, if anyone wants to use any of the remote gallery implementations (G2, G3 or Piwigo client) in its Java app, he will be able to use Log4J or logback, or any other slf4j bridge he wants !

Moving from Google code to GitHub for code hosting

I’m quite satisfied with Google Code hosting; in fact I still use it as a wiki and a bug tracker; the truth, I wanted to become familiar with Git, to test its benefits.

As I was not starting from scratch, I wanted to be able to keep the history of my project

There is an easy way to do so in GitHub : create a new project, and then select ‘Importing a Subversion repo’; but unfortunately, it did not keep track of all my tags; so I chose to go with the manual way.

Export google code svn repo to a local git repo

I use this utility called svn2git, I had to check out from GitHub : svn2git

It is written in Ruby, so you have to make sure you have ruby and rubygems installed.

Then, according to your gems directory, you can run it :

/var/lib/gems/1.8/bin/svn2git https://g2android.googlecode.com/svn/  –verbose

All the svn tags are imported as git tags (git tag to check all the tags are there) but the authors are not imported (« (no author) author not found in authors.txt)

To manually change the authors name, I found the solution reading this post.

git filter-branch -f --env-filter "GIT_AUTHOR_NAME='Newname';  GIT_AUTHOR_EMAIL='newemail'; GIT_COMMITER_NAME='Newname';  GIT_COMMITTER_EMAIL='newemail';" HEAD </code>

From now on, you have a local git repo with all your code  from your SVN (including the tags !) in a local git repo; let’s share this one !

First create a new repo on github (using the web interface), then set your local repo as the origin :

git remote add origin git@github.com:anthonydahanne/ReGalAndroid.git

Finally, sync the local and remote , including the tags of the master branch :

git push origin master --tags

And youŕe done migrating from Google code SVN to GitHub !

Migrating your users from a previous android app to a new one

The problem when you’re creating a new android application to replace a previous one, is that the users having the old app installed on their phone will not be notified of the availability of the new one, since the package name of your new application (referenced in your AndroidManifest.xml file) is different :

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="net.dahanne.android.g2android" android:versionCode="15" android:versionName="1.6.3">
 
</manifest><manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="net.dahanne.android.regalandroid" android:versionCode="2" android:versionName="1.0.1">
</manifest>

Then the market you’re using (let’s say Android Market) is not aware of your new application replacing the previous one.

For the particular case of the migration from G2Android to ReGalAndroid, I first, during a month, advertised the new app on Twitter, and on the dedicated G2, G3 and Piwigo forums and websites; so that I could have some early adopters.

Then, in a second step, to accelerate the migration, I updated G2Android, with a new activity, launched by default on startup to tell the user that the application is not maintained anymore and that he should tap on the button to download the new application.
Here is the source code to redirect users from the old android app to the new one

At the time of writing this blog post, here are the statistics reported by Android market about both apps :

It means that the migration is quite slow, since many users still have the old application installed on their phones; I may remove the old app from the market in the next few months to make sure they do not use it anymore (please note that ReGalAndroid is also available via other markets and also via direct download)

The final words

The application is open source and if I receive many issues and functional requirements via the ReGalAndroid bug tracker (and I thank the users for that, it clearly influences the path the application is taking) I would love to see new contributors and committers add some code (see the ReGalAndroid github repository); because this is before all what makes the app

Here are the steps I followed to create this project.

Creating this project, I wanted a lightweight Java library, easily embeddable in an Android application  (G2Android not to name it, a [...]]]> I finally started a java library to implement Gallery3 REST remote API; g3-java-client (the name is not really original huh ?!)

Here are the steps I followed to create this project.

The technical choices

Creating this project, I wanted a lightweight Java library, easily embeddable in an Android application  (G2Android not to name it, a Gallery2 client for Android).

So I carefully designed my dependencies, in order to leverage Android already included libraries, such as Apache Http Client, org.json packages (by the way I initially wanted to use the jersey REST client API, but… I wanted to stay as close as possible to the Android platform…)

Finally, I’m developing this library using TDD, and Maven as a CI tool :  I want a really reliable library, for 2 reasons : because it is motivating to create quality code, and also it is really painful to test an android application (you have to start an emulator or AVD and deploy the binary each time you launch a test, and each of these steps can take time) .

The licensing

I chose GPL v3 to make sure my work remains open source and not used in any commercial projects.

I’m using maven-license-plugin to add the license to the source files.

The hosting

I chose Github, mainly because I wanted to get familiar with git : I have heard so many people happy using Git instead of SVN,  and I also wanted to be able to switch easily from trunk to another branch… sounded appealing to me !

To tag the sources, I decided to follow Ulrich’s steps using mvn-release-plugin to tag every new release (in French, but you can follow this link to have an equivalent article in English)

And to host the binaries, I created a maven repo out of  a new Github project following Chas’tutorial; sure I could have asked to host my project on Sonatype’s Nexus for Open Source Software, but as the project is actually really young, I prefer to use my own repo; I guess later on I’ll switch to this better solution.

The commands used

If I had to initialize the workspace from another computer, I would type the following commands :

mkdir g3-java-client
git clone git@github.com:anthonydahanne/g3-java-client.git
cd g3-java-client/
#to make sure everything (compilation, testing) is ok
mvn clean install
#to add the license header to the source files
mvn license:check
mvn license:format
#to commit the changes to github
git commit -a -m 'commit message'
git push origin master
#to release a new version  (be careful there is no file named release.properties at the root of the project)
mvn release:prepare

We just added the license info, committed the snapshot version , committed the stable version and also created a new branch (mvn release:prepare)

Now, we can deploy it to a maven repo

#to deploy the current version to a repository on my local file system :
mvn -DaltDeploymentRepository=snapshot-repo::default::file:../../m2repo/snapshots clean deploy
#to commit this repo to github (I created this Github repo to serve as a maven repo http://github.com/anthonydahanne/m2repo)
cd ../../m2repo/snapshots
git commit -a -m 'new snapshot for g3-java-client'
git push origin master

Pretty clear and easy right ? (except the deploy phase…) all of this thanks to Maven and my pom configuration.

What’s next ?

First, finish implementing all the Gallery3 REST remote API commands; and then, create a new android project (G3Android ?!) to consume this library; using … maven-android-plugin of course !

-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y

So for example, if you want to debug an ant launch (launched via « ant -f myBuild.xml » for example), you simply have to set ANT_OPTS; on windows :

set ANT_OPTS=-Xdebug [...]]]> As long as you’re using a java application (ie an application calling your JVM), you can enable the debug mode with these parameters :

-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y

So for example, if you want to debug an ant launch (launched via « ant -f myBuild.xml » for example), you simply have to set ANT_OPTS; on windows :

set ANT_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y

Another example, with JBoss :

set JAVA_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y

and then you can debug your launch with Eclipse, for example, creating a new debug configuration (remote java application on port 8787) !
Option : you can choose whether or not the application should wait for your debugger setting suspend to y or n.

As always, you can get more info going to the project web page : http://code.google.com/p/g2android/, and even download the new [...]]]> Here is the new stable release of G2Android, your favorite Gallery2 application for Android, and great new features are now available :

• new cache feature
• fullscreen navigation with gestures
• download full res. picture to sdcard

As always, you can get more info going to the project web page : http://code.google.com/p/g2android/, and even download the new version
So what’s next ? tweeting and sending email with photo url, shortcuts for full screen navigation, synchronization between views… well, expect a new version by the end of November !

Vous vous apprétez à vendre ou à [...]]]> Envie d’effacer toutes les données d’un disque dur avant de le revendre ?
Envie d’effacer toutes vos données personnelles qui se situe dans un répertoire en particulier (sous windows), sans formater tout le disque ?
Suivez le guide !

Effacer de manière sécurisée toutes les partitions d’un volume

Vous vous apprétez à vendre ou à donner votre vieil ordinateur, et vous ne voulez pas que l’ensemble de vos documents privés se retrouvent sur internet ?

Dans ce cas, il ne suffit pas d’effacer vos fichiers via l’OS (ce qui ne les efface que de la table de registres du disque), ni de formater la partition (un logiciel de « recovery » serait capable de la reconstituer); ce qu’il vous faut, c’est réécrire plusieurs fois, avec des algorithmes éprouvés, des données aléatoires sur l’ensemble du disque.

Il existe pour cela pléthores d’outils payants (et qui n’ont pas l’air d’avoir la côte), et il existe DBAN, outil GPL de choix.

DBAN (Darik’s boot and Nuke) est un logiciel libre, redoutablement efficace, qui, même s’il n’est plus maintenu depuis 2007, vous propose plusieurs algos pour effacer votre disque de manière sécurisée (réécrire 1 fois dessus -> +rapide; 3 passes avec algo conforme au Department Of Defense américain -> +long)

Ce logiciel s’installe sur une clef USB, ou un CD-R, ou une disquette; bootez dessus (branchez auparavant sur votre ordinateur les périphériques que vous souhaitez effacer), tapez « autonuke » à l’invite de commandes, patientez, et c’est réglé !

Vous voulez en avoir le coeur net ? être sûr que DBAN a bien fait son travail ?

On peut faire une vérification sommaire, en tentant de retrouver des partitions sur le disque avec l’outil Testdisk, en GPL sous Linux/Windows/MacOs (etc..); le résultat est sans appel : après analyse complète du disque à la recherche de la moindre partition :

TestDisk 6.10, Data Recovery Utility, July 2008
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
 
Disk /dev/sdc - 81 GB / 76 GiB - CHS 9965 255 63
 
Partition                  Start        End    Size in sectors
 
No partition found or selected for recovery

Effacer vos données personnelles d’un répertoire

Vous utilisez régulièrement un ordinateur au bureau, vous y avez stocké des documents confidentiels, et vous vous apprétez à ne plus utiliser ce poste de travail ?

Vous pouvez alors utiliser Eraser, encore un logiciel libre sous GPL (mais malheureusement que pour Windows), qui appliquera les mêmes algorithmes de suppression que DBAN, mais dans des répertoires au choix, et non pas un volume entier; Eraser est facile à utiliser (version portable, pas besoin d’être admin pour s’en servir), et est encore maintenu à ce jour

Références :

http://www.webopedia.com/DidYouKnow/Computer_Science/2007/completely_erase_harddrive.asp

Now, you can still see your albums and pictures, but you can also :

The ergonomy is not yet perfect, as you may have [...]]]> I’m writing this small post just to indicate that the new version of the open source Gallery2 client for the android platform, G2Android, is out !

Now, you can still see your albums and pictures, but you can also :

• upload photos
• create new albums

The ergonomy is not yet perfect, as you may have already noticed, even though almost everything is multi threaded (using AsyncTask), meaning the ui won’t freeze anymore; the next features will probably will allow the user to insert a photo to his gallery from every picture context on the android platform (declaring a « share image » intent)

Stay tuned !