Removed source param from Keybindings an Commands APIs
Previously in 223:
Fixed some memory leaks
Added AttributedString.toHTML()
Fixed spelling of AttributedString.subsring method
Added host_permissions manifest key. To use the fetch API your extension needs both the fetch permission and the fetched URL needs to match one of the patterns in host_permissions.
Previously in 222:
Added Window > Log Explorer for extension developers
Changed postMessage and onMessage API to use Json instead of strings
I forgot to post the last few Bike 2 previews here.
Still working mainly on the extensions API. Also working on some extensions here (d3 layouts, calendar) to test that API. API is generally pretty stable in the big picture, but I’ve been breaking some things. Generally if you are testing any extensions you should make sure you have both latest version of Bike 2 and latest version of the extension.
I haven’t tried the 2.0 version yet and my license isn’t valid for current updates. Could you please comment in future release notes on the state of Bike 2 for everyday usage?
Still not ready for daily use, though I’m using it daily. In my experience it’s not full of crashes, it’s just missing major pieces such as spell check and find and replace, etc.
I’ll make quite a bit of noise, I hope I remember, when I do think it’s ready for general use.
Thanks I did this and Bike updated to Preview(191) version 1.22. I meant version 224 Version 2.
Do you mean if I download 223 then 224 will update this way?
Do you find you can use 224 instead of Version 1.XX daily?
Yes, from 2.0 Preview 223 you can get to 2.0 Preview 224 via Bike > Check for Update …
Whether it works yet for your daily use depends on the profile of your use.
I’m beginning to write little extensions for Bike 2.0 Preview, and finding it more than enough for outlining, but I run both, with separate shortcuts to each (still using some Bike 1 macros which I haven’t replaced yet)
FWIW I keep them separate by installing Bike 2.0 Preview in an Applications directory under my user account, rather than in the main Applications directory.
i.e. at ~/Applications/Bike.app for 2.0 Preview
while, on my system, /Applications/Bike.app is still Bike 1.0
@complexpoint is right… I think Software Update will give you the correct latest preview release… but the release page was messed up. The release numbers on that page are manually typed in by me, and I was off by one the last two releases… so while the correct versions we being downloaded by software update, the list in the releases page had the wrong numbers. Anyway, should be fixed up now!
Yes, this is just missing functionality that still needs to be implemented. Lots of interaction with the editor (Find Replace, Context menu, Spell check) is in same state.