[Official announcement] Sailfishos.org site renewal!

asked 2015-01-30 10:03:56 +0300

iekku
1261 ●10 ●12 ●22

moderator

updated 2015-03-15 23:12:20 +0300

simo

29079 ●345 ●466 ●481

http://reviewjolla.blogsp...

Ahoy Sailfish OS Community,

It's been almost two years since we first launched SailfishOS.org. Through this time we have provided 10 SDK releases, 10 SW updates to the Jolla smartphone, a development kit for The Other Half, the Hardware Adaptation Development Kit, accepted numerous quality apps into Jolla Harbour, adapted and improved the Sailfish UI, started regular meetings with the community, met many of you at Developer events, and much more. We made all these progress through your generous feedback and support, and now it's time to update the SailfishOS.org website to reflect the progress as well as to prepare for more exciting developments in the future for Sailfish OS developers!

Please take a look at the renewed site at https://sailfishos.org/ and share with us what you think! It's a new chapter, but much more of the Sailfish OS story is yet to come. We'll be working on more of the abovementioned activities, plus enriching the website with useful information and tools to support Sailfish OS developers. Your input will be greatly appreciated, as always.

Currently the SDK includes Tutorial, Design and API Documentation, and these are not available on the website. We did our best with the polish to give the website a bit of shine, however it is still a work in progress. If you find any broken links, please inform us. Also kindly note that your bookmarks for the old site may have change locations or may not exist anymore.

We hope you like the new SailfishOS.org!

On behalf of the SailfishOS.org renewal team,
Iekku Pylkkä
Head of Developer Affairs

edit retag flag offensive close delete

Comments

looks nice :)

William ( 2015-01-30 10:12:38 +0300 )edit

My first impression was: Where is the background image? Tried refreshing the page after 2 sec...

olpe ( 2015-01-30 10:19:57 +0300 )edit

7

Well, I'd advise to get rid of the large intro image. It's taking up so much space that all the useful information is not directly visible. Not even a slogan or other inspiring text.

Jarno ( 2015-01-30 10:32:10 +0300 )edit

1

I am not able to find reference manual.

xmlich02 ( 2015-01-30 10:34:07 +0300 )edit

yeah, the new site is nice text-centric; a little bit too clean maybe.

jarno is right: the intro image is to big. maybe as background image for the block below? i also think the left menu on design and develop (.et_pb_widget_area.et_pb_widget_area_left) for example should be fixed in page.

codeandcreate ( 2015-01-30 10:38:23 +0300 )edit

22

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

wazd
231 ●1 ●2 ●4

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

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.

image description

Thanks.

edit flag offensive delete publish link

Comments

5

Agree completely.

midnightoil ( 2015-02-01 01:00:18 +0300 )edit

3

@wazd I am not agree with you. what does it change on the content, that a website looks like on this or on this. On an healthy basis for a good job, people should be free to show the product on that they work with the vision that they have on it.
Why do you want to force the dev to with some restriction?
Do you really think that is healthy?
Did you see how they ar proud of it on this announcement? We don't really know why it's defeat the website. That your point of view not the one of all. and it changes nothing on content

cemoi71 ( 2015-02-02 11:53:40 +0300 )edit

3

@cemoi71 People are totally free to show off any product they want, but it would be better to do in the right place -> Jolla.com, and that is my point. I wonder why together.jolla.com does not start with fullscreen splash image? It's a jolla-related resource too, let's rock! And yes, it does change everything about the content, it makes the website to be about content, not fancy images. You have a nice overview of everything you will be provided with, from SDKs to community links, latest software version, latest sdk version with bloody download link right from the start (go find in there now). People come to these websites to get answers to their questions, not to behold impressive photoshopery or endlessly scroll through white space. I suggest to give'em these answers. And I'm not sure what "restrictions for devs" are you talking about.

wazd ( 2015-02-04 14:57:39 +0300 )edit

21

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

midnightoil

3612 ●39 ●49 ●54

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

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?

edit flag offensive delete publish link

20

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

simo

29079 ●345 ●466 ●481

http://reviewjolla.blogsp...

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

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

edit flag offensive delete publish link

14

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

tokaru
14054 ●175 ●219 ●220

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

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.

edit flag offensive delete publish link

Comments

Agreed, plus web browsers are DESIGNED to browse cross linked documents, such as API documentation ;)

Edit:

@eric Silica documentation was left out from the initial launch but it will return along with other improvements as we move forward in our iterations, stay tuned ;)

Tuke ( 2015-02-18 12:21:39 +0300 )edit

8

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

shmerl
9435 ●44 ●70 ●69

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

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.

edit flag offensive delete publish link

6

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

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.

edit flag offensive delete publish link

Comments

1

@cemoi71: Silica documentation was left out from the initial launch but it will return along with other improvements as we move forward in our iterations, stay tuned ;)

eric ( 2015-01-30 11:27:45 +0300 )edit

1

Thank you for comments @cemoi71. Like @eric mentioned already, we are working with several improvements.

iekku ( 2015-01-30 11:33:35 +0300 )edit

@cemoi71 the list of links to github sources, are not reference samples, so I don't think they should be linked as referenceon sailfishos.org.

Kontio ( 2015-01-30 13:21:51 +0300 )edit

@eric @iekku thank you very much for your feedback. i know. you've already said that you have a lots of work. That was just a report from me, as you asked for ;-)
Directly at the moment that you announced your new work on it, i wanted to give a look again,on the interface doc to make my own app. And was something really different., but i find the way it goes seems to be good. Wish you good continuation. and sail on!!! :-)

cemoi71 ( 2015-02-02 11:38:17 +0300 )edit

@Kontio i don't know, jolla-team should decide on it
Its just a suggestion from me.
I guess if i ask on it, then a lots of people could ask for it

i got those links from develop team on direct mail channel, because i needed it. they gave me nicely. good team.
Maybe could be judicious to give those link as samples as they do for me.
and spare a lots of work, to answer to the next ones...

cemoi71 ( 2015-02-02 11:42:55 +0300 )edit

4

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

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

edit flag offensive delete publish link

Comments

I agree that it was comfortable, being able to look it up on the web, but all the documentation is right in the SDK.

nodevel ( 2015-03-21 13:49:16 +0300 )edit

4

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

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.

edit flag offensive delete publish link

Comments

Here on Firefox/Android it does scroll to the right place. But it breaks the back button which is definitely a bug. And the URL should change to include the fragment id - you might want to copy that.

All doable in javascript while keeping the transition - though I also agree that's irritating and a waste of time.

'Open in new tab' works OK.

DaveRo ( 2015-09-29 09:28:47 +0300 )edit

[Official announcement] Sailfishos.org site renewal!

Comments

8 Answers

Comments

Comments

Comments

Comments

Comments

Question tools

Stats

Related questions

[Official announcement] Sailfishos.org site renewal!

Comments

8 Answers

Comments

Comments

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions