Support user-defined notes in preset files

dnave

New Member
Having the ability to create and edit user-defined notes in a presets file would be very useful for annotating preconditions, observed settings problems, Windows versions, etc.

The user interface need not be complex. For example, it would be sufficient to split the "Presets" pane, and add a text input control below the list of presets that updates depending upon which presets file is selected.

It would be handy if the notes in the presets XML file were editable outside of NTlite, but the feature would still be useful otherwise.
 
Hi,

I like that very much, added to the priority todo list as it should not delay other tasks for more than a day.
Let me know if you want the pre-release version when the example is ready these days.

Thanks.
 
Maybe this would be redundant, and less easy to implement, but I'd love to have similar ability in the Compatibility section..or maybe even an option to create Compatibilty presets? (of course, i can just have the related Presets notes and use them to copy and paste within that section of the Preset xml)
 
Maybe this would be redundant, and less easy to implement, but I'd love to have similar ability in the Compatibility section..or maybe even an option to create Compatibilty presets?
You can add hardware support list, open NTLite in another machine, load the Live Windows image,go to Drivers page and click export, copy and drop the list to where you have NTLite activated in NTLite\HWLists folder. Personalized compatibility list could be the same.

pmikep asked Is there a way to import this as a Compatibility check box? over 6 month ago, it has never proposed, what you think about it nuhi?
 
You can add hardware support list, open NTLite in another machine, load the Live Windows image,go to Drivers page and click export, copy and drop the list to where you have NTLite activated in NTLite\HWLists folder. Personalized compatibility list could be the same.

pmikep asked Is there a way to import this as a Compatibility check box? over 6 month ago, it has never proposed, what you think about it nuhi?
Indeed, how about an option to add Compatibilities in Settings.xml for now, to add an element like:

Code:
<Compatibility name="mycompat1" displayName="Private Protection">
     <Component>snippingtool</Component>
     <Component>mediaplayer</Component>
</Compatibility

Start the tool, and then that compatibility "Private Protection" would be listed like the rest.

Btw haven't yet gotten to the Presets notes, haven't forgot about it.

ButWait, adding comments to Compatibilities, can you elaborate a bit more why would it be needed?
 
New name same function. Handy at times. :D
Maybe you're missing something or that was a hidden feature in nLite that i never knew.

Here we will make a components list, not a files list, then our private components list will show up a check box in compatibility.
 
I get ya. What would be handy is a specified fonts list, i only need a certain amount, i have to check my font list text file when i write a new preset.

Hmm, have a User Fonts entry with an expanding/collapsing sub menu listing the fonts. Font tuning is a real pain in the rear as fishingfish found out. If the tool reads the contents from a .txt file it will be easier for users to add protected fonts and components and easier to add to than an xml file.
 
Last edited:
If the tool reads the contents from a .txt file it will be easier for users to add protected fonts and components and easier to add to than an xml file.

The font names are not as listed in NTLite, that would be not easy enough, i think xml is the way to go.
 
I think i mean this: For me, I want to have an interactive way of trying to learn the tool and want to see my usage reflected back at me in my own language. So it'd be great to have an in-progrm self-help notetakiing space. Such a space could be adjacent to Presets list, and it could be persistant across sections or a separately implemented space adjacent also to Compatibility. Those are just two key areas I'd imagine using it. It would supplement the helpful info's you've already got in there (throughout the GUI) about how things relate to one another. Sometimes I'd probably add a note that restates what's already communicated but in my own words. Sometimes I'd go on-line and ask a question or read posts, and be able to copy and paste that stuff adjacent to pertinent areas of the program (or at least have it always visible, like a playlist). It might say 'remember, if you remove X, you don't want to also disable it (see Kasual's post xxxx responding to user having removed x and then finding the files for it got installed anyway).' * Any user could use notes as personal training wheels, or as a space for commenting and bookmarking a troubleshooting process, etc. If a program update renders obsolete a habitual way of using the program, I might want to give myself a reminder.."doing such n such is no longer neccesary/deprecated'.

* Not sure if i've correctly paraphrased that first particular scenario, but clearly i'd have to either be more succint in my notes or the implementation of the notes space would need to be something like one line per comment but with a drop-down or infotip popup for a note that takes up more space. But the easiest might be to just have 2 inches wide and the verticle space of the program screen, and make it contiguous (ie, instead of in-line with a given compatibility item), in other words like 'space' of an open file in npp/notepad; or it could exist similarly to a playlist that can attach or detach from the main program window of a media player..
 
Hi,

I like that very much, added to the priority todo list as it should not delay other tasks for more than a day.
Let me know if you want the pre-release version when the example is ready these days.

Thanks.

Hi nuhi,

Any news on the pre-release "Notes" feature?

Thanks!
 
Code:
<Compatibility name="mycompat1" displayName="Private Protection">
     <Component>snippingtool</Component>
     <Component>mediaplayer</Component>
</Compatibility
Thats really nice.
Maybe some users would find some compatibility issues and write it in a own thread.

What you think about right click on component and with a context menu add this component to own compatibility?
I mean, with a gui it would be more user friendly
 
Back
Top