Upcoming library release - Google Data APIs Objective-C Client Library Discussion

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Data APIs Objective-C Client Library Discussion
Message from discussion Upcoming library release
Received-SPF: pass (google.com: domain of mr.riddlemef...@gmail.com designates 209.85.216.191 as permitted sender) client-ip=209.85.216.191;
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=reply-to:from:to:references:in-reply-to:subject:date:message-id
         :mime-version:content-type:x-mailer:thread-index:content-language;
        b=npTYHXRruWQmM7m430NtTwpqkXvIbU1Dj9RDQomvMJqpSTscZ6D4Ou4CgcmlTSx8Nk
         1Q5/X0nJSo7gCn9qC1WBCjt0u60SC5W9ZjHoO4/DsCui7B6aVZ8aATmcjBqP+byBTWCl
         1mIs29zO+VyVS0oBnJzmLA1y/2DkXGB62xCYk=
Reply-To: <mr.riddlemef...@gmail.com>
From: "Peter J. MASON" <mr.riddlemef...@gmail.com>
To: <gdata-objectivec-client@googlegroups.com>
References: <74ad61020910191859n36ae22abj8465dd30d3d07...@mail.gmail.com> <4add4d89.9413f30a.7eae.2...@mx.google.com> <74ad61020910200022h48b15416q27a1707d6301c...@mail.gmail.com>
In-Reply-To: <74ad61020910200022h48b15416q27a1707d6301c...@mail.gmail.com>
Subject: RE: Upcoming library release
Date: Tue, 20 Oct 2009 19:41:06 +1100
Message-ID: <4add77b6.9613f30a.042d.2...@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0372_01CA51BD.479AB330"
Thread-Index: AcpRVhJTRJW567K+SZ6KNkciPjMLNAACePfA
Content-language: en-au

This is a multi-part message in MIME format.

------=_NextPart_000_0372_01CA51BD.479AB330
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Greg, I'm assuming that the suggested procedure results in a static lib,
centrally located, and  linked to by several projects, each having their own
project space, sharing referenced headers.  I expect to be concurrently
developing, updates at least, and wouldn't wish to be managing the rebuild
each time of the static lib. Procedurally it would be a big deal if I had
the wrong lib build current then the link would fail and you'd go the lib
project and change things. Raised under "make (I)" and similar, rebuilding a
dependent lib is abit strange for me.

 

I think the next step is to break out, a common lib and several smaller libs
dedicated to the particular service. I don't know if you can do that with a
single XCode project however J That, I could use.

 

From: gdata-objectivec-client@googlegroups.com
[mailto:gdata-objectivec-client@googlegroups.com] On Behalf Of Greg Robbins
Sent: Tuesday, 20 October 2009 6:22 PM
To: gdata-objectivec-client@googlegroups.com
Subject: Re: Upcoming library release

 

There is no danger to defining GDATA_SUPPRESS_INCLUDE_WARNING. You'll just
have a needlessly-large executable size.

But I do not understand why you would not just tailor the static library for
each app to include the minimum set of services required by the app. It
seems like a simple, nearly-free way of reducing your app's code size by
leaving out all the unneeded library code.

Keeping a GData project file or xcode config file unique for each app should
make it easy to use compiler defines to indicate just the code needed for
the app.




------=_NextPart_000_0372_01CA51BD.479AB330
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-AU link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Greg, I&#8217;m assuming that the suggested procedure =
results in
a static lib, centrally located, and &nbsp;linked to by several =
projects, each
having their own project space, sharing referenced headers. &nbsp;I =
expect to
be concurrently developing, updates at least, and wouldn&#8217;t wish to =
be
managing the rebuild each time of the static lib. Procedurally it would =
be a
big deal if I had the wrong lib build current then the link would fail =
and you&#8217;d
go the lib project and change things. Raised under &#8220;make =
(I)&#8221; and similar,
rebuilding a dependent lib is abit strange for me.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I think the next step is to break out, a common lib and =
several
smaller libs dedicated to the particular service. I don&#8217;t know if =
you can
do that with a single XCode project however </span><span =
style=3D'font-size:11.0pt;
font-family:Wingdings;color:#1F497D'>J</span><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> That, I could =
use.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm =
0cm 4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

<p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> =
gdata-objectivec-client@googlegroups.com
[mailto:gdata-objectivec-client@googlegroups.com] <b>On Behalf Of =
</b>Greg
Robbins<br>
<b>Sent:</b> Tuesday, 20 October 2009 6:22 PM<br>
<b>To:</b> gdata-objectivec-client@googlegroups.com<br>
<b>Subject:</b> Re: Upcoming library release<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>There is no danger =
to defining
GDATA_SUPPRESS_INCLUDE_WARNING. You'll just have a needlessly-large =
executable
size.<br>
<br>
But I do not understand why you would not just tailor the static library =
for
each app to include the minimum set of services required by the app. It =
seems
like a simple, nearly-free way of reducing your app's code size by =
leaving out
all the unneeded library code.<br>
<br>
Keeping a GData project file or xcode config file unique for each app =
should
make it easy to use compiler defines to indicate just the code needed =
for the
app.<br>
<br>
<o:p></o:p></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_0372_01CA51BD.479AB330--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
