- ANDROID DEVONTHINK TO GO UPDATE
- ANDROID DEVONTHINK TO GO FULL
- ANDROID DEVONTHINK TO GO ANDROID
- ANDROID DEVONTHINK TO GO MAC
Capturing TEXT is a fairly trivial problem. Capturing anything outside of a traditional desktop context is going to suuuuuck. You'll have to roll your own infrastructure including backups.
ANDROID DEVONTHINK TO GO FULL
Yes a full text search and wiki linking interface would get a fairly large chunk of the essential functionality done. I would respectfully like to posit that perhaps you haven't fully thought through what makes EN and its ilk different. Beorg (iOS) is great but still pretty short on features. That _might_ be what finally gets me off EN but the mobile experience just isn't there yet. I dunno, I've tried em all and EN is still the best IMO. It's got a very usable api to integrate it into any part of your workflow they don't cover. Scan documents (and then find them with OCR).
ANDROID DEVONTHINK TO GO MAC
If you can't give me what I want in less than a few seconds you go in the bin.ĮN has the advantage of being available on Mac and Windows (and Linux w/ Wine), allows you to capture from literally anywhere and has a fantastic and fast search. I need to be able to get a piece of knowledge on the go fast. Notion covers most of the bases but its an electron app and its SLOOOOOOOOOThats a dealbreaker for me.
I prefer a nested hierarchy which I can get with tags in EN. OneNote is fine but I don't like they way it handles organizing data. Only ones that come close are OneNote and Notion. I've yet to find anything that touches it in terms of features and functionality. Yes they have had some problems and I have even tried to jump ship (as recently as last fall when I gave DEVONThink a go). It is from my own system.I find it weird that no one is mentioning that this article is written by an EN competitor. Please don’t mind the Devonthink label displayed on the left. I got the configuration from ĭisplay on Galaxy Ace emulator, the screen display is 480×320 HVGA, with 3.5 inch size.ĭisplay on Galaxy S3 emulator, the screen display is 1280×720 HD, with 4.8 inch size.ĭisplay on Google Nexus 7 emulator, the screen display is 1280×800 HD, with 7.27 inch size. Below are the screen displays when I try to run my app on Galaxy Ace, Galaxy S3, and Google Nexus 7. We will need to do this, because we want the size of the screen header, footer, labels to be consistent between screens. Share the standard size between Activities. I found my application loads a lot faster when I do this.ģ. I only called the previous method once or twice, then I just resize the other text elements based on the returned value.
ANDROID DEVONTHINK TO GO UPDATE
Call the method above and update the text elements. The first is the element to be resized, the second is the minimum ratio of the element, the third parameter is the maximum ratio of the element.Ĭ. I don’t want to be too precise in creating the dimension. We are going to resize the TextView or EditText using the below method. You can only resize the elements once you call the setContentView() method.ī. Resize the dimension of the current TextView or EditText.
Lets say based on the screen below, I want to display the word ‘Yellow’ around 15% of the screen width, and for the display ’00:00′, I want the first ’00’ to be 24% of the screen.Ģ. Decide the dimension of a label you want to display. My approach might not be perfect, but I see it is sufficient enough to make my app versatile.ġ. But here I would like to discuss about coding TextView and EditText, so their display will be based on the screen ratio. My approach is basically the same with the post I made on the 16th of Jan.
ANDROID DEVONTHINK TO GO ANDROID
I do not want to support for smaller screens since I found most of the devices with small screens are running Android OS lower than 2.3.3. I tested it using the emulator on Samsung Galaxy S, Galaxy S2, Galaxy S3, Galaxy Ace, Note, Note 2, Google Nexus 7, HTC One X. I have completed in making my app versatile enough to be displayed in Android screens which are normal, large and extra large. So I tried to work things around by coding screen elements based on the screen percentage ratio. When my application is displayed in Samsung Galaxy S3 and Samsung Galaxy S2, the display is not the same. I realised when coding with Android 2.3.3, the support given is not as smooth as promised. Android’s support for multiple screens across devices is great, but sometimes we need more. This writing is a continuation of my previous blog with the same title.