From: jerome <rom...@ya...> - 2012-12-16 14:43:21
|
Note, maybe you forgot to say if it is Windows 8, Pro or Windows RT? 32 or 64 bit? --- En date de : Dim 16.12.12, Enno Borgsteede <enn...@gm...> a écrit : > De: Enno Borgsteede <enn...@gm...> > Objet: Re: [Gramps-devel] Windows 8 development > À: "jerome" <rom...@ya...>, "Gramps Development List" <gra...@li...> > Date: Dimanche 16 décembre 2012, 14h52 > Hi Jerome, > > > The virtual marchine seems to be the 'easier' way! > > http://www.linuxfoundation.org/news-media/blogs/browse/2012/10/linux-foundation-uefi-secure-boot-system-open-source > > Thank you for posting this link. I read a lot of tricks on a > variety of forums, and they seem to be dangerous for people > like me, who don't know much about this UEFI stuff. When you > mess things up, Windows tells you to call for help, or to > return your system, which is something that I'd rather not > do, because I really like to manage my PC myself. > > Switching UEFI off in the BIOS seems to help a bit > sometimes, but I get the feeling that that also influences > Windows 8 in a way that I don't still understand, so I think > that I will follow your advice for now, or keep the old PC > for development. It's still on my desk, so ... > > > Also, for having gramps' environment (libs, binding) > and trunk. > > http://gramps-project.org/wiki/index.php?title=GEPS_029:_GTK3-GObject_introspection_Conversion#Installation > > Thanks for that too. I didn't try trunk yet, but with this > information, I feel more safe to try that some time. > > Can you or anyone else tell me whether it is useful for the > community to experiment with 3.4 on Windows 8? Some people > say that apps in Windows 8 will make the classic desktop PC > obsolete, and I know that Ancestry already has an app for > Windows 8. It's still read-only, but I think that it will > get the same editing capabilities as its Android > counterpart. > > And with that in mind, I suspect that spending any time on > 3.4 for Windows 8 is sort of a waste, except for bug fixing > of course. > > thanks, > > Enno > > |