Ajatus newsNews and blog postings about Ajatus - the distributed CRMhttp://www.ajatus.info/news/2008-08-28T07:49:39+00:00ajatus@ajatus.infoFeedCreator 1.7.6(BH) (info@mypapit.net)ETech 2009 CFP: Building the peer-to-peer business network2008-08-06T16:59:04+00:002008-08-06T16:59:04+00:00http://www.ajatus.info/midcom-permalink-550003f063dd11dda0925dd43a4390ac90achenri.bergius@iki.fi (Henri Bergius)ETech 2009, the O'Reilly conference on emerging technologies now has a call for papers. Here is my proposal for the "Nomadism & Shedworking" track:
The recent direction of business applications has been centralization to web-based systems, easing deployment, upgrades and management of application security. However, at same time centralization provides new risks like the introduction of a single point of failure for application usage and in most cases inability to work offline.
At the same time, working culture has started so shift more towards networked individuals, or "web workers" forming ad-hoc coalitions to work on various projects. For them, centralized applications might not be desirable due to data ownership and infrastructure requirements.
Moving the applications from centralized web servers to a peer-to-peer network allows web workers to be in control of their own data, stay productive even in unstable connectivity situations, and collaborate easily with their colleagues in an ad-hoc way.
This talk outlines some ways to move forward in building peer-to-peer networked business applications. There are many open source frameworks targeting the problem, including replicated databases like CouchDb and Prophet, and application-oriented P2P networks like Swallow/DBE. These will be discussed together with some real-world examples of business applications built with them:
Ajatus - a "Personal CRM" built on top of CouchDb, a RESTful replicated object database
OpenPsa - project management system doing resourcing over the DBE P2P network
Simple Defects - a P2P bug tracking system built on top of the Prophet replicated database
The first phase of P2P business applications will likely be services operating in closed networks of users' social networking or instant messaging contacts. But the P2P model can also provide opportunities for wider networking, making it possible to find new project partners or collaborators anywhere in the world. This wider-ranging business network will introduce new challenges like security and reputation management. Some ideas related to this will also be discussed.
]]>ETech 2009, the O'Reilly conference on emerging technologies now has a call for papers. Here is my proposal for the "Nomadism & Shedworking" track:
The recent direction of business applications has been centralization to web-based systems, easing deployment, upgrades and management of application security. However, at same time centralization provides new risks like the introduction of a single point of failure for application usage and in most cases inability to work offline.
At the same time, working culture has started so shift more towards networked individuals, or "web workers" forming ad-hoc coalitions to work on various projects. For them, centralized applications might not be desirable due to data ownership and infrastructure requirements.
Moving the applications from centralized web servers to a peer-to-peer network allows web workers to be in control of their own data, stay productive even in unstable connectivity situations, and collaborate easily with their colleagues in an ad-hoc way.
This talk outlines some ways to move forward in building peer-to-peer networked business applications. There are many open source frameworks targeting the problem, including replicated databases like CouchDb and Prophet, and application-oriented P2P networks like Swallow/DBE. These will be discussed together with some real-world examples of business applications built with them:
Ajatus - a "Personal CRM" built on top of CouchDb, a RESTful replicated object database
OpenPsa - project management system doing resourcing over the DBE P2P network
Simple Defects - a P2P bug tracking system built on top of the Prophet replicated database
The first phase of P2P business applications will likely be services operating in closed networks of users' social networking or instant messaging contacts. But the P2P model can also provide opportunities for wider networking, making it possible to find new project partners or collaborators anywhere in the world. This wider-ranging business network will introduce new challenges like security and reputation management. Some ideas related to this will also be discussed.
]]>Scrum in management of a small software consultancy2008-06-11T13:00:53+00:002008-06-11T13:00:53+00:00http://www.ajatus.info/midcom-permalink-4411d84037cb11ddb6b3b712548397ac97achenri.bergius@iki.fi (Henri Bergius)
Over the years we at Nemein have been experimenting with various ways of keeping our operations managed. Now with some personnel changes including Joe's departure it was a good time to change the way we work again.
I had some goals:
Keeping status of different projects up-to-date with more accuracy
Ensuring our sales and project management knows if some project is being blocked by missing materials
We're a small company of less than 10 people, and as such most project management methods have not been very successful for us. In general they have been made for situations where same person or team keeps on working on a project for several months, whereas in our situation a person typically works on several projects every day.
I discussed this over some beers with Tero Heikkinen from Rohea, and he told me how they were implementing Scrum in their small company. While their number of different projects running at the same time is a bit smaller, their situation otherwise is quite similar: same technologies used, Ajatus for work tracking, etc.
We had a company sauna evening and I presented Tero's ideas there: we would partially implement the Scrum model, and keep tuning it to our needs. At the first phase this means:
Every morning we have an all-hands 15-20min meeting ("the daily Scrum") where everybody goes over what they have been doing the previous day, and what they were planning to do today. If they are being blocked by something missing: a software bug, missing information or other materials, this is also brought forward
Every project has a file in Google Docs where we keep the project status and task list (Backlog). This task list is updated based on what comes up in the morning meeting
Work hours are reported with Ajatus. Rohea also uses it for project burn-down charts, and once their add-on for that is finished we may do the same
Emilia, the project manager (or Scrum Master) is responsible for resolving possible impediments and maintaining the per-project status files
The approach we have taken should be quite pragmatic and low-tech. Instead of fancy project management software we use simple word processing for status data. And thanks to Google Docs the documents produced are accessible and editable from anywhere.
Similarly the actual meetings are quite easy to manage. The people who are at the office attend there, and others attend either via a Skype or mobile phone conference call, depending on network availability. We decided to have them at 10am so that everybody will be able to participate. Even if there is a Sprint or meeting scheduled for the same time, the short time needed for our all-hands meeting means it can be held over a "cigarette break".
Ajatus is the only more experimental piece of software in our puzzle. In our company, we use it for hour reporting, expense tracking and keeping meeting minutes. For these it works quite well, although more reporting tools are definitely needed. The alpha status of CouchDb, the database software powering Ajatus has bit us a few times by database corruption (caused by OSX-specific erlang bug) or simply difficult installation procedure, but these problems will hopefully improve over time.
We're now in the second week of this model, and at least the gut feel is that this has improved coordination inside the company. The next challenge then is to let the customer get involved in the process. This can mean just sharing the project status files, or even giving them access to actual meetings or the Ajatus data.
]]>
Over the years we at Nemein have been experimenting with various ways of keeping our operations managed. Now with some personnel changes including Joe's departure it was a good time to change the way we work again.
I had some goals:
Keeping status of different projects up-to-date with more accuracy
Ensuring our sales and project management knows if some project is being blocked by missing materials
We're a small company of less than 10 people, and as such most project management methods have not been very successful for us. In general they have been made for situations where same person or team keeps on working on a project for several months, whereas in our situation a person typically works on several projects every day.
I discussed this over some beers with Tero Heikkinen from Rohea, and he told me how they were implementing Scrum in their small company. While their number of different projects running at the same time is a bit smaller, their situation otherwise is quite similar: same technologies used, Ajatus for work tracking, etc.
We had a company sauna evening and I presented Tero's ideas there: we would partially implement the Scrum model, and keep tuning it to our needs. At the first phase this means:
Every morning we have an all-hands 15-20min meeting ("the daily Scrum") where everybody goes over what they have been doing the previous day, and what they were planning to do today. If they are being blocked by something missing: a software bug, missing information or other materials, this is also brought forward
Every project has a file in Google Docs where we keep the project status and task list (Backlog). This task list is updated based on what comes up in the morning meeting
Work hours are reported with Ajatus. Rohea also uses it for project burn-down charts, and once their add-on for that is finished we may do the same
Emilia, the project manager (or Scrum Master) is responsible for resolving possible impediments and maintaining the per-project status files
The approach we have taken should be quite pragmatic and low-tech. Instead of fancy project management software we use simple word processing for status data. And thanks to Google Docs the documents produced are accessible and editable from anywhere.
Similarly the actual meetings are quite easy to manage. The people who are at the office attend there, and others attend either via a Skype or mobile phone conference call, depending on network availability. We decided to have them at 10am so that everybody will be able to participate. Even if there is a Sprint or meeting scheduled for the same time, the short time needed for our all-hands meeting means it can be held over a "cigarette break".
Ajatus is the only more experimental piece of software in our puzzle. In our company, we use it for hour reporting, expense tracking and keeping meeting minutes. For these it works quite well, although more reporting tools are definitely needed. The alpha status of CouchDb, the database software powering Ajatus has bit us a few times by database corruption (caused by OSX-specific erlang bug) or simply difficult installation procedure, but these problems will hopefully improve over time.
We're now in the second week of this model, and at least the gut feel is that this has improved coordination inside the company. The next challenge then is to let the customer get involved in the process. This can mean just sharing the project status files, or even giving them access to actual meetings or the Ajatus data.
]]>Couchdb Wiki: BreakingChanges2008-06-05T10:41:16+00:002008-06-05T10:41:16+00:00http://www.ajatus.info/midcom-permalink-dc69bd70634e11dda8eecde5b55c09880988henri.bergius@iki.fi (Henri Bergius)Google Video: Ajatus lightning talk in FOSDEM2008-03-11T21:15:25+00:002008-03-11T21:15:25+00:00http://www.ajatus.info/midcom-permalink-dba53888634e11dda8eecde5b55c09880988henri.bergius@iki.fi (Henri Bergius)Ajatus LT @ FOSDEM video2008-03-05T10:50:55+00:002008-03-05T10:50:55+00:00http://www.ajatus.info/midcom-permalink-81c1b14aeaa711dc82c027ba1ba013521352jerry.jalava@nemein.com (Jerry Jalava)the video is now available to be downloaded.
]]>Ajatus LightingTalk in AOP2008-03-03T19:23:01+00:002008-03-03T19:23:01+00:00http://www.ajatus.info/midcom-permalink-3bd6297ce95811dcbb5e4da3c52186fa86fajerry.jalava@nemein.com (Jerry Jalava)FOSS event "Avoimien Ohjelmien Päivä" in Turku, Finland.
I will be holding a LightningTalk of Ajatus there somewhere after 3pm.
If you are coming there, let's go for a beer etc. and discuss the topic or offtopic...]]>FOSS event "Avoimien Ohjelmien Päivä" in Turku, Finland.
I will be holding a LightningTalk of Ajatus there somewhere after 3pm.
If you are coming there, let's go for a beer etc. and discuss the topic or offtopic...]]>XMPP publish/subscribe for Midgard and Ajatus replication2008-02-24T14:33:46+00:002008-02-24T14:33:46+00:00http://www.ajatus.info/midcom-permalink-c3154774e2f511dcb9de3716f775976e976ehenri.bergius@iki.fi (Henri Bergius)On the side of FOSDEM we went today to the XMPP devcon held here in Brussels. In there we started formulating our ideas of XMPP publish/subscribe (XEP-0060) based replication for both Midgard and Ajatus.
This post contains very early ideas, but we would be happy to get some feedback on them.
Basic idea
Each Midgard or Ajatus server runs a "synchronization daemon" which is connected to a XMPP server using some JID identity.
The sync daemon registers a set of pub/sub nodes corresponding to the content structure on the Midgard or Ajatus instance:
in Midgard: Sitegroups, MgdSchema types, paths (possibly a regexp), approval state
/midgard_article/all, /midgard_article/approved
in Ajatus: tags
The pub/sub nodes can be set up with some access control rules. For example, Ajatus tags would by default require "whitelist" authorization to subscribe.
When content is changed, the sync daemon gets notified about it (via D-Bus signals in Midgard, and via CouchDb external indexer API in Ajatus).
The content object (and immediate children like parameters and file attachments) is serialized into the syndication format and sent onward as a XMPP "pub" leaf. If the object appears on multiple nodes (multiple Ajatus tags for instance), the "pub" leaf is sent to all of them.
XMPP server and the federated network will then handle notifying the subscribers of the nodes about the new leaf.
The subscribers will receive the leaf, and unserialize it to the Ajatus or Midgard database.
Communication between sync daemon and application
The sync daemon should exist as an entity separate from the actual user application. Communication between the sync daemon and Midgard or Ajatus should happen via the application database.
This means that XMPP pub/sub whitelists for Ajatus tags would be maintained in the ajatus_db (non-replicated) database, and the sync daemon would read them from there. The Jabber server credentials would also be stored in the same database.
Information about resources from jabber buddies
User's replication partners are stored as local contacts in the application database. In Ajatus this means "Contacts" and in Midgard "midgard_person" objects. Both storage models have optional JID field.
If JID is marked for a contact, the sync daemon should at startup (or at an interval) try to discover if the contact has pub/sub resources available.
Content transformation in replication stage
While mainly intended for Midgard-to-Midgard and Ajatus-to-Ajatus replication, the same mechanisms could work across different systems.
For this, the sync daemon on the subscribing end should support XSLT transformations before content is unserialized into the system. The XSLT transformation templates should be configurable per subscription.
Hermod / Hermóðr (Midgard replication)
"in Norse mythology, messenger of the gods. He was a son of the principal god, Odin, and his wife, Frigg. Known as Hermod the Swift, he was called upon by the other gods when they had a task requiring speed and urgency." - Encyclopedia Britannica
Written in Python
Using twisted framework or x60br XMPP library
using standard Midgard MgdSchema object serialize/unserialize methods
How to proof-of-concept before D-Bus? Some watcher in MidCOM? (watcher touches spool file)
PillowTalk (Ajatus and CouchDb replication)
Written on Erlang
Extendable through plugins
Content parsers (Midgard2Ajatus, Ajatus2Midgard)
Security
CDATA JSON block or convert to XML? (Decision of the content parser?)
This post contains very early ideas, but we would be happy to get some feedback on them.
Basic idea
Each Midgard or Ajatus server runs a "synchronization daemon" which is connected to a XMPP server using some JID identity.
The sync daemon registers a set of pub/sub nodes corresponding to the content structure on the Midgard or Ajatus instance:
in Midgard: Sitegroups, MgdSchema types, paths (possibly a regexp), approval state
/midgard_article/all, /midgard_article/approved
in Ajatus: tags
The pub/sub nodes can be set up with some access control rules. For example, Ajatus tags would by default require "whitelist" authorization to subscribe.
When content is changed, the sync daemon gets notified about it (via D-Bus signals in Midgard, and via CouchDb external indexer API in Ajatus).
The content object (and immediate children like parameters and file attachments) is serialized into the syndication format and sent onward as a XMPP "pub" leaf. If the object appears on multiple nodes (multiple Ajatus tags for instance), the "pub" leaf is sent to all of them.
XMPP server and the federated network will then handle notifying the subscribers of the nodes about the new leaf.
The subscribers will receive the leaf, and unserialize it to the Ajatus or Midgard database.
Communication between sync daemon and application
The sync daemon should exist as an entity separate from the actual user application. Communication between the sync daemon and Midgard or Ajatus should happen via the application database.
This means that XMPP pub/sub whitelists for Ajatus tags would be maintained in the ajatus_db (non-replicated) database, and the sync daemon would read them from there. The Jabber server credentials would also be stored in the same database.
Information about resources from jabber buddies
User's replication partners are stored as local contacts in the application database. In Ajatus this means "Contacts" and in Midgard "midgard_person" objects. Both storage models have optional JID field.
If JID is marked for a contact, the sync daemon should at startup (or at an interval) try to discover if the contact has pub/sub resources available.
Content transformation in replication stage
While mainly intended for Midgard-to-Midgard and Ajatus-to-Ajatus replication, the same mechanisms could work across different systems.
For this, the sync daemon on the subscribing end should support XSLT transformations before content is unserialized into the system. The XSLT transformation templates should be configurable per subscription.
Hermod / Hermóðr (Midgard replication)
"in Norse mythology, messenger of the gods. He was a son of the principal god, Odin, and his wife, Frigg. Known as Hermod the Swift, he was called upon by the other gods when they had a task requiring speed and urgency." - Encyclopedia Britannica
Written in Python
Using twisted framework or x60br XMPP library
using standard Midgard MgdSchema object serialize/unserialize methods
How to proof-of-concept before D-Bus? Some watcher in MidCOM? (watcher touches spool file)
PillowTalk (Ajatus and CouchDb replication)
Written on Erlang
Extendable through plugins
Content parsers (Midgard2Ajatus, Ajatus2Midgard)
Security
CDATA JSON block or convert to XML? (Decision of the content parser?)
]]>Offline web applications: a technology trend of 20082008-02-20T18:33:41+00:002008-02-20T18:33:41+00:00http://www.ajatus.info/midcom-permalink-44102bbedfea11dcb8eb6d077b2397c197c1henri.bergius@iki.fi (Henri Bergius)
MIT Technology Review's 10 Emerging Technologies of 2008 report includes offline web applications as a rising trend. When developing Ajatus, our new P2P personal CRM the offline issue was often in our minds. We even wrote in the manifesto:
Ideas may come to you when you're sitting in a bus, boarding an airplane or visiting a hospital. For a CRM to work the data must be available and editable in any situation.
Having now dogfooded Ajatus for almost two months, I have to say this has been an important aspect. It is powerful to have all your customer and project data with you at all times, and still be able to use it via the familiar web UI.
Offline is useful. You can write your notes in every meeting, update them in train, report expenses as they incur. And most importantly, as long as your computer is running, the application is never down. And still, though replication your data will be safe with your peers or the corporate server.
Ideas may come to you when you're sitting in a bus, boarding an airplane or visiting a hospital. For a CRM to work the data must be available and editable in any situation.
Having now dogfooded Ajatus for almost two months, I have to say this has been an important aspect. It is powerful to have all your customer and project data with you at all times, and still be able to use it via the familiar web UI.
Offline is useful. You can write your notes in every meeting, update them in train, report expenses as they incur. And most importantly, as long as your computer is running, the application is never down. And still, though replication your data will be safe with your peers or the corporate server.
]]>Conferences this spring2008-02-16T21:46:37+00:002008-02-16T21:46:37+00:00http://www.ajatus.info/midcom-permalink-ba0ec320dcde11dcbe815b495f0b09b009b0henri.bergius@iki.fi (Henri Bergius)
While last autumn was more quiet, this spring seems to have a number of events that I'm going to:
]]>Ajatus Lightning talk @ FOSDEM2008-02-08T21:14:01+00:002008-02-08T21:14:01+00:00http://www.ajatus.info/midcom-permalink-0d96f9acd68d11dcba42f38ea52c8f898f89jerry.jalava@nemein.com (Jerry Jalava)
Ajatus LT was accepted to this years FOSDEM in Belgium.
At this point it seems the presentation will be on Sunday 24 at 15:40.
I'll be introducing Ajatus itself and little bit about the pieces it is built on (CouchDB, jQuery).
Mostly I try to concentrate the presentation for developers interested either in offline AJAX development or even Ajatus itself.
I will be showing and explaining some of the layers inside Ajatus, different ways to expand it with plugins, etc and give sneak peak to the future of the app.
Some basic replication scenarios will be covered also.
At the same weekend Bergie and I will be attending the XMPP Devcon to collect and present our ideas of the automated XMPP based CouchDB replication currently going under name PillowTalk.
]]>
Ajatus LT was accepted to this years FOSDEM in Belgium.
At this point it seems the presentation will be on Sunday 24 at 15:40.
I'll be introducing Ajatus itself and little bit about the pieces it is built on (CouchDB, jQuery).
Mostly I try to concentrate the presentation for developers interested either in offline AJAX development or even Ajatus itself.
I will be showing and explaining some of the layers inside Ajatus, different ways to expand it with plugins, etc and give sneak peak to the future of the app.
Some basic replication scenarios will be covered also.
At the same weekend Bergie and I will be attending the XMPP Devcon to collect and present our ideas of the automated XMPP based CouchDB replication currently going under name PillowTalk.
]]>Ajatus 0.6.0 released2008-01-30T18:04:31+00:002008-01-30T18:04:31+00:00http://www.ajatus.info/midcom-permalink-6758a892cf6111dc890f011dd4922be62be6jerry.jalava@nemein.com (Jerry Jalava)
Finally got the new release out.
This fixes some bugs and adds cool new features.
There might be some dependencies which have to be manually installed. (Will be fixed later)
Currently the CouchDb installs itself to /usr and the databases are located at /usr/var/lib/couchdb.
I changed the DB path in /usr/etc/couchdb/couch.ini to point to my other memorycard (/media/mmc2/couchdb_db) which had some more space left.
Hopefully I get to release these as soon as possible for easier use.
Great thanks to the folks at #couchdb channel (nslater, jan,...)
And to Piotras
]]>
Today I got the complete stack working on my N800 device!
Erlang
ICU
CouchDB
Ajatus
They are far from perfect yet but I'm sure it'll get better little by little.
Currently I'm
preparing the packages for releasing them through maemo extras repository.
trying to compile the latest erlang R12.b.0 (now the package is R11.b.1)
adding dependencies to couchdb package
packaging Ajatus also
After first releases there are some possible tweaking to do... I still get some Segfaults at some points while using couchdb.
There might be some dependencies which have to be manually installed. (Will be fixed later)
Currently the CouchDb installs itself to /usr and the databases are located at /usr/var/lib/couchdb.
I changed the DB path in /usr/etc/couchdb/couch.ini to point to my other memorycard (/media/mmc2/couchdb_db) which had some more space left.
Hopefully I get to release these as soon as possible for easier use.
Great thanks to the folks at #couchdb channel (nslater, jan,...)
And to Piotras
]]>First set of Erlang packages for Maemo2008-01-23T06:48:56+00:002008-01-23T06:48:56+00:00http://www.ajatus.info/midcom-permalink-0469d09ec98511dc9e14a388e61ae873e873jerry.jalava@nemein.com (Jerry Jalava)
Last night I finally was able to do successful packages and installation on my N800.
I'll upload rest of the deps as I get to the office. Also I'm currently buildin ICU which is also needed by CouchDB. Hopefully today I have working native Ajatus on my N800.
UPDATE:
Just uploaded rest of the package files. Also there is packages for ICU.
I'm currently trying to get CouchDB to work, but still have some minor problems with it.
For basic usage of erlang one could only install the erlang-base and erlang-nox packages...
]]>
Last night I finally was able to do successful packages and installation on my N800.
I'll upload rest of the deps as I get to the office. Also I'm currently buildin ICU which is also needed by CouchDB. Hopefully today I have working native Ajatus on my N800.
UPDATE:
Just uploaded rest of the package files. Also there is packages for ICU.
I'm currently trying to get CouchDB to work, but still have some minor problems with it.
For basic usage of erlang one could only install the erlang-base and erlang-nox packages...
]]>Packaging Erlang for maemo2008-01-20T23:16:36+00:002008-01-20T23:16:36+00:00http://www.ajatus.info/midcom-permalink-a373896ec7af11dc9d04bfe5c5d276d976d9jerry.jalava@nemein.com (Jerry Jalava)
I was able to package Erlang for X86 target but collided with some segfaults on Armel. It seems the problem is the qemu and after a while trying to patch it I gave up for tonight. Have to continue tomorrow night.
Anyhow we aren't that far of getting CouchDB and Ajatus to work natively on Nokia n800/n810...
]]>
I was able to package Erlang for X86 target but collided with some segfaults on Armel. It seems the problem is the qemu and after a while trying to patch it I gave up for tonight. Have to continue tomorrow night.
Anyhow we aren't that far of getting CouchDB and Ajatus to work natively on Nokia n800/n810...
]]>I shouldn't browse the web2008-01-16T09:06:23+00:002008-01-16T09:06:23+00:00http://www.ajatus.info/midcom-permalink-a251e032c41511dcb4b4e51551b524382438jerry.jalava@nemein.com (Jerry Jalava)
Few nights ago while I was searching for Erlang resources in the big web I came across interesting project HaXe.
After few hours of reading I was sold. I started testing with different options and had an idea for a project... CouchBrowser.
CouchBrowser is cross platform CouchDB administrating utility which runs as standalone app. User interface is built with flex for sleek looks. Backend is written with haXe and ActionScript.
So currently I'm building CouchDb library for haXe similar to my other project jqCouch.
Planned features for the CouchBrowser are atleast the same functionality as the couch's own browser based utility plus some export/import features.
I'll put up some project site for this as it matures a bit and I get more time to work with it.
Here is a screenshot of the app (v0.0.1)
]]>
Few nights ago while I was searching for Erlang resources in the big web I came across interesting project HaXe.
After few hours of reading I was sold. I started testing with different options and had an idea for a project... CouchBrowser.
CouchBrowser is cross platform CouchDB administrating utility which runs as standalone app. User interface is built with flex for sleek looks. Backend is written with haXe and ActionScript.
So currently I'm building CouchDb library for haXe similar to my other project jqCouch.
Planned features for the CouchBrowser are atleast the same functionality as the couch's own browser based utility plus some export/import features.
I'll put up some project site for this as it matures a bit and I get more time to work with it.
Here is a screenshot of the app (v0.0.1)
]]>Bug fix release of Ajatus beta2008-01-04T06:53:46+00:002008-01-04T06:53:46+00:00http://www.ajatus.info/midcom-permalink-e140f946ba9611dca6600b1e5736964a964ajerry.jalava@nemein.com (Jerry Jalava)I encourage all users to update.
More info found from release notes ]]>I encourage all users to update.
More info found from release notes ]]>http://www.ajatus.info/download/0_5_1/2008-01-04T06:52:43+00:002008-01-04T06:52:43+00:00http://www.ajatus.info/midcom-permalink-e070747eba9611dca6600b1e5736964a964awebmaster@www.ajatus.info ()
http://www.ajatus.info/download/0_5_1/
]]>Tomorrow I'll upload a new release. This is a bug fix release and encourage everyone to update.2008-01-03T22:40:10+00:002008-01-03T22:40:10+00:00http://www.ajatus.info/midcom-permalink-d59a790cba5311dcb3f86f1f56fa611a611awebmaster@www.ajatus.info ()
Tomorrow I'll upload a new release. This is a bug fix release and encourage everyone to update.
]]>Auto save has countdown. (Will start after 70% has passed of the defined auto save interval). Countdown will appear above the form title2008-01-03T22:39:52+00:002008-01-03T22:39:52+00:00http://www.ajatus.info/midcom-permalink-d57a844eba5311dcb3f86f1f56fa611a611awebmaster@www.ajatus.info ()
Auto save has countdown. (Will start after 70% has passed of the defined auto save interval). Countdown will appear above the form title
]]>Saving document now checks if something has really changed before updating it to the database.2008-01-03T22:38:34+00:002008-01-03T22:38:34+00:00http://www.ajatus.info/midcom-permalink-d555c53cba5311dcb3f86f1f56fa611a611awebmaster@www.ajatus.info ()
Saving document now checks if something has really changed before updating it to the database.
