Re: Do we have a Nokia Internet Tablet in waiting? Tabco
 

Developer FAQs
What are the application development environments that will be supported on LiMo 4?

LiMo 4 will initially support Flash, AIR and WAC runtimes. In addition, LiMo OEM Members may potentially support native development.
When will SDKs and a LiMo developer program be available?

Instead of launching its own ecosystem, LiMo is supporting existing ecosystems such as WAC and Flash. Therefore, 3rd party developers are encouraged to use Adobe tools and WAC SDKs to develop applications for the LiMo Platform.

How will LiMo ensure compatibility (interoperability of 2nd and 3rd party apps) across LiMo devices from multiple vendors?

LiMo will make a Conformance Test Suite (CTS) available to OEMs planning to ship LiMo devices so that they can certify their devices as being LiMo compliant, thereby achieving application and middleware portabilty /interoperability.

Re: Do we have a Nokia Internet Tablet in waiting? Tabco
 

I've never mentioned C. GTK+ has bindings for many languages.

But why do you think it is not well suited for writing applications?

Re: Do we have a Nokia Internet Tablet in waiting? Tabco
 

While reading up on the whole Tabco subject, I've noticed a facebook comment mentioning german Ayinger Beer. According to their website, it's not widely distributed worldwide – but there is a company importing it located 10 minutes from Nokia Headquarters in Espoo.

If that's actually relevant at all, it might be interpreted as a pointer to at least former Nokians. :)

Re: Do we have a Nokia Internet Tablet in waiting? Tabco
 

The name TabCo keeps being misread--in my mind--as TOBACCO. :P I can't WAIT to see the first sets of OS patches. TABCO PATCHES!

Re: Do we have a Nokia Internet Tablet in waiting? Tabco
 

I just keep thinking "Tabasco" my favourite sauce.

I could picture a small group of ~80 people that were fired from Nokia after the Elopocalypse, that banded together to create the "TabCo" group.

They already knew Nokia's roadmap, so the best possible thing for them would be to:
Design a tablet with a NOKIA-esque to it.
Implement the latest MeeGo builds, particularily Alien Dalvik (a la RIM PlayBook).
Generate a viral marketing (since they can't market it themselves).
Scrap enough funding to sell it, similar to the success (failure?) of OpenPandora.

Re: Do we have a Nokia Internet Tablet in waiting? Tabco
 

I would love if that was true. Unfortunately it's not.

Source: Chuck Norris

Re: Do we have a Nokia Internet Tablet in waiting? Tabco
 

I'm quite sure it's coming from the Joojoo guys. The mockup they show in the videos is identical to the Grid tablet that appeared at FCC, they are americans and their CEO is really from Singapore.

PS: that and the else OS ;)

Re: Do we have a Nokia Internet Tablet in waiting? Tabco
 

Am I the only one to check TabCo's domain registration?

Interestingly enough, it's changed recently.

First time I checked it was:

Now it's

...so they stripped out the location info... hmmm... EDIT: or for unknown reasons I'm just getting different results (see post below)

http://www.whois.net/whois/whoistabco.com

Re: Do we have a Nokia Internet Tablet in waiting? Tabco
 

I still see location info in my whois:

Re: Do we have a Nokia Internet Tablet in waiting? Tabco
 

Because developers are lazy. Including myself :)

I did some apps using Gtk+ some years ago and nothing wrong with this toolkit.

But now I prefer Qt(Quick) it has more potential even for commercial apps etc...

And even if we prefer opensource we have to realise some apps will never be open and commercial devs prefer Qt over Gtk+ mostly because Qt is more "complete framework". That was probadly one reason Nokia dished Gtk/manyclibs in favour of Qt...

Just take a look at N900 and Maemo5 its WAY easier write apps using Qt(Mobility) instead of talk to lowlevel libs in C on Maemo5.

And yes I know there are SEVERAL bindings for Gtk+/Glib but in a way this gives more headache cause then those bindings has to be "extra" loaded in memory. Atleast in case of C -> C++ bindings its a drawback. In case of Python I guess its the same(drawback)...