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

Today re-opened one of my favourite projects web page – and have been nicely surprised to see that there is a whole community behind it already (before years ago the project has been at very ground level). But today it may actually happens that haXe can be a very nice choice of implementation for PDM having it as been compiled at runtime using ncannasse’s lib.

PS. Intended switch from pure php based implementation was needed to be able to build PDM as loosely coupled to any language/platform as possible. Therefore the quest for best abstract implementation on the topic still continues, but today is one step further:
- one have to be able to write down script-like actions to be included in PDM as well as to be able to use already predefined/contributed ones.
- script-like actions are also modules part of the PDM project, therefore PDM itself can be used to maintain their dependencies (ever wanted to make things loop infinitely)
- PDM should leave focus on development, without messing over it. Its up to the developer who will use the implementations.

PS. May be even switch to Neko ?

Because I really got tired of the way how I manage my code (java, php, flex, csharp) – I’ve decided to try gather some first hand use cases which I encounter in my day-to-day work:

1) web project mixed from flex frontend UI, php 5 based restfull service + some java (just to ensure that everything is enough complicated )
2) web php 4 based project with some deep underground support from a social platform.
3) 1.1 .NET csharp project (very old one indeed)
and many more… Mostly I go throught writing code, pushing to source control managment system (read SVN and lately git), writing some more code, and again the process goes. As during all this write I intend to re-use as much as possible + I see myself ending with having more 3th party libraries involved than my own ‘wrapper’ implementation.

More→

I got tired of extra-complicated project development managers so far like maven, ant, phing & many many more… So as natural developer I’ve decided to create my own, at least to be used for my own ever growing code base

So here are some initial thoughts:

Goals:
- Dependencies management (modules, libraries, 3th party
contributions, git, svn, cvs)
- Development management (debug, release conditional builds)
- Deployment management (testing, packaging, install, release)
- Simple & flexible
– creation
– dependencies
– configuration (better without)

Basis example of project development upon given problem (project
exists because they solve problems):
1) create project
2) include dependencies
3) build
4) see
5) modify code (repeat 3 -> 5 until solution is found )
6) package (make library, executable, install)
7) distribute (upload the outputs, push to collaborative scm & etc.) More→