|
I admit I can't see any logic to it: LinkedIn does seem to be the breeding grounds for the world's dumbest recruitment agencies rather than anything particularly usable. Lot of money for just all our personal details...maybe I should close my account... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
My first thought was also to close it...
I actually maintained my account to see some proposals, but only contractors made connection...
I just can't imagine what MS will do with it...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Keeping an eye on your personal info!
Shuvro
|
|
|
|
|
May be blow up the whistle too! 
Shuvro
|
|
|
|
|
Hmm.
Now would be a good time to set up inlinked.com, to take over, after ms has screwed up linkedin.
We'd better be quick, though. The ms screw-up velocity* had been increasing geometrically.
* "velocity" means speed in a particular direction**
** "Particular direction", in this case, means very much the wrong one.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Well thought
Shuvro
|
|
|
|
|
No, but I bet we're going to see plenty of advertisements by MSFT; advertisements targeting rival technologies. I am starting to think this is genius, but 26 billion for a junky HR website seem excessive.
|
|
|
|
|
And we will probably see Google, Oracle, Amazon, and Intel all change their HR policy so that employees must delete their LinkedIn accounts as a condition to hiring. Once LinkedIn is aquired, Microsoft will be able to easily index who works for who which will give them an unfair advantage in head-hunting skilled professionals and tracking what skill sets are getting hired the most. They can gauge the direction the industry is moving based off hiring today and not future revenue reports allowing them to position Microsoft ahead of the curve, at least that's the way I see it.
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
At first I figured that it was just an exercise in learning what went on behind the scenes, and that the layout designer would be introduced in chapter 10. But...
Xamarin Forms are all hand cranked XML or C# runtime code? No visual designer at all? 
Have I been transported back to pre-Visual Studio days?
XAML is verbose, cumbersome, and prone to errors - so a designer that lets you do the "donkey work" a-la WPF is a must, isn't it? But no. I know it's a lot of work to do from scratch, but surely MS can rework the WPF designer for the job? You want this taken up as mainstream (and I can see why it might be a damn good idea) you have to provide suitable tools, not a half-assed syntactic highlighter for notepad! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Actually, doing ASP.Net web forms, I never work in the designer. I do everything in source. But for learning a new tool, a visual designer would be very important.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Not just for learning: throw the basics together in the designer so they all have the right attributes to work together, then tidy up and customize in the source. Or (if the designer is as good as WinForms) say "sod the source" and let the designer do the donkey work!
I thought the idea of XAML was that visual designers did the XAML via tools, and the developer coded the stuff that does the work behind the scenes? Since most visual designers couldn't code their way out of a paper bag and most developers appear to be colour blind (and believe that 50 controls to the square inch is a good average) that makes a lot of sense.
But expecting visual designers (who can't reliably tie their own shoelaces but will have excellent taste in shoes) to work with raw XAML is daft.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Maybe you can hire a programmer via LinkedIn to develop a designer for you.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Now Griff, you're generalizing, designers are to hip to own shoes with laces.
It takes some time to learn both the presentation and logic layers of WPF. I can now build the visuals of an entire app in XAML or from code behind but the later takes a lot more typing though. And as for being color blind, I received a lot of flak for putting too much color in business applications so grays are all they get now.
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
But I hate all generalisations!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
All generalizations are wrong; including this one.
"You'd have to be a floating database guru clad in a white toga and ghandi level of sereneness to fix this goddamn clusterfuck.", BruceN[ ^]
|
|
|
|
|
I'd give my right arm to be ambidextrous!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: and believe that 50 controls to the square inch is a good average
Oi what s wrong, oh wait you said average, thats Ok then.
Battleshit grey, the only way to design a UI.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Personally, I don't use visual designers at all - they just stick loads of margin and other crap in. Not done any Xamarin, but does it give you a visual indication of what your XAML looks like when rendered?
Regards,
Rob Philpott.
|
|
|
|
|
You actually got Xamrin Forms installed & working? See my post in Mobile[^].
I just got started and I'm sick of it already.
BTW, what book are you referring to?
If it's not broken, fix it until it is
|
|
|
|
|
|
I have it on my iPad, but it's an early version. Thanks for the linke. I'll download the PDF and see if it's changed.
If it's not broken, fix it until it is
|
|
|
|
|
Yes - it took a while, but most of that was swearing at emulators.
I've got it running on Windows aps (8.1 in theory), my Android tablet and the Android emulator (though that's gawd awful slow).
It's a good framework, I think - difficult to tell, I hardly know it - and it has a huge potential if they develop it a bit. One app to write in C# and you get Windows, Windows Phone, Android and iOS? That could work to save WP from the dumping ground it seems headed for.
But it needs a designer for that.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Use the Visual Studio emulator.
The Android SDK Emulator are.. horrendous!
|
|
|
|
|
OriginalGriff wrote: but surely MS can rework the WPF designer for the job?
MS has never been able to figure out how to handle all the different resolutions and aspect ratios of screens, so no, I don't think they'll try very hard to fix this. Their position has pretty much always been to either let a layout manager do the work, or to have you write code to position the controls where you want them on the different form factors and resolutions you choose to support. Seems Xamarin forms took that same attitude and ran with it.
Thwarting WinForms to allow designer to be used to make multiple layouts and allow switching between them at runtime was interesting code to write. I can see why nobody has wanted to do it.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
If a frog leaps off a cliff, is he trying to Kermit suicide?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
