Is there a library simplifying the process of dragging and dropping between the Flash/Flex environment and the surrounding browser?
I've done some research on the process, and so far the closest thing that I have found is from HTML to Flash in a Floorplanning application. I have yet to find a demo going in the other direction however.
Is there a simpler way to do this now?
I didn't even think it was possible at first until I looked at that link, and I agree with their description that it will be very difficult to get working on all browsers / OS's.
Related
Problem
So we have quite a big project with lots of different Partial Views and a client side data binding framework (Knockout.js in our case).
One of the more problemtic parts is that is getting harder and harder to figure out which partial view is rendering an element that I see on my page.
So I need to debug this particular DIV. Okay, where do I find it?
Usually I try to find a very specific class or ID close by this element and do a search through the whole platform - far from ideal.
Question
So I was thinking about the following; tagging all elements (in debug mode) with the source file where they have been generated.
Right now I'm thinking about something like a precompiler that adds a data-source="" to every element. I might refer to an ID within a dictionary to prevent repeating all the long filenames.
Before I'm reinventing the wheel:
is there already something similar?
are there better alternatives?
We're using ASP.NET MVC, but any hints to how other platforms do this are perfect too.
If you are using Visual Studio, I highly recommend the Web Essentials extension. Among many great features, it has one called "Inspect Mode", part of the larger "Browser Link" feature, that does exactly what you are looking for; it identifies the file that a particular DOM element came from. It might be worth a shot if that option is open to you.
#Dirk, as per my understanding your issue is to easily identify the element/view. Adding data-source can be an option but before that have a look at this link
Editing Styles and DOM - Chrome Dev Tools
This page has many demonstrations which might be helpful to your problem. Furthermore, I do agree with Kevin suggestion.
I happend to stumble upon this site
http://www.htmlfivewow.com/demos/terminal/terminal.html
It is simply amazing. I was just wondering on how is the terminal being emulated in the browser ? Can we embed the terminal in the browser and use it normally ? If so how?
i found this link which kinda enlightens the architecture http://www.htmlfivewow.com/slide33
But one thing aint clear what exactly is CRX-LEss Web app ? its completly new term , i havent herd of it before ( googling dint quite help me )
The actual presentation for the demos is from the Google I/O conference, and the talk was called HTML5: The Wow and the How. If you watch the video, they go over everything that's implemented in the terminal demo:
http://www.youtube.com/watch?v=WlwY6_W4VG8
It's very cool stuff.
A great thing about the web is that on any page you can View Source. Give it a shot. The source is well-structured and though it could be better-commented it's pretty straightforward. Even if you don't understand it in its entirety it will give you a place to start searching for the techniques used.
With JavaScript, the DOM, and <canvas> (which, I should mention, isn't used in this instance) just about anything can be created, from terminal emulators to Nintendo emulators.
A CRX-Less web app is an unzipped Chrome extension and points to the manifest.json file for the extension. It is an experimental feature and must be enabled in the chrome:flags page. https://developers.google.com/chrome/apps/docs/no_crx explains how the process works.
As I was working on this project for a friend of mine who is terrified of changing from HTML to flash, I realized that maybe there could be a bridge between them. So I started working on a flash project that would grab the HTML from his page and parse it to display it in flash. Although I am sure there are resources available for this already, I figured that the experts on SO might be willing to suffer through the logic of one user trying to develop this script.
So basically, I am not asking for an answer, I am asking for some step-by-step direction that could be posted so other people could see the logic behind breaking down this project. I think it would be really useful (not just for me, but for anyone wanting to learn more about objects and oop).
So, much like the thread between primarily Senocular and Rampage, this would be a thread where I would be the student asking the questions in a logical step-by-step manner and someone else (or someones else) could provide guidance.
Let me know if you are interested and I can start by posting what I have already written. We can go from there and I am sure it will prove insightful to anyone who reads it. If no one is interested, or no one has the time or inclination, no problem.
Best wishes,
Jase
Who in their right mind would change from html to flash for displaying a simple website? I don't see the logic behind it, it's more like you are trying too hard. Flash has its function in the web, as well as html does. If it's just for simple displaying, using flash is just the wrong way and won't make your website any better but worse because its loading time will be too long.
Goole Search retrieved these:
HTMLWrapper
Groe.org HTMLParser
There is an article about the 1st on *drawlogic. I think the seconds' home is on sourceforge here.
Thing is, browsers already do a fine job at parsing html code. Having the flash player parse html files not only does away with any accessibility advantage your markup can offer but it also feels like reinventing the wheel. If you need to display html content, leave it to the browser.
Slightly offtopic - Flashpaper can convert most HTML pages into swf format.
Given properly "disciplined" HTML, you can use the XML parser in the player for the basic parsing. Are you really talking about writing an HTML renderer in Flash though? Or just being able to pull information from HTML dynamically?
Using both libraries will make my life easier. But there seem to be some sort of a problem. Anyone knows the solution to this? Thank you.
I agree with Dimitar, use one framework where you can, it will make life much easier. Mootools has a raft of goodies that you can plug in and get going with. I suggest you have a look at the clientcide site http://www.clientcide.com/ and their download page where you will find Tips.Pointy which will do just what you want.
http://www.clientcide.com/js
So you know Mootools has done alot of work to allow it to run side by side with other frameworks but any plugins written for them have to use these new features for it to all play nice. All of clientcide's code has been re-written to allow it to use these new "play nice" features in Moo.
Enjoy
you can make a non-prototypial library co-exist with mootools or prototype (for example, jquery) but you can't easily get libraries that change / extend the native prototypes to co-exist with each other.
chances are you can get things going if you namespace but any code that you have that depends on the first framework that you load may stop working as expected (prototypes again)
as far as i remember, there were some efforts in the past to get this going - there was a project called SmoothGallery or something.
my advice is - find a tooltip plugin for mootools and drop prototip. forcing two frameworks on your users is a bad practice anyway
good luck :)
I'm curious what change requests, from testers, clients, or managers, programmers have encountered that seemed really simple but were in fact really complicated.
Could you add an undo button? (To a custom WYSIWYG editor).
Back in my college days I worked on a side project for a client. It was a medium sized Win32 desktop application to do some 2D diagramming and every step of the way and every demo was great. The client liked it. Finally, I was ready to deliver it and be done when they asked if I could just make it run on the web first.
Classic "missing-requirement-kills-project" scenario.
How about adding a GUI to this command line app?
One thing I've hit was being asked to change a word in the title of a window. However, the title of the window was in fact localized in a library and was shared with several applications. Changing it's title in either title would mean either changing where it grabbed the data (ugly and inconsistent with the rest of the code), changing the dll (will impact other software), or adding a hard-coded fix (hacky).
"I'd like to use Oracle instead of SQLServer for the database."
"can you make it bigger?" in reference to the sizing of radio buttons.. back before CSS
"just make it more webbish"