Skip to content
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

Opening Pixeleditor #13

Closed
1 task done
matveysiva opened this issue May 14, 2024 · 2 comments
Closed
1 task done

Opening Pixeleditor #13

matveysiva opened this issue May 14, 2024 · 2 comments
Assignees
Labels

Comments

@matveysiva
Copy link

matveysiva commented May 14, 2024

As a User I want to be able to open Pixel Editor through the Apps Toolbar in squeak in order to access it quickly.

  • There has to be a button under "App" whith which you can open the Pixel Editor
@Deltapie-dev Deltapie-dev added enhancement New feature or request 5 Storypoints labels May 14, 2024
@Gunes315 Gunes315 added the Sprint Part of current Sprint label May 14, 2024
@GHOS939
Copy link

GHOS939 commented May 28, 2024

registering needs to be done "by-hand" in every new squeak image
this can't be changed as far as we know --> discuss with customer to approve

@GHOS939 GHOS939 added done - not seen by customer and removed Sprint Part of current Sprint 5 Storypoints labels May 28, 2024
@ekrebs5
Copy link
Member

ekrebs5 commented May 28, 2024

This won't help for users downloading your project via git, but the two mainways to things like installation etc for people outside your team are the following:

  • You create a so called baseline for your project. The baseline can define stuff like dependencies, but also supports a #postload method that is executed after all classes are loaded. This is the way SwaLint is added to your SWT images, we just load the baseline (https://github.com/hpi-swa-teaching/SwaLint)
  • You can register it in the #initialize method of one of your classes: When the class is first added to the system, your app is registered (this version might be git-loading compatible).
  • If you mainly want to share your project via sar files, similar to the preamble in the example script you can also add a postscript that is executed after all files from the sar are loaded.

To give your project to swa students, the first two versions would be preferred, sar loading would be difficult :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants