<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>success</status>
  <result>
    <project>
      <id>469525</id>
      <name>eviva</name>
      <created_at>2009-10-31T11:52:45Z</created_at>
      <updated_at>2009-11-12T17:56:28Z</updated_at>
      <description>EvivaThis idealistic project exists because I have this idea for a futuristic system and want to see a prototype of it.  First source commit is here on Google Code and the whole process will be open for anyone to see. 

In other words, development has just begun.  Expect 2+ years to pass before anything useful appears, and 5 years before something really mature surfaces.  Unless I manage to get this TDD project mode up and running. 

VisionFirst, increase application development speeds by making software development require dramatically less coding compared to what it is today. 

Second, democratize application development by less cryptic code syntax so many more people can enjoy the fantastic feeling of shaping their own creations. 

Third, empower each individual to tailor his or her own IT toolkit. 

First and second visions will be realized by the creation of the Eviva language. Third vision will be realized by creating an application using the Eviva language which will function as a platform for each individual IT toolkit. 

In other words, I'm fed up with spending days and weeks implementing data transfer and compatibility details caused by trying to use frameworks and programming languages to something way beyond what they were written to do in the 1970s. Despite bending and twisting them to new and really good ideas, coding applications still means much work. Why should all applications be tailor made when we know common patterns for applications?  Common patterns exists in administrative applications, web applications, desktop applications, web service applications, and the list could go on.  It is overdue time for a paradigm shift: Introduce a higher application level so that applications will be easier to write. The tradeoff is abstraction, i.e. control over fewer details.  Modern applications share common patterns.  By finding and utilizing these common ways of doing things, we will be able to construct applications by a fraction of their costs today.  Imagine science fiction programming.  Imagine taking the high-level mechanisms of database, web and desktop platforms to a new platform.  Focus on handling real world concepts and ignore field details for now. 

Initial solutionThe basic plans for the initial system is to read a concept model and then knowing the major data flow, where to read, where to write, where to listen, where to call other systems.  All details of how to view and arrange it on display as well as details of how to bind different data models together will be left to the system with the assistance of the user doing the initial tuning. 

With extensive Java background, I code the system in Java.  This project will start small to cover my own personal needs for an application environment, which is highly motivating and with a high potential for personal payoff.  I am starting off in nov 2009, so you know how fresh it is when you read this. 

Frame choicesApache License is logical for an open source project that aims to be further developed.  I have used Apache products for a long time and I admire what they have achieved.  Open source is fully satisfactory because if I will ever earn money from this, I expect it will be from contract work or councelling, not from selling the software. 

Google Code repository is chosen because I think the project will be safe and accessible to a lot of good programmers and along the way it will have adequate tools. 

Hopefully the project will become a spark for others on new projects or even some to join this project. 

Thor Hovden 

November 2009 

Bergen, Norway</description>
      <homepage_url>http://code.google.com/p/eviva/</homepage_url>
      <download_url></download_url>
      <url_name>eviva</url_name>
      <user_count>0</user_count>
      <average_rating></average_rating>
      <rating_count>0</rating_count>
      <analysis_id></analysis_id>
      <licenses>
        <license>
          <name>apache_2</name>
          <nice_name>Apache License 2.0</nice_name>
        </license>
      </licenses>
    </project>
  </result>
</response>
