Hi all.

These days I work on new project manager for Fresh. I made (still unpublished and unfinished) changes in Fresh to make one common interface for different editors (source editor, forms editor, different resource editors etc.). Now I want to implement this interface in the Project manager (that is in fact editor for .fpr files). So, as long as the present variant of Project manager works with not so good "fixed layout" I decided to create new style/layout/behaviour for it.
The problem is that there are several variants (and actually I don't like any of them )

I will atach in this post the latest work Fresh.exe with implemented two of these variants, so you can see them. Note that this version have a lot of bugs and can't actually work.

1. Present variant: Tree view control. Fixed layout (Main file, Forms, Includes... etc.) - you all know it.

2. Auto detecting the dependencies tree: I tryed this variant and it works pretty well. You give to project manager the name of the main file and it scans the tree of includes and create the Treeview layout to match it.
The problem is that the list of files become very unreadable and hard for search. Also, corresponding ASM(code) and INC(equates) files resides on different places in the list.
(You can try it with: File|"Open project" and then select Fresh.asm (not Fresh.fpr) )

3. Creation of the tree-view layout to follow the real disk directory/file tree.
Implemented in the below .exe when you open .FPR files (not "open project" but "Open file" with Fresh.fpr file.)

4. User customizeable "categoies" - It is only an idea. I am still not implemented it. The idea is to make some kind of "User categories", so everyone will have the ability to create "groups" whatever he wants.
(Maybe something like "Bookmarks" structure in web browsers.)

Also, when I think about advanced schemes for the project manager, almost all ideas tends to lead to big window with look and feel like windows explorer - i.e. folders in treeview on the left and listview for files on the right. But it is imposible to be implemented in such small window as now - so, maybe I should make it as "popup" window that to be shown with some hot-key and/or toolbar button.

Any opinions about these ideas and more generally about most comfortable navigation in big complex projects, will be highly appreciated.

Regards.

[edit] Outdated file removed.[/edit]

My classification:

1. Context menu from right click and with dblclick for default go to proc/macro/struc definition and the possibility to return back (very asm way to do it)
2. Tree-view created from a mix of your 2 and 3 and then alphabetically sorted within each subdirectory.
3. Functions in property window ala "RadAsm".

Make a poll!

Hi, pelaillo.

About context menus, "goto definition" etc. - I am fully agree, bu this is navigation in the source - "source editor" is responsible for such things. (and they will be implemented very soon)
Project manager should make navigation between different files in the project.



What you actually mean - my 2 and 3 are quite incompatible, so any mix seems for me imposible. Or you mean to implement them both and live the user to choose?

Regards.

No, what I mean is to read through include files using the relative path from the main file to populate the treeview. However, source included order is mandatory.

i.e. suppose you have included a "gui.inc" that calls several gui element definitions separated into several directories for simplicity (or for versioning), so you will have:

fresh.asm
gui.inc
bmp\
gif.inc
jpg.inc
manip.inc
text\
editbox.inc
combo.inc

...