Another ideas :) - add "handler" to app.yaml editor (i.e : "add new static dir -> browse it and select, add new static file, etc,...) Ordering handlers must be possible (it's important) - add an "index.yaml" editor - add a "real" GAE template : with all "required" dirs (img, static, css, template) that works with the webapp framework. And add your favicon to this template :) it creates an error by default. - add a built-in GQL manager : select db.Model and query the entities. We could dump the rows and for example, with blob if we choose the type (png, gif, binary, text,...) it could be possible to display the "real content" not only binary string. Rows must be editabled.
Regards On 30 août, 14:20, EricWittmann <[EMAIL PROTECTED]> wrote: > Cool - thanks for the ideas. I will need to put these into the gaedt > wiki at some point. > > Re: Command-Line Args - gaedt introduces a file called gae.yaml. This > file contains the dev server command line args. Right now it is only > port, but the intent is to contain all of the dev server args. > > I'll have to take a look at the profiling link - thanks for that. I > haven't gotten far enough into my own gae work yet to have worried > about profiling. But in general, I would think we'd want gaedt to > have as much built-in as possible, even if it's just integration with > existing technologies. We'd want best practices for profiling, unit > testing, etc etc. > > Built-in document is also a fantastic idea. Perhaps a separate view > for that, or maybe there's a way to integrate into the existing > Eclipse Help framework. > > On Aug 29, 5:38 pm, Sylvain <[EMAIL PROTECTED]> wrote: > > > One word : great ! > > > ideas : > > * add options : same as "Command-Line Arguments" (http:// > > code.google.com/appengine/docs/thedevwebserver.html > > * automaticaly add the profiling code > > :http://code.google.com/appengine/kb/commontasks.html#profiling > > * open the eclipse browser with the "local admin" _ah/admin > > * open the eclipse browser with the documentations (local, we can > > download it now or internet) > > > On 29 août, 18:31, EricWittmann <[EMAIL PROTECTED]> wrote: > > > > Hey everyone. > > > > We have started a project to create an Eclipse-based IDE for > > > developing Google App Engine applications. To that end, we have > > > create the following open source project: > > > >http://code.google.com/p/gaedt/ > > > > Some of the features already present in gaedt: > > > > 1) Based on PyDev for Eclipse > > > 2) New GAE Project Wizard > > > 3) Application Editor (editor for the app.yaml file) > > > 4) GAE Applications View - shows all GAE Applications found in the > > > workspace > > > 5) Quick Run/Debug/Browse (etc) actions for Applications listed in the > > > Applications View > > > > The long-term goal of the project is for gaedt to become the top/ > > > defacto development environment for create GAE apps. To accomplish > > > this, we'd love to get help from the rest of the GAE community. > > > Anything from feature ideas to development contributions would be > > > greatly appreciated. We'll be updating the gaedt ourselves as we > > > encounter stumbling blocks during development of our own GAE > > > project(s). But what I think is really needed is solid contributions > > > from the GAE community. > > > > Take a look at the project page and let us know what you think. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
