[Official announcement] Sailfishos.org site renewal!

answered 2015-01-31 16:08:47 +0200

wazd
231 ●1 ●2 ●4

updated 2015-01-31 16:09:56 +0200

Sailfishos.org is supposed to be more of an info vault for developers, not some promo landing page for "average consumer" with pretty renderings. I understand, the fullscreen image of a fish in Jolla is cool and stuff, but it defeats the purpose of the website completely. Here's more compact and informative version of the same thing.

Thanks.

answered 2015-02-01 00:58:57 +0200

midnightoil
3612 ●39 ●49 ●54

updated 2015-07-15 21:17:07 +0200

The site claims that Android apps work on Sailfish. However, as the situation currently stands, this is patently false. They work on Alien Dalvik, which is NOT baked into Sailfish. It is available on the Jolla phone, but not Sailfish as a whole.

Either this claim needs to be removed, or Jolla should clarify plans for a license revision which would allow them to provide Alien Dalvik to Sailfish generally (or via a paid app store whenever that finally happens). It would be great if the latter is true or happens, as it'd be a huge filip for the ecosystem generally, and would no doubt spur hardware adaption efforts ... but this needs to be addressed, because as of now it is untrue. The claim would be perfectly valid for the Jolla phone / tablet product pages, but this is the Sailfish.org site.

Edit: 6 months later the site is unchanged ... what was the point of asking for feedback if it was going to be completely ignored?

answered 2015-02-04 00:02:30 +0200

simo
29079 ●345 ●466 ●481

http://reviewjolla.blogsp...

updated 2015-03-15 23:11:17 +0200

There are really nice improvements, but I'm missing this statement from the earlier page content (quoted from https://sailfishos.org/about-license.html):

"Our goal with the Sailfish OS is to develop an open source operating system in co-operation with the community, thus ensuring the development of a best-of-breed operating system."

This removed content, archived last on Jan 1, 2015, can be achieved at: https://web.archive.org/web/20150101044101/https://sailfishos.org/about-license.html

The above has actually been my main driver in contributing to the community via spreading the word out with severe posts at my blog and active contributing here at TJC.

I wish I'll be able to read a similar statement soon, either on sailfishos.org or jolla.com, or even better, on both. Please? This is personally important to me to keep up contributing, and feeling unlike doing so

EDIT: This has just become more important. To get an idea why, please translate this (from Russia) and compare

• http://sailfishos.org
• https://source.tizen.org/

answered 2015-02-18 11:55:49 +0200

tokaru
14054 ●175 ●219 ●220

updated 2015-05-03 17:29:32 +0200

EDIT 2015-05-03: it seems the Silica reference is back online: https://sailfishos.org/develop/docs/silica/ @Jolla: with regards to user experience and search engine optimization I suggest to 301-redirect the old URLs, though.

Currently the SDK includes Tutorial, Design and API Documentation, and these are not available on the website.

Is it planned to bring them back online? I suggest so very much, for several reasons:

• It is not possible to share links to IDE-internal documentation in forums, mailing lists, etc.
• A lot of existing links to these pages are now broken, which is bad for user experience and for search engine reputation.
• People are not necessarily sitting in front of a running IDE when they want to look up something.

Personally, as a Qt newbie, I have spent quite some time on these pages even before installing the IDE. I think we should make it as comfortable as possible for (potential) developers to find information.

answered 2015-02-01 02:33:54 +0200

shmerl
9435 ●44 ●70 ●69

updated 2015-02-01 02:34:32 +0200

Great improvement, but like others already pointed out some links to open projects which are an important part of Sailfish are missing (like Sailfish browser on Github and so on).

Also, some page which breaks down open vs closed components should be present on the site to make it clear for all the participants and users.

answered 2015-01-30 11:13:52 +0200

cemoi71
14264 ●310 ●434 ●439

@iekku wow that is an huge changes! lots of works. Not bad.

otherwise, i think references to samples are missed:
https://github.com/sailfishapps/
https://github.com/d0b3rm4n/harbour-sidudict
https://github.com/d0b3rm4n/harbour-simpletorch
https://github.com/Armadill0/harbour-tasklist
https://github.com/karip/harbour-file-browser
https://github.com/beidl/harbour-owncloud
https://github.com/jrutila/harbour-newsblur
https://github.com/pycage/tidings

In QtCreator we could access 2 examples with code: click on the left side on the Qt icon (with text Welcome, the one on top), and then click on Examples in the next view. One is the Component app , the other is a Media Gallery app.

I don't find the sillica documentation any more for the gui elements.

On which part of the website could we informs us how to develop with the device interface? With all the sensors, the communication interfaces (wifi bluetooth, usb)

Thanks in advance for your answer.

answered 2015-03-21 13:43:35 +0200

kunev
61 ●1 ●4 ●6

A possible workaround for the documentation insanity(Jolla are awesome as hell, but srsly guys, two months now, just to get a shinier page out there earlier, it's kind of sad):

http://web.archive.org/web/20140703152009/https://sailfishos.org/develop-overview-article.html

answered 2015-09-29 03:39:42 +0200

Tanghus
10524 ●85 ●118 ●125

https://github.com/tanghu...

One thing that annoys the heck out of me, is the non-standard use of anchors.

For example if you're on https://sailfishos.org/develop/docs/nemo-qml-plugin-notifications/qml-org-nemomobile-notifications-notification.html/ and click on e.g. Properties the link shows a correct HTML anchor - https://sailfishos.org/develop/docs/nemo-qml-plugin-notifications/qml-org-nemomobile-notifications-notification.html/#properties - but when you click on it, it is intercepted by some javascript to make some smooth scroll (which btw scrolls too far) down to the place on the page, but it doesn't change the URL!

The result is that if I want to go back to where I was on the page by either clicking the back button or Alt-Left I am taken to the previous page instead...

Why not just drop that annoying piece of javascript and use the anchors as they're supposed to? It's faster, less distracting and The Right Way™ to do it.