Am Montag, den 14.07.2008, 21:24 +0100 schrieb Michael Meeks: > > I love how everybody cares about the users, but for this use-case > > skeletons and symlinks are definitely enough. > > So - really; do any distros actually configure a skeleton with nautilus > templates included ? how are they implemented ? with symlinks ? if so, > how does it feel never being able to move the destination files > again ? ;-) or is it the case that we ship something not that usable out > of the box on ~all distros ? :-)
I thought we agreed that this wouldn't be the distributors' job, but the administrators' job. And they should be perfectly able to add either a symlink to a global template directory with the appropriate permissions (shared templates), and/or a skeleton for new users (default user-specific templates). On the other hand, your objective seems to be to make Joe Doe use templates, which I like in principle, _but_: I do not think that we should add such seemingly complex code to Nautilus, “just” for animating users to use templates. Because those who do not know the UNIX modus operandi will ask themselves immediately “how can I modify the system templates?”. For now I'll just say “no”, although there are possibly some niche cases where this feature is useful. If it turns out that we have more similar niches, we can extend our plugin architecture: We could offer more UI hooks for the plugins, and allow users to conditionally enable/disable plugins (like in Epiphany). On top of that, everybody could compose complex grade A subsystems with bells and whistles and whatnot :). best regards, Christian Neumair -- Christian Neumair <[EMAIL PROTECTED]> -- nautilus-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/nautilus-list
