Sie sind nicht angemeldet.

Lieber Besucher, herzlich willkommen bei: Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.


Montag, 24. Dezember 2018, 16:17

Krpano-only Website

Hi, I would like to present my new website, it's made only with krpano, nothing else. Would be glad about some feedback

It's not completely finished but ready to go live. One thing I am
concerned about is missing SEO opportunities... I have no idea what to

do about there anything one could do to get the site interpreted in some way by google and co?

Mael B.


Beiträge: 122

Wohnort: France, Montpellier

  • Nachricht senden


Mittwoch, 26. Dezember 2018, 12:47

Nicely done *thumbup*
You should perhaps enlarge a bit the text font size and text windows ?
(I recognized some nice places from Mallorca ;-))


Mittwoch, 26. Dezember 2018, 17:50

thanks! About the font-size: it took me a lot of to get the text fit into a text-layer-size that fits in all screen sizes of desktops. And as I work with tables in the text-windows (on column is one page) it's not possible to get maybe four pages on small monitos and three on a large monitor. On a small monitor the layer is taking the whole heigth...thus, I couldn't enlarge the font-size even more. The only way would be to work with css-media queries but I don't know if krpano is recognizing them.... I will try it...

Mael B.


Beiträge: 122

Wohnort: France, Montpellier

  • Nachricht senden


Mittwoch, 26. Dezember 2018, 19:40

you can adapt the font size depending on the screen width with this code ;-)


set(style[your_style_name].css, calc( style[your_style_name].css + ' font-size:' +  (12*stagewidth/1920)  +'px;' ) );   	
assignstyle(layer[your_text_layer], 'your_style_name'); 

of course, change the formula (12*stagewidth/1920) as you want.


Mittwoch, 26. Dezember 2018, 20:04

ah, that's great, I didn't know that way! But I think I have to completely change the way I added css-styles because I did it by plugin.css within a data-tag? Or is it also possible to change values within a data-tag?

Mael B.


Beiträge: 122

Wohnort: France, Montpellier

  • Nachricht senden


Mittwoch, 26. Dezember 2018, 20:26

I think that you can change values within a data-tag... but I'm not sure that it will not be copy in the css-style of the text layer if this text layer is created before the change in the data-tag.
By using the function assignstyle() , you are sure to dynamically change css-style.


Mittwoch, 2. Januar 2019, 02:19

Where is the Progressive Enhancements ?


Basic content should be accessible to all web browsers
Basic functionality should be accessible to all web browsers
Sparse, semantic markup contains all content
Enhanced layout is provided by externally linked CSS
Enhanced behavior is provided by unobtrusive, externally linked JavaScript
End-user web browser preferences are respected
* no accessibility for the Visual impairment

* single page website, sub-sections unbookmarkable

welcome to the dark day of the Internet were FLASH and SHOCKWAVE website were all the rage


Mittwoch, 2. Januar 2019, 15:30



Mittwoch, 2. Januar 2019, 16:50

i agree with tomasparks,

you shouldnt do a website completely in krpano.
to create the menu and all contents (text) would have been possible by standard html/js, too.
you wouldn't even have to change the look of the site, the panos would just be the background with a fallback to normal images
then the content could be crawled by google and other search engines. everything linkable etc.

but as a krpano project itself ... nicely done :)

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »indexofrefraction« (2. Januar 2019, 21:48)


Mittwoch, 2. Januar 2019, 21:01

I also forgot the JavaScript required; Didn’t Read (JS;DR) community


I surf the web with NoScript (a FireFox extension to block java script on a per-domain basis, the sake of security). That also enforces "js; dr". Some pages show absolutely no content unless you allow JS from their domain, and perhaps others. I often don't bother; just back button out of there and go somewhere else.


I am seeing more and more single-page apps that are nothing more than documents, blogs or articles for which relying on JavaScript is not appropriate. Often this breaks down one way or another (back button, stuck "loading" screen, bad formatting).


js;dr = JavaScript required; Didn’t Read.
Pages that are empty without JS: dead to history (archive-org), unreliable for search results (despite any search engine claims of JS support, check it yourself), and thus ignorable. No need to waste time reading or responding.

Also known as, if it’s not curlable, it’s not on the web.

Because in 10 years nothing you built today that depends on JS for the content will be available, visible, or archived anywhere on the web.

All your fancy front-end-JS-required frameworks are dead to history, a mere evolutionary blip in web app development practices. Perhaps they provided interesting ephemeral prototypes, nothing more.


Mittwoch, 2. Januar 2019, 21:51

@ tomasparks
well krpano itself is js, so it does not make much sense to avoid js completely :-D
but unless you like to be hidden from search engines it is not advisable to store all content in encrypted xml :)


Donnerstag, 3. Januar 2019, 01:12

@ tomasparks
well krpano itself is js, so it does not make much sense to avoid js completely :-D
I agree with you there, if there is a section of the website that can only be done with JS (krapno, three.js, etc) make it its own directory and warn visitors (eg: JavaScript / WebGL ahead ) otherwise think of krpano/three.js like plugin that may or may not work