www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.ide - Dexed, revived!

reply Akira1364 <operator97 gmail.com> writes:
Thanks to someone who commented on this Reddit thread I made 
about it:

https://www.reddit.com/r/d_language/comments/ddrmz8/had_anyone_checked_out_dexed_locally_relatively/?st=k1uppkuk&sh=c643c481

I was able to track down a full copy of almost-the-latest-version 
of the Dexed repo (version 3.7.4) and have put it up here:

https://github.com/Akira13641/dexed

No binary downloads available yet, but I'll try to get them up 
for at least the platforms they were originally available ASAP 
(and perhaps, eventually for Mac, as the Cocoa backend for 
Lazarus is pretty mature at this point.)

There's a few obvious (to me at least) bugs with regards to the 
window docking system that I intend to fix first, though (as well 
as a few other things that strike me as having clear room for 
improvement.)
Oct 17 2019
next sibling parent reply Dennis <dkorpel gmail.com> writes:
On Thursday, 17 October 2019 at 13:03:08 UTC, Akira1364 wrote:
 I was able to track down a full copy of 
 almost-the-latest-version of the Dexed repo (version 3.7.4) and 
 have put it up here:
I'm glad to see it survive! I'm using Visual Studio Code myself but when I tried Dexed I was impressed how extensive it was for a one-man effort. It was mostly the built-in text-editor that felt lacking compared to other IDE's that kept me from using it more. I hope Basile is doing well.
Oct 18 2019
parent reply Akira1364 <operator97 gmail.com> writes:
On Friday, 18 October 2019 at 19:41:03 UTC, Dennis wrote:

 It was mostly the built-in text-editor that felt lacking 
 compared to other IDE's that kept me from using it more.
What did you miss with regards to it, exactly? I'm definitely interested in doing my best to make any improvements people may be / may have been hoping for, and I know the editor widget library (Synedit) quite well.
Oct 18 2019
parent reply Dennis <dkorpel gmail.com> writes:
On Friday, 18 October 2019 at 21:14:18 UTC, Akira1364 wrote:
 What did you miss with regards to it, exactly?
I should definitely give it another try, but from what I remember, I couldn't find (the equivalent of) some of my common VS code operations: - cut / copy / paste a line with ctrl+x/c/v when there is no selection - move a line / selection of lines with alt + up/down - create multiple cursors with meta+shift+arrow keys
Oct 18 2019
parent reply rikki cattermole <rikki cattermole.co.nz> writes:
On 19/10/2019 10:41 AM, Dennis wrote:
 - cut / copy / paste a line with ctrl+x/c/v when there is no selection
That is a feature that I missed heavily from Monodevelop. Basile did manage to get it sort of ok, but it never did work right.
Oct 18 2019
parent Akira1364 <operator97 gmail.com> writes:
On Saturday, 19 October 2019 at 02:34:35 UTC, rikki cattermole 
wrote:
 Basile did manage to get it sort of ok, but it never did work 
 right.
SynEdit definitely supports that in general, and trying it in Dexed just now seemed to work normally enough to me. What were the issues you noticed?
Oct 18 2019
prev sibling next sibling parent reply Basile B. <b2.temp gmx.com> writes:
On Thursday, 17 October 2019 at 13:03:08 UTC, Akira1364 wrote:
 Thanks to someone who commented on this Reddit thread I made 
 about it:

 https://www.reddit.com/r/d_language/comments/ddrmz8/had_anyone_checked_out_dexed_locally_relatively/?st=k1uppkuk&sh=c643c481

 I was able to track down a full copy of 
 almost-the-latest-version of the Dexed repo (version 3.7.4) and 
 have put it up here:

 https://github.com/Akira13641/dexed

 No binary downloads available yet, but I'll try to get them up 
 for at least the platforms they were originally available ASAP 
 (and perhaps, eventually for Mac, as the Cocoa backend for 
 Lazarus is pretty mature at this point.)

 There's a few obvious (to me at least) bugs with regards to the 
 window docking system that I intend to fix first, though (as 
 well as a few other things that strike me as having clear room 
 for improvement.)
Hi, you can get the binaries for linux here: https://c.gmx.com/ 558129942915716568/Mjsfj0odTRCDzKyMs6nEsQ https://c.gmx.com/ 558129942915716568/pWdPdzE_SPSc-7LgMYdg4Q https://c.gmx.com/ 558129942915716568/OP2NNDW2SJiyDUsEGUZuaQ https://c.gmx.com/ 558129942915716568/0R9q_SMSTk6gasfHg-8aNA Note that at this point I'm pretty sure (96%) that I won't come back. Add to this conviction the fact that I've been contacted for a resell of the project and that I had no active projects in D anymore, so I won't restart working on this neither give support about the project (from the "how it's made" POV. If it's sold I'll probably furnish a document about the internals), now that I realize it probably has value. It should just be good for some time if you update the dparse sub repository when grammar changes, and then rebuild "dastworx", because at some point new features will lead to false errors in the "symbol list" otherwise. I've seen that new features implying grammar changes may come (named args..., string interpolation, ...) docking issues come from the Lazarus component library so they have to be fixed in the component that is used (AnchorDocking), good luck with that ;)
Oct 19 2019
parent reply Akira1364 <operator97 gmail.com> writes:
On Saturday, 19 October 2019 at 11:59:23 UTC, Basile B. wrote:
 Hi, you can get the binaries for linux here:

 https://c.gmx.com/ 558129942915716568/Mjsfj0odTRCDzKyMs6nEsQ
 https://c.gmx.com/ 558129942915716568/pWdPdzE_SPSc-7LgMYdg4Q
 https://c.gmx.com/ 558129942915716568/OP2NNDW2SJiyDUsEGUZuaQ
 https://c.gmx.com/ 558129942915716568/0R9q_SMSTk6gasfHg-8aNA
Thanks for the binary links, Basile, that's definitely quite helpful.
 Note that at this point I'm pretty sure (96%) that I won't come 
 back.
That's ok, honestly. Applications like Dexed are right up the alley of what I do at work so it's not much of a stretch for me.
 docking issues come from the Lazarus component library so they 
 have to be fixed in the component that is used (AnchorDocking), 
 good luck with that ;)
I have no intention of using anything other than trunk FPC and trunk Lazarus to develop Dexed, TBH. AnchorDocking specifically has received a number of fixes recently and works quite well overall I'd say. Even before, I've used it successfully in several other apps I've worked on without encountering too many "bumps in the road".
Oct 19 2019
parent reply Basile B. <b2.temp gmx.com> writes:
On Sunday, 20 October 2019 at 00:18:36 UTC, Akira1364 wrote:
 On Saturday, 19 October 2019 at 11:59:23 UTC, Basile B. wrote:
 [...]
Thanks for the binary links, Basile, that's definitely quite helpful.
 [...]
That's ok, honestly. Applications like Dexed are right up the alley of what I do at work so it's not much of a stretch for me.
 [...]
I have no intention of using anything other than trunk FPC and trunk Lazarus to develop Dexed, TBH. AnchorDocking specifically has received a number of fixes recently and works quite well overall I'd say. Even before, I've used it successfully in several other apps I've worked on without encountering too many "bumps in the road".
Why didn't you participate to the project in the past, are you a new comer to D ?
Oct 20 2019
parent Akira1364 <operator97 gmail.com> writes:
On Sunday, 20 October 2019 at 16:46:34 UTC, Basile B. wrote:
 Why didn't you participate to the project in the past, are you 
 a new comer to D ?
As it stands now I don't even really use D myself at all. I've been a professional Object Pascal programmer forever though, and was always aware of Dexed as a project, and thought it was a good example of the kinds of things that can be built with Lazarus. I basically just wanted to "save" it simply because it seemed like a huge waste to me to let such a large, high-quality codebase disappear so easily.
Oct 20 2019
prev sibling next sibling parent reply Basile B. <b2.temp gmx.com> writes:
On Thursday, 17 October 2019 at 13:03:08 UTC, Akira1364 wrote:
 I was able to track down a full copy of 
 almost-the-latest-version of the Dexed repo (version 3.7.4) and 
 have put it up here:

 https://github.com/Akira13641/dexed
You shouldn't have added mir-core dependency. stdx allocators repository has a branch named "2.77.z" ([1]) that doesn't rely on mir-core. Most (if not all) of the tools based on dparse + stdx allocs use this branch, exactly to prevent the dependency. For example here, in the folder names, [2], the " <hash>" points to the last commit of this "2.77.z" branch. The reference is concretely stored somewhere in the ".git" folder, so when people do "git submodule update" the right branch is automatically selected. [1]: https://github.com/dlang-community/stdx-allocator/tree/2.77.z [2]: https://github.com/dlang-community/DCD
Oct 21 2019
parent Akira1364 <operator97 gmail.com> writes:
On Monday, 21 October 2019 at 13:39:00 UTC, Basile B. wrote:
 You shouldn't have added mir-core dependency.

 stdx allocators repository has a branch named "2.77.z" ([1]) 
 that doesn't rely on mir-core. Most (if not all) of the tools 
 based on dparse + stdx allocs use this branch, exactly to 
 prevent the dependency. For example here, in the folder names, 
 [2], the "  <hash>" points to the last commit of this "2.77.z" 
 branch. The reference is concretely stored somewhere in the 
 ".git" folder, so when people do "git submodule update" the 
 right branch is automatically selected.

 [1]: 
 https://github.com/dlang-community/stdx-allocator/tree/2.77.z
 [2]: https://github.com/dlang-community/DCD
Good to know, I'll change the submodule to direct to that branch of stdx-allocator. Thanks!
Oct 21 2019
prev sibling next sibling parent reply Basile B. <b2.temp gmx.com> writes:
On Thursday, 17 October 2019 at 13:03:08 UTC, Akira1364 wrote:
 Thanks to someone who commented on this Reddit thread I made 
 about it:

 https://www.reddit.com/r/d_language/comments/ddrmz8/had_anyone_checked_out_dexed_locally_relatively/?st=k1uppkuk&sh=c643c481

 I was able to track down a full copy of 
 almost-the-latest-version of the Dexed repo (version 3.7.4) and 
 have put it up here:
latest version is 3.7.10 and is 130 commits ahead.
 https://github.com/Akira13641/dexed

 [...]
Akira, I'm sorry but I've reported your revival attempt to GH, with the hope that they'll remove it, because I'm not happy with how you've botched the git history. For anyone who's interested to buy dexed and to take the leadership on the project, I sell dexed, so a a git project, with intact commits tree, 2500€.
Nov 12 2019
parent reply Basile B. <b2.temp gmx.com> writes:
On Wednesday, 13 November 2019 at 01:43:39 UTC, Basile B. wrote:
 [...]
 For anyone who's interested to buy dexed and to take the 
 leadership on the project, I sell dexed, so a a git project, 
 with intact commits tree, 2500€.
Well well well they refused anyway. It looks like it's dead forever now about monetizing the work. ---------------------------------------------------------------- Your request has been updated. You can add a comment by replying to this email. Mitch (GitHub Developer Support) Nov 13, 2:00 PM UTC Hello, If you are the copyright holder and want to have copyrighted content removed, please review our DMCA Takedown Policy, available here: https://help.github.com/articles/dmca-takedown-policy https://help.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/ If you're not the copyright holder, your best bet would be to contact the owner of the content and let them decide if they'd like to take action. Cheers, Mitch basile.b Nov 8, 3:14 AM UTC Here is the original project as a bare repository so that you can verify that the user I've reported didn't play fairly and destroyed the git history. https://c.gmx.com/ 558129942915716568/XF6bnHFWSLenLobZiKxmcg The file is protected with a password that is the full email address used to send this email. Note that I only provide the file as mean of verification and it must not be used or shared in any other context. To clarify my request that is to block or delete the user repository: The history of a project is essential to understand how it has evolved over time. The commits messages are essential to understand why something is done in a way and not another. The history also allows to revert changes and to track regressions. Typically a git repository also contains branches with partial work that may be useful, this is the case here. That's why I do not accept the way the user I've reported restarted the project. It's a tag of disrespect, toward 5 years of work. I do not blame the user to get on developping the software, I blame it for destroying the software "as a project". Thanks for your understanding. Envoyé: jeudi 7 novembre 2019 à 03:12 De: "GitHub Developer Support" <developer githubsupport.com> À: "basile.b" <> Objet: [GitHub Developer Support] Confirmation - Request Received basile.b Nov 7, 2:12 AM UTC Akira13641has uploaded a repository of mine, botching/squashing the whole git history, without even contacting me, while it was deleted explictely from your site by myself (old account was Basile-z) The repository is https://github.com/Akira13641/dexed I can provide the project with intact history in case of. I wish his repo to be blocked unless he conserves the whole history of the commits (that's several thousands). ----------------------------------------------------------------
Nov 15 2019
next sibling parent reply Basile B. <b2.temp gmx.com> writes:
On Friday, 15 November 2019 at 09:02:55 UTC, Basile B. wrote:
 On Wednesday, 13 November 2019 at 01:43:39 UTC, Basile B. wrote:
 [...]
Well well well they refused anyway. It looks like it's dead forever now about monetizing the work. [...]
The project is now here: https://gitlab.com/basile.b/dexed To be clear, I have not any bit of respect to what is more or less affiliated to microsoft.
Jan 13
next sibling parent reply p.shkadzko <p.shkadzko gmail.com> writes:
On Tuesday, 14 January 2020 at 06:10:05 UTC, Basile B. wrote:
 On Friday, 15 November 2019 at 09:02:55 UTC, Basile B. wrote:
 On Wednesday, 13 November 2019 at 01:43:39 UTC, Basile B. 
 wrote:
 [...]
Well well well they refused anyway. It looks like it's dead forever now about monetizing the work. [...]
The project is now here: https://gitlab.com/basile.b/dexed To be clear, I have not any bit of respect to what is more or less affiliated to microsoft.
After moving away from github, you forgot to copy at least build and installation instructions ;) Now all your README.md links are 404ed.
Jan 15
parent user1234 <user12324 1234.de> writes:
On Wednesday, 15 January 2020 at 10:27:42 UTC, p.shkadzko wrote:
 On Tuesday, 14 January 2020 at 06:10:05 UTC, Basile B. wrote:
 On Friday, 15 November 2019 at 09:02:55 UTC, Basile B. wrote:
 On Wednesday, 13 November 2019 at 01:43:39 UTC, Basile B. 
 wrote:
 [...]
Well well well they refused anyway. It looks like it's dead forever now about monetizing the work. [...]
The project is now here: https://gitlab.com/basile.b/dexed To be clear, I have not any bit of respect to what is more or less affiliated to microsoft.
After moving away from github, you forgot to copy at least build and installation instructions ;) Now all your README.md links are 404ed.
The doc source is still there but not rendered and not served anymore. https://gitlab.com/basile.b/dexed/blob/master/docs/build.md
Jan 19
prev sibling parent p.shkadzko <p.shkadzko gmail.com> writes:
On Tuesday, 14 January 2020 at 06:10:05 UTC, Basile B. wrote:
 On Friday, 15 November 2019 at 09:02:55 UTC, Basile B. wrote:
 On Wednesday, 13 November 2019 at 01:43:39 UTC, Basile B. 
 wrote:
 [...]
Well well well they refused anyway. It looks like it's dead forever now about monetizing the work. [...]
The project is now here: https://gitlab.com/basile.b/dexed To be clear, I have not any bit of respect to what is more or less affiliated to microsoft.
Before moving away from github, you forgot to copy at least build and installation instructions ;) Now all your README.md links are 404ed.
Jan 15
prev sibling parent reply Akira1364 <operator97 gmail.com> writes:
On Friday, 15 November 2019 at 09:02:55 UTC, Basile B. wrote:
 [...]
I clearly didn't *intentionally* leave out the history. It simply didn't exist in the tarball someone on Reddit found, that I restored the repo from. Looking at some other comments from more recently here though it seems they did later on find one with the history intact (and more up to date sources), so I'll see if I can merge that all in.
Feb 24
parent reply Basile B. <b2.temp gmx.com> writes:
On Tuesday, 25 February 2020 at 03:28:07 UTC, Akira1364 wrote:
 On Friday, 15 November 2019 at 09:02:55 UTC, Basile B. wrote:
 [...]
I clearly didn't *intentionally* leave out the history. It simply didn't exist in the tarball someone on Reddit found, that I restored the repo from. Looking at some other comments from more recently here though it seems they did later on find one with the history intact (and more up to date sources), so I'll see if I can merge that all in.
Don't bother. You will not be able to develop it anyway. While you seemed to mostly care about the dependencies I've already pushed new features and fixes like - the global compiler ; - during debug, inspect variable from mouse motion on the editor ; - fixed constant load even on idle (was 3-4% on my 5-6 years old hardware) - support for GNU-style messages ; - removed some confusing fields in the compiler path editor ; Most of these stuff can only be programmed by someone who practices D a bit at least. You (non-nominative) have to follow the language devel constantly and adapt the IDE accordingly (support for GNU messages is there because I check the DMD PRs and the issues daily). In the same order of ideas I'm pretty sure that you don't even know that at some point SemVer version 2 will have to be supported. There's also some activity related to the tools and DMD as a library... You see you have to follow what's happening. Also since there are (almost) not tests you risk to break things without even realizing. You need to have advanced projects, advanced scripts (for example I have a few that link automagically dbeaengine or cairo, they allow me to verify that the runnables and the module registry work). But if you want to give a hand there are a few areas of the software that don't really require to know D well. The terminal for example... I'm sure that a Lazarus developer would be useful since it's mostly about a GTK2 widget. I still don't manage to put those damn scrollbars... Another thing is the support for GTK3. Dexed just crashes at startup when use the GTK3 widget set. The profile viewer is also something that can be enhanced, though if I really need to profile I would rather use callgrind + KCacheGrind.
Feb 25
parent reply Akira1364 <operator97 gmail.com> writes:
On Tuesday, 25 February 2020 at 14:48:28 UTC, Basile B. wrote:
 Most of these stuff can only be programmed by someone who 
 practices D a bit at least.
I don't really agree, to be honest with you. I'd say at the very least 80% of it doesn't actually require a lot of D knowledge at all as it's just pretty universal IDE stuff (process management, etc.) I did quite a bit more than just rework the dependencies, also, and none of it was very difficult at all. For example, I reworked literally all the uses of container classes in the entire project around LGenerics: https://github.com/avk959/LGenerics which is significantly more performant than any of FPC's built-in non-generic *or* generic ones. I also fixed several general bugs, like by getting rid of your unnecessary custom JSON encoding translator (which didn't even completely work properly) and just using normal stream functionality instead. Also, a lot of the issues you seem to have with the LCL / FPC and such just don't exist in the trunk versions, which is why I opted to use them to work on it instead of the "stable" ones.
Feb 25
next sibling parent Akira1364 <operator97 gmail.com> writes:
On Tuesday, 25 February 2020 at 19:53:58 UTC, Akira1364 wrote:
 [...]
Also, I actually have been taking a bit of time to familiarize myself with D a bit more specifically because I felt like I probably should if I was going to keep working on Dexed. I ported my FPC implementation of the "Binary Trees" benchmark (which is currently in first place on the benchmarksgame website) to D, and even managed to get it just about as fast (on my machine at least): https://github.com/Akira13641/BinaryTreesBenchmark
Feb 25
prev sibling parent reply Basile B. <b2.temp gmx.com> writes:
On Tuesday, 25 February 2020 at 19:53:58 UTC, Akira1364 wrote:
 [...]
 I also fixed several general bugs, like by getting rid of your 
 unnecessary custom JSON encoding translator (which didn't even 
 completely work properly) and just using normal stream 
 functionality instead.

 Also, a lot of the issues you seem to have with the LCL / FPC 
 and such just don't exist in the trunk versions, which is why I 
 opted to use them to work on it instead of the "stable" ones.
Yeah but did you try to load a goddamn JSON recipe that **has** the BOM written ? This stuff was there for a good reason you know ;)
Feb 25
parent reply Akira1364 <operator97 gmail.com> writes:
On Tuesday, 25 February 2020 at 21:45:04 UTC, Basile B. wrote:
 Yeah but did you try to load a goddamn JSON recipe that **has** 
 the BOM written ?
 This stuff was there for a good reason you know ;)
The reason BOMs weren't working for you was because you were using a TMemoryStream to actually load the JSON files, and TMemoryStream is just a stream of raw bytes that knows absolutely nothing about encodings. All I had to do to get rid of your 30 lines of "BOM skipping" code was change the file loading part to this: ``` List := TStringList.Create; List.LoadFromFile(FFileName, TEncoding.UTF8); Stream := TStringStream.Create(List.Text, TEncoding.UTF8, False); List.Free; Stream.Position := 0; ``` And then continue by creating the TJSONParser from `Stream`. Doing it that way works correctly BOM or no BOM.
Feb 25
next sibling parent Basile B. <b2.temp gmx.com> writes:
On Wednesday, 26 February 2020 at 03:10:30 UTC, Akira1364 wrote:
 On Tuesday, 25 February 2020 at 21:45:04 UTC, Basile B. wrote:
 Yeah but did you try to load a goddamn JSON recipe that 
 **has** the BOM written ?
 This stuff was there for a good reason you know ;)
The reason BOMs weren't working for you was because you were using a TMemoryStream to actually load the JSON files, and TMemoryStream is just a stream of raw bytes that knows absolutely nothing about encodings. All I had to do to get rid of your 30 lines of "BOM skipping" code was change the file loading part to this: ``` List := TStringList.Create; List.LoadFromFile(FFileName, TEncoding.UTF8); Stream := TStringStream.Create(List.Text, TEncoding.UTF8, False); List.Free; Stream.Position := 0; ``` And then continue by creating the TJSONParser from `Stream`. Doing it that way works correctly BOM or no BOM.
Okay, I recognize that I've been a bit unfair in the previous message but remember that this constructor overload does not exist yet in the freepascal library version 3.0.4, so I could not use it, hence those 30 lines had to be written.
Feb 27
prev sibling parent reply Basile B. <b2.temp gmx.com> writes:
On Wednesday, 26 February 2020 at 03:10:30 UTC, Akira1364 wrote:
 On Tuesday, 25 February 2020 at 21:45:04 UTC, Basile B. wrote:
 Yeah but did you try to load a goddamn JSON recipe that 
 **has** the BOM written ?
 This stuff was there for a good reason you know ;)
The reason BOMs weren't working for you was because you were using a TMemoryStream to actually load the JSON files, and TMemoryStream is just a stream of raw bytes that knows absolutely nothing about encodings. All I had to do to get rid of your 30 lines of "BOM skipping" code was change the file loading part to this: ``` List := TStringList.Create; List.LoadFromFile(FFileName, TEncoding.UTF8); Stream := TStringStream.Create(List.Text, TEncoding.UTF8, False); List.Free; Stream.Position := 0; ``` And then continue by creating the TJSONParser from `Stream`. Doing it that way works correctly BOM or no BOM.
Okay, I recognize that I've been a bit unfair in the previous message but remember that this constructor overload does not exist yet in the freepascal library version 3.0.4, so I could not use it, hence those 30 lines had to be written.
Feb 27
parent reply RegeleIONESCU <regeleionescu gmail.com> writes:
Dear Sir, I am following your instructions on how to compile and 
build Dexed on Windows 10. Could you please help me find out why 
I get the following error?

C:\temp\dexed-v3.8.3\lazproj>lazbuild -B dexeddesigncontrols.lpk
Hint: (lazarus) Missing state file of DexedDesignControls 0.0: 
C:\temp\dexed-v3.8.3\lazproj\lib\x86_64-win64\DexedDesignControls.compiled
Info: (lazarus) Execute Title="Compile package 
DexedDesignControls 0.0"
Info: (lazarus) Working Directory="C:\temp\dexed-v3.8.3\lazproj\"
Info: (lazarus) 
Executable="C:\lazarus\fpc\3.0.4\bin\x86_64-win64\fpc.exe"
Info: (lazarus) Param[0]="-B"
Info: (lazarus) Param[1]="-MObjFPC"
Info: (lazarus) Param[2]="-Scghi"
Info: (lazarus) Param[3]="-O2"
Info: (lazarus) Param[4]="-g"
Info: (lazarus) Param[5]="-gl"
Info: (lazarus) Param[6]="-l"
Info: (lazarus) Param[7]="-venhibq"
Info: (lazarus) Param[8]="-vw-"
Info: (lazarus) Param[9]="-FuC:\temp\dexed-v3.8.3\src"
Info: (lazarus) 
Param[10]="-FuC:\lazarus\packager\units\x86_64-win64"
Info: (lazarus) 
Param[11]="-FuC:\lazarus\components\lazutils\lib\x86_64-win64"
Info: (lazarus) Param[12]="-FuC:\lazarus\lcl\units\x86_64-win64"
Info: (lazarus) 
Param[13]="-FuC:\lazarus\lcl\units\x86_64-win64\win32"
Info: (lazarus) Param[14]="-FuC:\temp\dexed-v3.8.3\lazproj\"
Info: (lazarus) 
Param[15]="-FUC:\temp\dexed-v3.8.3\lazproj\lib\x86_64-win64\"
Info: (lazarus) Param[16]="-dLCL"
Info: (lazarus) Param[17]="-dLCLwin32"
Info: (lazarus) Param[18]="dexeddesigncontrols.pas"
Hint: (11030) Start of reading config file 
C:\lazarus\fpc\3.0.4\bin\x86_64-win64\fpc.cfg
Hint: (11031) End of reading config file 
C:\lazarus\fpc\3.0.4\bin\x86_64-win64\fpc.cfg
Free Pascal Compiler version 3.0.4 [2019/10/27] for x86_64
Copyright (c) 1993-2017 by Florian Klaempfl and others
(1002) Target OS: Win64 for x64
(3104) Compiling dexeddesigncontrols.pas
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_dsgncontrols.pas
C:\temp\dexed-v3.8.3\src\u_dsgncontrols.pas(48,29) Hint: (5024) 
Parameter "sender" not used
C:\temp\dexed-v3.8.3\src\u_dsgncontrols.pas(49,30) Hint: (5024) 
Parameter "sender" not used
C:\temp\dexed-v3.8.3\src\u_dsgncontrols.pas(50,32) Hint: (5024) 
Parameter "sender" not used
C:\temp\dexed-v3.8.3\src\u_dsgncontrols.pas(52,34) Hint: (5024) 
Parameter "sender" not used
C:\temp\dexed-v3.8.3\src\u_dsgncontrols.pas(51,31) Hint: (5024) 
Parameter "sender" not used
(1008) 380 lines compiled, 0.8 sec
(1022) 7 hint(s) issued

C:\temp\dexed-v3.8.3\lazproj>lazbuild -B dexed.lpi
TProject.DoLoadStateFile Statefile not found: 
C:\temp\dexed-v3.8.3\lazproj\lib\x86_64-win64\dexed.compiled
Info: (lazarus) Execute Title="Compile Project, Mode: Release, 
Target: C:\temp\dexed-v3.8.3\bin\dexed.exe"
Info: (lazarus) Working Directory="C:\temp\dexed-v3.8.3\lazproj\"
Info: (lazarus) 
Executable="C:\lazarus\fpc\3.0.4\bin\x86_64-win64\fpc.exe"
Info: (lazarus) Param[0]="-B"
Info: (lazarus) Param[1]="-MObjFPC"
Info: (lazarus) Param[2]="-Scghi"
Info: (lazarus) Param[3]="-CX"
Info: (lazarus) Param[4]="-O3"
Info: (lazarus) Param[5]="-XX"
Info: (lazarus) Param[6]="-WG"
Info: (lazarus) Param[7]="-l"
Info: (lazarus) Param[8]="-vewnibq"
Info: (lazarus) Param[9]="-vh-"
Info: (lazarus) Param[10]="-vm5024"
Info: (lazarus) 
Param[11]="-FiC:\temp\dexed-v3.8.3\lazproj\lib\x86_64-win64"
Info: (lazarus) Param[12]="-FuC:\temp\dexed-v3.8.3\src"
Info: (lazarus) Param[13]="-FuC:\temp\dexed-v3.8.3\etc\terminal"
Info: (lazarus) 
Param[14]="-FuC:\lazarus\components\tachart\lib\x86_64-win64\win32"
Info: (lazarus) 
Param[15]="-FuC:\lazarus\components\rtticontrols\lib\x86_64-win64\win32"
Info: (lazarus) 
Param[16]="-FuC:\lazarus\components\ideintf\units\x86_64-win64\win32"
Info: (lazarus) 
Param[17]="-FuC:\lazarus\components\synedit\units\x86_64-win64\win32"
Info: (lazarus) 
Param[18]="-FuC:\lazarus\components\lazcontrols\lib\x86_64-win64\win32"
Info: (lazarus) 
Param[19]="-FuC:\temp\dexed-v3.8.3\lazproj\lib\x86_64-win64"
Info: (lazarus) 
Param[20]="-FuC:\lazarus\components\anchordocking\lib\x86_64-win64"
Info: (lazarus) 
Param[21]="-FuC:\lazarus\lcl\units\x86_64-win64\win32"
Info: (lazarus) Param[22]="-FuC:\lazarus\lcl\units\x86_64-win64"
Info: (lazarus) 
Param[23]="-FuC:\lazarus\components\lazutils\lib\x86_64-win64"
Info: (lazarus) 
Param[24]="-FuC:\lazarus\packager\units\x86_64-win64"
Info: (lazarus) Param[25]="-FuC:\temp\dexed-v3.8.3\lazproj\"
Info: (lazarus) 
Param[26]="-FUC:\temp\dexed-v3.8.3\lazproj\lib\x86_64-win64\"
Info: (lazarus) Param[27]="-FEC:\temp\dexed-v3.8.3\bin\"
Info: (lazarus) Param[28]="-oC:\temp\dexed-v3.8.3\bin\dexed.exe"
Info: (lazarus) Param[29]="-dLCL"
Info: (lazarus) Param[30]="-dLCLwin32"
Info: (lazarus) Param[31]="-dRELEASE"
Info: (lazarus) Param[32]="dexed.lpr"
Compiling Release Version
Free Pascal Compiler version 3.0.4 [2019/10/27] for x86_64
Copyright (c) 1993-2017 by Florian Klaempfl and others
(1002) Target OS: Win64 for x64
(3104) Compiling dexed.lpr
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_sharedres.pas
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_observer.pas
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_common.pas
Warning: (5059) Function result variable does not seem to 
initialized
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_libman.pas
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_writablecomponent.pas
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_dcd.pas
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_interfaces.pas
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_synmemo.pas
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_d2syn.pas
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_dlangutils.pas
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_dlangmaps.pas
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_txtsyn.pas
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_dialogs.pas
(3104) Compiling C:\temp\dexed-v3.8.3\src\u_dastworx.pas
C:\temp\dexed-v3.8.3\src\u_dastworx.pas(92,9) Error: (5000) 
Identifier not found "dlgOkError"
C:\temp\dexed-v3.8.3\src\u_dastworx.pas(103,9) Error: (5000) 
Identifier not found "dlgOkError"
u_dastworx.pas(199) Fatal: (10026) There were 2 errors compiling 
module, stopping
Fatal: (1018) Compilation aborted
Error: C:\lazarus\fpc\3.0.4\bin\x86_64-win64\ppcx64.exe returned 
an error exitcode
Error: (lazarus) Compile Project, Mode: Release, Target: 
C:\temp\dexed-v3.8.3\bin\dexed.exe: stopped with exit code 1
Error: (lazbuild) failed compiling of project 
C:\temp\dexed-v3.8.3\lazproj\dexed.lpi


I am using the last Lazarus 2.0.6 with FPC 3.0.4, on a Win10 64 
machine
Apr 11
parent reply Basile B. <b2.temp gmx.com> writes:
On Saturday, 11 April 2020 at 14:05:43 UTC, RegeleIONESCU wrote:
 Dear Sir, I am following your instructions on how to compile 
 and build Dexed on Windows 10. Could you please help me find 
 out why I get the following error?

 [...]
Sorry I don't know how I've managed to miss your message since the 11. Maybe it's because the topic was more about Akira's fork originally. The compiler error message means that u_dastworx is missing in the "use" clause (it's like D imports). You can try to add it by editing u_dastworx.pas.
 Fatal: (1018) Compilation aborted
 Error: C:\lazarus\fpc\3.0.4\bin\x86_64-win64\ppcx64.exe 
 returned an error exitcode
 Error: (lazarus) Compile Project, Mode: Release, Target: 
 C:\temp\dexed-v3.8.3\bin\dexed.exe: stopped with exit code 1
 Error: (lazbuild) failed compiling of project 
 C:\temp\dexed-v3.8.3\lazproj\dexed.lpi

 [...]
Note that the problem wont be fixed. 1. next version, v3.9.0, doesn't use dastworx anymore but rather a library, compiled with LDC. 2. I don't support Windows anymore so people have to submit their fixes if they want dexed to continue working on Windows. This can be done by sending me patches by email (clone the gitlab project, look at the git history to find my mail) or gitlab merge_requests.
Apr 24
parent Basile B. <b2.temp gmx.com> writes:
On Friday, 24 April 2020 at 08:44:10 UTC, Basile B. wrote:
 On Saturday, 11 April 2020 at 14:05:43 UTC, RegeleIONESCU wrote:
 Dear Sir, I am following your instructions on how to compile 
 and build Dexed on Windows 10. Could you please help me find 
 out why I get the following error?

 [...]
Sorry I don't know how I've managed to miss your message since the 11. Maybe it's because the topic was more about Akira's fork originally. The compiler error message means that u_dastworx is missing in the "use" clause (it's like D imports). You can try to add it by editing u_dastworx.pas.
 Fatal: (1018) Compilation aborted
 Error: C:\lazarus\fpc\3.0.4\bin\x86_64-win64\ppcx64.exe 
 returned an error exitcode
 Error: (lazarus) Compile Project, Mode: Release, Target: 
 C:\temp\dexed-v3.8.3\bin\dexed.exe: stopped with exit code 1
 Error: (lazbuild) failed compiling of project 
 C:\temp\dexed-v3.8.3\lazproj\dexed.lpi

 [...]
Note that the problem wont be fixed. 1. next version, v3.9.0, doesn't use dastworx anymore but rather a library, compiled with LDC. 2. I don't support Windows anymore so people have to submit their fixes if they want dexed to continue working on Windows. This can be done by sending me patches by email (clone the gitlab project, look at the git history to find my mail) or gitlab merge_requests.
I think that this might work fine actually. On linux I've just updated LDC and linking the new library doesn't require anything to be moved thanks to "-link-defaultlib-shared=false" so after clonig master, installing Laz and FPC 1. Have the path to ldc binaries in your PATH env variable 2. $ lazbuild -B dexeddesigncontrols.lpk 3. $ lazbuild -B dexed.lpi should be enough. At the beginning of step 3, DUB is automatically called to build the library. on linux the shortcut to dexed must now include a special env change so that the shell sees the library. For example, the "Exec" value of the .desktop file should be env LD_LIBRARY_PATH=<path to dexed bin> <path to dexed bin>/dexed mine concrectly is env LD_LIBRARY_PATH=~/dev/projects/dexed/bin ~/dev/projects/dexed/bin/dexed on windows I think that a dll is still detected when it stands in the same folder as the exe requiring it. To be verified. Everything is up to date here : https://basile.b.gitlab.io/dexed/build.html It just that nobody has tested if the windows version is still ok.
Apr 24
prev sibling parent Boris Carvajal <boris2.9 gmail.com> writes:
On Thursday, 17 October 2019 at 13:03:08 UTC, Akira1364 wrote:
 I was able to track down a full copy of 
 almost-the-latest-version of the Dexed repo (version 3.7.4) and 
 have put it up here:

 https://github.com/Akira13641/dexed
Someone replied on your reddit thread with a more up to date version (3.7.9) that includes the git commit history. https://github.com/Kozzi11/dexed
Nov 13 2019