Reply to thread

Message

Hi [USER=83973]@Owlsroost[/USER] ,

I do appreciate your efforts .

However, I don't think that it is a good idea to start a development where directory path information would begin to be scattered throughout the registry and needs to be maintained manually. Also your versions would need to become part of the official builds. Anayway, unless we cannot harmonize everything to correctly use the information as per the mediaportaldirs.xml, my personal view would be to keep things as they are now rather than promoting this possibility.

Actually, the symbolic link possibilities would be as good as the mediaportaldirs.xml, wouldn't they? So why actually bothering about mediaportaldirs when a simple batch script could do the job? Or am I missing something?

<blockquote data-quote="HTPCSourcer" data-source="post: 1149561" data-attributes="member: 74879">Hi [USER=83973]@Owlsroost[/USER] ,I do appreciate your efforts <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />.However, I don't think that it is a good idea to start a development where directory path information would begin to be scattered throughout the registry and needs to be maintained manually. Also your versions would need to become part of the official builds. Anayway, unless we cannot harmonize everything to correctly use the information as per the mediaportaldirs.xml, my personal view would be to keep things as they are now rather than promoting this possibility.Actually, the symbolic link possibilities would be as good as the mediaportaldirs.xml, wouldn't they? So why actually bothering about mediaportaldirs when a simple batch script could do the job? Or am I missing something?</blockquote>

[QUOTE="HTPCSourcer, post: 1149561, member: 74879"] Hi [USER=83973]@Owlsroost[/USER] , I do appreciate your efforts :). However, I don't think that it is a good idea to start a development where directory path information would begin to be scattered throughout the registry and needs to be maintained manually. Also your versions would need to become part of the official builds. Anayway, unless we cannot harmonize everything to correctly use the information as per the mediaportaldirs.xml, my personal view would be to keep things as they are now rather than promoting this possibility. Actually, the symbolic link possibilities would be as good as the mediaportaldirs.xml, wouldn't they? So why actually bothering about mediaportaldirs when a simple batch script could do the job? Or am I missing something? [/QUOTE]