[fpc-devel] Rather large flaw in TJSONConfig component

[Graeme Geldenhuys]

Op 2010-06-21 16:33, Michael Van Canneyt het geskryf:
> 
> The best way to avoid it is to create/destroy the config object after use.
> When the form is opened, you create an ini/json/whatever file object and

So then it's not wise to have TXMLConfig in the Lazarus component palette.
Because dropping a component on a form doesn't give the behaviour you
described.


> Likewise for a database application. Unless you take care of transaction
> support, 2 users editing a record will overwrite each other's changes,
> unless the programmer explicitly takes care of this.

Doesn't Delphi's TClientDataset popup a 'conflict resolution dialog' in
such a cases. I remember seeing such dialogs years ago (when I still used
Delphi).


> In 12 years that our apps run, we used the system 'last writer wins' and 
> no single user has complained yet about this.

Because they don't get notified about their data (last saved) being lost. :-)


Michael, how does documentation work in FCL? Can we start documentation on
these units and include these usage warnings - then not let them appear in
official documentation until the FCL-json or FCL-xml packages are 100%
documented? I know FPC has the policy that it doesn't allow "partial"
documentation. I just fear that not documenting it now (somewhere) - this
information will be forgotten when the docs are eventually written.

Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://opensoft.homeip.net/fpgui/