dynapi-dev — List related to the current DynAPI Core development

[Dynapi-Dev] [ dynapi-Bugs-762495 ] Wrong position retured when page has been scrolled down.

[SourceForge.net <no...@so...>]

Bugs item #762495, was opened at 2003-06-28 22:31
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757

Category: DynAPI 3 API
Group: Unverified
Status: Open
Resolution: None
Priority: 5
Submitted By: Sam Blum (bs_php)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong position retured when page has been scrolled down.

Initial Comment:
Reproduced the bug in IE and Mozilla 1.3

To see the effect, open the dynapi example:
examples/dynapi.api.mouseevent.html 
- You should see some colored layers that are cascaded 
in each 
  other in the middle of the page. 
- On the left we have some links to turn mouse-events 
on and off.
- The debugger window should open as well.

The page contains so much info, that a standard scroll-
bar should appear on the right of the browser. If not 
make the browser window less high.

Now do as follows:
A) Turn on the click/dblclick events for the blue layer. 
   This is done by clicking on the 
      "Listen to click/dblclick events -> blue -> on" 
   link (see the page)

B) Then click on the blue layer top left corner and look 
   at the output on the debugger window. It should say 
   something like this: 
   "click blue xy=0,0 pXY=300,200 origin=blue"

   NOTE: 
   xy are the coordinates of the click on the blue layer 
   relative to it's own top left corner. pXY are the 
   absolute coordinates relative to the view (top left 
   corner of the browser).

C) Now scroll down a little and click again on the blue 
   layer (try to hit the same spot). Now in the debugger 
   window look at the result: 
   "click blue xy=0,-148 pXY=300,52 origin=blue"

BUG: 
  Compare the xy result 0,0 and 0,-148. I would have 
  expected to get the same result in case A) and B) 
  for xy (the pXY results are OK). But the y axis has 
  a negative number, caused by the scrolling.
  
  
Side Effect Bug:  
  Next I modified the code and set the red layer 
to 'relative'
  Thus, I added line:  red.setPosition('relative');
  This will position the layers at the bottom of the 
  page. Again try to repeat B) and C) (as good as you 
can) 
  and compare the results:
    "click blue xy=8,496 pXY=308,696 origin=blue"
    "click blue xy=8,396 pXY=308,596 origin=blue"

The effect is the same AND a *side effect* shows up:
alway have an x offset of 8px (13px on IE). But I heard 
that reletive posistioning is problematic.

-- bs_php

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757

Re:[Dynapi-Dev] Documentation Stratagy for DynApi; is there one? ?

[Leif W <war...@us...>]

Hey,

This thought just occured to me since I'm working on the server side stuf=
f at
the moment.  What about the documentation there?  For example, the client=
 side
docs for IOElement look pretty complete, but there's no server-side docs,=
 just
source code with sparse documentation.  But in the dialogue about
documentation generation -- the server-side is going to have various lang=
uages
(PHP, Perl, ASP, TCL, etc.) -- what's the plan for having docs generated =
for
these additional languages?

Another thought that occured to me earlier.  It would be cool to have som=
e
sort of front end program (written in DynAPI?) that collected together th=
ings
such as documentation generation, source compression, etc.

Looking for doc volunteers?  I'm not too familiar with anything but the S=
napX
since that's all I wrote, but if it can be of help, tell me the format of=

comments and I can take care of that.  Otherwise, there's some comments i=
n
there already, maybe just needs some reformatting.  If there's any questi=
ons
feel free to ask.  If it's just a matter of data entry or grunt work, I c=
ould
help out if descriptions are provided to me, so I could go in and drop
comments in place in proper format.

Leif

P.S. I go on vacation from July 3rd to 9th, so I'll not be around then.


Raymond Irving <xw...@ya...> wrote:
> =

> --- Dan Willemsen <da...@wi...> wrote:
> > =

> > Quoting Darin Kadrioski
> > <DKa...@lm...>:
> > =

> > > http://sourceforge.net/projects/jsdoc/
> > =

> > nice... the only question i have is whether it will
> > parse some of the javascript
> > that we use in dynapi, some of it isn't all so
> > well-formed according to it's
> > definition i don't think
> =

> "...With the exception of the rules stated above how
> you document your code is not a matter of concern to
> the parser...."
> =

> As long and the comments follow the jsDoc rules then
> the DynAPI files will work great!
> =

> I think this a good start for the source codre
> documentation.
> =

> The question now is who are the persons that will be
> working on the source code documentation?  Dan I guess
> your in on this one?
> =

> =

> --
> Raymond.
> =

> > --
> > Dan Willemsen
> > =

> > =

> > =

> >
> -------------------------------------------------------
> > This SF.Net email sponsored by: Free pre-built
> > ASP.NET sites including
> > Data Reports, E-commerce, Portals, and Forums are
> > available now.
> > Download today and enter to win an XBOX or Visual
> > Studio .NET.
> >
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/0=
1
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> >
> http://www.mail-archive.com/dyn...@li.../
> =

> =

> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
> =

> =

> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/0=
1
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
> =

Re[2]: [Dynapi-Dev] Documentation Stratagy for DynApi; is there one? ?

[<sp...@4m...>]

 [Dynapi-Dev] Documentation Stratagy for DynApi; is there one??

Following comment to the suggestion of using 
'jsdoc' as documentation tool:

'jsdoc' is an half dad 2year old project!
An eary beta staged SW with only a minimum on 
functionallity and hardly any doc.

And look at the statistics of 'jsdoc':
http://sourceforge.net/project/stats/?group_id=30801
300 lausy downloads, 0 bug corrections in 2 years and 
falling intrest of the community.

Put this in relation to a living project like the phpDocumentor 
http://sourceforge.net/project/stats/?group_id=11194
with 19'548 downloads and 554 bug correction over 
the last 3 years and ask your self what you want to bet 
your money on.

DON'T REALY ON 'jsdoc'! 

I still hope to get more feedback on my offer to help 
out with a php solution. NOTE: PHP can now be used 
as standalone script interpreter (just like perl). 


> this is the type of thing I have been planning to do to generate 
> the quickref documentation, but haven't been able to yet.  
> I just found phpDocumentor yesterday, and was thinking 
> about writing another parser for it, javascript, but
> that looks like to much work for me.
> --
> Dan Willemsen

My suggestion is not about changing the code of 
phpDocumentor. Just want to make that clear.
I change the js-code to look like PHP code and then 
use the phpDocumentor to parse the doc from it 
(See below)

--
Regards Sam 

=========================================
> 
> --- Darin Kadrioski <DKa...@lm...>
> wrote:
> > http://sourceforge.net/projects/jsdoc/
> 
> Well this is something to look into for those working
> on the Docs for DynAPI.
> 
> --
> Raymond Irving
> 
>
> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On
> Behalf Of
> sp...@4m...
> Sent: Thursday, June 26, 2003 4:36 PM
> To: dyn...@li...
> Subject: [Dynapi-Dev] Documentation Stratagy for
> DynApi; is there one??
>
> Documentation Stratagy for DynApi; is there one??
> =================================
> 
> How do *you* plan to document DynApi code? 
> 
*snip*
> But I'm not aware that anthing exsists for js. So
> wath I did is: I wrote a simple converter that converts 
> js to PHP. Not 100% but good enough for
> the phpDocumentor to think it's valid PHP and let
> the converter do the HTML/PDF documenting 
> rendering work (including links aso).
> 
> The 'drawback' (if you can say so) is that I needed
> to write js code in a form that makes it easy to detect 
> classes and methods. My suggestion is following 
> code style:
> 
> /**
> * This is a sample class.
> * 
> * @example example_1.html
> *
> * @author    xxx
> * @package   core
> * @subpackage fx
> * @copyright LGNU
> */
> aClass = function() {
>   
>   /**
>   * Follwing is a short description.
>   * A longer description goes here.
>   * 
>   * @access public 
>   * @param object e Any object
>   * @return void
>   * @see onpathrun(), onpathstop()
>   */
>   this.onpathstart = function(e) {
>     status = start;
>   }
>   
>   // a.s.o.
> 
> }
> 
> I forgot to mention that the js files must go
> through a stripper. The  stripper removes all 
> comments and (if intelligent) can squeeze the
> js to a max. The striped js code is for productive
> use. While the original files stay commented!
> 
> In this way the doc and the source stay in sync.
> Separating code form doc is a very very dangerous 
> and will cause head acks for everybody! 
> 
> If you are thinking of maintaining doc separate from
> source, please, *please* over think you strategy. 
> I on my side am willing to share my
> knowledge on how to strip the js-code and give you a
> hand on the converter and phpDocumentor.

Re[2]: [Dynapi-Dev] Documentation Stratagy for DynApi; is there one? ?

[<bs...@in...>]

 [Dynapi-Dev] Documentation Stratagy for DynApi; is there one??

Following comment to the suggestion of using 
'jsdoc' as documentation tool:

'jsdoc' is an half dad 2year old project!
An eary beta staged SW with only a minimum on 
functionallity and hardly any doc.

And look at the statistics of 'jsdoc':
http://sourceforge.net/project/stats/?group_id=30801
300 lausy downloads, 0 bug corrections in 2 years and 
falling intrest of the community.

Put this in relation to a living project like the phpDocumentor 
http://sourceforge.net/project/stats/?group_id=11194
with 19'548 downloads and 554 bug correction over 
the last 3 years and ask your self what you want to bet 
your money on.

DON'T REALY ON 'jsdoc'! 

I still hope to get more feedback on my offer to help 
out with a php solution. NOTE: PHP can now be used 
as standalone script interpreter (just like perl). 


> this is the type of thing I have been planning to do to generate 
> the quickref documentation, but haven't been able to yet.  
> I just found phpDocumentor yesterday, and was thinking 
> about writing another parser for it, javascript, but
> that looks like to much work for me.
> --
> Dan Willemsen

My suggestion is not about changing the code of 
phpDocumentor. Just want to make that clear.
I change the js-code to look like PHP code and then 
use the phpDocumentor to parse the doc from it 
(See below)

--
Regards Sam 

=========================================
> 
> --- Darin Kadrioski <DKa...@lm...>
> wrote:
> > http://sourceforge.net/projects/jsdoc/
> 
> Well this is something to look into for those working
> on the Docs for DynAPI.
> 
> --
> Raymond Irving
> 
>
> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On
> Behalf Of
> sp...@4m...
> Sent: Thursday, June 26, 2003 4:36 PM
> To: dyn...@li...
> Subject: [Dynapi-Dev] Documentation Stratagy for
> DynApi; is there one??
>
> Documentation Stratagy for DynApi; is there one??
> =================================
> 
> How do *you* plan to document DynApi code? 
> 
*snip*
> But I'm not aware that anthing exsists for js. So
> wath I did is: I wrote a simple converter that converts 
> js to PHP. Not 100% but good enough for
> the phpDocumentor to think it's valid PHP and let
> the converter do the HTML/PDF documenting 
> rendering work (including links aso).
> 
> The 'drawback' (if you can say so) is that I needed
> to write js code in a form that makes it easy to detect 
> classes and methods. My suggestion is following 
> code style:
> 
> /**
> * This is a sample class.
> * 
> * @example example_1.html
> *
> * @author    xxx
> * @package   core
> * @subpackage fx
> * @copyright LGNU
> */
> aClass = function() {
>   
>   /**
>   * Follwing is a short description.
>   * A longer description goes here.
>   * 
>   * @access public 
>   * @param object e Any object
>   * @return void
>   * @see onpathrun(), onpathstop()
>   */
>   this.onpathstart = function(e) {
>     status = start;
>   }
>   
>   // a.s.o.
> 
> }
> 
> I forgot to mention that the js files must go
> through a stripper. The  stripper removes all 
> comments and (if intelligent) can squeeze the
> js to a max. The striped js code is for productive
> use. While the original files stay commented!
> 
> In this way the doc and the source stay in sync.
> Separating code form doc is a very very dangerous 
> and will cause head acks for everybody! 
> 
> If you are thinking of maintaining doc separate from
> source, please, *please* over think you strategy. 
> I on my side am willing to share my
> knowledge on how to strip the js-code and give you a
> hand on the converter and phpDocumentor.

RE: [Dynapi-Dev] Documentation Stratagy for DynApi; is there one? ?

[Raymond I. <xw...@ya...>]

--- Dan Willemsen <da...@wi...> wrote:
> 
> Quoting Darin Kadrioski
> <DKa...@lm...>:
> 
> > http://sourceforge.net/projects/jsdoc/
> 
> nice... the only question i have is whether it will
> parse some of the javascript
> that we use in dynapi, some of it isn't all so
> well-formed according to it's
> definition i don't think

"...With the exception of the rules stated above how
you document your code is not a matter of concern to
the parser...."

As long and the comments follow the jsDoc rules then
the DynAPI files will work great!

I think this a good start for the source codre
documentation.

The question now is who are the persons that will be
working on the source code documentation?  Dan I guess
your in on this one?


--
Raymond.

> --
> Dan Willemsen
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are
> available now.
> Download today and enter to win an XBOX or Visual
> Studio .NET.
>
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

Re: [Dynapi-Dev] Documentation Stratagy for DynApi; is there one??

[Dan W. <da...@wi...>]

this is the type of thing I have been planning to do to generate the quickref
documentation, but haven't been able to yet.  I just found phpDocumentor
yesterday, and was thinking about writing another parser for it, javascript, but
that looks like to much work for me.
--
Dan Willemsen
http://dan.willemsen.us/


Quoting sp...@4m...:

> Documentation Stratagy for DynApi; is there one??
> =================================
> 
> How do *you* plan to document DynApi code? 
> 
> I had the problem that I needed inline documentation for my javascripts
> (like javadoc for java and phpDocumentor for PHP).
> 
> E.g.
> /**
> * Follwing is a short description.
> * A longer description goes here.
> * 
> * @access public 
> * @param int i Starting point in pixel
> * @param string s Caption
> * @return object A new dynapi object
> * @see setEnd()
> */
> setStart(i, s) = function {
>   // the code
> }
> 
> But I'm not aware that anthing exsists for js. So wath I did is: I wrote
> a simple converter that converts js to PHP. Not 100% but good enough for
> the phpDocumentor to think it's valid PHP and let the converter do the
> HTML/PDF documenting rendering work (including links aso).
> 
> The 'drawback' (if you can say so) is that I needed to write js code in
> a form that makes it easy to detect classes and methods. My suggestion
> is following code style:
> 
> /**
> * This is a sample class.
> * 
> * @example example_1.html
> *
> * @author    xxx
> * @package   core
> * @subpackage fx
> * @copyright LGNU
> */
> aClass = function() {
>   
>   /**
>   * Follwing is a short description.
>   * A longer description goes here.
>   * 
>   * @access public 
>   * @param object e Any object
>   * @return void
>   * @see onpathrun(), onpathstop()
>   */
>   this.onpathstart = function(e) {
>     status = start;
>   }
>   
>   // a.s.o.
> 
> }
> 
> I forgot to mention that the js files must go through a stripper. The
> stripper removes all comments and (if intelligent) can squeeze the
> js to a max. The striped js code is for productive use. While the
> original files stay commented!
> 
> In this way the doc and the source stay in sync. Separating code form
> doc is a very very dangerous and will cause head acks for everybody! 
> 
> If you are thinking of maintaining doc separate from source, please,
> *please* over think you strategy. I on my side am willing to share my
> knowledge on how to strip the js-code and give you a hand on the
> converter and phpDocumentor.
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
> 

RE: [Dynapi-Dev] Documentation Stratagy for DynApi; is there one? ?

[Dan W. <da...@wi...>]

Quoting Darin Kadrioski <DKa...@lm...>:

> http://sourceforge.net/projects/jsdoc/

nice... the only question i have is whether it will parse some of the javascript
that we use in dynapi, some of it isn't all so well-formed according to it's
definition i don't think

--
Dan Willemsen

Re: [Dynapi-Dev] cvs problems

[Jesse V. <je...@6t...>]

 From the looks of it, Tortoise has a built in SSH client, but I'm not 
sure how it works, since I haven't tried to check everything in yet.  I 
was trying to come up with a list of all the changes I made and do an 
update first, but I was having trouble with CVS.

If you haven't seen / tried Tortoise yet, take a look.  As a CVS newbie, 
I found it much easier than WinCVS.
http://www.tortoisecvs.org/

Jesse

Raymond Irving wrote:

>I don't know how Tortoise CVS works with SSH but I do
>know that WinCVS can work with it.
>
>If you're going to commit changes to CVS you must use
>an SSH connection.
>
>Yesterday it seems like SourceForge was experiencing
>some problems but I guess it should be ok now.
>
>--
>Raymond Irving
>
>
>--- Jesse Vitrone <je...@6t...> wrote:
>  
>
>>I keep getting this error when I try to do stuff in
>>CVS:
>>
>>
>>In D:\development\dynapi3x: cvs -q update -d -P -C
>>src/gui/groupmanager.js
>>
>>    
>>
>CVSROOT=:pserver:ano...@cv...:/cvsroot/dynapi
>  
>
>>cvs [update aborted]: Error reading from server
>>cvs.sourceforge.net: -1
>>
>>Error, CVS operation failed
>>
>>
>>
>>It works about 1 in 10 times, the rest, I get this
>>error.  Has anyone 
>>else seen this problem?
>>
>>I'm using Tortoise CVS in windows xp.
>>
>>I'm finally getting around to checking in the
>>changes I made and the 
>>code I wrote for the java.compressor stuff, and I'm
>>having a really 
>>tough time doing it, since I have to try 10 times
>>just to do a diff or 
>>update.
>>
>>Jesse
>>
>>
>>
>>
>>    
>>
>-------------------------------------------------------
>  
>
>>This SF.Net email is sponsored by: INetU
>>Attention Web Developers & Consultants: Become An
>>INetU Hosting Partner.
>>Refer Dedicated Servers. We Manage Them. You Get 10%
>>Monthly Commission!
>>INetU Dedicated Managed Hosting
>>http://www.inetu.net/partner/index.php
>>_______________________________________________
>>Dynapi-Dev mailing list
>>Dyn...@li...
>>
>>    
>>
>http://www.mail-archive.com/dyn...@li.../
>
>
>__________________________________
>Do you Yahoo!?
>SBC Yahoo! DSL - Now only $29.95 per month!
>http://sbc.yahoo.com
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: INetU
>Attention Web Developers & Consultants: Become An INetU Hosting Partner.
>Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
>INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
>_______________________________________________
>Dynapi-Dev mailing list
>Dyn...@li...
>http://www.mail-archive.com/dyn...@li.../
>  
>

Re: [Dynapi-Dev] getClip() setClip() and opera

[Raymond I. <xw...@ya...>]

Seems like a bug! I hate bugs :)

--
Raymond Irving

--- Daniel Tiru <de...@ti...> wrote:
> Hi folks!
> 
> The getClip() and setClip() dont seam to work very
> well in opera.
> 
> I am using
> Version 7.11 
> Build 2887 
> 
> and am trying my new decinc swiper but dont work as
> the getClip() returns 0,NaN,NaN,NaN...
> 
> Any idees?
> 
> /Daniel
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An
> INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10%
> Monthly Commission!
> INetU Dedicated Managed Hosting
> http://www.inetu.net/partner/index.php
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

RE: [Dynapi-Dev] Documentation Stratagy for DynApi; is there one? ?

[Raymond I. <xw...@ya...>]

--- Darin Kadrioski <DKa...@lm...>
wrote:
> http://sourceforge.net/projects/jsdoc/

Well this is something to look into for those working
on the Docs for DynAPI.

--
Raymond Irving


> 
> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On
> Behalf Of
> sp...@4m...
> Sent: Thursday, June 26, 2003 4:36 PM
> To: dyn...@li...
> Subject: [Dynapi-Dev] Documentation Stratagy for
> DynApi; is there one??
> 
> 
> Documentation Stratagy for DynApi; is there one??
> =================================
> 
> How do *you* plan to document DynApi code? 
> 
> I had the problem that I needed inline documentation
> for my javascripts
> (like javadoc for java and phpDocumentor for PHP).
> 
> E.g.
> /**
> * Follwing is a short description.
> * A longer description goes here.
> * 
> * @access public 
> * @param int i Starting point in pixel
> * @param string s Caption
> * @return object A new dynapi object
> * @see setEnd()
> */
> setStart(i, s) = function {
>   // the code
> }
> 
> But I'm not aware that anthing exsists for js. So
> wath I did is: I wrote
> a simple converter that converts js to PHP. Not 100%
> but good enough for
> the phpDocumentor to think it's valid PHP and let
> the converter do the
> HTML/PDF documenting rendering work (including links
> aso).
> 
> The 'drawback' (if you can say so) is that I needed
> to write js code in
> a form that makes it easy to detect classes and
> methods. My suggestion
> is following code style:
> 
> /**
> * This is a sample class.
> * 
> * @example example_1.html
> *
> * @author    xxx
> * @package   core
> * @subpackage fx
> * @copyright LGNU
> */
> aClass = function() {
>   
>   /**
>   * Follwing is a short description.
>   * A longer description goes here.
>   * 
>   * @access public 
>   * @param object e Any object
>   * @return void
>   * @see onpathrun(), onpathstop()
>   */
>   this.onpathstart = function(e) {
>     status = start;
>   }
>   
>   // a.s.o.
> 
> }
> 
> I forgot to mention that the js files must go
> through a stripper. The
> stripper removes all comments and (if intelligent)
> can squeeze the
> js to a max. The striped js code is for productive
> use. While the
> original files stay commented!
> 
> In this way the doc and the source stay in sync.
> Separating code form
> doc is a very very dangerous and will cause head
> acks for everybody! 
> 
> If you are thinking of maintaining doc separate from
> source, please,
> *please* over think you strategy. I on my side am
> willing to share my
> knowledge on how to strip the js-code and give you a
> hand on the
> converter and phpDocumentor.
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An
> INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10%
> Monthly Commission!
> INetU Dedicated Managed Hosting
> http://www.inetu.net/partner/index.php
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An
> INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10%
> Monthly Commission!
> INetU Dedicated Managed Hosting
> http://www.inetu.net/partner/index.php
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

Re: [Dynapi-Dev] cvs problems

[Raymond I. <xw...@ya...>]

I don't know how Tortoise CVS works with SSH but I do
know that WinCVS can work with it.

If you're going to commit changes to CVS you must use
an SSH connection.

Yesterday it seems like SourceForge was experiencing
some problems but I guess it should be ok now.

--
Raymond Irving


--- Jesse Vitrone <je...@6t...> wrote:
> I keep getting this error when I try to do stuff in
> CVS:
> 
> 
> In D:\development\dynapi3x: cvs -q update -d -P -C
> src/gui/groupmanager.js
>
CVSROOT=:pserver:ano...@cv...:/cvsroot/dynapi
> 
> cvs [update aborted]: Error reading from server
> cvs.sourceforge.net: -1
> 
> Error, CVS operation failed
> 
> 
> 
> It works about 1 in 10 times, the rest, I get this
> error.  Has anyone 
> else seen this problem?
> 
> I'm using Tortoise CVS in windows xp.
> 
> I'm finally getting around to checking in the
> changes I made and the 
> code I wrote for the java.compressor stuff, and I'm
> having a really 
> tough time doing it, since I have to try 10 times
> just to do a diff or 
> update.
> 
> Jesse
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An
> INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10%
> Monthly Commission!
> INetU Dedicated Managed Hosting
> http://www.inetu.net/partner/index.php
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Dynapi-Dev] cvs problems

[Jesse V. <je...@6t...>]

I keep getting this error when I try to do stuff in CVS:


In D:\development\dynapi3x: cvs -q update -d -P -C src/gui/groupmanager.js
CVSROOT=:pserver:ano...@cv...:/cvsroot/dynapi

cvs [update aborted]: Error reading from server cvs.sourceforge.net: -1

Error, CVS operation failed



It works about 1 in 10 times, the rest, I get this error.  Has anyone 
else seen this problem?

I'm using Tortoise CVS in windows xp.

I'm finally getting around to checking in the changes I made and the 
code I wrote for the java.compressor stuff, and I'm having a really 
tough time doing it, since I have to try 10 times just to do a diff or 
update.

Jesse

[Dynapi-Dev] indec:swiper-like include...

[Daniel T. <de...@ti...>]

Hi!

I have made the incdec slider now... what it does is that instead of the swiper, it
- never hides the layers
- suports a min value so if using the decleft it will never be smaller than 10px on the left side... the incleft will then return it to the original clip. 
It doesnt shrink the layer but use clipping.

It only support inc/dec left/right/up/down now, but if someone feels like to have the left-up and so on i can make that to.

The functions/methods is exactly as the swiper... but needs a min value aswell.

Can someone test/check this if there is something wrong with it?

Regards
Daniel

[Dynapi-Dev] getClip() setClip() and opera

[Daniel T. <de...@ti...>]

Hi folks!

The getClip() and setClip() dont seam to work very well in opera.

I am using
Version 7.11 
Build 2887 

and am trying my new decinc swiper but dont work as the getClip() returns 0,NaN,NaN,NaN...

Any idees?

/Daniel

Re: [Dynapi-Dev] Documentation Stratagy for DynApi; is there one??

[Daniel T. <de...@ti...>]

I like the following layout..

Name Object etc

Syntax
object.method and so on...
 
Collections and etc.

Methods

Events

Remarks
Howto... and issues

Example
code...

Just my tip of the coin :)

/Daniel

> Documentation Stratagy for DynApi; is there one??
> =================================
> 
> How do *you* plan to document DynApi code? 
> 
> I had the problem that I needed inline documentation for my javascripts
> (like javadoc for java and phpDocumentor for PHP).
> 
> E.g.
> /**
> * Follwing is a short description.
> * A longer description goes here.
> * 
> * @access public 
> * @param int i Starting point in pixel
> * @param string s Caption
> * @return object A new dynapi object
> * @see setEnd()
> */
> setStart(i, s) = function {
>   // the code
> }
> 
> But I'm not aware that anthing exsists for js. So wath I did is: I wrote
> a simple converter that converts js to PHP. Not 100% but good enough for
> the phpDocumentor to think it's valid PHP and let the converter do the
> HTML/PDF documenting rendering work (including links aso).
> 
> The 'drawback' (if you can say so) is that I needed to write js code in
> a form that makes it easy to detect classes and methods. My suggestion
> is following code style:
> 
> /**
> * This is a sample class.
> * 
> * @example example_1.html
> *
> * @author    xxx
> * @package   core
> * @subpackage fx
> * @copyright LGNU
> */
> aClass = function() {
>   
>   /**
>   * Follwing is a short description.
>   * A longer description goes here.
>   * 
>   * @access public 
>   * @param object e Any object
>   * @return void
>   * @see onpathrun(), onpathstop()
>   */
>   this.onpathstart = function(e) {
>     status = start;
>   }
>   
>   // a.s.o.
> 
> }
> 
> I forgot to mention that the js files must go through a stripper. The
> stripper removes all comments and (if intelligent) can squeeze the
> js to a max. The striped js code is for productive use. While the
> original files stay commented!
> 
> In this way the doc and the source stay in sync. Separating code form
> doc is a very very dangerous and will cause head acks for everybody! 
> 
> If you are thinking of maintaining doc separate from source, please,
> *please* over think you strategy. I on my side am willing to share my
> knowledge on how to strip the js-code and give you a hand on the
> converter and phpDocumentor.
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../

RE: [Dynapi-Dev] Documentation Stratagy for DynApi; is there one? ?

[Darin K. <DKa...@lm...>]

http://sourceforge.net/projects/jsdoc/

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of
sp...@4m...
Sent: Thursday, June 26, 2003 4:36 PM
To: dyn...@li...
Subject: [Dynapi-Dev] Documentation Stratagy for DynApi; is there one??


Documentation Stratagy for DynApi; is there one??
=================================

How do *you* plan to document DynApi code? 

I had the problem that I needed inline documentation for my javascripts
(like javadoc for java and phpDocumentor for PHP).

E.g.
/**
* Follwing is a short description.
* A longer description goes here.
* 
* @access public 
* @param int i Starting point in pixel
* @param string s Caption
* @return object A new dynapi object
* @see setEnd()
*/
setStart(i, s) = function {
  // the code
}

But I'm not aware that anthing exsists for js. So wath I did is: I wrote
a simple converter that converts js to PHP. Not 100% but good enough for
the phpDocumentor to think it's valid PHP and let the converter do the
HTML/PDF documenting rendering work (including links aso).

The 'drawback' (if you can say so) is that I needed to write js code in
a form that makes it easy to detect classes and methods. My suggestion
is following code style:

/**
* This is a sample class.
* 
* @example example_1.html
*
* @author    xxx
* @package   core
* @subpackage fx
* @copyright LGNU
*/
aClass = function() {
  
  /**
  * Follwing is a short description.
  * A longer description goes here.
  * 
  * @access public 
  * @param object e Any object
  * @return void
  * @see onpathrun(), onpathstop()
  */
  this.onpathstart = function(e) {
    status = start;
  }
  
  // a.s.o.

}

I forgot to mention that the js files must go through a stripper. The
stripper removes all comments and (if intelligent) can squeeze the
js to a max. The striped js code is for productive use. While the
original files stay commented!

In this way the doc and the source stay in sync. Separating code form
doc is a very very dangerous and will cause head acks for everybody! 

If you are thinking of maintaining doc separate from source, please,
*please* over think you strategy. I on my side am willing to share my
knowledge on how to strip the js-code and give you a hand on the
converter and phpDocumentor.



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://www.mail-archive.com/dyn...@li.../

[Dynapi-Dev] Documentation Stratagy for DynApi; is there one??

[<sp...@4m...>]

Documentation Stratagy for DynApi; is there one??
=================================

How do *you* plan to document DynApi code? 

I had the problem that I needed inline documentation for my javascripts
(like javadoc for java and phpDocumentor for PHP).

E.g.
/**
* Follwing is a short description.
* A longer description goes here.
* 
* @access public 
* @param int i Starting point in pixel
* @param string s Caption
* @return object A new dynapi object
* @see setEnd()
*/
setStart(i, s) = function {
  // the code
}

But I'm not aware that anthing exsists for js. So wath I did is: I wrote
a simple converter that converts js to PHP. Not 100% but good enough for
the phpDocumentor to think it's valid PHP and let the converter do the
HTML/PDF documenting rendering work (including links aso).

The 'drawback' (if you can say so) is that I needed to write js code in
a form that makes it easy to detect classes and methods. My suggestion
is following code style:

/**
* This is a sample class.
* 
* @example example_1.html
*
* @author    xxx
* @package   core
* @subpackage fx
* @copyright LGNU
*/
aClass = function() {
  
  /**
  * Follwing is a short description.
  * A longer description goes here.
  * 
  * @access public 
  * @param object e Any object
  * @return void
  * @see onpathrun(), onpathstop()
  */
  this.onpathstart = function(e) {
    status = start;
  }
  
  // a.s.o.

}

I forgot to mention that the js files must go through a stripper. The
stripper removes all comments and (if intelligent) can squeeze the
js to a max. The striped js code is for productive use. While the
original files stay commented!

In this way the doc and the source stay in sync. Separating code form
doc is a very very dangerous and will cause head acks for everybody! 

If you are thinking of maintaining doc separate from source, please,
*please* over think you strategy. I on my side am willing to share my
knowledge on how to strip the js-code and give you a hand on the
converter and phpDocumentor.

[Dynapi-Dev] More Fixes & Updates

[Raymond I. <xw...@ya...>]

Hi All,

[*] Auto hide & underline calendar Year/Month selector
[-] Fix HTMLMenu sound events

See the dynapi.gui.htmlcalendar.html and
dynapi.gui.htmlmenu.html examples

Updates are inside CVS


Any comments?


--
Raymond Irving


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

Re: [Dynapi-Dev] reversed swiper

[Daniel T. <de...@ti...>]

Remark:

Probably i should not be playing with the setWidth in the file either? Must be better to use clip() here as then you can have the values of how big the layer should be when increasing it again after decresing it?

/Daniel Tiru

> Hi all!
> 
> I have made a reversed swiper... however i am not really stable at programming in js (yet) and would like some help.
> 
> I have copied the swiper file but somehow i cant include it in the page... so instead i used the swiper and added some stuff.
> 
> So if anyone got the time please see line 29,84-95 for the changes i have made... its not very nice codechanges but i think you see what i want to do and as you lot are the best it should be of no problem just to fix my lines of code? Then i will do the rest... Just need something to get me started... :)
> 
> So my question here is:
> How do i make the steps implemented in my code?
> How do i rename it and include it in my pages? Should probably be renamed to something else like invswiper.js or maybee get some more arguments to swiper.js so it could be reversed in the same file and not hidden/cliped from start? However i would like to set a maximum and a minimum value... like i have done here the decleft will not be decresed under 10 and the incright will not go over 100 pixels...
> 
> Best regards
> Daniel
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
> ----------------------------------------------------
>      Name: swiper.zip
>      Type: application/x-zip-compressed
>  Encoding: base64
>    Length: 0.91 KB

[Dynapi-Dev] reversed swiper

[Dev <de...@ti...>]

Hi all!

I have made a reversed swiper... however i am not really stable at programming in js (yet) and would like some help.

I have copied the swiper file but somehow i cant include it in the page... so instead i used the swiper and added some stuff.

So if anyone got the time please see line 29,84-95 for the changes i have made... its not very nice codechanges but i think you see what i want to do and as you lot are the best it should be of no problem just to fix my lines of code? Then i will do the rest... Just need something to get me started... :)

So my question here is:
How do i make the steps implemented in my code?
How do i rename it and include it in my pages? Should probably be renamed to something else like invswiper.js or maybee get some more arguments to swiper.js so it could be reversed in the same file and not hidden/cliped from start? However i would like to set a maximum and a minimum value... like i have done here the decleft will not be decresed under 10 and the incright will not go over 100 pixels...

Best regards
Daniel

[Dynapi-Dev] [ dynapi-Patches-761349 ] Fixes/Updates for GUI, UTIL, EXT, API Libraries

[SourceForge.net <no...@so...>]

Patches item #761349, was opened at 2003-06-26 18:18
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305757&aid=761349&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Raymond Irving (xwisdom)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fixes/Updates for GUI, UTIL, EXT, API Libraries

Initial Comment:
[*] Updated Documentation & Examples (See 
docs/index.html)
[*] Update quickrefs (See docs/docs/quickref.html)
[+] Added new examples (See 
examples/dynapi.gui.*.html)
[+] Add Sound Events to HCs
[+] Add cloneField() and addField() to TemplateManager
[+] Add Data-aware features to HCs
[+] Add HTMLClock, HTMLMenu, HTMLButton
[+] Add HTMLTextBox,HTMLTextArea,HTMLRadioButton
[+] Add HTMLCheckBox, HTMLFile,HTMLListBox
[+] Add HTMLDropDownMenu, HTMLDatePicker
[+] Add pkgFile (package file) arugment to 
dynapi.library.setPath(path,pkgFile). pkgFile most 
contain the full path and file name of the package file
[+] Add startFlash(fCol,tCol) and stopFlash() to 
HTMLHyperLink
[+] Add setAlarm feature to HTMLClock
[-] Fix GroupManager (GM) width bug
[*] Allow GroupManager to autoset boundary after a 
layer resizes
[+] Add sprintf() function to dynapi.functions.String
[+] Add getDayOfYear() to dynapi.functions.Date
[+] Add new ioelemsvr.php server-side library

Check out CVS for the latest updates

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305757&aid=761349&group_id=5757

[Dynapi-Dev] [ dynapi-Bugs-759703 ] Library Error: could not find [TemplateManager]

[SourceForge.net <no...@so...>]

Bugs item #759703, was opened at 2003-06-24 03:51
Message generated for change (Comment added) made by b0nj0m0n
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=759703&group_id=5757

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: ben smith (b0nj0m0n)
Assigned to: Nobody/Anonymous (nobody)
Summary: Library Error: could not find [TemplateManager]

Initial Comment:
The library claims that it can't find TemplateManager or 
SnapX. I checked in /ext/packages.js, and the filenames 
listed there correspond with the correct physical 
filenames.  Using DynAPI 3.0.0 with Internet Explorer 6 
and Mozilla 1.4 on a RedHat/Apache server.  

http://benchmark.s-m-i-t-h.com/testNavBar.htm

I'm brand new to the water, but it looked cold, so I tried 
the diving board.  Thanks much - it looks great, wish I 
could get it to work.



----------------------------------------------------------------------

>Comment By: ben smith (b0nj0m0n)
Date: 2003-06-26 00:06

Message:
Logged In: YES 
user_id=808185

XWisdom:

Thanks for new syntax reminder.

  I'm having trouble with CVSing DynAPI snapshots, it doesn't 
like my password when I enter it.  I don't want to waste this 
account but I'd much rather participate in new code than use 
old stable code - especially because I love the new features -
 and I'm on a time budget.  Has anyone had problems logging 
in?

Thanks!

----------------------------------------------------------------------

Comment By: Raymond Irving (xwisdom)
Date: 2003-06-24 08:12

Message:
Logged In: YES 
user_id=696242

Hi Ben,

Welcome to the new world of DynAPI 3.0

Thanks for the information. This issue has been resolved and 
will be in cvs soon.

On looking at your test page I found out that your still using 
the moveTo(x,y) function. This function was replaced with 
the setLocation(x,y) function

Enjoy!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=759703&group_id=5757

Re: [Dynapi-Dev] Learning IOElement and SODA, to convert to Perl

[Raymond I. <xw...@ya...>]

Well, I'm the one who created the SODA stuff so I
guess I'll have to give it a go (the indept
explaination that is). In the meantime you could take
a look at the ioelmsrv.php example

--
Raymond Irving

--- Leif W <war...@us...> wrote:
> Hi,
> 
> I'm still trying to figure out exactly what
> IOElement is, what SODA is, how to
> use them, how they differ.  Only then can I know if
> my Perl version is
> correct.  The documentation and examples are a bit
> difficult for me to absorb
> for some reason.  They both have client-side and
> server-side components,
> correct?  Is there a specific protocol that they
> use?  Could someone give a
> very simple example of a client-side script,
> explaining what it sends to the
> server, what the server side should do with that,
> and what the client expects
> in return?  Maybe if I see it explained a different
> way it'll sink in.  The
> conversion isn't hard, it's learning all this new
> stuff that's my hangup.
> 
> Thanks in advance for any help,
> 
> Leif
> 
> P.S. Once upon a time I hacked some old TCL script I
> had found at a job and
> subsequently converted it to Perl, so perhaps I can
> do the reverse and make a
> TCL version from my Perl script.  I've toyed with
> some Java, so I could hack
> code if someone else started something, but I'm
> still a little shakey to give
> it a go from scratch.  I can go through the PHP
> version as well and make sure
> all scripts & languages are complete and consistent.
> 
> 
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An
> INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10%
> Monthly Commission!
> INetU Dedicated Managed Hosting
> http://www.inetu.net/partner/index.php
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Dynapi-Dev] Learning IOElement and SODA, to convert to Perl

[Leif W <war...@us...>]

Hi,

I'm still trying to figure out exactly what IOElement is, what SODA is, h=
ow to
use them, how they differ.  Only then can I know if my Perl version is
correct.  The documentation and examples are a bit difficult for me to ab=
sorb
for some reason.  They both have client-side and server-side components,
correct?  Is there a specific protocol that they use?  Could someone give=
 a
very simple example of a client-side script, explaining what it sends to =
the
server, what the server side should do with that, and what the client exp=
ects
in return?  Maybe if I see it explained a different way it'll sink in.  T=
he
conversion isn't hard, it's learning all this new stuff that's my hangup.=


Thanks in advance for any help,

Leif

P.S. Once upon a time I hacked some old TCL script I had found at a job a=
nd
subsequently converted it to Perl, so perhaps I can do the reverse and ma=
ke a
TCL version from my Perl script.  I've toyed with some Java, so I could h=
ack
code if someone else started something, but I'm still a little shakey to =
give
it a go from scratch.  I can go through the PHP version as well and make =
sure
all scripts & languages are complete and consistent.

[Dynapi-Dev] A quick TemplateManager Patch

[Raymond I. <xw...@ya...>]

Hi All,

The attached is a quick patch for the TM which adds
cloneField() and addField() functions.

--
Raymond Irving

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com