IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 1 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Is this true about OSX?
This was on the Lyx user list.

On 17.04.2009, at 15:25, Niko Schwarz wrote:


On Fri, Apr 17, 2009 at 8:53 AM, Rainer M Krug <r.m.krug@gmail.com> wrote:


1) I like the lyx format as it is BECAUSE it is not compressed, so I
would definitely not change the default format.


Ok, maybe I didn't make myself clear: you can have self-contained archives
with no compression at all on OSX. It works like this: you make a directory
and in that directory you dump a special file that tells finder to display
the directory as a package.

But from the command line, it is still a directory. And in finder, you can
look into the package by choosing "Show Package Contents" from the pop up
menu.

Now Pages files for example come as such "packages", you can copy that
directory around, send it through email (yea, email clients handle it
surprisingly well), and it still works.

Now, other operating systems see a directory and not a package. People using
something other than OSX would have to be reminded to copy the directory
around the .lyx file around, which would be managed by lyx.

The file would still be accessible, no performance penalty, but complete
send-aroundability, and while it might feel a little alien on other OS's, on
OSX it's the standard way to do such things, so OSX users will cheer.


No, they won't.

The thing is that OSX -- or at least the OSX applications that use this concept,
with Pages being a good (well, bad) example -- do *not* treat packages as true
directories, but as a "personal container". Whenever you save a Pages document, for
instance, Pages deletes everything in the "directory" that was not created by
itself. This can be quite surprising! Pages might also decide to rename its files
in the directory. And so on.


All tools that need to manage side-by-side metadata in directories (such as CVS and
SVN) are inherently unusable with OSX apps that use the package format. You just
cannot put a Keynote presentation into an svn repository...


Packages are one of those OSX standards that are conceptually nice, but
unfortunately seriously broken in the actual implementation.


I'd like to get a MacBook at some point. I'd definitely like to know before I try it that CVS of SVN won't work as expected.
--

Drew
New I've never had that issue.
Of course, for the most part I don't try to put things other than text files in my SVN repositories.

This is the first I've heard of documents saved as packages; I've only seen applications saved that way. It's a great format for apps because you just have to copy the directory to install the app.

Many OS X apps don't have installers, per se: just a Finder dialog with a pointer to the app package and a soft link to /Applications. You drag the app icon to the Applications folder, and that's the whole installation.
Regards,
-scott
Welcome to Rivendell, Mr. Anderson.
New iWork documents are packages.
ETA: Oh, yes. I see now that Pages is mentioned.

Hmm.

I'm undecided on whether this is actual breakage or not; I've come to notice (especially from using things like VMS) is the UNIX mantras of "everything's a file" and "everything's plain text" are a bit simple for the real world.

I'm unclear, though, on the benefits of structuring documents in this way. Surely if there's lots of metadata and wotnot to maintain, some kind of container file à la OpenOffice.org would be in order?
Expand Edited by pwhysall April 26, 2009, 01:01:37 PM EDT
New IMO it's not breakage
I wouldn't use vim to edit video files. That's not the right app for that filetype.

So if an OSX package is not something that can be handled by Subversion, I just need to know that.
--

Drew
New Idiot!
You use emacs, of course.
New No, of course I don't
--

Drew
New Seems silly to me.
Just use a file. With the meta data in it. Then you're not breaking things like svn.

I can see the benefit from the *programmer's* aspect, obviously. They don't need to worry about file formats, rejiggering things if they insert sections, etc. Just have a separate file for everything you want to keep track of. And more than likely they don't really care if someone can stick an iWork document in a source code repository.
Regards,
-scott
Welcome to Rivendell, Mr. Anderson.
New Well, quite.
Why not do all that and then zip it up? That's what oo.o does.

Weird.

ETA: I know why not. Spotlight, that's why.
Expand Edited by pwhysall April 26, 2009, 04:30:45 PM EDT
     Is this true about OSX? - (drook) - (7)
         I've never had that issue. - (malraux) - (6)
             iWork documents are packages. - (pwhysall) - (5)
                 IMO it's not breakage - (drook) - (2)
                     Idiot! - (pwhysall) - (1)
                         No, of course I don't -NT - (drook)
                 Seems silly to me. - (malraux) - (1)
                     Well, quite. - (pwhysall)

NOTE: This video shows people getting hurt falling down a hill on purpose. Viewer discretion advised.
325 ms