From: Andreas N. <an...@kl...> - 2003-11-19 19:53:56
|
On Tue, 2003-11-18 at 23:39, Teemu wrote: > > .. are you talking about porting mimerdesk to OI?? > > Not only porting, but creating something new on top of it in the same time. It > will have additional functionality necessary in learning organizations and > education. Today I had more time to look at it and the demo and this is really great ! I see, you aim at the educational area, but some tools like projects and calendar definetly have a broader usage. Acutally, you obviously implemented quite a bit, that we are also thinking about! Great! Also, I talked to a colleague, who does consultancy for public schools in Germany. He said, that many larger schools are looking for open source tools for such tasks and that there are funds for this ( called N21 ). We will check this out... Apart from this, we have our own fund for our tools and would like to cooperate, if this is imaginable. Our focus in the last months was to work on a configurable workflow framework, we call NATS. As soon as we have a sample app and more documentation, we will release this to the open source. Looking at mimer desk, this could be hiden behind the Tasks screen and pull in all types of tasks in the workflow? What do you think ? > > For a long time I have searched for time to get rid of current MimerDesk code > base (which is scarce, complicated and has its' limits) to replace it with > something better. OI and additional time (money) for open source development > came to rescue. Now I also have better possibilities to put my improved OO > programming kung fu in practice.. This is the key solution ! When I stumbled over OI two years ago, I was in the middle of thinking about a self written framework, because at that time there was really nothing you could work with - all OO Perl things needed to be done from scratch. Looking back, we definetly made the right decision to take OI. I am really convinced, that there is no other tool, that can make you just as productive - regardless of dev language. Our first tries had there problems, of course, one of which was the misuse of SPOPS. Also, at that time there was no OpenInteract::CommonHandler, which is really the way to go for most things. Then we put to much functionality in the handler packages, which is not a good idea. Today we build separete classes that ( most of the times ) inherit from SPOPS and put the functionality in them. This on one side lets you use the functionality in scripts without a GUI, but also gives you the full power directly within the templates ! later, Andreas |