[openbeosstorage] Re: ISO9660/cdrom progress
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: openbeosstorage@xxxxxxxxxxxxx
- Date: Tue, 25 Feb 2003 20:34:08 +0100 CET
"Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx> wrote:
> > I don't know of any other applications than the famous cd-record
> > which
> > is also available for BeOS - but of course, this has never
> > interested
> > me much, as I rarely use other operating systems, if possible ;)
> > Has anyone tried to burn a multi-session disk using it=3D3D3F
> AFAIK cdrecord can burn CDs with multiple sessions, but I don't think
> it has any idea of ISO9660. It burns what it is been given, as track
> or
> session or whatever is correct.
Exactly, then take mkisofs/mkhybrid as the only application I know to
create those images and look what it does :-)
> > Oh, it's really not hard to *not* use a layout manager, but if you
> > really have to :-)
> Do I hear a volunteer desiring to take over=3D3F ;-)
Hehe, I highly doubt that ;-))
> Seriously, I hate calculating sizes for GUI elements. Even worse, as
> soon as you want to support resizing and have something as `complex'
> as
> two similarly sized boxes in a row or column, you have to recalculate
> manually. Finally you end up with a layout management for each of
> your
> grouping views.
Yes, that's true. But it's still not complicated, but in fact it was
one thing I hated about the gadtools.library as well.
> When switching from AmigaOS to BeOS, I was surprised how inferior the
> Interface Kit of this shiny new OS was compared with MUI.
Oh yes, me too! MUI is really nice. BTW also OpenStep has very inferior
(no) layout classes, I dunno about MacOS X, though.
Adios...
Axel.
- Follow-Ups:
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Ingo Weinhold
- References:
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Ingo Weinhold
Other related posts:
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Ingo Weinhold
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Ingo Weinhold