Infeasible
Status Update
No update yet.
Comments
lb...@gmail.com
I need imageio to use the geotiff-jai library for extracting GeoTIFF tags so I can
create a KML server.
create a KML server.
gh...@google.com
Also the native implementation of javax.imageio and the associated Sun jai-imageio
stuff eg com.sun.media.imageio.plugins.*.
This will significantly speed up image processing and will reduce used CPU hours/load
(which will be beneficial to Google too)
stuff eg com.sun.media.imageio.plugins.*.
This will significantly speed up image processing and will reduce used CPU hours/load
(which will be beneficial to Google too)
lb...@gmail.com
How about using a pure Java imaging library? For example, is anybody willing to try
Sanselan and see if it meets their needs?
http://incubator.apache.org/sanselan/site/index.html
Sanselan and see if it meets their needs?
lb...@gmail.com
Thanks for that link sounds interesting.
It's amazing what you can find on Apache these days!
Hmm, it could be very usefull for people after a pure Java replacement for ImageIO.
Pnly problem I have is that it doesn't have a GeoTIFF wrapper, but I'm sure that
won't be too hard.
May I suggest a wiki page be created with a list of alternative class libraries for
the blacklisted java.* classes?
I would still prefer the ImageIO classes be accessible (along with the other
blacklisted standard java.* packages...) as ImageIO allows for a speedy native
implementation of the core algorithims. And is generally more compatible with a lot
of existing software.
Only reason I can see this being blacklisted is because you want to force us to user
your imaging API which is billable (per call).
It's amazing what you can find on Apache these days!
Hmm, it could be very usefull for people after a pure Java replacement for ImageIO.
Pnly problem I have is that it doesn't have a GeoTIFF wrapper, but I'm sure that
won't be too hard.
May I suggest a wiki page be created with a list of alternative class libraries for
the blacklisted java.* classes?
I would still prefer the ImageIO classes be accessible (along with the other
blacklisted standard java.* packages...) as ImageIO allows for a speedy native
implementation of the core algorithims. And is generally more compatible with a lot
of existing software.
Only reason I can see this being blacklisted is because you want to force us to user
your imaging API which is billable (per call).
Description
Version of Gradle Plugin:
Version of Gradle:
Version of Java:
OS:
Android Studio 4.2.1
Build #AI-202.7660.26.42.7351085, built on May 10, 2021
Runtime version: 11.0.8+10-b944.6842174 amd64
VM: OpenJDK 64-Bit Server VM by N/A
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 8048M
Cores: 12
Registry: external.system.auto.import.disabled=true, ide.settings.move.mouse.on.default.button=true, debugger.watches.in.variables=false
Non-Bundled Plugins: GenerateSerialVersionUID, String Manipulation, com.dubreuia, org.jetbrains.kotlin, com.google.mad-scorecard, com.ppismerov.ksvu, izhangzhihao.rainbow.brackets, org.intellij.plugins.markdown
Steps to Reproduce:
1. Import the project from:
2. set as comment to the old "queries", and add the manifest part of the queries with what's suggested on:
3. Run app.
4. Remove the useless comments.
At some point here, I got the Kotlin code (which I didn't change or even look at) to be stuck on "analyzing", not letting me do any auto-suggestions/completions, and not being able to reach stuff either (CTRL+click) , and many other common things on Kotlin code.
Attached the project AFTER the modifications.