CAT | Out of Curiosity
1. No penmanship recognition
2. No stylus, it must be hard to go on an inspection or to a patient’s house and type your notes while you hold the iPad, with a single hand, hand write recognition has been there on tablets for a while.
3. No Flash support.
4. Hard to program on.
5. Censorship by Apple of the apps you are able to run on.
No tags
18
The Aqua Tower in Chicago, my favorite piece of architecture
No comments · Posted by lizet in Out of Curiosity
Visiting downtown Chicago I couldn’t help but falling in love with this piece of art and its eternal waves…
AQUA from Spirit of Space on Vimeo.
No tags
13
Silverlight development on Eclipse, with c# though :)
No comments · Posted by lizet in Out of Curiosity
For all the Java junkies that can’t get away from Eclipse, please see the release of Eclipse4SL from Soyatec.
I particurlarly prefer Visual Studio but can tell that the Express editions are not the best choice when debugging .NET code.
No tags
No tags
9
The best explanation of the credit crisis in just 5 mins
2 Comments · Posted by lizet in Out of Curiosity
I saw this video first on this speaker’s blog Sacha Chua
and vimeo’s copyright seems okay with bloggers like me embedding their videos on their sites.
Kuddos to the author Jonathan Jarvis
Enjoy! … the video, not the credit crisis…
The Credit Crisis – Animatic from Jonathan Jarvis on Vimeo.
No tags
17
Top worst ten bugs in history of software.
No comments · Posted by lizet in Out of Curiosity
I got this on a newsletter at work:
Top Ten worst bugs in history.
I remember the floating point bug on the Pentium. We received a few Pentium machines for the electronic lab at the University and that was the first thing we tried… and yes, there was a bug. It was fun to know why…
No tags
25
Adding an NHibernate collection to your QuickWatch initializes it
No comments · Posted by lizet in NHibernate, Out of Curiosity
I spent most of the day trying to improve performance on an application. We use NHibernate 2.0 and try to lazy load most of the collections.
I found these two links very useful for troubleshooting my performance issue:
http://djeeg.blogspot.com/2006/08/nhibernateutilisinitialized.html
and the NHibernate reference:
http://www.hibernate.org/hib_docs/nhibernate/html/performance.html
The curious thing is I got really confused when testing my
NHibernateUtil.IsInitialized(_myobject.MyCollection) line and it was false
but I saw a query retrieving the collection in Profiler… 
until I realized that adding the collection to the Watch initializes it. The same happens if you open this collection in QuickWatch. :-p
No tags
19
If you call your .NET application from a batch file…
No comments · Posted by lizet in .NET, Out of Curiosity
If you deploy your .NET applications with a batch file, be aware that the way you call your .NET application might affect how it behaves.
The facts are as follows (for our application anyways):
when the application is called using the following line in the batch file:
start C:\Progra~1\ApplicationFolder\Application.exe
the application fails
if you call the application using the windows explorer in the batch file:
explorer C:\Program Files\ApplicationFolder\Application.exe
it works fine but it shows a security warnings that you’re downloading files and that publisher is unknown…Not good for the end user, not good.
If you call the application from a path that doesn’t have white spaces using the start command, it works fine:
start C:\ApplicationFolder\Application.exe
(This option would be good if we didn’t use Program Files for the deployment, but most people do)
and, finally, if you use the start command but take out the DOS path it works!
start ” ” “c:\Program Files\ApplicationFolder\Application.exe”
I checked the assemblies binding errors, the code access security for every assembly in the application, debugged the application, et-cetera without results.
Changing the old DOS path did the trick!!!
Why? I still have to get a hold on this script guy to ask him why :-p
Happy coding!
No tags
