Qt.io webservices

I am using chrome

Ooops. Bug. Thanks!

Thanks Alexandra. I have fixed the page. May I suggest to add a button for it, and to automatically transforms internal links into Wiki links?

Ah! You have to add @[[Category:Learning]]@ somewhere on the page. Top is probably best. It's going to be better documented soon.

Channels are central to ExpressionEngine terminology. Basically, channels are containers for content. If you're curious you can dive into the details "in the EE docs(EE Documentation)":http://expressionengine.com/public_beta/docs/overview/channels.html.

Just checked it seems it has been fixed now

My entry was not lost. It was successful posted. However, I had to login again to make another post.

After making the post only did I realize that "both(http://developer.qt.nokia.com/forums/viewreply/151/)": these issues might be related.

Thanks, and by the way, the list will be shorter soon. It's rather long now if you have posted a bit.

Thanks, I managed to hit the same error and we shall sort it out.

It's not replacing any blog - and the labs blog will actually get upgraded! But if you think about it; where would a "developer using Qt" (not a "developer of Qt" like yourself) go on our sites to find blog posts to their liking? Examples: non-Doc tutorials, Top 5 Embarrassing Qt Coding Epic Fails, compilations of Qt material in Spanish, Qt Creator tips 'n tricks, Qt Creator shortcut of the day, Qt Creator featured plug-ins, Qt WoW Client developer diaries, blog post 1 in a series of 5 about learning QML for those that barely know java-script and absolutely no c++, Does it QtBlend?, clever use of Qt code that only works in Space, Qt Quick talk, other non-Doc helper material etc.? (those are just imagined examples btw, no promises!) The labs blog target "developers of Qt" (well, not quite true, but it's the "Labs" after all) and are limited to only certified Trolls posting. The PHB blog is at the other end of the spectrum where non-hardcore-developers like biz dev, partnering and our ace marketing team blog about Qt. In between the two there is a large void where we currently aren't providing much (examples above). It's not due to lack of content, we just haven't had anywhere to channel it to in an orderly fashion. When that is said, we're likely to re-evaluate our content map once we see how it turns out, except for the labs blog there should be no holy cows in our yard. ;)

That popup is just a helper to write textile (http://warpedvisions.org/projects/textile-cheat-sheet/), I'll check if we can use a jquery UI thing for it instead.

Great, I'll use Jira then! I was looking at a project QtDN, that's why I did not see it. Thanks for the link.

Thanks, we shall have a re-think on it.

I'll give it a spin on the development server :)

We have a new layout of the wiki action bar coming soon, where view/edit is one action etc. Adding the identification of current state (history/edit) to our plans, good point.

Was added today, but needs some more tweaking. Stay tuned.

I will ask it again: what about making a real first page on the wiki? The current first page mostly explains how to work with a Wiki. That is not why you go on a wiki, you go to look for information, and contribute if you feel like it. For me, what is the current first page should be in the links at the top (or buried deep inside the wiki). And I would replace the page by an overview with titles like Qt, QtWebKit, QtCreator, QtMobility, etc, and specific subjects under those categories. Even right now when I would like to contribute, I don't know where to start because the Wiki does not even have the beginning of a structure. For reference, that is how wikipedia uses to look: http://en.wikipedia.org/w/index.php?title=Main_Page&oldid=139992

Oops, wrong thread. Where is the "delete button"? :-D

That form is controlled by the CRM system, it's not a lot I can do with it, sorry.