Results 1 to 8 of 8
  1.    #1  
    This is a thread to discuss documentation of Legacy webOS.

    I guess the categories are:
    • User information (how to operate the system and hardware)
    • Tweaking (how users can enhance or fix webOS)
    • App development
    • System development / Hacking


    Sources:
    • Official sources (generally Palm & HP sites)
    • 3rd party websites
    • Forums
    • Archives (including off-line)


    As various sources date, break or get removed, the aim is to ensure the documentation is preserved. Options:
    • Preserve or encourage the maintenance of the original site.
    • Recover 'lost' material
    • Rehost material
    • Update existing material
    • Generate new material


    This thread will identify and list documentation by category or specific source and discuss the best preservation approach to take.
    Suggestions:
    • Preserve things as they are.
    • Link to archives
    • Consolidate data on a few sites
  2.    #2  
    So a suggestion might be:
    • News - pivotCE
    • User information - The pivotCE Guide
    • Tweaking (how users can enhance or fix webOS) - ???
    • App development - Site dedicated to Enyo / Mojo and other app coding methods
    • System development / Hacking - webOS Internals
    • Main forum - webOS Nation

    Possibly tweaking should also be on the webOS Internals wiki. There is of course a danger in splitting things up too much as there is overlap in all areas. Articles on pivotCE can highlight interesting developments in all areas.
  3. #3  
    I like the idea of this a lot. especially considering im just coming back so as to help avoid the week long pain of rooting around for others. My only advice would be something thats more inclusive. Going around searching 20 different sources makes things more difficult. For resources such as files Im already looking into hosting as I own my own domain.

    The real problem is maintenance. Things like wiki's get dated fast and need updating regularly. We all have lives and get busy so im not sure how that can be accomplished unless someone can live solely by donation's to just maintain things.

    Overall having one giant source encompassing as much as possible would make things easier.
  4.    #4  
    Just to reply to this:

    Quote Originally Posted by ami mizuno View Post
    The real problem is maintenance. Things like wiki's get dated fast and need updating regularly. We all have lives and get busy so im not sure how that can be accomplished unless someone can live solely by donation's to just maintain things.

    Overall having one giant source encompassing as much as possible would make things easier.
    At this point, legacy webOS is in 'maintenance mode', which is the polite way of saying that there are occasional fixes that keep the zombie OS staggering on. Changes since 2011 have been few (but sometimes significant), so most of the information that was correct then, remains so. If old information is checked to still be correct and the fixes since 2011 are documented, then the effort is not huge.

    In terms of resources, 'the community' does not run this forum. We have access to webOS Internal's wiki. Likewise, pivotCE welcomes community contributions. These sites ARE for practical purposes, community resources and as far as the future can be predicted, will be around for a while. Additionally, many community members maintain their own archives or websites. If we had the resources and control, one big site might be the answer. But that's when we might need money, time and effort to build and administer it - a big ask. I agree that the number of sites should be limited to prevent confusion, but a small number of sites - each dedicated to a particular aspect of webOS, would be easier to maintain and manage (as most already exist). We already have this forum for comment, Internals for system hacking and pivotCE for news. Still required is a user guide and app development tutorials. An advantage to having 4 or 5 separate sites is that if anything happens to one, material could be re-hosted at one of the others (if it's archived!).
    Last edited by Preemptive; 01/02/2018 at 08:47 PM.
  5.    #5  
    I saw this posted somewhere: https://docusaurus.io/
    Are there any comments on this? Would it have value for a new documentation site (probably on app development)? Is there any advantage over a wiki?
  6.    #6  
    I'm just going to post some sources I found. I don't know if they are 'lost' as they just came from a web search, but I'll post for reference.
    https://plugins.jetbrains.com/plugin/5867-webos-storm (Dev plugin)
    https://www.npmjs.com/search?q=webOS (webOS projects on NPM)
    https://books.google.co.uk/books?id=-B78Yw27i1oC (Frank Zametti's book)
  7. #7  
    The npmjs repository is for the tv version of webos, I think
  8.    #8  
    Looks like it, but some is old enough to maybe be of use for legacy also.

Similar Threads

  1. Syncthing for webOS
    By xon.xoff in forum webOS Apps & Games
    Replies: 24
    Last Post: 01/01/2018, 04:16 AM
  2. WebOS Internals Meta-Doctor - 2017
    By bbito in forum WebOS Internals
    Replies: 33
    Last Post: 11/10/2017, 05:19 PM
  3. Replies: 1
    Last Post: 09/08/2017, 07:54 PM
  4. Slower, uglier version of WebOS on lower-end TVs?
    By Infotainment in forum LG webOS TV
    Replies: 2
    Last Post: 09/07/2017, 05:11 PM
  5. Lg eg9100 webos
    By Rayancaleb in forum LG webOS TV
    Replies: 0
    Last Post: 09/04/2017, 08:14 AM

Tags for this Thread

Posting Permissions