Talk:DOM load and save flow: Difference between revisions
Jump to navigation
Jump to search
question on Creating a default I/O plug-in |
No edit summary |
||
| Line 1: | Line 1: | ||
== Creating a default I/O plug-in == | == Creating a default I/O plug-in == | ||
This article says that load & save "create default I/O plug-in (and database) if they don't exist". Does it/can it really create an I/O plug-in, or is it really just somehow installing (?) an existing default, which I presume is libxml? [[User:Elf|Elf]] 16:44, 21 March 2007 (PDT) | This article says that load & save "create default I/O plug-in (and database) if they don't exist". Does it/can it really create an I/O plug-in, or is it really just somehow installing (?) an existing default, which I presume is libxml? [[User:Elf|Elf]] 16:44, 21 March 2007 (PDT) | ||
A better word might be "instantiates". What the code does is it creates/instantiates an object of the default IOPlugin or Database classes and uses it. [[User:Alorino|Alorino]] 17:49, 21 March 2007 (PDT) | |||
Revision as of 00:49, 22 March 2007
Creating a default I/O plug-in
This article says that load & save "create default I/O plug-in (and database) if they don't exist". Does it/can it really create an I/O plug-in, or is it really just somehow installing (?) an existing default, which I presume is libxml? Elf 16:44, 21 March 2007 (PDT)
A better word might be "instantiates". What the code does is it creates/instantiates an object of the default IOPlugin or Database classes and uses it. Alorino 17:49, 21 March 2007 (PDT)