WFPad - XOML editor for Workflows

Don Box's Spoutlet

Syndication

Comments

Ian Griffiths wrote re: WFPad - XOML editor for Workflows
on 10-08-2005 2:09 AM
I had no idea your musical tastes were in that direction, but here you go:

http://www.indiepad.com/
Sami wrote re: WFPad - XOML editor for Workflows
on 10-08-2005 8:24 AM
Don,
Im totally off-topic but I'v seen that the API of Indigo CTP Sept has slighly changed since the Beta 2. Do you know where I can pick up those changes ? For example, OperationBehaviour no more contains AutoEnlist, AutoCompletion parameters, etc...
BindingRequirement attribute no more contains TransactionFlow... Classes have been renamed...
I know that Omri Gazzit has pointed out some (minor) changes...
Moreover, have the samples been adapted to reflect those changes ?
Thanx.
Sami
Javier G. Lozano wrote re: WFPad - XOML editor for Workflows
on 10-08-2005 10:39 AM
Don,

what are your ideas for IndiPad? I was thiking of creating a nice graphical tool that will let you edit your service and client endpoints in your config file.
<savas:blog /> wrote WFPad
on 10-08-2005 11:44 AM
This is very cool. If you want to learn and/or play with Windows Workflow Foundation (WF), WFPad is an excellent standalone tool. If you want VS.NET (Express) 2005 integration, you can download the extension pack (please note that the current beta 1 r...
Christopher Steen wrote Link Listing - October 9, 2005
on 10-09-2005 8:59 PM
AJAX and ASP.NET discussion list [Via: Wallym ]
ASP.NET Podcast #22 - Interveiw with Shanku Niyogi...
Javier G. Lozano wrote IndiPad: My Version
on 10-10-2005 9:54 PM
Javier G. Lozano wrote IndiPad: My Version
on 10-10-2005 9:55 PM
Michael Herman (Parallelspace) wrote Is XOML a DOA feature? ...or is WWF beta1 just a poor implmentation of this?
on 10-22-2005 9:19 AM
[potential reposting]

A key shortcoming of XOML is that it only persists a minimal amount of information about the workflow design.

A key requirement for business analysts is the visual layout of the workflow as much as the list of specific activities and their interconnections.

When a WWF workflow is serialized as a XOML stream, you only get the list of activities, their parameters and interconnections stored as XML.

All of the positioning information is thrown way unless you save it yourself. ...in which case, why does anyone need XOML if you end up having to rolling your own schema?

This is primarily true for the free form designers (e.g. State Machine Workflows).

Michael Herman
Parallelspace Corporation

Add a Comment

(required)  
(optional)
(required)  
Remember Me?