Who's Online |
107 user(s) are online ( 73 user(s) are browsing Forums)
Members: 1
Guests: 106
Maijestro,
more...
|
|
|
|
|
Re: Developers Kit
|
Posted on: 2013/12/30 21:38
#81
|
Just popping in 
|
@TSK
So I tried with setting my CLASSPATH to "CURRDIR:,$cptemp", and it works. So that's not your problem.
You however seem to have a few old libraries:
JAmiga:classpath/lib/classpath/javaio.library: javaio.library 2.1
should be 2.2 2013-07-03
JAmiga:classpath/lib/classpath/javalang.library: javalang.library 2.0
should be 2.1 2013-06-11
JAmiga:classpath/lib/classpath/javanio.library: javanio.library 2.6
should be 2.7 2013-08-22
JAmiga:classpath/lib/classpath/javautil.library: javautil.library 0.12
Have you updated all libraries for JAmiga? (I apparently didn't check for those dependencies for the developer kit.)
If you can't find them in AmiUpdate, I have done something terribly wrong somewhere.
|
|
|
|
|
|
Re: Developers Kit
|
Posted on: 2013/12/30 14:51
#82
|
Just popping in
|
@TSK Quote: [JAmiga ENV variables]
CLASSPATH CURRDIR:,$cptemp Aha! I believe that last $cptemp might destroy things. Try and do this: <code>setenv SAVE CLASSPATH CURRDIR:,</code> The $cptemp thing must have been added by my autoinstall, when an existing classpath env was empty... Or something like that. I'll try to fix that, so no-one else gets the same. But try the setenv, and I hope it'll fix things.
|
|
|
|
|
|
Re: Developers Kit
|
Posted on: 2013/12/30 11:26
#83
|
Just popping in
|
Hmm... again. Quote: Could it be the space in the drive name...? I'm not at my miggy currently, so I can't try it. But that could be one possible reason for failure. It might in that case work if you explicitly tell javac where the source file is: <code>jamiga:javac jamiga:examples/HelloWorld.java</code>
|
|
|
|
|
|
Re: Developers Kit
|
Posted on: 2013/12/30 11:15
#84
|
Just popping in
|
@TSK & JosDuchIt:
Hmm. Perhaps something is wrong with your CLASSPATH ENV-variable.
There are a few things needed in order to make it work:
1. The "CURRDIR:" assign needs to be in the CLASSPATH ENV variable.
2. The CLASSPATH ENV variable must be in uppercase. Even if the Amiga command getenv ignores the case, the internal getenv used by JamVM doesn't.
I tried to make my AutoInstall script fix these issues, even if you had your own CLASSPATH set.
So, please check these things:
<b>1. Check uppercase CLASSPATH ENV</b>
In CLI do:
<code> dir ENV:classpat#?</code>, and
<code> dir ENVARC:classpat#?</code>
Both should return CLASSPATH in uppercase:
<code> CLASSPATH</code>
If its in lowercase, please rename the files (or delete them both, and do the setenv thing below.)
<b>2. Check CURRDIR in CLASSPATH ENV</b>
In CLI do:
<code> getenv CLASSPATH</code>
It should return something like
<code> CURRDIR:,</code>
or, CURRDIR: followed by your previous settings
<code> CURRDIR:,JAmiga:,Work:blabla/,[other drawers you might have added]</code>
If it doesn't have CURRDIR:, please set the CLASSPATH ENV to "CURRDIR:," (or add it to the beginning of whatever you have).
<code> setenv SAVE CLASSPATH CURRDIR:</code>, or
<code> setenv SAVE CLASSPATH CURRDIR:,JAmiga:,Work:blabla/,[other drawers you might have added]</code>
If that doesn't solve it, please double-click JAmiga:JAmiga, and paste the output here.
You might also try running the ECJ compiler on its own (if you look in the JAmiga:javac script file, this is basically what is done):
<code> jamiga:jamvm -jar JAmiga:lib/ecj-4.3.jar</code>
This should give some version info and help. If it doesn't something is very wrong.
|
|
|
|
|
|
Developers Kit
|
Posted on: 2013/12/29 21:13
#85
|
Just popping in
|
On AmiUpdate you can find an update consisting of a few developer's files. There's a new Java compiler, a simple example, as well as documentation.
Just update your system, go to JAmiga:Documents/Developer.guide, and you're just minutes away from compiling your own applications.
I'll try to add more info on how you can use it with various third-party jar files.
|
|
|
|
|
|
Re: JamVM bug
|
Posted on: 2013/11/8 22:34
#86
|
Just popping in
|
Hi, sorry for my late reply. But I think I got this working, or at least running, with the latest updates from AmiUpdate. Quote: Filer:3e-partsprojekt/epubcheck-3.0.1> jamiga:jamvm -jar epubcheck-3.0.1.jar
Epubcheck Version 3.0.1
At least one argument expected
-help displays help
The tool will EXIT
Filer:3e-partsprojekt/epubcheck-3.0.1> jamiga:jamvm -jar epubcheck-3.0.1.jar -help
When running this tool, the first argument should be the name (with the path) of the file to check.
If checking a non-epub file, the epub version of the file must be specified using -v and the type of the file using -mode.
The default version is: 3.0.
Modes and versions supported:
-mode opf -v 2.0 // For single OPF file validation (EPUB 2)
-mode opf -v 3.0 // For single OPF file validation (EPUB 3)
-mode xhtml -v 2.0 // For single XHTML file validation (EPUB 2)
-mode xhtml -v 3.0 // For single XHTML file validation (EPUB 3)
-mode svg -v 2.0 // For single SVG file validation (EPUB 2)
-mode svg -v 3.0 // For single SVG file validation (EPUB 3)
-mode nav -v 3.0 // For single 'Navigation Document' validation
-mode mo -v 3.0 // For single 'Media Overlays' validation
-mode exp // For validating expanded EPUB archives
This tool also accepts the following flags:
-save = saves the epub created from the expanded epub (-mode exp)
-quiet = no message sent to stdout, only errors in stderr
-out <file> = ouput an assessment XML document in file (experimental)
-? or -help = displays this help message
Epubcheck Version 3.0.1
-help displays help
No file to check was specified in arguments
The tool will EXIT
I'm not sure what to do with it though. :) If you ahve a real use, please try it out! The bug with executing JAR files with the current directory set to the root of a drive, is however still there. This won't work: Quote: cd ram:
jamiga:jamvm -jar file.jar This however will: Quote: jamiga:jamvm -jar ram:file.jar I think I know where that problem might lie, so I'll look into it. Thank you for the bug report! Keep 'em coming!
|
|
|
|
|
|
Re: AmiUpdates for JAmiga available
|
Posted on: 2013/11/7 8:04
#87
|
Just popping in
|
@kas1e Quote: Btw, can i download somewhere that simple telnet client on which you do your tests before ? (so can try as well) I just made a small test, and it also doesn't work.  Or, that might actually be a good thing, since I've probably changed something that broke it. So I should just be able to diff and find out what I changed.
|
|
|
|
|
|
Re: AmiUpdates for JAmiga available
|
Posted on: 2013/11/7 6:56
#88
|
Just popping in
|
@kas1e I've looked at it, but not very thoroughly. I do however think that I might have experienced a similar problem, and it has something to do with how I read stuff from the console. I had a telnet client working, have to see if it still works though. So, I think it's a problem with JAmiga, and not jtelnet. I quickly looked at the console stream reading code of jtelnet, and it doesn't seem to be doing anything utterly quirky. So it should work. I'll keep investigating.
|
|
|
|
|
|
AmiUpdates for JAmiga available
|
Posted on: 2013/11/6 22:25
#89
|
Just popping in
|
Ok, so, I managed to ship a few erroneous files with the release.  Please AmiUpdate your JAmiga installation! You who have reported bugs and quirks, please try again after update (have you experienced crashes, please reboot as well).
|
|
|
|
|
|
Re: New JAmiga release: 1.2
|
Posted on: 2013/11/6 19:24
#90
|
Just popping in
|
@Raziel
For now, nothing with graphics will run. In the future? Hopefully, yes!
|
|
|
|
|
|
Support forum: JAmiga
|
Posted on: 2013/11/6 19:22
#91
|
Just popping in
|
Welcome to the support forum for JAmiga - Java for AmigaOS! This is the place to ask question on what JAmiga is, how it works, why it doesn't work, and also more general Java developer questions. Bug reportingIf you have bug reports, with crashlogs, please use the os4depot crashlog area, and please state which JAR files you ran, and where it can be downloaded. By double-clicking the JAmiga:JAmiga icon, you'll get info on which library and binary versions are in use. Always make sure you're properly AmiUpdated, and have the latest versions installed. If you've experienced crashes, and the update, please reboot since old libraries might still be loaded. LinksThe main page for JAmiga is the blog: http://jamiga2.blogspot.se/JAmiga is available on os4depot/development/language/jamiga.lha
|
|
|
|
|
|
Re: New JAmiga release: 1.2
|
Posted on: 2013/11/6 9:23
#92
|
Just popping in
|
@Hans Quote: I think that the problem might have something to do with jamvm using ":" as a separator when defining the classpath. This works fine with *nix, but on AmigaOS, the ":" is used when addressing drives/partitions.
[...]
All of this suggests that the colon character is causing trouble. Yep, I'm painfully aware of this.  In JAmiga I've changed to using comma as the separator, but there are obviously places where the colon sin't treated as I want it to. I think I've fixed it in the JVM (i.e. the jamvm executable), but there's still a few Java classes that handle the colon in ways I don't want it to.
|
|
|
|
|
|
Re: New JAmiga release: 1.2
|
Posted on: 2013/11/6 6:34
#93
|
Just popping in
|
@kas1e Quote: Maybe there just some different option, not -classpath, and not -cp, but something else ? As well as why it didn't works after i unpack it and run directly ? It all seems like something wrong with amiga native patches. I.e. all those adding of :/ and :/. imho make problems, dunno ..
Yes, there are evidently problems with amiga paths. Perhaps you could try to give an absolute path. Something like: Quote: jamiga:jamvm -cp ram:jtelnet.jar Also, there seems to be an issue with using the drive as root, given the slash that gets added: "ram:/jtelnet.jar". Perhaps just put the jar in a drawer in ram:? And that awful dot! Thought I had that fixed... Quote: Is there any reasons, why someone didn't include Manifest files by default ? Might be that there is no main method to be run? I.e. the jar file should really be used as a library? Or there's simply several possible main methods. I'll try to have a look at this tonight, had no amiga time yesterday.
|
|
|
|
|
|
Re: New JAmiga release: 1.2
|
Posted on: 2013/11/5 20:54
#94
|
Just popping in
|
Quote: Do you have any plans to create an arexx class similar in nature to the python arexx module?
If java programs could send arexx commnds and create arexx hosts then a lot of extra possibilities open up, incuding creating GUIs with proaction, and interaction with existing software. Yes, this is planned as well. Specifically with proaction in mind. I'm thinking of a general JAR-file, available also for platforms not supporting arexx, with reasonable graceful degradation. I.e. Non-amiga users would also benefit from amiga develoeprs creativity, just not quite as smart. 
|
|
|
|
|
|
Re: New JAmiga release: 1.2
|
Posted on: 2013/11/5 14:30
#95
|
Just popping in
|
@kas1e Thanks for trying it out! I will try to assemble some more information on how to develop and test stuff. I also have a developer kit planned. Quote:
jamiga:jamvm -jar jtelnet-withall.jar thor.app.telnet 192.168.1.1
Couldn't find Main-Class attribute in jtelnet-withall.jar Manifest.
This still tries to run the JAR-file, since you're using the "-jar" argument. Like others have said, this requires a manifest file. Instead, you coud try to run the class explicitly, and adding the JAR-file to your classpath, using the ".classpath" argument. Something like this (can't try it myself atm):
jamiga:jamvm -classpath jtelnet-withall.jar thor.app.telnet 192.168.1.1
To explain it utterly simplified: running a JAR-file without a Manifest file, is like trying to execute an Amiga library. So, when not having a Manifest file that points out the class containing the main-method (which is basically the same as a C main-function), you have to explicitly tell jamvm which to execute.
|
|
|
|
|
|
Re: New JAmiga release: 1.2
|
Posted on: 2013/11/4 22:48
#96
|
Just popping in
|
Quote: [...]it complained about AWT.
[...]is it planned or simply unrealistic ? Don't worry. Its planned. I won't tire you with yet another "when it's done", but... well... it is an appropriate response. I'll either continue what was started back in 2003-2004 by Peter Werno, or do a new implementation, looking at combining a GNU Classpath and OpenJDK implementation. (GNU Classpath being the "older", Java 5-only class library currently used by JAmiga, and OpenJDK being the official class library by Oracle with support for Java 8 and beyond.) Most likely I'll start looking at what was done, and take it from there.
|
|
|
|
|
|
Re: About Icons, automated Effects and why it will never work
|
Posted on: 2013/8/8 19:24
#98
|
Just popping in
|
Quote: why should the icons glow at all? Do they start burning when you select them or what? Where did the metaphor come from? I think it surfaced when the Workbench allowed for the frames to be removed. There was a need to indicate a selected icons, besides changing its appearance. I like the glow, i even have it on my windows: http://2.bp.blogspot.com/-1C9K-k0vmbI ... XEA/s1600/twitterdone.png
|
|
|
|
|
|
Re: A shortcut to Dropbox in AmigaOS
|
Posted on: 2013/8/7 6:11
#99
|
Just popping in
|
Another way might be to use the official Java API: https://www.dropbox.com/developers/core/sdks/javaHaven't managed to try it myself yet, but it shouldn't take many code lines to know whether it'll work or not. If something is missing in JAmiga, I can always add it.
|
|
|
|
|
|
Re: JAmiga beta-release
|
Posted on: 2013/8/1 19:51
#100
|
Just popping in
|
Quote: btw, I'm Chris_Y not ChrisH Oups. Sorry! Updated blog. And, its not a very big update, just that I wanted to get an AmiUpdateable version out there, so I don't have to create a new big release for each little update.
|
|
|
|
|
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
