OpenEuphoria

1. eugtk history

• Posted by ne1uno Aug 11, 2015
• 2681 views

I can understand not having a favorable experience with a GUI toolkit and maybe venting frustration but editing a wiki page to remove an OS because you couldn't get it working?

I may be taking out of turn here as I haven't tried the new version and so won't edit the wiki page. last time I did try most things worked. you can get a windows package very easily from some windows blender page. and note: gtk does require more setup and more package downloading than most toolkits.

if the newest version is no longer building for windows, then adding a newer version and older version page may have been a better edit than removing windows information altogether.

http://openeuphoria.org/wiki/history/eugtk.wc

feel free to tell me I haven't had my coffee yet. though I already know this.

3. Re: eugtk history

• Posted by petelomax Aug 11, 2015
• 2657 views

Maybe I have gone crazy. I was obviously very tired and very frustrated. I just thought it might be helpful to reflect the truth. It does not work, there is no support, and as far as I know nobody can get it to work.

Obviously I assume someone can and probably will undo those changes with a click of a button, but they'll be defending a lie.

Pete

PS For me, it just terminates with exit code #C0000005, at least according to procmon. No error message, no address, no ex.err, no core dump.

5. Re: eugtk history

• Posted by andi49 Aug 11, 2015
• 2855 views

Hi

Also i'am not a GTK-fanboy.

Try this: In GtkEngine.e around line 9074

---------------------------------------------------------------------------------------- 
export function define_proc(object name, object params={}) 
---------------------------------------------------------------------------------------- 
atom x 
	name='+'&name -- cdecl (remember it's not Windows so dll's may not use stdcall! 
[...] 

-------------------------------------------------------------------- 
export function define_func(object name, object params={}, object values=P) 
-------------------------------------------------------------------- 
atom x 
	name='+'&name -- cdecl (remember it's not Windows so dll's may not use stdcall! 
[...] 

Worked for me with an old GTK 3.4.2 setup from 2012 or so.

Hope this helps

Andreas

[Edit: Talking about 32bit dll's maybe it is different with 64bit dll's]

[Edit2: and this is how it looks on Win 10 http://euphoria.indonesianet.de/eugtk_win10.jpg]

7. Re: eugtk history

• Posted by ryanj Aug 14, 2015
• 2604 views

I haven't really kept up on EuGtk, but i agree with andi49. I think if windows support is having issues, the wiki page should be updated to explain that. What is the point of the wiki pages? To give really basic and useless info, or to give details of something so other people can know the whole truth of the status of something so they can learn what's going on with euphoria projects and make an informed decision on whether or not to use something or help to come up with a solution for it? Food for thought.

By the way, perhaps a little off topic, but, i have always been a little bit annoyed about how little information the wiki pages have about stuff. If people would spend some time working on wiki pages that give useful information about the projects they are creating with euphoria, that could be very useful. I feel like i'm the only one who does that with my Redy project and related applications, like i try too hard to market my incomplete software. It makes me wonder if i'm weird or something. But i wish other people would try to convince others why they should try their euphoria library or application. Maybe what i'm trying to say is i wish the euphoria community would do more to "market" their stuff, not just put it out there. That goes for euphoria itself, as well as libraries and applications, and even ideas about how to improve things in the euphoria community.

9. Re: eugtk history

• Posted by euphoric (admin) Aug 21, 2015
• 2693 views

	name='+'&name -- cdecl (remember it's not Windows so dll's may not use stdcall! 

This fix works for me, EXCEPT, I'm getting a console window popping up with this message:

FIXME Windows GtkEngine.e line 146...151 

What is that?

11. Re: eugtk history

• Posted by euphoric (admin) Aug 21, 2015
• 2442 views

FIXME Windows GtkEngine.e line 146...151 

constant os_info = os:uname() 
    localhost = "127.0.0.1", 
 
ifdef UNIX then 
 export constant  
    os_architecture = os_info[5], -- e.g: x86_64 
    os_shell = getenv("SHELL"), -- e.g: /bin/bash 
    host_addr = inet_address() 
end ifdef 
 
ifdef WINDOWS then -- FIXME 
    display("FIXME Windows GtkEngine.e line 146..151")    -- *** here be that message! *** 
export constant 
    os_architecture = "unknown", 
    os_shell = "cmd.com", 
    host_addr = localhost 
 end ifdef 
  
object os_term = getenv("TERM") 
    if atom(os_term) then os_term = "none" end if 
 
ifdef WINDOWS then os_term = "CMD.COM" end ifdef 

I have Euphoria code that identifies the Windows OS for another program I use. Do I need to plug it in here to fix this? Seems like that's what this needs, eh?

Thanks for the heads up, Pete!

Actually, Euphoria needs to know what OS it's running on. Doesn't it know that already?!?!

13. Re: eugtk history

• Posted by andi49 Aug 24, 2015
• 2402 views

Hi

does the fix work for anybody else? Except 'euphoric'?
Do the provided solutions for the 'FIXME' work on other machines (except mine)?

I just wan't to know. Becouse i personally do not use GTK3(Windows), and i do not like to waste time debugging it if nobody cares.

Andreas

15. Re: eugtk history

• Posted by andi49 Aug 24, 2015
• 2421 views

Hi

your code wan't work on Win8+ without this kind of manifest.xml

<exe>.manifest 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> 
<assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3"> 
    <assemblyIdentity  
        type="win32"  
        name=SXS_ASSEMBLY_NAME 
        version=SXS_ASSEMBLY_VERSION 
        processorArchitecture=SXS_PROCESSOR_ARCHITECTURE 
    /> 
    <description> my foo exe </description> 
    <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> 
        <security> 
            <requestedPrivileges> 
                <requestedExecutionLevel 
                    level="asInvoker" 
                    uiAccess="false" 
                />	 
            </requestedPrivileges> 
        </security> 
    </trustInfo> 
    <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">  
        <application>  
            <!-- Windows 10 -->  
            <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/> 
            <!-- Windows 8.1 --> 
            <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/> 
            <!-- Windows Vista --> 
            <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>  
            <!-- Windows 7 --> 
            <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/> 
            <!-- Windows 8 --> 
            <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/> 
        </application>  
    </compatibility> 
</assembly> 

For Euphoria Scripts euiw.exe or eui.exe needs to be compiled with this kind of manifest.xml. But it seems no one takes care about this since WInXP.
You may follow this old thread. http://openeuphoria.org/forum/124650.wc#124650
Andreas