I think it would be quite hard to do iOS dev on a Windows box because
you would need all the xCode libraries to do even the most basic thing.
Then you would be cross compiling to ARM code and would need some way to
fling your app to the phone in a secure way. There are cross-platform
dev setups to create apps that run on Android and iOS but Apple has
generally discouraged these. First, they tend to generate more bloated
code because they have to abstract away the platform differences. Then
there is the issue of only being able to use the
lowest-common-denomintaor features between the platforms so any
new/special stuff on iOS won't be available because it can't be ported
to Android. Then there is the problem of accessibility since
accessibility on Android only became possible in the very latest version
and so it's very far behind. A few apps I tested that came out of a
cross-platform dev environment (monoTouch if I recall) were totally
inaccessible on iOS. Another risk is you build your stuff in ABC to make
it cross platform and then a year later ABC goes out of business or is
acquired by XYZ so now your code is on an abandoned or unsupported
platform. Similarly is lag. Apple releases iOS 7 and then you have to
wait for ABC platform to support it.
CB
On 7/21/13 11:38 AM, Scott Berry wrote:
I was wondering is there anyway at all to code IOS apps in the Windows
environment? I have some ideas for programs but haven't had much luck
finding any programming languages that might be cross platform for the
Mac and IOS devices?
On 07/21/13 00:13, Steve Holmes wrote:
I want to personally thank you for the tips and references you have
offered here. I'm an experienced programmer though I have barely
touched programming with xcode. I have one of those books I recently
bought for introducing iOS programming but I think I would rather
start with something on the Mac first and then move to an iOS
environment. Anyway, there's a bunch to learn here. I'm anxious to
move away from mainframe programming as that has been a dieing
profession for years.
On Jul 6, 2013, at 11:32 AM, Barry Hadder <bhad...@gmail.com> wrote:
First, just to be clear I never have mouse follows vo turned on in
the utility.
Put vo on the unknown and then rout the mouse. Make sure the mouse
is where you want it with vo-f5. If it isn't, some times the
splitters can inter fear so you might need to try moving them
around. Same thing in the header file.
I lock the mouse with shift-vo-command-space then move vo to the
header file. I've noticed that starting in Lion, the mouse follows
vo when the mouse is locked and cursor tracking is on. I have cursor
tracking when I drag to a header file. There are other situations
when you will need to turn it off.
Last but not least, XCode can be buggy. You just have to learn to
deal with it if you use it.
On Jul 6, 2013, at 2:27 AM, Yuma Antoine Decaux <jamy...@gmail.com>
wrote:
Hi Barry,
Just as clarification, when you drag, what state is mouse pointer
on? Do you go to the unknown, vo command shift space with mouse
following voice over cursor, then go to the header file, or do you
first toggle cursor tracking off before moving from unknown to the
header file?
Best regards, and thanks a lot for helping out
"Light has no value without darkness"
On 6/07/2013, at 8:04 AM, Barry Hadder <bhad...@gmail.com> wrote:
There has been some discussion recently in regards to whether or
not one can use Voiceover with Interface builder. I'm not sure that
this list is the most appropriate place for discussing this, but I
feel that there have been some inaccurate assertions made and I
wanted to attempt to clear up a few points for the sate of those
who are programmers on this list and are interested in learning
about developing apps with XCode.
As the subject implies, I am using the tutorial found at
https://developer.apple.com/library/mac/#referencelibrary/GettingStarted/RoadMapOSX/books/RM_YourFirstApp_Mac/Articles/GettingStarted.html#//apple_ref/doc/uid/TP40012262-TP40012101-CH2-SW8.
I realize the IOS is the hottest thing, but I think that this
example is a little cleaner for the purpose of explaining this. It
works the same for the most part for an IOS app and I will point
out the most important differences at the end. I'm also only going
to go over laying out the window and referencing the objects in the
xib in your code. The tutorial explains how to create a project etc.
Make sure that the xib is opened in the source area and that the
utilities are visible with command-option-0.
First, add the controls to the windows content view:
1. With the mainmenu.xib file opened in the source group, make sure
the document outline is visible. You should see a table with all of
the objects in the xib.
2. Find the window object in the table and expand it to expose the
content view.
3. Move vo to the library group, interact, and select the object
library radio button.
4. Find text field, with vo, rout the mouse to vo, and lock the mouse.
5. Move vo to the windows content view in the outline, then release
the mouse. Now the content view should contain the textfield. (Note
that this can be glitchy sometimes and you might have to try it
again but not very often.)
6. Repeat for the slider and button.
Designing the layout:
I'm going to arrange the controls in a column centered in the
window and left justified with the button close to the bottom of
the window.
1. Select the content view and go to the size inspector. Git the
width and height. I have 480 by 360
2. In the xib, select the text field and. In the size inspector,
make sure layout rectangle is selected and select the origin to be
the top left corner.
3. In the origin section, type 20 in the x field and 340 for the y
value. Then stretch it across the window until the right side is 20
points from the right edge by selecting the origin in the top left
corner and typing a value of 440 in the width field. Note that you
could also resize the window to fit the text field, but this is
more simple.
4. Change the origin to the bottom left corner and get the y value.
I have 318.
5. Select the slider and in the size inspector, set the origin to
top left, set the x origin to 20 and the y to 308. That positions
the slider 20 points from the left edge of the window and 10 points
below the textfield.
6. With the button selected, set the origin to bottom left, set x
origin to 20 and the y origin to 20.
You can build an run at this point, but you can also check your
work with out even running the app by choosing "simulate document
in the editor menu. Cocoa simulator will open and you should be
able to move vo up and down through the lined up controls.
Create actions and outlets:
1. Select the AppDelegate object in the outline and open the
assistant editor. In the source pain, you should now see the
appdelegate.h file opened next to the xib.
2. Select the button in the xib file and in the connections
inspector, find the sent actions list.
3. The only item at this point in the list is selector. Move vo to
the unknown item directly to the right of it and drag from it to
the area in the header file between the @interface and @end
directives.
4. When you release the mouse at this point, a connections dialog
will come up where you will type the name of the action.. Type mute
then press ok. In the header file, you will now see the definition
of the action. - (IBAction)mute:(id)sender;
5. Select the text field in the outline and in the connections
inspector, find the referencing outlets list.
6. drag from the unknown thing next to "new referencing outlet" to
a blank area in the class declaration in the header file. In the
connection dialog type textField in the name.
7. Repeat for the slider.
When you are done, you will see the following objective c property
definitions:
@property (weak) IBOutlet NSTextField* textField;
@property (weak) IBOutlet NSSlider* slider;
And that is all there is to it.
One difference I want to point out between UIKit and AppKit is that
the origin in UIKit is in the top left corner of the screen and the
y values grow downward. So to place a control in the top left
corner of a view, the origin in the top left corner of a content
view would be 20x20.
This is a lot harder to right about than it is to do. I hope I
explained it well enough that someone gets something out of it.
However, this wont help anyone who doesn't know how to program in
Objective C.
--
Barry Hadder
bhad...@gmail.com
https://twitter.com/BarryHadder
UnitMaster
Available in the Mac app store.
--
You received this message because you are subscribed to the Google
Groups "MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups "MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups "MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/groups/opt_out.
--
¯\_(ツ)_/¯
--
You received this message because you are subscribed to the Google Groups
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/groups/opt_out.
