tag:blogger.com,1999:blog-44380472295963375172024-02-19T07:11:02.749+00:00howardbhowardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.comBlogger57125tag:blogger.com,1999:blog-4438047229596337517.post-60381137369924957532013-01-06T17:26:00.002+00:002013-01-06T17:26:16.403+00:00Preview of next CMarks release - Synced tabsHi all,
A quick post to give a sneaky preview from the upcoming release of CMarks. This will incldue the ability to access your Synced Tabs - so on your droid you can see the tabs currently open on your laptop and open the exact same webpages.
Please see the post on the new G+ page for the app - +CMarks
Note also that I'll no longer post things here - the +CMarks page will become the default howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.comtag:blogger.com,1999:blog-4438047229596337517.post-4584718016902004092012-12-20T21:00:00.002+00:002012-12-20T21:01:06.372+00:00CMarks - Updated 2012.12.20Hi all,
An emergency bugfix to CMarks today. Only one change.
Starting late on the 17th December, Google enable some new validation on the chromesync servers. This meant that a small proportion of users started getting an "Error 500" message when they sync. It took two days before it started to affect one of my test accounts and I could finally reproduce the error. I started playing and found howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-7778851109604399942012-11-11T18:51:00.000+00:002012-11-11T18:51:18.165+00:00CMarks updated - 2012.11.11Time for an update.
First, a reason for the recent lack of updates. I spent a good few weeks (remember, I only have a couple of hours free time per week anyway) trying to add a new library for communicating with Google. The new library claimed huge performance benefits which I hoped could make each sync even faster. But it took a while to plumb in and I had to contribute several patches to it howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-77747893102621251562012-09-16T13:57:00.000+01:002012-12-20T21:01:14.456+00:00CMarks Update - 2012.09.16Time for a quick update.
Added the ability to "hide" any of the Root folders i.e. Search Engines, Synced Bookmarks, etc. Also added a new option in the Settings, Application Defaults to allow you to manage this list. Only for the Full app, though!
Fixed a couple of crashes happening during the local sync on 2.x devices when syncing to the special folder in Chrome.
Some performance howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-59483577308973021252012-09-09T16:55:00.000+01:002012-12-20T21:01:22.060+00:00Cmarks Update - 2012.09.09A quick CMarks update. This is for the Full app only.
CMarks can now integrate your Chrome bookmarks into Dolphin using the same ordering you've specified in CMarks. Some caveats - though:
Dolphin always shows Folders alphabetically and at the top of a list. I can't change the ordering or placement of Folders.
Dolphin always removes any bookmark being inserted that has the same url as any howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-81071229358068908242012-09-02T15:39:00.000+01:002012-12-20T21:01:31.804+00:002012.09.02 - CMarks updateTime for another update!
Users of the Full app can now integrate their bookmarks into Dolphin browser or Dolphin Beta. This has only been possible due to the recently introduced Garage API for Dolphin - until about three months ago, this was still only possible for apps created and owned by Dolphin. Some points to bear in mind, though:
This is currently only one-way. So any changes made in the howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-77130529988331635332012-08-19T13:38:00.000+01:002012-12-20T21:01:40.163+00:00CMarks Update 19.08.2012Well, I'm still here, so I guess I'm okay to keep developing this app.
As such, some updates:
Finally managed to get Themes to work 3.x and above devices. Some changes Google made with 3.x caused some issues that I hadn't managed to work around previously. With a smidge of extra effort, I've found enough workarounds to re-enable Themes for all devices now.
Fixed a bug that had been annoying me howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-39599584503090698012012-08-10T00:02:00.001+01:002012-12-20T21:01:57.658+00:00Cmarks!So, some big changes to the app today.
Google changed their Play Store Policies recently. One of the changes was that apps must not impersonate other apps or system apps and that users should be not jump to the wrong conclusion and assume an app is officially supported by someone else by virtue of it's name, icon or content. Well, that's what I understand from the policy documents - to someonehowardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com2tag:blogger.com,1999:blog-4438047229596337517.post-63282712294930799782012-08-05T17:13:00.003+01:002012-12-20T21:01:49.712+00:00ChromeMarks update - 2012.08.05Time for another update!
Firstly, I completed missed the fact that in the middle of June, ChromeMarks Lite reached 500,000 downloads. That's a phenomenal number and I never dreamed of getting so many downloads for a single app! Especially since that app has only been out there for less than two years. Thank you to everyone who's downloaded the app - still many more new features yet to come!
&howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com3tag:blogger.com,1999:blog-4438047229596337517.post-13847216752297565342012-07-14T17:36:00.000+01:002012-07-14T17:36:36.958+01:00ChromeMarks 2012.07.14A new update to ChromeMarks today.
Firstly - apologies for the delay since the last update. The normal day job, the usual PC problems and no internet for a month all contributed to it. But I've been tinkering away as normal and the updates are coming!
The juicy details:
A bug fix for Jelly Bean users of the Full app. Turns out that Google made undocumented changes to the SSL implementation howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-61074302240214467032012-03-17T16:03:00.000+00:002012-03-17T16:03:41.858+00:00ChromeMarks - update 20112.03.17Time for another update..!
Some more changes made by Google on the chromesync servers which are starting to affect a few users:Some new error messages were being returned which users have started receiving. Since ChromeMarks isn't aware of these messages, the app isn't showing anything back to users so you don't know there was a problem. One of the new messages tells users "your bookmarks have howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-1795040807809476592012-02-26T14:23:00.000+00:002012-12-20T21:02:08.032+00:00Chromemarks Updated - 2012.02.26Time for another quick update. As usual, the highlights in more detail:
Fixed a bug where the app would state "the folder is not found" if you were creating or moving a bookmark in an empty folder. Was due to a mild logic bug and has been that way for about three months. With the help of some log files from Jordan and Denis, I've found and fixed the bug.
Fixed a bug whereby a large number of howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-40321420457304354672012-02-21T21:45:00.000+00:002012-02-21T21:45:13.241+00:00Chromemarks Updated - 2012.02.22A small update to the Full app only:
Since a user may use the local bookmarks function and then disable it at a later date, after each sync the app would do a mini tidy-up. If local bookmarks were disabled, it would ensure there were no klingons and remove them just in case. But this was causing some errors for users who had uninstalled the stock browser, or frozen it. Fixed this with a bit of howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-41871687921475023032012-02-19T13:25:00.001+00:002012-02-19T13:25:25.666+00:00Chromemarks Updated - 2012.02.19Time for another update. As usual the highlights in detail:
Google broke something. This was affecting the way my app was determining parent/child relationships between folders. It was making some folders appear multiple times and other folders "disappear". It looks like Google have clearly changed the way the sync server responds in the last two weeks. I've raised a chrome bug and attached howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-40354210782904403552012-01-12T15:57:00.000+00:002012-01-12T15:57:21.133+00:00Chromemarks Updated - 2012.01.12To continue with my new years' resolution of smaller, quicker updates - it's time for an update!
Added a new Tutorial or "Quick Start" screen. This is only shown for brand new installs. It shows briefly how to perform the first sync, some common customisations and some common problems. Also uses the fancy swipey new ViewPager with a cute title indicator across the top. Also a nice offset image ofhowardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com1tag:blogger.com,1999:blog-4438047229596337517.post-2386131667399528802012-01-05T13:12:00.000+00:002012-01-05T13:12:29.524+00:00Chromemarks Updated - 2012.01.05First new update of the year. Sorry it took so long but some of the changes had the potential to impact many users so I needed to take my time to test them more carefully.
As usual, the release notes:
I've completely rewritten the network stack. There are two common ways of performing a network request in Android - apache http client and java net. Both have pros and cons and the app had been howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-68492823012671481882012-01-02T15:46:00.000+00:002012-01-02T15:46:08.996+00:002011 / 2012Thought it was time for an update on some of the key points over the last year with regards to ChromeMarks and what's on the horizon this new year.
2011's highlights.In July, Google turned something off on the Chrome servers and the app started failing. 24 hours later, a fixed version was released. Honeycomb users are *still* waiting for their fix.. :-)
In Autumn, Chrome 14 arrived and with it's howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com2tag:blogger.com,1999:blog-4438047229596337517.post-12355619142107723012011-12-06T14:40:00.000+00:002012-12-20T21:08:04.893+00:00ChromeMarks updated - 2011.12.06Another ChromeMarks update.
The major change is the addition of synced Search Engines:
If you enable these for syncing in Chrome, they will now be available in the app and you can click on them and use them as quick search for the website in question.
In a later release, I'll try and add them to the Android Search Widget so you can do a similar thing to the chrome omni-box and hopefully howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-83411323478027793592011-11-29T14:58:00.001+00:002012-12-20T21:08:15.051+00:00Chromemarks Updated - 2011.11.29Time for another ChromeMarks update.
Pro users can now export/backup all their bookmarks to a file. This file is fully Chrome compatible. So if you accidentally deleted, say, every bookmark in Chrome and you haven't synced ChromeMarks then help is now at hand! Simply export from ChromeMarks, copy the file to your PC and re-import it and your bookmarks will be resurrected. Of course, folders and howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-48874250966766403172011-11-13T15:03:00.000+00:002011-11-13T15:03:18.934+00:00ChromeMarks updated - 2011.11.13A long overdue release of ChromeMarks today. As normal, the highlights:
The app can now handle Chrome encrypted bookmarks. This was originally expected to be a pro only feature for some time next year. But recent releases of Chrome have started enabling encrypted bookmarks by default, so I had to accelerate the plans. There were a large number of challenges to implement this (see previous howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com1tag:blogger.com,1999:blog-4438047229596337517.post-77741809416806463392011-10-17T23:31:00.001+01:002011-11-13T12:16:50.810+00:00ChromeMarks - Progress updateHi all.
Thought it was time for a progress update since its been a while since the last release of the app.
The main piece of functionality I've been working on is decryption/encryption. Originally I wasn't going to do this - I thought this was an additional feature that users would have to explicitly enable in Chrome and they could easily disable it in Chrome as well. At best, this howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com4tag:blogger.com,1999:blog-4438047229596337517.post-63839075585806469412011-08-28T17:17:00.001+01:002011-11-13T12:16:41.107+00:00ChromeMarks - 2011.08.28 releaseAnother new upgrade today.
Mostly upgrading the internals, but a few new bits.
For the Lite app, I've added an "Upgrade Options" screen to the settings. This will show you what features of the full app are available to you should you choose to upgrade. So for example, can the app specifically integrate to your browser? Screenshot below.
Upgraded the crash reporter (ACRA) from v3.2 to v4.1. Nothowardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-77496733504960859742011-08-07T13:17:00.002+01:002011-11-13T12:16:32.317+00:00ChromeMarks update - 2011.08.07Another new update for ChromeMarks. If a release could have a sub title, this would be the called the "performance release".
As usual, the list of changes:
Finally taken the plunge and upgraded the the ACL (Android Compatibility Library). The most noticeable thing this brings is an improved way of loading the data for the screen and better management of the memory. For users, they should howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-87346365388516196912011-07-22T14:19:00.001+01:002011-11-13T12:15:44.156+00:00ChromeMarks update 2011.07.22Hi all - time for another update to ChromeMarks. Thankfully the changes made on the 12th July haven't had any issues that required a fix here, so these are all new features or fixes to things that have been broken for a while.
New features - Gestures. Only in the paid app. You can now specify that flicking up or down performs some action (i.e. up a folder, goto root) and swiping a bookmark or howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0tag:blogger.com,1999:blog-4438047229596337517.post-10039592487623087262011-07-21T20:08:00.000+01:002011-07-21T20:08:09.743+01:00Twitter action!Just a quick message to say that I'm on twitter as @chromemarks and http://twitter.com/chromemarks. I'll try and tweet on new features I'm working on, new bugs or issues and anything else that might be useful. Send me a message if you have ideas, comments or questions!howardbhttp://www.blogger.com/profile/15097858261396164313noreply@blogger.com0