search for: propertynam

Hi all, I have a property, defined in an external stylesheet: .my_class { background-color: #FF0000; } I want to retrieve the value of this background-color of the class my_class. How can I do that with prototype/scriptaculous ? Thanks in advance, Nicolas Terray

...belongs_to :markable, polymorphic => true end class Property < ActiveRecord::Base has_one :name, :as => :markable has_one :value, :as => :markable end ? Based on what I know of the underlying implementation, this looks impossible. One alternative is to declare artificial classes PropertyName and PropertyValue, each of which has_one :value, :as => markable and then change Property to has_one :property_name and has_one :property_value: class PropertyName < ActiveRecord::Base has_one :value, :as => :markable end class PropertyValue < ActiveRecord::Base has_one :value,...

...point @@ -334,6 +369,16 @@ logN: function(number, base) { return Math.log(number) / Math.log(base); }, + + /** + * returns array of loaded provider apis + * @returns {Array} providers + */ + getAvailableProviders : function () { + var providers = []; + for (var propertyName in apis) providers.push(propertyName); + return providers; + }, dummy: 0 @@ -341,4 +386,5 @@ dummy: 0 }; + })(); Modified: trunk/source/mxn.yahoo.core.js ============================================================================== --- trunk/source/mxn.yahoo.cor...

Newbie-alert: I'm just getting started on a new project involving a full text search requirement, and my initial investigation points to xapian being the way to go. Two questions: - eventually I'll most likely be indexing towards 50 million documents - is this reasonable to expect or attempt with xapian? - each of my documents come with a set of attributes. These are easily stored

...# it''s a setter! # remove the trailing = methodnameStr.chop! return setProperty(methodnameStr, args[0]) else # it''s a getter! return getProperty(methodnameStr) end end # helper method for setting the given property def setProperty(propertyName, value) property = self.properties.find(:first, :conditions => [ "name = ?", propertyName]) if (property.nil?) # Looks like the property does not yet exist. # Create it and set the value... property = Property.new(:name => propertyName, :value => value...

...; propcol) at Microsoft.SharePoint.Utilities.SPUtility.GetUserPropertiesFromAD(SPWebApplic ation webApplicaiton, String loginName, String[]& origUserAdProperties) at Microsoft.SharePoint.Utilities.SPUtility.GetUserPropertyFromAD(SPWebApplicat ion webApplicaiton, String loginName, String propertyName) at Microsoft.SharePoint.Administration.SPManagedAccount.GetUserAccountControl(S tring username) at Microsoft.SharePoint.Administration.SPManagedAccount.Update() at Microsoft.SharePoint.Administration.SPProcessIdentity.Update() at Microsoft.SharePoint.Administration.SPApplicationPo...

This is enough to enable tessellation support on nvc0. It seems to work a lot better on my GF108 than GK208. I suspect that there's some sort of scheduling shenanigans that need to be adjusted for kepler+. Or perhaps some shader header things. Even with the GF108, I still get occasional blue triangles in Heaven, but I get a *ton* of them on the GK208 -- seemingly the same issue, but it's