1.9 nonsense behavior with folders?

Glider (IDE)
#1

I don’t understand what was done with 1.9 with respect to folders.

When I try and open my projects from my NAS, all my folders are now a bight blue, and when I double click the folders to traverse deeper into them, instead LUA tries to load these folders as ‘projects’. Once these folders are open then there is no option to set which one is main project, as just the folder name shows up there which has nothing buy subfolders

For example

-NetworkDrive

  -Code Projects

     -Project 1

        main.lua

     -Project 2

        main.lua

     -Project 3

         main.lua

If I double click on NetworkDrive, then it loads the empty folder as if it were a project, and now it will only let me set this empty networkDrive as the ‘main project’ and when you hit run, of course it says no main.lua was found.

This behaviour makes no sense…why is 1.9 seeing enpty folders as projects? It used to show a glider icon on the folder when it was a project…now it seems to make almost every single folder a bright blue ‘project’ folder…

#2

Hello Sean,

Sorry for the confusion but there are specific reasons we did it this way.

  1. The new project manager feature allows you to select arbitrary folders (with resources in it) to merge in with your project at build-time. In this case it is easier to have all your folders open (ie image folder, sound folder, art folder, etc) in the projects view. This would not be possible if all folders are not considered a “project.”
  2. Note that there should be a collapsable in the open dialog that allows you to traverse deeper into the folder, double clicking will open the folder as a library project. Even better yet you can just drag and drop a folder from windows explorer into the editor view, this will also open the project. You can also dnd multiple folders and they will batch open. 
  3. When you open a project the root folder will be considered the working directory and all require statements will be relative to that folder
  4. The only other way to demarcate “library” projects from regular folders is to force you to add some sort of marker file. Perhaps an empty main.lua file, empty .proj file, __init__.lua? But this is even more inconvenient.

We will have videos describing the overall workflow soon. It might take some getting used to but it will allow you to see all your assets in the project view related to a particular product (project groups.) Refactoring reused stuff into libraries will also increase code reuse and improve maintainability.

Regards,

M.Y. Developers

#3

Well now that you explain it :) 

It makes sense of course. It is always hard to implement new features when we the user are used to a certain ‘behavior’ in the code and ‘resist’ the changes ! Thank you for the hard work, enjoying it!

#4

Hello Sean,

No problem, this gives us a good idea of the things to stress in our tutorials. How is the performance on the NAS btw? I hope the scanning does not take too long.

Regards,

M.Y. Developers

#5

Performance is good, of course when I first did it I click the top folder which contained maybe 50 projects, of course then it sits and indexes and indexes and indexes :slight_smile: But after that initial mistake, performance is good!

#6

Hello Sean84,

Thanks for the update. We are glad it is working well now. Please let us know if you come across more issues.

Regards,

M.Y. Developers

#7

Hello Sean,

Sorry for the confusion but there are specific reasons we did it this way.

  1. The new project manager feature allows you to select arbitrary folders (with resources in it) to merge in with your project at build-time. In this case it is easier to have all your folders open (ie image folder, sound folder, art folder, etc) in the projects view. This would not be possible if all folders are not considered a “project.”
  2. Note that there should be a collapsable in the open dialog that allows you to traverse deeper into the folder, double clicking will open the folder as a library project. Even better yet you can just drag and drop a folder from windows explorer into the editor view, this will also open the project. You can also dnd multiple folders and they will batch open. 
  3. When you open a project the root folder will be considered the working directory and all require statements will be relative to that folder
  4. The only other way to demarcate “library” projects from regular folders is to force you to add some sort of marker file. Perhaps an empty main.lua file, empty .proj file, __init__.lua? But this is even more inconvenient.

We will have videos describing the overall workflow soon. It might take some getting used to but it will allow you to see all your assets in the project view related to a particular product (project groups.) Refactoring reused stuff into libraries will also increase code reuse and improve maintainability.

Regards,

M.Y. Developers

#8

Well now that you explain it :) 

It makes sense of course. It is always hard to implement new features when we the user are used to a certain ‘behavior’ in the code and ‘resist’ the changes ! Thank you for the hard work, enjoying it!

#9

Hello Sean,

No problem, this gives us a good idea of the things to stress in our tutorials. How is the performance on the NAS btw? I hope the scanning does not take too long.

Regards,

M.Y. Developers

#10

Performance is good, of course when I first did it I click the top folder which contained maybe 50 projects, of course then it sits and indexes and indexes and indexes :slight_smile: But after that initial mistake, performance is good!

#11

Hello Sean84,

Thanks for the update. We are glad it is working well now. Please let us know if you come across more issues.

Regards,

M.Y. Developers