Re: unixodbc gui split

Nick,

On Sat, Jan 16, 2016 at 5:30 AM, Nick Gorham <[email protected]> wrote:
> On 16/01/16 05:04, Igor Korot wrote:
>>
>> Hi, Peter,
>>
>> On Fri, Jan 15, 2016 at 10:32 PM, Peter Lai <[email protected]> wrote:
>>>
>>> This is the UNIX principle of KISS (keep it simple stupid). In a
>>> server environment, having the GUI part is neither necessary nor
>>> desirable. Core codebase provides the core functionality. As long as
>>> the API is documented and the hooks are present/maintained, the GUI
>>> code should be kept separate. This helps with development process
>>> workflow: why result in extra version bumps of UnixODBC every time
>>> some code in the GUI got changed? Why reduce portability/stability
>>> just to keep add-on code? I suppose an argument could be made to use
>>> Make flags to tell it whether to build the GUI or not.
>>
>> I believe you are wrong.
>
>
> Belief will always be personal, though not always correct.

Can't agree more. But not in this case.
unixODBC is a client-oriented software designed to make it easier for a client
to connect to a database thru the familiar interface. And this is
contradicting on what
Peter is saying.
I just wonder how unixODBC become a server-side software?

>>
>> unixODBC is a software for a client to make a client connect to DB server.
>>
>> Now as I said I am getting the error trying to compile the package:
>
>
> Well, if you find the fix, by all means make it available.

Is GUI part is building with every unixODBC release?

Another question: does it depend solely on unixODBC? And what version
of qt it can be built against?

Thank you.

>
>
> --
> Nick
> _______________________________________________
> unixODBC-dev mailing list
> [email protected]
> http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
_______________________________________________
unixODBC-dev mailing list
[email protected]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev