RE: [vtcl] I would like to maintain Visual Tcl 1.2
Don't know if there is a future planned re-write or not but do you have patch files that might be able to be used on the existing 1.3 code? There may be some signiciant changes between 1.2 and 1.3 though so that is my concern. Or does the group as a whole think it would be better to start development again based on 1.2? I would hate for all the 1.3 work to go to waste. You might check on the cvs tree at sourceforge with the current version at http://sourceforge.net/cvs/?group_id=285 > Sent: Thursday, March 23, 2000 1:39 AM > Subject: [vtcl] I would like to maintain Visual Tcl 1.2 > > I have started working on my own on Visual Tcl 1.2 and I saw there is a lot > of interest in it. > > I would be very interested to continue the development. > > Here is what I already added: > > Christian Gavin [EMAIL PROTECTED] > > I have posted a copy of my Visual Tcl at > > http://www.dnai.com/~cgavin/vtcl/download > > I would welcome comments, remarks, etc.! > > For now it requires Itcl but I am going to rewrite the few lines of > code in the image manager that use Itcl to use standard Tcl/Tk instead. There was talk of possibly using iTcl for the new stuff..so maybe this is a starting point, unless the development team is sure they don't want to make iTcl as part of it. Eric Bresie [EMAIL PROTECTED] --- To unsubscribe from the Visual Tcl mailing list, please send a message to [EMAIL PROTECTED] with "unsubscribe vtcl [EMAIL PROTECTED]" in the message body (where [EMAIL PROTECTED] is your e-mail address).
RE: [vtcl] anything new since 1.2.0?
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of J.R.Suckling > Sent: Tuesday, March 21, 2000 9:53 AM > To: [EMAIL PROTECTED] > Subject: Re: [vtcl] anything new since 1.2.0? > > > Rick Macdonald wrote: > > There are some features missing for me in vTcl that I don't think are > > easily added: > > This first one might not be so hard. > > > - multi source file development. > > The biggest deal here is that all the code that is sourced into > vtcl becomes part of the vtcl project. By that I mean when you > save your work everything, including all the sourced code, is saved. Just making sure I understand this...if you have multiple source files and you source them in your vtcl file...those seperate files are assimilated into the new vtcl source for the current project? Why was it done this way instead of leaving them in their original file? > There is a set of code that is not saved, that is the vtcl code it's > self. from what I can tell is that all the code that is prefixed with > 'vTcl' is not saved. One solution might be to turn this around and > define a prefix unique to each vtcl project ( or file ). Now use that > prefix to mark procs in the vtcl project. This set of prefixed procs > could be the only ones saved that way an external set of procs > could be used. > > > - calling one vTcl project from another. > > tcl was meant to be process glue from the start. > I think that should be done in software. open a pipe or something. > > Or am I missing something. > > Is this different from multi source file development? So this would require searching and identifying piping commands? or references to external commands? with these being included in the project tree? > > - multiple instances of a toplevel, including some sort of > > dynamic widget alias scheme. I thought there already was an aliasing scheme (I seem to recall something like that in the tutorial)? I don't recall if it works on the top level though. When would you need multiple toplevel items? Could you just have .($toplevel1) and .($toplevel2) just as easily? Isn't this a tcl/tk shortfall (only have one . and when you kill it, it exits the program - right?) > vtcl does not do dynamic widget creation. What I do is let vtcl make a prototype. > than I include that in a proc and a loop. (ie. I do my self) What do you mean when you say it doesn't do dynamic widget creation? As I understand vtcl, it is more for making the gui and you fill in how the gui reacts (when it's loaded, when it's hidden) I am a little rusty on my tcl/tk/vtcl so forgive me if I'm slightly off.. Eric Bresie --- To unsubscribe from the Visual Tcl mailing list, please send a message to [EMAIL PROTECTED] with "unsubscribe vtcl [EMAIL PROTECTED]" in the message body (where [EMAIL PROTECTED] is your e-mail address).
RE: [vtcl] anything new since 1.2.0?
Well...glad to here you are keeping busy. > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] > > It's true that I've begun to transition vtcl to sourceforge. The 1.2 and 1.3 CVS trees have been > imported. What's there is the most current stuff I have. I would also like > to transition the web site, mailing list and bug tracking facility. Since > I haven't had a lot of contiguous time to devote it's taking longer than > expected. Can you put the faq that Joao sent into the doc section of the cvs tree? > Over the last 2 years I've received a very low volume of patches. I cannot > judge from this the fluency of the vtcl user base as candidates for active > maintenance (update access to CVS). This and just a complete lack of time > have been the biggest barriers to ongoing development. Perhaps you can post something on any of the tcl/tk related newsgroups or mailing lists (if such things exist - I'm afraid this is as far as I read on the tcl/tk front) for those interested in maintaining it. > It's true that I > had much larger plans for vtcl than I ever got around to building. It's > still my hope to get there (or somewhere like it) someday whether or not > it's me who does the maintenance. Moving the site and source base to > sourceforge guarantees that it can be maintained in my absence. Do you think (I am not familiar with the sourceforge feature, but) that with the Survey section a wish list could be included or would that be better in the forum..or the bug tracking (say it's a bug in that the feature is missing and doesn't get closed until the desired feature is included) Perhaps in the forum and/or here, you could indicate your wish list also to have some kind of ideas of the direction you were hopiong the project would move towards. Fabien Coutant seem to have a nice todo/wish list started already. Perhaps you could indicate you plans (if you have any more that aren't already there) in the TODO Since I am not familiar specifically with the bugs listed in the TODO...do you think you can add these bugs to the bug tracking, in addition to those you mentioned here? Or is they identifiable in the mailing list archives? > I would be interested to hear your thoughts on how to select maintainers > (no more than two) for vtcl. It may be obvious to those who track the list > in which case nominations are in order (or nominate yourself). I think probable the best bet is to initially either have people send you patches and update it yourself, minimizing who has access...(until you find a co/replacement maintainer) but this can causes you extra work to validate patches (unless you accept on faith - which seems a little risky).. ..or find a co maintainer to do that job.. ..or give multiple people access (who have given patches or shown interest in maintaining it) with an occasional change review, and accept or deny as necessary, with denied ones being removed (but this might cause some confusion). ..for criteria for picking... (1) have they sent you patches (2) do they post regularly on the mailing list? (3) do they have free time to work on it? (4) are they currently using vtcl on a regular basis? (5) Are they using vtcl on an existing program? (6) are they working or have they worked on any similar development (any open source projects)? > A word or two on the 1.3 source base. As it stands, 1.3 runs and saves > but cannot re-load a project it has saved. I began to change the file > format to something more modular. The UI has changed significantly. I was > working on a tabbed panel for preferences and pluggable icon/widget bars. > Do not use 1.3 unless you want to a) kick the tires or b) write code to > fix it. Option 'b' will require a bit of investment to understand the code. > My apologies that is it not better commented. Perhaps we should make sure the docs re-emphasize the (major.minor version numbers with minor numbers being odd implies beta/development) - if they don't already. > Stewart > On Mon, 20 Mar 2000, Eric Bresie wrote: > > > I was just noticing this... > > > > http://sourceforge.net/project/?group_id=285 Can we include this reference in the mailing list tail to access this site instead of yours? Eric Bresie --- To unsubscribe from the Visual Tcl mailing list, please send a message to [EMAIL PROTECTED] with "unsubscribe vtcl [EMAIL PROTECTED]" in the message body (where [EMAIL PROTECTED] is your e-mail address).
RE: [vtcl] anything new since 1.2.0?
I was just noticing this... http://sourceforge.net/project/?group_id=285 It seems like the cvs tree that's on there has a lot of 1.2 code imported, however I am curious if any changes that may have been made on this one differ from the 1.3 code? Also..can we move the FAQ as part of the sourceforge.net cvs tree? perhaps in the docs? Then we can hopefully track it a little better. And also have it associated with a specific version also. Stewart is the Project Administrator (is he still working on this or should we have someone else take over). To be a developer you apparently have to contact Stewart. As a developer you can have access via ssh cvs access. I am not real familar with how sourceforge works...(but I am looking at it)..This looks like a good place to put things though, with a message forum, bug tracking, etc. Althought it seems like we might want to see about getting this mailing list included in the mailing list portion and/or moved over their. And maybe also move the home page their also. Eric Bresie > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Joao Cardoso > Sent: Friday, March 17, 2000 12:03 PM > To: [EMAIL PROTECTED] > Subject: Re: [vtcl] anything new since 1.2.0? > > > Uwe Koloska wrote: > > > > You wrote on Mit, 15 Mär 2000: > ... > > a FAQ maintainer was there -- is he still involved? > > Not really. The FAQ hasn't been updated for centuries. > > Most of the FAQs in the mailing list are really tcl/tk ones, and for > that that are excelent tcl/tk FAQs. > > Also, and nonelethess of the 'robots.txt' file the FAQ page is acessed > from robots, and that is ruining my budget... I would be happy if > someone hosted it. Perhaps vtcl.sourceforge.net? > Joao Cardoso, [EMAIL PROTECTED] --- To unsubscribe from the Visual Tcl mailing list, please send a message to [EMAIL PROTECTED] with "unsubscribe vtcl [EMAIL PROTECTED]" in the message body (where [EMAIL PROTECTED] is your e-mail address).
RE: [vtcl] can't save
What version of tcl/tk and vtcl are you using? I tried doing a "Save As.." with tcl/tk 8.3 (on Windows NT) with Vtcl 1.3.0a1 as soon as I start of Visual TCL (without having added anything yet) and I get a similar problem. Since I am on Windows NT 4, I am wondering if any of this has to do with permissions. I installed and am using it as a normal user (not Administrator). Could I have not set something in the registry or do not have an environment variable set correctly? Or maybe it is trying to save the preferences in a directory that I don't have permissions? The Stack Trace for Error is as follows (I am typing this in so hopefully there aren't any typos): unknown option "-title" while executing "toplevel.vTcl.statbar -title "Progress"" (procedure "vTCL:statbar" line 8) invoked from within "vTCL:statbar [expr ($vTcl(num,index)*100)/$vTcl(num,total)]" (procedure "vTCL:dump_top" line 45) invoked from within "vTCL:dump_top $i $file " (procedure "vTCL:save_tree" line 17) invoked from within "vTCL:save_tree . $file" (procedure "vTCL:save2" line 47) invoked from within "vTCL:save2 $file" (procedure "vTCL:save_as" line 6) invoked from within "vTCL:save_as" (menu invoke) Followed shortly by the following while trying to quit invalid command name ".vcl.ae.c.tops.f.f2.list" while executing "$base.f2.list delete 0 end" (procedure "vTcl:update_top_list line 5) invoked from within "vTcl:update_top_list" (procedure "vTcl:close" line 20) invoked from within "vTcl:close" (procedure "vTcl:quit" line 3) invoked from within "vTcl:quit" (command for "WM_DELETE_WINDOW" window manager protocol) Also, shortly after this, I have no focus on any of the vTcl windows. I have to end up killing vTcl with the Task Manager. Eric Bresie [EMAIL PROTECTED] > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > John J. cruz > Sent: Monday, March 06, 2000 4:31 PM > To: [EMAIL PROTECTED] > Subject: [vtcl] can't save > > > Visual tcl is better then I had hope for (maybe replace visual basic?). > I have a slight problem that I'm sure is my fault. My problem is that > I can not save. I'm using tk only for now, just to experiment with > Visual TCL. I click on the save as button, a directory comes up and I > select a directory. When I press enter this message is displayed, > "Error: unknown option "-title". What have I done wrong? > > jjc > PS: I'm using Linux Red Hat 6.0 --- To unsubscribe from the Visual Tcl mailing list, please send a message to [EMAIL PROTECTED] with "unsubscribe vtcl [EMAIL PROTECTED]" in the message body (where [EMAIL PROTECTED] is your e-mail address).
RE: [vtcl] vtcl and Perl/Tk
Could you do something along the same lines as what was done with the Vtcl Java version? Might require a little work, but maybe.. http://www.java.ro/vtclava/index.html Eric Bresie [EMAIL PROTECTED] > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Mark Kvale > Sent: Wednesday, March 01, 2000 3:53 PM > To: [EMAIL PROTECTED] > Subject: Re: [vtcl] vtcl and Perl/Tk > > > > has anybody tried to modify vtcl in order to generate Perl/Tk code? > > Which vtcl script files have to be modified ? > > Here is what I wrote before. I don't think the situation has changed much: > > Porting specTcl to perl/Tk was comparatively easy because specTcl compiles > into an IR (intermediate representaion), from which several backends, > such as Tck/Tk, java, perl/Tk, and more recently python, could generated. > Thus all I had to do was create an IR->perl/Tk converter and muck around > a little with the specTcl UI to accept perl variables, etc. As I > understand it, and please correct me if I am mistaken, vtcl projects are > stored in native Tcl/Tk and may even use the same code for both storage > and display in vtcl. I suspect one may have to do a good deal of > modification in many different files to generate perl/Tk code in vtcl and > keep the perl code synchronized with the tcl code. There are some > aspects, > such as composite widgets, that would be even trickier to handle. > As I see > it, there are four possible roads to creating "vperl": > > 1) Modify many of the vtcl modules to generate perl code in parallel with > tcl code, possibly forgo niceties like composite widgets. This might be > difficult to maintain, as perl code would be distributed and deeply > intertwined in the tcl code. > > 2) Use the specTcl model: modify vtcl to gereate an IR and create tcl > and perl backends for it. With some extensions, the specTcl IR could > probably do the trick. > > 3) Leave vtcl unchanged and a create program to covert the generated tcl > code to perl. We need a good tcl2perl porgram :) > > 4) The most ambitious, but perhaps most rewarding, approach would be to > rewrtie vtcl in perl. Then all the code would be native, the UI would > be guaranteed WYSIWYG and there would be no translation subtleties. > > I've started on 4), but haven't gotten far yet. > > -Mark > -- > - > To unsubscribe from the Visual Tcl mailing list, please send a message > to [EMAIL PROTECTED] with "unsubscribe vtcl [EMAIL PROTECTED]" in the > message body (where [EMAIL PROTECTED] is your e-mail address). --- To unsubscribe from the Visual Tcl mailing list, please send a message to [EMAIL PROTECTED] with "unsubscribe vtcl [EMAIL PROTECTED]" in the message body (where [EMAIL PROTECTED] is your e-mail address).
