RE: [Dynapi-Dev] VDE-0.1rc3 release

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

Hi again!

What i was thinking about is that we maybee make a separate "function"
for each widget that is implemented to the VDE returning the things
needed in a nice format.

Like 
getWidgetInfo(mywidget) {
	// returns two arrays or something with all the arguments 
	// needed for the constructor and one with the methods for the
	// widget. Maybee even some general info on what the widget is?
}

Is this possible to do and how to do it, i dont know the answer but
myabee this solution can be a quite quick one?

I agree with the adding of this project to the cvs.

Regards
Daniel

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...] On Behalf Of Raymond
Irving
Sent: den 23 oktober 2003 22:12
To: dyn...@li...
Subject: Re: [Dynapi-Dev] VDE-0.1rc3 release



See below:

--- Michael Bystrom <mi...@mi...>
wrote:
> 
> I also wrote a VDE wrapper that lets you import the
> saved vde xml file
> directly into the dynapi, and it will recreate the
> project for you.

Not sure how this works but will look into it.
 
> I also gave Spock a little face lift so that it
> doesn't feel left out.

Ok, but now I can hardly see the button outlines.

> If anybody got Ideas for the add event or add widget
> please let me know.

Add widget should be the last thing that we do. It's
very complex and will require us to design a some kind
of header file as Daniel had suggested.

I think add events to widgets should be much easier to
do. Here how I think it can be done:

1) Double click on a layer to open up a code window.
This window will contain a drop down menu of the
various events.

2) The user then selects the event and then enter som
code in a text box below the drop down menu and then
click ok. This should then save the text into some
events collection object.
 
> And please help debug on windows

Will do.

Have you ever tried creating a very large project with
the vde? You should try it and then try saving and
loading the project to how it performs performs.

SODA takes a longer time to convert a js object into
string and back than it would a js array. Where
possible it's best to use arrays. For the DataSource
class I had to use to following format inorder to get
better performance when working with lots of data.

record={
	dataRowIndex:0,
	dataRowCount:4,
	fieldnames:['id','fname'],
	fieldvalues:[
		[1,'mary'],
		[1,'jane'],
		[1,'john'],
		[1,'paul'],
	]
}


--
Raymond Irving
 
> http://www.michaelbystrom.com/download.php
> (at the bottom of the page VDE-0.1rc3)
> 
> Michael
> 
> 
> 
>
-------------------------------------------------------
> This SF.net email is sponsored by: The SF.net
> Donation Program.
> Do you like what SourceForge.net is doing for the
> Open
> Source Community?  Make a contribution, and help us
> add new
> features and functionality. Click here: http://sourceforge.net/donate/
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com


-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program. Do you
like what SourceForge.net is doing for the Open Source Community?  Make
a contribution, and help us add new features and functionality. Click
here: http://sourceforge.net/donate/
_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://www.mail-archive.com/dyn...@li.../