Guy Harris <gharris@xxxxxxxxx> schrieb am 03.09.02 01:54:23:
> On Tue, Sep 03, 2002 at 01:06:02AM +0200, Ulf Lamping wrote:
> > > > This would introduce a new file in the home directory maybe called
> > > > "recent".
>
> BTW, as it's specific to Ethereal, it should go into the same directory
> as the "preferences" file, not into the user's home directory on UNIX or
> their top-level profile directory on Windows.
Well, I meant exactly that ;-) Using the get_persconffile_path() function.
> > I think that the common code has really it's advantages, as this results
> > in fast development, I can implement a thing on win32, and it could run
> > on a linux platform without changes.
>
> There are both advantages and possible disadvantages - if an application
> would fit better into the {Windows, KDE, GNOME, MacOS X} desktop by
> using a native mechanism for keeping track of recent files, that might
> outweigh the disadvantages of not using common code.
>
I would see the recent file as a special case of a preferences file which is changed very often. I would also think, that the file format should be identical to that of the current preferences file (and I have started to implement it that way).
As I mentioned earlier, the recent file will not only hold the recent capture files, but also the recently used display filters and maybe other things as well in the future.
So I don't know, if this could also be done by a native mechanism.
I see, that native implementations have their advantages (common look & feel, mechanisms familiar to the user, ...) but I think the rapid development of Ethereal is mainly caused by lot's of different platform developers can write code on their machines.
If we would like to have different GUI implementations for different platforms, it would be maybe better to write the GUI code from scratch, than to change the existing things.
Again, I really would like to prevent forking of the code for different platforms in any way (where it can be prevented).
> In general, common code is good, but there are places where it's not -
> for example, we use different code on UNIX and Windows to determine the
> directory into which to store per-user configuration files (preferences,
> etc.).
>
This is a point, where seperate code MUST be used, as there must be done different things. A lot of other portability things is solved by Glib/Gtk, which I think is really a good way to handle this.
ULFL
______________________________________________________________________________
Die clevere Geldreserve: der DiBa-Privatkredit. Funktioniert wie ein Dispo,
ist aber viel günstiger! Alle Infos: http://diba.web.de/?mc=021104
