I like the SMP interface and being able to set up all my projects in one place. You can do that with Sublime as well (see below), but the UI is really clunky.

But it’s a no go for me if SMP doesn’t preserve the the view between session (as the default project system does via the workspace files). I’m don’t know if you can tap into the workspace system via the API. There’s a lot of really useful stuff you lose when you ditch the workspaces: remembering buffers, the build system, history for autocomplete, console, GoTo and more.

It takes your plugin elsewhere and you may not want to do this at all, but it seems to me that SMP (or something like it) can server as an interface to the project system (which would automatically take care of the workspaces as well). In terms of configuration, instead of having one file you would have a directory with a file for each project (User/SMP/Whatever.sublime-project). That would allow you to use the project system as-is, but simplify the user’s interaction with it.

Or am I not seeing this right?

Alex

Thanks your for your comments. I agree that it is a big loss for not being able to use the workspaces. When I first developed SPM, I also had an idea of putting all *.sublime-project and *.sublime-workspace files under a directory and let SPM manages it. Some how, I gave up this idea and chose to use a configure file.

There are advantages solid advantages of keeping the *.sublime-workspace files together with their sublime-project files. I just try to modified some code to demonstrate this idea. It turns out this approach is quite workable. SPM stands for SIMPLE project manager. It is time for an non-simple project manager.

Fair enough. Unfortunately it’s back to the default for me

Alex

I have written another package: Project Manager, github.com/randy3k/Project-Manager

It is essentially a duplicate of SPM, but with the support of workspace files. It is appreciated if you can help testing it out and give some feedbacks.
Now, the sublime-project and sublime-workspace files are stored under /User/Projects/. And Project Manager helps in organizing the two files.

You’re a machine!

For my devious purposes, this looks more useful than SMP. I’ll be able to test it more thoroughly over the weekend.

Some things I noticed:

• One of my concerns with SMP is how I would deal with multiple paths (on different computers). In SMP you provide the “path_*” setting, which doesn’t to seem to work in PM. (Because you’re using vanilla project files, presumably.) Because my User folder and most of my projects live in Dropbox I can use relative paths like “…/…/…/…/…/…/Project Folder/”, but I’m sure I’ll run into trouble eventually. Any ideas about this?

• I missed the rename option from SMP.

• As with SMP, project configuration is not instantly picked up – which, honestly, I only noticed because I’m fiddling with the settings for testing purposes

Alex

Now, it is not quite possible to use “path_*” setting as the contents of sublime-project files are never touched. I can’t think of a way to support it now except having multiple files…

Just add it.

Perhaps, reloading the settings can be triggered when the sublime-project is saved. One dirty trick for the moment is to reopen the project again. Since the workspace is used, your open files and unsaved work will not be discarded.

[quote=“randy3k”]
Just add it.[/quote]

?

[quote=“quodlibet”]

?[/quote]

You should now see an option

2qxp0ls.jpg639×506 39.9 KB

OK, sorry. Package Control didn’t pick up the update. I had to reinstall the package for some reason.

BTW, renaming projects is not as straight-forward as renaming the .sublime-project file. There’s also a reference in the .sublime-workspace file that needs to be changed. Otherwise it throws up an error. (And there may be more complexity to this. I didn’t have a chance to fiddle too much.)

Ah, where are the good ol’ days of the Simple Project Manager?

Alex

I just installed it and really quite like it. Thank you very much for the plugin!

[quote=“quodlibet”]OK, sorry. Package Control didn’t pick up the update. I had to reinstall the package for some reason.

BTW, renaming projects is not as straight-forward as renaming the .sublime-project file. There’s also a reference in the .sublime-workspace file that needs to be changed. Otherwise it throws up an error. (And there may be more complexity to this. I didn’t have a chance to fiddle too much.)

Ah, where are the good ol’ days of the Simple Project Manager?

Alex[/quote]

The corresponding changes in the sublime-workspace file has already been made.
github.com/randy3k/Project-Mana … pm.py#L134

I trashed my SPM files…SPM is just deprecated.

I’ve been quite happy with Project Manager thus far, though the paths issue is a bit a of a problem. It occurred to me that perhaps we’ve been thinking about this backwards. It might be more optimal to keep the project and workspace files within the project’s folder hierarchy and then keep an index of the projects in the User folder. That way you could define computer-specific paths in this custom index to the vanilla project files.

What do you think?

I start to believe that different sublime-project files should be used for the same project even on different platforms. May be I am wrong, but anyway, storing platform dependent settings in a single sublime-project file is difficult.

I’ve had some trouble with project build system across OSs. But the other settings would be identical, no?

Also, GitHub’s recommended gitignore settings for Sublime Text – as close an industry standard as I’m aware of – recommends that “project files should be checked into the repository, unless a significant proportion of contributors will probably not be using SublimeText”

github.com/github/gitignore/blo … nore#L9-11

So maybe including the project files in the within the project root and keeping the custom index of projects in User is the way to go. The benefit is your nicer UI, path settings, while maintaining compatibility with the buffoons who don’t use PM

Sorry for the long delay…I didn’t check this forum regularly. (side note: why still using phpbb??? it is so vintage…)

Perhaps, we could copy the local .sublime-project to /Users/Projects/ based on the modified time.
(Are github staff forced to use atom!? )

Yeah. Would you prefer if I open an issue an GitHub? I just didn’t want to make it sound like a demand or anything.

But I think leaving the project and workspace files within the appropriate projects and creating an index under User that PM relies on to locate them would solve all issues. And possibly bring about world peace. (But I could be wrong about this last one.)

Is there something you’re worried about this scheme?

Atom is interesting. I was jealous when it first came out in OSX, as I’m a Linux user by choice and Windows user at work. But even now that has been released for other platforms, I haven’t even tried it (though I will, at some point). I really like Sublime, warts and all.

I’m currently on the market for a CMS for a small project and I’m looking into Statamic, because it’s a flat file CMS. Which, basically, translates into spending more time in Sublime while building the site. I’m that sad

I finally have some time to implement this “import” feature. Have a look of the latest github commit. It should do what you are expecting.

Cool. This is probably the better way of doing it. Given your implementation there might be an issue with paths on different machines. It’s hard to tell because I had my two other laptops stolen a few weeks ago. (They were old and crappy but I hadn’t backed up some data in ages )

I’ll let you know how it goes once I transition my projects to the library.json system.

Oh, and it’s not that hard to figure out, but you should probably add a note to the README about where users can locate their projects.

P.S. I’m really tired of this forum. I even wrote a strongly-worded email to Sublime HQ about it

Sorry to hear that your laptop was stolen.

There are certainly some issues with paths on different machines. I am thinking a machine specified projects directory.
Perhaps something like

Packages/User/Projects/Machine1/
Packages/User/Projects/Machine2/

Project Manager will read both Packages/User/Projects/ and Packages/User/Projects/Machine1/