I have pruned my space back and have gotten the loading times down to a 
reasonable time. This particular slowness seems related to the attempt to 
render views that fail. After that TBC slows down to a crawl.

I  think that the best advice you are giving here is to attach a 
ui:instanceView directly to a class and I will try that rather than relying 
on ui:id or ui:priority. These latter approaches seem great if we have 
generalized views that we want to apply to broad swaths of classes but then 
where they have been defined gets confusing. As I mentioned before, it 
would be helpful to see a list, from the current resource back up to 
rdfs:Resource, of what will be selected for display (and then where they 
are defined). But I appear to be the only one who would find that helpful.

I have that javascript defined in the ui:headIncludes instead of a 
javascript file because it is a single function. You didn't answer my 
question about whether I could inject an SWP url into this code, but I have 
since answered the question for myself and the answer is yes if you have 
the syntax correct (e.g., if you use ascii codes for '&', etc.).

There are two other enhancements I would like to suggest for the GUI 
developers (maybe all of these are on the todo list already):

1. When working with the ui:prototypes for SWP they are often too large to 
see w/o scrolling, but the horizontal scrollbar is at the bottom of the 
window and sometimes you need to horizontally scroll higher up in the 
definition. I end up using the cursor to scroll and it is painful. Is there 
any way to force the scrollbar to appear in the view rather than at the 
bottom of the view?

2. I find that there are times when I want to undo something while editing 
in an SWP (for example the system is thinking and I mistype something). in 
some cases I can hit the escape key and get out but there is no 'undo' 
operation in the SWP editor and that would be very helpful.

3. It would be nice to have an undo history. The current undo seems to be a 
toggle (most current action). Most editors these days keep some history of 
actions that can be undone and that would be most helpful.

On Friday, July 18, 2014 4:58:48 PM UTC-7, Jack Hodges wrote:
>
> The following <ui:group> defines a javascript function that is called when 
> an item in the tree is selected for viewing. In this body all that is 
> stipulated is the url for the resource. In most of my views I can select 
> what kind of view is used with a match-id or a priority. Is the 
> ui:instanceView selected based on whether it (the resource type) is a class 
> or an instance? Certainly not in this function:
>
> <ui:group>
>     <script>var serverURL = ''; // 'http://localhost:8083/tbl/';&#13;
> &#13;
>  function openInNewTab(resource){&#13;
> var url=document.URL;&#13;
> var q= url.indexOf('?');&#13;
> var sendTo= url.substring(0,q)+"?_resource="+resource;;&#13;
> //alert('openInNewTab ' + sendTo);&#13;
> window.open(sendTo);&#13;
> }</script>
> </ui:group>
>
> I want to be able to determine which view will be used when and item in 
> the tree is selected. Can I construct the URL to use any SWP or will it be 
> overridden?
>
> I would just try it except that everything is taking so damned long I 
> might as well submit the question and wait for some kind of response here 
> :-(
>
> Thanks,
>
> Jack
>
>
>

-- 
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary 
Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, 
SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to