Re: [wxhaskell-users] splitterWindow
On Mon, 2 Apr 2012, Jeremy O'Donoghue wrote: This is a very good idea, but I was thinking of doing almost exactly the opposite: before I apply the changes to the main repo, I was planning to create a wxHaskell-0.13 (wxWidgets 2.8.x) branch on code.haskell.org, probably by creating wxdirect-0.13, wxcore-0.13 and wx-0.13 branches as separate directories. The other option would be to move 0.13 support to Darcsden. For the repositories of my projects I tend to use one repository per Cabal package, because I use darcs tags for tagging versions that I uploaded to Hackage and the versions, especially the minor versions, of the packages of one project are not always in sync. Translated to wxhaskell this means, current wxcore might have version 0.13.2.1 whereas wx might have version 0.13.3.7. I think it makes sense to have a 'central' repo for changes. It is easy for private repositories to be lost over time. Does this work for you? This would be perfect. What is the advantage of darcsden compared to code.haskell.org? Currently I am very happy with code.haskell.org. Best, Henning -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure___ wxhaskell-users mailing list wxhaskell-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
Re: [wxhaskell-users] splitterWindow
On 30 March 2012 08:42, Henning Thielemann wrote: > > On Tue, 27 Mar 2012, Henning Thielemann wrote: > > > I want to use a splitterWindow. For instance I wanted to change the > 'gravity' > > because the default value is not appropriate for my application. > > Unfortunately there is no splitterWindowSetSashGravity function. > > I have added splitterWindowSetSashGravity to WxcClassesMZ of my working > copy of wxcore. I have also some other small additions like 'selection' > attribute for notebooks. Since not everybody wants to move to the new > wxwidgets immediately, how about updating wx-0.13 with small additions for > a while? I could simply apply the patches myself and upload new wxhaskell > packages to Hackage myself if the main maintainers want to concentrate on > new wx versions. > This is a very good idea, but I was thinking of doing almost exactly the opposite: before I apply the changes to the main repo, I was planning to create a wxHaskell-0.13 (wxWidgets 2.8.x) branch on code.haskell.org, probably by creating wxdirect-0.13, wxcore-0.13 and wx-0.13 branches as separate directories. The other option would be to move 0.13 support to Darcsden. I think it makes sense to have a 'central' repo for changes. It is easy for private repositories to be lost over time. Does this work for you? Regards Jeremy -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure___ wxhaskell-users mailing list wxhaskell-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
