Sublime Forum

Using Sublime Text as a "frontend" for a note-taking app

#3

There are some bits and pieces I’m looking for indeed.

0 Likes
#5

tend to build toolchains where ST might be one link in the chain rather than relying on plugins or new feature requests.

That’s approximately what I want o achieve. ST is an excellent editor, but I’d rather have my app/db/search logic separate from the UI, to be able to switch to another editor, if need be.

0 Likes
#7

Funny that my post got flagged as suspicious, yet this nonsense went through.

0 Likes
#11

Urtext developer here. Thanks for the mention @herr.kaste. We are no longer updating this on packagecontrol.io but we are looking for test users. @andysh you can try it using the instructions at https://urtext.co/setup/sublime-text/. It has many, though not all, the features you list. The underlying library is made to work in any editor/environment where Python 3.3+ is available, so things like managing windows/panes would be a Sublime-specific feature.

0 Likes
#12

@nbeversl How do you handle the updates. Have you code that fetches new versions, or notifies the user about new versions? Maybe you could also tell what the problem with packagecontrol was.

0 Likes
#13

@herr.kaste I was doing frequent updates in the last few months and the status of the crawler for package control was unknown. Is it now back up? The current version is public but somewhat beta quality, so I need to be able to get changes out quickly. Glad to have it back on package control if I can have more insight into the status.

0 Likes
#14

Yeah, packagecontrol was down starting with Feb 14. It is now working again. Since a week, roughly.

0 Likes
#15

I see the PR removing Urtext was merged but the package remains at https://packagecontrol.io/search/urtext. So I’m still not exactly clear. When you asked (https://packagecontrol.io/search/urtext) how I handle updates – that is also what I am trying to best decide. If I have users who are not Git-savvy or otherwise rely on package control, they become unable to update without it. Not complaining, just trying to make a choice on the best option. We are about to do a call for some more test users so I want it to be straightforward for them.

0 Likes
#16

On packagecontrol the last version is frozen. (Otherwise it would have been uninstalled for users that already have it.)

IMO it should stay on packagecontrol as it should just work for users that are not also programmers. For this package it may be also recommended to use an independent, local version of Sublime Text. (Stand-alone version) Iirc your package grabs a lot of global key bindings.

Grabbing these keys is likely not necessary as you could use contexts here so that the keys are only bound when an urtext view is currently active.

0 Likes
#17

can you please clarify

independent, local version of Sublime Text. (Stand-alone version)

I am not sure what this is.

Yes, I could move the keybindings into a context only for the syntax.

0 Likes
#18

Stand-alone is what they call the portable version. You just unzip to a folder and run from there. image

This works on all platforms.

0 Likes
#19

Note that if you want a portable version for Linux you’ll need to make a Data directory next to the executable. I’m sure something similar works on macOS.

0 Likes
#20

Sorry for the late reply. The project looks promising, I’ll definitely give it a try.

0 Likes
#21

@herr.kaste PR is submitted again. I will change the keybindings so they are not global by default.

1 Like
#22

@herr.kaste I’m opting for separate channel installation instead of main package control. Would you consider removing Urtext from package control to prevent any confusion for new users?

0 Likes
#23

You really making things up here. The PR at package control is closed before getting a review. And now you want to use Package Control but own your own channel. What is actually here the benefit for the end-user, and what is the temperament of you or so-called developer convenience?

urtext should not have been removed in the first place as that is not correct if you still want to develop it. If you just remove the channel entry which you already did, Package Control freezes the last thing it knows. (There are good and bad parts about this obviously, but I think the original writer didn’t want plugins that just disappear under the users hands. Basically, a user already having the package must be able to look that up again. And automatic uninstalling was not an option at all as that would be hostile as f.)

Ideally, you would not have removed the original urtext entry as you still claim that name, and then developed a way to move to the new location. (Maybe just by adding “I hate PC. This package is now at X. Use PC to install it” to your README.)

0 Likes
#26

Love the humor, but the message should be delivered to your end-users not to me.
Ideally it would appear on https://packagecontrol.io/packages/Urtext to instruct them to make the move too.

0 Likes
#28

Looks like the code could work and do what’s advertised. But how do you want to ship that?

0 Likes
#30

You shouldn’t have made the repo rename. That is so confusing to users. And you never get the README on packagecontrol.io updated because you removed it.
Also, existing users never see the update. And new users are somewhat tricked. It is clever but I think:

You really making things up here.

Instead of waiting for a review you did a trick that might be read as an attack vector for other people.

0 Likes
#31

Maybe worth mentioning package control channel being reviewed/maintained primarily by one volunteer - with some others rarely jumping in - having been doing a great job for about a decade.

You should pay more pacience to those people spending their unpaid spare time to do a more or less boring job of reviewing plugins they most likely never use or need on their own.

Still they do a great job keeping default channel clean and safe, by preventing duplicates, hostile packages being added and ensuring least quality and compliance guidelines are satisfied.

packagecontrol.io having been down for a too long time is unfortune, but was communicated/reported/discussed in all available channels, including this forum, discord and github. Various devs have been hit by it, unfortunatelly.

Also note the current installer package using internal Package Control APIs which can change at any time rendering it useless.

Besides this package possibly being interpreted as a channel injection attack, I primarily don’t find it user friendly.

0 Likes