You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Until Dec 2022, we were working hard to bring phcode.dev to the browser with feature parity with brackets core. Now that phcode has been marked stable and feature parity attained(barring extension marketplace), we move to the second stage of the effort to bring in advanced code intelligence features and git support to web natively.
Phoenix is a browser-based code editor, and the current technology landscape presents challenges to enabling the below two features in a pure browser-based code editor:
While the above two are straightforward to do if node is available, it is extremely hard to do in a pure browser-based setting. The aim of this issue is to bring in first-class support for the above two workflows in the browser purely on the client side without any server/nodejs support.
Please click on the issue links to see more details.
Pheonix should support all features of GIT in the Browser without backed support. Brackets earlier had brackets-git extension that requires node runtime and git installed. But this will not work for Phoenix as client side web is the main target for Phoenix IDE. See the available technologies section below for options.
Phoenix is based on a virtual file system that presents a UNIX-like file system to the browser backed by indexedDB or fs access API. The filesystem is exposed by a nodejs fs like library that is partially compliant to node fs lib. This virtual filesystem presents as as single unified file system available within all contexts(main thread, workers, service workers). As it is backed by indexed db, it presents full support for change watchers across are js contexts in the same domain. The phoenix Virtual File system is the first of its kind to expose a node-js like fs API over the new fs access API. This abstracts out the tree like fs access APIs to a more conventional /path/based/api that is easier to work with. What is more convenient is that the same path is valid across all browsing context if an fs access path is mounted in any one of the tabs.
We need to thread this virtual file system to the isomorphic git library to make Git work in the browser in Phoenix IDE.
Language server support is essential for the future of phcode.dev. Language servers brings in code auto completion and advanced code assistance features inside phoenix. Almost all implementations currently in existence require node and the few that work in the browser(ts language server) run only in vscode.dev.
We should find a way to browserify popular language servers in pure browser-based environments. This will help web-based code editors like us and others to provide advanced IDE-like features in the browser.
The text was updated successfully, but these errors were encountered:
Until Dec 2022, we were working hard to bring phcode.dev to the browser with feature parity with brackets core. Now that phcode has been marked stable and feature parity attained(barring extension marketplace), we move to the second stage of the effort to bring in advanced code intelligence features and git support to web natively.
Phoenix is a browser-based code editor, and the current technology landscape presents challenges to enabling the below two features in a pure browser-based code editor:
While the above two are straightforward to do if node is available, it is extremely hard to do in a pure browser-based setting. The aim of this issue is to bring in first-class support for the above two workflows in the browser purely on the client side without any server/nodejs support.
Please click on the issue links to see more details.
Git support in the browser
Pheonix should support all features of GIT in the Browser without backed support. Brackets earlier had brackets-git extension that requires node runtime and git installed. But this will not work for Phoenix as client side web is the main target for Phoenix IDE. See the available technologies section below for options.
Phoenix is based on a virtual file system that presents a UNIX-like file system to the browser backed by indexedDB or fs access API. The filesystem is exposed by a nodejs
fs
like library that is partially compliant to node fs lib. This virtual filesystem presents as as single unified file system available within all contexts(main thread, workers, service workers). As it is backed by indexed db, it presents full support for change watchers across are js contexts in the same domain. The phoenix Virtual File system is the first of its kind to expose a node-js like fs API over the new fs access API. This abstracts out the tree like fs access APIs to a more conventional/path/based/api
that is easier to work with. What is more convenient is that the same path is valid across all browsing context if an fs access path ismounted
in any one of the tabs.We need to thread this virtual file system to the isomorphic git library to make Git work in the browser in Phoenix IDE.
language server support in the browser.
Language server support is essential for the future of phcode.dev. Language servers brings in code auto completion and advanced code assistance features inside phoenix. Almost all implementations currently in existence require node and the few that work in the browser(ts language server) run only in vscode.dev.
We should find a way to browserify popular language servers in pure browser-based environments. This will help web-based code editors like us and others to provide advanced IDE-like features in the browser.
The text was updated successfully, but these errors were encountered: