Re: [OT] Forums for Web Development?

2016-02-15 Thread Michael David Crawford 
Soylent News, http://soylentnews.org/

Submit an "Ask Soylent News" story.  If you ask your questions
intelligently they'll run your story.  Many Soylentils are web app
coders.
Michael David Crawford, Baritone
mdcrawf...@gmail.com

  One Must Not Trifle With Wizards For It Makes Us Soggy And Hard To Light.


On Mon, Feb 15, 2016 at 3:57 PM, David Delmonte  wrote:
> Have you tried StackOverflow? They have sister (brother?) forums, including 
> one for web masters. I think SO would be a good place to scout around.. The 
> second for me is YouTube/Vimeo. If you don’t minding learning from teenagers, 
> it can be quite helpful.
>
> David
>
> On Feb 15, 2016, at 6:43 PM, John Bartleson  wrote:
>
> After getting many great tips from this list over the years, I find myself 
> needing to switch gears and do some web development. I'm starting on a 
> server-based app that will be the front end to a SQL database that may grow 
> to be very large. Although it's easy to find info on the basic technologies 
> to be used in such an app (PHP, Javascript, HTML, SQL, AJAX, etc.), there 
> seems to be little written about how to front-end a large multi-server 
> database.
>
> So I'm looking for a forum where I can ask noob questions about large website 
> development. Apple (understandably) doesn't appear to have a list for this. 
> Can anybody here point to info sources such as forums, books, websites, etc.? 
> TIA
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/ddelmonte%40mac.com
>
> This email sent to ddelmo...@mac.com
>
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/mdcrawford%40gmail.com
>
> This email sent to mdcrawf...@gmail.com

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: [OT] Forums for Web Development?

2016-02-15 Thread David Delmonte 
Have you tried StackOverflow? They have sister (brother?) forums, including one 
for web masters. I think SO would be a good place to scout around.. The second 
for me is YouTube/Vimeo. If you don’t minding learning from teenagers, it can 
be quite helpful.

David

On Feb 15, 2016, at 6:43 PM, John Bartleson  wrote:

After getting many great tips from this list over the years, I find myself 
needing to switch gears and do some web development. I'm starting on a 
server-based app that will be the front end to a SQL database that may grow to 
be very large. Although it's easy to find info on the basic technologies to be 
used in such an app (PHP, Javascript, HTML, SQL, AJAX, etc.), there seems to be 
little written about how to front-end a large multi-server database.

So I'm looking for a forum where I can ask noob questions about large website 
development. Apple (understandably) doesn't appear to have a list for this. Can 
anybody here point to info sources such as forums, books, websites, etc.? TIA
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/ddelmonte%40mac.com

This email sent to ddelmo...@mac.com


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: ScalableUserInterface.framework

2016-02-15 Thread Raglan T. Tiger 



> On Feb 15, 2016, at 4:35 PM, Uli Kusterer  
> wrote:
> 
> Wildly guessing here:

I went back to 10.9 sdk and it links.

 I do not link with QuartzCore just Quartz.

In the Build Phases of the target settings is where I pick frameworks and libs 
tolling with so what ever Xcode is pointing me to their is what i used ... and 
these are in System/Library/Frameworks



___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

[OT] Forums for Web Development?

2016-02-15 Thread John Bartleson 
After getting many great tips from this list over the years, I find myself 
needing to switch gears and do some web development. I'm starting on a 
server-based app that will be the front end to a SQL database that may grow to 
be very large. Although it's easy to find info on the basic technologies to be 
used in such an app (PHP, Javascript, HTML, SQL, AJAX, etc.), there seems to be 
little written about how to front-end a large multi-server database.

So I'm looking for a forum where I can ask noob questions about large website 
development. Apple (understandably) doesn't appear to have a list for this. Can 
anybody here point to info sources such as forums, books, websites, etc.? TIA
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: ScalableUserInterface.framework

2016-02-15 Thread Uli Kusterer 
On 15 Feb 2016, at 23:53, Raglan T. Tiger  wrote:
> A target that has been building suddenly throws a link error:
> 
> ld: file not found: 
> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableUserInterface.framework/Versions/A/ScalableUserInterface
>  for architecture i386
> 
> Other targets in the project build jus fine linking the same frameworks.
> 
> Any help would be most appreciated.
> 
> (Yes, I know this is a Cocoa list, but this is where the smart people are to 
> be found!)

Wildly guessing here:

Are you actually explicitly linking against ScalableUserInterface? You should 
really only be linking against QuartzCore, not any of the embedded frameworks.

Alternately, are you really linking against the framework in 
/System/Library/Frameworks? You should really be linking against the framework 
from the SDK.

Finally, did you just update Xcode or change the SDK? Maybe the current SDK is 
now 64-bit only, but your app is still 32/64, and so it won't link because it 
can't find the 32-bit linking info anymore.

Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://stacksmith.org





___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

ScalableUserInterface.framework

2016-02-15 Thread Raglan T. Tiger 
A target that has been building suddenly throws a link error:

ld: file not found: 
/System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableUserInterface.framework/Versions/A/ScalableUserInterface
 for architecture i386



Other targets in the project build jus fine linking the same frameworks.

Any help would be most appreciated.

(Yes, I know this is a Cocoa list, but this is where the smart people are to be 
found!)





-rags



___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Secure coding NSArray

2016-02-15 Thread Quincey Morris 
On Feb 15, 2016, at 09:44 , Quincey Morris 
 wrote:
> 
>>  [archiver encodeObject: model forKey: @"model"];

Oh, in the test project that I pasted this code from, I used “model” as my root 
object key. In the real project, I’m using NSKeyedArchiveRootObjectKey, which 
seems like a better choice, since it should be backwards compatible with 
non-secure archiving that uses the convenience methods where you don’t specify 
a root object key explicitly.

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Secure coding NSArray

2016-02-15 Thread Quincey Morris 
On Feb 15, 2016, at 03:43 , Dave  wrote:
> 
> Do you know if same thing applies to dictionaries as well as arrays?


In the project that got me started on this, I don’t yet have any dictionaries, 
so I don’t know. But I would assume so.

On Feb 15, 2016, at 04:34 , Michael Starke 
 wrote:
> 
> I am unable to reproduce your exception. Is this something related to swift 
> interoperability? In pure objective-c environments it seems to work fine, 
> that is, securely decode without an exception!

There is some other magic-incantation stuff that’s needed to turn on secure 
archiving. Here’s the code I was using for archiving:

>   NSMutableData* data = [NSMutableData data];
>   NSKeyedArchiver* archiver = [[NSKeyedArchiver alloc] 
> initForWritingWithMutableData: data];
>   archiver.requiresSecureCoding = YES;
>   
>   [archiver encodeObject: model forKey: @"model"];
>   [archiver finishEncoding];

or in Swift:

>   let data = NSMutableData ()
>   let archiver = NSKeyedArchiver (forWritingWithMutableData: data)
>   archiver.requiresSecureCoding = true
>   
>   archiver.encodeObject (model, forKey: "model")
>   archiver.finishEncoding ()

and for unarchiving:

>   NSKeyedUnarchiver* unarchiver = [[NSKeyedUnarchiver alloc] 
> initForReadingWithData: data];
>   unarchiver.requiresSecureCoding = YES;
>   
>   model = [unarchiver decodeTopLevelObjectOfClass: [AllContainers class] 
> forKey: @"model" error: outError];

or in Swift:

>   let unarchiver = NSKeyedUnarchiver (forReadingWithData: data)
>   unarchiver.requiresSecureCoding = true
>   
>   do {
>   model = try unarchiver.decodeTopLevelObjectOfClass 
> (AllContainers.self, forKey: "model")!
>   }
>   catch let error as NSError { // Without this re-throw, the error is 
> converted to a plain ErrorType, which discards the userInfo dict where the 
> localized error is stored
>   throw error
>   }

You have to create an archiver/unarchiver manually, in order to tell it to use 
secure coding. Otherwise, ‘decodeObjectOfClass:forKey:’ (is documented to) 
decode without producing any errors. Separately, ‘decodeTopLevelObjectOfClass’ 
has the magic side effect of causing the unarchiving process to change to 
support proper error handling. The rest of the ‘decode…’ methods work the same, 
but you can use ‘failWithError:’ while decoding to generate an error which 
magically tunnels up to the top level. There’s way too much magic here, IMO.

So, my guess is that you didn’t actually turn secure coding on, and therefore 
didn’t get any errors. However, the entire process is so obscure, and obscurely 
documented, that you may have found an alternate route to get it working.

For completeness, I’ll add that every class which supports secure coding and 
has an initWithCoder: method must also implement the ‘supportsSecureCoding’ 
class property and return YES/true, overriding the super implementation if it 
exists. It’s not allowable to inherit the superclass property.

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Secure coding NSArray

2016-02-15 Thread Michael Starke 
Hi Quincey,

I am unable to reproduce your exception. Is this something related to swift 
interoperability? In pure objective-c environments it seems to work fine, that 
is, securely decode without an exception!

- Michael

> On 15 Feb 2016, at 12:43, Dave  wrote:
> 
> Hi Quincey,
> 
> Thank you so much for the "heads-up" on this, I will be changing my App to 
> use Secure Coding in the new future and it’s littered with NSArrays and 
> NSDictionary properties. 
> 
> Do you know if same thing applies to dictionaries as well as arrays?
> 
> All the Best
> Dave
> 
>> On 14 Feb 2016, at 08:45, Quincey Morris 
>>  wrote:
>> 
>> I might be late to this party, but since I just spent hours on it, I’ll 
>> document this for anyone who hasn’t run into it yet.
>> 
>> If you’re using NSSecureCoding, there’s a problem decoding NSArray objects. 
>> You can’t use this:
>> 
>>  myArray = [coder decodeObjectForKey: @“myArray”];
>> 
>> and you can’t use this:
>> 
>>  myArray = [coder decodeObjectOfClass: [NSArray class] forKey: 
>> @“myArray”];
>> 
>> The error message in the resulting exception won’t be very helpful, but it 
>> means that the class of the array elements is invalid. What you actually 
>> need to do is this:
>> 
>>  myArray = [coder decodeObjectOfClasses: [NSSet setWithObjects: [NSArray 
>> class], [MyElementClass class], nil] forKey: @“myArray”];
>> 
>> Besides being obscure, this is also semantically incorrect, in that it 
>> appears to allow decoding of objects that are not strictly arrays of 
>> MyElementClass objects. (I guess this is not a security violation, since it 
>> doesn’t permit an attack to substitute objects of arbitrary classes, but it 
>> sure is annoying.]
>> 
>> Now, if you want to do this in Swift, you might be tempted to try the 
>> obvious translation:
>> 
>>  let classes = Set (arrayLiteral: [… anything here… ])
>>  let myArray = coder.decodeObjectOfClasses (classes, forKey: “myArray”)
>> 
>> but that won’t work because AnyClass isn’t Hashable. So you might try (well, 
>> I tried) something like this:
>> 
>>  let classes = Set (arrayLiteral: [NSArray.self, 
>> MyElementClass.self])
>>  let myArray = coder.decodeObjectOfClasses (classes, forKey: “myArray”)
>> 
>> This compiles, but it fails at run-time, with a message saying it found an 
>> object of class ‘NSArray’, but only objects of classes ‘NSArray’ and 
>> ‘MyElementClass’ are allowed. (!)
>> 
>> The solution is to fall back to an explicit NSSet object:
>> 
>>  let classes = NSSet (objects: NSArray.self, MyElementClass.self)
>>  let myArray = coder.decodeObjectOfClasses (classes, forKey: “myArray”)
>> 
>> There really needs to be (radar #24646135) API to decode a NSArray and 
>> specify the class (or classes) of the elements. In Obj-C, something like:
>> 
>>  myArray = [coder decodeArrayWithObjectsOfClass: [MyElementClass class] 
>> forKey: @“myArray”];
>> 
>> or in Swift:
>> 
>>  let myArray = coder.decodeArrayWithObjectsOfClass (MyElementClass.self, 
>> forKey: “myArray”)
>> 
>> This would be particular useful in Swift, because it would give you 
>> compile-time checking of the types in the assignment. (There is already a 
>> Swift-only version of ‘decodeObjectOfClass’ that’s generic, so you get  the 
>> “correct” return type.)
>> 
>> 
>> 
>> ___
>> 
>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>> 
>> Please do not post admin requests or moderator comments to the list.
>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>> 
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/cocoa-dev/dave%40looktowindward.com
>> 
>> This email sent to d...@looktowindward.com
> 
> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/michael.starke%40hicknhack-software.com
> 
> This email sent to michael.sta...@hicknhack-software.com


___m i c h a e l   s t a r k e 
   geschäftsführer
   HicknHack Software GmbH
   www.hicknhack-software.com
   
___k o n t a k t
   +49 (170) 3686136
   cont...@hicknhack.com
   
___H i c k n H a c k   S o f t w a r e   G m b H
   geschäftsführer - maik lathan | andreas reischuck | michael starke
   bayreuther straße 32
   01187 dresden
   amtsgericht dresden HRB 30351
   sitz - dresden


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

Re: Secure coding NSArray

2016-02-15 Thread Dave 
Hi Quincey,

Thank you so much for the "heads-up" on this, I will be changing my App to use 
Secure Coding in the new future and it’s littered with NSArrays and 
NSDictionary properties. 

Do you know if same thing applies to dictionaries as well as arrays?

All the Best
Dave

> On 14 Feb 2016, at 08:45, Quincey Morris 
>  wrote:
> 
> I might be late to this party, but since I just spent hours on it, I’ll 
> document this for anyone who hasn’t run into it yet.
> 
> If you’re using NSSecureCoding, there’s a problem decoding NSArray objects. 
> You can’t use this:
> 
>   myArray = [coder decodeObjectForKey: @“myArray”];
> 
> and you can’t use this:
> 
>   myArray = [coder decodeObjectOfClass: [NSArray class] forKey: 
> @“myArray”];
> 
> The error message in the resulting exception won’t be very helpful, but it 
> means that the class of the array elements is invalid. What you actually need 
> to do is this:
> 
>   myArray = [coder decodeObjectOfClasses: [NSSet setWithObjects: [NSArray 
> class], [MyElementClass class], nil] forKey: @“myArray”];
> 
> Besides being obscure, this is also semantically incorrect, in that it 
> appears to allow decoding of objects that are not strictly arrays of 
> MyElementClass objects. (I guess this is not a security violation, since it 
> doesn’t permit an attack to substitute objects of arbitrary classes, but it 
> sure is annoying.]
> 
> Now, if you want to do this in Swift, you might be tempted to try the obvious 
> translation:
> 
>   let classes = Set (arrayLiteral: [… anything here… ])
>   let myArray = coder.decodeObjectOfClasses (classes, forKey: “myArray”)
> 
> but that won’t work because AnyClass isn’t Hashable. So you might try (well, 
> I tried) something like this:
> 
>   let classes = Set (arrayLiteral: [NSArray.self, 
> MyElementClass.self])
>   let myArray = coder.decodeObjectOfClasses (classes, forKey: “myArray”)
> 
> This compiles, but it fails at run-time, with a message saying it found an 
> object of class ‘NSArray’, but only objects of classes ‘NSArray’ and 
> ‘MyElementClass’ are allowed. (!)
> 
> The solution is to fall back to an explicit NSSet object:
> 
>   let classes = NSSet (objects: NSArray.self, MyElementClass.self)
>   let myArray = coder.decodeObjectOfClasses (classes, forKey: “myArray”)
> 
> There really needs to be (radar #24646135) API to decode a NSArray and 
> specify the class (or classes) of the elements. In Obj-C, something like:
> 
>   myArray = [coder decodeArrayWithObjectsOfClass: [MyElementClass class] 
> forKey: @“myArray”];
> 
> or in Swift:
> 
>   let myArray = coder.decodeArrayWithObjectsOfClass (MyElementClass.self, 
> forKey: “myArray”)
> 
> This would be particular useful in Swift, because it would give you 
> compile-time checking of the types in the assignment. (There is already a 
> Swift-only version of ‘decodeObjectOfClass’ that’s generic, so you get  the 
> “correct” return type.)
> 
> 
> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dave%40looktowindward.com
> 
> This email sent to d...@looktowindward.com


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com