學習,使用,開發工作流程引擎這麼長時間了,AgileFlow也開發到了0.8版,但在這整個期間,一直
沒有發現一個讓我感覺興奮的引擎;怎麼樣合理的定位工作流程引擎的邊界,合理的設計它提供
給外界的介面,怎麼樣合理的讓使用者進行非編譯方式的擴充,一直困擾著我;我試圖在AgileFlow
中給出答案,但給的算不上好,很多問題我是知道的,但就是找不到辦法.這兩天學習osworkflow,終於找到了那種很high的感覺!
osworkflow基本上解決了我以前考慮的98%的問題,而且在很多方面和我的思路是一樣的;它在
保證代碼最簡單邏輯最清晰的條件下,給出了最強的功能,而且這種功能是不需要對使用者有什麼
強制性的限制的.下面是它的說明:
OSWorkflow can be considered a "low level" workflow implementation.
Situations like "loops" and "conditions" that might be represented by a graphical
icon in other workflow systems must be "coded" in OSWorkflow.
That's not to say that actual code is needed to implement situations like this,
but a scripting language must be employed to specify these conditions.
It is not expected that a non-technical user modify workflow.
We've found that although some systems provide GUIs that allow for
simple editing of workflows, the applications surrounding the workflow
usually end up damaged when changes like these are made.
We believe it is best for these changes to be made by a developer who
is aware of each change. Having said that, the latest version provides
a GUI designer that can help with the editing of the workflow.osworkflow對工作流程引擎應該做什麼,不應該做什麼,應該達到什麼目標,和我的思路完全
一致.興奮,今天算是找到了知己.
