<qi-bot>
[commit] Werner Almesberger: cae-tools/cameo/fped2stl.pl (flush): substitute coordinates only once (master) http://qi-hw.com/p/cae-tools/e62da4e
dos1 has quit [Ping timeout: 272 seconds]
dos1 has joined #qi-hardware
kristianpaul has joined #qi-hardware
kristianpaul has joined #qi-hardware
dos1 has quit [Ping timeout: 272 seconds]
valhalla_ has joined #qi-hardware
valhalla has quit [Ping timeout: 272 seconds]
xiangfu has joined #qi-hardware
jekhor has joined #qi-hardware
lekernel has joined #qi-hardware
wolfspraul has joined #qi-hardware
apelete has joined #qi-hardware
larsc has quit [Ping timeout: 272 seconds]
larsc has joined #qi-hardware
dos1 has joined #qi-hardware
rz2k has joined #qi-hardware
viric has quit [Remote host closed the connection]
viric has joined #qi-hardware
jekhor has quit [Ping timeout: 272 seconds]
jekhor has joined #qi-hardware
wolfspraul has quit [Ping timeout: 246 seconds]
wolfspraul has joined #qi-hardware
rz2k has quit []
rz2k has joined #qi-hardware
kilae has joined #qi-hardware
rz2k has quit []
<DocScrutinizer05>
aaaaand level-II accomplished
<DocScrutinizer05>
\o/
<kristianpaul>
hmm?
<wpwrak>
whoo !
<wpwrak>
before you know it, you'll have one of those 100x over-funded projects on your hands ;-)
<larsc>
time to start looking for a nice island in the caribbean to buy ;)
<roh>
level2?
<larsc>
15k
<DocScrutinizer05>
15k in 3 days isn't that bad
<DocScrutinizer05>
particularly *donations*, not any preorder with refunding warranty crap kickstarter
<DocScrutinizer05>
and still a lot of "destinations" is not even supported (quite unfortunate :-/ )
<DocScrutinizer05>
I had 3 requests from users in china and other non supported destinations just today. Poor Nikolaus will receive a number of emails
<DocScrutinizer05>
probably harmattan is closer to sailfish than to fremantle
<DocScrutinizer05>
well, s/sailfish/nemo/ (aiui)
<roh>
i see
<DocScrutinizer05>
the whole concept of meego/harmattan based on QML and thus is kinda similar to other browser-based "OS" (rather: "desktops") basically
dandon_ has joined #qi-hardware
<DocScrutinizer05>
you still *can* develop plain X11 apps usng whatever toolkit for gfx you like
<DocScrutinizer05>
on sailfish/nemo they use some Qt flavour still, I think, but they discarded X11 and go for some wayland crap that not even supports X11 via compatibility layer anymore
<DocScrutinizer05>
for me that starts to tase stale, when it's abled 'linux'
<DocScrutinizer05>
labeled even
<DocScrutinizer05>
kinda reminds me at that qtopia episode
dandon has quit [Ping timeout: 240 seconds]
dandon_ is now known as dandon
<DocScrutinizer05>
to me sailfish is as much linux as OSX
<DocScrutinizer05>
and it's completely up to everybody's guess how open the whole jolla phone and OS incl core apps will be in the end. It seems they again go for "differnetiation" and similr excuses to not make their core apps like dialer etc or even the whole desktop FOSS
<DocScrutinizer05>
and definitely the whole UX concept moved focus from the NIT-paradigm to the smartphone/iPhone-MeToo-thinking
<DocScrutinizer05>
"user doesn't need a unix system. User wants apps"
<DocScrutinizer05>
BS
<DocScrutinizer05>
"we go wayland so we can playback HD" - WTF?!? Who needs HD on a 4" display?
<DocScrutinizer05>
play your dang HD to the HDMI output (so there's any such thing on your hw) using a mplayer specialized to do exactly that
<DocScrutinizer05>
leave alone the device display and the display server that handles it!
<DocScrutinizer05>
playback of HD on a 800*480 (or whatever) display - I must suffer from delusions
<DocScrutinizer05>
ubuntuization
<wpwrak>
well, they're putting ultra-high-res displays into those obesity-enhanced "phones" now. probably to give that hecacore something that will keep it at least 10% occupied.
<DocScrutinizer05>
yeah
<DocScrutinizer05>
and special siuts that have dynomos at every joint, so you recharge the 7Ah battery with every move you do
<DocScrutinizer05>
grr. suits, dynamos*
rz2k has joined #qi-hardware
lekernel has quit [Ping timeout: 240 seconds]
lekernel has joined #qi-hardware
pcercuei has joined #qi-hardware
unclouded has joined #qi-hardware
kilae has quit [Quit: ChatZilla 0.9.90.1 [Firefox 24.0/20130910160258]]
<qi-bot>
[commit] Werner Almesberger: cameo/fped2stl.pl: new options -x and -y to flip on X and Y axis (master) http://qi-hw.com/p/cae-tools/5b70e92
jekhor has quit [Ping timeout: 240 seconds]
Luke-Jr has quit [Read error: Connection reset by peer]
Luke-Jr has joined #qi-hardware
<eintopf>
yay
jekhor has joined #qi-hardware
jekhor has quit [Ping timeout: 260 seconds]
jekhor has joined #qi-hardware
Luke-Jr has quit [Read error: Connection reset by peer]
jekhor has quit [Ping timeout: 272 seconds]
Luke-Jr has joined #qi-hardware
Luke-Jr has quit [Read error: Connection reset by peer]
Luke-Jr has joined #qi-hardware
Luke-Jr has quit [Read error: Connection reset by peer]
Luke-Jr has joined #qi-hardware
<wpwrak>
CAD modeling, the Bruce Willis way :)
Luke-Jr has quit [Read error: Connection reset by peer]
Luke-Jr has joined #qi-hardware
Luke-Jr has quit [Read error: Connection reset by peer]
Luke-Jr has joined #qi-hardware
rz2k has quit []
<whitequark>
DocScrutinizer05: arguably there *is* an advantage for high-res displays. they just look nicer.
<whitequark>
you may not care for the quality of the thing you stare at for the better time of the day, but I do. the more DPI, the better (until it hits the resolution of the eye.(
<whitequark>
*).
<whitequark>
btw, another thing wayland solves is display tearing, which *is* important when you want to have smooth animations, which *are* important to have usable touch UI
<whitequark>
it's somewhat overhyped, yeah, but unimportant? no way in hell. if you weren't doing a touch device at all, now that would be interesting, but as long as you do, you have to play by the rules.
<wpwrak>
the problem with high-res is sourcing. there are three interconnected parameters, 1) bleeding edge, 2) openness, 3) your wealth. you have to sacrifice at least one.
<wpwrak>
so if you want bleeding edge AND openness, you better be prepared to purchase a company like broadcom, qualcomm, or similar, just to get the rights needed to open a bleeding edge product.
<wpwrak>
if you want bleeding edge and don't have that kind of money, you have to live with closed hardware.
wolfspraul has quit [Quit: leaving]
<whitequark>
that's true. I just wanted to say that bleeding edge is not all just bells and whistles, regardless of whether we can tap it or not
<wpwrak>
or you lower your demands in the bleeding edge area, and you have a chance to get something done that's open and still doesn't require millions
<wpwrak>
yeah, it offers some benefits. but in many cases, you only notice them in a side-by-side comparison.
<whitequark>
well, if not for side-by-side comparisons, we'd still all be running windows mobile 5 :) it all depends on what's your top priority.
<whitequark>
wait, russia is not a supported destination for neo900?.. sigh
<dos1>
isn't the dpi of devices like freerunner or n900 already high enough to be near eye resolution?
<wpwrak>
for me the main goals would be 1) does it handle basic everyday use well ? (e.g., if it already sucks to send an SMS, i may not like it) 2) is there a good way for people like me to add nice things ? 3) will it live long enough to actually make it worth my time to learn about all the cool things it can do ?
<dos1>
russia is supported, but via individual contact
<whitequark>
dos1: not nearly. my e973 has 320 dpi and it's slightly lower. I think at typical view distance for phones it's around 350 dpi.
<wpwrak>
dos1: the gta01/gta02 had, at their time, the highest resolution in the market. probably by a good margin. i think that proves that resolution alone isn't enough :)
<whitequark>
wpwrak: (main goals) I agree, though to me there's less of 3), and more of "do I will resent myself every day for buying this device at all?"
<wpwrak>
and of course, they were darn slow as a consequence. especially after adding the g-lam(e)-o graphics decelerator :-)
<wpwrak>
whitequark: i count on superior human adaptation skills ;-)
<whitequark>
wpwrak: actually, neo900 isn't that not-bleeding-edge
<whitequark>
plenty of RAM, more storage than my current phone, decent sensors and communications and camera
<wpwrak>
whitequark: and usability is much much more than just pretty pictures. you have to understand the workflow. e.g., once had an HP 100LX, monochrome CGA. it had a calendar with a great monthly overview. i've never seen anything like that afterwards. it wasn't fancy, far from it. just a very clean and efficient implementation of the concept.
<whitequark>
wpwrak: (main goals) I agree, though to me there's less of 3), and more of "do I will resent myself every day for buying this device at all?"
<whitequark>
errr
<whitequark>
what the hell irssi
<whitequark>
what I wanted to say: "the CPU isn't dual-core, but that's not going to matter with the smaller display, I think"
<whitequark>
if it does the job well, the only thing I would truly miss when compared to my current phone is 802.11a
<whitequark>
well, an
<whitequark>
it's weird when your cellular is faster than your wifi
<whitequark>
wpwrak: (usability) sure, but FOSS isn't exactly known by its great UI.
<wpwrak>
1 x 1 GHz ought to be plenty :) i kinda wonder by how many orders of magnitude, say, android applications are slower than just native C would be.
<whitequark>
wpwrak: for non-computational workloads, by not much. it much more depends on, say, properly tuned GC and task priorities than raw computing power.
<whitequark>
also, on android you can always drop down to native.
<wpwrak>
usability is mainly about workflows. most of the things you do, you do often. so a nice gui helps you on the first two days, but doesn't matter all the years after.
<whitequark>
it's not "nice" as in "intuitively understandable" (no such thing?), but just well-done. I don't want my everyday workflows to take 5x more time than necessary.
<wpwrak>
hmm, then they must have lots of delay_loop_ms(10); in their code ;-) or maybe all the supercharged cores are indeed just idling :)
lekernel has quit [Quit: Leaving]
<whitequark>
wpwrak: android <4 used to not prioritize GUI like iphone did, hence it felt *much* more sluggish than iOS on slower hw
<wpwrak>
yes, agreed. efficient workflows. show me what i need, let me do what i want, and (often overlooked) let me undo my mistakes.
<whitequark>
android 4 fixed that, in 4.4 they did tons of changes to GC which should make it even better.
<wpwrak>
well, that sounds like inefficient toolkits or inefficient use of them
<wpwrak>
heh, that's what you get for using languages with GC ;-)
<whitequark>
remember that it was originally developed for keyboard interaction, not touchscreen
<DocScrutinizer05>
I think anything >>300dpi is nonsense
<whitequark>
and with keyboard you don't have to center all your flow around smooth drawing
<wpwrak>
in the old days, you probably wouldn't even have implemented free() or GC if you had had 1 GB of RAM, since you could never fill that anyway ;-)
<whitequark>
android predates touchcraze by several years
<DocScrutinizer05>
unless that's a headmounted display
<whitequark>
DocScrutinizer05: you're right, I got wrong numbers.
<whitequark>
retina is exactly 300dpi
<whitequark>
well, exactly 326. :)
<whitequark>
so my LG should be somewhat under that.
<whitequark>
(retina) as in iphone display.
<wpwrak>
openmoko had some 283 dpi. that was pretty crazy.
<dos1>
n900 is 267 dpi
<wpwrak>
more than enough :)
<whitequark>
dos1: so, about same. nice.
<dos1>
and openmoko devices came years before apple "retina" displays :)
<whitequark>
interesting
<DocScrutinizer05>
and HD is what? 1080 lines? per 2"? 1.5"? on a usual normal sized phone like jolla
<whitequark>
DocScrutinizer05: 720 usually
<whitequark>
1080 could be on galaxy note, passionately called "the shovel" in russia
<whitequark>
(not joking)
<wpwrak>
DocScrutinizer05: hmm, careful with "microSDHC". that name may be dangerous to use.
<DocScrutinizer05>
thanks
<whitequark>
dos1: ok, so you *do* send to russia with personal contact?
<wpwrak>
at least wolfgang mentioned that several times. (similar with MicroSD and such)
<whitequark>
DocScrutinizer05: btw, the fancy specs page mentions LTE as a given but goldelico one says 4G is optional
<whitequark>
which one is right?
<DocScrutinizer05>
see faq
<whitequark>
I see
<dos1>
whitequark: it might require some "workarounds", but I think there were already some successful goldelico buyers from Russia
<whitequark>
dos1: would you say be able to just use fedex?
<whitequark>
or dhl, *not* state postal service specifically
<DocScrutinizer05>
btw CBA to sign up to openphoenux ML to answer NeilBrown
<whitequark>
also, what would I need to select in the destination box at goldelico?
<DocScrutinizer05>
SIR should work without any initialization, OMAP3 UART3 supports it on hw level. So why shouldn't bootconsole on UART3 work via SIR?
<wpwrak>
DocScrutinizer05: what you need is procmail. then you can subscribt to all the lists you might possibly be interested in and have the stuff just go to a folder you never have to look at unless something really matters to you
<DocScrutinizer05>
and worst case we use IR LED like a wire to thransmit raw unencoded 8N1, stopbit dark, startbit light
<DocScrutinizer05>
wpwrak: I can do that with my mail client as well
<DocScrutinizer05>
but still I need to register to the ML to answer
<DocScrutinizer05>
of course I could answer to the CC that got me this mail from NeilBrown, and it would reach him and Nikolaus to deal with the external post to ML. But... CBA
<DocScrutinizer05>
it happens that N900 maemo kernel bootconsole is already on UART3
<wpwrak>
you must have some horrible repressed childhood memories related to mailing lists :)