[ovirt-devel] ovirt support ie7 ?
Hi, all: Does ovirt support IE 7? If support , how could I build it for IE 7? ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] ovirt support ie7 ?
On Aug 25, 2014, at 10:41 , Lior Vernia lver...@redhat.com wrote: Hello, To the best of my knowledge IE9 and above is supported. To build exclusively for IE9 you could add the following line when running make (see README.developer file in the root your ovirt-engine source directory for reference): DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS=-Dgwt.userAgent=ie9 You might try passing ie6 or ie7 instead of ie9 - I have no experience doing this, but even if it's not supported it might work enough :) AFAIK it does not way too old…. IE8 may still work, very very slowly… Yours, Lior. On 25/08/14 11:25, Leaboy wrote: Hi, all: Does ovirt support IE 7? If support , how could I build it for IE 7? ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] ovirt support ie7 ?
- Original Message - From: Lior Vernia lver...@redhat.com To: Leaboy wlblea...@126.com Cc: engine-de...@ovirt.org devel@ovirt.org Sent: Monday, August 25, 2014 10:41:03 AM Subject: Re: [ovirt-devel] ovirt support ie7 ? Hello, To the best of my knowledge IE9 and above is supported. To build exclusively for IE9 you could add the following line when running make (see README.developer file in the root your ovirt-engine source directory for reference): DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS=-Dgwt.userAgent=ie9 You might try passing ie6 or ie7 instead of ie9 - I have no experience doing this, but even if it's not supported it might work enough :) well, I don't think it will work enough - I have seen userportal (which is way simpler than webadmin) about a year ago (when it was way simpler than today) on IE6 and it was not really possible to find any button there not to mention the performance :) Yours, Lior. On 25/08/14 11:25, Leaboy wrote: Hi, all: Does ovirt support IE 7? If support , how could I build it for IE 7? ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] ovirt support ie7 ?
- Original Message - From: Tomas Jelinek tjeli...@redhat.com To: Lior Vernia lver...@redhat.com Cc: Leaboy wlblea...@126.com, engine-de...@ovirt.org devel@ovirt.org Sent: Monday, August 25, 2014 10:42:22 AM Subject: Re: [ovirt-devel] ovirt support ie7 ? - Original Message - From: Lior Vernia lver...@redhat.com To: Leaboy wlblea...@126.com Cc: engine-de...@ovirt.org devel@ovirt.org Sent: Monday, August 25, 2014 10:41:03 AM Subject: Re: [ovirt-devel] ovirt support ie7 ? Hello, To the best of my knowledge IE9 and above is supported. To build exclusively for IE9 you could add the following line when running make (see README.developer file in the root your ovirt-engine source directory for reference): DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS=-Dgwt.userAgent=ie9 You might try passing ie6 or ie7 instead of ie9 - I have no experience doing this, but even if it's not supported it might work enough :) well, I don't think it will work enough - I have seen userportal (which is way simpler than webadmin) about a year ago (when it was way simpler than today) on IE6 and it was not really possible to find any button there not to mention the performance :) but if you will compile it for the ie7 and it will work let us know, I just don't really believe it... Anyway, why do you need it? Maybe you could use some alternative userportal? (http://www.ovirt.org/Sample_user_portals) Yours, Lior. On 25/08/14 11:25, Leaboy wrote: Hi, all: Does ovirt support IE 7? If support , how could I build it for IE 7? ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] ovirt support ie7 ?
On Monday, August 25, 2014 11:41:03 AM Lior Vernia wrote: Hello, To the best of my knowledge IE9 and above is supported. To build exclusively for IE9 you could add the following line when running make (see README.developer file in the root your ovirt-engine source directory for reference): DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS=-Dgwt.userAgent=ie9 You might try passing ie6 or ie7 instead of ie9 - I have no experience doing this, but even if it's not supported it might work enough :) I recommend against it, but if you insist on trying, there is no specific user agent to compile for IE7 as it uses pretty much the same Javascript engine as IE6, so you would have to pass IE6 as the user agent with the extra build flags as above. Yours, Lior. On 25/08/14 11:25, Leaboy wrote: Hi, all: Does ovirt support IE 7? If support , how could I build it for IE 7? ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] ovirt35 - deep dive - Prevent host fencing while kdumping - integrating with kexec tools
BEGIN:VCALENDAR PRODID:Zimbra-Calendar-Provider VERSION:2.0 METHOD:REQUEST BEGIN:VTIMEZONE TZID:Asia/Jerusalem BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETTO:+0200 TZOFFSETFROM:+0300 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU TZNAME:IST END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02 TZOFFSETTO:+0300 TZOFFSETFROM:+0200 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1FR TZNAME:IDT END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:cf2e371b-ae13-4500-967b-2acd264a5b65 SUMMARY:ovirt35 - deep dive - Prevent host fencing while kdumping - integrat ing with kexec tools ATTENDEE;CN=Martin Perina;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TR UE:mailto:mper...@redhat.com ATTENDEE;CN=Oved Ourfalli;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TR UE:mailto:ov...@redhat.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:users@o virt.org ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:devel@o virt.org ORGANIZER;CN=Barak Azulay:mailto:bazu...@redhat.com DTSTART;TZID=Asia/Jerusalem:20140826T163000 DTEND;TZID=Asia/Jerusalem:20140826T173000 STATUS:CONFIRMED CLASS:PUBLIC X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY TRANSP:OPAQUE LAST-MODIFIED:20140825T135405Z DTSTAMP:20140825T135405Z SEQUENCE:0 DESCRIPTION:The following is a new meeting request:\n\nSubject: ovirt35 - de ep dive - Prevent host fencing while kdumping - integrating with kexec tools \nOrganizer: Barak Azulay bazu...@redhat.com \n\nTime: Tuesday\, August 26\, 2014\, 4:30:00 PM - 5:30:00 PM GMT +02:00 Jerusalem\n \nInvitees: mper i...@redhat.com\; ov...@redhat.com\; us...@ovirt.org\; devel@ovirt.org \n\n\n *~*~*~*~*~*~*~*~*~*\n\nThis session describes how kdump mechanism is integra ted into oVirt 3.5 non-responsive host treatment \nin order to prevent host being fenced while gathering its crash dump. \n\ngoogle hangout link: https: //plus.google.com/events/c2np5fedno8e8qifas6el8a3ih4 \nwiki page link:http:/ /www.ovirt.org/Fence_kdump BEGIN:VALARM ACTION:DISPLAY TRIGGER;RELATED=START:-PT5M DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] Call for Papers Deadline Friday: Latinoware 2014
The CfP for the eleventh annual Latin American Free Software Conference closes on Aug. 29. http://2014.latinoware.org/?page_id=3033 (The page appears to be down right now, but hopefully will be up soon.) Peace, Brian -- Brian Proffitt oVirt Community Manager Project Atomic Community Lead Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] Some maven warnings while running ovirt-engine_3.5_find-bugs_merged
Can someone who understand how maven works better than me take a look at the warnings in http://jenkins.ovirt.org/job/ovirt-engine_3.5_find-bugs_merged/379/consoleFull And see if we can get rid of some of them? Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] Tools for developing and building oVirt.js project
Hi guys, last week, we had oVirt.js PoC session and I mentioned the possibility of using Node.js and related tools like npm to develop build oVirt.js project. I'd like to hear your opinion - what do you think about using Node.js in context of developing building JavaScript projects? (oVirt.js etc.) Obviously, I'm strongly biased towards Node.js because of its popularity and therefore availability of various tools (npm packages) for JavaScript, for example: grunt (task runner), jslint/hint (code analyzer), uglifyjs (minify/compress), karma (both one-time continuous test runner), traceur (es6 - es5 compiler), etc. My understanding is that any special-purpose JavaScript development tool is typically implemented as module for Node.js (due to its popularity), so I think it makes sense to use Node.js as a platform for JavaScript development. There are also Java-based projects for JavaScript (post)processing like wro4j, however these tend to be implemented by invoking JS tools (like uglifyjs) from Java context via Rhino (JS engine for Java), for example: https://code.google.com/p/wro4j/source/browse/wro4j-extensions/src/main/java/ro/isdc/wro/extensions/processor/support/uglify/UglifyJs.java (To me, developing JavaScript project with Java-centric tooling sounds quite strange in general.) There's also webjars repository for hosting popular web resources for use in Java applications (i.e. Maven artifact for uglifyjs etc.), but this is just for easier dependency management from Java perspective (JAR file as a distribution format for web resources): http://www.webjars.org/ Overall, I'm in favor of using Node.js to manage all tasks related to JavaScript development and build process. If you have any objections or suggestions, I'd like to hear them! (I understand that Node.js essentially means new dependency with all implications, but in this case, I think it's worth it. But this is just me, so please share your opinions.) Thanks, Vojtech ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] Ideas on modular UI
BEGIN:VCALENDAR PRODID:Zimbra-Calendar-Provider VERSION:2.0 METHOD:REQUEST BEGIN:VTIMEZONE TZID:Europe/Belgrade BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETTO:+0100 TZOFFSETFROM:+0200 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU TZNAME:CET END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02 TZOFFSETTO:+0200 TZOFFSETFROM:+0100 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1SU TZNAME:CEST END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:00d91ecb-e69c-4b6a-bf36-aa779bdaee6b SUMMARY:Ideas on modular UI ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:devel@o virt.org ORGANIZER;CN=Vojtech Szocs:mailto:vsz...@redhat.com DTSTART;TZID=Europe/Belgrade:20140827T15 DTEND;TZID=Europe/Belgrade:20140827T16 STATUS:CONFIRMED CLASS:PUBLIC X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY TRANSP:OPAQUE LAST-MODIFIED:20140825T155829Z DTSTAMP:20140825T155829Z SEQUENCE:0 DESCRIPTION:The following is a new meeting request:\n\nSubject: Ideas on mod ular UI \nOrganizer: Vojtech Szocs vsz...@redhat.com \n\nTime: Wednesday \, August 27\, 2014\, 3:00:00 PM - 4:00:00 PM GMT +01:00 Belgrade\, Bratisla va\, Budapest\, Ljubljana\, Prague\n \nInvitees: devel@ovirt.org \n\n\n*~*~* ~*~*~*~*~*~*~*\n\nHi guys\,\n\nthis session presents some ideas on making oV irt UI modular\,\nbreaking up complexity of monolithic GWT applications whil e\nallowing for easier (less painful) development and extension.\n\nThis sho uld be a rather short (30 min) session.\n\nThis meeting will be held via Blu eJeans: \n\nhttps://bluejeans.com/6473766993 \n\nIt's also possible to join via phone: \n\n1) Dial into BlueJeans: \nhttp://bluejeans.com/numbers \n\n2) Enter Conference ID: \n6473766993 \n\nSlides will be provided shortly.\n\nR egards\,\nVojtech\n BEGIN:VALARM ACTION:DISPLAY TRIGGER;RELATED=START:-PT5M DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] Ideas on modular UI - slides
Hi, slides are attached. Regards, Vojtech modular-ui.pdf Description: Adobe PDF document ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] What does your oVirt development environment look like?
On 21/08/14 09:17 -0400, Greg Sheremeta wrote: Good idea. Thanks, and thank you for sharing. I work on the UI, so I don't have much of a need for a complex setup. I have the two mini dells, and then I have two much more powerful personal machines that I use for work -- machine 1 (dauntless) is my main development machine, and machine 2 (starbase) is my main home server. I compile and run engine on dauntless, and starbase serves NFS and SMB. I don't have iscsi setup, although I probably should learn this. I use nested virt for all my hosts, For a Friday afternoon project you might want to check out this easy to follow guide for targetcli. It's what I use for software iSCSI and it works pretty well for me: https://wiki.archlinux.org/index.php/ISCSI_Target so mini dell 1 and mini dell 2 both run Fedora 20 and I basically just remote to them to install vms via virt-manager. I had cobbler running at one point, but I got frustrated with it one too many times and gave up. Now I just have a giant collection of isos available via NFS (and scattered on the desktops of the mini dells :)) I typically install fresh hosts using the F20 network-install iso. It's a little slower, but very reliable. Yeah, I am wondering if this would be a better approach (though I really do like the unattended PXE installations I can do with cobbler). I tend to not need more than one of two database instances at a time. I gave up using my laptop for primary development because I need three monitors on my dev rig, and my laptop supports two max. (I'm currently heartbroken at the lack of USB3 video for linux. See [1].) I basically use my laptop as a remote viewer to dauntless now when I'm working in bed or wanting to sit out on the porch. (RealVNC encrypted mode -- I use an xrandr script to toggle off two of dauntless's monitors, and then I full-screen VNC.) Old pic of my desk: [2] Wow, I feel really low-tech with my single widescreen monitor here. Dauntless, starbase, the dells, and all monitors are connected to a giant UPS. Home network equipment is all connected to another UPS. I've given some thought to building a distributed compile of ovirt (specifically the GWT part -- maybe distribute each permutation to worker nodes), but I was under the impression that most people just use their laptop for work. I think a distributed compile would be pretty nice for me, but not sure how many people would use it. ? I try to compile engine as infrequently as possible. Due to what it does to my running system, I usually reboot afterwords too. -- Adam Litke ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Tools for developing and building oVirt.js project
- Original Message - From: Vojtech Szocs vsz...@redhat.com To: devel@ovirt.org Sent: Monday, August 25, 2014 11:13:38 AM Subject: [ovirt-devel] Tools for developing and building oVirt.js project Hi guys, last week, we had oVirt.js PoC session and I mentioned the possibility of using Node.js and related tools like npm to develop build oVirt.js project. I'd like to hear your opinion - what do you think about using Node.js in context of developing building JavaScript projects? (oVirt.js etc.) Obviously, I'm strongly biased towards Node.js because of its popularity and therefore availability of various tools (npm packages) for JavaScript, for example: grunt (task runner), jslint/hint (code analyzer), uglifyjs (minify/compress), karma (both one-time continuous test runner), traceur (es6 - es5 compiler), etc. My understanding is that any special-purpose JavaScript development tool is typically implemented as module for Node.js (due to its popularity), so I think it makes sense to use Node.js as a platform for JavaScript development. There are also Java-based projects for JavaScript (post)processing like wro4j, however these tend to be implemented by invoking JS tools (like uglifyjs) from Java context via Rhino (JS engine for Java), for example: https://code.google.com/p/wro4j/source/browse/wro4j-extensions/src/main/java/ro/isdc/wro/extensions/processor/support/uglify/UglifyJs.java (To me, developing JavaScript project with Java-centric tooling sounds quite strange in general.) There's also webjars repository for hosting popular web resources for use in Java applications (i.e. Maven artifact for uglifyjs etc.), but this is just for easier dependency management from Java perspective (JAR file as a distribution format for web resources): http://www.webjars.org/ Overall, I'm in favor of using Node.js to manage all tasks related to JavaScript development and build process. If you have any objections or suggestions, I'd like to hear them! (I understand that Node.js essentially means new dependency with all implications, but in this case, I think it's worth it. But this is just me, so please share your opinions.) Thanks, Vojtech I think most developers would agree that node.js is the tool of choice for JavaScript development. The thing we must carefully consider is that node.js uses its own package manager (npm -- much like maven), and unlike maven, tooling does not yet exist to deal with npm packages in an rpm environment. This isn't on the same level as adding a logging library or a collections library or something. I'd argue that dependencies don't get any heavier than this one. That is worrisome to me. Run 'yum list available |grep nodejs' on your machine to see which node.js packages are available. Note that I don't see karma or uglify available in either Fedora or Red Hat SCL (Software Collections) [1]. [1] https://sochotni.fedorapeople.org/nodejs010-RHSCL-1-RHEL-6/Server/x86_64/os/Packages/ Greg ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
