Winbuilder Version 82 - What Happened?
#1
Posted 16 August 2011 - 12:07 PM
#2
Posted 16 August 2011 - 12:10 PM
You can grab the final version here: http://reboot.pro/fi...e/4-winbuilder/
There wasn't a big announcement cause we might still get some report of little details in need of correction and need to update binary.
#3
Posted 16 August 2011 - 12:18 PM
Hello,
You can grab the final version here: http://reboot.pro/fi...e/4-winbuilder/
There wasn't a big announcement cause we might still get some report of little details in need of correction and need to update binary.
So it's not "final" is "tentative release #x" with not even a hint of the approximate value of "x"
Wonko
#4
Posted 16 August 2011 - 12:27 PM
#5
Posted 16 August 2011 - 01:19 PM
Maybe you know the James Bond Movie titled (my translation, the English title may be different) "Never say Never"So it's not "final" is "tentative release #x" with not even a hint of the approximate value of "x"
Wonko
Comparable: No "Final" is "For Ever". It is for (propably) long time.
Peter
#6
Posted 16 August 2011 - 01:38 PM
d@mn board software.
Wonko
#7
Posted 16 August 2011 - 01:59 PM
Winbuilder follows its own standard definition of "final"
Sure.
The implied suggestion was :
Always check the TO-DO-list:Wait a few (latin) days before assuming that that one is the "final" version.
Is it the one with :Maybe you know the James Bond Movie titled (my translation, the English title may be different) "Never say Never"
Naah, that one was Goldfinger...
Wonko
#8
Posted 17 August 2011 - 01:21 AM
#9
Posted 17 August 2011 - 10:03 AM
#10
Posted 17 August 2011 - 12:08 PM
#11
Posted 17 August 2011 - 12:22 PM
Where did you get your assumption that 083 will be compiled with borland?
Peter
#12
Posted 17 August 2011 - 12:33 PM
As was said some time ago, the winbuilder engine will remain as the winbuilder engine.Glad to hear there is going to be a 083 version. I had thought version 082 may be the last version using the Borland compiler.
What we can do is provide services on top of the engine that are powered, say, by Java. Neither of these changes are over night or written in stone. We move and test each step to see if the results are good or not.
#13
Posted 17 August 2011 - 01:21 PM
Yes, I agree with your comment. Currently I am happy with the current 082 edition and I think we can settle with the current binary to start addressing in version 083 the reported defects.
I'm not. the PackParm command is still broken. which is a serious setback in the progress I"m trying to make on a script as well as breaking some functionality in the CAPI
other than that I haven't seen anymore serious problems. A few random instances where moving interface components doesn't save and reverts to the old positions but I haven't been able to reliably reproduce the behavior yet.
#14
Posted 17 August 2011 - 01:23 PM
Send me an example where PackParam fails. I was sure that it has been fixed.
I'm not. the PackParm command is still broken. which is a serious setback in the progress I"m trying to make on a script as well as breaking some functionality in the CAPI
other than that I haven't seen anymore serious problems. A few random instances where moving interface components doesn't save and reverts to the old positions but I haven't been able to reliably reproduce the behavior yet.
Peter
#15
Posted 17 August 2011 - 01:47 PM
re-downloaded 82.0.1.0 and now it is working...the download I did yesterday still showed 82.0.0.15Send me an example where PackParam fails. I was sure that it has been fixed.
Peter
#16
Posted 17 August 2011 - 02:00 PM
But now bad news: There is also a bug in GetParam
Until next release it can be worked-around by using StrFormat:
[process] Run,%ScriptFile%,Pack,1,2,something with space,4,5,6,7,8,9,10,11,12,13 [pack] PackParam,1,%packed% GetParam,3,%Value% Echo,%Value% StrFormat,SPLIT,%packed%,#$c,3,%Value% Echo,%Value%
Log 082:
Run - Processing section: [Pack] From file: [%BaseDir%\Projects\multiPE\CodeBox.txt]
file:///V:/multiPE/Pictures/parameter.gif with parameters: [1],[2],[something with space],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13]
file:///V:/multiPE/Pictures/accept.gif PackParam - Sucessfuly changed the value of [%packed%] to: [1,2,something with space,4,5,6,7,8,9,10,11,12,13]
file:///V:/multiPE/Pictures/accept.gif GetParam - Sucessfuly changed the value of [3] to: [something with space]
file:///V:/multiPE/Pictures/info.gif %Value%
file:///V:/multiPE/Pictures/accept.gif StrFormat - converted [SPLIT(1,2,something with space,4,5,6,7,8,9,10,11,12,13,,)] to variable: [%Value%] with result: [something with space]
file:///V:/multiPE/Pictures/info.gif something with space
Run - Processed section [Pack] in file: [%BaseDir%\Projects\multiPE\CodeBox.txt]
Log 080:
Run - Processing section: [Pack] From file: [%BaseDir%\Projects\multiPE\CodeBox.txt]
with parameters: [1],[2],[something with space],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13]
PackParam - Sucessfuly changed the value of [%packed%] to: ["1","2","something#$swith#$sspace","4","5","6","7","8","9","10","11","12","13"]
GetParam - Sucessfuly changed the value of [%Value%] to: [something#$swith#$sspace]
something with space
StrFormat - converted [SPLIT(%packed%,,,3)] to variable: [%Value%] with result: [something with space]
something with space
Run - Processed section [Pack] in file: [%BaseDir%\Projects\multiPE\CodeBox.txt]
Peter
#17
Posted 17 August 2011 - 03:18 PM
#18
Posted 17 August 2011 - 03:25 PM
When you use an external app, to change an actual open WinBuilder script, IMO it is not in the responsibility of WinBuilder what happens then.
Peter
BTW: Current WB version is 82.0.1.0
#19
Posted 17 August 2011 - 11:24 PM
However winbuilder should not hang. It should give an error.
#20
Posted 17 August 2011 - 11:28 PM
Must have misunderstood what you wrote earlier then. I thought you said winbuilder was being rewritten in Java.
#21
Posted 18 August 2011 - 01:42 AM
thats what I understood as well.@Nuno,
Must have misunderstood what you wrote earlier then. I thought you said winbuilder was being rewritten in Java.
#22
Posted 18 August 2011 - 05:29 PM
As long as end user experience is OK, either is fine with me.
#23
Posted 18 August 2011 - 06:04 PM
Actually with race cars the really difficult part is hide the new technologies used, confuse competitors and observers, drop casual comments to deceive them, all things that the good guys coding Winbuilder do perfectly well!I think it is a lot like trying to build a new race car while still running the race...You can either try to build a totally new car - OR - replace bits and pieces until eventually all the parts have been replaced...
Ditto as above!As long as end user experience is OK, either is fine with me.
Wonko
#24
Posted 18 August 2011 - 07:47 PM
Then place this thought as a request at the appropriate forum section.I agree. Its a bug in my program. It should not let you add a png file. Only supported types are jpg, gif, icon, emf, wmf.
However winbuilder should not hang. It should give an error.
What I wrote at the time can be found here:thats what I understood as well.
http://reboot.pro/14...post__p__129080
It says nothing about 083 being exclusively in Java:
In September 2011 (or sooner), a new platform using this concept of web services and asynchrony will be made available. The next version of Winbuilder around December 2011 will feature basic integration with this platform. Slowly we'll begin the transition to Java to ensure that past works remain functional.
Perhaps now more people also understand why I am so worried about seeing a really well structured API, it eases the porting of apps scripts to other platforms and projects that are not available today, instead of forcing everyone to rewrite them later.
The new web based Java platform was introduced in June (remedium), last week we introduced the concept of download portal web service to host app scripts. PSC is already working on a tool to interact with the new portal as we speak. On the same post I describe that winbuilder will be open to web requests so that other tools can fetch important details like the log of the ongoing project and/or set variables at running projects.
The dates are indicative, other factors might slow down or speed up the date of delivery for the planned features.
#25
Posted 18 August 2011 - 09:41 PM
What I wrote at the time can be found here:
http://reboot.pro/14...post__p__129080
It says nothing about 083 being exclusively in Java:
I don't remember anybody specifically saying it would be in the next version (083)
but the quote:
does say that you hope to migrate Winbuilder completely from Delphi to Java in the distant future....
Last but not least, there also plans for moving the WinBuilder engine from Delphi/Windows to the OS agnostic Java platform. It is of our best interest to only adopt new functionalities not tied to Windows from here forward while transitioning the current features to a platform agnostic state that can continue running in future years without worries.
...
One note of advice, these are plans for the upcoming years.
In September 2011 (or sooner), a new platform using this concept of web services and asynchrony will be made available. The next version of Winbuilder around December 2011 will feature basic integration with this platform. Slowly we'll begin the transition to Java to ensure that past works remain functional.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users