headers
Jayson Vantuyl | 1 Feb 2003 20:14

Laundry List Of Problems

In 5 hours (6pm CST) I'm supposed to be giving a presentation on using XWT and
a Python XMLRPC server for rapid application development to our local Linux
Users Group.

Unfortunately, nothing works right.

I can't even reach the Wiki (the server can't seem to find the / page!).  I
can't build XWT correctly (it appears that the Windows version can't decode a
perfectly good XWAR (gives exception in Main.main():
java.util.zip.ZipException: bad/missing magic number at end of .zip entry).
The Linux version just says Detecting JVM and then Aborting.  The launcher
appears to not exist.  The launcher on xwt.org for the demos just completely
fails (Tomcat can't find the script?).  I only just found dist.xwt.org
(completely from memory on a hunch) and I'm getting down to writing my
examples.  FYI, I started at 8am.

Needless to say, this state of things makes it really difficult to demo this
stuff.  Any help would be appreciated.  Also, when the whole
launcher/dist.xwt.org thing gets the way we want it, PLEASE update the
reference.

Hopefully, I can pull this off, but I thought my experience might inspire some
bug squashing in.  I push XWT really hard to some of the people I meet.  I
wonder how many of them never pursue it because they can't even load the
Demos...

Normally, I'm the kind of guy to submit a patch.  Regrettably, the wiki and
launcher stuff is not something anyone but Adam can fix.  As for the
build problems, I could use some tips here.  I haven't CVS'd the older version
of the gcc source yet (I suspect that may fix the above problems).  Has anyone
(Continue reading)

Permalink | Reply | 5 comments |
headers
Emiliano | 1 Feb 2003 20:42
Picon

Re: Laundry List Of Problems

On Sat, Feb 01, 2003 at 01:14:42PM -0600, Jayson Vantuyl wrote:

> Needless to say, this state of things makes it really difficult to demo this
> stuff.  Any help would be appreciated.  Also, when the whole
> launcher/dist.xwt.org thing gets the way we want it, PLEASE update the
> reference.
> 
> Hopefully, I can pull this off, but I thought my experience might inspire some
> bug squashing in.  I push XWT really hard to some of the people I meet.  I
> wonder how many of them never pursue it because they can't even load the
> Demos...

You might want to try IE or an older Netscape. I've been having
intermittent problems with Mozilla myself.

> Normally, I'm the kind of guy to submit a patch.  Regrettably, the wiki and
> launcher stuff is not something anyone but Adam can fix.

I posted a patch that allowed one to run a private launcher a while ago.
I have one pre-built if you want it. It includes all you need from
launch.xwt.org and dist.xwt.org. It's about 6 megs big; I could post it
on a website. You can bypass the launcher, BTW, and always load the
applet.

Emile

_______________________________________________
http://lists.xwt.org/listinfo/dev
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andrew Kohlsmith | 1 Feb 2003 20:50

Re: Laundry List Of Problems

> I can't even reach the Wiki (the server can't seem to find the / page!).  I

Hardware troubles.

> can't build XWT correctly (it appears that the Windows version can't decode
> a perfectly good XWAR (gives exception in Main.main():
> java.util.zip.ZipException: bad/missing magic number at end of .zip entry).

Yes.  Take an old CVS snapshot and replace Resource.java with the old one.  
Adam is trying to use a different zip engine from the jazz one, and there are 
some issues in it.  Rework the makefile to include the jazz stuff and you're 
done.  Please _ensure_ you rm -rf bin bin-Linux (dont use ant clean) before 
building or you'll get all kinds of goofy problems.

> The Linux version just says Detecting JVM and then Aborting.  The launcher
> appears to not exist.  The launcher on xwt.org for the demos just
> completely fails (Tomcat can't find the script?).  I only just found
> dist.xwt.org (completely from memory on a hunch) and I'm getting down to
> writing my examples.  FYI, I started at 8am.

I have a working engine now.  I have working xwars and so on (nothing that 
connects to the server).  http://xwt.mixdown.ca and 
http://www.mixdown.ca/~xwt -- I will try and put my working CVS up there as 
well.

> Needless to say, this state of things makes it really difficult to demo
> this stuff.  Any help would be appreciated.  Also, when the whole
> launcher/dist.xwt.org thing gets the way we want it, PLEASE update the
> reference.
(Continue reading)

Permalink | Reply | 3 comments |
headers
Jayson Vantuyl | 1 Feb 2003 23:47
Gravatar

Re: Laundry List Of Problems

On Sat, Feb 01, 2003 at 02:50:17PM -0500, Andrew Kohlsmith wrote:
> > I can't even reach the Wiki (the server can't seem to find the / page!).  I
> Hardware troubles.
Gotcha.

> Yes.  Take an old CVS snapshot and replace Resource.java with the old one.  
> Adam is trying to use a different zip engine from the jazz one, and there are 
> some issues in it.  Rework the makefile to include the jazz stuff and you're 
> done.  Please _ensure_ you rm -rf bin bin-Linux (dont use ant clean) before 
> building or you'll get all kinds of goofy problems.
Mmmmmm.  Don't have an old CVS copy.  Never had to build it before.

> I have a working engine now.  I have working xwars and so on (nothing that 
> connects to the server).  http://xwt.mixdown.ca and 
> http://www.mixdown.ca/~xwt -- I will try and put my working CVS up there as 
> well.
Okay.  I will be using some of those.  May I say that they look very
good (the sales.xwar in particular).

> I had a demo for the local PerlMongers chapter and had the same issues.  I 
> used a local mirror at the time.
Yeah.  I'm thinking that when the Wiki becomes available, we need to
have a BootStrappingXwt page that has all of these caveats (especially
the building ones) in it.

Jayson

_______________________________________________
http://lists.xwt.org/listinfo/dev
(Continue reading)

Permalink | Reply | 0 comments |
headers
Charles Goodwin | 3 Feb 2003 13:15
Picon

Re: <static> scope

test1.xwt :
 
<xwt>
    <static>
        var TEST = "testing123";
    </static>
</xwt>
 
test2.xwt :
 
<xwt>
    <preapply name="test" />
    <template>
        static.TEST = "poop";
        xwt.println( "test2 " + static.TEST );
    </template>
</xwt>
 
test3.xwt :
 
<xwt>
    <preapply name="test" />
    <template>
        xwt.println( "test3 " + static.TEST );
    </template>
</xwt>
 
test4.xwt :
 
<xwt>
    <template>
        <test2 />
        <test3 />
    </template>
</xwt>
 
xwt-log :
 
               test2: test2 poop
               test3: test2 poop
 
Looks like that answers my query. :)
_______________________________________________
http://lists.xwt.org/listinfo/dev
Permalink | Reply | 0 comments |
headers
Charles Goodwin | 3 Feb 2003 14:43
Picon

Re: RFC: Profiler functions in engine

You should be able to use the Date object for this.

datestamp = xwt.date();
timestamp = datestamp.getMilliseconds();

References:

xwt.date() in XWT Reference
http://www.xwt.org/reference.html

Date object in Netscape DevEdge JS 1.5 Reference
http://devedge.netscape.com/library/manuals/2000/javascript/1.5/reference/date.html

(hehe I know we discussed this in #xwt but I couldn't help myself.)



-----Original Message-----
From: Andrew Kohlsmith [mailto:akohlsmith-xwt <at> benshaw.com]
Sent: 31 January 2003 16:17
To: dev <at> xwt.org
Subject: [xwt-dev] RFC: Profiler functions in engine


Does anyone else see the need for some helper functions in the engine for
profiling xwt applications?

I was thinking of xwt.startTimer(), xwt.stopTimer() and xwt.timerNote()
functions.

startTimer() and stopTimer() would each take one string argument.  This would
be an identifier which is used to tie a start and stop together so that
multiple threads can be profiled.

timerNote() would take one or two strings: the identifier as mentioned above,
and just some aribitrary text.  If only one string is given, the current
timestamp and the text would be spit out on the console.

How it would work:

xwt.startTimer("matching");
...
...
if(interesting) xwt.timerNote("matching", "something interesting happened");
...
...
xwt.stopTimer("matching");

The resultant console output would look something like this:

11:13:08.781 matching started
11:13:09.434 matching: something interesting happened  (0.653s)
11:13:11.094 matching ended (2.313s)

I am thinking of getting our co-op student to add this to the engine code --
if done, would it be something that would be accepted into CVS?

Regards,
Andrew

_______________________________________________
http://lists.xwt.org/listinfo/dev 

_______________________________________________
http://lists.xwt.org/listinfo/dev
Permalink | Reply | 0 comments |
headers
Adam Megacz | 3 Feb 2003 14:54

xwt.org back up to full functionality


Okay, everything should be working again (including demos and the wiki).

Sorry about this; thanks for your patience.  I'll reappear in a few
days; right now I'm frantically trying to lay slate tile in my new
apartment before I get kicked out of my old one.

  - a

_______________________________________________
http://lists.xwt.org/listinfo/dev
Permalink | Reply | 1 comment |
headers
Andrew Kohlsmith | 3 Feb 2003 15:03

Re: xwt.org back up to full functionality

> Okay, everything should be working again (including demos and the wiki).

Thanks for the effort Adam, I am sure there are many people besides me happy 
to see this!  

Regards,
Andrew

_______________________________________________
http://lists.xwt.org/listinfo/dev
Permalink | Reply | 0 comments |
headers
Charles Goodwin | 3 Feb 2003 17:08
Picon

Publicity

http://www.osnews.com/comment.php?news_id=2708

We need to get this kinda publicity going.  Although I think we should have the widgets / demos tidied up first.  I'm working on some of the widgets and ideas.  Now I've answered my own <static> scope question, I'm modifying the 'simple' theme to change colours live.  I'll also try and get most of the widgets working with it. :)

It's good to have the launcher back up... there was quite a few people looking at XWT only to be rebuffed by the broken launcher and (hence) lack of demos.

Also, I've started the project xwt-services at http://sourceforge.net/projects/xwt-services to host some complimentry xwt stuff.  Emiliano has created a PHP launcher that he'll put up there whenever he's back online.  Basically it's just for community stuff without pushing it onto Adam or his servers.  If you have anything you want to go up there then email me.

I want to start collecting themes there too.

Cheers,

Charlie. 

_______________________________________________
http://lists.xwt.org/listinfo/dev
Permalink | Reply | 0 comments |
headers
Adam Megacz | 4 Feb 2003 01:44

Re: Signed applet/activex component


Emiliano <emile <at> iris-advies.nl> writes:
> If at all possible, I'd like to be able to run xwt without escalated
> privileges.

You can't make TCP connections to machines other than the one you came
from without escalated privs.  You also lose
xwt.openFile()/xwt.saveFile(), and all your windows have this ugly
"this is an applet" tag stuck on them.  Finally, you can't use native
builds (they require Runtime.getRuntime().createProcess()).

  - a

_______________________________________________
http://lists.xwt.org/listinfo/dev
Permalink | Reply | 6 comments |

Gmane