I'm writing a set of generic UI controls for the TD and at the moment I'm using C# with lots p/invoke Win32 API calls for gradient fills, alpha blending etc.
It works OK, and I'm spending a fair amount of time optimising for smooth appearance, although the primary goal of these controls is usability.
I haven't played with DirectShow/DirectDraw at all and just wondered what 2D capabilities are available? Is hardware alpha-blending possible? Can you draw and gradient-fill rounded rectangles quickly?
Anyone who's had any experience with this - I'd be very interested in hearing your opinions.
Thanks
Rich
Hmm
I was planning on doing this myself. I believe that D3DM has accelerated blending and gradient fills (I don't know how much of the D3D is supprted in D3DM).
Would you be planning on releasing any code/SDK? It would be nice to have something like to write apps with.
Yep - that was my plan. I used to be very tight with these things, but since spending the last couple of years playing with Linux I've decided that progress is much faster overall if people share stuff.
Can't guarantee that I'll get everything finished, but it's getting there. I've attached a few screenshots, but it's very much in the development stage.
Rich
nice
Looks good!
Hi everybody out there with a good hand for nice looking graphics ;-)
I started a little (now, its a bit more complex) tower defense game at least 6 months ago. Now, as it's getting colder out, i have a little bit more time (after my family) to start working further on it.
A lot of ground programming is done, as pathfinding, building, upgrading towers, with zooming in and out. Framerate is configurable. Enemies are also configurable to attack towers. Towers range, health, firepower and behaviour [shoot nearest, weakest etc. pp] is configurable (programmatically at the moment).
So, i used some tiles from other programmers (asking them before) but im not lucky with the graphics at all (and as you know, a game is getting better with it's graphics ^^). The graphics itself is 2D and i'm in need for all graphic related things, as splash screen, menu layout, playfields and of course, towers and enemies (mostly of course animated) - where tilesize should be 64 or 32.
AND of course, it's not ready made yet. It needs a lot of overhaul at the end (as game balancing, level design, difficulty level ...).
So, if anyone is interested in such a game (yeah, i know, there are a lot out there ... but maybe there are some nice ideas - improvements?) - send me a pm or reply in this thread
Id be interested in lending a hand, though it depends on exactly how much work you need. But I'd certainly be interested in hearing some more info about the style / theme you were going for, and I might be able to help out ~
splinter82 said:
Id be interested in lending a hand, though it depends on exactly how much work you need. But I'd certainly be interested in hearing some more info about the style / theme you were going for, and I might be able to help out ~
Click to expand...
Click to collapse
i need all graphics to be done. i've "borrowed" some graphics from other sites, asking the developers first, but the tilesets are not enough and i'm not really familar with graphics design (also simplest graphics )
what i need (and your imagination may have no limits) are:
- tilesets for towers
- tilesets for enemies
- playfields or "rooms"
- explosions
- projectiles
- maybe a well designed icon
format of tilesets (or single tiles) may be discussed, i prefer 32x32 or 64x64 tiles.
the style is not choosen yet. currently, style is medieval. but i really don't like it much and graphics looking not that good. style itself should not depend on implementation. as i wrote already, most of the implementation is done, graphics are changeable. so, if you're really interested, i may give you some short shots to get a picture of what's done so far.
and yes, graphics work is mostly 50% of the work ... the more eye candy an app is, the more successful.
Digital Eclairs went to Pinewood's after school program called AppLab, focused on getting kids more hands on on new electronics coming up.
We presented our project XnO, with multiple handled devices to kids (age group 8-12). After the first 15 mins of hands on experience, they were really enjoying the gameplay, comparing it to different games titles and how it was better, why they liked 3D, asking questions on when the app would be released, and they were very interested in knowing about the process of how it was created.
It showed us that 3D environments were a welcome change, kids respond well to warm colors we used. We set each kid on a different level and they seemed comfortable playing and getting familiar with the app. Some kids responded very well with the higher levels and some not so well because we had not ramped them through the initial gameplay, but after a few tries they started to get the hang of the game and when they were able to win they were really happy. In retrospect we realized that this was a bit of a difficult learning curve for someone new coming to this game, but with the release upon us we had to move forward with what he had. In order to give people a taste of the game on the iOS we released with a showcase of 5 levels, which looking back on it now, care is needed when choosing the level of difficulty to the casual gamer.
The Accelerometer presented an interesting challenge to the kids, once they figured out they could lift the device and tilt it left and right to move the character they were able to pick up on it quick and continue with how they had been completing the levels previously. We were short few devices and a few kids had to share the same device. The ones who were collaborating did very well on higher levels taking turns and really engaging in the game and helping each other and were faster in adapting to the game. This helped us understand that putting out a physics puzzled based game would definitely require a walkthrough to help the community through some of those tough levels.
As a developer with our first game a week away from release, it was an exhilarating experience to see our product being enjoyed by these kids. Their eagerness to explore all the game features gave us so much satisfaction and all the pain and efforts in building this game were totally worth it. The kids were very interested in knowing the process of how the game was made and when they were asked for feedback they all jumped in saying: They loved double headed turtle and wanted a three headed turtle, in-game currency that they can use to buy in things in game like weapons, wallpaper, and many more suggestions.
To anyone who want to make their own game, arrange group play tests ahead of time once you have a working build. You will get wonderful insight into your game. We had initially done a lot a individual testing from industry people, which is very useful and should not be ignored but for a complete overview on a game and end user perspective go for group tests, as individual test can sometimes be misleading. And do it as soon and as often as possible.
Digital Eclairs, is an independent game development studio. XnO - 3D Adventure Game is launch on iTunes and Google Play.
No story is complete without its origins. We love to share with you the very first white-box environment of XnO!
XnO began its origins from the name "Ice Breakers", the way the cylindrical blocks were breaking. We had 3 walls couple of boxes from unity asset packages. And began the journey. We wanted to take a simple idea and implement in it all the possible depths.
When we began majority of the games were 2D or side scrollers, that never gave the player full satisfaction of real life interaction with physics of the objects. So we chose a 3D engine, as to why "unity" - the amount of tutorials, community support and ease of start was a key factor in choosing that engine.
To be a team you would need atleast 3 components to begin with - programmer, 2D/3D artist and level designer. Not to say one person can handle more than one aspect. As a team we were all on the same page, we want to make a physics based game with focus on gameplay first.
We followed the following steps:
i) Create first level - We used very basic components - rectangle, sphere, cylinder to create a game play scenario.
ii) Create a flow through of the game - Main Menu, Options and Level Select Screens. Once this was done adding new levels was very easy.
iii) In Game HUD - To enter and exit from any level
iv) Uploaded a web version for our friends/family to play.
Once we had all the pieces then we focussed on exploring all the possible depths and variations in the gameplay that can be achieved to make the game engaging and fun. In our case - target variations, introducing obstacles, power-ups, use of accelerometer to enhance gameplay. Once we had built the key features in, we explored on how to increase difficulty of the levels as the game progressed. At this stage we made some of our models, used some from unity and still used royalty free music.
Once we had good 20 levels working with all the above, we started showing it to people who either played a lot of games or were in gaming. This gave us a good insight on how improve.
As an indie developer it was so much easier for us to do the white-box the way we did because we focussed on Gameplay and Game Design, not so much on the art in the beginning. So when we got the feedback to change, it was so much easier to do it. We were never set in stone.
XnO is our attempt at making a 3D game with as close as possible to real physics without sacrificing the gameplay and memory footprint of the game. XnO is now available on Google Play and Amazon App Store.
We all love the Nook but it's getting kind of old in the tooth.
Ok, the Glow4 (7.8") finally upped its game to 1 GB RAM, but that was kind of necessary.
It also added Bluetooth, something that could have been done cheaply and easily to earlier models.
Although I'm no fan of using the latest and greatest Android version, 4.4.2 is getting a bit old.
I understand that this is a tough business where every little part on the BOM (bill of materials) will hurt you.
Still, using single core processor is so yesterday. A Raspberry Pi Zero has quad core for $10-15.
To my mind a 6" 300 DPI reader is about optimal for flowing text reading.
For frequent or work PDF reading I'd want a 10" 300 DPI reader instead of high power reading glasses.
The 8" reader seems to fall uncomfortably in the middle.
The Kobos are Linux based, not Android.
Onyx has some decent choices in their (confusedly similar) product palette.
The older stuff has Android 4.4, the newer stuff Android 9.0
They have quad core and even octa core.
The "Poke 2" looks pretty nice for a 6", but why did they have to add the silver styling?
https://onyxboox.com/boox_poke2
(Oh, well, some sandpaper and a can of black spray paint would fix that.)
As I am in love with the Aard dictionary, my NST has been simply wonderful. But I understand Kobo no longer support an SD card. Where to now?
Same boat. I just got rid of my GLP BNRV510. Hated the light grey, small dictionary font. Also reading PDF seemed to convert those documents to oversized images. My NSTw/GL was awesome. I was going to upgrade to the new NGLP7.8 but the specs and issues with overheating are a turn off. Also I have read reviews stating that you can't side load books anymore? This may also apply to the GLP BNRV510 with the latest firmware update too. Which eReader now?
The Glow2 (BNRV510) is my main read.
If I have to read a PDF, I read it in landscape at two "chunks" a page.
I wouldn't think that B&N would try to lock down sideloads and I don't anticipate it would be hard to defeat.
I hope not but I understand the arguments for your question. To be honest NST as it was not my first choice (first choice was some Sony model) but I love it now. Last time I checked Kobo Aura looked nice but that was long ago and I do not know how things look now on the market.
Recently I was scrubbing my head around this issue. How I see the problem with NST? Well B&N locked out anything and everything humanly possible to prevent users doing something they did not wanted them to do. Devs unlock most of the obstacles out of protest or because of challenge ahead. As it runs ancient version of Android apps are scarce and disappearing fast. Writing an app dedicated for NST might be an act of love toward hardware base made by dedicated fanatic but we can assume there are not to many such individuals around today as Rennate said Nook is old.
So without further ado there are few roads as I see that could be taken if NST is to continue ahead.
1. Upgrades to Android version as far and much its hardware allows and using slightly more up to date apps for it (like CM11 approach running from SD card allows).
2. As Android is just an overlay on Linux leave it as is for B&N sake and good sleep but make some dual boot solution that will actually allow us to boot Linux (something in the line of Ubuntu for devices but not exactly so because as far as I remember that work only for versions of Android above 4) as that could give user maximum possible ability to customize it for his/her use.
3. Just say bye to B&N and build new NST OS from scratch be it Linux or another version of Android as that might be easier due to a clean slate/paper ahead and being less bound to a obstacles made by B&N.
4. It might be possible to create also dual profile on the current NST OS but given its restrictions that might not be of some great use - (B&N profile and user profile). What other forum members think about it?
P.S. I did not want to create separate thread about this and this thread seemed to fit in the general idea of talk about it. I hope Rennate wont mind.
Nah, I don't mind.
I use the same reader app on my Glow2 and everything else, including my $70 Walmart Onn 8" tablet.
Even a cheap-o (single CPU) tablet has 2G vs the Glow2's 0.5G
For better or worse, people like the Android ecosystem as a way to make apps.
Of course, Google & Co are working on making everything ginormous and expensive.
(And adding even more pointless animations.)
It's always a question of how much work you want to put in to fight annoying things.
Renate NST said:
Nah, I don't mind.
I use the same reader app on my Glow2 and everything else, including my $70 Walmart Onn 8" tablet.
Even a cheap-o (single CPU) tablet has 2G vs the Glow2's 0.5G
For better or worse, people like the Android ecosystem as a way to make apps.
Of course, Google & Co are working on making everything ginormous and expensive.
(And adding even more pointless animations.)
It's always a question of how much work you want to put in to fight annoying things.
Click to expand...
Click to collapse
I am glad that you do not mind and find this discussion still within topic you started.
As always you hit problem in the head with much less words then me. I have always wondered what are the limits of hardware requirements needed (minimum) for some tasks/programs to run reliably. And we see that people test those boundaries each day.
You are correct that Android had given people app making opportunities. Sadly recent trend is to take away that from us on old devices as this one. I agree that "awww look its so shiny and buzzing" might look nice but regarding information value its pretty much crap (no way to put it politely sorry). Information is what the people using books/ebooks find to have some merit and it is in the form of text, graph, still picture mostly. I accept that sometimes video can be better tool for presenting certain information but general trend is not in that direction. Information in any shape and form I will accept gladly. Sad truth is that today we have to duck and fight against flash advertising and eye candy web UI of very little value and dubious quality.
I have some doubts what would be the most likely way to continue that is why I made that post. If it was my thread I would make a poll but even here I am willing to hear what is your opinion? Amongst four options I wrote up what would you most likely choose as a way forward? Also if possible please explain why.
1) I think doing an upgrade of Android version on an older device is a bunch of work and hardly justified.
2) I'm not a fan of dual boot. I like to keep things simple. Especially on my main reading device where I just want to pick it up and read.
Android "Linux" has quite a few different things than normal Linux. If you want Linux, get a Kobo.
3) Porting something new to the NST is a lot of work. See #1
4) I don't see the necessity of dividing profiles. I also don't understand what you're looking for.
Ok, I'm a fan of the NST, but it's had its day. The Glows have better resolution and backlight.
You get your choice of capacitive (Glow2) or IR (Glow3) touch screen.
The Android 4.4.2 on the Glows is not so bad yet. (The NST Android 2.1 makes life difficult.)
I think more memory, Bluetooth and a better processor would be on my wish list (in order).
Yes, the Glow4 has Bluetooth.
With enough effort you can fix any little technical thing in life that annoys you.
(I just spend this morning grinding and filing down a piece on my brand new guitar because I couldn't stand the design.)
It's a question of time and also how many people your effort would help.
I think an Onyx Boox is in my future, but I wish they didn't have so many silly models.
It's funny, I still use my original Nook Simple Touch, but a few times a year I find myself curious and looking to see if there's a perfect e-reader out yet for me to upgrade to. In the end it always just seems like nothing is really so much better that I really want to buy it, though.
In particular, page refreshes and overall responsiveness, which are the main things I'd like to be better, still just haven't improved enough on affordable e-readers, in my opinion. A backlight would be kinda cool, but hardly seems like a big deal since personally I'm still pretty used to reading real books, which obviously don't have built in lighting either. I guess a higher density screen might be nice, but I can't say I really notice it on my NST. Newer Android? Maybe, though I've really always been able to find an app that does what I need and works on the NST even with Android 2.1, so I'm not sure what the advantage would be.
I'm a pretty light user of my Nook, though, I guess. Most of the time I'm just reading epubs or sometimes pdfs (scientific papers, which are usually published as double columns, so they work just fine on the NST screen), plus the occasional word games or round of picross here and there. Someday I'm sure I'll upgrade to a new reader, but I think it's gonna be a while at the rate the technology has been improving.
You have stated all valid points here. I understand them and agree to most. Maybe I should explain in more details my points.
I use NST as is. Still restrictions imposed on user by B&N are frustrating sometimes. I mentioned upgrading Android on the device only because its own base is abandoning 2.1 and cutting of access to application made for this version. I have nothing against sideloading apps but if the source to such apps is going to dry out it might be a time for a change. Theoretically with slight upgrade of Linux kernel on it upgrade to gingerbread/honeycomb looks doable. Is it worth the effort is a valid question and that is exactly what I am asking for opinion here.
I am mostly using an OS from that Redmond firm. Although I want to learn and use Linux more I am certainly not looking into using it on e-reader despite it is possible to do on Kobo. Point of dual boot would be to leave B&N stuff as is and do on Linux what you like. At least on Linux you would not be that easily cutoff from apps you want/need. Again looks doable but I am not sure if it is recommendable. Reason for me to considering this is that more and more I read about trying to write/rewrite an apps for this device. Even I have started something similar to porting Linux program to Android and being frustrated by next to nill progress so far started to wonder am I doing it backward and should I run Linux on NST and program in the environment it was written for.
I am surprised Renate is not for whole new OS because the way I see the things she is already halfway there with all the apps she wrote for NST. . I know OS is another matter but let's face it it was half baked product to begin with. I mean Phone.apk really? On a device without sound support! And that app control volume? Man B&N really had shoestring budget for software developer and had us use port of some phone OS instead writing dedicated stuff.
I find multiple profile least advised on such low power device but I could see its merit here and there. I have a cousin which would be happy if she had kids profile on its phone as that would prevent paying triple digit roaming charges. NST most likely do not have the power to pull of multiple profiles although in theory something like that could be made even for Eclare in some crumbly way.
NST have resolution just above low printing and we love it. If some device could achieve 300dpi and have larger screen A4 size preferably with A5 being minimum that would be awesome. There are few device on market Remarkable and Sony with 10 and 13.3 inch screen but they cost still an arm and a leg. Although they shifted concept more toward notebook/sketchbook I have no problem with that but e-book support is next to nothing PDF only if I remember well. I am old and I like to use "pen" on "paper". I will look about other device mentioned. Aura H2O did caught my eye once to be honest.
Now I hope you can see my points more clearly. I find this discussion fruitful. Even if we do nothing we at least have fresh input from others to tickle little gray cells.
As far as upgrades go, upgrading to anything less than Lollipop (5.0) is pretty pointless.
That's already five years old as it is.
As bloat is a given, you're always going to need more memory and a faster processor.
If you want to learn about Linux a Raspberry Pi is certainly an economical solution.
For ~$15 you can get a Raspberry Pi ZeroW.
Android *nix deviates a lot from Linux but mostly in system and startup issues.
You can cross-compile C programs on your Windows box using the the Android NDK and run them in the command line on your Nook.
You won't have direct access to the screen unless you want to write to /dev/graphics/fb0 yourself.
If you don't want the Android layer running at that time you can just turn it on and off with "stop" and "start".
You might try to get into writing regular Java (or Kotlin, but don't get me going on that) applications.
There is something to be said for having your own app that runs on both your phone and your Nook.
There's a lot of convenience in having whatever you're looking for on whatever device you have at the moment.
I always though that backlights were pointless, but I've learned to love them.
If you have copier paper a lot of it is 92% reflective.
The white in eInk is a lot grayer than that.
I always keep my backlight on, but only to the point that it makes up for the gray tint to make it white.
Looking at it you really don't get the impression that it is glowing.
I have stumbled on web page of a project to port some 4+ Android version on NST which pretty much surprised me. Can not remember was it ICS or JB and hell Kitkat would be awesome for device that old. I believe that for that they must abandon B&N stuff almost completely unless they somehow ported it back from Glow versions? And counting in size expected I bet that they reformatted partitions on the device to make it happen. Now will that stick together or fall apart spontaneously is another question. I remember that on xda that somewhere was a thread about disabling OTA from B&N that could brake such upgrade but since they no longer support NST we should not worry about this. I wonder why did you said Lollipop as minimum choice? Do you consider it as minimum acceptable Android version or maximum that NST could possibly run?
As far as Linux go nah I will just play with old laptop instead. Although I caught myself looking to buy present for nephews in electronic realm. Arduino or Pie? aye there is the rub...
I didn't program anything reasonable for a long time. Therefore I am more than rusty in that field. Although I believesome Python or lua script I could manage if enough effort is put on my side.Julia look to me as a programming language that shows some promise to the future from old man perspective. Certainly none of those are useful to porting anything to Android and NST. For the moment I cut my appetite back and will look into how I can backup NST and make virtual image out of it to run it in Virtual box. There I hope to try to learn how things work on Android an play/apply changes in the sand boxed environment. If I break something no harm done just delete virtual drive and start again. I don't want to brick my only NST. Maybe I should buy used one for latter to as I see lot of UK used one have hit the market after B&N closed in UK.
I hate Java from reasons unwilling to disclose or as you said let's not start about that. Idea behind it is fine. Sadly it is lot to be desired on the implementation side. I totally understand that Java might give some benefits especially if we count in the already existing base of programs written on Java. Have a friend who learn and use Java but I personally never manage to overcome my personal detest of it.
Regarding backlight... I never saw Glow. Is there true backlight in like shining through panel? Or did they made something in line of those book lights for real books? I think that could work for capacitive screen but not so much so for IR like NST have. That should not glow much I think and could be regulated in illumination and colour.
The NST has 256M RAM, the Glow2/3 has 512M, the Glow4 has 1G, my $40 phone has 2G.
The $60 Kobo I have has only 256M, but it just runs Linux.
I couldn't be bothered to update my NST even if you handed me an image on a platter.
ebay has the Glow4 (open box) for $130.
I wouldn't even try to update that to a newer version, too much work.
Since this thread started the Boox Poke3 6" reader has come out.
It has Android 10, 8 CPUs, 2G RAM, Bluetooth and lists for $190.
That's a heck of a lot more of a device than the Glow3 for $120.
It also doesn't have the ugly styling of the Poke2.
https://www.boox.com/poke3/
Hmm, currently not in the US warehouse.
I'm a big fan of Arduino and RPi, but it gets complicated.
An adult friend bought an Arduino, hooked up an LCD and a thermometer, loaded the sketch.
It worked. They got bored. End of the story.
I don't know what the solution is. You make it too easy, they get bored. You make it too hard, they get frustrated.
I'm not a fan of the whole Arduino infrastructure and the Processing language. I prefer just AVR8. But I am "old skool".
I use RPi a lot, but I've only seen the desktop version about once.
I use headless and also digital signage without X Windows or desktop.
The Glow2 has single color edge lit backlight, The Glow3/4 uses dual color (blending) edge lit backlight.
If you hold them sighting down the face of the screen at a very low angle you can tell there are discreet LEDs.
(It's nothing you could ever see in normal usage.)
I checked Boox first time you mentioned it. Impressive progress I must say. Paradox is that as I understand newer Android versions are more optimized to be run even on underpowered devices but I agree that NST is both old and underpowered. Still even you mentioned that Kobo has same low memory but still running successfully Linux only environment. That speaks a lot in Linux favor regarding resource management and use. Yes there are slim chances someone cook something up for NST and even then people will just buy new device that is several times better. You wouldn't believe but B&N readers are hard to find here. I had to ask a friend to bring me the one from Middle East because it was available there so go figure.
Thanks for the opinion about Arduino vs RPi. I think you might be right. Kids nowadays will be interested to program more than to assemble something and experiment. Its a shame because I think they could learn more about physics by fiddling with Arduino.
Thanks for explaining me or rather confirming how light on Glow device is made. I am curious how they sorted out possible interference of lighting with IR touchscreen but I guess they somehow used non overlapping LEDs for those two separate things or passthrough IR only filters on IR detector side. In theory even some simple software calibration could work for that but I am also an "old skool" and wouldn't choose that as my way had I have gotten the task to build something of this kind. I might rig me some "lights" for old fashioned hardcopy books. Not that I can't buy it online but I want to engage my fingers a little.
If you haven't played with it yet, the Touch-1.0.apk (in the sig) works on the NST and will show you how/where the beams of IR go.
It can be helpful to see where dirt or distortion of the bezel is making it difficult for touches to be registered correctly.
Since the party seems to be going into a topic of what next best e-reader should be maybe we could exchange opinions about certain things available as in are they necessary or good enough at this moment. For example Boox is offering a model that can show ebooks as black and white or I presume as 4 color "print". As B&W it present it as 300dpi which is on par with printed books and man can not ask for more in my opinion. Alas when it present 4 color "print" it is meager 100dpi that could mean even NST just blows it out of scene. So my vote on color e-reader is still no. If it ever reach 150dpi it will become a thing to consider but right now it is still under acceptable performance from mine point of view.
Do you consider making notes on a device important? I am asking because I have mentioned ReMarkable and Sony DPT (which is gone now). Sony again made good device only to withdraw from the market at the end. While I understand that in the e-reader case as Amazon blow them out securing the better library this time I am afraid it is Sony's own fault. There exist few rebranded models of hardware Sony used with seemingly better software Fujitsu Quadreno and Mooink Pro. Mooink support PDF, epub, docs and text and offers a software for file conversion and DRM management. There are few annoying things. Almost none have microSD card option now. It is replaced with cloud storage or printing. And I personally like having pen but I find being robbed when they sell it separately and with replaceable tips because they made those to wear out. Cost is way to high despite larger screen.
I'm not clear on what you mean with "4 color".
The only thing that I can see on the website is a way to save your scribbles to an external file where you can set the color saved (but not viewed) on the device.
If you've ever seen a store white/red/black eInk shelf label update you'll know that that's only useful for things that change once a day.
I don't look too closely at the reader software itself since I'll probably just use my own.
I hate the sort of pictograph selection of small, medium, large font.
What if I want 5% larger than medium?
There's always a bit of conflict between SD card and waterproof.
I figure 32 GB fixed storage is large enough for me.
There's always a big tossup what is the correct mix of devices, phone, ereader, tablet, tablet with pen, tablet with keyboard, laptop, desktop?
I've never owned a personal laptop, never seen the sense (for me).
Rarely do I use a tablet or a phone with a BT keyboard when I want to do some sort of bulk inputting or fleshing out an idea or transcribing lyrics.
I kind of like digitizers, but never found a way that the utility exceeds the space they take.
Onyx Boox Poke 2 Color is for example device able to reproduce color. Yet is it worth buying?
Yes I understand your choice to use custom reader software. File support seems to have always been a problem and it just went worse from there.
Yes waterproof device shouldn't have SD card. I have mean more in a sense of having the ability to root, backup and thinker with the device.
SJT75 said:
Onyx Boox Poke 2 Color is for example device able to reproduce color.
Click to expand...
Click to collapse
The product selection of Onyx or Boox or Onyx Boox has always confused the heck out of me.
Currently on https://www.boox.com/allproducts/ there is no indication of anything color.
Moreover, the "About Us" speaks of "We focus on E Ink ( ePaper) devices only. "
But I do remember seeing something previously on the website that spoke of color.