#321 Cloud integration


How about that: Your tex files are stored in the cloud and you can access and edit them from any computer, you just need to login to your cloud service provider.

So something like a login window for cloud services would be nice. These cloud services might exist already, we could use dropbox, google docs, amazon aws or create a new one maybe? There are some online LaTeX editors which save tex files on their servers, maybe we could use their servers?

We could also integrate svn somehow...


  • scenox

    After installing Dropbox, I come to the conclusion that this feature isn't really needed at the moment. When you have Dropbox, you can put your TeX folders in your dropbox folder and when editing the tex files with TeXstudio, they are automatically updated on your dropbox and on every other computer with your dropbox login.

    There are already tools to integrate every cloud service out there as a folder or network drive in your operating system and there you can save and open your tex files in TeXstudio. So there is no need to integrate cloud in the software itself, is there?

  • Tim Hoffmann
    Tim Hoffmann

    Right. I currently don't see any need to integrate any file-based cloud service. The only benefit would be for sevices, that don't upload the files automatically (which could be done on a file save in TXS). But that's really lowest priority and can probably be directly implemented in a user script).

    Just as a note: for automatically syncing folders like dropbox, it is a good idea to redirect the temporary files to a folder outside of dropbox. This possibility has just been implemented in TXS.

    And SVN support is already available (though I've not used it myself so far).

    Of course, if there are any real benefits in the integration of other cloud services, e.g. syncing to specialized online LaTeX editors or bibliography ressources, we can consider their integration.


  • Anonymous

    What's about writeLaTeX? It's one of the best online LaTeX editors out there. Another good editor is verbosus. Can someone contact the developers of these online editors? It would be a real benefit to just login with your online editor account and have all your documents synced with the cloud.

  • verbosus

    I'm the developer of verbosus.com and find the idea
    interesting. The idea of editing a project locally with
    texstudio then sync it to verbosus.com and then have the
    possibility to edit a project online and then sync it back
    could be a benefit for a user.

    Additionally, verbosus.com allows collaboration which could
    be used for users to work simultaneously on one project.
    Merge conflicts are calculated and displayed using a
    diff-view (already implemented at verbosus.com) - you could
    try that by sharing a project and then edit and save it in
    two browsers at the same time.

    Also note that we provide the user with an Android App (VerbTeX) and
    iOS App (iVerbTeX) version of verbosus.com which means a user could
    then not just edit the textstudio projects in the browser
    but also on their smartphones.

    I guess that would be a real benefit for texstudio users.

    If you're interested in a cooperation please let me know.

    Last edit: verbosus 2013-01-16
  • Tim Hoffmann
    Tim Hoffmann

    In discussion with the author of verbosus.com


  • Anonymous

    I'm one of the developers of writeLaTeX, and this is certainly something we'd be interested in doing - we have a rapidly growing userbase and there would be potential benefits in linking together with TeXstudio, both for writeLaTeX users (ability to easily edit offline), and for TeXstudio users (the simplicity and ease of use of the writeLaTeX online service).

    Tim - if you'd like to discuss how this could work with writeLaTeX, you can contact me at john@writelatex.com

    Best regards,
    John Hammersley

  • Tim Hoffmann
    Tim Hoffmann

    General remarks

    There seems to be quite an interest in this topic from a number of online platforms. After contemplating on it a bit more I'd like to share my thoughts:

    What are the benefits for the user?
    Via a web service, a user can access his files anywhere and maybe also share them with colleagues. Still, offline editors like TXS are to-date much more powerful than their online equivalents. Integration between TXS and web services might make it easier for the users maintain their documents in the cloud but still edit locally.

    What are the actual steps?
    1) Authenticate
    2) Download files
    3) Edit them locally
    4) Upload files
    5) Handle conflicts (if required)

    Since we don't want to reinvent the wheel, let's see what paths exist for the above procedure.

    First, this is a standart edit cycle in version control systems (VCS). So if the user data in your online platform already uses a VCS, it might be a good idea to use this path for integration.
    SVN is already supported in TXS. We might consider extending this to Mercurial or git.

    Second, if you integrate with automatically syncing file-based cloud services such as dropbox, users don't have to do anything. The could service does 1,2 and 4. (Not sure about conflict handling right now.)
    Nothing to do on the TXS side

    Another possibility for 1,2,4 would be SFTP. Note that this does not include conflict handling.
    TXS does not currently support SFTP. I'd consider it medium effort to add it.

    Have I forgotten any important standard? Proprietary solutions are less likely to be implemented, because it's much more work. We'd have to decide this on a case-by-case basis.

    Note, that TXS is programmed by some voluntaries in their spare time. The less there is to do on our side, the faster we may get to a solution. Also, there are many other open projects in TXS. So, I cannot really forecast how fast something is really implemented.

    How to proceed
    1) As an online platform maintainer, consider which of the paths for file exchange may be viable for you.
    2) Write them to me (thoffmann@texstudio.org), including, possibly, your thoughts on conflict handing. So far, I haven't thought this through completely.
    3) After agreeing on the communication, we'd program and start testing the authenticate/download/upload part.
    4) If useful, I might add a UI for simplified authentication/download/upload. Ideally this would be independent of the actual web service.
    5) In a later step, conflict handling can be added.