imager or packager

I recently read somewhere online about these 2 different styles of working in
the development environment. Can someone point me to where that was?

> I recently read somewhere online about these 2 different styles of working
in
> the development environment. Can someone point me to where that was?

Searching the archives for "bonkers" should point you to the relevant
thread - seriously :)

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]

On Thu, 27 Dec 2001 06:34:18 -0500, "Bill Schwab" <[hidden email]>
wrote:

>> I recently read somewhere online about these 2 different styles of working
>in
>> the development environment. Can someone point me to where that was?
>
>Searching the archives for "bonkers" should point you to the relevant
>thread - seriously :)

Very good search word :)

So how does one be a packager in Dolphin? When I used VSE, I'd commit packages
and exit without saving. Then on re-entry I could migrate to the committed
version.

In Dolphin I save the package, exit without saving, but on re-entry there is
no equivalent to migrating. You cant install a package if its already in the
image. Deleting the package first could be too traumatic for several reasons
(dependencies, overrides to baseline, etc)

I suppose one could start with a virgin image and never save it with any
version of any new package but that seems too restrictive. Occasionally one
would want to cut an image with packages (and maybe object instances) at a
certain level and use that as a baseline for going forward.

It would be nice if there was a package migrate function. Without it, being a
packager has to be an all or nothing proposition.

Hi

In Dolphin you can use the same pattern of work as you were using in VSE
(with "Team/V" I presume). What you need is an add-on called the Source
Tracking System.

With STS, when you end your daily work, you can make a new version of your
package (commit). Later you can either load your code from the repository or
migrate a package, and even load separate classes, methods, etc.

There is also functionality to browse repository without
installing/compiling code, comparing versions in repository with each other
as well as comparing your code in the image with versioned code in
repository to find out what you've changed. Multi-user development is also
supported, and with STS it is finaly practicaly possible for two developers
to work on the same package simultaneously STS (on-site or off-site
development).

Check out the product at:

http://www.gorisek.com

Best regards,

David


"ar" <[hidden email]> wrote in message
news:+[hidden email]...
> On Thu, 27 Dec 2001 06:34:18 -0500, "Bill Schwab"
<[hidden email]>
> wrote:
>
> >> I recently read somewhere online about these 2 different styles of
working
> >in
> >> the development environment. Can someone point me to where that was?
> >
> >Searching the archives for "bonkers" should point you to the relevant
> >thread - seriously :)
>
> Very good search word :)
>
> So how does one be a packager in Dolphin? When I used VSE, I'd commit
packages
> and exit without saving. Then on re-entry I could migrate to the committed
> version.
>
> In Dolphin I save the package, exit without saving, but on re-entry there
is
> no equivalent to migrating. You cant install a package if its already in
the
> image. Deleting the package first could be too traumatic for several
reasons
> (dependencies, overrides to baseline, etc)
>
> I suppose one could start with a virgin image and never save it with any
> version of any new package but that seems too restrictive. Occasionally
one
> would want to cut an image with packages (and maybe object instances) at a
> certain level and use that as a baseline for going forward.
>
> It would be nice if there was a package migrate function. Without it,
being a
> packager has to be an all or nothing proposition.
>