+ 5

A blog about Maximize's "Phone system"

This will be sort of a blog about my app contributions to the Maximize's "Phone system" store. I know posts in SoloLearn are technically under Q&A section... :/ I think Maximize's code is a great idea and I intend to contribute some apps to it :) "Phone system" store doesn't support comments nor app updates (!!!), so I can't fix bugs, advise how to avoid them or advertise my new apps inside the code itself. So I'll do the following two here instead :) https://code.sololearn.com/WtFjmk9mddZj/?ref=app

blog maximize phone-system

11th Feb 2018, 9:41 PM

Augustinas Lukauskas

5 odpowiedzi

+ 16

hey :) thanks for your contribution in my web app 😄✌ If you want to update your apps , I can do it ... so send me a code and I set it on your app 😁

12th Feb 2018, 12:35 PM

Maxımee

+ 3

I recommend instead posting about it via the discussion area on Sololearn, put this in a code. Not only can you freely put what you want (within reason, though) but it’ll help you with practicing code. https://www.sololearn.com/Content-Creation-Guidelines/

11th Feb 2018, 10:06 PM

luciel

+ 3

@luciel Thank you for your advise. I read the guidelines and I believe my post meets them. I am open to hear why you think it doesn't. I decided to make a post instead of a code because it's easier and Q&A section is used for non Q&A posts so frequently (example: challenges) that I believe the title lost its meaning. SoloLearn users and devs accept Q&A section being used for reasons other than actual questions and answers. "Thanks to sololearn for helping me" type of posts make it to the featured post of the day, challenges even have their own featuring term: "challenge of the day". "I reached platinum", "what's the best OS?" type of posts often make it near the top of most trending ones and get a lot of possitive comments. They all are in the Q&A section.

11th Feb 2018, 10:50 PM

Augustinas Lukauskas

+ 2

I uploaded my first app "Mdlbr" earlier today. It is my code "Mandelbrot set explorer" adapted to run inside "Phone system". The adaption process sounds easier when done, because there were a ton of nuances which prevented my code to work properly. One example: apps act as if there's no <!doctype html> defined (I had to figure it out) meaning styling works a bit differently, in particular canvas { width: 100%; height: 100% } doesn't produce a square canvas and has to be replaced with canvas { width: calc(100vw - *padding*); height: calc(100vw - *padding*) } Also, I noticed that an app's preview inside codE editor and the same app after it's been uploaded to the store have yet different stylings! If you'll upload any apps make sure to explicitly define as much CSS as possible (keeping in mind that <!doctype html> seems not to be defined) in order to know how your app will look once uploaded. As for my app, the interface is a bit messed up and there's currently no way to fix it, because the store doesn't support app updates :(

11th Feb 2018, 10:03 PM

Augustinas Lukauskas

+ 2

I just uploaded 2 new apps - Bing and SoundCloud (SndCld). They use full screen iframes :) I will share a template I use to avoid the weird styling once the app has been uploaded to the store <div id="wrapper"> * your HTML * </div> <style> #wrapper { font-family: Arial, Helvetica, sans-serif; font-style: normal; font-weight: normal; font-size: 1em; text-shadow: none; text-decoration: none; color: black; } </style>

12th Feb 2018, 1:39 AM

Augustinas Lukauskas