text:
Shopping Cart
My Cart -
Items 101 to 150 of 569 total
Built by you for a better tomorrow
Jaditoner is the exclusive online store distributing aftermarket printing supplies that are manufactured by Jadi Imaging Technologies, an independent toner manufacturer in Malaysia since 1993. A public-listed company in the Kuala Lumpur Stock Exchange ('KLSE'), Jadi Imaging Technologies has always pride itself with its research and development capabilities and global distribution network. From developing patented bio-based chemical toner derived of palm oil to being the only toner manufacturer to produce styrene acrylic toner resin for its own consumption, Jadi Imaging Technologies provides consistent quality toner for your convenience while preserving the environment for your future generations by reducing and recycling chemical waste.
Making your lives easy when buying printing supplies
Find branded and premium bulk toner and toner cartridges for use in a wide range of laser printers, photocopiers, facsimile machines and multi-function office equipment. Print at ease by saving 40%-70% as compared to buying OEM or genuine printing supplies. Guaranteed to fulfill your printing needs including after-sales technical support. Rest easy as our products meet specifications in the performance reports prior to commercialization. Bulk orders are accepted.
Disclaimer: All brand names and trademarks are the properties of their respective owners and are referred to here for descriptive purposes only.
The offers in this website are for end users, resellers, retailers and wholesalers only: All prices listed are net and exclude VAT as well as shipping & handling costs.
© 2017 of Jaditoner.com. All Rights Reserved. A B2B E-Commerce Platform of Jadi Imaging Technologies Sdn Bhd


text:
Micromax Mobile Motihari Service Center Address – telephone number, fax number, email address and website is listed here with the Micromax Mobile customer care number, toll free helpline number, customer support number, customer service center.
If are a Micromax mobile phones user, and you are looking Micromax Authorized Mobile Service Center in Motihari or Micromax Mobiles Repair Center in Motihari region; so, here you can get your nearest Micromax Mobile Service Center Address and other contact information in Motihari and nearby areas.
If you are facing any technical problem and issues with your own Micromax devices, you can contact to Micromax Mobile Motihari Service Center for repairing Micromax A1, Micromax Canvas Nitro, Micromax Bolt, Micromax Doodle, Micromax FIRE, Micromax Win, Micromax Turbo, Micromax Gold, Micromax Unite, Micromax Knight, XL, Micromax Canvas HD, Micromax Funbook, Micromax Canvas Tab, Micromax Tablet and other Micromax Smart phones and feature phones with Data Cards.
Micromax Mobile Motihari Service Center Contact Information
Here you can find the full contact details of Micromax Mobile Motihari Service Center for any issues and problems like software updating, warranty, repair, service, accessories, product issues, general support and technical support near you at Motihari and nearby cities.
List Of Micromax Authorized Service Centres in Motihari:
Micromax Mobile Motihari Service Center offer after sales support and services for all Mocromax mobile phones and related products such as Micromax handsets, Micromax smart phones, Micromax Canvas mobile phones.
[su_tabs][su_tab title="Center Details"]
Micromax Service Centers in Motihari, Balua Chowk, Bihar:
- Center Name: Tirupati Traders
- Center Address: Ansari Complex, Shop No. 6, Areraj Road, Balua Chowk, Motihari, East Champaran, Bihar – 845401, India
- Mobile Number: +91- 9801778557
- Center Phone Number: : +91- 9386598941
- Center Email Id: email@example.com
[su_tab title="Customer Care Number"]
Micromax Mobile Motihari Toll Free Phone Number:
[su_tab title="Head Office Address"]
User-Friendly Links of Micromax:
Click here to get customer care office address and phone number
Click here to find corporate headquarters and branch offices
We hope, resolves your queries and issues related to Micromax mobile phones by using above listed contact information, addresses, telephone numbers, and fax numbers, website and email ids. If you are unable to connect with the Micromax mobile Motihari service center, so kindly contact to Micromax customer care phone number from Motihari and other areas. For further details we recommend you to visit the official website of Micromax Mobile.

subset: commoncrawl


text:
The image was chilling: Snowmobile rider Caleb Moore, launched over his handlebars on a backflip gone wrong, rolled down the landing hill with his 450-pound machine somersaulting behind him.
ASPEN, Colo. (AP) ? The image was chilling: Snowmobile rider Caleb Moore, launched over his handlebars on a backflip gone wrong, rolled down the landing hill with his 450-pound machine somersaulting behind him.
Run over by his sled, Moore lay on the snow for several minutes before being helped off the course. As of Wednesday, he was hospitalized in critical condition because of bleeding around his heart and a complication involving his brain.
Moore's was the worst accident at the Winter X Games, which wrapped up Sunday night after four days of competition, but it wasn't the only harrowing moment. The wipeouts included a runaway snowmobile that sent spectators scrambling.
Even the highlights were hardly tame. Snowboarding star Shaun White soared a competition record 24 feet into the air during the superpipe competition, and fellow boarder Elena Hight showed off a difficult trick called a "double alley-oop backside rodeo" that involved a couple of backflips and a 180-degree rotation. It had never been seen in a competition.
All that, plus Moore's crash, has some wondering whether dialing up the difficulty each year improves action sports or has simply made them too dangerous.
"Should we be asking these questions? We absolutely should be," said Dan Lebowitz, the executive director of Sport in Society at Northeastern University, which examines the role of sports to promote healthy development and social responsibility.
The people performing these superhuman feats "really are just human," he said. "How do we maintain safety in that progression when that progression sometimes pushes every envelope to some amazingly extreme point?"
Moore's injuries underscore the dangers at Winter X, which was filled with numerous cover-your-eyes crashes.
Halldor Helgason of Iceland over-rotated on a flip in the snowboard big air competition and had to be taken off on a sled with a concussion. Rose Battersby of New Zealand sustained a lumbar spine fracture in a wipeout during practice before the skiing slopestyle competition, which will be an Olympic sport next winter at the Sochi Games.
Then there was this: Summer X Games motocross champion turned snowmobile newcomer Jackson Strong tumbled off his machine during the best trick competition, the throttle sticking and the sled swerving toward fans as they scurried away. The machine came to a rest when it got tangled in some netting and no one was seriously hurt.
Such a scenario had already crossed the mind of Levi LaVallee, a snowmobiler who captured two gold medals only to be sidelined for the final two competitions after tearing a muscle in his back.
"I've always thought about, 'What happens if the thing tips over and the throttle sticks?'" LaVallee said. "It was good, though, because it showed that X Games has a good setup with the fencing."
Whether action sports are too dangerous is an issue that's been raised before.
When freestyle skier Sarah Burke died in a training accident a little more than a year ago in Park City, Utah, there were questions about the halfpipe. Before that, the sport was examined when snowboarder Kevin Pearce suffered a severe brain injury in a fall in the same pipe as Burke two years earlier. Pearce has recovered and served as an analyst at Winter X.
But in general, the athletes accept the risks and defend their disciplines.
"To lose Sarah was such a blow to this entire industry," said snowboarder Gretchen Bleiler, who didn't compete this year as she recovers from a serious eye injury she suffered in training. "This sport brings so much joy, happiness and balance to my life and that far outweighs what could happen. You can't ever live your life with what could happen."
In a statement, X Games officials said they've paid close attention to safety issues over the event's 18-year history: "We've worked closely with athletes, risk management specialists, sport organizers and event managers to present the best possible experience for athletes and spectators. Further measures are constantly being evaluated."
Athletes say they prepare as best they can by trying out new tricks into foam pits and air bags set up at the bottom of courses. But even all the caution in the world can't prevent the fact that sometimes well-practiced maneuvers can go wrong in the air.
"You don't want to live your life in fear because of a situation," LaVallee said. "Look, I'm driving down the road right now and the worst-case scenario is a car could swerve over into my lane and run over me ? there it is, end of the road.
"That's kind of the same thing we think when we're competing. Hopefully, the preparation and countless hours of training and practicing will prevent the worst-case scenario from happening."
Tucker Hibbert ? the Shaun White of snowmobiling after winning his sixth straight SnoCross title ? just hopes casual fans understand that what they see on television is not true snowmobiling.
"You're seeing the most extreme side of what we do," Hibbert said. "That's a lot different than what the average person does on a snowmobile."
Hibbert doesn't participate in events such as best trick because, "I just wasn't born with those skills. I sit back and watch those guys, enjoy what they do."
He paused.
"You just hate to see anyone crash, anyone get hurt," Hibbert said.
Moore was in the middle of an impressive run in the freestyle event when he caught the top of the hill that was serving as a landing area. He initially walked away with help and went to a hospital with a concussion.
Moore later developed bleeding around his heart and had surgery. His family said that Moore, of Krum, Texas, also had a complication involving his brain.
Colten Moore, Caleb's younger brother and defending champion in the event, separated his pelvis in a crash later that same night.
LaVallee is no stranger to horrific wipeouts.
While training for the "Red Bull: New Year. No Limits" daredevil series two years ago in Southern California, LaVallee lost control of his snowmobile high in the air and landed violently on his side, bouncing down the landing ramp. He broke ribs, cracked his pelvis, collapsed one lung and punctured the other.
But he returned the next year and jumped a record 412 feet, 6 inches.
"We're passionate about the sport that we're in," LaVallee said.
"Anyone who competes has that drive to succeed, to go bigger than the next person or be the first one to do it."
The mentality is similar throughout action sports, even if the bar keeps getting raised.
"There are going to be benchmarks set and people trying to exceed that benchmark," Lebowitz said. "That's just the essence of our society and our social culture."


text:
Rik Hemsley: XAML versus Qt
An article on MSDN previewing XAML, a not-so-new idea by Microsoft, prompted me to try implementing the given example using Qt instead. It also prompted me to be a little scornful -- but don't let that fool you -- I'm rather pleased to see the company continuing to make life easier for us developers. Check out my article on how to implement Microsoft's example, using existing technology.
OK, own up....
Who else here rated the MSDN article at 1?
By Paul at Thu, 2004/03/25 - 6:00am
Re: OK, own up....
No - let 'em work it out for themselves.
By Guest at Wed, 2004/03/31 - 6:00am
Qt can even support no-compilation
By George Staikos at Thu, 2004/03/25 - 6:00am
Re: Qt can even support no-compilation
I enjoyed that KaXUL presentation, very funny, cheers.
By Paul at Thu, 2004/03/25 - 6:00am
Re: Qt can even support no-compilation
KaXUL looks promising...
The main thing is that XAML is really a Microsoft version:
Like KaXUL, it is expected that XAML will be translated into CLR code.
Obviously, comparing XAML with Qt is non-sense,
Obviously anyone could create that XAML example,
The big issue here is that W3C is still bogging SVG
So, basically it's like comparing some sort of Advanced .ui with XAML.
Are we getting any complete XUL/SVG renderer in Konqueror any time soon,
Currently, KSVG is far behind ASV3/ASV6. =(
Basically, the point is to have the full feature sets before Microsoft
Hopefully, the future looks promising...
By fprog26 at Sat, 2004/03/27 - 6:00am
Re: Qt can even support no-compilation
Yes I saw that, and downloaded the Nove Hrady presentation. It wasn't exactly Earth shattering, but it was certainly extremely interesting.
Although I don't see it being used for the things that Microsoft seem to be hyping it for (what are they hyping it for?), it should be interesting for form design (Kexi, office tools?) and various other exciting things I can't think of right now.
Talking efficiency
I haven't had anything to do with MS since I walked away from their sad excuse for software in the mid 90s. Back then I suspected that they actually added complexity to their coding requirements as a means of raising the barrier of entry for competition. Of course with Gates saying "everything is an object" and evidence I've been seeing for years indicating encapsulation and reuse are things they may discover at some later date it's possible there is another explanation.
The thing that is really fascinating here to me is the fundamental aspect of programmer efficiency. I remember at the advent of C++ the big point that was being made was that you could do "more in a line of code" and thus reduce the number of lines of code to do a task, producing more results from a programmer who is going to produce x lines of code in a day.
So if this example is effectively the same, as it appears to be, then using Qt not only provides cross platform benefits (which was and still should be the holy grail in programming) and a lesser level of frustration, but it is hugely more efficient. I expected it to be more efficient, but this example is remarkable... 60 lines compared to 200 is a savings of 70% and well worth while for the MS example. 11 lines compared to 60 lines is a savings of 81.67% over the XAML example and 94.5% over the raw code example!
That would seem to indicate that in the type of work done in the example a developer would be half way through his sixth dialog with the same number of lines of code as the XAML developer used to finish his first. Given that there is more than just coding here it is likely less efficient, but should still realize a result for that task of being at least twice as efficient. That's remarkable!
I continue to think that the MS advantage is held in place by a thread (held by bullies) and that there is a good reason they fear real competetition. How long can the emperor have no clothes?
By Eric Laffoon at Thu, 2004/03/25 - 6:00am
Except that Qt isn't native on the Mac
Be careful when making claims. Qt/Mac is a step up from having to run X11 to get the app, but it doesn't use native interface elements, it uses it's own cheesy implementation of the Aqua UI primitives. It looks quite ugly in some cases, especially in Panther, where the old-fashioned tabs look out of place. TrollTech really needs to do better.
By Frodo at Thu, 2004/03/25 - 6:00am
Re: Except that Qt isn't native on the Mac
I can assure to you that Qt _is_ native to the Mac: in fact, it uses the Appearance Manager to draw widgets just like Carbon and Cocoa do. The code is fully open source and in qt/styles/qmacintoshstyle.[cpp/h].
Now, there are a few bugs with the current implementation, especially in panther, but they will be fixed. Many of similar off-by-one bugs existed in early versions of Carbon on OSX, especially before MacOSX 10.1.5.
By anon at Thu, 2004/03/25 - 6:00am
Re: Except that Qt isn't native on the Mac
The main problem is that the Mac has a much more advanced GUI system then you'd find on any other platform, thus making emulation very difficult. I wonder if Trolltech should try a wrapper-based approach to Qt/Mac. This is already done with QMenuBar, and it probably could be done to the rest of the widgets as well. I believe this is how Java on the Mac works as well. wxWidgets definitely works this way.
Of course, this might mean losing very obscure functionality, like painting arbitrarily on a QPushButton, but for 99% of the use cases, the benefits of wrapping the native widgets would outweigh this loss. Maybe Qt could fall back to an emulated widget if someone performs such an obscure operation. If I wasn't so busy I might actually try implementing this, as it sounds like a lot of fun (if a lot of work).
In addition to this, the Mac supports advanced widgets, like the preferences dialog stuff. It would be nice if there were a way to take advantage of these widgets in a Qt/Mac app. Years ago, this kind of widget reuse just wasn't seen, but nowadays with KDE and Mac, there are lots of advanced widgets available, and "plain Qt" apps definitely stick out by not using them. We're entering the next generation of desktops, and being a native app is more than just using primitive widgets these days. Trolltech's got some work ahead.
By Justin Karneges at Thu, 2004/03/25 - 6:00am
Re: Except that Qt isn't native on the Mac
> I wonder if Trolltech should try a wrapper-based approach to Qt/Mac. This is already done with QMenuBar, and it probably could be done to the rest of the widgets as well.
This is exactly would Trolltech did with Mac-Qt 3.3.
By Olaf Jan Schmidt at Thu, 2004/03/25 - 6:00am
You GOT to be kidding me!!
XAML has the ease of use of XML/HTML, everyone can write a GUI on XAML with minimal training! That was the point of it!
Please people, be objective for once, that "XAML vs Qt" article is a joke. The author obviously doesn't get what XAML is and what its goals/advantages are in the first place.
By Mambo-Jumbo at Thu, 2004/03/25 - 6:00am
Re: You GOT to be kidding me!!
The author, I believe, does 'get' what XAML is. XAML is _not_ a system for allowing people to write GUIs without recourse to a 'real' programming language. Even if you were to try and write your application's logic entirely in the XAML dialect, you would find yourself needing a similar depth of understanding to the person using a 'real' language; you would also be stumped as soon as you tried to do anything non-trivial.
Also on the subject of programming, who stipulated that you must write your app in C++? Write it in Python if you wish; then you get to forget about the nasty C++ compiler and debugger.
I would also say that anyone can write a GUI with Qt, with minimal training, if they use Qt designer, as I did. What exactly will be the difference between XAML with an interface designer and Qt with an interface designer? Not much, I would say.
By Rik Hemsley at Thu, 2004/03/25 - 6:00am
Re: You GOT to be kidding me!!
Ugh. Manually doing this stuff in XML doesn't make much sense. XML isn't a very expressive language *at all*. Why do you think XSLT is such a nightmare ugly hack? Give my PyQt any day!
By Rayiner Hashem at Thu, 2004/03/25 - 6:00am
Re: You GOT to be kidding me!!
I second that. I made a GUI app in PyQT in one month, language and object concepts learning included. It's not extremely efficient, it's probably ugly in many senses but it does what I want. I can't expect XAML to be any simpler or faster to develop.
Best regards,
By Richard Van Den Boom at Thu, 2004/03/25 - 6:00am
Re: You GOT to be kidding me!!
You are both correct and incorrect. True, with XAML anyone can write a GUI with minimal training. But that GUI will be just a GUI. Nothing more. Without code behind it, it will be merely buttons and widgets that do nothing but look pretty. I can do the same thing with Qt Designer. Heck, I don't even need Designer, I can write my own ui file knowing only XML!
While XAML may have a few "featurettes" that Qt does not have, Qt gives you a complete easy-to-use development environment. Even if you don't know C++, you can still create the GUI. So while XAML gives you a screwdriver, Qt gives you a screwdriver, wrench, hammer and saw.
By David Johnson at Thu, 2004/03/25 - 6:00am
Re: You GOT to be kidding me!!
"True, with XAML anyone can write a GUI with minimal training. But that GUI will be just a GUI. Nothing more. Without code behind it, it will be merely buttons and widgets that do nothing but look pretty."
That's what I thought. It is even more pointless than I first imagined then. Are Microsoft actually selling this crap to people?
What I don't understand is why the MSDN article is showing you the XAML code and how to write it, because you're obviously going to need an IDE for this to really work for you, so it should all be transparent really. We've already got this in Qt Designer, and it produces XML, so I just cannot comprehend the hype some people are attributing to this thing.
This was useful, if only to ram home to me how totally pointless XAML is.
Re: You GOT to be kidding me!!
Oh, please - neither of you have the first clue what XAML actually does, and the same (sadly) goes for the author of this article. I really don't like Microsoft or its products, but even having said that I have to admit their implementation of XAML is damn clever.
For your reference, the XAML code is designed to lay out GUI objects. You have this much correct - you can put in tabs, buttons, menu items, etc. All things that XML describes very well.
However, that XAML can then have scripts added to it either in a compiled language (such as C#) or a script language such as JScript. One XAML file can contain a complete application written in VBScript and XAML: both very, very easy (if somewhat verbose and slow) languages. Comparing it to C++ is very stretched, and not accurate - XAML allows you to /fully/ separate design from the code driving it (a place that Qt Designer is rapidly approaching, as opposed to the 95% separation we have now), which means developers can be beavering away in Visual Studio with their C# whilst the designers are pointing and clicking to make the GUI look nice.
As far as I'm concerned, having the GUI defined in XAML and the code written in C# makes life much easier for the Mono developers, so everyone's a winner.
Honestly: did you really think MS made a technology that did nothing but display a fancy GUI?
By anon at Thu, 2004/04/01 - 6:00am
Re: You GOT to be kidding me!!
"However, that XAML can then have scripts added to it either in a compiled language (such as C#) or a script language such as JScript. One XAML file can contain a complete application written in VBScript and XAML: both very, very easy (if somewhat verbose and slow) languages. Comparing it to C++ is very stretched, and not accurate - XAML allows you to /fully/ separate design from the code driving it (a place that Qt Designer is rapidly approaching, as opposed to the 95% separation we have now), which means developers can be beavering away in Visual Studio with their C# whilst the designers are pointing and clicking to make the GUI look nice."
Yes I did know that, and it is still rather pointless. It may be of use to Windows developers, but not to others - that was the point of the article.
"Honestly: did you really think MS made a technology that did nothing but display a fancy GUI?"
Yes, and they have.
By David at Sat, 2004/04/03 - 6:00am
Re: You GOT to be kidding me!!
I got to go with Anon on this one. As much as I love Qt and usually hate microsoft tools I got to admitt that XAML is a good idea (although not completly new) and that it is not possible to compare it to Qt.
One point that I don't think anybody has mentioned yet, is that XAML allows you to use the same code for web pages as for applications. This is pretty cool in a way.
However I am one of those who think that one should not blur the distinction between the web and desktop applications like Microsoft is starting to do.
They should be treated separatly. In this respect I am not sure if XAML will be such a good idea. It might end up totally webifying all Windows applications.
I can also see that something similar should be possible to achieve with Qt without to much modification. We allready got the XML definition for the GUI. One only needs to expand it so that it can be understood by a web browser.
Lastly I think something similar to this is already possible with Java.
By Erik Engheim at Thu, 2004/04/01 - 6:00am
Re: You GOT to be kidding me!!
"One point that I don't think anybody has mentioned yet, is that XAML allows you to use the same code for web pages as for applications. This is pretty cool in a way. "
Where do you think this is heading?
By David at Sat, 2004/04/03 - 6:00am
Re: You GOT to be kidding me!!
""One point that I don't think anybody has mentioned yet, is that XAML allows you to use the same code for web pages as for applications. This is pretty cool in a way. "
Where do you think this is heading?"
Into further webifying of the windows desktop. The distinction between web applications and desktop applications is going to be blured.
Perhaps the whole windows OS will eventually be a mixture of web services running locally and remotly. For instance that when you run regular apps like MS word, part of the functionality of the program will be provided by web services or something.
I don't like this development, but what do you think?
By Erik Engheim at Sun, 2004/04/04 - 6:00am
Re: You GOT to be kidding me!!
"XAML has the ease of use of XML/HTML, everyone can write a GUI on XAML with minimal training!"
If everybody write XAML program as the do with HTML pages then I don't want to maintain this program :)
99% of the HTML web site don't use (X)HTML as they will do ;)
By Shift at Thu, 2004/03/25 - 6:00am
Re: You GOT to be kidding me!!
> XAML has the ease of use of XML/HTML, everyone can write a GUI on XAML with minimal training! That was the point of it!
This is easier than drawing it in Designer and getting the XML generated? Irrational!
> Qt is a C++ toolkit and no matter how simple it is, it is still a C++ toolkit and the programmer will have to know how to use the language, compilers, debuggers and all things that come with it.
Grab a copy of Kommander. You can build and run dialogs that assemble text to make strings, call DCOP or run applications. You can also use the scripting language of your choice as well as control the CVS version with DCOP. All of this in a non complied dialog based application with no C++... and you still get to draw the interface.
I think that beats what you're selling for ease of use for the common person.
By Eric Laffoon at Fri, 2004/03/26 - 6:00am
Benefits of XML approach to coding
The discussion concerning the inadvisability of XML over C++ (or Qt or Java or C#, et al) misses some fairly major points. When you're working with Algol based languages or frameworks, in general what you are doing is creating an imperative description of process -- call this function, pass this result to this store, change the state of this entity -- in a very linear fashion.
Algol languages emphasis DOing things. and typically the aggregation capabilities that are characteristics of GUI-centric languages such as Visual Basic, when converted into this type of code, can often become very cryptic, heavily dependent upon object APIs and tied to one host environment. I believe that it is this reason, more than bad coding practices directly, that is responsible for the plethora of truly bad VB apps.
XML based coding on the other hand, tends to BEing, rather than doing. The aggregation and encapsulation that is often the most complex part of maintaining state within C++ gets implemented for free, connectivity between components is defined more in terms of passing agreed upon XML structures through URL linking, and the API for interaction becomes a common one, namely the Document Object Model.
The significance of this should be obvious, though its usually not. I write an XML structure, and so long as I'm consistent within the language I've defined, it does not matter which platform I'm running on. Moreover, the code can be ported in and compiled into whatever the native platform formats are on the fly -- rather than passing the binaries (or even a low level IL like Java) you just pass the description of the environment.
It's not a perfect approach, of course -- there are places where XML is not appropriate. However, as someone who's been working with XML related programming issues for the last eight years, I've found that XML as a language descriptor is in fact far more powerful than the number of lines it saves a programmer would indicate. It can be generated dynamically, it can incorporate multiple outlier streams of content transparently, and can often hide the nasty issues of dealing with different data representations by using an XML bridge, such as that from a SQL database or LDAP directory.
If you use XML like C++, you will of course receive none of these benefits, because the underlying conceptual model is completely different (and even somewhat antagonistic).I see XML as being post-OOP, requiring a different paradigm for handling well, and capable of eliminating much of what currently exists in the procedural world.
-- Kurt Cagle
By Kurt Cagle at Wed, 2004/03/31 - 6:00am
Re: Benefits of XML approach to coding
What are the prons and cons of both XML and Compound files as a data storage?
By Anshul Bajpai at Wed, 2007/01/31 - 6:00am
What the hell is the point in XAML? Surely you can take .ui files, or XUL and with some work accomplish exactly the same thing. It doesn't mean a damn thing.
Besides, if your application is too complex for XAML, I guarantee you that it will quickly become a terrible nightmare very quickly. You will defintely have to use some sort of IDE for this, and since you will be doing that anyway, what's the point? Whoever wrote the MSDN article has obviously never thought about that. Dude, that's what programming languages are for. This is yet another absolutely pointless idea (trying to takeover the Internet?) from the boys in Redmond that is dangerous in the wrong hands. I can see some truly awful project failures due to some people saying "Oh, we can just use XAML". It also gives fuel to the people who say that XML is pointless.
Re: Pointless
I have no experience with XAML but I have used XUL to create a non-trivial application. That application turned out to be a failure in many ways, but it did enable me to realise that XUL is a flawed implementation of an otherwise sound idea.
Some people have compared XUL/XAML to Qt but they are not quite the same. I think the difference is more that the two technonogies foster different methodologies. In a Qt or VB type designer you place a widget and set its properties; likewise with XUL.
The end result is somehow different though. The XUL developer creates more widgets since its so easy to do and since it keeps the UI code clean. The XUL developer may also create smart widgets that have environmental awareness so that they change their behaviour dependent upon the widgets around them. This is likely possible in Qt, but it's easier in an XML UI language (XPath dependent methods or layouts, etc) and enables richer functionality to be expressed declarativey, again allowing the main UI code to be kept cleaner.
So the difference is more that the XML UI developer is more acutely aware of the mess he is making to his UI file, and has better tools to create widgets that allow him to express more of that functionality in a purely declarative manner. The disadvantage of this is that re-usable widgets take longer to code, but the advantage is that non-programmers that can understand declarative markup languages can create richer UIs before needing a programmer to take over, since the creation of richer widgets by programmers is more encouraged in the first place.
Just my tupence.
By Dominic Chambers at Fri, 2004/03/26 - 6:00am
Re: Pointless
We've seen this before. Creative WEB designers using Java applets for all kinds of UI enhancements. Applets that came with the designer tools. Big disadvantage was the limitations of HTML and heavyness of Java VM. So we have Flash these days. But interaction between make up language and plugin objects is still poor.
By koos at Fri, 2004/03/26 - 6:00am
Qt to the rescue!
I find it amusing to see people constantly reinventing the wheel. Rik's article is just one example. At work we're porting an old Motif application to Windows. One person is doing an evaluation of porting *just* the GUI using a motif-to-win32 conversion tool. He's spent two weeks on it so far, and is still not quite done. Funny thing is that I did the very same porting as an experiment two years ago using Qt Designer. It took me one day at the time.
By David Johnson at Thu, 2004/03/25 - 6:00am
Re: Qt to the rescue!
They're reinventing the wheel for one purpose: a moving target. Whatever is 'the norm' on MS-Windows will be what developers expect when they think of moving to KDE or GNOME. And, of course, KDE and GNOME have just about caught up with what the current MS-Win can do now, so they've gotta move the gaol (or should that be gaol?)
By Guest at Wed, 2004/03/31 - 6:00am
Re: Qt to the rescue!
"gaol" is the old spelling of English "gail".
By Ed at Sat, 2004/04/10 - 5:00am
Re: Qt to the rescue!
They're reinventing the wheel for one purpose: a moving target. Whatever is 'the norm' on MS-Windows will be what developers expect when they think of moving to KDE or GNOME. And, of course, KDE and GNOME have just about caught up with what the current MS-Win can do now, so they've gotta move the goal (or should that be gaol?)
By Guest at Wed, 2004/03/31 - 6:00am
I thought the point of XAML was for microsoft to be able to replace HTML with something which describes and renders richer applications - applications which are more akin to a typical GUI app than a web page with a form embedded in it.
Obviously, the key word here is "renders". HTML web browsers, as we know them, won't render XAML applications, but isn't XAML intricately bound up with .NET? I read an article about this a few months back (sorry, forgotten the link) and I concluded that IE6 is the last visable, seperate browser in windows because future versions of windows will have this new superbrowser/.NET capability built in.
I assume the goal is to be able to download an interface description in which the screen controls are bound to server-side event handlers in the same way ASP.NET works now, the difference being that the client is running .NET and therefore is able to render a rich GUI app rather than just an (X)HTML web page.
Maybe QT/KDE could be similarly extended to make distributable web apps with a rich interface possible on Linux. It'll happen eventually, anyway. The Mono crowd, led by Microsoft-admirerer-in-chief Miguel d'incaza, are eagerly implementing their own version of XAML. A nice challenge for Mr. Hemsley et al, I would have thought...
By Ez at Fri, 2004/03/26 - 6:00am
Isn't this what libGlade does for GTK? From the webpage:
"Whereas GLADE's output routines create C source code that must be compiled, libglade builds the interface from an XML file (GLADE's save format) at runtime. This can allow modifying the user interface without recompiling."
Read it here: http://www.daa.com.au/~james/software/libglade/
While I'm pretty sure QT doesn't provide that out of the box, obviously we have that power--otherwise Designer wouldn't be able to load it's own data files! And they're an XML format, so there you go. All we have to do to "have the power" as it were, is to refactor Designer's file-loader into a separate library. You know, create like a QWidget subclass called QDesignerUILoader, pass it a QFile pointing to the UI file, and show it. Or something similar, I'm not really a QT developer.
If one of the QT guys would implement this, that would be another bullet point for their widget set. While it takes coders to finish the UI file and make it completely usable, non-coders can take one with the appropriate stuff added and modify it to their heart's content, not unlike having web designers fiddle with templates written in DTML for Zope or Smarty for PHP.
By THIBOLOT at Fri, 2004/03/26 - 6:00am
Re: Glade?
You mean QWidgetFactory? Qt's had this for years. :)
By Justin Karneges at Fri, 2004/03/26 - 6:00am
Re: Glade?
Oh. Thanks... I'm glad we had this talk. :)
Were you going to tell them?
By THIBOLOT at Fri, 2004/03/26 - 6:00am
Missing the point, really missing the point...
Sorry, but I think that Rik's article completely misses the point, and dramatically underestimates the impact of XAML/Avalon in the desktop field.
The power of XAML is that it allows to create the general content of GUIs, without too much care for its representation (as it happens when you write XHTML). The final rendering is performed by the underlying desktop environment, that applies transformations (a-la XLS) and styles (a-la CSS) to ensure that the GUI always resembles the current human interface policies of the desktop environment (that may change over time). [NOTE: the MSDN article reported by Rik doesn't seem to stress this point]
Regarding actual application logic: it can be embedded in XAML pages, or put in external files, and it could be written using _any_ language supported by the .NET framework (C#, Visual Basic, Java, Javascript, Python...).
It basically means that XAML/Avalon applications are *very* easy to write (using your Favourite Language(TM)), can be approached by web developers (who often have strong GUI expertise), and have the potential of a *very* long life cycle: they can automatically adapt to the changes of the underlying desktop policies and programming environment, since both representation and logic are written using high level languages.
As of today, there's *nothing* in the free software world that resembles XAML/Avalon. The only common point is the XML usage - but sharing an underlying meta-format really doesn't give you much: the important part is *how* this format is used. XAML/Avalon use it as it was meant to be used (a way to store content, without representation), while the free software world uses it as a simple storage medium that also carries representation information.
If big corporations (and developers in general) choose XAML/Avalon to write their applications now, they won't be able to port them on the free software world, and will stick with Microsoft operating systems. It will, of course, force users to stick with Microsoft OSs as well. So we really need a free (and possibly compatible) XAML/Avalon alternative, as soon as possible
GNOMErs seem to have taken this issue more seriously. See, for example, this interesting article: "What next for GNOME's user interface?" - http://usefulinc.com/edd/blog/contents/2004/03/03-gnomeui/read
By Anonymous coward at Fri, 2004/03/26 - 6:00am
Re: Missing the point, really missing the point...
Actually we don't know if this will work in practice. Look at HTML it keeps going through some pretty major because what it needs to do changes so much over time that the older way things where done just don't work very well anymore. It is true that old webpages still render in modern browsers but the pages do look old and stuff done now will look just as bad a few years from now. Simple things like Forms are being redone as XForms which are far more powerful and if you want to use those features you will have to change your html. That is true of many others areas also. Your apps don't magically upgrade like you seem to be suggesting since new concepts need to be explained to the system so that it knows that they apply to your app.
Overall the best bet it is seperate the front end from the back end of the app so that it is easier to replace the gui since overall in computing history it seems that the guis need replacing a lot more often then the front ends do.
By Kosh at Fri, 2004/03/26 - 6:00am
Re: Missing the point, really missing the point...
> Actually we don't know if this will work in practice. Look at HTML it keeps
It happens because HTML is an inbreed between content and representation.
Things do change when using XML or XHTML: they have been created just to store *content*. The final representation is delegated to other systems (CSS or XLST).
Have a look at an XHTML page rendered without CSS support: it looks as ugly as the web pages written 10 years ago. But once you apply CSS rendering... The magik happens!
> That is true of many others areas also. Your apps don't magically upgrade like
That's the whole point of XAML/Avalon: you just create the "content" of the GUI, the underlying desktop environment will know and apply the "new concepts" to the final representation. It does definitely ease integrating old apps with new (and revised) system GUIs.
> Overall the best bet it is seperate the front end from the back end of the app
Yes, and XAML/Avalon do allow it: it's always possible to write pure code that interfaces to your GUI, choosing whatever language you want (as long as it works under .NET).
By Anonymous coward at Fri, 2004/03/26 - 6:00am
Re: Missing the point, really missing the point...
You obviously know far more about this than me, but what you've written seems to bear out my own response, further up this thread. I was a bit too unsure of my facts, when posting, to say outright that Rik's missed the point, but having read your post, I can now say, "I agree". Rik has missed the point on this one.
By Ez at Fri, 2004/03/26 - 6:00am
Re: Missing the point, really missing the point...
"to ensure that the GUI always resembles the current human interface policies of the desktop environment"
This sounds more like wishful thinking to me, unless the 'human interface policies' are flexible like bubble gum themselves or the flexibility of creating GUI's (not their content) using XAML is fundamentally restricted. And many of the XAML GUI examples I saw didn't look usable but hideous. Please refer me to some documentation clearing up how the separation of GUI and content you like to emphasize so much should work.
"If big corporations (and developers in general) choose XAML/Avalon to write their applications now"
Is that already possible? I think the whole development environment and framework for it to be really applicable is by far not usable in production use as of now, and that will only change when Longhorn is officially released (which will be in several years).
By Datschge at Fri, 2004/03/26 - 6:00am
Re: Missing the point, really missing the point...
> This sounds more like wishful thinking to me
Yes, it may be just complete vaporware and/or poorly implemented stuff... But it seems that Microsoft is really working in that field - while the free software world is completely unprepared, and often underestimates XAML/Avalon effects.
> Please refer me to some documentation clearing up how the separation of GUI and
There's no single reference (at least, I haven't found it yet): the plan can be understood by looking at the whole XAML/Longhorn scenario. If there was a clear explanation of Microsoft plans, maybe we wouldn't be discussing whether Rik's article underestimated XAML/Avalon consequences :-)
Some interesting stuff, however, is here: http://longhornblogs.com/
And most of the consequences are quite easy to understand: once you have such a XML-based GUI design system in place, integrated with the whole .NET framework, developers won't have to care e.g. about widget positioning and spacing: CSS-like and/or XLS-like transformations may take care of it, depending on the current theme and/or human interface policies. It may not help in *all* the cases (it's always possible to write bad GUIs and bad applications), but it *does* give an additional value that free software can't offer (yet).
One of the actual examples of how XAML/Avalon could work is given by... XUL (that uses the Mozilla rendering engine, Gecko, to apply CSS-like styles and transformations to XML-defined GUIs).
XAML is something like XUL, but applied to native widgets and themes, with a complete system integration (via the .NET framework) and a broader support for scripting languages (while XUL only supports Javascript, XAML supports all the languages of the .NET framework). In other words: XAML/Avalon are nothing new, but it promises to be very powerful and (as of today) free software competitors simply don't exist. See the Edd Dumbill's article I've pointed out for further details: http://usefulinc.com/edd/blog/contents/2004/03/03-gnomeui/read
> > If big corporations (and developers in general) choose XAML/Avalon to write
Sorry, I was unclear. XAML is not production quality, yet - but corporations and developers may start now their planning abut thecnologies to be used in future projects (and that's the whole point of the articles being published on MSDN: they want to influence these choices).
We can't answer to these articles just by saying "I've done the same with Qt and KDevelop", because it really takes into account one of the points (the RAD issue), and completely misses the long-term maintainability and system integration points.
By Anonymous coward at Fri, 2004/03/26 - 6:00am
XAML is good, but the threat is Avalon
(from the article:) XAML also seems to allow for transformation (e.g. rotation) of widgets. Many systems have provided this facility in the past few decades but as yet I haven't seen it used by any applications. There are some games which use slightly rotated buttons for menus, though, so perhaps game developers will find this feature useful. I'm not sure how you handle resizable layout when you have rotated widgets, though. (end)
XAML is a way of expressing parts of C# classes in XML. That's all. It's compiled into the application and run by the CLR. What most people are seeing of XAML is its application to the Avalon framework. That's what concerns me, most. With the release of Longhorn, Avalon will become the primary gui development toolkit for Windows. It has all the power that you've been gawping over on the Mac, plus a hell of integration work to make it easy to use and develop for.
This is serious, folks. Everything's done with vectors, now. The bitmapped raster ways of the past have gone forever, and in its place is something approximating the capabilities of postscript or pdf. You can do great effects, rotation, shadows, transparency, scaling... and it'll all be hardware accelerated because Microsoft have the power to demand it.
On UNIX platforms we're stuck with bitmaps. You can't put even put a button in your average canvas. Nothing's scalable and nothing's fun to develop awesome user interfaces in. If the Avalon threat goes unanswered we'll be back to the bad old days when you know you're running a unix app because of how crappy it looks. QT must evolve to take advantage of the new features available on Avalon and Quartz, and in doing so it must either bring X11 up to scratch or find something better. The clock is ticking. Everyone has working code but us.
By Benjamin. at Fri, 2004/03/26 - 6:00am
Re: XAML is good, but the threat is Avalon
"You can do great effects, rotation, shadows, transparency, scaling..."
That's just eye candy. While you want an interface to look good, you don't want it to look like a Hollywood special effects bonanza. That stuff does nothing to improve the usability of the interface. Hint: the usability improvements of Aqua over OS9 had nothing to do with its transparencies and animations. Those were just to get the media types to pay attention.
If the Avalon threat goes unanswered we'll be back to the bad old days when you know you're running a unix app because of how crappy it looks.
Unix looks crappy? Then you aren't running KDE. Plastik looks better than anything Microsoft offers, and you get to use real color schemes as well. Baghira simply rocks. You can't to anything like this in Windows.
By David Johnson at Fri, 2004/03/26 - 6:00am
Re: XAML is good, but the threat is Avalon
Bahh. Eye candy??
I need scaling and rotation on every-day widgets for my real-world safety-related and well-established work-related problem area. If you can't scale interactive diagrams that describe the state of your power station you don't get out of the starting blocks. Don't try and tell me that it's just eye-candy.
Then go and look at Max OSX. A few minutes of using that and you'll be saying "I wish my user interface was as engaging as this for average users". While low-eyecandy GUIs are good and important in many areas, you can't say that having a toolkit that simply can't do it is a competitive advantage.
Unix used to look crappy? Yes. Five years ago you always knew whether you were running a UNIX app. If we're still where we are now in five years (assuming the longhorn ship date slips a few...) you'll again know you're running a UNIX app. There are places where the toolkits just have to be able to keep up.
Take a look at this video: http://msdn.microsoft.com/msdntv/episode.aspx?xml=episodes/en/20031028LH...
For those without broadband, the video shows Avalon with a video playing in the background with transparent buttons and text boxes sitting on-top, rotated, and scaled to a size appropriate for the monitor. This is done by embedding the widgets (and some in-line text) in a text-flow layout, which in turn sits within a transform layout, which sits alongside the video playing in the same position within a canvas.
QT needs to adapt to be able to put everything in a canvas. There can't be any concept of a canvas item that is different from a regular widget. That, at least, needs to be done before Longhorn's release. If we ignore what is possible on other platforms we limit ourselves in where we can go with what we have.
By Benjamin. at Sat, 2004/03/27 - 6:00am
Re: XAML is good, but the threat is Avalon
Eh? Being able to scale an interactive diagram has nothing to do with the widget set used for standard applications. I would be very surprised if you could build such an interface with real widgets and have it practically usable - you'd be much better off writing a custom widget, just like you would now. These kind of special purpose diagramming applications have been built for years, without any of the things that Microsoft is proposing.
I'm not suggesting that some of these things aren't nice, but if you think they are absolutely necessary right now (and for mission-critical applications no less!) then I think you've been letting Microsoft whisper into your ear too long.
By Paul Eggleton at Sat, 2004/03/27 - 6:00am
Re: XAML is good, but the threat is Avalon
> When QT/Kde can do that in about as many lines of code we'll be back on track.
Hmm.. He is obviously trying to turn some peoples' anger up.
By anonymous anonymous at Sun, 2004/03/28 - 6:00am
Re: XAML is good, but the threat is Avalon
"Unix looks crappy?"
"Plastik looks better than anything Microsoft offers,"
That's nonsense. Windows default style looks as good as Plastik, wether it is Luna, Win2000 Style oder 2003-Style. The Windows gimmicks (eye candy) work usually better because of higher graphics performance.
By noname at Sat, 2004/03/27 - 6:00am
Re: XAML is good, but the threat is Avalon
"Hint: the usability improvements of Aqua over OS9 had nothing to do with its transparencies and animations. Those were just to get the media types to pay attention."
I beg to differ. All the eye candy in Aqua is not as useless as people make it.
1.Icons: Large icons are easier to hit and click than small ones. The big icons in Aqua makes this possible (that they look good is a nice side effect). The realistic look of the icons makes them easier and faster to identify. In the old days the icons looked so bad often that you couldn't really make out what they represented or tell them apart.
That cartoon look is better than realistic ones is just bullshit. OS 9 use cartoon look on icons and I am much slower at identifying icons in OS 9 than OS X.
2.Valuable visual cues: When you minimize windows you clearly see where the window goes. This should help newbies figuring out where their windows went. It even helps power users sometimes. For instance when you close a palette window in Word for OS X its window is sucked into the button that toggles it. Makes it very easy to refind the button to redisplay it.
3.The vector graphics allows powerfull switching between windows alla Expose. Expose is really awsome. It is one of the great user interface inventions in many years.
4.The scaling effect in the dock allows you to more easily identify the minimized windows.
There are lots of other examples (like toolbars). The point is however that most of this eye candy serves a purpose. Often it gives valuable visual cues to the user about the effects of the operation he performed.
In fact I would argue that XP has useless eye candy and OS X does not. In XP the webish user interfaces often have bitmaps and such to pretty up dialogs. However the bitmaps can't be clicked, display no information or serve any other function than decor. In Aqua the eyecandy at least serve a purpose if not for all users.
By Erik Engheim at Thu, 2004/04/01 - 6:00am


text:
Check out all kinds of Cute monthly, yearly and weekly calendars in different formats like MS word, Excel, PDFs and images. Print and download Two Month Editable February March 2020 Calendar Template free images from here. We also have One, Two, Three, Four, Six Monthly, Weekly and yearly calendar template designs which can be printed through this site. Contact Us if you have any suggestion, issue or query about this website.
Also check this : January Calendar 2020 Printable
Two Month Editable February March 2020 Calendar Template
If you want to print the calendar of next month, you will need to search the month name and year in the search box. Share these images on various social networking sites within a single click from here.


text:
|Home > Steering Wheels > RMD Steering Wheels > Rally `350` Wheels (3" Dished) > Rally `350` Wheels - Coloured Series > SVI-4152BSUB
|Solution by: totalwebsystems
Login | Register | My Account | Shopping Cart
Due to the Covid-19 virus Rally Design is now open only for mail order sales orders received via our website, email or eBay. Regrettably our trade sales shop is closed. So as to abide by social distancing we are reducing our staff levels & working Monday to Thursday - Closed Friday/Saturday/Sunday. There will inevitably be some delays in progressing orders, however we will try to keep these delays to a minimum. The sooner we overcome this virus the sooner we can return to normal operations, lets all try to help each other. Fortunately we are currently well stocked but some special order products may prove difficult to source. David Elderfield, Managing Director. Last Updated 24/03/2020.
Unit 4 St. Augustine's Business Park, Estuary Way, Swalecliffe, Kent, CT5 2QJ • Tel 01227 792792 • Fax 01227 794888
Vehicle Identification: References to vehicle marques such as Ford, Vauxhall, Westfield, Caterham etc. are for vehicle fitment identification purposes only.
These references must not be used to imply the vehicle manufacturers have been involved in the design of these products nor endorsement of same.
Product Images: The images shown on this website are for illustration purposes only and may not be that of the actual product. If you are unsure please ask.


text:
Men's Sale Spring Suits
Shop for Men's Clearance Spring Wetsuits online! If you have questions in regards to sizing, or would like to speak with someone about selecting the right wetsuit for your climate and intended use, please don't hesitate to give us a call and one of our expert staff will make sure you get the right fit, and functionality for your needs.
Hurley Advantage Plus 2/2 Short Sleeve Chest Zip Wetsuit - 2018
Regular Price: $219.95


text:
Among recent actions by the SEC and FINRA were charges against a hedge fund analyst and two friends for insider trading, and sanctions and fines for one firm for reporting and disclosure failures and another for options reporting failures.
Hedge Fund Analyst, Two Others Charged by SEC for Insider Trading
The SEC charged Matthew Teeple, a hedge fund analyst from San Clemente, Calif., with insider trading, along with two of his friends—a company executive who provided tips and a Denver-based investment professional.
According to the regulator, Teeple got the essential information on July 16, 2008, from David Riley, the chief information officer at Foundry Networks, which was to be acquired by Brocade Communication Systems on July 21 for approximately $3 billion. Armed with nonpublic data, Teeple got the hedge fund advisory firm where he worked to buy up large quantities of Foundry's stock before news of the acquisition went public. The stock gained 32% on the news, and the hedge funds the firm managed saw millions added to their bottom lines.
Teeple is accused of telling, among others, John Johnson, a Denver-based investor with whom he had become friends thanks to an earlier working relationship. Johnson also made illegal trades on Teeple's tip, as did the others Teeple told.
The acquisition took till Dec. 18 to be completed, and Riley slipped Teeple additional inside information on at least two other major announcements before Foundry actually made them—on an April earnings forecast and on a delayed shareholder vote on the acquisition—and Teeple's firm used these as well to make money or avoid losing money, the SEC said.
The SEC, whose investigation is continuing, seeks disgorgement of gains, prejudgment interest and additional financial penalties. The U.S. Attorney's Office for the Southern District of New York has also announced criminal charges against Teeple, Riley and Johnson.
HSBC Securities Fined, Sanctioned by FINRA
HSBC Securities was sanctioned by FINRA and fined $250,000 over numerous issues that included failure to accurately report short sales, incomplete disclosures and failure to retain text messages on BlackBerrys with text functionality.
FINRA found that short sales were reported as long sales because of a failure by the middle office to accurately include short sale indicators on back-office communications. As a result, for four years the firm was reporting short sales as long on their Blue Sheets. In addition, the firm did not deliver prospectuses or offering memoranda that were required for fixed-income transactions; failed to include some investment banking disclosures to research reports because of a breakdown in its automated feeds; and failed to accurately map company identifiers, which added to the disclosure issue. In addition, while the firm had a policy of disabling text messaging on employee BlackBerrys, this was not done on some registered employees' devices and the firm failed to retain all the text messages.
HSBC neither admitted to nor denied the charges.
Scottrade Sanctioned, Fined by FINRA on Options Reporting Failures
Scottrade, Inc. racked up four years' worth of options reporting failures, and as a result was censured by FINRA and fined $125,000. FINRA found that the firm, which neither admitted nor denied the findings, failed to report reportable options positions in standard options to the Securities Industry Automation Corp. (SIAC) large option positions reports (LOPR), and failed to report at least one reportable option position in standard options to the Options Clearing Corp. (OCC) LOPR.
Options were also a problem for accounts under common control or acting-in-concert, the firm failed to report numerous reportable positions in standard options to the SIAC and OCC. Some 8,000 were not reported to the LOPR over an 8-month period, and 9,300 options positions were not reported to the LOPR with the correct in-concert information for over 18 months.
There were additional failures to report options, and FINRA also found that for a period of about three years, the firm did not have an adequate system to supervise options reporting for accounts under common control or acting in-concert. It was worse for the supervisory system that conducted accuracy reviews of the firm's daily LOPR submissions, which FINRA found to be inadequate for more than five years.


text:
New London's parking-ticket arbiter ends career with a parking ticket
New London — You could call it karma.
Reid Burdick, who has had the final say on parking ticket appeals in the city for about 20 years, walked out of his last hearing in City Hall Wednesday and found a ticket on his windshield.
"I guess this is justice for those who had to pay today,'' Burdick said of the $25 ticket for violating the parking limit on Masonic Street.
As of July 1, Burdick will no longer have what he calls "the honor" of volunteering to hear parking disputes. He is being replaced as the emergency management director, a $10,000-a-year position he has held for 26 years, the duties of which include hearing parking ticket appeals.
"When I got this job, I didn't know a thing about what I was supposed to do,'' Burdick said after his final hearing Wednesday. "(Former) City Manager Richard Brown told me to 'Be fair. Be kind to New London residents and businesses. And keep the rest out of my office.'"
Burdick said that is how he has tried to conduct business.
"I'm not Judge Judy. I'm not Judge Joe,'' he said. "You can't yell at me. I don't write the rules. I have nothing in this, one way or the other."
A longtime resident of the city, Burdick is familiar with the names of every street and road, and knows where parking signs and fire hydrants are located, where the curbs are striped for no parking, and where there is resident-only parking.
"I've been running around New London for about 60 years,'' the former city councilor said. "You get used to where all the signs are."
About 100 of the 200 people who appealed their tickets and were scheduled an appeals hearing showed up at City Hall Wednesday. They came with briefcases and folders and 8-by-10 photos. They pulled out their cellphones and scrolled to their evidence. One young woman brought her laptop, spinning it around to show Burdick the image.
He tossed out about $2,000 worth of tickets and told 25 people they had no defense and had to pay. He also had the police department look into the facts surrounding 15 other violations.
He gave a break to those who contested tickets they received during one February snowstorm. The winter parking ban may have been in place too long, he said.
He patiently listened to the reasons violators gave for their innocence — they didn't see the sign; it wasn't snowing yet; the curb wasn't marked; they were only a foot over the line; my daughter was driving the car; the handicapped sticker was in another car.
A city employee who roams the streets looking for violators was among those who disputed a ticket.
"You're kind of in an odd spot here,'' Burdick said to Junel Dulcice, one of the city's two parking enforcement officers, who was fighting a ticket he received last year.
Dulcice said the lot near his house on Huntington Street did not have a sign for restricted parking. Burdick said he would have the police look into the missing sign.
A woman who got a ticket for parking in the fire lane in front of Home Goods said store employees told her to pull up there to load a large item she had purchased.
"My advice to you is not to take motor vehicle advice from people who work at Home Goods,'' he said.
Hans Hess of Old Lyme said he came to New London the week before Christmas to buy a present and parked in a permit-only space. It didn't make sense, he said, to ticket visitors patronizing businesses.
"The whole lot was empty,'' Hess said. "No one was on the street. I was the only person in downtown New London the week before Christmas."
But Burdick pointed out that just a few feet away were spaces designated for free two-hour parking. Hess had to pay.
Everyone had a story. The first woman of the day confessed to the room that she loved her nine children but didn't like eight of them, especially the one that kept getting parking tickets.
Sharon Whitfield, whose ticket for parking in front of a fire hydrant was voided after Burdick read her appeal, wouldn't leave until she had explained herself.
An animated Whitfield said she got out of her car on Gov. Winthrop Boulevard near Huntington Street, left the flashers on, and went to help her daughter and her two kids, who were standing on the corner. She turned around to find an officer writing up a ticket.
"If there was a fire, I would have been out of there before the fire department arrived,'' she said.
Burdick agreed it wasn't right.
"You're sweet,'' she said. "What's your name?"
Among the tickets Burdick asked Officer Wayne Neff to investigate further was given to a man who had been pulled over by police in front of ShopRite, and then was given a ticket for parking in a fire lane.
"They told me to pull over there,'' the man said.
"I think there's more to this one,'' Burdick agreed.
Several times during the hearing, he told disgruntled drivers who complained about the parking to talk to the city's administration.
"If you don't like the parking regulations in the city, you have to see the wizards who run the city, of which I am not,'' he said.
Burdick kept the meeting light, joking with nearly everyone.
He said he has enjoyed meeting people, tossing out a ticket when he could, and forcing repeat offenders to pay up.
"I've always tried to be fair, and I think, even with those who had to pay, we walked away friends,'' he said.
The deputy police chief will replace Burdick as the emergency management director, and Mayor Daryl Justin Finizio said he hopes a local attorney will volunteer to adjudicate parking disputes.
Burdick was philosophical when, after the hearing, he found the ticket on his car.
"I own it. I'll pay it," he said. "I should have known. It's what I would have told anyone."
Stories that may interest you
UPDATED: Local police leaders say Minneapolis incident erodes trust of community; demonstrators 'stand witness'
Police chiefs in Groton, New London and Norwich spoke out about the George Floyd incident as members of the community planned a small "Black Lives Matter" public witness gathering Friday afternoon in New London.
Preston residents offer mixed opinions on proposed school budget
A debate over the proposed $12.2 million school budget dominated a two-hour budget teleconference public hearing Thursday night.
Region's summer camps canceled or modified due to pandemic
With new state safety regulations and the ongoing COVID-19 crisis, private and town-run programs are either shutting down or adapting.
After 'some progress,' Lamont signs off on casino reopenings
Foxwoods Resort Casino and Mohegan Sun, set to open to the public Monday for the first time in 11 weeks, will cater to invited guests during "soft" openings over the weekend.


text: Monday, September 24, 2012 National Robotics Initiative Includes 3 Rehab Projects A collaboration among the National Institutes of Health (NIH) and 3 other federal agencies aims to accelerate the development of the next generation of robotics, called corobotics. These projects include robots that help engineers better design prosthetic legs for patients with amputation, miniature robot pills that help doctors diagnose and treat disease, and microrobots that help researchers make artificial tissues. Along with the National Science Foundation, the National Aeronautics and Space Administration, and the United States Department of Agriculture, NIH will find 6 projects over the next 4 years. The projects are expected to receive $4.4 million in funding. In addition to the below-knee prostheses project, 2 other projects have implications for the physical therapy profession. The goal of Control of Powered Segmented Legs for Humanoids and Rehabilitation Robotics is to uncover the principles behind the biomechanical design and neuromuscular control of human legs in a variety of gaits and to transfer these principles to the design and control of powered leg prostheses and robotic rehabilitation devices. Another proposal, titled Brain Machine Interface Control of a Therapeutic Exoskeleton, plans to combine a human-robot interface with a noninvasive brain-machine to allow the patient to use his or her thoughts to control the movement of the robot to better rehabilitate the upper limb affected by stroke. Comments Hi I'm a PT in MI, I was wondering how can I participate in these projects... Most interested in the workings of the 'brain machine'. Posted by Pragya Jalukar on 10/3/2012 7:09 AM


text:
16-year-old Gabby Douglas was not only heckled for her hair, but also now because people believe she doesn't represent America enough in her attire.
Conservative black radio host, David Webb, suggested that Douglas and her teammates weren't showing enough patriotism by not sporting red, white and blue leotards or draping themselves in American flags after their team's win.
Douglas sported a pink leotard in her historic gold medal placing in the All around. However, it's important to point out she has adorned blue and red before, but still people are attacking the gymnast.
Webb and other conservative commentators see Douglas's choice of pink rather than colors of the American flag, as well as other Olympiads, as a defiant stance against America.
"We've also lost over time that jingoistic feeling," he said. "You know, the National Anthem, we sing it at baseball games. I think the National Anthem should be followed with, "Play ball." It's kind of an American thing. We've lost a little of that, you know, saying The Pledge of Allegiance. And I think that plays over into some of this soft acceptance. You know what? Red, white and blue – wear it. Wave it. Be proud to be an American. It's not a political issue. But they make it a social issue."
Watch Webb's opinion below:


text:
If Samuel Johnson could sarcastically call second marriages the triumph of hope over experience, Americans should view news of Detroit's bankruptcy as the triumph of experience over hope.
The city has been in a tailspin for decades. Bond issuance, state aid, emergency managers, occasional pushes from the political class for union concessions, halfhearted suggestions of selling art assets, a last-minute plea to the White House — every little flight of hope was grounded in Thursday's bankruptcy filing.
Ultimately, Detroit's crushing long-term debt and vast unfunded pension obligations stretched beyond the city's revenue and borrowing ability.
This is not merely a stall for the Motor City — it is more like a breakdown of its transmission, whose repair will be extensive and costly. The city's 700,000 residents will likely see a further erosion in its already decrepit city services — its broken street lights and shuttered fire stations. And its creditors, including city pensioners, will see just pennies on the dollar.
The often dour critics of Blue State spending excess will probably say, "I told you so."
It is true that government at all levels including the federal government have spent recklessly.
And the list of cities with debt and pension problems like Detroit's is a long one. (Buried under all the Detroit news on the same day as its Chapter 9 filing, Moody's cut Chicago's credit standing three steps to A3, citing pension fund liabilities and crime-fighting costs.)
One can rail against the injustice of cops and firemen retiring in their early 50s with pension deals that private-sector stiffs can't obtain, about teachers who can't be fired despite their students' poor academic achievements.
But gnashing teeth about America's Greek future has had little impact on public policy; Detroit's bankruptcy — the canary in the progressive coalmine — is likely to have some impact.
Whatever frustrated fiscal conservatives think they might obtain from their morality lessons, austerity proposals or privatization pushes is dwarfed by the fear inspired by the actual severance of union contracts that bankruptcy will bring about.
The corrupt political alliances that traded union votes for sweet pay and pension deals is now undermined by the inability to deliver on the promises.
For too long, policy critics have acted as if all their opponents needed was an economics course. Not knowing how budgets work was never the problem; not caring was. And now, because of Detroit's bankruptcy, officials in similarly situated cities will care more than they used to.
While the fiscally reckless are learning a painful lesson, it is important that those who cling to hoary principles such as living within one's means learn some lessons too.
First, there is such a thing as a zeitgeist, an esprit du temps — we really need a pithy English-language equivalent to this. The spirit of our times is not one that would cheer Calvin Coolidge, and fiscal conservatives who yearn for a new Reagan Revolution must accept that that does not fit contemporary American priorities.
Ronald Reagan got far in politics by deriding his opponents for their tax-and-spend policies, but it is precisely taxing and spending that has fueled the political success of progressive politicians at all levels in the United States today (with some notable state exceptions).
What fiscal conservatives must therefore come to grips with is that they can, at best, propose but it is progressives who dispose in today's climate.
Like it or not, every person has his time and everything its place. A resurrected Reagan could not be elected today.
Knowing that your role is a subordinate one does not mean you should yield to despair. Remember that capitalism — which to paraphrase Churchill's statement about democracy may indeed be the worst economic system except for all the others — is a dynamic process of creation and destruction.
While Detroit's policies have immiserated its population, they have done wonders for Farmington Hills and West Bloomfield Township, suburbs that have prospered from contrasting public policies and city services.
And the likelihood that creative and enterprising Motor City refugees can be found in thriving economies like Dallas or Williston, N.D., evinces the very American tendency to vote for more sober public policies with feet rather than ballots. Detroit's population is, after all, less than half its 1950 peak.
Who knows what municipal bankruptcies, federal fiscal cliffs and Social Security distress lies ahead? It is to be hoped that the experience of disaster will further our education.
But until the pendulum shifts again, the spend-within-your-means crowd can console one another and humbly offer their thoughts to those who will listen among the dominant school of thought.
As Henry Wadsworth Longfellow's charming poem "The Arrow and the Song" advises:
"I breathed a song into the air, it fell to earth, I knew not where…
And the song from beginning to end, I found again in the heart of a friend."
More news analysis from Gil Weinreich on ThinkAdvisor:


text:
Two months after the U.S. Supreme Court invalidated a key provision of the 1996 Defense of Marriage Act, the Treasury Department and the IRS have issued a ruling that implements federal tax aspects of the court's decision.
The ruling, issued last week, says that same-sex couples who are legally married in one of the 50 states, the District of Columbia, a U.S. territory or a foreign country that recognizes their marriages will be treated as married for federal tax purposes.
Importantly, the ruling applies regardless of whether a couple lives in a jurisdiction that recognizes same-sex marriage or in one that does not.
Starting Sept. 16, same-sex couples will be treated as married for all federal tax purposes, including income and gift and estate taxes. The ruling applies to all federal tax provisions where marriage is a factor:
- Filing status
- Claiming personal and dependency exemptions
- Taking the standard deduction
- Employee benefits
- Contributing to an IRA
- Claiming the earned income tax credit or child tax credit.
The ruling does not apply to registered domestic partnerships, civil unions or similar formal relationships recognized under state law.
Treasury and the IRS said legally married same-sex couples generally must file their 2013 federal income tax return using either the married filing jointly or married filing separately filing status.
Individuals who were in same-sex marriages may, if they want, file original or amended returns choosing to be treated as married for federal tax purposes for one or more prior tax years still open under the statute of limitations.
Generally, the statute of limitations for filing a refund claim is three years from the date the return was filed or two years from the date the tax was paid, whichever is later. As a result, refund claims can still be filed for tax years 2010, 2011 and 2012, using Form 1040X, Amended U.S. Individual Income Tax Return.
In addition, employees who purchased same-sex spouse health insurance coverage from their employers on an after-tax basis may treat the amounts paid for that coverage as pretax and excludable from income.
Couples who live in jurisdictions that recognize same-sex marriage can also file joint state tax returns. However, the process will likely be more cumbersome for couples who live in jurisdictions that do not recognize same-sex marriage.
According to a report in The New York Times, each spouse will probably have to prepare a dummy federal return as if filing as a single person or head of household, then transfer the information on the dummy form to his or her state return, which must also be filled out as single or head of household.
Check out Post-DOMA's Demise, Prepping Your Practice to Meet the Needs of Same-Sex Couples on ThinkAdvisor.


text:
Like many folks, I have long admired parts of "Uncle Bob" Martin's work. While I disagree with him, sometimes strongly, on some of his views, there is no question that a meme he has long pushed is absolutely spot on: Checking in code without accompanying tests is unacceptable. I'm not here advocating Martin's larger solution (test-driven development), but rather acknowledging the rectitude of his fundamental position. To be fair, Martin is not the only person, nor even the most prominent, to advocate the value of checking in code and tests at the same time. Kent Beck, Michael Feathers, and many of the exponents behind continuous integration and DevOps have long articulated this position. But Martin has tirelessly championed it and, in large part because of his efforts, most diligent developers today reflexively understand the importance of writing tests that immediately exercise their new code.
It's become such a standard part of development that its absence looks like the sign of a shop mired in the past ways of doing things or just too sloppy to care about the code they write. For a while, perhaps up until a few years ago, you could argue that if we can put a man on the moon without developer-written tests, it's certainly possible to write good code without tests. And even today, I meet developers with this point of view. However great their unique talents, they simply cannot get around the important question: How do they know that changes they make don't affect the proper operation of existing code? This role of tests to act as sensors and monitors throughout the code base is probably the most compelling argument for their use.
Choosing not to have a comprehensive regression suite is, in my view, invariably wrong. And it leads to embarrassing situations like the one that erupted last week with Kaspersky, the consumer-oriented vendor of security software (anti-virus, anti-malware, etc.). One of its products is a password safe in which users place their passwords for safe, secure storage. When users need a password, they open the safe (with a separate password) and copy/paste the needed password, which shows up as a series of dots. After which, they close the safe and go on about their work. New passwords are added through a a simple form that wisely includes an option for an expiration date for the password. If the user chooses, the expiration date can be set to "never."
Last week, Kaspersky released an improperly tested update to the password safe. It was certainly not tested with a regression suite as I'll show in just a moment. The result of the update was that all passwords were suddenly marked as expired and the option to correct the expiration date was grayed out. I don't have any knowledge of how Kaspersky writes software, although the company was contacted for this article (and did not respond to inquiries). Despite this information, it's not difficult to derive some information based on the symptoms.
It is clear the company did not do regression testing or it would have found the problem. It occurs on Windows 7 machines, and in the case of a friend who alerted me to the problem, a fairly stripped-down all-Microsoft Windows 7 Home machine (meaning its primary applications are Microsoft Office, Outlook, and Internet Explorer). The frustrated forum comments indicate that many configurations of Windows 7 machines exhibit the symptoms. Given that Windows 7 is the most popular laptop OS today, the lack of testing on this platform is indeed remarkable.
But there is another telling clue that testing was insufficient or not performed at all: The passwords, which were all marked as "never expire" suddenly bore expiration dates from the year 1601.
The date is particularly troubling. In testing, it's always useful to know what the invariants of a program are. That is, the things about the program that are always true, regardless of what state the program is in. Invariants are rich veins to mine and should be exploited to the fullest in regression test suites. In this case, we know an invariant of the program is that no password can expire at a date that precedes the original release date of the software. If it originally was released by Kaspersky on, say, 1 July 2011, then clearly no user can enter a password expiration date prior to that date. It's an invariant that password expiration dates can never be earlier than 1 July 2011. Any violation is a symptom of an error.
A date of 1601 suggests lack of testing and/or a poor design decision; namely, to use invalid dates as data of some sort, such as an error code. This kind of reuse of a data field to represent a completely foreign data item is a terrible idea. It was common in the days when disk space and RAM were expensive. Bytes that were used as flags for one thing were often overloaded to signal unique or rare conditions. This practice still continues in resource-constrained embedded systems for lack of better alternatives. However, for desktop apps, it's an unmitigated problem. For one, you're now displaying mystifying information to a user who is already trying to figure out a confusing problem. Second, you've destabilized the invariant. Now, every test of the invariant must test for all exceptional values that are legitimate a constant maintenance problem as new error values are added to the overloaded field. Instead, errors should always be flagged by their own fields and own diagnostics. This maintains the integrity of the testing and, in addition, keeps the code clean and readable. (On the latter point, think about the code that tests dates and translates dates into error codes. How would you react to seeing that in an app you've been asked to maintain?)
It's now been a week since the first reports appeared on Kaspersky's support site. There is no fix yet, which again suggests test suites are badly missing. The only posted information is the repeated promise that a fix will be forthcoming. No explanation and no workaround. My friend is now wisely reexamining whether she should move on to another provider of security software that will never lock her out of her passwords. If you don't test your products adequately (beginning with developer tests, which would have caught this problem long before release), these are the just desserts.
Andrew Binstock
Editor in Chief
[email protected]
Twitter: platypusguy


text:
I hope it is a high as expected. I promised a revolution
I hope it is a high as expected. I promised a revolution
To leave feedback: Click seller/buyers name, Click feedback score, Click leave feedback
that paint deal is only for december
any idea what Vandal registrations are up to currently? Will they send me registration info or not until closer to the event?
The "paint deal" meaning our AO paint deal or the 1 free bag for every 2 cases you purchase?
Sometimes It's Good to be EVIL
Ha ...i was wrong it is cheaper to get here on AO. That is why you dont let a landscaper so the math. It works out to be $15 cheaper.
we dont get the free bag. when push comes to shove. 2 cases with a free bag comes to 0.033$ per ball and 2 cases from us comes to 0.032$ a ball. but for december only.
is that the CPX Free bag for December or the AO discount for December? I thought originally the AO paint discount was until Feb
the cpx free bag is december only
we have till febuary
Styg...they sent me an email conformation when I signed up.
yep got the same, just didn't know if they shipped out a packet of info or anything
so whats the deadline for sure and whats the free bag deal? ty
Our paint deal is 1 case (four bags) for $65. The "buy two cases, get a bag free" deal is $74.95 per case and you get one free bag for every two cases. This means that if you buy two cases with the group buy, you would get 8 bags for $130.00 (16.25/bag). If you buy two cases with the other deal, you get 9 bags for $149.90 ($16.66/bag).
So, according to the newsletter, this deal is for December only. However, buying paint through us is still a better deal, regardless of how many cases you order. Our deal is good until February. I hope this clears up the issue of the AO Army discount vs. the buy two, get a quarter free discount.Originally Posted by December CPX Newsletter
the case for 65 dec deadline is crappy with Christmas timing would love to jump on it but not possable , should be jan or feb.
For those of you who do not get the CPX or Living Legends newsletters, I have added the current promotions to the third post in this thread. I will update that every month when I get the newsletter.
how many people have ordered so far?
after watching the video on the LL link on cpx I hope 2 cases is enough as I doubt i can afford anymore.
it wont be... ooooo trust me
The December paint order has been placed.
all 3 of us?
what is the last deadline for paint...feb?
sean's on vacation till the 7th. said no paintball talk till then
January registration promo is up.
I think I screwed myself... registered in December and ordering paint in January - knocks me out for both drawings... about par for the course on my luck


text:
Wireless infrastructure software company Radisys has announced WebConnect JAVA, a JSR-309 compliant adapter which is compatible with the company's whole Media Resource Function (MRF) product family.
Java Enterprise Edition (Java EE) application developers are now able to use Radisys WebConnect to control media processing capabilities for real-time services.
This is essentially a JSR-309 compliant adapter for virtualized media processing platforms. It may help create more media-rich applications scenarios with Java developers.
So how does it work? Radisys WebConnect translates JSR-309 media processing requests, in a Java EE environment, into Session Internet Protocol (SIP) and Media Server Markup Language (MSML RFC 5707) XML-based control commands — which are compatible with any Radisys MRF. The resulting integration is a solution that supports IP multimedia packet processing across both OTT and IMS architectures for a range of interactive services, including VoLTE, WebRTC, conferencing, and network transcoding use cases.
"Service Delivery Platforms (SDP) based on Java EE are increasingly being utilized to support real-time telecommunication services — particularly for OTT and WebRTC," said Ari Banerjee, Senior Analyst at Heavy Reading.
"The Java community defined JSR-309 as the media control interface for Java-based platforms, yet the scalability, virtualization, and platform options for JSR-309 media processing have been somewhat limited across the market. The entry of a media processing leader like Radisys adding JSR-309 compliance across its MRF platforms provides OTT service providers and mobile operators with a well-supported range of media processing options to choose from."
Real-time communication services have traditionally been developed, and deployed, on specialized application server platforms designed to IP Multimedia Subsystem (IMS) standards supporting SIP. However, there is now a growing trend to develop interactive communication services, particularly Over The Top (OTT) and WebRTC services, on web application servers based on traditional Internet communication and programming standards, such as Java.
"Adding support for JSR-309 was a simple decision as many of the leading web application server platforms on the market today are Java EE based,
"In addition, the world has far more computer programming professionals with expertise in Java programming than telecommunication service developers with expertise in SIP. Radisys WebConnect is focused on opening up this market by delivering first-class media processing capabilities to the broad community of IT professionals developing real-time communication services using Java platforms be they WebRTC, video, or audio based."


text:
Our colorblock sport duffel is perfect to haul all your gear to the game or on a weekend retreat. It has a large main compartment, two large side pockets and two smaller front pockets. The strap is adjustable or removable so you can carry it whichever way is comfortable for you.
Every order is custom printed and personalized to your needs direct from our production facility in Detroit, MI. Items are typically completed within 5 business days and then require additional shipping time to reach your location.