Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Favourite Code/Text Editor
jakob wrote #336913:
Hi Phil, did you ever get the autocomplete / syntax plugin working in the end?
Jakob, as posted, the link to that extension (github.com/textpattern/Textpattern.novaextension) returns a 404.
I vaguely remember Phil making an extension for Coda which I had a look at to see if it could be ported to SubEthaEdit (the Coda text editing code came from SEE). I had it somehow working minus the autocomplete part, IIRC.
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg
Offline
Re: Favourite Code/Text Editor
Found recently: a code / text editor for iOS 15+: Runestone. I have not yet had the possibility to test it. It might be useful when on the road to scribble some txp or html code (with some form of code colouring) rather struggle in a textarea.
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg
Offline
Re: Favourite Code/Text Editor
I am so curious to know whether Phil took this Textpattern nova extension any further. I so hope so!
Unfortunately not, the regex stuff was beyond me. I have a bunch of clips instead that contain various Textpattern tags and that works quite well for my limited needs.
Offline
#34 2024-03-15 08:59:55
- Algaris
- Member
- From: England
- Registered: 2006-01-27
- Posts: 608
Re: Favourite Code/Text Editor
phiw13 wrote #336915:
Found recently: a code / text editor for iOS 15+: Runestone.
Now this does look interesting. I like that the Pro upgrade is a straight up £9.99 purchase with no monthly subscription.
Finding a decent code editors for iOS is quite hard these days. I’ve seen so many come and go, including Panic’s own code editor.
gaekwad wrote #336897:
I used Coda exclusively, having been a user since the early v1 releases. I used it in tandem with Tower for Gil stuff, and it worked just fine on my 2012-era fleet of cheap Macs running Mojave. I didn’t really notice any Electron overhead with Atom, and for my purposes it worked just fine…
Thank you for posting your workflow and rational. I really enjoyed reading it and found myself nodding my head in agreement with a number of things, especially keeping my Mac as vanilla as possible, which is why I’ve moved all of dev stuff onto a dedicated ubuntu server with VMs and Samba shares.
I did find it interesting that you’re going down the CodeKit root. I have CodeKit but found myself going more down the terminal root on my Ubuntu VMs. I install Bootstrap using npm and run a bash script on the server to convert all of my SCSS files into CSS before they are synced to my web root. Saying all that I would like to dig into CodeKit a bit more and give the tyres a good kick to see if I’m missing anything.
Last edited by Algaris (2024-03-15 09:13:22)
Offline
Re: Favourite Code/Text Editor
philwareham wrote #336916:
Unfortunately not, the regex stuff was beyond me.
Yes, totally understand you. FWIW: I vaguely remember reading they changed the tree-sitter at some point. It’s described here
phiw13 wrote #336914:
Jakob, as posted, the link to that extension (github.com/textpattern/Textpattern.novaextension) returns a 404.
Apologies. I see now that the repo is marked private and I am somehow allowed to see it.
TXP Builders – finely-crafted code, design and txp
Offline
Re: Favourite Code/Text Editor
gaekwad wrote #336897:
The next purchase I’m looking at is CodeKit […] My Mac environment is deliberately as vanilla as possible as far as background stuff is concerned. I don’t use Homebrew, for example. […] I see CodeKit as a halfway house, since it has a pretty way to do stuff using some of the CSS frameworks I use.
Algaris wrote #336917:
I did find it interesting that you’re going down the CodeKit root. I have CodeKit but found myself going more down the terminal root on my Ubuntu VMs. I install Bootstrap using
npmand run a bash script on the server to convert all of my SCSS files into CSS before they are synced to my web root. Saying all that I would like to dig into CodeKit a bit more and give the tyres a good kick to see if I’m missing anything.
I have used CodeKit for quite a while but am trying now to transition in the command-line direction.
Codekit has a myriad of options and a lot I haven’t/don’t use. It’s great for simple stuff like compiling sass and minifying js, and it makes things beautifully clear what it is doing, e.g.: “this source file will be processed to that target file in that folder with name/suffix xyz…”, what linked files will be processed, and what files to ignore or not process etc. You don’t have to work with a build folder, so can use your own folder setup if you want, at least for simpler setups. Browser autoprefixing according to browserslist settings are all included, and you can bring in npm packages for extras you may want (e.g. PostCSS) for post-processing. If it doesn’t do something you want, you can add hooks to do things like run a shell script, which are called according to conditions you set much like in the finder search options. In short, there’s a lot to like about it, as it gives you a mac-like interface to the comparatively impenetrable package.json scripts.
The biggest limitation is you can only share settings with other CodeKit users, so if they don’t run a Mac, or a Mac that can’t run CodeKit, you can’t work together. For ongoing projects it requires you stick with it, too. It’s updated every few months but external packages will update more frequently from npm.
On the command-line side of things, I never really got to grips with webpack/rollup, or they seemed too complex for my relatively straightforward needs, but LightningCSS / PostCSS Preset Env via Parcel or Vite I can just about handle. Again, I suspect I am just scratching the surface, but compiling from modular sass/css files and minifying css/js is straightforward and fast, and LightningCSS will convert modern CSS rules for backwards compatibility with earlier browsers according to your target browser profile (again using browserslist). This pretty much presupposes you’re using a src/build folder setup, so I have a /src/ and /assets/ folder set up in my Textpattern theme. For my use at least, I find I have to dumb down Parcel’s automatic intelligence a bit to just copy some stuff without processing it or to not timestamp all the files. It’s definitely fiddlier compared with Codekit, and sometimes you need not just a package.json but also a .parcelrc file to control the settings (at least when using parcel).
But it doesn’t cost extra and you can share your settings more easily. I use it with pnpm (see pnpm vs npm). You can also hook your dev and build scripts from your package.json to Nova’s project tasks and start/stop them from the title bar. I’m not sure I’ve completely mastered this setup yet, but it’s what I’ve been trying to use more recently.
TXP Builders – finely-crafted code, design and txp
Offline