|
|
|
Forum Member
 
Group: Forum Members
Last Login: 2010-01-06 19:34:12
Posts: 36,
Visits: 549
|
|
How do I access the "ProcessDefinition" screen as shown in the latest blog post "Knowing nothing, where to being"? Where is the documentation on this?
Mitch
|
|
|
|
|
Supreme Being
Group: Administrators
Last Login: Today @ 12:35:33
Posts: 155,
Visits: 1 941
|
|
| The Process-Definition feature is available in the later builds. We will soon promote one of the daily builds to a new released version. Until then you can access the dailybuilds here http://dl.capableobjects.com/dl/dailybuilds/ Once you have such a build you will see a "Processes" node in the modlr tree, right-click and choose New Process. It should all be pretty straight forward once you have a correct build.
|
|
|
|
|
Supreme Being
Group: Forum Members
Last Login: Today @ 05:16:23
Posts: 454,
Visits: 1 036
|
|
What do you DO with this "processes" nodes? Is it just documentation of the steps? Or is it more than that somehow? Does it tie to code somehow? Is there any documentation on this stuff that I haven't found yet?
/mtiede
Environment:
Windows 7 Ultimate 64 bit
Delphi 6
Rad Studio 2010 Enterprise with Prism 2011
|
|
|
|
|
Supreme Being
Group: Administrators
Last Login: Today @ 12:35:33
Posts: 155,
Visits: 1 941
|
|
|
|
|
|
Supreme Being
Group: Forum Members
Last Login: Today @ 05:16:23
Posts: 454,
Visits: 1 036
|
|
After looking at your write-up (again), I realized that I can't make a step under a step. I can only delete the step that is right-clicked. Is this fixed in one of your "daily builds"?
Are these daily builds to be looked at as "beta"s? Or is it safe to use them?
/mtiede
Environment:
Windows 7 Ultimate 64 bit
Delphi 6
Rad Studio 2010 Enterprise with Prism 2011
|
|
|
|
|
Supreme Being
Group: Administrators
Last Login: 2010-07-21 00:21:24
Posts: 1 228,
Visits: 1 373
|
|
The daily builds are just that. They are promoted from the build machine automatically once per night (unless the buildmachine is acting up and refuses to build). The daily builds may contain regression bugs and may contain really bad checkins, but usually they don't.
When we have sufficient good stuff in the daily builds, and we feel confident enough that we didn't break anything, we move a selected build from that location to the official website.
If we fix a bug that has been reported, we often mention the subversion revision that contains the fix so you know which build to download to test the fix.
Here is a breakdown of the numbers in the eco setup filename:
EcoSetup_5.0.0.4871_2010-02-26_b1036.exe
* 5.0.0 is the major version. This number is updated manually.
* 4871 is the subversion revision that this particular build was built from. Updated automatically each time we check in anything to the subversion repository
* 2010-02-26 is the date the build was built (build server is located in GMT+1)
* b1036 is the build-number and is just an incremental number that the buildserver maintains. It doesn't really mean anything, it is just used to make sure that each build gets a unique filename even if there hasn't been any new subversion revisions since the last build. This number can be reset if we reconfigure the build server.
/Jonas Hogstrom [CapableObjects]
|
|
|
|