I need links for blog, tutorials that covers GroovyFx. I have tried searching it on google, i'm not getting any useful tutorials. I need a full coverage of GroovyFx from top to bottom!
Thanks in advance.
You mean you want full coverage blog entries, or tutorials about GroovyFX for JavaFX 2.0?
GroovyFX (according to the best page I can find) is an Alpha v0.1 release.
That page was created June 7th 2011
I think, you're probably asking too much for a full top to bottom blog
Indeed, the best I can find at this time, is this interview page
GroovyFX is fairly new, and as mentioned it is still in alpha state, though it is pretty complete based on the current JavaFX 2.0 Beta. Our plan is to GA release it as soon as possible after JavaFX 2.0 is GA'd. Currently, we are writing API documentation and doing performance tuning. No tutorials yet, at least none by Dean or me, though a few people have been using it for projects.
Related
I am a history teacher and have been working to assist students learning English with class materials and work along with many of my co-workers. Although it has its issues, google translate is incredibly helpful. I had been looking for ways to translate slides efficiently when I found the "Quickstart: Translate add-on for Google Slides" page of G Suite Developers. Link Below.
I know a bit about code and was able to quickly follow the instructions (which were excellent) to set up the add on, but many of my co-workers may struggle with adding it to their slides.
Long story short here is the question:
I am wondering if there is an already published version of the page/Quickstart Translate add-on which people can use instead of setting up the add on manually? I have not been able to find one.
I'm running into the same problem and have found the same document as you. Have you thought about publishing the add-on to your domain only. You can do that and the link you have links to the documentation on how to do so. You may need to work with the Google Admin in your district to make it happen though. Good luck!
Many years ago I worked at a DEC-shop. We used a tool called Document (as far as I remember) to create documentation. It was provided by DEC and created the same layout as the original DEC documentation. Which is as far as I'm concerned a milestone in layout and typesetting.
Researching the web I found a more or less obscure company which sells this tool for Open VMS. But I would prefer an open source replacement.
Any help ?
Greetings Till
Touch Technology was, and perhaps still is, an interesting company with interesting folks like 'Mr Dan'.
They picked up a good bit of Digital software in a fire-sale and had some good stuff such themselves such as performance tuning tools and a 4GL (Intouch... available on OpenVMS Freeware).
The company appears to have moved one, judging by their current website front door which does not dwell on the old stuff , but you could do worse than try contact them.
The back door still list DECdocument: http://www.ttinet.com/documentation.html
Good luck!
Hein
If you're still looking for a solution, have you thought about LaTeX? The markup syntax isn't radically different from VAX DOCUMENT's SDML. They both have the same back-end; the final steps in processing an SDML file involved running it through TeX.
I would think the best solution would be DocBook, since it is also an SGML-ish format. You might be able to translate a substantial portion using XSS.
I am looking for a YUI book and this one seems to have reasonable reviews:
http://www.amazon.com/YUI-Learning-Library-Daniel-Barreiro/dp/1849510709
However, I will be using YUI 3.x. Will this book still be a useful introduction to YUI generally or is it more likely to confuse with out of date information?
A YUI 2.x book is going to be no help, I suggest the online docs & visiting the IRC channel (#yui on freenode).
Evan Goer is writing a YUI cookbook that is shaping up really nicely but won't be out for another several months. If you really want a book on YUI that one will be the one to get.
It will probably just confuse you. YUI 3's API is rather different from YUI 2.
The book was published in May '12 and has a lot of details on YUI3:
http://shop.oreilly.com/product/0636920013303.do
If you have questions, feel free to ask at the YUI Forums: http://yuilibrary.com/forum/
I've been curious about this for a while now, hopefully this isn't to secretive and some Googlers could give some information about this?
No, see e.g. https://code.google.com/p/or-tools/ which is Python 2 only.
Python is far from the main language at Google anyway, see https://groups.google.com/forum/?fromgroups=#!topic/unladen-swallow/TtvEBvVEZD4
Also, " Today dozens of Google engineers use Python," http://www.python.org/about/quotes/, which is a small fraction of all engineers.
I'm not a Googler, but I'd say the answer is most likely: yes.
After all, Guido van Rossum, creator of Python, has been working for Google since 2005. And it's not really like using Python 3 is such a secretive thing. A language upgrade isn't such a "killer feature" that will sweep all competition off their feet.
Do know that using Python 3 in house is one thing, and providing Python 3 APIs is another.
Case in point: Google has been using Guice since 2006 in its mission critical applications. This means Guice has probably been under development earlier than 2006. Yet, the first public release of Guice has been in March 2007.
There is no reason to believe they aren't doing the same with Python.
As you can see, my answer is highly speculative, but it does use some common sense based on facts and previous Google's moves.
I am not a Google employee, on Google App Engine they still provide Python 2.5
I have been using jQuery/Prototype/ExtJs and other frameworks for last two years. These frameworks have been very useful.
I switched to YUI recently and finding the learning curve a bit too steep. Also the framework is not making my life as easy as with Extjs or Jquery.
When I consulted several other developers no one seems to be very enthusiastic about YUI. Very few of them have actually used it. Of course this depends on where I stay and what kind of people I interact with but can I say safely that YUI is not beign received as enthusiastically as jQuery? Why is it so ?
NB: I'm an engineer on the YUI team! I think you ask a great question, something I have wondered myself.
IMO, jQuery is more widespread than YUI because it is easy to sprinkle it on web pages that need simple DOM manipulations and basic AJAX or animations. That said, YUI is an extremely popular library that has historically been a favorite of more advanced developers and application builders. We do have a huge and thriving online community on yuilibrary.com -- perhaps folks are too busy writing great code to make a lot of noise? ;-)
That said, we are hearing a lot of buzz these days from jQuery folks hitting the limits of that library as they transition from throwing together simple effects to needing more maintainable, performant, and well-architected code. YUI 3 takes you from the basics to the most complex applications without missing a beat. It is a world-class platform for novices, hackers, and application developers alike: a concise, convenient, and intuitive API that is lightweight and lightning fast, PLUS a well-thought-out infrastructure and comprehensive suite of tools to help you code like a professional.
I agree that the learning curve for YUI has been high -- we are in the midst of a website redesign and writing an O'Reilly cookbook to address exactly that issue. We're also hosting our second annual YUIConf this November to unveil our latest and greatest. We've coming a long way since the days of YUI 2 and we're excited to make it as easy as possible for folks like you to ramp up on YUI 3.
Akshar -- my response is YUI-centric, for sure, but the YUI developer community is huge, enthusiastic, and growing. Check out http://yuiblog.com/blog/category/in-the-wild for some of the implementations we've seen recently. In addition to what's out there in open source, the Yahoo! home page, Yahoo! Search, Flickr, and the upcoming redesign of Yahoo! Mail are all based on YUI 3, the next generation of the library -- which has been welcomed by developers as having industrial strength power along with the concision and selector-driven syntax that makes libraries like Prototype and jQuery so fun to use. My advice: Try it out. YUI 3 is a unique, incredibly powerful library, and its 200 community contributed gallery modules (a number that grows by the week) make it one of the most comprehensive libraries out there.
As a user of both jQuery and YUI, I have to admit that I look at them in almost completely different lights. I use jQuery for custom effects, animation, interactivity on our externally-facing website. The visual extensibility of jQuery means that we can customize the look and feel of these elements to match the rest of our website. I've used YUI as a quick and easy way to develop a snazzy front interface for some of our internal applications. These internal applications are simple Apache/MySQL/PHP apps, and YUI allows for simplified data visualization, form handling, tabs, etc. without having to worry about the look and feel as much. The standardized, slightly bland interface elements are a perfect, no-nonsense approach to quickly developing and rolling out these apps.
I found the learning curve to be a bit steep myself, but the examples help out a lot.
I've been using ExtJS and JQuery for some time, but now i'm experimenting with YUI 3. I like the general idea behind YUI (modules, async loader, plugins) but some things annoy me:
lots of documentation, but some things aren't documented at all or very scarcely
some features are very basic (data grids) compared to their ExtJS counterparts.
you never know which features are there in the core, in gallery or aren't implemented at all. You need to do the research yourself.
the framework feels less coherent than ExtJS
I'm trying to find a replacement for ExtJS for building business applications, but didn't find any framework that would be as rich and complete as ExtJS. I don't like how ExtJS looks and how it forces some strange implementation/architecture decisions on you (MVC!), but have to admit it's really hard to replace.