Menu
▾
▴
dynapi-dev
|
From: Barre B. <ba...@ho...> - 2000-11-16 13:40:58
|
Yeah.. I see what you mean :) Sure, as I say I have a mac at work and I am in the process of converting to dynapi2. Although I am not too fond of the mac and especially all the f***** problems/bugs that browsers on that platform have, I am quite cabable of debugging stuff on it; as it is part of my job :) So I'm totally up for hacking the mac to pieces. Literally. Heh I will however try stuff on a PC first and foremost. Anyway, how do you want me to go about it, sending reports or files or whatever? /Bart > > Answer: > Yes it is an integral part, but as you already mentioned > there is modularity, and also the fact that you might want > to use your own browser detection or another browser detection > in the future (just an idea :) > > > It's great that you have a Mac, and hopefully you'r capable > of debugging javascript because I tried to do it a couple of > times with people who own a Mac, they would tell me the errors > and I'd try to fix them one by one... and that doesn't work, so > we really need someone who can hack it on a Mac. > > > > Pascal Bestebroer > pb...@oi... > http://www.oibv.com > > > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Barre Bizon > Verzonden: maandag 13 november 2000 13:47 > Aan: dyn...@li... > Onderwerp: [Dynapi-Dev] Default > > > > Question: > Shouldn't browser.js be included by default when you create > dynlayers? > I mean it is an integral part of the DynAPI and cannot be > left out... > And as far as keeping modularity.. ok.. but it really seems > reduntant to always include browser.js as practically > nothing will work without it... > > Maybe I'm missing something, though, as I'm just starting > to check DynAPI2 out. :) > > Oh and by the way,I have access to a mac (I have it as a > testcomputer at my work desk) so I could help with the > development for mac. > I have worked extensivly with a modified version of the > first dynapi before, including the creation of a text > dropdown menu with extensive platform support. > I even made a simplified scroll that works with mac. > > checkout > http://www.saabusa.com/home/US/en/95_intro.xml > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > |
|
From: Barre B. <ba...@ho...> - 2000-11-16 13:43:47
|
Hmm... this is very interesting.. yes you are right offcourse.. And I have noticed this problem in other libraries that I have built. What is being done about modularity.. I would be very intrested to take a deeper look at it. /Bart > The DynAPI as it stands is only partially modular. > This is aparent by the fact that when one bug is fixed, it causes a problem > in either the widgets, or somewhere else in the core. > > Take heart though. There's hope for this problem in the future! > > ----- Original Message ----- > From: "Pascal Bestebroer" <pb...@oi...> > To: <dyn...@li...> > Sent: Tuesday, November 14, 2000 6:20 AM > Subject: RE: [Dynapi-Dev] Default > > > > > > Answer: > > Yes it is an integral part, but as you already mentioned > > there is modularity, and also the fact that you might want > > to use your own browser detection or another browser detection > > in the future (just an idea :) > > > > > > It's great that you have a Mac, and hopefully you'r capable > > of debugging javascript because I tried to do it a couple of > > times with people who own a Mac, they would tell me the errors > > and I'd try to fix them one by one... and that doesn't work, so > > we really need someone who can hack it on a Mac. > > > > > > > > Pascal Bestebroer > > pb...@oi... > > http://www.oibv.com > > > > > > -----Oorspronkelijk bericht----- > > Van: dyn...@li... > > [mailto:dyn...@li...]Namens Barre Bizon > > Verzonden: maandag 13 november 2000 13:47 > > Aan: dyn...@li... > > Onderwerp: [Dynapi-Dev] Default > > > > > > > > Question: > > Shouldn't browser.js be included by default when you create > > dynlayers? > > I mean it is an integral part of the DynAPI and cannot be > > left out... > > And as far as keeping modularity.. ok.. but it really seems > > reduntant to always include browser.js as practically > > nothing will work without it... > > > > Maybe I'm missing something, though, as I'm just starting > > to check DynAPI2 out. :) > > > > Oh and by the way,I have access to a mac (I have it as a > > testcomputer at my work desk) so I could help with the > > development for mac. > > I have worked extensivly with a modified version of the > > first dynapi before, including the creation of a text > > dropdown menu with extensive platform support. > > I even made a simplified scroll that works with mac. > > > > checkout > > http://www.saabusa.com/home/US/en/95_intro.xml > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Pascal B. <pb...@oi...> - 2000-11-16 15:55:01
|
I think the DynAPi is already very modular, you don't need to use events or dragging objects. The only problem we're having is that you need to include dyndocument and dynlayer, because dynlayers can only be added to dyndocuments.. but the rest isn't that bad is it? Brandon, care to share your ideas ? Pascal Bestebroer pb...@oi... http://www.oibv.com -----Oorspronkelijk bericht----- Van: dyn...@li... [mailto:dyn...@li...]Namens Barre Bizon Verzonden: donderdag 16 november 2000 14:43 Aan: dyn...@li... Onderwerp: Re: Re: [Dynapi-Dev] Default Hmm... this is very interesting.. yes you are right offcourse.. And I have noticed this problem in other libraries that I have built. What is being done about modularity.. I would be very intrested to take a deeper look at it. /Bart > The DynAPI as it stands is only partially modular. > This is aparent by the fact that when one bug is fixed, it causes a problem > in either the widgets, or somewhere else in the core. > > Take heart though. There's hope for this problem in the future! > > ----- Original Message ----- > From: "Pascal Bestebroer" <pb...@oi...> > To: <dyn...@li...> > Sent: Tuesday, November 14, 2000 6:20 AM > Subject: RE: [Dynapi-Dev] Default > > > > > > Answer: > > Yes it is an integral part, but as you already mentioned > > there is modularity, and also the fact that you might want > > to use your own browser detection or another browser detection > > in the future (just an idea :) > > > > > > It's great that you have a Mac, and hopefully you'r capable > > of debugging javascript because I tried to do it a couple of > > times with people who own a Mac, they would tell me the errors > > and I'd try to fix them one by one... and that doesn't work, so > > we really need someone who can hack it on a Mac. > > > > > > > > Pascal Bestebroer > > pb...@oi... > > http://www.oibv.com > > > > > > -----Oorspronkelijk bericht----- > > Van: dyn...@li... > > [mailto:dyn...@li...]Namens Barre Bizon > > Verzonden: maandag 13 november 2000 13:47 > > Aan: dyn...@li... > > Onderwerp: [Dynapi-Dev] Default > > > > > > > > Question: > > Shouldn't browser.js be included by default when you create > > dynlayers? > > I mean it is an integral part of the DynAPI and cannot be > > left out... > > And as far as keeping modularity.. ok.. but it really seems > > reduntant to always include browser.js as practically > > nothing will work without it... > > > > Maybe I'm missing something, though, as I'm just starting > > to check DynAPI2 out. :) > > > > Oh and by the way,I have access to a mac (I have it as a > > testcomputer at my work desk) so I could help with the > > development for mac. > > I have worked extensivly with a modified version of the > > first dynapi before, including the creation of a text > > dropdown menu with extensive platform support. > > I even made a simplified scroll that works with mac. > > > > checkout > > http://www.saabusa.com/home/US/en/95_intro.xml > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev _______________________________________________ Dynapi-Dev mailing list Dyn...@li... http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Robert R. <rra...@ya...> - 2000-11-16 19:59:33
|
You could have a DynAPI.require method that will add required files. Then when the first file is included, it will include all of the required files. I've done something similar to this before and it worked quite easily. Also, this allows you to set the required files in the widgets. That way if someone wanted to use the button widget, the only file that have to include is the button.js file and all of the others would automatically be included. \\Robert -- rra...@ya... > I think the DynAPi is already very modular, you don't need to use events or > dragging objects. > The only problem we're having is that you need to include dyndocument and > dynlayer, because dynlayers can only be added to dyndocuments.. but the rest > isn't that bad is it? > > Brandon, care to share your ideas ? > > > > Pascal Bestebroer > pb...@oi... > http://www.oibv.com > > |
|
From: Brandon M. <tr...@us...> - 2000-11-16 21:39:28
|
Although that's a novel idea, it would require a "standard" in writing widgets, which we all know, has created a long standing problem in that: - one side says development should be free-form. No rules to develop the app. - the other says that there should be standards so that widgets work together with little to no changes in code. Well... I say just leave things the way they are. don't bother creating a require, as it would require that all scripts that are included within the 'include' method notify the API that it has completed loading. Only IE5+ can truely detect successful completion of an external script. I say keep the list of "include" statements at the top for every required file. It allows a user viewing an application for the first time to know exactly everything that is needed to run the app. This shouldn't be C++ include within include within include.... simple one-pass include should suffice. ----- Original Message ----- From: "Robert Rainwater" <rra...@ya...> To: "Pascal Bestebroer" <dyn...@li...> Sent: Thursday, November 16, 2000 3:01 PM Subject: Re[3]: [Dynapi-Dev] Default > > You could have a DynAPI.require method that will add required files. > Then when the first file is included, it will include all of the > required files. I've done something similar to this before and it > worked quite easily. Also, this allows you to set the required files > in the widgets. That way if someone wanted to use the button widget, > the only file that have to include is the button.js file and all of > the others would automatically be included. > > > \\Robert > -- > rra...@ya... > > > I think the DynAPi is already very modular, you don't need to use events or > > dragging objects. > > The only problem we're having is that you need to include dyndocument and > > dynlayer, because dynlayers can only be added to dyndocuments.. but the rest > > isn't that bad is it? > > > > Brandon, care to share your ideas ? > > > > > > > > Pascal Bestebroer > > pb...@oi... > > http://www.oibv.com > > > > > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Darin K. <dka...@ef...> - 2000-11-16 20:47:36
|
Of course you'd need to keep a running list of all the files that had already been loaded are not loaded again. Otherwise, you could be making a lot of useless trips to the server :) -----Original Message----- From: Robert Rainwater [mailto:rra...@ya...] Sent: Thursday, November 16, 2000 12:01 PM To: Pascal Bestebroer Subject: Re[3]: [Dynapi-Dev] Default You could have a DynAPI.require method that will add required files. Then when the first file is included, it will include all of the required files. I've done something similar to this before and it worked quite easily. Also, this allows you to set the required files in the widgets. That way if someone wanted to use the button widget, the only file that have to include is the button.js file and all of the others would automatically be included. \\Robert -- rra...@ya... > I think the DynAPi is already very modular, you don't need to use events or > dragging objects. > The only problem we're having is that you need to include dyndocument and > dynlayer, because dynlayers can only be added to dyndocuments.. but the rest > isn't that bad is it? > > Brandon, care to share your ideas ? > > > > Pascal Bestebroer > pb...@oi... > http://www.oibv.com > > _______________________________________________ Dynapi-Dev mailing list Dyn...@li... http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Robert R. <rra...@ya...> - 2000-11-16 23:01:44
|
Yep, there's already a patch at sourceforge that does this with the include method, but unless we would actually use requires in the widgets, we don't really need it. \\Robert -- rra...@ya... |
|
From: Simon D. M. <di...@bi...> - 2000-11-17 16:32:33
|
May I suggest you drop the .pad property from DynLayer NS4's LAYER element has no native .padding property so setting a property does nothing thus a DynLayer's padding is not cross-browser If padding is needed, we can use the Label widget. The code using .pad could be removed from api/dynlayer.js along with the setPadding and getPadding methods in ext/layer.js Best, SD |
|
From: Stephan R. <SR...@la...> - 2000-11-17 09:00:20
|
Alas we don't have a preprocessor, but not use a construct like this (which u can find in almost every C or C++ source): #ifndef __DIRECTRY_H #include "directry.h" #endif public vars should be ok in JS. Stephan > > > > Of course you'd need to keep a running list of all the files that had > already been loaded are not loaded again. Otherwise, you could > be making a > lot of useless trips to the server :) > > > > You could have a DynAPI.require method that will add required files. > Then when the first file is included, it will include all of the > required files. I've done something similar to this before and it > worked quite easily. Also, this allows you to set the required files > in the widgets. That way if someone wanted to use the button widget, > the only file that have to include is the button.js file and all of > the others would automatically be included. > > > > I think the DynAPi is already very modular, you don't need to use events > or > > dragging objects. > > The only problem we're having is that you need to include > dyndocument and > > dynlayer, because dynlayers can only be added to dyndocuments.. but the > rest > > isn't that bad is it? > > > > Brandon, care to share your ideas ? > > |
|
From: Pascal B. <pa...@dy...> - 2000-11-16 15:44:48
|
I think the easiest way would be that you simply mail your patches to this mailing list, or use the patch area at sourceforge.. We can then see if the patch isn't breaking any windows/linux code and then use it in the DynAPI. You could use the test code I mailed to this list a few days ago and see how far things run on the Mac.. still some "deeper" code isn't included in the test so they would need other testing, but using the different widgets usually seem to be a good way of testing things aswell. Pascal Bestebroer pb...@oi... http://www.oibv.com -----Oorspronkelijk bericht----- Van: dyn...@li... [mailto:dyn...@li...]Namens Barre Bizon Verzonden: donderdag 16 november 2000 14:40 Aan: dyn...@li... Onderwerp: Re: RE: [Dynapi-Dev] Default Yeah.. I see what you mean :) Sure, as I say I have a mac at work and I am in the process of converting to dynapi2. Although I am not too fond of the mac and especially all the f***** problems/bugs that browsers on that platform have, I am quite cabable of debugging stuff on it; as it is part of my job :) So I'm totally up for hacking the mac to pieces. Literally. Heh I will however try stuff on a PC first and foremost. Anyway, how do you want me to go about it, sending reports or files or whatever? /Bart > > Answer: > Yes it is an integral part, but as you already mentioned > there is modularity, and also the fact that you might want > to use your own browser detection or another browser detection > in the future (just an idea :) > > > It's great that you have a Mac, and hopefully you'r capable > of debugging javascript because I tried to do it a couple of > times with people who own a Mac, they would tell me the errors > and I'd try to fix them one by one... and that doesn't work, so > we really need someone who can hack it on a Mac. > > > > Pascal Bestebroer > pb...@oi... > http://www.oibv.com > > > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Barre Bizon > Verzonden: maandag 13 november 2000 13:47 > Aan: dyn...@li... > Onderwerp: [Dynapi-Dev] Default > > > > Question: > Shouldn't browser.js be included by default when you create > dynlayers? > I mean it is an integral part of the DynAPI and cannot be > left out... > And as far as keeping modularity.. ok.. but it really seems > reduntant to always include browser.js as practically > nothing will work without it... > > Maybe I'm missing something, though, as I'm just starting > to check DynAPI2 out. :) > > Oh and by the way,I have access to a mac (I have it as a > testcomputer at my work desk) so I could help with the > development for mac. > I have worked extensivly with a modified version of the > first dynapi before, including the creation of a text > dropdown menu with extensive platform support. > I even made a simplified scroll that works with mac. > > checkout > http://www.saabusa.com/home/US/en/95_intro.xml > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > _______________________________________________ Dynapi-Dev mailing list Dyn...@li... http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X