I'm learning Flex and I've just found this nice effect. Would it be possible to import it in Flex?
Thanks in advance.
Greetings.
Yes, but you'll need one of 2 things:
Enough knowledge of the similarities and differences between Flash and Flex to be able to translate the instructions for making MovieClips and TextFields to using Flex components such as Box and Label. If you have that, you probably wouldn't have asked the question.
Someone who has that knowledge who is willing to explain the differences.
I can be quite patient and verbose when I haven't had a bad day, but today I have. I didn't want to leave your question completely unanswered, but the answer of "yes" probably won't get you too far without a lot of explaining.
Related
I started using core-style in (mostly) all of my components. On 0.4 it was pretty helpful, but i can't really see why should i use it now with 0.5. Is there any specifics to when should i use it?
Any case in particular?
ps.: The thing is: data-binding had a bunch of problems which i haven't encountered so far on .5. Can anyone help me? I know it's a bit broad question but i don't want to go through the trouble of getting it out of my code then back in again just so i know where i should actually be using it.
Core-style is useful to create shared themes across the application. Take a look at this artcile http://pascalprecht.github.io/2014/08/01/sharing-styles-across-web-components-with-polymer-and-core-style/
This is about kiosk contents(Full-Screen).
I'm trying to input some texts in the 'AIR popup-window'(facebook login)
with virtual keyboard(as3.0).
I know the 'HTML loader class' can be a solution, But I think this is different case.
How can I make it? I really need your ideas!
Thank you for read this, and sorry my bad English.
With respect you should really do a thorough search on google or even stackoverflow, as this question has been posed already at least once. Anyway here is a question on the same issue some one answered here:
Flash APIs for Android Platform
Basically it involves a new method in InteractiveObjects that manually invokes the system soft keyboard. Pretty basic stuff. Hope it helps! :)
In 4.5+ of the Flex SDK there's still no Sparks flex component that replaces the ViewStack. I know that there are several ways to mimic that behavior with states or includeInLayout properties. I also know that there's a couple people out there that have created their own sparks ViewStack.
My question is why is there no official replacement and what are best practices for the replacement of that functionality moving forward.
You are correct, there are several ViewStack implementations out there. One good one I found was Todd Anderson's here: http://custardbelly.com/blog/2009/09/02/viewstack-in-flex-4/
But moving forward the best practice now to get the functionality is to use Views and a View Navigator. Check out more information here: http://opensource.adobe.com/wiki/display/flexsdk/View+and+ViewNavigator
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?
I'm a non-developer building a simple Access 2003 database for an NGO that works in developing countries. I would like to provide in-app help (what certain fields mean, for example) in a number of forms and on the switchboard. I'm not sure about the best way to do this - not just on a technical standpoint but to increase user-friendliness. The users are usually using MS Access for the very fist time, and have only basic computer use knowledge.
I don't want to cram the forms with help text, so I'm thinking of adding little question mark buttons that pop up a separate form with just help text. Is that wise?
I've also noticed a Help Context ID property, but it looks complicated (I'm looking for something as simple as possible to implement, so that the help text can be edited as easily as possible by others in the future). I think this is where I'd start if this were the way to go: http://support.microsoft.com/?kbid=209843
This may need to be translated, etc, so again, the simpler the better.
Thanks!
I've built such a system using tables and forms in the FE. You can get an idea by reviewing some of the screen shots at http://www.granitefleet.com/ScreenShots/index.htm I only created general help describing processes where something on a setup form can affect this form. So the user will know where to ge to change something around.
If you haven't built your forms yet, put that information in the table design, using each field's Description. That will propagate through your forms, and will be displayed on the Status Bar whenever a user click in that field.
If your forms are already done, use the [Status Bar Text] and/or the [ControlTip Text] property of your controls.
Just train your users or write once that they should read the Status bar if they need more explanation.
KISS (keep it simple and simple)
Great question. I think the real solution to reducing the amount of work that you need to do is to work really hard on having a simple, clean UI. In the real world there are very few people who have the patience or inclination to read the manual or search the contextual help even in the face of being stuck.
I know this is slightly off topic from the question but if you look at this website for example it keeps the number of things you can do on anyone 'screen' down to the minimum and everything has a tool tip (ControlTip Text in msaccess). Even if site this was in Japanese, I thin i could navigate around it fairly easily and that is because of its simplicity. (I couldn't answer any questions though :P)
Jakob Neilsen has a great site on usability
" I think the real solution to reducing the amount of work that you need to do is to work really hard on having a simple, clean UI. In the
real world there are very few people who have the patience or
inclination to read the man*emphasized text*ual or search the
contextual help even in the face of being stuck.*
Regarding this, it really depends on the application. It is overly simplistic to assume that every application can have all the information it needs to be operated just by having a simple clean UI, especially if in the name of being simple, there are alot of useful features that are not included. In certain complex applications, people will simply need to have patience and read the information available or they will waste a lot of time guessing. It is better to have have information at the press of a button than have them asking for it once they figured out that they are wasting time figuring it out with no help. I agree that many apps are way more complicated than they need to be.