-
-
Similar Topics
-
By pivotCE
The webOS community may be a bit smaller these days but it’s no less devoted to the platform. WebOS Ports is a small team of developers. As you can imagine, it is a few people to maintain a full OS that consists of thousands of components. Things are starting to come together for LuneOS, with the current major rebase and stable release. But we still need your help.
As nice as it is to have some additional folk contributing, developing, and working on issues, we still need more developers to get involved to make this community project really take off.
“Our focus is core functionality”
We cannot stress enough that we are building an OS focused on core app integration that is simple, beautiful, and user-centric. Right now, function comes first. If we had a penny for every developer that knew some web code and could make a beautiful static mock-up of an app that didn’t do a thing in the backend and then said “I did my part, it’s up to you to make it work”…well, we’d have a lot of pennies.
Developer requirements
Once core app integration happens we will need HTML/CSS smart people. But to be an asset to the team, you need to have a good grasp on any or all of these technologies:
Javascript C node.js C++ QML Qt Yocto Graphics design Are you decent at some of these, but might need help from time to time? That’s fine! We’re a community, remember? Hit up the
link hidden, please login to view and/or channel and ask! Get the bugs out!
We have several applications already available but many are placeholders or have basic functionality. Some of the apps are almost fully functional like Settings. But even Settings has bugs and can use refinement. OK there are bugs everywhere! (If only it were as easy as a can of Raid to fix them)! We’ve received lots of questions about how to get plugged into the project quickly. Easy! Head over to our to see current issues. Find an area where you think you can help and then find us on or (see below) to talk about it.
Some examples of areas that need bug fixing are:
Email: Some minor bug fixes Settings: Add Settings when needed Phone: Further polishing Calendar: Google C+Dav integration needs updating to adopt for Google’s changes Browser: Rework UI to be more webOS/LuneOS like And more. Core Apps/Features/Backend magic
The Open webOS project released several core applications that were Enyo1 based. These apps are in LuneOS
Messaging: Needs a rework or rewrite to give proper functionality similar to legacy webOS PDF needs converting to QML. LuneOS also needs a media player app (maybe reuse/rework the webOS OSE app for this?). The C+Dav connector is there, but it needs updating for various changes by Google. It also needs testing for other providers. Additional IM connectors would be good to implement (Telegram, Signal) etc, there are existing plugins exist for Pidgin/libpurple that can be used. Looks aren’t everything
As you can see, to really make stuff work first, most of what we need is in the backend. It’s the old battle between form and function. Which comes first? Designers will argue form! But Ports is focused on the core functionality that has to work first and look pretty later. It’s a hard pill to swallow and we get that, but when building an OS, it’s the most important thing. If it looks pretty but doesn’t work, the project loses potential users. If it works but doesn’t look pretty it will at least show promise and that encourages positive feedback. And with a community led project, if you don’t have good feedback you’ve already lost.
Additional help wanted
Ports is looking to expand our public relations presence. If you are located outside of the United States or more specifically speak a different language than English and would like to help us advertise and direct interested people toward LuneOS and WebOS Ports, please let us know.
We are also looking for a WordPress “expert” for a new site we’ll be setting up soon. Are you good at making tutorials?
We have several “How to install LuneOS guides” on the wiki. If you’d like to make friendly guides, that’d be great!
And finally, we need a “wiki-meister”. Someone that really knows the ins and outs of running a mediawiki!
Get involved
Everyone can help in some way. We need testers and bug reports! Sign up on the , contact us to let us know that you signed up and what your username is, and we’ll upgrade your account so you can post issues.
Developers please join us on and/or drop by the IRC channel
How to Contact WebOS Ports
Want to get involved? Have a question? Get in touch with us.
[email protected]
Twitter:
IRC (Libera):
Telegram:
Issue Tracker:
User Support Forums
Join the forum .
The post first appeared on . Related posts:
-
By Alley Cat
There doesn't seem to be any replies whatsoever from anyone connected to LG, so just wondering.
-
By Yan Wong
Hi, I got a LG 55UH6500 and Magic Remote AN-MR600 and they are working perfectly for years. After I upgraded to the latest firmware 05.50.95, the TV refused to pair the Magic Remote and said only specific model and be paired. Can I go back to the firmware version 05.30.xx to solve the problem? I cant find the firmware from official LG website.
-
By Santhosh Akula
I wanted to connect my Lennovo Thinkpad to my LG web Is tv, can someone guide me to connect, the HDMI port my laptop seems to be different pls check attached images first one is my laptop port and second one is TV HDMI cable
-
-
By pivotCE
This article is unusual for pivotCE. Most of our articles are aimed at the general reader, but this one is specifically aimed at those with knowledge of javascript frameworks – specifically frameworks designed for app development. We hope this article will reach such people in our community and beyond in the hope that the
link hidden, please login to view project can benefit from a range of experience and insight and even perhaps recruit some new contributors. Long time webOS fans will be aware that one of it’s features was the ease with which apps could be created using methods more associated with web design. Most (non-game) apps were in fact mixtures of HTML & javascript. This and the ‘synergy’ of connecting data from various remote services into common user interfaces is what gave the system the name of webOS.
In the early days, webOS was at the cutting edge of using web technologies, but performance was not as responsive compared to more traditionally coded apps. Since the days of legacy webOS, many improvements have been made in app development frameworks and their implementation to bring speed up towards that of ‘native’ apps or at least fast enough for the user to see little difference. Increasing speed, power and multi-core processors have also helped, though performance is beginning to plateau as the physical limits of current hardware is reached.
The first (proprietary) development framework for webOS was called ‘Mojo’. After the purchase by HP, the (Open-source) ‘Enyo’ framework was introduced to target more varied screen sizes. Version 1 ran on the webOS 3.0 HP TouchPad and was back-ported to phones. Version 2 became a cross-platform framework also.
Of course, we all know about the end of hardware at HP and the eventual sell off of all parts of webOS. Officially, the is still maintained by LG & HP and have continued to develop the framework. The part used to make the UI for mobile apps is called ‘Onyx’. To make apps suitable for Television screens, LG developed a new UI library called, ‘Moonstone’. Enyo itself has developed through version 2.5 to now stand at version 2.7 and LGSVL now looks to the (). But this brings with it potential problems for LuneOS.
To begin with, the various iterations of Enyo are not entirely backwards compatible. This is not a big problem as each version can be installed and recent versions are even able to package up modular parts of the framework with the app itself. But to take advantage of the latest improvements, each app needs some rewriting. At this time, apps written specifically for LuneOS are almost all system apps and have been written in whichever version of Enyo was current at the time.
Secondly, the Enyo team are assessing developments in web app development and technology and considering where to next take the framework. This project is currently called, ‘Enyo-next gen’ and will be based in part on the framework. This means that compatibility will again be broken – likely to a greater extent than previously. For this reason, updates of existing LuneOS apps have been put on hold until the Enyo situation becomes clearer. As the Onyx UI library is built on Enyo 2.x, it will not work on React.js unless it is re-engineered. The team’s priorities are obviously lead by LG’s webOS product line: Televisions (briefly ) and now . It seems that the next generation Enyo will , but Onyx will not be part of the package. It remains to be seen what the replacement will be like.
To avoid remaining in a backwater, LuneOS will need apps. The time is approaching when developer attention must turn from the core OS to the app ecosystem. Millions of apps aren’t needed, but a decent range of modern apps will be. LuneOS has a modern browser based on Chrome. All modern JS frameworks support it and therefore many web apps can be run on LuneOS: old Legacy favourites, apps from similar systems and standalone web apps. Of course, the latter examples won’t necessarily resemble or act like webOS apps and LuneOS will still need a framework for original apps; One that will ‘feel’ and hopefully look like webOS. In short, the LuneOS project needs to make a choice of javascript framework for the future and standardise upon it.
What are the options?
webOS Ports could stick with Enyo 2.7. It will be supported for a while. The problem is that this version will not be updated as technology moves forward and the Ports team lack the resources to maintain the framework in addition to the OS. If Enyo-next gen works well (It is certainly expected to be a contender), but lacks the UI elements suitable for LuneOS, the team could attempt to maintain a version of the Onyx or Mochi UI libraries for dedicated use, but again human resource issues mean this option will probably be overlooked in favour of a more ‘off the shelf’ solution. Enyo-next gen could provide an ideal solution, offering the option of creating webOS-style mobile apps. Another suitable framework may need to be found – one that can offer modern performance and which will be supported for the foreseeable future. A popular framework could also deliver a range of apps from sources beyond the small webOS community. The webOS Ports team are soliciting demo web apps that show the “feel” of webOS can be duplicated by candidate frameworks. What is needed from a javascript framework suitable for LuneOS? LuneOS developer, Doug Reeder of suggests some requirements:
A fuller list can be found at .
Most of our articles link back to the forum at webOS Nation, but in this special case, we are going to link to the archive of the webOS Ports mailing list and invite those interested to join the list and the IRC channel.
Here are archives of the discussion so far:
, , .
, , .
If you are familiar with JS frameworks, you are invited to share your experiences of development and performance and suggest candidates for testing. Please for information on the IRC channel and how to join the webOS Ports mailing list. Please share this article with anyone who may have useful insights.
Image credit: .
Related posts:
-
-
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.