[Valentina] Re: Vdb files

[Ruslan Zasukhin]

on 1/20/03 6:01 PM, Robert Brenstein at rjb at rz.uni-potsdam.de wrote:

>> Reason is next:
> 
> sorry, but none of the reasons convince me:
> 
>> -- "set of extension" is property of *application*.
> 
> yes
> 
>> -- when you on windows build app, you assign it to extensions it must
>> recognize. Even more, on windows, we inform OpenDialog() about extensions we
>> want to filter.
> 
> exactly! The extensions are in our code, so we know what they are.
> 
>> -- so this is not correct by OO design put on Open() extensions.
> 
> but this is same as providing name with extension built in -- they
> are just split for clarity.

I think not the same.

Now we have kind of:

    App.SetExtensions()

You suggest put it on db level:

    db.Open( name, ext )

>> -- If we do this, it sounds like Open() must be able open ANY DB with ANY
>> extension. But this is not true. Application must be able open only .vdb
> 
> but we can specify custom extensions now. how is that different?

On different levels of logic.

-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://listserv.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------