I want to test a terminal emulator I have, but I really don't want to learn Hercules 360, before someone mentions that.
I'm not after creating mainframe applications, what really want to do is learn how to send tn3270 screens for display on a terminal emulator. My reason is simple; I have a set of screens from a customer where their layout, look and feel, etc are all fixed. I want to test my client software against those screens without having to trail all the way out to the customers site to do it in the first instance.
Failing that, does anyone know of a "less intense" method of simulating a tn3270 environment complete with fields, attributes, etc.. ?
I found a reference to an old freeware product called miniFrame by CodeCutter, but the website for it no longer exists and google returns various links that just point back to it.
Thanks
Related
I was wondering if anyone (possibly Adobe/Aviary) could clarify something for us. Our startup is looking at an photo enhancer/editor - and I'm curious about the Adobe Image Editor UI, but was quite put off by making users have and Adobe account and having to log in. I have looked at all the documentation, sample code and it all points to the "Integrating the Authentication Component" here https://creativesdk.adobe.com/docs/ios/#/articles/gettingstarted/index.html. Is not the client-id/client-secret enough to know the billing scenario for us?
In fact, even ONE external login would kill user experience for our offering.I understand that the Cloud components would require separate logins, but we just want Image Editor UI, nothing else (and willing to pay for this obviously).
What I want to know is, would the users of our app have to login and manage login state (with adobe) every time they want to use the Image Editor? If anyone could point me to the right documentation it would be great. I plan to write the wrappers for React Native once I can confirm this (yes, I'll open source it as well once I'm done).
Thanks
No need any user login.
You see this login screen since you are in DEVELOPMENT MODE, in release mode you won't see this.
To see how it's really works on production (release) mode, see some app that using this image editor.
I have an iOS app where I have analytics setup (as most people do) that tracks a whole set of different scenarios. In a few of them, the data I send with the tag doesn't all get sent. What I mean by this is best demonstrated with an example. If I send the following data as a tag in one of my analytics:
User successfully logged into the app and hit the homescreen
Now, I wouldn't normally send all of that in just one tag, it would get broken up, but for example purposes, pretend that's what I want to send. For quite a few users, tags like this will get sliced up into all sorts of different tags, so when I actually look in SiteCatalyst, I end up seeing a bunch of tags that may resemble something like so:
successfully logg
nd hit the homescreen
User successfully logged into the app and hit the homescreen
User successfully logg
And so on. It breaks it up into a bunch of different parts, and then displays them all as separate tags. The ones that are affected get broken up into 15-20 different tags all of which are different parts of the full tag.
Here is the hard part: I can't reproduce the issue. I'm trying, but haven't been able to yet. I also am not very well versed in Adobe analytics and am not sure how the backend setup is for us on SiteCat.
Because of my inexperience with analytics, I'm not sure what more data may be helpful. My code doesn't do any truncation, it simply calls trackAppState:withContextData:, and the tags in my contextData get truncated like I showed.
Does anyone know why this is happening? Has anyone seen anything similar? Or could anyone point me in a direction that may get me started looking into this issue? I'm really at a loss of how to go about debugging this issue.
Edit: One piece of info that just hit me! I build up the tag in question (at least the current one I'm trying to reproduce, for all I know there are other tags that get truncated that aren't built up like this, I haven't gotten a chance to look into all of them yet.) using `-[NSString stringWithFormat:] and take the errorMessage that is returned as my message, so it's a dynamic tag.
It may have something to do with the stringWithFormat: message? Again, very lost as to where to even start with this one.
can you give us a sample of the code you use to call the trackAppState?
If it can help you you can enable debug logging for the Adobe Analytics library calling the method [ADBMobile setDebugLogging:YES]; in the appDidFinishLaunchingWithOption.
In this way you can see in the console how Adobe send the data.
You can also use the tool "Bloodhound" which is a proxy App developed by Adobe expecially for osx in order to let you sniff all the info sent by your App in real time, you can find it in the help section of the mobile marketing interface.
Thanks,
Claudio.
I am looking to build an iOS app and website that work 'together'.
What the plan is for each:
On the iOS side, it will be pushing information to the server in the form of a post. The users will then be able to vote up and down on the posts as well; which also implies they will be able to see the other users information (in real time).
The website will be viewing this information in real time and using the posts. If a post gets enough down votes the server should tell the website and apps to remove it.
I have experience with SQL. Although SQL does not seem to be the appropriate server choice - for what I want to do - given my experience with it. (I could definitely be wrong.)
I would like to host the information myself, however have heard that Parse is good about holding information for iOS apps. I just don't know whether it gives you enough freedom to work with websites as well.
TL;DR: What kind of database/datastore should I use for a real time queries that allows for push notifications?
All suggestions are welcome. Thank you.
Try Using FireBase
firebase.google.com
Documentation
Can you tell me if Apple accepts an application that opens an embedded browser with most of the functionality living on a web application on the internet?
I have read contradicting opinions on this, and I have even seen several apps that seem to use an embedded browser for the main functionality of the app. Still I couldn't confirm this.
This way we could correct problems on the application functionality on the server with no need to submit another version of the app, while keeping the ease of release through the app store and the home screen shortcut.
Thanks!
I can't get the exact quote from the guidelines, but I know that Cordova apps are allowed, and updating the web files dynamically without going through a new native app version is also allowed, as long as:
* The updated code runs with the Safari Webkit engine (true for Cordova)
* The main functionality of the app is not changed
You say this is a bad idea because the user can save a bookmark on their home screen. This doesn't seem to me like a reason for something being a bad idea to me. If this is the only drawback then I would say go ahead and do it. Why should I care if someone wants to bookmark to my site? The app will not work very well outside the app anyway. If you have an actual logical reason why this is a bad idea instead of some emotional response then please bring it up.
I am doing this too in my application. I am under the impression that as long as you are pointing to a secure site then it should be okay. Please enlighten me: is there some good reason why Apple forces people to develop applications the hard way? A web application is hard enough without having to deal with some monolithic organisation imposing ridiculous rules on you.
Most sites are either fully released, or in beta.
But what happens if you have a large site, and some of the parts are still in Beta, and other parts aren't.
How do you effectively communicate this to the customer?
Maybe take a look at how Facebook, Bloglines, Gmail did it?
Like "We have this beta thing going on, come on over and see the same site with new stuff, but if it doesnt work, use the old parts"
Maybe gmail labs where you can sign up for "beta features"
If there's a certain way you enter the part of the beta site, maybe you can have a modal that pops up that they have to agree to every time. I wouldn't have it on every page since it gets annoying, so I would only use this approach if there is a definitive way to get into that part of the site (e.g. people won't be coming to random parts of the beta section through Google or something).
One way I've used for non-web software is a change to background. So for example if your normal site tended to have a plain white background, you could have the beta site have a repeating beta text in a background image. You want to make it fairly faint so it is present but doesn't detract from the overall experience.
Another subtle but present option would just be to change the title bar.
Or you could do what google does, which is a large site with some of it in beta. Check out Google experimental search. Basically the site is no different, but it is hard to get to accidentally.
There are a few ways.
Provide access to the site via two domains (e.g. www.domain.com and beta.domain.com) and only allow access to beta parts of the site when going in via beta.domain.com.
People will be accessing the same code base, but will only get access to the beta sections if they've specified the beta subdomain. Trying to access beta sections of the site will explain this & tell them how to access the beta.
Strongly Flag the beta sections of the application as being beta, and force the user to acknowledge that they're OK using beta features with some kind of agreement screen. The first time they try to use the beta feature, they'll be shown the agreement screen. Subsequent uses of the feature will prominently deisplay that "thios part of the site is in beta and is used at your own peril."