[google-appengine] Re: What's the difference among key, id, and key name?
When you create entities, you have the option of specifying a unique key name that you can use to reference these entities directly (e.g. retrieving entities without queries, thereby improving the performance of your application). I'm not sure what you mean by this. Are you saying if I know enough to reconstruct the full key name of an instance I want to retrieve I can instantiate the model with that key name and then start using it directly? In other words, I know that when I create these instances I use some_string + owner model name + something else as the key name, so if I'm in some other situation where I know all those values I can easily rebuild the key name and start using the model without having to run a query on the datastore? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Creating a filter using google api
What is a filter in this context? Is this a Java thing? I've been listening in on the group conversation as a python developer. I'm not following you guys. Thanks Stu On May 12, 4:08 pm, niklasr nik...@montao.com.br wrote: On May 11, 6:13 am, Nikhar nikhar...@gmail.com wrote: Hi I wanna create a filter and add it to my application using an google api can some help me with it i have reached up to some extent bt can't make it display .. easiest way is fork an existing project, then either filter according to inequality or equality by your choice, implementation preferred is either python or java though the most trivial app should be possible, if it'd be up2me, with nothing but yaml, for minimalism. i learnt many things from srv.appspot.com whose sources are public gae-services- examples.googlecode.com best wishes NiklasR --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: New Blog About GAE
Thanks for the heads up. I've subscribed to hear more. Stu On Mar 31, 5:23 pm, pfisk peter.f...@gmail.com wrote: Hello, I have started a new Blog discussing a new Website that will be deployed in April. The site uses GXT for the user interface, Google's Application Engine for the server and Scheme running in the browser as it's scripting language. The blog will describe the development and deployment of the site. http://wisperweb.wordpress.com/ Cheers, -- Peter Fisk --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: App Engine Patch - dumpdata then loaddata
Alright, I think I optimistically read Waldemars note about how DateTimeProperty was the only property that is supported. I'll shelf this for now. I'll take a stab at this at implementing the other properties at some point soon. Stu On Mar 24, 7:45 pm, Big Stu stu.dohe...@gmail.com wrote: Looks like this BadValueError is happening when the deserializer tries to parse the data field of the sessions.session model. On Mar 24, 7:30 pm, Big Stu stu.dohe...@gmail.com wrote: So, I editing the django1.0/core/serializers/python.py file to have the changes mentioned in Issue 70 for Google App Engine Helper, and I'm not getting this error: Installing json fixture 'data' from absolute path. Problem installing fixture 'data.json': Traceback (most recent call last): File /home/sadohert/development/google_ae/leagr_patch/common/zip- packages/django-1.0.2.zip/django/core/management/commands/ loaddata.py, line 116, in handle for obj in objects: File /home/sadohert/development/google_ae/leagr_patch/common/zip- packages/django-1.0.2.zip/django/core/serializers/json.py, line 41, in Deserializer for obj in PythonDeserializer(simplejson.load(stream)): File /home/sadohert/development/google_ae/leagr_patch/common/zip- packages/django-1.0.2.zip/django/core/serializers/python.py, line 119, in Deserializer data[field.name] = field.validate(field_value) File /home/sadohert/development/google_ae/google_appengine/google/ appengine/ext/db/__init__.py, line 1910, in validate 'to a Blob instance (%s)' % (self.name, err)) BadValueError: Property data must be convertible to a Blob instance (Blob() argument should be str instance, not unicode) Could there be something wrong with my setup? Otherwise I would think there would have been many complaints about this issue already. On Mar 24, 12:42 pm, Big Stu stu.dohe...@gmail.com wrote: I just found out how insanely easy it is to open, edit, and save a file within a zip file under vim. I came across it on this link: http://blog.vorpal.cc/category/linux/vim-can-open-zip-files.html On Mar 24, 12:34 pm, Big Stu stu.dohe...@gmail.com wrote: I'm working with the most recent GAE Patch but still seem to have the problem. This issue here with GAE-Helper describes what I'm seeing exactly: Issue 70: Deserializer does not decode datetime fields properlyhttp://code.google.com/p/google-app-engine-django/issues/detail?id=70 Is there any convenient way I can setup my development environment so django is used in its unzipped form? This way I can edit pieces and see if that solves my problem, without having to unzip django1.0, make the edit, and rezip? Thanks Stu On Mar 21, 7:08 am, Waldemar Kornewald wkornew...@gmail.com wrote: On Mar 20, 3:31 pm, Big Stu stu.dohe...@gmail.com wrote: Hi Waldemar, Thanks for following up, and thanks for all your hard work with App Engine Patch. I'm having a lot of fun learning about app engine and django in my spare time, and hope to one day move my full time career into this stuff. Django, GAE, and your stuff will have a huge hand in that. Anyway, the property I'm tryign to dump is DateTimeProperty: date = db.DateTimeProperty() That should work with the repository version. Bye, Waldemar Kornewald --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: App Engine Patch - dumpdata then loaddata
I'm working with the most recent GAE Patch but still seem to have the problem. This issue here with GAE-Helper describes what I'm seeing exactly: Issue 70:Deserializer does not decode datetime fields properly http://code.google.com/p/google-app-engine-django/issues/detail?id=70 Is there any convenient way I can setup my development environment so django is used in its unzipped form? This way I can edit pieces and see if that solves my problem, without having to unzip django1.0, make the edit, and rezip? Thanks Stu On Mar 21, 7:08 am, Waldemar Kornewald wkornew...@gmail.com wrote: On Mar 20, 3:31 pm, Big Stu stu.dohe...@gmail.com wrote: Hi Waldemar, Thanks for following up, and thanks for all your hard work with App Engine Patch. I'm having a lot of fun learning about app engine and django in my spare time, and hope to one day move my full time career into this stuff. Django, GAE, and your stuff will have a huge hand in that. Anyway, the property I'm tryign to dump is DateTimeProperty: date = db.DateTimeProperty() That should work with the repository version. Bye, Waldemar Kornewald --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: App Engine Patch - dumpdata then loaddata
I just found out how insanely easy it is to open, edit, and save a file within a zip file under vim. I came across it on this link: http://blog.vorpal.cc/category/linux/vim-can-open-zip-files.html On Mar 24, 12:34 pm, Big Stu stu.dohe...@gmail.com wrote: I'm working with the most recent GAE Patch but still seem to have the problem. This issue here with GAE-Helper describes what I'm seeing exactly: Issue 70: Deserializer does not decode datetime fields properlyhttp://code.google.com/p/google-app-engine-django/issues/detail?id=70 Is there any convenient way I can setup my development environment so django is used in its unzipped form? This way I can edit pieces and see if that solves my problem, without having to unzip django1.0, make the edit, and rezip? Thanks Stu On Mar 21, 7:08 am, Waldemar Kornewald wkornew...@gmail.com wrote: On Mar 20, 3:31 pm, Big Stu stu.dohe...@gmail.com wrote: Hi Waldemar, Thanks for following up, and thanks for all your hard work with App Engine Patch. I'm having a lot of fun learning about app engine and django in my spare time, and hope to one day move my full time career into this stuff. Django, GAE, and your stuff will have a huge hand in that. Anyway, the property I'm tryign to dump is DateTimeProperty: date = db.DateTimeProperty() That should work with the repository version. Bye, Waldemar Kornewald --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: App Engine Patch - dumpdata then loaddata
So, I editing the django1.0/core/serializers/python.py file to have the changes mentioned in Issue 70 for Google App Engine Helper, and I'm not getting this error: Installing json fixture 'data' from absolute path. Problem installing fixture 'data.json': Traceback (most recent call last): File /home/sadohert/development/google_ae/leagr_patch/common/zip- packages/django-1.0.2.zip/django/core/management/commands/ loaddata.py, line 116, in handle for obj in objects: File /home/sadohert/development/google_ae/leagr_patch/common/zip- packages/django-1.0.2.zip/django/core/serializers/json.py, line 41, in Deserializer for obj in PythonDeserializer(simplejson.load(stream)): File /home/sadohert/development/google_ae/leagr_patch/common/zip- packages/django-1.0.2.zip/django/core/serializers/python.py, line 119, in Deserializer data[field.name] = field.validate(field_value) File /home/sadohert/development/google_ae/google_appengine/google/ appengine/ext/db/__init__.py, line 1910, in validate 'to a Blob instance (%s)' % (self.name, err)) BadValueError: Property data must be convertible to a Blob instance (Blob() argument should be str instance, not unicode) Could there be something wrong with my setup? Otherwise I would think there would have been many complaints about this issue already. On Mar 24, 12:42 pm, Big Stu stu.dohe...@gmail.com wrote: I just found out how insanely easy it is to open, edit, and save a file within a zip file under vim. I came across it on this link: http://blog.vorpal.cc/category/linux/vim-can-open-zip-files.html On Mar 24, 12:34 pm, Big Stu stu.dohe...@gmail.com wrote: I'm working with the most recent GAE Patch but still seem to have the problem. This issue here with GAE-Helper describes what I'm seeing exactly: Issue 70: Deserializer does not decode datetime fields properlyhttp://code.google.com/p/google-app-engine-django/issues/detail?id=70 Is there any convenient way I can setup my development environment so django is used in its unzipped form? This way I can edit pieces and see if that solves my problem, without having to unzip django1.0, make the edit, and rezip? Thanks Stu On Mar 21, 7:08 am, Waldemar Kornewald wkornew...@gmail.com wrote: On Mar 20, 3:31 pm, Big Stu stu.dohe...@gmail.com wrote: Hi Waldemar, Thanks for following up, and thanks for all your hard work with App Engine Patch. I'm having a lot of fun learning about app engine and django in my spare time, and hope to one day move my full time career into this stuff. Django, GAE, and your stuff will have a huge hand in that. Anyway, the property I'm tryign to dump is DateTimeProperty: date = db.DateTimeProperty() That should work with the repository version. Bye, Waldemar Kornewald --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: App Engine Patch - dumpdata then loaddata
So, I editing the django1.0/core/serializers/python.py file to have the changes mentioned in Issue 70 for Google App Engine Helper, and I'm not getting this error: Installing json fixture 'data' from absolute path. Problem installing fixture 'data.json': Traceback (most recent call last): File /home/sadohert/development/google_ae/leagr_patch/common/zip- packages/django-1.0.2.zip/django/core/management/commands/ loaddata.py, line 116, in handle for obj in objects: File /home/sadohert/development/google_ae/leagr_patch/common/zip- packages/django-1.0.2.zip/django/core/serializers/json.py, line 41, in Deserializer for obj in PythonDeserializer(simplejson.load(stream)): File /home/sadohert/development/google_ae/leagr_patch/common/zip- packages/django-1.0.2.zip/django/core/serializers/python.py, line 119, in Deserializer data[field.name] = field.validate(field_value) File /home/sadohert/development/google_ae/google_appengine/google/ appengine/ext/db/__init__.py, line 1910, in validate 'to a Blob instance (%s)' % (self.name, err)) BadValueError: Property data must be convertible to a Blob instance (Blob() argument should be str instance, not unicode) Could there be something wrong with my setup? Otherwise I would think there would have been many complaints about this issue already. On Mar 24, 12:42 pm, Big Stu stu.dohe...@gmail.com wrote: I just found out how insanely easy it is to open, edit, and save a file within a zip file under vim. I came across it on this link: http://blog.vorpal.cc/category/linux/vim-can-open-zip-files.html On Mar 24, 12:34 pm, Big Stu stu.dohe...@gmail.com wrote: I'm working with the most recent GAE Patch but still seem to have the problem. This issue here with GAE-Helper describes what I'm seeing exactly: Issue 70: Deserializer does not decode datetime fields properlyhttp://code.google.com/p/google-app-engine-django/issues/detail?id=70 Is there any convenient way I can setup my development environment so django is used in its unzipped form? This way I can edit pieces and see if that solves my problem, without having to unzip django1.0, make the edit, and rezip? Thanks Stu On Mar 21, 7:08 am, Waldemar Kornewald wkornew...@gmail.com wrote: On Mar 20, 3:31 pm, Big Stu stu.dohe...@gmail.com wrote: Hi Waldemar, Thanks for following up, and thanks for all your hard work with App Engine Patch. I'm having a lot of fun learning about app engine and django in my spare time, and hope to one day move my full time career into this stuff. Django, GAE, and your stuff will have a huge hand in that. Anyway, the property I'm tryign to dump is DateTimeProperty: date = db.DateTimeProperty() That should work with the repository version. Bye, Waldemar Kornewald --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: App Engine Patch - dumpdata then loaddata
Looks like this BadValueError is happening when the deserializer tries to parse the data field of the sessions.session model. On Mar 24, 7:30 pm, Big Stu stu.dohe...@gmail.com wrote: So, I editing the django1.0/core/serializers/python.py file to have the changes mentioned in Issue 70 for Google App Engine Helper, and I'm not getting this error: Installing json fixture 'data' from absolute path. Problem installing fixture 'data.json': Traceback (most recent call last): File /home/sadohert/development/google_ae/leagr_patch/common/zip- packages/django-1.0.2.zip/django/core/management/commands/ loaddata.py, line 116, in handle for obj in objects: File /home/sadohert/development/google_ae/leagr_patch/common/zip- packages/django-1.0.2.zip/django/core/serializers/json.py, line 41, in Deserializer for obj in PythonDeserializer(simplejson.load(stream)): File /home/sadohert/development/google_ae/leagr_patch/common/zip- packages/django-1.0.2.zip/django/core/serializers/python.py, line 119, in Deserializer data[field.name] = field.validate(field_value) File /home/sadohert/development/google_ae/google_appengine/google/ appengine/ext/db/__init__.py, line 1910, in validate 'to a Blob instance (%s)' % (self.name, err)) BadValueError: Property data must be convertible to a Blob instance (Blob() argument should be str instance, not unicode) Could there be something wrong with my setup? Otherwise I would think there would have been many complaints about this issue already. On Mar 24, 12:42 pm, Big Stu stu.dohe...@gmail.com wrote: I just found out how insanely easy it is to open, edit, and save a file within a zip file under vim. I came across it on this link: http://blog.vorpal.cc/category/linux/vim-can-open-zip-files.html On Mar 24, 12:34 pm, Big Stu stu.dohe...@gmail.com wrote: I'm working with the most recent GAE Patch but still seem to have the problem. This issue here with GAE-Helper describes what I'm seeing exactly: Issue 70: Deserializer does not decode datetime fields properlyhttp://code.google.com/p/google-app-engine-django/issues/detail?id=70 Is there any convenient way I can setup my development environment so django is used in its unzipped form? This way I can edit pieces and see if that solves my problem, without having to unzip django1.0, make the edit, and rezip? Thanks Stu On Mar 21, 7:08 am, Waldemar Kornewald wkornew...@gmail.com wrote: On Mar 20, 3:31 pm, Big Stu stu.dohe...@gmail.com wrote: Hi Waldemar, Thanks for following up, and thanks for all your hard work with App Engine Patch. I'm having a lot of fun learning about app engine and django in my spare time, and hope to one day move my full time career into this stuff. Django, GAE, and your stuff will have a huge hand in that. Anyway, the property I'm tryign to dump is DateTimeProperty: date = db.DateTimeProperty() That should work with the repository version. Bye, Waldemar Kornewald --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Charging for you app.
I'm not absolutely sure myself (I haven't read the terms yet either), but from some of the previous questions/answers I've seen on here it sounds like you're good to go. Good luck! Stu On Mar 19, 10:38 am, Ronn Ross ronn.r...@gmail.com wrote: If I create an app in gae. Can I charge people for use. I didn't fully read term of use. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Dynamic Code Within Templates
If I understand you correctly you should be fine. You'd have a
base.html template with a {% block %} for your navigation, and then a
separate {%block%} for your content. In the navigation block you'd
use some dictionary entry (e.g., navbar_dict) to populate your various
entries in the navigation bar. Then whenever you render some child
template that inherits from the base.html template you need to make
sure you pass that navbar_dict element as well as any other dictionary
elements needed by the child template, and the navbar block should
pick up on those values and render appropriately.
On Mar 19, 3:31 am, dicko d...@mothdesign.com.au wrote:
Hi there
Just wondering if there is a way to dynamically include content from
within a global template like index.html. I'm hoping to serve
navigation elements from the database to this template while rendering
page specific content through another template. Does this make sense?
If there isn't a method to achieve this, could I use something like
URL Fetch to achieve the same objective or is this a really bad idea?
thanks heaps.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---
[google-appengine] Re: Datastore newbie question
I'm guessing you're just getting your app off the ground and you're referring to some test data you want to play with? You have datastore data available to your application after your application puts some in there itself. So you'd have your application running on the server (local development, or the full production google setup), and forming instances of db Models and calling the various datastore operations on those models is what puts your data into the datastore. This is done through the logic of your application. For example, someone hits your link for registration, which gives them a form in their browser to fill out personal data. When they hit submit your browser hits the app engine server with a particularly formed link. The app server uses that link to figure out which view handler to call and sends the form data to that handler. The View handler then takes that data and puts it into a db.Model (e.g., User). Then the view handler calls put on that data model instance, and at that point the data is in the datastore. if you just want to make some simulation data to play around with viewing, you could write up a straight python script that uses your own data models to populate the datastore for you. I followed mahmouds instructions here and they work great for my needs: http://groups.google.com/group/google-appengine/browse_thread/thread/2667c30d1726722e/a16ce7be0ab57c59?hl=enlnk=gstq=python+script+load+data#a16ce7be0ab57c59 I'd suggest you just work in the development server locally on your PC first. On Mar 19, 1:57 pm, Nora noorhanab...@yahoo.co.uk wrote: Hello, As I haven't used data stores before, I am unable to imagine how it is going to behave:) I have some text files and I want to store its contents in datastores. Do I load the datastore at the beginning and then upload my application and use the data in the datastore from there? Or do we fill the datastore up every time my applicaiton gets a request for it? Is the data saved in a certain file so when the application is uploaded on the google server, this file is transfered on the server and I start to use it from there? Thank you very much, N. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: App Engine Patch - dumpdata then loaddata
Hi Waldemar, Thanks for following up, and thanks for all your hard work with App Engine Patch. I'm having a lot of fun learning about app engine and django in my spare time, and hope to one day move my full time career into this stuff. Django, GAE, and your stuff will have a huge hand in that. Anyway, the property I'm tryign to dump is DateTimeProperty: date = db.DateTimeProperty() I'll have a look at that file you refer to and see if I can figure something out. Stu On Mar 19, 2:00 pm, Waldemar Kornewald wkornew...@gmail.com wrote: On Mar 18, 6:19 pm, Big Stu stu.dohe...@gmail.com wrote: I'm having a problem with my App Engine Patch project where if I dumpdata from my app engine server using: ./manage.py dumpdata --format json data.json Then reset the servers data: ./manage.py reset And then try to reload that data: ./manage.py loaddata data.json I get complaints about Date properties not being datetime objects. Currently, we only support DateTimeProperty and I don't know when I'll get to the other properties. I've got a lot of other stuff on my plate. If it's critical to you I'd suggest that you have a look at django/core/serializers/python.py and extend the deserializer. Bye, Waldemar Kornewald --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] App Engine Patch - dumpdata then loaddata
I'm having a problem with my App Engine Patch project where if I dumpdata from my app engine server using: ./manage.py dumpdata --format json data.json Then reset the servers data: ./manage.py reset And then try to reload that data: ./manage.py loaddata data.json I get complaints about Date properties not being datetime objects. I've read about some similar sounding issues with the deserializer used by Django, but these are from last summer or before, and they appear to have solutions. Any idea what I'm doing wrong? Incidentially, I have to remove the first line Running on app-engine- patch 1.0 from data.json. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: App Engine Patch - dumpdata then loaddata
If I try using a different serializer (yaml) I get this complaint: Error: Unable to serialize database: cannot represent an object: s...@localhost So json doesn't like date formats, and yaml doesn't like the email address field. Anyone know whats up here? THanks Stu --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: New GAE App: Wordds.com - magazine articles optimized for your iPhone, Kindle BlackBerry
Hey Eric, Looks really cool! Very clean design too. If you don't mind sharing, what kinds of tools/libraries did you use to put it together? I'm also looking at doing an app that I want to be as useful through a mobile device as through the desktop web. -What web framework? -Is the mobile view layer done completely separate from the desktop? or is there some view layer toolkit that makes that kind of thing easy (single code base) Thanks Stu --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Code reuse, templates, view layer understanding?
I'm slowly digesting all the pieces involved in this whole GAE thing (not to mention the ins and outs of web apps in general). Python is such a treat to work with. I recently read some article on Django/ Python that talked about the emphasis on code reuse woven into the technology. This is approach is something I really like. To illustrate my question I'll give an example. Lets say I want to build a competitor to gmail (on GAE... how funny would that be?!). Now, similar to gmail, I'd like to have a calender widget appear all throughout the the views the user gets on my app. So, when they view the inbox its on the bottom left. And maybe when they view their preferences its on the top right. And maybe if there's a family calender they would like to always see then both personal and family calenders would appear stacked all throughout the view on the app. So, my question is, is there some sort of code reuse like approach to producing the html/look for that calender (wherever its placed, however many different ones there are)? So that I can have multiple templates that I render (inbox,preferences, etc.) that will all have a calender in them, but without having to re-write the template code that creates the calender html/markup? Is this something I'd do with javascript, where I have javascript that implements the widget and just call that script into whatever templates I want it? Thanks in advance. Stu --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Entity Groups
It also benefits from locality. Entity groups are stored close together (needed to make transactions fast), which is why lots of small entity groups makes the overall application faster (because they can be spread out). If you do a bunch of processing on groups of entities in a single request then you can put them in a entity group, which should make that processing faster because they will be kept close. Dave. I don't quite have my head wrapped around the entity group thing either. The transaction part I get...other benefits I don't quite get yet. If I were to build an app for managing dollar store inventory or something like that would I want to make all the data related to a particular store part of the same entity group? So that the data for a store in Toronto is part of one group, and the data for Vancouver is part of another, and then as far as teh datastore and access times are concerned the storage of the datasets will be best suited to the geography of the situation? Am I getting this right? Thanks. Stu --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
