do-windows team mailing list archive

["Krisztian Gyuris" <gyurisc@xxxxxxxxx>]

Yes, let's use gtk. How do we handle these dependencies then? Shall I check
the binaries in the source code control?

On Fri, Jul 4, 2008 at 3:22 PM, Brian Pedersen <brian.pedersen@xxxxxxxxx>
wrote:

> Hehe, I was just writing something like "using what is already there to get
> up and running fast", but you got there first :)
>
> I was thinking of a three phased approach, something like:
>
> 1 -Get something up and running
> 2 - Optimize for ease of maintainability
> 3 - Optimize user experience
>
> If it speeds up the process using gtk in the first phase, lets do so.
>
> Once we have something up and running, we will be in a much better position
> to make decisions regarding which UI libraries to use on the long term.
>
> If on the other hand it is giving us a lot of problems getting it to work
> on windows with gtk, we should reconsider.
>
> In the end we would want to avoid having prerequiste installs like gtk, but
> for now I think it is best if we take one step at the time.
>
> /Brian
>
>
> 2008/7/4 Nick Parker <nickp@xxxxxxxxxxxxxxxxxx>:
>
> Krisztian/All,
>>
>> I agree that the install should be a no brainer, which is why I want to
>> start localizing all of the external library dependencies within the project
>> (I haven't seen what you have yet so maybe this is already done).  That
>> said, we can build the installer, probably using WiX to package everything
>> together so we can just require .NET 3.5 on the client machine (launch
>> condition), everything else will be in the .msi.
>>
>> As David mentioned previously, there are gtk+ libs for Windows.  From a
>> "get this thing going" perspective, I think it might be in our best interest
>> to use as many libraries as are available to get the main application
>> running on Windows.  From the point where it runs on Windows we know there
>> will be refactoring even from an OS platform that we want to look into, but
>> I would suggest we do this in stages and simply get the application running
>> first.
>>
>> Nick Parker
>> www.developernotes.com
>>
>> On Fri, Jul 4, 2008 at 2:31 AM, Krisztian Gyuris <gyurisc@xxxxxxxxx>
>> wrote:
>>
>>> One important area to focus on is that the install should be a no brainer
>>> for the end user. I would not really like to use something, where I need to
>>> hunt and install extra things onto my computer.
>>> This should be totally seamless...
>>>
>>> Krisztian
>>>
>>> On Fri, Jul 4, 2008 at 9:11 AM, Brian Pedersen <brian.pedersen@xxxxxxxxx>
>>> wrote:
>>>
>>>> Hi Krisztian
>>>>
>>>> Now is definately a good time for this discussion, I will try to put my
>>>> input on this into writing this evening and hopefully we can get a good
>>>> discussion going and find an approach which will cover our needs at least to
>>>> begin with, while we are moving towards a compilable state.
>>>>
>>>> I believe platform dependency and cross platform development are broad
>>>> covering terms, which we will need to split up into more specific areas, it
>>>> could however be we could start out focusing on only some of those areas, in
>>>> order to keep moving.
>>>>
>>>> /Brian
>>>>
>>>>
>>>>
>>>> 2008/7/4 Krisztian Gyuris <gyurisc@xxxxxxxxxxxxxxxxxxxxx>:
>>>>
>>>>>  All,
>>>>>
>>>>> I would like to discuss what approach to take with the dependencies of
>>>>> Do (widgets, mono specific classes).
>>>>>
>>>>> - Ignore them all
>>>>> - Try to refactor the code into thin layer and make it pluggable
>>>>> - Take windows only approach - meaning that we will only use what is
>>>>> available on windows
>>>>> - Take mono only approach - meaning that we will only use what is
>>>>> already in the code.
>>>>>
>>>>> It would be nice to hear your thoughts on this and the pros and cons of
>>>>> each approach.
>>>>>
>>>>> Krisztian
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~do-windows
>>>>> Post to     : do-windows@xxxxxxxxxxxxxxxxxxx
>>>>> Unsubscribe : https://launchpad.net/~do-windows
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~do-windows
>>> Post to     : do-windows@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~do-windows
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~do-windows
>> Post to     : do-windows@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~do-windows
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>