sudo visudo
user1 ALL=NOPASSWD: java -jar /usr/local/my_app.jar
gksu gedit /etc/rc.local
-=Oleg=-
-=Oleg=-
./appengine-java-sdk/bin/appcfg.sh vacuum_indexes myapp/war
appengine-java-sdk\bin\appcfg.cmd vacuum_indexes myapp/war
[/caption]-=Oleg=-
-=Oleg=-
-=Oleg=-
-=Oleg=-
-=Oleg=-
-=Oleg=-
-=Oleg=-
-=Oleg=-
Changing the styling of the Silverlight controls is simple. It’s somewhat similar to CSS, but it's more robust and syntax is completely different. What is different in Silverlight and WPF is that you can completely re-define control’s UI and behavior using styles. It took me about 20 minutes from absolute zero to the “Aha!” moment and become an expert in styling WPF and Silverlight applications. Here are the 3 links that helped me to clear the mistery behind Silverlight styles:
1. Using Style Elements to Better Encapsulate Look and Feel – a good example of how to change control’s properties using styles
2. Using Control Templates to Customize a Control's Look and Feel – a step further that shows how to make control look anyway you want. In other words how to draw control’s UI from scratch or combine several controls into one. All using styles! Pretty amazing yet simple.
3. MSDN: Customizing the Appearance of an Existing Control by Using a ControlTemplate – the final piece of puzzle is about how to make control to react on events like Pressed or Disabled and change its appearance. Just few more words about this. Basically every control has a list of pre-defined events (they called states in Silverlight) which can be referenced by ControlTemplate. The list of states differs for each control. This information is available in MSDN on control’s Class page as a list of TemplateVisualStateAttribute attributes applied to the class.
-=Oleg=-
-=Oleg=-
public class MainClass
{
public object Data { get; set; }
}
public class ChildClass1
{
//some properties
}
public class ChildClass2
{
//some properties
}
where Child Classes can be assigned to Data property of the MainClass and if you construct XmlSerializer object like this
new XmlSerializer(typeof(MainClass));
Then both serialization and deserialization will fail throwing an error saying that it has no knowledge of ChildClass1 or ChildClass2 classes. To resolve this error you need to provide XmlSerializer with additional class types which serializer may meet on its way when parsing XML string. Here is how to do that:
new XmlSerializer(typeof(MainClass), new Type[] { typeof(ChildClass1), typeof(ChildClass2) });
Here is the set of functions I use to serialize / deserialize my objects:
public static string SerializeToString(object aObject)
{
return SerializeToString(aObject, null);
}
public static string SerializeToString(object aObject, Type[] extraTypes)
{
XmlSerializer aSerializer;
if (extraTypes == null)
aSerializer = new XmlSerializer(aObject.GetType());
else
aSerializer = new XmlSerializer(aObject.GetType(), extraTypes);
MemoryStream aMemoryStream = new MemoryStream();
StreamReader aStreamReader = new StreamReader(aMemoryStream);
XmlWriterSettings aXMLWriterSettings = new XmlWriterSettings();
aXMLWriterSettings.Encoding = new UTF8Encoding(false);
aXMLWriterSettings.ConformanceLevel = ConformanceLevel.Document;
XmlWriter aXMLWriter = XmlWriter.Create(aMemoryStream, aXMLWriterSettings);
aSerializer.Serialize(aXMLWriter, aObject);
aXMLWriter.Flush();
aXMLWriter.Close();
aMemoryStream.Position = 0;
return aStreamReader.ReadToEnd();
}
public static object DeserializeFromString(string aMessage, System.Type aType)
{
return DeserializeFromString(aMessage, aType, null);
}
public static object DeserializeFromString(string aMessage, System.Type aType, Type[] extraTypes)
{
XmlSerializer aXMLSerializer;
if (extraTypes == null)
aXMLSerializer = new XmlSerializer(aType);
else
aXMLSerializer = new XmlSerializer(aType, extraTypes);
System.IO.StringReader aStringReader = new StringReader(aMessage);
return aXMLSerializer.Deserialize(aStringReader);
}
-= Oleg =-
