my GWT application doesn't open in chrome or firefox.

Hi,

My GWT application doesn't work with the chrome or firefox. It works only in IE explorer. I was thinking if it has to do anything with the meta tag definition in the html

<meta http-equiv="content-type" content="text/html; charset=UTF-8">

this is how I defined it currently. Please let me know. Thanks,

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[android-developers] Re: Do SQLiteDatabase references "go stale"?

Just another related thought: SQLiteDatabase contains some implicit "transaction magic" under the hood which is meant to prevent "accidents" due to simultaneous accesses from different threads. That does not always work that great and can lead to some kind of indefinite deadlock situation. You can ease that problem by making sure to only give one thread "ownership" of the db connection by letting it open and query the connection.

You also must make sure not to open the same database connection multiple times. In older Android versions that error was not treated gracefully and the database file could get corrupted. In newer versions you are greeted with an exception. When the database file gets corrupted, the default behavior of SQLiteDatabase is "silently" dropping the whole database file and creating a new one, so basically you start from scratch in such a situation and probably your table creation / setup routines kick in and start fresh.


On Wednesday, July 31, 2013 2:01:33 PM UTC-5, Nathan wrote:

On Wednesday, July 31, 2013 9:21:59 AM UTC-7, Nobu Games wrote:

How are you handling transactions in your queries?

A single record written is done as a single transaction. I believe, though, that the writing part is all done and it is now just reading. No transactions on reading.

 

In later versions of Android SQLite writes by default temporary "journaling" data files that are not immediately merged with the actual database file (see here: http://www.sqlite.org/tempfiles.html). This might be an explanation for the reported behavior, see the following quote from the SQLite documentation:

However, if the last connection does not shutdown cleanly, the WAL file will remain in the filesystem and will be automatically cleaned up the next time the database is opened.

I would expect some blocking on first open after a crash in that situation.
 

Other than that, are you sure the path argument is always the same?

Not completely sure. I want to investigate if there is a possibility of getting two paths that are equivalent, yet don't look the same in a string compare.
If so, this code would fail to prevent opening the same file twice in the same process.

Nathan

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[android-developers] Re: Do SQLiteDatabase references "go stale"?

Just another related thought: SQLiteDatabase contains some implicit "transaction magic" under the hood which is meant to prevent "accidents" due to simultaneous accesses from different threads. That does not always work that great and can lead to some kind of indefinite deadlock situation. You can ease that problem by making sure to only give one thread "ownership" of the db connection by letting it open and query the connection. You could enforce that by implementing a content provider that is only used by your app.

You also must make sure not to open the same database connection multiple times. In older Android versions that error was not treated gracefully and the database file could get corrupted. In newer versions you are greeted with an exception. When the database file gets corrupted, the default behavior of SQLiteDatabase is "silently" dropping the whole database file and creating a new one, so basically you start from scratch in such a situation and probably your table creation / setup routines kick in and start fresh.




On Wednesday, July 31, 2013 2:01:33 PM UTC-5, Nathan wrote:

On Wednesday, July 31, 2013 9:21:59 AM UTC-7, Nobu Games wrote:

How are you handling transactions in your queries?

A single record written is done as a single transaction. I believe, though, that the writing part is all done and it is now just reading. No transactions on reading.

 

In later versions of Android SQLite writes by default temporary "journaling" data files that are not immediately merged with the actual database file (see here: http://www.sqlite.org/tempfiles.html). This might be an explanation for the reported behavior, see the following quote from the SQLite documentation:

However, if the last connection does not shutdown cleanly, the WAL file will remain in the filesystem and will be automatically cleaned up the next time the database is opened.

I would expect some blocking on first open after a crash in that situation.
 

Other than that, are you sure the path argument is always the same?

Not completely sure. I want to investigate if there is a possibility of getting two paths that are equivalent, yet don't look the same in a string compare.
If so, this code would fail to prevent opening the same file twice in the same process.

Nathan

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: [Rails] Re: Proper rails deployment steps to DirectAdmin (or any hosting not focusing in apps) hosted server?

On Wed, Jul 31, 2013 at 12:26 PM, <southierobert@gmail.com> wrote:
> What is most popular way to deploy apps on non-Heroku machine that has
> standard Apache/MySQL setup?

One option: http://www.capistranorb.com/

--
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
http://about.me/hassanschroeder
twitter: @hassan

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CACmC4yAEhurnsFcVUD2dCowP3N%2BiyPac88VeKkp239eSZurTVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: detect sop violation from gwt rpc client

Sorry I'm so very new at this--I'm not sure I quite understand: once I have my CustomRequestTransport, how do I make my GWT-RPC services use it by casting them into ServiceDefTarget?

I'm using gwt-2.5.1, and when I look here, I don't see how ServiceDefTarget has something that takes a RequestTransport:

http://www.gwtproject.org/javadoc/latest/com/google/gwt/user/client/rpc/ServiceDefTarget.html

On Tuesday, July 30, 2013 7:25:20 AM UTC-6, Jens wrote:

You can extend DefaultRequestTransport to gain access to the raw server response. You then have to set your custom RequestTransport into your GWT-RPC services by casting them into ServiceDefTarget.

You should check if all browsers supported by your app set the location header in case of a SOP violation. Maybe some don't. Maybe some other browsers also sets the location header in cases of network outage. Your solution may not be 100% reliable. 

-- J.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Rails] Re: Proper rails deployment steps to DirectAdmin (or any hosting not focusing in apps) hosted server?

What is most popular way to deploy apps on non-Heroku machine that has standard Apache/MySQL setup? I would like to be able to deploy my apps (as I learn Rails) to my own dedicated machines. I have already installed Ruby, & rails gem, and I'm able to create apps on that machine without any issues. It is when I develop something localy when I face issue as I don't know how to deploy it "properly"? Do I simply upload entire app folder structure over FTP, run bundle install, config database, and start the app OR is there a faster/easier way?



On Wednesday, July 31, 2013 4:06:05 AM UTC-4, Frederick Cheung wrote:

On Monday, July 29, 2013 2:53:42 PM UTC+1, southi...@gmail.com wrote:
> Hi,
>  
> With PHP applications (only experience I had before), all I needed to do is to FTP all required files, create MySQL username/pass & upload SQL structure, add this username/pass in any given config file of the php script and the app worked.
>  
> Can you tell me what are standard/proper steps required to deploy an app that I worked on my local Ubuntu machine and want to have it working on 'standard' web hosting company that does not specialize in Rails app hosting?
>  

While there are many ways of deploying rails applications, it's extremely unlikely that a non rails specialist will have installed/configured any of them. If you're looking for an easy way to deploy a rails app, it's hard to beat heroku for simplicity.

Fred


> Thanks,
>  
> Rob

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/5734b792-eb1e-427b-9dc6-9805bc678ddd%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: Clarification needed on SimpleRemoteLogHandler

On Wednesday, July 31, 2013 8:56:50 PM UTC+2, QC wrote:

Hi everyone,

Recently I came across a rare incident where a client kept retrying on a URL that looks related to SimpleRemoteLogHandler.  But after I scrutinize the code, I believe it has nothing to do with the retry behavior. However, the doc below for this handler is a bit ambiguous (especially ''nor does it disable when the RPC calls fail repeatedly") --- making one of my teammate feel it does retry upon failures. 

/**
 * A very simple handler which sends messages to the server via GWT RPC to be
 * logged. Note that this logger does not do any intelligent batching of RPC's,
 * nor does it disable when the RPC calls fail repeatedly.
 */

It does not; look at the code. 

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[android-developers] Re: Do SQLiteDatabase references "go stale"?

On Wednesday, July 31, 2013 9:21:59 AM UTC-7, Nobu Games wrote:

How are you handling transactions in your queries?

A single record written is done as a single transaction. I believe, though, that the writing part is all done and it is now just reading. No transactions on reading.

 

In later versions of Android SQLite writes by default temporary "journaling" data files that are not immediately merged with the actual database file (see here: http://www.sqlite.org/tempfiles.html). This might be an explanation for the reported behavior, see the following quote from the SQLite documentation:

However, if the last connection does not shutdown cleanly, the WAL file will remain in the filesystem and will be automatically cleaned up the next time the database is opened.

I would expect some blocking on first open after a crash in that situation.
 

Other than that, are you sure the path argument is always the same?

Not completely sure. I want to investigate if there is a possibility of getting two paths that are equivalent, yet don't look the same in a string compare.
If so, this code would fail to prevent opening the same file twice in the same process.

Nathan

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Clarification needed on SimpleRemoteLogHandler

Hi everyone,

Recently I came across a rare incident where a client kept retrying on a URL that looks related to SimpleRemoteLogHandler.  But after I scrutinize the code, I believe it has nothing to do with the retry behavior. However, the doc below for this handler is a bit ambiguous (especially ''nor does it disable when the RPC calls fail repeatedly") --- making one of my teammate feel it does retry upon failures. 

/**
 * A very simple handler which sends messages to the server via GWT RPC to be
 * logged. Note that this logger does not do any intelligent batching of RPC's,
 * nor does it disable when the RPC calls fail repeatedly.
 */

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: [android-developers] Re: Getting OutOfMemory Error while loading images in fragments. (Only on Android OS version 4.1.2 Jelly Bean)

Oh ok, so do I need to use something like lazy list or is there any way that i can handle it in my code. I am using Fragment Activity and have created two fragments and replacing them alternatively for displaying all the images one by one. 

One more thing that i don't understand is why only on 4.1.2?! I tested the application on android 2.3.3, 4.0.3, 4.0.4, 4.1.1, 4.2, also on different devices with lower and higher processors, i.e. samsung galaxy s plus, galaxy s2, sony xperia tipo, samsung galaxy tab 7 and 10.1. On all the devices, it doesn't crash but only on the devices with version 4.1.2.

On Wed, Jul 31, 2013 at 7:34 PM, Piren <gpiren@gmail.com> wrote:

Your images are not 2.3MB, their compressed data is... the images when loaded by Android are much more than that (their size according to android is basically their resolution times the bit depth per pixel you defined).

The last image you loaded asked for 8.4MB alone...

I assume that you don't actually need to load all those images at the same time since you dont have the screen space for that, so load them only when they are visible and free them as soon as they are not.

On Wednesday, July 31, 2013 4:46:43 PM UTC+3, Matt wrote:

Hi all, 

I am loading several images on Fragments. I have about 22 images of total 2.3 MB. I am getting OutOfMemory error every time I test my app on devices with Jelly Bean 4.1.2. The weird thing is, this happens only when I test it on devices with Android version 4.1.2. It works fine on any other versions on any devices. I am posting my error log here. Please let me know what could be wrong:

07-31 14:08:48.688: D/dalvikvm(11970): GC_FOR_ALLOC freed 963K, 42% free 24641K/41863K, paused 30ms, total 31ms

07-31 14:08:48.688: I/dalvikvm-heap(11970): Grow heap (frag case) to 29.015MB for 3932176-byte allocation

07-31 14:08:48.748: D/dalvikvm(11970): GC_CONCURRENT freed 2170K, 38% free 26311K/41863K, paused 14ms+5ms, total 60ms

07-31 14:08:48.803: D/dalvikvm(11970): GC_FOR_ALLOC freed 0K, 38% free 26311K/41863K, paused 17ms, total 17ms

07-31 14:08:48.803: I/dalvikvm-heap(11970): Forcing collection of SoftReferences for 8847376-byte allocation

07-31 14:08:48.828: D/dalvikvm(11970): GC_BEFORE_OOM freed 0K, 38% free 26311K/41863K, paused 25ms, total 25ms

07-31 14:08:48.828: E/dalvikvm-heap(11970): Out of memory on a 8847376-byte allocation.

07-31 14:08:48.828: I/dalvikvm(11970): "main" prio=5 tid=1 RUNNABLE

07-31 14:08:48.828: I/dalvikvm(11970):   | group="main" sCount=0 dsCount=0 obj=0x4119c508 self=0x40f509a0

07-31 14:08:48.828: I/dalvikvm(11970):   | sysTid=11970 nice=0 sched=0/0 cgrp=apps handle=1074540336

07-31 14:08:48.828: I/dalvikvm(11970):   | schedstat=( 14365434265 4071559868 25502 ) utm=1314 stm=122 core=1

07-31 14:08:48.828: I/dalvikvm(11970):   at android.graphics.BitmapFactory.nativeDecodeAsset(Native Method)

07-31 14:08:48.828: I/dalvikvm(11970):   at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:625)

07-31 14:08:48.828: I/dalvikvm(11970):   at android.graphics.BitmapFactory.decodeResourceStream(BitmapFactory.java:478)

07-31 14:08:48.828: I/dalvikvm(11970):   at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:781)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.content.res.Resources.loadDrawable(Resources.java:1963)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.content.res.Resources.getDrawable(Resources.java:672)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.view.View.setBackgroundResource(View.java:14497)

07-31 14:08:48.833: I/dalvikvm(11970):   at com.example.myexample.pages.CoverPage.onActivityCreated(CoverPage.java:46)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.support.v4.app.Fragment.performActivityCreated(Fragment.java:1468)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:931)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1088)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.support.v4.app.BackStackRecord.run(BackStackRecord.java:682)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1444)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.support.v4.app.FragmentManagerImpl$1.run(FragmentManager.java:429)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.os.Handler.handleCallback(Handler.java:615)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.os.Handler.dispatchMessage(Handler.java:92)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.os.Looper.loop(Looper.java:137)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.app.ActivityThread.main(ActivityThread.java:4921)

07-31 14:08:48.833: I/dalvikvm(11970):   at java.lang.reflect.Method.invokeNative(Native Method)

07-31 14:08:48.833: I/dalvikvm(11970):   at java.lang.reflect.Method.invoke(Method.java:511)

07-31 14:08:48.833: I/dalvikvm(11970):   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1027)

07-31 14:08:48.833: I/dalvikvm(11970):   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:794)

07-31 14:08:48.833: I/dalvikvm(11970):   at dalvik.system.NativeStart.main(Native Method)

07-31 14:08:48.833: A/libc(11970): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 11970 (ple.storybookex)

07-31 14:08:58.808: E/run(11970): run-runnable

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "Android Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-developers/4ziD1KLInco/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: [android-developers] Re: Getting OutOfMemory Error while loading images in fragments. (Only on Android OS version 4.1.2 Jelly Bean)

Oh ok, so do I need to use something like lazy list or is there any way that i can handle it in my code. I am using Fragment Activity and have created two fragments and replacing them alternatively for displaying all the images one by one. 

One more thing that i don't understand is why only on 4.1.2?! I tested the application on android 2.3.3, 4.0.3, 4.0.4, 4.1.1, 4.2, also on different devices with lower and higher processors, i.e. samsung galaxy s plus, galaxy s2, sony xperia tipo, samsung galaxy tab 7 and 10.1. On all the devices, it doesn't crash but only on the devices with version 4.1.2.

On Wed, Jul 31, 2013 at 7:34 PM, Piren <gpiren@gmail.com> wrote:

Your images are not 2.3MB, their compressed data is... the images when loaded by Android are much more than that (their size according to android is basically their resolution times the bit depth per pixel you defined).

The last image you loaded asked for 8.4MB alone...

I assume that you don't actually need to load all those images at the same time since you dont have the screen space for that, so load them only when they are visible and free them as soon as they are not.

On Wednesday, July 31, 2013 4:46:43 PM UTC+3, Matt wrote:

Hi all, 

I am loading several images on Fragments. I have about 22 images of total 2.3 MB. I am getting OutOfMemory error every time I test my app on devices with Jelly Bean 4.1.2. The weird thing is, this happens only when I test it on devices with Android version 4.1.2. It works fine on any other versions on any devices. I am posting my error log here. Please let me know what could be wrong:

07-31 14:08:48.688: D/dalvikvm(11970): GC_FOR_ALLOC freed 963K, 42% free 24641K/41863K, paused 30ms, total 31ms

07-31 14:08:48.688: I/dalvikvm-heap(11970): Grow heap (frag case) to 29.015MB for 3932176-byte allocation

07-31 14:08:48.748: D/dalvikvm(11970): GC_CONCURRENT freed 2170K, 38% free 26311K/41863K, paused 14ms+5ms, total 60ms

07-31 14:08:48.803: D/dalvikvm(11970): GC_FOR_ALLOC freed 0K, 38% free 26311K/41863K, paused 17ms, total 17ms

07-31 14:08:48.803: I/dalvikvm-heap(11970): Forcing collection of SoftReferences for 8847376-byte allocation

07-31 14:08:48.828: D/dalvikvm(11970): GC_BEFORE_OOM freed 0K, 38% free 26311K/41863K, paused 25ms, total 25ms

07-31 14:08:48.828: E/dalvikvm-heap(11970): Out of memory on a 8847376-byte allocation.

07-31 14:08:48.828: I/dalvikvm(11970): "main" prio=5 tid=1 RUNNABLE

07-31 14:08:48.828: I/dalvikvm(11970):   | group="main" sCount=0 dsCount=0 obj=0x4119c508 self=0x40f509a0

07-31 14:08:48.828: I/dalvikvm(11970):   | sysTid=11970 nice=0 sched=0/0 cgrp=apps handle=1074540336

07-31 14:08:48.828: I/dalvikvm(11970):   | schedstat=( 14365434265 4071559868 25502 ) utm=1314 stm=122 core=1

07-31 14:08:48.828: I/dalvikvm(11970):   at android.graphics.BitmapFactory.nativeDecodeAsset(Native Method)

07-31 14:08:48.828: I/dalvikvm(11970):   at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:625)

07-31 14:08:48.828: I/dalvikvm(11970):   at android.graphics.BitmapFactory.decodeResourceStream(BitmapFactory.java:478)

07-31 14:08:48.828: I/dalvikvm(11970):   at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:781)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.content.res.Resources.loadDrawable(Resources.java:1963)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.content.res.Resources.getDrawable(Resources.java:672)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.view.View.setBackgroundResource(View.java:14497)

07-31 14:08:48.833: I/dalvikvm(11970):   at com.example.myexample.pages.CoverPage.onActivityCreated(CoverPage.java:46)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.support.v4.app.Fragment.performActivityCreated(Fragment.java:1468)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:931)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1088)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.support.v4.app.BackStackRecord.run(BackStackRecord.java:682)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1444)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.support.v4.app.FragmentManagerImpl$1.run(FragmentManager.java:429)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.os.Handler.handleCallback(Handler.java:615)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.os.Handler.dispatchMessage(Handler.java:92)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.os.Looper.loop(Looper.java:137)

07-31 14:08:48.833: I/dalvikvm(11970):   at android.app.ActivityThread.main(ActivityThread.java:4921)

07-31 14:08:48.833: I/dalvikvm(11970):   at java.lang.reflect.Method.invokeNative(Native Method)

07-31 14:08:48.833: I/dalvikvm(11970):   at java.lang.reflect.Method.invoke(Method.java:511)

07-31 14:08:48.833: I/dalvikvm(11970):   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1027)

07-31 14:08:48.833: I/dalvikvm(11970):   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:794)

07-31 14:08:48.833: I/dalvikvm(11970):   at dalvik.system.NativeStart.main(Native Method)

07-31 14:08:48.833: A/libc(11970): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 11970 (ple.storybookex)

07-31 14:08:58.808: E/run(11970): run-runnable

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "Android Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-developers/4ziD1KLInco/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

Thanks & Regards,

Maitrey Chhaya

Junior Software Engineer

 

Rossitek Software Solutions

#320/B, Sri Manjunatha Arcade,

1st phase, 2nd Stage 40 ft Road.

Manjunathnagar, Bangalore-560 010

Board Number       :  +91 80 41440617

 

www.rossitek.com

 

Offshore Mobile & Software Development House

IT Capital of India, Bangalore

Offshore Development Projects, Teams and Solutions

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: [android-developers] Bizarre OpenGL ES rendering artifact on Nexus 7 with Android 4.3

Thanks for the explanation

On Wednesday, July 31, 2013 12:52:14 PM UTC-5, Romain Guy (Google) wrote:

glSurfaceView.getHolder().setFormat(PixelFormat.RGBA_8888);

This gives you a translucent surface, which means that any pixel that is not drawn completely opaque will be blended with whatever window is behind your app. It will affect your performance btw.

 

Should I change the surface view format to RGB_888 instead?

Yes, that will fix your problem and improve perfornance.

 

Regards,

Thomas


On Wednesday, July 31, 2013 12:13:51 PM UTC-5, Romain Guy (Google) wrote:

Is your SurfaceView marked with the transparent pixel format? If so, what you are seeing would be expected. If your SurfaceView is opaque then you *must* draw every pixel opaque on screen.

On Wed, Jul 31, 2013 at 8:25 AM, Nobu Games <dev.nob...@gmail.com> wrote:

I got a big problem with a game of mine and the latest version of Android. Semi-transparent pixels rendered on the OpenGL ES surface let the underlying activity shine through as following screen shot shows.

This problem only appears in a new "AppGratis" promoted version of the game I just released this morning and here is the really bizarre thing: ONLY the APK downloaded from Google Play has this problem. When I install the same APK that is locally stored on my computer via adb I do not have this problem.
I re-installed the Google Play version multiple times and the rendering artifact is always reproducible.

It looks like Google Play alters the APK or maybe it is incorrectly installed on the device. However, I do not even know what may trigger that "shine through" effect. Any help (especially from Google) appreciated.

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-d...@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Romain Guy
Android framework engineer
roma...@android.com

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-d...@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Romain Guy
Android framework engineer
roma...@android.com

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: Odd issue with beforeFilter()

Okay..If anyone else has this issue, here is the solution to my particular problem.  I created an element 't_rt_keyhole' , which uses the requestAction to return data, in one of my views.  The troublesome line is:

$this->requestAction('/page_key_holes/keyhole/'.$pageid.'/'.$templateid);

Since this action uses a view of "keyhole" my before filter was not allowing the page.  Simply adding keyhole to me beforefilter did the trick:

function beforeFilter() { parent::beforeFilter(); $this->Auth->allow('view', 'keyhole'); }

Hope this helps others.

--
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
 
---
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscribe@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: [android-developers] Bizarre OpenGL ES rendering artifact on Nexus 7 with Android 4.3

glSurfaceView.getHolder().setFormat(PixelFormat.RGBA_8888);

This gives you a translucent surface, which means that any pixel that is not drawn completely opaque will be blended with whatever window is behind your app. It will affect your performance btw.

 

Should I change the surface view format to RGB_888 instead?

Yes, that will fix your problem and improve perfornance.

 

Regards,

Thomas


On Wednesday, July 31, 2013 12:13:51 PM UTC-5, Romain Guy (Google) wrote:

Is your SurfaceView marked with the transparent pixel format? If so, what you are seeing would be expected. If your SurfaceView is opaque then you *must* draw every pixel opaque on screen.

On Wed, Jul 31, 2013 at 8:25 AM, Nobu Games <dev.nob...@gmail.com> wrote:

I got a big problem with a game of mine and the latest version of Android. Semi-transparent pixels rendered on the OpenGL ES surface let the underlying activity shine through as following screen shot shows.

This problem only appears in a new "AppGratis" promoted version of the game I just released this morning and here is the really bizarre thing: ONLY the APK downloaded from Google Play has this problem. When I install the same APK that is locally stored on my computer via adb I do not have this problem.
I re-installed the Google Play version multiple times and the rendering artifact is always reproducible.

It looks like Google Play alters the APK or maybe it is incorrectly installed on the device. However, I do not even know what may trigger that "shine through" effect. Any help (especially from Google) appreciated.

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-d...@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Romain Guy
Android framework engineer
roma...@android.com

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Romain Guy
Android framework engineer
romainguy@android.com

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: [android-developers] Bizarre OpenGL ES rendering artifact on Nexus 7 with Android 4.3

Hi Romain,

thanks for your reply. It seems I do not understand the surface view initialization for making the alpha channel within OpenGL ES work. I set up the surface view with:

glSurfaceView.getHolder().setFormat(PixelFormat.RGBA_8888);

The game is already out with that surface view setup since May and nobody complained about the graphics so far. It also got reviewed with screen shots and videos and so on and this artifact is nowhere to be seen.

I also do not understand why there is a difference in rendering between the APK downloaded through Google Play and the exact same APK locally installed via adb.

Should I change the surface view format to RGB_888 instead?

Regards,

Thomas


On Wednesday, July 31, 2013 12:13:51 PM UTC-5, Romain Guy (Google) wrote:

Is your SurfaceView marked with the transparent pixel format? If so, what you are seeing would be expected. If your SurfaceView is opaque then you *must* draw every pixel opaque on screen.

On Wed, Jul 31, 2013 at 8:25 AM, Nobu Games <dev.nob...@gmail.com> wrote:

I got a big problem with a game of mine and the latest version of Android. Semi-transparent pixels rendered on the OpenGL ES surface let the underlying activity shine through as following screen shot shows.

This problem only appears in a new "AppGratis" promoted version of the game I just released this morning and here is the really bizarre thing: ONLY the APK downloaded from Google Play has this problem. When I install the same APK that is locally stored on my computer via adb I do not have this problem.
I re-installed the Google Play version multiple times and the rendering artifact is always reproducible.

It looks like Google Play alters the APK or maybe it is incorrectly installed on the device. However, I do not even know what may trigger that "shine through" effect. Any help (especially from Google) appreciated.

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-d...@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Romain Guy
Android framework engineer
roma...@android.com

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: [android-developers] Bizarre OpenGL ES rendering artifact on Nexus 7 with Android 4.3

Is your SurfaceView marked with the transparent pixel format? If so, what you are seeing would be expected. If your SurfaceView is opaque then you *must* draw every pixel opaque on screen.

On Wed, Jul 31, 2013 at 8:25 AM, Nobu Games <dev.nobu.games@gmail.com> wrote:

I got a big problem with a game of mine and the latest version of Android. Semi-transparent pixels rendered on the OpenGL ES surface let the underlying activity shine through as following screen shot shows.

This problem only appears in a new "AppGratis" promoted version of the game I just released this morning and here is the really bizarre thing: ONLY the APK downloaded from Google Play has this problem. When I install the same APK that is locally stored on my computer via adb I do not have this problem.
I re-installed the Google Play version multiple times and the rendering artifact is always reproducible.

It looks like Google Play alters the APK or maybe it is incorrectly installed on the device. However, I do not even know what may trigger that "shine through" effect. Any help (especially from Google) appreciated.

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Romain Guy
Android framework engineer
romainguy@android.com

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: [android-developers] Re: Dealing with 1000's of different devices, each one with its own bugs

Just because a test suite doesn't cover all possible behavior doesn't
mean stricter enforcement wouldn't help developers.

Test suites don't cover all of the codebase by definition, that's why
they're called test suites :-)

So I'm in favor of setting up a tracker for device bugs, but that
doesn't also mean that stricter enforcement of bugs couldn't aid
developers. E.g., to mention one of Omer's points: there could have
been a CTS test to test the gallery app on that intent. (I believe
other intents are tested...)

Kris


On Wed, Jul 31, 2013 at 12:46 PM, Daniele Segato
<daniele.segato@gmail.com> wrote:
> On 07/31/2013 05:17 PM, Kristopher Micinski wrote:
>>
>> Yes. To install Google Play or Google apps, you absolutely are
>> required to pass the CTS.
>>
>> But, from your discussion, the CTS obviously doesn't test all parts of
>> the Android platform: it's just a test suite.
>
>
> Yes, and never will.
>
> It may be a good idea to contact them and ask if they can help in setting up
> a bug database for incompatibilities between different android versions.
>
> No idea on how to contact them.

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: GLSurfaceView lag/delay on Galaxy S3.

I see in your code sample in your original post that you log the event coordinates. That can stall your app and may be a reason for these delays. Also, how do you communicate the touch events to your rendering thread?

On Wednesday, July 31, 2013 12:06:22 PM UTC-5, Edvinas Kilbauskas wrote:

2013 m. liepa 31 d., trečiadienis 19:28:23 UTC+3, Streets Of Boston rašė:

Is your render-mode continuously or when-dirty? 

If it is when-dirty, be sure to call surfaceView.requestRender() in your onTouchEvent implementation.

It's RENDERMODE_CONTINUOUSLY.

Also, I took the advice, and rewrote everything in OpenGL ES 2.0. And you know what? It still has the same amount of delay! What the hell?

I really though ES 2.0 would fix this issue, but it didn't!

Now i'm really thinking that this issue is not fixable. It probably has something to do with drivers.

But I still can't get out of my head why some other games have no lag or delay? Some games do, but not all of them. Or atleast I think they don't have delay, maybe it just seem like that... I don't know it's very annoying, If I turn power saving mode off it becomes better, but still has delay. 

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: Dealing with big cakephp applications

Hi, Diogo.

If your aim is to separate the models from the controllers, views, etc., then Cake can handle that.  I haven't tried this yet, but I was looking at the possibility of splitting off the back-end functions of my app to a separate app on a sub-domain.  From there I can either link to the models in in the main app, or split the models off into their own "app" just for modularity.  Like Reuben said, plugins would also help to avoid redundant code between apps.

The Cookbook shows you here http://book.cakephp.org/2.0/en/core-utility-libraries/app.html, in the section titled "Adding paths for App to find packages in" how to direct Cake to another directory containing the Models to be used by your app (theoretically, the same would apply for other Cake classes, like controllers, views, etc.).

Like I said, I haven't tried this yet, so I am not sure if there are any practical issues to be resolved.

Good luck.

--
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
 
---
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscribe@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[android-developers] Re: GLSurfaceView lag/delay on Galaxy S3.

2013 m. liepa 31 d., trečiadienis 19:28:23 UTC+3, Streets Of Boston rašė:

Is your render-mode continuously or when-dirty? 

If it is when-dirty, be sure to call surfaceView.requestRender() in your onTouchEvent implementation.

It's RENDERMODE_CONTINUOUSLY.

Also, I took the advice, and rewrote everything in OpenGL ES 2.0. And you know what? It still has the same amount of delay! What the hell?

I really though ES 2.0 would fix this issue, but it didn't!

Now i'm really thinking that this issue is not fixable. It probably has something to do with drivers.

But I still can't get out of my head why some other games have no lag or delay? Some games do, but not all of them. Or atleast I think they don't have delay, maybe it just seem like that... I don't know it's very annoying, If I turn power saving mode off it becomes better, but still has delay. 

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[android-developers] Re: android how to bring our application to foreground when it goes to background?

Not that I am in favor of such a behavior but I've seen apps with parental control feature doing that. They provide something like a controlled sandbox environment as an app (and not as a home screen replacement), so children cannot download stuff or do whatever they want with the device. Whenever you try to leave the app it pops up again. You can see that in action in Famigo.com's app.

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

(GugukluhayaT) .FIKRALAR...ÖZLÜ VE....GÜZEL SÖZLER....&...HARİKA FOTOLAR.... G.

SEVGIYI KEFEYE KOYAN, EKSIKLIGINI HEP HISSEDER.
MUTLU OLMAK ISTIYORSAN ; DÜNÜ BIRAKACAKSIN, YARINI UNUTACAKSIN, BUGÜNÜ
YASAYACAKSIN.
SEVDIGIN SEYI SAVUN , SAVUNDUGUN SEYI SEVME ; ÖGREN.
Unutmak seni!
Dikenli tellerle sarıvermek bedenimi,
Yok etmek göz bebeğimde ki cennetimi,
Öyle bir şey ki, unutmak seni;
Ellerimle dikip kefenimi,
Yaşarken ölmek gibi..! 

Karakterim ve Tavrımı birbirine
karıştırmayınız ! "Karakterim" kim
olduğumla ilgili , "Tavrım" ise sizin kim
olduğunuzla ...!!!!!!

========================================================================

SÜNNETÇİ

Sünnetçinin biri yıllardır kestiği deri parçalarını saklarmış ve bir gün artık emekli olmaya karar vermiş. Elindeki derileri alıp terzinin birine gitmiş ve;
- "Bana bunlardan bir şey yap, manevi değerleri çok fazla" demiş.
Terzi de;
- "Abi sen bir tatile çık gel o zamana kadar ben de siparişini bitiririm" demiş.
Sünnetçi tatile gidip gelmiş ve ilk iş olarak terzinin yanına uğramış.
- "Ne oldu benim sipariş" demiş.
Terzi de sünnetçiye bir cüzdan uzatmış.
Sünnetçi hışımla;
- "Ulan bunca yılın emeği bu küçük cüzdan mı?" demiş.
Terzi hemen cevaplamış;
- "Öyle deme abi, biraz okşayınca valiz oluyor!"

=======================================================================================================

Aslan yıllık izine çıkmadan önce;

'Hareketlidir, hızlıdır, ormanı dolaşıp gelince bana rapor verir' diye düşünüp vekaletini çakala bırakmış.Bunu tüm hayvanlara 'e-mail' atıp bildirmiş.''Çakal vekilimdir, ona saygısızlık ederseniz bana etmiş sayılırsınız,
geldiğimde hesabını sorarım'' diye yazmış.Çakal, ertesi gün büyük havalarda ve çalımla ormanda dolaşmaya başlamış.Bakmış Gergedan su içiyor. Arkasına yaklaşıp bir parmak atmış.
Gergedan hışımla geriye dönmüş, bakmış ki çakal, mail aklına gelince
gıkını çıkartmadan La havle..' çekip yürümüş.Biraz sonra çakal bakmış bir Fil ağaçtan meyve koparıp yiyor.
Ona da yaklaşıp bir parmak atmış. Fil kendine parmak atanı ezmek üzere dönmüş, 
bakmış ki çakal,maili de düşünüp vazgeçmiş.Çakal biraz daha gitmiş, bakmış bir erkek Ayı kovandan bal yiyor.
Gidip ona da parmak atmış. Ayı bir hışımla dönüp çakalı yakalamış,
yatırmış bir güzel bellemiş..Çakal, yalpalaya yalpalaya yürürken bir yandan söyleniyormuş;Ayı oğlu ayı, yine maillerine bakmamış".

=======================================================================================================

''Bildiklerini unut. ” diyor DOST.

Gelal eline bir silgi, şu yeni başlayan güne bilgilerini silmekle başla. ” Zanlarını,yargılarını, önyargılarını ve dahi bütün genellemelerini koy bir çuvala vehepten terk et. Gıybet etme sakın,… bil ki dedikodu denilen şey mıknatıs gibikötü enerji çeker. Kimseninaleyhine konuşma, uzaktan atıp tutma, insanları kem dille yargılama, bil kiyanılırsın.
Birini nekadar çok aşağılar yahut dışlarsan, onun durumuna düşme ihtimalin okadar artar. Kainatın matemetiğidir. Birkoyar, bir alır insan. Bilmedenkendi hesabını dürer ” diyor DOST… ” Hiçbirkonuda emin olma ” Kendiniayrıcalıklı sayma. Konumunaya da mevkine, ismine veya şöhretine güvenme. Şuhayatta tüm zahiri kisveler sabun köpüğünden ibarettir.
Nazlı nazlı yükselir köpük, derken pat diye sönüverir. Herzamanbaşkalarından öğrenmeye açık ol. Eniyi bildiğin konularda bile köşeli düşünme, büyük konuşma. Cümleninsonuna nokta değil, ünlem değil, virgül yahut üç nokta koy. Açıkbir kapı bırak daima. Nekadar bilsen de hiçbirzaman yeterince bilemeyeceğini unutma. Tevazudanşaşma. Ancakozaman kurtulabilirsin bilginin cehaletinden. ” diyor DOST…
Şems-i Tebrizi
=============================================FROM SAİM GÜVEN=========================================

--
You received this message because you are subscribed to the Google Groups "Gugukluhayat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gugukluhayat+unsubscribe@googlegroups.com.
To post to this group, send email to gugukluhayat@googlegroups.com.
Visit this group at http://groups.google.com/group/gugukluhayat.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: [android-developers] Re: Dealing with 1000's of different devices, each one with its own bugs

On 07/31/2013 05:17 PM, Kristopher Micinski wrote:
> Yes. To install Google Play or Google apps, you absolutely are
> required to pass the CTS.
>
> But, from your discussion, the CTS obviously doesn't test all parts of
> the Android platform: it's just a test suite.

Yes, and never will.

It may be a good idea to contact them and ask if they can help in
setting up a bug database for incompatibilities between different
android versions.

No idea on how to contact them.

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [android-developers] Dealing with 1000's of different devices, each one with its own bugs

Hi Thomas,

The bug trackers I proposed are all free to use and cloud bug trackers
(meaning no one has to maintain a server or something).

What's needed are admins for that bug tracker.
Categories can be created when needed.

If there are enough maintainers I think it can be done, the community is
big and if people really care about this issue I don't think it should
be a problem to find some.

If they don't really care so much then we will see no one stepping in,
that's for sure.

regards,
Daniele Segato

On 07/31/2013 06:30 PM, Nobu Games wrote:
> Oops, I sent my reply just to you, so here again for all to see:
>
> on the one hand that's a good idea. On the other hand we would need
> someone who is willing to host and maintain that bug tracker. Setting up
> products, versions etc. is a lot of work in a bug tracking system.
> That's why I think that a wiki has more chances to "take off" with the
> majority of Android developers as users. There are 10.000-something
> different Android devices out there. It's not much of a problem to
> introduce new devices in a wiki. But it takes a whole deal of dedication
> for doing that in a bug tracking system
>
> On Wednesday, July 31, 2013 11:17:48 AM UTC-5, Daniele Segato wrote:
>
> On 07/31/2013 05:58 PM, Nobu Games wrote:
> > I think a central website for collecting known issues and
> workarounds
> > would be a great idea. There are free wiki hosting services that
> could
> > be used for that:
> > https://en.wikipedia.org/wiki/Comparison_of_wiki_hosting_services
> <https://en.wikipedia.org/wiki/Comparison_of_wiki_hosting_services>
>
> I think a wiki is not a good idea for something like this.
>
> More like this:
> http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems
> <http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems>
>
>
> I think we need a bug tracker that allow tagging by vendor, devices,
> device variant, android version and let the user combine those when
> searching.
> It would also be good to have some statistics on those tags/categories.
>
> Jira would be perfect, but it's not free.
>
>
> I can list some, but do not know them well enough to compare or to know
> if they fit:
>
> - Google Code: https://code.google.com/
> - GitHub - the repository can just be a readme - https://github.com/
> - SourceForge - http://sourceforge.net/
>
>
> I'm sure there are others.

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: Sample Code for Purchased Check (App => PHP => App Order-Number Purchased State)?

As a humble start you could tell us what you tried to do and why exactly it doesn't work (error messages etc.). Also be careful with PHP related online tutorials. A lot of beginners provide you with material who do not grasp basic concepts of code / SQL injection and hardening your web service. Maybe you should find a professional PHP developer who codes that for you. Shouldn't take too long to implement.

On Sunday, July 28, 2013 4:38:24 AM UTC-5, AndroidYourself wrote:

Hello, I've read all the API documents many times, I've tried to make it working, but it doesnt work at all. 

I want to make to ask my server (Android APP => HTTP) to connect to Google Play and check whether an customer has purchased the app (User is entering his Order-Number and a PHP script is searching this Order-Number to check the purchased State).

Has anyone a solution for this with a "working sample code" for me? That would be nice.

(Please do not link to documents and complicated Tutorials, I've tried this a lot of days, with no solution).

Thanks in advanced.

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: [android-developers] Dealing with 1000's of different devices, each one with its own bugs

Oops, I sent my reply just to you, so here again for all to see:

on the one hand that's a good idea. On the other hand we would need someone who is willing to host and maintain that bug tracker. Setting up products, versions etc. is a lot of work in a bug tracking system. That's why I think that a wiki has more chances to "take off" with the majority of Android developers as users. There are 10.000-something different Android devices out there. It's not much of a problem to introduce new devices in a wiki. But it takes a whole deal of dedication for doing that in a bug tracking system

On Wednesday, July 31, 2013 11:17:48 AM UTC-5, Daniele Segato wrote:

On 07/31/2013 05:58 PM, Nobu Games wrote:
> I think a central website for collecting known issues and workarounds
> would be a great idea. There are free wiki hosting services that could
> be used for that:
> https://en.wikipedia.org/wiki/Comparison_of_wiki_hosting_services

I think a wiki is not a good idea for something like this.

More like this:
http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems


I think we need a bug tracker that allow tagging by vendor, devices,
device variant, android version and let the user combine those when
searching.
It would also be good to have some statistics on those tags/categories.

Jira would be perfect, but it's not free.


I can list some, but do not know them well enough to compare or to know
if they fit:

- Google Code: https://code.google.com/
- GitHub - the repository can just be a readme - https://github.com/
- SourceForge - http://sourceforge.net/


I'm sure there are others.

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[android-developers] Re: GLSurfaceView lag/delay on Galaxy S3.

Is your render-mode continuously or when-dirty? 

If it is when-dirty, be sure to call surfaceView.requestRender() in your onTouchEvent implementation.

On Tuesday, July 30, 2013 7:14:22 AM UTC-4, Edvinas Kilbauskas wrote:

The best solution to your problem is probably to "bite the bullet" and rewrite your code to use shaders in OpenGL ES 2.0. All major phones and quite a few minor ones support it now.

It may be your only solution, if the Galaxy S3 has to move too many more bits than the P350 did, or has a slower OpenGL client-server path. Or if Motorola took too many shortcuts in maintaining OpenGL ES 1.0 backwards compatibility.

Finally, from this snippet, we cannot tell if you are handling your buffers correctly. For example is 'buffer' a directly allocated ByteBuffer?

This is full code, I optimized it even more, but only making 4 OpenGL calls every frame.

public class MainActivity extends Activity implements Renderer, OnTouchListener {

    private GLSurfaceView surfaceView;

    private FloatBuffer vertices;

    private float x;

    private float y;

    private int SCREEN_WIDTH = 1280;

    private int SCREEN_HEIGHT = 720;

    @Override

    protected void onCreate(Bundle savedInstanceState) {

        super.onCreate(savedInstanceState);

        surfaceView = new GLSurfaceView(this);

        surfaceView.setOnTouchListener(this);

        surfaceView.setEGLConfigChooser(8,8,8,8,8,8);

        surfaceView.setRenderer(this);

        vertices = ByteBuffer.allocateDirect(12 * 4).order(ByteOrder.nativeOrder()).asFloatBuffer();

        vertices.put(new float[]{

                -1,-1,

                 1,-1,

                -1, 1,

                -1, 1,

                 1, 1,

                 1,-1

        });

        vertices.flip();

        setContentView(surfaceView);

    }

    public boolean onTouch(View view, MotionEvent motionEvent){

        x = motionEvent.getRawX();

        y = motionEvent.getRawY();

        return true;

    }

    public void onDrawFrame(GL10 gl){

        gl.glClear(GL10.GL_COLOR_BUFFER_BIT);

        float frustumWidth = SCREEN_WIDTH/100.0f;

        float frustumHeight = SCREEN_HEIGHT/100.0f;

        gl.glLoadIdentity();

        gl.glTranslatef((x/SCREEN_WIDTH)*frustumWidth,(y/SCREEN_HEIGHT)*frustumHeight,0);

        gl.glDrawArrays(GL10.GL_TRIANGLES, 0, 6);

    }

    public void onSurfaceChanged(GL10 gl, int width, int height){

        gl.glViewport(0,0,SCREEN_WIDTH,SCREEN_HEIGHT);

        gl.glMatrixMode(GL10.GL_PROJECTION);

        gl.glLoadIdentity();

        gl.glOrthof(0,SCREEN_WIDTH/100.0f,SCREEN_HEIGHT/100.0f,0,-1,1);

        gl.glMatrixMode(GL10.GL_MODELVIEW);

        gl.glEnableClientState(GL10.GL_VERTEX_ARRAY);

        gl.glVertexPointer(2, GL10.GL_FLOAT, 0, vertices);

    }

    public void onSurfaceCreated(GL10 gl, EGLConfig config){

    }

}

You can't make it any simpler than that, and there is still delay.

Well, I guess I will have to move on to OpenGL ES 2.0, I was actually planning on rewriting that framework in ES 2.0 entirely, but only after I finish this game first. So I guess I have to stop working on my game, and start rewriting my framework now... I HOPE this will do the trick. If not, then i'm screwed, big time.

 

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.