can_suspend_to_{x}

[Richard Hughes]

On 06/05/06, Holger Macht <hmacht at suse.de> wrote:
> I don't think that they should be called Hibernate() and Suspend() in Hal
> at all. The first time I looked at gpm and hal, I was completely impartial
> in respect to any other OS, and thus, I had absolutely no idea what
> Hibernate or Suspend does. I had to look up the code to get what
> hibernating does.

It's in the yelp file in the introduction.

> I really don't care about what the GUI shows to the user
> in the end, that's up to the project/desktop to decide, it's a plain
> useability issue. The Hal methods should exactly describe what they
> actually do in a technical manner. So for me, it would also be ok to call
> the HAL methods ACPISleep_S3/S4 or the like. But not Hibernate/Suspend. A
> developer which writes a application which uses these methods knows the
> technical meaning of suspend to disk, but he may not know what hibernating
> does. The frontend can show whatever it likes.

No, as HAL has to provide an architecture neutral interface that can
be used by users and developers.

> >
> > I figure getting the same names so it all makes sense when we document
> > it, is worth the short term pain of breaking (undocumented?) API.
> >
> > What do you think?
>
> In a technical discussion, I don't like Hibernate/Suspend for suspend to
> disk/ram at all, because these are suitable inventions for the desktop
> user, but not for a developer.

But I don't see why we should use different names just because one
project is "for developers" and one is "for users".

Richard.