The Silverlight Application Package extension is given as ".xap" which is a zip file. Why is it named XAP? why not something else? Does anyone know why microsoft went with the name XAP? Is there any meaning to XAP? or is XAP an acronym?
SAP
Trademarked. German Software Company. Out.
SLAP
A slap or "smack" is a broad stroke
made with the open hand, as opposed to
a punch that is made with a closed
fist. Slaps are frequently made across
the face, but can be also made across
hands or any other body part, and can
use either the palm of the hand or the
back of the hand.
Not the best connotation you need for Silverlight. Out.
XAP
XAML Application Package. Descriptive. Nonoffensive. Beats Apache to the punch nicely. In.
Two options come to mind:
A contraction/abbreviation of XAML Application (or XAML Application Package).
A contraction/abbreviation of cross-platform application.
I suspect it may have been the first option or possibly a combination of both.
Related
I am tasked with the localization of a Windows Phone 7 application. The first step is to replace the actual visible text with an ID and put the ID and the text in a resource file.
This is a very tedious work and I was wondering if there are tools for this to automate?
I am thinking along the lines of the gettext package and .po files used in the linux world.
Here is a codeplex project that may help you some. http://xlocalization.codeplex.com/. To use this method, each control that is to be localized must have the name property assigned.
I tried it with my existing project, and got results that were mixed, but in the long run, I decided to do it by hand. I don't remember specifically what the problems were that I had, but if you want to try it on a copy of your project, it won't take much time. If it works for you (and if your controls to be localized all have names), it could save you time.
Also, I don't know how familiar you are with localizing, but I wrote a blog on the subject that takes you from start to finish. It's at http://www.hopnet.mobi, click Blogs.
Hope this helps.
I know this will get a lot of traditional answers, but I would also like to put forward something completely original we tried (and succeeded) doing ourselves for more efficient localisation of Silverlight using Attached Properties instead of binding:
Localisation of Silverlight projects after completion
To pre-populate the database we wrote a XML parser to find our markers in all our project's XAML files (XAML is just a subset of XML after all). We could not find any existing tools to do what you suggested, but our requirements were simplified by our new method of localisation (no resource files and no horrid bindings).
(yes, this is almost the same answer as a previous one of mine today, but it seems to fit again).
Also for future reference keep an eye out for this tool: http://www.neovelop.com/ This tool will go in private beta soon and looks very promising. Judging from their preview movie this will do exactly what you asked for.
I have read a range of articles on advantages/disadvantages of Microsoft Silverlight framework in comparisson to Flash.
Fact that there were two version of Silverlight in the past 18 months worries me, as well as the fact that over 97% of web browsers already have Flash pre-installed.
I'm a .NET developer and I'm very happy with what I can do in the framework. At the moment I feel like I have to put my own preference to a side and decide whether I need to integrage flash with .NET instead of using Silverlight with WPF.
Did anybody try integrating Flash with .NET? What challanges did you come across? How easy was it in comparisson to working in Silverlight?
I have also read about recent talks between Microsoft and Adobe. Whatever way I go It feels very unstable. Can HTML 5 really compete with what's offered by Flash and Silverlight?
Thank you
I have integrated both Flash and Silverlight into my ASP.Net applications. I have to say that working with Silverlight was by far the easier way to go. Communication with the server is easier, initial setup was easier (along with a ASP.Net application or a simple HTML page). Integration into the ASP.Net application was the easiest part (as I'm sure you imagined it would be). If you're a .Net developer, then this is the way to go.
Also, I wouldn't worry about either of these technologies going away anytime soon. HTML5 is not going to take over. It'll take some of the market share, not all.
EDIT
Here are some links to other SO posts on the subject:
Which is the future of web development: HTML5 or Silverlight(or other RIA framework)?
Should I Abandon Adobe Flash for HTML5 and ?
Can HTML5 do most of what Flash does today?
This is basically the way I pick web technologies:
do you need to support every available platform made now, in the past and in the future? HTML4 (yes, 4!)
Do you have to make stuff that is not possible with HTML4, and are ready to sacrifice some user base? HTML5
Can you limit yourself to desktop users (no mobile devices) and need a very interactive application (more so than a "website")? Flash or Silverlight
Do you need to integrate with .NET? Silverlight
Are you familiar with .NET (more so than Flash)? Silverlight
Do you want to reach the absolute maximum number of users? Flash
Do you know Flash/ActionScript (more so than .NET)? Flash
Do you need even more features than what Silverlight provides, and can you limit your deployment to intranets? WPF/XBAP
The whole debate around Silverlight being dead is completely flawed in my opinion: those that thought Silverlight would be completely multiplatform really were not connected with the reality: just by looking at Flash it was clear from the beginning that iOS & co. would never support Silverlight.
HTML5 will probably be the real "universal multiplatform" environment (what is HTML4 now), but with all the nightmares we all know of html. If you are targeting desktops and need more interactivity, better tooling, unit testing & co. then Flash and Silverlight will still be the first choice.
Silverlight's user base is quickly coming close to Flash, so between those two it really comes down to the one you know better and the ease of integration with an existing backend.
The fact that Silverlight got a new major version every 9 months until now is just a sign of how much they are pushing it. Now that it's reached a mature stage you can expect to see larger intervals.
Frankly, AS3 is not hard to learn if you already know OOP. It will take a week or so. If you don't like all the frames stuff in Flash, you can create a single frame app and then manage everything from your custom AS classes.
I'm also a .NET developer, and I had no trouble learning AS3.0. Of course, one week is not enough to become an expert (it takes years to become an expert in any field). But if you simply need to create video or mp3 players, create drag and drop basic games/apps to add to an ASP.NET page, it's worth spending 20 or 30 hours on AS3. There are great video trainings out there . Seven or 8 hours training should take the 20 to 30 hours I mentioned. I went for AS3.0 a few years ago, rather than SL, simply because everybody has Flash plugin installed.
AS3.0 is typed (simple types like Number, String etc), but at least it's typed. There are plenty of functions, classes and methods allowing to implement hit tests, drag/drop, event listening (mouse events, keyboard events etc). Really cool and fun language.
Take care.
HTML5 has SVG and Canvas and video.
It's perfectly possible that at one point someone creative is going to create a very nice animation package that generates SVG files. There already are SVG generators there of course, but obviously they're not good enough because SVG and Flash is, so far, never mentioned in the same sentence.
But is ought to be possible. SVG does structured vector graphics, embedded scripting. The things you see done in Flash has to all be possible in SVG. Flash also has this awful notion of frames, which was a major design flaw from day one.
They should have just let you determine that you want to move an object from point A to B along a path determined by a line or curve or freehand path, and that the times of A and B can be anything and not just confined to a particular frame.
Then at playback, the faster your computer is, the better the frame rate ends up being. Slower computer, slower frame rate. As long as the object moves from A to B.
Then there are the bugs and just overall clumsy handling of Flash.
Flash can be done so much better.
So, I think that someone will at one point soon make an amazing SVG animation package that will just crush Flash.
I'm against Silverlight because it's Microsoft. Microsoft means proprietary. They do whatever they want to do. You've already mentioned different version numbers. This means your customers have to have the right version downloaded. You can count on your customers having to download major upgrades, and before you know it their entire .net install needs updating, before you can show your animations and applications.
Silverlight also doesn't work on Linux. It's supposed to, through Novell's efforts with Mono, etc, but in practice, in the field, it just does not work where you need it to.
I don't know if and how well, in practice, Silverlight works on the Mac, but I don't trust it.
Eventually, I think, that future HTML5/SVG (Canvas maybe?) is the way to go. It'll even do 3D using OpenGL accelerated graphics... (but I don't know if that's portable enough).
In the meantime, Flash is your safe bet, and it's almost guaranteed to run anywhere.
I wonder if anyone has created an animation package that outputs to swf files that's better than the Flash IDE. Shouldn't be too hard, given Flash IDE's clumsiness.
Microsoft recently announced a "change of direction" with Silverlight with more emphasis on mobile rather than desktop.
Flex/Flash and SilverL. now are very similar... using webservice for the clientt/server comunication you can work well with both.
Sure, for .NET developer with Visual Studio to use SilverL. is much more FAST and you need C# only.
But, Flash is more available on PCs, also for mobile devices... you could think for Flash if you need portability.
I'm trying to find out if Embedded Open Type (.eot) files can be used in Silverlight. I found an older post that says they can't, but it's a few years old and given how fast SL has moved, I'm not sure if that has changed.
If so, how would they be used? As a <Glyph/> object or...?
I don't think so. You can embed true type fonts fonts in your Silverilght app though. Expression Blend makes it easy to do, simply select a font and then tick the 'embed' box. You would of course need to make sure you met any font licensing requirements for fonts that you embed in your application.
The fonts are embedded as a zipped resource within your dll via a custom build action called 'BlendEmbeddedFont' and then referenced like this in your app:
<TextBlock Text="TextBlock" FontFamily="/SilverlightApplication12;component/Fonts/Fonts.zip#Segoe UI" />
No. This is because Silverlight (like Flash) thinks of itself as an "application", not a "document". There's a lot of banter on this subject of font embedding vs. linking and web fonts. Silverlight incorrectly uses the word "embed" where it actually "links" instead.
Like any good technology though, it may be possible to reverse engineer an EOT file though - these security guys did it using IE: Reverse Engineering the Embedded OpenType Decompression. I don't think would be illegal in any way as the compression/decompression is a submission to W3C on http://www.w3.org/Submission/2008/SUBM-MTX-20080305/ (although it may make the font foundries a little angry). Or maybe you could look at this ttf-to-eot converter and do the reverse: http://code.google.com/p/ttf2eot/
Anyway, you have a lot of work ahead of you if you want to go down this path.
My concern is that novice users will turn their back to a website which asks them to install Silverlight.
One of the reasons I think they might be scared of installing Silverlight is because they are not aware of what Silverlight actually is.
What's your take on this?
You can see the website riastats.com for information on install base, the main thing is if Silverlight gives an advantage such as the NBC Olympics coverage in United States uses Silverlight because of the Smooth Streaming technology plus the ablity to have a Live DVR where live streams can be "rewound" - all these features are probably better supported by Silverlight has the Client and Server ends can be well integrated (with Microsoft solutions).
I may be a little biased as I am a Silverlight developer, but with a less than 5MB download for runtime, that helps sell it more - especially as it may be a better alternative than the Flex download for Flash if this is required to create a solution that would have worked in Silverlight as it is a larger download.
Check out the silverlight.net showcase you'll see who and where it is being used - you can then make your decision based on this - rather than a few opinions (including mine!).
Well Silverlight is installed on about 50% of pc's now. So it depends on your market. Normal web users (ie. non-developers) tend to install anything you prompt them to if you can clearly and succinctly give them a compelling reason to run your application.
It doesn't tend to matter outside of the work place environments if you use silverlight or flash. What's more important is that your application will solve a problem the user has, and you can communicate that well.
They do not know what is is, marketshare is around 40%. I'd say it's not ready if you want to reach everyone.
However if Flash or javascript is not an option, give a firsttime visitor window informing your clients about silverlight.
I think you're going to have a lot of users on the public internet that don't have it installed. If you're really going for a mass-market site, and you aren't doing a crazy amount of media-rich type content, I would go with something like JQuery to make your Javascript easy and cross-platform.
I really need a way of loading a .ppt document in my wpf application. Can anyone give me a hint, code sample?
Checkout the following discussion thread. Also Dr.WPF got an interesting article that might help you as well: Hosting Office in WPF Application
However consider license costs will be quite high for your scenario...
According to this artice the DSO Framer is no longer supported. Have to look for something else.
You may need to elaborate a bit more on your particular need to get a practical answer.
I don't think hosting PowerPoint (ppt) is a good option because it requires ppt to be installed on the target machine.... and if the target machine has ppt then you can use its API to save the document as HTML and open it in a WebBrowser control.
If the target machine doesn't have powerpoint you may look into some online file conversion service and try hooking up there to convert to HTML and still use WebBrowser control.
I definitely don't recommend wasting your time with DSOFramer - it's very unstable at best and it will just feel like you're one step away from making it work for a while but it doesn't work.
Another option is of course to write your own parser for ppt files, the OfficeOpenXML version of the files is definitely "parseable". I've done that for Word docx and it's relatively easy to get the course data out of the document - say shapes, text... - but the devil there is in the details. There are a zillion little features to implement.