XPSE

- Page 1 -

Ragnar
Rehbein

a GUI stops I ditto not for necessary.

there for XPSE a todo-list ? Have I do not found.

therefore here short a wish The me to that XPSE to occur, even if it To christmas sure nothing more becomes (anyway not this year)

- it would helpful, if You the integrate of ph-Files on whom beginning settle could. in link with VWP2 is it often difficult The right place to find, so the integrate into proceduren then too The konstanten already famous are. (just as How You The global variables sortierst)

- several batch-switch nacheinander wären helpful, so z.b. The exe immediate in different directories copies go can.

- genial would a management of Builds. d.h. eachone compilerlauf counts a number (Build high). in the Program becomes these number of/ one konstanten transfer, so The buildnr. somewhere showing can. on wish ought to the .enh-File by the buildnummer complement go can. evtl. a anschließende kompression through batch-command.
so had one To each Program the my 4 walls leaves the spring archived and can with fehlermeldungen (The almost immmer The zeilennummer include) aimed search.
{$build projektxy.build &buildnr}
{$batch copy projektxy.enh projektxy_#buildnr#.enh}

in a File projektxy.build becomes The buildnr (as string) hochgezählt.
in the proposition becomes a konstante &buildnr created and allocated (evtl. alternatively too string $buildnr)
#buildnr# can as Placeholder using to be a suitable kopieroperation To datensicherungszwecken To join.
imaginable would too the verweis on a headerdatei, The into proposition eingebunden and that the from the XPSE updated becomes.

r.r.

12/02/05 ▲

Very nice suggestions!

i'll these umsetzen.

Specifically to the PH-Files - I hope thats Perhaps even not at all More declared go must - without Speedverlust!

salvo.

12/02/05 ▲

Michael
Wodrich

with the Build-story helps sure a INI.

[Projektname]
Build=101

[Projektname2]
Build=231

the jeweilige Program can itself then The Buildnummer self herausfischen. One Unterprogramm in the jeweiligen Program can then The desired activities self durchführen; because this is certainly each Programmer differently resolved.

so one not for each Program the wheel new invent must helps then Yes a Include-File.

so would XPSE then entlastet and need itself only around the Hochzählen concern. the append the Buildnummer on whom ENH-names would too me help

(verworfenes)

Versionsnummern can indeed programmintern from the Buildnummer produce:
BuildNr$ = ReadIni(C:\ProfanXPSE-projects.INI, Projektname2, Build)
Case BuildNr$=231 : Version$ = 2.02
Case BuildNr$=232 : Version$ = 2.10

Best wishes
Michael Wodrich

Programmieren, das spannendste Detektivspiel der Welt.

12/04/05 ▲

Ragnar
Rehbein

Hello michael

i think the with the the ini-File, so How You you the vorstellst, not functions.
The buildnummer must solid with each begot proposition and compilerlauf joined his.
therefore my überlegung the by a headerdatei To make The of XPSE updated becomes.

r.r.

12/04/05 ▲

Jac
de
Lad

Related to the Build sound well, had I yet always differently release. but well would too, if XPSE with Fehlern and Warnungen not only The row, separate The wirkliche Line and The suitable File spend would. once a INC includiert is, becomes always everything moved what about me find it umständlich, that if I not immediate white where the Error is, I always first The ENH-File search must and then again zurückspringen...this is irritating!

Jac

Profan² 2.6 bis XProfan 11.1+XPSE+XPIA+XPRR (und irgendwann XIDE)
Core2Duo E8500/T2250, 8192/1024 MB, Radeon HD4850/Radeon XPress 1250, Vista64/XP

12/04/05 ▲

- Page 2 -

so for diejenigen The XPIA benefit have I soebend on Franks Please there one KLEINES XPSE-Update uploaded.

The instruction ASMEND with Parameter means z.B. ASMEND (Z&) functions now.

One größeres XPSE-Update standing so naturally yet from - but in the momentum have I simply To plenty around the ears.

01/14/06 ▲

Jac
de
Lad

Schade, but the enhance The thrill, what it well new there!

Jac

Profan² 2.6 bis XProfan 11.1+XPSE+XPIA+XPRR (und irgendwann XIDE)
Core2Duo E8500/T2250, 8192/1024 MB, Radeon HD4850/Radeon XPress 1250, Vista64/XP

01/15/06 ▲

Jac
de
Lad

Hello iF, I had already something because of Buildnummern addressed. is it possible, a variable BuildNumber[Long] incorporate, The each Compilieren circa 1 hochgesetzt becomes? moreover could XPSE either a File BuildNumber.txt lay out, The quizzed and new stored becomes or a Compilierschalter $Build xyz receive, what me personally rather fallen would. then would The Buildnummer too always in the View source stand and not lost weg. Should only with the editor harmonieren...the must Yes then new loading.

Jac

Profan² 2.6 bis XProfan 11.1+XPSE+XPIA+XPRR (und irgendwann XIDE)
Core2Duo E8500/T2250, 8192/1024 MB, Radeon HD4850/Radeon XPress 1250, Vista64/XP

The Constant XPSECOMPILETIMESTAMPSTRING is brauchbarer as a simple BuildNr (these Nr. uses Yes in the Nachhinein often mere garnichts).

Jac
de
Lad

Yes and No. The Buildnummer is for developer partly already of weight...

Profan² 2.6 bis XProfan 11.1+XPSE+XPIA+XPRR (und irgendwann XIDE)
Core2Duo E8500/T2250, 8192/1024 MB, Radeon HD4850/Radeon XPress 1250, Vista64/XP

The XIDE (Yes - unfortunately not yet publizierfähig!) has this feature intus, and of course over freiprogrammierbare Plugins. I can the XPSE means this feature beruhigt save.

Jac
de
Lad

Profan² 2.6 bis XProfan 11.1+XPSE+XPIA+XPRR (und irgendwann XIDE)
Core2Duo E8500/T2250, 8192/1024 MB, Radeon HD4850/Radeon XPress 1250, Vista64/XP

12/04/07 ▲