Kodi Community Forum
XBMC_PC Win32 GUI Development Environment for skinners (skin developers) - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Development (https://forum.kodi.tv/forumdisplay.php?fid=32)
+--- Forum: Skinning (https://forum.kodi.tv/forumdisplay.php?fid=12)
+--- Thread: XBMC_PC Win32 GUI Development Environment for skinners (skin developers) (/showthread.php?tid=23235)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

- Jezz_X - 2008-02-13

You too WiSo there is however a win32 SDL version as well thats based on the linux port a guy named ArtVandelee has been making all the things work on it that don't work very well in the directx version you can see the thread here with a patch included
The advantage over the directx version is it actually has a couple of visualisations working with it.
I posted a list of things that don't really work in the directx version a while back in this thread

- WiSo - 2008-02-13

Yep read the thread. The question is how is the windows build supposed to continue? With sdl, directx or both merged? DirectX would be the natural choice under windows but with the sdl stuff the build is more close to the other ports.
Let's see how Art is proceeding.

- Jezz_X - 2008-02-13

Well jmarshall has said from the start that he has no desire to make the directx windows port anything more than a tool for skinnners and scripters. These days in the terms of functions the linux SDL version way outways the directx version with things like

*Web server works
*Visualizations work Including a milkdrop Varient (projectm)
*More Audio formats supported
*Video player has a lot more support
*MythTv backend can be accessed to play back live tv
*Settings like network / time / screen res actually change the pc
*Fullscreen works
*Joystick control (so you can use wired/wireless controllers)
*Remote control support
*Can be run as the default UI for the PC (no need to boot into windows then run)
*Vsync support to stop video tearing
*The UI actually resizes to the screen rez its not just a stretched out directx overlay
*A few really good devs who are doing a great job

and probaly more but thats all I remember right now Smile
I know that with some work the directx verison cn have all this too if some one really wants

- WiSo - 2008-02-13

Ok thanks for the enlightenment. I understand then the concentration on the sdl build.

- Gamester17 - 2008-02-13

Yes please only concentrate on the SDL version of XBMC for Windows (Win32 port from the "linuxport" branch in the SVN).

Note however that SDL is only a middle-ware-layer which underneath can be made to use either DirectX or OpenGL.

Though picking up where ArtVandelae left of in order to finish the OpenGL version of SDL Win32 port for Windows might be the best point to start before looking into using DirectX/Direct3D instead of OpenGL with SDL.

Big Grin

PS! You probably want to try to use the latest development version of SDL (SDL 1.3) which is under construction and available via libSDL subversion depository

Best of luck!

- WiSo - 2008-02-13

Ok, I'll give it a try when back home. How can I make sure to get the right version via svn? Currently I use https://xbmc.svn.sourceforge.net/svnroot/xbmc/trunk/XBMC to check out.
How can I choose the build target (DirectX or SDL)? Looking at the docu here http://www.xboxmediacenter.com/wiki/?title=HOW-TO:_Compile_XBMC_for_Win32_from_source_code it looks like that both builds using the same project file. Any precompiler definitions to set (found nothing in Art's patch file)?
Sorry for the questions but it takes some time to come in again Confused

- Gamester17 - 2008-02-13

WiSo Wrote:Ok, I'll give it a try when back home. How can I make sure to get the right version via svn? Currently I use https://xbmc.svn.sourceforge.net/svnroot/xbmc/trunk/XBMC to check out.
That is wrong for SDL, you should use the linuxport branch instead, so change the URL to https://xbmc.svn.sourceforge.net/svnroot/xbmc/branches/linuxport/XBMC/

I have not tried it myself but I believe that you should just be able to load the xbmc.vcproj project file in Microsoft Visual Studio(?), maybe ask ArtVandelae in his topic thread in the development forum to not get too much off-topic over here.

I pretty sure that the wiki article can not be trusted today, feel free to update it with the correct instructions when you get it to build (after you created an account on the wiki then PM pike for 'ninja' status for the wiki in order to get write access).

- WiSo - 2008-02-13

Ok that's enough for the beginning. I'll ask further questions in the development forum.
My other questions are also answered since the win32 project file of the linux branch contains the needed build targets and definitions.

- jmarshall - 2008-02-13

Good to see you around again WiSo. Just dump Art's patches over the linuxport branch and it should be all good (save for any changes since then).

Let me know if you need more info in dev forums Smile


Latest xbmc_pc compiles break's playing video's in color. - djdafreund - 2008-02-27

I built a new compile today (Rev.11823) using both the XBMCDBR method+PC build, and also made one using the Build.bat (choosing 2-pc,and rebuild NEW exe) and both are not showing color in video's, only shows black and white, so i'm only guessing based off this that the build isn't the problem. It's a found bug.
The oldest build i still have is backed up is from 2-16-2008, and when i take the XBMC_PC.exe file and copy it over to my XBMC-PC directory, it plays video's fine in color again. I know it's not a compile error, as i just grabbed the T3CH XBMC 2008-02-24 SVN rev11787 build and grabbed his XBMC_PC file, and tried that one and it's also black and white video's, no matter which settings. So it's confirmed it's not a bad build on my end, as i trust T3CH's builds, and have the same effect happening.
So somehow between 02-16-2008 fresh build, and 02-24-08 fresh build, color video playback got broke. Please tell me anything else needed and i will post it.

- pt-1 - 2008-02-27

I have the same result on 2 different PC's

PC 1 is a Laptop:

Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_qfe.070227-2300)
           Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
       System Model: Latitude D610                  
               BIOS: Phoenix ROM BIOS PLUS Version 1.10 A06
          Processor: Intel(R) Pentium(R) M processor 1.86GHz
             Memory: 2040MB RAM
          Page File: 724MB used, 3208MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
        Card name: Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family
     Manufacturer: Intel Corporation
        Chip type: Intel(R) 915GM/GMS,910GML Express Chipset
         DAC type: Internal
       Device Key: Enum\PCI\VEN_8086&DEV_2592&SUBSYS_01821028&REV_03
   Display Memory: 128.0 MB
     Current Mode: 1024 x 768 (32 bit) (60Hz)
          Monitor: Plug and Play Monitor
  Monitor Max Res: 1600,1200
      Driver Name: ialmrnt5.dll
   Driver Version: 6.14.0010.4410 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 10/14/2005 15:06:58, 36990 bytes

My other PC is a normal HP Desktop

Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.070227-2254)
           Language: English (Regional Setting: English)
System Manufacturer: Hewlett-Packard
       System Model: HP Compaq dc7100 SFF(DX878AV)
               BIOS: Default System BIOS
          Processor: Intel(R) Pentium(R) 4 CPU 2.80GHz (2 CPUs)
             Memory: 3072MB RAM
          Page File: 427MB used, 4024MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.2600.2180 32bit Unicode
Card name: Radeon X1550 Series  
     Manufacturer: ATI Technologies Inc.
        Chip type: ATI Radeon Graphics Processor (0x7187)
         DAC type: Internal DAC(400MHz)
       Device Key: Enum\PCI\VEN_1002&DEV_7187&SUBSYS_5920174B&REV_00
   Display Memory: 256.0 MB
     Current Mode: 1280 x 1024 (32 bit) (60Hz)
          Monitor: Plug and Play Monitor
  Monitor Max Res: 1600,1200
      Driver Name: ati2dvag.dll
   Driver Version: 6.14.0010.6764 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail

- Jezz_X - 2008-02-27

We know (well some us do anyway)

- BigBellyBilly - 2008-02-27

Using xbmc_pc on a PC that has a direct internet connection , I used to get the winsock error when using xbmc_pc, but after some advice, removing socket imports in scripts cured it.

but, I still get the error when using xbmc_pc on a PC internet connected throu a proxy (correct proxy details entered in proxy xbmc -> network -> proxy settings). the xbmc_pc retrieves home page rss feeds and weather without problem.

Any advice ?

- djdafreund - 2008-03-07

Is there a patch to fix it to get color again? What got broke?

- Jezz_X - 2008-03-07

we don't know what broke and since its meant to be a skinning / python tool no one is looking as far as i know