As DAssistA now has full featured abstract multi-core (check it out at http://github.com/outbounder/haxe.org.multicore ), time had been used to make the following module additions:

- GitBash wrapper
- FileSys wrapper (only xcopy)

Soon or later and installation package will a raise in front our eys.

Until then think of the following features:
- easy extendibility using CLI interface for autogenerating  DAssistA modules all around the projects repo
- same thing use but for other projects, languages, platforms & etc.
- automatic download & update.
- project dependencies
- phyton/text-mate cli integration
- something else?

As project development is so different as developers they are – then and DAssistA should be able to match on every requirement. One of the ‘must’ features for project build tools is to be able to interpret code at runtime, like many others (ruby, phyton, php). This is as easy as the one have running in its backyard a interpretor. But this is not DAssistA’s case, where the tool needs a lot more flexibility while keeping it strict & damn simple. Having in other hand haXe & its core based on compilation idea makes things even harder. But unfortunately nekovm comes with bunch of beautiful features & haXe can make use of them well.

Having only half an hour & a little knowledge of haXe, however proved successful because now DAssistA can execute at runtime any haXe written code under nekovm. The only thing which should be made is that the code should be structured as module & implement a simple interface like this:

interface IhaxeCode
{
   function execute(context:Dynamic):Dynamic
}

Thus  by writing such modules around will actually evolve DAssistA at some time to the need of multi-module-core.

Any ideas? (wonder)

Schema
Source

PS. Current solution requires haXe compiler.

First have to mention that the name makes the project. And the name is: DAssistA where its slogan(manta) should sound like “Project Development Assist”.

Here is the updated look & feel of it. While looking at this is not enough,

try fetching this: http://github.com/outbounder/DAssista
or even better -> forking it

And have to mention that cygwin is just a wonderful “hack” on windows. even better – combined with e-texteditor. It has cool implementation, it is fast & it is furious , only have been thinking “Why it is not free? or at least to use “name your price” method like creately.com“. Sadly it does not neither of those two… And therefore there aren’t so many working bundles on windows for it

And it was only near 20 years ago… Today -our- internet just does not sleeps. And as it will never fall asleep I expect that the network connecting so many people today – will become skeleton for the future. Interesting to say but currently our little www behaves more or less like our own so called in the past ‘nature’. See where ‘only the strongest, most adaptive & flexible will survive” and evolve. And such logic can be applied among our products/methodologies & even ideas.

While I was just passing by through world wide web’s surface found some interesting article which actually makes DAssist event more elegant in its implementation core doap project specification. Also it would be great to be able to track down project’s authors & inter-link credits to/from them via webFinger. Thinking in such direction – there is about time to have one simple-understandable structured data protocol. Such examples of reading are foaf & xrd.

Anyway DAssist moves in the forward direction…

DAssist

Just do not know what to put in the “?” box