Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 10 of 113

Hybrid View

  1. #1
    Member
    Join Date
    Oct 2012
    Location
    sdsddsds
    Age
    75
    Posts
    25
    Rep Power
    13

    Default

    Quote Originally Posted by Texas View Post
    I am thinking about doing that with the help of other members of course. Create some sort of guide what each ux plug-in do with screen shot from program if possible.

    Sent from my SM-N9005 using Tapatalk
    That would be very useful.

    Quote Originally Posted by osiris4isis View Post
    The problem with NextGen releases is that no one know where any of the components (ux, data.zip, .apk, etc...) come from. People take bits and pieces of them to get it working, then posted it for others to use and when there are issues, no one knows why. iGO/Primo uses one .zip file per skin which is nice to manipulate and debug. NextGen uses ux which is a pain in the butt to debug, too many conflicts in their interactions and their testing is always per release (one to one) and never against each another (one to many). We need to tagged and databased each ux, data.zip, etc... based on some sort of signature (crc-32) so we know who has what.
    Primo also uses ux. In my installation I have 5-6 of these. But I guess skins were more complete for primo so people didn't need to use many uxs.
    It would be nice to have a list to know what each ux is supposed to do. Whether they actually work on not on a particular installation is another matter that is, as you mention, quite complex. But at least if we knew what they're supposed to do we could test them ourselves.
    Last edited by naab; 23rd January 2016 at 01:48 PM.

  2.    Advertissements


 

 

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •