• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 83 subscribers
  • Views 106 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

C2000WARE: CCS theia dependency on Open-VSX Registry

owen flatley
Prodigy 75 points
Part Number: C2000WARE

Tool/software:

Hi TI,

I am not a fan of the old CCS-eclipse experience, so I am happy enough with the move to Theia.  And I understand that the old CCS is deprecated by the future release of CCSTheia 1.5.

One general comment: please consider that this toolset is used by developers in classified environments that are locked-down in regards to full/any internet access.  So, if there are hardcode assumption to go check the network for blah or blah, that's not ideal.

Aside from that, I do have an immediate issue(s) with Extensions. 

1) In VSCode, Extensions are tied to 'Marketplace' -- and it works that if you click on an installed extension, then you can see info about the extension in one of the centrally located views.  However, Theia seems tied to Open-VSX Registry.  It may be a problem of being in a restricted environment, but the attempt to access that (online) registry causes a TIMEOUT, in big red letter. I can get that to go away by adjusting Extension Proxy Settings, but there is never any Info update to the central view panel, as there is in VSCode. So, it seems like there is an expectation that Theia can reach Open-VSX.  I don't see anything equivalent to VSCode's settings.json, where that might be configured. 

 

2) Some VSCode extensions don't load (again, this are the approved extensions / versions that are cached on a closed network).  Do you know how I can get more info on what went wrong?    

3) Some extensions load, but don't update the F1 menu (even after Theia restart).  For instance 'TaskRunner' installed, but there are no Task items in the F1 menu

vs.

I started to dig some on Theia's documentation, but I wanted to get TI's take on this situation, hoping to save time.

Thanks

  • 0
    TI__Genius 15725 points

    Hello Owen,

    Thanks for reporting these issues.

    Re #1 - This is a Theia issue, the automatic proxy setting isn't fully functional like VSCode and required setting the proxy manually. Theia is lagging behind VSCode in terms of features, we are monitoring this issue will pickup Theia change as soon as it is available. Additionally, CCS Theia is a few versions behind the latest Theia release. We are planning on updating to the latest Theia.

    Re #2 - Not all VSCode extensions will be compatible to Theia, the one that are published to OpenVSX is supported by Theia and tested by the extension Author. However, VSCode extension that you have downloaded from the Visual Studio Code Market can be installed in Theia, but there is no guarantee that it is compatible. You can start off by checking the API requirement for the extension and compare it with the VSCode API version in the Help -> About dialog in CCS Theia.

    Re #3 - Same as #2, you will need to check if it is API compatible. Theia has a debugger window (DevTool), see Help -> Toggle Developer Tools. You can open the debugger console to see if there is any error when using this extension. This might give you a hint on why this extension doesn't work.

    Regards,
    Patrick

  • +1 in reply to Patrick Chuong
    Prodigy 75 points

    Thanks Patrick,

    Understood. All of this is WIP.  

    I do appreciate the sentiment of using non-microsoft product (i.e. although vscode source is open, vscode executable is not open and may actually do convert operations and telemetry) -- so, in theory, open source is more transparent.  In practice, places that work in a 'closed' environment may lag months behind what is available online, and open-source sw is always hard(er) and time-consuming to get approved.   And Extensions may take even longer to get approved -- which is why it would be nice it the MS Marketplace ones 'just worked'.  But I acknowledge that is a Theia issue, not a CCSTheia issue.  In all, even without being able to leverage and Extensions in CCSTheia.  On balance,  this new IDE is not worse than the old CCS (discounting issues like lack of multi-core Grouping, atm), and I am sure it will improve overtime. And for my part, I will just have to become more knowledgeable regarding Theia.

    Please just keep in mind that people in closed labs, with NO internet connection, will need this IDE to have a minimum of gotchas.  Any presumption/reliance about an internet connection is going to be tough. 

    v/r,

    Owen 

  • +1 in reply to owen flatley
    TI__Genius 15725 points

    Grouping and other new features such as pin&clone for multi-core debugging will be coming in the next release, v1.5, it is scheduled to be available by the end of August. 

    For a close lab environment, you can certainly get away without an internet connection by downloading the vsix files from OpenVSX website using another computer and install the extensions locally by browsing to the files using the three dots menu in the Extensions side bar view.

    Patrick

  • 0 in reply to Patrick Chuong
    Prodigy 75 points

    Hi Patrick, 

    Great, looking forward to 1.5.

    Yes, we must use a local approved cache for all of our software, not just Extensions.  So, all of the extensions I've tried to install are only from that local cache, installed via approved, vetted VSIX.  It is impossible any other way, here.   And we will not have the option to just install from open-vsx.  As a new CCSTheia user, (I'd guess the first, bc I needed to push it through our security approval process), is that there was a BIG RED ERROR in the Extensions window saying that contacting Open-VSX timed out.  And not really knowing why -- like is this a normal issue that occurs before some default config, or maybe I'm blocked, or maybe anything else -- i just needed to dig in the Extension Proxy settings.  Those that work for VSCode do not help CCSTheia.  So, from my customer perspective, it's a bit of work, including writing forums and looking at stuff online.  And because other stuff does not seem to work with total coherency, it's hard to know what's working and what is not working.  For instance, some of the Marketplace plugins install with a success message, but then don't appear in the Installed list.  

    I think it's great the TI is trying to improve the dev experience with Theia.  Just saying that there seem to be issues with Extensions.  And also asking that there is testing done without an internet connection, and that work arounds are provided if needed.  Thanks

  • +1 in reply to owen flatley
    TI__Guru**** 433951 points

    Thank you for the feedback. We are always looking to improve the experience with CCS Theia and your feedback is very valuable in helping us prioritize where improvements need to be made.