Talk:DOM load and save flow: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m →Creating a default I/O plug-in: folded in asnwer |
||
| Line 2: | Line 2: | ||
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) | :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) | ||
Done. [[User:Elf|Elf]] 11:57, 27 March 2007 (PDT) | |||
Latest revision as of 18:57, 27 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)
Done. Elf 11:57, 27 March 2007 (PDT)