https://linen.dev logo
Powered by
# haxe-ui
  • b
    ah other way around. Don't generate seperate externs just include libs and call exclude
  • p
    > Don't generate seperate externs just include libs and call exclude Yes, that's what I meant.
  • b
    the problem here is of course that macros that are not needed are called anyway. In addition, the files are also completely parsed.
  • p
    And why is that a problem?
  • b
    This consumes time. And it is very inconvenient if you have to wait 4 seconds each time until something appears.
  • p
    The compilation server should help with time consuming compilation.
  • b
    not rly. if you swap out the hxml file you need to rebuild the complete cache.
  • b
    perhaps first so my thought:
  • p
    Run two separate instances of the server? This won't integrate well with VSHaxe though. Also, why are you splitting up (in your code and base.js) in the first place?
  • b
    so - base, here is haxe.ui located, this part does not change and should be precompiled, it also contains the code for the display in vscode afterwards - project - if a .hx file is changed, the following should be done by vs code: - parse current hxml file. - compile the single .hx file as module to js but with the project path and libs from the hxml file (without compiling the base each time of course) - the base gets then that a .hx file would be changed and reloads accordingly - the base itself (js) then inludes all necessary compiled .hx files.
  • b
    if a file cannot be compiled (a single one) a haxe.ui.component.ErrorBox should simply be displayed.
  • p
    And what's the goal of this whole setup? Because it's probably doable, but complicated.
  • b
    The goal is of course to get a preview that is displayed quickly. On the other hand, own components can be and then of course in the case of faulty components not simply nothing more displayed.
  • b
  • b
    But this works only with xml and core elements
  • p
    And is "full" (ie haxeui + your code) compilation using the compilation server really that slow? (And I think the plan as described above will cost more time than you'll gain.) Preview inside VSCode sounds nice though.
  • b
    the problem here is the changing hxml file. Since the element which is compiled is always replaced, the whole cache is rebuilt. I have unfortunately not found so much documentation about this server. If it is possible to change a hxml file without re-caching the whole project. (if of course -cp does not change).
  • b
    With the server, of course, it would be much easier.
  • b
    When cached, it only lasts 0.1 second.
  • p
    Changing compilation parameters will always trigger a cache rebuild, and there's nothing you can do about that afaik.
  • b
    And there's the problem. I would actually only have to replace the current module. But unfortunately that is not possible.
  • b
    i have an idea
  • b
    let's use the idea of the compilation server. - we build a hxml based on the current hxml file - remove all modules or main classes from this hxml file - hxml -> add a haxe.ui.Preview to it - this file will be rewritten by us every time which module is needed. with maybe a simple method like public static function getComponent():Class { return somecustompackage.MyOwnButton; } - since the hxml file does not change the server should not be reloaded. - you can tell the compiler which module should be active by changing the getComponent function.
  • b
    do you think it could work?
  • p
    Think so. But why build every module seperately?
  • b
    to guarantee a display even if a component does not work.
  • b
    because you are limited to html5 it can happen that for example wxwidget projects cpp is used. So native components would not work in a html5 project. Therefore, there should rather just a red box be displayed instead of just nothing.
  • p
    Or just don't support native components? I think you're making this very complex, for not much gain.
  • b
    Do you think there might be a problem afterwards?
  • b
    i could set up a mandatory html5 target for the display. Vscode.haxe.activeBuildFile is html5
1...995996997...1687Latest