Hi,
I have been working with Espresso since the beta came out and I love it. The only concern I have is, that it will turn into something as useless as TextMate for working remotely. Now I have tried out the Update/Merge and Mirror features and they are great but sometimes it’s just not what one needs. I would like to be able to just work on a remote server without having to constantly exchange my files (just saving the remote file, nothing more). An external FTP app slows the production process down dramatically. Can we expect a feature like that in Espresso 1.0?

Thanks,
Max

Agree, I use CODA and has this feature and this is important for a fast development.

Yeah thats one feature I’d love to see. I really dig Coda’s “Mark for Publishing” then “Publish All” features. Although we don’t want to just copy them But its a really great way to do it.

One good thing about Espresso’s method is that it promotes a safer/better workflow. Eg. you don’t have older versions on your local copy, edit it remotely, then overwrite those changes when you upload the whole site again. I generally try to steer away from editing remotely, as it can cause all sorts of issues.

I think Espresso should learn from what Coda did right with its approach to remote files. A blend of Espresso’s ftp features and Coda’s would be awesome.

I think you should be able to drag remote files to the “workspace” (in the source list) to edit them. This currently crashes Espresso for me but hopefully that’ll be fixed.

I also need the ability to edit files remotely.  At least two of the projects I’m currently working on are remote access only (I don’t keep local copies since I’m just doing minor interface modifications and the projects are quite large).  Coda’s ability to log into both FTP and SSH terminal and allow me to edit the files remotely and do an SVN commit for them on the remote server is fantastic.

I definitely need to be able to work remotely.  It is one of the two things I need painfully.  The other being an editor as good as textmate.

I’m just going to throw in my negative here.

Not that I don’t think it’d be a feature that’s great for a lot of people! It will, as evidenced by the replies to this thread.

But at this point, I really hope Espresso development will stay focused on the Sugar API (be it Cocoa, XML, shell scripts, or Ruby). After all, you need some functionally complete Sugars to be released at the same time as Espresso, to really ride the 1.0 wave to best effect.

And I’ll throw my double-negative in here (or is that a positive?):

The lack of seamless remote working capabilities is what frustrates me most with Textmate.  It’s only the editor there which keeps me using it.  If there was something in the market with as sweet an editor, and remote working capabilities, then I would be completely sold.

I’ll throw my double positive in here:

Espresso needs both Sugar APIs and remote editing. They’re both extremely important features (and not mutually exclusive).

And I’ll raise you a triple positive here.  You are 100% correct sir!  I only howl about the remote working, because the sugar development seems to be coming along quite nicely.

alexgordon - 18 December 2008 04:52 PM

I’ll throw my double positive in here:

Espresso needs both Sugar APIs and remote editing. They’re both extremely important features (and not mutually exclusive).

Yes, it does. But not *right now*. I’d guess that ninety percent of Espresso’s features are not provided in the Sugar-developer preview releases that we’re seeing. Espresso may already *have* remote-editing functionality, and if it doesn’t, Jan will probably be open to adding it. I’m just saying that that’s not something that needs to be worried about for then (read my next words carefully) Sugar-developer-specific preview releases. Get my point?

elliottcable - 18 December 2008 04:54 PM

Yes, it does. But not *right now*. I’d guess that ninety percent of Espresso’s features are not provided in the Sugar-developer preview releases that we’re seeing. Espresso may already *have* remote-editing functionality, and if it doesn’t, Jan will probably be open to adding it. I’m just saying that that’s not something that needs to be worried about for then (read my next words carefully) Sugar-developer-specific preview releases. Get my point?

Agreed; fortunately, we as users don’t have to worry about when things are implemented.  Hopefully people won’t stop requesting things like this, but also won’t be disappointed if they don’t show up right away because Jan is focused on a different aspect of the program.

George the Flea - 18 December 2008 05:44 PM

elliottcable - 18 December 2008 04:54 PM

Yes, it does. But not *right now*. I’d guess that ninety percent of Espresso’s features are not provided in the Sugar-developer preview releases that we’re seeing. Espresso may already *have* remote-editing functionality, and if it doesn’t, Jan will probably be open to adding it. I’m just saying that that’s not something that needs to be worried about for then (read my next words carefully) Sugar-developer-specific preview releases. Get my point?

Agreed; fortunately, we as users don’t have to worry about when things are implemented.  Hopefully people won’t stop requesting things like this, but also won’t be disappointed if they don’t show up right away because Jan is focused on a different aspect of the program.

I love it when everybody agrees d-:

So, on that note. The feature discussed by the topic of this thread would be sexy. Omnomnom.

Not that I’d have as much of a chance to use it as everybody else here, since everything from my server’s configuration files to my blog posts are git-versioned, but hey, I bet I’d find a way.