Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

    Success! Looks like we've fixed this one. According to our records the fix was applied for EXTGWT-1524 in a recent build.
  1. #1
    Ext GWT Premium Member lefke123's Avatar
    Join Date
    Dec 2011
    Location
    Belgium
    Posts
    76
    Vote Rating
    2
    lefke123 is on a distinguished road

      0  

    Default (beta3) Mask doesn't have an appearance-enabled constructor

    (beta3) Mask doesn't have an appearance-enabled constructor


    Like the title says, the Mask class does not have a constructor that takes a MaskAppearance as parameter.
    Code:
    private Mask() {
      this.appearance = GWT.create(MaskDefaultAppearance.class);
    }
    And it always creates a MaskDefaultAppearance instead of using the MaskAppearance interface.
    Also, your MaskDefaultAppearance doesn't seem to have a constructor that has a resources parameter, as most other appearances have:
    Code:
    public MaskDefaultAppearance() {
        this.resources = GWT.create(MaskResources.class);
        this.style = this.resources.css();
        if (!injected) {
          StyleInjector.inject(style.getText(), true);
          injected = true;
        }
      }
    Instead of using:
    Code:
    public MaskDefaultAppearance(MaskResources resources) {
          this.resources = resources;
          this.style = this.resources.css();
          if (!injected) {
            StyleInjector.inject(style.getText(), true);
            injected = true;
          }
        }
    The default Mask appearance isn't included in the Blue theme, but as inner class of Mask.
    Last edited by lefke123; 28 Feb 2012 at 6:29 AM. Reason: Formatting.

  2. #2
    Sencha User WesleyMoy's Avatar
    Join Date
    Oct 2009
    Location
    Redwood City, California
    Posts
    402
    Vote Rating
    2
    WesleyMoy is on a distinguished road

      0  

    Default


    We made the decision to make some appearances, like the one for Mask, to be internal to their implementations when it would seem unlikely that a theme author would care to create their own appearance. As a result, we simply bundled the default appearance in with the component itself. The reasoning continues that, if someone were sufficiently motivated to replace the appearance, they could still do so by using a replace-with rule.

    That having been said, your other points do look like bugs. I've filed a ticket against the team to have them review Mask based on your comments, and I'll update this thread with any reasoning, guidance, or progress on fixes.

  3. #3
    Sencha User
    Join Date
    Feb 2012
    Posts
    17
    Vote Rating
    0
    vokiel is on a distinguished road

      0  

    Default


    Well I just slapped my own MaskAppearance class to add some progress indicator in my views. Works pretty well with mask/unmask, so if that's not a valid use case, I'd like to know which approach is best for this.

    I just like to blank/mask my views while data is being retrieved asynchronously on the server and show to the user something is happening.

  4. #4
    Sencha - GXT Dev Team darrellmeyer's Avatar
    Join Date
    May 2007
    Location
    Washington, DC
    Posts
    2,242
    Vote Rating
    2
    darrellmeyer is on a distinguished road

      0  

    Default


    We have changed the code to this:

    Code:
    this.appearance = GWT.create(MaskAppearance.class);
    You can now create a rule to choose a different impl.

    Code:
      <replace-with class="com.sencha.gxt.core.client.dom.Mask.MaskDefaultAppearance">
        <when-type-is class="com.sencha.gxt.core.client.dom.Mask.MaskAppearance" />
      </replace-with>
    Change is in SVN.

  5. #5
    Sencha User WesleyMoy's Avatar
    Join Date
    Oct 2009
    Location
    Redwood City, California
    Posts
    402
    Vote Rating
    2
    WesleyMoy is on a distinguished road

      0  

    Default


    This shortcoming has been fixed in the Ext GWT 3.0 Release Candidate. Please upgrade your copy of Ext GWT and try your scenario again. While we're confident that we've addressed this issue, please reply if you notice any continued problems after upgrading. Again, thanks for taking the time to report this bug.