I've begun thining of the idea, what about making Fresh to be runnable under linux too (not in wine but native). I've seen many projects (like fasm, jGRASP (java but anyways)) that have multi OS capabillities, the same core code but different OS specific code.
The ide is basically, make an internal wrapper API (like "proc open_file, file" which just opens the file an retruns some kind of hadle that works with the function "read_file", "write_file", "get_fileinfo", etc), or use an existing wrapper API, and then like fasm have dirs for win32 and linux (and possible more platforms later) "end code".
By doing this we'd IMO create an superior fasm IDE for both linux and windows (with respect to privalovs fasmw which is the original IDE - and the base), what do you all say about it? (is it just me who have the idea or are there others that share my idea)

I like your idea scientica I think linux needs an IDE more then windows does or maybe its just that the linux guys are not IDE fans. I think it would have been nice if you came up with this idea before the fresh project began because I suspect it would be a monstrous amount of work for the fresh developers to make the IDE portable. Anyway we'll just have to wait and see what JohnFound and the others think about it.

The idea is good, but IMO we should wait... too many parts of Fresh is based on windows-specific functions, messages, etc. I don't know how does it work in linux but i think that too many code would have to be modified. But making Fresh portable should be in todo list IMO.
And let's wait for John's opinion

Hi all.

Well, it is tempting idea. But there are several problems:
1. The main Fresh structure is still not clear and it is changed too often.
2. The sturcture of the Fresh visual created project is very Windows specific. In Linux it have to be different, because we don't have to force users of Fresh to overbloat theirs code with wrapper libraries.
3. Wrapper functions that make Fresh OS independent probably will overbloat the code of Fresh too, but I don't want this.

IMHO, the proper approach in this case is to wait until Fresh have almost clear structure (maybe after version 2.0) and to begin Linux porting from scratch. I know, it sounds awfully, but IMHO it is not so big deal, if developers (we) have good knowledge about Fresh and FASM internals.

Regards.

Ok, IMO we should continue to clear up the structure and try to make the code portable (like not using to much platfrom depended things). The wrapper libs I thiught of is just a set of functions that deals with low level thing like file I/O, Mem managment -- even for windows versions of Fresh a set of wrapper functions can be of use to aid in debugging (like keeping track of allocated resources which aren't released and such, understand what I mean?).
We need not make wrappers for the creation of buttons/dialogs, as they'll probably require a complete rewrite when porting to linux -- that would be overbloat.
Let's work and see where we end up . I just wanted to see if there was any interest in making a linux version, and it seems to me like there is - let's hope we're as interested (or more) in porting to linux when verison 2.0 is released.

Are there any news about Fresh porting for Linux/X11 after that time?