Domino 9 und frühere Versionen > ND8: Entwicklung

[DOJO] - Performanceprobleme beim EDITIEREN

<< < (2/2)

ata:
... mysteriös - da scheint in dem custom control css etwas zu passieren, daß sich mit dem dojo beißt - wie du schon gesagt hast.

Ist das custom control css ein "normales" css, oder sind Hacks drin für IE?
Sind im CSS auch Funktionsaufrufe eingebunden?
Ist die Benamsung eventuell im Weg?
Besteht das Custom Control mit dem css nur aus diesem oder ist da auch noch was anderes drin - JavaScript
Ist Flash mit im Spiel => MultipleUpload?

???

eknori:
Nein, im CSS ist nicht Besonderes drin, keine IE hacks o.Ä.

Ich habe es jetzt in dieser Form hinbekommen


--- Zitat ---      <xp:styleSheet
         href="/.ibmxspres/dojoroot/dojox/grid/enhanced/resources/tundra/EnhancedGrid.css" />
      <xp:script src="/lib.functions.Grid_SS.jss" clientSide="false" />
      <xp:script src="/lib.functions.Grid_CS.js" clientSide="true" />
      <xp:styleSheet
         contents="   .tundra .dojoxGridCell {border:none;}
                  .tundra .dojoxGridRow {border:1px solid #eee;}
                  .dojoxGridHeader {background-color:#dedede !important;border-top:1px solid #BFBFBF;}
                  .tundra   .dojoxGridHeader .dojoxGridCell {font-weight:bold;border:none;}" />
   </xp:this.resources>
--- Ende Zitat ---

eknori:
Im DesignPartner Forum hatte einer der Entwickler eine einfache wie verblüffende Lösung


--- Zitat ---Could you try adding a forward slash to the url to the stylesheet

So change
<xp:styleSheet href="css_Grid.css"></xp:styleSheet>
to
<xp:styleSheet href="/css_Grid.css"></xp:styleSheet>

Without that forward slash, the Designer design time code should not be able to resolve the url to the file.

Every time you type in an opening or closing tag, or drop a control on the page, it will go and try to get the stylesheet and if that is taking a long time, then that might be why you are seeing this.

That goes for more than just StyleSheets though. We have seen other issues as well where it is incredibly slow to type in source, but it has improved somewhat in recent releases.

Take this example. If you decide to put an xp:panel around the entire contents of a page, the visualization for that needs to draw a panel and then all the controls on the page that are now in the panel, need to be redrawn inside the panel.

The same thing happens when you're in source. Basically, as you add tags in the source tab, it is creating all the Design time visualizations for them in the design tab. If you are at the top of very large file and start typing an opening tag, before the closing tag has been added, Designer thinks everything else on the page is now a child of that opening tag. So it refreshes the entire visualization for the page. Which can cause a noticeable delay.

--- Ende Zitat ---

...

ata:
... kaum zu fassen  ::)

m3:
wow

Navigation

[0] Themen-Index

[*] Vorherige Sete