Re: RedyCode alpha almost ready!
- Posted by ryanj Nov 08, 2015
- 2010 views
One option could be that the LHS Tree becomes a simple list of filenames (maybe a copy or replacement for tabs along the top). This make for a "low visual clutter" option.
I was thinking about that, too. I don't necessarily like tabs at the top, that just seems to be a common way to do things. I could add an option to have a list of open files on the side instead.
The project file should have an easily edited list of files.
I figured it would be nice to have a "project tree" that is fully automated, not manually created. I understand that a generic text editor should have an editable project tree, but i am leaning towards making RedyCode more specific to building Redy GUI applications, following a specific set of standards, rather than making it a generic code editor. RedyCode will be very automated and have lots of visual assistance such as GUI layout editor, smart include and routine assistance while typing, etc. A RedyCode project would be defined as:
- a folder that contains a .redy file that defines the project properties
- at least one .ex, .exu, or .exw file to be the main eu source file
- additional source, config, or data files, or subfolders
RedyCode would scan the project folder and simply build a "Source" tree based on the existing files. The "Includes" tree would be based on what include paths are set up for the project. By default, that would mean the "stdlib" and "redylib" folders, but others could be added as well. Those are just there for convenience. They are not actually part of the project, just referenced by it.
RedyCode is based on the textedit.e library included in redylib. That library could be used to make another text editor with different design goals, such as a web development editor or generic code editor.
However, i would be happy to discuss this further. Nothing is set in stone at this point. It is highly experimental right now.
The project files should have a "user sort order" in addition to the natural tree order.
That is a good suggestion, unfortunately, the treebox widgetclass doesn't have the ability to allow dragging nodes to to positions yet, nor does it have the ability to define right-click popup menus for tree nodes yet. Those features are on my very long redylib todo list...
As it is, it looks good.
I appreciate the feedback, _tom.
I plan to upload the source code in a few days so people can try it.