Talk:Brackets (text editor)
 | This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
| ||||||||||||||
 | The contents of the Brackets (text editor) page were merged into Brackets on 16 April 2014. For the contribution history and old versions of the merged article please see its history. |
Naming of the editor
editThe editor is named and referred-to as Brackets rather than Adobe Brackets. While the project was started by Adobe and is supported by it, it is OSS and not a Adobe's product. Rather, Adobe markets Edge which is built on top of Brackets. Hence I'm going to move the article to its proper place. François Robere (talk) 18:56, 16 April 1990 (UTC)
Sloppy writing style
editThe first paragraph is indicative of the rest of the article's lack of attention to detail:
- Brackets is a source code editor with a primary focus on web development. Created by Adobe Systems, it is free and open-source software licensed under the MIT License, and is currently maintained on GitHub by Adobe and other open-sourced developers. It is written in JavaScript, HTML and CSS. Brackets is cross-platform, available for macOS, Windows, and most linux distros. The main purpose of brackets is its live html, css and js editing functionality.
- What is an 'open-sourced' developer?
- Which MIT licence it does this refer to? MIT has used many free licences throughout its history.
- If it is available to 'most' Linux distros, then it is potentially available to all Linux distros.
- Why is 'Linux' non-capitalised, but macOS and Windows written to follow the preferred naming conventions of those companies?
- Why is brackets non-capitalised? Why are HTML, CSS and JS non-capitalised?
- Why is JS not written out in full? JS is ambiguous.
What does the statement below mean?
- The main purpose of brackets is its live html, css and js editing functionality.
How can the purpose of a text editor be its functionality? Would the purpose of the editor not point to making it more efficient/easy/convenient/flexible to edit HTML, CSS and JavaScript code?
The rest of the article mostly follows in the same vein. Would someone please correct the problems I described?
GitHub repository statistics irrelevant
editThe Brackets repository on GitHub (Bracket repository) currently has 152 branches, 110 releases and 17,700 commits as of 30 Aug 2018. The source code is freely available under the MIT license. A developer can alter features on Brackets and personalize it for one's own convenience by forking the software code.[13]
Why is this relevant? This information is easily outdated and would have to be constantly updated to reflect reality. This is wasteful and tedious and should be removed. It also reads like an advertisement for GitHub.
Warning during preview
editDuring preview there is this warning:
- "Warning: Page using Template:Infobox software with unknown parameter "status" (this message is shown only in preview)."
Should something be done? --Mortense (talk) 11:33, 16 February 2019 (UTC)
- @Mortense: No. GUYWAN ( t · c ) 22:13, 8 July 2019 (UTC)
Reorganisation
editMove sections pertaining to features to the, uhm, Features section.
- Quick edit
- Live preview
- Split view
- Multiple file format support
GUYWAN ( t · c ) 22:15, 8 July 2019 (UTC)
EOL status
editAccording to the Brackets website, the app is transitioning from Adobe to a community-built release. The popup on the homepage says, "Brackets is being transitioned from Adobe to the Brackets Community. We are aware of issues with the extension manager and is working on top priority to push the fix by November 2021." — ★Parsa ☞ talk 22:18, 20 October 2021 (UTC)