On May 21, 2008, at 12:05 PM, Christiaan Hofman wrote: > > On 21 May 2008, at 7:18 PM, Maxwell, Adam R wrote: > >> On 05/21/08 10:03, "Simon Spiegel" <[EMAIL PROTECTED]> wrote: >> >>> >>> I know that the template doesn't contain this information – yet. But >>> how about putting the template files and a plist file with the >>> needed >>> information in a package ... Doubleclick it and everything gets >>> installed as it should ... >> >> The type info is totally separate from the templates, logically and >> in the code. I don't see how you could move that with the >> templates. For >> the rest, it sounds like you want a separate document type? That >> would >> preclude easy editing of templates in TextEdit. However, if the >> template >> editor's state could be archived and saved such that they could >> always be >> reopened, maybe it could become the exclusive way to edit templates? > > Certainy not, because the template editor is still restricted. There > are lots of advanced template features not available from the editor.
Fair enough...that's possibly a significant limitation. > Apart from the fact that it won't work. The whole ida of the template > system is that it makes properties in the program available. When the > properties are called they have no idea whether they're called because > they're included in a template or not. I've no idea what this has to do with wrapping up templates in a document in order for users to share templates more easily. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
