Git Product home page Git Product logo

app-inventor's People

Contributors

afmckinney avatar halatmit avatar halgoogle avatar jisqyv avatar lizlooney avatar mark-friedman avatar sharonperl avatar theindexer avatar

app-inventor's Issues

Display the revision number

Make the svn revision number visible in the designer, so we can ask people 
reporting bugs to say what version they are using.

Here's something that might help.

http://ccollins.wordpress.com/2008/01/30/getting-subversion-revision-in-ant/

Original issue reported on code.google.com by [email protected] on 15 Nov 2011 at 3:11

Code review request

Purpose of code changes on this branch:

Add threadsafe property to appengine-web.xml file to enable concurrency in the 
app engine server.

After the review, I'll merge this branch into:
/trunk


Original issue reported on code.google.com by [email protected] on 15 Nov 2011 at 5:58

Write some tests dealing with project building

Write some tests dealing with things like:

 In ProjectServiceTest.java: test the build() and getBuildResults methods

 Create BuildServerTest.java to test invocation of build requests and the sending of test results back to a (mocked?) AI server.

Original issue reported on code.google.com by [email protected] on 15 Nov 2011 at 10:57

Code review request

Purpose of code changes on this branch:
Add an example whitelist file.

Details of this change can be found at:
https://code.google.com/p/app-inventor/source/detail?r=13

After the review, I'll merge this branch into:
/trunk


Original issue reported on code.google.com by [email protected] on 16 Nov 2011 at 6:54

Add some sort of integrity check for saving the blocks file

I received yet another source zip from a user recently where the blocks file 
was corrupted (in this case, it was truncated) and therefore failed to load in 
the blocks editor. I think we should add an integrity check when we save the 
blocks file (e.g., length and checksum) and only save it if the check passes on 
the server.

Original issue reported on code.google.com by [email protected] on 17 Nov 2011 at 7:08

Give users better infomation about build server status and add better feedback on errors

Make it visible to users when the buildserver is up/down.   Probably with a 
status indicators in the designer.

The debugger shows how long the server has been waiting for the buildserver 
while packaging.  We should reflect this to the user.  Better would be to show 
a progress bar.

If you try to generate a barcode and the buildserver is down, the designer will 
just wait forever.   


Original issue reported on code.google.com by [email protected] on 19 Nov 2011 at 10:00

Set MOTD checking to be off by default

The property motd.check.interval.secs in appengine-web.xml controls how often 
the browser contacts the server to check for a new message of the day. Setting 
it to 0 disables checking. We should probably set it to 0 by default for the 
distribution so that it doesn't use up resources unintentionally.

Original issue reported on code.google.com by [email protected] on 16 Nov 2011 at 10:08

Code review request

Purpose of code changes on this branch:

Don't sign the blocks editor jar file as Google.

After the review, I'll merge this branch into:
/trunk


Original issue reported on code.google.com by [email protected] on 16 Nov 2011 at 7:43

Problem with Developer vs Production versions of client-side code

From Liz:

In the current open source code, the client-side code is the developer version, 
even when it is actually running in production.

This is caused by the code in the <property-provider name="ode.version"> 
section of appengine/src/com/google/appinventor/YaClient.gwt.xml.
Most of the code has been commented out and it now always returns "developer".

This is causing the following differences:
The "(Debugging)" panel is visible.
The Designer toolbar shows the "Add Screen" button.
The tab bar shows in the designer.
The "For internal use only" section of the palette is visible and contains the 
Pedometer component.
The client-side tracking (Google Analytics) is disabled.

From the TODO in YaClient.gwt.xml, I think the intention was to show developer 
messages (#1 above).

As a result of this, the power users have now seen some parts of the support 
for multi-screen apps, which is still incomplete and not really working.

Original issue reported on code.google.com by [email protected] on 19 Nov 2011 at 3:34

Whitelist is visible to any gmail account

When a person is not logged into system with gmail account then you get server 
unavailable. anyone who is logged in to gmail account can view whitelist. by 
browsing to appname.appspot.com/whitelist.

Original issue reported on code.google.com by [email protected] on 15 Nov 2011 at 7:52

YaiEvalTest fails by running out of Perm-en space

Running the test gives:

  [junit] Running com.google.appinventor.buildserver.YailEvalTest
    [junit] Exception in thread "main" java.lang.OutOfMemoryError: PermGen space
    [junit]     at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.createCDATASection(CoreDocumentImpl.java:581)
    [junit]     at org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter.formatOutput(XMLJUnitResultFormatter.java:298)
    [junit]     at org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter.setSystemOutput(XMLJUnitResultFormatter.java:102)
    [junit]     at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.sendOutAndErr(JUnitTestRunner.java:712)
    [junit]     at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:547)
    [junit]     at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1052)
    [junit]     at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:906)
    [junit] Running com.google.appinventor.buildserver.YailEvalTest

The log says:

junit.framework.AssertionFailedError: Forked Java VM exited abnormally

I tried increasing the Perm-Gen space, both for ant and for the Kawa process 
that's started up in Compiler.java, but that
didn't change the behavior.


Original issue reported on code.google.com by [email protected] on 28 Nov 2011 at 2:39

Bad value for logging properties

reported by Shival

One other thing i noticed this during my startup
Bad level value for property: .level

/opt/ai/appinventor-Nov-24/appinventor/war/WEB-INF/logging.properties

I'm guessing it does not like DEBUG which was the default defined in the file.
doing some googling the options are.

Original issue reported on code.google.com by [email protected] on 4 Dec 2011 at 2:23

Give better error message when user is not on whitelist

Rigth now, when you try to connect and you're not on the whitelist, you get a 
"server unavailable" message that makes it seem like the server is down.   It 
would be better to instead bring up a page that explains that you don't have 
access, and explains what is going on.

Original issue reported on code.google.com by [email protected] on 28 Nov 2011 at 1:55

  • Merged into: #56

Should the appengine server keep APK files forever?

If we decide not to keep APK files forever, we have to do the following:

Remove the AndroidServlet.

Delete the APK file from storage when it is retrieved, except if the request is 
from the appengine client barcode dialog.

Delete the APK file from storage when the appengine client barcode dialog is 
dismissed.

Original issue reported on code.google.com by [email protected] on 15 Nov 2011 at 10:54

Open source codeblocks jar should not be signed by "Google".

Currently, blockseditor/build.xml signs BlocksEditor.jar with 
"CN=corp.google.com, OU=Engineering, O=Google, L=Mountain View, ST=CA, C=US".

This needs to be changed so that people who build their own instance of App 
Inventor use their own information.

Original issue reported on code.google.com by [email protected] on 15 Nov 2011 at 11:02

Code review request

Purpose of code changes on this branch:
Put an example whitelist in the distribution. Leave flag that says to use the 
whitelist set to false.

Details of this change can be found at:
https://code.google.com/p/app-inventor/source/detail?r=13

After the review, I'll merge this branch into:
/trunk


Original issue reported on code.google.com by [email protected] on 16 Nov 2011 at 6:14

  • Merged into: #5

Figure out whether we need to use "backends" in App Engine

I initially thought we did, per  
http://code.google.com/appengine/docs/java/backends/overview.html. However, 
Wesley Chun says in an email:

>> 1. you mentioned 100k users, but yet asked for the highest end backend
>> systems. is there a reason why you think you need a backend vs.
>> responding to standard dynamic requests?
>>
> -->You and Greg will be much better judges of what we need than we are.
> Figuring out the right level of requirements is one of the things we're
> looking for you to help with.

yes, with my question in particular, i think a standard dynamic
request will suffice. running a backend is useful only when specific
requests require more than 10-minutes to process.

Original issue reported on code.google.com by [email protected] on 15 Nov 2011 at 10:37

Fix or get rid of the bug reporting feature

Ode.onModuleLoad has an option to pop up a bug report form for uncaught 
exceptions. The current version of BugReport.java has a link to a form that 
doesn't make sense for the open source version of the system. Possibly we 
should just get rid of this feature.

Original issue reported on code.google.com by [email protected] on 1 Dec 2011 at 10:33

Change initial "Grey button" message

The gray button that you push to connect a device, should start with the text 
"waiting to load project" or something like that.   Ir maybe the button should 
not come up until the first project is loaded.

Currently, most people think that a gray button (i.e., text gray_ means that 
there's no device connected, when in fact this is the state where a project is 
not loaded and the blocks editor isn't even looking for devices yet.

Original issue reported on code.google.com by [email protected] on 19 Nov 2011 at 10:03

Server dying on large project and bad error message

The attached project loads on appinventorbeta, but not on our appengine 
instances.  You get "server could not upload.  Please try again later (which is 
a bad error message here) and the Java console says

WARNING: /ode/upload/project/BIG_DADDY_BINGO
com.google.apphosting.api.ApiProxy$RequestTooLargeException: The request to API 
call datastore_v3.Put() was too large.
    at com.google.appengine.tools.development.ApiProxyLocalImpl$AsyncApiCall.callInternal(ApiProxyLocalImpl.java:463)
...

The project as lots of assets and a jillion blocks.  Deleting the assets wasn't 
enough to fix this, but delete about half the blocks did.

I don't know whether there's some storage limit we need to increase, but at a 
minimum, we should have a better error message in this case.


Original issue reported on code.google.com by [email protected] on 3 Dec 2011 at 7:01

Attachments:

Add server version numbers (visible to users)

As we're starting to let people test this, it would be nice to make some kind 
of version date or number visible to users.  The build date
info in the designer page currently isn't hooked up, and I'm not sure it's 
build date that's useful anyway, at present.

Original issue reported on code.google.com by [email protected] on 15 Nov 2011 at 11:00

  • Merged into: #1

Add support for multi-screen applications

This was issue #46 in the old issues list. 
http://code.google.com/p/app-inventor-for-android/issues/detail?id=46

It should be implemented in the open source code before the end of 2011.

Original issue reported on code.google.com by [email protected] on 28 Nov 2011 at 5:08

add version support to MIT experimental service

Add version support to mite experimental service.

See 

http://code.google.com/appengine/docs/java/config/appconfig.html#About_appengine
_web_xml

and

http://code.google.com/appengine/docs/java/tools/uploadinganapp.html#Command_Lin
e_Arguments

for information

Original issue reported on code.google.com by [email protected] on 4 Dec 2011 at 5:06

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.