New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to write a new backend for McCLIM #64

Open
ailisp opened this Issue Aug 14, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@ailisp
Contributor

ailisp commented Aug 14, 2016

I remember that there were gtkairo and graphicforms backends for McCLIM. If I want to write a new backend wrap native windows api to enable McCLIM to run under Windows, which files, classes and function/methods should be implemented? Which folder in the Backends folder can be a good reference? Thanks.

@dkochmanski

This comment has been minimized.

Show comment
Hide comment
@dkochmanski

dkochmanski Aug 14, 2016

Collaborator

Hey, currently we have no clear instructions how to write a new backend (we want to have such guide though). Current focus is targeted at improving CLX backend.

The other backends were broken and I won't be ably to provide any information on them except information covered here, but if you want to work on them here are some tips:

Regarding the system definitions, keep in mind that some systems might have changed their names. Regarding the dependencies, I'd look at CLX backend. Backend "Standard" is just a shared implementation of some functions.

If you want to change the default backend, you need to change Core/clim-basic/ports.lisp *server-path-search-order* to find your backend first and toplevel mcclim.asd system mcclim/looks to load your backend if accessible.

Toplevel file package.lisp contains a package clim-backend with a comment mentioning, that this symbols "must be defined by a backend" – it may be a good starting point to read them.

Collaborator

dkochmanski commented Aug 14, 2016

Hey, currently we have no clear instructions how to write a new backend (we want to have such guide though). Current focus is targeted at improving CLX backend.

The other backends were broken and I won't be ably to provide any information on them except information covered here, but if you want to work on them here are some tips:

Regarding the system definitions, keep in mind that some systems might have changed their names. Regarding the dependencies, I'd look at CLX backend. Backend "Standard" is just a shared implementation of some functions.

If you want to change the default backend, you need to change Core/clim-basic/ports.lisp *server-path-search-order* to find your backend first and toplevel mcclim.asd system mcclim/looks to load your backend if accessible.

Toplevel file package.lisp contains a package clim-backend with a comment mentioning, that this symbols "must be defined by a backend" – it may be a good starting point to read them.

@ailisp

This comment has been minimized.

Show comment
Hide comment
@ailisp

ailisp Aug 14, 2016

Contributor

Thanks, its quite detailed. I will try to write a windows backend.

Contributor

ailisp commented Aug 14, 2016

Thanks, its quite detailed. I will try to write a windows backend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment