OpenEuphoria

1. Redy 1.0.a1 released!

• Posted by ryanj Dec 08, 2014
• 4334 views

The first development release of Redy is finally finished!

See the official Redy website for documentation and downloading. I decided to go ahead and release what I had for now. RedyCode is too immature to use as a real text editor right now, but that will be my main priority for the next release, probably in January. I am open to feature requests. There is a long list of things I still plan to add, but it will probably take another 6-12 months to implement everything, so I will try to add the most useful things first.

I recommend running all of the includded apps first, and then use them as a starting point for writing your own. Documentation is not quite finished, but there should be enough to get started, and there is at least one tutorial for now. Let me know what you think. I will be happy to answer any questions on how to get Redy to do what you need.

I really hope you guys like it, because I have been working on this for about...i dunno...8 years? It has gone through about 3 name changes and at least a dozen complete rewrites. Now, for the first time in my life, I can say I am proud of how well-organized, well-written, and non-hack-job my code is, and there really isn't anything I can think of that needs to be unspaghettified.

I think what make the biggest difference was writing my own oswin library from scratch that directly accesses only the win32api that Redy needs and nothing extra. (Thanks to the various libraries I have found on the euarchives to borrow code from or look at for examples on wrapping C libraries.) Then, I reworked a lot of code I had and carefully cleaned it up and built it upon the layer that oswin provides. Because of this layered structure, I believe the process of porting Redy to Linux will be fairly straightforward, but that will have to wait until I finish the features I have planned.

Even though many little things are missing, it won't be difficult to finish because at this point, the foundational code has been established and seems to be very reliable and efficient. I just need to keep adding the features I have planned out in my mind before I can call it version 1.0.0. After that, I want to work on what is the ultimate reason I created this platform in the first place: applications.

Enjoy, my fellow Euphorians!

Sincerely,

Ryan J.

3. Re: Redy 1.0.a1 released!

• Posted by DerekParnell (admin) Dec 09, 2014
• 4262 views

Well done.

I have a simple backup/restore program which I wrote, and currently use each day, that needs a GUI interface. I'll let you know what I find using this.

5. Re: Redy 1.0.a1 released!

• Posted by Icy_Viking Dec 09, 2014
• 4184 views

Aweosme job. RedyCode could be a good IDE to use for Euphoria, add some intellisense and syntax coloring, and it would be awesome.

7. Re: Redy 1.0.a1 released!

• Posted by ChrisB (moderator) Dec 10, 2014
• 4155 views

Hi

I think this is great. Good job.

What I have found, and I am sure many other beginners will find, is that getting your head round the fitting widgets into containers expanding horizontally and vertically can be a bit 'brain straining' sometimes. Having looked at the 'include a separate dialog include' system, it shouldn't be a great jump to making an interactive dialog visual builder, which would make building programs a far more attractive proposition for the newcomer.

Anyway, nice job again.

Cheers

Chris

9. Re: Redy 1.0.a1 released!

• Posted by ryanj Dec 10, 2014
• 4085 views

Good point. It probably takes some getting used to. But I think it is better to let the system control layout instead of doing it manually, especially when themes, language options, and system font/dpi settings get factored in (which will work in a future version).

After the basic functionality works in RedyCode, i will add a visual GUI builder. I am also considering a library that can load widgets defined by xml files, if people are interested in that (or perhaps someone could write one).

11. Re: Redy 1.0.a1 released!

• Posted by ryanj Dec 15, 2014
• 3982 views

Status update:

The next step is to get RedyCode working, and that requires a powerful text editor library. This library will be the main new feature of the next release of Redy.

This library, gui/objects/textedit.e, will be the first real demonstration of what the canvas widget class can do. It is categorized as a "canvas object" library, which means it is specifically designed to control a canvas widget to present what you could think of as a "custom widget". This ability to create your own custom graphical controls or editors using the canvas widget class is one of the most important features of Redy.

I am designing it to be able to do word wrap, syntax highlighting for several file types, context-sensitive help, intelligent word/block completion, search/replace, spell checking, redo/undo, several editing modes, and formatted text rendering mode. I am using Euphoria's multitasking abilities and some optimization methods to handle large files efficiently and without locking up the application. This will take a long time to complete, but basic functionality should work in the next few weeks.

This library handles multiple instances of text editors. Basically, you create containers, and then tell the textedit.e library to create text editor instances, then to show selected instances in canvas widgets, by specifying the canvas widget name and parent container name. Here's a little snapshot of the test app:

without warning 
 
global constant  
App_Name = "Redy - textedit.e test", 
App_Version = "1.0.a1" 
 
include gui/gui.e as gui 
include gui/objects/textedit.e as txte 
 
include std/task.e 
include std/text.e 
include std/pretty.e 
include std/utils.e 
include std/sequence.e 
 
procedure gui_event(object evwidget, object evtype, object evdata) 
    --switch evwidget do 
    --end switch 
end procedure 
 
procedure start() 
    gui:wcreate({ 
        {"name", "winMain"}, 
        {"class", "window"}, 
        {"title", App_Name}, 
        {"visible", 1}, 
        {"size", {640, 480}}, 
        {"position", {0, 0}} 
    }) 
    gui:wcreate({ 
        {"name", "cntMain"}, 
        {"parent", "winMain"}, 
        {"class", "container"}, 
        {"orientation", "horizontal"}, 
        {"sizemode_x", "expand"}, 
        {"sizemode_y", "expand"} 
    }) 
    gui:wcreate({ 
        {"name", "cntLeft"}, 
        {"parent", "cntMain"}, 
        {"class", "container"}, 
        {"orientation", "vertical"}, 
        {"sizemode_x", "expand"}, 
        {"sizemode_y", "expand"} 
    }) 
    gui:wcreate({ 
        {"name", "divVerticalSplit"}, 
        {"parent", "cntMain"}, 
        {"class", "divider"}, 
        {"attach", "cntLeft"} 
    }) 
    gui:wcreate({ 
        {"name", "cntRight"}, 
        {"parent", "cntMain"}, 
        {"class", "container"}, 
        {"orientation", "vertical"}, 
        {"sizemode_x", "expand"}, 
        {"sizemode_y", "expand"} 
    }) 
    txte:create({ 
        {"name", "txt1"}, 
        {"label", "Text Editor 1"}, 
        {"text", { 
            "Lorem ipsum dolor sit amet consectetuer commodo et malesuada sapien Sed. Dui sollicitudin lacinia laoreet Curabitur tristique tempus Sed malesuada Curabitur ante. Aliquam lacus convallis tellus laoreet nibh iaculis gravida habitant Aliquam auctor. Magna pretium id Aenean eros nec nulla pulvinar urna magna ut. Scelerisque nibh malesuada risus dolor lacus Curabitur justo dignissim elit Morbi. Semper convallis magna eget mauris." 
        }} 
    }) 
    txte:create({ 
        {"name", "txt2"}, 
        {"label", "Text Editor 2"}, 
        {"text", { 
            "Redy is an open source project written in the Euphoria programming language which is easy to learn. Its use of simple English words rather than punctuation enables you to quickly read the source code and understand it. It uses dynamic variables called sequences to store data of any size and complexity without dealing with pointers, structures, or data types. It is an extremely fast interpreted language, and can be translated to C and compiled to run even faster.", 
            "Redy is a system of Euphoria libraries and programs designed according to specific standards to make it easy to write Euphoria programs. Its main feature is a Graphical User Interface library that is written from scratch in pure Euphoria code to take full advantage of Euphoria's syntax features with minimal overhead. This unique GUI hides the complexities of low-level operating-system-specific APIs with a system of widgets which are specially designed to be extremely easy to use. Additionally, Redy provides an Integrated Development Environment called RedyCode that makes it very easy to write, debug, document, and distibute programs in the Euphoria language." 
        }} 
    }) 
    txte:show("txt1", "canLeftEdit", "cntLeft") 
    txte:show("txt2", "canRightEdit", "cntRight") 
end procedure 
 
gui:start(routine_id("start"), routine_id("gui_event")) 

13. Re: Redy 1.0.a1 released!

• Posted by buzzo Dec 17, 2014
• 3720 views

I put the referenced includes in the proper place... recieved the same error..

running 4.0.5

15. Re: Redy 1.0.a1 released!

• Posted by buzzo Dec 17, 2014
• 3717 views

Do not think that the includes are the problem...

It maybe the order in which the includes are parsed ..

Error: C:\Euphoria\redy\apps\RedyDemos_1.0.dev\..\..\redylib_1.0.dev\gui\themes.e:459 
 
<0074>:: Errors resolving the following references: 
 
..\.\redylib-1.0.dev\gui\wc\wc_canvas.e <151>: ScreenX 
 
..\.\redylib-1.0.dev\gui\wc\wc_canvas.e <151>: ScreenY 

17. Re: Redy 1.0.a1 released!

• Posted by buzzo Dec 17, 2014
• 3713 views

the eu.cfg file was not altered.

the path to wc_canvas.e is Euphoria/redy/redylib_1.0.dev/gui/wc

as to the paths:

this line and the one below it are from the console Error: C:\Euphoria\redy\apps\RedyDemos_1.0.dev\..\..\redylib_1.0.dev\gui\themes.e:459

<0074>:: Errors resolving the following references:

the next two line are also from the console following the above line and are the first of many

..\.\redylib-1.0.dev\gui\wc\wc_canvas.e <151>: ScreenX

..\.\redylib-1.0.dev\gui\wc\wc_canvas.e <151>: ScreenY

do not know where this comes from: in the other messages ..\.\redylib-1.0.0.dev

-I C:\Euphoria\redy\redylib_1.0.dev\ 

19. Re: Redy 1.0.a1 released!

• Posted by buzzo Dec 17, 2014
• 3813 views

From the redy manual:

Each application folder will have at least two files:

eu.cfg (appname).exw or (appname).ex

The "eu.cfg" file tells the Euphoria interpreter where the redylib include files are. This file simply contains one line of text pointing to the folder name with the version number compatible with the application, such as:

-I ..\..\redylib_1.0.dev

Simply execute the main file (appname).exw or (appname).ex to run the application (use the eui or euiw interpreter.)

I changed eu.cfg to:

-I C:\Euphoria\redy\redylib_1.0.dev

and obtained the same results when running "basic_window.exw"

Console Error Message:

C:\Euphoria\redy\redylib_1.0.dev\gui\themes.e:459

<0074>:: Errors resolving the following references:

..\..\redylib_1.0.dev\gui\wc\wc_canvas.e (151): ScreenX

..\..\redylib_1.0.dev\gui\wc\wc_canvas.e (151): ScreenY

..\..\redylib_1.0.dev\gui\wc\wc_canvas.e (158): rgb

..\..\redylib_1.0.dev\gui\wc\wc_canvas.e (303): ScreenX

..\..\redylib_1.0.dev\gui\wc\wc_canvas.e (303): ScreenY

..\..\redylib_1.0.dev\gui\wc\wc_canvas.e (305): ScreenX

..\..\redylib_1.0.dev\gui\wc\wc_canvas.e (305): ScreenY

..\..\redylib_1.0.dev\gui\wc\wc_canvas.e (311): ScreenX

..\..\redylib_1.0.dev\gui\wc\wc_canvas.e (311): ScreenY

..\..\redylib_1.0.dev\gui\wc\wc_canvas.e (425): Normal

..\..\redylib_1.0.dev\gui\wc\wc_canvas.e (486): Bold

..\..\redylib_1.0.dev\gui\wc\wc_canvas.e (487): rgb

..\..\redylib_1.0.dev\gui\wc\wc_canvas.e (745): Normal

..\..\redylib_1.0.dev\gui\wc\wc_canvas.e (773): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (153): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (155): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (189): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (191): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (308): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (310): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (589): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (627): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (656): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (657): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (659): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (660): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (899): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (901): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (926): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (1328): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (1330): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (1360): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textedit.e (1391): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (130): rgb

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (175): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (177): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (659): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (661): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (696): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (698): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (819): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (821): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1181): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1218): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1219): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1221): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1222): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1519): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1521): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1544): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1546): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1773): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1775): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1807): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1827): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1887): Normal

..\..\redylib_1.0.dev\gui\wc\wc_textbox.e (1940): Normal

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (96): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (97): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (98): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (99): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (100): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (102): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (103): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (104): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (105): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (106): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (108): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (109): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (110): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (111): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (112): rgb

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (114): rgb

and so on......

..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (115): rgb ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (116): rgb ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (117): rgb ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (118): rgb ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (120): rgb ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (121): rgb ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (122): rgb ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (123): rgb ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (124): rgb ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (399): Normal ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (660): rgb ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (667): rgb ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (686): Bold ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (694): Normal ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (702): Normal ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (935): Normal ..\..\redylib_1.0.dev\gui\wc\wc_fancylist.e (963): Normal ..\..\redylib_1.0.dev\gui\wc\wc_listbox.e (421): Normal ..\..\redylib_1.0.dev\gui\wc\wc_listbox.e (487): Normal ..\..\redylib_1.0.dev\gui\wc\wc_listbox.e (501): rgb ..\..\redylib_1.0.dev\gui\wc\wc_listbox.e (526): Normal ..\..\redylib_1.0.dev\gui\wc\wc_listbox.e (604): rgb ..\..\redylib_1.0.dev\gui\wc\wc_listbox.e (856): Normal ..\..\redylib_1.0.dev\gui\wc\wc_listbox.e (884): Normal ..\..\redylib_1.0.dev\gui\wc\wc_treebox.e (420): Normal ..\..\redylib_1.0.dev\gui\wc\wc_treebox.e (449): Normal ..\..\redylib_1.0.dev\gui\wc\wc_treebox.e (504): rgb ..\..\redylib_1.0.dev\gui\wc\wc_treebox.e (511): rgb ..\..\redylib_1.0.dev\gui\wc\wc_treebox.e (541): rgb ..\..\redylib_1.0.dev\gui\wc\wc_treebox.e (547): Normal ..\..\redylib_1.0.dev\gui\wc\wc_treebox.e (768): Normal ..\..\redylib_1.0.dev\gui\wc\wc_treebox.e (803): Normal ..\..\redylib_1.0.dev\gui\wc\wc_option.e (219): Normal ..\..\redylib_1.0.dev\gui\wc\wc_option.e (453): Normal ..\..\redylib_1.0.dev\gui\wc\wc_toggle.e (207): Normal ..\..\redylib_1.0.dev\gui\wc\wc_toggle.e (438): Normal ..\..\redylib_1.0.dev\gui\wc\wc_button.e (163): Normal ..\..\redylib_1.0.dev\gui\wc\wc_button.e (288): Normal ..\..\redylib_1.0.dev\gui\wc\wc_button.e (310): Normal ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (140): rgb ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (144): rgb ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (149): rgb ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (154): rgb ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (160): rgb ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (167): rgb ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (170): Normal ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (187): rgb ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (188): Normal ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (207): rgb ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (219): rgb ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (225): rgb ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (231): rgb ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (234): rgb ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (299): Normal ..\..\redylib_1.0.dev\gui\wc\wc_progress.e (331): Normal ..\..\redylib_1.0.dev\gui\wc\wc_toolbar.e (70): Normal ..\..\redylib_1.0.dev\gui\wc\wc_toolbar.e (134): COLOR_WINDOW ..\..\redylib_1.0.dev\gui\wc\wc_toolbar.e (135): COLOR_BTNTEXT ..\..\redylib_1.0.dev\gui\wc\wc_toolbar.e (148): rgb ..\..\redylib_1.0.dev\gui\wc\wc_toolbar.e (149): rgb ..\..\redylib_1.0.dev\gui\wc\wc_toolbar.e (152): COLOR_BTNFACE ..\..\redylib_1.0.dev\gui\wc\wc_toolbar.e (154): COLOR_WINDOW ..\..\redylib_1.0.dev\gui\wc\wc_toolbar.e (156): COLOR_BTNTEXT ..\..\redylib_1.0.dev\gui\wc\wc_toolbar.e (160): COLOR_BTNSHADOW ..\..\redylib_1.0.dev\gui\wc\wc_toolbar.e (161): COLOR_BTNHIGHLIGHT ..\..\redylib_1.0.dev\gui\wc\wc_toolbar.e (163): COLOR_BTNHIGHLIGHT ..\..\redylib_1.0.dev\gui\wc\wc_toolbar.e (164): COLOR_BTNSHADOW ..\..\redylib_1.0.dev\gui\wc\wc_toolbar.e (188): Normal ..\..\redylib_1.0.dev\gui\wc\wc_menubar.e (179): Normal ..\..\redylib_1.0.dev\gui\wc\wc_menubar.e (186): Normal ..\..\redylib_1.0.dev\gui\wc\wc_menubar.e (358): Normal ..\..\redylib_1.0.dev\gui\wc\wc_container.e (259): Normal ..\..\redylib_1.0.dev\gui\wc\wc_container.e (458): Normal ..\..\redylib_1.0.dev\gui\wc\wc_list.e (248): rgb ..\..\redylib_1.0.dev\gui\wc\wc_list.e (281): Normal ..\..\redylib_1.0.dev\gui\wc\wc_menu.e (100): Normal ..\..\redylib_1.0.dev\gui\wc\wc_menu.e (306): Normal ..\..\redylib_1.0.dev\gui\wc\wc_menu.e (307): rgb ..\..\redylib_1.0.dev\gui\wc\wc_menu.e (313): Normal ..\..\redylib_1.0.dev\gui\wc\wc_menu.e (338): Normal ..\..\redylib_1.0.dev\gui\wc\wc_menu.e (355): Normal ..\..\redylib_1.0.dev\gui\wc\wc_window.e (94): rgb ..\..\redylib_1.0.dev\gui\wc\wc_window.e (246): rgb ..\..\redylib_1.0.dev\gui\themes.e (125): rgb ..\..\redylib_1.0.dev\gui\themes.e (126): rgb ..\..\redylib_1.0.dev\gui\themes.e (127): rgb ..\..\redylib_1.0.dev\gui\themes.e (128): rgb ..\..\redylib_1.0.dev\gui\themes.e (129): rgb ..\..\redylib_1.0.dev\gui\themes.e (132): rgb ..\..\redylib_1.0.dev\gui\themes.e (133): rgb ..\..\redylib_1.0.dev\gui\themes.e (134): rgb ..\..\redylib_1.0.dev\gui\themes.e (135): rgb ..\..\redylib_1.0.dev\gui\themes.e (136): rgb ..\..\redylib_1.0.dev\gui\themes.e (137): rgb ..\..\redylib_1.0.dev\gui\themes.e (138): rgb ..\..\redylib_1.0.dev\gui\themes.e (139): rgb ..\..\redylib_1.0.dev\gui\themes.e (142): rgb ..\..\redylib_1.0.dev\gui\themes.e (144): rgb ..\..\redylib_1.0.dev\gui\themes.e (146): rgb ..\..\redylib_1.0.dev\gui\themes.e (147): rgb ..\..\redylib_1.0.dev\gui\themes.e (149): rgb ..\..\redylib_1.0.dev\gui\themes.e (150): rgb ..\..\redylib_1.0.dev\gui\themes.e (152): rgb ..\..\redylib_1.0.dev\gui\themes.e (153): rgb ..\..\redylib_1.0.dev\gui\themes.e (155): rgb ..\..\redylib_1.0.dev\gui\themes.e (156): rgb ..\..\redylib_1.0.dev\gui\themes.e (158): rgb ..\..\redylib_1.0.dev\gui\themes.e (159): rgb ..\..\redylib_1.0.dev\gui\themes.e (162): rgb ..\..\redylib_1.0.dev\gui\themes.e (163): rgb ..\..\redylib_1.0.dev\gui\themes.e (164): rgb ..\..\redylib_1.0.dev\gui\themes.e (166): rgb ..\..\redylib_1.0.dev\gui\themes.e (167): rgb ..\..\redylib_1.0.dev\gui\themes.e (168): rgb ..\..\redylib_1.0.dev\gui\themes.e (170): rgb ..\..\redylib_1.0.dev\gui\themes.e (171): rgb ..\..\redylib_1.0.dev\gui\themes.e (172): rgb ..\..\redylib_1.0.dev\gui\themes.e (174): rgb ..\..\redylib_1.0.dev\gui\themes.e (175): rgb ..\..\redylib_1.0.dev\gui\themes.e (176): rgb ..\..\redylib_1.0.dev\gui\themes.e (178): rgb ..\..\redylib_1.0.dev\gui\themes.e (179): rgb ..\..\redylib_1.0.dev\gui\themes.e (180): rgb ..\..\redylib_1.0.dev\gui\themes.e (184): createMousePointer ..\..\redylib_1.0.dev\gui\themes.e (207): createMousePointer ..\..\redylib_1.0.dev\gui\themes.e (240): createMousePointer ..\..\redylib_1.0.dev\gui\themes.e (263): createMousePointer ..\..\redylib_1.0.dev\gui\themes.e (286): createMousePointer ..\..\redylib_1.0.dev\gui\themes.e (309): createMousePointer ..\..\redylib_1.0.dev\gui\themes.e (332): createMousePointer ..\..\redylib_1.0.dev\gui\themes.e (355): createMousePointer ..\..\redylib_1.0.dev\gui\themes.e (378): createMousePointer ..\..\redylib_1.0.dev\gui\themes.e (401): createMousePointer ..\..\redylib_1.0.dev\gui\themes.e (434): createMousePointer ..\..\redylib_1.0.dev\gui\themes.e (436): createMousePointer ..\..\redylib_1.0.dev\gui\themes.e (459): createMousePointer

mLink = createMousePointer(7, 0, { ^

Press Enter

21. Re: Redy 1.0.a1 released!

• Posted by DerekParnell (admin) Dec 17, 2014
• 3656 views

Good. Eliminated one potential issue.

I now suspect that the "unresolved" identifiers happen because these names are declared in more than one included file and Euphoria doesn't know which of them your program needs.

23. Re: Redy 1.0.a1 released!

• Posted by system_X Dec 17, 2014
• 3623 views

buzzo: What version of Euphoria are you using and 32 or 64 bit?

25. Re: Redy 1.0.a1 released!

• Posted by ryanj Dec 17, 2014
• 3612 views

Oops, i thought i stated this, but i should have been more clear. The above source code showing the textedit demo won't work for you, it was merely a snippet of what I am currently working on for the next release. Sorry for the confusion.

27. Re: Redy 1.0.a1 released!

• Posted by buzzo Dec 17, 2014
• 3637 views

I have not tried to run the textedit demo...

29. Re: Redy 1.0.a1 released!

• Posted by ryanj Dec 17, 2014
• 3631 views

You shouldn't have to change the relative path, as long as your redy files are in the correct place (they should be, just by unzipping the redy zip file into the C:\redy folder).

I wonder if there is something different about your euphoria installation. If you have a default installation of Euphoria 4.0.5 or 4.1 beta, it should work. I wish I knew how to help you with this problem, it is a mystery to me.

I am not an expert on how Euphoria configuration works, but I created the eu.cfg files based on what read in the Euphoria manual: http://openeuphoria.org/docs/installing_euphoria.html#_34_windows, http://openeuphoria.org/docs/configuration.html#_48_setuptheeuphoriaconfigurationfileeucfg and http://openeuphoria.org/docs/command_switches.html#_76_commandlineswitches.

31. Re: Redy 1.0.a1 released!

• Posted by buzzo Dec 18, 2014
• 3577 views

Both boxes eu 4.0.5 and win 7 home 32 bit..

33. Re: Redy 1.0.a1 released!

• Posted by BRyan Dec 18, 2014
• 3562 views

buzzo:

I don't know any thing about redy's software or code.

Windows 7 is different than xp.

Maybe this may have something to do with your problem.

http://windows7supportnow.com/windows-help-2/troubleshooting-the-ntvdm-exe-error

35. Re: Redy 1.0.a1 released!

• Posted by buzzo Dec 19, 2014
• 3397 views

Still attempting to debug my install...

results stll as outlined in reply 19, above.

has anyone installed redy and have it running ?

Buzzo

37. Re: Redy 1.0.a1 released!

• Posted by buzzo Dec 19, 2014
• 3390 views

Anyone successful running on win 7 home premium ???

39. Re: Redy 1.0.a1 released!

• Posted by ryanj Dec 20, 2014
• 3486 views

I don't know what to tell you. It has been tested by a few people on several versions of Windows and even WINE on Linux and I haven't heard of any problems from anyone else, except that it fails on the 64-bit version of Euphoria because of 64-bit pointers/handles not being handled correctly. I have tested it on Euphoria 4.0.5 and 4.1 beta (32bit), on Windows XP SP3, Vista Home Premium 32-bit, and Windows 7 64-bit, and haven't had any problems like that. Maybe you did something out of the ordinary in your Euphoria installation?

In the next release of Redy (in a few weeks) i'm going to clean up some stuff, and be more strict about public/export declarations, and namespaces. Maybe that will decrease the chances of include/declaration problems.

41. Re: Redy 1.0.a1 released!

• Posted by ChrisB (moderator) Dec 20, 2014
• 3354 views

Have you tried turning user account control off

http://windows.microsoft.com/en-gb/windows/turn-user-account-control-on-off#1TC=windows-7

Chris

43. Re: Redy 1.0.a1 released!

• Posted by buzzo Dec 20, 2014
• 3259 views

Permissions OK..

If I set EUDIR %EUDIR% C:/Euphoria and EUINC %EUINC% C:/Euphoria/include then none of the programs run.

I receive an error message informing that the includes can not be found when runing win32Lib demos.

If remove Eenvironment vars, the demos run fine..

45. Re: Redy 1.0.a1 released!

• Posted by ryanj Dec 20, 2014
• 3241 views

Does that mean Redy is working now?

47. Re: Redy 1.0.a1 released!

• Posted by ryanj Dec 20, 2014
• 3296 views

Update:

I am making good progress on the textedit.e library. It can now draw text with line numbers, and bookmark/code folding indicators. Word wrapping works, and readjusts when the canvas is resized. The display works correctly even if i change the font size, paragraph spacing, and line spacing. The next step is to get selecting/editing to work, which will require a lot of work.

This library uses what i call "tokens" to do word wrapping, syntax highlighting, and formatted text. A token is like a word of text, except it may not be a "word" in the English sense. It is a string of white space, punctuation, alphanumeric, etc. Each paragraph is broken up into tokens by the syntax parser, and each token has it's own position, size, font style, color, etc. Each paragraph also has a position and size, so when text needs to be drawn, edited, selected, etc. the paragraphs and tokens will be scanned and updated, only applying changes to ranges that actually changed, or drawing only tokens that are inside the area that need to be redrawn. I am using this technique because it seems to make it easier to add lots of features in a structured way, and i believe it will be efficient for large files (this will have to be verified once the library is complete).

Because every token has position and size pre-calculated, it makes it easier to determine which one the mouse is over, and to make the viewing area jump to the right position to show a token (for find/replace, goto line number, goto bookmarked line, goto line that has the error, etc.) Each token will be assigned a type, such as ttWhiteSpace, ttIdentifier, ttKeyword, ttNumber, ttSymbol, etc. and different types can be different text styles and have different behavior when you are typing, such as poping up different auto-complete options or help info.

Here is a screenshot. Notice the debugging rectangles, which show the outline of each paragraph and token. At this point, it won't be difficult to add syntax highlighting, formatted text (different fonts and sizes), justification, line spacing, paragraph spacing, indentation, etc. This will be useful for not just code editing, but displaying basic html/creole as formatted text.

49. Re: Redy 1.0.a1 released!

• Posted by ryanj Jan 18, 2015
• 3074 views

Update:

I have been working on the gui/objects/textedit.e library. Wordwrap and Euphoria syntax highlighting works now! It can update syntax colors on-the-fly. I still need to fix some bugs before it can be a useable text editor. I am also working on the general design of the RedyCode IDE. I will release more information soon.

51. Re: Redy 1.0.a1 released!

• Posted by SDPringle Jan 18, 2015
• 3019 views

This looks inviting enough to try out using Wine.

53. Re: Redy 1.0.a1 released!

• Posted by K_D_R Jan 19, 2015
• 3036 views

Redy 1.0a1 runs under Wine on Ubuntu 14.10

55. Re: Redy 1.0.a1 released!

• Posted by ryanj Jan 20, 2015
• 2856 views

Thanks for all the Linux how-tos. Perhaps some of this stuff you guys posted could be put into a wiki page. Actually, even though i'm not a "linux guru", i have used various distros over the years, and i do know how to do dual boot. I have even built a 12-core Opteron server with SAS drives and ECC ram, running Ubuntu Linux server with no GUI, used at work as a file, database, and intranet server. I plan to build a linux workstation at home, i just haven't had time or money to do it yet.

The reason i haven't ported Redy to linux yet isn't because of the lack of a linux machine, but a lack of time and knowledge about the x-window system. System_X was trying to get a generic XCB wrapper working, but has been having problems. I am too busy with my day job plus i have so much stuff to work on to finish Redy 1.0, so i just don't have time to mess with porting to linux right now.

Because Redy has it's own widget system, all it needs is basic window manipulation, event handling, and graphics routines. It seems like XCB would be the best choice. Let me emphasize, Redy does not need a complete widget toolkit, because Redy itself includes a widget toolkit, written in pure Euphoria source code! That means, i do not need or want to use GTK, wxWidgets, Qt, etc. I just need a raw x-windows or XCB and/or svgalib wrapper. If someone could get something like that working, then i would have a place to start with getting Redy to work on linux.

57. Re: Redy 1.0.a1 released!

• Posted by ryanj Jan 21, 2015
• 2788 views

After i posted that, i remembered i had seen something about svgalib in the eu archive in the past. Once i get a linux machine (real or virtual) set up, i should try it. It would be useful for making a full-screen GUI and desktop environment for RedyOS (Bare-minimum Linux + Euphoria + Redy). The purpose would be to have a very simple low-power embedded computer used for dedicated applications. The ARM version of Euphoria could be very useful for this.

59. Re: Redy 1.0.a1 released!

• Posted by ryanj Jan 21, 2015
• 2754 views

<cough>

Try to be concise

Get to the point! Stay on topic! Start new topics if you must.

</cough>