OpenEuphoria

2. Re: The Euphoria IDE Project

• Posted by ghaberek (admin) Jun 12, 2012
• 5148 views

Here's my original mockup for a new IDE from years ago.

(larger image)

-Greg

4. Re: The Euphoria IDE Project

• Posted by ghaberek (admin) Jun 12, 2012
• 5106 views

Indeed I was! Once I start coding something, to BitBucket it shall go!

-Greg

6. Re: The Euphoria IDE Project

• Posted by ghaberek (admin) Jun 13, 2012
• 5045 views

Yessir. Probably GPLv3.

-Greg

8. Re: The Euphoria IDE Project

• Posted by mattlewis (admin) Jun 13, 2012
• 5011 views

That seems unusual. I assumed he meant the IDE code itself would be GPL3. The copyright of the output would be owned by the guy using the IDE, and not any sort of derivative of the IDE itself.

Matt

10. Re: The Euphoria IDE Project

• Posted by jimcbrown (admin) Jun 13, 2012
• 5009 views

I'd guess that the only code that needed 'linking' to would be the wxEuphoria libraries and their dependencies (wxWidgets itself, et al.). So this shouldn't even be an issue.

12. Re: The Euphoria IDE Project

• Posted by Lone_EverGreen_Ranger Jun 13, 2012
• 4981 views

Perhaps the IDE could be released under a custom license. Something that would allow users to release projects or programs they create in the IDE royalty free. Since the GPL is iffy in different regards to releasing derivatives works and stuff like that. Although if the IDE was licensed under the GPL, if you made a program in the IDE, the program you made could be released under any license you wanted, right?

14. Re: The Euphoria IDE Project

• Posted by jeremy (admin) Jun 13, 2012
• 5013 views

The application (IDE) is fine to be released as GPL, even if it generates source code. If, however, you do have a framework library, if you want anyone to be able to use it for commercial or many open source situations, it can not be licensed as GPL. It could be LGPL. If you have no framework library, then there is no need to worry about about GPL or not.

Jeremy

16. Re: The Euphoria IDE Project

• Posted by m_sabal Jun 14, 2012
• 4889 views

If WX is the GUI toolkit of choice, has any work been done yet on implementing a wxEuphoria project on Mac without having to install the whole toolkit independently? If the toolkit does have to be distributed independently on Mac, does anybody know where there might be a pre-compiled dmg. I have a number of people asking for Euphoria based applications I've written for Windows to be available for Mac, and these people don't have any idea that Mac comes with a terminal application, much less know how to use a command line.

18. Re: The Euphoria IDE Project

• Posted by ghaberek (admin) Jun 14, 2012
• 4831 views

I've pretty much decided on wxEuphoria as the GUI toolkit; I'd like this project to be entirely cross-platform. I'm still working out the logistics of the framework - that needs to be done properly from the start.

I have an old eMac that I plan on doing some development on. I'd like to see wxEuphoria applications run on PowerPC computers as well.

-Greg

20. Re: The Euphoria IDE Project

• Posted by petelomax Jun 17, 2012
• 4567 views

I had a look this weekend at getting wxEuphoria to run on Phix, and I made some notes on the matter. My apologies if this isn't helpful.

It seems I would need to suck alot of complexity out of libwxeu.dll (C++) into wxeud.e, specifically defaults, reference counting, and delete routines. In short, libwxeu.dll/so should contain absolutely no knowledge whatsoever of underlying data structures, and hence be compatible with both OpenEu and Phix.

Routines must be called/defined with atoms/pointers (C_INT etc), rather than E_SEQUENCE/E_OBJECT/E_ATOM/E_INTEGER. The logic for defaulted parameters would need to be moved out of wxeu.cpp, so for example (simplified/untested) instead of:

global function create(integer class, sequence params) 
object rid 
    rid = WX_CREATE_ARRAY[class] 
    return c_func(rid, {params}) 
end function 

and

#define NEW_CONTROL(control) \ 
        s1_ptr p = SEQ_PTR( params );\ 
        wxPoint pos = wxDefaultPosition;\ 
        wxSize size = wxDefaultSize;\ 
        intptr_t style = 0;\ 
        wxWindowID id = -1;\ 
        wxString caption(wxT(""));\ 
        \ 
        switch( p->length ){\ 
                case 8:\ 
                        style = get_int( params, 8 );\ 
                \ 
                case 7:\ 
                        size = wxSize( get_int( params, 6 ), get_int( params, 7 ) );\ 
                \ 
                case 6:\ 
                case 5:\ 
                        pos = wxPoint( get_int( params, 4 ), get_int( params, 5) );\ 
                \ 
                case 4:\ 
                case 3:\ 
                        caption = get_string( params, 3 );\ 
                case 2:\ 
                        id = get_int( params, 2 );\ 
                default:\ 
                        break;\ 
        }\ 
        control * cont = new control( (wxWindow *)get_int(params, 1),\ 
                        id, caption,\ 
                        pos, size, style );\ 
        wxDeRefDS(params);\ 
        return BOX_INT( cont ); 

global function create(integer class, sequence params) 
object rid 
integer style = 0 
integer sizeX = -1, sizeY = -1 
integer posX = -1, posY = -1 
sequence caption = "" 
integer id = -1 
integer parent 
    switch length(params) with fallthrough 
      8: style = params[8] 
      7: sizeX = params[6] sizeY = params[7] 
      6,5: posX = params[4] posY = params[5] 
      4,3: caption = params[3] 
      2: id = params[2] 
      1: parent = params[1] 
    end switch 
    rid = WX_CREATE_ARRAY[class] 
    return c_func(rid, {parent,id,caption,posX,posY,sizeX,sizeY,style}) 
end function 

and

#define NEW_CONTROL(control) \ 
wxPoint pos = {posX,posY};\ 
wxSize size = {sizeX,sizeY};\ 
    return new control( (wxWindow *)parent, id, caption, pos, size, style ); 

I appreciate that with some 1,400 routines that may be a massive amount of work and I have no idea what impact it would have on performance, but it may lead to better errors, eg "type check error, caption is 0".

Also, I don't really understand why it needs wxDeRefDS() etc; I can only assume that because it is using E_SEQUENCE; params gets incref'd and ends up in libwxeu.dll with a ref count >=2? Unless you do on-the-fly creation in wxeud.e then the actual deallocation/calling of any delete routine etc will occur not in libwxeu.dll but in exeud.e when "params" gets decref'd or when some callee variable drops out of scope.

Anyway, that's where I got, like I said don't know if that is of any interest or use.

The alternative would be to rewrite wxeu.cpp pretty much from scratch, but embed the knowledge of the underlying Phix data structures rather than those of OpenEu.

Regards, Pete

22. Re: The Euphoria IDE Project

• Posted by EUWX Jun 17, 2012
• 4502 views

I am a simple programmer. I am sure there are many others like me, who are not too particular about changes in the structure of wxEuphoria, but would like a good working wxEuphoria IDE. I would think that making changes in the IDE to make it a nice working IDE would be far easier and much less time consuming.
Even a good working editor for wxEuphoria integrated with version 4, would be a great help

24. Re: The Euphoria IDE Project

• Posted by Fendaril Jun 18, 2012
• 4443 views

Speaking of this, I would love a gui designer that generated wxEuphoria code. That would attract lazy bums like me to euphoria, and lazy bums are prevalent in this age of RAD!

26. Re: The Euphoria IDE Project

• Posted by ghaberek (admin) Jun 18, 2012
• 4417 views

A GUI designer will be part of this IDE. That is my first and highest priority. I want to "do RAD right" this time around. (The Win32Lib IDE does a decent job with GUI design, but it's outdated and leaves a lot to be desired, plus Win32Lib doesn't really play to the cross-platform strengths of Euphoria 4.)

-Greg

28. Re: The Euphoria IDE Project

• Posted by mattlewis (admin) Jun 18, 2012
• 4379 views

First, I would like to emphasize that if you have used C_INT, C_LONG (or their unsigned counterparts) for a pointer, you're doing it wrong, as these are not portable. Euphoria 4.1 will also run on 64-bit operating systems, so this is important.

Previous versions of wxEuphoria required that the manipulation of pointers, peeking and poking be done on the euphoria side. Not surprisingly, it's a lot easier to work with C++ data in C++ than in euphoria. Also, moving the creation macros into euphoria code would mean writing a lot more code.

wxEuphoria follows "normal" euphoria reference counting semantics, which makes using it very simple from a euphoria point of view, and is necessary to take E_SEQUENCE, etc, parameters and prevent memory leaks.

Yes, it sounds like that's what would have to happen. After a lot of experimenting, I think that the way I've got wxEuphoria working is the easiest way to go about wrapping a C++ library.

Matt

30. Re: The Euphoria IDE Project

• Posted by EUWX Jun 18, 2012
• 4335 views

I have some other concerns too. I generated a small program using, pure Euphoria and also some wxEuphoria (2.8) code. I used Wordpad. The moment you save the file as Unicode, you can't use it.
I then tried with the trial version of EditPlus which is a sophisticated Editor, and again the same problem, Save it as any type of Unicode file and it s unusable by Euphoria.
I understand that wxWidgets 2.9 is totally Unicode, so there may be other problems using it with Euphoria.

32. Re: The Euphoria IDE Project

• Posted by EUWX Jun 18, 2012
• 4290 views

Thanks. I shall wait for your big swing to wxWidget2.9 and the corresponding wsEuphoria with all the proposed namespaces (Oh, I so dislike Namespaces and Includes)

34. Re: The Euphoria IDE Project

• Posted by petelomax Jun 19, 2012
• 4312 views

Just checking: C_PTR is fine on 64-bit? And 64-bit is what you meant by "portable"?

Hmm. Maybe I should start with an old version then. Is there one still available?

I thought about that but quickly realised it's a longer-term goal. There would need to be two different builds/names of libwxeu.dll. Get something (anything!) working first.

Quite right. Phix is asm-based and you're a C++-head so I wouldn't want your help anyway

Regards,
Pete

36. Re: The Euphoria IDE Project

• Posted by ghaberek (admin) Jun 19, 2012
• 4328 views

I plan on getting either a Raspberry Pi and/or an Android PC System so I can develop against ARM with wxEuphoria. (Assuming I can install something like Debian/Ubuntu on the APC).

-Greg

38. Re: The Euphoria IDE Project

• Posted by EUWX Jun 19, 2012
• 4261 views

If you have not yet looked at it, Randy Hyde's HLA is worth looking at.
http://tech.groups.yahoo.com/group/aoaprogramming/
It gives you a very good way of writing in Assembler and easy connection to C++, including interfacing to DLLs, etc

http://homepage.mac.com/randyhyde/webster.cs.ucr.edu/HighLevelAsm/dnld.html

40. Re: The Euphoria IDE Project

• Posted by SDPringle Nov 08, 2012
• 3082 views

Don't misunderstand: The C types C_LONG, C_INT, C_SHORT are as portable as C_POINTER. Get the alternative literals branch. It has cross enum type checking.