Jamroom 6.1 has been released!
Announcements
Responding to this post (after long absence for fieldwork etc.)
Strumelia:
OK, so today I (finally) updated ....
The only thing that kind of worries me at this point is that my Customized skin, which I originally created from "Ningja"s original jamroom version over two years ago, now has SOOOO many differences from the latest new Ninja skin version that I wouldn't even begin to know what/how to pick things out to apply to my custom skin anymore. But ---am I correct in thinking--- that as long as my custom skin is working and looking as I want it to, I shouldn't really worry about applying Ninja updates to my custom skin? As long as I keep applying core and module updates and the site looks and functions as I like? (and I don't use SiteBuilder, btw) ....Hoping you can reassure me that I'll "be ok" without slogging through the swamp of a thousand code lines that I don't understand anyway in every ninja template.... =:-\
I also worry about managing a custom skin after updates to the original jr skin module.
The existing compare tool is of course useful, but requires manual scrolling through all the templates regardless of whether they need to be updated. And when I compare my custom skin template with the latest jr skin template, I have to somehow determine if differences revealed are dues to changes made by me in the custom template, or a recent change in the skin template, or both. If it is the first, then I probably don't want to revert to the original jr skin version, if it is the second, I need to somehow determine whether the update will interfere with my customization, and if it is the third (both kinds of change), then I will be confused on all counts.
I wonder if it would be possible for JR to provide a more comprehensive skin update tool (or skin management module?), one that automates the process as far as possible.
This hypothetical tool would produce a window with a list of just the affected templates, and the option to update each one individually, manually or automatically, or all of them automatically. And it would distinguish differences that are the result of the new jr skin update, and differences that are the result of a previous customization.
In summary, the aim would be to make updating skins as simple as updating modules.
Perhaps this post should be in different forum, but
@Strumelia has described the issue very well, so I have posted here.
Thanks (and Happy New Year to all the JR team).
updated by @researchcooperative: 01/01/18 08:16:11PM