 |
AppletTalk.com Java discussions newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Roedy Green Guest
|
Posted: Tue Feb 07, 2006 4:01 am Post subject: Re: hair shirt literals |
|
|
On Sat, 4 Feb 2006 16:38:28 -0500, "Hal Rosser"
<hmrosser (AT) bellsouth (DOT) net> wrote, quoted or indirectly quoted someone
who said :
| Quote: | why not different font sizes - (to accomodate the minority) - the minority
is color blind.
you understand.
|
I have implemented that. You can see what it looks like in the
listings on my site, particularly the test document at
http://mindprod.com/projects/scid.html
My listings are generated two ways:
1. small ones are converted prior to load to HTML larded with styles.
2. big ones are pre-parsed and stored and stored as a compacted array
of token objects. Each token class knows or computes basic facts like
font, colour, size which a rendering Applet uses to compose the
scrolled image.
The catch is, the way thing work now I have to decide prior to upload
whether to group by 4s or 3s..
--
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching. |
|
| Back to top |
|
 |
Oliver Wong Guest
|
Posted: Tue Feb 07, 2006 7:44 pm Post subject: Re: hair shirt literals |
|
|
"Roedy Green" <my_email_is_posted_on_my_website (AT) munged (DOT) invalid> wrote in
message news:v0lfu1p0fs86qqsjbmdvpldfuctvr9uq3m (AT) 4ax (DOT) com...
| Quote: | On Sat, 4 Feb 2006 16:38:28 -0500, "Hal Rosser"
hmrosser (AT) bellsouth (DOT) net> wrote, quoted or indirectly quoted someone
who said :
why not different font sizes - (to accomodate the minority) - the minority
is color blind.
you understand.
I have implemented that. You can see what it looks like in the
listings on my site, particularly the test document at
http://mindprod.com/projects/scid.html
My listings are generated two ways:
1. small ones are converted prior to load to HTML larded with styles.
2. big ones are pre-parsed and stored and stored as a compacted array
of token objects. Each token class knows or computes basic facts like
font, colour, size which a rendering Applet uses to compose the
scrolled image.
The catch is, the way thing work now I have to decide prior to upload
whether to group by 4s or 3s..
|
You could use some fancy JavaScript and CSS to let the user toggle
between the two. Perhaps even store their preference in a cookie. Just have
both forms, and set one of them to style="visibility: hidden".
I don't know much JavaScript, but maybe there's even a way to detect
locale.
- Oliver |
|
| Back to top |
|
 |
Jeroen Wenting Guest
|
Posted: Thu Feb 09, 2006 12:03 am Post subject: Re: Java finally has a fantastic gui builder |
|
|
"Tor Iver Wilhelmsen" <jadedgamer (AT) hotmail (DOT) com> wrote in message
news:uacd45sh1.fsf (AT) hotmail (DOT) com...
| Quote: | Otis Mukinfus <phony (AT) emailaddress (DOT) com> writes:
What was your question?
Since when did Usenet news articles have to include a question? This
isn't rec.humor.oracle.
|
reads like it more often than not |
|
| Back to top |
|
 |
Barry S Guest
|
Posted: Sun Feb 12, 2006 5:35 am Post subject: Re: Java vs Python.....?? |
|
|
| Quote: | Been hearing a lot about Python from the Linux and OSS community....
Does anyone have any thoughts about Java vs Python...??
|
Well, I use both extensively.
I can say this. Python's biggest failure and biggest benefit is being dynamically typed.
For the less than 500 line program, python rocks. It's quick to flush out ideas in.
It has tremendous library support. It runs on all platforms.
However, once that "prototype" moves to a "production" program, it becomes harder to maintain.
The bugs creep in - sometimes in unforseen ways.
I honestly think that python is a *very* valuable tool.
In an ideal world, all version 1.0 programs should be fleshed out in python.
All version 2.0 programs should be re-written in java.
As we all know, the first version of anything is really deciding *what* the program should do (not how it should do it).
Thats where python shines, its such a quick language to develop in that you never spend time worrying about the nuts & bolts.
Python allows you to very quickly get the 'syntax problems' out of the way and allows you focus solely
on the problem at hand. Java however allows you to build a truly stable application that will seldom fail unexpectedly.
The happiest programs I've written are the ones that started out as python scripts and then migrated themselves to java servlets.
-B |
|
| Back to top |
|
 |
Kent Paul Dolan Guest
|
Posted: Wed Feb 15, 2006 11:12 pm Post subject: Re: response to a recruiter |
|
|
Blair P. Houghton wrote:
| Quote: | Kent Paul Dolan wrote:
Blair P. Houghton wrote:
Could reflecto-laugho on your skillset.
Or on my favoring of nicely formatted text
over slavishly adhering to a W3C standard
which has not yet seen fit to supply a
"continued on next rock" token for URLs.
But they have. It's called "rewrite", and it works as follows:
|
I suppose I fail to see the connection.
xanthian. |
|
| Back to top |
|
 |
Roedy Green Guest
|
Posted: Sat Feb 18, 2006 9:12 pm Post subject: documenting factory methods. |
|
|
On Fri, 17 Feb 2006 14:16:44 +0100, Timo Stamm <timo.stamm (AT) arcor (DOT) de>
wrote, quoted or indirectly quoted someone who said :
| Quote: | http://java.sun.com/javase/6/docs/api/javax/tools/JavaCompilerTool.html
|
That Javadoc is so frustrating. The classes don't have public
constructors, AND Sun keeps it "secret" where they have hidden static
factories.
I would like it if Javadoc did something to strongly encourage the
documenting of factory methods in the place where the constructor
would usually go.
on the class without a constructor you could say
@factory com.mindprod.example.Builder.create( long );
you could have multiple @factory entries.
You could also use the term @factory on a method by itself, declaring
it is a factory for its return type. That would generate Javadoc
notion both on the method that implement the factory and the Classes
it produces.
Details to be worked out so that it does not generate entries on
classes it could never actually generate even if it generates their
interfaces.
--
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching. |
|
| Back to top |
|
 |
Thomas Hawtin Guest
|
|
| Back to top |
|
 |
Roedy Green Guest
|
Posted: Sun Feb 19, 2006 12:12 pm Post subject: Re: documenting factory methods. |
|
|
On Sun, 19 Feb 2006 08:42:49 +0000, Thomas Hawtin
<usenet (AT) tackline (DOT) plus.com> wrote, quoted or indirectly quoted someone
who said :
This is so nuts. How long has it been there. I have been wanting this
since day 1 and never realised it was right under my nose.
--
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching. |
|
| Back to top |
|
 |
Thomas Weidenfeller Guest
|
|
| Back to top |
|
 |
Roedy Green Guest
|
Posted: Fri Mar 03, 2006 11:12 pm Post subject: Versionincrementaphobia |
|
|
In a very simple world, versions would start at 1 and increment each
time a new build was released to the public. Internally there could
be a build number that increments on every global rebuild.
I can see perhaps wanting to distinguish a major release with new
features from just touch ups.
So we would then have release 7.12
But what's with 1.3.1_01?/ do we really need FOUR levels. to
describe perhaps 3 actual releases. Get serious.
All this does is make for extra typing and making it harder to
remember the version numbers.
My own view is that version numbers should be based on date.
so a release today would be 2006.3 and if there were several in the
month, they would be 2006.3.5 and 2006.3.26.
Dates are much more meaningful on how fresh software is than version
numbers. My scheme would let you know instantly whether you likely had
the latest version on hearing the new version number.
--
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching. |
|
| Back to top |
|
 |
Jeroen Wenting Guest
|
Posted: Sat Mar 04, 2006 9:12 am Post subject: Re: Versionincrementaphobia |
|
|
"Roedy Green" <my_email_is_posted_on_my_website (AT) munged (DOT) invalid> wrote in
message news:a6gh02l6ef4javdem0666pad76bllc4cbm (AT) 4ax (DOT) com...
| Quote: | In a very simple world, versions would start at 1 and increment each
time a new build was released to the public. Internally there could
be a build number that increments on every global rebuild.
I can see perhaps wanting to distinguish a major release with new
features from just touch ups.
So we would then have release 7.12
But what's with 1.3.1_01?/ do we really need FOUR levels. to
describe perhaps 3 actual releases. Get serious.
|
You're obviously out of touch with the reality of modern software
development as practiced in the open source world. There you need an
infinite number of levels, and will not be considered a serious player if
you don't release alpha versions of release candidates of beta versions. |
|
| Back to top |
|
 |
Ben Caradoc-Davies Guest
|
Posted: Sat Mar 04, 2006 3:12 pm Post subject: Re: Versionincrementaphobia |
|
|
Jeroen Wenting wrote:
| Quote: | "Roedy Green" <my_email_is_posted_on_my_website (AT) munged (DOT) invalid> wrote in
message news:a6gh02l6ef4javdem0666pad76bllc4cbm (AT) 4ax (DOT) com...
In a very simple world, versions would start at 1 and increment each
time a new build was released to the public. Internally there could
be a build number that increments on every global rebuild.
I can see perhaps wanting to distinguish a major release with new
features from just touch ups.
So we would then have release 7.12
But what's with 1.3.1_01?/ do we really need FOUR levels. to
describe perhaps 3 actual releases. Get serious.
You're obviously out of touch with the reality of modern software
development as practiced in the open source world. There you need an
infinite number of levels, and will not be considered a serious player if
you don't release alpha versions of release candidates of beta versions.
|
The last word goes to the master:
http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXfuture
******
What is the future of TeX?
Knuth has declared that he will do no further development of TeX; he
will continue to fix any bugs that are reported to him (though bugs are
rare). This decision was made soon after TeX version 3.0 was released;
at each bug-fix release the version number acquires one more digit, so
that it tends to the limit pi (at the time of writing, Knuth's latest
release is version 3.141592). Knuth wants TeX to be frozen at version pi
when he dies; thereafter, no further changes may be made to Knuth's
source. (A similar rule is applied to Metafont; its version number tends
to the limit e, and currently stands at 2.718.)
******
--
Ben Caradoc-Davies <ben (AT) wintersun (DOT) org>
http://wintersun.org/
"Those who deny freedom to others deserve it not for themselves."
- Abraham Lincoln |
|
| Back to top |
|
 |
Ian Pilcher Guest
|
Posted: Sat Mar 04, 2006 6:12 pm Post subject: Re: Versionincrementaphobia |
|
|
Roedy Green wrote:
| Quote: | My own view is that version numbers should be based on date.
|
What would the marketing people do?
--
========================================================================
Ian Pilcher i.pilcher (AT) comcast (DOT) net
======================================================================== |
|
| Back to top |
|
 |
Thomas Hawtin Guest
|
Posted: Sat Mar 04, 2006 7:12 pm Post subject: Re: Versionincrementaphobia |
|
|
Roedy Green wrote:
| Quote: |
My own view is that version numbers should be based on date.
so a release today would be 2006.3 and if there were several in the
month, they would be 2006.3.5 and 2006.3.26.
Dates are much more meaningful on how fresh software is than version
numbers. My scheme would let you know instantly whether you likely had
the latest version on hearing the new version number.
|
So, would you not bother with any updates (say security updates) to Java
1.3 and 1.4 once 1.5 had been released? Should 1.5 have been dropped the
first 1.6.0-ea drop?
Tom Hawtin
--
Unemployed English Java programmer
http://jroller.com/page/tackline/ |
|
| Back to top |
|
 |
Andrey Kuznetsov Guest
|
Posted: Mon Mar 06, 2006 12:12 pm Post subject: Re: Versionincrementaphobia |
|
|
Sorry of this reply is a bit OT.
just yesterday I found that some pages contains links to old versions of
Imagero.
And since I move old versions to archive folder, these links points to
nothing.
User can hardly recognize that, aspecial if he don't get any error message -
download just does not start.
After some experimenting I came to following simple idee:
1. define custom error document - for example e404.php
2. parse redirect and try to determine what user wanted.
3. redirect user to proper location.
If some one is interesting - here is sample implementation:
Step 1:
- depends on your provider.
Step 2 and 3:
$redirect = $_SERVER['REDIRECT_URL'];
$appName = "myApp";
$docName = "myAppDoc";
$baseUrl = http://www.myApp.com/;
$downloadDir = "download/";
//do user wants to download myApp?
if(strpos($redirect, $appName ) === false) {
//no, but he wants to download folder
if(!strpos($redirect, "download") === false) {
header("Location: ".$baseUrl.$downloadDir);
return;
}
}
else {
if(!strpos($redirect, ".jar") === false) {
//user want to download myAppXXX.jar
$d = 'download';
$dir=opendir ($d);
//search for myAppXXX.jar
while ($file = readdir ($dir)) {
if(strpos($file, $appName) === false || strpos($file, ".jar") === false)
{
continue;
}
else {
header("Location: ".$baseUrl.$downloadDir.$file);
return;
}
}
}
if(!strpos($redirect, ".zip") === false) {
//it seems that user want to download myAppDocXXX.zip
$d = 'download';
$dir=opendir ($d);
while ($file = readdir ($dir)) {
if(strpos($file, $docName) === false || strpos($file, ".zip") === false)
{
continue;
}
else {
header("Location: ".$baseUrl.$downloadDir.$file);
return;
}
}
}
}
//ok we could not determine what user wanted.
//we can just go to main page or to some error page.
header("Location: ".$baseUrl);
--
Andrey Kuznetsov
http://uio.imagero.com Unified I/O for Java
http://reader.imagero.com Java image reader
http://jgui.imagero.com Java GUI components and utilities |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|