FASM insideFreshFASM inside

flat assembler visual programming IDE

Flat assembler | Message board

Important: Recently, the source repository of the project was moved from chiselapp.com to the Fresh home site.

Please, if you have local clones of the repository, update your remote-url following way:

fossil remote-url http://fresh.flatassembler.net/fossil/repo/fresh

Introduction

Hi. This is the home page of the project "Fresh".

Fresh is a visual assembly language IDE with built-in FASM assembler.

The project is free and open source, distributed under the terms of the EUPL 1.1 and other licenses.

The main goal of Fresh is to make programming in assembly as fast and efficient as in other visual languages, without sacrificing the small application size and the raw power of assembly language.

Because Fresh is the logical continuation of the FASM project in the area of visual programming, it is perfectly compatible with FASM and you can use all your knowledge about FASM to program in Fresh.

Of course, you can use Fresh not only for Windows programming, but also to create programs for any OS that FASM supports - DOS, Linux, FreeBSD, BeOS, MenuetOS - the same way as you do this in FASM.

Currently, the development is shifted mainly on FreshLib, that will be the base for the next generation of Fresh IDE 3 - highly portable IDE with advanced visual editing architecture, that to provide OS independence for the developed applications.

The road map of the project is planed following way:

The versions 2.x.x will still be Win32 only application. But you still can use Fresh IDE in Linux - check the Setup manual in the Documantation folder for details.

Another good reading is "Tips and tricks" article, where you can learn how to use the full potential of the IDE.

Fresh IDE v3.0.0 will be freely portable for all operating systems supported by FreshLib. For now they seems to be Windows, Linux and KolibriOS.

How to contribute?

If you like this project, you can help the project to reach its goals. How?

There are many things that have to be done in such a big project. As long as the main effort now is directed to the development of FreshLib, this is the area where more help is needed.

At first, FreshLib needs some extensive testing, probably provided by some automated test suit. The library is pretty big now and such a tool will help to keep the bugs out of the code. Writing such a tool would be a huge contribution to the project.

At seconds, FreshLib needs some common GUI widgets to be created in order to be useful for serious programming and porting of Fresh IDE. Toolbars, tree-view, list-view, combo and list boxes, etc. Creating of every particular widget is relatively easy, but they are too many for a single programmer.

Writing new libraries: FreshLib needs more data processing libraries. As long as FreshLib has open architecture, there is no limits on the included libraries. They only have to conforms to the FreshLib design principles in order to be flawlessly integrated in the whole. If you have some library idea, you can implement it as a part of FreshLib.

Last modified on: 13.04.2013 18:57:27

[X]
Title: