More > Media Center 17
Theater View television series
BartMan01:
--- Quote from: rick.ca on November 07, 2011, 04:34:09 pm ---I wonder what you mean by "building tools." it's difficult to imagine anything that would handle the capabilities of the Expression Language.
I find it helpful (and usually essential) to use Expression Columns in Standard View to build and test captions. I use separate columns to test bits of code (e.g., getting the syntax of an unfamiliar function correct) and copy those to another containing the entire expression (e.g., where there might be complex if-then logic).
--- End quote ---
I would like to see a beefed up expression builder similar to the set rules for file display builder. Even just having the expressions builder there would be better than the existing plain text, figure it out elsewhere box that exists currently.
rick.ca:
--- Quote ---I would like to see a beefed up expression builder similar to the set rules for file display builder.
--- End quote ---
That was the first thing I couldn't imagine working. ;)
I suppose something similar to the function helpers in Excel (where, having selected a function, you're shown the parameters required) would help a little—although the tooltips work fairly well.
--- Quote ---Even just having the expressions builder there would be better than the existing plain text, figure it out elsewhere box that exists currently.
--- End quote ---
But that's what drove me to use Expressions Columns—where I can use the full expression editor and see the results. I'd still do that for all but the simplest changes, even if there were an expression editor in the Options dialog. In any case, I agree. It's a place where expressions are entered, so the editor should be there.
BartMan01:
--- Quote from: rick.ca on November 08, 2011, 02:54:48 am ---That was the first thing I couldn't imagine working. ;)
I suppose something similar to the function helpers in Excel (where, having selected a function, you're shown the parameters required) would help a little—although the tooltips work fairly well.
But that's what drove me to use Expressions Columns—where I can use the full expression editor and see the results. I'd still do that for all but the simplest changes, even if there were an expression editor in the Options dialog. In any case, I agree. It's a place where expressions are entered, so the editor should be there.
--- End quote ---
At a minimum what I would like to see here would be:
The current expression editor functionality, expanded to either work with tool tips or that drops in parameters along with the function. For example right now if you choose 'If(...)' it just drops in 'If()'. It would be 'nicer' (for me anyway) if it dropped in 'If(Test Expression,True,False)' instead. Tool tips would be better but may be harder to do.
The problem I have here is that is such an overloaded expression trying to get it to display different things for different types of content. What I would REALLY like to see would be separate entries for the default caption as well as entries for each media type and sub type. The entry at the lowest level would win.
rick.ca:
--- Quote ---The problem I have here is that is such an overloaded expression trying to get it to display different things for different types of content. What I would REALLY like to see would be separate entries for the default caption as well as entries for each media type and sub type. The entry at the lowest level would win.
--- End quote ---
I agree there should be a caption for each [Media Type], and maybe a special one for [Media Sub Type]=[TV Show]. If it goes beyond that, it starts to get complicated for other reasons. That's sufficient for general rules. Then special situations should be dealt with by overriding those rules at the view level. The setting at the view level might even show the applicable default rule based on the view's Rules for file display, and then allow that expression to be edited if the override is engaged. In other words, in the view configuration, you would check a "Override default caption" box and an expression editor would appear—loaded with the applicable default caption.
BartMan01:
I like the idea of an override at the view level, but TV Shows are not the only 'special case'. In videos alone I have podcasts, movies, TV shows, and music videos - all of which (for me) would need completely different file captions. If I come in from a top level view that has a 'sub type' break out, I would still want the different types to have different captions. The current overload with 'if/then' gets very confusing very fast.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version