Package questions

Greetings,

I have two questions regarding packages in D6:

- The class Aspect (used via Gdiplus) is packaged in Development system
thus breaking my nicely automated build by popping up the "strip dev
system before deploying" reminder.
- The package comment of Dolphin MVP Deprecated seems to allow removal,
yet STS requires it.

Have a lovely evening,
s.

"Stefan Schmiedl" <[hidden email]> wrote in message
news:[hidden email]...
> Greetings,
>
> I have two questions regarding packages in D6:
>
> - The class Aspect (used via Gdiplus) is packaged in Development system
> thus breaking my nicely automated build by popping up the "strip dev
> system before deploying" reminder.

The Gdiplus Image View package (rather than the base Gdiplus package itself)
does have a dependency on the Development System packaged because it has a
published aspects method. Ideally this (and other dev stuff such as
examples, etc) should be separated out into a separate "Gdiplus Development"
package, but in fact the warning can be ignored in this case because the
offending method is categorised in the 'must strip' category, and so will be
removed during early on in the stripping process, breaking the dependency.

Actually I'm surprised you get the warning, because as a comment in the
image stripper states "['must strip'] methods must be stripped BEFORE
redundant packages, as they may cause pre-requisites we don't want in the
deployed application". Since the warning is not displayed until after such
methods have been removed, there should be no warning. Certainly I can
deploy the Gdiplus Image View sample without getting a warning. Are you sure
you haven't created this dependency yourself?

> - The package comment of Dolphin MVP Deprecated seems to allow removal,
> yet STS requires it.

Well the package comment does say that you can remove it if you don't have
any dependencies on it :-)

Seriously though, there was no time before the release to convert the list
views in the STS tools over from the old style multi-select lists.

Regards

Blair

Hi Blair,

On Fri, 06 Jan 2006 07:38:57 +0000, Blair McGlashan wrote:

>
> Actually I'm surprised you get the warning, because as a
> comment in the image stripper states "['must strip'] methods
> must be stripped BEFORE redundant packages, as they may cause
> pre-requisites we don't want in the deployed application".
> Since the warning is not displayed until after such methods
> have been removed, there should be no warning. Certainly I can
> deploy the Gdiplus Image View sample without getting a warning.
> Are you sure you haven't created this dependency yourself?

the warning appeared after adding Gdiplus views to the
application. I'll try filing the package into a pristine image
and see what happens tomorrow. Is there a way for me to find out
by which "path" the dependency is created?

>
>> - The package comment of Dolphin MVP Deprecated seems to allow removal,
>> yet STS requires it.
>
> Well the package comment does say that you can remove it if you don't have
> any dependencies on it :-)

That was my first thought, too :-)

Thanks,
s.

Hi Blair,

On Fri, 06 Jan 2006 20:54:15 +0100, Stefan Schmiedl wrote:

actually, that's one of those embarassing questions, as I already had seen
the answer in the PackageBrowser the day before ...

soo... I have a Presenter subclass MyPresenter with

MyPresenter>>createComponents
        super createComponents.
        image := self add: ImagePresenter new name: 'image'

and the culprit seems to be:

MyPresenter>>model: aModel
        super model: aModel.
        image model: (GdiplusImage fromFile: (FileLocator imageRelative
        localFileSpecFor: aModel))

because it references the global GdiplusImage which belongs to Gdiplus (base).

As I see GdiplusImageViewSampleShell does not set a model for the
ImagePresenter like I do, but ... uses GdiplusImage in the
initialize method! So it references the same global as I do ...

Comparing the methods remaining in the executables, my package requires
15 methods, 12 of which are the same as in the Gdiplus sample, the
additional three are: drawOn:, drawOn:at: and filename

Why does Lagoon complain about my package?

Curious,
s.