Have you looked at the gdata-apis
(http://code.google.com/apis/gdata/)? Once your app is running on GAE
you can access spreadsheets stored in Google Docs using the gdata
libs. Of course, depending on your app, it may be easier to directly
use the datastore instead of a spreadsheet.
It is very hard to say anything about what your app may cost to run
on GAE. Also don't forget the pricing will soon be changing, no one
yet knows how it will change things (other than becoming more
expensive).
Robert
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/dbBcc3ZF4HoJ.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/dbBcc3ZF4HoJ.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Seriously though, I came from a C with some C++ and C# background.
The lack of braces and semicolons was hard to accept at first. What I
can tell you for sure is that when I write C-type language code now
all I can think is "what is with the unnecessary markup?!" It is
crazy nice to work in, once you get past a few nuances.
Not to throw our more flame-bait, but I also agree with your choice
to skip django. Use webapp, or webapp2
(http://code.google.com/p/webapp-improved/). Personally I'd also
suggest finding another template language too, but that is personal
preference.
I'm not sure if you've got some specific tool in mind, but you can
create what ever API you might need for interacting with your data.
There is also the bulkloader tool to upload / fetch data.
Robert
On Wed, Aug 10, 2011 at 16:11, Joshua Mulloy <jmu...@sau4.org> wrote:
> I definitely agree with you on the python vs c markup.
> I just came back to post on my progress and read your post. After reading
> your post, I am not sure I made the right decision (actually using more of
> the Django framework). You sound very opposed to Django. If you are
> willing to share, I would be very interested in your reasons. I found
I'm not necessarily personally opposed to it, but it carries overhead
which does not always play well on app engine. It is also very heavy
and I find it rather monolithic. I personally prefer lighter, smaller
frameworks.
> Django-nonrel and two things made me decide to use the model framework.
> First, I really liked the Model syntax. I think it was easier for me to
> understand because they provided the related SQL code in their
> book http://www.djangobook.com/en/2.0/chapter05/. I was very frustrated by
> the lack of comparison examples in Programming Google App Engine. For
> example, instead of just mentioning (page 197) "This technique is similar to
> how you'd use 'join tables' in an SQL database." an actual mapped example
> would probably have made that entire chapter immediately mentally
> digestible.
The problem with App Engine is that you'll get into trouble by
thinking in terms of SQL. It is not SQL, and your *really* should try
to not think in SQL-like terms. Instead think simple data structures
and denormalize the hell out of stuff, precisely the opposite of
typical RDMS thinking.
> Second, I like that I can take the code and plop it somewhere else if
> necessary. I got burned from an unexpected limitation in GAS. If I run
> into another road block with GAE, I can take my code and run it on my server
> here with minor adjustment to the code.
Yeah, that is a bummer. Luckily most of your code will probably be
pretty portable no matter what you choose, worst case you might need
to implement a thin datastore abstraction layer. Or you could use
TyphoonAE!
> I have basically setup the data model for my app and the Django admin
> interface already has at least as much functionality as the old app. In
> looking at it, I could probably just put that up and give out one login and
> volunteers could start entering data (basically what they had before but
> needed a client). Then I could start "adding" features like:
> users inputting their own data instead of volunteers copying it from a paper
> form. There is still a ton I need to do and better understand. But now, I
> at least have an interface I can show to the PD committee and my boss and
> that is a big relief. I now have a bit more time to plan and consider
> alternatives, time I didn't think I would have this morning.
Honestly, I can't argue with results.
Nice to hear you chose Python. :)
Robert
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/IyyYM6sSoHcJ.
Robert