Hello Ambrose. Great to see you at Infragistics! I am a recent new customer and have been spending more time on the UltraWebGrid than I would have ever imagined when we bought the product. The samples in the KB are nice, but the documentation is still VERY spotty at best, which is giving us a VERY hard time being productive with it. For example try to find any decent explanation on how to use the invokeXMLHTTPRequest method on the UltraWebGrid.
So yes, one aspect to work on would be the documentation :)
Codemunicator seems to be a great job title :-) I'm a regularly reader here at the infragistics blogs and I'm looking forward to reading some great stuff here in yours ;-)
Thanks guys. I promise I won't be this tardy in responding to comments in general. I just had TechEd, holidays, and a bunch of other stuff get in the way. Plus, I'm not getting any notifications about comments, so I just plain didn't know they were here until I looked.
Michael, I'm sorry your experience with the docs has been less than optimal. We are working on improving those, and if you have specific areas (as you pointed out), please do share them. I imagine you're long past figuring out the invokeXMLHTTPRequest issue, but if not, let me know, and I'll try to come up with a sample for you.
Site looks great - nice job. Quick question: is the modal pop-up you are using an new control you will be providing or might that be the Atlas control or some other version out there. I have a need for such a control.
Hi Kevin, that was written specifically for the site. I've contacted you via email, but if anyone else would like to see a control like it (see the popups in the control galleries to see what he's talking about), let me know.
Love the new site...the layout looks great. questions: the vertical layout and space between the tab is it done in quick design or CSS. Can you tell me which part is using CSS and which is using the built-in quick design? Is it possible to send a sample project using this layout?
The styling, beyond what you see in the igweb:FeatureWebTab declaration in the post, is all done with CSS. In order to get some extra styling points, you can insert those in your content panes or tabs.
Here are the essential styles for the tab layout:
.FeatureTabs .Normal .tabTitle
.FeatureTabs .Selected DIV
.FeatureTabs .Selected .tabTitle
You can of course take a peek at all of them by grabbing our CSS files. The styles for the feature tabs are all in the control.css file. The spacing is chiefly due to the padding.
Thanks Ambrose. I will give this a try.
I upgraded one project that was using the 2006 Vol 3 - Office 2007 ribbon to the latest 2007 Vol I dlls and I started getting errors in my winform designer: Object reference not set to an instance of an object. Something to do with the UltraWinToolbars Dock Area elements.
I can't personally provide a solution, but we have a lot of avenues that may be able to help. Go to www.infragistics.com/gethelp to see the ways you can get help for specific issues like this.
My preferences would be C, then B and then E. For a demo that can have lasting effects even after I uninstall it (a very unfriendly practice) a VM copy would be mandatory for me.
I like to try out various products, and unfortunately, a great many of them do not live up to their marketing. Therefore, I like to just download the basic package. If it meets my needs and interests me then I download the help and whatever samples might be available. If a product doesn't live up to what it claims or isn't what I was looking for, forcing me to download 500MB only to uninstall it is a quick way to make me never want to try another one of your products.
If the trial and uninstall were a quick and pleasant experience (even if it wasn't what I wanted or a little to buggy) then I'm much more inclined to keep an eye on it and download it in the future.
As an owner (just reupped NetAdvantage.Net for the nth time) I would prefer the whole megillah, although having a shell available for a selective install is a nice option. I always tuck the whole thing away for a rainy (internet-is-down) day that requires a reinstall, so I would always end up downloading that anyway.
I'd prefer 'A' to get the whole ball-o-wax. A half-gig is no big deal on broadband...start her goin' and go get a coffee...everything is there when you get back.
BUT, and it is a pretty big BUT, I strongly recommend you make your help files and/or user guides available separately. I don't even mind if they download with the huge package but I DON'T want to have to install the demo just to explore the help and/or user guides.
When I evaluate a tool my first stop is your web site, then your online samples, then your documentation and then, maybe your demo. I might get my questions answered and place my order without even installing the demo.
Regarding a product evaluation, I'd prefer an online VM environment for trying some basic features. If it turns out, that I like the product, I would go for a full donwload.
The reason for the VM is that I don't want to mess up my hdd with every piece of software I like to evaluate.
I prefer C, then B.
Thanks for asking.
To test product functionality and evaluating:
i would prefer D) a VM where i can test new features. would be great, without install. anything...
to get the new version i would prefer A)
download all, install all, i have all on my desktop!
<P>I would Prefer A.</P>
<P>Get it download everyting and be ready before you start getting into the mood of evaluating. Let us say, you started with a tiny piece and it depends on something else and that depends on something else... it will go on forever till you endup downloading everything. This would leed to a frustration and may even give up in the middle.</P>
<P>I would rather have everything needed before even getting into that action and need not worry about not having something ready when you are in the middle of the work.</P>
<P>Thanks for the enquiry.</P>
Wouldn't miss it...
Read the book Object Thinking (based on your recommedation in the Story doc, thanks!). Wondering if this diagram needs to call out the collection objects as individual objects as well? For example between Calendar and Events there is a method on the Calendar object called GetEvents. This indicates the existence of an Events object which would have it's own behaviours regarding the aggregation of Event objects.
What are your thoughts on those being visible in a domain model or are they simply implied since we don't care about cardinality in these types of diagrams?
It would be nice if the VS class diagram could handle method return types like it handles properties--allowing them to be shown as relationships. It doesn't. I think I may have just used a generic List there, anyways, but FxCop recommends creating custom collection types derived from Collection<T> (IIRC), so yeah, I'd show that here if it had interesting behavior. Probably wouldn't show it, though, if it was just meeting the requirements/recommendations of the platform (as would likely be the case here).
It's not a perfect diagramming tool, especially w/o annotations as this image is. I usually finish my diagrams with annotations to elucidate the dark areas, and I use XML comments to do the same verbally in the API itself. If you had this loaded in VS, you could see those (if you were studious enough).
Anyways, the nice thing is that this DSL leaves you with the shell of your domain model already implemented. If I had my druthers (read: time/resources), I'd write my own DSL that would handle better modeling and also generate a lot of the boilerplate stuff to play nice in .NET.
Does Infragistics plan to host symbol files in a similar manner so that we can debug into Infragistic code just as easy? I know we can download your source now but this is a much easier way of doing things.
We are looking into ways to make debugging easier for our customers. I can't say yet if we'll be able to take advantage of this feature. Thanks for the feedback.
Really nice ground breaking work.
Great work - as usual!!
This looks ace guys.
I'll have to defer to our public roadmap (www.infragistics.com/.../roadmap.aspx), which says that our first release is targeting shortly after Silverlight 2.0 is released later this year.
Sweet app Ambrose. Of course, it doesn't work if your locale is set to UK (data parsing errors); I suspect this would be the same for other locales.
We do have culture-specific date parsing in the service, as you know. We figured we have control over the server, but yeah, it would be best to make it culture-smart. Maybe in round two. :)
I agree 10000000%
im trying to run the solution in VS2008
i get this error
Error 1 The "AddZhSatellites" task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with <UsingTask> in the project file, or in the *.tasks files located in the "C:\WINDOWS\Microsoft.NET\Framework\v3.5" directory. Infragistics.Labs.Silverlight.FaceOut.Presentation
The guys tell me that it looks like you're using an old version of the faceOut sample. Can you try downloading the latest from the Web site? If you have further issues, I recommend posting in the samples forum (forums.infragistics.com/.../68.aspx).
My new Infragistics Install Experience...
Good, but is missing the uninstaller (on request) of the previous version ...
I used the Platform Installer. It was very nice and convenient. The only issue I had is that it took all night to complete. I stopped it twice because after a couple hours I thought I had set something up incorrectly. Once I left it alone overnight it looked like everthing installed correctly.
Clay, that doesn't sound right. I'll ask someone to follow up with ya on that.
Could you please send me the details of your envioronment to my e-mail dabraham at infragistics dot com? Looking for RAM available, OS, any antivirus, internet speed. Also, did you select all the componets to be installed? We are looking into the performance issues reported by some of the users, trying to understand a pattern and fixing them soon.
I have always had excellent things to say about Infragistics until today. My install experience is the WORST that I've ever had. Please figure something else out. Overnight is pretty close to reality. It took me 15 minutes to install just the Windows Forms with no other options selected, and the latest deselected. The first try I selected everything and it was just frozen, so I rebooted after an hour of inactivity. What gives?
@air1kdf - yes, we did discover some perf issues that have significant impact in certain scenarios. We released an updated wrapper with the NA for Windows Phone launch earlier this week. Please email me at ambrose at infragistics dot com if you keep experiencing these issues.
I downloaded the CTP and made sure the reference to the dll is made, but "UndoManagerCommandSource" is not being recognzed by the designer. Do I need to put the undo.dll somewhere special?
Thank you to everyone who attended my TechBash sessions last Saturday. It’s never easy to give
As a former CIO, and in spite of beeing almost 60 years old, I cannot understand how IT "experts" cannot see the importance of touch screen in LOB apps. Just think in Hospitals where touch screen devices, strategically placed, can be a synonymous of increased productivity. Stop thinking Back Office, and put doctors, nurses, and other seeding data to the System in real time. Time based information is crucial! I could extend this to other industries and services "ad nauseaum". C'mon stop beeing "change resistant"
I disagree. Why is it so important to put everything on a tiny touch device, bound to overheat, get lost, get stolen and/or be outdated faster than a PC? Does everyone use a tablet and smartphone, no. Many do, but how fast can someone type up a document, design it, format it etc.. on a tiny touch device? I'm talking DAY TO DAY work. The article makes Metro sound like it works for everything, no caveats, no misgivings just all positive spin. Rah! Rah! A happy worker produces more, surely who could argue that, but what exactly are they going to produce more of? Original content? Hardly! The business apps will dictate that which the user will be able to create on a tiny touch screen. Ah right, they could put the video out on a bigger monitor that they've already been using for decades. Calendar and scheduling apps are a no brainer for Metro, though they've also been around on touch devices for years as well. What's the point of this article again?
While I do agree with the main topic of this article - that we as developers / designers / BA's need to focus on the user experience in LOB apps - I don't necessarily agree with MS's approach to this topic. I think the solution is closer to what they enabled with WPF/XAML - an expressive UI language that enables us to easily design usable applications. What they're doing with metro is saying "here's your new design, now use it".
There are definitely nice things in Metro that will help with usability, but to say that this one design can and will address all foreseeable UX issues in LOB applications is the same as saying "all your forms should be battleship grey". I would've liked to see them focus more on the OS integration like they do with live tiles, application settings, and other nice Win 8 features, and focus less on mandating all all future apps use Metro as a theme.
You offer valid points and I think there is no question that LOB *can* be done using Metro. However I think you forget that in the typical corporate world technology moves at the speed of the lowest common denominator: the business.
So it's not as much about *developers* placing a road block to Metro apps as much as it will be a slow process because of the speed of the business even getting to Windows 8. Then add on top the time to either successfully migrating key LOB apps or create new Win8 Metro apps.
I think your article focused more on the developer being resistant to LOB Metro apps, where I think it's more about the time it will take and the familiarity with the product from the business standpoint.
Here are some of my own thoughts (and no I am not the guy that said there are only 5 Metro apps ;-) ) on this topic: allen-conway-dotnet.blogspot.com/.../future-of-creating-line-of-business-and.html
Nice prose - but can you give, now, a concrete example of an customer contact form, an invoice form, an order from that has a "Metro" UI?
Than put that form in front of a 40-year old accountant and see how quick gets used to it and how productive is after that.
That's 95% of all LOB apps developed every day by thousands of developers wordwide - if you replace the menu with something more fancy is less important.
Thanks for the comments, guys. Some brief thoughts in reply:
@novreis - Yep, good observations.
@leknowlton - Microsoft has designed Metro/Win8 with more than just tablets in mind. Touch first works even for just touch enabled monitors. In fact, many of the principles, if applied, make for more usable interfaces even if one doesn't have a touch input device.
@ChadEmm - We're all welcome to our opinions of the Metro design language. There is actual value, though, in having a strong, enforced design language--because most devs (especially those working in internal/LOB environments) don't have access to designers. It takes some of the guess work (and hence the mistakes) out of it for devs. Even with the strong design language, there is plenty of room for making a beautiful, custom app using it. Check out Cocktail Flow, for example. But the fact is, most LOB apps don't need that level of stylistic expression, and a design language like Metro gives devs a step up to still create a pretty nicely styled app that is more usable than they might create today. Metro as a default is better than battleship grey or WPF white (or that bland default SL style).
@atconway - No doubt there are other barriers, but where we're at right now is in pre-early adopter phase. A lot of the folks thinking about (and criticizing/prejudging/dismissing) Metro are devs, so that's what I wanted to address here.
@tudor - Sure, check out the link to the Dynamics AX. And Microsoft has put Metro designs in front of 40-year old accountants. ;) Metro is not about being fancy; it's about being more useful and usable. The same could be said for mobile-first in general. I encourage you to read up on it. Even if you don't develop for WinRT, your designs will doubtless improve for the effort.
Great article...these nostalgic things are what strike beauty into the design, things that are part of our history and what apple has done very well at to incorporate into the experience.
While watching the live video from the Microsoft Office Preview event, me and my colleagues all had the
Have you ever found yourself in the situation where you had an app idea, but you didn’t have the time
In the previous post in this series, we went through the secant of five principles that guide successful
Why?? Seriously . Interaction prototyping is so much more effective. Honestly, it's a little baffling
You are absolutely correct Ambrose. In fact, I suggest we rename Adaptive/Responsive Web Design. It isn't "design" from our perspective but rather "display". Keep the acronym but place the focus where it truly is - on the device. If someone wants to understand how to organize the display, do the research and the prototyping.
I'm with ya, Kevin. Design is probably not the best term here, at least not in the big D sense of the term.
As the product manager for Indigo Studio, I get to keep an eye on what people are talking about in terms
Mióta nagyobb arányban használok kisebb kijelzős és érintőképernyős eszközöket, gyakrabban villan belém
Infragistics Undo/Redo Framework CTP - Evangelism - Infragistics.com Blog
PDC 2008 = Awesome - Evangelism - Infragistics.com Blog
What's New in Ignite UI and ASP.NET 14.2 - Evangelism - Infragistics.com Blog
Ignite UI Page Designer: Beta Testing - Evangelism - Infragistics.com Blog